1 Changes in version 0.2.6.9 - 2015-06-11
2 Tor 0.2.6.9 fixes a regression in the circuit isolation code, increases the
3 requirements for receiving an HSDir flag, and addresses some other small
4 bugs in the systemd and sandbox code. Clients using circuit isolation
5 should upgrade; all directory authorities should upgrade.
7 o Major bugfixes (client-side privacy):
8 - Properly separate out each SOCKSPort when applying stream
9 isolation. The error occured because each port's session group was
10 being overwritten by a default value when the listener connection
11 was initialized. Fixes bug 16247; bugfix on 0.2.6.3-alpha. Patch
14 o Minor feature (directory authorities, security):
15 - The HSDir flag given by authorities now requires the Stable flag.
16 For the current network, this results in going from 2887 to 2806
17 HSDirs. Also, it makes it harder for an attacker to launch a sybil
18 attack by raising the effort for a relay to become Stable which
19 takes at the very least 7 days to do so and by keeping the 96
20 hours uptime requirement for HSDir. Implements ticket 8243.
22 o Minor bugfixes (compilation):
23 - Build with --enable-systemd correctly when libsystemd is
24 installed, but systemd is not. Fixes bug 16164; bugfix on
25 0.2.6.3-alpha. Patch from Peter Palfrader.
27 o Minor bugfixes (Linux seccomp2 sandbox):
28 - Fix sandboxing to work when running as a relaymby renaming of
29 secret_id_key, and allowing the eventfd2 and futex syscalls. Fixes
30 bug 16244; bugfix on 0.2.6.1-alpha. Patch by Peter Palfrader.
31 - Allow systemd connections to work with the Linux seccomp2 sandbox
32 code. Fixes bug 16212; bugfix on 0.2.6.2-alpha. Patch by
35 o Minor bugfixes (tests):
36 - Fix a crash in the unit tests when built with MSVC2013. Fixes bug
37 16030; bugfix on 0.2.6.2-alpha. Patch from "NewEraCracker".
40 Changes in version 0.2.6.8 - 2015-05-21
41 Tor 0.2.6.8 fixes a bit of dodgy code in parsing INTRODUCE2 cells, and
42 fixes an authority-side bug in assigning the HSDir flag. All directory
43 authorities should upgrade.
45 o Major bugfixes (hidden services, backport from 0.2.7.1-alpha):
46 - Revert commit that made directory authorities assign the HSDir
47 flag to relay without a DirPort; this was bad because such relays
48 can't handle BEGIN_DIR cells. Fixes bug 15850; bugfix
51 o Minor bugfixes (hidden service, backport from 0.2.7.1-alpha):
52 - Fix an out-of-bounds read when parsing invalid INTRODUCE2 cells on
53 a client authorized hidden service. Fixes bug 15823; bugfix
56 o Minor features (geoip):
57 - Update geoip to the April 8 2015 Maxmind GeoLite2 Country database.
58 - Update geoip6 to the April 8 2015 Maxmind GeoLite2
61 Changes in version 0.2.6.7 - 2015-04-06
62 Tor 0.2.6.7 fixes two security issues that could be used by an
63 attacker to crash hidden services, or crash clients visiting hidden
64 services. Hidden services should upgrade as soon as possible; clients
65 should upgrade whenever packages become available.
67 This release also contains two simple improvements to make hidden
68 services a bit less vulnerable to denial-of-service attacks.
70 o Major bugfixes (security, hidden service):
71 - Fix an issue that would allow a malicious client to trigger an
72 assertion failure and halt a hidden service. Fixes bug 15600;
73 bugfix on 0.2.1.6-alpha. Reported by "disgleirio".
74 - Fix a bug that could cause a client to crash with an assertion
75 failure when parsing a malformed hidden service descriptor. Fixes
76 bug 15601; bugfix on 0.2.1.5-alpha. Found by "DonnchaC".
78 o Minor features (DoS-resistance, hidden service):
79 - Introduction points no longer allow multiple INTRODUCE1 cells to
80 arrive on the same circuit. This should make it more expensive for
81 attackers to overwhelm hidden services with introductions.
82 Resolves ticket 15515.
83 - Decrease the amount of reattempts that a hidden service performs
84 when its rendezvous circuits fail. This reduces the computational
85 cost for running a hidden service under heavy load. Resolves
89 Changes in version 0.2.6.6 - 2015-03-24
90 Tor 0.2.6.6 is the first stable release in the 0.2.6 series.
92 It adds numerous safety, security, correctness, and performance
93 improvements. Client programs can be configured to use more kinds of
94 sockets, AutomapHosts works better, the multithreading backend is
95 improved, cell transmission is refactored, test coverage is much
96 higher, more denial-of-service attacks are handled, guard selection is
97 improved to handle long-term guards better, pluggable transports
98 should work a bit better, and some annoying hidden service performance
99 bugs should be addressed.
101 o Minor bugfixes (portability):
102 - Use the correct datatype in the SipHash-2-4 function to prevent
103 compilers from assuming any sort of alignment. Fixes bug 15436;
104 bugfix on 0.2.5.3-alpha.
107 Changes in version 0.2.6.5-rc - 2015-03-18
108 Tor 0.2.6.5-rc is the second and (hopefully) last release candidate in
109 the 0.2.6. It fixes a small number of bugs found in 0.2.6.4-rc.
111 o Major bugfixes (client):
112 - Avoid crashing when making certain configuration option changes on
113 clients. Fixes bug 15245; bugfix on 0.2.6.3-alpha. Reported
116 o Major bugfixes (pluggable transports):
117 - Initialize the extended OR Port authentication cookie before
118 launching pluggable transports. This prevents a race condition
119 that occured when server-side pluggable transports would cache the
120 authentication cookie before it has been (re)generated. Fixes bug
121 15240; bugfix on 0.2.5.1-alpha.
123 o Major bugfixes (portability):
124 - Do not crash on startup when running on Solaris. Fixes a bug
125 related to our fix for 9495; bugfix on 0.2.6.1-alpha. Reported
128 o Minor features (heartbeat):
129 - On relays, report how many connections we negotiated using each
130 version of the Tor link protocols. This information will let us
131 know if removing support for very old versions of the Tor
132 protocols is harming the network. Closes ticket 15212.
134 o Code simplification and refactoring:
135 - Refactor main loop to extract the 'loop' part. This makes it
136 easier to run Tor under Shadow. Closes ticket 15176.
139 Changes in version 0.2.5.11 - 2015-03-17
140 Tor 0.2.5.11 is the second stable release in the 0.2.5 series.
142 It backports several bugfixes from the 0.2.6 branch, including a
143 couple of medium-level security fixes for relays and exit nodes.
144 It also updates the list of directory authorities.
146 o Directory authority changes:
147 - Remove turtles as a directory authority.
148 - Add longclaw as a new (v3) directory authority. This implements
149 ticket 13296. This keeps the directory authority count at 9.
150 - The directory authority Faravahar has a new IP address. This
153 o Major bugfixes (crash, OSX, security):
154 - Fix a remote denial-of-service opportunity caused by a bug in
155 OSX's _strlcat_chk() function. Fixes bug 15205; bug first appeared
158 o Major bugfixes (relay, stability, possible security):
159 - Fix a bug that could lead to a relay crashing with an assertion
160 failure if a buffer of exactly the wrong layout was passed to
161 buf_pullup() at exactly the wrong time. Fixes bug 15083; bugfix on
162 0.2.0.10-alpha. Patch from 'cypherpunks'.
163 - Do not assert if the 'data' pointer on a buffer is advanced to the
164 very end of the buffer; log a BUG message instead. Only assert if
165 it is past that point. Fixes bug 15083; bugfix on 0.2.0.10-alpha.
167 o Major bugfixes (exit node stability):
168 - Fix an assertion failure that could occur under high DNS load.
169 Fixes bug 14129; bugfix on Tor 0.0.7rc1. Found by "jowr";
170 diagnosed and fixed by "cypherpunks".
172 o Major bugfixes (Linux seccomp2 sandbox):
173 - Upon receiving sighup with the seccomp2 sandbox enabled, do not
174 crash during attempts to call wait4. Fixes bug 15088; bugfix on
175 0.2.5.1-alpha. Patch from "sanic".
177 o Minor features (controller):
178 - New "GETINFO bw-event-cache" to get information about recent
179 bandwidth events. Closes ticket 14128. Useful for controllers to
180 get recent bandwidth history after the fix for ticket 13988.
182 o Minor features (geoip):
183 - Update geoip to the March 3 2015 Maxmind GeoLite2 Country database.
184 - Update geoip6 to the March 3 2015 Maxmind GeoLite2
187 o Minor bugfixes (client, automapping):
188 - Avoid crashing on torrc lines for VirtualAddrNetworkIPv[4|6] when
189 no value follows the option. Fixes bug 14142; bugfix on
190 0.2.4.7-alpha. Patch by "teor".
191 - Fix a memory leak when using AutomapHostsOnResolve. Fixes bug
192 14195; bugfix on 0.1.0.1-rc.
194 o Minor bugfixes (compilation):
195 - Build without warnings with the stock OpenSSL srtp.h header, which
196 has a duplicate declaration of SSL_get_selected_srtp_profile().
197 Fixes bug 14220; this is OpenSSL's bug, not ours.
199 o Minor bugfixes (directory authority):
200 - Allow directory authorities to fetch more data from one another if
201 they find themselves missing lots of votes. Previously, they had
202 been bumping against the 10 MB queued data limit. Fixes bug 14261;
203 bugfix on 0.1.2.5-alpha.
204 - Enlarge the buffer to read bwauth generated files to avoid an
205 issue when parsing the file in dirserv_read_measured_bandwidths().
206 Fixes bug 14125; bugfix on 0.2.2.1-alpha.
208 o Minor bugfixes (statistics):
209 - Increase period over which bandwidth observations are aggregated
210 from 15 minutes to 4 hours. Fixes bug 13988; bugfix on 0.0.8pre1.
212 o Minor bugfixes (preventative security, C safety):
213 - When reading a hexadecimal, base-32, or base-64 encoded value from
214 a string, always overwrite the whole output buffer. This prevents
215 some bugs where we would look at (but fortunately, not reveal)
216 uninitialized memory on the stack. Fixes bug 14013; bugfix on all
220 Changes in version 0.2.4.26 - 2015-03-17
221 Tor 0.2.4.26 includes an updated list of directory authorities. It
222 also backports a couple of stability and security bugfixes from 0.2.5
225 o Directory authority changes:
226 - Remove turtles as a directory authority.
227 - Add longclaw as a new (v3) directory authority. This implements
228 ticket 13296. This keeps the directory authority count at 9.
229 - The directory authority Faravahar has a new IP address. This
232 o Major bugfixes (exit node stability, also in 0.2.6.3-alpha):
233 - Fix an assertion failure that could occur under high DNS load.
234 Fixes bug 14129; bugfix on Tor 0.0.7rc1. Found by "jowr";
235 diagnosed and fixed by "cypherpunks".
237 o Major bugfixes (relay, stability, possible security, also in 0.2.6.4-rc):
238 - Fix a bug that could lead to a relay crashing with an assertion
239 failure if a buffer of exactly the wrong layout was passed to
240 buf_pullup() at exactly the wrong time. Fixes bug 15083; bugfix on
241 0.2.0.10-alpha. Patch from 'cypherpunks'.
242 - Do not assert if the 'data' pointer on a buffer is advanced to the
243 very end of the buffer; log a BUG message instead. Only assert if
244 it is past that point. Fixes bug 15083; bugfix on 0.2.0.10-alpha.
246 o Minor features (geoip):
247 - Update geoip to the March 3 2015 Maxmind GeoLite2 Country database.
248 - Update geoip6 to the March 3 2015 Maxmind GeoLite2
252 Changes in version 0.2.6.4-rc - 2015-03-09
253 Tor 0.2.6.4-alpha fixes an issue in the directory code that an
254 attacker might be able to use in order to crash certain Tor
255 directories. It also resolves some minor issues left over from, or
256 introduced in, Tor 0.2.6.3-alpha or earlier.
258 o Major bugfixes (crash, OSX, security):
259 - Fix a remote denial-of-service opportunity caused by a bug in
260 OSX's _strlcat_chk() function. Fixes bug 15205; bug first appeared
263 o Major bugfixes (relay, stability, possible security):
264 - Fix a bug that could lead to a relay crashing with an assertion
265 failure if a buffer of exactly the wrong layout is passed to
266 buf_pullup() at exactly the wrong time. Fixes bug 15083; bugfix on
267 0.2.0.10-alpha. Patch from "cypherpunks".
268 - Do not assert if the 'data' pointer on a buffer is advanced to the
269 very end of the buffer; log a BUG message instead. Only assert if
270 it is past that point. Fixes bug 15083; bugfix on 0.2.0.10-alpha.
272 o Major bugfixes (FreeBSD IPFW transparent proxy):
273 - Fix address detection with FreeBSD transparent proxies, when
274 "TransProxyType ipfw" is in use. Fixes bug 15064; bugfix
277 o Major bugfixes (Linux seccomp2 sandbox):
278 - Pass IPPROTO_TCP rather than 0 to socket(), so that the Linux
279 seccomp2 sandbox doesn't fail. Fixes bug 14989; bugfix
281 - Allow AF_UNIX hidden services to be used with the seccomp2
282 sandbox. Fixes bug 15003; bugfix on 0.2.6.3-alpha.
283 - Upon receiving sighup with the seccomp2 sandbox enabled, do not
284 crash during attempts to call wait4. Fixes bug 15088; bugfix on
285 0.2.5.1-alpha. Patch from "sanic".
287 o Minor features (controller):
288 - Messages about problems in the bootstrap process now include
289 information about the server we were trying to connect to when we
290 noticed the problem. Closes ticket 15006.
292 o Minor features (geoip):
293 - Update geoip to the March 3 2015 Maxmind GeoLite2 Country database.
294 - Update geoip6 to the March 3 2015 Maxmind GeoLite2
297 o Minor features (logs):
298 - Quiet some log messages in the heartbeat and at startup. Closes
301 o Minor bugfixes (certificate handling):
302 - If an authority operator accidentally makes a signing certificate
303 with a future publication time, do not discard its real signing
304 certificates. Fixes bug 11457; bugfix on 0.2.0.3-alpha.
305 - Remove any old authority certificates that have been superseded
306 for at least two days. Previously, we would keep superseded
307 certificates until they expired, if they were published close in
308 time to the certificate that superseded them. Fixes bug 11454;
309 bugfix on 0.2.1.8-alpha.
311 o Minor bugfixes (compilation):
312 - Fix a compilation warning on s390. Fixes bug 14988; bugfix
314 - Fix a compilation warning on FreeBSD. Fixes bug 15151; bugfix
317 o Minor bugfixes (testing):
318 - Fix endianness issues in unit test for resolve_my_address() to
319 have it pass on big endian systems. Fixes bug 14980; bugfix on
321 - Avoid a side-effect in a tor_assert() in the unit tests. Fixes bug
322 15188; bugfix on 0.1.2.3-alpha. Patch from Tom van der Woerdt.
323 - When running the new 'make test-stem' target, use the configured
324 python binary. Fixes bug 15037; bugfix on 0.2.6.3-alpha. Patch
326 - When running the zero-length-keys tests, do not use the default
327 torrc file. Fixes bug 15033; bugfix on 0.2.6.3-alpha. Reported
330 o Directory authority IP change:
331 - The directory authority Faravahar has a new IP address. This
335 - Remove some lingering dead code that once supported mempools.
336 Mempools were disabled by default in 0.2.5, and removed entirely
337 in 0.2.6.3-alpha. Closes more of ticket 14848; patch
341 Changes in version 0.2.6.3-alpha - 2015-02-19
342 Tor 0.2.6.3-alpha is the third (and hopefully final) alpha release in
343 the 0.2.6.x series. It introduces support for more kinds of sockets,
344 makes it harder to accidentally run an exit, improves our
345 multithreading backend, incorporates several fixes for the
346 AutomapHostsOnResolve option, and fixes numerous other bugs besides.
348 If no major regressions or security holes are found in this version,
349 the next version will be a release candidate.
351 o Deprecated versions:
352 - Tor relays older than 0.2.4.18-rc are no longer allowed to
353 advertise themselves on the network. Closes ticket 13555.
355 o Major features (security, unix domain sockets):
356 - Allow SocksPort to be an AF_UNIX Unix Domain Socket. Now high risk
357 applications can reach Tor without having to create AF_INET or
358 AF_INET6 sockets, meaning they can completely disable their
359 ability to make non-Tor network connections. To create a socket of
360 this type, use "SocksPort unix:/path/to/socket". Implements
362 - Support mapping hidden service virtual ports to AF_UNIX sockets.
363 The syntax is "HiddenServicePort 80 unix:/path/to/socket".
364 Implements ticket 11485.
366 o Major features (changed defaults):
367 - Prevent relay operators from unintentionally running exits: When a
368 relay is configured as an exit node, we now warn the user unless
369 the "ExitRelay" option is set to 1. We warn even more loudly if
370 the relay is configured with the default exit policy, since this
371 can indicate accidental misconfiguration. Setting "ExitRelay 0"
372 stops Tor from running as an exit relay. Closes ticket 10067.
374 o Major features (directory system):
375 - When downloading server- or microdescriptors from a directory
376 server, we no longer launch multiple simultaneous requests to the
377 same server. This reduces load on the directory servers,
378 especially when directory guards are in use. Closes ticket 9969.
379 - When downloading server- or microdescriptors over a tunneled
380 connection, do not limit the length of our requests to what the
381 Squid proxy is willing to handle. Part of ticket 9969.
382 - Authorities can now vote on the correct digests and latest
383 versions for different software packages. This allows packages
384 that include Tor to use the Tor authority system as a way to get
385 notified of updates and their correct digests. Implements proposal
386 227. Closes ticket 10395.
388 o Major features (guards):
389 - Introduce the Guardfraction feature to improves load balancing on
390 guard nodes. Specifically, it aims to reduce the traffic gap that
391 guard nodes experience when they first get the Guard flag. This is
392 a required step if we want to increase the guard lifetime to 9
393 months or greater. Closes ticket 9321.
395 o Major features (performance):
396 - Make the CPU worker implementation more efficient by avoiding the
397 kernel and lengthening pipelines. The original implementation used
398 sockets to transfer data from the main thread to the workers, and
399 didn't allow any thread to be assigned more than a single piece of
400 work at once. The new implementation avoids communications
401 overhead by making requests in shared memory, avoiding kernel IO
402 where possible, and keeping more requests in flight at once.
403 Implements ticket 9682.
405 o Major features (relay):
406 - Raise the minimum acceptable configured bandwidth rate for bridges
407 to 50 KiB/sec and for relays to 75 KiB/sec. (The old values were
408 20 KiB/sec.) Closes ticket 13822.
410 o Major bugfixes (exit node stability):
411 - Fix an assertion failure that could occur under high DNS load.
412 Fixes bug 14129; bugfix on Tor 0.0.7rc1. Found by "jowr";
413 diagnosed and fixed by "cypherpunks".
415 o Major bugfixes (mixed relay-client operation):
416 - When running as a relay and client at the same time (not
417 recommended), if we decide not to use a new guard because we want
418 to retry older guards, only close the locally-originating circuits
419 passing through that guard. Previously we would close all the
420 circuits through that guard. Fixes bug 9819; bugfix on
421 0.2.1.1-alpha. Reported by "skruffy".
423 o Minor features (build):
424 - New --disable-system-torrc compile-time option to prevent Tor from
425 looking for the system-wide torrc or torrc-defaults files.
426 Resolves ticket 13037.
428 o Minor features (controller):
429 - Include SOCKS_USERNAME and SOCKS_PASSWORD values in controller
430 events so controllers can observe circuit isolation inputs. Closes
432 - ControlPort now supports the unix:/path/to/socket syntax as an
433 alternative to the ControlSocket option, for consistency with
434 SocksPort and HiddenServicePort. Closes ticket 14451.
435 - New "GETINFO bw-event-cache" to get information about recent
436 bandwidth events. Closes ticket 14128. Useful for controllers to
437 get recent bandwidth history after the fix for ticket 13988.
439 o Minor features (Denial of service resistance):
440 - Count the total number of bytes used storing hidden service
441 descriptors against the value of MaxMemInQueues. If we're low on
442 memory, and more than 20% of our memory is used holding hidden
443 service descriptors, free them until no more than 10% of our
444 memory holds hidden service descriptors. Free the least recently
445 fetched descriptors first. Resolves ticket 13806.
446 - When we have recently been under memory pressure (over 3/4 of
447 MaxMemInQueues is allocated), then allocate smaller zlib objects
448 for small requests. Closes ticket 11791.
450 o Minor features (geoip):
451 - Update geoip and geoip6 files to the January 7 2015 Maxmind
452 GeoLite2 Country database.
454 o Minor features (guard nodes):
455 - Reduce the time delay before saving guard status to disk from 10
456 minutes to 30 seconds (or from one hour to 10 minutes if
457 AvoidDiskWrites is set). Closes ticket 12485.
459 o Minor features (hidden service):
460 - Make Sybil attacks against hidden services harder by changing the
461 minimum time required to get the HSDir flag from 25 hours up to 96
462 hours. Addresses ticket 14149.
463 - New option "HiddenServiceAllowUnknownPorts" to allow hidden
464 services to disable the anti-scanning feature introduced in
465 0.2.6.2-alpha. With this option not set, a connection to an
466 unlisted port closes the circuit. With this option set, only a
467 RELAY_DONE cell is sent. Closes ticket 14084.
469 o Minor features (interface):
470 - Implement "-f -" command-line option to read torrc configuration
471 from standard input, if you don't want to store the torrc file in
472 the file system. Implements feature 13865.
474 o Minor features (logging):
475 - Add a count of unique clients to the bridge heartbeat message.
476 Resolves ticket 6852.
477 - Suppress "router info incompatible with extra info" message when
478 reading extrainfo documents from cache. (This message got loud
479 around when we closed bug 9812 in 0.2.6.2-alpha.) Closes
481 - Elevate hidden service authorized-client message from DEBUG to
482 INFO. Closes ticket 14015.
484 o Minor features (stability):
485 - Add assertions in our hash-table iteration code to check for
486 corrupted values that could cause infinite loops. Closes
489 o Minor features (systemd):
490 - Various improvements and modernizations in systemd hardening
491 support. Closes ticket 13805. Patch from Craig Andrews.
493 o Minor features (testing networks):
494 - Drop the minimum RendPostPeriod on a testing network to 5 seconds,
495 and the default on a testing network to 2 minutes. Drop the
496 MIN_REND_INITIAL_POST_DELAY on a testing network to 5 seconds, but
497 keep the default on a testing network at 30 seconds. This reduces
498 HS bootstrap time to around 25 seconds. Also, change the default
499 time in test-network.sh to match. Closes ticket 13401. Patch
501 - Create TestingDirAuthVoteHSDir to correspond to
502 TestingDirAuthVoteExit/Guard. Ensures that authorities vote the
503 HSDir flag for the listed relays regardless of uptime or ORPort
504 connectivity. Respects the value of VoteOnHidServDirectoriesV2.
505 Partial implementation for ticket 14067. Patch by "teor".
507 o Minor features (tor2web mode):
508 - Introduce the config option Tor2webRendezvousPoints, which allows
509 clients in Tor2webMode to select a specific Rendezvous Point to be
510 used in HS circuits. This might allow better performance for
511 Tor2Web nodes. Implements ticket 12844.
513 o Minor bugfixes (client DNS):
514 - Report the correct cached DNS expiration times on SOCKS port or in
515 DNS replies. Previously, we would report everything as "never
516 expires." Fixes bug 14193; bugfix on 0.2.3.17-beta.
517 - Avoid a small memory leak when we find a cached answer for a
518 reverse DNS lookup in a client-side DNS cache. (Remember, client-
519 side DNS caching is off by default, and is not recommended.) Fixes
520 bug 14259; bugfix on 0.2.0.1-alpha.
522 o Minor bugfixes (client, automapping):
523 - Avoid crashing on torrc lines for VirtualAddrNetworkIPv[4|6] when
524 no value follows the option. Fixes bug 14142; bugfix on
525 0.2.4.7-alpha. Patch by "teor".
526 - Fix a memory leak when using AutomapHostsOnResolve. Fixes bug
527 14195; bugfix on 0.1.0.1-rc.
528 - Prevent changes to other options from removing the wildcard value
529 "." from "AutomapHostsSuffixes". Fixes bug 12509; bugfix
531 - Allow MapAddress and AutomapHostsOnResolve to work together when
532 an address is mapped into another address type (like .onion) that
533 must be automapped at resolve time. Fixes bug 7555; bugfix
536 o Minor bugfixes (client, bridges):
537 - When we are using bridges and we had a network connectivity
538 problem, only retry connecting to our currently configured
539 bridges, not all bridges we know about and remember using. Fixes
540 bug 14216; bugfix on 0.2.2.17-alpha.
542 o Minor bugfixes (client, IPv6):
543 - Reject socks requests to literal IPv6 addresses when IPv6Traffic
544 flag is not set; and not because the NoIPv4Traffic flag was set.
545 Previously we'd looked at the NoIPv4Traffic flag for both types of
546 literal addresses. Fixes bug 14280; bugfix on 0.2.4.7-alpha.
548 o Minor bugfixes (compilation):
549 - The address of an array in the middle of a structure will always
550 be non-NULL. clang recognises this and complains. Disable the
551 tautologous and redundant check to silence this warning. Fixes bug
552 14001; bugfix on 0.2.1.2-alpha.
553 - Avoid warnings when building with systemd 209 or later. Fixes bug
554 14072; bugfix on 0.2.6.2-alpha. Patch from "h.venev".
555 - Compile correctly with (unreleased) OpenSSL 1.1.0 headers.
556 Addresses ticket 14188.
557 - Build without warnings with the stock OpenSSL srtp.h header, which
558 has a duplicate declaration of SSL_get_selected_srtp_profile().
559 Fixes bug 14220; this is OpenSSL's bug, not ours.
560 - Do not compile any code related to Tor2Web mode when Tor2Web mode
561 is not enabled at compile time. Previously, this code was included
562 in a disabled state. See discussion on ticket 12844.
563 - Remove the --disable-threads configure option again. It was
564 accidentally partially reintroduced in 29ac883606d6d. Fixes bug
565 14819; bugfix on 0.2.6.2-alpha.
567 o Minor bugfixes (controller):
568 - Report "down" in response to the "GETINFO entry-guards" command
569 when relays are down with an unreachable_since value. Previously,
570 we would report "up". Fixes bug 14184; bugfix on 0.1.2.2-alpha.
571 - Avoid crashing on a malformed EXTENDCIRCUIT command. Fixes bug
572 14116; bugfix on 0.2.2.9-alpha.
573 - Add a code for the END_CIRC_REASON_IP_NOW_REDUNDANT circuit close
574 reason. Fixes bug 14207; bugfix on 0.2.6.2-alpha.
576 o Minor bugfixes (directory authority):
577 - Allow directory authorities to fetch more data from one another if
578 they find themselves missing lots of votes. Previously, they had
579 been bumping against the 10 MB queued data limit. Fixes bug 14261;
580 bugfix on 0.1.2.5-alpha.
581 - Do not attempt to download extrainfo documents which we will be
582 unable to validate with a matching server descriptor. Fixes bug
583 13762; bugfix on 0.2.0.1-alpha.
584 - Fix a bug that was truncating AUTHDIR_NEWDESC events sent to the
585 control port. Fixes bug 14953; bugfix on 0.2.0.1-alpha.
586 - Enlarge the buffer to read bwauth generated files to avoid an
587 issue when parsing the file in dirserv_read_measured_bandwidths().
588 Fixes bug 14125; bugfix on 0.2.2.1-alpha.
590 o Minor bugfixes (file handling):
591 - Stop failing when key files are zero-length. Instead, generate new
592 keys, and overwrite the empty key files. Fixes bug 13111; bugfix
593 on all versions of Tor. Patch by "teor".
594 - Stop generating a fresh .old RSA onion key file when the .old file
595 is missing. Fixes part of 13111; bugfix on 0.0.6rc1.
596 - Avoid overwriting .old key files with empty key files.
597 - Skip loading zero-length extrainfo store, router store, stats,
598 state, and key files.
599 - Avoid crashing when trying to reload a torrc specified as a
600 relative path with RunAsDaemon turned on. Fixes bug 13397; bugfix
603 o Minor bugfixes (hidden services):
604 - Close the introduction circuit when we have no more usable intro
605 points, instead of waiting for it to time out. This also ensures
606 that no follow-up HS descriptor fetch is triggered when the
607 circuit eventually times out. Fixes bug 14224; bugfix on 0.0.6.
608 - When fetching a hidden service descriptor for a down service that
609 was recently up, do not keep refetching until we try the same
610 replica twice in a row. Fixes bug 14219; bugfix on 0.2.0.10-alpha.
611 - Successfully launch Tor with a nonexistent hidden service
612 directory. Our fix for bug 13942 didn't catch this case. Fixes bug
613 14106; bugfix on 0.2.6.2-alpha.
615 o Minor bugfixes (logging):
616 - Avoid crashing when there are more log domains than entries in
617 domain_list. Bugfix on 0.2.3.1-alpha.
618 - Add a string representation for LD_SCHED. Fixes bug 14740; bugfix
620 - Don't log messages to stdout twice when starting up. Fixes bug
621 13993; bugfix on 0.2.6.1-alpha.
623 o Minor bugfixes (parsing):
624 - Stop accepting milliseconds (or other junk) at the end of
625 descriptor publication times. Fixes bug 9286; bugfix on 0.0.2pre25.
626 - Support two-number and three-number version numbers correctly, in
627 case we change the Tor versioning system in the future. Fixes bug
628 13661; bugfix on 0.0.8pre1.
630 o Minor bugfixes (path counting):
631 - When deciding whether the consensus lists any exit nodes, count
632 the number listed in the consensus, not the number we have
633 descriptors for. Fixes part of bug 14918; bugfix on 0.2.6.2-alpha.
634 - When deciding whether we have any exit nodes, only examine
635 ExitNodes when the ExitNodes option is actually set. Fixes part of
636 bug 14918; bugfix on 0.2.6.2-alpha.
637 - Get rid of redundant and possibly scary warnings that we are
638 missing directory information while we bootstrap. Fixes part of
639 bug 14918; bugfix on 0.2.6.2-alpha.
641 o Minor bugfixes (portability):
642 - Fix the ioctl()-based network interface lookup code so that it
643 will work on systems that have variable-length struct ifreq, for
645 - Fix scheduler compilation on targets where char is unsigned. Fixes
646 bug 14764; bugfix on 0.2.6.2-alpha. Reported by Christian Kujau.
648 o Minor bugfixes (sandbox):
649 - Allow glibc fatal errors to be sent to stderr before Tor exits.
650 Previously, glibc would try to write them to /dev/tty, and the
651 sandbox would trap the call and make Tor exit prematurely. Fixes
652 bug 14759; bugfix on 0.2.5.1-alpha.
654 o Minor bugfixes (shutdown):
655 - When shutting down, always call event_del() on lingering read or
656 write events before freeing them. Otherwise, we risk double-frees
657 or read-after-frees in event_base_free(). Fixes bug 12985; bugfix
660 o Minor bugfixes (small memory leaks):
661 - Avoid leaking memory when using IPv6 virtual address mappings.
662 Fixes bug 14123; bugfix on 0.2.4.7-alpha. Patch by Tom van
665 o Minor bugfixes (statistics):
666 - Increase period over which bandwidth observations are aggregated
667 from 15 minutes to 4 hours. Fixes bug 13988; bugfix on 0.0.8pre1.
669 o Minor bugfixes (systemd support):
670 - Fix detection and operation of systemd watchdog. Fixes part of bug
671 14141; bugfix on 0.2.6.2-alpha. Patch from Tomasz Torcz.
672 - Run correctly under systemd with the RunAsDaemon option set. Fixes
673 part of bug 14141; bugfix on 0.2.5.7-rc. Patch from Tomasz Torcz.
674 - Inform the systemd supervisor about more changes in the Tor
675 process status. Implements part of ticket 14141. Patch from
677 - Cause the "--disable-systemd" option to actually disable systemd
678 support. Fixes bug 14350; bugfix on 0.2.6.2-alpha. Patch
681 o Minor bugfixes (TLS):
682 - Check more thoroughly throughout the TLS code for possible
683 unlogged TLS errors. Possible diagnostic or fix for bug 13319.
685 o Minor bugfixes (transparent proxy):
686 - Use getsockname, not getsockopt, to retrieve the address for a
687 TPROXY-redirected connection. Fixes bug 13796; bugfix
690 o Code simplification and refactoring:
691 - Move fields related to isolating and configuring client ports into
692 a shared structure. Previously, they were duplicated across
693 port_cfg_t, listener_connection_t, and edge_connection_t. Failure
694 to copy them correctly had been the cause of at least one bug in
695 the past. Closes ticket 8546.
696 - Refactor the get_interface_addresses_raw() doom-function into
697 multiple smaller and simpler subfunctions. Cover the resulting
698 subfunctions with unit-tests. Fixes a significant portion of
700 - Remove workaround in dirserv_thinks_router_is_hs_dir() that was
701 only for version <= 0.2.2.24 which is now deprecated. Closes
703 - Remove a test for a long-defunct broken version-one
707 - Adding section on OpenBSD to our TUNING document. Thanks to mmcc
708 for writing the OpenBSD-specific tips. Resolves ticket 13702.
709 - Make the tor-resolve documentation match its help string and its
710 options. Resolves part of ticket 14325.
711 - Log a more useful error message from tor-resolve when failing to
712 look up a hidden service address. Resolves part of ticket 14325.
714 o Downgraded warnings:
715 - Don't warn when we've attempted to contact a relay using the wrong
716 ntor onion key. Closes ticket 9635.
719 - To avoid confusion with the "ExitRelay" option, "ExitNode" is no
720 longer silently accepted as an alias for "ExitNodes".
721 - The --enable-mempool and --enable-buf-freelists options, which
722 were originally created to work around bad malloc implementations,
723 no longer exist. They were off-by-default in 0.2.5. Closes
727 - Make the checkdir/perms test complete successfully even if the
728 global umask is not 022. Fixes bug 14215; bugfix on 0.2.6.2-alpha.
729 - Test that tor does not fail when key files are zero-length. Check
730 that tor generates new keys, and overwrites the empty key files.
731 - Test that tor generates new keys when keys are missing
733 - Test that tor does not overwrite key files that already contain
734 data (existing behavior). Tests bug 13111. Patch by "teor".
735 - New "make test-stem" target to run stem integration tests.
736 Requires that the "STEM_SOURCE_DIR" environment variable be set.
738 - Make the test_cmdline_args.py script work correctly on Windows.
739 Patch from Gisle Vanem.
740 - Move the slower unit tests into a new "./src/test/test-slow"
741 binary that can be run independently of the other tests. Closes
743 - Avoid undefined behavior when sampling huge values from the
744 Laplace distribution. This made unittests fail on Raspberry Pi.
745 Bug found by Device. Fixes bug 14090; bugfix on 0.2.6.2-alpha.
748 Changes in version 0.2.6.2-alpha - 2014-12-31
749 Tor 0.2.6.2-alpha is the second alpha release in the 0.2.6.x series.
750 It introduces a major new backend for deciding when to send cells on
751 channels, which should lead down the road to big performance
752 increases. It contains security and statistics features for better
753 work on hidden services, and numerous bugfixes.
755 This release contains many new unit tests, along with major
756 performance improvements for running testing networks using Chutney.
757 Thanks to a series of patches contributed by "teor", testing networks
758 should now bootstrap in seconds, rather than minutes.
760 o Major features (relay, infrastructure):
761 - Complete revision of the code that relays use to decide which cell
762 to send next. Formerly, we selected the best circuit to write on
763 each channel, but we didn't select among channels in any
764 sophisticated way. Now, we choose the best circuits globally from
765 among those whose channels are ready to deliver traffic.
767 This patch implements a new inter-cmux comparison API, a global
768 high/low watermark mechanism and a global scheduler loop for
769 transmission prioritization across all channels as well as among
770 circuits on one channel. This schedule is currently tuned to
771 (tolerantly) avoid making changes in network performance, but it
772 should form the basis for major circuit performance increases in
773 the future. Code by Andrea; tuning by Rob Jansen; implements
776 o Major features (hidden services):
777 - Make HS port scanning more difficult by immediately closing the
778 circuit when a user attempts to connect to a nonexistent port.
780 - Add a HiddenServiceStatistics option that allows Tor relays to
781 gather and publish statistics about the overall size and volume of
782 hidden service usage. Specifically, when this option is turned on,
783 an HSDir will publish an approximate number of hidden services
784 that have published descriptors to it the past 24 hours. Also, if
785 a relay has acted as a hidden service rendezvous point, it will
786 publish the approximate amount of rendezvous cells it has relayed
787 the past 24 hours. The statistics themselves are obfuscated so
788 that the exact values cannot be derived. For more details see
789 proposal 238, "Better hidden service stats from Tor relays". This
790 feature is currently disabled by default. Implements feature 13192.
792 o Major bugfixes (client, automap):
793 - Repair automapping with IPv6 addresses. This automapping should
794 have worked previously, but one piece of debugging code that we
795 inserted to detect a regression actually caused the regression to
796 manifest itself again. Fixes bug 13811 and bug 12831; bugfix on
797 0.2.4.7-alpha. Diagnosed and fixed by Francisco Blas
800 o Major bugfixes (hidden services):
801 - When closing an introduction circuit that was opened in parallel
802 with others, don't mark the introduction point as unreachable.
803 Previously, the first successful connection to an introduction
804 point would make the other introduction points get marked as
805 having timed out. Fixes bug 13698; bugfix on 0.0.6rc2.
807 o Directory authority changes:
808 - Remove turtles as a directory authority.
809 - Add longclaw as a new (v3) directory authority. This implements
810 ticket 13296. This keeps the directory authority count at 9.
812 o Major removed features:
813 - Tor clients no longer support connecting to hidden services
814 running on Tor 0.2.2.x and earlier; the Support022HiddenServices
815 option has been removed. (There shouldn't be any hidden services
816 running these versions on the network.) Closes ticket 7803.
818 o Minor features (client):
819 - Validate hostnames in SOCKS5 requests more strictly. If SafeSocks
820 is enabled, reject requests with IP addresses as hostnames.
821 Resolves ticket 13315.
823 o Minor features (controller):
824 - Add a "SIGNAL HEARTBEAT" controller command that tells Tor to
825 write an unscheduled heartbeat message to the log. Implements
828 o Minor features (geoip):
829 - Update geoip and geoip6 to the November 15 2014 Maxmind GeoLite2
832 o Minor features (hidden services):
833 - When re-enabling the network, don't try to build introduction
834 circuits until we have successfully built a circuit. This makes
835 hidden services come up faster when the network is re-enabled.
836 Patch from "akwizgran". Closes ticket 13447.
837 - When we fail to retrieve a hidden service descriptor, send the
838 controller an "HS_DESC FAILED" controller event. Implements
840 - New HiddenServiceDirGroupReadable option to cause hidden service
841 directories and hostname files to be created group-readable. Patch
842 from "anon", David Stainton, and "meejah". Closes ticket 11291.
844 o Minor features (systemd):
845 - Where supported, when running with systemd, report successful
846 startup to systemd. Part of ticket 11016. Patch by Michael Scherer.
847 - When running with systemd, support systemd watchdog messages. Part
848 of ticket 11016. Patch by Michael Scherer.
850 o Minor features (transparent proxy):
851 - Update the transparent proxy option checks to allow for both ipfw
852 and pf on OS X. Closes ticket 14002.
853 - Use the correct option when using IPv6 with transparent proxy
854 support on Linux. Resolves 13808. Patch by Francisco Blas
857 o Minor bugfixes (preventative security, C safety):
858 - When reading a hexadecimal, base-32, or base-64 encoded value from
859 a string, always overwrite the whole output buffer. This prevents
860 some bugs where we would look at (but fortunately, not reveal)
861 uninitialized memory on the stack. Fixes bug 14013; bugfix on all
863 - Clear all memory targetted by tor_addr_{to,from}_sockaddr(), not
864 just the part that's used. This makes it harder for data leak bugs
865 to occur in the event of other programming failures. Resolves
868 o Minor bugfixes (client, microdescriptors):
869 - Use a full 256 bits of the SHA256 digest of a microdescriptor when
870 computing which microdescriptors to download. This keeps us from
871 erroneous download behavior if two microdescriptor digests ever
872 have the same first 160 bits. Fixes part of bug 13399; bugfix
874 - Reset a router's status if its microdescriptor digest changes,
875 even if the first 160 bits remain the same. Fixes part of bug
876 13399; bugfix on 0.2.3.1-alpha.
878 o Minor bugfixes (compilation):
879 - Silence clang warnings under --enable-expensive-hardening,
880 including implicit truncation of 64 bit values to 32 bit, const
881 char assignment to self, tautological compare, and additional
882 parentheses around equality tests. Fixes bug 13577; bugfix
884 - Fix a clang warning about checking whether an address in the
885 middle of a structure is NULL. Fixes bug 14001; bugfix
888 o Minor bugfixes (hidden services):
889 - Correctly send a controller event when we find that a rendezvous
890 circuit has finished. Fixes bug 13936; bugfix on 0.1.1.5-alpha.
891 - Pre-check directory permissions for new hidden-services to avoid
892 at least one case of "Bug: Acting on config options left us in a
893 broken state. Dying." Fixes bug 13942; bugfix on 0.0.6pre1.
894 - When adding a new hidden service (for example, via SETCONF), Tor
895 no longer congratulates the user for running a relay. Fixes bug
896 13941; bugfix on 0.2.6.1-alpha.
897 - When fetching hidden service descriptors, we now check not only
898 for whether we got the hidden service we had in mind, but also
899 whether we got the particular descriptors we wanted. This prevents
900 a class of inefficient but annoying DoS attacks by hidden service
901 directories. Fixes bug 13214; bugfix on 0.2.1.6-alpha. Reported
904 o Minor bugfixes (Linux seccomp2 sandbox):
905 - Make transparent proxy support work along with the seccomp2
906 sandbox. Fixes part of bug 13808; bugfix on 0.2.5.1-alpha. Patch
907 by Francisco Blas Izquierdo Riera.
908 - Fix a memory leak in tor-resolve when running with the sandbox
909 enabled. Fixes bug 14050; bugfix on 0.2.5.9-rc.
911 o Minor bugfixes (logging):
912 - Downgrade warnings about RSA signature failures to info log level.
913 Emit a warning when an extra info document is found incompatible
914 with a corresponding router descriptor. Fixes bug 9812; bugfix
916 - Make connection_ap_handshake_attach_circuit() log the circuit ID
917 correctly. Fixes bug 13701; bugfix on 0.0.6.
919 o Minor bugfixes (misc):
920 - Stop allowing invalid address patterns like "*/24" that contain
921 both a wildcard address and a bit prefix length. This affects all
922 our address-range parsing code. Fixes bug 7484; bugfix
925 o Minor bugfixes (testing networks, fast startup):
926 - Allow Tor to build circuits using a consensus with no exits. If
927 the consensus has no exits (typical of a bootstrapping test
928 network), allow Tor to build circuits once enough descriptors have
929 been downloaded. This assists in bootstrapping a testing Tor
930 network. Fixes bug 13718; bugfix on 0.2.4.10-alpha. Patch
932 - When V3AuthVotingInterval is low, give a lower If-Modified-Since
933 header to directory servers. This allows us to obtain consensuses
934 promptly when the consensus interval is very short. This assists
935 in bootstrapping a testing Tor network. Fixes parts of bugs 13718
936 and 13963; bugfix on 0.2.0.3-alpha. Patch by "teor".
937 - Stop assuming that private addresses are local when checking
938 reachability in a TestingTorNetwork. Instead, when testing, assume
939 all OR connections are remote. (This is necessary due to many test
940 scenarios running all relays on localhost.) This assists in
941 bootstrapping a testing Tor network. Fixes bug 13924; bugfix on
942 0.1.0.1-rc. Patch by "teor".
943 - Avoid building exit circuits from a consensus with no exits. Now
944 thanks to our fix for 13718, we accept a no-exit network as not
945 wholly lost, but we need to remember not to try to build exit
946 circuits on it. Closes ticket 13814; patch by "teor".
947 - Stop requiring exits to have non-zero bandwithcapacity in a
948 TestingTorNetwork. Instead, when TestingMinExitFlagThreshold is 0,
949 ignore exit bandwidthcapacity. This assists in bootstrapping a
950 testing Tor network. Fixes parts of bugs 13718 and 13839; bugfix
951 on 0.2.0.3-alpha. Patch by "teor".
952 - Add "internal" to some bootstrap statuses when no exits are
953 available. If the consensus does not contain Exits, Tor will only
954 build internal circuits. In this case, relevant statuses will
955 contain the word "internal" as indicated in the Tor control-
956 spec.txt. When bootstrap completes, Tor will be ready to build
957 internal circuits. If a future consensus contains Exits, exit
958 circuits may become available. Fixes part of bug 13718; bugfix on
959 0.2.4.10-alpha. Patch by "teor".
960 - Decrease minimum consensus interval to 10 seconds when
961 TestingTorNetwork is set, or 5 seconds for the first consensus.
962 Fix assumptions throughout the code that assume larger intervals.
963 Fixes bugs 13718 and 13823; bugfix on 0.2.0.3-alpha. Patch
965 - Avoid excluding guards from path building in minimal test
966 networks, when we're in a test network and excluding guards would
967 exclude all relays. This typically occurs in incredibly small tor
968 networks, and those using "TestingAuthVoteGuard *". Fixes part of
969 bug 13718; bugfix on 0.1.1.11-alpha. Patch by "teor".
971 o Code simplification and refactoring:
972 - Stop using can_complete_circuits as a global variable; access it
973 with a function instead.
974 - Avoid using operators directly as macro arguments: this lets us
975 apply coccinelle transformations to our codebase more directly.
977 - Combine the functions used to parse ClientTransportPlugin and
978 ServerTransportPlugin into a single function. Closes ticket 6456.
979 - Add inline functions and convenience macros for inspecting channel
980 state. Refactor the code to use convenience macros instead of
981 checking channel state directly. Fixes issue 7356.
982 - Document all members of was_router_added_t and rename
983 ROUTER_WAS_NOT_NEW to ROUTER_IS_ALREADY_KNOWN to make it less
984 confusable with ROUTER_WAS_TOO_OLD. Fixes issue 13644.
985 - In connection_exit_begin_conn(), use END_CIRC_REASON_TORPROTOCOL
986 constant instead of hardcoded value. Fixes issue 13840.
987 - Refactor our generic strmap and digestmap types into a single
988 implementation, so that we can add a new digest256map
992 - Document the bridge-authority-only 'networkstatus-bridges' file.
993 Closes ticket 13713; patch from "tom".
994 - Fix typo in PredictedPortsRelevanceTime option description in
995 manpage. Resolves issue 13707.
996 - Stop suggesting that users specify relays by nickname: it isn't a
997 good idea. Also, properly cross-reference how to specify relays in
998 all parts of manual documenting options that take a list of
999 relays. Closes ticket 13381.
1000 - Clarify the HiddenServiceDir option description in manpage to make
1001 it clear that relative paths are taken with respect to the current
1002 working directory. Also clarify that this behavior is not
1003 guaranteed to remain indefinitely. Fixes issue 13913.
1006 - New tests for many parts of channel, relay, and circuitmux
1007 functionality. Code by Andrea; part of 9262.
1008 - New tests for parse_transport_line(). Part of ticket 6456.
1009 - In the unit tests, use chgrp() to change the group of the unit
1010 test temporary directory to the current user, so that the sticky
1011 bit doesn't interfere with tests that check directory groups.
1013 - Add unit tests for resolve_my_addr(). Part of ticket 12376; patch
1017 Changes in version 0.2.6.1-alpha - 2014-10-30
1018 Tor 0.2.6.1-alpha is the first release in the Tor 0.2.6.x series. It
1019 includes numerous code cleanups and new tests, and fixes a large
1020 number of annoying bugs. Out-of-memory conditions are handled better
1021 than in 0.2.5, pluggable transports have improved proxy support, and
1022 clients now use optimistic data for contacting hidden services. Also,
1023 we are now more robust to changes in what we consider a parseable
1024 directory object, so that tightening restrictions does not have a risk
1025 of introducing infinite download loops.
1027 This is the first alpha release in a new series, so expect there to be
1028 bugs. Users who would rather test out a more stable branch should stay
1029 with 0.2.5.x for now.
1031 o New compiler and system requirements:
1032 - Tor 0.2.6.x requires that your compiler support more of the C99
1033 language standard than before. The 'configure' script now detects
1034 whether your compiler supports C99 mid-block declarations and
1035 designated initializers. If it does not, Tor will not compile.
1037 We may revisit this requirement if it turns out that a significant
1038 number of people need to build Tor with compilers that don't
1039 bother implementing a 15-year-old standard. Closes ticket 13233.
1040 - Tor no longer supports systems without threading support. When we
1041 began working on Tor, there were several systems that didn't have
1042 threads, or where the thread support wasn't able to run the
1043 threads of a single process on multiple CPUs. That no longer
1044 holds: every system where Tor needs to run well now has threading
1045 support. Resolves ticket 12439.
1047 o Removed platform support:
1048 - We no longer include special code to build on Windows CE; as far
1049 as we know, nobody has used Tor on Windows CE in a very long time.
1050 Closes ticket 11446.
1052 o Major features (bridges):
1053 - Expose the outgoing upstream HTTP/SOCKS proxy to pluggable
1054 transports if they are configured via the "TOR_PT_PROXY"
1055 environment variable. Implements proposal 232. Resolves
1058 o Major features (client performance, hidden services):
1059 - Allow clients to use optimistic data when connecting to a hidden
1060 service, which should remove a round-trip from hidden service
1061 initialization. See proposal 181 for details. Implements
1064 o Major features (directory system):
1065 - Upon receiving an unparseable directory object, if its digest
1066 matches what we expected, then don't try to download it again.
1067 Previously, when we got a descriptor we didn't like, we would keep
1068 trying to download it over and over. Closes ticket 11243.
1070 o Major features (sample torrc):
1071 - Add a new, infrequently-changed "torrc.minimal". This file is
1072 similar to torrc.sample, but it will change as infrequently as
1073 possible, for the benefit of users whose systems prompt them for
1074 intervention whenever a default configuration file is changed.
1075 Making this change allows us to update torrc.sample to be a more
1076 generally useful "sample torrc".
1078 o Major bugfixes (directory authorities):
1079 - Do not assign the HSDir flag to relays if they are not Valid, or
1080 currently hibernating. Fixes 12573; bugfix on 0.2.0.10-alpha.
1082 o Major bugfixes (directory bandwidth performance):
1083 - Don't flush the zlib buffer aggressively when compressing
1084 directory information for clients. This should save about 7% of
1085 the bandwidth currently used for compressed descriptors and
1086 microdescriptors. Fixes bug 11787; bugfix on 0.1.1.23.
1088 o Minor features (security, memory wiping):
1089 - Ensure we securely wipe keys from memory after
1090 crypto_digest_get_digest and init_curve25519_keypair_from_file
1091 have finished using them. Resolves ticket 13477.
1093 o Minor features (security, out-of-memory handling):
1094 - When handling an out-of-memory condition, allocate less memory for
1095 temporary data structures. Fixes issue 10115.
1096 - When handling an out-of-memory condition, consider more types of
1097 buffers, including those on directory connections, and zlib
1098 buffers. Resolves ticket 11792.
1101 - When identity keypair is generated for first time, log a
1102 congratulatory message that links to the new relay lifecycle
1103 document. Implements feature 10427.
1105 o Minor features (client):
1106 - Clients are now willing to send optimistic data (before they
1107 receive a 'connected' cell) to relays of any version. (Relays
1108 without support for optimistic data are no longer supported on the
1109 Tor network.) Resolves ticket 13153.
1111 o Minor features (directory authorities):
1112 - Don't list relays with a bandwidth estimate of 0 in the consensus.
1113 Implements a feature proposed during discussion of bug 13000.
1114 - In tor-gencert, report an error if the user provides the same
1115 argument more than once.
1116 - If a directory authority can't find a best consensus method in the
1117 votes that it holds, it now falls back to its favorite consensus
1118 method. Previously, it fell back to method 1. Neither of these is
1119 likely to get enough signatures, but "fall back to favorite"
1120 doesn't require us to maintain support an obsolete consensus
1121 method. Implements part of proposal 215.
1123 o Minor features (logging):
1124 - On Unix-like systems, you can now use named pipes as the target of
1125 the Log option, and other options that try to append to files.
1126 Closes ticket 12061. Patch from "carlo von lynX".
1127 - When opening a log file at startup, send it every log message that
1128 we generated between startup and opening it. Previously, log
1129 messages that were generated before opening the log file were only
1130 logged to stdout. Closes ticket 6938.
1131 - Add a TruncateLogFile option to overwrite logs instead of
1132 appending to them. Closes ticket 5583.
1134 o Minor features (portability, Solaris):
1135 - Threads are no longer disabled by default on Solaris; we believe
1136 that the versions of Solaris with broken threading support are all
1137 obsolete by now. Resolves ticket 9495.
1139 o Minor features (relay):
1140 - Re-check our address after we detect a changed IP address from
1141 getsockname(). This ensures that the controller command "GETINFO
1142 address" will report the correct value. Resolves ticket 11582.
1144 - A new AccountingRule option lets Relays set whether they'd like
1145 AccountingMax to be applied separately to inbound and outbound
1146 traffic, or applied to the sum of inbound and outbound traffic.
1147 Resolves ticket 961. Patch by "chobe".
1149 o Minor features (testing networks):
1150 - Add the TestingDirAuthVoteExit option, which lists nodes to assign
1151 the "Exit" flag regardless of their uptime, bandwidth, or exit
1152 policy. TestingTorNetwork must be set for this option to have any
1153 effect. Previously, authorities would take up to 35 minutes to
1154 give nodes the Exit flag in a test network. Partially implements
1157 o Minor features (validation):
1158 - Check all date/time values passed to tor_timegm and
1159 parse_rfc1123_time for validity, taking leap years into account.
1160 Improves HTTP header validation. Implemented with bug 13476.
1161 - In correct_tm(), limit the range of values returned by system
1162 localtime(_r) and gmtime(_r) to be between the years 1 and 8099.
1163 This means we don't have to deal with negative or too large dates,
1164 even if a clock is wrong. Otherwise we might fail to read a file
1165 written by us which includes such a date. Fixes bug 13476.
1167 o Minor bugfixes (bridge clients):
1168 - When configured to use a bridge without an identity digest (not
1169 recommended), avoid launching an extra channel to it when
1170 bootstrapping. Fixes bug 7733; bugfix on 0.2.4.4-alpha.
1172 o Minor bugfixes (bridges):
1173 - When DisableNetwork is set, do not launch pluggable transport
1174 plugins, and if any are running, terminate them. Fixes bug 13213;
1175 bugfix on 0.2.3.6-alpha.
1177 o Minor bugfixes (C correctness):
1178 - Fix several instances of possible integer overflow/underflow/NaN.
1179 Fixes bug 13104; bugfix on 0.2.3.1-alpha and later. Patches
1181 - In circuit_build_times_calculate_timeout() in circuitstats.c,
1182 avoid dividing by zero in the pareto calculations. This traps
1183 under clang's "undefined-trap" sanitizer. Fixes bug 13290; bugfix
1185 - Fix an integer overflow in format_time_interval(). Fixes bug
1186 13393; bugfix on 0.2.0.10-alpha.
1187 - Set the correct day of year value when the system's localtime(_r)
1188 or gmtime(_r) functions fail to set struct tm. Not externally
1189 visible. Fixes bug 13476; bugfix on 0.0.2pre14.
1190 - Avoid unlikely signed integer overflow in tor_timegm on systems
1191 with 32-bit time_t. Fixes bug 13476; bugfix on 0.0.2pre14.
1193 o Minor bugfixes (client):
1194 - Fix smartlist_choose_node_by_bandwidth() so that relays with the
1195 BadExit flag are not considered worthy candidates. Fixes bug
1196 13066; bugfix on 0.1.2.3-alpha.
1197 - Use the consensus schedule for downloading consensuses, and not
1198 the generic schedule. Fixes bug 11679; bugfix on 0.2.2.6-alpha.
1199 - Handle unsupported or malformed SOCKS5 requests properly by
1200 responding with the appropriate error message before closing the
1201 connection. Fixes bugs 12971 and 13314; bugfix on 0.0.2pre13.
1203 o Minor bugfixes (client, torrc):
1204 - Stop modifying the value of our DirReqStatistics torrc option just
1205 because we're not a bridge or relay. This bug was causing Tor
1206 Browser users to write "DirReqStatistics 0" in their torrc files
1207 as if they had chosen to change the config. Fixes bug 4244; bugfix
1209 - When GeoIPExcludeUnknown is enabled, do not incorrectly decide
1210 that our options have changed every time we SIGHUP. Fixes bug
1211 9801; bugfix on 0.2.4.10-alpha. Patch from "qwerty1".
1213 o Minor bugfixes (controller):
1214 - Return an error when the second or later arguments of the
1215 "setevents" controller command are invalid events. Previously we
1216 would return success while silently skipping invalid events. Fixes
1217 bug 13205; bugfix on 0.2.3.2-alpha. Reported by "fpxnns".
1219 o Minor bugfixes (directory system):
1220 - Always believe that v3 directory authorities serve extra-info
1221 documents, whether they advertise "caches-extra-info" or not.
1222 Fixes part of bug 11683; bugfix on 0.2.0.1-alpha.
1223 - When running as a v3 directory authority, advertise that you serve
1224 extra-info documents so that clients who want them can find them
1225 from you too. Fixes part of bug 11683; bugfix on 0.2.0.1-alpha.
1226 - Check the BRIDGE_DIRINFO flag bitwise rather than using equality.
1227 Previously, directories offering BRIDGE_DIRINFO and some other
1228 flag (i.e. microdescriptors or extrainfo) would be ignored when
1229 looking for bridges. Partially fixes bug 13163; bugfix
1232 o Minor bugfixes (networking):
1233 - Check for orconns and use connection_or_close_for_error() rather
1234 than connection_mark_for_close() directly in the getsockopt()
1235 failure case of connection_handle_write_impl(). Fixes bug 11302;
1236 bugfix on 0.2.4.4-alpha.
1238 o Minor bugfixes (relay):
1239 - When generating our family list, remove spaces from around the
1240 entries. Fixes bug 12728; bugfix on 0.2.1.7-alpha.
1241 - If our previous bandwidth estimate was 0 bytes, allow publishing a
1242 new relay descriptor immediately. Fixes bug 13000; bugfix
1245 o Minor bugfixes (testing networks):
1246 - Fix TestingDirAuthVoteGuard to properly give out Guard flags in a
1247 testing network. Fixes bug 13064; bugfix on 0.2.5.2-alpha.
1248 - Stop using the default authorities in networks which provide both
1249 AlternateDirAuthority and AlternateBridgeAuthority. Partially
1250 fixes bug 13163; bugfix on 0.2.0.13-alpha.
1252 o Minor bugfixes (testing):
1253 - Stop spawn test failures due to a race condition between the
1254 SIGCHLD handler updating the process status, and the test reading
1255 it. Fixes bug 13291; bugfix on 0.2.3.3-alpha.
1257 o Minor bugfixes (testing, Windows):
1258 - Avoid passing an extra backslash when creating a temporary
1259 directory for running the unit tests on Windows. Fixes bug 12392;
1260 bugfix on 0.2.2.25-alpha. Patch from Gisle Vanem.
1262 o Minor bugfixes (windows):
1263 - Remove code to special-case handling of NTE_BAD_KEYSET when
1264 acquiring windows CryptoAPI context. This error can't actually
1265 occur for the parameters we're providing. Fixes bug 10816; bugfix
1268 o Minor bugfixes (zlib):
1269 - Avoid truncating a zlib stream when trying to finalize it with an
1270 empty output buffer. Fixes bug 11824; bugfix on 0.1.1.23.
1273 - Allow our configure script to build correctly with autoconf 2.62
1274 again. Fixes bug 12693; bugfix on 0.2.5.2-alpha.
1275 - Improve the error message from ./configure to make it clear that
1276 when asciidoc has not been found, the user will have to either add
1277 --disable-asciidoc argument or install asciidoc. Resolves
1280 o Code simplification and refactoring:
1281 - Change the entry_is_live() function to take named bitfield
1282 elements instead of an unnamed list of booleans. Closes
1284 - Refactor and unit-test entry_is_time_to_retry() in entrynodes.c.
1285 Resolves ticket 12205.
1286 - Use calloc and reallocarray functions instead of multiply-
1287 then-malloc. This makes it less likely for us to fall victim to an
1288 integer overflow attack when allocating. Resolves ticket 12855.
1289 - Use the standard macro name SIZE_MAX, instead of our
1291 - Document usage of the NO_DIRINFO and ALL_DIRINFO flags clearly in
1292 functions which take them as arguments. Replace 0 with NO_DIRINFO
1293 in a function call for clarity. Seeks to prevent future issues
1295 - Avoid 4 null pointer errors under clang static analysis by using
1296 tor_assert() to prove that the pointers aren't null. Fixes
1298 - Rework the API of policies_parse_exit_policy() to use a bitmask to
1299 represent parsing options, instead of a confusing mess of
1300 booleans. Resolves ticket 8197.
1301 - Introduce a helper function to parse ExitPolicy in
1302 or_options_t structure.
1305 - Add a doc/TUNING document with tips for handling large numbers of
1306 TCP connections when running busy Tor relay. Update the warning
1307 message to point to this file when running out of sockets
1308 operating system is allowing to use simultaneously. Resolves
1312 - We no longer remind the user about configuration options that have
1313 been obsolete since 0.2.3.x or earlier. Patch by Adrien Bak.
1314 - Remove our old, non-weighted bandwidth-based node selection code.
1315 Previously, we used it as a fallback when we couldn't perform
1316 weighted bandwidth-based node selection. But that would only
1317 happen in the cases where we had no consensus, or when we had a
1318 consensus generated by buggy or ancient directory authorities. In
1319 either case, it's better to use the more modern, better maintained
1320 algorithm, with reasonable defaults for the weights. Closes
1322 - Remove the --disable-curve25519 configure option. Relays and
1323 clients now are required to support curve25519 and the
1325 - The old "StrictEntryNodes" and "StrictExitNodes" options, which
1326 used to be deprecated synonyms for "StrictNodes", are now marked
1327 obsolete. Resolves ticket 12226.
1328 - Clients don't understand the BadDirectory flag in the consensus
1329 anymore, and ignore it.
1332 - Refactor the function that chooses guard nodes so that it can more
1333 easily be tested; write some tests for it.
1334 - Fix and re-enable the fgets_eagain unit test. Fixes bug 12503;
1335 bugfix on 0.2.3.1-alpha. Patch from "cypherpunks."
1336 - Create unit tests for format_time_interval(). With bug 13393.
1337 - Add unit tests for tor_timegm signed overflow, tor_timegm and
1338 parse_rfc1123_time validity checks, correct_tm year clamping. Unit
1339 tests (visible) fixes in bug 13476.
1340 - Add a "coverage-html" make target to generate HTML-visualized
1341 coverage results when building with --enable-coverage. (Requires
1342 lcov.) Patch from Kevin Murray.
1343 - Enable the backtrace handler (where supported) when running the
1345 - Revise all unit tests that used the legacy test_* macros to
1346 instead use the recommended tt_* macros. This patch was generated
1347 with coccinelle, to avoid manual errors. Closes ticket 13119.
1349 o Distribution (systemd):
1350 - systemd unit file: only allow tor to write to /var/lib/tor and
1351 /var/log/tor. The rest of the filesystem is accessible for reading
1352 only. Patch by intrigeri; resolves ticket 12751.
1353 - systemd unit file: ensure that the process and all its children
1354 can never gain new privileges. Patch by intrigeri; resolves
1356 - systemd unit file: set up /var/run/tor as writable for the Tor
1357 service. Patch by intrigeri; resolves ticket 13196.
1359 o Removed features (directory authorities):
1360 - Remove code that prevented authorities from listing Tor relays
1361 affected by CVE-2011-2769 as guards. These relays are already
1362 rejected altogether due to the minimum version requirement of
1363 0.2.3.16-alpha. Closes ticket 13152.
1364 - The "AuthDirRejectUnlisted" option no longer has any effect, as
1365 the fingerprints file (approved-routers) has been deprecated.
1366 - Directory authorities do not support being Naming dirauths anymore.
1367 The "NamingAuthoritativeDir" config option is now obsolete.
1368 - Directory authorities do not support giving out the BadDirectory
1370 - Directory authorities no longer advertise or support consensus
1371 methods 1 through 12 inclusive. These consensus methods were
1372 obsolete and/or insecure: maintaining the ability to support them
1373 served no good purpose. Implements part of proposal 215; closes
1376 o Testing (test-network.sh):
1377 - Stop using "echo -n", as some shells' built-in echo doesn't
1378 support "-n". Instead, use "/bin/echo -n". Partially fixes
1380 - Stop an apparent test-network hang when used with make -j2. Fixes
1382 - Add a --delay option to test-network.sh, which configures the
1383 delay before the chutney network tests for data transmission.
1384 Partially implements ticket 13161.
1387 Changes in version 0.2.5.10 - 2014-10-24
1388 Tor 0.2.5.10 is the first stable release in the 0.2.5 series.
1390 It adds several new security features, including improved
1391 denial-of-service resistance for relays, new compiler hardening
1392 options, and a system-call sandbox for hardened installations on Linux
1393 (requires seccomp2). The controller protocol has several new features,
1394 resolving IPv6 addresses should work better than before, and relays
1395 should be a little more CPU-efficient. We've added support for more
1396 OpenBSD and FreeBSD transparent proxy types. We've improved the build
1397 system and testing infrastructure to allow unit testing of more parts
1398 of the Tor codebase. Finally, we've addressed several nagging pluggable
1399 transport usability issues, and included numerous other small bugfixes
1400 and features mentioned below.
1402 This release marks end-of-life for Tor 0.2.3.x; those Tor versions
1403 have accumulated many known flaws; everyone should upgrade.
1405 o Deprecated versions:
1406 - Tor 0.2.3.x has reached end-of-life; it has received no patches or
1407 attention for some while.
1410 Changes in version 0.2.5.9-rc - 2014-10-20
1411 Tor 0.2.5.9-rc is the third release candidate for the Tor 0.2.5.x
1412 series. It disables SSL3 in response to the recent "POODLE" attack
1413 (even though POODLE does not affect Tor). It also works around a crash
1414 bug caused by some operating systems' response to the "POODLE" attack
1415 (which does affect Tor). It also contains a few miscellaneous fixes.
1417 o Major security fixes:
1418 - Disable support for SSLv3. All versions of OpenSSL in use with Tor
1419 today support TLS 1.0 or later, so we can safely turn off support
1420 for this old (and insecure) protocol. Fixes bug 13426.
1422 o Major bugfixes (openssl bug workaround):
1423 - Avoid crashing when using OpenSSL version 0.9.8zc, 1.0.0o, or
1424 1.0.1j, built with the 'no-ssl3' configuration option. Fixes bug
1425 13471. This is a workaround for an OpenSSL bug.
1428 - Disable the sandbox name resolver cache when running tor-resolve:
1429 tor-resolve doesn't use the sandbox code, and turning it on was
1430 breaking attempts to do tor-resolve on a non-default server on
1431 Linux. Fixes bug 13295; bugfix on 0.2.5.3-alpha.
1433 o Compilation fixes:
1434 - Build and run correctly on systems like OpenBSD-current that have
1435 patched OpenSSL to remove get_cipher_by_char and/or its
1436 implementations. Fixes issue 13325.
1438 o Downgraded warnings:
1439 - Downgrade the severity of the 'unexpected sendme cell from client'
1440 from 'warn' to 'protocol warning'. Closes ticket 8093.
1443 Changes in version 0.2.4.25 - 2014-10-20
1444 Tor 0.2.4.25 disables SSL3 in response to the recent "POODLE" attack
1445 (even though POODLE does not affect Tor). It also works around a crash
1446 bug caused by some operating systems' response to the "POODLE" attack
1447 (which does affect Tor).
1449 o Major security fixes (also in 0.2.5.9-rc):
1450 - Disable support for SSLv3. All versions of OpenSSL in use with Tor
1451 today support TLS 1.0 or later, so we can safely turn off support
1452 for this old (and insecure) protocol. Fixes bug 13426.
1454 o Major bugfixes (openssl bug workaround, also in 0.2.5.9-rc):
1455 - Avoid crashing when using OpenSSL version 0.9.8zc, 1.0.0o, or
1456 1.0.1j, built with the 'no-ssl3' configuration option. Fixes bug
1457 13471. This is a workaround for an OpenSSL bug.
1460 Changes in version 0.2.5.8-rc - 2014-09-22
1461 Tor 0.2.5.8-rc is the second release candidate for the Tor 0.2.5.x
1462 series. It fixes a bug that affects consistency and speed when
1463 connecting to hidden services, and it updates the location of one of
1464 the directory authorities.
1467 - Clients now send the correct address for their chosen rendezvous
1468 point when trying to access a hidden service. They used to send
1469 the wrong address, which would still work some of the time because
1470 they also sent the identity digest of the rendezvous point, and if
1471 the hidden service happened to try connecting to the rendezvous
1472 point from a relay that already had a connection open to it,
1473 the relay would reuse that connection. Now connections to hidden
1474 services should be more robust and faster. Also, this bug meant
1475 that clients were leaking to the hidden service whether they were
1476 on a little-endian (common) or big-endian (rare) system, which for
1477 some users might have reduced their anonymity. Fixes bug 13151;
1478 bugfix on 0.2.1.5-alpha.
1480 o Directory authority changes:
1481 - Change IP address for gabelmoo (v3 directory authority).
1484 Changes in version 0.2.4.24 - 2014-09-22
1485 Tor 0.2.4.24 fixes a bug that affects consistency and speed when
1486 connecting to hidden services, and it updates the location of one of
1487 the directory authorities.
1490 - Clients now send the correct address for their chosen rendezvous
1491 point when trying to access a hidden service. They used to send
1492 the wrong address, which would still work some of the time because
1493 they also sent the identity digest of the rendezvous point, and if
1494 the hidden service happened to try connecting to the rendezvous
1495 point from a relay that already had a connection open to it,
1496 the relay would reuse that connection. Now connections to hidden
1497 services should be more robust and faster. Also, this bug meant
1498 that clients were leaking to the hidden service whether they were
1499 on a little-endian (common) or big-endian (rare) system, which for
1500 some users might have reduced their anonymity. Fixes bug 13151;
1501 bugfix on 0.2.1.5-alpha.
1503 o Directory authority changes:
1504 - Change IP address for gabelmoo (v3 directory authority).
1506 o Minor features (geoip):
1507 - Update geoip and geoip6 to the August 7 2014 Maxmind GeoLite2
1511 Changes in version 0.2.5.7-rc - 2014-09-11
1512 Tor 0.2.5.7-rc fixes several regressions from earlier in the 0.2.5.x
1513 release series, and some long-standing bugs related to ORPort reachability
1514 testing and failure to send CREATE cells. It is the first release
1515 candidate for the Tor 0.2.5.x series.
1517 o Major bugfixes (client, startup):
1518 - Start making circuits as soon as DisabledNetwork is turned off.
1519 When Tor started with DisabledNetwork set, it would correctly
1520 conclude that it shouldn't build circuits, but it would mistakenly
1521 cache this conclusion, and continue believing it even when
1522 DisableNetwork is set to 0. Fixes the bug introduced by the fix
1523 for bug 11200; bugfix on 0.2.5.4-alpha.
1524 - Resume expanding abbreviations for command-line options. The fix
1525 for bug 4647 accidentally removed our hack from bug 586 that
1526 rewrote HashedControlPassword to __HashedControlSessionPassword
1527 when it appears on the commandline (which allowed the user to set
1528 her own HashedControlPassword in the torrc file while the
1529 controller generates a fresh session password for each run). Fixes
1530 bug 12948; bugfix on 0.2.5.1-alpha.
1531 - Warn about attempts to run hidden services and relays in the same
1532 process: that's probably not a good idea. Closes ticket 12908.
1534 o Major bugfixes (relay):
1535 - Avoid queuing or sending destroy cells for circuit ID zero when we
1536 fail to send a CREATE cell. Fixes bug 12848; bugfix on 0.0.8pre1.
1537 Found and fixed by "cypherpunks".
1538 - Fix ORPort reachability detection on relays running behind a
1539 proxy, by correctly updating the "local" mark on the controlling
1540 channel when changing the address of an or_connection_t after the
1541 handshake. Fixes bug 12160; bugfix on 0.2.4.4-alpha.
1543 o Minor features (bridge):
1544 - Add an ExtORPortCookieAuthFileGroupReadable option to make the
1545 cookie file for the ExtORPort g+r by default.
1547 o Minor features (geoip):
1548 - Update geoip and geoip6 to the August 7 2014 Maxmind GeoLite2
1551 o Minor bugfixes (logging):
1552 - Reduce the log severity of the "Pluggable transport proxy does not
1553 provide any needed transports and will not be launched." message,
1554 since Tor Browser includes several ClientTransportPlugin lines in
1555 its torrc-defaults file, leading every Tor Browser user who looks
1556 at her logs to see these notices and wonder if they're dangerous.
1557 Resolves bug 13124; bugfix on 0.2.5.3-alpha.
1558 - Downgrade "Unexpected onionskin length after decryption" warning
1559 to a protocol-warn, since there's nothing relay operators can do
1560 about a client that sends them a malformed create cell. Resolves
1561 bug 12996; bugfix on 0.0.6rc1.
1562 - Log more specific warnings when we get an ESTABLISH_RENDEZVOUS
1563 cell on a cannibalized or non-OR circuit. Resolves ticket 12997.
1564 - When logging information about an EXTEND2 or EXTENDED2 cell, log
1565 their names correctly. Fixes part of bug 12700; bugfix
1567 - When logging information about a relay cell whose command we don't
1568 recognize, log its command as an integer. Fixes part of bug 12700;
1569 bugfix on 0.2.1.10-alpha.
1570 - Escape all strings from the directory connection before logging
1571 them. Fixes bug 13071; bugfix on 0.1.1.15. Patch from "teor".
1573 o Minor bugfixes (controller):
1574 - Restore the functionality of CookieAuthFileGroupReadable. Fixes
1575 bug 12864; bugfix on 0.2.5.1-alpha.
1576 - Actually send TRANSPORT_LAUNCHED and HS_DESC events to
1577 controllers. Fixes bug 13085; bugfix on 0.2.5.1-alpha. Patch
1580 o Minor bugfixes (compilation):
1581 - Fix compilation of test.h with MSVC. Patch from Gisle Vanem;
1582 bugfix on 0.2.5.5-alpha.
1583 - Make the nmake make files work again. Fixes bug 13081. Bugfix on
1584 0.2.5.1-alpha. Patch from "NewEraCracker".
1585 - In routerlist_assert_ok(), don't take the address of a
1586 routerinfo's cache_info member unless that routerinfo is non-NULL.
1587 Fixes bug 13096; bugfix on 0.1.1.9-alpha. Patch by "teor".
1588 - Fix a large number of false positive warnings from the clang
1589 analyzer static analysis tool. This should make real warnings
1590 easier for clang analyzer to find. Patch from "teor". Closes
1593 o Distribution (systemd):
1594 - Verify configuration file via ExecStartPre in the systemd unit
1595 file. Patch from intrigeri; resolves ticket 12730.
1596 - Explicitly disable RunAsDaemon in the systemd unit file. Our
1597 current systemd unit uses "Type = simple", so systemd does not
1598 expect tor to fork. If the user has "RunAsDaemon 1" in their
1599 torrc, then things won't work as expected. This is e.g. the case
1600 on Debian (and derivatives), since there we pass "--defaults-torrc
1601 /usr/share/tor/tor-service-defaults-torrc" (that contains
1602 "RunAsDaemon 1") by default. Patch by intrigeri; resolves
1606 - Adjust the URLs in the README to refer to the new locations of
1607 several documents on the website. Fixes bug 12830. Patch from
1609 - Document 'reject6' and 'accept6' ExitPolicy entries. Resolves
1613 Changes in version 0.2.5.6-alpha - 2014-07-28
1614 Tor 0.2.5.6-alpha brings us a big step closer to slowing down the
1615 risk from guard rotation, and fixes a variety of other issues to get
1616 us closer to a release candidate.
1618 o Major features (also in 0.2.4.23):
1619 - Make the number of entry guards configurable via a new
1620 NumEntryGuards consensus parameter, and the number of directory
1621 guards configurable via a new NumDirectoryGuards consensus
1622 parameter. Implements ticket 12688.
1624 o Major bugfixes (also in 0.2.4.23):
1625 - Fix a bug in the bounds-checking in the 32-bit curve25519-donna
1626 implementation that caused incorrect results on 32-bit
1627 implementations when certain malformed inputs were used along with
1628 a small class of private ntor keys. This bug does not currently
1629 appear to allow an attacker to learn private keys or impersonate a
1630 Tor server, but it could provide a means to distinguish 32-bit Tor
1631 implementations from 64-bit Tor implementations. Fixes bug 12694;
1632 bugfix on 0.2.4.8-alpha. Bug found by Robert Ransom; fix from
1636 - Perform circuit cleanup operations even when circuit
1637 construction operations are disabled (because the network is
1638 disabled, or because there isn't enough directory information).
1639 Previously, when we were not building predictive circuits, we
1640 were not closing expired circuits either. Fixes bug 8387; bugfix on
1641 0.1.1.11-alpha. This bug became visible in 0.2.4.10-alpha when we
1642 became more strict about when we have "enough directory information
1646 - Authorities now assign the Guard flag to the fastest 25% of the
1647 network (it used to be the fastest 50%). Also raise the consensus
1648 weight that guarantees the Guard flag from 250 to 2000. For the
1649 current network, this results in about 1100 guards, down from 2500.
1650 This step paves the way for moving the number of entry guards
1651 down to 1 (proposal 236) while still providing reasonable expected
1652 performance for most users. Implements ticket 12690.
1653 - Update geoip and geoip6 to the July 10 2014 Maxmind GeoLite2
1655 - Slightly enhance the diagnostic message for bug 12184.
1657 o Minor bugfixes (also in 0.2.4.23):
1658 - Warn and drop the circuit if we receive an inbound 'relay early'
1659 cell. Those used to be normal to receive on hidden service circuits
1660 due to bug 1038, but the buggy Tor versions are long gone from
1661 the network so we can afford to resume watching for them. Resolves
1662 the rest of bug 1038; bugfix on 0.2.1.19.
1663 - Correct a confusing error message when trying to extend a circuit
1664 via the control protocol but we don't know a descriptor or
1665 microdescriptor for one of the specified relays. Fixes bug 12718;
1666 bugfix on 0.2.3.1-alpha.
1669 - Fix compilation when building with bufferevents enabled. (This
1670 configuration is still not expected to work, however.)
1671 Fixes bugs 12438, 12474, 11578; bugfixes on 0.2.5.1-alpha and
1672 0.2.5.3-alpha. Patches from Anthony G. Basile and Sathyanarayanan
1674 - Compile correctly with builds and forks of OpenSSL (such as
1675 LibreSSL) that disable compression. Fixes bug 12602; bugfix on
1676 0.2.1.1-alpha. Patch from "dhill".
1679 Changes in version 0.2.4.23 - 2014-07-28
1680 Tor 0.2.4.23 brings us a big step closer to slowing down the risk from
1681 guard rotation, and also backports several important fixes from the
1682 Tor 0.2.5 alpha release series.
1685 - Clients now look at the "usecreatefast" consensus parameter to
1686 decide whether to use CREATE_FAST or CREATE cells for the first hop
1687 of their circuit. This approach can improve security on connections
1688 where Tor's circuit handshake is stronger than the available TLS
1689 connection security levels, but the tradeoff is more computational
1690 load on guard relays. Implements proposal 221. Resolves ticket 9386.
1691 - Make the number of entry guards configurable via a new
1692 NumEntryGuards consensus parameter, and the number of directory
1693 guards configurable via a new NumDirectoryGuards consensus
1694 parameter. Implements ticket 12688.
1697 - Fix a bug in the bounds-checking in the 32-bit curve25519-donna
1698 implementation that caused incorrect results on 32-bit
1699 implementations when certain malformed inputs were used along with
1700 a small class of private ntor keys. This bug does not currently
1701 appear to allow an attacker to learn private keys or impersonate a
1702 Tor server, but it could provide a means to distinguish 32-bit Tor
1703 implementations from 64-bit Tor implementations. Fixes bug 12694;
1704 bugfix on 0.2.4.8-alpha. Bug found by Robert Ransom; fix from
1708 - Warn and drop the circuit if we receive an inbound 'relay early'
1709 cell. Those used to be normal to receive on hidden service circuits
1710 due to bug 1038, but the buggy Tor versions are long gone from
1711 the network so we can afford to resume watching for them. Resolves
1712 the rest of bug 1038; bugfix on 0.2.1.19.
1713 - Correct a confusing error message when trying to extend a circuit
1714 via the control protocol but we don't know a descriptor or
1715 microdescriptor for one of the specified relays. Fixes bug 12718;
1716 bugfix on 0.2.3.1-alpha.
1717 - Avoid an illegal read from stack when initializing the TLS
1718 module using a version of OpenSSL without all of the ciphers
1719 used by the v2 link handshake. Fixes bug 12227; bugfix on
1720 0.2.4.8-alpha. Found by "starlight".
1723 - Update geoip and geoip6 to the July 10 2014 Maxmind GeoLite2
1727 Changes in version 0.2.5.5-alpha - 2014-06-18
1728 Tor 0.2.5.5-alpha fixes a wide variety of remaining issues in the Tor
1729 0.2.5.x release series, including a couple of DoS issues, some
1730 performance regressions, a large number of bugs affecting the Linux
1731 seccomp2 sandbox code, and various other bugfixes. It also adds
1732 diagnostic bugfixes for a few tricky issues that we're trying to
1735 o Major features (security, traffic analysis resistance):
1736 - Several major improvements to the algorithm used to decide when to
1737 close TLS connections. Previous versions of Tor closed connections
1738 at a fixed interval after the last time a non-padding cell was
1739 sent over the connection, regardless of the target of the
1740 connection. Now, we randomize the intervals by adding up to 50% of
1741 their base value, we measure the length of time since connection
1742 last had at least one circuit, and we allow connections to known
1743 ORs to remain open a little longer (15 minutes instead of 3
1744 minutes minimum). These changes should improve Tor's resistance
1745 against some kinds of traffic analysis, and lower some overhead
1746 from needlessly closed connections. Fixes ticket 6799.
1747 Incidentally fixes ticket 12023; bugfix on 0.2.5.1-alpha.
1749 o Major bugfixes (security, OOM, new since 0.2.5.4-alpha, also in 0.2.4.22):
1750 - Fix a memory leak that could occur if a microdescriptor parse
1751 fails during the tokenizing step. This bug could enable a memory
1752 exhaustion attack by directory servers. Fixes bug 11649; bugfix
1755 o Major bugfixes (security, directory authorities):
1756 - Directory authorities now include a digest of each relay's
1757 identity key as a part of its microdescriptor.
1759 This is a workaround for bug 11743 (reported by "cypherpunks"),
1760 where Tor clients do not support receiving multiple
1761 microdescriptors with the same SHA256 digest in the same
1762 consensus. When clients receive a consensus like this, they only
1763 use one of the relays. Without this fix, a hostile relay could
1764 selectively disable some client use of target relays by
1765 constructing a router descriptor with a different identity and the
1766 same microdescriptor parameters and getting the authorities to
1767 list it in a microdescriptor consensus. This fix prevents an
1768 attacker from causing a microdescriptor collision, because the
1769 router's identity is not forgeable.
1771 o Major bugfixes (relay):
1772 - Use a direct dirport connection when uploading non-anonymous
1773 descriptors to the directory authorities. Previously, relays would
1774 incorrectly use tunnel connections under a fairly wide variety of
1775 circumstances. Fixes bug 11469; bugfix on 0.2.4.3-alpha.
1776 - When a circuit accidentally has the same circuit ID for its
1777 forward and reverse direction, correctly detect the direction of
1778 cells using that circuit. Previously, this bug made roughly one
1779 circuit in a million non-functional. Fixes bug 12195; this is a
1780 bugfix on every version of Tor.
1782 o Major bugfixes (client, pluggable transports):
1783 - When managing pluggable transports, use OS notification facilities
1784 to learn if they have crashed, and don't attempt to kill any
1785 process that has already exited. Fixes bug 8746; bugfix
1788 o Minor features (diagnostic):
1789 - When logging a warning because of bug 7164, additionally check the
1790 hash table for consistency (as proposed on ticket 11737). This may
1791 help diagnose bug 7164.
1792 - When we log a heartbeat, log how many one-hop circuits we have
1793 that are at least 30 minutes old, and log status information about
1794 a few of them. This is an attempt to track down bug 8387.
1795 - When encountering an unexpected CR while writing text to a file on
1796 Windows, log the name of the file. Should help diagnosing
1798 - Give more specific warnings when a client notices that an onion
1799 handshake has failed. Fixes ticket 9635.
1800 - Add significant new logging code to attempt to diagnose bug 12184,
1801 where relays seem to run out of available circuit IDs.
1802 - Improve the diagnostic log message for bug 8387 even further to
1803 try to improve our odds of figuring out why one-hop directory
1804 circuits sometimes do not get closed.
1806 o Minor features (security, memory management):
1807 - Memory allocation tricks (mempools and buffer freelists) are now
1808 disabled by default. You can turn them back on with
1809 --enable-mempools and --enable-buf-freelists respectively. We're
1810 disabling these features because malloc performance is good enough
1811 on most platforms, and a similar feature in OpenSSL exacerbated
1812 exploitation of the Heartbleed attack. Resolves ticket 11476.
1814 o Minor features (security):
1815 - Apply the secure SipHash-2-4 function to the hash table mapping
1816 circuit IDs and channels to circuits. We missed this one when we
1817 were converting all the other hash functions to use SipHash back
1818 in 0.2.5.3-alpha. Resolves ticket 11750.
1820 o Minor features (build):
1821 - The configure script has a --disable-seccomp option to turn off
1822 support for libseccomp on systems that have it, in case it (or
1823 Tor's use of it) is broken. Resolves ticket 11628.
1825 o Minor features (other):
1826 - Update geoip and geoip6 to the June 4 2014 Maxmind GeoLite2
1829 o Minor bugfixes (security, new since 0.2.5.4-alpha, also in 0.2.4.22):
1830 - When running a hidden service, do not allow TunneledDirConns 0;
1831 this will keep the hidden service from running, and also
1832 make it publish its descriptors directly over HTTP. Fixes bug 10849;
1833 bugfix on 0.2.1.1-alpha.
1835 o Minor bugfixes (performance):
1836 - Avoid a bug where every successful connection made us recompute
1837 the flag telling us whether we have sufficient information to
1838 build circuits. Previously, we would forget our cached value
1839 whenever we successfully opened a channel (or marked a router as
1840 running or not running for any other reason), regardless of
1841 whether we had previously believed the router to be running. This
1842 forced us to run an expensive update operation far too often.
1843 Fixes bug 12170; bugfix on 0.1.2.1-alpha.
1844 - Avoid using tor_memeq() for checking relay cell integrity. This
1845 removes a possible performance bottleneck. Fixes part of bug
1846 12169; bugfix on 0.2.1.31.
1848 o Minor bugfixes (compilation):
1849 - Fix compilation of test_status.c when building with MVSC. Bugfix
1850 on 0.2.5.4-alpha. Patch from Gisle Vanem.
1851 - Resolve GCC complaints on OpenBSD about discarding constness in
1852 TO_{ORIGIN,OR}_CIRCUIT functions. Fixes part of bug 11633; bugfix
1853 on 0.1.1.23. Patch from Dana Koch.
1854 - Resolve clang complaints on OpenBSD with -Wshorten-64-to-32 due to
1855 treatment of long and time_t as comparable types. Fixes part of
1856 bug 11633. Patch from Dana Koch.
1857 - Make Tor compile correctly with --disable-buf-freelists. Fixes bug
1858 11623; bugfix on 0.2.5.3-alpha.
1859 - When deciding whether to build the 64-bit curve25519
1860 implementation, detect platforms where we can compile 128-bit
1861 arithmetic but cannot link it. Fixes bug 11729; bugfix on
1862 0.2.4.8-alpha. Patch from "conradev".
1863 - Fix compilation when DNS_CACHE_DEBUG is enabled. Fixes bug 11761;
1864 bugfix on 0.2.3.13-alpha. Found by "cypherpunks".
1865 - Fix compilation with dmalloc. Fixes bug 11605; bugfix
1868 o Minor bugfixes (Directory server):
1869 - When sending a compressed set of descriptors or microdescriptors,
1870 make sure to finalize the zlib stream. Previously, we would write
1871 all the compressed data, but if the last descriptor we wanted to
1872 send was missing or too old, we would not mark the stream as
1873 finished. This caused problems for decompression tools. Fixes bug
1874 11648; bugfix on 0.1.1.23.
1876 o Minor bugfixes (Linux seccomp sandbox):
1877 - Make the seccomp sandbox code compile under ARM Linux. Fixes bug
1878 11622; bugfix on 0.2.5.1-alpha.
1879 - Avoid crashing when re-opening listener ports with the seccomp
1880 sandbox active. Fixes bug 12115; bugfix on 0.2.5.1-alpha.
1881 - Avoid crashing with the seccomp sandbox enabled along with
1882 ConstrainedSockets. Fixes bug 12139; bugfix on 0.2.5.1-alpha.
1883 - When we receive a SIGHUP with the sandbox enabled, correctly
1884 support rotating our log files. Fixes bug 12032; bugfix
1886 - Avoid crash when running with sandboxing enabled and
1887 DirReqStatistics not disabled. Fixes bug 12035; bugfix
1889 - Fix a "BUG" warning when trying to write bridge-stats files with
1890 the Linux syscall sandbox filter enabled. Fixes bug 12041; bugfix
1892 - Prevent the sandbox from crashing on startup when run with the
1893 --enable-expensive-hardening configuration option. Fixes bug
1894 11477; bugfix on 0.2.5.4-alpha.
1895 - When running with DirPortFrontPage and sandboxing both enabled,
1896 reload the DirPortFrontPage correctly when restarting. Fixes bug
1897 12028; bugfix on 0.2.5.1-alpha.
1898 - Don't try to enable the sandbox when using the Tor binary to check
1899 its configuration, hash a passphrase, or so on. Doing so was
1900 crashing on startup for some users. Fixes bug 11609; bugfix
1902 - Avoid warnings when running with sandboxing and node statistics
1903 enabled at the same time. Fixes part of 12064; bugfix on
1904 0.2.5.1-alpha. Patch from Michael Wolf.
1905 - Avoid warnings when running with sandboxing enabled at the same
1906 time as cookie authentication, hidden services, or directory
1907 authority voting. Fixes part of 12064; bugfix on 0.2.5.1-alpha.
1908 - Do not allow options that require calls to exec to be enabled
1909 alongside the seccomp2 sandbox: they will inevitably crash. Fixes
1910 bug 12043; bugfix on 0.2.5.1-alpha.
1911 - Handle failures in getpwnam()/getpwuid() when running with the
1912 User option set and the Linux syscall sandbox enabled. Fixes bug
1913 11946; bugfix on 0.2.5.1-alpha.
1914 - Refactor the getaddrinfo workaround that the seccomp sandbox uses
1915 to avoid calling getaddrinfo() after installing the sandbox
1916 filters. Previously, it preloaded a cache with the IPv4 address
1917 for our hostname, and nothing else. Now, it loads the cache with
1918 every address that it used to initialize the Tor process. Fixes
1919 bug 11970; bugfix on 0.2.5.1-alpha.
1921 o Minor bugfixes (pluggable transports):
1922 - Enable the ExtORPortCookieAuthFile option, to allow changing the
1923 default location of the authentication token for the extended OR
1924 Port as used by sever-side pluggable transports. We had
1925 implemented this option before, but the code to make it settable
1926 had been omitted. Fixes bug 11635; bugfix on 0.2.5.1-alpha.
1927 - Avoid another 60-second delay when starting Tor in a pluggable-
1928 transport-using configuration when we already have cached
1929 descriptors for our bridges. Fixes bug 11965; bugfix
1932 o Minor bugfixes (client):
1933 - Avoid "Tried to open a socket with DisableNetwork set" warnings
1934 when starting a client with bridges configured and DisableNetwork
1935 set. (Tor launcher starts Tor with DisableNetwork set the first
1936 time it runs.) Fixes bug 10405; bugfix on 0.2.3.9-alpha.
1938 o Minor bugfixes (testing):
1939 - The Python parts of the test scripts now work on Python 3 as well
1940 as Python 2, so systems where '/usr/bin/python' is Python 3 will
1941 no longer have the tests break. Fixes bug 11608; bugfix
1943 - When looking for versions of python that we could run the tests
1944 with, check for "python2.7" and "python3.3"; previously we were
1945 only looking for "python", "python2", and "python3". Patch from
1946 Dana Koch. Fixes bug 11632; bugfix on 0.2.5.2-alpha.
1947 - Fix all valgrind warnings produced by the unit tests. There were
1948 over a thousand memory leak warnings previously, mostly produced
1949 by forgetting to free things in the unit test code. Fixes bug
1950 11618, bugfixes on many versions of Tor.
1952 o Minor bugfixes (tor-fw-helper):
1953 - Give a correct log message when tor-fw-helper fails to launch.
1954 (Previously, we would say something like "tor-fw-helper sent us a
1955 string we could not parse".) Fixes bug 9781; bugfix
1958 o Minor bugfixes (relay, threading):
1959 - Check return code on spawn_func() in cpuworker code, so that we
1960 don't think we've spawned a nonworking cpuworker and write junk to
1961 it forever. Fix related to bug 4345; bugfix on all released Tor
1962 versions. Found by "skruffy".
1963 - Use a pthread_attr to make sure that spawn_func() cannot return an
1964 error while at the same time launching a thread. Fix related to
1965 bug 4345; bugfix on all released Tor versions. Reported
1968 o Minor bugfixes (relay, oom prevention):
1969 - Correctly detect the total available system memory. We tried to do
1970 this in 0.2.5.4-alpha, but the code was set up to always return an
1971 error value, even on success. Fixes bug 11805; bugfix
1974 o Minor bugfixes (relay, other):
1975 - We now drop CREATE cells for already-existent circuit IDs and for
1976 zero-valued circuit IDs, regardless of other factors that might
1977 otherwise have called for DESTROY cells. Fixes bug 12191; bugfix
1979 - Avoid an illegal read from stack when initializing the TLS module
1980 using a version of OpenSSL without all of the ciphers used by the
1981 v2 link handshake. Fixes bug 12227; bugfix on 0.2.4.8-alpha. Found
1983 - When rejecting DATA cells for stream_id zero, still count them
1984 against the circuit's deliver window so that we don't fail to send
1985 a SENDME. Fixes bug 11246; bugfix on 0.2.4.10-alpha.
1987 o Minor bugfixes (logging):
1988 - Fix a misformatted log message about delayed directory fetches.
1989 Fixes bug 11654; bugfix on 0.2.5.3-alpha.
1990 - Squelch a spurious LD_BUG message "No origin circuit for
1991 successful SOCKS stream" in certain hidden service failure cases;
1995 - Include a tor.service file in contrib/dist for use with systemd.
1996 Some distributions will be able to use this file unmodified;
1997 others will need to tweak it, or write their own. Patch from Jamie
1998 Nguyen; resolves ticket 8368.
2001 - Clean up several option names in the manpage to match their real
2002 names, add the missing documentation for a couple of testing and
2003 directory authority options, remove the documentation for a
2004 V2-directory fetching option that no longer exists. Resolves
2006 - Correct the documenation so that it lists the correct directory
2007 for the stats files. (They are in a subdirectory called "stats",
2009 - In the manpage, move more authority-only options into the
2010 directory authority section so that operators of regular directory
2011 caches don't get confused.
2014 - The contrib directory has been sorted and tidied. Before, it was
2015 an unsorted dumping ground for useful and not-so-useful things.
2016 Now, it is divided based on functionality, and the items which
2017 seemed to be nonfunctional or useless have been removed. Resolves
2018 ticket 8966; based on patches from "rl1987".
2021 - Remove /tor/dbg-stability.txt URL that was meant to help debug WFU
2022 and MTBF calculations, but that nobody was using. Fixes ticket 11742.
2023 - The TunnelDirConns and PreferTunnelledDirConns options no longer
2024 exist; tunneled directory connections have been available since
2025 0.1.2.5-alpha, and turning them off is not a good idea. This is a
2026 brute-force fix for 10849, where "TunnelDirConns 0" would break
2030 Changes in version 0.2.4.22 - 2014-05-16
2031 Tor 0.2.4.22 backports numerous high-priority fixes from the Tor 0.2.5
2032 alpha release series. These include blocking all authority signing
2033 keys that may have been affected by the OpenSSL "heartbleed" bug,
2034 choosing a far more secure set of TLS ciphersuites by default, closing
2035 a couple of memory leaks that could be used to run a target relay out
2036 of RAM, and several others.
2038 o Major features (security, backport from 0.2.5.4-alpha):
2039 - Block authority signing keys that were used on authorities
2040 vulnerable to the "heartbleed" bug in OpenSSL (CVE-2014-0160). (We
2041 don't have any evidence that these keys _were_ compromised; we're
2042 doing this to be prudent.) Resolves ticket 11464.
2044 o Major bugfixes (security, OOM):
2045 - Fix a memory leak that could occur if a microdescriptor parse
2046 fails during the tokenizing step. This bug could enable a memory
2047 exhaustion attack by directory servers. Fixes bug 11649; bugfix
2050 o Major bugfixes (TLS cipher selection, backport from 0.2.5.4-alpha):
2051 - The relay ciphersuite list is now generated automatically based on
2052 uniform criteria, and includes all OpenSSL ciphersuites with
2053 acceptable strength and forward secrecy. Previously, we had left
2054 some perfectly fine ciphersuites unsupported due to omission or
2055 typo. Resolves bugs 11513, 11492, 11498, 11499. Bugs reported by
2056 'cypherpunks'. Bugfix on 0.2.4.8-alpha.
2057 - Relays now trust themselves to have a better view than clients of
2058 which TLS ciphersuites are better than others. (Thanks to bug
2059 11513, the relay list is now well-considered, whereas the client
2060 list has been chosen mainly for anti-fingerprinting purposes.)
2061 Relays prefer: AES over 3DES; then ECDHE over DHE; then GCM over
2062 CBC; then SHA384 over SHA256 over SHA1; and last, AES256 over
2063 AES128. Resolves ticket 11528.
2064 - Clients now try to advertise the same list of ciphersuites as
2065 Firefox 28. This change enables selection of (fast) GCM
2066 ciphersuites, disables some strange old ciphers, and stops
2067 advertising the ECDH (not to be confused with ECDHE) ciphersuites.
2068 Resolves ticket 11438.
2070 o Minor bugfixes (configuration, security):
2071 - When running a hidden service, do not allow TunneledDirConns 0:
2072 trying to set that option together with a hidden service would
2073 otherwise prevent the hidden service from running, and also make
2074 it publish its descriptors directly over HTTP. Fixes bug 10849;
2075 bugfix on 0.2.1.1-alpha.
2077 o Minor bugfixes (controller, backport from 0.2.5.4-alpha):
2078 - Avoid sending a garbage value to the controller when a circuit is
2079 cannibalized. Fixes bug 11519; bugfix on 0.2.3.11-alpha.
2081 o Minor bugfixes (exit relay, backport from 0.2.5.4-alpha):
2082 - Stop leaking memory when we successfully resolve a PTR record.
2083 Fixes bug 11437; bugfix on 0.2.4.7-alpha.
2085 o Minor bugfixes (bridge client, backport from 0.2.5.4-alpha):
2086 - Avoid 60-second delays in the bootstrapping process when Tor is
2087 launching for a second time while using bridges. Fixes bug 9229;
2088 bugfix on 0.2.0.3-alpha.
2090 o Minor bugfixes (relays and bridges, backport from 0.2.5.4-alpha):
2091 - Give the correct URL in the warning message when trying to run a
2092 relay on an ancient version of Windows. Fixes bug 9393.
2094 o Minor bugfixes (compilation):
2095 - Fix a compilation error when compiling with --disable-curve25519.
2096 Fixes bug 9700; bugfix on 0.2.4.17-rc.
2099 - Downgrade the warning severity for the the "md was still
2100 referenced 1 node(s)" warning. Tor 0.2.5.4-alpha has better code
2101 for trying to diagnose this bug, and the current warning in
2102 earlier versions of tor achieves nothing useful. Addresses warning
2105 o Minor features (log verbosity, backport from 0.2.5.4-alpha):
2106 - When we run out of usable circuit IDs on a channel, log only one
2107 warning for the whole channel, and describe how many circuits
2108 there were on the channel. Fixes part of ticket 11553.
2110 o Minor features (security, backport from 0.2.5.4-alpha):
2111 - Decrease the lower limit of MaxMemInCellQueues to 256 MBytes (but
2112 leave the default at 8GBytes), to better support Raspberry Pi
2113 users. Fixes bug 9686; bugfix on 0.2.4.14-alpha.
2115 o Documentation (backport from 0.2.5.4-alpha):
2116 - Correctly document that we search for a system torrc file before
2117 looking in ~/.torrc. Fixes documentation side of 9213; bugfix on
2121 Changes in version 0.2.5.4-alpha - 2014-04-25
2122 Tor 0.2.5.4-alpha includes several security and performance
2123 improvements for clients and relays, including blacklisting authority
2124 signing keys that were used while susceptible to the OpenSSL
2125 "heartbleed" bug, fixing two expensive functions on busy relays,
2126 improved TLS ciphersuite preference lists, support for run-time
2127 hardening on compilers that support AddressSanitizer, and more work on
2128 the Linux sandbox code.
2130 There are also several usability fixes for clients (especially clients
2131 that use bridges), two new TransPort protocols supported (one on
2132 OpenBSD, one on FreeBSD), and various other bugfixes.
2134 This release marks end-of-life for Tor 0.2.2.x; those Tor versions
2135 have accumulated many known flaws; everyone should upgrade.
2137 o Major features (security):
2138 - If you don't specify MaxMemInQueues yourself, Tor now tries to
2139 pick a good value based on your total system memory. Previously,
2140 the default was always 8 GB. You can still override the default by
2141 setting MaxMemInQueues yourself. Resolves ticket 11396.
2142 - Block authority signing keys that were used on authorities
2143 vulnerable to the "heartbleed" bug in OpenSSL (CVE-2014-0160). (We
2144 don't have any evidence that these keys _were_ compromised; we're
2145 doing this to be prudent.) Resolves ticket 11464.
2147 o Major features (relay performance):
2148 - Speed up server-side lookups of rendezvous and introduction point
2149 circuits by using hashtables instead of linear searches. These
2150 functions previously accounted between 3 and 7% of CPU usage on
2151 some busy relays. Resolves ticket 9841.
2152 - Avoid wasting CPU when extending a circuit over a channel that is
2153 nearly out of circuit IDs. Previously, we would do a linear scan
2154 over possible circuit IDs before finding one or deciding that we
2155 had exhausted our possibilities. Now, we try at most 64 random
2156 circuit IDs before deciding that we probably won't succeed. Fixes
2157 a possible root cause of ticket 11553.
2159 o Major features (seccomp2 sandbox, Linux only):
2160 - The seccomp2 sandbox can now run a test network for multiple hours
2161 without crashing. The sandbox is still experimental, and more bugs
2162 will probably turn up. To try it, enable "Sandbox 1" on a Linux
2163 host. Resolves ticket 11351.
2164 - Strengthen sandbox code: the sandbox can now test the arguments
2165 for rename(), and blocks _sysctl() entirely. Resolves another part
2167 - When the sandbox blocks a system call, it now tries to log a stack
2168 trace before exiting. Resolves ticket 11465.
2170 o Major bugfixes (TLS cipher selection):
2171 - The relay ciphersuite list is now generated automatically based on
2172 uniform criteria, and includes all OpenSSL ciphersuites with
2173 acceptable strength and forward secrecy. Previously, we had left
2174 some perfectly fine ciphersuites unsupported due to omission or
2175 typo. Resolves bugs 11513, 11492, 11498, 11499. Bugs reported by
2176 'cypherpunks'. Bugfix on 0.2.4.8-alpha.
2177 - Relays now trust themselves to have a better view than clients of
2178 which TLS ciphersuites are better than others. (Thanks to bug
2179 11513, the relay list is now well-considered, whereas the client
2180 list has been chosen mainly for anti-fingerprinting purposes.)
2181 Relays prefer: AES over 3DES; then ECDHE over DHE; then GCM over
2182 CBC; then SHA384 over SHA256 over SHA1; and last, AES256 over
2183 AES128. Resolves ticket 11528.
2184 - Clients now try to advertise the same list of ciphersuites as
2185 Firefox 28. This change enables selection of (fast) GCM
2186 ciphersuites, disables some strange old ciphers, and stops
2187 advertising the ECDH (not to be confused with ECDHE) ciphersuites.
2188 Resolves ticket 11438.
2190 o Major bugfixes (bridge client):
2191 - Avoid 60-second delays in the bootstrapping process when Tor is
2192 launching for a second time while using bridges. Fixes bug 9229;
2193 bugfix on 0.2.0.3-alpha.
2195 o Minor features (transparent proxy, *BSD):
2196 - Support FreeBSD's ipfw firewall interface for TransPort ports on
2197 FreeBSD. To enable it, set "TransProxyType ipfw". Resolves ticket
2198 10267; patch from "yurivict".
2199 - Support OpenBSD's divert-to rules with the pf firewall for
2200 transparent proxy ports. To enable it, set "TransProxyType
2201 pf-divert". This allows Tor to run a TransPort transparent proxy
2202 port on OpenBSD 4.4 or later without root privileges. See the
2203 pf.conf(5) manual page for information on configuring pf to use
2204 divert-to rules. Closes ticket 10896; patch from Dana Koch.
2206 o Minor features (security):
2207 - New --enable-expensive-hardening option to enable security
2208 hardening options that consume nontrivial amounts of CPU and
2209 memory. Right now, this includes AddressSanitizer and UbSan, which
2210 are supported in newer versions of GCC and Clang. Closes ticket
2213 o Minor features (log verbosity):
2214 - Demote the message that we give when a flushing connection times
2215 out for too long from NOTICE to INFO. It was usually meaningless.
2216 Resolves ticket 5286.
2217 - Don't log so many notice-level bootstrapping messages at startup
2218 about downloading descriptors. Previously, we'd log a notice
2219 whenever we learned about more routers. Now, we only log a notice
2220 at every 5% of progress. Fixes bug 9963.
2221 - Warn less verbosely when receiving a malformed
2222 ESTABLISH_RENDEZVOUS cell. Fixes ticket 11279.
2223 - When we run out of usable circuit IDs on a channel, log only one
2224 warning for the whole channel, and describe how many circuits
2225 there were on the channel. Fixes part of ticket 11553.
2227 o Minor features (relay):
2228 - If a circuit timed out for at least 3 minutes, check if we have a
2229 new external IP address, and publish a new descriptor with the new
2230 IP address if it changed. Resolves ticket 2454.
2232 o Minor features (controller):
2233 - Make the entire exit policy available from the control port via
2234 GETINFO exit-policy/*. Implements enhancement 7952. Patch from
2236 - Because of the fix for ticket 11396, the real limit for memory
2237 usage may no longer match the configured MaxMemInQueues value. The
2238 real limit is now exposed via GETINFO limits/max-mem-in-queues.
2240 o Minor features (bridge client):
2241 - Report a more useful failure message when we can't connect to a
2242 bridge because we don't have the right pluggable transport
2243 configured. Resolves ticket 9665. Patch from Fábio J. Bertinatto.
2245 o Minor features (diagnostic):
2246 - Add more log messages to diagnose bug 7164, which causes
2247 intermittent "microdesc_free() called but md was still referenced"
2248 warnings. We now include more information, to figure out why we
2249 might be cleaning a microdescriptor for being too old if it's
2250 still referenced by a live node_t object.
2252 o Minor bugfixes (client, DNSPort):
2253 - When using DNSPort, try to respond to AAAA requests with AAAA
2254 answers. Previously, we hadn't looked at the request type when
2255 deciding which answer type to prefer. Fixes bug 10468; bugfix on
2257 - When receiving a DNS query for an unsupported record type, reply
2258 with no answer rather than with a NOTIMPL error. This behavior
2259 isn't correct either, but it will break fewer client programs, we
2260 hope. Fixes bug 10268; bugfix on 0.2.0.1-alpha. Original patch
2263 o Minor bugfixes (exit relay):
2264 - Stop leaking memory when we successfully resolve a PTR record.
2265 Fixes bug 11437; bugfix on 0.2.4.7-alpha.
2267 o Minor bugfixes (bridge client):
2268 - Stop accepting bridge lines containing hostnames. Doing so would
2269 cause clients to perform DNS requests on the hostnames, which was
2270 not sensible behavior. Fixes bug 10801; bugfix on 0.2.0.1-alpha.
2271 - Avoid a 60-second delay in the bootstrapping process when a Tor
2272 client with pluggable transports re-reads its configuration at
2273 just the wrong time. Re-fixes bug 11156; bugfix on 0.2.5.3-alpha.
2275 o Minor bugfixes (client, logging during bootstrap):
2276 - Warn only once if we start logging in an unsafe way. Previously,
2277 we complain as many times as we had problems. Fixes bug 9870;
2278 bugfix on 0.2.5.1-alpha.
2279 - Only report the first fatal bootstrap error on a given OR
2280 connection. This stops us from telling the controller bogus error
2281 messages like "DONE". Fixes bug 10431; bugfix on 0.2.1.1-alpha.
2282 - Be more helpful when trying to run sandboxed on Linux without
2283 libseccomp. Instead of saying "Sandbox is not implemented on this
2284 platform", we now explain that we need to be built with
2285 libseccomp. Fixes bug 11543; bugfix on 0.2.5.1-alpha.
2286 - Avoid generating spurious warnings when starting with
2287 DisableNetwork enabled. Fixes bug 11200 and bug 10405; bugfix on
2290 o Minor bugfixes (closing OR connections):
2291 - If write_to_buf() in connection_write_to_buf_impl_() ever fails,
2292 check if it's an or_connection_t and correctly call
2293 connection_or_close_for_error() rather than
2294 connection_mark_for_close() directly. Fixes bug 11304; bugfix on
2296 - When closing all connections on setting DisableNetwork to 1, use
2297 connection_or_close_normally() rather than closing OR connections
2298 out from under the channel layer. Fixes bug 11306; bugfix on
2301 o Minor bugfixes (controller):
2302 - Avoid sending a garbage value to the controller when a circuit is
2303 cannibalized. Fixes bug 11519; bugfix on 0.2.3.11-alpha.
2305 o Minor bugfixes (tor-fw-helper):
2306 - Allow tor-fw-helper to build again by adding src/ext to its
2307 CPPFLAGS. Fixes bug 11296; bugfix on 0.2.5.3-alpha.
2309 o Minor bugfixes (bridges):
2310 - Avoid potential crashes or bad behavior when launching a
2311 server-side managed proxy with ORPort or ExtORPort temporarily
2312 disabled. Fixes bug 9650; bugfix on 0.2.3.16-alpha.
2314 o Minor bugfixes (platform-specific):
2315 - Fix compilation on Solaris, which does not have <endian.h>. Fixes
2316 bug 11426; bugfix on 0.2.5.3-alpha.
2317 - When dumping a malformed directory object to disk, save it in
2318 binary mode on Windows, not text mode. Fixes bug 11342; bugfix on
2320 - Don't report failures from make_socket_reuseable() on incoming
2321 sockets on OSX: this can happen when incoming connections close
2322 early. Fixes bug 10081.
2324 o Minor bugfixes (trivial memory leaks):
2325 - Fix a small memory leak when signing a directory object. Fixes bug
2326 11275; bugfix on 0.2.4.13-alpha.
2327 - Free placeholder entries in our circuit table at exit; fixes a
2328 harmless memory leak. Fixes bug 11278; bugfix on 0.2.5.1-alpha.
2329 - Don't re-initialize a second set of OpenSSL mutexes when starting
2330 up. Previously, we'd make one set of mutexes, and then immediately
2331 replace them with another. Fixes bug 11726; bugfix on
2333 - Resolve some memory leaks found by coverity in the unit tests, on
2334 exit in tor-gencert, and on a failure to compute digests for our
2335 own keys when generating a v3 networkstatus vote. These leaks
2336 should never have affected anyone in practice.
2338 o Minor bugfixes (hidden service):
2339 - Only retry attempts to connect to a chosen rendezvous point 8
2340 times, not 30. Fixes bug 4241; bugfix on 0.1.0.1-rc.
2342 o Minor bugfixes (misc code correctness):
2343 - Fix various instances of undefined behavior in channeltls.c,
2344 tor_memmem(), and eventdns.c that would cause us to construct
2345 pointers to memory outside an allocated object. (These invalid
2346 pointers were not accessed, but C does not even allow them to
2347 exist.) Fixes bug 10363; bugfixes on 0.1.1.1-alpha, 0.1.2.1-alpha,
2348 0.2.0.10-alpha, and 0.2.3.6-alpha. Reported by "bobnomnom".
2349 - Use the AddressSanitizer and Ubsan sanitizers (in clang-3.4) to
2350 fix some miscellaneous errors in our tests and codebase. Fixes bug
2351 11232. Bugfixes on versions back as far as 0.2.1.11-alpha.
2352 - Always check return values for unlink, munmap, UnmapViewOfFile;
2353 check strftime return values more often. In some cases all we can
2354 do is report a warning, but this may help prevent deeper bugs from
2355 going unnoticed. Closes ticket 8787; bugfixes on many, many tor
2357 - Fix numerous warnings from the clang "scan-build" static analyzer.
2358 Some of these are programming style issues; some of them are false
2359 positives that indicated awkward code; some are undefined behavior
2360 cases related to constructing (but not using) invalid pointers;
2361 some are assumptions about API behavior; some are (harmlessly)
2362 logging sizeof(ptr) bytes from a token when sizeof(*ptr) would be
2363 correct; and one or two are genuine bugs that weren't reachable
2364 from the rest of the program. Fixes bug 8793; bugfixes on many,
2368 - Build the torify.1 manpage again. Previously, we were only trying
2369 to build it when also building tor-fw-helper. That's why we didn't
2370 notice that we'd broken the ability to build it. Fixes bug 11321;
2371 bugfix on 0.2.5.1-alpha.
2372 - Fix the layout of the SOCKSPort flags in the manpage. Fixes bug
2373 11061; bugfix on 0.2.4.7-alpha.
2374 - Correctly document that we search for a system torrc file before
2375 looking in ~/.torrc. Fixes documentation side of 9213; bugfix on
2377 - Resolve warnings from Doxygen.
2379 o Code simplifications and refactoring:
2380 - Remove is_internal_IP() function. Resolves ticket 4645.
2381 - Remove unused function circuit_dump_by_chan from circuitlist.c.
2382 Closes issue 9107; patch from "marek".
2383 - Change our use of the ENUM_BF macro to avoid declarations that
2386 o Deprecated versions:
2387 - Tor 0.2.2.x has reached end-of-life; it has received no patches or
2388 attention for some while. Directory authorities no longer accept
2389 descriptors from relays running any version of Tor prior to Tor
2390 0.2.3.16-alpha. Resolves ticket 11149.
2393 - New macros in test.h to simplify writing mock-functions for unit
2394 tests. Part of ticket 11507. Patch from Dana Koch.
2395 - Complete tests for the status.c module. Resolves ticket 11507.
2396 Patch from Dana Koch.
2399 - Remove all code for the long unused v1 directory protocol.
2400 Resolves ticket 11070.
2403 Changes in version 0.2.5.3-alpha - 2014-03-22
2404 Tor 0.2.5.3-alpha includes all the fixes from 0.2.4.21. It contains
2405 two new anti-DoS features for Tor relays, resolves a bug that kept
2406 SOCKS5 support for IPv6 from working, fixes several annoying usability
2407 issues for bridge users, and removes more old code for unused
2410 The Tor 0.2.5.x release series is now in patch-freeze: no feature
2411 patches not already written will be considered for inclusion in 0.2.5.x.
2413 o Major features (relay security, DoS-resistance):
2414 - When deciding whether we have run out of memory and we need to
2415 close circuits, also consider memory allocated in buffers for
2416 streams attached to each circuit.
2418 This change, which extends an anti-DoS feature introduced in
2419 0.2.4.13-alpha and improved in 0.2.4.14-alpha, lets Tor exit relays
2420 better resist more memory-based DoS attacks than before. Since the
2421 MaxMemInCellQueues option now applies to all queues, it is renamed
2422 to MaxMemInQueues. This feature fixes bug 10169.
2423 - Avoid hash-flooding denial-of-service attacks by using the secure
2424 SipHash-2-4 hash function for our hashtables. Without this
2425 feature, an attacker could degrade performance of a targeted
2426 client or server by flooding their data structures with a large
2427 number of entries to be stored at the same hash table position,
2428 thereby slowing down the Tor instance. With this feature, hash
2429 table positions are derived from a randomized cryptographic key,
2430 and an attacker cannot predict which entries will collide. Closes
2432 - Decrease the lower limit of MaxMemInQueues to 256 MBytes (but leave
2433 the default at 8GBytes), to better support Raspberry Pi users. Fixes
2434 bug 9686; bugfix on 0.2.4.14-alpha.
2436 o Minor features (bridges, pluggable transports):
2437 - Bridges now write the SHA1 digest of their identity key
2438 fingerprint (that is, a hash of a hash of their public key) to
2439 notice-level logs, and to a new hashed-fingerprint file. This
2440 information will help bridge operators look up their bridge in
2441 Globe and similar tools. Resolves ticket 10884.
2442 - Improve the message that Tor displays when running as a bridge
2443 using pluggable transports without an Extended ORPort listener.
2444 Also, log the message in the log file too. Resolves ticket 11043.
2446 o Minor features (other):
2447 - Add a new option, PredictedPortsRelevanceTime, to control how long
2448 after having received a request to connect to a given port Tor
2449 will try to keep circuits ready in anticipation of future requests
2450 for that port. Patch from "unixninja92"; implements ticket 9176.
2451 - Generate a warning if any ports are listed in the SocksPolicy,
2452 DirPolicy, AuthDirReject, AuthDirInvalid, AuthDirBadDir, or
2453 AuthDirBadExit options. (These options only support address
2454 ranges.) Fixes part of ticket 11108.
2455 - Update geoip and geoip6 to the February 7 2014 Maxmind GeoLite2
2458 o Minor bugfixes (new since 0.2.5.2-alpha, also in 0.2.4.21):
2459 - Build without warnings under clang 3.4. (We have some macros that
2460 define static functions only some of which will get used later in
2461 the module. Starting with clang 3.4, these give a warning unless the
2462 unused attribute is set on them.) Resolves ticket 10904.
2463 - Fix build warnings about missing "a2x" comment when building the
2464 manpages from scratch on OpenBSD; OpenBSD calls it "a2x.py".
2465 Fixes bug 10929; bugfix on 0.2.2.9-alpha. Patch from Dana Koch.
2467 o Minor bugfixes (client):
2468 - Improve the log message when we can't connect to a hidden service
2469 because all of the hidden service directory nodes hosting its
2470 descriptor are excluded. Improves on our fix for bug 10722, which
2471 was a bugfix on 0.2.0.10-alpha.
2472 - Raise a control port warning when we fail to connect to all of
2473 our bridges. Previously, we didn't inform the controller, and
2474 the bootstrap process would stall. Fixes bug 11069; bugfix on
2476 - Exit immediately when a process-owning controller exits.
2477 Previously, tor relays would wait for a little while after their
2478 controller exited, as if they had gotten an INT signal -- but this
2479 was problematic, since there was no feedback for the user. To do a
2480 clean shutdown, controllers should send an INT signal and give Tor
2481 a chance to clean up. Fixes bug 10449; bugfix on 0.2.2.28-beta.
2482 - Stop attempting to connect to bridges before our pluggable
2483 transports are configured (harmless but resulted in some erroneous
2484 log messages). Fixes bug 11156; bugfix on 0.2.3.2-alpha.
2485 - Fix connections to IPv6 addresses over SOCKS5. Previously, we were
2486 generating incorrect SOCKS5 responses, and confusing client
2487 applications. Fixes bug 10987; bugfix on 0.2.4.7-alpha.
2489 o Minor bugfixes (relays and bridges):
2490 - Avoid crashing on a malformed resolv.conf file when running a
2491 relay using Libevent 1. Fixes bug 8788; bugfix on 0.1.1.23.
2492 - Non-exit relays no longer launch mock DNS requests to check for
2493 DNS hijacking. This has been unnecessary since 0.2.1.7-alpha, when
2494 non-exit relays stopped servicing DNS requests. Fixes bug 965;
2495 bugfix on 0.2.1.7-alpha. Patch from Matt Pagan.
2496 - Bridges now report complete directory request statistics. Related
2497 to bug 5824; bugfix on 0.2.2.1-alpha.
2498 - Bridges now never collect statistics that were designed for
2499 relays. Fixes bug 5824; bugfix on 0.2.3.8-alpha.
2500 - Stop giving annoying warning messages when we decide not to launch
2501 a pluggable transport proxy that we don't need (because there are
2502 no bridges configured to use it). Resolves ticket 5018; bugfix
2504 - Give the correct URL in the warning message when trying to run a
2505 relay on an ancient version of Windows. Fixes bug 9393.
2507 o Minor bugfixes (backtrace support):
2508 - Support automatic backtraces on more platforms by using the
2509 "-fasynchronous-unwind-tables" compiler option. This option is
2510 needed for platforms like 32-bit Intel where "-fomit-frame-pointer"
2511 is on by default and table generation is not. This doesn't yet
2512 add Windows support; only Linux, OSX, and some BSDs are affected.
2513 Reported by 'cypherpunks'; fixes bug 11047; bugfix on 0.2.5.2-alpha.
2514 - Avoid strange behavior if two threads hit failed assertions at the
2515 same time and both try to log backtraces at once. (Previously, if
2516 this had happened, both threads would have stored their intermediate
2517 results in the same buffer, and generated junk outputs.) Reported by
2518 "cypherpunks". Fixes bug 11048; bugfix on 0.2.5.2-alpha.
2519 - Fix a compiler warning in format_number_sigsafe(). Bugfix on
2520 0.2.5.2-alpha; patch from Nick Hopper.
2522 o Minor bugfixes (unit tests):
2523 - Fix a small bug in the unit tests that might have made the tests
2524 call 'chmod' with an uninitialized bitmask. Fixes bug 10928;
2525 bugfix on 0.2.5.1-alpha. Patch from Dana Koch.
2528 - Remove all remaining code related to version-0 hidden service
2529 descriptors: they have not been in use since 0.2.2.1-alpha. Fixes
2530 the rest of bug 10841.
2533 - Document in the manpage that "KBytes" may also be written as
2534 "kilobytes" or "KB", that "Kbits" may also be written as
2535 "kilobits", and so forth. Closes ticket 9222.
2536 - Document that the ClientOnly config option overrides ORPort.
2537 Our old explanation made ClientOnly sound as though it did
2538 nothing at all. Resolves bug 9059.
2539 - Explain that SocksPolicy, DirPolicy, and similar options don't
2540 take port arguments. Fixes the other part of ticket 11108.
2541 - Fix a comment about the rend_server_descriptor_t.protocols field
2542 to more accurately describe its range. Also, make that field
2543 unsigned, to more accurately reflect its usage. Fixes bug 9099;
2544 bugfix on 0.2.1.5-alpha.
2545 - Fix the manpage's description of HiddenServiceAuthorizeClient:
2546 the maximum client name length is 16, not 19. Fixes bug 11118;
2547 bugfix on 0.2.1.6-alpha.
2549 o Code simplifications and refactoring:
2550 - Get rid of router->address, since in all cases it was just the
2551 string representation of router->addr. Resolves ticket 5528.
2553 o Test infrastructure:
2554 - Update to the latest version of tinytest.
2555 - Improve the tinytest implementation of string operation tests so
2556 that comparisons with NULL strings no longer crash the tests; they
2557 now just fail, normally. Fixes bug 9004; bugfix on 0.2.2.4-alpha.
2560 Changes in version 0.2.4.21 - 2014-02-28
2561 Tor 0.2.4.21 further improves security against potential adversaries who
2562 find breaking 1024-bit crypto doable, and backports several stability
2563 and robustness patches from the 0.2.5 branch.
2565 o Major features (client security):
2566 - When we choose a path for a 3-hop circuit, make sure it contains
2567 at least one relay that supports the NTor circuit extension
2568 handshake. Otherwise, there is a chance that we're building
2569 a circuit that's worth attacking by an adversary who finds
2570 breaking 1024-bit crypto doable, and that chance changes the game
2571 theory. Implements ticket 9777.
2574 - Do not treat streams that fail with reason
2575 END_STREAM_REASON_INTERNAL as indicating a definite circuit failure,
2576 since it could also indicate an ENETUNREACH connection error. Fixes
2577 part of bug 10777; bugfix on 0.2.4.8-alpha.
2579 o Code simplification and refactoring:
2580 - Remove data structures which were introduced to implement the
2581 CellStatistics option: they are now redundant with the new timestamp
2582 field in the regular packed_cell_t data structure, which we did
2583 in 0.2.4.18-rc in order to resolve bug 9093. Resolves ticket 10870.
2586 - Always clear OpenSSL bignums before freeing them -- even bignums
2587 that don't contain secrets. Resolves ticket 10793. Patch by
2589 - Build without warnings under clang 3.4. (We have some macros that
2590 define static functions only some of which will get used later in
2591 the module. Starting with clang 3.4, these give a warning unless the
2592 unused attribute is set on them.) Resolves ticket 10904.
2593 - Update geoip and geoip6 files to the February 7 2014 Maxmind
2594 GeoLite2 Country database.
2597 - Set the listen() backlog limit to the largest actually supported
2598 on the system, not to the value in a header file. Fixes bug 9716;
2599 bugfix on every released Tor.
2600 - Treat ENETUNREACH, EACCES, and EPERM connection failures at an
2601 exit node as a NOROUTE error, not an INTERNAL error, since they
2602 can apparently happen when trying to connect to the wrong sort
2603 of netblocks. Fixes part of bug 10777; bugfix on 0.1.0.1-rc.
2604 - Fix build warnings about missing "a2x" comment when building the
2605 manpages from scratch on OpenBSD; OpenBSD calls it "a2x.py".
2606 Fixes bug 10929; bugfix on 0.2.2.9-alpha. Patch from Dana Koch.
2607 - Avoid a segfault on SIGUSR1, where we had freed a connection but did
2608 not entirely remove it from the connection lists. Fixes bug 9602;
2609 bugfix on 0.2.4.4-alpha.
2610 - Fix a segmentation fault in our benchmark code when running with
2611 Fedora's OpenSSL package, or any other OpenSSL that provides
2612 ECDH but not P224. Fixes bug 10835; bugfix on 0.2.4.8-alpha.
2613 - Turn "circuit handshake stats since last time" log messages into a
2614 heartbeat message. Fixes bug 10485; bugfix on 0.2.4.17-rc.
2616 o Documentation fixes:
2617 - Document that all but one DirPort entry must have the NoAdvertise
2618 flag set. Fixes bug 10470; bugfix on 0.2.3.3-alpha / 0.2.3.16-alpha.
2621 Changes in version 0.2.5.2-alpha - 2014-02-13
2622 Tor 0.2.5.2-alpha includes all the fixes from 0.2.4.18-rc and 0.2.4.20,
2623 like the "poor random number generation" fix and the "building too many
2624 circuits" fix. It also further improves security against potential
2625 adversaries who find breaking 1024-bit crypto doable, and launches
2626 pluggable transports on demand (which gets us closer to integrating
2627 pluggable transport support by default -- not to be confused with Tor
2628 bundles enabling pluggable transports and bridges by default).
2630 o Major features (client security):
2631 - When we choose a path for a 3-hop circuit, make sure it contains
2632 at least one relay that supports the NTor circuit extension
2633 handshake. Otherwise, there is a chance that we're building
2634 a circuit that's worth attacking by an adversary who finds
2635 breaking 1024-bit crypto doable, and that chance changes the game
2636 theory. Implements ticket 9777.
2637 - Clients now look at the "usecreatefast" consensus parameter to
2638 decide whether to use CREATE_FAST or CREATE cells for the first hop
2639 of their circuit. This approach can improve security on connections
2640 where Tor's circuit handshake is stronger than the available TLS
2641 connection security levels, but the tradeoff is more computational
2642 load on guard relays. Implements proposal 221. Resolves ticket 9386.
2644 o Major features (bridges):
2645 - Don't launch pluggable transport proxies if we don't have any
2646 bridges configured that would use them. Now we can list many
2647 pluggable transports, and Tor will dynamically start one when it
2648 hears a bridge address that needs it. Resolves ticket 5018.
2649 - The bridge directory authority now assigns status flags (Stable,
2650 Guard, etc) to bridges based on thresholds calculated over all
2651 Running bridges. Now bridgedb can finally make use of its features
2652 to e.g. include at least one Stable bridge in its answers. Fixes
2655 o Major features (other):
2656 - Extend ORCONN controller event to include an "ID" parameter,
2657 and add four new controller event types CONN_BW, CIRC_BW,
2658 CELL_STATS, and TB_EMPTY that show connection and circuit usage.
2659 The new events are emitted in private Tor networks only, with the
2660 goal of being able to better track performance and load during
2661 full-network simulations. Implements proposal 218 and ticket 7359.
2662 - On some platforms (currently: recent OSX versions, glibc-based
2663 platforms that support the ELF format, and a few other
2664 Unix-like operating systems), Tor can now dump stack traces
2665 when a crash occurs or an assertion fails. By default, traces
2666 are dumped to stderr (if possible) and to any logs that are
2667 reporting errors. Implements ticket 9299.
2670 - Avoid a segfault on SIGUSR1, where we had freed a connection but did
2671 not entirely remove it from the connection lists. Fixes bug 9602;
2672 bugfix on 0.2.4.4-alpha.
2673 - Do not treat streams that fail with reason
2674 END_STREAM_REASON_INTERNAL as indicating a definite circuit failure,
2675 since it could also indicate an ENETUNREACH connection error. Fixes
2676 part of bug 10777; bugfix on 0.2.4.8-alpha.
2678 o Major bugfixes (new since 0.2.5.1-alpha, also in 0.2.4.20):
2679 - Do not allow OpenSSL engines to replace the PRNG, even when
2680 HardwareAccel is set. The only default builtin PRNG engine uses
2681 the Intel RDRAND instruction to replace the entire PRNG, and
2682 ignores all attempts to seed it with more entropy. That's
2683 cryptographically stupid: the right response to a new alleged
2684 entropy source is never to discard all previously used entropy
2685 sources. Fixes bug 10402; works around behavior introduced in
2686 OpenSSL 1.0.0. Diagnosis and investigation thanks to "coderman"
2688 - Fix assertion failure when AutomapHostsOnResolve yields an IPv6
2689 address. Fixes bug 10465; bugfix on 0.2.4.7-alpha.
2690 - Avoid launching spurious extra circuits when a stream is pending.
2691 This fixes a bug where any circuit that _wasn't_ unusable for new
2692 streams would be treated as if it were, causing extra circuits to
2693 be launched. Fixes bug 10456; bugfix on 0.2.4.12-alpha.
2695 o Major bugfixes (new since 0.2.5.1-alpha, also in 0.2.4.18-rc):
2696 - No longer stop reading or writing on cpuworker connections when
2697 our rate limiting buckets go empty. Now we should handle circuit
2698 handshake requests more promptly. Resolves bug 9731.
2699 - Stop trying to bootstrap all our directory information from
2700 only our first guard. Discovered while fixing bug 9946; bugfix
2703 o Minor features (bridges, pluggable transports):
2704 - Add threshold cutoffs to the networkstatus document created by
2705 the Bridge Authority. Fixes bug 1117.
2706 - On Windows, spawn background processes using the CREATE_NO_WINDOW
2707 flag. Now Tor Browser Bundle 3.5 with pluggable transports enabled
2708 doesn't pop up a blank console window. (In Tor Browser Bundle 2.x,
2709 Vidalia set this option for us.) Implements ticket 10297.
2711 o Minor features (security):
2712 - Always clear OpenSSL bignums before freeing them -- even bignums
2713 that don't contain secrets. Resolves ticket 10793. Patch by
2716 o Minor features (config options and command line):
2717 - Add an --allow-missing-torrc commandline option that tells Tor to
2718 run even if the configuration file specified by -f is not available.
2719 Implements ticket 10060.
2720 - Add support for the TPROXY transparent proxying facility on Linux.
2721 See documentation for the new TransProxyType option for more
2722 details. Implementation by "thomo". Closes ticket 10582.
2724 o Minor features (controller):
2725 - Add a new "HS_DESC" controller event that reports activities
2726 related to hidden service descriptors. Resolves ticket 8510.
2727 - New "DROPGUARDS" controller command to forget all current entry
2728 guards. Not recommended for ordinary use, since replacing guards
2729 too frequently makes several attacks easier. Resolves ticket 9934;
2732 o Minor features (build):
2733 - Assume that a user using ./configure --host wants to cross-compile,
2734 and give an error if we cannot find a properly named
2735 tool-chain. Add a --disable-tool-name-check option to proceed
2736 nevertheless. Addresses ticket 9869. Patch by Benedikt Gollatz.
2737 - If we run ./configure and the compiler recognizes -fstack-protector
2738 but the linker rejects it, warn the user about a potentially missing
2739 libssp package. Addresses ticket 9948. Patch from Benedikt Gollatz.
2741 o Minor features (testing):
2742 - If Python is installed, "make check" now runs extra tests beyond
2743 the unit test scripts.
2744 - When bootstrapping a test network, sometimes very few relays get
2745 the Guard flag. Now a new option "TestingDirAuthVoteGuard" can
2746 specify a set of relays which should be voted Guard regardless of
2747 their uptime or bandwidth. Addresses ticket 9206.
2749 o Minor features (log messages):
2750 - When ServerTransportPlugin is set on a bridge, Tor can write more
2751 useful statistics about bridge use in its extrainfo descriptors,
2752 but only if the Extended ORPort ("ExtORPort") is set too. Add a
2753 log message to inform the user in this case. Resolves ticket 9651.
2754 - When receiving a new controller connection, log the origin address.
2755 Resolves ticket 9698; patch from "sigpipe".
2756 - When logging OpenSSL engine status at startup, log the status of
2757 more engines. Fixes ticket 10043; patch from Joshua Datko.
2758 - Turn "circuit handshake stats since last time" log messages into a
2759 heartbeat message. Fixes bug 10485; bugfix on 0.2.4.17-rc.
2761 o Minor features (new since 0.2.5.1-alpha, also in 0.2.4.18-rc):
2762 - Improve the circuit queue out-of-memory handler. Previously, when
2763 we ran low on memory, we'd close whichever circuits had the most
2764 queued cells. Now, we close those that have the *oldest* queued
2765 cells, on the theory that those are most responsible for us
2766 running low on memory. Based on analysis from a forthcoming paper
2767 by Jansen, Tschorsch, Johnson, and Scheuermann. Fixes bug 9093.
2768 - Generate bootstrapping status update events correctly when fetching
2769 microdescriptors. Fixes bug 9927.
2770 - Update to the October 2 2013 Maxmind GeoLite Country database.
2772 o Minor bugfixes (clients):
2773 - When closing a channel that has already been open, do not close
2774 pending circuits that were waiting to connect to the same relay.
2775 Fixes bug 9880; bugfix on 0.2.5.1-alpha. Thanks to skruffy for
2778 o Minor bugfixes (relays):
2779 - Treat ENETUNREACH, EACCES, and EPERM connection failures at an
2780 exit node as a NOROUTE error, not an INTERNAL error, since they
2781 can apparently happen when trying to connect to the wrong sort
2782 of netblocks. Fixes part of bug 10777; bugfix on 0.1.0.1-rc.
2784 o Minor bugfixes (bridges):
2785 - Fix a bug where the first connection works to a bridge that uses a
2786 pluggable transport with client-side parameters, but we don't send
2787 the client-side parameters on subsequent connections. (We don't
2788 use any pluggable transports with client-side parameters yet,
2789 but ScrambleSuit will soon become the first one.) Fixes bug 9162;
2790 bugfix on 0.2.0.3-alpha. Based on a patch from "rl1987".
2792 o Minor bugfixes (node selection):
2793 - If ExcludeNodes is set, consider non-excluded hidden service
2794 directory servers before excluded ones. Do not consider excluded
2795 hidden service directory servers at all if StrictNodes is
2796 set. (Previously, we would sometimes decide to connect to those
2797 servers, and then realize before we initiated a connection that
2798 we had excluded them.) Fixes bug 10722; bugfix on 0.2.0.10-alpha.
2800 - If we set the ExitNodes option but it doesn't include any nodes
2801 that have the Exit flag, we would choose not to bootstrap. Now we
2802 bootstrap so long as ExitNodes includes nodes which can exit to
2803 some port. Fixes bug 10543; bugfix on 0.2.4.10-alpha.
2805 o Minor bugfixes (controller and command-line):
2806 - If changing a config option via "setconf" fails in a recoverable
2807 way, we used to nonetheless write our new control ports to the
2808 file described by the "ControlPortWriteToFile" option. Now we only
2809 write out that file if we successfully switch to the new config
2810 option. Fixes bug 5605; bugfix on 0.2.2.26-beta. Patch from "Ryman".
2811 - When a command-line option such as --version or --help that
2812 ordinarily implies --hush appears on the command line along with
2813 --quiet, then actually obey --quiet. Previously, we obeyed --quiet
2814 only if it appeared later on the command line. Fixes bug 9578;
2815 bugfix on 0.2.5.1-alpha.
2817 o Minor bugfixes (code correctness):
2818 - Previously we used two temporary files when writing descriptors to
2819 disk; now we only use one. Fixes bug 1376.
2820 - Remove an erroneous (but impossible and thus harmless) pointer
2821 comparison that would have allowed compilers to skip a bounds
2822 check in channeltls.c. Fixes bugs 10313 and 9980; bugfix on
2823 0.2.0.10-alpha. Noticed by Jared L Wong and David Fifield.
2824 - Fix an always-true assertion in pluggable transports code so it
2825 actually checks what it was trying to check. Fixes bug 10046;
2826 bugfix on 0.2.3.9-alpha. Found by "dcb".
2828 o Minor bugfixes (protocol correctness):
2829 - When receiving a VERSIONS cell with an odd number of bytes, close
2830 the connection immediately since the cell is malformed. Fixes bug
2831 10365; bugfix on 0.2.0.10-alpha. Spotted by "bobnomnom"; fix by
2834 o Minor bugfixes (build):
2835 - Restore the ability to compile Tor with V2_HANDSHAKE_SERVER
2836 turned off (that is, without support for v2 link handshakes). Fixes
2837 bug 4677; bugfix on 0.2.3.2-alpha. Patch from "piet".
2838 - Fix compilation warnings and startup issues when running with
2839 "Sandbox 1" and libseccomp-2.1.0. Fixes bug 10563; bugfix on
2841 - Fix compilation on Solaris 9, which didn't like us having an
2842 identifier named "sun". Fixes bug 10565; bugfix in 0.2.5.1-alpha.
2844 o Minor bugfixes (testing):
2845 - Fix a segmentation fault in our benchmark code when running with
2846 Fedora's OpenSSL package, or any other OpenSSL that provides
2847 ECDH but not P224. Fixes bug 10835; bugfix on 0.2.4.8-alpha.
2849 o Minor bugfixes (log messages):
2850 - Fix a bug where clients using bridges would report themselves
2851 as 50% bootstrapped even without a live consensus document.
2852 Fixes bug 9922; bugfix on 0.2.1.1-alpha.
2853 - Suppress a warning where, if there's only one directory authority
2854 in the network, we would complain that votes and signatures cannot
2855 be uploaded to other directory authorities. Fixes bug 10842;
2856 bugfix on 0.2.2.26-beta.
2857 - Report bootstrapping progress correctly when we're downloading
2858 microdescriptors. We had updated our "do we have enough microdescs
2859 to begin building circuits?" logic most recently in 0.2.4.10-alpha
2860 (see bug 5956), but we left the bootstrap status event logic at
2861 "how far through getting 1/4 of them are we?" Fixes bug 9958;
2862 bugfix on 0.2.2.36, which is where they diverged (see bug 5343).
2864 o Minor bugfixes (new since 0.2.5.1-alpha, also in 0.2.4.20):
2865 - Avoid a crash bug when starting with a corrupted microdescriptor
2866 cache file. Fixes bug 10406; bugfix on 0.2.2.6-alpha.
2867 - If we fail to dump a previously cached microdescriptor to disk, avoid
2868 freeing duplicate data later on. Fixes bug 10423; bugfix on
2869 0.2.4.13-alpha. Spotted by "bobnomnom".
2871 o Minor bugfixes on 0.2.4.x (new since 0.2.5.1-alpha, also in 0.2.4.18-rc):
2872 - Correctly log long IPv6 exit policies, instead of truncating them
2873 or reporting an error. Fixes bug 9596; bugfix on 0.2.4.7-alpha.
2874 - Our default TLS ecdhe groups were backwards: we meant to be using
2875 P224 for relays (for performance win) and P256 for bridges (since
2876 it is more common in the wild). Instead we had it backwards. After
2877 reconsideration, we decided that the default should be P256 on all
2878 hosts, since its security is probably better, and since P224 is
2879 reportedly used quite little in the wild. Found by "skruffy" on
2880 IRC. Fix for bug 9780; bugfix on 0.2.4.8-alpha.
2881 - Free directory authority certificate download statuses on exit
2882 rather than leaking them. Fixes bug 9644; bugfix on 0.2.4.13-alpha.
2884 o Minor bugfixes on 0.2.3.x (new since 0.2.5.1-alpha, also in 0.2.4.18-rc):
2885 - If the guard we choose first doesn't answer, we would try the
2886 second guard, but once we connected to the second guard we would
2887 abandon it and retry the first one, slowing down bootstrapping.
2888 The fix is to treat all our initially chosen guards as acceptable
2889 to use. Fixes bug 9946; bugfix on 0.1.1.11-alpha.
2890 - Fix an assertion failure that would occur when disabling the
2891 ORPort setting on a running Tor process while accounting was
2892 enabled. Fixes bug 6979; bugfix on 0.2.2.18-alpha.
2893 - When examining the list of network interfaces to find our address,
2894 do not consider non-running or disabled network interfaces. Fixes
2895 bug 9904; bugfix on 0.2.3.11-alpha. Patch from "hantwister".
2896 - Avoid an off-by-one error when checking buffer boundaries when
2897 formatting the exit status of a pluggable transport helper.
2898 This is probably not an exploitable bug, but better safe than
2899 sorry. Fixes bug 9928; bugfix on 0.2.3.18-rc. Bug found by
2902 o Removed code and features:
2903 - Clients now reject any directory authority certificates lacking
2904 a dir-key-crosscert element. These have been included since
2905 0.2.1.9-alpha, so there's no real reason for them to be optional
2906 any longer. Completes proposal 157. Resolves ticket 10162.
2907 - Remove all code that existed to support the v2 directory system,
2908 since there are no longer any v2 directory authorities. Resolves
2910 - Remove the HSAuthoritativeDir and AlternateHSAuthority torrc
2911 options, which were used for designating authorities as "Hidden
2912 service authorities". There has been no use of hidden service
2913 authorities since 0.2.2.1-alpha, when we stopped uploading or
2914 downloading v0 hidden service descriptors. Fixes bug 10881; also
2915 part of a fix for bug 10841.
2917 o Code simplification and refactoring:
2918 - Remove some old fallback code designed to keep Tor clients working
2919 in a network with only two working relays. Elsewhere in the code we
2920 have long since stopped supporting such networks, so there wasn't
2921 much point in keeping it around. Addresses ticket 9926.
2922 - Reject 0-length EXTEND2 cells more explicitly. Fixes bug 10536;
2923 bugfix on 0.2.4.8-alpha. Reported by "cypherpunks".
2924 - Remove data structures which were introduced to implement the
2925 CellStatistics option: they are now redundant with the addition
2926 of a timestamp to the regular packed_cell_t data structure, which
2927 we did in 0.2.4.18-rc in order to resolve ticket 9093. Implements
2930 o Documentation (man page) fixes:
2931 - Update manpage to describe some of the files you can expect to
2932 find in Tor's DataDirectory. Addresses ticket 9839.
2933 - Document that all but one DirPort entry must have the NoAdvertise
2934 flag set. Fixes bug 10470; bugfix on 0.2.3.3-alpha / 0.2.3.16-alpha.
2936 o Documentation fixes (new since 0.2.5.1-alpha, also in 0.2.4.18-rc):
2937 - Clarify the usage and risks of setting the ContactInfo torrc line
2938 for your relay or bridge. Resolves ticket 9854.
2939 - Add anchors to the manpage so we can link to the html version of
2940 the documentation for specific options. Resolves ticket 9866.
2941 - Replace remaining references to DirServer in man page and
2942 log entries. Resolves ticket 10124.
2945 - Make the "tor-gencert" tool used by directory authority operators
2946 create 2048-bit signing keys by default (rather than 1024-bit, since
2947 1024-bit is uncomfortably small these days). Addresses ticket 10324.
2950 Changes in version 0.2.4.20 - 2013-12-22
2951 Tor 0.2.4.20 fixes potentially poor random number generation for users
2952 who 1) use OpenSSL 1.0.0 or later, 2) set "HardwareAccel 1" in their
2953 torrc file, 3) have "Sandy Bridge" or "Ivy Bridge" Intel processors,
2954 and 4) have no state file in their DataDirectory (as would happen on
2955 first start). Users who generated relay or hidden service identity
2956 keys in such a situation should discard them and generate new ones.
2958 This release also fixes a logic error that caused Tor clients to build
2959 many more preemptive circuits than they actually need.
2962 - Do not allow OpenSSL engines to replace the PRNG, even when
2963 HardwareAccel is set. The only default builtin PRNG engine uses
2964 the Intel RDRAND instruction to replace the entire PRNG, and
2965 ignores all attempts to seed it with more entropy. That's
2966 cryptographically stupid: the right response to a new alleged
2967 entropy source is never to discard all previously used entropy
2968 sources. Fixes bug 10402; works around behavior introduced in
2969 OpenSSL 1.0.0. Diagnosis and investigation thanks to "coderman"
2971 - Fix assertion failure when AutomapHostsOnResolve yields an IPv6
2972 address. Fixes bug 10465; bugfix on 0.2.4.7-alpha.
2973 - Avoid launching spurious extra circuits when a stream is pending.
2974 This fixes a bug where any circuit that _wasn't_ unusable for new
2975 streams would be treated as if it were, causing extra circuits to
2976 be launched. Fixes bug 10456; bugfix on 0.2.4.12-alpha.
2979 - Avoid a crash bug when starting with a corrupted microdescriptor
2980 cache file. Fixes bug 10406; bugfix on 0.2.2.6-alpha.
2981 - If we fail to dump a previously cached microdescriptor to disk, avoid
2982 freeing duplicate data later on. Fixes bug 10423; bugfix on
2983 0.2.4.13-alpha. Spotted by "bobnomnom".
2986 Changes in version 0.2.4.19 - 2013-12-11
2987 The Tor 0.2.4 release series is dedicated to the memory of Aaron Swartz
2988 (1986-2013). Aaron worked on diverse projects including helping to guide
2989 Creative Commons, playing a key role in stopping SOPA/PIPA, bringing
2990 transparency to the U.S government's PACER documents, and contributing
2991 design and development for Tor and Tor2Web. Aaron was one of the latest
2992 martyrs in our collective fight for civil liberties and human rights,
2993 and his death is all the more painful because he was one of us.
2995 Tor 0.2.4.19, the first stable release in the 0.2.4 branch, features
2996 a new circuit handshake and link encryption that use ECC to provide
2997 better security and efficiency; makes relays better manage circuit
2998 creation requests; uses "directory guards" to reduce client enumeration
2999 risks; makes bridges collect and report statistics about the pluggable
3000 transports they support; cleans up and improves our geoip database;
3001 gets much closer to IPv6 support for clients, bridges, and relays; makes
3002 directory authorities use measured bandwidths rather than advertised
3003 ones when computing flags and thresholds; disables client-side DNS
3004 caching to reduce tracking risks; and fixes a big bug in bridge
3005 reachability testing. This release introduces two new design
3006 abstractions in the code: a new "channel" abstraction between circuits
3007 and or_connections to allow for implementing alternate relay-to-relay
3008 transports, and a new "circuitmux" abstraction storing the queue of
3009 circuits for a channel. The release also includes many stability,
3010 security, and privacy fixes.
3013 Changes in version 0.2.4.18-rc - 2013-11-16
3014 Tor 0.2.4.18-rc is the fourth release candidate for the Tor 0.2.4.x
3015 series. It takes a variety of fixes from the 0.2.5.x branch to improve
3016 stability, performance, and better handling of edge cases.
3019 - Re-enable TLS 1.1 and 1.2 when built with OpenSSL 1.0.1e or later.
3020 Resolves ticket 6055. (OpenSSL before 1.0.1 didn't have TLS 1.1 or
3021 1.2, and OpenSSL from 1.0.1 through 1.0.1d had bugs that prevented
3022 renegotiation from working with TLS 1.1 or 1.2, so we had disabled
3023 them to solve bug 6033.)
3026 - No longer stop reading or writing on cpuworker connections when
3027 our rate limiting buckets go empty. Now we should handle circuit
3028 handshake requests more promptly. Resolves bug 9731.
3029 - If we are unable to save a microdescriptor to the journal, do not
3030 drop it from memory and then reattempt downloading it. Fixes bug
3031 9645; bugfix on 0.2.2.6-alpha.
3032 - Stop trying to bootstrap all our directory information from
3033 only our first guard. Discovered while fixing bug 9946; bugfix
3035 - The new channel code sometimes lost track of in-progress circuits,
3036 causing long-running clients to stop building new circuits. The
3037 fix is to always call circuit_n_chan_done(chan, 0) from
3038 channel_closed(). Fixes bug 9776; bugfix on 0.2.4.17-rc.
3040 o Minor bugfixes (on 0.2.4.x):
3041 - Correctly log long IPv6 exit policies, instead of truncating them
3042 or reporting an error. Fixes bug 9596; bugfix on 0.2.4.7-alpha.
3043 - Our default TLS ecdhe groups were backwards: we meant to be using
3044 P224 for relays (for performance win) and P256 for bridges (since
3045 it is more common in the wild). Instead we had it backwards. After
3046 reconsideration, we decided that the default should be P256 on all
3047 hosts, since its security is probably better, and since P224 is
3048 reportedly used quite little in the wild. Found by "skruffy" on
3049 IRC. Fix for bug 9780; bugfix on 0.2.4.8-alpha.
3050 - Free directory authority certificate download statuses on exit
3051 rather than leaking them. Fixes bug 9644; bugfix on 0.2.4.13-alpha.
3053 o Minor bugfixes (on 0.2.3.x and earlier):
3054 - If the guard we choose first doesn't answer, we would try the
3055 second guard, but once we connected to the second guard we would
3056 abandon it and retry the first one, slowing down bootstrapping.
3057 The fix is to treat all our initially chosen guards as acceptable
3058 to use. Fixes bug 9946; bugfix on 0.1.1.11-alpha.
3059 - Fix an assertion failure that would occur when disabling the
3060 ORPort setting on a running Tor process while accounting was
3061 enabled. Fixes bug 6979; bugfix on 0.2.2.18-alpha.
3062 - When examining the list of network interfaces to find our address,
3063 do not consider non-running or disabled network interfaces. Fixes
3064 bug 9904; bugfix on 0.2.3.11-alpha. Patch from "hantwister".
3065 - Avoid an off-by-one error when checking buffer boundaries when
3066 formatting the exit status of a pluggable transport helper.
3067 This is probably not an exploitable bug, but better safe than
3068 sorry. Fixes bug 9928; bugfix on 0.2.3.18-rc. Bug found by
3071 o Minor features (protecting client timestamps):
3072 - Clients no longer send timestamps in their NETINFO cells. These were
3073 not used for anything, and they provided one small way for clients
3074 to be distinguished from each other as they moved from network to
3075 network or behind NAT. Implements part of proposal 222.
3076 - Clients now round timestamps in INTRODUCE cells down to the nearest
3077 10 minutes. If a new Support022HiddenServices option is set to 0, or
3078 if it's set to "auto" and the feature is disabled in the consensus,
3079 the timestamp is sent as 0 instead. Implements part of proposal 222.
3080 - Stop sending timestamps in AUTHENTICATE cells. This is not such
3081 a big deal from a security point of view, but it achieves no actual
3082 good purpose, and isn't needed. Implements part of proposal 222.
3083 - Reduce down accuracy of timestamps in hidden service descriptors.
3084 Implements part of proposal 222.
3086 o Minor features (other):
3087 - Improve the circuit queue out-of-memory handler. Previously, when
3088 we ran low on memory, we'd close whichever circuits had the most
3089 queued cells. Now, we close those that have the *oldest* queued
3090 cells, on the theory that those are most responsible for us
3091 running low on memory. Based on analysis from a forthcoming paper
3092 by Jansen, Tschorsch, Johnson, and Scheuermann. Fixes bug 9093.
3093 - Generate bootstrapping status update events correctly when fetching
3094 microdescriptors. Fixes bug 9927.
3095 - Update to the October 2 2013 Maxmind GeoLite Country database.
3097 o Documentation fixes:
3098 - Clarify the usage and risks of setting the ContactInfo torrc line
3099 for your relay or bridge. Resolves ticket 9854.
3100 - Add anchors to the manpage so we can link to the html version of
3101 the documentation for specific options. Resolves ticket 9866.
3102 - Replace remaining references to DirServer in man page and
3103 log entries. Resolves ticket 10124.
3106 Changes in version 0.2.5.1-alpha - 2013-10-02
3107 Tor 0.2.5.1-alpha introduces experimental support for syscall sandboxing
3108 on Linux, allows bridges that offer pluggable transports to report usage
3109 statistics, fixes many issues to make testing easier, and provides
3110 a pile of minor features and bugfixes that have been waiting for a
3111 release of the new branch.
3113 This is the first alpha release in a new series, so expect there to
3114 be bugs. Users who would rather test out a more stable branch should
3115 stay with 0.2.4.x for now.
3117 o Major features (security):
3118 - Use the seccomp2 syscall filtering facility on Linux to limit
3119 which system calls Tor can invoke. This is an experimental,
3120 Linux-only feature to provide defense-in-depth against unknown
3121 attacks. To try turning it on, set "Sandbox 1" in your torrc
3122 file. Please be ready to report bugs. We hope to add support
3123 for better sandboxing in the future, including more fine-grained
3124 filters, better division of responsibility, and support for more
3125 platforms. This work has been done by Cristian-Matei Toader for
3126 Google Summer of Code.
3127 - Re-enable TLS 1.1 and 1.2 when built with OpenSSL 1.0.1e or later.
3128 Resolves ticket 6055. (OpenSSL before 1.0.1 didn't have TLS 1.1 or
3129 1.2, and OpenSSL from 1.0.1 through 1.0.1d had bugs that prevented
3130 renegotiation from working with TLS 1.1 or 1.2, so we had disabled
3131 them to solve bug 6033.)
3133 o Major features (other):
3134 - Add support for passing arguments to managed pluggable transport
3135 proxies. Implements ticket 3594.
3136 - Bridges now track GeoIP information and the number of their users
3137 even when pluggable transports are in use, and report usage
3138 statistics in their extra-info descriptors. Resolves tickets 4773
3140 - Make testing Tor networks bootstrap better: lower directory fetch
3141 retry schedules and maximum interval without directory requests,
3142 and raise maximum download tries. Implements ticket 6752.
3143 - Add make target 'test-network' to run tests on a Chutney network.
3144 Implements ticket 8530.
3145 - The ntor handshake is now on-by-default, no matter what the
3146 directory authorities recommend. Implements ticket 8561.
3149 - Instead of writing destroy cells directly to outgoing connection
3150 buffers, queue them and intersperse them with other outgoing cells.
3151 This can prevent a set of resource starvation conditions where too
3152 many pending destroy cells prevent data cells from actually getting
3153 delivered. Reported by "oftc_must_be_destroyed". Fixes bug 7912;
3154 bugfix on 0.2.0.1-alpha.
3155 - If we are unable to save a microdescriptor to the journal, do not
3156 drop it from memory and then reattempt downloading it. Fixes bug
3157 9645; bugfix on 0.2.2.6-alpha.
3158 - The new channel code sometimes lost track of in-progress circuits,
3159 causing long-running clients to stop building new circuits. The
3160 fix is to always call circuit_n_chan_done(chan, 0) from
3161 channel_closed(). Fixes bug 9776; bugfix on 0.2.4.17-rc.
3164 - Tor now builds each source file in two modes: a mode that avoids
3165 exposing identifiers needlessly, and another mode that exposes
3166 more identifiers for testing. This lets the compiler do better at
3167 optimizing the production code, while enabling us to take more
3168 radical measures to let the unit tests test things.
3169 - The production builds no longer include functions used only in
3170 the unit tests; all functions exposed from a module only for
3171 unit-testing are now static in production builds.
3172 - Add an --enable-coverage configuration option to make the unit
3173 tests (and a new src/or/tor-cov target) to build with gcov test
3177 - We now have rudimentary function mocking support that our unit
3178 tests can use to test functions in isolation. Function mocking
3179 lets the tests temporarily replace a function's dependencies with
3180 stub functions, so that the tests can check the function without
3181 invoking the other functions it calls.
3182 - Add more unit tests for the <circid,channel>->circuit map, and
3183 the destroy-cell-tracking code to fix bug 7912.
3184 - Unit tests for failing cases of the TAP onion handshake.
3185 - More unit tests for address-manipulation functions.
3187 o Minor features (protecting client timestamps):
3188 - Clients no longer send timestamps in their NETINFO cells. These were
3189 not used for anything, and they provided one small way for clients
3190 to be distinguished from each other as they moved from network to
3191 network or behind NAT. Implements part of proposal 222.
3192 - Clients now round timestamps in INTRODUCE cells down to the nearest
3193 10 minutes. If a new Support022HiddenServices option is set to 0, or
3194 if it's set to "auto" and the feature is disabled in the consensus,
3195 the timestamp is sent as 0 instead. Implements part of proposal 222.
3196 - Stop sending timestamps in AUTHENTICATE cells. This is not such
3197 a big deal from a security point of view, but it achieves no actual
3198 good purpose, and isn't needed. Implements part of proposal 222.
3199 - Reduce down accuracy of timestamps in hidden service descriptors.
3200 Implements part of proposal 222.
3202 o Minor features (config options):
3203 - Config (torrc) lines now handle fingerprints which are missing
3204 their initial '$'. Resolves ticket 4341; improvement over 0.0.9pre5.
3205 - Support a --dump-config option to print some or all of the
3206 configured options. Mainly useful for debugging the command-line
3207 option parsing code. Helps resolve ticket 4647.
3208 - Raise awareness of safer logging: notify user of potentially
3209 unsafe config options, like logging more verbosely than severity
3210 "notice" or setting SafeLogging to 0. Resolves ticket 5584.
3211 - Add a new configuration option TestingV3AuthVotingStartOffset
3212 that bootstraps a network faster by changing the timing for
3213 consensus votes. Addresses ticket 8532.
3214 - Add a new torrc option "ServerTransportOptions" that allows
3215 bridge operators to pass configuration parameters to their
3216 pluggable transports. Resolves ticket 8929.
3217 - The config (torrc) file now accepts bandwidth and space limits in
3218 bits as well as bytes. (Anywhere that you can say "2 Kilobytes",
3219 you can now say "16 kilobits", and so on.) Resolves ticket 9214.
3222 o Minor features (build):
3223 - Add support for `--library-versions` flag. Implements ticket 6384.
3224 - Return the "unexpected sendme" warnings to a warn severity, but make
3225 them rate limited, to help diagnose ticket 8093.
3226 - Detect a missing asciidoc, and warn the user about it, during
3227 configure rather than at build time. Fixes issue 6506. Patch from
3230 o Minor features (other):
3231 - Use the SOCK_NONBLOCK socket type, if supported, to open nonblocking
3232 sockets in a single system call. Implements ticket 5129.
3233 - Log current accounting state (bytes sent and received + remaining
3234 time for the current accounting period) in the relay's heartbeat
3235 message. Implements ticket 5526; patch from Peter Retzlaff.
3236 - Implement the TRANSPORT_LAUNCHED control port event that
3237 notifies controllers about new launched pluggable
3238 transports. Resolves ticket 5609.
3239 - If we're using the pure-C 32-bit curve25519_donna implementation
3240 of curve25519, build it with the -fomit-frame-pointer option to
3241 make it go faster on register-starved hosts. This improves our
3242 handshake performance by about 6% on i386 hosts without nacl.
3244 - Update to the September 4 2013 Maxmind GeoLite Country database.
3247 - Set the listen() backlog limit to the largest actually supported
3248 on the system, not to the value in a header file. Fixes bug 9716;
3249 bugfix on every released Tor.
3250 - No longer accept malformed http headers when parsing urls from
3251 headers. Now we reply with Bad Request ("400"). Fixes bug 2767;
3252 bugfix on 0.0.6pre1.
3253 - In munge_extrainfo_into_routerinfo(), check the return value of
3254 memchr(). This would have been a serious issue if we ever passed
3255 it a non-extrainfo. Fixes bug 8791; bugfix on 0.2.0.6-alpha. Patch
3257 - On the chance that somebody manages to build Tor on a
3258 platform where time_t is unsigned, correct the way that
3259 microdesc_add_to_cache() handles negative time arguments.
3260 Fixes bug 8042; bugfix on 0.2.3.1-alpha.
3261 - Reject relative control socket paths and emit a warning. Previously,
3262 single-component control socket paths would be rejected, but Tor
3263 would not log why it could not validate the config. Fixes bug 9258;
3264 bugfix on 0.2.3.16-alpha.
3266 o Minor bugfixes (command line):
3267 - Use a single command-line parser for parsing torrc options on the
3268 command line and for finding special command-line options to avoid
3269 inconsistent behavior for torrc option arguments that have the same
3270 names as command-line options. Fixes bugs 4647 and 9578; bugfix on
3272 - No longer allow 'tor --hash-password' with no arguments. Fixes bug
3273 9573; bugfix on 0.0.9pre5.
3275 o Minor fixes (build, auxiliary programs):
3276 - Stop preprocessing the "torify" script with autoconf, since
3277 it no longer refers to LOCALSTATEDIR. Fixes bug 5505; patch
3279 - The tor-fw-helper program now follows the standard convention and
3280 exits with status code "0" on success. Fixes bug 9030; bugfix on
3281 0.2.3.1-alpha. Patch by Arlo Breault.
3282 - Corrected ./configure advice for what openssl dev package you should
3283 install on Debian. Fixes bug 9207; bugfix on 0.2.0.1-alpha.
3285 o Minor code improvements:
3286 - Remove constants and tests for PKCS1 padding; it's insecure and
3287 shouldn't be used for anything new. Fixes bug 8792; patch
3289 - Remove instances of strcpy() from the unit tests. They weren't
3290 hurting anything, since they were only in the unit tests, but it's
3291 embarassing to have strcpy() in the code at all, and some analysis
3292 tools don't like it. Fixes bug 8790; bugfix on 0.2.3.6-alpha and
3293 0.2.3.8-alpha. Patch from Arlo Breault.
3296 - Remove migration code from when we renamed the "cached-routers"
3297 file to "cached-descriptors" back in 0.2.0.8-alpha. This
3298 incidentally resolves ticket 6502 by cleaning up the related code
3299 a bit. Patch from Akshay Hebbar.
3301 o Code simplification and refactoring:
3302 - Extract the common duplicated code for creating a subdirectory
3303 of the data directory and writing to a file in it. Fixes ticket
3304 4282; patch from Peter Retzlaff.
3305 - Since OpenSSL 0.9.7, the i2d_*() functions support allocating output
3306 buffer. Avoid calling twice: i2d_RSAPublicKey(), i2d_DHparams(),
3307 i2d_X509(), and i2d_PublicKey(). Resolves ticket 5170.
3308 - Add a set of accessor functions for the circuit timeout data
3309 structure. Fixes ticket 6153; patch from "piet".
3310 - Clean up exit paths from connection_listener_new(). Closes ticket
3311 8789. Patch from Arlo Breault.
3312 - Since we rely on OpenSSL 0.9.8 now, we can use EVP_PKEY_cmp()
3313 and drop our own custom pkey_eq() implementation. Fixes bug 9043.
3314 - Use a doubly-linked list to implement the global circuit list.
3315 Resolves ticket 9108. Patch from Marek Majkowski.
3316 - Remove contrib/id_to_fp.c since it wasn't used anywhere.
3319 Changes in version 0.2.4.17-rc - 2013-09-05
3320 Tor 0.2.4.17-rc is the third release candidate for the Tor 0.2.4.x
3321 series. It adds an emergency step to help us tolerate the massive
3322 influx of users: 0.2.4 clients using the new (faster and safer) "NTor"
3323 circuit-level handshakes now effectively jump the queue compared to
3324 the 0.2.3 clients using "TAP" handshakes. This release also fixes a
3325 big bug hindering bridge reachability tests.
3328 - Relays now process the new "NTor" circuit-level handshake requests
3329 with higher priority than the old "TAP" circuit-level handshake
3330 requests. We still process some TAP requests to not totally starve
3331 0.2.3 clients when NTor becomes popular. A new consensus parameter
3332 "NumNTorsPerTAP" lets us tune the balance later if we need to.
3333 Implements ticket 9574.
3336 - If the circuit build timeout logic is disabled (via the consensus,
3337 or because we are an authority), then don't build testing circuits.
3338 Fixes bug 9657; bugfix on 0.2.2.14-alpha.
3339 - Bridges now send AUTH_CHALLENGE cells during their v3 handshakes;
3340 previously they did not, which prevented them from receiving
3341 successful connections from relays for self-test or bandwidth
3342 testing. Also, when a relay is extending a circuit to a bridge,
3343 it needs to send a NETINFO cell, even when the bridge hasn't sent
3344 an AUTH_CHALLENGE cell. Fixes bug 9546; bugfix on 0.2.3.6-alpha.
3345 - If the time to download the next old-style networkstatus is in
3346 the future, do not decline to consider whether to download the
3347 next microdescriptor networkstatus. Fixes bug 9564; bugfix on
3351 - Avoid double-closing the listener socket in our socketpair()
3352 replacement (used on Windows) in the case where the addresses on
3353 our opened sockets don't match what we expected. Fixes bug 9400;
3354 bugfix on 0.0.2pre7. Found by Coverity.
3356 o Minor fixes (config options):
3357 - Avoid overflows when the user sets MaxCircuitDirtiness to a
3358 ridiculously high value, by imposing a (ridiculously high) 30-day
3359 maximum on MaxCircuitDirtiness.
3360 - Fix the documentation of HeartbeatPeriod to say that the heartbeat
3361 message is logged at notice, not at info.
3362 - Warn and fail if a server is configured not to advertise any
3363 ORPorts at all. (We need *something* to put in our descriptor,
3364 or we just won't work.)
3367 - Track how many "TAP" and "NTor" circuit handshake requests we get,
3368 and how many we complete, and log it every hour to help relay
3369 operators follow trends in network load. Addresses ticket 9658.
3370 - Update to the August 7 2013 Maxmind GeoLite Country database.
3373 Changes in version 0.2.4.16-rc - 2013-08-10
3374 Tor 0.2.4.16-rc is the second release candidate for the Tor 0.2.4.x
3375 series. It fixes several crash bugs in the 0.2.4 branch.
3378 - Fix a bug in the voting algorithm that could yield incorrect results
3379 when a non-naming authority declared too many flags. Fixes bug 9200;
3380 bugfix on 0.2.0.3-alpha.
3381 - Fix an uninitialized read that could in some cases lead to a remote
3382 crash while parsing INTRODUCE2 cells. Bugfix on 0.2.4.1-alpha.
3383 Anybody running a hidden service on the experimental 0.2.4.x
3384 branch should upgrade. (This is, so far as we know, unrelated to
3386 - Avoid an assertion failure when processing DNS replies without the
3387 answer types we expected. Fixes bug 9337; bugfix on 0.2.4.7-alpha.
3388 - Avoid a crash when using --hash-password. Fixes bug 9295; bugfix on
3389 0.2.4.15-rc. Found by stem integration tests.
3392 - Fix an invalid memory read that occured when a pluggable
3393 transport proxy failed its configuration protocol.
3394 Fixes bug 9288; bugfix on 0.2.4.1-alpha.
3395 - When evaluating whether to use a connection that we haven't
3396 decided is canonical using a recent link protocol version,
3397 decide that it's canonical only if it used address _does_
3398 match the desired address. Fixes bug 9309; bugfix on
3399 0.2.4.4-alpha. Reported by skruffy.
3400 - Make the default behavior of NumDirectoryGuards be to track
3401 NumEntryGuards. Now a user who changes only NumEntryGuards will get
3402 the behavior she expects. Fixes bug 9354; bugfix on 0.2.4.8-alpha.
3403 - Fix a spurious compilation warning with some older versions of
3404 GCC on FreeBSD. Fixes bug 9254; bugfix on 0.2.4.14-alpha.
3407 - Update to the July 3 2013 Maxmind GeoLite Country database.
3410 Changes in version 0.2.4.15-rc - 2013-07-01
3411 Tor 0.2.4.15-rc is the first release candidate for the Tor 0.2.4.x
3412 series. It fixes a few smaller bugs, but generally appears stable.
3413 Please test it and let us know whether it is!
3416 - When receiving a new configuration file via the control port's
3417 LOADCONF command, do not treat the defaults file as absent.
3418 Fixes bug 9122; bugfix on 0.2.3.9-alpha.
3421 - Issue a warning when running with the bufferevents backend enabled.
3422 It's still not stable, and people should know that they're likely
3423 to hit unexpected problems. Closes ticket 9147.
3426 Changes in version 0.2.4.14-alpha - 2013-06-18
3427 Tor 0.2.4.14-alpha fixes a pair of client guard enumeration problems
3428 present in 0.2.4.13-alpha.
3431 - When we have too much memory queued in circuits (according to a new
3432 MaxMemInCellQueues option), close the circuits consuming the most
3433 memory. This prevents us from running out of memory as a relay if
3434 circuits fill up faster than they can be drained. Fixes bug 9063;
3435 bugfix on the 54th commit of Tor. This bug is a further fix beyond
3436 bug 6252, whose fix was merged into 0.2.3.21-rc.
3438 This change also fixes an earlier approach taken in 0.2.4.13-alpha,
3439 where we tried to solve this issue simply by imposing an upper limit
3440 on the number of queued cells for a single circuit. That approach
3441 proved to be problematic, since there are ways to provoke clients to
3442 send a number of cells in excess of any such reasonable limit. Fixes
3443 bug 9072; bugfix on 0.2.4.13-alpha.
3445 - Limit hidden service descriptors to at most ten introduction
3446 points, to slow one kind of guard enumeration. Fixes bug 9002;
3447 bugfix on 0.1.1.11-alpha.
3450 Changes in version 0.2.4.13-alpha - 2013-06-14
3451 Tor 0.2.4.13-alpha fixes a variety of potential remote crash
3452 vulnerabilities, makes socks5 username/password circuit isolation
3453 actually actually work (this time for sure!), and cleans up a bunch
3454 of other issues in preparation for a release candidate.
3456 o Major bugfixes (robustness):
3457 - Close any circuit that has too many cells queued on it. Fixes
3458 bug 9063; bugfix on the 54th commit of Tor. This bug is a further
3459 fix beyond bug 6252, whose fix was merged into 0.2.3.21-rc.
3460 - Prevent the get_freelists() function from running off the end of
3461 the list of freelists if it somehow gets an unrecognized
3462 allocation. Fixes bug 8844; bugfix on 0.2.0.16-alpha. Reported by
3464 - Avoid an assertion failure on OpenBSD (and perhaps other BSDs)
3465 when an exit connection with optimistic data succeeds immediately
3466 rather than returning EINPROGRESS. Fixes bug 9017; bugfix on
3468 - Fix a directory authority crash bug when building a consensus
3469 using an older consensus as its basis. Fixes bug 8833. Bugfix
3473 - Avoid a memory leak where we would leak a consensus body when we
3474 find that a consensus which we couldn't previously verify due to
3475 missing certificates is now verifiable. Fixes bug 8719; bugfix
3477 - We used to always request authority certificates by identity digest,
3478 meaning we'd get the newest one even when we wanted one with a
3479 different signing key. Then we would complain about being given
3480 a certificate we already had, and never get the one we really
3481 wanted. Now we use the "fp-sk/" resource as well as the "fp/"
3482 resource to request the one we want. Fixes bug 5595; bugfix on
3484 - Follow the socks5 protocol when offering username/password
3485 authentication. The fix for bug 8117 exposed this bug, and it
3486 turns out real-world applications like Pidgin do care. Bugfix on
3487 0.2.3.2-alpha; fixes bug 8879.
3488 - Prevent failures on Windows Vista and later when rebuilding the
3489 microdescriptor cache. Diagnosed by Robert Ransom. Fixes bug 8822;
3490 bugfix on 0.2.4.12-alpha.
3493 - Fix an impossible buffer overrun in the AES unit tests. Fixes
3494 bug 8845; bugfix on 0.2.0.7-alpha. Found by eugenis.
3495 - If for some reason we fail to write a microdescriptor while
3496 rebuilding the cache, do not let the annotations from that
3497 microdescriptor linger in the cache file, and do not let the
3498 microdescriptor stay recorded as present in its old location.
3499 Fixes bug 9047; bugfix on 0.2.2.6-alpha.
3500 - Fix a memory leak that would occur whenever a configuration
3501 option changed. Fixes bug 8718; bugfix on 0.2.3.3-alpha.
3502 - Paste the description for PathBias parameters from the man
3503 page into or.h, so the code documents them too. Fixes bug 7982;
3504 bugfix on 0.2.3.17-beta and 0.2.4.8-alpha.
3505 - Relays now treat a changed IPv6 ORPort as sufficient reason to
3506 publish an updated descriptor. Fixes bug 6026; bugfix on
3508 - When launching a resolve request on behalf of an AF_UNIX control
3509 socket, omit the address field of the new entry connection, used in
3510 subsequent controller events, rather than letting tor_dup_addr()
3511 set it to "<unknown address type>". Fixes bug 8639; bugfix on
3514 o Minor bugfixes (log messages):
3515 - Fix a scaling issue in the path bias accounting code that
3516 resulted in "Bug:" log messages from either
3517 pathbias_scale_close_rates() or pathbias_count_build_success().
3518 This represents a bugfix on a previous bugfix: the original fix
3519 attempted in 0.2.4.10-alpha was incomplete. Fixes bug 8235; bugfix
3521 - Give a less useless error message when the user asks for an IPv4
3522 address on an IPv6-only port, or vice versa. Fixes bug 8846; bugfix
3526 - Downgrade "unexpected SENDME" warnings to protocol-warn for 0.2.4.x,
3527 to tolerate bug 8093 for now.
3528 - Add an "ignoring-advertised-bws" boolean to the flag-threshold lines
3529 in directory authority votes to describe whether they have enough
3530 measured bandwidths to ignore advertised (relay descriptor)
3531 bandwidth claims. Resolves ticket 8711.
3532 - Update to the June 5 2013 Maxmind GeoLite Country database.
3534 o Removed documentation:
3535 - Remove some of the older contents of doc/ as obsolete; move others
3536 to torspec.git. Fixes bug 8965.
3538 o Code simplification and refactoring:
3539 - Avoid using character buffers when constructing most directory
3540 objects: this approach was unwieldy and error-prone. Instead,
3541 build smartlists of strings, and concatenate them when done.
3544 Changes in version 0.2.4.12-alpha - 2013-04-18
3545 Tor 0.2.4.12-alpha moves Tor forward on several fronts: it starts the
3546 process for lengthening the guard rotation period, makes directory
3547 authority opinions in the consensus a bit less gameable, makes socks5
3548 username/password circuit isolation actually work, and fixes a wide
3549 variety of other issues.
3552 - Raise the default time that a client keeps an entry guard from
3553 "1-2 months" to "2-3 months", as suggested by Tariq Elahi's WPES
3554 2012 paper. (We would make it even longer, but we need better client
3555 load balancing first.) Also, make the guard lifetime controllable
3556 via a new GuardLifetime torrc option and a GuardLifetime consensus
3557 parameter. Start of a fix for bug 8240; bugfix on 0.1.1.11-alpha.
3558 - Directory authorities now prefer using measured bandwidths to
3559 advertised ones when computing flags and thresholds. Resolves
3561 - Directory authorities that have more than a threshold number
3562 of relays with measured bandwidths now treat relays with unmeasured
3563 bandwidths as having bandwidth 0. Resolves ticket 8435.
3565 o Major bugfixes (assert / resource use):
3566 - Avoid a bug where our response to TLS renegotiation under certain
3567 network conditions could lead to a busy-loop, with 100% CPU
3568 consumption. Fixes bug 5650; bugfix on 0.2.0.16-alpha.
3569 - Avoid an assertion when we discover that we'd like to write a cell
3570 onto a closing connection: just discard the cell. Fixes another
3571 case of bug 7350; bugfix on 0.2.4.4-alpha.
3573 o Major bugfixes (client-side privacy):
3574 - When we mark a circuit as unusable for new circuits, have it
3575 continue to be unusable for new circuits even if MaxCircuitDirtiness
3576 is increased too much at the wrong time, or the system clock jumps
3577 backwards. Fixes bug 6174; bugfix on 0.0.2pre26.
3578 - If ClientDNSRejectInternalAddresses ("do not believe DNS queries
3579 which have resolved to internal addresses") is set, apply that
3580 rule to IPv6 as well. Fixes bug 8475; bugfix on 0.2.0.7-alpha.
3581 - When an exit relay rejects a stream with reason "exit policy", but
3582 we only know an exit policy summary (e.g. from the microdesc
3583 consensus) for it, do not mark the relay as useless for all exiting.
3584 Instead, mark just the circuit as unsuitable for that particular
3585 address. Fixes part of bug 7582; bugfix on 0.2.3.2-alpha.
3586 - Allow applications to get proper stream isolation with
3587 IsolateSOCKSAuth. Many SOCKS5 clients that want to offer
3588 username/password authentication also offer "no authentication". Tor
3589 had previously preferred "no authentication", so the applications
3590 never actually sent Tor their auth details. Now Tor selects
3591 username/password authentication if it's offered. You can disable
3592 this behavior on a per-SOCKSPort basis via PreferSOCKSNoAuth. Fixes
3593 bug 8117; bugfix on 0.2.3.3-alpha.
3595 o Major bugfixes (other):
3596 - When unable to find any working directory nodes to use as a
3597 directory guard, give up rather than adding the same non-working
3598 nodes to the directory guard list over and over. Fixes bug 8231;
3599 bugfix on 0.2.4.8-alpha.
3602 - Reject as invalid most directory objects containing a NUL.
3603 Belt-and-suspender fix for bug 8037.
3604 - In our testsuite, create temporary directories with a bit more
3605 entropy in their name to make name collisions less likely. Fixes
3607 - Add CACHED keyword to ADDRMAP events in the control protocol
3608 to indicate whether a DNS result will be cached or not. Resolves
3610 - Update to the April 3 2013 Maxmind GeoLite Country database.
3612 o Minor features (build):
3613 - Detect and reject attempts to build Tor with threading support
3614 when OpenSSL has been compiled without threading support.
3616 - Clarify that when autoconf is checking for nacl, it is checking
3617 specifically for nacl with a fast curve25519 implementation.
3619 - Warn if building on a platform with an unsigned time_t: there
3620 are too many places where Tor currently assumes that time_t can
3621 hold negative values. We'd like to fix them all, but probably
3624 o Minor bugfixes (build):
3625 - Fix some bugs in tor-fw-helper-natpmp when trying to build and
3626 run it on Windows. More bugs likely remain. Patch from Gisle Vanem.
3627 Fixes bug 7280; bugfix on 0.2.3.1-alpha.
3628 - Add the old src/or/micro-revision.i filename to CLEANFILES.
3629 On the off chance that somebody has one, it will go away as soon
3630 as they run "make clean". Fix for bug 7143; bugfix on 0.2.4.1-alpha.
3631 - Build Tor correctly on 32-bit platforms where the compiler can build
3632 but not run code using the "uint128_t" construction. Fixes bug 8587;
3633 bugfix on 0.2.4.8-alpha.
3634 - Fix compilation warning with some versions of clang that would
3635 prefer the -Wswitch-enum compiler flag to warn about switch
3636 statements with missing enum values, even if those switch
3637 statements have a "default:" statement. Fixes bug 8598; bugfix
3640 o Minor bugfixes (protocol):
3641 - Fix the handling of a TRUNCATE cell when it arrives while the
3642 circuit extension is in progress. Fixes bug 7947; bugfix on 0.0.7.1.
3643 - Fix a misframing issue when reading the version numbers in a
3644 VERSIONS cell. Previously we would recognize [00 01 00 02] as
3645 'version 1, version 2, and version 0x100', when it should have
3646 only included versions 1 and 2. Fixes bug 8059; bugfix on
3647 0.2.0.10-alpha. Reported pseudonymously.
3648 - Make the format and order of STREAM events for DNS lookups
3649 consistent among the various ways to launch DNS lookups. Fixes
3650 bug 8203; bugfix on 0.2.0.24-rc. Patch by "Desoxy."
3651 - Correct our check for which versions of Tor support the EXTEND2
3652 cell. We had been willing to send it to Tor 0.2.4.7-alpha and
3653 later, when support was really added in version 0.2.4.8-alpha.
3654 Fixes bug 8464; bugfix on 0.2.4.8-alpha.
3656 o Minor bugfixes (other):
3657 - Correctly store microdescriptors and extrainfo descriptors with
3658 an internal NUL byte. Fixes bug 8037; bugfix on 0.2.0.1-alpha.
3659 Bug reported by "cypherpunks".
3660 - Increase the width of the field used to remember a connection's
3661 link protocol version to two bytes. Harmless for now, since the
3662 only currently recognized versions are one byte long. Reported
3663 pseudonymously. Fixes bug 8062; bugfix on 0.2.0.10-alpha.
3664 - If the state file's path bias counts are invalid (presumably from a
3665 buggy Tor prior to 0.2.4.10-alpha), make them correct. Also add
3666 additional checks and log messages to the scaling of Path Bias
3667 counts, in case there still are remaining issues with scaling.
3668 Should help resolve bug 8235.
3669 - Eliminate several instances where we use "Nickname=ID" to refer to
3670 nodes in logs. Use "Nickname (ID)" instead. (Elsewhere, we still use
3671 "$ID=Nickname", which is also acceptable.) Fixes bug 7065. Bugfix
3672 on 0.2.3.21-rc, 0.2.4.5-alpha, 0.2.4.8-alpha, and 0.2.4.10-alpha.
3674 o Minor bugfixes (syscalls):
3675 - Always check the return values of functions fcntl() and
3676 setsockopt(). We don't believe these are ever actually failing in
3677 practice, but better safe than sorry. Also, checking these return
3678 values should please analysis tools like Coverity. Patch from
3679 'flupzor'. Fixes bug 8206; bugfix on all versions of Tor.
3680 - Use direct writes rather than stdio when building microdescriptor
3681 caches, in an attempt to mitigate bug 8031, or at least make it
3684 o Minor bugfixes (config):
3685 - When rejecting a configuration because we were unable to parse a
3686 quoted string, log an actual error message. Fixes bug 7950; bugfix
3688 - Behave correctly when the user disables LearnCircuitBuildTimeout
3689 but doesn't tell us what they would like the timeout to be. Fixes
3690 bug 6304; bugfix on 0.2.2.14-alpha.
3691 - When autodetecting the number of CPUs, use the number of available
3692 CPUs in preference to the number of configured CPUs. Inform the
3693 user if this reduces the number of available CPUs. Fixes bug 8002;
3694 bugfix on 0.2.3.1-alpha.
3695 - Make it an error when you set EntryNodes but disable UseGuardNodes,
3696 since it will (surprisingly to some users) ignore EntryNodes. Fixes
3697 bug 8180; bugfix on 0.2.3.11-alpha.
3698 - Allow TestingTorNetworks to override the 4096-byte minimum for
3699 the Fast threshold. Otherwise they can't bootstrap until they've
3700 observed more traffic. Fixes bug 8508; bugfix on 0.2.4.10-alpha.
3701 - Fix some logic errors when the user manually overrides the
3702 PathsNeededToBuildCircuits option in torrc. Fixes bug 8599; bugfix
3705 o Minor bugfixes (log messages to help diagnose bugs):
3706 - If we fail to free a microdescriptor because of bug 7164, log
3707 the filename and line number from which we tried to free it.
3708 - Add another diagnostic to the heartbeat message: track and log
3709 overhead that TLS is adding to the data we write. If this is
3710 high, we are sending too little data to SSL_write at a time.
3711 Diagnostic for bug 7707.
3712 - Add more detail to a log message about relaxed timeouts, to help
3714 - Warn more aggressively when flushing microdescriptors to a
3715 microdescriptor cache fails, in an attempt to mitigate bug 8031,
3716 or at least make it more diagnosable.
3717 - Improve debugging output to help track down bug 8185 ("Bug:
3718 outgoing relay cell has n_chan==NULL. Dropping.")
3719 - Log the purpose of a path-bias testing circuit correctly.
3720 Improves a log message from bug 8477; bugfix on 0.2.4.8-alpha.
3722 o Minor bugfixes (0.2.4.x log messages that were too noisy):
3723 - Don't attempt to relax the timeout of already opened 1-hop circuits.
3724 They might never timeout. This should eliminate some/all cases of
3725 the relaxed timeout log message.
3726 - Use circuit creation time for network liveness evaluation. This
3727 should eliminate warning log messages about liveness caused
3728 by changes in timeout evaluation. Fixes bug 6572; bugfix on
3730 - Reduce a path bias length check from notice to info. The message
3731 is triggered when creating controller circuits. Fixes bug 8196;
3732 bugfix on 0.2.4.8-alpha.
3733 - Fix a path state issue that triggered a notice during relay startup.
3734 Fixes bug 8320; bugfix on 0.2.4.10-alpha.
3735 - Reduce occurrences of warns about circuit purpose in
3736 connection_ap_expire_building(). Fixes bug 8477; bugfix on
3739 o Minor bugfixes (pre-0.2.4.x log messages that were too noisy):
3740 - If we encounter a write failure on a SOCKS connection before we
3741 finish our SOCKS handshake, don't warn that we closed the
3742 connection before we could send a SOCKS reply. Fixes bug 8427;
3743 bugfix on 0.1.0.1-rc.
3744 - Correctly recognize that [::1] is a loopback address. Fixes
3745 bug 8377; bugfix on 0.2.1.3-alpha.
3746 - Fix a directory authority warn caused when we have a large amount
3747 of badexit bandwidth. Fixes bug 8419; bugfix on 0.2.2.10-alpha.
3748 - Don't log inappropriate heartbeat messages when hibernating: a
3749 hibernating node is _expected_ to drop out of the consensus,
3750 decide it isn't bootstrapped, and so forth. Fixes bug 7302;
3751 bugfix on 0.2.3.1-alpha.
3752 - Don't complain about bootstrapping problems while hibernating.
3753 These complaints reflect a general code problem, but not one
3754 with any problematic effects (no connections are actually
3755 opened). Fixes part of bug 7302; bugfix on 0.2.3.2-alpha.
3757 o Documentation fixes:
3758 - Update tor-fw-helper.1.txt and tor-fw-helper.c to make option
3759 names match. Fixes bug 7768.
3760 - Make the torify manpage no longer refer to tsocks; torify hasn't
3761 supported tsocks since 0.2.3.14-alpha.
3762 - Make the tor manpage no longer reference tsocks.
3763 - Fix the GeoIPExcludeUnknown documentation to refer to
3764 ExcludeExitNodes rather than the currently nonexistent
3765 ExcludeEntryNodes. Spotted by "hamahangi" on tor-talk.
3768 - The tor-tsocks.conf is no longer distributed or installed. We
3769 recommend that tsocks users use torsocks instead. Resolves
3773 Changes in version 0.2.4.11-alpha - 2013-03-11
3774 Tor 0.2.4.11-alpha makes relay measurement by directory authorities
3775 more robust, makes hidden service authentication work again, and
3776 resolves a DPI fingerprint for Tor's SSL transport.
3778 o Major features (directory authorities):
3779 - Directory authorities now support a new consensus method (17)
3780 where they cap the published bandwidth of servers for which
3781 insufficient bandwidth measurements exist. Fixes part of bug 2286.
3782 - Directory authorities that set "DisableV2DirectoryInfo_ 1" no longer
3783 serve any v2 directory information. Now we can test disabling the
3784 old deprecated v2 directory format, and see whether doing so has
3785 any effect on network load. Begins to fix bug 6783.
3786 - Directory authorities now include inside each vote a statement of
3787 the performance thresholds they used when assigning flags.
3788 Implements ticket 8151.
3790 o Major bugfixes (directory authorities):
3791 - Stop marking every relay as having been down for one hour every
3792 time we restart a directory authority. These artificial downtimes
3793 were messing with our Stable and Guard flag calculations. Fixes
3794 bug 8218 (introduced by the fix for 1035). Bugfix on 0.2.2.23-alpha.
3796 o Major bugfixes (hidden services):
3797 - Allow hidden service authentication to succeed again. When we
3798 refactored the hidden service introduction code back
3799 in 0.2.4.1-alpha, we didn't update the code that checks
3800 whether authentication information is present, causing all
3801 authentication checks to return "false". Fix for bug 8207; bugfix
3802 on 0.2.4.1-alpha. Found by Coverity; this is CID 718615.
3804 o Minor features (relays, bridges):
3805 - Make bridge relays check once a minute for whether their IP
3806 address has changed, rather than only every 15 minutes. Resolves
3808 - Refactor resolve_my_address() so it returns the method by which we
3809 decided our public IP address (explicitly configured, resolved from
3810 explicit hostname, guessed from interfaces, learned by gethostname).
3811 Now we can provide more helpful log messages when a relay guesses
3812 its IP address incorrectly (e.g. due to unexpected lines in
3813 /etc/hosts). Resolves ticket 2267.
3814 - Teach bridge-using clients to avoid 0.2.2 bridges when making
3815 microdescriptor-related dir requests, and only fall back to normal
3816 descriptors if none of their bridges can handle microdescriptors
3817 (as opposed to the fix in ticket 4013, which caused them to fall
3818 back to normal descriptors if *any* of their bridges preferred
3819 them). Resolves ticket 4994.
3820 - Randomize the lifetime of our SSL link certificate, so censors can't
3821 use the static value for filtering Tor flows. Resolves ticket 8443;
3822 related to ticket 4014 which was included in 0.2.2.33.
3823 - Support a new version of the link protocol that allows 4-byte circuit
3824 IDs. Previously, circuit IDs were limited to 2 bytes, which presented
3825 a possible resource exhaustion issue. Closes ticket 7351; implements
3828 o Minor features (portability):
3829 - Tweak the curve25519-donna*.c implementations to tolerate systems
3830 that lack stdint.h. Fixes bug 3894; bugfix on 0.2.4.8-alpha.
3831 - Use Ville Laurikari's implementation of AX_CHECK_SIGN() to determine
3832 the signs of types during autoconf. This is better than our old
3833 approach, which didn't work when cross-compiling.
3834 - Detect the sign of enum values, rather than assuming that MSC is the
3835 only compiler where enum types are all signed. Fixes bug 7727;
3836 bugfix on 0.2.4.10-alpha.
3838 o Minor features (other):
3839 - Say "KBytes" rather than "KB" in the man page (for various values
3840 of K), to further reduce confusion about whether Tor counts in
3841 units of memory or fractions of units of memory. Resolves ticket 7054.
3842 - Clear the high bit on curve25519 public keys before passing them to
3843 our backend, in case we ever wind up using a backend that doesn't do
3844 so itself. If we used such a backend, and *didn't* clear the high bit,
3845 we could wind up in a situation where users with such backends would
3846 be distinguishable from users without. Fixes bug 8121; bugfix on
3848 - Update to the March 6 2013 Maxmind GeoLite Country database.
3850 o Minor bugfixes (clients):
3851 - When we receive a RELAY_END cell with the reason DONE, or with no
3852 reason, before receiving a RELAY_CONNECTED cell, report the SOCKS
3853 status as "connection refused". Previously we reported these cases
3854 as success but then immediately closed the connection. Fixes bug
3855 7902; bugfix on 0.1.0.1-rc. Reported by "oftc_must_be_destroyed".
3856 - Downgrade an assertion in connection_ap_expire_beginning to an
3857 LD_BUG message. The fix for bug 8024 should prevent this message
3858 from displaying, but just in case, a warn that we can diagnose
3859 is better than more assert crashes. Fixes bug 8065; bugfix on
3861 - Lower path use bias thresholds to .80 for notice and .60 for warn.
3862 Also make the rate limiting flags for the path use bias log messages
3863 independent from the original path bias flags. Fixes bug 8161;
3864 bugfix on 0.2.4.10-alpha.
3866 o Minor bugfixes (relays):
3867 - Stop trying to resolve our hostname so often (e.g. every time we
3868 think about doing a directory fetch). Now we reuse the cached
3869 answer in some cases. Fixes bugs 1992 (bugfix on 0.2.0.20-rc)
3870 and 2410 (bugfix on 0.1.2.2-alpha).
3871 - Stop sending a stray "(null)" in some cases for the server status
3872 "EXTERNAL_ADDRESS" controller event. Resolves bug 8200; bugfix
3874 - When choosing which stream on a formerly stalled circuit to wake
3875 first, make better use of the platform's weak RNG. Previously,
3876 we had been using the % ("modulo") operator to try to generate a
3877 1/N chance of picking each stream, but this behaves badly with
3878 many platforms' choice of weak RNG. Fixes bug 7801; bugfix on
3880 - Use our own weak RNG when we need a weak RNG. Windows's rand() and
3881 Irix's random() only return 15 bits; Solaris's random() returns more
3882 bits but its RAND_MAX says it only returns 15, and so on. Motivated
3883 by the fix for bug 7801; bugfix on 0.2.2.20-alpha.
3885 o Minor bugfixes (directory authorities):
3886 - Directory authorities now use less space when formatting identical
3887 microdescriptor lines in directory votes. Fixes bug 8158; bugfix
3890 o Minor bugfixes (memory leaks spotted by Coverity -- bug 7816):
3891 - Avoid leaking memory if we fail to compute a consensus signature
3892 or we generate a consensus we can't parse. Bugfix on 0.2.0.5-alpha.
3893 - Fix a memory leak when receiving headers from an HTTPS proxy. Bugfix
3895 - Fix a memory leak during safe-cookie controller authentication.
3896 Bugfix on 0.2.3.13-alpha.
3897 - Avoid memory leak of IPv6 policy content if we fail to format it into
3898 a router descriptor. Bugfix on 0.2.4.7-alpha.
3900 o Minor bugfixes (other code correctness issues):
3901 - Avoid a crash if we fail to generate an extrainfo descriptor.
3902 Fixes bug 8208; bugfix on 0.2.3.16-alpha. Found by Coverity;
3904 - When detecting the largest possible file descriptor (in order to
3905 close all file descriptors when launching a new program), actually
3906 use _SC_OPEN_MAX. The old code for doing this was very, very broken.
3907 Fixes bug 8209; bugfix on 0.2.3.1-alpha. Found by Coverity; this
3909 - Fix a copy-and-paste error when adding a missing A1 to a routerset
3910 because of GeoIPExcludeUnknown. Fix for Coverity CID 980650.
3911 Bugfix on 0.2.4.10-alpha.
3912 - Fix an impossible-to-trigger integer overflow when estimating how
3913 long our onionskin queue would take. (This overflow would require us
3914 to accept 4 million onionskins before processing 100 of them.) Fixes
3915 bug 8210; bugfix on 0.2.4.10-alpha.
3917 o Code simplification and refactoring:
3918 - Add a wrapper function for the common "log a message with a
3922 Changes in version 0.2.4.10-alpha - 2013-02-04
3923 Tor 0.2.4.10-alpha adds defenses at the directory authority level from
3924 certain attacks that flood the network with relays; changes the queue
3925 for circuit create requests from a sized-based limit to a time-based
3926 limit; resumes building with MSVC on Windows; and fixes a wide variety
3929 o Major bugfixes (directory authority):
3930 - When computing directory thresholds, ignore any rejected-as-sybil
3931 nodes during the computation so that they can't influence Fast,
3932 Guard, etc. (We should have done this for proposal 109.) Fixes
3934 - When marking a node as a likely sybil, reset its uptime metrics
3935 to zero, so that it cannot time towards getting marked as Guard,
3936 Stable, or HSDir. (We should have done this for proposal 109.) Fixes
3940 - When a TLS write is partially successful but incomplete, remember
3941 that the flushed part has been flushed, and notice that bytes were
3942 actually written. Reported and fixed pseudonymously. Fixes bug
3943 7708; bugfix on Tor 0.1.0.5-rc.
3944 - Reject bogus create and relay cells with 0 circuit ID or 0 stream
3945 ID: these could be used to create unexpected streams and circuits
3946 which would count as "present" to some parts of Tor but "absent"
3947 to others, leading to zombie circuits and streams or to a bandwidth
3948 denial-of-service. Fixes bug 7889; bugfix on every released version
3949 of Tor. Reported by "oftc_must_be_destroyed".
3950 - Rename all macros in our local copy of queue.h to begin with "TOR_".
3951 This change seems the only good way to permanently prevent conflicts
3952 with queue.h on various operating systems. Fixes bug 8107; bugfix
3955 o Major features (relay):
3956 - Instead of limiting the number of queued onionskins (aka circuit
3957 create requests) to a fixed, hard-to-configure number, we limit
3958 the size of the queue based on how many we expect to be able to
3959 process in a given amount of time. We estimate the time it will
3960 take to process an onionskin based on average processing time
3961 of previous onionskins. Closes ticket 7291. You'll never have to
3962 configure MaxOnionsPending again.
3964 o Major features (portability):
3965 - Resume building correctly with MSVC and Makefile.nmake. This patch
3966 resolves numerous bugs and fixes reported by ultramage, including
3967 7305, 7308, 7309, 7310, 7312, 7313, 7315, 7316, and 7669.
3968 - Make the ntor and curve25519 code build correctly with MSVC.
3969 Fix on 0.2.4.8-alpha.
3972 - When directory authorities are computing thresholds for flags,
3973 never let the threshold for the Fast flag fall below 4096
3974 bytes. Also, do not consider nodes with extremely low bandwidths
3975 when deciding thresholds for various directory flags. This change
3976 should raise our threshold for Fast relays, possibly in turn
3977 improving overall network performance; see ticket 1854. Resolves
3979 - The Tor client now ignores sub-domain components of a .onion
3980 address. This change makes HTTP "virtual" hosting
3981 possible: http://foo.aaaaaaaaaaaaaaaa.onion/ and
3982 http://bar.aaaaaaaaaaaaaaaa.onion/ can be two different websites
3983 hosted on the same hidden service. Implements proposal 204.
3984 - We compute the overhead from passing onionskins back and forth to
3985 cpuworkers, and report it when dumping statistics in response to
3986 SIGUSR1. Supports ticket 7291.
3988 o Minor features (path selection):
3989 - When deciding whether we have enough descriptors to build circuits,
3990 instead of looking at raw relay counts, look at which fraction
3991 of (bandwidth-weighted) paths we're able to build. This approach
3992 keeps clients from building circuits if their paths are likely to
3993 stand out statistically. The default fraction of paths needed is
3994 taken from the consensus directory; you can override it with the
3995 new PathsNeededToBuildCircuits option. Fixes ticket 5956.
3996 - When any country code is listed in ExcludeNodes or ExcludeExitNodes,
3997 and we have GeoIP information, also exclude all nodes with unknown
3998 countries "??" and "A1". This behavior is controlled by the
3999 new GeoIPExcludeUnknown option: you can make such nodes always
4000 excluded with "GeoIPExcludeUnknown 1", and disable the feature
4001 with "GeoIPExcludeUnknown 0". Setting "GeoIPExcludeUnknown auto"
4002 gets you the default behavior. Implements feature 7706.
4003 - Path Use Bias: Perform separate accounting for successful circuit
4004 use. Keep separate statistics on stream attempt rates versus stream
4005 success rates for each guard. Provide configurable thresholds to
4006 determine when to emit log messages or disable use of guards that
4007 fail too many stream attempts. Resolves ticket 7802.
4009 o Minor features (log messages):
4010 - When learning a fingerprint for a bridge, log its corresponding
4011 transport type. Implements ticket 7896.
4012 - Improve the log message when "Bug/attack: unexpected sendme cell
4013 from client" occurs, to help us track bug 8093.
4016 - Remove a couple of extraneous semicolons that were upsetting the
4017 cparser library. Patch by Christian Grothoff. Fixes bug 7115;
4018 bugfix on 0.2.2.1-alpha.
4019 - Remove a source of rounding error during path bias count scaling;
4020 don't count cannibalized circuits as used for path bias until we
4021 actually try to use them; and fix a circuit_package_relay_cell()
4022 warning message about n_chan==NULL. Fixes bug 7802.
4023 - Detect nacl when its headers are in a nacl/ subdirectory. Also,
4024 actually link against nacl when we're configured to use it. Fixes
4025 bug 7972; bugfix on 0.2.4.8-alpha.
4026 - Compile correctly with the --disable-curve25519 option. Fixes
4027 bug 8153; bugfix on 0.2.4.8-alpha.
4029 o Build improvements:
4030 - Do not report status verbosely from autogen.sh unless the -v flag
4031 is specified. Fixes issue 4664. Patch from Onizuka.
4032 - Replace all calls to snprintf() outside of src/ext with
4033 tor_snprintf(). Also remove the #define to replace snprintf with
4034 _snprintf on Windows; they have different semantics, and all of
4035 our callers should be using tor_snprintf() anyway. Fixes bug 7304.
4036 - Try to detect if we are ever building on a platform where
4037 memset(...,0,...) does not set the value of a double to 0.0. Such
4038 platforms are permitted by the C standard, though in practice
4039 they're pretty rare (since IEEE 754 is nigh-ubiquitous). We don't
4040 currently support them, but it's better to detect them and fail
4041 than to perform erroneously.
4044 - Stop exporting estimates of v2 and v3 directory traffic shares
4045 in extrainfo documents. They were unneeded and sometimes inaccurate.
4046 Also stop exporting any v2 directory request statistics. Resolves
4048 - Drop support for detecting and warning about versions of Libevent
4049 before 1.3e. Nothing reasonable ships with them any longer;
4050 warning the user about them shouldn't be needed. Resolves ticket
4053 o Code simplifications and refactoring:
4054 - Rename "isin" functions to "contains", for grammar. Resolves
4056 - Rename Tor's logging function log() to tor_log(), to avoid conflicts
4057 with the natural logarithm function from the system libm. Resolves
4061 Changes in version 0.2.4.9-alpha - 2013-01-15
4062 Tor 0.2.4.9-alpha provides a quick fix to make the new ntor handshake
4066 - Fix backward compatibility logic when receiving an embedded ntor
4067 handshake tunneled in a CREATE cell. This clears up the "Bug:
4068 couldn't format CREATED cell" warning. Fixes bug 7959; bugfix
4072 Changes in version 0.2.4.8-alpha - 2013-01-14
4073 Tor 0.2.4.8-alpha introduces directory guards to reduce user enumeration
4074 risks, adds a new stronger and faster circuit handshake, and offers
4075 stronger and faster link encryption when both sides support it.
4078 - Preliminary support for directory guards (proposal 207): when
4079 possible, clients now use their entry guards for non-anonymous
4080 directory requests. This can help prevent client enumeration. Note
4081 that this behavior only works when we have a usable consensus
4082 directory, and when options about what to download are more or less
4083 standard. In the future we should re-bootstrap from our guards,
4084 rather than re-bootstrapping from the preconfigured list of
4085 directory sources that ships with Tor. Resolves ticket 6526.
4086 - Tor relays and clients now support a better CREATE/EXTEND cell
4087 format, allowing the sender to specify multiple address, identity,
4088 and handshake types. Implements Robert Ransom's proposal 200;
4091 o Major features (new circuit handshake):
4092 - Tor now supports a new circuit extension handshake designed by Ian
4093 Goldberg, Douglas Stebila, and Berkant Ustaoglu. Our original
4094 circuit extension handshake, later called "TAP", was a bit slow
4095 (especially on the relay side), had a fragile security proof, and
4096 used weaker keys than we'd now prefer. The new circuit handshake
4097 uses Dan Bernstein's "curve25519" elliptic-curve Diffie-Hellman
4098 function, making it significantly more secure than the older
4099 handshake, and significantly faster. Tor can use one of two built-in
4100 pure-C curve25519-donna implementations by Adam Langley, or it
4101 can link against the "nacl" library for a tuned version if present.
4103 The built-in version is very fast for 64-bit systems when building
4104 with GCC. The built-in 32-bit version is still faster than the
4105 old TAP protocol, but using libnacl is better on most such hosts.
4107 Clients don't currently use this protocol by default, since
4108 comparatively few clients support it so far. To try it, set
4109 UseNTorHandshake to 1.
4111 Implements proposal 216; closes ticket 7202.
4113 o Major features (better link encryption):
4114 - Relays can now enable the ECDHE TLS ciphersuites when available
4115 and appropriate. These ciphersuites let us negotiate forward-secure
4116 TLS secret keys more safely and more efficiently than with our
4117 previous use of Diffie-Hellman modulo a 1024-bit prime. By default,
4118 public relays prefer the (faster) P224 group, and bridges prefer
4119 the (more common) P256 group; you can override this with the
4122 Enabling these ciphers was a little tricky, since for a long time,
4123 clients had been claiming to support them without actually doing
4124 so, in order to foil fingerprinting. But with the client-side
4125 implementation of proposal 198 in 0.2.3.17-beta, clients can now
4126 match the ciphers from recent Firefox versions *and* list the
4127 ciphers they actually mean, so relays can believe such clients
4128 when they advertise ECDHE support in their TLS ClientHello messages.
4130 This feature requires clients running 0.2.3.17-beta or later,
4131 and requires both sides to be running OpenSSL 1.0.0 or later
4132 with ECC support. OpenSSL 1.0.1, with the compile-time option
4133 "enable-ec_nistp_64_gcc_128", is highly recommended.
4135 Implements the relay side of proposal 198; closes ticket 7200.
4138 - Avoid crashing when, as a relay without IPv6-exit support, a
4139 client insists on getting an IPv6 address or nothing. Fixes bug
4140 7814; bugfix on 0.2.4.7-alpha.
4143 - Improve circuit build timeout handling for hidden services.
4144 In particular: adjust build timeouts more accurately depending
4145 upon the number of hop-RTTs that a particular circuit type
4146 undergoes. Additionally, launch intro circuits in parallel
4147 if they timeout, and take the first one to reply as valid.
4148 - Work correctly on Unix systems where EAGAIN and EWOULDBLOCK are
4149 separate error codes; or at least, don't break for that reason.
4150 Fixes bug 7935. Reported by "oftc_must_be_destroyed".
4151 - Update to the January 2 2013 Maxmind GeoLite Country database.
4153 o Minor features (testing):
4154 - Add benchmarks for DH (1024-bit multiplicative group) and ECDH
4155 (P-256) Diffie-Hellman handshakes to src/or/bench.
4156 - Add benchmark functions to test onion handshake performance.
4158 o Minor features (path bias detection):
4159 - Alter the Path Bias log messages to be more descriptive in terms
4160 of reporting timeouts and other statistics.
4161 - Create three levels of Path Bias log messages, as opposed to just
4162 two. These are configurable via consensus as well as via the torrc
4163 options PathBiasNoticeRate, PathBiasWarnRate, PathBiasExtremeRate.
4164 The default values are 0.70, 0.50, and 0.30 respectively.
4165 - Separate the log message levels from the decision to drop guards,
4166 which also is available via torrc option PathBiasDropGuards.
4167 PathBiasDropGuards still defaults to 0 (off).
4168 - Deprecate PathBiasDisableRate in favor of PathBiasDropGuards
4169 in combination with PathBiasExtremeRate.
4170 - Increase the default values for PathBiasScaleThreshold and
4171 PathBiasCircThreshold from (200, 20) to (300, 150).
4172 - Add in circuit usage accounting to path bias. If we try to use a
4173 built circuit but fail for any reason, it counts as path bias.
4174 Certain classes of circuits where the adversary gets to pick your
4175 destination node are exempt from this accounting. Usage accounting
4176 can be specifically disabled via consensus parameter or torrc.
4177 - Convert all internal path bias state to double-precision floating
4178 point, to avoid roundoff error and other issues.
4179 - Only record path bias information for circuits that have completed
4180 *two* hops. Assuming end-to-end tagging is the attack vector, this
4181 makes us more resilient to ambient circuit failure without any
4182 detection capability loss.
4184 o Minor bugfixes (log messages):
4185 - Rate-limit the "No circuits are opened. Relaxed timeout for a
4186 circuit with channel state open..." message to once per hour to
4187 keep it from filling the notice logs. Mitigates bug 7799 but does
4188 not fix the underlying cause. Bugfix on 0.2.4.7-alpha.
4189 - Avoid spurious warnings when configuring multiple client ports of
4190 which only some are nonlocal. Previously, we had claimed that some
4191 were nonlocal when in fact they weren't. Fixes bug 7836; bugfix on
4194 o Code simplifications and refactoring:
4195 - Get rid of a couple of harmless clang warnings, where we compared
4196 enums to ints. These warnings are newly introduced in clang 3.2.
4197 - Split the onion.c file into separate modules for the onion queue
4198 and the different handshakes it supports.
4199 - Remove the marshalling/unmarshalling code for sending requests to
4200 cpuworkers over a socket, and instead just send structs. The
4201 recipient will always be the same Tor binary as the sender, so
4202 any encoding is overkill.
4205 Changes in version 0.2.4.7-alpha - 2012-12-24
4206 Tor 0.2.4.7-alpha introduces a new approach to providing fallback
4207 directory mirrors for more robust bootstrapping; fixes more issues where
4208 clients with changing network conditions refuse to make any circuits;
4209 adds initial support for exiting to IPv6 addresses; resumes being able
4210 to update our GeoIP database, and includes the geoip6 file this time;
4211 turns off the client-side DNS cache by default due to privacy risks;
4212 and fixes a variety of other issues.
4214 o Major features (client resilience):
4215 - Add a new "FallbackDir" torrc option to use when we can't use
4216 a directory mirror from the consensus (either because we lack a
4217 consensus, or because they're all down). Currently, all authorities
4218 are fallbacks by default, and there are no other default fallbacks,
4219 but that will change. This option will allow us to give clients a
4220 longer list of servers to try to get a consensus from when first
4221 connecting to the Tor network, and thereby reduce load on the
4222 directory authorities. Implements proposal 206, "Preconfigured
4223 directory sources for bootstrapping". We also removed the old
4224 "FallbackNetworkstatus" option, since we never got it working well
4225 enough to use it. Closes bug 572.
4226 - If we have no circuits open, use a relaxed timeout (the
4227 95-percentile cutoff) until a circuit succeeds. This heuristic
4228 should allow Tor to succeed at building circuits even when the
4229 network connection drastically changes. Should help with bug 3443.
4231 o Major features (IPv6):
4232 - Relays can now exit to IPv6 addresses: make sure that you have IPv6
4233 connectivity, then set the IPv6Exit flag to 1. Also make sure your
4234 exit policy reads as you would like: the address * applies to all
4235 address families, whereas *4 is IPv4 address only, and *6 is IPv6
4236 addresses only. On the client side, you'll need to wait until the
4237 authorities have upgraded, wait for enough exits to support IPv6,
4238 apply the "IPv6Traffic" flag to a SocksPort, and use Socks5. Closes
4239 ticket 5547, implements proposal 117 as revised in proposal 208.
4241 We DO NOT recommend that clients with actual anonymity needs start
4242 using IPv6 over Tor yet, since not enough exits support it yet.
4244 o Major features (geoip database):
4245 - Maxmind began labelling Tor relays as being in country "A1",
4246 which breaks by-country node selection inside Tor. Now we use a
4247 script to replace "A1" ("Anonymous Proxy") entries in our geoip
4248 file with real country codes. This script fixes about 90% of "A1"
4249 entries automatically and uses manual country code assignments to
4250 fix the remaining 10%. See src/config/README.geoip for details.
4251 Fixes bug 6266. Also update to the December 5 2012 Maxmind GeoLite
4252 Country database, as modified above.
4254 o Major bugfixes (client-side DNS):
4255 - Turn off the client-side DNS cache by default. Updating and using
4256 the DNS cache is now configurable on a per-client-port
4257 level. SOCKSPort, DNSPort, etc lines may now contain
4258 {No,}Cache{IPv4,IPv6,}DNS lines to indicate that we shouldn't
4259 cache these types of DNS answers when we receive them from an
4260 exit node in response to an application request on this port, and
4261 {No,}UseCached{IPv4,IPv6,DNS} lines to indicate that if we have
4262 cached DNS answers of these types, we shouldn't use them. It's
4263 potentially risky to use cached DNS answers at the client, since
4264 doing so can indicate to one exit what answers we've gotten
4265 for DNS lookups in the past. With IPv6, this becomes especially
4266 problematic. Using cached DNS answers for requests on the same
4267 circuit would present less linkability risk, since all traffic
4268 on a circuit is already linkable, but it would also provide
4269 little performance benefit: the exit node caches DNS replies
4270 too. Implements a simplified version of Proposal 205. Implements
4273 o Major bugfixes (other):
4274 - Alter circuit build timeout measurement to start at the point
4275 where we begin the CREATE/CREATE_FAST step (as opposed to circuit
4276 initialization). This should make our timeout measurements more
4277 uniform. Previously, we were sometimes including ORconn setup time
4278 in our circuit build time measurements. Should resolve bug 3443.
4279 - Fix an assertion that could trigger in hibernate_go_dormant() when
4280 closing an or_connection_t: call channel_mark_for_close() rather
4281 than connection_mark_for_close(). Fixes bug 7267. Bugfix on
4283 - Include the geoip6 IPv6 GeoIP database in the tarball. Fixes bug
4284 7655; bugfix on 0.2.4.6-alpha.
4287 - Add a new torrc option "ServerTransportListenAddr" to let bridge
4288 operators select the address where their pluggable transports will
4289 listen for connections. Resolves ticket 7013.
4290 - Allow an optional $ before the node identity digest in the
4291 controller command GETINFO ns/id/<identity>, for consistency with
4292 md/id/<identity> and desc/id/<identity>. Resolves ticket 7059.
4293 - Log packaged cell fullness as part of the heartbeat message.
4294 Diagnosis to try to determine the extent of bug 7743.
4296 o Minor features (IPv6):
4297 - AutomapHostsOnResolve now supports IPv6 addresses. By default, we
4298 prefer to hand out virtual IPv6 addresses, since there are more of
4299 them and we can't run out. To override this behavior and make IPv4
4300 addresses preferred, set NoPreferIPv6Automap on whatever SOCKSPort
4301 or DNSPort you're using for resolving. Implements ticket 7571.
4302 - AutomapHostsOnResolve responses are now randomized, to avoid
4303 annoying situations where Tor is restarted and applications
4304 connect to the wrong addresses.
4305 - Never try more than 1000 times to pick a new virtual address when
4306 AutomapHostsOnResolve is set. That's good enough so long as we
4307 aren't close to handing out our entire virtual address space;
4308 if you're getting there, it's best to switch to IPv6 virtual
4312 - The ADDRMAP command can no longer generate an ill-formed error
4313 code on a failed MAPADDRESS. It now says "internal" rather than
4314 an English sentence fragment with spaces in the middle. Bugfix on
4316 - Fix log messages and comments to avoid saying "GMT" when we mean
4317 "UTC". Fixes bug 6113.
4318 - Compile on win64 using mingw64. Fixes bug 7260; patches from
4320 - Fix a crash when debugging unit tests on Windows: deallocate a
4321 shared library with FreeLibrary, not CloseHandle. Fixes bug 7306;
4322 bugfix on 0.2.2.17-alpha. Reported by "ultramage".
4325 - The DirServer option is now DirAuthority, for consistency with
4326 current naming patterns. You can still use the old DirServer form.
4328 o Code simplification and refactoring:
4329 - Move the client-side address-map/virtual-address/DNS-cache code
4330 out of connection_edge.c into a new addressmap.c module.
4331 - Remove unused code for parsing v1 directories and "running routers"
4332 documents. Fixes bug 6887.
4335 Changes in version 0.2.3.25 - 2012-11-19
4336 The Tor 0.2.3 release series is dedicated to the memory of Len "rabbi"
4337 Sassaman (1980-2011), a long-time cypherpunk, anonymity researcher,
4338 Mixmaster maintainer, Pynchon Gate co-designer, CodeCon organizer,
4339 programmer, and friend. Unstinting in his dedication to the cause of
4340 freedom, he inspired and helped many of us as we began our work on
4341 anonymity, and inspires us still. Please honor his memory by writing
4342 software to protect people's freedoms, and by helping others to do so.
4344 Tor 0.2.3.25, the first stable release in the 0.2.3 branch, features
4345 significantly reduced directory overhead (via microdescriptors),
4346 enormous crypto performance improvements for fast relays on new
4347 enough hardware, a new v3 TLS handshake protocol that can better
4348 resist fingerprinting, support for protocol obfuscation plugins (aka
4349 pluggable transports), better scalability for hidden services, IPv6
4350 support for bridges, performance improvements like allowing clients
4351 to skip the first round-trip on the circuit ("optimistic data") and
4352 refilling token buckets more often, a new "stream isolation" design
4353 to isolate different applications on different circuits, and many
4354 stability, security, and privacy fixes.
4357 - Tor tries to wipe potentially sensitive data after using it, so
4358 that if some subsequent security failure exposes Tor's memory,
4359 the damage will be limited. But we had a bug where the compiler
4360 was eliminating these wipe operations when it decided that the
4361 memory was no longer visible to a (correctly running) program,
4362 hence defeating our attempt at defense in depth. We fix that
4363 by using OpenSSL's OPENSSL_cleanse() operation, which a compiler
4364 is unlikely to optimize away. Future versions of Tor may use
4365 a less ridiculously heavy approach for this. Fixes bug 7352.
4366 Reported in an article by Andrey Karpov.
4369 - Fix a harmless bug when opting against publishing a relay descriptor
4370 because DisableNetwork is set. Fixes bug 7464; bugfix on
4374 Changes in version 0.2.4.6-alpha - 2012-11-13
4375 Tor 0.2.4.6-alpha fixes an assert bug that has been plaguing relays,
4376 makes our defense-in-depth memory wiping more reliable, and begins to
4377 count IPv6 addresses in bridge statistics,
4380 - Fix an assertion failure that could occur when closing a connection
4381 with a spliced rendezvous circuit. Fix for bug 7212; bugfix on
4383 - Tor tries to wipe potentially sensitive data after using it, so
4384 that if some subsequent security failure exposes Tor's memory,
4385 the damage will be limited. But we had a bug where the compiler
4386 was eliminating these wipe operations when it decided that the
4387 memory was no longer visible to a (correctly running) program,
4388 hence defeating our attempt at defense in depth. We fix that
4389 by using OpenSSL's OPENSSL_cleanse() operation, which a compiler
4390 is unlikely to optimize away. Future versions of Tor may use
4391 a less ridiculously heavy approach for this. Fixes bug 7352.
4392 Reported in an article by Andrey Karpov.
4395 - Add GeoIP database for IPv6 addresses. The new config option
4397 - Bridge statistics now count bridge clients connecting over IPv6:
4398 bridge statistics files now list "bridge-ip-versions" and
4399 extra-info documents list "geoip6-db-digest". The control protocol
4400 "CLIENTS_SEEN" and "ip-to-country" queries now support IPv6. Initial
4401 implementation by "shkoo", addressing ticket 5055.
4404 - Warn when we are binding low ports when hibernation is enabled;
4405 previously we had warned when we were _advertising_ low ports with
4406 hibernation enabled. Fixes bug 7285; bugfix on 0.2.3.9-alpha.
4407 - Fix a harmless bug when opting against publishing a relay descriptor
4408 because DisableNetwork is set. Fixes bug 7464; bugfix on
4410 - Add warning message when a managed proxy dies during configuration.
4411 Fixes bug 7195; bugfix on 0.2.4.2-alpha.
4412 - Fix a linking error when building tor-fw-helper without miniupnp.
4413 Fixes bug 7235; bugfix on 0.2.4.2-alpha. Fix by Anthony G. Basile.
4414 - Check for closing an or_connection_t without going through correct
4415 channel functions; emit a warning and then call
4416 connection_or_close_for_error() so we don't assert as in bugs 7212
4418 - Compile correctly on compilers without C99 designated initializer
4419 support. Fixes bug 7286; bugfix on 0.2.4.4-alpha.
4420 - Avoid a possible assert that can occur when channel_send_destroy() is
4421 called on a channel in CHANNEL_STATE_CLOSING, CHANNEL_STATE_CLOSED,
4422 or CHANNEL_STATE_ERROR when the Tor process is resumed after being
4423 blocked for a long interval. Fixes bug 7350; bugfix on 0.2.4.4-alpha.
4424 - Fix a memory leak on failing cases of channel_tls_process_certs_cell.
4425 Fixes bug 7422; bugfix on 0.2.4.4-alpha.
4427 o Code simplification and refactoring:
4428 - Start using OpenBSD's implementation of queue.h, so that we don't
4429 need to hand-roll our own pointer and list structures whenever we
4430 need them. (We can't rely on a sys/queue.h, since some operating
4431 systems don't have them, and the ones that do have them don't all
4432 present the same extensions.)
4435 Changes in version 0.2.4.5-alpha - 2012-10-25
4436 Tor 0.2.4.5-alpha comes hard at the heels of 0.2.4.4-alpha, to fix
4437 two important security vulnerabilities that could lead to remotely
4438 triggerable relay crashes, fix a major bug that was preventing clients
4439 from choosing suitable exit nodes, and refactor some of our code.
4441 o Major bugfixes (security, also in 0.2.3.24-rc):
4442 - Fix a group of remotely triggerable assertion failures related to
4443 incorrect link protocol negotiation. Found, diagnosed, and fixed
4444 by "some guy from France". Fix for CVE-2012-2250; bugfix on
4446 - Fix a denial of service attack by which any directory authority
4447 could crash all the others, or by which a single v2 directory
4448 authority could crash everybody downloading v2 directory
4449 information. Fixes bug 7191; bugfix on 0.2.0.10-alpha.
4451 o Major bugfixes (also in 0.2.3.24-rc):
4452 - When parsing exit policy summaries from microdescriptors, we had
4453 previously been ignoring the last character in each one, so that
4454 "accept 80,443,8080" would be treated by clients as indicating
4455 a node that allows access to ports 80, 443, and 808. That would
4456 lead to clients attempting connections that could never work,
4457 and ignoring exit nodes that would support their connections. Now
4458 clients parse these exit policy summaries correctly. Fixes bug 7192;
4459 bugfix on 0.2.3.1-alpha.
4461 o Minor bugfixes (also in 0.2.3.24-rc):
4462 - Clients now consider the ClientRejectInternalAddresses config option
4463 when using a microdescriptor consensus stanza to decide whether
4464 an exit relay would allow exiting to an internal address. Fixes
4465 bug 7190; bugfix on 0.2.3.1-alpha.
4468 - Only disable TLS session ticket support when running as a TLS
4469 server. Now clients will blend better with regular Firefox
4470 connections. Fixes bug 7189; bugfix on Tor 0.2.3.23-rc.
4472 o Code simplification and refactoring:
4473 - Start using OpenBSD's implementation of queue.h (originally by
4475 - Move the entry node code from circuitbuild.c to its own file.
4476 - Move the circuit build timeout tracking code from circuitbuild.c
4480 Changes in version 0.2.3.24-rc - 2012-10-25
4481 Tor 0.2.3.24-rc fixes two important security vulnerabilities that
4482 could lead to remotely triggerable relay crashes, and fixes
4483 a major bug that was preventing clients from choosing suitable exit
4486 o Major bugfixes (security):
4487 - Fix a group of remotely triggerable assertion failures related to
4488 incorrect link protocol negotiation. Found, diagnosed, and fixed
4489 by "some guy from France". Fix for CVE-2012-2250; bugfix on
4491 - Fix a denial of service attack by which any directory authority
4492 could crash all the others, or by which a single v2 directory
4493 authority could crash everybody downloading v2 directory
4494 information. Fixes bug 7191; bugfix on 0.2.0.10-alpha.
4497 - When parsing exit policy summaries from microdescriptors, we had
4498 previously been ignoring the last character in each one, so that
4499 "accept 80,443,8080" would be treated by clients as indicating
4500 a node that allows access to ports 80, 443, and 808. That would
4501 lead to clients attempting connections that could never work,
4502 and ignoring exit nodes that would support their connections. Now
4503 clients parse these exit policy summaries correctly. Fixes bug 7192;
4504 bugfix on 0.2.3.1-alpha.
4507 - Clients now consider the ClientRejectInternalAddresses config option
4508 when using a microdescriptor consensus stanza to decide whether
4509 an exit relay would allow exiting to an internal address. Fixes
4510 bug 7190; bugfix on 0.2.3.1-alpha.
4513 Changes in version 0.2.4.4-alpha - 2012-10-20
4514 Tor 0.2.4.4-alpha adds a new v3 directory authority, fixes a privacy
4515 vulnerability introduced by a change in OpenSSL, fixes a remotely
4516 triggerable assert, and adds new channel_t and circuitmux_t abstractions
4517 that will make it easier to test new connection transport and cell
4518 scheduling algorithms.
4520 o New directory authorities (also in 0.2.3.23-rc):
4521 - Add Faravahar (run by Sina Rabbani) as the ninth v3 directory
4522 authority. Closes ticket 5749.
4524 o Major bugfixes (security/privacy, also in 0.2.3.23-rc):
4525 - Disable TLS session tickets. OpenSSL's implementation was giving
4526 our TLS session keys the lifetime of our TLS context objects, when
4527 perfect forward secrecy would want us to discard anything that
4528 could decrypt a link connection as soon as the link connection
4529 was closed. Fixes bug 7139; bugfix on all versions of Tor linked
4530 against OpenSSL 1.0.0 or later. Found by Florent Daignière.
4531 - Discard extraneous renegotiation attempts once the V3 link
4532 protocol has been initiated. Failure to do so left us open to
4533 a remotely triggerable assertion failure. Fixes CVE-2012-2249;
4534 bugfix on 0.2.3.6-alpha. Reported by "some guy from France".
4536 o Internal abstraction features:
4537 - Introduce new channel_t abstraction between circuits and
4538 or_connection_t to allow for implementing alternate OR-to-OR
4539 transports. A channel_t is an abstract object which can either be a
4540 cell-bearing channel, which is responsible for authenticating and
4541 handshaking with the remote OR and transmitting cells to and from
4542 it, or a listening channel, which spawns new cell-bearing channels
4543 at the request of remote ORs. Implements part of ticket 6465.
4544 - Also new is the channel_tls_t subclass of channel_t, adapting it
4545 to the existing or_connection_t code. The V2/V3 protocol handshaking
4546 code which formerly resided in command.c has been moved below the
4547 channel_t abstraction layer and may be found in channeltls.c now.
4548 Implements the rest of ticket 6465.
4549 - Introduce new circuitmux_t storing the queue of circuits for
4550 a channel; this encapsulates and abstracts the queue logic and
4551 circuit selection policy, and allows the latter to be overridden
4552 easily by switching out a policy object. The existing EWMA behavior
4553 is now implemented as a circuitmux_policy_t. Resolves ticket 6816.
4555 o Required libraries:
4556 - Tor now requires OpenSSL 0.9.8 or later. OpenSSL 1.0.0 or later is
4557 strongly recommended.
4560 - Warn users who run hidden services on a Tor client with
4561 UseEntryGuards disabled that their hidden services will be
4562 vulnerable to http://freehaven.net/anonbib/#hs-attack06 (the
4563 attack which motivated Tor to support entry guards in the first
4564 place). Resolves ticket 6889.
4565 - Tor now builds correctly on Bitrig, an OpenBSD fork. Patch from
4566 dhill. Resolves ticket 6982.
4567 - Option OutboundBindAddress can be specified multiple times and
4568 accepts IPv6 addresses. Resolves ticket 6876.
4570 o Minor bugfixes (also in 0.2.3.23-rc):
4571 - Don't serve or accept v2 hidden service descriptors over a
4572 relay's DirPort. It's never correct to do so, and disabling it
4573 might make it more annoying to exploit any bugs that turn up in the
4574 descriptor-parsing code. Fixes bug 7149.
4575 - Fix two cases in src/or/transports.c where we were calling
4576 fmt_addr() twice in a parameter list. Bug found by David
4577 Fifield. Fixes bug 7014; bugfix on 0.2.3.9-alpha.
4578 - Fix memory leaks whenever we logged any message about the "path
4579 bias" detection. Fixes bug 7022; bugfix on 0.2.3.21-rc.
4580 - When relays refuse a "create" cell because their queue of pending
4581 create cells is too big (typically because their cpu can't keep up
4582 with the arrival rate), send back reason "resource limit" rather
4583 than reason "internal", so network measurement scripts can get a
4584 more accurate picture. Fixes bug 7037; bugfix on 0.1.1.11-alpha.
4587 - Command-line option "--version" implies "--quiet". Fixes bug 6997.
4588 - Free some more still-in-use memory at exit, to make hunting for
4589 memory leaks easier. Resolves bug 7029.
4590 - When a Tor client gets a "truncated" relay cell, the first byte of
4591 its payload specifies why the circuit was truncated. We were
4592 ignoring this 'reason' byte when tearing down the circuit, resulting
4593 in the controller not being told why the circuit closed. Now we
4594 pass the reason from the truncated cell to the controller. Bugfix
4595 on 0.1.2.3-alpha; fixes bug 7039.
4596 - Downgrade "Failed to hand off onionskin" messages to "debug"
4597 severity, since they're typically redundant with the "Your computer
4598 is too slow" messages. Fixes bug 7038; bugfix on 0.2.2.16-alpha.
4599 - Make clients running with IPv6 bridges connect over IPv6 again,
4600 even without setting new config options ClientUseIPv6 and
4601 ClientPreferIPv6ORPort. Fixes bug 6757; bugfix on 0.2.4.1-alpha.
4602 - Use square brackets around IPv6 addresses in numerous places
4603 that needed them, including log messages, HTTPS CONNECT proxy
4604 requests, TransportProxy statefile entries, and pluggable transport
4605 extra-info lines. Fixes bug 7011; patch by David Fifield.
4607 o Code refactoring and cleanup:
4608 - Source files taken from other packages now reside in src/ext;
4609 previously they were scattered around the rest of Tor.
4610 - Avoid use of reserved identifiers in our C code. The C standard
4611 doesn't like us declaring anything that starts with an
4612 underscore, so let's knock it off before we get in trouble. Fix
4613 for bug 1031; bugfix on the first Tor commit.
4616 Changes in version 0.2.3.23-rc - 2012-10-20
4617 Tor 0.2.3.23-rc adds a new v3 directory authority, fixes a privacy
4618 vulnerability introduced by a change in OpenSSL, and fixes a variety
4619 of smaller bugs in preparation for the release.
4621 o New directory authorities:
4622 - Add Faravahar (run by Sina Rabbani) as the ninth v3 directory
4623 authority. Closes ticket 5749.
4625 o Major bugfixes (security/privacy):
4626 - Disable TLS session tickets. OpenSSL's implementation was giving
4627 our TLS session keys the lifetime of our TLS context objects, when
4628 perfect forward secrecy would want us to discard anything that
4629 could decrypt a link connection as soon as the link connection
4630 was closed. Fixes bug 7139; bugfix on all versions of Tor linked
4631 against OpenSSL 1.0.0 or later. Found by Florent Daignière.
4632 - Discard extraneous renegotiation attempts once the V3 link
4633 protocol has been initiated. Failure to do so left us open to
4634 a remotely triggerable assertion failure. Fixes CVE-2012-2249;
4635 bugfix on 0.2.3.6-alpha. Reported by "some guy from France".
4638 - Fix a possible crash bug when checking for deactivated circuits
4639 in connection_or_flush_from_first_active_circuit(). Fixes bug 6341;
4640 bugfix on 0.2.2.7-alpha. Bug report and fix received pseudonymously.
4642 o Minor bugfixes (on 0.2.3.x):
4643 - Fix two cases in src/or/transports.c where we were calling
4644 fmt_addr() twice in a parameter list. Bug found by David
4645 Fifield. Fixes bug 7014; bugfix on 0.2.3.9-alpha.
4646 - Convert an assert in the pathbias code to a log message. The assert
4647 appears to only be triggerable by Tor2Web mode. Fixes bug 6866;
4648 bugfix on 0.2.3.17-beta.
4649 - Fix memory leaks whenever we logged any message about the "path
4650 bias" detection. Fixes bug 7022; bugfix on 0.2.3.21-rc.
4652 o Minor bugfixes (on 0.2.2.x and earlier):
4653 - Don't serve or accept v2 hidden service descriptors over a relay's
4654 DirPort. It's never correct to do so, and disabling it might
4655 make it more annoying to exploit any bugs that turn up in the
4656 descriptor-parsing code. Fixes bug 7149.
4657 - When relays refuse a "create" cell because their queue of pending
4658 create cells is too big (typically because their cpu can't keep up
4659 with the arrival rate), send back reason "resource limit" rather
4660 than reason "internal", so network measurement scripts can get a
4661 more accurate picture. Bugfix on 0.1.1.11-alpha; fixes bug 7037.
4662 - Correct file sizes when reading binary files on Cygwin, to avoid
4663 a bug where Tor would fail to read its state file. Fixes bug 6844;
4664 bugfix on 0.1.2.7-alpha.
4665 - Avoid undefined behavior when parsing the list of supported
4666 rendezvous/introduction protocols in a hidden service descriptor.
4667 Previously, Tor would have confused (as-yet-unused) protocol version
4668 numbers greater than 32 with lower ones on many platforms. Fixes
4669 bug 6827; bugfix on 0.2.0.10-alpha. Found by George Kadianakis.
4671 o Documentation fixes:
4672 - Clarify that hidden services are TCP only. Fixes bug 6024.
4675 Changes in version 0.2.4.3-alpha - 2012-09-22
4676 Tor 0.2.4.3-alpha fixes another opportunity for a remotely triggerable
4677 assertion, resumes letting relays test reachability of their DirPort,
4678 and cleans up a bunch of smaller bugs.
4681 - Fix an assertion failure in tor_timegm() that could be triggered
4682 by a badly formatted directory object. Bug found by fuzzing with
4683 Radamsa. Fixes bug 6811; bugfix on 0.2.0.20-rc.
4686 - Fix a possible crash bug when checking for deactivated circuits
4687 in connection_or_flush_from_first_active_circuit(). Fixes bug 6341;
4688 bugfix on 0.2.2.7-alpha. Bug report and fix received pseudonymously.
4689 - Allow routers to detect that their own DirPorts are running. When
4690 we removed support for versions_supports_begindir, we also
4691 accidentally removed the mechanism we used to self-test our
4692 DirPort. Diagnosed with help from kargig. Fixes bugs 6814 and 6815;
4693 bugfix on 0.2.4.2-alpha.
4695 o Security features:
4696 - Switch to a completely time-invariant approach for picking nodes
4697 weighted by bandwidth. Our old approach would run through the
4698 part of the loop after it had made its choice slightly slower
4699 than it ran through the part of the loop before it had made its
4700 choice. Addresses ticket 6538.
4701 - Disable the use of Guard nodes when in Tor2WebMode. Guard usage
4702 by tor2web clients allows hidden services to identify tor2web
4703 clients through their repeated selection of the same rendezvous
4704 and introduction point circuit endpoints (their guards). Resolves
4708 - Enable Tor to read configuration, state, and key information from
4709 a FIFO. Previously Tor would only read from files with a positive
4710 stat.st_size. Code from meejah; fixes bug 6044.
4713 - Correct file sizes when reading binary files on Cygwin, to avoid
4714 a bug where Tor would fail to read its state file. Fixes bug 6844;
4715 bugfix on 0.1.2.7-alpha.
4716 - Correctly handle votes with more than 31 flags. Fixes bug 6853;
4717 bugfix on 0.2.0.3-alpha.
4718 - When complaining about a client port on a public address, log
4719 which address we're complaining about. Fixes bug 4020; bugfix on
4720 0.2.3.3-alpha. Patch by Tom Fitzhenry.
4721 - Convert an assert in the pathbias code to a log message. The assert
4722 appears to only be triggerable by Tor2Web mode. Fixes bug 6866;
4723 bugfix on 0.2.3.17-beta.
4724 - Our new buildsystem was overzealous about rebuilding manpages: it
4725 would rebuild them all whenever any one of them changed. Now our
4726 dependency checking should be correct. Fixes bug 6843; bugfix on
4728 - Don't do reachability testing over IPv6 unless AuthDirPublishIPv6
4729 is set. Fixes bug 6880. Bugfix on 0.2.4.1-alpha.
4730 - Correct log printout about which address family is preferred
4731 when connecting to a bridge with both an IPv4 and IPv6 OR port.
4732 Fixes bug 6884; bugfix on 0.2.4.1-alpha.
4734 o Minor bugfixes (code cleanliness):
4735 - Fix round_to_power_of_2() so it doesn't invoke undefined behavior
4736 with large values. This situation was untriggered, but nevertheless
4737 incorrect. Fixes bug 6831; bugfix on 0.2.0.1-alpha.
4738 - Reject consensus votes with more than 64 known-flags. We aren't even
4739 close to that limit yet, and our code doesn't handle it correctly.
4740 Fixes bug 6833; bugfix on 0.2.0.1-alpha.
4741 - Avoid undefined behavior when parsing the list of supported
4742 rendezvous/introduction protocols in a hidden service descriptor.
4743 Previously, Tor would have confused (as-yet-unused) protocol version
4744 numbers greater than 32 with lower ones on many platforms. Fixes
4745 bug 6827; bugfix on 0.2.0.10-alpha. Found by George Kadianakis.
4746 - Fix handling of rendezvous client authorization types over 8.
4747 Fixes bug 6861; bugfix on 0.2.1.5-alpha.
4748 - Fix building with older versions of GCC (2.95, for one) that don't
4749 like preprocessor directives inside macro arguments. Found by
4750 grarpamp. Fixes bug 6842; bugfix on 0.2.4.2-alpha.
4751 - Switch weighted node selection rule from using a list of doubles
4752 to using a list of int64_t. This change should make the process
4753 slightly easier to debug and maintain. Needed to finish ticket 6538.
4755 o Code simplification and refactoring:
4756 - Move the generic "config" code into a new file, and have "config.c"
4757 hold only torrc- and state-related code. Resolves ticket 6823.
4758 - Move the core of our "choose a weighted element at random" logic
4759 into its own function, and give it unit tests. Now the logic is
4760 testable, and a little less fragile too.
4761 - Removed the testing_since field of node_t, which hasn't been used
4762 for anything since 0.2.0.9-alpha.
4764 o Documentation fixes:
4765 - Clarify that hidden services are TCP only. Fixes bug 6024.
4766 - Resolve a typo in torrc.sample.in. Fixes bug 6819; bugfix on
4770 Changes in version 0.2.3.22-rc - 2012-09-11
4771 Tor 0.2.3.22-rc fixes another opportunity for a remotely triggerable
4775 - Fix an assertion failure in tor_timegm() that could be triggered
4776 by a badly formatted directory object. Bug found by fuzzing with
4777 Radamsa. Fixes bug 6811; bugfix on 0.2.0.20-rc.
4780 - Avoid segfault when starting up having run with an extremely old
4781 version of Tor and parsing its state file. Fixes bug 6801; bugfix
4785 Changes in version 0.2.2.39 - 2012-09-11
4786 Tor 0.2.2.39 fixes two more opportunities for remotely triggerable
4790 - Fix an assertion failure in tor_timegm() that could be triggered
4791 by a badly formatted directory object. Bug found by fuzzing with
4792 Radamsa. Fixes bug 6811; bugfix on 0.2.0.20-rc.
4793 - Do not crash when comparing an address with port value 0 to an
4794 address policy. This bug could have been used to cause a remote
4795 assertion failure by or against directory authorities, or to
4796 allow some applications to crash clients. Fixes bug 6690; bugfix
4800 Changes in version 0.2.4.2-alpha - 2012-09-10
4801 Tor 0.2.4.2-alpha enables port forwarding for pluggable transports,
4802 raises the default rate limiting even more, and makes the bootstrapping
4803 log messages less noisy.
4806 - Automatically forward the TCP ports of pluggable transport
4807 proxies using tor-fw-helper if PortForwarding is enabled. Implements
4811 - Raise the default BandwidthRate/BandwidthBurst values from 5MB/10MB
4812 to 1GB/1GB. The previous defaults were intended to be "basically
4813 infinite", but it turns out they're now limiting our 100mbit+
4814 relays and bridges. Fixes bug 6605; bugfix on 0.2.0.10-alpha (the
4815 last time we raised it).
4818 - Detect when we're running with a version of OpenSSL other than the
4819 one we compiled with. This has occasionally given people hard-to-
4821 - Log fewer lines at level "notice" about our OpenSSL and Libevent
4822 versions and capabilities when everything is going right. Resolves
4823 part of ticket 6736.
4824 - Directory authorities no long accept descriptors for any version of
4825 Tor before 0.2.2.35, or for any 0.2.3 release before 0.2.3.10-alpha.
4826 These versions are insecure, unsupported, or both. Implements
4830 - Rename the (internal-use-only) UsingTestingNetworkDefaults option
4831 to start with a triple-underscore so the controller won't touch it.
4832 Patch by Meejah. Fixes bug 3155. Bugfix on 0.2.2.23-alpha.
4833 - Avoid segfault when starting up having run with an extremely old
4834 version of Tor and parsing its state file. Fixes bug 6801; bugfix
4836 - Rename the (testing-use-only) _UseFilteringSSLBufferevents option
4837 so it doesn't start with _. Fixes bug 3155. Bugfix on 0.2.3.1-alpha.
4838 - Don't follow the NULL pointer if microdescriptor generation fails.
4839 (This does not appear to be triggerable, but it's best to be safe.)
4840 Found by "f. tp.". Fixes bug 6797; bugfix on 0.2.4.1-alpha.
4841 - Fix mis-declared dependencies on src/common/crypto.c and
4842 src/or/tor_main.c that could break out-of-tree builds under some
4843 circumstances. Fixes bug 6778; bugfix on 0.2.4.1-alpha.
4844 - Avoid a warning when building common_sha1.i out of tree. Fixes bug
4845 6778; bugfix on 0.2.4.1-alpha.
4846 - Fix a harmless (in this case) build warning for implicitly
4847 converting a strlen() to an int. Bugfix on 0.2.4.1-alpha.
4850 - Now that all versions before 0.2.2.x are disallowed, we no longer
4851 need to work around their missing features. Thus we can remove a
4852 bunch of compatibility code.
4855 - Tweak tor-fw-helper to accept an arbitrary amount of arbitrary
4856 TCP ports to forward. In the past it only accepted two ports:
4857 the ORPort and the DirPort.
4860 Changes in version 0.2.4.1-alpha - 2012-09-05
4861 Tor 0.2.4.1-alpha lets bridges publish their pluggable transports to
4862 bridgedb; lets relays use IPv6 addresses and directory authorities
4863 advertise them; and switches to a cleaner build interface.
4865 This is the first alpha release in a new series, so expect there to
4866 be bugs. Users who would rather test out a more stable branch should
4867 stay with 0.2.3.x for now.
4869 o Major features (bridges):
4870 - Bridges now report the pluggable transports they support to the
4871 bridge authority, so it can pass the supported transports on to
4872 bridgedb and/or eventually do reachability testing. Implements
4875 o Major features (IPv6):
4876 - Bridge authorities now accept IPv6 bridge addresses and include
4877 them in network status documents. Implements ticket 5534.
4878 - Clients who set "ClientUseIPv6 1" may connect to entry nodes over
4879 IPv6. Set "ClientPreferIPv6ORPort 1" to make this even more likely
4880 to happen. Implements ticket 5535.
4881 - All kind of relays, not just bridges, can now advertise an IPv6
4882 OR port. Implements ticket 6362.
4883 - Directory authorities vote on IPv6 OR ports using the new consensus
4884 method 14. Implements ticket 6363.
4886 o Major features (build):
4887 - Switch to a nonrecursive Makefile structure. Now instead of each
4888 Makefile.am invoking other Makefile.am's, there is a master
4889 Makefile.am that includes the others. This change makes our build
4890 process slightly more maintainable, and improves parallelism for
4891 building with make -j. Original patch by Stewart Smith; various
4892 fixes by Jim Meyering.
4893 - Where available, we now use automake's "silent" make rules by
4894 default, so that warnings are easier to spot. You can get the old
4895 behavior with "make V=1". Patch by Stewart Smith for ticket 6522.
4897 o Minor features (code security and spec conformance):
4898 - Clear keys and key-derived material left on the stack in
4899 rendservice.c and rendclient.c. Check return value of
4900 crypto_pk_write_private_key_to_string() in rend_service_load_keys().
4901 These fixes should make us more forward-secure against cold-boot
4902 attacks and the like. Fixes bug 2385.
4903 - Reject EXTEND cells sent to nonexistent streams. According to the
4904 spec, an EXTEND cell sent to _any_ nonzero stream ID is invalid, but
4905 we were only checking for stream IDs that were currently in use.
4906 Found while hunting for more instances of bug 6271. Bugfix on
4907 0.0.2pre8, which introduced incremental circuit construction.
4909 o Minor features (streamlining);
4910 - No longer include the "opt" prefix when generating routerinfos
4911 or v2 directories: it has been needless since Tor 0.1.2. Closes
4913 - Remove some now-needless code that tried to aggressively flush
4914 OR connections as data was added to them. Since 0.2.0.1-alpha, our
4915 cell queue logic has saved us from the failure mode that this code
4916 was supposed to prevent. Removing this code will limit the number
4917 of baroque control flow paths through Tor's network logic. Reported
4918 pseudonymously on IRC. Fixes bug 6468; bugfix on 0.2.0.1-alpha.
4920 o Minor features (controller):
4921 - Add a "GETINFO signal/names" control port command. Implements
4923 - Provide default values for all options via "GETINFO config/defaults".
4924 Implements ticket 4971.
4926 o Minor features (IPv6):
4927 - New config option "AuthDirHasIPv6Connectivity 1" that directory
4928 authorities should set if they have IPv6 connectivity and want to
4929 do reachability tests for IPv6 relays. Implements feature 5974.
4930 - A relay with an IPv6 OR port now sends that address in NETINFO
4931 cells (in addition to its other address). Implements ticket 6364.
4933 o Minor features (log messages):
4934 - Omit the first heartbeat log message, because it never has anything
4935 useful to say, and it clutters up the bootstrapping messages.
4936 Resolves ticket 6758.
4937 - Don't log about reloading the microdescriptor cache at startup. Our
4938 bootstrap warnings are supposed to tell the user when there's a
4939 problem, and our bootstrap notices say when there isn't. Resolves
4940 ticket 6759; bugfix on 0.2.2.6-alpha.
4941 - Don't log "I learned some more directory information" when we're
4942 reading cached directory information. Reserve it for when new
4943 directory information arrives in response to a fetch. Resolves
4945 - Prevent rounding error in path bias counts when scaling
4946 them down, and use the correct scale factor default. Also demote
4947 some path bias related log messages down a level and make others
4948 less scary sounding. Fixes bug 6647. Bugfix against 0.2.3.17-beta.
4949 - We no longer warn so much when generating manpages from their
4952 o Code simplifications and refactoring:
4953 - Enhance our internal sscanf replacement so that we can eliminate
4954 the last remaining uses of the system sscanf. (Though those uses
4955 of sscanf were safe, sscanf itself is generally error prone, so
4956 we want to eliminate when we can.) Fixes ticket 4195 and Coverity
4958 - Move ipv6_preferred from routerinfo_t to node_t. Addresses bug 4620.
4959 - Move last_reachable and testing_since from routerinfo_t to node_t.
4960 Implements ticket 5529.
4961 - Add replaycache_t structure, functions and unit tests, then refactor
4962 rend_service_introduce() to be more clear to read, improve, debug,
4963 and test. Resolves bug 6177.
4964 - Finally remove support for malloc_good_size and malloc_usable_size.
4965 We had hoped that these functions would let us eke a little more
4966 memory out of our malloc implementation. Unfortunately, the only
4967 implementations that provided these functions are also ones that
4968 are already efficient about not overallocation: they never got us
4969 more than 7 or so bytes per allocation. Removing them saves us a
4970 little code complexity and a nontrivial amount of build complexity.
4973 - Tor maintainers now require Automake version 1.9 or later to build
4974 Tor from the Git repository. (Automake is not required when building
4975 from a source distribution.)
4978 Changes in version 0.2.3.21-rc - 2012-09-05
4979 Tor 0.2.3.21-rc is the fourth release candidate for the Tor 0.2.3.x
4980 series. It fixes a trio of potential security bugs, fixes a bug where
4981 we were leaving some of the fast relays out of the microdescriptor
4982 consensus, resumes interpreting "ORPort 0" and "DirPort 0" correctly,
4983 and cleans up other smaller issues.
4985 o Major bugfixes (security):
4986 - Tear down the circuit if we get an unexpected SENDME cell. Clients
4987 could use this trick to make their circuits receive cells faster
4988 than our flow control would have allowed, or to gum up the network,
4989 or possibly to do targeted memory denial-of-service attacks on
4990 entry nodes. Fixes bug 6252. Bugfix on the 54th commit on Tor --
4991 from July 2002, before the release of Tor 0.0.0. We had committed
4992 this patch previously, but we had to revert it because of bug 6271.
4993 Now that 6271 is fixed, this patch appears to work.
4994 - Reject any attempt to extend to an internal address. Without
4995 this fix, a router could be used to probe addresses on an internal
4996 network to see whether they were accepting connections. Fixes bug
4997 6710; bugfix on 0.0.8pre1.
4998 - Do not crash when comparing an address with port value 0 to an
4999 address policy. This bug could have been used to cause a remote
5000 assertion failure by or against directory authorities, or to
5001 allow some applications to crash clients. Fixes bug 6690; bugfix
5005 - Remove the upper bound on microdescriptor length. We were hitting
5006 the limit for routers with complex exit policies or family
5007 declarations, causing clients to not use them. Fixes the first
5008 piece of bug 6404; fix on 0.2.2.6-alpha.
5009 - Detect "ORPort 0" as meaning, uniformly, that we're not running
5010 as a relay. Previously, some of our code would treat the presence
5011 of any ORPort line as meaning that we should act like a relay,
5012 even though our new listener code would correctly not open any
5013 ORPorts for ORPort 0. Similar bugs in other Port options are also
5014 fixed. Fixes the first half of bug 6507; bugfix on 0.2.3.3-alpha.
5017 - Avoid a pair of double-free and use-after-mark bugs that can
5018 occur with certain timings in canceled and re-received DNS
5019 requests. Fixes bug 6472; bugfix on 0.0.7rc1.
5020 - Fix build and 64-bit compile warnings from --enable-openbsd-malloc.
5021 Fixes bug 6379. Bugfix on 0.2.0.20-rc.
5022 - Allow one-hop directory fetching circuits the full "circuit build
5023 timeout" period, rather than just half of it, before failing them
5024 and marking the relay down. This fix should help reduce cases where
5025 clients declare relays (or worse, bridges) unreachable because
5026 the TLS handshake takes a few seconds to complete. Fixes bug 6743;
5027 bugfix on 0.2.2.2-alpha, where we changed the timeout from a static
5029 - Authorities no longer include any router in their microdescriptor
5030 consensuses for which they couldn't generate or agree on a
5031 microdescriptor. Fixes the second piece of bug 6404; fix on
5033 - Detect and reject attempts to specify both "FooPort" and
5034 "FooPort 0" in the same configuration domain. (It's still okay
5035 to have a FooPort in your configuration file, and use "FooPort 0"
5036 on the command line to disable it.) Fixes the second half of bug
5037 6507; bugfix on 0.2.3.3-alpha.
5038 - Make wildcarded addresses (that is, ones beginning with "*.") work
5039 when provided via the controller's MapAddress command. Previously,
5040 they were accepted, but we never actually noticed that they were
5041 wildcards. Fixes bug 6244; bugfix on 0.2.3.9-alpha.
5042 - Avoid crashing on a malformed state file where EntryGuardPathBias
5043 precedes EntryGuard. Fix for bug 6774; bugfix on 0.2.3.17-beta.
5044 - Add a (probably redundant) memory clear between iterations of
5045 the router status voting loop, to prevent future coding errors
5046 where data might leak between iterations of the loop. Resolves
5049 o Minor bugfixes (log messages):
5050 - Downgrade "set buildtimeout to low value" messages to "info"
5051 severity; they were never an actual problem, there was never
5052 anything reasonable to do about them, and they tended to spam logs
5053 from time to time. Fixes bug 6251; bugfix on 0.2.2.2-alpha.
5054 - Downgrade path-bias warning messages to "info". We'll try to get
5055 them working better in 0.2.4. Add internal circuit construction
5056 state to protect against the noisy warn message "Unexpectedly high
5057 circuit_successes". Also add some additional rate-limited notice
5058 messages to help determine the root cause of the warn. Fixes bug
5059 6475. Bugfix against 0.2.3.17-beta.
5060 - Move log message when unable to find a microdesc in a routerstatus
5061 entry to parse time. Previously we'd spam this warning every time
5062 we tried to figure out which microdescriptors to download. Fixes
5063 the third piece of bug 6404; fix on 0.2.3.18-rc.
5066 - Consider new, removed or changed IPv6 OR ports a non-cosmetic
5067 change when the authority is deciding whether to accept a newly
5068 uploaded descriptor. Implements ticket 6423.
5069 - Add missing documentation for consensus and microdesc files.
5070 Resolves ticket 6732.
5073 Changes in version 0.2.2.38 - 2012-08-12
5074 Tor 0.2.2.38 fixes a remotely triggerable crash bug, and fixes a timing
5075 attack that could in theory leak path information.
5078 - Avoid an uninitialized memory read when reading a vote or consensus
5079 document that has an unrecognized flavor name. This read could
5080 lead to a remote crash bug. Fixes bug 6530; bugfix on 0.2.2.6-alpha.
5081 - Try to leak less information about what relays a client is
5082 choosing to a side-channel attacker. Previously, a Tor client would
5083 stop iterating through the list of available relays as soon as it
5084 had chosen one, thus finishing a little earlier when it picked
5085 a router earlier in the list. If an attacker can recover this
5086 timing information (nontrivial but not proven to be impossible),
5087 they could learn some coarse-grained information about which relays
5088 a client was picking (middle nodes in particular are likelier to
5089 be affected than exits). The timing attack might be mitigated by
5090 other factors (see bug 6537 for some discussion), but it's best
5091 not to take chances. Fixes bug 6537; bugfix on 0.0.8rc1.
5094 Changes in version 0.2.3.20-rc - 2012-08-05
5095 Tor 0.2.3.20-rc is the third release candidate for the Tor 0.2.3.x
5096 series. It fixes a pair of code security bugs and a potential anonymity
5097 issue, updates our RPM spec files, and cleans up other smaller issues.
5100 - Avoid read-from-freed-memory and double-free bugs that could occur
5101 when a DNS request fails while launching it. Fixes bug 6480;
5102 bugfix on 0.2.0.1-alpha.
5103 - Avoid an uninitialized memory read when reading a vote or consensus
5104 document that has an unrecognized flavor name. This read could
5105 lead to a remote crash bug. Fixes bug 6530; bugfix on 0.2.2.6-alpha.
5106 - Try to leak less information about what relays a client is
5107 choosing to a side-channel attacker. Previously, a Tor client would
5108 stop iterating through the list of available relays as soon as it
5109 had chosen one, thus finishing a little earlier when it picked
5110 a router earlier in the list. If an attacker can recover this
5111 timing information (nontrivial but not proven to be impossible),
5112 they could learn some coarse-grained information about which relays
5113 a client was picking (middle nodes in particular are likelier to
5114 be affected than exits). The timing attack might be mitigated by
5115 other factors (see bug 6537 for some discussion), but it's best
5116 not to take chances. Fixes bug 6537; bugfix on 0.0.8rc1.
5119 - Try to make the warning when giving an obsolete SOCKSListenAddress
5120 a little more useful.
5121 - Terminate active server managed proxies if Tor stops being a
5122 relay. Addresses parts of bug 6274; bugfix on 0.2.3.6-alpha.
5123 - Provide a better error message about possible OSX Asciidoc failure
5124 reasons. Fixes bug 6436.
5125 - Warn when Tor is configured to use accounting in a way that can
5126 link a hidden service to some other hidden service or public
5127 address. Resolves ticket 6490.
5130 - Check return value of fputs() when writing authority certificate
5131 file. Fixes Coverity issue 709056; bugfix on 0.2.0.1-alpha.
5132 - Ignore ServerTransportPlugin lines when Tor is not configured as
5133 a relay. Fixes bug 6274; bugfix on 0.2.3.6-alpha.
5134 - When disabling guards for having too high a proportion of failed
5135 circuits, make sure to look at each guard. Fixes bug 6397; bugfix
5139 - Update our default RPM spec files to work with mock and rpmbuild
5140 on RHEL/Fedora. They have an updated set of dependencies and
5141 conflicts, a fix for an ancient typo when creating the "_tor"
5142 user, and better instructions. Thanks to Ondrej Mikle for the
5143 patch series. Fixes bug 6043.
5146 - Make it possible to set the TestingTorNetwork configuration
5147 option using AlternateDirAuthority and AlternateBridgeAuthority
5148 as an alternative to setting DirServer. Addresses ticket 6377.
5151 - Clarify the documentation for the Alternate*Authority options.
5153 - Fix some typos in the manpages. Patch from A. Costa. Fixes bug 6500.
5155 o Code simplification and refactoring:
5156 - Do not use SMARTLIST_FOREACH for any loop whose body exceeds
5157 10 lines. Also, don't nest them. Doing so in the past has
5158 led to hard-to-debug code. The new style is to use the
5159 SMARTLIST_FOREACH_{BEGIN,END} pair. Addresses issue 6400.
5162 Changes in version 0.2.3.19-rc - 2012-07-06
5163 Tor 0.2.3.19-rc is the second release candidate for the Tor 0.2.3.x
5164 series. It fixes the compile on Windows, reverts to a GeoIP database
5165 that isn't as broken, and fixes a flow control bug that has been around
5166 since the beginning of Tor.
5169 - Fix a bug handling SENDME cells on nonexistent streams that could
5170 result in bizarre window values. Report and patch contributed
5171 pseudonymously. Fixes part of bug 6271. This bug was introduced
5172 before the first Tor release, in svn commit r152.
5173 - Revert to the May 1 2012 Maxmind GeoLite Country database. In the
5174 June 2012 database, Maxmind marked many Tor relays as country "A1",
5175 which will cause risky behavior for clients that set EntryNodes
5176 or ExitNodes. Addresses bug 6334; bugfix on 0.2.3.17-beta.
5177 - Instead of ENOBUFS on Windows, say WSAENOBUFS. Fixes compilation
5178 on Windows. Fixes bug 6296; bugfix on 0.2.3.18-rc.
5181 - Fix wrong TCP port range in parse_port_range(). Fixes bug 6218;
5182 bugfix on 0.2.1.10-alpha.
5185 Changes in version 0.2.3.18-rc - 2012-06-28
5186 Tor 0.2.3.18-rc is the first release candidate for the Tor 0.2.3.x
5187 series. It fixes a few smaller bugs, but generally appears stable.
5188 Please test it and let us know whether it is!
5191 - Allow wildcarded mapaddress targets to be specified on the
5192 controlport. Partially fixes bug 6244; bugfix on 0.2.3.9-alpha.
5193 - Make our linker option detection code more robust against linkers
5194 such as on FreeBSD 8, where a bad combination of options completes
5195 successfully but makes an unrunnable binary. Fixes bug 6173;
5196 bugfix on 0.2.3.17-beta.
5198 o Minor bugfixes (on 0.2.2.x and earlier):
5199 - Avoid a false positive in the util/threads unit test by increasing
5200 the maximum timeout time. Fixes bug 6227; bugfix on 0.2.0.4-alpha.
5201 - Replace "Sending publish request" log messages with "Launching
5202 upload", so that they no longer confusingly imply that we're
5203 sending something to a directory we might not even be connected
5204 to yet. Fixes bug 3311; bugfix on 0.2.0.10-alpha.
5205 - Make sure to set *socket_error in all error cases in
5206 connection_connect(), so it can't produce a warning about
5207 errno being zero from errno_to_orconn_end_reason(). Bugfix on
5208 0.2.1.1-alpha; resolves ticket 6028.
5209 - Downgrade "Got a certificate, but we already have it" log messages
5210 from warning to info, except when we're a dirauth. Fixes bug 5238;
5211 bugfix on 0.2.1.7-alpha.
5212 - When checking for requested signatures on the latest consensus
5213 before serving it to a client, make sure to check the right
5214 consensus flavor. Bugfix on 0.2.2.6-alpha.
5215 - Downgrade "eventdns rejected address" message to LOG_PROTOCOL_WARN.
5216 Fixes bug 5932; bugfix on 0.2.2.7-alpha.
5218 o Minor bugfixes (on 0.2.3.x):
5219 - Make format_helper_exit_status() avoid unnecessary space padding
5220 and stop confusing log_from_pipe(). Fixes ticket 5557; bugfix
5222 - Downgrade a message about cleaning the microdescriptor cache to
5223 "info" from "notice". Fixes bug 6238; bugfix on 0.2.3.1-alpha.
5224 - Log a BUG message at severity INFO if we have a networkstatus with
5225 a missing entry for some microdescriptor. Continues on a patch
5227 - Improve the log message when a managed proxy fails to launch. Fixes
5228 bug 5099; bugfix on 0.2.3.6-alpha.
5229 - Don't do DNS lookups when parsing corrupted managed proxy protocol
5230 messages. Fixes bug 6226; bugfix on 0.2.3.6-alpha.
5231 - When formatting wildcarded address mappings for the controller,
5232 be sure to include "*." as appropriate. Partially fixes bug 6244;
5233 bugfix on 0.2.3.9-alpha.
5234 - Avoid a warning caused by using strcspn() from glibc with clang 3.0.
5235 Bugfix on 0.2.3.13-alpha.
5236 - Stop logging messages about running with circuit timeout learning
5237 enabled at severity LD_BUG. Fixes bug 6169; bugfix on 0.2.3.17-beta.
5238 - Disable a spurious warning about reading on a marked and flushing
5239 connection. We shouldn't be doing that, but apparently we
5240 sometimes do. Fixes bug 6203; bugfix on 0.2.3.17-beta.
5241 - Fix a bug that stopped AllowDotExit from working on addresses
5242 that had an entry in the DNS cache. Fixes bug 6211; bugfix on
5245 o Code simplification, refactoring, unit tests:
5246 - Move tor_gettimeofday_cached() into compat_libevent.c, and use
5247 Libevent's notion of cached time when possible.
5248 - Remove duplicate code for invoking getrlimit() from control.c.
5249 - Add a unit test for the environment_variable_names_equal function.
5252 - Document the --defaults-torrc option, and the new (in 0.2.3)
5253 semantics for overriding, extending, and clearing lists of
5254 options. Closes bug 4748.
5257 Changes in version 0.2.3.17-beta - 2012-06-15
5258 Tor 0.2.3.17-beta enables compiler and linker hardening by default,
5259 gets our TLS handshake back on track for being able to blend in with
5260 Firefox, fixes a big bug in 0.2.3.16-alpha that broke Tor's interaction
5261 with Vidalia, and otherwise continues to get us closer to a release
5265 - Enable gcc and ld hardening by default. Resolves ticket 5210.
5266 - Update TLS cipher list to match Firefox 8 and later. Resolves
5268 - Implement the client side of proposal 198: remove support for
5269 clients falsely claiming to support standard ciphersuites that
5270 they can actually provide. As of modern OpenSSL versions, it's not
5271 necessary to fake any standard ciphersuite, and doing so prevents
5272 us from using better ciphersuites in the future, since servers
5273 can't know whether an advertised ciphersuite is really supported or
5274 not. Some hosts -- notably, ones with very old versions of OpenSSL
5275 or where OpenSSL has been built with ECC disabled -- will stand
5276 out because of this change; TBB users should not be affected.
5279 - Change the default value for DynamicDHGroups (introduced in
5280 0.2.3.9-alpha) to 0. This feature can make Tor relays less
5281 identifiable by their use of the mod_ssl DH group, but at
5282 the cost of some usability (#4721) and bridge tracing (#6087)
5283 regressions. Resolves ticket 5598.
5284 - Send a CRLF at the end of each STATUS_* control protocol event. This
5285 bug tickled a bug in Vidalia which would make it freeze. Fixes
5286 bug 6094; bugfix on 0.2.3.16-alpha.
5289 - Disable writing on marked-for-close connections when they are
5290 blocked on bandwidth, to prevent busy-looping in Libevent. Fixes
5291 bug 5263; bugfix on 0.0.2pre13, where we first added a special
5292 case for flushing marked connections.
5293 - Detect SSL handshake even when the initial attempt to write the
5294 server hello fails. Fixes bug 4592; bugfix on 0.2.0.13-alpha.
5295 - Change the AllowDotExit rules so they should actually work.
5296 We now enforce AllowDotExit only immediately after receiving an
5297 address via SOCKS or DNSPort: other sources are free to provide
5298 .exit addresses after the resolution occurs. Fixes bug 3940;
5299 bugfix on 0.2.2.1-alpha.
5300 - Fix a (harmless) integer overflow in cell statistics reported by
5301 some fast relays. Fixes bug 5849; bugfix on 0.2.2.1-alpha.
5302 - Make sure circuitbuild.c checks LearnCircuitBuildTimeout in all the
5303 right places and never depends on the consensus parameters or
5304 computes adaptive timeouts when it is disabled. Fixes bug 5049;
5305 bugfix on 0.2.2.14-alpha.
5306 - When building Tor on Windows with -DUNICODE (not default), ensure
5307 that error messages, filenames, and DNS server names are always
5308 NUL-terminated when we convert them to a single-byte encoding.
5309 Fixes bug 5909; bugfix on 0.2.2.16-alpha.
5310 - Make Tor build correctly again with -DUNICODE -D_UNICODE defined.
5311 Fixes bug 6097; bugfix on 0.2.2.16-alpha.
5312 - Fix an edge case where TestingTorNetwork is set but the authorities
5313 and relays all have an uptime of zero, where the private Tor network
5314 could briefly lack support for hidden services. Fixes bug 3886;
5315 bugfix on 0.2.2.18-alpha.
5316 - Correct the manpage's descriptions for the default values of
5317 DirReqStatistics and ExtraInfoStatistics. Fixes bug 2865; bugfix
5319 - Fix the documentation for the --hush and --quiet command line
5320 options, which changed their behavior back in 0.2.3.3-alpha.
5321 - Fix compilation warning with clang 3.1. Fixes bug 6141; bugfix on
5325 - Rate-limit the "Weighted bandwidth is 0.000000" message, and add
5326 more information to it, so that we can track it down in case it
5327 returns again. Mitigates bug 5235.
5328 - Check CircuitBuildTimeout and LearnCircuitBuildTimeout in
5329 options_validate(); warn if LearnCircuitBuildTimeout is disabled and
5330 CircuitBuildTimeout is set unreasonably low. Resolves ticket 5452.
5331 - Warn the user when HTTPProxy, but no other proxy type, is
5332 configured. This can cause surprising behavior: it doesn't send
5333 all of Tor's traffic over the HTTPProxy -- it sends unencrypted
5334 directory traffic only. Resolves ticket 4663.
5335 - Issue a notice if a guard completes less than 40% of your circuits.
5336 Threshold is configurable by torrc option PathBiasNoticeRate and
5337 consensus parameter pb_noticepct. There is additional, off-by-
5338 default code to disable guards which fail too many circuits.
5339 Addresses ticket 5458.
5340 - Update to the June 6 2012 Maxmind GeoLite Country database.
5342 o Code simplifications and refactoring:
5343 - Remove validate_pluggable_transports_config(): its warning
5344 message is now handled by connection_or_connect().
5347 Changes in version 0.2.2.37 - 2012-06-06
5348 Tor 0.2.2.37 introduces a workaround for a critical renegotiation
5349 bug in OpenSSL 1.0.1 (where 20% of the Tor network can't talk to itself
5353 - Work around a bug in OpenSSL that broke renegotiation with TLS
5354 1.1 and TLS 1.2. Without this workaround, all attempts to speak
5355 the v2 Tor connection protocol when both sides were using OpenSSL
5356 1.0.1 would fail. Resolves ticket 6033.
5357 - When waiting for a client to renegotiate, don't allow it to add
5358 any bytes to the input buffer. This fixes a potential DoS issue.
5359 Fixes bugs 5934 and 6007; bugfix on 0.2.0.20-rc.
5360 - Fix an edge case where if we fetch or publish a hidden service
5361 descriptor, we might build a 4-hop circuit and then use that circuit
5362 for exiting afterwards -- even if the new last hop doesn't obey our
5363 ExitNodes config option. Fixes bug 5283; bugfix on 0.2.0.10-alpha.
5366 - Fix a build warning with Clang 3.1 related to our use of vasprintf.
5367 Fixes bug 5969. Bugfix on 0.2.2.11-alpha.
5370 - Tell GCC and Clang to check for any errors in format strings passed
5371 to the tor_v*(print|scan)f functions.
5374 Changes in version 0.2.3.16-alpha - 2012-06-05
5375 Tor 0.2.3.16-alpha introduces a workaround for a critical renegotiation
5376 bug in OpenSSL 1.0.1 (where 20% of the Tor network can't talk to itself
5377 currently). It also fixes a variety of smaller bugs and other cleanups
5378 that get us closer to a release candidate.
5380 o Major bugfixes (general):
5381 - Work around a bug in OpenSSL that broke renegotiation with TLS
5382 1.1 and TLS 1.2. Without this workaround, all attempts to speak
5383 the v2 Tor connection protocol when both sides were using OpenSSL
5384 1.0.1 would fail. Resolves ticket 6033.
5385 - When waiting for a client to renegotiate, don't allow it to add
5386 any bytes to the input buffer. This fixes a potential DoS issue.
5387 Fixes bugs 5934 and 6007; bugfix on 0.2.0.20-rc.
5388 - Pass correct OR address to managed proxies (like obfsproxy),
5389 even when ORListenAddress is used. Fixes bug 4865; bugfix on
5391 - The advertised platform of a router now includes only its operating
5392 system's name (e.g., "Linux", "Darwin", "Windows 7"), and not its
5393 service pack level (for Windows) or its CPU architecture (for Unix).
5394 We also no longer include the "git-XYZ" tag in the version. Resolves
5397 o Major bugfixes (clients):
5398 - If we are unable to find any exit that supports our predicted ports,
5399 stop calling them predicted, so that we don't loop and build
5400 hopeless circuits indefinitely. Fixes bug 3296; bugfix on 0.0.9pre6,
5401 which introduced predicted ports.
5402 - Fix an edge case where if we fetch or publish a hidden service
5403 descriptor, we might build a 4-hop circuit and then use that circuit
5404 for exiting afterwards -- even if the new last hop doesn't obey our
5405 ExitNodes config option. Fixes bug 5283; bugfix on 0.2.0.10-alpha.
5406 - Check at each new consensus whether our entry guards were picked
5407 long enough ago that we should rotate them. Previously, we only
5408 did this check at startup, which could lead to us holding a guard
5409 indefinitely. Fixes bug 5380; bugfix on 0.2.1.14-rc.
5410 - When fetching a bridge descriptor from a bridge authority,
5411 always do so anonymously, whether we have been able to open
5412 circuits or not. Partial fix for bug 1938; bugfix on 0.2.0.7-alpha.
5413 This behavior makes it *safer* to use UpdateBridgesFromAuthority,
5414 but we'll need to wait for bug 6010 before it's actually usable.
5416 o Major bugfixes (directory authorities):
5417 - When computing weight parameters, behave more robustly in the
5418 presence of a bad bwweightscale value. Previously, the authorities
5419 would crash if they agreed on a sufficiently broken weight_scale
5420 value: now, they use a reasonable default and carry on. Partial
5421 fix for 5786; bugfix on 0.2.2.17-alpha.
5422 - Check more thoroughly to prevent a rogue authority from
5423 double-voting on any consensus directory parameter. Previously,
5424 authorities would crash in this case if the total number of
5425 votes for any parameter exceeded the number of active voters,
5426 but would let it pass otherwise. Partial fix for bug 5786; bugfix
5430 - Rate-limit log messages when asked to connect anonymously to
5431 a private address. When these hit, they tended to hit fast and
5432 often. Also, don't bother trying to connect to addresses that we
5433 are sure will resolve to 127.0.0.1: getting 127.0.0.1 in a directory
5434 reply makes us think we have been lied to, even when the address the
5435 client tried to connect to was "localhost." Resolves ticket 2822.
5436 - Allow packagers to insert an extra string in server descriptor
5437 platform lines by setting the preprocessor variable TOR_BUILD_TAG.
5438 Resolves the rest of ticket 2988.
5439 - Raise the threshold of server descriptors needed (75%) and exit
5440 server descriptors needed (50%) before we will declare ourselves
5441 bootstrapped. This will make clients start building circuits a
5442 little later, but makes the initially constructed circuits less
5443 skewed and less in conflict with further directory fetches. Fixes
5445 - Close any connection that sends unrecognized junk before the
5446 handshake. Solves an issue noted in bug 4369.
5447 - Improve log messages about managed transports. Resolves ticket 5070.
5448 - Tag a bridge's descriptor as "never to be sent unencrypted".
5449 This shouldn't matter, since bridges don't open non-anonymous
5450 connections to the bridge authority and don't allow unencrypted
5451 directory connections from clients, but we might as well make
5452 sure. Closes bug 5139.
5453 - Expose our view of whether we have gone dormant to the controller,
5454 via a new "GETINFO dormant" value. Torbutton and other controllers
5455 can use this to avoid doing periodic requests through Tor while
5456 it's dormant (bug 4718). Fixes bug 5954.
5457 - Tell GCC and Clang to check for any errors in format strings passed
5458 to the tor_v*(print|scan)f functions.
5459 - Update to the May 1 2012 Maxmind GeoLite Country database.
5461 o Minor bugfixes (already included in 0.2.2.36):
5462 - Reject out-of-range times like 23:59:61 in parse_rfc1123_time().
5463 Fixes bug 5346; bugfix on 0.0.8pre3.
5464 - Correct parsing of certain date types in parse_http_time().
5465 Without this patch, If-Modified-Since would behave
5466 incorrectly. Fixes bug 5346; bugfix on 0.2.0.2-alpha. Patch from
5467 Esteban Manchado Velázques.
5468 - Make our number-parsing functions always treat too-large values
5469 as an error, even when those values exceed the width of the
5470 underlying type. Previously, if the caller provided these
5471 functions with minima or maxima set to the extreme values of the
5472 underlying integer type, these functions would return those
5473 values on overflow rather than treating overflow as an error.
5474 Fixes part of bug 5786; bugfix on 0.0.9.
5475 - If we hit the error case where routerlist_insert() replaces an
5476 existing (old) server descriptor, make sure to remove that
5477 server descriptor from the old_routers list. Fix related to bug
5478 1776. Bugfix on 0.2.2.18-alpha.
5479 - Clarify the behavior of MaxCircuitDirtiness with hidden service
5480 circuits. Fixes issue 5259.
5482 o Minor bugfixes (coding cleanup, on 0.2.2.x and earlier):
5483 - Prevent a null-pointer dereference when receiving a data cell
5484 for a nonexistent stream when the circuit in question has an
5485 empty deliver window. We don't believe this is triggerable,
5486 since we don't currently allow deliver windows to become empty,
5487 but the logic is tricky enough that it's better to make the code
5488 robust. Fixes bug 5541; bugfix on 0.0.2pre14.
5489 - Fix a memory leak when trying to launch a DNS request when the
5490 network is disabled or the nameservers are unconfigurable. Fixes
5491 bug 5916; bugfix on Tor 0.1.2.1-alpha (for the unconfigurable
5492 nameserver case) and on 0.2.3.9-alpha (for the DisableNetwork case).
5493 - Don't hold a Windows file handle open for every file mapping;
5494 the file mapping handle is sufficient. Fixes bug 5951; bugfix on
5496 - Avoid O(n^2) performance characteristics when parsing a large
5497 extrainfo cache. Fixes bug 5828; bugfix on 0.2.0.1-alpha.
5498 - Format more doubles with %f, not %lf. Patch from grarpamp to make
5499 Tor build correctly on older BSDs again. Fixes bug 3894; bugfix on
5501 - Make our replacement implementation of strtok_r() compatible with
5502 the standard behavior of strtok_r(). Patch by nils. Fixes bug 5091;
5503 bugfix on 0.2.2.1-alpha.
5504 - Fix a NULL-pointer dereference on a badly formed
5505 SETCIRCUITPURPOSE command. Found by mikeyc. Fixes bug 5796;
5506 bugfix on 0.2.2.9-alpha.
5507 - Fix a build warning with Clang 3.1 related to our use of vasprintf.
5508 Fixes bug 5969. Bugfix on 0.2.2.11-alpha.
5509 - Defensively refactor rend_mid_rendezvous() so that protocol
5510 violations and length checks happen in the beginning. Fixes
5512 - Set _WIN32_WINNT to 0x0501 consistently throughout the code, so
5513 that IPv6 stuff will compile on MSVC, and compilation issues
5514 will be easier to track down. Fixes bug 5861.
5516 o Minor bugfixes (correctness, on 0.2.2.x and earlier):
5517 - Exit nodes now correctly report EADDRINUSE and EADDRNOTAVAIL as
5518 resource exhaustion, so that clients can adjust their load to
5519 try other exits. Fixes bug 4710; bugfix on 0.1.0.1-rc, which
5520 started using END_STREAM_REASON_RESOURCELIMIT.
5521 - Don't check for whether the address we're using for outbound
5522 connections has changed until after the outbound connection has
5523 completed. On Windows, getsockname() doesn't succeed until the
5524 connection is finished. Fixes bug 5374; bugfix on 0.1.1.14-alpha.
5525 - If the configuration tries to set MyFamily on a bridge, refuse to
5526 do so, and warn about the security implications. Fixes bug 4657;
5527 bugfix on 0.2.0.3-alpha.
5528 - If the client fails to set a reasonable set of ciphersuites
5529 during its v2 handshake renegotiation, allow the renegotiation to
5530 continue nevertheless (i.e. send all the required certificates).
5531 Fixes bug 4591; bugfix on 0.2.0.20-rc.
5532 - When we receive a SIGHUP and the controller __ReloadTorrcOnSIGHUP
5533 option is set to 0 (which Vidalia version 0.2.16 now does when
5534 a SAVECONF attempt fails), perform other actions that SIGHUP
5535 usually causes (like reopening the logs). Fixes bug 5095; bugfix
5537 - If we fail to write a microdescriptor to the disk cache, do not
5538 continue replacing the old microdescriptor file. Fixes bug 2954;
5539 bugfix on 0.2.2.6-alpha.
5540 - Exit nodes don't need to fetch certificates for authorities that
5541 they don't recognize; only directory authorities, bridges,
5542 and caches need to do that. Fixes part of bug 2297; bugfix on
5544 - Correctly handle checking the permissions on the parent
5545 directory of a control socket in the root directory. Bug found
5546 by Esteban Manchado Velázquez. Fixes bug 5089; bugfix on Tor
5548 - When told to add a bridge with the same digest as a preexisting
5549 bridge but a different addr:port, change the addr:port as
5550 requested. Previously we would not notice the change. Fixes half
5551 of bug 5603; fix on 0.2.2.26-beta.
5552 - End AUTHCHALLENGE error messages (in the control protocol) with
5553 a CRLF. Fixes bug 5760; bugfix on 0.2.2.36 and 0.2.3.13-alpha.
5555 o Minor bugfixes (on 0.2.3.x):
5556 - Turn an assertion (that the number of handshakes received as a
5557 server is not < 1) into a warning. Fixes bug 4873; bugfix on
5559 - Format IPv4 addresses correctly in ADDRMAP events. (Previously,
5560 we had reversed them when the answer was cached.) Fixes bug
5561 5723; bugfix on 0.2.3.1-alpha.
5562 - Work correctly on Linux systems with accept4 support advertised in
5563 their headers, but without accept4 support in the kernel. Fix
5564 by murb. Fixes bug 5762; bugfix on 0.2.3.1-alpha.
5565 - When told to add a bridge with the same addr:port as a preexisting
5566 bridge but a different transport, change the transport as
5567 requested. Previously we would not notice the change. Fixes half
5568 of bug 5603; fix on 0.2.3.2-alpha.
5569 - Avoid a "double-reply" warning when replying to a SOCKS request
5570 with a parse error. Patch from Fabian Keil. Fixes bug 4108;
5571 bugfix on 0.2.3.4-alpha.
5572 - Fix a bug where a bridge authority crashes if it has seen no
5573 directory requests when it's time to write statistics to disk.
5574 Fixes bug 5891; bugfix on 0.2.3.6-alpha. Also fixes bug 5508 in
5576 - Don't try to open non-control listeners when DisableNetwork is set.
5577 Previously, we'd open all listeners, then immediately close them.
5578 Fixes bug 5604; bugfix on 0.2.3.9-alpha.
5579 - Don't abort the managed proxy protocol if the managed proxy
5580 sends us an unrecognized line; ignore it instead. Fixes bug
5581 5910; bugfix on 0.2.3.9-alpha.
5582 - Fix a compile warning in crypto.c when compiling with clang 3.1.
5583 Fixes bug 5969, bugfix on 0.2.3.9-alpha.
5584 - Fix a compilation issue on GNU Hurd, which doesn't have PATH_MAX.
5585 Fixes bug 5355; bugfix on 0.2.3.11-alpha.
5586 - Remove bogus definition of "_WIN32" from src/win32/orconfig.h, to
5587 unbreak the MSVC build. Fixes bug 5858; bugfix on 0.2.3.12-alpha.
5588 - Resolve numerous small warnings and build issues with MSVC. Resolves
5591 o Documentation fixes:
5592 - Improve the manual's documentation for the NT Service command-line
5593 options. Addresses ticket 3964.
5594 - Clarify SessionGroup documentation slightly; resolves ticket 5437.
5595 - Document the changes to the ORPort and DirPort options, and the
5596 fact that {OR/Dir}ListenAddress is now unnecessary (and
5597 therefore deprecated). Resolves ticket 5597.
5600 - Remove the torrc.bridge file: we don't use it for anything, and
5601 it had become badly desynchronized from torrc.sample. Resolves
5605 Changes in version 0.2.2.36 - 2012-05-24
5606 Tor 0.2.2.36 updates the addresses for two of the eight directory
5607 authorities, fixes some potential anonymity and security issues,
5608 and fixes several crash bugs.
5610 Tor 0.2.1.x has reached its end-of-life. Those Tor versions have many
5611 known flaws, and nobody should be using them. You should upgrade. If
5612 you're using a Linux or BSD and its packages are obsolete, stop using
5613 those packages and upgrade anyway.
5615 o Directory authority changes:
5616 - Change IP address for maatuska (v3 directory authority).
5617 - Change IP address for ides (v3 directory authority), and rename
5621 - When building or running with any version of OpenSSL earlier
5622 than 0.9.8s or 1.0.0f, disable SSLv3 support. These OpenSSL
5623 versions have a bug (CVE-2011-4576) in which their block cipher
5624 padding includes uninitialized data, potentially leaking sensitive
5625 information to any peer with whom they make a SSLv3 connection. Tor
5626 does not use SSL v3 by default, but a hostile client or server
5627 could force an SSLv3 connection in order to gain information that
5628 they shouldn't have been able to get. The best solution here is to
5629 upgrade to OpenSSL 0.9.8s or 1.0.0f (or later). But when building
5630 or running with a non-upgraded OpenSSL, we disable SSLv3 entirely
5631 to make sure that the bug can't happen.
5632 - Never use a bridge or a controller-supplied node as an exit, even
5633 if its exit policy allows it. Found by wanoskarnet. Fixes bug
5634 5342. Bugfix on 0.1.1.15-rc (for controller-purpose descriptors)
5635 and 0.2.0.3-alpha (for bridge-purpose descriptors).
5636 - Only build circuits if we have a sufficient threshold of the total
5637 descriptors that are marked in the consensus with the "Exit"
5638 flag. This mitigates an attack proposed by wanoskarnet, in which
5639 all of a client's bridges collude to restrict the exit nodes that
5640 the client knows about. Fixes bug 5343.
5641 - Provide controllers with a safer way to implement the cookie
5642 authentication mechanism. With the old method, if another locally
5643 running program could convince a controller that it was the Tor
5644 process, then that program could trick the controller into telling
5645 it the contents of an arbitrary 32-byte file. The new "SAFECOOKIE"
5646 authentication method uses a challenge-response approach to prevent
5647 this attack. Fixes bug 5185; implements proposal 193.
5650 - Avoid logging uninitialized data when unable to decode a hidden
5651 service descriptor cookie. Fixes bug 5647; bugfix on 0.2.1.5-alpha.
5652 - Avoid a client-side assertion failure when receiving an INTRODUCE2
5653 cell on a general purpose circuit. Fixes bug 5644; bugfix on
5655 - Fix builds when the path to sed, openssl, or sha1sum contains
5656 spaces, which is pretty common on Windows. Fixes bug 5065; bugfix
5658 - Correct our replacements for the timeradd() and timersub() functions
5659 on platforms that lack them (for example, Windows). The timersub()
5660 function is used when expiring circuits, while timeradd() is
5661 currently unused. Bug report and patch by Vektor. Fixes bug 4778;
5662 bugfix on 0.2.2.24-alpha.
5663 - Fix the SOCKET_OK test that we use to tell when socket
5664 creation fails so that it works on Win64. Fixes part of bug 4533;
5665 bugfix on 0.2.2.29-beta. Bug found by wanoskarnet.
5668 - Reject out-of-range times like 23:59:61 in parse_rfc1123_time().
5669 Fixes bug 5346; bugfix on 0.0.8pre3.
5670 - Make our number-parsing functions always treat too-large values
5671 as an error, even when those values exceed the width of the
5672 underlying type. Previously, if the caller provided these
5673 functions with minima or maxima set to the extreme values of the
5674 underlying integer type, these functions would return those
5675 values on overflow rather than treating overflow as an error.
5676 Fixes part of bug 5786; bugfix on 0.0.9.
5677 - Older Linux kernels erroneously respond to strange nmap behavior
5678 by having accept() return successfully with a zero-length
5679 socket. When this happens, just close the connection. Previously,
5680 we would try harder to learn the remote address: but there was
5681 no such remote address to learn, and our method for trying to
5682 learn it was incorrect. Fixes bugs 1240, 4745, and 4747. Bugfix
5683 on 0.1.0.3-rc. Reported and diagnosed by "r1eo".
5684 - Correct parsing of certain date types in parse_http_time().
5685 Without this patch, If-Modified-Since would behave
5686 incorrectly. Fixes bug 5346; bugfix on 0.2.0.2-alpha. Patch from
5687 Esteban Manchado Velázques.
5688 - Change the BridgePassword feature (part of the "bridge community"
5689 design, which is not yet implemented) to use a time-independent
5690 comparison. The old behavior might have allowed an adversary
5691 to use timing to guess the BridgePassword value. Fixes bug 5543;
5692 bugfix on 0.2.0.14-alpha.
5693 - Detect and reject certain misformed escape sequences in
5694 configuration values. Previously, these values would cause us
5695 to crash if received in a torrc file or over an authenticated
5696 control port. Bug found by Esteban Manchado Velázquez, and
5697 independently by Robert Connolly from Matta Consulting who further
5698 noted that it allows a post-authentication heap overflow. Patch
5699 by Alexander Schrijver. Fixes bugs 5090 and 5402 (CVE 2012-1668);
5700 bugfix on 0.2.0.16-alpha.
5701 - Fix a compile warning when using the --enable-openbsd-malloc
5702 configure option. Fixes bug 5340; bugfix on 0.2.0.20-rc.
5703 - During configure, detect when we're building with clang version
5704 3.0 or lower and disable the -Wnormalized=id and -Woverride-init
5705 CFLAGS. clang doesn't support them yet.
5706 - When sending an HTTP/1.1 proxy request, include a Host header.
5707 Fixes bug 5593; bugfix on 0.2.2.1-alpha.
5708 - Fix a NULL-pointer dereference on a badly formed SETCIRCUITPURPOSE
5709 command. Found by mikeyc. Fixes bug 5796; bugfix on 0.2.2.9-alpha.
5710 - If we hit the error case where routerlist_insert() replaces an
5711 existing (old) server descriptor, make sure to remove that
5712 server descriptor from the old_routers list. Fix related to bug
5713 1776. Bugfix on 0.2.2.18-alpha.
5715 o Minor bugfixes (documentation and log messages):
5716 - Fix a typo in a log message in rend_service_rendezvous_has_opened().
5717 Fixes bug 4856; bugfix on Tor 0.0.6.
5718 - Update "ClientOnly" man page entry to explain that there isn't
5719 really any point to messing with it. Resolves ticket 5005.
5720 - Document the GiveGuardFlagTo_CVE_2011_2768_VulnerableRelays
5721 directory authority option (introduced in Tor 0.2.2.34).
5722 - Downgrade the "We're missing a certificate" message from notice
5723 to info: people kept mistaking it for a real problem, whereas it
5724 is seldom the problem even when we are failing to bootstrap. Fixes
5725 bug 5067; bugfix on 0.2.0.10-alpha.
5726 - Correctly spell "connect" in a log message on failure to create a
5727 controlsocket. Fixes bug 4803; bugfix on 0.2.2.26-beta.
5728 - Clarify the behavior of MaxCircuitDirtiness with hidden service
5729 circuits. Fixes issue 5259.
5732 - Directory authorities now reject versions of Tor older than
5733 0.2.1.30, and Tor versions between 0.2.2.1-alpha and 0.2.2.20-alpha
5734 inclusive. These versions accounted for only a small fraction of
5735 the Tor network, and have numerous known security issues. Resolves
5737 - Update to the May 1 2012 Maxmind GeoLite Country database.
5740 - When sending or relaying a RELAY_EARLY cell, we used to convert
5741 it to a RELAY cell if the connection was using the v1 link
5742 protocol. This was a workaround for older versions of Tor, which
5743 didn't handle RELAY_EARLY cells properly. Now that all supported
5744 versions can handle RELAY_EARLY cells, and now that we're enforcing
5745 the "no RELAY_EXTEND commands except in RELAY_EARLY cells" rule,
5746 remove this workaround. Addresses bug 4786.
5749 Changes in version 0.2.3.15-alpha - 2012-04-30
5750 Tor 0.2.3.15-alpha fixes a variety of smaller bugs, including making
5751 the development branch build on Windows again.
5753 o Minor bugfixes (on 0.2.2.x and earlier):
5754 - Make sure that there are no unhandled pending TLS errors before
5755 reading from a TLS stream. We had checks in 0.1.0.3-rc, but
5756 lost them in 0.1.0.5-rc when we refactored read_to_buf_tls().
5757 Bugfix on 0.1.0.5-rc; fixes bug 4528.
5758 - Fix an assert that directory authorities could trigger on sighup
5759 during some configuration state transitions. We now don't treat
5760 it as a fatal error when the new descriptor we just generated in
5761 init_keys() isn't accepted. Fixes bug 4438; bugfix on 0.2.1.9-alpha.
5762 - After we pick a directory mirror, we would refuse to use it if
5763 it's in our ExcludeExitNodes list, resulting in mysterious failures
5764 to bootstrap for people who just wanted to avoid exiting from
5765 certain locations. Fixes bug 5623; bugfix on 0.2.2.25-alpha.
5766 - When building with --enable-static-tor on OpenBSD, do not
5767 erroneously attempt to link -lrt. Fixes bug 5103.
5769 o Minor bugfixes (on 0.2.3.x):
5770 - When Tor is built with kernel headers from a recent (last few
5771 years) Linux kernel, do not fail to run on older (pre-2.6.28
5772 Linux kernels). Fixes bug 5112; bugfix on 0.2.3.1-alpha.
5773 - Fix cross-compilation issues with mingw. Bugfixes on 0.2.3.6-alpha
5775 - Fix compilation with miniupnpc version 1.6; patch from
5776 Anthony G. Basile. Fixes bug 5434; bugfix on 0.2.3.12-alpha.
5777 - Fix compilation with MSVC, which had defined MS_WINDOWS. Bugfix
5778 on 0.2.3.13-alpha; found and fixed by Gisle Vanem.
5779 - Fix compilation on platforms without unistd.h, or where environ
5780 is defined in stdlib.h. Fixes bug 5704; bugfix on 0.2.3.13-alpha.
5783 - Directory authorities are now a little more lenient at accepting
5784 older router descriptors, or newer router descriptors that don't
5785 make big changes. This should help ameliorate past and future
5786 issues where routers think they have uploaded valid descriptors,
5787 but the authorities don't think so. Fix for ticket 2479.
5788 - Make the code that clients use to detect an address change be
5789 IPv6-aware, so that it won't fill clients' logs with error
5790 messages when trying to get the IPv4 address of an IPv6
5791 connection. Implements ticket 5537.
5794 - Remove the GiveGuardFlagTo_CVE_2011_2768_VulnerableRelays option;
5795 authorities needed to use it for a while to keep the network working
5796 as people upgraded to 0.2.1.31, 0.2.2.34, or 0.2.3.6-alpha, but
5797 that was six months ago. As of now, it should no longer be needed
5801 Changes in version 0.2.3.14-alpha - 2012-04-23
5802 Tor 0.2.3.14-alpha fixes yet more bugs to get us closer to a release
5803 candidate. It also dramatically speeds up AES: fast relays should
5804 consider switching to the newer OpenSSL library.
5806 o Directory authority changes:
5807 - Change IP address for ides (v3 directory authority), and rename
5811 - Avoid logging uninitialized data when unable to decode a hidden
5812 service descriptor cookie. Fixes bug 5647; bugfix on 0.2.1.5-alpha.
5813 - Avoid a client-side assertion failure when receiving an INTRODUCE2
5814 cell on a general purpose circuit. Fixes bug 5644; bugfix on
5816 - If authorities are unable to get a v2 consensus document from other
5817 directory authorities, they no longer fall back to fetching
5818 them from regular directory caches. Fixes bug 5635; bugfix on
5819 0.2.2.26-beta, where routers stopped downloading v2 consensus
5821 - When we start a Tor client with a normal consensus already cached,
5822 be willing to download a microdescriptor consensus. Fixes bug 4011;
5823 fix on 0.2.3.1-alpha.
5825 o Major features (performance):
5826 - When built to use OpenSSL 1.0.1, and built for an x86 or x86_64
5827 instruction set, take advantage of OpenSSL's AESNI, bitsliced, or
5828 vectorized AES implementations as appropriate. These can be much,
5829 much faster than other AES implementations.
5831 o Minor bugfixes (0.2.2.x and earlier):
5832 - Don't launch more than 10 service-side introduction-point circuits
5833 for a hidden service in five minutes. Previously, we would consider
5834 launching more introduction-point circuits if at least one second
5835 had passed without any introduction-point circuits failing. Fixes
5836 bug 4607; bugfix on 0.0.7pre1.
5837 - Change the BridgePassword feature (part of the "bridge community"
5838 design, which is not yet implemented) to use a time-independent
5839 comparison. The old behavior might have allowed an adversary
5840 to use timing to guess the BridgePassword value. Fixes bug 5543;
5841 bugfix on 0.2.0.14-alpha.
5842 - Enforce correct return behavior of tor_vsscanf() when the '%%'
5843 pattern is used. Fixes bug 5558. Bugfix on 0.2.1.13.
5844 - When sending an HTTP/1.1 proxy request, include a Host header.
5845 Fixes bug 5593; bugfix on 0.2.2.1-alpha.
5846 - Don't log that we have "decided to publish new relay descriptor"
5847 unless we are actually publishing a descriptor. Fixes bug 3942;
5848 bugfix on 0.2.2.28-beta.
5850 o Minor bugfixes (0.2.3.x):
5851 - Fix a bug where a bridge authority crashes (on a failed assert)
5852 if it has seen no directory requests when it's time to write
5853 statistics to disk. Fixes bug 5508. Bugfix on 0.2.3.6-alpha.
5854 - Fix bug stomping on ORPort option NoListen and ignoring option
5855 NoAdvertise. Fixes bug 5151; bugfix on 0.2.3.9-alpha.
5856 - In the testsuite, provide a large enough buffer in the tor_sscanf
5857 unit test. Otherwise we'd overrun that buffer and crash during
5858 the unit tests. Found by weasel. Fixes bug 5449; bugfix on
5860 - Make sure we create the keys directory if it doesn't exist and we're
5861 about to store the dynamic Diffie-Hellman parameters. Fixes bug
5862 5572; bugfix on 0.2.3.13-alpha.
5863 - Fix a small memory leak when trying to decode incorrect base16
5864 authenticator during SAFECOOKIE authentication. Found by
5865 Coverity Scan. Fixes CID 507. Bugfix on 0.2.3.13-alpha.
5868 - Add more information to a log statement that might help track down
5869 bug 4091. If you're seeing "Bug: tor_addr_is_internal() called with a
5870 non-IP address" messages (or any Bug messages, for that matter!),
5871 please let us know about it.
5872 - Relays now understand an IPv6 address when they get one from a
5873 directory server. Resolves ticket 4875.
5874 - Resolve IPv6 addresses in bridge and entry statistics to country
5875 code "??" which means we at least count them. Resolves ticket 5053;
5876 improves on 0.2.3.9-alpha.
5877 - Update to the April 3 2012 Maxmind GeoLite Country database.
5878 - Begin a doc/state-contents.txt file to explain the contents of
5879 the Tor state file. Fixes bug 2987.
5881 o Default torrc changes:
5882 - Stop listing "socksport 9050" in torrc.sample. We open a socks
5883 port on 9050 by default anyway, so this should not change anything
5885 - Stop mentioning the deprecated *ListenAddress options in
5886 torrc.sample. Fixes bug 5438.
5887 - Document unit of bandwidth related options in sample torrc.
5891 - The "torify" script no longer supports the "tsocks" socksifier
5892 tool, since tsocks doesn't support DNS and UDP right for Tor.
5893 Everyone should be using torsocks instead. Fixes bugs 3530 and
5894 5180. Based on a patch by "ugh".
5897 - Change the symmetric cipher interface so that creating and
5898 initializing a stream cipher are no longer separate functions.
5899 - Remove all internal support for unpadded RSA. We never used it, and
5900 it would be a bad idea to start.
5903 Changes in version 0.2.3.13-alpha - 2012-03-26
5904 Tor 0.2.3.13-alpha fixes a variety of stability and correctness bugs
5905 in managed pluggable transports, as well as providing other cleanups
5906 that get us closer to a release candidate.
5908 o Directory authority changes:
5909 - Change IP address for maatuska (v3 directory authority).
5912 - Provide controllers with a safer way to implement the cookie
5913 authentication mechanism. With the old method, if another locally
5914 running program could convince a controller that it was the Tor
5915 process, then that program could trick the controller into telling
5916 it the contents of an arbitrary 32-byte file. The new "SAFECOOKIE"
5917 authentication method uses a challenge-response approach to prevent
5918 this attack. Fixes bug 5185, implements proposal 193.
5919 - Never use a bridge or a controller-supplied node as an exit, even
5920 if its exit policy allows it. Found by wanoskarnet. Fixes bug
5921 5342. Bugfix on 0.1.1.15-rc (for controller-purpose descriptors)
5922 and 0.2.0.3-alpha (for bridge-purpose descriptors).
5923 - Only build circuits if we have a sufficient threshold of the total
5924 descriptors that are marked in the consensus with the "Exit"
5925 flag. This mitigates an attack proposed by wanoskarnet, in which
5926 all of a client's bridges collude to restrict the exit nodes that
5927 the client knows about. Fixes bug 5343.
5929 o Major bugfixes (on Tor 0.2.3.x):
5930 - Avoid an assert when managed proxies like obfsproxy are configured,
5931 and we receive HUP signals or setconf attempts too rapidly. This
5932 situation happens most commonly when Vidalia tries to attach to
5933 Tor or tries to configure the Tor it's attached to. Fixes bug 5084;
5934 bugfix on 0.2.3.6-alpha.
5935 - Fix a relay-side pluggable transports bug where managed proxies were
5936 unreachable from the Internet, because Tor asked them to bind on
5937 localhost. Fixes bug 4725; bugfix on 0.2.3.9-alpha.
5938 - Stop discarding command-line arguments when TestingTorNetwork
5939 is set. Discovered by Kevin Bauer. Fixes bug 5373; bugfix on
5940 0.2.3.9-alpha, where task 4552 added support for two layers of
5942 - Resume allowing the unit tests to run in gdb. This was accidentally
5943 made impossible when the DisableDebuggerAttachment option was
5944 introduced. Fixes bug 5448; bugfix on 0.2.3.9-alpha.
5945 - Resume building with nat-pmp support. Fixes bug 4955; bugfix on
5946 0.2.3.11-alpha. Reported by Anthony G. Basile.
5948 o Minor bugfixes (on 0.2.2.x and earlier):
5949 - Ensure we don't cannibalize circuits that are longer than three hops
5950 already, so we don't end up making circuits with 5 or more
5951 hops. Patch contributed by wanoskarnet. Fixes bug 5231; bugfix on
5952 0.1.0.1-rc which introduced cannibalization.
5953 - Detect and reject certain misformed escape sequences in
5954 configuration values. Previously, these values would cause us
5955 to crash if received in a torrc file or over an authenticated
5956 control port. Bug found by Esteban Manchado Velázquez, and
5957 independently by Robert Connolly from Matta Consulting who further
5958 noted that it allows a post-authentication heap overflow. Patch
5959 by Alexander Schrijver. Fixes bugs 5090 and 5402 (CVE 2012-1668);
5960 bugfix on 0.2.0.16-alpha.
5961 - Fix a compile warning when using the --enable-openbsd-malloc
5962 configure option. Fixes bug 5340; bugfix on 0.2.0.20-rc.
5963 - Directory caches no longer refuse to clean out descriptors because
5964 of missing v2 networkstatus documents, unless they're configured
5965 to retrieve v2 networkstatus documents. Fixes bug 4838; bugfix on
5966 0.2.2.26-beta. Patch by Daniel Bryg.
5967 - Update to the latest version of the tinytest unit testing framework.
5968 This includes a couple of bugfixes that can be relevant for
5969 running forked unit tests on Windows, and removes all reserved
5972 o Minor bugfixes (on 0.2.3.x):
5973 - On a failed pipe() call, don't leak file descriptors. Fixes bug
5974 4296; bugfix on 0.2.3.1-alpha.
5975 - Spec conformance: on a v3 handshake, do not send a NETINFO cell
5976 until after we have received a CERTS cell. Fixes bug 4361; bugfix
5977 on 0.2.3.6-alpha. Patch by "frosty".
5978 - When binding to an IPv6 address, set the IPV6_V6ONLY socket
5979 option, so that the IP stack doesn't decide to use it for IPv4
5980 too. Fixes bug 4760; bugfix on 0.2.3.9-alpha.
5981 - Ensure that variables set in Tor's environment cannot override
5982 environment variables that Tor passes to a managed
5983 pluggable-transport proxy. Previously, Tor would pass every
5984 variable in its environment to managed proxies along with the new
5985 ones, in such a way that on many operating systems, the inherited
5986 environment variables would override those which Tor tried to
5987 explicitly set. Bugfix on 0.2.3.12-alpha for most Unixoid systems;
5988 bugfix on 0.2.3.9-alpha for Windows.
5991 - A wide variety of new unit tests by Esteban Manchado Velázquez.
5992 - Shorten links in the tor-exit-notice file. Patch by Christian Kujau.
5993 - Update to the March 6 2012 Maxmind GeoLite Country database.
5996 Changes in version 0.2.3.12-alpha - 2012-02-13
5997 Tor 0.2.3.12-alpha lets fast exit relays scale better, allows clients
5998 to use bridges that run Tor 0.2.2.x, and resolves several big bugs
5999 when Tor is configured to use a pluggable transport like obfsproxy.
6002 - Fix builds when the path to sed, openssl, or sha1sum contains
6003 spaces, which is pretty common on Windows. Fixes bug 5065; bugfix
6005 - Set the SO_REUSEADDR socket option before we call bind() on outgoing
6006 connections. This change should allow busy exit relays to stop
6007 running out of available sockets as quickly. Fixes bug 4950;
6008 bugfix on 0.2.2.26-beta.
6009 - Allow 0.2.3.x clients to use 0.2.2.x bridges. Previously the client
6010 would ask the bridge for microdescriptors, which are only supported
6011 in 0.2.3.x, and then fail to bootstrap when it didn't get the
6012 answers it wanted. Fixes bug 4013; bugfix on 0.2.3.2-alpha.
6013 - Properly set up obfsproxy's environment when in managed mode. The
6014 Tor Browser Bundle needs LD_LIBRARY_PATH to be passed to obfsproxy,
6015 and when you run your Tor as a daemon, there's no HOME. Fixes bugs
6016 5076 and 5082; bugfix on 0.2.3.6-alpha.
6019 - Use the dead_strip option when building Tor on OS X. This reduces
6020 binary size by almost 19% when linking openssl and libevent
6021 statically, which we do for Tor Browser Bundle.
6022 - Fix broken URLs in the sample torrc file, and tell readers about
6023 the OutboundBindAddress, ExitPolicyRejectPrivate, and
6024 PublishServerDescriptor options. Addresses bug 4652.
6025 - Update to the February 7 2012 Maxmind GeoLite Country database.
6028 - Downgrade the "We're missing a certificate" message from notice
6029 to info: people kept mistaking it for a real problem, whereas it
6030 is seldom the problem even when we are failing to bootstrap. Fixes
6031 bug 5067; bugfix on 0.2.0.10-alpha.
6032 - Don't put "TOR_PT_EXTENDED_SERVER_PORT=127.0.0.1:4200" in a
6033 managed pluggable transport server proxy's environment.
6034 Previously, we would put it there, even though Tor doesn't
6035 implement an 'extended server port' yet, and even though Tor
6036 almost certainly isn't listening at that address. For now, we set
6037 it to an empty string to avoid crashing older obfsproxies. Bugfix
6039 - Log the heartbeat message every HeartbeatPeriod seconds, not every
6040 HeartbeatPeriod + 1 seconds. Fixes bug 4942; bugfix on
6041 0.2.3.1-alpha. Bug reported by Scott Bennett.
6042 - Calculate absolute paths correctly on Windows. Fixes bug 4973;
6043 bugfix on 0.2.3.11-alpha.
6044 - Update "ClientOnly" man page entry to explain that there isn't
6045 really any point to messing with it. Resolves ticket 5005.
6046 - Use the correct CVE number for CVE-2011-4576 in our comments and
6047 log messages. Found by "fermenthor". Resolves bug 5066; bugfix on
6050 o Code simplifications and refactoring:
6051 - Use the _WIN32 macro throughout our code to detect Windows.
6052 (Previously we had used the obsolete 'WIN32' and the idiosyncratic
6056 Changes in version 0.2.3.11-alpha - 2012-01-22
6057 Tor 0.2.3.11-alpha marks feature-freeze for the 0.2.3 tree. It deploys
6058 the last step of the plan to limit maximum circuit length, includes
6059 a wide variety of hidden service performance and correctness fixes,
6060 works around an OpenSSL security flaw if your distro is too stubborn
6061 to upgrade, and fixes a bunch of smaller issues.
6064 - Now that Tor 0.2.0.x is completely deprecated, enable the final
6065 part of "Proposal 110: Avoiding infinite length circuits" by
6066 refusing all circuit-extend requests that do not use a relay_early
6067 cell. This change helps Tor resist a class of denial-of-service
6068 attacks by limiting the maximum circuit length.
6069 - Adjust the number of introduction points that a hidden service
6070 will try to maintain based on how long its introduction points
6071 remain in use and how many introductions they handle. Fixes
6073 - Try to use system facilities for enumerating local interface
6074 addresses, before falling back to our old approach (which was
6075 binding a UDP socket, and calling getsockname() on it). That
6076 approach was scaring OS X users whose draconian firewall
6077 software warned about binding to UDP sockets, regardless of
6078 whether packets were sent. Now we try to use getifaddrs(),
6079 SIOCGIFCONF, or GetAdaptersAddresses(), depending on what the
6080 system supports. Resolves ticket 1827.
6082 o Major security workaround:
6083 - When building or running with any version of OpenSSL earlier
6084 than 0.9.8s or 1.0.0f, disable SSLv3 support. These OpenSSL
6085 versions have a bug (CVE-2011-4576) in which their block cipher
6086 padding includes uninitialized data, potentially leaking sensitive
6087 information to any peer with whom they make a SSLv3 connection. Tor
6088 does not use SSL v3 by default, but a hostile client or server
6089 could force an SSLv3 connection in order to gain information that
6090 they shouldn't have been able to get. The best solution here is to
6091 upgrade to OpenSSL 0.9.8s or 1.0.0f (or later). But when building
6092 or running with a non-upgraded OpenSSL, we disable SSLv3 entirely
6093 to make sure that the bug can't happen.
6096 - Fix the SOCKET_OK test that we use to tell when socket
6097 creation fails so that it works on Win64. Fixes part of bug 4533;
6098 bugfix on 0.2.2.29-beta. Bug found by wanoskarnet.
6099 - Correct our replacements for the timeradd() and timersub() functions
6100 on platforms that lack them (for example, Windows). The timersub()
6101 function is used when expiring circuits, while timeradd() is
6102 currently unused. Bug report and patch by Vektor. Fixes bug 4778;
6103 bugfix on 0.2.2.24-alpha and 0.2.3.1-alpha.
6104 - Do not use OpenSSL 1.0.0's counter mode: it has a critical bug
6105 that was fixed in OpenSSL 1.0.0a. We test for the counter mode
6106 bug at runtime, not compile time, because some distributions hack
6107 their OpenSSL to mis-report its version. Fixes bug 4779; bugfix
6108 on 0.2.3.9-alpha. Found by Pascal.
6110 o Minor features (controller):
6111 - Use absolute path names when reporting the torrc filename in the
6112 control protocol, so a controller can more easily find the torrc
6113 file. Resolves bug 1101.
6114 - Extend the control protocol to report flags that control a circuit's
6115 path selection in CIRC events and in replies to 'GETINFO
6116 circuit-status'. Implements part of ticket 2411.
6117 - Extend the control protocol to report the hidden service address
6118 and current state of a hidden-service-related circuit in CIRC
6119 events and in replies to 'GETINFO circuit-status'. Implements part
6121 - When reporting the path to the cookie file to the controller,
6122 give an absolute path. Resolves ticket 4881.
6123 - Allow controllers to request an event notification whenever a
6124 circuit is cannibalized or its purpose is changed. Implements
6125 part of ticket 3457.
6126 - Include the creation time of a circuit in CIRC and CIRC2
6127 control-port events and the list produced by the 'GETINFO
6128 circuit-status' control-port command.
6130 o Minor features (directory authorities):
6131 - Directory authorities now reject versions of Tor older than
6132 0.2.1.30, and Tor versions between 0.2.2.1-alpha and 0.2.2.20-alpha
6133 inclusive. These versions accounted for only a small fraction of
6134 the Tor network, and have numerous known security issues. Resolves
6136 - Authority operators can now vote for all relays in a given
6137 set of countries to be BadDir/BadExit/Invalid/Rejected.
6138 - Provide two consensus parameters (FastFlagMinThreshold and
6139 FastFlagMaxThreshold) to control the range of allowable bandwidths
6140 for the Fast directory flag. These allow authorities to run
6141 experiments on appropriate requirements for being a "Fast" node.
6142 The AuthDirFastGuarantee config value still applies. Implements
6144 - Document the GiveGuardFlagTo_CVE_2011_2768_VulnerableRelays
6145 directory authority option (introduced in Tor 0.2.2.34).
6147 o Minor features (other):
6148 - Don't disable the DirPort when we cannot exceed our AccountingMax
6149 limit during this interval because the effective bandwidthrate is
6150 low enough. This is useful in a situation where AccountMax is only
6151 used as an additional safeguard or to provide statistics.
6152 - Prepend an informative header to generated dynamic_dh_params files.
6153 - If EntryNodes are given, but UseEntryGuards is set to 0, warn that
6154 EntryNodes will have no effect. Resolves issue 2571.
6155 - Log more useful messages when we fail to disable debugger
6157 - Log which authority we're missing votes from when we go to fetch
6158 them from the other auths.
6159 - Log (at debug level) whenever a circuit's purpose is changed.
6160 - Add missing documentation for the MaxClientCircuitsPending,
6161 UseMicrodescriptors, UserspaceIOCPBuffers, and
6162 _UseFilteringSSLBufferevents options, all introduced during
6164 - Update to the January 3 2012 Maxmind GeoLite Country database.
6166 o Minor bugfixes (hidden services):
6167 - Don't close hidden service client circuits which have almost
6168 finished connecting to their destination when they reach
6169 the normal circuit-build timeout. Previously, we would close
6170 introduction circuits which are waiting for an acknowledgement
6171 from the introduction point, and rendezvous circuits which have
6172 been specified in an INTRODUCE1 cell sent to a hidden service,
6173 after the normal CBT. Now, we mark them as 'timed out', and launch
6174 another rendezvous attempt in parallel. This behavior change can
6175 be disabled using the new CloseHSClientCircuitsImmediatelyOnTimeout
6176 option. Fixes part of bug 1297; bugfix on 0.2.2.2-alpha.
6177 - Don't close hidden-service-side rendezvous circuits when they
6178 reach the normal circuit-build timeout. This behavior change can
6179 be disabled using the new
6180 CloseHSServiceRendCircuitsImmediatelyOnTimeout option. Fixes the
6181 remaining part of bug 1297; bugfix on 0.2.2.2-alpha.
6182 - Make sure we never mark the wrong rendezvous circuit as having
6183 had its introduction cell acknowleged by the introduction-point
6184 relay. Previously, when we received an INTRODUCE_ACK cell on a
6185 client-side hidden-service introduction circuit, we might have
6186 marked a rendezvous circuit other than the one we specified in
6187 the INTRODUCE1 cell as INTRO_ACKED, which would have produced
6188 a warning message and interfered with the hidden service
6189 connection-establishment process. Fixes bug 4759; bugfix on
6190 0.2.3.3-alpha, when we added the stream-isolation feature which
6191 might cause Tor to open multiple rendezvous circuits for the same
6193 - Don't trigger an assertion failure when we mark a new client-side
6194 hidden-service introduction circuit for close during the process
6195 of creating it. Fixes bug 4796; bugfix on 0.2.3.6-alpha. Reported
6198 o Minor bugfixes (log messages):
6199 - Correctly spell "connect" in a log message on failure to create a
6200 controlsocket. Fixes bug 4803; bugfix on 0.2.2.26-beta and
6202 - Fix a typo in a log message in rend_service_rendezvous_has_opened().
6203 Fixes bug 4856; bugfix on Tor 0.0.6.
6204 - Fix the log message describing how we work around discovering
6205 that our version is the ill-fated OpenSSL 0.9.8l. Fixes bug
6206 4837; bugfix on 0.2.2.9-alpha.
6207 - When logging about a disallowed .exit name, do not also call it
6208 an "invalid onion address". Fixes bug 3325; bugfix on 0.2.2.9-alpha.
6210 o Minor bugfixes (build fixes):
6211 - During configure, detect when we're building with clang version
6212 3.0 or lower and disable the -Wnormalized=id and -Woverride-init
6213 CFLAGS. clang doesn't support them yet.
6214 - During configure, search for library containing cos function as
6215 libm lives in libcore on some platforms (BeOS/Haiku). Linking
6216 against libm was hard-coded before. Fixes the first part of bug
6217 4727; bugfix on 0.2.2.2-alpha. Patch and analysis by Martin Hebnes
6219 - Detect attempts to build Tor on (as yet hypothetical) versions
6220 of Windows where sizeof(intptr_t) != sizeof(SOCKET). Partial
6221 fix for bug 4533. Bugfix on 0.2.2.28-beta.
6222 - Preprocessor directives should not be put inside the arguments
6223 of a macro. This would break compilation with GCC releases prior
6224 to version 3.3. We would never recommend such an old GCC version,
6225 but it is apparently required for binary compatibility on some
6226 platforms (namely, certain builds of Haiku). Fixes the other part
6227 of bug 4727; bugfix on 0.2.3.3-alpha. Patch and analysis by Martin
6230 o Minor bugfixes (other):
6231 - Older Linux kernels erroneously respond to strange nmap behavior
6232 by having accept() return successfully with a zero-length
6233 socket. When this happens, just close the connection. Previously,
6234 we would try harder to learn the remote address: but there was
6235 no such remote address to learn, and our method for trying to
6236 learn it was incorrect. Fixes bugs 1240, 4745, and 4747. Bugfix
6237 on 0.1.0.3-rc. Reported and diagnosed by "r1eo".
6238 - Fix null-pointer access that could occur if TLS allocation failed.
6239 Fixes bug 4531; bugfix on 0.2.0.20-rc. Found by "troll_un". This was
6240 erroneously listed as fixed in 0.2.3.9-alpha, but the fix had
6241 accidentally been reverted.
6242 - Fix our implementation of crypto_random_hostname() so it can't
6243 overflow on ridiculously large inputs. (No Tor version has ever
6244 provided this kind of bad inputs, but let's be correct in depth.)
6245 Fixes bug 4413; bugfix on 0.2.2.9-alpha. Fix by Stephen Palmateer.
6246 - Find more places in the code that should have been testing for
6247 invalid sockets using the SOCKET_OK macro. Required for a fix
6248 for bug 4533. Bugfix on 0.2.2.28-beta.
6249 - Fix an assertion failure when, while running with bufferevents, a
6250 connection finishes connecting after it is marked for close, but
6251 before it is closed. Fixes bug 4697; bugfix on 0.2.3.1-alpha.
6252 - test_util_spawn_background_ok() hardcoded the expected value
6253 for ENOENT to 2. This isn't portable as error numbers are
6254 platform specific, and particularly the hurd has ENOENT at
6255 0x40000002. Construct expected string at runtime, using the correct
6256 value for ENOENT. Fixes bug 4733; bugfix on 0.2.3.1-alpha.
6257 - Reject attempts to disable DisableDebuggerAttachment while Tor is
6258 running. Fixes bug 4650; bugfix on 0.2.3.9-alpha.
6259 - Use an appropriate-width type for sockets in tor-fw-helper on
6260 win64. Fixes bug 1983 at last. Bugfix on 0.2.3.9-alpha.
6263 - When sending or relaying a RELAY_EARLY cell, we used to convert
6264 it to a RELAY cell if the connection was using the v1 link
6265 protocol. This was a workaround for older versions of Tor, which
6266 didn't handle RELAY_EARLY cells properly. Now that all supported
6267 versions can handle RELAY_EARLY cells, and now that we're enforcing
6268 the "no RELAY_EXTEND commands except in RELAY_EARLY cells" rule,
6269 remove this workaround. Addresses bug 4786.
6271 o Code simplifications and refactoring:
6272 - Use OpenSSL's built-in SSL_state_string_long() instead of our
6273 own homebrewed ssl_state_to_string() replacement. Patch from
6274 Emile Snyder. Fixes bug 4653.
6275 - Use macros to indicate OpenSSL versions, so we don't need to worry
6276 about accidental hexadecimal bit shifts.
6277 - Remove some workaround code for OpenSSL 0.9.6 (which is no longer
6279 - Convert more instances of tor_snprintf+tor_strdup into tor_asprintf.
6280 - Use the smartlist_add_asprintf() alias more consistently.
6281 - Use a TOR_INVALID_SOCKET macro when initializing a socket to an
6282 invalid value, rather than just -1.
6283 - Rename a handful of old identifiers, mostly related to crypto
6284 structures and crypto functions. By convention, our "create an
6285 object" functions are called "type_new()", our "free an object"
6286 functions are called "type_free()", and our types indicate that
6287 they are types only with a final "_t". But a handful of older
6288 types and functions broke these rules, with function names like
6289 "type_create" or "subsystem_op_type", or with type names like
6293 Changes in version 0.2.3.10-alpha - 2011-12-16
6294 Tor 0.2.3.10-alpha fixes a critical heap-overflow security issue in
6295 Tor's buffers code. Absolutely everybody should upgrade.
6297 The bug relied on an incorrect calculation when making data continuous
6298 in one of our IO buffers, if the first chunk of the buffer was
6299 misaligned by just the wrong amount. The miscalculation would allow an
6300 attacker to overflow a piece of heap-allocated memory. To mount this
6301 attack, the attacker would need to either open a SOCKS connection to
6302 Tor's SocksPort (usually restricted to localhost), or target a Tor
6303 instance configured to make its connections through a SOCKS proxy
6304 (which Tor does not do by default).
6306 Good security practice requires that all heap-overflow bugs should be
6307 presumed to be exploitable until proven otherwise, so we are treating
6308 this as a potential code execution attack. Please upgrade immediately!
6309 This bug does not affect bufferevents-based builds of Tor. Special
6310 thanks to "Vektor" for reporting this issue to us!
6312 This release also contains a few minor bugfixes for issues discovered
6316 - Fix a heap overflow bug that could occur when trying to pull
6317 data into the first chunk of a buffer, when that chunk had
6318 already had some data drained from it. Fixes CVE-2011-2778;
6319 bugfix on 0.2.0.16-alpha. Reported by "Vektor".
6322 - If we can't attach streams to a rendezvous circuit when we
6323 finish connecting to a hidden service, clear the rendezvous
6324 circuit's stream-isolation state and try to attach streams
6325 again. Previously, we cleared rendezvous circuits' isolation
6326 state either too early (if they were freshly built) or not at all
6327 (if they had been built earlier and were cannibalized). Bugfix on
6328 0.2.3.3-alpha; fixes bug 4655.
6329 - Fix compilation of the libnatpmp helper on non-Windows. Bugfix on
6330 0.2.3.9-alpha; fixes bug 4691. Reported by Anthony G. Basile.
6331 - Fix an assertion failure when a relay with accounting enabled
6332 starts up while dormant. Fixes bug 4702; bugfix on 0.2.3.9-alpha.
6335 - Update to the December 6 2011 Maxmind GeoLite Country database.
6338 Changes in version 0.2.2.35 - 2011-12-16
6339 Tor 0.2.2.35 fixes a critical heap-overflow security issue in Tor's
6340 buffers code. Absolutely everybody should upgrade.
6342 The bug relied on an incorrect calculation when making data continuous
6343 in one of our IO buffers, if the first chunk of the buffer was
6344 misaligned by just the wrong amount. The miscalculation would allow an
6345 attacker to overflow a piece of heap-allocated memory. To mount this
6346 attack, the attacker would need to either open a SOCKS connection to
6347 Tor's SocksPort (usually restricted to localhost), or target a Tor
6348 instance configured to make its connections through a SOCKS proxy
6349 (which Tor does not do by default).
6351 Good security practice requires that all heap-overflow bugs should be
6352 presumed to be exploitable until proven otherwise, so we are treating
6353 this as a potential code execution attack. Please upgrade immediately!
6354 This bug does not affect bufferevents-based builds of Tor. Special
6355 thanks to "Vektor" for reporting this issue to us!
6357 Tor 0.2.2.35 also fixes several bugs in previous versions, including
6358 crash bugs for unusual configurations, and a long-term bug that
6359 would prevent Tor from starting on Windows machines with draconian
6362 With this release, we remind everyone that 0.2.0.x has reached its
6363 formal end-of-life. Those Tor versions have many known flaws, and
6364 nobody should be using them. You should upgrade -- ideally to the
6365 0.2.2.x series. If you're using a Linux or BSD and its packages are
6366 obsolete, stop using those packages and upgrade anyway.
6368 The Tor 0.2.1.x series is also approaching its end-of-life: it will no
6369 longer receive support after some time in early 2012.
6372 - Fix a heap overflow bug that could occur when trying to pull
6373 data into the first chunk of a buffer, when that chunk had
6374 already had some data drained from it. Fixes CVE-2011-2778;
6375 bugfix on 0.2.0.16-alpha. Reported by "Vektor".
6376 - Initialize Libevent with the EVENT_BASE_FLAG_NOLOCK flag enabled, so
6377 that it doesn't attempt to allocate a socketpair. This could cause
6378 some problems on Windows systems with overzealous firewalls. Fix for
6379 bug 4457; workaround for Libevent versions 2.0.1-alpha through
6381 - If we mark an OR connection for close based on a cell we process,
6382 don't process any further cells on it. We already avoid further
6383 reads on marked-for-close connections, but now we also discard the
6384 cells we'd already read. Fixes bug 4299; bugfix on 0.2.0.10-alpha,
6385 which was the first version where we might mark a connection for
6386 close based on processing a cell on it.
6387 - Correctly sanity-check that we don't underflow on a memory
6388 allocation (and then assert) for hidden service introduction
6389 point decryption. Bug discovered by Dan Rosenberg. Fixes bug 4410;
6390 bugfix on 0.2.1.5-alpha.
6391 - Fix a memory leak when we check whether a hidden service
6392 descriptor has any usable introduction points left. Fixes bug
6393 4424. Bugfix on 0.2.2.25-alpha.
6394 - Don't crash when we're running as a relay and don't have a GeoIP
6395 file. Bugfix on 0.2.2.34; fixes bug 4340. This backports a fix
6396 we've had in the 0.2.3.x branch already.
6397 - When running as a client, do not print a misleading (and plain
6398 wrong) log message that we're collecting "directory request"
6399 statistics: clients don't collect statistics. Also don't create a
6400 useless (because empty) stats file in the stats/ directory. Fixes
6401 bug 4353; bugfix on 0.2.2.34.
6404 - Detect failure to initialize Libevent. This fix provides better
6405 detection for future instances of bug 4457.
6406 - Avoid frequent calls to the fairly expensive cull_wedged_cpuworkers
6407 function. This was eating up hideously large amounts of time on some
6408 busy servers. Fixes bug 4518; bugfix on 0.0.9.8.
6409 - Resolve an integer overflow bug in smartlist_ensure_capacity().
6410 Fixes bug 4230; bugfix on Tor 0.1.0.1-rc. Based on a patch by
6412 - Don't warn about unused log_mutex in log.c when building with
6413 --disable-threads using a recent GCC. Fixes bug 4437; bugfix on
6414 0.1.0.6-rc which introduced --disable-threads.
6415 - When configuring, starting, or stopping an NT service, stop
6416 immediately after the service configuration attempt has succeeded
6417 or failed. Fixes bug 3963; bugfix on 0.2.0.7-alpha.
6418 - When sending a NETINFO cell, include the original address
6419 received for the other side, not its canonical address. Found
6420 by "troll_un"; fixes bug 4349; bugfix on 0.2.0.10-alpha.
6421 - Fix a typo in a hibernation-related log message. Fixes bug 4331;
6422 bugfix on 0.2.2.23-alpha; found by "tmpname0901".
6423 - Fix a memory leak in launch_direct_bridge_descriptor_fetch() that
6424 occurred when a client tried to fetch a descriptor for a bridge
6425 in ExcludeNodes. Fixes bug 4383; bugfix on 0.2.2.25-alpha.
6426 - Backport fixes for a pair of compilation warnings on Windows.
6427 Fixes bug 4521; bugfix on 0.2.2.28-beta and on 0.2.2.29-beta.
6428 - If we had ever tried to call tor_addr_to_str on an address of
6429 unknown type, we would have done a strdup on an uninitialized
6430 buffer. Now we won't. Fixes bug 4529; bugfix on 0.2.1.3-alpha.
6431 Reported by "troll_un".
6432 - Correctly detect and handle transient lookup failures from
6433 tor_addr_lookup. Fixes bug 4530; bugfix on 0.2.1.5-alpha.
6434 Reported by "troll_un".
6435 - Fix null-pointer access that could occur if TLS allocation failed.
6436 Fixes bug 4531; bugfix on 0.2.0.20-rc. Found by "troll_un".
6437 - Use tor_socket_t type for listener argument to accept(). Fixes bug
6438 4535; bugfix on 0.2.2.28-beta. Found by "troll_un".
6441 - Add two new config options for directory authorities:
6442 AuthDirFastGuarantee sets a bandwidth threshold for guaranteeing the
6443 Fast flag, and AuthDirGuardBWGuarantee sets a bandwidth threshold
6444 that is always sufficient to satisfy the bandwidth requirement for
6445 the Guard flag. Now it will be easier for researchers to simulate
6446 Tor networks with different values. Resolves ticket 4484.
6447 - When Tor ignores a hidden service specified in its configuration,
6448 include the hidden service's directory in the warning message.
6449 Previously, we would only tell the user that some hidden service
6450 was ignored. Bugfix on 0.0.6; fixes bug 4426.
6451 - Update to the December 6 2011 Maxmind GeoLite Country database.
6453 o Packaging changes:
6454 - Make it easier to automate expert package builds on Windows,
6455 by removing an absolute path from makensis.exe command.
6458 Changes in version 0.2.1.32 - 2011-12-16
6459 Tor 0.2.1.32 backports important security and privacy fixes for
6460 oldstable. This release is intended only for package maintainers and
6461 others who cannot use the 0.2.2 stable series. All others should be
6462 using Tor 0.2.2.x or newer.
6464 The Tor 0.2.1.x series will reach formal end-of-life some time in
6465 early 2012; we will stop releasing patches for it then.
6467 o Major bugfixes (also included in 0.2.2.x):
6468 - Correctly sanity-check that we don't underflow on a memory
6469 allocation (and then assert) for hidden service introduction
6470 point decryption. Bug discovered by Dan Rosenberg. Fixes bug 4410;
6471 bugfix on 0.2.1.5-alpha.
6472 - Fix a heap overflow bug that could occur when trying to pull
6473 data into the first chunk of a buffer, when that chunk had
6474 already had some data drained from it. Fixes CVE-2011-2778;
6475 bugfix on 0.2.0.16-alpha. Reported by "Vektor".
6478 - Update to the December 6 2011 Maxmind GeoLite Country database.
6481 Changes in version 0.2.3.9-alpha - 2011-12-08
6482 Tor 0.2.3.9-alpha introduces initial IPv6 support for bridges, adds
6483 a "DisableNetwork" security feature that bundles can use to avoid
6484 touching the network until bridges are configured, moves forward on
6485 the pluggable transport design, fixes a flaw in the hidden service
6486 design that unnecessarily prevented clients with wrong clocks from
6487 reaching hidden services, and fixes a wide variety of other issues.
6490 - Clients can now connect to private bridges over IPv6. Bridges
6491 still need at least one IPv4 address in order to connect to
6492 other relays. Note that we don't yet handle the case where the
6493 user has two bridge lines for the same bridge (one IPv4, one
6494 IPv6). Implements parts of proposal 186.
6495 - New "DisableNetwork" config option to prevent Tor from launching any
6496 connections or accepting any connections except on a control port.
6497 Bundles and controllers can set this option before letting Tor talk
6498 to the rest of the network, for example to prevent any connections
6499 to a non-bridge address. Packages like Orbot can also use this
6500 option to instruct Tor to save power when the network is off.
6501 - Clients and bridges can now be configured to use a separate
6502 "transport" proxy. This approach makes the censorship arms race
6503 easier by allowing bridges to use protocol obfuscation plugins. It
6504 implements the "managed proxy" part of proposal 180 (ticket 3472).
6505 - When using OpenSSL 1.0.0 or later, use OpenSSL's counter mode
6506 implementation. It makes AES_CTR about 7% faster than our old one
6507 (which was about 10% faster than the one OpenSSL used to provide).
6508 Resolves ticket 4526.
6509 - Add a "tor2web mode" for clients that want to connect to hidden
6510 services non-anonymously (and possibly more quickly). As a safety
6511 measure to try to keep users from turning this on without knowing
6512 what they are doing, tor2web mode must be explicitly enabled at
6513 compile time, and a copy of Tor compiled to run in tor2web mode
6514 cannot be used as a normal Tor client. Implements feature 2553.
6515 - Add experimental support for running on Windows with IOCP and no
6516 kernel-space socket buffers. This feature is controlled by a new
6517 "UserspaceIOCPBuffers" config option (off by default), which has
6518 no effect unless Tor has been built with support for bufferevents,
6519 is running on Windows, and has enabled IOCP. This may, in the long
6520 run, help solve or mitigate bug 98.
6521 - Use a more secure consensus parameter voting algorithm. Now at
6522 least three directory authorities or a majority of them must
6523 vote on a given parameter before it will be included in the
6524 consensus. Implements proposal 178.
6527 - Hidden services now ignore the timestamps on INTRODUCE2 cells.
6528 They used to check that the timestamp was within 30 minutes
6529 of their system clock, so they could cap the size of their
6530 replay-detection cache, but that approach unnecessarily refused
6531 service to clients with wrong clocks. Bugfix on 0.2.1.6-alpha, when
6532 the v3 intro-point protocol (the first one which sent a timestamp
6533 field in the INTRODUCE2 cell) was introduced; fixes bug 3460.
6534 - Only use the EVP interface when AES acceleration is enabled,
6535 to avoid a 5-7% performance regression. Resolves issue 4525;
6536 bugfix on 0.2.3.8-alpha.
6538 o Privacy/anonymity features (bridge detection):
6539 - Make bridge SSL certificates a bit more stealthy by using random
6540 serial numbers, in the same fashion as OpenSSL when generating
6541 self-signed certificates. Implements ticket 4584.
6542 - Introduce a new config option "DynamicDHGroups", enabled by
6543 default, which provides each bridge with a unique prime DH modulus
6544 to be used during SSL handshakes. This option attempts to help
6545 against censors who might use the Apache DH modulus as a static
6546 identifier for bridges. Addresses ticket 4548.
6548 o Minor features (new/different config options):
6549 - New configuration option "DisableDebuggerAttachment" (on by default)
6550 to prevent basic debugging attachment attempts by other processes.
6551 Supports Mac OS X and Gnu/Linux. Resolves ticket 3313.
6552 - Allow MapAddress directives to specify matches against super-domains,
6553 as in "MapAddress *.torproject.org *.torproject.org.torserver.exit".
6554 Implements issue 933.
6555 - Slightly change behavior of "list" options (that is, config
6556 options that can appear more than once) when they appear both in
6557 torrc and on the command line. Previously, the command-line options
6558 would be appended to the ones from torrc. Now, the command-line
6559 options override the torrc options entirely. This new behavior
6560 allows the user to override list options (like exit policies and
6561 ports to listen on) from the command line, rather than simply
6562 appending to the list.
6563 - You can get the old (appending) command-line behavior for "list"
6564 options by prefixing the option name with a "+".
6565 - You can remove all the values for a "list" option from the command
6566 line without adding any new ones by prefixing the option name
6568 - Add experimental support for a "defaults" torrc file to be parsed
6569 before the regular torrc. Torrc options override the defaults file's
6570 options in the same way that the command line overrides the torrc.
6571 The SAVECONF controller command saves only those options which
6572 differ between the current configuration and the defaults file. HUP
6573 reloads both files. (Note: This is an experimental feature; its
6574 behavior will probably be refined in future 0.2.3.x-alpha versions
6575 to better meet packagers' needs.) Implements task 4552.
6578 - Try to make the introductory warning message that Tor prints on
6579 startup more useful for actually finding help and information.
6580 Resolves ticket 2474.
6581 - Running "make version" now displays the version of Tor that
6582 we're about to build. Idea from katmagic; resolves issue 4400.
6583 - Expire old or over-used hidden service introduction points.
6584 Required by fix for bug 3460.
6585 - Move the replay-detection cache for the RSA-encrypted parts of
6586 INTRODUCE2 cells to the introduction point data structures.
6587 Previously, we would use one replay-detection cache per hidden
6588 service. Required by fix for bug 3460.
6589 - Reduce the lifetime of elements of hidden services' Diffie-Hellman
6590 public key replay-detection cache from 60 minutes to 5 minutes. This
6591 replay-detection cache is now used only to detect multiple
6592 INTRODUCE2 cells specifying the same rendezvous point, so we can
6593 avoid launching multiple simultaneous attempts to connect to it.
6595 o Minor bugfixes (on Tor 0.2.2.x and earlier):
6596 - Resolve an integer overflow bug in smartlist_ensure_capacity().
6597 Fixes bug 4230; bugfix on Tor 0.1.0.1-rc. Based on a patch by
6599 - Fix a minor formatting issue in one of tor-gencert's error messages.
6601 - Prevent a false positive from the check-spaces script, by disabling
6602 the "whitespace between function name and (" check for functions
6604 - Fix a log message suggesting that people contact a non-existent
6605 email address. Fixes bug 3448.
6606 - Fix null-pointer access that could occur if TLS allocation failed.
6607 Fixes bug 4531; bugfix on 0.2.0.20-rc. Found by "troll_un".
6608 - Report a real bootstrap problem to the controller on router
6609 identity mismatch. Previously we just said "foo", which probably
6610 made a lot of sense at the time. Fixes bug 4169; bugfix on
6612 - If we had ever tried to call tor_addr_to_str() on an address of
6613 unknown type, we would have done a strdup() on an uninitialized
6614 buffer. Now we won't. Fixes bug 4529; bugfix on 0.2.1.3-alpha.
6615 Reported by "troll_un".
6616 - Correctly detect and handle transient lookup failures from
6617 tor_addr_lookup(). Fixes bug 4530; bugfix on 0.2.1.5-alpha.
6618 Reported by "troll_un".
6619 - Use tor_socket_t type for listener argument to accept(). Fixes bug
6620 4535; bugfix on 0.2.2.28-beta. Found by "troll_un".
6621 - Initialize conn->addr to a valid state in spawn_cpuworker(). Fixes
6622 bug 4532; found by "troll_un".
6624 o Minor bugfixes (on Tor 0.2.3.x):
6625 - Fix a compile warning in tor_inet_pton(). Bugfix on 0.2.3.8-alpha;
6627 - Don't send two ESTABLISH_RENDEZVOUS cells when opening a new
6628 circuit for use as a hidden service client's rendezvous point.
6629 Fixes bugs 4641 and 4171; bugfix on 0.2.3.3-alpha. Diagnosed
6630 with help from wanoskarnet.
6631 - Restore behavior of overriding SocksPort, ORPort, and similar
6632 options from the command line. Bugfix on 0.2.3.3-alpha.
6635 - Properly handle the case where the build-tree is not the same
6636 as the source tree when generating src/common/common_sha1.i,
6637 src/or/micro-revision.i, and src/or/or_sha1.i. Fixes bug 3953;
6638 bugfix on 0.2.0.1-alpha.
6640 o Code simplifications, cleanups, and refactorings:
6641 - Remove the pure attribute from all functions that used it
6642 previously. In many cases we assigned it incorrectly, because the
6643 functions might assert or call impure functions, and we don't have
6644 evidence that keeping the pure attribute is worthwhile. Implements
6645 changes suggested in ticket 4421.
6646 - Remove some dead code spotted by coverity. Fixes cid 432.
6647 Bugfix on 0.2.3.1-alpha, closes bug 4637.
6650 Changes in version 0.2.3.8-alpha - 2011-11-22
6651 Tor 0.2.3.8-alpha fixes some crash and assert bugs, including a
6652 socketpair-related bug that has been bothering Windows users. It adds
6653 support to serve microdescriptors to controllers, so Vidalia's network
6654 map can resume listing relays (once Vidalia implements its side),
6655 and adds better support for hardware AES acceleration. Finally, it
6656 starts the process of adjusting the bandwidth cutoff for getting the
6657 "Fast" flag from 20KB to (currently) 32KB -- preliminary results show
6658 that tiny relays harm performance more than they help network capacity.
6661 - Initialize Libevent with the EVENT_BASE_FLAG_NOLOCK flag enabled, so
6662 that it doesn't attempt to allocate a socketpair. This could cause
6663 some problems on Windows systems with overzealous firewalls. Fix for
6664 bug 4457; workaround for Libevent versions 2.0.1-alpha through
6666 - Correctly sanity-check that we don't underflow on a memory
6667 allocation (and then assert) for hidden service introduction
6668 point decryption. Bug discovered by Dan Rosenberg. Fixes bug 4410;
6669 bugfix on 0.2.1.5-alpha.
6670 - Remove the artificially low cutoff of 20KB to guarantee the Fast
6671 flag. In the past few years the average relay speed has picked
6672 up, and while the "top 7/8 of the network get the Fast flag" and
6673 "all relays with 20KB or more of capacity get the Fast flag" rules
6674 used to have the same result, now the top 7/8 of the network has
6675 a capacity more like 32KB. Bugfix on 0.2.1.14-rc. Fixes bug 4489.
6676 - Fix a rare assertion failure when checking whether a v0 hidden
6677 service descriptor has any usable introduction points left, and
6678 we don't have enough information to build a circuit to the first
6679 intro point named in the descriptor. The HS client code in
6680 0.2.3.x no longer uses v0 HS descriptors, but this assertion can
6681 trigger on (and crash) v0 HS authorities. Fixes bug 4411.
6682 Bugfix on 0.2.3.1-alpha; diagnosed by frosty_un.
6683 - Make bridge authorities not crash when they are asked for their own
6684 descriptor. Bugfix on 0.2.3.7-alpha, reported by Lucky Green.
6685 - When running as a client, do not print a misleading (and plain
6686 wrong) log message that we're collecting "directory request"
6687 statistics: clients don't collect statistics. Also don't create a
6688 useless (because empty) stats file in the stats/ directory. Fixes
6689 bug 4353; bugfix on 0.2.2.34 and 0.2.3.7-alpha.
6692 - Allow Tor controllers like Vidalia to obtain the microdescriptor
6693 for a relay by identity digest or nickname. Previously,
6694 microdescriptors were only available by their own digests, so a
6695 controller would have to ask for and parse the whole microdescriptor
6696 consensus in order to look up a single relay's microdesc. Fixes
6697 bug 3832; bugfix on 0.2.3.1-alpha.
6698 - Use OpenSSL's EVP interface for AES encryption, so that all AES
6699 operations can use hardware acceleration (if present). Resolves
6702 o Minor bugfixes (on 0.2.2.x and earlier):
6703 - Detect failure to initialize Libevent. This fix provides better
6704 detection for future instances of bug 4457.
6705 - Avoid frequent calls to the fairly expensive cull_wedged_cpuworkers
6706 function. This was eating up hideously large amounts of time on some
6707 busy servers. Fixes bug 4518; bugfix on 0.0.9.8.
6708 - Don't warn about unused log_mutex in log.c when building with
6709 --disable-threads using a recent GCC. Fixes bug 4437; bugfix on
6710 0.1.0.6-rc which introduced --disable-threads.
6711 - Allow manual 'authenticate' commands to the controller interface
6712 from netcat (nc) as well as telnet. We were rejecting them because
6713 they didn't come with the expected whitespace at the end of the
6714 command. Bugfix on 0.1.1.1-alpha; fixes bug 2893.
6715 - Fix some (not actually triggerable) buffer size checks in usage of
6716 tor_inet_ntop. Fixes bug 4434; bugfix on Tor 0.2.0.1-alpha. Patch
6718 - Fix parsing of some corner-cases with tor_inet_pton(). Fixes
6719 bug 4515; bugfix on 0.2.0.1-alpha; fix by Anders Sundman.
6720 - When configuring, starting, or stopping an NT service, stop
6721 immediately after the service configuration attempt has succeeded
6722 or failed. Fixes bug 3963; bugfix on 0.2.0.7-alpha.
6723 - When sending a NETINFO cell, include the original address
6724 received for the other side, not its canonical address. Found
6725 by "troll_un"; fixes bug 4349; bugfix on 0.2.0.10-alpha.
6726 - Rename the bench_{aes,dmap} functions to test_*, so that tinytest
6727 can pick them up when the tests aren't disabled. Bugfix on
6728 0.2.2.4-alpha which introduced tinytest.
6729 - Fix a memory leak when we check whether a hidden service
6730 descriptor has any usable introduction points left. Fixes bug
6731 4424. Bugfix on 0.2.2.25-alpha.
6732 - Fix a memory leak in launch_direct_bridge_descriptor_fetch() that
6733 occurred when a client tried to fetch a descriptor for a bridge
6734 in ExcludeNodes. Fixes bug 4383; bugfix on 0.2.2.25-alpha.
6736 o Minor bugfixes (on 0.2.3.x):
6737 - Make util unit tests build correctly with MSVC. Bugfix on
6738 0.2.3.3-alpha. Patch by Gisle Vanem.
6739 - Successfully detect AUTH_CHALLENGE cells with no recognized
6740 authentication type listed. Fixes bug 4367; bugfix on 0.2.3.6-alpha.
6742 - If a relay receives an AUTH_CHALLENGE cell it can't answer,
6743 it should still send a NETINFO cell to allow the connection to
6744 become open. Fixes bug 4368; fix on 0.2.3.6-alpha; bug found by
6746 - Log less loudly when we get an invalid authentication certificate
6747 from a source other than a directory authority: it's not unusual
6748 to see invalid certs because of clock skew. Fixes bug 4370; bugfix
6750 - Tolerate servers with more clock skew in their authentication
6751 certificates than previously. Fixes bug 4371; bugfix on
6753 - Fix a couple of compile warnings on Windows. Fixes bug 4469; bugfix
6754 on 0.2.3.4-alpha and 0.2.3.6-alpha.
6757 - Add two new config options for directory authorities:
6758 AuthDirFastGuarantee sets a bandwidth threshold for guaranteeing the
6759 Fast flag, and AuthDirGuardBWGuarantee sets a bandwidth threshold
6760 that is always sufficient to satisfy the bandwidth requirement for
6761 the Guard flag. Now it will be easier for researchers to simulate
6762 Tor networks with different values. Resolves ticket 4484.
6763 - When Tor ignores a hidden service specified in its configuration,
6764 include the hidden service's directory in the warning message.
6765 Previously, we would only tell the user that some hidden service
6766 was ignored. Bugfix on 0.0.6; fixes bug 4426.
6767 - When we fail to initialize Libevent, retry with IOCP disabled so we
6768 don't need to turn on multi-threading support in Libevent, which in
6769 turn requires a working socketpair(). This is a workaround for bug
6770 4457, which affects Libevent versions from 2.0.1-alpha through
6772 - Detect when we try to build on a platform that doesn't define
6773 AF_UNSPEC to 0. We don't work there, so refuse to compile.
6774 - Update to the November 1 2011 Maxmind GeoLite Country database.
6776 o Packaging changes:
6777 - Make it easier to automate expert package builds on Windows,
6778 by removing an absolute path from makensis.exe command.
6780 o Code simplifications and refactoring:
6781 - Remove some redundant #include directives throughout the code.
6782 Patch from Andrea Gelmini.
6783 - Unconditionally use OpenSSL's AES implementation instead of our
6784 old built-in one. OpenSSL's AES has been better for a while, and
6785 relatively few servers should still be on any version of OpenSSL
6786 that doesn't have good optimized assembly AES.
6787 - Use the name "CERTS" consistently to refer to the new cell type;
6788 we were calling it CERT in some places and CERTS in others.
6791 - Numerous new unit tests for functions in util.c and address.c by
6793 - The long-disabled benchmark tests are now split into their own
6794 ./src/test/bench binary.
6795 - The benchmark tests can now use more accurate timers than
6796 gettimeofday() when such timers are available.
6799 Changes in version 0.2.3.7-alpha - 2011-10-30
6800 Tor 0.2.3.7-alpha fixes a crash bug in 0.2.3.6-alpha introduced by
6801 the new v3 handshake. It also resolves yet another bridge address
6805 - If we mark an OR connection for close based on a cell we process,
6806 don't process any further cells on it. We already avoid further
6807 reads on marked-for-close connections, but now we also discard the
6808 cells we'd already read. Fixes bug 4299; bugfix on 0.2.0.10-alpha,
6809 which was the first version where we might mark a connection for
6810 close based on processing a cell on it.
6811 - Fix a double-free bug that would occur when we received an invalid
6812 certificate in a CERT cell in the new v3 handshake. Fixes bug 4343;
6813 bugfix on 0.2.3.6-alpha.
6814 - Bridges no longer include their address in NETINFO cells on outgoing
6815 OR connections, to allow them to blend in better with clients.
6816 Removes another avenue for enumerating bridges. Reported by
6817 "troll_un". Fixes bug 4348; bugfix on 0.2.0.10-alpha, when NETINFO
6818 cells were introduced.
6821 - Fixed a typo in a hibernation-related log message. Fixes bug 4331;
6822 bugfix on 0.2.2.23-alpha; found by "tmpname0901".
6825 Changes in version 0.2.3.6-alpha - 2011-10-26
6826 Tor 0.2.3.6-alpha includes the fix from 0.2.2.34 for a critical
6827 anonymity vulnerability where an attacker can deanonymize Tor
6828 users. Everybody should upgrade.
6830 This release also features support for a new v3 connection handshake
6831 protocol, and fixes to make hidden service connections more robust.
6834 - Implement a new handshake protocol (v3) for authenticating Tors to
6835 each other over TLS. It should be more resistant to fingerprinting
6836 than previous protocols, and should require less TLS hacking for
6837 future Tor implementations. Implements proposal 176.
6838 - Allow variable-length padding cells to disguise the length of
6839 Tor's TLS records. Implements part of proposal 184.
6841 o Privacy/anonymity fixes (clients):
6842 - Clients and bridges no longer send TLS certificate chains on
6843 outgoing OR connections. Previously, each client or bridge would
6844 use the same cert chain for all outgoing OR connections until
6845 its IP address changes, which allowed any relay that the client
6846 or bridge contacted to determine which entry guards it is using.
6847 Fixes CVE-2011-2768. Bugfix on 0.0.9pre5; found by "frosty_un".
6848 - If a relay receives a CREATE_FAST cell on a TLS connection, it
6849 no longer considers that connection as suitable for satisfying a
6850 circuit EXTEND request. Now relays can protect clients from the
6851 CVE-2011-2768 issue even if the clients haven't upgraded yet.
6852 - Directory authorities no longer assign the Guard flag to relays
6853 that haven't upgraded to the above "refuse EXTEND requests
6854 to client connections" fix. Now directory authorities can
6855 protect clients from the CVE-2011-2768 issue even if neither
6856 the clients nor the relays have upgraded yet. There's a new
6857 "GiveGuardFlagTo_CVE_2011_2768_VulnerableRelays" config option
6858 to let us transition smoothly, else tomorrow there would be no
6861 o Major bugfixes (hidden services):
6862 - Improve hidden service robustness: when an attempt to connect to
6863 a hidden service ends, be willing to refetch its hidden service
6864 descriptors from each of the HSDir relays responsible for them
6865 immediately. Previously, we would not consider refetching the
6866 service's descriptors from each HSDir for 15 minutes after the last
6867 fetch, which was inconvenient if the hidden service was not running
6868 during the first attempt. Bugfix on 0.2.0.18-alpha; fixes bug 3335.
6869 - When one of a hidden service's introduction points appears to be
6870 unreachable, stop trying it. Previously, we would keep trying
6871 to build circuits to the introduction point until we lost the
6872 descriptor, usually because the user gave up and restarted Tor.
6873 Partly fixes bug 3825.
6874 - Don't launch a useless circuit after failing to use one of a
6875 hidden service's introduction points. Previously, we would
6876 launch a new introduction circuit, but not set the hidden service
6877 which that circuit was intended to connect to, so it would never
6878 actually be used. A different piece of code would then create a
6879 new introduction circuit correctly. Bug reported by katmagic and
6880 found by Sebastian Hahn. Bugfix on 0.2.1.13-alpha; fixes bug 4212.
6882 o Major bugfixes (other):
6883 - Bridges now refuse CREATE or CREATE_FAST cells on OR connections
6884 that they initiated. Relays could distinguish incoming bridge
6885 connections from client connections, creating another avenue for
6886 enumerating bridges. Fixes CVE-2011-2769. Bugfix on 0.2.0.3-alpha.
6887 Found by "frosty_un".
6888 - Don't update the AccountingSoftLimitHitAt state file entry whenever
6889 tor gets started. This prevents a wrong average bandwidth
6890 estimate, which would cause relays to always start a new accounting
6891 interval at the earliest possible moment. Fixes bug 2003; bugfix
6892 on 0.2.2.7-alpha. Reported by BryonEldridge, who also helped
6893 immensely in tracking this bug down.
6894 - Fix a crash bug when changing node restrictions while a DNS lookup
6895 is in-progress. Fixes bug 4259; bugfix on 0.2.2.25-alpha. Bugfix
6898 o Minor bugfixes (on 0.2.2.x and earlier):
6899 - When a hidden service turns an extra service-side introduction
6900 circuit into a general-purpose circuit, free the rend_data and
6901 intro_key fields first, so we won't leak memory if the circuit
6902 is cannibalized for use as another service-side introduction
6903 circuit. Bugfix on 0.2.1.7-alpha; fixes bug 4251.
6904 - Rephrase the log message emitted if the TestSocks check is
6905 successful. Patch from Fabian Keil; fixes bug 4094.
6906 - Bridges now skip DNS self-tests, to act a little more stealthily.
6907 Fixes bug 4201; bugfix on 0.2.0.3-alpha, which first introduced
6908 bridges. Patch by "warms0x".
6909 - Remove a confusing dollar sign from the example fingerprint in the
6910 man page, and also make the example fingerprint a valid one. Fixes
6911 bug 4309; bugfix on 0.2.1.3-alpha.
6912 - Fix internal bug-checking logic that was supposed to catch
6913 failures in digest generation so that it will fail more robustly
6914 if we ask for a nonexistent algorithm. Found by Coverity Scan.
6915 Bugfix on 0.2.2.1-alpha; fixes Coverity CID 479.
6916 - Report any failure in init_keys() calls launched because our
6917 IP address has changed. Spotted by Coverity Scan. Bugfix on
6918 0.1.1.4-alpha; fixes CID 484.
6920 o Minor bugfixes (on 0.2.3.x):
6921 - Fix a bug in configure.in that kept it from building a configure
6922 script with autoconf versions earlier than 2.61. Fixes bug 2430;
6923 bugfix on 0.2.3.1-alpha.
6924 - Don't warn users that they are exposing a client port to the
6925 Internet if they have specified an RFC1918 address. Previously,
6926 we would warn if the user had specified any non-loopback
6927 address. Bugfix on 0.2.3.3-alpha. Fixes bug 4018; reported by Tas.
6928 - Fix memory leaks in the failing cases of the new SocksPort and
6929 ControlPort code. Found by Coverity Scan. Bugfix on 0.2.3.3-alpha;
6930 fixes coverity CIDs 485, 486, and 487.
6933 - When a hidden service's introduction point times out, consider
6934 trying it again during the next attempt to connect to the
6935 HS. Previously, we would not try it again unless a newly fetched
6936 descriptor contained it. Required by fixes for bugs 1297 and 3825.
6937 - The next version of Windows will be called Windows 8, and it has
6938 a major version of 6, minor version of 2. Correctly identify that
6939 version instead of calling it "Very recent version". Resolves
6940 ticket 4153; reported by funkstar.
6941 - The Bridge Authority now writes statistics on how many bridge
6942 descriptors it gave out in total, and how many unique descriptors
6943 it gave out. It also lists how often the most and least commonly
6944 fetched descriptors were given out, as well as the median and
6945 25th/75th percentile. Implements tickets 4200 and 4294.
6946 - Update to the October 4 2011 Maxmind GeoLite Country database.
6948 o Code simplifications and refactoring:
6949 - Remove some old code to remember statistics about which descriptors
6950 we've served as a directory mirror. The feature wasn't used and
6951 is outdated now that microdescriptors are around.
6952 - Rename Tor functions that turn strings into addresses, so that
6953 "parse" indicates that no hostname resolution occurs, and
6954 "lookup" indicates that hostname resolution may occur. This
6955 should help prevent mistakes in the future. Fixes bug 3512.
6958 Changes in version 0.2.2.34 - 2011-10-26
6959 Tor 0.2.2.34 fixes a critical anonymity vulnerability where an attacker
6960 can deanonymize Tor users. Everybody should upgrade.
6962 The attack relies on four components: 1) Clients reuse their TLS cert
6963 when talking to different relays, so relays can recognize a user by
6964 the identity key in her cert. 2) An attacker who knows the client's
6965 identity key can probe each guard relay to see if that identity key
6966 is connected to that guard relay right now. 3) A variety of active
6967 attacks in the literature (starting from "Low-Cost Traffic Analysis
6968 of Tor" by Murdoch and Danezis in 2005) allow a malicious website to
6969 discover the guard relays that a Tor user visiting the website is using.
6970 4) Clients typically pick three guards at random, so the set of guards
6971 for a given user could well be a unique fingerprint for her. This
6972 release fixes components #1 and #2, which is enough to block the attack;
6973 the other two remain as open research problems. Special thanks to
6974 "frosty_un" for reporting the issue to us!
6976 Clients should upgrade so they are no longer recognizable by the TLS
6977 certs they present. Relays should upgrade so they no longer allow a
6978 remote attacker to probe them to test whether unpatched clients are
6979 currently connected to them.
6981 This release also fixes several vulnerabilities that allow an attacker
6982 to enumerate bridge relays. Some bridge enumeration attacks still
6983 remain; see for example proposal 188.
6985 o Privacy/anonymity fixes (clients):
6986 - Clients and bridges no longer send TLS certificate chains on
6987 outgoing OR connections. Previously, each client or bridge would
6988 use the same cert chain for all outgoing OR connections until
6989 its IP address changes, which allowed any relay that the client
6990 or bridge contacted to determine which entry guards it is using.
6991 Fixes CVE-2011-2768. Bugfix on 0.0.9pre5; found by "frosty_un".
6992 - If a relay receives a CREATE_FAST cell on a TLS connection, it
6993 no longer considers that connection as suitable for satisfying a
6994 circuit EXTEND request. Now relays can protect clients from the
6995 CVE-2011-2768 issue even if the clients haven't upgraded yet.
6996 - Directory authorities no longer assign the Guard flag to relays
6997 that haven't upgraded to the above "refuse EXTEND requests
6998 to client connections" fix. Now directory authorities can
6999 protect clients from the CVE-2011-2768 issue even if neither
7000 the clients nor the relays have upgraded yet. There's a new
7001 "GiveGuardFlagTo_CVE_2011_2768_VulnerableRelays" config option
7002 to let us transition smoothly, else tomorrow there would be no
7005 o Privacy/anonymity fixes (bridge enumeration):
7006 - Bridge relays now do their directory fetches inside Tor TLS
7007 connections, like all the other clients do, rather than connecting
7008 directly to the DirPort like public relays do. Removes another
7009 avenue for enumerating bridges. Fixes bug 4115; bugfix on 0.2.0.35.
7010 - Bridges relays now build circuits for themselves in a more similar
7011 way to how clients build them. Removes another avenue for
7012 enumerating bridges. Fixes bug 4124; bugfix on 0.2.0.3-alpha,
7013 when bridges were introduced.
7014 - Bridges now refuse CREATE or CREATE_FAST cells on OR connections
7015 that they initiated. Relays could distinguish incoming bridge
7016 connections from client connections, creating another avenue for
7017 enumerating bridges. Fixes CVE-2011-2769. Bugfix on 0.2.0.3-alpha.
7018 Found by "frosty_un".
7021 - Fix a crash bug when changing node restrictions while a DNS lookup
7022 is in-progress. Fixes bug 4259; bugfix on 0.2.2.25-alpha. Bugfix
7024 - Don't launch a useless circuit after failing to use one of a
7025 hidden service's introduction points. Previously, we would
7026 launch a new introduction circuit, but not set the hidden service
7027 which that circuit was intended to connect to, so it would never
7028 actually be used. A different piece of code would then create a
7029 new introduction circuit correctly. Bug reported by katmagic and
7030 found by Sebastian Hahn. Bugfix on 0.2.1.13-alpha; fixes bug 4212.
7033 - Change an integer overflow check in the OpenBSD_Malloc code so
7034 that GCC is less likely to eliminate it as impossible. Patch
7035 from Mansour Moufid. Fixes bug 4059.
7036 - When a hidden service turns an extra service-side introduction
7037 circuit into a general-purpose circuit, free the rend_data and
7038 intro_key fields first, so we won't leak memory if the circuit
7039 is cannibalized for use as another service-side introduction
7040 circuit. Bugfix on 0.2.1.7-alpha; fixes bug 4251.
7041 - Bridges now skip DNS self-tests, to act a little more stealthily.
7042 Fixes bug 4201; bugfix on 0.2.0.3-alpha, which first introduced
7043 bridges. Patch by "warms0x".
7044 - Fix internal bug-checking logic that was supposed to catch
7045 failures in digest generation so that it will fail more robustly
7046 if we ask for a nonexistent algorithm. Found by Coverity Scan.
7047 Bugfix on 0.2.2.1-alpha; fixes Coverity CID 479.
7048 - Report any failure in init_keys() calls launched because our
7049 IP address has changed. Spotted by Coverity Scan. Bugfix on
7050 0.1.1.4-alpha; fixes CID 484.
7052 o Minor bugfixes (log messages and documentation):
7053 - Remove a confusing dollar sign from the example fingerprint in the
7054 man page, and also make the example fingerprint a valid one. Fixes
7055 bug 4309; bugfix on 0.2.1.3-alpha.
7056 - The next version of Windows will be called Windows 8, and it has
7057 a major version of 6, minor version of 2. Correctly identify that
7058 version instead of calling it "Very recent version". Resolves
7059 ticket 4153; reported by funkstar.
7060 - Downgrade log messages about circuit timeout calibration from
7061 "notice" to "info": they don't require or suggest any human
7062 intervention. Patch from Tom Lowenthal. Fixes bug 4063;
7063 bugfix on 0.2.2.14-alpha.
7066 - Turn on directory request statistics by default and include them in
7067 extra-info descriptors. Don't break if we have no GeoIP database.
7068 Backported from 0.2.3.1-alpha; implements ticket 3951.
7069 - Update to the October 4 2011 Maxmind GeoLite Country database.
7072 Changes in version 0.2.1.31 - 2011-10-26
7073 Tor 0.2.1.31 backports important security and privacy fixes for
7074 oldstable. This release is intended only for package maintainers and
7075 others who cannot use the 0.2.2 stable series. All others should be
7076 using Tor 0.2.2.x or newer.
7078 o Security fixes (also included in 0.2.2.x):
7079 - Replace all potentially sensitive memory comparison operations
7080 with versions whose runtime does not depend on the data being
7081 compared. This will help resist a class of attacks where an
7082 adversary can use variations in timing information to learn
7083 sensitive data. Fix for one case of bug 3122. (Safe memcmp
7084 implementation by Robert Ransom based partially on code by DJB.)
7085 - Fix an assert in parsing router descriptors containing IPv6
7086 addresses. This one took down the directory authorities when
7087 somebody tried some experimental code. Bugfix on 0.2.1.3-alpha.
7089 o Privacy/anonymity fixes (also included in 0.2.2.x):
7090 - Clients and bridges no longer send TLS certificate chains on
7091 outgoing OR connections. Previously, each client or bridge would
7092 use the same cert chain for all outgoing OR connections until
7093 its IP address changes, which allowed any relay that the client
7094 or bridge contacted to determine which entry guards it is using.
7095 Fixes CVE-2011-2768. Bugfix on 0.0.9pre5; found by "frosty_un".
7096 - If a relay receives a CREATE_FAST cell on a TLS connection, it
7097 no longer considers that connection as suitable for satisfying a
7098 circuit EXTEND request. Now relays can protect clients from the
7099 CVE-2011-2768 issue even if the clients haven't upgraded yet.
7100 - Bridges now refuse CREATE or CREATE_FAST cells on OR connections
7101 that they initiated. Relays could distinguish incoming bridge
7102 connections from client connections, creating another avenue for
7103 enumerating bridges. Fixes CVE-2011-2769. Bugfix on 0.2.0.3-alpha.
7104 Found by "frosty_un".
7105 - When receiving a hidden service descriptor, check that it is for
7106 the hidden service we wanted. Previously, Tor would store any
7107 hidden service descriptors that a directory gave it, whether it
7108 wanted them or not. This wouldn't have let an attacker impersonate
7109 a hidden service, but it did let directories pre-seed a client
7110 with descriptors that it didn't want. Bugfix on 0.0.6.
7111 - Avoid linkability based on cached hidden service descriptors: forget
7112 all hidden service descriptors cached as a client when processing a
7113 SIGNAL NEWNYM command. Fixes bug 3000; bugfix on 0.0.6.
7114 - Make the bridge directory authority refuse to answer directory
7115 requests for "all" descriptors. It used to include bridge
7116 descriptors in its answer, which was a major information leak.
7117 Found by "piebeer". Bugfix on 0.2.0.3-alpha.
7118 - Don't attach new streams to old rendezvous circuits after SIGNAL
7119 NEWNYM. Previously, we would keep using an existing rendezvous
7120 circuit if it remained open (i.e. if it were kept open by a
7121 long-lived stream, or if a new stream were attached to it before
7122 Tor could notice that it was old and no longer in use). Bugfix on
7123 0.1.1.15-rc; fixes bug 3375.
7125 o Minor bugfixes (also included in 0.2.2.x):
7126 - When we restart our relay, we might get a successful connection
7127 from the outside before we've started our reachability tests,
7128 triggering a warning: "ORPort found reachable, but I have no
7129 routerinfo yet. Failing to inform controller of success." This
7130 bug was harmless unless Tor is running under a controller
7131 like Vidalia, in which case the controller would never get a
7132 REACHABILITY_SUCCEEDED status event. Bugfix on 0.1.2.6-alpha;
7134 - Build correctly on OSX with zlib 1.2.4 and higher with all warnings
7135 enabled. Fixes bug 1526.
7136 - Remove undocumented option "-F" from tor-resolve: it hasn't done
7137 anything since 0.2.1.16-rc.
7138 - Avoid signed/unsigned comparisons by making SIZE_T_CEILING unsigned.
7139 None of the cases where we did this before were wrong, but by making
7140 this change we avoid warnings. Fixes bug 2475; bugfix on 0.2.1.28.
7141 - Fix a rare crash bug that could occur when a client was configured
7142 with a large number of bridges. Fixes bug 2629; bugfix on
7143 0.2.1.2-alpha. Bugfix by trac user "shitlei".
7144 - Correct the warning displayed when a rendezvous descriptor exceeds
7145 the maximum size. Fixes bug 2750; bugfix on 0.2.1.5-alpha. Found by
7147 - Fix an uncommon assertion failure when running with DNSPort under
7148 heavy load. Fixes bug 2933; bugfix on 0.2.0.1-alpha.
7149 - When warning about missing zlib development packages during compile,
7150 give the correct package names. Bugfix on 0.2.0.1-alpha.
7151 - Require that introduction point keys and onion keys have public
7152 exponent 65537. Bugfix on 0.2.0.10-alpha.
7153 - Do not crash when our configuration file becomes unreadable, for
7154 example due to a permissions change, between when we start up
7155 and when a controller calls SAVECONF. Fixes bug 3135; bugfix
7157 - Fix warnings from GCC 4.6's "-Wunused-but-set-variable" option.
7159 - Always NUL-terminate the sun_path field of a sockaddr_un before
7160 passing it to the kernel. (Not a security issue: kernels are
7161 smart enough to reject bad sockaddr_uns.) Found by Coverity;
7162 CID #428. Bugfix on Tor 0.2.0.3-alpha.
7163 - Don't stack-allocate the list of supplementary GIDs when we're
7164 about to log them. Stack-allocating NGROUPS_MAX gid_t elements
7165 could take up to 256K, which is way too much stack. Found by
7166 Coverity; CID #450. Bugfix on 0.2.1.7-alpha.
7168 o Minor bugfixes (only in 0.2.1.x):
7169 - Resume using micro-version numbers in 0.2.1.x: our Debian packages
7170 rely on them. Bugfix on 0.2.1.30.
7171 - Use git revisions instead of svn revisions when generating our
7172 micro-version numbers. Bugfix on 0.2.1.15-rc; fixes bug 2402.
7174 o Minor features (also included in 0.2.2.x):
7175 - Adjust the expiration time on our SSL session certificates to
7176 better match SSL certs seen in the wild. Resolves ticket 4014.
7177 - Allow nameservers with IPv6 address. Resolves bug 2574.
7178 - Update to the October 4 2011 Maxmind GeoLite Country database.
7181 Changes in version 0.2.3.5-alpha - 2011-09-28
7182 Tor 0.2.3.5-alpha fixes two bugs that make it possible to enumerate
7183 bridge relays; fixes an assertion error that many users started hitting
7184 today; and adds the ability to refill token buckets more often than
7185 once per second, allowing significant performance improvements.
7188 - Bridge relays now do their directory fetches inside Tor TLS
7189 connections, like all the other clients do, rather than connecting
7190 directly to the DirPort like public relays do. Removes another
7191 avenue for enumerating bridges. Fixes bug 4115; bugfix on 0.2.0.35.
7192 - Bridges relays now build circuits for themselves in a more similar
7193 way to how clients build them. Removes another avenue for
7194 enumerating bridges. Fixes bug 4124; bugfix on 0.2.0.3-alpha,
7195 when bridges were introduced.
7198 - Fix an "Assertion md->held_by_node == 1 failed" error that could
7199 occur when the same microdescriptor was referenced by two node_t
7200 objects at once. Fix for bug 4118; bugfix on Tor 0.2.3.1-alpha.
7202 o Major features (networking):
7203 - Add a new TokenBucketRefillInterval option to refill token buckets
7204 more frequently than once per second. This should improve network
7205 performance, alleviate queueing problems, and make traffic less
7206 bursty. Implements proposal 183; closes ticket 3630. Design by
7207 Florian Tschorsch and Björn Scheuermann; implementation by
7211 - Change an integer overflow check in the OpenBSD_Malloc code so
7212 that GCC is less likely to eliminate it as impossible. Patch
7213 from Mansour Moufid. Fixes bug 4059.
7215 o Minor bugfixes (usability):
7216 - Downgrade log messages about circuit timeout calibration from
7217 "notice" to "info": they don't require or suggest any human
7218 intervention. Patch from Tom Lowenthal. Fixes bug 4063;
7219 bugfix on 0.2.2.14-alpha.
7221 o Minor features (diagnostics):
7222 - When the system call to create a listener socket fails, log the
7223 error message explaining why. This may help diagnose bug 4027.
7226 Changes in version 0.2.3.4-alpha - 2011-09-13
7227 Tor 0.2.3.4-alpha includes the fixes from 0.2.2.33, including a slight
7228 tweak to Tor's TLS handshake that makes relays and bridges that run
7229 this new version reachable from Iran again. It also fixes a few new
7230 bugs in 0.2.3.x, and teaches relays to recognize when they're not
7231 listed in the network consensus and republish.
7233 o Major bugfixes (also part of 0.2.2.33):
7234 - Avoid an assertion failure when reloading a configuration with
7235 TrackExitHosts changes. Found and fixed by 'laruldan'. Fixes bug
7236 3923; bugfix on 0.2.2.25-alpha.
7238 o Minor features (security, also part of 0.2.2.33):
7239 - Check for replays of the public-key encrypted portion of an
7240 INTRODUCE1 cell, in addition to the current check for replays of
7241 the g^x value. This prevents a possible class of active attacks
7242 by an attacker who controls both an introduction point and a
7243 rendezvous point, and who uses the malleability of AES-CTR to
7244 alter the encrypted g^x portion of the INTRODUCE1 cell. We think
7245 that these attacks are infeasible (requiring the attacker to send
7246 on the order of zettabytes of altered cells in a short interval),
7247 but we'd rather block them off in case there are any classes of
7248 this attack that we missed. Reported by Willem Pinckaers.
7250 o Minor features (also part of 0.2.2.33):
7251 - Adjust the expiration time on our SSL session certificates to
7252 better match SSL certs seen in the wild. Resolves ticket 4014.
7253 - Change the default required uptime for a relay to be accepted as
7254 a HSDir (hidden service directory) from 24 hours to 25 hours.
7255 Improves on 0.2.0.10-alpha; resolves ticket 2649.
7256 - Add a VoteOnHidServDirectoriesV2 config option to allow directory
7257 authorities to abstain from voting on assignment of the HSDir
7258 consensus flag. Related to bug 2649.
7259 - Update to the September 6 2011 Maxmind GeoLite Country database.
7261 o Minor bugfixes (also part of 0.2.2.33):
7262 - Demote the 'replay detected' log message emitted when a hidden
7263 service receives the same Diffie-Hellman public key in two different
7264 INTRODUCE2 cells to info level. A normal Tor client can cause that
7265 log message during its normal operation. Bugfix on 0.2.1.6-alpha;
7266 fixes part of bug 2442.
7267 - Demote the 'INTRODUCE2 cell is too {old,new}' log message to info
7268 level. There is nothing that a hidden service's operator can do
7269 to fix its clients' clocks. Bugfix on 0.2.1.6-alpha; fixes part
7271 - Clarify a log message specifying the characters permitted in
7272 HiddenServiceAuthorizeClient client names. Previously, the log
7273 message said that "[A-Za-z0-9+-_]" were permitted; that could have
7274 given the impression that every ASCII character between "+" and "_"
7275 was permitted. Now we say "[A-Za-z0-9+_-]". Bugfix on 0.2.1.5-alpha.
7277 o Build fixes (also part of 0.2.2.33):
7278 - Clean up some code issues that prevented Tor from building on older
7279 BSDs. Fixes bug 3894; reported by "grarpamp".
7280 - Search for a platform-specific version of "ar" when cross-compiling.
7281 Should fix builds on iOS. Resolves bug 3909, found by Marco Bonetti.
7284 - Fix a bug where the SocksPort option (for example) would get
7285 ignored and replaced by the default if a SocksListenAddress
7286 option was set. Bugfix on 0.2.3.3-alpha; fixes bug 3936. Fix by
7290 - Relays now try regenerating and uploading their descriptor more
7291 frequently if they are not listed in the consensus, or if the
7292 version of their descriptor listed in the consensus is too
7293 old. This fix should prevent situations where a server declines
7294 to re-publish itself because it has done so too recently, even
7295 though the authorities decided not to list its recent-enough
7296 descriptor. Fix for bug 3327.
7299 - Relays now include a reason for regenerating their descriptors
7300 in an HTTP header when uploading to the authorities. This will
7301 make it easier to debug descriptor-upload issues in the future.
7302 - When starting as root and then changing our UID via the User
7303 control option, and we have a ControlSocket configured, make sure
7304 that the ControlSocket is owned by the same account that Tor will
7305 run under. Implements ticket 3421; fix by Jérémy Bobbio.
7308 - Abort if tor_vasprintf fails in connection_printf_to_buf (a
7309 utility function used in the control-port code). This shouldn't
7310 ever happen unless Tor is completely out of memory, but if it did
7311 happen and Tor somehow recovered from it, Tor could have sent a log
7312 message to a control port in the middle of a reply to a controller
7313 command. Fixes part of bug 3428; bugfix on 0.1.2.3-alpha.
7314 - Make 'FetchUselessDescriptors' cause all descriptor types and
7315 all consensus types (including microdescriptors) to get fetched.
7316 Fixes bug 3851; bugfix on 0.2.3.1-alpha.
7319 - Make a new "entry connection" struct as an internal subtype of "edge
7320 connection", to simplify the code and make exit connections smaller.
7323 Changes in version 0.2.2.33 - 2011-09-13
7324 Tor 0.2.2.33 fixes several bugs, and includes a slight tweak to Tor's
7325 TLS handshake that makes relays and bridges that run this new version
7326 reachable from Iran again.
7329 - Avoid an assertion failure when reloading a configuration with
7330 TrackExitHosts changes. Found and fixed by 'laruldan'. Fixes bug
7331 3923; bugfix on 0.2.2.25-alpha.
7333 o Minor features (security):
7334 - Check for replays of the public-key encrypted portion of an
7335 INTRODUCE1 cell, in addition to the current check for replays of
7336 the g^x value. This prevents a possible class of active attacks
7337 by an attacker who controls both an introduction point and a
7338 rendezvous point, and who uses the malleability of AES-CTR to
7339 alter the encrypted g^x portion of the INTRODUCE1 cell. We think
7340 that these attacks are infeasible (requiring the attacker to send
7341 on the order of zettabytes of altered cells in a short interval),
7342 but we'd rather block them off in case there are any classes of
7343 this attack that we missed. Reported by Willem Pinckaers.
7346 - Adjust the expiration time on our SSL session certificates to
7347 better match SSL certs seen in the wild. Resolves ticket 4014.
7348 - Change the default required uptime for a relay to be accepted as
7349 a HSDir (hidden service directory) from 24 hours to 25 hours.
7350 Improves on 0.2.0.10-alpha; resolves ticket 2649.
7351 - Add a VoteOnHidServDirectoriesV2 config option to allow directory
7352 authorities to abstain from voting on assignment of the HSDir
7353 consensus flag. Related to bug 2649.
7354 - Update to the September 6 2011 Maxmind GeoLite Country database.
7356 o Minor bugfixes (documentation and log messages):
7357 - Correct the man page to explain that HashedControlPassword and
7358 CookieAuthentication can both be set, in which case either method
7359 is sufficient to authenticate to Tor. Bugfix on 0.2.0.7-alpha,
7360 when we decided to allow these config options to both be set. Issue
7362 - Demote the 'replay detected' log message emitted when a hidden
7363 service receives the same Diffie-Hellman public key in two different
7364 INTRODUCE2 cells to info level. A normal Tor client can cause that
7365 log message during its normal operation. Bugfix on 0.2.1.6-alpha;
7366 fixes part of bug 2442.
7367 - Demote the 'INTRODUCE2 cell is too {old,new}' log message to info
7368 level. There is nothing that a hidden service's operator can do
7369 to fix its clients' clocks. Bugfix on 0.2.1.6-alpha; fixes part
7371 - Clarify a log message specifying the characters permitted in
7372 HiddenServiceAuthorizeClient client names. Previously, the log
7373 message said that "[A-Za-z0-9+-_]" were permitted; that could have
7374 given the impression that every ASCII character between "+" and "_"
7375 was permitted. Now we say "[A-Za-z0-9+_-]". Bugfix on 0.2.1.5-alpha.
7378 - Provide a substitute implementation of lround() for MSVC, which
7379 apparently lacks it. Patch from Gisle Vanem.
7380 - Clean up some code issues that prevented Tor from building on older
7381 BSDs. Fixes bug 3894; reported by "grarpamp".
7382 - Search for a platform-specific version of "ar" when cross-compiling.
7383 Should fix builds on iOS. Resolves bug 3909, found by Marco Bonetti.
7386 Changes in version 0.2.3.3-alpha - 2011-09-01
7387 Tor 0.2.3.3-alpha adds a new "stream isolation" feature to improve Tor's
7388 security, and provides client-side support for the microdescriptor
7389 and optimistic data features introduced earlier in the 0.2.3.x
7390 series. It also includes numerous critical bugfixes in the (optional)
7391 bufferevent-based networking backend.
7393 o Major features (stream isolation):
7394 - You can now configure Tor so that streams from different
7395 applications are isolated on different circuits, to prevent an
7396 attacker who sees your streams as they leave an exit node from
7397 linking your sessions to one another. To do this, choose some way
7398 to distinguish the applications: have them connect to different
7399 SocksPorts, or have one of them use SOCKS4 while the other uses
7400 SOCKS5, or have them pass different authentication strings to the
7401 SOCKS proxy. Then, use the new SocksPort syntax to configure the
7402 degree of isolation you need. This implements Proposal 171.
7403 - There's a new syntax for specifying multiple client ports (such as
7404 SOCKSPort, TransPort, DNSPort, NATDPort): you can now just declare
7405 multiple *Port entries with full addr:port syntax on each.
7406 The old *ListenAddress format is still supported, but you can't
7407 mix it with the new *Port syntax.
7409 o Major features (other):
7410 - Enable microdescriptor fetching by default for clients. This allows
7411 clients to download a much smaller amount of directory information.
7412 To disable it (and go back to the old-style consensus and
7413 descriptors), set "UseMicrodescriptors 0" in your torrc file.
7414 - Tor's firewall-helper feature, introduced in 0.2.3.1-alpha (see the
7415 "PortForwarding" config option), now supports Windows.
7416 - When using an exit relay running 0.2.3.x, clients can now
7417 "optimistically" send data before the exit relay reports that
7418 the stream has opened. This saves a round trip when starting
7419 connections where the client speaks first (such as web browsing).
7420 This behavior is controlled by a consensus parameter (currently
7421 disabled). To turn it on or off manually, use the "OptimisticData"
7422 torrc option. Implements proposal 181; code by Ian Goldberg.
7424 o Major bugfixes (bufferevents, fixes on 0.2.3.1-alpha):
7425 - When using IOCP on Windows, we need to enable Libevent windows
7427 - The IOCP backend now works even when the user has not specified
7428 the (internal, debugging-only) _UseFilteringSSLBufferevents option.
7429 Fixes part of bug 3752.
7430 - Correctly record the bytes we've read and written when using
7431 bufferevents, so that we can include them in our bandwidth history
7432 and advertised bandwidth. Fixes bug 3803.
7433 - Apply rate-limiting only at the bottom of a chain of filtering
7434 bufferevents. This prevents us from filling up internal read
7435 buffers and violating rate-limits when filtering bufferevents
7436 are enabled. Fixes part of bug 3804.
7437 - Add high-watermarks to the output buffers for filtered
7438 bufferevents. This prevents us from filling up internal write
7439 buffers and wasting CPU cycles when filtering bufferevents are
7440 enabled. Fixes part of bug 3804.
7441 - Correctly notice when data has been written from a bufferevent
7442 without flushing it completely. Fixes bug 3805.
7443 - Fix a bug where server-side tunneled bufferevent-based directory
7444 streams would get closed prematurely. Fixes bug 3814.
7445 - Fix a use-after-free error with per-connection rate-limiting
7446 buckets. Fixes bug 3888.
7448 o Major bugfixes (also part of 0.2.2.31-rc):
7449 - If we're configured to write our ControlPorts to disk, only write
7450 them after switching UID and creating the data directory. This way,
7451 we don't fail when starting up with a nonexistent DataDirectory
7452 and a ControlPortWriteToFile setting based on that directory. Fixes
7453 bug 3747; bugfix on Tor 0.2.2.26-beta.
7456 - Added a new CONF_CHANGED event so that controllers can be notified
7457 of any configuration changes made by other controllers, or by the
7458 user. Implements ticket 1692.
7459 - Use evbuffer_copyout() in inspect_evbuffer(). This fixes a memory
7460 leak when using bufferevents, and lets Libevent worry about how to
7461 best copy data out of a buffer.
7462 - Replace files in stats/ rather than appending to them. Now that we
7463 include statistics in extra-info descriptors, it makes no sense to
7464 keep old statistics forever. Implements ticket 2930.
7466 o Minor features (build compatibility):
7467 - Limited, experimental support for building with nmake and MSVC.
7468 - Provide a substitute implementation of lround() for MSVC, which
7469 apparently lacks it. Patch from Gisle Vanem.
7471 o Minor features (also part of 0.2.2.31-rc):
7472 - Update to the August 2 2011 Maxmind GeoLite Country database.
7474 o Minor bugfixes (on 0.2.3.x-alpha):
7475 - Fix a spurious warning when parsing SOCKS requests with
7476 bufferevents enabled. Fixes bug 3615; bugfix on 0.2.3.2-alpha.
7477 - Get rid of a harmless warning that could happen on relays running
7478 with bufferevents. The warning was caused by someone doing an http
7479 request to a relay's orport. Also don't warn for a few related
7480 non-errors. Fixes bug 3700; bugfix on 0.2.3.1-alpha.
7482 o Minor bugfixes (on 2.2.x and earlier):
7483 - Correct the man page to explain that HashedControlPassword and
7484 CookieAuthentication can both be set, in which case either method
7485 is sufficient to authenticate to Tor. Bugfix on 0.2.0.7-alpha,
7486 when we decided to allow these config options to both be set. Issue
7488 - The "--quiet" and "--hush" options now apply not only to Tor's
7489 behavior before logs are configured, but also to Tor's behavior in
7490 the absense of configured logs. Fixes bug 3550; bugfix on
7493 o Minor bugfixes (also part of 0.2.2.31-rc):
7494 - Write several files in text mode, on OSes that distinguish text
7495 mode from binary mode (namely, Windows). These files are:
7496 'buffer-stats', 'dirreq-stats', and 'entry-stats' on relays
7497 that collect those statistics; 'client_keys' and 'hostname' for
7498 hidden services that use authentication; and (in the tor-gencert
7499 utility) newly generated identity and signing keys. Previously,
7500 we wouldn't specify text mode or binary mode, leading to an
7501 assertion failure. Fixes bug 3607. Bugfix on 0.2.1.1-alpha (when
7502 the DirRecordUsageByCountry option which would have triggered
7503 the assertion failure was added), although this assertion failure
7504 would have occurred in tor-gencert on Windows in 0.2.0.1-alpha.
7505 - Selectively disable deprecation warnings on OS X because Lion
7506 started deprecating the shipped copy of openssl. Fixes bug 3643.
7507 - Remove an extra pair of quotation marks around the error
7508 message in control-port STATUS_GENERAL BUG events. Bugfix on
7509 0.1.2.6-alpha; fixes bug 3732.
7510 - When unable to format an address as a string, report its value
7511 as "???" rather than reusing the last formatted address. Bugfix
7514 o Code simplifications and refactoring:
7515 - Rewrite the listener-selection logic so that parsing which ports
7516 we want to listen on is now separate from binding to the ports
7520 - Building Tor with bufferevent support now requires Libevent
7521 2.0.13-stable or later. Previous versions of Libevent had bugs in
7522 SSL-related bufferevents and related issues that would make Tor
7523 work badly with bufferevents. Requiring 2.0.13-stable also allows
7524 Tor with bufferevents to take advantage of Libevent APIs
7525 introduced after 2.0.8-rc.
7528 Changes in version 0.2.2.32 - 2011-08-27
7529 The Tor 0.2.2 release series is dedicated to the memory of Andreas
7530 Pfitzmann (1958-2010), a pioneer in anonymity and privacy research,
7531 a founder of the PETS community, a leader in our field, a mentor,
7532 and a friend. He left us with these words: "I had the possibility
7533 to contribute to this world that is not as it should be. I hope I
7534 could help in some areas to make the world a better place, and that
7535 I could also encourage other people to be engaged in improving the
7536 world. Please, stay engaged. This world needs you, your love, your
7537 initiative -- now I cannot be part of that anymore."
7539 Tor 0.2.2.32, the first stable release in the 0.2.2 branch, is finally
7540 ready. More than two years in the making, this release features improved
7541 client performance and hidden service reliability, better compatibility
7542 for Android, correct behavior for bridges that listen on more than
7543 one address, more extensible and flexible directory object handling,
7544 better reporting of network statistics, improved code security, and
7545 many many other features and bugfixes.
7548 Changes in version 0.2.2.31-rc - 2011-08-17
7549 Tor 0.2.2.31-rc is the second and hopefully final release candidate
7550 for the Tor 0.2.2.x series.
7553 - Remove an extra pair of quotation marks around the error
7554 message in control-port STATUS_GENERAL BUG events. Bugfix on
7555 0.1.2.6-alpha; fixes bug 3732.
7556 - If we're configured to write our ControlPorts to disk, only write
7557 them after switching UID and creating the data directory. This way,
7558 we don't fail when starting up with a nonexistent DataDirectory
7559 and a ControlPortWriteToFile setting based on that directory. Fixes
7560 bug 3747; bugfix on Tor 0.2.2.26-beta.
7563 - Update to the August 2 2011 Maxmind GeoLite Country database.
7566 - Allow GETINFO fingerprint to return a fingerprint even when
7567 we have not yet built a router descriptor. Fixes bug 3577;
7568 bugfix on 0.2.0.1-alpha.
7569 - Write several files in text mode, on OSes that distinguish text
7570 mode from binary mode (namely, Windows). These files are:
7571 'buffer-stats', 'dirreq-stats', and 'entry-stats' on relays
7572 that collect those statistics; 'client_keys' and 'hostname' for
7573 hidden services that use authentication; and (in the tor-gencert
7574 utility) newly generated identity and signing keys. Previously,
7575 we wouldn't specify text mode or binary mode, leading to an
7576 assertion failure. Fixes bug 3607. Bugfix on 0.2.1.1-alpha (when
7577 the DirRecordUsageByCountry option which would have triggered
7578 the assertion failure was added), although this assertion failure
7579 would have occurred in tor-gencert on Windows in 0.2.0.1-alpha.
7580 - Selectively disable deprecation warnings on OS X because Lion
7581 started deprecating the shipped copy of openssl. Fixes bug 3643.
7582 - When unable to format an address as a string, report its value
7583 as "???" rather than reusing the last formatted address. Bugfix
7587 Changes in version 0.2.3.2-alpha - 2011-07-18
7588 Tor 0.2.3.2-alpha introduces two new experimental features:
7589 microdescriptors and pluggable transports. It also continues cleaning
7590 up a variety of recently introduced features.
7593 - Clients can now use microdescriptors instead of regular descriptors
7594 to build circuits. Microdescriptors are authority-generated
7595 summaries of regular descriptors' contents, designed to change
7596 very rarely (see proposal 158 for details). This feature is
7597 designed to save bandwidth, especially for clients on slow internet
7598 connections. It's off by default for now, since nearly no caches
7599 support it, but it will be on-by-default for clients in a future
7600 version. You can use the UseMicrodescriptors option to turn it on.
7601 - Tor clients using bridges can now be configured to use a separate
7602 'transport' proxy for each bridge. This approach helps to resist
7603 censorship by allowing bridges to use protocol obfuscation
7604 plugins. It implements part of proposal 180. Implements ticket 2841.
7605 - While we're trying to bootstrap, record how many TLS connections
7606 fail in each state, and report which states saw the most failures
7607 in response to any bootstrap failures. This feature may speed up
7608 diagnosis of censorship events. Implements ticket 3116.
7610 o Major bugfixes (on 0.2.3.1-alpha):
7611 - When configuring a large set of nodes in EntryNodes (as with
7612 'EntryNodes {cc}' or 'EntryNodes 1.1.1.1/16'), choose only a
7613 random subset to be guards, and choose them in random
7614 order. Fixes bug 2798.
7615 - Tor could crash when remembering a consensus in a non-used consensus
7616 flavor without having a current consensus set. Fixes bug 3361.
7617 - Comparing an unknown address to a microdescriptor's shortened exit
7618 policy would always give a "rejected" result. Fixes bug 3599.
7619 - Using microdescriptors as a client no longer prevents Tor from
7620 uploading and downloading hidden service descriptors. Fixes
7624 - Allow nameservers with IPv6 address. Resolves bug 2574.
7625 - Accept attempts to include a password authenticator in the
7626 handshake, as supported by SOCKS5. This handles SOCKS clients that
7627 don't know how to omit a password when authenticating. Resolves
7629 - When configuring a large set of nodes in EntryNodes, and there are
7630 enough of them listed as Guard so that we don't need to consider
7631 the non-guard entries, prefer the ones listed with the Guard flag.
7632 - Check for and recover from inconsistency in the microdescriptor
7633 cache. This will make it harder for us to accidentally free a
7634 microdescriptor without removing it from the appropriate data
7635 structures. Fixes issue 3135; issue noted by "wanoskarnet".
7636 - Log SSL state transitions at log level DEBUG, log domain
7637 HANDSHAKE. This can be useful for debugging censorship events.
7638 Implements ticket 3264.
7639 - Add port 6523 (Gobby) to LongLivedPorts. Patch by intrigeri;
7640 implements ticket 3439.
7642 o Minor bugfixes (on 0.2.3.1-alpha):
7643 - Do not free all general-purpose regular descriptors just
7644 because microdescriptor use is enabled. Fixes bug 3113.
7645 - Correctly link libevent_openssl when --enable-static-libevent
7646 is passed to configure. Fixes bug 3118.
7647 - Bridges should not complain during their heartbeat log messages that
7648 they are unlisted in the consensus: that's more or less the point
7649 of being a bridge. Fixes bug 3183.
7650 - Report a SIGNAL event to controllers when acting on a delayed
7651 SIGNAL NEWNYM command. Previously, we would report a SIGNAL
7652 event to the controller if we acted on a SIGNAL NEWNYM command
7653 immediately, and otherwise not report a SIGNAL event for the
7654 command at all. Fixes bug 3349.
7655 - Fix a crash when handling the SIGNAL controller command or
7656 reporting ERR-level status events with bufferevents enabled. Found
7657 by Robert Ransom. Fixes bug 3367.
7658 - Always ship the tor-fw-helper manpage in our release tarballs.
7659 Fixes bug 3389. Reported by Stephen Walker.
7660 - Fix a class of double-mark-for-close bugs when bufferevents
7661 are enabled. Fixes bug 3403.
7662 - Update tor-fw-helper to support libnatpmp-20110618. Fixes bug 3434.
7663 - Add SIGNAL to the list returned by the 'GETINFO events/names'
7664 control-port command. Fixes part of bug 3465.
7665 - Prevent using negative indices during unit test runs when read_all()
7666 fails. Spotted by coverity.
7667 - Fix a rare memory leak when checking the nodelist without it being
7668 present. Found by coverity.
7669 - Only try to download a microdescriptor-flavored consensus from
7670 a directory cache that provides them.
7672 o Minor bugfixes (on 0.2.2.x and earlier):
7673 - Assert that hidden-service-related operations are not performed
7674 using single-hop circuits. Previously, Tor would assert that
7675 client-side streams are not attached to single-hop circuits,
7676 but not that other sensitive operations on the client and service
7677 side are not performed using single-hop circuits. Fixes bug 3332;
7679 - Don't publish a new relay descriptor when we reload our onion key,
7680 unless the onion key has actually changed. Fixes bug 3263 and
7681 resolves another cause of bug 1810. Bugfix on 0.1.1.11-alpha.
7682 - Allow GETINFO fingerprint to return a fingerprint even when
7683 we have not yet built a router descriptor. Fixes bug 3577;
7684 bugfix on 0.2.0.1-alpha.
7685 - Make 'tor --digests' list hashes of all Tor source files. Bugfix
7686 on 0.2.2.4-alpha; fixes bug 3427.
7688 o Code simplification and refactoring:
7689 - Use tor_sscanf() in place of scanf() in more places through the
7690 code. This makes us a little more locale-independent, and
7691 should help shut up code-analysis tools that can't tell
7692 a safe sscanf string from a dangerous one.
7693 - Use tt_assert(), not tor_assert(), for checking for test failures.
7694 This makes the unit tests more able to go on in the event that
7696 - Split connection_about_to_close() into separate functions for each
7700 - On Windows, we now define the _WIN32_WINNT macros only if they
7701 are not already defined. This lets the person building Tor decide,
7702 if they want, to require a later version of Windows.
7705 Changes in version 0.2.2.30-rc - 2011-07-07
7706 Tor 0.2.2.30-rc is the first release candidate for the Tor 0.2.2.x
7707 series. It fixes a few smaller bugs, but generally appears stable.
7708 Please test it and let us know whether it is!
7711 - Send a SUCCEEDED stream event to the controller when a reverse
7712 resolve succeeded. Fixes bug 3536; bugfix on 0.0.8pre1. Issue
7713 discovered by katmagic.
7714 - Always NUL-terminate the sun_path field of a sockaddr_un before
7715 passing it to the kernel. (Not a security issue: kernels are
7716 smart enough to reject bad sockaddr_uns.) Found by Coverity;
7717 CID #428. Bugfix on Tor 0.2.0.3-alpha.
7718 - Don't stack-allocate the list of supplementary GIDs when we're
7719 about to log them. Stack-allocating NGROUPS_MAX gid_t elements
7720 could take up to 256K, which is way too much stack. Found by
7721 Coverity; CID #450. Bugfix on 0.2.1.7-alpha.
7722 - Add BUILDTIMEOUT_SET to the list returned by the 'GETINFO
7723 events/names' control-port command. Bugfix on 0.2.2.9-alpha;
7724 fixes part of bug 3465.
7725 - Fix a memory leak when receiving a descriptor for a hidden
7726 service we didn't ask for. Found by Coverity; CID #30. Bugfix
7730 - Update to the July 1 2011 Maxmind GeoLite Country database.
7733 Changes in version 0.2.2.29-beta - 2011-06-20
7734 Tor 0.2.2.29-beta reverts an accidental behavior change for users who
7735 have bridge lines in their torrc but don't want to use them; gets
7736 us closer to having the control socket feature working on Debian;
7737 and fixes a variety of smaller bugs.
7740 - Revert the UseBridges option to its behavior before 0.2.2.28-beta.
7741 When we changed the default behavior to "use bridges if any
7742 are listed in the torrc", we surprised users who had bridges
7743 in their torrc files but who didn't actually want to use them.
7744 Partial resolution for bug 3354.
7747 - Don't attach new streams to old rendezvous circuits after SIGNAL
7748 NEWNYM. Previously, we would keep using an existing rendezvous
7749 circuit if it remained open (i.e. if it were kept open by a
7750 long-lived stream, or if a new stream were attached to it before
7751 Tor could notice that it was old and no longer in use). Bugfix on
7752 0.1.1.15-rc; fixes bug 3375.
7755 - Fix a bug when using ControlSocketsGroupWritable with User. The
7756 directory's group would be checked against the current group, not
7757 the configured group. Patch by Jérémy Bobbio. Fixes bug 3393;
7758 bugfix on 0.2.2.26-beta.
7759 - Make connection_printf_to_buf()'s behavior sane. Its callers
7760 expect it to emit a CRLF iff the format string ends with CRLF;
7761 it actually emitted a CRLF iff (a) the format string ended with
7762 CRLF or (b) the resulting string was over 1023 characters long or
7763 (c) the format string did not end with CRLF *and* the resulting
7764 string was 1021 characters long or longer. Bugfix on 0.1.1.9-alpha;
7765 fixes part of bug 3407.
7766 - Make send_control_event_impl()'s behavior sane. Its callers
7767 expect it to always emit a CRLF at the end of the string; it
7768 might have emitted extra control characters as well. Bugfix on
7769 0.1.1.9-alpha; fixes another part of bug 3407.
7770 - Make crypto_rand_int() check the value of its input correctly.
7771 Previously, it accepted values up to UINT_MAX, but could return a
7772 negative number if given a value above INT_MAX+1. Found by George
7773 Kadianakis. Fixes bug 3306; bugfix on 0.2.2pre14.
7774 - Avoid a segfault when reading a malformed circuit build state
7775 with more than INT_MAX entries. Found by wanoskarnet. Bugfix on
7777 - When asked about a DNS record type we don't support via a
7778 client DNSPort, reply with NOTIMPL rather than an empty
7779 reply. Patch by intrigeri. Fixes bug 3369; bugfix on 2.0.1-alpha.
7780 - Fix a rare memory leak during stats writing. Found by coverity.
7783 - Update to the June 1 2011 Maxmind GeoLite Country database.
7785 o Code simplifications and refactoring:
7786 - Remove some dead code as indicated by coverity.
7787 - Remove a few dead assignments during router parsing. Found by
7789 - Add some forgotten return value checks during unit tests. Found
7791 - Don't use 1-bit wide signed bit fields. Found by coverity.
7794 Changes in version 0.2.2.28-beta - 2011-06-04
7795 Tor 0.2.2.28-beta makes great progress towards a new stable release: we
7796 fixed a big bug in whether relays stay in the consensus consistently,
7797 we moved closer to handling bridges and hidden services correctly,
7798 and we started the process of better handling the dreaded "my Vidalia
7799 died, and now my Tor demands a password when I try to reconnect to it"
7803 - Don't decide to make a new descriptor when receiving a HUP signal.
7804 This bug has caused a lot of 0.2.2.x relays to disappear from the
7805 consensus periodically. Fixes the most common case of triggering
7806 bug 1810; bugfix on 0.2.2.7-alpha.
7807 - Actually allow nameservers with IPv6 addresses. Fixes bug 2574.
7808 - Don't try to build descriptors if "ORPort auto" is set and we
7809 don't know our actual ORPort yet. Fix for bug 3216; bugfix on
7811 - Resolve a crash that occurred when setting BridgeRelay to 1 with
7812 accounting enabled. Fixes bug 3228; bugfix on 0.2.2.18-alpha.
7813 - Apply circuit timeouts to opened hidden-service-related circuits
7814 based on the correct start time. Previously, we would apply the
7815 circuit build timeout based on time since the circuit's creation;
7816 it was supposed to be applied based on time since the circuit
7817 entered its current state. Bugfix on 0.0.6; fixes part of bug 1297.
7818 - Use the same circuit timeout for client-side introduction
7819 circuits as for other four-hop circuits, rather than the timeout
7820 for single-hop directory-fetch circuits; the shorter timeout may
7821 have been appropriate with the static circuit build timeout in
7822 0.2.1.x and earlier, but caused many hidden service access attempts
7823 to fail with the adaptive CBT introduced in 0.2.2.2-alpha. Bugfix
7824 on 0.2.2.2-alpha; fixes another part of bug 1297.
7825 - In ticket 2511 we fixed a case where you could use an unconfigured
7826 bridge if you had configured it as a bridge the last time you ran
7827 Tor. Now fix another edge case: if you had configured it as a bridge
7828 but then switched to a different bridge via the controller, you
7829 would still be willing to use the old one. Bugfix on 0.2.0.1-alpha;
7833 - Add an __OwningControllerProcess configuration option and a
7834 TAKEOWNERSHIP control-port command. Now a Tor controller can ensure
7835 that when it exits, Tor will shut down. Implements feature 3049.
7836 - If "UseBridges 1" is set and no bridges are configured, Tor will
7837 now refuse to build any circuits until some bridges are set.
7838 If "UseBridges auto" is set, Tor will use bridges if they are
7839 configured and we are not running as a server, but otherwise will
7840 make circuits as usual. The new default is "auto". Patch by anonym,
7841 so the Tails LiveCD can stop automatically revealing you as a Tor
7845 - Fix warnings from GCC 4.6's "-Wunused-but-set-variable" option.
7846 - Remove a trailing asterisk from "exit-policy/default" in the
7847 output of the control port command "GETINFO info/names". Bugfix
7849 - Use a wide type to hold sockets when built for 64-bit Windows builds.
7851 - Warn when the user configures two HiddenServiceDir lines that point
7852 to the same directory. Bugfix on 0.0.6 (the version introducing
7853 HiddenServiceDir); fixes bug 3289.
7854 - Remove dead code from rend_cache_lookup_v2_desc_as_dir. Fixes
7855 part of bug 2748; bugfix on 0.2.0.10-alpha.
7856 - Log malformed requests for rendezvous descriptors as protocol
7857 warnings, not warnings. Also, use a more informative log message
7858 in case someone sees it at log level warning without prior
7859 info-level messages. Fixes the other part of bug 2748; bugfix
7861 - Clear the table recording the time of the last request for each
7862 hidden service descriptor from each HS directory on SIGNAL NEWNYM.
7863 Previously, we would clear our HS descriptor cache on SIGNAL
7864 NEWNYM, but if we had previously retrieved a descriptor (or tried
7865 to) from every directory responsible for it, we would refuse to
7866 fetch it again for up to 15 minutes. Bugfix on 0.2.2.25-alpha;
7868 - Fix a log message that said "bits" while displaying a value in
7869 bytes. Found by wanoskarnet. Fixes bug 3318; bugfix on
7871 - When checking for 1024-bit keys, check for 1024 bits, not 128
7872 bytes. This allows Tor to correctly discard keys of length 1017
7873 through 1023. Bugfix on 0.0.9pre5.
7876 - Relays now log the reason for publishing a new relay descriptor,
7877 so we have a better chance of hunting down instances of bug 1810.
7878 Resolves ticket 3252.
7879 - Revise most log messages that refer to nodes by nickname to
7880 instead use the "$key=nickname at address" format. This should be
7881 more useful, especially since nicknames are less and less likely
7882 to be unique. Resolves ticket 3045.
7883 - Log (at info level) when purging pieces of hidden-service-client
7884 state because of SIGNAL NEWNYM.
7887 - Remove undocumented option "-F" from tor-resolve: it hasn't done
7888 anything since 0.2.1.16-rc.
7891 Changes in version 0.2.2.27-beta - 2011-05-18
7892 Tor 0.2.2.27-beta fixes a bridge-related stability bug in the previous
7893 release, and also adds a few more general bugfixes.
7896 - Fix a crash bug when changing bridges in a running Tor process.
7897 Fixes bug 3213; bugfix on 0.2.2.26-beta.
7898 - When the controller configures a new bridge, don't wait 10 to 60
7899 seconds before trying to fetch its descriptor. Bugfix on
7900 0.2.0.3-alpha; fixes bug 3198 (suggested by 2355).
7903 - Require that onion keys have exponent 65537 in microdescriptors too.
7904 Fixes more of bug 3207; bugfix on 0.2.2.26-beta.
7905 - Tor used to limit HttpProxyAuthenticator values to 48 characters.
7906 Changed the limit to 512 characters by removing base64 newlines.
7907 Fixes bug 2752. Fix by Michael Yakubovich.
7908 - When a client starts or stops using bridges, never use a circuit
7909 that was built before the configuration change. This behavior could
7910 put at risk a user who uses bridges to ensure that her traffic
7911 only goes to the chosen addresses. Bugfix on 0.2.0.3-alpha; fixes
7915 Changes in version 0.2.2.26-beta - 2011-05-17
7916 Tor 0.2.2.26-beta fixes a variety of potential privacy problems. It
7917 also introduces a new "socksport auto" approach that should make it
7918 easier to run multiple Tors on the same system, and does a lot of
7919 cleanup to get us closer to a release candidate.
7921 o Security/privacy fixes:
7922 - Replace all potentially sensitive memory comparison operations
7923 with versions whose runtime does not depend on the data being
7924 compared. This will help resist a class of attacks where an
7925 adversary can use variations in timing information to learn
7926 sensitive data. Fix for one case of bug 3122. (Safe memcmp
7927 implementation by Robert Ransom based partially on code by DJB.)
7928 - When receiving a hidden service descriptor, check that it is for
7929 the hidden service we wanted. Previously, Tor would store any
7930 hidden service descriptors that a directory gave it, whether it
7931 wanted them or not. This wouldn't have let an attacker impersonate
7932 a hidden service, but it did let directories pre-seed a client
7933 with descriptors that it didn't want. Bugfix on 0.0.6.
7934 - On SIGHUP, do not clear out all TrackHostExits mappings, client
7935 DNS cache entries, and virtual address mappings: that's what
7936 NEWNYM is for. Fixes bug 1345; bugfix on 0.1.0.1-rc.
7939 - The options SocksPort, ControlPort, and so on now all accept a
7940 value "auto" that opens a socket on an OS-selected port. A
7941 new ControlPortWriteToFile option tells Tor to write its
7942 actual control port or ports to a chosen file. If the option
7943 ControlPortFileGroupReadable is set, the file is created as
7944 group-readable. Now users can run two Tor clients on the same
7945 system without needing to manually mess with parameters. Resolves
7946 part of ticket 3076.
7947 - Set SO_REUSEADDR on all sockets, not just listeners. This should
7948 help busy exit nodes avoid running out of useable ports just
7949 because all the ports have been used in the near past. Resolves
7953 - New "GETINFO net/listeners/(type)" controller command to return
7954 a list of addresses and ports that are bound for listeners for a
7955 given connection type. This is useful when the user has configured
7956 "SocksPort auto" and the controller needs to know which port got
7957 chosen. Resolves another part of ticket 3076.
7958 - Add a new ControlSocketsGroupWritable configuration option: when
7959 it is turned on, ControlSockets are group-writeable by the default
7960 group of the current user. Patch by Jérémy Bobbio; implements
7962 - Tor now refuses to create a ControlSocket in a directory that is
7963 world-readable (or group-readable if ControlSocketsGroupWritable
7964 is 0). This is necessary because some operating systems do not
7965 enforce permissions on an AF_UNIX sockets. Permissions on the
7966 directory holding the socket, however, seems to work everywhere.
7967 - Rate-limit a warning about failures to download v2 networkstatus
7968 documents. Resolves part of bug 1352.
7969 - Backport code from 0.2.3.x that allows directory authorities to
7970 clean their microdescriptor caches. Needed to resolve bug 2230.
7971 - When an HTTPS proxy reports "403 Forbidden", we now explain
7972 what it means rather than calling it an unexpected status code.
7973 Closes bug 2503. Patch from Michael Yakubovich.
7974 - Update to the May 1 2011 Maxmind GeoLite Country database.
7977 - Authorities now clean their microdesc cache periodically and when
7978 reading from disk initially, not only when adding new descriptors.
7979 This prevents a bug where we could lose microdescriptors. Bugfix
7980 on 0.2.2.6-alpha. Fixes bug 2230.
7981 - Do not crash when our configuration file becomes unreadable, for
7982 example due to a permissions change, between when we start up
7983 and when a controller calls SAVECONF. Fixes bug 3135; bugfix
7985 - Avoid a bug that would keep us from replacing a microdescriptor
7986 cache on Windows. (We would try to replace the file while still
7987 holding it open. That's fine on Unix, but Windows doesn't let us
7988 do that.) Bugfix on 0.2.2.6-alpha; bug found by wanoskarnet.
7989 - Add missing explanations for the authority-related torrc options
7990 RephistTrackTime, BridgePassword, and V3AuthUseLegacyKey in the
7991 man page. Resolves issue 2379.
7992 - As an authority, do not upload our own vote or signature set to
7993 ourself. It would tell us nothing new, and as of 0.2.2.24-alpha,
7994 it would get flagged as a duplicate. Resolves bug 3026.
7995 - Accept hidden service descriptors if we think we might be a hidden
7996 service directory, regardless of what our consensus says. This
7997 helps robustness, since clients and hidden services can sometimes
7998 have a more up-to-date view of the network consensus than we do,
7999 and if they think that the directory authorities list us a HSDir,
8000 we might actually be one. Related to bug 2732; bugfix on
8002 - When a controller changes TrackHostExits, remove mappings for
8003 hosts that should no longer have their exits tracked. Bugfix on
8005 - When a controller changes VirtualAddrNetwork, remove any mappings
8006 for hosts that were automapped to the old network. Bugfix on
8008 - When a controller changes one of the AutomapHosts* options, remove
8009 any mappings for hosts that should no longer be automapped. Bugfix
8011 - Do not reset the bridge descriptor download status every time we
8012 re-parse our configuration or get a configuration change. Fixes
8013 bug 3019; bugfix on 0.2.0.3-alpha.
8015 o Minor bugfixes (code cleanup):
8016 - When loading the microdesc journal, remember its current size.
8017 In 0.2.2, this helps prevent the microdesc journal from growing
8018 without limit on authorities (who are the only ones to use it in
8019 0.2.2). Fixes a part of bug 2230; bugfix on 0.2.2.6-alpha.
8020 Fix posted by "cypherpunks."
8021 - The microdesc journal is supposed to get rebuilt only if it is
8022 at least _half_ the length of the store, not _twice_ the length
8023 of the store. Bugfix on 0.2.2.6-alpha; fixes part of bug 2230.
8024 - Fix a potential null-pointer dereference while computing a
8025 consensus. Bugfix on tor-0.2.0.3-alpha, found with the help of
8027 - Avoid a possible null-pointer dereference when rebuilding the mdesc
8028 cache without actually having any descriptors to cache. Bugfix on
8029 0.2.2.6-alpha. Issue discovered using clang's static analyzer.
8030 - If we fail to compute the identity digest of a v3 legacy keypair,
8031 warn, and don't use a buffer-full of junk instead. Bugfix on
8032 0.2.1.1-alpha; fixes bug 3106.
8033 - Resolve an untriggerable issue in smartlist_string_num_isin(),
8034 where if the function had ever in the future been used to check
8035 for the presence of a too-large number, it would have given an
8036 incorrect result. (Fortunately, we only used it for 16-bit
8037 values.) Fixes bug 3175; bugfix on 0.1.0.1-rc.
8038 - Require that introduction point keys and onion handshake keys
8039 have a public exponent of 65537. Starts to fix bug 3207; bugfix
8043 - Caches no longer download and serve v2 networkstatus documents
8044 unless FetchV2Networkstatus flag is set: these documents haven't
8045 haven't been used by clients or relays since 0.2.0.x. Resolves
8049 Changes in version 0.2.3.1-alpha - 2011-05-05
8050 Tor 0.2.3.1-alpha adds some new experimental features, including support
8051 for an improved network IO backend, IOCP networking on Windows,
8052 microdescriptor caching, "fast-start" support for streams, and automatic
8053 home router configuration. There are also numerous internal improvements
8054 to try to make the code easier for developers to work with.
8056 This is the first alpha release in a new series, so expect there to be
8057 bugs. Users who would rather test out a more stable branch should
8058 stay with 0.2.2.x for now.
8061 - Tor can now optionally build with the "bufferevents" buffered IO
8062 backend provided by Libevent 2. To use this feature, make sure you
8063 have the latest possible version of Libevent, and pass the
8064 --enable-bufferevents flag to configure when building Tor from
8065 source. This feature will make our networking code more flexible,
8066 let us stack layers on each other, and let us use more efficient
8067 zero-copy transports where available.
8068 - As an experimental feature, Tor can use IOCP for networking on Windows.
8069 Once this code is tuned and optimized, it promises much better
8070 performance than the select-based backend we've used in the past. To
8071 try this feature, you must build Tor with Libevent 2, configure Tor
8072 with the "bufferevents" buffered IO backend, and add "DisableIOCP 0" to
8073 your torrc. There are known bugs here: only try this if you can help
8074 debug it as it breaks.
8075 - The EntryNodes option can now include country codes like {de} or IP
8076 addresses or network masks. Previously we had disallowed these options
8077 because we didn't have an efficient way to keep the list up to
8078 date. Fixes bug 1982, but see bug 2798 for an unresolved issue here.
8079 - Exit nodes now accept and queue data on not-yet-connected streams.
8080 Previously, the client wasn't allowed to send data until the stream was
8081 connected, which slowed down all connections. This change will enable
8082 clients to perform a "fast-start" on streams and send data without
8083 having to wait for a confirmation that the stream has opened. (Patch
8084 from Ian Goldberg; implements the server side of Proposal 174.)
8085 - Tor now has initial support for automatic port mapping on the many
8086 home routers that support NAT-PMP or UPnP. (Not yet supported on
8087 Windows). To build the support code, you'll need to have libnatpnp
8088 library and/or the libminiupnpc library, and you'll need to enable the
8089 feature specifically by passing "--enable-upnp" and/or
8090 "--enable-natpnp" to configure. To turn it on, use the new
8091 PortForwarding option.
8092 - Caches now download, cache, and serve multiple "flavors" of the
8093 consensus, including a flavor that describes microdescriptors.
8094 - Caches now download, cache, and serve microdescriptors -- small
8095 summaries of router descriptors that are authenticated by all of the
8096 directory authorities. Once enough caches are running this code,
8097 clients will be able to save significant amounts of directory bandwidth
8098 by downloading microdescriptors instead of router descriptors.
8101 - Make logging resolution configurable with a new LogTimeGranularity
8102 option, and change the default from 1 millisecond to 1 second.
8103 Implements enhancement 1668.
8104 - We log which torrc file we're using on startup. Implements ticket
8106 - Ordinarily, Tor does not count traffic from private addresses (like
8107 127.0.0.1 or 10.0.0.1) when calculating rate limits or accounting.
8108 There is now a new option, CountPrivateBandwidth, to disable this
8109 behavior. Patch from Daniel Cagara.
8110 - New --enable-static-tor configure option for building Tor as
8111 statically as possible. Idea, general hackery and thoughts from
8112 Alexei Czeskis, John Gilmore, Jacob Appelbaum. Implements ticket
8114 - If you set the NumCPUs option to 0, Tor will now try to detect how
8115 many CPUs you have. This is the new default behavior.
8116 - Turn on directory request statistics by default and include them in
8117 extra-info descriptors. Don't break if we have no GeoIP database.
8118 - Relays that set "ConnDirectionStatistics 1" write statistics on the
8119 bidirectional use of connections to disk every 24 hours.
8120 - Add a GeoIP file digest to the extra-info descriptor. Implements
8122 - The NodeFamily option -- which let you declare that you want to
8123 consider nodes to be part of a family whether they list themselves
8124 that way or not -- now allows IP address ranges and country codes.
8125 - Add a new 'Heartbeat' log message type to periodically log a message
8126 describing Tor's status at level Notice. This feature is meant for
8127 operators who log at notice, and want to make sure that their Tor
8128 server is still working. Implementation by George Kadianakis.
8130 o Minor bugfixes (on 0.2.2.25-alpha):
8131 - When loading the microdesc journal, remember its current size.
8132 In 0.2.2, this helps prevent the microdesc journal from growing
8133 without limit on authorities (who are the only ones to use it in
8134 0.2.2). Fixes a part of bug 2230; bugfix on 0.2.2.6-alpha.
8135 Fix posted by "cypherpunks."
8136 - The microdesc journal is supposed to get rebuilt only if it is
8137 at least _half_ the length of the store, not _twice_ the length
8138 of the store. Bugfix on 0.2.2.6-alpha; fixes part of bug 2230.
8139 - If as an authority we fail to compute the identity digest of a v3
8140 legacy keypair, warn, and don't use a buffer-full of junk instead.
8141 Bugfix on 0.2.1.1-alpha; fixes bug 3106.
8142 - Authorities now clean their microdesc cache periodically and when
8143 reading from disk initially, not only when adding new descriptors.
8144 This prevents a bug where we could lose microdescriptors. Bugfix
8147 o Minor features (controller):
8148 - Add a new SIGNAL event to the controller interface so that
8149 controllers can be notified when Tor handles a signal. Resolves
8150 issue 1955. Patch by John Brooks.
8151 - Add a new GETINFO option to get total bytes read and written. Patch
8152 from pipe, revised by atagar. Resolves ticket 2345.
8153 - Implement some GETINFO controller fields to provide information about
8154 the Tor process's pid, euid, username, and resource limits.
8157 - Our build system requires automake 1.6 or later to create the
8158 Makefile.in files. Previously, you could have used 1.4.
8159 This only affects developers and people building Tor from git;
8160 people who build Tor from the source distribution without changing
8161 the Makefile.am files should be fine.
8162 - Our autogen.sh script uses autoreconf to launch autoconf, automake, and
8163 so on. This is more robust against some of the failure modes
8164 associated with running the autotools pieces on their own.
8166 o Minor packaging issues:
8167 - On OpenSUSE, create the /var/run/tor directory on startup if it is not
8168 already created. Patch from Andreas Stieger. Fixes bug 2573.
8170 o Code simplifications and refactoring:
8171 - A major revision to our internal node-selecting and listing logic.
8172 Tor already had at least two major ways to look at the question of
8173 "which Tor servers do we know about": a list of router descriptors,
8174 and a list of entries in the current consensus. With
8175 microdescriptors, we're adding a third. Having so many systems
8176 without an abstraction layer over them was hurting the codebase.
8177 Now, we have a new "node_t" abstraction that presents a consistent
8178 interface to a client's view of a Tor node, and holds (nearly) all
8179 of the mutable state formerly in routerinfo_t and routerstatus_t.
8180 - The helper programs tor-gencert, tor-resolve, and tor-checkkey
8181 no longer link against Libevent: they never used it, but
8182 our library structure used to force them to link it.
8185 - Remove some old code to work around even older versions of Tor that
8186 used forked processes to handle DNS requests. Such versions of Tor
8187 are no longer in use as servers.
8189 o Documentation fixes:
8190 - Correct a broken faq link in the INSTALL file. Fixes bug 2307.
8191 - Add missing documentation for the authority-related torrc options
8192 RephistTrackTime, BridgePassword, and V3AuthUseLegacyKey. Resolves
8196 Changes in version 0.2.2.25-alpha - 2011-04-29
8197 Tor 0.2.2.25-alpha fixes many bugs: hidden service clients are more
8198 robust, routers no longer overreport their bandwidth, Win7 should crash
8199 a little less, and NEWNYM (as used by Vidalia's "new identity" button)
8200 now prevents hidden service-related activity from being linkable. It
8201 provides more information to Vidalia so you can see if your bridge is
8202 working. Also, 0.2.2.25-alpha revamps the Entry/Exit/ExcludeNodes and
8203 StrictNodes configuration options to make them more reliable, more
8204 understandable, and more regularly applied. If you use those options,
8205 please see the revised documentation for them in the manual page.
8208 - Relays were publishing grossly inflated bandwidth values because
8209 they were writing their state files wrong--now they write the
8210 correct value. Also, resume reading bandwidth history from the
8211 state file correctly. Fixes bug 2704; bugfix on 0.2.2.23-alpha.
8212 - Improve hidden service robustness: When we find that we have
8213 extended a hidden service's introduction circuit to a relay not
8214 listed as an introduction point in the HS descriptor we currently
8215 have, retry with an introduction point from the current
8216 descriptor. Previously we would just give up. Fixes bugs 1024 and
8217 1930; bugfix on 0.2.0.10-alpha.
8218 - Clients now stop trying to use an exit node associated with a given
8219 destination by TrackHostExits if they fail to reach that exit node.
8220 Fixes bug 2999. Bugfix on 0.2.0.20-rc.
8221 - Fix crash bug on platforms where gmtime and localtime can return
8222 NULL. Windows 7 users were running into this one. Fixes part of bug
8223 2077. Bugfix on all versions of Tor. Found by boboper.
8225 o Security and stability fixes:
8226 - Don't double-free a parsable, but invalid, microdescriptor, even if
8227 it is followed in the blob we're parsing by an unparsable
8228 microdescriptor. Fixes an issue reported in a comment on bug 2954.
8229 Bugfix on 0.2.2.6-alpha; fix by "cypherpunks".
8230 - If the Nickname configuration option isn't given, Tor would pick a
8231 nickname based on the local hostname as the nickname for a relay.
8232 Because nicknames are not very important in today's Tor and the
8233 "Unnamed" nickname has been implemented, this is now problematic
8234 behavior: It leaks information about the hostname without being
8235 useful at all. Fixes bug 2979; bugfix on 0.1.2.2-alpha, which
8236 introduced the Unnamed nickname. Reported by tagnaq.
8237 - Fix an uncommon assertion failure when running with DNSPort under
8238 heavy load. Fixes bug 2933; bugfix on 0.2.0.1-alpha.
8239 - Avoid linkability based on cached hidden service descriptors: forget
8240 all hidden service descriptors cached as a client when processing a
8241 SIGNAL NEWNYM command. Fixes bug 3000; bugfix on 0.0.6.
8244 - Export GeoIP information on bridge usage to controllers even if we
8245 have not yet been running for 24 hours. Now Vidalia bridge operators
8246 can get more accurate and immediate feedback about their
8247 contributions to the network.
8249 o Major features and bugfixes (node selection):
8250 - Revise and reconcile the meaning of the ExitNodes, EntryNodes,
8251 ExcludeEntryNodes, ExcludeExitNodes, ExcludeNodes, and StrictNodes
8252 options. Previously, we had been ambiguous in describing what
8253 counted as an "exit" node, and what operations exactly "StrictNodes
8254 0" would permit. This created confusion when people saw nodes built
8255 through unexpected circuits, and made it hard to tell real bugs from
8256 surprises. Now the intended behavior is:
8257 . "Exit", in the context of ExitNodes and ExcludeExitNodes, means
8258 a node that delivers user traffic outside the Tor network.
8259 . "Entry", in the context of EntryNodes, means a node used as the
8260 first hop of a multihop circuit. It doesn't include direct
8261 connections to directory servers.
8262 . "ExcludeNodes" applies to all nodes.
8263 . "StrictNodes" changes the behavior of ExcludeNodes only. When
8264 StrictNodes is set, Tor should avoid all nodes listed in
8265 ExcludeNodes, even when it will make user requests fail. When
8266 StrictNodes is *not* set, then Tor should follow ExcludeNodes
8267 whenever it can, except when it must use an excluded node to
8268 perform self-tests, connect to a hidden service, provide a
8269 hidden service, fulfill a .exit request, upload directory
8270 information, or fetch directory information.
8271 Collectively, the changes to implement the behavior fix bug 1090.
8272 - ExcludeNodes now takes precedence over EntryNodes and ExitNodes: if
8273 a node is listed in both, it's treated as excluded.
8274 - ExcludeNodes now applies to directory nodes -- as a preference if
8275 StrictNodes is 0, or an absolute requirement if StrictNodes is 1.
8276 Don't exclude all the directory authorities and set StrictNodes to 1
8277 unless you really want your Tor to break.
8278 - ExcludeNodes and ExcludeExitNodes now override exit enclaving.
8279 - ExcludeExitNodes now overrides .exit requests.
8280 - We don't use bridges listed in ExcludeNodes.
8281 - When StrictNodes is 1:
8282 . We now apply ExcludeNodes to hidden service introduction points
8283 and to rendezvous points selected by hidden service users. This
8284 can make your hidden service less reliable: use it with caution!
8285 . If we have used ExcludeNodes on ourself, do not try relay
8286 reachability self-tests.
8287 . If we have excluded all the directory authorities, we will not
8288 even try to upload our descriptor if we're a relay.
8289 . Do not honor .exit requests to an excluded node.
8290 - Remove a misfeature that caused us to ignore the Fast/Stable flags
8291 when ExitNodes is set. Bugfix on 0.2.2.7-alpha.
8292 - When the set of permitted nodes changes, we now remove any mappings
8293 introduced via TrackExitHosts to now-excluded nodes. Bugfix on
8295 - We never cannibalize a circuit that had excluded nodes on it, even
8296 if StrictNodes is 0. Bugfix on 0.1.0.1-rc.
8297 - Revert a change where we would be laxer about attaching streams to
8298 circuits than when building the circuits. This was meant to prevent
8299 a set of bugs where streams were never attachable, but our improved
8300 code here should make this unnecessary. Bugfix on 0.2.2.7-alpha.
8301 - Keep track of how many times we launch a new circuit to handle a
8302 given stream. Too many launches could indicate an inconsistency
8303 between our "launch a circuit to handle this stream" logic and our
8304 "attach this stream to one of the available circuits" logic.
8305 - Improve log messages related to excluded nodes.
8308 - Fix a spurious warning when moving from a short month to a long
8309 month on relays with month-based BandwidthAccounting. Bugfix on
8310 0.2.2.17-alpha; fixes bug 3020.
8311 - When a client finds that an origin circuit has run out of 16-bit
8312 stream IDs, we now mark it as unusable for new streams. Previously,
8313 we would try to close the entire circuit. Bugfix on 0.0.6.
8314 - Add a forgotten cast that caused a compile warning on OS X 10.6.
8315 Bugfix on 0.2.2.24-alpha.
8316 - Be more careful about reporting the correct error from a failed
8317 connect() system call. Under some circumstances, it was possible to
8318 look at an incorrect value for errno when sending the end reason.
8319 Bugfix on 0.1.0.1-rc.
8320 - Correctly handle an "impossible" overflow cases in connection byte
8321 counting, where we write or read more than 4GB on an edge connection
8322 in a single second. Bugfix on 0.1.2.8-beta.
8323 - Correct the warning displayed when a rendezvous descriptor exceeds
8324 the maximum size. Fixes bug 2750; bugfix on 0.2.1.5-alpha. Found by
8326 - Clients and hidden services now use HSDir-flagged relays for hidden
8327 service descriptor downloads and uploads even if the relays have no
8328 DirPort set and the client has disabled TunnelDirConns. This will
8329 eventually allow us to give the HSDir flag to relays with no
8330 DirPort. Fixes bug 2722; bugfix on 0.2.1.6-alpha.
8331 - Downgrade "no current certificates known for authority" message from
8332 Notice to Info. Fixes bug 2899; bugfix on 0.2.0.10-alpha.
8333 - Make the SIGNAL DUMP control-port command work on FreeBSD. Fixes bug
8334 2917. Bugfix on 0.1.1.1-alpha.
8335 - Only limit the lengths of single HS descriptors, even when multiple
8336 HS descriptors are published to an HSDir relay in a single POST
8337 operation. Fixes bug 2948; bugfix on 0.2.1.5-alpha. Found by hsdir.
8338 - Write the current time into the LastWritten line in our state file,
8339 rather than the time from the previous write attempt. Also, stop
8340 trying to use a time of -1 in our log statements. Fixes bug 3039;
8341 bugfix on 0.2.2.14-alpha.
8342 - Be more consistent in our treatment of file system paths. "~" should
8343 get expanded to the user's home directory in the Log config option.
8344 Fixes bug 2971; bugfix on 0.2.0.1-alpha, which introduced the
8345 feature for the -f and --DataDirectory options.
8348 - Make sure every relay writes a state file at least every 12 hours.
8349 Previously, a relay could go for weeks without writing its state
8350 file, and on a crash could lose its bandwidth history, capacity
8351 estimates, client country statistics, and so on. Addresses bug 3012.
8352 - Send END_STREAM_REASON_NOROUTE in response to EHOSTUNREACH errors.
8353 Clients before 0.2.1.27 didn't handle NOROUTE correctly, but such
8354 clients are already deprecated because of security bugs.
8355 - Don't allow v0 hidden service authorities to act as clients.
8356 Required by fix for bug 3000.
8357 - Ignore SIGNAL NEWNYM commands on relay-only Tor instances. Required
8358 by fix for bug 3000.
8359 - Ensure that no empty [dirreq-](read|write)-history lines are added
8360 to an extrainfo document. Implements ticket 2497.
8362 o Code simplification and refactoring:
8363 - Remove workaround code to handle directory responses from servers
8364 that had bug 539 (they would send HTTP status 503 responses _and_
8365 send a body too). Since only server versions before
8366 0.2.0.16-alpha/0.1.2.19 were affected, there is no longer reason to
8367 keep the workaround in place.
8368 - Remove the old 'fuzzy time' logic. It was supposed to be used for
8369 handling calculations where we have a known amount of clock skew and
8370 an allowed amount of unknown skew. But we only used it in three
8371 places, and we never adjusted the known/unknown skew values. This is
8372 still something we might want to do someday, but if we do, we'll
8373 want to do it differently.
8374 - Avoid signed/unsigned comparisons by making SIZE_T_CEILING unsigned.
8375 None of the cases where we did this before were wrong, but by making
8376 this change we avoid warnings. Fixes bug 2475; bugfix on 0.2.1.28.
8377 - Use GetTempDir to find the proper temporary directory location on
8378 Windows when generating temporary files for the unit tests. Patch by
8382 Changes in version 0.2.2.24-alpha - 2011-04-08
8383 Tor 0.2.2.24-alpha fixes a variety of bugs, including a big bug that
8384 prevented Tor clients from effectively using "multihomed" bridges,
8385 that is, bridges that listen on multiple ports or IP addresses so users
8386 can continue to use some of their addresses even if others get blocked.
8389 - Fix a bug where bridge users who configure the non-canonical
8390 address of a bridge automatically switch to its canonical
8391 address. If a bridge listens at more than one address, it should be
8392 able to advertise those addresses independently and any non-blocked
8393 addresses should continue to work. Bugfix on Tor 0.2.0.x. Fixes
8395 - If you configured Tor to use bridge A, and then quit and
8396 configured Tor to use bridge B instead, it would happily continue
8397 to use bridge A if it's still reachable. While this behavior is
8398 a feature if your goal is connectivity, in some scenarios it's a
8399 dangerous bug. Bugfix on Tor 0.2.0.1-alpha; fixes bug 2511.
8400 - Directory authorities now use data collected from their own
8401 uptime observations when choosing whether to assign the HSDir flag
8402 to relays, instead of trusting the uptime value the relay reports in
8403 its descriptor. This change helps prevent an attack where a small
8404 set of nodes with frequently-changing identity keys can blackhole
8405 a hidden service. (Only authorities need upgrade; others will be
8406 fine once they do.) Bugfix on 0.2.0.10-alpha; fixes bug 2709.
8409 - When we restart our relay, we might get a successful connection
8410 from the outside before we've started our reachability tests,
8411 triggering a warning: "ORPort found reachable, but I have no
8412 routerinfo yet. Failing to inform controller of success." This
8413 bug was harmless unless Tor is running under a controller
8414 like Vidalia, in which case the controller would never get a
8415 REACHABILITY_SUCCEEDED status event. Bugfix on 0.1.2.6-alpha;
8417 - Make directory authorities more accurate at recording when
8418 relays that have failed several reachability tests became
8419 unreachable, so we can provide more accuracy at assigning Stable,
8420 Guard, HSDir, etc flags. Bugfix on 0.2.0.6-alpha. Resolves bug 2716.
8421 - Fix an issue that prevented static linking of libevent on
8422 some platforms (notably Linux). Fixes bug 2698; bugfix on
8423 versions 0.2.1.23/0.2.2.8-alpha (the versions introducing
8424 the --with-static-libevent configure option).
8425 - We now ask the other side of a stream (the client or the exit)
8426 for more data on that stream when the amount of queued data on
8427 that stream dips low enough. Previously, we wouldn't ask the
8428 other side for more data until either it sent us more data (which
8429 it wasn't supposed to do if it had exhausted its window!) or we
8430 had completely flushed all our queued data. This flow control fix
8431 should improve throughput. Fixes bug 2756; bugfix on the earliest
8432 released versions of Tor (svn commit r152).
8433 - Avoid a double-mark-for-free warning when failing to attach a
8434 transparent proxy connection. (We thought we had fixed this in
8435 0.2.2.23-alpha, but it turns out our fix was checking the wrong
8436 connection.) Fixes bug 2757; bugfix on 0.1.2.1-alpha (the original
8437 bug) and 0.2.2.23-alpha (the incorrect fix).
8438 - When warning about missing zlib development packages during compile,
8439 give the correct package names. Bugfix on 0.2.0.1-alpha.
8442 - Directory authorities now log the source of a rejected POSTed v3
8444 - Make compilation with clang possible when using
8445 --enable-gcc-warnings by removing two warning options that clang
8446 hasn't implemented yet and by fixing a few warnings. Implements
8448 - When expiring circuits, use microsecond timers rather than
8449 one-second timers. This can avoid an unpleasant situation where a
8450 circuit is launched near the end of one second and expired right
8451 near the beginning of the next, and prevent fluctuations in circuit
8453 - Use computed circuit-build timeouts to decide when to launch
8454 parallel introduction circuits for hidden services. (Previously,
8455 we would retry after 15 seconds.)
8456 - Update to the April 1 2011 Maxmind GeoLite Country database.
8459 - Create the /var/run/tor directory on startup on OpenSUSE if it is
8460 not already created. Patch from Andreas Stieger. Fixes bug 2573.
8462 o Documentation changes:
8463 - Modernize the doxygen configuration file slightly. Fixes bug 2707.
8464 - Resolve all doxygen warnings except those for missing documentation.
8466 - Add doxygen documentation for more functions, fields, and types.
8469 Changes in version 0.2.2.23-alpha - 2011-03-08
8470 Tor 0.2.2.23-alpha lets relays record their bandwidth history so when
8471 they restart they don't lose their bandwidth capacity estimate. This
8472 release also fixes a diverse set of user-facing bugs, ranging from
8473 relays overrunning their rate limiting to clients falsely warning about
8474 clock skew to bridge descriptor leaks by our bridge directory authority.
8477 - Stop sending a CLOCK_SKEW controller status event whenever
8478 we fetch directory information from a relay that has a wrong clock.
8479 Instead, only inform the controller when it's a trusted authority
8480 that claims our clock is wrong. Bugfix on 0.1.2.6-alpha; fixes
8481 the rest of bug 1074.
8482 - Fix an assert in parsing router descriptors containing IPv6
8483 addresses. This one took down the directory authorities when
8484 somebody tried some experimental code. Bugfix on 0.2.1.3-alpha.
8485 - Make the bridge directory authority refuse to answer directory
8486 requests for "all" descriptors. It used to include bridge
8487 descriptors in its answer, which was a major information leak.
8488 Found by "piebeer". Bugfix on 0.2.0.3-alpha.
8489 - If relays set RelayBandwidthBurst but not RelayBandwidthRate,
8490 Tor would ignore their RelayBandwidthBurst setting,
8491 potentially using more bandwidth than expected. Bugfix on
8492 0.2.0.1-alpha. Reported by Paul Wouters. Fixes bug 2470.
8493 - Ignore and warn if the user mistakenly sets "PublishServerDescriptor
8494 hidserv" in her torrc. The 'hidserv' argument never controlled
8495 publication of hidden service descriptors. Bugfix on 0.2.0.1-alpha.
8498 - Relays now save observed peak bandwidth throughput rates to their
8499 state file (along with total usage, which was already saved)
8500 so that they can determine their correct estimated bandwidth on
8501 restart. Resolves bug 1863, where Tor relays would reset their
8502 estimated bandwidth to 0 after restarting.
8503 - Directory authorities now take changes in router IP address and
8504 ORPort into account when determining router stability. Previously,
8505 if a router changed its IP or ORPort, the authorities would not
8506 treat it as having any downtime for the purposes of stability
8507 calculation, whereas clients would experience downtime since the
8508 change could take a while to propagate to them. Resolves issue 1035.
8509 - Enable Address Space Layout Randomization (ASLR) and Data Execution
8510 Prevention (DEP) by default on Windows to make it harder for
8511 attackers to exploit vulnerabilities. Patch from John Brooks.
8513 o Minor bugfixes (on 0.2.1.x and earlier):
8514 - Fix a rare crash bug that could occur when a client was configured
8515 with a large number of bridges. Fixes bug 2629; bugfix on
8516 0.2.1.2-alpha. Bugfix by trac user "shitlei".
8517 - Avoid a double mark-for-free warning when failing to attach a
8518 transparent proxy connection. Bugfix on 0.1.2.1-alpha. Fixes
8520 - Correctly detect failure to allocate an OpenSSL BIO. Fixes bug 2378;
8521 found by "cypherpunks". This bug was introduced before the first
8522 Tor release, in svn commit r110.
8523 - Country codes aren't supported in EntryNodes until 0.2.3.x, so
8524 don't mention them in the manpage. Fixes bug 2450; issue
8525 spotted by keb and G-Lo.
8526 - Fix a bug in bandwidth history state parsing that could have been
8527 triggered if a future version of Tor ever changed the timing
8528 granularity at which bandwidth history is measured. Bugfix on
8530 - When a relay decides that its DNS is too broken for it to serve
8531 as an exit server, it advertised itself as a non-exit, but
8532 continued to act as an exit. This could create accidental
8533 partitioning opportunities for users. Instead, if a relay is
8534 going to advertise reject *:* as its exit policy, it should
8535 really act with exit policy "reject *:*". Fixes bug 2366.
8536 Bugfix on Tor 0.1.2.5-alpha. Bugfix by user "postman" on trac.
8537 - In the special case where you configure a public exit relay as your
8538 bridge, Tor would be willing to use that exit relay as the last
8539 hop in your circuit as well. Now we fail that circuit instead.
8540 Bugfix on 0.2.0.12-alpha. Fixes bug 2403. Reported by "piebeer".
8541 - Fix a bug with our locking implementation on Windows that couldn't
8542 correctly detect when a file was already locked. Fixes bug 2504,
8543 bugfix on 0.2.1.6-alpha.
8544 - Fix IPv6-related connect() failures on some platforms (BSD, OS X).
8545 Bugfix on 0.2.0.3-alpha; fixes first part of bug 2660. Patch by
8547 - Set target port in get_interface_address6() correctly. Bugfix
8548 on 0.1.1.4-alpha and 0.2.0.3-alpha; fixes second part of bug 2660.
8549 - Directory authorities are now more robust to hops back in time
8550 when calculating router stability. Previously, if a run of uptime
8551 or downtime appeared to be negative, the calculation could give
8552 incorrect results. Bugfix on 0.2.0.6-alpha; noticed when fixing
8554 - Fix an assert that got triggered when using the TestingTorNetwork
8555 configuration option and then issuing a GETINFO config-text control
8556 command. Fixes bug 2250; bugfix on 0.2.1.2-alpha.
8558 o Minor bugfixes (on 0.2.2.x):
8559 - Clients should not weight BadExit nodes as Exits in their node
8560 selection. Similarly, directory authorities should not count BadExit
8561 bandwidth as Exit bandwidth when computing bandwidth-weights.
8562 Bugfix on 0.2.2.10-alpha; fixes bug 2203.
8563 - Correctly clear our dir_read/dir_write history when there is an
8564 error parsing any bw history value from the state file. Bugfix on
8566 - Resolve a bug in verifying signatures of directory objects
8567 with digests longer than SHA1. Bugfix on 0.2.2.20-alpha.
8568 Fixes bug 2409. Found by "piebeer".
8569 - Bridge authorities no longer crash on SIGHUP when they try to
8570 publish their relay descriptor to themselves. Fixes bug 2572. Bugfix
8574 - Log less aggressively about circuit timeout changes, and improve
8575 some other circuit timeout messages. Resolves bug 2004.
8576 - Log a little more clearly about the times at which we're no longer
8577 accepting new connections. Resolves bug 2181.
8578 - Reject attempts at the client side to open connections to private
8579 IP addresses (like 127.0.0.1, 10.0.0.1, and so on) with
8580 a randomly chosen exit node. Attempts to do so are always
8581 ill-defined, generally prevented by exit policies, and usually
8582 in error. This will also help to detect loops in transparent
8583 proxy configurations. You can disable this feature by setting
8584 "ClientRejectInternalAddresses 0" in your torrc.
8585 - Always treat failure to allocate an RSA key as an unrecoverable
8587 - Update to the March 1 2011 Maxmind GeoLite Country database.
8589 o Minor features (log subsystem):
8590 - Add documentation for configuring logging at different severities in
8591 different log domains. We've had this feature since 0.2.1.1-alpha,
8592 but for some reason it never made it into the manpage. Fixes
8594 - Make it simpler to specify "All log domains except for A and B".
8595 Previously you needed to say "[*,~A,~B]". Now you can just say
8597 - Add a "LogMessageDomains 1" option to include the domains of log
8598 messages along with the messages. Without this, there's no way
8599 to use log domains without reading the source or doing a lot
8602 o Packaging changes:
8603 - Stop shipping the Tor specs files and development proposal documents
8604 in the tarball. They are now in a separate git repository at
8605 git://git.torproject.org/torspec.git
8608 Changes in version 0.2.1.30 - 2011-02-23
8609 Tor 0.2.1.30 fixes a variety of less critical bugs. The main other
8610 change is a slight tweak to Tor's TLS handshake that makes relays
8611 and bridges that run this new version reachable from Iran again.
8612 We don't expect this tweak will win the arms race long-term, but it
8613 buys us time until we roll out a better solution.
8616 - Stop sending a CLOCK_SKEW controller status event whenever
8617 we fetch directory information from a relay that has a wrong clock.
8618 Instead, only inform the controller when it's a trusted authority
8619 that claims our clock is wrong. Bugfix on 0.1.2.6-alpha; fixes
8620 the rest of bug 1074.
8621 - Fix a bounds-checking error that could allow an attacker to
8622 remotely crash a directory authority. Bugfix on 0.2.1.5-alpha.
8624 - If relays set RelayBandwidthBurst but not RelayBandwidthRate,
8625 Tor would ignore their RelayBandwidthBurst setting,
8626 potentially using more bandwidth than expected. Bugfix on
8627 0.2.0.1-alpha. Reported by Paul Wouters. Fixes bug 2470.
8628 - Ignore and warn if the user mistakenly sets "PublishServerDescriptor
8629 hidserv" in her torrc. The 'hidserv' argument never controlled
8630 publication of hidden service descriptors. Bugfix on 0.2.0.1-alpha.
8633 - Adjust our TLS Diffie-Hellman parameters to match those used by
8635 - Update to the February 1 2011 Maxmind GeoLite Country database.
8638 - Check for and reject overly long directory certificates and
8639 directory tokens before they have a chance to hit any assertions.
8640 Bugfix on 0.2.1.28. Found by "doorss".
8641 - Bring the logic that gathers routerinfos and assesses the
8642 acceptability of circuits into line. This prevents a Tor OP from
8643 getting locked in a cycle of choosing its local OR as an exit for a
8644 path (due to a .exit request) and then rejecting the circuit because
8645 its OR is not listed yet. It also prevents Tor clients from using an
8646 OR running in the same instance as an exit (due to a .exit request)
8647 if the OR does not meet the same requirements expected of an OR
8648 running elsewhere. Fixes bug 1859; bugfix on 0.1.0.1-rc.
8650 o Packaging changes:
8651 - Stop shipping the Tor specs files and development proposal documents
8652 in the tarball. They are now in a separate git repository at
8653 git://git.torproject.org/torspec.git
8654 - Do not include Git version tags as though they are SVN tags when
8655 generating a tarball from inside a repository that has switched
8656 between branches. Bugfix on 0.2.1.15-rc; fixes bug 2402.
8659 Changes in version 0.2.2.22-alpha - 2011-01-25
8660 Tor 0.2.2.22-alpha fixes a few more less-critical security issues. The
8661 main other change is a slight tweak to Tor's TLS handshake that makes
8662 relays and bridges that run this new version reachable from Iran again.
8663 We don't expect this tweak will win the arms race long-term, but it
8664 will buy us a bit more time until we roll out a better solution.
8667 - Fix a bounds-checking error that could allow an attacker to
8668 remotely crash a directory authority. Bugfix on 0.2.1.5-alpha.
8670 - Don't assert when changing from bridge to relay or vice versa
8671 via the controller. The assert happened because we didn't properly
8672 initialize our keys in this case. Bugfix on 0.2.2.18-alpha; fixes
8673 bug 2433. Reported by bastik.
8676 - Adjust our TLS Diffie-Hellman parameters to match those used by
8678 - Provide a log message stating which geoip file we're parsing
8679 instead of just stating that we're parsing the geoip file.
8680 Implements ticket 2432.
8683 - Check for and reject overly long directory certificates and
8684 directory tokens before they have a chance to hit any assertions.
8685 Bugfix on 0.2.1.28 / 0.2.2.20-alpha. Found by "doorss".
8688 Changes in version 0.2.2.21-alpha - 2011-01-15
8689 Tor 0.2.2.21-alpha includes all the patches from Tor 0.2.1.29, which
8690 continues our recent code security audit work. The main fix resolves
8691 a remote heap overflow vulnerability that can allow remote code
8692 execution (CVE-2011-0427). Other fixes address a variety of assert
8693 and crash bugs, most of which we think are hard to exploit remotely.
8695 o Major bugfixes (security), also included in 0.2.1.29:
8696 - Fix a heap overflow bug where an adversary could cause heap
8697 corruption. This bug probably allows remote code execution
8698 attacks. Reported by "debuger". Fixes CVE-2011-0427. Bugfix on
8700 - Prevent a denial-of-service attack by disallowing any
8701 zlib-compressed data whose compression factor is implausibly
8702 high. Fixes part of bug 2324; reported by "doorss".
8703 - Zero out a few more keys in memory before freeing them. Fixes
8704 bug 2384 and part of bug 2385. These key instances found by
8705 "cypherpunks", based on Andrew Case's report about being able
8706 to find sensitive data in Tor's memory space if you have enough
8707 permissions. Bugfix on 0.0.2pre9.
8709 o Major bugfixes (crashes), also included in 0.2.1.29:
8710 - Prevent calls to Libevent from inside Libevent log handlers.
8711 This had potential to cause a nasty set of crashes, especially
8712 if running Libevent with debug logging enabled, and running
8713 Tor with a controller watching for low-severity log messages.
8714 Bugfix on 0.1.0.2-rc. Fixes bug 2190.
8715 - Add a check for SIZE_T_MAX to tor_realloc() to try to avoid
8716 underflow errors there too. Fixes the other part of bug 2324.
8717 - Fix a bug where we would assert if we ever had a
8718 cached-descriptors.new file (or another file read directly into
8719 memory) of exactly SIZE_T_CEILING bytes. Fixes bug 2326; bugfix
8720 on 0.2.1.25. Found by doorss.
8721 - Fix some potential asserts and parsing issues with grossly
8722 malformed router caches. Fixes bug 2352; bugfix on Tor 0.2.1.27.
8725 o Minor bugfixes (other), also included in 0.2.1.29:
8726 - Fix a bug with handling misformed replies to reverse DNS lookup
8727 requests in DNSPort. Bugfix on Tor 0.2.0.1-alpha. Related to a
8728 bug reported by doorss.
8729 - Fix compilation on mingw when a pthreads compatibility library
8730 has been installed. (We don't want to use it, so we shouldn't
8731 be including pthread.h.) Fixes bug 2313; bugfix on 0.1.0.1-rc.
8732 - Fix a bug where we would declare that we had run out of virtual
8733 addresses when the address space was only half-exhausted. Bugfix
8735 - Correctly handle the case where AutomapHostsOnResolve is set but
8736 no virtual addresses are available. Fixes bug 2328; bugfix on
8737 0.1.2.1-alpha. Bug found by doorss.
8738 - Correctly handle wrapping around when we run out of virtual
8739 address space. Found by cypherpunks; bugfix on 0.2.0.5-alpha.
8741 o Minor features, also included in 0.2.1.29:
8742 - Update to the January 1 2011 Maxmind GeoLite Country database.
8743 - Introduce output size checks on all of our decryption functions.
8745 o Build changes, also included in 0.2.1.29:
8746 - Tor does not build packages correctly with Automake 1.6 and earlier;
8747 added a check to Makefile.am to make sure that we're building with
8748 Automake 1.7 or later.
8749 - The 0.2.1.28 tarball was missing src/common/OpenBSD_malloc_Linux.c
8750 because we built it with a too-old version of automake. Thus that
8751 release broke ./configure --enable-openbsd-malloc, which is popular
8752 among really fast exit relays on Linux.
8754 o Major bugfixes, new in 0.2.2.21-alpha:
8755 - Prevent crash/heap corruption when the cbtnummodes consensus
8756 parameter is set to 0 or large values. Fixes bug 2317; bugfix
8759 o Major features, new in 0.2.2.21-alpha:
8760 - Introduce minimum/maximum values that clients will believe
8761 from the consensus. Now we'll have a better chance to avoid crashes
8762 or worse when a consensus param has a weird value.
8764 o Minor features, new in 0.2.2.21-alpha:
8765 - Make sure to disable DirPort if running as a bridge. DirPorts aren't
8766 used on bridges, and it makes bridge scanning somewhat easier.
8767 - If writing the state file to disk fails, wait up to an hour before
8768 retrying again, rather than trying again each second. Fixes bug
8769 2346; bugfix on Tor 0.1.1.3-alpha.
8770 - Make Libevent log messages get delivered to controllers later,
8771 and not from inside the Libevent log handler. This prevents unsafe
8772 reentrant Libevent calls while still letting the log messages
8774 - Detect platforms that brokenly use a signed size_t, and refuse to
8775 build there. Found and analyzed by doorss and rransom.
8776 - Fix a bunch of compile warnings revealed by mingw with gcc 4.5.
8779 o Minor bugfixes, new in 0.2.2.21-alpha:
8780 - Handle SOCKS messages longer than 128 bytes long correctly, rather
8781 than waiting forever for them to finish. Fixes bug 2330; bugfix
8782 on 0.2.0.16-alpha. Found by doorss.
8783 - Add assertions to check for overflow in arguments to
8784 base32_encode() and base32_decode(); fix a signed-unsigned
8785 comparison there too. These bugs are not actually reachable in Tor,
8786 but it's good to prevent future errors too. Found by doorss.
8787 - Correctly detect failures to create DNS requests when using Libevent
8788 versions before v2. (Before Libevent 2, we used our own evdns
8789 implementation. Its return values for Libevent's evdns_resolve_*()
8790 functions are not consistent with those from Libevent.) Fixes bug
8791 2363; bugfix on 0.2.2.6-alpha. Found by "lodger".
8793 o Documentation, new in 0.2.2.21-alpha:
8794 - Document the default socks host and port (127.0.0.1:9050) for
8798 Changes in version 0.2.1.29 - 2011-01-15
8799 Tor 0.2.1.29 continues our recent code security audit work. The main
8800 fix resolves a remote heap overflow vulnerability that can allow remote
8801 code execution. Other fixes address a variety of assert and crash bugs,
8802 most of which we think are hard to exploit remotely.
8804 o Major bugfixes (security):
8805 - Fix a heap overflow bug where an adversary could cause heap
8806 corruption. This bug probably allows remote code execution
8807 attacks. Reported by "debuger". Fixes CVE-2011-0427. Bugfix on
8809 - Prevent a denial-of-service attack by disallowing any
8810 zlib-compressed data whose compression factor is implausibly
8811 high. Fixes part of bug 2324; reported by "doorss".
8812 - Zero out a few more keys in memory before freeing them. Fixes
8813 bug 2384 and part of bug 2385. These key instances found by
8814 "cypherpunks", based on Andrew Case's report about being able
8815 to find sensitive data in Tor's memory space if you have enough
8816 permissions. Bugfix on 0.0.2pre9.
8818 o Major bugfixes (crashes):
8819 - Prevent calls to Libevent from inside Libevent log handlers.
8820 This had potential to cause a nasty set of crashes, especially
8821 if running Libevent with debug logging enabled, and running
8822 Tor with a controller watching for low-severity log messages.
8823 Bugfix on 0.1.0.2-rc. Fixes bug 2190.
8824 - Add a check for SIZE_T_MAX to tor_realloc() to try to avoid
8825 underflow errors there too. Fixes the other part of bug 2324.
8826 - Fix a bug where we would assert if we ever had a
8827 cached-descriptors.new file (or another file read directly into
8828 memory) of exactly SIZE_T_CEILING bytes. Fixes bug 2326; bugfix
8829 on 0.2.1.25. Found by doorss.
8830 - Fix some potential asserts and parsing issues with grossly
8831 malformed router caches. Fixes bug 2352; bugfix on Tor 0.2.1.27.
8834 o Minor bugfixes (other):
8835 - Fix a bug with handling misformed replies to reverse DNS lookup
8836 requests in DNSPort. Bugfix on Tor 0.2.0.1-alpha. Related to a
8837 bug reported by doorss.
8838 - Fix compilation on mingw when a pthreads compatibility library
8839 has been installed. (We don't want to use it, so we shouldn't
8840 be including pthread.h.) Fixes bug 2313; bugfix on 0.1.0.1-rc.
8841 - Fix a bug where we would declare that we had run out of virtual
8842 addresses when the address space was only half-exhausted. Bugfix
8844 - Correctly handle the case where AutomapHostsOnResolve is set but
8845 no virtual addresses are available. Fixes bug 2328; bugfix on
8846 0.1.2.1-alpha. Bug found by doorss.
8847 - Correctly handle wrapping around to when we run out of virtual
8848 address space. Found by cypherpunks, bugfix on 0.2.0.5-alpha.
8849 - The 0.2.1.28 tarball was missing src/common/OpenBSD_malloc_Linux.c
8850 because we built it with a too-old version of automake. Thus that
8851 release broke ./configure --enable-openbsd-malloc, which is popular
8852 among really fast exit relays on Linux.
8855 - Update to the January 1 2011 Maxmind GeoLite Country database.
8856 - Introduce output size checks on all of our decryption functions.
8859 - Tor does not build packages correctly with Automake 1.6 and earlier;
8860 added a check to Makefile.am to make sure that we're building with
8861 Automake 1.7 or later.
8864 Changes in version 0.2.2.20-alpha - 2010-12-17
8865 Tor 0.2.2.20-alpha does some code cleanup to reduce the risk of remotely
8866 exploitable bugs. We also fix a variety of other significant bugs,
8867 change the IP address for one of our directory authorities, and update
8868 the minimum version that Tor relays must run to join the network.
8871 - Fix a remotely exploitable bug that could be used to crash instances
8872 of Tor remotely by overflowing on the heap. Remote-code execution
8873 hasn't been confirmed, but can't be ruled out. Everyone should
8874 upgrade. Bugfix on the 0.1.1 series and later.
8875 - Fix a bug that could break accounting on 64-bit systems with large
8876 time_t values, making them hibernate for impossibly long intervals.
8877 Fixes bug 2146. Bugfix on 0.0.9pre6; fix by boboper.
8878 - Fix a logic error in directory_fetches_from_authorities() that
8879 would cause all _non_-exits refusing single-hop-like circuits
8880 to fetch from authorities, when we wanted to have _exits_ fetch
8881 from authorities. Fixes more of 2097. Bugfix on 0.2.2.16-alpha;
8883 - Fix a stream fairness bug that would cause newer streams on a given
8884 circuit to get preference when reading bytes from the origin or
8885 destination. Fixes bug 2210. Fix by Mashael AlSabah. This bug was
8886 introduced before the first Tor release, in svn revision r152.
8888 o Directory authority changes:
8889 - Change IP address and ports for gabelmoo (v3 directory authority).
8892 - Avoid crashes when AccountingMax is set on clients. Fixes bug 2235.
8893 Bugfix on 0.2.2.18-alpha. Diagnosed by boboper.
8894 - Fix an off-by-one error in calculating some controller command
8895 argument lengths. Fortunately, this mistake is harmless since
8896 the controller code does redundant NUL termination too. Found by
8897 boboper. Bugfix on 0.1.1.1-alpha.
8898 - Do not dereference NULL if a bridge fails to build its
8899 extra-info descriptor. Found by an anonymous commenter on
8900 Trac. Bugfix on 0.2.2.19-alpha.
8903 - Update to the December 1 2010 Maxmind GeoLite Country database.
8904 - Directory authorities now reject relays running any versions of
8905 Tor between 0.2.1.3-alpha and 0.2.1.18 inclusive; they have
8906 known bugs that keep RELAY_EARLY cells from working on rendezvous
8907 circuits. Followup to fix for bug 2081.
8908 - Directory authorities now reject relays running any version of Tor
8909 older than 0.2.0.26-rc. That version is the earliest that fetches
8910 current directory information correctly. Fixes bug 2156.
8911 - Report only the top 10 ports in exit-port stats in order not to
8912 exceed the maximum extra-info descriptor length of 50 KB. Implements
8916 Changes in version 0.2.1.28 - 2010-12-17
8917 Tor 0.2.1.28 does some code cleanup to reduce the risk of remotely
8918 exploitable bugs. We also took this opportunity to change the IP address
8919 for one of our directory authorities, and to update the geoip database
8923 - Fix a remotely exploitable bug that could be used to crash instances
8924 of Tor remotely by overflowing on the heap. Remote-code execution
8925 hasn't been confirmed, but can't be ruled out. Everyone should
8926 upgrade. Bugfix on the 0.1.1 series and later.
8928 o Directory authority changes:
8929 - Change IP address and ports for gabelmoo (v3 directory authority).
8932 - Update to the December 1 2010 Maxmind GeoLite Country database.
8935 Changes in version 0.2.1.27 - 2010-11-23
8936 Yet another OpenSSL security patch broke its compatibility with Tor:
8937 Tor 0.2.1.27 makes relays work with openssl 0.9.8p and 1.0.0.b. We
8938 also took this opportunity to fix several crash bugs, integrate a new
8939 directory authority, and update the bundled GeoIP database.
8942 - Resolve an incompatibility with OpenSSL 0.9.8p and OpenSSL 1.0.0b:
8943 No longer set the tlsext_host_name extension on server SSL objects;
8944 but continue to set it on client SSL objects. Our goal in setting
8945 it was to imitate a browser, not a vhosting server. Fixes bug 2204;
8946 bugfix on 0.2.1.1-alpha.
8947 - Do not log messages to the controller while shrinking buffer
8948 freelists. Doing so would sometimes make the controller connection
8949 try to allocate a buffer chunk, which would mess up the internals
8950 of the freelist and cause an assertion failure. Fixes bug 1125;
8951 fixed by Robert Ransom. Bugfix on 0.2.0.16-alpha.
8952 - Learn our external IP address when we're a relay or bridge, even if
8953 we set PublishServerDescriptor to 0. Bugfix on 0.2.0.3-alpha,
8954 where we introduced bridge relays that don't need to publish to
8955 be useful. Fixes bug 2050.
8956 - Do even more to reject (and not just ignore) annotations on
8957 router descriptors received anywhere but from the cache. Previously
8958 we would ignore such annotations at first, but cache them to disk
8959 anyway. Bugfix on 0.2.0.8-alpha. Found by piebeer.
8960 - When you're using bridges and your network goes away and your
8961 bridges get marked as down, recover when you attempt a new socks
8962 connection (if the network is back), rather than waiting up to an
8963 hour to try fetching new descriptors for your bridges. Bugfix on
8964 0.2.0.3-alpha; fixes bug 1981.
8967 - Move to the November 2010 Maxmind GeoLite country db (rather
8968 than the June 2009 ip-to-country GeoIP db) for our statistics that
8969 count how many users relays are seeing from each country. Now we'll
8970 have more accurate data, especially for many African countries.
8972 o New directory authorities:
8973 - Set up maatuska (run by Linus Nordberg) as the eighth v3 directory
8977 - Fix an assertion failure that could occur in directory caches or
8978 bridge users when using a very short voting interval on a testing
8979 network. Diagnosed by Robert Hogan. Fixes bug 1141; bugfix on
8981 - Enforce multiplicity rules when parsing annotations. Bugfix on
8982 0.2.0.8-alpha. Found by piebeer.
8983 - Allow handshaking OR connections to take a full KeepalivePeriod
8984 seconds to handshake. Previously, we would close them after
8985 IDLE_OR_CONN_TIMEOUT (180) seconds, the same timeout as if they
8986 were open. Bugfix on 0.2.1.26; fixes bug 1840. Thanks to mingw-san
8988 - When building with --enable-gcc-warnings on OpenBSD, disable
8989 warnings in system headers. This makes --enable-gcc-warnings
8990 pass on OpenBSD 4.8.
8993 - Exit nodes didn't recognize EHOSTUNREACH as a plausible error code,
8994 and so sent back END_STREAM_REASON_MISC. Clients now recognize a new
8995 stream ending reason for this case: END_STREAM_REASON_NOROUTE.
8996 Servers can start sending this code when enough clients recognize
8997 it. Bugfix on 0.1.0.1-rc; fixes part of bug 1793.
8998 - Build correctly on mingw with more recent versions of OpenSSL 0.9.8.
8999 Patch from mingw-san.
9002 - Remove the old debian/ directory from the main Tor distribution.
9003 The official Tor-for-debian git repository lives at the URL
9004 https://git.torproject.org/debian/tor.git
9005 - Stop shipping the old doc/website/ directory in the tarball. We
9006 changed the website format in late 2010, and what we shipped in
9007 0.2.1.26 really wasn't that useful anyway.
9010 Changes in version 0.2.2.19-alpha - 2010-11-22
9011 Yet another OpenSSL security patch broke its compatibility with Tor:
9012 Tor 0.2.2.19-alpha makes relays work with OpenSSL 0.9.8p and 1.0.0.b.
9015 - Resolve an incompatibility with OpenSSL 0.9.8p and OpenSSL 1.0.0b:
9016 No longer set the tlsext_host_name extension on server SSL objects;
9017 but continue to set it on client SSL objects. Our goal in setting
9018 it was to imitate a browser, not a vhosting server. Fixes bug 2204;
9019 bugfix on 0.2.1.1-alpha.
9022 - Try harder not to exceed the maximum length of 50 KB when writing
9023 statistics to extra-info descriptors. This bug was triggered by very
9024 fast relays reporting exit-port, entry, and dirreq statistics.
9025 Reported by Olaf Selke. Bugfix on 0.2.2.1-alpha. Fixes bug 2183.
9026 - Publish a router descriptor even if generating an extra-info
9027 descriptor fails. Previously we would not publish a router
9028 descriptor without an extra-info descriptor; this can cause fast
9029 exit relays collecting exit-port statistics to drop from the
9030 consensus. Bugfix on 0.1.2.9-rc; fixes bug 2195.
9033 Changes in version 0.2.2.18-alpha - 2010-11-16
9034 Tor 0.2.2.18-alpha fixes several crash bugs that have been nagging
9035 us lately, makes unpublished bridge relays able to detect their IP
9036 address, and fixes a wide variety of other bugs to get us much closer
9037 to a stable release.
9040 - Do even more to reject (and not just ignore) annotations on
9041 router descriptors received anywhere but from the cache. Previously
9042 we would ignore such annotations at first, but cache them to disk
9043 anyway. Bugfix on 0.2.0.8-alpha. Found by piebeer.
9044 - Do not log messages to the controller while shrinking buffer
9045 freelists. Doing so would sometimes make the controller connection
9046 try to allocate a buffer chunk, which would mess up the internals
9047 of the freelist and cause an assertion failure. Fixes bug 1125;
9048 fixed by Robert Ransom. Bugfix on 0.2.0.16-alpha.
9049 - Learn our external IP address when we're a relay or bridge, even if
9050 we set PublishServerDescriptor to 0. Bugfix on 0.2.0.3-alpha,
9051 where we introduced bridge relays that don't need to publish to
9052 be useful. Fixes bug 2050.
9053 - Maintain separate TLS contexts and certificates for incoming and
9054 outgoing connections in bridge relays. Previously we would use the
9055 same TLS contexts and certs for incoming and outgoing connections.
9056 Bugfix on 0.2.0.3-alpha; addresses bug 988.
9057 - Maintain separate identity keys for incoming and outgoing TLS
9058 contexts in bridge relays. Previously we would use the same
9059 identity keys for incoming and outgoing TLS contexts. Bugfix on
9060 0.2.0.3-alpha; addresses the other half of bug 988.
9061 - Avoid an assertion failure when we as an authority receive a
9062 duplicate upload of a router descriptor that we already have,
9063 but which we previously considered an obsolete descriptor.
9064 Fixes another case of bug 1776. Bugfix on 0.2.2.16-alpha.
9065 - Avoid a crash bug triggered by looking at a dangling pointer while
9066 setting the network status consensus. Found by Robert Ransom.
9067 Bugfix on 0.2.2.17-alpha. Fixes bug 2097.
9068 - Fix a logic error where servers that _didn't_ act as exits would
9069 try to keep their server lists more aggressively up to date than
9070 exits, when it was supposed to be the other way around. Bugfix
9073 o Minor bugfixes (on Tor 0.2.1.x and earlier):
9074 - When we're trying to guess whether we know our IP address as
9075 a relay, we would log various ways that we failed to guess
9076 our address, but never log that we ended up guessing it
9077 successfully. Now add a log line to help confused and anxious
9078 relay operators. Bugfix on 0.1.2.1-alpha; fixes bug 1534.
9079 - Bring the logic that gathers routerinfos and assesses the
9080 acceptability of circuits into line. This prevents a Tor OP from
9081 getting locked in a cycle of choosing its local OR as an exit for a
9082 path (due to a .exit request) and then rejecting the circuit because
9083 its OR is not listed yet. It also prevents Tor clients from using an
9084 OR running in the same instance as an exit (due to a .exit request)
9085 if the OR does not meet the same requirements expected of an OR
9086 running elsewhere. Fixes bug 1859; bugfix on 0.1.0.1-rc.
9087 - Correctly describe errors that occur when generating a TLS object.
9088 Previously we would attribute them to a failure while generating a
9089 TLS context. Patch by Robert Ransom. Bugfix on 0.1.0.4-rc; fixes
9091 - Enforce multiplicity rules when parsing annotations. Bugfix on
9092 0.2.0.8-alpha. Found by piebeer.
9093 - Fix warnings that newer versions of autoconf produced during
9094 ./autogen.sh. These warnings appear to be harmless in our case,
9095 but they were extremely verbose. Fixes bug 2020.
9097 o Minor bugfixes (on Tor 0.2.2.x):
9098 - Enable protection of small arrays whenever we build with gcc
9099 hardening features, not only when also building with warnings
9100 enabled. Fixes bug 2031; bugfix on 0.2.2.14-alpha. Reported by keb.
9103 - Make hidden services work better in private Tor networks by not
9104 requiring any uptime to join the hidden service descriptor
9105 DHT. Implements ticket 2088.
9106 - Rate-limit the "your application is giving Tor only an IP address"
9107 warning. Addresses bug 2000; bugfix on 0.0.8pre2.
9108 - When AllowSingleHopExits is set, print a warning to explain to the
9109 relay operator why most clients are avoiding her relay.
9110 - Update to the November 1 2010 Maxmind GeoLite Country database.
9112 o Code simplifications and refactoring:
9113 - When we fixed bug 1038 we had to put in a restriction not to send
9114 RELAY_EARLY cells on rend circuits. This was necessary as long
9115 as relays using Tor 0.2.1.3-alpha through 0.2.1.18-alpha were
9116 active. Now remove this obsolete check. Resolves bug 2081.
9117 - Some options used different conventions for uppercasing of acronyms
9118 when comparing manpage and source. Fix those in favor of the
9119 manpage, as it makes sense to capitalize acronyms.
9120 - Remove the torrc.complete file. It hasn't been kept up to date
9121 and users will have better luck checking out the manpage.
9122 - Remove the obsolete "NoPublish" option; it has been flagged
9123 as obsolete and has produced a warning since 0.1.1.18-rc.
9124 - Remove everything related to building the expert bundle for OS X.
9125 It has confused many users, doesn't work right on OS X 10.6,
9126 and is hard to get rid of once installed. Resolves bug 1274.
9129 Changes in version 0.2.2.17-alpha - 2010-09-30
9130 Tor 0.2.2.17-alpha introduces a feature to make it harder for clients
9131 to use one-hop circuits (which can put the exit relays at higher risk,
9132 plus unbalance the network); fixes a big bug in bandwidth accounting
9133 for relays that want to limit their monthly bandwidth use; fixes a
9134 big pile of bugs in how clients tolerate temporary network failure;
9135 and makes our adaptive circuit build timeout feature (which improves
9136 client performance if your network is fast while not breaking things
9137 if your network is slow) better handle bad networks.
9140 - Exit relays now try harder to block exit attempts from unknown
9141 relays, to make it harder for people to use them as one-hop proxies
9142 a la tortunnel. Controlled by the refuseunknownexits consensus
9143 parameter (currently enabled), or you can override it on your
9144 relay with the RefuseUnknownExits torrc option. Resolves bug 1751.
9146 o Major bugfixes (0.2.1.x and earlier):
9147 - Fix a bug in bandwidth accounting that could make us use twice
9148 the intended bandwidth when our interval start changes due to
9149 daylight saving time. Now we tolerate skew in stored vs computed
9150 interval starts: if the start of the period changes by no more than
9151 50% of the period's duration, we remember bytes that we transferred
9152 in the old period. Fixes bug 1511; bugfix on 0.0.9pre5.
9153 - Always search the Windows system directory for system DLLs, and
9154 nowhere else. Bugfix on 0.1.1.23; fixes bug 1954.
9155 - When you're using bridges and your network goes away and your
9156 bridges get marked as down, recover when you attempt a new socks
9157 connection (if the network is back), rather than waiting up to an
9158 hour to try fetching new descriptors for your bridges. Bugfix on
9159 0.2.0.3-alpha; fixes bug 1981.
9161 o Major bugfixes (on 0.2.2.x):
9162 - Fix compilation on Windows. Bugfix on 0.2.2.16-alpha; related to
9164 - Fix a segfault that could happen when operating a bridge relay with
9165 no GeoIP database set. Fixes bug 1964; bugfix on 0.2.2.15-alpha.
9166 - The consensus bandwidth-weights (used by clients to choose fast
9167 relays) entered an unexpected edge case in September where
9168 Exits were much scarcer than Guards, resulting in bad weight
9169 recommendations. Now we compute them using new constraints that
9170 should succeed in all cases. Also alter directory authorities to
9171 not include the bandwidth-weights line if they fail to produce
9172 valid values. Fixes bug 1952; bugfix on 0.2.2.10-alpha.
9173 - When weighting bridges during path selection, we used to trust
9174 the bandwidths they provided in their descriptor, only capping them
9175 at 10MB/s. This turned out to be problematic for two reasons:
9176 Bridges could claim to handle a lot more traffic then they
9177 actually would, thus making more clients pick them and have a
9178 pretty effective DoS attack. The other issue is that new bridges
9179 that might not have a good estimate for their bw capacity yet
9180 would not get used at all unless no other bridges are available
9181 to a client. Fixes bug 1912; bugfix on 0.2.2.7-alpha.
9183 o Major bugfixes (on the circuit build timeout feature, 0.2.2.x):
9184 - Ignore cannibalized circuits when recording circuit build times.
9185 This should provide for a minor performance improvement for hidden
9186 service users using 0.2.2.14-alpha, and should remove two spurious
9187 notice log messages. Bugfix on 0.2.2.14-alpha; fixes bug 1740.
9188 - Simplify the logic that causes us to decide if the network is
9189 unavailable for purposes of recording circuit build times. If we
9190 receive no cells whatsoever for the entire duration of a circuit's
9191 full measured lifetime, the network is probably down. Also ignore
9192 one-hop directory fetching circuit timeouts when calculating our
9193 circuit build times. These changes should hopefully reduce the
9194 cases where we see ridiculous circuit build timeouts for people
9195 with spotty wireless connections. Fixes part of bug 1772; bugfix
9197 - Prevent the circuit build timeout from becoming larger than
9198 the maximum build time we have ever seen. Also, prevent the time
9199 period for measurement circuits from becoming larger than twice that
9200 value. Fixes the other part of bug 1772; bugfix on 0.2.2.2-alpha.
9203 - When we run out of directory information such that we can't build
9204 circuits, but then get enough that we can build circuits, log when
9205 we actually construct a circuit, so the user has a better chance of
9206 knowing what's going on. Fixes bug 1362.
9207 - Be more generous with how much bandwidth we'd use up (with
9208 accounting enabled) before entering "soft hibernation". Previously,
9209 we'd refuse new connections and circuits once we'd used up 95% of
9210 our allotment. Now, we use up 95% of our allotment, AND make sure
9211 that we have no more than 500MB (or 3 hours of expected traffic,
9212 whichever is lower) remaining before we enter soft hibernation.
9213 - If we've configured EntryNodes and our network goes away and/or all
9214 our entrynodes get marked down, optimistically retry them all when
9215 a new socks application request appears. Fixes bug 1882.
9216 - Add some more defensive programming for architectures that can't
9217 handle unaligned integer accesses. We don't know of any actual bugs
9218 right now, but that's the best time to fix them. Fixes bug 1943.
9219 - Support line continuations in the torrc config file. If a line
9220 ends with a single backslash character, the newline is ignored, and
9221 the configuration value is treated as continuing on the next line.
9224 o Minor bugfixes (on 0.2.1.x and earlier):
9225 - For bandwidth accounting, calculate our expected bandwidth rate
9226 based on the time during which we were active and not in
9227 soft-hibernation during the last interval. Previously, we were
9228 also considering the time spent in soft-hibernation. If this
9229 was a long time, we would wind up underestimating our bandwidth
9230 by a lot, and skewing our wakeup time towards the start of the
9231 accounting interval. Fixes bug 1789. Bugfix on 0.0.9pre5.
9233 o Minor bugfixes (on 0.2.2.x):
9234 - Resume generating CIRC FAILED REASON=TIMEOUT control port messages,
9235 which were disabled by the circuit build timeout changes in
9236 0.2.2.14-alpha. Bugfix on 0.2.2.14-alpha; fixes bug 1739.
9237 - Make sure we don't warn about missing bandwidth weights when
9238 choosing bridges or other relays not in the consensus. Bugfix on
9239 0.2.2.10-alpha; fixes bug 1805.
9240 - In our logs, do not double-report signatures from unrecognized
9241 authorities both as "from unknown authority" and "not
9242 present". Fixes bug 1956, bugfix on 0.2.2.16-alpha.
9245 Changes in version 0.2.2.16-alpha - 2010-09-17
9246 Tor 0.2.2.16-alpha fixes a variety of old stream fairness bugs (most
9247 evident at exit relays), and also continues to resolve all the little
9248 bugs that have been filling up trac lately.
9250 o Major bugfixes (stream-level fairness):
9251 - When receiving a circuit-level SENDME for a blocked circuit, try
9252 to package cells fairly from all the streams that had previously
9253 been blocked on that circuit. Previously, we had started with the
9254 oldest stream, and allowed each stream to potentially exhaust
9255 the circuit's package window. This gave older streams on any
9256 given circuit priority over newer ones. Fixes bug 1937. Detected
9257 originally by Camilo Viecco. This bug was introduced before the
9258 first Tor release, in svn commit r152: it is the new winner of
9259 the longest-lived bug prize.
9260 - When the exit relay got a circuit-level sendme cell, it started
9261 reading on the exit streams, even if had 500 cells queued in the
9262 circuit queue already, so the circuit queue just grew and grew in
9263 some cases. We fix this by not re-enabling reading on receipt of a
9264 sendme cell when the cell queue is blocked. Fixes bug 1653. Bugfix
9265 on 0.2.0.1-alpha. Detected by Mashael AlSabah. Original patch by
9267 - Newly created streams were allowed to read cells onto circuits,
9268 even if the circuit's cell queue was blocked and waiting to drain.
9269 This created potential unfairness, as older streams would be
9270 blocked, but newer streams would gladly fill the queue completely.
9271 We add code to detect this situation and prevent any stream from
9272 getting more than one free cell. Bugfix on 0.2.0.1-alpha. Partially
9276 - Update to the September 1 2010 Maxmind GeoLite Country database.
9277 - Warn when CookieAuthFileGroupReadable is set but CookieAuthFile is
9278 not. This would lead to a cookie that is still not group readable.
9279 Closes bug 1843. Suggested by katmagic.
9280 - When logging a rate-limited warning, we now mention how many messages
9281 got suppressed since the last warning.
9282 - Add new "perconnbwrate" and "perconnbwburst" consensus params to
9283 do individual connection-level rate limiting of clients. The torrc
9284 config options with the same names trump the consensus params, if
9285 both are present. Replaces the old "bwconnrate" and "bwconnburst"
9286 consensus params which were broken from 0.2.2.7-alpha through
9287 0.2.2.14-alpha. Closes bug 1947.
9288 - When a router changes IP address or port, authorities now launch
9289 a new reachability test for it. Implements ticket 1899.
9290 - Make the formerly ugly "2 unknown, 7 missing key, 0 good, 0 bad,
9291 2 no signature, 4 required" messages about consensus signatures
9292 easier to read, and make sure they get logged at the same severity
9293 as the messages explaining which keys are which. Fixes bug 1290.
9294 - Don't warn when we have a consensus that we can't verify because
9295 of missing certificates, unless those certificates are ones
9296 that we have been trying and failing to download. Fixes bug 1145.
9297 - If you configure your bridge with a known identity fingerprint,
9298 and the bridge authority is unreachable (as it is in at least
9299 one country now), fall back to directly requesting the descriptor
9300 from the bridge. Finishes the feature started in 0.2.0.10-alpha;
9302 - When building with --enable-gcc-warnings on OpenBSD, disable
9303 warnings in system headers. This makes --enable-gcc-warnings
9304 pass on OpenBSD 4.8.
9306 o Minor bugfixes (on 0.2.1.x and earlier):
9307 - Authorities will now attempt to download consensuses if their
9308 own efforts to make a live consensus have failed. This change
9309 means authorities that restart will fetch a valid consensus, and
9310 it means authorities that didn't agree with the current consensus
9311 will still fetch and serve it if it has enough signatures. Bugfix
9312 on 0.2.0.9-alpha; fixes bug 1300.
9313 - Ensure DNS requests launched by "RESOLVE" commands from the
9314 controller respect the __LeaveStreamsUnattached setconf options. The
9315 same goes for requests launched via DNSPort or transparent
9316 proxying. Bugfix on 0.2.0.1-alpha; fixes bug 1525.
9317 - Allow handshaking OR connections to take a full KeepalivePeriod
9318 seconds to handshake. Previously, we would close them after
9319 IDLE_OR_CONN_TIMEOUT (180) seconds, the same timeout as if they
9320 were open. Bugfix on 0.2.1.26; fixes bug 1840. Thanks to mingw-san
9322 - Rate-limit "Failed to hand off onionskin" warnings.
9323 - Never relay a cell for a circuit we have already destroyed.
9324 Between marking a circuit as closeable and finally closing it,
9325 it may have been possible for a few queued cells to get relayed,
9326 even though they would have been immediately dropped by the next
9327 OR in the circuit. Fixes bug 1184; bugfix on 0.2.0.1-alpha.
9328 - Never queue a cell for a circuit that's already been marked
9330 - Never vote for a server as "Running" if we have a descriptor for
9331 it claiming to be hibernating, and that descriptor was published
9332 more recently than our last contact with the server. Bugfix on
9333 0.2.0.3-alpha; fixes bug 911.
9334 - Squash a compile warning on OpenBSD. Reported by Tas; fixes
9337 o Minor bugfixes (on 0.2.2.x):
9338 - Fix a regression introduced in 0.2.2.7-alpha that marked relays
9339 down if a directory fetch fails and you've configured either
9340 bridges or EntryNodes. The intent was to mark the relay as down
9341 _unless_ you're using bridges or EntryNodes, since if you are
9342 then you could quickly run out of entry points.
9343 - Fix the Windows directory-listing code. A bug introduced in
9344 0.2.2.14-alpha could make Windows directory servers forget to load
9345 some of their cached v2 networkstatus files.
9346 - Really allow clients to use relays as bridges. Fixes bug 1776;
9347 bugfix on 0.2.2.15-alpha.
9348 - Demote a warn to info that happens when the CellStatistics option
9349 was just enabled. Bugfix on 0.2.2.15-alpha; fixes bug 1921.
9350 Reported by Moritz Bartl.
9351 - On Windows, build correctly either with or without Unicode support.
9352 This is necessary so that Tor can support fringe platforms like
9353 Windows 98 (which has no Unicode), or Windows CE (which has no
9354 non-Unicode). Bugfix on 0.2.2.14-alpha; fixes bug 1797.
9357 - Add a unit test for cross-platform directory-listing code.
9360 Changes in version 0.2.2.15-alpha - 2010-08-18
9361 Tor 0.2.2.15-alpha fixes a big bug in hidden service availability,
9362 fixes a variety of other bugs that were preventing performance
9363 experiments from moving forward, fixes several bothersome memory leaks,
9364 and generally closes a lot of smaller bugs that have been filling up
9368 - Stop assigning the HSDir flag to relays that disable their
9369 DirPort (and thus will refuse to answer directory requests). This
9370 fix should dramatically improve the reachability of hidden services:
9371 hidden services and hidden service clients pick six HSDir relays
9372 to store and retrieve the hidden service descriptor, and currently
9373 about half of the HSDir relays will refuse to work. Bugfix on
9374 0.2.0.10-alpha; fixes part of bug 1693.
9375 - The PerConnBWRate and Burst config options, along with the
9376 bwconnrate and bwconnburst consensus params, initialized each conn's
9377 token bucket values only when the connection is established. Now we
9378 update them if the config options change, and update them every time
9379 we get a new consensus. Otherwise we can encounter an ugly edge
9380 case where we initialize an OR conn to client-level bandwidth,
9381 but then later the relay joins the consensus and we leave it
9382 throttled. Bugfix on 0.2.2.7-alpha; fixes bug 1830.
9383 - Fix a regression that caused Tor to rebind its ports if it receives
9384 SIGHUP while hibernating. Bugfix in 0.1.1.6-alpha; closes bug 919.
9387 - Lower the maximum weighted-fractional-uptime cutoff to 98%. This
9388 should give us approximately 40-50% more Guard-flagged nodes,
9389 improving the anonymity the Tor network can provide and also
9390 decreasing the dropoff in throughput that relays experience when
9391 they first get the Guard flag.
9392 - Allow enabling or disabling the *Statistics config options while
9396 - Update to the August 1 2010 Maxmind GeoLite Country database.
9397 - Have the controller interface give a more useful message than
9398 "Internal Error" in response to failed GETINFO requests.
9399 - Warn when the same option is provided more than once in a torrc
9400 file, on the command line, or in a single SETCONF statement, and
9401 the option is one that only accepts a single line. Closes bug 1384.
9402 - Build correctly on mingw with more recent versions of OpenSSL 0.9.8.
9403 Patch from mingw-san.
9404 - Add support for the country code "{??}" in torrc options like
9405 ExcludeNodes, to indicate all routers of unknown country. Closes
9407 - Relays report the number of bytes spent on answering directory
9408 requests in extra-info descriptors similar to {read,write}-history.
9409 Implements enhancement 1790.
9411 o Minor bugfixes (on 0.2.1.x and earlier):
9412 - Complain if PublishServerDescriptor is given multiple arguments that
9413 include 0 or 1. This configuration will be rejected in the future.
9414 Bugfix on 0.2.0.1-alpha; closes bug 1107.
9415 - Disallow BridgeRelay 1 and ORPort 0 at once in the configuration.
9416 Bugfix on 0.2.0.13-alpha; closes bug 928.
9417 - Change "Application request when we're believed to be offline."
9418 notice to "Application request when we haven't used client
9419 functionality lately.", to clarify that it's not an error. Bugfix
9420 on 0.0.9.3; fixes bug 1222.
9421 - Fix a bug in the controller interface where "GETINFO ns/asdaskljkl"
9422 would return "551 Internal error" rather than "552 Unrecognized key
9423 ns/asdaskljkl". Bugfix on 0.1.2.3-alpha.
9424 - Users can't configure a regular relay to be their bridge. It didn't
9425 work because when Tor fetched the bridge descriptor, it found
9426 that it already had it, and didn't realize that the purpose of the
9427 descriptor had changed. Now we replace routers with a purpose other
9428 than bridge with bridge descriptors when fetching them. Bugfix on
9429 0.1.1.9-alpha. Bug 1776 not yet fixed because now we immediately
9430 refetch the descriptor with router purpose 'general', disabling
9432 - Fix a rare bug in rend_fn unit tests: we would fail a test when
9433 a randomly generated port is 0. Diagnosed by Matt Edman. Bugfix
9434 on 0.2.0.10-alpha; fixes bug 1808.
9435 - Exit nodes didn't recognize EHOSTUNREACH as a plausible error code,
9436 and so sent back END_STREAM_REASON_MISC. Clients now recognize a new
9437 stream ending reason for this case: END_STREAM_REASON_NOROUTE.
9438 Servers can start sending this code when enough clients recognize
9439 it. Also update the spec to reflect this new reason. Bugfix on
9440 0.1.0.1-rc; fixes part of bug 1793.
9441 - Delay geoip stats collection by bridges for 6 hours, not 2 hours,
9442 when we switch from being a public relay to a bridge. Otherwise
9443 there will still be clients that see the relay in their consensus,
9444 and the stats will end up wrong. Bugfix on 0.2.1.15-rc; fixes bug
9446 - Instead of giving an assertion failure on an internal mismatch
9447 on estimated freelist size, just log a BUG warning and try later.
9448 Mitigates but does not fix bug 1125.
9449 - Fix an assertion failure that could occur in caches or bridge users
9450 when using a very short voting interval on a testing network.
9451 Diagnosed by Robert Hogan. Fixes bug 1141; bugfix on 0.2.0.8-alpha.
9453 o Minor bugfixes (on 0.2.2.x):
9454 - Alter directory authorities to always consider Exit-flagged nodes
9455 as potential Guard nodes in their votes. The actual decision to
9456 use Exits as Guards is done in the consensus bandwidth weights.
9457 Fixes bug 1294; bugfix on 0.2.2.10-alpha.
9458 - When the controller is reporting the purpose of circuits that
9459 didn't finish building before the circuit build timeout, it was
9460 printing UNKNOWN_13. Now print EXPIRED. Bugfix on 0.2.2.14-alpha.
9461 - Our libevent version parsing code couldn't handle versions like
9462 1.4.14b-stable and incorrectly warned the user about using an
9463 old and broken version of libevent. Treat 1.4.14b-stable like
9464 1.4.14-stable when parsing the version. Fixes bug 1731; bugfix
9466 - Don't use substitution references like $(VAR:MOD) when
9467 $(asciidoc_files) is empty -- make(1) on NetBSD transforms
9468 '$(:x)' to 'x' rather than the empty string. This bites us in
9469 doc/ when configured with --disable-asciidoc. Bugfix on
9470 0.2.2.9-alpha; fixes bug 1773.
9471 - Remove a spurious hidden service server-side log notice about
9472 "Ancient non-dirty circuits". Bugfix on 0.2.2.14-alpha; fixes
9474 - Fix compilation with --with-dmalloc set. Bugfix on 0.2.2.6-alpha;
9476 - Correctly report written bytes on linked connections. Found while
9477 implementing 1790. Bugfix on 0.2.2.4-alpha.
9478 - Fix three memory leaks: one in circuit_build_times_parse_state(),
9479 one in dirvote_add_signatures_to_pending_consensus(), and one every
9480 time we parse a v3 network consensus. Bugfixes on 0.2.2.14-alpha,
9481 0.2.2.6-alpha, and 0.2.2.10-alpha respectively; fixes bug 1831.
9483 o Code simplifications and refactoring:
9484 - Take a first step towards making or.h smaller by splitting out
9485 function definitions for all source files in src/or/. Leave
9486 structures and defines in or.h for now.
9487 - Remove a bunch of unused function declarations as well as a block of
9488 #if 0'd code from the unit tests. Closes bug 1824.
9489 - New unit tests for exit-port history statistics; refactored exit
9490 statistics code to be more easily tested.
9491 - Remove the old debian/ directory from the main Tor distribution.
9492 The official Tor-for-debian git repository lives at the URL
9493 https://git.torproject.org/debian/tor.git
9496 Changes in version 0.2.2.14-alpha - 2010-07-12
9497 Tor 0.2.2.14-alpha greatly improves client-side handling of
9498 circuit build timeouts, which are used to estimate speed and improve
9499 performance. We also move to a much better GeoIP database, port Tor to
9500 Windows CE, introduce new compile flags that improve code security,
9501 add an eighth v3 directory authority, and address a lot of more
9505 - Tor directory authorities no longer crash when started with a
9506 cached-microdesc-consensus file in their data directory. Bugfix
9507 on 0.2.2.6-alpha; fixes bug 1532.
9508 - Treat an unset $HOME like an empty $HOME rather than triggering an
9509 assert. Bugfix on 0.0.8pre1; fixes bug 1522.
9510 - Ignore negative and large circuit build timeout values that can
9511 happen during a suspend or hibernate. These values caused various
9512 asserts to fire. Bugfix on 0.2.2.2-alpha; fixes bug 1245.
9513 - Alter calculation of Pareto distribution parameter 'Xm' for
9514 Circuit Build Timeout learning to use the weighted average of the
9515 top N=3 modes (because we have three entry guards). Considering
9516 multiple modes should improve the timeout calculation in some cases,
9517 and prevent extremely high timeout values. Bugfix on 0.2.2.2-alpha;
9519 - Alter calculation of Pareto distribution parameter 'Alpha' to use a
9520 right censored distribution model. This approach improves over the
9521 synthetic timeout generation approach that was producing insanely
9522 high timeout values. Now we calculate build timeouts using truncated
9523 times. Bugfix on 0.2.2.2-alpha; fixes bugs 1245 and 1335.
9524 - Do not close circuits that are under construction when they reach
9525 the circuit build timeout. Instead, leave them building (but do not
9526 use them) for up until the time corresponding to the 95th percentile
9527 on the Pareto CDF or 60 seconds, whichever is greater. This is done
9528 to provide better data for the new Pareto model. This percentile
9529 can be controlled by the consensus.
9532 - Move to the June 2010 Maxmind GeoLite country db (rather than the
9533 June 2009 ip-to-country GeoIP db) for our statistics that count
9534 how many users relays are seeing from each country. Now we have
9535 more accurate data for many African countries.
9536 - Port Tor to build and run correctly on Windows CE systems, using
9537 the wcecompat library. Contributed by Valerio Lupi.
9538 - New "--enable-gcc-hardening" ./configure flag (off by default)
9539 to turn on gcc compile time hardening options. It ensures
9540 that signed ints have defined behavior (-fwrapv), enables
9541 -D_FORTIFY_SOURCE=2 (requiring -O2), adds stack smashing protection
9542 with canaries (-fstack-protector-all), turns on ASLR protection if
9543 supported by the kernel (-fPIE, -pie), and adds additional security
9544 related warnings. Verified to work on Mac OS X and Debian Lenny.
9545 - New "--enable-linker-hardening" ./configure flag (off by default)
9546 to turn on ELF specific hardening features (relro, now). This does
9547 not work with Mac OS X or any other non-ELF binary format.
9549 o New directory authorities:
9550 - Set up maatuska (run by Linus Nordberg) as the eighth v3 directory
9554 - New config option "WarnUnsafeSocks 0" disables the warning that
9555 occurs whenever Tor receives a socks handshake using a version of
9556 the socks protocol that can only provide an IP address (rather
9557 than a hostname). Setups that do DNS locally over Tor are fine,
9558 and we shouldn't spam the logs in that case.
9559 - Convert the HACKING file to asciidoc, and add a few new sections
9560 to it, explaining how we use Git, how we make changelogs, and
9561 what should go in a patch.
9562 - Add a TIMEOUT_RATE keyword to the BUILDTIMEOUT_SET control port
9563 event, to give information on the current rate of circuit timeouts
9564 over our stored history.
9565 - Add ability to disable circuit build time learning via consensus
9566 parameter and via a LearnCircuitBuildTimeout config option. Also
9567 automatically disable circuit build time calculation if we are
9568 either a AuthoritativeDirectory, or if we fail to write our state
9569 file. Fixes bug 1296.
9570 - More gracefully handle corrupt state files, removing asserts
9571 in favor of saving a backup and resetting state.
9572 - Rename the "log.h" header to "torlog.h" so as to conflict with fewer
9576 - Build correctly on OSX with zlib 1.2.4 and higher with all warnings
9578 - When a2x fails, mention that the user could disable manpages instead
9579 of trying to fix their asciidoc installation.
9580 - Where available, use Libevent 2.0's periodic timers so that our
9581 once-per-second cleanup code gets called even more closely to
9582 once per second than it would otherwise. Fixes bug 943.
9583 - If you run a bridge that listens on multiple IP addresses, and
9584 some user configures a bridge address that uses a different IP
9585 address than your bridge writes in its router descriptor, and the
9586 user doesn't specify an identity key, their Tor would discard the
9587 descriptor because "it isn't one of our configured bridges", and
9588 fail to bootstrap. Now believe the descriptor and bootstrap anyway.
9589 Bugfix on 0.2.0.3-alpha.
9590 - If OpenSSL fails to make a duplicate of a private or public key, log
9591 an error message and try to exit cleanly. May help with debugging
9592 if bug 1209 ever remanifests.
9593 - Save a couple bytes in memory allocation every time we escape
9594 certain characters in a string. Patch from Florian Zumbiehl.
9595 - Make it explicit that we don't cannibalize one-hop circuits. This
9596 happens in the wild, but doesn't turn out to be a problem because
9597 we fortunately don't use those circuits. Many thanks to outofwords
9598 for the initial analysis and to swissknife who confirmed that
9599 two-hop circuits are actually created.
9600 - Make directory mirrors report non-zero dirreq-v[23]-shares again.
9601 Fixes bug 1564; bugfix on 0.2.2.9-alpha.
9602 - Eliminate a case where a circuit build time warning was displayed
9603 after network connectivity resumed. Bugfix on 0.2.2.2-alpha.
9606 Changes in version 0.2.1.26 - 2010-05-02
9607 Tor 0.2.1.26 addresses the recent connection and memory overload
9608 problems we've been seeing on relays, especially relays with their
9609 DirPort open. If your relay has been crashing, or you turned it off
9610 because it used too many resources, give this release a try.
9612 This release also fixes yet another instance of broken OpenSSL libraries
9613 that was causing some relays to drop out of the consensus.
9616 - Teach relays to defend themselves from connection overload. Relays
9617 now close idle circuits early if it looks like they were intended
9618 for directory fetches. Relays are also more aggressive about closing
9619 TLS connections that have no circuits on them. Such circuits are
9620 unlikely to be re-used, and tens of thousands of them were piling
9621 up at the fast relays, causing the relays to run out of sockets
9622 and memory. Bugfix on 0.2.0.22-rc (where clients started tunneling
9623 their directory fetches over TLS).
9624 - Fix SSL renegotiation behavior on OpenSSL versions like on Centos
9625 that claim to be earlier than 0.9.8m, but which have in reality
9626 backported huge swaths of 0.9.8m or 0.9.8n renegotiation
9627 behavior. Possible fix for some cases of bug 1346.
9628 - Directory mirrors were fetching relay descriptors only from v2
9629 directory authorities, rather than v3 authorities like they should.
9630 Only 2 v2 authorities remain (compared to 7 v3 authorities), leading
9631 to a serious bottleneck. Bugfix on 0.2.0.9-alpha. Fixes bug 1324.
9634 - Finally get rid of the deprecated and now harmful notion of "clique
9635 mode", where directory authorities maintain TLS connections to
9639 - In the util/threads test, no longer free the test_mutex before all
9640 worker threads have finished. Bugfix on 0.2.1.6-alpha.
9641 - The master thread could starve the worker threads quite badly on
9642 certain systems, causing them to run only partially in the allowed
9643 window. This resulted in test failures. Now the master thread sleeps
9644 occasionally for a few microseconds while the two worker-threads
9645 compete for the mutex. Bugfix on 0.2.0.1-alpha.
9648 Changes in version 0.2.2.13-alpha - 2010-04-24
9649 Tor 0.2.2.13-alpha addresses the recent connection and memory overload
9650 problems we've been seeing on relays, especially relays with their
9651 DirPort open. If your relay has been crashing, or you turned it off
9652 because it used too many resources, give this release a try.
9655 - Teach relays to defend themselves from connection overload. Relays
9656 now close idle circuits early if it looks like they were intended
9657 for directory fetches. Relays are also more aggressive about closing
9658 TLS connections that have no circuits on them. Such circuits are
9659 unlikely to be re-used, and tens of thousands of them were piling
9660 up at the fast relays, causing the relays to run out of sockets
9661 and memory. Bugfix on 0.2.0.22-rc (where clients started tunneling
9662 their directory fetches over TLS).
9665 - Finally get rid of the deprecated and now harmful notion of "clique
9666 mode", where directory authorities maintain TLS connections to
9668 - Directory authorities now do an immediate reachability check as soon
9669 as they hear about a new relay. This change should slightly reduce
9670 the time between setting up a relay and getting listed as running
9671 in the consensus. It should also improve the time between setting
9672 up a bridge and seeing use by bridge users.
9673 - Directory authorities no longer launch a TLS connection to every
9674 relay as they startup. Now that we have 2k+ descriptors cached,
9675 the resulting network hiccup is becoming a burden. Besides,
9676 authorities already avoid voting about Running for the first half
9677 hour of their uptime.
9680 Changes in version 0.2.2.12-alpha - 2010-04-20
9681 Tor 0.2.2.12-alpha fixes a critical bug in how directory authorities
9682 handle and vote on descriptors. It was causing relays to drop out of
9686 - Many relays have been falling out of the consensus lately because
9687 not enough authorities know about their descriptor for them to get
9688 a majority of votes. When we deprecated the v2 directory protocol,
9689 we got rid of the only way that v3 authorities can hear from each
9690 other about other descriptors. Now authorities examine every v3
9691 vote for new descriptors, and fetch them from that authority. Bugfix
9693 - Fix two typos in tor_vasprintf() that broke the compile on Windows,
9694 and a warning in or.h related to bandwidth_weight_rule_t that
9695 prevented clean compile on OS X. Fixes bug 1363; bugfix on
9697 - Fix a segfault on relays when DirReqStatistics is enabled
9698 and 24 hours pass. Bug found by keb. Fixes bug 1365; bugfix on
9702 - Demote a confusing TLS warning that relay operators might get when
9703 someone tries to talk to their OrPort. It is neither the operator's
9704 fault nor can they do anything about it. Fixes bug 1364; bugfix
9708 Changes in version 0.2.2.11-alpha - 2010-04-15
9709 Tor 0.2.2.11-alpha fixes yet another instance of broken OpenSSL
9710 libraries that was causing some relays to drop out of the consensus.
9713 - Directory mirrors were fetching relay descriptors only from v2
9714 directory authorities, rather than v3 authorities like they should.
9715 Only 2 v2 authorities remain (compared to 7 v3 authorities), leading
9716 to a serious bottleneck. Bugfix on 0.2.0.9-alpha. Fixes bug 1324.
9717 - Fix a parsing error that made every possible value of
9718 CircPriorityHalflifeMsec get treated as "1 msec". Bugfix
9719 on 0.2.2.7-alpha. Rename CircPriorityHalflifeMsec to
9720 CircuitPriorityHalflifeMsec, so authorities can tell newer relays
9721 about the option without breaking older ones.
9722 - Fix SSL renegotiation behavior on OpenSSL versions like on Centos
9723 that claim to be earlier than 0.9.8m, but which have in reality
9724 backported huge swaths of 0.9.8m or 0.9.8n renegotiation
9725 behavior. Possible fix for some cases of bug 1346.
9728 - Experiment with a more aggressive approach to preventing clients
9729 from making one-hop exit streams. Exit relays who want to try it
9730 out can set "RefuseUnknownExits 1" in their torrc, and then look
9731 for "Attempt by %s to open a stream" log messages. Let us know
9733 - Add support for statically linking zlib by specifying
9734 --enable-static-zlib, to go with our support for statically linking
9735 openssl and libevent. Resolves bug 1358.
9738 - Fix a segfault that happens whenever a Tor client that is using
9739 libevent2's bufferevents gets a hup signal. Bugfix on 0.2.2.5-alpha;
9741 - When we cleaned up the contrib/tor-exit-notice.html file, we left
9742 out the first line. Fixes bug 1295.
9743 - When building the manpage from a tarball, we required asciidoc, but
9744 the asciidoc -> roff/html conversion was already done for the
9745 tarball. Make 'make' complain only when we need asciidoc (either
9746 because we're compiling directly from git, or because we altered
9747 the asciidoc manpage in the tarball). Bugfix on 0.2.2.9-alpha.
9748 - When none of the directory authorities vote on any params, Tor
9749 segfaulted when trying to make the consensus from the votes. We
9750 didn't trigger the bug in practice, because authorities do include
9751 params in their votes. Bugfix on 0.2.2.10-alpha; fixes bug 1322.
9754 - In the util/threads test, no longer free the test_mutex before all
9755 worker threads have finished. Bugfix on 0.2.1.6-alpha.
9756 - The master thread could starve the worker threads quite badly on
9757 certain systems, causing them to run only partially in the allowed
9758 window. This resulted in test failures. Now the master thread sleeps
9759 occasionally for a few microseconds while the two worker-threads
9760 compete for the mutex. Bugfix on 0.2.0.1-alpha.
9763 Changes in version 0.2.2.10-alpha - 2010-03-07
9764 Tor 0.2.2.10-alpha fixes a regression introduced in 0.2.2.9-alpha that
9765 could prevent relays from guessing their IP address correctly. It also
9766 starts the groundwork for another client-side performance boost, since
9767 currently we're not making efficient use of relays that have both the
9768 Guard flag and the Exit flag.
9771 - Fix a regression from our patch for bug 1244 that caused relays
9772 to guess their IP address incorrectly if they didn't set Address
9773 in their torrc and/or their address fails to resolve. Bugfix on
9774 0.2.2.9-alpha; fixes bug 1269.
9776 o Major features (performance):
9777 - Directory authorities now compute consensus weightings that instruct
9778 clients how to weight relays flagged as Guard, Exit, Guard+Exit,
9779 and no flag. Clients that use these weightings will distribute
9780 network load more evenly across these different relay types. The
9781 weightings are in the consensus so we can change them globally in
9782 the future. Extra thanks to "outofwords" for finding some nasty
9783 security bugs in the first implementation of this feature.
9785 o Minor features (performance):
9786 - Always perform router selections using weighted relay bandwidth,
9787 even if we don't need a high capacity circuit at the time. Non-fast
9788 circuits now only differ from fast ones in that they can use relays
9789 not marked with the Fast flag. This "feature" could turn out to
9790 be a horrible bug; we should investigate more before it goes into
9794 - Allow disabling building of the manpages. Skipping the manpage
9795 speeds up the build considerably.
9797 o Minor bugfixes (on 0.2.2.x):
9798 - Fix a memleak in the EXTENDCIRCUIT logic. Spotted by coverity.
9799 Bugfix on 0.2.2.9-alpha.
9800 - Disallow values larger than INT32_MAX for PerConnBWRate|Burst
9801 config option. Bugfix on 0.2.2.7-alpha.
9802 - Ship the asciidoc-helper file in the tarball, so that people can
9803 build from source if they want to, and touching the .1.txt files
9804 doesn't break the build. Bugfix on 0.2.2.9-alpha.
9806 o Minor bugfixes (on 0.2.1.x or earlier):
9807 - Fix a dereference-then-NULL-check sequence when publishing
9808 descriptors. Bugfix on 0.2.1.5-alpha. Discovered by ekir; fixes
9810 - Fix another dereference-then-NULL-check sequence. Bugfix on
9811 0.2.1.14-rc. Discovered by ekir; fixes bug 1256.
9812 - Make sure we treat potentially not NUL-terminated strings correctly.
9813 Bugfix on 0.1.1.13-alpha. Discovered by rieo; fixes bug 1257.
9815 o Code simplifications and refactoring:
9816 - Fix some urls in the exit notice file and make it XHTML1.1 strict
9817 compliant. Based on a patch from Christian Kujau.
9818 - Don't use sed in asciidoc-helper anymore.
9819 - Make the build process fail if asciidoc cannot be found and
9820 building with asciidoc isn't disabled.
9823 Changes in version 0.2.2.9-alpha - 2010-02-22
9824 Tor 0.2.2.9-alpha makes Tor work again on the latest OS X, updates the
9825 location of a directory authority, and cleans up a bunch of small bugs.
9827 o Directory authority changes:
9828 - Change IP address for dannenberg (v3 directory authority), and
9829 remove moria2 (obsolete v1, v2 directory authority and v0 hidden
9830 service directory authority) from the list.
9833 - Make Tor work again on the latest OS X: when deciding whether to
9834 use strange flags to turn TLS renegotiation on, detect the OpenSSL
9835 version at run-time, not compile time. We need to do this because
9836 Apple doesn't update its dev-tools headers when it updates its
9837 libraries in a security patch.
9838 - Fix a potential buffer overflow in lookup_last_hid_serv_request()
9839 that could happen on 32-bit platforms with 64-bit time_t. Also fix
9840 a memory leak when requesting a hidden service descriptor we've
9841 requested before. Fixes bug 1242, bugfix on 0.2.0.18-alpha. Found
9843 - Authorities could be tricked into giving out the Exit flag to relays
9844 that didn't allow exiting to any ports. This bug could screw
9845 with load balancing and stats. Bugfix on 0.1.1.6-alpha; fixes bug
9846 1238. Bug discovered by Martin Kowalczyk.
9847 - When freeing a session key, zero it out completely. We only zeroed
9848 the first ptrsize bytes. Bugfix on 0.0.2pre8. Discovered and
9849 patched by ekir. Fixes bug 1254.
9852 - Fix static compilation by listing the openssl libraries in the right
9853 order. Bugfix on Tor 0.2.2.8-alpha; fixes bug 1237.
9854 - Resume handling .exit hostnames in a special way: originally we
9855 stripped the .exit part and used the requested exit relay. In
9856 0.2.2.1-alpha we stopped treating them in any special way, meaning
9857 if you use a .exit address then Tor will pass it on to the exit
9858 relay. Now we reject the .exit stream outright, since that behavior
9859 might be more expected by the user. Found and diagnosed by Scott
9860 Bennett and Downie on or-talk.
9861 - Don't spam the controller with events when we have no file
9862 descriptors available. Bugfix on 0.2.1.5-alpha. (Rate-limiting
9863 for log messages was already solved from bug 748.)
9864 - Avoid a bogus overlapped memcpy in tor_addr_copy(). Reported by
9866 - Make the DNSPort option work with libevent 2.x. Don't alter the
9867 behavior for libevent 1.x. Fixes bug 1143. Found by SwissTorExit.
9868 - Emit a GUARD DROPPED controller event for a case we missed.
9869 - Make more fields in the controller protocol case-insensitive, since
9870 control-spec.txt said they were.
9871 - Refactor resolve_my_address() to not use gethostbyname() anymore.
9872 Fixes bug 1244; bugfix on 0.0.2pre25. Reported by Mike Mestnik.
9873 - Fix a spec conformance issue: the network-status-version token
9874 must be the first token in a v3 consensus or vote. Discovered by
9875 parakeep. Bugfix on 0.2.0.3-alpha.
9877 o Code simplifications and refactoring:
9878 - Generate our manpage and HTML documentation using Asciidoc. This
9879 change should make it easier to maintain the documentation, and
9881 - Remove the --enable-iphone option. According to reports from Marco
9882 Bonetti, Tor builds fine without any special tweaking on recent
9883 iPhone SDK versions.
9884 - Removed some unnecessary files from the source distribution. The
9885 AUTHORS file has now been merged into the people page on the
9886 website. The roadmaps and design doc can now be found in the
9887 projects directory in svn.
9888 - Enabled various circuit build timeout constants to be controlled
9889 by consensus parameters. Also set better defaults for these
9890 parameters based on experimentation on broadband and simulated
9894 - The 'EXTENDCIRCUIT' control port command can now be used with
9895 a circ id of 0 and no path. This feature will cause Tor to build
9896 a new 'fast' general purpose circuit using its own path selection
9898 - Added a BUILDTIMEOUT_SET controller event to describe changes
9899 to the circuit build timeout.
9900 - Future-proof the controller protocol a bit by ignoring keyword
9901 arguments we do not recognize.
9902 - Expand homedirs passed to tor-checkkey. This should silence a
9903 coverity complaint about passing a user-supplied string into
9904 open() without checking it.
9907 Changes in version 0.2.1.25 - 2010-03-16
9908 Tor 0.2.1.25 fixes a regression introduced in 0.2.1.23 that could
9909 prevent relays from guessing their IP address correctly. It also fixes
9910 several minor potential security bugs.
9913 - Fix a regression from our patch for bug 1244 that caused relays
9914 to guess their IP address incorrectly if they didn't set Address
9915 in their torrc and/or their address fails to resolve. Bugfix on
9916 0.2.1.23; fixes bug 1269.
9917 - When freeing a session key, zero it out completely. We only zeroed
9918 the first ptrsize bytes. Bugfix on 0.0.2pre8. Discovered and
9919 patched by ekir. Fixes bug 1254.
9922 - Fix a dereference-then-NULL-check sequence when publishing
9923 descriptors. Bugfix on 0.2.1.5-alpha. Discovered by ekir; fixes
9925 - Fix another dereference-then-NULL-check sequence. Bugfix on
9926 0.2.1.14-rc. Discovered by ekir; fixes bug 1256.
9927 - Make sure we treat potentially not NUL-terminated strings correctly.
9928 Bugfix on 0.1.1.13-alpha. Discovered by rieo; fixes bug 1257.
9932 Changes in version 0.2.1.24 - 2010-02-21
9933 Tor 0.2.1.24 makes Tor work again on the latest OS X -- this time
9937 - Work correctly out-of-the-box with even more vendor-patched versions
9938 of OpenSSL. In particular, make it so Debian and OS X don't need
9939 customized patches to run/build.
9942 Changes in version 0.2.1.23 - 2010-02-13
9943 Tor 0.2.1.23 fixes a huge client-side performance bug, makes Tor work
9944 again on the latest OS X, and updates the location of a directory
9947 o Major bugfixes (performance):
9948 - We were selecting our guards uniformly at random, and then weighting
9949 which of our guards we'd use uniformly at random. This imbalance
9950 meant that Tor clients were severely limited on throughput (and
9951 probably latency too) by the first hop in their circuit. Now we
9952 select guards weighted by currently advertised bandwidth. We also
9953 automatically discard guards picked using the old algorithm. Fixes
9954 bug 1217; bugfix on 0.2.1.3-alpha. Found by Mike Perry.
9957 - Make Tor work again on the latest OS X: when deciding whether to
9958 use strange flags to turn TLS renegotiation on, detect the OpenSSL
9959 version at run-time, not compile time. We need to do this because
9960 Apple doesn't update its dev-tools headers when it updates its
9961 libraries in a security patch.
9962 - Fix a potential buffer overflow in lookup_last_hid_serv_request()
9963 that could happen on 32-bit platforms with 64-bit time_t. Also fix
9964 a memory leak when requesting a hidden service descriptor we've
9965 requested before. Fixes bug 1242, bugfix on 0.2.0.18-alpha. Found
9968 o Directory authority changes:
9969 - Change IP address for dannenberg (v3 directory authority), and
9970 remove moria2 (obsolete v1, v2 directory authority and v0 hidden
9971 service directory authority) from the list.
9974 - Refactor resolve_my_address() to not use gethostbyname() anymore.
9975 Fixes bug 1244; bugfix on 0.0.2pre25. Reported by Mike Mestnik.
9978 - Avoid a mad rush at the beginning of each month when each client
9979 rotates half of its guards. Instead we spread the rotation out
9980 throughout the month, but we still avoid leaving a precise timestamp
9981 in the state file about when we first picked the guard. Improves
9982 over the behavior introduced in 0.1.2.17.
9985 Changes in version 0.2.2.8-alpha - 2010-01-26
9986 Tor 0.2.2.8-alpha fixes a crash bug in 0.2.2.7-alpha that has been
9987 causing bridge relays to disappear. If you're running a bridge,
9991 - Fix a memory corruption bug on bridges that occured during the
9992 inclusion of stats data in extra-info descriptors. Also fix the
9993 interface for geoip_get_bridge_stats* to prevent similar bugs in
9994 the future. Diagnosis by Tas, patch by Karsten and Sebastian.
9995 Fixes bug 1208; bugfix on 0.2.2.7-alpha.
9998 - Ignore OutboundBindAddress when connecting to localhost.
9999 Connections to localhost need to come _from_ localhost, or else
10000 local servers (like DNS and outgoing HTTP/SOCKS proxies) will often
10004 Changes in version 0.2.2.7-alpha - 2010-01-19
10005 Tor 0.2.2.7-alpha fixes a huge client-side performance bug, as well
10006 as laying the groundwork for further relay-side performance fixes. It
10007 also starts cleaning up client behavior with respect to the EntryNodes,
10008 ExitNodes, and StrictNodes config options.
10010 This release also rotates two directory authority keys, due to a
10011 security breach of some of the Torproject servers.
10013 o Directory authority changes:
10014 - Rotate keys (both v3 identity and relay identity) for moria1
10017 o Major features (performance):
10018 - We were selecting our guards uniformly at random, and then weighting
10019 which of our guards we'd use uniformly at random. This imbalance
10020 meant that Tor clients were severely limited on throughput (and
10021 probably latency too) by the first hop in their circuit. Now we
10022 select guards weighted by currently advertised bandwidth. We also
10023 automatically discard guards picked using the old algorithm. Fixes
10024 bug 1217; bugfix on 0.2.1.3-alpha. Found by Mike Perry.
10025 - When choosing which cells to relay first, relays can now favor
10026 circuits that have been quiet recently, to provide lower latency
10027 for low-volume circuits. By default, relays enable or disable this
10028 feature based on a setting in the consensus. You can override
10029 this default by using the new "CircuitPriorityHalflife" config
10030 option. Design and code by Ian Goldberg, Can Tang, and Chris
10032 - Add separate per-conn write limiting to go with the per-conn read
10033 limiting. We added a global write limit in Tor 0.1.2.5-alpha,
10034 but never per-conn write limits.
10035 - New consensus params "bwconnrate" and "bwconnburst" to let us
10036 rate-limit client connections as they enter the network. It's
10037 controlled in the consensus so we can turn it on and off for
10038 experiments. It's starting out off. Based on proposal 163.
10040 o Major features (relay selection options):
10041 - Switch to a StrictNodes config option, rather than the previous
10042 "StrictEntryNodes" / "StrictExitNodes" separation that was missing a
10043 "StrictExcludeNodes" option.
10044 - If EntryNodes, ExitNodes, ExcludeNodes, or ExcludeExitNodes
10045 change during a config reload, mark and discard all our origin
10046 circuits. This fix should address edge cases where we change the
10047 config options and but then choose a circuit that we created before
10049 - If EntryNodes or ExitNodes are set, be more willing to use an
10050 unsuitable (e.g. slow or unstable) circuit. The user asked for it,
10052 - Make EntryNodes config option much more aggressive even when
10053 StrictNodes is not set. Before it would prepend your requested
10054 entrynodes to your list of guard nodes, but feel free to use others
10055 after that. Now it chooses only from your EntryNodes if any of
10056 those are available, and only falls back to others if a) they're
10057 all down and b) StrictNodes is not set.
10058 - Now we refresh your entry guards from EntryNodes at each consensus
10059 fetch -- rather than just at startup and then they slowly rot as
10060 the network changes.
10063 - Stop bridge directory authorities from answering dbg-stability.txt
10064 directory queries, which would let people fetch a list of all
10065 bridge identities they track. Bugfix on 0.2.1.6-alpha.
10068 - Log a notice when we get a new control connection. Now it's easier
10069 for security-conscious users to recognize when a local application
10070 is knocking on their controller door. Suggested by bug 1196.
10071 - New config option "CircuitStreamTimeout" to override our internal
10072 timeout schedule for how many seconds until we detach a stream from
10073 a circuit and try a new circuit. If your network is particularly
10074 slow, you might want to set this to a number like 60.
10075 - New controller command "getinfo config-text". It returns the
10076 contents that Tor would write if you send it a SAVECONF command,
10077 so the controller can write the file to disk itself.
10078 - New options for SafeLogging to allow scrubbing only log messages
10079 generated while acting as a relay.
10080 - Ship the bridges spec file in the tarball too.
10081 - Avoid a mad rush at the beginning of each month when each client
10082 rotates half of its guards. Instead we spread the rotation out
10083 throughout the month, but we still avoid leaving a precise timestamp
10084 in the state file about when we first picked the guard. Improves
10085 over the behavior introduced in 0.1.2.17.
10087 o Minor bugfixes (compiling):
10088 - Fix compilation on OS X 10.3, which has a stub mlockall() but
10089 hides it. Bugfix on 0.2.2.6-alpha.
10090 - Fix compilation on Solaris by removing support for the
10091 DisableAllSwap config option. Solaris doesn't have an rlimit for
10092 mlockall, so we cannot use it safely. Fixes bug 1198; bugfix on
10095 o Minor bugfixes (crashes):
10096 - Do not segfault when writing buffer stats when we haven't observed
10097 a single circuit to report about. Found by Fabian Lanze. Bugfix on
10099 - If we're in the pathological case where there's no exit bandwidth
10100 but there is non-exit bandwidth, or no guard bandwidth but there
10101 is non-guard bandwidth, don't crash during path selection. Bugfix
10103 - Fix an impossible-to-actually-trigger buffer overflow in relay
10104 descriptor generation. Bugfix on 0.1.0.15.
10106 o Minor bugfixes (privacy):
10107 - Fix an instance where a Tor directory mirror might accidentally
10108 log the IP address of a misbehaving Tor client. Bugfix on
10110 - Don't list Windows capabilities in relay descriptors. We never made
10111 use of them, and maybe it's a bad idea to publish them. Bugfix
10114 o Minor bugfixes (other):
10115 - Resolve an edge case in path weighting that could make us misweight
10116 our relay selection. Fixes bug 1203; bugfix on 0.0.8rc1.
10117 - Fix statistics on client numbers by country as seen by bridges that
10118 were broken in 0.2.2.1-alpha. Also switch to reporting full 24-hour
10119 intervals instead of variable 12-to-48-hour intervals.
10120 - After we free an internal connection structure, overwrite it
10121 with a different memory value than we use for overwriting a freed
10122 internal circuit structure. Should help with debugging. Suggested
10124 - Update our OpenSSL 0.9.8l fix so that it works with OpenSSL 0.9.8m
10127 o Removed features:
10128 - Remove the HSAuthorityRecordStats option that version 0 hidden
10129 service authorities could have used to track statistics of overall
10130 hidden service usage.
10133 Changes in version 0.2.1.22 - 2010-01-19
10134 Tor 0.2.1.22 fixes a critical privacy problem in bridge directory
10135 authorities -- it would tell you its whole history of bridge descriptors
10136 if you make the right directory request. This stable update also
10137 rotates two of the seven v3 directory authority keys and locations.
10139 o Directory authority changes:
10140 - Rotate keys (both v3 identity and relay identity) for moria1
10144 - Stop bridge directory authorities from answering dbg-stability.txt
10145 directory queries, which would let people fetch a list of all
10146 bridge identities they track. Bugfix on 0.2.1.6-alpha.
10149 Changes in version 0.2.1.21 - 2009-12-21
10150 Tor 0.2.1.21 fixes an incompatibility with the most recent OpenSSL
10151 library. If you use Tor on Linux / Unix and you're getting SSL
10152 renegotiation errors, upgrading should help. We also recommend an
10153 upgrade if you're an exit relay.
10156 - Work around a security feature in OpenSSL 0.9.8l that prevents our
10157 handshake from working unless we explicitly tell OpenSSL that we
10158 are using SSL renegotiation safely. We are, of course, but OpenSSL
10159 0.9.8l won't work unless we say we are.
10160 - Avoid crashing if the client is trying to upload many bytes and the
10161 circuit gets torn down at the same time, or if the flip side
10162 happens on the exit relay. Bugfix on 0.2.0.1-alpha; fixes bug 1150.
10165 - Do not refuse to learn about authority certs and v2 networkstatus
10166 documents that are older than the latest consensus. This bug might
10167 have degraded client bootstrapping. Bugfix on 0.2.0.10-alpha.
10168 Spotted and fixed by xmux.
10169 - Fix a couple of very-hard-to-trigger memory leaks, and one hard-to-
10170 trigger platform-specific option misparsing case found by Coverity
10172 - Fix a compilation warning on Fedora 12 by removing an impossible-to-
10173 trigger assert. Fixes bug 1173.
10176 Changes in version 0.2.2.6-alpha - 2009-11-19
10177 Tor 0.2.2.6-alpha lays the groundwork for many upcoming features:
10178 support for the new lower-footprint "microdescriptor" directory design,
10179 future-proofing our consensus format against new hash functions or
10180 other changes, and an Android port. It also makes Tor compatible with
10181 the upcoming OpenSSL 0.9.8l release, and fixes a variety of bugs.
10184 - Directory authorities can now create, vote on, and serve multiple
10185 parallel formats of directory data as part of their voting process.
10186 Partially implements Proposal 162: "Publish the consensus in
10188 - Directory authorities can now agree on and publish small summaries
10189 of router information that clients can use in place of regular
10190 server descriptors. This transition will eventually allow clients
10191 to use far less bandwidth for downloading information about the
10192 network. Begins the implementation of Proposal 158: "Clients
10193 download consensus + microdescriptors".
10194 - The directory voting system is now extensible to use multiple hash
10195 algorithms for signatures and resource selection. Newer formats
10196 are signed with SHA256, with a possibility for moving to a better
10197 hash algorithm in the future.
10198 - New DisableAllSwap option. If set to 1, Tor will attempt to lock all
10199 current and future memory pages via mlockall(). On supported
10200 platforms (modern Linux and probably BSD but not Windows or OS X),
10201 this should effectively disable any and all attempts to page out
10202 memory. This option requires that you start your Tor as root --
10203 if you use DisableAllSwap, please consider using the User option
10204 to properly reduce the privileges of your Tor.
10205 - Numerous changes, bugfixes, and workarounds from Nathan Freitas
10206 to help Tor build correctly for Android phones.
10209 - Work around a security feature in OpenSSL 0.9.8l that prevents our
10210 handshake from working unless we explicitly tell OpenSSL that we
10211 are using SSL renegotiation safely. We are, but OpenSSL 0.9.8l
10212 won't work unless we say we are.
10215 - Fix a crash bug when trying to initialize the evdns module in
10216 Libevent 2. Bugfix on 0.2.1.16-rc.
10217 - Stop logging at severity 'warn' when some other Tor client tries
10218 to establish a circuit with us using weak DH keys. It's a protocol
10219 violation, but that doesn't mean ordinary users need to hear about
10220 it. Fixes the bug part of bug 1114. Bugfix on 0.1.0.13.
10221 - Do not refuse to learn about authority certs and v2 networkstatus
10222 documents that are older than the latest consensus. This bug might
10223 have degraded client bootstrapping. Bugfix on 0.2.0.10-alpha.
10224 Spotted and fixed by xmux.
10225 - Fix numerous small code-flaws found by Coverity Scan Rung 3.
10226 - If all authorities restart at once right before a consensus vote,
10227 nobody will vote about "Running", and clients will get a consensus
10228 with no usable relays. Instead, authorities refuse to build a
10229 consensus if this happens. Bugfix on 0.2.0.10-alpha; fixes bug 1066.
10230 - If your relay can't keep up with the number of incoming create
10231 cells, it would log one warning per failure into your logs. Limit
10232 warnings to 1 per minute. Bugfix on 0.0.2pre10; fixes bug 1042.
10233 - Bridges now use "reject *:*" as their default exit policy. Bugfix
10234 on 0.2.0.3-alpha; fixes bug 1113.
10235 - Fix a memory leak on directory authorities during voting that was
10236 introduced in 0.2.2.1-alpha. Found via valgrind.
10239 Changes in version 0.2.1.20 - 2009-10-15
10240 Tor 0.2.1.20 fixes a crash bug when you're accessing many hidden
10241 services at once, prepares for more performance improvements, and
10242 fixes a bunch of smaller bugs.
10244 The Windows and OS X bundles also include a more recent Vidalia,
10245 and switch from Privoxy to Polipo.
10247 The OS X installers are now drag and drop. It's best to un-install
10248 Tor/Vidalia and then install this new bundle, rather than upgrade. If
10249 you want to upgrade, you'll need to update the paths for Tor and Polipo
10250 in the Vidalia Settings window.
10253 - Send circuit or stream sendme cells when our window has decreased
10254 by 100 cells, not when it has decreased by 101 cells. Bug uncovered
10255 by Karsten when testing the "reduce circuit window" performance
10256 patch. Bugfix on the 54th commit on Tor -- from July 2002,
10257 before the release of Tor 0.0.0. This is the new winner of the
10259 - Fix a remotely triggerable memory leak when a consensus document
10260 contains more than one signature from the same voter. Bugfix on
10262 - Avoid segfault in rare cases when finishing an introduction circuit
10263 as a client and finding out that we don't have an introduction key
10264 for it. Fixes bug 1073. Reported by Aaron Swartz.
10267 - Tor now reads the "circwindow" parameter out of the consensus,
10268 and uses that value for its circuit package window rather than the
10269 default of 1000 cells. Begins the implementation of proposal 168.
10271 o New directory authorities:
10272 - Set up urras (run by Jacob Appelbaum) as the seventh v3 directory
10274 - Move moria1 and tonga to alternate IP addresses.
10277 - Fix a signed/unsigned compile warning in 0.2.1.19.
10278 - Fix possible segmentation fault on directory authorities. Bugfix on
10280 - Fix an extremely rare infinite recursion bug that could occur if
10281 we tried to log a message after shutting down the log subsystem.
10282 Found by Matt Edman. Bugfix on 0.2.0.16-alpha.
10283 - Fix an obscure bug where hidden services on 64-bit big-endian
10284 systems might mis-read the timestamp in v3 introduce cells, and
10285 refuse to connect back to the client. Discovered by "rotor".
10286 Bugfix on 0.2.1.6-alpha.
10287 - We were triggering a CLOCK_SKEW controller status event whenever
10288 we connect via the v2 connection protocol to any relay that has
10289 a wrong clock. Instead, we should only inform the controller when
10290 it's a trusted authority that claims our clock is wrong. Bugfix
10291 on 0.2.0.20-rc; starts to fix bug 1074. Reported by SwissTorExit.
10292 - We were telling the controller about CHECKING_REACHABILITY and
10293 REACHABILITY_FAILED status events whenever we launch a testing
10294 circuit or notice that one has failed. Instead, only tell the
10295 controller when we want to inform the user of overall success or
10296 overall failure. Bugfix on 0.1.2.6-alpha. Fixes bug 1075. Reported
10298 - Don't warn when we're using a circuit that ends with a node
10299 excluded in ExcludeExitNodes, but the circuit is not used to access
10300 the outside world. This should help fix bug 1090. Bugfix on
10302 - Work around a small memory leak in some versions of OpenSSL that
10303 stopped the memory used by the hostname TLS extension from being
10307 - Add a "getinfo status/accepted-server-descriptor" controller
10308 command, which is the recommended way for controllers to learn
10309 whether our server descriptor has been successfully received by at
10310 least on directory authority. Un-recommend good-server-descriptor
10311 getinfo and status events until we have a better design for them.
10314 Changes in version 0.2.2.5-alpha - 2009-10-11
10315 Tor 0.2.2.5-alpha fixes a few compile problems in 0.2.2.4-alpha.
10318 - Make the tarball compile again. Oops. Bugfix on 0.2.2.4-alpha.
10320 o Directory authorities:
10321 - Temporarily (just for this release) move dizum to an alternate
10325 Changes in version 0.2.2.4-alpha - 2009-10-10
10326 Tor 0.2.2.4-alpha fixes more crash bugs in 0.2.2.2-alpha. It also
10327 introduces a new unit test framework, shifts directry authority
10328 addresses around to reduce the impact from recent blocking events,
10329 and fixes a few smaller bugs.
10332 - Fix several more asserts in the circuit_build_times code, for
10333 example one that causes Tor to fail to start once we have
10334 accumulated 5000 build times in the state file. Bugfixes on
10335 0.2.2.2-alpha; fixes bug 1108.
10337 o New directory authorities:
10338 - Move moria1 and Tonga to alternate IP addresses.
10341 - Log SSL state transitions at debug level during handshake, and
10342 include SSL states in error messages. This may help debug future
10343 SSL handshake issues.
10344 - Add a new "Handshake" log domain for activities that happen
10345 during the TLS handshake.
10346 - Revert to the "June 3 2009" ip-to-country file. The September one
10347 seems to have removed most US IP addresses.
10348 - Directory authorities now reject Tor relays with versions less than
10349 0.1.2.14. This step cuts out four relays from the current network,
10350 none of which are very big.
10353 - Fix a couple of smaller issues with gathering statistics. Bugfixes
10355 - Fix two memory leaks in the error case of
10356 circuit_build_times_parse_state(). Bugfix on 0.2.2.2-alpha.
10357 - Don't count one-hop circuits when we're estimating how long it
10358 takes circuits to build on average. Otherwise we'll set our circuit
10359 build timeout lower than we should. Bugfix on 0.2.2.2-alpha.
10360 - Directory authorities no longer change their opinion of, or vote on,
10361 whether a router is Running, unless they have themselves been
10362 online long enough to have some idea. Bugfix on 0.2.0.6-alpha.
10365 o Code simplifications and refactoring:
10366 - Revise our unit tests to use the "tinytest" framework, so we
10367 can run tests in their own processes, have smarter setup/teardown
10368 code, and so on. The unit test code has moved to its own
10369 subdirectory, and has been split into multiple modules.
10372 Changes in version 0.2.2.3-alpha - 2009-09-23
10373 Tor 0.2.2.3-alpha fixes a few crash bugs in 0.2.2.2-alpha.
10376 - Fix an overzealous assert in our new circuit build timeout code.
10377 Bugfix on 0.2.2.2-alpha; fixes bug 1103.
10380 - If the networkstatus consensus tells us that we should use a
10381 negative circuit package window, ignore it. Otherwise we'll
10382 believe it and then trigger an assert. Bugfix on 0.2.2.2-alpha.
10385 Changes in version 0.2.2.2-alpha - 2009-09-21
10386 Tor 0.2.2.2-alpha introduces our latest performance improvement for
10387 clients: Tor tracks the average time it takes to build a circuit, and
10388 avoids using circuits that take too long to build. For fast connections,
10389 this feature can cut your expected latency in half. For slow or flaky
10390 connections, it could ruin your Tor experience. Let us know if it does!
10393 - Tor now tracks how long it takes to build client-side circuits
10394 over time, and adapts its timeout to local network performance.
10395 Since a circuit that takes a long time to build will also provide
10396 bad performance, we get significant latency improvements by
10397 discarding the slowest 20% of circuits. Specifically, Tor creates
10398 circuits more aggressively than usual until it has enough data
10399 points for a good timeout estimate. Implements proposal 151.
10400 We are especially looking for reports (good and bad) from users with
10401 both EDGE and broadband connections that can move from broadband
10402 to EDGE and find out if the build-time data in the .tor/state gets
10403 reset without loss of Tor usability. You should also see a notice
10404 log message telling you that Tor has reset its timeout.
10405 - Directory authorities can now vote on arbitary integer values as
10406 part of the consensus process. This is designed to help set
10407 network-wide parameters. Implements proposal 167.
10408 - Tor now reads the "circwindow" parameter out of the consensus,
10409 and uses that value for its circuit package window rather than the
10410 default of 1000 cells. Begins the implementation of proposal 168.
10413 - Fix a remotely triggerable memory leak when a consensus document
10414 contains more than one signature from the same voter. Bugfix on
10418 - Fix an extremely rare infinite recursion bug that could occur if
10419 we tried to log a message after shutting down the log subsystem.
10420 Found by Matt Edman. Bugfix on 0.2.0.16-alpha.
10421 - Fix parsing for memory or time units given without a space between
10422 the number and the unit. Bugfix on 0.2.2.1-alpha; fixes bug 1076.
10423 - A networkstatus vote must contain exactly one signature. Spec
10424 conformance issue. Bugfix on 0.2.0.3-alpha.
10425 - Fix an obscure bug where hidden services on 64-bit big-endian
10426 systems might mis-read the timestamp in v3 introduce cells, and
10427 refuse to connect back to the client. Discovered by "rotor".
10428 Bugfix on 0.2.1.6-alpha.
10429 - We were triggering a CLOCK_SKEW controller status event whenever
10430 we connect via the v2 connection protocol to any relay that has
10431 a wrong clock. Instead, we should only inform the controller when
10432 it's a trusted authority that claims our clock is wrong. Bugfix
10433 on 0.2.0.20-rc; starts to fix bug 1074. Reported by SwissTorExit.
10434 - We were telling the controller about CHECKING_REACHABILITY and
10435 REACHABILITY_FAILED status events whenever we launch a testing
10436 circuit or notice that one has failed. Instead, only tell the
10437 controller when we want to inform the user of overall success or
10438 overall failure. Bugfix on 0.1.2.6-alpha. Fixes bug 1075. Reported
10440 - Don't warn when we're using a circuit that ends with a node
10441 excluded in ExcludeExitNodes, but the circuit is not used to access
10442 the outside world. This should help fix bug 1090, but more problems
10443 remain. Bugfix on 0.2.1.6-alpha.
10444 - Work around a small memory leak in some versions of OpenSSL that
10445 stopped the memory used by the hostname TLS extension from being
10447 - Make our 'torify' script more portable; if we have only one of
10448 'torsocks' or 'tsocks' installed, don't complain to the user;
10449 and explain our warning about tsocks better.
10452 - Add a "getinfo status/accepted-server-descriptor" controller
10453 command, which is the recommended way for controllers to learn
10454 whether our server descriptor has been successfully received by at
10455 least on directory authority. Un-recommend good-server-descriptor
10456 getinfo and status events until we have a better design for them.
10457 - Update to the "September 4 2009" ip-to-country file.
10460 Changes in version 0.2.2.1-alpha - 2009-08-26
10461 Tor 0.2.2.1-alpha disables ".exit" address notation by default, allows
10462 Tor clients to bootstrap on networks where only port 80 is reachable,
10463 makes it more straightforward to support hardware crypto accelerators,
10464 and starts the groundwork for gathering stats safely at relays.
10467 - Start the process of disabling ".exit" address notation, since it
10468 can be used for a variety of esoteric application-level attacks
10469 on users. To reenable it, set "AllowDotExit 1" in your torrc. Fix
10472 o New directory authorities:
10473 - Set up urras (run by Jacob Appelbaum) as the seventh v3 directory
10477 - New AccelName and AccelDir options add support for dynamic OpenSSL
10478 hardware crypto acceleration engines.
10479 - Tor now supports tunneling all of its outgoing connections over
10480 a SOCKS proxy, using the SOCKS4Proxy and/or SOCKS5Proxy
10481 configuration options. Code by Christopher Davis.
10484 - Send circuit or stream sendme cells when our window has decreased
10485 by 100 cells, not when it has decreased by 101 cells. Bug uncovered
10486 by Karsten when testing the "reduce circuit window" performance
10487 patch. Bugfix on the 54th commit on Tor -- from July 2002,
10488 before the release of Tor 0.0.0. This is the new winner of the
10491 o New options for gathering stats safely:
10492 - Directory mirrors that set "DirReqStatistics 1" write statistics
10493 about directory requests to disk every 24 hours. As compared to the
10494 --enable-geoip-stats flag in 0.2.1.x, there are a few improvements:
10495 1) stats are written to disk exactly every 24 hours; 2) estimated
10496 shares of v2 and v3 requests are determined as mean values, not at
10497 the end of a measurement period; 3) unresolved requests are listed
10498 with country code '??'; 4) directories also measure download times.
10499 - Exit nodes that set "ExitPortStatistics 1" write statistics on the
10500 number of exit streams and transferred bytes per port to disk every
10502 - Relays that set "CellStatistics 1" write statistics on how long
10503 cells spend in their circuit queues to disk every 24 hours.
10504 - Entry nodes that set "EntryStatistics 1" write statistics on the
10505 rough number and origins of connecting clients to disk every 24
10507 - Relays that write any of the above statistics to disk and set
10508 "ExtraInfoStatistics 1" include the past 24 hours of statistics in
10509 their extra-info documents.
10512 - New --digests command-line switch to output the digests of the
10513 source files Tor was built with.
10514 - The "torify" script now uses torsocks where available.
10515 - The memarea code now uses a sentinel value at the end of each area
10516 to make sure nothing writes beyond the end of an area. This might
10517 help debug some conceivable causes of bug 930.
10518 - Time and memory units in the configuration file can now be set to
10519 fractional units. For example, "2.5 GB" is now a valid value for
10521 - Certain Tor clients (such as those behind check.torproject.org) may
10522 want to fetch the consensus in an extra early manner. To enable this
10523 a user may now set FetchDirInfoExtraEarly to 1. This also depends on
10524 setting FetchDirInfoEarly to 1. Previous behavior will stay the same
10525 as only certain clients who must have this information sooner should
10527 - Instead of adding the svn revision to the Tor version string, report
10528 the git commit (when we're building from a git checkout).
10531 - If any of the v3 certs we download are unparseable, we should
10532 actually notice the failure so we don't retry indefinitely. Bugfix
10533 on 0.2.0.x; reported by "rotator".
10534 - If the cached cert file is unparseable, warn but don't exit.
10535 - Fix possible segmentation fault on directory authorities. Bugfix on
10537 - When Tor fails to parse a descriptor of any kind, dump it to disk.
10538 Might help diagnosing bug 1051.
10540 o Deprecated and removed features:
10541 - The controller no longer accepts the old obsolete "addr-mappings/"
10542 or "unregistered-servers-" GETINFO values.
10543 - Hidden services no longer publish version 0 descriptors, and clients
10544 do not request or use version 0 descriptors. However, the old hidden
10545 service authorities still accept and serve version 0 descriptors
10546 when contacted by older hidden services/clients.
10547 - The EXTENDED_EVENTS and VERBOSE_NAMES controller features are now
10548 always on; using them is necessary for correct forward-compatible
10550 - Remove support for .noconnect style addresses. Nobody was using
10551 them, and they provided another avenue for detecting Tor users
10552 via application-level web tricks.
10554 o Packaging changes:
10555 - Upgrade Vidalia from 0.1.15 to 0.2.3 in the Windows and OS X
10556 installer bundles. See
10557 https://trac.vidalia-project.net/browser/vidalia/tags/vidalia-0.2.3/CHANGELOG
10558 for details of what's new in Vidalia 0.2.3.
10559 - Windows Vidalia Bundle: update Privoxy from 3.0.6 to 3.0.14-beta.
10560 - OS X Vidalia Bundle: move to Polipo 1.0.4 with Tor specific
10561 configuration file, rather than the old Privoxy.
10562 - OS X Vidalia Bundle: Vidalia, Tor, and Polipo are compiled as
10563 x86-only for better compatibility with OS X 10.6, aka Snow Leopard.
10564 - OS X Tor Expert Bundle: Tor is compiled as x86-only for
10565 better compatibility with OS X 10.6, aka Snow Leopard.
10566 - OS X Vidalia Bundle: The multi-package installer is now replaced
10567 by a simple drag and drop to the /Applications folder. This change
10568 occurred with the upgrade to Vidalia 0.2.3.
10571 Changes in version 0.2.1.19 - 2009-07-28
10572 Tor 0.2.1.19 fixes a major bug with accessing and providing hidden
10573 services on Tor 0.2.1.3-alpha through 0.2.1.18.
10576 - Make accessing hidden services on 0.2.1.x work right again.
10577 Bugfix on 0.2.1.3-alpha; workaround for bug 1038. Diagnosis and
10578 part of patch provided by "optimist".
10581 - When a relay/bridge is writing out its identity key fingerprint to
10582 the "fingerprint" file and to its logs, write it without spaces. Now
10583 it will look like the fingerprints in our bridges documentation,
10584 and confuse fewer users.
10587 - Relays no longer publish a new server descriptor if they change
10588 their MaxAdvertisedBandwidth config option but it doesn't end up
10589 changing their advertised bandwidth numbers. Bugfix on 0.2.0.28-rc;
10590 fixes bug 1026. Patch from Sebastian.
10591 - Avoid leaking memory every time we get a create cell but we have
10592 so many already queued that we refuse it. Bugfix on 0.2.0.19-alpha;
10593 fixes bug 1034. Reported by BarkerJr.
10596 Changes in version 0.2.1.18 - 2009-07-24
10597 Tor 0.2.1.18 lays the foundations for performance improvements,
10598 adds status events to help users diagnose bootstrap problems, adds
10599 optional authentication/authorization for hidden services, fixes a
10600 variety of potential anonymity problems, and includes a huge pile of
10601 other features and bug fixes.
10604 - Add LIBS=-lrt to Makefile.am so the Tor RPMs use a static libevent.
10607 Changes in version 0.2.1.17-rc - 2009-07-07
10608 Tor 0.2.1.17-rc marks the fourth -- and hopefully last -- release
10609 candidate for the 0.2.1.x series. It lays the groundwork for further
10610 client performance improvements, and also fixes a big bug with directory
10611 authorities that were causing them to assign Guard and Stable flags
10614 The Windows bundles also finally include the geoip database that we
10615 thought we'd been shipping since 0.2.0.x (oops), and the OS X bundles
10616 should actually install Torbutton rather than giving you a cryptic
10617 failure message (oops).
10620 - Clients now use the bandwidth values in the consensus, rather than
10621 the bandwidth values in each relay descriptor. This approach opens
10622 the door to more accurate bandwidth estimates once the directory
10623 authorities start doing active measurements. Implements more of
10627 - When Tor clients restart after 1-5 days, they discard all their
10628 cached descriptors as too old, but they still use the cached
10629 consensus document. This approach is good for robustness, but
10630 bad for performance: since they don't know any bandwidths, they
10631 end up choosing at random rather than weighting their choice by
10632 speed. Fixed by the above feature of putting bandwidths in the
10633 consensus. Bugfix on 0.2.0.x.
10634 - Directory authorities were neglecting to mark relays down in their
10635 internal histories if the relays fall off the routerlist without
10636 ever being found unreachable. So there were relays in the histories
10637 that haven't been seen for eight months, and are listed as being
10638 up for eight months. This wreaked havoc on the "median wfu"
10639 and "median mtbf" calculations, in turn making Guard and Stable
10640 flags very wrong, hurting network performance. Fixes bugs 696 and
10641 969. Bugfix on 0.2.0.6-alpha.
10644 - Serve the DirPortFrontPage page even when we have been approaching
10645 our quotas recently. Fixes bug 1013; bugfix on 0.2.1.8-alpha.
10646 - The control port would close the connection before flushing long
10647 replies, such as the network consensus, if a QUIT command was issued
10648 before the reply had completed. Now, the control port flushes all
10649 pending replies before closing the connection. Also fixed a spurious
10650 warning when a QUIT command is issued after a malformed or rejected
10651 AUTHENTICATE command, but before the connection was closed. Patch
10652 by Marcus Griep. Bugfix on 0.2.0.x; fixes bugs 1015 and 1016.
10653 - When we can't find an intro key for a v2 hidden service descriptor,
10654 fall back to the v0 hidden service descriptor and log a bug message.
10655 Workaround for bug 1024.
10656 - Fix a log message that did not respect the SafeLogging option.
10660 - If we're a relay and we change our IP address, be more verbose
10661 about the reason that made us change. Should help track down
10662 further bugs for relays on dynamic IP addresses.
10665 Changes in version 0.2.0.35 - 2009-06-24
10667 - Avoid crashing in the presence of certain malformed descriptors.
10668 Found by lark, and by automated fuzzing.
10669 - Fix an edge case where a malicious exit relay could convince a
10670 controller that the client's DNS question resolves to an internal IP
10671 address. Bug found and fixed by "optimist"; bugfix on 0.1.2.8-beta.
10674 - Finally fix the bug where dynamic-IP relays disappear when their
10675 IP address changes: directory mirrors were mistakenly telling
10676 them their old address if they asked via begin_dir, so they
10677 never got an accurate answer about their new address, so they
10678 just vanished after a day. For belt-and-suspenders, relays that
10679 don't set Address in their config now avoid using begin_dir for
10680 all direct connections. Should fix bugs 827, 883, and 900.
10681 - Fix a timing-dependent, allocator-dependent, DNS-related crash bug
10682 that would occur on some exit nodes when DNS failures and timeouts
10683 occurred in certain patterns. Fix for bug 957.
10686 - When starting with a cache over a few days old, do not leak
10687 memory for the obsolete router descriptors in it. Bugfix on
10688 0.2.0.33; fixes bug 672.
10689 - Hidden service clients didn't use a cached service descriptor that
10690 was older than 15 minutes, but wouldn't fetch a new one either,
10691 because there was already one in the cache. Now, fetch a v2
10692 descriptor unless the same descriptor was added to the cache within
10693 the last 15 minutes. Fixes bug 997; reported by Marcus Griep.
10696 Changes in version 0.2.1.16-rc - 2009-06-20
10697 Tor 0.2.1.16-rc speeds up performance for fast exit relays, and fixes
10698 a bunch of minor bugs.
10701 - Fix an edge case where a malicious exit relay could convince a
10702 controller that the client's DNS question resolves to an internal IP
10703 address. Bug found and fixed by "optimist"; bugfix on 0.1.2.8-beta.
10705 o Major performance improvements (on 0.2.0.x):
10706 - Disable and refactor some debugging checks that forced a linear scan
10707 over the whole server-side DNS cache. These accounted for over 50%
10708 of CPU time on a relatively busy exit node's gprof profile. Found
10710 - Disable some debugging checks that appeared in exit node profile
10714 - Update to the "June 3 2009" ip-to-country file.
10715 - Do not have tor-resolve automatically refuse all .onion addresses;
10716 if AutomapHostsOnResolve is set in your torrc, this will work fine.
10718 o Minor bugfixes (on 0.2.0.x):
10719 - Log correct error messages for DNS-related network errors on
10721 - Fix a race condition that could cause crashes or memory corruption
10722 when running as a server with a controller listening for log
10724 - Avoid crashing when we have a policy specified in a DirPolicy or
10725 SocksPolicy or ReachableAddresses option with ports set on it,
10726 and we re-load the policy. May fix bug 996.
10727 - Hidden service clients didn't use a cached service descriptor that
10728 was older than 15 minutes, but wouldn't fetch a new one either,
10729 because there was already one in the cache. Now, fetch a v2
10730 descriptor unless the same descriptor was added to the cache within
10731 the last 15 minutes. Fixes bug 997; reported by Marcus Griep.
10733 o Minor bugfixes (on 0.2.1.x):
10734 - Don't warn users about low port and hibernation mix when they
10735 provide a *ListenAddress directive to fix that. Bugfix on
10737 - When switching back and forth between bridge mode, do not start
10738 gathering GeoIP data until two hours have passed.
10739 - Do not complain that the user has requested an excluded node as
10740 an exit when the node is not really an exit. This could happen
10741 because the circuit was for testing, or an introduction point.
10745 Changes in version 0.2.1.15-rc - 2009-05-25
10746 Tor 0.2.1.15-rc marks the second release candidate for the 0.2.1.x
10747 series. It fixes a major bug on fast exit relays, as well as a variety
10748 of more minor bugs.
10750 o Major bugfixes (on 0.2.0.x):
10751 - Fix a timing-dependent, allocator-dependent, DNS-related crash bug
10752 that would occur on some exit nodes when DNS failures and timeouts
10753 occurred in certain patterns. Fix for bug 957.
10755 o Minor bugfixes (on 0.2.0.x):
10756 - Actually return -1 in the error case for read_bandwidth_usage().
10757 Harmless bug, since we currently don't care about the return value
10758 anywhere. Bugfix on 0.2.0.9-alpha.
10759 - Provide a more useful log message if bug 977 (related to buffer
10760 freelists) ever reappears, and do not crash right away.
10761 - Fix an assertion failure on 64-bit platforms when we allocated
10762 memory right up to the end of a memarea, then realigned the memory
10763 one step beyond the end. Fixes a possible cause of bug 930.
10764 - Protect the count of open sockets with a mutex, so we can't
10765 corrupt it when two threads are closing or opening sockets at once.
10766 Fix for bug 939. Bugfix on 0.2.0.1-alpha.
10767 - Don't allow a bridge to publish its router descriptor to a
10768 non-bridge directory authority. Fixes part of bug 932.
10769 - When we change to or from being a bridge, reset our counts of
10770 client usage by country. Fixes bug 932.
10771 - Fix a bug that made stream bandwidth get misreported to the
10773 - Stop using malloc_usable_size() to use more area than we had
10774 actually allocated: it was safe, but made valgrind really unhappy.
10775 - Fix a memory leak when v3 directory authorities load their keys
10776 and cert from disk. Bugfix on 0.2.0.1-alpha.
10778 o Minor bugfixes (on 0.2.1.x):
10779 - Fix use of freed memory when deciding to mark a non-addable
10780 descriptor as never-downloadable. Bugfix on 0.2.1.9-alpha.
10783 Changes in version 0.2.1.14-rc - 2009-04-12
10784 Tor 0.2.1.14-rc marks the first release candidate for the 0.2.1.x
10785 series. It begins fixing some major performance problems, and also
10786 finally addresses the bug that was causing relays on dynamic IP
10787 addresses to fall out of the directory.
10790 - Clients replace entry guards that were chosen more than a few months
10791 ago. This change should significantly improve client performance,
10792 especially once more people upgrade, since relays that have been
10793 a guard for a long time are currently overloaded.
10795 o Major bugfixes (on 0.2.0):
10796 - Finally fix the bug where dynamic-IP relays disappear when their
10797 IP address changes: directory mirrors were mistakenly telling
10798 them their old address if they asked via begin_dir, so they
10799 never got an accurate answer about their new address, so they
10800 just vanished after a day. For belt-and-suspenders, relays that
10801 don't set Address in their config now avoid using begin_dir for
10802 all direct connections. Should fix bugs 827, 883, and 900.
10803 - Relays were falling out of the networkstatus consensus for
10804 part of a day if they changed their local config but the
10805 authorities discarded their new descriptor as "not sufficiently
10806 different". Now directory authorities accept a descriptor as changed
10807 if bandwidthrate or bandwidthburst changed. Partial fix for bug 962;
10808 patch by Sebastian.
10809 - Avoid crashing in the presence of certain malformed descriptors.
10810 Found by lark, and by automated fuzzing.
10813 - When generating circuit events with verbose nicknames for
10814 controllers, try harder to look up nicknames for routers on a
10815 circuit. (Previously, we would look in the router descriptors we had
10816 for nicknames, but not in the consensus.) Partial fix for bug 941.
10817 - If the bridge config line doesn't specify a port, assume 443.
10818 This makes bridge lines a bit smaller and easier for users to
10820 - Raise the minimum bandwidth to be a relay from 20000 bytes to 20480
10821 bytes (aka 20KB/s), to match our documentation. Also update
10822 directory authorities so they always assign the Fast flag to relays
10823 with 20KB/s of capacity. Now people running relays won't suddenly
10824 find themselves not seeing any use, if the network gets faster
10826 - Update to the "April 3 2009" ip-to-country file.
10829 - Avoid trying to print raw memory to the logs when we decide to
10830 give up on downloading a given relay descriptor. Bugfix on
10832 - In tor-resolve, when the Tor client to use is specified by
10833 <hostname>:<port>, actually use the specified port rather than
10834 defaulting to 9050. Bugfix on 0.2.1.6-alpha.
10835 - Make directory usage recording work again. Bugfix on 0.2.1.6-alpha.
10836 - When starting with a cache over a few days old, do not leak
10837 memory for the obsolete router descriptors in it. Bugfix on
10839 - Avoid double-free on list of successfully uploaded hidden
10840 service discriptors. Fix for bug 948. Bugfix on 0.2.1.6-alpha.
10841 - Change memarea_strndup() implementation to work even when
10842 duplicating a string at the end of a page. This bug was
10843 harmless for now, but could have meant crashes later. Fix by
10844 lark. Bugfix on 0.2.1.1-alpha.
10845 - Limit uploaded directory documents to be 16M rather than 500K.
10846 The directory authorities were refusing v3 consensus votes from
10847 other authorities, since the votes are now 504K. Fixes bug 959;
10848 bugfix on 0.0.2pre17 (where we raised it from 50K to 500K ;).
10849 - Directory authorities should never send a 503 "busy" response to
10850 requests for votes or keys. Bugfix on 0.2.0.8-alpha; exposed by
10854 Changes in version 0.2.1.13-alpha - 2009-03-09
10855 Tor 0.2.1.13-alpha includes another big pile of minor bugfixes and
10856 cleanups. We're finally getting close to a release candidate.
10859 - Correctly update the list of which countries we exclude as
10860 exits, when the GeoIP file is loaded or reloaded. Diagnosed by
10861 lark. Bugfix on 0.2.1.6-alpha.
10863 o Minor bugfixes (on 0.2.0.x and earlier):
10864 - Automatically detect MacOSX versions earlier than 10.4.0, and
10865 disable kqueue from inside Tor when running with these versions.
10866 We previously did this from the startup script, but that was no
10867 help to people who didn't use the startup script. Resolves bug 863.
10868 - When we had picked an exit node for a connection, but marked it as
10869 "optional", and it turned out we had no onion key for the exit,
10870 stop wanting that exit and try again. This situation may not
10871 be possible now, but will probably become feasible with proposal
10872 158. Spotted by rovv. Fixes another case of bug 752.
10873 - Clients no longer cache certificates for authorities they do not
10874 recognize. Bugfix on 0.2.0.9-alpha.
10875 - When we can't transmit a DNS request due to a network error, retry
10876 it after a while, and eventually transmit a failing response to
10877 the RESOLVED cell. Bugfix on 0.1.2.5-alpha.
10878 - If the controller claimed responsibility for a stream, but that
10879 stream never finished making its connection, it would live
10880 forever in circuit_wait state. Now we close it after SocksTimeout
10881 seconds. Bugfix on 0.1.2.7-alpha; reported by Mike Perry.
10882 - Drop begin cells to a hidden service if they come from the middle
10883 of a circuit. Patch from lark.
10884 - When we erroneously receive two EXTEND cells for the same circuit
10885 ID on the same connection, drop the second. Patch from lark.
10886 - Fix a crash that occurs on exit nodes when a nameserver request
10887 timed out. Bugfix on 0.1.2.1-alpha; our CLEAR debugging code had
10888 been suppressing the bug since 0.1.2.10-alpha. Partial fix for
10890 - Do not assume that a stack-allocated character array will be
10891 64-bit aligned on platforms that demand that uint64_t access is
10892 aligned. Possible fix for bug 604.
10893 - Parse dates and IPv4 addresses in a locale- and libc-independent
10894 manner, to avoid platform-dependent behavior on malformed input.
10895 - Build correctly when configured to build outside the main source
10896 path. Patch from Michael Gold.
10897 - We were already rejecting relay begin cells with destination port
10898 of 0. Now also reject extend cells with destination port or address
10899 of 0. Suggested by lark.
10901 o Minor bugfixes (on 0.2.1.x):
10902 - Don't re-extend introduction circuits if we ran out of RELAY_EARLY
10903 cells. Bugfix on 0.2.1.3-alpha. Fixes more of bug 878.
10904 - If we're an exit node, scrub the IP address to which we are exiting
10905 in the logs. Bugfix on 0.2.1.8-alpha.
10908 - On Linux, use the prctl call to re-enable core dumps when the user
10910 - New controller event NEWCONSENSUS that lists the networkstatus
10911 lines for every recommended relay. Now controllers like Torflow
10912 can keep up-to-date on which relays they should be using.
10913 - Update to the "February 26 2009" ip-to-country file.
10916 Changes in version 0.2.0.34 - 2009-02-08
10917 Tor 0.2.0.34 features several more security-related fixes. You should
10918 upgrade, especially if you run an exit relay (remote crash) or a
10919 directory authority (remote infinite loop), or you're on an older
10920 (pre-XP) or not-recently-patched Windows (remote exploit).
10922 This release marks end-of-life for Tor 0.1.2.x. Those Tor versions
10923 have many known flaws, and nobody should be using them. You should
10924 upgrade. If you're using a Linux or BSD and its packages are obsolete,
10925 stop using those packages and upgrade anyway.
10928 - Fix an infinite-loop bug on handling corrupt votes under certain
10929 circumstances. Bugfix on 0.2.0.8-alpha.
10930 - Fix a temporary DoS vulnerability that could be performed by
10931 a directory mirror. Bugfix on 0.2.0.9-alpha; reported by lark.
10932 - Avoid a potential crash on exit nodes when processing malformed
10933 input. Remote DoS opportunity. Bugfix on 0.2.0.33.
10934 - Do not accept incomplete ipv4 addresses (like 192.168.0) as valid.
10935 Spec conformance issue. Bugfix on Tor 0.0.2pre27.
10938 - Fix compilation on systems where time_t is a 64-bit integer.
10939 Patch from Matthias Drochner.
10940 - Don't consider expiring already-closed client connections. Fixes
10941 bug 893. Bugfix on 0.0.2pre20.
10944 Changes in version 0.2.1.12-alpha - 2009-02-08
10945 Tor 0.2.1.12-alpha features several more security-related fixes. You
10946 should upgrade, especially if you run an exit relay (remote crash) or
10947 a directory authority (remote infinite loop), or you're on an older
10948 (pre-XP) or not-recently-patched Windows (remote exploit). It also
10949 includes a big pile of minor bugfixes and cleanups.
10952 - Fix an infinite-loop bug on handling corrupt votes under certain
10953 circumstances. Bugfix on 0.2.0.8-alpha.
10954 - Fix a temporary DoS vulnerability that could be performed by
10955 a directory mirror. Bugfix on 0.2.0.9-alpha; reported by lark.
10956 - Avoid a potential crash on exit nodes when processing malformed
10957 input. Remote DoS opportunity. Bugfix on 0.2.1.7-alpha.
10960 - Let controllers actually ask for the "clients_seen" event for
10961 getting usage summaries on bridge relays. Bugfix on 0.2.1.10-alpha;
10962 reported by Matt Edman.
10963 - Fix a compile warning on OSX Panther. Fixes bug 913; bugfix against
10965 - Fix a bug in address parsing that was preventing bridges or hidden
10966 service targets from being at IPv6 addresses.
10967 - Solve a bug that kept hardware crypto acceleration from getting
10968 enabled when accounting was turned on. Fixes bug 907. Bugfix on
10970 - Remove a bash-ism from configure.in to build properly on non-Linux
10971 platforms. Bugfix on 0.2.1.1-alpha.
10972 - Fix code so authorities _actually_ send back X-Descriptor-Not-New
10973 headers. Bugfix on 0.2.0.10-alpha.
10974 - Don't consider expiring already-closed client connections. Fixes
10975 bug 893. Bugfix on 0.0.2pre20.
10976 - Fix another interesting corner-case of bug 891 spotted by rovv:
10977 Previously, if two hosts had different amounts of clock drift, and
10978 one of them created a new connection with just the wrong timing,
10979 the other might decide to deprecate the new connection erroneously.
10980 Bugfix on 0.1.1.13-alpha.
10981 - Resolve a very rare crash bug that could occur when the user forced
10982 a nameserver reconfiguration during the middle of a nameserver
10983 probe. Fixes bug 526. Bugfix on 0.1.2.1-alpha.
10984 - Support changing value of ServerDNSRandomizeCase during SIGHUP.
10985 Bugfix on 0.2.1.7-alpha.
10986 - If we're using bridges and our network goes away, be more willing
10987 to forgive our bridges and try again when we get an application
10988 request. Bugfix on 0.2.0.x.
10991 - Support platforms where time_t is 64 bits long. (Congratulations,
10992 NetBSD!) Patch from Matthias Drochner.
10993 - Add a 'getinfo status/clients-seen' controller command, in case
10994 controllers want to hear clients_seen events but connect late.
10997 - Disable GCC's strict alias optimization by default, to avoid the
10998 likelihood of its introducing subtle bugs whenever our code violates
10999 the letter of C99's alias rules.
11002 Changes in version 0.2.0.33 - 2009-01-21
11003 Tor 0.2.0.33 fixes a variety of bugs that were making relays less
11004 useful to users. It also finally fixes a bug where a relay or client
11005 that's been off for many days would take a long time to bootstrap.
11007 This update also fixes an important security-related bug reported by
11008 Ilja van Sprundel. You should upgrade. (We'll send out more details
11009 about the bug once people have had some time to upgrade.)
11012 - Fix a heap-corruption bug that may be remotely triggerable on
11013 some platforms. Reported by Ilja van Sprundel.
11016 - When a stream at an exit relay is in state "resolving" or
11017 "connecting" and it receives an "end" relay cell, the exit relay
11018 would silently ignore the end cell and not close the stream. If
11019 the client never closes the circuit, then the exit relay never
11020 closes the TCP connection. Bug introduced in Tor 0.1.2.1-alpha;
11021 reported by "wood".
11022 - When sending CREATED cells back for a given circuit, use a 64-bit
11023 connection ID to find the right connection, rather than an addr:port
11024 combination. Now that we can have multiple OR connections between
11025 the same ORs, it is no longer possible to use addr:port to uniquely
11026 identify a connection.
11027 - Bridge relays that had DirPort set to 0 would stop fetching
11028 descriptors shortly after startup, and then briefly resume
11029 after a new bandwidth test and/or after publishing a new bridge
11030 descriptor. Bridge users that try to bootstrap from them would
11031 get a recent networkstatus but would get descriptors from up to
11032 18 hours earlier, meaning most of the descriptors were obsolete
11033 already. Reported by Tas; bugfix on 0.2.0.13-alpha.
11034 - Prevent bridge relays from serving their 'extrainfo' document
11035 to anybody who asks, now that extrainfo docs include potentially
11036 sensitive aggregated client geoip summaries. Bugfix on
11038 - If the cached networkstatus consensus is more than five days old,
11039 discard it rather than trying to use it. In theory it could be
11040 useful because it lists alternate directory mirrors, but in practice
11041 it just means we spend many minutes trying directory mirrors that
11042 are long gone from the network. Also discard router descriptors as
11043 we load them if they are more than five days old, since the onion
11044 key is probably wrong by now. Bugfix on 0.2.0.x. Fixes bug 887.
11047 - Do not mark smartlist_bsearch_idx() function as ATTR_PURE. This bug
11048 could make gcc generate non-functional binary search code. Bugfix
11050 - Build correctly on platforms without socklen_t.
11051 - Compile without warnings on solaris.
11052 - Avoid potential crash on internal error during signature collection.
11053 Fixes bug 864. Patch from rovv.
11054 - Correct handling of possible malformed authority signing key
11055 certificates with internal signature types. Fixes bug 880.
11056 Bugfix on 0.2.0.3-alpha.
11057 - Fix a hard-to-trigger resource leak when logging credential status.
11059 - When we can't initialize DNS because the network is down, do not
11060 automatically stop Tor from starting. Instead, we retry failed
11061 dns_init() every 10 minutes, and change the exit policy to reject
11062 *:* until one succeeds. Fixes bug 691.
11063 - Use 64 bits instead of 32 bits for connection identifiers used with
11064 the controller protocol, to greatly reduce risk of identifier reuse.
11065 - When we're choosing an exit node for a circuit, and we have
11066 no pending streams, choose a good general exit rather than one that
11067 supports "all the pending streams". Bugfix on 0.1.1.x. Fix by rovv.
11068 - Fix another case of assuming, when a specific exit is requested,
11069 that we know more than the user about what hosts it allows.
11070 Fixes one case of bug 752. Patch from rovv.
11071 - Clip the MaxCircuitDirtiness config option to a minimum of 10
11072 seconds. Warn the user if lower values are given in the
11073 configuration. Bugfix on 0.1.0.1-rc. Patch by Sebastian.
11074 - Clip the CircuitBuildTimeout to a minimum of 30 seconds. Warn the
11075 user if lower values are given in the configuration. Bugfix on
11076 0.1.1.17-rc. Patch by Sebastian.
11077 - Fix a memory leak when we decline to add a v2 rendezvous descriptor to
11078 the cache because we already had a v0 descriptor with the same ID.
11079 Bugfix on 0.2.0.18-alpha.
11080 - Fix a race condition when freeing keys shared between main thread
11081 and CPU workers that could result in a memory leak. Bugfix on
11082 0.1.0.1-rc. Fixes bug 889.
11083 - Send a valid END cell back when a client tries to connect to a
11084 nonexistent hidden service port. Bugfix on 0.1.2.15. Fixes bug
11085 840. Patch from rovv.
11086 - Check which hops rendezvous stream cells are associated with to
11087 prevent possible guess-the-streamid injection attacks from
11088 intermediate hops. Fixes another case of bug 446. Based on patch
11090 - If a broken client asks a non-exit router to connect somewhere,
11091 do not even do the DNS lookup before rejecting the connection.
11092 Fixes another case of bug 619. Patch from rovv.
11093 - When a relay gets a create cell it can't decrypt (e.g. because it's
11094 using the wrong onion key), we were dropping it and letting the
11095 client time out. Now actually answer with a destroy cell. Fixes
11096 bug 904. Bugfix on 0.0.2pre8.
11098 o Minor bugfixes (hidden services):
11099 - Do not throw away existing introduction points on SIGHUP. Bugfix on
11100 0.0.6pre1. Patch by Karsten. Fixes bug 874.
11103 - Report the case where all signatures in a detached set are rejected
11104 differently than the case where there is an error handling the
11106 - When we realize that another process has modified our cached
11107 descriptors, print out a more useful error message rather than
11108 triggering an assertion. Fixes bug 885. Patch from Karsten.
11109 - Implement the 0x20 hack to better resist DNS poisoning: set the
11110 case on outgoing DNS requests randomly, and reject responses that do
11111 not match the case correctly. This logic can be disabled with the
11112 ServerDNSRamdomizeCase setting, if you are using one of the 0.3%
11113 of servers that do not reliably preserve case in replies. See
11114 "Increased DNS Forgery Resistance through 0x20-Bit Encoding"
11116 - Check DNS replies for more matching fields to better resist DNS
11118 - Never use OpenSSL compression: it wastes RAM and CPU trying to
11119 compress cells, which are basically all encrypted, compressed, or
11123 Changes in version 0.2.1.11-alpha - 2009-01-20
11124 Tor 0.2.1.11-alpha finishes fixing the "if your Tor is off for a
11125 week it will take a long time to bootstrap again" bug. It also fixes
11126 an important security-related bug reported by Ilja van Sprundel. You
11127 should upgrade. (We'll send out more details about the bug once people
11128 have had some time to upgrade.)
11131 - Fix a heap-corruption bug that may be remotely triggerable on
11132 some platforms. Reported by Ilja van Sprundel.
11135 - Discard router descriptors as we load them if they are more than
11136 five days old. Otherwise if Tor is off for a long time and then
11137 starts with cached descriptors, it will try to use the onion
11138 keys in those obsolete descriptors when building circuits. Bugfix
11139 on 0.2.0.x. Fixes bug 887.
11142 - Try to make sure that the version of Libevent we're running with
11143 is binary-compatible with the one we built with. May address bug
11145 - Make setting ServerDNSRandomizeCase to 0 actually work. Bugfix
11146 for bug 905. Bugfix on 0.2.1.7-alpha.
11147 - Add a new --enable-local-appdata configuration switch to change
11148 the default location of the datadir on win32 from APPDATA to
11149 LOCAL_APPDATA. In the future, we should migrate to LOCAL_APPDATA
11150 entirely. Patch from coderman.
11153 - Make outbound DNS packets respect the OutboundBindAddress setting.
11154 Fixes the bug part of bug 798. Bugfix on 0.1.2.2-alpha.
11155 - When our circuit fails at the first hop (e.g. we get a destroy
11156 cell back), avoid using that OR connection anymore, and also
11157 tell all the one-hop directory requests waiting for it that they
11158 should fail. Bugfix on 0.2.1.3-alpha.
11159 - In the torify(1) manpage, mention that tsocks will leak your
11163 Changes in version 0.2.1.10-alpha - 2009-01-06
11164 Tor 0.2.1.10-alpha fixes two major bugs in bridge relays (one that
11165 would make the bridge relay not so useful if it had DirPort set to 0,
11166 and one that could let an attacker learn a little bit of information
11167 about the bridge's users), and a bug that would cause your Tor relay
11168 to ignore a circuit create request it can't decrypt (rather than reply
11169 with an error). It also fixes a wide variety of other bugs.
11172 - If the cached networkstatus consensus is more than five days old,
11173 discard it rather than trying to use it. In theory it could
11174 be useful because it lists alternate directory mirrors, but in
11175 practice it just means we spend many minutes trying directory
11176 mirrors that are long gone from the network. Helps bug 887 a bit;
11178 - Bridge relays that had DirPort set to 0 would stop fetching
11179 descriptors shortly after startup, and then briefly resume
11180 after a new bandwidth test and/or after publishing a new bridge
11181 descriptor. Bridge users that try to bootstrap from them would
11182 get a recent networkstatus but would get descriptors from up to
11183 18 hours earlier, meaning most of the descriptors were obsolete
11184 already. Reported by Tas; bugfix on 0.2.0.13-alpha.
11185 - Prevent bridge relays from serving their 'extrainfo' document
11186 to anybody who asks, now that extrainfo docs include potentially
11187 sensitive aggregated client geoip summaries. Bugfix on
11191 - New controller event "clients_seen" to report a geoip-based summary
11192 of which countries we've seen clients from recently. Now controllers
11193 like Vidalia can show bridge operators that they're actually making
11195 - Build correctly against versions of OpenSSL 0.9.8 or later built
11196 without support for deprecated functions.
11197 - Update to the "December 19 2008" ip-to-country file.
11199 o Minor bugfixes (on 0.2.0.x):
11200 - Authorities now vote for the Stable flag for any router whose
11201 weighted MTBF is at least 5 days, regardless of the mean MTBF.
11202 - Do not remove routers as too old if we do not have any consensus
11203 document. Bugfix on 0.2.0.7-alpha.
11204 - Do not accept incomplete ipv4 addresses (like 192.168.0) as valid.
11205 Spec conformance issue. Bugfix on Tor 0.0.2pre27.
11206 - When an exit relay resolves a stream address to a local IP address,
11207 do not just keep retrying that same exit relay over and
11208 over. Instead, just close the stream. Addresses bug 872. Bugfix
11209 on 0.2.0.32. Patch from rovv.
11210 - If a hidden service sends us an END cell, do not consider
11211 retrying the connection; just close it. Patch from rovv.
11212 - When we made bridge authorities stop serving bridge descriptors over
11213 unencrypted links, we also broke DirPort reachability testing for
11214 bridges. So bridges with a non-zero DirPort were printing spurious
11215 warns to their logs. Bugfix on 0.2.0.16-alpha. Fixes bug 709.
11216 - When a relay gets a create cell it can't decrypt (e.g. because it's
11217 using the wrong onion key), we were dropping it and letting the
11218 client time out. Now actually answer with a destroy cell. Fixes
11219 bug 904. Bugfix on 0.0.2pre8.
11220 - Squeeze 2-5% out of client performance (according to oprofile) by
11221 improving the implementation of some policy-manipulation functions.
11223 o Minor bugfixes (on 0.2.1.x):
11224 - Make get_interface_address() function work properly again; stop
11225 guessing the wrong parts of our address as our address.
11226 - Do not cannibalize a circuit if we're out of RELAY_EARLY cells to
11227 send on that circuit. Otherwise we might violate the proposal-110
11228 limit. Bugfix on 0.2.1.3-alpha. Partial fix for bug 878. Diagnosis
11230 - When we're sending non-EXTEND cells to the first hop in a circuit,
11231 for example to use an encrypted directory connection, we don't need
11232 to use RELAY_EARLY cells: the first hop knows what kind of cell
11233 it is, and nobody else can even see the cell type. Conserving
11234 RELAY_EARLY cells makes it easier to cannibalize circuits like
11236 - Stop logging nameserver addresses in reverse order.
11237 - If we are retrying a directory download slowly over and over, do
11238 not automatically give up after the 254th failure. Bugfix on
11240 - Resume reporting accurate "stream end" reasons to the local control
11241 port. They were lost in the changes for Proposal 148. Bugfix on
11244 o Deprecated and removed features:
11245 - The old "tor --version --version" command, which would print out
11246 the subversion "Id" of most of the source files, is now removed. It
11247 turned out to be less useful than we'd expected, and harder to
11250 o Code simplifications and refactoring:
11251 - Change our header file guard macros to be less likely to conflict
11252 with system headers. Adam Langley noticed that we were conflicting
11253 with log.h on Android.
11254 - Tool-assisted documentation cleanup. Nearly every function or
11255 static variable in Tor should have its own documentation now.
11258 Changes in version 0.2.1.9-alpha - 2008-12-25
11259 Tor 0.2.1.9-alpha fixes many more bugs, some of them security-related.
11261 o New directory authorities:
11262 - gabelmoo (the authority run by Karsten Loesing) now has a new
11266 - Never use a connection with a mismatched address to extend a
11267 circuit, unless that connection is canonical. A canonical
11268 connection is one whose address is authenticated by the router's
11269 identity key, either in a NETINFO cell or in a router descriptor.
11270 - Avoid a possible memory corruption bug when receiving hidden service
11271 descriptors. Bugfix on 0.2.1.6-alpha.
11274 - Fix a logic error that would automatically reject all but the first
11275 configured DNS server. Bugfix on 0.2.1.5-alpha. Possible fix for
11276 part of bug 813/868. Bug spotted by coderman.
11277 - When a stream at an exit relay is in state "resolving" or
11278 "connecting" and it receives an "end" relay cell, the exit relay
11279 would silently ignore the end cell and not close the stream. If
11280 the client never closes the circuit, then the exit relay never
11281 closes the TCP connection. Bug introduced in 0.1.2.1-alpha;
11282 reported by "wood".
11283 - When we can't initialize DNS because the network is down, do not
11284 automatically stop Tor from starting. Instead, retry failed
11285 dns_init() every 10 minutes, and change the exit policy to reject
11286 *:* until one succeeds. Fixes bug 691.
11289 - Give a better error message when an overzealous init script says
11290 "sudo -u username tor --user username". Makes Bug 882 easier for
11292 - When a directory authority gives us a new guess for our IP address,
11293 log which authority we used. Hopefully this will help us debug
11294 the recent complaints about bad IP address guesses.
11295 - Detect svn revision properly when we're using git-svn.
11296 - Try not to open more than one descriptor-downloading connection
11297 to an authority at once. This should reduce load on directory
11298 authorities. Fixes bug 366.
11299 - Add cross-certification to newly generated certificates, so that
11300 a signing key is enough information to look up a certificate.
11301 Partial implementation of proposal 157.
11302 - Start serving certificates by <identity digest, signing key digest>
11303 pairs. Partial implementation of proposal 157.
11304 - Clients now never report any stream end reason except 'MISC'.
11305 Implements proposal 148.
11306 - On platforms with a maximum syslog string length, truncate syslog
11307 messages to that length ourselves, rather than relying on the
11308 system to do it for us.
11309 - Optimize out calls to time(NULL) that occur for every IO operation,
11310 or for every cell. On systems where time() is a slow syscall,
11311 this fix will be slightly helpful.
11312 - Exit servers can now answer resolve requests for ip6.arpa addresses.
11313 - When we download a descriptor that we then immediately (as
11314 a directory authority) reject, do not retry downloading it right
11315 away. Should save some bandwidth on authorities. Fix for bug
11316 888. Patch by Sebastian Hahn.
11317 - When a download gets us zero good descriptors, do not notify
11318 Tor that new directory information has arrived.
11319 - Avoid some nasty corner cases in the logic for marking connections
11320 as too old or obsolete or noncanonical for circuits. Partial
11323 o Minor features (controller):
11324 - New CONSENSUS_ARRIVED event to note when a new consensus has
11325 been fetched and validated.
11326 - When we realize that another process has modified our cached
11327 descriptors file, print out a more useful error message rather
11328 than triggering an assertion. Fixes bug 885. Patch from Karsten.
11329 - Add an internal-use-only __ReloadTorrcOnSIGHUP option for
11330 controllers to prevent SIGHUP from reloading the
11331 configuration. Fixes bug 856.
11334 - Resume using the correct "REASON=" stream when telling the
11335 controller why we closed a stream. Bugfix in 0.2.1.1-alpha.
11336 - When a canonical connection appears later in our internal list
11337 than a noncanonical one for a given OR ID, always use the
11338 canonical one. Bugfix on 0.2.0.12-alpha. Fixes bug 805.
11340 - Clip the MaxCircuitDirtiness config option to a minimum of 10
11341 seconds. Warn the user if lower values are given in the
11342 configuration. Bugfix on 0.1.0.1-rc. Patch by Sebastian.
11343 - Clip the CircuitBuildTimeout to a minimum of 30 seconds. Warn the
11344 user if lower values are given in the configuration. Bugfix on
11345 0.1.1.17-rc. Patch by Sebastian.
11346 - Fix a race condition when freeing keys shared between main thread
11347 and CPU workers that could result in a memory leak. Bugfix on
11348 0.1.0.1-rc. Fixes bug 889.
11350 o Minor bugfixes (hidden services):
11351 - Do not throw away existing introduction points on SIGHUP (bugfix on
11352 0.0.6pre1); also, do not stall hidden services because we're
11353 throwing away introduction points; bugfix on 0.2.1.7-alpha. Spotted
11354 by John Brooks. Patch by Karsten. Fixes bug 874.
11355 - Fix a memory leak when we decline to add a v2 rendezvous
11356 descriptor to the cache because we already had a v0 descriptor
11357 with the same ID. Bugfix on 0.2.0.18-alpha.
11359 o Deprecated and removed features:
11360 - RedirectExits has been removed. It was deprecated since
11362 - Finally remove deprecated "EXTENDED_FORMAT" controller feature. It
11363 has been called EXTENDED_EVENTS since 0.1.2.4-alpha.
11364 - Cell pools are now always enabled; --disable-cell-pools is ignored.
11366 o Code simplifications and refactoring:
11367 - Rename the confusing or_is_obsolete field to the more appropriate
11368 is_bad_for_new_circs, and move it to or_connection_t where it
11370 - Move edge-only flags from connection_t to edge_connection_t: not
11371 only is this better coding, but on machines of plausible alignment,
11372 it should save 4-8 bytes per connection_t. "Every little bit helps."
11373 - Rename ServerDNSAllowBrokenResolvConf to ServerDNSAllowBrokenConfig
11374 for consistency; keep old option working for backward compatibility.
11375 - Simplify the code for finding connections to use for a circuit.
11378 Changes in version 0.2.1.8-alpha - 2008-12-08
11379 Tor 0.2.1.8-alpha fixes some crash bugs in earlier alpha releases,
11380 builds better on unusual platforms like Solaris and old OS X, and
11381 fixes a variety of other issues.
11384 - New DirPortFrontPage option that takes an html file and publishes
11385 it as "/" on the DirPort. Now relay operators can provide a
11386 disclaimer without needing to set up a separate webserver. There's
11387 a sample disclaimer in contrib/tor-exit-notice.html.
11390 - When the client is choosing entry guards, now it selects at most
11391 one guard from a given relay family. Otherwise we could end up with
11392 all of our entry points into the network run by the same operator.
11393 Suggested by Camilo Viecco. Fix on 0.1.1.11-alpha.
11396 - Fix a DOS opportunity during the voting signature collection process
11397 at directory authorities. Spotted by rovv. Bugfix on 0.2.0.x.
11398 - Fix a possible segfault when establishing an exit connection. Bugfix
11402 - Get file locking working on win32. Bugfix on 0.2.1.6-alpha. Fixes
11404 - Made Tor a little less aggressive about deleting expired
11405 certificates. Partial fix for bug 854.
11406 - Stop doing unaligned memory access that generated bus errors on
11407 sparc64. Bugfix on 0.2.0.10-alpha. Fix for bug 862.
11408 - Fix a crash bug when changing EntryNodes from the controller. Bugfix
11409 on 0.2.1.6-alpha. Fix for bug 867. Patched by Sebastian.
11410 - Make USR2 log-level switch take effect immediately. Bugfix on
11412 - If one win32 nameserver fails to get added, continue adding the
11413 rest, and don't automatically fail.
11414 - Use fcntl() for locking when flock() is not available. Should fix
11415 compilation on Solaris. Should fix Bug 873. Bugfix on 0.2.1.6-alpha.
11416 - Do not mark smartlist_bsearch_idx() function as ATTR_PURE. This bug
11417 could make gcc generate non-functional binary search code. Bugfix
11419 - Build correctly on platforms without socklen_t.
11420 - Avoid potential crash on internal error during signature collection.
11421 Fixes bug 864. Patch from rovv.
11422 - Do not use C's stdio library for writing to log files. This will
11423 improve logging performance by a minute amount, and will stop
11424 leaking fds when our disk is full. Fixes bug 861.
11425 - Stop erroneous use of O_APPEND in cases where we did not in fact
11426 want to re-seek to the end of a file before every last write().
11427 - Correct handling of possible malformed authority signing key
11428 certificates with internal signature types. Fixes bug 880. Bugfix
11430 - Fix a hard-to-trigger resource leak when logging credential status.
11434 - Directory mirrors no longer fetch the v1 directory or
11435 running-routers files. They are obsolete, and nobody asks for them
11436 anymore. This is the first step to making v1 authorities obsolete.
11438 o Minor features (controller):
11439 - Return circuit purposes in response to GETINFO circuit-status. Fixes
11443 Changes in version 0.2.0.32 - 2008-11-20
11444 Tor 0.2.0.32 fixes a major security problem in Debian and Ubuntu
11445 packages (and maybe other packages) noticed by Theo de Raadt, fixes
11446 a smaller security flaw that might allow an attacker to access local
11447 services, further improves hidden service performance, and fixes a
11448 variety of other issues.
11451 - The "User" and "Group" config options did not clear the
11452 supplementary group entries for the Tor process. The "User" option
11453 is now more robust, and we now set the groups to the specified
11454 user's primary group. The "Group" option is now ignored. For more
11455 detailed logging on credential switching, set CREDENTIAL_LOG_LEVEL
11456 in common/compat.c to LOG_NOTICE or higher. Patch by Jacob Appelbaum
11457 and Steven Murdoch. Bugfix on 0.0.2pre14. Fixes bug 848 and 857.
11458 - The "ClientDNSRejectInternalAddresses" config option wasn't being
11459 consistently obeyed: if an exit relay refuses a stream because its
11460 exit policy doesn't allow it, we would remember what IP address
11461 the relay said the destination address resolves to, even if it's
11462 an internal IP address. Bugfix on 0.2.0.7-alpha; patch by rovv.
11465 - Fix a DOS opportunity during the voting signature collection process
11466 at directory authorities. Spotted by rovv. Bugfix on 0.2.0.x.
11468 o Major bugfixes (hidden services):
11469 - When fetching v0 and v2 rendezvous service descriptors in parallel,
11470 we were failing the whole hidden service request when the v0
11471 descriptor fetch fails, even if the v2 fetch is still pending and
11472 might succeed. Similarly, if the last v2 fetch fails, we were
11473 failing the whole hidden service request even if a v0 fetch is
11474 still pending. Fixes bug 814. Bugfix on 0.2.0.10-alpha.
11475 - When extending a circuit to a hidden service directory to upload a
11476 rendezvous descriptor using a BEGIN_DIR cell, almost 1/6 of all
11477 requests failed, because the router descriptor has not been
11478 downloaded yet. In these cases, do not attempt to upload the
11479 rendezvous descriptor, but wait until the router descriptor is
11480 downloaded and retry. Likewise, do not attempt to fetch a rendezvous
11481 descriptor from a hidden service directory for which the router
11482 descriptor has not yet been downloaded. Fixes bug 767. Bugfix
11486 - Fix several infrequent memory leaks spotted by Coverity.
11487 - When testing for libevent functions, set the LDFLAGS variable
11488 correctly. Found by Riastradh.
11489 - Avoid a bug where the FastFirstHopPK 0 option would keep Tor from
11490 bootstrapping with tunneled directory connections. Bugfix on
11491 0.1.2.5-alpha. Fixes bug 797. Found by Erwin Lam.
11492 - When asked to connect to A.B.exit:80, if we don't know the IP for A
11493 and we know that server B rejects most-but-not all connections to
11494 port 80, we would previously reject the connection. Now, we assume
11495 the user knows what they were asking for. Fixes bug 752. Bugfix
11496 on 0.0.9rc5. Diagnosed by BarkerJr.
11497 - If we overrun our per-second write limits a little, count this as
11498 having used up our write allocation for the second, and choke
11499 outgoing directory writes. Previously, we had only counted this when
11500 we had met our limits precisely. Fixes bug 824. Patch from by rovv.
11501 Bugfix on 0.2.0.x (??).
11502 - Remove the old v2 directory authority 'lefkada' from the default
11503 list. It has been gone for many months.
11504 - Stop doing unaligned memory access that generated bus errors on
11505 sparc64. Bugfix on 0.2.0.10-alpha. Fixes bug 862.
11506 - Make USR2 log-level switch take effect immediately. Bugfix on
11509 o Minor bugfixes (controller):
11510 - Make DNS resolved events into "CLOSED", not "FAILED". Bugfix on
11511 0.1.2.5-alpha. Fix by Robert Hogan. Resolves bug 807.
11514 Changes in version 0.2.1.7-alpha - 2008-11-08
11515 Tor 0.2.1.7-alpha fixes a major security problem in Debian and Ubuntu
11516 packages (and maybe other packages) noticed by Theo de Raadt, fixes
11517 a smaller security flaw that might allow an attacker to access local
11518 services, adds better defense against DNS poisoning attacks on exit
11519 relays, further improves hidden service performance, and fixes a
11520 variety of other issues.
11523 - The "ClientDNSRejectInternalAddresses" config option wasn't being
11524 consistently obeyed: if an exit relay refuses a stream because its
11525 exit policy doesn't allow it, we would remember what IP address
11526 the relay said the destination address resolves to, even if it's
11527 an internal IP address. Bugfix on 0.2.0.7-alpha; patch by rovv.
11528 - The "User" and "Group" config options did not clear the
11529 supplementary group entries for the Tor process. The "User" option
11530 is now more robust, and we now set the groups to the specified
11531 user's primary group. The "Group" option is now ignored. For more
11532 detailed logging on credential switching, set CREDENTIAL_LOG_LEVEL
11533 in common/compat.c to LOG_NOTICE or higher. Patch by Jacob Appelbaum
11534 and Steven Murdoch. Bugfix on 0.0.2pre14. Fixes bug 848.
11535 - Do not use or believe expired v3 authority certificates. Patch
11536 from Karsten. Bugfix in 0.2.0.x. Fixes bug 851.
11539 - Now NodeFamily and MyFamily config options allow spaces in
11540 identity fingerprints, so it's easier to paste them in.
11541 Suggested by Lucky Green.
11542 - Implement the 0x20 hack to better resist DNS poisoning: set the
11543 case on outgoing DNS requests randomly, and reject responses that do
11544 not match the case correctly. This logic can be disabled with the
11545 ServerDNSRandomizeCase setting, if you are using one of the 0.3%
11546 of servers that do not reliably preserve case in replies. See
11547 "Increased DNS Forgery Resistance through 0x20-Bit Encoding"
11549 - Preserve case in replies to DNSPort requests in order to support
11550 the 0x20 hack for resisting DNS poisoning attacks.
11552 o Hidden service performance improvements:
11553 - When the client launches an introduction circuit, retry with a
11554 new circuit after 30 seconds rather than 60 seconds.
11555 - Launch a second client-side introduction circuit in parallel
11556 after a delay of 15 seconds (based on work by Christian Wilms).
11557 - Hidden services start out building five intro circuits rather
11558 than three, and when the first three finish they publish a service
11559 descriptor using those. Now we publish our service descriptor much
11560 faster after restart.
11563 - Minor fix in the warning messages when you're having problems
11564 bootstrapping; also, be more forgiving of bootstrap problems when
11565 we're still making incremental progress on a given bootstrap phase.
11566 - When we're choosing an exit node for a circuit, and we have
11567 no pending streams, choose a good general exit rather than one that
11568 supports "all the pending streams". Bugfix on 0.1.1.x. Fix by rovv.
11569 - Send a valid END cell back when a client tries to connect to a
11570 nonexistent hidden service port. Bugfix on 0.1.2.15. Fixes bug
11571 840. Patch from rovv.
11572 - If a broken client asks a non-exit router to connect somewhere,
11573 do not even do the DNS lookup before rejecting the connection.
11574 Fixes another case of bug 619. Patch from rovv.
11575 - Fix another case of assuming, when a specific exit is requested,
11576 that we know more than the user about what hosts it allows.
11577 Fixes another case of bug 752. Patch from rovv.
11578 - Check which hops rendezvous stream cells are associated with to
11579 prevent possible guess-the-streamid injection attacks from
11580 intermediate hops. Fixes another case of bug 446. Based on patch
11582 - Avoid using a negative right-shift when comparing 32-bit
11583 addresses. Possible fix for bug 845 and bug 811.
11584 - Make the assert_circuit_ok() function work correctly on circuits that
11585 have already been marked for close.
11586 - Fix read-off-the-end-of-string error in unit tests when decoding
11587 introduction points.
11588 - Fix uninitialized size field for memory area allocation: may improve
11589 memory performance during directory parsing.
11590 - Treat duplicate certificate fetches as failures, so that we do
11591 not try to re-fetch an expired certificate over and over and over.
11592 - Do not say we're fetching a certificate when we'll in fact skip it
11593 because of a pending download.
11596 Changes in version 0.2.1.6-alpha - 2008-09-30
11597 Tor 0.2.1.6-alpha further improves performance and robustness of
11598 hidden services, starts work on supporting per-country relay selection,
11599 and fixes a variety of smaller issues.
11602 - Implement proposal 121: make it possible to build hidden services
11603 that only certain clients are allowed to connect to. This is
11604 enforced at several points, so that unauthorized clients are unable
11605 to send INTRODUCE cells to the service, or even (depending on the
11606 type of authentication) to learn introduction points. This feature
11607 raises the bar for certain kinds of active attacks against hidden
11608 services. Code by Karsten Loesing.
11609 - Relays now store and serve v2 hidden service descriptors by default,
11610 i.e., the new default value for HidServDirectoryV2 is 1. This is
11611 the last step in proposal 114, which aims to make hidden service
11612 lookups more reliable.
11613 - Start work to allow node restrictions to include country codes. The
11614 syntax to exclude nodes in a country with country code XX is
11615 "ExcludeNodes {XX}". Patch from Robert Hogan. It still needs some
11616 refinement to decide what config options should take priority if
11617 you ask to both use a particular node and exclude it.
11618 - Allow ExitNodes list to include IP ranges and country codes, just
11619 like the Exclude*Nodes lists. Patch from Robert Hogan.
11622 - Fix a bug when parsing ports in tor_addr_port_parse() that caused
11623 Tor to fail to start if you had it configured to use a bridge
11624 relay. Fixes bug 809. Bugfix on 0.2.1.5-alpha.
11625 - When extending a circuit to a hidden service directory to upload a
11626 rendezvous descriptor using a BEGIN_DIR cell, almost 1/6 of all
11627 requests failed, because the router descriptor had not been
11628 downloaded yet. In these cases, we now wait until the router
11629 descriptor is downloaded, and then retry. Likewise, clients
11630 now skip over a hidden service directory if they don't yet have
11631 its router descriptor, rather than futilely requesting it and
11632 putting mysterious complaints in the logs. Fixes bug 767. Bugfix
11634 - When fetching v0 and v2 rendezvous service descriptors in parallel,
11635 we were failing the whole hidden service request when the v0
11636 descriptor fetch fails, even if the v2 fetch is still pending and
11637 might succeed. Similarly, if the last v2 fetch fails, we were
11638 failing the whole hidden service request even if a v0 fetch is
11639 still pending. Fixes bug 814. Bugfix on 0.2.0.10-alpha.
11640 - DNS replies need to have names matching their requests, but
11641 these names should be in the questions section, not necessarily
11642 in the answers section. Fixes bug 823. Bugfix on 0.2.1.5-alpha.
11645 - Update to the "September 1 2008" ip-to-country file.
11646 - Allow ports 465 and 587 in the default exit policy again. We had
11647 rejected them in 0.1.0.15, because back in 2005 they were commonly
11648 misconfigured and ended up as spam targets. We hear they are better
11649 locked down these days.
11650 - Use a lockfile to make sure that two Tor processes are not
11651 simultaneously running with the same datadir.
11652 - Serve the latest v3 networkstatus consensus via the control
11653 port. Use "getinfo dir/status-vote/current/consensus" to fetch it.
11654 - Better logging about stability/reliability calculations on directory
11656 - Drop the requirement to have an open dir port for storing and
11657 serving v2 hidden service descriptors.
11658 - Directory authorities now serve a /tor/dbg-stability.txt URL to
11659 help debug WFU and MTBF calculations.
11660 - Implement most of Proposal 152: allow specialized servers to permit
11661 single-hop circuits, and clients to use those servers to build
11662 single-hop circuits when using a specialized controller. Patch
11663 from Josh Albrecht. Resolves feature request 768.
11664 - Add a -p option to tor-resolve for specifying the SOCKS port: some
11665 people find host:port too confusing.
11666 - Make TrackHostExit mappings expire a while after their last use, not
11667 after their creation. Patch from Robert Hogan.
11668 - Provide circuit purposes along with circuit events to the controller.
11671 - Fix compile on OpenBSD 4.4-current. Bugfix on 0.2.1.5-alpha.
11673 - Fixed some memory leaks -- some quite frequent, some almost
11674 impossible to trigger -- based on results from Coverity.
11675 - When testing for libevent functions, set the LDFLAGS variable
11676 correctly. Found by Riastradh.
11677 - Fix an assertion bug in parsing policy-related options; possible fix
11679 - Catch and report a few more bootstrapping failure cases when Tor
11680 fails to establish a TCP connection. Cleanup on 0.2.1.x.
11681 - Avoid a bug where the FastFirstHopPK 0 option would keep Tor from
11682 bootstrapping with tunneled directory connections. Bugfix on
11683 0.1.2.5-alpha. Fixes bug 797. Found by Erwin Lam.
11684 - When asked to connect to A.B.exit:80, if we don't know the IP for A
11685 and we know that server B rejects most-but-not all connections to
11686 port 80, we would previously reject the connection. Now, we assume
11687 the user knows what they were asking for. Fixes bug 752. Bugfix
11688 on 0.0.9rc5. Diagnosed by BarkerJr.
11689 - If we are not using BEGIN_DIR cells, don't attempt to contact hidden
11690 service directories if they have no advertised dir port. Bugfix
11692 - If we overrun our per-second write limits a little, count this as
11693 having used up our write allocation for the second, and choke
11694 outgoing directory writes. Previously, we had only counted this when
11695 we had met our limits precisely. Fixes bug 824. Patch by rovv.
11696 Bugfix on 0.2.0.x (??).
11697 - Avoid a "0 divided by 0" calculation when calculating router uptime
11698 at directory authorities. Bugfix on 0.2.0.8-alpha.
11699 - Make DNS resolved controller events into "CLOSED", not
11700 "FAILED". Bugfix on 0.1.2.5-alpha. Fix by Robert Hogan. Resolves
11702 - Fix a bug where an unreachable relay would establish enough
11703 reachability testing circuits to do a bandwidth test -- if
11704 we already have a connection to the middle hop of the testing
11705 circuit, then it could establish the last hop by using the existing
11706 connection. Bugfix on 0.1.2.2-alpha, exposed when we made testing
11707 circuits no longer use entry guards in 0.2.1.3-alpha.
11708 - If we have correct permissions on $datadir, we complain to stdout
11709 and fail to start. But dangerous permissions on
11710 $datadir/cached-status/ would cause us to open a log and complain
11711 there. Now complain to stdout and fail to start in both cases. Fixes
11712 bug 820, reported by seeess.
11713 - Remove the old v2 directory authority 'lefkada' from the default
11714 list. It has been gone for many months.
11716 o Code simplifications and refactoring:
11717 - Revise the connection_new functions so that a more typesafe variant
11718 exists. This will work better with Coverity, and let us find any
11719 actual mistakes we're making here.
11720 - Refactor unit testing logic so that dmalloc can be used sensibly
11721 with unit tests to check for memory leaks.
11722 - Move all hidden-service related fields from connection and circuit
11723 structure to substructures: this way they won't eat so much memory.
11726 Changes in version 0.2.0.31 - 2008-09-03
11727 Tor 0.2.0.31 addresses two potential anonymity issues, starts to fix
11728 a big bug we're seeing where in rare cases traffic from one Tor stream
11729 gets mixed into another stream, and fixes a variety of smaller issues.
11732 - Make sure that two circuits can never exist on the same connection
11733 with the same circuit ID, even if one is marked for close. This
11734 is conceivably a bugfix for bug 779. Bugfix on 0.1.0.4-rc.
11735 - Relays now reject risky extend cells: if the extend cell includes
11736 a digest of all zeroes, or asks to extend back to the relay that
11737 sent the extend cell, tear down the circuit. Ideas suggested
11739 - If not enough of our entry guards are available so we add a new
11740 one, we might use the new one even if it overlapped with the
11741 current circuit's exit relay (or its family). Anonymity bugfix
11742 pointed out by rovv.
11745 - Recover 3-7 bytes that were wasted per memory chunk. Fixes bug
11746 794; bug spotted by rovv. Bugfix on 0.2.0.1-alpha.
11747 - Correctly detect the presence of the linux/netfilter_ipv4.h header
11748 when building against recent kernels. Bugfix on 0.1.2.1-alpha.
11749 - Pick size of default geoip filename string correctly on windows.
11750 Fixes bug 806. Bugfix on 0.2.0.30.
11751 - Make the autoconf script accept the obsolete --with-ssl-dir
11752 option as an alias for the actually-working --with-openssl-dir
11753 option. Fix the help documentation to recommend --with-openssl-dir.
11754 Based on a patch by "Dave". Bugfix on 0.2.0.1-alpha.
11755 - When using the TransPort option on OpenBSD, and using the User
11756 option to change UID and drop privileges, make sure to open
11757 /dev/pf before dropping privileges. Fixes bug 782. Patch from
11758 Christopher Davis. Bugfix on 0.1.2.1-alpha.
11759 - Try to attach connections immediately upon receiving a RENDEZVOUS2
11760 or RENDEZVOUS_ESTABLISHED cell. This can save a second or two
11761 on the client side when connecting to a hidden service. Bugfix
11762 on 0.0.6pre1. Found and fixed by Christian Wilms; resolves bug 743.
11763 - When closing an application-side connection because its circuit is
11764 getting torn down, generate the stream event correctly. Bugfix on
11765 0.1.2.x. Anonymous patch.
11768 Changes in version 0.2.1.5-alpha - 2008-08-31
11769 Tor 0.2.1.5-alpha moves us closer to handling IPv6 destinations, puts
11770 in a lot of the infrastructure for adding authorization to hidden
11771 services, lays the groundwork for having clients read their load
11772 balancing information out of the networkstatus consensus rather than
11773 the individual router descriptors, addresses two potential anonymity
11774 issues, and fixes a variety of smaller issues.
11777 - Convert many internal address representations to optionally hold
11779 - Generate and accept IPv6 addresses in many protocol elements.
11780 - Make resolver code handle nameservers located at ipv6 addresses.
11781 - Begin implementation of proposal 121 ("Client authorization for
11782 hidden services"): configure hidden services with client
11783 authorization, publish descriptors for them, and configure
11784 authorization data for hidden services at clients. The next
11785 step is to actually access hidden services that perform client
11787 - More progress toward proposal 141: Network status consensus
11788 documents and votes now contain bandwidth information for each
11789 router and a summary of that router's exit policy. Eventually this
11790 will be used by clients so that they do not have to download every
11791 known descriptor before building circuits.
11793 o Major bugfixes (on 0.2.0.x and before):
11794 - When sending CREATED cells back for a given circuit, use a 64-bit
11795 connection ID to find the right connection, rather than an addr:port
11796 combination. Now that we can have multiple OR connections between
11797 the same ORs, it is no longer possible to use addr:port to uniquely
11798 identify a connection.
11799 - Relays now reject risky extend cells: if the extend cell includes
11800 a digest of all zeroes, or asks to extend back to the relay that
11801 sent the extend cell, tear down the circuit. Ideas suggested
11803 - If not enough of our entry guards are available so we add a new
11804 one, we might use the new one even if it overlapped with the
11805 current circuit's exit relay (or its family). Anonymity bugfix
11806 pointed out by rovv.
11809 - Recover 3-7 bytes that were wasted per memory chunk. Fixes bug
11810 794; bug spotted by rovv. Bugfix on 0.2.0.1-alpha.
11811 - When using the TransPort option on OpenBSD, and using the User
11812 option to change UID and drop privileges, make sure to open /dev/pf
11813 before dropping privileges. Fixes bug 782. Patch from Christopher
11814 Davis. Bugfix on 0.1.2.1-alpha.
11815 - Correctly detect the presence of the linux/netfilter_ipv4.h header
11816 when building against recent kernels. Bugfix on 0.1.2.1-alpha.
11817 - Add a missing safe_str() call for a debug log message.
11818 - Use 64 bits instead of 32 bits for connection identifiers used with
11819 the controller protocol, to greatly reduce risk of identifier reuse.
11820 - Make the autoconf script accept the obsolete --with-ssl-dir
11821 option as an alias for the actually-working --with-openssl-dir
11822 option. Fix the help documentation to recommend --with-openssl-dir.
11823 Based on a patch by "Dave". Bugfix on 0.2.0.1-alpha.
11826 - Rate-limit too-many-sockets messages: when they happen, they happen
11827 a lot. Resolves bug 748.
11828 - Resist DNS poisoning a little better by making sure that names in
11829 answer sections match.
11830 - Print the SOCKS5 error message string as well as the error code
11831 when a tor-resolve request fails. Patch from Jacob.
11834 Changes in version 0.2.1.4-alpha - 2008-08-04
11835 Tor 0.2.1.4-alpha fixes a pair of crash bugs in 0.2.1.3-alpha.
11838 - The address part of exit policies was not correctly written
11839 to router descriptors. This generated router descriptors that failed
11840 their self-checks. Noticed by phobos, fixed by Karsten. Bugfix
11842 - Tor triggered a false assert when extending a circuit to a relay
11843 but we already have a connection open to that relay. Noticed by
11844 phobos, fixed by Karsten. Bugfix on 0.2.1.3-alpha.
11847 - Fix a hidden service logging bug: in some edge cases, the router
11848 descriptor of a previously picked introduction point becomes
11849 obsolete and we need to give up on it rather than continually
11850 complaining that it has become obsolete. Observed by xiando. Bugfix
11853 o Removed features:
11854 - Take out the TestVia config option, since it was a workaround for
11855 a bug that was fixed in Tor 0.1.1.21.
11858 Changes in version 0.2.1.3-alpha - 2008-08-03
11859 Tor 0.2.1.3-alpha implements most of the pieces to prevent
11860 infinite-length circuit attacks (see proposal 110); fixes a bug that
11861 might cause exit relays to corrupt streams they send back; allows
11862 address patterns (e.g. 255.128.0.0/16) to appear in ExcludeNodes and
11863 ExcludeExitNodes config options; and fixes a big pile of bugs.
11865 o Bootstrapping bugfixes (on 0.2.1.x-alpha):
11866 - Send a bootstrap problem "warn" event on the first problem if the
11867 reason is NO_ROUTE (that is, our network is down).
11870 - Implement most of proposal 110: The first K cells to be sent
11871 along a circuit are marked as special "early" cells; only K "early"
11872 cells will be allowed. Once this code is universal, we can block
11873 certain kinds of DOS attack by requiring that EXTEND commands must
11874 be sent using an "early" cell.
11877 - Try to attach connections immediately upon receiving a RENDEZVOUS2
11878 or RENDEZVOUS_ESTABLISHED cell. This can save a second or two
11879 on the client side when connecting to a hidden service. Bugfix
11880 on 0.0.6pre1. Found and fixed by Christian Wilms; resolves bug 743.
11881 - Ensure that two circuits can never exist on the same connection
11882 with the same circuit ID, even if one is marked for close. This
11883 is conceivably a bugfix for bug 779; fixes a bug on 0.1.0.4-rc.
11886 - When relays do their initial bandwidth measurement, don't limit
11887 to just our entry guards for the test circuits. Otherwise we tend
11888 to have multiple test circuits going through a single entry guard,
11889 which makes our bandwidth test less accurate. Fixes part of bug 654;
11890 patch contributed by Josh Albrecht.
11891 - Add an ExcludeExitNodes option so users can list a set of nodes
11892 that should be be excluded from the exit node position, but
11893 allowed elsewhere. Implements proposal 151.
11894 - Allow address patterns (e.g., 255.128.0.0/16) to appear in
11895 ExcludeNodes and ExcludeExitNodes lists.
11896 - Change the implementation of ExcludeNodes and ExcludeExitNodes to
11897 be more efficient. Formerly it was quadratic in the number of
11898 servers; now it should be linear. Fixes bug 509.
11899 - Save 16-22 bytes per open circuit by moving the n_addr, n_port,
11900 and n_conn_id_digest fields into a separate structure that's
11901 only needed when the circuit has not yet attached to an n_conn.
11904 - Change the contrib/tor.logrotate script so it makes the new
11905 logs as "_tor:_tor" rather than the default, which is generally
11906 "root:wheel". Fixes bug 676, reported by Serge Koksharov.
11907 - Stop using __attribute__((nonnull)) with GCC: it can give us useful
11908 warnings (occasionally), but it can also cause the compiler to
11909 eliminate error-checking code. Suggested by Peter Gutmann.
11910 - When a hidden service is giving up on an introduction point candidate
11911 that was not included in the last published rendezvous descriptor,
11912 don't reschedule publication of the next descriptor. Fixes bug 763.
11914 - Mark RendNodes, RendExcludeNodes, HiddenServiceNodes, and
11915 HiddenServiceExcludeNodes as obsolete: they never worked properly,
11916 and nobody claims to be using them. Fixes bug 754. Bugfix on
11917 0.1.0.1-rc. Patch from Christian Wilms.
11918 - Fix a small alignment and memory-wasting bug on buffer chunks.
11921 o Minor bugfixes (controller):
11922 - When closing an application-side connection because its circuit
11923 is getting torn down, generate the stream event correctly.
11924 Bugfix on 0.1.2.x. Anonymous patch.
11926 o Removed features:
11927 - Remove all backward-compatibility code to support relays running
11928 versions of Tor so old that they no longer work at all on the
11932 Changes in version 0.2.0.30 - 2008-07-15
11934 - Stop using __attribute__((nonnull)) with GCC: it can give us useful
11935 warnings (occasionally), but it can also cause the compiler to
11936 eliminate error-checking code. Suggested by Peter Gutmann.
11939 Changes in version 0.2.0.29-rc - 2008-07-08
11940 Tor 0.2.0.29-rc fixes two big bugs with using bridges, fixes more
11941 hidden-service performance bugs, and fixes a bunch of smaller bugs.
11944 - If you have more than one bridge but don't know their keys,
11945 you would only launch a request for the descriptor of the first one
11946 on your list. (Tor considered launching requests for the others, but
11947 found that it already had a connection on the way for $0000...0000
11948 so it didn't open another.) Bugfix on 0.2.0.x.
11949 - If you have more than one bridge but don't know their keys, and the
11950 connection to one of the bridges failed, you would cancel all
11951 pending bridge connections. (After all, they all have the same
11952 digest.) Bugfix on 0.2.0.x.
11953 - When a hidden service was trying to establish an introduction point,
11954 and Tor had built circuits preemptively for such purposes, we
11955 were ignoring all the preemptive circuits and launching a new one
11956 instead. Bugfix on 0.2.0.14-alpha.
11957 - When a hidden service was trying to establish an introduction point,
11958 and Tor *did* manage to reuse one of the preemptively built
11959 circuits, it didn't correctly remember which one it used,
11960 so it asked for another one soon after, until there were no
11961 more preemptive circuits, at which point it launched one from
11962 scratch. Bugfix on 0.0.9.x.
11963 - Make directory servers include the X-Your-Address-Is: http header in
11964 their responses even for begin_dir conns. Now clients who only
11965 ever use begin_dir connections still have a way to learn their IP
11966 address. Fixes bug 737; bugfix on 0.2.0.22-rc. Reported by goldy.
11969 - Fix a macro/CPP interaction that was confusing some compilers:
11970 some GCCs don't like #if/#endif pairs inside macro arguments.
11972 - Fix macro collision between OpenSSL 0.9.8h and Windows headers.
11973 Fixes bug 704; fix from Steven Murdoch.
11974 - When opening /dev/null in finish_daemonize(), do not pass the
11975 O_CREAT flag. Fortify was complaining, and correctly so. Fixes
11976 bug 742; fix from Michael Scherer. Bugfix on 0.0.2pre19.
11977 - Correctly detect transparent proxy support on Linux hosts that
11978 require in.h to be included before netfilter_ipv4.h. Patch
11980 - Disallow session resumption attempts during the renegotiation
11981 stage of the v2 handshake protocol. Clients should never be trying
11982 session resumption at this point, but apparently some did, in
11983 ways that caused the handshake to fail. Bugfix on 0.2.0.20-rc. Bug
11984 found by Geoff Goodell.
11987 Changes in version 0.2.1.2-alpha - 2008-06-20
11988 Tor 0.2.1.2-alpha includes a new "TestingTorNetwork" config option to
11989 make it easier to set up your own private Tor network; fixes several
11990 big bugs with using more than one bridge relay; fixes a big bug with
11991 offering hidden services quickly after Tor starts; and uses a better
11992 API for reporting potential bootstrapping problems to the controller.
11995 - New TestingTorNetwork config option to allow adjustment of
11996 previously constant values that, while reasonable, could slow
11997 bootstrapping. Implements proposal 135. Patch from Karsten.
12000 - If you have more than one bridge but don't know their digests,
12001 you would only learn a request for the descriptor of the first one
12002 on your list. (Tor considered launching requests for the others, but
12003 found that it already had a connection on the way for $0000...0000
12004 so it didn't open another.) Bugfix on 0.2.0.x.
12005 - If you have more than one bridge but don't know their digests,
12006 and the connection to one of the bridges failed, you would cancel
12007 all pending bridge connections. (After all, they all have the
12008 same digest.) Bugfix on 0.2.0.x.
12009 - When establishing a hidden service, introduction points that
12010 originate from cannibalized circuits are completely ignored and not
12011 included in rendezvous service descriptors. This might be another
12012 reason for delay in making a hidden service available. Bugfix
12013 from long ago (0.0.9.x?)
12016 - Allow OpenSSL to use dynamic locks if it wants.
12017 - When building a consensus, do not include routers that are down.
12018 This will cut down 30% to 40% on consensus size. Implements
12020 - In directory authorities' approved-routers files, allow
12021 fingerprints with or without space.
12022 - Add a "GETINFO /status/bootstrap-phase" controller option, so the
12023 controller can query our current bootstrap state in case it attaches
12024 partway through and wants to catch up.
12025 - Send an initial "Starting" bootstrap status event, so we have a
12026 state to start out in.
12029 - Asking for a conditional consensus at .../consensus/<fingerprints>
12030 would crash a dirserver if it did not already have a
12031 consensus. Bugfix on 0.2.1.1-alpha.
12032 - Clean up some macro/CPP interactions: some GCC versions don't like
12033 #if/#endif pairs inside macro arguments. Fixes bug 707. Bugfix on
12036 o Bootstrapping bugfixes (on 0.2.1.1-alpha):
12037 - Directory authorities shouldn't complain about bootstrapping
12038 problems just because they do a lot of reachability testing and
12039 some of the connection attempts fail.
12040 - Start sending "count" and "recommendation" key/value pairs in
12041 bootstrap problem status events, so the controller can hear about
12042 problems even before Tor decides they're worth reporting for sure.
12043 - If you're using bridges, generate "bootstrap problem" warnings
12044 as soon as you run out of working bridges, rather than waiting
12045 for ten failures -- which will never happen if you have less than
12047 - If we close our OR connection because there's been a circuit
12048 pending on it for too long, we were telling our bootstrap status
12049 events "REASON=NONE". Now tell them "REASON=TIMEOUT".
12052 Changes in version 0.2.1.1-alpha - 2008-06-13
12053 Tor 0.2.1.1-alpha fixes a lot of memory fragmentation problems that
12054 were making the Tor process bloat especially on Linux; makes our TLS
12055 handshake blend in better; sends "bootstrap phase" status events to
12056 the controller, so it can keep the user informed of progress (and
12057 problems) fetching directory information and establishing circuits;
12058 and adds a variety of smaller features.
12061 - More work on making our TLS handshake blend in: modify the list
12062 of ciphers advertised by OpenSSL in client mode to even more
12063 closely resemble a common web browser. We cheat a little so that
12064 we can advertise ciphers that the locally installed OpenSSL doesn't
12066 - Start sending "bootstrap phase" status events to the controller,
12067 so it can keep the user informed of progress fetching directory
12068 information and establishing circuits. Also inform the controller
12069 if we think we're stuck at a particular bootstrap phase. Implements
12071 - Resume using OpenSSL's RAND_poll() for better (and more portable)
12072 cross-platform entropy collection again. We used to use it, then
12073 stopped using it because of a bug that could crash systems that
12074 called RAND_poll when they had a lot of fds open. It looks like the
12075 bug got fixed in late 2006. Our new behavior is to call RAND_poll()
12076 at startup, and to call RAND_poll() when we reseed later only if
12077 we have a non-buggy OpenSSL version.
12080 - When we choose to abandon a new entry guard because we think our
12081 older ones might be better, close any circuits pending on that
12082 new entry guard connection. This fix should make us recover much
12083 faster when our network is down and then comes back. Bugfix on
12084 0.1.2.8-beta; found by lodger.
12086 o Memory fixes and improvements:
12087 - Add a malloc_good_size implementation to OpenBSD_malloc_linux.c,
12088 to avoid unused RAM in buffer chunks and memory pools.
12089 - Speed up parsing and cut down on memory fragmentation by using
12090 stack-style allocations for parsing directory objects. Previously,
12091 this accounted for over 40% of allocations from within Tor's code
12092 on a typical directory cache.
12093 - Use a Bloom filter rather than a digest-based set to track which
12094 descriptors we need to keep around when we're cleaning out old
12095 router descriptors. This speeds up the computation significantly,
12096 and may reduce fragmentation.
12097 - Reduce the default smartlist size from 32 to 16; it turns out that
12098 most smartlists hold around 8-12 elements tops.
12099 - Make dumpstats() log the fullness and size of openssl-internal
12101 - If the user has applied the experimental SSL_MODE_RELEASE_BUFFERS
12102 patch to their OpenSSL, turn it on to save memory on servers. This
12103 patch will (with any luck) get included in a mainline distribution
12105 - Never use OpenSSL compression: it wastes RAM and CPU trying to
12106 compress cells, which are basically all encrypted, compressed,
12110 - Stop reloading the router list from disk for no reason when we
12111 run out of reachable directory mirrors. Once upon a time reloading
12112 it would set the 'is_running' flag back to 1 for them. It hasn't
12113 done that for a long time.
12114 - In very rare situations new hidden service descriptors were
12115 published earlier than 30 seconds after the last change to the
12116 service. (We currently think that a hidden service descriptor
12117 that's been stable for 30 seconds is worth publishing.)
12120 - Allow separate log levels to be configured for different logging
12121 domains. For example, this allows one to log all notices, warnings,
12122 or errors, plus all memory management messages of level debug or
12123 higher, with: Log [MM] debug-err [*] notice-err file /var/log/tor.
12124 - Add a couple of extra warnings to --enable-gcc-warnings for GCC 4.3,
12125 and stop using a warning that had become unfixably verbose under
12127 - New --hush command-line option similar to --quiet. While --quiet
12128 disables all logging to the console on startup, --hush limits the
12129 output to messages of warning and error severity.
12130 - Servers support a new URL scheme for consensus downloads that
12131 allows the client to specify which authorities are trusted.
12132 The server then only sends the consensus if the client will trust
12133 it. Otherwise a 404 error is sent back. Clients use this
12134 new scheme when the server supports it (meaning it's running
12135 0.2.1.1-alpha or later). Implements proposal 134.
12136 - New configure/torrc options (--enable-geoip-stats,
12137 DirRecordUsageByCountry) to record how many IPs we've served
12138 directory info to in each country code, how many status documents
12139 total we've sent to each country code, and what share of the total
12140 directory requests we should expect to see.
12141 - Use the TLS1 hostname extension to more closely resemble browser
12143 - Lots of new unit tests.
12144 - Add a macro to implement the common pattern of iterating through
12145 two parallel lists in lockstep.
12148 Changes in version 0.2.0.28-rc - 2008-06-13
12149 Tor 0.2.0.28-rc fixes an anonymity-related bug, fixes a hidden-service
12150 performance bug, and fixes a bunch of smaller bugs.
12153 - Fix a bug where, when we were choosing the 'end stream reason' to
12154 put in our relay end cell that we send to the exit relay, Tor
12155 clients on Windows were sometimes sending the wrong 'reason'. The
12156 anonymity problem is that exit relays may be able to guess whether
12157 the client is running Windows, thus helping partition the anonymity
12158 set. Down the road we should stop sending reasons to exit relays,
12159 or otherwise prevent future versions of this bug.
12162 - While setting up a hidden service, some valid introduction circuits
12163 were overlooked and abandoned. This might be the reason for
12164 the long delay in making a hidden service available. Bugfix on
12168 - Update to the "June 9 2008" ip-to-country file.
12169 - Run 'make test' as part of 'make dist', so we stop releasing so
12170 many development snapshots that fail their unit tests.
12173 - When we're checking if we have enough dir info for each relay
12174 to begin establishing circuits, make sure that we actually have
12175 the descriptor listed in the consensus, not just any descriptor.
12177 - Bridge relays no longer print "xx=0" in their extrainfo document
12178 for every single country code in the geoip db. Bugfix on
12180 - Only warn when we fail to load the geoip file if we were planning to
12181 include geoip stats in our extrainfo document. Bugfix on 0.2.0.27-rc.
12182 - If we change our MaxAdvertisedBandwidth and then reload torrc,
12183 Tor won't realize it should publish a new relay descriptor. Fixes
12184 bug 688, reported by mfr. Bugfix on 0.1.2.x.
12185 - When we haven't had any application requests lately, don't bother
12186 logging that we have expired a bunch of descriptors. Bugfix
12188 - Make relay cells written on a connection count as non-padding when
12189 tracking how long a connection has been in use. Bugfix on
12190 0.2.0.1-alpha. Spotted by lodger.
12191 - Fix unit tests in 0.2.0.27-rc.
12192 - Fix compile on Windows.
12195 Changes in version 0.2.0.27-rc - 2008-06-03
12196 Tor 0.2.0.27-rc adds a few features we left out of the earlier
12197 release candidates. In particular, we now include an IP-to-country
12198 GeoIP database, so controllers can easily look up what country a
12199 given relay is in, and so bridge relays can give us some sanitized
12200 summaries about which countries are making use of bridges. (See proposal
12201 126-geoip-fetching.txt for details.)
12204 - Include an IP-to-country GeoIP file in the tarball, so bridge
12205 relays can report sanitized summaries of the usage they're seeing.
12208 - Add a "PURPOSE=" argument to "STREAM NEW" events, as suggested by
12209 Robert Hogan. Fixes the first part of bug 681.
12210 - Make bridge authorities never serve extrainfo docs.
12211 - Add support to detect Libevent versions in the 1.4.x series
12213 - Fix build on gcc 4.3 with --enable-gcc-warnings set.
12214 - Include a new contrib/tor-exit-notice.html file that exit relay
12215 operators can put on their website to help reduce abuse queries.
12218 - When tunneling an encrypted directory connection, and its first
12219 circuit fails, do not leave it unattached and ask the controller
12220 to deal. Fixes the second part of bug 681.
12221 - Make bridge authorities correctly expire old extrainfo documents
12225 Changes in version 0.2.0.26-rc - 2008-05-13
12226 Tor 0.2.0.26-rc fixes a major security vulnerability caused by a bug
12227 in Debian's OpenSSL packages. All users running any 0.2.0.x version
12228 should upgrade, whether they're running Debian or not.
12230 o Major security fixes:
12231 - Use new V3 directory authority keys on the tor26, gabelmoo, and
12232 moria1 V3 directory authorities. The old keys were generated with
12233 a vulnerable version of Debian's OpenSSL package, and must be
12234 considered compromised. Other authorities' keys were not generated
12235 with an affected version of OpenSSL.
12238 - List authority signatures as "unrecognized" based on DirServer
12239 lines, not on cert cache. Bugfix on 0.2.0.x.
12242 - Add a new V3AuthUseLegacyKey option to make it easier for
12243 authorities to change their identity keys if they have to.
12246 Changes in version 0.2.0.25-rc - 2008-04-23
12247 Tor 0.2.0.25-rc makes Tor work again on OS X and certain BSDs.
12250 - Remember to initialize threading before initializing logging.
12251 Otherwise, many BSD-family implementations will crash hard on
12252 startup. Fixes bug 671. Bugfix on 0.2.0.24-rc.
12255 - Authorities correctly free policies on bad servers on
12256 exit. Fixes bug 672. Bugfix on 0.2.0.x.
12259 Changes in version 0.2.0.24-rc - 2008-04-22
12260 Tor 0.2.0.24-rc adds dizum (run by Alex de Joode) as the new sixth
12261 v3 directory authority, makes relays with dynamic IP addresses and no
12262 DirPort notice more quickly when their IP address changes, fixes a few
12263 rare crashes and memory leaks, and fixes a few other miscellaneous bugs.
12265 o New directory authorities:
12266 - Take lefkada out of the list of v3 directory authorities, since
12267 it has been down for months.
12268 - Set up dizum (run by Alex de Joode) as the new sixth v3 directory
12272 - Detect address changes more quickly on non-directory mirror
12273 relays. Bugfix on 0.2.0.18-alpha; fixes bug 652.
12275 o Minor features (security):
12276 - Reject requests for reverse-dns lookup of names that are in
12277 a private address space. Patch from lodger.
12278 - Non-exit relays no longer allow DNS requests. Fixes bug 619. Patch
12281 o Minor bugfixes (crashes):
12282 - Avoid a rare assert that can trigger when Tor doesn't have much
12283 directory information yet and it tries to fetch a v2 hidden
12284 service descriptor. Fixes bug 651, reported by nwf.
12285 - Initialize log mutex before initializing dmalloc. Otherwise,
12286 running with dmalloc would crash. Bugfix on 0.2.0.x-alpha.
12287 - Use recursive pthread mutexes in order to avoid deadlock when
12288 logging debug-level messages to a controller. Bug spotted by nwf,
12289 bugfix on 0.2.0.16-alpha.
12291 o Minor bugfixes (resource management):
12292 - Keep address policies from leaking memory: start their refcount
12293 at 1, not 2. Bugfix on 0.2.0.16-alpha.
12294 - Free authority certificates on exit, so they don't look like memory
12295 leaks. Bugfix on 0.2.0.19-alpha.
12296 - Free static hashtables for policy maps and for TLS connections on
12297 shutdown, so they don't look like memory leaks. Bugfix on 0.2.0.x.
12298 - Avoid allocating extra space when computing consensuses on 64-bit
12299 platforms. Bug spotted by aakova.
12301 o Minor bugfixes (misc):
12302 - Do not read the configuration file when we've only been told to
12303 generate a password hash. Fixes bug 643. Bugfix on 0.0.9pre5. Fix
12304 based on patch from Sebastian Hahn.
12305 - Exit relays that are used as a client can now reach themselves
12306 using the .exit notation, rather than just launching an infinite
12307 pile of circuits. Fixes bug 641. Reported by Sebastian Hahn.
12308 - When attempting to open a logfile fails, tell us why.
12309 - Fix a dumb bug that was preventing us from knowing that we should
12310 preemptively build circuits to handle expected directory requests.
12311 Fixes bug 660. Bugfix on 0.1.2.x.
12312 - Warn less verbosely about clock skew from netinfo cells from
12313 untrusted sources. Fixes bug 663.
12314 - Make controller stream events for DNS requests more consistent,
12315 by adding "new stream" events for DNS requests, and removing
12316 spurious "stream closed" events" for cached reverse resolves.
12317 Patch from mwenge. Fixes bug 646.
12318 - Correctly notify one-hop connections when a circuit build has
12319 failed. Possible fix for bug 669. Found by lodger.
12322 Changes in version 0.2.0.23-rc - 2008-03-24
12323 Tor 0.2.0.23-rc is the fourth release candidate for the 0.2.0 series. It
12324 makes bootstrapping faster if the first directory mirror you contact
12325 is down. The bundles also include the new Vidalia 0.1.2 release.
12328 - When a tunneled directory request is made to a directory server
12329 that's down, notice after 30 seconds rather than 120 seconds. Also,
12330 fail any begindir streams that are pending on it, so they can
12331 retry elsewhere. This was causing multi-minute delays on bootstrap.
12334 Changes in version 0.2.0.22-rc - 2008-03-18
12335 Tor 0.2.0.22-rc is the third release candidate for the 0.2.0 series. It
12336 enables encrypted directory connections by default for non-relays, fixes
12337 some broken TLS behavior we added in 0.2.0.20-rc, and resolves many
12338 other bugs. The bundles also include Vidalia 0.1.1 and Torbutton 1.1.17.
12341 - Enable encrypted directory connections by default for non-relays,
12342 so censor tools that block Tor directory connections based on their
12343 plaintext patterns will no longer work. This means Tor works in
12344 certain censored countries by default again.
12347 - Make sure servers always request certificates from clients during
12348 TLS renegotiation. Reported by lodger; bugfix on 0.2.0.20-rc.
12349 - Do not enter a CPU-eating loop when a connection is closed in
12350 the middle of client-side TLS renegotiation. Fixes bug 622. Bug
12351 diagnosed by lodger; bugfix on 0.2.0.20-rc.
12352 - Fix assertion failure that could occur when a blocked circuit
12353 became unblocked, and it had pending client DNS requests. Bugfix
12354 on 0.2.0.1-alpha. Fixes bug 632.
12356 o Minor bugfixes (on 0.1.2.x):
12357 - Generate "STATUS_SERVER" events rather than misspelled
12358 "STATUS_SEVER" events. Caught by mwenge.
12359 - When counting the number of bytes written on a TLS connection,
12360 look at the BIO actually used for writing to the network, not
12361 at the BIO used (sometimes) to buffer data for the network.
12362 Looking at different BIOs could result in write counts on the
12363 order of ULONG_MAX. Fixes bug 614.
12364 - On Windows, correctly detect errors when listing the contents of
12365 a directory. Fix from lodger.
12367 o Minor bugfixes (on 0.2.0.x):
12368 - Downgrade "sslv3 alert handshake failure" message to INFO.
12369 - If we set RelayBandwidthRate and RelayBandwidthBurst very high but
12370 left BandwidthRate and BandwidthBurst at the default, we would be
12371 silently limited by those defaults. Now raise them to match the
12372 RelayBandwidth* values.
12373 - Fix the SVK version detection logic to work correctly on a branch.
12374 - Make --enable-openbsd-malloc work correctly on Linux with alpha
12375 CPUs. Fixes bug 625.
12376 - Logging functions now check that the passed severity is sane.
12377 - Use proper log levels in the testsuite call of
12378 get_interface_address6().
12379 - When using a nonstandard malloc, do not use the platform values for
12380 HAVE_MALLOC_GOOD_SIZE or HAVE_MALLOC_USABLE_SIZE.
12381 - Make the openbsd malloc code use 8k pages on alpha CPUs and
12383 - Detect mismatched page sizes when using --enable-openbsd-malloc.
12384 - Avoid double-marked-for-close warning when certain kinds of invalid
12385 .in-addr.arpa addresses are passed to the DNSPort. Part of a fix
12386 for bug 617. Bugfix on 0.2.0.1-alpha.
12387 - Make sure that the "NULL-means-reject *:*" convention is followed by
12388 all the policy manipulation functions, avoiding some possible crash
12389 bugs. Bug found by lodger. Bugfix on 0.2.0.16-alpha.
12390 - Fix the implementation of ClientDNSRejectInternalAddresses so that it
12391 actually works, and doesn't warn about every single reverse lookup.
12392 Fixes the other part of bug 617. Bugfix on 0.2.0.1-alpha.
12395 - Only log guard node status when guard node status has changed.
12396 - Downgrade the 3 most common "INFO" messages to "DEBUG". This will
12397 make "INFO" 75% less verbose.
12400 Changes in version 0.2.0.21-rc - 2008-03-02
12401 Tor 0.2.0.21-rc is the second release candidate for the 0.2.0 series. It
12402 makes Tor work well with Vidalia again, fixes a rare assert bug,
12403 and fixes a pair of more minor bugs. The bundles also include Vidalia
12404 0.1.0 and Torbutton 1.1.16.
12407 - The control port should declare that it requires password auth
12408 when HashedControlSessionPassword is set too. Patch from Matt Edman;
12409 bugfix on 0.2.0.20-rc. Fixes bug 615.
12410 - Downgrade assert in connection_buckets_decrement() to a log message.
12411 This may help us solve bug 614, and in any case will make its
12412 symptoms less severe. Bugfix on 0.2.0.20-rc. Reported by fredzupy.
12413 - We were sometimes miscounting the number of bytes read from the
12414 network, causing our rate limiting to not be followed exactly.
12415 Bugfix on 0.2.0.16-alpha. Reported by lodger.
12418 - Fix compilation with OpenSSL 0.9.8 and 0.9.8a. All other supported
12419 OpenSSL versions should have been working fine. Diagnosis and patch
12420 from lodger, Karsten Loesing, and Sebastian Hahn. Fixes bug 616.
12421 Bugfix on 0.2.0.20-rc.
12424 Changes in version 0.2.0.20-rc - 2008-02-24
12425 Tor 0.2.0.20-rc is the first release candidate for the 0.2.0 series. It
12426 makes more progress towards normalizing Tor's TLS handshake, makes
12427 hidden services work better again, helps relays bootstrap if they don't
12428 know their IP address, adds optional support for linking in openbsd's
12429 allocator or tcmalloc, allows really fast relays to scale past 15000
12430 sockets, and fixes a bunch of minor bugs reported by Veracode.
12433 - Enable the revised TLS handshake based on the one designed by
12434 Steven Murdoch in proposal 124, as revised in proposal 130. It
12435 includes version negotiation for OR connections as described in
12436 proposal 105. The new handshake is meant to be harder for censors
12437 to fingerprint, and it adds the ability to detect certain kinds of
12438 man-in-the-middle traffic analysis attacks. The version negotiation
12439 feature will allow us to improve Tor's link protocol more safely
12441 - Choose which bridge to use proportional to its advertised bandwidth,
12442 rather than uniformly at random. This should speed up Tor for
12443 bridge users. Also do this for people who set StrictEntryNodes.
12444 - When a TrackHostExits-chosen exit fails too many times in a row,
12445 stop using it. Bugfix on 0.1.2.x; fixes bug 437.
12448 - Resolved problems with (re-)fetching hidden service descriptors.
12449 Patch from Karsten Loesing; fixes problems with 0.2.0.18-alpha
12450 and 0.2.0.19-alpha.
12451 - If we only ever used Tor for hidden service lookups or posts, we
12452 would stop building circuits and start refusing connections after
12453 24 hours, since we falsely believed that Tor was dormant. Reported
12454 by nwf; bugfix on 0.1.2.x.
12455 - Servers that don't know their own IP address should go to the
12456 authorities for their first directory fetch, even if their DirPort
12457 is off or if they don't know they're reachable yet. This will help
12458 them bootstrap better. Bugfix on 0.2.0.18-alpha; fixes bug 609.
12459 - When counting the number of open sockets, count not only the number
12460 of sockets we have received from the socket() call, but also
12461 the number we've gotten from accept() and socketpair(). This bug
12462 made us fail to count all sockets that we were using for incoming
12463 connections. Bugfix on 0.2.0.x.
12464 - Fix code used to find strings within buffers, when those strings
12465 are not in the first chunk of the buffer. Bugfix on 0.2.0.x.
12466 - Fix potential segfault when parsing HTTP headers. Bugfix on 0.2.0.x.
12467 - Add a new __HashedControlSessionPassword option for controllers
12468 to use for one-off session password hashes that shouldn't get
12469 saved to disk by SAVECONF --- Vidalia users were accumulating a
12470 pile of HashedControlPassword lines in their torrc files, one for
12471 each time they had restarted Tor and then clicked Save. Make Tor
12472 automatically convert "HashedControlPassword" to this new option but
12473 only when it's given on the command line. Partial fix for bug 586.
12475 o Minor features (performance):
12476 - Tune parameters for cell pool allocation to minimize amount of
12478 - Add OpenBSD malloc code from phk as an optional malloc
12479 replacement on Linux: some glibc libraries do very poorly
12480 with Tor's memory allocation patterns. Pass
12481 --enable-openbsd-malloc to get the replacement malloc code.
12482 - Add a --with-tcmalloc option to the configure script to link
12483 against tcmalloc (if present). Does not yet search for
12484 non-system include paths.
12485 - Stop imposing an arbitrary maximum on the number of file descriptors
12486 used for busy servers. Bug reported by Olaf Selke; patch from
12489 o Minor features (other):
12490 - When SafeLogging is disabled, log addresses along with all TLS
12492 - When building with --enable-gcc-warnings, check for whether Apple's
12493 warning "-Wshorten-64-to-32" is available.
12494 - Add a --passphrase-fd argument to the tor-gencert command for
12497 o Minor bugfixes (memory leaks and code problems):
12498 - We were leaking a file descriptor if Tor started with a zero-length
12499 cached-descriptors file. Patch by freddy77; bugfix on 0.1.2.
12500 - Detect size overflow in zlib code. Reported by Justin Ferguson and
12502 - We were comparing the raw BridgePassword entry with a base64'ed
12503 version of it, when handling a "/tor/networkstatus-bridges"
12504 directory request. Now compare correctly. Noticed by Veracode.
12505 - Recover from bad tracked-since value in MTBF-history file.
12506 Should fix bug 537.
12507 - Alter the code that tries to recover from unhandled write
12508 errors, to not try to flush onto a socket that's given us
12509 unhandled errors. Bugfix on 0.1.2.x.
12510 - Make Unix controlsockets work correctly on OpenBSD. Patch from
12511 tup. Bugfix on 0.2.0.3-alpha.
12513 o Minor bugfixes (other):
12514 - If we have an extra-info document for our server, always make
12515 it available on the control port, even if we haven't gotten
12516 a copy of it from an authority yet. Patch from mwenge.
12517 - Log the correct memory chunk sizes for empty RAM chunks in mempool.c.
12518 - Directory mirrors no longer include a guess at the client's IP
12519 address if the connection appears to be coming from the same /24
12520 network; it was producing too many wrong guesses.
12521 - Make the new hidden service code respect the SafeLogging setting.
12522 Bugfix on 0.2.0.x. Patch from Karsten.
12523 - When starting as an authority, do not overwrite all certificates
12524 cached from other authorities. Bugfix on 0.2.0.x. Fixes bug 606.
12525 - If we're trying to flush the last bytes on a connection (for
12526 example, when answering a directory request), reset the
12527 time-to-give-up timeout every time we manage to write something
12528 on the socket. Bugfix on 0.1.2.x.
12529 - Change the behavior of "getinfo status/good-server-descriptor"
12530 so it doesn't return failure when any authority disappears.
12531 - Even though the man page said that "TrackHostExits ." should
12532 work, nobody had ever implemented it. Bugfix on 0.1.0.x.
12533 - Report TLS "zero return" case as a "clean close" and "IO error"
12534 as a "close". Stop calling closes "unexpected closes": existing
12535 Tors don't use SSL_close(), so having a connection close without
12536 the TLS shutdown handshake is hardly unexpected.
12537 - Send NAMESERVER_STATUS messages for a single failed nameserver
12540 o Code simplifications and refactoring:
12541 - Remove the tor_strpartition function: its logic was confused,
12542 and it was only used for one thing that could be implemented far
12546 Changes in version 0.2.0.19-alpha - 2008-02-09
12547 Tor 0.2.0.19-alpha makes more progress towards normalizing Tor's TLS
12548 handshake, makes path selection for relays more secure and IP address
12549 guessing more robust, and generally fixes a lot of bugs in preparation
12550 for calling the 0.2.0 branch stable.
12553 - Do not include recognizeable strings in the commonname part of
12554 Tor's x509 certificates.
12557 - If we're a relay, avoid picking ourselves as an introduction point,
12558 a rendezvous point, or as the final hop for internal circuits. Bug
12559 reported by taranis and lodger. Bugfix on 0.1.2.x.
12560 - Patch from "Andrew S. Lists" to catch when we contact a directory
12561 mirror at IP address X and he says we look like we're coming from
12562 IP address X. Bugfix on 0.1.2.x.
12564 o Minor features (security):
12565 - Be more paranoid about overwriting sensitive memory on free(),
12566 as a defensive programming tactic to ensure forward secrecy.
12568 o Minor features (directory authority):
12569 - Actually validate the options passed to AuthDirReject,
12570 AuthDirInvalid, AuthDirBadDir, and AuthDirBadExit.
12571 - Reject router descriptors with out-of-range bandwidthcapacity or
12572 bandwidthburst values.
12574 o Minor features (controller):
12575 - Reject controller commands over 1MB in length. This keeps rogue
12576 processes from running us out of memory.
12578 o Minor features (misc):
12579 - Give more descriptive well-formedness errors for out-of-range
12580 hidden service descriptor/protocol versions.
12581 - Make memory debugging information describe more about history
12582 of cell allocation, so we can help reduce our memory use.
12584 o Deprecated features (controller):
12585 - The status/version/num-versioning and status/version/num-concurring
12586 GETINFO options are no longer useful in the v3 directory protocol:
12587 treat them as deprecated, and warn when they're used.
12590 - When our consensus networkstatus has been expired for a while, stop
12591 being willing to build circuits using it. Fixes bug 401. Bugfix
12593 - Directory caches now fetch certificates from all authorities
12594 listed in a networkstatus consensus, even when they do not
12595 recognize them. Fixes bug 571. Bugfix on 0.2.0.x.
12596 - When connecting to a bridge without specifying its key, insert
12597 the connection into the identity-to-connection map as soon as
12598 a key is learned. Fixes bug 574. Bugfix on 0.2.0.x.
12599 - Detect versions of OS X where malloc_good_size() is present in the
12600 library but never actually declared. Resolves bug 587. Bugfix
12602 - Stop incorrectly truncating zlib responses to directory authority
12603 signature download requests. Fixes bug 593. Bugfix on 0.2.0.x.
12604 - Stop recommending that every server operator send mail to tor-ops.
12605 Resolves bug 597. Bugfix on 0.1.2.x.
12606 - Don't trigger an assert if we start a directory authority with a
12607 private IP address (like 127.0.0.1).
12608 - Avoid possible failures when generating a directory with routers
12609 with over-long versions strings, or too many flags set. Bugfix
12611 - If an attempt to launch a DNS resolve request over the control
12612 port fails because we have overrun the limit on the number of
12613 connections, tell the controller that the request has failed.
12614 - Avoid using too little bandwidth when our clock skips a few
12615 seconds. Bugfix on 0.1.2.x.
12616 - Fix shell error when warning about missing packages in configure
12617 script, on Fedora or Red Hat machines. Bugfix on 0.2.0.x.
12618 - Do not become confused when receiving a spurious VERSIONS-like
12619 cell from a confused v1 client. Bugfix on 0.2.0.x.
12620 - Re-fetch v2 (as well as v0) rendezvous descriptors when all
12621 introduction points for a hidden service have failed. Patch from
12622 Karsten Loesing. Bugfix on 0.2.0.x.
12624 o Code simplifications and refactoring:
12625 - Remove some needless generality from cpuworker code, for improved
12627 - Stop overloading the circuit_t.onionskin field for both "onionskin
12628 from a CREATE cell that we are waiting for a cpuworker to be
12629 assigned" and "onionskin from an EXTEND cell that we are going to
12630 send to an OR as soon as we are connected". Might help with bug 600.
12631 - Add an in-place version of aes_crypt() so that we can avoid doing a
12632 needless memcpy() call on each cell payload.
12635 Changes in version 0.2.0.18-alpha - 2008-01-25
12636 Tor 0.2.0.18-alpha adds a sixth v3 directory authority run by CCC,
12637 fixes a big memory leak in 0.2.0.17-alpha, and adds new config options
12638 that can warn or reject connections to ports generally associated with
12639 vulnerable-plaintext protocols.
12641 o New directory authorities:
12642 - Set up dannenberg (run by CCC) as the sixth v3 directory
12646 - Fix a major memory leak when attempting to use the v2 TLS
12647 handshake code. Bugfix on 0.2.0.x; fixes bug 589.
12648 - We accidentally enabled the under-development v2 TLS handshake
12649 code, which was causing log entries like "TLS error while
12650 renegotiating handshake". Disable it again. Resolves bug 590.
12651 - We were computing the wrong Content-Length: header for directory
12652 responses that need to be compressed on the fly, causing clients
12653 asking for those items to always fail. Bugfix on 0.2.0.x; partially
12657 - Avoid going directly to the directory authorities even if you're a
12658 relay, if you haven't found yourself reachable yet or if you've
12659 decided not to advertise your dirport yet. Addresses bug 556.
12660 - If we've gone 12 hours since our last bandwidth check, and we
12661 estimate we have less than 50KB bandwidth capacity but we could
12662 handle more, do another bandwidth test.
12663 - New config options WarnPlaintextPorts and RejectPlaintextPorts so
12664 Tor can warn and/or refuse connections to ports commonly used with
12665 vulnerable-plaintext protocols. Currently we warn on ports 23,
12666 109, 110, and 143, but we don't reject any.
12669 - When we setconf ClientOnly to 1, close any current OR and Dir
12670 listeners. Reported by mwenge.
12671 - When we get a consensus that's been signed by more people than
12672 we expect, don't log about it; it's not a big deal. Reported
12676 - Don't answer "/tor/networkstatus-bridges" directory requests if
12677 the request isn't encrypted.
12678 - Make "ClientOnly 1" config option disable directory ports too.
12679 - Patches from Karsten Loesing to make v2 hidden services more
12680 robust: work even when there aren't enough HSDir relays available;
12681 retry when a v2 rend desc fetch fails; but don't retry if we
12682 already have a usable v0 rend desc.
12685 Changes in version 0.2.0.17-alpha - 2008-01-17
12686 Tor 0.2.0.17-alpha makes the tarball build cleanly again (whoops).
12689 - Make the tor-gencert man page get included correctly in the tarball.
12692 Changes in version 0.2.0.16-alpha - 2008-01-17
12693 Tor 0.2.0.16-alpha adds a fifth v3 directory authority run by Karsten
12694 Loesing, and generally cleans up a lot of features and minor bugs.
12696 o New directory authorities:
12697 - Set up gabelmoo (run by Karsten Loesing) as the fifth v3 directory
12700 o Major performance improvements:
12701 - Switch our old ring buffer implementation for one more like that
12702 used by free Unix kernels. The wasted space in a buffer with 1mb
12703 of data will now be more like 8k than 1mb. The new implementation
12704 also avoids realloc();realloc(); patterns that can contribute to
12705 memory fragmentation.
12708 - Configuration files now accept C-style strings as values. This
12709 helps encode characters not allowed in the current configuration
12710 file format, such as newline or #. Addresses bug 557.
12711 - Although we fixed bug 539 (where servers would send HTTP status 503
12712 responses _and_ send a body too), there are still servers out
12713 there that haven't upgraded. Therefore, make clients parse such
12714 bodies when they receive them.
12715 - When we're not serving v2 directory information, there is no reason
12716 to actually keep any around. Remove the obsolete files and directory
12717 on startup if they are very old and we aren't going to serve them.
12719 o Minor performance improvements:
12720 - Reference-count and share copies of address policy entries; only 5%
12721 of them were actually distinct.
12722 - Never walk through the list of logs if we know that no log is
12723 interested in a given message.
12726 - When an authority has not signed a consensus, do not try to
12727 download a nonexistent "certificate with key 00000000". Bugfix
12728 on 0.2.0.x. Fixes bug 569.
12729 - Fix a rare assert error when we're closing one of our threads:
12730 use a mutex to protect the list of logs, so we never write to the
12731 list as it's being freed. Bugfix on 0.1.2.x. Fixes the very rare
12732 bug 575, which is kind of the revenge of bug 222.
12733 - Patch from Karsten Loesing to complain less at both the client
12734 and the relay when a relay used to have the HSDir flag but doesn't
12735 anymore, and we try to upload a hidden service descriptor.
12736 - Stop leaking one cert per TLS context. Fixes bug 582. Bugfix on
12738 - Do not try to download missing certificates until we have tried
12739 to check our fallback consensus. Fixes bug 583.
12740 - Make bridges round reported GeoIP stats info up to the nearest
12741 estimate, not down. Now we can distinguish between "0 people from
12742 this country" and "1 person from this country".
12743 - Avoid a spurious free on base64 failure. Bugfix on 0.1.2.
12744 - Avoid possible segfault if key generation fails in
12745 crypto_pk_hybrid_encrypt. Bugfix on 0.2.0.
12746 - Avoid segfault in the case where a badly behaved v2 versioning
12747 directory sends a signed networkstatus with missing client-versions.
12749 - Avoid segfaults on certain complex invocations of
12750 router_get_by_hexdigest(). Bugfix on 0.1.2.
12751 - Correct bad index on array access in parse_http_time(). Bugfix
12753 - Fix possible bug in vote generation when server versions are present
12754 but client versions are not.
12755 - Fix rare bug on REDIRECTSTREAM control command when called with no
12756 port set: it could erroneously report an error when none had
12758 - Avoid bogus crash-prone, leak-prone tor_realloc when we're
12759 compressing large objects and find ourselves with more than 4k
12760 left over. Bugfix on 0.2.0.
12761 - Fix a small memory leak when setting up a hidden service.
12762 - Fix a few memory leaks that could in theory happen under bizarre
12764 - Fix an assert if we post a general-purpose descriptor via the
12765 control port but that descriptor isn't mentioned in our current
12766 network consensus. Bug reported by Jon McLachlan; bugfix on
12769 o Minor features (controller):
12770 - Get NS events working again. Patch from tup.
12771 - The GETCONF command now escapes and quotes configuration values
12772 that don't otherwise fit into the torrc file.
12773 - The SETCONF command now handles quoted values correctly.
12775 o Minor features (directory authorities):
12776 - New configuration options to override default maximum number of
12777 servers allowed on a single IP address. This is important for
12778 running a test network on a single host.
12779 - Actually implement the -s option to tor-gencert.
12780 - Add a manual page for tor-gencert.
12782 o Minor features (bridges):
12783 - Bridge authorities no longer serve bridge descriptors over
12784 unencrypted connections.
12786 o Minor features (other):
12787 - Add hidden services and DNSPorts to the list of things that make
12788 Tor accept that it has running ports. Change starting Tor with no
12789 ports from a fatal error to a warning; we might change it back if
12790 this turns out to confuse anybody. Fixes bug 579.
12793 Changes in version 0.1.2.19 - 2008-01-17
12794 Tor 0.1.2.19 fixes a huge memory leak on exit relays, makes the default
12795 exit policy a little bit more conservative so it's safer to run an
12796 exit relay on a home system, and fixes a variety of smaller issues.
12799 - Exit policies now reject connections that are addressed to a
12800 relay's public (external) IP address too, unless
12801 ExitPolicyRejectPrivate is turned off. We do this because too
12802 many relays are running nearby to services that trust them based
12803 on network address.
12806 - When the clock jumps forward a lot, do not allow the bandwidth
12807 buckets to become negative. Fixes bug 544.
12808 - Fix a memory leak on exit relays; we were leaking a cached_resolve_t
12809 on every successful resolve. Reported by Mike Perry.
12810 - Purge old entries from the "rephist" database and the hidden
12811 service descriptor database even when DirPort is zero.
12812 - Stop thinking that 0.1.2.x directory servers can handle "begin_dir"
12813 requests. Should ease bugs 406 and 419 where 0.1.2.x relays are
12814 crashing or mis-answering these requests.
12815 - When we decide to send a 503 response to a request for servers, do
12816 not then also send the server descriptors: this defeats the whole
12817 purpose. Fixes bug 539.
12820 - Changing the ExitPolicyRejectPrivate setting should cause us to
12821 rebuild our server descriptor.
12822 - Fix handling of hex nicknames when answering controller requests for
12823 networkstatus by name, or when deciding whether to warn about
12824 unknown routers in a config option. (Patch from mwenge.)
12825 - Fix a couple of hard-to-trigger autoconf problems that could result
12826 in really weird results on platforms whose sys/types.h files define
12827 nonstandard integer types.
12828 - Don't try to create the datadir when running --verify-config or
12829 --hash-password. Resolves bug 540.
12830 - If we were having problems getting a particular descriptor from the
12831 directory caches, and then we learned about a new descriptor for
12832 that router, we weren't resetting our failure count. Reported
12834 - Although we fixed bug 539 (where servers would send HTTP status 503
12835 responses _and_ send a body too), there are still servers out there
12836 that haven't upgraded. Therefore, make clients parse such bodies
12837 when they receive them.
12838 - Run correctly on systems where rlim_t is larger than unsigned long.
12839 This includes some 64-bit systems.
12840 - Run correctly on platforms (like some versions of OS X 10.5) where
12841 the real limit for number of open files is OPEN_FILES, not rlim_max
12842 from getrlimit(RLIMIT_NOFILES).
12843 - Avoid a spurious free on base64 failure.
12844 - Avoid segfaults on certain complex invocations of
12845 router_get_by_hexdigest().
12846 - Fix rare bug on REDIRECTSTREAM control command when called with no
12847 port set: it could erroneously report an error when none had
12851 Changes in version 0.2.0.15-alpha - 2007-12-25
12852 Tor 0.2.0.14-alpha and 0.2.0.15-alpha fix a bunch of bugs with the
12853 features added in 0.2.0.13-alpha.
12856 - Fix several remotely triggerable asserts based on DirPort requests
12857 for a v2 or v3 networkstatus object before we were prepared. This
12858 was particularly bad for 0.2.0.13 and later bridge relays, who
12859 would never have a v2 networkstatus and would thus always crash
12860 when used. Bugfixes on 0.2.0.x.
12861 - Estimate the v3 networkstatus size more accurately, rather than
12862 estimating it at zero bytes and giving it artificially high priority
12863 compared to other directory requests. Bugfix on 0.2.0.x.
12866 - Fix configure.in logic for cross-compilation.
12867 - When we load a bridge descriptor from the cache, and it was
12868 previously unreachable, mark it as retriable so we won't just
12869 ignore it. Also, try fetching a new copy immediately. Bugfixes
12871 - The bridge GeoIP stats were counting other relays, for example
12872 self-reachability and authority-reachability tests.
12875 - Support compilation to target iPhone; patch from cjacker huang.
12876 To build for iPhone, pass the --enable-iphone option to configure.
12879 Changes in version 0.2.0.14-alpha - 2007-12-23
12881 - Fix a crash on startup if you install Tor 0.2.0.13-alpha fresh
12882 without a datadirectory from a previous Tor install. Reported
12884 - Fix a crash when we fetch a descriptor that turns out to be
12885 unexpected (it used to be in our networkstatus when we started
12886 fetching it, but it isn't in our current networkstatus), and we
12887 aren't using bridges. Bugfix on 0.2.0.x.
12888 - Fix a crash when accessing hidden services: it would work the first
12889 time you use a given introduction point for your service, but
12890 on subsequent requests we'd be using garbage memory. Fixed by
12891 Karsten Loesing. Bugfix on 0.2.0.13-alpha.
12892 - Fix a crash when we load a bridge descriptor from disk but we don't
12893 currently have a Bridge line for it in our torrc. Bugfix on
12897 - If bridge authorities set BridgePassword, they will serve a
12898 snapshot of known bridge routerstatuses from their DirPort to
12899 anybody who knows that password. Unset by default.
12902 - Make the unit tests build again.
12903 - Make "GETINFO/desc-annotations/id/<OR digest>" actually work.
12904 - Make PublishServerDescriptor default to 1, so the default doesn't
12905 have to change as we invent new directory protocol versions.
12906 - Fix test for rlim_t on OSX 10.3: sys/resource.h doesn't want to
12907 be included unless sys/time.h is already included. Fixes
12908 bug 553. Bugfix on 0.2.0.x.
12909 - If we receive a general-purpose descriptor and then receive an
12910 identical bridge-purpose descriptor soon after, don't discard
12911 the next one as a duplicate.
12914 - If BridgeRelay is set to 1, then the default for
12915 PublishServerDescriptor is now "bridge" rather than "v2,v3".
12916 - If the user sets RelayBandwidthRate but doesn't set
12917 RelayBandwidthBurst, then make them equal rather than erroring out.
12920 Changes in version 0.2.0.13-alpha - 2007-12-21
12921 Tor 0.2.0.13-alpha adds a fourth v3 directory authority run by Geoff
12922 Goodell, fixes many more bugs, and adds a lot of infrastructure for
12925 o New directory authorities:
12926 - Set up lefkada (run by Geoff Goodell) as the fourth v3 directory
12930 - Only update guard status (usable / not usable) once we have
12931 enough directory information. This was causing us to always pick
12932 two new guards on startup (bugfix on 0.2.0.9-alpha), and it was
12933 causing us to discard all our guards on startup if we hadn't been
12934 running for a few weeks (bugfix on 0.1.2.x). Fixes bug 448.
12935 - Purge old entries from the "rephist" database and the hidden
12936 service descriptor databases even when DirPort is zero. Bugfix
12938 - We were ignoring our RelayBandwidthRate for the first 30 seconds
12939 after opening a circuit -- even a relayed circuit. Bugfix on
12941 - Stop thinking that 0.1.2.x directory servers can handle "begin_dir"
12942 requests. Should ease bugs 406 and 419 where 0.1.2.x relays are
12943 crashing or mis-answering these types of requests.
12944 - Relays were publishing their server descriptor to v1 and v2
12945 directory authorities, but they didn't try publishing to v3-only
12946 authorities. Fix this; and also stop publishing to v1 authorities.
12948 - When we were reading router descriptors from cache, we were ignoring
12949 the annotations -- so for example we were reading in bridge-purpose
12950 descriptors as general-purpose descriptors. Bugfix on 0.2.0.8-alpha.
12951 - When we decided to send a 503 response to a request for servers, we
12952 were then also sending the server descriptors: this defeats the
12953 whole purpose. Fixes bug 539; bugfix on 0.1.2.x.
12956 - Bridge relays now behave like clients with respect to time
12957 intervals for downloading new consensus documents -- otherwise they
12958 stand out. Bridge users now wait until the end of the interval,
12959 so their bridge relay will be sure to have a new consensus document.
12960 - Three new config options (AlternateDirAuthority,
12961 AlternateBridgeAuthority, and AlternateHSAuthority) that let the
12962 user selectively replace the default directory authorities by type,
12963 rather than the all-or-nothing replacement that DirServer offers.
12964 - Tor can now be configured to read a GeoIP file from disk in one
12965 of two formats. This can be used by controllers to map IP addresses
12966 to countries. Eventually, it may support exit-by-country.
12967 - When possible, bridge relays remember which countries users
12968 are coming from, and report aggregate information in their
12969 extra-info documents, so that the bridge authorities can learn
12970 where Tor is blocked.
12971 - Bridge directory authorities now do reachability testing on the
12972 bridges they know. They provide router status summaries to the
12973 controller via "getinfo ns/purpose/bridge", and also dump summaries
12974 to a file periodically.
12975 - Stop fetching directory info so aggressively if your DirPort is
12976 on but your ORPort is off; stop fetching v2 dir info entirely.
12977 You can override these choices with the new FetchDirInfoEarly
12981 - The fix in 0.2.0.12-alpha cleared the "hsdir" flag in v3 network
12982 consensus documents when there are too many relays at a single
12983 IP address. Now clear it in v2 network status documents too, and
12984 also clear it in routerinfo_t when the relay is no longer listed
12985 in the relevant networkstatus document.
12986 - Don't crash if we get an unexpected value for the
12987 PublishServerDescriptor config option. Reported by Matt Edman;
12988 bugfix on 0.2.0.9-alpha.
12989 - Our new v2 hidden service descriptor format allows descriptors
12990 that have no introduction points. But Tor crashed when we tried
12991 to build a descriptor with no intro points (and it would have
12992 crashed if we had tried to parse one). Bugfix on 0.2.0.x; patch
12993 by Karsten Loesing.
12994 - Fix building with dmalloc 5.5.2 with glibc.
12995 - Reject uploaded descriptors and extrainfo documents if they're
12996 huge. Otherwise we'll cache them all over the network and it'll
12997 clog everything up. Reported by Aljosha Judmayer.
12998 - Check for presence of s6_addr16 and s6_addr32 fields in in6_addr
12999 via autoconf. Should fix compile on solaris. Bugfix on 0.2.0.x.
13000 - When the DANGEROUS_VERSION controller status event told us we're
13001 running an obsolete version, it used the string "OLD" to describe
13002 it. Yet the "getinfo" interface used the string "OBSOLETE". Now use
13003 "OBSOLETE" in both cases. Bugfix on 0.1.2.x.
13004 - If we can't expand our list of entry guards (e.g. because we're
13005 using bridges or we have StrictEntryNodes set), don't mark relays
13006 down when they fail a directory request. Otherwise we're too quick
13007 to mark all our entry points down. Bugfix on 0.1.2.x.
13008 - Fix handling of hex nicknames when answering controller requests for
13009 networkstatus by name, or when deciding whether to warn about unknown
13010 routers in a config option. Bugfix on 0.1.2.x. (Patch from mwenge.)
13011 - Fix a couple of hard-to-trigger autoconf problems that could result
13012 in really weird results on platforms whose sys/types.h files define
13013 nonstandard integer types. Bugfix on 0.1.2.x.
13014 - Fix compilation with --disable-threads set. Bugfix on 0.2.0.x.
13015 - Don't crash on name lookup when we have no current consensus. Fixes
13016 bug 538; bugfix on 0.2.0.x.
13017 - Only Tors that want to mirror the v2 directory info should
13018 create the "cached-status" directory in their datadir. (All Tors
13019 used to create it.) Bugfix on 0.2.0.9-alpha.
13020 - Directory authorities should only automatically download Extra Info
13021 documents if they're v1, v2, or v3 authorities. Bugfix on 0.1.2.x.
13024 - On the USR1 signal, when dmalloc is in use, log the top 10 memory
13025 consumers. (We already do this on HUP.)
13026 - Authorities and caches fetch the v2 networkstatus documents
13027 less often, now that v3 is encouraged.
13028 - Add a new config option BridgeRelay that specifies you want to
13029 be a bridge relay. Right now the only difference is that it makes
13030 you answer begin_dir requests, and it makes you cache dir info,
13031 even if your DirPort isn't on.
13032 - Add "GETINFO/desc-annotations/id/<OR digest>" so controllers can
13033 ask about source, timestamp of arrival, purpose, etc. We need
13034 something like this to help Vidalia not do GeoIP lookups on bridge
13036 - Allow multiple HashedControlPassword config lines, to support
13037 multiple controller passwords.
13038 - Authorities now decide whether they're authoritative for a given
13039 router based on the router's purpose.
13040 - New config options AuthDirBadDir and AuthDirListBadDirs for
13041 authorities to mark certain relays as "bad directories" in the
13042 networkstatus documents. Also supports the "!baddir" directive in
13043 the approved-routers file.
13046 Changes in version 0.2.0.12-alpha - 2007-11-16
13047 This twelfth development snapshot fixes some more build problems as
13048 well as a few minor bugs.
13051 - Make it build on OpenBSD again. Patch from tup.
13052 - Substitute BINDIR and LOCALSTATEDIR in scripts. Fixes
13053 package-building for Red Hat, OS X, etc.
13055 o Minor bugfixes (on 0.1.2.x):
13056 - Changing the ExitPolicyRejectPrivate setting should cause us to
13057 rebuild our server descriptor.
13059 o Minor bugfixes (on 0.2.0.x):
13060 - When we're lacking a consensus, don't try to perform rendezvous
13061 operations. Reported by Karsten Loesing.
13062 - Fix a small memory leak whenever we decide against using a
13063 newly picked entry guard. Reported by Mike Perry.
13064 - When authorities detected more than two relays running on the same
13065 IP address, they were clearing all the status flags but forgetting
13066 to clear the "hsdir" flag. So clients were being told that a
13067 given relay was the right choice for a v2 hsdir lookup, yet they
13068 never had its descriptor because it was marked as 'not running'
13070 - If we're trying to fetch a bridge descriptor and there's no way
13071 the bridge authority could help us (for example, we don't know
13072 a digest, or there is no bridge authority), don't be so eager to
13073 fall back to asking the bridge authority.
13074 - If we're using bridges or have strictentrynodes set, and our
13075 chosen exit is in the same family as all our bridges/entry guards,
13076 then be flexible about families.
13079 - When we negotiate a v2 link-layer connection (not yet implemented),
13080 accept RELAY_EARLY cells and turn them into RELAY cells if we've
13081 negotiated a v1 connection for their next step. Initial code for
13085 Changes in version 0.2.0.11-alpha - 2007-11-12
13086 This eleventh development snapshot fixes some build problems with
13087 the previous snapshot. It also includes a more secure-by-default exit
13088 policy for relays, fixes an enormous memory leak for exit relays, and
13089 fixes another bug where servers were falling out of the directory list.
13092 - Exit policies now reject connections that are addressed to a
13093 relay's public (external) IP address too, unless
13094 ExitPolicyRejectPrivate is turned off. We do this because too
13095 many relays are running nearby to services that trust them based
13096 on network address. Bugfix on 0.1.2.x.
13099 - Fix a memory leak on exit relays; we were leaking a cached_resolve_t
13100 on every successful resolve. Reported by Mike Perry; bugfix
13102 - On authorities, never downgrade to old router descriptors simply
13103 because they're listed in the consensus. This created a catch-22
13104 where we wouldn't list a new descriptor because there was an
13105 old one in the consensus, and we couldn't get the new one in the
13106 consensus because we wouldn't list it. Possible fix for bug 548.
13107 Also, this might cause bug 543 to appear on authorities; if so,
13108 we'll need a band-aid for that. Bugfix on 0.2.0.9-alpha.
13110 o Packaging fixes on 0.2.0.10-alpha:
13111 - We were including instructions about what to do with the
13112 src/config/fallback-consensus file, but we weren't actually
13113 including it in the tarball. Disable all of that for now.
13116 - Allow people to say PreferTunnelledDirConns rather than
13117 PreferTunneledDirConns, for those alternate-spellers out there.
13120 - Don't reevaluate all the information from our consensus document
13121 just because we've downloaded a v2 networkstatus that we intend
13122 to cache. Fixes bug 545; bugfix on 0.2.0.x.
13125 Changes in version 0.2.0.10-alpha - 2007-11-10
13126 This tenth development snapshot adds a third v3 directory authority
13127 run by Mike Perry, adds most of Karsten Loesing's new hidden service
13128 descriptor format, fixes a bad crash bug and new bridge bugs introduced
13129 in 0.2.0.9-alpha, fixes many bugs with the v3 directory implementation,
13130 fixes some minor memory leaks in previous 0.2.0.x snapshots, and
13131 addresses many more minor issues.
13133 o New directory authorities:
13134 - Set up ides (run by Mike Perry) as the third v3 directory authority.
13137 - Allow tunnelled directory connections to ask for an encrypted
13138 "begin_dir" connection or an anonymized "uses a full Tor circuit"
13139 connection independently. Now we can make anonymized begin_dir
13140 connections for (e.g.) more secure hidden service posting and
13142 - More progress on proposal 114: code from Karsten Loesing to
13143 implement new hidden service descriptor format.
13144 - Raise the default BandwidthRate/BandwidthBurst to 5MB/10MB, to
13145 accommodate the growing number of servers that use the default
13146 and are reaching it.
13147 - Directory authorities use a new formula for selecting which nodes
13148 to advertise as Guards: they must be in the top 7/8 in terms of
13149 how long we have known about them, and above the median of those
13150 nodes in terms of weighted fractional uptime.
13151 - Make "not enough dir info yet" warnings describe *why* Tor feels
13152 it doesn't have enough directory info yet.
13155 - Stop servers from crashing if they set a Family option (or
13156 maybe in other situations too). Bugfix on 0.2.0.9-alpha; reported
13158 - Make bridge users work again -- the move to v3 directories in
13159 0.2.0.9-alpha had introduced a number of bugs that made bridges
13160 no longer work for clients.
13161 - When the clock jumps forward a lot, do not allow the bandwidth
13162 buckets to become negative. Bugfix on 0.1.2.x; fixes bug 544.
13164 o Major bugfixes (v3 dir, bugfixes on 0.2.0.9-alpha):
13165 - When the consensus lists a router descriptor that we previously were
13166 mirroring, but that we considered non-canonical, reload the
13167 descriptor as canonical. This fixes bug 543 where Tor servers
13168 would start complaining after a few days that they don't have
13169 enough directory information to build a circuit.
13170 - Consider replacing the current consensus when certificates arrive
13171 that make the pending consensus valid. Previously, we were only
13172 considering replacement when the new certs _didn't_ help.
13173 - Fix an assert error on startup if we didn't already have the
13174 consensus and certs cached in our datadirectory: we were caching
13175 the consensus in consensus_waiting_for_certs but then free'ing it
13177 - Avoid sending a request for "keys/fp" (for which we'll get a 400 Bad
13178 Request) if we need more v3 certs but we've already got pending
13179 requests for all of them.
13180 - Correctly back off from failing certificate downloads. Fixes
13182 - Authorities don't vote on the Running flag if they have been running
13183 for less than 30 minutes themselves. Fixes bug 547, where a newly
13184 started authority would vote that everyone was down.
13186 o New requirements:
13187 - Drop support for OpenSSL version 0.9.6. Just about nobody was using
13188 it, it had no AES, and it hasn't seen any security patches since
13192 - Clients now hold circuitless TLS connections open for 1.5 times
13193 MaxCircuitDirtiness (15 minutes), since it is likely that they'll
13194 rebuild a new circuit over them within that timeframe. Previously,
13195 they held them open only for KeepalivePeriod (5 minutes).
13196 - Use "If-Modified-Since" to avoid retrieving consensus
13197 networkstatuses that we already have.
13198 - When we have no consensus, check FallbackNetworkstatusFile (defaults
13199 to $PREFIX/share/tor/fallback-consensus) for a consensus. This way
13200 we start knowing some directory caches.
13201 - When we receive a consensus from the future, warn about skew.
13202 - Improve skew reporting: try to give the user a better log message
13203 about how skewed they are, and how much this matters.
13204 - When we have a certificate for an authority, believe that
13205 certificate's claims about the authority's IP address.
13206 - New --quiet command-line option to suppress the default console log.
13207 Good in combination with --hash-password.
13208 - Authorities send back an X-Descriptor-Not-New header in response to
13209 an accepted-but-discarded descriptor upload. Partially implements
13211 - Make the log message for "tls error. breaking." more useful.
13212 - Better log messages about certificate downloads, to attempt to
13213 track down the second incarnation of bug 546.
13215 o Minor features (bridges):
13216 - If bridge users set UpdateBridgesFromAuthority, but the digest
13217 they ask for is a 404 from the bridge authority, they now fall
13218 back to trying the bridge directly.
13219 - Bridges now use begin_dir to publish their server descriptor to
13220 the bridge authority, even when they haven't set TunnelDirConns.
13222 o Minor features (controller):
13223 - When reporting clock skew, and we know that the clock is _at least
13224 as skewed_ as some value, but we don't know the actual value,
13225 report the value as a "minimum skew."
13228 - Update linux-tor-prio.sh script to allow QoS based on the uid of
13229 the Tor process. Patch from Marco Bonetti with tweaks from Mike
13233 - Refuse to start if both ORPort and UseBridges are set. Bugfix
13234 on 0.2.0.x, suggested by Matt Edman.
13235 - Don't stop fetching descriptors when FetchUselessDescriptors is
13236 set, even if we stop asking for circuits. Bugfix on 0.1.2.x;
13237 reported by tup and ioerror.
13238 - Better log message on vote from unknown authority.
13239 - Don't log "Launching 0 request for 0 router" message.
13241 o Minor bugfixes (memory leaks):
13242 - Stop leaking memory every time we parse a v3 certificate. Bugfix
13244 - Stop leaking memory every time we load a v3 certificate. Bugfix
13245 on 0.2.0.1-alpha. Fixes bug 536.
13246 - Stop leaking a cached networkstatus on exit. Bugfix on
13248 - Stop leaking voter information every time we free a consensus.
13249 Bugfix on 0.2.0.3-alpha.
13250 - Stop leaking signed data every time we check a voter signature.
13251 Bugfix on 0.2.0.3-alpha.
13252 - Stop leaking a signature every time we fail to parse a consensus or
13253 a vote. Bugfix on 0.2.0.3-alpha.
13254 - Stop leaking v2_download_status_map on shutdown. Bugfix on
13256 - Stop leaking conn->nickname every time we make a connection to a
13257 Tor relay without knowing its expected identity digest (e.g. when
13258 using bridges). Bugfix on 0.2.0.3-alpha.
13260 - Minor bugfixes (portability):
13261 - Run correctly on platforms where rlim_t is larger than unsigned
13262 long, and/or where the real limit for number of open files is
13263 OPEN_FILES, not rlim_max from getrlimit(RLIMIT_NOFILES). In
13264 particular, these may be needed for OS X 10.5.
13267 Changes in version 0.1.2.18 - 2007-10-28
13268 Tor 0.1.2.18 fixes many problems including crash bugs, problems with
13269 hidden service introduction that were causing huge delays, and a big
13270 bug that was causing some servers to disappear from the network status
13271 lists for a few hours each day.
13273 o Major bugfixes (crashes):
13274 - If a connection is shut down abruptly because of something that
13275 happened inside connection_flushed_some(), do not call
13276 connection_finished_flushing(). Should fix bug 451:
13277 "connection_stop_writing: Assertion conn->write_event failed"
13278 Bugfix on 0.1.2.7-alpha.
13279 - Fix possible segfaults in functions called from
13280 rend_process_relay_cell().
13282 o Major bugfixes (hidden services):
13283 - Hidden services were choosing introduction points uniquely by
13284 hexdigest, but when constructing the hidden service descriptor
13285 they merely wrote the (potentially ambiguous) nickname.
13286 - Clients now use the v2 intro format for hidden service
13287 connections: they specify their chosen rendezvous point by identity
13288 digest rather than by (potentially ambiguous) nickname. These
13289 changes could speed up hidden service connections dramatically.
13291 o Major bugfixes (other):
13292 - Stop publishing a new server descriptor just because we get a
13293 HUP signal. This led (in a roundabout way) to some servers getting
13294 dropped from the networkstatus lists for a few hours each day.
13295 - When looking for a circuit to cannibalize, consider family as well
13296 as identity. Fixes bug 438. Bugfix on 0.1.0.x (which introduced
13297 circuit cannibalization).
13298 - When a router wasn't listed in a new networkstatus, we were leaving
13299 the flags for that router alone -- meaning it remained Named,
13300 Running, etc -- even though absence from the networkstatus means
13301 that it shouldn't be considered to exist at all anymore. Now we
13302 clear all the flags for routers that fall out of the networkstatus
13303 consensus. Fixes bug 529.
13306 - Don't try to access (or alter) the state file when running
13307 --list-fingerprint or --verify-config or --hash-password. Resolves
13309 - When generating information telling us how to extend to a given
13310 router, do not try to include the nickname if it is
13311 absent. Resolves bug 467.
13312 - Fix a user-triggerable segfault in expand_filename(). (There isn't
13313 a way to trigger this remotely.)
13314 - When sending a status event to the controller telling it that an
13315 OR address is reachable, set the port correctly. (Previously we
13316 were reporting the dir port.)
13317 - Fix a minor memory leak whenever a controller sends the PROTOCOLINFO
13318 command. Bugfix on 0.1.2.17.
13319 - When loading bandwidth history, do not believe any information in
13320 the future. Fixes bug 434.
13321 - When loading entry guard information, do not believe any information
13323 - When we have our clock set far in the future and generate an
13324 onion key, then re-set our clock to be correct, we should not stop
13325 the onion key from getting rotated.
13326 - On some platforms, accept() can return a broken address. Detect
13327 this more quietly, and deal accordingly. Fixes bug 483.
13328 - It's not actually an error to find a non-pending entry in the DNS
13329 cache when canceling a pending resolve. Don't log unless stuff
13330 is fishy. Resolves bug 463.
13331 - Don't reset trusted dir server list when we set a configuration
13332 option. Patch from Robert Hogan.
13333 - Don't try to create the datadir when running --verify-config or
13334 --hash-password. Resolves bug 540.
13337 Changes in version 0.2.0.9-alpha - 2007-10-24
13338 This ninth development snapshot switches clients to the new v3 directory
13339 system; allows servers to be listed in the network status even when they
13340 have the same nickname as a registered server; and fixes many other
13341 bugs including a big one that was causing some servers to disappear
13342 from the network status lists for a few hours each day.
13344 o Major features (directory system):
13345 - Clients now download v3 consensus networkstatus documents instead
13346 of v2 networkstatus documents. Clients and caches now base their
13347 opinions about routers on these consensus documents. Clients only
13348 download router descriptors listed in the consensus.
13349 - Authorities now list servers who have the same nickname as
13350 a different named server, but list them with a new flag,
13351 "Unnamed". Now we can list servers that happen to pick the same
13352 nickname as a server that registered two years ago and then
13353 disappeared. Partially implements proposal 122.
13354 - If the consensus lists a router as "Unnamed", the name is assigned
13355 to a different router: do not identify the router by that name.
13356 Partially implements proposal 122.
13357 - Authorities can now come to a consensus on which method to use to
13358 compute the consensus. This gives us forward compatibility.
13361 - Stop publishing a new server descriptor just because we HUP or
13362 when we find our DirPort to be reachable but won't actually publish
13363 it. New descriptors without any real changes are dropped by the
13364 authorities, and can screw up our "publish every 18 hours" schedule.
13366 - When a router wasn't listed in a new networkstatus, we were leaving
13367 the flags for that router alone -- meaning it remained Named,
13368 Running, etc -- even though absence from the networkstatus means
13369 that it shouldn't be considered to exist at all anymore. Now we
13370 clear all the flags for routers that fall out of the networkstatus
13371 consensus. Fixes bug 529; bugfix on 0.1.2.x.
13372 - Fix awful behavior in DownloadExtraInfo option where we'd fetch
13373 extrainfo documents and then discard them immediately for not
13374 matching the latest router. Bugfix on 0.2.0.1-alpha.
13376 o Minor features (v3 directory protocol):
13377 - Allow tor-gencert to generate a new certificate without replacing
13379 - Allow certificates to include an address.
13380 - When we change our directory-cache settings, reschedule all voting
13381 and download operations.
13382 - Reattempt certificate downloads immediately on failure, as long as
13383 we haven't failed a threshold number of times yet.
13384 - Delay retrying consensus downloads while we're downloading
13385 certificates to verify the one we just got. Also, count getting a
13386 consensus that we already have (or one that isn't valid) as a failure,
13387 and count failing to get the certificates after 20 minutes as a
13389 - Build circuits and download descriptors even if our consensus is a
13390 little expired. (This feature will go away once authorities are
13393 o Minor features (router descriptor cache):
13394 - If we find a cached-routers file that's been sitting around for more
13395 than 28 days unmodified, then most likely it's a leftover from
13396 when we upgraded to 0.2.0.8-alpha. Remove it. It has no good
13398 - When we (as a cache) download a descriptor because it was listed
13399 in a consensus, remember when the consensus was supposed to expire,
13400 and don't expire the descriptor until then.
13402 o Minor features (performance):
13403 - Call routerlist_remove_old_routers() much less often. This should
13404 speed startup, especially on directory caches.
13405 - Don't try to launch new descriptor downloads quite so often when we
13406 already have enough directory information to build circuits.
13407 - Base64 decoding was actually showing up on our profile when parsing
13408 the initial descriptor file; switch to an in-process all-at-once
13409 implementation that's about 3.5x times faster than calling out to
13412 o Minor features (compilation):
13413 - Detect non-ASCII platforms (if any still exist) and refuse to
13414 build there: some of our code assumes that 'A' is 65 and so on.
13416 o Minor bugfixes (v3 directory authorities, bugfixes on 0.2.0.x):
13417 - Make the "next period" votes into "current period" votes immediately
13418 after publishing the consensus; avoid a heisenbug that made them
13419 stick around indefinitely.
13420 - When we discard a vote as a duplicate, do not report this as
13422 - Treat missing v3 keys or certificates as an error when running as a
13423 v3 directory authority.
13424 - When we're configured to be a v3 authority, but we're only listed
13425 as a non-v3 authority in our DirServer line for ourself, correct
13427 - If an authority doesn't have a qualified hostname, just put
13428 its address in the vote. This fixes the problem where we referred to
13429 "moria on moria:9031."
13430 - Distinguish between detached signatures for the wrong period, and
13431 detached signatures for a divergent vote.
13432 - Fix a small memory leak when computing a consensus.
13433 - When there's no concensus, we were forming a vote every 30
13434 minutes, but writing the "valid-after" line in our vote based
13435 on our configured V3AuthVotingInterval: so unless the intervals
13436 matched up, we immediately rejected our own vote because it didn't
13437 start at the voting interval that caused us to construct a vote.
13439 o Minor bugfixes (v3 directory protocol, bugfixes on 0.2.0.x):
13440 - Delete unverified-consensus when the real consensus is set.
13441 - Consider retrying a consensus networkstatus fetch immediately
13442 after one fails: don't wait 60 seconds to notice.
13443 - When fetching a consensus as a cache, wait until a newer consensus
13444 should exist before trying to replace the current one.
13445 - Use a more forgiving schedule for retrying failed consensus
13446 downloads than for other types.
13448 o Minor bugfixes (other directory issues):
13449 - Correct the implementation of "download votes by digest." Bugfix on
13451 - Authorities no longer send back "400 you're unreachable please fix
13452 it" errors to Tor servers that aren't online all the time. We're
13453 supposed to tolerate these servers now. Bugfix on 0.1.2.x.
13455 o Minor bugfixes (controller):
13456 - Don't reset trusted dir server list when we set a configuration
13457 option. Patch from Robert Hogan; bugfix on 0.1.2.x.
13458 - Respond to INT and TERM SIGNAL commands before we execute the
13459 signal, in case the signal shuts us down. We had a patch in
13460 0.1.2.1-alpha that tried to do this by queueing the response on
13461 the connection's buffer before shutting down, but that really
13462 isn't the same thing at all. Bug located by Matt Edman.
13464 o Minor bugfixes (misc):
13465 - Correctly check for bad options to the "PublishServerDescriptor"
13466 config option. Bugfix on 0.2.0.1-alpha; reported by Matt Edman.
13467 - Stop leaking memory on failing case of base32_decode, and make
13468 it accept upper-case letters. Bugfixes on 0.2.0.7-alpha.
13469 - Don't try to download extrainfo documents when we're trying to
13470 fetch enough directory info to build a circuit: having enough
13471 info should get priority. Bugfix on 0.2.0.x.
13472 - Don't complain that "your server has not managed to confirm that its
13473 ports are reachable" if we haven't been able to build any circuits
13474 yet. Bug found by spending four hours without a v3 consensus. Bugfix
13476 - Detect the reason for failing to mmap a descriptor file we just
13477 wrote, and give a more useful log message. Fixes bug 533. Bugfix
13480 o Code simplifications and refactoring:
13481 - Remove support for the old bw_accounting file: we've been storing
13482 bandwidth accounting information in the state file since
13483 0.1.2.5-alpha. This may result in bandwidth accounting errors
13484 if you try to upgrade from 0.1.1.x or earlier, or if you try to
13485 downgrade to 0.1.1.x or earlier.
13486 - New convenience code to locate a file within the DataDirectory.
13487 - Move non-authority functionality out of dirvote.c.
13488 - Refactor the arguments for router_pick_{directory_|trusteddir}server
13489 so that they all take the same named flags.
13492 - Include the "tor-ctrl.sh" bash script by Stefan Behte to provide
13493 Unix users an easy way to script their Tor process (e.g. by
13494 adjusting bandwidth based on the time of the day).
13497 Changes in version 0.2.0.8-alpha - 2007-10-12
13498 This eighth development snapshot fixes a crash bug that's been bothering
13499 us since February 2007, lets bridge authorities store a list of bridge
13500 descriptors they've seen, gets v3 directory voting closer to working,
13501 starts caching v3 directory consensus documents on directory mirrors,
13502 and fixes a variety of smaller issues including some minor memory leaks.
13504 o Major features (router descriptor cache):
13505 - Store routers in a file called cached-descriptors instead of in
13506 cached-routers. Initialize cached-descriptors from cached-routers
13507 if the old format is around. The new format allows us to store
13508 annotations along with descriptors.
13509 - Use annotations to record the time we received each descriptor, its
13510 source, and its purpose.
13511 - Disable the SETROUTERPURPOSE controller command: it is now
13513 - Controllers should now specify cache=no or cache=yes when using
13514 the +POSTDESCRIPTOR command.
13515 - Bridge authorities now write bridge descriptors to disk, meaning
13516 we can export them to other programs and begin distributing them
13519 o Major features (directory authorities):
13520 - When a v3 authority is missing votes or signatures, it now tries
13522 - Directory authorities track weighted fractional uptime as well as
13523 weighted mean-time-between failures. WFU is suitable for deciding
13524 whether a node is "usually up", while MTBF is suitable for deciding
13525 whether a node is "likely to stay up." We need both, because
13526 "usually up" is a good requirement for guards, while "likely to
13527 stay up" is a good requirement for long-lived connections.
13529 o Major features (v3 directory system):
13530 - Caches now download v3 network status documents as needed,
13531 and download the descriptors listed in them.
13532 - All hosts now attempt to download and keep fresh v3 authority
13533 certificates, and re-attempt after failures.
13534 - More internal-consistency checks for vote parsing.
13536 o Major bugfixes (crashes):
13537 - If a connection is shut down abruptly because of something that
13538 happened inside connection_flushed_some(), do not call
13539 connection_finished_flushing(). Should fix bug 451. Bugfix on
13542 o Major bugfixes (performance):
13543 - Fix really bad O(n^2) performance when parsing a long list of
13544 routers: Instead of searching the entire list for an "extra-info "
13545 string which usually wasn't there, once for every routerinfo
13546 we read, just scan lines forward until we find one we like.
13548 - When we add data to a write buffer in response to the data on that
13549 write buffer getting low because of a flush, do not consider the
13550 newly added data as a candidate for immediate flushing, but rather
13551 make it wait until the next round of writing. Otherwise, we flush
13552 and refill recursively, and a single greedy TLS connection can
13553 eat all of our bandwidth. Bugfix on 0.1.2.7-alpha.
13555 o Minor features (v3 authority system):
13556 - Add more ways for tools to download the votes that lead to the
13558 - Send a 503 when low on bandwidth and a vote, consensus, or
13559 certificate is requested.
13560 - If-modified-since is now implemented properly for all kinds of
13561 certificate requests.
13563 o Minor bugfixes (network statuses):
13564 - Tweak the implementation of proposal 109 slightly: allow at most
13565 two Tor servers on the same IP address, except if it's the location
13566 of a directory authority, in which case allow five. Bugfix on
13569 o Minor bugfixes (controller):
13570 - When sending a status event to the controller telling it that an
13571 OR address is reachable, set the port correctly. (Previously we
13572 were reporting the dir port.) Bugfix on 0.1.2.x.
13574 o Minor bugfixes (v3 directory system):
13575 - Fix logic to look up a cert by its signing key digest. Bugfix on
13577 - Only change the reply to a vote to "OK" if it's not already
13578 set. This gets rid of annoying "400 OK" log messages, which may
13579 have been masking some deeper issue. Bugfix on 0.2.0.7-alpha.
13580 - When we get a valid consensus, recompute the voting schedule.
13581 - Base the valid-after time of a vote on the consensus voting
13582 schedule, not on our preferred schedule.
13583 - Make the return values and messages from signature uploads and
13584 downloads more sensible.
13585 - Fix a memory leak when serving votes and consensus documents, and
13586 another when serving certificates.
13588 o Minor bugfixes (performance):
13589 - Use a slightly simpler string hashing algorithm (copying Python's
13590 instead of Java's) and optimize our digest hashing algorithm to take
13591 advantage of 64-bit platforms and to remove some possibly-costly
13593 - Fix a minor memory leak whenever we parse guards from our state
13594 file. Bugfix on 0.2.0.7-alpha.
13595 - Fix a minor memory leak whenever we write out a file. Bugfix on
13597 - Fix a minor memory leak whenever a controller sends the PROTOCOLINFO
13598 command. Bugfix on 0.2.0.5-alpha.
13600 o Minor bugfixes (portability):
13601 - On some platforms, accept() can return a broken address. Detect
13602 this more quietly, and deal accordingly. Fixes bug 483.
13603 - Stop calling tor_strlower() on uninitialized memory in some cases.
13604 Bugfix in 0.2.0.7-alpha.
13606 o Minor bugfixes (usability):
13607 - Treat some 403 responses from directory servers as INFO rather than
13608 WARN-severity events.
13609 - It's not actually an error to find a non-pending entry in the DNS
13610 cache when canceling a pending resolve. Don't log unless stuff is
13611 fishy. Resolves bug 463.
13613 o Minor bugfixes (anonymity):
13614 - Never report that we've used more bandwidth than we're willing to
13615 relay: it leaks how much non-relay traffic we're using. Resolves
13617 - When looking for a circuit to cannibalize, consider family as well
13618 as identity. Fixes bug 438. Bugfix on 0.1.0.x (which introduced
13619 circuit cannibalization).
13621 o Code simplifications and refactoring:
13622 - Make a bunch of functions static. Remove some dead code.
13623 - Pull out about a third of the really big routerlist.c; put it in a
13624 new module, networkstatus.c.
13625 - Merge the extra fields in local_routerstatus_t back into
13626 routerstatus_t: we used to need one routerstatus_t for each
13627 authority's opinion, plus a local_routerstatus_t for the locally
13628 computed consensus opinion. To save space, we put the locally
13629 modified fields into local_routerstatus_t, and only the common
13630 stuff into routerstatus_t. But once v3 directories are in use,
13631 clients and caches will no longer need to hold authority opinions;
13632 thus, the rationale for keeping the types separate is now gone.
13633 - Make the code used to reschedule and reattempt downloads more
13635 - Turn all 'Are we a directory server/mirror?' logic into a call to
13637 - Remove the code to generate the oldest (v1) directory format.
13638 The code has been disabled since 0.2.0.5-alpha.
13641 Changes in version 0.2.0.7-alpha - 2007-09-21
13642 This seventh development snapshot makes bridges work again, makes bridge
13643 authorities work for the first time, fixes two huge performance flaws
13644 in hidden services, and fixes a variety of minor issues.
13646 o New directory authorities:
13647 - Set up moria1 and tor26 as the first v3 directory authorities. See
13648 doc/spec/dir-spec.txt for details on the new directory design.
13650 o Major bugfixes (crashes):
13651 - Fix possible segfaults in functions called from
13652 rend_process_relay_cell(). Bugfix on 0.1.2.x.
13654 o Major bugfixes (bridges):
13655 - Fix a bug that made servers send a "404 Not found" in response to
13656 attempts to fetch their server descriptor. This caused Tor servers
13657 to take many minutes to establish reachability for their DirPort,
13658 and it totally crippled bridges. Bugfix on 0.2.0.5-alpha.
13659 - Make "UpdateBridgesFromAuthority" torrc option work: when bridge
13660 users configure that and specify a bridge with an identity
13661 fingerprint, now they will lookup the bridge descriptor at the
13662 default bridge authority via a one-hop tunnel, but once circuits
13663 are established they will switch to a three-hop tunnel for later
13664 connections to the bridge authority. Bugfix in 0.2.0.3-alpha.
13666 o Major bugfixes (hidden services):
13667 - Hidden services were choosing introduction points uniquely by
13668 hexdigest, but when constructing the hidden service descriptor
13669 they merely wrote the (potentially ambiguous) nickname.
13670 - Clients now use the v2 intro format for hidden service
13671 connections: they specify their chosen rendezvous point by identity
13672 digest rather than by (potentially ambiguous) nickname. Both
13673 are bugfixes on 0.1.2.x, and they could speed up hidden service
13674 connections dramatically. Thanks to Karsten Loesing.
13676 o Minor features (security):
13677 - As a client, do not believe any server that tells us that an
13678 address maps to an internal address space.
13679 - Make it possible to enable HashedControlPassword and
13680 CookieAuthentication at the same time.
13682 o Minor features (guard nodes):
13683 - Tag every guard node in our state file with the version that
13684 we believe added it, or with our own version if we add it. This way,
13685 if a user temporarily runs an old version of Tor and then switches
13686 back to a new one, she doesn't automatically lose her guards.
13688 o Minor features (speed):
13689 - When implementing AES counter mode, update only the portions of the
13690 counter buffer that need to change, and don't keep separate
13691 network-order and host-order counters when they are the same (i.e.,
13692 on big-endian hosts.)
13694 o Minor features (controller):
13695 - Accept LF instead of CRLF on controller, since some software has a
13696 hard time generating real Internet newlines.
13697 - Add GETINFO values for the server status events
13698 "REACHABILITY_SUCCEEDED" and "GOOD_SERVER_DESCRIPTOR". Patch from
13701 o Removed features:
13702 - Routers no longer include bandwidth-history lines in their
13703 descriptors; this information is already available in extra-info
13704 documents, and including it in router descriptors took up 60%
13705 (!) of compressed router descriptor downloads. Completes
13706 implementation of proposal 104.
13707 - Remove the contrib scripts ExerciseServer.py, PathDemo.py,
13708 and TorControl.py, as they use the old v0 controller protocol,
13709 and are obsoleted by TorFlow anyway.
13710 - Drop support for v1 rendezvous descriptors, since we never used
13711 them anyway, and the code has probably rotted by now. Based on
13712 patch from Karsten Loesing.
13713 - On OSX, stop warning the user that kqueue support in libevent is
13714 "experimental", since it seems to have worked fine for ages.
13717 - When generating information telling us how to extend to a given
13718 router, do not try to include the nickname if it is absent. Fixes
13719 bug 467. Bugfix on 0.2.0.3-alpha.
13720 - Fix a user-triggerable (but not remotely-triggerable) segfault
13721 in expand_filename(). Bugfix on 0.1.2.x.
13722 - Fix a memory leak when freeing incomplete requests from DNSPort.
13723 Found by Niels Provos with valgrind. Bugfix on 0.2.0.1-alpha.
13724 - Don't try to access (or alter) the state file when running
13725 --list-fingerprint or --verify-config or --hash-password. (Resolves
13726 bug 499.) Bugfix on 0.1.2.x.
13727 - Servers used to decline to publish their DirPort if their
13728 BandwidthRate, RelayBandwidthRate, or MaxAdvertisedBandwidth
13729 were below a threshold. Now they only look at BandwidthRate and
13730 RelayBandwidthRate. Bugfix on 0.1.2.x.
13731 - Remove an optimization in the AES counter-mode code that assumed
13732 that the counter never exceeded 2^68. When the counter can be set
13733 arbitrarily as an IV (as it is by Karsten's new hidden services
13734 code), this assumption no longer holds. Bugfix on 0.1.2.x.
13735 - Resume listing "AUTHORITY" flag for authorities in network status.
13736 Bugfix on 0.2.0.3-alpha; reported by Alex de Joode.
13738 o Code simplifications and refactoring:
13739 - Revamp file-writing logic so we don't need to have the entire
13740 contents of a file in memory at once before we write to disk. Tor,
13742 - Turn "descriptor store" into a full-fledged type.
13743 - Move all NT services code into a separate source file.
13744 - Unify all code that computes medians, percentile elements, etc.
13745 - Get rid of a needless malloc when parsing address policies.
13748 Changes in version 0.1.2.17 - 2007-08-30
13749 Tor 0.1.2.17 features a new Vidalia version in the Windows and OS
13750 X bundles. Vidalia 0.0.14 makes authentication required for the
13751 ControlPort in the default configuration, which addresses important
13752 security risks. Everybody who uses Vidalia (or another controller)
13755 In addition, this Tor update fixes major load balancing problems with
13756 path selection, which should speed things up a lot once many people
13759 o Major bugfixes (security):
13760 - We removed support for the old (v0) control protocol. It has been
13761 deprecated since Tor 0.1.1.1-alpha, and keeping it secure has
13762 become more of a headache than it's worth.
13764 o Major bugfixes (load balancing):
13765 - When choosing nodes for non-guard positions, weight guards
13766 proportionally less, since they already have enough load. Patch
13768 - Raise the "max believable bandwidth" from 1.5MB/s to 10MB/s. This
13769 will allow fast Tor servers to get more attention.
13770 - When we're upgrading from an old Tor version, forget our current
13771 guards and pick new ones according to the new weightings. These
13772 three load balancing patches could raise effective network capacity
13773 by a factor of four. Thanks to Mike Perry for measurements.
13775 o Major bugfixes (stream expiration):
13776 - Expire not-yet-successful application streams in all cases if
13777 they've been around longer than SocksTimeout. Right now there are
13778 some cases where the stream will live forever, demanding a new
13779 circuit every 15 seconds. Fixes bug 454; reported by lodger.
13781 o Minor features (controller):
13782 - Add a PROTOCOLINFO controller command. Like AUTHENTICATE, it
13783 is valid before any authentication has been received. It tells
13784 a controller what kind of authentication is expected, and what
13785 protocol is spoken. Implements proposal 119.
13787 o Minor bugfixes (performance):
13788 - Save on most routerlist_assert_ok() calls in routerlist.c, thus
13789 greatly speeding up loading cached-routers from disk on startup.
13790 - Disable sentinel-based debugging for buffer code: we squashed all
13791 the bugs that this was supposed to detect a long time ago, and now
13792 its only effect is to change our buffer sizes from nice powers of
13793 two (which platform mallocs tend to like) to values slightly over
13794 powers of two (which make some platform mallocs sad).
13796 o Minor bugfixes (misc):
13797 - If exit bandwidth ever exceeds one third of total bandwidth, then
13798 use the correct formula to weight exit nodes when choosing paths.
13799 Based on patch from Mike Perry.
13800 - Choose perfectly fairly among routers when choosing by bandwidth and
13801 weighting by fraction of bandwidth provided by exits. Previously, we
13802 would choose with only approximate fairness, and correct ourselves
13803 if we ran off the end of the list.
13804 - If we require CookieAuthentication but we fail to write the
13805 cookie file, we would warn but not exit, and end up in a state
13806 where no controller could authenticate. Now we exit.
13807 - If we require CookieAuthentication, stop generating a new cookie
13808 every time we change any piece of our config.
13809 - Refuse to start with certain directory authority keys, and
13810 encourage people using them to stop.
13811 - Terminate multi-line control events properly. Original patch
13813 - Fix a minor memory leak when we fail to find enough suitable
13814 servers to choose a circuit.
13815 - Stop leaking part of the descriptor when we run into a particularly
13816 unparseable piece of it.
13819 Changes in version 0.2.0.6-alpha - 2007-08-26
13820 This sixth development snapshot features a new Vidalia version in the
13821 Windows and OS X bundles. Vidalia 0.0.14 makes authentication required for
13822 the ControlPort in the default configuration, which addresses important
13825 In addition, this snapshot fixes major load balancing problems
13826 with path selection, which should speed things up a lot once many
13827 people have upgraded. The directory authorities also use a new
13828 mean-time-between-failure approach to tracking which servers are stable,
13829 rather than just looking at the most recent uptime.
13831 o New directory authorities:
13832 - Set up Tonga as the default bridge directory authority.
13835 - Directory authorities now track servers by weighted
13836 mean-times-between-failures. When we have 4 or more days of data,
13837 use measured MTBF rather than declared uptime to decide whether
13838 to call a router Stable. Implements proposal 108.
13840 o Major bugfixes (load balancing):
13841 - When choosing nodes for non-guard positions, weight guards
13842 proportionally less, since they already have enough load. Patch
13844 - Raise the "max believable bandwidth" from 1.5MB/s to 10MB/s. This
13845 will allow fast Tor servers to get more attention.
13846 - When we're upgrading from an old Tor version, forget our current
13847 guards and pick new ones according to the new weightings. These
13848 three load balancing patches could raise effective network capacity
13849 by a factor of four. Thanks to Mike Perry for measurements.
13851 o Major bugfixes (descriptor parsing):
13852 - Handle unexpected whitespace better in malformed descriptors. Bug
13853 found using Benedikt Boss's new Tor fuzzer! Bugfix on 0.2.0.x.
13856 - There is now an ugly, temporary "desc/all-recent-extrainfo-hack"
13857 GETINFO for Torstat to use until it can switch to using extrainfos.
13858 - Optionally (if built with -DEXPORTMALLINFO) export the output
13859 of mallinfo via http, as tor/mallinfo.txt. Only accessible
13863 - Do not intermix bridge routers with controller-added
13864 routers. (Bugfix on 0.2.0.x)
13865 - Do not fail with an assert when accept() returns an unexpected
13866 address family. Addresses but does not wholly fix bug 483. (Bugfix
13868 - Let directory authorities startup even when they can't generate
13869 a descriptor immediately, e.g. because they don't know their
13871 - Stop putting the authentication cookie in a file called "0"
13872 in your working directory if you don't specify anything for the
13873 new CookieAuthFile option. Reported by Matt Edman.
13874 - Make it possible to read the PROTOCOLINFO response in a way that
13875 conforms to our control-spec. Reported by Matt Edman.
13876 - Fix a minor memory leak when we fail to find enough suitable
13877 servers to choose a circuit. Bugfix on 0.1.2.x.
13878 - Stop leaking part of the descriptor when we run into a particularly
13879 unparseable piece of it. Bugfix on 0.1.2.x.
13880 - Unmap the extrainfo cache file on exit.
13883 Changes in version 0.2.0.5-alpha - 2007-08-19
13884 This fifth development snapshot fixes compilation on Windows again;
13885 fixes an obnoxious client-side bug that slowed things down and put
13886 extra load on the network; gets us closer to using the v3 directory
13887 voting scheme; makes it easier for Tor controllers to use cookie-based
13888 authentication; and fixes a variety of other bugs.
13890 o Removed features:
13891 - Version 1 directories are no longer generated in full. Instead,
13892 authorities generate and serve "stub" v1 directories that list
13893 no servers. This will stop Tor versions 0.1.0.x and earlier from
13894 working, but (for security reasons) nobody should be running those
13897 o Major bugfixes (compilation, 0.2.0.x):
13898 - Try to fix Win32 compilation again: improve checking for IPv6 types.
13899 - Try to fix MSVC compilation: build correctly on platforms that do
13900 not define s6_addr16 or s6_addr32.
13901 - Fix compile on platforms without getaddrinfo: bug found by Li-Hui
13904 o Major bugfixes (stream expiration):
13905 - Expire not-yet-successful application streams in all cases if
13906 they've been around longer than SocksTimeout. Right now there are
13907 some cases where the stream will live forever, demanding a new
13908 circuit every 15 seconds. Bugfix on 0.1.2.7-alpha; fixes bug 454;
13909 reported by lodger.
13911 o Minor features (directory servers):
13912 - When somebody requests a list of statuses or servers, and we have
13913 none of those, return a 404 rather than an empty 200.
13915 o Minor features (directory voting):
13916 - Store v3 consensus status consensuses on disk, and reload them
13919 o Minor features (security):
13920 - Warn about unsafe ControlPort configurations.
13921 - Refuse to start with certain directory authority keys, and
13922 encourage people using them to stop.
13924 o Minor features (controller):
13925 - Add a PROTOCOLINFO controller command. Like AUTHENTICATE, it
13926 is valid before any authentication has been received. It tells
13927 a controller what kind of authentication is expected, and what
13928 protocol is spoken. Implements proposal 119.
13929 - New config option CookieAuthFile to choose a new location for the
13930 cookie authentication file, and config option
13931 CookieAuthFileGroupReadable to make it group-readable.
13933 o Minor features (unit testing):
13934 - Add command-line arguments to unit-test executable so that we can
13935 invoke any chosen test from the command line rather than having
13936 to run the whole test suite at once; and so that we can turn on
13937 logging for the unit tests.
13939 o Minor bugfixes (on 0.1.2.x):
13940 - If we require CookieAuthentication but we fail to write the
13941 cookie file, we would warn but not exit, and end up in a state
13942 where no controller could authenticate. Now we exit.
13943 - If we require CookieAuthentication, stop generating a new cookie
13944 every time we change any piece of our config.
13945 - When loading bandwidth history, do not believe any information in
13946 the future. Fixes bug 434.
13947 - When loading entry guard information, do not believe any information
13949 - When we have our clock set far in the future and generate an
13950 onion key, then re-set our clock to be correct, we should not stop
13951 the onion key from getting rotated.
13952 - Clean up torrc sample config file.
13953 - Do not automatically run configure from autogen.sh. This
13954 non-standard behavior tended to annoy people who have built other
13957 o Minor bugfixes (on 0.2.0.x):
13958 - Fix a bug with AutomapHostsOnResolve that would always cause
13959 the second request to fail. Bug reported by Kate. Bugfix on
13961 - Fix a bug in ADDRMAP controller replies that would sometimes
13962 try to print a NULL. Patch from tup.
13963 - Read v3 directory authority keys from the right location.
13964 - Numerous bugfixes to directory voting code.
13967 Changes in version 0.1.2.16 - 2007-08-01
13968 Tor 0.1.2.16 fixes a critical security vulnerability that allows a
13969 remote attacker in certain situations to rewrite the user's torrc
13970 configuration file. This can completely compromise anonymity of users
13971 in most configurations, including those running the Vidalia bundles,
13972 TorK, etc. Or worse.
13974 o Major security fixes:
13975 - Close immediately after missing authentication on control port;
13976 do not allow multiple authentication attempts.
13979 Changes in version 0.2.0.4-alpha - 2007-08-01
13980 This fourth development snapshot fixes a critical security vulnerability
13981 for most users, specifically those running Vidalia, TorK, etc. Everybody
13982 should upgrade to either 0.1.2.16 or 0.2.0.4-alpha.
13984 o Major security fixes:
13985 - Close immediately after missing authentication on control port;
13986 do not allow multiple authentication attempts.
13988 o Major bugfixes (compilation):
13989 - Fix win32 compilation: apparently IN_ADDR and IN6_ADDR are already
13992 o Minor features (performance):
13993 - Be even more aggressive about releasing RAM from small
13994 empty buffers. Thanks to our free-list code, this shouldn't be too
13995 performance-intensive.
13996 - Disable sentinel-based debugging for buffer code: we squashed all
13997 the bugs that this was supposed to detect a long time ago, and
13998 now its only effect is to change our buffer sizes from nice
13999 powers of two (which platform mallocs tend to like) to values
14000 slightly over powers of two (which make some platform mallocs sad).
14001 - Log malloc statistics from mallinfo() on platforms where it
14005 Changes in version 0.2.0.3-alpha - 2007-07-29
14006 This third development snapshot introduces new experimental
14007 blocking-resistance features and a preliminary version of the v3
14008 directory voting design, and includes many other smaller features
14012 - The first pieces of our "bridge" design for blocking-resistance
14013 are implemented. People can run bridge directory authorities;
14014 people can run bridges; and people can configure their Tor clients
14015 with a set of bridges to use as the first hop into the Tor network.
14016 See http://archives.seul.org/or/talk/Jul-2007/msg00249.html for
14018 - Create listener connections before we setuid to the configured
14019 User and Group. Now non-Windows users can choose port values
14020 under 1024, start Tor as root, and have Tor bind those ports
14021 before it changes to another UID. (Windows users could already
14023 - Added a new ConstrainedSockets config option to set SO_SNDBUF and
14024 SO_RCVBUF on TCP sockets. Hopefully useful for Tor servers running
14025 on "vserver" accounts. (Patch from coderman.)
14026 - Be even more aggressive about separating local traffic from relayed
14027 traffic when RelayBandwidthRate is set. (Refines proposal 111.)
14029 o Major features (experimental):
14030 - First cut of code for "v3 dir voting": directory authorities will
14031 vote on a common network status document rather than each publishing
14032 their own opinion. This code needs more testing and more corner-case
14033 handling before it's ready for use.
14036 - Directory authorities now call routers Fast if their bandwidth is
14037 at least 100KB/s, and consider their bandwidth adequate to be a
14038 Guard if it is at least 250KB/s, no matter the medians. This fix
14039 complements proposal 107. [Bugfix on 0.1.2.x]
14040 - Directory authorities now never mark more than 3 servers per IP as
14041 Valid and Running. (Implements proposal 109, by Kevin Bauer and
14043 - Minor change to organizationName and commonName generation
14044 procedures in TLS certificates during Tor handshakes, to invalidate
14045 some earlier censorware approaches. This is not a long-term
14046 solution, but applying it will give us a bit of time to look into
14047 the epidemiology of countermeasures as they spread.
14049 o Major bugfixes (directory):
14050 - Rewrite directory tokenization code to never run off the end of
14051 a string. Fixes bug 455. Patch from croup. [Bugfix on 0.1.2.x]
14053 o Minor features (controller):
14054 - Add a SOURCE_ADDR field to STREAM NEW events so that controllers can
14055 match requests to applications. (Patch from Robert Hogan.)
14056 - Report address and port correctly on connections to DNSPort. (Patch
14057 from Robert Hogan.)
14058 - Add a RESOLVE command to launch hostname lookups. (Original patch
14059 from Robert Hogan.)
14060 - Add GETINFO status/enough-dir-info to let controllers tell whether
14061 Tor has downloaded sufficient directory information. (Patch
14063 - You can now use the ControlSocket option to tell Tor to listen for
14064 controller connections on Unix domain sockets on systems that
14065 support them. (Patch from Peter Palfrader.)
14066 - STREAM NEW events are generated for DNSPort requests and for
14067 tunneled directory connections. (Patch from Robert Hogan.)
14068 - New "GETINFO address-mappings/*" command to get address mappings
14069 with expiry information. "addr-mappings/*" is now deprecated.
14072 o Minor features (misc):
14073 - Merge in some (as-yet-unused) IPv6 address manipulation code. (Patch
14075 - The tor-gencert tool for v3 directory authorities now creates all
14076 files as readable to the file creator only, and write-protects
14077 the authority identity key.
14078 - When dumping memory usage, list bytes used in buffer memory
14080 - When running with dmalloc, dump more stats on hup and on exit.
14081 - Directory authorities now fail quickly and (relatively) harmlessly
14082 if they generate a network status document that is somehow
14085 o Traffic load balancing improvements:
14086 - If exit bandwidth ever exceeds one third of total bandwidth, then
14087 use the correct formula to weight exit nodes when choosing paths.
14088 (Based on patch from Mike Perry.)
14089 - Choose perfectly fairly among routers when choosing by bandwidth and
14090 weighting by fraction of bandwidth provided by exits. Previously, we
14091 would choose with only approximate fairness, and correct ourselves
14092 if we ran off the end of the list. [Bugfix on 0.1.2.x]
14094 o Performance improvements:
14095 - Be more aggressive with freeing buffer RAM or putting it on the
14097 - Use Critical Sections rather than Mutexes for synchronizing threads
14098 on win32; Mutexes are heavier-weight, and designed for synchronizing
14101 o Deprecated and removed features:
14102 - RedirectExits is now deprecated.
14103 - Stop allowing address masks that do not correspond to bit prefixes.
14104 We have warned about these for a really long time; now it's time
14105 to reject them. (Patch from croup.)
14107 o Minor bugfixes (directory):
14108 - Fix another crash bug related to extra-info caching. (Bug found by
14109 Peter Palfrader.) [Bugfix on 0.2.0.2-alpha]
14110 - Directories no longer return a "304 not modified" when they don't
14111 have the networkstatus the client asked for. Also fix a memory
14112 leak when returning 304 not modified. [Bugfixes on 0.2.0.2-alpha]
14113 - We had accidentally labelled 0.1.2.x directory servers as not
14114 suitable for begin_dir requests, and had labelled no directory
14115 servers as suitable for uploading extra-info documents. [Bugfix
14118 o Minor bugfixes (dns):
14119 - Fix a crash when DNSPort is set more than once. (Patch from Robert
14120 Hogan.) [Bugfix on 0.2.0.2-alpha]
14121 - Add DNSPort connections to the global connection list, so that we
14122 can time them out correctly. (Bug found by Robert Hogan.) [Bugfix
14124 - Fix a dangling reference that could lead to a crash when DNSPort is
14125 changed or closed (Patch from Robert Hogan.) [Bugfix on
14128 o Minor bugfixes (controller):
14129 - Provide DNS expiry times in GMT, not in local time. For backward
14130 compatibility, ADDRMAP events only provide GMT expiry in an extended
14131 field. "GETINFO address-mappings" always does the right thing.
14132 - Use CRLF line endings properly in NS events.
14133 - Terminate multi-line control events properly. (Original patch
14134 from tup.) [Bugfix on 0.1.2.x-alpha]
14135 - Do not include spaces in SOURCE_ADDR fields in STREAM
14136 events. Resolves bug 472. [Bugfix on 0.2.0.x-alpha]
14139 Changes in version 0.1.2.15 - 2007-07-17
14140 Tor 0.1.2.15 fixes several crash bugs, fixes some anonymity-related
14141 problems, fixes compilation on BSD, and fixes a variety of other
14142 bugs. Everybody should upgrade.
14144 o Major bugfixes (compilation):
14145 - Fix compile on FreeBSD/NetBSD/OpenBSD. Oops.
14147 o Major bugfixes (crashes):
14148 - Try even harder not to dereference the first character after
14149 an mmap(). Reported by lodger.
14150 - Fix a crash bug in directory authorities when we re-number the
14151 routerlist while inserting a new router.
14152 - When the cached-routers file is an even multiple of the page size,
14153 don't run off the end and crash. (Fixes bug 455; based on idea
14155 - Fix eventdns.c behavior on Solaris: It is critical to include
14156 orconfig.h _before_ sys/types.h, so that we can get the expected
14157 definition of _FILE_OFFSET_BITS.
14159 o Major bugfixes (security):
14160 - Fix a possible buffer overrun when using BSD natd support. Bug
14162 - When sending destroy cells from a circuit's origin, don't include
14163 the reason for tearing down the circuit. The spec says we didn't,
14164 and now we actually don't. Reported by lodger.
14165 - Keep streamids from different exits on a circuit separate. This
14166 bug may have allowed other routers on a given circuit to inject
14167 cells into streams. Reported by lodger; fixes bug 446.
14168 - If there's a never-before-connected-to guard node in our list,
14169 never choose any guards past it. This way we don't expand our
14170 guard list unless we need to.
14172 o Minor bugfixes (guard nodes):
14173 - Weight guard selection by bandwidth, so that low-bandwidth nodes
14174 don't get overused as guards.
14176 o Minor bugfixes (directory):
14177 - Correctly count the number of authorities that recommend each
14178 version. Previously, we were under-counting by 1.
14179 - Fix a potential crash bug when we load many server descriptors at
14180 once and some of them make others of them obsolete. Fixes bug 458.
14182 o Minor bugfixes (hidden services):
14183 - Stop tearing down the whole circuit when the user asks for a
14184 connection to a port that the hidden service didn't configure.
14187 o Minor bugfixes (misc):
14188 - On Windows, we were preventing other processes from reading
14189 cached-routers while Tor was running. Reported by janbar.
14190 - Fix a possible (but very unlikely) bug in picking routers by
14191 bandwidth. Add a log message to confirm that it is in fact
14192 unlikely. Patch from lodger.
14193 - Backport a couple of memory leak fixes.
14194 - Backport miscellaneous cosmetic bugfixes.
14197 Changes in version 0.2.0.2-alpha - 2007-06-02
14198 o Major bugfixes on 0.2.0.1-alpha:
14199 - Fix an assertion failure related to servers without extra-info digests.
14200 Resolves bugs 441 and 442.
14202 o Minor features (directory):
14203 - Support "If-Modified-Since" when answering HTTP requests for
14204 directories, running-routers documents, and network-status documents.
14205 (There's no need to support it for router descriptors, since those
14206 are downloaded by descriptor digest.)
14208 o Minor build issues:
14209 - Clear up some MIPSPro compiler warnings.
14210 - When building from a tarball on a machine that happens to have SVK
14211 installed, report the micro-revision as whatever version existed
14212 in the tarball, not as "x".
14215 Changes in version 0.2.0.1-alpha - 2007-06-01
14216 This early development snapshot provides new features for people running
14217 Tor as both a client and a server (check out the new RelayBandwidth
14218 config options); lets Tor run as a DNS proxy; and generally moves us
14219 forward on a lot of fronts.
14221 o Major features, server usability:
14222 - New config options RelayBandwidthRate and RelayBandwidthBurst:
14223 a separate set of token buckets for relayed traffic. Right now
14224 relayed traffic is defined as answers to directory requests, and
14225 OR connections that don't have any local circuits on them.
14227 o Major features, client usability:
14228 - A client-side DNS proxy feature to replace the need for
14229 dns-proxy-tor: Just set "DNSPort 9999", and Tor will now listen
14230 for DNS requests on port 9999, use the Tor network to resolve them
14231 anonymously, and send the reply back like a regular DNS server.
14232 The code still only implements a subset of DNS.
14233 - Make PreferTunneledDirConns and TunnelDirConns work even when
14234 we have no cached directory info. This means Tor clients can now
14235 do all of their connections protected by TLS.
14237 o Major features, performance and efficiency:
14238 - Directory authorities accept and serve "extra info" documents for
14239 routers. These documents contain fields from router descriptors
14240 that aren't usually needed, and that use a lot of excess
14241 bandwidth. Once these fields are removed from router descriptors,
14242 the bandwidth savings should be about 60%. [Partially implements
14244 - Servers upload extra-info documents to any authority that accepts
14245 them. Authorities (and caches that have been configured to download
14246 extra-info documents) download them as needed. [Partially implements
14248 - Change the way that Tor buffers data that it is waiting to write.
14249 Instead of queueing data cells in an enormous ring buffer for each
14250 client->OR or OR->OR connection, we now queue cells on a separate
14251 queue for each circuit. This lets us use less slack memory, and
14252 will eventually let us be smarter about prioritizing different kinds
14254 - Use memory pools to allocate cells with better speed and memory
14255 efficiency, especially on platforms where malloc() is inefficient.
14256 - Stop reading on edge connections when their corresponding circuit
14257 buffers are full; start again as the circuits empty out.
14259 o Major features, other:
14260 - Add an HSAuthorityRecordStats option that hidden service authorities
14261 can use to track statistics of overall hidden service usage without
14262 logging information that would be very useful to an attacker.
14263 - Start work implementing multi-level keys for directory authorities:
14264 Add a standalone tool to generate key certificates. (Proposal 103.)
14267 - Directory authorities now call routers Stable if they have an
14268 uptime of at least 30 days, even if that's not the median uptime
14269 in the network. Implements proposal 107, suggested by Kevin Bauer
14272 o Minor fixes (resource management):
14273 - Count the number of open sockets separately from the number
14274 of active connection_t objects. This will let us avoid underusing
14275 our allocated connection limit.
14276 - We no longer use socket pairs to link an edge connection to an
14277 anonymous directory connection or a DirPort test connection.
14278 Instead, we track the link internally and transfer the data
14279 in-process. This saves two sockets per "linked" connection (at the
14280 client and at the server), and avoids the nasty Windows socketpair()
14282 - Keep unused 4k and 16k buffers on free lists, rather than wasting 8k
14283 for every single inactive connection_t. Free items from the
14284 4k/16k-buffer free lists when they haven't been used for a while.
14286 o Minor features (build):
14287 - Make autoconf search for libevent, openssl, and zlib consistently.
14288 - Update deprecated macros in configure.in.
14289 - When warning about missing headers, tell the user to let us
14290 know if the compile succeeds anyway, so we can downgrade the
14292 - Include the current subversion revision as part of the version
14293 string: either fetch it directly if we're in an SVN checkout, do
14294 some magic to guess it if we're in an SVK checkout, or use
14295 the last-detected version if we're building from a .tar.gz.
14296 Use this version consistently in log messages.
14298 o Minor features (logging):
14299 - Always prepend "Bug: " to any log message about a bug.
14300 - Put a platform string (e.g. "Linux i686") in the startup log
14301 message, so when people paste just their logs, we know if it's
14302 OpenBSD or Windows or what.
14303 - When logging memory usage, break down memory used in buffers by
14306 o Minor features (directory system):
14307 - New config option V2AuthoritativeDirectory that all directory
14308 authorities should set. This will let future authorities choose
14309 not to serve V2 directory information.
14310 - Directory authorities allow multiple router descriptors and/or extra
14311 info documents to be uploaded in a single go. This will make
14312 implementing proposal 104 simpler.
14314 o Minor features (controller):
14315 - Add a new config option __DisablePredictedCircuits designed for
14316 use by the controller, when we don't want Tor to build any circuits
14318 - Let the controller specify HOP=%d as an argument to ATTACHSTREAM,
14319 so we can exit from the middle of the circuit.
14320 - Implement "getinfo status/circuit-established".
14321 - Implement "getinfo status/version/..." so a controller can tell
14322 whether the current version is recommended, and whether any versions
14323 are good, and how many authorities agree. (Patch from shibz.)
14325 o Minor features (hidden services):
14326 - Allow multiple HiddenServicePort directives with the same virtual
14327 port; when they occur, the user is sent round-robin to one
14328 of the target ports chosen at random. Partially fixes bug 393 by
14329 adding limited ad-hoc round-robining.
14331 o Minor features (other):
14333 - Add a new AutomapHostsOnResolve option: when it is enabled, any
14334 resolve request for hosts matching a given pattern causes Tor to
14335 generate an internal virtual address mapping for that host. This
14336 allows DNSPort to work sensibly with hidden service users. By
14337 default, .exit and .onion addresses are remapped; the list of
14338 patterns can be reconfigured with AutomapHostsSuffixes.
14339 - Add an "-F" option to tor-resolve to force a resolve for a .onion
14340 address. Thanks to the AutomapHostsOnResolve option, this is no
14341 longer a completely silly thing to do.
14342 - If Tor is invoked from something that isn't a shell (e.g. Vidalia),
14343 now we expand "-f ~/.tor/torrc" correctly. Suggested by Matt Edman.
14344 - Treat "2gb" when given in torrc for a bandwidth as meaning 2gb,
14345 minus 1 byte: the actual maximum declared bandwidth.
14347 o Removed features:
14348 - Removed support for the old binary "version 0" controller protocol.
14349 This has been deprecated since 0.1.1, and warnings have been issued
14350 since 0.1.2. When we encounter a v0 control message, we now send
14351 back an error and close the connection.
14352 - Remove the old "dns worker" server DNS code: it hasn't been default
14353 since 0.1.2.2-alpha, and all the servers seem to be using the new
14356 o Minor bugfixes (portability):
14357 - Even though Windows is equally happy with / and \ as path separators,
14358 try to use \ consistently on Windows and / consistently on Unix: it
14359 makes the log messages nicer.
14360 - Correctly report platform name on Windows 95 OSR2 and Windows 98 SE.
14361 - Read resolv.conf files correctly on platforms where read() returns
14362 partial results on small file reads.
14364 o Minor bugfixes (directory):
14365 - Correctly enforce that elements of directory objects do not appear
14366 more often than they are allowed to appear.
14367 - When we are reporting the DirServer line we just parsed, we were
14368 logging the second stanza of the key fingerprint, not the first.
14370 o Minor bugfixes (logging):
14371 - When we hit an EOF on a log (probably because we're shutting down),
14372 don't try to remove the log from the list: just mark it as
14373 unusable. (Bulletproofs against bug 222.)
14375 o Minor bugfixes (other):
14376 - In the exitlist script, only consider the most recently published
14377 server descriptor for each server. Also, when the user requests
14378 a list of servers that _reject_ connections to a given address,
14379 explicitly exclude the IPs that also have servers that accept
14380 connections to that address. (Resolves bug 405.)
14381 - Stop allowing hibernating servers to be "stable" or "fast".
14382 - On Windows, we were preventing other processes from reading
14383 cached-routers while Tor was running. (Reported by janbar)
14384 - Make the NodeFamilies config option work. (Reported by
14385 lodger -- it has never actually worked, even though we added it
14387 - Check return values from pthread_mutex functions.
14388 - Don't save non-general-purpose router descriptors to the disk cache,
14389 because we have no way of remembering what their purpose was when
14391 - Add even more asserts to hunt down bug 417.
14392 - Build without verbose warnings even on (not-yet-released) gcc 4.2.
14393 - Fix a possible (but very unlikely) bug in picking routers by bandwidth.
14394 Add a log message to confirm that it is in fact unlikely.
14396 o Minor bugfixes (controller):
14397 - Make 'getinfo fingerprint' return a 551 error if we're not a
14398 server, so we match what the control spec claims we do. Reported
14400 - Fix a typo in an error message when extendcircuit fails that
14401 caused us to not follow the \r\n-based delimiter protocol. Reported
14404 o Code simplifications and refactoring:
14405 - Stop passing around circuit_t and crypt_path_t pointers that are
14406 implicit in other procedure arguments.
14407 - Drop the old code to choke directory connections when the
14408 corresponding OR connections got full: thanks to the cell queue
14409 feature, OR conns don't get full any more.
14410 - Make dns_resolve() handle attaching connections to circuits
14411 properly, so the caller doesn't have to.
14412 - Rename wants_to_read and wants_to_write to read/write_blocked_on_bw.
14413 - Keep the connection array as a dynamic smartlist_t, rather than as
14414 a fixed-sized array. This is important, as the number of connections
14415 is becoming increasingly decoupled from the number of sockets.
14418 Changes in version 0.1.2.14 - 2007-05-25
14419 Tor 0.1.2.14 changes the addresses of two directory authorities (this
14420 change especially affects those who serve or use hidden services),
14421 and fixes several other crash- and security-related bugs.
14423 o Directory authority changes:
14424 - Two directory authorities (moria1 and moria2) just moved to new
14425 IP addresses. This change will particularly affect those who serve
14426 or use hidden services.
14428 o Major bugfixes (crashes):
14429 - If a directory server runs out of space in the connection table
14430 as it's processing a begin_dir request, it will free the exit stream
14431 but leave it attached to the circuit, leading to unpredictable
14432 behavior. (Reported by seeess, fixes bug 425.)
14433 - Fix a bug in dirserv_remove_invalid() that would cause authorities
14434 to corrupt memory under some really unlikely scenarios.
14435 - Tighten router parsing rules. (Bugs reported by Benedikt Boss.)
14436 - Avoid segfaults when reading from mmaped descriptor file. (Reported
14439 o Major bugfixes (security):
14440 - When choosing an entry guard for a circuit, avoid using guards
14441 that are in the same family as the chosen exit -- not just guards
14442 that are exactly the chosen exit. (Reported by lodger.)
14444 o Major bugfixes (resource management):
14445 - If a directory authority is down, skip it when deciding where to get
14446 networkstatus objects or descriptors. Otherwise we keep asking
14447 every 10 seconds forever. Fixes bug 384.
14448 - Count it as a failure if we fetch a valid network-status but we
14449 don't want to keep it. Otherwise we'll keep fetching it and keep
14450 not wanting to keep it. Fixes part of bug 422.
14451 - If all of our dirservers have given us bad or no networkstatuses
14452 lately, then stop hammering them once per minute even when we
14453 think they're failed. Fixes another part of bug 422.
14456 - Actually set the purpose correctly for descriptors inserted with
14457 purpose=controller.
14458 - When we have k non-v2 authorities in our DirServer config,
14459 we ignored the last k authorities in the list when updating our
14461 - Correctly back-off from requesting router descriptors that we are
14462 having a hard time downloading.
14463 - Read resolv.conf files correctly on platforms where read() returns
14464 partial results on small file reads.
14465 - Don't rebuild the entire router store every time we get 32K of
14466 routers: rebuild it when the journal gets very large, or when
14467 the gaps in the store get very large.
14470 - When routers publish SVN revisions in their router descriptors,
14471 authorities now include those versions correctly in networkstatus
14473 - Warn when using a version of libevent before 1.3b to run a server on
14474 OSX or BSD: these versions interact badly with userspace threads.
14477 Changes in version 0.1.2.13 - 2007-04-24
14478 This release features some major anonymity fixes, such as safer path
14479 selection; better client performance; faster bootstrapping, better
14480 address detection, and better DNS support for servers; write limiting as
14481 well as read limiting to make servers easier to run; and a huge pile of
14482 other features and bug fixes. The bundles also ship with Vidalia 0.0.11.
14484 Tor 0.1.2.13 is released in memory of Rob Levin (1955-2006), aka lilo
14485 of the Freenode IRC network, remembering his patience and vision for
14486 free speech on the Internet.
14489 - Fix a memory leak when we ask for "all" networkstatuses and we
14490 get one we don't recognize.
14491 - Add more asserts to hunt down bug 417.
14492 - Disable kqueue on OS X 10.3 and earlier, to fix bug 371.
14495 Changes in version 0.1.2.12-rc - 2007-03-16
14497 - Fix an infinite loop introduced in 0.1.2.7-alpha when we serve
14498 directory information requested inside Tor connections (i.e. via
14499 begin_dir cells). It only triggered when the same connection was
14500 serving other data at the same time. Reported by seeess.
14503 - When creating a circuit via the controller, send a 'launched'
14504 event when we're done, so we follow the spec better.
14507 Changes in version 0.1.2.11-rc - 2007-03-15
14508 o Minor bugfixes (controller), reported by daejees:
14509 - Correct the control spec to match how the code actually responds
14510 to 'getinfo addr-mappings/*'.
14511 - The control spec described a GUARDS event, but the code
14512 implemented a GUARD event. Standardize on GUARD, but let people
14513 ask for GUARDS too.
14516 Changes in version 0.1.2.10-rc - 2007-03-07
14517 o Major bugfixes (Windows):
14518 - Do not load the NT services library functions (which may not exist)
14519 just to detect if we're a service trying to shut down. Now we run
14520 on Win98 and friends again.
14522 o Minor bugfixes (other):
14523 - Clarify a couple of log messages.
14524 - Fix a misleading socks5 error number.
14527 Changes in version 0.1.2.9-rc - 2007-03-02
14528 o Major bugfixes (Windows):
14529 - On MinGW, use "%I64u" to printf/scanf 64-bit integers, instead
14530 of the usual GCC "%llu". This prevents a bug when saving 64-bit
14531 int configuration values: the high-order 32 bits would get
14532 truncated. In particular, we were being bitten by the default
14533 MaxAdvertisedBandwidth of 128 TB turning into 0. (Fixes bug 400
14534 and maybe also bug 397.)
14536 o Minor bugfixes (performance):
14537 - Use OpenSSL's AES implementation on platforms where it's faster.
14538 This could save us as much as 10% CPU usage.
14540 o Minor bugfixes (server):
14541 - Do not rotate onion key immediately after setting it for the first
14544 o Minor bugfixes (directory authorities):
14545 - Stop calling servers that have been hibernating for a long time
14546 "stable". Also, stop letting hibernating or obsolete servers affect
14547 uptime and bandwidth cutoffs.
14548 - Stop listing hibernating servers in the v1 directory.
14550 o Minor bugfixes (hidden services):
14551 - Upload hidden service descriptors slightly less often, to reduce
14552 load on authorities.
14554 o Minor bugfixes (other):
14555 - Fix an assert that could trigger if a controller quickly set then
14556 cleared EntryNodes. Bug found by Udo van den Heuvel.
14557 - On architectures where sizeof(int)>4, still clamp declarable bandwidth
14559 - Fix a potential race condition in the rpm installer. Found by
14561 - Try to fix eventdns warnings once and for all: do not treat a dns rcode
14562 of 2 as indicating that the server is completely bad; it sometimes
14563 means that the server is just bad for the request in question. (may fix
14564 the last of bug 326.)
14565 - Disable encrypted directory connections when we don't have a server
14566 descriptor for the destination. We'll get this working again in
14570 Changes in version 0.1.2.8-beta - 2007-02-26
14571 o Major bugfixes (crashes):
14572 - Stop crashing when the controller asks us to resetconf more than
14573 one config option at once. (Vidalia 0.0.11 does this.)
14574 - Fix a crash that happened on Win98 when we're given command-line
14575 arguments: don't try to load NT service functions from advapi32.dll
14576 except when we need them. (Bug introduced in 0.1.2.7-alpha;
14578 - Fix a longstanding obscure crash bug that could occur when
14579 we run out of DNS worker processes. (Resolves bug 390.)
14581 o Major bugfixes (hidden services):
14582 - Correctly detect whether hidden service descriptor downloads are
14583 in-progress. (Suggested by Karsten Loesing; fixes bug 399.)
14585 o Major bugfixes (accounting):
14586 - When we start during an accounting interval before it's time to wake
14587 up, remember to wake up at the correct time. (May fix bug 342.)
14589 o Minor bugfixes (controller):
14590 - Give the controller END_STREAM_REASON_DESTROY events _before_ we
14591 clear the corresponding on_circuit variable, and remember later
14592 that we don't need to send a redundant CLOSED event. Resolves part
14594 - Report events where a resolve succeeded or where we got a socks
14595 protocol error correctly, rather than calling both of them
14597 - Change reported stream target addresses to IP consistently when
14598 we finally get the IP from an exit node.
14599 - Send log messages to the controller even if they happen to be very
14602 o Minor bugfixes (other):
14603 - Display correct results when reporting which versions are
14604 recommended, and how recommended they are. (Resolves bug 383.)
14605 - Improve our estimates for directory bandwidth to be less random:
14606 guess that an unrecognized directory will have the average bandwidth
14607 from all known directories, not that it will have the average
14608 bandwidth from those directories earlier than it on the list.
14609 - If we start a server with ClientOnly 1, then set ClientOnly to 0
14610 and hup, stop triggering an assert based on an empty onion_key.
14611 - On platforms with no working mmap() equivalent, don't warn the
14612 user when cached-routers doesn't exist.
14613 - Warn the user when mmap() [or its equivalent] fails for some reason
14614 other than file-not-found.
14615 - Don't warn the user when cached-routers.new doesn't exist: that's
14616 perfectly fine when starting up for the first time.
14617 - When EntryNodes are configured, rebuild the guard list to contain,
14618 in order: the EntryNodes that were guards before; the rest of the
14619 EntryNodes; the nodes that were guards before.
14620 - Mask out all signals in sub-threads; only the libevent signal
14621 handler should be processing them. This should prevent some crashes
14622 on some machines using pthreads. (Patch from coderman.)
14623 - Fix switched arguments on memset in the implementation of
14624 tor_munmap() for systems with no mmap() call.
14625 - When Tor receives a router descriptor that it asked for, but
14626 no longer wants (because it has received fresh networkstatuses
14627 in the meantime), do not warn the user. Cache the descriptor if
14628 we're a cache; drop it if we aren't.
14629 - Make earlier entry guards _really_ get retried when the network
14631 - On a malformed DNS reply, always give an error to the corresponding
14633 - Build with recent libevents on platforms that do not define the
14634 nonstandard types "u_int8_t" and friends.
14636 o Minor features (controller):
14637 - Warn the user when an application uses the obsolete binary v0
14638 control protocol. We're planning to remove support for it during
14639 the next development series, so it's good to give people some
14641 - Add STREAM_BW events to report per-entry-stream bandwidth
14642 use. (Patch from Robert Hogan.)
14643 - Rate-limit SIGNEWNYM signals in response to controllers that
14644 impolitely generate them for every single stream. (Patch from
14645 mwenge; closes bug 394.)
14646 - Make REMAP stream events have a SOURCE (cache or exit), and
14647 make them generated in every case where we get a successful
14648 connected or resolved cell.
14650 o Minor bugfixes (performance):
14651 - Call router_have_min_dir_info half as often. (This is showing up in
14652 some profiles, but not others.)
14653 - When using GCC, make log_debug never get called at all, and its
14654 arguments never get evaluated, when no debug logs are configured.
14655 (This is showing up in some profiles, but not others.)
14658 - Remove some never-implemented options. Mark PathlenCoinWeight as
14660 - Implement proposal 106: Stop requiring clients to have well-formed
14661 certificates; stop checking nicknames in certificates. (Clients
14662 have certificates so that they can look like Tor servers, but in
14663 the future we might want to allow them to look like regular TLS
14664 clients instead. Nicknames in certificates serve no purpose other
14665 than making our protocol easier to recognize on the wire.)
14666 - Revise messages on handshake failure again to be even more clear about
14667 which are incoming connections and which are outgoing.
14668 - Discard any v1 directory info that's over 1 month old (for
14669 directories) or over 1 week old (for running-routers lists).
14670 - Do not warn when individual nodes in the configuration's EntryNodes,
14671 ExitNodes, etc are down: warn only when all possible nodes
14672 are down. (Fixes bug 348.)
14673 - Always remove expired routers and networkstatus docs before checking
14674 whether we have enough information to build circuits. (Fixes
14676 - Put a lower-bound on MaxAdvertisedBandwidth.
14679 Changes in version 0.1.2.7-alpha - 2007-02-06
14680 o Major bugfixes (rate limiting):
14681 - Servers decline directory requests much more aggressively when
14682 they're low on bandwidth. Otherwise they end up queueing more and
14683 more directory responses, which can't be good for latency.
14684 - But never refuse directory requests from local addresses.
14685 - Fix a memory leak when sending a 503 response for a networkstatus
14687 - Be willing to read or write on local connections (e.g. controller
14688 connections) even when the global rate limiting buckets are empty.
14689 - If our system clock jumps back in time, don't publish a negative
14690 uptime in the descriptor. Also, don't let the global rate limiting
14691 buckets go absurdly negative.
14692 - Flush local controller connection buffers periodically as we're
14693 writing to them, so we avoid queueing 4+ megabytes of data before
14696 o Major bugfixes (NT services):
14697 - Install as NT_AUTHORITY\LocalService rather than as SYSTEM; add a
14698 command-line flag so that admins can override the default by saying
14699 "tor --service install --user "SomeUser"". This will not affect
14700 existing installed services. Also, warn the user that the service
14701 will look for its configuration file in the service user's
14702 %appdata% directory. (We can't do the 'hardwire the user's appdata
14703 directory' trick any more, since we may not have read access to that
14706 o Major bugfixes (other):
14707 - Previously, we would cache up to 16 old networkstatus documents
14708 indefinitely, if they came from nontrusted authorities. Now we
14709 discard them if they are more than 10 days old.
14710 - Fix a crash bug in the presence of DNS hijacking (reported by Andrew
14712 - Detect and reject malformed DNS responses containing circular
14714 - If exits are rare enough that we're not marking exits as guards,
14715 ignore exit bandwidth when we're deciding the required bandwidth
14717 - When we're handling a directory connection tunneled over Tor,
14718 don't fill up internal memory buffers with all the data we want
14719 to tunnel; instead, only add it if the OR connection that will
14720 eventually receive it has some room for it. (This can lead to
14721 slowdowns in tunneled dir connections; a better solution will have
14722 to wait for 0.2.0.)
14724 o Minor bugfixes (dns):
14725 - Add some defensive programming to eventdns.c in an attempt to catch
14726 possible memory-stomping bugs.
14727 - Detect and reject DNS replies containing IPv4 or IPv6 records with
14728 an incorrect number of bytes. (Previously, we would ignore the
14730 - Fix as-yet-unused reverse IPv6 lookup code so it sends nybbles
14731 in the correct order, and doesn't crash.
14732 - Free memory held in recently-completed DNS lookup attempts on exit.
14733 This was not a memory leak, but may have been hiding memory leaks.
14734 - Handle TTL values correctly on reverse DNS lookups.
14735 - Treat failure to parse resolv.conf as an error.
14737 o Minor bugfixes (other):
14738 - Fix crash with "tor --list-fingerprint" (reported by seeess).
14739 - When computing clock skew from directory HTTP headers, consider what
14740 time it was when we finished asking for the directory, not what
14742 - Expire socks connections if they spend too long waiting for the
14743 handshake to finish. Previously we would let them sit around for
14744 days, if the connecting application didn't close them either.
14745 - And if the socks handshake hasn't started, don't send a
14746 "DNS resolve socks failed" handshake reply; just close it.
14747 - Stop using C functions that OpenBSD's linker doesn't like.
14748 - Don't launch requests for descriptors unless we have networkstatuses
14749 from at least half of the authorities. This delays the first
14750 download slightly under pathological circumstances, but can prevent
14751 us from downloading a bunch of descriptors we don't need.
14752 - Do not log IPs with TLS failures for incoming TLS
14753 connections. (Fixes bug 382.)
14754 - If the user asks to use invalid exit nodes, be willing to use
14756 - Stop using the reserved ac_cv namespace in our configure script.
14757 - Call stat() slightly less often; use fstat() when possible.
14758 - Refactor the way we handle pending circuits when an OR connection
14759 completes or fails, in an attempt to fix a rare crash bug.
14760 - Only rewrite a conn's address based on X-Forwarded-For: headers
14761 if it's a parseable public IP address; and stop adding extra quotes
14762 to the resulting address.
14765 - Weight directory requests by advertised bandwidth. Now we can
14766 let servers enable write limiting but still allow most clients to
14767 succeed at their directory requests. (We still ignore weights when
14768 choosing a directory authority; I hope this is a feature.)
14771 - Create a new file ReleaseNotes which was the old ChangeLog. The
14772 new ChangeLog file now includes the summaries for all development
14774 - Check for addresses with invalid characters at the exit as well
14775 as at the client, and warn less verbosely when they fail. You can
14776 override this by setting ServerDNSAllowNonRFC953Addresses to 1.
14777 - Adapt a patch from goodell to let the contrib/exitlist script
14778 take arguments rather than require direct editing.
14779 - Inform the server operator when we decide not to advertise a
14780 DirPort due to AccountingMax enabled or a low BandwidthRate. It
14781 was confusing Zax, so now we're hopefully more helpful.
14782 - Bring us one step closer to being able to establish an encrypted
14783 directory tunnel without knowing a descriptor first. Still not
14784 ready yet. As part of the change, now assume we can use a
14785 create_fast cell if we don't know anything about a router.
14786 - Allow exit nodes to use nameservers running on ports other than 53.
14787 - Servers now cache reverse DNS replies.
14788 - Add an --ignore-missing-torrc command-line option so that we can
14789 get the "use sensible defaults if the configuration file doesn't
14790 exist" behavior even when specifying a torrc location on the command
14793 o Minor features (controller):
14794 - Track reasons for OR connection failure; make these reasons
14795 available via the controller interface. (Patch from Mike Perry.)
14796 - Add a SOCKS_BAD_HOSTNAME client status event so controllers
14797 can learn when clients are sending malformed hostnames to Tor.
14798 - Clean up documentation for controller status events.
14799 - Add a REMAP status to stream events to note that a stream's
14800 address has changed because of a cached address or a MapAddress
14804 Changes in version 0.1.2.6-alpha - 2007-01-09
14806 - Fix an assert error introduced in 0.1.2.5-alpha: if a single TLS
14807 connection handles more than 4 gigs in either direction, we crash.
14808 - Fix an assert error introduced in 0.1.2.5-alpha: if we're an
14809 advertised exit node, somebody might try to exit from us when
14810 we're bootstrapping and before we've built our descriptor yet.
14811 Refuse the connection rather than crashing.
14814 - Warn if we (as a server) find that we've resolved an address that we
14815 weren't planning to resolve.
14816 - Warn that using select() on any libevent version before 1.1 will be
14817 unnecessarily slow (even for select()).
14818 - Flush ERR-level controller status events just like we currently
14819 flush ERR-level log events, so that a Tor shutdown doesn't prevent
14820 the controller from learning about current events.
14822 o Minor features (more controller status events):
14823 - Implement EXTERNAL_ADDRESS server status event so controllers can
14824 learn when our address changes.
14825 - Implement BAD_SERVER_DESCRIPTOR server status event so controllers
14826 can learn when directories reject our descriptor.
14827 - Implement SOCKS_UNKNOWN_PROTOCOL client status event so controllers
14828 can learn when a client application is speaking a non-socks protocol
14830 - Implement DANGEROUS_SOCKS client status event so controllers
14831 can learn when a client application is leaking DNS addresses.
14832 - Implement BUG general status event so controllers can learn when
14833 Tor is unhappy about its internal invariants.
14834 - Implement CLOCK_SKEW general status event so controllers can learn
14835 when Tor thinks the system clock is set incorrectly.
14836 - Implement GOOD_SERVER_DESCRIPTOR and ACCEPTED_SERVER_DESCRIPTOR
14837 server status events so controllers can learn when their descriptors
14838 are accepted by a directory.
14839 - Implement CHECKING_REACHABILITY and REACHABILITY_{SUCCEEDED|FAILED}
14840 server status events so controllers can learn about Tor's progress in
14841 deciding whether it's reachable from the outside.
14842 - Implement BAD_LIBEVENT general status event so controllers can learn
14843 when we have a version/method combination in libevent that needs to
14845 - Implement NAMESERVER_STATUS, NAMESERVER_ALL_DOWN, DNS_HIJACKED,
14846 and DNS_USELESS server status events so controllers can learn
14847 about changes to DNS server status.
14849 o Minor features (directory):
14850 - Authorities no longer recommend exits as guards if this would shift
14851 too much load to the exit nodes.
14854 Changes in version 0.1.2.5-alpha - 2007-01-06
14856 - Enable write limiting as well as read limiting. Now we sacrifice
14857 capacity if we're pushing out lots of directory traffic, rather
14858 than overrunning the user's intended bandwidth limits.
14859 - Include TLS overhead when counting bandwidth usage; previously, we
14860 would count only the bytes sent over TLS, but not the bytes used
14862 - Support running the Tor service with a torrc not in the same
14863 directory as tor.exe and default to using the torrc located in
14864 the %appdata%\Tor\ of the user who installed the service. Patch
14866 - Servers now check for the case when common DNS requests are going to
14867 wildcarded addresses (i.e. all getting the same answer), and change
14868 their exit policy to reject *:* if it's happening.
14869 - Implement BEGIN_DIR cells, so we can connect to the directory
14870 server via TLS to do encrypted directory requests rather than
14871 plaintext. Enable via the TunnelDirConns and PreferTunneledDirConns
14872 config options if you like.
14874 o Minor features (config and docs):
14875 - Start using the state file to store bandwidth accounting data:
14876 the bw_accounting file is now obsolete. We'll keep generating it
14877 for a while for people who are still using 0.1.2.4-alpha.
14878 - Try to batch changes to the state file so that we do as few
14879 disk writes as possible while still storing important things in
14881 - The state file and the bw_accounting file get saved less often when
14882 the AvoidDiskWrites config option is set.
14883 - Make PIDFile work on Windows (untested).
14884 - Add internal descriptions for a bunch of configuration options:
14885 accessible via controller interface and in comments in saved
14887 - Reject *:563 (NNTPS) in the default exit policy. We already reject
14888 NNTP by default, so this seems like a sensible addition.
14889 - Clients now reject hostnames with invalid characters. This should
14890 avoid some inadvertent info leaks. Add an option
14891 AllowNonRFC953Hostnames to disable this behavior, in case somebody
14892 is running a private network with hosts called @, !, and #.
14893 - Add a maintainer script to tell us which options are missing
14894 documentation: "make check-docs".
14895 - Add a new address-spec.txt document to describe our special-case
14896 addresses: .exit, .onion, and .noconnnect.
14898 o Minor features (DNS):
14899 - Ongoing work on eventdns infrastructure: now it has dns server
14900 and ipv6 support. One day Tor will make use of it.
14901 - Add client-side caching for reverse DNS lookups.
14902 - Add support to tor-resolve tool for reverse lookups and SOCKS5.
14903 - When we change nameservers or IP addresses, reset and re-launch
14904 our tests for DNS hijacking.
14906 o Minor features (directory):
14907 - Authorities now specify server versions in networkstatus. This adds
14908 about 2% to the size of compressed networkstatus docs, and allows
14909 clients to tell which servers support BEGIN_DIR and which don't.
14910 The implementation is forward-compatible with a proposed future
14911 protocol version scheme not tied to Tor versions.
14912 - DirServer configuration lines now have an orport= option so
14913 clients can open encrypted tunnels to the authorities without
14914 having downloaded their descriptors yet. Enabled for moria1,
14915 moria2, tor26, and lefkada now in the default configuration.
14916 - Directory servers are more willing to send a 503 "busy" if they
14917 are near their write limit, especially for v1 directory requests.
14918 Now they can use their limited bandwidth for actual Tor traffic.
14919 - Clients track responses with status 503 from dirservers. After a
14920 dirserver has given us a 503, we try not to use it until an hour has
14921 gone by, or until we have no dirservers that haven't given us a 503.
14922 - When we get a 503 from a directory, and we're not a server, we don't
14923 count the failure against the total number of failures allowed
14924 for the thing we're trying to download.
14925 - Report X-Your-Address-Is correctly from tunneled directory
14926 connections; don't report X-Your-Address-Is when it's an internal
14927 address; and never believe reported remote addresses when they're
14929 - Protect against an unlikely DoS attack on directory servers.
14930 - Add a BadDirectory flag to network status docs so that authorities
14931 can (eventually) tell clients about caches they believe to be
14934 o Minor features (controller):
14935 - Have GETINFO dir/status/* work on hosts with DirPort disabled.
14936 - Reimplement GETINFO so that info/names stays in sync with the
14938 - Implement "GETINFO fingerprint".
14939 - Implement "SETEVENTS GUARD" so controllers can get updates on
14940 entry guard status as it changes.
14942 o Minor features (clean up obsolete pieces):
14943 - Remove some options that have been deprecated since at least
14944 0.1.0.x: AccountingMaxKB, LogFile, DebugLogFile, LogLevel, and
14945 SysLog. Use AccountingMax instead of AccountingMaxKB, and use Log
14946 to set log options.
14947 - We no longer look for identity and onion keys in "identity.key" and
14948 "onion.key" -- these were replaced by secret_id_key and
14949 secret_onion_key in 0.0.8pre1.
14950 - We no longer require unrecognized directory entries to be
14953 o Major bugfixes (security):
14954 - Stop sending the HttpProxyAuthenticator string to directory
14955 servers when directory connections are tunnelled through Tor.
14956 - Clients no longer store bandwidth history in the state file.
14957 - Do not log introduction points for hidden services if SafeLogging
14959 - When generating bandwidth history, round down to the nearest
14960 1k. When storing accounting data, round up to the nearest 1k.
14961 - When we're running as a server, remember when we last rotated onion
14962 keys, so that we will rotate keys once they're a week old even if
14963 we never stay up for a week ourselves.
14965 o Major bugfixes (other):
14966 - Fix a longstanding bug in eventdns that prevented the count of
14967 timed-out resolves from ever being reset. This bug caused us to
14968 give up on a nameserver the third time it timed out, and try it
14969 10 seconds later... and to give up on it every time it timed out
14971 - Take out the '5 second' timeout from the connection retry
14972 schedule. Now the first connect attempt will wait a full 10
14973 seconds before switching to a new circuit. Perhaps this will help
14974 a lot. Based on observations from Mike Perry.
14975 - Fix a bug on the Windows implementation of tor_mmap_file() that
14976 would prevent the cached-routers file from ever loading. Reported
14980 - Fix an assert failure when a directory authority sets
14981 AuthDirRejectUnlisted and then receives a descriptor from an
14982 unlisted router. Reported by seeess.
14983 - Avoid a double-free when parsing malformed DirServer lines.
14984 - Fix a bug when a BSD-style PF socket is first used. Patch from
14986 - Fix a bug in 0.1.2.2-alpha that prevented clients from asking
14987 to resolve an address at a given exit node even when they ask for
14989 - Servers no longer ever list themselves in their "family" line,
14990 even if configured to do so. This makes it easier to configure
14991 family lists conveniently.
14992 - When running as a server, don't fall back to 127.0.0.1 when no
14993 nameservers are configured in /etc/resolv.conf; instead, make the
14994 user fix resolv.conf or specify nameservers explicitly. (Resolves
14996 - Stop accepting certain malformed ports in configured exit policies.
14997 - Don't re-write the fingerprint file every restart, unless it has
14999 - Stop warning when a single nameserver fails: only warn when _all_ of
15000 our nameservers have failed. Also, when we only have one nameserver,
15001 raise the threshold for deciding that the nameserver is dead.
15002 - Directory authorities now only decide that routers are reachable
15003 if their identity keys are as expected.
15004 - When the user uses bad syntax in the Log config line, stop
15005 suggesting other bad syntax as a replacement.
15006 - Correctly detect ipv6 DNS capability on OpenBSD.
15008 o Minor bugfixes (controller):
15009 - Report the circuit number correctly in STREAM CLOSED events. Bug
15010 reported by Mike Perry.
15011 - Do not report bizarre values for results of accounting GETINFOs
15012 when the last second's write or read exceeds the allotted bandwidth.
15013 - Report "unrecognized key" rather than an empty string when the
15014 controller tries to fetch a networkstatus that doesn't exist.
15017 Changes in version 0.1.1.26 - 2006-12-14
15018 o Security bugfixes:
15019 - Stop sending the HttpProxyAuthenticator string to directory
15020 servers when directory connections are tunnelled through Tor.
15021 - Clients no longer store bandwidth history in the state file.
15022 - Do not log introduction points for hidden services if SafeLogging
15026 - Fix an assert failure when a directory authority sets
15027 AuthDirRejectUnlisted and then receives a descriptor from an
15028 unlisted router (reported by seeess).
15031 Changes in version 0.1.2.4-alpha - 2006-12-03
15033 - Add support for using natd; this allows FreeBSDs earlier than
15034 5.1.2 to have ipfw send connections through Tor without using
15035 SOCKS. (Patch from Zajcev Evgeny with tweaks from tup.)
15038 - Make all connections to addresses of the form ".noconnect"
15039 immediately get closed. This lets application/controller combos
15040 successfully test whether they're talking to the same Tor by
15041 watching for STREAM events.
15042 - Make cross.sh cross-compilation script work even when autogen.sh
15043 hasn't been run. (Patch from Michael Mohr.)
15044 - Statistics dumped by -USR2 now include a breakdown of public key
15045 operations, for profiling.
15048 - Fix a major leak when directory authorities parse their
15049 approved-routers list, a minor memory leak when we fail to pick
15050 an exit node, and a few rare leaks on errors.
15051 - Handle TransPort connections even when the server sends data before
15052 the client sends data. Previously, the connection would just hang
15053 until the client sent data. (Patch from tup based on patch from
15055 - Avoid assert failure when our cached-routers file is empty on
15059 - Don't log spurious warnings when we see a circuit close reason we
15060 don't recognize; it's probably just from a newer version of Tor.
15061 - Have directory authorities allow larger amounts of drift in uptime
15062 without replacing the server descriptor: previously, a server that
15063 restarted every 30 minutes could have 48 "interesting" descriptors
15065 - Start linking to the Tor specification and Tor reference manual
15066 correctly in the Windows installer.
15067 - Add Vidalia to the OS X uninstaller script, so when we uninstall
15068 Tor/Privoxy we also uninstall Vidalia.
15069 - Resume building on Irix64, and fix a lot of warnings from its
15070 MIPSpro C compiler.
15071 - Don't corrupt last_guessed_ip in router_new_address_suggestion()
15072 when we're running as a client.
15075 Changes in version 0.1.1.25 - 2006-11-04
15077 - When a client asks us to resolve (rather than connect to)
15078 an address, and we have a cached answer, give them the cached
15079 answer. Previously, we would give them no answer at all.
15080 - We were building exactly the wrong circuits when we predict
15081 hidden service requirements, meaning Tor would have to build all
15082 its circuits on demand.
15083 - If none of our live entry guards have a high uptime, but we
15084 require a guard with a high uptime, try adding a new guard before
15085 we give up on the requirement. This patch should make long-lived
15086 connections more stable on average.
15087 - When testing reachability of our DirPort, don't launch new
15088 tests when there's already one in progress -- unreachable
15089 servers were stacking up dozens of testing streams.
15091 o Security bugfixes:
15092 - When the user sends a NEWNYM signal, clear the client-side DNS
15093 cache too. Otherwise we continue to act on previous information.
15096 - Avoid a memory corruption bug when creating a hash table for
15098 - Avoid possibility of controller-triggered crash when misusing
15099 certain commands from a v0 controller on platforms that do not
15100 handle printf("%s",NULL) gracefully.
15101 - Avoid infinite loop on unexpected controller input.
15102 - Don't log spurious warnings when we see a circuit close reason we
15103 don't recognize; it's probably just from a newer version of Tor.
15104 - Add Vidalia to the OS X uninstaller script, so when we uninstall
15105 Tor/Privoxy we also uninstall Vidalia.
15108 Changes in version 0.1.2.3-alpha - 2006-10-29
15110 - Prepare for servers to publish descriptors less often: never
15111 discard a descriptor simply for being too old until either it is
15112 recommended by no authorities, or until we get a better one for
15113 the same router. Make caches consider retaining old recommended
15114 routers for even longer.
15115 - If most authorities set a BadExit flag for a server, clients
15116 don't think of it as a general-purpose exit. Clients only consider
15117 authorities that advertise themselves as listing bad exits.
15118 - Directory servers now provide 'Pragma: no-cache' and 'Expires'
15119 headers for content, so that we can work better in the presence of
15120 caching HTTP proxies.
15121 - Allow authorities to list nodes as bad exits by fingerprint or by
15124 o Minor features, controller:
15125 - Add a REASON field to CIRC events; for backward compatibility, this
15126 field is sent only to controllers that have enabled the extended
15127 event format. Also, add additional reason codes to explain why
15128 a given circuit has been destroyed or truncated. (Patches from
15130 - Add a REMOTE_REASON field to extended CIRC events to tell the
15131 controller about why a remote OR told us to close a circuit.
15132 - Stream events also now have REASON and REMOTE_REASON fields,
15133 working much like those for circuit events.
15134 - There's now a GETINFO ns/... field so that controllers can ask Tor
15135 about the current status of a router.
15136 - A new event type "NS" to inform a controller when our opinion of
15137 a router's status has changed.
15138 - Add a GETINFO events/names and GETINFO features/names so controllers
15139 can tell which events and features are supported.
15140 - A new CLEARDNSCACHE signal to allow controllers to clear the
15141 client-side DNS cache without expiring circuits.
15143 o Security bugfixes:
15144 - When the user sends a NEWNYM signal, clear the client-side DNS
15145 cache too. Otherwise we continue to act on previous information.
15148 - Avoid sending junk to controllers or segfaulting when a controller
15149 uses EVENT_NEW_DESC with verbose nicknames.
15150 - Stop triggering asserts if the controller tries to extend hidden
15151 service circuits (reported by mwenge).
15152 - Avoid infinite loop on unexpected controller input.
15153 - When the controller does a "GETINFO network-status", tell it
15154 about even those routers whose descriptors are very old, and use
15155 long nicknames where appropriate.
15156 - Change NT service functions to be loaded on demand. This lets us
15157 build with MinGW without breaking Tor for Windows 98 users.
15158 - Do DirPort reachability tests less often, since a single test
15159 chews through many circuits before giving up.
15160 - In the hidden service example in torrc.sample, stop recommending
15161 esoteric and discouraged hidden service options.
15162 - When stopping an NT service, wait up to 10 sec for it to actually
15163 stop. Patch from Matt Edman; resolves bug 295.
15164 - Fix handling of verbose nicknames with ORCONN controller events:
15165 make them show up exactly when requested, rather than exactly when
15167 - When reporting verbose nicknames in entry_guards_getinfo(), avoid
15168 printing a duplicate "$" in the keys we send (reported by mwenge).
15169 - Correctly set maximum connection limit on Cygwin. (This time
15171 - Try to detect Windows correctly when cross-compiling.
15172 - Detect the size of the routers file correctly even if it is
15173 corrupted (on systems without mmap) or not page-aligned (on systems
15174 with mmap). This bug was harmless.
15175 - Sometimes we didn't bother sending a RELAY_END cell when an attempt
15176 to open a stream fails; now we do in more cases. This should
15177 make clients able to find a good exit faster in some cases, since
15178 unhandleable requests will now get an error rather than timing out.
15179 - Resolve two memory leaks when rebuilding the on-disk router cache
15180 (reported by fookoowa).
15181 - Clean up minor code warnings suggested by the MIPSpro C compiler,
15182 and reported by some Centos users.
15183 - Controller signals now work on non-Unix platforms that don't define
15184 SIGUSR1 and SIGUSR2 the way we expect.
15185 - Patch from Michael Mohr to contrib/cross.sh, so it checks more
15186 values before failing, and always enables eventdns.
15187 - Libevent-1.2 exports, but does not define in its headers, strlcpy.
15188 Try to fix this in configure.in by checking for most functions
15189 before we check for libevent.
15192 Changes in version 0.1.2.2-alpha - 2006-10-07
15194 - Make our async eventdns library on-by-default for Tor servers,
15195 and plan to deprecate the separate dnsworker threads.
15196 - Add server-side support for "reverse" DNS lookups (using PTR
15197 records so clients can determine the canonical hostname for a given
15198 IPv4 address). Only supported by servers using eventdns; servers
15199 now announce in their descriptors whether they support eventdns.
15200 - Specify and implement client-side SOCKS5 interface for reverse DNS
15201 lookups (see doc/socks-extensions.txt).
15202 - Add a BEGIN_DIR relay cell type for an easier in-protocol way to
15203 connect to directory servers through Tor. Previously, clients needed
15204 to find Tor exits to make private connections to directory servers.
15205 - Avoid choosing Exit nodes for entry or middle hops when the
15206 total bandwidth available from non-Exit nodes is much higher than
15207 the total bandwidth available from Exit nodes.
15208 - Workaround for name servers (like Earthlink's) that hijack failing
15209 DNS requests and replace the no-such-server answer with a "helpful"
15210 redirect to an advertising-driven search portal. Also work around
15211 DNS hijackers who "helpfully" decline to hijack known-invalid
15212 RFC2606 addresses. Config option "ServerDNSDetectHijacking 0"
15213 lets you turn it off.
15214 - Send out a burst of long-range padding cells once we've established
15215 that we're reachable. Spread them over 4 circuits, so hopefully
15216 a few will be fast. This exercises our bandwidth and bootstraps
15217 us into the directory more quickly.
15219 o New/improved config options:
15220 - Add new config option "ResolvConf" to let the server operator
15221 choose an alternate resolve.conf file when using eventdns.
15222 - Add an "EnforceDistinctSubnets" option to control our "exclude
15223 servers on the same /16" behavior. It's still on by default; this
15224 is mostly for people who want to operate private test networks with
15225 all the machines on the same subnet.
15226 - If one of our entry guards is on the ExcludeNodes list, or the
15227 directory authorities don't think it's a good guard, treat it as
15228 if it were unlisted: stop using it as a guard, and throw it off
15229 the guards list if it stays that way for a long time.
15230 - Allow directory authorities to be marked separately as authorities
15231 for the v1 directory protocol, the v2 directory protocol, and
15232 as hidden service directories, to make it easier to retire old
15233 authorities. V1 authorities should set "HSAuthoritativeDir 1"
15234 to continue being hidden service authorities too.
15235 - Remove 8888 as a LongLivedPort, and add 6697 (IRCS).
15237 o Minor features, controller:
15238 - Fix CIRC controller events so that controllers can learn the
15239 identity digests of non-Named servers used in circuit paths.
15240 - Let controllers ask for more useful identifiers for servers. Instead
15241 of learning identity digests for un-Named servers and nicknames
15242 for Named servers, the new identifiers include digest, nickname,
15243 and indication of Named status. Off by default; see control-spec.txt
15244 for more information.
15245 - Add a "getinfo address" controller command so it can display Tor's
15246 best guess to the user.
15247 - New controller event to alert the controller when our server
15248 descriptor has changed.
15249 - Give more meaningful errors on controller authentication failure.
15251 o Minor features, other:
15252 - When asked to resolve a hostname, don't use non-exit servers unless
15253 requested to do so. This allows servers with broken DNS to be
15254 useful to the network.
15255 - Divide eventdns log messages into warn and info messages.
15256 - Reserve the nickname "Unnamed" for routers that can't pick
15257 a hostname: any router can call itself Unnamed; directory
15258 authorities will never allocate Unnamed to any particular router;
15259 clients won't believe that any router is the canonical Unnamed.
15260 - Only include function names in log messages for info/debug messages.
15261 For notice/warn/err, the content of the message should be clear on
15262 its own, and printing the function name only confuses users.
15263 - Avoid some false positives during reachability testing: don't try
15264 to test via a server that's on the same /24 as us.
15265 - If we fail to build a circuit to an intended enclave, and it's
15266 not mandatory that we use that enclave, stop wanting it.
15267 - When eventdns is enabled, allow multithreaded builds on NetBSD and
15268 OpenBSD. (We had previously disabled threads on these platforms
15269 because they didn't have working thread-safe resolver functions.)
15271 o Major bugfixes, anonymity/security:
15272 - If a client asked for a server by name, and there's a named server
15273 in our network-status but we don't have its descriptor yet, we
15274 could return an unnamed server instead.
15275 - Fix NetBSD bug that could allow someone to force uninitialized RAM
15276 to be sent to a server's DNS resolver. This only affects NetBSD
15277 and other platforms that do not bounds-check tolower().
15278 - Reject (most) attempts to use Tor circuits with length one. (If
15279 many people start using Tor as a one-hop proxy, exit nodes become
15280 a more attractive target for compromise.)
15281 - Just because your DirPort is open doesn't mean people should be
15282 able to remotely teach you about hidden service descriptors. Now
15283 only accept rendezvous posts if you've got HSAuthoritativeDir set.
15285 o Major bugfixes, other:
15286 - Don't crash on race condition in dns.c: tor_assert(!resolve->expire)
15287 - When a client asks the server to resolve (not connect to)
15288 an address, and it has a cached answer, give them the cached answer.
15289 Previously, the server would give them no answer at all.
15290 - Allow really slow clients to not hang up five minutes into their
15291 directory downloads (suggested by Adam J. Richter).
15292 - We were building exactly the wrong circuits when we anticipated
15293 hidden service requirements, meaning Tor would have to build all
15294 its circuits on demand.
15295 - Avoid crashing when we mmap a router cache file of size 0.
15296 - When testing reachability of our DirPort, don't launch new
15297 tests when there's already one in progress -- unreachable
15298 servers were stacking up dozens of testing streams.
15300 o Minor bugfixes, correctness:
15301 - If we're a directory mirror and we ask for "all" network status
15302 documents, we would discard status documents from authorities
15303 we don't recognize.
15304 - Avoid a memory corruption bug when creating a hash table for
15306 - Avoid controller-triggered crash when misusing certain commands
15307 from a v0 controller on platforms that do not handle
15308 printf("%s",NULL) gracefully.
15309 - Don't crash when a controller sends a third argument to an
15310 "extendcircuit" request.
15311 - Controller protocol fixes: fix encoding in "getinfo addr-mappings"
15312 response; fix error code when "getinfo dir/status/" fails.
15313 - Avoid crash when telling controller stream-status and a stream
15315 - Patch from Adam Langley to fix assert() in eventdns.c.
15316 - Fix a debug log message in eventdns to say "X resolved to Y"
15317 instead of "X resolved to X".
15318 - Make eventdns give strings for DNS errors, not just error numbers.
15319 - Track unreachable entry guards correctly: don't conflate
15320 'unreachable by us right now' with 'listed as down by the directory
15321 authorities'. With the old code, if a guard was unreachable by
15322 us but listed as running, it would clog our guard list forever.
15323 - Behave correctly in case we ever have a network with more than
15324 2GB/s total advertised capacity.
15325 - Make TrackExitHosts case-insensitive, and fix the behavior of
15326 ".suffix" TrackExitHosts items to avoid matching in the middle of
15328 - Finally fix the openssl warnings from newer gccs that believe that
15329 ignoring a return value is okay, but casting a return value and
15330 then ignoring it is a sign of madness.
15331 - Prevent the contrib/exitlist script from printing the same
15332 result more than once.
15333 - Patch from Steve Hildrey: Generate network status correctly on
15334 non-versioning dirservers.
15335 - Don't listen to the X-Your-Address-Is hint if you did the lookup
15336 via Tor; otherwise you'll think you're the exit node's IP address.
15338 o Minor bugfixes, performance:
15339 - Two small performance improvements on parsing descriptors.
15340 - Major performance improvement on inserting descriptors: change
15341 algorithm from O(n^2) to O(n).
15342 - Make the common memory allocation path faster on machines where
15343 malloc(0) returns a pointer.
15344 - Start remembering X-Your-Address-Is directory hints even if you're
15345 a client, so you can become a server more smoothly.
15346 - Avoid duplicate entries on MyFamily line in server descriptor.
15348 o Packaging, features:
15349 - Remove architecture from OS X builds. The official builds are
15350 now universal binaries.
15351 - The Debian package now uses --verify-config when (re)starting,
15352 to distinguish configuration errors from other errors.
15353 - Update RPMs to require libevent 1.1b.
15355 o Packaging, bugfixes:
15356 - Patches so Tor builds with MinGW on Windows.
15357 - Patches so Tor might run on Cygwin again.
15358 - Resume building on non-gcc compilers and ancient gcc. Resume
15359 building with the -O0 compile flag. Resume building cleanly on
15361 - Run correctly on OS X platforms with case-sensitive filesystems.
15362 - Correct includes for net/if.h and net/pfvar.h on OpenBSD (from Tup).
15363 - Add autoconf checks so Tor can build on Solaris x86 again.
15366 - Documented (and renamed) ServerDNSSearchDomains and
15367 ServerDNSResolvConfFile options.
15368 - Be clearer that the *ListenAddress directives can be repeated
15372 Changes in version 0.1.1.24 - 2006-09-29
15374 - Allow really slow clients to not hang up five minutes into their
15375 directory downloads (suggested by Adam J. Richter).
15376 - Fix major performance regression from 0.1.0.x: instead of checking
15377 whether we have enough directory information every time we want to
15378 do something, only check when the directory information has changed.
15379 This should improve client CPU usage by 25-50%.
15380 - Don't crash if, after a server has been running for a while,
15381 it can't resolve its hostname.
15384 - Allow Tor to start when RunAsDaemon is set but no logs are set.
15385 - Don't crash when the controller receives a third argument to an
15386 "extendcircuit" request.
15387 - Controller protocol fixes: fix encoding in "getinfo addr-mappings"
15388 response; fix error code when "getinfo dir/status/" fails.
15389 - Fix configure.in to not produce broken configure files with
15390 more recent versions of autoconf. Thanks to Clint for his auto*
15392 - Fix security bug on NetBSD that could allow someone to force
15393 uninitialized RAM to be sent to a server's DNS resolver. This
15394 only affects NetBSD and other platforms that do not bounds-check
15396 - Warn user when using libevent 1.1a or earlier with win32 or kqueue
15397 methods: these are known to be buggy.
15398 - If we're a directory mirror and we ask for "all" network status
15399 documents, we would discard status documents from authorities
15400 we don't recognize.
15403 Changes in version 0.1.2.1-alpha - 2006-08-27
15405 - Add "eventdns" async dns library from Adam Langley, tweaked to
15406 build on OSX and Windows. Only enabled if you pass the
15407 --enable-eventdns argument to configure.
15408 - Allow servers with no hostname or IP address to learn their
15409 IP address by asking the directory authorities. This code only
15410 kicks in when you would normally have exited with a "no address"
15411 error. Nothing's authenticated, so use with care.
15412 - Rather than waiting a fixed amount of time between retrying
15413 application connections, we wait only 5 seconds for the first,
15414 10 seconds for the second, and 15 seconds for each retry after
15415 that. Hopefully this will improve the expected user experience.
15416 - Patch from Tup to add support for transparent AP connections:
15417 this basically bundles the functionality of trans-proxy-tor
15418 into the Tor mainline. Now hosts with compliant pf/netfilter
15419 implementations can redirect TCP connections straight to Tor
15420 without diverting through SOCKS. Needs docs.
15421 - Busy directory servers save lots of memory by spooling server
15422 descriptors, v1 directories, and v2 networkstatus docs to buffers
15423 as needed rather than en masse. Also mmap the cached-routers
15424 files, so we don't need to keep the whole thing in memory too.
15425 - Automatically avoid picking more than one node from the same
15426 /16 network when constructing a circuit.
15427 - Revise and clean up the torrc.sample that we ship with; add
15428 a section for BandwidthRate and BandwidthBurst.
15431 - Split circuit_t into origin_circuit_t and or_circuit_t, and
15432 split connection_t into edge, or, dir, control, and base structs.
15433 These will save quite a bit of memory on busy servers, and they'll
15434 also help us track down bugs in the code and bugs in the spec.
15435 - Experimentally re-enable kqueue on OSX when using libevent 1.1b
15436 or later. Log when we are doing this, so we can diagnose it when
15437 it fails. (Also, recommend libevent 1.1b for kqueue and
15438 win32 methods; deprecate libevent 1.0b harder; make libevent
15439 recommendation system saner.)
15440 - Start being able to build universal binaries on OS X (thanks
15442 - Export the default exit policy via the control port, so controllers
15443 don't need to guess what it is / will be later.
15444 - Add a man page entry for ProtocolWarnings.
15445 - Add TestVia config option to the man page.
15446 - Remove even more protocol-related warnings from Tor server logs,
15447 such as bad TLS handshakes and malformed begin cells.
15448 - Stop fetching descriptors if you're not a dir mirror and you
15449 haven't tried to establish any circuits lately. [This currently
15450 causes some dangerous behavior, because when you start up again
15451 you'll use your ancient server descriptors.]
15452 - New DirPort behavior: if you have your dirport set, you download
15453 descriptors aggressively like a directory mirror, whether or not
15454 your ORPort is set.
15455 - Get rid of the router_retry_connections notion. Now routers
15456 no longer try to rebuild long-term connections to directory
15457 authorities, and directory authorities no longer try to rebuild
15458 long-term connections to all servers. We still don't hang up
15459 connections in these two cases though -- we need to look at it
15460 more carefully to avoid flapping, and we likely need to wait til
15461 0.1.1.x is obsolete.
15462 - Drop compatibility with obsolete Tors that permit create cells
15463 to have the wrong circ_id_type.
15464 - Re-enable per-connection rate limiting. Get rid of the "OP
15465 bandwidth" concept. Lay groundwork for "bandwidth classes" --
15466 separate global buckets that apply depending on what sort of conn
15468 - Start publishing one minute or so after we find our ORPort
15469 to be reachable. This will help reduce the number of descriptors
15470 we have for ourselves floating around, since it's quite likely
15471 other things (e.g. DirPort) will change during that minute too.
15472 - Fork the v1 directory protocol into its own spec document,
15473 and mark dir-spec.txt as the currently correct (v2) spec.
15476 - When we find our DirPort to be reachable, publish a new descriptor
15477 so we'll tell the world (reported by pnx).
15478 - Publish a new descriptor after we hup/reload. This is important
15479 if our config has changed such that we'll want to start advertising
15480 our DirPort now, etc.
15481 - Allow Tor to start when RunAsDaemon is set but no logs are set.
15482 - When we have a state file we cannot parse, tell the user and
15483 move it aside. Now we avoid situations where the user starts
15484 Tor in 1904, Tor writes a state file with that timestamp in it,
15485 the user fixes her clock, and Tor refuses to start.
15486 - Fix configure.in to not produce broken configure files with
15487 more recent versions of autoconf. Thanks to Clint for his auto*
15489 - "tor --verify-config" now exits with -1(255) or 0 depending on
15490 whether the config options are bad or good.
15491 - Resolve bug 321 when using dnsworkers: append a period to every
15492 address we resolve at the exit node, so that we do not accidentally
15493 pick up local addresses, and so that failing searches are retried
15494 in the resolver search domains. (This is already solved for
15495 eventdns.) (This breaks Blossom servers for now.)
15496 - If we are using an exit enclave and we can't connect, e.g. because
15497 its webserver is misconfigured to not listen on localhost, then
15498 back off and try connecting from somewhere else before we fail.
15501 - Start compiling on MinGW on Windows (patches from Mike Chiussi).
15502 - Start compiling on MSVC6 on Windows (patches from Frediano Ziglio).
15503 - Fix bug 314: Tor clients issued "unsafe socks" warnings even
15504 when the IP address is mapped through MapAddress to a hostname.
15505 - Start passing "ipv4" hints to getaddrinfo(), so servers don't do
15506 useless IPv6 DNS resolves.
15507 - Patch suggested by Karsten Loesing: respond to SIGNAL command
15508 before we execute the signal, in case the signal shuts us down.
15509 - Clean up AllowInvalidNodes man page entry.
15510 - Claim a commonname of Tor, rather than TOR, in TLS handshakes.
15511 - Add more asserts to track down an assert error on a windows Tor
15512 server with connection_add being called with socket == -1.
15513 - Handle reporting OR_CONN_EVENT_NEW events to the controller.
15514 - Fix misleading log messages: an entry guard that is "unlisted",
15515 as well as not known to be "down" (because we've never heard
15516 of it), is not therefore "up".
15517 - Remove code to special-case "-cvs" ending, since it has not
15518 actually mattered since 0.0.9.
15519 - Make our socks5 handling more robust to broken socks clients:
15520 throw out everything waiting on the buffer in between socks
15521 handshake phases, since they can't possibly (so the theory
15522 goes) have predicted what we plan to respond to them.
15525 Changes in version 0.1.1.23 - 2006-07-30
15527 - Fast Tor servers, especially exit nodes, were triggering asserts
15528 due to a bug in handling the list of pending DNS resolves. Some
15529 bugs still remain here; we're hunting them.
15530 - Entry guards could crash clients by sending unexpected input.
15531 - More fixes on reachability testing: if you find yourself reachable,
15532 then don't ever make any client requests (so you stop predicting
15533 circuits), then hup or have your clock jump, then later your IP
15534 changes, you won't think circuits are working, so you won't try to
15535 test reachability, so you won't publish.
15538 - Avoid a crash if the controller does a resetconf firewallports
15539 and then a setconf fascistfirewall=1.
15540 - Avoid an integer underflow when the dir authority decides whether
15541 a router is stable: we might wrongly label it stable, and compute
15542 a slightly wrong median stability, when a descriptor is published
15544 - Fix a place where we might trigger an assert if we can't build our
15545 own server descriptor yet.
15548 Changes in version 0.1.1.22 - 2006-07-05
15550 - Fix a big bug that was causing servers to not find themselves
15551 reachable if they changed IP addresses. Since only 0.1.1.22+
15552 servers can do reachability testing correctly, now we automatically
15553 make sure to test via one of these.
15554 - Fix to allow clients and mirrors to learn directory info from
15555 descriptor downloads that get cut off partway through.
15556 - Directory authorities had a bug in deciding if a newly published
15557 descriptor was novel enough to make everybody want a copy -- a few
15558 servers seem to be publishing new descriptors many times a minute.
15560 - Fix a rare bug that was causing some servers to complain about
15561 "closing wedged cpuworkers" and skip some circuit create requests.
15562 - Make the Exit flag in directory status documents actually work.
15565 Changes in version 0.1.1.21 - 2006-06-10
15566 o Crash and assert fixes from 0.1.1.20:
15567 - Fix a rare crash on Tor servers that have enabled hibernation.
15568 - Fix a seg fault on startup for Tor networks that use only one
15569 directory authority.
15570 - Fix an assert from a race condition that occurs on Tor servers
15571 while exiting, where various threads are trying to log that they're
15572 exiting, and delete the logs, at the same time.
15573 - Make our unit tests pass again on certain obscure platforms.
15576 - Add support for building SUSE RPM packages.
15577 - Speed up initial bootstrapping for clients: if we are making our
15578 first ever connection to any entry guard, then don't mark it down
15580 - When only one Tor server in the network is labelled as a guard,
15581 and we've already picked him, we would cycle endlessly picking him
15582 again, being unhappy about it, etc. Now we specifically exclude
15583 current guards when picking a new guard.
15584 - Servers send create cells more reliably after the TLS connection
15585 is established: we were sometimes forgetting to send half of them
15586 when we had more than one pending.
15587 - If we get a create cell that asks us to extend somewhere, but the
15588 Tor server there doesn't match the expected digest, we now send
15589 a destroy cell back, rather than silently doing nothing.
15590 - Make options->RedirectExit work again.
15591 - Make cookie authentication for the controller work again.
15592 - Stop being picky about unusual characters in the arguments to
15593 mapaddress. It's none of our business.
15594 - Add a new config option "TestVia" that lets you specify preferred
15595 middle hops to use for test circuits. Perhaps this will let me
15596 debug the reachability problems better.
15598 o Log / documentation fixes:
15599 - If we're a server and some peer has a broken TLS certificate, don't
15600 log about it unless ProtocolWarnings is set, i.e., we want to hear
15601 about protocol violations by others.
15602 - Fix spelling of VirtualAddrNetwork in man page.
15603 - Add a better explanation at the top of the autogenerated torrc file
15604 about what happened to our old torrc.
15607 Changes in version 0.1.1.20 - 2006-05-23
15609 - Downgrade a log severity where servers complain that they're
15611 - Avoid a compile warning on FreeBSD.
15612 - Remove string size limit on NEWDESC messages; solve bug 291.
15613 - Correct the RunAsDaemon entry in the man page; ignore RunAsDaemon
15614 more thoroughly when we're running on windows.
15617 Changes in version 0.1.1.19-rc - 2006-05-03
15619 - Regenerate our local descriptor if it's dirty and we try to use
15620 it locally (e.g. if it changes during reachability detection).
15621 - If we setconf our ORPort to 0, we continued to listen on the
15622 old ORPort and receive connections.
15623 - Avoid a second warning about machine/limits.h on Debian
15625 - Be willing to add our own routerinfo into the routerlist.
15626 Now authorities will include themselves in their directories
15627 and network-statuses.
15628 - Stop trying to upload rendezvous descriptors to every
15629 directory authority: only try the v1 authorities.
15630 - Servers no longer complain when they think they're not
15631 registered with the directory authorities. There were too many
15633 - Backport dist-rpm changes so rpms can be built without errors.
15636 - Implement an option, VirtualAddrMask, to set which addresses
15637 get handed out in response to mapaddress requests. This works
15638 around a bug in tsocks where 127.0.0.0/8 is never socksified.
15641 Changes in version 0.1.1.18-rc - 2006-04-10
15643 - Work harder to download live network-statuses from all the
15644 directory authorities we know about. Improve the threshold
15645 decision logic so we're more robust to edge cases.
15646 - When fetching rendezvous descriptors, we were willing to ask
15647 v2 authorities too, which would always return 404.
15650 - Stop listing down or invalid nodes in the v1 directory. This will
15651 reduce its bulk by about 1/3, and reduce load on directory
15653 - When deciding whether a router is Fast or Guard-worthy, consider
15654 his advertised BandwidthRate and not just the BandwidthCapacity.
15655 - No longer ship INSTALL and README files -- they are useless now.
15656 - Force rpmbuild to behave and honor target_cpu.
15657 - Avoid warnings about machine/limits.h on Debian GNU/kFreeBSD.
15658 - Start to include translated versions of the tor-doc-*.html
15659 files, along with the screenshots. Still needs more work.
15660 - Start sending back 512 and 451 errors if mapaddress fails,
15661 rather than not sending anything back at all.
15662 - When we fail to bind or listen on an incoming or outgoing
15663 socket, we should close it before failing. otherwise we just
15664 leak it. (thanks to weasel for finding.)
15665 - Allow "getinfo dir/status/foo" to work, as long as your DirPort
15666 is enabled. (This is a hack, and will be fixed in 0.1.2.x.)
15667 - Make NoPublish (even though deprecated) work again.
15668 - Fix a minor security flaw where a versioning auth dirserver
15669 could list a recommended version many times in a row to make
15670 clients more convinced that it's recommended.
15671 - Fix crash bug if there are two unregistered servers running
15672 with the same nickname, one of them is down, and you ask for
15673 them by nickname in your EntryNodes or ExitNodes. Also, try
15674 to pick the one that's running rather than an arbitrary one.
15675 - Fix an infinite loop we could hit if we go offline for too long.
15676 - Complain when we hit WSAENOBUFS on recv() or write() too.
15677 Perhaps this will help us hunt the bug.
15678 - If you're not a versioning dirserver, don't put the string
15679 "client-versions \nserver-versions \n" in your network-status.
15680 - Lower the minimum required number of file descriptors to 1000,
15681 so we can have some overhead for Valgrind on Linux, where the
15682 default ulimit -n is 1024.
15685 - Add tor.dizum.com as the fifth authoritative directory server.
15686 - Add a new config option FetchUselessDescriptors, off by default,
15687 for when you plan to run "exitlist" on your client and you want
15688 to know about even the non-running descriptors.
15691 Changes in version 0.1.1.17-rc - 2006-03-28
15693 - Clients and servers since 0.1.1.10-alpha have been expiring
15694 connections whenever they are idle for 5 minutes and they *do*
15695 have circuits on them. Oops. With this new version, clients will
15696 discard their previous entry guard choices and avoid choosing
15697 entry guards running these flawed versions.
15698 - Fix memory leak when uncompressing concatenated zlib streams. This
15699 was causing substantial leaks over time on Tor servers.
15700 - The v1 directory was including servers as much as 48 hours old,
15701 because that's how the new routerlist->routers works. Now only
15702 include them if they're 20 hours old or less.
15705 - Resume building on irix64, netbsd 2.0, etc.
15706 - On non-gcc compilers (e.g. solaris), use "-g -O" instead of
15708 - Stop writing the "router.desc" file, ever. Nothing uses it anymore,
15709 and it is confusing some users.
15710 - Mirrors stop caching the v1 directory so often.
15711 - Make the max number of old descriptors that a cache will hold
15712 rise with the number of directory authorities, so we can scale.
15713 - Change our win32 uname() hack to be more forgiving about what
15714 win32 versions it thinks it's found.
15717 - Add lefkada.eecs.harvard.edu as a fourth authoritative directory
15719 - When the controller's *setconf commands fail, collect an error
15720 message in a string and hand it back to the controller.
15721 - Make the v2 dir's "Fast" flag based on relative capacity, just
15722 like "Stable" is based on median uptime. Name everything in the
15723 top 7/8 Fast, and only the top 1/2 gets to be a Guard.
15724 - Log server fingerprint on startup, so new server operators don't
15725 have to go hunting around their filesystem for it.
15726 - Return a robots.txt on our dirport to discourage google indexing.
15727 - Let the controller ask for GETINFO dir/status/foo so it can ask
15728 directly rather than connecting to the dir port. Only works when
15729 dirport is set for now.
15731 o New config options rather than constants in the code:
15732 - SocksTimeout: How long do we let a socks connection wait
15733 unattached before we fail it?
15734 - CircuitBuildTimeout: Cull non-open circuits that were born
15735 at least this many seconds ago.
15736 - CircuitIdleTimeout: Cull open clean circuits that were born
15737 at least this many seconds ago.
15740 Changes in version 0.1.1.16-rc - 2006-03-18
15741 o Bugfixes on 0.1.1.15-rc:
15742 - Fix assert when the controller asks to attachstream a connect-wait
15743 or resolve-wait stream.
15744 - Now do address rewriting when the controller asks us to attach
15745 to a particular circuit too. This will let Blossom specify
15746 "moria2.exit" without having to learn what moria2's IP address is.
15747 - Make the "tor --verify-config" command-line work again, so people
15748 can automatically check if their torrc will parse.
15749 - Authoritative dirservers no longer require an open connection from
15750 a server to consider him "reachable". We need this change because
15751 when we add new auth dirservers, old servers won't know not to
15753 - Let Tor build on Sun CC again.
15754 - Fix an off-by-one buffer size in dirserv.c that magically never
15755 hit our three authorities but broke sjmurdoch's own tor network.
15756 - If we as a directory mirror don't know of any v1 directory
15757 authorities, then don't try to cache any v1 directories.
15758 - Stop warning about unknown servers in our family when they are
15759 given as hex digests.
15760 - Stop complaining as quickly to the server operator that he
15761 hasn't registered his nickname/key binding.
15762 - Various cleanups so we can add new V2 Auth Dirservers.
15763 - Change "AllowUnverifiedNodes" to "AllowInvalidNodes", to
15764 reflect the updated flags in our v2 dir protocol.
15765 - Resume allowing non-printable characters for exit streams (both
15766 for connecting and for resolving). Now we tolerate applications
15767 that don't follow the RFCs. But continue to block malformed names
15770 o Bugfixes on 0.1.0.x:
15771 - Fix assert bug in close_logs(): when we close and delete logs,
15772 remove them all from the global "logfiles" list.
15773 - Fix minor integer overflow in calculating when we expect to use up
15774 our bandwidth allocation before hibernating.
15775 - Fix a couple of bugs in OpenSSL detection. Also, deal better when
15776 there are multiple SSLs installed with different versions.
15777 - When we try to be a server and Address is not explicitly set and
15778 our hostname resolves to a private IP address, try to use an
15779 interface address if it has a public address. Now Windows machines
15780 that think of themselves as localhost can work by default.
15783 - Let the controller ask for GETINFO dir/server/foo so it can ask
15784 directly rather than connecting to the dir port.
15785 - Let the controller tell us about certain router descriptors
15786 that it doesn't want Tor to use in circuits. Implement
15787 SETROUTERPURPOSE and modify +POSTDESCRIPTOR to do this.
15788 - New config option SafeSocks to reject all application connections
15789 using unsafe socks protocols. Defaults to off.
15792 Changes in version 0.1.1.15-rc - 2006-03-11
15793 o Bugfixes and cleanups:
15794 - When we're printing strings from the network, don't try to print
15795 non-printable characters. This protects us against shell escape
15796 sequence exploits, and also against attacks to fool humans into
15797 misreading their logs.
15798 - Fix a bug where Tor would fail to establish any connections if you
15799 left it off for 24 hours and then started it: we were happy with
15800 the obsolete network statuses, but they all referred to router
15801 descriptors that were too old to fetch, so we ended up with no
15802 valid router descriptors.
15803 - Fix a seg fault in the controller's "getinfo orconn-status"
15804 command while listing status on incoming handshaking connections.
15805 Introduce a status name "NEW" for these connections.
15806 - If we get a linelist or linelist_s config option from the torrc
15807 (e.g. ExitPolicy) and it has no value, warn and skip rather than
15808 silently resetting it to its default.
15809 - Don't abandon entry guards until they've been down or gone for
15811 - Cleaner and quieter log messages.
15814 - New controller signal NEWNYM that makes new application requests
15815 use clean circuits.
15816 - Add a new circuit purpose 'controller' to let the controller ask
15817 for a circuit that Tor won't try to use. Extend the EXTENDCIRCUIT
15818 controller command to let you specify the purpose if you're
15819 starting a new circuit. Add a new SETCIRCUITPURPOSE controller
15820 command to let you change a circuit's purpose after it's been
15822 - Accept "private:*" in routerdesc exit policies; not generated yet
15823 because older Tors do not understand it.
15824 - Add BSD-style contributed startup script "rc.subr" from Peter
15828 Changes in version 0.1.1.14-alpha - 2006-02-20
15829 o Bugfixes on 0.1.1.x:
15830 - Don't die if we ask for a stdout or stderr log (even implicitly)
15831 and we're set to RunAsDaemon -- just warn.
15832 - We still had a few bugs in the OR connection rotation code that
15833 caused directory servers to slowly aggregate connections to other
15834 fast Tor servers. This time for sure!
15835 - Make log entries on Win32 include the name of the function again.
15836 - We were treating a pair of exit policies if they were equal even
15837 if one said accept and the other said reject -- causing us to
15838 not always publish a new descriptor since we thought nothing
15840 - Retry pending server downloads as well as pending networkstatus
15841 downloads when we unexpectedly get a socks request.
15842 - We were ignoring the IS_FAST flag in the directory status,
15843 meaning we were willing to pick trivial-bandwidth nodes for "fast"
15845 - If the controller's SAVECONF command fails (e.g. due to file
15846 permissions), let the controller know that it failed.
15849 - If we're trying to be a Tor server and running Windows 95/98/ME
15850 as a server, explain that we'll likely crash.
15851 - When we're a server, a client asks for an old-style directory,
15852 and our write bucket is empty, don't give it to him. This way
15853 small servers can continue to serve the directory *sometimes*,
15854 without getting overloaded.
15855 - Compress exit policies even more -- look for duplicate lines
15857 - Clients now honor the "guard" flag in the router status when
15858 picking entry guards, rather than looking at is_fast or is_stable.
15859 - Retain unrecognized lines in $DATADIR/state file, so that we can
15860 be forward-compatible.
15861 - Generate 18.0.0.0/8 address policy format in descs when we can;
15862 warn when the mask is not reducible to a bit-prefix.
15863 - Let the user set ControlListenAddress in the torrc. This can be
15864 dangerous, but there are some cases (like a secured LAN) where it
15866 - Split ReachableAddresses into ReachableDirAddresses and
15867 ReachableORAddresses, so we can restrict Dir conns to port 80
15868 and OR conns to port 443.
15869 - Now we can target arch and OS in rpm builds (contributed by
15870 Phobos). Also make the resulting dist-rpm filename match the
15872 - New config options to help controllers: FetchServerDescriptors
15873 and FetchHidServDescriptors for whether to fetch server
15874 info and hidserv info or let the controller do it, and
15875 PublishServerDescriptor and PublishHidServDescriptors.
15876 - Also let the controller set the __AllDirActionsPrivate config
15877 option if you want all directory fetches/publishes to happen via
15878 Tor (it assumes your controller bootstraps your circuits).
15881 Changes in version 0.1.0.17 - 2006-02-17
15882 o Crash bugfixes on 0.1.0.x:
15883 - When servers with a non-zero DirPort came out of hibernation,
15884 sometimes they would trigger an assert.
15886 o Other important bugfixes:
15887 - On platforms that don't have getrlimit (like Windows), we were
15888 artificially constraining ourselves to a max of 1024
15889 connections. Now just assume that we can handle as many as 15000
15890 connections. Hopefully this won't cause other problems.
15892 o Backported features:
15893 - When we're a server, a client asks for an old-style directory,
15894 and our write bucket is empty, don't give it to him. This way
15895 small servers can continue to serve the directory *sometimes*,
15896 without getting overloaded.
15897 - Whenever you get a 503 in response to a directory fetch, try
15898 once more. This will become important once servers start sending
15899 503's whenever they feel busy.
15900 - Fetch a new directory every 120 minutes, not every 40 minutes.
15901 Now that we have hundreds of thousands of users running the old
15902 directory algorithm, it's starting to hurt a lot.
15903 - Bump up the period for forcing a hidden service descriptor upload
15904 from 20 minutes to 1 hour.
15907 Changes in version 0.1.1.13-alpha - 2006-02-09
15908 o Crashes in 0.1.1.x:
15909 - When you tried to setconf ORPort via the controller, Tor would
15910 crash. So people using TorCP to become a server were sad.
15911 - Solve (I hope) the stack-smashing bug that we were seeing on fast
15912 servers. The problem appears to be something do with OpenSSL's
15913 random number generation, or how we call it, or something. Let me
15914 know if the crashes continue.
15915 - Turn crypto hardware acceleration off by default, until we find
15916 somebody smart who can test it for us. (It appears to produce
15917 seg faults in at least some cases.)
15918 - Fix a rare assert error when we've tried all intro points for
15919 a hidden service and we try fetching the service descriptor again:
15920 "Assertion conn->state != AP_CONN_STATE_RENDDESC_WAIT failed"
15923 - Fix a major load balance bug: we were round-robining in 16 KB
15924 chunks, and servers with bandwidthrate of 20 KB, while downloading
15925 a 600 KB directory, would starve their other connections. Now we
15926 try to be a bit more fair.
15927 - Dir authorities and mirrors were never expiring the newest
15928 descriptor for each server, causing memory and directory bloat.
15929 - Fix memory-bloating and connection-bloating bug on servers: We
15930 were never closing any connection that had ever had a circuit on
15931 it, because we were checking conn->n_circuits == 0, yet we had a
15932 bug that let it go negative.
15933 - Make Tor work using squid as your http proxy again -- squid
15934 returns an error if you ask for a URL that's too long, and it uses
15935 a really generic error message. Plus, many people are behind a
15936 transparent squid so they don't even realize it.
15937 - On platforms that don't have getrlimit (like Windows), we were
15938 artificially constraining ourselves to a max of 1024
15939 connections. Now just assume that we can handle as many as 15000
15940 connections. Hopefully this won't cause other problems.
15941 - Add a new config option ExitPolicyRejectPrivate which defaults to
15942 1. This means all exit policies will begin with rejecting private
15943 addresses, unless the server operator explicitly turns it off.
15946 - Clients no longer download descriptors for non-running
15948 - Before we add new directory authorities, we should make it
15949 clear that only v1 authorities should receive/publish hidden
15950 service descriptors.
15953 - As soon as we've fetched some more directory info, immediately
15954 try to download more server descriptors. This way we don't have
15955 a 10 second pause during initial bootstrapping.
15956 - Remove even more loud log messages that the server operator can't
15958 - When we're running an obsolete or un-recommended version, make
15959 the log message more clear about what the problem is and what
15960 versions *are* still recommended.
15961 - Provide a more useful warn message when our onion queue gets full:
15962 the CPU is too slow or the exit policy is too liberal.
15963 - Don't warn when we receive a 503 from a dirserver/cache -- this
15964 will pave the way for them being able to refuse if they're busy.
15965 - When we fail to bind a listener, try to provide a more useful
15966 log message: e.g., "Is Tor already running?"
15967 - Adjust tor-spec to parameterize cell and key lengths. Now Ian
15968 Goldberg can prove things about our handshake protocol more
15970 - MaxConn has been obsolete for a while now. Document the ConnLimit
15971 config option, which is a *minimum* number of file descriptors
15972 that must be available else Tor refuses to start.
15973 - Apply Matt Ghali's --with-syslog-facility patch to ./configure
15974 if you log to syslog and want something other than LOG_DAEMON.
15975 - Make dirservers generate a separate "guard" flag to mean,
15976 "would make a good entry guard". Make clients parse it and vote
15977 on it. Not used by clients yet.
15978 - Implement --with-libevent-dir option to ./configure. Also, improve
15979 search techniques to find libevent, and use those for openssl too.
15980 - Bump the default bandwidthrate to 3 MB, and burst to 6 MB
15981 - Only start testing reachability once we've established a
15982 circuit. This will make startup on dirservers less noisy.
15983 - Don't try to upload hidden service descriptors until we have
15984 established a circuit.
15985 - Fix the controller's "attachstream 0" command to treat conn like
15986 it just connected, doing address remapping, handling .exit and
15987 .onion idioms, and so on. Now we're more uniform in making sure
15988 that the controller hears about new and closing connections.
15991 Changes in version 0.1.1.12-alpha - 2006-01-11
15992 o Bugfixes on 0.1.1.x:
15993 - The fix to close duplicate server connections was closing all
15994 Tor client connections if they didn't establish a circuit
15995 quickly enough. Oops.
15996 - Fix minor memory issue (double-free) that happened on exit.
15998 o Bugfixes on 0.1.0.x:
15999 - Tor didn't warn when it failed to open a log file.
16002 Changes in version 0.1.1.11-alpha - 2006-01-10
16003 o Crashes in 0.1.1.x:
16004 - Include all the assert/crash fixes from 0.1.0.16.
16005 - If you start Tor and then quit very quickly, there were some
16006 races that tried to free things that weren't allocated yet.
16007 - Fix a rare memory stomp if you're running hidden services.
16008 - Fix segfault when specifying DirServer in config without nickname.
16009 - Fix a seg fault when you finish connecting to a server but at
16010 that moment you dump his server descriptor.
16011 - Extendcircuit and Attachstream controller commands would
16012 assert/crash if you don't give them enough arguments.
16013 - Fix an assert error when we're out of space in the connection_list
16014 and we try to post a hidden service descriptor (reported by weasel).
16015 - If you specify a relative torrc path and you set RunAsDaemon in
16016 your torrc, then it chdir()'s to the new directory. If you HUP,
16017 it tries to load the new torrc location, fails, and exits.
16018 The fix: no longer allow a relative path to torrc using -f.
16021 - Implement "entry guards": automatically choose a handful of entry
16022 nodes and stick with them for all circuits. Only pick new guards
16023 when the ones you have are unsuitable, and if the old guards
16024 become suitable again, switch back. This will increase security
16025 dramatically against certain end-point attacks. The EntryNodes
16026 config option now provides some hints about which entry guards you
16027 want to use most; and StrictEntryNodes means to only use those.
16028 - New directory logic: download by descriptor digest, not by
16029 fingerprint. Caches try to download all listed digests from
16030 authorities; clients try to download "best" digests from caches.
16031 This avoids partitioning and isolating attacks better.
16032 - Make the "stable" router flag in network-status be the median of
16033 the uptimes of running valid servers, and make clients pay
16034 attention to the network-status flags. Thus the cutoff adapts
16035 to the stability of the network as a whole, making IRC, IM, etc
16036 connections more reliable.
16039 - Tor servers with dynamic IP addresses were needing to wait 18
16040 hours before they could start doing reachability testing using
16041 the new IP address and ports. This is because they were using
16042 the internal descriptor to learn what to test, yet they were only
16043 rebuilding the descriptor once they decided they were reachable.
16044 - Tor 0.1.1.9 and 0.1.1.10 had a serious bug that caused clients
16045 to download certain server descriptors, throw them away, and then
16046 fetch them again after 30 minutes. Now mirrors throw away these
16047 server descriptors so clients can't get them.
16048 - We were leaving duplicate connections to other ORs open for a week,
16049 rather than closing them once we detect a duplicate. This only
16050 really affected authdirservers, but it affected them a lot.
16051 - Spread the authdirservers' reachability testing over the entire
16052 testing interval, so we don't try to do 500 TLS's at once every
16056 - If the network is down, and we try to connect to a conn because
16057 we have a circuit in mind, and we timeout (30 seconds) because the
16058 network never answers, we were expiring the circuit, but we weren't
16059 obsoleting the connection or telling the entry_guards functions.
16060 - Some Tor servers process billions of cells per day. These statistics
16061 need to be uint64_t's.
16062 - Check for integer overflows in more places, when adding elements
16063 to smartlists. This could possibly prevent a buffer overflow
16064 on malicious huge inputs. I don't see any, but I haven't looked
16066 - ReachableAddresses kept growing new "reject *:*" lines on every
16068 - When you "setconf log" via the controller, it should remove all
16069 logs. We were automatically adding back in a "log notice stdout".
16070 - Newly bootstrapped Tor networks couldn't establish hidden service
16071 circuits until they had nodes with high uptime. Be more tolerant.
16072 - We were marking servers down when they could not answer every piece
16073 of the directory request we sent them. This was far too harsh.
16074 - Fix the torify (tsocks) config file to not use Tor for localhost
16076 - Directory authorities now go to the proper authority when asking for
16077 a networkstatus, even when they want a compressed one.
16078 - Fix a harmless bug that was causing Tor servers to log
16079 "Got an end because of misc error, but we're not an AP. Closing."
16080 - Authorities were treating their own descriptor changes as cosmetic,
16081 meaning the descriptor available in the network-status and the
16082 descriptor that clients downloaded were different.
16083 - The OS X installer was adding a symlink for tor_resolve but
16084 the binary was called tor-resolve (reported by Thomas Hardly).
16085 - Workaround a problem with some http proxies where they refuse GET
16086 requests that specify "Content-Length: 0" (reported by Adrian).
16087 - Fix wrong log message when you add a "HiddenServiceNodes" config
16088 line without any HiddenServiceDir line (reported by Chris Thomas).
16091 - Write the TorVersion into the state file so we have a prayer of
16092 keeping forward and backward compatibility.
16093 - Revive the FascistFirewall config option rather than eliminating it:
16094 now it's a synonym for ReachableAddresses *:80,*:443.
16095 - Clients choose directory servers from the network status lists,
16096 not from their internal list of router descriptors. Now they can
16097 go to caches directly rather than needing to go to authorities
16099 - Directory authorities ignore router descriptors that have only
16100 cosmetic differences: do this for 0.1.0.x servers now too.
16101 - Add a new flag to network-status indicating whether the server
16102 can answer v2 directory requests too.
16103 - Authdirs now stop whining so loudly about bad descriptors that
16104 they fetch from other dirservers. So when there's a log complaint,
16105 it's for sure from a freshly uploaded descriptor.
16106 - Reduce memory requirements in our structs by changing the order
16108 - There used to be two ways to specify your listening ports in a
16109 server descriptor: on the "router" line and with a separate "ports"
16110 line. Remove support for the "ports" line.
16111 - New config option "AuthDirRejectUnlisted" for auth dirservers as
16112 a panic button: if we get flooded with unusable servers we can
16113 revert to only listing servers in the approved-routers file.
16114 - Auth dir servers can now mark a fingerprint as "!reject" or
16115 "!invalid" in the approved-routers file (as its nickname), to
16116 refuse descriptors outright or include them but marked as invalid.
16117 - Servers store bandwidth history across restarts/crashes.
16118 - Add reasons to DESTROY and RELAY_TRUNCATED cells, so clients can
16119 get a better idea of why their circuits failed. Not used yet.
16120 - Directory mirrors now cache up to 16 unrecognized network-status
16121 docs. Now we can add new authdirservers and they'll be cached too.
16122 - When picking a random directory, prefer non-authorities if any
16124 - New controller option "getinfo desc/all-recent" to fetch the
16125 latest server descriptor for every router that Tor knows about.
16128 Changes in version 0.1.0.16 - 2006-01-02
16129 o Crash bugfixes on 0.1.0.x:
16130 - On Windows, build with a libevent patch from "I-M Weasel" to avoid
16131 corrupting the heap, losing FDs, or crashing when we need to resize
16132 the fd_sets. (This affects the Win32 binaries, not Tor's sources.)
16133 - It turns out sparc64 platforms crash on unaligned memory access
16134 too -- so detect and avoid this.
16135 - Handle truncated compressed data correctly (by detecting it and
16137 - Fix possible-but-unlikely free(NULL) in control.c.
16138 - When we were closing connections, there was a rare case that
16139 stomped on memory, triggering seg faults and asserts.
16140 - Avoid potential infinite recursion when building a descriptor. (We
16141 don't know that it ever happened, but better to fix it anyway.)
16142 - We were neglecting to unlink marked circuits from soon-to-close OR
16143 connections, which caused some rare scribbling on freed memory.
16144 - Fix a memory stomping race bug when closing the joining point of two
16145 rendezvous circuits.
16146 - Fix an assert in time parsing found by Steven Murdoch.
16148 o Other bugfixes on 0.1.0.x:
16149 - When we're doing reachability testing, provide more useful log
16150 messages so the operator knows what to expect.
16151 - Do not check whether DirPort is reachable when we are suppressing
16152 advertising it because of hibernation.
16153 - When building with -static or on Solaris, we sometimes needed -ldl.
16154 - When we're deciding whether a stream has enough circuits around
16155 that can handle it, count the freshly dirty ones and not the ones
16156 that are so dirty they won't be able to handle it.
16157 - When we're expiring old circuits, we had a logic error that caused
16158 us to close new rendezvous circuits rather than old ones.
16159 - Give a more helpful log message when you try to change ORPort via
16160 the controller: you should upgrade Tor if you want that to work.
16161 - We were failing to parse Tor versions that start with "Tor ".
16162 - Tolerate faulty streams better: when a stream fails for reason
16163 exitpolicy, stop assuming that the router is lying about his exit
16164 policy. When a stream fails for reason misc, allow it to retry just
16165 as if it was resolvefailed. When a stream has failed three times,
16166 reset its failure count so we can try again and get all three tries.
16169 Changes in version 0.1.1.10-alpha - 2005-12-11
16170 o Correctness bugfixes on 0.1.0.x:
16171 - On Windows, build with a libevent patch from "I-M Weasel" to avoid
16172 corrupting the heap, losing FDs, or crashing when we need to resize
16173 the fd_sets. (This affects the Win32 binaries, not Tor's sources.)
16174 - Stop doing the complex voodoo overkill checking for insecure
16175 Diffie-Hellman keys. Just check if it's in [2,p-2] and be happy.
16176 - When we were closing connections, there was a rare case that
16177 stomped on memory, triggering seg faults and asserts.
16178 - We were neglecting to unlink marked circuits from soon-to-close OR
16179 connections, which caused some rare scribbling on freed memory.
16180 - When we're deciding whether a stream has enough circuits around
16181 that can handle it, count the freshly dirty ones and not the ones
16182 that are so dirty they won't be able to handle it.
16183 - Recover better from TCP connections to Tor servers that are
16184 broken but don't tell you (it happens!); and rotate TLS
16185 connections once a week.
16186 - When we're expiring old circuits, we had a logic error that caused
16187 us to close new rendezvous circuits rather than old ones.
16188 - Fix a scary-looking but apparently harmless bug where circuits
16189 would sometimes start out in state CIRCUIT_STATE_OR_WAIT at
16190 servers, and never switch to state CIRCUIT_STATE_OPEN.
16191 - When building with -static or on Solaris, we sometimes needed to
16193 - Give a useful message when people run Tor as the wrong user,
16194 rather than telling them to start chowning random directories.
16195 - We were failing to inform the controller about new .onion streams.
16197 o Security bugfixes on 0.1.0.x:
16198 - Refuse server descriptors if the fingerprint line doesn't match
16199 the included identity key. Tor doesn't care, but other apps (and
16200 humans) might actually be trusting the fingerprint line.
16201 - We used to kill the circuit when we receive a relay command we
16202 don't recognize. Now we just drop it.
16203 - Start obeying our firewall options more rigorously:
16204 . If we can't get to a dirserver directly, try going via Tor.
16205 . Don't ever try to connect (as a client) to a place our
16206 firewall options forbid.
16207 . If we specify a proxy and also firewall options, obey the
16208 firewall options even when we're using the proxy: some proxies
16209 can only proxy to certain destinations.
16210 - Fix a bug found by Lasse Overlier: when we were making internal
16211 circuits (intended to be cannibalized later for rendezvous and
16212 introduction circuits), we were picking them so that they had
16213 useful exit nodes. There was no need for this, and it actually
16214 aids some statistical attacks.
16215 - Start treating internal circuits and exit circuits separately.
16216 It's important to keep them separate because internal circuits
16217 have their last hops picked like middle hops, rather than like
16218 exit hops. So exiting on them will break the user's expectations.
16220 o Bugfixes on 0.1.1.x:
16221 - Take out the mis-feature where we tried to detect IP address
16222 flapping for people with DynDNS, and chose not to upload a new
16223 server descriptor sometimes.
16224 - Try to be compatible with OpenSSL 0.9.6 again.
16225 - Log fix: when the controller is logging about .onion addresses,
16226 sometimes it didn't include the ".onion" part of the address.
16227 - Don't try to modify options->DirServers internally -- if the
16228 user didn't specify any, just add the default ones directly to
16229 the trusted dirserver list. This fixes a bug where people running
16230 controllers would use SETCONF on some totally unrelated config
16231 option, and Tor would start yelling at them about changing their
16233 - Let the controller's redirectstream command specify a port, in
16234 case the controller wants to change that too.
16235 - When we requested a pile of server descriptors, we sometimes
16236 accidentally launched a duplicate request for the first one.
16237 - Bugfix for trackhostexits: write down the fingerprint of the
16238 chosen exit, not its nickname, because the chosen exit might not
16240 - When parsing foo.exit, if foo is unknown, and we are leaving
16241 circuits unattached, set the chosen_exit field and leave the
16242 address empty. This matters because controllers got confused
16244 - Directory authorities no longer try to download server
16245 descriptors that they know they will reject.
16247 o Features and updates:
16248 - Replace balanced trees with hash tables: this should make stuff
16249 significantly faster.
16250 - Resume using the AES counter-mode implementation that we ship,
16251 rather than OpenSSL's. Ours is significantly faster.
16252 - Many other CPU and memory improvements.
16253 - Add a new config option FastFirstHopPK (on by default) so clients
16254 do a trivial crypto handshake for their first hop, since TLS has
16255 already taken care of confidentiality and authentication.
16256 - Add a new config option TestSocks so people can see if their
16257 applications are using socks4, socks4a, socks5-with-ip, or
16258 socks5-with-hostname. This way they don't have to keep mucking
16259 with tcpdump and wondering if something got cached somewhere.
16260 - Warn when listening on a public address for socks. I suspect a
16261 lot of people are setting themselves up as open socks proxies,
16262 and they have no idea that jerks on the Internet are using them,
16263 since they simply proxy the traffic into the Tor network.
16264 - Add "private:*" as an alias in configuration for policies. Now
16265 you can simplify your exit policy rather than needing to list
16266 every single internal or nonroutable network space.
16267 - Add a new controller event type that allows controllers to get
16268 all server descriptors that were uploaded to a router in its role
16269 as authoritative dirserver.
16270 - Start shipping socks-extensions.txt, tor-doc-unix.html,
16271 tor-doc-server.html, and stylesheet.css in the tarball.
16272 - Stop shipping tor-doc.html in the tarball.
16275 Changes in version 0.1.1.9-alpha - 2005-11-15
16276 o Usability improvements:
16277 - Start calling it FooListenAddress rather than FooBindAddress,
16278 since few of our users know what it means to bind an address
16280 - Reduce clutter in server logs. We're going to try to make
16281 them actually usable now. New config option ProtocolWarnings that
16282 lets you hear about how _other Tors_ are breaking the protocol. Off
16284 - Divide log messages into logging domains. Once we put some sort
16285 of interface on this, it will let people looking at more verbose
16286 log levels specify the topics they want to hear more about.
16287 - Make directory servers return better http 404 error messages
16288 instead of a generic "Servers unavailable".
16289 - Check for even more Windows version flags when writing the platform
16290 string in server descriptors, and note any we don't recognize.
16291 - Clean up more of the OpenSSL memory when exiting, so we can detect
16292 memory leaks better.
16293 - Make directory authorities be non-versioning, non-naming by
16294 default. Now we can add new directory servers without requiring
16295 their operators to pay close attention.
16296 - When logging via syslog, include the pid whenever we provide
16297 a log entry. Suggested by Todd Fries.
16299 o Performance improvements:
16300 - Directory servers now silently throw away new descriptors that
16301 haven't changed much if the timestamps are similar. We do this to
16302 tolerate older Tor servers that upload a new descriptor every 15
16303 minutes. (It seemed like a good idea at the time.)
16304 - Inline bottleneck smartlist functions; use fast versions by default.
16305 - Add a "Map from digest to void*" abstraction digestmap_t so we
16306 can do less hex encoding/decoding. Use it in router_get_by_digest()
16307 to resolve a performance bottleneck.
16308 - Allow tor_gzip_uncompress to extract as much as possible from
16309 truncated compressed data. Try to extract as many
16310 descriptors as possible from truncated http responses (when
16311 DIR_PURPOSE_FETCH_ROUTERDESC).
16312 - Make circ->onionskin a pointer, not a static array. moria2 was using
16313 125000 circuit_t's after it had been up for a few weeks, which
16314 translates to 20+ megs of wasted space.
16315 - The private half of our EDH handshake keys are now chosen out
16316 of 320 bits, not 1024 bits. (Suggested by Ian Goldberg.)
16318 o Security improvements:
16319 - Start making directory caches retain old routerinfos, so soon
16320 clients can start asking by digest of descriptor rather than by
16321 fingerprint of server.
16322 - Add half our entropy from RAND_poll in OpenSSL. This knows how
16323 to use egd (if present), openbsd weirdness (if present), vms/os2
16324 weirdness (if we ever port there), and more in the future.
16326 o Bugfixes on 0.1.0.x:
16327 - Do round-robin writes of at most 16 kB per write. This might be
16328 more fair on loaded Tor servers, and it might resolve our Windows
16329 crash bug. It might also slow things down.
16330 - Our TLS handshakes were generating a single public/private
16331 keypair for the TLS context, rather than making a new one for
16332 each new connections. Oops. (But we were still rotating them
16333 periodically, so it's not so bad.)
16334 - When we were cannibalizing a circuit with a particular exit
16335 node in mind, we weren't checking to see if that exit node was
16336 already present earlier in the circuit. Oops.
16337 - When a Tor server's IP changes (e.g. from a dyndns address),
16338 upload a new descriptor so clients will learn too.
16339 - Really busy servers were keeping enough circuits open on stable
16340 connections that they were wrapping around the circuit_id
16341 space. (It's only two bytes.) This exposed a bug where we would
16342 feel free to reuse a circuit_id even if it still exists but has
16343 been marked for close. Try to fix this bug. Some bug remains.
16344 - If we would close a stream early (e.g. it asks for a .exit that
16345 we know would refuse it) but the LeaveStreamsUnattached config
16346 option is set by the controller, then don't close it.
16348 o Bugfixes on 0.1.1.8-alpha:
16349 - Fix a big pile of memory leaks, some of them serious.
16350 - Do not try to download a routerdesc if we would immediately reject
16352 - Resume inserting a newline between all router descriptors when
16353 generating (old style) signed directories, since our spec says
16355 - When providing content-type application/octet-stream for
16356 server descriptors using .z, we were leaving out the
16357 content-encoding header. Oops. (Everything tolerated this just
16358 fine, but that doesn't mean we need to be part of the problem.)
16359 - Fix a potential seg fault in getconf and getinfo using version 1
16360 of the controller protocol.
16361 - Avoid crash: do not check whether DirPort is reachable when we
16362 are suppressing it because of hibernation.
16363 - Make --hash-password not crash on exit.
16366 Changes in version 0.1.1.8-alpha - 2005-10-07
16367 o New features (major):
16368 - Clients don't download or use the directory anymore. Now they
16369 download and use network-statuses from the trusted dirservers,
16370 and fetch individual server descriptors as needed from mirrors.
16371 See dir-spec.txt for all the gory details.
16372 - Be more conservative about whether to advertise our DirPort.
16373 The main change is to not advertise if we're running at capacity
16374 and either a) we could hibernate or b) our capacity is low and
16375 we're using a default DirPort.
16376 - Use OpenSSL's AES when OpenSSL has version 0.9.7 or later.
16378 o New features (minor):
16379 - Try to be smart about when to retry network-status and
16380 server-descriptor fetches. Still needs some tuning.
16381 - Stop parsing, storing, or using running-routers output (but
16382 mirrors still cache and serve it).
16383 - Consider a threshold of versioning dirservers (dirservers who have
16384 an opinion about which Tor versions are still recommended) before
16385 deciding whether to warn the user that he's obsolete.
16386 - Dirservers can now reject/invalidate by key and IP, with the
16387 config options "AuthDirInvalid" and "AuthDirReject". This is
16388 useful since currently we automatically list servers as running
16389 and usable even if we know they're jerks.
16390 - Provide dire warnings to any users who set DirServer; move it out
16391 of torrc.sample and into torrc.complete.
16392 - Add MyFamily to torrc.sample in the server section.
16393 - Add nicknames to the DirServer line, so we can refer to them
16394 without requiring all our users to memorize their IP addresses.
16395 - When we get an EOF or a timeout on a directory connection, note
16396 how many bytes of serverdesc we are dropping. This will help
16397 us determine whether it is smart to parse incomplete serverdesc
16399 - Add a new function to "change pseudonyms" -- that is, to stop
16400 using any currently-dirty circuits for new streams, so we don't
16401 link new actions to old actions. Currently it's only called on
16402 HUP (or SIGNAL RELOAD).
16403 - On sighup, if UseHelperNodes changed to 1, use new circuits.
16404 - Start using RAND_bytes rather than RAND_pseudo_bytes from
16405 OpenSSL. Also, reseed our entropy every hour, not just at
16406 startup. And entropy in 512-bit chunks, not 160-bit chunks.
16408 o Fixes on 0.1.1.7-alpha:
16409 - Nobody ever implemented EVENT_ADDRMAP for control protocol
16410 version 0, so don't let version 0 controllers ask for it.
16411 - If you requested something with too many newlines via the
16412 v1 controller protocol, you could crash tor.
16413 - Fix a number of memory leaks, including some pretty serious ones.
16414 - Re-enable DirPort testing again, so Tor servers will be willing
16415 to advertise their DirPort if it's reachable.
16416 - On TLS handshake, only check the other router's nickname against
16417 its expected nickname if is_named is set.
16419 o Fixes forward-ported from 0.1.0.15:
16420 - Don't crash when we don't have any spare file descriptors and we
16421 try to spawn a dns or cpu worker.
16422 - Make the numbers in read-history and write-history into uint64s,
16423 so they don't overflow and publish negatives in the descriptor.
16425 o Fixes on 0.1.0.x:
16426 - For the OS X package's modified privoxy config file, comment
16427 out the "logfile" line so we don't log everything passed
16429 - We were whining about using socks4 or socks5-with-local-lookup
16430 even when it's an IP in the "virtual" range we designed exactly
16432 - We were leaking some memory every time the client changes IPs.
16433 - Never call free() on tor_malloc()d memory. This will help us
16434 use dmalloc to detect memory leaks.
16435 - Check for named servers when looking them up by nickname;
16436 warn when we'recalling a non-named server by its nickname;
16437 don't warn twice about the same name.
16438 - Try to list MyFamily elements by key, not by nickname, and warn
16439 if we've not heard of the server.
16440 - Make windows platform detection (uname equivalent) smarter.
16441 - It turns out sparc64 doesn't like unaligned access either.
16444 Changes in version 0.1.0.15 - 2005-09-23
16445 o Bugfixes on 0.1.0.x:
16446 - Reject ports 465 and 587 (spam targets) in default exit policy.
16447 - Don't crash when we don't have any spare file descriptors and we
16448 try to spawn a dns or cpu worker.
16449 - Get rid of IgnoreVersion undocumented config option, and make us
16450 only warn, never exit, when we're running an obsolete version.
16451 - Don't try to print a null string when your server finds itself to
16452 be unreachable and the Address config option is empty.
16453 - Make the numbers in read-history and write-history into uint64s,
16454 so they don't overflow and publish negatives in the descriptor.
16455 - Fix a minor memory leak in smartlist_string_remove().
16456 - We were only allowing ourselves to upload a server descriptor at
16457 most every 20 minutes, even if it changed earlier than that.
16458 - Clean up log entries that pointed to old URLs.
16461 Changes in version 0.1.1.7-alpha - 2005-09-14
16462 o Fixes on 0.1.1.6-alpha:
16463 - Exit servers were crashing when people asked them to make a
16464 connection to an address not in their exit policy.
16465 - Looking up a non-existent stream for a v1 control connection would
16467 - Fix a seg fault if we ask a dirserver for a descriptor by
16468 fingerprint but he doesn't know about him.
16469 - SETCONF was appending items to linelists, not clearing them.
16470 - SETCONF SocksBindAddress killed Tor if it fails to bind. Now back
16471 out and refuse the setconf if it would fail.
16472 - Downgrade the dirserver log messages when whining about
16476 - Add Peter Palfrader's check-tor script to tor/contrib/
16477 It lets you easily check whether a given server (referenced by
16478 nickname) is reachable by you.
16479 - Numerous changes to move towards client-side v2 directories. Not
16482 o Fixes on 0.1.0.x:
16483 - If the user gave tor an odd number of command-line arguments,
16484 we were silently ignoring the last one. Now we complain and fail.
16485 [This wins the oldest-bug prize -- this bug has been present since
16486 November 2002, as released in Tor 0.0.0.]
16487 - Do not use unaligned memory access on alpha, mips, or mipsel.
16488 It *works*, but is very slow, so we treat them as if it doesn't.
16489 - Retry directory requests if we fail to get an answer we like
16490 from a given dirserver (we were retrying before, but only if
16491 we fail to connect).
16492 - When writing the RecommendedVersions line, sort them first.
16493 - When the client asked for a rendezvous port that the hidden
16494 service didn't want to provide, we were sending an IP address
16495 back along with the end cell. Fortunately, it was zero. But stop
16497 - Correct "your server is reachable" log entries to indicate that
16498 it was self-testing that told us so.
16501 Changes in version 0.1.1.6-alpha - 2005-09-09
16502 o Fixes on 0.1.1.5-alpha:
16503 - We broke fascistfirewall in 0.1.1.5-alpha. Oops.
16504 - Fix segfault in unit tests in 0.1.1.5-alpha. Oops.
16505 - Fix bug with tor_memmem finding a match at the end of the string.
16506 - Make unit tests run without segfaulting.
16507 - Resolve some solaris x86 compile warnings.
16508 - Handle duplicate lines in approved-routers files without warning.
16509 - Fix bug where as soon as a server refused any requests due to his
16510 exit policy (e.g. when we ask for localhost and he tells us that's
16511 127.0.0.1 and he won't do it), we decided he wasn't obeying his
16512 exit policy using him for any exits.
16513 - Only do openssl hardware accelerator stuff if openssl version is
16516 o New controller features/fixes:
16517 - Add a "RESETCONF" command so you can set config options like
16518 AllowUnverifiedNodes and LongLivedPorts to "". Also, if you give
16519 a config option in the torrc with no value, then it clears it
16520 entirely (rather than setting it to its default).
16521 - Add a "GETINFO config-file" to tell us where torrc is.
16522 - Avoid sending blank lines when GETINFO replies should be empty.
16523 - Add a QUIT command for the controller (for using it manually).
16524 - Fix a bug in SAVECONF that was adding default dirservers and
16525 other redundant entries to the torrc file.
16527 o Start on the new directory design:
16528 - Generate, publish, cache, serve new network-status format.
16529 - Publish individual descriptors (by fingerprint, by "all", and by
16531 - Publish client and server recommended versions separately.
16532 - Allow tor_gzip_uncompress() to handle multiple concatenated
16533 compressed strings. Serve compressed groups of router
16534 descriptors. The compression logic here could be more
16536 - Distinguish v1 authorities (all currently trusted directories)
16537 from v2 authorities (all trusted directories).
16538 - Change DirServers config line to note which dirs are v1 authorities.
16539 - Add configuration option "V1AuthoritativeDirectory 1" which
16540 moria1, moria2, and tor26 should set.
16541 - Remove option when getting directory cache to see whether they
16542 support running-routers; they all do now. Replace it with one
16543 to see whether caches support v2 stuff.
16546 - Dirservers now do their own external reachability testing of each
16547 Tor server, and only list them as running if they've been found to
16548 be reachable. We also send back warnings to the server's logs if
16549 it uploads a descriptor that we already believe is unreachable.
16550 - Implement exit enclaves: if we know an IP address for the
16551 destination, and there's a running Tor server at that address
16552 which allows exit to the destination, then extend the circuit to
16553 that exit first. This provides end-to-end encryption and end-to-end
16554 authentication. Also, if the user wants a .exit address or enclave,
16555 use 4 hops rather than 3, and cannibalize a general circ for it
16557 - Permit transitioning from ORPort=0 to ORPort!=0, and back, from the
16558 controller. Also, rotate dns and cpu workers if the controller
16559 changes options that will affect them; and initialize the dns
16560 worker cache tree whether or not we start out as a server.
16561 - Only upload a new server descriptor when options change, 18
16562 hours have passed, uptime is reset, or bandwidth changes a lot.
16563 - Check [X-]Forwarded-For headers in HTTP requests when generating
16564 log messages. This lets people run dirservers (and caches) behind
16565 Apache but still know which IP addresses are causing warnings.
16567 o Config option changes:
16568 - Replace (Fascist)Firewall* config options with a new
16569 ReachableAddresses option that understands address policies.
16570 For example, "ReachableAddresses *:80,*:443"
16571 - Get rid of IgnoreVersion undocumented config option, and make us
16572 only warn, never exit, when we're running an obsolete version.
16573 - Make MonthlyAccountingStart config option truly obsolete now.
16575 o Fixes on 0.1.0.x:
16576 - Reject ports 465 and 587 in the default exit policy, since
16577 people have started using them for spam too.
16578 - It turns out we couldn't bootstrap a network since we added
16579 reachability detection in 0.1.0.1-rc. Good thing the Tor network
16580 has never gone down. Add an AssumeReachable config option to let
16581 servers and dirservers bootstrap. When we're trying to build a
16582 high-uptime or high-bandwidth circuit but there aren't enough
16583 suitable servers, try being less picky rather than simply failing.
16584 - Our logic to decide if the OR we connected to was the right guy
16585 was brittle and maybe open to a mitm for unverified routers.
16586 - We weren't cannibalizing circuits correctly for
16587 CIRCUIT_PURPOSE_C_ESTABLISH_REND and
16588 CIRCUIT_PURPOSE_S_ESTABLISH_INTRO, so we were being forced to
16589 build those from scratch. This should make hidden services faster.
16590 - Predict required circuits better, with an eye toward making hidden
16591 services faster on the service end.
16592 - Retry streams if the exit node sends back a 'misc' failure. This
16593 should result in fewer random failures. Also, after failing
16594 from resolve failed or misc, reset the num failures, so we give
16595 it a fair shake next time we try.
16596 - Clean up the rendezvous warn log msgs, and downgrade some to info.
16597 - Reduce severity on logs about dns worker spawning and culling.
16598 - When we're shutting down and we do something like try to post a
16599 server descriptor or rendezvous descriptor, don't complain that
16600 we seem to be unreachable. Of course we are, we're shutting down.
16601 - Add TTLs to RESOLVED, CONNECTED, and END_REASON_EXITPOLICY cells.
16602 We don't use them yet, but maybe one day our DNS resolver will be
16603 able to discover them.
16604 - Make ContactInfo mandatory for authoritative directory servers.
16605 - Require server descriptors to list IPv4 addresses -- hostnames
16606 are no longer allowed. This also fixes some potential security
16607 problems with people providing hostnames as their address and then
16608 preferentially resolving them to partition users.
16609 - Change log line for unreachability to explicitly suggest /etc/hosts
16610 as the culprit. Also make it clearer what IP address and ports we're
16611 testing for reachability.
16612 - Put quotes around user-supplied strings when logging so users are
16613 more likely to realize if they add bad characters (like quotes)
16615 - Let auth dir servers start without specifying an Address config
16617 - Make unit tests (and other invocations that aren't the real Tor)
16618 run without launching listeners, creating subdirectories, and so on.
16621 Changes in version 0.1.1.5-alpha - 2005-08-08
16622 o Bugfixes included in 0.1.0.14.
16624 o Bugfixes on 0.1.0.x:
16625 - If you write "HiddenServicePort 6667 127.0.0.1 6668" in your
16626 torrc rather than "HiddenServicePort 6667 127.0.0.1:6668",
16627 it would silently using ignore the 6668.
16630 Changes in version 0.1.0.14 - 2005-08-08
16631 o Bugfixes on 0.1.0.x:
16632 - Fix the other half of the bug with crypto handshakes
16634 - Fix an assert trigger if you send a 'signal term' via the
16635 controller when it's listening for 'event info' messages.
16638 Changes in version 0.1.1.4-alpha - 2005-08-04
16639 o Bugfixes included in 0.1.0.13.
16642 - Improve tor_gettimeofday() granularity on windows.
16643 - Make clients regenerate their keys when their IP address changes.
16644 - Implement some more GETINFO goodness: expose helper nodes, config
16645 options, getinfo keys.
16648 Changes in version 0.1.0.13 - 2005-08-04
16649 o Bugfixes on 0.1.0.x:
16650 - Fix a critical bug in the security of our crypto handshakes.
16651 - Fix a size_t underflow in smartlist_join_strings2() that made
16652 it do bad things when you hand it an empty smartlist.
16653 - Fix Windows installer to ship Tor license (thanks to Aphex for
16654 pointing out this oversight) and put a link to the doc directory
16656 - Explicitly set no-unaligned-access for sparc: it turns out the
16657 new gcc's let you compile broken code, but that doesn't make it
16661 Changes in version 0.1.1.3-alpha - 2005-07-23
16662 o Bugfixes on 0.1.1.2-alpha:
16663 - Fix a bug in handling the controller's "post descriptor"
16665 - Fix several bugs in handling the controller's "extend circuit"
16667 - Fix a bug in handling the controller's "stream status" event.
16668 - Fix an assert failure if we have a controller listening for
16669 circuit events and we go offline.
16670 - Re-allow hidden service descriptors to publish 0 intro points.
16671 - Fix a crash when generating your hidden service descriptor if
16672 you don't have enough intro points already.
16674 o New features on 0.1.1.2-alpha:
16675 - New controller function "getinfo accounting", to ask how
16676 many bytes we've used in this time period.
16677 - Experimental support for helper nodes: a lot of the risk from
16678 a small static adversary comes because users pick new random
16679 nodes every time they rebuild a circuit. Now users will try to
16680 stick to the same small set of entry nodes if they can. Not
16681 enabled by default yet.
16683 o Bugfixes on 0.1.0.12:
16684 - If you're an auth dir server, always publish your dirport,
16685 even if you haven't yet found yourself to be reachable.
16686 - Fix a size_t underflow in smartlist_join_strings2() that made
16687 it do bad things when you hand it an empty smartlist.
16690 Changes in version 0.1.0.12 - 2005-07-18
16691 o New directory servers:
16692 - tor26 has changed IP address.
16694 o Bugfixes on 0.1.0.x:
16695 - Fix a possible double-free in tor_gzip_uncompress().
16696 - When --disable-threads is set, do not search for or link against
16697 pthreads libraries.
16698 - Don't trigger an assert if an authoritative directory server
16699 claims its dirport is 0.
16700 - Fix bug with removing Tor as an NT service: some people were
16701 getting "The service did not return an error." Thanks to Matt
16705 Changes in version 0.1.1.2-alpha - 2005-07-15
16706 o New directory servers:
16707 - tor26 has changed IP address.
16709 o Bugfixes on 0.1.0.x, crashes/leaks:
16710 - Port the servers-not-obeying-their-exit-policies fix from
16712 - Fix an fd leak in start_daemon().
16713 - On Windows, you can't always reopen a port right after you've
16714 closed it. So change retry_listeners() to only close and re-open
16715 ports that have changed.
16716 - Fix a possible double-free in tor_gzip_uncompress().
16718 o Bugfixes on 0.1.0.x, usability:
16719 - When tor_socketpair() fails in Windows, give a reasonable
16720 Windows-style errno back.
16721 - Let people type "tor --install" as well as "tor -install" when
16723 want to make it an NT service.
16724 - NT service patch from Matt Edman to improve error messages.
16725 - When the controller asks for a config option with an abbreviated
16726 name, give the full name in our response.
16727 - Correct the man page entry on TrackHostExitsExpire.
16728 - Looks like we were never delivering deflated (i.e. compressed)
16729 running-routers lists, even when asked. Oops.
16730 - When --disable-threads is set, do not search for or link against
16731 pthreads libraries.
16733 o Bugfixes on 0.1.1.x:
16734 - Fix a seg fault with autodetecting which controller version is
16738 - New hidden service descriptor format: put a version in it, and
16739 let people specify introduction/rendezvous points that aren't
16740 in "the directory" (which is subjective anyway).
16741 - Allow the DEBUG controller event to work again. Mark certain log
16742 entries as "don't tell this to controllers", so we avoid cycles.
16745 Changes in version 0.1.0.11 - 2005-06-30
16746 o Bugfixes on 0.1.0.x:
16747 - Fix major security bug: servers were disregarding their
16748 exit policies if clients behaved unexpectedly.
16749 - Make OS X init script check for missing argument, so we don't
16750 confuse users who invoke it incorrectly.
16751 - Fix a seg fault in "tor --hash-password foo".
16752 - The MAPADDRESS control command was broken.
16755 Changes in version 0.1.1.1-alpha - 2005-06-29
16757 - Make OS X init script check for missing argument, so we don't
16758 confuse users who invoke it incorrectly.
16759 - Fix a seg fault in "tor --hash-password foo".
16760 - Fix a possible way to DoS dirservers.
16761 - When we complain that your exit policy implicitly allows local or
16762 private address spaces, name them explicitly so operators can
16764 - Make the log message less scary when all the dirservers are
16765 temporarily unreachable.
16766 - We were printing the number of idle dns workers incorrectly when
16770 - Revised controller protocol (version 1) that uses ascii rather
16771 than binary. Add supporting libraries in python and java so you
16772 can use the controller from your applications without caring how
16773 our protocol works.
16774 - Spiffy new support for crypto hardware accelerators. Can somebody
16778 Changes in version 0.0.9.10 - 2005-06-16
16779 o Bugfixes on 0.0.9.x (backported from 0.1.0.10):
16780 - Refuse relay cells that claim to have a length larger than the
16781 maximum allowed. This prevents a potential attack that could read
16782 arbitrary memory (e.g. keys) from an exit server's process
16786 Changes in version 0.1.0.10 - 2005-06-14
16787 o Allow a few EINVALs from libevent before dying. Warn on kqueue with
16788 libevent before 1.1a.
16791 Changes in version 0.1.0.9-rc - 2005-06-09
16793 - Reset buf->highwater every time buf_shrink() is called, not just on
16794 a successful shrink. This was causing significant memory bloat.
16795 - Fix buffer overflow when checking hashed passwords.
16796 - Security fix: if seeding the RNG on Win32 fails, quit.
16797 - Allow seeding the RNG on Win32 even when you're not running as
16799 - Disable threading on Solaris too. Something is wonky with it,
16800 cpuworkers, and reentrant libs.
16801 - Reenable the part of the code that tries to flush as soon as an
16802 OR outbuf has a full TLS record available. Perhaps this will make
16803 OR outbufs not grow as huge except in rare cases, thus saving lots
16804 of CPU time plus memory.
16805 - Reject malformed .onion addresses rather then passing them on as
16806 normal web requests.
16807 - Adapt patch from Adam Langley: fix possible memory leak in
16808 tor_lookup_hostname().
16809 - Initialize libevent later in the startup process, so the logs are
16810 already established by the time we start logging libevent warns.
16811 - Use correct errno on win32 if libevent fails.
16812 - Check and warn about known-bad/slow libevent versions.
16813 - Pay more attention to the ClientOnly config option.
16814 - Have torctl.in/tor.sh.in check for location of su binary (needed
16816 - Correct/add man page entries for LongLivedPorts, ExitPolicy,
16817 KeepalivePeriod, ClientOnly, NoPublish, HttpProxy, HttpsProxy,
16818 HttpProxyAuthenticator
16819 - Stop warning about sigpipes in the logs. We're going to
16820 pretend that getting these occassionally is normal and fine.
16821 - Resolve OS X installer bugs: stop claiming to be 0.0.9.2 in
16823 installer screens; and don't put stuff into StartupItems unless
16824 the user asks you to.
16825 - Require servers that use the default dirservers to have public IP
16826 addresses. We have too many servers that are configured with private
16827 IPs and their admins never notice the log entries complaining that
16828 their descriptors are being rejected.
16829 - Add OSX uninstall instructions. An actual uninstall script will
16833 Changes in version 0.1.0.8-rc - 2005-05-23
16835 - It turns out that kqueue on OS X 10.3.9 was causing kernel
16836 panics. Disable kqueue on all OS X Tors.
16837 - Fix RPM: remove duplicate line accidentally added to the rpm
16839 - Disable threads on openbsd too, since its gethostaddr is not
16841 - Tolerate libevent 0.8 since it still works, even though it's
16843 - Enable building on Red Hat 9.0 again.
16844 - Allow the middle hop of the testing circuit to be running any
16845 version, now that most of them have the bugfix to let them connect
16846 to unknown servers. This will allow reachability testing to work
16847 even when 0.0.9.7-0.0.9.9 become obsolete.
16848 - Handle relay cells with rh.length too large. This prevents
16849 a potential attack that could read arbitrary memory (maybe even
16850 keys) from the exit server's process.
16851 - We screwed up the dirport reachability testing when we don't yet
16852 have a cached version of the directory. Hopefully now fixed.
16853 - Clean up router_load_single_router() (used by the controller),
16854 so it doesn't seg fault on error.
16855 - Fix a minor memory leak when somebody establishes an introduction
16856 point at your Tor server.
16857 - If a socks connection ends because read fails, don't warn that
16858 you're not sending a socks reply back.
16861 - Add HttpProxyAuthenticator config option too, that works like
16862 the HttpsProxyAuthenticator config option.
16863 - Encode hashed controller passwords in hex instead of base64,
16864 to make it easier to write controllers.
16867 Changes in version 0.1.0.7-rc - 2005-05-17
16869 - Fix a bug in the OS X package installer that prevented it from
16870 installing on Tiger.
16871 - Fix a script bug in the OS X package installer that made it
16872 complain during installation.
16873 - Find libevent even if it's hiding in /usr/local/ and your
16874 CFLAGS and LDFLAGS don't tell you to look there.
16875 - Be able to link with libevent as a shared library (the default
16876 after 1.0d), even if it's hiding in /usr/local/lib and even
16877 if you haven't added /usr/local/lib to your /etc/ld.so.conf,
16878 assuming you're running gcc. Otherwise fail and give a useful
16880 - Fix a bug in the RPM packager: set home directory for _tor to
16881 something more reasonable when first installing.
16882 - Free a minor amount of memory that is still reachable on exit.
16885 Changes in version 0.1.0.6-rc - 2005-05-14
16887 - Implement --disable-threads configure option. Disable threads on
16888 netbsd by default, because it appears to have no reentrant resolver
16890 - Apple's OS X 10.4.0 ships with a broken kqueue. The new libevent
16891 release (1.1) detects and disables kqueue if it's broken.
16892 - Append default exit policy before checking for implicit internal
16893 addresses. Now we don't log a bunch of complaints on startup
16894 when using the default exit policy.
16895 - Some people were putting "Address " in their torrc, and they had
16896 a buggy resolver that resolved " " to 0.0.0.0. Oops.
16897 - If DataDir is ~/.tor, and that expands to /.tor, then default to
16898 LOCALSTATEDIR/tor instead.
16899 - Fix fragmented-message bug in TorControl.py.
16900 - Resolve a minor bug which would prevent unreachable dirports
16901 from getting suppressed in the published descriptor.
16902 - When the controller gave us a new descriptor, we weren't resolving
16903 it immediately, so Tor would think its address was 0.0.0.0 until
16904 we fetched a new directory.
16905 - Fix an uppercase/lowercase case error in suppressing a bogus
16906 libevent warning on some Linuxes.
16909 - Begin scrubbing sensitive strings from logs by default. Turn off
16910 the config option SafeLogging if you need to do debugging.
16911 - Switch to a new buffer management algorithm, which tries to avoid
16912 reallocing and copying quite as much. In first tests it looks like
16913 it uses *more* memory on average, but less cpu.
16914 - First cut at support for "create-fast" cells. Clients can use
16915 these when extending to their first hop, since the TLS already
16916 provides forward secrecy and authentication. Not enabled on
16918 - When dirservers refuse a router descriptor, we now log its
16919 contactinfo, platform, and the poster's IP address.
16920 - Call tor_free_all instead of connections_free_all after forking, to
16921 save memory on systems that need to fork.
16922 - Whine at you if you're a server and you don't set your contactinfo.
16923 - Implement --verify-config command-line option to check if your torrc
16924 is valid without actually launching Tor.
16925 - Rewrite address "serifos.exit" to "localhost.serifos.exit"
16926 rather than just rejecting it.
16929 Changes in version 0.1.0.5-rc - 2005-04-27
16931 - Stop trying to print a null pointer if an OR conn fails because
16932 we didn't like its cert.
16934 - Switch our internal buffers implementation to use a ring buffer,
16935 to hopefully improve performance for fast servers a lot.
16936 - Add HttpsProxyAuthenticator support (basic auth only), based
16937 on patch from Adam Langley.
16938 - Bump the default BandwidthRate from 1 MB to 2 MB, to accommodate
16939 the fast servers that have been joining lately.
16940 - Give hidden service accesses extra time on the first attempt,
16941 since 60 seconds is often only barely enough. This might improve
16943 - Improve performance for dirservers: stop re-parsing the whole
16944 directory every time you regenerate it.
16945 - Add more debugging info to help us find the weird dns freebsd
16946 pthreads bug; cleaner debug messages to help track future issues.
16949 Changes in version 0.0.9.9 - 2005-04-23
16950 o Bugfixes on 0.0.9.x:
16951 - If unofficial Tor clients connect and send weird TLS certs, our
16952 Tor server triggers an assert. This release contains a minimal
16953 backport from the broader fix that we put into 0.1.0.4-rc.
16956 Changes in version 0.1.0.4-rc - 2005-04-23
16958 - If unofficial Tor clients connect and send weird TLS certs, our
16959 Tor server triggers an assert. Stop asserting, and start handling
16960 TLS errors better in other situations too.
16961 - When the controller asks us to tell it about all the debug-level
16962 logs, it turns out we were generating debug-level logs while
16963 telling it about them, which turns into a bad loop. Now keep
16964 track of whether you're sending a debug log to the controller,
16965 and don't log when you are.
16966 - Fix the "postdescriptor" feature of the controller interface: on
16967 non-complete success, only say "done" once.
16969 - Clients are now willing to load balance over up to 2mB, not 1mB,
16970 of advertised bandwidth capacity.
16971 - Add a NoPublish config option, so you can be a server (e.g. for
16972 testing running Tor servers in other Tor networks) without
16973 publishing your descriptor to the primary dirservers.
16976 Changes in version 0.1.0.3-rc - 2005-04-08
16977 o Improvements on 0.1.0.2-rc:
16978 - Client now retries when streams end early for 'hibernating' or
16979 'resource limit' reasons, rather than failing them.
16980 - More automated handling for dirserver operators:
16981 - Automatically approve nodes running 0.1.0.2-rc or later,
16982 now that the the reachability detection stuff is working.
16983 - Now we allow two unverified servers with the same nickname
16984 but different keys. But if a nickname is verified, only that
16985 nickname+key are allowed.
16986 - If you're an authdirserver connecting to an address:port,
16987 and it's not the OR you were expecting, forget about that
16988 descriptor. If he *was* the one you were expecting, then forget
16989 about all other descriptors for that address:port.
16990 - Allow servers to publish descriptors from 12 hours in the future.
16991 Corollary: only whine about clock skew from the dirserver if
16992 he's a trusted dirserver (since now even verified servers could
16993 have quite wrong clocks).
16994 - Adjust maximum skew and age for rendezvous descriptors: let skew
16995 be 48 hours rather than 90 minutes.
16996 - Efficiency improvements:
16997 - Keep a big splay tree of (circid,orconn)->circuit mappings to make
16998 it much faster to look up a circuit for each relay cell.
16999 - Remove most calls to assert_all_pending_dns_resolves_ok(),
17000 since they're eating our cpu on exit nodes.
17001 - Stop wasting time doing a case insensitive comparison for every
17002 dns name every time we do any lookup. Canonicalize the names to
17003 lowercase and be done with it.
17004 - Start sending 'truncated' cells back rather than destroy cells,
17005 if the circuit closes in front of you. This means we won't have
17006 to abandon partially built circuits.
17007 - Only warn once per nickname from add_nickname_list_to_smartlist
17008 per failure, so an entrynode or exitnode choice that's down won't
17010 - Put a note in the torrc about abuse potential with the default
17012 - Revise control spec and implementation to allow all log messages to
17013 be sent to controller with their severities intact (suggested by
17014 Matt Edman). Update TorControl to handle new log event types.
17015 - Provide better explanation messages when controller's POSTDESCRIPTOR
17017 - Stop putting nodename in the Platform string in server descriptors.
17018 It doesn't actually help, and it is confusing/upsetting some people.
17020 o Bugfixes on 0.1.0.2-rc:
17021 - We were printing the host mask wrong in exit policies in server
17022 descriptors. This isn't a critical bug though, since we were still
17023 obeying the exit policy internally.
17024 - Fix Tor when compiled with libevent but without pthreads: move
17025 connection_unregister() from _connection_free() to
17027 - Fix an assert trigger (already fixed in 0.0.9.x): when we have
17028 the rare mysterious case of accepting a conn on 0.0.0.0:0, then
17029 when we look through the connection array, we'll find any of the
17030 cpu/dnsworkers. This is no good.
17032 o Bugfixes on 0.0.9.8:
17033 - Fix possible bug on threading platforms (e.g. win32) which was
17034 leaking a file descriptor whenever a cpuworker or dnsworker died.
17035 - When using preferred entry or exit nodes, ignore whether the
17036 circuit wants uptime or capacity. They asked for the nodes, they
17038 - chdir() to your datadirectory at the *end* of the daemonize process,
17039 not the beginning. This was a problem because the first time you
17040 run tor, if your datadir isn't there, and you have runasdaemon set
17041 to 1, it will try to chdir to it before it tries to create it. Oops.
17042 - Handle changed router status correctly when dirserver reloads
17043 fingerprint file. We used to be dropping all unverified descriptors
17044 right then. The bug was hidden because we would immediately
17045 fetch a directory from another dirserver, which would include the
17046 descriptors we just dropped.
17047 - When we're connecting to an OR and he's got a different nickname/key
17048 than we were expecting, only complain loudly if we're an OP or a
17049 dirserver. Complaining loudly to the OR admins just confuses them.
17050 - Tie MAX_DIR_SIZE to MAX_BUF_SIZE, so now directory sizes won't get
17051 artificially capped at 500kB.
17054 Changes in version 0.0.9.8 - 2005-04-07
17055 o Bugfixes on 0.0.9.x:
17056 - We have a bug that I haven't found yet. Sometimes, very rarely,
17057 cpuworkers get stuck in the 'busy' state, even though the cpuworker
17058 thinks of itself as idle. This meant that no new circuits ever got
17059 established. Here's a workaround to kill any cpuworker that's been
17060 busy for more than 100 seconds.
17063 Changes in version 0.1.0.2-rc - 2005-04-01
17064 o Bugfixes on 0.1.0.1-rc:
17065 - Fixes on reachability detection:
17066 - Don't check for reachability while hibernating.
17067 - If ORPort is reachable but DirPort isn't, still publish the
17068 descriptor, but zero out DirPort until it's found reachable.
17069 - When building testing circs for ORPort testing, use only
17070 high-bandwidth nodes, so fewer circuits fail.
17071 - Complain about unreachable ORPort separately from unreachable
17072 DirPort, so the user knows what's going on.
17073 - Make sure we only conclude ORPort reachability if we didn't
17074 initiate the conn. Otherwise we could falsely conclude that
17075 we're reachable just because we connected to the guy earlier
17076 and he used that same pipe to extend to us.
17077 - Authdirservers shouldn't do ORPort reachability detection,
17078 since they're in clique mode, so it will be rare to find a
17079 server not already connected to them.
17080 - When building testing circuits, always pick middle hops running
17081 Tor 0.0.9.7, so we avoid the "can't extend to unknown routers"
17082 bug. (This is a kludge; it will go away when 0.0.9.x becomes
17084 - When we decide we're reachable, actually publish our descriptor
17086 - Fix bug in redirectstream in the controller.
17087 - Fix the state descriptor strings so logs don't claim edge streams
17088 are in a different state than they actually are.
17089 - Use recent libevent features when possible (this only really affects
17090 win32 and osx right now, because the new libevent with these
17091 features hasn't been released yet). Add code to suppress spurious
17093 - Prevent possible segfault in connection_close_unattached_ap().
17094 - Fix newlines on torrc in win32.
17095 - Improve error msgs when tor-resolve fails.
17097 o Improvements on 0.0.9.x:
17098 - New experimental script tor/contrib/ExerciseServer.py (needs more
17099 work) that uses the controller interface to build circuits and
17100 fetch pages over them. This will help us bootstrap servers that
17101 have lots of capacity but haven't noticed it yet.
17102 - New experimental script tor/contrib/PathDemo.py (needs more work)
17103 that uses the controller interface to let you choose whole paths
17105 "<hostname>.<path,separated by dots>.<length of path>.path"
17106 - When we've connected to an OR and handshaked but didn't like
17107 the result, we were closing the conn without sending destroy
17108 cells back for pending circuits. Now send those destroys.
17111 Changes in version 0.0.9.7 - 2005-04-01
17112 o Bugfixes on 0.0.9.x:
17113 - Fix another race crash bug (thanks to Glenn Fink for reporting).
17114 - Compare identity to identity, not to nickname, when extending to
17115 a router not already in the directory. This was preventing us from
17116 extending to unknown routers. Oops.
17117 - Make sure to create OS X Tor user in <500 range, so we aren't
17118 creating actual system users.
17119 - Note where connection-that-hasn't-sent-end was marked, and fix
17120 a few really loud instances of this harmless bug (it's fixed more
17124 Changes in version 0.1.0.1-rc - 2005-03-28
17126 - Add reachability testing. Your Tor server will automatically try
17127 to see if its ORPort and DirPort are reachable from the outside,
17128 and it won't upload its descriptor until it decides they are.
17129 - Handle unavailable hidden services better. Handle slow or busy
17130 hidden services better.
17131 - Add support for CONNECTing through https proxies, with "HttpsProxy"
17133 - New exit policy: accept most low-numbered ports, rather than
17134 rejecting most low-numbered ports.
17135 - More Tor controller support (still experimental). See
17136 http://tor.eff.org/doc/control-spec.txt for all the new features,
17137 including signals to emulate unix signals from any platform;
17138 redirectstream; extendcircuit; mapaddress; getinfo; postdescriptor;
17139 closestream; closecircuit; etc.
17140 - Make nt services work and start on startup on win32 (based on
17141 patch by Matt Edman).
17142 - Add a new AddressMap config directive to rewrite incoming socks
17143 addresses. This lets you, for example, declare an implicit
17144 required exit node for certain sites.
17145 - Add a new TrackHostExits config directive to trigger addressmaps
17146 for certain incoming socks addresses -- for sites that break when
17147 your exit keeps changing (based on patch by Mike Perry).
17148 - Redo the client-side dns cache so it's just an addressmap too.
17149 - Notice when our IP changes, and reset stats/uptime/reachability.
17150 - When an application is using socks5, give him the whole variety of
17151 potential socks5 responses (connect refused, host unreachable, etc),
17152 rather than just "success" or "failure".
17153 - A more sane version numbering system. See
17154 http://tor.eff.org/cvs/tor/doc/version-spec.txt for details.
17155 - New contributed script "exitlist": a simple python script to
17156 parse directories and find Tor nodes that exit to listed
17158 - New contributed script "privoxy-tor-toggle" to toggle whether
17159 Privoxy uses Tor. Seems to be configured for Debian by default.
17160 - Report HTTP reasons to client when getting a response from directory
17161 servers -- so you can actually know what went wrong.
17162 - New config option MaxAdvertisedBandwidth which lets you advertise
17163 a low bandwidthrate (to not attract as many circuits) while still
17164 allowing a higher bandwidthrate in reality.
17166 o Robustness/stability fixes:
17167 - Make Tor use Niels Provos's libevent instead of its current
17168 poll-but-sometimes-select mess. This will let us use faster async
17169 cores (like epoll, kpoll, and /dev/poll), and hopefully work better
17171 - pthread support now too. This was forced because when we forked,
17172 we ended up wasting a lot of duplicate ram over time. Also switch
17173 to foo_r versions of some library calls to allow reentry and
17175 - Better handling for heterogeneous / unreliable nodes:
17176 - Annotate circuits w/ whether they aim to contain high uptime nodes
17177 and/or high capacity nodes. When building circuits, choose
17179 - This means that every single node in an intro rend circuit,
17180 not just the last one, will have a minimum uptime.
17181 - New config option LongLivedPorts to indicate application streams
17182 that will want high uptime circuits.
17183 - Servers reset uptime when a dir fetch entirely fails. This
17184 hopefully reflects stability of the server's network connectivity.
17185 - If somebody starts his tor server in Jan 2004 and then fixes his
17186 clock, don't make his published uptime be a year.
17187 - Reset published uptime when you wake up from hibernation.
17188 - Introduce a notion of 'internal' circs, which are chosen without
17189 regard to the exit policy of the last hop. Intro and rendezvous
17190 circs must be internal circs, to avoid leaking information. Resolve
17191 and connect streams can use internal circs if they want.
17192 - New circuit pooling algorithm: make sure to have enough circs around
17193 to satisfy any predicted ports, and also make sure to have 2 internal
17194 circs around if we've required internal circs lately (and with high
17195 uptime if we've seen that lately too).
17196 - Split NewCircuitPeriod option into NewCircuitPeriod (30 secs),
17197 which describes how often we retry making new circuits if current
17198 ones are dirty, and MaxCircuitDirtiness (10 mins), which describes
17199 how long we're willing to make use of an already-dirty circuit.
17200 - Cannibalize GENERAL circs to be C_REND, C_INTRO, S_INTRO, and S_REND
17201 circ as necessary, if there are any completed ones lying around
17202 when we try to launch one.
17203 - Make hidden services try to establish a rendezvous for 30 seconds,
17204 rather than for n (where n=3) attempts to build a circuit.
17205 - Change SHUTDOWN_WAIT_LENGTH from a fixed 30 secs to a config option
17206 "ShutdownWaitLength".
17207 - Try to be more zealous about calling connection_edge_end when
17208 things go bad with edge conns in connection.c.
17209 - Revise tor-spec to add more/better stream end reasons.
17210 - Revise all calls to connection_edge_end to avoid sending "misc",
17211 and to take errno into account where possible.
17214 - Fix a race condition that can trigger an assert, when we have a
17215 pending create cell and an OR connection fails right then.
17216 - Fix several double-mark-for-close bugs, e.g. where we were finding
17217 a conn for a cell even if that conn is already marked for close.
17218 - Make sequence of log messages when starting on win32 with no config
17219 file more reasonable.
17220 - When choosing an exit node for a new non-internal circ, don't take
17221 into account whether it'll be useful for any pending x.onion
17222 addresses -- it won't.
17223 - Turn addr_policy_compare from a tristate to a quadstate; this should
17224 help address our "Ah, you allow 1.2.3.4:80. You are a good choice
17225 for google.com" problem.
17226 - Make "platform" string in descriptor more accurate for Win32 servers,
17227 so it's not just "unknown platform".
17228 - Fix an edge case in parsing config options (thanks weasel).
17229 If they say "--" on the commandline, it's not an option.
17230 - Reject odd-looking addresses at the client (e.g. addresses that
17231 contain a colon), rather than having the server drop them because
17233 - tor-resolve requests were ignoring .exit if there was a working circuit
17234 they could use instead.
17235 - REUSEADDR on normal platforms means you can rebind to the port
17236 right after somebody else has let it go. But REUSEADDR on win32
17237 means to let you bind to the port _even when somebody else
17238 already has it bound_! So, don't do that on Win32.
17239 - Change version parsing logic: a version is "obsolete" if it is not
17240 recommended and (1) there is a newer recommended version in the
17241 same series, or (2) there are no recommended versions in the same
17242 series, but there are some recommended versions in a newer series.
17243 A version is "new" if it is newer than any recommended version in
17245 - Stop most cases of hanging up on a socks connection without sending
17249 - Require BandwidthRate to be at least 20kB/s for servers.
17250 - When a dirserver causes you to give a warn, mention which dirserver
17252 - New config option DirAllowPrivateAddresses for authdirservers.
17253 Now by default they refuse router descriptors that have non-IP or
17254 private-IP addresses.
17255 - Stop publishing socksport in the directory, since it's not
17256 actually meant to be public. For compatibility, publish a 0 there
17258 - Change DirFetchPeriod/StatusFetchPeriod to have a special "Be
17259 smart" value, that is low for servers and high for clients.
17260 - If our clock jumps forward by 100 seconds or more, assume something
17261 has gone wrong with our network and abandon all not-yet-used circs.
17262 - Warn when exit policy implicitly allows local addresses.
17263 - If we get an incredibly skewed timestamp from a dirserver mirror
17264 that isn't a verified OR, don't warn -- it's probably him that's
17266 - Since we ship our own Privoxy on OS X, tweak it so it doesn't write
17267 cookies to disk and doesn't log each web request to disk. (Thanks
17268 to Brett Carrington for pointing this out.)
17269 - When a client asks us for a dir mirror and we don't have one,
17270 launch an attempt to get a fresh one.
17271 - If we're hibernating and we get a SIGINT, exit immediately.
17272 - Add --with-dmalloc ./configure option, to track memory leaks.
17273 - And try to free all memory on closing, so we can detect what
17275 - Cache local dns resolves correctly even when they're .exit
17277 - Give a better warning when some other server advertises an
17278 ORPort that is actually an apache running ssl.
17279 - Add "opt hibernating 1" to server descriptor to make it clearer
17280 whether the server is hibernating.
17283 Changes in version 0.0.9.6 - 2005-03-24
17284 o Bugfixes on 0.0.9.x (crashes and asserts):
17285 - Add new end stream reasons to maintainance branch. Fix bug where
17286 reason (8) could trigger an assert. Prevent bug from recurring.
17287 - Apparently win32 stat wants paths to not end with a slash.
17288 - Fix assert triggers in assert_cpath_layer_ok(), where we were
17289 blowing away the circuit that conn->cpath_layer points to, then
17290 checking to see if the circ is well-formed. Backport check to make
17291 sure we dont use the cpath on a closed connection.
17292 - Prevent circuit_resume_edge_reading_helper() from trying to package
17293 inbufs for marked-for-close streams.
17294 - Don't crash on hup if your options->address has become unresolvable.
17295 - Some systems (like OS X) sometimes accept() a connection and tell
17296 you the remote host is 0.0.0.0:0. If this happens, due to some
17297 other mis-features, we get confused; so refuse the conn for now.
17299 o Bugfixes on 0.0.9.x (other):
17300 - Fix harmless but scary "Unrecognized content encoding" warn message.
17301 - Add new stream error reason: TORPROTOCOL reason means "you are not
17302 speaking a version of Tor I understand; say bye-bye to your stream."
17303 - Be willing to cache directories from up to ROUTER_MAX_AGE seconds
17304 into the future, now that we are more tolerant of skew. This
17305 resolves a bug where a Tor server would refuse to cache a directory
17306 because all the directories it gets are too far in the future;
17307 yet the Tor server never logs any complaints about clock skew.
17308 - Mac packaging magic: make man pages useable, and do not overwrite
17309 existing torrc files.
17310 - Make OS X log happily to /var/log/tor/tor.log
17313 Changes in version 0.0.9.5 - 2005-02-22
17314 o Bugfixes on 0.0.9.x:
17315 - Fix an assert race at exit nodes when resolve requests fail.
17316 - Stop picking unverified dir mirrors--it only leads to misery.
17317 - Patch from Matt Edman to make NT services work better. Service
17318 support is still not compiled into the executable by default.
17319 - Patch from Dmitri Bely so the Tor service runs better under
17320 the win32 SYSTEM account.
17321 - Make tor-resolve actually work (?) on Win32.
17322 - Fix a sign bug when getrlimit claims to have 4+ billion
17323 file descriptors available.
17324 - Stop refusing to start when bandwidthburst == bandwidthrate.
17325 - When create cells have been on the onion queue more than five
17326 seconds, just send back a destroy and take them off the list.
17329 Changes in version 0.0.9.4 - 2005-02-03
17330 o Bugfixes on 0.0.9:
17331 - Fix an assert bug that took down most of our servers: when
17332 a server claims to have 1 GB of bandwidthburst, don't
17334 - Don't crash as badly if we have spawned the max allowed number
17335 of dnsworkers, or we're out of file descriptors.
17336 - Block more file-sharing ports in the default exit policy.
17337 - MaxConn is now automatically set to the hard limit of max
17338 file descriptors we're allowed (ulimit -n), minus a few for
17340 - Give a clearer message when servers need to raise their
17341 ulimit -n when they start running out of file descriptors.
17342 - SGI Compatibility patches from Jan Schaumann.
17343 - Tolerate a corrupt cached directory better.
17344 - When a dirserver hasn't approved your server, list which one.
17345 - Go into soft hibernation after 95% of the bandwidth is used,
17346 not 99%. This is especially important for daily hibernators who
17347 have a small accounting max. Hopefully it will result in fewer
17348 cut connections when the hard hibernation starts.
17349 - Load-balance better when using servers that claim more than
17350 800kB/s of capacity.
17351 - Make NT services work (experimental, only used if compiled in).
17354 Changes in version 0.0.9.3 - 2005-01-21
17355 o Bugfixes on 0.0.9:
17356 - Backport the cpu use fixes from main branch, so busy servers won't
17357 need as much processor time.
17358 - Work better when we go offline and then come back, or when we
17359 run Tor at boot before the network is up. We do this by
17360 optimistically trying to fetch a new directory whenever an
17361 application request comes in and we think we're offline -- the
17362 human is hopefully a good measure of when the network is back.
17363 - Backport some minimal hidserv bugfixes: keep rend circuits open as
17364 long as you keep using them; actually publish hidserv descriptors
17365 shortly after they change, rather than waiting 20-40 minutes.
17366 - Enable Mac startup script by default.
17367 - Fix duplicate dns_cancel_pending_resolve reported by Giorgos Pallas.
17368 - When you update AllowUnverifiedNodes or FirewallPorts via the
17369 controller's setconf feature, we were always appending, never
17371 - When you update HiddenServiceDir via setconf, it was screwing up
17372 the order of reading the lines, making it fail.
17373 - Do not rewrite a cached directory back to the cache; otherwise we
17374 will think it is recent and not fetch a newer one on startup.
17375 - Workaround for webservers that lie about Content-Encoding: Tor
17376 now tries to autodetect compressed directories and compression
17377 itself. This lets us Proxypass dir fetches through apache.
17380 Changes in version 0.0.9.2 - 2005-01-04
17381 o Bugfixes on 0.0.9 (crashes and asserts):
17382 - Fix an assert on startup when the disk is full and you're logging
17384 - If you do socks4 with an IP of 0.0.0.x but *don't* provide a socks4a
17385 style address, then we'd crash.
17386 - Fix an assert trigger when the running-routers string we get from
17387 a dirserver is broken.
17388 - Make worker threads start and run on win32. Now win32 servers
17390 - Bandaid (not actually fix, but now it doesn't crash) an assert
17391 where the dns worker dies mysteriously and the main Tor process
17392 doesn't remember anything about the address it was resolving.
17394 o Bugfixes on 0.0.9 (Win32):
17395 - Workaround for brain-damaged __FILE__ handling on MSVC: keep Nick's
17396 name out of the warning/assert messages.
17397 - Fix a superficial "unhandled error on read" bug on win32.
17398 - The win32 installer no longer requires a click-through for our
17399 license, since our Free Software license grants rights but does not
17401 - Win32: When connecting to a dirserver fails, try another one
17402 immediately. (This was already working for non-win32 Tors.)
17403 - Stop trying to parse $HOME on win32 when hunting for default
17405 - Make tor-resolve.c work on win32 by calling network_init().
17407 o Bugfixes on 0.0.9 (other):
17408 - Make 0.0.9.x build on Solaris again.
17409 - Due to a fencepost error, we were blowing away the \n when reporting
17410 confvalue items in the controller. So asking for multiple config
17411 values at once couldn't work.
17412 - When listing circuits that are pending on an opening OR connection,
17413 if we're an OR we were listing circuits that *end* at us as
17414 being pending on every listener, dns/cpu worker, etc. Stop that.
17415 - Dirservers were failing to create 'running-routers' or 'directory'
17416 strings if we had more than some threshold of routers. Fix them so
17417 they can handle any number of routers.
17418 - Fix a superficial "Duplicate mark for close" bug.
17419 - Stop checking for clock skew for OR connections, even for servers.
17420 - Fix a fencepost error that was chopping off the last letter of any
17421 nickname that is the maximum allowed nickname length.
17422 - Update URLs in log messages so they point to the new website.
17423 - Fix a potential problem in mangling server private keys while
17424 writing to disk (not triggered yet, as far as we know).
17425 - Include the licenses for other free software we include in Tor,
17426 now that we're shipping binary distributions more regularly.
17429 Changes in version 0.0.9.1 - 2004-12-15
17430 o Bugfixes on 0.0.9:
17431 - Make hibernation actually work.
17432 - Make HashedControlPassword config option work.
17433 - When we're reporting event circuit status to a controller,
17434 don't use the stream status code.
17437 Changes in version 0.0.9 - 2004-12-12
17439 - Clean up manpage and torrc.sample file.
17440 - Clean up severities and text of log warnings.
17442 - Make servers trigger an assert when they enter hibernation.
17445 Changes in version 0.0.9rc7 - 2004-12-08
17446 o Bugfixes on 0.0.9rc:
17447 - Fix a stack-trashing crash when an exit node begins hibernating.
17448 - Avoid looking at unallocated memory while considering which
17449 ports we need to build circuits to cover.
17450 - Stop a sigpipe: when an 'end' cell races with eof from the app,
17451 we shouldn't hold-open-until-flush if the eof arrived first.
17452 - Fix a bug with init_cookie_authentication() in the controller.
17453 - When recommending new-format log lines, if the upper bound is
17454 LOG_ERR, leave it implicit.
17456 o Bugfixes on 0.0.8.1:
17457 - Fix a whole slew of memory leaks.
17458 - Fix isspace() and friends so they still make Solaris happy
17459 but also so they don't trigger asserts on win32.
17460 - Fix parse_iso_time on platforms without strptime (eg win32).
17461 - win32: tolerate extra "readable" events better.
17462 - win32: when being multithreaded, leave parent fdarray open.
17463 - Make unit tests work on win32.
17466 Changes in version 0.0.9rc6 - 2004-12-06
17467 o Bugfixes on 0.0.9pre:
17468 - Clean up some more integer underflow opportunities (not exploitable
17470 - While hibernating, hup should not regrow our listeners.
17471 - Send an end to the streams we close when we hibernate, rather
17472 than just chopping them off.
17473 - React to eof immediately on non-open edge connections.
17475 o Bugfixes on 0.0.8.1:
17476 - Calculate timeout for waiting for a connected cell from the time
17477 we sent the begin cell, not from the time the stream started. If
17478 it took a long time to establish the circuit, we would time out
17479 right after sending the begin cell.
17480 - Fix router_compare_addr_to_addr_policy: it was not treating a port
17481 of * as always matching, so we were picking reject *:* nodes as
17482 exit nodes too. Oops.
17485 - New circuit building strategy: keep a list of ports that we've
17486 used in the past 6 hours, and always try to have 2 circuits open
17487 or on the way that will handle each such port. Seed us with port
17488 80 so web users won't complain that Tor is "slow to start up".
17489 - Make kill -USR1 dump more useful stats about circuits.
17490 - When warning about retrying or giving up, print the address, so
17491 the user knows which one it's talking about.
17492 - If you haven't used a clean circuit in an hour, throw it away,
17493 just to be on the safe side. (This means after 6 hours a totally
17494 unused Tor client will have no circuits open.)
17497 Changes in version 0.0.9rc5 - 2004-12-01
17498 o Bugfixes on 0.0.8.1:
17499 - Disallow NDEBUG. We don't ever want anybody to turn off debug.
17500 - Let resolve conns retry/expire also, rather than sticking around
17502 - If we are using select, make sure we stay within FD_SETSIZE.
17504 o Bugfixes on 0.0.9pre:
17505 - Fix integer underflow in tor_vsnprintf() that may be exploitable,
17506 but doesn't seem to be currently; thanks to Ilja van Sprundel for
17508 - If anybody set DirFetchPostPeriod, give them StatusFetchPeriod
17509 instead. Impose minima and maxima for all *Period options; impose
17510 even tighter maxima for fetching if we are a caching dirserver.
17511 Clip rather than rejecting.
17512 - Fetch cached running-routers from servers that serve it (that is,
17513 authdirservers and servers running 0.0.9rc5-cvs or later.)
17516 - Accept *:706 (silc) in default exit policy.
17517 - Implement new versioning format for post 0.1.
17518 - Support "foo.nickname.exit" addresses, to let Alice request the
17519 address "foo" as viewed by exit node "nickname". Based on a patch
17521 - Make tor --version --version dump the cvs Id of every file.
17524 Changes in version 0.0.9rc4 - 2004-11-28
17525 o Bugfixes on 0.0.8.1:
17526 - Make windows sockets actually non-blocking (oops), and handle
17527 win32 socket errors better.
17529 o Bugfixes on 0.0.9rc1:
17530 - Actually catch the -USR2 signal.
17533 Changes in version 0.0.9rc3 - 2004-11-25
17534 o Bugfixes on 0.0.8.1:
17535 - Flush the log file descriptor after we print "Tor opening log file",
17536 so we don't see those messages days later.
17538 o Bugfixes on 0.0.9rc1:
17539 - Make tor-resolve work again.
17540 - Avoid infinite loop in tor-resolve if tor hangs up on it.
17541 - Fix an assert trigger for clients/servers handling resolves.
17544 Changes in version 0.0.9rc2 - 2004-11-24
17545 o Bugfixes on 0.0.9rc1:
17546 - I broke socks5 support while fixing the eof bug.
17547 - Allow unitless bandwidths and intervals; they default to bytes
17549 - New servers don't start out hibernating; they are active until
17550 they run out of bytes, so they have a better estimate of how
17551 long it takes, and so their operators can know they're working.
17554 Changes in version 0.0.9rc1 - 2004-11-23
17555 o Bugfixes on 0.0.8.1:
17556 - Finally fix a bug that's been plaguing us for a year:
17557 With high load, circuit package window was reaching 0. Whenever
17558 we got a circuit-level sendme, we were reading a lot on each
17559 socket, but only writing out a bit. So we would eventually reach
17560 eof. This would be noticed and acted on even when there were still
17561 bytes sitting in the inbuf.
17562 - When poll() is interrupted, we shouldn't believe the revents values.
17564 o Bugfixes on 0.0.9pre6:
17565 - Fix hibernate bug that caused pre6 to be broken.
17566 - Don't keep rephist info for routers that haven't had activity for
17567 24 hours. (This matters now that clients have keys, since we track
17569 - Never call close_temp_logs while validating log options.
17570 - Fix backslash-escaping on tor.sh.in and torctl.in.
17573 - Implement weekly/monthly/daily accounting: now you specify your
17574 hibernation properties by
17575 AccountingMax N bytes|KB|MB|GB|TB
17576 AccountingStart day|week|month [day] HH:MM
17577 Defaults to "month 1 0:00".
17578 - Let bandwidth and interval config options be specified as 5 bytes,
17579 kb, kilobytes, etc; and as seconds, minutes, hours, days, weeks.
17580 - kill -USR2 now moves all logs to loglevel debug (kill -HUP to
17581 get back to normal.)
17582 - If your requested entry or exit node has advertised bandwidth 0,
17584 - Be more greedy about filling up relay cells -- we try reading again
17585 once we've processed the stuff we read, in case enough has arrived
17586 to fill the last cell completely.
17587 - Apply NT service patch from Osamu Fujino. Still needs more work.
17590 Changes in version 0.0.9pre6 - 2004-11-15
17591 o Bugfixes on 0.0.8.1:
17592 - Fix assert failure on malformed socks4a requests.
17593 - Use identity comparison, not nickname comparison, to choose which
17594 half of circuit-ID-space each side gets to use. This is needed
17595 because sometimes we think of a router as a nickname, and sometimes
17596 as a hex ID, and we can't predict what the other side will do.
17597 - Catch and ignore SIGXFSZ signals when log files exceed 2GB; our
17598 write() call will fail and we handle it there.
17599 - Add a FAST_SMARTLIST define to optionally inline smartlist_get
17600 and smartlist_len, which are two major profiling offenders.
17602 o Bugfixes on 0.0.9pre5:
17603 - Fix a bug in read_all that was corrupting config files on windows.
17604 - When we're raising the max number of open file descriptors to
17605 'unlimited', don't log that we just raised it to '-1'.
17606 - Include event code with events, as required by control-spec.txt.
17607 - Don't give a fingerprint when clients do --list-fingerprint:
17608 it's misleading, because it will never be the same again.
17609 - Stop using strlcpy in tor_strndup, since it was slowing us
17611 - Remove warn on startup about missing cached-directory file.
17612 - Make kill -USR1 work again.
17613 - Hibernate if we start tor during the "wait for wakeup-time" phase
17614 of an accounting interval. Log our hibernation plans better.
17615 - Authoritative dirservers now also cache their directory, so they
17616 have it on start-up.
17619 - Fetch running-routers; cache running-routers; compress
17620 running-routers; serve compressed running-routers.z
17621 - Add NSI installer script contributed by J Doe.
17622 - Commit VC6 and VC7 workspace/project files.
17623 - Commit a tor.spec for making RPM files, with help from jbash.
17624 - Add contrib/torctl.in contributed by Glenn Fink.
17625 - Implement the control-spec's SAVECONF command, to write your
17626 configuration to torrc.
17627 - Get cookie authentication for the controller closer to working.
17628 - Include control-spec.txt in the tarball.
17629 - When set_conf changes our server descriptor, upload a new copy.
17630 But don't upload it too often if there are frequent changes.
17631 - Document authentication config in man page, and document signals
17633 - Clean up confusing parts of man page and torrc.sample.
17634 - Make expand_filename handle ~ and ~username.
17635 - Use autoconf to enable largefile support where necessary. Use
17636 ftello where available, since ftell can fail at 2GB.
17637 - Distinguish between TOR_TLS_CLOSE and TOR_TLS_ERROR, so we can
17638 log more informatively.
17639 - Give a slightly more useful output for "tor -h".
17640 - Refuse application socks connections to port 0.
17641 - Check clock skew for verified servers, but allow unverified
17642 servers and clients to have any clock skew.
17643 - Break DirFetchPostPeriod into:
17644 - DirFetchPeriod for fetching full directory,
17645 - StatusFetchPeriod for fetching running-routers,
17646 - DirPostPeriod for posting server descriptor,
17647 - RendPostPeriod for posting hidden service descriptors.
17648 - Make sure the hidden service descriptors are at a random offset
17649 from each other, to hinder linkability.
17652 Changes in version 0.0.9pre5 - 2004-11-09
17653 o Bugfixes on 0.0.9pre4:
17654 - Fix a seg fault in unit tests (doesn't affect main program).
17655 - Fix an assert bug where a hidden service provider would fail if
17656 the first hop of his rendezvous circuit was down.
17657 - Hidden service operators now correctly handle version 1 style
17658 INTRODUCE1 cells (nobody generates them still, so not a critical
17660 - If do_hup fails, actually notice.
17661 - Handle more errnos from accept() without closing the listener.
17662 Some OpenBSD machines were closing their listeners because
17663 they ran out of file descriptors.
17664 - Send resolve cells to exit routers that are running a new
17665 enough version of the resolve code to work right.
17666 - Better handling of winsock includes on non-MSV win32 compilers.
17667 - Some people had wrapped their tor client/server in a script
17668 that would restart it whenever it died. This did not play well
17669 with our "shut down if your version is obsolete" code. Now people
17670 don't fetch a new directory if their local cached version is
17672 - Make our autogen.sh work on ksh as well as bash.
17675 - Hibernation: New config option "AccountingMaxKB" lets you
17676 set how many KBytes per month you want to allow your server to
17677 consume. Rather than spreading those bytes out evenly over the
17678 month, we instead hibernate for some of the month and pop up
17679 at a deterministic time, work until the bytes are consumed, then
17680 hibernate again. Config option "MonthlyAccountingStart" lets you
17681 specify which day of the month your billing cycle starts on.
17682 - Control interface: a separate program can now talk to your
17683 client/server over a socket, and get/set config options, receive
17684 notifications of circuits and streams starting/finishing/dying,
17685 bandwidth used, etc. The next step is to get some GUIs working.
17686 Let us know if you want to help out. See doc/control-spec.txt .
17687 - Ship a contrib/tor-control.py as an example script to interact
17688 with the control port.
17689 - "tor --hash-password zzyxz" will output a salted password for
17690 use in authenticating to the control interface.
17691 - New log format in config:
17692 "Log minsev[-maxsev] stdout|stderr|syslog" or
17693 "Log minsev[-maxsev] file /var/foo"
17696 - DirPolicy config option, to let people reject incoming addresses
17697 from their dirserver.
17698 - "tor --list-fingerprint" will list your identity key fingerprint
17700 - Add "pass" target for RedirectExit, to make it easier to break
17701 out of a sequence of RedirectExit rules.
17702 - Clients now generate a TLS cert too, in preparation for having
17703 them act more like real nodes.
17704 - Ship src/win32/ in the tarball, so people can use it to build.
17705 - Make old win32 fall back to CWD if SHGetSpecialFolderLocation
17707 - New "router-status" line in directory, to better bind each verified
17708 nickname to its identity key.
17709 - Deprecate unofficial config option abbreviations, and abbreviations
17710 not on the command line.
17711 - Add a pure-C tor-resolve implementation.
17712 - Use getrlimit and friends to ensure we can reach MaxConn (currently
17713 1024) file descriptors.
17715 o Code security improvements, inspired by Ilja:
17716 - Replace sprintf with snprintf. (I think they were all safe, but
17718 - Replace strcpy/strncpy with strlcpy in more places.
17719 - Avoid strcat; use snprintf or strlcat instead.
17720 - snprintf wrapper with consistent (though not C99) overflow behavior.
17723 Changes in version 0.0.9pre4 - 2004-10-17
17724 o Bugfixes on 0.0.9pre3:
17725 - If the server doesn't specify an exit policy, use the real default
17726 exit policy, not reject *:*.
17727 - Ignore fascistfirewall when uploading/downloading hidden service
17728 descriptors, since we go through Tor for those; and when using
17729 an HttpProxy, since we assume it can reach them all.
17730 - When looking for an authoritative dirserver, use only the ones
17731 configured at boot. Don't bother looking in the directory.
17732 - The rest of the fix for get_default_conf_file() on older win32.
17733 - Make 'Routerfile' config option obsolete.
17736 - New 'MyFamily nick1,...' config option for a server to
17737 specify other servers that shouldn't be used in the same circuit
17738 with it. Only believed if nick1 also specifies us.
17739 - New 'NodeFamily nick1,nick2,...' config option for a client to
17740 specify nodes that it doesn't want to use in the same circuit.
17741 - New 'Redirectexit pattern address:port' config option for a
17742 server to redirect exit connections, e.g. to a local squid.
17745 Changes in version 0.0.9pre3 - 2004-10-13
17746 o Bugfixes on 0.0.8.1:
17747 - Better torrc example lines for dirbindaddress and orbindaddress.
17748 - Improved bounds checking on parsed ints (e.g. config options and
17749 the ones we find in directories.)
17750 - Better handling of size_t vs int, so we're more robust on 64
17752 - Fix the rest of the bug where a newly started OR would appear
17753 as unverified even after we've added his fingerprint and hupped
17755 - Fix a bug from 0.0.7: when read() failed on a stream, we would
17756 close it without sending back an end. So 'connection refused'
17757 would simply be ignored and the user would get no response.
17759 o Bugfixes on 0.0.9pre2:
17760 - Serving the cached-on-disk directory to people is bad. We now
17761 provide no directory until we've fetched a fresh one.
17762 - Workaround for bug on windows where cached-directories get crlf
17764 - Make get_default_conf_file() work on older windows too.
17765 - If we write a *:* exit policy line in the descriptor, don't write
17766 any more exit policy lines.
17769 - Use only 0.0.9pre1 and later servers for resolve cells.
17770 - Make the dirservers file obsolete.
17771 - Include a dir-signing-key token in directories to tell the
17772 parsing entity which key is being used to sign.
17773 - Remove the built-in bulky default dirservers string.
17774 - New config option "Dirserver %s:%d [fingerprint]", which can be
17775 repeated as many times as needed. If no dirservers specified,
17776 default to moria1,moria2,tor26.
17777 - Make moria2 advertise a dirport of 80, so people behind firewalls
17778 will be able to get a directory.
17779 - Http proxy support
17780 - Dirservers translate requests for http://%s:%d/x to /x
17781 - You can specify "HttpProxy %s[:%d]" and all dir fetches will
17782 be routed through this host.
17783 - Clients ask for /tor/x rather than /x for new enough dirservers.
17784 This way we can one day coexist peacefully with apache.
17785 - Clients specify a "Host: %s%d" http header, to be compatible
17786 with more proxies, and so running squid on an exit node can work.
17789 Changes in version 0.0.8.1 - 2004-10-13
17791 - Fix a seg fault that can be triggered remotely for Tor
17792 clients/servers with an open dirport.
17793 - Fix a rare assert trigger, where routerinfos for entries in
17794 our cpath would expire while we're building the path.
17795 - Fix a bug in OutboundBindAddress so it (hopefully) works.
17796 - Fix a rare seg fault for people running hidden services on
17797 intermittent connections.
17798 - Fix a bug in parsing opt keywords with objects.
17799 - Fix a stale pointer assert bug when a stream detaches and
17801 - Fix a string format vulnerability (probably not exploitable)
17802 in reporting stats locally.
17803 - Fix an assert trigger: sometimes launching circuits can fail
17804 immediately, e.g. because too many circuits have failed recently.
17805 - Fix a compile warning on 64 bit platforms.
17808 Changes in version 0.0.9pre2 - 2004-10-03
17810 - Make fetching a cached directory work for 64-bit platforms too.
17811 - Make zlib.h a required header, not an optional header.
17814 Changes in version 0.0.9pre1 - 2004-10-01
17816 - Stop using separate defaults for no-config-file and
17817 empty-config-file. Now you have to explicitly turn off SocksPort,
17818 if you don't want it open.
17819 - Fix a bug in OutboundBindAddress so it (hopefully) works.
17820 - Improve man page to mention more of the 0.0.8 features.
17821 - Fix a rare seg fault for people running hidden services on
17822 intermittent connections.
17823 - Change our file IO stuff (especially wrt OpenSSL) so win32 is
17825 - Fix more dns related bugs: send back resolve_failed and end cells
17826 more reliably when the resolve fails, rather than closing the
17827 circuit and then trying to send the cell. Also attach dummy resolve
17828 connections to a circuit *before* calling dns_resolve(), to fix
17829 a bug where cached answers would never be sent in RESOLVED cells.
17830 - When we run out of disk space, or other log writing error, don't
17831 crash. Just stop logging to that log and continue.
17832 - We were starting to daemonize before we opened our logs, so if
17833 there were any problems opening logs, we would complain to stderr,
17834 which wouldn't work, and then mysteriously exit.
17835 - Fix a rare bug where sometimes a verified OR would connect to us
17836 before he'd uploaded his descriptor, which would cause us to
17837 assign conn->nickname as though he's unverified. Now we look through
17838 the fingerprint list to see if he's there.
17839 - Fix a rare assert trigger, where routerinfos for entries in
17840 our cpath would expire while we're building the path.
17843 - Clients can ask dirservers for /dir.z to get a compressed version
17844 of the directory. Only works for servers running 0.0.9, of course.
17845 - Make clients cache directories and use them to seed their router
17846 lists at startup. This means clients have a datadir again.
17847 - Configuration infrastructure support for warning on obsolete
17849 - Respond to content-encoding headers by trying to uncompress as
17851 - Reply with a deflated directory when a client asks for "dir.z".
17852 We could use allow-encodings instead, but allow-encodings isn't
17853 specified in HTTP 1.0.
17854 - Raise the max dns workers from 50 to 100.
17855 - Discourage people from setting their dirfetchpostperiod more often
17856 than once per minute.
17857 - Protect dirservers from overzealous descriptor uploading -- wait
17858 10 seconds after directory gets dirty, before regenerating.
17861 Changes in version 0.0.8 - 2004-08-25
17862 o Port it to SunOS 5.9 / Athena
17865 Changes in version 0.0.8rc2 - 2004-08-20
17866 o Make it compile on cygwin again.
17867 o When picking unverified routers, skip those with low uptime and/or
17868 low bandwidth, depending on what properties you care about.
17871 Changes in version 0.0.8rc1 - 2004-08-18
17872 o Changes from 0.0.7.3:
17874 - Fix assert triggers: if the other side returns an address 0.0.0.0,
17875 don't put it into the client dns cache.
17876 - If a begin failed due to exit policy, but we believe the IP address
17877 should have been allowed, switch that router to exitpolicy reject *:*
17878 until we get our next directory.
17880 - Clients choose nodes proportional to advertised bandwidth.
17881 - Avoid using nodes with low uptime as introduction points.
17882 - Handle servers with dynamic IP addresses: don't replace
17883 options->Address with the resolved one at startup, and
17884 detect our address right before we make a routerinfo each time.
17885 - 'FascistFirewall' option to pick dirservers and ORs on specific
17886 ports; plus 'FirewallPorts' config option to tell FascistFirewall
17887 which ports are open. (Defaults to 80,443)
17888 - Be more aggressive about trying to make circuits when the network
17889 has changed (e.g. when you unsuspend your laptop).
17890 - Check for time skew on http headers; report date in response to
17892 - If the entrynode config line has only one node, don't pick it as
17894 - Add strict{entry|exit}nodes config options. If set to 1, then
17895 we refuse to build circuits that don't include the specified entry
17897 - OutboundBindAddress config option, to bind to a specific
17898 IP address for outgoing connect()s.
17899 - End truncated log entries (e.g. directories) with "[truncated]".
17901 o Patches to 0.0.8preX:
17903 - Patches to compile and run on win32 again (maybe)?
17904 - Fix crash when looking for ~/.torrc with no $HOME set.
17905 - Fix a race bug in the unit tests.
17906 - Handle verified/unverified name collisions better when new
17907 routerinfo's arrive in a directory.
17908 - Sometimes routers were getting entered into the stats before
17909 we'd assigned their identity_digest. Oops.
17910 - Only pick and establish intro points after we've gotten a
17913 - AllowUnverifiedNodes config option to let circuits choose no-name
17914 routers in entry,middle,exit,introduction,rendezvous positions.
17915 Allow middle and rendezvous positions by default.
17916 - Add a man page for tor-resolve.
17919 Changes in version 0.0.7.3 - 2004-08-12
17920 o Stop dnsworkers from triggering an assert failure when you
17921 ask them to resolve the host "".
17924 Changes in version 0.0.8pre3 - 2004-08-09
17925 o Changes from 0.0.7.2:
17926 - Allow multiple ORs with same nickname in routerlist -- now when
17927 people give us one identity key for a nickname, then later
17928 another, we don't constantly complain until the first expires.
17929 - Remember used bandwidth (both in and out), and publish 15-minute
17930 snapshots for the past day into our descriptor.
17931 - You can now fetch $DIRURL/running-routers to get just the
17932 running-routers line, not the whole descriptor list. (But
17933 clients don't use this yet.)
17934 - When people mistakenly use Tor as an http proxy, point them
17935 at the tor-doc.html rather than the INSTALL.
17936 - Remove our mostly unused -- and broken -- hex_encode()
17937 function. Use base16_encode() instead. (Thanks to Timo Lindfors
17938 for pointing out this bug.)
17939 - Rotate onion keys every 12 hours, not every 2 hours, so we have
17940 fewer problems with people using the wrong key.
17941 - Change the default exit policy to reject the default edonkey,
17942 kazaa, gnutella ports.
17943 - Add replace_file() to util.[ch] to handle win32's rename().
17945 o Changes from 0.0.8preX:
17946 - Fix two bugs in saving onion keys to disk when rotating, so
17947 hopefully we'll get fewer people using old onion keys.
17948 - Fix an assert error that was making SocksPolicy not work.
17949 - Be willing to expire routers that have an open dirport -- it's
17950 just the authoritative dirservers we want to not forget.
17951 - Reject tor-resolve requests for .onion addresses early, so we
17952 don't build a whole rendezvous circuit and then fail.
17953 - When you're warning a server that he's unverified, don't cry
17954 wolf unpredictably.
17955 - Fix a race condition: don't try to extend onto a connection
17956 that's still handshaking.
17957 - For servers in clique mode, require the conn to be open before
17958 you'll choose it for your path.
17959 - Fix some cosmetic bugs about duplicate mark-for-close, lack of
17960 end relay cell, etc.
17961 - Measure bandwidth capacity over the last 24 hours, not just 12
17962 - Bugfix: authoritative dirservers were making and signing a new
17963 directory for each client, rather than reusing the cached one.
17966 Changes in version 0.0.8pre2 - 2004-08-04
17967 o Changes from 0.0.7.2:
17969 - Check directory signature _before_ you decide whether you're
17970 you're running an obsolete version and should exit.
17971 - Check directory signature _before_ you parse the running-routers
17972 list to decide who's running or verified.
17973 - Bugfixes and features:
17974 - Check return value of fclose while writing to disk, so we don't
17975 end up with broken files when servers run out of disk space.
17976 - Log a warning if the user uses an unsafe socks variant, so people
17977 are more likely to learn about privoxy or socat.
17978 - Dirservers now include RFC1123-style dates in the HTTP headers,
17979 which one day we will use to better detect clock skew.
17981 o Changes from 0.0.8pre1:
17982 - Make it compile without warnings again on win32.
17983 - Log a warning if you're running an unverified server, to let you
17984 know you might want to get it verified.
17985 - Only pick a default nickname if you plan to be a server.
17988 Changes in version 0.0.8pre1 - 2004-07-23
17990 - Made our unit tests compile again on OpenBSD 3.5, and tor
17991 itself compile again on OpenBSD on a sparc64.
17992 - We were neglecting milliseconds when logging on win32, so
17993 everything appeared to happen at the beginning of each second.
17995 o Protocol changes:
17996 - 'Extend' relay cell payloads now include the digest of the
17997 intended next hop's identity key. Now we can verify that we're
17998 extending to the right router, and also extend to routers we
17999 hadn't heard of before.
18002 - Tor nodes can now act as relays (with an advertised ORPort)
18003 without being manually verified by the dirserver operators.
18004 - Uploaded descriptors of unverified routers are now accepted
18005 by the dirservers, and included in the directory.
18006 - Verified routers are listed by nickname in the running-routers
18007 list; unverified routers are listed as "$<fingerprint>".
18008 - We now use hash-of-identity-key in most places rather than
18009 nickname or addr:port, for improved security/flexibility.
18010 - To avoid Sybil attacks, paths still use only verified servers.
18011 But now we have a chance to play around with hybrid approaches.
18012 - Nodes track bandwidth usage to estimate capacity (not used yet).
18013 - ClientOnly option for nodes that never want to become servers.
18014 - Directory caching.
18015 - "AuthoritativeDir 1" option for the official dirservers.
18016 - Now other nodes (clients and servers) will cache the latest
18017 directory they've pulled down.
18018 - They can enable their DirPort to serve it to others.
18019 - Clients will pull down a directory from any node with an open
18020 DirPort, and check the signature/timestamp correctly.
18021 - Authoritative dirservers now fetch directories from other
18022 authdirservers, to stay better synced.
18023 - Running-routers list tells who's down also, along with noting
18024 if they're verified (listed by nickname) or unverified (listed
18026 - Allow dirservers to serve running-router list separately.
18027 This isn't used yet.
18028 - ORs connect-on-demand to other ORs
18029 - If you get an extend cell to an OR you're not connected to,
18030 connect, handshake, and forward the create cell.
18031 - The authoritative dirservers stay connected to everybody,
18032 and everybody stays connected to 0.0.7 servers, but otherwise
18033 clients/servers expire unused connections after 5 minutes.
18034 - When servers get a sigint, they delay 30 seconds (refusing new
18035 connections) then exit. A second sigint causes immediate exit.
18036 - File and name management:
18037 - Look for .torrc if no CONFDIR "torrc" is found.
18038 - If no datadir is defined, then choose, make, and secure ~/.tor
18040 - If torrc not found, exitpolicy reject *:*.
18041 - Expands ~/ in filenames to $HOME/ (but doesn't yet expand ~arma).
18042 - If no nickname is defined, derive default from hostname.
18043 - Rename secret key files, e.g. identity.key -> secret_id_key,
18044 to discourage people from mailing their identity key to tor-ops.
18045 - Refuse to build a circuit before the directory has arrived --
18046 it won't work anyway, since you won't know the right onion keys
18048 - Try other dirservers immediately if the one you try is down. This
18049 should tolerate down dirservers better now.
18050 - Parse tor version numbers so we can do an is-newer-than check
18051 rather than an is-in-the-list check.
18052 - New socks command 'resolve', to let us shim gethostbyname()
18054 - A 'tor_resolve' script to access the socks resolve functionality.
18055 - A new socks-extensions.txt doc file to describe our
18056 interpretation and extensions to the socks protocols.
18057 - Add a ContactInfo option, which gets published in descriptor.
18058 - Publish OR uptime in descriptor (and thus in directory) too.
18059 - Write tor version at the top of each log file
18060 - New docs in the tarball:
18062 - Document that you should proxy your SSL traffic too.
18065 Changes in version 0.0.7.2 - 2004-07-07
18066 o A better fix for the 0.0.0.0 problem, that will hopefully
18067 eliminate the remaining related assertion failures.
18070 Changes in version 0.0.7.1 - 2004-07-04
18071 o When an address resolves to 0.0.0.0, treat it as a failed resolve,
18072 since internally we use 0.0.0.0 to signify "not yet resolved".
18075 Changes in version 0.0.7 - 2004-06-07
18076 o Updated the man page to reflect the new features.
18079 Changes in version 0.0.7rc2 - 2004-06-06
18080 o Changes from 0.0.7rc1:
18081 - Make it build on Win32 again.
18082 o Changes from 0.0.6.2:
18083 - Rotate dnsworkers and cpuworkers on SIGHUP, so they get new config
18087 Changes in version 0.0.7rc1 - 2004-06-02
18089 - On sighup, we were adding another log without removing the first
18090 one. So log messages would get duplicated n times for n sighups.
18091 - Several cases of using a connection after we'd freed it. The
18092 problem was that connections that are pending resolve are in both
18093 the pending_resolve tree, and also the circuit's resolving_streams
18094 list. When you want to remove one, you must remove it from both.
18095 - Fix a double-mark-for-close where an end cell arrived for a
18096 resolving stream, and then the resolve failed.
18097 - Check directory signatures based on name of signer, not on whom
18098 we got the directory from. This will let us cache directories more
18101 - Crank up some of our constants to handle more users.
18104 Changes in version 0.0.7pre1 - 2004-06-02
18105 o Fixes for crashes and other obnoxious bugs:
18106 - Fix an epipe bug: sometimes when directory connections failed
18107 to connect, we would give them a chance to flush before closing
18109 - When we detached from a circuit because of resolvefailed, we
18110 would immediately try the same circuit twice more, and then
18111 give up on the resolve thinking we'd tried three different
18113 - Limit the number of intro circuits we'll attempt to build for a
18114 hidden service per 15-minute period.
18115 - Check recommended-software string *early*, before actually parsing
18116 the directory. Thus we can detect an obsolete version and exit,
18117 even if the new directory format doesn't parse.
18118 o Fixes for security bugs:
18119 - Remember which nodes are dirservers when you startup, and if a
18120 random OR enables his dirport, don't automatically assume he's
18121 a trusted dirserver.
18123 - Directory connections were asking the wrong poll socket to
18124 start writing, and not asking themselves to start writing.
18125 - When we detached from a circuit because we sent a begin but
18126 didn't get a connected, we would use it again the first time;
18127 but after that we would correctly switch to a different one.
18128 - Stop warning when the first onion decrypt attempt fails; they
18129 will sometimes legitimately fail now that we rotate keys.
18130 - Override unaligned-access-ok check when $host_cpu is ia64 or
18131 arm. Apparently they allow it but the kernel whines.
18132 - Dirservers try to reconnect periodically too, in case connections
18134 - Fix some memory leaks in directory servers.
18135 - Allow backslash in Win32 filenames.
18136 - Made Tor build complain-free on FreeBSD, hopefully without
18137 breaking other BSD builds. We'll see.
18139 - Doxygen markup on all functions and global variables.
18140 - Make directory functions update routerlist, not replace it. So
18141 now directory disagreements are not so critical a problem.
18142 - Remove the upper limit on number of descriptors in a dirserver's
18143 directory (not that we were anywhere close).
18144 - Allow multiple logfiles at different severity ranges.
18145 - Allow *BindAddress to specify ":port" rather than setting *Port
18146 separately. Allow multiple instances of each BindAddress config
18147 option, so you can bind to multiple interfaces if you want.
18148 - Allow multiple exit policy lines, which are processed in order.
18149 Now we don't need that huge line with all the commas in it.
18150 - Enable accept/reject policies on SOCKS connections, so you can bind
18151 to 0.0.0.0 but still control who can use your OP.
18154 Changes in version 0.0.6.2 - 2004-05-16
18155 o Our integrity-checking digest was checking only the most recent cell,
18156 not the previous cells like we'd thought.
18157 Thanks to Stefan Mark for finding the flaw!
18160 Changes in version 0.0.6.1 - 2004-05-06
18161 o Fix two bugs in our AES counter-mode implementation (this affected
18162 onion-level stream encryption, but not TLS-level). It turns
18163 out we were doing something much more akin to a 16-character
18164 polyalphabetic cipher. Oops.
18165 Thanks to Stefan Mark for finding the flaw!
18166 o Retire moria3 as a directory server, and add tor26 as a directory
18170 Changes in version 0.0.6 - 2004-05-02
18171 [version bump only]
18174 Changes in version 0.0.6rc4 - 2004-05-01
18175 o Update the built-in dirservers list to use the new directory format
18176 o Fix a rare seg fault: if a node offering a hidden service attempts
18177 to build a circuit to Alice's rendezvous point and fails before it
18178 reaches the last hop, it retries with a different circuit, but
18180 o Handle windows socket errors correctly.
18183 Changes in version 0.0.6rc3 - 2004-04-28
18184 o Don't expire non-general excess circuits (if we had enough
18185 circuits open, we were expiring rendezvous circuits -- even
18186 when they had a stream attached. oops.)
18187 o Fetch randomness from /dev/urandom better (not via fopen/fread)
18188 o Better debugging for tls errors
18189 o Some versions of openssl have an SSL_pending function that erroneously
18190 returns bytes when there is a non-application record pending.
18191 o Set Content-Type on the directory and hidserv descriptor.
18192 o Remove IVs from cipher code, since AES-ctr has none.
18193 o Win32 fixes. Tor now compiles on win32 with no warnings/errors.
18194 o We were using an array of length zero in a few places.
18195 o win32's gethostbyname can't resolve an IP to an IP.
18196 o win32's close can't close a socket.
18199 Changes in version 0.0.6rc2 - 2004-04-26
18200 o Fix a bug where we were closing tls connections intermittently.
18201 It turns out openssl keeps its errors around -- so if an error
18202 happens, and you don't ask about it, and then another openssl
18203 operation happens and succeeds, and you ask if there was an error,
18204 it tells you about the first error. Fun fun.
18205 o Fix a bug that's been lurking since 27 may 03 (!)
18206 When passing back a destroy cell, we would use the wrong circ id.
18207 'Mostly harmless', but still worth fixing.
18208 o Since we don't support truncateds much, don't bother sending them;
18209 just close the circ.
18210 o check for <machine/limits.h> so we build on NetBSD again (I hope).
18211 o don't crash if a conn that sent a begin has suddenly lost its circuit
18212 (this was quite rare).
18215 Changes in version 0.0.6rc1 - 2004-04-25
18216 o We now rotate link (tls context) keys and onion keys.
18217 o CREATE cells now include oaep padding, so you can tell
18218 if you decrypted them correctly.
18219 o Add bandwidthburst to server descriptor.
18220 o Directories now say which dirserver signed them.
18221 o Use a tor_assert macro that logs failed assertions too.
18224 Changes in version 0.0.6pre5 - 2004-04-18
18225 o changes from 0.0.6pre4:
18226 - make tor build on broken freebsd 5.2 installs
18227 - fix a failed assert when you try an intro point, get a nack, and try
18228 a second one and it works.
18229 - when alice uses a port that the hidden service doesn't accept,
18230 it now sends back an end cell (denied by exit policy). otherwise
18231 alice would just have to wait to time out.
18232 - fix another rare bug: when we had tried all the intro
18233 points for a hidden service, we fetched the descriptor
18234 again, but we left our introcirc thinking it had already
18235 sent an intro, so it kept waiting for a response...
18236 - bugfix: when you sleep your hidden-service laptop, as soon
18237 as it wakes up it tries to upload a service descriptor, but
18238 socketpair fails for some reason (localhost not up yet?).
18239 now we simply give up on that upload, and we'll try again later.
18240 i'd still like to find the bug though.
18241 - if an intro circ waiting for an ack dies before getting one, then
18243 - we were reusing stale service descriptors and refetching usable
18247 Changes in version 0.0.6pre4 - 2004-04-14
18248 o changes from 0.0.6pre3:
18249 - when bob fails to connect to the rendezvous point, and his
18250 circ didn't fail because of the rendezvous point itself, then
18251 he retries a couple of times
18252 - we expire introduction and rendezvous circs more thoroughly
18253 (sometimes they were hanging around forever)
18254 - we expire unattached rendezvous streams that have been around
18255 too long (they were sticking around forever).
18256 - fix a measly fencepost error that was crashing everybody with
18260 Changes in version 0.0.6pre3 - 2004-04-14
18261 o changes from 0.0.6pre2:
18262 - make hup work again
18263 - fix some memory leaks for dirservers
18264 - allow more skew in rendezvous descriptor timestamps, to help
18265 handle people like blanu who don't know what time it is
18266 - normal circs are 3 hops, but some rend/intro circs are 4, if
18267 the initiator doesn't get to choose the last hop
18268 - send acks for introductions, so alice can know whether to try
18270 - bob publishes intro points more correctly
18271 o changes from 0.0.5:
18272 - fix an assert trigger that's been plaguing us since the days
18273 of 0.0.2prexx (thanks weasel!)
18274 - retry stream correctly when we fail to connect because of
18275 exit-policy-reject (should try another) or can't-resolve-address
18276 (also should try another, because dns on random internet servers
18278 - when we hup a dirserver and we've *removed* a server from the
18279 approved-routers list, now we remove that server from the
18280 in-memory directories too
18283 Changes in version 0.0.6pre2 - 2004-04-08
18284 o We fixed our base32 implementation. Now it works on all architectures.
18287 Changes in version 0.0.6pre1 - 2004-04-08
18289 - Hidden services and rendezvous points are implemented. Go to
18290 http://6sxoyfb3h2nvok2d.onion/ for an index of currently available
18291 hidden services. (This only works via a socks4a proxy such as
18292 Privoxy, and currently it's quite slow.)
18295 Changes in version 0.0.5 - 2004-03-30
18296 [version bump only]
18299 Changes in version 0.0.5rc3 - 2004-03-29
18300 o Install torrc as torrc.sample -- we no longer clobber your
18302 o Re-enable recommendedversion checking (we broke it in rc2, oops)
18303 o Add in a 'notice' log level for things the operator should hear
18304 but that aren't warnings
18307 Changes in version 0.0.5rc2 - 2004-03-29
18308 o Hold socks connection open until reply is flushed (if possible)
18309 o Make exit nodes resolve IPs to IPs immediately, rather than asking
18310 the dns farm to do it.
18311 o Fix c99 aliasing warnings in rephist.c
18312 o Don't include server descriptors that are older than 24 hours in the
18314 o Give socks 'reject' replies their whole 15s to attempt to flush,
18315 rather than seeing the 60s timeout and assuming the flush had failed.
18316 o Clean automake droppings from the cvs repository
18319 Changes in version 0.0.5rc1 - 2004-03-28
18320 o Fix mangled-state bug in directory fetching (was causing sigpipes).
18321 o Only build circuits after we've fetched the directory: clients were
18322 using only the directory servers before they'd fetched a directory.
18323 This also means longer startup time; so it goes.
18324 o Fix an assert trigger where an OP would fail to handshake, and we'd
18325 expect it to have a nickname.
18326 o Work around a tsocks bug: do a socks reject when AP connection dies
18327 early, else tsocks goes into an infinite loop.
18330 Changes in version 0.0.4 - 2004-03-26
18331 o When connecting to a dirserver or OR and the network is down,
18335 Changes in version 0.0.3 - 2004-03-26
18336 o Warn and fail if server chose a nickname with illegal characters
18337 o Port to Solaris and Sparc:
18338 - include missing header fcntl.h
18339 - have autoconf find -lsocket -lnsl automatically
18340 - deal with hardware word alignment
18341 - make uname() work (solaris has a different return convention)
18342 - switch from using signal() to sigaction()
18343 o Preliminary work on reputation system:
18344 - Keep statistics on success/fail of connect attempts; they're published
18345 by kill -USR1 currently.
18346 - Add a RunTesting option to try to learn link state by creating test
18347 circuits, even when SocksPort is off.
18348 - Remove unused open circuits when there are too many.
18351 Changes in version 0.0.2 - 2004-03-19
18352 - Include strlcpy and strlcat for safer string ops
18353 - define INADDR_NONE so we compile (but still not run) on solaris
18356 Changes in version 0.0.2pre27 - 2004-03-14
18358 - Allow internal tor networks (we were rejecting internal IPs,
18359 now we allow them if they're set explicitly).
18360 - And fix a few endian issues.
18363 Changes in version 0.0.2pre26 - 2004-03-14
18365 - If a stream times out after 15s without a connected cell, don't
18366 try that circuit again: try a new one.
18367 - Retry streams at most 4 times. Then give up.
18368 - When a dirserver gets a descriptor from an unknown router, it
18369 logs its fingerprint (so the dirserver operator can choose to
18370 accept it even without mail from the server operator).
18371 - Inform unapproved servers when we reject their descriptors.
18372 - Make tor build on Windows again. It works as a client, who knows
18374 - Clearer instructions in the torrc for how to set up a server.
18375 - Be more efficient about reading fd's when our global token bucket
18376 (used for rate limiting) becomes empty.
18378 - Stop asserting that computers always go forward in time. It's
18380 - When we sent a cell (e.g. destroy) and then marked an OR connection
18381 expired, we might close it before finishing a flush if the other
18382 side isn't reading right then.
18383 - Don't allow dirservers to start if they haven't defined
18384 RecommendedVersions
18385 - We were caching transient dns failures. Oops.
18386 - Prevent servers from publishing an internal IP as their address.
18387 - Address a strcat vulnerability in circuit.c
18390 Changes in version 0.0.2pre25 - 2004-03-04
18392 - Put the OR's IP in its router descriptor, not its fqdn. That way
18393 we'll stop being stalled by gethostbyname for nodes with flaky dns,
18396 - If the user typed in an address that didn't resolve, the server
18400 Changes in version 0.0.2pre24 - 2004-03-03
18402 - Fix an assertion failure in dns.c, where we were trying to dequeue
18403 a pending dns resolve even if it wasn't pending
18404 - Fix a spurious socks5 warning about still trying to write after the
18405 connection is finished.
18406 - Hold certain marked_for_close connections open until they're finished
18407 flushing, rather than losing bytes by closing them too early.
18408 - Correctly report the reason for ending a stream
18409 - Remove some duplicate calls to connection_mark_for_close
18410 - Put switch_id and start_daemon earlier in the boot sequence, so it
18411 will actually try to chdir() to options.DataDirectory
18412 - Make 'make test' exit(1) if a test fails; fix some unit tests
18413 - Make tor fail when you use a config option it doesn't know about,
18414 rather than warn and continue.
18415 - Make --version work
18416 - Bugfixes on the rpm spec file and tor.sh, so it's more up to date
18419 Changes in version 0.0.2pre23 - 2004-02-29
18421 - Print a statement when the first circ is finished, so the user
18422 knows it's working.
18423 - If a relay cell is unrecognized at the end of the circuit,
18424 send back a destroy. (So attacks to mutate cells are more
18426 - New config option 'excludenodes' to avoid certain nodes for circuits.
18427 - When it daemonizes, it chdir's to the DataDirectory rather than "/",
18428 so you can collect coredumps there.
18430 - Fix a bug in tls flushing where sometimes data got wedged and
18431 didn't flush until more data got sent. Hopefully this bug was
18432 a big factor in the random delays we were seeing.
18433 - Make 'connected' cells include the resolved IP, so the client
18434 dns cache actually gets populated.
18435 - Disallow changing from ORPort=0 to ORPort>0 on hup.
18436 - When we time-out on a stream and detach from the circuit, send an
18437 end cell down it first.
18438 - Only warn about an unknown router (in exitnodes, entrynodes,
18439 excludenodes) after we've fetched a directory.
18442 Changes in version 0.0.2pre22 - 2004-02-26
18444 - Servers publish less revealing uname information in descriptors.
18445 - More memory tracking and assertions, to crash more usefully when
18447 - If the default torrc isn't there, just use some default defaults.
18448 Plus provide an internal dirservers file if they don't have one.
18449 - When the user tries to use Tor as an http proxy, give them an http
18450 501 failure explaining that we're a socks proxy.
18451 - Dump a new router.desc on hup, to help confused people who change
18452 their exit policies and then wonder why router.desc doesn't reflect
18454 - Clean up the generic tor.sh init script that we ship with.
18456 - If the exit stream is pending on the resolve, and a destroy arrives,
18457 then the stream wasn't getting removed from the pending list. I
18458 think this was the one causing recent server crashes.
18459 - Use a more robust poll on OSX 10.3, since their poll is flaky.
18460 - When it couldn't resolve any dirservers, it was useless from then on.
18461 Now it reloads the RouterFile (or default dirservers) if it has no
18463 - Move the 'tor' binary back to /usr/local/bin/ -- it turns out
18464 many users don't even *have* a /usr/local/sbin/.
18467 Changes in version 0.0.2pre21 - 2004-02-18
18469 - There's a ChangeLog file that actually reflects the changelog.
18470 - There's a 'torify' wrapper script, with an accompanying
18471 tor-tsocks.conf, that simplifies the process of using tsocks for
18472 tor. It even has a man page.
18473 - The tor binary gets installed to sbin rather than bin now.
18474 - Retry streams where the connected cell hasn't arrived in 15 seconds
18475 - Clean up exit policy handling -- get the default out of the torrc,
18476 so we can update it without forcing each server operator to fix
18478 - Allow imaps and pop3s in default exit policy
18480 - Prevent picking middleman nodes as the last node in the circuit
18483 Changes in version 0.0.2pre20 - 2004-01-30
18485 - We now have a deb package, and it's in debian unstable. Go to
18486 it, apt-getters. :)
18487 - I've split the TotalBandwidth option into BandwidthRate (how many
18488 bytes per second you want to allow, long-term) and
18489 BandwidthBurst (how many bytes you will allow at once before the cap
18490 kicks in). This better token bucket approach lets you, say, set
18491 BandwidthRate to 10KB/s and BandwidthBurst to 10MB, allowing good
18492 performance while not exceeding your monthly bandwidth quota.
18493 - Push out a tls record's worth of data once you've got it, rather
18494 than waiting until you've read everything waiting to be read. This
18495 may improve performance by pipelining better. We'll see.
18496 - Add an AP_CONN_STATE_CONNECTING state, to allow streams to detach
18497 from failed circuits (if they haven't been connected yet) and attach
18499 - Expire old streams that haven't managed to connect. Some day we'll
18500 have them reattach to new circuits instead.
18503 - Fix several memory leaks that were causing servers to become bloated
18505 - Fix a few very rare assert triggers. A few more remain.
18506 - Setuid to User _before_ complaining about running as root.
18509 Changes in version 0.0.2pre19 - 2004-01-07
18511 - Fix deadlock condition in dns farm. We were telling a child to die by
18512 closing the parent's file descriptor to him. But newer children were
18513 inheriting the open file descriptor from the parent, and since they
18514 weren't closing it, the socket never closed, so the child never read
18515 eof, so he never knew to exit. Similarly, dns workers were holding
18516 open other sockets, leading to all sorts of chaos.
18517 - New cleaner daemon() code for forking and backgrounding.
18518 - If you log to a file, it now prints an entry at the top of the
18519 logfile so you know it's working.
18520 - The onionskin challenge length was 30 bytes longer than necessary.
18521 - Started to patch up the spec so it's not quite so out of date.
18524 Changes in version 0.0.2pre18 - 2004-01-02
18526 - Fix endian issues with the 'integrity' field in the relay header.
18527 - Fix a potential bug where connections in state
18528 AP_CONN_STATE_CIRCUIT_WAIT might unexpectedly ask to write.
18531 Changes in version 0.0.2pre17 - 2003-12-30
18533 - Made --debuglogfile (or any second log file, actually) work.
18534 - Resolved an edge case in get_unique_circ_id_by_conn where a smart
18535 adversary could force us into an infinite loop.
18538 - Each onionskin handshake now includes a hash of the computed key,
18539 to prove the server's identity and help perfect forward secrecy.
18540 - Changed cell size from 256 to 512 bytes (working toward compatibility
18542 - Changed cell length to 2 bytes, and moved it to the relay header.
18543 - Implemented end-to-end integrity checking for the payloads of
18545 - Separated streamid from 'recognized' (otherwise circuits will get
18546 messed up when we try to have streams exit from the middle). We
18547 use the integrity-checking to confirm that a cell is addressed to
18549 - Randomize the initial circid and streamid values, so an adversary who
18550 breaks into a node can't learn how many circuits or streams have
18554 Changes in version 0.0.2pre16 - 2003-12-14
18556 - Fixed a bug that made HUP trigger an assert
18557 - Fixed a bug where a circuit that immediately failed wasn't being
18558 counted as a failed circuit in counting retries.
18561 - Now we close the circuit when we get a truncated cell: otherwise we're
18562 open to an anonymity attack where a bad node in the path truncates
18563 the circuit and then we open streams at him.
18564 - Add port ranges to exit policies
18565 - Add a conservative default exit policy
18566 - Warn if you're running tor as root
18567 - on HUP, retry OR connections and close/rebind listeners
18568 - options.EntryNodes: try these nodes first when picking the first node
18569 - options.ExitNodes: if your best choices happen to include any of
18570 your preferred exit nodes, you choose among just those preferred
18572 - options.ExcludedNodes: nodes that are never picked in path building
18575 Changes in version 0.0.2pre15 - 2003-12-03
18576 o Robustness and bugfixes:
18577 - Sometimes clients would cache incorrect DNS resolves, which would
18578 really screw things up.
18579 - An OP that goes offline would slowly leak all its sockets and stop
18581 - A wide variety of bugfixes in exit node selection, exit policy
18582 handling, and processing pending streams when a new circuit is
18584 - Pick nodes for a path only from those the directory says are up
18585 - Choose randomly from all running dirservers, not always the first one
18586 - Increase allowed http header size for directory fetch.
18587 - Stop writing to stderr (if we're daemonized it will be closed).
18588 - Enable -g always, so cores will be more useful to me.
18589 - Switch "-lcrypto -lssl" to "-lssl -lcrypto" for broken distributions.
18592 - Wrote a man page. It lists commonly used options.
18595 - Change default loglevel to warn.
18596 - Make PidFile default to null rather than littering in your CWD.
18597 - OnionRouter config option is now obsolete. Instead it just checks
18599 - Moved to a single unified torrc file for both clients and servers.
18602 Changes in version 0.0.2pre14 - 2003-11-29
18603 o Robustness and bugfixes:
18604 - Force the admin to make the DataDirectory himself
18605 - to get ownership/permissions right
18606 - so clients no longer make a DataDirectory and then never use it
18607 - fix bug where a client who was offline for 45 minutes would never
18608 pull down a directory again
18609 - fix (or at least hide really well) the dns assert bug that was
18610 causing server crashes
18611 - warnings and improved robustness wrt clockskew for certs
18612 - use the native daemon(3) to daemonize, when available
18613 - exit if bind() fails
18614 - exit if neither socksport nor orport is defined
18615 - include our own tor_timegm (Win32 doesn't have its own)
18616 - bugfix for win32 with lots of connections
18617 - fix minor bias in PRNG
18618 - make dirserver more robust to corrupt cached directory
18621 - Wrote the design document (woo)
18623 o Circuit building and exit policies:
18624 - Circuits no longer try to use nodes that the directory has told them
18626 - Exit policies now support bitmasks (18.0.0.0/255.0.0.0) and
18627 bitcounts (18.0.0.0/8).
18628 - Make AP connections standby for a circuit if no suitable circuit
18629 exists, rather than failing
18630 - Circuits choose exit node based on addr/port, exit policies, and
18631 which AP connections are standing by
18632 - Bump min pathlen from 2 to 3
18633 - Relay end cells have a payload to describe why the stream ended.
18634 - If the stream failed because of exit policy, try again with a new
18636 - Clients have a dns cache to remember resolved addresses.
18637 - Notice more quickly when we have no working circuits
18640 - APPort is now called SocksPort
18641 - SocksBindAddress, ORBindAddress, DirBindAddress let you configure
18643 - RecommendedVersions is now a config variable rather than
18644 hardcoded (for dirservers)
18645 - Reloads config on HUP
18646 - Usage info on -h or --help
18647 - If you set User and Group config vars, it'll setu/gid to them.
18650 Changes in version 0.0.2pre13 - 2003-10-19
18651 o General stability:
18652 - SSL_write no longer fails when it returns WANTWRITE and the number
18653 of bytes in the buf has changed by the next SSL_write call.
18654 - Fix segfault fetching directory when network is down
18655 - Fix a variety of minor memory leaks
18656 - Dirservers reload the fingerprints file on HUP, so I don't have
18657 to take down the network when I approve a new router
18658 - Default server config file has explicit Address line to specify fqdn
18661 - Buffers grow and shrink as needed (Cut process size from 20M to 2M)
18662 - Make listener connections not ever alloc bufs
18664 o Autoconf improvements:
18665 - don't clobber an external CFLAGS in ./configure
18666 - Make install now works
18667 - create var/lib/tor on make install
18668 - autocreate a tor.sh initscript to help distribs
18669 - autocreate the torrc and sample-server-torrc with correct paths
18671 o Log files and Daemonizing now work:
18672 - If --DebugLogFile is specified, log to it at -l debug
18673 - If --LogFile is specified, use it instead of commandline
18674 - If --RunAsDaemon is set, tor forks and backgrounds on startup