1 Changes in version 0.2.6.1-alpha - 2014-??-??
4 Changes in version 0.2.5.6-alpha - 2014-07-28
5 Tor 0.2.5.6-alpha brings us a big step closer to slowing down the
6 risk from guard rotation, and fixes a variety of other issues to get
7 us closer to a release candidate.
9 o Major features (also in 0.2.4.23):
10 - Make the number of entry guards configurable via a new
11 NumEntryGuards consensus parameter, and the number of directory
12 guards configurable via a new NumDirectoryGuards consensus
13 parameter. Implements ticket 12688.
15 o Major bugfixes (also in 0.2.4.23):
16 - Fix a bug in the bounds-checking in the 32-bit curve25519-donna
17 implementation that caused incorrect results on 32-bit
18 implementations when certain malformed inputs were used along with
19 a small class of private ntor keys. This bug does not currently
20 appear to allow an attacker to learn private keys or impersonate a
21 Tor server, but it could provide a means to distinguish 32-bit Tor
22 implementations from 64-bit Tor implementations. Fixes bug 12694;
23 bugfix on 0.2.4.8-alpha. Bug found by Robert Ransom; fix from
27 - Perform circuit cleanup operations even when circuit
28 construction operations are disabled (because the network is
29 disabled, or because there isn't enough directory information).
30 Previously, when we were not building predictive circuits, we
31 were not closing expired circuits either. Fixes bug 8387; bugfix on
32 0.1.1.11-alpha. This bug became visible in 0.2.4.10-alpha when we
33 became more strict about when we have "enough directory information
37 - Authorities now assign the Guard flag to the fastest 25% of the
38 network (it used to be the fastest 50%). Also raise the consensus
39 weight that guarantees the Guard flag from 250 to 2000. For the
40 current network, this results in about 1100 guards, down from 2500.
41 This step paves the way for moving the number of entry guards
42 down to 1 (proposal 236) while still providing reasonable expected
43 performance for most users. Implements ticket 12690.
44 - Update geoip and geoip6 to the July 10 2014 Maxmind GeoLite2
46 - Slightly enhance the diagnostic message for bug 12184.
48 o Minor bugfixes (also in 0.2.4.23):
49 - Warn and drop the circuit if we receive an inbound 'relay early'
50 cell. Those used to be normal to receive on hidden service circuits
51 due to bug 1038, but the buggy Tor versions are long gone from
52 the network so we can afford to resume watching for them. Resolves
53 the rest of bug 1038; bugfix on 0.2.1.19.
54 - Correct a confusing error message when trying to extend a circuit
55 via the control protocol but we don't know a descriptor or
56 microdescriptor for one of the specified relays. Fixes bug 12718;
57 bugfix on 0.2.3.1-alpha.
60 - Fix compilation when building with bufferevents enabled. (This
61 configuration is still not expected to work, however.)
62 Fixes bugs 12438, 12474, 11578; bugfixes on 0.2.5.1-alpha and
63 0.2.5.3-alpha. Patches from Anthony G. Basile and Sathyanarayanan
65 - Compile correctly with builds and forks of OpenSSL (such as
66 LibreSSL) that disable compression. Fixes bug 12602; bugfix on
67 0.2.1.1-alpha. Patch from "dhill".
70 Changes in version 0.2.4.23 - 2014-07-28
71 Tor 0.2.4.23 brings us a big step closer to slowing down the risk from
72 guard rotation, and also backports several important fixes from the
73 Tor 0.2.5 alpha release series.
76 - Clients now look at the "usecreatefast" consensus parameter to
77 decide whether to use CREATE_FAST or CREATE cells for the first hop
78 of their circuit. This approach can improve security on connections
79 where Tor's circuit handshake is stronger than the available TLS
80 connection security levels, but the tradeoff is more computational
81 load on guard relays. Implements proposal 221. Resolves ticket 9386.
82 - Make the number of entry guards configurable via a new
83 NumEntryGuards consensus parameter, and the number of directory
84 guards configurable via a new NumDirectoryGuards consensus
85 parameter. Implements ticket 12688.
88 - Fix a bug in the bounds-checking in the 32-bit curve25519-donna
89 implementation that caused incorrect results on 32-bit
90 implementations when certain malformed inputs were used along with
91 a small class of private ntor keys. This bug does not currently
92 appear to allow an attacker to learn private keys or impersonate a
93 Tor server, but it could provide a means to distinguish 32-bit Tor
94 implementations from 64-bit Tor implementations. Fixes bug 12694;
95 bugfix on 0.2.4.8-alpha. Bug found by Robert Ransom; fix from
99 - Warn and drop the circuit if we receive an inbound 'relay early'
100 cell. Those used to be normal to receive on hidden service circuits
101 due to bug 1038, but the buggy Tor versions are long gone from
102 the network so we can afford to resume watching for them. Resolves
103 the rest of bug 1038; bugfix on 0.2.1.19.
104 - Correct a confusing error message when trying to extend a circuit
105 via the control protocol but we don't know a descriptor or
106 microdescriptor for one of the specified relays. Fixes bug 12718;
107 bugfix on 0.2.3.1-alpha.
108 - Avoid an illegal read from stack when initializing the TLS
109 module using a version of OpenSSL without all of the ciphers
110 used by the v2 link handshake. Fixes bug 12227; bugfix on
111 0.2.4.8-alpha. Found by "starlight".
114 - Update geoip and geoip6 to the July 10 2014 Maxmind GeoLite2
118 Changes in version 0.2.5.5-alpha - 2014-06-18
119 Tor 0.2.5.5-alpha fixes a wide variety of remaining issues in the Tor
120 0.2.5.x release series, including a couple of DoS issues, some
121 performance regressions, a large number of bugs affecting the Linux
122 seccomp2 sandbox code, and various other bugfixes. It also adds
123 diagnostic bugfixes for a few tricky issues that we're trying to
126 o Major features (security, traffic analysis resistance):
127 - Several major improvements to the algorithm used to decide when to
128 close TLS connections. Previous versions of Tor closed connections
129 at a fixed interval after the last time a non-padding cell was
130 sent over the connection, regardless of the target of the
131 connection. Now, we randomize the intervals by adding up to 50% of
132 their base value, we measure the length of time since connection
133 last had at least one circuit, and we allow connections to known
134 ORs to remain open a little longer (15 minutes instead of 3
135 minutes minimum). These changes should improve Tor's resistance
136 against some kinds of traffic analysis, and lower some overhead
137 from needlessly closed connections. Fixes ticket 6799.
138 Incidentally fixes ticket 12023; bugfix on 0.2.5.1-alpha.
140 o Major bugfixes (security, OOM, new since 0.2.5.4-alpha, also in 0.2.4.22):
141 - Fix a memory leak that could occur if a microdescriptor parse
142 fails during the tokenizing step. This bug could enable a memory
143 exhaustion attack by directory servers. Fixes bug 11649; bugfix
146 o Major bugfixes (security, directory authorities):
147 - Directory authorities now include a digest of each relay's
148 identity key as a part of its microdescriptor.
150 This is a workaround for bug 11743 (reported by "cypherpunks"),
151 where Tor clients do not support receiving multiple
152 microdescriptors with the same SHA256 digest in the same
153 consensus. When clients receive a consensus like this, they only
154 use one of the relays. Without this fix, a hostile relay could
155 selectively disable some client use of target relays by
156 constructing a router descriptor with a different identity and the
157 same microdescriptor parameters and getting the authorities to
158 list it in a microdescriptor consensus. This fix prevents an
159 attacker from causing a microdescriptor collision, because the
160 router's identity is not forgeable.
162 o Major bugfixes (relay):
163 - Use a direct dirport connection when uploading non-anonymous
164 descriptors to the directory authorities. Previously, relays would
165 incorrectly use tunnel connections under a fairly wide variety of
166 circumstances. Fixes bug 11469; bugfix on 0.2.4.3-alpha.
167 - When a circuit accidentally has the same circuit ID for its
168 forward and reverse direction, correctly detect the direction of
169 cells using that circuit. Previously, this bug made roughly one
170 circuit in a million non-functional. Fixes bug 12195; this is a
171 bugfix on every version of Tor.
173 o Major bugfixes (client, pluggable transports):
174 - When managing pluggable transports, use OS notification facilities
175 to learn if they have crashed, and don't attempt to kill any
176 process that has already exited. Fixes bug 8746; bugfix
179 o Minor features (diagnostic):
180 - When logging a warning because of bug 7164, additionally check the
181 hash table for consistency (as proposed on ticket 11737). This may
182 help diagnose bug 7164.
183 - When we log a heartbeat, log how many one-hop circuits we have
184 that are at least 30 minutes old, and log status information about
185 a few of them. This is an attempt to track down bug 8387.
186 - When encountering an unexpected CR while writing text to a file on
187 Windows, log the name of the file. Should help diagnosing
189 - Give more specific warnings when a client notices that an onion
190 handshake has failed. Fixes ticket 9635.
191 - Add significant new logging code to attempt to diagnose bug 12184,
192 where relays seem to run out of available circuit IDs.
193 - Improve the diagnostic log message for bug 8387 even further to
194 try to improve our odds of figuring out why one-hop directory
195 circuits sometimes do not get closed.
197 o Minor features (security, memory management):
198 - Memory allocation tricks (mempools and buffer freelists) are now
199 disabled by default. You can turn them back on with
200 --enable-mempools and --enable-buf-freelists respectively. We're
201 disabling these features because malloc performance is good enough
202 on most platforms, and a similar feature in OpenSSL exacerbated
203 exploitation of the Heartbleed attack. Resolves ticket 11476.
205 o Minor features (security):
206 - Apply the secure SipHash-2-4 function to the hash table mapping
207 circuit IDs and channels to circuits. We missed this one when we
208 were converting all the other hash functions to use SipHash back
209 in 0.2.5.3-alpha. Resolves ticket 11750.
211 o Minor features (build):
212 - The configure script has a --disable-seccomp option to turn off
213 support for libseccomp on systems that have it, in case it (or
214 Tor's use of it) is broken. Resolves ticket 11628.
216 o Minor features (other):
217 - Update geoip and geoip6 to the June 4 2014 Maxmind GeoLite2
220 o Minor bugfixes (security, new since 0.2.5.4-alpha, also in 0.2.4.22):
221 - When running a hidden service, do not allow TunneledDirConns 0;
222 this will keep the hidden service from running, and also
223 make it publish its descriptors directly over HTTP. Fixes bug 10849;
224 bugfix on 0.2.1.1-alpha.
226 o Minor bugfixes (performance):
227 - Avoid a bug where every successful connection made us recompute
228 the flag telling us whether we have sufficient information to
229 build circuits. Previously, we would forget our cached value
230 whenever we successfully opened a channel (or marked a router as
231 running or not running for any other reason), regardless of
232 whether we had previously believed the router to be running. This
233 forced us to run an expensive update operation far too often.
234 Fixes bug 12170; bugfix on 0.1.2.1-alpha.
235 - Avoid using tor_memeq() for checking relay cell integrity. This
236 removes a possible performance bottleneck. Fixes part of bug
237 12169; bugfix on 0.2.1.31.
239 o Minor bugfixes (compilation):
240 - Fix compilation of test_status.c when building with MVSC. Bugfix
241 on 0.2.5.4-alpha. Patch from Gisle Vanem.
242 - Resolve GCC complaints on OpenBSD about discarding constness in
243 TO_{ORIGIN,OR}_CIRCUIT functions. Fixes part of bug 11633; bugfix
244 on 0.1.1.23. Patch from Dana Koch.
245 - Resolve clang complaints on OpenBSD with -Wshorten-64-to-32 due to
246 treatment of long and time_t as comparable types. Fixes part of
247 bug 11633. Patch from Dana Koch.
248 - Make Tor compile correctly with --disable-buf-freelists. Fixes bug
249 11623; bugfix on 0.2.5.3-alpha.
250 - When deciding whether to build the 64-bit curve25519
251 implementation, detect platforms where we can compile 128-bit
252 arithmetic but cannot link it. Fixes bug 11729; bugfix on
253 0.2.4.8-alpha. Patch from "conradev".
254 - Fix compilation when DNS_CACHE_DEBUG is enabled. Fixes bug 11761;
255 bugfix on 0.2.3.13-alpha. Found by "cypherpunks".
256 - Fix compilation with dmalloc. Fixes bug 11605; bugfix
259 o Minor bugfixes (Directory server):
260 - When sending a compressed set of descriptors or microdescriptors,
261 make sure to finalize the zlib stream. Previously, we would write
262 all the compressed data, but if the last descriptor we wanted to
263 send was missing or too old, we would not mark the stream as
264 finished. This caused problems for decompression tools. Fixes bug
265 11648; bugfix on 0.1.1.23.
267 o Minor bugfixes (Linux seccomp sandbox):
268 - Make the seccomp sandbox code compile under ARM Linux. Fixes bug
269 11622; bugfix on 0.2.5.1-alpha.
270 - Avoid crashing when re-opening listener ports with the seccomp
271 sandbox active. Fixes bug 12115; bugfix on 0.2.5.1-alpha.
272 - Avoid crashing with the seccomp sandbox enabled along with
273 ConstrainedSockets. Fixes bug 12139; bugfix on 0.2.5.1-alpha.
274 - When we receive a SIGHUP with the sandbox enabled, correctly
275 support rotating our log files. Fixes bug 12032; bugfix
277 - Avoid crash when running with sandboxing enabled and
278 DirReqStatistics not disabled. Fixes bug 12035; bugfix
280 - Fix a "BUG" warning when trying to write bridge-stats files with
281 the Linux syscall sandbox filter enabled. Fixes bug 12041; bugfix
283 - Prevent the sandbox from crashing on startup when run with the
284 --enable-expensive-hardening configuration option. Fixes bug
285 11477; bugfix on 0.2.5.4-alpha.
286 - When running with DirPortFrontPage and sandboxing both enabled,
287 reload the DirPortFrontPage correctly when restarting. Fixes bug
288 12028; bugfix on 0.2.5.1-alpha.
289 - Don't try to enable the sandbox when using the Tor binary to check
290 its configuration, hash a passphrase, or so on. Doing so was
291 crashing on startup for some users. Fixes bug 11609; bugfix
293 - Avoid warnings when running with sandboxing and node statistics
294 enabled at the same time. Fixes part of 12064; bugfix on
295 0.2.5.1-alpha. Patch from Michael Wolf.
296 - Avoid warnings when running with sandboxing enabled at the same
297 time as cookie authentication, hidden services, or directory
298 authority voting. Fixes part of 12064; bugfix on 0.2.5.1-alpha.
299 - Do not allow options that require calls to exec to be enabled
300 alongside the seccomp2 sandbox: they will inevitably crash. Fixes
301 bug 12043; bugfix on 0.2.5.1-alpha.
302 - Handle failures in getpwnam()/getpwuid() when running with the
303 User option set and the Linux syscall sandbox enabled. Fixes bug
304 11946; bugfix on 0.2.5.1-alpha.
305 - Refactor the getaddrinfo workaround that the seccomp sandbox uses
306 to avoid calling getaddrinfo() after installing the sandbox
307 filters. Previously, it preloaded a cache with the IPv4 address
308 for our hostname, and nothing else. Now, it loads the cache with
309 every address that it used to initialize the Tor process. Fixes
310 bug 11970; bugfix on 0.2.5.1-alpha.
312 o Minor bugfixes (pluggable transports):
313 - Enable the ExtORPortCookieAuthFile option, to allow changing the
314 default location of the authentication token for the extended OR
315 Port as used by sever-side pluggable transports. We had
316 implemented this option before, but the code to make it settable
317 had been omitted. Fixes bug 11635; bugfix on 0.2.5.1-alpha.
318 - Avoid another 60-second delay when starting Tor in a pluggable-
319 transport-using configuration when we already have cached
320 descriptors for our bridges. Fixes bug 11965; bugfix
323 o Minor bugfixes (client):
324 - Avoid "Tried to open a socket with DisableNetwork set" warnings
325 when starting a client with bridges configured and DisableNetwork
326 set. (Tor launcher starts Tor with DisableNetwork set the first
327 time it runs.) Fixes bug 10405; bugfix on 0.2.3.9-alpha.
329 o Minor bugfixes (testing):
330 - The Python parts of the test scripts now work on Python 3 as well
331 as Python 2, so systems where '/usr/bin/python' is Python 3 will
332 no longer have the tests break. Fixes bug 11608; bugfix
334 - When looking for versions of python that we could run the tests
335 with, check for "python2.7" and "python3.3"; previously we were
336 only looking for "python", "python2", and "python3". Patch from
337 Dana Koch. Fixes bug 11632; bugfix on 0.2.5.2-alpha.
338 - Fix all valgrind warnings produced by the unit tests. There were
339 over a thousand memory leak warnings previously, mostly produced
340 by forgetting to free things in the unit test code. Fixes bug
341 11618, bugfixes on many versions of Tor.
343 o Minor bugfixes (tor-fw-helper):
344 - Give a correct log message when tor-fw-helper fails to launch.
345 (Previously, we would say something like "tor-fw-helper sent us a
346 string we could not parse".) Fixes bug 9781; bugfix
349 o Minor bugfixes (relay, threading):
350 - Check return code on spawn_func() in cpuworker code, so that we
351 don't think we've spawned a nonworking cpuworker and write junk to
352 it forever. Fix related to bug 4345; bugfix on all released Tor
353 versions. Found by "skruffy".
354 - Use a pthread_attr to make sure that spawn_func() cannot return an
355 error while at the same time launching a thread. Fix related to
356 bug 4345; bugfix on all released Tor versions. Reported
359 o Minor bugfixes (relay, oom prevention):
360 - Correctly detect the total available system memory. We tried to do
361 this in 0.2.5.4-alpha, but the code was set up to always return an
362 error value, even on success. Fixes bug 11805; bugfix
365 o Minor bugfixes (relay, other):
366 - We now drop CREATE cells for already-existent circuit IDs and for
367 zero-valued circuit IDs, regardless of other factors that might
368 otherwise have called for DESTROY cells. Fixes bug 12191; bugfix
370 - Avoid an illegal read from stack when initializing the TLS module
371 using a version of OpenSSL without all of the ciphers used by the
372 v2 link handshake. Fixes bug 12227; bugfix on 0.2.4.8-alpha. Found
374 - When rejecting DATA cells for stream_id zero, still count them
375 against the circuit's deliver window so that we don't fail to send
376 a SENDME. Fixes bug 11246; bugfix on 0.2.4.10-alpha.
378 o Minor bugfixes (logging):
379 - Fix a misformatted log message about delayed directory fetches.
380 Fixes bug 11654; bugfix on 0.2.5.3-alpha.
381 - Squelch a spurious LD_BUG message "No origin circuit for
382 successful SOCKS stream" in certain hidden service failure cases;
386 - Include a tor.service file in contrib/dist for use with systemd.
387 Some distributions will be able to use this file unmodified;
388 others will need to tweak it, or write their own. Patch from Jamie
389 Nguyen; resolves ticket 8368.
392 - Clean up several option names in the manpage to match their real
393 names, add the missing documentation for a couple of testing and
394 directory authority options, remove the documentation for a
395 V2-directory fetching option that no longer exists. Resolves
397 - Correct the documenation so that it lists the correct directory
398 for the stats files. (They are in a subdirectory called "stats",
400 - In the manpage, move more authority-only options into the
401 directory authority section so that operators of regular directory
402 caches don't get confused.
405 - The contrib directory has been sorted and tidied. Before, it was
406 an unsorted dumping ground for useful and not-so-useful things.
407 Now, it is divided based on functionality, and the items which
408 seemed to be nonfunctional or useless have been removed. Resolves
409 ticket 8966; based on patches from "rl1987".
412 - Remove /tor/dbg-stability.txt URL that was meant to help debug WFU
413 and MTBF calculations, but that nobody was using. Fixes #11742.
414 - The TunnelDirConns and PreferTunnelledDirConns options no longer
415 exist; tunneled directory connections have been available since
416 0.1.2.5-alpha, and turning them off is not a good idea. This is a
417 brute-force fix for 10849, where "TunnelDirConns 0" would break
421 Changes in version 0.2.4.22 - 2014-05-16
422 Tor 0.2.4.22 backports numerous high-priority fixes from the Tor 0.2.5
423 alpha release series. These include blocking all authority signing
424 keys that may have been affected by the OpenSSL "heartbleed" bug,
425 choosing a far more secure set of TLS ciphersuites by default, closing
426 a couple of memory leaks that could be used to run a target relay out
427 of RAM, and several others.
429 o Major features (security, backport from 0.2.5.4-alpha):
430 - Block authority signing keys that were used on authorities
431 vulnerable to the "heartbleed" bug in OpenSSL (CVE-2014-0160). (We
432 don't have any evidence that these keys _were_ compromised; we're
433 doing this to be prudent.) Resolves ticket 11464.
435 o Major bugfixes (security, OOM):
436 - Fix a memory leak that could occur if a microdescriptor parse
437 fails during the tokenizing step. This bug could enable a memory
438 exhaustion attack by directory servers. Fixes bug 11649; bugfix
441 o Major bugfixes (TLS cipher selection, backport from 0.2.5.4-alpha):
442 - The relay ciphersuite list is now generated automatically based on
443 uniform criteria, and includes all OpenSSL ciphersuites with
444 acceptable strength and forward secrecy. Previously, we had left
445 some perfectly fine ciphersuites unsupported due to omission or
446 typo. Resolves bugs 11513, 11492, 11498, 11499. Bugs reported by
447 'cypherpunks'. Bugfix on 0.2.4.8-alpha.
448 - Relays now trust themselves to have a better view than clients of
449 which TLS ciphersuites are better than others. (Thanks to bug
450 11513, the relay list is now well-considered, whereas the client
451 list has been chosen mainly for anti-fingerprinting purposes.)
452 Relays prefer: AES over 3DES; then ECDHE over DHE; then GCM over
453 CBC; then SHA384 over SHA256 over SHA1; and last, AES256 over
454 AES128. Resolves ticket 11528.
455 - Clients now try to advertise the same list of ciphersuites as
456 Firefox 28. This change enables selection of (fast) GCM
457 ciphersuites, disables some strange old ciphers, and stops
458 advertising the ECDH (not to be confused with ECDHE) ciphersuites.
459 Resolves ticket 11438.
461 o Minor bugfixes (configuration, security):
462 - When running a hidden service, do not allow TunneledDirConns 0:
463 trying to set that option together with a hidden service would
464 otherwise prevent the hidden service from running, and also make
465 it publish its descriptors directly over HTTP. Fixes bug 10849;
466 bugfix on 0.2.1.1-alpha.
468 o Minor bugfixes (controller, backport from 0.2.5.4-alpha):
469 - Avoid sending a garbage value to the controller when a circuit is
470 cannibalized. Fixes bug 11519; bugfix on 0.2.3.11-alpha.
472 o Minor bugfixes (exit relay, backport from 0.2.5.4-alpha):
473 - Stop leaking memory when we successfully resolve a PTR record.
474 Fixes bug 11437; bugfix on 0.2.4.7-alpha.
476 o Minor bugfixes (bridge client, backport from 0.2.5.4-alpha):
477 - Avoid 60-second delays in the bootstrapping process when Tor is
478 launching for a second time while using bridges. Fixes bug 9229;
479 bugfix on 0.2.0.3-alpha.
481 o Minor bugfixes (relays and bridges, backport from 0.2.5.4-alpha):
482 - Give the correct URL in the warning message when trying to run a
483 relay on an ancient version of Windows. Fixes bug 9393.
485 o Minor bugfixes (compilation):
486 - Fix a compilation error when compiling with --disable-curve25519.
487 Fixes bug 9700; bugfix on 0.2.4.17-rc.
490 - Downgrade the warning severity for the the "md was still
491 referenced 1 node(s)" warning. Tor 0.2.5.4-alpha has better code
492 for trying to diagnose this bug, and the current warning in
493 earlier versions of tor achieves nothing useful. Addresses warning
496 o Minor features (log verbosity, backport from 0.2.5.4-alpha):
497 - When we run out of usable circuit IDs on a channel, log only one
498 warning for the whole channel, and describe how many circuits
499 there were on the channel. Fixes part of ticket 11553.
501 o Minor features (security, backport from 0.2.5.4-alpha):
502 - Decrease the lower limit of MaxMemInCellQueues to 256 MBytes (but
503 leave the default at 8GBytes), to better support Raspberry Pi
504 users. Fixes bug 9686; bugfix on 0.2.4.14-alpha.
506 o Documentation (backport from 0.2.5.4-alpha):
507 - Correctly document that we search for a system torrc file before
508 looking in ~/.torrc. Fixes documentation side of 9213; bugfix on
512 Changes in version 0.2.5.4-alpha - 2014-04-25
513 Tor 0.2.5.4-alpha includes several security and performance
514 improvements for clients and relays, including blacklisting authority
515 signing keys that were used while susceptible to the OpenSSL
516 "heartbleed" bug, fixing two expensive functions on busy relays,
517 improved TLS ciphersuite preference lists, support for run-time
518 hardening on compilers that support AddressSanitizer, and more work on
519 the Linux sandbox code.
521 There are also several usability fixes for clients (especially clients
522 that use bridges), two new TransPort protocols supported (one on
523 OpenBSD, one on FreeBSD), and various other bugfixes.
525 This release marks end-of-life for Tor 0.2.2.x; those Tor versions
526 have accumulated many known flaws; everyone should upgrade.
528 o Major features (security):
529 - If you don't specify MaxMemInQueues yourself, Tor now tries to
530 pick a good value based on your total system memory. Previously,
531 the default was always 8 GB. You can still override the default by
532 setting MaxMemInQueues yourself. Resolves ticket 11396.
533 - Block authority signing keys that were used on authorities
534 vulnerable to the "heartbleed" bug in OpenSSL (CVE-2014-0160). (We
535 don't have any evidence that these keys _were_ compromised; we're
536 doing this to be prudent.) Resolves ticket 11464.
538 o Major features (relay performance):
539 - Speed up server-side lookups of rendezvous and introduction point
540 circuits by using hashtables instead of linear searches. These
541 functions previously accounted between 3 and 7% of CPU usage on
542 some busy relays. Resolves ticket 9841.
543 - Avoid wasting CPU when extending a circuit over a channel that is
544 nearly out of circuit IDs. Previously, we would do a linear scan
545 over possible circuit IDs before finding one or deciding that we
546 had exhausted our possibilities. Now, we try at most 64 random
547 circuit IDs before deciding that we probably won't succeed. Fixes
548 a possible root cause of ticket 11553.
550 o Major features (seccomp2 sandbox, Linux only):
551 - The seccomp2 sandbox can now run a test network for multiple hours
552 without crashing. The sandbox is still experimental, and more bugs
553 will probably turn up. To try it, enable "Sandbox 1" on a Linux
554 host. Resolves ticket 11351.
555 - Strengthen sandbox code: the sandbox can now test the arguments
556 for rename(), and blocks _sysctl() entirely. Resolves another part
558 - When the sandbox blocks a system call, it now tries to log a stack
559 trace before exiting. Resolves ticket 11465.
561 o Major bugfixes (TLS cipher selection):
562 - The relay ciphersuite list is now generated automatically based on
563 uniform criteria, and includes all OpenSSL ciphersuites with
564 acceptable strength and forward secrecy. Previously, we had left
565 some perfectly fine ciphersuites unsupported due to omission or
566 typo. Resolves bugs 11513, 11492, 11498, 11499. Bugs reported by
567 'cypherpunks'. Bugfix on 0.2.4.8-alpha.
568 - Relays now trust themselves to have a better view than clients of
569 which TLS ciphersuites are better than others. (Thanks to bug
570 11513, the relay list is now well-considered, whereas the client
571 list has been chosen mainly for anti-fingerprinting purposes.)
572 Relays prefer: AES over 3DES; then ECDHE over DHE; then GCM over
573 CBC; then SHA384 over SHA256 over SHA1; and last, AES256 over
574 AES128. Resolves ticket 11528.
575 - Clients now try to advertise the same list of ciphersuites as
576 Firefox 28. This change enables selection of (fast) GCM
577 ciphersuites, disables some strange old ciphers, and stops
578 advertising the ECDH (not to be confused with ECDHE) ciphersuites.
579 Resolves ticket 11438.
581 o Major bugfixes (bridge client):
582 - Avoid 60-second delays in the bootstrapping process when Tor is
583 launching for a second time while using bridges. Fixes bug 9229;
584 bugfix on 0.2.0.3-alpha.
586 o Minor features (transparent proxy, *BSD):
587 - Support FreeBSD's ipfw firewall interface for TransPort ports on
588 FreeBSD. To enable it, set "TransProxyType ipfw". Resolves ticket
589 10267; patch from "yurivict".
590 - Support OpenBSD's divert-to rules with the pf firewall for
591 transparent proxy ports. To enable it, set "TransProxyType
592 pf-divert". This allows Tor to run a TransPort transparent proxy
593 port on OpenBSD 4.4 or later without root privileges. See the
594 pf.conf(5) manual page for information on configuring pf to use
595 divert-to rules. Closes ticket 10896; patch from Dana Koch.
597 o Minor features (security):
598 - New --enable-expensive-hardening option to enable security
599 hardening options that consume nontrivial amounts of CPU and
600 memory. Right now, this includes AddressSanitizer and UbSan, which
601 are supported in newer versions of GCC and Clang. Closes ticket
604 o Minor features (log verbosity):
605 - Demote the message that we give when a flushing connection times
606 out for too long from NOTICE to INFO. It was usually meaningless.
607 Resolves ticket 5286.
608 - Don't log so many notice-level bootstrapping messages at startup
609 about downloading descriptors. Previously, we'd log a notice
610 whenever we learned about more routers. Now, we only log a notice
611 at every 5% of progress. Fixes bug 9963.
612 - Warn less verbosely when receiving a malformed
613 ESTABLISH_RENDEZVOUS cell. Fixes ticket 11279.
614 - When we run out of usable circuit IDs on a channel, log only one
615 warning for the whole channel, and describe how many circuits
616 there were on the channel. Fixes part of ticket 11553.
618 o Minor features (relay):
619 - If a circuit timed out for at least 3 minutes, check if we have a
620 new external IP address, and publish a new descriptor with the new
621 IP address if it changed. Resolves ticket 2454.
623 o Minor features (controller):
624 - Make the entire exit policy available from the control port via
625 GETINFO exit-policy/*. Implements enhancement 7952. Patch from
627 - Because of the fix for ticket 11396, the real limit for memory
628 usage may no longer match the configured MaxMemInQueues value. The
629 real limit is now exposed via GETINFO limits/max-mem-in-queues.
631 o Minor features (bridge client):
632 - Report a more useful failure message when we can't connect to a
633 bridge because we don't have the right pluggable transport
634 configured. Resolves ticket 9665. Patch from Fábio J. Bertinatto.
636 o Minor features (diagnostic):
637 - Add more log messages to diagnose bug 7164, which causes
638 intermittent "microdesc_free() called but md was still referenced"
639 warnings. We now include more information, to figure out why we
640 might be cleaning a microdescriptor for being too old if it's
641 still referenced by a live node_t object.
643 o Minor bugfixes (client, DNSPort):
644 - When using DNSPort, try to respond to AAAA requests with AAAA
645 answers. Previously, we hadn't looked at the request type when
646 deciding which answer type to prefer. Fixes bug 10468; bugfix on
648 - When receiving a DNS query for an unsupported record type, reply
649 with no answer rather than with a NOTIMPL error. This behavior
650 isn't correct either, but it will break fewer client programs, we
651 hope. Fixes bug 10268; bugfix on 0.2.0.1-alpha. Original patch
654 o Minor bugfixes (exit relay):
655 - Stop leaking memory when we successfully resolve a PTR record.
656 Fixes bug 11437; bugfix on 0.2.4.7-alpha.
658 o Minor bugfixes (bridge client):
659 - Stop accepting bridge lines containing hostnames. Doing so would
660 cause clients to perform DNS requests on the hostnames, which was
661 not sensible behavior. Fixes bug 10801; bugfix on 0.2.0.1-alpha.
662 - Avoid a 60-second delay in the bootstrapping process when a Tor
663 client with pluggable transports re-reads its configuration at
664 just the wrong time. Re-fixes bug 11156; bugfix on 0.2.5.3-alpha.
666 o Minor bugfixes (client, logging during bootstrap):
667 - Warn only once if we start logging in an unsafe way. Previously,
668 we complain as many times as we had problems. Fixes bug 9870;
669 bugfix on 0.2.5.1-alpha.
670 - Only report the first fatal bootstrap error on a given OR
671 connection. This stops us from telling the controller bogus error
672 messages like "DONE". Fixes bug 10431; bugfix on 0.2.1.1-alpha.
673 - Be more helpful when trying to run sandboxed on Linux without
674 libseccomp. Instead of saying "Sandbox is not implemented on this
675 platform", we now explain that we need to be built with
676 libseccomp. Fixes bug 11543; bugfix on 0.2.5.1-alpha.
677 - Avoid generating spurious warnings when starting with
678 DisableNetwork enabled. Fixes bug 11200 and bug 10405; bugfix on
681 o Minor bugfixes (closing OR connections):
682 - If write_to_buf() in connection_write_to_buf_impl_() ever fails,
683 check if it's an or_connection_t and correctly call
684 connection_or_close_for_error() rather than
685 connection_mark_for_close() directly. Fixes bug 11304; bugfix on
687 - When closing all connections on setting DisableNetwork to 1, use
688 connection_or_close_normally() rather than closing OR connections
689 out from under the channel layer. Fixes bug 11306; bugfix on
692 o Minor bugfixes (controller):
693 - Avoid sending a garbage value to the controller when a circuit is
694 cannibalized. Fixes bug 11519; bugfix on 0.2.3.11-alpha.
696 o Minor bugfixes (tor-fw-helper):
697 - Allow tor-fw-helper to build again by adding src/ext to its
698 CPPFLAGS. Fixes bug 11296; bugfix on 0.2.5.3-alpha.
700 o Minor bugfixes (bridges):
701 - Avoid potential crashes or bad behavior when launching a
702 server-side managed proxy with ORPort or ExtORPort temporarily
703 disabled. Fixes bug 9650; bugfix on 0.2.3.16-alpha.
705 o Minor bugfixes (platform-specific):
706 - Fix compilation on Solaris, which does not have <endian.h>. Fixes
707 bug 11426; bugfix on 0.2.5.3-alpha.
708 - When dumping a malformed directory object to disk, save it in
709 binary mode on Windows, not text mode. Fixes bug 11342; bugfix on
711 - Don't report failures from make_socket_reuseable() on incoming
712 sockets on OSX: this can happen when incoming connections close
713 early. Fixes bug 10081.
715 o Minor bugfixes (trivial memory leaks):
716 - Fix a small memory leak when signing a directory object. Fixes bug
717 11275; bugfix on 0.2.4.13-alpha.
718 - Free placeholder entries in our circuit table at exit; fixes a
719 harmless memory leak. Fixes bug 11278; bugfix on 0.2.5.1-alpha.
720 - Don't re-initialize a second set of OpenSSL mutexes when starting
721 up. Previously, we'd make one set of mutexes, and then immediately
722 replace them with another. Fixes bug 11726; bugfix on
724 - Resolve some memory leaks found by coverity in the unit tests, on
725 exit in tor-gencert, and on a failure to compute digests for our
726 own keys when generating a v3 networkstatus vote. These leaks
727 should never have affected anyone in practice.
729 o Minor bugfixes (hidden service):
730 - Only retry attempts to connect to a chosen rendezvous point 8
731 times, not 30. Fixes bug 4241; bugfix on 0.1.0.1-rc.
733 o Minor bugfixes (misc code correctness):
734 - Fix various instances of undefined behavior in channeltls.c,
735 tor_memmem(), and eventdns.c that would cause us to construct
736 pointers to memory outside an allocated object. (These invalid
737 pointers were not accessed, but C does not even allow them to
738 exist.) Fixes bug 10363; bugfixes on 0.1.1.1-alpha, 0.1.2.1-alpha,
739 0.2.0.10-alpha, and 0.2.3.6-alpha. Reported by "bobnomnom".
740 - Use the AddressSanitizer and Ubsan sanitizers (in clang-3.4) to
741 fix some miscellaneous errors in our tests and codebase. Fixes bug
742 11232. Bugfixes on versions back as far as 0.2.1.11-alpha.
743 - Always check return values for unlink, munmap, UnmapViewOfFile;
744 check strftime return values more often. In some cases all we can
745 do is report a warning, but this may help prevent deeper bugs from
746 going unnoticed. Closes ticket 8787; bugfixes on many, many tor
748 - Fix numerous warnings from the clang "scan-build" static analyzer.
749 Some of these are programming style issues; some of them are false
750 positives that indicated awkward code; some are undefined behavior
751 cases related to constructing (but not using) invalid pointers;
752 some are assumptions about API behavior; some are (harmlessly)
753 logging sizeof(ptr) bytes from a token when sizeof(*ptr) would be
754 correct; and one or two are genuine bugs that weren't reachable
755 from the rest of the program. Fixes bug 8793; bugfixes on many,
759 - Build the torify.1 manpage again. Previously, we were only trying
760 to build it when also building tor-fw-helper. That's why we didn't
761 notice that we'd broken the ability to build it. Fixes bug 11321;
762 bugfix on 0.2.5.1-alpha.
763 - Fix the layout of the SOCKSPort flags in the manpage. Fixes bug
764 11061; bugfix on 0.2.4.7-alpha.
765 - Correctly document that we search for a system torrc file before
766 looking in ~/.torrc. Fixes documentation side of 9213; bugfix on
768 - Resolve warnings from Doxygen.
770 o Code simplifications and refactoring:
771 - Remove is_internal_IP() function. Resolves ticket 4645.
772 - Remove unused function circuit_dump_by_chan from circuitlist.c.
773 Closes issue 9107; patch from "marek".
774 - Change our use of the ENUM_BF macro to avoid declarations that
777 o Deprecated versions:
778 - Tor 0.2.2.x has reached end-of-life; it has received no patches or
779 attention for some while. Directory authorities no longer accept
780 descriptors from relays running any version of Tor prior to Tor
781 0.2.3.16-alpha. Resolves ticket 11149.
784 - New macros in test.h to simplify writing mock-functions for unit
785 tests. Part of ticket 11507. Patch from Dana Koch.
786 - Complete tests for the status.c module. Resolves ticket 11507.
787 Patch from Dana Koch.
790 - Remove all code for the long unused v1 directory protocol.
791 Resolves ticket 11070.
794 Changes in version 0.2.5.3-alpha - 2014-03-22
795 Tor 0.2.5.3-alpha includes all the fixes from 0.2.4.21. It contains
796 two new anti-DoS features for Tor relays, resolves a bug that kept
797 SOCKS5 support for IPv6 from working, fixes several annoying usability
798 issues for bridge users, and removes more old code for unused
801 The Tor 0.2.5.x release series is now in patch-freeze: no feature
802 patches not already written will be considered for inclusion in 0.2.5.x.
804 o Major features (relay security, DoS-resistance):
805 - When deciding whether we have run out of memory and we need to
806 close circuits, also consider memory allocated in buffers for
807 streams attached to each circuit.
809 This change, which extends an anti-DoS feature introduced in
810 0.2.4.13-alpha and improved in 0.2.4.14-alpha, lets Tor exit relays
811 better resist more memory-based DoS attacks than before. Since the
812 MaxMemInCellQueues option now applies to all queues, it is renamed
813 to MaxMemInQueues. This feature fixes bug 10169.
814 - Avoid hash-flooding denial-of-service attacks by using the secure
815 SipHash-2-4 hash function for our hashtables. Without this
816 feature, an attacker could degrade performance of a targeted
817 client or server by flooding their data structures with a large
818 number of entries to be stored at the same hash table position,
819 thereby slowing down the Tor instance. With this feature, hash
820 table positions are derived from a randomized cryptographic key,
821 and an attacker cannot predict which entries will collide. Closes
823 - Decrease the lower limit of MaxMemInQueues to 256 MBytes (but leave
824 the default at 8GBytes), to better support Raspberry Pi users. Fixes
825 bug 9686; bugfix on 0.2.4.14-alpha.
827 o Minor features (bridges, pluggable transports):
828 - Bridges now write the SHA1 digest of their identity key
829 fingerprint (that is, a hash of a hash of their public key) to
830 notice-level logs, and to a new hashed-fingerprint file. This
831 information will help bridge operators look up their bridge in
832 Globe and similar tools. Resolves ticket 10884.
833 - Improve the message that Tor displays when running as a bridge
834 using pluggable transports without an Extended ORPort listener.
835 Also, log the message in the log file too. Resolves ticket 11043.
837 o Minor features (other):
838 - Add a new option, PredictedPortsRelevanceTime, to control how long
839 after having received a request to connect to a given port Tor
840 will try to keep circuits ready in anticipation of future requests
841 for that port. Patch from "unixninja92"; implements ticket 9176.
842 - Generate a warning if any ports are listed in the SocksPolicy,
843 DirPolicy, AuthDirReject, AuthDirInvalid, AuthDirBadDir, or
844 AuthDirBadExit options. (These options only support address
845 ranges.) Fixes part of ticket 11108.
846 - Update geoip and geoip6 to the February 7 2014 Maxmind GeoLite2
849 o Minor bugfixes (new since 0.2.5.2-alpha, also in 0.2.4.21):
850 - Build without warnings under clang 3.4. (We have some macros that
851 define static functions only some of which will get used later in
852 the module. Starting with clang 3.4, these give a warning unless the
853 unused attribute is set on them.) Resolves ticket 10904.
854 - Fix build warnings about missing "a2x" comment when building the
855 manpages from scratch on OpenBSD; OpenBSD calls it "a2x.py".
856 Fixes bug 10929; bugfix on 0.2.2.9-alpha. Patch from Dana Koch.
858 o Minor bugfixes (client):
859 - Improve the log message when we can't connect to a hidden service
860 because all of the hidden service directory nodes hosting its
861 descriptor are excluded. Improves on our fix for bug 10722, which
862 was a bugfix on 0.2.0.10-alpha.
863 - Raise a control port warning when we fail to connect to all of
864 our bridges. Previously, we didn't inform the controller, and
865 the bootstrap process would stall. Fixes bug 11069; bugfix on
867 - Exit immediately when a process-owning controller exits.
868 Previously, tor relays would wait for a little while after their
869 controller exited, as if they had gotten an INT signal -- but this
870 was problematic, since there was no feedback for the user. To do a
871 clean shutdown, controllers should send an INT signal and give Tor
872 a chance to clean up. Fixes bug 10449; bugfix on 0.2.2.28-beta.
873 - Stop attempting to connect to bridges before our pluggable
874 transports are configured (harmless but resulted in some erroneous
875 log messages). Fixes bug 11156; bugfix on 0.2.3.2-alpha.
876 - Fix connections to IPv6 addresses over SOCKS5. Previously, we were
877 generating incorrect SOCKS5 responses, and confusing client
878 applications. Fixes bug 10987; bugfix on 0.2.4.7-alpha.
880 o Minor bugfixes (relays and bridges):
881 - Avoid crashing on a malformed resolv.conf file when running a
882 relay using Libevent 1. Fixes bug 8788; bugfix on 0.1.1.23.
883 - Non-exit relays no longer launch mock DNS requests to check for
884 DNS hijacking. This has been unnecessary since 0.2.1.7-alpha, when
885 non-exit relays stopped servicing DNS requests. Fixes bug 965;
886 bugfix on 0.2.1.7-alpha. Patch from Matt Pagan.
887 - Bridges now report complete directory request statistics. Related
888 to bug 5824; bugfix on 0.2.2.1-alpha.
889 - Bridges now never collect statistics that were designed for
890 relays. Fixes bug 5824; bugfix on 0.2.3.8-alpha.
891 - Stop giving annoying warning messages when we decide not to launch
892 a pluggable transport proxy that we don't need (because there are
893 no bridges configured to use it). Resolves ticket 5018; bugfix
895 - Give the correct URL in the warning message when trying to run a
896 relay on an ancient version of Windows. Fixes bug 9393.
898 o Minor bugfixes (backtrace support):
899 - Support automatic backtraces on more platforms by using the
900 "-fasynchronous-unwind-tables" compiler option. This option is
901 needed for platforms like 32-bit Intel where "-fomit-frame-pointer"
902 is on by default and table generation is not. This doesn't yet
903 add Windows support; only Linux, OSX, and some BSDs are affected.
904 Reported by 'cypherpunks'; fixes bug 11047; bugfix on 0.2.5.2-alpha.
905 - Avoid strange behavior if two threads hit failed assertions at the
906 same time and both try to log backtraces at once. (Previously, if
907 this had happened, both threads would have stored their intermediate
908 results in the same buffer, and generated junk outputs.) Reported by
909 "cypherpunks". Fixes bug 11048; bugfix on 0.2.5.2-alpha.
910 - Fix a compiler warning in format_number_sigsafe(). Bugfix on
911 0.2.5.2-alpha; patch from Nick Hopper.
913 o Minor bugfixes (unit tests):
914 - Fix a small bug in the unit tests that might have made the tests
915 call 'chmod' with an uninitialized bitmask. Fixes bug 10928;
916 bugfix on 0.2.5.1-alpha. Patch from Dana Koch.
919 - Remove all remaining code related to version-0 hidden service
920 descriptors: they have not been in use since 0.2.2.1-alpha. Fixes
921 the rest of bug 10841.
924 - Document in the manpage that "KBytes" may also be written as
925 "kilobytes" or "KB", that "Kbits" may also be written as
926 "kilobits", and so forth. Closes ticket 9222.
927 - Document that the ClientOnly config option overrides ORPort.
928 Our old explanation made ClientOnly sound as though it did
929 nothing at all. Resolves bug 9059.
930 - Explain that SocksPolicy, DirPolicy, and similar options don't
931 take port arguments. Fixes the other part of ticket 11108.
932 - Fix a comment about the rend_server_descriptor_t.protocols field
933 to more accurately describe its range. Also, make that field
934 unsigned, to more accurately reflect its usage. Fixes bug 9099;
935 bugfix on 0.2.1.5-alpha.
936 - Fix the manpage's description of HiddenServiceAuthorizeClient:
937 the maximum client name length is 16, not 19. Fixes bug 11118;
938 bugfix on 0.2.1.6-alpha.
940 o Code simplifications and refactoring:
941 - Get rid of router->address, since in all cases it was just the
942 string representation of router->addr. Resolves ticket 5528.
944 o Test infrastructure:
945 - Update to the latest version of tinytest.
946 - Improve the tinytest implementation of string operation tests so
947 that comparisons with NULL strings no longer crash the tests; they
948 now just fail, normally. Fixes bug 9004; bugfix on 0.2.2.4-alpha.
951 Changes in version 0.2.4.21 - 2014-02-28
952 Tor 0.2.4.21 further improves security against potential adversaries who
953 find breaking 1024-bit crypto doable, and backports several stability
954 and robustness patches from the 0.2.5 branch.
956 o Major features (client security):
957 - When we choose a path for a 3-hop circuit, make sure it contains
958 at least one relay that supports the NTor circuit extension
959 handshake. Otherwise, there is a chance that we're building
960 a circuit that's worth attacking by an adversary who finds
961 breaking 1024-bit crypto doable, and that chance changes the game
962 theory. Implements ticket 9777.
965 - Do not treat streams that fail with reason
966 END_STREAM_REASON_INTERNAL as indicating a definite circuit failure,
967 since it could also indicate an ENETUNREACH connection error. Fixes
968 part of bug 10777; bugfix on 0.2.4.8-alpha.
970 o Code simplification and refactoring:
971 - Remove data structures which were introduced to implement the
972 CellStatistics option: they are now redundant with the new timestamp
973 field in the regular packed_cell_t data structure, which we did
974 in 0.2.4.18-rc in order to resolve bug 9093. Resolves ticket 10870.
977 - Always clear OpenSSL bignums before freeing them -- even bignums
978 that don't contain secrets. Resolves ticket 10793. Patch by
980 - Build without warnings under clang 3.4. (We have some macros that
981 define static functions only some of which will get used later in
982 the module. Starting with clang 3.4, these give a warning unless the
983 unused attribute is set on them.) Resolves ticket 10904.
984 - Update geoip and geoip6 files to the February 7 2014 Maxmind
985 GeoLite2 Country database.
988 - Set the listen() backlog limit to the largest actually supported
989 on the system, not to the value in a header file. Fixes bug 9716;
990 bugfix on every released Tor.
991 - Treat ENETUNREACH, EACCES, and EPERM connection failures at an
992 exit node as a NOROUTE error, not an INTERNAL error, since they
993 can apparently happen when trying to connect to the wrong sort
994 of netblocks. Fixes part of bug 10777; bugfix on 0.1.0.1-rc.
995 - Fix build warnings about missing "a2x" comment when building the
996 manpages from scratch on OpenBSD; OpenBSD calls it "a2x.py".
997 Fixes bug 10929; bugfix on 0.2.2.9-alpha. Patch from Dana Koch.
998 - Avoid a segfault on SIGUSR1, where we had freed a connection but did
999 not entirely remove it from the connection lists. Fixes bug 9602;
1000 bugfix on 0.2.4.4-alpha.
1001 - Fix a segmentation fault in our benchmark code when running with
1002 Fedora's OpenSSL package, or any other OpenSSL that provides
1003 ECDH but not P224. Fixes bug 10835; bugfix on 0.2.4.8-alpha.
1004 - Turn "circuit handshake stats since last time" log messages into a
1005 heartbeat message. Fixes bug 10485; bugfix on 0.2.4.17-rc.
1007 o Documentation fixes:
1008 - Document that all but one DirPort entry must have the NoAdvertise
1009 flag set. Fixes bug 10470; bugfix on 0.2.3.3-alpha / 0.2.3.16-alpha.
1012 Changes in version 0.2.5.2-alpha - 2014-02-13
1013 Tor 0.2.5.2-alpha includes all the fixes from 0.2.4.18-rc and 0.2.4.20,
1014 like the "poor random number generation" fix and the "building too many
1015 circuits" fix. It also further improves security against potential
1016 adversaries who find breaking 1024-bit crypto doable, and launches
1017 pluggable transports on demand (which gets us closer to integrating
1018 pluggable transport support by default -- not to be confused with Tor
1019 bundles enabling pluggable transports and bridges by default).
1021 o Major features (client security):
1022 - When we choose a path for a 3-hop circuit, make sure it contains
1023 at least one relay that supports the NTor circuit extension
1024 handshake. Otherwise, there is a chance that we're building
1025 a circuit that's worth attacking by an adversary who finds
1026 breaking 1024-bit crypto doable, and that chance changes the game
1027 theory. Implements ticket 9777.
1028 - Clients now look at the "usecreatefast" consensus parameter to
1029 decide whether to use CREATE_FAST or CREATE cells for the first hop
1030 of their circuit. This approach can improve security on connections
1031 where Tor's circuit handshake is stronger than the available TLS
1032 connection security levels, but the tradeoff is more computational
1033 load on guard relays. Implements proposal 221. Resolves ticket 9386.
1035 o Major features (bridges):
1036 - Don't launch pluggable transport proxies if we don't have any
1037 bridges configured that would use them. Now we can list many
1038 pluggable transports, and Tor will dynamically start one when it
1039 hears a bridge address that needs it. Resolves ticket 5018.
1040 - The bridge directory authority now assigns status flags (Stable,
1041 Guard, etc) to bridges based on thresholds calculated over all
1042 Running bridges. Now bridgedb can finally make use of its features
1043 to e.g. include at least one Stable bridge in its answers. Fixes
1046 o Major features (other):
1047 - Extend ORCONN controller event to include an "ID" parameter,
1048 and add four new controller event types CONN_BW, CIRC_BW,
1049 CELL_STATS, and TB_EMPTY that show connection and circuit usage.
1050 The new events are emitted in private Tor networks only, with the
1051 goal of being able to better track performance and load during
1052 full-network simulations. Implements proposal 218 and ticket 7359.
1053 - On some platforms (currently: recent OSX versions, glibc-based
1054 platforms that support the ELF format, and a few other
1055 Unix-like operating systems), Tor can now dump stack traces
1056 when a crash occurs or an assertion fails. By default, traces
1057 are dumped to stderr (if possible) and to any logs that are
1058 reporting errors. Implements ticket 9299.
1061 - Avoid a segfault on SIGUSR1, where we had freed a connection but did
1062 not entirely remove it from the connection lists. Fixes bug 9602;
1063 bugfix on 0.2.4.4-alpha.
1064 - Do not treat streams that fail with reason
1065 END_STREAM_REASON_INTERNAL as indicating a definite circuit failure,
1066 since it could also indicate an ENETUNREACH connection error. Fixes
1067 part of bug 10777; bugfix on 0.2.4.8-alpha.
1069 o Major bugfixes (new since 0.2.5.1-alpha, also in 0.2.4.20):
1070 - Do not allow OpenSSL engines to replace the PRNG, even when
1071 HardwareAccel is set. The only default builtin PRNG engine uses
1072 the Intel RDRAND instruction to replace the entire PRNG, and
1073 ignores all attempts to seed it with more entropy. That's
1074 cryptographically stupid: the right response to a new alleged
1075 entropy source is never to discard all previously used entropy
1076 sources. Fixes bug 10402; works around behavior introduced in
1077 OpenSSL 1.0.0. Diagnosis and investigation thanks to "coderman"
1079 - Fix assertion failure when AutomapHostsOnResolve yields an IPv6
1080 address. Fixes bug 10465; bugfix on 0.2.4.7-alpha.
1081 - Avoid launching spurious extra circuits when a stream is pending.
1082 This fixes a bug where any circuit that _wasn't_ unusable for new
1083 streams would be treated as if it were, causing extra circuits to
1084 be launched. Fixes bug 10456; bugfix on 0.2.4.12-alpha.
1086 o Major bugfixes (new since 0.2.5.1-alpha, also in 0.2.4.18-rc):
1087 - No longer stop reading or writing on cpuworker connections when
1088 our rate limiting buckets go empty. Now we should handle circuit
1089 handshake requests more promptly. Resolves bug 9731.
1090 - Stop trying to bootstrap all our directory information from
1091 only our first guard. Discovered while fixing bug 9946; bugfix
1094 o Minor features (bridges, pluggable transports):
1095 - Add threshold cutoffs to the networkstatus document created by
1096 the Bridge Authority. Fixes bug 1117.
1097 - On Windows, spawn background processes using the CREATE_NO_WINDOW
1098 flag. Now Tor Browser Bundle 3.5 with pluggable transports enabled
1099 doesn't pop up a blank console window. (In Tor Browser Bundle 2.x,
1100 Vidalia set this option for us.) Implements ticket 10297.
1102 o Minor features (security):
1103 - Always clear OpenSSL bignums before freeing them -- even bignums
1104 that don't contain secrets. Resolves ticket 10793. Patch by
1107 o Minor features (config options and command line):
1108 - Add an --allow-missing-torrc commandline option that tells Tor to
1109 run even if the configuration file specified by -f is not available.
1110 Implements ticket 10060.
1111 - Add support for the TPROXY transparent proxying facility on Linux.
1112 See documentation for the new TransProxyType option for more
1113 details. Implementation by "thomo". Closes ticket 10582.
1115 o Minor features (controller):
1116 - Add a new "HS_DESC" controller event that reports activities
1117 related to hidden service descriptors. Resolves ticket 8510.
1118 - New "DROPGUARDS" controller command to forget all current entry
1119 guards. Not recommended for ordinary use, since replacing guards
1120 too frequently makes several attacks easier. Resolves ticket 9934;
1123 o Minor features (build):
1124 - Assume that a user using ./configure --host wants to cross-compile,
1125 and give an error if we cannot find a properly named
1126 tool-chain. Add a --disable-tool-name-check option to proceed
1127 nevertheless. Addresses ticket 9869. Patch by Benedikt Gollatz.
1128 - If we run ./configure and the compiler recognizes -fstack-protector
1129 but the linker rejects it, warn the user about a potentially missing
1130 libssp package. Addresses ticket 9948. Patch from Benedikt Gollatz.
1132 o Minor features (testing):
1133 - If Python is installed, "make check" now runs extra tests beyond
1134 the unit test scripts.
1135 - When bootstrapping a test network, sometimes very few relays get
1136 the Guard flag. Now a new option "TestingDirAuthVoteGuard" can
1137 specify a set of relays which should be voted Guard regardless of
1138 their uptime or bandwidth. Addresses ticket 9206.
1140 o Minor features (log messages):
1141 - When ServerTransportPlugin is set on a bridge, Tor can write more
1142 useful statistics about bridge use in its extrainfo descriptors,
1143 but only if the Extended ORPort ("ExtORPort") is set too. Add a
1144 log message to inform the user in this case. Resolves ticket 9651.
1145 - When receiving a new controller connection, log the origin address.
1146 Resolves ticket 9698; patch from "sigpipe".
1147 - When logging OpenSSL engine status at startup, log the status of
1148 more engines. Fixes ticket 10043; patch from Joshua Datko.
1149 - Turn "circuit handshake stats since last time" log messages into a
1150 heartbeat message. Fixes bug 10485; bugfix on 0.2.4.17-rc.
1152 o Minor features (new since 0.2.5.1-alpha, also in 0.2.4.18-rc):
1153 - Improve the circuit queue out-of-memory handler. Previously, when
1154 we ran low on memory, we'd close whichever circuits had the most
1155 queued cells. Now, we close those that have the *oldest* queued
1156 cells, on the theory that those are most responsible for us
1157 running low on memory. Based on analysis from a forthcoming paper
1158 by Jansen, Tschorsch, Johnson, and Scheuermann. Fixes bug 9093.
1159 - Generate bootstrapping status update events correctly when fetching
1160 microdescriptors. Fixes bug 9927.
1161 - Update to the October 2 2013 Maxmind GeoLite Country database.
1163 o Minor bugfixes (clients):
1164 - When closing a channel that has already been open, do not close
1165 pending circuits that were waiting to connect to the same relay.
1166 Fixes bug 9880; bugfix on 0.2.5.1-alpha. Thanks to skruffy for
1169 o Minor bugfixes (relays):
1170 - Treat ENETUNREACH, EACCES, and EPERM connection failures at an
1171 exit node as a NOROUTE error, not an INTERNAL error, since they
1172 can apparently happen when trying to connect to the wrong sort
1173 of netblocks. Fixes part of bug 10777; bugfix on 0.1.0.1-rc.
1175 o Minor bugfixes (bridges):
1176 - Fix a bug where the first connection works to a bridge that uses a
1177 pluggable transport with client-side parameters, but we don't send
1178 the client-side parameters on subsequent connections. (We don't
1179 use any pluggable transports with client-side parameters yet,
1180 but ScrambleSuit will soon become the first one.) Fixes bug 9162;
1181 bugfix on 0.2.0.3-alpha. Based on a patch from "rl1987".
1183 o Minor bugfixes (node selection):
1184 - If ExcludeNodes is set, consider non-excluded hidden service
1185 directory servers before excluded ones. Do not consider excluded
1186 hidden service directory servers at all if StrictNodes is
1187 set. (Previously, we would sometimes decide to connect to those
1188 servers, and then realize before we initiated a connection that
1189 we had excluded them.) Fixes bug 10722; bugfix on 0.2.0.10-alpha.
1191 - If we set the ExitNodes option but it doesn't include any nodes
1192 that have the Exit flag, we would choose not to bootstrap. Now we
1193 bootstrap so long as ExitNodes includes nodes which can exit to
1194 some port. Fixes bug 10543; bugfix on 0.2.4.10-alpha.
1196 o Minor bugfixes (controller and command-line):
1197 - If changing a config option via "setconf" fails in a recoverable
1198 way, we used to nonetheless write our new control ports to the
1199 file described by the "ControlPortWriteToFile" option. Now we only
1200 write out that file if we successfully switch to the new config
1201 option. Fixes bug 5605; bugfix on 0.2.2.26-beta. Patch from "Ryman".
1202 - When a command-line option such as --version or --help that
1203 ordinarily implies --hush appears on the command line along with
1204 --quiet, then actually obey --quiet. Previously, we obeyed --quiet
1205 only if it appeared later on the command line. Fixes bug 9578;
1206 bugfix on 0.2.5.1-alpha.
1208 o Minor bugfixes (code correctness):
1209 - Previously we used two temporary files when writing descriptors to
1210 disk; now we only use one. Fixes bug 1376.
1211 - Remove an erroneous (but impossible and thus harmless) pointer
1212 comparison that would have allowed compilers to skip a bounds
1213 check in channeltls.c. Fixes bugs 10313 and 9980; bugfix on
1214 0.2.0.10-alpha. Noticed by Jared L Wong and David Fifield.
1215 - Fix an always-true assertion in pluggable transports code so it
1216 actually checks what it was trying to check. Fixes bug 10046;
1217 bugfix on 0.2.3.9-alpha. Found by "dcb".
1219 o Minor bugfixes (protocol correctness):
1220 - When receiving a VERSIONS cell with an odd number of bytes, close
1221 the connection immediately since the cell is malformed. Fixes bug
1222 10365; bugfix on 0.2.0.10-alpha. Spotted by "bobnomnom"; fix by
1225 o Minor bugfixes (build):
1226 - Restore the ability to compile Tor with V2_HANDSHAKE_SERVER
1227 turned off (that is, without support for v2 link handshakes). Fixes
1228 bug 4677; bugfix on 0.2.3.2-alpha. Patch from "piet".
1229 - Fix compilation warnings and startup issues when running with
1230 "Sandbox 1" and libseccomp-2.1.0. Fixes bug 10563; bugfix on
1232 - Fix compilation on Solaris 9, which didn't like us having an
1233 identifier named "sun". Fixes bug 10565; bugfix in 0.2.5.1-alpha.
1235 o Minor bugfixes (testing):
1236 - Fix a segmentation fault in our benchmark code when running with
1237 Fedora's OpenSSL package, or any other OpenSSL that provides
1238 ECDH but not P224. Fixes bug 10835; bugfix on 0.2.4.8-alpha.
1240 o Minor bugfixes (log messages):
1241 - Fix a bug where clients using bridges would report themselves
1242 as 50% bootstrapped even without a live consensus document.
1243 Fixes bug 9922; bugfix on 0.2.1.1-alpha.
1244 - Suppress a warning where, if there's only one directory authority
1245 in the network, we would complain that votes and signatures cannot
1246 be uploaded to other directory authorities. Fixes bug 10842;
1247 bugfix on 0.2.2.26-beta.
1248 - Report bootstrapping progress correctly when we're downloading
1249 microdescriptors. We had updated our "do we have enough microdescs
1250 to begin building circuits?" logic most recently in 0.2.4.10-alpha
1251 (see bug 5956), but we left the bootstrap status event logic at
1252 "how far through getting 1/4 of them are we?" Fixes bug 9958;
1253 bugfix on 0.2.2.36, which is where they diverged (see bug 5343).
1255 o Minor bugfixes (new since 0.2.5.1-alpha, also in 0.2.4.20):
1256 - Avoid a crash bug when starting with a corrupted microdescriptor
1257 cache file. Fixes bug 10406; bugfix on 0.2.2.6-alpha.
1258 - If we fail to dump a previously cached microdescriptor to disk, avoid
1259 freeing duplicate data later on. Fixes bug 10423; bugfix on
1260 0.2.4.13-alpha. Spotted by "bobnomnom".
1262 o Minor bugfixes on 0.2.4.x (new since 0.2.5.1-alpha, also in 0.2.4.18-rc):
1263 - Correctly log long IPv6 exit policies, instead of truncating them
1264 or reporting an error. Fixes bug 9596; bugfix on 0.2.4.7-alpha.
1265 - Our default TLS ecdhe groups were backwards: we meant to be using
1266 P224 for relays (for performance win) and P256 for bridges (since
1267 it is more common in the wild). Instead we had it backwards. After
1268 reconsideration, we decided that the default should be P256 on all
1269 hosts, since its security is probably better, and since P224 is
1270 reportedly used quite little in the wild. Found by "skruffy" on
1271 IRC. Fix for bug 9780; bugfix on 0.2.4.8-alpha.
1272 - Free directory authority certificate download statuses on exit
1273 rather than leaking them. Fixes bug 9644; bugfix on 0.2.4.13-alpha.
1275 o Minor bugfixes on 0.2.3.x (new since 0.2.5.1-alpha, also in 0.2.4.18-rc):
1276 - If the guard we choose first doesn't answer, we would try the
1277 second guard, but once we connected to the second guard we would
1278 abandon it and retry the first one, slowing down bootstrapping.
1279 The fix is to treat all our initially chosen guards as acceptable
1280 to use. Fixes bug 9946; bugfix on 0.1.1.11-alpha.
1281 - Fix an assertion failure that would occur when disabling the
1282 ORPort setting on a running Tor process while accounting was
1283 enabled. Fixes bug 6979; bugfix on 0.2.2.18-alpha.
1284 - When examining the list of network interfaces to find our address,
1285 do not consider non-running or disabled network interfaces. Fixes
1286 bug 9904; bugfix on 0.2.3.11-alpha. Patch from "hantwister".
1287 - Avoid an off-by-one error when checking buffer boundaries when
1288 formatting the exit status of a pluggable transport helper.
1289 This is probably not an exploitable bug, but better safe than
1290 sorry. Fixes bug 9928; bugfix on 0.2.3.18-rc. Bug found by
1293 o Removed code and features:
1294 - Clients now reject any directory authority certificates lacking
1295 a dir-key-crosscert element. These have been included since
1296 0.2.1.9-alpha, so there's no real reason for them to be optional
1297 any longer. Completes proposal 157. Resolves ticket 10162.
1298 - Remove all code that existed to support the v2 directory system,
1299 since there are no longer any v2 directory authorities. Resolves
1301 - Remove the HSAuthoritativeDir and AlternateHSAuthority torrc
1302 options, which were used for designating authorities as "Hidden
1303 service authorities". There has been no use of hidden service
1304 authorities since 0.2.2.1-alpha, when we stopped uploading or
1305 downloading v0 hidden service descriptors. Fixes bug 10881; also
1306 part of a fix for bug 10841.
1308 o Code simplification and refactoring:
1309 - Remove some old fallback code designed to keep Tor clients working
1310 in a network with only two working relays. Elsewhere in the code we
1311 have long since stopped supporting such networks, so there wasn't
1312 much point in keeping it around. Addresses ticket 9926.
1313 - Reject 0-length EXTEND2 cells more explicitly. Fixes bug 10536;
1314 bugfix on 0.2.4.8-alpha. Reported by "cypherpunks".
1315 - Remove data structures which were introduced to implement the
1316 CellStatistics option: they are now redundant with the addition
1317 of a timestamp to the regular packed_cell_t data structure, which
1318 we did in 0.2.4.18-rc in order to resolve ticket 9093. Implements
1321 o Documentation (man page) fixes:
1322 - Update manpage to describe some of the files you can expect to
1323 find in Tor's DataDirectory. Addresses ticket 9839.
1324 - Document that all but one DirPort entry must have the NoAdvertise
1325 flag set. Fixes bug 10470; bugfix on 0.2.3.3-alpha / 0.2.3.16-alpha.
1327 o Documentation fixes (new since 0.2.5.1-alpha, also in 0.2.4.18-rc):
1328 - Clarify the usage and risks of setting the ContactInfo torrc line
1329 for your relay or bridge. Resolves ticket 9854.
1330 - Add anchors to the manpage so we can link to the html version of
1331 the documentation for specific options. Resolves ticket 9866.
1332 - Replace remaining references to DirServer in man page and
1333 log entries. Resolves ticket 10124.
1336 - Make the "tor-gencert" tool used by directory authority operators
1337 create 2048-bit signing keys by default (rather than 1024-bit, since
1338 1024-bit is uncomfortably small these days). Addresses ticket 10324.
1341 Changes in version 0.2.4.20 - 2013-12-22
1342 Tor 0.2.4.20 fixes potentially poor random number generation for users
1343 who 1) use OpenSSL 1.0.0 or later, 2) set "HardwareAccel 1" in their
1344 torrc file, 3) have "Sandy Bridge" or "Ivy Bridge" Intel processors,
1345 and 4) have no state file in their DataDirectory (as would happen on
1346 first start). Users who generated relay or hidden service identity
1347 keys in such a situation should discard them and generate new ones.
1349 This release also fixes a logic error that caused Tor clients to build
1350 many more preemptive circuits than they actually need.
1353 - Do not allow OpenSSL engines to replace the PRNG, even when
1354 HardwareAccel is set. The only default builtin PRNG engine uses
1355 the Intel RDRAND instruction to replace the entire PRNG, and
1356 ignores all attempts to seed it with more entropy. That's
1357 cryptographically stupid: the right response to a new alleged
1358 entropy source is never to discard all previously used entropy
1359 sources. Fixes bug 10402; works around behavior introduced in
1360 OpenSSL 1.0.0. Diagnosis and investigation thanks to "coderman"
1362 - Fix assertion failure when AutomapHostsOnResolve yields an IPv6
1363 address. Fixes bug 10465; bugfix on 0.2.4.7-alpha.
1364 - Avoid launching spurious extra circuits when a stream is pending.
1365 This fixes a bug where any circuit that _wasn't_ unusable for new
1366 streams would be treated as if it were, causing extra circuits to
1367 be launched. Fixes bug 10456; bugfix on 0.2.4.12-alpha.
1370 - Avoid a crash bug when starting with a corrupted microdescriptor
1371 cache file. Fixes bug 10406; bugfix on 0.2.2.6-alpha.
1372 - If we fail to dump a previously cached microdescriptor to disk, avoid
1373 freeing duplicate data later on. Fixes bug 10423; bugfix on
1374 0.2.4.13-alpha. Spotted by "bobnomnom".
1377 Changes in version 0.2.4.19 - 2013-12-11
1378 The Tor 0.2.4 release series is dedicated to the memory of Aaron Swartz
1379 (1986-2013). Aaron worked on diverse projects including helping to guide
1380 Creative Commons, playing a key role in stopping SOPA/PIPA, bringing
1381 transparency to the U.S government's PACER documents, and contributing
1382 design and development for Tor and Tor2Web. Aaron was one of the latest
1383 martyrs in our collective fight for civil liberties and human rights,
1384 and his death is all the more painful because he was one of us.
1386 Tor 0.2.4.19, the first stable release in the 0.2.4 branch, features
1387 a new circuit handshake and link encryption that use ECC to provide
1388 better security and efficiency; makes relays better manage circuit
1389 creation requests; uses "directory guards" to reduce client enumeration
1390 risks; makes bridges collect and report statistics about the pluggable
1391 transports they support; cleans up and improves our geoip database;
1392 gets much closer to IPv6 support for clients, bridges, and relays; makes
1393 directory authorities use measured bandwidths rather than advertised
1394 ones when computing flags and thresholds; disables client-side DNS
1395 caching to reduce tracking risks; and fixes a big bug in bridge
1396 reachability testing. This release introduces two new design
1397 abstractions in the code: a new "channel" abstraction between circuits
1398 and or_connections to allow for implementing alternate relay-to-relay
1399 transports, and a new "circuitmux" abstraction storing the queue of
1400 circuits for a channel. The release also includes many stability,
1401 security, and privacy fixes.
1404 Changes in version 0.2.4.18-rc - 2013-11-16
1405 Tor 0.2.4.18-rc is the fourth release candidate for the Tor 0.2.4.x
1406 series. It takes a variety of fixes from the 0.2.5.x branch to improve
1407 stability, performance, and better handling of edge cases.
1410 - Re-enable TLS 1.1 and 1.2 when built with OpenSSL 1.0.1e or later.
1411 Resolves ticket 6055. (OpenSSL before 1.0.1 didn't have TLS 1.1 or
1412 1.2, and OpenSSL from 1.0.1 through 1.0.1d had bugs that prevented
1413 renegotiation from working with TLS 1.1 or 1.2, so we had disabled
1414 them to solve bug 6033.)
1417 - No longer stop reading or writing on cpuworker connections when
1418 our rate limiting buckets go empty. Now we should handle circuit
1419 handshake requests more promptly. Resolves bug 9731.
1420 - If we are unable to save a microdescriptor to the journal, do not
1421 drop it from memory and then reattempt downloading it. Fixes bug
1422 9645; bugfix on 0.2.2.6-alpha.
1423 - Stop trying to bootstrap all our directory information from
1424 only our first guard. Discovered while fixing bug 9946; bugfix
1426 - The new channel code sometimes lost track of in-progress circuits,
1427 causing long-running clients to stop building new circuits. The
1428 fix is to always call circuit_n_chan_done(chan, 0) from
1429 channel_closed(). Fixes bug 9776; bugfix on 0.2.4.17-rc.
1431 o Minor bugfixes (on 0.2.4.x):
1432 - Correctly log long IPv6 exit policies, instead of truncating them
1433 or reporting an error. Fixes bug 9596; bugfix on 0.2.4.7-alpha.
1434 - Our default TLS ecdhe groups were backwards: we meant to be using
1435 P224 for relays (for performance win) and P256 for bridges (since
1436 it is more common in the wild). Instead we had it backwards. After
1437 reconsideration, we decided that the default should be P256 on all
1438 hosts, since its security is probably better, and since P224 is
1439 reportedly used quite little in the wild. Found by "skruffy" on
1440 IRC. Fix for bug 9780; bugfix on 0.2.4.8-alpha.
1441 - Free directory authority certificate download statuses on exit
1442 rather than leaking them. Fixes bug 9644; bugfix on 0.2.4.13-alpha.
1444 o Minor bugfixes (on 0.2.3.x and earlier):
1445 - If the guard we choose first doesn't answer, we would try the
1446 second guard, but once we connected to the second guard we would
1447 abandon it and retry the first one, slowing down bootstrapping.
1448 The fix is to treat all our initially chosen guards as acceptable
1449 to use. Fixes bug 9946; bugfix on 0.1.1.11-alpha.
1450 - Fix an assertion failure that would occur when disabling the
1451 ORPort setting on a running Tor process while accounting was
1452 enabled. Fixes bug 6979; bugfix on 0.2.2.18-alpha.
1453 - When examining the list of network interfaces to find our address,
1454 do not consider non-running or disabled network interfaces. Fixes
1455 bug 9904; bugfix on 0.2.3.11-alpha. Patch from "hantwister".
1456 - Avoid an off-by-one error when checking buffer boundaries when
1457 formatting the exit status of a pluggable transport helper.
1458 This is probably not an exploitable bug, but better safe than
1459 sorry. Fixes bug 9928; bugfix on 0.2.3.18-rc. Bug found by
1462 o Minor features (protecting client timestamps):
1463 - Clients no longer send timestamps in their NETINFO cells. These were
1464 not used for anything, and they provided one small way for clients
1465 to be distinguished from each other as they moved from network to
1466 network or behind NAT. Implements part of proposal 222.
1467 - Clients now round timestamps in INTRODUCE cells down to the nearest
1468 10 minutes. If a new Support022HiddenServices option is set to 0, or
1469 if it's set to "auto" and the feature is disabled in the consensus,
1470 the timestamp is sent as 0 instead. Implements part of proposal 222.
1471 - Stop sending timestamps in AUTHENTICATE cells. This is not such
1472 a big deal from a security point of view, but it achieves no actual
1473 good purpose, and isn't needed. Implements part of proposal 222.
1474 - Reduce down accuracy of timestamps in hidden service descriptors.
1475 Implements part of proposal 222.
1477 o Minor features (other):
1478 - Improve the circuit queue out-of-memory handler. Previously, when
1479 we ran low on memory, we'd close whichever circuits had the most
1480 queued cells. Now, we close those that have the *oldest* queued
1481 cells, on the theory that those are most responsible for us
1482 running low on memory. Based on analysis from a forthcoming paper
1483 by Jansen, Tschorsch, Johnson, and Scheuermann. Fixes bug 9093.
1484 - Generate bootstrapping status update events correctly when fetching
1485 microdescriptors. Fixes bug 9927.
1486 - Update to the October 2 2013 Maxmind GeoLite Country database.
1488 o Documentation fixes:
1489 - Clarify the usage and risks of setting the ContactInfo torrc line
1490 for your relay or bridge. Resolves ticket 9854.
1491 - Add anchors to the manpage so we can link to the html version of
1492 the documentation for specific options. Resolves ticket 9866.
1493 - Replace remaining references to DirServer in man page and
1494 log entries. Resolves ticket 10124.
1497 Changes in version 0.2.5.1-alpha - 2013-10-02
1498 Tor 0.2.5.1-alpha introduces experimental support for syscall sandboxing
1499 on Linux, allows bridges that offer pluggable transports to report usage
1500 statistics, fixes many issues to make testing easier, and provides
1501 a pile of minor features and bugfixes that have been waiting for a
1502 release of the new branch.
1504 This is the first alpha release in a new series, so expect there to
1505 be bugs. Users who would rather test out a more stable branch should
1506 stay with 0.2.4.x for now.
1508 o Major features (security):
1509 - Use the seccomp2 syscall filtering facility on Linux to limit
1510 which system calls Tor can invoke. This is an experimental,
1511 Linux-only feature to provide defense-in-depth against unknown
1512 attacks. To try turning it on, set "Sandbox 1" in your torrc
1513 file. Please be ready to report bugs. We hope to add support
1514 for better sandboxing in the future, including more fine-grained
1515 filters, better division of responsibility, and support for more
1516 platforms. This work has been done by Cristian-Matei Toader for
1517 Google Summer of Code.
1518 - Re-enable TLS 1.1 and 1.2 when built with OpenSSL 1.0.1e or later.
1519 Resolves ticket 6055. (OpenSSL before 1.0.1 didn't have TLS 1.1 or
1520 1.2, and OpenSSL from 1.0.1 through 1.0.1d had bugs that prevented
1521 renegotiation from working with TLS 1.1 or 1.2, so we had disabled
1522 them to solve bug 6033.)
1524 o Major features (other):
1525 - Add support for passing arguments to managed pluggable transport
1526 proxies. Implements ticket 3594.
1527 - Bridges now track GeoIP information and the number of their users
1528 even when pluggable transports are in use, and report usage
1529 statistics in their extra-info descriptors. Resolves tickets 4773
1531 - Make testing Tor networks bootstrap better: lower directory fetch
1532 retry schedules and maximum interval without directory requests,
1533 and raise maximum download tries. Implements ticket 6752.
1534 - Add make target 'test-network' to run tests on a Chutney network.
1535 Implements ticket 8530.
1536 - The ntor handshake is now on-by-default, no matter what the
1537 directory authorities recommend. Implements ticket 8561.
1540 - Instead of writing destroy cells directly to outgoing connection
1541 buffers, queue them and intersperse them with other outgoing cells.
1542 This can prevent a set of resource starvation conditions where too
1543 many pending destroy cells prevent data cells from actually getting
1544 delivered. Reported by "oftc_must_be_destroyed". Fixes bug 7912;
1545 bugfix on 0.2.0.1-alpha.
1546 - If we are unable to save a microdescriptor to the journal, do not
1547 drop it from memory and then reattempt downloading it. Fixes bug
1548 9645; bugfix on 0.2.2.6-alpha.
1549 - The new channel code sometimes lost track of in-progress circuits,
1550 causing long-running clients to stop building new circuits. The
1551 fix is to always call circuit_n_chan_done(chan, 0) from
1552 channel_closed(). Fixes bug 9776; bugfix on 0.2.4.17-rc.
1555 - Tor now builds each source file in two modes: a mode that avoids
1556 exposing identifiers needlessly, and another mode that exposes
1557 more identifiers for testing. This lets the compiler do better at
1558 optimizing the production code, while enabling us to take more
1559 radical measures to let the unit tests test things.
1560 - The production builds no longer include functions used only in
1561 the unit tests; all functions exposed from a module only for
1562 unit-testing are now static in production builds.
1563 - Add an --enable-coverage configuration option to make the unit
1564 tests (and a new src/or/tor-cov target) to build with gcov test
1568 - We now have rudimentary function mocking support that our unit
1569 tests can use to test functions in isolation. Function mocking
1570 lets the tests temporarily replace a function's dependencies with
1571 stub functions, so that the tests can check the function without
1572 invoking the other functions it calls.
1573 - Add more unit tests for the <circid,channel>->circuit map, and
1574 the destroy-cell-tracking code to fix bug 7912.
1575 - Unit tests for failing cases of the TAP onion handshake.
1576 - More unit tests for address-manipulation functions.
1578 o Minor features (protecting client timestamps):
1579 - Clients no longer send timestamps in their NETINFO cells. These were
1580 not used for anything, and they provided one small way for clients
1581 to be distinguished from each other as they moved from network to
1582 network or behind NAT. Implements part of proposal 222.
1583 - Clients now round timestamps in INTRODUCE cells down to the nearest
1584 10 minutes. If a new Support022HiddenServices option is set to 0, or
1585 if it's set to "auto" and the feature is disabled in the consensus,
1586 the timestamp is sent as 0 instead. Implements part of proposal 222.
1587 - Stop sending timestamps in AUTHENTICATE cells. This is not such
1588 a big deal from a security point of view, but it achieves no actual
1589 good purpose, and isn't needed. Implements part of proposal 222.
1590 - Reduce down accuracy of timestamps in hidden service descriptors.
1591 Implements part of proposal 222.
1593 o Minor features (config options):
1594 - Config (torrc) lines now handle fingerprints which are missing
1595 their initial '$'. Resolves ticket 4341; improvement over 0.0.9pre5.
1596 - Support a --dump-config option to print some or all of the
1597 configured options. Mainly useful for debugging the command-line
1598 option parsing code. Helps resolve ticket 4647.
1599 - Raise awareness of safer logging: notify user of potentially
1600 unsafe config options, like logging more verbosely than severity
1601 "notice" or setting SafeLogging to 0. Resolves ticket 5584.
1602 - Add a new configuration option TestingV3AuthVotingStartOffset
1603 that bootstraps a network faster by changing the timing for
1604 consensus votes. Addresses ticket 8532.
1605 - Add a new torrc option "ServerTransportOptions" that allows
1606 bridge operators to pass configuration parameters to their
1607 pluggable transports. Resolves ticket 8929.
1608 - The config (torrc) file now accepts bandwidth and space limits in
1609 bits as well as bytes. (Anywhere that you can say "2 Kilobytes",
1610 you can now say "16 kilobits", and so on.) Resolves ticket 9214.
1613 o Minor features (build):
1614 - Add support for `--library-versions` flag. Implements ticket 6384.
1615 - Return the "unexpected sendme" warnings to a warn severity, but make
1616 them rate limited, to help diagnose ticket 8093.
1617 - Detect a missing asciidoc, and warn the user about it, during
1618 configure rather than at build time. Fixes issue 6506. Patch from
1621 o Minor features (other):
1622 - Use the SOCK_NONBLOCK socket type, if supported, to open nonblocking
1623 sockets in a single system call. Implements ticket 5129.
1624 - Log current accounting state (bytes sent and received + remaining
1625 time for the current accounting period) in the relay's heartbeat
1626 message. Implements ticket 5526; patch from Peter Retzlaff.
1627 - Implement the TRANSPORT_LAUNCHED control port event that
1628 notifies controllers about new launched pluggable
1629 transports. Resolves ticket 5609.
1630 - If we're using the pure-C 32-bit curve25519_donna implementation
1631 of curve25519, build it with the -fomit-frame-pointer option to
1632 make it go faster on register-starved hosts. This improves our
1633 handshake performance by about 6% on i386 hosts without nacl.
1635 - Update to the September 4 2013 Maxmind GeoLite Country database.
1638 - Set the listen() backlog limit to the largest actually supported
1639 on the system, not to the value in a header file. Fixes bug 9716;
1640 bugfix on every released Tor.
1641 - No longer accept malformed http headers when parsing urls from
1642 headers. Now we reply with Bad Request ("400"). Fixes bug 2767;
1643 bugfix on 0.0.6pre1.
1644 - In munge_extrainfo_into_routerinfo(), check the return value of
1645 memchr(). This would have been a serious issue if we ever passed
1646 it a non-extrainfo. Fixes bug 8791; bugfix on 0.2.0.6-alpha. Patch
1648 - On the chance that somebody manages to build Tor on a
1649 platform where time_t is unsigned, correct the way that
1650 microdesc_add_to_cache() handles negative time arguments.
1651 Fixes bug 8042; bugfix on 0.2.3.1-alpha.
1652 - Reject relative control socket paths and emit a warning. Previously,
1653 single-component control socket paths would be rejected, but Tor
1654 would not log why it could not validate the config. Fixes bug 9258;
1655 bugfix on 0.2.3.16-alpha.
1657 o Minor bugfixes (command line):
1658 - Use a single command-line parser for parsing torrc options on the
1659 command line and for finding special command-line options to avoid
1660 inconsistent behavior for torrc option arguments that have the same
1661 names as command-line options. Fixes bugs 4647 and 9578; bugfix on
1663 - No longer allow 'tor --hash-password' with no arguments. Fixes bug
1664 9573; bugfix on 0.0.9pre5.
1666 o Minor fixes (build, auxiliary programs):
1667 - Stop preprocessing the "torify" script with autoconf, since
1668 it no longer refers to LOCALSTATEDIR. Fixes bug 5505; patch
1670 - The tor-fw-helper program now follows the standard convention and
1671 exits with status code "0" on success. Fixes bug 9030; bugfix on
1672 0.2.3.1-alpha. Patch by Arlo Breault.
1673 - Corrected ./configure advice for what openssl dev package you should
1674 install on Debian. Fixes bug 9207; bugfix on 0.2.0.1-alpha.
1676 o Minor code improvements:
1677 - Remove constants and tests for PKCS1 padding; it's insecure and
1678 shouldn't be used for anything new. Fixes bug 8792; patch
1680 - Remove instances of strcpy() from the unit tests. They weren't
1681 hurting anything, since they were only in the unit tests, but it's
1682 embarassing to have strcpy() in the code at all, and some analysis
1683 tools don't like it. Fixes bug 8790; bugfix on 0.2.3.6-alpha and
1684 0.2.3.8-alpha. Patch from Arlo Breault.
1687 - Remove migration code from when we renamed the "cached-routers"
1688 file to "cached-descriptors" back in 0.2.0.8-alpha. This
1689 incidentally resolves ticket 6502 by cleaning up the related code
1690 a bit. Patch from Akshay Hebbar.
1692 o Code simplification and refactoring:
1693 - Extract the common duplicated code for creating a subdirectory
1694 of the data directory and writing to a file in it. Fixes ticket
1695 4282; patch from Peter Retzlaff.
1696 - Since OpenSSL 0.9.7, the i2d_*() functions support allocating output
1697 buffer. Avoid calling twice: i2d_RSAPublicKey(), i2d_DHparams(),
1698 i2d_X509(), and i2d_PublicKey(). Resolves ticket 5170.
1699 - Add a set of accessor functions for the circuit timeout data
1700 structure. Fixes ticket 6153; patch from "piet".
1701 - Clean up exit paths from connection_listener_new(). Closes ticket
1702 8789. Patch from Arlo Breault.
1703 - Since we rely on OpenSSL 0.9.8 now, we can use EVP_PKEY_cmp()
1704 and drop our own custom pkey_eq() implementation. Fixes bug 9043.
1705 - Use a doubly-linked list to implement the global circuit list.
1706 Resolves ticket 9108. Patch from Marek Majkowski.
1707 - Remove contrib/id_to_fp.c since it wasn't used anywhere.
1710 Changes in version 0.2.4.17-rc - 2013-09-05
1711 Tor 0.2.4.17-rc is the third release candidate for the Tor 0.2.4.x
1712 series. It adds an emergency step to help us tolerate the massive
1713 influx of users: 0.2.4 clients using the new (faster and safer) "NTor"
1714 circuit-level handshakes now effectively jump the queue compared to
1715 the 0.2.3 clients using "TAP" handshakes. This release also fixes a
1716 big bug hindering bridge reachability tests.
1719 - Relays now process the new "NTor" circuit-level handshake requests
1720 with higher priority than the old "TAP" circuit-level handshake
1721 requests. We still process some TAP requests to not totally starve
1722 0.2.3 clients when NTor becomes popular. A new consensus parameter
1723 "NumNTorsPerTAP" lets us tune the balance later if we need to.
1724 Implements ticket 9574.
1727 - If the circuit build timeout logic is disabled (via the consensus,
1728 or because we are an authority), then don't build testing circuits.
1729 Fixes bug 9657; bugfix on 0.2.2.14-alpha.
1730 - Bridges now send AUTH_CHALLENGE cells during their v3 handshakes;
1731 previously they did not, which prevented them from receiving
1732 successful connections from relays for self-test or bandwidth
1733 testing. Also, when a relay is extending a circuit to a bridge,
1734 it needs to send a NETINFO cell, even when the bridge hasn't sent
1735 an AUTH_CHALLENGE cell. Fixes bug 9546; bugfix on 0.2.3.6-alpha.
1736 - If the time to download the next old-style networkstatus is in
1737 the future, do not decline to consider whether to download the
1738 next microdescriptor networkstatus. Fixes bug 9564; bugfix on
1742 - Avoid double-closing the listener socket in our socketpair()
1743 replacement (used on Windows) in the case where the addresses on
1744 our opened sockets don't match what we expected. Fixes bug 9400;
1745 bugfix on 0.0.2pre7. Found by Coverity.
1747 o Minor fixes (config options):
1748 - Avoid overflows when the user sets MaxCircuitDirtiness to a
1749 ridiculously high value, by imposing a (ridiculously high) 30-day
1750 maximum on MaxCircuitDirtiness.
1751 - Fix the documentation of HeartbeatPeriod to say that the heartbeat
1752 message is logged at notice, not at info.
1753 - Warn and fail if a server is configured not to advertise any
1754 ORPorts at all. (We need *something* to put in our descriptor,
1755 or we just won't work.)
1758 - Track how many "TAP" and "NTor" circuit handshake requests we get,
1759 and how many we complete, and log it every hour to help relay
1760 operators follow trends in network load. Addresses ticket 9658.
1761 - Update to the August 7 2013 Maxmind GeoLite Country database.
1764 Changes in version 0.2.4.16-rc - 2013-08-10
1765 Tor 0.2.4.16-rc is the second release candidate for the Tor 0.2.4.x
1766 series. It fixes several crash bugs in the 0.2.4 branch.
1769 - Fix a bug in the voting algorithm that could yield incorrect results
1770 when a non-naming authority declared too many flags. Fixes bug 9200;
1771 bugfix on 0.2.0.3-alpha.
1772 - Fix an uninitialized read that could in some cases lead to a remote
1773 crash while parsing INTRODUCE2 cells. Bugfix on 0.2.4.1-alpha.
1774 Anybody running a hidden service on the experimental 0.2.4.x
1775 branch should upgrade. (This is, so far as we know, unrelated to
1777 - Avoid an assertion failure when processing DNS replies without the
1778 answer types we expected. Fixes bug 9337; bugfix on 0.2.4.7-alpha.
1779 - Avoid a crash when using --hash-password. Fixes bug 9295; bugfix on
1780 0.2.4.15-rc. Found by stem integration tests.
1783 - Fix an invalid memory read that occured when a pluggable
1784 transport proxy failed its configuration protocol.
1785 Fixes bug 9288; bugfix on 0.2.4.1-alpha.
1786 - When evaluating whether to use a connection that we haven't
1787 decided is canonical using a recent link protocol version,
1788 decide that it's canonical only if it used address _does_
1789 match the desired address. Fixes bug 9309; bugfix on
1790 0.2.4.4-alpha. Reported by skruffy.
1791 - Make the default behavior of NumDirectoryGuards be to track
1792 NumEntryGuards. Now a user who changes only NumEntryGuards will get
1793 the behavior she expects. Fixes bug 9354; bugfix on 0.2.4.8-alpha.
1794 - Fix a spurious compilation warning with some older versions of
1795 GCC on FreeBSD. Fixes bug 9254; bugfix on 0.2.4.14-alpha.
1798 - Update to the July 3 2013 Maxmind GeoLite Country database.
1801 Changes in version 0.2.4.15-rc - 2013-07-01
1802 Tor 0.2.4.15-rc is the first release candidate for the Tor 0.2.4.x
1803 series. It fixes a few smaller bugs, but generally appears stable.
1804 Please test it and let us know whether it is!
1807 - When receiving a new configuration file via the control port's
1808 LOADCONF command, do not treat the defaults file as absent.
1809 Fixes bug 9122; bugfix on 0.2.3.9-alpha.
1812 - Issue a warning when running with the bufferevents backend enabled.
1813 It's still not stable, and people should know that they're likely
1814 to hit unexpected problems. Closes ticket 9147.
1817 Changes in version 0.2.4.14-alpha - 2013-06-18
1818 Tor 0.2.4.14-alpha fixes a pair of client guard enumeration problems
1819 present in 0.2.4.13-alpha.
1822 - When we have too much memory queued in circuits (according to a new
1823 MaxMemInCellQueues option), close the circuits consuming the most
1824 memory. This prevents us from running out of memory as a relay if
1825 circuits fill up faster than they can be drained. Fixes bug 9063;
1826 bugfix on the 54th commit of Tor. This bug is a further fix beyond
1827 bug 6252, whose fix was merged into 0.2.3.21-rc.
1829 This change also fixes an earlier approach taken in 0.2.4.13-alpha,
1830 where we tried to solve this issue simply by imposing an upper limit
1831 on the number of queued cells for a single circuit. That approach
1832 proved to be problematic, since there are ways to provoke clients to
1833 send a number of cells in excess of any such reasonable limit. Fixes
1834 bug 9072; bugfix on 0.2.4.13-alpha.
1836 - Limit hidden service descriptors to at most ten introduction
1837 points, to slow one kind of guard enumeration. Fixes bug 9002;
1838 bugfix on 0.1.1.11-alpha.
1841 Changes in version 0.2.4.13-alpha - 2013-06-14
1842 Tor 0.2.4.13-alpha fixes a variety of potential remote crash
1843 vulnerabilities, makes socks5 username/password circuit isolation
1844 actually actually work (this time for sure!), and cleans up a bunch
1845 of other issues in preparation for a release candidate.
1847 o Major bugfixes (robustness):
1848 - Close any circuit that has too many cells queued on it. Fixes
1849 bug 9063; bugfix on the 54th commit of Tor. This bug is a further
1850 fix beyond bug 6252, whose fix was merged into 0.2.3.21-rc.
1851 - Prevent the get_freelists() function from running off the end of
1852 the list of freelists if it somehow gets an unrecognized
1853 allocation. Fixes bug 8844; bugfix on 0.2.0.16-alpha. Reported by
1855 - Avoid an assertion failure on OpenBSD (and perhaps other BSDs)
1856 when an exit connection with optimistic data succeeds immediately
1857 rather than returning EINPROGRESS. Fixes bug 9017; bugfix on
1859 - Fix a directory authority crash bug when building a consensus
1860 using an older consensus as its basis. Fixes bug 8833. Bugfix
1864 - Avoid a memory leak where we would leak a consensus body when we
1865 find that a consensus which we couldn't previously verify due to
1866 missing certificates is now verifiable. Fixes bug 8719; bugfix
1868 - We used to always request authority certificates by identity digest,
1869 meaning we'd get the newest one even when we wanted one with a
1870 different signing key. Then we would complain about being given
1871 a certificate we already had, and never get the one we really
1872 wanted. Now we use the "fp-sk/" resource as well as the "fp/"
1873 resource to request the one we want. Fixes bug 5595; bugfix on
1875 - Follow the socks5 protocol when offering username/password
1876 authentication. The fix for bug 8117 exposed this bug, and it
1877 turns out real-world applications like Pidgin do care. Bugfix on
1878 0.2.3.2-alpha; fixes bug 8879.
1879 - Prevent failures on Windows Vista and later when rebuilding the
1880 microdescriptor cache. Diagnosed by Robert Ransom. Fixes bug 8822;
1881 bugfix on 0.2.4.12-alpha.
1884 - Fix an impossible buffer overrun in the AES unit tests. Fixes
1885 bug 8845; bugfix on 0.2.0.7-alpha. Found by eugenis.
1886 - If for some reason we fail to write a microdescriptor while
1887 rebuilding the cache, do not let the annotations from that
1888 microdescriptor linger in the cache file, and do not let the
1889 microdescriptor stay recorded as present in its old location.
1890 Fixes bug 9047; bugfix on 0.2.2.6-alpha.
1891 - Fix a memory leak that would occur whenever a configuration
1892 option changed. Fixes bug 8718; bugfix on 0.2.3.3-alpha.
1893 - Paste the description for PathBias parameters from the man
1894 page into or.h, so the code documents them too. Fixes bug 7982;
1895 bugfix on 0.2.3.17-beta and 0.2.4.8-alpha.
1896 - Relays now treat a changed IPv6 ORPort as sufficient reason to
1897 publish an updated descriptor. Fixes bug 6026; bugfix on
1899 - When launching a resolve request on behalf of an AF_UNIX control
1900 socket, omit the address field of the new entry connection, used in
1901 subsequent controller events, rather than letting tor_dup_addr()
1902 set it to "<unknown address type>". Fixes bug 8639; bugfix on
1905 o Minor bugfixes (log messages):
1906 - Fix a scaling issue in the path bias accounting code that
1907 resulted in "Bug:" log messages from either
1908 pathbias_scale_close_rates() or pathbias_count_build_success().
1909 This represents a bugfix on a previous bugfix: the original fix
1910 attempted in 0.2.4.10-alpha was incomplete. Fixes bug 8235; bugfix
1912 - Give a less useless error message when the user asks for an IPv4
1913 address on an IPv6-only port, or vice versa. Fixes bug 8846; bugfix
1917 - Downgrade "unexpected SENDME" warnings to protocol-warn for 0.2.4.x,
1918 to tolerate bug 8093 for now.
1919 - Add an "ignoring-advertised-bws" boolean to the flag-threshold lines
1920 in directory authority votes to describe whether they have enough
1921 measured bandwidths to ignore advertised (relay descriptor)
1922 bandwidth claims. Resolves ticket 8711.
1923 - Update to the June 5 2013 Maxmind GeoLite Country database.
1925 o Removed documentation:
1926 - Remove some of the older contents of doc/ as obsolete; move others
1927 to torspec.git. Fixes bug 8965.
1929 o Code simplification and refactoring:
1930 - Avoid using character buffers when constructing most directory
1931 objects: this approach was unwieldy and error-prone. Instead,
1932 build smartlists of strings, and concatenate them when done.
1935 Changes in version 0.2.4.12-alpha - 2013-04-18
1936 Tor 0.2.4.12-alpha moves Tor forward on several fronts: it starts the
1937 process for lengthening the guard rotation period, makes directory
1938 authority opinions in the consensus a bit less gameable, makes socks5
1939 username/password circuit isolation actually work, and fixes a wide
1940 variety of other issues.
1943 - Raise the default time that a client keeps an entry guard from
1944 "1-2 months" to "2-3 months", as suggested by Tariq Elahi's WPES
1945 2012 paper. (We would make it even longer, but we need better client
1946 load balancing first.) Also, make the guard lifetime controllable
1947 via a new GuardLifetime torrc option and a GuardLifetime consensus
1948 parameter. Start of a fix for bug 8240; bugfix on 0.1.1.11-alpha.
1949 - Directory authorities now prefer using measured bandwidths to
1950 advertised ones when computing flags and thresholds. Resolves
1952 - Directory authorities that have more than a threshold number
1953 of relays with measured bandwidths now treat relays with unmeasured
1954 bandwidths as having bandwidth 0. Resolves ticket 8435.
1956 o Major bugfixes (assert / resource use):
1957 - Avoid a bug where our response to TLS renegotiation under certain
1958 network conditions could lead to a busy-loop, with 100% CPU
1959 consumption. Fixes bug 5650; bugfix on 0.2.0.16-alpha.
1960 - Avoid an assertion when we discover that we'd like to write a cell
1961 onto a closing connection: just discard the cell. Fixes another
1962 case of bug 7350; bugfix on 0.2.4.4-alpha.
1964 o Major bugfixes (client-side privacy):
1965 - When we mark a circuit as unusable for new circuits, have it
1966 continue to be unusable for new circuits even if MaxCircuitDirtiness
1967 is increased too much at the wrong time, or the system clock jumps
1968 backwards. Fixes bug 6174; bugfix on 0.0.2pre26.
1969 - If ClientDNSRejectInternalAddresses ("do not believe DNS queries
1970 which have resolved to internal addresses") is set, apply that
1971 rule to IPv6 as well. Fixes bug 8475; bugfix on 0.2.0.7-alpha.
1972 - When an exit relay rejects a stream with reason "exit policy", but
1973 we only know an exit policy summary (e.g. from the microdesc
1974 consensus) for it, do not mark the relay as useless for all exiting.
1975 Instead, mark just the circuit as unsuitable for that particular
1976 address. Fixes part of bug 7582; bugfix on 0.2.3.2-alpha.
1977 - Allow applications to get proper stream isolation with
1978 IsolateSOCKSAuth. Many SOCKS5 clients that want to offer
1979 username/password authentication also offer "no authentication". Tor
1980 had previously preferred "no authentication", so the applications
1981 never actually sent Tor their auth details. Now Tor selects
1982 username/password authentication if it's offered. You can disable
1983 this behavior on a per-SOCKSPort basis via PreferSOCKSNoAuth. Fixes
1984 bug 8117; bugfix on 0.2.3.3-alpha.
1986 o Major bugfixes (other):
1987 - When unable to find any working directory nodes to use as a
1988 directory guard, give up rather than adding the same non-working
1989 nodes to the directory guard list over and over. Fixes bug 8231;
1990 bugfix on 0.2.4.8-alpha.
1993 - Reject as invalid most directory objects containing a NUL.
1994 Belt-and-suspender fix for bug 8037.
1995 - In our testsuite, create temporary directories with a bit more
1996 entropy in their name to make name collisions less likely. Fixes
1998 - Add CACHED keyword to ADDRMAP events in the control protocol
1999 to indicate whether a DNS result will be cached or not. Resolves
2001 - Update to the April 3 2013 Maxmind GeoLite Country database.
2003 o Minor features (build):
2004 - Detect and reject attempts to build Tor with threading support
2005 when OpenSSL has been compiled without threading support.
2007 - Clarify that when autoconf is checking for nacl, it is checking
2008 specifically for nacl with a fast curve25519 implementation.
2010 - Warn if building on a platform with an unsigned time_t: there
2011 are too many places where Tor currently assumes that time_t can
2012 hold negative values. We'd like to fix them all, but probably
2015 o Minor bugfixes (build):
2016 - Fix some bugs in tor-fw-helper-natpmp when trying to build and
2017 run it on Windows. More bugs likely remain. Patch from Gisle Vanem.
2018 Fixes bug 7280; bugfix on 0.2.3.1-alpha.
2019 - Add the old src/or/micro-revision.i filename to CLEANFILES.
2020 On the off chance that somebody has one, it will go away as soon
2021 as they run "make clean". Fix for bug 7143; bugfix on 0.2.4.1-alpha.
2022 - Build Tor correctly on 32-bit platforms where the compiler can build
2023 but not run code using the "uint128_t" construction. Fixes bug 8587;
2024 bugfix on 0.2.4.8-alpha.
2025 - Fix compilation warning with some versions of clang that would
2026 prefer the -Wswitch-enum compiler flag to warn about switch
2027 statements with missing enum values, even if those switch
2028 statements have a "default:" statement. Fixes bug 8598; bugfix
2031 o Minor bugfixes (protocol):
2032 - Fix the handling of a TRUNCATE cell when it arrives while the
2033 circuit extension is in progress. Fixes bug 7947; bugfix on 0.0.7.1.
2034 - Fix a misframing issue when reading the version numbers in a
2035 VERSIONS cell. Previously we would recognize [00 01 00 02] as
2036 'version 1, version 2, and version 0x100', when it should have
2037 only included versions 1 and 2. Fixes bug 8059; bugfix on
2038 0.2.0.10-alpha. Reported pseudonymously.
2039 - Make the format and order of STREAM events for DNS lookups
2040 consistent among the various ways to launch DNS lookups. Fixes
2041 bug 8203; bugfix on 0.2.0.24-rc. Patch by "Desoxy."
2042 - Correct our check for which versions of Tor support the EXTEND2
2043 cell. We had been willing to send it to Tor 0.2.4.7-alpha and
2044 later, when support was really added in version 0.2.4.8-alpha.
2045 Fixes bug 8464; bugfix on 0.2.4.8-alpha.
2047 o Minor bugfixes (other):
2048 - Correctly store microdescriptors and extrainfo descriptors with
2049 an internal NUL byte. Fixes bug 8037; bugfix on 0.2.0.1-alpha.
2050 Bug reported by "cypherpunks".
2051 - Increase the width of the field used to remember a connection's
2052 link protocol version to two bytes. Harmless for now, since the
2053 only currently recognized versions are one byte long. Reported
2054 pseudonymously. Fixes bug 8062; bugfix on 0.2.0.10-alpha.
2055 - If the state file's path bias counts are invalid (presumably from a
2056 buggy Tor prior to 0.2.4.10-alpha), make them correct. Also add
2057 additional checks and log messages to the scaling of Path Bias
2058 counts, in case there still are remaining issues with scaling.
2059 Should help resolve bug 8235.
2060 - Eliminate several instances where we use "Nickname=ID" to refer to
2061 nodes in logs. Use "Nickname (ID)" instead. (Elsewhere, we still use
2062 "$ID=Nickname", which is also acceptable.) Fixes bug 7065. Bugfix
2063 on 0.2.3.21-rc, 0.2.4.5-alpha, 0.2.4.8-alpha, and 0.2.4.10-alpha.
2065 o Minor bugfixes (syscalls):
2066 - Always check the return values of functions fcntl() and
2067 setsockopt(). We don't believe these are ever actually failing in
2068 practice, but better safe than sorry. Also, checking these return
2069 values should please analysis tools like Coverity. Patch from
2070 'flupzor'. Fixes bug 8206; bugfix on all versions of Tor.
2071 - Use direct writes rather than stdio when building microdescriptor
2072 caches, in an attempt to mitigate bug 8031, or at least make it
2075 o Minor bugfixes (config):
2076 - When rejecting a configuration because we were unable to parse a
2077 quoted string, log an actual error message. Fixes bug 7950; bugfix
2079 - Behave correctly when the user disables LearnCircuitBuildTimeout
2080 but doesn't tell us what they would like the timeout to be. Fixes
2081 bug 6304; bugfix on 0.2.2.14-alpha.
2082 - When autodetecting the number of CPUs, use the number of available
2083 CPUs in preference to the number of configured CPUs. Inform the
2084 user if this reduces the number of available CPUs. Fixes bug 8002;
2085 bugfix on 0.2.3.1-alpha.
2086 - Make it an error when you set EntryNodes but disable UseGuardNodes,
2087 since it will (surprisingly to some users) ignore EntryNodes. Fixes
2088 bug 8180; bugfix on 0.2.3.11-alpha.
2089 - Allow TestingTorNetworks to override the 4096-byte minimum for
2090 the Fast threshold. Otherwise they can't bootstrap until they've
2091 observed more traffic. Fixes bug 8508; bugfix on 0.2.4.10-alpha.
2092 - Fix some logic errors when the user manually overrides the
2093 PathsNeededToBuildCircuits option in torrc. Fixes bug 8599; bugfix
2096 o Minor bugfixes (log messages to help diagnose bugs):
2097 - If we fail to free a microdescriptor because of bug 7164, log
2098 the filename and line number from which we tried to free it.
2099 - Add another diagnostic to the heartbeat message: track and log
2100 overhead that TLS is adding to the data we write. If this is
2101 high, we are sending too little data to SSL_write at a time.
2102 Diagnostic for bug 7707.
2103 - Add more detail to a log message about relaxed timeouts, to help
2105 - Warn more aggressively when flushing microdescriptors to a
2106 microdescriptor cache fails, in an attempt to mitigate bug 8031,
2107 or at least make it more diagnosable.
2108 - Improve debugging output to help track down bug 8185 ("Bug:
2109 outgoing relay cell has n_chan==NULL. Dropping.")
2110 - Log the purpose of a path-bias testing circuit correctly.
2111 Improves a log message from bug 8477; bugfix on 0.2.4.8-alpha.
2113 o Minor bugfixes (0.2.4.x log messages that were too noisy):
2114 - Don't attempt to relax the timeout of already opened 1-hop circuits.
2115 They might never timeout. This should eliminate some/all cases of
2116 the relaxed timeout log message.
2117 - Use circuit creation time for network liveness evaluation. This
2118 should eliminate warning log messages about liveness caused
2119 by changes in timeout evaluation. Fixes bug 6572; bugfix on
2121 - Reduce a path bias length check from notice to info. The message
2122 is triggered when creating controller circuits. Fixes bug 8196;
2123 bugfix on 0.2.4.8-alpha.
2124 - Fix a path state issue that triggered a notice during relay startup.
2125 Fixes bug 8320; bugfix on 0.2.4.10-alpha.
2126 - Reduce occurrences of warns about circuit purpose in
2127 connection_ap_expire_building(). Fixes bug 8477; bugfix on
2130 o Minor bugfixes (pre-0.2.4.x log messages that were too noisy):
2131 - If we encounter a write failure on a SOCKS connection before we
2132 finish our SOCKS handshake, don't warn that we closed the
2133 connection before we could send a SOCKS reply. Fixes bug 8427;
2134 bugfix on 0.1.0.1-rc.
2135 - Correctly recognize that [::1] is a loopback address. Fixes
2136 bug 8377; bugfix on 0.2.1.3-alpha.
2137 - Fix a directory authority warn caused when we have a large amount
2138 of badexit bandwidth. Fixes bug 8419; bugfix on 0.2.2.10-alpha.
2139 - Don't log inappropriate heartbeat messages when hibernating: a
2140 hibernating node is _expected_ to drop out of the consensus,
2141 decide it isn't bootstrapped, and so forth. Fixes bug 7302;
2142 bugfix on 0.2.3.1-alpha.
2143 - Don't complain about bootstrapping problems while hibernating.
2144 These complaints reflect a general code problem, but not one
2145 with any problematic effects (no connections are actually
2146 opened). Fixes part of bug 7302; bugfix on 0.2.3.2-alpha.
2148 o Documentation fixes:
2149 - Update tor-fw-helper.1.txt and tor-fw-helper.c to make option
2150 names match. Fixes bug 7768.
2151 - Make the torify manpage no longer refer to tsocks; torify hasn't
2152 supported tsocks since 0.2.3.14-alpha.
2153 - Make the tor manpage no longer reference tsocks.
2154 - Fix the GeoIPExcludeUnknown documentation to refer to
2155 ExcludeExitNodes rather than the currently nonexistent
2156 ExcludeEntryNodes. Spotted by "hamahangi" on tor-talk.
2159 - The tor-tsocks.conf is no longer distributed or installed. We
2160 recommend that tsocks users use torsocks instead. Resolves
2164 Changes in version 0.2.4.11-alpha - 2013-03-11
2165 Tor 0.2.4.11-alpha makes relay measurement by directory authorities
2166 more robust, makes hidden service authentication work again, and
2167 resolves a DPI fingerprint for Tor's SSL transport.
2169 o Major features (directory authorities):
2170 - Directory authorities now support a new consensus method (17)
2171 where they cap the published bandwidth of servers for which
2172 insufficient bandwidth measurements exist. Fixes part of bug 2286.
2173 - Directory authorities that set "DisableV2DirectoryInfo_ 1" no longer
2174 serve any v2 directory information. Now we can test disabling the
2175 old deprecated v2 directory format, and see whether doing so has
2176 any effect on network load. Begins to fix bug 6783.
2177 - Directory authorities now include inside each vote a statement of
2178 the performance thresholds they used when assigning flags.
2179 Implements ticket 8151.
2181 o Major bugfixes (directory authorities):
2182 - Stop marking every relay as having been down for one hour every
2183 time we restart a directory authority. These artificial downtimes
2184 were messing with our Stable and Guard flag calculations. Fixes
2185 bug 8218 (introduced by the fix for 1035). Bugfix on 0.2.2.23-alpha.
2187 o Major bugfixes (hidden services):
2188 - Allow hidden service authentication to succeed again. When we
2189 refactored the hidden service introduction code back
2190 in 0.2.4.1-alpha, we didn't update the code that checks
2191 whether authentication information is present, causing all
2192 authentication checks to return "false". Fix for bug 8207; bugfix
2193 on 0.2.4.1-alpha. Found by Coverity; this is CID 718615.
2195 o Minor features (relays, bridges):
2196 - Make bridge relays check once a minute for whether their IP
2197 address has changed, rather than only every 15 minutes. Resolves
2199 - Refactor resolve_my_address() so it returns the method by which we
2200 decided our public IP address (explicitly configured, resolved from
2201 explicit hostname, guessed from interfaces, learned by gethostname).
2202 Now we can provide more helpful log messages when a relay guesses
2203 its IP address incorrectly (e.g. due to unexpected lines in
2204 /etc/hosts). Resolves ticket 2267.
2205 - Teach bridge-using clients to avoid 0.2.2 bridges when making
2206 microdescriptor-related dir requests, and only fall back to normal
2207 descriptors if none of their bridges can handle microdescriptors
2208 (as opposed to the fix in ticket 4013, which caused them to fall
2209 back to normal descriptors if *any* of their bridges preferred
2210 them). Resolves ticket 4994.
2211 - Randomize the lifetime of our SSL link certificate, so censors can't
2212 use the static value for filtering Tor flows. Resolves ticket 8443;
2213 related to ticket 4014 which was included in 0.2.2.33.
2214 - Support a new version of the link protocol that allows 4-byte circuit
2215 IDs. Previously, circuit IDs were limited to 2 bytes, which presented
2216 a possible resource exhaustion issue. Closes ticket 7351; implements
2219 o Minor features (portability):
2220 - Tweak the curve25519-donna*.c implementations to tolerate systems
2221 that lack stdint.h. Fixes bug 3894; bugfix on 0.2.4.8-alpha.
2222 - Use Ville Laurikari's implementation of AX_CHECK_SIGN() to determine
2223 the signs of types during autoconf. This is better than our old
2224 approach, which didn't work when cross-compiling.
2225 - Detect the sign of enum values, rather than assuming that MSC is the
2226 only compiler where enum types are all signed. Fixes bug 7727;
2227 bugfix on 0.2.4.10-alpha.
2229 o Minor features (other):
2230 - Say "KBytes" rather than "KB" in the man page (for various values
2231 of K), to further reduce confusion about whether Tor counts in
2232 units of memory or fractions of units of memory. Resolves ticket 7054.
2233 - Clear the high bit on curve25519 public keys before passing them to
2234 our backend, in case we ever wind up using a backend that doesn't do
2235 so itself. If we used such a backend, and *didn't* clear the high bit,
2236 we could wind up in a situation where users with such backends would
2237 be distinguishable from users without. Fixes bug 8121; bugfix on
2239 - Update to the March 6 2013 Maxmind GeoLite Country database.
2241 o Minor bugfixes (clients):
2242 - When we receive a RELAY_END cell with the reason DONE, or with no
2243 reason, before receiving a RELAY_CONNECTED cell, report the SOCKS
2244 status as "connection refused". Previously we reported these cases
2245 as success but then immediately closed the connection. Fixes bug
2246 7902; bugfix on 0.1.0.1-rc. Reported by "oftc_must_be_destroyed".
2247 - Downgrade an assertion in connection_ap_expire_beginning to an
2248 LD_BUG message. The fix for bug 8024 should prevent this message
2249 from displaying, but just in case, a warn that we can diagnose
2250 is better than more assert crashes. Fixes bug 8065; bugfix on
2252 - Lower path use bias thresholds to .80 for notice and .60 for warn.
2253 Also make the rate limiting flags for the path use bias log messages
2254 independent from the original path bias flags. Fixes bug 8161;
2255 bugfix on 0.2.4.10-alpha.
2257 o Minor bugfixes (relays):
2258 - Stop trying to resolve our hostname so often (e.g. every time we
2259 think about doing a directory fetch). Now we reuse the cached
2260 answer in some cases. Fixes bugs 1992 (bugfix on 0.2.0.20-rc)
2261 and 2410 (bugfix on 0.1.2.2-alpha).
2262 - Stop sending a stray "(null)" in some cases for the server status
2263 "EXTERNAL_ADDRESS" controller event. Resolves bug 8200; bugfix
2265 - When choosing which stream on a formerly stalled circuit to wake
2266 first, make better use of the platform's weak RNG. Previously,
2267 we had been using the % ("modulo") operator to try to generate a
2268 1/N chance of picking each stream, but this behaves badly with
2269 many platforms' choice of weak RNG. Fixes bug 7801; bugfix on
2271 - Use our own weak RNG when we need a weak RNG. Windows's rand() and
2272 Irix's random() only return 15 bits; Solaris's random() returns more
2273 bits but its RAND_MAX says it only returns 15, and so on. Motivated
2274 by the fix for bug 7801; bugfix on 0.2.2.20-alpha.
2276 o Minor bugfixes (directory authorities):
2277 - Directory authorities now use less space when formatting identical
2278 microdescriptor lines in directory votes. Fixes bug 8158; bugfix
2281 o Minor bugfixes (memory leaks spotted by Coverity -- bug 7816):
2282 - Avoid leaking memory if we fail to compute a consensus signature
2283 or we generate a consensus we can't parse. Bugfix on 0.2.0.5-alpha.
2284 - Fix a memory leak when receiving headers from an HTTPS proxy. Bugfix
2286 - Fix a memory leak during safe-cookie controller authentication.
2287 Bugfix on 0.2.3.13-alpha.
2288 - Avoid memory leak of IPv6 policy content if we fail to format it into
2289 a router descriptor. Bugfix on 0.2.4.7-alpha.
2291 o Minor bugfixes (other code correctness issues):
2292 - Avoid a crash if we fail to generate an extrainfo descriptor.
2293 Fixes bug 8208; bugfix on 0.2.3.16-alpha. Found by Coverity;
2295 - When detecting the largest possible file descriptor (in order to
2296 close all file descriptors when launching a new program), actually
2297 use _SC_OPEN_MAX. The old code for doing this was very, very broken.
2298 Fixes bug 8209; bugfix on 0.2.3.1-alpha. Found by Coverity; this
2300 - Fix a copy-and-paste error when adding a missing A1 to a routerset
2301 because of GeoIPExcludeUnknown. Fix for Coverity CID 980650.
2302 Bugfix on 0.2.4.10-alpha.
2303 - Fix an impossible-to-trigger integer overflow when estimating how
2304 long our onionskin queue would take. (This overflow would require us
2305 to accept 4 million onionskins before processing 100 of them.) Fixes
2306 bug 8210; bugfix on 0.2.4.10-alpha.
2308 o Code simplification and refactoring:
2309 - Add a wrapper function for the common "log a message with a
2313 Changes in version 0.2.4.10-alpha - 2013-02-04
2314 Tor 0.2.4.10-alpha adds defenses at the directory authority level from
2315 certain attacks that flood the network with relays; changes the queue
2316 for circuit create requests from a sized-based limit to a time-based
2317 limit; resumes building with MSVC on Windows; and fixes a wide variety
2320 o Major bugfixes (directory authority):
2321 - When computing directory thresholds, ignore any rejected-as-sybil
2322 nodes during the computation so that they can't influence Fast,
2323 Guard, etc. (We should have done this for proposal 109.) Fixes
2325 - When marking a node as a likely sybil, reset its uptime metrics
2326 to zero, so that it cannot time towards getting marked as Guard,
2327 Stable, or HSDir. (We should have done this for proposal 109.) Fixes
2331 - When a TLS write is partially successful but incomplete, remember
2332 that the flushed part has been flushed, and notice that bytes were
2333 actually written. Reported and fixed pseudonymously. Fixes bug
2334 7708; bugfix on Tor 0.1.0.5-rc.
2335 - Reject bogus create and relay cells with 0 circuit ID or 0 stream
2336 ID: these could be used to create unexpected streams and circuits
2337 which would count as "present" to some parts of Tor but "absent"
2338 to others, leading to zombie circuits and streams or to a bandwidth
2339 denial-of-service. Fixes bug 7889; bugfix on every released version
2340 of Tor. Reported by "oftc_must_be_destroyed".
2341 - Rename all macros in our local copy of queue.h to begin with "TOR_".
2342 This change seems the only good way to permanently prevent conflicts
2343 with queue.h on various operating systems. Fixes bug 8107; bugfix
2346 o Major features (relay):
2347 - Instead of limiting the number of queued onionskins (aka circuit
2348 create requests) to a fixed, hard-to-configure number, we limit
2349 the size of the queue based on how many we expect to be able to
2350 process in a given amount of time. We estimate the time it will
2351 take to process an onionskin based on average processing time
2352 of previous onionskins. Closes ticket 7291. You'll never have to
2353 configure MaxOnionsPending again.
2355 o Major features (portability):
2356 - Resume building correctly with MSVC and Makefile.nmake. This patch
2357 resolves numerous bugs and fixes reported by ultramage, including
2358 7305, 7308, 7309, 7310, 7312, 7313, 7315, 7316, and 7669.
2359 - Make the ntor and curve25519 code build correctly with MSVC.
2360 Fix on 0.2.4.8-alpha.
2363 - When directory authorities are computing thresholds for flags,
2364 never let the threshold for the Fast flag fall below 4096
2365 bytes. Also, do not consider nodes with extremely low bandwidths
2366 when deciding thresholds for various directory flags. This change
2367 should raise our threshold for Fast relays, possibly in turn
2368 improving overall network performance; see ticket 1854. Resolves
2370 - The Tor client now ignores sub-domain components of a .onion
2371 address. This change makes HTTP "virtual" hosting
2372 possible: http://foo.aaaaaaaaaaaaaaaa.onion/ and
2373 http://bar.aaaaaaaaaaaaaaaa.onion/ can be two different websites
2374 hosted on the same hidden service. Implements proposal 204.
2375 - We compute the overhead from passing onionskins back and forth to
2376 cpuworkers, and report it when dumping statistics in response to
2377 SIGUSR1. Supports ticket 7291.
2379 o Minor features (path selection):
2380 - When deciding whether we have enough descriptors to build circuits,
2381 instead of looking at raw relay counts, look at which fraction
2382 of (bandwidth-weighted) paths we're able to build. This approach
2383 keeps clients from building circuits if their paths are likely to
2384 stand out statistically. The default fraction of paths needed is
2385 taken from the consensus directory; you can override it with the
2386 new PathsNeededToBuildCircuits option. Fixes ticket 5956.
2387 - When any country code is listed in ExcludeNodes or ExcludeExitNodes,
2388 and we have GeoIP information, also exclude all nodes with unknown
2389 countries "??" and "A1". This behavior is controlled by the
2390 new GeoIPExcludeUnknown option: you can make such nodes always
2391 excluded with "GeoIPExcludeUnknown 1", and disable the feature
2392 with "GeoIPExcludeUnknown 0". Setting "GeoIPExcludeUnknown auto"
2393 gets you the default behavior. Implements feature 7706.
2394 - Path Use Bias: Perform separate accounting for successful circuit
2395 use. Keep separate statistics on stream attempt rates versus stream
2396 success rates for each guard. Provide configurable thresholds to
2397 determine when to emit log messages or disable use of guards that
2398 fail too many stream attempts. Resolves ticket 7802.
2400 o Minor features (log messages):
2401 - When learning a fingerprint for a bridge, log its corresponding
2402 transport type. Implements ticket 7896.
2403 - Improve the log message when "Bug/attack: unexpected sendme cell
2404 from client" occurs, to help us track bug 8093.
2407 - Remove a couple of extraneous semicolons that were upsetting the
2408 cparser library. Patch by Christian Grothoff. Fixes bug 7115;
2409 bugfix on 0.2.2.1-alpha.
2410 - Remove a source of rounding error during path bias count scaling;
2411 don't count cannibalized circuits as used for path bias until we
2412 actually try to use them; and fix a circuit_package_relay_cell()
2413 warning message about n_chan==NULL. Fixes bug 7802.
2414 - Detect nacl when its headers are in a nacl/ subdirectory. Also,
2415 actually link against nacl when we're configured to use it. Fixes
2416 bug 7972; bugfix on 0.2.4.8-alpha.
2417 - Compile correctly with the --disable-curve25519 option. Fixes
2418 bug 8153; bugfix on 0.2.4.8-alpha.
2420 o Build improvements:
2421 - Do not report status verbosely from autogen.sh unless the -v flag
2422 is specified. Fixes issue 4664. Patch from Onizuka.
2423 - Replace all calls to snprintf() outside of src/ext with
2424 tor_snprintf(). Also remove the #define to replace snprintf with
2425 _snprintf on Windows; they have different semantics, and all of
2426 our callers should be using tor_snprintf() anyway. Fixes bug 7304.
2427 - Try to detect if we are ever building on a platform where
2428 memset(...,0,...) does not set the value of a double to 0.0. Such
2429 platforms are permitted by the C standard, though in practice
2430 they're pretty rare (since IEEE 754 is nigh-ubiquitous). We don't
2431 currently support them, but it's better to detect them and fail
2432 than to perform erroneously.
2435 - Stop exporting estimates of v2 and v3 directory traffic shares
2436 in extrainfo documents. They were unneeded and sometimes inaccurate.
2437 Also stop exporting any v2 directory request statistics. Resolves
2439 - Drop support for detecting and warning about versions of Libevent
2440 before 1.3e. Nothing reasonable ships with them any longer;
2441 warning the user about them shouldn't be needed. Resolves ticket
2444 o Code simplifications and refactoring:
2445 - Rename "isin" functions to "contains", for grammar. Resolves
2447 - Rename Tor's logging function log() to tor_log(), to avoid conflicts
2448 with the natural logarithm function from the system libm. Resolves
2452 Changes in version 0.2.4.9-alpha - 2013-01-15
2453 Tor 0.2.4.9-alpha provides a quick fix to make the new ntor handshake
2457 - Fix backward compatibility logic when receiving an embedded ntor
2458 handshake tunneled in a CREATE cell. This clears up the "Bug:
2459 couldn't format CREATED cell" warning. Fixes bug 7959; bugfix
2463 Changes in version 0.2.4.8-alpha - 2013-01-14
2464 Tor 0.2.4.8-alpha introduces directory guards to reduce user enumeration
2465 risks, adds a new stronger and faster circuit handshake, and offers
2466 stronger and faster link encryption when both sides support it.
2469 - Preliminary support for directory guards (proposal 207): when
2470 possible, clients now use their entry guards for non-anonymous
2471 directory requests. This can help prevent client enumeration. Note
2472 that this behavior only works when we have a usable consensus
2473 directory, and when options about what to download are more or less
2474 standard. In the future we should re-bootstrap from our guards,
2475 rather than re-bootstrapping from the preconfigured list of
2476 directory sources that ships with Tor. Resolves ticket 6526.
2477 - Tor relays and clients now support a better CREATE/EXTEND cell
2478 format, allowing the sender to specify multiple address, identity,
2479 and handshake types. Implements Robert Ransom's proposal 200;
2482 o Major features (new circuit handshake):
2483 - Tor now supports a new circuit extension handshake designed by Ian
2484 Goldberg, Douglas Stebila, and Berkant Ustaoglu. Our original
2485 circuit extension handshake, later called "TAP", was a bit slow
2486 (especially on the relay side), had a fragile security proof, and
2487 used weaker keys than we'd now prefer. The new circuit handshake
2488 uses Dan Bernstein's "curve25519" elliptic-curve Diffie-Hellman
2489 function, making it significantly more secure than the older
2490 handshake, and significantly faster. Tor can use one of two built-in
2491 pure-C curve25519-donna implementations by Adam Langley, or it
2492 can link against the "nacl" library for a tuned version if present.
2494 The built-in version is very fast for 64-bit systems when building
2495 with GCC. The built-in 32-bit version is still faster than the
2496 old TAP protocol, but using libnacl is better on most such hosts.
2498 Clients don't currently use this protocol by default, since
2499 comparatively few clients support it so far. To try it, set
2500 UseNTorHandshake to 1.
2502 Implements proposal 216; closes ticket 7202.
2504 o Major features (better link encryption):
2505 - Relays can now enable the ECDHE TLS ciphersuites when available
2506 and appropriate. These ciphersuites let us negotiate forward-secure
2507 TLS secret keys more safely and more efficiently than with our
2508 previous use of Diffie-Hellman modulo a 1024-bit prime. By default,
2509 public relays prefer the (faster) P224 group, and bridges prefer
2510 the (more common) P256 group; you can override this with the
2513 Enabling these ciphers was a little tricky, since for a long time,
2514 clients had been claiming to support them without actually doing
2515 so, in order to foil fingerprinting. But with the client-side
2516 implementation of proposal 198 in 0.2.3.17-beta, clients can now
2517 match the ciphers from recent Firefox versions *and* list the
2518 ciphers they actually mean, so relays can believe such clients
2519 when they advertise ECDHE support in their TLS ClientHello messages.
2521 This feature requires clients running 0.2.3.17-beta or later,
2522 and requires both sides to be running OpenSSL 1.0.0 or later
2523 with ECC support. OpenSSL 1.0.1, with the compile-time option
2524 "enable-ec_nistp_64_gcc_128", is highly recommended.
2526 Implements the relay side of proposal 198; closes ticket 7200.
2529 - Avoid crashing when, as a relay without IPv6-exit support, a
2530 client insists on getting an IPv6 address or nothing. Fixes bug
2531 7814; bugfix on 0.2.4.7-alpha.
2534 - Improve circuit build timeout handling for hidden services.
2535 In particular: adjust build timeouts more accurately depending
2536 upon the number of hop-RTTs that a particular circuit type
2537 undergoes. Additionally, launch intro circuits in parallel
2538 if they timeout, and take the first one to reply as valid.
2539 - Work correctly on Unix systems where EAGAIN and EWOULDBLOCK are
2540 separate error codes; or at least, don't break for that reason.
2541 Fixes bug 7935. Reported by "oftc_must_be_destroyed".
2542 - Update to the January 2 2013 Maxmind GeoLite Country database.
2544 o Minor features (testing):
2545 - Add benchmarks for DH (1024-bit multiplicative group) and ECDH
2546 (P-256) Diffie-Hellman handshakes to src/or/bench.
2547 - Add benchmark functions to test onion handshake performance.
2549 o Minor features (path bias detection):
2550 - Alter the Path Bias log messages to be more descriptive in terms
2551 of reporting timeouts and other statistics.
2552 - Create three levels of Path Bias log messages, as opposed to just
2553 two. These are configurable via consensus as well as via the torrc
2554 options PathBiasNoticeRate, PathBiasWarnRate, PathBiasExtremeRate.
2555 The default values are 0.70, 0.50, and 0.30 respectively.
2556 - Separate the log message levels from the decision to drop guards,
2557 which also is available via torrc option PathBiasDropGuards.
2558 PathBiasDropGuards still defaults to 0 (off).
2559 - Deprecate PathBiasDisableRate in favor of PathBiasDropGuards
2560 in combination with PathBiasExtremeRate.
2561 - Increase the default values for PathBiasScaleThreshold and
2562 PathBiasCircThreshold from (200, 20) to (300, 150).
2563 - Add in circuit usage accounting to path bias. If we try to use a
2564 built circuit but fail for any reason, it counts as path bias.
2565 Certain classes of circuits where the adversary gets to pick your
2566 destination node are exempt from this accounting. Usage accounting
2567 can be specifically disabled via consensus parameter or torrc.
2568 - Convert all internal path bias state to double-precision floating
2569 point, to avoid roundoff error and other issues.
2570 - Only record path bias information for circuits that have completed
2571 *two* hops. Assuming end-to-end tagging is the attack vector, this
2572 makes us more resilient to ambient circuit failure without any
2573 detection capability loss.
2575 o Minor bugfixes (log messages):
2576 - Rate-limit the "No circuits are opened. Relaxed timeout for a
2577 circuit with channel state open..." message to once per hour to
2578 keep it from filling the notice logs. Mitigates bug 7799 but does
2579 not fix the underlying cause. Bugfix on 0.2.4.7-alpha.
2580 - Avoid spurious warnings when configuring multiple client ports of
2581 which only some are nonlocal. Previously, we had claimed that some
2582 were nonlocal when in fact they weren't. Fixes bug 7836; bugfix on
2585 o Code simplifications and refactoring:
2586 - Get rid of a couple of harmless clang warnings, where we compared
2587 enums to ints. These warnings are newly introduced in clang 3.2.
2588 - Split the onion.c file into separate modules for the onion queue
2589 and the different handshakes it supports.
2590 - Remove the marshalling/unmarshalling code for sending requests to
2591 cpuworkers over a socket, and instead just send structs. The
2592 recipient will always be the same Tor binary as the sender, so
2593 any encoding is overkill.
2596 Changes in version 0.2.4.7-alpha - 2012-12-24
2597 Tor 0.2.4.7-alpha introduces a new approach to providing fallback
2598 directory mirrors for more robust bootstrapping; fixes more issues where
2599 clients with changing network conditions refuse to make any circuits;
2600 adds initial support for exiting to IPv6 addresses; resumes being able
2601 to update our GeoIP database, and includes the geoip6 file this time;
2602 turns off the client-side DNS cache by default due to privacy risks;
2603 and fixes a variety of other issues.
2605 o Major features (client resilience):
2606 - Add a new "FallbackDir" torrc option to use when we can't use
2607 a directory mirror from the consensus (either because we lack a
2608 consensus, or because they're all down). Currently, all authorities
2609 are fallbacks by default, and there are no other default fallbacks,
2610 but that will change. This option will allow us to give clients a
2611 longer list of servers to try to get a consensus from when first
2612 connecting to the Tor network, and thereby reduce load on the
2613 directory authorities. Implements proposal 206, "Preconfigured
2614 directory sources for bootstrapping". We also removed the old
2615 "FallbackNetworkstatus" option, since we never got it working well
2616 enough to use it. Closes bug 572.
2617 - If we have no circuits open, use a relaxed timeout (the
2618 95-percentile cutoff) until a circuit succeeds. This heuristic
2619 should allow Tor to succeed at building circuits even when the
2620 network connection drastically changes. Should help with bug 3443.
2622 o Major features (IPv6):
2623 - Relays can now exit to IPv6 addresses: make sure that you have IPv6
2624 connectivity, then set the IPv6Exit flag to 1. Also make sure your
2625 exit policy reads as you would like: the address * applies to all
2626 address families, whereas *4 is IPv4 address only, and *6 is IPv6
2627 addresses only. On the client side, you'll need to wait until the
2628 authorities have upgraded, wait for enough exits to support IPv6,
2629 apply the "IPv6Traffic" flag to a SocksPort, and use Socks5. Closes
2630 ticket 5547, implements proposal 117 as revised in proposal 208.
2632 We DO NOT recommend that clients with actual anonymity needs start
2633 using IPv6 over Tor yet, since not enough exits support it yet.
2635 o Major features (geoip database):
2636 - Maxmind began labelling Tor relays as being in country "A1",
2637 which breaks by-country node selection inside Tor. Now we use a
2638 script to replace "A1" ("Anonymous Proxy") entries in our geoip
2639 file with real country codes. This script fixes about 90% of "A1"
2640 entries automatically and uses manual country code assignments to
2641 fix the remaining 10%. See src/config/README.geoip for details.
2642 Fixes bug 6266. Also update to the December 5 2012 Maxmind GeoLite
2643 Country database, as modified above.
2645 o Major bugfixes (client-side DNS):
2646 - Turn off the client-side DNS cache by default. Updating and using
2647 the DNS cache is now configurable on a per-client-port
2648 level. SOCKSPort, DNSPort, etc lines may now contain
2649 {No,}Cache{IPv4,IPv6,}DNS lines to indicate that we shouldn't
2650 cache these types of DNS answers when we receive them from an
2651 exit node in response to an application request on this port, and
2652 {No,}UseCached{IPv4,IPv6,DNS} lines to indicate that if we have
2653 cached DNS answers of these types, we shouldn't use them. It's
2654 potentially risky to use cached DNS answers at the client, since
2655 doing so can indicate to one exit what answers we've gotten
2656 for DNS lookups in the past. With IPv6, this becomes especially
2657 problematic. Using cached DNS answers for requests on the same
2658 circuit would present less linkability risk, since all traffic
2659 on a circuit is already linkable, but it would also provide
2660 little performance benefit: the exit node caches DNS replies
2661 too. Implements a simplified version of Proposal 205. Implements
2664 o Major bugfixes (other):
2665 - Alter circuit build timeout measurement to start at the point
2666 where we begin the CREATE/CREATE_FAST step (as opposed to circuit
2667 initialization). This should make our timeout measurements more
2668 uniform. Previously, we were sometimes including ORconn setup time
2669 in our circuit build time measurements. Should resolve bug 3443.
2670 - Fix an assertion that could trigger in hibernate_go_dormant() when
2671 closing an or_connection_t: call channel_mark_for_close() rather
2672 than connection_mark_for_close(). Fixes bug 7267. Bugfix on
2674 - Include the geoip6 IPv6 GeoIP database in the tarball. Fixes bug
2675 7655; bugfix on 0.2.4.6-alpha.
2678 - Add a new torrc option "ServerTransportListenAddr" to let bridge
2679 operators select the address where their pluggable transports will
2680 listen for connections. Resolves ticket 7013.
2681 - Allow an optional $ before the node identity digest in the
2682 controller command GETINFO ns/id/<identity>, for consistency with
2683 md/id/<identity> and desc/id/<identity>. Resolves ticket 7059.
2684 - Log packaged cell fullness as part of the heartbeat message.
2685 Diagnosis to try to determine the extent of bug 7743.
2687 o Minor features (IPv6):
2688 - AutomapHostsOnResolve now supports IPv6 addresses. By default, we
2689 prefer to hand out virtual IPv6 addresses, since there are more of
2690 them and we can't run out. To override this behavior and make IPv4
2691 addresses preferred, set NoPreferIPv6Automap on whatever SOCKSPort
2692 or DNSPort you're using for resolving. Implements ticket 7571.
2693 - AutomapHostsOnResolve responses are now randomized, to avoid
2694 annoying situations where Tor is restarted and applications
2695 connect to the wrong addresses.
2696 - Never try more than 1000 times to pick a new virtual address when
2697 AutomapHostsOnResolve is set. That's good enough so long as we
2698 aren't close to handing out our entire virtual address space;
2699 if you're getting there, it's best to switch to IPv6 virtual
2703 - The ADDRMAP command can no longer generate an ill-formed error
2704 code on a failed MAPADDRESS. It now says "internal" rather than
2705 an English sentence fragment with spaces in the middle. Bugfix on
2707 - Fix log messages and comments to avoid saying "GMT" when we mean
2708 "UTC". Fixes bug 6113.
2709 - Compile on win64 using mingw64. Fixes bug 7260; patches from
2711 - Fix a crash when debugging unit tests on Windows: deallocate a
2712 shared library with FreeLibrary, not CloseHandle. Fixes bug 7306;
2713 bugfix on 0.2.2.17-alpha. Reported by "ultramage".
2716 - The DirServer option is now DirAuthority, for consistency with
2717 current naming patterns. You can still use the old DirServer form.
2719 o Code simplification and refactoring:
2720 - Move the client-side address-map/virtual-address/DNS-cache code
2721 out of connection_edge.c into a new addressmap.c module.
2722 - Remove unused code for parsing v1 directories and "running routers"
2723 documents. Fixes bug 6887.
2726 Changes in version 0.2.3.25 - 2012-11-19
2727 The Tor 0.2.3 release series is dedicated to the memory of Len "rabbi"
2728 Sassaman (1980-2011), a long-time cypherpunk, anonymity researcher,
2729 Mixmaster maintainer, Pynchon Gate co-designer, CodeCon organizer,
2730 programmer, and friend. Unstinting in his dedication to the cause of
2731 freedom, he inspired and helped many of us as we began our work on
2732 anonymity, and inspires us still. Please honor his memory by writing
2733 software to protect people's freedoms, and by helping others to do so.
2735 Tor 0.2.3.25, the first stable release in the 0.2.3 branch, features
2736 significantly reduced directory overhead (via microdescriptors),
2737 enormous crypto performance improvements for fast relays on new
2738 enough hardware, a new v3 TLS handshake protocol that can better
2739 resist fingerprinting, support for protocol obfuscation plugins (aka
2740 pluggable transports), better scalability for hidden services, IPv6
2741 support for bridges, performance improvements like allowing clients
2742 to skip the first round-trip on the circuit ("optimistic data") and
2743 refilling token buckets more often, a new "stream isolation" design
2744 to isolate different applications on different circuits, and many
2745 stability, security, and privacy fixes.
2748 - Tor tries to wipe potentially sensitive data after using it, so
2749 that if some subsequent security failure exposes Tor's memory,
2750 the damage will be limited. But we had a bug where the compiler
2751 was eliminating these wipe operations when it decided that the
2752 memory was no longer visible to a (correctly running) program,
2753 hence defeating our attempt at defense in depth. We fix that
2754 by using OpenSSL's OPENSSL_cleanse() operation, which a compiler
2755 is unlikely to optimize away. Future versions of Tor may use
2756 a less ridiculously heavy approach for this. Fixes bug 7352.
2757 Reported in an article by Andrey Karpov.
2760 - Fix a harmless bug when opting against publishing a relay descriptor
2761 because DisableNetwork is set. Fixes bug 7464; bugfix on
2765 Changes in version 0.2.4.6-alpha - 2012-11-13
2766 Tor 0.2.4.6-alpha fixes an assert bug that has been plaguing relays,
2767 makes our defense-in-depth memory wiping more reliable, and begins to
2768 count IPv6 addresses in bridge statistics,
2771 - Fix an assertion failure that could occur when closing a connection
2772 with a spliced rendezvous circuit. Fix for bug 7212; bugfix on
2774 - Tor tries to wipe potentially sensitive data after using it, so
2775 that if some subsequent security failure exposes Tor's memory,
2776 the damage will be limited. But we had a bug where the compiler
2777 was eliminating these wipe operations when it decided that the
2778 memory was no longer visible to a (correctly running) program,
2779 hence defeating our attempt at defense in depth. We fix that
2780 by using OpenSSL's OPENSSL_cleanse() operation, which a compiler
2781 is unlikely to optimize away. Future versions of Tor may use
2782 a less ridiculously heavy approach for this. Fixes bug 7352.
2783 Reported in an article by Andrey Karpov.
2786 - Add GeoIP database for IPv6 addresses. The new config option
2788 - Bridge statistics now count bridge clients connecting over IPv6:
2789 bridge statistics files now list "bridge-ip-versions" and
2790 extra-info documents list "geoip6-db-digest". The control protocol
2791 "CLIENTS_SEEN" and "ip-to-country" queries now support IPv6. Initial
2792 implementation by "shkoo", addressing ticket 5055.
2795 - Warn when we are binding low ports when hibernation is enabled;
2796 previously we had warned when we were _advertising_ low ports with
2797 hibernation enabled. Fixes bug 7285; bugfix on 0.2.3.9-alpha.
2798 - Fix a harmless bug when opting against publishing a relay descriptor
2799 because DisableNetwork is set. Fixes bug 7464; bugfix on
2801 - Add warning message when a managed proxy dies during configuration.
2802 Fixes bug 7195; bugfix on 0.2.4.2-alpha.
2803 - Fix a linking error when building tor-fw-helper without miniupnp.
2804 Fixes bug 7235; bugfix on 0.2.4.2-alpha. Fix by Anthony G. Basile.
2805 - Check for closing an or_connection_t without going through correct
2806 channel functions; emit a warning and then call
2807 connection_or_close_for_error() so we don't assert as in bugs 7212
2809 - Compile correctly on compilers without C99 designated initializer
2810 support. Fixes bug 7286; bugfix on 0.2.4.4-alpha.
2811 - Avoid a possible assert that can occur when channel_send_destroy() is
2812 called on a channel in CHANNEL_STATE_CLOSING, CHANNEL_STATE_CLOSED,
2813 or CHANNEL_STATE_ERROR when the Tor process is resumed after being
2814 blocked for a long interval. Fixes bug 7350; bugfix on 0.2.4.4-alpha.
2815 - Fix a memory leak on failing cases of channel_tls_process_certs_cell.
2816 Fixes bug 7422; bugfix on 0.2.4.4-alpha.
2818 o Code simplification and refactoring:
2819 - Start using OpenBSD's implementation of queue.h, so that we don't
2820 need to hand-roll our own pointer and list structures whenever we
2821 need them. (We can't rely on a sys/queue.h, since some operating
2822 systems don't have them, and the ones that do have them don't all
2823 present the same extensions.)
2826 Changes in version 0.2.4.5-alpha - 2012-10-25
2827 Tor 0.2.4.5-alpha comes hard at the heels of 0.2.4.4-alpha, to fix
2828 two important security vulnerabilities that could lead to remotely
2829 triggerable relay crashes, fix a major bug that was preventing clients
2830 from choosing suitable exit nodes, and refactor some of our code.
2832 o Major bugfixes (security, also in 0.2.3.24-rc):
2833 - Fix a group of remotely triggerable assertion failures related to
2834 incorrect link protocol negotiation. Found, diagnosed, and fixed
2835 by "some guy from France". Fix for CVE-2012-2250; bugfix on
2837 - Fix a denial of service attack by which any directory authority
2838 could crash all the others, or by which a single v2 directory
2839 authority could crash everybody downloading v2 directory
2840 information. Fixes bug 7191; bugfix on 0.2.0.10-alpha.
2842 o Major bugfixes (also in 0.2.3.24-rc):
2843 - When parsing exit policy summaries from microdescriptors, we had
2844 previously been ignoring the last character in each one, so that
2845 "accept 80,443,8080" would be treated by clients as indicating
2846 a node that allows access to ports 80, 443, and 808. That would
2847 lead to clients attempting connections that could never work,
2848 and ignoring exit nodes that would support their connections. Now
2849 clients parse these exit policy summaries correctly. Fixes bug 7192;
2850 bugfix on 0.2.3.1-alpha.
2852 o Minor bugfixes (also in 0.2.3.24-rc):
2853 - Clients now consider the ClientRejectInternalAddresses config option
2854 when using a microdescriptor consensus stanza to decide whether
2855 an exit relay would allow exiting to an internal address. Fixes
2856 bug 7190; bugfix on 0.2.3.1-alpha.
2859 - Only disable TLS session ticket support when running as a TLS
2860 server. Now clients will blend better with regular Firefox
2861 connections. Fixes bug 7189; bugfix on Tor 0.2.3.23-rc.
2863 o Code simplification and refactoring:
2864 - Start using OpenBSD's implementation of queue.h (originally by
2866 - Move the entry node code from circuitbuild.c to its own file.
2867 - Move the circuit build timeout tracking code from circuitbuild.c
2871 Changes in version 0.2.3.24-rc - 2012-10-25
2872 Tor 0.2.3.24-rc fixes two important security vulnerabilities that
2873 could lead to remotely triggerable relay crashes, and fixes
2874 a major bug that was preventing clients from choosing suitable exit
2877 o Major bugfixes (security):
2878 - Fix a group of remotely triggerable assertion failures related to
2879 incorrect link protocol negotiation. Found, diagnosed, and fixed
2880 by "some guy from France". Fix for CVE-2012-2250; bugfix on
2882 - Fix a denial of service attack by which any directory authority
2883 could crash all the others, or by which a single v2 directory
2884 authority could crash everybody downloading v2 directory
2885 information. Fixes bug 7191; bugfix on 0.2.0.10-alpha.
2888 - When parsing exit policy summaries from microdescriptors, we had
2889 previously been ignoring the last character in each one, so that
2890 "accept 80,443,8080" would be treated by clients as indicating
2891 a node that allows access to ports 80, 443, and 808. That would
2892 lead to clients attempting connections that could never work,
2893 and ignoring exit nodes that would support their connections. Now
2894 clients parse these exit policy summaries correctly. Fixes bug 7192;
2895 bugfix on 0.2.3.1-alpha.
2898 - Clients now consider the ClientRejectInternalAddresses config option
2899 when using a microdescriptor consensus stanza to decide whether
2900 an exit relay would allow exiting to an internal address. Fixes
2901 bug 7190; bugfix on 0.2.3.1-alpha.
2904 Changes in version 0.2.4.4-alpha - 2012-10-20
2905 Tor 0.2.4.4-alpha adds a new v3 directory authority, fixes a privacy
2906 vulnerability introduced by a change in OpenSSL, fixes a remotely
2907 triggerable assert, and adds new channel_t and circuitmux_t abstractions
2908 that will make it easier to test new connection transport and cell
2909 scheduling algorithms.
2911 o New directory authorities (also in 0.2.3.23-rc):
2912 - Add Faravahar (run by Sina Rabbani) as the ninth v3 directory
2913 authority. Closes ticket 5749.
2915 o Major bugfixes (security/privacy, also in 0.2.3.23-rc):
2916 - Disable TLS session tickets. OpenSSL's implementation was giving
2917 our TLS session keys the lifetime of our TLS context objects, when
2918 perfect forward secrecy would want us to discard anything that
2919 could decrypt a link connection as soon as the link connection
2920 was closed. Fixes bug 7139; bugfix on all versions of Tor linked
2921 against OpenSSL 1.0.0 or later. Found by Florent Daignière.
2922 - Discard extraneous renegotiation attempts once the V3 link
2923 protocol has been initiated. Failure to do so left us open to
2924 a remotely triggerable assertion failure. Fixes CVE-2012-2249;
2925 bugfix on 0.2.3.6-alpha. Reported by "some guy from France".
2927 o Internal abstraction features:
2928 - Introduce new channel_t abstraction between circuits and
2929 or_connection_t to allow for implementing alternate OR-to-OR
2930 transports. A channel_t is an abstract object which can either be a
2931 cell-bearing channel, which is responsible for authenticating and
2932 handshaking with the remote OR and transmitting cells to and from
2933 it, or a listening channel, which spawns new cell-bearing channels
2934 at the request of remote ORs. Implements part of ticket 6465.
2935 - Also new is the channel_tls_t subclass of channel_t, adapting it
2936 to the existing or_connection_t code. The V2/V3 protocol handshaking
2937 code which formerly resided in command.c has been moved below the
2938 channel_t abstraction layer and may be found in channeltls.c now.
2939 Implements the rest of ticket 6465.
2940 - Introduce new circuitmux_t storing the queue of circuits for
2941 a channel; this encapsulates and abstracts the queue logic and
2942 circuit selection policy, and allows the latter to be overridden
2943 easily by switching out a policy object. The existing EWMA behavior
2944 is now implemented as a circuitmux_policy_t. Resolves ticket 6816.
2946 o Required libraries:
2947 - Tor now requires OpenSSL 0.9.8 or later. OpenSSL 1.0.0 or later is
2948 strongly recommended.
2951 - Warn users who run hidden services on a Tor client with
2952 UseEntryGuards disabled that their hidden services will be
2953 vulnerable to http://freehaven.net/anonbib/#hs-attack06 (the
2954 attack which motivated Tor to support entry guards in the first
2955 place). Resolves ticket 6889.
2956 - Tor now builds correctly on Bitrig, an OpenBSD fork. Patch from
2957 dhill. Resolves ticket 6982.
2958 - Option OutboundBindAddress can be specified multiple times and
2959 accepts IPv6 addresses. Resolves ticket 6876.
2961 o Minor bugfixes (also in 0.2.3.23-rc):
2962 - Don't serve or accept v2 hidden service descriptors over a
2963 relay's DirPort. It's never correct to do so, and disabling it
2964 might make it more annoying to exploit any bugs that turn up in the
2965 descriptor-parsing code. Fixes bug 7149.
2966 - Fix two cases in src/or/transports.c where we were calling
2967 fmt_addr() twice in a parameter list. Bug found by David
2968 Fifield. Fixes bug 7014; bugfix on 0.2.3.9-alpha.
2969 - Fix memory leaks whenever we logged any message about the "path
2970 bias" detection. Fixes bug 7022; bugfix on 0.2.3.21-rc.
2971 - When relays refuse a "create" cell because their queue of pending
2972 create cells is too big (typically because their cpu can't keep up
2973 with the arrival rate), send back reason "resource limit" rather
2974 than reason "internal", so network measurement scripts can get a
2975 more accurate picture. Fixes bug 7037; bugfix on 0.1.1.11-alpha.
2978 - Command-line option "--version" implies "--quiet". Fixes bug 6997.
2979 - Free some more still-in-use memory at exit, to make hunting for
2980 memory leaks easier. Resolves bug 7029.
2981 - When a Tor client gets a "truncated" relay cell, the first byte of
2982 its payload specifies why the circuit was truncated. We were
2983 ignoring this 'reason' byte when tearing down the circuit, resulting
2984 in the controller not being told why the circuit closed. Now we
2985 pass the reason from the truncated cell to the controller. Bugfix
2986 on 0.1.2.3-alpha; fixes bug 7039.
2987 - Downgrade "Failed to hand off onionskin" messages to "debug"
2988 severity, since they're typically redundant with the "Your computer
2989 is too slow" messages. Fixes bug 7038; bugfix on 0.2.2.16-alpha.
2990 - Make clients running with IPv6 bridges connect over IPv6 again,
2991 even without setting new config options ClientUseIPv6 and
2992 ClientPreferIPv6ORPort. Fixes bug 6757; bugfix on 0.2.4.1-alpha.
2993 - Use square brackets around IPv6 addresses in numerous places
2994 that needed them, including log messages, HTTPS CONNECT proxy
2995 requests, TransportProxy statefile entries, and pluggable transport
2996 extra-info lines. Fixes bug 7011; patch by David Fifield.
2998 o Code refactoring and cleanup:
2999 - Source files taken from other packages now reside in src/ext;
3000 previously they were scattered around the rest of Tor.
3001 - Avoid use of reserved identifiers in our C code. The C standard
3002 doesn't like us declaring anything that starts with an
3003 underscore, so let's knock it off before we get in trouble. Fix
3004 for bug 1031; bugfix on the first Tor commit.
3007 Changes in version 0.2.3.23-rc - 2012-10-20
3008 Tor 0.2.3.23-rc adds a new v3 directory authority, fixes a privacy
3009 vulnerability introduced by a change in OpenSSL, and fixes a variety
3010 of smaller bugs in preparation for the release.
3012 o New directory authorities:
3013 - Add Faravahar (run by Sina Rabbani) as the ninth v3 directory
3014 authority. Closes ticket 5749.
3016 o Major bugfixes (security/privacy):
3017 - Disable TLS session tickets. OpenSSL's implementation was giving
3018 our TLS session keys the lifetime of our TLS context objects, when
3019 perfect forward secrecy would want us to discard anything that
3020 could decrypt a link connection as soon as the link connection
3021 was closed. Fixes bug 7139; bugfix on all versions of Tor linked
3022 against OpenSSL 1.0.0 or later. Found by Florent Daignière.
3023 - Discard extraneous renegotiation attempts once the V3 link
3024 protocol has been initiated. Failure to do so left us open to
3025 a remotely triggerable assertion failure. Fixes CVE-2012-2249;
3026 bugfix on 0.2.3.6-alpha. Reported by "some guy from France".
3029 - Fix a possible crash bug when checking for deactivated circuits
3030 in connection_or_flush_from_first_active_circuit(). Fixes bug 6341;
3031 bugfix on 0.2.2.7-alpha. Bug report and fix received pseudonymously.
3033 o Minor bugfixes (on 0.2.3.x):
3034 - Fix two cases in src/or/transports.c where we were calling
3035 fmt_addr() twice in a parameter list. Bug found by David
3036 Fifield. Fixes bug 7014; bugfix on 0.2.3.9-alpha.
3037 - Convert an assert in the pathbias code to a log message. The assert
3038 appears to only be triggerable by Tor2Web mode. Fixes bug 6866;
3039 bugfix on 0.2.3.17-beta.
3040 - Fix memory leaks whenever we logged any message about the "path
3041 bias" detection. Fixes bug 7022; bugfix on 0.2.3.21-rc.
3043 o Minor bugfixes (on 0.2.2.x and earlier):
3044 - Don't serve or accept v2 hidden service descriptors over a relay's
3045 DirPort. It's never correct to do so, and disabling it might
3046 make it more annoying to exploit any bugs that turn up in the
3047 descriptor-parsing code. Fixes bug 7149.
3048 - When relays refuse a "create" cell because their queue of pending
3049 create cells is too big (typically because their cpu can't keep up
3050 with the arrival rate), send back reason "resource limit" rather
3051 than reason "internal", so network measurement scripts can get a
3052 more accurate picture. Bugfix on 0.1.1.11-alpha; fixes bug 7037.
3053 - Correct file sizes when reading binary files on Cygwin, to avoid
3054 a bug where Tor would fail to read its state file. Fixes bug 6844;
3055 bugfix on 0.1.2.7-alpha.
3056 - Avoid undefined behaviour when parsing the list of supported
3057 rendezvous/introduction protocols in a hidden service descriptor.
3058 Previously, Tor would have confused (as-yet-unused) protocol version
3059 numbers greater than 32 with lower ones on many platforms. Fixes
3060 bug 6827; bugfix on 0.2.0.10-alpha. Found by George Kadianakis.
3062 o Documentation fixes:
3063 - Clarify that hidden services are TCP only. Fixes bug 6024.
3066 Changes in version 0.2.4.3-alpha - 2012-09-22
3067 Tor 0.2.4.3-alpha fixes another opportunity for a remotely triggerable
3068 assertion, resumes letting relays test reachability of their DirPort,
3069 and cleans up a bunch of smaller bugs.
3072 - Fix an assertion failure in tor_timegm() that could be triggered
3073 by a badly formatted directory object. Bug found by fuzzing with
3074 Radamsa. Fixes bug 6811; bugfix on 0.2.0.20-rc.
3077 - Fix a possible crash bug when checking for deactivated circuits
3078 in connection_or_flush_from_first_active_circuit(). Fixes bug 6341;
3079 bugfix on 0.2.2.7-alpha. Bug report and fix received pseudonymously.
3080 - Allow routers to detect that their own DirPorts are running. When
3081 we removed support for versions_supports_begindir, we also
3082 accidentally removed the mechanism we used to self-test our
3083 DirPort. Diagnosed with help from kargig. Fixes bugs 6814 and 6815;
3084 bugfix on 0.2.4.2-alpha.
3086 o Security features:
3087 - Switch to a completely time-invariant approach for picking nodes
3088 weighted by bandwidth. Our old approach would run through the
3089 part of the loop after it had made its choice slightly slower
3090 than it ran through the part of the loop before it had made its
3091 choice. Addresses ticket 6538.
3092 - Disable the use of Guard nodes when in Tor2WebMode. Guard usage
3093 by tor2web clients allows hidden services to identify tor2web
3094 clients through their repeated selection of the same rendezvous
3095 and introduction point circuit endpoints (their guards). Resolves
3099 - Enable Tor to read configuration, state, and key information from
3100 a FIFO. Previously Tor would only read from files with a positive
3101 stat.st_size. Code from meejah; fixes bug 6044.
3104 - Correct file sizes when reading binary files on Cygwin, to avoid
3105 a bug where Tor would fail to read its state file. Fixes bug 6844;
3106 bugfix on 0.1.2.7-alpha.
3107 - Correctly handle votes with more than 31 flags. Fixes bug 6853;
3108 bugfix on 0.2.0.3-alpha.
3109 - When complaining about a client port on a public address, log
3110 which address we're complaining about. Fixes bug 4020; bugfix on
3111 0.2.3.3-alpha. Patch by Tom Fitzhenry.
3112 - Convert an assert in the pathbias code to a log message. The assert
3113 appears to only be triggerable by Tor2Web mode. Fixes bug 6866;
3114 bugfix on 0.2.3.17-beta.
3115 - Our new buildsystem was overzealous about rebuilding manpages: it
3116 would rebuild them all whenever any one of them changed. Now our
3117 dependency checking should be correct. Fixes bug 6843; bugfix on
3119 - Don't do reachability testing over IPv6 unless AuthDirPublishIPv6
3120 is set. Fixes bug 6880. Bugfix on 0.2.4.1-alpha.
3121 - Correct log printout about which address family is preferred
3122 when connecting to a bridge with both an IPv4 and IPv6 OR port.
3123 Fixes bug 6884; bugfix on 0.2.4.1-alpha.
3125 o Minor bugfixes (code cleanliness):
3126 - Fix round_to_power_of_2() so it doesn't invoke undefined behavior
3127 with large values. This situation was untriggered, but nevertheless
3128 incorrect. Fixes bug 6831; bugfix on 0.2.0.1-alpha.
3129 - Reject consensus votes with more than 64 known-flags. We aren't even
3130 close to that limit yet, and our code doesn't handle it correctly.
3131 Fixes bug 6833; bugfix on 0.2.0.1-alpha.
3132 - Avoid undefined behaviour when parsing the list of supported
3133 rendezvous/introduction protocols in a hidden service descriptor.
3134 Previously, Tor would have confused (as-yet-unused) protocol version
3135 numbers greater than 32 with lower ones on many platforms. Fixes
3136 bug 6827; bugfix on 0.2.0.10-alpha. Found by George Kadianakis.
3137 - Fix handling of rendezvous client authorization types over 8.
3138 Fixes bug 6861; bugfix on 0.2.1.5-alpha.
3139 - Fix building with older versions of GCC (2.95, for one) that don't
3140 like preprocessor directives inside macro arguments. Found by
3141 grarpamp. Fixes bug 6842; bugfix on 0.2.4.2-alpha.
3142 - Switch weighted node selection rule from using a list of doubles
3143 to using a list of int64_t. This change should make the process
3144 slightly easier to debug and maintain. Needed to finish ticket 6538.
3146 o Code simplification and refactoring:
3147 - Move the generic "config" code into a new file, and have "config.c"
3148 hold only torrc- and state-related code. Resolves ticket 6823.
3149 - Move the core of our "choose a weighted element at random" logic
3150 into its own function, and give it unit tests. Now the logic is
3151 testable, and a little less fragile too.
3152 - Removed the testing_since field of node_t, which hasn't been used
3153 for anything since 0.2.0.9-alpha.
3155 o Documentation fixes:
3156 - Clarify that hidden services are TCP only. Fixes bug 6024.
3157 - Resolve a typo in torrc.sample.in. Fixes bug 6819; bugfix on
3161 Changes in version 0.2.3.22-rc - 2012-09-11
3162 Tor 0.2.3.22-rc fixes another opportunity for a remotely triggerable
3166 - Fix an assertion failure in tor_timegm() that could be triggered
3167 by a badly formatted directory object. Bug found by fuzzing with
3168 Radamsa. Fixes bug 6811; bugfix on 0.2.0.20-rc.
3171 - Avoid segfault when starting up having run with an extremely old
3172 version of Tor and parsing its state file. Fixes bug 6801; bugfix
3176 Changes in version 0.2.2.39 - 2012-09-11
3177 Tor 0.2.2.39 fixes two more opportunities for remotely triggerable
3181 - Fix an assertion failure in tor_timegm() that could be triggered
3182 by a badly formatted directory object. Bug found by fuzzing with
3183 Radamsa. Fixes bug 6811; bugfix on 0.2.0.20-rc.
3184 - Do not crash when comparing an address with port value 0 to an
3185 address policy. This bug could have been used to cause a remote
3186 assertion failure by or against directory authorities, or to
3187 allow some applications to crash clients. Fixes bug 6690; bugfix
3191 Changes in version 0.2.4.2-alpha - 2012-09-10
3192 Tor 0.2.4.2-alpha enables port forwarding for pluggable transports,
3193 raises the default rate limiting even more, and makes the bootstrapping
3194 log messages less noisy.
3197 - Automatically forward the TCP ports of pluggable transport
3198 proxies using tor-fw-helper if PortForwarding is enabled. Implements
3202 - Raise the default BandwidthRate/BandwidthBurst values from 5MB/10MB
3203 to 1GB/1GB. The previous defaults were intended to be "basically
3204 infinite", but it turns out they're now limiting our 100mbit+
3205 relays and bridges. Fixes bug 6605; bugfix on 0.2.0.10-alpha (the
3206 last time we raised it).
3209 - Detect when we're running with a version of OpenSSL other than the
3210 one we compiled with. This has occasionally given people hard-to-
3212 - Log fewer lines at level "notice" about our OpenSSL and Libevent
3213 versions and capabilities when everything is going right. Resolves
3214 part of ticket 6736.
3215 - Directory authorities no long accept descriptors for any version of
3216 Tor before 0.2.2.35, or for any 0.2.3 release before 0.2.3.10-alpha.
3217 These versions are insecure, unsupported, or both. Implements
3221 - Rename the (internal-use-only) UsingTestingNetworkDefaults option
3222 to start with a triple-underscore so the controller won't touch it.
3223 Patch by Meejah. Fixes bug 3155. Bugfix on 0.2.2.23-alpha.
3224 - Avoid segfault when starting up having run with an extremely old
3225 version of Tor and parsing its state file. Fixes bug 6801; bugfix
3227 - Rename the (testing-use-only) _UseFilteringSSLBufferevents option
3228 so it doesn't start with _. Fixes bug 3155. Bugfix on 0.2.3.1-alpha.
3229 - Don't follow the NULL pointer if microdescriptor generation fails.
3230 (This does not appear to be triggerable, but it's best to be safe.)
3231 Found by "f. tp.". Fixes bug 6797; bugfix on 0.2.4.1-alpha.
3232 - Fix mis-declared dependencies on src/common/crypto.c and
3233 src/or/tor_main.c that could break out-of-tree builds under some
3234 circumstances. Fixes bug 6778; bugfix on 0.2.4.1-alpha.
3235 - Avoid a warning when building common_sha1.i out of tree. Fixes bug
3236 6778; bugfix on 0.2.4.1-alpha.
3237 - Fix a harmless (in this case) build warning for implicitly
3238 converting a strlen() to an int. Bugfix on 0.2.4.1-alpha.
3241 - Now that all versions before 0.2.2.x are disallowed, we no longer
3242 need to work around their missing features. Thus we can remove a
3243 bunch of compatibility code.
3246 - Tweak tor-fw-helper to accept an arbitrary amount of arbitrary
3247 TCP ports to forward. In the past it only accepted two ports:
3248 the ORPort and the DirPort.
3251 Changes in version 0.2.4.1-alpha - 2012-09-05
3252 Tor 0.2.4.1-alpha lets bridges publish their pluggable transports to
3253 bridgedb; lets relays use IPv6 addresses and directory authorities
3254 advertise them; and switches to a cleaner build interface.
3256 This is the first alpha release in a new series, so expect there to
3257 be bugs. Users who would rather test out a more stable branch should
3258 stay with 0.2.3.x for now.
3260 o Major features (bridges):
3261 - Bridges now report the pluggable transports they support to the
3262 bridge authority, so it can pass the supported transports on to
3263 bridgedb and/or eventually do reachability testing. Implements
3266 o Major features (IPv6):
3267 - Bridge authorities now accept IPv6 bridge addresses and include
3268 them in network status documents. Implements ticket 5534.
3269 - Clients who set "ClientUseIPv6 1" may connect to entry nodes over
3270 IPv6. Set "ClientPreferIPv6ORPort 1" to make this even more likely
3271 to happen. Implements ticket 5535.
3272 - All kind of relays, not just bridges, can now advertise an IPv6
3273 OR port. Implements ticket 6362.
3274 - Directory authorities vote on IPv6 OR ports using the new consensus
3275 method 14. Implements ticket 6363.
3277 o Major features (build):
3278 - Switch to a nonrecursive Makefile structure. Now instead of each
3279 Makefile.am invoking other Makefile.am's, there is a master
3280 Makefile.am that includes the others. This change makes our build
3281 process slightly more maintainable, and improves parallelism for
3282 building with make -j. Original patch by Stewart Smith; various
3283 fixes by Jim Meyering.
3284 - Where available, we now use automake's "silent" make rules by
3285 default, so that warnings are easier to spot. You can get the old
3286 behavior with "make V=1". Patch by Stewart Smith for ticket 6522.
3288 o Minor features (code security and spec conformance):
3289 - Clear keys and key-derived material left on the stack in
3290 rendservice.c and rendclient.c. Check return value of
3291 crypto_pk_write_private_key_to_string() in rend_service_load_keys().
3292 These fixes should make us more forward-secure against cold-boot
3293 attacks and the like. Fixes bug 2385.
3294 - Reject EXTEND cells sent to nonexistent streams. According to the
3295 spec, an EXTEND cell sent to _any_ nonzero stream ID is invalid, but
3296 we were only checking for stream IDs that were currently in use.
3297 Found while hunting for more instances of bug 6271. Bugfix on
3298 0.0.2pre8, which introduced incremental circuit construction.
3300 o Minor features (streamlining);
3301 - No longer include the "opt" prefix when generating routerinfos
3302 or v2 directories: it has been needless since Tor 0.1.2. Closes
3304 - Remove some now-needless code that tried to aggressively flush
3305 OR connections as data was added to them. Since 0.2.0.1-alpha, our
3306 cell queue logic has saved us from the failure mode that this code
3307 was supposed to prevent. Removing this code will limit the number
3308 of baroque control flow paths through Tor's network logic. Reported
3309 pseudonymously on IRC. Fixes bug 6468; bugfix on 0.2.0.1-alpha.
3311 o Minor features (controller):
3312 - Add a "GETINFO signal/names" control port command. Implements
3314 - Provide default values for all options via "GETINFO config/defaults".
3315 Implements ticket 4971.
3317 o Minor features (IPv6):
3318 - New config option "AuthDirHasIPv6Connectivity 1" that directory
3319 authorities should set if they have IPv6 connectivity and want to
3320 do reachability tests for IPv6 relays. Implements feature 5974.
3321 - A relay with an IPv6 OR port now sends that address in NETINFO
3322 cells (in addition to its other address). Implements ticket 6364.
3324 o Minor features (log messages):
3325 - Omit the first heartbeat log message, because it never has anything
3326 useful to say, and it clutters up the bootstrapping messages.
3327 Resolves ticket 6758.
3328 - Don't log about reloading the microdescriptor cache at startup. Our
3329 bootstrap warnings are supposed to tell the user when there's a
3330 problem, and our bootstrap notices say when there isn't. Resolves
3331 ticket 6759; bugfix on 0.2.2.6-alpha.
3332 - Don't log "I learned some more directory information" when we're
3333 reading cached directory information. Reserve it for when new
3334 directory information arrives in response to a fetch. Resolves
3336 - Prevent rounding error in path bias counts when scaling
3337 them down, and use the correct scale factor default. Also demote
3338 some path bias related log messages down a level and make others
3339 less scary sounding. Fixes bug 6647. Bugfix against 0.2.3.17-beta.
3340 - We no longer warn so much when generating manpages from their
3343 o Code simplifications and refactoring:
3344 - Enhance our internal sscanf replacement so that we can eliminate
3345 the last remaining uses of the system sscanf. (Though those uses
3346 of sscanf were safe, sscanf itself is generally error prone, so
3347 we want to eliminate when we can.) Fixes ticket 4195 and Coverity
3349 - Move ipv6_preferred from routerinfo_t to node_t. Addresses bug 4620.
3350 - Move last_reachable and testing_since from routerinfo_t to node_t.
3351 Implements ticket 5529.
3352 - Add replaycache_t structure, functions and unit tests, then refactor
3353 rend_service_introduce() to be more clear to read, improve, debug,
3354 and test. Resolves bug 6177.
3355 - Finally remove support for malloc_good_size and malloc_usable_size.
3356 We had hoped that these functions would let us eke a little more
3357 memory out of our malloc implementation. Unfortunately, the only
3358 implementations that provided these functions are also ones that
3359 are already efficient about not overallocation: they never got us
3360 more than 7 or so bytes per allocation. Removing them saves us a
3361 little code complexity and a nontrivial amount of build complexity.
3364 - Tor maintainers now require Automake version 1.9 or later to build
3365 Tor from the Git repository. (Automake is not required when building
3366 from a source distribution.)
3369 Changes in version 0.2.3.21-rc - 2012-09-05
3370 Tor 0.2.3.21-rc is the fourth release candidate for the Tor 0.2.3.x
3371 series. It fixes a trio of potential security bugs, fixes a bug where
3372 we were leaving some of the fast relays out of the microdescriptor
3373 consensus, resumes interpreting "ORPort 0" and "DirPort 0" correctly,
3374 and cleans up other smaller issues.
3376 o Major bugfixes (security):
3377 - Tear down the circuit if we get an unexpected SENDME cell. Clients
3378 could use this trick to make their circuits receive cells faster
3379 than our flow control would have allowed, or to gum up the network,
3380 or possibly to do targeted memory denial-of-service attacks on
3381 entry nodes. Fixes bug 6252. Bugfix on the 54th commit on Tor --
3382 from July 2002, before the release of Tor 0.0.0. We had committed
3383 this patch previously, but we had to revert it because of bug 6271.
3384 Now that 6271 is fixed, this patch appears to work.
3385 - Reject any attempt to extend to an internal address. Without
3386 this fix, a router could be used to probe addresses on an internal
3387 network to see whether they were accepting connections. Fixes bug
3388 6710; bugfix on 0.0.8pre1.
3389 - Do not crash when comparing an address with port value 0 to an
3390 address policy. This bug could have been used to cause a remote
3391 assertion failure by or against directory authorities, or to
3392 allow some applications to crash clients. Fixes bug 6690; bugfix
3396 - Remove the upper bound on microdescriptor length. We were hitting
3397 the limit for routers with complex exit policies or family
3398 declarations, causing clients to not use them. Fixes the first
3399 piece of bug 6404; fix on 0.2.2.6-alpha.
3400 - Detect "ORPort 0" as meaning, uniformly, that we're not running
3401 as a relay. Previously, some of our code would treat the presence
3402 of any ORPort line as meaning that we should act like a relay,
3403 even though our new listener code would correctly not open any
3404 ORPorts for ORPort 0. Similar bugs in other Port options are also
3405 fixed. Fixes the first half of bug 6507; bugfix on 0.2.3.3-alpha.
3408 - Avoid a pair of double-free and use-after-mark bugs that can
3409 occur with certain timings in canceled and re-received DNS
3410 requests. Fixes bug 6472; bugfix on 0.0.7rc1.
3411 - Fix build and 64-bit compile warnings from --enable-openbsd-malloc.
3412 Fixes bug 6379. Bugfix on 0.2.0.20-rc.
3413 - Allow one-hop directory fetching circuits the full "circuit build
3414 timeout" period, rather than just half of it, before failing them
3415 and marking the relay down. This fix should help reduce cases where
3416 clients declare relays (or worse, bridges) unreachable because
3417 the TLS handshake takes a few seconds to complete. Fixes bug 6743;
3418 bugfix on 0.2.2.2-alpha, where we changed the timeout from a static
3420 - Authorities no longer include any router in their microdescriptor
3421 consensuses for which they couldn't generate or agree on a
3422 microdescriptor. Fixes the second piece of bug 6404; fix on
3424 - Detect and reject attempts to specify both "FooPort" and
3425 "FooPort 0" in the same configuration domain. (It's still okay
3426 to have a FooPort in your configuration file, and use "FooPort 0"
3427 on the command line to disable it.) Fixes the second half of bug
3428 6507; bugfix on 0.2.3.3-alpha.
3429 - Make wildcarded addresses (that is, ones beginning with "*.") work
3430 when provided via the controller's MapAddress command. Previously,
3431 they were accepted, but we never actually noticed that they were
3432 wildcards. Fixes bug 6244; bugfix on 0.2.3.9-alpha.
3433 - Avoid crashing on a malformed state file where EntryGuardPathBias
3434 precedes EntryGuard. Fix for bug 6774; bugfix on 0.2.3.17-beta.
3435 - Add a (probably redundant) memory clear between iterations of
3436 the router status voting loop, to prevent future coding errors
3437 where data might leak between iterations of the loop. Resolves
3440 o Minor bugfixes (log messages):
3441 - Downgrade "set buildtimeout to low value" messages to "info"
3442 severity; they were never an actual problem, there was never
3443 anything reasonable to do about them, and they tended to spam logs
3444 from time to time. Fixes bug 6251; bugfix on 0.2.2.2-alpha.
3445 - Downgrade path-bias warning messages to "info". We'll try to get
3446 them working better in 0.2.4. Add internal circuit construction
3447 state to protect against the noisy warn message "Unexpectedly high
3448 circuit_successes". Also add some additional rate-limited notice
3449 messages to help determine the root cause of the warn. Fixes bug
3450 6475. Bugfix against 0.2.3.17-beta.
3451 - Move log message when unable to find a microdesc in a routerstatus
3452 entry to parse time. Previously we'd spam this warning every time
3453 we tried to figure out which microdescriptors to download. Fixes
3454 the third piece of bug 6404; fix on 0.2.3.18-rc.
3457 - Consider new, removed or changed IPv6 OR ports a non-cosmetic
3458 change when the authority is deciding whether to accept a newly
3459 uploaded descriptor. Implements ticket 6423.
3460 - Add missing documentation for consensus and microdesc files.
3461 Resolves ticket 6732.
3464 Changes in version 0.2.2.38 - 2012-08-12
3465 Tor 0.2.2.38 fixes a remotely triggerable crash bug, and fixes a timing
3466 attack that could in theory leak path information.
3469 - Avoid an uninitialized memory read when reading a vote or consensus
3470 document that has an unrecognized flavor name. This read could
3471 lead to a remote crash bug. Fixes bug 6530; bugfix on 0.2.2.6-alpha.
3472 - Try to leak less information about what relays a client is
3473 choosing to a side-channel attacker. Previously, a Tor client would
3474 stop iterating through the list of available relays as soon as it
3475 had chosen one, thus finishing a little earlier when it picked
3476 a router earlier in the list. If an attacker can recover this
3477 timing information (nontrivial but not proven to be impossible),
3478 they could learn some coarse-grained information about which relays
3479 a client was picking (middle nodes in particular are likelier to
3480 be affected than exits). The timing attack might be mitigated by
3481 other factors (see bug 6537 for some discussion), but it's best
3482 not to take chances. Fixes bug 6537; bugfix on 0.0.8rc1.
3485 Changes in version 0.2.3.20-rc - 2012-08-05
3486 Tor 0.2.3.20-rc is the third release candidate for the Tor 0.2.3.x
3487 series. It fixes a pair of code security bugs and a potential anonymity
3488 issue, updates our RPM spec files, and cleans up other smaller issues.
3491 - Avoid read-from-freed-memory and double-free bugs that could occur
3492 when a DNS request fails while launching it. Fixes bug 6480;
3493 bugfix on 0.2.0.1-alpha.
3494 - Avoid an uninitialized memory read when reading a vote or consensus
3495 document that has an unrecognized flavor name. This read could
3496 lead to a remote crash bug. Fixes bug 6530; bugfix on 0.2.2.6-alpha.
3497 - Try to leak less information about what relays a client is
3498 choosing to a side-channel attacker. Previously, a Tor client would
3499 stop iterating through the list of available relays as soon as it
3500 had chosen one, thus finishing a little earlier when it picked
3501 a router earlier in the list. If an attacker can recover this
3502 timing information (nontrivial but not proven to be impossible),
3503 they could learn some coarse-grained information about which relays
3504 a client was picking (middle nodes in particular are likelier to
3505 be affected than exits). The timing attack might be mitigated by
3506 other factors (see bug 6537 for some discussion), but it's best
3507 not to take chances. Fixes bug 6537; bugfix on 0.0.8rc1.
3510 - Try to make the warning when giving an obsolete SOCKSListenAddress
3511 a little more useful.
3512 - Terminate active server managed proxies if Tor stops being a
3513 relay. Addresses parts of bug 6274; bugfix on 0.2.3.6-alpha.
3514 - Provide a better error message about possible OSX Asciidoc failure
3515 reasons. Fixes bug 6436.
3516 - Warn when Tor is configured to use accounting in a way that can
3517 link a hidden service to some other hidden service or public
3518 address. Resolves ticket 6490.
3521 - Check return value of fputs() when writing authority certificate
3522 file. Fixes Coverity issue 709056; bugfix on 0.2.0.1-alpha.
3523 - Ignore ServerTransportPlugin lines when Tor is not configured as
3524 a relay. Fixes bug 6274; bugfix on 0.2.3.6-alpha.
3525 - When disabling guards for having too high a proportion of failed
3526 circuits, make sure to look at each guard. Fixes bug 6397; bugfix
3530 - Update our default RPM spec files to work with mock and rpmbuild
3531 on RHEL/Fedora. They have an updated set of dependencies and
3532 conflicts, a fix for an ancient typo when creating the "_tor"
3533 user, and better instructions. Thanks to Ondrej Mikle for the
3534 patch series. Fixes bug 6043.
3537 - Make it possible to set the TestingTorNetwork configuration
3538 option using AlternateDirAuthority and AlternateBridgeAuthority
3539 as an alternative to setting DirServer. Addresses ticket 6377.
3542 - Clarify the documentation for the Alternate*Authority options.
3544 - Fix some typos in the manpages. Patch from A. Costa. Fixes bug 6500.
3546 o Code simplification and refactoring:
3547 - Do not use SMARTLIST_FOREACH for any loop whose body exceeds
3548 10 lines. Also, don't nest them. Doing so in the past has
3549 led to hard-to-debug code. The new style is to use the
3550 SMARTLIST_FOREACH_{BEGIN,END} pair. Addresses issue 6400.
3553 Changes in version 0.2.3.19-rc - 2012-07-06
3554 Tor 0.2.3.19-rc is the second release candidate for the Tor 0.2.3.x
3555 series. It fixes the compile on Windows, reverts to a GeoIP database
3556 that isn't as broken, and fixes a flow control bug that has been around
3557 since the beginning of Tor.
3560 - Fix a bug handling SENDME cells on nonexistent streams that could
3561 result in bizarre window values. Report and patch contributed
3562 pseudonymously. Fixes part of bug 6271. This bug was introduced
3563 before the first Tor release, in svn commit r152.
3564 - Revert to the May 1 2012 Maxmind GeoLite Country database. In the
3565 June 2012 database, Maxmind marked many Tor relays as country "A1",
3566 which will cause risky behavior for clients that set EntryNodes
3567 or ExitNodes. Addresses bug 6334; bugfix on 0.2.3.17-beta.
3568 - Instead of ENOBUFS on Windows, say WSAENOBUFS. Fixes compilation
3569 on Windows. Fixes bug 6296; bugfix on 0.2.3.18-rc.
3572 - Fix wrong TCP port range in parse_port_range(). Fixes bug 6218;
3573 bugfix on 0.2.1.10-alpha.
3576 Changes in version 0.2.3.18-rc - 2012-06-28
3577 Tor 0.2.3.18-rc is the first release candidate for the Tor 0.2.3.x
3578 series. It fixes a few smaller bugs, but generally appears stable.
3579 Please test it and let us know whether it is!
3582 - Allow wildcarded mapaddress targets to be specified on the
3583 controlport. Partially fixes bug 6244; bugfix on 0.2.3.9-alpha.
3584 - Make our linker option detection code more robust against linkers
3585 such as on FreeBSD 8, where a bad combination of options completes
3586 successfully but makes an unrunnable binary. Fixes bug 6173;
3587 bugfix on 0.2.3.17-beta.
3589 o Minor bugfixes (on 0.2.2.x and earlier):
3590 - Avoid a false positive in the util/threads unit test by increasing
3591 the maximum timeout time. Fixes bug 6227; bugfix on 0.2.0.4-alpha.
3592 - Replace "Sending publish request" log messages with "Launching
3593 upload", so that they no longer confusingly imply that we're
3594 sending something to a directory we might not even be connected
3595 to yet. Fixes bug 3311; bugfix on 0.2.0.10-alpha.
3596 - Make sure to set *socket_error in all error cases in
3597 connection_connect(), so it can't produce a warning about
3598 errno being zero from errno_to_orconn_end_reason(). Bugfix on
3599 0.2.1.1-alpha; resolves ticket 6028.
3600 - Downgrade "Got a certificate, but we already have it" log messages
3601 from warning to info, except when we're a dirauth. Fixes bug 5238;
3602 bugfix on 0.2.1.7-alpha.
3603 - When checking for requested signatures on the latest consensus
3604 before serving it to a client, make sure to check the right
3605 consensus flavor. Bugfix on 0.2.2.6-alpha.
3606 - Downgrade "eventdns rejected address" message to LOG_PROTOCOL_WARN.
3607 Fixes bug 5932; bugfix on 0.2.2.7-alpha.
3609 o Minor bugfixes (on 0.2.3.x):
3610 - Make format_helper_exit_status() avoid unnecessary space padding
3611 and stop confusing log_from_pipe(). Fixes ticket 5557; bugfix
3613 - Downgrade a message about cleaning the microdescriptor cache to
3614 "info" from "notice". Fixes bug 6238; bugfix on 0.2.3.1-alpha.
3615 - Log a BUG message at severity INFO if we have a networkstatus with
3616 a missing entry for some microdescriptor. Continues on a patch
3618 - Improve the log message when a managed proxy fails to launch. Fixes
3619 bug 5099; bugfix on 0.2.3.6-alpha.
3620 - Don't do DNS lookups when parsing corrupted managed proxy protocol
3621 messages. Fixes bug 6226; bugfix on 0.2.3.6-alpha.
3622 - When formatting wildcarded address mappings for the controller,
3623 be sure to include "*." as appropriate. Partially fixes bug 6244;
3624 bugfix on 0.2.3.9-alpha.
3625 - Avoid a warning caused by using strcspn() from glibc with clang 3.0.
3626 Bugfix on 0.2.3.13-alpha.
3627 - Stop logging messages about running with circuit timeout learning
3628 enabled at severity LD_BUG. Fixes bug 6169; bugfix on 0.2.3.17-beta.
3629 - Disable a spurious warning about reading on a marked and flushing
3630 connection. We shouldn't be doing that, but apparently we
3631 sometimes do. Fixes bug 6203; bugfix on 0.2.3.17-beta.
3632 - Fix a bug that stopped AllowDotExit from working on addresses
3633 that had an entry in the DNS cache. Fixes bug 6211; bugfix on
3636 o Code simplification, refactoring, unit tests:
3637 - Move tor_gettimeofday_cached() into compat_libevent.c, and use
3638 Libevent's notion of cached time when possible.
3639 - Remove duplicate code for invoking getrlimit() from control.c.
3640 - Add a unit test for the environment_variable_names_equal function.
3643 - Document the --defaults-torrc option, and the new (in 0.2.3)
3644 semantics for overriding, extending, and clearing lists of
3645 options. Closes bug 4748.
3648 Changes in version 0.2.3.17-beta - 2012-06-15
3649 Tor 0.2.3.17-beta enables compiler and linker hardening by default,
3650 gets our TLS handshake back on track for being able to blend in with
3651 Firefox, fixes a big bug in 0.2.3.16-alpha that broke Tor's interaction
3652 with Vidalia, and otherwise continues to get us closer to a release
3656 - Enable gcc and ld hardening by default. Resolves ticket 5210.
3657 - Update TLS cipher list to match Firefox 8 and later. Resolves
3659 - Implement the client side of proposal 198: remove support for
3660 clients falsely claiming to support standard ciphersuites that
3661 they can actually provide. As of modern OpenSSL versions, it's not
3662 necessary to fake any standard ciphersuite, and doing so prevents
3663 us from using better ciphersuites in the future, since servers
3664 can't know whether an advertised ciphersuite is really supported or
3665 not. Some hosts -- notably, ones with very old versions of OpenSSL
3666 or where OpenSSL has been built with ECC disabled -- will stand
3667 out because of this change; TBB users should not be affected.
3670 - Change the default value for DynamicDHGroups (introduced in
3671 0.2.3.9-alpha) to 0. This feature can make Tor relays less
3672 identifiable by their use of the mod_ssl DH group, but at
3673 the cost of some usability (#4721) and bridge tracing (#6087)
3674 regressions. Resolves ticket 5598.
3675 - Send a CRLF at the end of each STATUS_* control protocol event. This
3676 bug tickled a bug in Vidalia which would make it freeze. Fixes
3677 bug 6094; bugfix on 0.2.3.16-alpha.
3680 - Disable writing on marked-for-close connections when they are
3681 blocked on bandwidth, to prevent busy-looping in Libevent. Fixes
3682 bug 5263; bugfix on 0.0.2pre13, where we first added a special
3683 case for flushing marked connections.
3684 - Detect SSL handshake even when the initial attempt to write the
3685 server hello fails. Fixes bug 4592; bugfix on 0.2.0.13-alpha.
3686 - Change the AllowDotExit rules so they should actually work.
3687 We now enforce AllowDotExit only immediately after receiving an
3688 address via SOCKS or DNSPort: other sources are free to provide
3689 .exit addresses after the resolution occurs. Fixes bug 3940;
3690 bugfix on 0.2.2.1-alpha.
3691 - Fix a (harmless) integer overflow in cell statistics reported by
3692 some fast relays. Fixes bug 5849; bugfix on 0.2.2.1-alpha.
3693 - Make sure circuitbuild.c checks LearnCircuitBuildTimeout in all the
3694 right places and never depends on the consensus parameters or
3695 computes adaptive timeouts when it is disabled. Fixes bug 5049;
3696 bugfix on 0.2.2.14-alpha.
3697 - When building Tor on Windows with -DUNICODE (not default), ensure
3698 that error messages, filenames, and DNS server names are always
3699 NUL-terminated when we convert them to a single-byte encoding.
3700 Fixes bug 5909; bugfix on 0.2.2.16-alpha.
3701 - Make Tor build correctly again with -DUNICODE -D_UNICODE defined.
3702 Fixes bug 6097; bugfix on 0.2.2.16-alpha.
3703 - Fix an edge case where TestingTorNetwork is set but the authorities
3704 and relays all have an uptime of zero, where the private Tor network
3705 could briefly lack support for hidden services. Fixes bug 3886;
3706 bugfix on 0.2.2.18-alpha.
3707 - Correct the manpage's descriptions for the default values of
3708 DirReqStatistics and ExtraInfoStatistics. Fixes bug 2865; bugfix
3710 - Fix the documentation for the --hush and --quiet command line
3711 options, which changed their behavior back in 0.2.3.3-alpha.
3712 - Fix compilation warning with clang 3.1. Fixes bug 6141; bugfix on
3716 - Rate-limit the "Weighted bandwidth is 0.000000" message, and add
3717 more information to it, so that we can track it down in case it
3718 returns again. Mitigates bug 5235.
3719 - Check CircuitBuildTimeout and LearnCircuitBuildTimeout in
3720 options_validate(); warn if LearnCircuitBuildTimeout is disabled and
3721 CircuitBuildTimeout is set unreasonably low. Resolves ticket 5452.
3722 - Warn the user when HTTPProxy, but no other proxy type, is
3723 configured. This can cause surprising behavior: it doesn't send
3724 all of Tor's traffic over the HTTPProxy -- it sends unencrypted
3725 directory traffic only. Resolves ticket 4663.
3726 - Issue a notice if a guard completes less than 40% of your circuits.
3727 Threshold is configurable by torrc option PathBiasNoticeRate and
3728 consensus parameter pb_noticepct. There is additional, off-by-
3729 default code to disable guards which fail too many circuits.
3730 Addresses ticket 5458.
3731 - Update to the June 6 2012 Maxmind GeoLite Country database.
3733 o Code simplifications and refactoring:
3734 - Remove validate_pluggable_transports_config(): its warning
3735 message is now handled by connection_or_connect().
3738 Changes in version 0.2.2.37 - 2012-06-06
3739 Tor 0.2.2.37 introduces a workaround for a critical renegotiation
3740 bug in OpenSSL 1.0.1 (where 20% of the Tor network can't talk to itself
3744 - Work around a bug in OpenSSL that broke renegotiation with TLS
3745 1.1 and TLS 1.2. Without this workaround, all attempts to speak
3746 the v2 Tor connection protocol when both sides were using OpenSSL
3747 1.0.1 would fail. Resolves ticket 6033.
3748 - When waiting for a client to renegotiate, don't allow it to add
3749 any bytes to the input buffer. This fixes a potential DoS issue.
3750 Fixes bugs 5934 and 6007; bugfix on 0.2.0.20-rc.
3751 - Fix an edge case where if we fetch or publish a hidden service
3752 descriptor, we might build a 4-hop circuit and then use that circuit
3753 for exiting afterwards -- even if the new last hop doesn't obey our
3754 ExitNodes config option. Fixes bug 5283; bugfix on 0.2.0.10-alpha.
3757 - Fix a build warning with Clang 3.1 related to our use of vasprintf.
3758 Fixes bug 5969. Bugfix on 0.2.2.11-alpha.
3761 - Tell GCC and Clang to check for any errors in format strings passed
3762 to the tor_v*(print|scan)f functions.
3765 Changes in version 0.2.3.16-alpha - 2012-06-05
3766 Tor 0.2.3.16-alpha introduces a workaround for a critical renegotiation
3767 bug in OpenSSL 1.0.1 (where 20% of the Tor network can't talk to itself
3768 currently). It also fixes a variety of smaller bugs and other cleanups
3769 that get us closer to a release candidate.
3771 o Major bugfixes (general):
3772 - Work around a bug in OpenSSL that broke renegotiation with TLS
3773 1.1 and TLS 1.2. Without this workaround, all attempts to speak
3774 the v2 Tor connection protocol when both sides were using OpenSSL
3775 1.0.1 would fail. Resolves ticket 6033.
3776 - When waiting for a client to renegotiate, don't allow it to add
3777 any bytes to the input buffer. This fixes a potential DoS issue.
3778 Fixes bugs 5934 and 6007; bugfix on 0.2.0.20-rc.
3779 - Pass correct OR address to managed proxies (like obfsproxy),
3780 even when ORListenAddress is used. Fixes bug 4865; bugfix on
3782 - The advertised platform of a router now includes only its operating
3783 system's name (e.g., "Linux", "Darwin", "Windows 7"), and not its
3784 service pack level (for Windows) or its CPU architecture (for Unix).
3785 We also no longer include the "git-XYZ" tag in the version. Resolves
3788 o Major bugfixes (clients):
3789 - If we are unable to find any exit that supports our predicted ports,
3790 stop calling them predicted, so that we don't loop and build
3791 hopeless circuits indefinitely. Fixes bug 3296; bugfix on 0.0.9pre6,
3792 which introduced predicted ports.
3793 - Fix an edge case where if we fetch or publish a hidden service
3794 descriptor, we might build a 4-hop circuit and then use that circuit
3795 for exiting afterwards -- even if the new last hop doesn't obey our
3796 ExitNodes config option. Fixes bug 5283; bugfix on 0.2.0.10-alpha.
3797 - Check at each new consensus whether our entry guards were picked
3798 long enough ago that we should rotate them. Previously, we only
3799 did this check at startup, which could lead to us holding a guard
3800 indefinitely. Fixes bug 5380; bugfix on 0.2.1.14-rc.
3801 - When fetching a bridge descriptor from a bridge authority,
3802 always do so anonymously, whether we have been able to open
3803 circuits or not. Partial fix for bug 1938; bugfix on 0.2.0.7-alpha.
3804 This behavior makes it *safer* to use UpdateBridgesFromAuthority,
3805 but we'll need to wait for bug 6010 before it's actually usable.
3807 o Major bugfixes (directory authorities):
3808 - When computing weight parameters, behave more robustly in the
3809 presence of a bad bwweightscale value. Previously, the authorities
3810 would crash if they agreed on a sufficiently broken weight_scale
3811 value: now, they use a reasonable default and carry on. Partial
3812 fix for 5786; bugfix on 0.2.2.17-alpha.
3813 - Check more thoroughly to prevent a rogue authority from
3814 double-voting on any consensus directory parameter. Previously,
3815 authorities would crash in this case if the total number of
3816 votes for any parameter exceeded the number of active voters,
3817 but would let it pass otherwise. Partial fix for bug 5786; bugfix
3821 - Rate-limit log messages when asked to connect anonymously to
3822 a private address. When these hit, they tended to hit fast and
3823 often. Also, don't bother trying to connect to addresses that we
3824 are sure will resolve to 127.0.0.1: getting 127.0.0.1 in a directory
3825 reply makes us think we have been lied to, even when the address the
3826 client tried to connect to was "localhost." Resolves ticket 2822.
3827 - Allow packagers to insert an extra string in server descriptor
3828 platform lines by setting the preprocessor variable TOR_BUILD_TAG.
3829 Resolves the rest of ticket 2988.
3830 - Raise the threshold of server descriptors needed (75%) and exit
3831 server descriptors needed (50%) before we will declare ourselves
3832 bootstrapped. This will make clients start building circuits a
3833 little later, but makes the initially constructed circuits less
3834 skewed and less in conflict with further directory fetches. Fixes
3836 - Close any connection that sends unrecognized junk before the
3837 handshake. Solves an issue noted in bug 4369.
3838 - Improve log messages about managed transports. Resolves ticket 5070.
3839 - Tag a bridge's descriptor as "never to be sent unencrypted".
3840 This shouldn't matter, since bridges don't open non-anonymous
3841 connections to the bridge authority and don't allow unencrypted
3842 directory connections from clients, but we might as well make
3843 sure. Closes bug 5139.
3844 - Expose our view of whether we have gone dormant to the controller,
3845 via a new "GETINFO dormant" value. Torbutton and other controllers
3846 can use this to avoid doing periodic requests through Tor while
3847 it's dormant (bug 4718). Fixes bug 5954.
3848 - Tell GCC and Clang to check for any errors in format strings passed
3849 to the tor_v*(print|scan)f functions.
3850 - Update to the May 1 2012 Maxmind GeoLite Country database.
3852 o Minor bugfixes (already included in 0.2.2.36):
3853 - Reject out-of-range times like 23:59:61 in parse_rfc1123_time().
3854 Fixes bug 5346; bugfix on 0.0.8pre3.
3855 - Correct parsing of certain date types in parse_http_time().
3856 Without this patch, If-Modified-Since would behave
3857 incorrectly. Fixes bug 5346; bugfix on 0.2.0.2-alpha. Patch from
3858 Esteban Manchado Velázques.
3859 - Make our number-parsing functions always treat too-large values
3860 as an error, even when those values exceed the width of the
3861 underlying type. Previously, if the caller provided these
3862 functions with minima or maxima set to the extreme values of the
3863 underlying integer type, these functions would return those
3864 values on overflow rather than treating overflow as an error.
3865 Fixes part of bug 5786; bugfix on 0.0.9.
3866 - If we hit the error case where routerlist_insert() replaces an
3867 existing (old) server descriptor, make sure to remove that
3868 server descriptor from the old_routers list. Fix related to bug
3869 1776. Bugfix on 0.2.2.18-alpha.
3870 - Clarify the behavior of MaxCircuitDirtiness with hidden service
3871 circuits. Fixes issue 5259.
3873 o Minor bugfixes (coding cleanup, on 0.2.2.x and earlier):
3874 - Prevent a null-pointer dereference when receiving a data cell
3875 for a nonexistent stream when the circuit in question has an
3876 empty deliver window. We don't believe this is triggerable,
3877 since we don't currently allow deliver windows to become empty,
3878 but the logic is tricky enough that it's better to make the code
3879 robust. Fixes bug 5541; bugfix on 0.0.2pre14.
3880 - Fix a memory leak when trying to launch a DNS request when the
3881 network is disabled or the nameservers are unconfigurable. Fixes
3882 bug 5916; bugfix on Tor 0.1.2.1-alpha (for the unconfigurable
3883 nameserver case) and on 0.2.3.9-alpha (for the DisableNetwork case).
3884 - Don't hold a Windows file handle open for every file mapping;
3885 the file mapping handle is sufficient. Fixes bug 5951; bugfix on
3887 - Avoid O(n^2) performance characteristics when parsing a large
3888 extrainfo cache. Fixes bug 5828; bugfix on 0.2.0.1-alpha.
3889 - Format more doubles with %f, not %lf. Patch from grarpamp to make
3890 Tor build correctly on older BSDs again. Fixes bug 3894; bugfix on
3892 - Make our replacement implementation of strtok_r() compatible with
3893 the standard behavior of strtok_r(). Patch by nils. Fixes bug 5091;
3894 bugfix on 0.2.2.1-alpha.
3895 - Fix a NULL-pointer dereference on a badly formed
3896 SETCIRCUITPURPOSE command. Found by mikeyc. Fixes bug 5796;
3897 bugfix on 0.2.2.9-alpha.
3898 - Fix a build warning with Clang 3.1 related to our use of vasprintf.
3899 Fixes bug 5969. Bugfix on 0.2.2.11-alpha.
3900 - Defensively refactor rend_mid_rendezvous() so that protocol
3901 violations and length checks happen in the beginning. Fixes
3903 - Set _WIN32_WINNT to 0x0501 consistently throughout the code, so
3904 that IPv6 stuff will compile on MSVC, and compilation issues
3905 will be easier to track down. Fixes bug 5861.
3907 o Minor bugfixes (correctness, on 0.2.2.x and earlier):
3908 - Exit nodes now correctly report EADDRINUSE and EADDRNOTAVAIL as
3909 resource exhaustion, so that clients can adjust their load to
3910 try other exits. Fixes bug 4710; bugfix on 0.1.0.1-rc, which
3911 started using END_STREAM_REASON_RESOURCELIMIT.
3912 - Don't check for whether the address we're using for outbound
3913 connections has changed until after the outbound connection has
3914 completed. On Windows, getsockname() doesn't succeed until the
3915 connection is finished. Fixes bug 5374; bugfix on 0.1.1.14-alpha.
3916 - If the configuration tries to set MyFamily on a bridge, refuse to
3917 do so, and warn about the security implications. Fixes bug 4657;
3918 bugfix on 0.2.0.3-alpha.
3919 - If the client fails to set a reasonable set of ciphersuites
3920 during its v2 handshake renegotiation, allow the renegotiation to
3921 continue nevertheless (i.e. send all the required certificates).
3922 Fixes bug 4591; bugfix on 0.2.0.20-rc.
3923 - When we receive a SIGHUP and the controller __ReloadTorrcOnSIGHUP
3924 option is set to 0 (which Vidalia version 0.2.16 now does when
3925 a SAVECONF attempt fails), perform other actions that SIGHUP
3926 usually causes (like reopening the logs). Fixes bug 5095; bugfix
3928 - If we fail to write a microdescriptor to the disk cache, do not
3929 continue replacing the old microdescriptor file. Fixes bug 2954;
3930 bugfix on 0.2.2.6-alpha.
3931 - Exit nodes don't need to fetch certificates for authorities that
3932 they don't recognize; only directory authorities, bridges,
3933 and caches need to do that. Fixes part of bug 2297; bugfix on
3935 - Correctly handle checking the permissions on the parent
3936 directory of a control socket in the root directory. Bug found
3937 by Esteban Manchado Velázquez. Fixes bug 5089; bugfix on Tor
3939 - When told to add a bridge with the same digest as a preexisting
3940 bridge but a different addr:port, change the addr:port as
3941 requested. Previously we would not notice the change. Fixes half
3942 of bug 5603; fix on 0.2.2.26-beta.
3943 - End AUTHCHALLENGE error messages (in the control protocol) with
3944 a CRLF. Fixes bug 5760; bugfix on 0.2.2.36 and 0.2.3.13-alpha.
3946 o Minor bugfixes (on 0.2.3.x):
3947 - Turn an assertion (that the number of handshakes received as a
3948 server is not < 1) into a warning. Fixes bug 4873; bugfix on
3950 - Format IPv4 addresses correctly in ADDRMAP events. (Previously,
3951 we had reversed them when the answer was cached.) Fixes bug
3952 5723; bugfix on 0.2.3.1-alpha.
3953 - Work correctly on Linux systems with accept4 support advertised in
3954 their headers, but without accept4 support in the kernel. Fix
3955 by murb. Fixes bug 5762; bugfix on 0.2.3.1-alpha.
3956 - When told to add a bridge with the same addr:port as a preexisting
3957 bridge but a different transport, change the transport as
3958 requested. Previously we would not notice the change. Fixes half
3959 of bug 5603; fix on 0.2.3.2-alpha.
3960 - Avoid a "double-reply" warning when replying to a SOCKS request
3961 with a parse error. Patch from Fabian Keil. Fixes bug 4108;
3962 bugfix on 0.2.3.4-alpha.
3963 - Fix a bug where a bridge authority crashes if it has seen no
3964 directory requests when it's time to write statistics to disk.
3965 Fixes bug 5891; bugfix on 0.2.3.6-alpha. Also fixes bug 5508 in
3967 - Don't try to open non-control listeners when DisableNetwork is set.
3968 Previously, we'd open all listeners, then immediately close them.
3969 Fixes bug 5604; bugfix on 0.2.3.9-alpha.
3970 - Don't abort the managed proxy protocol if the managed proxy
3971 sends us an unrecognized line; ignore it instead. Fixes bug
3972 5910; bugfix on 0.2.3.9-alpha.
3973 - Fix a compile warning in crypto.c when compiling with clang 3.1.
3974 Fixes bug 5969, bugfix on 0.2.3.9-alpha.
3975 - Fix a compilation issue on GNU Hurd, which doesn't have PATH_MAX.
3976 Fixes bug 5355; bugfix on 0.2.3.11-alpha.
3977 - Remove bogus definition of "_WIN32" from src/win32/orconfig.h, to
3978 unbreak the MSVC build. Fixes bug 5858; bugfix on 0.2.3.12-alpha.
3979 - Resolve numerous small warnings and build issues with MSVC. Resolves
3982 o Documentation fixes:
3983 - Improve the manual's documentation for the NT Service command-line
3984 options. Addresses ticket 3964.
3985 - Clarify SessionGroup documentation slightly; resolves ticket 5437.
3986 - Document the changes to the ORPort and DirPort options, and the
3987 fact that {OR/Dir}ListenAddress is now unnecessary (and
3988 therefore deprecated). Resolves ticket 5597.
3991 - Remove the torrc.bridge file: we don't use it for anything, and
3992 it had become badly desynchronized from torrc.sample. Resolves
3996 Changes in version 0.2.2.36 - 2012-05-24
3997 Tor 0.2.2.36 updates the addresses for two of the eight directory
3998 authorities, fixes some potential anonymity and security issues,
3999 and fixes several crash bugs.
4001 Tor 0.2.1.x has reached its end-of-life. Those Tor versions have many
4002 known flaws, and nobody should be using them. You should upgrade. If
4003 you're using a Linux or BSD and its packages are obsolete, stop using
4004 those packages and upgrade anyway.
4006 o Directory authority changes:
4007 - Change IP address for maatuska (v3 directory authority).
4008 - Change IP address for ides (v3 directory authority), and rename
4012 - When building or running with any version of OpenSSL earlier
4013 than 0.9.8s or 1.0.0f, disable SSLv3 support. These OpenSSL
4014 versions have a bug (CVE-2011-4576) in which their block cipher
4015 padding includes uninitialized data, potentially leaking sensitive
4016 information to any peer with whom they make a SSLv3 connection. Tor
4017 does not use SSL v3 by default, but a hostile client or server
4018 could force an SSLv3 connection in order to gain information that
4019 they shouldn't have been able to get. The best solution here is to
4020 upgrade to OpenSSL 0.9.8s or 1.0.0f (or later). But when building
4021 or running with a non-upgraded OpenSSL, we disable SSLv3 entirely
4022 to make sure that the bug can't happen.
4023 - Never use a bridge or a controller-supplied node as an exit, even
4024 if its exit policy allows it. Found by wanoskarnet. Fixes bug
4025 5342. Bugfix on 0.1.1.15-rc (for controller-purpose descriptors)
4026 and 0.2.0.3-alpha (for bridge-purpose descriptors).
4027 - Only build circuits if we have a sufficient threshold of the total
4028 descriptors that are marked in the consensus with the "Exit"
4029 flag. This mitigates an attack proposed by wanoskarnet, in which
4030 all of a client's bridges collude to restrict the exit nodes that
4031 the client knows about. Fixes bug 5343.
4032 - Provide controllers with a safer way to implement the cookie
4033 authentication mechanism. With the old method, if another locally
4034 running program could convince a controller that it was the Tor
4035 process, then that program could trick the controller into telling
4036 it the contents of an arbitrary 32-byte file. The new "SAFECOOKIE"
4037 authentication method uses a challenge-response approach to prevent
4038 this attack. Fixes bug 5185; implements proposal 193.
4041 - Avoid logging uninitialized data when unable to decode a hidden
4042 service descriptor cookie. Fixes bug 5647; bugfix on 0.2.1.5-alpha.
4043 - Avoid a client-side assertion failure when receiving an INTRODUCE2
4044 cell on a general purpose circuit. Fixes bug 5644; bugfix on
4046 - Fix builds when the path to sed, openssl, or sha1sum contains
4047 spaces, which is pretty common on Windows. Fixes bug 5065; bugfix
4049 - Correct our replacements for the timeradd() and timersub() functions
4050 on platforms that lack them (for example, Windows). The timersub()
4051 function is used when expiring circuits, while timeradd() is
4052 currently unused. Bug report and patch by Vektor. Fixes bug 4778;
4053 bugfix on 0.2.2.24-alpha.
4054 - Fix the SOCKET_OK test that we use to tell when socket
4055 creation fails so that it works on Win64. Fixes part of bug 4533;
4056 bugfix on 0.2.2.29-beta. Bug found by wanoskarnet.
4059 - Reject out-of-range times like 23:59:61 in parse_rfc1123_time().
4060 Fixes bug 5346; bugfix on 0.0.8pre3.
4061 - Make our number-parsing functions always treat too-large values
4062 as an error, even when those values exceed the width of the
4063 underlying type. Previously, if the caller provided these
4064 functions with minima or maxima set to the extreme values of the
4065 underlying integer type, these functions would return those
4066 values on overflow rather than treating overflow as an error.
4067 Fixes part of bug 5786; bugfix on 0.0.9.
4068 - Older Linux kernels erroneously respond to strange nmap behavior
4069 by having accept() return successfully with a zero-length
4070 socket. When this happens, just close the connection. Previously,
4071 we would try harder to learn the remote address: but there was
4072 no such remote address to learn, and our method for trying to
4073 learn it was incorrect. Fixes bugs 1240, 4745, and 4747. Bugfix
4074 on 0.1.0.3-rc. Reported and diagnosed by "r1eo".
4075 - Correct parsing of certain date types in parse_http_time().
4076 Without this patch, If-Modified-Since would behave
4077 incorrectly. Fixes bug 5346; bugfix on 0.2.0.2-alpha. Patch from
4078 Esteban Manchado Velázques.
4079 - Change the BridgePassword feature (part of the "bridge community"
4080 design, which is not yet implemented) to use a time-independent
4081 comparison. The old behavior might have allowed an adversary
4082 to use timing to guess the BridgePassword value. Fixes bug 5543;
4083 bugfix on 0.2.0.14-alpha.
4084 - Detect and reject certain misformed escape sequences in
4085 configuration values. Previously, these values would cause us
4086 to crash if received in a torrc file or over an authenticated
4087 control port. Bug found by Esteban Manchado Velázquez, and
4088 independently by Robert Connolly from Matta Consulting who further
4089 noted that it allows a post-authentication heap overflow. Patch
4090 by Alexander Schrijver. Fixes bugs 5090 and 5402 (CVE 2012-1668);
4091 bugfix on 0.2.0.16-alpha.
4092 - Fix a compile warning when using the --enable-openbsd-malloc
4093 configure option. Fixes bug 5340; bugfix on 0.2.0.20-rc.
4094 - During configure, detect when we're building with clang version
4095 3.0 or lower and disable the -Wnormalized=id and -Woverride-init
4096 CFLAGS. clang doesn't support them yet.
4097 - When sending an HTTP/1.1 proxy request, include a Host header.
4098 Fixes bug 5593; bugfix on 0.2.2.1-alpha.
4099 - Fix a NULL-pointer dereference on a badly formed SETCIRCUITPURPOSE
4100 command. Found by mikeyc. Fixes bug 5796; bugfix on 0.2.2.9-alpha.
4101 - If we hit the error case where routerlist_insert() replaces an
4102 existing (old) server descriptor, make sure to remove that
4103 server descriptor from the old_routers list. Fix related to bug
4104 1776. Bugfix on 0.2.2.18-alpha.
4106 o Minor bugfixes (documentation and log messages):
4107 - Fix a typo in a log message in rend_service_rendezvous_has_opened().
4108 Fixes bug 4856; bugfix on Tor 0.0.6.
4109 - Update "ClientOnly" man page entry to explain that there isn't
4110 really any point to messing with it. Resolves ticket 5005.
4111 - Document the GiveGuardFlagTo_CVE_2011_2768_VulnerableRelays
4112 directory authority option (introduced in Tor 0.2.2.34).
4113 - Downgrade the "We're missing a certificate" message from notice
4114 to info: people kept mistaking it for a real problem, whereas it
4115 is seldom the problem even when we are failing to bootstrap. Fixes
4116 bug 5067; bugfix on 0.2.0.10-alpha.
4117 - Correctly spell "connect" in a log message on failure to create a
4118 controlsocket. Fixes bug 4803; bugfix on 0.2.2.26-beta.
4119 - Clarify the behavior of MaxCircuitDirtiness with hidden service
4120 circuits. Fixes issue 5259.
4123 - Directory authorities now reject versions of Tor older than
4124 0.2.1.30, and Tor versions between 0.2.2.1-alpha and 0.2.2.20-alpha
4125 inclusive. These versions accounted for only a small fraction of
4126 the Tor network, and have numerous known security issues. Resolves
4128 - Update to the May 1 2012 Maxmind GeoLite Country database.
4131 - When sending or relaying a RELAY_EARLY cell, we used to convert
4132 it to a RELAY cell if the connection was using the v1 link
4133 protocol. This was a workaround for older versions of Tor, which
4134 didn't handle RELAY_EARLY cells properly. Now that all supported
4135 versions can handle RELAY_EARLY cells, and now that we're enforcing
4136 the "no RELAY_EXTEND commands except in RELAY_EARLY cells" rule,
4137 remove this workaround. Addresses bug 4786.
4140 Changes in version 0.2.3.15-alpha - 2012-04-30
4141 Tor 0.2.3.15-alpha fixes a variety of smaller bugs, including making
4142 the development branch build on Windows again.
4144 o Minor bugfixes (on 0.2.2.x and earlier):
4145 - Make sure that there are no unhandled pending TLS errors before
4146 reading from a TLS stream. We had checks in 0.1.0.3-rc, but
4147 lost them in 0.1.0.5-rc when we refactored read_to_buf_tls().
4148 Bugfix on 0.1.0.5-rc; fixes bug 4528.
4149 - Fix an assert that directory authorities could trigger on sighup
4150 during some configuration state transitions. We now don't treat
4151 it as a fatal error when the new descriptor we just generated in
4152 init_keys() isn't accepted. Fixes bug 4438; bugfix on 0.2.1.9-alpha.
4153 - After we pick a directory mirror, we would refuse to use it if
4154 it's in our ExcludeExitNodes list, resulting in mysterious failures
4155 to bootstrap for people who just wanted to avoid exiting from
4156 certain locations. Fixes bug 5623; bugfix on 0.2.2.25-alpha.
4157 - When building with --enable-static-tor on OpenBSD, do not
4158 erroneously attempt to link -lrt. Fixes bug 5103.
4160 o Minor bugfixes (on 0.2.3.x):
4161 - When Tor is built with kernel headers from a recent (last few
4162 years) Linux kernel, do not fail to run on older (pre-2.6.28
4163 Linux kernels). Fixes bug 5112; bugfix on 0.2.3.1-alpha.
4164 - Fix cross-compilation issues with mingw. Bugfixes on 0.2.3.6-alpha
4166 - Fix compilation with miniupnpc version 1.6; patch from
4167 Anthony G. Basile. Fixes bug 5434; bugfix on 0.2.3.12-alpha.
4168 - Fix compilation with MSVC, which had defined MS_WINDOWS. Bugfix
4169 on 0.2.3.13-alpha; found and fixed by Gisle Vanem.
4170 - Fix compilation on platforms without unistd.h, or where environ
4171 is defined in stdlib.h. Fixes bug 5704; bugfix on 0.2.3.13-alpha.
4174 - Directory authorities are now a little more lenient at accepting
4175 older router descriptors, or newer router descriptors that don't
4176 make big changes. This should help ameliorate past and future
4177 issues where routers think they have uploaded valid descriptors,
4178 but the authorities don't think so. Fix for ticket 2479.
4179 - Make the code that clients use to detect an address change be
4180 IPv6-aware, so that it won't fill clients' logs with error
4181 messages when trying to get the IPv4 address of an IPv6
4182 connection. Implements ticket 5537.
4185 - Remove the GiveGuardFlagTo_CVE_2011_2768_VulnerableRelays option;
4186 authorities needed to use it for a while to keep the network working
4187 as people upgraded to 0.2.1.31, 0.2.2.34, or 0.2.3.6-alpha, but
4188 that was six months ago. As of now, it should no longer be needed
4192 Changes in version 0.2.3.14-alpha - 2012-04-23
4193 Tor 0.2.3.14-alpha fixes yet more bugs to get us closer to a release
4194 candidate. It also dramatically speeds up AES: fast relays should
4195 consider switching to the newer OpenSSL library.
4197 o Directory authority changes:
4198 - Change IP address for ides (v3 directory authority), and rename
4202 - Avoid logging uninitialized data when unable to decode a hidden
4203 service descriptor cookie. Fixes bug 5647; bugfix on 0.2.1.5-alpha.
4204 - Avoid a client-side assertion failure when receiving an INTRODUCE2
4205 cell on a general purpose circuit. Fixes bug 5644; bugfix on
4207 - If authorities are unable to get a v2 consensus document from other
4208 directory authorities, they no longer fall back to fetching
4209 them from regular directory caches. Fixes bug 5635; bugfix on
4210 0.2.2.26-beta, where routers stopped downloading v2 consensus
4212 - When we start a Tor client with a normal consensus already cached,
4213 be willing to download a microdescriptor consensus. Fixes bug 4011;
4214 fix on 0.2.3.1-alpha.
4216 o Major features (performance):
4217 - When built to use OpenSSL 1.0.1, and built for an x86 or x86_64
4218 instruction set, take advantage of OpenSSL's AESNI, bitsliced, or
4219 vectorized AES implementations as appropriate. These can be much,
4220 much faster than other AES implementations.
4222 o Minor bugfixes (0.2.2.x and earlier):
4223 - Don't launch more than 10 service-side introduction-point circuits
4224 for a hidden service in five minutes. Previously, we would consider
4225 launching more introduction-point circuits if at least one second
4226 had passed without any introduction-point circuits failing. Fixes
4227 bug 4607; bugfix on 0.0.7pre1.
4228 - Change the BridgePassword feature (part of the "bridge community"
4229 design, which is not yet implemented) to use a time-independent
4230 comparison. The old behavior might have allowed an adversary
4231 to use timing to guess the BridgePassword value. Fixes bug 5543;
4232 bugfix on 0.2.0.14-alpha.
4233 - Enforce correct return behavior of tor_vsscanf() when the '%%'
4234 pattern is used. Fixes bug 5558. Bugfix on 0.2.1.13.
4235 - When sending an HTTP/1.1 proxy request, include a Host header.
4236 Fixes bug 5593; bugfix on 0.2.2.1-alpha.
4237 - Don't log that we have "decided to publish new relay descriptor"
4238 unless we are actually publishing a descriptor. Fixes bug 3942;
4239 bugfix on 0.2.2.28-beta.
4241 o Minor bugfixes (0.2.3.x):
4242 - Fix a bug where a bridge authority crashes (on a failed assert)
4243 if it has seen no directory requests when it's time to write
4244 statistics to disk. Fixes bug 5508. Bugfix on 0.2.3.6-alpha.
4245 - Fix bug stomping on ORPort option NoListen and ignoring option
4246 NoAdvertise. Fixes bug 5151; bugfix on 0.2.3.9-alpha.
4247 - In the testsuite, provide a large enough buffer in the tor_sscanf
4248 unit test. Otherwise we'd overrun that buffer and crash during
4249 the unit tests. Found by weasel. Fixes bug 5449; bugfix on
4251 - Make sure we create the keys directory if it doesn't exist and we're
4252 about to store the dynamic Diffie-Hellman parameters. Fixes bug
4253 5572; bugfix on 0.2.3.13-alpha.
4254 - Fix a small memory leak when trying to decode incorrect base16
4255 authenticator during SAFECOOKIE authentication. Found by
4256 Coverity Scan. Fixes CID 507. Bugfix on 0.2.3.13-alpha.
4259 - Add more information to a log statement that might help track down
4260 bug 4091. If you're seeing "Bug: tor_addr_is_internal() called with a
4261 non-IP address" messages (or any Bug messages, for that matter!),
4262 please let us know about it.
4263 - Relays now understand an IPv6 address when they get one from a
4264 directory server. Resolves ticket 4875.
4265 - Resolve IPv6 addresses in bridge and entry statistics to country
4266 code "??" which means we at least count them. Resolves ticket 5053;
4267 improves on 0.2.3.9-alpha.
4268 - Update to the April 3 2012 Maxmind GeoLite Country database.
4269 - Begin a doc/state-contents.txt file to explain the contents of
4270 the Tor state file. Fixes bug 2987.
4272 o Default torrc changes:
4273 - Stop listing "socksport 9050" in torrc.sample. We open a socks
4274 port on 9050 by default anyway, so this should not change anything
4276 - Stop mentioning the deprecated *ListenAddress options in
4277 torrc.sample. Fixes bug 5438.
4278 - Document unit of bandwidth related options in sample torrc.
4282 - The "torify" script no longer supports the "tsocks" socksifier
4283 tool, since tsocks doesn't support DNS and UDP right for Tor.
4284 Everyone should be using torsocks instead. Fixes bugs 3530 and
4285 5180. Based on a patch by "ugh".
4288 - Change the symmetric cipher interface so that creating and
4289 initializing a stream cipher are no longer separate functions.
4290 - Remove all internal support for unpadded RSA. We never used it, and
4291 it would be a bad idea to start.
4294 Changes in version 0.2.3.13-alpha - 2012-03-26
4295 Tor 0.2.3.13-alpha fixes a variety of stability and correctness bugs
4296 in managed pluggable transports, as well as providing other cleanups
4297 that get us closer to a release candidate.
4299 o Directory authority changes:
4300 - Change IP address for maatuska (v3 directory authority).
4303 - Provide controllers with a safer way to implement the cookie
4304 authentication mechanism. With the old method, if another locally
4305 running program could convince a controller that it was the Tor
4306 process, then that program could trick the controller into telling
4307 it the contents of an arbitrary 32-byte file. The new "SAFECOOKIE"
4308 authentication method uses a challenge-response approach to prevent
4309 this attack. Fixes bug 5185, implements proposal 193.
4310 - Never use a bridge or a controller-supplied node as an exit, even
4311 if its exit policy allows it. Found by wanoskarnet. Fixes bug
4312 5342. Bugfix on 0.1.1.15-rc (for controller-purpose descriptors)
4313 and 0.2.0.3-alpha (for bridge-purpose descriptors).
4314 - Only build circuits if we have a sufficient threshold of the total
4315 descriptors that are marked in the consensus with the "Exit"
4316 flag. This mitigates an attack proposed by wanoskarnet, in which
4317 all of a client's bridges collude to restrict the exit nodes that
4318 the client knows about. Fixes bug 5343.
4320 o Major bugfixes (on Tor 0.2.3.x):
4321 - Avoid an assert when managed proxies like obfsproxy are configured,
4322 and we receive HUP signals or setconf attempts too rapidly. This
4323 situation happens most commonly when Vidalia tries to attach to
4324 Tor or tries to configure the Tor it's attached to. Fixes bug 5084;
4325 bugfix on 0.2.3.6-alpha.
4326 - Fix a relay-side pluggable transports bug where managed proxies were
4327 unreachable from the Internet, because Tor asked them to bind on
4328 localhost. Fixes bug 4725; bugfix on 0.2.3.9-alpha.
4329 - Stop discarding command-line arguments when TestingTorNetwork
4330 is set. Discovered by Kevin Bauer. Fixes bug 5373; bugfix on
4331 0.2.3.9-alpha, where task 4552 added support for two layers of
4333 - Resume allowing the unit tests to run in gdb. This was accidentally
4334 made impossible when the DisableDebuggerAttachment option was
4335 introduced. Fixes bug 5448; bugfix on 0.2.3.9-alpha.
4336 - Resume building with nat-pmp support. Fixes bug 4955; bugfix on
4337 0.2.3.11-alpha. Reported by Anthony G. Basile.
4339 o Minor bugfixes (on 0.2.2.x and earlier):
4340 - Ensure we don't cannibalize circuits that are longer than three hops
4341 already, so we don't end up making circuits with 5 or more
4342 hops. Patch contributed by wanoskarnet. Fixes bug 5231; bugfix on
4343 0.1.0.1-rc which introduced cannibalization.
4344 - Detect and reject certain misformed escape sequences in
4345 configuration values. Previously, these values would cause us
4346 to crash if received in a torrc file or over an authenticated
4347 control port. Bug found by Esteban Manchado Velázquez, and
4348 independently by Robert Connolly from Matta Consulting who further
4349 noted that it allows a post-authentication heap overflow. Patch
4350 by Alexander Schrijver. Fixes bugs 5090 and 5402 (CVE 2012-1668);
4351 bugfix on 0.2.0.16-alpha.
4352 - Fix a compile warning when using the --enable-openbsd-malloc
4353 configure option. Fixes bug 5340; bugfix on 0.2.0.20-rc.
4354 - Directory caches no longer refuse to clean out descriptors because
4355 of missing v2 networkstatus documents, unless they're configured
4356 to retrieve v2 networkstatus documents. Fixes bug 4838; bugfix on
4357 0.2.2.26-beta. Patch by Daniel Bryg.
4358 - Update to the latest version of the tinytest unit testing framework.
4359 This includes a couple of bugfixes that can be relevant for
4360 running forked unit tests on Windows, and removes all reserved
4363 o Minor bugfixes (on 0.2.3.x):
4364 - On a failed pipe() call, don't leak file descriptors. Fixes bug
4365 4296; bugfix on 0.2.3.1-alpha.
4366 - Spec conformance: on a v3 handshake, do not send a NETINFO cell
4367 until after we have received a CERTS cell. Fixes bug 4361; bugfix
4368 on 0.2.3.6-alpha. Patch by "frosty".
4369 - When binding to an IPv6 address, set the IPV6_V6ONLY socket
4370 option, so that the IP stack doesn't decide to use it for IPv4
4371 too. Fixes bug 4760; bugfix on 0.2.3.9-alpha.
4372 - Ensure that variables set in Tor's environment cannot override
4373 environment variables that Tor passes to a managed
4374 pluggable-transport proxy. Previously, Tor would pass every
4375 variable in its environment to managed proxies along with the new
4376 ones, in such a way that on many operating systems, the inherited
4377 environment variables would override those which Tor tried to
4378 explicitly set. Bugfix on 0.2.3.12-alpha for most Unixoid systems;
4379 bugfix on 0.2.3.9-alpha for Windows.
4382 - A wide variety of new unit tests by Esteban Manchado Velázquez.
4383 - Shorten links in the tor-exit-notice file. Patch by Christian Kujau.
4384 - Update to the March 6 2012 Maxmind GeoLite Country database.
4387 Changes in version 0.2.3.12-alpha - 2012-02-13
4388 Tor 0.2.3.12-alpha lets fast exit relays scale better, allows clients
4389 to use bridges that run Tor 0.2.2.x, and resolves several big bugs
4390 when Tor is configured to use a pluggable transport like obfsproxy.
4393 - Fix builds when the path to sed, openssl, or sha1sum contains
4394 spaces, which is pretty common on Windows. Fixes bug 5065; bugfix
4396 - Set the SO_REUSEADDR socket option before we call bind() on outgoing
4397 connections. This change should allow busy exit relays to stop
4398 running out of available sockets as quickly. Fixes bug 4950;
4399 bugfix on 0.2.2.26-beta.
4400 - Allow 0.2.3.x clients to use 0.2.2.x bridges. Previously the client
4401 would ask the bridge for microdescriptors, which are only supported
4402 in 0.2.3.x, and then fail to bootstrap when it didn't get the
4403 answers it wanted. Fixes bug 4013; bugfix on 0.2.3.2-alpha.
4404 - Properly set up obfsproxy's environment when in managed mode. The
4405 Tor Browser Bundle needs LD_LIBRARY_PATH to be passed to obfsproxy,
4406 and when you run your Tor as a daemon, there's no HOME. Fixes bugs
4407 5076 and 5082; bugfix on 0.2.3.6-alpha.
4410 - Use the dead_strip option when building Tor on OS X. This reduces
4411 binary size by almost 19% when linking openssl and libevent
4412 statically, which we do for Tor Browser Bundle.
4413 - Fix broken URLs in the sample torrc file, and tell readers about
4414 the OutboundBindAddress, ExitPolicyRejectPrivate, and
4415 PublishServerDescriptor options. Addresses bug 4652.
4416 - Update to the February 7 2012 Maxmind GeoLite Country database.
4419 - Downgrade the "We're missing a certificate" message from notice
4420 to info: people kept mistaking it for a real problem, whereas it
4421 is seldom the problem even when we are failing to bootstrap. Fixes
4422 bug 5067; bugfix on 0.2.0.10-alpha.
4423 - Don't put "TOR_PT_EXTENDED_SERVER_PORT=127.0.0.1:4200" in a
4424 managed pluggable transport server proxy's environment.
4425 Previously, we would put it there, even though Tor doesn't
4426 implement an 'extended server port' yet, and even though Tor
4427 almost certainly isn't listening at that address. For now, we set
4428 it to an empty string to avoid crashing older obfsproxies. Bugfix
4430 - Log the heartbeat message every HeartbeatPeriod seconds, not every
4431 HeartbeatPeriod + 1 seconds. Fixes bug 4942; bugfix on
4432 0.2.3.1-alpha. Bug reported by Scott Bennett.
4433 - Calculate absolute paths correctly on Windows. Fixes bug 4973;
4434 bugfix on 0.2.3.11-alpha.
4435 - Update "ClientOnly" man page entry to explain that there isn't
4436 really any point to messing with it. Resolves ticket 5005.
4437 - Use the correct CVE number for CVE-2011-4576 in our comments and
4438 log messages. Found by "fermenthor". Resolves bug 5066; bugfix on
4441 o Code simplifications and refactoring:
4442 - Use the _WIN32 macro throughout our code to detect Windows.
4443 (Previously we had used the obsolete 'WIN32' and the idiosyncratic
4447 Changes in version 0.2.3.11-alpha - 2012-01-22
4448 Tor 0.2.3.11-alpha marks feature-freeze for the 0.2.3 tree. It deploys
4449 the last step of the plan to limit maximum circuit length, includes
4450 a wide variety of hidden service performance and correctness fixes,
4451 works around an OpenSSL security flaw if your distro is too stubborn
4452 to upgrade, and fixes a bunch of smaller issues.
4455 - Now that Tor 0.2.0.x is completely deprecated, enable the final
4456 part of "Proposal 110: Avoiding infinite length circuits" by
4457 refusing all circuit-extend requests that do not use a relay_early
4458 cell. This change helps Tor resist a class of denial-of-service
4459 attacks by limiting the maximum circuit length.
4460 - Adjust the number of introduction points that a hidden service
4461 will try to maintain based on how long its introduction points
4462 remain in use and how many introductions they handle. Fixes
4464 - Try to use system facilities for enumerating local interface
4465 addresses, before falling back to our old approach (which was
4466 binding a UDP socket, and calling getsockname() on it). That
4467 approach was scaring OS X users whose draconian firewall
4468 software warned about binding to UDP sockets, regardless of
4469 whether packets were sent. Now we try to use getifaddrs(),
4470 SIOCGIFCONF, or GetAdaptersAddresses(), depending on what the
4471 system supports. Resolves ticket 1827.
4473 o Major security workaround:
4474 - When building or running with any version of OpenSSL earlier
4475 than 0.9.8s or 1.0.0f, disable SSLv3 support. These OpenSSL
4476 versions have a bug (CVE-2011-4576) in which their block cipher
4477 padding includes uninitialized data, potentially leaking sensitive
4478 information to any peer with whom they make a SSLv3 connection. Tor
4479 does not use SSL v3 by default, but a hostile client or server
4480 could force an SSLv3 connection in order to gain information that
4481 they shouldn't have been able to get. The best solution here is to
4482 upgrade to OpenSSL 0.9.8s or 1.0.0f (or later). But when building
4483 or running with a non-upgraded OpenSSL, we disable SSLv3 entirely
4484 to make sure that the bug can't happen.
4487 - Fix the SOCKET_OK test that we use to tell when socket
4488 creation fails so that it works on Win64. Fixes part of bug 4533;
4489 bugfix on 0.2.2.29-beta. Bug found by wanoskarnet.
4490 - Correct our replacements for the timeradd() and timersub() functions
4491 on platforms that lack them (for example, Windows). The timersub()
4492 function is used when expiring circuits, while timeradd() is
4493 currently unused. Bug report and patch by Vektor. Fixes bug 4778;
4494 bugfix on 0.2.2.24-alpha and 0.2.3.1-alpha.
4495 - Do not use OpenSSL 1.0.0's counter mode: it has a critical bug
4496 that was fixed in OpenSSL 1.0.0a. We test for the counter mode
4497 bug at runtime, not compile time, because some distributions hack
4498 their OpenSSL to mis-report its version. Fixes bug 4779; bugfix
4499 on 0.2.3.9-alpha. Found by Pascal.
4501 o Minor features (controller):
4502 - Use absolute path names when reporting the torrc filename in the
4503 control protocol, so a controller can more easily find the torrc
4504 file. Resolves bug 1101.
4505 - Extend the control protocol to report flags that control a circuit's
4506 path selection in CIRC events and in replies to 'GETINFO
4507 circuit-status'. Implements part of ticket 2411.
4508 - Extend the control protocol to report the hidden service address
4509 and current state of a hidden-service-related circuit in CIRC
4510 events and in replies to 'GETINFO circuit-status'. Implements part
4512 - When reporting the path to the cookie file to the controller,
4513 give an absolute path. Resolves ticket 4881.
4514 - Allow controllers to request an event notification whenever a
4515 circuit is cannibalized or its purpose is changed. Implements
4516 part of ticket 3457.
4517 - Include the creation time of a circuit in CIRC and CIRC2
4518 control-port events and the list produced by the 'GETINFO
4519 circuit-status' control-port command.
4521 o Minor features (directory authorities):
4522 - Directory authorities now reject versions of Tor older than
4523 0.2.1.30, and Tor versions between 0.2.2.1-alpha and 0.2.2.20-alpha
4524 inclusive. These versions accounted for only a small fraction of
4525 the Tor network, and have numerous known security issues. Resolves
4527 - Authority operators can now vote for all relays in a given
4528 set of countries to be BadDir/BadExit/Invalid/Rejected.
4529 - Provide two consensus parameters (FastFlagMinThreshold and
4530 FastFlagMaxThreshold) to control the range of allowable bandwidths
4531 for the Fast directory flag. These allow authorities to run
4532 experiments on appropriate requirements for being a "Fast" node.
4533 The AuthDirFastGuarantee config value still applies. Implements
4535 - Document the GiveGuardFlagTo_CVE_2011_2768_VulnerableRelays
4536 directory authority option (introduced in Tor 0.2.2.34).
4538 o Minor features (other):
4539 - Don't disable the DirPort when we cannot exceed our AccountingMax
4540 limit during this interval because the effective bandwidthrate is
4541 low enough. This is useful in a situation where AccountMax is only
4542 used as an additional safeguard or to provide statistics.
4543 - Prepend an informative header to generated dynamic_dh_params files.
4544 - If EntryNodes are given, but UseEntryGuards is set to 0, warn that
4545 EntryNodes will have no effect. Resolves issue 2571.
4546 - Log more useful messages when we fail to disable debugger
4548 - Log which authority we're missing votes from when we go to fetch
4549 them from the other auths.
4550 - Log (at debug level) whenever a circuit's purpose is changed.
4551 - Add missing documentation for the MaxClientCircuitsPending,
4552 UseMicrodescriptors, UserspaceIOCPBuffers, and
4553 _UseFilteringSSLBufferevents options, all introduced during
4555 - Update to the January 3 2012 Maxmind GeoLite Country database.
4557 o Minor bugfixes (hidden services):
4558 - Don't close hidden service client circuits which have almost
4559 finished connecting to their destination when they reach
4560 the normal circuit-build timeout. Previously, we would close
4561 introduction circuits which are waiting for an acknowledgement
4562 from the introduction point, and rendezvous circuits which have
4563 been specified in an INTRODUCE1 cell sent to a hidden service,
4564 after the normal CBT. Now, we mark them as 'timed out', and launch
4565 another rendezvous attempt in parallel. This behavior change can
4566 be disabled using the new CloseHSClientCircuitsImmediatelyOnTimeout
4567 option. Fixes part of bug 1297; bugfix on 0.2.2.2-alpha.
4568 - Don't close hidden-service-side rendezvous circuits when they
4569 reach the normal circuit-build timeout. This behaviour change can
4570 be disabled using the new
4571 CloseHSServiceRendCircuitsImmediatelyOnTimeout option. Fixes the
4572 remaining part of bug 1297; bugfix on 0.2.2.2-alpha.
4573 - Make sure we never mark the wrong rendezvous circuit as having
4574 had its introduction cell acknowleged by the introduction-point
4575 relay. Previously, when we received an INTRODUCE_ACK cell on a
4576 client-side hidden-service introduction circuit, we might have
4577 marked a rendezvous circuit other than the one we specified in
4578 the INTRODUCE1 cell as INTRO_ACKED, which would have produced
4579 a warning message and interfered with the hidden service
4580 connection-establishment process. Fixes bug 4759; bugfix on
4581 0.2.3.3-alpha, when we added the stream-isolation feature which
4582 might cause Tor to open multiple rendezvous circuits for the same
4584 - Don't trigger an assertion failure when we mark a new client-side
4585 hidden-service introduction circuit for close during the process
4586 of creating it. Fixes bug 4796; bugfix on 0.2.3.6-alpha. Reported
4589 o Minor bugfixes (log messages):
4590 - Correctly spell "connect" in a log message on failure to create a
4591 controlsocket. Fixes bug 4803; bugfix on 0.2.2.26-beta and
4593 - Fix a typo in a log message in rend_service_rendezvous_has_opened().
4594 Fixes bug 4856; bugfix on Tor 0.0.6.
4595 - Fix the log message describing how we work around discovering
4596 that our version is the ill-fated OpenSSL 0.9.8l. Fixes bug
4597 4837; bugfix on 0.2.2.9-alpha.
4598 - When logging about a disallowed .exit name, do not also call it
4599 an "invalid onion address". Fixes bug 3325; bugfix on 0.2.2.9-alpha.
4601 o Minor bugfixes (build fixes):
4602 - During configure, detect when we're building with clang version
4603 3.0 or lower and disable the -Wnormalized=id and -Woverride-init
4604 CFLAGS. clang doesn't support them yet.
4605 - During configure, search for library containing cos function as
4606 libm lives in libcore on some platforms (BeOS/Haiku). Linking
4607 against libm was hard-coded before. Fixes the first part of bug
4608 4727; bugfix on 0.2.2.2-alpha. Patch and analysis by Martin Hebnes
4610 - Detect attempts to build Tor on (as yet hypothetical) versions
4611 of Windows where sizeof(intptr_t) != sizeof(SOCKET). Partial
4612 fix for bug 4533. Bugfix on 0.2.2.28-beta.
4613 - Preprocessor directives should not be put inside the arguments
4614 of a macro. This would break compilation with GCC releases prior
4615 to version 3.3. We would never recommend such an old GCC version,
4616 but it is apparently required for binary compatibility on some
4617 platforms (namely, certain builds of Haiku). Fixes the other part
4618 of bug 4727; bugfix on 0.2.3.3-alpha. Patch and analysis by Martin
4621 o Minor bugfixes (other):
4622 - Older Linux kernels erroneously respond to strange nmap behavior
4623 by having accept() return successfully with a zero-length
4624 socket. When this happens, just close the connection. Previously,
4625 we would try harder to learn the remote address: but there was
4626 no such remote address to learn, and our method for trying to
4627 learn it was incorrect. Fixes bugs 1240, 4745, and 4747. Bugfix
4628 on 0.1.0.3-rc. Reported and diagnosed by "r1eo".
4629 - Fix null-pointer access that could occur if TLS allocation failed.
4630 Fixes bug 4531; bugfix on 0.2.0.20-rc. Found by "troll_un". This was
4631 erroneously listed as fixed in 0.2.3.9-alpha, but the fix had
4632 accidentally been reverted.
4633 - Fix our implementation of crypto_random_hostname() so it can't
4634 overflow on ridiculously large inputs. (No Tor version has ever
4635 provided this kind of bad inputs, but let's be correct in depth.)
4636 Fixes bug 4413; bugfix on 0.2.2.9-alpha. Fix by Stephen Palmateer.
4637 - Find more places in the code that should have been testing for
4638 invalid sockets using the SOCKET_OK macro. Required for a fix
4639 for bug 4533. Bugfix on 0.2.2.28-beta.
4640 - Fix an assertion failure when, while running with bufferevents, a
4641 connection finishes connecting after it is marked for close, but
4642 before it is closed. Fixes bug 4697; bugfix on 0.2.3.1-alpha.
4643 - test_util_spawn_background_ok() hardcoded the expected value
4644 for ENOENT to 2. This isn't portable as error numbers are
4645 platform specific, and particularly the hurd has ENOENT at
4646 0x40000002. Construct expected string at runtime, using the correct
4647 value for ENOENT. Fixes bug 4733; bugfix on 0.2.3.1-alpha.
4648 - Reject attempts to disable DisableDebuggerAttachment while Tor is
4649 running. Fixes bug 4650; bugfix on 0.2.3.9-alpha.
4650 - Use an appropriate-width type for sockets in tor-fw-helper on
4651 win64. Fixes bug 1983 at last. Bugfix on 0.2.3.9-alpha.
4654 - When sending or relaying a RELAY_EARLY cell, we used to convert
4655 it to a RELAY cell if the connection was using the v1 link
4656 protocol. This was a workaround for older versions of Tor, which
4657 didn't handle RELAY_EARLY cells properly. Now that all supported
4658 versions can handle RELAY_EARLY cells, and now that we're enforcing
4659 the "no RELAY_EXTEND commands except in RELAY_EARLY cells" rule,
4660 remove this workaround. Addresses bug 4786.
4662 o Code simplifications and refactoring:
4663 - Use OpenSSL's built-in SSL_state_string_long() instead of our
4664 own homebrewed ssl_state_to_string() replacement. Patch from
4665 Emile Snyder. Fixes bug 4653.
4666 - Use macros to indicate OpenSSL versions, so we don't need to worry
4667 about accidental hexadecimal bit shifts.
4668 - Remove some workaround code for OpenSSL 0.9.6 (which is no longer
4670 - Convert more instances of tor_snprintf+tor_strdup into tor_asprintf.
4671 - Use the smartlist_add_asprintf() alias more consistently.
4672 - Use a TOR_INVALID_SOCKET macro when initializing a socket to an
4673 invalid value, rather than just -1.
4674 - Rename a handful of old identifiers, mostly related to crypto
4675 structures and crypto functions. By convention, our "create an
4676 object" functions are called "type_new()", our "free an object"
4677 functions are called "type_free()", and our types indicate that
4678 they are types only with a final "_t". But a handful of older
4679 types and functions broke these rules, with function names like
4680 "type_create" or "subsystem_op_type", or with type names like
4684 Changes in version 0.2.3.10-alpha - 2011-12-16
4685 Tor 0.2.3.10-alpha fixes a critical heap-overflow security issue in
4686 Tor's buffers code. Absolutely everybody should upgrade.
4688 The bug relied on an incorrect calculation when making data continuous
4689 in one of our IO buffers, if the first chunk of the buffer was
4690 misaligned by just the wrong amount. The miscalculation would allow an
4691 attacker to overflow a piece of heap-allocated memory. To mount this
4692 attack, the attacker would need to either open a SOCKS connection to
4693 Tor's SocksPort (usually restricted to localhost), or target a Tor
4694 instance configured to make its connections through a SOCKS proxy
4695 (which Tor does not do by default).
4697 Good security practice requires that all heap-overflow bugs should be
4698 presumed to be exploitable until proven otherwise, so we are treating
4699 this as a potential code execution attack. Please upgrade immediately!
4700 This bug does not affect bufferevents-based builds of Tor. Special
4701 thanks to "Vektor" for reporting this issue to us!
4703 This release also contains a few minor bugfixes for issues discovered
4707 - Fix a heap overflow bug that could occur when trying to pull
4708 data into the first chunk of a buffer, when that chunk had
4709 already had some data drained from it. Fixes CVE-2011-2778;
4710 bugfix on 0.2.0.16-alpha. Reported by "Vektor".
4713 - If we can't attach streams to a rendezvous circuit when we
4714 finish connecting to a hidden service, clear the rendezvous
4715 circuit's stream-isolation state and try to attach streams
4716 again. Previously, we cleared rendezvous circuits' isolation
4717 state either too early (if they were freshly built) or not at all
4718 (if they had been built earlier and were cannibalized). Bugfix on
4719 0.2.3.3-alpha; fixes bug 4655.
4720 - Fix compilation of the libnatpmp helper on non-Windows. Bugfix on
4721 0.2.3.9-alpha; fixes bug 4691. Reported by Anthony G. Basile.
4722 - Fix an assertion failure when a relay with accounting enabled
4723 starts up while dormant. Fixes bug 4702; bugfix on 0.2.3.9-alpha.
4726 - Update to the December 6 2011 Maxmind GeoLite Country database.
4729 Changes in version 0.2.2.35 - 2011-12-16
4730 Tor 0.2.2.35 fixes a critical heap-overflow security issue in Tor's
4731 buffers code. Absolutely everybody should upgrade.
4733 The bug relied on an incorrect calculation when making data continuous
4734 in one of our IO buffers, if the first chunk of the buffer was
4735 misaligned by just the wrong amount. The miscalculation would allow an
4736 attacker to overflow a piece of heap-allocated memory. To mount this
4737 attack, the attacker would need to either open a SOCKS connection to
4738 Tor's SocksPort (usually restricted to localhost), or target a Tor
4739 instance configured to make its connections through a SOCKS proxy
4740 (which Tor does not do by default).
4742 Good security practice requires that all heap-overflow bugs should be
4743 presumed to be exploitable until proven otherwise, so we are treating
4744 this as a potential code execution attack. Please upgrade immediately!
4745 This bug does not affect bufferevents-based builds of Tor. Special
4746 thanks to "Vektor" for reporting this issue to us!
4748 Tor 0.2.2.35 also fixes several bugs in previous versions, including
4749 crash bugs for unusual configurations, and a long-term bug that
4750 would prevent Tor from starting on Windows machines with draconian
4753 With this release, we remind everyone that 0.2.0.x has reached its
4754 formal end-of-life. Those Tor versions have many known flaws, and
4755 nobody should be using them. You should upgrade -- ideally to the
4756 0.2.2.x series. If you're using a Linux or BSD and its packages are
4757 obsolete, stop using those packages and upgrade anyway.
4759 The Tor 0.2.1.x series is also approaching its end-of-life: it will no
4760 longer receive support after some time in early 2012.
4763 - Fix a heap overflow bug that could occur when trying to pull
4764 data into the first chunk of a buffer, when that chunk had
4765 already had some data drained from it. Fixes CVE-2011-2778;
4766 bugfix on 0.2.0.16-alpha. Reported by "Vektor".
4767 - Initialize Libevent with the EVENT_BASE_FLAG_NOLOCK flag enabled, so
4768 that it doesn't attempt to allocate a socketpair. This could cause
4769 some problems on Windows systems with overzealous firewalls. Fix for
4770 bug 4457; workaround for Libevent versions 2.0.1-alpha through
4772 - If we mark an OR connection for close based on a cell we process,
4773 don't process any further cells on it. We already avoid further
4774 reads on marked-for-close connections, but now we also discard the
4775 cells we'd already read. Fixes bug 4299; bugfix on 0.2.0.10-alpha,
4776 which was the first version where we might mark a connection for
4777 close based on processing a cell on it.
4778 - Correctly sanity-check that we don't underflow on a memory
4779 allocation (and then assert) for hidden service introduction
4780 point decryption. Bug discovered by Dan Rosenberg. Fixes bug 4410;
4781 bugfix on 0.2.1.5-alpha.
4782 - Fix a memory leak when we check whether a hidden service
4783 descriptor has any usable introduction points left. Fixes bug
4784 4424. Bugfix on 0.2.2.25-alpha.
4785 - Don't crash when we're running as a relay and don't have a GeoIP
4786 file. Bugfix on 0.2.2.34; fixes bug 4340. This backports a fix
4787 we've had in the 0.2.3.x branch already.
4788 - When running as a client, do not print a misleading (and plain
4789 wrong) log message that we're collecting "directory request"
4790 statistics: clients don't collect statistics. Also don't create a
4791 useless (because empty) stats file in the stats/ directory. Fixes
4792 bug 4353; bugfix on 0.2.2.34.
4795 - Detect failure to initialize Libevent. This fix provides better
4796 detection for future instances of bug 4457.
4797 - Avoid frequent calls to the fairly expensive cull_wedged_cpuworkers
4798 function. This was eating up hideously large amounts of time on some
4799 busy servers. Fixes bug 4518; bugfix on 0.0.9.8.
4800 - Resolve an integer overflow bug in smartlist_ensure_capacity().
4801 Fixes bug 4230; bugfix on Tor 0.1.0.1-rc. Based on a patch by
4803 - Don't warn about unused log_mutex in log.c when building with
4804 --disable-threads using a recent GCC. Fixes bug 4437; bugfix on
4805 0.1.0.6-rc which introduced --disable-threads.
4806 - When configuring, starting, or stopping an NT service, stop
4807 immediately after the service configuration attempt has succeeded
4808 or failed. Fixes bug 3963; bugfix on 0.2.0.7-alpha.
4809 - When sending a NETINFO cell, include the original address
4810 received for the other side, not its canonical address. Found
4811 by "troll_un"; fixes bug 4349; bugfix on 0.2.0.10-alpha.
4812 - Fix a typo in a hibernation-related log message. Fixes bug 4331;
4813 bugfix on 0.2.2.23-alpha; found by "tmpname0901".
4814 - Fix a memory leak in launch_direct_bridge_descriptor_fetch() that
4815 occurred when a client tried to fetch a descriptor for a bridge
4816 in ExcludeNodes. Fixes bug 4383; bugfix on 0.2.2.25-alpha.
4817 - Backport fixes for a pair of compilation warnings on Windows.
4818 Fixes bug 4521; bugfix on 0.2.2.28-beta and on 0.2.2.29-beta.
4819 - If we had ever tried to call tor_addr_to_str on an address of
4820 unknown type, we would have done a strdup on an uninitialized
4821 buffer. Now we won't. Fixes bug 4529; bugfix on 0.2.1.3-alpha.
4822 Reported by "troll_un".
4823 - Correctly detect and handle transient lookup failures from
4824 tor_addr_lookup. Fixes bug 4530; bugfix on 0.2.1.5-alpha.
4825 Reported by "troll_un".
4826 - Fix null-pointer access that could occur if TLS allocation failed.
4827 Fixes bug 4531; bugfix on 0.2.0.20-rc. Found by "troll_un".
4828 - Use tor_socket_t type for listener argument to accept(). Fixes bug
4829 4535; bugfix on 0.2.2.28-beta. Found by "troll_un".
4832 - Add two new config options for directory authorities:
4833 AuthDirFastGuarantee sets a bandwidth threshold for guaranteeing the
4834 Fast flag, and AuthDirGuardBWGuarantee sets a bandwidth threshold
4835 that is always sufficient to satisfy the bandwidth requirement for
4836 the Guard flag. Now it will be easier for researchers to simulate
4837 Tor networks with different values. Resolves ticket 4484.
4838 - When Tor ignores a hidden service specified in its configuration,
4839 include the hidden service's directory in the warning message.
4840 Previously, we would only tell the user that some hidden service
4841 was ignored. Bugfix on 0.0.6; fixes bug 4426.
4842 - Update to the December 6 2011 Maxmind GeoLite Country database.
4844 o Packaging changes:
4845 - Make it easier to automate expert package builds on Windows,
4846 by removing an absolute path from makensis.exe command.
4849 Changes in version 0.2.1.32 - 2011-12-16
4850 Tor 0.2.1.32 backports important security and privacy fixes for
4851 oldstable. This release is intended only for package maintainers and
4852 others who cannot use the 0.2.2 stable series. All others should be
4853 using Tor 0.2.2.x or newer.
4855 The Tor 0.2.1.x series will reach formal end-of-life some time in
4856 early 2012; we will stop releasing patches for it then.
4858 o Major bugfixes (also included in 0.2.2.x):
4859 - Correctly sanity-check that we don't underflow on a memory
4860 allocation (and then assert) for hidden service introduction
4861 point decryption. Bug discovered by Dan Rosenberg. Fixes bug 4410;
4862 bugfix on 0.2.1.5-alpha.
4863 - Fix a heap overflow bug that could occur when trying to pull
4864 data into the first chunk of a buffer, when that chunk had
4865 already had some data drained from it. Fixes CVE-2011-2778;
4866 bugfix on 0.2.0.16-alpha. Reported by "Vektor".
4869 - Update to the December 6 2011 Maxmind GeoLite Country database.
4872 Changes in version 0.2.3.9-alpha - 2011-12-08
4873 Tor 0.2.3.9-alpha introduces initial IPv6 support for bridges, adds
4874 a "DisableNetwork" security feature that bundles can use to avoid
4875 touching the network until bridges are configured, moves forward on
4876 the pluggable transport design, fixes a flaw in the hidden service
4877 design that unnecessarily prevented clients with wrong clocks from
4878 reaching hidden services, and fixes a wide variety of other issues.
4881 - Clients can now connect to private bridges over IPv6. Bridges
4882 still need at least one IPv4 address in order to connect to
4883 other relays. Note that we don't yet handle the case where the
4884 user has two bridge lines for the same bridge (one IPv4, one
4885 IPv6). Implements parts of proposal 186.
4886 - New "DisableNetwork" config option to prevent Tor from launching any
4887 connections or accepting any connections except on a control port.
4888 Bundles and controllers can set this option before letting Tor talk
4889 to the rest of the network, for example to prevent any connections
4890 to a non-bridge address. Packages like Orbot can also use this
4891 option to instruct Tor to save power when the network is off.
4892 - Clients and bridges can now be configured to use a separate
4893 "transport" proxy. This approach makes the censorship arms race
4894 easier by allowing bridges to use protocol obfuscation plugins. It
4895 implements the "managed proxy" part of proposal 180 (ticket 3472).
4896 - When using OpenSSL 1.0.0 or later, use OpenSSL's counter mode
4897 implementation. It makes AES_CTR about 7% faster than our old one
4898 (which was about 10% faster than the one OpenSSL used to provide).
4899 Resolves ticket 4526.
4900 - Add a "tor2web mode" for clients that want to connect to hidden
4901 services non-anonymously (and possibly more quickly). As a safety
4902 measure to try to keep users from turning this on without knowing
4903 what they are doing, tor2web mode must be explicitly enabled at
4904 compile time, and a copy of Tor compiled to run in tor2web mode
4905 cannot be used as a normal Tor client. Implements feature 2553.
4906 - Add experimental support for running on Windows with IOCP and no
4907 kernel-space socket buffers. This feature is controlled by a new
4908 "UserspaceIOCPBuffers" config option (off by default), which has
4909 no effect unless Tor has been built with support for bufferevents,
4910 is running on Windows, and has enabled IOCP. This may, in the long
4911 run, help solve or mitigate bug 98.
4912 - Use a more secure consensus parameter voting algorithm. Now at
4913 least three directory authorities or a majority of them must
4914 vote on a given parameter before it will be included in the
4915 consensus. Implements proposal 178.
4918 - Hidden services now ignore the timestamps on INTRODUCE2 cells.
4919 They used to check that the timestamp was within 30 minutes
4920 of their system clock, so they could cap the size of their
4921 replay-detection cache, but that approach unnecessarily refused
4922 service to clients with wrong clocks. Bugfix on 0.2.1.6-alpha, when
4923 the v3 intro-point protocol (the first one which sent a timestamp
4924 field in the INTRODUCE2 cell) was introduced; fixes bug 3460.
4925 - Only use the EVP interface when AES acceleration is enabled,
4926 to avoid a 5-7% performance regression. Resolves issue 4525;
4927 bugfix on 0.2.3.8-alpha.
4929 o Privacy/anonymity features (bridge detection):
4930 - Make bridge SSL certificates a bit more stealthy by using random
4931 serial numbers, in the same fashion as OpenSSL when generating
4932 self-signed certificates. Implements ticket 4584.
4933 - Introduce a new config option "DynamicDHGroups", enabled by
4934 default, which provides each bridge with a unique prime DH modulus
4935 to be used during SSL handshakes. This option attempts to help
4936 against censors who might use the Apache DH modulus as a static
4937 identifier for bridges. Addresses ticket 4548.
4939 o Minor features (new/different config options):
4940 - New configuration option "DisableDebuggerAttachment" (on by default)
4941 to prevent basic debugging attachment attempts by other processes.
4942 Supports Mac OS X and Gnu/Linux. Resolves ticket 3313.
4943 - Allow MapAddress directives to specify matches against super-domains,
4944 as in "MapAddress *.torproject.org *.torproject.org.torserver.exit".
4945 Implements issue 933.
4946 - Slightly change behavior of "list" options (that is, config
4947 options that can appear more than once) when they appear both in
4948 torrc and on the command line. Previously, the command-line options
4949 would be appended to the ones from torrc. Now, the command-line
4950 options override the torrc options entirely. This new behavior
4951 allows the user to override list options (like exit policies and
4952 ports to listen on) from the command line, rather than simply
4953 appending to the list.
4954 - You can get the old (appending) command-line behavior for "list"
4955 options by prefixing the option name with a "+".
4956 - You can remove all the values for a "list" option from the command
4957 line without adding any new ones by prefixing the option name
4959 - Add experimental support for a "defaults" torrc file to be parsed
4960 before the regular torrc. Torrc options override the defaults file's
4961 options in the same way that the command line overrides the torrc.
4962 The SAVECONF controller command saves only those options which
4963 differ between the current configuration and the defaults file. HUP
4964 reloads both files. (Note: This is an experimental feature; its
4965 behavior will probably be refined in future 0.2.3.x-alpha versions
4966 to better meet packagers' needs.) Implements task 4552.
4969 - Try to make the introductory warning message that Tor prints on
4970 startup more useful for actually finding help and information.
4971 Resolves ticket 2474.
4972 - Running "make version" now displays the version of Tor that
4973 we're about to build. Idea from katmagic; resolves issue 4400.
4974 - Expire old or over-used hidden service introduction points.
4975 Required by fix for bug 3460.
4976 - Move the replay-detection cache for the RSA-encrypted parts of
4977 INTRODUCE2 cells to the introduction point data structures.
4978 Previously, we would use one replay-detection cache per hidden
4979 service. Required by fix for bug 3460.
4980 - Reduce the lifetime of elements of hidden services' Diffie-Hellman
4981 public key replay-detection cache from 60 minutes to 5 minutes. This
4982 replay-detection cache is now used only to detect multiple
4983 INTRODUCE2 cells specifying the same rendezvous point, so we can
4984 avoid launching multiple simultaneous attempts to connect to it.
4986 o Minor bugfixes (on Tor 0.2.2.x and earlier):
4987 - Resolve an integer overflow bug in smartlist_ensure_capacity().
4988 Fixes bug 4230; bugfix on Tor 0.1.0.1-rc. Based on a patch by
4990 - Fix a minor formatting issue in one of tor-gencert's error messages.
4992 - Prevent a false positive from the check-spaces script, by disabling
4993 the "whitespace between function name and (" check for functions
4995 - Fix a log message suggesting that people contact a non-existent
4996 email address. Fixes bug 3448.
4997 - Fix null-pointer access that could occur if TLS allocation failed.
4998 Fixes bug 4531; bugfix on 0.2.0.20-rc. Found by "troll_un".
4999 - Report a real bootstrap problem to the controller on router
5000 identity mismatch. Previously we just said "foo", which probably
5001 made a lot of sense at the time. Fixes bug 4169; bugfix on
5003 - If we had ever tried to call tor_addr_to_str() on an address of
5004 unknown type, we would have done a strdup() on an uninitialized
5005 buffer. Now we won't. Fixes bug 4529; bugfix on 0.2.1.3-alpha.
5006 Reported by "troll_un".
5007 - Correctly detect and handle transient lookup failures from
5008 tor_addr_lookup(). Fixes bug 4530; bugfix on 0.2.1.5-alpha.
5009 Reported by "troll_un".
5010 - Use tor_socket_t type for listener argument to accept(). Fixes bug
5011 4535; bugfix on 0.2.2.28-beta. Found by "troll_un".
5012 - Initialize conn->addr to a valid state in spawn_cpuworker(). Fixes
5013 bug 4532; found by "troll_un".
5015 o Minor bugfixes (on Tor 0.2.3.x):
5016 - Fix a compile warning in tor_inet_pton(). Bugfix on 0.2.3.8-alpha;
5018 - Don't send two ESTABLISH_RENDEZVOUS cells when opening a new
5019 circuit for use as a hidden service client's rendezvous point.
5020 Fixes bugs 4641 and 4171; bugfix on 0.2.3.3-alpha. Diagnosed
5021 with help from wanoskarnet.
5022 - Restore behavior of overriding SocksPort, ORPort, and similar
5023 options from the command line. Bugfix on 0.2.3.3-alpha.
5026 - Properly handle the case where the build-tree is not the same
5027 as the source tree when generating src/common/common_sha1.i,
5028 src/or/micro-revision.i, and src/or/or_sha1.i. Fixes bug 3953;
5029 bugfix on 0.2.0.1-alpha.
5031 o Code simplifications, cleanups, and refactorings:
5032 - Remove the pure attribute from all functions that used it
5033 previously. In many cases we assigned it incorrectly, because the
5034 functions might assert or call impure functions, and we don't have
5035 evidence that keeping the pure attribute is worthwhile. Implements
5036 changes suggested in ticket 4421.
5037 - Remove some dead code spotted by coverity. Fixes cid 432.
5038 Bugfix on 0.2.3.1-alpha, closes bug 4637.
5041 Changes in version 0.2.3.8-alpha - 2011-11-22
5042 Tor 0.2.3.8-alpha fixes some crash and assert bugs, including a
5043 socketpair-related bug that has been bothering Windows users. It adds
5044 support to serve microdescriptors to controllers, so Vidalia's network
5045 map can resume listing relays (once Vidalia implements its side),
5046 and adds better support for hardware AES acceleration. Finally, it
5047 starts the process of adjusting the bandwidth cutoff for getting the
5048 "Fast" flag from 20KB to (currently) 32KB -- preliminary results show
5049 that tiny relays harm performance more than they help network capacity.
5052 - Initialize Libevent with the EVENT_BASE_FLAG_NOLOCK flag enabled, so
5053 that it doesn't attempt to allocate a socketpair. This could cause
5054 some problems on Windows systems with overzealous firewalls. Fix for
5055 bug 4457; workaround for Libevent versions 2.0.1-alpha through
5057 - Correctly sanity-check that we don't underflow on a memory
5058 allocation (and then assert) for hidden service introduction
5059 point decryption. Bug discovered by Dan Rosenberg. Fixes bug 4410;
5060 bugfix on 0.2.1.5-alpha.
5061 - Remove the artificially low cutoff of 20KB to guarantee the Fast
5062 flag. In the past few years the average relay speed has picked
5063 up, and while the "top 7/8 of the network get the Fast flag" and
5064 "all relays with 20KB or more of capacity get the Fast flag" rules
5065 used to have the same result, now the top 7/8 of the network has
5066 a capacity more like 32KB. Bugfix on 0.2.1.14-rc. Fixes bug 4489.
5067 - Fix a rare assertion failure when checking whether a v0 hidden
5068 service descriptor has any usable introduction points left, and
5069 we don't have enough information to build a circuit to the first
5070 intro point named in the descriptor. The HS client code in
5071 0.2.3.x no longer uses v0 HS descriptors, but this assertion can
5072 trigger on (and crash) v0 HS authorities. Fixes bug 4411.
5073 Bugfix on 0.2.3.1-alpha; diagnosed by frosty_un.
5074 - Make bridge authorities not crash when they are asked for their own
5075 descriptor. Bugfix on 0.2.3.7-alpha, reported by Lucky Green.
5076 - When running as a client, do not print a misleading (and plain
5077 wrong) log message that we're collecting "directory request"
5078 statistics: clients don't collect statistics. Also don't create a
5079 useless (because empty) stats file in the stats/ directory. Fixes
5080 bug 4353; bugfix on 0.2.2.34 and 0.2.3.7-alpha.
5083 - Allow Tor controllers like Vidalia to obtain the microdescriptor
5084 for a relay by identity digest or nickname. Previously,
5085 microdescriptors were only available by their own digests, so a
5086 controller would have to ask for and parse the whole microdescriptor
5087 consensus in order to look up a single relay's microdesc. Fixes
5088 bug 3832; bugfix on 0.2.3.1-alpha.
5089 - Use OpenSSL's EVP interface for AES encryption, so that all AES
5090 operations can use hardware acceleration (if present). Resolves
5093 o Minor bugfixes (on 0.2.2.x and earlier):
5094 - Detect failure to initialize Libevent. This fix provides better
5095 detection for future instances of bug 4457.
5096 - Avoid frequent calls to the fairly expensive cull_wedged_cpuworkers
5097 function. This was eating up hideously large amounts of time on some
5098 busy servers. Fixes bug 4518; bugfix on 0.0.9.8.
5099 - Don't warn about unused log_mutex in log.c when building with
5100 --disable-threads using a recent GCC. Fixes bug 4437; bugfix on
5101 0.1.0.6-rc which introduced --disable-threads.
5102 - Allow manual 'authenticate' commands to the controller interface
5103 from netcat (nc) as well as telnet. We were rejecting them because
5104 they didn't come with the expected whitespace at the end of the
5105 command. Bugfix on 0.1.1.1-alpha; fixes bug 2893.
5106 - Fix some (not actually triggerable) buffer size checks in usage of
5107 tor_inet_ntop. Fixes bug 4434; bugfix on Tor 0.2.0.1-alpha. Patch
5109 - Fix parsing of some corner-cases with tor_inet_pton(). Fixes
5110 bug 4515; bugfix on 0.2.0.1-alpha; fix by Anders Sundman.
5111 - When configuring, starting, or stopping an NT service, stop
5112 immediately after the service configuration attempt has succeeded
5113 or failed. Fixes bug 3963; bugfix on 0.2.0.7-alpha.
5114 - When sending a NETINFO cell, include the original address
5115 received for the other side, not its canonical address. Found
5116 by "troll_un"; fixes bug 4349; bugfix on 0.2.0.10-alpha.
5117 - Rename the bench_{aes,dmap} functions to test_*, so that tinytest
5118 can pick them up when the tests aren't disabled. Bugfix on
5119 0.2.2.4-alpha which introduced tinytest.
5120 - Fix a memory leak when we check whether a hidden service
5121 descriptor has any usable introduction points left. Fixes bug
5122 4424. Bugfix on 0.2.2.25-alpha.
5123 - Fix a memory leak in launch_direct_bridge_descriptor_fetch() that
5124 occurred when a client tried to fetch a descriptor for a bridge
5125 in ExcludeNodes. Fixes bug 4383; bugfix on 0.2.2.25-alpha.
5127 o Minor bugfixes (on 0.2.3.x):
5128 - Make util unit tests build correctly with MSVC. Bugfix on
5129 0.2.3.3-alpha. Patch by Gisle Vanem.
5130 - Successfully detect AUTH_CHALLENGE cells with no recognized
5131 authentication type listed. Fixes bug 4367; bugfix on 0.2.3.6-alpha.
5133 - If a relay receives an AUTH_CHALLENGE cell it can't answer,
5134 it should still send a NETINFO cell to allow the connection to
5135 become open. Fixes bug 4368; fix on 0.2.3.6-alpha; bug found by
5137 - Log less loudly when we get an invalid authentication certificate
5138 from a source other than a directory authority: it's not unusual
5139 to see invalid certs because of clock skew. Fixes bug 4370; bugfix
5141 - Tolerate servers with more clock skew in their authentication
5142 certificates than previously. Fixes bug 4371; bugfix on
5144 - Fix a couple of compile warnings on Windows. Fixes bug 4469; bugfix
5145 on 0.2.3.4-alpha and 0.2.3.6-alpha.
5148 - Add two new config options for directory authorities:
5149 AuthDirFastGuarantee sets a bandwidth threshold for guaranteeing the
5150 Fast flag, and AuthDirGuardBWGuarantee sets a bandwidth threshold
5151 that is always sufficient to satisfy the bandwidth requirement for
5152 the Guard flag. Now it will be easier for researchers to simulate
5153 Tor networks with different values. Resolves ticket 4484.
5154 - When Tor ignores a hidden service specified in its configuration,
5155 include the hidden service's directory in the warning message.
5156 Previously, we would only tell the user that some hidden service
5157 was ignored. Bugfix on 0.0.6; fixes bug 4426.
5158 - When we fail to initialize Libevent, retry with IOCP disabled so we
5159 don't need to turn on multi-threading support in Libevent, which in
5160 turn requires a working socketpair(). This is a workaround for bug
5161 4457, which affects Libevent versions from 2.0.1-alpha through
5163 - Detect when we try to build on a platform that doesn't define
5164 AF_UNSPEC to 0. We don't work there, so refuse to compile.
5165 - Update to the November 1 2011 Maxmind GeoLite Country database.
5167 o Packaging changes:
5168 - Make it easier to automate expert package builds on Windows,
5169 by removing an absolute path from makensis.exe command.
5171 o Code simplifications and refactoring:
5172 - Remove some redundant #include directives throughout the code.
5173 Patch from Andrea Gelmini.
5174 - Unconditionally use OpenSSL's AES implementation instead of our
5175 old built-in one. OpenSSL's AES has been better for a while, and
5176 relatively few servers should still be on any version of OpenSSL
5177 that doesn't have good optimized assembly AES.
5178 - Use the name "CERTS" consistently to refer to the new cell type;
5179 we were calling it CERT in some places and CERTS in others.
5182 - Numerous new unit tests for functions in util.c and address.c by
5184 - The long-disabled benchmark tests are now split into their own
5185 ./src/test/bench binary.
5186 - The benchmark tests can now use more accurate timers than
5187 gettimeofday() when such timers are available.
5190 Changes in version 0.2.3.7-alpha - 2011-10-30
5191 Tor 0.2.3.7-alpha fixes a crash bug in 0.2.3.6-alpha introduced by
5192 the new v3 handshake. It also resolves yet another bridge address
5196 - If we mark an OR connection for close based on a cell we process,
5197 don't process any further cells on it. We already avoid further
5198 reads on marked-for-close connections, but now we also discard the
5199 cells we'd already read. Fixes bug 4299; bugfix on 0.2.0.10-alpha,
5200 which was the first version where we might mark a connection for
5201 close based on processing a cell on it.
5202 - Fix a double-free bug that would occur when we received an invalid
5203 certificate in a CERT cell in the new v3 handshake. Fixes bug 4343;
5204 bugfix on 0.2.3.6-alpha.
5205 - Bridges no longer include their address in NETINFO cells on outgoing
5206 OR connections, to allow them to blend in better with clients.
5207 Removes another avenue for enumerating bridges. Reported by
5208 "troll_un". Fixes bug 4348; bugfix on 0.2.0.10-alpha, when NETINFO
5209 cells were introduced.
5212 - Fixed a typo in a hibernation-related log message. Fixes bug 4331;
5213 bugfix on 0.2.2.23-alpha; found by "tmpname0901".
5216 Changes in version 0.2.3.6-alpha - 2011-10-26
5217 Tor 0.2.3.6-alpha includes the fix from 0.2.2.34 for a critical
5218 anonymity vulnerability where an attacker can deanonymize Tor
5219 users. Everybody should upgrade.
5221 This release also features support for a new v3 connection handshake
5222 protocol, and fixes to make hidden service connections more robust.
5225 - Implement a new handshake protocol (v3) for authenticating Tors to
5226 each other over TLS. It should be more resistant to fingerprinting
5227 than previous protocols, and should require less TLS hacking for
5228 future Tor implementations. Implements proposal 176.
5229 - Allow variable-length padding cells to disguise the length of
5230 Tor's TLS records. Implements part of proposal 184.
5232 o Privacy/anonymity fixes (clients):
5233 - Clients and bridges no longer send TLS certificate chains on
5234 outgoing OR connections. Previously, each client or bridge would
5235 use the same cert chain for all outgoing OR connections until
5236 its IP address changes, which allowed any relay that the client
5237 or bridge contacted to determine which entry guards it is using.
5238 Fixes CVE-2011-2768. Bugfix on 0.0.9pre5; found by "frosty_un".
5239 - If a relay receives a CREATE_FAST cell on a TLS connection, it
5240 no longer considers that connection as suitable for satisfying a
5241 circuit EXTEND request. Now relays can protect clients from the
5242 CVE-2011-2768 issue even if the clients haven't upgraded yet.
5243 - Directory authorities no longer assign the Guard flag to relays
5244 that haven't upgraded to the above "refuse EXTEND requests
5245 to client connections" fix. Now directory authorities can
5246 protect clients from the CVE-2011-2768 issue even if neither
5247 the clients nor the relays have upgraded yet. There's a new
5248 "GiveGuardFlagTo_CVE_2011_2768_VulnerableRelays" config option
5249 to let us transition smoothly, else tomorrow there would be no
5252 o Major bugfixes (hidden services):
5253 - Improve hidden service robustness: when an attempt to connect to
5254 a hidden service ends, be willing to refetch its hidden service
5255 descriptors from each of the HSDir relays responsible for them
5256 immediately. Previously, we would not consider refetching the
5257 service's descriptors from each HSDir for 15 minutes after the last
5258 fetch, which was inconvenient if the hidden service was not running
5259 during the first attempt. Bugfix on 0.2.0.18-alpha; fixes bug 3335.
5260 - When one of a hidden service's introduction points appears to be
5261 unreachable, stop trying it. Previously, we would keep trying
5262 to build circuits to the introduction point until we lost the
5263 descriptor, usually because the user gave up and restarted Tor.
5264 Partly fixes bug 3825.
5265 - Don't launch a useless circuit after failing to use one of a
5266 hidden service's introduction points. Previously, we would
5267 launch a new introduction circuit, but not set the hidden service
5268 which that circuit was intended to connect to, so it would never
5269 actually be used. A different piece of code would then create a
5270 new introduction circuit correctly. Bug reported by katmagic and
5271 found by Sebastian Hahn. Bugfix on 0.2.1.13-alpha; fixes bug 4212.
5273 o Major bugfixes (other):
5274 - Bridges now refuse CREATE or CREATE_FAST cells on OR connections
5275 that they initiated. Relays could distinguish incoming bridge
5276 connections from client connections, creating another avenue for
5277 enumerating bridges. Fixes CVE-2011-2769. Bugfix on 0.2.0.3-alpha.
5278 Found by "frosty_un".
5279 - Don't update the AccountingSoftLimitHitAt state file entry whenever
5280 tor gets started. This prevents a wrong average bandwidth
5281 estimate, which would cause relays to always start a new accounting
5282 interval at the earliest possible moment. Fixes bug 2003; bugfix
5283 on 0.2.2.7-alpha. Reported by BryonEldridge, who also helped
5284 immensely in tracking this bug down.
5285 - Fix a crash bug when changing node restrictions while a DNS lookup
5286 is in-progress. Fixes bug 4259; bugfix on 0.2.2.25-alpha. Bugfix
5289 o Minor bugfixes (on 0.2.2.x and earlier):
5290 - When a hidden service turns an extra service-side introduction
5291 circuit into a general-purpose circuit, free the rend_data and
5292 intro_key fields first, so we won't leak memory if the circuit
5293 is cannibalized for use as another service-side introduction
5294 circuit. Bugfix on 0.2.1.7-alpha; fixes bug 4251.
5295 - Rephrase the log message emitted if the TestSocks check is
5296 successful. Patch from Fabian Keil; fixes bug 4094.
5297 - Bridges now skip DNS self-tests, to act a little more stealthily.
5298 Fixes bug 4201; bugfix on 0.2.0.3-alpha, which first introduced
5299 bridges. Patch by "warms0x".
5300 - Remove a confusing dollar sign from the example fingerprint in the
5301 man page, and also make the example fingerprint a valid one. Fixes
5302 bug 4309; bugfix on 0.2.1.3-alpha.
5303 - Fix internal bug-checking logic that was supposed to catch
5304 failures in digest generation so that it will fail more robustly
5305 if we ask for a nonexistent algorithm. Found by Coverity Scan.
5306 Bugfix on 0.2.2.1-alpha; fixes Coverity CID 479.
5307 - Report any failure in init_keys() calls launched because our
5308 IP address has changed. Spotted by Coverity Scan. Bugfix on
5309 0.1.1.4-alpha; fixes CID 484.
5311 o Minor bugfixes (on 0.2.3.x):
5312 - Fix a bug in configure.in that kept it from building a configure
5313 script with autoconf versions earlier than 2.61. Fixes bug 2430;
5314 bugfix on 0.2.3.1-alpha.
5315 - Don't warn users that they are exposing a client port to the
5316 Internet if they have specified an RFC1918 address. Previously,
5317 we would warn if the user had specified any non-loopback
5318 address. Bugfix on 0.2.3.3-alpha. Fixes bug 4018; reported by Tas.
5319 - Fix memory leaks in the failing cases of the new SocksPort and
5320 ControlPort code. Found by Coverity Scan. Bugfix on 0.2.3.3-alpha;
5321 fixes coverity CIDs 485, 486, and 487.
5324 - When a hidden service's introduction point times out, consider
5325 trying it again during the next attempt to connect to the
5326 HS. Previously, we would not try it again unless a newly fetched
5327 descriptor contained it. Required by fixes for bugs 1297 and 3825.
5328 - The next version of Windows will be called Windows 8, and it has
5329 a major version of 6, minor version of 2. Correctly identify that
5330 version instead of calling it "Very recent version". Resolves
5331 ticket 4153; reported by funkstar.
5332 - The Bridge Authority now writes statistics on how many bridge
5333 descriptors it gave out in total, and how many unique descriptors
5334 it gave out. It also lists how often the most and least commonly
5335 fetched descriptors were given out, as well as the median and
5336 25th/75th percentile. Implements tickets 4200 and 4294.
5337 - Update to the October 4 2011 Maxmind GeoLite Country database.
5339 o Code simplifications and refactoring:
5340 - Remove some old code to remember statistics about which descriptors
5341 we've served as a directory mirror. The feature wasn't used and
5342 is outdated now that microdescriptors are around.
5343 - Rename Tor functions that turn strings into addresses, so that
5344 "parse" indicates that no hostname resolution occurs, and
5345 "lookup" indicates that hostname resolution may occur. This
5346 should help prevent mistakes in the future. Fixes bug 3512.
5349 Changes in version 0.2.2.34 - 2011-10-26
5350 Tor 0.2.2.34 fixes a critical anonymity vulnerability where an attacker
5351 can deanonymize Tor users. Everybody should upgrade.
5353 The attack relies on four components: 1) Clients reuse their TLS cert
5354 when talking to different relays, so relays can recognize a user by
5355 the identity key in her cert. 2) An attacker who knows the client's
5356 identity key can probe each guard relay to see if that identity key
5357 is connected to that guard relay right now. 3) A variety of active
5358 attacks in the literature (starting from "Low-Cost Traffic Analysis
5359 of Tor" by Murdoch and Danezis in 2005) allow a malicious website to
5360 discover the guard relays that a Tor user visiting the website is using.
5361 4) Clients typically pick three guards at random, so the set of guards
5362 for a given user could well be a unique fingerprint for her. This
5363 release fixes components #1 and #2, which is enough to block the attack;
5364 the other two remain as open research problems. Special thanks to
5365 "frosty_un" for reporting the issue to us!
5367 Clients should upgrade so they are no longer recognizable by the TLS
5368 certs they present. Relays should upgrade so they no longer allow a
5369 remote attacker to probe them to test whether unpatched clients are
5370 currently connected to them.
5372 This release also fixes several vulnerabilities that allow an attacker
5373 to enumerate bridge relays. Some bridge enumeration attacks still
5374 remain; see for example proposal 188.
5376 o Privacy/anonymity fixes (clients):
5377 - Clients and bridges no longer send TLS certificate chains on
5378 outgoing OR connections. Previously, each client or bridge would
5379 use the same cert chain for all outgoing OR connections until
5380 its IP address changes, which allowed any relay that the client
5381 or bridge contacted to determine which entry guards it is using.
5382 Fixes CVE-2011-2768. Bugfix on 0.0.9pre5; found by "frosty_un".
5383 - If a relay receives a CREATE_FAST cell on a TLS connection, it
5384 no longer considers that connection as suitable for satisfying a
5385 circuit EXTEND request. Now relays can protect clients from the
5386 CVE-2011-2768 issue even if the clients haven't upgraded yet.
5387 - Directory authorities no longer assign the Guard flag to relays
5388 that haven't upgraded to the above "refuse EXTEND requests
5389 to client connections" fix. Now directory authorities can
5390 protect clients from the CVE-2011-2768 issue even if neither
5391 the clients nor the relays have upgraded yet. There's a new
5392 "GiveGuardFlagTo_CVE_2011_2768_VulnerableRelays" config option
5393 to let us transition smoothly, else tomorrow there would be no
5396 o Privacy/anonymity fixes (bridge enumeration):
5397 - Bridge relays now do their directory fetches inside Tor TLS
5398 connections, like all the other clients do, rather than connecting
5399 directly to the DirPort like public relays do. Removes another
5400 avenue for enumerating bridges. Fixes bug 4115; bugfix on 0.2.0.35.
5401 - Bridges relays now build circuits for themselves in a more similar
5402 way to how clients build them. Removes another avenue for
5403 enumerating bridges. Fixes bug 4124; bugfix on 0.2.0.3-alpha,
5404 when bridges were introduced.
5405 - Bridges now refuse CREATE or CREATE_FAST cells on OR connections
5406 that they initiated. Relays could distinguish incoming bridge
5407 connections from client connections, creating another avenue for
5408 enumerating bridges. Fixes CVE-2011-2769. Bugfix on 0.2.0.3-alpha.
5409 Found by "frosty_un".
5412 - Fix a crash bug when changing node restrictions while a DNS lookup
5413 is in-progress. Fixes bug 4259; bugfix on 0.2.2.25-alpha. Bugfix
5415 - Don't launch a useless circuit after failing to use one of a
5416 hidden service's introduction points. Previously, we would
5417 launch a new introduction circuit, but not set the hidden service
5418 which that circuit was intended to connect to, so it would never
5419 actually be used. A different piece of code would then create a
5420 new introduction circuit correctly. Bug reported by katmagic and
5421 found by Sebastian Hahn. Bugfix on 0.2.1.13-alpha; fixes bug 4212.
5424 - Change an integer overflow check in the OpenBSD_Malloc code so
5425 that GCC is less likely to eliminate it as impossible. Patch
5426 from Mansour Moufid. Fixes bug 4059.
5427 - When a hidden service turns an extra service-side introduction
5428 circuit into a general-purpose circuit, free the rend_data and
5429 intro_key fields first, so we won't leak memory if the circuit
5430 is cannibalized for use as another service-side introduction
5431 circuit. Bugfix on 0.2.1.7-alpha; fixes bug 4251.
5432 - Bridges now skip DNS self-tests, to act a little more stealthily.
5433 Fixes bug 4201; bugfix on 0.2.0.3-alpha, which first introduced
5434 bridges. Patch by "warms0x".
5435 - Fix internal bug-checking logic that was supposed to catch
5436 failures in digest generation so that it will fail more robustly
5437 if we ask for a nonexistent algorithm. Found by Coverity Scan.
5438 Bugfix on 0.2.2.1-alpha; fixes Coverity CID 479.
5439 - Report any failure in init_keys() calls launched because our
5440 IP address has changed. Spotted by Coverity Scan. Bugfix on
5441 0.1.1.4-alpha; fixes CID 484.
5443 o Minor bugfixes (log messages and documentation):
5444 - Remove a confusing dollar sign from the example fingerprint in the
5445 man page, and also make the example fingerprint a valid one. Fixes
5446 bug 4309; bugfix on 0.2.1.3-alpha.
5447 - The next version of Windows will be called Windows 8, and it has
5448 a major version of 6, minor version of 2. Correctly identify that
5449 version instead of calling it "Very recent version". Resolves
5450 ticket 4153; reported by funkstar.
5451 - Downgrade log messages about circuit timeout calibration from
5452 "notice" to "info": they don't require or suggest any human
5453 intervention. Patch from Tom Lowenthal. Fixes bug 4063;
5454 bugfix on 0.2.2.14-alpha.
5457 - Turn on directory request statistics by default and include them in
5458 extra-info descriptors. Don't break if we have no GeoIP database.
5459 Backported from 0.2.3.1-alpha; implements ticket 3951.
5460 - Update to the October 4 2011 Maxmind GeoLite Country database.
5463 Changes in version 0.2.1.31 - 2011-10-26
5464 Tor 0.2.1.31 backports important security and privacy fixes for
5465 oldstable. This release is intended only for package maintainers and
5466 others who cannot use the 0.2.2 stable series. All others should be
5467 using Tor 0.2.2.x or newer.
5469 o Security fixes (also included in 0.2.2.x):
5470 - Replace all potentially sensitive memory comparison operations
5471 with versions whose runtime does not depend on the data being
5472 compared. This will help resist a class of attacks where an
5473 adversary can use variations in timing information to learn
5474 sensitive data. Fix for one case of bug 3122. (Safe memcmp
5475 implementation by Robert Ransom based partially on code by DJB.)
5476 - Fix an assert in parsing router descriptors containing IPv6
5477 addresses. This one took down the directory authorities when
5478 somebody tried some experimental code. Bugfix on 0.2.1.3-alpha.
5480 o Privacy/anonymity fixes (also included in 0.2.2.x):
5481 - Clients and bridges no longer send TLS certificate chains on
5482 outgoing OR connections. Previously, each client or bridge would
5483 use the same cert chain for all outgoing OR connections until
5484 its IP address changes, which allowed any relay that the client
5485 or bridge contacted to determine which entry guards it is using.
5486 Fixes CVE-2011-2768. Bugfix on 0.0.9pre5; found by "frosty_un".
5487 - If a relay receives a CREATE_FAST cell on a TLS connection, it
5488 no longer considers that connection as suitable for satisfying a
5489 circuit EXTEND request. Now relays can protect clients from the
5490 CVE-2011-2768 issue even if the clients haven't upgraded yet.
5491 - Bridges now refuse CREATE or CREATE_FAST cells on OR connections
5492 that they initiated. Relays could distinguish incoming bridge
5493 connections from client connections, creating another avenue for
5494 enumerating bridges. Fixes CVE-2011-2769. Bugfix on 0.2.0.3-alpha.
5495 Found by "frosty_un".
5496 - When receiving a hidden service descriptor, check that it is for
5497 the hidden service we wanted. Previously, Tor would store any
5498 hidden service descriptors that a directory gave it, whether it
5499 wanted them or not. This wouldn't have let an attacker impersonate
5500 a hidden service, but it did let directories pre-seed a client
5501 with descriptors that it didn't want. Bugfix on 0.0.6.
5502 - Avoid linkability based on cached hidden service descriptors: forget
5503 all hidden service descriptors cached as a client when processing a
5504 SIGNAL NEWNYM command. Fixes bug 3000; bugfix on 0.0.6.
5505 - Make the bridge directory authority refuse to answer directory
5506 requests for "all" descriptors. It used to include bridge
5507 descriptors in its answer, which was a major information leak.
5508 Found by "piebeer". Bugfix on 0.2.0.3-alpha.
5509 - Don't attach new streams to old rendezvous circuits after SIGNAL
5510 NEWNYM. Previously, we would keep using an existing rendezvous
5511 circuit if it remained open (i.e. if it were kept open by a
5512 long-lived stream, or if a new stream were attached to it before
5513 Tor could notice that it was old and no longer in use). Bugfix on
5514 0.1.1.15-rc; fixes bug 3375.
5516 o Minor bugfixes (also included in 0.2.2.x):
5517 - When we restart our relay, we might get a successful connection
5518 from the outside before we've started our reachability tests,
5519 triggering a warning: "ORPort found reachable, but I have no
5520 routerinfo yet. Failing to inform controller of success." This
5521 bug was harmless unless Tor is running under a controller
5522 like Vidalia, in which case the controller would never get a
5523 REACHABILITY_SUCCEEDED status event. Bugfix on 0.1.2.6-alpha;
5525 - Build correctly on OSX with zlib 1.2.4 and higher with all warnings
5526 enabled. Fixes bug 1526.
5527 - Remove undocumented option "-F" from tor-resolve: it hasn't done
5528 anything since 0.2.1.16-rc.
5529 - Avoid signed/unsigned comparisons by making SIZE_T_CEILING unsigned.
5530 None of the cases where we did this before were wrong, but by making
5531 this change we avoid warnings. Fixes bug 2475; bugfix on 0.2.1.28.
5532 - Fix a rare crash bug that could occur when a client was configured
5533 with a large number of bridges. Fixes bug 2629; bugfix on
5534 0.2.1.2-alpha. Bugfix by trac user "shitlei".
5535 - Correct the warning displayed when a rendezvous descriptor exceeds
5536 the maximum size. Fixes bug 2750; bugfix on 0.2.1.5-alpha. Found by
5538 - Fix an uncommon assertion failure when running with DNSPort under
5539 heavy load. Fixes bug 2933; bugfix on 0.2.0.1-alpha.
5540 - When warning about missing zlib development packages during compile,
5541 give the correct package names. Bugfix on 0.2.0.1-alpha.
5542 - Require that introduction point keys and onion keys have public
5543 exponent 65537. Bugfix on 0.2.0.10-alpha.
5544 - Do not crash when our configuration file becomes unreadable, for
5545 example due to a permissions change, between when we start up
5546 and when a controller calls SAVECONF. Fixes bug 3135; bugfix
5548 - Fix warnings from GCC 4.6's "-Wunused-but-set-variable" option.
5550 - Always NUL-terminate the sun_path field of a sockaddr_un before
5551 passing it to the kernel. (Not a security issue: kernels are
5552 smart enough to reject bad sockaddr_uns.) Found by Coverity;
5553 CID #428. Bugfix on Tor 0.2.0.3-alpha.
5554 - Don't stack-allocate the list of supplementary GIDs when we're
5555 about to log them. Stack-allocating NGROUPS_MAX gid_t elements
5556 could take up to 256K, which is way too much stack. Found by
5557 Coverity; CID #450. Bugfix on 0.2.1.7-alpha.
5559 o Minor bugfixes (only in 0.2.1.x):
5560 - Resume using micro-version numbers in 0.2.1.x: our Debian packages
5561 rely on them. Bugfix on 0.2.1.30.
5562 - Use git revisions instead of svn revisions when generating our
5563 micro-version numbers. Bugfix on 0.2.1.15-rc; fixes bug 2402.
5565 o Minor features (also included in 0.2.2.x):
5566 - Adjust the expiration time on our SSL session certificates to
5567 better match SSL certs seen in the wild. Resolves ticket 4014.
5568 - Allow nameservers with IPv6 address. Resolves bug 2574.
5569 - Update to the October 4 2011 Maxmind GeoLite Country database.
5572 Changes in version 0.2.3.5-alpha - 2011-09-28
5573 Tor 0.2.3.5-alpha fixes two bugs that make it possible to enumerate
5574 bridge relays; fixes an assertion error that many users started hitting
5575 today; and adds the ability to refill token buckets more often than
5576 once per second, allowing significant performance improvements.
5579 - Bridge relays now do their directory fetches inside Tor TLS
5580 connections, like all the other clients do, rather than connecting
5581 directly to the DirPort like public relays do. Removes another
5582 avenue for enumerating bridges. Fixes bug 4115; bugfix on 0.2.0.35.
5583 - Bridges relays now build circuits for themselves in a more similar
5584 way to how clients build them. Removes another avenue for
5585 enumerating bridges. Fixes bug 4124; bugfix on 0.2.0.3-alpha,
5586 when bridges were introduced.
5589 - Fix an "Assertion md->held_by_node == 1 failed" error that could
5590 occur when the same microdescriptor was referenced by two node_t
5591 objects at once. Fix for bug 4118; bugfix on Tor 0.2.3.1-alpha.
5593 o Major features (networking):
5594 - Add a new TokenBucketRefillInterval option to refill token buckets
5595 more frequently than once per second. This should improve network
5596 performance, alleviate queueing problems, and make traffic less
5597 bursty. Implements proposal 183; closes ticket 3630. Design by
5598 Florian Tschorsch and Björn Scheuermann; implementation by
5602 - Change an integer overflow check in the OpenBSD_Malloc code so
5603 that GCC is less likely to eliminate it as impossible. Patch
5604 from Mansour Moufid. Fixes bug 4059.
5606 o Minor bugfixes (usability):
5607 - Downgrade log messages about circuit timeout calibration from
5608 "notice" to "info": they don't require or suggest any human
5609 intervention. Patch from Tom Lowenthal. Fixes bug 4063;
5610 bugfix on 0.2.2.14-alpha.
5612 o Minor features (diagnostics):
5613 - When the system call to create a listener socket fails, log the
5614 error message explaining why. This may help diagnose bug 4027.
5617 Changes in version 0.2.3.4-alpha - 2011-09-13
5618 Tor 0.2.3.4-alpha includes the fixes from 0.2.2.33, including a slight
5619 tweak to Tor's TLS handshake that makes relays and bridges that run
5620 this new version reachable from Iran again. It also fixes a few new
5621 bugs in 0.2.3.x, and teaches relays to recognize when they're not
5622 listed in the network consensus and republish.
5624 o Major bugfixes (also part of 0.2.2.33):
5625 - Avoid an assertion failure when reloading a configuration with
5626 TrackExitHosts changes. Found and fixed by 'laruldan'. Fixes bug
5627 3923; bugfix on 0.2.2.25-alpha.
5629 o Minor features (security, also part of 0.2.2.33):
5630 - Check for replays of the public-key encrypted portion of an
5631 INTRODUCE1 cell, in addition to the current check for replays of
5632 the g^x value. This prevents a possible class of active attacks
5633 by an attacker who controls both an introduction point and a
5634 rendezvous point, and who uses the malleability of AES-CTR to
5635 alter the encrypted g^x portion of the INTRODUCE1 cell. We think
5636 that these attacks are infeasible (requiring the attacker to send
5637 on the order of zettabytes of altered cells in a short interval),
5638 but we'd rather block them off in case there are any classes of
5639 this attack that we missed. Reported by Willem Pinckaers.
5641 o Minor features (also part of 0.2.2.33):
5642 - Adjust the expiration time on our SSL session certificates to
5643 better match SSL certs seen in the wild. Resolves ticket 4014.
5644 - Change the default required uptime for a relay to be accepted as
5645 a HSDir (hidden service directory) from 24 hours to 25 hours.
5646 Improves on 0.2.0.10-alpha; resolves ticket 2649.
5647 - Add a VoteOnHidServDirectoriesV2 config option to allow directory
5648 authorities to abstain from voting on assignment of the HSDir
5649 consensus flag. Related to bug 2649.
5650 - Update to the September 6 2011 Maxmind GeoLite Country database.
5652 o Minor bugfixes (also part of 0.2.2.33):
5653 - Demote the 'replay detected' log message emitted when a hidden
5654 service receives the same Diffie-Hellman public key in two different
5655 INTRODUCE2 cells to info level. A normal Tor client can cause that
5656 log message during its normal operation. Bugfix on 0.2.1.6-alpha;
5657 fixes part of bug 2442.
5658 - Demote the 'INTRODUCE2 cell is too {old,new}' log message to info
5659 level. There is nothing that a hidden service's operator can do
5660 to fix its clients' clocks. Bugfix on 0.2.1.6-alpha; fixes part
5662 - Clarify a log message specifying the characters permitted in
5663 HiddenServiceAuthorizeClient client names. Previously, the log
5664 message said that "[A-Za-z0-9+-_]" were permitted; that could have
5665 given the impression that every ASCII character between "+" and "_"
5666 was permitted. Now we say "[A-Za-z0-9+_-]". Bugfix on 0.2.1.5-alpha.
5668 o Build fixes (also part of 0.2.2.33):
5669 - Clean up some code issues that prevented Tor from building on older
5670 BSDs. Fixes bug 3894; reported by "grarpamp".
5671 - Search for a platform-specific version of "ar" when cross-compiling.
5672 Should fix builds on iOS. Resolves bug 3909, found by Marco Bonetti.
5675 - Fix a bug where the SocksPort option (for example) would get
5676 ignored and replaced by the default if a SocksListenAddress
5677 option was set. Bugfix on 0.2.3.3-alpha; fixes bug 3936. Fix by
5681 - Relays now try regenerating and uploading their descriptor more
5682 frequently if they are not listed in the consensus, or if the
5683 version of their descriptor listed in the consensus is too
5684 old. This fix should prevent situations where a server declines
5685 to re-publish itself because it has done so too recently, even
5686 though the authorities decided not to list its recent-enough
5687 descriptor. Fix for bug 3327.
5690 - Relays now include a reason for regenerating their descriptors
5691 in an HTTP header when uploading to the authorities. This will
5692 make it easier to debug descriptor-upload issues in the future.
5693 - When starting as root and then changing our UID via the User
5694 control option, and we have a ControlSocket configured, make sure
5695 that the ControlSocket is owned by the same account that Tor will
5696 run under. Implements ticket 3421; fix by Jérémy Bobbio.
5699 - Abort if tor_vasprintf fails in connection_printf_to_buf (a
5700 utility function used in the control-port code). This shouldn't
5701 ever happen unless Tor is completely out of memory, but if it did
5702 happen and Tor somehow recovered from it, Tor could have sent a log
5703 message to a control port in the middle of a reply to a controller
5704 command. Fixes part of bug 3428; bugfix on 0.1.2.3-alpha.
5705 - Make 'FetchUselessDescriptors' cause all descriptor types and
5706 all consensus types (including microdescriptors) to get fetched.
5707 Fixes bug 3851; bugfix on 0.2.3.1-alpha.
5710 - Make a new "entry connection" struct as an internal subtype of "edge
5711 connection", to simplify the code and make exit connections smaller.
5714 Changes in version 0.2.2.33 - 2011-09-13
5715 Tor 0.2.2.33 fixes several bugs, and includes a slight tweak to Tor's
5716 TLS handshake that makes relays and bridges that run this new version
5717 reachable from Iran again.
5720 - Avoid an assertion failure when reloading a configuration with
5721 TrackExitHosts changes. Found and fixed by 'laruldan'. Fixes bug
5722 3923; bugfix on 0.2.2.25-alpha.
5724 o Minor features (security):
5725 - Check for replays of the public-key encrypted portion of an
5726 INTRODUCE1 cell, in addition to the current check for replays of
5727 the g^x value. This prevents a possible class of active attacks
5728 by an attacker who controls both an introduction point and a
5729 rendezvous point, and who uses the malleability of AES-CTR to
5730 alter the encrypted g^x portion of the INTRODUCE1 cell. We think
5731 that these attacks are infeasible (requiring the attacker to send
5732 on the order of zettabytes of altered cells in a short interval),
5733 but we'd rather block them off in case there are any classes of
5734 this attack that we missed. Reported by Willem Pinckaers.
5737 - Adjust the expiration time on our SSL session certificates to
5738 better match SSL certs seen in the wild. Resolves ticket 4014.
5739 - Change the default required uptime for a relay to be accepted as
5740 a HSDir (hidden service directory) from 24 hours to 25 hours.
5741 Improves on 0.2.0.10-alpha; resolves ticket 2649.
5742 - Add a VoteOnHidServDirectoriesV2 config option to allow directory
5743 authorities to abstain from voting on assignment of the HSDir
5744 consensus flag. Related to bug 2649.
5745 - Update to the September 6 2011 Maxmind GeoLite Country database.
5747 o Minor bugfixes (documentation and log messages):
5748 - Correct the man page to explain that HashedControlPassword and
5749 CookieAuthentication can both be set, in which case either method
5750 is sufficient to authenticate to Tor. Bugfix on 0.2.0.7-alpha,
5751 when we decided to allow these config options to both be set. Issue
5753 - Demote the 'replay detected' log message emitted when a hidden
5754 service receives the same Diffie-Hellman public key in two different
5755 INTRODUCE2 cells to info level. A normal Tor client can cause that
5756 log message during its normal operation. Bugfix on 0.2.1.6-alpha;
5757 fixes part of bug 2442.
5758 - Demote the 'INTRODUCE2 cell is too {old,new}' log message to info
5759 level. There is nothing that a hidden service's operator can do
5760 to fix its clients' clocks. Bugfix on 0.2.1.6-alpha; fixes part
5762 - Clarify a log message specifying the characters permitted in
5763 HiddenServiceAuthorizeClient client names. Previously, the log
5764 message said that "[A-Za-z0-9+-_]" were permitted; that could have
5765 given the impression that every ASCII character between "+" and "_"
5766 was permitted. Now we say "[A-Za-z0-9+_-]". Bugfix on 0.2.1.5-alpha.
5769 - Provide a substitute implementation of lround() for MSVC, which
5770 apparently lacks it. Patch from Gisle Vanem.
5771 - Clean up some code issues that prevented Tor from building on older
5772 BSDs. Fixes bug 3894; reported by "grarpamp".
5773 - Search for a platform-specific version of "ar" when cross-compiling.
5774 Should fix builds on iOS. Resolves bug 3909, found by Marco Bonetti.
5777 Changes in version 0.2.3.3-alpha - 2011-09-01
5778 Tor 0.2.3.3-alpha adds a new "stream isolation" feature to improve Tor's
5779 security, and provides client-side support for the microdescriptor
5780 and optimistic data features introduced earlier in the 0.2.3.x
5781 series. It also includes numerous critical bugfixes in the (optional)
5782 bufferevent-based networking backend.
5784 o Major features (stream isolation):
5785 - You can now configure Tor so that streams from different
5786 applications are isolated on different circuits, to prevent an
5787 attacker who sees your streams as they leave an exit node from
5788 linking your sessions to one another. To do this, choose some way
5789 to distinguish the applications: have them connect to different
5790 SocksPorts, or have one of them use SOCKS4 while the other uses
5791 SOCKS5, or have them pass different authentication strings to the
5792 SOCKS proxy. Then, use the new SocksPort syntax to configure the
5793 degree of isolation you need. This implements Proposal 171.
5794 - There's a new syntax for specifying multiple client ports (such as
5795 SOCKSPort, TransPort, DNSPort, NATDPort): you can now just declare
5796 multiple *Port entries with full addr:port syntax on each.
5797 The old *ListenAddress format is still supported, but you can't
5798 mix it with the new *Port syntax.
5800 o Major features (other):
5801 - Enable microdescriptor fetching by default for clients. This allows
5802 clients to download a much smaller amount of directory information.
5803 To disable it (and go back to the old-style consensus and
5804 descriptors), set "UseMicrodescriptors 0" in your torrc file.
5805 - Tor's firewall-helper feature, introduced in 0.2.3.1-alpha (see the
5806 "PortForwarding" config option), now supports Windows.
5807 - When using an exit relay running 0.2.3.x, clients can now
5808 "optimistically" send data before the exit relay reports that
5809 the stream has opened. This saves a round trip when starting
5810 connections where the client speaks first (such as web browsing).
5811 This behavior is controlled by a consensus parameter (currently
5812 disabled). To turn it on or off manually, use the "OptimisticData"
5813 torrc option. Implements proposal 181; code by Ian Goldberg.
5815 o Major bugfixes (bufferevents, fixes on 0.2.3.1-alpha):
5816 - When using IOCP on Windows, we need to enable Libevent windows
5818 - The IOCP backend now works even when the user has not specified
5819 the (internal, debugging-only) _UseFilteringSSLBufferevents option.
5820 Fixes part of bug 3752.
5821 - Correctly record the bytes we've read and written when using
5822 bufferevents, so that we can include them in our bandwidth history
5823 and advertised bandwidth. Fixes bug 3803.
5824 - Apply rate-limiting only at the bottom of a chain of filtering
5825 bufferevents. This prevents us from filling up internal read
5826 buffers and violating rate-limits when filtering bufferevents
5827 are enabled. Fixes part of bug 3804.
5828 - Add high-watermarks to the output buffers for filtered
5829 bufferevents. This prevents us from filling up internal write
5830 buffers and wasting CPU cycles when filtering bufferevents are
5831 enabled. Fixes part of bug 3804.
5832 - Correctly notice when data has been written from a bufferevent
5833 without flushing it completely. Fixes bug 3805.
5834 - Fix a bug where server-side tunneled bufferevent-based directory
5835 streams would get closed prematurely. Fixes bug 3814.
5836 - Fix a use-after-free error with per-connection rate-limiting
5837 buckets. Fixes bug 3888.
5839 o Major bugfixes (also part of 0.2.2.31-rc):
5840 - If we're configured to write our ControlPorts to disk, only write
5841 them after switching UID and creating the data directory. This way,
5842 we don't fail when starting up with a nonexistent DataDirectory
5843 and a ControlPortWriteToFile setting based on that directory. Fixes
5844 bug 3747; bugfix on Tor 0.2.2.26-beta.
5847 - Added a new CONF_CHANGED event so that controllers can be notified
5848 of any configuration changes made by other controllers, or by the
5849 user. Implements ticket 1692.
5850 - Use evbuffer_copyout() in inspect_evbuffer(). This fixes a memory
5851 leak when using bufferevents, and lets Libevent worry about how to
5852 best copy data out of a buffer.
5853 - Replace files in stats/ rather than appending to them. Now that we
5854 include statistics in extra-info descriptors, it makes no sense to
5855 keep old statistics forever. Implements ticket 2930.
5857 o Minor features (build compatibility):
5858 - Limited, experimental support for building with nmake and MSVC.
5859 - Provide a substitute implementation of lround() for MSVC, which
5860 apparently lacks it. Patch from Gisle Vanem.
5862 o Minor features (also part of 0.2.2.31-rc):
5863 - Update to the August 2 2011 Maxmind GeoLite Country database.
5865 o Minor bugfixes (on 0.2.3.x-alpha):
5866 - Fix a spurious warning when parsing SOCKS requests with
5867 bufferevents enabled. Fixes bug 3615; bugfix on 0.2.3.2-alpha.
5868 - Get rid of a harmless warning that could happen on relays running
5869 with bufferevents. The warning was caused by someone doing an http
5870 request to a relay's orport. Also don't warn for a few related
5871 non-errors. Fixes bug 3700; bugfix on 0.2.3.1-alpha.
5873 o Minor bugfixes (on 2.2.x and earlier):
5874 - Correct the man page to explain that HashedControlPassword and
5875 CookieAuthentication can both be set, in which case either method
5876 is sufficient to authenticate to Tor. Bugfix on 0.2.0.7-alpha,
5877 when we decided to allow these config options to both be set. Issue
5879 - The "--quiet" and "--hush" options now apply not only to Tor's
5880 behavior before logs are configured, but also to Tor's behavior in
5881 the absense of configured logs. Fixes bug 3550; bugfix on
5884 o Minor bugfixes (also part of 0.2.2.31-rc):
5885 - Write several files in text mode, on OSes that distinguish text
5886 mode from binary mode (namely, Windows). These files are:
5887 'buffer-stats', 'dirreq-stats', and 'entry-stats' on relays
5888 that collect those statistics; 'client_keys' and 'hostname' for
5889 hidden services that use authentication; and (in the tor-gencert
5890 utility) newly generated identity and signing keys. Previously,
5891 we wouldn't specify text mode or binary mode, leading to an
5892 assertion failure. Fixes bug 3607. Bugfix on 0.2.1.1-alpha (when
5893 the DirRecordUsageByCountry option which would have triggered
5894 the assertion failure was added), although this assertion failure
5895 would have occurred in tor-gencert on Windows in 0.2.0.1-alpha.
5896 - Selectively disable deprecation warnings on OS X because Lion
5897 started deprecating the shipped copy of openssl. Fixes bug 3643.
5898 - Remove an extra pair of quotation marks around the error
5899 message in control-port STATUS_GENERAL BUG events. Bugfix on
5900 0.1.2.6-alpha; fixes bug 3732.
5901 - When unable to format an address as a string, report its value
5902 as "???" rather than reusing the last formatted address. Bugfix
5905 o Code simplifications and refactoring:
5906 - Rewrite the listener-selection logic so that parsing which ports
5907 we want to listen on is now separate from binding to the ports
5911 - Building Tor with bufferevent support now requires Libevent
5912 2.0.13-stable or later. Previous versions of Libevent had bugs in
5913 SSL-related bufferevents and related issues that would make Tor
5914 work badly with bufferevents. Requiring 2.0.13-stable also allows
5915 Tor with bufferevents to take advantage of Libevent APIs
5916 introduced after 2.0.8-rc.
5919 Changes in version 0.2.2.32 - 2011-08-27
5920 The Tor 0.2.2 release series is dedicated to the memory of Andreas
5921 Pfitzmann (1958-2010), a pioneer in anonymity and privacy research,
5922 a founder of the PETS community, a leader in our field, a mentor,
5923 and a friend. He left us with these words: "I had the possibility
5924 to contribute to this world that is not as it should be. I hope I
5925 could help in some areas to make the world a better place, and that
5926 I could also encourage other people to be engaged in improving the
5927 world. Please, stay engaged. This world needs you, your love, your
5928 initiative -- now I cannot be part of that anymore."
5930 Tor 0.2.2.32, the first stable release in the 0.2.2 branch, is finally
5931 ready. More than two years in the making, this release features improved
5932 client performance and hidden service reliability, better compatibility
5933 for Android, correct behavior for bridges that listen on more than
5934 one address, more extensible and flexible directory object handling,
5935 better reporting of network statistics, improved code security, and
5936 many many other features and bugfixes.
5939 Changes in version 0.2.2.31-rc - 2011-08-17
5940 Tor 0.2.2.31-rc is the second and hopefully final release candidate
5941 for the Tor 0.2.2.x series.
5944 - Remove an extra pair of quotation marks around the error
5945 message in control-port STATUS_GENERAL BUG events. Bugfix on
5946 0.1.2.6-alpha; fixes bug 3732.
5947 - If we're configured to write our ControlPorts to disk, only write
5948 them after switching UID and creating the data directory. This way,
5949 we don't fail when starting up with a nonexistent DataDirectory
5950 and a ControlPortWriteToFile setting based on that directory. Fixes
5951 bug 3747; bugfix on Tor 0.2.2.26-beta.
5954 - Update to the August 2 2011 Maxmind GeoLite Country database.
5957 - Allow GETINFO fingerprint to return a fingerprint even when
5958 we have not yet built a router descriptor. Fixes bug 3577;
5959 bugfix on 0.2.0.1-alpha.
5960 - Write several files in text mode, on OSes that distinguish text
5961 mode from binary mode (namely, Windows). These files are:
5962 'buffer-stats', 'dirreq-stats', and 'entry-stats' on relays
5963 that collect those statistics; 'client_keys' and 'hostname' for
5964 hidden services that use authentication; and (in the tor-gencert
5965 utility) newly generated identity and signing keys. Previously,
5966 we wouldn't specify text mode or binary mode, leading to an
5967 assertion failure. Fixes bug 3607. Bugfix on 0.2.1.1-alpha (when
5968 the DirRecordUsageByCountry option which would have triggered
5969 the assertion failure was added), although this assertion failure
5970 would have occurred in tor-gencert on Windows in 0.2.0.1-alpha.
5971 - Selectively disable deprecation warnings on OS X because Lion
5972 started deprecating the shipped copy of openssl. Fixes bug 3643.
5973 - When unable to format an address as a string, report its value
5974 as "???" rather than reusing the last formatted address. Bugfix
5978 Changes in version 0.2.3.2-alpha - 2011-07-18
5979 Tor 0.2.3.2-alpha introduces two new experimental features:
5980 microdescriptors and pluggable transports. It also continues cleaning
5981 up a variety of recently introduced features.
5984 - Clients can now use microdescriptors instead of regular descriptors
5985 to build circuits. Microdescriptors are authority-generated
5986 summaries of regular descriptors' contents, designed to change
5987 very rarely (see proposal 158 for details). This feature is
5988 designed to save bandwidth, especially for clients on slow internet
5989 connections. It's off by default for now, since nearly no caches
5990 support it, but it will be on-by-default for clients in a future
5991 version. You can use the UseMicrodescriptors option to turn it on.
5992 - Tor clients using bridges can now be configured to use a separate
5993 'transport' proxy for each bridge. This approach helps to resist
5994 censorship by allowing bridges to use protocol obfuscation
5995 plugins. It implements part of proposal 180. Implements ticket 2841.
5996 - While we're trying to bootstrap, record how many TLS connections
5997 fail in each state, and report which states saw the most failures
5998 in response to any bootstrap failures. This feature may speed up
5999 diagnosis of censorship events. Implements ticket 3116.
6001 o Major bugfixes (on 0.2.3.1-alpha):
6002 - When configuring a large set of nodes in EntryNodes (as with
6003 'EntryNodes {cc}' or 'EntryNodes 1.1.1.1/16'), choose only a
6004 random subset to be guards, and choose them in random
6005 order. Fixes bug 2798.
6006 - Tor could crash when remembering a consensus in a non-used consensus
6007 flavor without having a current consensus set. Fixes bug 3361.
6008 - Comparing an unknown address to a microdescriptor's shortened exit
6009 policy would always give a "rejected" result. Fixes bug 3599.
6010 - Using microdescriptors as a client no longer prevents Tor from
6011 uploading and downloading hidden service descriptors. Fixes
6015 - Allow nameservers with IPv6 address. Resolves bug 2574.
6016 - Accept attempts to include a password authenticator in the
6017 handshake, as supported by SOCKS5. This handles SOCKS clients that
6018 don't know how to omit a password when authenticating. Resolves
6020 - When configuring a large set of nodes in EntryNodes, and there are
6021 enough of them listed as Guard so that we don't need to consider
6022 the non-guard entries, prefer the ones listed with the Guard flag.
6023 - Check for and recover from inconsistency in the microdescriptor
6024 cache. This will make it harder for us to accidentally free a
6025 microdescriptor without removing it from the appropriate data
6026 structures. Fixes issue 3135; issue noted by "wanoskarnet".
6027 - Log SSL state transitions at log level DEBUG, log domain
6028 HANDSHAKE. This can be useful for debugging censorship events.
6029 Implements ticket 3264.
6030 - Add port 6523 (Gobby) to LongLivedPorts. Patch by intrigeri;
6031 implements ticket 3439.
6033 o Minor bugfixes (on 0.2.3.1-alpha):
6034 - Do not free all general-purpose regular descriptors just
6035 because microdescriptor use is enabled. Fixes bug 3113.
6036 - Correctly link libevent_openssl when --enable-static-libevent
6037 is passed to configure. Fixes bug 3118.
6038 - Bridges should not complain during their heartbeat log messages that
6039 they are unlisted in the consensus: that's more or less the point
6040 of being a bridge. Fixes bug 3183.
6041 - Report a SIGNAL event to controllers when acting on a delayed
6042 SIGNAL NEWNYM command. Previously, we would report a SIGNAL
6043 event to the controller if we acted on a SIGNAL NEWNYM command
6044 immediately, and otherwise not report a SIGNAL event for the
6045 command at all. Fixes bug 3349.
6046 - Fix a crash when handling the SIGNAL controller command or
6047 reporting ERR-level status events with bufferevents enabled. Found
6048 by Robert Ransom. Fixes bug 3367.
6049 - Always ship the tor-fw-helper manpage in our release tarballs.
6050 Fixes bug 3389. Reported by Stephen Walker.
6051 - Fix a class of double-mark-for-close bugs when bufferevents
6052 are enabled. Fixes bug 3403.
6053 - Update tor-fw-helper to support libnatpmp-20110618. Fixes bug 3434.
6054 - Add SIGNAL to the list returned by the 'GETINFO events/names'
6055 control-port command. Fixes part of bug 3465.
6056 - Prevent using negative indices during unit test runs when read_all()
6057 fails. Spotted by coverity.
6058 - Fix a rare memory leak when checking the nodelist without it being
6059 present. Found by coverity.
6060 - Only try to download a microdescriptor-flavored consensus from
6061 a directory cache that provides them.
6063 o Minor bugfixes (on 0.2.2.x and earlier):
6064 - Assert that hidden-service-related operations are not performed
6065 using single-hop circuits. Previously, Tor would assert that
6066 client-side streams are not attached to single-hop circuits,
6067 but not that other sensitive operations on the client and service
6068 side are not performed using single-hop circuits. Fixes bug 3332;
6070 - Don't publish a new relay descriptor when we reload our onion key,
6071 unless the onion key has actually changed. Fixes bug 3263 and
6072 resolves another cause of bug 1810. Bugfix on 0.1.1.11-alpha.
6073 - Allow GETINFO fingerprint to return a fingerprint even when
6074 we have not yet built a router descriptor. Fixes bug 3577;
6075 bugfix on 0.2.0.1-alpha.
6076 - Make 'tor --digests' list hashes of all Tor source files. Bugfix
6077 on 0.2.2.4-alpha; fixes bug 3427.
6079 o Code simplification and refactoring:
6080 - Use tor_sscanf() in place of scanf() in more places through the
6081 code. This makes us a little more locale-independent, and
6082 should help shut up code-analysis tools that can't tell
6083 a safe sscanf string from a dangerous one.
6084 - Use tt_assert(), not tor_assert(), for checking for test failures.
6085 This makes the unit tests more able to go on in the event that
6087 - Split connection_about_to_close() into separate functions for each
6091 - On Windows, we now define the _WIN32_WINNT macros only if they
6092 are not already defined. This lets the person building Tor decide,
6093 if they want, to require a later version of Windows.
6096 Changes in version 0.2.2.30-rc - 2011-07-07
6097 Tor 0.2.2.30-rc is the first release candidate for the Tor 0.2.2.x
6098 series. It fixes a few smaller bugs, but generally appears stable.
6099 Please test it and let us know whether it is!
6102 - Send a SUCCEEDED stream event to the controller when a reverse
6103 resolve succeeded. Fixes bug 3536; bugfix on 0.0.8pre1. Issue
6104 discovered by katmagic.
6105 - Always NUL-terminate the sun_path field of a sockaddr_un before
6106 passing it to the kernel. (Not a security issue: kernels are
6107 smart enough to reject bad sockaddr_uns.) Found by Coverity;
6108 CID #428. Bugfix on Tor 0.2.0.3-alpha.
6109 - Don't stack-allocate the list of supplementary GIDs when we're
6110 about to log them. Stack-allocating NGROUPS_MAX gid_t elements
6111 could take up to 256K, which is way too much stack. Found by
6112 Coverity; CID #450. Bugfix on 0.2.1.7-alpha.
6113 - Add BUILDTIMEOUT_SET to the list returned by the 'GETINFO
6114 events/names' control-port command. Bugfix on 0.2.2.9-alpha;
6115 fixes part of bug 3465.
6116 - Fix a memory leak when receiving a descriptor for a hidden
6117 service we didn't ask for. Found by Coverity; CID #30. Bugfix
6121 - Update to the July 1 2011 Maxmind GeoLite Country database.
6124 Changes in version 0.2.2.29-beta - 2011-06-20
6125 Tor 0.2.2.29-beta reverts an accidental behavior change for users who
6126 have bridge lines in their torrc but don't want to use them; gets
6127 us closer to having the control socket feature working on Debian;
6128 and fixes a variety of smaller bugs.
6131 - Revert the UseBridges option to its behavior before 0.2.2.28-beta.
6132 When we changed the default behavior to "use bridges if any
6133 are listed in the torrc", we surprised users who had bridges
6134 in their torrc files but who didn't actually want to use them.
6135 Partial resolution for bug 3354.
6138 - Don't attach new streams to old rendezvous circuits after SIGNAL
6139 NEWNYM. Previously, we would keep using an existing rendezvous
6140 circuit if it remained open (i.e. if it were kept open by a
6141 long-lived stream, or if a new stream were attached to it before
6142 Tor could notice that it was old and no longer in use). Bugfix on
6143 0.1.1.15-rc; fixes bug 3375.
6146 - Fix a bug when using ControlSocketsGroupWritable with User. The
6147 directory's group would be checked against the current group, not
6148 the configured group. Patch by Jérémy Bobbio. Fixes bug 3393;
6149 bugfix on 0.2.2.26-beta.
6150 - Make connection_printf_to_buf()'s behaviour sane. Its callers
6151 expect it to emit a CRLF iff the format string ends with CRLF;
6152 it actually emitted a CRLF iff (a) the format string ended with
6153 CRLF or (b) the resulting string was over 1023 characters long or
6154 (c) the format string did not end with CRLF *and* the resulting
6155 string was 1021 characters long or longer. Bugfix on 0.1.1.9-alpha;
6156 fixes part of bug 3407.
6157 - Make send_control_event_impl()'s behaviour sane. Its callers
6158 expect it to always emit a CRLF at the end of the string; it
6159 might have emitted extra control characters as well. Bugfix on
6160 0.1.1.9-alpha; fixes another part of bug 3407.
6161 - Make crypto_rand_int() check the value of its input correctly.
6162 Previously, it accepted values up to UINT_MAX, but could return a
6163 negative number if given a value above INT_MAX+1. Found by George
6164 Kadianakis. Fixes bug 3306; bugfix on 0.2.2pre14.
6165 - Avoid a segfault when reading a malformed circuit build state
6166 with more than INT_MAX entries. Found by wanoskarnet. Bugfix on
6168 - When asked about a DNS record type we don't support via a
6169 client DNSPort, reply with NOTIMPL rather than an empty
6170 reply. Patch by intrigeri. Fixes bug 3369; bugfix on 2.0.1-alpha.
6171 - Fix a rare memory leak during stats writing. Found by coverity.
6174 - Update to the June 1 2011 Maxmind GeoLite Country database.
6176 o Code simplifications and refactoring:
6177 - Remove some dead code as indicated by coverity.
6178 - Remove a few dead assignments during router parsing. Found by
6180 - Add some forgotten return value checks during unit tests. Found
6182 - Don't use 1-bit wide signed bit fields. Found by coverity.
6185 Changes in version 0.2.2.28-beta - 2011-06-04
6186 Tor 0.2.2.28-beta makes great progress towards a new stable release: we
6187 fixed a big bug in whether relays stay in the consensus consistently,
6188 we moved closer to handling bridges and hidden services correctly,
6189 and we started the process of better handling the dreaded "my Vidalia
6190 died, and now my Tor demands a password when I try to reconnect to it"
6194 - Don't decide to make a new descriptor when receiving a HUP signal.
6195 This bug has caused a lot of 0.2.2.x relays to disappear from the
6196 consensus periodically. Fixes the most common case of triggering
6197 bug 1810; bugfix on 0.2.2.7-alpha.
6198 - Actually allow nameservers with IPv6 addresses. Fixes bug 2574.
6199 - Don't try to build descriptors if "ORPort auto" is set and we
6200 don't know our actual ORPort yet. Fix for bug 3216; bugfix on
6202 - Resolve a crash that occurred when setting BridgeRelay to 1 with
6203 accounting enabled. Fixes bug 3228; bugfix on 0.2.2.18-alpha.
6204 - Apply circuit timeouts to opened hidden-service-related circuits
6205 based on the correct start time. Previously, we would apply the
6206 circuit build timeout based on time since the circuit's creation;
6207 it was supposed to be applied based on time since the circuit
6208 entered its current state. Bugfix on 0.0.6; fixes part of bug 1297.
6209 - Use the same circuit timeout for client-side introduction
6210 circuits as for other four-hop circuits, rather than the timeout
6211 for single-hop directory-fetch circuits; the shorter timeout may
6212 have been appropriate with the static circuit build timeout in
6213 0.2.1.x and earlier, but caused many hidden service access attempts
6214 to fail with the adaptive CBT introduced in 0.2.2.2-alpha. Bugfix
6215 on 0.2.2.2-alpha; fixes another part of bug 1297.
6216 - In ticket 2511 we fixed a case where you could use an unconfigured
6217 bridge if you had configured it as a bridge the last time you ran
6218 Tor. Now fix another edge case: if you had configured it as a bridge
6219 but then switched to a different bridge via the controller, you
6220 would still be willing to use the old one. Bugfix on 0.2.0.1-alpha;
6224 - Add an __OwningControllerProcess configuration option and a
6225 TAKEOWNERSHIP control-port command. Now a Tor controller can ensure
6226 that when it exits, Tor will shut down. Implements feature 3049.
6227 - If "UseBridges 1" is set and no bridges are configured, Tor will
6228 now refuse to build any circuits until some bridges are set.
6229 If "UseBridges auto" is set, Tor will use bridges if they are
6230 configured and we are not running as a server, but otherwise will
6231 make circuits as usual. The new default is "auto". Patch by anonym,
6232 so the Tails LiveCD can stop automatically revealing you as a Tor
6236 - Fix warnings from GCC 4.6's "-Wunused-but-set-variable" option.
6237 - Remove a trailing asterisk from "exit-policy/default" in the
6238 output of the control port command "GETINFO info/names". Bugfix
6240 - Use a wide type to hold sockets when built for 64-bit Windows builds.
6242 - Warn when the user configures two HiddenServiceDir lines that point
6243 to the same directory. Bugfix on 0.0.6 (the version introducing
6244 HiddenServiceDir); fixes bug 3289.
6245 - Remove dead code from rend_cache_lookup_v2_desc_as_dir. Fixes
6246 part of bug 2748; bugfix on 0.2.0.10-alpha.
6247 - Log malformed requests for rendezvous descriptors as protocol
6248 warnings, not warnings. Also, use a more informative log message
6249 in case someone sees it at log level warning without prior
6250 info-level messages. Fixes the other part of bug 2748; bugfix
6252 - Clear the table recording the time of the last request for each
6253 hidden service descriptor from each HS directory on SIGNAL NEWNYM.
6254 Previously, we would clear our HS descriptor cache on SIGNAL
6255 NEWNYM, but if we had previously retrieved a descriptor (or tried
6256 to) from every directory responsible for it, we would refuse to
6257 fetch it again for up to 15 minutes. Bugfix on 0.2.2.25-alpha;
6259 - Fix a log message that said "bits" while displaying a value in
6260 bytes. Found by wanoskarnet. Fixes bug 3318; bugfix on
6262 - When checking for 1024-bit keys, check for 1024 bits, not 128
6263 bytes. This allows Tor to correctly discard keys of length 1017
6264 through 1023. Bugfix on 0.0.9pre5.
6267 - Relays now log the reason for publishing a new relay descriptor,
6268 so we have a better chance of hunting down instances of bug 1810.
6269 Resolves ticket 3252.
6270 - Revise most log messages that refer to nodes by nickname to
6271 instead use the "$key=nickname at address" format. This should be
6272 more useful, especially since nicknames are less and less likely
6273 to be unique. Resolves ticket 3045.
6274 - Log (at info level) when purging pieces of hidden-service-client
6275 state because of SIGNAL NEWNYM.
6278 - Remove undocumented option "-F" from tor-resolve: it hasn't done
6279 anything since 0.2.1.16-rc.
6282 Changes in version 0.2.2.27-beta - 2011-05-18
6283 Tor 0.2.2.27-beta fixes a bridge-related stability bug in the previous
6284 release, and also adds a few more general bugfixes.
6287 - Fix a crash bug when changing bridges in a running Tor process.
6288 Fixes bug 3213; bugfix on 0.2.2.26-beta.
6289 - When the controller configures a new bridge, don't wait 10 to 60
6290 seconds before trying to fetch its descriptor. Bugfix on
6291 0.2.0.3-alpha; fixes bug 3198 (suggested by 2355).
6294 - Require that onion keys have exponent 65537 in microdescriptors too.
6295 Fixes more of bug 3207; bugfix on 0.2.2.26-beta.
6296 - Tor used to limit HttpProxyAuthenticator values to 48 characters.
6297 Changed the limit to 512 characters by removing base64 newlines.
6298 Fixes bug 2752. Fix by Michael Yakubovich.
6299 - When a client starts or stops using bridges, never use a circuit
6300 that was built before the configuration change. This behavior could
6301 put at risk a user who uses bridges to ensure that her traffic
6302 only goes to the chosen addresses. Bugfix on 0.2.0.3-alpha; fixes
6306 Changes in version 0.2.2.26-beta - 2011-05-17
6307 Tor 0.2.2.26-beta fixes a variety of potential privacy problems. It
6308 also introduces a new "socksport auto" approach that should make it
6309 easier to run multiple Tors on the same system, and does a lot of
6310 cleanup to get us closer to a release candidate.
6312 o Security/privacy fixes:
6313 - Replace all potentially sensitive memory comparison operations
6314 with versions whose runtime does not depend on the data being
6315 compared. This will help resist a class of attacks where an
6316 adversary can use variations in timing information to learn
6317 sensitive data. Fix for one case of bug 3122. (Safe memcmp
6318 implementation by Robert Ransom based partially on code by DJB.)
6319 - When receiving a hidden service descriptor, check that it is for
6320 the hidden service we wanted. Previously, Tor would store any
6321 hidden service descriptors that a directory gave it, whether it
6322 wanted them or not. This wouldn't have let an attacker impersonate
6323 a hidden service, but it did let directories pre-seed a client
6324 with descriptors that it didn't want. Bugfix on 0.0.6.
6325 - On SIGHUP, do not clear out all TrackHostExits mappings, client
6326 DNS cache entries, and virtual address mappings: that's what
6327 NEWNYM is for. Fixes bug 1345; bugfix on 0.1.0.1-rc.
6330 - The options SocksPort, ControlPort, and so on now all accept a
6331 value "auto" that opens a socket on an OS-selected port. A
6332 new ControlPortWriteToFile option tells Tor to write its
6333 actual control port or ports to a chosen file. If the option
6334 ControlPortFileGroupReadable is set, the file is created as
6335 group-readable. Now users can run two Tor clients on the same
6336 system without needing to manually mess with parameters. Resolves
6337 part of ticket 3076.
6338 - Set SO_REUSEADDR on all sockets, not just listeners. This should
6339 help busy exit nodes avoid running out of useable ports just
6340 because all the ports have been used in the near past. Resolves
6344 - New "GETINFO net/listeners/(type)" controller command to return
6345 a list of addresses and ports that are bound for listeners for a
6346 given connection type. This is useful when the user has configured
6347 "SocksPort auto" and the controller needs to know which port got
6348 chosen. Resolves another part of ticket 3076.
6349 - Add a new ControlSocketsGroupWritable configuration option: when
6350 it is turned on, ControlSockets are group-writeable by the default
6351 group of the current user. Patch by Jérémy Bobbio; implements
6353 - Tor now refuses to create a ControlSocket in a directory that is
6354 world-readable (or group-readable if ControlSocketsGroupWritable
6355 is 0). This is necessary because some operating systems do not
6356 enforce permissions on an AF_UNIX sockets. Permissions on the
6357 directory holding the socket, however, seems to work everywhere.
6358 - Rate-limit a warning about failures to download v2 networkstatus
6359 documents. Resolves part of bug 1352.
6360 - Backport code from 0.2.3.x that allows directory authorities to
6361 clean their microdescriptor caches. Needed to resolve bug 2230.
6362 - When an HTTPS proxy reports "403 Forbidden", we now explain
6363 what it means rather than calling it an unexpected status code.
6364 Closes bug 2503. Patch from Michael Yakubovich.
6365 - Update to the May 1 2011 Maxmind GeoLite Country database.
6368 - Authorities now clean their microdesc cache periodically and when
6369 reading from disk initially, not only when adding new descriptors.
6370 This prevents a bug where we could lose microdescriptors. Bugfix
6371 on 0.2.2.6-alpha. Fixes bug 2230.
6372 - Do not crash when our configuration file becomes unreadable, for
6373 example due to a permissions change, between when we start up
6374 and when a controller calls SAVECONF. Fixes bug 3135; bugfix
6376 - Avoid a bug that would keep us from replacing a microdescriptor
6377 cache on Windows. (We would try to replace the file while still
6378 holding it open. That's fine on Unix, but Windows doesn't let us
6379 do that.) Bugfix on 0.2.2.6-alpha; bug found by wanoskarnet.
6380 - Add missing explanations for the authority-related torrc options
6381 RephistTrackTime, BridgePassword, and V3AuthUseLegacyKey in the
6382 man page. Resolves issue 2379.
6383 - As an authority, do not upload our own vote or signature set to
6384 ourself. It would tell us nothing new, and as of 0.2.2.24-alpha,
6385 it would get flagged as a duplicate. Resolves bug 3026.
6386 - Accept hidden service descriptors if we think we might be a hidden
6387 service directory, regardless of what our consensus says. This
6388 helps robustness, since clients and hidden services can sometimes
6389 have a more up-to-date view of the network consensus than we do,
6390 and if they think that the directory authorities list us a HSDir,
6391 we might actually be one. Related to bug 2732; bugfix on
6393 - When a controller changes TrackHostExits, remove mappings for
6394 hosts that should no longer have their exits tracked. Bugfix on
6396 - When a controller changes VirtualAddrNetwork, remove any mappings
6397 for hosts that were automapped to the old network. Bugfix on
6399 - When a controller changes one of the AutomapHosts* options, remove
6400 any mappings for hosts that should no longer be automapped. Bugfix
6402 - Do not reset the bridge descriptor download status every time we
6403 re-parse our configuration or get a configuration change. Fixes
6404 bug 3019; bugfix on 0.2.0.3-alpha.
6406 o Minor bugfixes (code cleanup):
6407 - When loading the microdesc journal, remember its current size.
6408 In 0.2.2, this helps prevent the microdesc journal from growing
6409 without limit on authorities (who are the only ones to use it in
6410 0.2.2). Fixes a part of bug 2230; bugfix on 0.2.2.6-alpha.
6411 Fix posted by "cypherpunks."
6412 - The microdesc journal is supposed to get rebuilt only if it is
6413 at least _half_ the length of the store, not _twice_ the length
6414 of the store. Bugfix on 0.2.2.6-alpha; fixes part of bug 2230.
6415 - Fix a potential null-pointer dereference while computing a
6416 consensus. Bugfix on tor-0.2.0.3-alpha, found with the help of
6418 - Avoid a possible null-pointer dereference when rebuilding the mdesc
6419 cache without actually having any descriptors to cache. Bugfix on
6420 0.2.2.6-alpha. Issue discovered using clang's static analyzer.
6421 - If we fail to compute the identity digest of a v3 legacy keypair,
6422 warn, and don't use a buffer-full of junk instead. Bugfix on
6423 0.2.1.1-alpha; fixes bug 3106.
6424 - Resolve an untriggerable issue in smartlist_string_num_isin(),
6425 where if the function had ever in the future been used to check
6426 for the presence of a too-large number, it would have given an
6427 incorrect result. (Fortunately, we only used it for 16-bit
6428 values.) Fixes bug 3175; bugfix on 0.1.0.1-rc.
6429 - Require that introduction point keys and onion handshake keys
6430 have a public exponent of 65537. Starts to fix bug 3207; bugfix
6434 - Caches no longer download and serve v2 networkstatus documents
6435 unless FetchV2Networkstatus flag is set: these documents haven't
6436 haven't been used by clients or relays since 0.2.0.x. Resolves
6440 Changes in version 0.2.3.1-alpha - 2011-05-05
6441 Tor 0.2.3.1-alpha adds some new experimental features, including support
6442 for an improved network IO backend, IOCP networking on Windows,
6443 microdescriptor caching, "fast-start" support for streams, and automatic
6444 home router configuration. There are also numerous internal improvements
6445 to try to make the code easier for developers to work with.
6447 This is the first alpha release in a new series, so expect there to be
6448 bugs. Users who would rather test out a more stable branch should
6449 stay with 0.2.2.x for now.
6452 - Tor can now optionally build with the "bufferevents" buffered IO
6453 backend provided by Libevent 2. To use this feature, make sure you
6454 have the latest possible version of Libevent, and pass the
6455 --enable-bufferevents flag to configure when building Tor from
6456 source. This feature will make our networking code more flexible,
6457 let us stack layers on each other, and let us use more efficient
6458 zero-copy transports where available.
6459 - As an experimental feature, Tor can use IOCP for networking on Windows.
6460 Once this code is tuned and optimized, it promises much better
6461 performance than the select-based backend we've used in the past. To
6462 try this feature, you must build Tor with Libevent 2, configure Tor
6463 with the "bufferevents" buffered IO backend, and add "DisableIOCP 0" to
6464 your torrc. There are known bugs here: only try this if you can help
6465 debug it as it breaks.
6466 - The EntryNodes option can now include country codes like {de} or IP
6467 addresses or network masks. Previously we had disallowed these options
6468 because we didn't have an efficient way to keep the list up to
6469 date. Fixes bug 1982, but see bug 2798 for an unresolved issue here.
6470 - Exit nodes now accept and queue data on not-yet-connected streams.
6471 Previously, the client wasn't allowed to send data until the stream was
6472 connected, which slowed down all connections. This change will enable
6473 clients to perform a "fast-start" on streams and send data without
6474 having to wait for a confirmation that the stream has opened. (Patch
6475 from Ian Goldberg; implements the server side of Proposal 174.)
6476 - Tor now has initial support for automatic port mapping on the many
6477 home routers that support NAT-PMP or UPnP. (Not yet supported on
6478 Windows). To build the support code, you'll need to have libnatpnp
6479 library and/or the libminiupnpc library, and you'll need to enable the
6480 feature specifically by passing "--enable-upnp" and/or
6481 "--enable-natpnp" to configure. To turn it on, use the new
6482 PortForwarding option.
6483 - Caches now download, cache, and serve multiple "flavors" of the
6484 consensus, including a flavor that describes microdescriptors.
6485 - Caches now download, cache, and serve microdescriptors -- small
6486 summaries of router descriptors that are authenticated by all of the
6487 directory authorities. Once enough caches are running this code,
6488 clients will be able to save significant amounts of directory bandwidth
6489 by downloading microdescriptors instead of router descriptors.
6492 - Make logging resolution configurable with a new LogTimeGranularity
6493 option, and change the default from 1 millisecond to 1 second.
6494 Implements enhancement 1668.
6495 - We log which torrc file we're using on startup. Implements ticket
6497 - Ordinarily, Tor does not count traffic from private addresses (like
6498 127.0.0.1 or 10.0.0.1) when calculating rate limits or accounting.
6499 There is now a new option, CountPrivateBandwidth, to disable this
6500 behavior. Patch from Daniel Cagara.
6501 - New --enable-static-tor configure option for building Tor as
6502 statically as possible. Idea, general hackery and thoughts from
6503 Alexei Czeskis, John Gilmore, Jacob Appelbaum. Implements ticket
6505 - If you set the NumCPUs option to 0, Tor will now try to detect how
6506 many CPUs you have. This is the new default behavior.
6507 - Turn on directory request statistics by default and include them in
6508 extra-info descriptors. Don't break if we have no GeoIP database.
6509 - Relays that set "ConnDirectionStatistics 1" write statistics on the
6510 bidirectional use of connections to disk every 24 hours.
6511 - Add a GeoIP file digest to the extra-info descriptor. Implements
6513 - The NodeFamily option -- which let you declare that you want to
6514 consider nodes to be part of a family whether they list themselves
6515 that way or not -- now allows IP address ranges and country codes.
6516 - Add a new 'Heartbeat' log message type to periodically log a message
6517 describing Tor's status at level Notice. This feature is meant for
6518 operators who log at notice, and want to make sure that their Tor
6519 server is still working. Implementation by George Kadianakis.
6521 o Minor bugfixes (on 0.2.2.25-alpha):
6522 - When loading the microdesc journal, remember its current size.
6523 In 0.2.2, this helps prevent the microdesc journal from growing
6524 without limit on authorities (who are the only ones to use it in
6525 0.2.2). Fixes a part of bug 2230; bugfix on 0.2.2.6-alpha.
6526 Fix posted by "cypherpunks."
6527 - The microdesc journal is supposed to get rebuilt only if it is
6528 at least _half_ the length of the store, not _twice_ the length
6529 of the store. Bugfix on 0.2.2.6-alpha; fixes part of bug 2230.
6530 - If as an authority we fail to compute the identity digest of a v3
6531 legacy keypair, warn, and don't use a buffer-full of junk instead.
6532 Bugfix on 0.2.1.1-alpha; fixes bug 3106.
6533 - Authorities now clean their microdesc cache periodically and when
6534 reading from disk initially, not only when adding new descriptors.
6535 This prevents a bug where we could lose microdescriptors. Bugfix
6538 o Minor features (controller):
6539 - Add a new SIGNAL event to the controller interface so that
6540 controllers can be notified when Tor handles a signal. Resolves
6541 issue 1955. Patch by John Brooks.
6542 - Add a new GETINFO option to get total bytes read and written. Patch
6543 from pipe, revised by atagar. Resolves ticket 2345.
6544 - Implement some GETINFO controller fields to provide information about
6545 the Tor process's pid, euid, username, and resource limits.
6548 - Our build system requires automake 1.6 or later to create the
6549 Makefile.in files. Previously, you could have used 1.4.
6550 This only affects developers and people building Tor from git;
6551 people who build Tor from the source distribution without changing
6552 the Makefile.am files should be fine.
6553 - Our autogen.sh script uses autoreconf to launch autoconf, automake, and
6554 so on. This is more robust against some of the failure modes
6555 associated with running the autotools pieces on their own.
6557 o Minor packaging issues:
6558 - On OpenSUSE, create the /var/run/tor directory on startup if it is not
6559 already created. Patch from Andreas Stieger. Fixes bug 2573.
6561 o Code simplifications and refactoring:
6562 - A major revision to our internal node-selecting and listing logic.
6563 Tor already had at least two major ways to look at the question of
6564 "which Tor servers do we know about": a list of router descriptors,
6565 and a list of entries in the current consensus. With
6566 microdescriptors, we're adding a third. Having so many systems
6567 without an abstraction layer over them was hurting the codebase.
6568 Now, we have a new "node_t" abstraction that presents a consistent
6569 interface to a client's view of a Tor node, and holds (nearly) all
6570 of the mutable state formerly in routerinfo_t and routerstatus_t.
6571 - The helper programs tor-gencert, tor-resolve, and tor-checkkey
6572 no longer link against Libevent: they never used it, but
6573 our library structure used to force them to link it.
6576 - Remove some old code to work around even older versions of Tor that
6577 used forked processes to handle DNS requests. Such versions of Tor
6578 are no longer in use as servers.
6580 o Documentation fixes:
6581 - Correct a broken faq link in the INSTALL file. Fixes bug 2307.
6582 - Add missing documentation for the authority-related torrc options
6583 RephistTrackTime, BridgePassword, and V3AuthUseLegacyKey. Resolves
6587 Changes in version 0.2.2.25-alpha - 2011-04-29
6588 Tor 0.2.2.25-alpha fixes many bugs: hidden service clients are more
6589 robust, routers no longer overreport their bandwidth, Win7 should crash
6590 a little less, and NEWNYM (as used by Vidalia's "new identity" button)
6591 now prevents hidden service-related activity from being linkable. It
6592 provides more information to Vidalia so you can see if your bridge is
6593 working. Also, 0.2.2.25-alpha revamps the Entry/Exit/ExcludeNodes and
6594 StrictNodes configuration options to make them more reliable, more
6595 understandable, and more regularly applied. If you use those options,
6596 please see the revised documentation for them in the manual page.
6599 - Relays were publishing grossly inflated bandwidth values because
6600 they were writing their state files wrong--now they write the
6601 correct value. Also, resume reading bandwidth history from the
6602 state file correctly. Fixes bug 2704; bugfix on 0.2.2.23-alpha.
6603 - Improve hidden service robustness: When we find that we have
6604 extended a hidden service's introduction circuit to a relay not
6605 listed as an introduction point in the HS descriptor we currently
6606 have, retry with an introduction point from the current
6607 descriptor. Previously we would just give up. Fixes bugs 1024 and
6608 1930; bugfix on 0.2.0.10-alpha.
6609 - Clients now stop trying to use an exit node associated with a given
6610 destination by TrackHostExits if they fail to reach that exit node.
6611 Fixes bug 2999. Bugfix on 0.2.0.20-rc.
6612 - Fix crash bug on platforms where gmtime and localtime can return
6613 NULL. Windows 7 users were running into this one. Fixes part of bug
6614 2077. Bugfix on all versions of Tor. Found by boboper.
6616 o Security and stability fixes:
6617 - Don't double-free a parsable, but invalid, microdescriptor, even if
6618 it is followed in the blob we're parsing by an unparsable
6619 microdescriptor. Fixes an issue reported in a comment on bug 2954.
6620 Bugfix on 0.2.2.6-alpha; fix by "cypherpunks".
6621 - If the Nickname configuration option isn't given, Tor would pick a
6622 nickname based on the local hostname as the nickname for a relay.
6623 Because nicknames are not very important in today's Tor and the
6624 "Unnamed" nickname has been implemented, this is now problematic
6625 behavior: It leaks information about the hostname without being
6626 useful at all. Fixes bug 2979; bugfix on 0.1.2.2-alpha, which
6627 introduced the Unnamed nickname. Reported by tagnaq.
6628 - Fix an uncommon assertion failure when running with DNSPort under
6629 heavy load. Fixes bug 2933; bugfix on 0.2.0.1-alpha.
6630 - Avoid linkability based on cached hidden service descriptors: forget
6631 all hidden service descriptors cached as a client when processing a
6632 SIGNAL NEWNYM command. Fixes bug 3000; bugfix on 0.0.6.
6635 - Export GeoIP information on bridge usage to controllers even if we
6636 have not yet been running for 24 hours. Now Vidalia bridge operators
6637 can get more accurate and immediate feedback about their
6638 contributions to the network.
6640 o Major features and bugfixes (node selection):
6641 - Revise and reconcile the meaning of the ExitNodes, EntryNodes,
6642 ExcludeEntryNodes, ExcludeExitNodes, ExcludeNodes, and StrictNodes
6643 options. Previously, we had been ambiguous in describing what
6644 counted as an "exit" node, and what operations exactly "StrictNodes
6645 0" would permit. This created confusion when people saw nodes built
6646 through unexpected circuits, and made it hard to tell real bugs from
6647 surprises. Now the intended behavior is:
6648 . "Exit", in the context of ExitNodes and ExcludeExitNodes, means
6649 a node that delivers user traffic outside the Tor network.
6650 . "Entry", in the context of EntryNodes, means a node used as the
6651 first hop of a multihop circuit. It doesn't include direct
6652 connections to directory servers.
6653 . "ExcludeNodes" applies to all nodes.
6654 . "StrictNodes" changes the behavior of ExcludeNodes only. When
6655 StrictNodes is set, Tor should avoid all nodes listed in
6656 ExcludeNodes, even when it will make user requests fail. When
6657 StrictNodes is *not* set, then Tor should follow ExcludeNodes
6658 whenever it can, except when it must use an excluded node to
6659 perform self-tests, connect to a hidden service, provide a
6660 hidden service, fulfill a .exit request, upload directory
6661 information, or fetch directory information.
6662 Collectively, the changes to implement the behavior fix bug 1090.
6663 - ExcludeNodes now takes precedence over EntryNodes and ExitNodes: if
6664 a node is listed in both, it's treated as excluded.
6665 - ExcludeNodes now applies to directory nodes -- as a preference if
6666 StrictNodes is 0, or an absolute requirement if StrictNodes is 1.
6667 Don't exclude all the directory authorities and set StrictNodes to 1
6668 unless you really want your Tor to break.
6669 - ExcludeNodes and ExcludeExitNodes now override exit enclaving.
6670 - ExcludeExitNodes now overrides .exit requests.
6671 - We don't use bridges listed in ExcludeNodes.
6672 - When StrictNodes is 1:
6673 . We now apply ExcludeNodes to hidden service introduction points
6674 and to rendezvous points selected by hidden service users. This
6675 can make your hidden service less reliable: use it with caution!
6676 . If we have used ExcludeNodes on ourself, do not try relay
6677 reachability self-tests.
6678 . If we have excluded all the directory authorities, we will not
6679 even try to upload our descriptor if we're a relay.
6680 . Do not honor .exit requests to an excluded node.
6681 - Remove a misfeature that caused us to ignore the Fast/Stable flags
6682 when ExitNodes is set. Bugfix on 0.2.2.7-alpha.
6683 - When the set of permitted nodes changes, we now remove any mappings
6684 introduced via TrackExitHosts to now-excluded nodes. Bugfix on
6686 - We never cannibalize a circuit that had excluded nodes on it, even
6687 if StrictNodes is 0. Bugfix on 0.1.0.1-rc.
6688 - Revert a change where we would be laxer about attaching streams to
6689 circuits than when building the circuits. This was meant to prevent
6690 a set of bugs where streams were never attachable, but our improved
6691 code here should make this unnecessary. Bugfix on 0.2.2.7-alpha.
6692 - Keep track of how many times we launch a new circuit to handle a
6693 given stream. Too many launches could indicate an inconsistency
6694 between our "launch a circuit to handle this stream" logic and our
6695 "attach this stream to one of the available circuits" logic.
6696 - Improve log messages related to excluded nodes.
6699 - Fix a spurious warning when moving from a short month to a long
6700 month on relays with month-based BandwidthAccounting. Bugfix on
6701 0.2.2.17-alpha; fixes bug 3020.
6702 - When a client finds that an origin circuit has run out of 16-bit
6703 stream IDs, we now mark it as unusable for new streams. Previously,
6704 we would try to close the entire circuit. Bugfix on 0.0.6.
6705 - Add a forgotten cast that caused a compile warning on OS X 10.6.
6706 Bugfix on 0.2.2.24-alpha.
6707 - Be more careful about reporting the correct error from a failed
6708 connect() system call. Under some circumstances, it was possible to
6709 look at an incorrect value for errno when sending the end reason.
6710 Bugfix on 0.1.0.1-rc.
6711 - Correctly handle an "impossible" overflow cases in connection byte
6712 counting, where we write or read more than 4GB on an edge connection
6713 in a single second. Bugfix on 0.1.2.8-beta.
6714 - Correct the warning displayed when a rendezvous descriptor exceeds
6715 the maximum size. Fixes bug 2750; bugfix on 0.2.1.5-alpha. Found by
6717 - Clients and hidden services now use HSDir-flagged relays for hidden
6718 service descriptor downloads and uploads even if the relays have no
6719 DirPort set and the client has disabled TunnelDirConns. This will
6720 eventually allow us to give the HSDir flag to relays with no
6721 DirPort. Fixes bug 2722; bugfix on 0.2.1.6-alpha.
6722 - Downgrade "no current certificates known for authority" message from
6723 Notice to Info. Fixes bug 2899; bugfix on 0.2.0.10-alpha.
6724 - Make the SIGNAL DUMP control-port command work on FreeBSD. Fixes bug
6725 2917. Bugfix on 0.1.1.1-alpha.
6726 - Only limit the lengths of single HS descriptors, even when multiple
6727 HS descriptors are published to an HSDir relay in a single POST
6728 operation. Fixes bug 2948; bugfix on 0.2.1.5-alpha. Found by hsdir.
6729 - Write the current time into the LastWritten line in our state file,
6730 rather than the time from the previous write attempt. Also, stop
6731 trying to use a time of -1 in our log statements. Fixes bug 3039;
6732 bugfix on 0.2.2.14-alpha.
6733 - Be more consistent in our treatment of file system paths. "~" should
6734 get expanded to the user's home directory in the Log config option.
6735 Fixes bug 2971; bugfix on 0.2.0.1-alpha, which introduced the
6736 feature for the -f and --DataDirectory options.
6739 - Make sure every relay writes a state file at least every 12 hours.
6740 Previously, a relay could go for weeks without writing its state
6741 file, and on a crash could lose its bandwidth history, capacity
6742 estimates, client country statistics, and so on. Addresses bug 3012.
6743 - Send END_STREAM_REASON_NOROUTE in response to EHOSTUNREACH errors.
6744 Clients before 0.2.1.27 didn't handle NOROUTE correctly, but such
6745 clients are already deprecated because of security bugs.
6746 - Don't allow v0 hidden service authorities to act as clients.
6747 Required by fix for bug 3000.
6748 - Ignore SIGNAL NEWNYM commands on relay-only Tor instances. Required
6749 by fix for bug 3000.
6750 - Ensure that no empty [dirreq-](read|write)-history lines are added
6751 to an extrainfo document. Implements ticket 2497.
6753 o Code simplification and refactoring:
6754 - Remove workaround code to handle directory responses from servers
6755 that had bug 539 (they would send HTTP status 503 responses _and_
6756 send a body too). Since only server versions before
6757 0.2.0.16-alpha/0.1.2.19 were affected, there is no longer reason to
6758 keep the workaround in place.
6759 - Remove the old 'fuzzy time' logic. It was supposed to be used for
6760 handling calculations where we have a known amount of clock skew and
6761 an allowed amount of unknown skew. But we only used it in three
6762 places, and we never adjusted the known/unknown skew values. This is
6763 still something we might want to do someday, but if we do, we'll
6764 want to do it differently.
6765 - Avoid signed/unsigned comparisons by making SIZE_T_CEILING unsigned.
6766 None of the cases where we did this before were wrong, but by making
6767 this change we avoid warnings. Fixes bug 2475; bugfix on 0.2.1.28.
6768 - Use GetTempDir to find the proper temporary directory location on
6769 Windows when generating temporary files for the unit tests. Patch by
6773 Changes in version 0.2.2.24-alpha - 2011-04-08
6774 Tor 0.2.2.24-alpha fixes a variety of bugs, including a big bug that
6775 prevented Tor clients from effectively using "multihomed" bridges,
6776 that is, bridges that listen on multiple ports or IP addresses so users
6777 can continue to use some of their addresses even if others get blocked.
6780 - Fix a bug where bridge users who configure the non-canonical
6781 address of a bridge automatically switch to its canonical
6782 address. If a bridge listens at more than one address, it should be
6783 able to advertise those addresses independently and any non-blocked
6784 addresses should continue to work. Bugfix on Tor 0.2.0.x. Fixes
6786 - If you configured Tor to use bridge A, and then quit and
6787 configured Tor to use bridge B instead, it would happily continue
6788 to use bridge A if it's still reachable. While this behavior is
6789 a feature if your goal is connectivity, in some scenarios it's a
6790 dangerous bug. Bugfix on Tor 0.2.0.1-alpha; fixes bug 2511.
6791 - Directory authorities now use data collected from their own
6792 uptime observations when choosing whether to assign the HSDir flag
6793 to relays, instead of trusting the uptime value the relay reports in
6794 its descriptor. This change helps prevent an attack where a small
6795 set of nodes with frequently-changing identity keys can blackhole
6796 a hidden service. (Only authorities need upgrade; others will be
6797 fine once they do.) Bugfix on 0.2.0.10-alpha; fixes bug 2709.
6800 - When we restart our relay, we might get a successful connection
6801 from the outside before we've started our reachability tests,
6802 triggering a warning: "ORPort found reachable, but I have no
6803 routerinfo yet. Failing to inform controller of success." This
6804 bug was harmless unless Tor is running under a controller
6805 like Vidalia, in which case the controller would never get a
6806 REACHABILITY_SUCCEEDED status event. Bugfix on 0.1.2.6-alpha;
6808 - Make directory authorities more accurate at recording when
6809 relays that have failed several reachability tests became
6810 unreachable, so we can provide more accuracy at assigning Stable,
6811 Guard, HSDir, etc flags. Bugfix on 0.2.0.6-alpha. Resolves bug 2716.
6812 - Fix an issue that prevented static linking of libevent on
6813 some platforms (notably Linux). Fixes bug 2698; bugfix on
6814 versions 0.2.1.23/0.2.2.8-alpha (the versions introducing
6815 the --with-static-libevent configure option).
6816 - We now ask the other side of a stream (the client or the exit)
6817 for more data on that stream when the amount of queued data on
6818 that stream dips low enough. Previously, we wouldn't ask the
6819 other side for more data until either it sent us more data (which
6820 it wasn't supposed to do if it had exhausted its window!) or we
6821 had completely flushed all our queued data. This flow control fix
6822 should improve throughput. Fixes bug 2756; bugfix on the earliest
6823 released versions of Tor (svn commit r152).
6824 - Avoid a double-mark-for-free warning when failing to attach a
6825 transparent proxy connection. (We thought we had fixed this in
6826 0.2.2.23-alpha, but it turns out our fix was checking the wrong
6827 connection.) Fixes bug 2757; bugfix on 0.1.2.1-alpha (the original
6828 bug) and 0.2.2.23-alpha (the incorrect fix).
6829 - When warning about missing zlib development packages during compile,
6830 give the correct package names. Bugfix on 0.2.0.1-alpha.
6833 - Directory authorities now log the source of a rejected POSTed v3
6835 - Make compilation with clang possible when using
6836 --enable-gcc-warnings by removing two warning options that clang
6837 hasn't implemented yet and by fixing a few warnings. Implements
6839 - When expiring circuits, use microsecond timers rather than
6840 one-second timers. This can avoid an unpleasant situation where a
6841 circuit is launched near the end of one second and expired right
6842 near the beginning of the next, and prevent fluctuations in circuit
6844 - Use computed circuit-build timeouts to decide when to launch
6845 parallel introduction circuits for hidden services. (Previously,
6846 we would retry after 15 seconds.)
6847 - Update to the April 1 2011 Maxmind GeoLite Country database.
6850 - Create the /var/run/tor directory on startup on OpenSUSE if it is
6851 not already created. Patch from Andreas Stieger. Fixes bug 2573.
6853 o Documentation changes:
6854 - Modernize the doxygen configuration file slightly. Fixes bug 2707.
6855 - Resolve all doxygen warnings except those for missing documentation.
6857 - Add doxygen documentation for more functions, fields, and types.
6860 Changes in version 0.2.2.23-alpha - 2011-03-08
6861 Tor 0.2.2.23-alpha lets relays record their bandwidth history so when
6862 they restart they don't lose their bandwidth capacity estimate. This
6863 release also fixes a diverse set of user-facing bugs, ranging from
6864 relays overrunning their rate limiting to clients falsely warning about
6865 clock skew to bridge descriptor leaks by our bridge directory authority.
6868 - Stop sending a CLOCK_SKEW controller status event whenever
6869 we fetch directory information from a relay that has a wrong clock.
6870 Instead, only inform the controller when it's a trusted authority
6871 that claims our clock is wrong. Bugfix on 0.1.2.6-alpha; fixes
6872 the rest of bug 1074.
6873 - Fix an assert in parsing router descriptors containing IPv6
6874 addresses. This one took down the directory authorities when
6875 somebody tried some experimental code. Bugfix on 0.2.1.3-alpha.
6876 - Make the bridge directory authority refuse to answer directory
6877 requests for "all" descriptors. It used to include bridge
6878 descriptors in its answer, which was a major information leak.
6879 Found by "piebeer". Bugfix on 0.2.0.3-alpha.
6880 - If relays set RelayBandwidthBurst but not RelayBandwidthRate,
6881 Tor would ignore their RelayBandwidthBurst setting,
6882 potentially using more bandwidth than expected. Bugfix on
6883 0.2.0.1-alpha. Reported by Paul Wouters. Fixes bug 2470.
6884 - Ignore and warn if the user mistakenly sets "PublishServerDescriptor
6885 hidserv" in her torrc. The 'hidserv' argument never controlled
6886 publication of hidden service descriptors. Bugfix on 0.2.0.1-alpha.
6889 - Relays now save observed peak bandwidth throughput rates to their
6890 state file (along with total usage, which was already saved)
6891 so that they can determine their correct estimated bandwidth on
6892 restart. Resolves bug 1863, where Tor relays would reset their
6893 estimated bandwidth to 0 after restarting.
6894 - Directory authorities now take changes in router IP address and
6895 ORPort into account when determining router stability. Previously,
6896 if a router changed its IP or ORPort, the authorities would not
6897 treat it as having any downtime for the purposes of stability
6898 calculation, whereas clients would experience downtime since the
6899 change could take a while to propagate to them. Resolves issue 1035.
6900 - Enable Address Space Layout Randomization (ASLR) and Data Execution
6901 Prevention (DEP) by default on Windows to make it harder for
6902 attackers to exploit vulnerabilities. Patch from John Brooks.
6904 o Minor bugfixes (on 0.2.1.x and earlier):
6905 - Fix a rare crash bug that could occur when a client was configured
6906 with a large number of bridges. Fixes bug 2629; bugfix on
6907 0.2.1.2-alpha. Bugfix by trac user "shitlei".
6908 - Avoid a double mark-for-free warning when failing to attach a
6909 transparent proxy connection. Bugfix on 0.1.2.1-alpha. Fixes
6911 - Correctly detect failure to allocate an OpenSSL BIO. Fixes bug 2378;
6912 found by "cypherpunks". This bug was introduced before the first
6913 Tor release, in svn commit r110.
6914 - Country codes aren't supported in EntryNodes until 0.2.3.x, so
6915 don't mention them in the manpage. Fixes bug 2450; issue
6916 spotted by keb and G-Lo.
6917 - Fix a bug in bandwidth history state parsing that could have been
6918 triggered if a future version of Tor ever changed the timing
6919 granularity at which bandwidth history is measured. Bugfix on
6921 - When a relay decides that its DNS is too broken for it to serve
6922 as an exit server, it advertised itself as a non-exit, but
6923 continued to act as an exit. This could create accidental
6924 partitioning opportunities for users. Instead, if a relay is
6925 going to advertise reject *:* as its exit policy, it should
6926 really act with exit policy "reject *:*". Fixes bug 2366.
6927 Bugfix on Tor 0.1.2.5-alpha. Bugfix by user "postman" on trac.
6928 - In the special case where you configure a public exit relay as your
6929 bridge, Tor would be willing to use that exit relay as the last
6930 hop in your circuit as well. Now we fail that circuit instead.
6931 Bugfix on 0.2.0.12-alpha. Fixes bug 2403. Reported by "piebeer".
6932 - Fix a bug with our locking implementation on Windows that couldn't
6933 correctly detect when a file was already locked. Fixes bug 2504,
6934 bugfix on 0.2.1.6-alpha.
6935 - Fix IPv6-related connect() failures on some platforms (BSD, OS X).
6936 Bugfix on 0.2.0.3-alpha; fixes first part of bug 2660. Patch by
6938 - Set target port in get_interface_address6() correctly. Bugfix
6939 on 0.1.1.4-alpha and 0.2.0.3-alpha; fixes second part of bug 2660.
6940 - Directory authorities are now more robust to hops back in time
6941 when calculating router stability. Previously, if a run of uptime
6942 or downtime appeared to be negative, the calculation could give
6943 incorrect results. Bugfix on 0.2.0.6-alpha; noticed when fixing
6945 - Fix an assert that got triggered when using the TestingTorNetwork
6946 configuration option and then issuing a GETINFO config-text control
6947 command. Fixes bug 2250; bugfix on 0.2.1.2-alpha.
6949 o Minor bugfixes (on 0.2.2.x):
6950 - Clients should not weight BadExit nodes as Exits in their node
6951 selection. Similarly, directory authorities should not count BadExit
6952 bandwidth as Exit bandwidth when computing bandwidth-weights.
6953 Bugfix on 0.2.2.10-alpha; fixes bug 2203.
6954 - Correctly clear our dir_read/dir_write history when there is an
6955 error parsing any bw history value from the state file. Bugfix on
6957 - Resolve a bug in verifying signatures of directory objects
6958 with digests longer than SHA1. Bugfix on 0.2.2.20-alpha.
6959 Fixes bug 2409. Found by "piebeer".
6960 - Bridge authorities no longer crash on SIGHUP when they try to
6961 publish their relay descriptor to themselves. Fixes bug 2572. Bugfix
6965 - Log less aggressively about circuit timeout changes, and improve
6966 some other circuit timeout messages. Resolves bug 2004.
6967 - Log a little more clearly about the times at which we're no longer
6968 accepting new connections. Resolves bug 2181.
6969 - Reject attempts at the client side to open connections to private
6970 IP addresses (like 127.0.0.1, 10.0.0.1, and so on) with
6971 a randomly chosen exit node. Attempts to do so are always
6972 ill-defined, generally prevented by exit policies, and usually
6973 in error. This will also help to detect loops in transparent
6974 proxy configurations. You can disable this feature by setting
6975 "ClientRejectInternalAddresses 0" in your torrc.
6976 - Always treat failure to allocate an RSA key as an unrecoverable
6978 - Update to the March 1 2011 Maxmind GeoLite Country database.
6980 o Minor features (log subsystem):
6981 - Add documentation for configuring logging at different severities in
6982 different log domains. We've had this feature since 0.2.1.1-alpha,
6983 but for some reason it never made it into the manpage. Fixes
6985 - Make it simpler to specify "All log domains except for A and B".
6986 Previously you needed to say "[*,~A,~B]". Now you can just say
6988 - Add a "LogMessageDomains 1" option to include the domains of log
6989 messages along with the messages. Without this, there's no way
6990 to use log domains without reading the source or doing a lot
6993 o Packaging changes:
6994 - Stop shipping the Tor specs files and development proposal documents
6995 in the tarball. They are now in a separate git repository at
6996 git://git.torproject.org/torspec.git
6999 Changes in version 0.2.1.30 - 2011-02-23
7000 Tor 0.2.1.30 fixes a variety of less critical bugs. The main other
7001 change is a slight tweak to Tor's TLS handshake that makes relays
7002 and bridges that run this new version reachable from Iran again.
7003 We don't expect this tweak will win the arms race long-term, but it
7004 buys us time until we roll out a better solution.
7007 - Stop sending a CLOCK_SKEW controller status event whenever
7008 we fetch directory information from a relay that has a wrong clock.
7009 Instead, only inform the controller when it's a trusted authority
7010 that claims our clock is wrong. Bugfix on 0.1.2.6-alpha; fixes
7011 the rest of bug 1074.
7012 - Fix a bounds-checking error that could allow an attacker to
7013 remotely crash a directory authority. Bugfix on 0.2.1.5-alpha.
7015 - If relays set RelayBandwidthBurst but not RelayBandwidthRate,
7016 Tor would ignore their RelayBandwidthBurst setting,
7017 potentially using more bandwidth than expected. Bugfix on
7018 0.2.0.1-alpha. Reported by Paul Wouters. Fixes bug 2470.
7019 - Ignore and warn if the user mistakenly sets "PublishServerDescriptor
7020 hidserv" in her torrc. The 'hidserv' argument never controlled
7021 publication of hidden service descriptors. Bugfix on 0.2.0.1-alpha.
7024 - Adjust our TLS Diffie-Hellman parameters to match those used by
7026 - Update to the February 1 2011 Maxmind GeoLite Country database.
7029 - Check for and reject overly long directory certificates and
7030 directory tokens before they have a chance to hit any assertions.
7031 Bugfix on 0.2.1.28. Found by "doorss".
7032 - Bring the logic that gathers routerinfos and assesses the
7033 acceptability of circuits into line. This prevents a Tor OP from
7034 getting locked in a cycle of choosing its local OR as an exit for a
7035 path (due to a .exit request) and then rejecting the circuit because
7036 its OR is not listed yet. It also prevents Tor clients from using an
7037 OR running in the same instance as an exit (due to a .exit request)
7038 if the OR does not meet the same requirements expected of an OR
7039 running elsewhere. Fixes bug 1859; bugfix on 0.1.0.1-rc.
7041 o Packaging changes:
7042 - Stop shipping the Tor specs files and development proposal documents
7043 in the tarball. They are now in a separate git repository at
7044 git://git.torproject.org/torspec.git
7045 - Do not include Git version tags as though they are SVN tags when
7046 generating a tarball from inside a repository that has switched
7047 between branches. Bugfix on 0.2.1.15-rc; fixes bug 2402.
7050 Changes in version 0.2.2.22-alpha - 2011-01-25
7051 Tor 0.2.2.22-alpha fixes a few more less-critical security issues. The
7052 main other change is a slight tweak to Tor's TLS handshake that makes
7053 relays and bridges that run this new version reachable from Iran again.
7054 We don't expect this tweak will win the arms race long-term, but it
7055 will buy us a bit more time until we roll out a better solution.
7058 - Fix a bounds-checking error that could allow an attacker to
7059 remotely crash a directory authority. Bugfix on 0.2.1.5-alpha.
7061 - Don't assert when changing from bridge to relay or vice versa
7062 via the controller. The assert happened because we didn't properly
7063 initialize our keys in this case. Bugfix on 0.2.2.18-alpha; fixes
7064 bug 2433. Reported by bastik.
7067 - Adjust our TLS Diffie-Hellman parameters to match those used by
7069 - Provide a log message stating which geoip file we're parsing
7070 instead of just stating that we're parsing the geoip file.
7071 Implements ticket 2432.
7074 - Check for and reject overly long directory certificates and
7075 directory tokens before they have a chance to hit any assertions.
7076 Bugfix on 0.2.1.28 / 0.2.2.20-alpha. Found by "doorss".
7079 Changes in version 0.2.2.21-alpha - 2011-01-15
7080 Tor 0.2.2.21-alpha includes all the patches from Tor 0.2.1.29, which
7081 continues our recent code security audit work. The main fix resolves
7082 a remote heap overflow vulnerability that can allow remote code
7083 execution (CVE-2011-0427). Other fixes address a variety of assert
7084 and crash bugs, most of which we think are hard to exploit remotely.
7086 o Major bugfixes (security), also included in 0.2.1.29:
7087 - Fix a heap overflow bug where an adversary could cause heap
7088 corruption. This bug probably allows remote code execution
7089 attacks. Reported by "debuger". Fixes CVE-2011-0427. Bugfix on
7091 - Prevent a denial-of-service attack by disallowing any
7092 zlib-compressed data whose compression factor is implausibly
7093 high. Fixes part of bug 2324; reported by "doorss".
7094 - Zero out a few more keys in memory before freeing them. Fixes
7095 bug 2384 and part of bug 2385. These key instances found by
7096 "cypherpunks", based on Andrew Case's report about being able
7097 to find sensitive data in Tor's memory space if you have enough
7098 permissions. Bugfix on 0.0.2pre9.
7100 o Major bugfixes (crashes), also included in 0.2.1.29:
7101 - Prevent calls to Libevent from inside Libevent log handlers.
7102 This had potential to cause a nasty set of crashes, especially
7103 if running Libevent with debug logging enabled, and running
7104 Tor with a controller watching for low-severity log messages.
7105 Bugfix on 0.1.0.2-rc. Fixes bug 2190.
7106 - Add a check for SIZE_T_MAX to tor_realloc() to try to avoid
7107 underflow errors there too. Fixes the other part of bug 2324.
7108 - Fix a bug where we would assert if we ever had a
7109 cached-descriptors.new file (or another file read directly into
7110 memory) of exactly SIZE_T_CEILING bytes. Fixes bug 2326; bugfix
7111 on 0.2.1.25. Found by doorss.
7112 - Fix some potential asserts and parsing issues with grossly
7113 malformed router caches. Fixes bug 2352; bugfix on Tor 0.2.1.27.
7116 o Minor bugfixes (other), also included in 0.2.1.29:
7117 - Fix a bug with handling misformed replies to reverse DNS lookup
7118 requests in DNSPort. Bugfix on Tor 0.2.0.1-alpha. Related to a
7119 bug reported by doorss.
7120 - Fix compilation on mingw when a pthreads compatibility library
7121 has been installed. (We don't want to use it, so we shouldn't
7122 be including pthread.h.) Fixes bug 2313; bugfix on 0.1.0.1-rc.
7123 - Fix a bug where we would declare that we had run out of virtual
7124 addresses when the address space was only half-exhausted. Bugfix
7126 - Correctly handle the case where AutomapHostsOnResolve is set but
7127 no virtual addresses are available. Fixes bug 2328; bugfix on
7128 0.1.2.1-alpha. Bug found by doorss.
7129 - Correctly handle wrapping around when we run out of virtual
7130 address space. Found by cypherpunks; bugfix on 0.2.0.5-alpha.
7132 o Minor features, also included in 0.2.1.29:
7133 - Update to the January 1 2011 Maxmind GeoLite Country database.
7134 - Introduce output size checks on all of our decryption functions.
7136 o Build changes, also included in 0.2.1.29:
7137 - Tor does not build packages correctly with Automake 1.6 and earlier;
7138 added a check to Makefile.am to make sure that we're building with
7139 Automake 1.7 or later.
7140 - The 0.2.1.28 tarball was missing src/common/OpenBSD_malloc_Linux.c
7141 because we built it with a too-old version of automake. Thus that
7142 release broke ./configure --enable-openbsd-malloc, which is popular
7143 among really fast exit relays on Linux.
7145 o Major bugfixes, new in 0.2.2.21-alpha:
7146 - Prevent crash/heap corruption when the cbtnummodes consensus
7147 parameter is set to 0 or large values. Fixes bug 2317; bugfix
7150 o Major features, new in 0.2.2.21-alpha:
7151 - Introduce minimum/maximum values that clients will believe
7152 from the consensus. Now we'll have a better chance to avoid crashes
7153 or worse when a consensus param has a weird value.
7155 o Minor features, new in 0.2.2.21-alpha:
7156 - Make sure to disable DirPort if running as a bridge. DirPorts aren't
7157 used on bridges, and it makes bridge scanning somewhat easier.
7158 - If writing the state file to disk fails, wait up to an hour before
7159 retrying again, rather than trying again each second. Fixes bug
7160 2346; bugfix on Tor 0.1.1.3-alpha.
7161 - Make Libevent log messages get delivered to controllers later,
7162 and not from inside the Libevent log handler. This prevents unsafe
7163 reentrant Libevent calls while still letting the log messages
7165 - Detect platforms that brokenly use a signed size_t, and refuse to
7166 build there. Found and analyzed by doorss and rransom.
7167 - Fix a bunch of compile warnings revealed by mingw with gcc 4.5.
7170 o Minor bugfixes, new in 0.2.2.21-alpha:
7171 - Handle SOCKS messages longer than 128 bytes long correctly, rather
7172 than waiting forever for them to finish. Fixes bug 2330; bugfix
7173 on 0.2.0.16-alpha. Found by doorss.
7174 - Add assertions to check for overflow in arguments to
7175 base32_encode() and base32_decode(); fix a signed-unsigned
7176 comparison there too. These bugs are not actually reachable in Tor,
7177 but it's good to prevent future errors too. Found by doorss.
7178 - Correctly detect failures to create DNS requests when using Libevent
7179 versions before v2. (Before Libevent 2, we used our own evdns
7180 implementation. Its return values for Libevent's evdns_resolve_*()
7181 functions are not consistent with those from Libevent.) Fixes bug
7182 2363; bugfix on 0.2.2.6-alpha. Found by "lodger".
7184 o Documentation, new in 0.2.2.21-alpha:
7185 - Document the default socks host and port (127.0.0.1:9050) for
7189 Changes in version 0.2.1.29 - 2011-01-15
7190 Tor 0.2.1.29 continues our recent code security audit work. The main
7191 fix resolves a remote heap overflow vulnerability that can allow remote
7192 code execution. Other fixes address a variety of assert and crash bugs,
7193 most of which we think are hard to exploit remotely.
7195 o Major bugfixes (security):
7196 - Fix a heap overflow bug where an adversary could cause heap
7197 corruption. This bug probably allows remote code execution
7198 attacks. Reported by "debuger". Fixes CVE-2011-0427. Bugfix on
7200 - Prevent a denial-of-service attack by disallowing any
7201 zlib-compressed data whose compression factor is implausibly
7202 high. Fixes part of bug 2324; reported by "doorss".
7203 - Zero out a few more keys in memory before freeing them. Fixes
7204 bug 2384 and part of bug 2385. These key instances found by
7205 "cypherpunks", based on Andrew Case's report about being able
7206 to find sensitive data in Tor's memory space if you have enough
7207 permissions. Bugfix on 0.0.2pre9.
7209 o Major bugfixes (crashes):
7210 - Prevent calls to Libevent from inside Libevent log handlers.
7211 This had potential to cause a nasty set of crashes, especially
7212 if running Libevent with debug logging enabled, and running
7213 Tor with a controller watching for low-severity log messages.
7214 Bugfix on 0.1.0.2-rc. Fixes bug 2190.
7215 - Add a check for SIZE_T_MAX to tor_realloc() to try to avoid
7216 underflow errors there too. Fixes the other part of bug 2324.
7217 - Fix a bug where we would assert if we ever had a
7218 cached-descriptors.new file (or another file read directly into
7219 memory) of exactly SIZE_T_CEILING bytes. Fixes bug 2326; bugfix
7220 on 0.2.1.25. Found by doorss.
7221 - Fix some potential asserts and parsing issues with grossly
7222 malformed router caches. Fixes bug 2352; bugfix on Tor 0.2.1.27.
7225 o Minor bugfixes (other):
7226 - Fix a bug with handling misformed replies to reverse DNS lookup
7227 requests in DNSPort. Bugfix on Tor 0.2.0.1-alpha. Related to a
7228 bug reported by doorss.
7229 - Fix compilation on mingw when a pthreads compatibility library
7230 has been installed. (We don't want to use it, so we shouldn't
7231 be including pthread.h.) Fixes bug 2313; bugfix on 0.1.0.1-rc.
7232 - Fix a bug where we would declare that we had run out of virtual
7233 addresses when the address space was only half-exhausted. Bugfix
7235 - Correctly handle the case where AutomapHostsOnResolve is set but
7236 no virtual addresses are available. Fixes bug 2328; bugfix on
7237 0.1.2.1-alpha. Bug found by doorss.
7238 - Correctly handle wrapping around to when we run out of virtual
7239 address space. Found by cypherpunks, bugfix on 0.2.0.5-alpha.
7240 - The 0.2.1.28 tarball was missing src/common/OpenBSD_malloc_Linux.c
7241 because we built it with a too-old version of automake. Thus that
7242 release broke ./configure --enable-openbsd-malloc, which is popular
7243 among really fast exit relays on Linux.
7246 - Update to the January 1 2011 Maxmind GeoLite Country database.
7247 - Introduce output size checks on all of our decryption functions.
7250 - Tor does not build packages correctly with Automake 1.6 and earlier;
7251 added a check to Makefile.am to make sure that we're building with
7252 Automake 1.7 or later.
7255 Changes in version 0.2.2.20-alpha - 2010-12-17
7256 Tor 0.2.2.20-alpha does some code cleanup to reduce the risk of remotely
7257 exploitable bugs. We also fix a variety of other significant bugs,
7258 change the IP address for one of our directory authorities, and update
7259 the minimum version that Tor relays must run to join the network.
7262 - Fix a remotely exploitable bug that could be used to crash instances
7263 of Tor remotely by overflowing on the heap. Remote-code execution
7264 hasn't been confirmed, but can't be ruled out. Everyone should
7265 upgrade. Bugfix on the 0.1.1 series and later.
7266 - Fix a bug that could break accounting on 64-bit systems with large
7267 time_t values, making them hibernate for impossibly long intervals.
7268 Fixes bug 2146. Bugfix on 0.0.9pre6; fix by boboper.
7269 - Fix a logic error in directory_fetches_from_authorities() that
7270 would cause all _non_-exits refusing single-hop-like circuits
7271 to fetch from authorities, when we wanted to have _exits_ fetch
7272 from authorities. Fixes more of 2097. Bugfix on 0.2.2.16-alpha;
7274 - Fix a stream fairness bug that would cause newer streams on a given
7275 circuit to get preference when reading bytes from the origin or
7276 destination. Fixes bug 2210. Fix by Mashael AlSabah. This bug was
7277 introduced before the first Tor release, in svn revision r152.
7279 o Directory authority changes:
7280 - Change IP address and ports for gabelmoo (v3 directory authority).
7283 - Avoid crashes when AccountingMax is set on clients. Fixes bug 2235.
7284 Bugfix on 0.2.2.18-alpha. Diagnosed by boboper.
7285 - Fix an off-by-one error in calculating some controller command
7286 argument lengths. Fortunately, this mistake is harmless since
7287 the controller code does redundant NUL termination too. Found by
7288 boboper. Bugfix on 0.1.1.1-alpha.
7289 - Do not dereference NULL if a bridge fails to build its
7290 extra-info descriptor. Found by an anonymous commenter on
7291 Trac. Bugfix on 0.2.2.19-alpha.
7294 - Update to the December 1 2010 Maxmind GeoLite Country database.
7295 - Directory authorities now reject relays running any versions of
7296 Tor between 0.2.1.3-alpha and 0.2.1.18 inclusive; they have
7297 known bugs that keep RELAY_EARLY cells from working on rendezvous
7298 circuits. Followup to fix for bug 2081.
7299 - Directory authorities now reject relays running any version of Tor
7300 older than 0.2.0.26-rc. That version is the earliest that fetches
7301 current directory information correctly. Fixes bug 2156.
7302 - Report only the top 10 ports in exit-port stats in order not to
7303 exceed the maximum extra-info descriptor length of 50 KB. Implements
7307 Changes in version 0.2.1.28 - 2010-12-17
7308 Tor 0.2.1.28 does some code cleanup to reduce the risk of remotely
7309 exploitable bugs. We also took this opportunity to change the IP address
7310 for one of our directory authorities, and to update the geoip database
7314 - Fix a remotely exploitable bug that could be used to crash instances
7315 of Tor remotely by overflowing on the heap. Remote-code execution
7316 hasn't been confirmed, but can't be ruled out. Everyone should
7317 upgrade. Bugfix on the 0.1.1 series and later.
7319 o Directory authority changes:
7320 - Change IP address and ports for gabelmoo (v3 directory authority).
7323 - Update to the December 1 2010 Maxmind GeoLite Country database.
7326 Changes in version 0.2.1.27 - 2010-11-23
7327 Yet another OpenSSL security patch broke its compatibility with Tor:
7328 Tor 0.2.1.27 makes relays work with openssl 0.9.8p and 1.0.0.b. We
7329 also took this opportunity to fix several crash bugs, integrate a new
7330 directory authority, and update the bundled GeoIP database.
7333 - Resolve an incompatibility with OpenSSL 0.9.8p and OpenSSL 1.0.0b:
7334 No longer set the tlsext_host_name extension on server SSL objects;
7335 but continue to set it on client SSL objects. Our goal in setting
7336 it was to imitate a browser, not a vhosting server. Fixes bug 2204;
7337 bugfix on 0.2.1.1-alpha.
7338 - Do not log messages to the controller while shrinking buffer
7339 freelists. Doing so would sometimes make the controller connection
7340 try to allocate a buffer chunk, which would mess up the internals
7341 of the freelist and cause an assertion failure. Fixes bug 1125;
7342 fixed by Robert Ransom. Bugfix on 0.2.0.16-alpha.
7343 - Learn our external IP address when we're a relay or bridge, even if
7344 we set PublishServerDescriptor to 0. Bugfix on 0.2.0.3-alpha,
7345 where we introduced bridge relays that don't need to publish to
7346 be useful. Fixes bug 2050.
7347 - Do even more to reject (and not just ignore) annotations on
7348 router descriptors received anywhere but from the cache. Previously
7349 we would ignore such annotations at first, but cache them to disk
7350 anyway. Bugfix on 0.2.0.8-alpha. Found by piebeer.
7351 - When you're using bridges and your network goes away and your
7352 bridges get marked as down, recover when you attempt a new socks
7353 connection (if the network is back), rather than waiting up to an
7354 hour to try fetching new descriptors for your bridges. Bugfix on
7355 0.2.0.3-alpha; fixes bug 1981.
7358 - Move to the November 2010 Maxmind GeoLite country db (rather
7359 than the June 2009 ip-to-country GeoIP db) for our statistics that
7360 count how many users relays are seeing from each country. Now we'll
7361 have more accurate data, especially for many African countries.
7363 o New directory authorities:
7364 - Set up maatuska (run by Linus Nordberg) as the eighth v3 directory
7368 - Fix an assertion failure that could occur in directory caches or
7369 bridge users when using a very short voting interval on a testing
7370 network. Diagnosed by Robert Hogan. Fixes bug 1141; bugfix on
7372 - Enforce multiplicity rules when parsing annotations. Bugfix on
7373 0.2.0.8-alpha. Found by piebeer.
7374 - Allow handshaking OR connections to take a full KeepalivePeriod
7375 seconds to handshake. Previously, we would close them after
7376 IDLE_OR_CONN_TIMEOUT (180) seconds, the same timeout as if they
7377 were open. Bugfix on 0.2.1.26; fixes bug 1840. Thanks to mingw-san
7379 - When building with --enable-gcc-warnings on OpenBSD, disable
7380 warnings in system headers. This makes --enable-gcc-warnings
7381 pass on OpenBSD 4.8.
7384 - Exit nodes didn't recognize EHOSTUNREACH as a plausible error code,
7385 and so sent back END_STREAM_REASON_MISC. Clients now recognize a new
7386 stream ending reason for this case: END_STREAM_REASON_NOROUTE.
7387 Servers can start sending this code when enough clients recognize
7388 it. Bugfix on 0.1.0.1-rc; fixes part of bug 1793.
7389 - Build correctly on mingw with more recent versions of OpenSSL 0.9.8.
7390 Patch from mingw-san.
7393 - Remove the old debian/ directory from the main Tor distribution.
7394 The official Tor-for-debian git repository lives at the URL
7395 https://git.torproject.org/debian/tor.git
7396 - Stop shipping the old doc/website/ directory in the tarball. We
7397 changed the website format in late 2010, and what we shipped in
7398 0.2.1.26 really wasn't that useful anyway.
7401 Changes in version 0.2.2.19-alpha - 2010-11-22
7402 Yet another OpenSSL security patch broke its compatibility with Tor:
7403 Tor 0.2.2.19-alpha makes relays work with OpenSSL 0.9.8p and 1.0.0.b.
7406 - Resolve an incompatibility with OpenSSL 0.9.8p and OpenSSL 1.0.0b:
7407 No longer set the tlsext_host_name extension on server SSL objects;
7408 but continue to set it on client SSL objects. Our goal in setting
7409 it was to imitate a browser, not a vhosting server. Fixes bug 2204;
7410 bugfix on 0.2.1.1-alpha.
7413 - Try harder not to exceed the maximum length of 50 KB when writing
7414 statistics to extra-info descriptors. This bug was triggered by very
7415 fast relays reporting exit-port, entry, and dirreq statistics.
7416 Reported by Olaf Selke. Bugfix on 0.2.2.1-alpha. Fixes bug 2183.
7417 - Publish a router descriptor even if generating an extra-info
7418 descriptor fails. Previously we would not publish a router
7419 descriptor without an extra-info descriptor; this can cause fast
7420 exit relays collecting exit-port statistics to drop from the
7421 consensus. Bugfix on 0.1.2.9-rc; fixes bug 2195.
7424 Changes in version 0.2.2.18-alpha - 2010-11-16
7425 Tor 0.2.2.18-alpha fixes several crash bugs that have been nagging
7426 us lately, makes unpublished bridge relays able to detect their IP
7427 address, and fixes a wide variety of other bugs to get us much closer
7428 to a stable release.
7431 - Do even more to reject (and not just ignore) annotations on
7432 router descriptors received anywhere but from the cache. Previously
7433 we would ignore such annotations at first, but cache them to disk
7434 anyway. Bugfix on 0.2.0.8-alpha. Found by piebeer.
7435 - Do not log messages to the controller while shrinking buffer
7436 freelists. Doing so would sometimes make the controller connection
7437 try to allocate a buffer chunk, which would mess up the internals
7438 of the freelist and cause an assertion failure. Fixes bug 1125;
7439 fixed by Robert Ransom. Bugfix on 0.2.0.16-alpha.
7440 - Learn our external IP address when we're a relay or bridge, even if
7441 we set PublishServerDescriptor to 0. Bugfix on 0.2.0.3-alpha,
7442 where we introduced bridge relays that don't need to publish to
7443 be useful. Fixes bug 2050.
7444 - Maintain separate TLS contexts and certificates for incoming and
7445 outgoing connections in bridge relays. Previously we would use the
7446 same TLS contexts and certs for incoming and outgoing connections.
7447 Bugfix on 0.2.0.3-alpha; addresses bug 988.
7448 - Maintain separate identity keys for incoming and outgoing TLS
7449 contexts in bridge relays. Previously we would use the same
7450 identity keys for incoming and outgoing TLS contexts. Bugfix on
7451 0.2.0.3-alpha; addresses the other half of bug 988.
7452 - Avoid an assertion failure when we as an authority receive a
7453 duplicate upload of a router descriptor that we already have,
7454 but which we previously considered an obsolete descriptor.
7455 Fixes another case of bug 1776. Bugfix on 0.2.2.16-alpha.
7456 - Avoid a crash bug triggered by looking at a dangling pointer while
7457 setting the network status consensus. Found by Robert Ransom.
7458 Bugfix on 0.2.2.17-alpha. Fixes bug 2097.
7459 - Fix a logic error where servers that _didn't_ act as exits would
7460 try to keep their server lists more aggressively up to date than
7461 exits, when it was supposed to be the other way around. Bugfix
7464 o Minor bugfixes (on Tor 0.2.1.x and earlier):
7465 - When we're trying to guess whether we know our IP address as
7466 a relay, we would log various ways that we failed to guess
7467 our address, but never log that we ended up guessing it
7468 successfully. Now add a log line to help confused and anxious
7469 relay operators. Bugfix on 0.1.2.1-alpha; fixes bug 1534.
7470 - Bring the logic that gathers routerinfos and assesses the
7471 acceptability of circuits into line. This prevents a Tor OP from
7472 getting locked in a cycle of choosing its local OR as an exit for a
7473 path (due to a .exit request) and then rejecting the circuit because
7474 its OR is not listed yet. It also prevents Tor clients from using an
7475 OR running in the same instance as an exit (due to a .exit request)
7476 if the OR does not meet the same requirements expected of an OR
7477 running elsewhere. Fixes bug 1859; bugfix on 0.1.0.1-rc.
7478 - Correctly describe errors that occur when generating a TLS object.
7479 Previously we would attribute them to a failure while generating a
7480 TLS context. Patch by Robert Ransom. Bugfix on 0.1.0.4-rc; fixes
7482 - Enforce multiplicity rules when parsing annotations. Bugfix on
7483 0.2.0.8-alpha. Found by piebeer.
7484 - Fix warnings that newer versions of autoconf produced during
7485 ./autogen.sh. These warnings appear to be harmless in our case,
7486 but they were extremely verbose. Fixes bug 2020.
7488 o Minor bugfixes (on Tor 0.2.2.x):
7489 - Enable protection of small arrays whenever we build with gcc
7490 hardening features, not only when also building with warnings
7491 enabled. Fixes bug 2031; bugfix on 0.2.2.14-alpha. Reported by keb.
7494 - Make hidden services work better in private Tor networks by not
7495 requiring any uptime to join the hidden service descriptor
7496 DHT. Implements ticket 2088.
7497 - Rate-limit the "your application is giving Tor only an IP address"
7498 warning. Addresses bug 2000; bugfix on 0.0.8pre2.
7499 - When AllowSingleHopExits is set, print a warning to explain to the
7500 relay operator why most clients are avoiding her relay.
7501 - Update to the November 1 2010 Maxmind GeoLite Country database.
7503 o Code simplifications and refactoring:
7504 - When we fixed bug 1038 we had to put in a restriction not to send
7505 RELAY_EARLY cells on rend circuits. This was necessary as long
7506 as relays using Tor 0.2.1.3-alpha through 0.2.1.18-alpha were
7507 active. Now remove this obsolete check. Resolves bug 2081.
7508 - Some options used different conventions for uppercasing of acronyms
7509 when comparing manpage and source. Fix those in favor of the
7510 manpage, as it makes sense to capitalize acronyms.
7511 - Remove the torrc.complete file. It hasn't been kept up to date
7512 and users will have better luck checking out the manpage.
7513 - Remove the obsolete "NoPublish" option; it has been flagged
7514 as obsolete and has produced a warning since 0.1.1.18-rc.
7515 - Remove everything related to building the expert bundle for OS X.
7516 It has confused many users, doesn't work right on OS X 10.6,
7517 and is hard to get rid of once installed. Resolves bug 1274.
7520 Changes in version 0.2.2.17-alpha - 2010-09-30
7521 Tor 0.2.2.17-alpha introduces a feature to make it harder for clients
7522 to use one-hop circuits (which can put the exit relays at higher risk,
7523 plus unbalance the network); fixes a big bug in bandwidth accounting
7524 for relays that want to limit their monthly bandwidth use; fixes a
7525 big pile of bugs in how clients tolerate temporary network failure;
7526 and makes our adaptive circuit build timeout feature (which improves
7527 client performance if your network is fast while not breaking things
7528 if your network is slow) better handle bad networks.
7531 - Exit relays now try harder to block exit attempts from unknown
7532 relays, to make it harder for people to use them as one-hop proxies
7533 a la tortunnel. Controlled by the refuseunknownexits consensus
7534 parameter (currently enabled), or you can override it on your
7535 relay with the RefuseUnknownExits torrc option. Resolves bug 1751.
7537 o Major bugfixes (0.2.1.x and earlier):
7538 - Fix a bug in bandwidth accounting that could make us use twice
7539 the intended bandwidth when our interval start changes due to
7540 daylight saving time. Now we tolerate skew in stored vs computed
7541 interval starts: if the start of the period changes by no more than
7542 50% of the period's duration, we remember bytes that we transferred
7543 in the old period. Fixes bug 1511; bugfix on 0.0.9pre5.
7544 - Always search the Windows system directory for system DLLs, and
7545 nowhere else. Bugfix on 0.1.1.23; fixes bug 1954.
7546 - When you're using bridges and your network goes away and your
7547 bridges get marked as down, recover when you attempt a new socks
7548 connection (if the network is back), rather than waiting up to an
7549 hour to try fetching new descriptors for your bridges. Bugfix on
7550 0.2.0.3-alpha; fixes bug 1981.
7552 o Major bugfixes (on 0.2.2.x):
7553 - Fix compilation on Windows. Bugfix on 0.2.2.16-alpha; related to
7555 - Fix a segfault that could happen when operating a bridge relay with
7556 no GeoIP database set. Fixes bug 1964; bugfix on 0.2.2.15-alpha.
7557 - The consensus bandwidth-weights (used by clients to choose fast
7558 relays) entered an unexpected edge case in September where
7559 Exits were much scarcer than Guards, resulting in bad weight
7560 recommendations. Now we compute them using new constraints that
7561 should succeed in all cases. Also alter directory authorities to
7562 not include the bandwidth-weights line if they fail to produce
7563 valid values. Fixes bug 1952; bugfix on 0.2.2.10-alpha.
7564 - When weighting bridges during path selection, we used to trust
7565 the bandwidths they provided in their descriptor, only capping them
7566 at 10MB/s. This turned out to be problematic for two reasons:
7567 Bridges could claim to handle a lot more traffic then they
7568 actually would, thus making more clients pick them and have a
7569 pretty effective DoS attack. The other issue is that new bridges
7570 that might not have a good estimate for their bw capacity yet
7571 would not get used at all unless no other bridges are available
7572 to a client. Fixes bug 1912; bugfix on 0.2.2.7-alpha.
7574 o Major bugfixes (on the circuit build timeout feature, 0.2.2.x):
7575 - Ignore cannibalized circuits when recording circuit build times.
7576 This should provide for a minor performance improvement for hidden
7577 service users using 0.2.2.14-alpha, and should remove two spurious
7578 notice log messages. Bugfix on 0.2.2.14-alpha; fixes bug 1740.
7579 - Simplify the logic that causes us to decide if the network is
7580 unavailable for purposes of recording circuit build times. If we
7581 receive no cells whatsoever for the entire duration of a circuit's
7582 full measured lifetime, the network is probably down. Also ignore
7583 one-hop directory fetching circuit timeouts when calculating our
7584 circuit build times. These changes should hopefully reduce the
7585 cases where we see ridiculous circuit build timeouts for people
7586 with spotty wireless connections. Fixes part of bug 1772; bugfix
7588 - Prevent the circuit build timeout from becoming larger than
7589 the maximum build time we have ever seen. Also, prevent the time
7590 period for measurement circuits from becoming larger than twice that
7591 value. Fixes the other part of bug 1772; bugfix on 0.2.2.2-alpha.
7594 - When we run out of directory information such that we can't build
7595 circuits, but then get enough that we can build circuits, log when
7596 we actually construct a circuit, so the user has a better chance of
7597 knowing what's going on. Fixes bug 1362.
7598 - Be more generous with how much bandwidth we'd use up (with
7599 accounting enabled) before entering "soft hibernation". Previously,
7600 we'd refuse new connections and circuits once we'd used up 95% of
7601 our allotment. Now, we use up 95% of our allotment, AND make sure
7602 that we have no more than 500MB (or 3 hours of expected traffic,
7603 whichever is lower) remaining before we enter soft hibernation.
7604 - If we've configured EntryNodes and our network goes away and/or all
7605 our entrynodes get marked down, optimistically retry them all when
7606 a new socks application request appears. Fixes bug 1882.
7607 - Add some more defensive programming for architectures that can't
7608 handle unaligned integer accesses. We don't know of any actual bugs
7609 right now, but that's the best time to fix them. Fixes bug 1943.
7610 - Support line continuations in the torrc config file. If a line
7611 ends with a single backslash character, the newline is ignored, and
7612 the configuration value is treated as continuing on the next line.
7615 o Minor bugfixes (on 0.2.1.x and earlier):
7616 - For bandwidth accounting, calculate our expected bandwidth rate
7617 based on the time during which we were active and not in
7618 soft-hibernation during the last interval. Previously, we were
7619 also considering the time spent in soft-hibernation. If this
7620 was a long time, we would wind up underestimating our bandwidth
7621 by a lot, and skewing our wakeup time towards the start of the
7622 accounting interval. Fixes bug 1789. Bugfix on 0.0.9pre5.
7624 o Minor bugfixes (on 0.2.2.x):
7625 - Resume generating CIRC FAILED REASON=TIMEOUT control port messages,
7626 which were disabled by the circuit build timeout changes in
7627 0.2.2.14-alpha. Bugfix on 0.2.2.14-alpha; fixes bug 1739.
7628 - Make sure we don't warn about missing bandwidth weights when
7629 choosing bridges or other relays not in the consensus. Bugfix on
7630 0.2.2.10-alpha; fixes bug 1805.
7631 - In our logs, do not double-report signatures from unrecognized
7632 authorities both as "from unknown authority" and "not
7633 present". Fixes bug 1956, bugfix on 0.2.2.16-alpha.
7636 Changes in version 0.2.2.16-alpha - 2010-09-17
7637 Tor 0.2.2.16-alpha fixes a variety of old stream fairness bugs (most
7638 evident at exit relays), and also continues to resolve all the little
7639 bugs that have been filling up trac lately.
7641 o Major bugfixes (stream-level fairness):
7642 - When receiving a circuit-level SENDME for a blocked circuit, try
7643 to package cells fairly from all the streams that had previously
7644 been blocked on that circuit. Previously, we had started with the
7645 oldest stream, and allowed each stream to potentially exhaust
7646 the circuit's package window. This gave older streams on any
7647 given circuit priority over newer ones. Fixes bug 1937. Detected
7648 originally by Camilo Viecco. This bug was introduced before the
7649 first Tor release, in svn commit r152: it is the new winner of
7650 the longest-lived bug prize.
7651 - When the exit relay got a circuit-level sendme cell, it started
7652 reading on the exit streams, even if had 500 cells queued in the
7653 circuit queue already, so the circuit queue just grew and grew in
7654 some cases. We fix this by not re-enabling reading on receipt of a
7655 sendme cell when the cell queue is blocked. Fixes bug 1653. Bugfix
7656 on 0.2.0.1-alpha. Detected by Mashael AlSabah. Original patch by
7658 - Newly created streams were allowed to read cells onto circuits,
7659 even if the circuit's cell queue was blocked and waiting to drain.
7660 This created potential unfairness, as older streams would be
7661 blocked, but newer streams would gladly fill the queue completely.
7662 We add code to detect this situation and prevent any stream from
7663 getting more than one free cell. Bugfix on 0.2.0.1-alpha. Partially
7667 - Update to the September 1 2010 Maxmind GeoLite Country database.
7668 - Warn when CookieAuthFileGroupReadable is set but CookieAuthFile is
7669 not. This would lead to a cookie that is still not group readable.
7670 Closes bug 1843. Suggested by katmagic.
7671 - When logging a rate-limited warning, we now mention how many messages
7672 got suppressed since the last warning.
7673 - Add new "perconnbwrate" and "perconnbwburst" consensus params to
7674 do individual connection-level rate limiting of clients. The torrc
7675 config options with the same names trump the consensus params, if
7676 both are present. Replaces the old "bwconnrate" and "bwconnburst"
7677 consensus params which were broken from 0.2.2.7-alpha through
7678 0.2.2.14-alpha. Closes bug 1947.
7679 - When a router changes IP address or port, authorities now launch
7680 a new reachability test for it. Implements ticket 1899.
7681 - Make the formerly ugly "2 unknown, 7 missing key, 0 good, 0 bad,
7682 2 no signature, 4 required" messages about consensus signatures
7683 easier to read, and make sure they get logged at the same severity
7684 as the messages explaining which keys are which. Fixes bug 1290.
7685 - Don't warn when we have a consensus that we can't verify because
7686 of missing certificates, unless those certificates are ones
7687 that we have been trying and failing to download. Fixes bug 1145.
7688 - If you configure your bridge with a known identity fingerprint,
7689 and the bridge authority is unreachable (as it is in at least
7690 one country now), fall back to directly requesting the descriptor
7691 from the bridge. Finishes the feature started in 0.2.0.10-alpha;
7693 - When building with --enable-gcc-warnings on OpenBSD, disable
7694 warnings in system headers. This makes --enable-gcc-warnings
7695 pass on OpenBSD 4.8.
7697 o Minor bugfixes (on 0.2.1.x and earlier):
7698 - Authorities will now attempt to download consensuses if their
7699 own efforts to make a live consensus have failed. This change
7700 means authorities that restart will fetch a valid consensus, and
7701 it means authorities that didn't agree with the current consensus
7702 will still fetch and serve it if it has enough signatures. Bugfix
7703 on 0.2.0.9-alpha; fixes bug 1300.
7704 - Ensure DNS requests launched by "RESOLVE" commands from the
7705 controller respect the __LeaveStreamsUnattached setconf options. The
7706 same goes for requests launched via DNSPort or transparent
7707 proxying. Bugfix on 0.2.0.1-alpha; fixes bug 1525.
7708 - Allow handshaking OR connections to take a full KeepalivePeriod
7709 seconds to handshake. Previously, we would close them after
7710 IDLE_OR_CONN_TIMEOUT (180) seconds, the same timeout as if they
7711 were open. Bugfix on 0.2.1.26; fixes bug 1840. Thanks to mingw-san
7713 - Rate-limit "Failed to hand off onionskin" warnings.
7714 - Never relay a cell for a circuit we have already destroyed.
7715 Between marking a circuit as closeable and finally closing it,
7716 it may have been possible for a few queued cells to get relayed,
7717 even though they would have been immediately dropped by the next
7718 OR in the circuit. Fixes bug 1184; bugfix on 0.2.0.1-alpha.
7719 - Never queue a cell for a circuit that's already been marked
7721 - Never vote for a server as "Running" if we have a descriptor for
7722 it claiming to be hibernating, and that descriptor was published
7723 more recently than our last contact with the server. Bugfix on
7724 0.2.0.3-alpha; fixes bug 911.
7725 - Squash a compile warning on OpenBSD. Reported by Tas; fixes
7728 o Minor bugfixes (on 0.2.2.x):
7729 - Fix a regression introduced in 0.2.2.7-alpha that marked relays
7730 down if a directory fetch fails and you've configured either
7731 bridges or EntryNodes. The intent was to mark the relay as down
7732 _unless_ you're using bridges or EntryNodes, since if you are
7733 then you could quickly run out of entry points.
7734 - Fix the Windows directory-listing code. A bug introduced in
7735 0.2.2.14-alpha could make Windows directory servers forget to load
7736 some of their cached v2 networkstatus files.
7737 - Really allow clients to use relays as bridges. Fixes bug 1776;
7738 bugfix on 0.2.2.15-alpha.
7739 - Demote a warn to info that happens when the CellStatistics option
7740 was just enabled. Bugfix on 0.2.2.15-alpha; fixes bug 1921.
7741 Reported by Moritz Bartl.
7742 - On Windows, build correctly either with or without Unicode support.
7743 This is necessary so that Tor can support fringe platforms like
7744 Windows 98 (which has no Unicode), or Windows CE (which has no
7745 non-Unicode). Bugfix on 0.2.2.14-alpha; fixes bug 1797.
7748 - Add a unit test for cross-platform directory-listing code.
7751 Changes in version 0.2.2.15-alpha - 2010-08-18
7752 Tor 0.2.2.15-alpha fixes a big bug in hidden service availability,
7753 fixes a variety of other bugs that were preventing performance
7754 experiments from moving forward, fixes several bothersome memory leaks,
7755 and generally closes a lot of smaller bugs that have been filling up
7759 - Stop assigning the HSDir flag to relays that disable their
7760 DirPort (and thus will refuse to answer directory requests). This
7761 fix should dramatically improve the reachability of hidden services:
7762 hidden services and hidden service clients pick six HSDir relays
7763 to store and retrieve the hidden service descriptor, and currently
7764 about half of the HSDir relays will refuse to work. Bugfix on
7765 0.2.0.10-alpha; fixes part of bug 1693.
7766 - The PerConnBWRate and Burst config options, along with the
7767 bwconnrate and bwconnburst consensus params, initialized each conn's
7768 token bucket values only when the connection is established. Now we
7769 update them if the config options change, and update them every time
7770 we get a new consensus. Otherwise we can encounter an ugly edge
7771 case where we initialize an OR conn to client-level bandwidth,
7772 but then later the relay joins the consensus and we leave it
7773 throttled. Bugfix on 0.2.2.7-alpha; fixes bug 1830.
7774 - Fix a regression that caused Tor to rebind its ports if it receives
7775 SIGHUP while hibernating. Bugfix in 0.1.1.6-alpha; closes bug 919.
7778 - Lower the maximum weighted-fractional-uptime cutoff to 98%. This
7779 should give us approximately 40-50% more Guard-flagged nodes,
7780 improving the anonymity the Tor network can provide and also
7781 decreasing the dropoff in throughput that relays experience when
7782 they first get the Guard flag.
7783 - Allow enabling or disabling the *Statistics config options while
7787 - Update to the August 1 2010 Maxmind GeoLite Country database.
7788 - Have the controller interface give a more useful message than
7789 "Internal Error" in response to failed GETINFO requests.
7790 - Warn when the same option is provided more than once in a torrc
7791 file, on the command line, or in a single SETCONF statement, and
7792 the option is one that only accepts a single line. Closes bug 1384.
7793 - Build correctly on mingw with more recent versions of OpenSSL 0.9.8.
7794 Patch from mingw-san.
7795 - Add support for the country code "{??}" in torrc options like
7796 ExcludeNodes, to indicate all routers of unknown country. Closes
7798 - Relays report the number of bytes spent on answering directory
7799 requests in extra-info descriptors similar to {read,write}-history.
7800 Implements enhancement 1790.
7802 o Minor bugfixes (on 0.2.1.x and earlier):
7803 - Complain if PublishServerDescriptor is given multiple arguments that
7804 include 0 or 1. This configuration will be rejected in the future.
7805 Bugfix on 0.2.0.1-alpha; closes bug 1107.
7806 - Disallow BridgeRelay 1 and ORPort 0 at once in the configuration.
7807 Bugfix on 0.2.0.13-alpha; closes bug 928.
7808 - Change "Application request when we're believed to be offline."
7809 notice to "Application request when we haven't used client
7810 functionality lately.", to clarify that it's not an error. Bugfix
7811 on 0.0.9.3; fixes bug 1222.
7812 - Fix a bug in the controller interface where "GETINFO ns/asdaskljkl"
7813 would return "551 Internal error" rather than "552 Unrecognized key
7814 ns/asdaskljkl". Bugfix on 0.1.2.3-alpha.
7815 - Users can't configure a regular relay to be their bridge. It didn't
7816 work because when Tor fetched the bridge descriptor, it found
7817 that it already had it, and didn't realize that the purpose of the
7818 descriptor had changed. Now we replace routers with a purpose other
7819 than bridge with bridge descriptors when fetching them. Bugfix on
7820 0.1.1.9-alpha. Bug 1776 not yet fixed because now we immediately
7821 refetch the descriptor with router purpose 'general', disabling
7823 - Fix a rare bug in rend_fn unit tests: we would fail a test when
7824 a randomly generated port is 0. Diagnosed by Matt Edman. Bugfix
7825 on 0.2.0.10-alpha; fixes bug 1808.
7826 - Exit nodes didn't recognize EHOSTUNREACH as a plausible error code,
7827 and so sent back END_STREAM_REASON_MISC. Clients now recognize a new
7828 stream ending reason for this case: END_STREAM_REASON_NOROUTE.
7829 Servers can start sending this code when enough clients recognize
7830 it. Also update the spec to reflect this new reason. Bugfix on
7831 0.1.0.1-rc; fixes part of bug 1793.
7832 - Delay geoip stats collection by bridges for 6 hours, not 2 hours,
7833 when we switch from being a public relay to a bridge. Otherwise
7834 there will still be clients that see the relay in their consensus,
7835 and the stats will end up wrong. Bugfix on 0.2.1.15-rc; fixes bug
7837 - Instead of giving an assertion failure on an internal mismatch
7838 on estimated freelist size, just log a BUG warning and try later.
7839 Mitigates but does not fix bug 1125.
7840 - Fix an assertion failure that could occur in caches or bridge users
7841 when using a very short voting interval on a testing network.
7842 Diagnosed by Robert Hogan. Fixes bug 1141; bugfix on 0.2.0.8-alpha.
7844 o Minor bugfixes (on 0.2.2.x):
7845 - Alter directory authorities to always consider Exit-flagged nodes
7846 as potential Guard nodes in their votes. The actual decision to
7847 use Exits as Guards is done in the consensus bandwidth weights.
7848 Fixes bug 1294; bugfix on 0.2.2.10-alpha.
7849 - When the controller is reporting the purpose of circuits that
7850 didn't finish building before the circuit build timeout, it was
7851 printing UNKNOWN_13. Now print EXPIRED. Bugfix on 0.2.2.14-alpha.
7852 - Our libevent version parsing code couldn't handle versions like
7853 1.4.14b-stable and incorrectly warned the user about using an
7854 old and broken version of libevent. Treat 1.4.14b-stable like
7855 1.4.14-stable when parsing the version. Fixes bug 1731; bugfix
7857 - Don't use substitution references like $(VAR:MOD) when
7858 $(asciidoc_files) is empty -- make(1) on NetBSD transforms
7859 '$(:x)' to 'x' rather than the empty string. This bites us in
7860 doc/ when configured with --disable-asciidoc. Bugfix on
7861 0.2.2.9-alpha; fixes bug 1773.
7862 - Remove a spurious hidden service server-side log notice about
7863 "Ancient non-dirty circuits". Bugfix on 0.2.2.14-alpha; fixes
7865 - Fix compilation with --with-dmalloc set. Bugfix on 0.2.2.6-alpha;
7867 - Correctly report written bytes on linked connections. Found while
7868 implementing 1790. Bugfix on 0.2.2.4-alpha.
7869 - Fix three memory leaks: one in circuit_build_times_parse_state(),
7870 one in dirvote_add_signatures_to_pending_consensus(), and one every
7871 time we parse a v3 network consensus. Bugfixes on 0.2.2.14-alpha,
7872 0.2.2.6-alpha, and 0.2.2.10-alpha respectively; fixes bug 1831.
7874 o Code simplifications and refactoring:
7875 - Take a first step towards making or.h smaller by splitting out
7876 function definitions for all source files in src/or/. Leave
7877 structures and defines in or.h for now.
7878 - Remove a bunch of unused function declarations as well as a block of
7879 #if 0'd code from the unit tests. Closes bug 1824.
7880 - New unit tests for exit-port history statistics; refactored exit
7881 statistics code to be more easily tested.
7882 - Remove the old debian/ directory from the main Tor distribution.
7883 The official Tor-for-debian git repository lives at the URL
7884 https://git.torproject.org/debian/tor.git
7887 Changes in version 0.2.2.14-alpha - 2010-07-12
7888 Tor 0.2.2.14-alpha greatly improves client-side handling of
7889 circuit build timeouts, which are used to estimate speed and improve
7890 performance. We also move to a much better GeoIP database, port Tor to
7891 Windows CE, introduce new compile flags that improve code security,
7892 add an eighth v3 directory authority, and address a lot of more
7896 - Tor directory authorities no longer crash when started with a
7897 cached-microdesc-consensus file in their data directory. Bugfix
7898 on 0.2.2.6-alpha; fixes bug 1532.
7899 - Treat an unset $HOME like an empty $HOME rather than triggering an
7900 assert. Bugfix on 0.0.8pre1; fixes bug 1522.
7901 - Ignore negative and large circuit build timeout values that can
7902 happen during a suspend or hibernate. These values caused various
7903 asserts to fire. Bugfix on 0.2.2.2-alpha; fixes bug 1245.
7904 - Alter calculation of Pareto distribution parameter 'Xm' for
7905 Circuit Build Timeout learning to use the weighted average of the
7906 top N=3 modes (because we have three entry guards). Considering
7907 multiple modes should improve the timeout calculation in some cases,
7908 and prevent extremely high timeout values. Bugfix on 0.2.2.2-alpha;
7910 - Alter calculation of Pareto distribution parameter 'Alpha' to use a
7911 right censored distribution model. This approach improves over the
7912 synthetic timeout generation approach that was producing insanely
7913 high timeout values. Now we calculate build timeouts using truncated
7914 times. Bugfix on 0.2.2.2-alpha; fixes bugs 1245 and 1335.
7915 - Do not close circuits that are under construction when they reach
7916 the circuit build timeout. Instead, leave them building (but do not
7917 use them) for up until the time corresponding to the 95th percentile
7918 on the Pareto CDF or 60 seconds, whichever is greater. This is done
7919 to provide better data for the new Pareto model. This percentile
7920 can be controlled by the consensus.
7923 - Move to the June 2010 Maxmind GeoLite country db (rather than the
7924 June 2009 ip-to-country GeoIP db) for our statistics that count
7925 how many users relays are seeing from each country. Now we have
7926 more accurate data for many African countries.
7927 - Port Tor to build and run correctly on Windows CE systems, using
7928 the wcecompat library. Contributed by Valerio Lupi.
7929 - New "--enable-gcc-hardening" ./configure flag (off by default)
7930 to turn on gcc compile time hardening options. It ensures
7931 that signed ints have defined behavior (-fwrapv), enables
7932 -D_FORTIFY_SOURCE=2 (requiring -O2), adds stack smashing protection
7933 with canaries (-fstack-protector-all), turns on ASLR protection if
7934 supported by the kernel (-fPIE, -pie), and adds additional security
7935 related warnings. Verified to work on Mac OS X and Debian Lenny.
7936 - New "--enable-linker-hardening" ./configure flag (off by default)
7937 to turn on ELF specific hardening features (relro, now). This does
7938 not work with Mac OS X or any other non-ELF binary format.
7940 o New directory authorities:
7941 - Set up maatuska (run by Linus Nordberg) as the eighth v3 directory
7945 - New config option "WarnUnsafeSocks 0" disables the warning that
7946 occurs whenever Tor receives a socks handshake using a version of
7947 the socks protocol that can only provide an IP address (rather
7948 than a hostname). Setups that do DNS locally over Tor are fine,
7949 and we shouldn't spam the logs in that case.
7950 - Convert the HACKING file to asciidoc, and add a few new sections
7951 to it, explaining how we use Git, how we make changelogs, and
7952 what should go in a patch.
7953 - Add a TIMEOUT_RATE keyword to the BUILDTIMEOUT_SET control port
7954 event, to give information on the current rate of circuit timeouts
7955 over our stored history.
7956 - Add ability to disable circuit build time learning via consensus
7957 parameter and via a LearnCircuitBuildTimeout config option. Also
7958 automatically disable circuit build time calculation if we are
7959 either a AuthoritativeDirectory, or if we fail to write our state
7960 file. Fixes bug 1296.
7961 - More gracefully handle corrupt state files, removing asserts
7962 in favor of saving a backup and resetting state.
7963 - Rename the "log.h" header to "torlog.h" so as to conflict with fewer
7967 - Build correctly on OSX with zlib 1.2.4 and higher with all warnings
7969 - When a2x fails, mention that the user could disable manpages instead
7970 of trying to fix their asciidoc installation.
7971 - Where available, use Libevent 2.0's periodic timers so that our
7972 once-per-second cleanup code gets called even more closely to
7973 once per second than it would otherwise. Fixes bug 943.
7974 - If you run a bridge that listens on multiple IP addresses, and
7975 some user configures a bridge address that uses a different IP
7976 address than your bridge writes in its router descriptor, and the
7977 user doesn't specify an identity key, their Tor would discard the
7978 descriptor because "it isn't one of our configured bridges", and
7979 fail to bootstrap. Now believe the descriptor and bootstrap anyway.
7980 Bugfix on 0.2.0.3-alpha.
7981 - If OpenSSL fails to make a duplicate of a private or public key, log
7982 an error message and try to exit cleanly. May help with debugging
7983 if bug 1209 ever remanifests.
7984 - Save a couple bytes in memory allocation every time we escape
7985 certain characters in a string. Patch from Florian Zumbiehl.
7986 - Make it explicit that we don't cannibalize one-hop circuits. This
7987 happens in the wild, but doesn't turn out to be a problem because
7988 we fortunately don't use those circuits. Many thanks to outofwords
7989 for the initial analysis and to swissknife who confirmed that
7990 two-hop circuits are actually created.
7991 - Make directory mirrors report non-zero dirreq-v[23]-shares again.
7992 Fixes bug 1564; bugfix on 0.2.2.9-alpha.
7993 - Eliminate a case where a circuit build time warning was displayed
7994 after network connectivity resumed. Bugfix on 0.2.2.2-alpha.
7997 Changes in version 0.2.1.26 - 2010-05-02
7998 Tor 0.2.1.26 addresses the recent connection and memory overload
7999 problems we've been seeing on relays, especially relays with their
8000 DirPort open. If your relay has been crashing, or you turned it off
8001 because it used too many resources, give this release a try.
8003 This release also fixes yet another instance of broken OpenSSL libraries
8004 that was causing some relays to drop out of the consensus.
8007 - Teach relays to defend themselves from connection overload. Relays
8008 now close idle circuits early if it looks like they were intended
8009 for directory fetches. Relays are also more aggressive about closing
8010 TLS connections that have no circuits on them. Such circuits are
8011 unlikely to be re-used, and tens of thousands of them were piling
8012 up at the fast relays, causing the relays to run out of sockets
8013 and memory. Bugfix on 0.2.0.22-rc (where clients started tunneling
8014 their directory fetches over TLS).
8015 - Fix SSL renegotiation behavior on OpenSSL versions like on Centos
8016 that claim to be earlier than 0.9.8m, but which have in reality
8017 backported huge swaths of 0.9.8m or 0.9.8n renegotiation
8018 behavior. Possible fix for some cases of bug 1346.
8019 - Directory mirrors were fetching relay descriptors only from v2
8020 directory authorities, rather than v3 authorities like they should.
8021 Only 2 v2 authorities remain (compared to 7 v3 authorities), leading
8022 to a serious bottleneck. Bugfix on 0.2.0.9-alpha. Fixes bug 1324.
8025 - Finally get rid of the deprecated and now harmful notion of "clique
8026 mode", where directory authorities maintain TLS connections to
8030 - In the util/threads test, no longer free the test_mutex before all
8031 worker threads have finished. Bugfix on 0.2.1.6-alpha.
8032 - The master thread could starve the worker threads quite badly on
8033 certain systems, causing them to run only partially in the allowed
8034 window. This resulted in test failures. Now the master thread sleeps
8035 occasionally for a few microseconds while the two worker-threads
8036 compete for the mutex. Bugfix on 0.2.0.1-alpha.
8039 Changes in version 0.2.2.13-alpha - 2010-04-24
8040 Tor 0.2.2.13-alpha addresses the recent connection and memory overload
8041 problems we've been seeing on relays, especially relays with their
8042 DirPort open. If your relay has been crashing, or you turned it off
8043 because it used too many resources, give this release a try.
8046 - Teach relays to defend themselves from connection overload. Relays
8047 now close idle circuits early if it looks like they were intended
8048 for directory fetches. Relays are also more aggressive about closing
8049 TLS connections that have no circuits on them. Such circuits are
8050 unlikely to be re-used, and tens of thousands of them were piling
8051 up at the fast relays, causing the relays to run out of sockets
8052 and memory. Bugfix on 0.2.0.22-rc (where clients started tunneling
8053 their directory fetches over TLS).
8056 - Finally get rid of the deprecated and now harmful notion of "clique
8057 mode", where directory authorities maintain TLS connections to
8059 - Directory authorities now do an immediate reachability check as soon
8060 as they hear about a new relay. This change should slightly reduce
8061 the time between setting up a relay and getting listed as running
8062 in the consensus. It should also improve the time between setting
8063 up a bridge and seeing use by bridge users.
8064 - Directory authorities no longer launch a TLS connection to every
8065 relay as they startup. Now that we have 2k+ descriptors cached,
8066 the resulting network hiccup is becoming a burden. Besides,
8067 authorities already avoid voting about Running for the first half
8068 hour of their uptime.
8071 Changes in version 0.2.2.12-alpha - 2010-04-20
8072 Tor 0.2.2.12-alpha fixes a critical bug in how directory authorities
8073 handle and vote on descriptors. It was causing relays to drop out of
8077 - Many relays have been falling out of the consensus lately because
8078 not enough authorities know about their descriptor for them to get
8079 a majority of votes. When we deprecated the v2 directory protocol,
8080 we got rid of the only way that v3 authorities can hear from each
8081 other about other descriptors. Now authorities examine every v3
8082 vote for new descriptors, and fetch them from that authority. Bugfix
8084 - Fix two typos in tor_vasprintf() that broke the compile on Windows,
8085 and a warning in or.h related to bandwidth_weight_rule_t that
8086 prevented clean compile on OS X. Fixes bug 1363; bugfix on
8088 - Fix a segfault on relays when DirReqStatistics is enabled
8089 and 24 hours pass. Bug found by keb. Fixes bug 1365; bugfix on
8093 - Demote a confusing TLS warning that relay operators might get when
8094 someone tries to talk to their OrPort. It is neither the operator's
8095 fault nor can they do anything about it. Fixes bug 1364; bugfix
8099 Changes in version 0.2.2.11-alpha - 2010-04-15
8100 Tor 0.2.2.11-alpha fixes yet another instance of broken OpenSSL
8101 libraries that was causing some relays to drop out of the consensus.
8104 - Directory mirrors were fetching relay descriptors only from v2
8105 directory authorities, rather than v3 authorities like they should.
8106 Only 2 v2 authorities remain (compared to 7 v3 authorities), leading
8107 to a serious bottleneck. Bugfix on 0.2.0.9-alpha. Fixes bug 1324.
8108 - Fix a parsing error that made every possible value of
8109 CircPriorityHalflifeMsec get treated as "1 msec". Bugfix
8110 on 0.2.2.7-alpha. Rename CircPriorityHalflifeMsec to
8111 CircuitPriorityHalflifeMsec, so authorities can tell newer relays
8112 about the option without breaking older ones.
8113 - Fix SSL renegotiation behavior on OpenSSL versions like on Centos
8114 that claim to be earlier than 0.9.8m, but which have in reality
8115 backported huge swaths of 0.9.8m or 0.9.8n renegotiation
8116 behavior. Possible fix for some cases of bug 1346.
8119 - Experiment with a more aggressive approach to preventing clients
8120 from making one-hop exit streams. Exit relays who want to try it
8121 out can set "RefuseUnknownExits 1" in their torrc, and then look
8122 for "Attempt by %s to open a stream" log messages. Let us know
8124 - Add support for statically linking zlib by specifying
8125 --enable-static-zlib, to go with our support for statically linking
8126 openssl and libevent. Resolves bug 1358.
8129 - Fix a segfault that happens whenever a Tor client that is using
8130 libevent2's bufferevents gets a hup signal. Bugfix on 0.2.2.5-alpha;
8132 - When we cleaned up the contrib/tor-exit-notice.html file, we left
8133 out the first line. Fixes bug 1295.
8134 - When building the manpage from a tarball, we required asciidoc, but
8135 the asciidoc -> roff/html conversion was already done for the
8136 tarball. Make 'make' complain only when we need asciidoc (either
8137 because we're compiling directly from git, or because we altered
8138 the asciidoc manpage in the tarball). Bugfix on 0.2.2.9-alpha.
8139 - When none of the directory authorities vote on any params, Tor
8140 segfaulted when trying to make the consensus from the votes. We
8141 didn't trigger the bug in practice, because authorities do include
8142 params in their votes. Bugfix on 0.2.2.10-alpha; fixes bug 1322.
8145 - In the util/threads test, no longer free the test_mutex before all
8146 worker threads have finished. Bugfix on 0.2.1.6-alpha.
8147 - The master thread could starve the worker threads quite badly on
8148 certain systems, causing them to run only partially in the allowed
8149 window. This resulted in test failures. Now the master thread sleeps
8150 occasionally for a few microseconds while the two worker-threads
8151 compete for the mutex. Bugfix on 0.2.0.1-alpha.
8154 Changes in version 0.2.2.10-alpha - 2010-03-07
8155 Tor 0.2.2.10-alpha fixes a regression introduced in 0.2.2.9-alpha that
8156 could prevent relays from guessing their IP address correctly. It also
8157 starts the groundwork for another client-side performance boost, since
8158 currently we're not making efficient use of relays that have both the
8159 Guard flag and the Exit flag.
8162 - Fix a regression from our patch for bug 1244 that caused relays
8163 to guess their IP address incorrectly if they didn't set Address
8164 in their torrc and/or their address fails to resolve. Bugfix on
8165 0.2.2.9-alpha; fixes bug 1269.
8167 o Major features (performance):
8168 - Directory authorities now compute consensus weightings that instruct
8169 clients how to weight relays flagged as Guard, Exit, Guard+Exit,
8170 and no flag. Clients that use these weightings will distribute
8171 network load more evenly across these different relay types. The
8172 weightings are in the consensus so we can change them globally in
8173 the future. Extra thanks to "outofwords" for finding some nasty
8174 security bugs in the first implementation of this feature.
8176 o Minor features (performance):
8177 - Always perform router selections using weighted relay bandwidth,
8178 even if we don't need a high capacity circuit at the time. Non-fast
8179 circuits now only differ from fast ones in that they can use relays
8180 not marked with the Fast flag. This "feature" could turn out to
8181 be a horrible bug; we should investigate more before it goes into
8185 - Allow disabling building of the manpages. Skipping the manpage
8186 speeds up the build considerably.
8188 o Minor bugfixes (on 0.2.2.x):
8189 - Fix a memleak in the EXTENDCIRCUIT logic. Spotted by coverity.
8190 Bugfix on 0.2.2.9-alpha.
8191 - Disallow values larger than INT32_MAX for PerConnBWRate|Burst
8192 config option. Bugfix on 0.2.2.7-alpha.
8193 - Ship the asciidoc-helper file in the tarball, so that people can
8194 build from source if they want to, and touching the .1.txt files
8195 doesn't break the build. Bugfix on 0.2.2.9-alpha.
8197 o Minor bugfixes (on 0.2.1.x or earlier):
8198 - Fix a dereference-then-NULL-check sequence when publishing
8199 descriptors. Bugfix on 0.2.1.5-alpha. Discovered by ekir; fixes
8201 - Fix another dereference-then-NULL-check sequence. Bugfix on
8202 0.2.1.14-rc. Discovered by ekir; fixes bug 1256.
8203 - Make sure we treat potentially not NUL-terminated strings correctly.
8204 Bugfix on 0.1.1.13-alpha. Discovered by rieo; fixes bug 1257.
8206 o Code simplifications and refactoring:
8207 - Fix some urls in the exit notice file and make it XHTML1.1 strict
8208 compliant. Based on a patch from Christian Kujau.
8209 - Don't use sed in asciidoc-helper anymore.
8210 - Make the build process fail if asciidoc cannot be found and
8211 building with asciidoc isn't disabled.
8214 Changes in version 0.2.2.9-alpha - 2010-02-22
8215 Tor 0.2.2.9-alpha makes Tor work again on the latest OS X, updates the
8216 location of a directory authority, and cleans up a bunch of small bugs.
8218 o Directory authority changes:
8219 - Change IP address for dannenberg (v3 directory authority), and
8220 remove moria2 (obsolete v1, v2 directory authority and v0 hidden
8221 service directory authority) from the list.
8224 - Make Tor work again on the latest OS X: when deciding whether to
8225 use strange flags to turn TLS renegotiation on, detect the OpenSSL
8226 version at run-time, not compile time. We need to do this because
8227 Apple doesn't update its dev-tools headers when it updates its
8228 libraries in a security patch.
8229 - Fix a potential buffer overflow in lookup_last_hid_serv_request()
8230 that could happen on 32-bit platforms with 64-bit time_t. Also fix
8231 a memory leak when requesting a hidden service descriptor we've
8232 requested before. Fixes bug 1242, bugfix on 0.2.0.18-alpha. Found
8234 - Authorities could be tricked into giving out the Exit flag to relays
8235 that didn't allow exiting to any ports. This bug could screw
8236 with load balancing and stats. Bugfix on 0.1.1.6-alpha; fixes bug
8237 1238. Bug discovered by Martin Kowalczyk.
8238 - When freeing a session key, zero it out completely. We only zeroed
8239 the first ptrsize bytes. Bugfix on 0.0.2pre8. Discovered and
8240 patched by ekir. Fixes bug 1254.
8243 - Fix static compilation by listing the openssl libraries in the right
8244 order. Bugfix on Tor 0.2.2.8-alpha; fixes bug 1237.
8245 - Resume handling .exit hostnames in a special way: originally we
8246 stripped the .exit part and used the requested exit relay. In
8247 0.2.2.1-alpha we stopped treating them in any special way, meaning
8248 if you use a .exit address then Tor will pass it on to the exit
8249 relay. Now we reject the .exit stream outright, since that behavior
8250 might be more expected by the user. Found and diagnosed by Scott
8251 Bennett and Downie on or-talk.
8252 - Don't spam the controller with events when we have no file
8253 descriptors available. Bugfix on 0.2.1.5-alpha. (Rate-limiting
8254 for log messages was already solved from bug 748.)
8255 - Avoid a bogus overlapped memcpy in tor_addr_copy(). Reported by
8257 - Make the DNSPort option work with libevent 2.x. Don't alter the
8258 behaviour for libevent 1.x. Fixes bug 1143. Found by SwissTorExit.
8259 - Emit a GUARD DROPPED controller event for a case we missed.
8260 - Make more fields in the controller protocol case-insensitive, since
8261 control-spec.txt said they were.
8262 - Refactor resolve_my_address() to not use gethostbyname() anymore.
8263 Fixes bug 1244; bugfix on 0.0.2pre25. Reported by Mike Mestnik.
8264 - Fix a spec conformance issue: the network-status-version token
8265 must be the first token in a v3 consensus or vote. Discovered by
8266 parakeep. Bugfix on 0.2.0.3-alpha.
8268 o Code simplifications and refactoring:
8269 - Generate our manpage and HTML documentation using Asciidoc. This
8270 change should make it easier to maintain the documentation, and
8272 - Remove the --enable-iphone option. According to reports from Marco
8273 Bonetti, Tor builds fine without any special tweaking on recent
8274 iPhone SDK versions.
8275 - Removed some unnecessary files from the source distribution. The
8276 AUTHORS file has now been merged into the people page on the
8277 website. The roadmaps and design doc can now be found in the
8278 projects directory in svn.
8279 - Enabled various circuit build timeout constants to be controlled
8280 by consensus parameters. Also set better defaults for these
8281 parameters based on experimentation on broadband and simulated
8285 - The 'EXTENDCIRCUIT' control port command can now be used with
8286 a circ id of 0 and no path. This feature will cause Tor to build
8287 a new 'fast' general purpose circuit using its own path selection
8289 - Added a BUILDTIMEOUT_SET controller event to describe changes
8290 to the circuit build timeout.
8291 - Future-proof the controller protocol a bit by ignoring keyword
8292 arguments we do not recognize.
8293 - Expand homedirs passed to tor-checkkey. This should silence a
8294 coverity complaint about passing a user-supplied string into
8295 open() without checking it.
8298 Changes in version 0.2.1.25 - 2010-03-16
8299 Tor 0.2.1.25 fixes a regression introduced in 0.2.1.23 that could
8300 prevent relays from guessing their IP address correctly. It also fixes
8301 several minor potential security bugs.
8304 - Fix a regression from our patch for bug 1244 that caused relays
8305 to guess their IP address incorrectly if they didn't set Address
8306 in their torrc and/or their address fails to resolve. Bugfix on
8307 0.2.1.23; fixes bug 1269.
8308 - When freeing a session key, zero it out completely. We only zeroed
8309 the first ptrsize bytes. Bugfix on 0.0.2pre8. Discovered and
8310 patched by ekir. Fixes bug 1254.
8313 - Fix a dereference-then-NULL-check sequence when publishing
8314 descriptors. Bugfix on 0.2.1.5-alpha. Discovered by ekir; fixes
8316 - Fix another dereference-then-NULL-check sequence. Bugfix on
8317 0.2.1.14-rc. Discovered by ekir; fixes bug 1256.
8318 - Make sure we treat potentially not NUL-terminated strings correctly.
8319 Bugfix on 0.1.1.13-alpha. Discovered by rieo; fixes bug 1257.
8323 Changes in version 0.2.1.24 - 2010-02-21
8324 Tor 0.2.1.24 makes Tor work again on the latest OS X -- this time
8328 - Work correctly out-of-the-box with even more vendor-patched versions
8329 of OpenSSL. In particular, make it so Debian and OS X don't need
8330 customized patches to run/build.
8333 Changes in version 0.2.1.23 - 2010-02-13
8334 Tor 0.2.1.23 fixes a huge client-side performance bug, makes Tor work
8335 again on the latest OS X, and updates the location of a directory
8338 o Major bugfixes (performance):
8339 - We were selecting our guards uniformly at random, and then weighting
8340 which of our guards we'd use uniformly at random. This imbalance
8341 meant that Tor clients were severely limited on throughput (and
8342 probably latency too) by the first hop in their circuit. Now we
8343 select guards weighted by currently advertised bandwidth. We also
8344 automatically discard guards picked using the old algorithm. Fixes
8345 bug 1217; bugfix on 0.2.1.3-alpha. Found by Mike Perry.
8348 - Make Tor work again on the latest OS X: when deciding whether to
8349 use strange flags to turn TLS renegotiation on, detect the OpenSSL
8350 version at run-time, not compile time. We need to do this because
8351 Apple doesn't update its dev-tools headers when it updates its
8352 libraries in a security patch.
8353 - Fix a potential buffer overflow in lookup_last_hid_serv_request()
8354 that could happen on 32-bit platforms with 64-bit time_t. Also fix
8355 a memory leak when requesting a hidden service descriptor we've
8356 requested before. Fixes bug 1242, bugfix on 0.2.0.18-alpha. Found
8359 o Directory authority changes:
8360 - Change IP address for dannenberg (v3 directory authority), and
8361 remove moria2 (obsolete v1, v2 directory authority and v0 hidden
8362 service directory authority) from the list.
8365 - Refactor resolve_my_address() to not use gethostbyname() anymore.
8366 Fixes bug 1244; bugfix on 0.0.2pre25. Reported by Mike Mestnik.
8369 - Avoid a mad rush at the beginning of each month when each client
8370 rotates half of its guards. Instead we spread the rotation out
8371 throughout the month, but we still avoid leaving a precise timestamp
8372 in the state file about when we first picked the guard. Improves
8373 over the behavior introduced in 0.1.2.17.
8376 Changes in version 0.2.2.8-alpha - 2010-01-26
8377 Tor 0.2.2.8-alpha fixes a crash bug in 0.2.2.7-alpha that has been
8378 causing bridge relays to disappear. If you're running a bridge,
8382 - Fix a memory corruption bug on bridges that occured during the
8383 inclusion of stats data in extra-info descriptors. Also fix the
8384 interface for geoip_get_bridge_stats* to prevent similar bugs in
8385 the future. Diagnosis by Tas, patch by Karsten and Sebastian.
8386 Fixes bug 1208; bugfix on 0.2.2.7-alpha.
8389 - Ignore OutboundBindAddress when connecting to localhost.
8390 Connections to localhost need to come _from_ localhost, or else
8391 local servers (like DNS and outgoing HTTP/SOCKS proxies) will often
8395 Changes in version 0.2.2.7-alpha - 2010-01-19
8396 Tor 0.2.2.7-alpha fixes a huge client-side performance bug, as well
8397 as laying the groundwork for further relay-side performance fixes. It
8398 also starts cleaning up client behavior with respect to the EntryNodes,
8399 ExitNodes, and StrictNodes config options.
8401 This release also rotates two directory authority keys, due to a
8402 security breach of some of the Torproject servers.
8404 o Directory authority changes:
8405 - Rotate keys (both v3 identity and relay identity) for moria1
8408 o Major features (performance):
8409 - We were selecting our guards uniformly at random, and then weighting
8410 which of our guards we'd use uniformly at random. This imbalance
8411 meant that Tor clients were severely limited on throughput (and
8412 probably latency too) by the first hop in their circuit. Now we
8413 select guards weighted by currently advertised bandwidth. We also
8414 automatically discard guards picked using the old algorithm. Fixes
8415 bug 1217; bugfix on 0.2.1.3-alpha. Found by Mike Perry.
8416 - When choosing which cells to relay first, relays can now favor
8417 circuits that have been quiet recently, to provide lower latency
8418 for low-volume circuits. By default, relays enable or disable this
8419 feature based on a setting in the consensus. You can override
8420 this default by using the new "CircuitPriorityHalflife" config
8421 option. Design and code by Ian Goldberg, Can Tang, and Chris
8423 - Add separate per-conn write limiting to go with the per-conn read
8424 limiting. We added a global write limit in Tor 0.1.2.5-alpha,
8425 but never per-conn write limits.
8426 - New consensus params "bwconnrate" and "bwconnburst" to let us
8427 rate-limit client connections as they enter the network. It's
8428 controlled in the consensus so we can turn it on and off for
8429 experiments. It's starting out off. Based on proposal 163.
8431 o Major features (relay selection options):
8432 - Switch to a StrictNodes config option, rather than the previous
8433 "StrictEntryNodes" / "StrictExitNodes" separation that was missing a
8434 "StrictExcludeNodes" option.
8435 - If EntryNodes, ExitNodes, ExcludeNodes, or ExcludeExitNodes
8436 change during a config reload, mark and discard all our origin
8437 circuits. This fix should address edge cases where we change the
8438 config options and but then choose a circuit that we created before
8440 - If EntryNodes or ExitNodes are set, be more willing to use an
8441 unsuitable (e.g. slow or unstable) circuit. The user asked for it,
8443 - Make EntryNodes config option much more aggressive even when
8444 StrictNodes is not set. Before it would prepend your requested
8445 entrynodes to your list of guard nodes, but feel free to use others
8446 after that. Now it chooses only from your EntryNodes if any of
8447 those are available, and only falls back to others if a) they're
8448 all down and b) StrictNodes is not set.
8449 - Now we refresh your entry guards from EntryNodes at each consensus
8450 fetch -- rather than just at startup and then they slowly rot as
8451 the network changes.
8454 - Stop bridge directory authorities from answering dbg-stability.txt
8455 directory queries, which would let people fetch a list of all
8456 bridge identities they track. Bugfix on 0.2.1.6-alpha.
8459 - Log a notice when we get a new control connection. Now it's easier
8460 for security-conscious users to recognize when a local application
8461 is knocking on their controller door. Suggested by bug 1196.
8462 - New config option "CircuitStreamTimeout" to override our internal
8463 timeout schedule for how many seconds until we detach a stream from
8464 a circuit and try a new circuit. If your network is particularly
8465 slow, you might want to set this to a number like 60.
8466 - New controller command "getinfo config-text". It returns the
8467 contents that Tor would write if you send it a SAVECONF command,
8468 so the controller can write the file to disk itself.
8469 - New options for SafeLogging to allow scrubbing only log messages
8470 generated while acting as a relay.
8471 - Ship the bridges spec file in the tarball too.
8472 - Avoid a mad rush at the beginning of each month when each client
8473 rotates half of its guards. Instead we spread the rotation out
8474 throughout the month, but we still avoid leaving a precise timestamp
8475 in the state file about when we first picked the guard. Improves
8476 over the behavior introduced in 0.1.2.17.
8478 o Minor bugfixes (compiling):
8479 - Fix compilation on OS X 10.3, which has a stub mlockall() but
8480 hides it. Bugfix on 0.2.2.6-alpha.
8481 - Fix compilation on Solaris by removing support for the
8482 DisableAllSwap config option. Solaris doesn't have an rlimit for
8483 mlockall, so we cannot use it safely. Fixes bug 1198; bugfix on
8486 o Minor bugfixes (crashes):
8487 - Do not segfault when writing buffer stats when we haven't observed
8488 a single circuit to report about. Found by Fabian Lanze. Bugfix on
8490 - If we're in the pathological case where there's no exit bandwidth
8491 but there is non-exit bandwidth, or no guard bandwidth but there
8492 is non-guard bandwidth, don't crash during path selection. Bugfix
8494 - Fix an impossible-to-actually-trigger buffer overflow in relay
8495 descriptor generation. Bugfix on 0.1.0.15.
8497 o Minor bugfixes (privacy):
8498 - Fix an instance where a Tor directory mirror might accidentally
8499 log the IP address of a misbehaving Tor client. Bugfix on
8501 - Don't list Windows capabilities in relay descriptors. We never made
8502 use of them, and maybe it's a bad idea to publish them. Bugfix
8505 o Minor bugfixes (other):
8506 - Resolve an edge case in path weighting that could make us misweight
8507 our relay selection. Fixes bug 1203; bugfix on 0.0.8rc1.
8508 - Fix statistics on client numbers by country as seen by bridges that
8509 were broken in 0.2.2.1-alpha. Also switch to reporting full 24-hour
8510 intervals instead of variable 12-to-48-hour intervals.
8511 - After we free an internal connection structure, overwrite it
8512 with a different memory value than we use for overwriting a freed
8513 internal circuit structure. Should help with debugging. Suggested
8515 - Update our OpenSSL 0.9.8l fix so that it works with OpenSSL 0.9.8m
8519 - Remove the HSAuthorityRecordStats option that version 0 hidden
8520 service authorities could have used to track statistics of overall
8521 hidden service usage.
8524 Changes in version 0.2.1.22 - 2010-01-19
8525 Tor 0.2.1.22 fixes a critical privacy problem in bridge directory
8526 authorities -- it would tell you its whole history of bridge descriptors
8527 if you make the right directory request. This stable update also
8528 rotates two of the seven v3 directory authority keys and locations.
8530 o Directory authority changes:
8531 - Rotate keys (both v3 identity and relay identity) for moria1
8535 - Stop bridge directory authorities from answering dbg-stability.txt
8536 directory queries, which would let people fetch a list of all
8537 bridge identities they track. Bugfix on 0.2.1.6-alpha.
8540 Changes in version 0.2.1.21 - 2009-12-21
8541 Tor 0.2.1.21 fixes an incompatibility with the most recent OpenSSL
8542 library. If you use Tor on Linux / Unix and you're getting SSL
8543 renegotiation errors, upgrading should help. We also recommend an
8544 upgrade if you're an exit relay.
8547 - Work around a security feature in OpenSSL 0.9.8l that prevents our
8548 handshake from working unless we explicitly tell OpenSSL that we
8549 are using SSL renegotiation safely. We are, of course, but OpenSSL
8550 0.9.8l won't work unless we say we are.
8551 - Avoid crashing if the client is trying to upload many bytes and the
8552 circuit gets torn down at the same time, or if the flip side
8553 happens on the exit relay. Bugfix on 0.2.0.1-alpha; fixes bug 1150.
8556 - Do not refuse to learn about authority certs and v2 networkstatus
8557 documents that are older than the latest consensus. This bug might
8558 have degraded client bootstrapping. Bugfix on 0.2.0.10-alpha.
8559 Spotted and fixed by xmux.
8560 - Fix a couple of very-hard-to-trigger memory leaks, and one hard-to-
8561 trigger platform-specific option misparsing case found by Coverity
8563 - Fix a compilation warning on Fedora 12 by removing an impossible-to-
8564 trigger assert. Fixes bug 1173.
8567 Changes in version 0.2.2.6-alpha - 2009-11-19
8568 Tor 0.2.2.6-alpha lays the groundwork for many upcoming features:
8569 support for the new lower-footprint "microdescriptor" directory design,
8570 future-proofing our consensus format against new hash functions or
8571 other changes, and an Android port. It also makes Tor compatible with
8572 the upcoming OpenSSL 0.9.8l release, and fixes a variety of bugs.
8575 - Directory authorities can now create, vote on, and serve multiple
8576 parallel formats of directory data as part of their voting process.
8577 Partially implements Proposal 162: "Publish the consensus in
8579 - Directory authorities can now agree on and publish small summaries
8580 of router information that clients can use in place of regular
8581 server descriptors. This transition will eventually allow clients
8582 to use far less bandwidth for downloading information about the
8583 network. Begins the implementation of Proposal 158: "Clients
8584 download consensus + microdescriptors".
8585 - The directory voting system is now extensible to use multiple hash
8586 algorithms for signatures and resource selection. Newer formats
8587 are signed with SHA256, with a possibility for moving to a better
8588 hash algorithm in the future.
8589 - New DisableAllSwap option. If set to 1, Tor will attempt to lock all
8590 current and future memory pages via mlockall(). On supported
8591 platforms (modern Linux and probably BSD but not Windows or OS X),
8592 this should effectively disable any and all attempts to page out
8593 memory. This option requires that you start your Tor as root --
8594 if you use DisableAllSwap, please consider using the User option
8595 to properly reduce the privileges of your Tor.
8596 - Numerous changes, bugfixes, and workarounds from Nathan Freitas
8597 to help Tor build correctly for Android phones.
8600 - Work around a security feature in OpenSSL 0.9.8l that prevents our
8601 handshake from working unless we explicitly tell OpenSSL that we
8602 are using SSL renegotiation safely. We are, but OpenSSL 0.9.8l
8603 won't work unless we say we are.
8606 - Fix a crash bug when trying to initialize the evdns module in
8607 Libevent 2. Bugfix on 0.2.1.16-rc.
8608 - Stop logging at severity 'warn' when some other Tor client tries
8609 to establish a circuit with us using weak DH keys. It's a protocol
8610 violation, but that doesn't mean ordinary users need to hear about
8611 it. Fixes the bug part of bug 1114. Bugfix on 0.1.0.13.
8612 - Do not refuse to learn about authority certs and v2 networkstatus
8613 documents that are older than the latest consensus. This bug might
8614 have degraded client bootstrapping. Bugfix on 0.2.0.10-alpha.
8615 Spotted and fixed by xmux.
8616 - Fix numerous small code-flaws found by Coverity Scan Rung 3.
8617 - If all authorities restart at once right before a consensus vote,
8618 nobody will vote about "Running", and clients will get a consensus
8619 with no usable relays. Instead, authorities refuse to build a
8620 consensus if this happens. Bugfix on 0.2.0.10-alpha; fixes bug 1066.
8621 - If your relay can't keep up with the number of incoming create
8622 cells, it would log one warning per failure into your logs. Limit
8623 warnings to 1 per minute. Bugfix on 0.0.2pre10; fixes bug 1042.
8624 - Bridges now use "reject *:*" as their default exit policy. Bugfix
8625 on 0.2.0.3-alpha; fixes bug 1113.
8626 - Fix a memory leak on directory authorities during voting that was
8627 introduced in 0.2.2.1-alpha. Found via valgrind.
8630 Changes in version 0.2.1.20 - 2009-10-15
8631 Tor 0.2.1.20 fixes a crash bug when you're accessing many hidden
8632 services at once, prepares for more performance improvements, and
8633 fixes a bunch of smaller bugs.
8635 The Windows and OS X bundles also include a more recent Vidalia,
8636 and switch from Privoxy to Polipo.
8638 The OS X installers are now drag and drop. It's best to un-install
8639 Tor/Vidalia and then install this new bundle, rather than upgrade. If
8640 you want to upgrade, you'll need to update the paths for Tor and Polipo
8641 in the Vidalia Settings window.
8644 - Send circuit or stream sendme cells when our window has decreased
8645 by 100 cells, not when it has decreased by 101 cells. Bug uncovered
8646 by Karsten when testing the "reduce circuit window" performance
8647 patch. Bugfix on the 54th commit on Tor -- from July 2002,
8648 before the release of Tor 0.0.0. This is the new winner of the
8650 - Fix a remotely triggerable memory leak when a consensus document
8651 contains more than one signature from the same voter. Bugfix on
8653 - Avoid segfault in rare cases when finishing an introduction circuit
8654 as a client and finding out that we don't have an introduction key
8655 for it. Fixes bug 1073. Reported by Aaron Swartz.
8658 - Tor now reads the "circwindow" parameter out of the consensus,
8659 and uses that value for its circuit package window rather than the
8660 default of 1000 cells. Begins the implementation of proposal 168.
8662 o New directory authorities:
8663 - Set up urras (run by Jacob Appelbaum) as the seventh v3 directory
8665 - Move moria1 and tonga to alternate IP addresses.
8668 - Fix a signed/unsigned compile warning in 0.2.1.19.
8669 - Fix possible segmentation fault on directory authorities. Bugfix on
8671 - Fix an extremely rare infinite recursion bug that could occur if
8672 we tried to log a message after shutting down the log subsystem.
8673 Found by Matt Edman. Bugfix on 0.2.0.16-alpha.
8674 - Fix an obscure bug where hidden services on 64-bit big-endian
8675 systems might mis-read the timestamp in v3 introduce cells, and
8676 refuse to connect back to the client. Discovered by "rotor".
8677 Bugfix on 0.2.1.6-alpha.
8678 - We were triggering a CLOCK_SKEW controller status event whenever
8679 we connect via the v2 connection protocol to any relay that has
8680 a wrong clock. Instead, we should only inform the controller when
8681 it's a trusted authority that claims our clock is wrong. Bugfix
8682 on 0.2.0.20-rc; starts to fix bug 1074. Reported by SwissTorExit.
8683 - We were telling the controller about CHECKING_REACHABILITY and
8684 REACHABILITY_FAILED status events whenever we launch a testing
8685 circuit or notice that one has failed. Instead, only tell the
8686 controller when we want to inform the user of overall success or
8687 overall failure. Bugfix on 0.1.2.6-alpha. Fixes bug 1075. Reported
8689 - Don't warn when we're using a circuit that ends with a node
8690 excluded in ExcludeExitNodes, but the circuit is not used to access
8691 the outside world. This should help fix bug 1090. Bugfix on
8693 - Work around a small memory leak in some versions of OpenSSL that
8694 stopped the memory used by the hostname TLS extension from being
8698 - Add a "getinfo status/accepted-server-descriptor" controller
8699 command, which is the recommended way for controllers to learn
8700 whether our server descriptor has been successfully received by at
8701 least on directory authority. Un-recommend good-server-descriptor
8702 getinfo and status events until we have a better design for them.
8705 Changes in version 0.2.2.5-alpha - 2009-10-11
8706 Tor 0.2.2.5-alpha fixes a few compile problems in 0.2.2.4-alpha.
8709 - Make the tarball compile again. Oops. Bugfix on 0.2.2.4-alpha.
8711 o Directory authorities:
8712 - Temporarily (just for this release) move dizum to an alternate
8716 Changes in version 0.2.2.4-alpha - 2009-10-10
8717 Tor 0.2.2.4-alpha fixes more crash bugs in 0.2.2.2-alpha. It also
8718 introduces a new unit test framework, shifts directry authority
8719 addresses around to reduce the impact from recent blocking events,
8720 and fixes a few smaller bugs.
8723 - Fix several more asserts in the circuit_build_times code, for
8724 example one that causes Tor to fail to start once we have
8725 accumulated 5000 build times in the state file. Bugfixes on
8726 0.2.2.2-alpha; fixes bug 1108.
8728 o New directory authorities:
8729 - Move moria1 and Tonga to alternate IP addresses.
8732 - Log SSL state transitions at debug level during handshake, and
8733 include SSL states in error messages. This may help debug future
8734 SSL handshake issues.
8735 - Add a new "Handshake" log domain for activities that happen
8736 during the TLS handshake.
8737 - Revert to the "June 3 2009" ip-to-country file. The September one
8738 seems to have removed most US IP addresses.
8739 - Directory authorities now reject Tor relays with versions less than
8740 0.1.2.14. This step cuts out four relays from the current network,
8741 none of which are very big.
8744 - Fix a couple of smaller issues with gathering statistics. Bugfixes
8746 - Fix two memory leaks in the error case of
8747 circuit_build_times_parse_state(). Bugfix on 0.2.2.2-alpha.
8748 - Don't count one-hop circuits when we're estimating how long it
8749 takes circuits to build on average. Otherwise we'll set our circuit
8750 build timeout lower than we should. Bugfix on 0.2.2.2-alpha.
8751 - Directory authorities no longer change their opinion of, or vote on,
8752 whether a router is Running, unless they have themselves been
8753 online long enough to have some idea. Bugfix on 0.2.0.6-alpha.
8756 o Code simplifications and refactoring:
8757 - Revise our unit tests to use the "tinytest" framework, so we
8758 can run tests in their own processes, have smarter setup/teardown
8759 code, and so on. The unit test code has moved to its own
8760 subdirectory, and has been split into multiple modules.
8763 Changes in version 0.2.2.3-alpha - 2009-09-23
8764 Tor 0.2.2.3-alpha fixes a few crash bugs in 0.2.2.2-alpha.
8767 - Fix an overzealous assert in our new circuit build timeout code.
8768 Bugfix on 0.2.2.2-alpha; fixes bug 1103.
8771 - If the networkstatus consensus tells us that we should use a
8772 negative circuit package window, ignore it. Otherwise we'll
8773 believe it and then trigger an assert. Bugfix on 0.2.2.2-alpha.
8776 Changes in version 0.2.2.2-alpha - 2009-09-21
8777 Tor 0.2.2.2-alpha introduces our latest performance improvement for
8778 clients: Tor tracks the average time it takes to build a circuit, and
8779 avoids using circuits that take too long to build. For fast connections,
8780 this feature can cut your expected latency in half. For slow or flaky
8781 connections, it could ruin your Tor experience. Let us know if it does!
8784 - Tor now tracks how long it takes to build client-side circuits
8785 over time, and adapts its timeout to local network performance.
8786 Since a circuit that takes a long time to build will also provide
8787 bad performance, we get significant latency improvements by
8788 discarding the slowest 20% of circuits. Specifically, Tor creates
8789 circuits more aggressively than usual until it has enough data
8790 points for a good timeout estimate. Implements proposal 151.
8791 We are especially looking for reports (good and bad) from users with
8792 both EDGE and broadband connections that can move from broadband
8793 to EDGE and find out if the build-time data in the .tor/state gets
8794 reset without loss of Tor usability. You should also see a notice
8795 log message telling you that Tor has reset its timeout.
8796 - Directory authorities can now vote on arbitary integer values as
8797 part of the consensus process. This is designed to help set
8798 network-wide parameters. Implements proposal 167.
8799 - Tor now reads the "circwindow" parameter out of the consensus,
8800 and uses that value for its circuit package window rather than the
8801 default of 1000 cells. Begins the implementation of proposal 168.
8804 - Fix a remotely triggerable memory leak when a consensus document
8805 contains more than one signature from the same voter. Bugfix on
8809 - Fix an extremely rare infinite recursion bug that could occur if
8810 we tried to log a message after shutting down the log subsystem.
8811 Found by Matt Edman. Bugfix on 0.2.0.16-alpha.
8812 - Fix parsing for memory or time units given without a space between
8813 the number and the unit. Bugfix on 0.2.2.1-alpha; fixes bug 1076.
8814 - A networkstatus vote must contain exactly one signature. Spec
8815 conformance issue. Bugfix on 0.2.0.3-alpha.
8816 - Fix an obscure bug where hidden services on 64-bit big-endian
8817 systems might mis-read the timestamp in v3 introduce cells, and
8818 refuse to connect back to the client. Discovered by "rotor".
8819 Bugfix on 0.2.1.6-alpha.
8820 - We were triggering a CLOCK_SKEW controller status event whenever
8821 we connect via the v2 connection protocol to any relay that has
8822 a wrong clock. Instead, we should only inform the controller when
8823 it's a trusted authority that claims our clock is wrong. Bugfix
8824 on 0.2.0.20-rc; starts to fix bug 1074. Reported by SwissTorExit.
8825 - We were telling the controller about CHECKING_REACHABILITY and
8826 REACHABILITY_FAILED status events whenever we launch a testing
8827 circuit or notice that one has failed. Instead, only tell the
8828 controller when we want to inform the user of overall success or
8829 overall failure. Bugfix on 0.1.2.6-alpha. Fixes bug 1075. Reported
8831 - Don't warn when we're using a circuit that ends with a node
8832 excluded in ExcludeExitNodes, but the circuit is not used to access
8833 the outside world. This should help fix bug 1090, but more problems
8834 remain. Bugfix on 0.2.1.6-alpha.
8835 - Work around a small memory leak in some versions of OpenSSL that
8836 stopped the memory used by the hostname TLS extension from being
8838 - Make our 'torify' script more portable; if we have only one of
8839 'torsocks' or 'tsocks' installed, don't complain to the user;
8840 and explain our warning about tsocks better.
8843 - Add a "getinfo status/accepted-server-descriptor" controller
8844 command, which is the recommended way for controllers to learn
8845 whether our server descriptor has been successfully received by at
8846 least on directory authority. Un-recommend good-server-descriptor
8847 getinfo and status events until we have a better design for them.
8848 - Update to the "September 4 2009" ip-to-country file.
8851 Changes in version 0.2.2.1-alpha - 2009-08-26
8852 Tor 0.2.2.1-alpha disables ".exit" address notation by default, allows
8853 Tor clients to bootstrap on networks where only port 80 is reachable,
8854 makes it more straightforward to support hardware crypto accelerators,
8855 and starts the groundwork for gathering stats safely at relays.
8858 - Start the process of disabling ".exit" address notation, since it
8859 can be used for a variety of esoteric application-level attacks
8860 on users. To reenable it, set "AllowDotExit 1" in your torrc. Fix
8863 o New directory authorities:
8864 - Set up urras (run by Jacob Appelbaum) as the seventh v3 directory
8868 - New AccelName and AccelDir options add support for dynamic OpenSSL
8869 hardware crypto acceleration engines.
8870 - Tor now supports tunneling all of its outgoing connections over
8871 a SOCKS proxy, using the SOCKS4Proxy and/or SOCKS5Proxy
8872 configuration options. Code by Christopher Davis.
8875 - Send circuit or stream sendme cells when our window has decreased
8876 by 100 cells, not when it has decreased by 101 cells. Bug uncovered
8877 by Karsten when testing the "reduce circuit window" performance
8878 patch. Bugfix on the 54th commit on Tor -- from July 2002,
8879 before the release of Tor 0.0.0. This is the new winner of the
8882 o New options for gathering stats safely:
8883 - Directory mirrors that set "DirReqStatistics 1" write statistics
8884 about directory requests to disk every 24 hours. As compared to the
8885 --enable-geoip-stats flag in 0.2.1.x, there are a few improvements:
8886 1) stats are written to disk exactly every 24 hours; 2) estimated
8887 shares of v2 and v3 requests are determined as mean values, not at
8888 the end of a measurement period; 3) unresolved requests are listed
8889 with country code '??'; 4) directories also measure download times.
8890 - Exit nodes that set "ExitPortStatistics 1" write statistics on the
8891 number of exit streams and transferred bytes per port to disk every
8893 - Relays that set "CellStatistics 1" write statistics on how long
8894 cells spend in their circuit queues to disk every 24 hours.
8895 - Entry nodes that set "EntryStatistics 1" write statistics on the
8896 rough number and origins of connecting clients to disk every 24
8898 - Relays that write any of the above statistics to disk and set
8899 "ExtraInfoStatistics 1" include the past 24 hours of statistics in
8900 their extra-info documents.
8903 - New --digests command-line switch to output the digests of the
8904 source files Tor was built with.
8905 - The "torify" script now uses torsocks where available.
8906 - The memarea code now uses a sentinel value at the end of each area
8907 to make sure nothing writes beyond the end of an area. This might
8908 help debug some conceivable causes of bug 930.
8909 - Time and memory units in the configuration file can now be set to
8910 fractional units. For example, "2.5 GB" is now a valid value for
8912 - Certain Tor clients (such as those behind check.torproject.org) may
8913 want to fetch the consensus in an extra early manner. To enable this
8914 a user may now set FetchDirInfoExtraEarly to 1. This also depends on
8915 setting FetchDirInfoEarly to 1. Previous behavior will stay the same
8916 as only certain clients who must have this information sooner should
8918 - Instead of adding the svn revision to the Tor version string, report
8919 the git commit (when we're building from a git checkout).
8922 - If any of the v3 certs we download are unparseable, we should
8923 actually notice the failure so we don't retry indefinitely. Bugfix
8924 on 0.2.0.x; reported by "rotator".
8925 - If the cached cert file is unparseable, warn but don't exit.
8926 - Fix possible segmentation fault on directory authorities. Bugfix on
8928 - When Tor fails to parse a descriptor of any kind, dump it to disk.
8929 Might help diagnosing bug 1051.
8931 o Deprecated and removed features:
8932 - The controller no longer accepts the old obsolete "addr-mappings/"
8933 or "unregistered-servers-" GETINFO values.
8934 - Hidden services no longer publish version 0 descriptors, and clients
8935 do not request or use version 0 descriptors. However, the old hidden
8936 service authorities still accept and serve version 0 descriptors
8937 when contacted by older hidden services/clients.
8938 - The EXTENDED_EVENTS and VERBOSE_NAMES controller features are now
8939 always on; using them is necessary for correct forward-compatible
8941 - Remove support for .noconnect style addresses. Nobody was using
8942 them, and they provided another avenue for detecting Tor users
8943 via application-level web tricks.
8945 o Packaging changes:
8946 - Upgrade Vidalia from 0.1.15 to 0.2.3 in the Windows and OS X
8947 installer bundles. See
8948 https://trac.vidalia-project.net/browser/vidalia/tags/vidalia-0.2.3/CHANGELOG
8949 for details of what's new in Vidalia 0.2.3.
8950 - Windows Vidalia Bundle: update Privoxy from 3.0.6 to 3.0.14-beta.
8951 - OS X Vidalia Bundle: move to Polipo 1.0.4 with Tor specific
8952 configuration file, rather than the old Privoxy.
8953 - OS X Vidalia Bundle: Vidalia, Tor, and Polipo are compiled as
8954 x86-only for better compatibility with OS X 10.6, aka Snow Leopard.
8955 - OS X Tor Expert Bundle: Tor is compiled as x86-only for
8956 better compatibility with OS X 10.6, aka Snow Leopard.
8957 - OS X Vidalia Bundle: The multi-package installer is now replaced
8958 by a simple drag and drop to the /Applications folder. This change
8959 occurred with the upgrade to Vidalia 0.2.3.
8962 Changes in version 0.2.1.19 - 2009-07-28
8963 Tor 0.2.1.19 fixes a major bug with accessing and providing hidden
8964 services on Tor 0.2.1.3-alpha through 0.2.1.18.
8967 - Make accessing hidden services on 0.2.1.x work right again.
8968 Bugfix on 0.2.1.3-alpha; workaround for bug 1038. Diagnosis and
8969 part of patch provided by "optimist".
8972 - When a relay/bridge is writing out its identity key fingerprint to
8973 the "fingerprint" file and to its logs, write it without spaces. Now
8974 it will look like the fingerprints in our bridges documentation,
8975 and confuse fewer users.
8978 - Relays no longer publish a new server descriptor if they change
8979 their MaxAdvertisedBandwidth config option but it doesn't end up
8980 changing their advertised bandwidth numbers. Bugfix on 0.2.0.28-rc;
8981 fixes bug 1026. Patch from Sebastian.
8982 - Avoid leaking memory every time we get a create cell but we have
8983 so many already queued that we refuse it. Bugfix on 0.2.0.19-alpha;
8984 fixes bug 1034. Reported by BarkerJr.
8987 Changes in version 0.2.1.18 - 2009-07-24
8988 Tor 0.2.1.18 lays the foundations for performance improvements,
8989 adds status events to help users diagnose bootstrap problems, adds
8990 optional authentication/authorization for hidden services, fixes a
8991 variety of potential anonymity problems, and includes a huge pile of
8992 other features and bug fixes.
8995 - Add LIBS=-lrt to Makefile.am so the Tor RPMs use a static libevent.
8998 Changes in version 0.2.1.17-rc - 2009-07-07
8999 Tor 0.2.1.17-rc marks the fourth -- and hopefully last -- release
9000 candidate for the 0.2.1.x series. It lays the groundwork for further
9001 client performance improvements, and also fixes a big bug with directory
9002 authorities that were causing them to assign Guard and Stable flags
9005 The Windows bundles also finally include the geoip database that we
9006 thought we'd been shipping since 0.2.0.x (oops), and the OS X bundles
9007 should actually install Torbutton rather than giving you a cryptic
9008 failure message (oops).
9011 - Clients now use the bandwidth values in the consensus, rather than
9012 the bandwidth values in each relay descriptor. This approach opens
9013 the door to more accurate bandwidth estimates once the directory
9014 authorities start doing active measurements. Implements more of
9018 - When Tor clients restart after 1-5 days, they discard all their
9019 cached descriptors as too old, but they still use the cached
9020 consensus document. This approach is good for robustness, but
9021 bad for performance: since they don't know any bandwidths, they
9022 end up choosing at random rather than weighting their choice by
9023 speed. Fixed by the above feature of putting bandwidths in the
9024 consensus. Bugfix on 0.2.0.x.
9025 - Directory authorities were neglecting to mark relays down in their
9026 internal histories if the relays fall off the routerlist without
9027 ever being found unreachable. So there were relays in the histories
9028 that haven't been seen for eight months, and are listed as being
9029 up for eight months. This wreaked havoc on the "median wfu"
9030 and "median mtbf" calculations, in turn making Guard and Stable
9031 flags very wrong, hurting network performance. Fixes bugs 696 and
9032 969. Bugfix on 0.2.0.6-alpha.
9035 - Serve the DirPortFrontPage page even when we have been approaching
9036 our quotas recently. Fixes bug 1013; bugfix on 0.2.1.8-alpha.
9037 - The control port would close the connection before flushing long
9038 replies, such as the network consensus, if a QUIT command was issued
9039 before the reply had completed. Now, the control port flushes all
9040 pending replies before closing the connection. Also fixed a spurious
9041 warning when a QUIT command is issued after a malformed or rejected
9042 AUTHENTICATE command, but before the connection was closed. Patch
9043 by Marcus Griep. Bugfix on 0.2.0.x; fixes bugs 1015 and 1016.
9044 - When we can't find an intro key for a v2 hidden service descriptor,
9045 fall back to the v0 hidden service descriptor and log a bug message.
9046 Workaround for bug 1024.
9047 - Fix a log message that did not respect the SafeLogging option.
9051 - If we're a relay and we change our IP address, be more verbose
9052 about the reason that made us change. Should help track down
9053 further bugs for relays on dynamic IP addresses.
9056 Changes in version 0.2.0.35 - 2009-06-24
9058 - Avoid crashing in the presence of certain malformed descriptors.
9059 Found by lark, and by automated fuzzing.
9060 - Fix an edge case where a malicious exit relay could convince a
9061 controller that the client's DNS question resolves to an internal IP
9062 address. Bug found and fixed by "optimist"; bugfix on 0.1.2.8-beta.
9065 - Finally fix the bug where dynamic-IP relays disappear when their
9066 IP address changes: directory mirrors were mistakenly telling
9067 them their old address if they asked via begin_dir, so they
9068 never got an accurate answer about their new address, so they
9069 just vanished after a day. For belt-and-suspenders, relays that
9070 don't set Address in their config now avoid using begin_dir for
9071 all direct connections. Should fix bugs 827, 883, and 900.
9072 - Fix a timing-dependent, allocator-dependent, DNS-related crash bug
9073 that would occur on some exit nodes when DNS failures and timeouts
9074 occurred in certain patterns. Fix for bug 957.
9077 - When starting with a cache over a few days old, do not leak
9078 memory for the obsolete router descriptors in it. Bugfix on
9079 0.2.0.33; fixes bug 672.
9080 - Hidden service clients didn't use a cached service descriptor that
9081 was older than 15 minutes, but wouldn't fetch a new one either,
9082 because there was already one in the cache. Now, fetch a v2
9083 descriptor unless the same descriptor was added to the cache within
9084 the last 15 minutes. Fixes bug 997; reported by Marcus Griep.
9087 Changes in version 0.2.1.16-rc - 2009-06-20
9088 Tor 0.2.1.16-rc speeds up performance for fast exit relays, and fixes
9089 a bunch of minor bugs.
9092 - Fix an edge case where a malicious exit relay could convince a
9093 controller that the client's DNS question resolves to an internal IP
9094 address. Bug found and fixed by "optimist"; bugfix on 0.1.2.8-beta.
9096 o Major performance improvements (on 0.2.0.x):
9097 - Disable and refactor some debugging checks that forced a linear scan
9098 over the whole server-side DNS cache. These accounted for over 50%
9099 of CPU time on a relatively busy exit node's gprof profile. Found
9101 - Disable some debugging checks that appeared in exit node profile
9105 - Update to the "June 3 2009" ip-to-country file.
9106 - Do not have tor-resolve automatically refuse all .onion addresses;
9107 if AutomapHostsOnResolve is set in your torrc, this will work fine.
9109 o Minor bugfixes (on 0.2.0.x):
9110 - Log correct error messages for DNS-related network errors on
9112 - Fix a race condition that could cause crashes or memory corruption
9113 when running as a server with a controller listening for log
9115 - Avoid crashing when we have a policy specified in a DirPolicy or
9116 SocksPolicy or ReachableAddresses option with ports set on it,
9117 and we re-load the policy. May fix bug 996.
9118 - Hidden service clients didn't use a cached service descriptor that
9119 was older than 15 minutes, but wouldn't fetch a new one either,
9120 because there was already one in the cache. Now, fetch a v2
9121 descriptor unless the same descriptor was added to the cache within
9122 the last 15 minutes. Fixes bug 997; reported by Marcus Griep.
9124 o Minor bugfixes (on 0.2.1.x):
9125 - Don't warn users about low port and hibernation mix when they
9126 provide a *ListenAddress directive to fix that. Bugfix on
9128 - When switching back and forth between bridge mode, do not start
9129 gathering GeoIP data until two hours have passed.
9130 - Do not complain that the user has requested an excluded node as
9131 an exit when the node is not really an exit. This could happen
9132 because the circuit was for testing, or an introduction point.
9136 Changes in version 0.2.1.15-rc - 2009-05-25
9137 Tor 0.2.1.15-rc marks the second release candidate for the 0.2.1.x
9138 series. It fixes a major bug on fast exit relays, as well as a variety
9141 o Major bugfixes (on 0.2.0.x):
9142 - Fix a timing-dependent, allocator-dependent, DNS-related crash bug
9143 that would occur on some exit nodes when DNS failures and timeouts
9144 occurred in certain patterns. Fix for bug 957.
9146 o Minor bugfixes (on 0.2.0.x):
9147 - Actually return -1 in the error case for read_bandwidth_usage().
9148 Harmless bug, since we currently don't care about the return value
9149 anywhere. Bugfix on 0.2.0.9-alpha.
9150 - Provide a more useful log message if bug 977 (related to buffer
9151 freelists) ever reappears, and do not crash right away.
9152 - Fix an assertion failure on 64-bit platforms when we allocated
9153 memory right up to the end of a memarea, then realigned the memory
9154 one step beyond the end. Fixes a possible cause of bug 930.
9155 - Protect the count of open sockets with a mutex, so we can't
9156 corrupt it when two threads are closing or opening sockets at once.
9157 Fix for bug 939. Bugfix on 0.2.0.1-alpha.
9158 - Don't allow a bridge to publish its router descriptor to a
9159 non-bridge directory authority. Fixes part of bug 932.
9160 - When we change to or from being a bridge, reset our counts of
9161 client usage by country. Fixes bug 932.
9162 - Fix a bug that made stream bandwidth get misreported to the
9164 - Stop using malloc_usable_size() to use more area than we had
9165 actually allocated: it was safe, but made valgrind really unhappy.
9166 - Fix a memory leak when v3 directory authorities load their keys
9167 and cert from disk. Bugfix on 0.2.0.1-alpha.
9169 o Minor bugfixes (on 0.2.1.x):
9170 - Fix use of freed memory when deciding to mark a non-addable
9171 descriptor as never-downloadable. Bugfix on 0.2.1.9-alpha.
9174 Changes in version 0.2.1.14-rc - 2009-04-12
9175 Tor 0.2.1.14-rc marks the first release candidate for the 0.2.1.x
9176 series. It begins fixing some major performance problems, and also
9177 finally addresses the bug that was causing relays on dynamic IP
9178 addresses to fall out of the directory.
9181 - Clients replace entry guards that were chosen more than a few months
9182 ago. This change should significantly improve client performance,
9183 especially once more people upgrade, since relays that have been
9184 a guard for a long time are currently overloaded.
9186 o Major bugfixes (on 0.2.0):
9187 - Finally fix the bug where dynamic-IP relays disappear when their
9188 IP address changes: directory mirrors were mistakenly telling
9189 them their old address if they asked via begin_dir, so they
9190 never got an accurate answer about their new address, so they
9191 just vanished after a day. For belt-and-suspenders, relays that
9192 don't set Address in their config now avoid using begin_dir for
9193 all direct connections. Should fix bugs 827, 883, and 900.
9194 - Relays were falling out of the networkstatus consensus for
9195 part of a day if they changed their local config but the
9196 authorities discarded their new descriptor as "not sufficiently
9197 different". Now directory authorities accept a descriptor as changed
9198 if bandwidthrate or bandwidthburst changed. Partial fix for bug 962;
9200 - Avoid crashing in the presence of certain malformed descriptors.
9201 Found by lark, and by automated fuzzing.
9204 - When generating circuit events with verbose nicknames for
9205 controllers, try harder to look up nicknames for routers on a
9206 circuit. (Previously, we would look in the router descriptors we had
9207 for nicknames, but not in the consensus.) Partial fix for bug 941.
9208 - If the bridge config line doesn't specify a port, assume 443.
9209 This makes bridge lines a bit smaller and easier for users to
9211 - Raise the minimum bandwidth to be a relay from 20000 bytes to 20480
9212 bytes (aka 20KB/s), to match our documentation. Also update
9213 directory authorities so they always assign the Fast flag to relays
9214 with 20KB/s of capacity. Now people running relays won't suddenly
9215 find themselves not seeing any use, if the network gets faster
9217 - Update to the "April 3 2009" ip-to-country file.
9220 - Avoid trying to print raw memory to the logs when we decide to
9221 give up on downloading a given relay descriptor. Bugfix on
9223 - In tor-resolve, when the Tor client to use is specified by
9224 <hostname>:<port>, actually use the specified port rather than
9225 defaulting to 9050. Bugfix on 0.2.1.6-alpha.
9226 - Make directory usage recording work again. Bugfix on 0.2.1.6-alpha.
9227 - When starting with a cache over a few days old, do not leak
9228 memory for the obsolete router descriptors in it. Bugfix on
9230 - Avoid double-free on list of successfully uploaded hidden
9231 service discriptors. Fix for bug 948. Bugfix on 0.2.1.6-alpha.
9232 - Change memarea_strndup() implementation to work even when
9233 duplicating a string at the end of a page. This bug was
9234 harmless for now, but could have meant crashes later. Fix by
9235 lark. Bugfix on 0.2.1.1-alpha.
9236 - Limit uploaded directory documents to be 16M rather than 500K.
9237 The directory authorities were refusing v3 consensus votes from
9238 other authorities, since the votes are now 504K. Fixes bug 959;
9239 bugfix on 0.0.2pre17 (where we raised it from 50K to 500K ;).
9240 - Directory authorities should never send a 503 "busy" response to
9241 requests for votes or keys. Bugfix on 0.2.0.8-alpha; exposed by
9245 Changes in version 0.2.1.13-alpha - 2009-03-09
9246 Tor 0.2.1.13-alpha includes another big pile of minor bugfixes and
9247 cleanups. We're finally getting close to a release candidate.
9250 - Correctly update the list of which countries we exclude as
9251 exits, when the GeoIP file is loaded or reloaded. Diagnosed by
9252 lark. Bugfix on 0.2.1.6-alpha.
9254 o Minor bugfixes (on 0.2.0.x and earlier):
9255 - Automatically detect MacOSX versions earlier than 10.4.0, and
9256 disable kqueue from inside Tor when running with these versions.
9257 We previously did this from the startup script, but that was no
9258 help to people who didn't use the startup script. Resolves bug 863.
9259 - When we had picked an exit node for a connection, but marked it as
9260 "optional", and it turned out we had no onion key for the exit,
9261 stop wanting that exit and try again. This situation may not
9262 be possible now, but will probably become feasible with proposal
9263 158. Spotted by rovv. Fixes another case of bug 752.
9264 - Clients no longer cache certificates for authorities they do not
9265 recognize. Bugfix on 0.2.0.9-alpha.
9266 - When we can't transmit a DNS request due to a network error, retry
9267 it after a while, and eventually transmit a failing response to
9268 the RESOLVED cell. Bugfix on 0.1.2.5-alpha.
9269 - If the controller claimed responsibility for a stream, but that
9270 stream never finished making its connection, it would live
9271 forever in circuit_wait state. Now we close it after SocksTimeout
9272 seconds. Bugfix on 0.1.2.7-alpha; reported by Mike Perry.
9273 - Drop begin cells to a hidden service if they come from the middle
9274 of a circuit. Patch from lark.
9275 - When we erroneously receive two EXTEND cells for the same circuit
9276 ID on the same connection, drop the second. Patch from lark.
9277 - Fix a crash that occurs on exit nodes when a nameserver request
9278 timed out. Bugfix on 0.1.2.1-alpha; our CLEAR debugging code had
9279 been suppressing the bug since 0.1.2.10-alpha. Partial fix for
9281 - Do not assume that a stack-allocated character array will be
9282 64-bit aligned on platforms that demand that uint64_t access is
9283 aligned. Possible fix for bug 604.
9284 - Parse dates and IPv4 addresses in a locale- and libc-independent
9285 manner, to avoid platform-dependent behavior on malformed input.
9286 - Build correctly when configured to build outside the main source
9287 path. Patch from Michael Gold.
9288 - We were already rejecting relay begin cells with destination port
9289 of 0. Now also reject extend cells with destination port or address
9290 of 0. Suggested by lark.
9292 o Minor bugfixes (on 0.2.1.x):
9293 - Don't re-extend introduction circuits if we ran out of RELAY_EARLY
9294 cells. Bugfix on 0.2.1.3-alpha. Fixes more of bug 878.
9295 - If we're an exit node, scrub the IP address to which we are exiting
9296 in the logs. Bugfix on 0.2.1.8-alpha.
9299 - On Linux, use the prctl call to re-enable core dumps when the user
9301 - New controller event NEWCONSENSUS that lists the networkstatus
9302 lines for every recommended relay. Now controllers like Torflow
9303 can keep up-to-date on which relays they should be using.
9304 - Update to the "February 26 2009" ip-to-country file.
9307 Changes in version 0.2.0.34 - 2009-02-08
9308 Tor 0.2.0.34 features several more security-related fixes. You should
9309 upgrade, especially if you run an exit relay (remote crash) or a
9310 directory authority (remote infinite loop), or you're on an older
9311 (pre-XP) or not-recently-patched Windows (remote exploit).
9313 This release marks end-of-life for Tor 0.1.2.x. Those Tor versions
9314 have many known flaws, and nobody should be using them. You should
9315 upgrade. If you're using a Linux or BSD and its packages are obsolete,
9316 stop using those packages and upgrade anyway.
9319 - Fix an infinite-loop bug on handling corrupt votes under certain
9320 circumstances. Bugfix on 0.2.0.8-alpha.
9321 - Fix a temporary DoS vulnerability that could be performed by
9322 a directory mirror. Bugfix on 0.2.0.9-alpha; reported by lark.
9323 - Avoid a potential crash on exit nodes when processing malformed
9324 input. Remote DoS opportunity. Bugfix on 0.2.0.33.
9325 - Do not accept incomplete ipv4 addresses (like 192.168.0) as valid.
9326 Spec conformance issue. Bugfix on Tor 0.0.2pre27.
9329 - Fix compilation on systems where time_t is a 64-bit integer.
9330 Patch from Matthias Drochner.
9331 - Don't consider expiring already-closed client connections. Fixes
9332 bug 893. Bugfix on 0.0.2pre20.
9335 Changes in version 0.2.1.12-alpha - 2009-02-08
9336 Tor 0.2.1.12-alpha features several more security-related fixes. You
9337 should upgrade, especially if you run an exit relay (remote crash) or
9338 a directory authority (remote infinite loop), or you're on an older
9339 (pre-XP) or not-recently-patched Windows (remote exploit). It also
9340 includes a big pile of minor bugfixes and cleanups.
9343 - Fix an infinite-loop bug on handling corrupt votes under certain
9344 circumstances. Bugfix on 0.2.0.8-alpha.
9345 - Fix a temporary DoS vulnerability that could be performed by
9346 a directory mirror. Bugfix on 0.2.0.9-alpha; reported by lark.
9347 - Avoid a potential crash on exit nodes when processing malformed
9348 input. Remote DoS opportunity. Bugfix on 0.2.1.7-alpha.
9351 - Let controllers actually ask for the "clients_seen" event for
9352 getting usage summaries on bridge relays. Bugfix on 0.2.1.10-alpha;
9353 reported by Matt Edman.
9354 - Fix a compile warning on OSX Panther. Fixes bug 913; bugfix against
9356 - Fix a bug in address parsing that was preventing bridges or hidden
9357 service targets from being at IPv6 addresses.
9358 - Solve a bug that kept hardware crypto acceleration from getting
9359 enabled when accounting was turned on. Fixes bug 907. Bugfix on
9361 - Remove a bash-ism from configure.in to build properly on non-Linux
9362 platforms. Bugfix on 0.2.1.1-alpha.
9363 - Fix code so authorities _actually_ send back X-Descriptor-Not-New
9364 headers. Bugfix on 0.2.0.10-alpha.
9365 - Don't consider expiring already-closed client connections. Fixes
9366 bug 893. Bugfix on 0.0.2pre20.
9367 - Fix another interesting corner-case of bug 891 spotted by rovv:
9368 Previously, if two hosts had different amounts of clock drift, and
9369 one of them created a new connection with just the wrong timing,
9370 the other might decide to deprecate the new connection erroneously.
9371 Bugfix on 0.1.1.13-alpha.
9372 - Resolve a very rare crash bug that could occur when the user forced
9373 a nameserver reconfiguration during the middle of a nameserver
9374 probe. Fixes bug 526. Bugfix on 0.1.2.1-alpha.
9375 - Support changing value of ServerDNSRandomizeCase during SIGHUP.
9376 Bugfix on 0.2.1.7-alpha.
9377 - If we're using bridges and our network goes away, be more willing
9378 to forgive our bridges and try again when we get an application
9379 request. Bugfix on 0.2.0.x.
9382 - Support platforms where time_t is 64 bits long. (Congratulations,
9383 NetBSD!) Patch from Matthias Drochner.
9384 - Add a 'getinfo status/clients-seen' controller command, in case
9385 controllers want to hear clients_seen events but connect late.
9388 - Disable GCC's strict alias optimization by default, to avoid the
9389 likelihood of its introducing subtle bugs whenever our code violates
9390 the letter of C99's alias rules.
9393 Changes in version 0.2.0.33 - 2009-01-21
9394 Tor 0.2.0.33 fixes a variety of bugs that were making relays less
9395 useful to users. It also finally fixes a bug where a relay or client
9396 that's been off for many days would take a long time to bootstrap.
9398 This update also fixes an important security-related bug reported by
9399 Ilja van Sprundel. You should upgrade. (We'll send out more details
9400 about the bug once people have had some time to upgrade.)
9403 - Fix a heap-corruption bug that may be remotely triggerable on
9404 some platforms. Reported by Ilja van Sprundel.
9407 - When a stream at an exit relay is in state "resolving" or
9408 "connecting" and it receives an "end" relay cell, the exit relay
9409 would silently ignore the end cell and not close the stream. If
9410 the client never closes the circuit, then the exit relay never
9411 closes the TCP connection. Bug introduced in Tor 0.1.2.1-alpha;
9413 - When sending CREATED cells back for a given circuit, use a 64-bit
9414 connection ID to find the right connection, rather than an addr:port
9415 combination. Now that we can have multiple OR connections between
9416 the same ORs, it is no longer possible to use addr:port to uniquely
9417 identify a connection.
9418 - Bridge relays that had DirPort set to 0 would stop fetching
9419 descriptors shortly after startup, and then briefly resume
9420 after a new bandwidth test and/or after publishing a new bridge
9421 descriptor. Bridge users that try to bootstrap from them would
9422 get a recent networkstatus but would get descriptors from up to
9423 18 hours earlier, meaning most of the descriptors were obsolete
9424 already. Reported by Tas; bugfix on 0.2.0.13-alpha.
9425 - Prevent bridge relays from serving their 'extrainfo' document
9426 to anybody who asks, now that extrainfo docs include potentially
9427 sensitive aggregated client geoip summaries. Bugfix on
9429 - If the cached networkstatus consensus is more than five days old,
9430 discard it rather than trying to use it. In theory it could be
9431 useful because it lists alternate directory mirrors, but in practice
9432 it just means we spend many minutes trying directory mirrors that
9433 are long gone from the network. Also discard router descriptors as
9434 we load them if they are more than five days old, since the onion
9435 key is probably wrong by now. Bugfix on 0.2.0.x. Fixes bug 887.
9438 - Do not mark smartlist_bsearch_idx() function as ATTR_PURE. This bug
9439 could make gcc generate non-functional binary search code. Bugfix
9441 - Build correctly on platforms without socklen_t.
9442 - Compile without warnings on solaris.
9443 - Avoid potential crash on internal error during signature collection.
9444 Fixes bug 864. Patch from rovv.
9445 - Correct handling of possible malformed authority signing key
9446 certificates with internal signature types. Fixes bug 880.
9447 Bugfix on 0.2.0.3-alpha.
9448 - Fix a hard-to-trigger resource leak when logging credential status.
9450 - When we can't initialize DNS because the network is down, do not
9451 automatically stop Tor from starting. Instead, we retry failed
9452 dns_init() every 10 minutes, and change the exit policy to reject
9453 *:* until one succeeds. Fixes bug 691.
9454 - Use 64 bits instead of 32 bits for connection identifiers used with
9455 the controller protocol, to greatly reduce risk of identifier reuse.
9456 - When we're choosing an exit node for a circuit, and we have
9457 no pending streams, choose a good general exit rather than one that
9458 supports "all the pending streams". Bugfix on 0.1.1.x. Fix by rovv.
9459 - Fix another case of assuming, when a specific exit is requested,
9460 that we know more than the user about what hosts it allows.
9461 Fixes one case of bug 752. Patch from rovv.
9462 - Clip the MaxCircuitDirtiness config option to a minimum of 10
9463 seconds. Warn the user if lower values are given in the
9464 configuration. Bugfix on 0.1.0.1-rc. Patch by Sebastian.
9465 - Clip the CircuitBuildTimeout to a minimum of 30 seconds. Warn the
9466 user if lower values are given in the configuration. Bugfix on
9467 0.1.1.17-rc. Patch by Sebastian.
9468 - Fix a memory leak when we decline to add a v2 rendezvous descriptor to
9469 the cache because we already had a v0 descriptor with the same ID.
9470 Bugfix on 0.2.0.18-alpha.
9471 - Fix a race condition when freeing keys shared between main thread
9472 and CPU workers that could result in a memory leak. Bugfix on
9473 0.1.0.1-rc. Fixes bug 889.
9474 - Send a valid END cell back when a client tries to connect to a
9475 nonexistent hidden service port. Bugfix on 0.1.2.15. Fixes bug
9476 840. Patch from rovv.
9477 - Check which hops rendezvous stream cells are associated with to
9478 prevent possible guess-the-streamid injection attacks from
9479 intermediate hops. Fixes another case of bug 446. Based on patch
9481 - If a broken client asks a non-exit router to connect somewhere,
9482 do not even do the DNS lookup before rejecting the connection.
9483 Fixes another case of bug 619. Patch from rovv.
9484 - When a relay gets a create cell it can't decrypt (e.g. because it's
9485 using the wrong onion key), we were dropping it and letting the
9486 client time out. Now actually answer with a destroy cell. Fixes
9487 bug 904. Bugfix on 0.0.2pre8.
9489 o Minor bugfixes (hidden services):
9490 - Do not throw away existing introduction points on SIGHUP. Bugfix on
9491 0.0.6pre1. Patch by Karsten. Fixes bug 874.
9494 - Report the case where all signatures in a detached set are rejected
9495 differently than the case where there is an error handling the
9497 - When we realize that another process has modified our cached
9498 descriptors, print out a more useful error message rather than
9499 triggering an assertion. Fixes bug 885. Patch from Karsten.
9500 - Implement the 0x20 hack to better resist DNS poisoning: set the
9501 case on outgoing DNS requests randomly, and reject responses that do
9502 not match the case correctly. This logic can be disabled with the
9503 ServerDNSRamdomizeCase setting, if you are using one of the 0.3%
9504 of servers that do not reliably preserve case in replies. See
9505 "Increased DNS Forgery Resistance through 0x20-Bit Encoding"
9507 - Check DNS replies for more matching fields to better resist DNS
9509 - Never use OpenSSL compression: it wastes RAM and CPU trying to
9510 compress cells, which are basically all encrypted, compressed, or
9514 Changes in version 0.2.1.11-alpha - 2009-01-20
9515 Tor 0.2.1.11-alpha finishes fixing the "if your Tor is off for a
9516 week it will take a long time to bootstrap again" bug. It also fixes
9517 an important security-related bug reported by Ilja van Sprundel. You
9518 should upgrade. (We'll send out more details about the bug once people
9519 have had some time to upgrade.)
9522 - Fix a heap-corruption bug that may be remotely triggerable on
9523 some platforms. Reported by Ilja van Sprundel.
9526 - Discard router descriptors as we load them if they are more than
9527 five days old. Otherwise if Tor is off for a long time and then
9528 starts with cached descriptors, it will try to use the onion
9529 keys in those obsolete descriptors when building circuits. Bugfix
9530 on 0.2.0.x. Fixes bug 887.
9533 - Try to make sure that the version of Libevent we're running with
9534 is binary-compatible with the one we built with. May address bug
9536 - Make setting ServerDNSRandomizeCase to 0 actually work. Bugfix
9537 for bug 905. Bugfix on 0.2.1.7-alpha.
9538 - Add a new --enable-local-appdata configuration switch to change
9539 the default location of the datadir on win32 from APPDATA to
9540 LOCAL_APPDATA. In the future, we should migrate to LOCAL_APPDATA
9541 entirely. Patch from coderman.
9544 - Make outbound DNS packets respect the OutboundBindAddress setting.
9545 Fixes the bug part of bug 798. Bugfix on 0.1.2.2-alpha.
9546 - When our circuit fails at the first hop (e.g. we get a destroy
9547 cell back), avoid using that OR connection anymore, and also
9548 tell all the one-hop directory requests waiting for it that they
9549 should fail. Bugfix on 0.2.1.3-alpha.
9550 - In the torify(1) manpage, mention that tsocks will leak your
9554 Changes in version 0.2.1.10-alpha - 2009-01-06
9555 Tor 0.2.1.10-alpha fixes two major bugs in bridge relays (one that
9556 would make the bridge relay not so useful if it had DirPort set to 0,
9557 and one that could let an attacker learn a little bit of information
9558 about the bridge's users), and a bug that would cause your Tor relay
9559 to ignore a circuit create request it can't decrypt (rather than reply
9560 with an error). It also fixes a wide variety of other bugs.
9563 - If the cached networkstatus consensus is more than five days old,
9564 discard it rather than trying to use it. In theory it could
9565 be useful because it lists alternate directory mirrors, but in
9566 practice it just means we spend many minutes trying directory
9567 mirrors that are long gone from the network. Helps bug 887 a bit;
9569 - Bridge relays that had DirPort set to 0 would stop fetching
9570 descriptors shortly after startup, and then briefly resume
9571 after a new bandwidth test and/or after publishing a new bridge
9572 descriptor. Bridge users that try to bootstrap from them would
9573 get a recent networkstatus but would get descriptors from up to
9574 18 hours earlier, meaning most of the descriptors were obsolete
9575 already. Reported by Tas; bugfix on 0.2.0.13-alpha.
9576 - Prevent bridge relays from serving their 'extrainfo' document
9577 to anybody who asks, now that extrainfo docs include potentially
9578 sensitive aggregated client geoip summaries. Bugfix on
9582 - New controller event "clients_seen" to report a geoip-based summary
9583 of which countries we've seen clients from recently. Now controllers
9584 like Vidalia can show bridge operators that they're actually making
9586 - Build correctly against versions of OpenSSL 0.9.8 or later built
9587 without support for deprecated functions.
9588 - Update to the "December 19 2008" ip-to-country file.
9590 o Minor bugfixes (on 0.2.0.x):
9591 - Authorities now vote for the Stable flag for any router whose
9592 weighted MTBF is at least 5 days, regardless of the mean MTBF.
9593 - Do not remove routers as too old if we do not have any consensus
9594 document. Bugfix on 0.2.0.7-alpha.
9595 - Do not accept incomplete ipv4 addresses (like 192.168.0) as valid.
9596 Spec conformance issue. Bugfix on Tor 0.0.2pre27.
9597 - When an exit relay resolves a stream address to a local IP address,
9598 do not just keep retrying that same exit relay over and
9599 over. Instead, just close the stream. Addresses bug 872. Bugfix
9600 on 0.2.0.32. Patch from rovv.
9601 - If a hidden service sends us an END cell, do not consider
9602 retrying the connection; just close it. Patch from rovv.
9603 - When we made bridge authorities stop serving bridge descriptors over
9604 unencrypted links, we also broke DirPort reachability testing for
9605 bridges. So bridges with a non-zero DirPort were printing spurious
9606 warns to their logs. Bugfix on 0.2.0.16-alpha. Fixes bug 709.
9607 - When a relay gets a create cell it can't decrypt (e.g. because it's
9608 using the wrong onion key), we were dropping it and letting the
9609 client time out. Now actually answer with a destroy cell. Fixes
9610 bug 904. Bugfix on 0.0.2pre8.
9611 - Squeeze 2-5% out of client performance (according to oprofile) by
9612 improving the implementation of some policy-manipulation functions.
9614 o Minor bugfixes (on 0.2.1.x):
9615 - Make get_interface_address() function work properly again; stop
9616 guessing the wrong parts of our address as our address.
9617 - Do not cannibalize a circuit if we're out of RELAY_EARLY cells to
9618 send on that circuit. Otherwise we might violate the proposal-110
9619 limit. Bugfix on 0.2.1.3-alpha. Partial fix for bug 878. Diagnosis
9621 - When we're sending non-EXTEND cells to the first hop in a circuit,
9622 for example to use an encrypted directory connection, we don't need
9623 to use RELAY_EARLY cells: the first hop knows what kind of cell
9624 it is, and nobody else can even see the cell type. Conserving
9625 RELAY_EARLY cells makes it easier to cannibalize circuits like
9627 - Stop logging nameserver addresses in reverse order.
9628 - If we are retrying a directory download slowly over and over, do
9629 not automatically give up after the 254th failure. Bugfix on
9631 - Resume reporting accurate "stream end" reasons to the local control
9632 port. They were lost in the changes for Proposal 148. Bugfix on
9635 o Deprecated and removed features:
9636 - The old "tor --version --version" command, which would print out
9637 the subversion "Id" of most of the source files, is now removed. It
9638 turned out to be less useful than we'd expected, and harder to
9641 o Code simplifications and refactoring:
9642 - Change our header file guard macros to be less likely to conflict
9643 with system headers. Adam Langley noticed that we were conflicting
9644 with log.h on Android.
9645 - Tool-assisted documentation cleanup. Nearly every function or
9646 static variable in Tor should have its own documentation now.
9649 Changes in version 0.2.1.9-alpha - 2008-12-25
9650 Tor 0.2.1.9-alpha fixes many more bugs, some of them security-related.
9652 o New directory authorities:
9653 - gabelmoo (the authority run by Karsten Loesing) now has a new
9657 - Never use a connection with a mismatched address to extend a
9658 circuit, unless that connection is canonical. A canonical
9659 connection is one whose address is authenticated by the router's
9660 identity key, either in a NETINFO cell or in a router descriptor.
9661 - Avoid a possible memory corruption bug when receiving hidden service
9662 descriptors. Bugfix on 0.2.1.6-alpha.
9665 - Fix a logic error that would automatically reject all but the first
9666 configured DNS server. Bugfix on 0.2.1.5-alpha. Possible fix for
9667 part of bug 813/868. Bug spotted by coderman.
9668 - When a stream at an exit relay is in state "resolving" or
9669 "connecting" and it receives an "end" relay cell, the exit relay
9670 would silently ignore the end cell and not close the stream. If
9671 the client never closes the circuit, then the exit relay never
9672 closes the TCP connection. Bug introduced in 0.1.2.1-alpha;
9674 - When we can't initialize DNS because the network is down, do not
9675 automatically stop Tor from starting. Instead, retry failed
9676 dns_init() every 10 minutes, and change the exit policy to reject
9677 *:* until one succeeds. Fixes bug 691.
9680 - Give a better error message when an overzealous init script says
9681 "sudo -u username tor --user username". Makes Bug 882 easier for
9683 - When a directory authority gives us a new guess for our IP address,
9684 log which authority we used. Hopefully this will help us debug
9685 the recent complaints about bad IP address guesses.
9686 - Detect svn revision properly when we're using git-svn.
9687 - Try not to open more than one descriptor-downloading connection
9688 to an authority at once. This should reduce load on directory
9689 authorities. Fixes bug 366.
9690 - Add cross-certification to newly generated certificates, so that
9691 a signing key is enough information to look up a certificate.
9692 Partial implementation of proposal 157.
9693 - Start serving certificates by <identity digest, signing key digest>
9694 pairs. Partial implementation of proposal 157.
9695 - Clients now never report any stream end reason except 'MISC'.
9696 Implements proposal 148.
9697 - On platforms with a maximum syslog string length, truncate syslog
9698 messages to that length ourselves, rather than relying on the
9699 system to do it for us.
9700 - Optimize out calls to time(NULL) that occur for every IO operation,
9701 or for every cell. On systems where time() is a slow syscall,
9702 this fix will be slightly helpful.
9703 - Exit servers can now answer resolve requests for ip6.arpa addresses.
9704 - When we download a descriptor that we then immediately (as
9705 a directory authority) reject, do not retry downloading it right
9706 away. Should save some bandwidth on authorities. Fix for bug
9707 888. Patch by Sebastian Hahn.
9708 - When a download gets us zero good descriptors, do not notify
9709 Tor that new directory information has arrived.
9710 - Avoid some nasty corner cases in the logic for marking connections
9711 as too old or obsolete or noncanonical for circuits. Partial
9714 o Minor features (controller):
9715 - New CONSENSUS_ARRIVED event to note when a new consensus has
9716 been fetched and validated.
9717 - When we realize that another process has modified our cached
9718 descriptors file, print out a more useful error message rather
9719 than triggering an assertion. Fixes bug 885. Patch from Karsten.
9720 - Add an internal-use-only __ReloadTorrcOnSIGHUP option for
9721 controllers to prevent SIGHUP from reloading the
9722 configuration. Fixes bug 856.
9725 - Resume using the correct "REASON=" stream when telling the
9726 controller why we closed a stream. Bugfix in 0.2.1.1-alpha.
9727 - When a canonical connection appears later in our internal list
9728 than a noncanonical one for a given OR ID, always use the
9729 canonical one. Bugfix on 0.2.0.12-alpha. Fixes bug 805.
9731 - Clip the MaxCircuitDirtiness config option to a minimum of 10
9732 seconds. Warn the user if lower values are given in the
9733 configuration. Bugfix on 0.1.0.1-rc. Patch by Sebastian.
9734 - Clip the CircuitBuildTimeout to a minimum of 30 seconds. Warn the
9735 user if lower values are given in the configuration. Bugfix on
9736 0.1.1.17-rc. Patch by Sebastian.
9737 - Fix a race condition when freeing keys shared between main thread
9738 and CPU workers that could result in a memory leak. Bugfix on
9739 0.1.0.1-rc. Fixes bug 889.
9741 o Minor bugfixes (hidden services):
9742 - Do not throw away existing introduction points on SIGHUP (bugfix on
9743 0.0.6pre1); also, do not stall hidden services because we're
9744 throwing away introduction points; bugfix on 0.2.1.7-alpha. Spotted
9745 by John Brooks. Patch by Karsten. Fixes bug 874.
9746 - Fix a memory leak when we decline to add a v2 rendezvous
9747 descriptor to the cache because we already had a v0 descriptor
9748 with the same ID. Bugfix on 0.2.0.18-alpha.
9750 o Deprecated and removed features:
9751 - RedirectExits has been removed. It was deprecated since
9753 - Finally remove deprecated "EXTENDED_FORMAT" controller feature. It
9754 has been called EXTENDED_EVENTS since 0.1.2.4-alpha.
9755 - Cell pools are now always enabled; --disable-cell-pools is ignored.
9757 o Code simplifications and refactoring:
9758 - Rename the confusing or_is_obsolete field to the more appropriate
9759 is_bad_for_new_circs, and move it to or_connection_t where it
9761 - Move edge-only flags from connection_t to edge_connection_t: not
9762 only is this better coding, but on machines of plausible alignment,
9763 it should save 4-8 bytes per connection_t. "Every little bit helps."
9764 - Rename ServerDNSAllowBrokenResolvConf to ServerDNSAllowBrokenConfig
9765 for consistency; keep old option working for backward compatibility.
9766 - Simplify the code for finding connections to use for a circuit.
9769 Changes in version 0.2.1.8-alpha - 2008-12-08
9770 Tor 0.2.1.8-alpha fixes some crash bugs in earlier alpha releases,
9771 builds better on unusual platforms like Solaris and old OS X, and
9772 fixes a variety of other issues.
9775 - New DirPortFrontPage option that takes an html file and publishes
9776 it as "/" on the DirPort. Now relay operators can provide a
9777 disclaimer without needing to set up a separate webserver. There's
9778 a sample disclaimer in contrib/tor-exit-notice.html.
9781 - When the client is choosing entry guards, now it selects at most
9782 one guard from a given relay family. Otherwise we could end up with
9783 all of our entry points into the network run by the same operator.
9784 Suggested by Camilo Viecco. Fix on 0.1.1.11-alpha.
9787 - Fix a DOS opportunity during the voting signature collection process
9788 at directory authorities. Spotted by rovv. Bugfix on 0.2.0.x.
9789 - Fix a possible segfault when establishing an exit connection. Bugfix
9793 - Get file locking working on win32. Bugfix on 0.2.1.6-alpha. Fixes
9795 - Made Tor a little less aggressive about deleting expired
9796 certificates. Partial fix for bug 854.
9797 - Stop doing unaligned memory access that generated bus errors on
9798 sparc64. Bugfix on 0.2.0.10-alpha. Fix for bug 862.
9799 - Fix a crash bug when changing EntryNodes from the controller. Bugfix
9800 on 0.2.1.6-alpha. Fix for bug 867. Patched by Sebastian.
9801 - Make USR2 log-level switch take effect immediately. Bugfix on
9803 - If one win32 nameserver fails to get added, continue adding the
9804 rest, and don't automatically fail.
9805 - Use fcntl() for locking when flock() is not available. Should fix
9806 compilation on Solaris. Should fix Bug 873. Bugfix on 0.2.1.6-alpha.
9807 - Do not mark smartlist_bsearch_idx() function as ATTR_PURE. This bug
9808 could make gcc generate non-functional binary search code. Bugfix
9810 - Build correctly on platforms without socklen_t.
9811 - Avoid potential crash on internal error during signature collection.
9812 Fixes bug 864. Patch from rovv.
9813 - Do not use C's stdio library for writing to log files. This will
9814 improve logging performance by a minute amount, and will stop
9815 leaking fds when our disk is full. Fixes bug 861.
9816 - Stop erroneous use of O_APPEND in cases where we did not in fact
9817 want to re-seek to the end of a file before every last write().
9818 - Correct handling of possible malformed authority signing key
9819 certificates with internal signature types. Fixes bug 880. Bugfix
9821 - Fix a hard-to-trigger resource leak when logging credential status.
9825 - Directory mirrors no longer fetch the v1 directory or
9826 running-routers files. They are obsolete, and nobody asks for them
9827 anymore. This is the first step to making v1 authorities obsolete.
9829 o Minor features (controller):
9830 - Return circuit purposes in response to GETINFO circuit-status. Fixes
9834 Changes in version 0.2.0.32 - 2008-11-20
9835 Tor 0.2.0.32 fixes a major security problem in Debian and Ubuntu
9836 packages (and maybe other packages) noticed by Theo de Raadt, fixes
9837 a smaller security flaw that might allow an attacker to access local
9838 services, further improves hidden service performance, and fixes a
9839 variety of other issues.
9842 - The "User" and "Group" config options did not clear the
9843 supplementary group entries for the Tor process. The "User" option
9844 is now more robust, and we now set the groups to the specified
9845 user's primary group. The "Group" option is now ignored. For more
9846 detailed logging on credential switching, set CREDENTIAL_LOG_LEVEL
9847 in common/compat.c to LOG_NOTICE or higher. Patch by Jacob Appelbaum
9848 and Steven Murdoch. Bugfix on 0.0.2pre14. Fixes bug 848 and 857.
9849 - The "ClientDNSRejectInternalAddresses" config option wasn't being
9850 consistently obeyed: if an exit relay refuses a stream because its
9851 exit policy doesn't allow it, we would remember what IP address
9852 the relay said the destination address resolves to, even if it's
9853 an internal IP address. Bugfix on 0.2.0.7-alpha; patch by rovv.
9856 - Fix a DOS opportunity during the voting signature collection process
9857 at directory authorities. Spotted by rovv. Bugfix on 0.2.0.x.
9859 o Major bugfixes (hidden services):
9860 - When fetching v0 and v2 rendezvous service descriptors in parallel,
9861 we were failing the whole hidden service request when the v0
9862 descriptor fetch fails, even if the v2 fetch is still pending and
9863 might succeed. Similarly, if the last v2 fetch fails, we were
9864 failing the whole hidden service request even if a v0 fetch is
9865 still pending. Fixes bug 814. Bugfix on 0.2.0.10-alpha.
9866 - When extending a circuit to a hidden service directory to upload a
9867 rendezvous descriptor using a BEGIN_DIR cell, almost 1/6 of all
9868 requests failed, because the router descriptor has not been
9869 downloaded yet. In these cases, do not attempt to upload the
9870 rendezvous descriptor, but wait until the router descriptor is
9871 downloaded and retry. Likewise, do not attempt to fetch a rendezvous
9872 descriptor from a hidden service directory for which the router
9873 descriptor has not yet been downloaded. Fixes bug 767. Bugfix
9877 - Fix several infrequent memory leaks spotted by Coverity.
9878 - When testing for libevent functions, set the LDFLAGS variable
9879 correctly. Found by Riastradh.
9880 - Avoid a bug where the FastFirstHopPK 0 option would keep Tor from
9881 bootstrapping with tunneled directory connections. Bugfix on
9882 0.1.2.5-alpha. Fixes bug 797. Found by Erwin Lam.
9883 - When asked to connect to A.B.exit:80, if we don't know the IP for A
9884 and we know that server B rejects most-but-not all connections to
9885 port 80, we would previously reject the connection. Now, we assume
9886 the user knows what they were asking for. Fixes bug 752. Bugfix
9887 on 0.0.9rc5. Diagnosed by BarkerJr.
9888 - If we overrun our per-second write limits a little, count this as
9889 having used up our write allocation for the second, and choke
9890 outgoing directory writes. Previously, we had only counted this when
9891 we had met our limits precisely. Fixes bug 824. Patch from by rovv.
9892 Bugfix on 0.2.0.x (??).
9893 - Remove the old v2 directory authority 'lefkada' from the default
9894 list. It has been gone for many months.
9895 - Stop doing unaligned memory access that generated bus errors on
9896 sparc64. Bugfix on 0.2.0.10-alpha. Fixes bug 862.
9897 - Make USR2 log-level switch take effect immediately. Bugfix on
9900 o Minor bugfixes (controller):
9901 - Make DNS resolved events into "CLOSED", not "FAILED". Bugfix on
9902 0.1.2.5-alpha. Fix by Robert Hogan. Resolves bug 807.
9905 Changes in version 0.2.1.7-alpha - 2008-11-08
9906 Tor 0.2.1.7-alpha fixes a major security problem in Debian and Ubuntu
9907 packages (and maybe other packages) noticed by Theo de Raadt, fixes
9908 a smaller security flaw that might allow an attacker to access local
9909 services, adds better defense against DNS poisoning attacks on exit
9910 relays, further improves hidden service performance, and fixes a
9911 variety of other issues.
9914 - The "ClientDNSRejectInternalAddresses" config option wasn't being
9915 consistently obeyed: if an exit relay refuses a stream because its
9916 exit policy doesn't allow it, we would remember what IP address
9917 the relay said the destination address resolves to, even if it's
9918 an internal IP address. Bugfix on 0.2.0.7-alpha; patch by rovv.
9919 - The "User" and "Group" config options did not clear the
9920 supplementary group entries for the Tor process. The "User" option
9921 is now more robust, and we now set the groups to the specified
9922 user's primary group. The "Group" option is now ignored. For more
9923 detailed logging on credential switching, set CREDENTIAL_LOG_LEVEL
9924 in common/compat.c to LOG_NOTICE or higher. Patch by Jacob Appelbaum
9925 and Steven Murdoch. Bugfix on 0.0.2pre14. Fixes bug 848.
9926 - Do not use or believe expired v3 authority certificates. Patch
9927 from Karsten. Bugfix in 0.2.0.x. Fixes bug 851.
9930 - Now NodeFamily and MyFamily config options allow spaces in
9931 identity fingerprints, so it's easier to paste them in.
9932 Suggested by Lucky Green.
9933 - Implement the 0x20 hack to better resist DNS poisoning: set the
9934 case on outgoing DNS requests randomly, and reject responses that do
9935 not match the case correctly. This logic can be disabled with the
9936 ServerDNSRandomizeCase setting, if you are using one of the 0.3%
9937 of servers that do not reliably preserve case in replies. See
9938 "Increased DNS Forgery Resistance through 0x20-Bit Encoding"
9940 - Preserve case in replies to DNSPort requests in order to support
9941 the 0x20 hack for resisting DNS poisoning attacks.
9943 o Hidden service performance improvements:
9944 - When the client launches an introduction circuit, retry with a
9945 new circuit after 30 seconds rather than 60 seconds.
9946 - Launch a second client-side introduction circuit in parallel
9947 after a delay of 15 seconds (based on work by Christian Wilms).
9948 - Hidden services start out building five intro circuits rather
9949 than three, and when the first three finish they publish a service
9950 descriptor using those. Now we publish our service descriptor much
9951 faster after restart.
9954 - Minor fix in the warning messages when you're having problems
9955 bootstrapping; also, be more forgiving of bootstrap problems when
9956 we're still making incremental progress on a given bootstrap phase.
9957 - When we're choosing an exit node for a circuit, and we have
9958 no pending streams, choose a good general exit rather than one that
9959 supports "all the pending streams". Bugfix on 0.1.1.x. Fix by rovv.
9960 - Send a valid END cell back when a client tries to connect to a
9961 nonexistent hidden service port. Bugfix on 0.1.2.15. Fixes bug
9962 840. Patch from rovv.
9963 - If a broken client asks a non-exit router to connect somewhere,
9964 do not even do the DNS lookup before rejecting the connection.
9965 Fixes another case of bug 619. Patch from rovv.
9966 - Fix another case of assuming, when a specific exit is requested,
9967 that we know more than the user about what hosts it allows.
9968 Fixes another case of bug 752. Patch from rovv.
9969 - Check which hops rendezvous stream cells are associated with to
9970 prevent possible guess-the-streamid injection attacks from
9971 intermediate hops. Fixes another case of bug 446. Based on patch
9973 - Avoid using a negative right-shift when comparing 32-bit
9974 addresses. Possible fix for bug 845 and bug 811.
9975 - Make the assert_circuit_ok() function work correctly on circuits that
9976 have already been marked for close.
9977 - Fix read-off-the-end-of-string error in unit tests when decoding
9978 introduction points.
9979 - Fix uninitialized size field for memory area allocation: may improve
9980 memory performance during directory parsing.
9981 - Treat duplicate certificate fetches as failures, so that we do
9982 not try to re-fetch an expired certificate over and over and over.
9983 - Do not say we're fetching a certificate when we'll in fact skip it
9984 because of a pending download.
9987 Changes in version 0.2.1.6-alpha - 2008-09-30
9988 Tor 0.2.1.6-alpha further improves performance and robustness of
9989 hidden services, starts work on supporting per-country relay selection,
9990 and fixes a variety of smaller issues.
9993 - Implement proposal 121: make it possible to build hidden services
9994 that only certain clients are allowed to connect to. This is
9995 enforced at several points, so that unauthorized clients are unable
9996 to send INTRODUCE cells to the service, or even (depending on the
9997 type of authentication) to learn introduction points. This feature
9998 raises the bar for certain kinds of active attacks against hidden
9999 services. Code by Karsten Loesing.
10000 - Relays now store and serve v2 hidden service descriptors by default,
10001 i.e., the new default value for HidServDirectoryV2 is 1. This is
10002 the last step in proposal 114, which aims to make hidden service
10003 lookups more reliable.
10004 - Start work to allow node restrictions to include country codes. The
10005 syntax to exclude nodes in a country with country code XX is
10006 "ExcludeNodes {XX}". Patch from Robert Hogan. It still needs some
10007 refinement to decide what config options should take priority if
10008 you ask to both use a particular node and exclude it.
10009 - Allow ExitNodes list to include IP ranges and country codes, just
10010 like the Exclude*Nodes lists. Patch from Robert Hogan.
10013 - Fix a bug when parsing ports in tor_addr_port_parse() that caused
10014 Tor to fail to start if you had it configured to use a bridge
10015 relay. Fixes bug 809. Bugfix on 0.2.1.5-alpha.
10016 - When extending a circuit to a hidden service directory to upload a
10017 rendezvous descriptor using a BEGIN_DIR cell, almost 1/6 of all
10018 requests failed, because the router descriptor had not been
10019 downloaded yet. In these cases, we now wait until the router
10020 descriptor is downloaded, and then retry. Likewise, clients
10021 now skip over a hidden service directory if they don't yet have
10022 its router descriptor, rather than futilely requesting it and
10023 putting mysterious complaints in the logs. Fixes bug 767. Bugfix
10025 - When fetching v0 and v2 rendezvous service descriptors in parallel,
10026 we were failing the whole hidden service request when the v0
10027 descriptor fetch fails, even if the v2 fetch is still pending and
10028 might succeed. Similarly, if the last v2 fetch fails, we were
10029 failing the whole hidden service request even if a v0 fetch is
10030 still pending. Fixes bug 814. Bugfix on 0.2.0.10-alpha.
10031 - DNS replies need to have names matching their requests, but
10032 these names should be in the questions section, not necessarily
10033 in the answers section. Fixes bug 823. Bugfix on 0.2.1.5-alpha.
10036 - Update to the "September 1 2008" ip-to-country file.
10037 - Allow ports 465 and 587 in the default exit policy again. We had
10038 rejected them in 0.1.0.15, because back in 2005 they were commonly
10039 misconfigured and ended up as spam targets. We hear they are better
10040 locked down these days.
10041 - Use a lockfile to make sure that two Tor processes are not
10042 simultaneously running with the same datadir.
10043 - Serve the latest v3 networkstatus consensus via the control
10044 port. Use "getinfo dir/status-vote/current/consensus" to fetch it.
10045 - Better logging about stability/reliability calculations on directory
10047 - Drop the requirement to have an open dir port for storing and
10048 serving v2 hidden service descriptors.
10049 - Directory authorities now serve a /tor/dbg-stability.txt URL to
10050 help debug WFU and MTBF calculations.
10051 - Implement most of Proposal 152: allow specialized servers to permit
10052 single-hop circuits, and clients to use those servers to build
10053 single-hop circuits when using a specialized controller. Patch
10054 from Josh Albrecht. Resolves feature request 768.
10055 - Add a -p option to tor-resolve for specifying the SOCKS port: some
10056 people find host:port too confusing.
10057 - Make TrackHostExit mappings expire a while after their last use, not
10058 after their creation. Patch from Robert Hogan.
10059 - Provide circuit purposes along with circuit events to the controller.
10062 - Fix compile on OpenBSD 4.4-current. Bugfix on 0.2.1.5-alpha.
10064 - Fixed some memory leaks -- some quite frequent, some almost
10065 impossible to trigger -- based on results from Coverity.
10066 - When testing for libevent functions, set the LDFLAGS variable
10067 correctly. Found by Riastradh.
10068 - Fix an assertion bug in parsing policy-related options; possible fix
10070 - Catch and report a few more bootstrapping failure cases when Tor
10071 fails to establish a TCP connection. Cleanup on 0.2.1.x.
10072 - Avoid a bug where the FastFirstHopPK 0 option would keep Tor from
10073 bootstrapping with tunneled directory connections. Bugfix on
10074 0.1.2.5-alpha. Fixes bug 797. Found by Erwin Lam.
10075 - When asked to connect to A.B.exit:80, if we don't know the IP for A
10076 and we know that server B rejects most-but-not all connections to
10077 port 80, we would previously reject the connection. Now, we assume
10078 the user knows what they were asking for. Fixes bug 752. Bugfix
10079 on 0.0.9rc5. Diagnosed by BarkerJr.
10080 - If we are not using BEGIN_DIR cells, don't attempt to contact hidden
10081 service directories if they have no advertised dir port. Bugfix
10083 - If we overrun our per-second write limits a little, count this as
10084 having used up our write allocation for the second, and choke
10085 outgoing directory writes. Previously, we had only counted this when
10086 we had met our limits precisely. Fixes bug 824. Patch by rovv.
10087 Bugfix on 0.2.0.x (??).
10088 - Avoid a "0 divided by 0" calculation when calculating router uptime
10089 at directory authorities. Bugfix on 0.2.0.8-alpha.
10090 - Make DNS resolved controller events into "CLOSED", not
10091 "FAILED". Bugfix on 0.1.2.5-alpha. Fix by Robert Hogan. Resolves
10093 - Fix a bug where an unreachable relay would establish enough
10094 reachability testing circuits to do a bandwidth test -- if
10095 we already have a connection to the middle hop of the testing
10096 circuit, then it could establish the last hop by using the existing
10097 connection. Bugfix on 0.1.2.2-alpha, exposed when we made testing
10098 circuits no longer use entry guards in 0.2.1.3-alpha.
10099 - If we have correct permissions on $datadir, we complain to stdout
10100 and fail to start. But dangerous permissions on
10101 $datadir/cached-status/ would cause us to open a log and complain
10102 there. Now complain to stdout and fail to start in both cases. Fixes
10103 bug 820, reported by seeess.
10104 - Remove the old v2 directory authority 'lefkada' from the default
10105 list. It has been gone for many months.
10107 o Code simplifications and refactoring:
10108 - Revise the connection_new functions so that a more typesafe variant
10109 exists. This will work better with Coverity, and let us find any
10110 actual mistakes we're making here.
10111 - Refactor unit testing logic so that dmalloc can be used sensibly
10112 with unit tests to check for memory leaks.
10113 - Move all hidden-service related fields from connection and circuit
10114 structure to substructures: this way they won't eat so much memory.
10117 Changes in version 0.2.0.31 - 2008-09-03
10118 Tor 0.2.0.31 addresses two potential anonymity issues, starts to fix
10119 a big bug we're seeing where in rare cases traffic from one Tor stream
10120 gets mixed into another stream, and fixes a variety of smaller issues.
10123 - Make sure that two circuits can never exist on the same connection
10124 with the same circuit ID, even if one is marked for close. This
10125 is conceivably a bugfix for bug 779. Bugfix on 0.1.0.4-rc.
10126 - Relays now reject risky extend cells: if the extend cell includes
10127 a digest of all zeroes, or asks to extend back to the relay that
10128 sent the extend cell, tear down the circuit. Ideas suggested
10130 - If not enough of our entry guards are available so we add a new
10131 one, we might use the new one even if it overlapped with the
10132 current circuit's exit relay (or its family). Anonymity bugfix
10133 pointed out by rovv.
10136 - Recover 3-7 bytes that were wasted per memory chunk. Fixes bug
10137 794; bug spotted by rovv. Bugfix on 0.2.0.1-alpha.
10138 - Correctly detect the presence of the linux/netfilter_ipv4.h header
10139 when building against recent kernels. Bugfix on 0.1.2.1-alpha.
10140 - Pick size of default geoip filename string correctly on windows.
10141 Fixes bug 806. Bugfix on 0.2.0.30.
10142 - Make the autoconf script accept the obsolete --with-ssl-dir
10143 option as an alias for the actually-working --with-openssl-dir
10144 option. Fix the help documentation to recommend --with-openssl-dir.
10145 Based on a patch by "Dave". Bugfix on 0.2.0.1-alpha.
10146 - When using the TransPort option on OpenBSD, and using the User
10147 option to change UID and drop privileges, make sure to open
10148 /dev/pf before dropping privileges. Fixes bug 782. Patch from
10149 Christopher Davis. Bugfix on 0.1.2.1-alpha.
10150 - Try to attach connections immediately upon receiving a RENDEZVOUS2
10151 or RENDEZVOUS_ESTABLISHED cell. This can save a second or two
10152 on the client side when connecting to a hidden service. Bugfix
10153 on 0.0.6pre1. Found and fixed by Christian Wilms; resolves bug 743.
10154 - When closing an application-side connection because its circuit is
10155 getting torn down, generate the stream event correctly. Bugfix on
10156 0.1.2.x. Anonymous patch.
10159 Changes in version 0.2.1.5-alpha - 2008-08-31
10160 Tor 0.2.1.5-alpha moves us closer to handling IPv6 destinations, puts
10161 in a lot of the infrastructure for adding authorization to hidden
10162 services, lays the groundwork for having clients read their load
10163 balancing information out of the networkstatus consensus rather than
10164 the individual router descriptors, addresses two potential anonymity
10165 issues, and fixes a variety of smaller issues.
10168 - Convert many internal address representations to optionally hold
10170 - Generate and accept IPv6 addresses in many protocol elements.
10171 - Make resolver code handle nameservers located at ipv6 addresses.
10172 - Begin implementation of proposal 121 ("Client authorization for
10173 hidden services"): configure hidden services with client
10174 authorization, publish descriptors for them, and configure
10175 authorization data for hidden services at clients. The next
10176 step is to actually access hidden services that perform client
10178 - More progress toward proposal 141: Network status consensus
10179 documents and votes now contain bandwidth information for each
10180 router and a summary of that router's exit policy. Eventually this
10181 will be used by clients so that they do not have to download every
10182 known descriptor before building circuits.
10184 o Major bugfixes (on 0.2.0.x and before):
10185 - When sending CREATED cells back for a given circuit, use a 64-bit
10186 connection ID to find the right connection, rather than an addr:port
10187 combination. Now that we can have multiple OR connections between
10188 the same ORs, it is no longer possible to use addr:port to uniquely
10189 identify a connection.
10190 - Relays now reject risky extend cells: if the extend cell includes
10191 a digest of all zeroes, or asks to extend back to the relay that
10192 sent the extend cell, tear down the circuit. Ideas suggested
10194 - If not enough of our entry guards are available so we add a new
10195 one, we might use the new one even if it overlapped with the
10196 current circuit's exit relay (or its family). Anonymity bugfix
10197 pointed out by rovv.
10200 - Recover 3-7 bytes that were wasted per memory chunk. Fixes bug
10201 794; bug spotted by rovv. Bugfix on 0.2.0.1-alpha.
10202 - When using the TransPort option on OpenBSD, and using the User
10203 option to change UID and drop privileges, make sure to open /dev/pf
10204 before dropping privileges. Fixes bug 782. Patch from Christopher
10205 Davis. Bugfix on 0.1.2.1-alpha.
10206 - Correctly detect the presence of the linux/netfilter_ipv4.h header
10207 when building against recent kernels. Bugfix on 0.1.2.1-alpha.
10208 - Add a missing safe_str() call for a debug log message.
10209 - Use 64 bits instead of 32 bits for connection identifiers used with
10210 the controller protocol, to greatly reduce risk of identifier reuse.
10211 - Make the autoconf script accept the obsolete --with-ssl-dir
10212 option as an alias for the actually-working --with-openssl-dir
10213 option. Fix the help documentation to recommend --with-openssl-dir.
10214 Based on a patch by "Dave". Bugfix on 0.2.0.1-alpha.
10217 - Rate-limit too-many-sockets messages: when they happen, they happen
10218 a lot. Resolves bug 748.
10219 - Resist DNS poisoning a little better by making sure that names in
10220 answer sections match.
10221 - Print the SOCKS5 error message string as well as the error code
10222 when a tor-resolve request fails. Patch from Jacob.
10225 Changes in version 0.2.1.4-alpha - 2008-08-04
10226 Tor 0.2.1.4-alpha fixes a pair of crash bugs in 0.2.1.3-alpha.
10229 - The address part of exit policies was not correctly written
10230 to router descriptors. This generated router descriptors that failed
10231 their self-checks. Noticed by phobos, fixed by Karsten. Bugfix
10233 - Tor triggered a false assert when extending a circuit to a relay
10234 but we already have a connection open to that relay. Noticed by
10235 phobos, fixed by Karsten. Bugfix on 0.2.1.3-alpha.
10238 - Fix a hidden service logging bug: in some edge cases, the router
10239 descriptor of a previously picked introduction point becomes
10240 obsolete and we need to give up on it rather than continually
10241 complaining that it has become obsolete. Observed by xiando. Bugfix
10244 o Removed features:
10245 - Take out the TestVia config option, since it was a workaround for
10246 a bug that was fixed in Tor 0.1.1.21.
10249 Changes in version 0.2.1.3-alpha - 2008-08-03
10250 Tor 0.2.1.3-alpha implements most of the pieces to prevent
10251 infinite-length circuit attacks (see proposal 110); fixes a bug that
10252 might cause exit relays to corrupt streams they send back; allows
10253 address patterns (e.g. 255.128.0.0/16) to appear in ExcludeNodes and
10254 ExcludeExitNodes config options; and fixes a big pile of bugs.
10256 o Bootstrapping bugfixes (on 0.2.1.x-alpha):
10257 - Send a bootstrap problem "warn" event on the first problem if the
10258 reason is NO_ROUTE (that is, our network is down).
10261 - Implement most of proposal 110: The first K cells to be sent
10262 along a circuit are marked as special "early" cells; only K "early"
10263 cells will be allowed. Once this code is universal, we can block
10264 certain kinds of DOS attack by requiring that EXTEND commands must
10265 be sent using an "early" cell.
10268 - Try to attach connections immediately upon receiving a RENDEZVOUS2
10269 or RENDEZVOUS_ESTABLISHED cell. This can save a second or two
10270 on the client side when connecting to a hidden service. Bugfix
10271 on 0.0.6pre1. Found and fixed by Christian Wilms; resolves bug 743.
10272 - Ensure that two circuits can never exist on the same connection
10273 with the same circuit ID, even if one is marked for close. This
10274 is conceivably a bugfix for bug 779; fixes a bug on 0.1.0.4-rc.
10277 - When relays do their initial bandwidth measurement, don't limit
10278 to just our entry guards for the test circuits. Otherwise we tend
10279 to have multiple test circuits going through a single entry guard,
10280 which makes our bandwidth test less accurate. Fixes part of bug 654;
10281 patch contributed by Josh Albrecht.
10282 - Add an ExcludeExitNodes option so users can list a set of nodes
10283 that should be be excluded from the exit node position, but
10284 allowed elsewhere. Implements proposal 151.
10285 - Allow address patterns (e.g., 255.128.0.0/16) to appear in
10286 ExcludeNodes and ExcludeExitNodes lists.
10287 - Change the implementation of ExcludeNodes and ExcludeExitNodes to
10288 be more efficient. Formerly it was quadratic in the number of
10289 servers; now it should be linear. Fixes bug 509.
10290 - Save 16-22 bytes per open circuit by moving the n_addr, n_port,
10291 and n_conn_id_digest fields into a separate structure that's
10292 only needed when the circuit has not yet attached to an n_conn.
10295 - Change the contrib/tor.logrotate script so it makes the new
10296 logs as "_tor:_tor" rather than the default, which is generally
10297 "root:wheel". Fixes bug 676, reported by Serge Koksharov.
10298 - Stop using __attribute__((nonnull)) with GCC: it can give us useful
10299 warnings (occasionally), but it can also cause the compiler to
10300 eliminate error-checking code. Suggested by Peter Gutmann.
10301 - When a hidden service is giving up on an introduction point candidate
10302 that was not included in the last published rendezvous descriptor,
10303 don't reschedule publication of the next descriptor. Fixes bug 763.
10305 - Mark RendNodes, RendExcludeNodes, HiddenServiceNodes, and
10306 HiddenServiceExcludeNodes as obsolete: they never worked properly,
10307 and nobody claims to be using them. Fixes bug 754. Bugfix on
10308 0.1.0.1-rc. Patch from Christian Wilms.
10309 - Fix a small alignment and memory-wasting bug on buffer chunks.
10312 o Minor bugfixes (controller):
10313 - When closing an application-side connection because its circuit
10314 is getting torn down, generate the stream event correctly.
10315 Bugfix on 0.1.2.x. Anonymous patch.
10317 o Removed features:
10318 - Remove all backward-compatibility code to support relays running
10319 versions of Tor so old that they no longer work at all on the
10323 Changes in version 0.2.0.30 - 2008-07-15
10325 - Stop using __attribute__((nonnull)) with GCC: it can give us useful
10326 warnings (occasionally), but it can also cause the compiler to
10327 eliminate error-checking code. Suggested by Peter Gutmann.
10330 Changes in version 0.2.0.29-rc - 2008-07-08
10331 Tor 0.2.0.29-rc fixes two big bugs with using bridges, fixes more
10332 hidden-service performance bugs, and fixes a bunch of smaller bugs.
10335 - If you have more than one bridge but don't know their keys,
10336 you would only launch a request for the descriptor of the first one
10337 on your list. (Tor considered launching requests for the others, but
10338 found that it already had a connection on the way for $0000...0000
10339 so it didn't open another.) Bugfix on 0.2.0.x.
10340 - If you have more than one bridge but don't know their keys, and the
10341 connection to one of the bridges failed, you would cancel all
10342 pending bridge connections. (After all, they all have the same
10343 digest.) Bugfix on 0.2.0.x.
10344 - When a hidden service was trying to establish an introduction point,
10345 and Tor had built circuits preemptively for such purposes, we
10346 were ignoring all the preemptive circuits and launching a new one
10347 instead. Bugfix on 0.2.0.14-alpha.
10348 - When a hidden service was trying to establish an introduction point,
10349 and Tor *did* manage to reuse one of the preemptively built
10350 circuits, it didn't correctly remember which one it used,
10351 so it asked for another one soon after, until there were no
10352 more preemptive circuits, at which point it launched one from
10353 scratch. Bugfix on 0.0.9.x.
10354 - Make directory servers include the X-Your-Address-Is: http header in
10355 their responses even for begin_dir conns. Now clients who only
10356 ever use begin_dir connections still have a way to learn their IP
10357 address. Fixes bug 737; bugfix on 0.2.0.22-rc. Reported by goldy.
10360 - Fix a macro/CPP interaction that was confusing some compilers:
10361 some GCCs don't like #if/#endif pairs inside macro arguments.
10363 - Fix macro collision between OpenSSL 0.9.8h and Windows headers.
10364 Fixes bug 704; fix from Steven Murdoch.
10365 - When opening /dev/null in finish_daemonize(), do not pass the
10366 O_CREAT flag. Fortify was complaining, and correctly so. Fixes
10367 bug 742; fix from Michael Scherer. Bugfix on 0.0.2pre19.
10368 - Correctly detect transparent proxy support on Linux hosts that
10369 require in.h to be included before netfilter_ipv4.h. Patch
10371 - Disallow session resumption attempts during the renegotiation
10372 stage of the v2 handshake protocol. Clients should never be trying
10373 session resumption at this point, but apparently some did, in
10374 ways that caused the handshake to fail. Bugfix on 0.2.0.20-rc. Bug
10375 found by Geoff Goodell.
10378 Changes in version 0.2.1.2-alpha - 2008-06-20
10379 Tor 0.2.1.2-alpha includes a new "TestingTorNetwork" config option to
10380 make it easier to set up your own private Tor network; fixes several
10381 big bugs with using more than one bridge relay; fixes a big bug with
10382 offering hidden services quickly after Tor starts; and uses a better
10383 API for reporting potential bootstrapping problems to the controller.
10386 - New TestingTorNetwork config option to allow adjustment of
10387 previously constant values that, while reasonable, could slow
10388 bootstrapping. Implements proposal 135. Patch from Karsten.
10391 - If you have more than one bridge but don't know their digests,
10392 you would only learn a request for the descriptor of the first one
10393 on your list. (Tor considered launching requests for the others, but
10394 found that it already had a connection on the way for $0000...0000
10395 so it didn't open another.) Bugfix on 0.2.0.x.
10396 - If you have more than one bridge but don't know their digests,
10397 and the connection to one of the bridges failed, you would cancel
10398 all pending bridge connections. (After all, they all have the
10399 same digest.) Bugfix on 0.2.0.x.
10400 - When establishing a hidden service, introduction points that
10401 originate from cannibalized circuits are completely ignored and not
10402 included in rendezvous service descriptors. This might be another
10403 reason for delay in making a hidden service available. Bugfix
10404 from long ago (0.0.9.x?)
10407 - Allow OpenSSL to use dynamic locks if it wants.
10408 - When building a consensus, do not include routers that are down.
10409 This will cut down 30% to 40% on consensus size. Implements
10411 - In directory authorities' approved-routers files, allow
10412 fingerprints with or without space.
10413 - Add a "GETINFO /status/bootstrap-phase" controller option, so the
10414 controller can query our current bootstrap state in case it attaches
10415 partway through and wants to catch up.
10416 - Send an initial "Starting" bootstrap status event, so we have a
10417 state to start out in.
10420 - Asking for a conditional consensus at .../consensus/<fingerprints>
10421 would crash a dirserver if it did not already have a
10422 consensus. Bugfix on 0.2.1.1-alpha.
10423 - Clean up some macro/CPP interactions: some GCC versions don't like
10424 #if/#endif pairs inside macro arguments. Fixes bug 707. Bugfix on
10427 o Bootstrapping bugfixes (on 0.2.1.1-alpha):
10428 - Directory authorities shouldn't complain about bootstrapping
10429 problems just because they do a lot of reachability testing and
10430 some of the connection attempts fail.
10431 - Start sending "count" and "recommendation" key/value pairs in
10432 bootstrap problem status events, so the controller can hear about
10433 problems even before Tor decides they're worth reporting for sure.
10434 - If you're using bridges, generate "bootstrap problem" warnings
10435 as soon as you run out of working bridges, rather than waiting
10436 for ten failures -- which will never happen if you have less than
10438 - If we close our OR connection because there's been a circuit
10439 pending on it for too long, we were telling our bootstrap status
10440 events "REASON=NONE". Now tell them "REASON=TIMEOUT".
10443 Changes in version 0.2.1.1-alpha - 2008-06-13
10444 Tor 0.2.1.1-alpha fixes a lot of memory fragmentation problems that
10445 were making the Tor process bloat especially on Linux; makes our TLS
10446 handshake blend in better; sends "bootstrap phase" status events to
10447 the controller, so it can keep the user informed of progress (and
10448 problems) fetching directory information and establishing circuits;
10449 and adds a variety of smaller features.
10452 - More work on making our TLS handshake blend in: modify the list
10453 of ciphers advertised by OpenSSL in client mode to even more
10454 closely resemble a common web browser. We cheat a little so that
10455 we can advertise ciphers that the locally installed OpenSSL doesn't
10457 - Start sending "bootstrap phase" status events to the controller,
10458 so it can keep the user informed of progress fetching directory
10459 information and establishing circuits. Also inform the controller
10460 if we think we're stuck at a particular bootstrap phase. Implements
10462 - Resume using OpenSSL's RAND_poll() for better (and more portable)
10463 cross-platform entropy collection again. We used to use it, then
10464 stopped using it because of a bug that could crash systems that
10465 called RAND_poll when they had a lot of fds open. It looks like the
10466 bug got fixed in late 2006. Our new behavior is to call RAND_poll()
10467 at startup, and to call RAND_poll() when we reseed later only if
10468 we have a non-buggy OpenSSL version.
10471 - When we choose to abandon a new entry guard because we think our
10472 older ones might be better, close any circuits pending on that
10473 new entry guard connection. This fix should make us recover much
10474 faster when our network is down and then comes back. Bugfix on
10475 0.1.2.8-beta; found by lodger.
10477 o Memory fixes and improvements:
10478 - Add a malloc_good_size implementation to OpenBSD_malloc_linux.c,
10479 to avoid unused RAM in buffer chunks and memory pools.
10480 - Speed up parsing and cut down on memory fragmentation by using
10481 stack-style allocations for parsing directory objects. Previously,
10482 this accounted for over 40% of allocations from within Tor's code
10483 on a typical directory cache.
10484 - Use a Bloom filter rather than a digest-based set to track which
10485 descriptors we need to keep around when we're cleaning out old
10486 router descriptors. This speeds up the computation significantly,
10487 and may reduce fragmentation.
10488 - Reduce the default smartlist size from 32 to 16; it turns out that
10489 most smartlists hold around 8-12 elements tops.
10490 - Make dumpstats() log the fullness and size of openssl-internal
10492 - If the user has applied the experimental SSL_MODE_RELEASE_BUFFERS
10493 patch to their OpenSSL, turn it on to save memory on servers. This
10494 patch will (with any luck) get included in a mainline distribution
10496 - Never use OpenSSL compression: it wastes RAM and CPU trying to
10497 compress cells, which are basically all encrypted, compressed,
10501 - Stop reloading the router list from disk for no reason when we
10502 run out of reachable directory mirrors. Once upon a time reloading
10503 it would set the 'is_running' flag back to 1 for them. It hasn't
10504 done that for a long time.
10505 - In very rare situations new hidden service descriptors were
10506 published earlier than 30 seconds after the last change to the
10507 service. (We currently think that a hidden service descriptor
10508 that's been stable for 30 seconds is worth publishing.)
10511 - Allow separate log levels to be configured for different logging
10512 domains. For example, this allows one to log all notices, warnings,
10513 or errors, plus all memory management messages of level debug or
10514 higher, with: Log [MM] debug-err [*] notice-err file /var/log/tor.
10515 - Add a couple of extra warnings to --enable-gcc-warnings for GCC 4.3,
10516 and stop using a warning that had become unfixably verbose under
10518 - New --hush command-line option similar to --quiet. While --quiet
10519 disables all logging to the console on startup, --hush limits the
10520 output to messages of warning and error severity.
10521 - Servers support a new URL scheme for consensus downloads that
10522 allows the client to specify which authorities are trusted.
10523 The server then only sends the consensus if the client will trust
10524 it. Otherwise a 404 error is sent back. Clients use this
10525 new scheme when the server supports it (meaning it's running
10526 0.2.1.1-alpha or later). Implements proposal 134.
10527 - New configure/torrc options (--enable-geoip-stats,
10528 DirRecordUsageByCountry) to record how many IPs we've served
10529 directory info to in each country code, how many status documents
10530 total we've sent to each country code, and what share of the total
10531 directory requests we should expect to see.
10532 - Use the TLS1 hostname extension to more closely resemble browser
10534 - Lots of new unit tests.
10535 - Add a macro to implement the common pattern of iterating through
10536 two parallel lists in lockstep.
10539 Changes in version 0.2.0.28-rc - 2008-06-13
10540 Tor 0.2.0.28-rc fixes an anonymity-related bug, fixes a hidden-service
10541 performance bug, and fixes a bunch of smaller bugs.
10544 - Fix a bug where, when we were choosing the 'end stream reason' to
10545 put in our relay end cell that we send to the exit relay, Tor
10546 clients on Windows were sometimes sending the wrong 'reason'. The
10547 anonymity problem is that exit relays may be able to guess whether
10548 the client is running Windows, thus helping partition the anonymity
10549 set. Down the road we should stop sending reasons to exit relays,
10550 or otherwise prevent future versions of this bug.
10553 - While setting up a hidden service, some valid introduction circuits
10554 were overlooked and abandoned. This might be the reason for
10555 the long delay in making a hidden service available. Bugfix on
10559 - Update to the "June 9 2008" ip-to-country file.
10560 - Run 'make test' as part of 'make dist', so we stop releasing so
10561 many development snapshots that fail their unit tests.
10564 - When we're checking if we have enough dir info for each relay
10565 to begin establishing circuits, make sure that we actually have
10566 the descriptor listed in the consensus, not just any descriptor.
10568 - Bridge relays no longer print "xx=0" in their extrainfo document
10569 for every single country code in the geoip db. Bugfix on
10571 - Only warn when we fail to load the geoip file if we were planning to
10572 include geoip stats in our extrainfo document. Bugfix on 0.2.0.27-rc.
10573 - If we change our MaxAdvertisedBandwidth and then reload torrc,
10574 Tor won't realize it should publish a new relay descriptor. Fixes
10575 bug 688, reported by mfr. Bugfix on 0.1.2.x.
10576 - When we haven't had any application requests lately, don't bother
10577 logging that we have expired a bunch of descriptors. Bugfix
10579 - Make relay cells written on a connection count as non-padding when
10580 tracking how long a connection has been in use. Bugfix on
10581 0.2.0.1-alpha. Spotted by lodger.
10582 - Fix unit tests in 0.2.0.27-rc.
10583 - Fix compile on Windows.
10586 Changes in version 0.2.0.27-rc - 2008-06-03
10587 Tor 0.2.0.27-rc adds a few features we left out of the earlier
10588 release candidates. In particular, we now include an IP-to-country
10589 GeoIP database, so controllers can easily look up what country a
10590 given relay is in, and so bridge relays can give us some sanitized
10591 summaries about which countries are making use of bridges. (See proposal
10592 126-geoip-fetching.txt for details.)
10595 - Include an IP-to-country GeoIP file in the tarball, so bridge
10596 relays can report sanitized summaries of the usage they're seeing.
10599 - Add a "PURPOSE=" argument to "STREAM NEW" events, as suggested by
10600 Robert Hogan. Fixes the first part of bug 681.
10601 - Make bridge authorities never serve extrainfo docs.
10602 - Add support to detect Libevent versions in the 1.4.x series
10604 - Fix build on gcc 4.3 with --enable-gcc-warnings set.
10605 - Include a new contrib/tor-exit-notice.html file that exit relay
10606 operators can put on their website to help reduce abuse queries.
10609 - When tunneling an encrypted directory connection, and its first
10610 circuit fails, do not leave it unattached and ask the controller
10611 to deal. Fixes the second part of bug 681.
10612 - Make bridge authorities correctly expire old extrainfo documents
10616 Changes in version 0.2.0.26-rc - 2008-05-13
10617 Tor 0.2.0.26-rc fixes a major security vulnerability caused by a bug
10618 in Debian's OpenSSL packages. All users running any 0.2.0.x version
10619 should upgrade, whether they're running Debian or not.
10621 o Major security fixes:
10622 - Use new V3 directory authority keys on the tor26, gabelmoo, and
10623 moria1 V3 directory authorities. The old keys were generated with
10624 a vulnerable version of Debian's OpenSSL package, and must be
10625 considered compromised. Other authorities' keys were not generated
10626 with an affected version of OpenSSL.
10629 - List authority signatures as "unrecognized" based on DirServer
10630 lines, not on cert cache. Bugfix on 0.2.0.x.
10633 - Add a new V3AuthUseLegacyKey option to make it easier for
10634 authorities to change their identity keys if they have to.
10637 Changes in version 0.2.0.25-rc - 2008-04-23
10638 Tor 0.2.0.25-rc makes Tor work again on OS X and certain BSDs.
10641 - Remember to initialize threading before initializing logging.
10642 Otherwise, many BSD-family implementations will crash hard on
10643 startup. Fixes bug 671. Bugfix on 0.2.0.24-rc.
10646 - Authorities correctly free policies on bad servers on
10647 exit. Fixes bug 672. Bugfix on 0.2.0.x.
10650 Changes in version 0.2.0.24-rc - 2008-04-22
10651 Tor 0.2.0.24-rc adds dizum (run by Alex de Joode) as the new sixth
10652 v3 directory authority, makes relays with dynamic IP addresses and no
10653 DirPort notice more quickly when their IP address changes, fixes a few
10654 rare crashes and memory leaks, and fixes a few other miscellaneous bugs.
10656 o New directory authorities:
10657 - Take lefkada out of the list of v3 directory authorities, since
10658 it has been down for months.
10659 - Set up dizum (run by Alex de Joode) as the new sixth v3 directory
10663 - Detect address changes more quickly on non-directory mirror
10664 relays. Bugfix on 0.2.0.18-alpha; fixes bug 652.
10666 o Minor features (security):
10667 - Reject requests for reverse-dns lookup of names that are in
10668 a private address space. Patch from lodger.
10669 - Non-exit relays no longer allow DNS requests. Fixes bug 619. Patch
10672 o Minor bugfixes (crashes):
10673 - Avoid a rare assert that can trigger when Tor doesn't have much
10674 directory information yet and it tries to fetch a v2 hidden
10675 service descriptor. Fixes bug 651, reported by nwf.
10676 - Initialize log mutex before initializing dmalloc. Otherwise,
10677 running with dmalloc would crash. Bugfix on 0.2.0.x-alpha.
10678 - Use recursive pthread mutexes in order to avoid deadlock when
10679 logging debug-level messages to a controller. Bug spotted by nwf,
10680 bugfix on 0.2.0.16-alpha.
10682 o Minor bugfixes (resource management):
10683 - Keep address policies from leaking memory: start their refcount
10684 at 1, not 2. Bugfix on 0.2.0.16-alpha.
10685 - Free authority certificates on exit, so they don't look like memory
10686 leaks. Bugfix on 0.2.0.19-alpha.
10687 - Free static hashtables for policy maps and for TLS connections on
10688 shutdown, so they don't look like memory leaks. Bugfix on 0.2.0.x.
10689 - Avoid allocating extra space when computing consensuses on 64-bit
10690 platforms. Bug spotted by aakova.
10692 o Minor bugfixes (misc):
10693 - Do not read the configuration file when we've only been told to
10694 generate a password hash. Fixes bug 643. Bugfix on 0.0.9pre5. Fix
10695 based on patch from Sebastian Hahn.
10696 - Exit relays that are used as a client can now reach themselves
10697 using the .exit notation, rather than just launching an infinite
10698 pile of circuits. Fixes bug 641. Reported by Sebastian Hahn.
10699 - When attempting to open a logfile fails, tell us why.
10700 - Fix a dumb bug that was preventing us from knowing that we should
10701 preemptively build circuits to handle expected directory requests.
10702 Fixes bug 660. Bugfix on 0.1.2.x.
10703 - Warn less verbosely about clock skew from netinfo cells from
10704 untrusted sources. Fixes bug 663.
10705 - Make controller stream events for DNS requests more consistent,
10706 by adding "new stream" events for DNS requests, and removing
10707 spurious "stream closed" events" for cached reverse resolves.
10708 Patch from mwenge. Fixes bug 646.
10709 - Correctly notify one-hop connections when a circuit build has
10710 failed. Possible fix for bug 669. Found by lodger.
10713 Changes in version 0.2.0.23-rc - 2008-03-24
10714 Tor 0.2.0.23-rc is the fourth release candidate for the 0.2.0 series. It
10715 makes bootstrapping faster if the first directory mirror you contact
10716 is down. The bundles also include the new Vidalia 0.1.2 release.
10719 - When a tunneled directory request is made to a directory server
10720 that's down, notice after 30 seconds rather than 120 seconds. Also,
10721 fail any begindir streams that are pending on it, so they can
10722 retry elsewhere. This was causing multi-minute delays on bootstrap.
10725 Changes in version 0.2.0.22-rc - 2008-03-18
10726 Tor 0.2.0.22-rc is the third release candidate for the 0.2.0 series. It
10727 enables encrypted directory connections by default for non-relays, fixes
10728 some broken TLS behavior we added in 0.2.0.20-rc, and resolves many
10729 other bugs. The bundles also include Vidalia 0.1.1 and Torbutton 1.1.17.
10732 - Enable encrypted directory connections by default for non-relays,
10733 so censor tools that block Tor directory connections based on their
10734 plaintext patterns will no longer work. This means Tor works in
10735 certain censored countries by default again.
10738 - Make sure servers always request certificates from clients during
10739 TLS renegotiation. Reported by lodger; bugfix on 0.2.0.20-rc.
10740 - Do not enter a CPU-eating loop when a connection is closed in
10741 the middle of client-side TLS renegotiation. Fixes bug 622. Bug
10742 diagnosed by lodger; bugfix on 0.2.0.20-rc.
10743 - Fix assertion failure that could occur when a blocked circuit
10744 became unblocked, and it had pending client DNS requests. Bugfix
10745 on 0.2.0.1-alpha. Fixes bug 632.
10747 o Minor bugfixes (on 0.1.2.x):
10748 - Generate "STATUS_SERVER" events rather than misspelled
10749 "STATUS_SEVER" events. Caught by mwenge.
10750 - When counting the number of bytes written on a TLS connection,
10751 look at the BIO actually used for writing to the network, not
10752 at the BIO used (sometimes) to buffer data for the network.
10753 Looking at different BIOs could result in write counts on the
10754 order of ULONG_MAX. Fixes bug 614.
10755 - On Windows, correctly detect errors when listing the contents of
10756 a directory. Fix from lodger.
10758 o Minor bugfixes (on 0.2.0.x):
10759 - Downgrade "sslv3 alert handshake failure" message to INFO.
10760 - If we set RelayBandwidthRate and RelayBandwidthBurst very high but
10761 left BandwidthRate and BandwidthBurst at the default, we would be
10762 silently limited by those defaults. Now raise them to match the
10763 RelayBandwidth* values.
10764 - Fix the SVK version detection logic to work correctly on a branch.
10765 - Make --enable-openbsd-malloc work correctly on Linux with alpha
10766 CPUs. Fixes bug 625.
10767 - Logging functions now check that the passed severity is sane.
10768 - Use proper log levels in the testsuite call of
10769 get_interface_address6().
10770 - When using a nonstandard malloc, do not use the platform values for
10771 HAVE_MALLOC_GOOD_SIZE or HAVE_MALLOC_USABLE_SIZE.
10772 - Make the openbsd malloc code use 8k pages on alpha CPUs and
10774 - Detect mismatched page sizes when using --enable-openbsd-malloc.
10775 - Avoid double-marked-for-close warning when certain kinds of invalid
10776 .in-addr.arpa addresses are passed to the DNSPort. Part of a fix
10777 for bug 617. Bugfix on 0.2.0.1-alpha.
10778 - Make sure that the "NULL-means-reject *:*" convention is followed by
10779 all the policy manipulation functions, avoiding some possible crash
10780 bugs. Bug found by lodger. Bugfix on 0.2.0.16-alpha.
10781 - Fix the implementation of ClientDNSRejectInternalAddresses so that it
10782 actually works, and doesn't warn about every single reverse lookup.
10783 Fixes the other part of bug 617. Bugfix on 0.2.0.1-alpha.
10786 - Only log guard node status when guard node status has changed.
10787 - Downgrade the 3 most common "INFO" messages to "DEBUG". This will
10788 make "INFO" 75% less verbose.
10791 Changes in version 0.2.0.21-rc - 2008-03-02
10792 Tor 0.2.0.21-rc is the second release candidate for the 0.2.0 series. It
10793 makes Tor work well with Vidalia again, fixes a rare assert bug,
10794 and fixes a pair of more minor bugs. The bundles also include Vidalia
10795 0.1.0 and Torbutton 1.1.16.
10798 - The control port should declare that it requires password auth
10799 when HashedControlSessionPassword is set too. Patch from Matt Edman;
10800 bugfix on 0.2.0.20-rc. Fixes bug 615.
10801 - Downgrade assert in connection_buckets_decrement() to a log message.
10802 This may help us solve bug 614, and in any case will make its
10803 symptoms less severe. Bugfix on 0.2.0.20-rc. Reported by fredzupy.
10804 - We were sometimes miscounting the number of bytes read from the
10805 network, causing our rate limiting to not be followed exactly.
10806 Bugfix on 0.2.0.16-alpha. Reported by lodger.
10809 - Fix compilation with OpenSSL 0.9.8 and 0.9.8a. All other supported
10810 OpenSSL versions should have been working fine. Diagnosis and patch
10811 from lodger, Karsten Loesing, and Sebastian Hahn. Fixes bug 616.
10812 Bugfix on 0.2.0.20-rc.
10815 Changes in version 0.2.0.20-rc - 2008-02-24
10816 Tor 0.2.0.20-rc is the first release candidate for the 0.2.0 series. It
10817 makes more progress towards normalizing Tor's TLS handshake, makes
10818 hidden services work better again, helps relays bootstrap if they don't
10819 know their IP address, adds optional support for linking in openbsd's
10820 allocator or tcmalloc, allows really fast relays to scale past 15000
10821 sockets, and fixes a bunch of minor bugs reported by Veracode.
10824 - Enable the revised TLS handshake based on the one designed by
10825 Steven Murdoch in proposal 124, as revised in proposal 130. It
10826 includes version negotiation for OR connections as described in
10827 proposal 105. The new handshake is meant to be harder for censors
10828 to fingerprint, and it adds the ability to detect certain kinds of
10829 man-in-the-middle traffic analysis attacks. The version negotiation
10830 feature will allow us to improve Tor's link protocol more safely
10832 - Choose which bridge to use proportional to its advertised bandwidth,
10833 rather than uniformly at random. This should speed up Tor for
10834 bridge users. Also do this for people who set StrictEntryNodes.
10835 - When a TrackHostExits-chosen exit fails too many times in a row,
10836 stop using it. Bugfix on 0.1.2.x; fixes bug 437.
10839 - Resolved problems with (re-)fetching hidden service descriptors.
10840 Patch from Karsten Loesing; fixes problems with 0.2.0.18-alpha
10841 and 0.2.0.19-alpha.
10842 - If we only ever used Tor for hidden service lookups or posts, we
10843 would stop building circuits and start refusing connections after
10844 24 hours, since we falsely believed that Tor was dormant. Reported
10845 by nwf; bugfix on 0.1.2.x.
10846 - Servers that don't know their own IP address should go to the
10847 authorities for their first directory fetch, even if their DirPort
10848 is off or if they don't know they're reachable yet. This will help
10849 them bootstrap better. Bugfix on 0.2.0.18-alpha; fixes bug 609.
10850 - When counting the number of open sockets, count not only the number
10851 of sockets we have received from the socket() call, but also
10852 the number we've gotten from accept() and socketpair(). This bug
10853 made us fail to count all sockets that we were using for incoming
10854 connections. Bugfix on 0.2.0.x.
10855 - Fix code used to find strings within buffers, when those strings
10856 are not in the first chunk of the buffer. Bugfix on 0.2.0.x.
10857 - Fix potential segfault when parsing HTTP headers. Bugfix on 0.2.0.x.
10858 - Add a new __HashedControlSessionPassword option for controllers
10859 to use for one-off session password hashes that shouldn't get
10860 saved to disk by SAVECONF --- Vidalia users were accumulating a
10861 pile of HashedControlPassword lines in their torrc files, one for
10862 each time they had restarted Tor and then clicked Save. Make Tor
10863 automatically convert "HashedControlPassword" to this new option but
10864 only when it's given on the command line. Partial fix for bug 586.
10866 o Minor features (performance):
10867 - Tune parameters for cell pool allocation to minimize amount of
10869 - Add OpenBSD malloc code from phk as an optional malloc
10870 replacement on Linux: some glibc libraries do very poorly
10871 with Tor's memory allocation patterns. Pass
10872 --enable-openbsd-malloc to get the replacement malloc code.
10873 - Add a --with-tcmalloc option to the configure script to link
10874 against tcmalloc (if present). Does not yet search for
10875 non-system include paths.
10876 - Stop imposing an arbitrary maximum on the number of file descriptors
10877 used for busy servers. Bug reported by Olaf Selke; patch from
10880 o Minor features (other):
10881 - When SafeLogging is disabled, log addresses along with all TLS
10883 - When building with --enable-gcc-warnings, check for whether Apple's
10884 warning "-Wshorten-64-to-32" is available.
10885 - Add a --passphrase-fd argument to the tor-gencert command for
10888 o Minor bugfixes (memory leaks and code problems):
10889 - We were leaking a file descriptor if Tor started with a zero-length
10890 cached-descriptors file. Patch by freddy77; bugfix on 0.1.2.
10891 - Detect size overflow in zlib code. Reported by Justin Ferguson and
10893 - We were comparing the raw BridgePassword entry with a base64'ed
10894 version of it, when handling a "/tor/networkstatus-bridges"
10895 directory request. Now compare correctly. Noticed by Veracode.
10896 - Recover from bad tracked-since value in MTBF-history file.
10897 Should fix bug 537.
10898 - Alter the code that tries to recover from unhandled write
10899 errors, to not try to flush onto a socket that's given us
10900 unhandled errors. Bugfix on 0.1.2.x.
10901 - Make Unix controlsockets work correctly on OpenBSD. Patch from
10902 tup. Bugfix on 0.2.0.3-alpha.
10904 o Minor bugfixes (other):
10905 - If we have an extra-info document for our server, always make
10906 it available on the control port, even if we haven't gotten
10907 a copy of it from an authority yet. Patch from mwenge.
10908 - Log the correct memory chunk sizes for empty RAM chunks in mempool.c.
10909 - Directory mirrors no longer include a guess at the client's IP
10910 address if the connection appears to be coming from the same /24
10911 network; it was producing too many wrong guesses.
10912 - Make the new hidden service code respect the SafeLogging setting.
10913 Bugfix on 0.2.0.x. Patch from Karsten.
10914 - When starting as an authority, do not overwrite all certificates
10915 cached from other authorities. Bugfix on 0.2.0.x. Fixes bug 606.
10916 - If we're trying to flush the last bytes on a connection (for
10917 example, when answering a directory request), reset the
10918 time-to-give-up timeout every time we manage to write something
10919 on the socket. Bugfix on 0.1.2.x.
10920 - Change the behavior of "getinfo status/good-server-descriptor"
10921 so it doesn't return failure when any authority disappears.
10922 - Even though the man page said that "TrackHostExits ." should
10923 work, nobody had ever implemented it. Bugfix on 0.1.0.x.
10924 - Report TLS "zero return" case as a "clean close" and "IO error"
10925 as a "close". Stop calling closes "unexpected closes": existing
10926 Tors don't use SSL_close(), so having a connection close without
10927 the TLS shutdown handshake is hardly unexpected.
10928 - Send NAMESERVER_STATUS messages for a single failed nameserver
10931 o Code simplifications and refactoring:
10932 - Remove the tor_strpartition function: its logic was confused,
10933 and it was only used for one thing that could be implemented far
10937 Changes in version 0.2.0.19-alpha - 2008-02-09
10938 Tor 0.2.0.19-alpha makes more progress towards normalizing Tor's TLS
10939 handshake, makes path selection for relays more secure and IP address
10940 guessing more robust, and generally fixes a lot of bugs in preparation
10941 for calling the 0.2.0 branch stable.
10944 - Do not include recognizeable strings in the commonname part of
10945 Tor's x509 certificates.
10948 - If we're a relay, avoid picking ourselves as an introduction point,
10949 a rendezvous point, or as the final hop for internal circuits. Bug
10950 reported by taranis and lodger. Bugfix on 0.1.2.x.
10951 - Patch from "Andrew S. Lists" to catch when we contact a directory
10952 mirror at IP address X and he says we look like we're coming from
10953 IP address X. Bugfix on 0.1.2.x.
10955 o Minor features (security):
10956 - Be more paranoid about overwriting sensitive memory on free(),
10957 as a defensive programming tactic to ensure forward secrecy.
10959 o Minor features (directory authority):
10960 - Actually validate the options passed to AuthDirReject,
10961 AuthDirInvalid, AuthDirBadDir, and AuthDirBadExit.
10962 - Reject router descriptors with out-of-range bandwidthcapacity or
10963 bandwidthburst values.
10965 o Minor features (controller):
10966 - Reject controller commands over 1MB in length. This keeps rogue
10967 processes from running us out of memory.
10969 o Minor features (misc):
10970 - Give more descriptive well-formedness errors for out-of-range
10971 hidden service descriptor/protocol versions.
10972 - Make memory debugging information describe more about history
10973 of cell allocation, so we can help reduce our memory use.
10975 o Deprecated features (controller):
10976 - The status/version/num-versioning and status/version/num-concurring
10977 GETINFO options are no longer useful in the v3 directory protocol:
10978 treat them as deprecated, and warn when they're used.
10981 - When our consensus networkstatus has been expired for a while, stop
10982 being willing to build circuits using it. Fixes bug 401. Bugfix
10984 - Directory caches now fetch certificates from all authorities
10985 listed in a networkstatus consensus, even when they do not
10986 recognize them. Fixes bug 571. Bugfix on 0.2.0.x.
10987 - When connecting to a bridge without specifying its key, insert
10988 the connection into the identity-to-connection map as soon as
10989 a key is learned. Fixes bug 574. Bugfix on 0.2.0.x.
10990 - Detect versions of OS X where malloc_good_size() is present in the
10991 library but never actually declared. Resolves bug 587. Bugfix
10993 - Stop incorrectly truncating zlib responses to directory authority
10994 signature download requests. Fixes bug 593. Bugfix on 0.2.0.x.
10995 - Stop recommending that every server operator send mail to tor-ops.
10996 Resolves bug 597. Bugfix on 0.1.2.x.
10997 - Don't trigger an assert if we start a directory authority with a
10998 private IP address (like 127.0.0.1).
10999 - Avoid possible failures when generating a directory with routers
11000 with over-long versions strings, or too many flags set. Bugfix
11002 - If an attempt to launch a DNS resolve request over the control
11003 port fails because we have overrun the limit on the number of
11004 connections, tell the controller that the request has failed.
11005 - Avoid using too little bandwidth when our clock skips a few
11006 seconds. Bugfix on 0.1.2.x.
11007 - Fix shell error when warning about missing packages in configure
11008 script, on Fedora or Red Hat machines. Bugfix on 0.2.0.x.
11009 - Do not become confused when receiving a spurious VERSIONS-like
11010 cell from a confused v1 client. Bugfix on 0.2.0.x.
11011 - Re-fetch v2 (as well as v0) rendezvous descriptors when all
11012 introduction points for a hidden service have failed. Patch from
11013 Karsten Loesing. Bugfix on 0.2.0.x.
11015 o Code simplifications and refactoring:
11016 - Remove some needless generality from cpuworker code, for improved
11018 - Stop overloading the circuit_t.onionskin field for both "onionskin
11019 from a CREATE cell that we are waiting for a cpuworker to be
11020 assigned" and "onionskin from an EXTEND cell that we are going to
11021 send to an OR as soon as we are connected". Might help with bug 600.
11022 - Add an in-place version of aes_crypt() so that we can avoid doing a
11023 needless memcpy() call on each cell payload.
11026 Changes in version 0.2.0.18-alpha - 2008-01-25
11027 Tor 0.2.0.18-alpha adds a sixth v3 directory authority run by CCC,
11028 fixes a big memory leak in 0.2.0.17-alpha, and adds new config options
11029 that can warn or reject connections to ports generally associated with
11030 vulnerable-plaintext protocols.
11032 o New directory authorities:
11033 - Set up dannenberg (run by CCC) as the sixth v3 directory
11037 - Fix a major memory leak when attempting to use the v2 TLS
11038 handshake code. Bugfix on 0.2.0.x; fixes bug 589.
11039 - We accidentally enabled the under-development v2 TLS handshake
11040 code, which was causing log entries like "TLS error while
11041 renegotiating handshake". Disable it again. Resolves bug 590.
11042 - We were computing the wrong Content-Length: header for directory
11043 responses that need to be compressed on the fly, causing clients
11044 asking for those items to always fail. Bugfix on 0.2.0.x; partially
11048 - Avoid going directly to the directory authorities even if you're a
11049 relay, if you haven't found yourself reachable yet or if you've
11050 decided not to advertise your dirport yet. Addresses bug 556.
11051 - If we've gone 12 hours since our last bandwidth check, and we
11052 estimate we have less than 50KB bandwidth capacity but we could
11053 handle more, do another bandwidth test.
11054 - New config options WarnPlaintextPorts and RejectPlaintextPorts so
11055 Tor can warn and/or refuse connections to ports commonly used with
11056 vulnerable-plaintext protocols. Currently we warn on ports 23,
11057 109, 110, and 143, but we don't reject any.
11060 - When we setconf ClientOnly to 1, close any current OR and Dir
11061 listeners. Reported by mwenge.
11062 - When we get a consensus that's been signed by more people than
11063 we expect, don't log about it; it's not a big deal. Reported
11067 - Don't answer "/tor/networkstatus-bridges" directory requests if
11068 the request isn't encrypted.
11069 - Make "ClientOnly 1" config option disable directory ports too.
11070 - Patches from Karsten Loesing to make v2 hidden services more
11071 robust: work even when there aren't enough HSDir relays available;
11072 retry when a v2 rend desc fetch fails; but don't retry if we
11073 already have a usable v0 rend desc.
11076 Changes in version 0.2.0.17-alpha - 2008-01-17
11077 Tor 0.2.0.17-alpha makes the tarball build cleanly again (whoops).
11080 - Make the tor-gencert man page get included correctly in the tarball.
11083 Changes in version 0.2.0.16-alpha - 2008-01-17
11084 Tor 0.2.0.16-alpha adds a fifth v3 directory authority run by Karsten
11085 Loesing, and generally cleans up a lot of features and minor bugs.
11087 o New directory authorities:
11088 - Set up gabelmoo (run by Karsten Loesing) as the fifth v3 directory
11091 o Major performance improvements:
11092 - Switch our old ring buffer implementation for one more like that
11093 used by free Unix kernels. The wasted space in a buffer with 1mb
11094 of data will now be more like 8k than 1mb. The new implementation
11095 also avoids realloc();realloc(); patterns that can contribute to
11096 memory fragmentation.
11099 - Configuration files now accept C-style strings as values. This
11100 helps encode characters not allowed in the current configuration
11101 file format, such as newline or #. Addresses bug 557.
11102 - Although we fixed bug 539 (where servers would send HTTP status 503
11103 responses _and_ send a body too), there are still servers out
11104 there that haven't upgraded. Therefore, make clients parse such
11105 bodies when they receive them.
11106 - When we're not serving v2 directory information, there is no reason
11107 to actually keep any around. Remove the obsolete files and directory
11108 on startup if they are very old and we aren't going to serve them.
11110 o Minor performance improvements:
11111 - Reference-count and share copies of address policy entries; only 5%
11112 of them were actually distinct.
11113 - Never walk through the list of logs if we know that no log is
11114 interested in a given message.
11117 - When an authority has not signed a consensus, do not try to
11118 download a nonexistent "certificate with key 00000000". Bugfix
11119 on 0.2.0.x. Fixes bug 569.
11120 - Fix a rare assert error when we're closing one of our threads:
11121 use a mutex to protect the list of logs, so we never write to the
11122 list as it's being freed. Bugfix on 0.1.2.x. Fixes the very rare
11123 bug 575, which is kind of the revenge of bug 222.
11124 - Patch from Karsten Loesing to complain less at both the client
11125 and the relay when a relay used to have the HSDir flag but doesn't
11126 anymore, and we try to upload a hidden service descriptor.
11127 - Stop leaking one cert per TLS context. Fixes bug 582. Bugfix on
11129 - Do not try to download missing certificates until we have tried
11130 to check our fallback consensus. Fixes bug 583.
11131 - Make bridges round reported GeoIP stats info up to the nearest
11132 estimate, not down. Now we can distinguish between "0 people from
11133 this country" and "1 person from this country".
11134 - Avoid a spurious free on base64 failure. Bugfix on 0.1.2.
11135 - Avoid possible segfault if key generation fails in
11136 crypto_pk_hybrid_encrypt. Bugfix on 0.2.0.
11137 - Avoid segfault in the case where a badly behaved v2 versioning
11138 directory sends a signed networkstatus with missing client-versions.
11140 - Avoid segfaults on certain complex invocations of
11141 router_get_by_hexdigest(). Bugfix on 0.1.2.
11142 - Correct bad index on array access in parse_http_time(). Bugfix
11144 - Fix possible bug in vote generation when server versions are present
11145 but client versions are not.
11146 - Fix rare bug on REDIRECTSTREAM control command when called with no
11147 port set: it could erroneously report an error when none had
11149 - Avoid bogus crash-prone, leak-prone tor_realloc when we're
11150 compressing large objects and find ourselves with more than 4k
11151 left over. Bugfix on 0.2.0.
11152 - Fix a small memory leak when setting up a hidden service.
11153 - Fix a few memory leaks that could in theory happen under bizarre
11155 - Fix an assert if we post a general-purpose descriptor via the
11156 control port but that descriptor isn't mentioned in our current
11157 network consensus. Bug reported by Jon McLachlan; bugfix on
11160 o Minor features (controller):
11161 - Get NS events working again. Patch from tup.
11162 - The GETCONF command now escapes and quotes configuration values
11163 that don't otherwise fit into the torrc file.
11164 - The SETCONF command now handles quoted values correctly.
11166 o Minor features (directory authorities):
11167 - New configuration options to override default maximum number of
11168 servers allowed on a single IP address. This is important for
11169 running a test network on a single host.
11170 - Actually implement the -s option to tor-gencert.
11171 - Add a manual page for tor-gencert.
11173 o Minor features (bridges):
11174 - Bridge authorities no longer serve bridge descriptors over
11175 unencrypted connections.
11177 o Minor features (other):
11178 - Add hidden services and DNSPorts to the list of things that make
11179 Tor accept that it has running ports. Change starting Tor with no
11180 ports from a fatal error to a warning; we might change it back if
11181 this turns out to confuse anybody. Fixes bug 579.
11184 Changes in version 0.1.2.19 - 2008-01-17
11185 Tor 0.1.2.19 fixes a huge memory leak on exit relays, makes the default
11186 exit policy a little bit more conservative so it's safer to run an
11187 exit relay on a home system, and fixes a variety of smaller issues.
11190 - Exit policies now reject connections that are addressed to a
11191 relay's public (external) IP address too, unless
11192 ExitPolicyRejectPrivate is turned off. We do this because too
11193 many relays are running nearby to services that trust them based
11194 on network address.
11197 - When the clock jumps forward a lot, do not allow the bandwidth
11198 buckets to become negative. Fixes bug 544.
11199 - Fix a memory leak on exit relays; we were leaking a cached_resolve_t
11200 on every successful resolve. Reported by Mike Perry.
11201 - Purge old entries from the "rephist" database and the hidden
11202 service descriptor database even when DirPort is zero.
11203 - Stop thinking that 0.1.2.x directory servers can handle "begin_dir"
11204 requests. Should ease bugs 406 and 419 where 0.1.2.x relays are
11205 crashing or mis-answering these requests.
11206 - When we decide to send a 503 response to a request for servers, do
11207 not then also send the server descriptors: this defeats the whole
11208 purpose. Fixes bug 539.
11211 - Changing the ExitPolicyRejectPrivate setting should cause us to
11212 rebuild our server descriptor.
11213 - Fix handling of hex nicknames when answering controller requests for
11214 networkstatus by name, or when deciding whether to warn about
11215 unknown routers in a config option. (Patch from mwenge.)
11216 - Fix a couple of hard-to-trigger autoconf problems that could result
11217 in really weird results on platforms whose sys/types.h files define
11218 nonstandard integer types.
11219 - Don't try to create the datadir when running --verify-config or
11220 --hash-password. Resolves bug 540.
11221 - If we were having problems getting a particular descriptor from the
11222 directory caches, and then we learned about a new descriptor for
11223 that router, we weren't resetting our failure count. Reported
11225 - Although we fixed bug 539 (where servers would send HTTP status 503
11226 responses _and_ send a body too), there are still servers out there
11227 that haven't upgraded. Therefore, make clients parse such bodies
11228 when they receive them.
11229 - Run correctly on systems where rlim_t is larger than unsigned long.
11230 This includes some 64-bit systems.
11231 - Run correctly on platforms (like some versions of OS X 10.5) where
11232 the real limit for number of open files is OPEN_FILES, not rlim_max
11233 from getrlimit(RLIMIT_NOFILES).
11234 - Avoid a spurious free on base64 failure.
11235 - Avoid segfaults on certain complex invocations of
11236 router_get_by_hexdigest().
11237 - Fix rare bug on REDIRECTSTREAM control command when called with no
11238 port set: it could erroneously report an error when none had
11242 Changes in version 0.2.0.15-alpha - 2007-12-25
11243 Tor 0.2.0.14-alpha and 0.2.0.15-alpha fix a bunch of bugs with the
11244 features added in 0.2.0.13-alpha.
11247 - Fix several remotely triggerable asserts based on DirPort requests
11248 for a v2 or v3 networkstatus object before we were prepared. This
11249 was particularly bad for 0.2.0.13 and later bridge relays, who
11250 would never have a v2 networkstatus and would thus always crash
11251 when used. Bugfixes on 0.2.0.x.
11252 - Estimate the v3 networkstatus size more accurately, rather than
11253 estimating it at zero bytes and giving it artificially high priority
11254 compared to other directory requests. Bugfix on 0.2.0.x.
11257 - Fix configure.in logic for cross-compilation.
11258 - When we load a bridge descriptor from the cache, and it was
11259 previously unreachable, mark it as retriable so we won't just
11260 ignore it. Also, try fetching a new copy immediately. Bugfixes
11262 - The bridge GeoIP stats were counting other relays, for example
11263 self-reachability and authority-reachability tests.
11266 - Support compilation to target iPhone; patch from cjacker huang.
11267 To build for iPhone, pass the --enable-iphone option to configure.
11270 Changes in version 0.2.0.14-alpha - 2007-12-23
11272 - Fix a crash on startup if you install Tor 0.2.0.13-alpha fresh
11273 without a datadirectory from a previous Tor install. Reported
11275 - Fix a crash when we fetch a descriptor that turns out to be
11276 unexpected (it used to be in our networkstatus when we started
11277 fetching it, but it isn't in our current networkstatus), and we
11278 aren't using bridges. Bugfix on 0.2.0.x.
11279 - Fix a crash when accessing hidden services: it would work the first
11280 time you use a given introduction point for your service, but
11281 on subsequent requests we'd be using garbage memory. Fixed by
11282 Karsten Loesing. Bugfix on 0.2.0.13-alpha.
11283 - Fix a crash when we load a bridge descriptor from disk but we don't
11284 currently have a Bridge line for it in our torrc. Bugfix on
11288 - If bridge authorities set BridgePassword, they will serve a
11289 snapshot of known bridge routerstatuses from their DirPort to
11290 anybody who knows that password. Unset by default.
11293 - Make the unit tests build again.
11294 - Make "GETINFO/desc-annotations/id/<OR digest>" actually work.
11295 - Make PublishServerDescriptor default to 1, so the default doesn't
11296 have to change as we invent new directory protocol versions.
11297 - Fix test for rlim_t on OSX 10.3: sys/resource.h doesn't want to
11298 be included unless sys/time.h is already included. Fixes
11299 bug 553. Bugfix on 0.2.0.x.
11300 - If we receive a general-purpose descriptor and then receive an
11301 identical bridge-purpose descriptor soon after, don't discard
11302 the next one as a duplicate.
11305 - If BridgeRelay is set to 1, then the default for
11306 PublishServerDescriptor is now "bridge" rather than "v2,v3".
11307 - If the user sets RelayBandwidthRate but doesn't set
11308 RelayBandwidthBurst, then make them equal rather than erroring out.
11311 Changes in version 0.2.0.13-alpha - 2007-12-21
11312 Tor 0.2.0.13-alpha adds a fourth v3 directory authority run by Geoff
11313 Goodell, fixes many more bugs, and adds a lot of infrastructure for
11316 o New directory authorities:
11317 - Set up lefkada (run by Geoff Goodell) as the fourth v3 directory
11321 - Only update guard status (usable / not usable) once we have
11322 enough directory information. This was causing us to always pick
11323 two new guards on startup (bugfix on 0.2.0.9-alpha), and it was
11324 causing us to discard all our guards on startup if we hadn't been
11325 running for a few weeks (bugfix on 0.1.2.x). Fixes bug 448.
11326 - Purge old entries from the "rephist" database and the hidden
11327 service descriptor databases even when DirPort is zero. Bugfix
11329 - We were ignoring our RelayBandwidthRate for the first 30 seconds
11330 after opening a circuit -- even a relayed circuit. Bugfix on
11332 - Stop thinking that 0.1.2.x directory servers can handle "begin_dir"
11333 requests. Should ease bugs 406 and 419 where 0.1.2.x relays are
11334 crashing or mis-answering these types of requests.
11335 - Relays were publishing their server descriptor to v1 and v2
11336 directory authorities, but they didn't try publishing to v3-only
11337 authorities. Fix this; and also stop publishing to v1 authorities.
11339 - When we were reading router descriptors from cache, we were ignoring
11340 the annotations -- so for example we were reading in bridge-purpose
11341 descriptors as general-purpose descriptors. Bugfix on 0.2.0.8-alpha.
11342 - When we decided to send a 503 response to a request for servers, we
11343 were then also sending the server descriptors: this defeats the
11344 whole purpose. Fixes bug 539; bugfix on 0.1.2.x.
11347 - Bridge relays now behave like clients with respect to time
11348 intervals for downloading new consensus documents -- otherwise they
11349 stand out. Bridge users now wait until the end of the interval,
11350 so their bridge relay will be sure to have a new consensus document.
11351 - Three new config options (AlternateDirAuthority,
11352 AlternateBridgeAuthority, and AlternateHSAuthority) that let the
11353 user selectively replace the default directory authorities by type,
11354 rather than the all-or-nothing replacement that DirServer offers.
11355 - Tor can now be configured to read a GeoIP file from disk in one
11356 of two formats. This can be used by controllers to map IP addresses
11357 to countries. Eventually, it may support exit-by-country.
11358 - When possible, bridge relays remember which countries users
11359 are coming from, and report aggregate information in their
11360 extra-info documents, so that the bridge authorities can learn
11361 where Tor is blocked.
11362 - Bridge directory authorities now do reachability testing on the
11363 bridges they know. They provide router status summaries to the
11364 controller via "getinfo ns/purpose/bridge", and also dump summaries
11365 to a file periodically.
11366 - Stop fetching directory info so aggressively if your DirPort is
11367 on but your ORPort is off; stop fetching v2 dir info entirely.
11368 You can override these choices with the new FetchDirInfoEarly
11372 - The fix in 0.2.0.12-alpha cleared the "hsdir" flag in v3 network
11373 consensus documents when there are too many relays at a single
11374 IP address. Now clear it in v2 network status documents too, and
11375 also clear it in routerinfo_t when the relay is no longer listed
11376 in the relevant networkstatus document.
11377 - Don't crash if we get an unexpected value for the
11378 PublishServerDescriptor config option. Reported by Matt Edman;
11379 bugfix on 0.2.0.9-alpha.
11380 - Our new v2 hidden service descriptor format allows descriptors
11381 that have no introduction points. But Tor crashed when we tried
11382 to build a descriptor with no intro points (and it would have
11383 crashed if we had tried to parse one). Bugfix on 0.2.0.x; patch
11384 by Karsten Loesing.
11385 - Fix building with dmalloc 5.5.2 with glibc.
11386 - Reject uploaded descriptors and extrainfo documents if they're
11387 huge. Otherwise we'll cache them all over the network and it'll
11388 clog everything up. Reported by Aljosha Judmayer.
11389 - Check for presence of s6_addr16 and s6_addr32 fields in in6_addr
11390 via autoconf. Should fix compile on solaris. Bugfix on 0.2.0.x.
11391 - When the DANGEROUS_VERSION controller status event told us we're
11392 running an obsolete version, it used the string "OLD" to describe
11393 it. Yet the "getinfo" interface used the string "OBSOLETE". Now use
11394 "OBSOLETE" in both cases. Bugfix on 0.1.2.x.
11395 - If we can't expand our list of entry guards (e.g. because we're
11396 using bridges or we have StrictEntryNodes set), don't mark relays
11397 down when they fail a directory request. Otherwise we're too quick
11398 to mark all our entry points down. Bugfix on 0.1.2.x.
11399 - Fix handling of hex nicknames when answering controller requests for
11400 networkstatus by name, or when deciding whether to warn about unknown
11401 routers in a config option. Bugfix on 0.1.2.x. (Patch from mwenge.)
11402 - Fix a couple of hard-to-trigger autoconf problems that could result
11403 in really weird results on platforms whose sys/types.h files define
11404 nonstandard integer types. Bugfix on 0.1.2.x.
11405 - Fix compilation with --disable-threads set. Bugfix on 0.2.0.x.
11406 - Don't crash on name lookup when we have no current consensus. Fixes
11407 bug 538; bugfix on 0.2.0.x.
11408 - Only Tors that want to mirror the v2 directory info should
11409 create the "cached-status" directory in their datadir. (All Tors
11410 used to create it.) Bugfix on 0.2.0.9-alpha.
11411 - Directory authorities should only automatically download Extra Info
11412 documents if they're v1, v2, or v3 authorities. Bugfix on 0.1.2.x.
11415 - On the USR1 signal, when dmalloc is in use, log the top 10 memory
11416 consumers. (We already do this on HUP.)
11417 - Authorities and caches fetch the v2 networkstatus documents
11418 less often, now that v3 is encouraged.
11419 - Add a new config option BridgeRelay that specifies you want to
11420 be a bridge relay. Right now the only difference is that it makes
11421 you answer begin_dir requests, and it makes you cache dir info,
11422 even if your DirPort isn't on.
11423 - Add "GETINFO/desc-annotations/id/<OR digest>" so controllers can
11424 ask about source, timestamp of arrival, purpose, etc. We need
11425 something like this to help Vidalia not do GeoIP lookups on bridge
11427 - Allow multiple HashedControlPassword config lines, to support
11428 multiple controller passwords.
11429 - Authorities now decide whether they're authoritative for a given
11430 router based on the router's purpose.
11431 - New config options AuthDirBadDir and AuthDirListBadDirs for
11432 authorities to mark certain relays as "bad directories" in the
11433 networkstatus documents. Also supports the "!baddir" directive in
11434 the approved-routers file.
11437 Changes in version 0.2.0.12-alpha - 2007-11-16
11438 This twelfth development snapshot fixes some more build problems as
11439 well as a few minor bugs.
11442 - Make it build on OpenBSD again. Patch from tup.
11443 - Substitute BINDIR and LOCALSTATEDIR in scripts. Fixes
11444 package-building for Red Hat, OS X, etc.
11446 o Minor bugfixes (on 0.1.2.x):
11447 - Changing the ExitPolicyRejectPrivate setting should cause us to
11448 rebuild our server descriptor.
11450 o Minor bugfixes (on 0.2.0.x):
11451 - When we're lacking a consensus, don't try to perform rendezvous
11452 operations. Reported by Karsten Loesing.
11453 - Fix a small memory leak whenever we decide against using a
11454 newly picked entry guard. Reported by Mike Perry.
11455 - When authorities detected more than two relays running on the same
11456 IP address, they were clearing all the status flags but forgetting
11457 to clear the "hsdir" flag. So clients were being told that a
11458 given relay was the right choice for a v2 hsdir lookup, yet they
11459 never had its descriptor because it was marked as 'not running'
11461 - If we're trying to fetch a bridge descriptor and there's no way
11462 the bridge authority could help us (for example, we don't know
11463 a digest, or there is no bridge authority), don't be so eager to
11464 fall back to asking the bridge authority.
11465 - If we're using bridges or have strictentrynodes set, and our
11466 chosen exit is in the same family as all our bridges/entry guards,
11467 then be flexible about families.
11470 - When we negotiate a v2 link-layer connection (not yet implemented),
11471 accept RELAY_EARLY cells and turn them into RELAY cells if we've
11472 negotiated a v1 connection for their next step. Initial code for
11476 Changes in version 0.2.0.11-alpha - 2007-11-12
11477 This eleventh development snapshot fixes some build problems with
11478 the previous snapshot. It also includes a more secure-by-default exit
11479 policy for relays, fixes an enormous memory leak for exit relays, and
11480 fixes another bug where servers were falling out of the directory list.
11483 - Exit policies now reject connections that are addressed to a
11484 relay's public (external) IP address too, unless
11485 ExitPolicyRejectPrivate is turned off. We do this because too
11486 many relays are running nearby to services that trust them based
11487 on network address. Bugfix on 0.1.2.x.
11490 - Fix a memory leak on exit relays; we were leaking a cached_resolve_t
11491 on every successful resolve. Reported by Mike Perry; bugfix
11493 - On authorities, never downgrade to old router descriptors simply
11494 because they're listed in the consensus. This created a catch-22
11495 where we wouldn't list a new descriptor because there was an
11496 old one in the consensus, and we couldn't get the new one in the
11497 consensus because we wouldn't list it. Possible fix for bug 548.
11498 Also, this might cause bug 543 to appear on authorities; if so,
11499 we'll need a band-aid for that. Bugfix on 0.2.0.9-alpha.
11501 o Packaging fixes on 0.2.0.10-alpha:
11502 - We were including instructions about what to do with the
11503 src/config/fallback-consensus file, but we weren't actually
11504 including it in the tarball. Disable all of that for now.
11507 - Allow people to say PreferTunnelledDirConns rather than
11508 PreferTunneledDirConns, for those alternate-spellers out there.
11511 - Don't reevaluate all the information from our consensus document
11512 just because we've downloaded a v2 networkstatus that we intend
11513 to cache. Fixes bug 545; bugfix on 0.2.0.x.
11516 Changes in version 0.2.0.10-alpha - 2007-11-10
11517 This tenth development snapshot adds a third v3 directory authority
11518 run by Mike Perry, adds most of Karsten Loesing's new hidden service
11519 descriptor format, fixes a bad crash bug and new bridge bugs introduced
11520 in 0.2.0.9-alpha, fixes many bugs with the v3 directory implementation,
11521 fixes some minor memory leaks in previous 0.2.0.x snapshots, and
11522 addresses many more minor issues.
11524 o New directory authorities:
11525 - Set up ides (run by Mike Perry) as the third v3 directory authority.
11528 - Allow tunnelled directory connections to ask for an encrypted
11529 "begin_dir" connection or an anonymized "uses a full Tor circuit"
11530 connection independently. Now we can make anonymized begin_dir
11531 connections for (e.g.) more secure hidden service posting and
11533 - More progress on proposal 114: code from Karsten Loesing to
11534 implement new hidden service descriptor format.
11535 - Raise the default BandwidthRate/BandwidthBurst to 5MB/10MB, to
11536 accommodate the growing number of servers that use the default
11537 and are reaching it.
11538 - Directory authorities use a new formula for selecting which nodes
11539 to advertise as Guards: they must be in the top 7/8 in terms of
11540 how long we have known about them, and above the median of those
11541 nodes in terms of weighted fractional uptime.
11542 - Make "not enough dir info yet" warnings describe *why* Tor feels
11543 it doesn't have enough directory info yet.
11546 - Stop servers from crashing if they set a Family option (or
11547 maybe in other situations too). Bugfix on 0.2.0.9-alpha; reported
11549 - Make bridge users work again -- the move to v3 directories in
11550 0.2.0.9-alpha had introduced a number of bugs that made bridges
11551 no longer work for clients.
11552 - When the clock jumps forward a lot, do not allow the bandwidth
11553 buckets to become negative. Bugfix on 0.1.2.x; fixes bug 544.
11555 o Major bugfixes (v3 dir, bugfixes on 0.2.0.9-alpha):
11556 - When the consensus lists a router descriptor that we previously were
11557 mirroring, but that we considered non-canonical, reload the
11558 descriptor as canonical. This fixes bug 543 where Tor servers
11559 would start complaining after a few days that they don't have
11560 enough directory information to build a circuit.
11561 - Consider replacing the current consensus when certificates arrive
11562 that make the pending consensus valid. Previously, we were only
11563 considering replacement when the new certs _didn't_ help.
11564 - Fix an assert error on startup if we didn't already have the
11565 consensus and certs cached in our datadirectory: we were caching
11566 the consensus in consensus_waiting_for_certs but then free'ing it
11568 - Avoid sending a request for "keys/fp" (for which we'll get a 400 Bad
11569 Request) if we need more v3 certs but we've already got pending
11570 requests for all of them.
11571 - Correctly back off from failing certificate downloads. Fixes
11573 - Authorities don't vote on the Running flag if they have been running
11574 for less than 30 minutes themselves. Fixes bug 547, where a newly
11575 started authority would vote that everyone was down.
11577 o New requirements:
11578 - Drop support for OpenSSL version 0.9.6. Just about nobody was using
11579 it, it had no AES, and it hasn't seen any security patches since
11583 - Clients now hold circuitless TLS connections open for 1.5 times
11584 MaxCircuitDirtiness (15 minutes), since it is likely that they'll
11585 rebuild a new circuit over them within that timeframe. Previously,
11586 they held them open only for KeepalivePeriod (5 minutes).
11587 - Use "If-Modified-Since" to avoid retrieving consensus
11588 networkstatuses that we already have.
11589 - When we have no consensus, check FallbackNetworkstatusFile (defaults
11590 to $PREFIX/share/tor/fallback-consensus) for a consensus. This way
11591 we start knowing some directory caches.
11592 - When we receive a consensus from the future, warn about skew.
11593 - Improve skew reporting: try to give the user a better log message
11594 about how skewed they are, and how much this matters.
11595 - When we have a certificate for an authority, believe that
11596 certificate's claims about the authority's IP address.
11597 - New --quiet command-line option to suppress the default console log.
11598 Good in combination with --hash-password.
11599 - Authorities send back an X-Descriptor-Not-New header in response to
11600 an accepted-but-discarded descriptor upload. Partially implements
11602 - Make the log message for "tls error. breaking." more useful.
11603 - Better log messages about certificate downloads, to attempt to
11604 track down the second incarnation of bug 546.
11606 o Minor features (bridges):
11607 - If bridge users set UpdateBridgesFromAuthority, but the digest
11608 they ask for is a 404 from the bridge authority, they now fall
11609 back to trying the bridge directly.
11610 - Bridges now use begin_dir to publish their server descriptor to
11611 the bridge authority, even when they haven't set TunnelDirConns.
11613 o Minor features (controller):
11614 - When reporting clock skew, and we know that the clock is _at least
11615 as skewed_ as some value, but we don't know the actual value,
11616 report the value as a "minimum skew."
11619 - Update linux-tor-prio.sh script to allow QoS based on the uid of
11620 the Tor process. Patch from Marco Bonetti with tweaks from Mike
11624 - Refuse to start if both ORPort and UseBridges are set. Bugfix
11625 on 0.2.0.x, suggested by Matt Edman.
11626 - Don't stop fetching descriptors when FetchUselessDescriptors is
11627 set, even if we stop asking for circuits. Bugfix on 0.1.2.x;
11628 reported by tup and ioerror.
11629 - Better log message on vote from unknown authority.
11630 - Don't log "Launching 0 request for 0 router" message.
11632 o Minor bugfixes (memory leaks):
11633 - Stop leaking memory every time we parse a v3 certificate. Bugfix
11635 - Stop leaking memory every time we load a v3 certificate. Bugfix
11636 on 0.2.0.1-alpha. Fixes bug 536.
11637 - Stop leaking a cached networkstatus on exit. Bugfix on
11639 - Stop leaking voter information every time we free a consensus.
11640 Bugfix on 0.2.0.3-alpha.
11641 - Stop leaking signed data every time we check a voter signature.
11642 Bugfix on 0.2.0.3-alpha.
11643 - Stop leaking a signature every time we fail to parse a consensus or
11644 a vote. Bugfix on 0.2.0.3-alpha.
11645 - Stop leaking v2_download_status_map on shutdown. Bugfix on
11647 - Stop leaking conn->nickname every time we make a connection to a
11648 Tor relay without knowing its expected identity digest (e.g. when
11649 using bridges). Bugfix on 0.2.0.3-alpha.
11651 - Minor bugfixes (portability):
11652 - Run correctly on platforms where rlim_t is larger than unsigned
11653 long, and/or where the real limit for number of open files is
11654 OPEN_FILES, not rlim_max from getrlimit(RLIMIT_NOFILES). In
11655 particular, these may be needed for OS X 10.5.
11658 Changes in version 0.1.2.18 - 2007-10-28
11659 Tor 0.1.2.18 fixes many problems including crash bugs, problems with
11660 hidden service introduction that were causing huge delays, and a big
11661 bug that was causing some servers to disappear from the network status
11662 lists for a few hours each day.
11664 o Major bugfixes (crashes):
11665 - If a connection is shut down abruptly because of something that
11666 happened inside connection_flushed_some(), do not call
11667 connection_finished_flushing(). Should fix bug 451:
11668 "connection_stop_writing: Assertion conn->write_event failed"
11669 Bugfix on 0.1.2.7-alpha.
11670 - Fix possible segfaults in functions called from
11671 rend_process_relay_cell().
11673 o Major bugfixes (hidden services):
11674 - Hidden services were choosing introduction points uniquely by
11675 hexdigest, but when constructing the hidden service descriptor
11676 they merely wrote the (potentially ambiguous) nickname.
11677 - Clients now use the v2 intro format for hidden service
11678 connections: they specify their chosen rendezvous point by identity
11679 digest rather than by (potentially ambiguous) nickname. These
11680 changes could speed up hidden service connections dramatically.
11682 o Major bugfixes (other):
11683 - Stop publishing a new server descriptor just because we get a
11684 HUP signal. This led (in a roundabout way) to some servers getting
11685 dropped from the networkstatus lists for a few hours each day.
11686 - When looking for a circuit to cannibalize, consider family as well
11687 as identity. Fixes bug 438. Bugfix on 0.1.0.x (which introduced
11688 circuit cannibalization).
11689 - When a router wasn't listed in a new networkstatus, we were leaving
11690 the flags for that router alone -- meaning it remained Named,
11691 Running, etc -- even though absence from the networkstatus means
11692 that it shouldn't be considered to exist at all anymore. Now we
11693 clear all the flags for routers that fall out of the networkstatus
11694 consensus. Fixes bug 529.
11697 - Don't try to access (or alter) the state file when running
11698 --list-fingerprint or --verify-config or --hash-password. Resolves
11700 - When generating information telling us how to extend to a given
11701 router, do not try to include the nickname if it is
11702 absent. Resolves bug 467.
11703 - Fix a user-triggerable segfault in expand_filename(). (There isn't
11704 a way to trigger this remotely.)
11705 - When sending a status event to the controller telling it that an
11706 OR address is reachable, set the port correctly. (Previously we
11707 were reporting the dir port.)
11708 - Fix a minor memory leak whenever a controller sends the PROTOCOLINFO
11709 command. Bugfix on 0.1.2.17.
11710 - When loading bandwidth history, do not believe any information in
11711 the future. Fixes bug 434.
11712 - When loading entry guard information, do not believe any information
11714 - When we have our clock set far in the future and generate an
11715 onion key, then re-set our clock to be correct, we should not stop
11716 the onion key from getting rotated.
11717 - On some platforms, accept() can return a broken address. Detect
11718 this more quietly, and deal accordingly. Fixes bug 483.
11719 - It's not actually an error to find a non-pending entry in the DNS
11720 cache when canceling a pending resolve. Don't log unless stuff
11721 is fishy. Resolves bug 463.
11722 - Don't reset trusted dir server list when we set a configuration
11723 option. Patch from Robert Hogan.
11724 - Don't try to create the datadir when running --verify-config or
11725 --hash-password. Resolves bug 540.
11728 Changes in version 0.2.0.9-alpha - 2007-10-24
11729 This ninth development snapshot switches clients to the new v3 directory
11730 system; allows servers to be listed in the network status even when they
11731 have the same nickname as a registered server; and fixes many other
11732 bugs including a big one that was causing some servers to disappear
11733 from the network status lists for a few hours each day.
11735 o Major features (directory system):
11736 - Clients now download v3 consensus networkstatus documents instead
11737 of v2 networkstatus documents. Clients and caches now base their
11738 opinions about routers on these consensus documents. Clients only
11739 download router descriptors listed in the consensus.
11740 - Authorities now list servers who have the same nickname as
11741 a different named server, but list them with a new flag,
11742 "Unnamed". Now we can list servers that happen to pick the same
11743 nickname as a server that registered two years ago and then
11744 disappeared. Partially implements proposal 122.
11745 - If the consensus lists a router as "Unnamed", the name is assigned
11746 to a different router: do not identify the router by that name.
11747 Partially implements proposal 122.
11748 - Authorities can now come to a consensus on which method to use to
11749 compute the consensus. This gives us forward compatibility.
11752 - Stop publishing a new server descriptor just because we HUP or
11753 when we find our DirPort to be reachable but won't actually publish
11754 it. New descriptors without any real changes are dropped by the
11755 authorities, and can screw up our "publish every 18 hours" schedule.
11757 - When a router wasn't listed in a new networkstatus, we were leaving
11758 the flags for that router alone -- meaning it remained Named,
11759 Running, etc -- even though absence from the networkstatus means
11760 that it shouldn't be considered to exist at all anymore. Now we
11761 clear all the flags for routers that fall out of the networkstatus
11762 consensus. Fixes bug 529; bugfix on 0.1.2.x.
11763 - Fix awful behavior in DownloadExtraInfo option where we'd fetch
11764 extrainfo documents and then discard them immediately for not
11765 matching the latest router. Bugfix on 0.2.0.1-alpha.
11767 o Minor features (v3 directory protocol):
11768 - Allow tor-gencert to generate a new certificate without replacing
11770 - Allow certificates to include an address.
11771 - When we change our directory-cache settings, reschedule all voting
11772 and download operations.
11773 - Reattempt certificate downloads immediately on failure, as long as
11774 we haven't failed a threshold number of times yet.
11775 - Delay retrying consensus downloads while we're downloading
11776 certificates to verify the one we just got. Also, count getting a
11777 consensus that we already have (or one that isn't valid) as a failure,
11778 and count failing to get the certificates after 20 minutes as a
11780 - Build circuits and download descriptors even if our consensus is a
11781 little expired. (This feature will go away once authorities are
11784 o Minor features (router descriptor cache):
11785 - If we find a cached-routers file that's been sitting around for more
11786 than 28 days unmodified, then most likely it's a leftover from
11787 when we upgraded to 0.2.0.8-alpha. Remove it. It has no good
11789 - When we (as a cache) download a descriptor because it was listed
11790 in a consensus, remember when the consensus was supposed to expire,
11791 and don't expire the descriptor until then.
11793 o Minor features (performance):
11794 - Call routerlist_remove_old_routers() much less often. This should
11795 speed startup, especially on directory caches.
11796 - Don't try to launch new descriptor downloads quite so often when we
11797 already have enough directory information to build circuits.
11798 - Base64 decoding was actually showing up on our profile when parsing
11799 the initial descriptor file; switch to an in-process all-at-once
11800 implementation that's about 3.5x times faster than calling out to
11803 o Minor features (compilation):
11804 - Detect non-ASCII platforms (if any still exist) and refuse to
11805 build there: some of our code assumes that 'A' is 65 and so on.
11807 o Minor bugfixes (v3 directory authorities, bugfixes on 0.2.0.x):
11808 - Make the "next period" votes into "current period" votes immediately
11809 after publishing the consensus; avoid a heisenbug that made them
11810 stick around indefinitely.
11811 - When we discard a vote as a duplicate, do not report this as
11813 - Treat missing v3 keys or certificates as an error when running as a
11814 v3 directory authority.
11815 - When we're configured to be a v3 authority, but we're only listed
11816 as a non-v3 authority in our DirServer line for ourself, correct
11818 - If an authority doesn't have a qualified hostname, just put
11819 its address in the vote. This fixes the problem where we referred to
11820 "moria on moria:9031."
11821 - Distinguish between detached signatures for the wrong period, and
11822 detached signatures for a divergent vote.
11823 - Fix a small memory leak when computing a consensus.
11824 - When there's no concensus, we were forming a vote every 30
11825 minutes, but writing the "valid-after" line in our vote based
11826 on our configured V3AuthVotingInterval: so unless the intervals
11827 matched up, we immediately rejected our own vote because it didn't
11828 start at the voting interval that caused us to construct a vote.
11830 o Minor bugfixes (v3 directory protocol, bugfixes on 0.2.0.x):
11831 - Delete unverified-consensus when the real consensus is set.
11832 - Consider retrying a consensus networkstatus fetch immediately
11833 after one fails: don't wait 60 seconds to notice.
11834 - When fetching a consensus as a cache, wait until a newer consensus
11835 should exist before trying to replace the current one.
11836 - Use a more forgiving schedule for retrying failed consensus
11837 downloads than for other types.
11839 o Minor bugfixes (other directory issues):
11840 - Correct the implementation of "download votes by digest." Bugfix on
11842 - Authorities no longer send back "400 you're unreachable please fix
11843 it" errors to Tor servers that aren't online all the time. We're
11844 supposed to tolerate these servers now. Bugfix on 0.1.2.x.
11846 o Minor bugfixes (controller):
11847 - Don't reset trusted dir server list when we set a configuration
11848 option. Patch from Robert Hogan; bugfix on 0.1.2.x.
11849 - Respond to INT and TERM SIGNAL commands before we execute the
11850 signal, in case the signal shuts us down. We had a patch in
11851 0.1.2.1-alpha that tried to do this by queueing the response on
11852 the connection's buffer before shutting down, but that really
11853 isn't the same thing at all. Bug located by Matt Edman.
11855 o Minor bugfixes (misc):
11856 - Correctly check for bad options to the "PublishServerDescriptor"
11857 config option. Bugfix on 0.2.0.1-alpha; reported by Matt Edman.
11858 - Stop leaking memory on failing case of base32_decode, and make
11859 it accept upper-case letters. Bugfixes on 0.2.0.7-alpha.
11860 - Don't try to download extrainfo documents when we're trying to
11861 fetch enough directory info to build a circuit: having enough
11862 info should get priority. Bugfix on 0.2.0.x.
11863 - Don't complain that "your server has not managed to confirm that its
11864 ports are reachable" if we haven't been able to build any circuits
11865 yet. Bug found by spending four hours without a v3 consensus. Bugfix
11867 - Detect the reason for failing to mmap a descriptor file we just
11868 wrote, and give a more useful log message. Fixes bug 533. Bugfix
11871 o Code simplifications and refactoring:
11872 - Remove support for the old bw_accounting file: we've been storing
11873 bandwidth accounting information in the state file since
11874 0.1.2.5-alpha. This may result in bandwidth accounting errors
11875 if you try to upgrade from 0.1.1.x or earlier, or if you try to
11876 downgrade to 0.1.1.x or earlier.
11877 - New convenience code to locate a file within the DataDirectory.
11878 - Move non-authority functionality out of dirvote.c.
11879 - Refactor the arguments for router_pick_{directory_|trusteddir}server
11880 so that they all take the same named flags.
11883 - Include the "tor-ctrl.sh" bash script by Stefan Behte to provide
11884 Unix users an easy way to script their Tor process (e.g. by
11885 adjusting bandwidth based on the time of the day).
11888 Changes in version 0.2.0.8-alpha - 2007-10-12
11889 This eighth development snapshot fixes a crash bug that's been bothering
11890 us since February 2007, lets bridge authorities store a list of bridge
11891 descriptors they've seen, gets v3 directory voting closer to working,
11892 starts caching v3 directory consensus documents on directory mirrors,
11893 and fixes a variety of smaller issues including some minor memory leaks.
11895 o Major features (router descriptor cache):
11896 - Store routers in a file called cached-descriptors instead of in
11897 cached-routers. Initialize cached-descriptors from cached-routers
11898 if the old format is around. The new format allows us to store
11899 annotations along with descriptors.
11900 - Use annotations to record the time we received each descriptor, its
11901 source, and its purpose.
11902 - Disable the SETROUTERPURPOSE controller command: it is now
11904 - Controllers should now specify cache=no or cache=yes when using
11905 the +POSTDESCRIPTOR command.
11906 - Bridge authorities now write bridge descriptors to disk, meaning
11907 we can export them to other programs and begin distributing them
11910 o Major features (directory authorities):
11911 - When a v3 authority is missing votes or signatures, it now tries
11913 - Directory authorities track weighted fractional uptime as well as
11914 weighted mean-time-between failures. WFU is suitable for deciding
11915 whether a node is "usually up", while MTBF is suitable for deciding
11916 whether a node is "likely to stay up." We need both, because
11917 "usually up" is a good requirement for guards, while "likely to
11918 stay up" is a good requirement for long-lived connections.
11920 o Major features (v3 directory system):
11921 - Caches now download v3 network status documents as needed,
11922 and download the descriptors listed in them.
11923 - All hosts now attempt to download and keep fresh v3 authority
11924 certificates, and re-attempt after failures.
11925 - More internal-consistency checks for vote parsing.
11927 o Major bugfixes (crashes):
11928 - If a connection is shut down abruptly because of something that
11929 happened inside connection_flushed_some(), do not call
11930 connection_finished_flushing(). Should fix bug 451. Bugfix on
11933 o Major bugfixes (performance):
11934 - Fix really bad O(n^2) performance when parsing a long list of
11935 routers: Instead of searching the entire list for an "extra-info "
11936 string which usually wasn't there, once for every routerinfo
11937 we read, just scan lines forward until we find one we like.
11939 - When we add data to a write buffer in response to the data on that
11940 write buffer getting low because of a flush, do not consider the
11941 newly added data as a candidate for immediate flushing, but rather
11942 make it wait until the next round of writing. Otherwise, we flush
11943 and refill recursively, and a single greedy TLS connection can
11944 eat all of our bandwidth. Bugfix on 0.1.2.7-alpha.
11946 o Minor features (v3 authority system):
11947 - Add more ways for tools to download the votes that lead to the
11949 - Send a 503 when low on bandwidth and a vote, consensus, or
11950 certificate is requested.
11951 - If-modified-since is now implemented properly for all kinds of
11952 certificate requests.
11954 o Minor bugfixes (network statuses):
11955 - Tweak the implementation of proposal 109 slightly: allow at most
11956 two Tor servers on the same IP address, except if it's the location
11957 of a directory authority, in which case allow five. Bugfix on
11960 o Minor bugfixes (controller):
11961 - When sending a status event to the controller telling it that an
11962 OR address is reachable, set the port correctly. (Previously we
11963 were reporting the dir port.) Bugfix on 0.1.2.x.
11965 o Minor bugfixes (v3 directory system):
11966 - Fix logic to look up a cert by its signing key digest. Bugfix on
11968 - Only change the reply to a vote to "OK" if it's not already
11969 set. This gets rid of annoying "400 OK" log messages, which may
11970 have been masking some deeper issue. Bugfix on 0.2.0.7-alpha.
11971 - When we get a valid consensus, recompute the voting schedule.
11972 - Base the valid-after time of a vote on the consensus voting
11973 schedule, not on our preferred schedule.
11974 - Make the return values and messages from signature uploads and
11975 downloads more sensible.
11976 - Fix a memory leak when serving votes and consensus documents, and
11977 another when serving certificates.
11979 o Minor bugfixes (performance):
11980 - Use a slightly simpler string hashing algorithm (copying Python's
11981 instead of Java's) and optimize our digest hashing algorithm to take
11982 advantage of 64-bit platforms and to remove some possibly-costly
11984 - Fix a minor memory leak whenever we parse guards from our state
11985 file. Bugfix on 0.2.0.7-alpha.
11986 - Fix a minor memory leak whenever we write out a file. Bugfix on
11988 - Fix a minor memory leak whenever a controller sends the PROTOCOLINFO
11989 command. Bugfix on 0.2.0.5-alpha.
11991 o Minor bugfixes (portability):
11992 - On some platforms, accept() can return a broken address. Detect
11993 this more quietly, and deal accordingly. Fixes bug 483.
11994 - Stop calling tor_strlower() on uninitialized memory in some cases.
11995 Bugfix in 0.2.0.7-alpha.
11997 o Minor bugfixes (usability):
11998 - Treat some 403 responses from directory servers as INFO rather than
11999 WARN-severity events.
12000 - It's not actually an error to find a non-pending entry in the DNS
12001 cache when canceling a pending resolve. Don't log unless stuff is
12002 fishy. Resolves bug 463.
12004 o Minor bugfixes (anonymity):
12005 - Never report that we've used more bandwidth than we're willing to
12006 relay: it leaks how much non-relay traffic we're using. Resolves
12008 - When looking for a circuit to cannibalize, consider family as well
12009 as identity. Fixes bug 438. Bugfix on 0.1.0.x (which introduced
12010 circuit cannibalization).
12012 o Code simplifications and refactoring:
12013 - Make a bunch of functions static. Remove some dead code.
12014 - Pull out about a third of the really big routerlist.c; put it in a
12015 new module, networkstatus.c.
12016 - Merge the extra fields in local_routerstatus_t back into
12017 routerstatus_t: we used to need one routerstatus_t for each
12018 authority's opinion, plus a local_routerstatus_t for the locally
12019 computed consensus opinion. To save space, we put the locally
12020 modified fields into local_routerstatus_t, and only the common
12021 stuff into routerstatus_t. But once v3 directories are in use,
12022 clients and caches will no longer need to hold authority opinions;
12023 thus, the rationale for keeping the types separate is now gone.
12024 - Make the code used to reschedule and reattempt downloads more
12026 - Turn all 'Are we a directory server/mirror?' logic into a call to
12028 - Remove the code to generate the oldest (v1) directory format.
12029 The code has been disabled since 0.2.0.5-alpha.
12032 Changes in version 0.2.0.7-alpha - 2007-09-21
12033 This seventh development snapshot makes bridges work again, makes bridge
12034 authorities work for the first time, fixes two huge performance flaws
12035 in hidden services, and fixes a variety of minor issues.
12037 o New directory authorities:
12038 - Set up moria1 and tor26 as the first v3 directory authorities. See
12039 doc/spec/dir-spec.txt for details on the new directory design.
12041 o Major bugfixes (crashes):
12042 - Fix possible segfaults in functions called from
12043 rend_process_relay_cell(). Bugfix on 0.1.2.x.
12045 o Major bugfixes (bridges):
12046 - Fix a bug that made servers send a "404 Not found" in response to
12047 attempts to fetch their server descriptor. This caused Tor servers
12048 to take many minutes to establish reachability for their DirPort,
12049 and it totally crippled bridges. Bugfix on 0.2.0.5-alpha.
12050 - Make "UpdateBridgesFromAuthority" torrc option work: when bridge
12051 users configure that and specify a bridge with an identity
12052 fingerprint, now they will lookup the bridge descriptor at the
12053 default bridge authority via a one-hop tunnel, but once circuits
12054 are established they will switch to a three-hop tunnel for later
12055 connections to the bridge authority. Bugfix in 0.2.0.3-alpha.
12057 o Major bugfixes (hidden services):
12058 - Hidden services were choosing introduction points uniquely by
12059 hexdigest, but when constructing the hidden service descriptor
12060 they merely wrote the (potentially ambiguous) nickname.
12061 - Clients now use the v2 intro format for hidden service
12062 connections: they specify their chosen rendezvous point by identity
12063 digest rather than by (potentially ambiguous) nickname. Both
12064 are bugfixes on 0.1.2.x, and they could speed up hidden service
12065 connections dramatically. Thanks to Karsten Loesing.
12067 o Minor features (security):
12068 - As a client, do not believe any server that tells us that an
12069 address maps to an internal address space.
12070 - Make it possible to enable HashedControlPassword and
12071 CookieAuthentication at the same time.
12073 o Minor features (guard nodes):
12074 - Tag every guard node in our state file with the version that
12075 we believe added it, or with our own version if we add it. This way,
12076 if a user temporarily runs an old version of Tor and then switches
12077 back to a new one, she doesn't automatically lose her guards.
12079 o Minor features (speed):
12080 - When implementing AES counter mode, update only the portions of the
12081 counter buffer that need to change, and don't keep separate
12082 network-order and host-order counters when they are the same (i.e.,
12083 on big-endian hosts.)
12085 o Minor features (controller):
12086 - Accept LF instead of CRLF on controller, since some software has a
12087 hard time generating real Internet newlines.
12088 - Add GETINFO values for the server status events
12089 "REACHABILITY_SUCCEEDED" and "GOOD_SERVER_DESCRIPTOR". Patch from
12092 o Removed features:
12093 - Routers no longer include bandwidth-history lines in their
12094 descriptors; this information is already available in extra-info
12095 documents, and including it in router descriptors took up 60%
12096 (!) of compressed router descriptor downloads. Completes
12097 implementation of proposal 104.
12098 - Remove the contrib scripts ExerciseServer.py, PathDemo.py,
12099 and TorControl.py, as they use the old v0 controller protocol,
12100 and are obsoleted by TorFlow anyway.
12101 - Drop support for v1 rendezvous descriptors, since we never used
12102 them anyway, and the code has probably rotted by now. Based on
12103 patch from Karsten Loesing.
12104 - On OSX, stop warning the user that kqueue support in libevent is
12105 "experimental", since it seems to have worked fine for ages.
12108 - When generating information telling us how to extend to a given
12109 router, do not try to include the nickname if it is absent. Fixes
12110 bug 467. Bugfix on 0.2.0.3-alpha.
12111 - Fix a user-triggerable (but not remotely-triggerable) segfault
12112 in expand_filename(). Bugfix on 0.1.2.x.
12113 - Fix a memory leak when freeing incomplete requests from DNSPort.
12114 Found by Niels Provos with valgrind. Bugfix on 0.2.0.1-alpha.
12115 - Don't try to access (or alter) the state file when running
12116 --list-fingerprint or --verify-config or --hash-password. (Resolves
12117 bug 499.) Bugfix on 0.1.2.x.
12118 - Servers used to decline to publish their DirPort if their
12119 BandwidthRate, RelayBandwidthRate, or MaxAdvertisedBandwidth
12120 were below a threshold. Now they only look at BandwidthRate and
12121 RelayBandwidthRate. Bugfix on 0.1.2.x.
12122 - Remove an optimization in the AES counter-mode code that assumed
12123 that the counter never exceeded 2^68. When the counter can be set
12124 arbitrarily as an IV (as it is by Karsten's new hidden services
12125 code), this assumption no longer holds. Bugfix on 0.1.2.x.
12126 - Resume listing "AUTHORITY" flag for authorities in network status.
12127 Bugfix on 0.2.0.3-alpha; reported by Alex de Joode.
12129 o Code simplifications and refactoring:
12130 - Revamp file-writing logic so we don't need to have the entire
12131 contents of a file in memory at once before we write to disk. Tor,
12133 - Turn "descriptor store" into a full-fledged type.
12134 - Move all NT services code into a separate source file.
12135 - Unify all code that computes medians, percentile elements, etc.
12136 - Get rid of a needless malloc when parsing address policies.
12139 Changes in version 0.1.2.17 - 2007-08-30
12140 Tor 0.1.2.17 features a new Vidalia version in the Windows and OS
12141 X bundles. Vidalia 0.0.14 makes authentication required for the
12142 ControlPort in the default configuration, which addresses important
12143 security risks. Everybody who uses Vidalia (or another controller)
12146 In addition, this Tor update fixes major load balancing problems with
12147 path selection, which should speed things up a lot once many people
12150 o Major bugfixes (security):
12151 - We removed support for the old (v0) control protocol. It has been
12152 deprecated since Tor 0.1.1.1-alpha, and keeping it secure has
12153 become more of a headache than it's worth.
12155 o Major bugfixes (load balancing):
12156 - When choosing nodes for non-guard positions, weight guards
12157 proportionally less, since they already have enough load. Patch
12159 - Raise the "max believable bandwidth" from 1.5MB/s to 10MB/s. This
12160 will allow fast Tor servers to get more attention.
12161 - When we're upgrading from an old Tor version, forget our current
12162 guards and pick new ones according to the new weightings. These
12163 three load balancing patches could raise effective network capacity
12164 by a factor of four. Thanks to Mike Perry for measurements.
12166 o Major bugfixes (stream expiration):
12167 - Expire not-yet-successful application streams in all cases if
12168 they've been around longer than SocksTimeout. Right now there are
12169 some cases where the stream will live forever, demanding a new
12170 circuit every 15 seconds. Fixes bug 454; reported by lodger.
12172 o Minor features (controller):
12173 - Add a PROTOCOLINFO controller command. Like AUTHENTICATE, it
12174 is valid before any authentication has been received. It tells
12175 a controller what kind of authentication is expected, and what
12176 protocol is spoken. Implements proposal 119.
12178 o Minor bugfixes (performance):
12179 - Save on most routerlist_assert_ok() calls in routerlist.c, thus
12180 greatly speeding up loading cached-routers from disk on startup.
12181 - Disable sentinel-based debugging for buffer code: we squashed all
12182 the bugs that this was supposed to detect a long time ago, and now
12183 its only effect is to change our buffer sizes from nice powers of
12184 two (which platform mallocs tend to like) to values slightly over
12185 powers of two (which make some platform mallocs sad).
12187 o Minor bugfixes (misc):
12188 - If exit bandwidth ever exceeds one third of total bandwidth, then
12189 use the correct formula to weight exit nodes when choosing paths.
12190 Based on patch from Mike Perry.
12191 - Choose perfectly fairly among routers when choosing by bandwidth and
12192 weighting by fraction of bandwidth provided by exits. Previously, we
12193 would choose with only approximate fairness, and correct ourselves
12194 if we ran off the end of the list.
12195 - If we require CookieAuthentication but we fail to write the
12196 cookie file, we would warn but not exit, and end up in a state
12197 where no controller could authenticate. Now we exit.
12198 - If we require CookieAuthentication, stop generating a new cookie
12199 every time we change any piece of our config.
12200 - Refuse to start with certain directory authority keys, and
12201 encourage people using them to stop.
12202 - Terminate multi-line control events properly. Original patch
12204 - Fix a minor memory leak when we fail to find enough suitable
12205 servers to choose a circuit.
12206 - Stop leaking part of the descriptor when we run into a particularly
12207 unparseable piece of it.
12210 Changes in version 0.2.0.6-alpha - 2007-08-26
12211 This sixth development snapshot features a new Vidalia version in the
12212 Windows and OS X bundles. Vidalia 0.0.14 makes authentication required for
12213 the ControlPort in the default configuration, which addresses important
12216 In addition, this snapshot fixes major load balancing problems
12217 with path selection, which should speed things up a lot once many
12218 people have upgraded. The directory authorities also use a new
12219 mean-time-between-failure approach to tracking which servers are stable,
12220 rather than just looking at the most recent uptime.
12222 o New directory authorities:
12223 - Set up Tonga as the default bridge directory authority.
12226 - Directory authorities now track servers by weighted
12227 mean-times-between-failures. When we have 4 or more days of data,
12228 use measured MTBF rather than declared uptime to decide whether
12229 to call a router Stable. Implements proposal 108.
12231 o Major bugfixes (load balancing):
12232 - When choosing nodes for non-guard positions, weight guards
12233 proportionally less, since they already have enough load. Patch
12235 - Raise the "max believable bandwidth" from 1.5MB/s to 10MB/s. This
12236 will allow fast Tor servers to get more attention.
12237 - When we're upgrading from an old Tor version, forget our current
12238 guards and pick new ones according to the new weightings. These
12239 three load balancing patches could raise effective network capacity
12240 by a factor of four. Thanks to Mike Perry for measurements.
12242 o Major bugfixes (descriptor parsing):
12243 - Handle unexpected whitespace better in malformed descriptors. Bug
12244 found using Benedikt Boss's new Tor fuzzer! Bugfix on 0.2.0.x.
12247 - There is now an ugly, temporary "desc/all-recent-extrainfo-hack"
12248 GETINFO for Torstat to use until it can switch to using extrainfos.
12249 - Optionally (if built with -DEXPORTMALLINFO) export the output
12250 of mallinfo via http, as tor/mallinfo.txt. Only accessible
12254 - Do not intermix bridge routers with controller-added
12255 routers. (Bugfix on 0.2.0.x)
12256 - Do not fail with an assert when accept() returns an unexpected
12257 address family. Addresses but does not wholly fix bug 483. (Bugfix
12259 - Let directory authorities startup even when they can't generate
12260 a descriptor immediately, e.g. because they don't know their
12262 - Stop putting the authentication cookie in a file called "0"
12263 in your working directory if you don't specify anything for the
12264 new CookieAuthFile option. Reported by Matt Edman.
12265 - Make it possible to read the PROTOCOLINFO response in a way that
12266 conforms to our control-spec. Reported by Matt Edman.
12267 - Fix a minor memory leak when we fail to find enough suitable
12268 servers to choose a circuit. Bugfix on 0.1.2.x.
12269 - Stop leaking part of the descriptor when we run into a particularly
12270 unparseable piece of it. Bugfix on 0.1.2.x.
12271 - Unmap the extrainfo cache file on exit.
12274 Changes in version 0.2.0.5-alpha - 2007-08-19
12275 This fifth development snapshot fixes compilation on Windows again;
12276 fixes an obnoxious client-side bug that slowed things down and put
12277 extra load on the network; gets us closer to using the v3 directory
12278 voting scheme; makes it easier for Tor controllers to use cookie-based
12279 authentication; and fixes a variety of other bugs.
12281 o Removed features:
12282 - Version 1 directories are no longer generated in full. Instead,
12283 authorities generate and serve "stub" v1 directories that list
12284 no servers. This will stop Tor versions 0.1.0.x and earlier from
12285 working, but (for security reasons) nobody should be running those
12288 o Major bugfixes (compilation, 0.2.0.x):
12289 - Try to fix Win32 compilation again: improve checking for IPv6 types.
12290 - Try to fix MSVC compilation: build correctly on platforms that do
12291 not define s6_addr16 or s6_addr32.
12292 - Fix compile on platforms without getaddrinfo: bug found by Li-Hui
12295 o Major bugfixes (stream expiration):
12296 - Expire not-yet-successful application streams in all cases if
12297 they've been around longer than SocksTimeout. Right now there are
12298 some cases where the stream will live forever, demanding a new
12299 circuit every 15 seconds. Bugfix on 0.1.2.7-alpha; fixes bug 454;
12300 reported by lodger.
12302 o Minor features (directory servers):
12303 - When somebody requests a list of statuses or servers, and we have
12304 none of those, return a 404 rather than an empty 200.
12306 o Minor features (directory voting):
12307 - Store v3 consensus status consensuses on disk, and reload them
12310 o Minor features (security):
12311 - Warn about unsafe ControlPort configurations.
12312 - Refuse to start with certain directory authority keys, and
12313 encourage people using them to stop.
12315 o Minor features (controller):
12316 - Add a PROTOCOLINFO controller command. Like AUTHENTICATE, it
12317 is valid before any authentication has been received. It tells
12318 a controller what kind of authentication is expected, and what
12319 protocol is spoken. Implements proposal 119.
12320 - New config option CookieAuthFile to choose a new location for the
12321 cookie authentication file, and config option
12322 CookieAuthFileGroupReadable to make it group-readable.
12324 o Minor features (unit testing):
12325 - Add command-line arguments to unit-test executable so that we can
12326 invoke any chosen test from the command line rather than having
12327 to run the whole test suite at once; and so that we can turn on
12328 logging for the unit tests.
12330 o Minor bugfixes (on 0.1.2.x):
12331 - If we require CookieAuthentication but we fail to write the
12332 cookie file, we would warn but not exit, and end up in a state
12333 where no controller could authenticate. Now we exit.
12334 - If we require CookieAuthentication, stop generating a new cookie
12335 every time we change any piece of our config.
12336 - When loading bandwidth history, do not believe any information in
12337 the future. Fixes bug 434.
12338 - When loading entry guard information, do not believe any information
12340 - When we have our clock set far in the future and generate an
12341 onion key, then re-set our clock to be correct, we should not stop
12342 the onion key from getting rotated.
12343 - Clean up torrc sample config file.
12344 - Do not automatically run configure from autogen.sh. This
12345 non-standard behavior tended to annoy people who have built other
12348 o Minor bugfixes (on 0.2.0.x):
12349 - Fix a bug with AutomapHostsOnResolve that would always cause
12350 the second request to fail. Bug reported by Kate. Bugfix on
12352 - Fix a bug in ADDRMAP controller replies that would sometimes
12353 try to print a NULL. Patch from tup.
12354 - Read v3 directory authority keys from the right location.
12355 - Numerous bugfixes to directory voting code.
12358 Changes in version 0.1.2.16 - 2007-08-01
12359 Tor 0.1.2.16 fixes a critical security vulnerability that allows a
12360 remote attacker in certain situations to rewrite the user's torrc
12361 configuration file. This can completely compromise anonymity of users
12362 in most configurations, including those running the Vidalia bundles,
12363 TorK, etc. Or worse.
12365 o Major security fixes:
12366 - Close immediately after missing authentication on control port;
12367 do not allow multiple authentication attempts.
12370 Changes in version 0.2.0.4-alpha - 2007-08-01
12371 This fourth development snapshot fixes a critical security vulnerability
12372 for most users, specifically those running Vidalia, TorK, etc. Everybody
12373 should upgrade to either 0.1.2.16 or 0.2.0.4-alpha.
12375 o Major security fixes:
12376 - Close immediately after missing authentication on control port;
12377 do not allow multiple authentication attempts.
12379 o Major bugfixes (compilation):
12380 - Fix win32 compilation: apparently IN_ADDR and IN6_ADDR are already
12383 o Minor features (performance):
12384 - Be even more aggressive about releasing RAM from small
12385 empty buffers. Thanks to our free-list code, this shouldn't be too
12386 performance-intensive.
12387 - Disable sentinel-based debugging for buffer code: we squashed all
12388 the bugs that this was supposed to detect a long time ago, and
12389 now its only effect is to change our buffer sizes from nice
12390 powers of two (which platform mallocs tend to like) to values
12391 slightly over powers of two (which make some platform mallocs sad).
12392 - Log malloc statistics from mallinfo() on platforms where it
12396 Changes in version 0.2.0.3-alpha - 2007-07-29
12397 This third development snapshot introduces new experimental
12398 blocking-resistance features and a preliminary version of the v3
12399 directory voting design, and includes many other smaller features
12403 - The first pieces of our "bridge" design for blocking-resistance
12404 are implemented. People can run bridge directory authorities;
12405 people can run bridges; and people can configure their Tor clients
12406 with a set of bridges to use as the first hop into the Tor network.
12407 See http://archives.seul.org/or/talk/Jul-2007/msg00249.html for
12409 - Create listener connections before we setuid to the configured
12410 User and Group. Now non-Windows users can choose port values
12411 under 1024, start Tor as root, and have Tor bind those ports
12412 before it changes to another UID. (Windows users could already
12414 - Added a new ConstrainedSockets config option to set SO_SNDBUF and
12415 SO_RCVBUF on TCP sockets. Hopefully useful for Tor servers running
12416 on "vserver" accounts. (Patch from coderman.)
12417 - Be even more aggressive about separating local traffic from relayed
12418 traffic when RelayBandwidthRate is set. (Refines proposal 111.)
12420 o Major features (experimental):
12421 - First cut of code for "v3 dir voting": directory authorities will
12422 vote on a common network status document rather than each publishing
12423 their own opinion. This code needs more testing and more corner-case
12424 handling before it's ready for use.
12427 - Directory authorities now call routers Fast if their bandwidth is
12428 at least 100KB/s, and consider their bandwidth adequate to be a
12429 Guard if it is at least 250KB/s, no matter the medians. This fix
12430 complements proposal 107. [Bugfix on 0.1.2.x]
12431 - Directory authorities now never mark more than 3 servers per IP as
12432 Valid and Running. (Implements proposal 109, by Kevin Bauer and
12434 - Minor change to organizationName and commonName generation
12435 procedures in TLS certificates during Tor handshakes, to invalidate
12436 some earlier censorware approaches. This is not a long-term
12437 solution, but applying it will give us a bit of time to look into
12438 the epidemiology of countermeasures as they spread.
12440 o Major bugfixes (directory):
12441 - Rewrite directory tokenization code to never run off the end of
12442 a string. Fixes bug 455. Patch from croup. [Bugfix on 0.1.2.x]
12444 o Minor features (controller):
12445 - Add a SOURCE_ADDR field to STREAM NEW events so that controllers can
12446 match requests to applications. (Patch from Robert Hogan.)
12447 - Report address and port correctly on connections to DNSPort. (Patch
12448 from Robert Hogan.)
12449 - Add a RESOLVE command to launch hostname lookups. (Original patch
12450 from Robert Hogan.)
12451 - Add GETINFO status/enough-dir-info to let controllers tell whether
12452 Tor has downloaded sufficient directory information. (Patch
12454 - You can now use the ControlSocket option to tell Tor to listen for
12455 controller connections on Unix domain sockets on systems that
12456 support them. (Patch from Peter Palfrader.)
12457 - STREAM NEW events are generated for DNSPort requests and for
12458 tunneled directory connections. (Patch from Robert Hogan.)
12459 - New "GETINFO address-mappings/*" command to get address mappings
12460 with expiry information. "addr-mappings/*" is now deprecated.
12463 o Minor features (misc):
12464 - Merge in some (as-yet-unused) IPv6 address manipulation code. (Patch
12466 - The tor-gencert tool for v3 directory authorities now creates all
12467 files as readable to the file creator only, and write-protects
12468 the authority identity key.
12469 - When dumping memory usage, list bytes used in buffer memory
12471 - When running with dmalloc, dump more stats on hup and on exit.
12472 - Directory authorities now fail quickly and (relatively) harmlessly
12473 if they generate a network status document that is somehow
12476 o Traffic load balancing improvements:
12477 - If exit bandwidth ever exceeds one third of total bandwidth, then
12478 use the correct formula to weight exit nodes when choosing paths.
12479 (Based on patch from Mike Perry.)
12480 - Choose perfectly fairly among routers when choosing by bandwidth and
12481 weighting by fraction of bandwidth provided by exits. Previously, we
12482 would choose with only approximate fairness, and correct ourselves
12483 if we ran off the end of the list. [Bugfix on 0.1.2.x]
12485 o Performance improvements:
12486 - Be more aggressive with freeing buffer RAM or putting it on the
12488 - Use Critical Sections rather than Mutexes for synchronizing threads
12489 on win32; Mutexes are heavier-weight, and designed for synchronizing
12492 o Deprecated and removed features:
12493 - RedirectExits is now deprecated.
12494 - Stop allowing address masks that do not correspond to bit prefixes.
12495 We have warned about these for a really long time; now it's time
12496 to reject them. (Patch from croup.)
12498 o Minor bugfixes (directory):
12499 - Fix another crash bug related to extra-info caching. (Bug found by
12500 Peter Palfrader.) [Bugfix on 0.2.0.2-alpha]
12501 - Directories no longer return a "304 not modified" when they don't
12502 have the networkstatus the client asked for. Also fix a memory
12503 leak when returning 304 not modified. [Bugfixes on 0.2.0.2-alpha]
12504 - We had accidentally labelled 0.1.2.x directory servers as not
12505 suitable for begin_dir requests, and had labelled no directory
12506 servers as suitable for uploading extra-info documents. [Bugfix
12509 o Minor bugfixes (dns):
12510 - Fix a crash when DNSPort is set more than once. (Patch from Robert
12511 Hogan.) [Bugfix on 0.2.0.2-alpha]
12512 - Add DNSPort connections to the global connection list, so that we
12513 can time them out correctly. (Bug found by Robert Hogan.) [Bugfix
12515 - Fix a dangling reference that could lead to a crash when DNSPort is
12516 changed or closed (Patch from Robert Hogan.) [Bugfix on
12519 o Minor bugfixes (controller):
12520 - Provide DNS expiry times in GMT, not in local time. For backward
12521 compatibility, ADDRMAP events only provide GMT expiry in an extended
12522 field. "GETINFO address-mappings" always does the right thing.
12523 - Use CRLF line endings properly in NS events.
12524 - Terminate multi-line control events properly. (Original patch
12525 from tup.) [Bugfix on 0.1.2.x-alpha]
12526 - Do not include spaces in SOURCE_ADDR fields in STREAM
12527 events. Resolves bug 472. [Bugfix on 0.2.0.x-alpha]
12530 Changes in version 0.1.2.15 - 2007-07-17
12531 Tor 0.1.2.15 fixes several crash bugs, fixes some anonymity-related
12532 problems, fixes compilation on BSD, and fixes a variety of other
12533 bugs. Everybody should upgrade.
12535 o Major bugfixes (compilation):
12536 - Fix compile on FreeBSD/NetBSD/OpenBSD. Oops.
12538 o Major bugfixes (crashes):
12539 - Try even harder not to dereference the first character after
12540 an mmap(). Reported by lodger.
12541 - Fix a crash bug in directory authorities when we re-number the
12542 routerlist while inserting a new router.
12543 - When the cached-routers file is an even multiple of the page size,
12544 don't run off the end and crash. (Fixes bug 455; based on idea
12546 - Fix eventdns.c behavior on Solaris: It is critical to include
12547 orconfig.h _before_ sys/types.h, so that we can get the expected
12548 definition of _FILE_OFFSET_BITS.
12550 o Major bugfixes (security):
12551 - Fix a possible buffer overrun when using BSD natd support. Bug
12553 - When sending destroy cells from a circuit's origin, don't include
12554 the reason for tearing down the circuit. The spec says we didn't,
12555 and now we actually don't. Reported by lodger.
12556 - Keep streamids from different exits on a circuit separate. This
12557 bug may have allowed other routers on a given circuit to inject
12558 cells into streams. Reported by lodger; fixes bug 446.
12559 - If there's a never-before-connected-to guard node in our list,
12560 never choose any guards past it. This way we don't expand our
12561 guard list unless we need to.
12563 o Minor bugfixes (guard nodes):
12564 - Weight guard selection by bandwidth, so that low-bandwidth nodes
12565 don't get overused as guards.
12567 o Minor bugfixes (directory):
12568 - Correctly count the number of authorities that recommend each
12569 version. Previously, we were under-counting by 1.
12570 - Fix a potential crash bug when we load many server descriptors at
12571 once and some of them make others of them obsolete. Fixes bug 458.
12573 o Minor bugfixes (hidden services):
12574 - Stop tearing down the whole circuit when the user asks for a
12575 connection to a port that the hidden service didn't configure.
12578 o Minor bugfixes (misc):
12579 - On Windows, we were preventing other processes from reading
12580 cached-routers while Tor was running. Reported by janbar.
12581 - Fix a possible (but very unlikely) bug in picking routers by
12582 bandwidth. Add a log message to confirm that it is in fact
12583 unlikely. Patch from lodger.
12584 - Backport a couple of memory leak fixes.
12585 - Backport miscellaneous cosmetic bugfixes.
12588 Changes in version 0.2.0.2-alpha - 2007-06-02
12589 o Major bugfixes on 0.2.0.1-alpha:
12590 - Fix an assertion failure related to servers without extra-info digests.
12591 Resolves bugs 441 and 442.
12593 o Minor features (directory):
12594 - Support "If-Modified-Since" when answering HTTP requests for
12595 directories, running-routers documents, and network-status documents.
12596 (There's no need to support it for router descriptors, since those
12597 are downloaded by descriptor digest.)
12599 o Minor build issues:
12600 - Clear up some MIPSPro compiler warnings.
12601 - When building from a tarball on a machine that happens to have SVK
12602 installed, report the micro-revision as whatever version existed
12603 in the tarball, not as "x".
12606 Changes in version 0.2.0.1-alpha - 2007-06-01
12607 This early development snapshot provides new features for people running
12608 Tor as both a client and a server (check out the new RelayBandwidth
12609 config options); lets Tor run as a DNS proxy; and generally moves us
12610 forward on a lot of fronts.
12612 o Major features, server usability:
12613 - New config options RelayBandwidthRate and RelayBandwidthBurst:
12614 a separate set of token buckets for relayed traffic. Right now
12615 relayed traffic is defined as answers to directory requests, and
12616 OR connections that don't have any local circuits on them.
12618 o Major features, client usability:
12619 - A client-side DNS proxy feature to replace the need for
12620 dns-proxy-tor: Just set "DNSPort 9999", and Tor will now listen
12621 for DNS requests on port 9999, use the Tor network to resolve them
12622 anonymously, and send the reply back like a regular DNS server.
12623 The code still only implements a subset of DNS.
12624 - Make PreferTunneledDirConns and TunnelDirConns work even when
12625 we have no cached directory info. This means Tor clients can now
12626 do all of their connections protected by TLS.
12628 o Major features, performance and efficiency:
12629 - Directory authorities accept and serve "extra info" documents for
12630 routers. These documents contain fields from router descriptors
12631 that aren't usually needed, and that use a lot of excess
12632 bandwidth. Once these fields are removed from router descriptors,
12633 the bandwidth savings should be about 60%. [Partially implements
12635 - Servers upload extra-info documents to any authority that accepts
12636 them. Authorities (and caches that have been configured to download
12637 extra-info documents) download them as needed. [Partially implements
12639 - Change the way that Tor buffers data that it is waiting to write.
12640 Instead of queueing data cells in an enormous ring buffer for each
12641 client->OR or OR->OR connection, we now queue cells on a separate
12642 queue for each circuit. This lets us use less slack memory, and
12643 will eventually let us be smarter about prioritizing different kinds
12645 - Use memory pools to allocate cells with better speed and memory
12646 efficiency, especially on platforms where malloc() is inefficient.
12647 - Stop reading on edge connections when their corresponding circuit
12648 buffers are full; start again as the circuits empty out.
12650 o Major features, other:
12651 - Add an HSAuthorityRecordStats option that hidden service authorities
12652 can use to track statistics of overall hidden service usage without
12653 logging information that would be very useful to an attacker.
12654 - Start work implementing multi-level keys for directory authorities:
12655 Add a standalone tool to generate key certificates. (Proposal 103.)
12658 - Directory authorities now call routers Stable if they have an
12659 uptime of at least 30 days, even if that's not the median uptime
12660 in the network. Implements proposal 107, suggested by Kevin Bauer
12663 o Minor fixes (resource management):
12664 - Count the number of open sockets separately from the number
12665 of active connection_t objects. This will let us avoid underusing
12666 our allocated connection limit.
12667 - We no longer use socket pairs to link an edge connection to an
12668 anonymous directory connection or a DirPort test connection.
12669 Instead, we track the link internally and transfer the data
12670 in-process. This saves two sockets per "linked" connection (at the
12671 client and at the server), and avoids the nasty Windows socketpair()
12673 - Keep unused 4k and 16k buffers on free lists, rather than wasting 8k
12674 for every single inactive connection_t. Free items from the
12675 4k/16k-buffer free lists when they haven't been used for a while.
12677 o Minor features (build):
12678 - Make autoconf search for libevent, openssl, and zlib consistently.
12679 - Update deprecated macros in configure.in.
12680 - When warning about missing headers, tell the user to let us
12681 know if the compile succeeds anyway, so we can downgrade the
12683 - Include the current subversion revision as part of the version
12684 string: either fetch it directly if we're in an SVN checkout, do
12685 some magic to guess it if we're in an SVK checkout, or use
12686 the last-detected version if we're building from a .tar.gz.
12687 Use this version consistently in log messages.
12689 o Minor features (logging):
12690 - Always prepend "Bug: " to any log message about a bug.
12691 - Put a platform string (e.g. "Linux i686") in the startup log
12692 message, so when people paste just their logs, we know if it's
12693 OpenBSD or Windows or what.
12694 - When logging memory usage, break down memory used in buffers by
12697 o Minor features (directory system):
12698 - New config option V2AuthoritativeDirectory that all directory
12699 authorities should set. This will let future authorities choose
12700 not to serve V2 directory information.
12701 - Directory authorities allow multiple router descriptors and/or extra
12702 info documents to be uploaded in a single go. This will make
12703 implementing proposal 104 simpler.
12705 o Minor features (controller):
12706 - Add a new config option __DisablePredictedCircuits designed for
12707 use by the controller, when we don't want Tor to build any circuits
12709 - Let the controller specify HOP=%d as an argument to ATTACHSTREAM,
12710 so we can exit from the middle of the circuit.
12711 - Implement "getinfo status/circuit-established".
12712 - Implement "getinfo status/version/..." so a controller can tell
12713 whether the current version is recommended, and whether any versions
12714 are good, and how many authorities agree. (Patch from shibz.)
12716 o Minor features (hidden services):
12717 - Allow multiple HiddenServicePort directives with the same virtual
12718 port; when they occur, the user is sent round-robin to one
12719 of the target ports chosen at random. Partially fixes bug 393 by
12720 adding limited ad-hoc round-robining.
12722 o Minor features (other):
12724 - Add a new AutomapHostsOnResolve option: when it is enabled, any
12725 resolve request for hosts matching a given pattern causes Tor to
12726 generate an internal virtual address mapping for that host. This
12727 allows DNSPort to work sensibly with hidden service users. By
12728 default, .exit and .onion addresses are remapped; the list of
12729 patterns can be reconfigured with AutomapHostsSuffixes.
12730 - Add an "-F" option to tor-resolve to force a resolve for a .onion
12731 address. Thanks to the AutomapHostsOnResolve option, this is no
12732 longer a completely silly thing to do.
12733 - If Tor is invoked from something that isn't a shell (e.g. Vidalia),
12734 now we expand "-f ~/.tor/torrc" correctly. Suggested by Matt Edman.
12735 - Treat "2gb" when given in torrc for a bandwidth as meaning 2gb,
12736 minus 1 byte: the actual maximum declared bandwidth.
12738 o Removed features:
12739 - Removed support for the old binary "version 0" controller protocol.
12740 This has been deprecated since 0.1.1, and warnings have been issued
12741 since 0.1.2. When we encounter a v0 control message, we now send
12742 back an error and close the connection.
12743 - Remove the old "dns worker" server DNS code: it hasn't been default
12744 since 0.1.2.2-alpha, and all the servers seem to be using the new
12747 o Minor bugfixes (portability):
12748 - Even though Windows is equally happy with / and \ as path separators,
12749 try to use \ consistently on Windows and / consistently on Unix: it
12750 makes the log messages nicer.
12751 - Correctly report platform name on Windows 95 OSR2 and Windows 98 SE.
12752 - Read resolv.conf files correctly on platforms where read() returns
12753 partial results on small file reads.
12755 o Minor bugfixes (directory):
12756 - Correctly enforce that elements of directory objects do not appear
12757 more often than they are allowed to appear.
12758 - When we are reporting the DirServer line we just parsed, we were
12759 logging the second stanza of the key fingerprint, not the first.
12761 o Minor bugfixes (logging):
12762 - When we hit an EOF on a log (probably because we're shutting down),
12763 don't try to remove the log from the list: just mark it as
12764 unusable. (Bulletproofs against bug 222.)
12766 o Minor bugfixes (other):
12767 - In the exitlist script, only consider the most recently published
12768 server descriptor for each server. Also, when the user requests
12769 a list of servers that _reject_ connections to a given address,
12770 explicitly exclude the IPs that also have servers that accept
12771 connections to that address. (Resolves bug 405.)
12772 - Stop allowing hibernating servers to be "stable" or "fast".
12773 - On Windows, we were preventing other processes from reading
12774 cached-routers while Tor was running. (Reported by janbar)
12775 - Make the NodeFamilies config option work. (Reported by
12776 lodger -- it has never actually worked, even though we added it
12778 - Check return values from pthread_mutex functions.
12779 - Don't save non-general-purpose router descriptors to the disk cache,
12780 because we have no way of remembering what their purpose was when
12782 - Add even more asserts to hunt down bug 417.
12783 - Build without verbose warnings even on (not-yet-released) gcc 4.2.
12784 - Fix a possible (but very unlikely) bug in picking routers by bandwidth.
12785 Add a log message to confirm that it is in fact unlikely.
12787 o Minor bugfixes (controller):
12788 - Make 'getinfo fingerprint' return a 551 error if we're not a
12789 server, so we match what the control spec claims we do. Reported
12791 - Fix a typo in an error message when extendcircuit fails that
12792 caused us to not follow the \r\n-based delimiter protocol. Reported
12795 o Code simplifications and refactoring:
12796 - Stop passing around circuit_t and crypt_path_t pointers that are
12797 implicit in other procedure arguments.
12798 - Drop the old code to choke directory connections when the
12799 corresponding OR connections got full: thanks to the cell queue
12800 feature, OR conns don't get full any more.
12801 - Make dns_resolve() handle attaching connections to circuits
12802 properly, so the caller doesn't have to.
12803 - Rename wants_to_read and wants_to_write to read/write_blocked_on_bw.
12804 - Keep the connection array as a dynamic smartlist_t, rather than as
12805 a fixed-sized array. This is important, as the number of connections
12806 is becoming increasingly decoupled from the number of sockets.
12809 Changes in version 0.1.2.14 - 2007-05-25
12810 Tor 0.1.2.14 changes the addresses of two directory authorities (this
12811 change especially affects those who serve or use hidden services),
12812 and fixes several other crash- and security-related bugs.
12814 o Directory authority changes:
12815 - Two directory authorities (moria1 and moria2) just moved to new
12816 IP addresses. This change will particularly affect those who serve
12817 or use hidden services.
12819 o Major bugfixes (crashes):
12820 - If a directory server runs out of space in the connection table
12821 as it's processing a begin_dir request, it will free the exit stream
12822 but leave it attached to the circuit, leading to unpredictable
12823 behavior. (Reported by seeess, fixes bug 425.)
12824 - Fix a bug in dirserv_remove_invalid() that would cause authorities
12825 to corrupt memory under some really unlikely scenarios.
12826 - Tighten router parsing rules. (Bugs reported by Benedikt Boss.)
12827 - Avoid segfaults when reading from mmaped descriptor file. (Reported
12830 o Major bugfixes (security):
12831 - When choosing an entry guard for a circuit, avoid using guards
12832 that are in the same family as the chosen exit -- not just guards
12833 that are exactly the chosen exit. (Reported by lodger.)
12835 o Major bugfixes (resource management):
12836 - If a directory authority is down, skip it when deciding where to get
12837 networkstatus objects or descriptors. Otherwise we keep asking
12838 every 10 seconds forever. Fixes bug 384.
12839 - Count it as a failure if we fetch a valid network-status but we
12840 don't want to keep it. Otherwise we'll keep fetching it and keep
12841 not wanting to keep it. Fixes part of bug 422.
12842 - If all of our dirservers have given us bad or no networkstatuses
12843 lately, then stop hammering them once per minute even when we
12844 think they're failed. Fixes another part of bug 422.
12847 - Actually set the purpose correctly for descriptors inserted with
12848 purpose=controller.
12849 - When we have k non-v2 authorities in our DirServer config,
12850 we ignored the last k authorities in the list when updating our
12852 - Correctly back-off from requesting router descriptors that we are
12853 having a hard time downloading.
12854 - Read resolv.conf files correctly on platforms where read() returns
12855 partial results on small file reads.
12856 - Don't rebuild the entire router store every time we get 32K of
12857 routers: rebuild it when the journal gets very large, or when
12858 the gaps in the store get very large.
12861 - When routers publish SVN revisions in their router descriptors,
12862 authorities now include those versions correctly in networkstatus
12864 - Warn when using a version of libevent before 1.3b to run a server on
12865 OSX or BSD: these versions interact badly with userspace threads.
12868 Changes in version 0.1.2.13 - 2007-04-24
12869 This release features some major anonymity fixes, such as safer path
12870 selection; better client performance; faster bootstrapping, better
12871 address detection, and better DNS support for servers; write limiting as
12872 well as read limiting to make servers easier to run; and a huge pile of
12873 other features and bug fixes. The bundles also ship with Vidalia 0.0.11.
12875 Tor 0.1.2.13 is released in memory of Rob Levin (1955-2006), aka lilo
12876 of the Freenode IRC network, remembering his patience and vision for
12877 free speech on the Internet.
12880 - Fix a memory leak when we ask for "all" networkstatuses and we
12881 get one we don't recognize.
12882 - Add more asserts to hunt down bug 417.
12883 - Disable kqueue on OS X 10.3 and earlier, to fix bug 371.
12886 Changes in version 0.1.2.12-rc - 2007-03-16
12888 - Fix an infinite loop introduced in 0.1.2.7-alpha when we serve
12889 directory information requested inside Tor connections (i.e. via
12890 begin_dir cells). It only triggered when the same connection was
12891 serving other data at the same time. Reported by seeess.
12894 - When creating a circuit via the controller, send a 'launched'
12895 event when we're done, so we follow the spec better.
12898 Changes in version 0.1.2.11-rc - 2007-03-15
12899 o Minor bugfixes (controller), reported by daejees:
12900 - Correct the control spec to match how the code actually responds
12901 to 'getinfo addr-mappings/*'.
12902 - The control spec described a GUARDS event, but the code
12903 implemented a GUARD event. Standardize on GUARD, but let people
12904 ask for GUARDS too.
12907 Changes in version 0.1.2.10-rc - 2007-03-07
12908 o Major bugfixes (Windows):
12909 - Do not load the NT services library functions (which may not exist)
12910 just to detect if we're a service trying to shut down. Now we run
12911 on Win98 and friends again.
12913 o Minor bugfixes (other):
12914 - Clarify a couple of log messages.
12915 - Fix a misleading socks5 error number.
12918 Changes in version 0.1.2.9-rc - 2007-03-02
12919 o Major bugfixes (Windows):
12920 - On MinGW, use "%I64u" to printf/scanf 64-bit integers, instead
12921 of the usual GCC "%llu". This prevents a bug when saving 64-bit
12922 int configuration values: the high-order 32 bits would get
12923 truncated. In particular, we were being bitten by the default
12924 MaxAdvertisedBandwidth of 128 TB turning into 0. (Fixes bug 400
12925 and maybe also bug 397.)
12927 o Minor bugfixes (performance):
12928 - Use OpenSSL's AES implementation on platforms where it's faster.
12929 This could save us as much as 10% CPU usage.
12931 o Minor bugfixes (server):
12932 - Do not rotate onion key immediately after setting it for the first
12935 o Minor bugfixes (directory authorities):
12936 - Stop calling servers that have been hibernating for a long time
12937 "stable". Also, stop letting hibernating or obsolete servers affect
12938 uptime and bandwidth cutoffs.
12939 - Stop listing hibernating servers in the v1 directory.
12941 o Minor bugfixes (hidden services):
12942 - Upload hidden service descriptors slightly less often, to reduce
12943 load on authorities.
12945 o Minor bugfixes (other):
12946 - Fix an assert that could trigger if a controller quickly set then
12947 cleared EntryNodes. Bug found by Udo van den Heuvel.
12948 - On architectures where sizeof(int)>4, still clamp declarable bandwidth
12950 - Fix a potential race condition in the rpm installer. Found by
12952 - Try to fix eventdns warnings once and for all: do not treat a dns rcode
12953 of 2 as indicating that the server is completely bad; it sometimes
12954 means that the server is just bad for the request in question. (may fix
12955 the last of bug 326.)
12956 - Disable encrypted directory connections when we don't have a server
12957 descriptor for the destination. We'll get this working again in
12961 Changes in version 0.1.2.8-beta - 2007-02-26
12962 o Major bugfixes (crashes):
12963 - Stop crashing when the controller asks us to resetconf more than
12964 one config option at once. (Vidalia 0.0.11 does this.)
12965 - Fix a crash that happened on Win98 when we're given command-line
12966 arguments: don't try to load NT service functions from advapi32.dll
12967 except when we need them. (Bug introduced in 0.1.2.7-alpha;
12969 - Fix a longstanding obscure crash bug that could occur when
12970 we run out of DNS worker processes. (Resolves bug 390.)
12972 o Major bugfixes (hidden services):
12973 - Correctly detect whether hidden service descriptor downloads are
12974 in-progress. (Suggested by Karsten Loesing; fixes bug 399.)
12976 o Major bugfixes (accounting):
12977 - When we start during an accounting interval before it's time to wake
12978 up, remember to wake up at the correct time. (May fix bug 342.)
12980 o Minor bugfixes (controller):
12981 - Give the controller END_STREAM_REASON_DESTROY events _before_ we
12982 clear the corresponding on_circuit variable, and remember later
12983 that we don't need to send a redundant CLOSED event. Resolves part
12985 - Report events where a resolve succeeded or where we got a socks
12986 protocol error correctly, rather than calling both of them
12988 - Change reported stream target addresses to IP consistently when
12989 we finally get the IP from an exit node.
12990 - Send log messages to the controller even if they happen to be very
12993 o Minor bugfixes (other):
12994 - Display correct results when reporting which versions are
12995 recommended, and how recommended they are. (Resolves bug 383.)
12996 - Improve our estimates for directory bandwidth to be less random:
12997 guess that an unrecognized directory will have the average bandwidth
12998 from all known directories, not that it will have the average
12999 bandwidth from those directories earlier than it on the list.
13000 - If we start a server with ClientOnly 1, then set ClientOnly to 0
13001 and hup, stop triggering an assert based on an empty onion_key.
13002 - On platforms with no working mmap() equivalent, don't warn the
13003 user when cached-routers doesn't exist.
13004 - Warn the user when mmap() [or its equivalent] fails for some reason
13005 other than file-not-found.
13006 - Don't warn the user when cached-routers.new doesn't exist: that's
13007 perfectly fine when starting up for the first time.
13008 - When EntryNodes are configured, rebuild the guard list to contain,
13009 in order: the EntryNodes that were guards before; the rest of the
13010 EntryNodes; the nodes that were guards before.
13011 - Mask out all signals in sub-threads; only the libevent signal
13012 handler should be processing them. This should prevent some crashes
13013 on some machines using pthreads. (Patch from coderman.)
13014 - Fix switched arguments on memset in the implementation of
13015 tor_munmap() for systems with no mmap() call.
13016 - When Tor receives a router descriptor that it asked for, but
13017 no longer wants (because it has received fresh networkstatuses
13018 in the meantime), do not warn the user. Cache the descriptor if
13019 we're a cache; drop it if we aren't.
13020 - Make earlier entry guards _really_ get retried when the network
13022 - On a malformed DNS reply, always give an error to the corresponding
13024 - Build with recent libevents on platforms that do not define the
13025 nonstandard types "u_int8_t" and friends.
13027 o Minor features (controller):
13028 - Warn the user when an application uses the obsolete binary v0
13029 control protocol. We're planning to remove support for it during
13030 the next development series, so it's good to give people some
13032 - Add STREAM_BW events to report per-entry-stream bandwidth
13033 use. (Patch from Robert Hogan.)
13034 - Rate-limit SIGNEWNYM signals in response to controllers that
13035 impolitely generate them for every single stream. (Patch from
13036 mwenge; closes bug 394.)
13037 - Make REMAP stream events have a SOURCE (cache or exit), and
13038 make them generated in every case where we get a successful
13039 connected or resolved cell.
13041 o Minor bugfixes (performance):
13042 - Call router_have_min_dir_info half as often. (This is showing up in
13043 some profiles, but not others.)
13044 - When using GCC, make log_debug never get called at all, and its
13045 arguments never get evaluated, when no debug logs are configured.
13046 (This is showing up in some profiles, but not others.)
13049 - Remove some never-implemented options. Mark PathlenCoinWeight as
13051 - Implement proposal 106: Stop requiring clients to have well-formed
13052 certificates; stop checking nicknames in certificates. (Clients
13053 have certificates so that they can look like Tor servers, but in
13054 the future we might want to allow them to look like regular TLS
13055 clients instead. Nicknames in certificates serve no purpose other
13056 than making our protocol easier to recognize on the wire.)
13057 - Revise messages on handshake failure again to be even more clear about
13058 which are incoming connections and which are outgoing.
13059 - Discard any v1 directory info that's over 1 month old (for
13060 directories) or over 1 week old (for running-routers lists).
13061 - Do not warn when individual nodes in the configuration's EntryNodes,
13062 ExitNodes, etc are down: warn only when all possible nodes
13063 are down. (Fixes bug 348.)
13064 - Always remove expired routers and networkstatus docs before checking
13065 whether we have enough information to build circuits. (Fixes
13067 - Put a lower-bound on MaxAdvertisedBandwidth.
13070 Changes in version 0.1.2.7-alpha - 2007-02-06
13071 o Major bugfixes (rate limiting):
13072 - Servers decline directory requests much more aggressively when
13073 they're low on bandwidth. Otherwise they end up queueing more and
13074 more directory responses, which can't be good for latency.
13075 - But never refuse directory requests from local addresses.
13076 - Fix a memory leak when sending a 503 response for a networkstatus
13078 - Be willing to read or write on local connections (e.g. controller
13079 connections) even when the global rate limiting buckets are empty.
13080 - If our system clock jumps back in time, don't publish a negative
13081 uptime in the descriptor. Also, don't let the global rate limiting
13082 buckets go absurdly negative.
13083 - Flush local controller connection buffers periodically as we're
13084 writing to them, so we avoid queueing 4+ megabytes of data before
13087 o Major bugfixes (NT services):
13088 - Install as NT_AUTHORITY\LocalService rather than as SYSTEM; add a
13089 command-line flag so that admins can override the default by saying
13090 "tor --service install --user "SomeUser"". This will not affect
13091 existing installed services. Also, warn the user that the service
13092 will look for its configuration file in the service user's
13093 %appdata% directory. (We can't do the 'hardwire the user's appdata
13094 directory' trick any more, since we may not have read access to that
13097 o Major bugfixes (other):
13098 - Previously, we would cache up to 16 old networkstatus documents
13099 indefinitely, if they came from nontrusted authorities. Now we
13100 discard them if they are more than 10 days old.
13101 - Fix a crash bug in the presence of DNS hijacking (reported by Andrew
13103 - Detect and reject malformed DNS responses containing circular
13105 - If exits are rare enough that we're not marking exits as guards,
13106 ignore exit bandwidth when we're deciding the required bandwidth
13108 - When we're handling a directory connection tunneled over Tor,
13109 don't fill up internal memory buffers with all the data we want
13110 to tunnel; instead, only add it if the OR connection that will
13111 eventually receive it has some room for it. (This can lead to
13112 slowdowns in tunneled dir connections; a better solution will have
13113 to wait for 0.2.0.)
13115 o Minor bugfixes (dns):
13116 - Add some defensive programming to eventdns.c in an attempt to catch
13117 possible memory-stomping bugs.
13118 - Detect and reject DNS replies containing IPv4 or IPv6 records with
13119 an incorrect number of bytes. (Previously, we would ignore the
13121 - Fix as-yet-unused reverse IPv6 lookup code so it sends nybbles
13122 in the correct order, and doesn't crash.
13123 - Free memory held in recently-completed DNS lookup attempts on exit.
13124 This was not a memory leak, but may have been hiding memory leaks.
13125 - Handle TTL values correctly on reverse DNS lookups.
13126 - Treat failure to parse resolv.conf as an error.
13128 o Minor bugfixes (other):
13129 - Fix crash with "tor --list-fingerprint" (reported by seeess).
13130 - When computing clock skew from directory HTTP headers, consider what
13131 time it was when we finished asking for the directory, not what
13133 - Expire socks connections if they spend too long waiting for the
13134 handshake to finish. Previously we would let them sit around for
13135 days, if the connecting application didn't close them either.
13136 - And if the socks handshake hasn't started, don't send a
13137 "DNS resolve socks failed" handshake reply; just close it.
13138 - Stop using C functions that OpenBSD's linker doesn't like.
13139 - Don't launch requests for descriptors unless we have networkstatuses
13140 from at least half of the authorities. This delays the first
13141 download slightly under pathological circumstances, but can prevent
13142 us from downloading a bunch of descriptors we don't need.
13143 - Do not log IPs with TLS failures for incoming TLS
13144 connections. (Fixes bug 382.)
13145 - If the user asks to use invalid exit nodes, be willing to use
13147 - Stop using the reserved ac_cv namespace in our configure script.
13148 - Call stat() slightly less often; use fstat() when possible.
13149 - Refactor the way we handle pending circuits when an OR connection
13150 completes or fails, in an attempt to fix a rare crash bug.
13151 - Only rewrite a conn's address based on X-Forwarded-For: headers
13152 if it's a parseable public IP address; and stop adding extra quotes
13153 to the resulting address.
13156 - Weight directory requests by advertised bandwidth. Now we can
13157 let servers enable write limiting but still allow most clients to
13158 succeed at their directory requests. (We still ignore weights when
13159 choosing a directory authority; I hope this is a feature.)
13162 - Create a new file ReleaseNotes which was the old ChangeLog. The
13163 new ChangeLog file now includes the summaries for all development
13165 - Check for addresses with invalid characters at the exit as well
13166 as at the client, and warn less verbosely when they fail. You can
13167 override this by setting ServerDNSAllowNonRFC953Addresses to 1.
13168 - Adapt a patch from goodell to let the contrib/exitlist script
13169 take arguments rather than require direct editing.
13170 - Inform the server operator when we decide not to advertise a
13171 DirPort due to AccountingMax enabled or a low BandwidthRate. It
13172 was confusing Zax, so now we're hopefully more helpful.
13173 - Bring us one step closer to being able to establish an encrypted
13174 directory tunnel without knowing a descriptor first. Still not
13175 ready yet. As part of the change, now assume we can use a
13176 create_fast cell if we don't know anything about a router.
13177 - Allow exit nodes to use nameservers running on ports other than 53.
13178 - Servers now cache reverse DNS replies.
13179 - Add an --ignore-missing-torrc command-line option so that we can
13180 get the "use sensible defaults if the configuration file doesn't
13181 exist" behavior even when specifying a torrc location on the command
13184 o Minor features (controller):
13185 - Track reasons for OR connection failure; make these reasons
13186 available via the controller interface. (Patch from Mike Perry.)
13187 - Add a SOCKS_BAD_HOSTNAME client status event so controllers
13188 can learn when clients are sending malformed hostnames to Tor.
13189 - Clean up documentation for controller status events.
13190 - Add a REMAP status to stream events to note that a stream's
13191 address has changed because of a cached address or a MapAddress
13195 Changes in version 0.1.2.6-alpha - 2007-01-09
13197 - Fix an assert error introduced in 0.1.2.5-alpha: if a single TLS
13198 connection handles more than 4 gigs in either direction, we crash.
13199 - Fix an assert error introduced in 0.1.2.5-alpha: if we're an
13200 advertised exit node, somebody might try to exit from us when
13201 we're bootstrapping and before we've built our descriptor yet.
13202 Refuse the connection rather than crashing.
13205 - Warn if we (as a server) find that we've resolved an address that we
13206 weren't planning to resolve.
13207 - Warn that using select() on any libevent version before 1.1 will be
13208 unnecessarily slow (even for select()).
13209 - Flush ERR-level controller status events just like we currently
13210 flush ERR-level log events, so that a Tor shutdown doesn't prevent
13211 the controller from learning about current events.
13213 o Minor features (more controller status events):
13214 - Implement EXTERNAL_ADDRESS server status event so controllers can
13215 learn when our address changes.
13216 - Implement BAD_SERVER_DESCRIPTOR server status event so controllers
13217 can learn when directories reject our descriptor.
13218 - Implement SOCKS_UNKNOWN_PROTOCOL client status event so controllers
13219 can learn when a client application is speaking a non-socks protocol
13221 - Implement DANGEROUS_SOCKS client status event so controllers
13222 can learn when a client application is leaking DNS addresses.
13223 - Implement BUG general status event so controllers can learn when
13224 Tor is unhappy about its internal invariants.
13225 - Implement CLOCK_SKEW general status event so controllers can learn
13226 when Tor thinks the system clock is set incorrectly.
13227 - Implement GOOD_SERVER_DESCRIPTOR and ACCEPTED_SERVER_DESCRIPTOR
13228 server status events so controllers can learn when their descriptors
13229 are accepted by a directory.
13230 - Implement CHECKING_REACHABILITY and REACHABILITY_{SUCCEEDED|FAILED}
13231 server status events so controllers can learn about Tor's progress in
13232 deciding whether it's reachable from the outside.
13233 - Implement BAD_LIBEVENT general status event so controllers can learn
13234 when we have a version/method combination in libevent that needs to
13236 - Implement NAMESERVER_STATUS, NAMESERVER_ALL_DOWN, DNS_HIJACKED,
13237 and DNS_USELESS server status events so controllers can learn
13238 about changes to DNS server status.
13240 o Minor features (directory):
13241 - Authorities no longer recommend exits as guards if this would shift
13242 too much load to the exit nodes.
13245 Changes in version 0.1.2.5-alpha - 2007-01-06
13247 - Enable write limiting as well as read limiting. Now we sacrifice
13248 capacity if we're pushing out lots of directory traffic, rather
13249 than overrunning the user's intended bandwidth limits.
13250 - Include TLS overhead when counting bandwidth usage; previously, we
13251 would count only the bytes sent over TLS, but not the bytes used
13253 - Support running the Tor service with a torrc not in the same
13254 directory as tor.exe and default to using the torrc located in
13255 the %appdata%\Tor\ of the user who installed the service. Patch
13257 - Servers now check for the case when common DNS requests are going to
13258 wildcarded addresses (i.e. all getting the same answer), and change
13259 their exit policy to reject *:* if it's happening.
13260 - Implement BEGIN_DIR cells, so we can connect to the directory
13261 server via TLS to do encrypted directory requests rather than
13262 plaintext. Enable via the TunnelDirConns and PreferTunneledDirConns
13263 config options if you like.
13265 o Minor features (config and docs):
13266 - Start using the state file to store bandwidth accounting data:
13267 the bw_accounting file is now obsolete. We'll keep generating it
13268 for a while for people who are still using 0.1.2.4-alpha.
13269 - Try to batch changes to the state file so that we do as few
13270 disk writes as possible while still storing important things in
13272 - The state file and the bw_accounting file get saved less often when
13273 the AvoidDiskWrites config option is set.
13274 - Make PIDFile work on Windows (untested).
13275 - Add internal descriptions for a bunch of configuration options:
13276 accessible via controller interface and in comments in saved
13278 - Reject *:563 (NNTPS) in the default exit policy. We already reject
13279 NNTP by default, so this seems like a sensible addition.
13280 - Clients now reject hostnames with invalid characters. This should
13281 avoid some inadvertent info leaks. Add an option
13282 AllowNonRFC953Hostnames to disable this behavior, in case somebody
13283 is running a private network with hosts called @, !, and #.
13284 - Add a maintainer script to tell us which options are missing
13285 documentation: "make check-docs".
13286 - Add a new address-spec.txt document to describe our special-case
13287 addresses: .exit, .onion, and .noconnnect.
13289 o Minor features (DNS):
13290 - Ongoing work on eventdns infrastructure: now it has dns server
13291 and ipv6 support. One day Tor will make use of it.
13292 - Add client-side caching for reverse DNS lookups.
13293 - Add support to tor-resolve tool for reverse lookups and SOCKS5.
13294 - When we change nameservers or IP addresses, reset and re-launch
13295 our tests for DNS hijacking.
13297 o Minor features (directory):
13298 - Authorities now specify server versions in networkstatus. This adds
13299 about 2% to the size of compressed networkstatus docs, and allows
13300 clients to tell which servers support BEGIN_DIR and which don't.
13301 The implementation is forward-compatible with a proposed future
13302 protocol version scheme not tied to Tor versions.
13303 - DirServer configuration lines now have an orport= option so
13304 clients can open encrypted tunnels to the authorities without
13305 having downloaded their descriptors yet. Enabled for moria1,
13306 moria2, tor26, and lefkada now in the default configuration.
13307 - Directory servers are more willing to send a 503 "busy" if they
13308 are near their write limit, especially for v1 directory requests.
13309 Now they can use their limited bandwidth for actual Tor traffic.
13310 - Clients track responses with status 503 from dirservers. After a
13311 dirserver has given us a 503, we try not to use it until an hour has
13312 gone by, or until we have no dirservers that haven't given us a 503.
13313 - When we get a 503 from a directory, and we're not a server, we don't
13314 count the failure against the total number of failures allowed
13315 for the thing we're trying to download.
13316 - Report X-Your-Address-Is correctly from tunneled directory
13317 connections; don't report X-Your-Address-Is when it's an internal
13318 address; and never believe reported remote addresses when they're
13320 - Protect against an unlikely DoS attack on directory servers.
13321 - Add a BadDirectory flag to network status docs so that authorities
13322 can (eventually) tell clients about caches they believe to be
13325 o Minor features (controller):
13326 - Have GETINFO dir/status/* work on hosts with DirPort disabled.
13327 - Reimplement GETINFO so that info/names stays in sync with the
13329 - Implement "GETINFO fingerprint".
13330 - Implement "SETEVENTS GUARD" so controllers can get updates on
13331 entry guard status as it changes.
13333 o Minor features (clean up obsolete pieces):
13334 - Remove some options that have been deprecated since at least
13335 0.1.0.x: AccountingMaxKB, LogFile, DebugLogFile, LogLevel, and
13336 SysLog. Use AccountingMax instead of AccountingMaxKB, and use Log
13337 to set log options.
13338 - We no longer look for identity and onion keys in "identity.key" and
13339 "onion.key" -- these were replaced by secret_id_key and
13340 secret_onion_key in 0.0.8pre1.
13341 - We no longer require unrecognized directory entries to be
13344 o Major bugfixes (security):
13345 - Stop sending the HttpProxyAuthenticator string to directory
13346 servers when directory connections are tunnelled through Tor.
13347 - Clients no longer store bandwidth history in the state file.
13348 - Do not log introduction points for hidden services if SafeLogging
13350 - When generating bandwidth history, round down to the nearest
13351 1k. When storing accounting data, round up to the nearest 1k.
13352 - When we're running as a server, remember when we last rotated onion
13353 keys, so that we will rotate keys once they're a week old even if
13354 we never stay up for a week ourselves.
13356 o Major bugfixes (other):
13357 - Fix a longstanding bug in eventdns that prevented the count of
13358 timed-out resolves from ever being reset. This bug caused us to
13359 give up on a nameserver the third time it timed out, and try it
13360 10 seconds later... and to give up on it every time it timed out
13362 - Take out the '5 second' timeout from the connection retry
13363 schedule. Now the first connect attempt will wait a full 10
13364 seconds before switching to a new circuit. Perhaps this will help
13365 a lot. Based on observations from Mike Perry.
13366 - Fix a bug on the Windows implementation of tor_mmap_file() that
13367 would prevent the cached-routers file from ever loading. Reported
13371 - Fix an assert failure when a directory authority sets
13372 AuthDirRejectUnlisted and then receives a descriptor from an
13373 unlisted router. Reported by seeess.
13374 - Avoid a double-free when parsing malformed DirServer lines.
13375 - Fix a bug when a BSD-style PF socket is first used. Patch from
13377 - Fix a bug in 0.1.2.2-alpha that prevented clients from asking
13378 to resolve an address at a given exit node even when they ask for
13380 - Servers no longer ever list themselves in their "family" line,
13381 even if configured to do so. This makes it easier to configure
13382 family lists conveniently.
13383 - When running as a server, don't fall back to 127.0.0.1 when no
13384 nameservers are configured in /etc/resolv.conf; instead, make the
13385 user fix resolv.conf or specify nameservers explicitly. (Resolves
13387 - Stop accepting certain malformed ports in configured exit policies.
13388 - Don't re-write the fingerprint file every restart, unless it has
13390 - Stop warning when a single nameserver fails: only warn when _all_ of
13391 our nameservers have failed. Also, when we only have one nameserver,
13392 raise the threshold for deciding that the nameserver is dead.
13393 - Directory authorities now only decide that routers are reachable
13394 if their identity keys are as expected.
13395 - When the user uses bad syntax in the Log config line, stop
13396 suggesting other bad syntax as a replacement.
13397 - Correctly detect ipv6 DNS capability on OpenBSD.
13399 o Minor bugfixes (controller):
13400 - Report the circuit number correctly in STREAM CLOSED events. Bug
13401 reported by Mike Perry.
13402 - Do not report bizarre values for results of accounting GETINFOs
13403 when the last second's write or read exceeds the allotted bandwidth.
13404 - Report "unrecognized key" rather than an empty string when the
13405 controller tries to fetch a networkstatus that doesn't exist.
13408 Changes in version 0.1.1.26 - 2006-12-14
13409 o Security bugfixes:
13410 - Stop sending the HttpProxyAuthenticator string to directory
13411 servers when directory connections are tunnelled through Tor.
13412 - Clients no longer store bandwidth history in the state file.
13413 - Do not log introduction points for hidden services if SafeLogging
13417 - Fix an assert failure when a directory authority sets
13418 AuthDirRejectUnlisted and then receives a descriptor from an
13419 unlisted router (reported by seeess).
13422 Changes in version 0.1.2.4-alpha - 2006-12-03
13424 - Add support for using natd; this allows FreeBSDs earlier than
13425 5.1.2 to have ipfw send connections through Tor without using
13426 SOCKS. (Patch from Zajcev Evgeny with tweaks from tup.)
13429 - Make all connections to addresses of the form ".noconnect"
13430 immediately get closed. This lets application/controller combos
13431 successfully test whether they're talking to the same Tor by
13432 watching for STREAM events.
13433 - Make cross.sh cross-compilation script work even when autogen.sh
13434 hasn't been run. (Patch from Michael Mohr.)
13435 - Statistics dumped by -USR2 now include a breakdown of public key
13436 operations, for profiling.
13439 - Fix a major leak when directory authorities parse their
13440 approved-routers list, a minor memory leak when we fail to pick
13441 an exit node, and a few rare leaks on errors.
13442 - Handle TransPort connections even when the server sends data before
13443 the client sends data. Previously, the connection would just hang
13444 until the client sent data. (Patch from tup based on patch from
13446 - Avoid assert failure when our cached-routers file is empty on
13450 - Don't log spurious warnings when we see a circuit close reason we
13451 don't recognize; it's probably just from a newer version of Tor.
13452 - Have directory authorities allow larger amounts of drift in uptime
13453 without replacing the server descriptor: previously, a server that
13454 restarted every 30 minutes could have 48 "interesting" descriptors
13456 - Start linking to the Tor specification and Tor reference manual
13457 correctly in the Windows installer.
13458 - Add Vidalia to the OS X uninstaller script, so when we uninstall
13459 Tor/Privoxy we also uninstall Vidalia.
13460 - Resume building on Irix64, and fix a lot of warnings from its
13461 MIPSpro C compiler.
13462 - Don't corrupt last_guessed_ip in router_new_address_suggestion()
13463 when we're running as a client.
13466 Changes in version 0.1.1.25 - 2006-11-04
13468 - When a client asks us to resolve (rather than connect to)
13469 an address, and we have a cached answer, give them the cached
13470 answer. Previously, we would give them no answer at all.
13471 - We were building exactly the wrong circuits when we predict
13472 hidden service requirements, meaning Tor would have to build all
13473 its circuits on demand.
13474 - If none of our live entry guards have a high uptime, but we
13475 require a guard with a high uptime, try adding a new guard before
13476 we give up on the requirement. This patch should make long-lived
13477 connections more stable on average.
13478 - When testing reachability of our DirPort, don't launch new
13479 tests when there's already one in progress -- unreachable
13480 servers were stacking up dozens of testing streams.
13482 o Security bugfixes:
13483 - When the user sends a NEWNYM signal, clear the client-side DNS
13484 cache too. Otherwise we continue to act on previous information.
13487 - Avoid a memory corruption bug when creating a hash table for
13489 - Avoid possibility of controller-triggered crash when misusing
13490 certain commands from a v0 controller on platforms that do not
13491 handle printf("%s",NULL) gracefully.
13492 - Avoid infinite loop on unexpected controller input.
13493 - Don't log spurious warnings when we see a circuit close reason we
13494 don't recognize; it's probably just from a newer version of Tor.
13495 - Add Vidalia to the OS X uninstaller script, so when we uninstall
13496 Tor/Privoxy we also uninstall Vidalia.
13499 Changes in version 0.1.2.3-alpha - 2006-10-29
13501 - Prepare for servers to publish descriptors less often: never
13502 discard a descriptor simply for being too old until either it is
13503 recommended by no authorities, or until we get a better one for
13504 the same router. Make caches consider retaining old recommended
13505 routers for even longer.
13506 - If most authorities set a BadExit flag for a server, clients
13507 don't think of it as a general-purpose exit. Clients only consider
13508 authorities that advertise themselves as listing bad exits.
13509 - Directory servers now provide 'Pragma: no-cache' and 'Expires'
13510 headers for content, so that we can work better in the presence of
13511 caching HTTP proxies.
13512 - Allow authorities to list nodes as bad exits by fingerprint or by
13515 o Minor features, controller:
13516 - Add a REASON field to CIRC events; for backward compatibility, this
13517 field is sent only to controllers that have enabled the extended
13518 event format. Also, add additional reason codes to explain why
13519 a given circuit has been destroyed or truncated. (Patches from
13521 - Add a REMOTE_REASON field to extended CIRC events to tell the
13522 controller about why a remote OR told us to close a circuit.
13523 - Stream events also now have REASON and REMOTE_REASON fields,
13524 working much like those for circuit events.
13525 - There's now a GETINFO ns/... field so that controllers can ask Tor
13526 about the current status of a router.
13527 - A new event type "NS" to inform a controller when our opinion of
13528 a router's status has changed.
13529 - Add a GETINFO events/names and GETINFO features/names so controllers
13530 can tell which events and features are supported.
13531 - A new CLEARDNSCACHE signal to allow controllers to clear the
13532 client-side DNS cache without expiring circuits.
13534 o Security bugfixes:
13535 - When the user sends a NEWNYM signal, clear the client-side DNS
13536 cache too. Otherwise we continue to act on previous information.
13539 - Avoid sending junk to controllers or segfaulting when a controller
13540 uses EVENT_NEW_DESC with verbose nicknames.
13541 - Stop triggering asserts if the controller tries to extend hidden
13542 service circuits (reported by mwenge).
13543 - Avoid infinite loop on unexpected controller input.
13544 - When the controller does a "GETINFO network-status", tell it
13545 about even those routers whose descriptors are very old, and use
13546 long nicknames where appropriate.
13547 - Change NT service functions to be loaded on demand. This lets us
13548 build with MinGW without breaking Tor for Windows 98 users.
13549 - Do DirPort reachability tests less often, since a single test
13550 chews through many circuits before giving up.
13551 - In the hidden service example in torrc.sample, stop recommending
13552 esoteric and discouraged hidden service options.
13553 - When stopping an NT service, wait up to 10 sec for it to actually
13554 stop. Patch from Matt Edman; resolves bug 295.
13555 - Fix handling of verbose nicknames with ORCONN controller events:
13556 make them show up exactly when requested, rather than exactly when
13558 - When reporting verbose nicknames in entry_guards_getinfo(), avoid
13559 printing a duplicate "$" in the keys we send (reported by mwenge).
13560 - Correctly set maximum connection limit on Cygwin. (This time
13562 - Try to detect Windows correctly when cross-compiling.
13563 - Detect the size of the routers file correctly even if it is
13564 corrupted (on systems without mmap) or not page-aligned (on systems
13565 with mmap). This bug was harmless.
13566 - Sometimes we didn't bother sending a RELAY_END cell when an attempt
13567 to open a stream fails; now we do in more cases. This should
13568 make clients able to find a good exit faster in some cases, since
13569 unhandleable requests will now get an error rather than timing out.
13570 - Resolve two memory leaks when rebuilding the on-disk router cache
13571 (reported by fookoowa).
13572 - Clean up minor code warnings suggested by the MIPSpro C compiler,
13573 and reported by some Centos users.
13574 - Controller signals now work on non-Unix platforms that don't define
13575 SIGUSR1 and SIGUSR2 the way we expect.
13576 - Patch from Michael Mohr to contrib/cross.sh, so it checks more
13577 values before failing, and always enables eventdns.
13578 - Libevent-1.2 exports, but does not define in its headers, strlcpy.
13579 Try to fix this in configure.in by checking for most functions
13580 before we check for libevent.
13583 Changes in version 0.1.2.2-alpha - 2006-10-07
13585 - Make our async eventdns library on-by-default for Tor servers,
13586 and plan to deprecate the separate dnsworker threads.
13587 - Add server-side support for "reverse" DNS lookups (using PTR
13588 records so clients can determine the canonical hostname for a given
13589 IPv4 address). Only supported by servers using eventdns; servers
13590 now announce in their descriptors whether they support eventdns.
13591 - Specify and implement client-side SOCKS5 interface for reverse DNS
13592 lookups (see doc/socks-extensions.txt).
13593 - Add a BEGIN_DIR relay cell type for an easier in-protocol way to
13594 connect to directory servers through Tor. Previously, clients needed
13595 to find Tor exits to make private connections to directory servers.
13596 - Avoid choosing Exit nodes for entry or middle hops when the
13597 total bandwidth available from non-Exit nodes is much higher than
13598 the total bandwidth available from Exit nodes.
13599 - Workaround for name servers (like Earthlink's) that hijack failing
13600 DNS requests and replace the no-such-server answer with a "helpful"
13601 redirect to an advertising-driven search portal. Also work around
13602 DNS hijackers who "helpfully" decline to hijack known-invalid
13603 RFC2606 addresses. Config option "ServerDNSDetectHijacking 0"
13604 lets you turn it off.
13605 - Send out a burst of long-range padding cells once we've established
13606 that we're reachable. Spread them over 4 circuits, so hopefully
13607 a few will be fast. This exercises our bandwidth and bootstraps
13608 us into the directory more quickly.
13610 o New/improved config options:
13611 - Add new config option "ResolvConf" to let the server operator
13612 choose an alternate resolve.conf file when using eventdns.
13613 - Add an "EnforceDistinctSubnets" option to control our "exclude
13614 servers on the same /16" behavior. It's still on by default; this
13615 is mostly for people who want to operate private test networks with
13616 all the machines on the same subnet.
13617 - If one of our entry guards is on the ExcludeNodes list, or the
13618 directory authorities don't think it's a good guard, treat it as
13619 if it were unlisted: stop using it as a guard, and throw it off
13620 the guards list if it stays that way for a long time.
13621 - Allow directory authorities to be marked separately as authorities
13622 for the v1 directory protocol, the v2 directory protocol, and
13623 as hidden service directories, to make it easier to retire old
13624 authorities. V1 authorities should set "HSAuthoritativeDir 1"
13625 to continue being hidden service authorities too.
13626 - Remove 8888 as a LongLivedPort, and add 6697 (IRCS).
13628 o Minor features, controller:
13629 - Fix CIRC controller events so that controllers can learn the
13630 identity digests of non-Named servers used in circuit paths.
13631 - Let controllers ask for more useful identifiers for servers. Instead
13632 of learning identity digests for un-Named servers and nicknames
13633 for Named servers, the new identifiers include digest, nickname,
13634 and indication of Named status. Off by default; see control-spec.txt
13635 for more information.
13636 - Add a "getinfo address" controller command so it can display Tor's
13637 best guess to the user.
13638 - New controller event to alert the controller when our server
13639 descriptor has changed.
13640 - Give more meaningful errors on controller authentication failure.
13642 o Minor features, other:
13643 - When asked to resolve a hostname, don't use non-exit servers unless
13644 requested to do so. This allows servers with broken DNS to be
13645 useful to the network.
13646 - Divide eventdns log messages into warn and info messages.
13647 - Reserve the nickname "Unnamed" for routers that can't pick
13648 a hostname: any router can call itself Unnamed; directory
13649 authorities will never allocate Unnamed to any particular router;
13650 clients won't believe that any router is the canonical Unnamed.
13651 - Only include function names in log messages for info/debug messages.
13652 For notice/warn/err, the content of the message should be clear on
13653 its own, and printing the function name only confuses users.
13654 - Avoid some false positives during reachability testing: don't try
13655 to test via a server that's on the same /24 as us.
13656 - If we fail to build a circuit to an intended enclave, and it's
13657 not mandatory that we use that enclave, stop wanting it.
13658 - When eventdns is enabled, allow multithreaded builds on NetBSD and
13659 OpenBSD. (We had previously disabled threads on these platforms
13660 because they didn't have working thread-safe resolver functions.)
13662 o Major bugfixes, anonymity/security:
13663 - If a client asked for a server by name, and there's a named server
13664 in our network-status but we don't have its descriptor yet, we
13665 could return an unnamed server instead.
13666 - Fix NetBSD bug that could allow someone to force uninitialized RAM
13667 to be sent to a server's DNS resolver. This only affects NetBSD
13668 and other platforms that do not bounds-check tolower().
13669 - Reject (most) attempts to use Tor circuits with length one. (If
13670 many people start using Tor as a one-hop proxy, exit nodes become
13671 a more attractive target for compromise.)
13672 - Just because your DirPort is open doesn't mean people should be
13673 able to remotely teach you about hidden service descriptors. Now
13674 only accept rendezvous posts if you've got HSAuthoritativeDir set.
13676 o Major bugfixes, other:
13677 - Don't crash on race condition in dns.c: tor_assert(!resolve->expire)
13678 - When a client asks the server to resolve (not connect to)
13679 an address, and it has a cached answer, give them the cached answer.
13680 Previously, the server would give them no answer at all.
13681 - Allow really slow clients to not hang up five minutes into their
13682 directory downloads (suggested by Adam J. Richter).
13683 - We were building exactly the wrong circuits when we anticipated
13684 hidden service requirements, meaning Tor would have to build all
13685 its circuits on demand.
13686 - Avoid crashing when we mmap a router cache file of size 0.
13687 - When testing reachability of our DirPort, don't launch new
13688 tests when there's already one in progress -- unreachable
13689 servers were stacking up dozens of testing streams.
13691 o Minor bugfixes, correctness:
13692 - If we're a directory mirror and we ask for "all" network status
13693 documents, we would discard status documents from authorities
13694 we don't recognize.
13695 - Avoid a memory corruption bug when creating a hash table for
13697 - Avoid controller-triggered crash when misusing certain commands
13698 from a v0 controller on platforms that do not handle
13699 printf("%s",NULL) gracefully.
13700 - Don't crash when a controller sends a third argument to an
13701 "extendcircuit" request.
13702 - Controller protocol fixes: fix encoding in "getinfo addr-mappings"
13703 response; fix error code when "getinfo dir/status/" fails.
13704 - Avoid crash when telling controller stream-status and a stream
13706 - Patch from Adam Langley to fix assert() in eventdns.c.
13707 - Fix a debug log message in eventdns to say "X resolved to Y"
13708 instead of "X resolved to X".
13709 - Make eventdns give strings for DNS errors, not just error numbers.
13710 - Track unreachable entry guards correctly: don't conflate
13711 'unreachable by us right now' with 'listed as down by the directory
13712 authorities'. With the old code, if a guard was unreachable by
13713 us but listed as running, it would clog our guard list forever.
13714 - Behave correctly in case we ever have a network with more than
13715 2GB/s total advertised capacity.
13716 - Make TrackExitHosts case-insensitive, and fix the behavior of
13717 ".suffix" TrackExitHosts items to avoid matching in the middle of
13719 - Finally fix the openssl warnings from newer gccs that believe that
13720 ignoring a return value is okay, but casting a return value and
13721 then ignoring it is a sign of madness.
13722 - Prevent the contrib/exitlist script from printing the same
13723 result more than once.
13724 - Patch from Steve Hildrey: Generate network status correctly on
13725 non-versioning dirservers.
13726 - Don't listen to the X-Your-Address-Is hint if you did the lookup
13727 via Tor; otherwise you'll think you're the exit node's IP address.
13729 o Minor bugfixes, performance:
13730 - Two small performance improvements on parsing descriptors.
13731 - Major performance improvement on inserting descriptors: change
13732 algorithm from O(n^2) to O(n).
13733 - Make the common memory allocation path faster on machines where
13734 malloc(0) returns a pointer.
13735 - Start remembering X-Your-Address-Is directory hints even if you're
13736 a client, so you can become a server more smoothly.
13737 - Avoid duplicate entries on MyFamily line in server descriptor.
13739 o Packaging, features:
13740 - Remove architecture from OS X builds. The official builds are
13741 now universal binaries.
13742 - The Debian package now uses --verify-config when (re)starting,
13743 to distinguish configuration errors from other errors.
13744 - Update RPMs to require libevent 1.1b.
13746 o Packaging, bugfixes:
13747 - Patches so Tor builds with MinGW on Windows.
13748 - Patches so Tor might run on Cygwin again.
13749 - Resume building on non-gcc compilers and ancient gcc. Resume
13750 building with the -O0 compile flag. Resume building cleanly on
13752 - Run correctly on OS X platforms with case-sensitive filesystems.
13753 - Correct includes for net/if.h and net/pfvar.h on OpenBSD (from Tup).
13754 - Add autoconf checks so Tor can build on Solaris x86 again.
13757 - Documented (and renamed) ServerDNSSearchDomains and
13758 ServerDNSResolvConfFile options.
13759 - Be clearer that the *ListenAddress directives can be repeated
13763 Changes in version 0.1.1.24 - 2006-09-29
13765 - Allow really slow clients to not hang up five minutes into their
13766 directory downloads (suggested by Adam J. Richter).
13767 - Fix major performance regression from 0.1.0.x: instead of checking
13768 whether we have enough directory information every time we want to
13769 do something, only check when the directory information has changed.
13770 This should improve client CPU usage by 25-50%.
13771 - Don't crash if, after a server has been running for a while,
13772 it can't resolve its hostname.
13775 - Allow Tor to start when RunAsDaemon is set but no logs are set.
13776 - Don't crash when the controller receives a third argument to an
13777 "extendcircuit" request.
13778 - Controller protocol fixes: fix encoding in "getinfo addr-mappings"
13779 response; fix error code when "getinfo dir/status/" fails.
13780 - Fix configure.in to not produce broken configure files with
13781 more recent versions of autoconf. Thanks to Clint for his auto*
13783 - Fix security bug on NetBSD that could allow someone to force
13784 uninitialized RAM to be sent to a server's DNS resolver. This
13785 only affects NetBSD and other platforms that do not bounds-check
13787 - Warn user when using libevent 1.1a or earlier with win32 or kqueue
13788 methods: these are known to be buggy.
13789 - If we're a directory mirror and we ask for "all" network status
13790 documents, we would discard status documents from authorities
13791 we don't recognize.
13794 Changes in version 0.1.2.1-alpha - 2006-08-27
13796 - Add "eventdns" async dns library from Adam Langley, tweaked to
13797 build on OSX and Windows. Only enabled if you pass the
13798 --enable-eventdns argument to configure.
13799 - Allow servers with no hostname or IP address to learn their
13800 IP address by asking the directory authorities. This code only
13801 kicks in when you would normally have exited with a "no address"
13802 error. Nothing's authenticated, so use with care.
13803 - Rather than waiting a fixed amount of time between retrying
13804 application connections, we wait only 5 seconds for the first,
13805 10 seconds for the second, and 15 seconds for each retry after
13806 that. Hopefully this will improve the expected user experience.
13807 - Patch from Tup to add support for transparent AP connections:
13808 this basically bundles the functionality of trans-proxy-tor
13809 into the Tor mainline. Now hosts with compliant pf/netfilter
13810 implementations can redirect TCP connections straight to Tor
13811 without diverting through SOCKS. Needs docs.
13812 - Busy directory servers save lots of memory by spooling server
13813 descriptors, v1 directories, and v2 networkstatus docs to buffers
13814 as needed rather than en masse. Also mmap the cached-routers
13815 files, so we don't need to keep the whole thing in memory too.
13816 - Automatically avoid picking more than one node from the same
13817 /16 network when constructing a circuit.
13818 - Revise and clean up the torrc.sample that we ship with; add
13819 a section for BandwidthRate and BandwidthBurst.
13822 - Split circuit_t into origin_circuit_t and or_circuit_t, and
13823 split connection_t into edge, or, dir, control, and base structs.
13824 These will save quite a bit of memory on busy servers, and they'll
13825 also help us track down bugs in the code and bugs in the spec.
13826 - Experimentally re-enable kqueue on OSX when using libevent 1.1b
13827 or later. Log when we are doing this, so we can diagnose it when
13828 it fails. (Also, recommend libevent 1.1b for kqueue and
13829 win32 methods; deprecate libevent 1.0b harder; make libevent
13830 recommendation system saner.)
13831 - Start being able to build universal binaries on OS X (thanks
13833 - Export the default exit policy via the control port, so controllers
13834 don't need to guess what it is / will be later.
13835 - Add a man page entry for ProtocolWarnings.
13836 - Add TestVia config option to the man page.
13837 - Remove even more protocol-related warnings from Tor server logs,
13838 such as bad TLS handshakes and malformed begin cells.
13839 - Stop fetching descriptors if you're not a dir mirror and you
13840 haven't tried to establish any circuits lately. [This currently
13841 causes some dangerous behavior, because when you start up again
13842 you'll use your ancient server descriptors.]
13843 - New DirPort behavior: if you have your dirport set, you download
13844 descriptors aggressively like a directory mirror, whether or not
13845 your ORPort is set.
13846 - Get rid of the router_retry_connections notion. Now routers
13847 no longer try to rebuild long-term connections to directory
13848 authorities, and directory authorities no longer try to rebuild
13849 long-term connections to all servers. We still don't hang up
13850 connections in these two cases though -- we need to look at it
13851 more carefully to avoid flapping, and we likely need to wait til
13852 0.1.1.x is obsolete.
13853 - Drop compatibility with obsolete Tors that permit create cells
13854 to have the wrong circ_id_type.
13855 - Re-enable per-connection rate limiting. Get rid of the "OP
13856 bandwidth" concept. Lay groundwork for "bandwidth classes" --
13857 separate global buckets that apply depending on what sort of conn
13859 - Start publishing one minute or so after we find our ORPort
13860 to be reachable. This will help reduce the number of descriptors
13861 we have for ourselves floating around, since it's quite likely
13862 other things (e.g. DirPort) will change during that minute too.
13863 - Fork the v1 directory protocol into its own spec document,
13864 and mark dir-spec.txt as the currently correct (v2) spec.
13867 - When we find our DirPort to be reachable, publish a new descriptor
13868 so we'll tell the world (reported by pnx).
13869 - Publish a new descriptor after we hup/reload. This is important
13870 if our config has changed such that we'll want to start advertising
13871 our DirPort now, etc.
13872 - Allow Tor to start when RunAsDaemon is set but no logs are set.
13873 - When we have a state file we cannot parse, tell the user and
13874 move it aside. Now we avoid situations where the user starts
13875 Tor in 1904, Tor writes a state file with that timestamp in it,
13876 the user fixes her clock, and Tor refuses to start.
13877 - Fix configure.in to not produce broken configure files with
13878 more recent versions of autoconf. Thanks to Clint for his auto*
13880 - "tor --verify-config" now exits with -1(255) or 0 depending on
13881 whether the config options are bad or good.
13882 - Resolve bug 321 when using dnsworkers: append a period to every
13883 address we resolve at the exit node, so that we do not accidentally
13884 pick up local addresses, and so that failing searches are retried
13885 in the resolver search domains. (This is already solved for
13886 eventdns.) (This breaks Blossom servers for now.)
13887 - If we are using an exit enclave and we can't connect, e.g. because
13888 its webserver is misconfigured to not listen on localhost, then
13889 back off and try connecting from somewhere else before we fail.
13892 - Start compiling on MinGW on Windows (patches from Mike Chiussi).
13893 - Start compiling on MSVC6 on Windows (patches from Frediano Ziglio).
13894 - Fix bug 314: Tor clients issued "unsafe socks" warnings even
13895 when the IP address is mapped through MapAddress to a hostname.
13896 - Start passing "ipv4" hints to getaddrinfo(), so servers don't do
13897 useless IPv6 DNS resolves.
13898 - Patch suggested by Karsten Loesing: respond to SIGNAL command
13899 before we execute the signal, in case the signal shuts us down.
13900 - Clean up AllowInvalidNodes man page entry.
13901 - Claim a commonname of Tor, rather than TOR, in TLS handshakes.
13902 - Add more asserts to track down an assert error on a windows Tor
13903 server with connection_add being called with socket == -1.
13904 - Handle reporting OR_CONN_EVENT_NEW events to the controller.
13905 - Fix misleading log messages: an entry guard that is "unlisted",
13906 as well as not known to be "down" (because we've never heard
13907 of it), is not therefore "up".
13908 - Remove code to special-case "-cvs" ending, since it has not
13909 actually mattered since 0.0.9.
13910 - Make our socks5 handling more robust to broken socks clients:
13911 throw out everything waiting on the buffer in between socks
13912 handshake phases, since they can't possibly (so the theory
13913 goes) have predicted what we plan to respond to them.
13916 Changes in version 0.1.1.23 - 2006-07-30
13918 - Fast Tor servers, especially exit nodes, were triggering asserts
13919 due to a bug in handling the list of pending DNS resolves. Some
13920 bugs still remain here; we're hunting them.
13921 - Entry guards could crash clients by sending unexpected input.
13922 - More fixes on reachability testing: if you find yourself reachable,
13923 then don't ever make any client requests (so you stop predicting
13924 circuits), then hup or have your clock jump, then later your IP
13925 changes, you won't think circuits are working, so you won't try to
13926 test reachability, so you won't publish.
13929 - Avoid a crash if the controller does a resetconf firewallports
13930 and then a setconf fascistfirewall=1.
13931 - Avoid an integer underflow when the dir authority decides whether
13932 a router is stable: we might wrongly label it stable, and compute
13933 a slightly wrong median stability, when a descriptor is published
13935 - Fix a place where we might trigger an assert if we can't build our
13936 own server descriptor yet.
13939 Changes in version 0.1.1.22 - 2006-07-05
13941 - Fix a big bug that was causing servers to not find themselves
13942 reachable if they changed IP addresses. Since only 0.1.1.22+
13943 servers can do reachability testing correctly, now we automatically
13944 make sure to test via one of these.
13945 - Fix to allow clients and mirrors to learn directory info from
13946 descriptor downloads that get cut off partway through.
13947 - Directory authorities had a bug in deciding if a newly published
13948 descriptor was novel enough to make everybody want a copy -- a few
13949 servers seem to be publishing new descriptors many times a minute.
13951 - Fix a rare bug that was causing some servers to complain about
13952 "closing wedged cpuworkers" and skip some circuit create requests.
13953 - Make the Exit flag in directory status documents actually work.
13956 Changes in version 0.1.1.21 - 2006-06-10
13957 o Crash and assert fixes from 0.1.1.20:
13958 - Fix a rare crash on Tor servers that have enabled hibernation.
13959 - Fix a seg fault on startup for Tor networks that use only one
13960 directory authority.
13961 - Fix an assert from a race condition that occurs on Tor servers
13962 while exiting, where various threads are trying to log that they're
13963 exiting, and delete the logs, at the same time.
13964 - Make our unit tests pass again on certain obscure platforms.
13967 - Add support for building SUSE RPM packages.
13968 - Speed up initial bootstrapping for clients: if we are making our
13969 first ever connection to any entry guard, then don't mark it down
13971 - When only one Tor server in the network is labelled as a guard,
13972 and we've already picked him, we would cycle endlessly picking him
13973 again, being unhappy about it, etc. Now we specifically exclude
13974 current guards when picking a new guard.
13975 - Servers send create cells more reliably after the TLS connection
13976 is established: we were sometimes forgetting to send half of them
13977 when we had more than one pending.
13978 - If we get a create cell that asks us to extend somewhere, but the
13979 Tor server there doesn't match the expected digest, we now send
13980 a destroy cell back, rather than silently doing nothing.
13981 - Make options->RedirectExit work again.
13982 - Make cookie authentication for the controller work again.
13983 - Stop being picky about unusual characters in the arguments to
13984 mapaddress. It's none of our business.
13985 - Add a new config option "TestVia" that lets you specify preferred
13986 middle hops to use for test circuits. Perhaps this will let me
13987 debug the reachability problems better.
13989 o Log / documentation fixes:
13990 - If we're a server and some peer has a broken TLS certificate, don't
13991 log about it unless ProtocolWarnings is set, i.e., we want to hear
13992 about protocol violations by others.
13993 - Fix spelling of VirtualAddrNetwork in man page.
13994 - Add a better explanation at the top of the autogenerated torrc file
13995 about what happened to our old torrc.
13998 Changes in version 0.1.1.20 - 2006-05-23
14000 - Downgrade a log severity where servers complain that they're
14002 - Avoid a compile warning on FreeBSD.
14003 - Remove string size limit on NEWDESC messages; solve bug 291.
14004 - Correct the RunAsDaemon entry in the man page; ignore RunAsDaemon
14005 more thoroughly when we're running on windows.
14008 Changes in version 0.1.1.19-rc - 2006-05-03
14010 - Regenerate our local descriptor if it's dirty and we try to use
14011 it locally (e.g. if it changes during reachability detection).
14012 - If we setconf our ORPort to 0, we continued to listen on the
14013 old ORPort and receive connections.
14014 - Avoid a second warning about machine/limits.h on Debian
14016 - Be willing to add our own routerinfo into the routerlist.
14017 Now authorities will include themselves in their directories
14018 and network-statuses.
14019 - Stop trying to upload rendezvous descriptors to every
14020 directory authority: only try the v1 authorities.
14021 - Servers no longer complain when they think they're not
14022 registered with the directory authorities. There were too many
14024 - Backport dist-rpm changes so rpms can be built without errors.
14027 - Implement an option, VirtualAddrMask, to set which addresses
14028 get handed out in response to mapaddress requests. This works
14029 around a bug in tsocks where 127.0.0.0/8 is never socksified.
14032 Changes in version 0.1.1.18-rc - 2006-04-10
14034 - Work harder to download live network-statuses from all the
14035 directory authorities we know about. Improve the threshold
14036 decision logic so we're more robust to edge cases.
14037 - When fetching rendezvous descriptors, we were willing to ask
14038 v2 authorities too, which would always return 404.
14041 - Stop listing down or invalid nodes in the v1 directory. This will
14042 reduce its bulk by about 1/3, and reduce load on directory
14044 - When deciding whether a router is Fast or Guard-worthy, consider
14045 his advertised BandwidthRate and not just the BandwidthCapacity.
14046 - No longer ship INSTALL and README files -- they are useless now.
14047 - Force rpmbuild to behave and honor target_cpu.
14048 - Avoid warnings about machine/limits.h on Debian GNU/kFreeBSD.
14049 - Start to include translated versions of the tor-doc-*.html
14050 files, along with the screenshots. Still needs more work.
14051 - Start sending back 512 and 451 errors if mapaddress fails,
14052 rather than not sending anything back at all.
14053 - When we fail to bind or listen on an incoming or outgoing
14054 socket, we should close it before failing. otherwise we just
14055 leak it. (thanks to weasel for finding.)
14056 - Allow "getinfo dir/status/foo" to work, as long as your DirPort
14057 is enabled. (This is a hack, and will be fixed in 0.1.2.x.)
14058 - Make NoPublish (even though deprecated) work again.
14059 - Fix a minor security flaw where a versioning auth dirserver
14060 could list a recommended version many times in a row to make
14061 clients more convinced that it's recommended.
14062 - Fix crash bug if there are two unregistered servers running
14063 with the same nickname, one of them is down, and you ask for
14064 them by nickname in your EntryNodes or ExitNodes. Also, try
14065 to pick the one that's running rather than an arbitrary one.
14066 - Fix an infinite loop we could hit if we go offline for too long.
14067 - Complain when we hit WSAENOBUFS on recv() or write() too.
14068 Perhaps this will help us hunt the bug.
14069 - If you're not a versioning dirserver, don't put the string
14070 "client-versions \nserver-versions \n" in your network-status.
14071 - Lower the minimum required number of file descriptors to 1000,
14072 so we can have some overhead for Valgrind on Linux, where the
14073 default ulimit -n is 1024.
14076 - Add tor.dizum.com as the fifth authoritative directory server.
14077 - Add a new config option FetchUselessDescriptors, off by default,
14078 for when you plan to run "exitlist" on your client and you want
14079 to know about even the non-running descriptors.
14082 Changes in version 0.1.1.17-rc - 2006-03-28
14084 - Clients and servers since 0.1.1.10-alpha have been expiring
14085 connections whenever they are idle for 5 minutes and they *do*
14086 have circuits on them. Oops. With this new version, clients will
14087 discard their previous entry guard choices and avoid choosing
14088 entry guards running these flawed versions.
14089 - Fix memory leak when uncompressing concatenated zlib streams. This
14090 was causing substantial leaks over time on Tor servers.
14091 - The v1 directory was including servers as much as 48 hours old,
14092 because that's how the new routerlist->routers works. Now only
14093 include them if they're 20 hours old or less.
14096 - Resume building on irix64, netbsd 2.0, etc.
14097 - On non-gcc compilers (e.g. solaris), use "-g -O" instead of
14099 - Stop writing the "router.desc" file, ever. Nothing uses it anymore,
14100 and it is confusing some users.
14101 - Mirrors stop caching the v1 directory so often.
14102 - Make the max number of old descriptors that a cache will hold
14103 rise with the number of directory authorities, so we can scale.
14104 - Change our win32 uname() hack to be more forgiving about what
14105 win32 versions it thinks it's found.
14108 - Add lefkada.eecs.harvard.edu as a fourth authoritative directory
14110 - When the controller's *setconf commands fail, collect an error
14111 message in a string and hand it back to the controller.
14112 - Make the v2 dir's "Fast" flag based on relative capacity, just
14113 like "Stable" is based on median uptime. Name everything in the
14114 top 7/8 Fast, and only the top 1/2 gets to be a Guard.
14115 - Log server fingerprint on startup, so new server operators don't
14116 have to go hunting around their filesystem for it.
14117 - Return a robots.txt on our dirport to discourage google indexing.
14118 - Let the controller ask for GETINFO dir/status/foo so it can ask
14119 directly rather than connecting to the dir port. Only works when
14120 dirport is set for now.
14122 o New config options rather than constants in the code:
14123 - SocksTimeout: How long do we let a socks connection wait
14124 unattached before we fail it?
14125 - CircuitBuildTimeout: Cull non-open circuits that were born
14126 at least this many seconds ago.
14127 - CircuitIdleTimeout: Cull open clean circuits that were born
14128 at least this many seconds ago.
14131 Changes in version 0.1.1.16-rc - 2006-03-18
14132 o Bugfixes on 0.1.1.15-rc:
14133 - Fix assert when the controller asks to attachstream a connect-wait
14134 or resolve-wait stream.
14135 - Now do address rewriting when the controller asks us to attach
14136 to a particular circuit too. This will let Blossom specify
14137 "moria2.exit" without having to learn what moria2's IP address is.
14138 - Make the "tor --verify-config" command-line work again, so people
14139 can automatically check if their torrc will parse.
14140 - Authoritative dirservers no longer require an open connection from
14141 a server to consider him "reachable". We need this change because
14142 when we add new auth dirservers, old servers won't know not to
14144 - Let Tor build on Sun CC again.
14145 - Fix an off-by-one buffer size in dirserv.c that magically never
14146 hit our three authorities but broke sjmurdoch's own tor network.
14147 - If we as a directory mirror don't know of any v1 directory
14148 authorities, then don't try to cache any v1 directories.
14149 - Stop warning about unknown servers in our family when they are
14150 given as hex digests.
14151 - Stop complaining as quickly to the server operator that he
14152 hasn't registered his nickname/key binding.
14153 - Various cleanups so we can add new V2 Auth Dirservers.
14154 - Change "AllowUnverifiedNodes" to "AllowInvalidNodes", to
14155 reflect the updated flags in our v2 dir protocol.
14156 - Resume allowing non-printable characters for exit streams (both
14157 for connecting and for resolving). Now we tolerate applications
14158 that don't follow the RFCs. But continue to block malformed names
14161 o Bugfixes on 0.1.0.x:
14162 - Fix assert bug in close_logs(): when we close and delete logs,
14163 remove them all from the global "logfiles" list.
14164 - Fix minor integer overflow in calculating when we expect to use up
14165 our bandwidth allocation before hibernating.
14166 - Fix a couple of bugs in OpenSSL detection. Also, deal better when
14167 there are multiple SSLs installed with different versions.
14168 - When we try to be a server and Address is not explicitly set and
14169 our hostname resolves to a private IP address, try to use an
14170 interface address if it has a public address. Now Windows machines
14171 that think of themselves as localhost can work by default.
14174 - Let the controller ask for GETINFO dir/server/foo so it can ask
14175 directly rather than connecting to the dir port.
14176 - Let the controller tell us about certain router descriptors
14177 that it doesn't want Tor to use in circuits. Implement
14178 SETROUTERPURPOSE and modify +POSTDESCRIPTOR to do this.
14179 - New config option SafeSocks to reject all application connections
14180 using unsafe socks protocols. Defaults to off.
14183 Changes in version 0.1.1.15-rc - 2006-03-11
14184 o Bugfixes and cleanups:
14185 - When we're printing strings from the network, don't try to print
14186 non-printable characters. This protects us against shell escape
14187 sequence exploits, and also against attacks to fool humans into
14188 misreading their logs.
14189 - Fix a bug where Tor would fail to establish any connections if you
14190 left it off for 24 hours and then started it: we were happy with
14191 the obsolete network statuses, but they all referred to router
14192 descriptors that were too old to fetch, so we ended up with no
14193 valid router descriptors.
14194 - Fix a seg fault in the controller's "getinfo orconn-status"
14195 command while listing status on incoming handshaking connections.
14196 Introduce a status name "NEW" for these connections.
14197 - If we get a linelist or linelist_s config option from the torrc
14198 (e.g. ExitPolicy) and it has no value, warn and skip rather than
14199 silently resetting it to its default.
14200 - Don't abandon entry guards until they've been down or gone for
14202 - Cleaner and quieter log messages.
14205 - New controller signal NEWNYM that makes new application requests
14206 use clean circuits.
14207 - Add a new circuit purpose 'controller' to let the controller ask
14208 for a circuit that Tor won't try to use. Extend the EXTENDCIRCUIT
14209 controller command to let you specify the purpose if you're
14210 starting a new circuit. Add a new SETCIRCUITPURPOSE controller
14211 command to let you change a circuit's purpose after it's been
14213 - Accept "private:*" in routerdesc exit policies; not generated yet
14214 because older Tors do not understand it.
14215 - Add BSD-style contributed startup script "rc.subr" from Peter
14219 Changes in version 0.1.1.14-alpha - 2006-02-20
14220 o Bugfixes on 0.1.1.x:
14221 - Don't die if we ask for a stdout or stderr log (even implicitly)
14222 and we're set to RunAsDaemon -- just warn.
14223 - We still had a few bugs in the OR connection rotation code that
14224 caused directory servers to slowly aggregate connections to other
14225 fast Tor servers. This time for sure!
14226 - Make log entries on Win32 include the name of the function again.
14227 - We were treating a pair of exit policies if they were equal even
14228 if one said accept and the other said reject -- causing us to
14229 not always publish a new descriptor since we thought nothing
14231 - Retry pending server downloads as well as pending networkstatus
14232 downloads when we unexpectedly get a socks request.
14233 - We were ignoring the IS_FAST flag in the directory status,
14234 meaning we were willing to pick trivial-bandwidth nodes for "fast"
14236 - If the controller's SAVECONF command fails (e.g. due to file
14237 permissions), let the controller know that it failed.
14240 - If we're trying to be a Tor server and running Windows 95/98/ME
14241 as a server, explain that we'll likely crash.
14242 - When we're a server, a client asks for an old-style directory,
14243 and our write bucket is empty, don't give it to him. This way
14244 small servers can continue to serve the directory *sometimes*,
14245 without getting overloaded.
14246 - Compress exit policies even more -- look for duplicate lines
14248 - Clients now honor the "guard" flag in the router status when
14249 picking entry guards, rather than looking at is_fast or is_stable.
14250 - Retain unrecognized lines in $DATADIR/state file, so that we can
14251 be forward-compatible.
14252 - Generate 18.0.0.0/8 address policy format in descs when we can;
14253 warn when the mask is not reducible to a bit-prefix.
14254 - Let the user set ControlListenAddress in the torrc. This can be
14255 dangerous, but there are some cases (like a secured LAN) where it
14257 - Split ReachableAddresses into ReachableDirAddresses and
14258 ReachableORAddresses, so we can restrict Dir conns to port 80
14259 and OR conns to port 443.
14260 - Now we can target arch and OS in rpm builds (contributed by
14261 Phobos). Also make the resulting dist-rpm filename match the
14263 - New config options to help controllers: FetchServerDescriptors
14264 and FetchHidServDescriptors for whether to fetch server
14265 info and hidserv info or let the controller do it, and
14266 PublishServerDescriptor and PublishHidServDescriptors.
14267 - Also let the controller set the __AllDirActionsPrivate config
14268 option if you want all directory fetches/publishes to happen via
14269 Tor (it assumes your controller bootstraps your circuits).
14272 Changes in version 0.1.0.17 - 2006-02-17
14273 o Crash bugfixes on 0.1.0.x:
14274 - When servers with a non-zero DirPort came out of hibernation,
14275 sometimes they would trigger an assert.
14277 o Other important bugfixes:
14278 - On platforms that don't have getrlimit (like Windows), we were
14279 artificially constraining ourselves to a max of 1024
14280 connections. Now just assume that we can handle as many as 15000
14281 connections. Hopefully this won't cause other problems.
14283 o Backported features:
14284 - When we're a server, a client asks for an old-style directory,
14285 and our write bucket is empty, don't give it to him. This way
14286 small servers can continue to serve the directory *sometimes*,
14287 without getting overloaded.
14288 - Whenever you get a 503 in response to a directory fetch, try
14289 once more. This will become important once servers start sending
14290 503's whenever they feel busy.
14291 - Fetch a new directory every 120 minutes, not every 40 minutes.
14292 Now that we have hundreds of thousands of users running the old
14293 directory algorithm, it's starting to hurt a lot.
14294 - Bump up the period for forcing a hidden service descriptor upload
14295 from 20 minutes to 1 hour.
14298 Changes in version 0.1.1.13-alpha - 2006-02-09
14299 o Crashes in 0.1.1.x:
14300 - When you tried to setconf ORPort via the controller, Tor would
14301 crash. So people using TorCP to become a server were sad.
14302 - Solve (I hope) the stack-smashing bug that we were seeing on fast
14303 servers. The problem appears to be something do with OpenSSL's
14304 random number generation, or how we call it, or something. Let me
14305 know if the crashes continue.
14306 - Turn crypto hardware acceleration off by default, until we find
14307 somebody smart who can test it for us. (It appears to produce
14308 seg faults in at least some cases.)
14309 - Fix a rare assert error when we've tried all intro points for
14310 a hidden service and we try fetching the service descriptor again:
14311 "Assertion conn->state != AP_CONN_STATE_RENDDESC_WAIT failed"
14314 - Fix a major load balance bug: we were round-robining in 16 KB
14315 chunks, and servers with bandwidthrate of 20 KB, while downloading
14316 a 600 KB directory, would starve their other connections. Now we
14317 try to be a bit more fair.
14318 - Dir authorities and mirrors were never expiring the newest
14319 descriptor for each server, causing memory and directory bloat.
14320 - Fix memory-bloating and connection-bloating bug on servers: We
14321 were never closing any connection that had ever had a circuit on
14322 it, because we were checking conn->n_circuits == 0, yet we had a
14323 bug that let it go negative.
14324 - Make Tor work using squid as your http proxy again -- squid
14325 returns an error if you ask for a URL that's too long, and it uses
14326 a really generic error message. Plus, many people are behind a
14327 transparent squid so they don't even realize it.
14328 - On platforms that don't have getrlimit (like Windows), we were
14329 artificially constraining ourselves to a max of 1024
14330 connections. Now just assume that we can handle as many as 15000
14331 connections. Hopefully this won't cause other problems.
14332 - Add a new config option ExitPolicyRejectPrivate which defaults to
14333 1. This means all exit policies will begin with rejecting private
14334 addresses, unless the server operator explicitly turns it off.
14337 - Clients no longer download descriptors for non-running
14339 - Before we add new directory authorities, we should make it
14340 clear that only v1 authorities should receive/publish hidden
14341 service descriptors.
14344 - As soon as we've fetched some more directory info, immediately
14345 try to download more server descriptors. This way we don't have
14346 a 10 second pause during initial bootstrapping.
14347 - Remove even more loud log messages that the server operator can't
14349 - When we're running an obsolete or un-recommended version, make
14350 the log message more clear about what the problem is and what
14351 versions *are* still recommended.
14352 - Provide a more useful warn message when our onion queue gets full:
14353 the CPU is too slow or the exit policy is too liberal.
14354 - Don't warn when we receive a 503 from a dirserver/cache -- this
14355 will pave the way for them being able to refuse if they're busy.
14356 - When we fail to bind a listener, try to provide a more useful
14357 log message: e.g., "Is Tor already running?"
14358 - Adjust tor-spec to parameterize cell and key lengths. Now Ian
14359 Goldberg can prove things about our handshake protocol more
14361 - MaxConn has been obsolete for a while now. Document the ConnLimit
14362 config option, which is a *minimum* number of file descriptors
14363 that must be available else Tor refuses to start.
14364 - Apply Matt Ghali's --with-syslog-facility patch to ./configure
14365 if you log to syslog and want something other than LOG_DAEMON.
14366 - Make dirservers generate a separate "guard" flag to mean,
14367 "would make a good entry guard". Make clients parse it and vote
14368 on it. Not used by clients yet.
14369 - Implement --with-libevent-dir option to ./configure. Also, improve
14370 search techniques to find libevent, and use those for openssl too.
14371 - Bump the default bandwidthrate to 3 MB, and burst to 6 MB
14372 - Only start testing reachability once we've established a
14373 circuit. This will make startup on dirservers less noisy.
14374 - Don't try to upload hidden service descriptors until we have
14375 established a circuit.
14376 - Fix the controller's "attachstream 0" command to treat conn like
14377 it just connected, doing address remapping, handling .exit and
14378 .onion idioms, and so on. Now we're more uniform in making sure
14379 that the controller hears about new and closing connections.
14382 Changes in version 0.1.1.12-alpha - 2006-01-11
14383 o Bugfixes on 0.1.1.x:
14384 - The fix to close duplicate server connections was closing all
14385 Tor client connections if they didn't establish a circuit
14386 quickly enough. Oops.
14387 - Fix minor memory issue (double-free) that happened on exit.
14389 o Bugfixes on 0.1.0.x:
14390 - Tor didn't warn when it failed to open a log file.
14393 Changes in version 0.1.1.11-alpha - 2006-01-10
14394 o Crashes in 0.1.1.x:
14395 - Include all the assert/crash fixes from 0.1.0.16.
14396 - If you start Tor and then quit very quickly, there were some
14397 races that tried to free things that weren't allocated yet.
14398 - Fix a rare memory stomp if you're running hidden services.
14399 - Fix segfault when specifying DirServer in config without nickname.
14400 - Fix a seg fault when you finish connecting to a server but at
14401 that moment you dump his server descriptor.
14402 - Extendcircuit and Attachstream controller commands would
14403 assert/crash if you don't give them enough arguments.
14404 - Fix an assert error when we're out of space in the connection_list
14405 and we try to post a hidden service descriptor (reported by weasel).
14406 - If you specify a relative torrc path and you set RunAsDaemon in
14407 your torrc, then it chdir()'s to the new directory. If you HUP,
14408 it tries to load the new torrc location, fails, and exits.
14409 The fix: no longer allow a relative path to torrc using -f.
14412 - Implement "entry guards": automatically choose a handful of entry
14413 nodes and stick with them for all circuits. Only pick new guards
14414 when the ones you have are unsuitable, and if the old guards
14415 become suitable again, switch back. This will increase security
14416 dramatically against certain end-point attacks. The EntryNodes
14417 config option now provides some hints about which entry guards you
14418 want to use most; and StrictEntryNodes means to only use those.
14419 - New directory logic: download by descriptor digest, not by
14420 fingerprint. Caches try to download all listed digests from
14421 authorities; clients try to download "best" digests from caches.
14422 This avoids partitioning and isolating attacks better.
14423 - Make the "stable" router flag in network-status be the median of
14424 the uptimes of running valid servers, and make clients pay
14425 attention to the network-status flags. Thus the cutoff adapts
14426 to the stability of the network as a whole, making IRC, IM, etc
14427 connections more reliable.
14430 - Tor servers with dynamic IP addresses were needing to wait 18
14431 hours before they could start doing reachability testing using
14432 the new IP address and ports. This is because they were using
14433 the internal descriptor to learn what to test, yet they were only
14434 rebuilding the descriptor once they decided they were reachable.
14435 - Tor 0.1.1.9 and 0.1.1.10 had a serious bug that caused clients
14436 to download certain server descriptors, throw them away, and then
14437 fetch them again after 30 minutes. Now mirrors throw away these
14438 server descriptors so clients can't get them.
14439 - We were leaving duplicate connections to other ORs open for a week,
14440 rather than closing them once we detect a duplicate. This only
14441 really affected authdirservers, but it affected them a lot.
14442 - Spread the authdirservers' reachability testing over the entire
14443 testing interval, so we don't try to do 500 TLS's at once every
14447 - If the network is down, and we try to connect to a conn because
14448 we have a circuit in mind, and we timeout (30 seconds) because the
14449 network never answers, we were expiring the circuit, but we weren't
14450 obsoleting the connection or telling the entry_guards functions.
14451 - Some Tor servers process billions of cells per day. These statistics
14452 need to be uint64_t's.
14453 - Check for integer overflows in more places, when adding elements
14454 to smartlists. This could possibly prevent a buffer overflow
14455 on malicious huge inputs. I don't see any, but I haven't looked
14457 - ReachableAddresses kept growing new "reject *:*" lines on every
14459 - When you "setconf log" via the controller, it should remove all
14460 logs. We were automatically adding back in a "log notice stdout".
14461 - Newly bootstrapped Tor networks couldn't establish hidden service
14462 circuits until they had nodes with high uptime. Be more tolerant.
14463 - We were marking servers down when they could not answer every piece
14464 of the directory request we sent them. This was far too harsh.
14465 - Fix the torify (tsocks) config file to not use Tor for localhost
14467 - Directory authorities now go to the proper authority when asking for
14468 a networkstatus, even when they want a compressed one.
14469 - Fix a harmless bug that was causing Tor servers to log
14470 "Got an end because of misc error, but we're not an AP. Closing."
14471 - Authorities were treating their own descriptor changes as cosmetic,
14472 meaning the descriptor available in the network-status and the
14473 descriptor that clients downloaded were different.
14474 - The OS X installer was adding a symlink for tor_resolve but
14475 the binary was called tor-resolve (reported by Thomas Hardly).
14476 - Workaround a problem with some http proxies where they refuse GET
14477 requests that specify "Content-Length: 0" (reported by Adrian).
14478 - Fix wrong log message when you add a "HiddenServiceNodes" config
14479 line without any HiddenServiceDir line (reported by Chris Thomas).
14482 - Write the TorVersion into the state file so we have a prayer of
14483 keeping forward and backward compatibility.
14484 - Revive the FascistFirewall config option rather than eliminating it:
14485 now it's a synonym for ReachableAddresses *:80,*:443.
14486 - Clients choose directory servers from the network status lists,
14487 not from their internal list of router descriptors. Now they can
14488 go to caches directly rather than needing to go to authorities
14490 - Directory authorities ignore router descriptors that have only
14491 cosmetic differences: do this for 0.1.0.x servers now too.
14492 - Add a new flag to network-status indicating whether the server
14493 can answer v2 directory requests too.
14494 - Authdirs now stop whining so loudly about bad descriptors that
14495 they fetch from other dirservers. So when there's a log complaint,
14496 it's for sure from a freshly uploaded descriptor.
14497 - Reduce memory requirements in our structs by changing the order
14499 - There used to be two ways to specify your listening ports in a
14500 server descriptor: on the "router" line and with a separate "ports"
14501 line. Remove support for the "ports" line.
14502 - New config option "AuthDirRejectUnlisted" for auth dirservers as
14503 a panic button: if we get flooded with unusable servers we can
14504 revert to only listing servers in the approved-routers file.
14505 - Auth dir servers can now mark a fingerprint as "!reject" or
14506 "!invalid" in the approved-routers file (as its nickname), to
14507 refuse descriptors outright or include them but marked as invalid.
14508 - Servers store bandwidth history across restarts/crashes.
14509 - Add reasons to DESTROY and RELAY_TRUNCATED cells, so clients can
14510 get a better idea of why their circuits failed. Not used yet.
14511 - Directory mirrors now cache up to 16 unrecognized network-status
14512 docs. Now we can add new authdirservers and they'll be cached too.
14513 - When picking a random directory, prefer non-authorities if any
14515 - New controller option "getinfo desc/all-recent" to fetch the
14516 latest server descriptor for every router that Tor knows about.
14519 Changes in version 0.1.0.16 - 2006-01-02
14520 o Crash bugfixes on 0.1.0.x:
14521 - On Windows, build with a libevent patch from "I-M Weasel" to avoid
14522 corrupting the heap, losing FDs, or crashing when we need to resize
14523 the fd_sets. (This affects the Win32 binaries, not Tor's sources.)
14524 - It turns out sparc64 platforms crash on unaligned memory access
14525 too -- so detect and avoid this.
14526 - Handle truncated compressed data correctly (by detecting it and
14528 - Fix possible-but-unlikely free(NULL) in control.c.
14529 - When we were closing connections, there was a rare case that
14530 stomped on memory, triggering seg faults and asserts.
14531 - Avoid potential infinite recursion when building a descriptor. (We
14532 don't know that it ever happened, but better to fix it anyway.)
14533 - We were neglecting to unlink marked circuits from soon-to-close OR
14534 connections, which caused some rare scribbling on freed memory.
14535 - Fix a memory stomping race bug when closing the joining point of two
14536 rendezvous circuits.
14537 - Fix an assert in time parsing found by Steven Murdoch.
14539 o Other bugfixes on 0.1.0.x:
14540 - When we're doing reachability testing, provide more useful log
14541 messages so the operator knows what to expect.
14542 - Do not check whether DirPort is reachable when we are suppressing
14543 advertising it because of hibernation.
14544 - When building with -static or on Solaris, we sometimes needed -ldl.
14545 - When we're deciding whether a stream has enough circuits around
14546 that can handle it, count the freshly dirty ones and not the ones
14547 that are so dirty they won't be able to handle it.
14548 - When we're expiring old circuits, we had a logic error that caused
14549 us to close new rendezvous circuits rather than old ones.
14550 - Give a more helpful log message when you try to change ORPort via
14551 the controller: you should upgrade Tor if you want that to work.
14552 - We were failing to parse Tor versions that start with "Tor ".
14553 - Tolerate faulty streams better: when a stream fails for reason
14554 exitpolicy, stop assuming that the router is lying about his exit
14555 policy. When a stream fails for reason misc, allow it to retry just
14556 as if it was resolvefailed. When a stream has failed three times,
14557 reset its failure count so we can try again and get all three tries.
14560 Changes in version 0.1.1.10-alpha - 2005-12-11
14561 o Correctness bugfixes on 0.1.0.x:
14562 - On Windows, build with a libevent patch from "I-M Weasel" to avoid
14563 corrupting the heap, losing FDs, or crashing when we need to resize
14564 the fd_sets. (This affects the Win32 binaries, not Tor's sources.)
14565 - Stop doing the complex voodoo overkill checking for insecure
14566 Diffie-Hellman keys. Just check if it's in [2,p-2] and be happy.
14567 - When we were closing connections, there was a rare case that
14568 stomped on memory, triggering seg faults and asserts.
14569 - We were neglecting to unlink marked circuits from soon-to-close OR
14570 connections, which caused some rare scribbling on freed memory.
14571 - When we're deciding whether a stream has enough circuits around
14572 that can handle it, count the freshly dirty ones and not the ones
14573 that are so dirty they won't be able to handle it.
14574 - Recover better from TCP connections to Tor servers that are
14575 broken but don't tell you (it happens!); and rotate TLS
14576 connections once a week.
14577 - When we're expiring old circuits, we had a logic error that caused
14578 us to close new rendezvous circuits rather than old ones.
14579 - Fix a scary-looking but apparently harmless bug where circuits
14580 would sometimes start out in state CIRCUIT_STATE_OR_WAIT at
14581 servers, and never switch to state CIRCUIT_STATE_OPEN.
14582 - When building with -static or on Solaris, we sometimes needed to
14584 - Give a useful message when people run Tor as the wrong user,
14585 rather than telling them to start chowning random directories.
14586 - We were failing to inform the controller about new .onion streams.
14588 o Security bugfixes on 0.1.0.x:
14589 - Refuse server descriptors if the fingerprint line doesn't match
14590 the included identity key. Tor doesn't care, but other apps (and
14591 humans) might actually be trusting the fingerprint line.
14592 - We used to kill the circuit when we receive a relay command we
14593 don't recognize. Now we just drop it.
14594 - Start obeying our firewall options more rigorously:
14595 . If we can't get to a dirserver directly, try going via Tor.
14596 . Don't ever try to connect (as a client) to a place our
14597 firewall options forbid.
14598 . If we specify a proxy and also firewall options, obey the
14599 firewall options even when we're using the proxy: some proxies
14600 can only proxy to certain destinations.
14601 - Fix a bug found by Lasse Overlier: when we were making internal
14602 circuits (intended to be cannibalized later for rendezvous and
14603 introduction circuits), we were picking them so that they had
14604 useful exit nodes. There was no need for this, and it actually
14605 aids some statistical attacks.
14606 - Start treating internal circuits and exit circuits separately.
14607 It's important to keep them separate because internal circuits
14608 have their last hops picked like middle hops, rather than like
14609 exit hops. So exiting on them will break the user's expectations.
14611 o Bugfixes on 0.1.1.x:
14612 - Take out the mis-feature where we tried to detect IP address
14613 flapping for people with DynDNS, and chose not to upload a new
14614 server descriptor sometimes.
14615 - Try to be compatible with OpenSSL 0.9.6 again.
14616 - Log fix: when the controller is logging about .onion addresses,
14617 sometimes it didn't include the ".onion" part of the address.
14618 - Don't try to modify options->DirServers internally -- if the
14619 user didn't specify any, just add the default ones directly to
14620 the trusted dirserver list. This fixes a bug where people running
14621 controllers would use SETCONF on some totally unrelated config
14622 option, and Tor would start yelling at them about changing their
14624 - Let the controller's redirectstream command specify a port, in
14625 case the controller wants to change that too.
14626 - When we requested a pile of server descriptors, we sometimes
14627 accidentally launched a duplicate request for the first one.
14628 - Bugfix for trackhostexits: write down the fingerprint of the
14629 chosen exit, not its nickname, because the chosen exit might not
14631 - When parsing foo.exit, if foo is unknown, and we are leaving
14632 circuits unattached, set the chosen_exit field and leave the
14633 address empty. This matters because controllers got confused
14635 - Directory authorities no longer try to download server
14636 descriptors that they know they will reject.
14638 o Features and updates:
14639 - Replace balanced trees with hash tables: this should make stuff
14640 significantly faster.
14641 - Resume using the AES counter-mode implementation that we ship,
14642 rather than OpenSSL's. Ours is significantly faster.
14643 - Many other CPU and memory improvements.
14644 - Add a new config option FastFirstHopPK (on by default) so clients
14645 do a trivial crypto handshake for their first hop, since TLS has
14646 already taken care of confidentiality and authentication.
14647 - Add a new config option TestSocks so people can see if their
14648 applications are using socks4, socks4a, socks5-with-ip, or
14649 socks5-with-hostname. This way they don't have to keep mucking
14650 with tcpdump and wondering if something got cached somewhere.
14651 - Warn when listening on a public address for socks. I suspect a
14652 lot of people are setting themselves up as open socks proxies,
14653 and they have no idea that jerks on the Internet are using them,
14654 since they simply proxy the traffic into the Tor network.
14655 - Add "private:*" as an alias in configuration for policies. Now
14656 you can simplify your exit policy rather than needing to list
14657 every single internal or nonroutable network space.
14658 - Add a new controller event type that allows controllers to get
14659 all server descriptors that were uploaded to a router in its role
14660 as authoritative dirserver.
14661 - Start shipping socks-extensions.txt, tor-doc-unix.html,
14662 tor-doc-server.html, and stylesheet.css in the tarball.
14663 - Stop shipping tor-doc.html in the tarball.
14666 Changes in version 0.1.1.9-alpha - 2005-11-15
14667 o Usability improvements:
14668 - Start calling it FooListenAddress rather than FooBindAddress,
14669 since few of our users know what it means to bind an address
14671 - Reduce clutter in server logs. We're going to try to make
14672 them actually usable now. New config option ProtocolWarnings that
14673 lets you hear about how _other Tors_ are breaking the protocol. Off
14675 - Divide log messages into logging domains. Once we put some sort
14676 of interface on this, it will let people looking at more verbose
14677 log levels specify the topics they want to hear more about.
14678 - Make directory servers return better http 404 error messages
14679 instead of a generic "Servers unavailable".
14680 - Check for even more Windows version flags when writing the platform
14681 string in server descriptors, and note any we don't recognize.
14682 - Clean up more of the OpenSSL memory when exiting, so we can detect
14683 memory leaks better.
14684 - Make directory authorities be non-versioning, non-naming by
14685 default. Now we can add new directory servers without requiring
14686 their operators to pay close attention.
14687 - When logging via syslog, include the pid whenever we provide
14688 a log entry. Suggested by Todd Fries.
14690 o Performance improvements:
14691 - Directory servers now silently throw away new descriptors that
14692 haven't changed much if the timestamps are similar. We do this to
14693 tolerate older Tor servers that upload a new descriptor every 15
14694 minutes. (It seemed like a good idea at the time.)
14695 - Inline bottleneck smartlist functions; use fast versions by default.
14696 - Add a "Map from digest to void*" abstraction digestmap_t so we
14697 can do less hex encoding/decoding. Use it in router_get_by_digest()
14698 to resolve a performance bottleneck.
14699 - Allow tor_gzip_uncompress to extract as much as possible from
14700 truncated compressed data. Try to extract as many
14701 descriptors as possible from truncated http responses (when
14702 DIR_PURPOSE_FETCH_ROUTERDESC).
14703 - Make circ->onionskin a pointer, not a static array. moria2 was using
14704 125000 circuit_t's after it had been up for a few weeks, which
14705 translates to 20+ megs of wasted space.
14706 - The private half of our EDH handshake keys are now chosen out
14707 of 320 bits, not 1024 bits. (Suggested by Ian Goldberg.)
14709 o Security improvements:
14710 - Start making directory caches retain old routerinfos, so soon
14711 clients can start asking by digest of descriptor rather than by
14712 fingerprint of server.
14713 - Add half our entropy from RAND_poll in OpenSSL. This knows how
14714 to use egd (if present), openbsd weirdness (if present), vms/os2
14715 weirdness (if we ever port there), and more in the future.
14717 o Bugfixes on 0.1.0.x:
14718 - Do round-robin writes of at most 16 kB per write. This might be
14719 more fair on loaded Tor servers, and it might resolve our Windows
14720 crash bug. It might also slow things down.
14721 - Our TLS handshakes were generating a single public/private
14722 keypair for the TLS context, rather than making a new one for
14723 each new connections. Oops. (But we were still rotating them
14724 periodically, so it's not so bad.)
14725 - When we were cannibalizing a circuit with a particular exit
14726 node in mind, we weren't checking to see if that exit node was
14727 already present earlier in the circuit. Oops.
14728 - When a Tor server's IP changes (e.g. from a dyndns address),
14729 upload a new descriptor so clients will learn too.
14730 - Really busy servers were keeping enough circuits open on stable
14731 connections that they were wrapping around the circuit_id
14732 space. (It's only two bytes.) This exposed a bug where we would
14733 feel free to reuse a circuit_id even if it still exists but has
14734 been marked for close. Try to fix this bug. Some bug remains.
14735 - If we would close a stream early (e.g. it asks for a .exit that
14736 we know would refuse it) but the LeaveStreamsUnattached config
14737 option is set by the controller, then don't close it.
14739 o Bugfixes on 0.1.1.8-alpha:
14740 - Fix a big pile of memory leaks, some of them serious.
14741 - Do not try to download a routerdesc if we would immediately reject
14743 - Resume inserting a newline between all router descriptors when
14744 generating (old style) signed directories, since our spec says
14746 - When providing content-type application/octet-stream for
14747 server descriptors using .z, we were leaving out the
14748 content-encoding header. Oops. (Everything tolerated this just
14749 fine, but that doesn't mean we need to be part of the problem.)
14750 - Fix a potential seg fault in getconf and getinfo using version 1
14751 of the controller protocol.
14752 - Avoid crash: do not check whether DirPort is reachable when we
14753 are suppressing it because of hibernation.
14754 - Make --hash-password not crash on exit.
14757 Changes in version 0.1.1.8-alpha - 2005-10-07
14758 o New features (major):
14759 - Clients don't download or use the directory anymore. Now they
14760 download and use network-statuses from the trusted dirservers,
14761 and fetch individual server descriptors as needed from mirrors.
14762 See dir-spec.txt for all the gory details.
14763 - Be more conservative about whether to advertise our DirPort.
14764 The main change is to not advertise if we're running at capacity
14765 and either a) we could hibernate or b) our capacity is low and
14766 we're using a default DirPort.
14767 - Use OpenSSL's AES when OpenSSL has version 0.9.7 or later.
14769 o New features (minor):
14770 - Try to be smart about when to retry network-status and
14771 server-descriptor fetches. Still needs some tuning.
14772 - Stop parsing, storing, or using running-routers output (but
14773 mirrors still cache and serve it).
14774 - Consider a threshold of versioning dirservers (dirservers who have
14775 an opinion about which Tor versions are still recommended) before
14776 deciding whether to warn the user that he's obsolete.
14777 - Dirservers can now reject/invalidate by key and IP, with the
14778 config options "AuthDirInvalid" and "AuthDirReject". This is
14779 useful since currently we automatically list servers as running
14780 and usable even if we know they're jerks.
14781 - Provide dire warnings to any users who set DirServer; move it out
14782 of torrc.sample and into torrc.complete.
14783 - Add MyFamily to torrc.sample in the server section.
14784 - Add nicknames to the DirServer line, so we can refer to them
14785 without requiring all our users to memorize their IP addresses.
14786 - When we get an EOF or a timeout on a directory connection, note
14787 how many bytes of serverdesc we are dropping. This will help
14788 us determine whether it is smart to parse incomplete serverdesc
14790 - Add a new function to "change pseudonyms" -- that is, to stop
14791 using any currently-dirty circuits for new streams, so we don't
14792 link new actions to old actions. Currently it's only called on
14793 HUP (or SIGNAL RELOAD).
14794 - On sighup, if UseHelperNodes changed to 1, use new circuits.
14795 - Start using RAND_bytes rather than RAND_pseudo_bytes from
14796 OpenSSL. Also, reseed our entropy every hour, not just at
14797 startup. And entropy in 512-bit chunks, not 160-bit chunks.
14799 o Fixes on 0.1.1.7-alpha:
14800 - Nobody ever implemented EVENT_ADDRMAP for control protocol
14801 version 0, so don't let version 0 controllers ask for it.
14802 - If you requested something with too many newlines via the
14803 v1 controller protocol, you could crash tor.
14804 - Fix a number of memory leaks, including some pretty serious ones.
14805 - Re-enable DirPort testing again, so Tor servers will be willing
14806 to advertise their DirPort if it's reachable.
14807 - On TLS handshake, only check the other router's nickname against
14808 its expected nickname if is_named is set.
14810 o Fixes forward-ported from 0.1.0.15:
14811 - Don't crash when we don't have any spare file descriptors and we
14812 try to spawn a dns or cpu worker.
14813 - Make the numbers in read-history and write-history into uint64s,
14814 so they don't overflow and publish negatives in the descriptor.
14816 o Fixes on 0.1.0.x:
14817 - For the OS X package's modified privoxy config file, comment
14818 out the "logfile" line so we don't log everything passed
14820 - We were whining about using socks4 or socks5-with-local-lookup
14821 even when it's an IP in the "virtual" range we designed exactly
14823 - We were leaking some memory every time the client changes IPs.
14824 - Never call free() on tor_malloc()d memory. This will help us
14825 use dmalloc to detect memory leaks.
14826 - Check for named servers when looking them up by nickname;
14827 warn when we'recalling a non-named server by its nickname;
14828 don't warn twice about the same name.
14829 - Try to list MyFamily elements by key, not by nickname, and warn
14830 if we've not heard of the server.
14831 - Make windows platform detection (uname equivalent) smarter.
14832 - It turns out sparc64 doesn't like unaligned access either.
14835 Changes in version 0.1.0.15 - 2005-09-23
14836 o Bugfixes on 0.1.0.x:
14837 - Reject ports 465 and 587 (spam targets) in default exit policy.
14838 - Don't crash when we don't have any spare file descriptors and we
14839 try to spawn a dns or cpu worker.
14840 - Get rid of IgnoreVersion undocumented config option, and make us
14841 only warn, never exit, when we're running an obsolete version.
14842 - Don't try to print a null string when your server finds itself to
14843 be unreachable and the Address config option is empty.
14844 - Make the numbers in read-history and write-history into uint64s,
14845 so they don't overflow and publish negatives in the descriptor.
14846 - Fix a minor memory leak in smartlist_string_remove().
14847 - We were only allowing ourselves to upload a server descriptor at
14848 most every 20 minutes, even if it changed earlier than that.
14849 - Clean up log entries that pointed to old URLs.
14852 Changes in version 0.1.1.7-alpha - 2005-09-14
14853 o Fixes on 0.1.1.6-alpha:
14854 - Exit servers were crashing when people asked them to make a
14855 connection to an address not in their exit policy.
14856 - Looking up a non-existent stream for a v1 control connection would
14858 - Fix a seg fault if we ask a dirserver for a descriptor by
14859 fingerprint but he doesn't know about him.
14860 - SETCONF was appending items to linelists, not clearing them.
14861 - SETCONF SocksBindAddress killed Tor if it fails to bind. Now back
14862 out and refuse the setconf if it would fail.
14863 - Downgrade the dirserver log messages when whining about
14867 - Add Peter Palfrader's check-tor script to tor/contrib/
14868 It lets you easily check whether a given server (referenced by
14869 nickname) is reachable by you.
14870 - Numerous changes to move towards client-side v2 directories. Not
14873 o Fixes on 0.1.0.x:
14874 - If the user gave tor an odd number of command-line arguments,
14875 we were silently ignoring the last one. Now we complain and fail.
14876 [This wins the oldest-bug prize -- this bug has been present since
14877 November 2002, as released in Tor 0.0.0.]
14878 - Do not use unaligned memory access on alpha, mips, or mipsel.
14879 It *works*, but is very slow, so we treat them as if it doesn't.
14880 - Retry directory requests if we fail to get an answer we like
14881 from a given dirserver (we were retrying before, but only if
14882 we fail to connect).
14883 - When writing the RecommendedVersions line, sort them first.
14884 - When the client asked for a rendezvous port that the hidden
14885 service didn't want to provide, we were sending an IP address
14886 back along with the end cell. Fortunately, it was zero. But stop
14888 - Correct "your server is reachable" log entries to indicate that
14889 it was self-testing that told us so.
14892 Changes in version 0.1.1.6-alpha - 2005-09-09
14893 o Fixes on 0.1.1.5-alpha:
14894 - We broke fascistfirewall in 0.1.1.5-alpha. Oops.
14895 - Fix segfault in unit tests in 0.1.1.5-alpha. Oops.
14896 - Fix bug with tor_memmem finding a match at the end of the string.
14897 - Make unit tests run without segfaulting.
14898 - Resolve some solaris x86 compile warnings.
14899 - Handle duplicate lines in approved-routers files without warning.
14900 - Fix bug where as soon as a server refused any requests due to his
14901 exit policy (e.g. when we ask for localhost and he tells us that's
14902 127.0.0.1 and he won't do it), we decided he wasn't obeying his
14903 exit policy using him for any exits.
14904 - Only do openssl hardware accelerator stuff if openssl version is
14907 o New controller features/fixes:
14908 - Add a "RESETCONF" command so you can set config options like
14909 AllowUnverifiedNodes and LongLivedPorts to "". Also, if you give
14910 a config option in the torrc with no value, then it clears it
14911 entirely (rather than setting it to its default).
14912 - Add a "GETINFO config-file" to tell us where torrc is.
14913 - Avoid sending blank lines when GETINFO replies should be empty.
14914 - Add a QUIT command for the controller (for using it manually).
14915 - Fix a bug in SAVECONF that was adding default dirservers and
14916 other redundant entries to the torrc file.
14918 o Start on the new directory design:
14919 - Generate, publish, cache, serve new network-status format.
14920 - Publish individual descriptors (by fingerprint, by "all", and by
14922 - Publish client and server recommended versions separately.
14923 - Allow tor_gzip_uncompress() to handle multiple concatenated
14924 compressed strings. Serve compressed groups of router
14925 descriptors. The compression logic here could be more
14927 - Distinguish v1 authorities (all currently trusted directories)
14928 from v2 authorities (all trusted directories).
14929 - Change DirServers config line to note which dirs are v1 authorities.
14930 - Add configuration option "V1AuthoritativeDirectory 1" which
14931 moria1, moria2, and tor26 should set.
14932 - Remove option when getting directory cache to see whether they
14933 support running-routers; they all do now. Replace it with one
14934 to see whether caches support v2 stuff.
14937 - Dirservers now do their own external reachability testing of each
14938 Tor server, and only list them as running if they've been found to
14939 be reachable. We also send back warnings to the server's logs if
14940 it uploads a descriptor that we already believe is unreachable.
14941 - Implement exit enclaves: if we know an IP address for the
14942 destination, and there's a running Tor server at that address
14943 which allows exit to the destination, then extend the circuit to
14944 that exit first. This provides end-to-end encryption and end-to-end
14945 authentication. Also, if the user wants a .exit address or enclave,
14946 use 4 hops rather than 3, and cannibalize a general circ for it
14948 - Permit transitioning from ORPort=0 to ORPort!=0, and back, from the
14949 controller. Also, rotate dns and cpu workers if the controller
14950 changes options that will affect them; and initialize the dns
14951 worker cache tree whether or not we start out as a server.
14952 - Only upload a new server descriptor when options change, 18
14953 hours have passed, uptime is reset, or bandwidth changes a lot.
14954 - Check [X-]Forwarded-For headers in HTTP requests when generating
14955 log messages. This lets people run dirservers (and caches) behind
14956 Apache but still know which IP addresses are causing warnings.
14958 o Config option changes:
14959 - Replace (Fascist)Firewall* config options with a new
14960 ReachableAddresses option that understands address policies.
14961 For example, "ReachableAddresses *:80,*:443"
14962 - Get rid of IgnoreVersion undocumented config option, and make us
14963 only warn, never exit, when we're running an obsolete version.
14964 - Make MonthlyAccountingStart config option truly obsolete now.
14966 o Fixes on 0.1.0.x:
14967 - Reject ports 465 and 587 in the default exit policy, since
14968 people have started using them for spam too.
14969 - It turns out we couldn't bootstrap a network since we added
14970 reachability detection in 0.1.0.1-rc. Good thing the Tor network
14971 has never gone down. Add an AssumeReachable config option to let
14972 servers and dirservers bootstrap. When we're trying to build a
14973 high-uptime or high-bandwidth circuit but there aren't enough
14974 suitable servers, try being less picky rather than simply failing.
14975 - Our logic to decide if the OR we connected to was the right guy
14976 was brittle and maybe open to a mitm for unverified routers.
14977 - We weren't cannibalizing circuits correctly for
14978 CIRCUIT_PURPOSE_C_ESTABLISH_REND and
14979 CIRCUIT_PURPOSE_S_ESTABLISH_INTRO, so we were being forced to
14980 build those from scratch. This should make hidden services faster.
14981 - Predict required circuits better, with an eye toward making hidden
14982 services faster on the service end.
14983 - Retry streams if the exit node sends back a 'misc' failure. This
14984 should result in fewer random failures. Also, after failing
14985 from resolve failed or misc, reset the num failures, so we give
14986 it a fair shake next time we try.
14987 - Clean up the rendezvous warn log msgs, and downgrade some to info.
14988 - Reduce severity on logs about dns worker spawning and culling.
14989 - When we're shutting down and we do something like try to post a
14990 server descriptor or rendezvous descriptor, don't complain that
14991 we seem to be unreachable. Of course we are, we're shutting down.
14992 - Add TTLs to RESOLVED, CONNECTED, and END_REASON_EXITPOLICY cells.
14993 We don't use them yet, but maybe one day our DNS resolver will be
14994 able to discover them.
14995 - Make ContactInfo mandatory for authoritative directory servers.
14996 - Require server descriptors to list IPv4 addresses -- hostnames
14997 are no longer allowed. This also fixes some potential security
14998 problems with people providing hostnames as their address and then
14999 preferentially resolving them to partition users.
15000 - Change log line for unreachability to explicitly suggest /etc/hosts
15001 as the culprit. Also make it clearer what IP address and ports we're
15002 testing for reachability.
15003 - Put quotes around user-supplied strings when logging so users are
15004 more likely to realize if they add bad characters (like quotes)
15006 - Let auth dir servers start without specifying an Address config
15008 - Make unit tests (and other invocations that aren't the real Tor)
15009 run without launching listeners, creating subdirectories, and so on.
15012 Changes in version 0.1.1.5-alpha - 2005-08-08
15013 o Bugfixes included in 0.1.0.14.
15015 o Bugfixes on 0.1.0.x:
15016 - If you write "HiddenServicePort 6667 127.0.0.1 6668" in your
15017 torrc rather than "HiddenServicePort 6667 127.0.0.1:6668",
15018 it would silently using ignore the 6668.
15021 Changes in version 0.1.0.14 - 2005-08-08
15022 o Bugfixes on 0.1.0.x:
15023 - Fix the other half of the bug with crypto handshakes
15025 - Fix an assert trigger if you send a 'signal term' via the
15026 controller when it's listening for 'event info' messages.
15029 Changes in version 0.1.1.4-alpha - 2005-08-04
15030 o Bugfixes included in 0.1.0.13.
15033 - Improve tor_gettimeofday() granularity on windows.
15034 - Make clients regenerate their keys when their IP address changes.
15035 - Implement some more GETINFO goodness: expose helper nodes, config
15036 options, getinfo keys.
15039 Changes in version 0.1.0.13 - 2005-08-04
15040 o Bugfixes on 0.1.0.x:
15041 - Fix a critical bug in the security of our crypto handshakes.
15042 - Fix a size_t underflow in smartlist_join_strings2() that made
15043 it do bad things when you hand it an empty smartlist.
15044 - Fix Windows installer to ship Tor license (thanks to Aphex for
15045 pointing out this oversight) and put a link to the doc directory
15047 - Explicitly set no-unaligned-access for sparc: it turns out the
15048 new gcc's let you compile broken code, but that doesn't make it
15052 Changes in version 0.1.1.3-alpha - 2005-07-23
15053 o Bugfixes on 0.1.1.2-alpha:
15054 - Fix a bug in handling the controller's "post descriptor"
15056 - Fix several bugs in handling the controller's "extend circuit"
15058 - Fix a bug in handling the controller's "stream status" event.
15059 - Fix an assert failure if we have a controller listening for
15060 circuit events and we go offline.
15061 - Re-allow hidden service descriptors to publish 0 intro points.
15062 - Fix a crash when generating your hidden service descriptor if
15063 you don't have enough intro points already.
15065 o New features on 0.1.1.2-alpha:
15066 - New controller function "getinfo accounting", to ask how
15067 many bytes we've used in this time period.
15068 - Experimental support for helper nodes: a lot of the risk from
15069 a small static adversary comes because users pick new random
15070 nodes every time they rebuild a circuit. Now users will try to
15071 stick to the same small set of entry nodes if they can. Not
15072 enabled by default yet.
15074 o Bugfixes on 0.1.0.12:
15075 - If you're an auth dir server, always publish your dirport,
15076 even if you haven't yet found yourself to be reachable.
15077 - Fix a size_t underflow in smartlist_join_strings2() that made
15078 it do bad things when you hand it an empty smartlist.
15081 Changes in version 0.1.0.12 - 2005-07-18
15082 o New directory servers:
15083 - tor26 has changed IP address.
15085 o Bugfixes on 0.1.0.x:
15086 - Fix a possible double-free in tor_gzip_uncompress().
15087 - When --disable-threads is set, do not search for or link against
15088 pthreads libraries.
15089 - Don't trigger an assert if an authoritative directory server
15090 claims its dirport is 0.
15091 - Fix bug with removing Tor as an NT service: some people were
15092 getting "The service did not return an error." Thanks to Matt
15096 Changes in version 0.1.1.2-alpha - 2005-07-15
15097 o New directory servers:
15098 - tor26 has changed IP address.
15100 o Bugfixes on 0.1.0.x, crashes/leaks:
15101 - Port the servers-not-obeying-their-exit-policies fix from
15103 - Fix an fd leak in start_daemon().
15104 - On Windows, you can't always reopen a port right after you've
15105 closed it. So change retry_listeners() to only close and re-open
15106 ports that have changed.
15107 - Fix a possible double-free in tor_gzip_uncompress().
15109 o Bugfixes on 0.1.0.x, usability:
15110 - When tor_socketpair() fails in Windows, give a reasonable
15111 Windows-style errno back.
15112 - Let people type "tor --install" as well as "tor -install" when
15114 want to make it an NT service.
15115 - NT service patch from Matt Edman to improve error messages.
15116 - When the controller asks for a config option with an abbreviated
15117 name, give the full name in our response.
15118 - Correct the man page entry on TrackHostExitsExpire.
15119 - Looks like we were never delivering deflated (i.e. compressed)
15120 running-routers lists, even when asked. Oops.
15121 - When --disable-threads is set, do not search for or link against
15122 pthreads libraries.
15124 o Bugfixes on 0.1.1.x:
15125 - Fix a seg fault with autodetecting which controller version is
15129 - New hidden service descriptor format: put a version in it, and
15130 let people specify introduction/rendezvous points that aren't
15131 in "the directory" (which is subjective anyway).
15132 - Allow the DEBUG controller event to work again. Mark certain log
15133 entries as "don't tell this to controllers", so we avoid cycles.
15136 Changes in version 0.1.0.11 - 2005-06-30
15137 o Bugfixes on 0.1.0.x:
15138 - Fix major security bug: servers were disregarding their
15139 exit policies if clients behaved unexpectedly.
15140 - Make OS X init script check for missing argument, so we don't
15141 confuse users who invoke it incorrectly.
15142 - Fix a seg fault in "tor --hash-password foo".
15143 - The MAPADDRESS control command was broken.
15146 Changes in version 0.1.1.1-alpha - 2005-06-29
15148 - Make OS X init script check for missing argument, so we don't
15149 confuse users who invoke it incorrectly.
15150 - Fix a seg fault in "tor --hash-password foo".
15151 - Fix a possible way to DoS dirservers.
15152 - When we complain that your exit policy implicitly allows local or
15153 private address spaces, name them explicitly so operators can
15155 - Make the log message less scary when all the dirservers are
15156 temporarily unreachable.
15157 - We were printing the number of idle dns workers incorrectly when
15161 - Revised controller protocol (version 1) that uses ascii rather
15162 than binary. Add supporting libraries in python and java so you
15163 can use the controller from your applications without caring how
15164 our protocol works.
15165 - Spiffy new support for crypto hardware accelerators. Can somebody
15169 Changes in version 0.0.9.10 - 2005-06-16
15170 o Bugfixes on 0.0.9.x (backported from 0.1.0.10):
15171 - Refuse relay cells that claim to have a length larger than the
15172 maximum allowed. This prevents a potential attack that could read
15173 arbitrary memory (e.g. keys) from an exit server's process
15177 Changes in version 0.1.0.10 - 2005-06-14
15178 o Allow a few EINVALs from libevent before dying. Warn on kqueue with
15179 libevent before 1.1a.
15182 Changes in version 0.1.0.9-rc - 2005-06-09
15184 - Reset buf->highwater every time buf_shrink() is called, not just on
15185 a successful shrink. This was causing significant memory bloat.
15186 - Fix buffer overflow when checking hashed passwords.
15187 - Security fix: if seeding the RNG on Win32 fails, quit.
15188 - Allow seeding the RNG on Win32 even when you're not running as
15190 - Disable threading on Solaris too. Something is wonky with it,
15191 cpuworkers, and reentrant libs.
15192 - Reenable the part of the code that tries to flush as soon as an
15193 OR outbuf has a full TLS record available. Perhaps this will make
15194 OR outbufs not grow as huge except in rare cases, thus saving lots
15195 of CPU time plus memory.
15196 - Reject malformed .onion addresses rather then passing them on as
15197 normal web requests.
15198 - Adapt patch from Adam Langley: fix possible memory leak in
15199 tor_lookup_hostname().
15200 - Initialize libevent later in the startup process, so the logs are
15201 already established by the time we start logging libevent warns.
15202 - Use correct errno on win32 if libevent fails.
15203 - Check and warn about known-bad/slow libevent versions.
15204 - Pay more attention to the ClientOnly config option.
15205 - Have torctl.in/tor.sh.in check for location of su binary (needed
15207 - Correct/add man page entries for LongLivedPorts, ExitPolicy,
15208 KeepalivePeriod, ClientOnly, NoPublish, HttpProxy, HttpsProxy,
15209 HttpProxyAuthenticator
15210 - Stop warning about sigpipes in the logs. We're going to
15211 pretend that getting these occassionally is normal and fine.
15212 - Resolve OS X installer bugs: stop claiming to be 0.0.9.2 in
15214 installer screens; and don't put stuff into StartupItems unless
15215 the user asks you to.
15216 - Require servers that use the default dirservers to have public IP
15217 addresses. We have too many servers that are configured with private
15218 IPs and their admins never notice the log entries complaining that
15219 their descriptors are being rejected.
15220 - Add OSX uninstall instructions. An actual uninstall script will
15224 Changes in version 0.1.0.8-rc - 2005-05-23
15226 - It turns out that kqueue on OS X 10.3.9 was causing kernel
15227 panics. Disable kqueue on all OS X Tors.
15228 - Fix RPM: remove duplicate line accidentally added to the rpm
15230 - Disable threads on openbsd too, since its gethostaddr is not
15232 - Tolerate libevent 0.8 since it still works, even though it's
15234 - Enable building on Red Hat 9.0 again.
15235 - Allow the middle hop of the testing circuit to be running any
15236 version, now that most of them have the bugfix to let them connect
15237 to unknown servers. This will allow reachability testing to work
15238 even when 0.0.9.7-0.0.9.9 become obsolete.
15239 - Handle relay cells with rh.length too large. This prevents
15240 a potential attack that could read arbitrary memory (maybe even
15241 keys) from the exit server's process.
15242 - We screwed up the dirport reachability testing when we don't yet
15243 have a cached version of the directory. Hopefully now fixed.
15244 - Clean up router_load_single_router() (used by the controller),
15245 so it doesn't seg fault on error.
15246 - Fix a minor memory leak when somebody establishes an introduction
15247 point at your Tor server.
15248 - If a socks connection ends because read fails, don't warn that
15249 you're not sending a socks reply back.
15252 - Add HttpProxyAuthenticator config option too, that works like
15253 the HttpsProxyAuthenticator config option.
15254 - Encode hashed controller passwords in hex instead of base64,
15255 to make it easier to write controllers.
15258 Changes in version 0.1.0.7-rc - 2005-05-17
15260 - Fix a bug in the OS X package installer that prevented it from
15261 installing on Tiger.
15262 - Fix a script bug in the OS X package installer that made it
15263 complain during installation.
15264 - Find libevent even if it's hiding in /usr/local/ and your
15265 CFLAGS and LDFLAGS don't tell you to look there.
15266 - Be able to link with libevent as a shared library (the default
15267 after 1.0d), even if it's hiding in /usr/local/lib and even
15268 if you haven't added /usr/local/lib to your /etc/ld.so.conf,
15269 assuming you're running gcc. Otherwise fail and give a useful
15271 - Fix a bug in the RPM packager: set home directory for _tor to
15272 something more reasonable when first installing.
15273 - Free a minor amount of memory that is still reachable on exit.
15276 Changes in version 0.1.0.6-rc - 2005-05-14
15278 - Implement --disable-threads configure option. Disable threads on
15279 netbsd by default, because it appears to have no reentrant resolver
15281 - Apple's OS X 10.4.0 ships with a broken kqueue. The new libevent
15282 release (1.1) detects and disables kqueue if it's broken.
15283 - Append default exit policy before checking for implicit internal
15284 addresses. Now we don't log a bunch of complaints on startup
15285 when using the default exit policy.
15286 - Some people were putting "Address " in their torrc, and they had
15287 a buggy resolver that resolved " " to 0.0.0.0. Oops.
15288 - If DataDir is ~/.tor, and that expands to /.tor, then default to
15289 LOCALSTATEDIR/tor instead.
15290 - Fix fragmented-message bug in TorControl.py.
15291 - Resolve a minor bug which would prevent unreachable dirports
15292 from getting suppressed in the published descriptor.
15293 - When the controller gave us a new descriptor, we weren't resolving
15294 it immediately, so Tor would think its address was 0.0.0.0 until
15295 we fetched a new directory.
15296 - Fix an uppercase/lowercase case error in suppressing a bogus
15297 libevent warning on some Linuxes.
15300 - Begin scrubbing sensitive strings from logs by default. Turn off
15301 the config option SafeLogging if you need to do debugging.
15302 - Switch to a new buffer management algorithm, which tries to avoid
15303 reallocing and copying quite as much. In first tests it looks like
15304 it uses *more* memory on average, but less cpu.
15305 - First cut at support for "create-fast" cells. Clients can use
15306 these when extending to their first hop, since the TLS already
15307 provides forward secrecy and authentication. Not enabled on
15309 - When dirservers refuse a router descriptor, we now log its
15310 contactinfo, platform, and the poster's IP address.
15311 - Call tor_free_all instead of connections_free_all after forking, to
15312 save memory on systems that need to fork.
15313 - Whine at you if you're a server and you don't set your contactinfo.
15314 - Implement --verify-config command-line option to check if your torrc
15315 is valid without actually launching Tor.
15316 - Rewrite address "serifos.exit" to "localhost.serifos.exit"
15317 rather than just rejecting it.
15320 Changes in version 0.1.0.5-rc - 2005-04-27
15322 - Stop trying to print a null pointer if an OR conn fails because
15323 we didn't like its cert.
15325 - Switch our internal buffers implementation to use a ring buffer,
15326 to hopefully improve performance for fast servers a lot.
15327 - Add HttpsProxyAuthenticator support (basic auth only), based
15328 on patch from Adam Langley.
15329 - Bump the default BandwidthRate from 1 MB to 2 MB, to accommodate
15330 the fast servers that have been joining lately.
15331 - Give hidden service accesses extra time on the first attempt,
15332 since 60 seconds is often only barely enough. This might improve
15334 - Improve performance for dirservers: stop re-parsing the whole
15335 directory every time you regenerate it.
15336 - Add more debugging info to help us find the weird dns freebsd
15337 pthreads bug; cleaner debug messages to help track future issues.
15340 Changes in version 0.0.9.9 - 2005-04-23
15341 o Bugfixes on 0.0.9.x:
15342 - If unofficial Tor clients connect and send weird TLS certs, our
15343 Tor server triggers an assert. This release contains a minimal
15344 backport from the broader fix that we put into 0.1.0.4-rc.
15347 Changes in version 0.1.0.4-rc - 2005-04-23
15349 - If unofficial Tor clients connect and send weird TLS certs, our
15350 Tor server triggers an assert. Stop asserting, and start handling
15351 TLS errors better in other situations too.
15352 - When the controller asks us to tell it about all the debug-level
15353 logs, it turns out we were generating debug-level logs while
15354 telling it about them, which turns into a bad loop. Now keep
15355 track of whether you're sending a debug log to the controller,
15356 and don't log when you are.
15357 - Fix the "postdescriptor" feature of the controller interface: on
15358 non-complete success, only say "done" once.
15360 - Clients are now willing to load balance over up to 2mB, not 1mB,
15361 of advertised bandwidth capacity.
15362 - Add a NoPublish config option, so you can be a server (e.g. for
15363 testing running Tor servers in other Tor networks) without
15364 publishing your descriptor to the primary dirservers.
15367 Changes in version 0.1.0.3-rc - 2005-04-08
15368 o Improvements on 0.1.0.2-rc:
15369 - Client now retries when streams end early for 'hibernating' or
15370 'resource limit' reasons, rather than failing them.
15371 - More automated handling for dirserver operators:
15372 - Automatically approve nodes running 0.1.0.2-rc or later,
15373 now that the the reachability detection stuff is working.
15374 - Now we allow two unverified servers with the same nickname
15375 but different keys. But if a nickname is verified, only that
15376 nickname+key are allowed.
15377 - If you're an authdirserver connecting to an address:port,
15378 and it's not the OR you were expecting, forget about that
15379 descriptor. If he *was* the one you were expecting, then forget
15380 about all other descriptors for that address:port.
15381 - Allow servers to publish descriptors from 12 hours in the future.
15382 Corollary: only whine about clock skew from the dirserver if
15383 he's a trusted dirserver (since now even verified servers could
15384 have quite wrong clocks).
15385 - Adjust maximum skew and age for rendezvous descriptors: let skew
15386 be 48 hours rather than 90 minutes.
15387 - Efficiency improvements:
15388 - Keep a big splay tree of (circid,orconn)->circuit mappings to make
15389 it much faster to look up a circuit for each relay cell.
15390 - Remove most calls to assert_all_pending_dns_resolves_ok(),
15391 since they're eating our cpu on exit nodes.
15392 - Stop wasting time doing a case insensitive comparison for every
15393 dns name every time we do any lookup. Canonicalize the names to
15394 lowercase and be done with it.
15395 - Start sending 'truncated' cells back rather than destroy cells,
15396 if the circuit closes in front of you. This means we won't have
15397 to abandon partially built circuits.
15398 - Only warn once per nickname from add_nickname_list_to_smartlist
15399 per failure, so an entrynode or exitnode choice that's down won't
15401 - Put a note in the torrc about abuse potential with the default
15403 - Revise control spec and implementation to allow all log messages to
15404 be sent to controller with their severities intact (suggested by
15405 Matt Edman). Update TorControl to handle new log event types.
15406 - Provide better explanation messages when controller's POSTDESCRIPTOR
15408 - Stop putting nodename in the Platform string in server descriptors.
15409 It doesn't actually help, and it is confusing/upsetting some people.
15411 o Bugfixes on 0.1.0.2-rc:
15412 - We were printing the host mask wrong in exit policies in server
15413 descriptors. This isn't a critical bug though, since we were still
15414 obeying the exit policy internally.
15415 - Fix Tor when compiled with libevent but without pthreads: move
15416 connection_unregister() from _connection_free() to
15418 - Fix an assert trigger (already fixed in 0.0.9.x): when we have
15419 the rare mysterious case of accepting a conn on 0.0.0.0:0, then
15420 when we look through the connection array, we'll find any of the
15421 cpu/dnsworkers. This is no good.
15423 o Bugfixes on 0.0.9.8:
15424 - Fix possible bug on threading platforms (e.g. win32) which was
15425 leaking a file descriptor whenever a cpuworker or dnsworker died.
15426 - When using preferred entry or exit nodes, ignore whether the
15427 circuit wants uptime or capacity. They asked for the nodes, they
15429 - chdir() to your datadirectory at the *end* of the daemonize process,
15430 not the beginning. This was a problem because the first time you
15431 run tor, if your datadir isn't there, and you have runasdaemon set
15432 to 1, it will try to chdir to it before it tries to create it. Oops.
15433 - Handle changed router status correctly when dirserver reloads
15434 fingerprint file. We used to be dropping all unverified descriptors
15435 right then. The bug was hidden because we would immediately
15436 fetch a directory from another dirserver, which would include the
15437 descriptors we just dropped.
15438 - When we're connecting to an OR and he's got a different nickname/key
15439 than we were expecting, only complain loudly if we're an OP or a
15440 dirserver. Complaining loudly to the OR admins just confuses them.
15441 - Tie MAX_DIR_SIZE to MAX_BUF_SIZE, so now directory sizes won't get
15442 artificially capped at 500kB.
15445 Changes in version 0.0.9.8 - 2005-04-07
15446 o Bugfixes on 0.0.9.x:
15447 - We have a bug that I haven't found yet. Sometimes, very rarely,
15448 cpuworkers get stuck in the 'busy' state, even though the cpuworker
15449 thinks of itself as idle. This meant that no new circuits ever got
15450 established. Here's a workaround to kill any cpuworker that's been
15451 busy for more than 100 seconds.
15454 Changes in version 0.1.0.2-rc - 2005-04-01
15455 o Bugfixes on 0.1.0.1-rc:
15456 - Fixes on reachability detection:
15457 - Don't check for reachability while hibernating.
15458 - If ORPort is reachable but DirPort isn't, still publish the
15459 descriptor, but zero out DirPort until it's found reachable.
15460 - When building testing circs for ORPort testing, use only
15461 high-bandwidth nodes, so fewer circuits fail.
15462 - Complain about unreachable ORPort separately from unreachable
15463 DirPort, so the user knows what's going on.
15464 - Make sure we only conclude ORPort reachability if we didn't
15465 initiate the conn. Otherwise we could falsely conclude that
15466 we're reachable just because we connected to the guy earlier
15467 and he used that same pipe to extend to us.
15468 - Authdirservers shouldn't do ORPort reachability detection,
15469 since they're in clique mode, so it will be rare to find a
15470 server not already connected to them.
15471 - When building testing circuits, always pick middle hops running
15472 Tor 0.0.9.7, so we avoid the "can't extend to unknown routers"
15473 bug. (This is a kludge; it will go away when 0.0.9.x becomes
15475 - When we decide we're reachable, actually publish our descriptor
15477 - Fix bug in redirectstream in the controller.
15478 - Fix the state descriptor strings so logs don't claim edge streams
15479 are in a different state than they actually are.
15480 - Use recent libevent features when possible (this only really affects
15481 win32 and osx right now, because the new libevent with these
15482 features hasn't been released yet). Add code to suppress spurious
15484 - Prevent possible segfault in connection_close_unattached_ap().
15485 - Fix newlines on torrc in win32.
15486 - Improve error msgs when tor-resolve fails.
15488 o Improvements on 0.0.9.x:
15489 - New experimental script tor/contrib/ExerciseServer.py (needs more
15490 work) that uses the controller interface to build circuits and
15491 fetch pages over them. This will help us bootstrap servers that
15492 have lots of capacity but haven't noticed it yet.
15493 - New experimental script tor/contrib/PathDemo.py (needs more work)
15494 that uses the controller interface to let you choose whole paths
15496 "<hostname>.<path,separated by dots>.<length of path>.path"
15497 - When we've connected to an OR and handshaked but didn't like
15498 the result, we were closing the conn without sending destroy
15499 cells back for pending circuits. Now send those destroys.
15502 Changes in version 0.0.9.7 - 2005-04-01
15503 o Bugfixes on 0.0.9.x:
15504 - Fix another race crash bug (thanks to Glenn Fink for reporting).
15505 - Compare identity to identity, not to nickname, when extending to
15506 a router not already in the directory. This was preventing us from
15507 extending to unknown routers. Oops.
15508 - Make sure to create OS X Tor user in <500 range, so we aren't
15509 creating actual system users.
15510 - Note where connection-that-hasn't-sent-end was marked, and fix
15511 a few really loud instances of this harmless bug (it's fixed more
15515 Changes in version 0.1.0.1-rc - 2005-03-28
15517 - Add reachability testing. Your Tor server will automatically try
15518 to see if its ORPort and DirPort are reachable from the outside,
15519 and it won't upload its descriptor until it decides they are.
15520 - Handle unavailable hidden services better. Handle slow or busy
15521 hidden services better.
15522 - Add support for CONNECTing through https proxies, with "HttpsProxy"
15524 - New exit policy: accept most low-numbered ports, rather than
15525 rejecting most low-numbered ports.
15526 - More Tor controller support (still experimental). See
15527 http://tor.eff.org/doc/control-spec.txt for all the new features,
15528 including signals to emulate unix signals from any platform;
15529 redirectstream; extendcircuit; mapaddress; getinfo; postdescriptor;
15530 closestream; closecircuit; etc.
15531 - Make nt services work and start on startup on win32 (based on
15532 patch by Matt Edman).
15533 - Add a new AddressMap config directive to rewrite incoming socks
15534 addresses. This lets you, for example, declare an implicit
15535 required exit node for certain sites.
15536 - Add a new TrackHostExits config directive to trigger addressmaps
15537 for certain incoming socks addresses -- for sites that break when
15538 your exit keeps changing (based on patch by Mike Perry).
15539 - Redo the client-side dns cache so it's just an addressmap too.
15540 - Notice when our IP changes, and reset stats/uptime/reachability.
15541 - When an application is using socks5, give him the whole variety of
15542 potential socks5 responses (connect refused, host unreachable, etc),
15543 rather than just "success" or "failure".
15544 - A more sane version numbering system. See
15545 http://tor.eff.org/cvs/tor/doc/version-spec.txt for details.
15546 - New contributed script "exitlist": a simple python script to
15547 parse directories and find Tor nodes that exit to listed
15549 - New contributed script "privoxy-tor-toggle" to toggle whether
15550 Privoxy uses Tor. Seems to be configured for Debian by default.
15551 - Report HTTP reasons to client when getting a response from directory
15552 servers -- so you can actually know what went wrong.
15553 - New config option MaxAdvertisedBandwidth which lets you advertise
15554 a low bandwidthrate (to not attract as many circuits) while still
15555 allowing a higher bandwidthrate in reality.
15557 o Robustness/stability fixes:
15558 - Make Tor use Niels Provos's libevent instead of its current
15559 poll-but-sometimes-select mess. This will let us use faster async
15560 cores (like epoll, kpoll, and /dev/poll), and hopefully work better
15562 - pthread support now too. This was forced because when we forked,
15563 we ended up wasting a lot of duplicate ram over time. Also switch
15564 to foo_r versions of some library calls to allow reentry and
15566 - Better handling for heterogeneous / unreliable nodes:
15567 - Annotate circuits w/ whether they aim to contain high uptime nodes
15568 and/or high capacity nodes. When building circuits, choose
15570 - This means that every single node in an intro rend circuit,
15571 not just the last one, will have a minimum uptime.
15572 - New config option LongLivedPorts to indicate application streams
15573 that will want high uptime circuits.
15574 - Servers reset uptime when a dir fetch entirely fails. This
15575 hopefully reflects stability of the server's network connectivity.
15576 - If somebody starts his tor server in Jan 2004 and then fixes his
15577 clock, don't make his published uptime be a year.
15578 - Reset published uptime when you wake up from hibernation.
15579 - Introduce a notion of 'internal' circs, which are chosen without
15580 regard to the exit policy of the last hop. Intro and rendezvous
15581 circs must be internal circs, to avoid leaking information. Resolve
15582 and connect streams can use internal circs if they want.
15583 - New circuit pooling algorithm: make sure to have enough circs around
15584 to satisfy any predicted ports, and also make sure to have 2 internal
15585 circs around if we've required internal circs lately (and with high
15586 uptime if we've seen that lately too).
15587 - Split NewCircuitPeriod option into NewCircuitPeriod (30 secs),
15588 which describes how often we retry making new circuits if current
15589 ones are dirty, and MaxCircuitDirtiness (10 mins), which describes
15590 how long we're willing to make use of an already-dirty circuit.
15591 - Cannibalize GENERAL circs to be C_REND, C_INTRO, S_INTRO, and S_REND
15592 circ as necessary, if there are any completed ones lying around
15593 when we try to launch one.
15594 - Make hidden services try to establish a rendezvous for 30 seconds,
15595 rather than for n (where n=3) attempts to build a circuit.
15596 - Change SHUTDOWN_WAIT_LENGTH from a fixed 30 secs to a config option
15597 "ShutdownWaitLength".
15598 - Try to be more zealous about calling connection_edge_end when
15599 things go bad with edge conns in connection.c.
15600 - Revise tor-spec to add more/better stream end reasons.
15601 - Revise all calls to connection_edge_end to avoid sending "misc",
15602 and to take errno into account where possible.
15605 - Fix a race condition that can trigger an assert, when we have a
15606 pending create cell and an OR connection fails right then.
15607 - Fix several double-mark-for-close bugs, e.g. where we were finding
15608 a conn for a cell even if that conn is already marked for close.
15609 - Make sequence of log messages when starting on win32 with no config
15610 file more reasonable.
15611 - When choosing an exit node for a new non-internal circ, don't take
15612 into account whether it'll be useful for any pending x.onion
15613 addresses -- it won't.
15614 - Turn addr_policy_compare from a tristate to a quadstate; this should
15615 help address our "Ah, you allow 1.2.3.4:80. You are a good choice
15616 for google.com" problem.
15617 - Make "platform" string in descriptor more accurate for Win32 servers,
15618 so it's not just "unknown platform".
15619 - Fix an edge case in parsing config options (thanks weasel).
15620 If they say "--" on the commandline, it's not an option.
15621 - Reject odd-looking addresses at the client (e.g. addresses that
15622 contain a colon), rather than having the server drop them because
15624 - tor-resolve requests were ignoring .exit if there was a working circuit
15625 they could use instead.
15626 - REUSEADDR on normal platforms means you can rebind to the port
15627 right after somebody else has let it go. But REUSEADDR on win32
15628 means to let you bind to the port _even when somebody else
15629 already has it bound_! So, don't do that on Win32.
15630 - Change version parsing logic: a version is "obsolete" if it is not
15631 recommended and (1) there is a newer recommended version in the
15632 same series, or (2) there are no recommended versions in the same
15633 series, but there are some recommended versions in a newer series.
15634 A version is "new" if it is newer than any recommended version in
15636 - Stop most cases of hanging up on a socks connection without sending
15640 - Require BandwidthRate to be at least 20kB/s for servers.
15641 - When a dirserver causes you to give a warn, mention which dirserver
15643 - New config option DirAllowPrivateAddresses for authdirservers.
15644 Now by default they refuse router descriptors that have non-IP or
15645 private-IP addresses.
15646 - Stop publishing socksport in the directory, since it's not
15647 actually meant to be public. For compatibility, publish a 0 there
15649 - Change DirFetchPeriod/StatusFetchPeriod to have a special "Be
15650 smart" value, that is low for servers and high for clients.
15651 - If our clock jumps forward by 100 seconds or more, assume something
15652 has gone wrong with our network and abandon all not-yet-used circs.
15653 - Warn when exit policy implicitly allows local addresses.
15654 - If we get an incredibly skewed timestamp from a dirserver mirror
15655 that isn't a verified OR, don't warn -- it's probably him that's
15657 - Since we ship our own Privoxy on OS X, tweak it so it doesn't write
15658 cookies to disk and doesn't log each web request to disk. (Thanks
15659 to Brett Carrington for pointing this out.)
15660 - When a client asks us for a dir mirror and we don't have one,
15661 launch an attempt to get a fresh one.
15662 - If we're hibernating and we get a SIGINT, exit immediately.
15663 - Add --with-dmalloc ./configure option, to track memory leaks.
15664 - And try to free all memory on closing, so we can detect what
15666 - Cache local dns resolves correctly even when they're .exit
15668 - Give a better warning when some other server advertises an
15669 ORPort that is actually an apache running ssl.
15670 - Add "opt hibernating 1" to server descriptor to make it clearer
15671 whether the server is hibernating.
15674 Changes in version 0.0.9.6 - 2005-03-24
15675 o Bugfixes on 0.0.9.x (crashes and asserts):
15676 - Add new end stream reasons to maintainance branch. Fix bug where
15677 reason (8) could trigger an assert. Prevent bug from recurring.
15678 - Apparently win32 stat wants paths to not end with a slash.
15679 - Fix assert triggers in assert_cpath_layer_ok(), where we were
15680 blowing away the circuit that conn->cpath_layer points to, then
15681 checking to see if the circ is well-formed. Backport check to make
15682 sure we dont use the cpath on a closed connection.
15683 - Prevent circuit_resume_edge_reading_helper() from trying to package
15684 inbufs for marked-for-close streams.
15685 - Don't crash on hup if your options->address has become unresolvable.
15686 - Some systems (like OS X) sometimes accept() a connection and tell
15687 you the remote host is 0.0.0.0:0. If this happens, due to some
15688 other mis-features, we get confused; so refuse the conn for now.
15690 o Bugfixes on 0.0.9.x (other):
15691 - Fix harmless but scary "Unrecognized content encoding" warn message.
15692 - Add new stream error reason: TORPROTOCOL reason means "you are not
15693 speaking a version of Tor I understand; say bye-bye to your stream."
15694 - Be willing to cache directories from up to ROUTER_MAX_AGE seconds
15695 into the future, now that we are more tolerant of skew. This
15696 resolves a bug where a Tor server would refuse to cache a directory
15697 because all the directories it gets are too far in the future;
15698 yet the Tor server never logs any complaints about clock skew.
15699 - Mac packaging magic: make man pages useable, and do not overwrite
15700 existing torrc files.
15701 - Make OS X log happily to /var/log/tor/tor.log
15704 Changes in version 0.0.9.5 - 2005-02-22
15705 o Bugfixes on 0.0.9.x:
15706 - Fix an assert race at exit nodes when resolve requests fail.
15707 - Stop picking unverified dir mirrors--it only leads to misery.
15708 - Patch from Matt Edman to make NT services work better. Service
15709 support is still not compiled into the executable by default.
15710 - Patch from Dmitri Bely so the Tor service runs better under
15711 the win32 SYSTEM account.
15712 - Make tor-resolve actually work (?) on Win32.
15713 - Fix a sign bug when getrlimit claims to have 4+ billion
15714 file descriptors available.
15715 - Stop refusing to start when bandwidthburst == bandwidthrate.
15716 - When create cells have been on the onion queue more than five
15717 seconds, just send back a destroy and take them off the list.
15720 Changes in version 0.0.9.4 - 2005-02-03
15721 o Bugfixes on 0.0.9:
15722 - Fix an assert bug that took down most of our servers: when
15723 a server claims to have 1 GB of bandwidthburst, don't
15725 - Don't crash as badly if we have spawned the max allowed number
15726 of dnsworkers, or we're out of file descriptors.
15727 - Block more file-sharing ports in the default exit policy.
15728 - MaxConn is now automatically set to the hard limit of max
15729 file descriptors we're allowed (ulimit -n), minus a few for
15731 - Give a clearer message when servers need to raise their
15732 ulimit -n when they start running out of file descriptors.
15733 - SGI Compatibility patches from Jan Schaumann.
15734 - Tolerate a corrupt cached directory better.
15735 - When a dirserver hasn't approved your server, list which one.
15736 - Go into soft hibernation after 95% of the bandwidth is used,
15737 not 99%. This is especially important for daily hibernators who
15738 have a small accounting max. Hopefully it will result in fewer
15739 cut connections when the hard hibernation starts.
15740 - Load-balance better when using servers that claim more than
15741 800kB/s of capacity.
15742 - Make NT services work (experimental, only used if compiled in).
15745 Changes in version 0.0.9.3 - 2005-01-21
15746 o Bugfixes on 0.0.9:
15747 - Backport the cpu use fixes from main branch, so busy servers won't
15748 need as much processor time.
15749 - Work better when we go offline and then come back, or when we
15750 run Tor at boot before the network is up. We do this by
15751 optimistically trying to fetch a new directory whenever an
15752 application request comes in and we think we're offline -- the
15753 human is hopefully a good measure of when the network is back.
15754 - Backport some minimal hidserv bugfixes: keep rend circuits open as
15755 long as you keep using them; actually publish hidserv descriptors
15756 shortly after they change, rather than waiting 20-40 minutes.
15757 - Enable Mac startup script by default.
15758 - Fix duplicate dns_cancel_pending_resolve reported by Giorgos Pallas.
15759 - When you update AllowUnverifiedNodes or FirewallPorts via the
15760 controller's setconf feature, we were always appending, never
15762 - When you update HiddenServiceDir via setconf, it was screwing up
15763 the order of reading the lines, making it fail.
15764 - Do not rewrite a cached directory back to the cache; otherwise we
15765 will think it is recent and not fetch a newer one on startup.
15766 - Workaround for webservers that lie about Content-Encoding: Tor
15767 now tries to autodetect compressed directories and compression
15768 itself. This lets us Proxypass dir fetches through apache.
15771 Changes in version 0.0.9.2 - 2005-01-04
15772 o Bugfixes on 0.0.9 (crashes and asserts):
15773 - Fix an assert on startup when the disk is full and you're logging
15775 - If you do socks4 with an IP of 0.0.0.x but *don't* provide a socks4a
15776 style address, then we'd crash.
15777 - Fix an assert trigger when the running-routers string we get from
15778 a dirserver is broken.
15779 - Make worker threads start and run on win32. Now win32 servers
15781 - Bandaid (not actually fix, but now it doesn't crash) an assert
15782 where the dns worker dies mysteriously and the main Tor process
15783 doesn't remember anything about the address it was resolving.
15785 o Bugfixes on 0.0.9 (Win32):
15786 - Workaround for brain-damaged __FILE__ handling on MSVC: keep Nick's
15787 name out of the warning/assert messages.
15788 - Fix a superficial "unhandled error on read" bug on win32.
15789 - The win32 installer no longer requires a click-through for our
15790 license, since our Free Software license grants rights but does not
15792 - Win32: When connecting to a dirserver fails, try another one
15793 immediately. (This was already working for non-win32 Tors.)
15794 - Stop trying to parse $HOME on win32 when hunting for default
15796 - Make tor-resolve.c work on win32 by calling network_init().
15798 o Bugfixes on 0.0.9 (other):
15799 - Make 0.0.9.x build on Solaris again.
15800 - Due to a fencepost error, we were blowing away the \n when reporting
15801 confvalue items in the controller. So asking for multiple config
15802 values at once couldn't work.
15803 - When listing circuits that are pending on an opening OR connection,
15804 if we're an OR we were listing circuits that *end* at us as
15805 being pending on every listener, dns/cpu worker, etc. Stop that.
15806 - Dirservers were failing to create 'running-routers' or 'directory'
15807 strings if we had more than some threshold of routers. Fix them so
15808 they can handle any number of routers.
15809 - Fix a superficial "Duplicate mark for close" bug.
15810 - Stop checking for clock skew for OR connections, even for servers.
15811 - Fix a fencepost error that was chopping off the last letter of any
15812 nickname that is the maximum allowed nickname length.
15813 - Update URLs in log messages so they point to the new website.
15814 - Fix a potential problem in mangling server private keys while
15815 writing to disk (not triggered yet, as far as we know).
15816 - Include the licenses for other free software we include in Tor,
15817 now that we're shipping binary distributions more regularly.
15820 Changes in version 0.0.9.1 - 2004-12-15
15821 o Bugfixes on 0.0.9:
15822 - Make hibernation actually work.
15823 - Make HashedControlPassword config option work.
15824 - When we're reporting event circuit status to a controller,
15825 don't use the stream status code.
15828 Changes in version 0.0.9 - 2004-12-12
15830 - Clean up manpage and torrc.sample file.
15831 - Clean up severities and text of log warnings.
15833 - Make servers trigger an assert when they enter hibernation.
15836 Changes in version 0.0.9rc7 - 2004-12-08
15837 o Bugfixes on 0.0.9rc:
15838 - Fix a stack-trashing crash when an exit node begins hibernating.
15839 - Avoid looking at unallocated memory while considering which
15840 ports we need to build circuits to cover.
15841 - Stop a sigpipe: when an 'end' cell races with eof from the app,
15842 we shouldn't hold-open-until-flush if the eof arrived first.
15843 - Fix a bug with init_cookie_authentication() in the controller.
15844 - When recommending new-format log lines, if the upper bound is
15845 LOG_ERR, leave it implicit.
15847 o Bugfixes on 0.0.8.1:
15848 - Fix a whole slew of memory leaks.
15849 - Fix isspace() and friends so they still make Solaris happy
15850 but also so they don't trigger asserts on win32.
15851 - Fix parse_iso_time on platforms without strptime (eg win32).
15852 - win32: tolerate extra "readable" events better.
15853 - win32: when being multithreaded, leave parent fdarray open.
15854 - Make unit tests work on win32.
15857 Changes in version 0.0.9rc6 - 2004-12-06
15858 o Bugfixes on 0.0.9pre:
15859 - Clean up some more integer underflow opportunities (not exploitable
15861 - While hibernating, hup should not regrow our listeners.
15862 - Send an end to the streams we close when we hibernate, rather
15863 than just chopping them off.
15864 - React to eof immediately on non-open edge connections.
15866 o Bugfixes on 0.0.8.1:
15867 - Calculate timeout for waiting for a connected cell from the time
15868 we sent the begin cell, not from the time the stream started. If
15869 it took a long time to establish the circuit, we would time out
15870 right after sending the begin cell.
15871 - Fix router_compare_addr_to_addr_policy: it was not treating a port
15872 of * as always matching, so we were picking reject *:* nodes as
15873 exit nodes too. Oops.
15876 - New circuit building strategy: keep a list of ports that we've
15877 used in the past 6 hours, and always try to have 2 circuits open
15878 or on the way that will handle each such port. Seed us with port
15879 80 so web users won't complain that Tor is "slow to start up".
15880 - Make kill -USR1 dump more useful stats about circuits.
15881 - When warning about retrying or giving up, print the address, so
15882 the user knows which one it's talking about.
15883 - If you haven't used a clean circuit in an hour, throw it away,
15884 just to be on the safe side. (This means after 6 hours a totally
15885 unused Tor client will have no circuits open.)
15888 Changes in version 0.0.9rc5 - 2004-12-01
15889 o Bugfixes on 0.0.8.1:
15890 - Disallow NDEBUG. We don't ever want anybody to turn off debug.
15891 - Let resolve conns retry/expire also, rather than sticking around
15893 - If we are using select, make sure we stay within FD_SETSIZE.
15895 o Bugfixes on 0.0.9pre:
15896 - Fix integer underflow in tor_vsnprintf() that may be exploitable,
15897 but doesn't seem to be currently; thanks to Ilja van Sprundel for
15899 - If anybody set DirFetchPostPeriod, give them StatusFetchPeriod
15900 instead. Impose minima and maxima for all *Period options; impose
15901 even tighter maxima for fetching if we are a caching dirserver.
15902 Clip rather than rejecting.
15903 - Fetch cached running-routers from servers that serve it (that is,
15904 authdirservers and servers running 0.0.9rc5-cvs or later.)
15907 - Accept *:706 (silc) in default exit policy.
15908 - Implement new versioning format for post 0.1.
15909 - Support "foo.nickname.exit" addresses, to let Alice request the
15910 address "foo" as viewed by exit node "nickname". Based on a patch
15912 - Make tor --version --version dump the cvs Id of every file.
15915 Changes in version 0.0.9rc4 - 2004-11-28
15916 o Bugfixes on 0.0.8.1:
15917 - Make windows sockets actually non-blocking (oops), and handle
15918 win32 socket errors better.
15920 o Bugfixes on 0.0.9rc1:
15921 - Actually catch the -USR2 signal.
15924 Changes in version 0.0.9rc3 - 2004-11-25
15925 o Bugfixes on 0.0.8.1:
15926 - Flush the log file descriptor after we print "Tor opening log file",
15927 so we don't see those messages days later.
15929 o Bugfixes on 0.0.9rc1:
15930 - Make tor-resolve work again.
15931 - Avoid infinite loop in tor-resolve if tor hangs up on it.
15932 - Fix an assert trigger for clients/servers handling resolves.
15935 Changes in version 0.0.9rc2 - 2004-11-24
15936 o Bugfixes on 0.0.9rc1:
15937 - I broke socks5 support while fixing the eof bug.
15938 - Allow unitless bandwidths and intervals; they default to bytes
15940 - New servers don't start out hibernating; they are active until
15941 they run out of bytes, so they have a better estimate of how
15942 long it takes, and so their operators can know they're working.
15945 Changes in version 0.0.9rc1 - 2004-11-23
15946 o Bugfixes on 0.0.8.1:
15947 - Finally fix a bug that's been plaguing us for a year:
15948 With high load, circuit package window was reaching 0. Whenever
15949 we got a circuit-level sendme, we were reading a lot on each
15950 socket, but only writing out a bit. So we would eventually reach
15951 eof. This would be noticed and acted on even when there were still
15952 bytes sitting in the inbuf.
15953 - When poll() is interrupted, we shouldn't believe the revents values.
15955 o Bugfixes on 0.0.9pre6:
15956 - Fix hibernate bug that caused pre6 to be broken.
15957 - Don't keep rephist info for routers that haven't had activity for
15958 24 hours. (This matters now that clients have keys, since we track
15960 - Never call close_temp_logs while validating log options.
15961 - Fix backslash-escaping on tor.sh.in and torctl.in.
15964 - Implement weekly/monthly/daily accounting: now you specify your
15965 hibernation properties by
15966 AccountingMax N bytes|KB|MB|GB|TB
15967 AccountingStart day|week|month [day] HH:MM
15968 Defaults to "month 1 0:00".
15969 - Let bandwidth and interval config options be specified as 5 bytes,
15970 kb, kilobytes, etc; and as seconds, minutes, hours, days, weeks.
15971 - kill -USR2 now moves all logs to loglevel debug (kill -HUP to
15972 get back to normal.)
15973 - If your requested entry or exit node has advertised bandwidth 0,
15975 - Be more greedy about filling up relay cells -- we try reading again
15976 once we've processed the stuff we read, in case enough has arrived
15977 to fill the last cell completely.
15978 - Apply NT service patch from Osamu Fujino. Still needs more work.
15981 Changes in version 0.0.9pre6 - 2004-11-15
15982 o Bugfixes on 0.0.8.1:
15983 - Fix assert failure on malformed socks4a requests.
15984 - Use identity comparison, not nickname comparison, to choose which
15985 half of circuit-ID-space each side gets to use. This is needed
15986 because sometimes we think of a router as a nickname, and sometimes
15987 as a hex ID, and we can't predict what the other side will do.
15988 - Catch and ignore SIGXFSZ signals when log files exceed 2GB; our
15989 write() call will fail and we handle it there.
15990 - Add a FAST_SMARTLIST define to optionally inline smartlist_get
15991 and smartlist_len, which are two major profiling offenders.
15993 o Bugfixes on 0.0.9pre5:
15994 - Fix a bug in read_all that was corrupting config files on windows.
15995 - When we're raising the max number of open file descriptors to
15996 'unlimited', don't log that we just raised it to '-1'.
15997 - Include event code with events, as required by control-spec.txt.
15998 - Don't give a fingerprint when clients do --list-fingerprint:
15999 it's misleading, because it will never be the same again.
16000 - Stop using strlcpy in tor_strndup, since it was slowing us
16002 - Remove warn on startup about missing cached-directory file.
16003 - Make kill -USR1 work again.
16004 - Hibernate if we start tor during the "wait for wakeup-time" phase
16005 of an accounting interval. Log our hibernation plans better.
16006 - Authoritative dirservers now also cache their directory, so they
16007 have it on start-up.
16010 - Fetch running-routers; cache running-routers; compress
16011 running-routers; serve compressed running-routers.z
16012 - Add NSI installer script contributed by J Doe.
16013 - Commit VC6 and VC7 workspace/project files.
16014 - Commit a tor.spec for making RPM files, with help from jbash.
16015 - Add contrib/torctl.in contributed by Glenn Fink.
16016 - Implement the control-spec's SAVECONF command, to write your
16017 configuration to torrc.
16018 - Get cookie authentication for the controller closer to working.
16019 - Include control-spec.txt in the tarball.
16020 - When set_conf changes our server descriptor, upload a new copy.
16021 But don't upload it too often if there are frequent changes.
16022 - Document authentication config in man page, and document signals
16024 - Clean up confusing parts of man page and torrc.sample.
16025 - Make expand_filename handle ~ and ~username.
16026 - Use autoconf to enable largefile support where necessary. Use
16027 ftello where available, since ftell can fail at 2GB.
16028 - Distinguish between TOR_TLS_CLOSE and TOR_TLS_ERROR, so we can
16029 log more informatively.
16030 - Give a slightly more useful output for "tor -h".
16031 - Refuse application socks connections to port 0.
16032 - Check clock skew for verified servers, but allow unverified
16033 servers and clients to have any clock skew.
16034 - Break DirFetchPostPeriod into:
16035 - DirFetchPeriod for fetching full directory,
16036 - StatusFetchPeriod for fetching running-routers,
16037 - DirPostPeriod for posting server descriptor,
16038 - RendPostPeriod for posting hidden service descriptors.
16039 - Make sure the hidden service descriptors are at a random offset
16040 from each other, to hinder linkability.
16043 Changes in version 0.0.9pre5 - 2004-11-09
16044 o Bugfixes on 0.0.9pre4:
16045 - Fix a seg fault in unit tests (doesn't affect main program).
16046 - Fix an assert bug where a hidden service provider would fail if
16047 the first hop of his rendezvous circuit was down.
16048 - Hidden service operators now correctly handle version 1 style
16049 INTRODUCE1 cells (nobody generates them still, so not a critical
16051 - If do_hup fails, actually notice.
16052 - Handle more errnos from accept() without closing the listener.
16053 Some OpenBSD machines were closing their listeners because
16054 they ran out of file descriptors.
16055 - Send resolve cells to exit routers that are running a new
16056 enough version of the resolve code to work right.
16057 - Better handling of winsock includes on non-MSV win32 compilers.
16058 - Some people had wrapped their tor client/server in a script
16059 that would restart it whenever it died. This did not play well
16060 with our "shut down if your version is obsolete" code. Now people
16061 don't fetch a new directory if their local cached version is
16063 - Make our autogen.sh work on ksh as well as bash.
16066 - Hibernation: New config option "AccountingMaxKB" lets you
16067 set how many KBytes per month you want to allow your server to
16068 consume. Rather than spreading those bytes out evenly over the
16069 month, we instead hibernate for some of the month and pop up
16070 at a deterministic time, work until the bytes are consumed, then
16071 hibernate again. Config option "MonthlyAccountingStart" lets you
16072 specify which day of the month your billing cycle starts on.
16073 - Control interface: a separate program can now talk to your
16074 client/server over a socket, and get/set config options, receive
16075 notifications of circuits and streams starting/finishing/dying,
16076 bandwidth used, etc. The next step is to get some GUIs working.
16077 Let us know if you want to help out. See doc/control-spec.txt .
16078 - Ship a contrib/tor-control.py as an example script to interact
16079 with the control port.
16080 - "tor --hash-password zzyxz" will output a salted password for
16081 use in authenticating to the control interface.
16082 - New log format in config:
16083 "Log minsev[-maxsev] stdout|stderr|syslog" or
16084 "Log minsev[-maxsev] file /var/foo"
16087 - DirPolicy config option, to let people reject incoming addresses
16088 from their dirserver.
16089 - "tor --list-fingerprint" will list your identity key fingerprint
16091 - Add "pass" target for RedirectExit, to make it easier to break
16092 out of a sequence of RedirectExit rules.
16093 - Clients now generate a TLS cert too, in preparation for having
16094 them act more like real nodes.
16095 - Ship src/win32/ in the tarball, so people can use it to build.
16096 - Make old win32 fall back to CWD if SHGetSpecialFolderLocation
16098 - New "router-status" line in directory, to better bind each verified
16099 nickname to its identity key.
16100 - Deprecate unofficial config option abbreviations, and abbreviations
16101 not on the command line.
16102 - Add a pure-C tor-resolve implementation.
16103 - Use getrlimit and friends to ensure we can reach MaxConn (currently
16104 1024) file descriptors.
16106 o Code security improvements, inspired by Ilja:
16107 - Replace sprintf with snprintf. (I think they were all safe, but
16109 - Replace strcpy/strncpy with strlcpy in more places.
16110 - Avoid strcat; use snprintf or strlcat instead.
16111 - snprintf wrapper with consistent (though not C99) overflow behavior.
16114 Changes in version 0.0.9pre4 - 2004-10-17
16115 o Bugfixes on 0.0.9pre3:
16116 - If the server doesn't specify an exit policy, use the real default
16117 exit policy, not reject *:*.
16118 - Ignore fascistfirewall when uploading/downloading hidden service
16119 descriptors, since we go through Tor for those; and when using
16120 an HttpProxy, since we assume it can reach them all.
16121 - When looking for an authoritative dirserver, use only the ones
16122 configured at boot. Don't bother looking in the directory.
16123 - The rest of the fix for get_default_conf_file() on older win32.
16124 - Make 'Routerfile' config option obsolete.
16127 - New 'MyFamily nick1,...' config option for a server to
16128 specify other servers that shouldn't be used in the same circuit
16129 with it. Only believed if nick1 also specifies us.
16130 - New 'NodeFamily nick1,nick2,...' config option for a client to
16131 specify nodes that it doesn't want to use in the same circuit.
16132 - New 'Redirectexit pattern address:port' config option for a
16133 server to redirect exit connections, e.g. to a local squid.
16136 Changes in version 0.0.9pre3 - 2004-10-13
16137 o Bugfixes on 0.0.8.1:
16138 - Better torrc example lines for dirbindaddress and orbindaddress.
16139 - Improved bounds checking on parsed ints (e.g. config options and
16140 the ones we find in directories.)
16141 - Better handling of size_t vs int, so we're more robust on 64
16143 - Fix the rest of the bug where a newly started OR would appear
16144 as unverified even after we've added his fingerprint and hupped
16146 - Fix a bug from 0.0.7: when read() failed on a stream, we would
16147 close it without sending back an end. So 'connection refused'
16148 would simply be ignored and the user would get no response.
16150 o Bugfixes on 0.0.9pre2:
16151 - Serving the cached-on-disk directory to people is bad. We now
16152 provide no directory until we've fetched a fresh one.
16153 - Workaround for bug on windows where cached-directories get crlf
16155 - Make get_default_conf_file() work on older windows too.
16156 - If we write a *:* exit policy line in the descriptor, don't write
16157 any more exit policy lines.
16160 - Use only 0.0.9pre1 and later servers for resolve cells.
16161 - Make the dirservers file obsolete.
16162 - Include a dir-signing-key token in directories to tell the
16163 parsing entity which key is being used to sign.
16164 - Remove the built-in bulky default dirservers string.
16165 - New config option "Dirserver %s:%d [fingerprint]", which can be
16166 repeated as many times as needed. If no dirservers specified,
16167 default to moria1,moria2,tor26.
16168 - Make moria2 advertise a dirport of 80, so people behind firewalls
16169 will be able to get a directory.
16170 - Http proxy support
16171 - Dirservers translate requests for http://%s:%d/x to /x
16172 - You can specify "HttpProxy %s[:%d]" and all dir fetches will
16173 be routed through this host.
16174 - Clients ask for /tor/x rather than /x for new enough dirservers.
16175 This way we can one day coexist peacefully with apache.
16176 - Clients specify a "Host: %s%d" http header, to be compatible
16177 with more proxies, and so running squid on an exit node can work.
16180 Changes in version 0.0.8.1 - 2004-10-13
16182 - Fix a seg fault that can be triggered remotely for Tor
16183 clients/servers with an open dirport.
16184 - Fix a rare assert trigger, where routerinfos for entries in
16185 our cpath would expire while we're building the path.
16186 - Fix a bug in OutboundBindAddress so it (hopefully) works.
16187 - Fix a rare seg fault for people running hidden services on
16188 intermittent connections.
16189 - Fix a bug in parsing opt keywords with objects.
16190 - Fix a stale pointer assert bug when a stream detaches and
16192 - Fix a string format vulnerability (probably not exploitable)
16193 in reporting stats locally.
16194 - Fix an assert trigger: sometimes launching circuits can fail
16195 immediately, e.g. because too many circuits have failed recently.
16196 - Fix a compile warning on 64 bit platforms.
16199 Changes in version 0.0.9pre2 - 2004-10-03
16201 - Make fetching a cached directory work for 64-bit platforms too.
16202 - Make zlib.h a required header, not an optional header.
16205 Changes in version 0.0.9pre1 - 2004-10-01
16207 - Stop using separate defaults for no-config-file and
16208 empty-config-file. Now you have to explicitly turn off SocksPort,
16209 if you don't want it open.
16210 - Fix a bug in OutboundBindAddress so it (hopefully) works.
16211 - Improve man page to mention more of the 0.0.8 features.
16212 - Fix a rare seg fault for people running hidden services on
16213 intermittent connections.
16214 - Change our file IO stuff (especially wrt OpenSSL) so win32 is
16216 - Fix more dns related bugs: send back resolve_failed and end cells
16217 more reliably when the resolve fails, rather than closing the
16218 circuit and then trying to send the cell. Also attach dummy resolve
16219 connections to a circuit *before* calling dns_resolve(), to fix
16220 a bug where cached answers would never be sent in RESOLVED cells.
16221 - When we run out of disk space, or other log writing error, don't
16222 crash. Just stop logging to that log and continue.
16223 - We were starting to daemonize before we opened our logs, so if
16224 there were any problems opening logs, we would complain to stderr,
16225 which wouldn't work, and then mysteriously exit.
16226 - Fix a rare bug where sometimes a verified OR would connect to us
16227 before he'd uploaded his descriptor, which would cause us to
16228 assign conn->nickname as though he's unverified. Now we look through
16229 the fingerprint list to see if he's there.
16230 - Fix a rare assert trigger, where routerinfos for entries in
16231 our cpath would expire while we're building the path.
16234 - Clients can ask dirservers for /dir.z to get a compressed version
16235 of the directory. Only works for servers running 0.0.9, of course.
16236 - Make clients cache directories and use them to seed their router
16237 lists at startup. This means clients have a datadir again.
16238 - Configuration infrastructure support for warning on obsolete
16240 - Respond to content-encoding headers by trying to uncompress as
16242 - Reply with a deflated directory when a client asks for "dir.z".
16243 We could use allow-encodings instead, but allow-encodings isn't
16244 specified in HTTP 1.0.
16245 - Raise the max dns workers from 50 to 100.
16246 - Discourage people from setting their dirfetchpostperiod more often
16247 than once per minute.
16248 - Protect dirservers from overzealous descriptor uploading -- wait
16249 10 seconds after directory gets dirty, before regenerating.
16252 Changes in version 0.0.8 - 2004-08-25
16253 o Port it to SunOS 5.9 / Athena
16256 Changes in version 0.0.8rc2 - 2004-08-20
16257 o Make it compile on cygwin again.
16258 o When picking unverified routers, skip those with low uptime and/or
16259 low bandwidth, depending on what properties you care about.
16262 Changes in version 0.0.8rc1 - 2004-08-18
16263 o Changes from 0.0.7.3:
16265 - Fix assert triggers: if the other side returns an address 0.0.0.0,
16266 don't put it into the client dns cache.
16267 - If a begin failed due to exit policy, but we believe the IP address
16268 should have been allowed, switch that router to exitpolicy reject *:*
16269 until we get our next directory.
16271 - Clients choose nodes proportional to advertised bandwidth.
16272 - Avoid using nodes with low uptime as introduction points.
16273 - Handle servers with dynamic IP addresses: don't replace
16274 options->Address with the resolved one at startup, and
16275 detect our address right before we make a routerinfo each time.
16276 - 'FascistFirewall' option to pick dirservers and ORs on specific
16277 ports; plus 'FirewallPorts' config option to tell FascistFirewall
16278 which ports are open. (Defaults to 80,443)
16279 - Be more aggressive about trying to make circuits when the network
16280 has changed (e.g. when you unsuspend your laptop).
16281 - Check for time skew on http headers; report date in response to
16283 - If the entrynode config line has only one node, don't pick it as
16285 - Add strict{entry|exit}nodes config options. If set to 1, then
16286 we refuse to build circuits that don't include the specified entry
16288 - OutboundBindAddress config option, to bind to a specific
16289 IP address for outgoing connect()s.
16290 - End truncated log entries (e.g. directories) with "[truncated]".
16292 o Patches to 0.0.8preX:
16294 - Patches to compile and run on win32 again (maybe)?
16295 - Fix crash when looking for ~/.torrc with no $HOME set.
16296 - Fix a race bug in the unit tests.
16297 - Handle verified/unverified name collisions better when new
16298 routerinfo's arrive in a directory.
16299 - Sometimes routers were getting entered into the stats before
16300 we'd assigned their identity_digest. Oops.
16301 - Only pick and establish intro points after we've gotten a
16304 - AllowUnverifiedNodes config option to let circuits choose no-name
16305 routers in entry,middle,exit,introduction,rendezvous positions.
16306 Allow middle and rendezvous positions by default.
16307 - Add a man page for tor-resolve.
16310 Changes in version 0.0.7.3 - 2004-08-12
16311 o Stop dnsworkers from triggering an assert failure when you
16312 ask them to resolve the host "".
16315 Changes in version 0.0.8pre3 - 2004-08-09
16316 o Changes from 0.0.7.2:
16317 - Allow multiple ORs with same nickname in routerlist -- now when
16318 people give us one identity key for a nickname, then later
16319 another, we don't constantly complain until the first expires.
16320 - Remember used bandwidth (both in and out), and publish 15-minute
16321 snapshots for the past day into our descriptor.
16322 - You can now fetch $DIRURL/running-routers to get just the
16323 running-routers line, not the whole descriptor list. (But
16324 clients don't use this yet.)
16325 - When people mistakenly use Tor as an http proxy, point them
16326 at the tor-doc.html rather than the INSTALL.
16327 - Remove our mostly unused -- and broken -- hex_encode()
16328 function. Use base16_encode() instead. (Thanks to Timo Lindfors
16329 for pointing out this bug.)
16330 - Rotate onion keys every 12 hours, not every 2 hours, so we have
16331 fewer problems with people using the wrong key.
16332 - Change the default exit policy to reject the default edonkey,
16333 kazaa, gnutella ports.
16334 - Add replace_file() to util.[ch] to handle win32's rename().
16336 o Changes from 0.0.8preX:
16337 - Fix two bugs in saving onion keys to disk when rotating, so
16338 hopefully we'll get fewer people using old onion keys.
16339 - Fix an assert error that was making SocksPolicy not work.
16340 - Be willing to expire routers that have an open dirport -- it's
16341 just the authoritative dirservers we want to not forget.
16342 - Reject tor-resolve requests for .onion addresses early, so we
16343 don't build a whole rendezvous circuit and then fail.
16344 - When you're warning a server that he's unverified, don't cry
16345 wolf unpredictably.
16346 - Fix a race condition: don't try to extend onto a connection
16347 that's still handshaking.
16348 - For servers in clique mode, require the conn to be open before
16349 you'll choose it for your path.
16350 - Fix some cosmetic bugs about duplicate mark-for-close, lack of
16351 end relay cell, etc.
16352 - Measure bandwidth capacity over the last 24 hours, not just 12
16353 - Bugfix: authoritative dirservers were making and signing a new
16354 directory for each client, rather than reusing the cached one.
16357 Changes in version 0.0.8pre2 - 2004-08-04
16358 o Changes from 0.0.7.2:
16360 - Check directory signature _before_ you decide whether you're
16361 you're running an obsolete version and should exit.
16362 - Check directory signature _before_ you parse the running-routers
16363 list to decide who's running or verified.
16364 - Bugfixes and features:
16365 - Check return value of fclose while writing to disk, so we don't
16366 end up with broken files when servers run out of disk space.
16367 - Log a warning if the user uses an unsafe socks variant, so people
16368 are more likely to learn about privoxy or socat.
16369 - Dirservers now include RFC1123-style dates in the HTTP headers,
16370 which one day we will use to better detect clock skew.
16372 o Changes from 0.0.8pre1:
16373 - Make it compile without warnings again on win32.
16374 - Log a warning if you're running an unverified server, to let you
16375 know you might want to get it verified.
16376 - Only pick a default nickname if you plan to be a server.
16379 Changes in version 0.0.8pre1 - 2004-07-23
16381 - Made our unit tests compile again on OpenBSD 3.5, and tor
16382 itself compile again on OpenBSD on a sparc64.
16383 - We were neglecting milliseconds when logging on win32, so
16384 everything appeared to happen at the beginning of each second.
16386 o Protocol changes:
16387 - 'Extend' relay cell payloads now include the digest of the
16388 intended next hop's identity key. Now we can verify that we're
16389 extending to the right router, and also extend to routers we
16390 hadn't heard of before.
16393 - Tor nodes can now act as relays (with an advertised ORPort)
16394 without being manually verified by the dirserver operators.
16395 - Uploaded descriptors of unverified routers are now accepted
16396 by the dirservers, and included in the directory.
16397 - Verified routers are listed by nickname in the running-routers
16398 list; unverified routers are listed as "$<fingerprint>".
16399 - We now use hash-of-identity-key in most places rather than
16400 nickname or addr:port, for improved security/flexibility.
16401 - To avoid Sybil attacks, paths still use only verified servers.
16402 But now we have a chance to play around with hybrid approaches.
16403 - Nodes track bandwidth usage to estimate capacity (not used yet).
16404 - ClientOnly option for nodes that never want to become servers.
16405 - Directory caching.
16406 - "AuthoritativeDir 1" option for the official dirservers.
16407 - Now other nodes (clients and servers) will cache the latest
16408 directory they've pulled down.
16409 - They can enable their DirPort to serve it to others.
16410 - Clients will pull down a directory from any node with an open
16411 DirPort, and check the signature/timestamp correctly.
16412 - Authoritative dirservers now fetch directories from other
16413 authdirservers, to stay better synced.
16414 - Running-routers list tells who's down also, along with noting
16415 if they're verified (listed by nickname) or unverified (listed
16417 - Allow dirservers to serve running-router list separately.
16418 This isn't used yet.
16419 - ORs connect-on-demand to other ORs
16420 - If you get an extend cell to an OR you're not connected to,
16421 connect, handshake, and forward the create cell.
16422 - The authoritative dirservers stay connected to everybody,
16423 and everybody stays connected to 0.0.7 servers, but otherwise
16424 clients/servers expire unused connections after 5 minutes.
16425 - When servers get a sigint, they delay 30 seconds (refusing new
16426 connections) then exit. A second sigint causes immediate exit.
16427 - File and name management:
16428 - Look for .torrc if no CONFDIR "torrc" is found.
16429 - If no datadir is defined, then choose, make, and secure ~/.tor
16431 - If torrc not found, exitpolicy reject *:*.
16432 - Expands ~/ in filenames to $HOME/ (but doesn't yet expand ~arma).
16433 - If no nickname is defined, derive default from hostname.
16434 - Rename secret key files, e.g. identity.key -> secret_id_key,
16435 to discourage people from mailing their identity key to tor-ops.
16436 - Refuse to build a circuit before the directory has arrived --
16437 it won't work anyway, since you won't know the right onion keys
16439 - Try other dirservers immediately if the one you try is down. This
16440 should tolerate down dirservers better now.
16441 - Parse tor version numbers so we can do an is-newer-than check
16442 rather than an is-in-the-list check.
16443 - New socks command 'resolve', to let us shim gethostbyname()
16445 - A 'tor_resolve' script to access the socks resolve functionality.
16446 - A new socks-extensions.txt doc file to describe our
16447 interpretation and extensions to the socks protocols.
16448 - Add a ContactInfo option, which gets published in descriptor.
16449 - Publish OR uptime in descriptor (and thus in directory) too.
16450 - Write tor version at the top of each log file
16451 - New docs in the tarball:
16453 - Document that you should proxy your SSL traffic too.
16456 Changes in version 0.0.7.2 - 2004-07-07
16457 o A better fix for the 0.0.0.0 problem, that will hopefully
16458 eliminate the remaining related assertion failures.
16461 Changes in version 0.0.7.1 - 2004-07-04
16462 o When an address resolves to 0.0.0.0, treat it as a failed resolve,
16463 since internally we use 0.0.0.0 to signify "not yet resolved".
16466 Changes in version 0.0.7 - 2004-06-07
16467 o Updated the man page to reflect the new features.
16470 Changes in version 0.0.7rc2 - 2004-06-06
16471 o Changes from 0.0.7rc1:
16472 - Make it build on Win32 again.
16473 o Changes from 0.0.6.2:
16474 - Rotate dnsworkers and cpuworkers on SIGHUP, so they get new config
16478 Changes in version 0.0.7rc1 - 2004-06-02
16480 - On sighup, we were adding another log without removing the first
16481 one. So log messages would get duplicated n times for n sighups.
16482 - Several cases of using a connection after we'd freed it. The
16483 problem was that connections that are pending resolve are in both
16484 the pending_resolve tree, and also the circuit's resolving_streams
16485 list. When you want to remove one, you must remove it from both.
16486 - Fix a double-mark-for-close where an end cell arrived for a
16487 resolving stream, and then the resolve failed.
16488 - Check directory signatures based on name of signer, not on whom
16489 we got the directory from. This will let us cache directories more
16492 - Crank up some of our constants to handle more users.
16495 Changes in version 0.0.7pre1 - 2004-06-02
16496 o Fixes for crashes and other obnoxious bugs:
16497 - Fix an epipe bug: sometimes when directory connections failed
16498 to connect, we would give them a chance to flush before closing
16500 - When we detached from a circuit because of resolvefailed, we
16501 would immediately try the same circuit twice more, and then
16502 give up on the resolve thinking we'd tried three different
16504 - Limit the number of intro circuits we'll attempt to build for a
16505 hidden service per 15-minute period.
16506 - Check recommended-software string *early*, before actually parsing
16507 the directory. Thus we can detect an obsolete version and exit,
16508 even if the new directory format doesn't parse.
16509 o Fixes for security bugs:
16510 - Remember which nodes are dirservers when you startup, and if a
16511 random OR enables his dirport, don't automatically assume he's
16512 a trusted dirserver.
16514 - Directory connections were asking the wrong poll socket to
16515 start writing, and not asking themselves to start writing.
16516 - When we detached from a circuit because we sent a begin but
16517 didn't get a connected, we would use it again the first time;
16518 but after that we would correctly switch to a different one.
16519 - Stop warning when the first onion decrypt attempt fails; they
16520 will sometimes legitimately fail now that we rotate keys.
16521 - Override unaligned-access-ok check when $host_cpu is ia64 or
16522 arm. Apparently they allow it but the kernel whines.
16523 - Dirservers try to reconnect periodically too, in case connections
16525 - Fix some memory leaks in directory servers.
16526 - Allow backslash in Win32 filenames.
16527 - Made Tor build complain-free on FreeBSD, hopefully without
16528 breaking other BSD builds. We'll see.
16530 - Doxygen markup on all functions and global variables.
16531 - Make directory functions update routerlist, not replace it. So
16532 now directory disagreements are not so critical a problem.
16533 - Remove the upper limit on number of descriptors in a dirserver's
16534 directory (not that we were anywhere close).
16535 - Allow multiple logfiles at different severity ranges.
16536 - Allow *BindAddress to specify ":port" rather than setting *Port
16537 separately. Allow multiple instances of each BindAddress config
16538 option, so you can bind to multiple interfaces if you want.
16539 - Allow multiple exit policy lines, which are processed in order.
16540 Now we don't need that huge line with all the commas in it.
16541 - Enable accept/reject policies on SOCKS connections, so you can bind
16542 to 0.0.0.0 but still control who can use your OP.
16545 Changes in version 0.0.6.2 - 2004-05-16
16546 o Our integrity-checking digest was checking only the most recent cell,
16547 not the previous cells like we'd thought.
16548 Thanks to Stefan Mark for finding the flaw!
16551 Changes in version 0.0.6.1 - 2004-05-06
16552 o Fix two bugs in our AES counter-mode implementation (this affected
16553 onion-level stream encryption, but not TLS-level). It turns
16554 out we were doing something much more akin to a 16-character
16555 polyalphabetic cipher. Oops.
16556 Thanks to Stefan Mark for finding the flaw!
16557 o Retire moria3 as a directory server, and add tor26 as a directory
16561 Changes in version 0.0.6 - 2004-05-02
16562 [version bump only]
16565 Changes in version 0.0.6rc4 - 2004-05-01
16566 o Update the built-in dirservers list to use the new directory format
16567 o Fix a rare seg fault: if a node offering a hidden service attempts
16568 to build a circuit to Alice's rendezvous point and fails before it
16569 reaches the last hop, it retries with a different circuit, but
16571 o Handle windows socket errors correctly.
16574 Changes in version 0.0.6rc3 - 2004-04-28
16575 o Don't expire non-general excess circuits (if we had enough
16576 circuits open, we were expiring rendezvous circuits -- even
16577 when they had a stream attached. oops.)
16578 o Fetch randomness from /dev/urandom better (not via fopen/fread)
16579 o Better debugging for tls errors
16580 o Some versions of openssl have an SSL_pending function that erroneously
16581 returns bytes when there is a non-application record pending.
16582 o Set Content-Type on the directory and hidserv descriptor.
16583 o Remove IVs from cipher code, since AES-ctr has none.
16584 o Win32 fixes. Tor now compiles on win32 with no warnings/errors.
16585 o We were using an array of length zero in a few places.
16586 o win32's gethostbyname can't resolve an IP to an IP.
16587 o win32's close can't close a socket.
16590 Changes in version 0.0.6rc2 - 2004-04-26
16591 o Fix a bug where we were closing tls connections intermittently.
16592 It turns out openssl keeps its errors around -- so if an error
16593 happens, and you don't ask about it, and then another openssl
16594 operation happens and succeeds, and you ask if there was an error,
16595 it tells you about the first error. Fun fun.
16596 o Fix a bug that's been lurking since 27 may 03 (!)
16597 When passing back a destroy cell, we would use the wrong circ id.
16598 'Mostly harmless', but still worth fixing.
16599 o Since we don't support truncateds much, don't bother sending them;
16600 just close the circ.
16601 o check for <machine/limits.h> so we build on NetBSD again (I hope).
16602 o don't crash if a conn that sent a begin has suddenly lost its circuit
16603 (this was quite rare).
16606 Changes in version 0.0.6rc1 - 2004-04-25
16607 o We now rotate link (tls context) keys and onion keys.
16608 o CREATE cells now include oaep padding, so you can tell
16609 if you decrypted them correctly.
16610 o Add bandwidthburst to server descriptor.
16611 o Directories now say which dirserver signed them.
16612 o Use a tor_assert macro that logs failed assertions too.
16615 Changes in version 0.0.6pre5 - 2004-04-18
16616 o changes from 0.0.6pre4:
16617 - make tor build on broken freebsd 5.2 installs
16618 - fix a failed assert when you try an intro point, get a nack, and try
16619 a second one and it works.
16620 - when alice uses a port that the hidden service doesn't accept,
16621 it now sends back an end cell (denied by exit policy). otherwise
16622 alice would just have to wait to time out.
16623 - fix another rare bug: when we had tried all the intro
16624 points for a hidden service, we fetched the descriptor
16625 again, but we left our introcirc thinking it had already
16626 sent an intro, so it kept waiting for a response...
16627 - bugfix: when you sleep your hidden-service laptop, as soon
16628 as it wakes up it tries to upload a service descriptor, but
16629 socketpair fails for some reason (localhost not up yet?).
16630 now we simply give up on that upload, and we'll try again later.
16631 i'd still like to find the bug though.
16632 - if an intro circ waiting for an ack dies before getting one, then
16634 - we were reusing stale service descriptors and refetching usable
16638 Changes in version 0.0.6pre4 - 2004-04-14
16639 o changes from 0.0.6pre3:
16640 - when bob fails to connect to the rendezvous point, and his
16641 circ didn't fail because of the rendezvous point itself, then
16642 he retries a couple of times
16643 - we expire introduction and rendezvous circs more thoroughly
16644 (sometimes they were hanging around forever)
16645 - we expire unattached rendezvous streams that have been around
16646 too long (they were sticking around forever).
16647 - fix a measly fencepost error that was crashing everybody with
16651 Changes in version 0.0.6pre3 - 2004-04-14
16652 o changes from 0.0.6pre2:
16653 - make hup work again
16654 - fix some memory leaks for dirservers
16655 - allow more skew in rendezvous descriptor timestamps, to help
16656 handle people like blanu who don't know what time it is
16657 - normal circs are 3 hops, but some rend/intro circs are 4, if
16658 the initiator doesn't get to choose the last hop
16659 - send acks for introductions, so alice can know whether to try
16661 - bob publishes intro points more correctly
16662 o changes from 0.0.5:
16663 - fix an assert trigger that's been plaguing us since the days
16664 of 0.0.2prexx (thanks weasel!)
16665 - retry stream correctly when we fail to connect because of
16666 exit-policy-reject (should try another) or can't-resolve-address
16667 (also should try another, because dns on random internet servers
16669 - when we hup a dirserver and we've *removed* a server from the
16670 approved-routers list, now we remove that server from the
16671 in-memory directories too
16674 Changes in version 0.0.6pre2 - 2004-04-08
16675 o We fixed our base32 implementation. Now it works on all architectures.
16678 Changes in version 0.0.6pre1 - 2004-04-08
16680 - Hidden services and rendezvous points are implemented. Go to
16681 http://6sxoyfb3h2nvok2d.onion/ for an index of currently available
16682 hidden services. (This only works via a socks4a proxy such as
16683 Privoxy, and currently it's quite slow.)
16686 Changes in version 0.0.5 - 2004-03-30
16687 [version bump only]
16690 Changes in version 0.0.5rc3 - 2004-03-29
16691 o Install torrc as torrc.sample -- we no longer clobber your
16693 o Re-enable recommendedversion checking (we broke it in rc2, oops)
16694 o Add in a 'notice' log level for things the operator should hear
16695 but that aren't warnings
16698 Changes in version 0.0.5rc2 - 2004-03-29
16699 o Hold socks connection open until reply is flushed (if possible)
16700 o Make exit nodes resolve IPs to IPs immediately, rather than asking
16701 the dns farm to do it.
16702 o Fix c99 aliasing warnings in rephist.c
16703 o Don't include server descriptors that are older than 24 hours in the
16705 o Give socks 'reject' replies their whole 15s to attempt to flush,
16706 rather than seeing the 60s timeout and assuming the flush had failed.
16707 o Clean automake droppings from the cvs repository
16710 Changes in version 0.0.5rc1 - 2004-03-28
16711 o Fix mangled-state bug in directory fetching (was causing sigpipes).
16712 o Only build circuits after we've fetched the directory: clients were
16713 using only the directory servers before they'd fetched a directory.
16714 This also means longer startup time; so it goes.
16715 o Fix an assert trigger where an OP would fail to handshake, and we'd
16716 expect it to have a nickname.
16717 o Work around a tsocks bug: do a socks reject when AP connection dies
16718 early, else tsocks goes into an infinite loop.
16721 Changes in version 0.0.4 - 2004-03-26
16722 o When connecting to a dirserver or OR and the network is down,
16726 Changes in version 0.0.3 - 2004-03-26
16727 o Warn and fail if server chose a nickname with illegal characters
16728 o Port to Solaris and Sparc:
16729 - include missing header fcntl.h
16730 - have autoconf find -lsocket -lnsl automatically
16731 - deal with hardware word alignment
16732 - make uname() work (solaris has a different return convention)
16733 - switch from using signal() to sigaction()
16734 o Preliminary work on reputation system:
16735 - Keep statistics on success/fail of connect attempts; they're published
16736 by kill -USR1 currently.
16737 - Add a RunTesting option to try to learn link state by creating test
16738 circuits, even when SocksPort is off.
16739 - Remove unused open circuits when there are too many.
16742 Changes in version 0.0.2 - 2004-03-19
16743 - Include strlcpy and strlcat for safer string ops
16744 - define INADDR_NONE so we compile (but still not run) on solaris
16747 Changes in version 0.0.2pre27 - 2004-03-14
16749 - Allow internal tor networks (we were rejecting internal IPs,
16750 now we allow them if they're set explicitly).
16751 - And fix a few endian issues.
16754 Changes in version 0.0.2pre26 - 2004-03-14
16756 - If a stream times out after 15s without a connected cell, don't
16757 try that circuit again: try a new one.
16758 - Retry streams at most 4 times. Then give up.
16759 - When a dirserver gets a descriptor from an unknown router, it
16760 logs its fingerprint (so the dirserver operator can choose to
16761 accept it even without mail from the server operator).
16762 - Inform unapproved servers when we reject their descriptors.
16763 - Make tor build on Windows again. It works as a client, who knows
16765 - Clearer instructions in the torrc for how to set up a server.
16766 - Be more efficient about reading fd's when our global token bucket
16767 (used for rate limiting) becomes empty.
16769 - Stop asserting that computers always go forward in time. It's
16771 - When we sent a cell (e.g. destroy) and then marked an OR connection
16772 expired, we might close it before finishing a flush if the other
16773 side isn't reading right then.
16774 - Don't allow dirservers to start if they haven't defined
16775 RecommendedVersions
16776 - We were caching transient dns failures. Oops.
16777 - Prevent servers from publishing an internal IP as their address.
16778 - Address a strcat vulnerability in circuit.c
16781 Changes in version 0.0.2pre25 - 2004-03-04
16783 - Put the OR's IP in its router descriptor, not its fqdn. That way
16784 we'll stop being stalled by gethostbyname for nodes with flaky dns,
16787 - If the user typed in an address that didn't resolve, the server
16791 Changes in version 0.0.2pre24 - 2004-03-03
16793 - Fix an assertion failure in dns.c, where we were trying to dequeue
16794 a pending dns resolve even if it wasn't pending
16795 - Fix a spurious socks5 warning about still trying to write after the
16796 connection is finished.
16797 - Hold certain marked_for_close connections open until they're finished
16798 flushing, rather than losing bytes by closing them too early.
16799 - Correctly report the reason for ending a stream
16800 - Remove some duplicate calls to connection_mark_for_close
16801 - Put switch_id and start_daemon earlier in the boot sequence, so it
16802 will actually try to chdir() to options.DataDirectory
16803 - Make 'make test' exit(1) if a test fails; fix some unit tests
16804 - Make tor fail when you use a config option it doesn't know about,
16805 rather than warn and continue.
16806 - Make --version work
16807 - Bugfixes on the rpm spec file and tor.sh, so it's more up to date
16810 Changes in version 0.0.2pre23 - 2004-02-29
16812 - Print a statement when the first circ is finished, so the user
16813 knows it's working.
16814 - If a relay cell is unrecognized at the end of the circuit,
16815 send back a destroy. (So attacks to mutate cells are more
16817 - New config option 'excludenodes' to avoid certain nodes for circuits.
16818 - When it daemonizes, it chdir's to the DataDirectory rather than "/",
16819 so you can collect coredumps there.
16821 - Fix a bug in tls flushing where sometimes data got wedged and
16822 didn't flush until more data got sent. Hopefully this bug was
16823 a big factor in the random delays we were seeing.
16824 - Make 'connected' cells include the resolved IP, so the client
16825 dns cache actually gets populated.
16826 - Disallow changing from ORPort=0 to ORPort>0 on hup.
16827 - When we time-out on a stream and detach from the circuit, send an
16828 end cell down it first.
16829 - Only warn about an unknown router (in exitnodes, entrynodes,
16830 excludenodes) after we've fetched a directory.
16833 Changes in version 0.0.2pre22 - 2004-02-26
16835 - Servers publish less revealing uname information in descriptors.
16836 - More memory tracking and assertions, to crash more usefully when
16838 - If the default torrc isn't there, just use some default defaults.
16839 Plus provide an internal dirservers file if they don't have one.
16840 - When the user tries to use Tor as an http proxy, give them an http
16841 501 failure explaining that we're a socks proxy.
16842 - Dump a new router.desc on hup, to help confused people who change
16843 their exit policies and then wonder why router.desc doesn't reflect
16845 - Clean up the generic tor.sh init script that we ship with.
16847 - If the exit stream is pending on the resolve, and a destroy arrives,
16848 then the stream wasn't getting removed from the pending list. I
16849 think this was the one causing recent server crashes.
16850 - Use a more robust poll on OSX 10.3, since their poll is flaky.
16851 - When it couldn't resolve any dirservers, it was useless from then on.
16852 Now it reloads the RouterFile (or default dirservers) if it has no
16854 - Move the 'tor' binary back to /usr/local/bin/ -- it turns out
16855 many users don't even *have* a /usr/local/sbin/.
16858 Changes in version 0.0.2pre21 - 2004-02-18
16860 - There's a ChangeLog file that actually reflects the changelog.
16861 - There's a 'torify' wrapper script, with an accompanying
16862 tor-tsocks.conf, that simplifies the process of using tsocks for
16863 tor. It even has a man page.
16864 - The tor binary gets installed to sbin rather than bin now.
16865 - Retry streams where the connected cell hasn't arrived in 15 seconds
16866 - Clean up exit policy handling -- get the default out of the torrc,
16867 so we can update it without forcing each server operator to fix
16869 - Allow imaps and pop3s in default exit policy
16871 - Prevent picking middleman nodes as the last node in the circuit
16874 Changes in version 0.0.2pre20 - 2004-01-30
16876 - We now have a deb package, and it's in debian unstable. Go to
16877 it, apt-getters. :)
16878 - I've split the TotalBandwidth option into BandwidthRate (how many
16879 bytes per second you want to allow, long-term) and
16880 BandwidthBurst (how many bytes you will allow at once before the cap
16881 kicks in). This better token bucket approach lets you, say, set
16882 BandwidthRate to 10KB/s and BandwidthBurst to 10MB, allowing good
16883 performance while not exceeding your monthly bandwidth quota.
16884 - Push out a tls record's worth of data once you've got it, rather
16885 than waiting until you've read everything waiting to be read. This
16886 may improve performance by pipelining better. We'll see.
16887 - Add an AP_CONN_STATE_CONNECTING state, to allow streams to detach
16888 from failed circuits (if they haven't been connected yet) and attach
16890 - Expire old streams that haven't managed to connect. Some day we'll
16891 have them reattach to new circuits instead.
16894 - Fix several memory leaks that were causing servers to become bloated
16896 - Fix a few very rare assert triggers. A few more remain.
16897 - Setuid to User _before_ complaining about running as root.
16900 Changes in version 0.0.2pre19 - 2004-01-07
16902 - Fix deadlock condition in dns farm. We were telling a child to die by
16903 closing the parent's file descriptor to him. But newer children were
16904 inheriting the open file descriptor from the parent, and since they
16905 weren't closing it, the socket never closed, so the child never read
16906 eof, so he never knew to exit. Similarly, dns workers were holding
16907 open other sockets, leading to all sorts of chaos.
16908 - New cleaner daemon() code for forking and backgrounding.
16909 - If you log to a file, it now prints an entry at the top of the
16910 logfile so you know it's working.
16911 - The onionskin challenge length was 30 bytes longer than necessary.
16912 - Started to patch up the spec so it's not quite so out of date.
16915 Changes in version 0.0.2pre18 - 2004-01-02
16917 - Fix endian issues with the 'integrity' field in the relay header.
16918 - Fix a potential bug where connections in state
16919 AP_CONN_STATE_CIRCUIT_WAIT might unexpectedly ask to write.
16922 Changes in version 0.0.2pre17 - 2003-12-30
16924 - Made --debuglogfile (or any second log file, actually) work.
16925 - Resolved an edge case in get_unique_circ_id_by_conn where a smart
16926 adversary could force us into an infinite loop.
16929 - Each onionskin handshake now includes a hash of the computed key,
16930 to prove the server's identity and help perfect forward secrecy.
16931 - Changed cell size from 256 to 512 bytes (working toward compatibility
16933 - Changed cell length to 2 bytes, and moved it to the relay header.
16934 - Implemented end-to-end integrity checking for the payloads of
16936 - Separated streamid from 'recognized' (otherwise circuits will get
16937 messed up when we try to have streams exit from the middle). We
16938 use the integrity-checking to confirm that a cell is addressed to
16940 - Randomize the initial circid and streamid values, so an adversary who
16941 breaks into a node can't learn how many circuits or streams have
16945 Changes in version 0.0.2pre16 - 2003-12-14
16947 - Fixed a bug that made HUP trigger an assert
16948 - Fixed a bug where a circuit that immediately failed wasn't being
16949 counted as a failed circuit in counting retries.
16952 - Now we close the circuit when we get a truncated cell: otherwise we're
16953 open to an anonymity attack where a bad node in the path truncates
16954 the circuit and then we open streams at him.
16955 - Add port ranges to exit policies
16956 - Add a conservative default exit policy
16957 - Warn if you're running tor as root
16958 - on HUP, retry OR connections and close/rebind listeners
16959 - options.EntryNodes: try these nodes first when picking the first node
16960 - options.ExitNodes: if your best choices happen to include any of
16961 your preferred exit nodes, you choose among just those preferred
16963 - options.ExcludedNodes: nodes that are never picked in path building
16966 Changes in version 0.0.2pre15 - 2003-12-03
16967 o Robustness and bugfixes:
16968 - Sometimes clients would cache incorrect DNS resolves, which would
16969 really screw things up.
16970 - An OP that goes offline would slowly leak all its sockets and stop
16972 - A wide variety of bugfixes in exit node selection, exit policy
16973 handling, and processing pending streams when a new circuit is
16975 - Pick nodes for a path only from those the directory says are up
16976 - Choose randomly from all running dirservers, not always the first one
16977 - Increase allowed http header size for directory fetch.
16978 - Stop writing to stderr (if we're daemonized it will be closed).
16979 - Enable -g always, so cores will be more useful to me.
16980 - Switch "-lcrypto -lssl" to "-lssl -lcrypto" for broken distributions.
16983 - Wrote a man page. It lists commonly used options.
16986 - Change default loglevel to warn.
16987 - Make PidFile default to null rather than littering in your CWD.
16988 - OnionRouter config option is now obsolete. Instead it just checks
16990 - Moved to a single unified torrc file for both clients and servers.
16993 Changes in version 0.0.2pre14 - 2003-11-29
16994 o Robustness and bugfixes:
16995 - Force the admin to make the DataDirectory himself
16996 - to get ownership/permissions right
16997 - so clients no longer make a DataDirectory and then never use it
16998 - fix bug where a client who was offline for 45 minutes would never
16999 pull down a directory again
17000 - fix (or at least hide really well) the dns assert bug that was
17001 causing server crashes
17002 - warnings and improved robustness wrt clockskew for certs
17003 - use the native daemon(3) to daemonize, when available
17004 - exit if bind() fails
17005 - exit if neither socksport nor orport is defined
17006 - include our own tor_timegm (Win32 doesn't have its own)
17007 - bugfix for win32 with lots of connections
17008 - fix minor bias in PRNG
17009 - make dirserver more robust to corrupt cached directory
17012 - Wrote the design document (woo)
17014 o Circuit building and exit policies:
17015 - Circuits no longer try to use nodes that the directory has told them
17017 - Exit policies now support bitmasks (18.0.0.0/255.0.0.0) and
17018 bitcounts (18.0.0.0/8).
17019 - Make AP connections standby for a circuit if no suitable circuit
17020 exists, rather than failing
17021 - Circuits choose exit node based on addr/port, exit policies, and
17022 which AP connections are standing by
17023 - Bump min pathlen from 2 to 3
17024 - Relay end cells have a payload to describe why the stream ended.
17025 - If the stream failed because of exit policy, try again with a new
17027 - Clients have a dns cache to remember resolved addresses.
17028 - Notice more quickly when we have no working circuits
17031 - APPort is now called SocksPort
17032 - SocksBindAddress, ORBindAddress, DirBindAddress let you configure
17034 - RecommendedVersions is now a config variable rather than
17035 hardcoded (for dirservers)
17036 - Reloads config on HUP
17037 - Usage info on -h or --help
17038 - If you set User and Group config vars, it'll setu/gid to them.
17041 Changes in version 0.0.2pre13 - 2003-10-19
17042 o General stability:
17043 - SSL_write no longer fails when it returns WANTWRITE and the number
17044 of bytes in the buf has changed by the next SSL_write call.
17045 - Fix segfault fetching directory when network is down
17046 - Fix a variety of minor memory leaks
17047 - Dirservers reload the fingerprints file on HUP, so I don't have
17048 to take down the network when I approve a new router
17049 - Default server config file has explicit Address line to specify fqdn
17052 - Buffers grow and shrink as needed (Cut process size from 20M to 2M)
17053 - Make listener connections not ever alloc bufs
17055 o Autoconf improvements:
17056 - don't clobber an external CFLAGS in ./configure
17057 - Make install now works
17058 - create var/lib/tor on make install
17059 - autocreate a tor.sh initscript to help distribs
17060 - autocreate the torrc and sample-server-torrc with correct paths
17062 o Log files and Daemonizing now work:
17063 - If --DebugLogFile is specified, log to it at -l debug
17064 - If --LogFile is specified, use it instead of commandline
17065 - If --RunAsDaemon is set, tor forks and backgrounds on startup