1 Changes in version 0.2.7.1-alpha - 2015-0?-??
4 Changes in version 0.2.6.6 - 2015-03-24
5 Tor 0.2.6.6 is the first stable release in the 0.2.6 series.
7 It adds numerous safety, security, correctness, and performance
8 improvements. Client programs can be configured to use more kinds of
9 sockets, AutomapHosts works better, the multithreading backend is
10 improved, cell transmission is refactored, test coverage is much
11 higher, more denial-of-service attacks are handled, guard selection is
12 improved to handle long-term guards better, pluggable transports
13 should work a bit better, and some annoying hidden service performance
14 bugs should be addressed.
16 o Minor bugfixes (portability):
17 - Use the correct datatype in the SipHash-2-4 function to prevent
18 compilers from assuming any sort of alignment. Fixes bug 15436;
19 bugfix on 0.2.5.3-alpha.
21 Changes in version 0.2.6.5-rc - 2015-03-18
22 Tor 0.2.6.5-rc is the second and (hopefully) last release candidate in
23 the 0.2.6. It fixes a small number of bugs found in 0.2.6.4-rc.
25 o Major bugfixes (client):
26 - Avoid crashing when making certain configuration option changes on
27 clients. Fixes bug 15245; bugfix on 0.2.6.3-alpha. Reported
30 o Major bugfixes (pluggable transports):
31 - Initialize the extended OR Port authentication cookie before
32 launching pluggable transports. This prevents a race condition
33 that occured when server-side pluggable transports would cache the
34 authentication cookie before it has been (re)generated. Fixes bug
35 15240; bugfix on 0.2.5.1-alpha.
37 o Major bugfixes (portability):
38 - Do not crash on startup when running on Solaris. Fixes a bug
39 related to our fix for 9495; bugfix on 0.2.6.1-alpha. Reported
42 o Minor features (heartbeat):
43 - On relays, report how many connections we negotiated using each
44 version of the Tor link protocols. This information will let us
45 know if removing support for very old versions of the Tor
46 protocols is harming the network. Closes ticket 15212.
48 o Code simplification and refactoring:
49 - Refactor main loop to extract the 'loop' part. This makes it
50 easier to run Tor under Shadow. Closes ticket 15176.
53 Changes in version 0.2.5.11 - 2015-03-17
54 Tor 0.2.5.11 is the second stable release in the 0.2.5 series.
56 It backports several bugfixes from the 0.2.6 branch, including a
57 couple of medium-level security fixes for relays and exit nodes.
58 It also updates the list of directory authorities.
60 o Directory authority changes:
61 - Remove turtles as a directory authority.
62 - Add longclaw as a new (v3) directory authority. This implements
63 ticket 13296. This keeps the directory authority count at 9.
64 - The directory authority Faravahar has a new IP address. This
67 o Major bugfixes (crash, OSX, security):
68 - Fix a remote denial-of-service opportunity caused by a bug in
69 OSX's _strlcat_chk() function. Fixes bug 15205; bug first appeared
72 o Major bugfixes (relay, stability, possible security):
73 - Fix a bug that could lead to a relay crashing with an assertion
74 failure if a buffer of exactly the wrong layout was passed to
75 buf_pullup() at exactly the wrong time. Fixes bug 15083; bugfix on
76 0.2.0.10-alpha. Patch from 'cypherpunks'.
77 - Do not assert if the 'data' pointer on a buffer is advanced to the
78 very end of the buffer; log a BUG message instead. Only assert if
79 it is past that point. Fixes bug 15083; bugfix on 0.2.0.10-alpha.
81 o Major bugfixes (exit node stability):
82 - Fix an assertion failure that could occur under high DNS load.
83 Fixes bug 14129; bugfix on Tor 0.0.7rc1. Found by "jowr";
84 diagnosed and fixed by "cypherpunks".
86 o Major bugfixes (Linux seccomp2 sandbox):
87 - Upon receiving sighup with the seccomp2 sandbox enabled, do not
88 crash during attempts to call wait4. Fixes bug 15088; bugfix on
89 0.2.5.1-alpha. Patch from "sanic".
91 o Minor features (controller):
92 - New "GETINFO bw-event-cache" to get information about recent
93 bandwidth events. Closes ticket 14128. Useful for controllers to
94 get recent bandwidth history after the fix for ticket 13988.
96 o Minor features (geoip):
97 - Update geoip to the March 3 2015 Maxmind GeoLite2 Country database.
98 - Update geoip6 to the March 3 2015 Maxmind GeoLite2
101 o Minor bugfixes (client, automapping):
102 - Avoid crashing on torrc lines for VirtualAddrNetworkIPv[4|6] when
103 no value follows the option. Fixes bug 14142; bugfix on
104 0.2.4.7-alpha. Patch by "teor".
105 - Fix a memory leak when using AutomapHostsOnResolve. Fixes bug
106 14195; bugfix on 0.1.0.1-rc.
108 o Minor bugfixes (compilation):
109 - Build without warnings with the stock OpenSSL srtp.h header, which
110 has a duplicate declaration of SSL_get_selected_srtp_profile().
111 Fixes bug 14220; this is OpenSSL's bug, not ours.
113 o Minor bugfixes (directory authority):
114 - Allow directory authorities to fetch more data from one another if
115 they find themselves missing lots of votes. Previously, they had
116 been bumping against the 10 MB queued data limit. Fixes bug 14261;
117 bugfix on 0.1.2.5-alpha.
118 - Enlarge the buffer to read bwauth generated files to avoid an
119 issue when parsing the file in dirserv_read_measured_bandwidths().
120 Fixes bug 14125; bugfix on 0.2.2.1-alpha.
122 o Minor bugfixes (statistics):
123 - Increase period over which bandwidth observations are aggregated
124 from 15 minutes to 4 hours. Fixes bug 13988; bugfix on 0.0.8pre1.
126 o Minor bugfixes (preventative security, C safety):
127 - When reading a hexadecimal, base-32, or base-64 encoded value from
128 a string, always overwrite the whole output buffer. This prevents
129 some bugs where we would look at (but fortunately, not reveal)
130 uninitialized memory on the stack. Fixes bug 14013; bugfix on all
134 Changes in version 0.2.4.26 - 2015-03-17
135 Tor 0.2.4.26 includes an updated list of directory authorities. It
136 also backports a couple of stability and security bugfixes from 0.2.5
139 o Directory authority changes:
140 - Remove turtles as a directory authority.
141 - Add longclaw as a new (v3) directory authority. This implements
142 ticket 13296. This keeps the directory authority count at 9.
143 - The directory authority Faravahar has a new IP address. This
146 o Major bugfixes (exit node stability, also in 0.2.6.3-alpha):
147 - Fix an assertion failure that could occur under high DNS load.
148 Fixes bug 14129; bugfix on Tor 0.0.7rc1. Found by "jowr";
149 diagnosed and fixed by "cypherpunks".
151 o Major bugfixes (relay, stability, possible security, also in 0.2.6.4-rc):
152 - Fix a bug that could lead to a relay crashing with an assertion
153 failure if a buffer of exactly the wrong layout was passed to
154 buf_pullup() at exactly the wrong time. Fixes bug 15083; bugfix on
155 0.2.0.10-alpha. Patch from 'cypherpunks'.
156 - Do not assert if the 'data' pointer on a buffer is advanced to the
157 very end of the buffer; log a BUG message instead. Only assert if
158 it is past that point. Fixes bug 15083; bugfix on 0.2.0.10-alpha.
160 o Minor features (geoip):
161 - Update geoip to the March 3 2015 Maxmind GeoLite2 Country database.
162 - Update geoip6 to the March 3 2015 Maxmind GeoLite2
165 Changes in version 0.2.6.4-rc - 2015-03-09
166 Tor 0.2.6.4-alpha fixes an issue in the directory code that an
167 attacker might be able to use in order to crash certain Tor
168 directories. It also resolves some minor issues left over from, or
169 introduced in, Tor 0.2.6.3-alpha or earlier.
171 o Major bugfixes (crash, OSX, security):
172 - Fix a remote denial-of-service opportunity caused by a bug in
173 OSX's _strlcat_chk() function. Fixes bug 15205; bug first appeared
176 o Major bugfixes (relay, stability, possible security):
177 - Fix a bug that could lead to a relay crashing with an assertion
178 failure if a buffer of exactly the wrong layout is passed to
179 buf_pullup() at exactly the wrong time. Fixes bug 15083; bugfix on
180 0.2.0.10-alpha. Patch from "cypherpunks".
181 - Do not assert if the 'data' pointer on a buffer is advanced to the
182 very end of the buffer; log a BUG message instead. Only assert if
183 it is past that point. Fixes bug 15083; bugfix on 0.2.0.10-alpha.
185 o Major bugfixes (FreeBSD IPFW transparent proxy):
186 - Fix address detection with FreeBSD transparent proxies, when
187 "TransProxyType ipfw" is in use. Fixes bug 15064; bugfix
190 o Major bugfixes (Linux seccomp2 sandbox):
191 - Pass IPPROTO_TCP rather than 0 to socket(), so that the Linux
192 seccomp2 sandbox doesn't fail. Fixes bug 14989; bugfix
194 - Allow AF_UNIX hidden services to be used with the seccomp2
195 sandbox. Fixes bug 15003; bugfix on 0.2.6.3-alpha.
196 - Upon receiving sighup with the seccomp2 sandbox enabled, do not
197 crash during attempts to call wait4. Fixes bug 15088; bugfix on
198 0.2.5.1-alpha. Patch from "sanic".
200 o Minor features (controller):
201 - Messages about problems in the bootstrap process now include
202 information about the server we were trying to connect to when we
203 noticed the problem. Closes ticket 15006.
205 o Minor features (geoip):
206 - Update geoip to the March 3 2015 Maxmind GeoLite2 Country database.
207 - Update geoip6 to the March 3 2015 Maxmind GeoLite2
210 o Minor features (logs):
211 - Quiet some log messages in the heartbeat and at startup. Closes
214 o Minor bugfixes (certificate handling):
215 - If an authority operator accidentally makes a signing certificate
216 with a future publication time, do not discard its real signing
217 certificates. Fixes bug 11457; bugfix on 0.2.0.3-alpha.
218 - Remove any old authority certificates that have been superseded
219 for at least two days. Previously, we would keep superseded
220 certificates until they expired, if they were published close in
221 time to the certificate that superseded them. Fixes bug 11454;
222 bugfix on 0.2.1.8-alpha.
224 o Minor bugfixes (compilation):
225 - Fix a compilation warning on s390. Fixes bug 14988; bugfix
227 - Fix a compilation warning on FreeBSD. Fixes bug 15151; bugfix
230 o Minor bugfixes (testing):
231 - Fix endianness issues in unit test for resolve_my_address() to
232 have it pass on big endian systems. Fixes bug 14980; bugfix on
234 - Avoid a side-effect in a tor_assert() in the unit tests. Fixes bug
235 15188; bugfix on 0.1.2.3-alpha. Patch from Tom van der Woerdt.
236 - When running the new 'make test-stem' target, use the configured
237 python binary. Fixes bug 15037; bugfix on 0.2.6.3-alpha. Patch
239 - When running the zero-length-keys tests, do not use the default
240 torrc file. Fixes bug 15033; bugfix on 0.2.6.3-alpha. Reported
243 o Directory authority IP change:
244 - The directory authority Faravahar has a new IP address. This
248 - Remove some lingering dead code that once supported mempools.
249 Mempools were disabled by default in 0.2.5, and removed entirely
250 in 0.2.6.3-alpha. Closes more of ticket 14848; patch
254 Changes in version 0.2.6.3-alpha - 2015-02-19
255 Tor 0.2.6.3-alpha is the third (and hopefully final) alpha release in
256 the 0.2.6.x series. It introduces support for more kinds of sockets,
257 makes it harder to accidentally run an exit, improves our
258 multithreading backend, incorporates several fixes for the
259 AutomapHostsOnResolve option, and fixes numerous other bugs besides.
261 If no major regressions or security holes are found in this version,
262 the next version will be a release candidate.
264 o Deprecated versions:
265 - Tor relays older than 0.2.4.18-rc are no longer allowed to
266 advertise themselves on the network. Closes ticket 13555.
268 o Major features (security, unix domain sockets):
269 - Allow SocksPort to be an AF_UNIX Unix Domain Socket. Now high risk
270 applications can reach Tor without having to create AF_INET or
271 AF_INET6 sockets, meaning they can completely disable their
272 ability to make non-Tor network connections. To create a socket of
273 this type, use "SocksPort unix:/path/to/socket". Implements
275 - Support mapping hidden service virtual ports to AF_UNIX sockets.
276 The syntax is "HiddenServicePort 80 unix:/path/to/socket".
277 Implements ticket 11485.
279 o Major features (changed defaults):
280 - Prevent relay operators from unintentionally running exits: When a
281 relay is configured as an exit node, we now warn the user unless
282 the "ExitRelay" option is set to 1. We warn even more loudly if
283 the relay is configured with the default exit policy, since this
284 can indicate accidental misconfiguration. Setting "ExitRelay 0"
285 stops Tor from running as an exit relay. Closes ticket 10067.
287 o Major features (directory system):
288 - When downloading server- or microdescriptors from a directory
289 server, we no longer launch multiple simultaneous requests to the
290 same server. This reduces load on the directory servers,
291 especially when directory guards are in use. Closes ticket 9969.
292 - When downloading server- or microdescriptors over a tunneled
293 connection, do not limit the length of our requests to what the
294 Squid proxy is willing to handle. Part of ticket 9969.
295 - Authorities can now vote on the correct digests and latest
296 versions for different software packages. This allows packages
297 that include Tor to use the Tor authority system as a way to get
298 notified of updates and their correct digests. Implements proposal
299 227. Closes ticket 10395.
301 o Major features (guards):
302 - Introduce the Guardfraction feature to improves load balancing on
303 guard nodes. Specifically, it aims to reduce the traffic gap that
304 guard nodes experience when they first get the Guard flag. This is
305 a required step if we want to increase the guard lifetime to 9
306 months or greater. Closes ticket 9321.
308 o Major features (performance):
309 - Make the CPU worker implementation more efficient by avoiding the
310 kernel and lengthening pipelines. The original implementation used
311 sockets to transfer data from the main thread to the workers, and
312 didn't allow any thread to be assigned more than a single piece of
313 work at once. The new implementation avoids communications
314 overhead by making requests in shared memory, avoiding kernel IO
315 where possible, and keeping more requests in flight at once.
316 Implements ticket 9682.
318 o Major features (relay):
319 - Raise the minimum acceptable configured bandwidth rate for bridges
320 to 50 KiB/sec and for relays to 75 KiB/sec. (The old values were
321 20 KiB/sec.) Closes ticket 13822.
323 o Major bugfixes (exit node stability):
324 - Fix an assertion failure that could occur under high DNS load.
325 Fixes bug 14129; bugfix on Tor 0.0.7rc1. Found by "jowr";
326 diagnosed and fixed by "cypherpunks".
328 o Major bugfixes (mixed relay-client operation):
329 - When running as a relay and client at the same time (not
330 recommended), if we decide not to use a new guard because we want
331 to retry older guards, only close the locally-originating circuits
332 passing through that guard. Previously we would close all the
333 circuits through that guard. Fixes bug 9819; bugfix on
334 0.2.1.1-alpha. Reported by "skruffy".
336 o Minor features (build):
337 - New --disable-system-torrc compile-time option to prevent Tor from
338 looking for the system-wide torrc or torrc-defaults files.
339 Resolves ticket 13037.
341 o Minor features (controller):
342 - Include SOCKS_USERNAME and SOCKS_PASSWORD values in controller
343 events so controllers can observe circuit isolation inputs. Closes
345 - ControlPort now supports the unix:/path/to/socket syntax as an
346 alternative to the ControlSocket option, for consistency with
347 SocksPort and HiddenServicePort. Closes ticket 14451.
348 - New "GETINFO bw-event-cache" to get information about recent
349 bandwidth events. Closes ticket 14128. Useful for controllers to
350 get recent bandwidth history after the fix for ticket 13988.
352 o Minor features (Denial of service resistance):
353 - Count the total number of bytes used storing hidden service
354 descriptors against the value of MaxMemInQueues. If we're low on
355 memory, and more than 20% of our memory is used holding hidden
356 service descriptors, free them until no more than 10% of our
357 memory holds hidden service descriptors. Free the least recently
358 fetched descriptors first. Resolves ticket 13806.
359 - When we have recently been under memory pressure (over 3/4 of
360 MaxMemInQueues is allocated), then allocate smaller zlib objects
361 for small requests. Closes ticket 11791.
363 o Minor features (geoip):
364 - Update geoip and geoip6 files to the January 7 2015 Maxmind
365 GeoLite2 Country database.
367 o Minor features (guard nodes):
368 - Reduce the time delay before saving guard status to disk from 10
369 minutes to 30 seconds (or from one hour to 10 minutes if
370 AvoidDiskWrites is set). Closes ticket 12485.
372 o Minor features (hidden service):
373 - Make Sybil attacks against hidden services harder by changing the
374 minimum time required to get the HSDir flag from 25 hours up to 96
375 hours. Addresses ticket 14149.
376 - New option "HiddenServiceAllowUnknownPorts" to allow hidden
377 services to disable the anti-scanning feature introduced in
378 0.2.6.2-alpha. With this option not set, a connection to an
379 unlisted port closes the circuit. With this option set, only a
380 RELAY_DONE cell is sent. Closes ticket 14084.
382 o Minor features (interface):
383 - Implement "-f -" command-line option to read torrc configuration
384 from standard input, if you don't want to store the torrc file in
385 the file system. Implements feature 13865.
387 o Minor features (logging):
388 - Add a count of unique clients to the bridge heartbeat message.
389 Resolves ticket 6852.
390 - Suppress "router info incompatible with extra info" message when
391 reading extrainfo documents from cache. (This message got loud
392 around when we closed bug 9812 in 0.2.6.2-alpha.) Closes
394 - Elevate hidden service authorized-client message from DEBUG to
395 INFO. Closes ticket 14015.
397 o Minor features (stability):
398 - Add assertions in our hash-table iteration code to check for
399 corrupted values that could cause infinite loops. Closes
402 o Minor features (systemd):
403 - Various improvements and modernizations in systemd hardening
404 support. Closes ticket 13805. Patch from Craig Andrews.
406 o Minor features (testing networks):
407 - Drop the minimum RendPostPeriod on a testing network to 5 seconds,
408 and the default on a testing network to 2 minutes. Drop the
409 MIN_REND_INITIAL_POST_DELAY on a testing network to 5 seconds, but
410 keep the default on a testing network at 30 seconds. This reduces
411 HS bootstrap time to around 25 seconds. Also, change the default
412 time in test-network.sh to match. Closes ticket 13401. Patch
414 - Create TestingDirAuthVoteHSDir to correspond to
415 TestingDirAuthVoteExit/Guard. Ensures that authorities vote the
416 HSDir flag for the listed relays regardless of uptime or ORPort
417 connectivity. Respects the value of VoteOnHidServDirectoriesV2.
418 Partial implementation for ticket 14067. Patch by "teor".
420 o Minor features (tor2web mode):
421 - Introduce the config option Tor2webRendezvousPoints, which allows
422 clients in Tor2webMode to select a specific Rendezvous Point to be
423 used in HS circuits. This might allow better performance for
424 Tor2Web nodes. Implements ticket 12844.
426 o Minor bugfixes (client DNS):
427 - Report the correct cached DNS expiration times on SOCKS port or in
428 DNS replies. Previously, we would report everything as "never
429 expires." Fixes bug 14193; bugfix on 0.2.3.17-beta.
430 - Avoid a small memory leak when we find a cached answer for a
431 reverse DNS lookup in a client-side DNS cache. (Remember, client-
432 side DNS caching is off by default, and is not recommended.) Fixes
433 bug 14259; bugfix on 0.2.0.1-alpha.
435 o Minor bugfixes (client, automapping):
436 - Avoid crashing on torrc lines for VirtualAddrNetworkIPv[4|6] when
437 no value follows the option. Fixes bug 14142; bugfix on
438 0.2.4.7-alpha. Patch by "teor".
439 - Fix a memory leak when using AutomapHostsOnResolve. Fixes bug
440 14195; bugfix on 0.1.0.1-rc.
441 - Prevent changes to other options from removing the wildcard value
442 "." from "AutomapHostsSuffixes". Fixes bug 12509; bugfix
444 - Allow MapAddress and AutomapHostsOnResolve to work together when
445 an address is mapped into another address type (like .onion) that
446 must be automapped at resolve time. Fixes bug 7555; bugfix
449 o Minor bugfixes (client, bridges):
450 - When we are using bridges and we had a network connectivity
451 problem, only retry connecting to our currently configured
452 bridges, not all bridges we know about and remember using. Fixes
453 bug 14216; bugfix on 0.2.2.17-alpha.
455 o Minor bugfixes (client, IPv6):
456 - Reject socks requests to literal IPv6 addresses when IPv6Traffic
457 flag is not set; and not because the NoIPv4Traffic flag was set.
458 Previously we'd looked at the NoIPv4Traffic flag for both types of
459 literal addresses. Fixes bug 14280; bugfix on 0.2.4.7-alpha.
461 o Minor bugfixes (compilation):
462 - The address of an array in the middle of a structure will always
463 be non-NULL. clang recognises this and complains. Disable the
464 tautologous and redundant check to silence this warning. Fixes bug
465 14001; bugfix on 0.2.1.2-alpha.
466 - Avoid warnings when building with systemd 209 or later. Fixes bug
467 14072; bugfix on 0.2.6.2-alpha. Patch from "h.venev".
468 - Compile correctly with (unreleased) OpenSSL 1.1.0 headers.
469 Addresses ticket 14188.
470 - Build without warnings with the stock OpenSSL srtp.h header, which
471 has a duplicate declaration of SSL_get_selected_srtp_profile().
472 Fixes bug 14220; this is OpenSSL's bug, not ours.
473 - Do not compile any code related to Tor2Web mode when Tor2Web mode
474 is not enabled at compile time. Previously, this code was included
475 in a disabled state. See discussion on ticket 12844.
476 - Remove the --disable-threads configure option again. It was
477 accidentally partially reintroduced in 29ac883606d6d. Fixes bug
478 14819; bugfix on 0.2.6.2-alpha.
480 o Minor bugfixes (controller):
481 - Report "down" in response to the "GETINFO entry-guards" command
482 when relays are down with an unreachable_since value. Previously,
483 we would report "up". Fixes bug 14184; bugfix on 0.1.2.2-alpha.
484 - Avoid crashing on a malformed EXTENDCIRCUIT command. Fixes bug
485 14116; bugfix on 0.2.2.9-alpha.
486 - Add a code for the END_CIRC_REASON_IP_NOW_REDUNDANT circuit close
487 reason. Fixes bug 14207; bugfix on 0.2.6.2-alpha.
489 o Minor bugfixes (directory authority):
490 - Allow directory authorities to fetch more data from one another if
491 they find themselves missing lots of votes. Previously, they had
492 been bumping against the 10 MB queued data limit. Fixes bug 14261;
493 bugfix on 0.1.2.5-alpha.
494 - Do not attempt to download extrainfo documents which we will be
495 unable to validate with a matching server descriptor. Fixes bug
496 13762; bugfix on 0.2.0.1-alpha.
497 - Fix a bug that was truncating AUTHDIR_NEWDESC events sent to the
498 control port. Fixes bug 14953; bugfix on 0.2.0.1-alpha.
499 - Enlarge the buffer to read bwauth generated files to avoid an
500 issue when parsing the file in dirserv_read_measured_bandwidths().
501 Fixes bug 14125; bugfix on 0.2.2.1-alpha.
503 o Minor bugfixes (file handling):
504 - Stop failing when key files are zero-length. Instead, generate new
505 keys, and overwrite the empty key files. Fixes bug 13111; bugfix
506 on all versions of Tor. Patch by "teor".
507 - Stop generating a fresh .old RSA onion key file when the .old file
508 is missing. Fixes part of 13111; bugfix on 0.0.6rc1.
509 - Avoid overwriting .old key files with empty key files.
510 - Skip loading zero-length extrainfo store, router store, stats,
511 state, and key files.
512 - Avoid crashing when trying to reload a torrc specified as a
513 relative path with RunAsDaemon turned on. Fixes bug 13397; bugfix
516 o Minor bugfixes (hidden services):
517 - Close the introduction circuit when we have no more usable intro
518 points, instead of waiting for it to time out. This also ensures
519 that no follow-up HS descriptor fetch is triggered when the
520 circuit eventually times out. Fixes bug 14224; bugfix on 0.0.6.
521 - When fetching a hidden service descriptor for a down service that
522 was recently up, do not keep refetching until we try the same
523 replica twice in a row. Fixes bug 14219; bugfix on 0.2.0.10-alpha.
524 - Successfully launch Tor with a nonexistent hidden service
525 directory. Our fix for bug 13942 didn't catch this case. Fixes bug
526 14106; bugfix on 0.2.6.2-alpha.
528 o Minor bugfixes (logging):
529 - Avoid crashing when there are more log domains than entries in
530 domain_list. Bugfix on 0.2.3.1-alpha.
531 - Add a string representation for LD_SCHED. Fixes bug 14740; bugfix
533 - Don't log messages to stdout twice when starting up. Fixes bug
534 13993; bugfix on 0.2.6.1-alpha.
536 o Minor bugfixes (parsing):
537 - Stop accepting milliseconds (or other junk) at the end of
538 descriptor publication times. Fixes bug 9286; bugfix on 0.0.2pre25.
539 - Support two-number and three-number version numbers correctly, in
540 case we change the Tor versioning system in the future. Fixes bug
541 13661; bugfix on 0.0.8pre1.
543 o Minor bugfixes (path counting):
544 - When deciding whether the consensus lists any exit nodes, count
545 the number listed in the consensus, not the number we have
546 descriptors for. Fixes part of bug 14918; bugfix on 0.2.6.2-alpha.
547 - When deciding whether we have any exit nodes, only examine
548 ExitNodes when the ExitNodes option is actually set. Fixes part of
549 bug 14918; bugfix on 0.2.6.2-alpha.
550 - Get rid of redundant and possibly scary warnings that we are
551 missing directory information while we bootstrap. Fixes part of
552 bug 14918; bugfix on 0.2.6.2-alpha.
554 o Minor bugfixes (portability):
555 - Fix the ioctl()-based network interface lookup code so that it
556 will work on systems that have variable-length struct ifreq, for
558 - Fix scheduler compilation on targets where char is unsigned. Fixes
559 bug 14764; bugfix on 0.2.6.2-alpha. Reported by Christian Kujau.
561 o Minor bugfixes (sandbox):
562 - Allow glibc fatal errors to be sent to stderr before Tor exits.
563 Previously, glibc would try to write them to /dev/tty, and the
564 sandbox would trap the call and make Tor exit prematurely. Fixes
565 bug 14759; bugfix on 0.2.5.1-alpha.
567 o Minor bugfixes (shutdown):
568 - When shutting down, always call event_del() on lingering read or
569 write events before freeing them. Otherwise, we risk double-frees
570 or read-after-frees in event_base_free(). Fixes bug 12985; bugfix
573 o Minor bugfixes (small memory leaks):
574 - Avoid leaking memory when using IPv6 virtual address mappings.
575 Fixes bug 14123; bugfix on 0.2.4.7-alpha. Patch by Tom van
578 o Minor bugfixes (statistics):
579 - Increase period over which bandwidth observations are aggregated
580 from 15 minutes to 4 hours. Fixes bug 13988; bugfix on 0.0.8pre1.
582 o Minor bugfixes (systemd support):
583 - Fix detection and operation of systemd watchdog. Fixes part of bug
584 14141; bugfix on 0.2.6.2-alpha. Patch from Tomasz Torcz.
585 - Run correctly under systemd with the RunAsDaemon option set. Fixes
586 part of bug 14141; bugfix on 0.2.5.7-rc. Patch from Tomasz Torcz.
587 - Inform the systemd supervisor about more changes in the Tor
588 process status. Implements part of ticket 14141. Patch from
590 - Cause the "--disable-systemd" option to actually disable systemd
591 support. Fixes bug 14350; bugfix on 0.2.6.2-alpha. Patch
594 o Minor bugfixes (TLS):
595 - Check more thoroughly throughout the TLS code for possible
596 unlogged TLS errors. Possible diagnostic or fix for bug 13319.
598 o Minor bugfixes (transparent proxy):
599 - Use getsockname, not getsockopt, to retrieve the address for a
600 TPROXY-redirected connection. Fixes bug 13796; bugfix
603 o Code simplification and refactoring:
604 - Move fields related to isolating and configuring client ports into
605 a shared structure. Previously, they were duplicated across
606 port_cfg_t, listener_connection_t, and edge_connection_t. Failure
607 to copy them correctly had been the cause of at least one bug in
608 the past. Closes ticket 8546.
609 - Refactor the get_interface_addresses_raw() doom-function into
610 multiple smaller and simpler subfunctions. Cover the resulting
611 subfunctions with unit-tests. Fixes a significant portion of
613 - Remove workaround in dirserv_thinks_router_is_hs_dir() that was
614 only for version <= 0.2.2.24 which is now deprecated. Closes
616 - Remove a test for a long-defunct broken version-one
620 - Adding section on OpenBSD to our TUNING document. Thanks to mmcc
621 for writing the OpenBSD-specific tips. Resolves ticket 13702.
622 - Make the tor-resolve documentation match its help string and its
623 options. Resolves part of ticket 14325.
624 - Log a more useful error message from tor-resolve when failing to
625 look up a hidden service address. Resolves part of ticket 14325.
627 o Downgraded warnings:
628 - Don't warn when we've attempted to contact a relay using the wrong
629 ntor onion key. Closes ticket 9635.
632 - To avoid confusion with the "ExitRelay" option, "ExitNode" is no
633 longer silently accepted as an alias for "ExitNodes".
634 - The --enable-mempool and --enable-buf-freelists options, which
635 were originally created to work around bad malloc implementations,
636 no longer exist. They were off-by-default in 0.2.5. Closes
640 - Make the checkdir/perms test complete successfully even if the
641 global umask is not 022. Fixes bug 14215; bugfix on 0.2.6.2-alpha.
642 - Test that tor does not fail when key files are zero-length. Check
643 that tor generates new keys, and overwrites the empty key files.
644 - Test that tor generates new keys when keys are missing
646 - Test that tor does not overwrite key files that already contain
647 data (existing behavior). Tests bug 13111. Patch by "teor".
648 - New "make test-stem" target to run stem integration tests.
649 Requires that the "STEM_SOURCE_DIR" environment variable be set.
651 - Make the test_cmdline_args.py script work correctly on Windows.
652 Patch from Gisle Vanem.
653 - Move the slower unit tests into a new "./src/test/test-slow"
654 binary that can be run independently of the other tests. Closes
656 - Avoid undefined behavior when sampling huge values from the
657 Laplace distribution. This made unittests fail on Raspberry Pi.
658 Bug found by Device. Fixes bug 14090; bugfix on 0.2.6.2-alpha.
661 Changes in version 0.2.6.2-alpha - 2014-12-31
662 Tor 0.2.6.2-alpha is the second alpha release in the 0.2.6.x series.
663 It introduces a major new backend for deciding when to send cells on
664 channels, which should lead down the road to big performance
665 increases. It contains security and statistics features for better
666 work on hidden services, and numerous bugfixes.
668 This release contains many new unit tests, along with major
669 performance improvements for running testing networks using Chutney.
670 Thanks to a series of patches contributed by "teor", testing networks
671 should now bootstrap in seconds, rather than minutes.
673 o Major features (relay, infrastructure):
674 - Complete revision of the code that relays use to decide which cell
675 to send next. Formerly, we selected the best circuit to write on
676 each channel, but we didn't select among channels in any
677 sophisticated way. Now, we choose the best circuits globally from
678 among those whose channels are ready to deliver traffic.
680 This patch implements a new inter-cmux comparison API, a global
681 high/low watermark mechanism and a global scheduler loop for
682 transmission prioritization across all channels as well as among
683 circuits on one channel. This schedule is currently tuned to
684 (tolerantly) avoid making changes in network performance, but it
685 should form the basis for major circuit performance increases in
686 the future. Code by Andrea; tuning by Rob Jansen; implements
689 o Major features (hidden services):
690 - Make HS port scanning more difficult by immediately closing the
691 circuit when a user attempts to connect to a nonexistent port.
693 - Add a HiddenServiceStatistics option that allows Tor relays to
694 gather and publish statistics about the overall size and volume of
695 hidden service usage. Specifically, when this option is turned on,
696 an HSDir will publish an approximate number of hidden services
697 that have published descriptors to it the past 24 hours. Also, if
698 a relay has acted as a hidden service rendezvous point, it will
699 publish the approximate amount of rendezvous cells it has relayed
700 the past 24 hours. The statistics themselves are obfuscated so
701 that the exact values cannot be derived. For more details see
702 proposal 238, "Better hidden service stats from Tor relays". This
703 feature is currently disabled by default. Implements feature 13192.
705 o Major bugfixes (client, automap):
706 - Repair automapping with IPv6 addresses. This automapping should
707 have worked previously, but one piece of debugging code that we
708 inserted to detect a regression actually caused the regression to
709 manifest itself again. Fixes bug 13811 and bug 12831; bugfix on
710 0.2.4.7-alpha. Diagnosed and fixed by Francisco Blas
713 o Major bugfixes (hidden services):
714 - When closing an introduction circuit that was opened in parallel
715 with others, don't mark the introduction point as unreachable.
716 Previously, the first successful connection to an introduction
717 point would make the other introduction points get marked as
718 having timed out. Fixes bug 13698; bugfix on 0.0.6rc2.
720 o Directory authority changes:
721 - Remove turtles as a directory authority.
722 - Add longclaw as a new (v3) directory authority. This implements
723 ticket 13296. This keeps the directory authority count at 9.
725 o Major removed features:
726 - Tor clients no longer support connecting to hidden services
727 running on Tor 0.2.2.x and earlier; the Support022HiddenServices
728 option has been removed. (There shouldn't be any hidden services
729 running these versions on the network.) Closes ticket 7803.
731 o Minor features (client):
732 - Validate hostnames in SOCKS5 requests more strictly. If SafeSocks
733 is enabled, reject requests with IP addresses as hostnames.
734 Resolves ticket 13315.
736 o Minor features (controller):
737 - Add a "SIGNAL HEARTBEAT" controller command that tells Tor to
738 write an unscheduled heartbeat message to the log. Implements
741 o Minor features (geoip):
742 - Update geoip and geoip6 to the November 15 2014 Maxmind GeoLite2
745 o Minor features (hidden services):
746 - When re-enabling the network, don't try to build introduction
747 circuits until we have successfully built a circuit. This makes
748 hidden services come up faster when the network is re-enabled.
749 Patch from "akwizgran". Closes ticket 13447.
750 - When we fail to retrieve a hidden service descriptor, send the
751 controller an "HS_DESC FAILED" controller event. Implements
753 - New HiddenServiceDirGroupReadable option to cause hidden service
754 directories and hostname files to be created group-readable. Patch
755 from "anon", David Stainton, and "meejah". Closes ticket 11291.
757 o Minor features (systemd):
758 - Where supported, when running with systemd, report successful
759 startup to systemd. Part of ticket 11016. Patch by Michael Scherer.
760 - When running with systemd, support systemd watchdog messages. Part
761 of ticket 11016. Patch by Michael Scherer.
763 o Minor features (transparent proxy):
764 - Update the transparent proxy option checks to allow for both ipfw
765 and pf on OS X. Closes ticket 14002.
766 - Use the correct option when using IPv6 with transparent proxy
767 support on Linux. Resolves 13808. Patch by Francisco Blas
770 o Minor bugfixes (preventative security, C safety):
771 - When reading a hexadecimal, base-32, or base-64 encoded value from
772 a string, always overwrite the whole output buffer. This prevents
773 some bugs where we would look at (but fortunately, not reveal)
774 uninitialized memory on the stack. Fixes bug 14013; bugfix on all
776 - Clear all memory targetted by tor_addr_{to,from}_sockaddr(), not
777 just the part that's used. This makes it harder for data leak bugs
778 to occur in the event of other programming failures. Resolves
781 o Minor bugfixes (client, microdescriptors):
782 - Use a full 256 bits of the SHA256 digest of a microdescriptor when
783 computing which microdescriptors to download. This keeps us from
784 erroneous download behavior if two microdescriptor digests ever
785 have the same first 160 bits. Fixes part of bug 13399; bugfix
787 - Reset a router's status if its microdescriptor digest changes,
788 even if the first 160 bits remain the same. Fixes part of bug
789 13399; bugfix on 0.2.3.1-alpha.
791 o Minor bugfixes (compilation):
792 - Silence clang warnings under --enable-expensive-hardening,
793 including implicit truncation of 64 bit values to 32 bit, const
794 char assignment to self, tautological compare, and additional
795 parentheses around equality tests. Fixes bug 13577; bugfix
797 - Fix a clang warning about checking whether an address in the
798 middle of a structure is NULL. Fixes bug 14001; bugfix
801 o Minor bugfixes (hidden services):
802 - Correctly send a controller event when we find that a rendezvous
803 circuit has finished. Fixes bug 13936; bugfix on 0.1.1.5-alpha.
804 - Pre-check directory permissions for new hidden-services to avoid
805 at least one case of "Bug: Acting on config options left us in a
806 broken state. Dying." Fixes bug 13942; bugfix on 0.0.6pre1.
807 - When adding a new hidden service (for example, via SETCONF), Tor
808 no longer congratulates the user for running a relay. Fixes bug
809 13941; bugfix on 0.2.6.1-alpha.
810 - When fetching hidden service descriptors, we now check not only
811 for whether we got the hidden service we had in mind, but also
812 whether we got the particular descriptors we wanted. This prevents
813 a class of inefficient but annoying DoS attacks by hidden service
814 directories. Fixes bug 13214; bugfix on 0.2.1.6-alpha. Reported
817 o Minor bugfixes (Linux seccomp2 sandbox):
818 - Make transparent proxy support work along with the seccomp2
819 sandbox. Fixes part of bug 13808; bugfix on 0.2.5.1-alpha. Patch
820 by Francisco Blas Izquierdo Riera.
821 - Fix a memory leak in tor-resolve when running with the sandbox
822 enabled. Fixes bug 14050; bugfix on 0.2.5.9-rc.
824 o Minor bugfixes (logging):
825 - Downgrade warnings about RSA signature failures to info log level.
826 Emit a warning when an extra info document is found incompatible
827 with a corresponding router descriptor. Fixes bug 9812; bugfix
829 - Make connection_ap_handshake_attach_circuit() log the circuit ID
830 correctly. Fixes bug 13701; bugfix on 0.0.6.
832 o Minor bugfixes (misc):
833 - Stop allowing invalid address patterns like "*/24" that contain
834 both a wildcard address and a bit prefix length. This affects all
835 our address-range parsing code. Fixes bug 7484; bugfix
838 o Minor bugfixes (testing networks, fast startup):
839 - Allow Tor to build circuits using a consensus with no exits. If
840 the consensus has no exits (typical of a bootstrapping test
841 network), allow Tor to build circuits once enough descriptors have
842 been downloaded. This assists in bootstrapping a testing Tor
843 network. Fixes bug 13718; bugfix on 0.2.4.10-alpha. Patch
845 - When V3AuthVotingInterval is low, give a lower If-Modified-Since
846 header to directory servers. This allows us to obtain consensuses
847 promptly when the consensus interval is very short. This assists
848 in bootstrapping a testing Tor network. Fixes parts of bugs 13718
849 and 13963; bugfix on 0.2.0.3-alpha. Patch by "teor".
850 - Stop assuming that private addresses are local when checking
851 reachability in a TestingTorNetwork. Instead, when testing, assume
852 all OR connections are remote. (This is necessary due to many test
853 scenarios running all relays on localhost.) This assists in
854 bootstrapping a testing Tor network. Fixes bug 13924; bugfix on
855 0.1.0.1-rc. Patch by "teor".
856 - Avoid building exit circuits from a consensus with no exits. Now
857 thanks to our fix for 13718, we accept a no-exit network as not
858 wholly lost, but we need to remember not to try to build exit
859 circuits on it. Closes ticket 13814; patch by "teor".
860 - Stop requiring exits to have non-zero bandwithcapacity in a
861 TestingTorNetwork. Instead, when TestingMinExitFlagThreshold is 0,
862 ignore exit bandwidthcapacity. This assists in bootstrapping a
863 testing Tor network. Fixes parts of bugs 13718 and 13839; bugfix
864 on 0.2.0.3-alpha. Patch by "teor".
865 - Add "internal" to some bootstrap statuses when no exits are
866 available. If the consensus does not contain Exits, Tor will only
867 build internal circuits. In this case, relevant statuses will
868 contain the word "internal" as indicated in the Tor control-
869 spec.txt. When bootstrap completes, Tor will be ready to build
870 internal circuits. If a future consensus contains Exits, exit
871 circuits may become available. Fixes part of bug 13718; bugfix on
872 0.2.4.10-alpha. Patch by "teor".
873 - Decrease minimum consensus interval to 10 seconds when
874 TestingTorNetwork is set, or 5 seconds for the first consensus.
875 Fix assumptions throughout the code that assume larger intervals.
876 Fixes bugs 13718 and 13823; bugfix on 0.2.0.3-alpha. Patch
878 - Avoid excluding guards from path building in minimal test
879 networks, when we're in a test network and excluding guards would
880 exclude all relays. This typically occurs in incredibly small tor
881 networks, and those using "TestingAuthVoteGuard *". Fixes part of
882 bug 13718; bugfix on 0.1.1.11-alpha. Patch by "teor".
884 o Code simplification and refactoring:
885 - Stop using can_complete_circuits as a global variable; access it
886 with a function instead.
887 - Avoid using operators directly as macro arguments: this lets us
888 apply coccinelle transformations to our codebase more directly.
890 - Combine the functions used to parse ClientTransportPlugin and
891 ServerTransportPlugin into a single function. Closes ticket 6456.
892 - Add inline functions and convenience macros for inspecting channel
893 state. Refactor the code to use convenience macros instead of
894 checking channel state directly. Fixes issue 7356.
895 - Document all members of was_router_added_t and rename
896 ROUTER_WAS_NOT_NEW to ROUTER_IS_ALREADY_KNOWN to make it less
897 confusable with ROUTER_WAS_TOO_OLD. Fixes issue 13644.
898 - In connection_exit_begin_conn(), use END_CIRC_REASON_TORPROTOCOL
899 constant instead of hardcoded value. Fixes issue 13840.
900 - Refactor our generic strmap and digestmap types into a single
901 implementation, so that we can add a new digest256map
905 - Document the bridge-authority-only 'networkstatus-bridges' file.
906 Closes ticket 13713; patch from "tom".
907 - Fix typo in PredictedPortsRelevanceTime option description in
908 manpage. Resolves issue 13707.
909 - Stop suggesting that users specify relays by nickname: it isn't a
910 good idea. Also, properly cross-reference how to specify relays in
911 all parts of manual documenting options that take a list of
912 relays. Closes ticket 13381.
913 - Clarify the HiddenServiceDir option description in manpage to make
914 it clear that relative paths are taken with respect to the current
915 working directory. Also clarify that this behavior is not
916 guaranteed to remain indefinitely. Fixes issue 13913.
919 - New tests for many parts of channel, relay, and circuitmux
920 functionality. Code by Andrea; part of 9262.
921 - New tests for parse_transport_line(). Part of ticket 6456.
922 - In the unit tests, use chgrp() to change the group of the unit
923 test temporary directory to the current user, so that the sticky
924 bit doesn't interfere with tests that check directory groups.
926 - Add unit tests for resolve_my_addr(). Part of ticket 12376; patch
930 Changes in version 0.2.6.1-alpha - 2014-10-30
931 Tor 0.2.6.1-alpha is the first release in the Tor 0.2.6.x series. It
932 includes numerous code cleanups and new tests, and fixes a large
933 number of annoying bugs. Out-of-memory conditions are handled better
934 than in 0.2.5, pluggable transports have improved proxy support, and
935 clients now use optimistic data for contacting hidden services. Also,
936 we are now more robust to changes in what we consider a parseable
937 directory object, so that tightening restrictions does not have a risk
938 of introducing infinite download loops.
940 This is the first alpha release in a new series, so expect there to be
941 bugs. Users who would rather test out a more stable branch should stay
942 with 0.2.5.x for now.
944 o New compiler and system requirements:
945 - Tor 0.2.6.x requires that your compiler support more of the C99
946 language standard than before. The 'configure' script now detects
947 whether your compiler supports C99 mid-block declarations and
948 designated initializers. If it does not, Tor will not compile.
950 We may revisit this requirement if it turns out that a significant
951 number of people need to build Tor with compilers that don't
952 bother implementing a 15-year-old standard. Closes ticket 13233.
953 - Tor no longer supports systems without threading support. When we
954 began working on Tor, there were several systems that didn't have
955 threads, or where the thread support wasn't able to run the
956 threads of a single process on multiple CPUs. That no longer
957 holds: every system where Tor needs to run well now has threading
958 support. Resolves ticket 12439.
960 o Removed platform support:
961 - We no longer include special code to build on Windows CE; as far
962 as we know, nobody has used Tor on Windows CE in a very long time.
965 o Major features (bridges):
966 - Expose the outgoing upstream HTTP/SOCKS proxy to pluggable
967 transports if they are configured via the "TOR_PT_PROXY"
968 environment variable. Implements proposal 232. Resolves
971 o Major features (client performance, hidden services):
972 - Allow clients to use optimistic data when connecting to a hidden
973 service, which should remove a round-trip from hidden service
974 initialization. See proposal 181 for details. Implements
977 o Major features (directory system):
978 - Upon receiving an unparseable directory object, if its digest
979 matches what we expected, then don't try to download it again.
980 Previously, when we got a descriptor we didn't like, we would keep
981 trying to download it over and over. Closes ticket 11243.
983 o Major features (sample torrc):
984 - Add a new, infrequently-changed "torrc.minimal". This file is
985 similar to torrc.sample, but it will change as infrequently as
986 possible, for the benefit of users whose systems prompt them for
987 intervention whenever a default configuration file is changed.
988 Making this change allows us to update torrc.sample to be a more
989 generally useful "sample torrc".
991 o Major bugfixes (directory authorities):
992 - Do not assign the HSDir flag to relays if they are not Valid, or
993 currently hibernating. Fixes 12573; bugfix on 0.2.0.10-alpha.
995 o Major bugfixes (directory bandwidth performance):
996 - Don't flush the zlib buffer aggressively when compressing
997 directory information for clients. This should save about 7% of
998 the bandwidth currently used for compressed descriptors and
999 microdescriptors. Fixes bug 11787; bugfix on 0.1.1.23.
1001 o Minor features (security, memory wiping):
1002 - Ensure we securely wipe keys from memory after
1003 crypto_digest_get_digest and init_curve25519_keypair_from_file
1004 have finished using them. Resolves ticket 13477.
1006 o Minor features (security, out-of-memory handling):
1007 - When handling an out-of-memory condition, allocate less memory for
1008 temporary data structures. Fixes issue 10115.
1009 - When handling an out-of-memory condition, consider more types of
1010 buffers, including those on directory connections, and zlib
1011 buffers. Resolves ticket 11792.
1014 - When identity keypair is generated for first time, log a
1015 congratulatory message that links to the new relay lifecycle
1016 document. Implements feature 10427.
1018 o Minor features (client):
1019 - Clients are now willing to send optimistic data (before they
1020 receive a 'connected' cell) to relays of any version. (Relays
1021 without support for optimistic data are no longer supported on the
1022 Tor network.) Resolves ticket 13153.
1024 o Minor features (directory authorities):
1025 - Don't list relays with a bandwidth estimate of 0 in the consensus.
1026 Implements a feature proposed during discussion of bug 13000.
1027 - In tor-gencert, report an error if the user provides the same
1028 argument more than once.
1029 - If a directory authority can't find a best consensus method in the
1030 votes that it holds, it now falls back to its favorite consensus
1031 method. Previously, it fell back to method 1. Neither of these is
1032 likely to get enough signatures, but "fall back to favorite"
1033 doesn't require us to maintain support an obsolete consensus
1034 method. Implements part of proposal 215.
1036 o Minor features (logging):
1037 - On Unix-like systems, you can now use named pipes as the target of
1038 the Log option, and other options that try to append to files.
1039 Closes ticket 12061. Patch from "carlo von lynX".
1040 - When opening a log file at startup, send it every log message that
1041 we generated between startup and opening it. Previously, log
1042 messages that were generated before opening the log file were only
1043 logged to stdout. Closes ticket 6938.
1044 - Add a TruncateLogFile option to overwrite logs instead of
1045 appending to them. Closes ticket 5583.
1047 o Minor features (portability, Solaris):
1048 - Threads are no longer disabled by default on Solaris; we believe
1049 that the versions of Solaris with broken threading support are all
1050 obsolete by now. Resolves ticket 9495.
1052 o Minor features (relay):
1053 - Re-check our address after we detect a changed IP address from
1054 getsockname(). This ensures that the controller command "GETINFO
1055 address" will report the correct value. Resolves ticket 11582.
1057 - A new AccountingRule option lets Relays set whether they'd like
1058 AccountingMax to be applied separately to inbound and outbound
1059 traffic, or applied to the sum of inbound and outbound traffic.
1060 Resolves ticket 961. Patch by "chobe".
1062 o Minor features (testing networks):
1063 - Add the TestingDirAuthVoteExit option, which lists nodes to assign
1064 the "Exit" flag regardless of their uptime, bandwidth, or exit
1065 policy. TestingTorNetwork must be set for this option to have any
1066 effect. Previously, authorities would take up to 35 minutes to
1067 give nodes the Exit flag in a test network. Partially implements
1070 o Minor features (validation):
1071 - Check all date/time values passed to tor_timegm and
1072 parse_rfc1123_time for validity, taking leap years into account.
1073 Improves HTTP header validation. Implemented with bug 13476.
1074 - In correct_tm(), limit the range of values returned by system
1075 localtime(_r) and gmtime(_r) to be between the years 1 and 8099.
1076 This means we don't have to deal with negative or too large dates,
1077 even if a clock is wrong. Otherwise we might fail to read a file
1078 written by us which includes such a date. Fixes bug 13476.
1080 o Minor bugfixes (bridge clients):
1081 - When configured to use a bridge without an identity digest (not
1082 recommended), avoid launching an extra channel to it when
1083 bootstrapping. Fixes bug 7733; bugfix on 0.2.4.4-alpha.
1085 o Minor bugfixes (bridges):
1086 - When DisableNetwork is set, do not launch pluggable transport
1087 plugins, and if any are running, terminate them. Fixes bug 13213;
1088 bugfix on 0.2.3.6-alpha.
1090 o Minor bugfixes (C correctness):
1091 - Fix several instances of possible integer overflow/underflow/NaN.
1092 Fixes bug 13104; bugfix on 0.2.3.1-alpha and later. Patches
1094 - In circuit_build_times_calculate_timeout() in circuitstats.c,
1095 avoid dividing by zero in the pareto calculations. This traps
1096 under clang's "undefined-trap" sanitizer. Fixes bug 13290; bugfix
1098 - Fix an integer overflow in format_time_interval(). Fixes bug
1099 13393; bugfix on 0.2.0.10-alpha.
1100 - Set the correct day of year value when the system's localtime(_r)
1101 or gmtime(_r) functions fail to set struct tm. Not externally
1102 visible. Fixes bug 13476; bugfix on 0.0.2pre14.
1103 - Avoid unlikely signed integer overflow in tor_timegm on systems
1104 with 32-bit time_t. Fixes bug 13476; bugfix on 0.0.2pre14.
1106 o Minor bugfixes (client):
1107 - Fix smartlist_choose_node_by_bandwidth() so that relays with the
1108 BadExit flag are not considered worthy candidates. Fixes bug
1109 13066; bugfix on 0.1.2.3-alpha.
1110 - Use the consensus schedule for downloading consensuses, and not
1111 the generic schedule. Fixes bug 11679; bugfix on 0.2.2.6-alpha.
1112 - Handle unsupported or malformed SOCKS5 requests properly by
1113 responding with the appropriate error message before closing the
1114 connection. Fixes bugs 12971 and 13314; bugfix on 0.0.2pre13.
1116 o Minor bugfixes (client, torrc):
1117 - Stop modifying the value of our DirReqStatistics torrc option just
1118 because we're not a bridge or relay. This bug was causing Tor
1119 Browser users to write "DirReqStatistics 0" in their torrc files
1120 as if they had chosen to change the config. Fixes bug 4244; bugfix
1122 - When GeoIPExcludeUnknown is enabled, do not incorrectly decide
1123 that our options have changed every time we SIGHUP. Fixes bug
1124 9801; bugfix on 0.2.4.10-alpha. Patch from "qwerty1".
1126 o Minor bugfixes (controller):
1127 - Return an error when the second or later arguments of the
1128 "setevents" controller command are invalid events. Previously we
1129 would return success while silently skipping invalid events. Fixes
1130 bug 13205; bugfix on 0.2.3.2-alpha. Reported by "fpxnns".
1132 o Minor bugfixes (directory system):
1133 - Always believe that v3 directory authorities serve extra-info
1134 documents, whether they advertise "caches-extra-info" or not.
1135 Fixes part of bug 11683; bugfix on 0.2.0.1-alpha.
1136 - When running as a v3 directory authority, advertise that you serve
1137 extra-info documents so that clients who want them can find them
1138 from you too. Fixes part of bug 11683; bugfix on 0.2.0.1-alpha.
1139 - Check the BRIDGE_DIRINFO flag bitwise rather than using equality.
1140 Previously, directories offering BRIDGE_DIRINFO and some other
1141 flag (i.e. microdescriptors or extrainfo) would be ignored when
1142 looking for bridges. Partially fixes bug 13163; bugfix
1145 o Minor bugfixes (networking):
1146 - Check for orconns and use connection_or_close_for_error() rather
1147 than connection_mark_for_close() directly in the getsockopt()
1148 failure case of connection_handle_write_impl(). Fixes bug 11302;
1149 bugfix on 0.2.4.4-alpha.
1151 o Minor bugfixes (relay):
1152 - When generating our family list, remove spaces from around the
1153 entries. Fixes bug 12728; bugfix on 0.2.1.7-alpha.
1154 - If our previous bandwidth estimate was 0 bytes, allow publishing a
1155 new relay descriptor immediately. Fixes bug 13000; bugfix
1158 o Minor bugfixes (testing networks):
1159 - Fix TestingDirAuthVoteGuard to properly give out Guard flags in a
1160 testing network. Fixes bug 13064; bugfix on 0.2.5.2-alpha.
1161 - Stop using the default authorities in networks which provide both
1162 AlternateDirAuthority and AlternateBridgeAuthority. Partially
1163 fixes bug 13163; bugfix on 0.2.0.13-alpha.
1165 o Minor bugfixes (testing):
1166 - Stop spawn test failures due to a race condition between the
1167 SIGCHLD handler updating the process status, and the test reading
1168 it. Fixes bug 13291; bugfix on 0.2.3.3-alpha.
1170 o Minor bugfixes (testing, Windows):
1171 - Avoid passing an extra backslash when creating a temporary
1172 directory for running the unit tests on Windows. Fixes bug 12392;
1173 bugfix on 0.2.2.25-alpha. Patch from Gisle Vanem.
1175 o Minor bugfixes (windows):
1176 - Remove code to special-case handling of NTE_BAD_KEYSET when
1177 acquiring windows CryptoAPI context. This error can't actually
1178 occur for the parameters we're providing. Fixes bug 10816; bugfix
1181 o Minor bugfixes (zlib):
1182 - Avoid truncating a zlib stream when trying to finalize it with an
1183 empty output buffer. Fixes bug 11824; bugfix on 0.1.1.23.
1186 - Allow our configure script to build correctly with autoconf 2.62
1187 again. Fixes bug 12693; bugfix on 0.2.5.2-alpha.
1188 - Improve the error message from ./configure to make it clear that
1189 when asciidoc has not been found, the user will have to either add
1190 --disable-asciidoc argument or install asciidoc. Resolves
1193 o Code simplification and refactoring:
1194 - Change the entry_is_live() function to take named bitfield
1195 elements instead of an unnamed list of booleans. Closes
1197 - Refactor and unit-test entry_is_time_to_retry() in entrynodes.c.
1198 Resolves ticket 12205.
1199 - Use calloc and reallocarray functions instead of multiply-
1200 then-malloc. This makes it less likely for us to fall victim to an
1201 integer overflow attack when allocating. Resolves ticket 12855.
1202 - Use the standard macro name SIZE_MAX, instead of our
1204 - Document usage of the NO_DIRINFO and ALL_DIRINFO flags clearly in
1205 functions which take them as arguments. Replace 0 with NO_DIRINFO
1206 in a function call for clarity. Seeks to prevent future issues
1208 - Avoid 4 null pointer errors under clang static analysis by using
1209 tor_assert() to prove that the pointers aren't null. Fixes
1211 - Rework the API of policies_parse_exit_policy() to use a bitmask to
1212 represent parsing options, instead of a confusing mess of
1213 booleans. Resolves ticket 8197.
1214 - Introduce a helper function to parse ExitPolicy in
1215 or_options_t structure.
1218 - Add a doc/TUNING document with tips for handling large numbers of
1219 TCP connections when running busy Tor relay. Update the warning
1220 message to point to this file when running out of sockets
1221 operating system is allowing to use simultaneously. Resolves
1225 - We no longer remind the user about configuration options that have
1226 been obsolete since 0.2.3.x or earlier. Patch by Adrien Bak.
1227 - Remove our old, non-weighted bandwidth-based node selection code.
1228 Previously, we used it as a fallback when we couldn't perform
1229 weighted bandwidth-based node selection. But that would only
1230 happen in the cases where we had no consensus, or when we had a
1231 consensus generated by buggy or ancient directory authorities. In
1232 either case, it's better to use the more modern, better maintained
1233 algorithm, with reasonable defaults for the weights. Closes
1235 - Remove the --disable-curve25519 configure option. Relays and
1236 clients now are required to support curve25519 and the
1238 - The old "StrictEntryNodes" and "StrictExitNodes" options, which
1239 used to be deprecated synonyms for "StrictNodes", are now marked
1240 obsolete. Resolves ticket 12226.
1241 - Clients don't understand the BadDirectory flag in the consensus
1242 anymore, and ignore it.
1245 - Refactor the function that chooses guard nodes so that it can more
1246 easily be tested; write some tests for it.
1247 - Fix and re-enable the fgets_eagain unit test. Fixes bug 12503;
1248 bugfix on 0.2.3.1-alpha. Patch from "cypherpunks."
1249 - Create unit tests for format_time_interval(). With bug 13393.
1250 - Add unit tests for tor_timegm signed overflow, tor_timegm and
1251 parse_rfc1123_time validity checks, correct_tm year clamping. Unit
1252 tests (visible) fixes in bug 13476.
1253 - Add a "coverage-html" make target to generate HTML-visualized
1254 coverage results when building with --enable-coverage. (Requires
1255 lcov.) Patch from Kevin Murray.
1256 - Enable the backtrace handler (where supported) when running the
1258 - Revise all unit tests that used the legacy test_* macros to
1259 instead use the recommended tt_* macros. This patch was generated
1260 with coccinelle, to avoid manual errors. Closes ticket 13119.
1262 o Distribution (systemd):
1263 - systemd unit file: only allow tor to write to /var/lib/tor and
1264 /var/log/tor. The rest of the filesystem is accessible for reading
1265 only. Patch by intrigeri; resolves ticket 12751.
1266 - systemd unit file: ensure that the process and all its children
1267 can never gain new privileges. Patch by intrigeri; resolves
1269 - systemd unit file: set up /var/run/tor as writable for the Tor
1270 service. Patch by intrigeri; resolves ticket 13196.
1272 o Removed features (directory authorities):
1273 - Remove code that prevented authorities from listing Tor relays
1274 affected by CVE-2011-2769 as guards. These relays are already
1275 rejected altogether due to the minimum version requirement of
1276 0.2.3.16-alpha. Closes ticket 13152.
1277 - The "AuthDirRejectUnlisted" option no longer has any effect, as
1278 the fingerprints file (approved-routers) has been deprecated.
1279 - Directory authorities do not support being Naming dirauths anymore.
1280 The "NamingAuthoritativeDir" config option is now obsolete.
1281 - Directory authorities do not support giving out the BadDirectory
1283 - Directory authorities no longer advertise or support consensus
1284 methods 1 through 12 inclusive. These consensus methods were
1285 obsolete and/or insecure: maintaining the ability to support them
1286 served no good purpose. Implements part of proposal 215; closes
1289 o Testing (test-network.sh):
1290 - Stop using "echo -n", as some shells' built-in echo doesn't
1291 support "-n". Instead, use "/bin/echo -n". Partially fixes
1293 - Stop an apparent test-network hang when used with make -j2. Fixes
1295 - Add a --delay option to test-network.sh, which configures the
1296 delay before the chutney network tests for data transmission.
1297 Partially implements ticket 13161.
1300 Changes in version 0.2.5.10 - 2014-10-24
1301 Tor 0.2.5.10 is the first stable release in the 0.2.5 series.
1303 It adds several new security features, including improved
1304 denial-of-service resistance for relays, new compiler hardening
1305 options, and a system-call sandbox for hardened installations on Linux
1306 (requires seccomp2). The controller protocol has several new features,
1307 resolving IPv6 addresses should work better than before, and relays
1308 should be a little more CPU-efficient. We've added support for more
1309 OpenBSD and FreeBSD transparent proxy types. We've improved the build
1310 system and testing infrastructure to allow unit testing of more parts
1311 of the Tor codebase. Finally, we've addressed several nagging pluggable
1312 transport usability issues, and included numerous other small bugfixes
1313 and features mentioned below.
1315 This release marks end-of-life for Tor 0.2.3.x; those Tor versions
1316 have accumulated many known flaws; everyone should upgrade.
1318 o Deprecated versions:
1319 - Tor 0.2.3.x has reached end-of-life; it has received no patches or
1320 attention for some while.
1323 Changes in version 0.2.5.9-rc - 2014-10-20
1324 Tor 0.2.5.9-rc is the third release candidate for the Tor 0.2.5.x
1325 series. It disables SSL3 in response to the recent "POODLE" attack
1326 (even though POODLE does not affect Tor). It also works around a crash
1327 bug caused by some operating systems' response to the "POODLE" attack
1328 (which does affect Tor). It also contains a few miscellaneous fixes.
1330 o Major security fixes:
1331 - Disable support for SSLv3. All versions of OpenSSL in use with Tor
1332 today support TLS 1.0 or later, so we can safely turn off support
1333 for this old (and insecure) protocol. Fixes bug 13426.
1335 o Major bugfixes (openssl bug workaround):
1336 - Avoid crashing when using OpenSSL version 0.9.8zc, 1.0.0o, or
1337 1.0.1j, built with the 'no-ssl3' configuration option. Fixes bug
1338 13471. This is a workaround for an OpenSSL bug.
1341 - Disable the sandbox name resolver cache when running tor-resolve:
1342 tor-resolve doesn't use the sandbox code, and turning it on was
1343 breaking attempts to do tor-resolve on a non-default server on
1344 Linux. Fixes bug 13295; bugfix on 0.2.5.3-alpha.
1346 o Compilation fixes:
1347 - Build and run correctly on systems like OpenBSD-current that have
1348 patched OpenSSL to remove get_cipher_by_char and/or its
1349 implementations. Fixes issue 13325.
1351 o Downgraded warnings:
1352 - Downgrade the severity of the 'unexpected sendme cell from client'
1353 from 'warn' to 'protocol warning'. Closes ticket 8093.
1356 Changes in version 0.2.4.25 - 2014-10-20
1357 Tor 0.2.4.25 disables SSL3 in response to the recent "POODLE" attack
1358 (even though POODLE does not affect Tor). It also works around a crash
1359 bug caused by some operating systems' response to the "POODLE" attack
1360 (which does affect Tor).
1362 o Major security fixes (also in 0.2.5.9-rc):
1363 - Disable support for SSLv3. All versions of OpenSSL in use with Tor
1364 today support TLS 1.0 or later, so we can safely turn off support
1365 for this old (and insecure) protocol. Fixes bug 13426.
1367 o Major bugfixes (openssl bug workaround, also in 0.2.5.9-rc):
1368 - Avoid crashing when using OpenSSL version 0.9.8zc, 1.0.0o, or
1369 1.0.1j, built with the 'no-ssl3' configuration option. Fixes bug
1370 13471. This is a workaround for an OpenSSL bug.
1373 Changes in version 0.2.5.8-rc - 2014-09-22
1374 Tor 0.2.5.8-rc is the second release candidate for the Tor 0.2.5.x
1375 series. It fixes a bug that affects consistency and speed when
1376 connecting to hidden services, and it updates the location of one of
1377 the directory authorities.
1380 - Clients now send the correct address for their chosen rendezvous
1381 point when trying to access a hidden service. They used to send
1382 the wrong address, which would still work some of the time because
1383 they also sent the identity digest of the rendezvous point, and if
1384 the hidden service happened to try connecting to the rendezvous
1385 point from a relay that already had a connection open to it,
1386 the relay would reuse that connection. Now connections to hidden
1387 services should be more robust and faster. Also, this bug meant
1388 that clients were leaking to the hidden service whether they were
1389 on a little-endian (common) or big-endian (rare) system, which for
1390 some users might have reduced their anonymity. Fixes bug 13151;
1391 bugfix on 0.2.1.5-alpha.
1393 o Directory authority changes:
1394 - Change IP address for gabelmoo (v3 directory authority).
1397 Changes in version 0.2.4.24 - 2014-09-22
1398 Tor 0.2.4.24 fixes a bug that affects consistency and speed when
1399 connecting to hidden services, and it updates the location of one of
1400 the directory authorities.
1403 - Clients now send the correct address for their chosen rendezvous
1404 point when trying to access a hidden service. They used to send
1405 the wrong address, which would still work some of the time because
1406 they also sent the identity digest of the rendezvous point, and if
1407 the hidden service happened to try connecting to the rendezvous
1408 point from a relay that already had a connection open to it,
1409 the relay would reuse that connection. Now connections to hidden
1410 services should be more robust and faster. Also, this bug meant
1411 that clients were leaking to the hidden service whether they were
1412 on a little-endian (common) or big-endian (rare) system, which for
1413 some users might have reduced their anonymity. Fixes bug 13151;
1414 bugfix on 0.2.1.5-alpha.
1416 o Directory authority changes:
1417 - Change IP address for gabelmoo (v3 directory authority).
1419 o Minor features (geoip):
1420 - Update geoip and geoip6 to the August 7 2014 Maxmind GeoLite2
1424 Changes in version 0.2.5.7-rc - 2014-09-11
1425 Tor 0.2.5.7-rc fixes several regressions from earlier in the 0.2.5.x
1426 release series, and some long-standing bugs related to ORPort reachability
1427 testing and failure to send CREATE cells. It is the first release
1428 candidate for the Tor 0.2.5.x series.
1430 o Major bugfixes (client, startup):
1431 - Start making circuits as soon as DisabledNetwork is turned off.
1432 When Tor started with DisabledNetwork set, it would correctly
1433 conclude that it shouldn't build circuits, but it would mistakenly
1434 cache this conclusion, and continue believing it even when
1435 DisableNetwork is set to 0. Fixes the bug introduced by the fix
1436 for bug 11200; bugfix on 0.2.5.4-alpha.
1437 - Resume expanding abbreviations for command-line options. The fix
1438 for bug 4647 accidentally removed our hack from bug 586 that
1439 rewrote HashedControlPassword to __HashedControlSessionPassword
1440 when it appears on the commandline (which allowed the user to set
1441 her own HashedControlPassword in the torrc file while the
1442 controller generates a fresh session password for each run). Fixes
1443 bug 12948; bugfix on 0.2.5.1-alpha.
1444 - Warn about attempts to run hidden services and relays in the same
1445 process: that's probably not a good idea. Closes ticket 12908.
1447 o Major bugfixes (relay):
1448 - Avoid queuing or sending destroy cells for circuit ID zero when we
1449 fail to send a CREATE cell. Fixes bug 12848; bugfix on 0.0.8pre1.
1450 Found and fixed by "cypherpunks".
1451 - Fix ORPort reachability detection on relays running behind a
1452 proxy, by correctly updating the "local" mark on the controlling
1453 channel when changing the address of an or_connection_t after the
1454 handshake. Fixes bug 12160; bugfix on 0.2.4.4-alpha.
1456 o Minor features (bridge):
1457 - Add an ExtORPortCookieAuthFileGroupReadable option to make the
1458 cookie file for the ExtORPort g+r by default.
1460 o Minor features (geoip):
1461 - Update geoip and geoip6 to the August 7 2014 Maxmind GeoLite2
1464 o Minor bugfixes (logging):
1465 - Reduce the log severity of the "Pluggable transport proxy does not
1466 provide any needed transports and will not be launched." message,
1467 since Tor Browser includes several ClientTransportPlugin lines in
1468 its torrc-defaults file, leading every Tor Browser user who looks
1469 at her logs to see these notices and wonder if they're dangerous.
1470 Resolves bug 13124; bugfix on 0.2.5.3-alpha.
1471 - Downgrade "Unexpected onionskin length after decryption" warning
1472 to a protocol-warn, since there's nothing relay operators can do
1473 about a client that sends them a malformed create cell. Resolves
1474 bug 12996; bugfix on 0.0.6rc1.
1475 - Log more specific warnings when we get an ESTABLISH_RENDEZVOUS
1476 cell on a cannibalized or non-OR circuit. Resolves ticket 12997.
1477 - When logging information about an EXTEND2 or EXTENDED2 cell, log
1478 their names correctly. Fixes part of bug 12700; bugfix
1480 - When logging information about a relay cell whose command we don't
1481 recognize, log its command as an integer. Fixes part of bug 12700;
1482 bugfix on 0.2.1.10-alpha.
1483 - Escape all strings from the directory connection before logging
1484 them. Fixes bug 13071; bugfix on 0.1.1.15. Patch from "teor".
1486 o Minor bugfixes (controller):
1487 - Restore the functionality of CookieAuthFileGroupReadable. Fixes
1488 bug 12864; bugfix on 0.2.5.1-alpha.
1489 - Actually send TRANSPORT_LAUNCHED and HS_DESC events to
1490 controllers. Fixes bug 13085; bugfix on 0.2.5.1-alpha. Patch
1493 o Minor bugfixes (compilation):
1494 - Fix compilation of test.h with MSVC. Patch from Gisle Vanem;
1495 bugfix on 0.2.5.5-alpha.
1496 - Make the nmake make files work again. Fixes bug 13081. Bugfix on
1497 0.2.5.1-alpha. Patch from "NewEraCracker".
1498 - In routerlist_assert_ok(), don't take the address of a
1499 routerinfo's cache_info member unless that routerinfo is non-NULL.
1500 Fixes bug 13096; bugfix on 0.1.1.9-alpha. Patch by "teor".
1501 - Fix a large number of false positive warnings from the clang
1502 analyzer static analysis tool. This should make real warnings
1503 easier for clang analyzer to find. Patch from "teor". Closes
1506 o Distribution (systemd):
1507 - Verify configuration file via ExecStartPre in the systemd unit
1508 file. Patch from intrigeri; resolves ticket 12730.
1509 - Explicitly disable RunAsDaemon in the systemd unit file. Our
1510 current systemd unit uses "Type = simple", so systemd does not
1511 expect tor to fork. If the user has "RunAsDaemon 1" in their
1512 torrc, then things won't work as expected. This is e.g. the case
1513 on Debian (and derivatives), since there we pass "--defaults-torrc
1514 /usr/share/tor/tor-service-defaults-torrc" (that contains
1515 "RunAsDaemon 1") by default. Patch by intrigeri; resolves
1519 - Adjust the URLs in the README to refer to the new locations of
1520 several documents on the website. Fixes bug 12830. Patch from
1522 - Document 'reject6' and 'accept6' ExitPolicy entries. Resolves
1526 Changes in version 0.2.5.6-alpha - 2014-07-28
1527 Tor 0.2.5.6-alpha brings us a big step closer to slowing down the
1528 risk from guard rotation, and fixes a variety of other issues to get
1529 us closer to a release candidate.
1531 o Major features (also in 0.2.4.23):
1532 - Make the number of entry guards configurable via a new
1533 NumEntryGuards consensus parameter, and the number of directory
1534 guards configurable via a new NumDirectoryGuards consensus
1535 parameter. Implements ticket 12688.
1537 o Major bugfixes (also in 0.2.4.23):
1538 - Fix a bug in the bounds-checking in the 32-bit curve25519-donna
1539 implementation that caused incorrect results on 32-bit
1540 implementations when certain malformed inputs were used along with
1541 a small class of private ntor keys. This bug does not currently
1542 appear to allow an attacker to learn private keys or impersonate a
1543 Tor server, but it could provide a means to distinguish 32-bit Tor
1544 implementations from 64-bit Tor implementations. Fixes bug 12694;
1545 bugfix on 0.2.4.8-alpha. Bug found by Robert Ransom; fix from
1549 - Perform circuit cleanup operations even when circuit
1550 construction operations are disabled (because the network is
1551 disabled, or because there isn't enough directory information).
1552 Previously, when we were not building predictive circuits, we
1553 were not closing expired circuits either. Fixes bug 8387; bugfix on
1554 0.1.1.11-alpha. This bug became visible in 0.2.4.10-alpha when we
1555 became more strict about when we have "enough directory information
1559 - Authorities now assign the Guard flag to the fastest 25% of the
1560 network (it used to be the fastest 50%). Also raise the consensus
1561 weight that guarantees the Guard flag from 250 to 2000. For the
1562 current network, this results in about 1100 guards, down from 2500.
1563 This step paves the way for moving the number of entry guards
1564 down to 1 (proposal 236) while still providing reasonable expected
1565 performance for most users. Implements ticket 12690.
1566 - Update geoip and geoip6 to the July 10 2014 Maxmind GeoLite2
1568 - Slightly enhance the diagnostic message for bug 12184.
1570 o Minor bugfixes (also in 0.2.4.23):
1571 - Warn and drop the circuit if we receive an inbound 'relay early'
1572 cell. Those used to be normal to receive on hidden service circuits
1573 due to bug 1038, but the buggy Tor versions are long gone from
1574 the network so we can afford to resume watching for them. Resolves
1575 the rest of bug 1038; bugfix on 0.2.1.19.
1576 - Correct a confusing error message when trying to extend a circuit
1577 via the control protocol but we don't know a descriptor or
1578 microdescriptor for one of the specified relays. Fixes bug 12718;
1579 bugfix on 0.2.3.1-alpha.
1582 - Fix compilation when building with bufferevents enabled. (This
1583 configuration is still not expected to work, however.)
1584 Fixes bugs 12438, 12474, 11578; bugfixes on 0.2.5.1-alpha and
1585 0.2.5.3-alpha. Patches from Anthony G. Basile and Sathyanarayanan
1587 - Compile correctly with builds and forks of OpenSSL (such as
1588 LibreSSL) that disable compression. Fixes bug 12602; bugfix on
1589 0.2.1.1-alpha. Patch from "dhill".
1592 Changes in version 0.2.4.23 - 2014-07-28
1593 Tor 0.2.4.23 brings us a big step closer to slowing down the risk from
1594 guard rotation, and also backports several important fixes from the
1595 Tor 0.2.5 alpha release series.
1598 - Clients now look at the "usecreatefast" consensus parameter to
1599 decide whether to use CREATE_FAST or CREATE cells for the first hop
1600 of their circuit. This approach can improve security on connections
1601 where Tor's circuit handshake is stronger than the available TLS
1602 connection security levels, but the tradeoff is more computational
1603 load on guard relays. Implements proposal 221. Resolves ticket 9386.
1604 - Make the number of entry guards configurable via a new
1605 NumEntryGuards consensus parameter, and the number of directory
1606 guards configurable via a new NumDirectoryGuards consensus
1607 parameter. Implements ticket 12688.
1610 - Fix a bug in the bounds-checking in the 32-bit curve25519-donna
1611 implementation that caused incorrect results on 32-bit
1612 implementations when certain malformed inputs were used along with
1613 a small class of private ntor keys. This bug does not currently
1614 appear to allow an attacker to learn private keys or impersonate a
1615 Tor server, but it could provide a means to distinguish 32-bit Tor
1616 implementations from 64-bit Tor implementations. Fixes bug 12694;
1617 bugfix on 0.2.4.8-alpha. Bug found by Robert Ransom; fix from
1621 - Warn and drop the circuit if we receive an inbound 'relay early'
1622 cell. Those used to be normal to receive on hidden service circuits
1623 due to bug 1038, but the buggy Tor versions are long gone from
1624 the network so we can afford to resume watching for them. Resolves
1625 the rest of bug 1038; bugfix on 0.2.1.19.
1626 - Correct a confusing error message when trying to extend a circuit
1627 via the control protocol but we don't know a descriptor or
1628 microdescriptor for one of the specified relays. Fixes bug 12718;
1629 bugfix on 0.2.3.1-alpha.
1630 - Avoid an illegal read from stack when initializing the TLS
1631 module using a version of OpenSSL without all of the ciphers
1632 used by the v2 link handshake. Fixes bug 12227; bugfix on
1633 0.2.4.8-alpha. Found by "starlight".
1636 - Update geoip and geoip6 to the July 10 2014 Maxmind GeoLite2
1640 Changes in version 0.2.5.5-alpha - 2014-06-18
1641 Tor 0.2.5.5-alpha fixes a wide variety of remaining issues in the Tor
1642 0.2.5.x release series, including a couple of DoS issues, some
1643 performance regressions, a large number of bugs affecting the Linux
1644 seccomp2 sandbox code, and various other bugfixes. It also adds
1645 diagnostic bugfixes for a few tricky issues that we're trying to
1648 o Major features (security, traffic analysis resistance):
1649 - Several major improvements to the algorithm used to decide when to
1650 close TLS connections. Previous versions of Tor closed connections
1651 at a fixed interval after the last time a non-padding cell was
1652 sent over the connection, regardless of the target of the
1653 connection. Now, we randomize the intervals by adding up to 50% of
1654 their base value, we measure the length of time since connection
1655 last had at least one circuit, and we allow connections to known
1656 ORs to remain open a little longer (15 minutes instead of 3
1657 minutes minimum). These changes should improve Tor's resistance
1658 against some kinds of traffic analysis, and lower some overhead
1659 from needlessly closed connections. Fixes ticket 6799.
1660 Incidentally fixes ticket 12023; bugfix on 0.2.5.1-alpha.
1662 o Major bugfixes (security, OOM, new since 0.2.5.4-alpha, also in 0.2.4.22):
1663 - Fix a memory leak that could occur if a microdescriptor parse
1664 fails during the tokenizing step. This bug could enable a memory
1665 exhaustion attack by directory servers. Fixes bug 11649; bugfix
1668 o Major bugfixes (security, directory authorities):
1669 - Directory authorities now include a digest of each relay's
1670 identity key as a part of its microdescriptor.
1672 This is a workaround for bug 11743 (reported by "cypherpunks"),
1673 where Tor clients do not support receiving multiple
1674 microdescriptors with the same SHA256 digest in the same
1675 consensus. When clients receive a consensus like this, they only
1676 use one of the relays. Without this fix, a hostile relay could
1677 selectively disable some client use of target relays by
1678 constructing a router descriptor with a different identity and the
1679 same microdescriptor parameters and getting the authorities to
1680 list it in a microdescriptor consensus. This fix prevents an
1681 attacker from causing a microdescriptor collision, because the
1682 router's identity is not forgeable.
1684 o Major bugfixes (relay):
1685 - Use a direct dirport connection when uploading non-anonymous
1686 descriptors to the directory authorities. Previously, relays would
1687 incorrectly use tunnel connections under a fairly wide variety of
1688 circumstances. Fixes bug 11469; bugfix on 0.2.4.3-alpha.
1689 - When a circuit accidentally has the same circuit ID for its
1690 forward and reverse direction, correctly detect the direction of
1691 cells using that circuit. Previously, this bug made roughly one
1692 circuit in a million non-functional. Fixes bug 12195; this is a
1693 bugfix on every version of Tor.
1695 o Major bugfixes (client, pluggable transports):
1696 - When managing pluggable transports, use OS notification facilities
1697 to learn if they have crashed, and don't attempt to kill any
1698 process that has already exited. Fixes bug 8746; bugfix
1701 o Minor features (diagnostic):
1702 - When logging a warning because of bug 7164, additionally check the
1703 hash table for consistency (as proposed on ticket 11737). This may
1704 help diagnose bug 7164.
1705 - When we log a heartbeat, log how many one-hop circuits we have
1706 that are at least 30 minutes old, and log status information about
1707 a few of them. This is an attempt to track down bug 8387.
1708 - When encountering an unexpected CR while writing text to a file on
1709 Windows, log the name of the file. Should help diagnosing
1711 - Give more specific warnings when a client notices that an onion
1712 handshake has failed. Fixes ticket 9635.
1713 - Add significant new logging code to attempt to diagnose bug 12184,
1714 where relays seem to run out of available circuit IDs.
1715 - Improve the diagnostic log message for bug 8387 even further to
1716 try to improve our odds of figuring out why one-hop directory
1717 circuits sometimes do not get closed.
1719 o Minor features (security, memory management):
1720 - Memory allocation tricks (mempools and buffer freelists) are now
1721 disabled by default. You can turn them back on with
1722 --enable-mempools and --enable-buf-freelists respectively. We're
1723 disabling these features because malloc performance is good enough
1724 on most platforms, and a similar feature in OpenSSL exacerbated
1725 exploitation of the Heartbleed attack. Resolves ticket 11476.
1727 o Minor features (security):
1728 - Apply the secure SipHash-2-4 function to the hash table mapping
1729 circuit IDs and channels to circuits. We missed this one when we
1730 were converting all the other hash functions to use SipHash back
1731 in 0.2.5.3-alpha. Resolves ticket 11750.
1733 o Minor features (build):
1734 - The configure script has a --disable-seccomp option to turn off
1735 support for libseccomp on systems that have it, in case it (or
1736 Tor's use of it) is broken. Resolves ticket 11628.
1738 o Minor features (other):
1739 - Update geoip and geoip6 to the June 4 2014 Maxmind GeoLite2
1742 o Minor bugfixes (security, new since 0.2.5.4-alpha, also in 0.2.4.22):
1743 - When running a hidden service, do not allow TunneledDirConns 0;
1744 this will keep the hidden service from running, and also
1745 make it publish its descriptors directly over HTTP. Fixes bug 10849;
1746 bugfix on 0.2.1.1-alpha.
1748 o Minor bugfixes (performance):
1749 - Avoid a bug where every successful connection made us recompute
1750 the flag telling us whether we have sufficient information to
1751 build circuits. Previously, we would forget our cached value
1752 whenever we successfully opened a channel (or marked a router as
1753 running or not running for any other reason), regardless of
1754 whether we had previously believed the router to be running. This
1755 forced us to run an expensive update operation far too often.
1756 Fixes bug 12170; bugfix on 0.1.2.1-alpha.
1757 - Avoid using tor_memeq() for checking relay cell integrity. This
1758 removes a possible performance bottleneck. Fixes part of bug
1759 12169; bugfix on 0.2.1.31.
1761 o Minor bugfixes (compilation):
1762 - Fix compilation of test_status.c when building with MVSC. Bugfix
1763 on 0.2.5.4-alpha. Patch from Gisle Vanem.
1764 - Resolve GCC complaints on OpenBSD about discarding constness in
1765 TO_{ORIGIN,OR}_CIRCUIT functions. Fixes part of bug 11633; bugfix
1766 on 0.1.1.23. Patch from Dana Koch.
1767 - Resolve clang complaints on OpenBSD with -Wshorten-64-to-32 due to
1768 treatment of long and time_t as comparable types. Fixes part of
1769 bug 11633. Patch from Dana Koch.
1770 - Make Tor compile correctly with --disable-buf-freelists. Fixes bug
1771 11623; bugfix on 0.2.5.3-alpha.
1772 - When deciding whether to build the 64-bit curve25519
1773 implementation, detect platforms where we can compile 128-bit
1774 arithmetic but cannot link it. Fixes bug 11729; bugfix on
1775 0.2.4.8-alpha. Patch from "conradev".
1776 - Fix compilation when DNS_CACHE_DEBUG is enabled. Fixes bug 11761;
1777 bugfix on 0.2.3.13-alpha. Found by "cypherpunks".
1778 - Fix compilation with dmalloc. Fixes bug 11605; bugfix
1781 o Minor bugfixes (Directory server):
1782 - When sending a compressed set of descriptors or microdescriptors,
1783 make sure to finalize the zlib stream. Previously, we would write
1784 all the compressed data, but if the last descriptor we wanted to
1785 send was missing or too old, we would not mark the stream as
1786 finished. This caused problems for decompression tools. Fixes bug
1787 11648; bugfix on 0.1.1.23.
1789 o Minor bugfixes (Linux seccomp sandbox):
1790 - Make the seccomp sandbox code compile under ARM Linux. Fixes bug
1791 11622; bugfix on 0.2.5.1-alpha.
1792 - Avoid crashing when re-opening listener ports with the seccomp
1793 sandbox active. Fixes bug 12115; bugfix on 0.2.5.1-alpha.
1794 - Avoid crashing with the seccomp sandbox enabled along with
1795 ConstrainedSockets. Fixes bug 12139; bugfix on 0.2.5.1-alpha.
1796 - When we receive a SIGHUP with the sandbox enabled, correctly
1797 support rotating our log files. Fixes bug 12032; bugfix
1799 - Avoid crash when running with sandboxing enabled and
1800 DirReqStatistics not disabled. Fixes bug 12035; bugfix
1802 - Fix a "BUG" warning when trying to write bridge-stats files with
1803 the Linux syscall sandbox filter enabled. Fixes bug 12041; bugfix
1805 - Prevent the sandbox from crashing on startup when run with the
1806 --enable-expensive-hardening configuration option. Fixes bug
1807 11477; bugfix on 0.2.5.4-alpha.
1808 - When running with DirPortFrontPage and sandboxing both enabled,
1809 reload the DirPortFrontPage correctly when restarting. Fixes bug
1810 12028; bugfix on 0.2.5.1-alpha.
1811 - Don't try to enable the sandbox when using the Tor binary to check
1812 its configuration, hash a passphrase, or so on. Doing so was
1813 crashing on startup for some users. Fixes bug 11609; bugfix
1815 - Avoid warnings when running with sandboxing and node statistics
1816 enabled at the same time. Fixes part of 12064; bugfix on
1817 0.2.5.1-alpha. Patch from Michael Wolf.
1818 - Avoid warnings when running with sandboxing enabled at the same
1819 time as cookie authentication, hidden services, or directory
1820 authority voting. Fixes part of 12064; bugfix on 0.2.5.1-alpha.
1821 - Do not allow options that require calls to exec to be enabled
1822 alongside the seccomp2 sandbox: they will inevitably crash. Fixes
1823 bug 12043; bugfix on 0.2.5.1-alpha.
1824 - Handle failures in getpwnam()/getpwuid() when running with the
1825 User option set and the Linux syscall sandbox enabled. Fixes bug
1826 11946; bugfix on 0.2.5.1-alpha.
1827 - Refactor the getaddrinfo workaround that the seccomp sandbox uses
1828 to avoid calling getaddrinfo() after installing the sandbox
1829 filters. Previously, it preloaded a cache with the IPv4 address
1830 for our hostname, and nothing else. Now, it loads the cache with
1831 every address that it used to initialize the Tor process. Fixes
1832 bug 11970; bugfix on 0.2.5.1-alpha.
1834 o Minor bugfixes (pluggable transports):
1835 - Enable the ExtORPortCookieAuthFile option, to allow changing the
1836 default location of the authentication token for the extended OR
1837 Port as used by sever-side pluggable transports. We had
1838 implemented this option before, but the code to make it settable
1839 had been omitted. Fixes bug 11635; bugfix on 0.2.5.1-alpha.
1840 - Avoid another 60-second delay when starting Tor in a pluggable-
1841 transport-using configuration when we already have cached
1842 descriptors for our bridges. Fixes bug 11965; bugfix
1845 o Minor bugfixes (client):
1846 - Avoid "Tried to open a socket with DisableNetwork set" warnings
1847 when starting a client with bridges configured and DisableNetwork
1848 set. (Tor launcher starts Tor with DisableNetwork set the first
1849 time it runs.) Fixes bug 10405; bugfix on 0.2.3.9-alpha.
1851 o Minor bugfixes (testing):
1852 - The Python parts of the test scripts now work on Python 3 as well
1853 as Python 2, so systems where '/usr/bin/python' is Python 3 will
1854 no longer have the tests break. Fixes bug 11608; bugfix
1856 - When looking for versions of python that we could run the tests
1857 with, check for "python2.7" and "python3.3"; previously we were
1858 only looking for "python", "python2", and "python3". Patch from
1859 Dana Koch. Fixes bug 11632; bugfix on 0.2.5.2-alpha.
1860 - Fix all valgrind warnings produced by the unit tests. There were
1861 over a thousand memory leak warnings previously, mostly produced
1862 by forgetting to free things in the unit test code. Fixes bug
1863 11618, bugfixes on many versions of Tor.
1865 o Minor bugfixes (tor-fw-helper):
1866 - Give a correct log message when tor-fw-helper fails to launch.
1867 (Previously, we would say something like "tor-fw-helper sent us a
1868 string we could not parse".) Fixes bug 9781; bugfix
1871 o Minor bugfixes (relay, threading):
1872 - Check return code on spawn_func() in cpuworker code, so that we
1873 don't think we've spawned a nonworking cpuworker and write junk to
1874 it forever. Fix related to bug 4345; bugfix on all released Tor
1875 versions. Found by "skruffy".
1876 - Use a pthread_attr to make sure that spawn_func() cannot return an
1877 error while at the same time launching a thread. Fix related to
1878 bug 4345; bugfix on all released Tor versions. Reported
1881 o Minor bugfixes (relay, oom prevention):
1882 - Correctly detect the total available system memory. We tried to do
1883 this in 0.2.5.4-alpha, but the code was set up to always return an
1884 error value, even on success. Fixes bug 11805; bugfix
1887 o Minor bugfixes (relay, other):
1888 - We now drop CREATE cells for already-existent circuit IDs and for
1889 zero-valued circuit IDs, regardless of other factors that might
1890 otherwise have called for DESTROY cells. Fixes bug 12191; bugfix
1892 - Avoid an illegal read from stack when initializing the TLS module
1893 using a version of OpenSSL without all of the ciphers used by the
1894 v2 link handshake. Fixes bug 12227; bugfix on 0.2.4.8-alpha. Found
1896 - When rejecting DATA cells for stream_id zero, still count them
1897 against the circuit's deliver window so that we don't fail to send
1898 a SENDME. Fixes bug 11246; bugfix on 0.2.4.10-alpha.
1900 o Minor bugfixes (logging):
1901 - Fix a misformatted log message about delayed directory fetches.
1902 Fixes bug 11654; bugfix on 0.2.5.3-alpha.
1903 - Squelch a spurious LD_BUG message "No origin circuit for
1904 successful SOCKS stream" in certain hidden service failure cases;
1908 - Include a tor.service file in contrib/dist for use with systemd.
1909 Some distributions will be able to use this file unmodified;
1910 others will need to tweak it, or write their own. Patch from Jamie
1911 Nguyen; resolves ticket 8368.
1914 - Clean up several option names in the manpage to match their real
1915 names, add the missing documentation for a couple of testing and
1916 directory authority options, remove the documentation for a
1917 V2-directory fetching option that no longer exists. Resolves
1919 - Correct the documenation so that it lists the correct directory
1920 for the stats files. (They are in a subdirectory called "stats",
1922 - In the manpage, move more authority-only options into the
1923 directory authority section so that operators of regular directory
1924 caches don't get confused.
1927 - The contrib directory has been sorted and tidied. Before, it was
1928 an unsorted dumping ground for useful and not-so-useful things.
1929 Now, it is divided based on functionality, and the items which
1930 seemed to be nonfunctional or useless have been removed. Resolves
1931 ticket 8966; based on patches from "rl1987".
1934 - Remove /tor/dbg-stability.txt URL that was meant to help debug WFU
1935 and MTBF calculations, but that nobody was using. Fixes ticket 11742.
1936 - The TunnelDirConns and PreferTunnelledDirConns options no longer
1937 exist; tunneled directory connections have been available since
1938 0.1.2.5-alpha, and turning them off is not a good idea. This is a
1939 brute-force fix for 10849, where "TunnelDirConns 0" would break
1943 Changes in version 0.2.4.22 - 2014-05-16
1944 Tor 0.2.4.22 backports numerous high-priority fixes from the Tor 0.2.5
1945 alpha release series. These include blocking all authority signing
1946 keys that may have been affected by the OpenSSL "heartbleed" bug,
1947 choosing a far more secure set of TLS ciphersuites by default, closing
1948 a couple of memory leaks that could be used to run a target relay out
1949 of RAM, and several others.
1951 o Major features (security, backport from 0.2.5.4-alpha):
1952 - Block authority signing keys that were used on authorities
1953 vulnerable to the "heartbleed" bug in OpenSSL (CVE-2014-0160). (We
1954 don't have any evidence that these keys _were_ compromised; we're
1955 doing this to be prudent.) Resolves ticket 11464.
1957 o Major bugfixes (security, OOM):
1958 - Fix a memory leak that could occur if a microdescriptor parse
1959 fails during the tokenizing step. This bug could enable a memory
1960 exhaustion attack by directory servers. Fixes bug 11649; bugfix
1963 o Major bugfixes (TLS cipher selection, backport from 0.2.5.4-alpha):
1964 - The relay ciphersuite list is now generated automatically based on
1965 uniform criteria, and includes all OpenSSL ciphersuites with
1966 acceptable strength and forward secrecy. Previously, we had left
1967 some perfectly fine ciphersuites unsupported due to omission or
1968 typo. Resolves bugs 11513, 11492, 11498, 11499. Bugs reported by
1969 'cypherpunks'. Bugfix on 0.2.4.8-alpha.
1970 - Relays now trust themselves to have a better view than clients of
1971 which TLS ciphersuites are better than others. (Thanks to bug
1972 11513, the relay list is now well-considered, whereas the client
1973 list has been chosen mainly for anti-fingerprinting purposes.)
1974 Relays prefer: AES over 3DES; then ECDHE over DHE; then GCM over
1975 CBC; then SHA384 over SHA256 over SHA1; and last, AES256 over
1976 AES128. Resolves ticket 11528.
1977 - Clients now try to advertise the same list of ciphersuites as
1978 Firefox 28. This change enables selection of (fast) GCM
1979 ciphersuites, disables some strange old ciphers, and stops
1980 advertising the ECDH (not to be confused with ECDHE) ciphersuites.
1981 Resolves ticket 11438.
1983 o Minor bugfixes (configuration, security):
1984 - When running a hidden service, do not allow TunneledDirConns 0:
1985 trying to set that option together with a hidden service would
1986 otherwise prevent the hidden service from running, and also make
1987 it publish its descriptors directly over HTTP. Fixes bug 10849;
1988 bugfix on 0.2.1.1-alpha.
1990 o Minor bugfixes (controller, backport from 0.2.5.4-alpha):
1991 - Avoid sending a garbage value to the controller when a circuit is
1992 cannibalized. Fixes bug 11519; bugfix on 0.2.3.11-alpha.
1994 o Minor bugfixes (exit relay, backport from 0.2.5.4-alpha):
1995 - Stop leaking memory when we successfully resolve a PTR record.
1996 Fixes bug 11437; bugfix on 0.2.4.7-alpha.
1998 o Minor bugfixes (bridge client, backport from 0.2.5.4-alpha):
1999 - Avoid 60-second delays in the bootstrapping process when Tor is
2000 launching for a second time while using bridges. Fixes bug 9229;
2001 bugfix on 0.2.0.3-alpha.
2003 o Minor bugfixes (relays and bridges, backport from 0.2.5.4-alpha):
2004 - Give the correct URL in the warning message when trying to run a
2005 relay on an ancient version of Windows. Fixes bug 9393.
2007 o Minor bugfixes (compilation):
2008 - Fix a compilation error when compiling with --disable-curve25519.
2009 Fixes bug 9700; bugfix on 0.2.4.17-rc.
2012 - Downgrade the warning severity for the the "md was still
2013 referenced 1 node(s)" warning. Tor 0.2.5.4-alpha has better code
2014 for trying to diagnose this bug, and the current warning in
2015 earlier versions of tor achieves nothing useful. Addresses warning
2018 o Minor features (log verbosity, backport from 0.2.5.4-alpha):
2019 - When we run out of usable circuit IDs on a channel, log only one
2020 warning for the whole channel, and describe how many circuits
2021 there were on the channel. Fixes part of ticket 11553.
2023 o Minor features (security, backport from 0.2.5.4-alpha):
2024 - Decrease the lower limit of MaxMemInCellQueues to 256 MBytes (but
2025 leave the default at 8GBytes), to better support Raspberry Pi
2026 users. Fixes bug 9686; bugfix on 0.2.4.14-alpha.
2028 o Documentation (backport from 0.2.5.4-alpha):
2029 - Correctly document that we search for a system torrc file before
2030 looking in ~/.torrc. Fixes documentation side of 9213; bugfix on
2034 Changes in version 0.2.5.4-alpha - 2014-04-25
2035 Tor 0.2.5.4-alpha includes several security and performance
2036 improvements for clients and relays, including blacklisting authority
2037 signing keys that were used while susceptible to the OpenSSL
2038 "heartbleed" bug, fixing two expensive functions on busy relays,
2039 improved TLS ciphersuite preference lists, support for run-time
2040 hardening on compilers that support AddressSanitizer, and more work on
2041 the Linux sandbox code.
2043 There are also several usability fixes for clients (especially clients
2044 that use bridges), two new TransPort protocols supported (one on
2045 OpenBSD, one on FreeBSD), and various other bugfixes.
2047 This release marks end-of-life for Tor 0.2.2.x; those Tor versions
2048 have accumulated many known flaws; everyone should upgrade.
2050 o Major features (security):
2051 - If you don't specify MaxMemInQueues yourself, Tor now tries to
2052 pick a good value based on your total system memory. Previously,
2053 the default was always 8 GB. You can still override the default by
2054 setting MaxMemInQueues yourself. Resolves ticket 11396.
2055 - Block authority signing keys that were used on authorities
2056 vulnerable to the "heartbleed" bug in OpenSSL (CVE-2014-0160). (We
2057 don't have any evidence that these keys _were_ compromised; we're
2058 doing this to be prudent.) Resolves ticket 11464.
2060 o Major features (relay performance):
2061 - Speed up server-side lookups of rendezvous and introduction point
2062 circuits by using hashtables instead of linear searches. These
2063 functions previously accounted between 3 and 7% of CPU usage on
2064 some busy relays. Resolves ticket 9841.
2065 - Avoid wasting CPU when extending a circuit over a channel that is
2066 nearly out of circuit IDs. Previously, we would do a linear scan
2067 over possible circuit IDs before finding one or deciding that we
2068 had exhausted our possibilities. Now, we try at most 64 random
2069 circuit IDs before deciding that we probably won't succeed. Fixes
2070 a possible root cause of ticket 11553.
2072 o Major features (seccomp2 sandbox, Linux only):
2073 - The seccomp2 sandbox can now run a test network for multiple hours
2074 without crashing. The sandbox is still experimental, and more bugs
2075 will probably turn up. To try it, enable "Sandbox 1" on a Linux
2076 host. Resolves ticket 11351.
2077 - Strengthen sandbox code: the sandbox can now test the arguments
2078 for rename(), and blocks _sysctl() entirely. Resolves another part
2080 - When the sandbox blocks a system call, it now tries to log a stack
2081 trace before exiting. Resolves ticket 11465.
2083 o Major bugfixes (TLS cipher selection):
2084 - The relay ciphersuite list is now generated automatically based on
2085 uniform criteria, and includes all OpenSSL ciphersuites with
2086 acceptable strength and forward secrecy. Previously, we had left
2087 some perfectly fine ciphersuites unsupported due to omission or
2088 typo. Resolves bugs 11513, 11492, 11498, 11499. Bugs reported by
2089 'cypherpunks'. Bugfix on 0.2.4.8-alpha.
2090 - Relays now trust themselves to have a better view than clients of
2091 which TLS ciphersuites are better than others. (Thanks to bug
2092 11513, the relay list is now well-considered, whereas the client
2093 list has been chosen mainly for anti-fingerprinting purposes.)
2094 Relays prefer: AES over 3DES; then ECDHE over DHE; then GCM over
2095 CBC; then SHA384 over SHA256 over SHA1; and last, AES256 over
2096 AES128. Resolves ticket 11528.
2097 - Clients now try to advertise the same list of ciphersuites as
2098 Firefox 28. This change enables selection of (fast) GCM
2099 ciphersuites, disables some strange old ciphers, and stops
2100 advertising the ECDH (not to be confused with ECDHE) ciphersuites.
2101 Resolves ticket 11438.
2103 o Major bugfixes (bridge client):
2104 - Avoid 60-second delays in the bootstrapping process when Tor is
2105 launching for a second time while using bridges. Fixes bug 9229;
2106 bugfix on 0.2.0.3-alpha.
2108 o Minor features (transparent proxy, *BSD):
2109 - Support FreeBSD's ipfw firewall interface for TransPort ports on
2110 FreeBSD. To enable it, set "TransProxyType ipfw". Resolves ticket
2111 10267; patch from "yurivict".
2112 - Support OpenBSD's divert-to rules with the pf firewall for
2113 transparent proxy ports. To enable it, set "TransProxyType
2114 pf-divert". This allows Tor to run a TransPort transparent proxy
2115 port on OpenBSD 4.4 or later without root privileges. See the
2116 pf.conf(5) manual page for information on configuring pf to use
2117 divert-to rules. Closes ticket 10896; patch from Dana Koch.
2119 o Minor features (security):
2120 - New --enable-expensive-hardening option to enable security
2121 hardening options that consume nontrivial amounts of CPU and
2122 memory. Right now, this includes AddressSanitizer and UbSan, which
2123 are supported in newer versions of GCC and Clang. Closes ticket
2126 o Minor features (log verbosity):
2127 - Demote the message that we give when a flushing connection times
2128 out for too long from NOTICE to INFO. It was usually meaningless.
2129 Resolves ticket 5286.
2130 - Don't log so many notice-level bootstrapping messages at startup
2131 about downloading descriptors. Previously, we'd log a notice
2132 whenever we learned about more routers. Now, we only log a notice
2133 at every 5% of progress. Fixes bug 9963.
2134 - Warn less verbosely when receiving a malformed
2135 ESTABLISH_RENDEZVOUS cell. Fixes ticket 11279.
2136 - When we run out of usable circuit IDs on a channel, log only one
2137 warning for the whole channel, and describe how many circuits
2138 there were on the channel. Fixes part of ticket 11553.
2140 o Minor features (relay):
2141 - If a circuit timed out for at least 3 minutes, check if we have a
2142 new external IP address, and publish a new descriptor with the new
2143 IP address if it changed. Resolves ticket 2454.
2145 o Minor features (controller):
2146 - Make the entire exit policy available from the control port via
2147 GETINFO exit-policy/*. Implements enhancement 7952. Patch from
2149 - Because of the fix for ticket 11396, the real limit for memory
2150 usage may no longer match the configured MaxMemInQueues value. The
2151 real limit is now exposed via GETINFO limits/max-mem-in-queues.
2153 o Minor features (bridge client):
2154 - Report a more useful failure message when we can't connect to a
2155 bridge because we don't have the right pluggable transport
2156 configured. Resolves ticket 9665. Patch from Fábio J. Bertinatto.
2158 o Minor features (diagnostic):
2159 - Add more log messages to diagnose bug 7164, which causes
2160 intermittent "microdesc_free() called but md was still referenced"
2161 warnings. We now include more information, to figure out why we
2162 might be cleaning a microdescriptor for being too old if it's
2163 still referenced by a live node_t object.
2165 o Minor bugfixes (client, DNSPort):
2166 - When using DNSPort, try to respond to AAAA requests with AAAA
2167 answers. Previously, we hadn't looked at the request type when
2168 deciding which answer type to prefer. Fixes bug 10468; bugfix on
2170 - When receiving a DNS query for an unsupported record type, reply
2171 with no answer rather than with a NOTIMPL error. This behavior
2172 isn't correct either, but it will break fewer client programs, we
2173 hope. Fixes bug 10268; bugfix on 0.2.0.1-alpha. Original patch
2176 o Minor bugfixes (exit relay):
2177 - Stop leaking memory when we successfully resolve a PTR record.
2178 Fixes bug 11437; bugfix on 0.2.4.7-alpha.
2180 o Minor bugfixes (bridge client):
2181 - Stop accepting bridge lines containing hostnames. Doing so would
2182 cause clients to perform DNS requests on the hostnames, which was
2183 not sensible behavior. Fixes bug 10801; bugfix on 0.2.0.1-alpha.
2184 - Avoid a 60-second delay in the bootstrapping process when a Tor
2185 client with pluggable transports re-reads its configuration at
2186 just the wrong time. Re-fixes bug 11156; bugfix on 0.2.5.3-alpha.
2188 o Minor bugfixes (client, logging during bootstrap):
2189 - Warn only once if we start logging in an unsafe way. Previously,
2190 we complain as many times as we had problems. Fixes bug 9870;
2191 bugfix on 0.2.5.1-alpha.
2192 - Only report the first fatal bootstrap error on a given OR
2193 connection. This stops us from telling the controller bogus error
2194 messages like "DONE". Fixes bug 10431; bugfix on 0.2.1.1-alpha.
2195 - Be more helpful when trying to run sandboxed on Linux without
2196 libseccomp. Instead of saying "Sandbox is not implemented on this
2197 platform", we now explain that we need to be built with
2198 libseccomp. Fixes bug 11543; bugfix on 0.2.5.1-alpha.
2199 - Avoid generating spurious warnings when starting with
2200 DisableNetwork enabled. Fixes bug 11200 and bug 10405; bugfix on
2203 o Minor bugfixes (closing OR connections):
2204 - If write_to_buf() in connection_write_to_buf_impl_() ever fails,
2205 check if it's an or_connection_t and correctly call
2206 connection_or_close_for_error() rather than
2207 connection_mark_for_close() directly. Fixes bug 11304; bugfix on
2209 - When closing all connections on setting DisableNetwork to 1, use
2210 connection_or_close_normally() rather than closing OR connections
2211 out from under the channel layer. Fixes bug 11306; bugfix on
2214 o Minor bugfixes (controller):
2215 - Avoid sending a garbage value to the controller when a circuit is
2216 cannibalized. Fixes bug 11519; bugfix on 0.2.3.11-alpha.
2218 o Minor bugfixes (tor-fw-helper):
2219 - Allow tor-fw-helper to build again by adding src/ext to its
2220 CPPFLAGS. Fixes bug 11296; bugfix on 0.2.5.3-alpha.
2222 o Minor bugfixes (bridges):
2223 - Avoid potential crashes or bad behavior when launching a
2224 server-side managed proxy with ORPort or ExtORPort temporarily
2225 disabled. Fixes bug 9650; bugfix on 0.2.3.16-alpha.
2227 o Minor bugfixes (platform-specific):
2228 - Fix compilation on Solaris, which does not have <endian.h>. Fixes
2229 bug 11426; bugfix on 0.2.5.3-alpha.
2230 - When dumping a malformed directory object to disk, save it in
2231 binary mode on Windows, not text mode. Fixes bug 11342; bugfix on
2233 - Don't report failures from make_socket_reuseable() on incoming
2234 sockets on OSX: this can happen when incoming connections close
2235 early. Fixes bug 10081.
2237 o Minor bugfixes (trivial memory leaks):
2238 - Fix a small memory leak when signing a directory object. Fixes bug
2239 11275; bugfix on 0.2.4.13-alpha.
2240 - Free placeholder entries in our circuit table at exit; fixes a
2241 harmless memory leak. Fixes bug 11278; bugfix on 0.2.5.1-alpha.
2242 - Don't re-initialize a second set of OpenSSL mutexes when starting
2243 up. Previously, we'd make one set of mutexes, and then immediately
2244 replace them with another. Fixes bug 11726; bugfix on
2246 - Resolve some memory leaks found by coverity in the unit tests, on
2247 exit in tor-gencert, and on a failure to compute digests for our
2248 own keys when generating a v3 networkstatus vote. These leaks
2249 should never have affected anyone in practice.
2251 o Minor bugfixes (hidden service):
2252 - Only retry attempts to connect to a chosen rendezvous point 8
2253 times, not 30. Fixes bug 4241; bugfix on 0.1.0.1-rc.
2255 o Minor bugfixes (misc code correctness):
2256 - Fix various instances of undefined behavior in channeltls.c,
2257 tor_memmem(), and eventdns.c that would cause us to construct
2258 pointers to memory outside an allocated object. (These invalid
2259 pointers were not accessed, but C does not even allow them to
2260 exist.) Fixes bug 10363; bugfixes on 0.1.1.1-alpha, 0.1.2.1-alpha,
2261 0.2.0.10-alpha, and 0.2.3.6-alpha. Reported by "bobnomnom".
2262 - Use the AddressSanitizer and Ubsan sanitizers (in clang-3.4) to
2263 fix some miscellaneous errors in our tests and codebase. Fixes bug
2264 11232. Bugfixes on versions back as far as 0.2.1.11-alpha.
2265 - Always check return values for unlink, munmap, UnmapViewOfFile;
2266 check strftime return values more often. In some cases all we can
2267 do is report a warning, but this may help prevent deeper bugs from
2268 going unnoticed. Closes ticket 8787; bugfixes on many, many tor
2270 - Fix numerous warnings from the clang "scan-build" static analyzer.
2271 Some of these are programming style issues; some of them are false
2272 positives that indicated awkward code; some are undefined behavior
2273 cases related to constructing (but not using) invalid pointers;
2274 some are assumptions about API behavior; some are (harmlessly)
2275 logging sizeof(ptr) bytes from a token when sizeof(*ptr) would be
2276 correct; and one or two are genuine bugs that weren't reachable
2277 from the rest of the program. Fixes bug 8793; bugfixes on many,
2281 - Build the torify.1 manpage again. Previously, we were only trying
2282 to build it when also building tor-fw-helper. That's why we didn't
2283 notice that we'd broken the ability to build it. Fixes bug 11321;
2284 bugfix on 0.2.5.1-alpha.
2285 - Fix the layout of the SOCKSPort flags in the manpage. Fixes bug
2286 11061; bugfix on 0.2.4.7-alpha.
2287 - Correctly document that we search for a system torrc file before
2288 looking in ~/.torrc. Fixes documentation side of 9213; bugfix on
2290 - Resolve warnings from Doxygen.
2292 o Code simplifications and refactoring:
2293 - Remove is_internal_IP() function. Resolves ticket 4645.
2294 - Remove unused function circuit_dump_by_chan from circuitlist.c.
2295 Closes issue 9107; patch from "marek".
2296 - Change our use of the ENUM_BF macro to avoid declarations that
2299 o Deprecated versions:
2300 - Tor 0.2.2.x has reached end-of-life; it has received no patches or
2301 attention for some while. Directory authorities no longer accept
2302 descriptors from relays running any version of Tor prior to Tor
2303 0.2.3.16-alpha. Resolves ticket 11149.
2306 - New macros in test.h to simplify writing mock-functions for unit
2307 tests. Part of ticket 11507. Patch from Dana Koch.
2308 - Complete tests for the status.c module. Resolves ticket 11507.
2309 Patch from Dana Koch.
2312 - Remove all code for the long unused v1 directory protocol.
2313 Resolves ticket 11070.
2316 Changes in version 0.2.5.3-alpha - 2014-03-22
2317 Tor 0.2.5.3-alpha includes all the fixes from 0.2.4.21. It contains
2318 two new anti-DoS features for Tor relays, resolves a bug that kept
2319 SOCKS5 support for IPv6 from working, fixes several annoying usability
2320 issues for bridge users, and removes more old code for unused
2323 The Tor 0.2.5.x release series is now in patch-freeze: no feature
2324 patches not already written will be considered for inclusion in 0.2.5.x.
2326 o Major features (relay security, DoS-resistance):
2327 - When deciding whether we have run out of memory and we need to
2328 close circuits, also consider memory allocated in buffers for
2329 streams attached to each circuit.
2331 This change, which extends an anti-DoS feature introduced in
2332 0.2.4.13-alpha and improved in 0.2.4.14-alpha, lets Tor exit relays
2333 better resist more memory-based DoS attacks than before. Since the
2334 MaxMemInCellQueues option now applies to all queues, it is renamed
2335 to MaxMemInQueues. This feature fixes bug 10169.
2336 - Avoid hash-flooding denial-of-service attacks by using the secure
2337 SipHash-2-4 hash function for our hashtables. Without this
2338 feature, an attacker could degrade performance of a targeted
2339 client or server by flooding their data structures with a large
2340 number of entries to be stored at the same hash table position,
2341 thereby slowing down the Tor instance. With this feature, hash
2342 table positions are derived from a randomized cryptographic key,
2343 and an attacker cannot predict which entries will collide. Closes
2345 - Decrease the lower limit of MaxMemInQueues to 256 MBytes (but leave
2346 the default at 8GBytes), to better support Raspberry Pi users. Fixes
2347 bug 9686; bugfix on 0.2.4.14-alpha.
2349 o Minor features (bridges, pluggable transports):
2350 - Bridges now write the SHA1 digest of their identity key
2351 fingerprint (that is, a hash of a hash of their public key) to
2352 notice-level logs, and to a new hashed-fingerprint file. This
2353 information will help bridge operators look up their bridge in
2354 Globe and similar tools. Resolves ticket 10884.
2355 - Improve the message that Tor displays when running as a bridge
2356 using pluggable transports without an Extended ORPort listener.
2357 Also, log the message in the log file too. Resolves ticket 11043.
2359 o Minor features (other):
2360 - Add a new option, PredictedPortsRelevanceTime, to control how long
2361 after having received a request to connect to a given port Tor
2362 will try to keep circuits ready in anticipation of future requests
2363 for that port. Patch from "unixninja92"; implements ticket 9176.
2364 - Generate a warning if any ports are listed in the SocksPolicy,
2365 DirPolicy, AuthDirReject, AuthDirInvalid, AuthDirBadDir, or
2366 AuthDirBadExit options. (These options only support address
2367 ranges.) Fixes part of ticket 11108.
2368 - Update geoip and geoip6 to the February 7 2014 Maxmind GeoLite2
2371 o Minor bugfixes (new since 0.2.5.2-alpha, also in 0.2.4.21):
2372 - Build without warnings under clang 3.4. (We have some macros that
2373 define static functions only some of which will get used later in
2374 the module. Starting with clang 3.4, these give a warning unless the
2375 unused attribute is set on them.) Resolves ticket 10904.
2376 - Fix build warnings about missing "a2x" comment when building the
2377 manpages from scratch on OpenBSD; OpenBSD calls it "a2x.py".
2378 Fixes bug 10929; bugfix on 0.2.2.9-alpha. Patch from Dana Koch.
2380 o Minor bugfixes (client):
2381 - Improve the log message when we can't connect to a hidden service
2382 because all of the hidden service directory nodes hosting its
2383 descriptor are excluded. Improves on our fix for bug 10722, which
2384 was a bugfix on 0.2.0.10-alpha.
2385 - Raise a control port warning when we fail to connect to all of
2386 our bridges. Previously, we didn't inform the controller, and
2387 the bootstrap process would stall. Fixes bug 11069; bugfix on
2389 - Exit immediately when a process-owning controller exits.
2390 Previously, tor relays would wait for a little while after their
2391 controller exited, as if they had gotten an INT signal -- but this
2392 was problematic, since there was no feedback for the user. To do a
2393 clean shutdown, controllers should send an INT signal and give Tor
2394 a chance to clean up. Fixes bug 10449; bugfix on 0.2.2.28-beta.
2395 - Stop attempting to connect to bridges before our pluggable
2396 transports are configured (harmless but resulted in some erroneous
2397 log messages). Fixes bug 11156; bugfix on 0.2.3.2-alpha.
2398 - Fix connections to IPv6 addresses over SOCKS5. Previously, we were
2399 generating incorrect SOCKS5 responses, and confusing client
2400 applications. Fixes bug 10987; bugfix on 0.2.4.7-alpha.
2402 o Minor bugfixes (relays and bridges):
2403 - Avoid crashing on a malformed resolv.conf file when running a
2404 relay using Libevent 1. Fixes bug 8788; bugfix on 0.1.1.23.
2405 - Non-exit relays no longer launch mock DNS requests to check for
2406 DNS hijacking. This has been unnecessary since 0.2.1.7-alpha, when
2407 non-exit relays stopped servicing DNS requests. Fixes bug 965;
2408 bugfix on 0.2.1.7-alpha. Patch from Matt Pagan.
2409 - Bridges now report complete directory request statistics. Related
2410 to bug 5824; bugfix on 0.2.2.1-alpha.
2411 - Bridges now never collect statistics that were designed for
2412 relays. Fixes bug 5824; bugfix on 0.2.3.8-alpha.
2413 - Stop giving annoying warning messages when we decide not to launch
2414 a pluggable transport proxy that we don't need (because there are
2415 no bridges configured to use it). Resolves ticket 5018; bugfix
2417 - Give the correct URL in the warning message when trying to run a
2418 relay on an ancient version of Windows. Fixes bug 9393.
2420 o Minor bugfixes (backtrace support):
2421 - Support automatic backtraces on more platforms by using the
2422 "-fasynchronous-unwind-tables" compiler option. This option is
2423 needed for platforms like 32-bit Intel where "-fomit-frame-pointer"
2424 is on by default and table generation is not. This doesn't yet
2425 add Windows support; only Linux, OSX, and some BSDs are affected.
2426 Reported by 'cypherpunks'; fixes bug 11047; bugfix on 0.2.5.2-alpha.
2427 - Avoid strange behavior if two threads hit failed assertions at the
2428 same time and both try to log backtraces at once. (Previously, if
2429 this had happened, both threads would have stored their intermediate
2430 results in the same buffer, and generated junk outputs.) Reported by
2431 "cypherpunks". Fixes bug 11048; bugfix on 0.2.5.2-alpha.
2432 - Fix a compiler warning in format_number_sigsafe(). Bugfix on
2433 0.2.5.2-alpha; patch from Nick Hopper.
2435 o Minor bugfixes (unit tests):
2436 - Fix a small bug in the unit tests that might have made the tests
2437 call 'chmod' with an uninitialized bitmask. Fixes bug 10928;
2438 bugfix on 0.2.5.1-alpha. Patch from Dana Koch.
2441 - Remove all remaining code related to version-0 hidden service
2442 descriptors: they have not been in use since 0.2.2.1-alpha. Fixes
2443 the rest of bug 10841.
2446 - Document in the manpage that "KBytes" may also be written as
2447 "kilobytes" or "KB", that "Kbits" may also be written as
2448 "kilobits", and so forth. Closes ticket 9222.
2449 - Document that the ClientOnly config option overrides ORPort.
2450 Our old explanation made ClientOnly sound as though it did
2451 nothing at all. Resolves bug 9059.
2452 - Explain that SocksPolicy, DirPolicy, and similar options don't
2453 take port arguments. Fixes the other part of ticket 11108.
2454 - Fix a comment about the rend_server_descriptor_t.protocols field
2455 to more accurately describe its range. Also, make that field
2456 unsigned, to more accurately reflect its usage. Fixes bug 9099;
2457 bugfix on 0.2.1.5-alpha.
2458 - Fix the manpage's description of HiddenServiceAuthorizeClient:
2459 the maximum client name length is 16, not 19. Fixes bug 11118;
2460 bugfix on 0.2.1.6-alpha.
2462 o Code simplifications and refactoring:
2463 - Get rid of router->address, since in all cases it was just the
2464 string representation of router->addr. Resolves ticket 5528.
2466 o Test infrastructure:
2467 - Update to the latest version of tinytest.
2468 - Improve the tinytest implementation of string operation tests so
2469 that comparisons with NULL strings no longer crash the tests; they
2470 now just fail, normally. Fixes bug 9004; bugfix on 0.2.2.4-alpha.
2473 Changes in version 0.2.4.21 - 2014-02-28
2474 Tor 0.2.4.21 further improves security against potential adversaries who
2475 find breaking 1024-bit crypto doable, and backports several stability
2476 and robustness patches from the 0.2.5 branch.
2478 o Major features (client security):
2479 - When we choose a path for a 3-hop circuit, make sure it contains
2480 at least one relay that supports the NTor circuit extension
2481 handshake. Otherwise, there is a chance that we're building
2482 a circuit that's worth attacking by an adversary who finds
2483 breaking 1024-bit crypto doable, and that chance changes the game
2484 theory. Implements ticket 9777.
2487 - Do not treat streams that fail with reason
2488 END_STREAM_REASON_INTERNAL as indicating a definite circuit failure,
2489 since it could also indicate an ENETUNREACH connection error. Fixes
2490 part of bug 10777; bugfix on 0.2.4.8-alpha.
2492 o Code simplification and refactoring:
2493 - Remove data structures which were introduced to implement the
2494 CellStatistics option: they are now redundant with the new timestamp
2495 field in the regular packed_cell_t data structure, which we did
2496 in 0.2.4.18-rc in order to resolve bug 9093. Resolves ticket 10870.
2499 - Always clear OpenSSL bignums before freeing them -- even bignums
2500 that don't contain secrets. Resolves ticket 10793. Patch by
2502 - Build without warnings under clang 3.4. (We have some macros that
2503 define static functions only some of which will get used later in
2504 the module. Starting with clang 3.4, these give a warning unless the
2505 unused attribute is set on them.) Resolves ticket 10904.
2506 - Update geoip and geoip6 files to the February 7 2014 Maxmind
2507 GeoLite2 Country database.
2510 - Set the listen() backlog limit to the largest actually supported
2511 on the system, not to the value in a header file. Fixes bug 9716;
2512 bugfix on every released Tor.
2513 - Treat ENETUNREACH, EACCES, and EPERM connection failures at an
2514 exit node as a NOROUTE error, not an INTERNAL error, since they
2515 can apparently happen when trying to connect to the wrong sort
2516 of netblocks. Fixes part of bug 10777; bugfix on 0.1.0.1-rc.
2517 - Fix build warnings about missing "a2x" comment when building the
2518 manpages from scratch on OpenBSD; OpenBSD calls it "a2x.py".
2519 Fixes bug 10929; bugfix on 0.2.2.9-alpha. Patch from Dana Koch.
2520 - Avoid a segfault on SIGUSR1, where we had freed a connection but did
2521 not entirely remove it from the connection lists. Fixes bug 9602;
2522 bugfix on 0.2.4.4-alpha.
2523 - Fix a segmentation fault in our benchmark code when running with
2524 Fedora's OpenSSL package, or any other OpenSSL that provides
2525 ECDH but not P224. Fixes bug 10835; bugfix on 0.2.4.8-alpha.
2526 - Turn "circuit handshake stats since last time" log messages into a
2527 heartbeat message. Fixes bug 10485; bugfix on 0.2.4.17-rc.
2529 o Documentation fixes:
2530 - Document that all but one DirPort entry must have the NoAdvertise
2531 flag set. Fixes bug 10470; bugfix on 0.2.3.3-alpha / 0.2.3.16-alpha.
2534 Changes in version 0.2.5.2-alpha - 2014-02-13
2535 Tor 0.2.5.2-alpha includes all the fixes from 0.2.4.18-rc and 0.2.4.20,
2536 like the "poor random number generation" fix and the "building too many
2537 circuits" fix. It also further improves security against potential
2538 adversaries who find breaking 1024-bit crypto doable, and launches
2539 pluggable transports on demand (which gets us closer to integrating
2540 pluggable transport support by default -- not to be confused with Tor
2541 bundles enabling pluggable transports and bridges by default).
2543 o Major features (client security):
2544 - When we choose a path for a 3-hop circuit, make sure it contains
2545 at least one relay that supports the NTor circuit extension
2546 handshake. Otherwise, there is a chance that we're building
2547 a circuit that's worth attacking by an adversary who finds
2548 breaking 1024-bit crypto doable, and that chance changes the game
2549 theory. Implements ticket 9777.
2550 - Clients now look at the "usecreatefast" consensus parameter to
2551 decide whether to use CREATE_FAST or CREATE cells for the first hop
2552 of their circuit. This approach can improve security on connections
2553 where Tor's circuit handshake is stronger than the available TLS
2554 connection security levels, but the tradeoff is more computational
2555 load on guard relays. Implements proposal 221. Resolves ticket 9386.
2557 o Major features (bridges):
2558 - Don't launch pluggable transport proxies if we don't have any
2559 bridges configured that would use them. Now we can list many
2560 pluggable transports, and Tor will dynamically start one when it
2561 hears a bridge address that needs it. Resolves ticket 5018.
2562 - The bridge directory authority now assigns status flags (Stable,
2563 Guard, etc) to bridges based on thresholds calculated over all
2564 Running bridges. Now bridgedb can finally make use of its features
2565 to e.g. include at least one Stable bridge in its answers. Fixes
2568 o Major features (other):
2569 - Extend ORCONN controller event to include an "ID" parameter,
2570 and add four new controller event types CONN_BW, CIRC_BW,
2571 CELL_STATS, and TB_EMPTY that show connection and circuit usage.
2572 The new events are emitted in private Tor networks only, with the
2573 goal of being able to better track performance and load during
2574 full-network simulations. Implements proposal 218 and ticket 7359.
2575 - On some platforms (currently: recent OSX versions, glibc-based
2576 platforms that support the ELF format, and a few other
2577 Unix-like operating systems), Tor can now dump stack traces
2578 when a crash occurs or an assertion fails. By default, traces
2579 are dumped to stderr (if possible) and to any logs that are
2580 reporting errors. Implements ticket 9299.
2583 - Avoid a segfault on SIGUSR1, where we had freed a connection but did
2584 not entirely remove it from the connection lists. Fixes bug 9602;
2585 bugfix on 0.2.4.4-alpha.
2586 - Do not treat streams that fail with reason
2587 END_STREAM_REASON_INTERNAL as indicating a definite circuit failure,
2588 since it could also indicate an ENETUNREACH connection error. Fixes
2589 part of bug 10777; bugfix on 0.2.4.8-alpha.
2591 o Major bugfixes (new since 0.2.5.1-alpha, also in 0.2.4.20):
2592 - Do not allow OpenSSL engines to replace the PRNG, even when
2593 HardwareAccel is set. The only default builtin PRNG engine uses
2594 the Intel RDRAND instruction to replace the entire PRNG, and
2595 ignores all attempts to seed it with more entropy. That's
2596 cryptographically stupid: the right response to a new alleged
2597 entropy source is never to discard all previously used entropy
2598 sources. Fixes bug 10402; works around behavior introduced in
2599 OpenSSL 1.0.0. Diagnosis and investigation thanks to "coderman"
2601 - Fix assertion failure when AutomapHostsOnResolve yields an IPv6
2602 address. Fixes bug 10465; bugfix on 0.2.4.7-alpha.
2603 - Avoid launching spurious extra circuits when a stream is pending.
2604 This fixes a bug where any circuit that _wasn't_ unusable for new
2605 streams would be treated as if it were, causing extra circuits to
2606 be launched. Fixes bug 10456; bugfix on 0.2.4.12-alpha.
2608 o Major bugfixes (new since 0.2.5.1-alpha, also in 0.2.4.18-rc):
2609 - No longer stop reading or writing on cpuworker connections when
2610 our rate limiting buckets go empty. Now we should handle circuit
2611 handshake requests more promptly. Resolves bug 9731.
2612 - Stop trying to bootstrap all our directory information from
2613 only our first guard. Discovered while fixing bug 9946; bugfix
2616 o Minor features (bridges, pluggable transports):
2617 - Add threshold cutoffs to the networkstatus document created by
2618 the Bridge Authority. Fixes bug 1117.
2619 - On Windows, spawn background processes using the CREATE_NO_WINDOW
2620 flag. Now Tor Browser Bundle 3.5 with pluggable transports enabled
2621 doesn't pop up a blank console window. (In Tor Browser Bundle 2.x,
2622 Vidalia set this option for us.) Implements ticket 10297.
2624 o Minor features (security):
2625 - Always clear OpenSSL bignums before freeing them -- even bignums
2626 that don't contain secrets. Resolves ticket 10793. Patch by
2629 o Minor features (config options and command line):
2630 - Add an --allow-missing-torrc commandline option that tells Tor to
2631 run even if the configuration file specified by -f is not available.
2632 Implements ticket 10060.
2633 - Add support for the TPROXY transparent proxying facility on Linux.
2634 See documentation for the new TransProxyType option for more
2635 details. Implementation by "thomo". Closes ticket 10582.
2637 o Minor features (controller):
2638 - Add a new "HS_DESC" controller event that reports activities
2639 related to hidden service descriptors. Resolves ticket 8510.
2640 - New "DROPGUARDS" controller command to forget all current entry
2641 guards. Not recommended for ordinary use, since replacing guards
2642 too frequently makes several attacks easier. Resolves ticket 9934;
2645 o Minor features (build):
2646 - Assume that a user using ./configure --host wants to cross-compile,
2647 and give an error if we cannot find a properly named
2648 tool-chain. Add a --disable-tool-name-check option to proceed
2649 nevertheless. Addresses ticket 9869. Patch by Benedikt Gollatz.
2650 - If we run ./configure and the compiler recognizes -fstack-protector
2651 but the linker rejects it, warn the user about a potentially missing
2652 libssp package. Addresses ticket 9948. Patch from Benedikt Gollatz.
2654 o Minor features (testing):
2655 - If Python is installed, "make check" now runs extra tests beyond
2656 the unit test scripts.
2657 - When bootstrapping a test network, sometimes very few relays get
2658 the Guard flag. Now a new option "TestingDirAuthVoteGuard" can
2659 specify a set of relays which should be voted Guard regardless of
2660 their uptime or bandwidth. Addresses ticket 9206.
2662 o Minor features (log messages):
2663 - When ServerTransportPlugin is set on a bridge, Tor can write more
2664 useful statistics about bridge use in its extrainfo descriptors,
2665 but only if the Extended ORPort ("ExtORPort") is set too. Add a
2666 log message to inform the user in this case. Resolves ticket 9651.
2667 - When receiving a new controller connection, log the origin address.
2668 Resolves ticket 9698; patch from "sigpipe".
2669 - When logging OpenSSL engine status at startup, log the status of
2670 more engines. Fixes ticket 10043; patch from Joshua Datko.
2671 - Turn "circuit handshake stats since last time" log messages into a
2672 heartbeat message. Fixes bug 10485; bugfix on 0.2.4.17-rc.
2674 o Minor features (new since 0.2.5.1-alpha, also in 0.2.4.18-rc):
2675 - Improve the circuit queue out-of-memory handler. Previously, when
2676 we ran low on memory, we'd close whichever circuits had the most
2677 queued cells. Now, we close those that have the *oldest* queued
2678 cells, on the theory that those are most responsible for us
2679 running low on memory. Based on analysis from a forthcoming paper
2680 by Jansen, Tschorsch, Johnson, and Scheuermann. Fixes bug 9093.
2681 - Generate bootstrapping status update events correctly when fetching
2682 microdescriptors. Fixes bug 9927.
2683 - Update to the October 2 2013 Maxmind GeoLite Country database.
2685 o Minor bugfixes (clients):
2686 - When closing a channel that has already been open, do not close
2687 pending circuits that were waiting to connect to the same relay.
2688 Fixes bug 9880; bugfix on 0.2.5.1-alpha. Thanks to skruffy for
2691 o Minor bugfixes (relays):
2692 - Treat ENETUNREACH, EACCES, and EPERM connection failures at an
2693 exit node as a NOROUTE error, not an INTERNAL error, since they
2694 can apparently happen when trying to connect to the wrong sort
2695 of netblocks. Fixes part of bug 10777; bugfix on 0.1.0.1-rc.
2697 o Minor bugfixes (bridges):
2698 - Fix a bug where the first connection works to a bridge that uses a
2699 pluggable transport with client-side parameters, but we don't send
2700 the client-side parameters on subsequent connections. (We don't
2701 use any pluggable transports with client-side parameters yet,
2702 but ScrambleSuit will soon become the first one.) Fixes bug 9162;
2703 bugfix on 0.2.0.3-alpha. Based on a patch from "rl1987".
2705 o Minor bugfixes (node selection):
2706 - If ExcludeNodes is set, consider non-excluded hidden service
2707 directory servers before excluded ones. Do not consider excluded
2708 hidden service directory servers at all if StrictNodes is
2709 set. (Previously, we would sometimes decide to connect to those
2710 servers, and then realize before we initiated a connection that
2711 we had excluded them.) Fixes bug 10722; bugfix on 0.2.0.10-alpha.
2713 - If we set the ExitNodes option but it doesn't include any nodes
2714 that have the Exit flag, we would choose not to bootstrap. Now we
2715 bootstrap so long as ExitNodes includes nodes which can exit to
2716 some port. Fixes bug 10543; bugfix on 0.2.4.10-alpha.
2718 o Minor bugfixes (controller and command-line):
2719 - If changing a config option via "setconf" fails in a recoverable
2720 way, we used to nonetheless write our new control ports to the
2721 file described by the "ControlPortWriteToFile" option. Now we only
2722 write out that file if we successfully switch to the new config
2723 option. Fixes bug 5605; bugfix on 0.2.2.26-beta. Patch from "Ryman".
2724 - When a command-line option such as --version or --help that
2725 ordinarily implies --hush appears on the command line along with
2726 --quiet, then actually obey --quiet. Previously, we obeyed --quiet
2727 only if it appeared later on the command line. Fixes bug 9578;
2728 bugfix on 0.2.5.1-alpha.
2730 o Minor bugfixes (code correctness):
2731 - Previously we used two temporary files when writing descriptors to
2732 disk; now we only use one. Fixes bug 1376.
2733 - Remove an erroneous (but impossible and thus harmless) pointer
2734 comparison that would have allowed compilers to skip a bounds
2735 check in channeltls.c. Fixes bugs 10313 and 9980; bugfix on
2736 0.2.0.10-alpha. Noticed by Jared L Wong and David Fifield.
2737 - Fix an always-true assertion in pluggable transports code so it
2738 actually checks what it was trying to check. Fixes bug 10046;
2739 bugfix on 0.2.3.9-alpha. Found by "dcb".
2741 o Minor bugfixes (protocol correctness):
2742 - When receiving a VERSIONS cell with an odd number of bytes, close
2743 the connection immediately since the cell is malformed. Fixes bug
2744 10365; bugfix on 0.2.0.10-alpha. Spotted by "bobnomnom"; fix by
2747 o Minor bugfixes (build):
2748 - Restore the ability to compile Tor with V2_HANDSHAKE_SERVER
2749 turned off (that is, without support for v2 link handshakes). Fixes
2750 bug 4677; bugfix on 0.2.3.2-alpha. Patch from "piet".
2751 - Fix compilation warnings and startup issues when running with
2752 "Sandbox 1" and libseccomp-2.1.0. Fixes bug 10563; bugfix on
2754 - Fix compilation on Solaris 9, which didn't like us having an
2755 identifier named "sun". Fixes bug 10565; bugfix in 0.2.5.1-alpha.
2757 o Minor bugfixes (testing):
2758 - Fix a segmentation fault in our benchmark code when running with
2759 Fedora's OpenSSL package, or any other OpenSSL that provides
2760 ECDH but not P224. Fixes bug 10835; bugfix on 0.2.4.8-alpha.
2762 o Minor bugfixes (log messages):
2763 - Fix a bug where clients using bridges would report themselves
2764 as 50% bootstrapped even without a live consensus document.
2765 Fixes bug 9922; bugfix on 0.2.1.1-alpha.
2766 - Suppress a warning where, if there's only one directory authority
2767 in the network, we would complain that votes and signatures cannot
2768 be uploaded to other directory authorities. Fixes bug 10842;
2769 bugfix on 0.2.2.26-beta.
2770 - Report bootstrapping progress correctly when we're downloading
2771 microdescriptors. We had updated our "do we have enough microdescs
2772 to begin building circuits?" logic most recently in 0.2.4.10-alpha
2773 (see bug 5956), but we left the bootstrap status event logic at
2774 "how far through getting 1/4 of them are we?" Fixes bug 9958;
2775 bugfix on 0.2.2.36, which is where they diverged (see bug 5343).
2777 o Minor bugfixes (new since 0.2.5.1-alpha, also in 0.2.4.20):
2778 - Avoid a crash bug when starting with a corrupted microdescriptor
2779 cache file. Fixes bug 10406; bugfix on 0.2.2.6-alpha.
2780 - If we fail to dump a previously cached microdescriptor to disk, avoid
2781 freeing duplicate data later on. Fixes bug 10423; bugfix on
2782 0.2.4.13-alpha. Spotted by "bobnomnom".
2784 o Minor bugfixes on 0.2.4.x (new since 0.2.5.1-alpha, also in 0.2.4.18-rc):
2785 - Correctly log long IPv6 exit policies, instead of truncating them
2786 or reporting an error. Fixes bug 9596; bugfix on 0.2.4.7-alpha.
2787 - Our default TLS ecdhe groups were backwards: we meant to be using
2788 P224 for relays (for performance win) and P256 for bridges (since
2789 it is more common in the wild). Instead we had it backwards. After
2790 reconsideration, we decided that the default should be P256 on all
2791 hosts, since its security is probably better, and since P224 is
2792 reportedly used quite little in the wild. Found by "skruffy" on
2793 IRC. Fix for bug 9780; bugfix on 0.2.4.8-alpha.
2794 - Free directory authority certificate download statuses on exit
2795 rather than leaking them. Fixes bug 9644; bugfix on 0.2.4.13-alpha.
2797 o Minor bugfixes on 0.2.3.x (new since 0.2.5.1-alpha, also in 0.2.4.18-rc):
2798 - If the guard we choose first doesn't answer, we would try the
2799 second guard, but once we connected to the second guard we would
2800 abandon it and retry the first one, slowing down bootstrapping.
2801 The fix is to treat all our initially chosen guards as acceptable
2802 to use. Fixes bug 9946; bugfix on 0.1.1.11-alpha.
2803 - Fix an assertion failure that would occur when disabling the
2804 ORPort setting on a running Tor process while accounting was
2805 enabled. Fixes bug 6979; bugfix on 0.2.2.18-alpha.
2806 - When examining the list of network interfaces to find our address,
2807 do not consider non-running or disabled network interfaces. Fixes
2808 bug 9904; bugfix on 0.2.3.11-alpha. Patch from "hantwister".
2809 - Avoid an off-by-one error when checking buffer boundaries when
2810 formatting the exit status of a pluggable transport helper.
2811 This is probably not an exploitable bug, but better safe than
2812 sorry. Fixes bug 9928; bugfix on 0.2.3.18-rc. Bug found by
2815 o Removed code and features:
2816 - Clients now reject any directory authority certificates lacking
2817 a dir-key-crosscert element. These have been included since
2818 0.2.1.9-alpha, so there's no real reason for them to be optional
2819 any longer. Completes proposal 157. Resolves ticket 10162.
2820 - Remove all code that existed to support the v2 directory system,
2821 since there are no longer any v2 directory authorities. Resolves
2823 - Remove the HSAuthoritativeDir and AlternateHSAuthority torrc
2824 options, which were used for designating authorities as "Hidden
2825 service authorities". There has been no use of hidden service
2826 authorities since 0.2.2.1-alpha, when we stopped uploading or
2827 downloading v0 hidden service descriptors. Fixes bug 10881; also
2828 part of a fix for bug 10841.
2830 o Code simplification and refactoring:
2831 - Remove some old fallback code designed to keep Tor clients working
2832 in a network with only two working relays. Elsewhere in the code we
2833 have long since stopped supporting such networks, so there wasn't
2834 much point in keeping it around. Addresses ticket 9926.
2835 - Reject 0-length EXTEND2 cells more explicitly. Fixes bug 10536;
2836 bugfix on 0.2.4.8-alpha. Reported by "cypherpunks".
2837 - Remove data structures which were introduced to implement the
2838 CellStatistics option: they are now redundant with the addition
2839 of a timestamp to the regular packed_cell_t data structure, which
2840 we did in 0.2.4.18-rc in order to resolve ticket 9093. Implements
2843 o Documentation (man page) fixes:
2844 - Update manpage to describe some of the files you can expect to
2845 find in Tor's DataDirectory. Addresses ticket 9839.
2846 - Document that all but one DirPort entry must have the NoAdvertise
2847 flag set. Fixes bug 10470; bugfix on 0.2.3.3-alpha / 0.2.3.16-alpha.
2849 o Documentation fixes (new since 0.2.5.1-alpha, also in 0.2.4.18-rc):
2850 - Clarify the usage and risks of setting the ContactInfo torrc line
2851 for your relay or bridge. Resolves ticket 9854.
2852 - Add anchors to the manpage so we can link to the html version of
2853 the documentation for specific options. Resolves ticket 9866.
2854 - Replace remaining references to DirServer in man page and
2855 log entries. Resolves ticket 10124.
2858 - Make the "tor-gencert" tool used by directory authority operators
2859 create 2048-bit signing keys by default (rather than 1024-bit, since
2860 1024-bit is uncomfortably small these days). Addresses ticket 10324.
2863 Changes in version 0.2.4.20 - 2013-12-22
2864 Tor 0.2.4.20 fixes potentially poor random number generation for users
2865 who 1) use OpenSSL 1.0.0 or later, 2) set "HardwareAccel 1" in their
2866 torrc file, 3) have "Sandy Bridge" or "Ivy Bridge" Intel processors,
2867 and 4) have no state file in their DataDirectory (as would happen on
2868 first start). Users who generated relay or hidden service identity
2869 keys in such a situation should discard them and generate new ones.
2871 This release also fixes a logic error that caused Tor clients to build
2872 many more preemptive circuits than they actually need.
2875 - Do not allow OpenSSL engines to replace the PRNG, even when
2876 HardwareAccel is set. The only default builtin PRNG engine uses
2877 the Intel RDRAND instruction to replace the entire PRNG, and
2878 ignores all attempts to seed it with more entropy. That's
2879 cryptographically stupid: the right response to a new alleged
2880 entropy source is never to discard all previously used entropy
2881 sources. Fixes bug 10402; works around behavior introduced in
2882 OpenSSL 1.0.0. Diagnosis and investigation thanks to "coderman"
2884 - Fix assertion failure when AutomapHostsOnResolve yields an IPv6
2885 address. Fixes bug 10465; bugfix on 0.2.4.7-alpha.
2886 - Avoid launching spurious extra circuits when a stream is pending.
2887 This fixes a bug where any circuit that _wasn't_ unusable for new
2888 streams would be treated as if it were, causing extra circuits to
2889 be launched. Fixes bug 10456; bugfix on 0.2.4.12-alpha.
2892 - Avoid a crash bug when starting with a corrupted microdescriptor
2893 cache file. Fixes bug 10406; bugfix on 0.2.2.6-alpha.
2894 - If we fail to dump a previously cached microdescriptor to disk, avoid
2895 freeing duplicate data later on. Fixes bug 10423; bugfix on
2896 0.2.4.13-alpha. Spotted by "bobnomnom".
2899 Changes in version 0.2.4.19 - 2013-12-11
2900 The Tor 0.2.4 release series is dedicated to the memory of Aaron Swartz
2901 (1986-2013). Aaron worked on diverse projects including helping to guide
2902 Creative Commons, playing a key role in stopping SOPA/PIPA, bringing
2903 transparency to the U.S government's PACER documents, and contributing
2904 design and development for Tor and Tor2Web. Aaron was one of the latest
2905 martyrs in our collective fight for civil liberties and human rights,
2906 and his death is all the more painful because he was one of us.
2908 Tor 0.2.4.19, the first stable release in the 0.2.4 branch, features
2909 a new circuit handshake and link encryption that use ECC to provide
2910 better security and efficiency; makes relays better manage circuit
2911 creation requests; uses "directory guards" to reduce client enumeration
2912 risks; makes bridges collect and report statistics about the pluggable
2913 transports they support; cleans up and improves our geoip database;
2914 gets much closer to IPv6 support for clients, bridges, and relays; makes
2915 directory authorities use measured bandwidths rather than advertised
2916 ones when computing flags and thresholds; disables client-side DNS
2917 caching to reduce tracking risks; and fixes a big bug in bridge
2918 reachability testing. This release introduces two new design
2919 abstractions in the code: a new "channel" abstraction between circuits
2920 and or_connections to allow for implementing alternate relay-to-relay
2921 transports, and a new "circuitmux" abstraction storing the queue of
2922 circuits for a channel. The release also includes many stability,
2923 security, and privacy fixes.
2926 Changes in version 0.2.4.18-rc - 2013-11-16
2927 Tor 0.2.4.18-rc is the fourth release candidate for the Tor 0.2.4.x
2928 series. It takes a variety of fixes from the 0.2.5.x branch to improve
2929 stability, performance, and better handling of edge cases.
2932 - Re-enable TLS 1.1 and 1.2 when built with OpenSSL 1.0.1e or later.
2933 Resolves ticket 6055. (OpenSSL before 1.0.1 didn't have TLS 1.1 or
2934 1.2, and OpenSSL from 1.0.1 through 1.0.1d had bugs that prevented
2935 renegotiation from working with TLS 1.1 or 1.2, so we had disabled
2936 them to solve bug 6033.)
2939 - No longer stop reading or writing on cpuworker connections when
2940 our rate limiting buckets go empty. Now we should handle circuit
2941 handshake requests more promptly. Resolves bug 9731.
2942 - If we are unable to save a microdescriptor to the journal, do not
2943 drop it from memory and then reattempt downloading it. Fixes bug
2944 9645; bugfix on 0.2.2.6-alpha.
2945 - Stop trying to bootstrap all our directory information from
2946 only our first guard. Discovered while fixing bug 9946; bugfix
2948 - The new channel code sometimes lost track of in-progress circuits,
2949 causing long-running clients to stop building new circuits. The
2950 fix is to always call circuit_n_chan_done(chan, 0) from
2951 channel_closed(). Fixes bug 9776; bugfix on 0.2.4.17-rc.
2953 o Minor bugfixes (on 0.2.4.x):
2954 - Correctly log long IPv6 exit policies, instead of truncating them
2955 or reporting an error. Fixes bug 9596; bugfix on 0.2.4.7-alpha.
2956 - Our default TLS ecdhe groups were backwards: we meant to be using
2957 P224 for relays (for performance win) and P256 for bridges (since
2958 it is more common in the wild). Instead we had it backwards. After
2959 reconsideration, we decided that the default should be P256 on all
2960 hosts, since its security is probably better, and since P224 is
2961 reportedly used quite little in the wild. Found by "skruffy" on
2962 IRC. Fix for bug 9780; bugfix on 0.2.4.8-alpha.
2963 - Free directory authority certificate download statuses on exit
2964 rather than leaking them. Fixes bug 9644; bugfix on 0.2.4.13-alpha.
2966 o Minor bugfixes (on 0.2.3.x and earlier):
2967 - If the guard we choose first doesn't answer, we would try the
2968 second guard, but once we connected to the second guard we would
2969 abandon it and retry the first one, slowing down bootstrapping.
2970 The fix is to treat all our initially chosen guards as acceptable
2971 to use. Fixes bug 9946; bugfix on 0.1.1.11-alpha.
2972 - Fix an assertion failure that would occur when disabling the
2973 ORPort setting on a running Tor process while accounting was
2974 enabled. Fixes bug 6979; bugfix on 0.2.2.18-alpha.
2975 - When examining the list of network interfaces to find our address,
2976 do not consider non-running or disabled network interfaces. Fixes
2977 bug 9904; bugfix on 0.2.3.11-alpha. Patch from "hantwister".
2978 - Avoid an off-by-one error when checking buffer boundaries when
2979 formatting the exit status of a pluggable transport helper.
2980 This is probably not an exploitable bug, but better safe than
2981 sorry. Fixes bug 9928; bugfix on 0.2.3.18-rc. Bug found by
2984 o Minor features (protecting client timestamps):
2985 - Clients no longer send timestamps in their NETINFO cells. These were
2986 not used for anything, and they provided one small way for clients
2987 to be distinguished from each other as they moved from network to
2988 network or behind NAT. Implements part of proposal 222.
2989 - Clients now round timestamps in INTRODUCE cells down to the nearest
2990 10 minutes. If a new Support022HiddenServices option is set to 0, or
2991 if it's set to "auto" and the feature is disabled in the consensus,
2992 the timestamp is sent as 0 instead. Implements part of proposal 222.
2993 - Stop sending timestamps in AUTHENTICATE cells. This is not such
2994 a big deal from a security point of view, but it achieves no actual
2995 good purpose, and isn't needed. Implements part of proposal 222.
2996 - Reduce down accuracy of timestamps in hidden service descriptors.
2997 Implements part of proposal 222.
2999 o Minor features (other):
3000 - Improve the circuit queue out-of-memory handler. Previously, when
3001 we ran low on memory, we'd close whichever circuits had the most
3002 queued cells. Now, we close those that have the *oldest* queued
3003 cells, on the theory that those are most responsible for us
3004 running low on memory. Based on analysis from a forthcoming paper
3005 by Jansen, Tschorsch, Johnson, and Scheuermann. Fixes bug 9093.
3006 - Generate bootstrapping status update events correctly when fetching
3007 microdescriptors. Fixes bug 9927.
3008 - Update to the October 2 2013 Maxmind GeoLite Country database.
3010 o Documentation fixes:
3011 - Clarify the usage and risks of setting the ContactInfo torrc line
3012 for your relay or bridge. Resolves ticket 9854.
3013 - Add anchors to the manpage so we can link to the html version of
3014 the documentation for specific options. Resolves ticket 9866.
3015 - Replace remaining references to DirServer in man page and
3016 log entries. Resolves ticket 10124.
3019 Changes in version 0.2.5.1-alpha - 2013-10-02
3020 Tor 0.2.5.1-alpha introduces experimental support for syscall sandboxing
3021 on Linux, allows bridges that offer pluggable transports to report usage
3022 statistics, fixes many issues to make testing easier, and provides
3023 a pile of minor features and bugfixes that have been waiting for a
3024 release of the new branch.
3026 This is the first alpha release in a new series, so expect there to
3027 be bugs. Users who would rather test out a more stable branch should
3028 stay with 0.2.4.x for now.
3030 o Major features (security):
3031 - Use the seccomp2 syscall filtering facility on Linux to limit
3032 which system calls Tor can invoke. This is an experimental,
3033 Linux-only feature to provide defense-in-depth against unknown
3034 attacks. To try turning it on, set "Sandbox 1" in your torrc
3035 file. Please be ready to report bugs. We hope to add support
3036 for better sandboxing in the future, including more fine-grained
3037 filters, better division of responsibility, and support for more
3038 platforms. This work has been done by Cristian-Matei Toader for
3039 Google Summer of Code.
3040 - Re-enable TLS 1.1 and 1.2 when built with OpenSSL 1.0.1e or later.
3041 Resolves ticket 6055. (OpenSSL before 1.0.1 didn't have TLS 1.1 or
3042 1.2, and OpenSSL from 1.0.1 through 1.0.1d had bugs that prevented
3043 renegotiation from working with TLS 1.1 or 1.2, so we had disabled
3044 them to solve bug 6033.)
3046 o Major features (other):
3047 - Add support for passing arguments to managed pluggable transport
3048 proxies. Implements ticket 3594.
3049 - Bridges now track GeoIP information and the number of their users
3050 even when pluggable transports are in use, and report usage
3051 statistics in their extra-info descriptors. Resolves tickets 4773
3053 - Make testing Tor networks bootstrap better: lower directory fetch
3054 retry schedules and maximum interval without directory requests,
3055 and raise maximum download tries. Implements ticket 6752.
3056 - Add make target 'test-network' to run tests on a Chutney network.
3057 Implements ticket 8530.
3058 - The ntor handshake is now on-by-default, no matter what the
3059 directory authorities recommend. Implements ticket 8561.
3062 - Instead of writing destroy cells directly to outgoing connection
3063 buffers, queue them and intersperse them with other outgoing cells.
3064 This can prevent a set of resource starvation conditions where too
3065 many pending destroy cells prevent data cells from actually getting
3066 delivered. Reported by "oftc_must_be_destroyed". Fixes bug 7912;
3067 bugfix on 0.2.0.1-alpha.
3068 - If we are unable to save a microdescriptor to the journal, do not
3069 drop it from memory and then reattempt downloading it. Fixes bug
3070 9645; bugfix on 0.2.2.6-alpha.
3071 - The new channel code sometimes lost track of in-progress circuits,
3072 causing long-running clients to stop building new circuits. The
3073 fix is to always call circuit_n_chan_done(chan, 0) from
3074 channel_closed(). Fixes bug 9776; bugfix on 0.2.4.17-rc.
3077 - Tor now builds each source file in two modes: a mode that avoids
3078 exposing identifiers needlessly, and another mode that exposes
3079 more identifiers for testing. This lets the compiler do better at
3080 optimizing the production code, while enabling us to take more
3081 radical measures to let the unit tests test things.
3082 - The production builds no longer include functions used only in
3083 the unit tests; all functions exposed from a module only for
3084 unit-testing are now static in production builds.
3085 - Add an --enable-coverage configuration option to make the unit
3086 tests (and a new src/or/tor-cov target) to build with gcov test
3090 - We now have rudimentary function mocking support that our unit
3091 tests can use to test functions in isolation. Function mocking
3092 lets the tests temporarily replace a function's dependencies with
3093 stub functions, so that the tests can check the function without
3094 invoking the other functions it calls.
3095 - Add more unit tests for the <circid,channel>->circuit map, and
3096 the destroy-cell-tracking code to fix bug 7912.
3097 - Unit tests for failing cases of the TAP onion handshake.
3098 - More unit tests for address-manipulation functions.
3100 o Minor features (protecting client timestamps):
3101 - Clients no longer send timestamps in their NETINFO cells. These were
3102 not used for anything, and they provided one small way for clients
3103 to be distinguished from each other as they moved from network to
3104 network or behind NAT. Implements part of proposal 222.
3105 - Clients now round timestamps in INTRODUCE cells down to the nearest
3106 10 minutes. If a new Support022HiddenServices option is set to 0, or
3107 if it's set to "auto" and the feature is disabled in the consensus,
3108 the timestamp is sent as 0 instead. Implements part of proposal 222.
3109 - Stop sending timestamps in AUTHENTICATE cells. This is not such
3110 a big deal from a security point of view, but it achieves no actual
3111 good purpose, and isn't needed. Implements part of proposal 222.
3112 - Reduce down accuracy of timestamps in hidden service descriptors.
3113 Implements part of proposal 222.
3115 o Minor features (config options):
3116 - Config (torrc) lines now handle fingerprints which are missing
3117 their initial '$'. Resolves ticket 4341; improvement over 0.0.9pre5.
3118 - Support a --dump-config option to print some or all of the
3119 configured options. Mainly useful for debugging the command-line
3120 option parsing code. Helps resolve ticket 4647.
3121 - Raise awareness of safer logging: notify user of potentially
3122 unsafe config options, like logging more verbosely than severity
3123 "notice" or setting SafeLogging to 0. Resolves ticket 5584.
3124 - Add a new configuration option TestingV3AuthVotingStartOffset
3125 that bootstraps a network faster by changing the timing for
3126 consensus votes. Addresses ticket 8532.
3127 - Add a new torrc option "ServerTransportOptions" that allows
3128 bridge operators to pass configuration parameters to their
3129 pluggable transports. Resolves ticket 8929.
3130 - The config (torrc) file now accepts bandwidth and space limits in
3131 bits as well as bytes. (Anywhere that you can say "2 Kilobytes",
3132 you can now say "16 kilobits", and so on.) Resolves ticket 9214.
3135 o Minor features (build):
3136 - Add support for `--library-versions` flag. Implements ticket 6384.
3137 - Return the "unexpected sendme" warnings to a warn severity, but make
3138 them rate limited, to help diagnose ticket 8093.
3139 - Detect a missing asciidoc, and warn the user about it, during
3140 configure rather than at build time. Fixes issue 6506. Patch from
3143 o Minor features (other):
3144 - Use the SOCK_NONBLOCK socket type, if supported, to open nonblocking
3145 sockets in a single system call. Implements ticket 5129.
3146 - Log current accounting state (bytes sent and received + remaining
3147 time for the current accounting period) in the relay's heartbeat
3148 message. Implements ticket 5526; patch from Peter Retzlaff.
3149 - Implement the TRANSPORT_LAUNCHED control port event that
3150 notifies controllers about new launched pluggable
3151 transports. Resolves ticket 5609.
3152 - If we're using the pure-C 32-bit curve25519_donna implementation
3153 of curve25519, build it with the -fomit-frame-pointer option to
3154 make it go faster on register-starved hosts. This improves our
3155 handshake performance by about 6% on i386 hosts without nacl.
3157 - Update to the September 4 2013 Maxmind GeoLite Country database.
3160 - Set the listen() backlog limit to the largest actually supported
3161 on the system, not to the value in a header file. Fixes bug 9716;
3162 bugfix on every released Tor.
3163 - No longer accept malformed http headers when parsing urls from
3164 headers. Now we reply with Bad Request ("400"). Fixes bug 2767;
3165 bugfix on 0.0.6pre1.
3166 - In munge_extrainfo_into_routerinfo(), check the return value of
3167 memchr(). This would have been a serious issue if we ever passed
3168 it a non-extrainfo. Fixes bug 8791; bugfix on 0.2.0.6-alpha. Patch
3170 - On the chance that somebody manages to build Tor on a
3171 platform where time_t is unsigned, correct the way that
3172 microdesc_add_to_cache() handles negative time arguments.
3173 Fixes bug 8042; bugfix on 0.2.3.1-alpha.
3174 - Reject relative control socket paths and emit a warning. Previously,
3175 single-component control socket paths would be rejected, but Tor
3176 would not log why it could not validate the config. Fixes bug 9258;
3177 bugfix on 0.2.3.16-alpha.
3179 o Minor bugfixes (command line):
3180 - Use a single command-line parser for parsing torrc options on the
3181 command line and for finding special command-line options to avoid
3182 inconsistent behavior for torrc option arguments that have the same
3183 names as command-line options. Fixes bugs 4647 and 9578; bugfix on
3185 - No longer allow 'tor --hash-password' with no arguments. Fixes bug
3186 9573; bugfix on 0.0.9pre5.
3188 o Minor fixes (build, auxiliary programs):
3189 - Stop preprocessing the "torify" script with autoconf, since
3190 it no longer refers to LOCALSTATEDIR. Fixes bug 5505; patch
3192 - The tor-fw-helper program now follows the standard convention and
3193 exits with status code "0" on success. Fixes bug 9030; bugfix on
3194 0.2.3.1-alpha. Patch by Arlo Breault.
3195 - Corrected ./configure advice for what openssl dev package you should
3196 install on Debian. Fixes bug 9207; bugfix on 0.2.0.1-alpha.
3198 o Minor code improvements:
3199 - Remove constants and tests for PKCS1 padding; it's insecure and
3200 shouldn't be used for anything new. Fixes bug 8792; patch
3202 - Remove instances of strcpy() from the unit tests. They weren't
3203 hurting anything, since they were only in the unit tests, but it's
3204 embarassing to have strcpy() in the code at all, and some analysis
3205 tools don't like it. Fixes bug 8790; bugfix on 0.2.3.6-alpha and
3206 0.2.3.8-alpha. Patch from Arlo Breault.
3209 - Remove migration code from when we renamed the "cached-routers"
3210 file to "cached-descriptors" back in 0.2.0.8-alpha. This
3211 incidentally resolves ticket 6502 by cleaning up the related code
3212 a bit. Patch from Akshay Hebbar.
3214 o Code simplification and refactoring:
3215 - Extract the common duplicated code for creating a subdirectory
3216 of the data directory and writing to a file in it. Fixes ticket
3217 4282; patch from Peter Retzlaff.
3218 - Since OpenSSL 0.9.7, the i2d_*() functions support allocating output
3219 buffer. Avoid calling twice: i2d_RSAPublicKey(), i2d_DHparams(),
3220 i2d_X509(), and i2d_PublicKey(). Resolves ticket 5170.
3221 - Add a set of accessor functions for the circuit timeout data
3222 structure. Fixes ticket 6153; patch from "piet".
3223 - Clean up exit paths from connection_listener_new(). Closes ticket
3224 8789. Patch from Arlo Breault.
3225 - Since we rely on OpenSSL 0.9.8 now, we can use EVP_PKEY_cmp()
3226 and drop our own custom pkey_eq() implementation. Fixes bug 9043.
3227 - Use a doubly-linked list to implement the global circuit list.
3228 Resolves ticket 9108. Patch from Marek Majkowski.
3229 - Remove contrib/id_to_fp.c since it wasn't used anywhere.
3232 Changes in version 0.2.4.17-rc - 2013-09-05
3233 Tor 0.2.4.17-rc is the third release candidate for the Tor 0.2.4.x
3234 series. It adds an emergency step to help us tolerate the massive
3235 influx of users: 0.2.4 clients using the new (faster and safer) "NTor"
3236 circuit-level handshakes now effectively jump the queue compared to
3237 the 0.2.3 clients using "TAP" handshakes. This release also fixes a
3238 big bug hindering bridge reachability tests.
3241 - Relays now process the new "NTor" circuit-level handshake requests
3242 with higher priority than the old "TAP" circuit-level handshake
3243 requests. We still process some TAP requests to not totally starve
3244 0.2.3 clients when NTor becomes popular. A new consensus parameter
3245 "NumNTorsPerTAP" lets us tune the balance later if we need to.
3246 Implements ticket 9574.
3249 - If the circuit build timeout logic is disabled (via the consensus,
3250 or because we are an authority), then don't build testing circuits.
3251 Fixes bug 9657; bugfix on 0.2.2.14-alpha.
3252 - Bridges now send AUTH_CHALLENGE cells during their v3 handshakes;
3253 previously they did not, which prevented them from receiving
3254 successful connections from relays for self-test or bandwidth
3255 testing. Also, when a relay is extending a circuit to a bridge,
3256 it needs to send a NETINFO cell, even when the bridge hasn't sent
3257 an AUTH_CHALLENGE cell. Fixes bug 9546; bugfix on 0.2.3.6-alpha.
3258 - If the time to download the next old-style networkstatus is in
3259 the future, do not decline to consider whether to download the
3260 next microdescriptor networkstatus. Fixes bug 9564; bugfix on
3264 - Avoid double-closing the listener socket in our socketpair()
3265 replacement (used on Windows) in the case where the addresses on
3266 our opened sockets don't match what we expected. Fixes bug 9400;
3267 bugfix on 0.0.2pre7. Found by Coverity.
3269 o Minor fixes (config options):
3270 - Avoid overflows when the user sets MaxCircuitDirtiness to a
3271 ridiculously high value, by imposing a (ridiculously high) 30-day
3272 maximum on MaxCircuitDirtiness.
3273 - Fix the documentation of HeartbeatPeriod to say that the heartbeat
3274 message is logged at notice, not at info.
3275 - Warn and fail if a server is configured not to advertise any
3276 ORPorts at all. (We need *something* to put in our descriptor,
3277 or we just won't work.)
3280 - Track how many "TAP" and "NTor" circuit handshake requests we get,
3281 and how many we complete, and log it every hour to help relay
3282 operators follow trends in network load. Addresses ticket 9658.
3283 - Update to the August 7 2013 Maxmind GeoLite Country database.
3286 Changes in version 0.2.4.16-rc - 2013-08-10
3287 Tor 0.2.4.16-rc is the second release candidate for the Tor 0.2.4.x
3288 series. It fixes several crash bugs in the 0.2.4 branch.
3291 - Fix a bug in the voting algorithm that could yield incorrect results
3292 when a non-naming authority declared too many flags. Fixes bug 9200;
3293 bugfix on 0.2.0.3-alpha.
3294 - Fix an uninitialized read that could in some cases lead to a remote
3295 crash while parsing INTRODUCE2 cells. Bugfix on 0.2.4.1-alpha.
3296 Anybody running a hidden service on the experimental 0.2.4.x
3297 branch should upgrade. (This is, so far as we know, unrelated to
3299 - Avoid an assertion failure when processing DNS replies without the
3300 answer types we expected. Fixes bug 9337; bugfix on 0.2.4.7-alpha.
3301 - Avoid a crash when using --hash-password. Fixes bug 9295; bugfix on
3302 0.2.4.15-rc. Found by stem integration tests.
3305 - Fix an invalid memory read that occured when a pluggable
3306 transport proxy failed its configuration protocol.
3307 Fixes bug 9288; bugfix on 0.2.4.1-alpha.
3308 - When evaluating whether to use a connection that we haven't
3309 decided is canonical using a recent link protocol version,
3310 decide that it's canonical only if it used address _does_
3311 match the desired address. Fixes bug 9309; bugfix on
3312 0.2.4.4-alpha. Reported by skruffy.
3313 - Make the default behavior of NumDirectoryGuards be to track
3314 NumEntryGuards. Now a user who changes only NumEntryGuards will get
3315 the behavior she expects. Fixes bug 9354; bugfix on 0.2.4.8-alpha.
3316 - Fix a spurious compilation warning with some older versions of
3317 GCC on FreeBSD. Fixes bug 9254; bugfix on 0.2.4.14-alpha.
3320 - Update to the July 3 2013 Maxmind GeoLite Country database.
3323 Changes in version 0.2.4.15-rc - 2013-07-01
3324 Tor 0.2.4.15-rc is the first release candidate for the Tor 0.2.4.x
3325 series. It fixes a few smaller bugs, but generally appears stable.
3326 Please test it and let us know whether it is!
3329 - When receiving a new configuration file via the control port's
3330 LOADCONF command, do not treat the defaults file as absent.
3331 Fixes bug 9122; bugfix on 0.2.3.9-alpha.
3334 - Issue a warning when running with the bufferevents backend enabled.
3335 It's still not stable, and people should know that they're likely
3336 to hit unexpected problems. Closes ticket 9147.
3339 Changes in version 0.2.4.14-alpha - 2013-06-18
3340 Tor 0.2.4.14-alpha fixes a pair of client guard enumeration problems
3341 present in 0.2.4.13-alpha.
3344 - When we have too much memory queued in circuits (according to a new
3345 MaxMemInCellQueues option), close the circuits consuming the most
3346 memory. This prevents us from running out of memory as a relay if
3347 circuits fill up faster than they can be drained. Fixes bug 9063;
3348 bugfix on the 54th commit of Tor. This bug is a further fix beyond
3349 bug 6252, whose fix was merged into 0.2.3.21-rc.
3351 This change also fixes an earlier approach taken in 0.2.4.13-alpha,
3352 where we tried to solve this issue simply by imposing an upper limit
3353 on the number of queued cells for a single circuit. That approach
3354 proved to be problematic, since there are ways to provoke clients to
3355 send a number of cells in excess of any such reasonable limit. Fixes
3356 bug 9072; bugfix on 0.2.4.13-alpha.
3358 - Limit hidden service descriptors to at most ten introduction
3359 points, to slow one kind of guard enumeration. Fixes bug 9002;
3360 bugfix on 0.1.1.11-alpha.
3363 Changes in version 0.2.4.13-alpha - 2013-06-14
3364 Tor 0.2.4.13-alpha fixes a variety of potential remote crash
3365 vulnerabilities, makes socks5 username/password circuit isolation
3366 actually actually work (this time for sure!), and cleans up a bunch
3367 of other issues in preparation for a release candidate.
3369 o Major bugfixes (robustness):
3370 - Close any circuit that has too many cells queued on it. Fixes
3371 bug 9063; bugfix on the 54th commit of Tor. This bug is a further
3372 fix beyond bug 6252, whose fix was merged into 0.2.3.21-rc.
3373 - Prevent the get_freelists() function from running off the end of
3374 the list of freelists if it somehow gets an unrecognized
3375 allocation. Fixes bug 8844; bugfix on 0.2.0.16-alpha. Reported by
3377 - Avoid an assertion failure on OpenBSD (and perhaps other BSDs)
3378 when an exit connection with optimistic data succeeds immediately
3379 rather than returning EINPROGRESS. Fixes bug 9017; bugfix on
3381 - Fix a directory authority crash bug when building a consensus
3382 using an older consensus as its basis. Fixes bug 8833. Bugfix
3386 - Avoid a memory leak where we would leak a consensus body when we
3387 find that a consensus which we couldn't previously verify due to
3388 missing certificates is now verifiable. Fixes bug 8719; bugfix
3390 - We used to always request authority certificates by identity digest,
3391 meaning we'd get the newest one even when we wanted one with a
3392 different signing key. Then we would complain about being given
3393 a certificate we already had, and never get the one we really
3394 wanted. Now we use the "fp-sk/" resource as well as the "fp/"
3395 resource to request the one we want. Fixes bug 5595; bugfix on
3397 - Follow the socks5 protocol when offering username/password
3398 authentication. The fix for bug 8117 exposed this bug, and it
3399 turns out real-world applications like Pidgin do care. Bugfix on
3400 0.2.3.2-alpha; fixes bug 8879.
3401 - Prevent failures on Windows Vista and later when rebuilding the
3402 microdescriptor cache. Diagnosed by Robert Ransom. Fixes bug 8822;
3403 bugfix on 0.2.4.12-alpha.
3406 - Fix an impossible buffer overrun in the AES unit tests. Fixes
3407 bug 8845; bugfix on 0.2.0.7-alpha. Found by eugenis.
3408 - If for some reason we fail to write a microdescriptor while
3409 rebuilding the cache, do not let the annotations from that
3410 microdescriptor linger in the cache file, and do not let the
3411 microdescriptor stay recorded as present in its old location.
3412 Fixes bug 9047; bugfix on 0.2.2.6-alpha.
3413 - Fix a memory leak that would occur whenever a configuration
3414 option changed. Fixes bug 8718; bugfix on 0.2.3.3-alpha.
3415 - Paste the description for PathBias parameters from the man
3416 page into or.h, so the code documents them too. Fixes bug 7982;
3417 bugfix on 0.2.3.17-beta and 0.2.4.8-alpha.
3418 - Relays now treat a changed IPv6 ORPort as sufficient reason to
3419 publish an updated descriptor. Fixes bug 6026; bugfix on
3421 - When launching a resolve request on behalf of an AF_UNIX control
3422 socket, omit the address field of the new entry connection, used in
3423 subsequent controller events, rather than letting tor_dup_addr()
3424 set it to "<unknown address type>". Fixes bug 8639; bugfix on
3427 o Minor bugfixes (log messages):
3428 - Fix a scaling issue in the path bias accounting code that
3429 resulted in "Bug:" log messages from either
3430 pathbias_scale_close_rates() or pathbias_count_build_success().
3431 This represents a bugfix on a previous bugfix: the original fix
3432 attempted in 0.2.4.10-alpha was incomplete. Fixes bug 8235; bugfix
3434 - Give a less useless error message when the user asks for an IPv4
3435 address on an IPv6-only port, or vice versa. Fixes bug 8846; bugfix
3439 - Downgrade "unexpected SENDME" warnings to protocol-warn for 0.2.4.x,
3440 to tolerate bug 8093 for now.
3441 - Add an "ignoring-advertised-bws" boolean to the flag-threshold lines
3442 in directory authority votes to describe whether they have enough
3443 measured bandwidths to ignore advertised (relay descriptor)
3444 bandwidth claims. Resolves ticket 8711.
3445 - Update to the June 5 2013 Maxmind GeoLite Country database.
3447 o Removed documentation:
3448 - Remove some of the older contents of doc/ as obsolete; move others
3449 to torspec.git. Fixes bug 8965.
3451 o Code simplification and refactoring:
3452 - Avoid using character buffers when constructing most directory
3453 objects: this approach was unwieldy and error-prone. Instead,
3454 build smartlists of strings, and concatenate them when done.
3457 Changes in version 0.2.4.12-alpha - 2013-04-18
3458 Tor 0.2.4.12-alpha moves Tor forward on several fronts: it starts the
3459 process for lengthening the guard rotation period, makes directory
3460 authority opinions in the consensus a bit less gameable, makes socks5
3461 username/password circuit isolation actually work, and fixes a wide
3462 variety of other issues.
3465 - Raise the default time that a client keeps an entry guard from
3466 "1-2 months" to "2-3 months", as suggested by Tariq Elahi's WPES
3467 2012 paper. (We would make it even longer, but we need better client
3468 load balancing first.) Also, make the guard lifetime controllable
3469 via a new GuardLifetime torrc option and a GuardLifetime consensus
3470 parameter. Start of a fix for bug 8240; bugfix on 0.1.1.11-alpha.
3471 - Directory authorities now prefer using measured bandwidths to
3472 advertised ones when computing flags and thresholds. Resolves
3474 - Directory authorities that have more than a threshold number
3475 of relays with measured bandwidths now treat relays with unmeasured
3476 bandwidths as having bandwidth 0. Resolves ticket 8435.
3478 o Major bugfixes (assert / resource use):
3479 - Avoid a bug where our response to TLS renegotiation under certain
3480 network conditions could lead to a busy-loop, with 100% CPU
3481 consumption. Fixes bug 5650; bugfix on 0.2.0.16-alpha.
3482 - Avoid an assertion when we discover that we'd like to write a cell
3483 onto a closing connection: just discard the cell. Fixes another
3484 case of bug 7350; bugfix on 0.2.4.4-alpha.
3486 o Major bugfixes (client-side privacy):
3487 - When we mark a circuit as unusable for new circuits, have it
3488 continue to be unusable for new circuits even if MaxCircuitDirtiness
3489 is increased too much at the wrong time, or the system clock jumps
3490 backwards. Fixes bug 6174; bugfix on 0.0.2pre26.
3491 - If ClientDNSRejectInternalAddresses ("do not believe DNS queries
3492 which have resolved to internal addresses") is set, apply that
3493 rule to IPv6 as well. Fixes bug 8475; bugfix on 0.2.0.7-alpha.
3494 - When an exit relay rejects a stream with reason "exit policy", but
3495 we only know an exit policy summary (e.g. from the microdesc
3496 consensus) for it, do not mark the relay as useless for all exiting.
3497 Instead, mark just the circuit as unsuitable for that particular
3498 address. Fixes part of bug 7582; bugfix on 0.2.3.2-alpha.
3499 - Allow applications to get proper stream isolation with
3500 IsolateSOCKSAuth. Many SOCKS5 clients that want to offer
3501 username/password authentication also offer "no authentication". Tor
3502 had previously preferred "no authentication", so the applications
3503 never actually sent Tor their auth details. Now Tor selects
3504 username/password authentication if it's offered. You can disable
3505 this behavior on a per-SOCKSPort basis via PreferSOCKSNoAuth. Fixes
3506 bug 8117; bugfix on 0.2.3.3-alpha.
3508 o Major bugfixes (other):
3509 - When unable to find any working directory nodes to use as a
3510 directory guard, give up rather than adding the same non-working
3511 nodes to the directory guard list over and over. Fixes bug 8231;
3512 bugfix on 0.2.4.8-alpha.
3515 - Reject as invalid most directory objects containing a NUL.
3516 Belt-and-suspender fix for bug 8037.
3517 - In our testsuite, create temporary directories with a bit more
3518 entropy in their name to make name collisions less likely. Fixes
3520 - Add CACHED keyword to ADDRMAP events in the control protocol
3521 to indicate whether a DNS result will be cached or not. Resolves
3523 - Update to the April 3 2013 Maxmind GeoLite Country database.
3525 o Minor features (build):
3526 - Detect and reject attempts to build Tor with threading support
3527 when OpenSSL has been compiled without threading support.
3529 - Clarify that when autoconf is checking for nacl, it is checking
3530 specifically for nacl with a fast curve25519 implementation.
3532 - Warn if building on a platform with an unsigned time_t: there
3533 are too many places where Tor currently assumes that time_t can
3534 hold negative values. We'd like to fix them all, but probably
3537 o Minor bugfixes (build):
3538 - Fix some bugs in tor-fw-helper-natpmp when trying to build and
3539 run it on Windows. More bugs likely remain. Patch from Gisle Vanem.
3540 Fixes bug 7280; bugfix on 0.2.3.1-alpha.
3541 - Add the old src/or/micro-revision.i filename to CLEANFILES.
3542 On the off chance that somebody has one, it will go away as soon
3543 as they run "make clean". Fix for bug 7143; bugfix on 0.2.4.1-alpha.
3544 - Build Tor correctly on 32-bit platforms where the compiler can build
3545 but not run code using the "uint128_t" construction. Fixes bug 8587;
3546 bugfix on 0.2.4.8-alpha.
3547 - Fix compilation warning with some versions of clang that would
3548 prefer the -Wswitch-enum compiler flag to warn about switch
3549 statements with missing enum values, even if those switch
3550 statements have a "default:" statement. Fixes bug 8598; bugfix
3553 o Minor bugfixes (protocol):
3554 - Fix the handling of a TRUNCATE cell when it arrives while the
3555 circuit extension is in progress. Fixes bug 7947; bugfix on 0.0.7.1.
3556 - Fix a misframing issue when reading the version numbers in a
3557 VERSIONS cell. Previously we would recognize [00 01 00 02] as
3558 'version 1, version 2, and version 0x100', when it should have
3559 only included versions 1 and 2. Fixes bug 8059; bugfix on
3560 0.2.0.10-alpha. Reported pseudonymously.
3561 - Make the format and order of STREAM events for DNS lookups
3562 consistent among the various ways to launch DNS lookups. Fixes
3563 bug 8203; bugfix on 0.2.0.24-rc. Patch by "Desoxy."
3564 - Correct our check for which versions of Tor support the EXTEND2
3565 cell. We had been willing to send it to Tor 0.2.4.7-alpha and
3566 later, when support was really added in version 0.2.4.8-alpha.
3567 Fixes bug 8464; bugfix on 0.2.4.8-alpha.
3569 o Minor bugfixes (other):
3570 - Correctly store microdescriptors and extrainfo descriptors with
3571 an internal NUL byte. Fixes bug 8037; bugfix on 0.2.0.1-alpha.
3572 Bug reported by "cypherpunks".
3573 - Increase the width of the field used to remember a connection's
3574 link protocol version to two bytes. Harmless for now, since the
3575 only currently recognized versions are one byte long. Reported
3576 pseudonymously. Fixes bug 8062; bugfix on 0.2.0.10-alpha.
3577 - If the state file's path bias counts are invalid (presumably from a
3578 buggy Tor prior to 0.2.4.10-alpha), make them correct. Also add
3579 additional checks and log messages to the scaling of Path Bias
3580 counts, in case there still are remaining issues with scaling.
3581 Should help resolve bug 8235.
3582 - Eliminate several instances where we use "Nickname=ID" to refer to
3583 nodes in logs. Use "Nickname (ID)" instead. (Elsewhere, we still use
3584 "$ID=Nickname", which is also acceptable.) Fixes bug 7065. Bugfix
3585 on 0.2.3.21-rc, 0.2.4.5-alpha, 0.2.4.8-alpha, and 0.2.4.10-alpha.
3587 o Minor bugfixes (syscalls):
3588 - Always check the return values of functions fcntl() and
3589 setsockopt(). We don't believe these are ever actually failing in
3590 practice, but better safe than sorry. Also, checking these return
3591 values should please analysis tools like Coverity. Patch from
3592 'flupzor'. Fixes bug 8206; bugfix on all versions of Tor.
3593 - Use direct writes rather than stdio when building microdescriptor
3594 caches, in an attempt to mitigate bug 8031, or at least make it
3597 o Minor bugfixes (config):
3598 - When rejecting a configuration because we were unable to parse a
3599 quoted string, log an actual error message. Fixes bug 7950; bugfix
3601 - Behave correctly when the user disables LearnCircuitBuildTimeout
3602 but doesn't tell us what they would like the timeout to be. Fixes
3603 bug 6304; bugfix on 0.2.2.14-alpha.
3604 - When autodetecting the number of CPUs, use the number of available
3605 CPUs in preference to the number of configured CPUs. Inform the
3606 user if this reduces the number of available CPUs. Fixes bug 8002;
3607 bugfix on 0.2.3.1-alpha.
3608 - Make it an error when you set EntryNodes but disable UseGuardNodes,
3609 since it will (surprisingly to some users) ignore EntryNodes. Fixes
3610 bug 8180; bugfix on 0.2.3.11-alpha.
3611 - Allow TestingTorNetworks to override the 4096-byte minimum for
3612 the Fast threshold. Otherwise they can't bootstrap until they've
3613 observed more traffic. Fixes bug 8508; bugfix on 0.2.4.10-alpha.
3614 - Fix some logic errors when the user manually overrides the
3615 PathsNeededToBuildCircuits option in torrc. Fixes bug 8599; bugfix
3618 o Minor bugfixes (log messages to help diagnose bugs):
3619 - If we fail to free a microdescriptor because of bug 7164, log
3620 the filename and line number from which we tried to free it.
3621 - Add another diagnostic to the heartbeat message: track and log
3622 overhead that TLS is adding to the data we write. If this is
3623 high, we are sending too little data to SSL_write at a time.
3624 Diagnostic for bug 7707.
3625 - Add more detail to a log message about relaxed timeouts, to help
3627 - Warn more aggressively when flushing microdescriptors to a
3628 microdescriptor cache fails, in an attempt to mitigate bug 8031,
3629 or at least make it more diagnosable.
3630 - Improve debugging output to help track down bug 8185 ("Bug:
3631 outgoing relay cell has n_chan==NULL. Dropping.")
3632 - Log the purpose of a path-bias testing circuit correctly.
3633 Improves a log message from bug 8477; bugfix on 0.2.4.8-alpha.
3635 o Minor bugfixes (0.2.4.x log messages that were too noisy):
3636 - Don't attempt to relax the timeout of already opened 1-hop circuits.
3637 They might never timeout. This should eliminate some/all cases of
3638 the relaxed timeout log message.
3639 - Use circuit creation time for network liveness evaluation. This
3640 should eliminate warning log messages about liveness caused
3641 by changes in timeout evaluation. Fixes bug 6572; bugfix on
3643 - Reduce a path bias length check from notice to info. The message
3644 is triggered when creating controller circuits. Fixes bug 8196;
3645 bugfix on 0.2.4.8-alpha.
3646 - Fix a path state issue that triggered a notice during relay startup.
3647 Fixes bug 8320; bugfix on 0.2.4.10-alpha.
3648 - Reduce occurrences of warns about circuit purpose in
3649 connection_ap_expire_building(). Fixes bug 8477; bugfix on
3652 o Minor bugfixes (pre-0.2.4.x log messages that were too noisy):
3653 - If we encounter a write failure on a SOCKS connection before we
3654 finish our SOCKS handshake, don't warn that we closed the
3655 connection before we could send a SOCKS reply. Fixes bug 8427;
3656 bugfix on 0.1.0.1-rc.
3657 - Correctly recognize that [::1] is a loopback address. Fixes
3658 bug 8377; bugfix on 0.2.1.3-alpha.
3659 - Fix a directory authority warn caused when we have a large amount
3660 of badexit bandwidth. Fixes bug 8419; bugfix on 0.2.2.10-alpha.
3661 - Don't log inappropriate heartbeat messages when hibernating: a
3662 hibernating node is _expected_ to drop out of the consensus,
3663 decide it isn't bootstrapped, and so forth. Fixes bug 7302;
3664 bugfix on 0.2.3.1-alpha.
3665 - Don't complain about bootstrapping problems while hibernating.
3666 These complaints reflect a general code problem, but not one
3667 with any problematic effects (no connections are actually
3668 opened). Fixes part of bug 7302; bugfix on 0.2.3.2-alpha.
3670 o Documentation fixes:
3671 - Update tor-fw-helper.1.txt and tor-fw-helper.c to make option
3672 names match. Fixes bug 7768.
3673 - Make the torify manpage no longer refer to tsocks; torify hasn't
3674 supported tsocks since 0.2.3.14-alpha.
3675 - Make the tor manpage no longer reference tsocks.
3676 - Fix the GeoIPExcludeUnknown documentation to refer to
3677 ExcludeExitNodes rather than the currently nonexistent
3678 ExcludeEntryNodes. Spotted by "hamahangi" on tor-talk.
3681 - The tor-tsocks.conf is no longer distributed or installed. We
3682 recommend that tsocks users use torsocks instead. Resolves
3686 Changes in version 0.2.4.11-alpha - 2013-03-11
3687 Tor 0.2.4.11-alpha makes relay measurement by directory authorities
3688 more robust, makes hidden service authentication work again, and
3689 resolves a DPI fingerprint for Tor's SSL transport.
3691 o Major features (directory authorities):
3692 - Directory authorities now support a new consensus method (17)
3693 where they cap the published bandwidth of servers for which
3694 insufficient bandwidth measurements exist. Fixes part of bug 2286.
3695 - Directory authorities that set "DisableV2DirectoryInfo_ 1" no longer
3696 serve any v2 directory information. Now we can test disabling the
3697 old deprecated v2 directory format, and see whether doing so has
3698 any effect on network load. Begins to fix bug 6783.
3699 - Directory authorities now include inside each vote a statement of
3700 the performance thresholds they used when assigning flags.
3701 Implements ticket 8151.
3703 o Major bugfixes (directory authorities):
3704 - Stop marking every relay as having been down for one hour every
3705 time we restart a directory authority. These artificial downtimes
3706 were messing with our Stable and Guard flag calculations. Fixes
3707 bug 8218 (introduced by the fix for 1035). Bugfix on 0.2.2.23-alpha.
3709 o Major bugfixes (hidden services):
3710 - Allow hidden service authentication to succeed again. When we
3711 refactored the hidden service introduction code back
3712 in 0.2.4.1-alpha, we didn't update the code that checks
3713 whether authentication information is present, causing all
3714 authentication checks to return "false". Fix for bug 8207; bugfix
3715 on 0.2.4.1-alpha. Found by Coverity; this is CID 718615.
3717 o Minor features (relays, bridges):
3718 - Make bridge relays check once a minute for whether their IP
3719 address has changed, rather than only every 15 minutes. Resolves
3721 - Refactor resolve_my_address() so it returns the method by which we
3722 decided our public IP address (explicitly configured, resolved from
3723 explicit hostname, guessed from interfaces, learned by gethostname).
3724 Now we can provide more helpful log messages when a relay guesses
3725 its IP address incorrectly (e.g. due to unexpected lines in
3726 /etc/hosts). Resolves ticket 2267.
3727 - Teach bridge-using clients to avoid 0.2.2 bridges when making
3728 microdescriptor-related dir requests, and only fall back to normal
3729 descriptors if none of their bridges can handle microdescriptors
3730 (as opposed to the fix in ticket 4013, which caused them to fall
3731 back to normal descriptors if *any* of their bridges preferred
3732 them). Resolves ticket 4994.
3733 - Randomize the lifetime of our SSL link certificate, so censors can't
3734 use the static value for filtering Tor flows. Resolves ticket 8443;
3735 related to ticket 4014 which was included in 0.2.2.33.
3736 - Support a new version of the link protocol that allows 4-byte circuit
3737 IDs. Previously, circuit IDs were limited to 2 bytes, which presented
3738 a possible resource exhaustion issue. Closes ticket 7351; implements
3741 o Minor features (portability):
3742 - Tweak the curve25519-donna*.c implementations to tolerate systems
3743 that lack stdint.h. Fixes bug 3894; bugfix on 0.2.4.8-alpha.
3744 - Use Ville Laurikari's implementation of AX_CHECK_SIGN() to determine
3745 the signs of types during autoconf. This is better than our old
3746 approach, which didn't work when cross-compiling.
3747 - Detect the sign of enum values, rather than assuming that MSC is the
3748 only compiler where enum types are all signed. Fixes bug 7727;
3749 bugfix on 0.2.4.10-alpha.
3751 o Minor features (other):
3752 - Say "KBytes" rather than "KB" in the man page (for various values
3753 of K), to further reduce confusion about whether Tor counts in
3754 units of memory or fractions of units of memory. Resolves ticket 7054.
3755 - Clear the high bit on curve25519 public keys before passing them to
3756 our backend, in case we ever wind up using a backend that doesn't do
3757 so itself. If we used such a backend, and *didn't* clear the high bit,
3758 we could wind up in a situation where users with such backends would
3759 be distinguishable from users without. Fixes bug 8121; bugfix on
3761 - Update to the March 6 2013 Maxmind GeoLite Country database.
3763 o Minor bugfixes (clients):
3764 - When we receive a RELAY_END cell with the reason DONE, or with no
3765 reason, before receiving a RELAY_CONNECTED cell, report the SOCKS
3766 status as "connection refused". Previously we reported these cases
3767 as success but then immediately closed the connection. Fixes bug
3768 7902; bugfix on 0.1.0.1-rc. Reported by "oftc_must_be_destroyed".
3769 - Downgrade an assertion in connection_ap_expire_beginning to an
3770 LD_BUG message. The fix for bug 8024 should prevent this message
3771 from displaying, but just in case, a warn that we can diagnose
3772 is better than more assert crashes. Fixes bug 8065; bugfix on
3774 - Lower path use bias thresholds to .80 for notice and .60 for warn.
3775 Also make the rate limiting flags for the path use bias log messages
3776 independent from the original path bias flags. Fixes bug 8161;
3777 bugfix on 0.2.4.10-alpha.
3779 o Minor bugfixes (relays):
3780 - Stop trying to resolve our hostname so often (e.g. every time we
3781 think about doing a directory fetch). Now we reuse the cached
3782 answer in some cases. Fixes bugs 1992 (bugfix on 0.2.0.20-rc)
3783 and 2410 (bugfix on 0.1.2.2-alpha).
3784 - Stop sending a stray "(null)" in some cases for the server status
3785 "EXTERNAL_ADDRESS" controller event. Resolves bug 8200; bugfix
3787 - When choosing which stream on a formerly stalled circuit to wake
3788 first, make better use of the platform's weak RNG. Previously,
3789 we had been using the % ("modulo") operator to try to generate a
3790 1/N chance of picking each stream, but this behaves badly with
3791 many platforms' choice of weak RNG. Fixes bug 7801; bugfix on
3793 - Use our own weak RNG when we need a weak RNG. Windows's rand() and
3794 Irix's random() only return 15 bits; Solaris's random() returns more
3795 bits but its RAND_MAX says it only returns 15, and so on. Motivated
3796 by the fix for bug 7801; bugfix on 0.2.2.20-alpha.
3798 o Minor bugfixes (directory authorities):
3799 - Directory authorities now use less space when formatting identical
3800 microdescriptor lines in directory votes. Fixes bug 8158; bugfix
3803 o Minor bugfixes (memory leaks spotted by Coverity -- bug 7816):
3804 - Avoid leaking memory if we fail to compute a consensus signature
3805 or we generate a consensus we can't parse. Bugfix on 0.2.0.5-alpha.
3806 - Fix a memory leak when receiving headers from an HTTPS proxy. Bugfix
3808 - Fix a memory leak during safe-cookie controller authentication.
3809 Bugfix on 0.2.3.13-alpha.
3810 - Avoid memory leak of IPv6 policy content if we fail to format it into
3811 a router descriptor. Bugfix on 0.2.4.7-alpha.
3813 o Minor bugfixes (other code correctness issues):
3814 - Avoid a crash if we fail to generate an extrainfo descriptor.
3815 Fixes bug 8208; bugfix on 0.2.3.16-alpha. Found by Coverity;
3817 - When detecting the largest possible file descriptor (in order to
3818 close all file descriptors when launching a new program), actually
3819 use _SC_OPEN_MAX. The old code for doing this was very, very broken.
3820 Fixes bug 8209; bugfix on 0.2.3.1-alpha. Found by Coverity; this
3822 - Fix a copy-and-paste error when adding a missing A1 to a routerset
3823 because of GeoIPExcludeUnknown. Fix for Coverity CID 980650.
3824 Bugfix on 0.2.4.10-alpha.
3825 - Fix an impossible-to-trigger integer overflow when estimating how
3826 long our onionskin queue would take. (This overflow would require us
3827 to accept 4 million onionskins before processing 100 of them.) Fixes
3828 bug 8210; bugfix on 0.2.4.10-alpha.
3830 o Code simplification and refactoring:
3831 - Add a wrapper function for the common "log a message with a
3835 Changes in version 0.2.4.10-alpha - 2013-02-04
3836 Tor 0.2.4.10-alpha adds defenses at the directory authority level from
3837 certain attacks that flood the network with relays; changes the queue
3838 for circuit create requests from a sized-based limit to a time-based
3839 limit; resumes building with MSVC on Windows; and fixes a wide variety
3842 o Major bugfixes (directory authority):
3843 - When computing directory thresholds, ignore any rejected-as-sybil
3844 nodes during the computation so that they can't influence Fast,
3845 Guard, etc. (We should have done this for proposal 109.) Fixes
3847 - When marking a node as a likely sybil, reset its uptime metrics
3848 to zero, so that it cannot time towards getting marked as Guard,
3849 Stable, or HSDir. (We should have done this for proposal 109.) Fixes
3853 - When a TLS write is partially successful but incomplete, remember
3854 that the flushed part has been flushed, and notice that bytes were
3855 actually written. Reported and fixed pseudonymously. Fixes bug
3856 7708; bugfix on Tor 0.1.0.5-rc.
3857 - Reject bogus create and relay cells with 0 circuit ID or 0 stream
3858 ID: these could be used to create unexpected streams and circuits
3859 which would count as "present" to some parts of Tor but "absent"
3860 to others, leading to zombie circuits and streams or to a bandwidth
3861 denial-of-service. Fixes bug 7889; bugfix on every released version
3862 of Tor. Reported by "oftc_must_be_destroyed".
3863 - Rename all macros in our local copy of queue.h to begin with "TOR_".
3864 This change seems the only good way to permanently prevent conflicts
3865 with queue.h on various operating systems. Fixes bug 8107; bugfix
3868 o Major features (relay):
3869 - Instead of limiting the number of queued onionskins (aka circuit
3870 create requests) to a fixed, hard-to-configure number, we limit
3871 the size of the queue based on how many we expect to be able to
3872 process in a given amount of time. We estimate the time it will
3873 take to process an onionskin based on average processing time
3874 of previous onionskins. Closes ticket 7291. You'll never have to
3875 configure MaxOnionsPending again.
3877 o Major features (portability):
3878 - Resume building correctly with MSVC and Makefile.nmake. This patch
3879 resolves numerous bugs and fixes reported by ultramage, including
3880 7305, 7308, 7309, 7310, 7312, 7313, 7315, 7316, and 7669.
3881 - Make the ntor and curve25519 code build correctly with MSVC.
3882 Fix on 0.2.4.8-alpha.
3885 - When directory authorities are computing thresholds for flags,
3886 never let the threshold for the Fast flag fall below 4096
3887 bytes. Also, do not consider nodes with extremely low bandwidths
3888 when deciding thresholds for various directory flags. This change
3889 should raise our threshold for Fast relays, possibly in turn
3890 improving overall network performance; see ticket 1854. Resolves
3892 - The Tor client now ignores sub-domain components of a .onion
3893 address. This change makes HTTP "virtual" hosting
3894 possible: http://foo.aaaaaaaaaaaaaaaa.onion/ and
3895 http://bar.aaaaaaaaaaaaaaaa.onion/ can be two different websites
3896 hosted on the same hidden service. Implements proposal 204.
3897 - We compute the overhead from passing onionskins back and forth to
3898 cpuworkers, and report it when dumping statistics in response to
3899 SIGUSR1. Supports ticket 7291.
3901 o Minor features (path selection):
3902 - When deciding whether we have enough descriptors to build circuits,
3903 instead of looking at raw relay counts, look at which fraction
3904 of (bandwidth-weighted) paths we're able to build. This approach
3905 keeps clients from building circuits if their paths are likely to
3906 stand out statistically. The default fraction of paths needed is
3907 taken from the consensus directory; you can override it with the
3908 new PathsNeededToBuildCircuits option. Fixes ticket 5956.
3909 - When any country code is listed in ExcludeNodes or ExcludeExitNodes,
3910 and we have GeoIP information, also exclude all nodes with unknown
3911 countries "??" and "A1". This behavior is controlled by the
3912 new GeoIPExcludeUnknown option: you can make such nodes always
3913 excluded with "GeoIPExcludeUnknown 1", and disable the feature
3914 with "GeoIPExcludeUnknown 0". Setting "GeoIPExcludeUnknown auto"
3915 gets you the default behavior. Implements feature 7706.
3916 - Path Use Bias: Perform separate accounting for successful circuit
3917 use. Keep separate statistics on stream attempt rates versus stream
3918 success rates for each guard. Provide configurable thresholds to
3919 determine when to emit log messages or disable use of guards that
3920 fail too many stream attempts. Resolves ticket 7802.
3922 o Minor features (log messages):
3923 - When learning a fingerprint for a bridge, log its corresponding
3924 transport type. Implements ticket 7896.
3925 - Improve the log message when "Bug/attack: unexpected sendme cell
3926 from client" occurs, to help us track bug 8093.
3929 - Remove a couple of extraneous semicolons that were upsetting the
3930 cparser library. Patch by Christian Grothoff. Fixes bug 7115;
3931 bugfix on 0.2.2.1-alpha.
3932 - Remove a source of rounding error during path bias count scaling;
3933 don't count cannibalized circuits as used for path bias until we
3934 actually try to use them; and fix a circuit_package_relay_cell()
3935 warning message about n_chan==NULL. Fixes bug 7802.
3936 - Detect nacl when its headers are in a nacl/ subdirectory. Also,
3937 actually link against nacl when we're configured to use it. Fixes
3938 bug 7972; bugfix on 0.2.4.8-alpha.
3939 - Compile correctly with the --disable-curve25519 option. Fixes
3940 bug 8153; bugfix on 0.2.4.8-alpha.
3942 o Build improvements:
3943 - Do not report status verbosely from autogen.sh unless the -v flag
3944 is specified. Fixes issue 4664. Patch from Onizuka.
3945 - Replace all calls to snprintf() outside of src/ext with
3946 tor_snprintf(). Also remove the #define to replace snprintf with
3947 _snprintf on Windows; they have different semantics, and all of
3948 our callers should be using tor_snprintf() anyway. Fixes bug 7304.
3949 - Try to detect if we are ever building on a platform where
3950 memset(...,0,...) does not set the value of a double to 0.0. Such
3951 platforms are permitted by the C standard, though in practice
3952 they're pretty rare (since IEEE 754 is nigh-ubiquitous). We don't
3953 currently support them, but it's better to detect them and fail
3954 than to perform erroneously.
3957 - Stop exporting estimates of v2 and v3 directory traffic shares
3958 in extrainfo documents. They were unneeded and sometimes inaccurate.
3959 Also stop exporting any v2 directory request statistics. Resolves
3961 - Drop support for detecting and warning about versions of Libevent
3962 before 1.3e. Nothing reasonable ships with them any longer;
3963 warning the user about them shouldn't be needed. Resolves ticket
3966 o Code simplifications and refactoring:
3967 - Rename "isin" functions to "contains", for grammar. Resolves
3969 - Rename Tor's logging function log() to tor_log(), to avoid conflicts
3970 with the natural logarithm function from the system libm. Resolves
3974 Changes in version 0.2.4.9-alpha - 2013-01-15
3975 Tor 0.2.4.9-alpha provides a quick fix to make the new ntor handshake
3979 - Fix backward compatibility logic when receiving an embedded ntor
3980 handshake tunneled in a CREATE cell. This clears up the "Bug:
3981 couldn't format CREATED cell" warning. Fixes bug 7959; bugfix
3985 Changes in version 0.2.4.8-alpha - 2013-01-14
3986 Tor 0.2.4.8-alpha introduces directory guards to reduce user enumeration
3987 risks, adds a new stronger and faster circuit handshake, and offers
3988 stronger and faster link encryption when both sides support it.
3991 - Preliminary support for directory guards (proposal 207): when
3992 possible, clients now use their entry guards for non-anonymous
3993 directory requests. This can help prevent client enumeration. Note
3994 that this behavior only works when we have a usable consensus
3995 directory, and when options about what to download are more or less
3996 standard. In the future we should re-bootstrap from our guards,
3997 rather than re-bootstrapping from the preconfigured list of
3998 directory sources that ships with Tor. Resolves ticket 6526.
3999 - Tor relays and clients now support a better CREATE/EXTEND cell
4000 format, allowing the sender to specify multiple address, identity,
4001 and handshake types. Implements Robert Ransom's proposal 200;
4004 o Major features (new circuit handshake):
4005 - Tor now supports a new circuit extension handshake designed by Ian
4006 Goldberg, Douglas Stebila, and Berkant Ustaoglu. Our original
4007 circuit extension handshake, later called "TAP", was a bit slow
4008 (especially on the relay side), had a fragile security proof, and
4009 used weaker keys than we'd now prefer. The new circuit handshake
4010 uses Dan Bernstein's "curve25519" elliptic-curve Diffie-Hellman
4011 function, making it significantly more secure than the older
4012 handshake, and significantly faster. Tor can use one of two built-in
4013 pure-C curve25519-donna implementations by Adam Langley, or it
4014 can link against the "nacl" library for a tuned version if present.
4016 The built-in version is very fast for 64-bit systems when building
4017 with GCC. The built-in 32-bit version is still faster than the
4018 old TAP protocol, but using libnacl is better on most such hosts.
4020 Clients don't currently use this protocol by default, since
4021 comparatively few clients support it so far. To try it, set
4022 UseNTorHandshake to 1.
4024 Implements proposal 216; closes ticket 7202.
4026 o Major features (better link encryption):
4027 - Relays can now enable the ECDHE TLS ciphersuites when available
4028 and appropriate. These ciphersuites let us negotiate forward-secure
4029 TLS secret keys more safely and more efficiently than with our
4030 previous use of Diffie-Hellman modulo a 1024-bit prime. By default,
4031 public relays prefer the (faster) P224 group, and bridges prefer
4032 the (more common) P256 group; you can override this with the
4035 Enabling these ciphers was a little tricky, since for a long time,
4036 clients had been claiming to support them without actually doing
4037 so, in order to foil fingerprinting. But with the client-side
4038 implementation of proposal 198 in 0.2.3.17-beta, clients can now
4039 match the ciphers from recent Firefox versions *and* list the
4040 ciphers they actually mean, so relays can believe such clients
4041 when they advertise ECDHE support in their TLS ClientHello messages.
4043 This feature requires clients running 0.2.3.17-beta or later,
4044 and requires both sides to be running OpenSSL 1.0.0 or later
4045 with ECC support. OpenSSL 1.0.1, with the compile-time option
4046 "enable-ec_nistp_64_gcc_128", is highly recommended.
4048 Implements the relay side of proposal 198; closes ticket 7200.
4051 - Avoid crashing when, as a relay without IPv6-exit support, a
4052 client insists on getting an IPv6 address or nothing. Fixes bug
4053 7814; bugfix on 0.2.4.7-alpha.
4056 - Improve circuit build timeout handling for hidden services.
4057 In particular: adjust build timeouts more accurately depending
4058 upon the number of hop-RTTs that a particular circuit type
4059 undergoes. Additionally, launch intro circuits in parallel
4060 if they timeout, and take the first one to reply as valid.
4061 - Work correctly on Unix systems where EAGAIN and EWOULDBLOCK are
4062 separate error codes; or at least, don't break for that reason.
4063 Fixes bug 7935. Reported by "oftc_must_be_destroyed".
4064 - Update to the January 2 2013 Maxmind GeoLite Country database.
4066 o Minor features (testing):
4067 - Add benchmarks for DH (1024-bit multiplicative group) and ECDH
4068 (P-256) Diffie-Hellman handshakes to src/or/bench.
4069 - Add benchmark functions to test onion handshake performance.
4071 o Minor features (path bias detection):
4072 - Alter the Path Bias log messages to be more descriptive in terms
4073 of reporting timeouts and other statistics.
4074 - Create three levels of Path Bias log messages, as opposed to just
4075 two. These are configurable via consensus as well as via the torrc
4076 options PathBiasNoticeRate, PathBiasWarnRate, PathBiasExtremeRate.
4077 The default values are 0.70, 0.50, and 0.30 respectively.
4078 - Separate the log message levels from the decision to drop guards,
4079 which also is available via torrc option PathBiasDropGuards.
4080 PathBiasDropGuards still defaults to 0 (off).
4081 - Deprecate PathBiasDisableRate in favor of PathBiasDropGuards
4082 in combination with PathBiasExtremeRate.
4083 - Increase the default values for PathBiasScaleThreshold and
4084 PathBiasCircThreshold from (200, 20) to (300, 150).
4085 - Add in circuit usage accounting to path bias. If we try to use a
4086 built circuit but fail for any reason, it counts as path bias.
4087 Certain classes of circuits where the adversary gets to pick your
4088 destination node are exempt from this accounting. Usage accounting
4089 can be specifically disabled via consensus parameter or torrc.
4090 - Convert all internal path bias state to double-precision floating
4091 point, to avoid roundoff error and other issues.
4092 - Only record path bias information for circuits that have completed
4093 *two* hops. Assuming end-to-end tagging is the attack vector, this
4094 makes us more resilient to ambient circuit failure without any
4095 detection capability loss.
4097 o Minor bugfixes (log messages):
4098 - Rate-limit the "No circuits are opened. Relaxed timeout for a
4099 circuit with channel state open..." message to once per hour to
4100 keep it from filling the notice logs. Mitigates bug 7799 but does
4101 not fix the underlying cause. Bugfix on 0.2.4.7-alpha.
4102 - Avoid spurious warnings when configuring multiple client ports of
4103 which only some are nonlocal. Previously, we had claimed that some
4104 were nonlocal when in fact they weren't. Fixes bug 7836; bugfix on
4107 o Code simplifications and refactoring:
4108 - Get rid of a couple of harmless clang warnings, where we compared
4109 enums to ints. These warnings are newly introduced in clang 3.2.
4110 - Split the onion.c file into separate modules for the onion queue
4111 and the different handshakes it supports.
4112 - Remove the marshalling/unmarshalling code for sending requests to
4113 cpuworkers over a socket, and instead just send structs. The
4114 recipient will always be the same Tor binary as the sender, so
4115 any encoding is overkill.
4118 Changes in version 0.2.4.7-alpha - 2012-12-24
4119 Tor 0.2.4.7-alpha introduces a new approach to providing fallback
4120 directory mirrors for more robust bootstrapping; fixes more issues where
4121 clients with changing network conditions refuse to make any circuits;
4122 adds initial support for exiting to IPv6 addresses; resumes being able
4123 to update our GeoIP database, and includes the geoip6 file this time;
4124 turns off the client-side DNS cache by default due to privacy risks;
4125 and fixes a variety of other issues.
4127 o Major features (client resilience):
4128 - Add a new "FallbackDir" torrc option to use when we can't use
4129 a directory mirror from the consensus (either because we lack a
4130 consensus, or because they're all down). Currently, all authorities
4131 are fallbacks by default, and there are no other default fallbacks,
4132 but that will change. This option will allow us to give clients a
4133 longer list of servers to try to get a consensus from when first
4134 connecting to the Tor network, and thereby reduce load on the
4135 directory authorities. Implements proposal 206, "Preconfigured
4136 directory sources for bootstrapping". We also removed the old
4137 "FallbackNetworkstatus" option, since we never got it working well
4138 enough to use it. Closes bug 572.
4139 - If we have no circuits open, use a relaxed timeout (the
4140 95-percentile cutoff) until a circuit succeeds. This heuristic
4141 should allow Tor to succeed at building circuits even when the
4142 network connection drastically changes. Should help with bug 3443.
4144 o Major features (IPv6):
4145 - Relays can now exit to IPv6 addresses: make sure that you have IPv6
4146 connectivity, then set the IPv6Exit flag to 1. Also make sure your
4147 exit policy reads as you would like: the address * applies to all
4148 address families, whereas *4 is IPv4 address only, and *6 is IPv6
4149 addresses only. On the client side, you'll need to wait until the
4150 authorities have upgraded, wait for enough exits to support IPv6,
4151 apply the "IPv6Traffic" flag to a SocksPort, and use Socks5. Closes
4152 ticket 5547, implements proposal 117 as revised in proposal 208.
4154 We DO NOT recommend that clients with actual anonymity needs start
4155 using IPv6 over Tor yet, since not enough exits support it yet.
4157 o Major features (geoip database):
4158 - Maxmind began labelling Tor relays as being in country "A1",
4159 which breaks by-country node selection inside Tor. Now we use a
4160 script to replace "A1" ("Anonymous Proxy") entries in our geoip
4161 file with real country codes. This script fixes about 90% of "A1"
4162 entries automatically and uses manual country code assignments to
4163 fix the remaining 10%. See src/config/README.geoip for details.
4164 Fixes bug 6266. Also update to the December 5 2012 Maxmind GeoLite
4165 Country database, as modified above.
4167 o Major bugfixes (client-side DNS):
4168 - Turn off the client-side DNS cache by default. Updating and using
4169 the DNS cache is now configurable on a per-client-port
4170 level. SOCKSPort, DNSPort, etc lines may now contain
4171 {No,}Cache{IPv4,IPv6,}DNS lines to indicate that we shouldn't
4172 cache these types of DNS answers when we receive them from an
4173 exit node in response to an application request on this port, and
4174 {No,}UseCached{IPv4,IPv6,DNS} lines to indicate that if we have
4175 cached DNS answers of these types, we shouldn't use them. It's
4176 potentially risky to use cached DNS answers at the client, since
4177 doing so can indicate to one exit what answers we've gotten
4178 for DNS lookups in the past. With IPv6, this becomes especially
4179 problematic. Using cached DNS answers for requests on the same
4180 circuit would present less linkability risk, since all traffic
4181 on a circuit is already linkable, but it would also provide
4182 little performance benefit: the exit node caches DNS replies
4183 too. Implements a simplified version of Proposal 205. Implements
4186 o Major bugfixes (other):
4187 - Alter circuit build timeout measurement to start at the point
4188 where we begin the CREATE/CREATE_FAST step (as opposed to circuit
4189 initialization). This should make our timeout measurements more
4190 uniform. Previously, we were sometimes including ORconn setup time
4191 in our circuit build time measurements. Should resolve bug 3443.
4192 - Fix an assertion that could trigger in hibernate_go_dormant() when
4193 closing an or_connection_t: call channel_mark_for_close() rather
4194 than connection_mark_for_close(). Fixes bug 7267. Bugfix on
4196 - Include the geoip6 IPv6 GeoIP database in the tarball. Fixes bug
4197 7655; bugfix on 0.2.4.6-alpha.
4200 - Add a new torrc option "ServerTransportListenAddr" to let bridge
4201 operators select the address where their pluggable transports will
4202 listen for connections. Resolves ticket 7013.
4203 - Allow an optional $ before the node identity digest in the
4204 controller command GETINFO ns/id/<identity>, for consistency with
4205 md/id/<identity> and desc/id/<identity>. Resolves ticket 7059.
4206 - Log packaged cell fullness as part of the heartbeat message.
4207 Diagnosis to try to determine the extent of bug 7743.
4209 o Minor features (IPv6):
4210 - AutomapHostsOnResolve now supports IPv6 addresses. By default, we
4211 prefer to hand out virtual IPv6 addresses, since there are more of
4212 them and we can't run out. To override this behavior and make IPv4
4213 addresses preferred, set NoPreferIPv6Automap on whatever SOCKSPort
4214 or DNSPort you're using for resolving. Implements ticket 7571.
4215 - AutomapHostsOnResolve responses are now randomized, to avoid
4216 annoying situations where Tor is restarted and applications
4217 connect to the wrong addresses.
4218 - Never try more than 1000 times to pick a new virtual address when
4219 AutomapHostsOnResolve is set. That's good enough so long as we
4220 aren't close to handing out our entire virtual address space;
4221 if you're getting there, it's best to switch to IPv6 virtual
4225 - The ADDRMAP command can no longer generate an ill-formed error
4226 code on a failed MAPADDRESS. It now says "internal" rather than
4227 an English sentence fragment with spaces in the middle. Bugfix on
4229 - Fix log messages and comments to avoid saying "GMT" when we mean
4230 "UTC". Fixes bug 6113.
4231 - Compile on win64 using mingw64. Fixes bug 7260; patches from
4233 - Fix a crash when debugging unit tests on Windows: deallocate a
4234 shared library with FreeLibrary, not CloseHandle. Fixes bug 7306;
4235 bugfix on 0.2.2.17-alpha. Reported by "ultramage".
4238 - The DirServer option is now DirAuthority, for consistency with
4239 current naming patterns. You can still use the old DirServer form.
4241 o Code simplification and refactoring:
4242 - Move the client-side address-map/virtual-address/DNS-cache code
4243 out of connection_edge.c into a new addressmap.c module.
4244 - Remove unused code for parsing v1 directories and "running routers"
4245 documents. Fixes bug 6887.
4248 Changes in version 0.2.3.25 - 2012-11-19
4249 The Tor 0.2.3 release series is dedicated to the memory of Len "rabbi"
4250 Sassaman (1980-2011), a long-time cypherpunk, anonymity researcher,
4251 Mixmaster maintainer, Pynchon Gate co-designer, CodeCon organizer,
4252 programmer, and friend. Unstinting in his dedication to the cause of
4253 freedom, he inspired and helped many of us as we began our work on
4254 anonymity, and inspires us still. Please honor his memory by writing
4255 software to protect people's freedoms, and by helping others to do so.
4257 Tor 0.2.3.25, the first stable release in the 0.2.3 branch, features
4258 significantly reduced directory overhead (via microdescriptors),
4259 enormous crypto performance improvements for fast relays on new
4260 enough hardware, a new v3 TLS handshake protocol that can better
4261 resist fingerprinting, support for protocol obfuscation plugins (aka
4262 pluggable transports), better scalability for hidden services, IPv6
4263 support for bridges, performance improvements like allowing clients
4264 to skip the first round-trip on the circuit ("optimistic data") and
4265 refilling token buckets more often, a new "stream isolation" design
4266 to isolate different applications on different circuits, and many
4267 stability, security, and privacy fixes.
4270 - Tor tries to wipe potentially sensitive data after using it, so
4271 that if some subsequent security failure exposes Tor's memory,
4272 the damage will be limited. But we had a bug where the compiler
4273 was eliminating these wipe operations when it decided that the
4274 memory was no longer visible to a (correctly running) program,
4275 hence defeating our attempt at defense in depth. We fix that
4276 by using OpenSSL's OPENSSL_cleanse() operation, which a compiler
4277 is unlikely to optimize away. Future versions of Tor may use
4278 a less ridiculously heavy approach for this. Fixes bug 7352.
4279 Reported in an article by Andrey Karpov.
4282 - Fix a harmless bug when opting against publishing a relay descriptor
4283 because DisableNetwork is set. Fixes bug 7464; bugfix on
4287 Changes in version 0.2.4.6-alpha - 2012-11-13
4288 Tor 0.2.4.6-alpha fixes an assert bug that has been plaguing relays,
4289 makes our defense-in-depth memory wiping more reliable, and begins to
4290 count IPv6 addresses in bridge statistics,
4293 - Fix an assertion failure that could occur when closing a connection
4294 with a spliced rendezvous circuit. Fix for bug 7212; bugfix on
4296 - Tor tries to wipe potentially sensitive data after using it, so
4297 that if some subsequent security failure exposes Tor's memory,
4298 the damage will be limited. But we had a bug where the compiler
4299 was eliminating these wipe operations when it decided that the
4300 memory was no longer visible to a (correctly running) program,
4301 hence defeating our attempt at defense in depth. We fix that
4302 by using OpenSSL's OPENSSL_cleanse() operation, which a compiler
4303 is unlikely to optimize away. Future versions of Tor may use
4304 a less ridiculously heavy approach for this. Fixes bug 7352.
4305 Reported in an article by Andrey Karpov.
4308 - Add GeoIP database for IPv6 addresses. The new config option
4310 - Bridge statistics now count bridge clients connecting over IPv6:
4311 bridge statistics files now list "bridge-ip-versions" and
4312 extra-info documents list "geoip6-db-digest". The control protocol
4313 "CLIENTS_SEEN" and "ip-to-country" queries now support IPv6. Initial
4314 implementation by "shkoo", addressing ticket 5055.
4317 - Warn when we are binding low ports when hibernation is enabled;
4318 previously we had warned when we were _advertising_ low ports with
4319 hibernation enabled. Fixes bug 7285; bugfix on 0.2.3.9-alpha.
4320 - Fix a harmless bug when opting against publishing a relay descriptor
4321 because DisableNetwork is set. Fixes bug 7464; bugfix on
4323 - Add warning message when a managed proxy dies during configuration.
4324 Fixes bug 7195; bugfix on 0.2.4.2-alpha.
4325 - Fix a linking error when building tor-fw-helper without miniupnp.
4326 Fixes bug 7235; bugfix on 0.2.4.2-alpha. Fix by Anthony G. Basile.
4327 - Check for closing an or_connection_t without going through correct
4328 channel functions; emit a warning and then call
4329 connection_or_close_for_error() so we don't assert as in bugs 7212
4331 - Compile correctly on compilers without C99 designated initializer
4332 support. Fixes bug 7286; bugfix on 0.2.4.4-alpha.
4333 - Avoid a possible assert that can occur when channel_send_destroy() is
4334 called on a channel in CHANNEL_STATE_CLOSING, CHANNEL_STATE_CLOSED,
4335 or CHANNEL_STATE_ERROR when the Tor process is resumed after being
4336 blocked for a long interval. Fixes bug 7350; bugfix on 0.2.4.4-alpha.
4337 - Fix a memory leak on failing cases of channel_tls_process_certs_cell.
4338 Fixes bug 7422; bugfix on 0.2.4.4-alpha.
4340 o Code simplification and refactoring:
4341 - Start using OpenBSD's implementation of queue.h, so that we don't
4342 need to hand-roll our own pointer and list structures whenever we
4343 need them. (We can't rely on a sys/queue.h, since some operating
4344 systems don't have them, and the ones that do have them don't all
4345 present the same extensions.)
4348 Changes in version 0.2.4.5-alpha - 2012-10-25
4349 Tor 0.2.4.5-alpha comes hard at the heels of 0.2.4.4-alpha, to fix
4350 two important security vulnerabilities that could lead to remotely
4351 triggerable relay crashes, fix a major bug that was preventing clients
4352 from choosing suitable exit nodes, and refactor some of our code.
4354 o Major bugfixes (security, also in 0.2.3.24-rc):
4355 - Fix a group of remotely triggerable assertion failures related to
4356 incorrect link protocol negotiation. Found, diagnosed, and fixed
4357 by "some guy from France". Fix for CVE-2012-2250; bugfix on
4359 - Fix a denial of service attack by which any directory authority
4360 could crash all the others, or by which a single v2 directory
4361 authority could crash everybody downloading v2 directory
4362 information. Fixes bug 7191; bugfix on 0.2.0.10-alpha.
4364 o Major bugfixes (also in 0.2.3.24-rc):
4365 - When parsing exit policy summaries from microdescriptors, we had
4366 previously been ignoring the last character in each one, so that
4367 "accept 80,443,8080" would be treated by clients as indicating
4368 a node that allows access to ports 80, 443, and 808. That would
4369 lead to clients attempting connections that could never work,
4370 and ignoring exit nodes that would support their connections. Now
4371 clients parse these exit policy summaries correctly. Fixes bug 7192;
4372 bugfix on 0.2.3.1-alpha.
4374 o Minor bugfixes (also in 0.2.3.24-rc):
4375 - Clients now consider the ClientRejectInternalAddresses config option
4376 when using a microdescriptor consensus stanza to decide whether
4377 an exit relay would allow exiting to an internal address. Fixes
4378 bug 7190; bugfix on 0.2.3.1-alpha.
4381 - Only disable TLS session ticket support when running as a TLS
4382 server. Now clients will blend better with regular Firefox
4383 connections. Fixes bug 7189; bugfix on Tor 0.2.3.23-rc.
4385 o Code simplification and refactoring:
4386 - Start using OpenBSD's implementation of queue.h (originally by
4388 - Move the entry node code from circuitbuild.c to its own file.
4389 - Move the circuit build timeout tracking code from circuitbuild.c
4393 Changes in version 0.2.3.24-rc - 2012-10-25
4394 Tor 0.2.3.24-rc fixes two important security vulnerabilities that
4395 could lead to remotely triggerable relay crashes, and fixes
4396 a major bug that was preventing clients from choosing suitable exit
4399 o Major bugfixes (security):
4400 - Fix a group of remotely triggerable assertion failures related to
4401 incorrect link protocol negotiation. Found, diagnosed, and fixed
4402 by "some guy from France". Fix for CVE-2012-2250; bugfix on
4404 - Fix a denial of service attack by which any directory authority
4405 could crash all the others, or by which a single v2 directory
4406 authority could crash everybody downloading v2 directory
4407 information. Fixes bug 7191; bugfix on 0.2.0.10-alpha.
4410 - When parsing exit policy summaries from microdescriptors, we had
4411 previously been ignoring the last character in each one, so that
4412 "accept 80,443,8080" would be treated by clients as indicating
4413 a node that allows access to ports 80, 443, and 808. That would
4414 lead to clients attempting connections that could never work,
4415 and ignoring exit nodes that would support their connections. Now
4416 clients parse these exit policy summaries correctly. Fixes bug 7192;
4417 bugfix on 0.2.3.1-alpha.
4420 - Clients now consider the ClientRejectInternalAddresses config option
4421 when using a microdescriptor consensus stanza to decide whether
4422 an exit relay would allow exiting to an internal address. Fixes
4423 bug 7190; bugfix on 0.2.3.1-alpha.
4426 Changes in version 0.2.4.4-alpha - 2012-10-20
4427 Tor 0.2.4.4-alpha adds a new v3 directory authority, fixes a privacy
4428 vulnerability introduced by a change in OpenSSL, fixes a remotely
4429 triggerable assert, and adds new channel_t and circuitmux_t abstractions
4430 that will make it easier to test new connection transport and cell
4431 scheduling algorithms.
4433 o New directory authorities (also in 0.2.3.23-rc):
4434 - Add Faravahar (run by Sina Rabbani) as the ninth v3 directory
4435 authority. Closes ticket 5749.
4437 o Major bugfixes (security/privacy, also in 0.2.3.23-rc):
4438 - Disable TLS session tickets. OpenSSL's implementation was giving
4439 our TLS session keys the lifetime of our TLS context objects, when
4440 perfect forward secrecy would want us to discard anything that
4441 could decrypt a link connection as soon as the link connection
4442 was closed. Fixes bug 7139; bugfix on all versions of Tor linked
4443 against OpenSSL 1.0.0 or later. Found by Florent Daignière.
4444 - Discard extraneous renegotiation attempts once the V3 link
4445 protocol has been initiated. Failure to do so left us open to
4446 a remotely triggerable assertion failure. Fixes CVE-2012-2249;
4447 bugfix on 0.2.3.6-alpha. Reported by "some guy from France".
4449 o Internal abstraction features:
4450 - Introduce new channel_t abstraction between circuits and
4451 or_connection_t to allow for implementing alternate OR-to-OR
4452 transports. A channel_t is an abstract object which can either be a
4453 cell-bearing channel, which is responsible for authenticating and
4454 handshaking with the remote OR and transmitting cells to and from
4455 it, or a listening channel, which spawns new cell-bearing channels
4456 at the request of remote ORs. Implements part of ticket 6465.
4457 - Also new is the channel_tls_t subclass of channel_t, adapting it
4458 to the existing or_connection_t code. The V2/V3 protocol handshaking
4459 code which formerly resided in command.c has been moved below the
4460 channel_t abstraction layer and may be found in channeltls.c now.
4461 Implements the rest of ticket 6465.
4462 - Introduce new circuitmux_t storing the queue of circuits for
4463 a channel; this encapsulates and abstracts the queue logic and
4464 circuit selection policy, and allows the latter to be overridden
4465 easily by switching out a policy object. The existing EWMA behavior
4466 is now implemented as a circuitmux_policy_t. Resolves ticket 6816.
4468 o Required libraries:
4469 - Tor now requires OpenSSL 0.9.8 or later. OpenSSL 1.0.0 or later is
4470 strongly recommended.
4473 - Warn users who run hidden services on a Tor client with
4474 UseEntryGuards disabled that their hidden services will be
4475 vulnerable to http://freehaven.net/anonbib/#hs-attack06 (the
4476 attack which motivated Tor to support entry guards in the first
4477 place). Resolves ticket 6889.
4478 - Tor now builds correctly on Bitrig, an OpenBSD fork. Patch from
4479 dhill. Resolves ticket 6982.
4480 - Option OutboundBindAddress can be specified multiple times and
4481 accepts IPv6 addresses. Resolves ticket 6876.
4483 o Minor bugfixes (also in 0.2.3.23-rc):
4484 - Don't serve or accept v2 hidden service descriptors over a
4485 relay's DirPort. It's never correct to do so, and disabling it
4486 might make it more annoying to exploit any bugs that turn up in the
4487 descriptor-parsing code. Fixes bug 7149.
4488 - Fix two cases in src/or/transports.c where we were calling
4489 fmt_addr() twice in a parameter list. Bug found by David
4490 Fifield. Fixes bug 7014; bugfix on 0.2.3.9-alpha.
4491 - Fix memory leaks whenever we logged any message about the "path
4492 bias" detection. Fixes bug 7022; bugfix on 0.2.3.21-rc.
4493 - When relays refuse a "create" cell because their queue of pending
4494 create cells is too big (typically because their cpu can't keep up
4495 with the arrival rate), send back reason "resource limit" rather
4496 than reason "internal", so network measurement scripts can get a
4497 more accurate picture. Fixes bug 7037; bugfix on 0.1.1.11-alpha.
4500 - Command-line option "--version" implies "--quiet". Fixes bug 6997.
4501 - Free some more still-in-use memory at exit, to make hunting for
4502 memory leaks easier. Resolves bug 7029.
4503 - When a Tor client gets a "truncated" relay cell, the first byte of
4504 its payload specifies why the circuit was truncated. We were
4505 ignoring this 'reason' byte when tearing down the circuit, resulting
4506 in the controller not being told why the circuit closed. Now we
4507 pass the reason from the truncated cell to the controller. Bugfix
4508 on 0.1.2.3-alpha; fixes bug 7039.
4509 - Downgrade "Failed to hand off onionskin" messages to "debug"
4510 severity, since they're typically redundant with the "Your computer
4511 is too slow" messages. Fixes bug 7038; bugfix on 0.2.2.16-alpha.
4512 - Make clients running with IPv6 bridges connect over IPv6 again,
4513 even without setting new config options ClientUseIPv6 and
4514 ClientPreferIPv6ORPort. Fixes bug 6757; bugfix on 0.2.4.1-alpha.
4515 - Use square brackets around IPv6 addresses in numerous places
4516 that needed them, including log messages, HTTPS CONNECT proxy
4517 requests, TransportProxy statefile entries, and pluggable transport
4518 extra-info lines. Fixes bug 7011; patch by David Fifield.
4520 o Code refactoring and cleanup:
4521 - Source files taken from other packages now reside in src/ext;
4522 previously they were scattered around the rest of Tor.
4523 - Avoid use of reserved identifiers in our C code. The C standard
4524 doesn't like us declaring anything that starts with an
4525 underscore, so let's knock it off before we get in trouble. Fix
4526 for bug 1031; bugfix on the first Tor commit.
4529 Changes in version 0.2.3.23-rc - 2012-10-20
4530 Tor 0.2.3.23-rc adds a new v3 directory authority, fixes a privacy
4531 vulnerability introduced by a change in OpenSSL, and fixes a variety
4532 of smaller bugs in preparation for the release.
4534 o New directory authorities:
4535 - Add Faravahar (run by Sina Rabbani) as the ninth v3 directory
4536 authority. Closes ticket 5749.
4538 o Major bugfixes (security/privacy):
4539 - Disable TLS session tickets. OpenSSL's implementation was giving
4540 our TLS session keys the lifetime of our TLS context objects, when
4541 perfect forward secrecy would want us to discard anything that
4542 could decrypt a link connection as soon as the link connection
4543 was closed. Fixes bug 7139; bugfix on all versions of Tor linked
4544 against OpenSSL 1.0.0 or later. Found by Florent Daignière.
4545 - Discard extraneous renegotiation attempts once the V3 link
4546 protocol has been initiated. Failure to do so left us open to
4547 a remotely triggerable assertion failure. Fixes CVE-2012-2249;
4548 bugfix on 0.2.3.6-alpha. Reported by "some guy from France".
4551 - Fix a possible crash bug when checking for deactivated circuits
4552 in connection_or_flush_from_first_active_circuit(). Fixes bug 6341;
4553 bugfix on 0.2.2.7-alpha. Bug report and fix received pseudonymously.
4555 o Minor bugfixes (on 0.2.3.x):
4556 - Fix two cases in src/or/transports.c where we were calling
4557 fmt_addr() twice in a parameter list. Bug found by David
4558 Fifield. Fixes bug 7014; bugfix on 0.2.3.9-alpha.
4559 - Convert an assert in the pathbias code to a log message. The assert
4560 appears to only be triggerable by Tor2Web mode. Fixes bug 6866;
4561 bugfix on 0.2.3.17-beta.
4562 - Fix memory leaks whenever we logged any message about the "path
4563 bias" detection. Fixes bug 7022; bugfix on 0.2.3.21-rc.
4565 o Minor bugfixes (on 0.2.2.x and earlier):
4566 - Don't serve or accept v2 hidden service descriptors over a relay's
4567 DirPort. It's never correct to do so, and disabling it might
4568 make it more annoying to exploit any bugs that turn up in the
4569 descriptor-parsing code. Fixes bug 7149.
4570 - When relays refuse a "create" cell because their queue of pending
4571 create cells is too big (typically because their cpu can't keep up
4572 with the arrival rate), send back reason "resource limit" rather
4573 than reason "internal", so network measurement scripts can get a
4574 more accurate picture. Bugfix on 0.1.1.11-alpha; fixes bug 7037.
4575 - Correct file sizes when reading binary files on Cygwin, to avoid
4576 a bug where Tor would fail to read its state file. Fixes bug 6844;
4577 bugfix on 0.1.2.7-alpha.
4578 - Avoid undefined behavior when parsing the list of supported
4579 rendezvous/introduction protocols in a hidden service descriptor.
4580 Previously, Tor would have confused (as-yet-unused) protocol version
4581 numbers greater than 32 with lower ones on many platforms. Fixes
4582 bug 6827; bugfix on 0.2.0.10-alpha. Found by George Kadianakis.
4584 o Documentation fixes:
4585 - Clarify that hidden services are TCP only. Fixes bug 6024.
4588 Changes in version 0.2.4.3-alpha - 2012-09-22
4589 Tor 0.2.4.3-alpha fixes another opportunity for a remotely triggerable
4590 assertion, resumes letting relays test reachability of their DirPort,
4591 and cleans up a bunch of smaller bugs.
4594 - Fix an assertion failure in tor_timegm() that could be triggered
4595 by a badly formatted directory object. Bug found by fuzzing with
4596 Radamsa. Fixes bug 6811; bugfix on 0.2.0.20-rc.
4599 - Fix a possible crash bug when checking for deactivated circuits
4600 in connection_or_flush_from_first_active_circuit(). Fixes bug 6341;
4601 bugfix on 0.2.2.7-alpha. Bug report and fix received pseudonymously.
4602 - Allow routers to detect that their own DirPorts are running. When
4603 we removed support for versions_supports_begindir, we also
4604 accidentally removed the mechanism we used to self-test our
4605 DirPort. Diagnosed with help from kargig. Fixes bugs 6814 and 6815;
4606 bugfix on 0.2.4.2-alpha.
4608 o Security features:
4609 - Switch to a completely time-invariant approach for picking nodes
4610 weighted by bandwidth. Our old approach would run through the
4611 part of the loop after it had made its choice slightly slower
4612 than it ran through the part of the loop before it had made its
4613 choice. Addresses ticket 6538.
4614 - Disable the use of Guard nodes when in Tor2WebMode. Guard usage
4615 by tor2web clients allows hidden services to identify tor2web
4616 clients through their repeated selection of the same rendezvous
4617 and introduction point circuit endpoints (their guards). Resolves
4621 - Enable Tor to read configuration, state, and key information from
4622 a FIFO. Previously Tor would only read from files with a positive
4623 stat.st_size. Code from meejah; fixes bug 6044.
4626 - Correct file sizes when reading binary files on Cygwin, to avoid
4627 a bug where Tor would fail to read its state file. Fixes bug 6844;
4628 bugfix on 0.1.2.7-alpha.
4629 - Correctly handle votes with more than 31 flags. Fixes bug 6853;
4630 bugfix on 0.2.0.3-alpha.
4631 - When complaining about a client port on a public address, log
4632 which address we're complaining about. Fixes bug 4020; bugfix on
4633 0.2.3.3-alpha. Patch by Tom Fitzhenry.
4634 - Convert an assert in the pathbias code to a log message. The assert
4635 appears to only be triggerable by Tor2Web mode. Fixes bug 6866;
4636 bugfix on 0.2.3.17-beta.
4637 - Our new buildsystem was overzealous about rebuilding manpages: it
4638 would rebuild them all whenever any one of them changed. Now our
4639 dependency checking should be correct. Fixes bug 6843; bugfix on
4641 - Don't do reachability testing over IPv6 unless AuthDirPublishIPv6
4642 is set. Fixes bug 6880. Bugfix on 0.2.4.1-alpha.
4643 - Correct log printout about which address family is preferred
4644 when connecting to a bridge with both an IPv4 and IPv6 OR port.
4645 Fixes bug 6884; bugfix on 0.2.4.1-alpha.
4647 o Minor bugfixes (code cleanliness):
4648 - Fix round_to_power_of_2() so it doesn't invoke undefined behavior
4649 with large values. This situation was untriggered, but nevertheless
4650 incorrect. Fixes bug 6831; bugfix on 0.2.0.1-alpha.
4651 - Reject consensus votes with more than 64 known-flags. We aren't even
4652 close to that limit yet, and our code doesn't handle it correctly.
4653 Fixes bug 6833; bugfix on 0.2.0.1-alpha.
4654 - Avoid undefined behavior when parsing the list of supported
4655 rendezvous/introduction protocols in a hidden service descriptor.
4656 Previously, Tor would have confused (as-yet-unused) protocol version
4657 numbers greater than 32 with lower ones on many platforms. Fixes
4658 bug 6827; bugfix on 0.2.0.10-alpha. Found by George Kadianakis.
4659 - Fix handling of rendezvous client authorization types over 8.
4660 Fixes bug 6861; bugfix on 0.2.1.5-alpha.
4661 - Fix building with older versions of GCC (2.95, for one) that don't
4662 like preprocessor directives inside macro arguments. Found by
4663 grarpamp. Fixes bug 6842; bugfix on 0.2.4.2-alpha.
4664 - Switch weighted node selection rule from using a list of doubles
4665 to using a list of int64_t. This change should make the process
4666 slightly easier to debug and maintain. Needed to finish ticket 6538.
4668 o Code simplification and refactoring:
4669 - Move the generic "config" code into a new file, and have "config.c"
4670 hold only torrc- and state-related code. Resolves ticket 6823.
4671 - Move the core of our "choose a weighted element at random" logic
4672 into its own function, and give it unit tests. Now the logic is
4673 testable, and a little less fragile too.
4674 - Removed the testing_since field of node_t, which hasn't been used
4675 for anything since 0.2.0.9-alpha.
4677 o Documentation fixes:
4678 - Clarify that hidden services are TCP only. Fixes bug 6024.
4679 - Resolve a typo in torrc.sample.in. Fixes bug 6819; bugfix on
4683 Changes in version 0.2.3.22-rc - 2012-09-11
4684 Tor 0.2.3.22-rc fixes another opportunity for a remotely triggerable
4688 - Fix an assertion failure in tor_timegm() that could be triggered
4689 by a badly formatted directory object. Bug found by fuzzing with
4690 Radamsa. Fixes bug 6811; bugfix on 0.2.0.20-rc.
4693 - Avoid segfault when starting up having run with an extremely old
4694 version of Tor and parsing its state file. Fixes bug 6801; bugfix
4698 Changes in version 0.2.2.39 - 2012-09-11
4699 Tor 0.2.2.39 fixes two more opportunities for remotely triggerable
4703 - Fix an assertion failure in tor_timegm() that could be triggered
4704 by a badly formatted directory object. Bug found by fuzzing with
4705 Radamsa. Fixes bug 6811; bugfix on 0.2.0.20-rc.
4706 - Do not crash when comparing an address with port value 0 to an
4707 address policy. This bug could have been used to cause a remote
4708 assertion failure by or against directory authorities, or to
4709 allow some applications to crash clients. Fixes bug 6690; bugfix
4713 Changes in version 0.2.4.2-alpha - 2012-09-10
4714 Tor 0.2.4.2-alpha enables port forwarding for pluggable transports,
4715 raises the default rate limiting even more, and makes the bootstrapping
4716 log messages less noisy.
4719 - Automatically forward the TCP ports of pluggable transport
4720 proxies using tor-fw-helper if PortForwarding is enabled. Implements
4724 - Raise the default BandwidthRate/BandwidthBurst values from 5MB/10MB
4725 to 1GB/1GB. The previous defaults were intended to be "basically
4726 infinite", but it turns out they're now limiting our 100mbit+
4727 relays and bridges. Fixes bug 6605; bugfix on 0.2.0.10-alpha (the
4728 last time we raised it).
4731 - Detect when we're running with a version of OpenSSL other than the
4732 one we compiled with. This has occasionally given people hard-to-
4734 - Log fewer lines at level "notice" about our OpenSSL and Libevent
4735 versions and capabilities when everything is going right. Resolves
4736 part of ticket 6736.
4737 - Directory authorities no long accept descriptors for any version of
4738 Tor before 0.2.2.35, or for any 0.2.3 release before 0.2.3.10-alpha.
4739 These versions are insecure, unsupported, or both. Implements
4743 - Rename the (internal-use-only) UsingTestingNetworkDefaults option
4744 to start with a triple-underscore so the controller won't touch it.
4745 Patch by Meejah. Fixes bug 3155. Bugfix on 0.2.2.23-alpha.
4746 - Avoid segfault when starting up having run with an extremely old
4747 version of Tor and parsing its state file. Fixes bug 6801; bugfix
4749 - Rename the (testing-use-only) _UseFilteringSSLBufferevents option
4750 so it doesn't start with _. Fixes bug 3155. Bugfix on 0.2.3.1-alpha.
4751 - Don't follow the NULL pointer if microdescriptor generation fails.
4752 (This does not appear to be triggerable, but it's best to be safe.)
4753 Found by "f. tp.". Fixes bug 6797; bugfix on 0.2.4.1-alpha.
4754 - Fix mis-declared dependencies on src/common/crypto.c and
4755 src/or/tor_main.c that could break out-of-tree builds under some
4756 circumstances. Fixes bug 6778; bugfix on 0.2.4.1-alpha.
4757 - Avoid a warning when building common_sha1.i out of tree. Fixes bug
4758 6778; bugfix on 0.2.4.1-alpha.
4759 - Fix a harmless (in this case) build warning for implicitly
4760 converting a strlen() to an int. Bugfix on 0.2.4.1-alpha.
4763 - Now that all versions before 0.2.2.x are disallowed, we no longer
4764 need to work around their missing features. Thus we can remove a
4765 bunch of compatibility code.
4768 - Tweak tor-fw-helper to accept an arbitrary amount of arbitrary
4769 TCP ports to forward. In the past it only accepted two ports:
4770 the ORPort and the DirPort.
4773 Changes in version 0.2.4.1-alpha - 2012-09-05
4774 Tor 0.2.4.1-alpha lets bridges publish their pluggable transports to
4775 bridgedb; lets relays use IPv6 addresses and directory authorities
4776 advertise them; and switches to a cleaner build interface.
4778 This is the first alpha release in a new series, so expect there to
4779 be bugs. Users who would rather test out a more stable branch should
4780 stay with 0.2.3.x for now.
4782 o Major features (bridges):
4783 - Bridges now report the pluggable transports they support to the
4784 bridge authority, so it can pass the supported transports on to
4785 bridgedb and/or eventually do reachability testing. Implements
4788 o Major features (IPv6):
4789 - Bridge authorities now accept IPv6 bridge addresses and include
4790 them in network status documents. Implements ticket 5534.
4791 - Clients who set "ClientUseIPv6 1" may connect to entry nodes over
4792 IPv6. Set "ClientPreferIPv6ORPort 1" to make this even more likely
4793 to happen. Implements ticket 5535.
4794 - All kind of relays, not just bridges, can now advertise an IPv6
4795 OR port. Implements ticket 6362.
4796 - Directory authorities vote on IPv6 OR ports using the new consensus
4797 method 14. Implements ticket 6363.
4799 o Major features (build):
4800 - Switch to a nonrecursive Makefile structure. Now instead of each
4801 Makefile.am invoking other Makefile.am's, there is a master
4802 Makefile.am that includes the others. This change makes our build
4803 process slightly more maintainable, and improves parallelism for
4804 building with make -j. Original patch by Stewart Smith; various
4805 fixes by Jim Meyering.
4806 - Where available, we now use automake's "silent" make rules by
4807 default, so that warnings are easier to spot. You can get the old
4808 behavior with "make V=1". Patch by Stewart Smith for ticket 6522.
4810 o Minor features (code security and spec conformance):
4811 - Clear keys and key-derived material left on the stack in
4812 rendservice.c and rendclient.c. Check return value of
4813 crypto_pk_write_private_key_to_string() in rend_service_load_keys().
4814 These fixes should make us more forward-secure against cold-boot
4815 attacks and the like. Fixes bug 2385.
4816 - Reject EXTEND cells sent to nonexistent streams. According to the
4817 spec, an EXTEND cell sent to _any_ nonzero stream ID is invalid, but
4818 we were only checking for stream IDs that were currently in use.
4819 Found while hunting for more instances of bug 6271. Bugfix on
4820 0.0.2pre8, which introduced incremental circuit construction.
4822 o Minor features (streamlining);
4823 - No longer include the "opt" prefix when generating routerinfos
4824 or v2 directories: it has been needless since Tor 0.1.2. Closes
4826 - Remove some now-needless code that tried to aggressively flush
4827 OR connections as data was added to them. Since 0.2.0.1-alpha, our
4828 cell queue logic has saved us from the failure mode that this code
4829 was supposed to prevent. Removing this code will limit the number
4830 of baroque control flow paths through Tor's network logic. Reported
4831 pseudonymously on IRC. Fixes bug 6468; bugfix on 0.2.0.1-alpha.
4833 o Minor features (controller):
4834 - Add a "GETINFO signal/names" control port command. Implements
4836 - Provide default values for all options via "GETINFO config/defaults".
4837 Implements ticket 4971.
4839 o Minor features (IPv6):
4840 - New config option "AuthDirHasIPv6Connectivity 1" that directory
4841 authorities should set if they have IPv6 connectivity and want to
4842 do reachability tests for IPv6 relays. Implements feature 5974.
4843 - A relay with an IPv6 OR port now sends that address in NETINFO
4844 cells (in addition to its other address). Implements ticket 6364.
4846 o Minor features (log messages):
4847 - Omit the first heartbeat log message, because it never has anything
4848 useful to say, and it clutters up the bootstrapping messages.
4849 Resolves ticket 6758.
4850 - Don't log about reloading the microdescriptor cache at startup. Our
4851 bootstrap warnings are supposed to tell the user when there's a
4852 problem, and our bootstrap notices say when there isn't. Resolves
4853 ticket 6759; bugfix on 0.2.2.6-alpha.
4854 - Don't log "I learned some more directory information" when we're
4855 reading cached directory information. Reserve it for when new
4856 directory information arrives in response to a fetch. Resolves
4858 - Prevent rounding error in path bias counts when scaling
4859 them down, and use the correct scale factor default. Also demote
4860 some path bias related log messages down a level and make others
4861 less scary sounding. Fixes bug 6647. Bugfix against 0.2.3.17-beta.
4862 - We no longer warn so much when generating manpages from their
4865 o Code simplifications and refactoring:
4866 - Enhance our internal sscanf replacement so that we can eliminate
4867 the last remaining uses of the system sscanf. (Though those uses
4868 of sscanf were safe, sscanf itself is generally error prone, so
4869 we want to eliminate when we can.) Fixes ticket 4195 and Coverity
4871 - Move ipv6_preferred from routerinfo_t to node_t. Addresses bug 4620.
4872 - Move last_reachable and testing_since from routerinfo_t to node_t.
4873 Implements ticket 5529.
4874 - Add replaycache_t structure, functions and unit tests, then refactor
4875 rend_service_introduce() to be more clear to read, improve, debug,
4876 and test. Resolves bug 6177.
4877 - Finally remove support for malloc_good_size and malloc_usable_size.
4878 We had hoped that these functions would let us eke a little more
4879 memory out of our malloc implementation. Unfortunately, the only
4880 implementations that provided these functions are also ones that
4881 are already efficient about not overallocation: they never got us
4882 more than 7 or so bytes per allocation. Removing them saves us a
4883 little code complexity and a nontrivial amount of build complexity.
4886 - Tor maintainers now require Automake version 1.9 or later to build
4887 Tor from the Git repository. (Automake is not required when building
4888 from a source distribution.)
4891 Changes in version 0.2.3.21-rc - 2012-09-05
4892 Tor 0.2.3.21-rc is the fourth release candidate for the Tor 0.2.3.x
4893 series. It fixes a trio of potential security bugs, fixes a bug where
4894 we were leaving some of the fast relays out of the microdescriptor
4895 consensus, resumes interpreting "ORPort 0" and "DirPort 0" correctly,
4896 and cleans up other smaller issues.
4898 o Major bugfixes (security):
4899 - Tear down the circuit if we get an unexpected SENDME cell. Clients
4900 could use this trick to make their circuits receive cells faster
4901 than our flow control would have allowed, or to gum up the network,
4902 or possibly to do targeted memory denial-of-service attacks on
4903 entry nodes. Fixes bug 6252. Bugfix on the 54th commit on Tor --
4904 from July 2002, before the release of Tor 0.0.0. We had committed
4905 this patch previously, but we had to revert it because of bug 6271.
4906 Now that 6271 is fixed, this patch appears to work.
4907 - Reject any attempt to extend to an internal address. Without
4908 this fix, a router could be used to probe addresses on an internal
4909 network to see whether they were accepting connections. Fixes bug
4910 6710; bugfix on 0.0.8pre1.
4911 - Do not crash when comparing an address with port value 0 to an
4912 address policy. This bug could have been used to cause a remote
4913 assertion failure by or against directory authorities, or to
4914 allow some applications to crash clients. Fixes bug 6690; bugfix
4918 - Remove the upper bound on microdescriptor length. We were hitting
4919 the limit for routers with complex exit policies or family
4920 declarations, causing clients to not use them. Fixes the first
4921 piece of bug 6404; fix on 0.2.2.6-alpha.
4922 - Detect "ORPort 0" as meaning, uniformly, that we're not running
4923 as a relay. Previously, some of our code would treat the presence
4924 of any ORPort line as meaning that we should act like a relay,
4925 even though our new listener code would correctly not open any
4926 ORPorts for ORPort 0. Similar bugs in other Port options are also
4927 fixed. Fixes the first half of bug 6507; bugfix on 0.2.3.3-alpha.
4930 - Avoid a pair of double-free and use-after-mark bugs that can
4931 occur with certain timings in canceled and re-received DNS
4932 requests. Fixes bug 6472; bugfix on 0.0.7rc1.
4933 - Fix build and 64-bit compile warnings from --enable-openbsd-malloc.
4934 Fixes bug 6379. Bugfix on 0.2.0.20-rc.
4935 - Allow one-hop directory fetching circuits the full "circuit build
4936 timeout" period, rather than just half of it, before failing them
4937 and marking the relay down. This fix should help reduce cases where
4938 clients declare relays (or worse, bridges) unreachable because
4939 the TLS handshake takes a few seconds to complete. Fixes bug 6743;
4940 bugfix on 0.2.2.2-alpha, where we changed the timeout from a static
4942 - Authorities no longer include any router in their microdescriptor
4943 consensuses for which they couldn't generate or agree on a
4944 microdescriptor. Fixes the second piece of bug 6404; fix on
4946 - Detect and reject attempts to specify both "FooPort" and
4947 "FooPort 0" in the same configuration domain. (It's still okay
4948 to have a FooPort in your configuration file, and use "FooPort 0"
4949 on the command line to disable it.) Fixes the second half of bug
4950 6507; bugfix on 0.2.3.3-alpha.
4951 - Make wildcarded addresses (that is, ones beginning with "*.") work
4952 when provided via the controller's MapAddress command. Previously,
4953 they were accepted, but we never actually noticed that they were
4954 wildcards. Fixes bug 6244; bugfix on 0.2.3.9-alpha.
4955 - Avoid crashing on a malformed state file where EntryGuardPathBias
4956 precedes EntryGuard. Fix for bug 6774; bugfix on 0.2.3.17-beta.
4957 - Add a (probably redundant) memory clear between iterations of
4958 the router status voting loop, to prevent future coding errors
4959 where data might leak between iterations of the loop. Resolves
4962 o Minor bugfixes (log messages):
4963 - Downgrade "set buildtimeout to low value" messages to "info"
4964 severity; they were never an actual problem, there was never
4965 anything reasonable to do about them, and they tended to spam logs
4966 from time to time. Fixes bug 6251; bugfix on 0.2.2.2-alpha.
4967 - Downgrade path-bias warning messages to "info". We'll try to get
4968 them working better in 0.2.4. Add internal circuit construction
4969 state to protect against the noisy warn message "Unexpectedly high
4970 circuit_successes". Also add some additional rate-limited notice
4971 messages to help determine the root cause of the warn. Fixes bug
4972 6475. Bugfix against 0.2.3.17-beta.
4973 - Move log message when unable to find a microdesc in a routerstatus
4974 entry to parse time. Previously we'd spam this warning every time
4975 we tried to figure out which microdescriptors to download. Fixes
4976 the third piece of bug 6404; fix on 0.2.3.18-rc.
4979 - Consider new, removed or changed IPv6 OR ports a non-cosmetic
4980 change when the authority is deciding whether to accept a newly
4981 uploaded descriptor. Implements ticket 6423.
4982 - Add missing documentation for consensus and microdesc files.
4983 Resolves ticket 6732.
4986 Changes in version 0.2.2.38 - 2012-08-12
4987 Tor 0.2.2.38 fixes a remotely triggerable crash bug, and fixes a timing
4988 attack that could in theory leak path information.
4991 - Avoid an uninitialized memory read when reading a vote or consensus
4992 document that has an unrecognized flavor name. This read could
4993 lead to a remote crash bug. Fixes bug 6530; bugfix on 0.2.2.6-alpha.
4994 - Try to leak less information about what relays a client is
4995 choosing to a side-channel attacker. Previously, a Tor client would
4996 stop iterating through the list of available relays as soon as it
4997 had chosen one, thus finishing a little earlier when it picked
4998 a router earlier in the list. If an attacker can recover this
4999 timing information (nontrivial but not proven to be impossible),
5000 they could learn some coarse-grained information about which relays
5001 a client was picking (middle nodes in particular are likelier to
5002 be affected than exits). The timing attack might be mitigated by
5003 other factors (see bug 6537 for some discussion), but it's best
5004 not to take chances. Fixes bug 6537; bugfix on 0.0.8rc1.
5007 Changes in version 0.2.3.20-rc - 2012-08-05
5008 Tor 0.2.3.20-rc is the third release candidate for the Tor 0.2.3.x
5009 series. It fixes a pair of code security bugs and a potential anonymity
5010 issue, updates our RPM spec files, and cleans up other smaller issues.
5013 - Avoid read-from-freed-memory and double-free bugs that could occur
5014 when a DNS request fails while launching it. Fixes bug 6480;
5015 bugfix on 0.2.0.1-alpha.
5016 - Avoid an uninitialized memory read when reading a vote or consensus
5017 document that has an unrecognized flavor name. This read could
5018 lead to a remote crash bug. Fixes bug 6530; bugfix on 0.2.2.6-alpha.
5019 - Try to leak less information about what relays a client is
5020 choosing to a side-channel attacker. Previously, a Tor client would
5021 stop iterating through the list of available relays as soon as it
5022 had chosen one, thus finishing a little earlier when it picked
5023 a router earlier in the list. If an attacker can recover this
5024 timing information (nontrivial but not proven to be impossible),
5025 they could learn some coarse-grained information about which relays
5026 a client was picking (middle nodes in particular are likelier to
5027 be affected than exits). The timing attack might be mitigated by
5028 other factors (see bug 6537 for some discussion), but it's best
5029 not to take chances. Fixes bug 6537; bugfix on 0.0.8rc1.
5032 - Try to make the warning when giving an obsolete SOCKSListenAddress
5033 a little more useful.
5034 - Terminate active server managed proxies if Tor stops being a
5035 relay. Addresses parts of bug 6274; bugfix on 0.2.3.6-alpha.
5036 - Provide a better error message about possible OSX Asciidoc failure
5037 reasons. Fixes bug 6436.
5038 - Warn when Tor is configured to use accounting in a way that can
5039 link a hidden service to some other hidden service or public
5040 address. Resolves ticket 6490.
5043 - Check return value of fputs() when writing authority certificate
5044 file. Fixes Coverity issue 709056; bugfix on 0.2.0.1-alpha.
5045 - Ignore ServerTransportPlugin lines when Tor is not configured as
5046 a relay. Fixes bug 6274; bugfix on 0.2.3.6-alpha.
5047 - When disabling guards for having too high a proportion of failed
5048 circuits, make sure to look at each guard. Fixes bug 6397; bugfix
5052 - Update our default RPM spec files to work with mock and rpmbuild
5053 on RHEL/Fedora. They have an updated set of dependencies and
5054 conflicts, a fix for an ancient typo when creating the "_tor"
5055 user, and better instructions. Thanks to Ondrej Mikle for the
5056 patch series. Fixes bug 6043.
5059 - Make it possible to set the TestingTorNetwork configuration
5060 option using AlternateDirAuthority and AlternateBridgeAuthority
5061 as an alternative to setting DirServer. Addresses ticket 6377.
5064 - Clarify the documentation for the Alternate*Authority options.
5066 - Fix some typos in the manpages. Patch from A. Costa. Fixes bug 6500.
5068 o Code simplification and refactoring:
5069 - Do not use SMARTLIST_FOREACH for any loop whose body exceeds
5070 10 lines. Also, don't nest them. Doing so in the past has
5071 led to hard-to-debug code. The new style is to use the
5072 SMARTLIST_FOREACH_{BEGIN,END} pair. Addresses issue 6400.
5075 Changes in version 0.2.3.19-rc - 2012-07-06
5076 Tor 0.2.3.19-rc is the second release candidate for the Tor 0.2.3.x
5077 series. It fixes the compile on Windows, reverts to a GeoIP database
5078 that isn't as broken, and fixes a flow control bug that has been around
5079 since the beginning of Tor.
5082 - Fix a bug handling SENDME cells on nonexistent streams that could
5083 result in bizarre window values. Report and patch contributed
5084 pseudonymously. Fixes part of bug 6271. This bug was introduced
5085 before the first Tor release, in svn commit r152.
5086 - Revert to the May 1 2012 Maxmind GeoLite Country database. In the
5087 June 2012 database, Maxmind marked many Tor relays as country "A1",
5088 which will cause risky behavior for clients that set EntryNodes
5089 or ExitNodes. Addresses bug 6334; bugfix on 0.2.3.17-beta.
5090 - Instead of ENOBUFS on Windows, say WSAENOBUFS. Fixes compilation
5091 on Windows. Fixes bug 6296; bugfix on 0.2.3.18-rc.
5094 - Fix wrong TCP port range in parse_port_range(). Fixes bug 6218;
5095 bugfix on 0.2.1.10-alpha.
5098 Changes in version 0.2.3.18-rc - 2012-06-28
5099 Tor 0.2.3.18-rc is the first release candidate for the Tor 0.2.3.x
5100 series. It fixes a few smaller bugs, but generally appears stable.
5101 Please test it and let us know whether it is!
5104 - Allow wildcarded mapaddress targets to be specified on the
5105 controlport. Partially fixes bug 6244; bugfix on 0.2.3.9-alpha.
5106 - Make our linker option detection code more robust against linkers
5107 such as on FreeBSD 8, where a bad combination of options completes
5108 successfully but makes an unrunnable binary. Fixes bug 6173;
5109 bugfix on 0.2.3.17-beta.
5111 o Minor bugfixes (on 0.2.2.x and earlier):
5112 - Avoid a false positive in the util/threads unit test by increasing
5113 the maximum timeout time. Fixes bug 6227; bugfix on 0.2.0.4-alpha.
5114 - Replace "Sending publish request" log messages with "Launching
5115 upload", so that they no longer confusingly imply that we're
5116 sending something to a directory we might not even be connected
5117 to yet. Fixes bug 3311; bugfix on 0.2.0.10-alpha.
5118 - Make sure to set *socket_error in all error cases in
5119 connection_connect(), so it can't produce a warning about
5120 errno being zero from errno_to_orconn_end_reason(). Bugfix on
5121 0.2.1.1-alpha; resolves ticket 6028.
5122 - Downgrade "Got a certificate, but we already have it" log messages
5123 from warning to info, except when we're a dirauth. Fixes bug 5238;
5124 bugfix on 0.2.1.7-alpha.
5125 - When checking for requested signatures on the latest consensus
5126 before serving it to a client, make sure to check the right
5127 consensus flavor. Bugfix on 0.2.2.6-alpha.
5128 - Downgrade "eventdns rejected address" message to LOG_PROTOCOL_WARN.
5129 Fixes bug 5932; bugfix on 0.2.2.7-alpha.
5131 o Minor bugfixes (on 0.2.3.x):
5132 - Make format_helper_exit_status() avoid unnecessary space padding
5133 and stop confusing log_from_pipe(). Fixes ticket 5557; bugfix
5135 - Downgrade a message about cleaning the microdescriptor cache to
5136 "info" from "notice". Fixes bug 6238; bugfix on 0.2.3.1-alpha.
5137 - Log a BUG message at severity INFO if we have a networkstatus with
5138 a missing entry for some microdescriptor. Continues on a patch
5140 - Improve the log message when a managed proxy fails to launch. Fixes
5141 bug 5099; bugfix on 0.2.3.6-alpha.
5142 - Don't do DNS lookups when parsing corrupted managed proxy protocol
5143 messages. Fixes bug 6226; bugfix on 0.2.3.6-alpha.
5144 - When formatting wildcarded address mappings for the controller,
5145 be sure to include "*." as appropriate. Partially fixes bug 6244;
5146 bugfix on 0.2.3.9-alpha.
5147 - Avoid a warning caused by using strcspn() from glibc with clang 3.0.
5148 Bugfix on 0.2.3.13-alpha.
5149 - Stop logging messages about running with circuit timeout learning
5150 enabled at severity LD_BUG. Fixes bug 6169; bugfix on 0.2.3.17-beta.
5151 - Disable a spurious warning about reading on a marked and flushing
5152 connection. We shouldn't be doing that, but apparently we
5153 sometimes do. Fixes bug 6203; bugfix on 0.2.3.17-beta.
5154 - Fix a bug that stopped AllowDotExit from working on addresses
5155 that had an entry in the DNS cache. Fixes bug 6211; bugfix on
5158 o Code simplification, refactoring, unit tests:
5159 - Move tor_gettimeofday_cached() into compat_libevent.c, and use
5160 Libevent's notion of cached time when possible.
5161 - Remove duplicate code for invoking getrlimit() from control.c.
5162 - Add a unit test for the environment_variable_names_equal function.
5165 - Document the --defaults-torrc option, and the new (in 0.2.3)
5166 semantics for overriding, extending, and clearing lists of
5167 options. Closes bug 4748.
5170 Changes in version 0.2.3.17-beta - 2012-06-15
5171 Tor 0.2.3.17-beta enables compiler and linker hardening by default,
5172 gets our TLS handshake back on track for being able to blend in with
5173 Firefox, fixes a big bug in 0.2.3.16-alpha that broke Tor's interaction
5174 with Vidalia, and otherwise continues to get us closer to a release
5178 - Enable gcc and ld hardening by default. Resolves ticket 5210.
5179 - Update TLS cipher list to match Firefox 8 and later. Resolves
5181 - Implement the client side of proposal 198: remove support for
5182 clients falsely claiming to support standard ciphersuites that
5183 they can actually provide. As of modern OpenSSL versions, it's not
5184 necessary to fake any standard ciphersuite, and doing so prevents
5185 us from using better ciphersuites in the future, since servers
5186 can't know whether an advertised ciphersuite is really supported or
5187 not. Some hosts -- notably, ones with very old versions of OpenSSL
5188 or where OpenSSL has been built with ECC disabled -- will stand
5189 out because of this change; TBB users should not be affected.
5192 - Change the default value for DynamicDHGroups (introduced in
5193 0.2.3.9-alpha) to 0. This feature can make Tor relays less
5194 identifiable by their use of the mod_ssl DH group, but at
5195 the cost of some usability (#4721) and bridge tracing (#6087)
5196 regressions. Resolves ticket 5598.
5197 - Send a CRLF at the end of each STATUS_* control protocol event. This
5198 bug tickled a bug in Vidalia which would make it freeze. Fixes
5199 bug 6094; bugfix on 0.2.3.16-alpha.
5202 - Disable writing on marked-for-close connections when they are
5203 blocked on bandwidth, to prevent busy-looping in Libevent. Fixes
5204 bug 5263; bugfix on 0.0.2pre13, where we first added a special
5205 case for flushing marked connections.
5206 - Detect SSL handshake even when the initial attempt to write the
5207 server hello fails. Fixes bug 4592; bugfix on 0.2.0.13-alpha.
5208 - Change the AllowDotExit rules so they should actually work.
5209 We now enforce AllowDotExit only immediately after receiving an
5210 address via SOCKS or DNSPort: other sources are free to provide
5211 .exit addresses after the resolution occurs. Fixes bug 3940;
5212 bugfix on 0.2.2.1-alpha.
5213 - Fix a (harmless) integer overflow in cell statistics reported by
5214 some fast relays. Fixes bug 5849; bugfix on 0.2.2.1-alpha.
5215 - Make sure circuitbuild.c checks LearnCircuitBuildTimeout in all the
5216 right places and never depends on the consensus parameters or
5217 computes adaptive timeouts when it is disabled. Fixes bug 5049;
5218 bugfix on 0.2.2.14-alpha.
5219 - When building Tor on Windows with -DUNICODE (not default), ensure
5220 that error messages, filenames, and DNS server names are always
5221 NUL-terminated when we convert them to a single-byte encoding.
5222 Fixes bug 5909; bugfix on 0.2.2.16-alpha.
5223 - Make Tor build correctly again with -DUNICODE -D_UNICODE defined.
5224 Fixes bug 6097; bugfix on 0.2.2.16-alpha.
5225 - Fix an edge case where TestingTorNetwork is set but the authorities
5226 and relays all have an uptime of zero, where the private Tor network
5227 could briefly lack support for hidden services. Fixes bug 3886;
5228 bugfix on 0.2.2.18-alpha.
5229 - Correct the manpage's descriptions for the default values of
5230 DirReqStatistics and ExtraInfoStatistics. Fixes bug 2865; bugfix
5232 - Fix the documentation for the --hush and --quiet command line
5233 options, which changed their behavior back in 0.2.3.3-alpha.
5234 - Fix compilation warning with clang 3.1. Fixes bug 6141; bugfix on
5238 - Rate-limit the "Weighted bandwidth is 0.000000" message, and add
5239 more information to it, so that we can track it down in case it
5240 returns again. Mitigates bug 5235.
5241 - Check CircuitBuildTimeout and LearnCircuitBuildTimeout in
5242 options_validate(); warn if LearnCircuitBuildTimeout is disabled and
5243 CircuitBuildTimeout is set unreasonably low. Resolves ticket 5452.
5244 - Warn the user when HTTPProxy, but no other proxy type, is
5245 configured. This can cause surprising behavior: it doesn't send
5246 all of Tor's traffic over the HTTPProxy -- it sends unencrypted
5247 directory traffic only. Resolves ticket 4663.
5248 - Issue a notice if a guard completes less than 40% of your circuits.
5249 Threshold is configurable by torrc option PathBiasNoticeRate and
5250 consensus parameter pb_noticepct. There is additional, off-by-
5251 default code to disable guards which fail too many circuits.
5252 Addresses ticket 5458.
5253 - Update to the June 6 2012 Maxmind GeoLite Country database.
5255 o Code simplifications and refactoring:
5256 - Remove validate_pluggable_transports_config(): its warning
5257 message is now handled by connection_or_connect().
5260 Changes in version 0.2.2.37 - 2012-06-06
5261 Tor 0.2.2.37 introduces a workaround for a critical renegotiation
5262 bug in OpenSSL 1.0.1 (where 20% of the Tor network can't talk to itself
5266 - Work around a bug in OpenSSL that broke renegotiation with TLS
5267 1.1 and TLS 1.2. Without this workaround, all attempts to speak
5268 the v2 Tor connection protocol when both sides were using OpenSSL
5269 1.0.1 would fail. Resolves ticket 6033.
5270 - When waiting for a client to renegotiate, don't allow it to add
5271 any bytes to the input buffer. This fixes a potential DoS issue.
5272 Fixes bugs 5934 and 6007; bugfix on 0.2.0.20-rc.
5273 - Fix an edge case where if we fetch or publish a hidden service
5274 descriptor, we might build a 4-hop circuit and then use that circuit
5275 for exiting afterwards -- even if the new last hop doesn't obey our
5276 ExitNodes config option. Fixes bug 5283; bugfix on 0.2.0.10-alpha.
5279 - Fix a build warning with Clang 3.1 related to our use of vasprintf.
5280 Fixes bug 5969. Bugfix on 0.2.2.11-alpha.
5283 - Tell GCC and Clang to check for any errors in format strings passed
5284 to the tor_v*(print|scan)f functions.
5287 Changes in version 0.2.3.16-alpha - 2012-06-05
5288 Tor 0.2.3.16-alpha introduces a workaround for a critical renegotiation
5289 bug in OpenSSL 1.0.1 (where 20% of the Tor network can't talk to itself
5290 currently). It also fixes a variety of smaller bugs and other cleanups
5291 that get us closer to a release candidate.
5293 o Major bugfixes (general):
5294 - Work around a bug in OpenSSL that broke renegotiation with TLS
5295 1.1 and TLS 1.2. Without this workaround, all attempts to speak
5296 the v2 Tor connection protocol when both sides were using OpenSSL
5297 1.0.1 would fail. Resolves ticket 6033.
5298 - When waiting for a client to renegotiate, don't allow it to add
5299 any bytes to the input buffer. This fixes a potential DoS issue.
5300 Fixes bugs 5934 and 6007; bugfix on 0.2.0.20-rc.
5301 - Pass correct OR address to managed proxies (like obfsproxy),
5302 even when ORListenAddress is used. Fixes bug 4865; bugfix on
5304 - The advertised platform of a router now includes only its operating
5305 system's name (e.g., "Linux", "Darwin", "Windows 7"), and not its
5306 service pack level (for Windows) or its CPU architecture (for Unix).
5307 We also no longer include the "git-XYZ" tag in the version. Resolves
5310 o Major bugfixes (clients):
5311 - If we are unable to find any exit that supports our predicted ports,
5312 stop calling them predicted, so that we don't loop and build
5313 hopeless circuits indefinitely. Fixes bug 3296; bugfix on 0.0.9pre6,
5314 which introduced predicted ports.
5315 - Fix an edge case where if we fetch or publish a hidden service
5316 descriptor, we might build a 4-hop circuit and then use that circuit
5317 for exiting afterwards -- even if the new last hop doesn't obey our
5318 ExitNodes config option. Fixes bug 5283; bugfix on 0.2.0.10-alpha.
5319 - Check at each new consensus whether our entry guards were picked
5320 long enough ago that we should rotate them. Previously, we only
5321 did this check at startup, which could lead to us holding a guard
5322 indefinitely. Fixes bug 5380; bugfix on 0.2.1.14-rc.
5323 - When fetching a bridge descriptor from a bridge authority,
5324 always do so anonymously, whether we have been able to open
5325 circuits or not. Partial fix for bug 1938; bugfix on 0.2.0.7-alpha.
5326 This behavior makes it *safer* to use UpdateBridgesFromAuthority,
5327 but we'll need to wait for bug 6010 before it's actually usable.
5329 o Major bugfixes (directory authorities):
5330 - When computing weight parameters, behave more robustly in the
5331 presence of a bad bwweightscale value. Previously, the authorities
5332 would crash if they agreed on a sufficiently broken weight_scale
5333 value: now, they use a reasonable default and carry on. Partial
5334 fix for 5786; bugfix on 0.2.2.17-alpha.
5335 - Check more thoroughly to prevent a rogue authority from
5336 double-voting on any consensus directory parameter. Previously,
5337 authorities would crash in this case if the total number of
5338 votes for any parameter exceeded the number of active voters,
5339 but would let it pass otherwise. Partial fix for bug 5786; bugfix
5343 - Rate-limit log messages when asked to connect anonymously to
5344 a private address. When these hit, they tended to hit fast and
5345 often. Also, don't bother trying to connect to addresses that we
5346 are sure will resolve to 127.0.0.1: getting 127.0.0.1 in a directory
5347 reply makes us think we have been lied to, even when the address the
5348 client tried to connect to was "localhost." Resolves ticket 2822.
5349 - Allow packagers to insert an extra string in server descriptor
5350 platform lines by setting the preprocessor variable TOR_BUILD_TAG.
5351 Resolves the rest of ticket 2988.
5352 - Raise the threshold of server descriptors needed (75%) and exit
5353 server descriptors needed (50%) before we will declare ourselves
5354 bootstrapped. This will make clients start building circuits a
5355 little later, but makes the initially constructed circuits less
5356 skewed and less in conflict with further directory fetches. Fixes
5358 - Close any connection that sends unrecognized junk before the
5359 handshake. Solves an issue noted in bug 4369.
5360 - Improve log messages about managed transports. Resolves ticket 5070.
5361 - Tag a bridge's descriptor as "never to be sent unencrypted".
5362 This shouldn't matter, since bridges don't open non-anonymous
5363 connections to the bridge authority and don't allow unencrypted
5364 directory connections from clients, but we might as well make
5365 sure. Closes bug 5139.
5366 - Expose our view of whether we have gone dormant to the controller,
5367 via a new "GETINFO dormant" value. Torbutton and other controllers
5368 can use this to avoid doing periodic requests through Tor while
5369 it's dormant (bug 4718). Fixes bug 5954.
5370 - Tell GCC and Clang to check for any errors in format strings passed
5371 to the tor_v*(print|scan)f functions.
5372 - Update to the May 1 2012 Maxmind GeoLite Country database.
5374 o Minor bugfixes (already included in 0.2.2.36):
5375 - Reject out-of-range times like 23:59:61 in parse_rfc1123_time().
5376 Fixes bug 5346; bugfix on 0.0.8pre3.
5377 - Correct parsing of certain date types in parse_http_time().
5378 Without this patch, If-Modified-Since would behave
5379 incorrectly. Fixes bug 5346; bugfix on 0.2.0.2-alpha. Patch from
5380 Esteban Manchado Velázques.
5381 - Make our number-parsing functions always treat too-large values
5382 as an error, even when those values exceed the width of the
5383 underlying type. Previously, if the caller provided these
5384 functions with minima or maxima set to the extreme values of the
5385 underlying integer type, these functions would return those
5386 values on overflow rather than treating overflow as an error.
5387 Fixes part of bug 5786; bugfix on 0.0.9.
5388 - If we hit the error case where routerlist_insert() replaces an
5389 existing (old) server descriptor, make sure to remove that
5390 server descriptor from the old_routers list. Fix related to bug
5391 1776. Bugfix on 0.2.2.18-alpha.
5392 - Clarify the behavior of MaxCircuitDirtiness with hidden service
5393 circuits. Fixes issue 5259.
5395 o Minor bugfixes (coding cleanup, on 0.2.2.x and earlier):
5396 - Prevent a null-pointer dereference when receiving a data cell
5397 for a nonexistent stream when the circuit in question has an
5398 empty deliver window. We don't believe this is triggerable,
5399 since we don't currently allow deliver windows to become empty,
5400 but the logic is tricky enough that it's better to make the code
5401 robust. Fixes bug 5541; bugfix on 0.0.2pre14.
5402 - Fix a memory leak when trying to launch a DNS request when the
5403 network is disabled or the nameservers are unconfigurable. Fixes
5404 bug 5916; bugfix on Tor 0.1.2.1-alpha (for the unconfigurable
5405 nameserver case) and on 0.2.3.9-alpha (for the DisableNetwork case).
5406 - Don't hold a Windows file handle open for every file mapping;
5407 the file mapping handle is sufficient. Fixes bug 5951; bugfix on
5409 - Avoid O(n^2) performance characteristics when parsing a large
5410 extrainfo cache. Fixes bug 5828; bugfix on 0.2.0.1-alpha.
5411 - Format more doubles with %f, not %lf. Patch from grarpamp to make
5412 Tor build correctly on older BSDs again. Fixes bug 3894; bugfix on
5414 - Make our replacement implementation of strtok_r() compatible with
5415 the standard behavior of strtok_r(). Patch by nils. Fixes bug 5091;
5416 bugfix on 0.2.2.1-alpha.
5417 - Fix a NULL-pointer dereference on a badly formed
5418 SETCIRCUITPURPOSE command. Found by mikeyc. Fixes bug 5796;
5419 bugfix on 0.2.2.9-alpha.
5420 - Fix a build warning with Clang 3.1 related to our use of vasprintf.
5421 Fixes bug 5969. Bugfix on 0.2.2.11-alpha.
5422 - Defensively refactor rend_mid_rendezvous() so that protocol
5423 violations and length checks happen in the beginning. Fixes
5425 - Set _WIN32_WINNT to 0x0501 consistently throughout the code, so
5426 that IPv6 stuff will compile on MSVC, and compilation issues
5427 will be easier to track down. Fixes bug 5861.
5429 o Minor bugfixes (correctness, on 0.2.2.x and earlier):
5430 - Exit nodes now correctly report EADDRINUSE and EADDRNOTAVAIL as
5431 resource exhaustion, so that clients can adjust their load to
5432 try other exits. Fixes bug 4710; bugfix on 0.1.0.1-rc, which
5433 started using END_STREAM_REASON_RESOURCELIMIT.
5434 - Don't check for whether the address we're using for outbound
5435 connections has changed until after the outbound connection has
5436 completed. On Windows, getsockname() doesn't succeed until the
5437 connection is finished. Fixes bug 5374; bugfix on 0.1.1.14-alpha.
5438 - If the configuration tries to set MyFamily on a bridge, refuse to
5439 do so, and warn about the security implications. Fixes bug 4657;
5440 bugfix on 0.2.0.3-alpha.
5441 - If the client fails to set a reasonable set of ciphersuites
5442 during its v2 handshake renegotiation, allow the renegotiation to
5443 continue nevertheless (i.e. send all the required certificates).
5444 Fixes bug 4591; bugfix on 0.2.0.20-rc.
5445 - When we receive a SIGHUP and the controller __ReloadTorrcOnSIGHUP
5446 option is set to 0 (which Vidalia version 0.2.16 now does when
5447 a SAVECONF attempt fails), perform other actions that SIGHUP
5448 usually causes (like reopening the logs). Fixes bug 5095; bugfix
5450 - If we fail to write a microdescriptor to the disk cache, do not
5451 continue replacing the old microdescriptor file. Fixes bug 2954;
5452 bugfix on 0.2.2.6-alpha.
5453 - Exit nodes don't need to fetch certificates for authorities that
5454 they don't recognize; only directory authorities, bridges,
5455 and caches need to do that. Fixes part of bug 2297; bugfix on
5457 - Correctly handle checking the permissions on the parent
5458 directory of a control socket in the root directory. Bug found
5459 by Esteban Manchado Velázquez. Fixes bug 5089; bugfix on Tor
5461 - When told to add a bridge with the same digest as a preexisting
5462 bridge but a different addr:port, change the addr:port as
5463 requested. Previously we would not notice the change. Fixes half
5464 of bug 5603; fix on 0.2.2.26-beta.
5465 - End AUTHCHALLENGE error messages (in the control protocol) with
5466 a CRLF. Fixes bug 5760; bugfix on 0.2.2.36 and 0.2.3.13-alpha.
5468 o Minor bugfixes (on 0.2.3.x):
5469 - Turn an assertion (that the number of handshakes received as a
5470 server is not < 1) into a warning. Fixes bug 4873; bugfix on
5472 - Format IPv4 addresses correctly in ADDRMAP events. (Previously,
5473 we had reversed them when the answer was cached.) Fixes bug
5474 5723; bugfix on 0.2.3.1-alpha.
5475 - Work correctly on Linux systems with accept4 support advertised in
5476 their headers, but without accept4 support in the kernel. Fix
5477 by murb. Fixes bug 5762; bugfix on 0.2.3.1-alpha.
5478 - When told to add a bridge with the same addr:port as a preexisting
5479 bridge but a different transport, change the transport as
5480 requested. Previously we would not notice the change. Fixes half
5481 of bug 5603; fix on 0.2.3.2-alpha.
5482 - Avoid a "double-reply" warning when replying to a SOCKS request
5483 with a parse error. Patch from Fabian Keil. Fixes bug 4108;
5484 bugfix on 0.2.3.4-alpha.
5485 - Fix a bug where a bridge authority crashes if it has seen no
5486 directory requests when it's time to write statistics to disk.
5487 Fixes bug 5891; bugfix on 0.2.3.6-alpha. Also fixes bug 5508 in
5489 - Don't try to open non-control listeners when DisableNetwork is set.
5490 Previously, we'd open all listeners, then immediately close them.
5491 Fixes bug 5604; bugfix on 0.2.3.9-alpha.
5492 - Don't abort the managed proxy protocol if the managed proxy
5493 sends us an unrecognized line; ignore it instead. Fixes bug
5494 5910; bugfix on 0.2.3.9-alpha.
5495 - Fix a compile warning in crypto.c when compiling with clang 3.1.
5496 Fixes bug 5969, bugfix on 0.2.3.9-alpha.
5497 - Fix a compilation issue on GNU Hurd, which doesn't have PATH_MAX.
5498 Fixes bug 5355; bugfix on 0.2.3.11-alpha.
5499 - Remove bogus definition of "_WIN32" from src/win32/orconfig.h, to
5500 unbreak the MSVC build. Fixes bug 5858; bugfix on 0.2.3.12-alpha.
5501 - Resolve numerous small warnings and build issues with MSVC. Resolves
5504 o Documentation fixes:
5505 - Improve the manual's documentation for the NT Service command-line
5506 options. Addresses ticket 3964.
5507 - Clarify SessionGroup documentation slightly; resolves ticket 5437.
5508 - Document the changes to the ORPort and DirPort options, and the
5509 fact that {OR/Dir}ListenAddress is now unnecessary (and
5510 therefore deprecated). Resolves ticket 5597.
5513 - Remove the torrc.bridge file: we don't use it for anything, and
5514 it had become badly desynchronized from torrc.sample. Resolves
5518 Changes in version 0.2.2.36 - 2012-05-24
5519 Tor 0.2.2.36 updates the addresses for two of the eight directory
5520 authorities, fixes some potential anonymity and security issues,
5521 and fixes several crash bugs.
5523 Tor 0.2.1.x has reached its end-of-life. Those Tor versions have many
5524 known flaws, and nobody should be using them. You should upgrade. If
5525 you're using a Linux or BSD and its packages are obsolete, stop using
5526 those packages and upgrade anyway.
5528 o Directory authority changes:
5529 - Change IP address for maatuska (v3 directory authority).
5530 - Change IP address for ides (v3 directory authority), and rename
5534 - When building or running with any version of OpenSSL earlier
5535 than 0.9.8s or 1.0.0f, disable SSLv3 support. These OpenSSL
5536 versions have a bug (CVE-2011-4576) in which their block cipher
5537 padding includes uninitialized data, potentially leaking sensitive
5538 information to any peer with whom they make a SSLv3 connection. Tor
5539 does not use SSL v3 by default, but a hostile client or server
5540 could force an SSLv3 connection in order to gain information that
5541 they shouldn't have been able to get. The best solution here is to
5542 upgrade to OpenSSL 0.9.8s or 1.0.0f (or later). But when building
5543 or running with a non-upgraded OpenSSL, we disable SSLv3 entirely
5544 to make sure that the bug can't happen.
5545 - Never use a bridge or a controller-supplied node as an exit, even
5546 if its exit policy allows it. Found by wanoskarnet. Fixes bug
5547 5342. Bugfix on 0.1.1.15-rc (for controller-purpose descriptors)
5548 and 0.2.0.3-alpha (for bridge-purpose descriptors).
5549 - Only build circuits if we have a sufficient threshold of the total
5550 descriptors that are marked in the consensus with the "Exit"
5551 flag. This mitigates an attack proposed by wanoskarnet, in which
5552 all of a client's bridges collude to restrict the exit nodes that
5553 the client knows about. Fixes bug 5343.
5554 - Provide controllers with a safer way to implement the cookie
5555 authentication mechanism. With the old method, if another locally
5556 running program could convince a controller that it was the Tor
5557 process, then that program could trick the controller into telling
5558 it the contents of an arbitrary 32-byte file. The new "SAFECOOKIE"
5559 authentication method uses a challenge-response approach to prevent
5560 this attack. Fixes bug 5185; implements proposal 193.
5563 - Avoid logging uninitialized data when unable to decode a hidden
5564 service descriptor cookie. Fixes bug 5647; bugfix on 0.2.1.5-alpha.
5565 - Avoid a client-side assertion failure when receiving an INTRODUCE2
5566 cell on a general purpose circuit. Fixes bug 5644; bugfix on
5568 - Fix builds when the path to sed, openssl, or sha1sum contains
5569 spaces, which is pretty common on Windows. Fixes bug 5065; bugfix
5571 - Correct our replacements for the timeradd() and timersub() functions
5572 on platforms that lack them (for example, Windows). The timersub()
5573 function is used when expiring circuits, while timeradd() is
5574 currently unused. Bug report and patch by Vektor. Fixes bug 4778;
5575 bugfix on 0.2.2.24-alpha.
5576 - Fix the SOCKET_OK test that we use to tell when socket
5577 creation fails so that it works on Win64. Fixes part of bug 4533;
5578 bugfix on 0.2.2.29-beta. Bug found by wanoskarnet.
5581 - Reject out-of-range times like 23:59:61 in parse_rfc1123_time().
5582 Fixes bug 5346; bugfix on 0.0.8pre3.
5583 - Make our number-parsing functions always treat too-large values
5584 as an error, even when those values exceed the width of the
5585 underlying type. Previously, if the caller provided these
5586 functions with minima or maxima set to the extreme values of the
5587 underlying integer type, these functions would return those
5588 values on overflow rather than treating overflow as an error.
5589 Fixes part of bug 5786; bugfix on 0.0.9.
5590 - Older Linux kernels erroneously respond to strange nmap behavior
5591 by having accept() return successfully with a zero-length
5592 socket. When this happens, just close the connection. Previously,
5593 we would try harder to learn the remote address: but there was
5594 no such remote address to learn, and our method for trying to
5595 learn it was incorrect. Fixes bugs 1240, 4745, and 4747. Bugfix
5596 on 0.1.0.3-rc. Reported and diagnosed by "r1eo".
5597 - Correct parsing of certain date types in parse_http_time().
5598 Without this patch, If-Modified-Since would behave
5599 incorrectly. Fixes bug 5346; bugfix on 0.2.0.2-alpha. Patch from
5600 Esteban Manchado Velázques.
5601 - Change the BridgePassword feature (part of the "bridge community"
5602 design, which is not yet implemented) to use a time-independent
5603 comparison. The old behavior might have allowed an adversary
5604 to use timing to guess the BridgePassword value. Fixes bug 5543;
5605 bugfix on 0.2.0.14-alpha.
5606 - Detect and reject certain misformed escape sequences in
5607 configuration values. Previously, these values would cause us
5608 to crash if received in a torrc file or over an authenticated
5609 control port. Bug found by Esteban Manchado Velázquez, and
5610 independently by Robert Connolly from Matta Consulting who further
5611 noted that it allows a post-authentication heap overflow. Patch
5612 by Alexander Schrijver. Fixes bugs 5090 and 5402 (CVE 2012-1668);
5613 bugfix on 0.2.0.16-alpha.
5614 - Fix a compile warning when using the --enable-openbsd-malloc
5615 configure option. Fixes bug 5340; bugfix on 0.2.0.20-rc.
5616 - During configure, detect when we're building with clang version
5617 3.0 or lower and disable the -Wnormalized=id and -Woverride-init
5618 CFLAGS. clang doesn't support them yet.
5619 - When sending an HTTP/1.1 proxy request, include a Host header.
5620 Fixes bug 5593; bugfix on 0.2.2.1-alpha.
5621 - Fix a NULL-pointer dereference on a badly formed SETCIRCUITPURPOSE
5622 command. Found by mikeyc. Fixes bug 5796; bugfix on 0.2.2.9-alpha.
5623 - If we hit the error case where routerlist_insert() replaces an
5624 existing (old) server descriptor, make sure to remove that
5625 server descriptor from the old_routers list. Fix related to bug
5626 1776. Bugfix on 0.2.2.18-alpha.
5628 o Minor bugfixes (documentation and log messages):
5629 - Fix a typo in a log message in rend_service_rendezvous_has_opened().
5630 Fixes bug 4856; bugfix on Tor 0.0.6.
5631 - Update "ClientOnly" man page entry to explain that there isn't
5632 really any point to messing with it. Resolves ticket 5005.
5633 - Document the GiveGuardFlagTo_CVE_2011_2768_VulnerableRelays
5634 directory authority option (introduced in Tor 0.2.2.34).
5635 - Downgrade the "We're missing a certificate" message from notice
5636 to info: people kept mistaking it for a real problem, whereas it
5637 is seldom the problem even when we are failing to bootstrap. Fixes
5638 bug 5067; bugfix on 0.2.0.10-alpha.
5639 - Correctly spell "connect" in a log message on failure to create a
5640 controlsocket. Fixes bug 4803; bugfix on 0.2.2.26-beta.
5641 - Clarify the behavior of MaxCircuitDirtiness with hidden service
5642 circuits. Fixes issue 5259.
5645 - Directory authorities now reject versions of Tor older than
5646 0.2.1.30, and Tor versions between 0.2.2.1-alpha and 0.2.2.20-alpha
5647 inclusive. These versions accounted for only a small fraction of
5648 the Tor network, and have numerous known security issues. Resolves
5650 - Update to the May 1 2012 Maxmind GeoLite Country database.
5653 - When sending or relaying a RELAY_EARLY cell, we used to convert
5654 it to a RELAY cell if the connection was using the v1 link
5655 protocol. This was a workaround for older versions of Tor, which
5656 didn't handle RELAY_EARLY cells properly. Now that all supported
5657 versions can handle RELAY_EARLY cells, and now that we're enforcing
5658 the "no RELAY_EXTEND commands except in RELAY_EARLY cells" rule,
5659 remove this workaround. Addresses bug 4786.
5662 Changes in version 0.2.3.15-alpha - 2012-04-30
5663 Tor 0.2.3.15-alpha fixes a variety of smaller bugs, including making
5664 the development branch build on Windows again.
5666 o Minor bugfixes (on 0.2.2.x and earlier):
5667 - Make sure that there are no unhandled pending TLS errors before
5668 reading from a TLS stream. We had checks in 0.1.0.3-rc, but
5669 lost them in 0.1.0.5-rc when we refactored read_to_buf_tls().
5670 Bugfix on 0.1.0.5-rc; fixes bug 4528.
5671 - Fix an assert that directory authorities could trigger on sighup
5672 during some configuration state transitions. We now don't treat
5673 it as a fatal error when the new descriptor we just generated in
5674 init_keys() isn't accepted. Fixes bug 4438; bugfix on 0.2.1.9-alpha.
5675 - After we pick a directory mirror, we would refuse to use it if
5676 it's in our ExcludeExitNodes list, resulting in mysterious failures
5677 to bootstrap for people who just wanted to avoid exiting from
5678 certain locations. Fixes bug 5623; bugfix on 0.2.2.25-alpha.
5679 - When building with --enable-static-tor on OpenBSD, do not
5680 erroneously attempt to link -lrt. Fixes bug 5103.
5682 o Minor bugfixes (on 0.2.3.x):
5683 - When Tor is built with kernel headers from a recent (last few
5684 years) Linux kernel, do not fail to run on older (pre-2.6.28
5685 Linux kernels). Fixes bug 5112; bugfix on 0.2.3.1-alpha.
5686 - Fix cross-compilation issues with mingw. Bugfixes on 0.2.3.6-alpha
5688 - Fix compilation with miniupnpc version 1.6; patch from
5689 Anthony G. Basile. Fixes bug 5434; bugfix on 0.2.3.12-alpha.
5690 - Fix compilation with MSVC, which had defined MS_WINDOWS. Bugfix
5691 on 0.2.3.13-alpha; found and fixed by Gisle Vanem.
5692 - Fix compilation on platforms without unistd.h, or where environ
5693 is defined in stdlib.h. Fixes bug 5704; bugfix on 0.2.3.13-alpha.
5696 - Directory authorities are now a little more lenient at accepting
5697 older router descriptors, or newer router descriptors that don't
5698 make big changes. This should help ameliorate past and future
5699 issues where routers think they have uploaded valid descriptors,
5700 but the authorities don't think so. Fix for ticket 2479.
5701 - Make the code that clients use to detect an address change be
5702 IPv6-aware, so that it won't fill clients' logs with error
5703 messages when trying to get the IPv4 address of an IPv6
5704 connection. Implements ticket 5537.
5707 - Remove the GiveGuardFlagTo_CVE_2011_2768_VulnerableRelays option;
5708 authorities needed to use it for a while to keep the network working
5709 as people upgraded to 0.2.1.31, 0.2.2.34, or 0.2.3.6-alpha, but
5710 that was six months ago. As of now, it should no longer be needed
5714 Changes in version 0.2.3.14-alpha - 2012-04-23
5715 Tor 0.2.3.14-alpha fixes yet more bugs to get us closer to a release
5716 candidate. It also dramatically speeds up AES: fast relays should
5717 consider switching to the newer OpenSSL library.
5719 o Directory authority changes:
5720 - Change IP address for ides (v3 directory authority), and rename
5724 - Avoid logging uninitialized data when unable to decode a hidden
5725 service descriptor cookie. Fixes bug 5647; bugfix on 0.2.1.5-alpha.
5726 - Avoid a client-side assertion failure when receiving an INTRODUCE2
5727 cell on a general purpose circuit. Fixes bug 5644; bugfix on
5729 - If authorities are unable to get a v2 consensus document from other
5730 directory authorities, they no longer fall back to fetching
5731 them from regular directory caches. Fixes bug 5635; bugfix on
5732 0.2.2.26-beta, where routers stopped downloading v2 consensus
5734 - When we start a Tor client with a normal consensus already cached,
5735 be willing to download a microdescriptor consensus. Fixes bug 4011;
5736 fix on 0.2.3.1-alpha.
5738 o Major features (performance):
5739 - When built to use OpenSSL 1.0.1, and built for an x86 or x86_64
5740 instruction set, take advantage of OpenSSL's AESNI, bitsliced, or
5741 vectorized AES implementations as appropriate. These can be much,
5742 much faster than other AES implementations.
5744 o Minor bugfixes (0.2.2.x and earlier):
5745 - Don't launch more than 10 service-side introduction-point circuits
5746 for a hidden service in five minutes. Previously, we would consider
5747 launching more introduction-point circuits if at least one second
5748 had passed without any introduction-point circuits failing. Fixes
5749 bug 4607; bugfix on 0.0.7pre1.
5750 - Change the BridgePassword feature (part of the "bridge community"
5751 design, which is not yet implemented) to use a time-independent
5752 comparison. The old behavior might have allowed an adversary
5753 to use timing to guess the BridgePassword value. Fixes bug 5543;
5754 bugfix on 0.2.0.14-alpha.
5755 - Enforce correct return behavior of tor_vsscanf() when the '%%'
5756 pattern is used. Fixes bug 5558. Bugfix on 0.2.1.13.
5757 - When sending an HTTP/1.1 proxy request, include a Host header.
5758 Fixes bug 5593; bugfix on 0.2.2.1-alpha.
5759 - Don't log that we have "decided to publish new relay descriptor"
5760 unless we are actually publishing a descriptor. Fixes bug 3942;
5761 bugfix on 0.2.2.28-beta.
5763 o Minor bugfixes (0.2.3.x):
5764 - Fix a bug where a bridge authority crashes (on a failed assert)
5765 if it has seen no directory requests when it's time to write
5766 statistics to disk. Fixes bug 5508. Bugfix on 0.2.3.6-alpha.
5767 - Fix bug stomping on ORPort option NoListen and ignoring option
5768 NoAdvertise. Fixes bug 5151; bugfix on 0.2.3.9-alpha.
5769 - In the testsuite, provide a large enough buffer in the tor_sscanf
5770 unit test. Otherwise we'd overrun that buffer and crash during
5771 the unit tests. Found by weasel. Fixes bug 5449; bugfix on
5773 - Make sure we create the keys directory if it doesn't exist and we're
5774 about to store the dynamic Diffie-Hellman parameters. Fixes bug
5775 5572; bugfix on 0.2.3.13-alpha.
5776 - Fix a small memory leak when trying to decode incorrect base16
5777 authenticator during SAFECOOKIE authentication. Found by
5778 Coverity Scan. Fixes CID 507. Bugfix on 0.2.3.13-alpha.
5781 - Add more information to a log statement that might help track down
5782 bug 4091. If you're seeing "Bug: tor_addr_is_internal() called with a
5783 non-IP address" messages (or any Bug messages, for that matter!),
5784 please let us know about it.
5785 - Relays now understand an IPv6 address when they get one from a
5786 directory server. Resolves ticket 4875.
5787 - Resolve IPv6 addresses in bridge and entry statistics to country
5788 code "??" which means we at least count them. Resolves ticket 5053;
5789 improves on 0.2.3.9-alpha.
5790 - Update to the April 3 2012 Maxmind GeoLite Country database.
5791 - Begin a doc/state-contents.txt file to explain the contents of
5792 the Tor state file. Fixes bug 2987.
5794 o Default torrc changes:
5795 - Stop listing "socksport 9050" in torrc.sample. We open a socks
5796 port on 9050 by default anyway, so this should not change anything
5798 - Stop mentioning the deprecated *ListenAddress options in
5799 torrc.sample. Fixes bug 5438.
5800 - Document unit of bandwidth related options in sample torrc.
5804 - The "torify" script no longer supports the "tsocks" socksifier
5805 tool, since tsocks doesn't support DNS and UDP right for Tor.
5806 Everyone should be using torsocks instead. Fixes bugs 3530 and
5807 5180. Based on a patch by "ugh".
5810 - Change the symmetric cipher interface so that creating and
5811 initializing a stream cipher are no longer separate functions.
5812 - Remove all internal support for unpadded RSA. We never used it, and
5813 it would be a bad idea to start.
5816 Changes in version 0.2.3.13-alpha - 2012-03-26
5817 Tor 0.2.3.13-alpha fixes a variety of stability and correctness bugs
5818 in managed pluggable transports, as well as providing other cleanups
5819 that get us closer to a release candidate.
5821 o Directory authority changes:
5822 - Change IP address for maatuska (v3 directory authority).
5825 - Provide controllers with a safer way to implement the cookie
5826 authentication mechanism. With the old method, if another locally
5827 running program could convince a controller that it was the Tor
5828 process, then that program could trick the controller into telling
5829 it the contents of an arbitrary 32-byte file. The new "SAFECOOKIE"
5830 authentication method uses a challenge-response approach to prevent
5831 this attack. Fixes bug 5185, implements proposal 193.
5832 - Never use a bridge or a controller-supplied node as an exit, even
5833 if its exit policy allows it. Found by wanoskarnet. Fixes bug
5834 5342. Bugfix on 0.1.1.15-rc (for controller-purpose descriptors)
5835 and 0.2.0.3-alpha (for bridge-purpose descriptors).
5836 - Only build circuits if we have a sufficient threshold of the total
5837 descriptors that are marked in the consensus with the "Exit"
5838 flag. This mitigates an attack proposed by wanoskarnet, in which
5839 all of a client's bridges collude to restrict the exit nodes that
5840 the client knows about. Fixes bug 5343.
5842 o Major bugfixes (on Tor 0.2.3.x):
5843 - Avoid an assert when managed proxies like obfsproxy are configured,
5844 and we receive HUP signals or setconf attempts too rapidly. This
5845 situation happens most commonly when Vidalia tries to attach to
5846 Tor or tries to configure the Tor it's attached to. Fixes bug 5084;
5847 bugfix on 0.2.3.6-alpha.
5848 - Fix a relay-side pluggable transports bug where managed proxies were
5849 unreachable from the Internet, because Tor asked them to bind on
5850 localhost. Fixes bug 4725; bugfix on 0.2.3.9-alpha.
5851 - Stop discarding command-line arguments when TestingTorNetwork
5852 is set. Discovered by Kevin Bauer. Fixes bug 5373; bugfix on
5853 0.2.3.9-alpha, where task 4552 added support for two layers of
5855 - Resume allowing the unit tests to run in gdb. This was accidentally
5856 made impossible when the DisableDebuggerAttachment option was
5857 introduced. Fixes bug 5448; bugfix on 0.2.3.9-alpha.
5858 - Resume building with nat-pmp support. Fixes bug 4955; bugfix on
5859 0.2.3.11-alpha. Reported by Anthony G. Basile.
5861 o Minor bugfixes (on 0.2.2.x and earlier):
5862 - Ensure we don't cannibalize circuits that are longer than three hops
5863 already, so we don't end up making circuits with 5 or more
5864 hops. Patch contributed by wanoskarnet. Fixes bug 5231; bugfix on
5865 0.1.0.1-rc which introduced cannibalization.
5866 - Detect and reject certain misformed escape sequences in
5867 configuration values. Previously, these values would cause us
5868 to crash if received in a torrc file or over an authenticated
5869 control port. Bug found by Esteban Manchado Velázquez, and
5870 independently by Robert Connolly from Matta Consulting who further
5871 noted that it allows a post-authentication heap overflow. Patch
5872 by Alexander Schrijver. Fixes bugs 5090 and 5402 (CVE 2012-1668);
5873 bugfix on 0.2.0.16-alpha.
5874 - Fix a compile warning when using the --enable-openbsd-malloc
5875 configure option. Fixes bug 5340; bugfix on 0.2.0.20-rc.
5876 - Directory caches no longer refuse to clean out descriptors because
5877 of missing v2 networkstatus documents, unless they're configured
5878 to retrieve v2 networkstatus documents. Fixes bug 4838; bugfix on
5879 0.2.2.26-beta. Patch by Daniel Bryg.
5880 - Update to the latest version of the tinytest unit testing framework.
5881 This includes a couple of bugfixes that can be relevant for
5882 running forked unit tests on Windows, and removes all reserved
5885 o Minor bugfixes (on 0.2.3.x):
5886 - On a failed pipe() call, don't leak file descriptors. Fixes bug
5887 4296; bugfix on 0.2.3.1-alpha.
5888 - Spec conformance: on a v3 handshake, do not send a NETINFO cell
5889 until after we have received a CERTS cell. Fixes bug 4361; bugfix
5890 on 0.2.3.6-alpha. Patch by "frosty".
5891 - When binding to an IPv6 address, set the IPV6_V6ONLY socket
5892 option, so that the IP stack doesn't decide to use it for IPv4
5893 too. Fixes bug 4760; bugfix on 0.2.3.9-alpha.
5894 - Ensure that variables set in Tor's environment cannot override
5895 environment variables that Tor passes to a managed
5896 pluggable-transport proxy. Previously, Tor would pass every
5897 variable in its environment to managed proxies along with the new
5898 ones, in such a way that on many operating systems, the inherited
5899 environment variables would override those which Tor tried to
5900 explicitly set. Bugfix on 0.2.3.12-alpha for most Unixoid systems;
5901 bugfix on 0.2.3.9-alpha for Windows.
5904 - A wide variety of new unit tests by Esteban Manchado Velázquez.
5905 - Shorten links in the tor-exit-notice file. Patch by Christian Kujau.
5906 - Update to the March 6 2012 Maxmind GeoLite Country database.
5909 Changes in version 0.2.3.12-alpha - 2012-02-13
5910 Tor 0.2.3.12-alpha lets fast exit relays scale better, allows clients
5911 to use bridges that run Tor 0.2.2.x, and resolves several big bugs
5912 when Tor is configured to use a pluggable transport like obfsproxy.
5915 - Fix builds when the path to sed, openssl, or sha1sum contains
5916 spaces, which is pretty common on Windows. Fixes bug 5065; bugfix
5918 - Set the SO_REUSEADDR socket option before we call bind() on outgoing
5919 connections. This change should allow busy exit relays to stop
5920 running out of available sockets as quickly. Fixes bug 4950;
5921 bugfix on 0.2.2.26-beta.
5922 - Allow 0.2.3.x clients to use 0.2.2.x bridges. Previously the client
5923 would ask the bridge for microdescriptors, which are only supported
5924 in 0.2.3.x, and then fail to bootstrap when it didn't get the
5925 answers it wanted. Fixes bug 4013; bugfix on 0.2.3.2-alpha.
5926 - Properly set up obfsproxy's environment when in managed mode. The
5927 Tor Browser Bundle needs LD_LIBRARY_PATH to be passed to obfsproxy,
5928 and when you run your Tor as a daemon, there's no HOME. Fixes bugs
5929 5076 and 5082; bugfix on 0.2.3.6-alpha.
5932 - Use the dead_strip option when building Tor on OS X. This reduces
5933 binary size by almost 19% when linking openssl and libevent
5934 statically, which we do for Tor Browser Bundle.
5935 - Fix broken URLs in the sample torrc file, and tell readers about
5936 the OutboundBindAddress, ExitPolicyRejectPrivate, and
5937 PublishServerDescriptor options. Addresses bug 4652.
5938 - Update to the February 7 2012 Maxmind GeoLite Country database.
5941 - Downgrade the "We're missing a certificate" message from notice
5942 to info: people kept mistaking it for a real problem, whereas it
5943 is seldom the problem even when we are failing to bootstrap. Fixes
5944 bug 5067; bugfix on 0.2.0.10-alpha.
5945 - Don't put "TOR_PT_EXTENDED_SERVER_PORT=127.0.0.1:4200" in a
5946 managed pluggable transport server proxy's environment.
5947 Previously, we would put it there, even though Tor doesn't
5948 implement an 'extended server port' yet, and even though Tor
5949 almost certainly isn't listening at that address. For now, we set
5950 it to an empty string to avoid crashing older obfsproxies. Bugfix
5952 - Log the heartbeat message every HeartbeatPeriod seconds, not every
5953 HeartbeatPeriod + 1 seconds. Fixes bug 4942; bugfix on
5954 0.2.3.1-alpha. Bug reported by Scott Bennett.
5955 - Calculate absolute paths correctly on Windows. Fixes bug 4973;
5956 bugfix on 0.2.3.11-alpha.
5957 - Update "ClientOnly" man page entry to explain that there isn't
5958 really any point to messing with it. Resolves ticket 5005.
5959 - Use the correct CVE number for CVE-2011-4576 in our comments and
5960 log messages. Found by "fermenthor". Resolves bug 5066; bugfix on
5963 o Code simplifications and refactoring:
5964 - Use the _WIN32 macro throughout our code to detect Windows.
5965 (Previously we had used the obsolete 'WIN32' and the idiosyncratic
5969 Changes in version 0.2.3.11-alpha - 2012-01-22
5970 Tor 0.2.3.11-alpha marks feature-freeze for the 0.2.3 tree. It deploys
5971 the last step of the plan to limit maximum circuit length, includes
5972 a wide variety of hidden service performance and correctness fixes,
5973 works around an OpenSSL security flaw if your distro is too stubborn
5974 to upgrade, and fixes a bunch of smaller issues.
5977 - Now that Tor 0.2.0.x is completely deprecated, enable the final
5978 part of "Proposal 110: Avoiding infinite length circuits" by
5979 refusing all circuit-extend requests that do not use a relay_early
5980 cell. This change helps Tor resist a class of denial-of-service
5981 attacks by limiting the maximum circuit length.
5982 - Adjust the number of introduction points that a hidden service
5983 will try to maintain based on how long its introduction points
5984 remain in use and how many introductions they handle. Fixes
5986 - Try to use system facilities for enumerating local interface
5987 addresses, before falling back to our old approach (which was
5988 binding a UDP socket, and calling getsockname() on it). That
5989 approach was scaring OS X users whose draconian firewall
5990 software warned about binding to UDP sockets, regardless of
5991 whether packets were sent. Now we try to use getifaddrs(),
5992 SIOCGIFCONF, or GetAdaptersAddresses(), depending on what the
5993 system supports. Resolves ticket 1827.
5995 o Major security workaround:
5996 - When building or running with any version of OpenSSL earlier
5997 than 0.9.8s or 1.0.0f, disable SSLv3 support. These OpenSSL
5998 versions have a bug (CVE-2011-4576) in which their block cipher
5999 padding includes uninitialized data, potentially leaking sensitive
6000 information to any peer with whom they make a SSLv3 connection. Tor
6001 does not use SSL v3 by default, but a hostile client or server
6002 could force an SSLv3 connection in order to gain information that
6003 they shouldn't have been able to get. The best solution here is to
6004 upgrade to OpenSSL 0.9.8s or 1.0.0f (or later). But when building
6005 or running with a non-upgraded OpenSSL, we disable SSLv3 entirely
6006 to make sure that the bug can't happen.
6009 - Fix the SOCKET_OK test that we use to tell when socket
6010 creation fails so that it works on Win64. Fixes part of bug 4533;
6011 bugfix on 0.2.2.29-beta. Bug found by wanoskarnet.
6012 - Correct our replacements for the timeradd() and timersub() functions
6013 on platforms that lack them (for example, Windows). The timersub()
6014 function is used when expiring circuits, while timeradd() is
6015 currently unused. Bug report and patch by Vektor. Fixes bug 4778;
6016 bugfix on 0.2.2.24-alpha and 0.2.3.1-alpha.
6017 - Do not use OpenSSL 1.0.0's counter mode: it has a critical bug
6018 that was fixed in OpenSSL 1.0.0a. We test for the counter mode
6019 bug at runtime, not compile time, because some distributions hack
6020 their OpenSSL to mis-report its version. Fixes bug 4779; bugfix
6021 on 0.2.3.9-alpha. Found by Pascal.
6023 o Minor features (controller):
6024 - Use absolute path names when reporting the torrc filename in the
6025 control protocol, so a controller can more easily find the torrc
6026 file. Resolves bug 1101.
6027 - Extend the control protocol to report flags that control a circuit's
6028 path selection in CIRC events and in replies to 'GETINFO
6029 circuit-status'. Implements part of ticket 2411.
6030 - Extend the control protocol to report the hidden service address
6031 and current state of a hidden-service-related circuit in CIRC
6032 events and in replies to 'GETINFO circuit-status'. Implements part
6034 - When reporting the path to the cookie file to the controller,
6035 give an absolute path. Resolves ticket 4881.
6036 - Allow controllers to request an event notification whenever a
6037 circuit is cannibalized or its purpose is changed. Implements
6038 part of ticket 3457.
6039 - Include the creation time of a circuit in CIRC and CIRC2
6040 control-port events and the list produced by the 'GETINFO
6041 circuit-status' control-port command.
6043 o Minor features (directory authorities):
6044 - Directory authorities now reject versions of Tor older than
6045 0.2.1.30, and Tor versions between 0.2.2.1-alpha and 0.2.2.20-alpha
6046 inclusive. These versions accounted for only a small fraction of
6047 the Tor network, and have numerous known security issues. Resolves
6049 - Authority operators can now vote for all relays in a given
6050 set of countries to be BadDir/BadExit/Invalid/Rejected.
6051 - Provide two consensus parameters (FastFlagMinThreshold and
6052 FastFlagMaxThreshold) to control the range of allowable bandwidths
6053 for the Fast directory flag. These allow authorities to run
6054 experiments on appropriate requirements for being a "Fast" node.
6055 The AuthDirFastGuarantee config value still applies. Implements
6057 - Document the GiveGuardFlagTo_CVE_2011_2768_VulnerableRelays
6058 directory authority option (introduced in Tor 0.2.2.34).
6060 o Minor features (other):
6061 - Don't disable the DirPort when we cannot exceed our AccountingMax
6062 limit during this interval because the effective bandwidthrate is
6063 low enough. This is useful in a situation where AccountMax is only
6064 used as an additional safeguard or to provide statistics.
6065 - Prepend an informative header to generated dynamic_dh_params files.
6066 - If EntryNodes are given, but UseEntryGuards is set to 0, warn that
6067 EntryNodes will have no effect. Resolves issue 2571.
6068 - Log more useful messages when we fail to disable debugger
6070 - Log which authority we're missing votes from when we go to fetch
6071 them from the other auths.
6072 - Log (at debug level) whenever a circuit's purpose is changed.
6073 - Add missing documentation for the MaxClientCircuitsPending,
6074 UseMicrodescriptors, UserspaceIOCPBuffers, and
6075 _UseFilteringSSLBufferevents options, all introduced during
6077 - Update to the January 3 2012 Maxmind GeoLite Country database.
6079 o Minor bugfixes (hidden services):
6080 - Don't close hidden service client circuits which have almost
6081 finished connecting to their destination when they reach
6082 the normal circuit-build timeout. Previously, we would close
6083 introduction circuits which are waiting for an acknowledgement
6084 from the introduction point, and rendezvous circuits which have
6085 been specified in an INTRODUCE1 cell sent to a hidden service,
6086 after the normal CBT. Now, we mark them as 'timed out', and launch
6087 another rendezvous attempt in parallel. This behavior change can
6088 be disabled using the new CloseHSClientCircuitsImmediatelyOnTimeout
6089 option. Fixes part of bug 1297; bugfix on 0.2.2.2-alpha.
6090 - Don't close hidden-service-side rendezvous circuits when they
6091 reach the normal circuit-build timeout. This behavior change can
6092 be disabled using the new
6093 CloseHSServiceRendCircuitsImmediatelyOnTimeout option. Fixes the
6094 remaining part of bug 1297; bugfix on 0.2.2.2-alpha.
6095 - Make sure we never mark the wrong rendezvous circuit as having
6096 had its introduction cell acknowleged by the introduction-point
6097 relay. Previously, when we received an INTRODUCE_ACK cell on a
6098 client-side hidden-service introduction circuit, we might have
6099 marked a rendezvous circuit other than the one we specified in
6100 the INTRODUCE1 cell as INTRO_ACKED, which would have produced
6101 a warning message and interfered with the hidden service
6102 connection-establishment process. Fixes bug 4759; bugfix on
6103 0.2.3.3-alpha, when we added the stream-isolation feature which
6104 might cause Tor to open multiple rendezvous circuits for the same
6106 - Don't trigger an assertion failure when we mark a new client-side
6107 hidden-service introduction circuit for close during the process
6108 of creating it. Fixes bug 4796; bugfix on 0.2.3.6-alpha. Reported
6111 o Minor bugfixes (log messages):
6112 - Correctly spell "connect" in a log message on failure to create a
6113 controlsocket. Fixes bug 4803; bugfix on 0.2.2.26-beta and
6115 - Fix a typo in a log message in rend_service_rendezvous_has_opened().
6116 Fixes bug 4856; bugfix on Tor 0.0.6.
6117 - Fix the log message describing how we work around discovering
6118 that our version is the ill-fated OpenSSL 0.9.8l. Fixes bug
6119 4837; bugfix on 0.2.2.9-alpha.
6120 - When logging about a disallowed .exit name, do not also call it
6121 an "invalid onion address". Fixes bug 3325; bugfix on 0.2.2.9-alpha.
6123 o Minor bugfixes (build fixes):
6124 - During configure, detect when we're building with clang version
6125 3.0 or lower and disable the -Wnormalized=id and -Woverride-init
6126 CFLAGS. clang doesn't support them yet.
6127 - During configure, search for library containing cos function as
6128 libm lives in libcore on some platforms (BeOS/Haiku). Linking
6129 against libm was hard-coded before. Fixes the first part of bug
6130 4727; bugfix on 0.2.2.2-alpha. Patch and analysis by Martin Hebnes
6132 - Detect attempts to build Tor on (as yet hypothetical) versions
6133 of Windows where sizeof(intptr_t) != sizeof(SOCKET). Partial
6134 fix for bug 4533. Bugfix on 0.2.2.28-beta.
6135 - Preprocessor directives should not be put inside the arguments
6136 of a macro. This would break compilation with GCC releases prior
6137 to version 3.3. We would never recommend such an old GCC version,
6138 but it is apparently required for binary compatibility on some
6139 platforms (namely, certain builds of Haiku). Fixes the other part
6140 of bug 4727; bugfix on 0.2.3.3-alpha. Patch and analysis by Martin
6143 o Minor bugfixes (other):
6144 - Older Linux kernels erroneously respond to strange nmap behavior
6145 by having accept() return successfully with a zero-length
6146 socket. When this happens, just close the connection. Previously,
6147 we would try harder to learn the remote address: but there was
6148 no such remote address to learn, and our method for trying to
6149 learn it was incorrect. Fixes bugs 1240, 4745, and 4747. Bugfix
6150 on 0.1.0.3-rc. Reported and diagnosed by "r1eo".
6151 - Fix null-pointer access that could occur if TLS allocation failed.
6152 Fixes bug 4531; bugfix on 0.2.0.20-rc. Found by "troll_un". This was
6153 erroneously listed as fixed in 0.2.3.9-alpha, but the fix had
6154 accidentally been reverted.
6155 - Fix our implementation of crypto_random_hostname() so it can't
6156 overflow on ridiculously large inputs. (No Tor version has ever
6157 provided this kind of bad inputs, but let's be correct in depth.)
6158 Fixes bug 4413; bugfix on 0.2.2.9-alpha. Fix by Stephen Palmateer.
6159 - Find more places in the code that should have been testing for
6160 invalid sockets using the SOCKET_OK macro. Required for a fix
6161 for bug 4533. Bugfix on 0.2.2.28-beta.
6162 - Fix an assertion failure when, while running with bufferevents, a
6163 connection finishes connecting after it is marked for close, but
6164 before it is closed. Fixes bug 4697; bugfix on 0.2.3.1-alpha.
6165 - test_util_spawn_background_ok() hardcoded the expected value
6166 for ENOENT to 2. This isn't portable as error numbers are
6167 platform specific, and particularly the hurd has ENOENT at
6168 0x40000002. Construct expected string at runtime, using the correct
6169 value for ENOENT. Fixes bug 4733; bugfix on 0.2.3.1-alpha.
6170 - Reject attempts to disable DisableDebuggerAttachment while Tor is
6171 running. Fixes bug 4650; bugfix on 0.2.3.9-alpha.
6172 - Use an appropriate-width type for sockets in tor-fw-helper on
6173 win64. Fixes bug 1983 at last. Bugfix on 0.2.3.9-alpha.
6176 - When sending or relaying a RELAY_EARLY cell, we used to convert
6177 it to a RELAY cell if the connection was using the v1 link
6178 protocol. This was a workaround for older versions of Tor, which
6179 didn't handle RELAY_EARLY cells properly. Now that all supported
6180 versions can handle RELAY_EARLY cells, and now that we're enforcing
6181 the "no RELAY_EXTEND commands except in RELAY_EARLY cells" rule,
6182 remove this workaround. Addresses bug 4786.
6184 o Code simplifications and refactoring:
6185 - Use OpenSSL's built-in SSL_state_string_long() instead of our
6186 own homebrewed ssl_state_to_string() replacement. Patch from
6187 Emile Snyder. Fixes bug 4653.
6188 - Use macros to indicate OpenSSL versions, so we don't need to worry
6189 about accidental hexadecimal bit shifts.
6190 - Remove some workaround code for OpenSSL 0.9.6 (which is no longer
6192 - Convert more instances of tor_snprintf+tor_strdup into tor_asprintf.
6193 - Use the smartlist_add_asprintf() alias more consistently.
6194 - Use a TOR_INVALID_SOCKET macro when initializing a socket to an
6195 invalid value, rather than just -1.
6196 - Rename a handful of old identifiers, mostly related to crypto
6197 structures and crypto functions. By convention, our "create an
6198 object" functions are called "type_new()", our "free an object"
6199 functions are called "type_free()", and our types indicate that
6200 they are types only with a final "_t". But a handful of older
6201 types and functions broke these rules, with function names like
6202 "type_create" or "subsystem_op_type", or with type names like
6206 Changes in version 0.2.3.10-alpha - 2011-12-16
6207 Tor 0.2.3.10-alpha fixes a critical heap-overflow security issue in
6208 Tor's buffers code. Absolutely everybody should upgrade.
6210 The bug relied on an incorrect calculation when making data continuous
6211 in one of our IO buffers, if the first chunk of the buffer was
6212 misaligned by just the wrong amount. The miscalculation would allow an
6213 attacker to overflow a piece of heap-allocated memory. To mount this
6214 attack, the attacker would need to either open a SOCKS connection to
6215 Tor's SocksPort (usually restricted to localhost), or target a Tor
6216 instance configured to make its connections through a SOCKS proxy
6217 (which Tor does not do by default).
6219 Good security practice requires that all heap-overflow bugs should be
6220 presumed to be exploitable until proven otherwise, so we are treating
6221 this as a potential code execution attack. Please upgrade immediately!
6222 This bug does not affect bufferevents-based builds of Tor. Special
6223 thanks to "Vektor" for reporting this issue to us!
6225 This release also contains a few minor bugfixes for issues discovered
6229 - Fix a heap overflow bug that could occur when trying to pull
6230 data into the first chunk of a buffer, when that chunk had
6231 already had some data drained from it. Fixes CVE-2011-2778;
6232 bugfix on 0.2.0.16-alpha. Reported by "Vektor".
6235 - If we can't attach streams to a rendezvous circuit when we
6236 finish connecting to a hidden service, clear the rendezvous
6237 circuit's stream-isolation state and try to attach streams
6238 again. Previously, we cleared rendezvous circuits' isolation
6239 state either too early (if they were freshly built) or not at all
6240 (if they had been built earlier and were cannibalized). Bugfix on
6241 0.2.3.3-alpha; fixes bug 4655.
6242 - Fix compilation of the libnatpmp helper on non-Windows. Bugfix on
6243 0.2.3.9-alpha; fixes bug 4691. Reported by Anthony G. Basile.
6244 - Fix an assertion failure when a relay with accounting enabled
6245 starts up while dormant. Fixes bug 4702; bugfix on 0.2.3.9-alpha.
6248 - Update to the December 6 2011 Maxmind GeoLite Country database.
6251 Changes in version 0.2.2.35 - 2011-12-16
6252 Tor 0.2.2.35 fixes a critical heap-overflow security issue in Tor's
6253 buffers code. Absolutely everybody should upgrade.
6255 The bug relied on an incorrect calculation when making data continuous
6256 in one of our IO buffers, if the first chunk of the buffer was
6257 misaligned by just the wrong amount. The miscalculation would allow an
6258 attacker to overflow a piece of heap-allocated memory. To mount this
6259 attack, the attacker would need to either open a SOCKS connection to
6260 Tor's SocksPort (usually restricted to localhost), or target a Tor
6261 instance configured to make its connections through a SOCKS proxy
6262 (which Tor does not do by default).
6264 Good security practice requires that all heap-overflow bugs should be
6265 presumed to be exploitable until proven otherwise, so we are treating
6266 this as a potential code execution attack. Please upgrade immediately!
6267 This bug does not affect bufferevents-based builds of Tor. Special
6268 thanks to "Vektor" for reporting this issue to us!
6270 Tor 0.2.2.35 also fixes several bugs in previous versions, including
6271 crash bugs for unusual configurations, and a long-term bug that
6272 would prevent Tor from starting on Windows machines with draconian
6275 With this release, we remind everyone that 0.2.0.x has reached its
6276 formal end-of-life. Those Tor versions have many known flaws, and
6277 nobody should be using them. You should upgrade -- ideally to the
6278 0.2.2.x series. If you're using a Linux or BSD and its packages are
6279 obsolete, stop using those packages and upgrade anyway.
6281 The Tor 0.2.1.x series is also approaching its end-of-life: it will no
6282 longer receive support after some time in early 2012.
6285 - Fix a heap overflow bug that could occur when trying to pull
6286 data into the first chunk of a buffer, when that chunk had
6287 already had some data drained from it. Fixes CVE-2011-2778;
6288 bugfix on 0.2.0.16-alpha. Reported by "Vektor".
6289 - Initialize Libevent with the EVENT_BASE_FLAG_NOLOCK flag enabled, so
6290 that it doesn't attempt to allocate a socketpair. This could cause
6291 some problems on Windows systems with overzealous firewalls. Fix for
6292 bug 4457; workaround for Libevent versions 2.0.1-alpha through
6294 - If we mark an OR connection for close based on a cell we process,
6295 don't process any further cells on it. We already avoid further
6296 reads on marked-for-close connections, but now we also discard the
6297 cells we'd already read. Fixes bug 4299; bugfix on 0.2.0.10-alpha,
6298 which was the first version where we might mark a connection for
6299 close based on processing a cell on it.
6300 - Correctly sanity-check that we don't underflow on a memory
6301 allocation (and then assert) for hidden service introduction
6302 point decryption. Bug discovered by Dan Rosenberg. Fixes bug 4410;
6303 bugfix on 0.2.1.5-alpha.
6304 - Fix a memory leak when we check whether a hidden service
6305 descriptor has any usable introduction points left. Fixes bug
6306 4424. Bugfix on 0.2.2.25-alpha.
6307 - Don't crash when we're running as a relay and don't have a GeoIP
6308 file. Bugfix on 0.2.2.34; fixes bug 4340. This backports a fix
6309 we've had in the 0.2.3.x branch already.
6310 - When running as a client, do not print a misleading (and plain
6311 wrong) log message that we're collecting "directory request"
6312 statistics: clients don't collect statistics. Also don't create a
6313 useless (because empty) stats file in the stats/ directory. Fixes
6314 bug 4353; bugfix on 0.2.2.34.
6317 - Detect failure to initialize Libevent. This fix provides better
6318 detection for future instances of bug 4457.
6319 - Avoid frequent calls to the fairly expensive cull_wedged_cpuworkers
6320 function. This was eating up hideously large amounts of time on some
6321 busy servers. Fixes bug 4518; bugfix on 0.0.9.8.
6322 - Resolve an integer overflow bug in smartlist_ensure_capacity().
6323 Fixes bug 4230; bugfix on Tor 0.1.0.1-rc. Based on a patch by
6325 - Don't warn about unused log_mutex in log.c when building with
6326 --disable-threads using a recent GCC. Fixes bug 4437; bugfix on
6327 0.1.0.6-rc which introduced --disable-threads.
6328 - When configuring, starting, or stopping an NT service, stop
6329 immediately after the service configuration attempt has succeeded
6330 or failed. Fixes bug 3963; bugfix on 0.2.0.7-alpha.
6331 - When sending a NETINFO cell, include the original address
6332 received for the other side, not its canonical address. Found
6333 by "troll_un"; fixes bug 4349; bugfix on 0.2.0.10-alpha.
6334 - Fix a typo in a hibernation-related log message. Fixes bug 4331;
6335 bugfix on 0.2.2.23-alpha; found by "tmpname0901".
6336 - Fix a memory leak in launch_direct_bridge_descriptor_fetch() that
6337 occurred when a client tried to fetch a descriptor for a bridge
6338 in ExcludeNodes. Fixes bug 4383; bugfix on 0.2.2.25-alpha.
6339 - Backport fixes for a pair of compilation warnings on Windows.
6340 Fixes bug 4521; bugfix on 0.2.2.28-beta and on 0.2.2.29-beta.
6341 - If we had ever tried to call tor_addr_to_str on an address of
6342 unknown type, we would have done a strdup on an uninitialized
6343 buffer. Now we won't. Fixes bug 4529; bugfix on 0.2.1.3-alpha.
6344 Reported by "troll_un".
6345 - Correctly detect and handle transient lookup failures from
6346 tor_addr_lookup. Fixes bug 4530; bugfix on 0.2.1.5-alpha.
6347 Reported by "troll_un".
6348 - Fix null-pointer access that could occur if TLS allocation failed.
6349 Fixes bug 4531; bugfix on 0.2.0.20-rc. Found by "troll_un".
6350 - Use tor_socket_t type for listener argument to accept(). Fixes bug
6351 4535; bugfix on 0.2.2.28-beta. Found by "troll_un".
6354 - Add two new config options for directory authorities:
6355 AuthDirFastGuarantee sets a bandwidth threshold for guaranteeing the
6356 Fast flag, and AuthDirGuardBWGuarantee sets a bandwidth threshold
6357 that is always sufficient to satisfy the bandwidth requirement for
6358 the Guard flag. Now it will be easier for researchers to simulate
6359 Tor networks with different values. Resolves ticket 4484.
6360 - When Tor ignores a hidden service specified in its configuration,
6361 include the hidden service's directory in the warning message.
6362 Previously, we would only tell the user that some hidden service
6363 was ignored. Bugfix on 0.0.6; fixes bug 4426.
6364 - Update to the December 6 2011 Maxmind GeoLite Country database.
6366 o Packaging changes:
6367 - Make it easier to automate expert package builds on Windows,
6368 by removing an absolute path from makensis.exe command.
6371 Changes in version 0.2.1.32 - 2011-12-16
6372 Tor 0.2.1.32 backports important security and privacy fixes for
6373 oldstable. This release is intended only for package maintainers and
6374 others who cannot use the 0.2.2 stable series. All others should be
6375 using Tor 0.2.2.x or newer.
6377 The Tor 0.2.1.x series will reach formal end-of-life some time in
6378 early 2012; we will stop releasing patches for it then.
6380 o Major bugfixes (also included in 0.2.2.x):
6381 - Correctly sanity-check that we don't underflow on a memory
6382 allocation (and then assert) for hidden service introduction
6383 point decryption. Bug discovered by Dan Rosenberg. Fixes bug 4410;
6384 bugfix on 0.2.1.5-alpha.
6385 - Fix a heap overflow bug that could occur when trying to pull
6386 data into the first chunk of a buffer, when that chunk had
6387 already had some data drained from it. Fixes CVE-2011-2778;
6388 bugfix on 0.2.0.16-alpha. Reported by "Vektor".
6391 - Update to the December 6 2011 Maxmind GeoLite Country database.
6394 Changes in version 0.2.3.9-alpha - 2011-12-08
6395 Tor 0.2.3.9-alpha introduces initial IPv6 support for bridges, adds
6396 a "DisableNetwork" security feature that bundles can use to avoid
6397 touching the network until bridges are configured, moves forward on
6398 the pluggable transport design, fixes a flaw in the hidden service
6399 design that unnecessarily prevented clients with wrong clocks from
6400 reaching hidden services, and fixes a wide variety of other issues.
6403 - Clients can now connect to private bridges over IPv6. Bridges
6404 still need at least one IPv4 address in order to connect to
6405 other relays. Note that we don't yet handle the case where the
6406 user has two bridge lines for the same bridge (one IPv4, one
6407 IPv6). Implements parts of proposal 186.
6408 - New "DisableNetwork" config option to prevent Tor from launching any
6409 connections or accepting any connections except on a control port.
6410 Bundles and controllers can set this option before letting Tor talk
6411 to the rest of the network, for example to prevent any connections
6412 to a non-bridge address. Packages like Orbot can also use this
6413 option to instruct Tor to save power when the network is off.
6414 - Clients and bridges can now be configured to use a separate
6415 "transport" proxy. This approach makes the censorship arms race
6416 easier by allowing bridges to use protocol obfuscation plugins. It
6417 implements the "managed proxy" part of proposal 180 (ticket 3472).
6418 - When using OpenSSL 1.0.0 or later, use OpenSSL's counter mode
6419 implementation. It makes AES_CTR about 7% faster than our old one
6420 (which was about 10% faster than the one OpenSSL used to provide).
6421 Resolves ticket 4526.
6422 - Add a "tor2web mode" for clients that want to connect to hidden
6423 services non-anonymously (and possibly more quickly). As a safety
6424 measure to try to keep users from turning this on without knowing
6425 what they are doing, tor2web mode must be explicitly enabled at
6426 compile time, and a copy of Tor compiled to run in tor2web mode
6427 cannot be used as a normal Tor client. Implements feature 2553.
6428 - Add experimental support for running on Windows with IOCP and no
6429 kernel-space socket buffers. This feature is controlled by a new
6430 "UserspaceIOCPBuffers" config option (off by default), which has
6431 no effect unless Tor has been built with support for bufferevents,
6432 is running on Windows, and has enabled IOCP. This may, in the long
6433 run, help solve or mitigate bug 98.
6434 - Use a more secure consensus parameter voting algorithm. Now at
6435 least three directory authorities or a majority of them must
6436 vote on a given parameter before it will be included in the
6437 consensus. Implements proposal 178.
6440 - Hidden services now ignore the timestamps on INTRODUCE2 cells.
6441 They used to check that the timestamp was within 30 minutes
6442 of their system clock, so they could cap the size of their
6443 replay-detection cache, but that approach unnecessarily refused
6444 service to clients with wrong clocks. Bugfix on 0.2.1.6-alpha, when
6445 the v3 intro-point protocol (the first one which sent a timestamp
6446 field in the INTRODUCE2 cell) was introduced; fixes bug 3460.
6447 - Only use the EVP interface when AES acceleration is enabled,
6448 to avoid a 5-7% performance regression. Resolves issue 4525;
6449 bugfix on 0.2.3.8-alpha.
6451 o Privacy/anonymity features (bridge detection):
6452 - Make bridge SSL certificates a bit more stealthy by using random
6453 serial numbers, in the same fashion as OpenSSL when generating
6454 self-signed certificates. Implements ticket 4584.
6455 - Introduce a new config option "DynamicDHGroups", enabled by
6456 default, which provides each bridge with a unique prime DH modulus
6457 to be used during SSL handshakes. This option attempts to help
6458 against censors who might use the Apache DH modulus as a static
6459 identifier for bridges. Addresses ticket 4548.
6461 o Minor features (new/different config options):
6462 - New configuration option "DisableDebuggerAttachment" (on by default)
6463 to prevent basic debugging attachment attempts by other processes.
6464 Supports Mac OS X and Gnu/Linux. Resolves ticket 3313.
6465 - Allow MapAddress directives to specify matches against super-domains,
6466 as in "MapAddress *.torproject.org *.torproject.org.torserver.exit".
6467 Implements issue 933.
6468 - Slightly change behavior of "list" options (that is, config
6469 options that can appear more than once) when they appear both in
6470 torrc and on the command line. Previously, the command-line options
6471 would be appended to the ones from torrc. Now, the command-line
6472 options override the torrc options entirely. This new behavior
6473 allows the user to override list options (like exit policies and
6474 ports to listen on) from the command line, rather than simply
6475 appending to the list.
6476 - You can get the old (appending) command-line behavior for "list"
6477 options by prefixing the option name with a "+".
6478 - You can remove all the values for a "list" option from the command
6479 line without adding any new ones by prefixing the option name
6481 - Add experimental support for a "defaults" torrc file to be parsed
6482 before the regular torrc. Torrc options override the defaults file's
6483 options in the same way that the command line overrides the torrc.
6484 The SAVECONF controller command saves only those options which
6485 differ between the current configuration and the defaults file. HUP
6486 reloads both files. (Note: This is an experimental feature; its
6487 behavior will probably be refined in future 0.2.3.x-alpha versions
6488 to better meet packagers' needs.) Implements task 4552.
6491 - Try to make the introductory warning message that Tor prints on
6492 startup more useful for actually finding help and information.
6493 Resolves ticket 2474.
6494 - Running "make version" now displays the version of Tor that
6495 we're about to build. Idea from katmagic; resolves issue 4400.
6496 - Expire old or over-used hidden service introduction points.
6497 Required by fix for bug 3460.
6498 - Move the replay-detection cache for the RSA-encrypted parts of
6499 INTRODUCE2 cells to the introduction point data structures.
6500 Previously, we would use one replay-detection cache per hidden
6501 service. Required by fix for bug 3460.
6502 - Reduce the lifetime of elements of hidden services' Diffie-Hellman
6503 public key replay-detection cache from 60 minutes to 5 minutes. This
6504 replay-detection cache is now used only to detect multiple
6505 INTRODUCE2 cells specifying the same rendezvous point, so we can
6506 avoid launching multiple simultaneous attempts to connect to it.
6508 o Minor bugfixes (on Tor 0.2.2.x and earlier):
6509 - Resolve an integer overflow bug in smartlist_ensure_capacity().
6510 Fixes bug 4230; bugfix on Tor 0.1.0.1-rc. Based on a patch by
6512 - Fix a minor formatting issue in one of tor-gencert's error messages.
6514 - Prevent a false positive from the check-spaces script, by disabling
6515 the "whitespace between function name and (" check for functions
6517 - Fix a log message suggesting that people contact a non-existent
6518 email address. Fixes bug 3448.
6519 - Fix null-pointer access that could occur if TLS allocation failed.
6520 Fixes bug 4531; bugfix on 0.2.0.20-rc. Found by "troll_un".
6521 - Report a real bootstrap problem to the controller on router
6522 identity mismatch. Previously we just said "foo", which probably
6523 made a lot of sense at the time. Fixes bug 4169; bugfix on
6525 - If we had ever tried to call tor_addr_to_str() on an address of
6526 unknown type, we would have done a strdup() on an uninitialized
6527 buffer. Now we won't. Fixes bug 4529; bugfix on 0.2.1.3-alpha.
6528 Reported by "troll_un".
6529 - Correctly detect and handle transient lookup failures from
6530 tor_addr_lookup(). Fixes bug 4530; bugfix on 0.2.1.5-alpha.
6531 Reported by "troll_un".
6532 - Use tor_socket_t type for listener argument to accept(). Fixes bug
6533 4535; bugfix on 0.2.2.28-beta. Found by "troll_un".
6534 - Initialize conn->addr to a valid state in spawn_cpuworker(). Fixes
6535 bug 4532; found by "troll_un".
6537 o Minor bugfixes (on Tor 0.2.3.x):
6538 - Fix a compile warning in tor_inet_pton(). Bugfix on 0.2.3.8-alpha;
6540 - Don't send two ESTABLISH_RENDEZVOUS cells when opening a new
6541 circuit for use as a hidden service client's rendezvous point.
6542 Fixes bugs 4641 and 4171; bugfix on 0.2.3.3-alpha. Diagnosed
6543 with help from wanoskarnet.
6544 - Restore behavior of overriding SocksPort, ORPort, and similar
6545 options from the command line. Bugfix on 0.2.3.3-alpha.
6548 - Properly handle the case where the build-tree is not the same
6549 as the source tree when generating src/common/common_sha1.i,
6550 src/or/micro-revision.i, and src/or/or_sha1.i. Fixes bug 3953;
6551 bugfix on 0.2.0.1-alpha.
6553 o Code simplifications, cleanups, and refactorings:
6554 - Remove the pure attribute from all functions that used it
6555 previously. In many cases we assigned it incorrectly, because the
6556 functions might assert or call impure functions, and we don't have
6557 evidence that keeping the pure attribute is worthwhile. Implements
6558 changes suggested in ticket 4421.
6559 - Remove some dead code spotted by coverity. Fixes cid 432.
6560 Bugfix on 0.2.3.1-alpha, closes bug 4637.
6563 Changes in version 0.2.3.8-alpha - 2011-11-22
6564 Tor 0.2.3.8-alpha fixes some crash and assert bugs, including a
6565 socketpair-related bug that has been bothering Windows users. It adds
6566 support to serve microdescriptors to controllers, so Vidalia's network
6567 map can resume listing relays (once Vidalia implements its side),
6568 and adds better support for hardware AES acceleration. Finally, it
6569 starts the process of adjusting the bandwidth cutoff for getting the
6570 "Fast" flag from 20KB to (currently) 32KB -- preliminary results show
6571 that tiny relays harm performance more than they help network capacity.
6574 - Initialize Libevent with the EVENT_BASE_FLAG_NOLOCK flag enabled, so
6575 that it doesn't attempt to allocate a socketpair. This could cause
6576 some problems on Windows systems with overzealous firewalls. Fix for
6577 bug 4457; workaround for Libevent versions 2.0.1-alpha through
6579 - Correctly sanity-check that we don't underflow on a memory
6580 allocation (and then assert) for hidden service introduction
6581 point decryption. Bug discovered by Dan Rosenberg. Fixes bug 4410;
6582 bugfix on 0.2.1.5-alpha.
6583 - Remove the artificially low cutoff of 20KB to guarantee the Fast
6584 flag. In the past few years the average relay speed has picked
6585 up, and while the "top 7/8 of the network get the Fast flag" and
6586 "all relays with 20KB or more of capacity get the Fast flag" rules
6587 used to have the same result, now the top 7/8 of the network has
6588 a capacity more like 32KB. Bugfix on 0.2.1.14-rc. Fixes bug 4489.
6589 - Fix a rare assertion failure when checking whether a v0 hidden
6590 service descriptor has any usable introduction points left, and
6591 we don't have enough information to build a circuit to the first
6592 intro point named in the descriptor. The HS client code in
6593 0.2.3.x no longer uses v0 HS descriptors, but this assertion can
6594 trigger on (and crash) v0 HS authorities. Fixes bug 4411.
6595 Bugfix on 0.2.3.1-alpha; diagnosed by frosty_un.
6596 - Make bridge authorities not crash when they are asked for their own
6597 descriptor. Bugfix on 0.2.3.7-alpha, reported by Lucky Green.
6598 - When running as a client, do not print a misleading (and plain
6599 wrong) log message that we're collecting "directory request"
6600 statistics: clients don't collect statistics. Also don't create a
6601 useless (because empty) stats file in the stats/ directory. Fixes
6602 bug 4353; bugfix on 0.2.2.34 and 0.2.3.7-alpha.
6605 - Allow Tor controllers like Vidalia to obtain the microdescriptor
6606 for a relay by identity digest or nickname. Previously,
6607 microdescriptors were only available by their own digests, so a
6608 controller would have to ask for and parse the whole microdescriptor
6609 consensus in order to look up a single relay's microdesc. Fixes
6610 bug 3832; bugfix on 0.2.3.1-alpha.
6611 - Use OpenSSL's EVP interface for AES encryption, so that all AES
6612 operations can use hardware acceleration (if present). Resolves
6615 o Minor bugfixes (on 0.2.2.x and earlier):
6616 - Detect failure to initialize Libevent. This fix provides better
6617 detection for future instances of bug 4457.
6618 - Avoid frequent calls to the fairly expensive cull_wedged_cpuworkers
6619 function. This was eating up hideously large amounts of time on some
6620 busy servers. Fixes bug 4518; bugfix on 0.0.9.8.
6621 - Don't warn about unused log_mutex in log.c when building with
6622 --disable-threads using a recent GCC. Fixes bug 4437; bugfix on
6623 0.1.0.6-rc which introduced --disable-threads.
6624 - Allow manual 'authenticate' commands to the controller interface
6625 from netcat (nc) as well as telnet. We were rejecting them because
6626 they didn't come with the expected whitespace at the end of the
6627 command. Bugfix on 0.1.1.1-alpha; fixes bug 2893.
6628 - Fix some (not actually triggerable) buffer size checks in usage of
6629 tor_inet_ntop. Fixes bug 4434; bugfix on Tor 0.2.0.1-alpha. Patch
6631 - Fix parsing of some corner-cases with tor_inet_pton(). Fixes
6632 bug 4515; bugfix on 0.2.0.1-alpha; fix by Anders Sundman.
6633 - When configuring, starting, or stopping an NT service, stop
6634 immediately after the service configuration attempt has succeeded
6635 or failed. Fixes bug 3963; bugfix on 0.2.0.7-alpha.
6636 - When sending a NETINFO cell, include the original address
6637 received for the other side, not its canonical address. Found
6638 by "troll_un"; fixes bug 4349; bugfix on 0.2.0.10-alpha.
6639 - Rename the bench_{aes,dmap} functions to test_*, so that tinytest
6640 can pick them up when the tests aren't disabled. Bugfix on
6641 0.2.2.4-alpha which introduced tinytest.
6642 - Fix a memory leak when we check whether a hidden service
6643 descriptor has any usable introduction points left. Fixes bug
6644 4424. Bugfix on 0.2.2.25-alpha.
6645 - Fix a memory leak in launch_direct_bridge_descriptor_fetch() that
6646 occurred when a client tried to fetch a descriptor for a bridge
6647 in ExcludeNodes. Fixes bug 4383; bugfix on 0.2.2.25-alpha.
6649 o Minor bugfixes (on 0.2.3.x):
6650 - Make util unit tests build correctly with MSVC. Bugfix on
6651 0.2.3.3-alpha. Patch by Gisle Vanem.
6652 - Successfully detect AUTH_CHALLENGE cells with no recognized
6653 authentication type listed. Fixes bug 4367; bugfix on 0.2.3.6-alpha.
6655 - If a relay receives an AUTH_CHALLENGE cell it can't answer,
6656 it should still send a NETINFO cell to allow the connection to
6657 become open. Fixes bug 4368; fix on 0.2.3.6-alpha; bug found by
6659 - Log less loudly when we get an invalid authentication certificate
6660 from a source other than a directory authority: it's not unusual
6661 to see invalid certs because of clock skew. Fixes bug 4370; bugfix
6663 - Tolerate servers with more clock skew in their authentication
6664 certificates than previously. Fixes bug 4371; bugfix on
6666 - Fix a couple of compile warnings on Windows. Fixes bug 4469; bugfix
6667 on 0.2.3.4-alpha and 0.2.3.6-alpha.
6670 - Add two new config options for directory authorities:
6671 AuthDirFastGuarantee sets a bandwidth threshold for guaranteeing the
6672 Fast flag, and AuthDirGuardBWGuarantee sets a bandwidth threshold
6673 that is always sufficient to satisfy the bandwidth requirement for
6674 the Guard flag. Now it will be easier for researchers to simulate
6675 Tor networks with different values. Resolves ticket 4484.
6676 - When Tor ignores a hidden service specified in its configuration,
6677 include the hidden service's directory in the warning message.
6678 Previously, we would only tell the user that some hidden service
6679 was ignored. Bugfix on 0.0.6; fixes bug 4426.
6680 - When we fail to initialize Libevent, retry with IOCP disabled so we
6681 don't need to turn on multi-threading support in Libevent, which in
6682 turn requires a working socketpair(). This is a workaround for bug
6683 4457, which affects Libevent versions from 2.0.1-alpha through
6685 - Detect when we try to build on a platform that doesn't define
6686 AF_UNSPEC to 0. We don't work there, so refuse to compile.
6687 - Update to the November 1 2011 Maxmind GeoLite Country database.
6689 o Packaging changes:
6690 - Make it easier to automate expert package builds on Windows,
6691 by removing an absolute path from makensis.exe command.
6693 o Code simplifications and refactoring:
6694 - Remove some redundant #include directives throughout the code.
6695 Patch from Andrea Gelmini.
6696 - Unconditionally use OpenSSL's AES implementation instead of our
6697 old built-in one. OpenSSL's AES has been better for a while, and
6698 relatively few servers should still be on any version of OpenSSL
6699 that doesn't have good optimized assembly AES.
6700 - Use the name "CERTS" consistently to refer to the new cell type;
6701 we were calling it CERT in some places and CERTS in others.
6704 - Numerous new unit tests for functions in util.c and address.c by
6706 - The long-disabled benchmark tests are now split into their own
6707 ./src/test/bench binary.
6708 - The benchmark tests can now use more accurate timers than
6709 gettimeofday() when such timers are available.
6712 Changes in version 0.2.3.7-alpha - 2011-10-30
6713 Tor 0.2.3.7-alpha fixes a crash bug in 0.2.3.6-alpha introduced by
6714 the new v3 handshake. It also resolves yet another bridge address
6718 - If we mark an OR connection for close based on a cell we process,
6719 don't process any further cells on it. We already avoid further
6720 reads on marked-for-close connections, but now we also discard the
6721 cells we'd already read. Fixes bug 4299; bugfix on 0.2.0.10-alpha,
6722 which was the first version where we might mark a connection for
6723 close based on processing a cell on it.
6724 - Fix a double-free bug that would occur when we received an invalid
6725 certificate in a CERT cell in the new v3 handshake. Fixes bug 4343;
6726 bugfix on 0.2.3.6-alpha.
6727 - Bridges no longer include their address in NETINFO cells on outgoing
6728 OR connections, to allow them to blend in better with clients.
6729 Removes another avenue for enumerating bridges. Reported by
6730 "troll_un". Fixes bug 4348; bugfix on 0.2.0.10-alpha, when NETINFO
6731 cells were introduced.
6734 - Fixed a typo in a hibernation-related log message. Fixes bug 4331;
6735 bugfix on 0.2.2.23-alpha; found by "tmpname0901".
6738 Changes in version 0.2.3.6-alpha - 2011-10-26
6739 Tor 0.2.3.6-alpha includes the fix from 0.2.2.34 for a critical
6740 anonymity vulnerability where an attacker can deanonymize Tor
6741 users. Everybody should upgrade.
6743 This release also features support for a new v3 connection handshake
6744 protocol, and fixes to make hidden service connections more robust.
6747 - Implement a new handshake protocol (v3) for authenticating Tors to
6748 each other over TLS. It should be more resistant to fingerprinting
6749 than previous protocols, and should require less TLS hacking for
6750 future Tor implementations. Implements proposal 176.
6751 - Allow variable-length padding cells to disguise the length of
6752 Tor's TLS records. Implements part of proposal 184.
6754 o Privacy/anonymity fixes (clients):
6755 - Clients and bridges no longer send TLS certificate chains on
6756 outgoing OR connections. Previously, each client or bridge would
6757 use the same cert chain for all outgoing OR connections until
6758 its IP address changes, which allowed any relay that the client
6759 or bridge contacted to determine which entry guards it is using.
6760 Fixes CVE-2011-2768. Bugfix on 0.0.9pre5; found by "frosty_un".
6761 - If a relay receives a CREATE_FAST cell on a TLS connection, it
6762 no longer considers that connection as suitable for satisfying a
6763 circuit EXTEND request. Now relays can protect clients from the
6764 CVE-2011-2768 issue even if the clients haven't upgraded yet.
6765 - Directory authorities no longer assign the Guard flag to relays
6766 that haven't upgraded to the above "refuse EXTEND requests
6767 to client connections" fix. Now directory authorities can
6768 protect clients from the CVE-2011-2768 issue even if neither
6769 the clients nor the relays have upgraded yet. There's a new
6770 "GiveGuardFlagTo_CVE_2011_2768_VulnerableRelays" config option
6771 to let us transition smoothly, else tomorrow there would be no
6774 o Major bugfixes (hidden services):
6775 - Improve hidden service robustness: when an attempt to connect to
6776 a hidden service ends, be willing to refetch its hidden service
6777 descriptors from each of the HSDir relays responsible for them
6778 immediately. Previously, we would not consider refetching the
6779 service's descriptors from each HSDir for 15 minutes after the last
6780 fetch, which was inconvenient if the hidden service was not running
6781 during the first attempt. Bugfix on 0.2.0.18-alpha; fixes bug 3335.
6782 - When one of a hidden service's introduction points appears to be
6783 unreachable, stop trying it. Previously, we would keep trying
6784 to build circuits to the introduction point until we lost the
6785 descriptor, usually because the user gave up and restarted Tor.
6786 Partly fixes bug 3825.
6787 - Don't launch a useless circuit after failing to use one of a
6788 hidden service's introduction points. Previously, we would
6789 launch a new introduction circuit, but not set the hidden service
6790 which that circuit was intended to connect to, so it would never
6791 actually be used. A different piece of code would then create a
6792 new introduction circuit correctly. Bug reported by katmagic and
6793 found by Sebastian Hahn. Bugfix on 0.2.1.13-alpha; fixes bug 4212.
6795 o Major bugfixes (other):
6796 - Bridges now refuse CREATE or CREATE_FAST cells on OR connections
6797 that they initiated. Relays could distinguish incoming bridge
6798 connections from client connections, creating another avenue for
6799 enumerating bridges. Fixes CVE-2011-2769. Bugfix on 0.2.0.3-alpha.
6800 Found by "frosty_un".
6801 - Don't update the AccountingSoftLimitHitAt state file entry whenever
6802 tor gets started. This prevents a wrong average bandwidth
6803 estimate, which would cause relays to always start a new accounting
6804 interval at the earliest possible moment. Fixes bug 2003; bugfix
6805 on 0.2.2.7-alpha. Reported by BryonEldridge, who also helped
6806 immensely in tracking this bug down.
6807 - Fix a crash bug when changing node restrictions while a DNS lookup
6808 is in-progress. Fixes bug 4259; bugfix on 0.2.2.25-alpha. Bugfix
6811 o Minor bugfixes (on 0.2.2.x and earlier):
6812 - When a hidden service turns an extra service-side introduction
6813 circuit into a general-purpose circuit, free the rend_data and
6814 intro_key fields first, so we won't leak memory if the circuit
6815 is cannibalized for use as another service-side introduction
6816 circuit. Bugfix on 0.2.1.7-alpha; fixes bug 4251.
6817 - Rephrase the log message emitted if the TestSocks check is
6818 successful. Patch from Fabian Keil; fixes bug 4094.
6819 - Bridges now skip DNS self-tests, to act a little more stealthily.
6820 Fixes bug 4201; bugfix on 0.2.0.3-alpha, which first introduced
6821 bridges. Patch by "warms0x".
6822 - Remove a confusing dollar sign from the example fingerprint in the
6823 man page, and also make the example fingerprint a valid one. Fixes
6824 bug 4309; bugfix on 0.2.1.3-alpha.
6825 - Fix internal bug-checking logic that was supposed to catch
6826 failures in digest generation so that it will fail more robustly
6827 if we ask for a nonexistent algorithm. Found by Coverity Scan.
6828 Bugfix on 0.2.2.1-alpha; fixes Coverity CID 479.
6829 - Report any failure in init_keys() calls launched because our
6830 IP address has changed. Spotted by Coverity Scan. Bugfix on
6831 0.1.1.4-alpha; fixes CID 484.
6833 o Minor bugfixes (on 0.2.3.x):
6834 - Fix a bug in configure.in that kept it from building a configure
6835 script with autoconf versions earlier than 2.61. Fixes bug 2430;
6836 bugfix on 0.2.3.1-alpha.
6837 - Don't warn users that they are exposing a client port to the
6838 Internet if they have specified an RFC1918 address. Previously,
6839 we would warn if the user had specified any non-loopback
6840 address. Bugfix on 0.2.3.3-alpha. Fixes bug 4018; reported by Tas.
6841 - Fix memory leaks in the failing cases of the new SocksPort and
6842 ControlPort code. Found by Coverity Scan. Bugfix on 0.2.3.3-alpha;
6843 fixes coverity CIDs 485, 486, and 487.
6846 - When a hidden service's introduction point times out, consider
6847 trying it again during the next attempt to connect to the
6848 HS. Previously, we would not try it again unless a newly fetched
6849 descriptor contained it. Required by fixes for bugs 1297 and 3825.
6850 - The next version of Windows will be called Windows 8, and it has
6851 a major version of 6, minor version of 2. Correctly identify that
6852 version instead of calling it "Very recent version". Resolves
6853 ticket 4153; reported by funkstar.
6854 - The Bridge Authority now writes statistics on how many bridge
6855 descriptors it gave out in total, and how many unique descriptors
6856 it gave out. It also lists how often the most and least commonly
6857 fetched descriptors were given out, as well as the median and
6858 25th/75th percentile. Implements tickets 4200 and 4294.
6859 - Update to the October 4 2011 Maxmind GeoLite Country database.
6861 o Code simplifications and refactoring:
6862 - Remove some old code to remember statistics about which descriptors
6863 we've served as a directory mirror. The feature wasn't used and
6864 is outdated now that microdescriptors are around.
6865 - Rename Tor functions that turn strings into addresses, so that
6866 "parse" indicates that no hostname resolution occurs, and
6867 "lookup" indicates that hostname resolution may occur. This
6868 should help prevent mistakes in the future. Fixes bug 3512.
6871 Changes in version 0.2.2.34 - 2011-10-26
6872 Tor 0.2.2.34 fixes a critical anonymity vulnerability where an attacker
6873 can deanonymize Tor users. Everybody should upgrade.
6875 The attack relies on four components: 1) Clients reuse their TLS cert
6876 when talking to different relays, so relays can recognize a user by
6877 the identity key in her cert. 2) An attacker who knows the client's
6878 identity key can probe each guard relay to see if that identity key
6879 is connected to that guard relay right now. 3) A variety of active
6880 attacks in the literature (starting from "Low-Cost Traffic Analysis
6881 of Tor" by Murdoch and Danezis in 2005) allow a malicious website to
6882 discover the guard relays that a Tor user visiting the website is using.
6883 4) Clients typically pick three guards at random, so the set of guards
6884 for a given user could well be a unique fingerprint for her. This
6885 release fixes components #1 and #2, which is enough to block the attack;
6886 the other two remain as open research problems. Special thanks to
6887 "frosty_un" for reporting the issue to us!
6889 Clients should upgrade so they are no longer recognizable by the TLS
6890 certs they present. Relays should upgrade so they no longer allow a
6891 remote attacker to probe them to test whether unpatched clients are
6892 currently connected to them.
6894 This release also fixes several vulnerabilities that allow an attacker
6895 to enumerate bridge relays. Some bridge enumeration attacks still
6896 remain; see for example proposal 188.
6898 o Privacy/anonymity fixes (clients):
6899 - Clients and bridges no longer send TLS certificate chains on
6900 outgoing OR connections. Previously, each client or bridge would
6901 use the same cert chain for all outgoing OR connections until
6902 its IP address changes, which allowed any relay that the client
6903 or bridge contacted to determine which entry guards it is using.
6904 Fixes CVE-2011-2768. Bugfix on 0.0.9pre5; found by "frosty_un".
6905 - If a relay receives a CREATE_FAST cell on a TLS connection, it
6906 no longer considers that connection as suitable for satisfying a
6907 circuit EXTEND request. Now relays can protect clients from the
6908 CVE-2011-2768 issue even if the clients haven't upgraded yet.
6909 - Directory authorities no longer assign the Guard flag to relays
6910 that haven't upgraded to the above "refuse EXTEND requests
6911 to client connections" fix. Now directory authorities can
6912 protect clients from the CVE-2011-2768 issue even if neither
6913 the clients nor the relays have upgraded yet. There's a new
6914 "GiveGuardFlagTo_CVE_2011_2768_VulnerableRelays" config option
6915 to let us transition smoothly, else tomorrow there would be no
6918 o Privacy/anonymity fixes (bridge enumeration):
6919 - Bridge relays now do their directory fetches inside Tor TLS
6920 connections, like all the other clients do, rather than connecting
6921 directly to the DirPort like public relays do. Removes another
6922 avenue for enumerating bridges. Fixes bug 4115; bugfix on 0.2.0.35.
6923 - Bridges relays now build circuits for themselves in a more similar
6924 way to how clients build them. Removes another avenue for
6925 enumerating bridges. Fixes bug 4124; bugfix on 0.2.0.3-alpha,
6926 when bridges were introduced.
6927 - Bridges now refuse CREATE or CREATE_FAST cells on OR connections
6928 that they initiated. Relays could distinguish incoming bridge
6929 connections from client connections, creating another avenue for
6930 enumerating bridges. Fixes CVE-2011-2769. Bugfix on 0.2.0.3-alpha.
6931 Found by "frosty_un".
6934 - Fix a crash bug when changing node restrictions while a DNS lookup
6935 is in-progress. Fixes bug 4259; bugfix on 0.2.2.25-alpha. Bugfix
6937 - Don't launch a useless circuit after failing to use one of a
6938 hidden service's introduction points. Previously, we would
6939 launch a new introduction circuit, but not set the hidden service
6940 which that circuit was intended to connect to, so it would never
6941 actually be used. A different piece of code would then create a
6942 new introduction circuit correctly. Bug reported by katmagic and
6943 found by Sebastian Hahn. Bugfix on 0.2.1.13-alpha; fixes bug 4212.
6946 - Change an integer overflow check in the OpenBSD_Malloc code so
6947 that GCC is less likely to eliminate it as impossible. Patch
6948 from Mansour Moufid. Fixes bug 4059.
6949 - When a hidden service turns an extra service-side introduction
6950 circuit into a general-purpose circuit, free the rend_data and
6951 intro_key fields first, so we won't leak memory if the circuit
6952 is cannibalized for use as another service-side introduction
6953 circuit. Bugfix on 0.2.1.7-alpha; fixes bug 4251.
6954 - Bridges now skip DNS self-tests, to act a little more stealthily.
6955 Fixes bug 4201; bugfix on 0.2.0.3-alpha, which first introduced
6956 bridges. Patch by "warms0x".
6957 - Fix internal bug-checking logic that was supposed to catch
6958 failures in digest generation so that it will fail more robustly
6959 if we ask for a nonexistent algorithm. Found by Coverity Scan.
6960 Bugfix on 0.2.2.1-alpha; fixes Coverity CID 479.
6961 - Report any failure in init_keys() calls launched because our
6962 IP address has changed. Spotted by Coverity Scan. Bugfix on
6963 0.1.1.4-alpha; fixes CID 484.
6965 o Minor bugfixes (log messages and documentation):
6966 - Remove a confusing dollar sign from the example fingerprint in the
6967 man page, and also make the example fingerprint a valid one. Fixes
6968 bug 4309; bugfix on 0.2.1.3-alpha.
6969 - The next version of Windows will be called Windows 8, and it has
6970 a major version of 6, minor version of 2. Correctly identify that
6971 version instead of calling it "Very recent version". Resolves
6972 ticket 4153; reported by funkstar.
6973 - Downgrade log messages about circuit timeout calibration from
6974 "notice" to "info": they don't require or suggest any human
6975 intervention. Patch from Tom Lowenthal. Fixes bug 4063;
6976 bugfix on 0.2.2.14-alpha.
6979 - Turn on directory request statistics by default and include them in
6980 extra-info descriptors. Don't break if we have no GeoIP database.
6981 Backported from 0.2.3.1-alpha; implements ticket 3951.
6982 - Update to the October 4 2011 Maxmind GeoLite Country database.
6985 Changes in version 0.2.1.31 - 2011-10-26
6986 Tor 0.2.1.31 backports important security and privacy fixes for
6987 oldstable. This release is intended only for package maintainers and
6988 others who cannot use the 0.2.2 stable series. All others should be
6989 using Tor 0.2.2.x or newer.
6991 o Security fixes (also included in 0.2.2.x):
6992 - Replace all potentially sensitive memory comparison operations
6993 with versions whose runtime does not depend on the data being
6994 compared. This will help resist a class of attacks where an
6995 adversary can use variations in timing information to learn
6996 sensitive data. Fix for one case of bug 3122. (Safe memcmp
6997 implementation by Robert Ransom based partially on code by DJB.)
6998 - Fix an assert in parsing router descriptors containing IPv6
6999 addresses. This one took down the directory authorities when
7000 somebody tried some experimental code. Bugfix on 0.2.1.3-alpha.
7002 o Privacy/anonymity fixes (also included in 0.2.2.x):
7003 - Clients and bridges no longer send TLS certificate chains on
7004 outgoing OR connections. Previously, each client or bridge would
7005 use the same cert chain for all outgoing OR connections until
7006 its IP address changes, which allowed any relay that the client
7007 or bridge contacted to determine which entry guards it is using.
7008 Fixes CVE-2011-2768. Bugfix on 0.0.9pre5; found by "frosty_un".
7009 - If a relay receives a CREATE_FAST cell on a TLS connection, it
7010 no longer considers that connection as suitable for satisfying a
7011 circuit EXTEND request. Now relays can protect clients from the
7012 CVE-2011-2768 issue even if the clients haven't upgraded yet.
7013 - Bridges now refuse CREATE or CREATE_FAST cells on OR connections
7014 that they initiated. Relays could distinguish incoming bridge
7015 connections from client connections, creating another avenue for
7016 enumerating bridges. Fixes CVE-2011-2769. Bugfix on 0.2.0.3-alpha.
7017 Found by "frosty_un".
7018 - When receiving a hidden service descriptor, check that it is for
7019 the hidden service we wanted. Previously, Tor would store any
7020 hidden service descriptors that a directory gave it, whether it
7021 wanted them or not. This wouldn't have let an attacker impersonate
7022 a hidden service, but it did let directories pre-seed a client
7023 with descriptors that it didn't want. Bugfix on 0.0.6.
7024 - Avoid linkability based on cached hidden service descriptors: forget
7025 all hidden service descriptors cached as a client when processing a
7026 SIGNAL NEWNYM command. Fixes bug 3000; bugfix on 0.0.6.
7027 - Make the bridge directory authority refuse to answer directory
7028 requests for "all" descriptors. It used to include bridge
7029 descriptors in its answer, which was a major information leak.
7030 Found by "piebeer". Bugfix on 0.2.0.3-alpha.
7031 - Don't attach new streams to old rendezvous circuits after SIGNAL
7032 NEWNYM. Previously, we would keep using an existing rendezvous
7033 circuit if it remained open (i.e. if it were kept open by a
7034 long-lived stream, or if a new stream were attached to it before
7035 Tor could notice that it was old and no longer in use). Bugfix on
7036 0.1.1.15-rc; fixes bug 3375.
7038 o Minor bugfixes (also included in 0.2.2.x):
7039 - When we restart our relay, we might get a successful connection
7040 from the outside before we've started our reachability tests,
7041 triggering a warning: "ORPort found reachable, but I have no
7042 routerinfo yet. Failing to inform controller of success." This
7043 bug was harmless unless Tor is running under a controller
7044 like Vidalia, in which case the controller would never get a
7045 REACHABILITY_SUCCEEDED status event. Bugfix on 0.1.2.6-alpha;
7047 - Build correctly on OSX with zlib 1.2.4 and higher with all warnings
7048 enabled. Fixes bug 1526.
7049 - Remove undocumented option "-F" from tor-resolve: it hasn't done
7050 anything since 0.2.1.16-rc.
7051 - Avoid signed/unsigned comparisons by making SIZE_T_CEILING unsigned.
7052 None of the cases where we did this before were wrong, but by making
7053 this change we avoid warnings. Fixes bug 2475; bugfix on 0.2.1.28.
7054 - Fix a rare crash bug that could occur when a client was configured
7055 with a large number of bridges. Fixes bug 2629; bugfix on
7056 0.2.1.2-alpha. Bugfix by trac user "shitlei".
7057 - Correct the warning displayed when a rendezvous descriptor exceeds
7058 the maximum size. Fixes bug 2750; bugfix on 0.2.1.5-alpha. Found by
7060 - Fix an uncommon assertion failure when running with DNSPort under
7061 heavy load. Fixes bug 2933; bugfix on 0.2.0.1-alpha.
7062 - When warning about missing zlib development packages during compile,
7063 give the correct package names. Bugfix on 0.2.0.1-alpha.
7064 - Require that introduction point keys and onion keys have public
7065 exponent 65537. Bugfix on 0.2.0.10-alpha.
7066 - Do not crash when our configuration file becomes unreadable, for
7067 example due to a permissions change, between when we start up
7068 and when a controller calls SAVECONF. Fixes bug 3135; bugfix
7070 - Fix warnings from GCC 4.6's "-Wunused-but-set-variable" option.
7072 - Always NUL-terminate the sun_path field of a sockaddr_un before
7073 passing it to the kernel. (Not a security issue: kernels are
7074 smart enough to reject bad sockaddr_uns.) Found by Coverity;
7075 CID #428. Bugfix on Tor 0.2.0.3-alpha.
7076 - Don't stack-allocate the list of supplementary GIDs when we're
7077 about to log them. Stack-allocating NGROUPS_MAX gid_t elements
7078 could take up to 256K, which is way too much stack. Found by
7079 Coverity; CID #450. Bugfix on 0.2.1.7-alpha.
7081 o Minor bugfixes (only in 0.2.1.x):
7082 - Resume using micro-version numbers in 0.2.1.x: our Debian packages
7083 rely on them. Bugfix on 0.2.1.30.
7084 - Use git revisions instead of svn revisions when generating our
7085 micro-version numbers. Bugfix on 0.2.1.15-rc; fixes bug 2402.
7087 o Minor features (also included in 0.2.2.x):
7088 - Adjust the expiration time on our SSL session certificates to
7089 better match SSL certs seen in the wild. Resolves ticket 4014.
7090 - Allow nameservers with IPv6 address. Resolves bug 2574.
7091 - Update to the October 4 2011 Maxmind GeoLite Country database.
7094 Changes in version 0.2.3.5-alpha - 2011-09-28
7095 Tor 0.2.3.5-alpha fixes two bugs that make it possible to enumerate
7096 bridge relays; fixes an assertion error that many users started hitting
7097 today; and adds the ability to refill token buckets more often than
7098 once per second, allowing significant performance improvements.
7101 - Bridge relays now do their directory fetches inside Tor TLS
7102 connections, like all the other clients do, rather than connecting
7103 directly to the DirPort like public relays do. Removes another
7104 avenue for enumerating bridges. Fixes bug 4115; bugfix on 0.2.0.35.
7105 - Bridges relays now build circuits for themselves in a more similar
7106 way to how clients build them. Removes another avenue for
7107 enumerating bridges. Fixes bug 4124; bugfix on 0.2.0.3-alpha,
7108 when bridges were introduced.
7111 - Fix an "Assertion md->held_by_node == 1 failed" error that could
7112 occur when the same microdescriptor was referenced by two node_t
7113 objects at once. Fix for bug 4118; bugfix on Tor 0.2.3.1-alpha.
7115 o Major features (networking):
7116 - Add a new TokenBucketRefillInterval option to refill token buckets
7117 more frequently than once per second. This should improve network
7118 performance, alleviate queueing problems, and make traffic less
7119 bursty. Implements proposal 183; closes ticket 3630. Design by
7120 Florian Tschorsch and Björn Scheuermann; implementation by
7124 - Change an integer overflow check in the OpenBSD_Malloc code so
7125 that GCC is less likely to eliminate it as impossible. Patch
7126 from Mansour Moufid. Fixes bug 4059.
7128 o Minor bugfixes (usability):
7129 - Downgrade log messages about circuit timeout calibration from
7130 "notice" to "info": they don't require or suggest any human
7131 intervention. Patch from Tom Lowenthal. Fixes bug 4063;
7132 bugfix on 0.2.2.14-alpha.
7134 o Minor features (diagnostics):
7135 - When the system call to create a listener socket fails, log the
7136 error message explaining why. This may help diagnose bug 4027.
7139 Changes in version 0.2.3.4-alpha - 2011-09-13
7140 Tor 0.2.3.4-alpha includes the fixes from 0.2.2.33, including a slight
7141 tweak to Tor's TLS handshake that makes relays and bridges that run
7142 this new version reachable from Iran again. It also fixes a few new
7143 bugs in 0.2.3.x, and teaches relays to recognize when they're not
7144 listed in the network consensus and republish.
7146 o Major bugfixes (also part of 0.2.2.33):
7147 - Avoid an assertion failure when reloading a configuration with
7148 TrackExitHosts changes. Found and fixed by 'laruldan'. Fixes bug
7149 3923; bugfix on 0.2.2.25-alpha.
7151 o Minor features (security, also part of 0.2.2.33):
7152 - Check for replays of the public-key encrypted portion of an
7153 INTRODUCE1 cell, in addition to the current check for replays of
7154 the g^x value. This prevents a possible class of active attacks
7155 by an attacker who controls both an introduction point and a
7156 rendezvous point, and who uses the malleability of AES-CTR to
7157 alter the encrypted g^x portion of the INTRODUCE1 cell. We think
7158 that these attacks are infeasible (requiring the attacker to send
7159 on the order of zettabytes of altered cells in a short interval),
7160 but we'd rather block them off in case there are any classes of
7161 this attack that we missed. Reported by Willem Pinckaers.
7163 o Minor features (also part of 0.2.2.33):
7164 - Adjust the expiration time on our SSL session certificates to
7165 better match SSL certs seen in the wild. Resolves ticket 4014.
7166 - Change the default required uptime for a relay to be accepted as
7167 a HSDir (hidden service directory) from 24 hours to 25 hours.
7168 Improves on 0.2.0.10-alpha; resolves ticket 2649.
7169 - Add a VoteOnHidServDirectoriesV2 config option to allow directory
7170 authorities to abstain from voting on assignment of the HSDir
7171 consensus flag. Related to bug 2649.
7172 - Update to the September 6 2011 Maxmind GeoLite Country database.
7174 o Minor bugfixes (also part of 0.2.2.33):
7175 - Demote the 'replay detected' log message emitted when a hidden
7176 service receives the same Diffie-Hellman public key in two different
7177 INTRODUCE2 cells to info level. A normal Tor client can cause that
7178 log message during its normal operation. Bugfix on 0.2.1.6-alpha;
7179 fixes part of bug 2442.
7180 - Demote the 'INTRODUCE2 cell is too {old,new}' log message to info
7181 level. There is nothing that a hidden service's operator can do
7182 to fix its clients' clocks. Bugfix on 0.2.1.6-alpha; fixes part
7184 - Clarify a log message specifying the characters permitted in
7185 HiddenServiceAuthorizeClient client names. Previously, the log
7186 message said that "[A-Za-z0-9+-_]" were permitted; that could have
7187 given the impression that every ASCII character between "+" and "_"
7188 was permitted. Now we say "[A-Za-z0-9+_-]". Bugfix on 0.2.1.5-alpha.
7190 o Build fixes (also part of 0.2.2.33):
7191 - Clean up some code issues that prevented Tor from building on older
7192 BSDs. Fixes bug 3894; reported by "grarpamp".
7193 - Search for a platform-specific version of "ar" when cross-compiling.
7194 Should fix builds on iOS. Resolves bug 3909, found by Marco Bonetti.
7197 - Fix a bug where the SocksPort option (for example) would get
7198 ignored and replaced by the default if a SocksListenAddress
7199 option was set. Bugfix on 0.2.3.3-alpha; fixes bug 3936. Fix by
7203 - Relays now try regenerating and uploading their descriptor more
7204 frequently if they are not listed in the consensus, or if the
7205 version of their descriptor listed in the consensus is too
7206 old. This fix should prevent situations where a server declines
7207 to re-publish itself because it has done so too recently, even
7208 though the authorities decided not to list its recent-enough
7209 descriptor. Fix for bug 3327.
7212 - Relays now include a reason for regenerating their descriptors
7213 in an HTTP header when uploading to the authorities. This will
7214 make it easier to debug descriptor-upload issues in the future.
7215 - When starting as root and then changing our UID via the User
7216 control option, and we have a ControlSocket configured, make sure
7217 that the ControlSocket is owned by the same account that Tor will
7218 run under. Implements ticket 3421; fix by Jérémy Bobbio.
7221 - Abort if tor_vasprintf fails in connection_printf_to_buf (a
7222 utility function used in the control-port code). This shouldn't
7223 ever happen unless Tor is completely out of memory, but if it did
7224 happen and Tor somehow recovered from it, Tor could have sent a log
7225 message to a control port in the middle of a reply to a controller
7226 command. Fixes part of bug 3428; bugfix on 0.1.2.3-alpha.
7227 - Make 'FetchUselessDescriptors' cause all descriptor types and
7228 all consensus types (including microdescriptors) to get fetched.
7229 Fixes bug 3851; bugfix on 0.2.3.1-alpha.
7232 - Make a new "entry connection" struct as an internal subtype of "edge
7233 connection", to simplify the code and make exit connections smaller.
7236 Changes in version 0.2.2.33 - 2011-09-13
7237 Tor 0.2.2.33 fixes several bugs, and includes a slight tweak to Tor's
7238 TLS handshake that makes relays and bridges that run this new version
7239 reachable from Iran again.
7242 - Avoid an assertion failure when reloading a configuration with
7243 TrackExitHosts changes. Found and fixed by 'laruldan'. Fixes bug
7244 3923; bugfix on 0.2.2.25-alpha.
7246 o Minor features (security):
7247 - Check for replays of the public-key encrypted portion of an
7248 INTRODUCE1 cell, in addition to the current check for replays of
7249 the g^x value. This prevents a possible class of active attacks
7250 by an attacker who controls both an introduction point and a
7251 rendezvous point, and who uses the malleability of AES-CTR to
7252 alter the encrypted g^x portion of the INTRODUCE1 cell. We think
7253 that these attacks are infeasible (requiring the attacker to send
7254 on the order of zettabytes of altered cells in a short interval),
7255 but we'd rather block them off in case there are any classes of
7256 this attack that we missed. Reported by Willem Pinckaers.
7259 - Adjust the expiration time on our SSL session certificates to
7260 better match SSL certs seen in the wild. Resolves ticket 4014.
7261 - Change the default required uptime for a relay to be accepted as
7262 a HSDir (hidden service directory) from 24 hours to 25 hours.
7263 Improves on 0.2.0.10-alpha; resolves ticket 2649.
7264 - Add a VoteOnHidServDirectoriesV2 config option to allow directory
7265 authorities to abstain from voting on assignment of the HSDir
7266 consensus flag. Related to bug 2649.
7267 - Update to the September 6 2011 Maxmind GeoLite Country database.
7269 o Minor bugfixes (documentation and log messages):
7270 - Correct the man page to explain that HashedControlPassword and
7271 CookieAuthentication can both be set, in which case either method
7272 is sufficient to authenticate to Tor. Bugfix on 0.2.0.7-alpha,
7273 when we decided to allow these config options to both be set. Issue
7275 - Demote the 'replay detected' log message emitted when a hidden
7276 service receives the same Diffie-Hellman public key in two different
7277 INTRODUCE2 cells to info level. A normal Tor client can cause that
7278 log message during its normal operation. Bugfix on 0.2.1.6-alpha;
7279 fixes part of bug 2442.
7280 - Demote the 'INTRODUCE2 cell is too {old,new}' log message to info
7281 level. There is nothing that a hidden service's operator can do
7282 to fix its clients' clocks. Bugfix on 0.2.1.6-alpha; fixes part
7284 - Clarify a log message specifying the characters permitted in
7285 HiddenServiceAuthorizeClient client names. Previously, the log
7286 message said that "[A-Za-z0-9+-_]" were permitted; that could have
7287 given the impression that every ASCII character between "+" and "_"
7288 was permitted. Now we say "[A-Za-z0-9+_-]". Bugfix on 0.2.1.5-alpha.
7291 - Provide a substitute implementation of lround() for MSVC, which
7292 apparently lacks it. Patch from Gisle Vanem.
7293 - Clean up some code issues that prevented Tor from building on older
7294 BSDs. Fixes bug 3894; reported by "grarpamp".
7295 - Search for a platform-specific version of "ar" when cross-compiling.
7296 Should fix builds on iOS. Resolves bug 3909, found by Marco Bonetti.
7299 Changes in version 0.2.3.3-alpha - 2011-09-01
7300 Tor 0.2.3.3-alpha adds a new "stream isolation" feature to improve Tor's
7301 security, and provides client-side support for the microdescriptor
7302 and optimistic data features introduced earlier in the 0.2.3.x
7303 series. It also includes numerous critical bugfixes in the (optional)
7304 bufferevent-based networking backend.
7306 o Major features (stream isolation):
7307 - You can now configure Tor so that streams from different
7308 applications are isolated on different circuits, to prevent an
7309 attacker who sees your streams as they leave an exit node from
7310 linking your sessions to one another. To do this, choose some way
7311 to distinguish the applications: have them connect to different
7312 SocksPorts, or have one of them use SOCKS4 while the other uses
7313 SOCKS5, or have them pass different authentication strings to the
7314 SOCKS proxy. Then, use the new SocksPort syntax to configure the
7315 degree of isolation you need. This implements Proposal 171.
7316 - There's a new syntax for specifying multiple client ports (such as
7317 SOCKSPort, TransPort, DNSPort, NATDPort): you can now just declare
7318 multiple *Port entries with full addr:port syntax on each.
7319 The old *ListenAddress format is still supported, but you can't
7320 mix it with the new *Port syntax.
7322 o Major features (other):
7323 - Enable microdescriptor fetching by default for clients. This allows
7324 clients to download a much smaller amount of directory information.
7325 To disable it (and go back to the old-style consensus and
7326 descriptors), set "UseMicrodescriptors 0" in your torrc file.
7327 - Tor's firewall-helper feature, introduced in 0.2.3.1-alpha (see the
7328 "PortForwarding" config option), now supports Windows.
7329 - When using an exit relay running 0.2.3.x, clients can now
7330 "optimistically" send data before the exit relay reports that
7331 the stream has opened. This saves a round trip when starting
7332 connections where the client speaks first (such as web browsing).
7333 This behavior is controlled by a consensus parameter (currently
7334 disabled). To turn it on or off manually, use the "OptimisticData"
7335 torrc option. Implements proposal 181; code by Ian Goldberg.
7337 o Major bugfixes (bufferevents, fixes on 0.2.3.1-alpha):
7338 - When using IOCP on Windows, we need to enable Libevent windows
7340 - The IOCP backend now works even when the user has not specified
7341 the (internal, debugging-only) _UseFilteringSSLBufferevents option.
7342 Fixes part of bug 3752.
7343 - Correctly record the bytes we've read and written when using
7344 bufferevents, so that we can include them in our bandwidth history
7345 and advertised bandwidth. Fixes bug 3803.
7346 - Apply rate-limiting only at the bottom of a chain of filtering
7347 bufferevents. This prevents us from filling up internal read
7348 buffers and violating rate-limits when filtering bufferevents
7349 are enabled. Fixes part of bug 3804.
7350 - Add high-watermarks to the output buffers for filtered
7351 bufferevents. This prevents us from filling up internal write
7352 buffers and wasting CPU cycles when filtering bufferevents are
7353 enabled. Fixes part of bug 3804.
7354 - Correctly notice when data has been written from a bufferevent
7355 without flushing it completely. Fixes bug 3805.
7356 - Fix a bug where server-side tunneled bufferevent-based directory
7357 streams would get closed prematurely. Fixes bug 3814.
7358 - Fix a use-after-free error with per-connection rate-limiting
7359 buckets. Fixes bug 3888.
7361 o Major bugfixes (also part of 0.2.2.31-rc):
7362 - If we're configured to write our ControlPorts to disk, only write
7363 them after switching UID and creating the data directory. This way,
7364 we don't fail when starting up with a nonexistent DataDirectory
7365 and a ControlPortWriteToFile setting based on that directory. Fixes
7366 bug 3747; bugfix on Tor 0.2.2.26-beta.
7369 - Added a new CONF_CHANGED event so that controllers can be notified
7370 of any configuration changes made by other controllers, or by the
7371 user. Implements ticket 1692.
7372 - Use evbuffer_copyout() in inspect_evbuffer(). This fixes a memory
7373 leak when using bufferevents, and lets Libevent worry about how to
7374 best copy data out of a buffer.
7375 - Replace files in stats/ rather than appending to them. Now that we
7376 include statistics in extra-info descriptors, it makes no sense to
7377 keep old statistics forever. Implements ticket 2930.
7379 o Minor features (build compatibility):
7380 - Limited, experimental support for building with nmake and MSVC.
7381 - Provide a substitute implementation of lround() for MSVC, which
7382 apparently lacks it. Patch from Gisle Vanem.
7384 o Minor features (also part of 0.2.2.31-rc):
7385 - Update to the August 2 2011 Maxmind GeoLite Country database.
7387 o Minor bugfixes (on 0.2.3.x-alpha):
7388 - Fix a spurious warning when parsing SOCKS requests with
7389 bufferevents enabled. Fixes bug 3615; bugfix on 0.2.3.2-alpha.
7390 - Get rid of a harmless warning that could happen on relays running
7391 with bufferevents. The warning was caused by someone doing an http
7392 request to a relay's orport. Also don't warn for a few related
7393 non-errors. Fixes bug 3700; bugfix on 0.2.3.1-alpha.
7395 o Minor bugfixes (on 2.2.x and earlier):
7396 - Correct the man page to explain that HashedControlPassword and
7397 CookieAuthentication can both be set, in which case either method
7398 is sufficient to authenticate to Tor. Bugfix on 0.2.0.7-alpha,
7399 when we decided to allow these config options to both be set. Issue
7401 - The "--quiet" and "--hush" options now apply not only to Tor's
7402 behavior before logs are configured, but also to Tor's behavior in
7403 the absense of configured logs. Fixes bug 3550; bugfix on
7406 o Minor bugfixes (also part of 0.2.2.31-rc):
7407 - Write several files in text mode, on OSes that distinguish text
7408 mode from binary mode (namely, Windows). These files are:
7409 'buffer-stats', 'dirreq-stats', and 'entry-stats' on relays
7410 that collect those statistics; 'client_keys' and 'hostname' for
7411 hidden services that use authentication; and (in the tor-gencert
7412 utility) newly generated identity and signing keys. Previously,
7413 we wouldn't specify text mode or binary mode, leading to an
7414 assertion failure. Fixes bug 3607. Bugfix on 0.2.1.1-alpha (when
7415 the DirRecordUsageByCountry option which would have triggered
7416 the assertion failure was added), although this assertion failure
7417 would have occurred in tor-gencert on Windows in 0.2.0.1-alpha.
7418 - Selectively disable deprecation warnings on OS X because Lion
7419 started deprecating the shipped copy of openssl. Fixes bug 3643.
7420 - Remove an extra pair of quotation marks around the error
7421 message in control-port STATUS_GENERAL BUG events. Bugfix on
7422 0.1.2.6-alpha; fixes bug 3732.
7423 - When unable to format an address as a string, report its value
7424 as "???" rather than reusing the last formatted address. Bugfix
7427 o Code simplifications and refactoring:
7428 - Rewrite the listener-selection logic so that parsing which ports
7429 we want to listen on is now separate from binding to the ports
7433 - Building Tor with bufferevent support now requires Libevent
7434 2.0.13-stable or later. Previous versions of Libevent had bugs in
7435 SSL-related bufferevents and related issues that would make Tor
7436 work badly with bufferevents. Requiring 2.0.13-stable also allows
7437 Tor with bufferevents to take advantage of Libevent APIs
7438 introduced after 2.0.8-rc.
7441 Changes in version 0.2.2.32 - 2011-08-27
7442 The Tor 0.2.2 release series is dedicated to the memory of Andreas
7443 Pfitzmann (1958-2010), a pioneer in anonymity and privacy research,
7444 a founder of the PETS community, a leader in our field, a mentor,
7445 and a friend. He left us with these words: "I had the possibility
7446 to contribute to this world that is not as it should be. I hope I
7447 could help in some areas to make the world a better place, and that
7448 I could also encourage other people to be engaged in improving the
7449 world. Please, stay engaged. This world needs you, your love, your
7450 initiative -- now I cannot be part of that anymore."
7452 Tor 0.2.2.32, the first stable release in the 0.2.2 branch, is finally
7453 ready. More than two years in the making, this release features improved
7454 client performance and hidden service reliability, better compatibility
7455 for Android, correct behavior for bridges that listen on more than
7456 one address, more extensible and flexible directory object handling,
7457 better reporting of network statistics, improved code security, and
7458 many many other features and bugfixes.
7461 Changes in version 0.2.2.31-rc - 2011-08-17
7462 Tor 0.2.2.31-rc is the second and hopefully final release candidate
7463 for the Tor 0.2.2.x series.
7466 - Remove an extra pair of quotation marks around the error
7467 message in control-port STATUS_GENERAL BUG events. Bugfix on
7468 0.1.2.6-alpha; fixes bug 3732.
7469 - If we're configured to write our ControlPorts to disk, only write
7470 them after switching UID and creating the data directory. This way,
7471 we don't fail when starting up with a nonexistent DataDirectory
7472 and a ControlPortWriteToFile setting based on that directory. Fixes
7473 bug 3747; bugfix on Tor 0.2.2.26-beta.
7476 - Update to the August 2 2011 Maxmind GeoLite Country database.
7479 - Allow GETINFO fingerprint to return a fingerprint even when
7480 we have not yet built a router descriptor. Fixes bug 3577;
7481 bugfix on 0.2.0.1-alpha.
7482 - Write several files in text mode, on OSes that distinguish text
7483 mode from binary mode (namely, Windows). These files are:
7484 'buffer-stats', 'dirreq-stats', and 'entry-stats' on relays
7485 that collect those statistics; 'client_keys' and 'hostname' for
7486 hidden services that use authentication; and (in the tor-gencert
7487 utility) newly generated identity and signing keys. Previously,
7488 we wouldn't specify text mode or binary mode, leading to an
7489 assertion failure. Fixes bug 3607. Bugfix on 0.2.1.1-alpha (when
7490 the DirRecordUsageByCountry option which would have triggered
7491 the assertion failure was added), although this assertion failure
7492 would have occurred in tor-gencert on Windows in 0.2.0.1-alpha.
7493 - Selectively disable deprecation warnings on OS X because Lion
7494 started deprecating the shipped copy of openssl. Fixes bug 3643.
7495 - When unable to format an address as a string, report its value
7496 as "???" rather than reusing the last formatted address. Bugfix
7500 Changes in version 0.2.3.2-alpha - 2011-07-18
7501 Tor 0.2.3.2-alpha introduces two new experimental features:
7502 microdescriptors and pluggable transports. It also continues cleaning
7503 up a variety of recently introduced features.
7506 - Clients can now use microdescriptors instead of regular descriptors
7507 to build circuits. Microdescriptors are authority-generated
7508 summaries of regular descriptors' contents, designed to change
7509 very rarely (see proposal 158 for details). This feature is
7510 designed to save bandwidth, especially for clients on slow internet
7511 connections. It's off by default for now, since nearly no caches
7512 support it, but it will be on-by-default for clients in a future
7513 version. You can use the UseMicrodescriptors option to turn it on.
7514 - Tor clients using bridges can now be configured to use a separate
7515 'transport' proxy for each bridge. This approach helps to resist
7516 censorship by allowing bridges to use protocol obfuscation
7517 plugins. It implements part of proposal 180. Implements ticket 2841.
7518 - While we're trying to bootstrap, record how many TLS connections
7519 fail in each state, and report which states saw the most failures
7520 in response to any bootstrap failures. This feature may speed up
7521 diagnosis of censorship events. Implements ticket 3116.
7523 o Major bugfixes (on 0.2.3.1-alpha):
7524 - When configuring a large set of nodes in EntryNodes (as with
7525 'EntryNodes {cc}' or 'EntryNodes 1.1.1.1/16'), choose only a
7526 random subset to be guards, and choose them in random
7527 order. Fixes bug 2798.
7528 - Tor could crash when remembering a consensus in a non-used consensus
7529 flavor without having a current consensus set. Fixes bug 3361.
7530 - Comparing an unknown address to a microdescriptor's shortened exit
7531 policy would always give a "rejected" result. Fixes bug 3599.
7532 - Using microdescriptors as a client no longer prevents Tor from
7533 uploading and downloading hidden service descriptors. Fixes
7537 - Allow nameservers with IPv6 address. Resolves bug 2574.
7538 - Accept attempts to include a password authenticator in the
7539 handshake, as supported by SOCKS5. This handles SOCKS clients that
7540 don't know how to omit a password when authenticating. Resolves
7542 - When configuring a large set of nodes in EntryNodes, and there are
7543 enough of them listed as Guard so that we don't need to consider
7544 the non-guard entries, prefer the ones listed with the Guard flag.
7545 - Check for and recover from inconsistency in the microdescriptor
7546 cache. This will make it harder for us to accidentally free a
7547 microdescriptor without removing it from the appropriate data
7548 structures. Fixes issue 3135; issue noted by "wanoskarnet".
7549 - Log SSL state transitions at log level DEBUG, log domain
7550 HANDSHAKE. This can be useful for debugging censorship events.
7551 Implements ticket 3264.
7552 - Add port 6523 (Gobby) to LongLivedPorts. Patch by intrigeri;
7553 implements ticket 3439.
7555 o Minor bugfixes (on 0.2.3.1-alpha):
7556 - Do not free all general-purpose regular descriptors just
7557 because microdescriptor use is enabled. Fixes bug 3113.
7558 - Correctly link libevent_openssl when --enable-static-libevent
7559 is passed to configure. Fixes bug 3118.
7560 - Bridges should not complain during their heartbeat log messages that
7561 they are unlisted in the consensus: that's more or less the point
7562 of being a bridge. Fixes bug 3183.
7563 - Report a SIGNAL event to controllers when acting on a delayed
7564 SIGNAL NEWNYM command. Previously, we would report a SIGNAL
7565 event to the controller if we acted on a SIGNAL NEWNYM command
7566 immediately, and otherwise not report a SIGNAL event for the
7567 command at all. Fixes bug 3349.
7568 - Fix a crash when handling the SIGNAL controller command or
7569 reporting ERR-level status events with bufferevents enabled. Found
7570 by Robert Ransom. Fixes bug 3367.
7571 - Always ship the tor-fw-helper manpage in our release tarballs.
7572 Fixes bug 3389. Reported by Stephen Walker.
7573 - Fix a class of double-mark-for-close bugs when bufferevents
7574 are enabled. Fixes bug 3403.
7575 - Update tor-fw-helper to support libnatpmp-20110618. Fixes bug 3434.
7576 - Add SIGNAL to the list returned by the 'GETINFO events/names'
7577 control-port command. Fixes part of bug 3465.
7578 - Prevent using negative indices during unit test runs when read_all()
7579 fails. Spotted by coverity.
7580 - Fix a rare memory leak when checking the nodelist without it being
7581 present. Found by coverity.
7582 - Only try to download a microdescriptor-flavored consensus from
7583 a directory cache that provides them.
7585 o Minor bugfixes (on 0.2.2.x and earlier):
7586 - Assert that hidden-service-related operations are not performed
7587 using single-hop circuits. Previously, Tor would assert that
7588 client-side streams are not attached to single-hop circuits,
7589 but not that other sensitive operations on the client and service
7590 side are not performed using single-hop circuits. Fixes bug 3332;
7592 - Don't publish a new relay descriptor when we reload our onion key,
7593 unless the onion key has actually changed. Fixes bug 3263 and
7594 resolves another cause of bug 1810. Bugfix on 0.1.1.11-alpha.
7595 - Allow GETINFO fingerprint to return a fingerprint even when
7596 we have not yet built a router descriptor. Fixes bug 3577;
7597 bugfix on 0.2.0.1-alpha.
7598 - Make 'tor --digests' list hashes of all Tor source files. Bugfix
7599 on 0.2.2.4-alpha; fixes bug 3427.
7601 o Code simplification and refactoring:
7602 - Use tor_sscanf() in place of scanf() in more places through the
7603 code. This makes us a little more locale-independent, and
7604 should help shut up code-analysis tools that can't tell
7605 a safe sscanf string from a dangerous one.
7606 - Use tt_assert(), not tor_assert(), for checking for test failures.
7607 This makes the unit tests more able to go on in the event that
7609 - Split connection_about_to_close() into separate functions for each
7613 - On Windows, we now define the _WIN32_WINNT macros only if they
7614 are not already defined. This lets the person building Tor decide,
7615 if they want, to require a later version of Windows.
7618 Changes in version 0.2.2.30-rc - 2011-07-07
7619 Tor 0.2.2.30-rc is the first release candidate for the Tor 0.2.2.x
7620 series. It fixes a few smaller bugs, but generally appears stable.
7621 Please test it and let us know whether it is!
7624 - Send a SUCCEEDED stream event to the controller when a reverse
7625 resolve succeeded. Fixes bug 3536; bugfix on 0.0.8pre1. Issue
7626 discovered by katmagic.
7627 - Always NUL-terminate the sun_path field of a sockaddr_un before
7628 passing it to the kernel. (Not a security issue: kernels are
7629 smart enough to reject bad sockaddr_uns.) Found by Coverity;
7630 CID #428. Bugfix on Tor 0.2.0.3-alpha.
7631 - Don't stack-allocate the list of supplementary GIDs when we're
7632 about to log them. Stack-allocating NGROUPS_MAX gid_t elements
7633 could take up to 256K, which is way too much stack. Found by
7634 Coverity; CID #450. Bugfix on 0.2.1.7-alpha.
7635 - Add BUILDTIMEOUT_SET to the list returned by the 'GETINFO
7636 events/names' control-port command. Bugfix on 0.2.2.9-alpha;
7637 fixes part of bug 3465.
7638 - Fix a memory leak when receiving a descriptor for a hidden
7639 service we didn't ask for. Found by Coverity; CID #30. Bugfix
7643 - Update to the July 1 2011 Maxmind GeoLite Country database.
7646 Changes in version 0.2.2.29-beta - 2011-06-20
7647 Tor 0.2.2.29-beta reverts an accidental behavior change for users who
7648 have bridge lines in their torrc but don't want to use them; gets
7649 us closer to having the control socket feature working on Debian;
7650 and fixes a variety of smaller bugs.
7653 - Revert the UseBridges option to its behavior before 0.2.2.28-beta.
7654 When we changed the default behavior to "use bridges if any
7655 are listed in the torrc", we surprised users who had bridges
7656 in their torrc files but who didn't actually want to use them.
7657 Partial resolution for bug 3354.
7660 - Don't attach new streams to old rendezvous circuits after SIGNAL
7661 NEWNYM. Previously, we would keep using an existing rendezvous
7662 circuit if it remained open (i.e. if it were kept open by a
7663 long-lived stream, or if a new stream were attached to it before
7664 Tor could notice that it was old and no longer in use). Bugfix on
7665 0.1.1.15-rc; fixes bug 3375.
7668 - Fix a bug when using ControlSocketsGroupWritable with User. The
7669 directory's group would be checked against the current group, not
7670 the configured group. Patch by Jérémy Bobbio. Fixes bug 3393;
7671 bugfix on 0.2.2.26-beta.
7672 - Make connection_printf_to_buf()'s behavior sane. Its callers
7673 expect it to emit a CRLF iff the format string ends with CRLF;
7674 it actually emitted a CRLF iff (a) the format string ended with
7675 CRLF or (b) the resulting string was over 1023 characters long or
7676 (c) the format string did not end with CRLF *and* the resulting
7677 string was 1021 characters long or longer. Bugfix on 0.1.1.9-alpha;
7678 fixes part of bug 3407.
7679 - Make send_control_event_impl()'s behavior sane. Its callers
7680 expect it to always emit a CRLF at the end of the string; it
7681 might have emitted extra control characters as well. Bugfix on
7682 0.1.1.9-alpha; fixes another part of bug 3407.
7683 - Make crypto_rand_int() check the value of its input correctly.
7684 Previously, it accepted values up to UINT_MAX, but could return a
7685 negative number if given a value above INT_MAX+1. Found by George
7686 Kadianakis. Fixes bug 3306; bugfix on 0.2.2pre14.
7687 - Avoid a segfault when reading a malformed circuit build state
7688 with more than INT_MAX entries. Found by wanoskarnet. Bugfix on
7690 - When asked about a DNS record type we don't support via a
7691 client DNSPort, reply with NOTIMPL rather than an empty
7692 reply. Patch by intrigeri. Fixes bug 3369; bugfix on 2.0.1-alpha.
7693 - Fix a rare memory leak during stats writing. Found by coverity.
7696 - Update to the June 1 2011 Maxmind GeoLite Country database.
7698 o Code simplifications and refactoring:
7699 - Remove some dead code as indicated by coverity.
7700 - Remove a few dead assignments during router parsing. Found by
7702 - Add some forgotten return value checks during unit tests. Found
7704 - Don't use 1-bit wide signed bit fields. Found by coverity.
7707 Changes in version 0.2.2.28-beta - 2011-06-04
7708 Tor 0.2.2.28-beta makes great progress towards a new stable release: we
7709 fixed a big bug in whether relays stay in the consensus consistently,
7710 we moved closer to handling bridges and hidden services correctly,
7711 and we started the process of better handling the dreaded "my Vidalia
7712 died, and now my Tor demands a password when I try to reconnect to it"
7716 - Don't decide to make a new descriptor when receiving a HUP signal.
7717 This bug has caused a lot of 0.2.2.x relays to disappear from the
7718 consensus periodically. Fixes the most common case of triggering
7719 bug 1810; bugfix on 0.2.2.7-alpha.
7720 - Actually allow nameservers with IPv6 addresses. Fixes bug 2574.
7721 - Don't try to build descriptors if "ORPort auto" is set and we
7722 don't know our actual ORPort yet. Fix for bug 3216; bugfix on
7724 - Resolve a crash that occurred when setting BridgeRelay to 1 with
7725 accounting enabled. Fixes bug 3228; bugfix on 0.2.2.18-alpha.
7726 - Apply circuit timeouts to opened hidden-service-related circuits
7727 based on the correct start time. Previously, we would apply the
7728 circuit build timeout based on time since the circuit's creation;
7729 it was supposed to be applied based on time since the circuit
7730 entered its current state. Bugfix on 0.0.6; fixes part of bug 1297.
7731 - Use the same circuit timeout for client-side introduction
7732 circuits as for other four-hop circuits, rather than the timeout
7733 for single-hop directory-fetch circuits; the shorter timeout may
7734 have been appropriate with the static circuit build timeout in
7735 0.2.1.x and earlier, but caused many hidden service access attempts
7736 to fail with the adaptive CBT introduced in 0.2.2.2-alpha. Bugfix
7737 on 0.2.2.2-alpha; fixes another part of bug 1297.
7738 - In ticket 2511 we fixed a case where you could use an unconfigured
7739 bridge if you had configured it as a bridge the last time you ran
7740 Tor. Now fix another edge case: if you had configured it as a bridge
7741 but then switched to a different bridge via the controller, you
7742 would still be willing to use the old one. Bugfix on 0.2.0.1-alpha;
7746 - Add an __OwningControllerProcess configuration option and a
7747 TAKEOWNERSHIP control-port command. Now a Tor controller can ensure
7748 that when it exits, Tor will shut down. Implements feature 3049.
7749 - If "UseBridges 1" is set and no bridges are configured, Tor will
7750 now refuse to build any circuits until some bridges are set.
7751 If "UseBridges auto" is set, Tor will use bridges if they are
7752 configured and we are not running as a server, but otherwise will
7753 make circuits as usual. The new default is "auto". Patch by anonym,
7754 so the Tails LiveCD can stop automatically revealing you as a Tor
7758 - Fix warnings from GCC 4.6's "-Wunused-but-set-variable" option.
7759 - Remove a trailing asterisk from "exit-policy/default" in the
7760 output of the control port command "GETINFO info/names". Bugfix
7762 - Use a wide type to hold sockets when built for 64-bit Windows builds.
7764 - Warn when the user configures two HiddenServiceDir lines that point
7765 to the same directory. Bugfix on 0.0.6 (the version introducing
7766 HiddenServiceDir); fixes bug 3289.
7767 - Remove dead code from rend_cache_lookup_v2_desc_as_dir. Fixes
7768 part of bug 2748; bugfix on 0.2.0.10-alpha.
7769 - Log malformed requests for rendezvous descriptors as protocol
7770 warnings, not warnings. Also, use a more informative log message
7771 in case someone sees it at log level warning without prior
7772 info-level messages. Fixes the other part of bug 2748; bugfix
7774 - Clear the table recording the time of the last request for each
7775 hidden service descriptor from each HS directory on SIGNAL NEWNYM.
7776 Previously, we would clear our HS descriptor cache on SIGNAL
7777 NEWNYM, but if we had previously retrieved a descriptor (or tried
7778 to) from every directory responsible for it, we would refuse to
7779 fetch it again for up to 15 minutes. Bugfix on 0.2.2.25-alpha;
7781 - Fix a log message that said "bits" while displaying a value in
7782 bytes. Found by wanoskarnet. Fixes bug 3318; bugfix on
7784 - When checking for 1024-bit keys, check for 1024 bits, not 128
7785 bytes. This allows Tor to correctly discard keys of length 1017
7786 through 1023. Bugfix on 0.0.9pre5.
7789 - Relays now log the reason for publishing a new relay descriptor,
7790 so we have a better chance of hunting down instances of bug 1810.
7791 Resolves ticket 3252.
7792 - Revise most log messages that refer to nodes by nickname to
7793 instead use the "$key=nickname at address" format. This should be
7794 more useful, especially since nicknames are less and less likely
7795 to be unique. Resolves ticket 3045.
7796 - Log (at info level) when purging pieces of hidden-service-client
7797 state because of SIGNAL NEWNYM.
7800 - Remove undocumented option "-F" from tor-resolve: it hasn't done
7801 anything since 0.2.1.16-rc.
7804 Changes in version 0.2.2.27-beta - 2011-05-18
7805 Tor 0.2.2.27-beta fixes a bridge-related stability bug in the previous
7806 release, and also adds a few more general bugfixes.
7809 - Fix a crash bug when changing bridges in a running Tor process.
7810 Fixes bug 3213; bugfix on 0.2.2.26-beta.
7811 - When the controller configures a new bridge, don't wait 10 to 60
7812 seconds before trying to fetch its descriptor. Bugfix on
7813 0.2.0.3-alpha; fixes bug 3198 (suggested by 2355).
7816 - Require that onion keys have exponent 65537 in microdescriptors too.
7817 Fixes more of bug 3207; bugfix on 0.2.2.26-beta.
7818 - Tor used to limit HttpProxyAuthenticator values to 48 characters.
7819 Changed the limit to 512 characters by removing base64 newlines.
7820 Fixes bug 2752. Fix by Michael Yakubovich.
7821 - When a client starts or stops using bridges, never use a circuit
7822 that was built before the configuration change. This behavior could
7823 put at risk a user who uses bridges to ensure that her traffic
7824 only goes to the chosen addresses. Bugfix on 0.2.0.3-alpha; fixes
7828 Changes in version 0.2.2.26-beta - 2011-05-17
7829 Tor 0.2.2.26-beta fixes a variety of potential privacy problems. It
7830 also introduces a new "socksport auto" approach that should make it
7831 easier to run multiple Tors on the same system, and does a lot of
7832 cleanup to get us closer to a release candidate.
7834 o Security/privacy fixes:
7835 - Replace all potentially sensitive memory comparison operations
7836 with versions whose runtime does not depend on the data being
7837 compared. This will help resist a class of attacks where an
7838 adversary can use variations in timing information to learn
7839 sensitive data. Fix for one case of bug 3122. (Safe memcmp
7840 implementation by Robert Ransom based partially on code by DJB.)
7841 - When receiving a hidden service descriptor, check that it is for
7842 the hidden service we wanted. Previously, Tor would store any
7843 hidden service descriptors that a directory gave it, whether it
7844 wanted them or not. This wouldn't have let an attacker impersonate
7845 a hidden service, but it did let directories pre-seed a client
7846 with descriptors that it didn't want. Bugfix on 0.0.6.
7847 - On SIGHUP, do not clear out all TrackHostExits mappings, client
7848 DNS cache entries, and virtual address mappings: that's what
7849 NEWNYM is for. Fixes bug 1345; bugfix on 0.1.0.1-rc.
7852 - The options SocksPort, ControlPort, and so on now all accept a
7853 value "auto" that opens a socket on an OS-selected port. A
7854 new ControlPortWriteToFile option tells Tor to write its
7855 actual control port or ports to a chosen file. If the option
7856 ControlPortFileGroupReadable is set, the file is created as
7857 group-readable. Now users can run two Tor clients on the same
7858 system without needing to manually mess with parameters. Resolves
7859 part of ticket 3076.
7860 - Set SO_REUSEADDR on all sockets, not just listeners. This should
7861 help busy exit nodes avoid running out of useable ports just
7862 because all the ports have been used in the near past. Resolves
7866 - New "GETINFO net/listeners/(type)" controller command to return
7867 a list of addresses and ports that are bound for listeners for a
7868 given connection type. This is useful when the user has configured
7869 "SocksPort auto" and the controller needs to know which port got
7870 chosen. Resolves another part of ticket 3076.
7871 - Add a new ControlSocketsGroupWritable configuration option: when
7872 it is turned on, ControlSockets are group-writeable by the default
7873 group of the current user. Patch by Jérémy Bobbio; implements
7875 - Tor now refuses to create a ControlSocket in a directory that is
7876 world-readable (or group-readable if ControlSocketsGroupWritable
7877 is 0). This is necessary because some operating systems do not
7878 enforce permissions on an AF_UNIX sockets. Permissions on the
7879 directory holding the socket, however, seems to work everywhere.
7880 - Rate-limit a warning about failures to download v2 networkstatus
7881 documents. Resolves part of bug 1352.
7882 - Backport code from 0.2.3.x that allows directory authorities to
7883 clean their microdescriptor caches. Needed to resolve bug 2230.
7884 - When an HTTPS proxy reports "403 Forbidden", we now explain
7885 what it means rather than calling it an unexpected status code.
7886 Closes bug 2503. Patch from Michael Yakubovich.
7887 - Update to the May 1 2011 Maxmind GeoLite Country database.
7890 - Authorities now clean their microdesc cache periodically and when
7891 reading from disk initially, not only when adding new descriptors.
7892 This prevents a bug where we could lose microdescriptors. Bugfix
7893 on 0.2.2.6-alpha. Fixes bug 2230.
7894 - Do not crash when our configuration file becomes unreadable, for
7895 example due to a permissions change, between when we start up
7896 and when a controller calls SAVECONF. Fixes bug 3135; bugfix
7898 - Avoid a bug that would keep us from replacing a microdescriptor
7899 cache on Windows. (We would try to replace the file while still
7900 holding it open. That's fine on Unix, but Windows doesn't let us
7901 do that.) Bugfix on 0.2.2.6-alpha; bug found by wanoskarnet.
7902 - Add missing explanations for the authority-related torrc options
7903 RephistTrackTime, BridgePassword, and V3AuthUseLegacyKey in the
7904 man page. Resolves issue 2379.
7905 - As an authority, do not upload our own vote or signature set to
7906 ourself. It would tell us nothing new, and as of 0.2.2.24-alpha,
7907 it would get flagged as a duplicate. Resolves bug 3026.
7908 - Accept hidden service descriptors if we think we might be a hidden
7909 service directory, regardless of what our consensus says. This
7910 helps robustness, since clients and hidden services can sometimes
7911 have a more up-to-date view of the network consensus than we do,
7912 and if they think that the directory authorities list us a HSDir,
7913 we might actually be one. Related to bug 2732; bugfix on
7915 - When a controller changes TrackHostExits, remove mappings for
7916 hosts that should no longer have their exits tracked. Bugfix on
7918 - When a controller changes VirtualAddrNetwork, remove any mappings
7919 for hosts that were automapped to the old network. Bugfix on
7921 - When a controller changes one of the AutomapHosts* options, remove
7922 any mappings for hosts that should no longer be automapped. Bugfix
7924 - Do not reset the bridge descriptor download status every time we
7925 re-parse our configuration or get a configuration change. Fixes
7926 bug 3019; bugfix on 0.2.0.3-alpha.
7928 o Minor bugfixes (code cleanup):
7929 - When loading the microdesc journal, remember its current size.
7930 In 0.2.2, this helps prevent the microdesc journal from growing
7931 without limit on authorities (who are the only ones to use it in
7932 0.2.2). Fixes a part of bug 2230; bugfix on 0.2.2.6-alpha.
7933 Fix posted by "cypherpunks."
7934 - The microdesc journal is supposed to get rebuilt only if it is
7935 at least _half_ the length of the store, not _twice_ the length
7936 of the store. Bugfix on 0.2.2.6-alpha; fixes part of bug 2230.
7937 - Fix a potential null-pointer dereference while computing a
7938 consensus. Bugfix on tor-0.2.0.3-alpha, found with the help of
7940 - Avoid a possible null-pointer dereference when rebuilding the mdesc
7941 cache without actually having any descriptors to cache. Bugfix on
7942 0.2.2.6-alpha. Issue discovered using clang's static analyzer.
7943 - If we fail to compute the identity digest of a v3 legacy keypair,
7944 warn, and don't use a buffer-full of junk instead. Bugfix on
7945 0.2.1.1-alpha; fixes bug 3106.
7946 - Resolve an untriggerable issue in smartlist_string_num_isin(),
7947 where if the function had ever in the future been used to check
7948 for the presence of a too-large number, it would have given an
7949 incorrect result. (Fortunately, we only used it for 16-bit
7950 values.) Fixes bug 3175; bugfix on 0.1.0.1-rc.
7951 - Require that introduction point keys and onion handshake keys
7952 have a public exponent of 65537. Starts to fix bug 3207; bugfix
7956 - Caches no longer download and serve v2 networkstatus documents
7957 unless FetchV2Networkstatus flag is set: these documents haven't
7958 haven't been used by clients or relays since 0.2.0.x. Resolves
7962 Changes in version 0.2.3.1-alpha - 2011-05-05
7963 Tor 0.2.3.1-alpha adds some new experimental features, including support
7964 for an improved network IO backend, IOCP networking on Windows,
7965 microdescriptor caching, "fast-start" support for streams, and automatic
7966 home router configuration. There are also numerous internal improvements
7967 to try to make the code easier for developers to work with.
7969 This is the first alpha release in a new series, so expect there to be
7970 bugs. Users who would rather test out a more stable branch should
7971 stay with 0.2.2.x for now.
7974 - Tor can now optionally build with the "bufferevents" buffered IO
7975 backend provided by Libevent 2. To use this feature, make sure you
7976 have the latest possible version of Libevent, and pass the
7977 --enable-bufferevents flag to configure when building Tor from
7978 source. This feature will make our networking code more flexible,
7979 let us stack layers on each other, and let us use more efficient
7980 zero-copy transports where available.
7981 - As an experimental feature, Tor can use IOCP for networking on Windows.
7982 Once this code is tuned and optimized, it promises much better
7983 performance than the select-based backend we've used in the past. To
7984 try this feature, you must build Tor with Libevent 2, configure Tor
7985 with the "bufferevents" buffered IO backend, and add "DisableIOCP 0" to
7986 your torrc. There are known bugs here: only try this if you can help
7987 debug it as it breaks.
7988 - The EntryNodes option can now include country codes like {de} or IP
7989 addresses or network masks. Previously we had disallowed these options
7990 because we didn't have an efficient way to keep the list up to
7991 date. Fixes bug 1982, but see bug 2798 for an unresolved issue here.
7992 - Exit nodes now accept and queue data on not-yet-connected streams.
7993 Previously, the client wasn't allowed to send data until the stream was
7994 connected, which slowed down all connections. This change will enable
7995 clients to perform a "fast-start" on streams and send data without
7996 having to wait for a confirmation that the stream has opened. (Patch
7997 from Ian Goldberg; implements the server side of Proposal 174.)
7998 - Tor now has initial support for automatic port mapping on the many
7999 home routers that support NAT-PMP or UPnP. (Not yet supported on
8000 Windows). To build the support code, you'll need to have libnatpnp
8001 library and/or the libminiupnpc library, and you'll need to enable the
8002 feature specifically by passing "--enable-upnp" and/or
8003 "--enable-natpnp" to configure. To turn it on, use the new
8004 PortForwarding option.
8005 - Caches now download, cache, and serve multiple "flavors" of the
8006 consensus, including a flavor that describes microdescriptors.
8007 - Caches now download, cache, and serve microdescriptors -- small
8008 summaries of router descriptors that are authenticated by all of the
8009 directory authorities. Once enough caches are running this code,
8010 clients will be able to save significant amounts of directory bandwidth
8011 by downloading microdescriptors instead of router descriptors.
8014 - Make logging resolution configurable with a new LogTimeGranularity
8015 option, and change the default from 1 millisecond to 1 second.
8016 Implements enhancement 1668.
8017 - We log which torrc file we're using on startup. Implements ticket
8019 - Ordinarily, Tor does not count traffic from private addresses (like
8020 127.0.0.1 or 10.0.0.1) when calculating rate limits or accounting.
8021 There is now a new option, CountPrivateBandwidth, to disable this
8022 behavior. Patch from Daniel Cagara.
8023 - New --enable-static-tor configure option for building Tor as
8024 statically as possible. Idea, general hackery and thoughts from
8025 Alexei Czeskis, John Gilmore, Jacob Appelbaum. Implements ticket
8027 - If you set the NumCPUs option to 0, Tor will now try to detect how
8028 many CPUs you have. This is the new default behavior.
8029 - Turn on directory request statistics by default and include them in
8030 extra-info descriptors. Don't break if we have no GeoIP database.
8031 - Relays that set "ConnDirectionStatistics 1" write statistics on the
8032 bidirectional use of connections to disk every 24 hours.
8033 - Add a GeoIP file digest to the extra-info descriptor. Implements
8035 - The NodeFamily option -- which let you declare that you want to
8036 consider nodes to be part of a family whether they list themselves
8037 that way or not -- now allows IP address ranges and country codes.
8038 - Add a new 'Heartbeat' log message type to periodically log a message
8039 describing Tor's status at level Notice. This feature is meant for
8040 operators who log at notice, and want to make sure that their Tor
8041 server is still working. Implementation by George Kadianakis.
8043 o Minor bugfixes (on 0.2.2.25-alpha):
8044 - When loading the microdesc journal, remember its current size.
8045 In 0.2.2, this helps prevent the microdesc journal from growing
8046 without limit on authorities (who are the only ones to use it in
8047 0.2.2). Fixes a part of bug 2230; bugfix on 0.2.2.6-alpha.
8048 Fix posted by "cypherpunks."
8049 - The microdesc journal is supposed to get rebuilt only if it is
8050 at least _half_ the length of the store, not _twice_ the length
8051 of the store. Bugfix on 0.2.2.6-alpha; fixes part of bug 2230.
8052 - If as an authority we fail to compute the identity digest of a v3
8053 legacy keypair, warn, and don't use a buffer-full of junk instead.
8054 Bugfix on 0.2.1.1-alpha; fixes bug 3106.
8055 - Authorities now clean their microdesc cache periodically and when
8056 reading from disk initially, not only when adding new descriptors.
8057 This prevents a bug where we could lose microdescriptors. Bugfix
8060 o Minor features (controller):
8061 - Add a new SIGNAL event to the controller interface so that
8062 controllers can be notified when Tor handles a signal. Resolves
8063 issue 1955. Patch by John Brooks.
8064 - Add a new GETINFO option to get total bytes read and written. Patch
8065 from pipe, revised by atagar. Resolves ticket 2345.
8066 - Implement some GETINFO controller fields to provide information about
8067 the Tor process's pid, euid, username, and resource limits.
8070 - Our build system requires automake 1.6 or later to create the
8071 Makefile.in files. Previously, you could have used 1.4.
8072 This only affects developers and people building Tor from git;
8073 people who build Tor from the source distribution without changing
8074 the Makefile.am files should be fine.
8075 - Our autogen.sh script uses autoreconf to launch autoconf, automake, and
8076 so on. This is more robust against some of the failure modes
8077 associated with running the autotools pieces on their own.
8079 o Minor packaging issues:
8080 - On OpenSUSE, create the /var/run/tor directory on startup if it is not
8081 already created. Patch from Andreas Stieger. Fixes bug 2573.
8083 o Code simplifications and refactoring:
8084 - A major revision to our internal node-selecting and listing logic.
8085 Tor already had at least two major ways to look at the question of
8086 "which Tor servers do we know about": a list of router descriptors,
8087 and a list of entries in the current consensus. With
8088 microdescriptors, we're adding a third. Having so many systems
8089 without an abstraction layer over them was hurting the codebase.
8090 Now, we have a new "node_t" abstraction that presents a consistent
8091 interface to a client's view of a Tor node, and holds (nearly) all
8092 of the mutable state formerly in routerinfo_t and routerstatus_t.
8093 - The helper programs tor-gencert, tor-resolve, and tor-checkkey
8094 no longer link against Libevent: they never used it, but
8095 our library structure used to force them to link it.
8098 - Remove some old code to work around even older versions of Tor that
8099 used forked processes to handle DNS requests. Such versions of Tor
8100 are no longer in use as servers.
8102 o Documentation fixes:
8103 - Correct a broken faq link in the INSTALL file. Fixes bug 2307.
8104 - Add missing documentation for the authority-related torrc options
8105 RephistTrackTime, BridgePassword, and V3AuthUseLegacyKey. Resolves
8109 Changes in version 0.2.2.25-alpha - 2011-04-29
8110 Tor 0.2.2.25-alpha fixes many bugs: hidden service clients are more
8111 robust, routers no longer overreport their bandwidth, Win7 should crash
8112 a little less, and NEWNYM (as used by Vidalia's "new identity" button)
8113 now prevents hidden service-related activity from being linkable. It
8114 provides more information to Vidalia so you can see if your bridge is
8115 working. Also, 0.2.2.25-alpha revamps the Entry/Exit/ExcludeNodes and
8116 StrictNodes configuration options to make them more reliable, more
8117 understandable, and more regularly applied. If you use those options,
8118 please see the revised documentation for them in the manual page.
8121 - Relays were publishing grossly inflated bandwidth values because
8122 they were writing their state files wrong--now they write the
8123 correct value. Also, resume reading bandwidth history from the
8124 state file correctly. Fixes bug 2704; bugfix on 0.2.2.23-alpha.
8125 - Improve hidden service robustness: When we find that we have
8126 extended a hidden service's introduction circuit to a relay not
8127 listed as an introduction point in the HS descriptor we currently
8128 have, retry with an introduction point from the current
8129 descriptor. Previously we would just give up. Fixes bugs 1024 and
8130 1930; bugfix on 0.2.0.10-alpha.
8131 - Clients now stop trying to use an exit node associated with a given
8132 destination by TrackHostExits if they fail to reach that exit node.
8133 Fixes bug 2999. Bugfix on 0.2.0.20-rc.
8134 - Fix crash bug on platforms where gmtime and localtime can return
8135 NULL. Windows 7 users were running into this one. Fixes part of bug
8136 2077. Bugfix on all versions of Tor. Found by boboper.
8138 o Security and stability fixes:
8139 - Don't double-free a parsable, but invalid, microdescriptor, even if
8140 it is followed in the blob we're parsing by an unparsable
8141 microdescriptor. Fixes an issue reported in a comment on bug 2954.
8142 Bugfix on 0.2.2.6-alpha; fix by "cypherpunks".
8143 - If the Nickname configuration option isn't given, Tor would pick a
8144 nickname based on the local hostname as the nickname for a relay.
8145 Because nicknames are not very important in today's Tor and the
8146 "Unnamed" nickname has been implemented, this is now problematic
8147 behavior: It leaks information about the hostname without being
8148 useful at all. Fixes bug 2979; bugfix on 0.1.2.2-alpha, which
8149 introduced the Unnamed nickname. Reported by tagnaq.
8150 - Fix an uncommon assertion failure when running with DNSPort under
8151 heavy load. Fixes bug 2933; bugfix on 0.2.0.1-alpha.
8152 - Avoid linkability based on cached hidden service descriptors: forget
8153 all hidden service descriptors cached as a client when processing a
8154 SIGNAL NEWNYM command. Fixes bug 3000; bugfix on 0.0.6.
8157 - Export GeoIP information on bridge usage to controllers even if we
8158 have not yet been running for 24 hours. Now Vidalia bridge operators
8159 can get more accurate and immediate feedback about their
8160 contributions to the network.
8162 o Major features and bugfixes (node selection):
8163 - Revise and reconcile the meaning of the ExitNodes, EntryNodes,
8164 ExcludeEntryNodes, ExcludeExitNodes, ExcludeNodes, and StrictNodes
8165 options. Previously, we had been ambiguous in describing what
8166 counted as an "exit" node, and what operations exactly "StrictNodes
8167 0" would permit. This created confusion when people saw nodes built
8168 through unexpected circuits, and made it hard to tell real bugs from
8169 surprises. Now the intended behavior is:
8170 . "Exit", in the context of ExitNodes and ExcludeExitNodes, means
8171 a node that delivers user traffic outside the Tor network.
8172 . "Entry", in the context of EntryNodes, means a node used as the
8173 first hop of a multihop circuit. It doesn't include direct
8174 connections to directory servers.
8175 . "ExcludeNodes" applies to all nodes.
8176 . "StrictNodes" changes the behavior of ExcludeNodes only. When
8177 StrictNodes is set, Tor should avoid all nodes listed in
8178 ExcludeNodes, even when it will make user requests fail. When
8179 StrictNodes is *not* set, then Tor should follow ExcludeNodes
8180 whenever it can, except when it must use an excluded node to
8181 perform self-tests, connect to a hidden service, provide a
8182 hidden service, fulfill a .exit request, upload directory
8183 information, or fetch directory information.
8184 Collectively, the changes to implement the behavior fix bug 1090.
8185 - ExcludeNodes now takes precedence over EntryNodes and ExitNodes: if
8186 a node is listed in both, it's treated as excluded.
8187 - ExcludeNodes now applies to directory nodes -- as a preference if
8188 StrictNodes is 0, or an absolute requirement if StrictNodes is 1.
8189 Don't exclude all the directory authorities and set StrictNodes to 1
8190 unless you really want your Tor to break.
8191 - ExcludeNodes and ExcludeExitNodes now override exit enclaving.
8192 - ExcludeExitNodes now overrides .exit requests.
8193 - We don't use bridges listed in ExcludeNodes.
8194 - When StrictNodes is 1:
8195 . We now apply ExcludeNodes to hidden service introduction points
8196 and to rendezvous points selected by hidden service users. This
8197 can make your hidden service less reliable: use it with caution!
8198 . If we have used ExcludeNodes on ourself, do not try relay
8199 reachability self-tests.
8200 . If we have excluded all the directory authorities, we will not
8201 even try to upload our descriptor if we're a relay.
8202 . Do not honor .exit requests to an excluded node.
8203 - Remove a misfeature that caused us to ignore the Fast/Stable flags
8204 when ExitNodes is set. Bugfix on 0.2.2.7-alpha.
8205 - When the set of permitted nodes changes, we now remove any mappings
8206 introduced via TrackExitHosts to now-excluded nodes. Bugfix on
8208 - We never cannibalize a circuit that had excluded nodes on it, even
8209 if StrictNodes is 0. Bugfix on 0.1.0.1-rc.
8210 - Revert a change where we would be laxer about attaching streams to
8211 circuits than when building the circuits. This was meant to prevent
8212 a set of bugs where streams were never attachable, but our improved
8213 code here should make this unnecessary. Bugfix on 0.2.2.7-alpha.
8214 - Keep track of how many times we launch a new circuit to handle a
8215 given stream. Too many launches could indicate an inconsistency
8216 between our "launch a circuit to handle this stream" logic and our
8217 "attach this stream to one of the available circuits" logic.
8218 - Improve log messages related to excluded nodes.
8221 - Fix a spurious warning when moving from a short month to a long
8222 month on relays with month-based BandwidthAccounting. Bugfix on
8223 0.2.2.17-alpha; fixes bug 3020.
8224 - When a client finds that an origin circuit has run out of 16-bit
8225 stream IDs, we now mark it as unusable for new streams. Previously,
8226 we would try to close the entire circuit. Bugfix on 0.0.6.
8227 - Add a forgotten cast that caused a compile warning on OS X 10.6.
8228 Bugfix on 0.2.2.24-alpha.
8229 - Be more careful about reporting the correct error from a failed
8230 connect() system call. Under some circumstances, it was possible to
8231 look at an incorrect value for errno when sending the end reason.
8232 Bugfix on 0.1.0.1-rc.
8233 - Correctly handle an "impossible" overflow cases in connection byte
8234 counting, where we write or read more than 4GB on an edge connection
8235 in a single second. Bugfix on 0.1.2.8-beta.
8236 - Correct the warning displayed when a rendezvous descriptor exceeds
8237 the maximum size. Fixes bug 2750; bugfix on 0.2.1.5-alpha. Found by
8239 - Clients and hidden services now use HSDir-flagged relays for hidden
8240 service descriptor downloads and uploads even if the relays have no
8241 DirPort set and the client has disabled TunnelDirConns. This will
8242 eventually allow us to give the HSDir flag to relays with no
8243 DirPort. Fixes bug 2722; bugfix on 0.2.1.6-alpha.
8244 - Downgrade "no current certificates known for authority" message from
8245 Notice to Info. Fixes bug 2899; bugfix on 0.2.0.10-alpha.
8246 - Make the SIGNAL DUMP control-port command work on FreeBSD. Fixes bug
8247 2917. Bugfix on 0.1.1.1-alpha.
8248 - Only limit the lengths of single HS descriptors, even when multiple
8249 HS descriptors are published to an HSDir relay in a single POST
8250 operation. Fixes bug 2948; bugfix on 0.2.1.5-alpha. Found by hsdir.
8251 - Write the current time into the LastWritten line in our state file,
8252 rather than the time from the previous write attempt. Also, stop
8253 trying to use a time of -1 in our log statements. Fixes bug 3039;
8254 bugfix on 0.2.2.14-alpha.
8255 - Be more consistent in our treatment of file system paths. "~" should
8256 get expanded to the user's home directory in the Log config option.
8257 Fixes bug 2971; bugfix on 0.2.0.1-alpha, which introduced the
8258 feature for the -f and --DataDirectory options.
8261 - Make sure every relay writes a state file at least every 12 hours.
8262 Previously, a relay could go for weeks without writing its state
8263 file, and on a crash could lose its bandwidth history, capacity
8264 estimates, client country statistics, and so on. Addresses bug 3012.
8265 - Send END_STREAM_REASON_NOROUTE in response to EHOSTUNREACH errors.
8266 Clients before 0.2.1.27 didn't handle NOROUTE correctly, but such
8267 clients are already deprecated because of security bugs.
8268 - Don't allow v0 hidden service authorities to act as clients.
8269 Required by fix for bug 3000.
8270 - Ignore SIGNAL NEWNYM commands on relay-only Tor instances. Required
8271 by fix for bug 3000.
8272 - Ensure that no empty [dirreq-](read|write)-history lines are added
8273 to an extrainfo document. Implements ticket 2497.
8275 o Code simplification and refactoring:
8276 - Remove workaround code to handle directory responses from servers
8277 that had bug 539 (they would send HTTP status 503 responses _and_
8278 send a body too). Since only server versions before
8279 0.2.0.16-alpha/0.1.2.19 were affected, there is no longer reason to
8280 keep the workaround in place.
8281 - Remove the old 'fuzzy time' logic. It was supposed to be used for
8282 handling calculations where we have a known amount of clock skew and
8283 an allowed amount of unknown skew. But we only used it in three
8284 places, and we never adjusted the known/unknown skew values. This is
8285 still something we might want to do someday, but if we do, we'll
8286 want to do it differently.
8287 - Avoid signed/unsigned comparisons by making SIZE_T_CEILING unsigned.
8288 None of the cases where we did this before were wrong, but by making
8289 this change we avoid warnings. Fixes bug 2475; bugfix on 0.2.1.28.
8290 - Use GetTempDir to find the proper temporary directory location on
8291 Windows when generating temporary files for the unit tests. Patch by
8295 Changes in version 0.2.2.24-alpha - 2011-04-08
8296 Tor 0.2.2.24-alpha fixes a variety of bugs, including a big bug that
8297 prevented Tor clients from effectively using "multihomed" bridges,
8298 that is, bridges that listen on multiple ports or IP addresses so users
8299 can continue to use some of their addresses even if others get blocked.
8302 - Fix a bug where bridge users who configure the non-canonical
8303 address of a bridge automatically switch to its canonical
8304 address. If a bridge listens at more than one address, it should be
8305 able to advertise those addresses independently and any non-blocked
8306 addresses should continue to work. Bugfix on Tor 0.2.0.x. Fixes
8308 - If you configured Tor to use bridge A, and then quit and
8309 configured Tor to use bridge B instead, it would happily continue
8310 to use bridge A if it's still reachable. While this behavior is
8311 a feature if your goal is connectivity, in some scenarios it's a
8312 dangerous bug. Bugfix on Tor 0.2.0.1-alpha; fixes bug 2511.
8313 - Directory authorities now use data collected from their own
8314 uptime observations when choosing whether to assign the HSDir flag
8315 to relays, instead of trusting the uptime value the relay reports in
8316 its descriptor. This change helps prevent an attack where a small
8317 set of nodes with frequently-changing identity keys can blackhole
8318 a hidden service. (Only authorities need upgrade; others will be
8319 fine once they do.) Bugfix on 0.2.0.10-alpha; fixes bug 2709.
8322 - When we restart our relay, we might get a successful connection
8323 from the outside before we've started our reachability tests,
8324 triggering a warning: "ORPort found reachable, but I have no
8325 routerinfo yet. Failing to inform controller of success." This
8326 bug was harmless unless Tor is running under a controller
8327 like Vidalia, in which case the controller would never get a
8328 REACHABILITY_SUCCEEDED status event. Bugfix on 0.1.2.6-alpha;
8330 - Make directory authorities more accurate at recording when
8331 relays that have failed several reachability tests became
8332 unreachable, so we can provide more accuracy at assigning Stable,
8333 Guard, HSDir, etc flags. Bugfix on 0.2.0.6-alpha. Resolves bug 2716.
8334 - Fix an issue that prevented static linking of libevent on
8335 some platforms (notably Linux). Fixes bug 2698; bugfix on
8336 versions 0.2.1.23/0.2.2.8-alpha (the versions introducing
8337 the --with-static-libevent configure option).
8338 - We now ask the other side of a stream (the client or the exit)
8339 for more data on that stream when the amount of queued data on
8340 that stream dips low enough. Previously, we wouldn't ask the
8341 other side for more data until either it sent us more data (which
8342 it wasn't supposed to do if it had exhausted its window!) or we
8343 had completely flushed all our queued data. This flow control fix
8344 should improve throughput. Fixes bug 2756; bugfix on the earliest
8345 released versions of Tor (svn commit r152).
8346 - Avoid a double-mark-for-free warning when failing to attach a
8347 transparent proxy connection. (We thought we had fixed this in
8348 0.2.2.23-alpha, but it turns out our fix was checking the wrong
8349 connection.) Fixes bug 2757; bugfix on 0.1.2.1-alpha (the original
8350 bug) and 0.2.2.23-alpha (the incorrect fix).
8351 - When warning about missing zlib development packages during compile,
8352 give the correct package names. Bugfix on 0.2.0.1-alpha.
8355 - Directory authorities now log the source of a rejected POSTed v3
8357 - Make compilation with clang possible when using
8358 --enable-gcc-warnings by removing two warning options that clang
8359 hasn't implemented yet and by fixing a few warnings. Implements
8361 - When expiring circuits, use microsecond timers rather than
8362 one-second timers. This can avoid an unpleasant situation where a
8363 circuit is launched near the end of one second and expired right
8364 near the beginning of the next, and prevent fluctuations in circuit
8366 - Use computed circuit-build timeouts to decide when to launch
8367 parallel introduction circuits for hidden services. (Previously,
8368 we would retry after 15 seconds.)
8369 - Update to the April 1 2011 Maxmind GeoLite Country database.
8372 - Create the /var/run/tor directory on startup on OpenSUSE if it is
8373 not already created. Patch from Andreas Stieger. Fixes bug 2573.
8375 o Documentation changes:
8376 - Modernize the doxygen configuration file slightly. Fixes bug 2707.
8377 - Resolve all doxygen warnings except those for missing documentation.
8379 - Add doxygen documentation for more functions, fields, and types.
8382 Changes in version 0.2.2.23-alpha - 2011-03-08
8383 Tor 0.2.2.23-alpha lets relays record their bandwidth history so when
8384 they restart they don't lose their bandwidth capacity estimate. This
8385 release also fixes a diverse set of user-facing bugs, ranging from
8386 relays overrunning their rate limiting to clients falsely warning about
8387 clock skew to bridge descriptor leaks by our bridge directory authority.
8390 - Stop sending a CLOCK_SKEW controller status event whenever
8391 we fetch directory information from a relay that has a wrong clock.
8392 Instead, only inform the controller when it's a trusted authority
8393 that claims our clock is wrong. Bugfix on 0.1.2.6-alpha; fixes
8394 the rest of bug 1074.
8395 - Fix an assert in parsing router descriptors containing IPv6
8396 addresses. This one took down the directory authorities when
8397 somebody tried some experimental code. Bugfix on 0.2.1.3-alpha.
8398 - Make the bridge directory authority refuse to answer directory
8399 requests for "all" descriptors. It used to include bridge
8400 descriptors in its answer, which was a major information leak.
8401 Found by "piebeer". Bugfix on 0.2.0.3-alpha.
8402 - If relays set RelayBandwidthBurst but not RelayBandwidthRate,
8403 Tor would ignore their RelayBandwidthBurst setting,
8404 potentially using more bandwidth than expected. Bugfix on
8405 0.2.0.1-alpha. Reported by Paul Wouters. Fixes bug 2470.
8406 - Ignore and warn if the user mistakenly sets "PublishServerDescriptor
8407 hidserv" in her torrc. The 'hidserv' argument never controlled
8408 publication of hidden service descriptors. Bugfix on 0.2.0.1-alpha.
8411 - Relays now save observed peak bandwidth throughput rates to their
8412 state file (along with total usage, which was already saved)
8413 so that they can determine their correct estimated bandwidth on
8414 restart. Resolves bug 1863, where Tor relays would reset their
8415 estimated bandwidth to 0 after restarting.
8416 - Directory authorities now take changes in router IP address and
8417 ORPort into account when determining router stability. Previously,
8418 if a router changed its IP or ORPort, the authorities would not
8419 treat it as having any downtime for the purposes of stability
8420 calculation, whereas clients would experience downtime since the
8421 change could take a while to propagate to them. Resolves issue 1035.
8422 - Enable Address Space Layout Randomization (ASLR) and Data Execution
8423 Prevention (DEP) by default on Windows to make it harder for
8424 attackers to exploit vulnerabilities. Patch from John Brooks.
8426 o Minor bugfixes (on 0.2.1.x and earlier):
8427 - Fix a rare crash bug that could occur when a client was configured
8428 with a large number of bridges. Fixes bug 2629; bugfix on
8429 0.2.1.2-alpha. Bugfix by trac user "shitlei".
8430 - Avoid a double mark-for-free warning when failing to attach a
8431 transparent proxy connection. Bugfix on 0.1.2.1-alpha. Fixes
8433 - Correctly detect failure to allocate an OpenSSL BIO. Fixes bug 2378;
8434 found by "cypherpunks". This bug was introduced before the first
8435 Tor release, in svn commit r110.
8436 - Country codes aren't supported in EntryNodes until 0.2.3.x, so
8437 don't mention them in the manpage. Fixes bug 2450; issue
8438 spotted by keb and G-Lo.
8439 - Fix a bug in bandwidth history state parsing that could have been
8440 triggered if a future version of Tor ever changed the timing
8441 granularity at which bandwidth history is measured. Bugfix on
8443 - When a relay decides that its DNS is too broken for it to serve
8444 as an exit server, it advertised itself as a non-exit, but
8445 continued to act as an exit. This could create accidental
8446 partitioning opportunities for users. Instead, if a relay is
8447 going to advertise reject *:* as its exit policy, it should
8448 really act with exit policy "reject *:*". Fixes bug 2366.
8449 Bugfix on Tor 0.1.2.5-alpha. Bugfix by user "postman" on trac.
8450 - In the special case where you configure a public exit relay as your
8451 bridge, Tor would be willing to use that exit relay as the last
8452 hop in your circuit as well. Now we fail that circuit instead.
8453 Bugfix on 0.2.0.12-alpha. Fixes bug 2403. Reported by "piebeer".
8454 - Fix a bug with our locking implementation on Windows that couldn't
8455 correctly detect when a file was already locked. Fixes bug 2504,
8456 bugfix on 0.2.1.6-alpha.
8457 - Fix IPv6-related connect() failures on some platforms (BSD, OS X).
8458 Bugfix on 0.2.0.3-alpha; fixes first part of bug 2660. Patch by
8460 - Set target port in get_interface_address6() correctly. Bugfix
8461 on 0.1.1.4-alpha and 0.2.0.3-alpha; fixes second part of bug 2660.
8462 - Directory authorities are now more robust to hops back in time
8463 when calculating router stability. Previously, if a run of uptime
8464 or downtime appeared to be negative, the calculation could give
8465 incorrect results. Bugfix on 0.2.0.6-alpha; noticed when fixing
8467 - Fix an assert that got triggered when using the TestingTorNetwork
8468 configuration option and then issuing a GETINFO config-text control
8469 command. Fixes bug 2250; bugfix on 0.2.1.2-alpha.
8471 o Minor bugfixes (on 0.2.2.x):
8472 - Clients should not weight BadExit nodes as Exits in their node
8473 selection. Similarly, directory authorities should not count BadExit
8474 bandwidth as Exit bandwidth when computing bandwidth-weights.
8475 Bugfix on 0.2.2.10-alpha; fixes bug 2203.
8476 - Correctly clear our dir_read/dir_write history when there is an
8477 error parsing any bw history value from the state file. Bugfix on
8479 - Resolve a bug in verifying signatures of directory objects
8480 with digests longer than SHA1. Bugfix on 0.2.2.20-alpha.
8481 Fixes bug 2409. Found by "piebeer".
8482 - Bridge authorities no longer crash on SIGHUP when they try to
8483 publish their relay descriptor to themselves. Fixes bug 2572. Bugfix
8487 - Log less aggressively about circuit timeout changes, and improve
8488 some other circuit timeout messages. Resolves bug 2004.
8489 - Log a little more clearly about the times at which we're no longer
8490 accepting new connections. Resolves bug 2181.
8491 - Reject attempts at the client side to open connections to private
8492 IP addresses (like 127.0.0.1, 10.0.0.1, and so on) with
8493 a randomly chosen exit node. Attempts to do so are always
8494 ill-defined, generally prevented by exit policies, and usually
8495 in error. This will also help to detect loops in transparent
8496 proxy configurations. You can disable this feature by setting
8497 "ClientRejectInternalAddresses 0" in your torrc.
8498 - Always treat failure to allocate an RSA key as an unrecoverable
8500 - Update to the March 1 2011 Maxmind GeoLite Country database.
8502 o Minor features (log subsystem):
8503 - Add documentation for configuring logging at different severities in
8504 different log domains. We've had this feature since 0.2.1.1-alpha,
8505 but for some reason it never made it into the manpage. Fixes
8507 - Make it simpler to specify "All log domains except for A and B".
8508 Previously you needed to say "[*,~A,~B]". Now you can just say
8510 - Add a "LogMessageDomains 1" option to include the domains of log
8511 messages along with the messages. Without this, there's no way
8512 to use log domains without reading the source or doing a lot
8515 o Packaging changes:
8516 - Stop shipping the Tor specs files and development proposal documents
8517 in the tarball. They are now in a separate git repository at
8518 git://git.torproject.org/torspec.git
8521 Changes in version 0.2.1.30 - 2011-02-23
8522 Tor 0.2.1.30 fixes a variety of less critical bugs. The main other
8523 change is a slight tweak to Tor's TLS handshake that makes relays
8524 and bridges that run this new version reachable from Iran again.
8525 We don't expect this tweak will win the arms race long-term, but it
8526 buys us time until we roll out a better solution.
8529 - Stop sending a CLOCK_SKEW controller status event whenever
8530 we fetch directory information from a relay that has a wrong clock.
8531 Instead, only inform the controller when it's a trusted authority
8532 that claims our clock is wrong. Bugfix on 0.1.2.6-alpha; fixes
8533 the rest of bug 1074.
8534 - Fix a bounds-checking error that could allow an attacker to
8535 remotely crash a directory authority. Bugfix on 0.2.1.5-alpha.
8537 - If relays set RelayBandwidthBurst but not RelayBandwidthRate,
8538 Tor would ignore their RelayBandwidthBurst setting,
8539 potentially using more bandwidth than expected. Bugfix on
8540 0.2.0.1-alpha. Reported by Paul Wouters. Fixes bug 2470.
8541 - Ignore and warn if the user mistakenly sets "PublishServerDescriptor
8542 hidserv" in her torrc. The 'hidserv' argument never controlled
8543 publication of hidden service descriptors. Bugfix on 0.2.0.1-alpha.
8546 - Adjust our TLS Diffie-Hellman parameters to match those used by
8548 - Update to the February 1 2011 Maxmind GeoLite Country database.
8551 - Check for and reject overly long directory certificates and
8552 directory tokens before they have a chance to hit any assertions.
8553 Bugfix on 0.2.1.28. Found by "doorss".
8554 - Bring the logic that gathers routerinfos and assesses the
8555 acceptability of circuits into line. This prevents a Tor OP from
8556 getting locked in a cycle of choosing its local OR as an exit for a
8557 path (due to a .exit request) and then rejecting the circuit because
8558 its OR is not listed yet. It also prevents Tor clients from using an
8559 OR running in the same instance as an exit (due to a .exit request)
8560 if the OR does not meet the same requirements expected of an OR
8561 running elsewhere. Fixes bug 1859; bugfix on 0.1.0.1-rc.
8563 o Packaging changes:
8564 - Stop shipping the Tor specs files and development proposal documents
8565 in the tarball. They are now in a separate git repository at
8566 git://git.torproject.org/torspec.git
8567 - Do not include Git version tags as though they are SVN tags when
8568 generating a tarball from inside a repository that has switched
8569 between branches. Bugfix on 0.2.1.15-rc; fixes bug 2402.
8572 Changes in version 0.2.2.22-alpha - 2011-01-25
8573 Tor 0.2.2.22-alpha fixes a few more less-critical security issues. The
8574 main other change is a slight tweak to Tor's TLS handshake that makes
8575 relays and bridges that run this new version reachable from Iran again.
8576 We don't expect this tweak will win the arms race long-term, but it
8577 will buy us a bit more time until we roll out a better solution.
8580 - Fix a bounds-checking error that could allow an attacker to
8581 remotely crash a directory authority. Bugfix on 0.2.1.5-alpha.
8583 - Don't assert when changing from bridge to relay or vice versa
8584 via the controller. The assert happened because we didn't properly
8585 initialize our keys in this case. Bugfix on 0.2.2.18-alpha; fixes
8586 bug 2433. Reported by bastik.
8589 - Adjust our TLS Diffie-Hellman parameters to match those used by
8591 - Provide a log message stating which geoip file we're parsing
8592 instead of just stating that we're parsing the geoip file.
8593 Implements ticket 2432.
8596 - Check for and reject overly long directory certificates and
8597 directory tokens before they have a chance to hit any assertions.
8598 Bugfix on 0.2.1.28 / 0.2.2.20-alpha. Found by "doorss".
8601 Changes in version 0.2.2.21-alpha - 2011-01-15
8602 Tor 0.2.2.21-alpha includes all the patches from Tor 0.2.1.29, which
8603 continues our recent code security audit work. The main fix resolves
8604 a remote heap overflow vulnerability that can allow remote code
8605 execution (CVE-2011-0427). Other fixes address a variety of assert
8606 and crash bugs, most of which we think are hard to exploit remotely.
8608 o Major bugfixes (security), also included in 0.2.1.29:
8609 - Fix a heap overflow bug where an adversary could cause heap
8610 corruption. This bug probably allows remote code execution
8611 attacks. Reported by "debuger". Fixes CVE-2011-0427. Bugfix on
8613 - Prevent a denial-of-service attack by disallowing any
8614 zlib-compressed data whose compression factor is implausibly
8615 high. Fixes part of bug 2324; reported by "doorss".
8616 - Zero out a few more keys in memory before freeing them. Fixes
8617 bug 2384 and part of bug 2385. These key instances found by
8618 "cypherpunks", based on Andrew Case's report about being able
8619 to find sensitive data in Tor's memory space if you have enough
8620 permissions. Bugfix on 0.0.2pre9.
8622 o Major bugfixes (crashes), also included in 0.2.1.29:
8623 - Prevent calls to Libevent from inside Libevent log handlers.
8624 This had potential to cause a nasty set of crashes, especially
8625 if running Libevent with debug logging enabled, and running
8626 Tor with a controller watching for low-severity log messages.
8627 Bugfix on 0.1.0.2-rc. Fixes bug 2190.
8628 - Add a check for SIZE_T_MAX to tor_realloc() to try to avoid
8629 underflow errors there too. Fixes the other part of bug 2324.
8630 - Fix a bug where we would assert if we ever had a
8631 cached-descriptors.new file (or another file read directly into
8632 memory) of exactly SIZE_T_CEILING bytes. Fixes bug 2326; bugfix
8633 on 0.2.1.25. Found by doorss.
8634 - Fix some potential asserts and parsing issues with grossly
8635 malformed router caches. Fixes bug 2352; bugfix on Tor 0.2.1.27.
8638 o Minor bugfixes (other), also included in 0.2.1.29:
8639 - Fix a bug with handling misformed replies to reverse DNS lookup
8640 requests in DNSPort. Bugfix on Tor 0.2.0.1-alpha. Related to a
8641 bug reported by doorss.
8642 - Fix compilation on mingw when a pthreads compatibility library
8643 has been installed. (We don't want to use it, so we shouldn't
8644 be including pthread.h.) Fixes bug 2313; bugfix on 0.1.0.1-rc.
8645 - Fix a bug where we would declare that we had run out of virtual
8646 addresses when the address space was only half-exhausted. Bugfix
8648 - Correctly handle the case where AutomapHostsOnResolve is set but
8649 no virtual addresses are available. Fixes bug 2328; bugfix on
8650 0.1.2.1-alpha. Bug found by doorss.
8651 - Correctly handle wrapping around when we run out of virtual
8652 address space. Found by cypherpunks; bugfix on 0.2.0.5-alpha.
8654 o Minor features, also included in 0.2.1.29:
8655 - Update to the January 1 2011 Maxmind GeoLite Country database.
8656 - Introduce output size checks on all of our decryption functions.
8658 o Build changes, also included in 0.2.1.29:
8659 - Tor does not build packages correctly with Automake 1.6 and earlier;
8660 added a check to Makefile.am to make sure that we're building with
8661 Automake 1.7 or later.
8662 - The 0.2.1.28 tarball was missing src/common/OpenBSD_malloc_Linux.c
8663 because we built it with a too-old version of automake. Thus that
8664 release broke ./configure --enable-openbsd-malloc, which is popular
8665 among really fast exit relays on Linux.
8667 o Major bugfixes, new in 0.2.2.21-alpha:
8668 - Prevent crash/heap corruption when the cbtnummodes consensus
8669 parameter is set to 0 or large values. Fixes bug 2317; bugfix
8672 o Major features, new in 0.2.2.21-alpha:
8673 - Introduce minimum/maximum values that clients will believe
8674 from the consensus. Now we'll have a better chance to avoid crashes
8675 or worse when a consensus param has a weird value.
8677 o Minor features, new in 0.2.2.21-alpha:
8678 - Make sure to disable DirPort if running as a bridge. DirPorts aren't
8679 used on bridges, and it makes bridge scanning somewhat easier.
8680 - If writing the state file to disk fails, wait up to an hour before
8681 retrying again, rather than trying again each second. Fixes bug
8682 2346; bugfix on Tor 0.1.1.3-alpha.
8683 - Make Libevent log messages get delivered to controllers later,
8684 and not from inside the Libevent log handler. This prevents unsafe
8685 reentrant Libevent calls while still letting the log messages
8687 - Detect platforms that brokenly use a signed size_t, and refuse to
8688 build there. Found and analyzed by doorss and rransom.
8689 - Fix a bunch of compile warnings revealed by mingw with gcc 4.5.
8692 o Minor bugfixes, new in 0.2.2.21-alpha:
8693 - Handle SOCKS messages longer than 128 bytes long correctly, rather
8694 than waiting forever for them to finish. Fixes bug 2330; bugfix
8695 on 0.2.0.16-alpha. Found by doorss.
8696 - Add assertions to check for overflow in arguments to
8697 base32_encode() and base32_decode(); fix a signed-unsigned
8698 comparison there too. These bugs are not actually reachable in Tor,
8699 but it's good to prevent future errors too. Found by doorss.
8700 - Correctly detect failures to create DNS requests when using Libevent
8701 versions before v2. (Before Libevent 2, we used our own evdns
8702 implementation. Its return values for Libevent's evdns_resolve_*()
8703 functions are not consistent with those from Libevent.) Fixes bug
8704 2363; bugfix on 0.2.2.6-alpha. Found by "lodger".
8706 o Documentation, new in 0.2.2.21-alpha:
8707 - Document the default socks host and port (127.0.0.1:9050) for
8711 Changes in version 0.2.1.29 - 2011-01-15
8712 Tor 0.2.1.29 continues our recent code security audit work. The main
8713 fix resolves a remote heap overflow vulnerability that can allow remote
8714 code execution. Other fixes address a variety of assert and crash bugs,
8715 most of which we think are hard to exploit remotely.
8717 o Major bugfixes (security):
8718 - Fix a heap overflow bug where an adversary could cause heap
8719 corruption. This bug probably allows remote code execution
8720 attacks. Reported by "debuger". Fixes CVE-2011-0427. Bugfix on
8722 - Prevent a denial-of-service attack by disallowing any
8723 zlib-compressed data whose compression factor is implausibly
8724 high. Fixes part of bug 2324; reported by "doorss".
8725 - Zero out a few more keys in memory before freeing them. Fixes
8726 bug 2384 and part of bug 2385. These key instances found by
8727 "cypherpunks", based on Andrew Case's report about being able
8728 to find sensitive data in Tor's memory space if you have enough
8729 permissions. Bugfix on 0.0.2pre9.
8731 o Major bugfixes (crashes):
8732 - Prevent calls to Libevent from inside Libevent log handlers.
8733 This had potential to cause a nasty set of crashes, especially
8734 if running Libevent with debug logging enabled, and running
8735 Tor with a controller watching for low-severity log messages.
8736 Bugfix on 0.1.0.2-rc. Fixes bug 2190.
8737 - Add a check for SIZE_T_MAX to tor_realloc() to try to avoid
8738 underflow errors there too. Fixes the other part of bug 2324.
8739 - Fix a bug where we would assert if we ever had a
8740 cached-descriptors.new file (or another file read directly into
8741 memory) of exactly SIZE_T_CEILING bytes. Fixes bug 2326; bugfix
8742 on 0.2.1.25. Found by doorss.
8743 - Fix some potential asserts and parsing issues with grossly
8744 malformed router caches. Fixes bug 2352; bugfix on Tor 0.2.1.27.
8747 o Minor bugfixes (other):
8748 - Fix a bug with handling misformed replies to reverse DNS lookup
8749 requests in DNSPort. Bugfix on Tor 0.2.0.1-alpha. Related to a
8750 bug reported by doorss.
8751 - Fix compilation on mingw when a pthreads compatibility library
8752 has been installed. (We don't want to use it, so we shouldn't
8753 be including pthread.h.) Fixes bug 2313; bugfix on 0.1.0.1-rc.
8754 - Fix a bug where we would declare that we had run out of virtual
8755 addresses when the address space was only half-exhausted. Bugfix
8757 - Correctly handle the case where AutomapHostsOnResolve is set but
8758 no virtual addresses are available. Fixes bug 2328; bugfix on
8759 0.1.2.1-alpha. Bug found by doorss.
8760 - Correctly handle wrapping around to when we run out of virtual
8761 address space. Found by cypherpunks, bugfix on 0.2.0.5-alpha.
8762 - The 0.2.1.28 tarball was missing src/common/OpenBSD_malloc_Linux.c
8763 because we built it with a too-old version of automake. Thus that
8764 release broke ./configure --enable-openbsd-malloc, which is popular
8765 among really fast exit relays on Linux.
8768 - Update to the January 1 2011 Maxmind GeoLite Country database.
8769 - Introduce output size checks on all of our decryption functions.
8772 - Tor does not build packages correctly with Automake 1.6 and earlier;
8773 added a check to Makefile.am to make sure that we're building with
8774 Automake 1.7 or later.
8777 Changes in version 0.2.2.20-alpha - 2010-12-17
8778 Tor 0.2.2.20-alpha does some code cleanup to reduce the risk of remotely
8779 exploitable bugs. We also fix a variety of other significant bugs,
8780 change the IP address for one of our directory authorities, and update
8781 the minimum version that Tor relays must run to join the network.
8784 - Fix a remotely exploitable bug that could be used to crash instances
8785 of Tor remotely by overflowing on the heap. Remote-code execution
8786 hasn't been confirmed, but can't be ruled out. Everyone should
8787 upgrade. Bugfix on the 0.1.1 series and later.
8788 - Fix a bug that could break accounting on 64-bit systems with large
8789 time_t values, making them hibernate for impossibly long intervals.
8790 Fixes bug 2146. Bugfix on 0.0.9pre6; fix by boboper.
8791 - Fix a logic error in directory_fetches_from_authorities() that
8792 would cause all _non_-exits refusing single-hop-like circuits
8793 to fetch from authorities, when we wanted to have _exits_ fetch
8794 from authorities. Fixes more of 2097. Bugfix on 0.2.2.16-alpha;
8796 - Fix a stream fairness bug that would cause newer streams on a given
8797 circuit to get preference when reading bytes from the origin or
8798 destination. Fixes bug 2210. Fix by Mashael AlSabah. This bug was
8799 introduced before the first Tor release, in svn revision r152.
8801 o Directory authority changes:
8802 - Change IP address and ports for gabelmoo (v3 directory authority).
8805 - Avoid crashes when AccountingMax is set on clients. Fixes bug 2235.
8806 Bugfix on 0.2.2.18-alpha. Diagnosed by boboper.
8807 - Fix an off-by-one error in calculating some controller command
8808 argument lengths. Fortunately, this mistake is harmless since
8809 the controller code does redundant NUL termination too. Found by
8810 boboper. Bugfix on 0.1.1.1-alpha.
8811 - Do not dereference NULL if a bridge fails to build its
8812 extra-info descriptor. Found by an anonymous commenter on
8813 Trac. Bugfix on 0.2.2.19-alpha.
8816 - Update to the December 1 2010 Maxmind GeoLite Country database.
8817 - Directory authorities now reject relays running any versions of
8818 Tor between 0.2.1.3-alpha and 0.2.1.18 inclusive; they have
8819 known bugs that keep RELAY_EARLY cells from working on rendezvous
8820 circuits. Followup to fix for bug 2081.
8821 - Directory authorities now reject relays running any version of Tor
8822 older than 0.2.0.26-rc. That version is the earliest that fetches
8823 current directory information correctly. Fixes bug 2156.
8824 - Report only the top 10 ports in exit-port stats in order not to
8825 exceed the maximum extra-info descriptor length of 50 KB. Implements
8829 Changes in version 0.2.1.28 - 2010-12-17
8830 Tor 0.2.1.28 does some code cleanup to reduce the risk of remotely
8831 exploitable bugs. We also took this opportunity to change the IP address
8832 for one of our directory authorities, and to update the geoip database
8836 - Fix a remotely exploitable bug that could be used to crash instances
8837 of Tor remotely by overflowing on the heap. Remote-code execution
8838 hasn't been confirmed, but can't be ruled out. Everyone should
8839 upgrade. Bugfix on the 0.1.1 series and later.
8841 o Directory authority changes:
8842 - Change IP address and ports for gabelmoo (v3 directory authority).
8845 - Update to the December 1 2010 Maxmind GeoLite Country database.
8848 Changes in version 0.2.1.27 - 2010-11-23
8849 Yet another OpenSSL security patch broke its compatibility with Tor:
8850 Tor 0.2.1.27 makes relays work with openssl 0.9.8p and 1.0.0.b. We
8851 also took this opportunity to fix several crash bugs, integrate a new
8852 directory authority, and update the bundled GeoIP database.
8855 - Resolve an incompatibility with OpenSSL 0.9.8p and OpenSSL 1.0.0b:
8856 No longer set the tlsext_host_name extension on server SSL objects;
8857 but continue to set it on client SSL objects. Our goal in setting
8858 it was to imitate a browser, not a vhosting server. Fixes bug 2204;
8859 bugfix on 0.2.1.1-alpha.
8860 - Do not log messages to the controller while shrinking buffer
8861 freelists. Doing so would sometimes make the controller connection
8862 try to allocate a buffer chunk, which would mess up the internals
8863 of the freelist and cause an assertion failure. Fixes bug 1125;
8864 fixed by Robert Ransom. Bugfix on 0.2.0.16-alpha.
8865 - Learn our external IP address when we're a relay or bridge, even if
8866 we set PublishServerDescriptor to 0. Bugfix on 0.2.0.3-alpha,
8867 where we introduced bridge relays that don't need to publish to
8868 be useful. Fixes bug 2050.
8869 - Do even more to reject (and not just ignore) annotations on
8870 router descriptors received anywhere but from the cache. Previously
8871 we would ignore such annotations at first, but cache them to disk
8872 anyway. Bugfix on 0.2.0.8-alpha. Found by piebeer.
8873 - When you're using bridges and your network goes away and your
8874 bridges get marked as down, recover when you attempt a new socks
8875 connection (if the network is back), rather than waiting up to an
8876 hour to try fetching new descriptors for your bridges. Bugfix on
8877 0.2.0.3-alpha; fixes bug 1981.
8880 - Move to the November 2010 Maxmind GeoLite country db (rather
8881 than the June 2009 ip-to-country GeoIP db) for our statistics that
8882 count how many users relays are seeing from each country. Now we'll
8883 have more accurate data, especially for many African countries.
8885 o New directory authorities:
8886 - Set up maatuska (run by Linus Nordberg) as the eighth v3 directory
8890 - Fix an assertion failure that could occur in directory caches or
8891 bridge users when using a very short voting interval on a testing
8892 network. Diagnosed by Robert Hogan. Fixes bug 1141; bugfix on
8894 - Enforce multiplicity rules when parsing annotations. Bugfix on
8895 0.2.0.8-alpha. Found by piebeer.
8896 - Allow handshaking OR connections to take a full KeepalivePeriod
8897 seconds to handshake. Previously, we would close them after
8898 IDLE_OR_CONN_TIMEOUT (180) seconds, the same timeout as if they
8899 were open. Bugfix on 0.2.1.26; fixes bug 1840. Thanks to mingw-san
8901 - When building with --enable-gcc-warnings on OpenBSD, disable
8902 warnings in system headers. This makes --enable-gcc-warnings
8903 pass on OpenBSD 4.8.
8906 - Exit nodes didn't recognize EHOSTUNREACH as a plausible error code,
8907 and so sent back END_STREAM_REASON_MISC. Clients now recognize a new
8908 stream ending reason for this case: END_STREAM_REASON_NOROUTE.
8909 Servers can start sending this code when enough clients recognize
8910 it. Bugfix on 0.1.0.1-rc; fixes part of bug 1793.
8911 - Build correctly on mingw with more recent versions of OpenSSL 0.9.8.
8912 Patch from mingw-san.
8915 - Remove the old debian/ directory from the main Tor distribution.
8916 The official Tor-for-debian git repository lives at the URL
8917 https://git.torproject.org/debian/tor.git
8918 - Stop shipping the old doc/website/ directory in the tarball. We
8919 changed the website format in late 2010, and what we shipped in
8920 0.2.1.26 really wasn't that useful anyway.
8923 Changes in version 0.2.2.19-alpha - 2010-11-22
8924 Yet another OpenSSL security patch broke its compatibility with Tor:
8925 Tor 0.2.2.19-alpha makes relays work with OpenSSL 0.9.8p and 1.0.0.b.
8928 - Resolve an incompatibility with OpenSSL 0.9.8p and OpenSSL 1.0.0b:
8929 No longer set the tlsext_host_name extension on server SSL objects;
8930 but continue to set it on client SSL objects. Our goal in setting
8931 it was to imitate a browser, not a vhosting server. Fixes bug 2204;
8932 bugfix on 0.2.1.1-alpha.
8935 - Try harder not to exceed the maximum length of 50 KB when writing
8936 statistics to extra-info descriptors. This bug was triggered by very
8937 fast relays reporting exit-port, entry, and dirreq statistics.
8938 Reported by Olaf Selke. Bugfix on 0.2.2.1-alpha. Fixes bug 2183.
8939 - Publish a router descriptor even if generating an extra-info
8940 descriptor fails. Previously we would not publish a router
8941 descriptor without an extra-info descriptor; this can cause fast
8942 exit relays collecting exit-port statistics to drop from the
8943 consensus. Bugfix on 0.1.2.9-rc; fixes bug 2195.
8946 Changes in version 0.2.2.18-alpha - 2010-11-16
8947 Tor 0.2.2.18-alpha fixes several crash bugs that have been nagging
8948 us lately, makes unpublished bridge relays able to detect their IP
8949 address, and fixes a wide variety of other bugs to get us much closer
8950 to a stable release.
8953 - Do even more to reject (and not just ignore) annotations on
8954 router descriptors received anywhere but from the cache. Previously
8955 we would ignore such annotations at first, but cache them to disk
8956 anyway. Bugfix on 0.2.0.8-alpha. Found by piebeer.
8957 - Do not log messages to the controller while shrinking buffer
8958 freelists. Doing so would sometimes make the controller connection
8959 try to allocate a buffer chunk, which would mess up the internals
8960 of the freelist and cause an assertion failure. Fixes bug 1125;
8961 fixed by Robert Ransom. Bugfix on 0.2.0.16-alpha.
8962 - Learn our external IP address when we're a relay or bridge, even if
8963 we set PublishServerDescriptor to 0. Bugfix on 0.2.0.3-alpha,
8964 where we introduced bridge relays that don't need to publish to
8965 be useful. Fixes bug 2050.
8966 - Maintain separate TLS contexts and certificates for incoming and
8967 outgoing connections in bridge relays. Previously we would use the
8968 same TLS contexts and certs for incoming and outgoing connections.
8969 Bugfix on 0.2.0.3-alpha; addresses bug 988.
8970 - Maintain separate identity keys for incoming and outgoing TLS
8971 contexts in bridge relays. Previously we would use the same
8972 identity keys for incoming and outgoing TLS contexts. Bugfix on
8973 0.2.0.3-alpha; addresses the other half of bug 988.
8974 - Avoid an assertion failure when we as an authority receive a
8975 duplicate upload of a router descriptor that we already have,
8976 but which we previously considered an obsolete descriptor.
8977 Fixes another case of bug 1776. Bugfix on 0.2.2.16-alpha.
8978 - Avoid a crash bug triggered by looking at a dangling pointer while
8979 setting the network status consensus. Found by Robert Ransom.
8980 Bugfix on 0.2.2.17-alpha. Fixes bug 2097.
8981 - Fix a logic error where servers that _didn't_ act as exits would
8982 try to keep their server lists more aggressively up to date than
8983 exits, when it was supposed to be the other way around. Bugfix
8986 o Minor bugfixes (on Tor 0.2.1.x and earlier):
8987 - When we're trying to guess whether we know our IP address as
8988 a relay, we would log various ways that we failed to guess
8989 our address, but never log that we ended up guessing it
8990 successfully. Now add a log line to help confused and anxious
8991 relay operators. Bugfix on 0.1.2.1-alpha; fixes bug 1534.
8992 - Bring the logic that gathers routerinfos and assesses the
8993 acceptability of circuits into line. This prevents a Tor OP from
8994 getting locked in a cycle of choosing its local OR as an exit for a
8995 path (due to a .exit request) and then rejecting the circuit because
8996 its OR is not listed yet. It also prevents Tor clients from using an
8997 OR running in the same instance as an exit (due to a .exit request)
8998 if the OR does not meet the same requirements expected of an OR
8999 running elsewhere. Fixes bug 1859; bugfix on 0.1.0.1-rc.
9000 - Correctly describe errors that occur when generating a TLS object.
9001 Previously we would attribute them to a failure while generating a
9002 TLS context. Patch by Robert Ransom. Bugfix on 0.1.0.4-rc; fixes
9004 - Enforce multiplicity rules when parsing annotations. Bugfix on
9005 0.2.0.8-alpha. Found by piebeer.
9006 - Fix warnings that newer versions of autoconf produced during
9007 ./autogen.sh. These warnings appear to be harmless in our case,
9008 but they were extremely verbose. Fixes bug 2020.
9010 o Minor bugfixes (on Tor 0.2.2.x):
9011 - Enable protection of small arrays whenever we build with gcc
9012 hardening features, not only when also building with warnings
9013 enabled. Fixes bug 2031; bugfix on 0.2.2.14-alpha. Reported by keb.
9016 - Make hidden services work better in private Tor networks by not
9017 requiring any uptime to join the hidden service descriptor
9018 DHT. Implements ticket 2088.
9019 - Rate-limit the "your application is giving Tor only an IP address"
9020 warning. Addresses bug 2000; bugfix on 0.0.8pre2.
9021 - When AllowSingleHopExits is set, print a warning to explain to the
9022 relay operator why most clients are avoiding her relay.
9023 - Update to the November 1 2010 Maxmind GeoLite Country database.
9025 o Code simplifications and refactoring:
9026 - When we fixed bug 1038 we had to put in a restriction not to send
9027 RELAY_EARLY cells on rend circuits. This was necessary as long
9028 as relays using Tor 0.2.1.3-alpha through 0.2.1.18-alpha were
9029 active. Now remove this obsolete check. Resolves bug 2081.
9030 - Some options used different conventions for uppercasing of acronyms
9031 when comparing manpage and source. Fix those in favor of the
9032 manpage, as it makes sense to capitalize acronyms.
9033 - Remove the torrc.complete file. It hasn't been kept up to date
9034 and users will have better luck checking out the manpage.
9035 - Remove the obsolete "NoPublish" option; it has been flagged
9036 as obsolete and has produced a warning since 0.1.1.18-rc.
9037 - Remove everything related to building the expert bundle for OS X.
9038 It has confused many users, doesn't work right on OS X 10.6,
9039 and is hard to get rid of once installed. Resolves bug 1274.
9042 Changes in version 0.2.2.17-alpha - 2010-09-30
9043 Tor 0.2.2.17-alpha introduces a feature to make it harder for clients
9044 to use one-hop circuits (which can put the exit relays at higher risk,
9045 plus unbalance the network); fixes a big bug in bandwidth accounting
9046 for relays that want to limit their monthly bandwidth use; fixes a
9047 big pile of bugs in how clients tolerate temporary network failure;
9048 and makes our adaptive circuit build timeout feature (which improves
9049 client performance if your network is fast while not breaking things
9050 if your network is slow) better handle bad networks.
9053 - Exit relays now try harder to block exit attempts from unknown
9054 relays, to make it harder for people to use them as one-hop proxies
9055 a la tortunnel. Controlled by the refuseunknownexits consensus
9056 parameter (currently enabled), or you can override it on your
9057 relay with the RefuseUnknownExits torrc option. Resolves bug 1751.
9059 o Major bugfixes (0.2.1.x and earlier):
9060 - Fix a bug in bandwidth accounting that could make us use twice
9061 the intended bandwidth when our interval start changes due to
9062 daylight saving time. Now we tolerate skew in stored vs computed
9063 interval starts: if the start of the period changes by no more than
9064 50% of the period's duration, we remember bytes that we transferred
9065 in the old period. Fixes bug 1511; bugfix on 0.0.9pre5.
9066 - Always search the Windows system directory for system DLLs, and
9067 nowhere else. Bugfix on 0.1.1.23; fixes bug 1954.
9068 - When you're using bridges and your network goes away and your
9069 bridges get marked as down, recover when you attempt a new socks
9070 connection (if the network is back), rather than waiting up to an
9071 hour to try fetching new descriptors for your bridges. Bugfix on
9072 0.2.0.3-alpha; fixes bug 1981.
9074 o Major bugfixes (on 0.2.2.x):
9075 - Fix compilation on Windows. Bugfix on 0.2.2.16-alpha; related to
9077 - Fix a segfault that could happen when operating a bridge relay with
9078 no GeoIP database set. Fixes bug 1964; bugfix on 0.2.2.15-alpha.
9079 - The consensus bandwidth-weights (used by clients to choose fast
9080 relays) entered an unexpected edge case in September where
9081 Exits were much scarcer than Guards, resulting in bad weight
9082 recommendations. Now we compute them using new constraints that
9083 should succeed in all cases. Also alter directory authorities to
9084 not include the bandwidth-weights line if they fail to produce
9085 valid values. Fixes bug 1952; bugfix on 0.2.2.10-alpha.
9086 - When weighting bridges during path selection, we used to trust
9087 the bandwidths they provided in their descriptor, only capping them
9088 at 10MB/s. This turned out to be problematic for two reasons:
9089 Bridges could claim to handle a lot more traffic then they
9090 actually would, thus making more clients pick them and have a
9091 pretty effective DoS attack. The other issue is that new bridges
9092 that might not have a good estimate for their bw capacity yet
9093 would not get used at all unless no other bridges are available
9094 to a client. Fixes bug 1912; bugfix on 0.2.2.7-alpha.
9096 o Major bugfixes (on the circuit build timeout feature, 0.2.2.x):
9097 - Ignore cannibalized circuits when recording circuit build times.
9098 This should provide for a minor performance improvement for hidden
9099 service users using 0.2.2.14-alpha, and should remove two spurious
9100 notice log messages. Bugfix on 0.2.2.14-alpha; fixes bug 1740.
9101 - Simplify the logic that causes us to decide if the network is
9102 unavailable for purposes of recording circuit build times. If we
9103 receive no cells whatsoever for the entire duration of a circuit's
9104 full measured lifetime, the network is probably down. Also ignore
9105 one-hop directory fetching circuit timeouts when calculating our
9106 circuit build times. These changes should hopefully reduce the
9107 cases where we see ridiculous circuit build timeouts for people
9108 with spotty wireless connections. Fixes part of bug 1772; bugfix
9110 - Prevent the circuit build timeout from becoming larger than
9111 the maximum build time we have ever seen. Also, prevent the time
9112 period for measurement circuits from becoming larger than twice that
9113 value. Fixes the other part of bug 1772; bugfix on 0.2.2.2-alpha.
9116 - When we run out of directory information such that we can't build
9117 circuits, but then get enough that we can build circuits, log when
9118 we actually construct a circuit, so the user has a better chance of
9119 knowing what's going on. Fixes bug 1362.
9120 - Be more generous with how much bandwidth we'd use up (with
9121 accounting enabled) before entering "soft hibernation". Previously,
9122 we'd refuse new connections and circuits once we'd used up 95% of
9123 our allotment. Now, we use up 95% of our allotment, AND make sure
9124 that we have no more than 500MB (or 3 hours of expected traffic,
9125 whichever is lower) remaining before we enter soft hibernation.
9126 - If we've configured EntryNodes and our network goes away and/or all
9127 our entrynodes get marked down, optimistically retry them all when
9128 a new socks application request appears. Fixes bug 1882.
9129 - Add some more defensive programming for architectures that can't
9130 handle unaligned integer accesses. We don't know of any actual bugs
9131 right now, but that's the best time to fix them. Fixes bug 1943.
9132 - Support line continuations in the torrc config file. If a line
9133 ends with a single backslash character, the newline is ignored, and
9134 the configuration value is treated as continuing on the next line.
9137 o Minor bugfixes (on 0.2.1.x and earlier):
9138 - For bandwidth accounting, calculate our expected bandwidth rate
9139 based on the time during which we were active and not in
9140 soft-hibernation during the last interval. Previously, we were
9141 also considering the time spent in soft-hibernation. If this
9142 was a long time, we would wind up underestimating our bandwidth
9143 by a lot, and skewing our wakeup time towards the start of the
9144 accounting interval. Fixes bug 1789. Bugfix on 0.0.9pre5.
9146 o Minor bugfixes (on 0.2.2.x):
9147 - Resume generating CIRC FAILED REASON=TIMEOUT control port messages,
9148 which were disabled by the circuit build timeout changes in
9149 0.2.2.14-alpha. Bugfix on 0.2.2.14-alpha; fixes bug 1739.
9150 - Make sure we don't warn about missing bandwidth weights when
9151 choosing bridges or other relays not in the consensus. Bugfix on
9152 0.2.2.10-alpha; fixes bug 1805.
9153 - In our logs, do not double-report signatures from unrecognized
9154 authorities both as "from unknown authority" and "not
9155 present". Fixes bug 1956, bugfix on 0.2.2.16-alpha.
9158 Changes in version 0.2.2.16-alpha - 2010-09-17
9159 Tor 0.2.2.16-alpha fixes a variety of old stream fairness bugs (most
9160 evident at exit relays), and also continues to resolve all the little
9161 bugs that have been filling up trac lately.
9163 o Major bugfixes (stream-level fairness):
9164 - When receiving a circuit-level SENDME for a blocked circuit, try
9165 to package cells fairly from all the streams that had previously
9166 been blocked on that circuit. Previously, we had started with the
9167 oldest stream, and allowed each stream to potentially exhaust
9168 the circuit's package window. This gave older streams on any
9169 given circuit priority over newer ones. Fixes bug 1937. Detected
9170 originally by Camilo Viecco. This bug was introduced before the
9171 first Tor release, in svn commit r152: it is the new winner of
9172 the longest-lived bug prize.
9173 - When the exit relay got a circuit-level sendme cell, it started
9174 reading on the exit streams, even if had 500 cells queued in the
9175 circuit queue already, so the circuit queue just grew and grew in
9176 some cases. We fix this by not re-enabling reading on receipt of a
9177 sendme cell when the cell queue is blocked. Fixes bug 1653. Bugfix
9178 on 0.2.0.1-alpha. Detected by Mashael AlSabah. Original patch by
9180 - Newly created streams were allowed to read cells onto circuits,
9181 even if the circuit's cell queue was blocked and waiting to drain.
9182 This created potential unfairness, as older streams would be
9183 blocked, but newer streams would gladly fill the queue completely.
9184 We add code to detect this situation and prevent any stream from
9185 getting more than one free cell. Bugfix on 0.2.0.1-alpha. Partially
9189 - Update to the September 1 2010 Maxmind GeoLite Country database.
9190 - Warn when CookieAuthFileGroupReadable is set but CookieAuthFile is
9191 not. This would lead to a cookie that is still not group readable.
9192 Closes bug 1843. Suggested by katmagic.
9193 - When logging a rate-limited warning, we now mention how many messages
9194 got suppressed since the last warning.
9195 - Add new "perconnbwrate" and "perconnbwburst" consensus params to
9196 do individual connection-level rate limiting of clients. The torrc
9197 config options with the same names trump the consensus params, if
9198 both are present. Replaces the old "bwconnrate" and "bwconnburst"
9199 consensus params which were broken from 0.2.2.7-alpha through
9200 0.2.2.14-alpha. Closes bug 1947.
9201 - When a router changes IP address or port, authorities now launch
9202 a new reachability test for it. Implements ticket 1899.
9203 - Make the formerly ugly "2 unknown, 7 missing key, 0 good, 0 bad,
9204 2 no signature, 4 required" messages about consensus signatures
9205 easier to read, and make sure they get logged at the same severity
9206 as the messages explaining which keys are which. Fixes bug 1290.
9207 - Don't warn when we have a consensus that we can't verify because
9208 of missing certificates, unless those certificates are ones
9209 that we have been trying and failing to download. Fixes bug 1145.
9210 - If you configure your bridge with a known identity fingerprint,
9211 and the bridge authority is unreachable (as it is in at least
9212 one country now), fall back to directly requesting the descriptor
9213 from the bridge. Finishes the feature started in 0.2.0.10-alpha;
9215 - When building with --enable-gcc-warnings on OpenBSD, disable
9216 warnings in system headers. This makes --enable-gcc-warnings
9217 pass on OpenBSD 4.8.
9219 o Minor bugfixes (on 0.2.1.x and earlier):
9220 - Authorities will now attempt to download consensuses if their
9221 own efforts to make a live consensus have failed. This change
9222 means authorities that restart will fetch a valid consensus, and
9223 it means authorities that didn't agree with the current consensus
9224 will still fetch and serve it if it has enough signatures. Bugfix
9225 on 0.2.0.9-alpha; fixes bug 1300.
9226 - Ensure DNS requests launched by "RESOLVE" commands from the
9227 controller respect the __LeaveStreamsUnattached setconf options. The
9228 same goes for requests launched via DNSPort or transparent
9229 proxying. Bugfix on 0.2.0.1-alpha; fixes bug 1525.
9230 - Allow handshaking OR connections to take a full KeepalivePeriod
9231 seconds to handshake. Previously, we would close them after
9232 IDLE_OR_CONN_TIMEOUT (180) seconds, the same timeout as if they
9233 were open. Bugfix on 0.2.1.26; fixes bug 1840. Thanks to mingw-san
9235 - Rate-limit "Failed to hand off onionskin" warnings.
9236 - Never relay a cell for a circuit we have already destroyed.
9237 Between marking a circuit as closeable and finally closing it,
9238 it may have been possible for a few queued cells to get relayed,
9239 even though they would have been immediately dropped by the next
9240 OR in the circuit. Fixes bug 1184; bugfix on 0.2.0.1-alpha.
9241 - Never queue a cell for a circuit that's already been marked
9243 - Never vote for a server as "Running" if we have a descriptor for
9244 it claiming to be hibernating, and that descriptor was published
9245 more recently than our last contact with the server. Bugfix on
9246 0.2.0.3-alpha; fixes bug 911.
9247 - Squash a compile warning on OpenBSD. Reported by Tas; fixes
9250 o Minor bugfixes (on 0.2.2.x):
9251 - Fix a regression introduced in 0.2.2.7-alpha that marked relays
9252 down if a directory fetch fails and you've configured either
9253 bridges or EntryNodes. The intent was to mark the relay as down
9254 _unless_ you're using bridges or EntryNodes, since if you are
9255 then you could quickly run out of entry points.
9256 - Fix the Windows directory-listing code. A bug introduced in
9257 0.2.2.14-alpha could make Windows directory servers forget to load
9258 some of their cached v2 networkstatus files.
9259 - Really allow clients to use relays as bridges. Fixes bug 1776;
9260 bugfix on 0.2.2.15-alpha.
9261 - Demote a warn to info that happens when the CellStatistics option
9262 was just enabled. Bugfix on 0.2.2.15-alpha; fixes bug 1921.
9263 Reported by Moritz Bartl.
9264 - On Windows, build correctly either with or without Unicode support.
9265 This is necessary so that Tor can support fringe platforms like
9266 Windows 98 (which has no Unicode), or Windows CE (which has no
9267 non-Unicode). Bugfix on 0.2.2.14-alpha; fixes bug 1797.
9270 - Add a unit test for cross-platform directory-listing code.
9273 Changes in version 0.2.2.15-alpha - 2010-08-18
9274 Tor 0.2.2.15-alpha fixes a big bug in hidden service availability,
9275 fixes a variety of other bugs that were preventing performance
9276 experiments from moving forward, fixes several bothersome memory leaks,
9277 and generally closes a lot of smaller bugs that have been filling up
9281 - Stop assigning the HSDir flag to relays that disable their
9282 DirPort (and thus will refuse to answer directory requests). This
9283 fix should dramatically improve the reachability of hidden services:
9284 hidden services and hidden service clients pick six HSDir relays
9285 to store and retrieve the hidden service descriptor, and currently
9286 about half of the HSDir relays will refuse to work. Bugfix on
9287 0.2.0.10-alpha; fixes part of bug 1693.
9288 - The PerConnBWRate and Burst config options, along with the
9289 bwconnrate and bwconnburst consensus params, initialized each conn's
9290 token bucket values only when the connection is established. Now we
9291 update them if the config options change, and update them every time
9292 we get a new consensus. Otherwise we can encounter an ugly edge
9293 case where we initialize an OR conn to client-level bandwidth,
9294 but then later the relay joins the consensus and we leave it
9295 throttled. Bugfix on 0.2.2.7-alpha; fixes bug 1830.
9296 - Fix a regression that caused Tor to rebind its ports if it receives
9297 SIGHUP while hibernating. Bugfix in 0.1.1.6-alpha; closes bug 919.
9300 - Lower the maximum weighted-fractional-uptime cutoff to 98%. This
9301 should give us approximately 40-50% more Guard-flagged nodes,
9302 improving the anonymity the Tor network can provide and also
9303 decreasing the dropoff in throughput that relays experience when
9304 they first get the Guard flag.
9305 - Allow enabling or disabling the *Statistics config options while
9309 - Update to the August 1 2010 Maxmind GeoLite Country database.
9310 - Have the controller interface give a more useful message than
9311 "Internal Error" in response to failed GETINFO requests.
9312 - Warn when the same option is provided more than once in a torrc
9313 file, on the command line, or in a single SETCONF statement, and
9314 the option is one that only accepts a single line. Closes bug 1384.
9315 - Build correctly on mingw with more recent versions of OpenSSL 0.9.8.
9316 Patch from mingw-san.
9317 - Add support for the country code "{??}" in torrc options like
9318 ExcludeNodes, to indicate all routers of unknown country. Closes
9320 - Relays report the number of bytes spent on answering directory
9321 requests in extra-info descriptors similar to {read,write}-history.
9322 Implements enhancement 1790.
9324 o Minor bugfixes (on 0.2.1.x and earlier):
9325 - Complain if PublishServerDescriptor is given multiple arguments that
9326 include 0 or 1. This configuration will be rejected in the future.
9327 Bugfix on 0.2.0.1-alpha; closes bug 1107.
9328 - Disallow BridgeRelay 1 and ORPort 0 at once in the configuration.
9329 Bugfix on 0.2.0.13-alpha; closes bug 928.
9330 - Change "Application request when we're believed to be offline."
9331 notice to "Application request when we haven't used client
9332 functionality lately.", to clarify that it's not an error. Bugfix
9333 on 0.0.9.3; fixes bug 1222.
9334 - Fix a bug in the controller interface where "GETINFO ns/asdaskljkl"
9335 would return "551 Internal error" rather than "552 Unrecognized key
9336 ns/asdaskljkl". Bugfix on 0.1.2.3-alpha.
9337 - Users can't configure a regular relay to be their bridge. It didn't
9338 work because when Tor fetched the bridge descriptor, it found
9339 that it already had it, and didn't realize that the purpose of the
9340 descriptor had changed. Now we replace routers with a purpose other
9341 than bridge with bridge descriptors when fetching them. Bugfix on
9342 0.1.1.9-alpha. Bug 1776 not yet fixed because now we immediately
9343 refetch the descriptor with router purpose 'general', disabling
9345 - Fix a rare bug in rend_fn unit tests: we would fail a test when
9346 a randomly generated port is 0. Diagnosed by Matt Edman. Bugfix
9347 on 0.2.0.10-alpha; fixes bug 1808.
9348 - Exit nodes didn't recognize EHOSTUNREACH as a plausible error code,
9349 and so sent back END_STREAM_REASON_MISC. Clients now recognize a new
9350 stream ending reason for this case: END_STREAM_REASON_NOROUTE.
9351 Servers can start sending this code when enough clients recognize
9352 it. Also update the spec to reflect this new reason. Bugfix on
9353 0.1.0.1-rc; fixes part of bug 1793.
9354 - Delay geoip stats collection by bridges for 6 hours, not 2 hours,
9355 when we switch from being a public relay to a bridge. Otherwise
9356 there will still be clients that see the relay in their consensus,
9357 and the stats will end up wrong. Bugfix on 0.2.1.15-rc; fixes bug
9359 - Instead of giving an assertion failure on an internal mismatch
9360 on estimated freelist size, just log a BUG warning and try later.
9361 Mitigates but does not fix bug 1125.
9362 - Fix an assertion failure that could occur in caches or bridge users
9363 when using a very short voting interval on a testing network.
9364 Diagnosed by Robert Hogan. Fixes bug 1141; bugfix on 0.2.0.8-alpha.
9366 o Minor bugfixes (on 0.2.2.x):
9367 - Alter directory authorities to always consider Exit-flagged nodes
9368 as potential Guard nodes in their votes. The actual decision to
9369 use Exits as Guards is done in the consensus bandwidth weights.
9370 Fixes bug 1294; bugfix on 0.2.2.10-alpha.
9371 - When the controller is reporting the purpose of circuits that
9372 didn't finish building before the circuit build timeout, it was
9373 printing UNKNOWN_13. Now print EXPIRED. Bugfix on 0.2.2.14-alpha.
9374 - Our libevent version parsing code couldn't handle versions like
9375 1.4.14b-stable and incorrectly warned the user about using an
9376 old and broken version of libevent. Treat 1.4.14b-stable like
9377 1.4.14-stable when parsing the version. Fixes bug 1731; bugfix
9379 - Don't use substitution references like $(VAR:MOD) when
9380 $(asciidoc_files) is empty -- make(1) on NetBSD transforms
9381 '$(:x)' to 'x' rather than the empty string. This bites us in
9382 doc/ when configured with --disable-asciidoc. Bugfix on
9383 0.2.2.9-alpha; fixes bug 1773.
9384 - Remove a spurious hidden service server-side log notice about
9385 "Ancient non-dirty circuits". Bugfix on 0.2.2.14-alpha; fixes
9387 - Fix compilation with --with-dmalloc set. Bugfix on 0.2.2.6-alpha;
9389 - Correctly report written bytes on linked connections. Found while
9390 implementing 1790. Bugfix on 0.2.2.4-alpha.
9391 - Fix three memory leaks: one in circuit_build_times_parse_state(),
9392 one in dirvote_add_signatures_to_pending_consensus(), and one every
9393 time we parse a v3 network consensus. Bugfixes on 0.2.2.14-alpha,
9394 0.2.2.6-alpha, and 0.2.2.10-alpha respectively; fixes bug 1831.
9396 o Code simplifications and refactoring:
9397 - Take a first step towards making or.h smaller by splitting out
9398 function definitions for all source files in src/or/. Leave
9399 structures and defines in or.h for now.
9400 - Remove a bunch of unused function declarations as well as a block of
9401 #if 0'd code from the unit tests. Closes bug 1824.
9402 - New unit tests for exit-port history statistics; refactored exit
9403 statistics code to be more easily tested.
9404 - Remove the old debian/ directory from the main Tor distribution.
9405 The official Tor-for-debian git repository lives at the URL
9406 https://git.torproject.org/debian/tor.git
9409 Changes in version 0.2.2.14-alpha - 2010-07-12
9410 Tor 0.2.2.14-alpha greatly improves client-side handling of
9411 circuit build timeouts, which are used to estimate speed and improve
9412 performance. We also move to a much better GeoIP database, port Tor to
9413 Windows CE, introduce new compile flags that improve code security,
9414 add an eighth v3 directory authority, and address a lot of more
9418 - Tor directory authorities no longer crash when started with a
9419 cached-microdesc-consensus file in their data directory. Bugfix
9420 on 0.2.2.6-alpha; fixes bug 1532.
9421 - Treat an unset $HOME like an empty $HOME rather than triggering an
9422 assert. Bugfix on 0.0.8pre1; fixes bug 1522.
9423 - Ignore negative and large circuit build timeout values that can
9424 happen during a suspend or hibernate. These values caused various
9425 asserts to fire. Bugfix on 0.2.2.2-alpha; fixes bug 1245.
9426 - Alter calculation of Pareto distribution parameter 'Xm' for
9427 Circuit Build Timeout learning to use the weighted average of the
9428 top N=3 modes (because we have three entry guards). Considering
9429 multiple modes should improve the timeout calculation in some cases,
9430 and prevent extremely high timeout values. Bugfix on 0.2.2.2-alpha;
9432 - Alter calculation of Pareto distribution parameter 'Alpha' to use a
9433 right censored distribution model. This approach improves over the
9434 synthetic timeout generation approach that was producing insanely
9435 high timeout values. Now we calculate build timeouts using truncated
9436 times. Bugfix on 0.2.2.2-alpha; fixes bugs 1245 and 1335.
9437 - Do not close circuits that are under construction when they reach
9438 the circuit build timeout. Instead, leave them building (but do not
9439 use them) for up until the time corresponding to the 95th percentile
9440 on the Pareto CDF or 60 seconds, whichever is greater. This is done
9441 to provide better data for the new Pareto model. This percentile
9442 can be controlled by the consensus.
9445 - Move to the June 2010 Maxmind GeoLite country db (rather than the
9446 June 2009 ip-to-country GeoIP db) for our statistics that count
9447 how many users relays are seeing from each country. Now we have
9448 more accurate data for many African countries.
9449 - Port Tor to build and run correctly on Windows CE systems, using
9450 the wcecompat library. Contributed by Valerio Lupi.
9451 - New "--enable-gcc-hardening" ./configure flag (off by default)
9452 to turn on gcc compile time hardening options. It ensures
9453 that signed ints have defined behavior (-fwrapv), enables
9454 -D_FORTIFY_SOURCE=2 (requiring -O2), adds stack smashing protection
9455 with canaries (-fstack-protector-all), turns on ASLR protection if
9456 supported by the kernel (-fPIE, -pie), and adds additional security
9457 related warnings. Verified to work on Mac OS X and Debian Lenny.
9458 - New "--enable-linker-hardening" ./configure flag (off by default)
9459 to turn on ELF specific hardening features (relro, now). This does
9460 not work with Mac OS X or any other non-ELF binary format.
9462 o New directory authorities:
9463 - Set up maatuska (run by Linus Nordberg) as the eighth v3 directory
9467 - New config option "WarnUnsafeSocks 0" disables the warning that
9468 occurs whenever Tor receives a socks handshake using a version of
9469 the socks protocol that can only provide an IP address (rather
9470 than a hostname). Setups that do DNS locally over Tor are fine,
9471 and we shouldn't spam the logs in that case.
9472 - Convert the HACKING file to asciidoc, and add a few new sections
9473 to it, explaining how we use Git, how we make changelogs, and
9474 what should go in a patch.
9475 - Add a TIMEOUT_RATE keyword to the BUILDTIMEOUT_SET control port
9476 event, to give information on the current rate of circuit timeouts
9477 over our stored history.
9478 - Add ability to disable circuit build time learning via consensus
9479 parameter and via a LearnCircuitBuildTimeout config option. Also
9480 automatically disable circuit build time calculation if we are
9481 either a AuthoritativeDirectory, or if we fail to write our state
9482 file. Fixes bug 1296.
9483 - More gracefully handle corrupt state files, removing asserts
9484 in favor of saving a backup and resetting state.
9485 - Rename the "log.h" header to "torlog.h" so as to conflict with fewer
9489 - Build correctly on OSX with zlib 1.2.4 and higher with all warnings
9491 - When a2x fails, mention that the user could disable manpages instead
9492 of trying to fix their asciidoc installation.
9493 - Where available, use Libevent 2.0's periodic timers so that our
9494 once-per-second cleanup code gets called even more closely to
9495 once per second than it would otherwise. Fixes bug 943.
9496 - If you run a bridge that listens on multiple IP addresses, and
9497 some user configures a bridge address that uses a different IP
9498 address than your bridge writes in its router descriptor, and the
9499 user doesn't specify an identity key, their Tor would discard the
9500 descriptor because "it isn't one of our configured bridges", and
9501 fail to bootstrap. Now believe the descriptor and bootstrap anyway.
9502 Bugfix on 0.2.0.3-alpha.
9503 - If OpenSSL fails to make a duplicate of a private or public key, log
9504 an error message and try to exit cleanly. May help with debugging
9505 if bug 1209 ever remanifests.
9506 - Save a couple bytes in memory allocation every time we escape
9507 certain characters in a string. Patch from Florian Zumbiehl.
9508 - Make it explicit that we don't cannibalize one-hop circuits. This
9509 happens in the wild, but doesn't turn out to be a problem because
9510 we fortunately don't use those circuits. Many thanks to outofwords
9511 for the initial analysis and to swissknife who confirmed that
9512 two-hop circuits are actually created.
9513 - Make directory mirrors report non-zero dirreq-v[23]-shares again.
9514 Fixes bug 1564; bugfix on 0.2.2.9-alpha.
9515 - Eliminate a case where a circuit build time warning was displayed
9516 after network connectivity resumed. Bugfix on 0.2.2.2-alpha.
9519 Changes in version 0.2.1.26 - 2010-05-02
9520 Tor 0.2.1.26 addresses the recent connection and memory overload
9521 problems we've been seeing on relays, especially relays with their
9522 DirPort open. If your relay has been crashing, or you turned it off
9523 because it used too many resources, give this release a try.
9525 This release also fixes yet another instance of broken OpenSSL libraries
9526 that was causing some relays to drop out of the consensus.
9529 - Teach relays to defend themselves from connection overload. Relays
9530 now close idle circuits early if it looks like they were intended
9531 for directory fetches. Relays are also more aggressive about closing
9532 TLS connections that have no circuits on them. Such circuits are
9533 unlikely to be re-used, and tens of thousands of them were piling
9534 up at the fast relays, causing the relays to run out of sockets
9535 and memory. Bugfix on 0.2.0.22-rc (where clients started tunneling
9536 their directory fetches over TLS).
9537 - Fix SSL renegotiation behavior on OpenSSL versions like on Centos
9538 that claim to be earlier than 0.9.8m, but which have in reality
9539 backported huge swaths of 0.9.8m or 0.9.8n renegotiation
9540 behavior. Possible fix for some cases of bug 1346.
9541 - Directory mirrors were fetching relay descriptors only from v2
9542 directory authorities, rather than v3 authorities like they should.
9543 Only 2 v2 authorities remain (compared to 7 v3 authorities), leading
9544 to a serious bottleneck. Bugfix on 0.2.0.9-alpha. Fixes bug 1324.
9547 - Finally get rid of the deprecated and now harmful notion of "clique
9548 mode", where directory authorities maintain TLS connections to
9552 - In the util/threads test, no longer free the test_mutex before all
9553 worker threads have finished. Bugfix on 0.2.1.6-alpha.
9554 - The master thread could starve the worker threads quite badly on
9555 certain systems, causing them to run only partially in the allowed
9556 window. This resulted in test failures. Now the master thread sleeps
9557 occasionally for a few microseconds while the two worker-threads
9558 compete for the mutex. Bugfix on 0.2.0.1-alpha.
9561 Changes in version 0.2.2.13-alpha - 2010-04-24
9562 Tor 0.2.2.13-alpha addresses the recent connection and memory overload
9563 problems we've been seeing on relays, especially relays with their
9564 DirPort open. If your relay has been crashing, or you turned it off
9565 because it used too many resources, give this release a try.
9568 - Teach relays to defend themselves from connection overload. Relays
9569 now close idle circuits early if it looks like they were intended
9570 for directory fetches. Relays are also more aggressive about closing
9571 TLS connections that have no circuits on them. Such circuits are
9572 unlikely to be re-used, and tens of thousands of them were piling
9573 up at the fast relays, causing the relays to run out of sockets
9574 and memory. Bugfix on 0.2.0.22-rc (where clients started tunneling
9575 their directory fetches over TLS).
9578 - Finally get rid of the deprecated and now harmful notion of "clique
9579 mode", where directory authorities maintain TLS connections to
9581 - Directory authorities now do an immediate reachability check as soon
9582 as they hear about a new relay. This change should slightly reduce
9583 the time between setting up a relay and getting listed as running
9584 in the consensus. It should also improve the time between setting
9585 up a bridge and seeing use by bridge users.
9586 - Directory authorities no longer launch a TLS connection to every
9587 relay as they startup. Now that we have 2k+ descriptors cached,
9588 the resulting network hiccup is becoming a burden. Besides,
9589 authorities already avoid voting about Running for the first half
9590 hour of their uptime.
9593 Changes in version 0.2.2.12-alpha - 2010-04-20
9594 Tor 0.2.2.12-alpha fixes a critical bug in how directory authorities
9595 handle and vote on descriptors. It was causing relays to drop out of
9599 - Many relays have been falling out of the consensus lately because
9600 not enough authorities know about their descriptor for them to get
9601 a majority of votes. When we deprecated the v2 directory protocol,
9602 we got rid of the only way that v3 authorities can hear from each
9603 other about other descriptors. Now authorities examine every v3
9604 vote for new descriptors, and fetch them from that authority. Bugfix
9606 - Fix two typos in tor_vasprintf() that broke the compile on Windows,
9607 and a warning in or.h related to bandwidth_weight_rule_t that
9608 prevented clean compile on OS X. Fixes bug 1363; bugfix on
9610 - Fix a segfault on relays when DirReqStatistics is enabled
9611 and 24 hours pass. Bug found by keb. Fixes bug 1365; bugfix on
9615 - Demote a confusing TLS warning that relay operators might get when
9616 someone tries to talk to their OrPort. It is neither the operator's
9617 fault nor can they do anything about it. Fixes bug 1364; bugfix
9621 Changes in version 0.2.2.11-alpha - 2010-04-15
9622 Tor 0.2.2.11-alpha fixes yet another instance of broken OpenSSL
9623 libraries that was causing some relays to drop out of the consensus.
9626 - Directory mirrors were fetching relay descriptors only from v2
9627 directory authorities, rather than v3 authorities like they should.
9628 Only 2 v2 authorities remain (compared to 7 v3 authorities), leading
9629 to a serious bottleneck. Bugfix on 0.2.0.9-alpha. Fixes bug 1324.
9630 - Fix a parsing error that made every possible value of
9631 CircPriorityHalflifeMsec get treated as "1 msec". Bugfix
9632 on 0.2.2.7-alpha. Rename CircPriorityHalflifeMsec to
9633 CircuitPriorityHalflifeMsec, so authorities can tell newer relays
9634 about the option without breaking older ones.
9635 - Fix SSL renegotiation behavior on OpenSSL versions like on Centos
9636 that claim to be earlier than 0.9.8m, but which have in reality
9637 backported huge swaths of 0.9.8m or 0.9.8n renegotiation
9638 behavior. Possible fix for some cases of bug 1346.
9641 - Experiment with a more aggressive approach to preventing clients
9642 from making one-hop exit streams. Exit relays who want to try it
9643 out can set "RefuseUnknownExits 1" in their torrc, and then look
9644 for "Attempt by %s to open a stream" log messages. Let us know
9646 - Add support for statically linking zlib by specifying
9647 --enable-static-zlib, to go with our support for statically linking
9648 openssl and libevent. Resolves bug 1358.
9651 - Fix a segfault that happens whenever a Tor client that is using
9652 libevent2's bufferevents gets a hup signal. Bugfix on 0.2.2.5-alpha;
9654 - When we cleaned up the contrib/tor-exit-notice.html file, we left
9655 out the first line. Fixes bug 1295.
9656 - When building the manpage from a tarball, we required asciidoc, but
9657 the asciidoc -> roff/html conversion was already done for the
9658 tarball. Make 'make' complain only when we need asciidoc (either
9659 because we're compiling directly from git, or because we altered
9660 the asciidoc manpage in the tarball). Bugfix on 0.2.2.9-alpha.
9661 - When none of the directory authorities vote on any params, Tor
9662 segfaulted when trying to make the consensus from the votes. We
9663 didn't trigger the bug in practice, because authorities do include
9664 params in their votes. Bugfix on 0.2.2.10-alpha; fixes bug 1322.
9667 - In the util/threads test, no longer free the test_mutex before all
9668 worker threads have finished. Bugfix on 0.2.1.6-alpha.
9669 - The master thread could starve the worker threads quite badly on
9670 certain systems, causing them to run only partially in the allowed
9671 window. This resulted in test failures. Now the master thread sleeps
9672 occasionally for a few microseconds while the two worker-threads
9673 compete for the mutex. Bugfix on 0.2.0.1-alpha.
9676 Changes in version 0.2.2.10-alpha - 2010-03-07
9677 Tor 0.2.2.10-alpha fixes a regression introduced in 0.2.2.9-alpha that
9678 could prevent relays from guessing their IP address correctly. It also
9679 starts the groundwork for another client-side performance boost, since
9680 currently we're not making efficient use of relays that have both the
9681 Guard flag and the Exit flag.
9684 - Fix a regression from our patch for bug 1244 that caused relays
9685 to guess their IP address incorrectly if they didn't set Address
9686 in their torrc and/or their address fails to resolve. Bugfix on
9687 0.2.2.9-alpha; fixes bug 1269.
9689 o Major features (performance):
9690 - Directory authorities now compute consensus weightings that instruct
9691 clients how to weight relays flagged as Guard, Exit, Guard+Exit,
9692 and no flag. Clients that use these weightings will distribute
9693 network load more evenly across these different relay types. The
9694 weightings are in the consensus so we can change them globally in
9695 the future. Extra thanks to "outofwords" for finding some nasty
9696 security bugs in the first implementation of this feature.
9698 o Minor features (performance):
9699 - Always perform router selections using weighted relay bandwidth,
9700 even if we don't need a high capacity circuit at the time. Non-fast
9701 circuits now only differ from fast ones in that they can use relays
9702 not marked with the Fast flag. This "feature" could turn out to
9703 be a horrible bug; we should investigate more before it goes into
9707 - Allow disabling building of the manpages. Skipping the manpage
9708 speeds up the build considerably.
9710 o Minor bugfixes (on 0.2.2.x):
9711 - Fix a memleak in the EXTENDCIRCUIT logic. Spotted by coverity.
9712 Bugfix on 0.2.2.9-alpha.
9713 - Disallow values larger than INT32_MAX for PerConnBWRate|Burst
9714 config option. Bugfix on 0.2.2.7-alpha.
9715 - Ship the asciidoc-helper file in the tarball, so that people can
9716 build from source if they want to, and touching the .1.txt files
9717 doesn't break the build. Bugfix on 0.2.2.9-alpha.
9719 o Minor bugfixes (on 0.2.1.x or earlier):
9720 - Fix a dereference-then-NULL-check sequence when publishing
9721 descriptors. Bugfix on 0.2.1.5-alpha. Discovered by ekir; fixes
9723 - Fix another dereference-then-NULL-check sequence. Bugfix on
9724 0.2.1.14-rc. Discovered by ekir; fixes bug 1256.
9725 - Make sure we treat potentially not NUL-terminated strings correctly.
9726 Bugfix on 0.1.1.13-alpha. Discovered by rieo; fixes bug 1257.
9728 o Code simplifications and refactoring:
9729 - Fix some urls in the exit notice file and make it XHTML1.1 strict
9730 compliant. Based on a patch from Christian Kujau.
9731 - Don't use sed in asciidoc-helper anymore.
9732 - Make the build process fail if asciidoc cannot be found and
9733 building with asciidoc isn't disabled.
9736 Changes in version 0.2.2.9-alpha - 2010-02-22
9737 Tor 0.2.2.9-alpha makes Tor work again on the latest OS X, updates the
9738 location of a directory authority, and cleans up a bunch of small bugs.
9740 o Directory authority changes:
9741 - Change IP address for dannenberg (v3 directory authority), and
9742 remove moria2 (obsolete v1, v2 directory authority and v0 hidden
9743 service directory authority) from the list.
9746 - Make Tor work again on the latest OS X: when deciding whether to
9747 use strange flags to turn TLS renegotiation on, detect the OpenSSL
9748 version at run-time, not compile time. We need to do this because
9749 Apple doesn't update its dev-tools headers when it updates its
9750 libraries in a security patch.
9751 - Fix a potential buffer overflow in lookup_last_hid_serv_request()
9752 that could happen on 32-bit platforms with 64-bit time_t. Also fix
9753 a memory leak when requesting a hidden service descriptor we've
9754 requested before. Fixes bug 1242, bugfix on 0.2.0.18-alpha. Found
9756 - Authorities could be tricked into giving out the Exit flag to relays
9757 that didn't allow exiting to any ports. This bug could screw
9758 with load balancing and stats. Bugfix on 0.1.1.6-alpha; fixes bug
9759 1238. Bug discovered by Martin Kowalczyk.
9760 - When freeing a session key, zero it out completely. We only zeroed
9761 the first ptrsize bytes. Bugfix on 0.0.2pre8. Discovered and
9762 patched by ekir. Fixes bug 1254.
9765 - Fix static compilation by listing the openssl libraries in the right
9766 order. Bugfix on Tor 0.2.2.8-alpha; fixes bug 1237.
9767 - Resume handling .exit hostnames in a special way: originally we
9768 stripped the .exit part and used the requested exit relay. In
9769 0.2.2.1-alpha we stopped treating them in any special way, meaning
9770 if you use a .exit address then Tor will pass it on to the exit
9771 relay. Now we reject the .exit stream outright, since that behavior
9772 might be more expected by the user. Found and diagnosed by Scott
9773 Bennett and Downie on or-talk.
9774 - Don't spam the controller with events when we have no file
9775 descriptors available. Bugfix on 0.2.1.5-alpha. (Rate-limiting
9776 for log messages was already solved from bug 748.)
9777 - Avoid a bogus overlapped memcpy in tor_addr_copy(). Reported by
9779 - Make the DNSPort option work with libevent 2.x. Don't alter the
9780 behavior for libevent 1.x. Fixes bug 1143. Found by SwissTorExit.
9781 - Emit a GUARD DROPPED controller event for a case we missed.
9782 - Make more fields in the controller protocol case-insensitive, since
9783 control-spec.txt said they were.
9784 - Refactor resolve_my_address() to not use gethostbyname() anymore.
9785 Fixes bug 1244; bugfix on 0.0.2pre25. Reported by Mike Mestnik.
9786 - Fix a spec conformance issue: the network-status-version token
9787 must be the first token in a v3 consensus or vote. Discovered by
9788 parakeep. Bugfix on 0.2.0.3-alpha.
9790 o Code simplifications and refactoring:
9791 - Generate our manpage and HTML documentation using Asciidoc. This
9792 change should make it easier to maintain the documentation, and
9794 - Remove the --enable-iphone option. According to reports from Marco
9795 Bonetti, Tor builds fine without any special tweaking on recent
9796 iPhone SDK versions.
9797 - Removed some unnecessary files from the source distribution. The
9798 AUTHORS file has now been merged into the people page on the
9799 website. The roadmaps and design doc can now be found in the
9800 projects directory in svn.
9801 - Enabled various circuit build timeout constants to be controlled
9802 by consensus parameters. Also set better defaults for these
9803 parameters based on experimentation on broadband and simulated
9807 - The 'EXTENDCIRCUIT' control port command can now be used with
9808 a circ id of 0 and no path. This feature will cause Tor to build
9809 a new 'fast' general purpose circuit using its own path selection
9811 - Added a BUILDTIMEOUT_SET controller event to describe changes
9812 to the circuit build timeout.
9813 - Future-proof the controller protocol a bit by ignoring keyword
9814 arguments we do not recognize.
9815 - Expand homedirs passed to tor-checkkey. This should silence a
9816 coverity complaint about passing a user-supplied string into
9817 open() without checking it.
9820 Changes in version 0.2.1.25 - 2010-03-16
9821 Tor 0.2.1.25 fixes a regression introduced in 0.2.1.23 that could
9822 prevent relays from guessing their IP address correctly. It also fixes
9823 several minor potential security bugs.
9826 - Fix a regression from our patch for bug 1244 that caused relays
9827 to guess their IP address incorrectly if they didn't set Address
9828 in their torrc and/or their address fails to resolve. Bugfix on
9829 0.2.1.23; fixes bug 1269.
9830 - When freeing a session key, zero it out completely. We only zeroed
9831 the first ptrsize bytes. Bugfix on 0.0.2pre8. Discovered and
9832 patched by ekir. Fixes bug 1254.
9835 - Fix a dereference-then-NULL-check sequence when publishing
9836 descriptors. Bugfix on 0.2.1.5-alpha. Discovered by ekir; fixes
9838 - Fix another dereference-then-NULL-check sequence. Bugfix on
9839 0.2.1.14-rc. Discovered by ekir; fixes bug 1256.
9840 - Make sure we treat potentially not NUL-terminated strings correctly.
9841 Bugfix on 0.1.1.13-alpha. Discovered by rieo; fixes bug 1257.
9845 Changes in version 0.2.1.24 - 2010-02-21
9846 Tor 0.2.1.24 makes Tor work again on the latest OS X -- this time
9850 - Work correctly out-of-the-box with even more vendor-patched versions
9851 of OpenSSL. In particular, make it so Debian and OS X don't need
9852 customized patches to run/build.
9855 Changes in version 0.2.1.23 - 2010-02-13
9856 Tor 0.2.1.23 fixes a huge client-side performance bug, makes Tor work
9857 again on the latest OS X, and updates the location of a directory
9860 o Major bugfixes (performance):
9861 - We were selecting our guards uniformly at random, and then weighting
9862 which of our guards we'd use uniformly at random. This imbalance
9863 meant that Tor clients were severely limited on throughput (and
9864 probably latency too) by the first hop in their circuit. Now we
9865 select guards weighted by currently advertised bandwidth. We also
9866 automatically discard guards picked using the old algorithm. Fixes
9867 bug 1217; bugfix on 0.2.1.3-alpha. Found by Mike Perry.
9870 - Make Tor work again on the latest OS X: when deciding whether to
9871 use strange flags to turn TLS renegotiation on, detect the OpenSSL
9872 version at run-time, not compile time. We need to do this because
9873 Apple doesn't update its dev-tools headers when it updates its
9874 libraries in a security patch.
9875 - Fix a potential buffer overflow in lookup_last_hid_serv_request()
9876 that could happen on 32-bit platforms with 64-bit time_t. Also fix
9877 a memory leak when requesting a hidden service descriptor we've
9878 requested before. Fixes bug 1242, bugfix on 0.2.0.18-alpha. Found
9881 o Directory authority changes:
9882 - Change IP address for dannenberg (v3 directory authority), and
9883 remove moria2 (obsolete v1, v2 directory authority and v0 hidden
9884 service directory authority) from the list.
9887 - Refactor resolve_my_address() to not use gethostbyname() anymore.
9888 Fixes bug 1244; bugfix on 0.0.2pre25. Reported by Mike Mestnik.
9891 - Avoid a mad rush at the beginning of each month when each client
9892 rotates half of its guards. Instead we spread the rotation out
9893 throughout the month, but we still avoid leaving a precise timestamp
9894 in the state file about when we first picked the guard. Improves
9895 over the behavior introduced in 0.1.2.17.
9898 Changes in version 0.2.2.8-alpha - 2010-01-26
9899 Tor 0.2.2.8-alpha fixes a crash bug in 0.2.2.7-alpha that has been
9900 causing bridge relays to disappear. If you're running a bridge,
9904 - Fix a memory corruption bug on bridges that occured during the
9905 inclusion of stats data in extra-info descriptors. Also fix the
9906 interface for geoip_get_bridge_stats* to prevent similar bugs in
9907 the future. Diagnosis by Tas, patch by Karsten and Sebastian.
9908 Fixes bug 1208; bugfix on 0.2.2.7-alpha.
9911 - Ignore OutboundBindAddress when connecting to localhost.
9912 Connections to localhost need to come _from_ localhost, or else
9913 local servers (like DNS and outgoing HTTP/SOCKS proxies) will often
9917 Changes in version 0.2.2.7-alpha - 2010-01-19
9918 Tor 0.2.2.7-alpha fixes a huge client-side performance bug, as well
9919 as laying the groundwork for further relay-side performance fixes. It
9920 also starts cleaning up client behavior with respect to the EntryNodes,
9921 ExitNodes, and StrictNodes config options.
9923 This release also rotates two directory authority keys, due to a
9924 security breach of some of the Torproject servers.
9926 o Directory authority changes:
9927 - Rotate keys (both v3 identity and relay identity) for moria1
9930 o Major features (performance):
9931 - We were selecting our guards uniformly at random, and then weighting
9932 which of our guards we'd use uniformly at random. This imbalance
9933 meant that Tor clients were severely limited on throughput (and
9934 probably latency too) by the first hop in their circuit. Now we
9935 select guards weighted by currently advertised bandwidth. We also
9936 automatically discard guards picked using the old algorithm. Fixes
9937 bug 1217; bugfix on 0.2.1.3-alpha. Found by Mike Perry.
9938 - When choosing which cells to relay first, relays can now favor
9939 circuits that have been quiet recently, to provide lower latency
9940 for low-volume circuits. By default, relays enable or disable this
9941 feature based on a setting in the consensus. You can override
9942 this default by using the new "CircuitPriorityHalflife" config
9943 option. Design and code by Ian Goldberg, Can Tang, and Chris
9945 - Add separate per-conn write limiting to go with the per-conn read
9946 limiting. We added a global write limit in Tor 0.1.2.5-alpha,
9947 but never per-conn write limits.
9948 - New consensus params "bwconnrate" and "bwconnburst" to let us
9949 rate-limit client connections as they enter the network. It's
9950 controlled in the consensus so we can turn it on and off for
9951 experiments. It's starting out off. Based on proposal 163.
9953 o Major features (relay selection options):
9954 - Switch to a StrictNodes config option, rather than the previous
9955 "StrictEntryNodes" / "StrictExitNodes" separation that was missing a
9956 "StrictExcludeNodes" option.
9957 - If EntryNodes, ExitNodes, ExcludeNodes, or ExcludeExitNodes
9958 change during a config reload, mark and discard all our origin
9959 circuits. This fix should address edge cases where we change the
9960 config options and but then choose a circuit that we created before
9962 - If EntryNodes or ExitNodes are set, be more willing to use an
9963 unsuitable (e.g. slow or unstable) circuit. The user asked for it,
9965 - Make EntryNodes config option much more aggressive even when
9966 StrictNodes is not set. Before it would prepend your requested
9967 entrynodes to your list of guard nodes, but feel free to use others
9968 after that. Now it chooses only from your EntryNodes if any of
9969 those are available, and only falls back to others if a) they're
9970 all down and b) StrictNodes is not set.
9971 - Now we refresh your entry guards from EntryNodes at each consensus
9972 fetch -- rather than just at startup and then they slowly rot as
9973 the network changes.
9976 - Stop bridge directory authorities from answering dbg-stability.txt
9977 directory queries, which would let people fetch a list of all
9978 bridge identities they track. Bugfix on 0.2.1.6-alpha.
9981 - Log a notice when we get a new control connection. Now it's easier
9982 for security-conscious users to recognize when a local application
9983 is knocking on their controller door. Suggested by bug 1196.
9984 - New config option "CircuitStreamTimeout" to override our internal
9985 timeout schedule for how many seconds until we detach a stream from
9986 a circuit and try a new circuit. If your network is particularly
9987 slow, you might want to set this to a number like 60.
9988 - New controller command "getinfo config-text". It returns the
9989 contents that Tor would write if you send it a SAVECONF command,
9990 so the controller can write the file to disk itself.
9991 - New options for SafeLogging to allow scrubbing only log messages
9992 generated while acting as a relay.
9993 - Ship the bridges spec file in the tarball too.
9994 - Avoid a mad rush at the beginning of each month when each client
9995 rotates half of its guards. Instead we spread the rotation out
9996 throughout the month, but we still avoid leaving a precise timestamp
9997 in the state file about when we first picked the guard. Improves
9998 over the behavior introduced in 0.1.2.17.
10000 o Minor bugfixes (compiling):
10001 - Fix compilation on OS X 10.3, which has a stub mlockall() but
10002 hides it. Bugfix on 0.2.2.6-alpha.
10003 - Fix compilation on Solaris by removing support for the
10004 DisableAllSwap config option. Solaris doesn't have an rlimit for
10005 mlockall, so we cannot use it safely. Fixes bug 1198; bugfix on
10008 o Minor bugfixes (crashes):
10009 - Do not segfault when writing buffer stats when we haven't observed
10010 a single circuit to report about. Found by Fabian Lanze. Bugfix on
10012 - If we're in the pathological case where there's no exit bandwidth
10013 but there is non-exit bandwidth, or no guard bandwidth but there
10014 is non-guard bandwidth, don't crash during path selection. Bugfix
10016 - Fix an impossible-to-actually-trigger buffer overflow in relay
10017 descriptor generation. Bugfix on 0.1.0.15.
10019 o Minor bugfixes (privacy):
10020 - Fix an instance where a Tor directory mirror might accidentally
10021 log the IP address of a misbehaving Tor client. Bugfix on
10023 - Don't list Windows capabilities in relay descriptors. We never made
10024 use of them, and maybe it's a bad idea to publish them. Bugfix
10027 o Minor bugfixes (other):
10028 - Resolve an edge case in path weighting that could make us misweight
10029 our relay selection. Fixes bug 1203; bugfix on 0.0.8rc1.
10030 - Fix statistics on client numbers by country as seen by bridges that
10031 were broken in 0.2.2.1-alpha. Also switch to reporting full 24-hour
10032 intervals instead of variable 12-to-48-hour intervals.
10033 - After we free an internal connection structure, overwrite it
10034 with a different memory value than we use for overwriting a freed
10035 internal circuit structure. Should help with debugging. Suggested
10037 - Update our OpenSSL 0.9.8l fix so that it works with OpenSSL 0.9.8m
10040 o Removed features:
10041 - Remove the HSAuthorityRecordStats option that version 0 hidden
10042 service authorities could have used to track statistics of overall
10043 hidden service usage.
10046 Changes in version 0.2.1.22 - 2010-01-19
10047 Tor 0.2.1.22 fixes a critical privacy problem in bridge directory
10048 authorities -- it would tell you its whole history of bridge descriptors
10049 if you make the right directory request. This stable update also
10050 rotates two of the seven v3 directory authority keys and locations.
10052 o Directory authority changes:
10053 - Rotate keys (both v3 identity and relay identity) for moria1
10057 - Stop bridge directory authorities from answering dbg-stability.txt
10058 directory queries, which would let people fetch a list of all
10059 bridge identities they track. Bugfix on 0.2.1.6-alpha.
10062 Changes in version 0.2.1.21 - 2009-12-21
10063 Tor 0.2.1.21 fixes an incompatibility with the most recent OpenSSL
10064 library. If you use Tor on Linux / Unix and you're getting SSL
10065 renegotiation errors, upgrading should help. We also recommend an
10066 upgrade if you're an exit relay.
10069 - Work around a security feature in OpenSSL 0.9.8l that prevents our
10070 handshake from working unless we explicitly tell OpenSSL that we
10071 are using SSL renegotiation safely. We are, of course, but OpenSSL
10072 0.9.8l won't work unless we say we are.
10073 - Avoid crashing if the client is trying to upload many bytes and the
10074 circuit gets torn down at the same time, or if the flip side
10075 happens on the exit relay. Bugfix on 0.2.0.1-alpha; fixes bug 1150.
10078 - Do not refuse to learn about authority certs and v2 networkstatus
10079 documents that are older than the latest consensus. This bug might
10080 have degraded client bootstrapping. Bugfix on 0.2.0.10-alpha.
10081 Spotted and fixed by xmux.
10082 - Fix a couple of very-hard-to-trigger memory leaks, and one hard-to-
10083 trigger platform-specific option misparsing case found by Coverity
10085 - Fix a compilation warning on Fedora 12 by removing an impossible-to-
10086 trigger assert. Fixes bug 1173.
10089 Changes in version 0.2.2.6-alpha - 2009-11-19
10090 Tor 0.2.2.6-alpha lays the groundwork for many upcoming features:
10091 support for the new lower-footprint "microdescriptor" directory design,
10092 future-proofing our consensus format against new hash functions or
10093 other changes, and an Android port. It also makes Tor compatible with
10094 the upcoming OpenSSL 0.9.8l release, and fixes a variety of bugs.
10097 - Directory authorities can now create, vote on, and serve multiple
10098 parallel formats of directory data as part of their voting process.
10099 Partially implements Proposal 162: "Publish the consensus in
10101 - Directory authorities can now agree on and publish small summaries
10102 of router information that clients can use in place of regular
10103 server descriptors. This transition will eventually allow clients
10104 to use far less bandwidth for downloading information about the
10105 network. Begins the implementation of Proposal 158: "Clients
10106 download consensus + microdescriptors".
10107 - The directory voting system is now extensible to use multiple hash
10108 algorithms for signatures and resource selection. Newer formats
10109 are signed with SHA256, with a possibility for moving to a better
10110 hash algorithm in the future.
10111 - New DisableAllSwap option. If set to 1, Tor will attempt to lock all
10112 current and future memory pages via mlockall(). On supported
10113 platforms (modern Linux and probably BSD but not Windows or OS X),
10114 this should effectively disable any and all attempts to page out
10115 memory. This option requires that you start your Tor as root --
10116 if you use DisableAllSwap, please consider using the User option
10117 to properly reduce the privileges of your Tor.
10118 - Numerous changes, bugfixes, and workarounds from Nathan Freitas
10119 to help Tor build correctly for Android phones.
10122 - Work around a security feature in OpenSSL 0.9.8l that prevents our
10123 handshake from working unless we explicitly tell OpenSSL that we
10124 are using SSL renegotiation safely. We are, but OpenSSL 0.9.8l
10125 won't work unless we say we are.
10128 - Fix a crash bug when trying to initialize the evdns module in
10129 Libevent 2. Bugfix on 0.2.1.16-rc.
10130 - Stop logging at severity 'warn' when some other Tor client tries
10131 to establish a circuit with us using weak DH keys. It's a protocol
10132 violation, but that doesn't mean ordinary users need to hear about
10133 it. Fixes the bug part of bug 1114. Bugfix on 0.1.0.13.
10134 - Do not refuse to learn about authority certs and v2 networkstatus
10135 documents that are older than the latest consensus. This bug might
10136 have degraded client bootstrapping. Bugfix on 0.2.0.10-alpha.
10137 Spotted and fixed by xmux.
10138 - Fix numerous small code-flaws found by Coverity Scan Rung 3.
10139 - If all authorities restart at once right before a consensus vote,
10140 nobody will vote about "Running", and clients will get a consensus
10141 with no usable relays. Instead, authorities refuse to build a
10142 consensus if this happens. Bugfix on 0.2.0.10-alpha; fixes bug 1066.
10143 - If your relay can't keep up with the number of incoming create
10144 cells, it would log one warning per failure into your logs. Limit
10145 warnings to 1 per minute. Bugfix on 0.0.2pre10; fixes bug 1042.
10146 - Bridges now use "reject *:*" as their default exit policy. Bugfix
10147 on 0.2.0.3-alpha; fixes bug 1113.
10148 - Fix a memory leak on directory authorities during voting that was
10149 introduced in 0.2.2.1-alpha. Found via valgrind.
10152 Changes in version 0.2.1.20 - 2009-10-15
10153 Tor 0.2.1.20 fixes a crash bug when you're accessing many hidden
10154 services at once, prepares for more performance improvements, and
10155 fixes a bunch of smaller bugs.
10157 The Windows and OS X bundles also include a more recent Vidalia,
10158 and switch from Privoxy to Polipo.
10160 The OS X installers are now drag and drop. It's best to un-install
10161 Tor/Vidalia and then install this new bundle, rather than upgrade. If
10162 you want to upgrade, you'll need to update the paths for Tor and Polipo
10163 in the Vidalia Settings window.
10166 - Send circuit or stream sendme cells when our window has decreased
10167 by 100 cells, not when it has decreased by 101 cells. Bug uncovered
10168 by Karsten when testing the "reduce circuit window" performance
10169 patch. Bugfix on the 54th commit on Tor -- from July 2002,
10170 before the release of Tor 0.0.0. This is the new winner of the
10172 - Fix a remotely triggerable memory leak when a consensus document
10173 contains more than one signature from the same voter. Bugfix on
10175 - Avoid segfault in rare cases when finishing an introduction circuit
10176 as a client and finding out that we don't have an introduction key
10177 for it. Fixes bug 1073. Reported by Aaron Swartz.
10180 - Tor now reads the "circwindow" parameter out of the consensus,
10181 and uses that value for its circuit package window rather than the
10182 default of 1000 cells. Begins the implementation of proposal 168.
10184 o New directory authorities:
10185 - Set up urras (run by Jacob Appelbaum) as the seventh v3 directory
10187 - Move moria1 and tonga to alternate IP addresses.
10190 - Fix a signed/unsigned compile warning in 0.2.1.19.
10191 - Fix possible segmentation fault on directory authorities. Bugfix on
10193 - Fix an extremely rare infinite recursion bug that could occur if
10194 we tried to log a message after shutting down the log subsystem.
10195 Found by Matt Edman. Bugfix on 0.2.0.16-alpha.
10196 - Fix an obscure bug where hidden services on 64-bit big-endian
10197 systems might mis-read the timestamp in v3 introduce cells, and
10198 refuse to connect back to the client. Discovered by "rotor".
10199 Bugfix on 0.2.1.6-alpha.
10200 - We were triggering a CLOCK_SKEW controller status event whenever
10201 we connect via the v2 connection protocol to any relay that has
10202 a wrong clock. Instead, we should only inform the controller when
10203 it's a trusted authority that claims our clock is wrong. Bugfix
10204 on 0.2.0.20-rc; starts to fix bug 1074. Reported by SwissTorExit.
10205 - We were telling the controller about CHECKING_REACHABILITY and
10206 REACHABILITY_FAILED status events whenever we launch a testing
10207 circuit or notice that one has failed. Instead, only tell the
10208 controller when we want to inform the user of overall success or
10209 overall failure. Bugfix on 0.1.2.6-alpha. Fixes bug 1075. Reported
10211 - Don't warn when we're using a circuit that ends with a node
10212 excluded in ExcludeExitNodes, but the circuit is not used to access
10213 the outside world. This should help fix bug 1090. Bugfix on
10215 - Work around a small memory leak in some versions of OpenSSL that
10216 stopped the memory used by the hostname TLS extension from being
10220 - Add a "getinfo status/accepted-server-descriptor" controller
10221 command, which is the recommended way for controllers to learn
10222 whether our server descriptor has been successfully received by at
10223 least on directory authority. Un-recommend good-server-descriptor
10224 getinfo and status events until we have a better design for them.
10227 Changes in version 0.2.2.5-alpha - 2009-10-11
10228 Tor 0.2.2.5-alpha fixes a few compile problems in 0.2.2.4-alpha.
10231 - Make the tarball compile again. Oops. Bugfix on 0.2.2.4-alpha.
10233 o Directory authorities:
10234 - Temporarily (just for this release) move dizum to an alternate
10238 Changes in version 0.2.2.4-alpha - 2009-10-10
10239 Tor 0.2.2.4-alpha fixes more crash bugs in 0.2.2.2-alpha. It also
10240 introduces a new unit test framework, shifts directry authority
10241 addresses around to reduce the impact from recent blocking events,
10242 and fixes a few smaller bugs.
10245 - Fix several more asserts in the circuit_build_times code, for
10246 example one that causes Tor to fail to start once we have
10247 accumulated 5000 build times in the state file. Bugfixes on
10248 0.2.2.2-alpha; fixes bug 1108.
10250 o New directory authorities:
10251 - Move moria1 and Tonga to alternate IP addresses.
10254 - Log SSL state transitions at debug level during handshake, and
10255 include SSL states in error messages. This may help debug future
10256 SSL handshake issues.
10257 - Add a new "Handshake" log domain for activities that happen
10258 during the TLS handshake.
10259 - Revert to the "June 3 2009" ip-to-country file. The September one
10260 seems to have removed most US IP addresses.
10261 - Directory authorities now reject Tor relays with versions less than
10262 0.1.2.14. This step cuts out four relays from the current network,
10263 none of which are very big.
10266 - Fix a couple of smaller issues with gathering statistics. Bugfixes
10268 - Fix two memory leaks in the error case of
10269 circuit_build_times_parse_state(). Bugfix on 0.2.2.2-alpha.
10270 - Don't count one-hop circuits when we're estimating how long it
10271 takes circuits to build on average. Otherwise we'll set our circuit
10272 build timeout lower than we should. Bugfix on 0.2.2.2-alpha.
10273 - Directory authorities no longer change their opinion of, or vote on,
10274 whether a router is Running, unless they have themselves been
10275 online long enough to have some idea. Bugfix on 0.2.0.6-alpha.
10278 o Code simplifications and refactoring:
10279 - Revise our unit tests to use the "tinytest" framework, so we
10280 can run tests in their own processes, have smarter setup/teardown
10281 code, and so on. The unit test code has moved to its own
10282 subdirectory, and has been split into multiple modules.
10285 Changes in version 0.2.2.3-alpha - 2009-09-23
10286 Tor 0.2.2.3-alpha fixes a few crash bugs in 0.2.2.2-alpha.
10289 - Fix an overzealous assert in our new circuit build timeout code.
10290 Bugfix on 0.2.2.2-alpha; fixes bug 1103.
10293 - If the networkstatus consensus tells us that we should use a
10294 negative circuit package window, ignore it. Otherwise we'll
10295 believe it and then trigger an assert. Bugfix on 0.2.2.2-alpha.
10298 Changes in version 0.2.2.2-alpha - 2009-09-21
10299 Tor 0.2.2.2-alpha introduces our latest performance improvement for
10300 clients: Tor tracks the average time it takes to build a circuit, and
10301 avoids using circuits that take too long to build. For fast connections,
10302 this feature can cut your expected latency in half. For slow or flaky
10303 connections, it could ruin your Tor experience. Let us know if it does!
10306 - Tor now tracks how long it takes to build client-side circuits
10307 over time, and adapts its timeout to local network performance.
10308 Since a circuit that takes a long time to build will also provide
10309 bad performance, we get significant latency improvements by
10310 discarding the slowest 20% of circuits. Specifically, Tor creates
10311 circuits more aggressively than usual until it has enough data
10312 points for a good timeout estimate. Implements proposal 151.
10313 We are especially looking for reports (good and bad) from users with
10314 both EDGE and broadband connections that can move from broadband
10315 to EDGE and find out if the build-time data in the .tor/state gets
10316 reset without loss of Tor usability. You should also see a notice
10317 log message telling you that Tor has reset its timeout.
10318 - Directory authorities can now vote on arbitary integer values as
10319 part of the consensus process. This is designed to help set
10320 network-wide parameters. Implements proposal 167.
10321 - Tor now reads the "circwindow" parameter out of the consensus,
10322 and uses that value for its circuit package window rather than the
10323 default of 1000 cells. Begins the implementation of proposal 168.
10326 - Fix a remotely triggerable memory leak when a consensus document
10327 contains more than one signature from the same voter. Bugfix on
10331 - Fix an extremely rare infinite recursion bug that could occur if
10332 we tried to log a message after shutting down the log subsystem.
10333 Found by Matt Edman. Bugfix on 0.2.0.16-alpha.
10334 - Fix parsing for memory or time units given without a space between
10335 the number and the unit. Bugfix on 0.2.2.1-alpha; fixes bug 1076.
10336 - A networkstatus vote must contain exactly one signature. Spec
10337 conformance issue. Bugfix on 0.2.0.3-alpha.
10338 - Fix an obscure bug where hidden services on 64-bit big-endian
10339 systems might mis-read the timestamp in v3 introduce cells, and
10340 refuse to connect back to the client. Discovered by "rotor".
10341 Bugfix on 0.2.1.6-alpha.
10342 - We were triggering a CLOCK_SKEW controller status event whenever
10343 we connect via the v2 connection protocol to any relay that has
10344 a wrong clock. Instead, we should only inform the controller when
10345 it's a trusted authority that claims our clock is wrong. Bugfix
10346 on 0.2.0.20-rc; starts to fix bug 1074. Reported by SwissTorExit.
10347 - We were telling the controller about CHECKING_REACHABILITY and
10348 REACHABILITY_FAILED status events whenever we launch a testing
10349 circuit or notice that one has failed. Instead, only tell the
10350 controller when we want to inform the user of overall success or
10351 overall failure. Bugfix on 0.1.2.6-alpha. Fixes bug 1075. Reported
10353 - Don't warn when we're using a circuit that ends with a node
10354 excluded in ExcludeExitNodes, but the circuit is not used to access
10355 the outside world. This should help fix bug 1090, but more problems
10356 remain. Bugfix on 0.2.1.6-alpha.
10357 - Work around a small memory leak in some versions of OpenSSL that
10358 stopped the memory used by the hostname TLS extension from being
10360 - Make our 'torify' script more portable; if we have only one of
10361 'torsocks' or 'tsocks' installed, don't complain to the user;
10362 and explain our warning about tsocks better.
10365 - Add a "getinfo status/accepted-server-descriptor" controller
10366 command, which is the recommended way for controllers to learn
10367 whether our server descriptor has been successfully received by at
10368 least on directory authority. Un-recommend good-server-descriptor
10369 getinfo and status events until we have a better design for them.
10370 - Update to the "September 4 2009" ip-to-country file.
10373 Changes in version 0.2.2.1-alpha - 2009-08-26
10374 Tor 0.2.2.1-alpha disables ".exit" address notation by default, allows
10375 Tor clients to bootstrap on networks where only port 80 is reachable,
10376 makes it more straightforward to support hardware crypto accelerators,
10377 and starts the groundwork for gathering stats safely at relays.
10380 - Start the process of disabling ".exit" address notation, since it
10381 can be used for a variety of esoteric application-level attacks
10382 on users. To reenable it, set "AllowDotExit 1" in your torrc. Fix
10385 o New directory authorities:
10386 - Set up urras (run by Jacob Appelbaum) as the seventh v3 directory
10390 - New AccelName and AccelDir options add support for dynamic OpenSSL
10391 hardware crypto acceleration engines.
10392 - Tor now supports tunneling all of its outgoing connections over
10393 a SOCKS proxy, using the SOCKS4Proxy and/or SOCKS5Proxy
10394 configuration options. Code by Christopher Davis.
10397 - Send circuit or stream sendme cells when our window has decreased
10398 by 100 cells, not when it has decreased by 101 cells. Bug uncovered
10399 by Karsten when testing the "reduce circuit window" performance
10400 patch. Bugfix on the 54th commit on Tor -- from July 2002,
10401 before the release of Tor 0.0.0. This is the new winner of the
10404 o New options for gathering stats safely:
10405 - Directory mirrors that set "DirReqStatistics 1" write statistics
10406 about directory requests to disk every 24 hours. As compared to the
10407 --enable-geoip-stats flag in 0.2.1.x, there are a few improvements:
10408 1) stats are written to disk exactly every 24 hours; 2) estimated
10409 shares of v2 and v3 requests are determined as mean values, not at
10410 the end of a measurement period; 3) unresolved requests are listed
10411 with country code '??'; 4) directories also measure download times.
10412 - Exit nodes that set "ExitPortStatistics 1" write statistics on the
10413 number of exit streams and transferred bytes per port to disk every
10415 - Relays that set "CellStatistics 1" write statistics on how long
10416 cells spend in their circuit queues to disk every 24 hours.
10417 - Entry nodes that set "EntryStatistics 1" write statistics on the
10418 rough number and origins of connecting clients to disk every 24
10420 - Relays that write any of the above statistics to disk and set
10421 "ExtraInfoStatistics 1" include the past 24 hours of statistics in
10422 their extra-info documents.
10425 - New --digests command-line switch to output the digests of the
10426 source files Tor was built with.
10427 - The "torify" script now uses torsocks where available.
10428 - The memarea code now uses a sentinel value at the end of each area
10429 to make sure nothing writes beyond the end of an area. This might
10430 help debug some conceivable causes of bug 930.
10431 - Time and memory units in the configuration file can now be set to
10432 fractional units. For example, "2.5 GB" is now a valid value for
10434 - Certain Tor clients (such as those behind check.torproject.org) may
10435 want to fetch the consensus in an extra early manner. To enable this
10436 a user may now set FetchDirInfoExtraEarly to 1. This also depends on
10437 setting FetchDirInfoEarly to 1. Previous behavior will stay the same
10438 as only certain clients who must have this information sooner should
10440 - Instead of adding the svn revision to the Tor version string, report
10441 the git commit (when we're building from a git checkout).
10444 - If any of the v3 certs we download are unparseable, we should
10445 actually notice the failure so we don't retry indefinitely. Bugfix
10446 on 0.2.0.x; reported by "rotator".
10447 - If the cached cert file is unparseable, warn but don't exit.
10448 - Fix possible segmentation fault on directory authorities. Bugfix on
10450 - When Tor fails to parse a descriptor of any kind, dump it to disk.
10451 Might help diagnosing bug 1051.
10453 o Deprecated and removed features:
10454 - The controller no longer accepts the old obsolete "addr-mappings/"
10455 or "unregistered-servers-" GETINFO values.
10456 - Hidden services no longer publish version 0 descriptors, and clients
10457 do not request or use version 0 descriptors. However, the old hidden
10458 service authorities still accept and serve version 0 descriptors
10459 when contacted by older hidden services/clients.
10460 - The EXTENDED_EVENTS and VERBOSE_NAMES controller features are now
10461 always on; using them is necessary for correct forward-compatible
10463 - Remove support for .noconnect style addresses. Nobody was using
10464 them, and they provided another avenue for detecting Tor users
10465 via application-level web tricks.
10467 o Packaging changes:
10468 - Upgrade Vidalia from 0.1.15 to 0.2.3 in the Windows and OS X
10469 installer bundles. See
10470 https://trac.vidalia-project.net/browser/vidalia/tags/vidalia-0.2.3/CHANGELOG
10471 for details of what's new in Vidalia 0.2.3.
10472 - Windows Vidalia Bundle: update Privoxy from 3.0.6 to 3.0.14-beta.
10473 - OS X Vidalia Bundle: move to Polipo 1.0.4 with Tor specific
10474 configuration file, rather than the old Privoxy.
10475 - OS X Vidalia Bundle: Vidalia, Tor, and Polipo are compiled as
10476 x86-only for better compatibility with OS X 10.6, aka Snow Leopard.
10477 - OS X Tor Expert Bundle: Tor is compiled as x86-only for
10478 better compatibility with OS X 10.6, aka Snow Leopard.
10479 - OS X Vidalia Bundle: The multi-package installer is now replaced
10480 by a simple drag and drop to the /Applications folder. This change
10481 occurred with the upgrade to Vidalia 0.2.3.
10484 Changes in version 0.2.1.19 - 2009-07-28
10485 Tor 0.2.1.19 fixes a major bug with accessing and providing hidden
10486 services on Tor 0.2.1.3-alpha through 0.2.1.18.
10489 - Make accessing hidden services on 0.2.1.x work right again.
10490 Bugfix on 0.2.1.3-alpha; workaround for bug 1038. Diagnosis and
10491 part of patch provided by "optimist".
10494 - When a relay/bridge is writing out its identity key fingerprint to
10495 the "fingerprint" file and to its logs, write it without spaces. Now
10496 it will look like the fingerprints in our bridges documentation,
10497 and confuse fewer users.
10500 - Relays no longer publish a new server descriptor if they change
10501 their MaxAdvertisedBandwidth config option but it doesn't end up
10502 changing their advertised bandwidth numbers. Bugfix on 0.2.0.28-rc;
10503 fixes bug 1026. Patch from Sebastian.
10504 - Avoid leaking memory every time we get a create cell but we have
10505 so many already queued that we refuse it. Bugfix on 0.2.0.19-alpha;
10506 fixes bug 1034. Reported by BarkerJr.
10509 Changes in version 0.2.1.18 - 2009-07-24
10510 Tor 0.2.1.18 lays the foundations for performance improvements,
10511 adds status events to help users diagnose bootstrap problems, adds
10512 optional authentication/authorization for hidden services, fixes a
10513 variety of potential anonymity problems, and includes a huge pile of
10514 other features and bug fixes.
10517 - Add LIBS=-lrt to Makefile.am so the Tor RPMs use a static libevent.
10520 Changes in version 0.2.1.17-rc - 2009-07-07
10521 Tor 0.2.1.17-rc marks the fourth -- and hopefully last -- release
10522 candidate for the 0.2.1.x series. It lays the groundwork for further
10523 client performance improvements, and also fixes a big bug with directory
10524 authorities that were causing them to assign Guard and Stable flags
10527 The Windows bundles also finally include the geoip database that we
10528 thought we'd been shipping since 0.2.0.x (oops), and the OS X bundles
10529 should actually install Torbutton rather than giving you a cryptic
10530 failure message (oops).
10533 - Clients now use the bandwidth values in the consensus, rather than
10534 the bandwidth values in each relay descriptor. This approach opens
10535 the door to more accurate bandwidth estimates once the directory
10536 authorities start doing active measurements. Implements more of
10540 - When Tor clients restart after 1-5 days, they discard all their
10541 cached descriptors as too old, but they still use the cached
10542 consensus document. This approach is good for robustness, but
10543 bad for performance: since they don't know any bandwidths, they
10544 end up choosing at random rather than weighting their choice by
10545 speed. Fixed by the above feature of putting bandwidths in the
10546 consensus. Bugfix on 0.2.0.x.
10547 - Directory authorities were neglecting to mark relays down in their
10548 internal histories if the relays fall off the routerlist without
10549 ever being found unreachable. So there were relays in the histories
10550 that haven't been seen for eight months, and are listed as being
10551 up for eight months. This wreaked havoc on the "median wfu"
10552 and "median mtbf" calculations, in turn making Guard and Stable
10553 flags very wrong, hurting network performance. Fixes bugs 696 and
10554 969. Bugfix on 0.2.0.6-alpha.
10557 - Serve the DirPortFrontPage page even when we have been approaching
10558 our quotas recently. Fixes bug 1013; bugfix on 0.2.1.8-alpha.
10559 - The control port would close the connection before flushing long
10560 replies, such as the network consensus, if a QUIT command was issued
10561 before the reply had completed. Now, the control port flushes all
10562 pending replies before closing the connection. Also fixed a spurious
10563 warning when a QUIT command is issued after a malformed or rejected
10564 AUTHENTICATE command, but before the connection was closed. Patch
10565 by Marcus Griep. Bugfix on 0.2.0.x; fixes bugs 1015 and 1016.
10566 - When we can't find an intro key for a v2 hidden service descriptor,
10567 fall back to the v0 hidden service descriptor and log a bug message.
10568 Workaround for bug 1024.
10569 - Fix a log message that did not respect the SafeLogging option.
10573 - If we're a relay and we change our IP address, be more verbose
10574 about the reason that made us change. Should help track down
10575 further bugs for relays on dynamic IP addresses.
10578 Changes in version 0.2.0.35 - 2009-06-24
10580 - Avoid crashing in the presence of certain malformed descriptors.
10581 Found by lark, and by automated fuzzing.
10582 - Fix an edge case where a malicious exit relay could convince a
10583 controller that the client's DNS question resolves to an internal IP
10584 address. Bug found and fixed by "optimist"; bugfix on 0.1.2.8-beta.
10587 - Finally fix the bug where dynamic-IP relays disappear when their
10588 IP address changes: directory mirrors were mistakenly telling
10589 them their old address if they asked via begin_dir, so they
10590 never got an accurate answer about their new address, so they
10591 just vanished after a day. For belt-and-suspenders, relays that
10592 don't set Address in their config now avoid using begin_dir for
10593 all direct connections. Should fix bugs 827, 883, and 900.
10594 - Fix a timing-dependent, allocator-dependent, DNS-related crash bug
10595 that would occur on some exit nodes when DNS failures and timeouts
10596 occurred in certain patterns. Fix for bug 957.
10599 - When starting with a cache over a few days old, do not leak
10600 memory for the obsolete router descriptors in it. Bugfix on
10601 0.2.0.33; fixes bug 672.
10602 - Hidden service clients didn't use a cached service descriptor that
10603 was older than 15 minutes, but wouldn't fetch a new one either,
10604 because there was already one in the cache. Now, fetch a v2
10605 descriptor unless the same descriptor was added to the cache within
10606 the last 15 minutes. Fixes bug 997; reported by Marcus Griep.
10609 Changes in version 0.2.1.16-rc - 2009-06-20
10610 Tor 0.2.1.16-rc speeds up performance for fast exit relays, and fixes
10611 a bunch of minor bugs.
10614 - Fix an edge case where a malicious exit relay could convince a
10615 controller that the client's DNS question resolves to an internal IP
10616 address. Bug found and fixed by "optimist"; bugfix on 0.1.2.8-beta.
10618 o Major performance improvements (on 0.2.0.x):
10619 - Disable and refactor some debugging checks that forced a linear scan
10620 over the whole server-side DNS cache. These accounted for over 50%
10621 of CPU time on a relatively busy exit node's gprof profile. Found
10623 - Disable some debugging checks that appeared in exit node profile
10627 - Update to the "June 3 2009" ip-to-country file.
10628 - Do not have tor-resolve automatically refuse all .onion addresses;
10629 if AutomapHostsOnResolve is set in your torrc, this will work fine.
10631 o Minor bugfixes (on 0.2.0.x):
10632 - Log correct error messages for DNS-related network errors on
10634 - Fix a race condition that could cause crashes or memory corruption
10635 when running as a server with a controller listening for log
10637 - Avoid crashing when we have a policy specified in a DirPolicy or
10638 SocksPolicy or ReachableAddresses option with ports set on it,
10639 and we re-load the policy. May fix bug 996.
10640 - Hidden service clients didn't use a cached service descriptor that
10641 was older than 15 minutes, but wouldn't fetch a new one either,
10642 because there was already one in the cache. Now, fetch a v2
10643 descriptor unless the same descriptor was added to the cache within
10644 the last 15 minutes. Fixes bug 997; reported by Marcus Griep.
10646 o Minor bugfixes (on 0.2.1.x):
10647 - Don't warn users about low port and hibernation mix when they
10648 provide a *ListenAddress directive to fix that. Bugfix on
10650 - When switching back and forth between bridge mode, do not start
10651 gathering GeoIP data until two hours have passed.
10652 - Do not complain that the user has requested an excluded node as
10653 an exit when the node is not really an exit. This could happen
10654 because the circuit was for testing, or an introduction point.
10658 Changes in version 0.2.1.15-rc - 2009-05-25
10659 Tor 0.2.1.15-rc marks the second release candidate for the 0.2.1.x
10660 series. It fixes a major bug on fast exit relays, as well as a variety
10661 of more minor bugs.
10663 o Major bugfixes (on 0.2.0.x):
10664 - Fix a timing-dependent, allocator-dependent, DNS-related crash bug
10665 that would occur on some exit nodes when DNS failures and timeouts
10666 occurred in certain patterns. Fix for bug 957.
10668 o Minor bugfixes (on 0.2.0.x):
10669 - Actually return -1 in the error case for read_bandwidth_usage().
10670 Harmless bug, since we currently don't care about the return value
10671 anywhere. Bugfix on 0.2.0.9-alpha.
10672 - Provide a more useful log message if bug 977 (related to buffer
10673 freelists) ever reappears, and do not crash right away.
10674 - Fix an assertion failure on 64-bit platforms when we allocated
10675 memory right up to the end of a memarea, then realigned the memory
10676 one step beyond the end. Fixes a possible cause of bug 930.
10677 - Protect the count of open sockets with a mutex, so we can't
10678 corrupt it when two threads are closing or opening sockets at once.
10679 Fix for bug 939. Bugfix on 0.2.0.1-alpha.
10680 - Don't allow a bridge to publish its router descriptor to a
10681 non-bridge directory authority. Fixes part of bug 932.
10682 - When we change to or from being a bridge, reset our counts of
10683 client usage by country. Fixes bug 932.
10684 - Fix a bug that made stream bandwidth get misreported to the
10686 - Stop using malloc_usable_size() to use more area than we had
10687 actually allocated: it was safe, but made valgrind really unhappy.
10688 - Fix a memory leak when v3 directory authorities load their keys
10689 and cert from disk. Bugfix on 0.2.0.1-alpha.
10691 o Minor bugfixes (on 0.2.1.x):
10692 - Fix use of freed memory when deciding to mark a non-addable
10693 descriptor as never-downloadable. Bugfix on 0.2.1.9-alpha.
10696 Changes in version 0.2.1.14-rc - 2009-04-12
10697 Tor 0.2.1.14-rc marks the first release candidate for the 0.2.1.x
10698 series. It begins fixing some major performance problems, and also
10699 finally addresses the bug that was causing relays on dynamic IP
10700 addresses to fall out of the directory.
10703 - Clients replace entry guards that were chosen more than a few months
10704 ago. This change should significantly improve client performance,
10705 especially once more people upgrade, since relays that have been
10706 a guard for a long time are currently overloaded.
10708 o Major bugfixes (on 0.2.0):
10709 - Finally fix the bug where dynamic-IP relays disappear when their
10710 IP address changes: directory mirrors were mistakenly telling
10711 them their old address if they asked via begin_dir, so they
10712 never got an accurate answer about their new address, so they
10713 just vanished after a day. For belt-and-suspenders, relays that
10714 don't set Address in their config now avoid using begin_dir for
10715 all direct connections. Should fix bugs 827, 883, and 900.
10716 - Relays were falling out of the networkstatus consensus for
10717 part of a day if they changed their local config but the
10718 authorities discarded their new descriptor as "not sufficiently
10719 different". Now directory authorities accept a descriptor as changed
10720 if bandwidthrate or bandwidthburst changed. Partial fix for bug 962;
10721 patch by Sebastian.
10722 - Avoid crashing in the presence of certain malformed descriptors.
10723 Found by lark, and by automated fuzzing.
10726 - When generating circuit events with verbose nicknames for
10727 controllers, try harder to look up nicknames for routers on a
10728 circuit. (Previously, we would look in the router descriptors we had
10729 for nicknames, but not in the consensus.) Partial fix for bug 941.
10730 - If the bridge config line doesn't specify a port, assume 443.
10731 This makes bridge lines a bit smaller and easier for users to
10733 - Raise the minimum bandwidth to be a relay from 20000 bytes to 20480
10734 bytes (aka 20KB/s), to match our documentation. Also update
10735 directory authorities so they always assign the Fast flag to relays
10736 with 20KB/s of capacity. Now people running relays won't suddenly
10737 find themselves not seeing any use, if the network gets faster
10739 - Update to the "April 3 2009" ip-to-country file.
10742 - Avoid trying to print raw memory to the logs when we decide to
10743 give up on downloading a given relay descriptor. Bugfix on
10745 - In tor-resolve, when the Tor client to use is specified by
10746 <hostname>:<port>, actually use the specified port rather than
10747 defaulting to 9050. Bugfix on 0.2.1.6-alpha.
10748 - Make directory usage recording work again. Bugfix on 0.2.1.6-alpha.
10749 - When starting with a cache over a few days old, do not leak
10750 memory for the obsolete router descriptors in it. Bugfix on
10752 - Avoid double-free on list of successfully uploaded hidden
10753 service discriptors. Fix for bug 948. Bugfix on 0.2.1.6-alpha.
10754 - Change memarea_strndup() implementation to work even when
10755 duplicating a string at the end of a page. This bug was
10756 harmless for now, but could have meant crashes later. Fix by
10757 lark. Bugfix on 0.2.1.1-alpha.
10758 - Limit uploaded directory documents to be 16M rather than 500K.
10759 The directory authorities were refusing v3 consensus votes from
10760 other authorities, since the votes are now 504K. Fixes bug 959;
10761 bugfix on 0.0.2pre17 (where we raised it from 50K to 500K ;).
10762 - Directory authorities should never send a 503 "busy" response to
10763 requests for votes or keys. Bugfix on 0.2.0.8-alpha; exposed by
10767 Changes in version 0.2.1.13-alpha - 2009-03-09
10768 Tor 0.2.1.13-alpha includes another big pile of minor bugfixes and
10769 cleanups. We're finally getting close to a release candidate.
10772 - Correctly update the list of which countries we exclude as
10773 exits, when the GeoIP file is loaded or reloaded. Diagnosed by
10774 lark. Bugfix on 0.2.1.6-alpha.
10776 o Minor bugfixes (on 0.2.0.x and earlier):
10777 - Automatically detect MacOSX versions earlier than 10.4.0, and
10778 disable kqueue from inside Tor when running with these versions.
10779 We previously did this from the startup script, but that was no
10780 help to people who didn't use the startup script. Resolves bug 863.
10781 - When we had picked an exit node for a connection, but marked it as
10782 "optional", and it turned out we had no onion key for the exit,
10783 stop wanting that exit and try again. This situation may not
10784 be possible now, but will probably become feasible with proposal
10785 158. Spotted by rovv. Fixes another case of bug 752.
10786 - Clients no longer cache certificates for authorities they do not
10787 recognize. Bugfix on 0.2.0.9-alpha.
10788 - When we can't transmit a DNS request due to a network error, retry
10789 it after a while, and eventually transmit a failing response to
10790 the RESOLVED cell. Bugfix on 0.1.2.5-alpha.
10791 - If the controller claimed responsibility for a stream, but that
10792 stream never finished making its connection, it would live
10793 forever in circuit_wait state. Now we close it after SocksTimeout
10794 seconds. Bugfix on 0.1.2.7-alpha; reported by Mike Perry.
10795 - Drop begin cells to a hidden service if they come from the middle
10796 of a circuit. Patch from lark.
10797 - When we erroneously receive two EXTEND cells for the same circuit
10798 ID on the same connection, drop the second. Patch from lark.
10799 - Fix a crash that occurs on exit nodes when a nameserver request
10800 timed out. Bugfix on 0.1.2.1-alpha; our CLEAR debugging code had
10801 been suppressing the bug since 0.1.2.10-alpha. Partial fix for
10803 - Do not assume that a stack-allocated character array will be
10804 64-bit aligned on platforms that demand that uint64_t access is
10805 aligned. Possible fix for bug 604.
10806 - Parse dates and IPv4 addresses in a locale- and libc-independent
10807 manner, to avoid platform-dependent behavior on malformed input.
10808 - Build correctly when configured to build outside the main source
10809 path. Patch from Michael Gold.
10810 - We were already rejecting relay begin cells with destination port
10811 of 0. Now also reject extend cells with destination port or address
10812 of 0. Suggested by lark.
10814 o Minor bugfixes (on 0.2.1.x):
10815 - Don't re-extend introduction circuits if we ran out of RELAY_EARLY
10816 cells. Bugfix on 0.2.1.3-alpha. Fixes more of bug 878.
10817 - If we're an exit node, scrub the IP address to which we are exiting
10818 in the logs. Bugfix on 0.2.1.8-alpha.
10821 - On Linux, use the prctl call to re-enable core dumps when the user
10823 - New controller event NEWCONSENSUS that lists the networkstatus
10824 lines for every recommended relay. Now controllers like Torflow
10825 can keep up-to-date on which relays they should be using.
10826 - Update to the "February 26 2009" ip-to-country file.
10829 Changes in version 0.2.0.34 - 2009-02-08
10830 Tor 0.2.0.34 features several more security-related fixes. You should
10831 upgrade, especially if you run an exit relay (remote crash) or a
10832 directory authority (remote infinite loop), or you're on an older
10833 (pre-XP) or not-recently-patched Windows (remote exploit).
10835 This release marks end-of-life for Tor 0.1.2.x. Those Tor versions
10836 have many known flaws, and nobody should be using them. You should
10837 upgrade. If you're using a Linux or BSD and its packages are obsolete,
10838 stop using those packages and upgrade anyway.
10841 - Fix an infinite-loop bug on handling corrupt votes under certain
10842 circumstances. Bugfix on 0.2.0.8-alpha.
10843 - Fix a temporary DoS vulnerability that could be performed by
10844 a directory mirror. Bugfix on 0.2.0.9-alpha; reported by lark.
10845 - Avoid a potential crash on exit nodes when processing malformed
10846 input. Remote DoS opportunity. Bugfix on 0.2.0.33.
10847 - Do not accept incomplete ipv4 addresses (like 192.168.0) as valid.
10848 Spec conformance issue. Bugfix on Tor 0.0.2pre27.
10851 - Fix compilation on systems where time_t is a 64-bit integer.
10852 Patch from Matthias Drochner.
10853 - Don't consider expiring already-closed client connections. Fixes
10854 bug 893. Bugfix on 0.0.2pre20.
10857 Changes in version 0.2.1.12-alpha - 2009-02-08
10858 Tor 0.2.1.12-alpha features several more security-related fixes. You
10859 should upgrade, especially if you run an exit relay (remote crash) or
10860 a directory authority (remote infinite loop), or you're on an older
10861 (pre-XP) or not-recently-patched Windows (remote exploit). It also
10862 includes a big pile of minor bugfixes and cleanups.
10865 - Fix an infinite-loop bug on handling corrupt votes under certain
10866 circumstances. Bugfix on 0.2.0.8-alpha.
10867 - Fix a temporary DoS vulnerability that could be performed by
10868 a directory mirror. Bugfix on 0.2.0.9-alpha; reported by lark.
10869 - Avoid a potential crash on exit nodes when processing malformed
10870 input. Remote DoS opportunity. Bugfix on 0.2.1.7-alpha.
10873 - Let controllers actually ask for the "clients_seen" event for
10874 getting usage summaries on bridge relays. Bugfix on 0.2.1.10-alpha;
10875 reported by Matt Edman.
10876 - Fix a compile warning on OSX Panther. Fixes bug 913; bugfix against
10878 - Fix a bug in address parsing that was preventing bridges or hidden
10879 service targets from being at IPv6 addresses.
10880 - Solve a bug that kept hardware crypto acceleration from getting
10881 enabled when accounting was turned on. Fixes bug 907. Bugfix on
10883 - Remove a bash-ism from configure.in to build properly on non-Linux
10884 platforms. Bugfix on 0.2.1.1-alpha.
10885 - Fix code so authorities _actually_ send back X-Descriptor-Not-New
10886 headers. Bugfix on 0.2.0.10-alpha.
10887 - Don't consider expiring already-closed client connections. Fixes
10888 bug 893. Bugfix on 0.0.2pre20.
10889 - Fix another interesting corner-case of bug 891 spotted by rovv:
10890 Previously, if two hosts had different amounts of clock drift, and
10891 one of them created a new connection with just the wrong timing,
10892 the other might decide to deprecate the new connection erroneously.
10893 Bugfix on 0.1.1.13-alpha.
10894 - Resolve a very rare crash bug that could occur when the user forced
10895 a nameserver reconfiguration during the middle of a nameserver
10896 probe. Fixes bug 526. Bugfix on 0.1.2.1-alpha.
10897 - Support changing value of ServerDNSRandomizeCase during SIGHUP.
10898 Bugfix on 0.2.1.7-alpha.
10899 - If we're using bridges and our network goes away, be more willing
10900 to forgive our bridges and try again when we get an application
10901 request. Bugfix on 0.2.0.x.
10904 - Support platforms where time_t is 64 bits long. (Congratulations,
10905 NetBSD!) Patch from Matthias Drochner.
10906 - Add a 'getinfo status/clients-seen' controller command, in case
10907 controllers want to hear clients_seen events but connect late.
10910 - Disable GCC's strict alias optimization by default, to avoid the
10911 likelihood of its introducing subtle bugs whenever our code violates
10912 the letter of C99's alias rules.
10915 Changes in version 0.2.0.33 - 2009-01-21
10916 Tor 0.2.0.33 fixes a variety of bugs that were making relays less
10917 useful to users. It also finally fixes a bug where a relay or client
10918 that's been off for many days would take a long time to bootstrap.
10920 This update also fixes an important security-related bug reported by
10921 Ilja van Sprundel. You should upgrade. (We'll send out more details
10922 about the bug once people have had some time to upgrade.)
10925 - Fix a heap-corruption bug that may be remotely triggerable on
10926 some platforms. Reported by Ilja van Sprundel.
10929 - When a stream at an exit relay is in state "resolving" or
10930 "connecting" and it receives an "end" relay cell, the exit relay
10931 would silently ignore the end cell and not close the stream. If
10932 the client never closes the circuit, then the exit relay never
10933 closes the TCP connection. Bug introduced in Tor 0.1.2.1-alpha;
10934 reported by "wood".
10935 - When sending CREATED cells back for a given circuit, use a 64-bit
10936 connection ID to find the right connection, rather than an addr:port
10937 combination. Now that we can have multiple OR connections between
10938 the same ORs, it is no longer possible to use addr:port to uniquely
10939 identify a connection.
10940 - Bridge relays that had DirPort set to 0 would stop fetching
10941 descriptors shortly after startup, and then briefly resume
10942 after a new bandwidth test and/or after publishing a new bridge
10943 descriptor. Bridge users that try to bootstrap from them would
10944 get a recent networkstatus but would get descriptors from up to
10945 18 hours earlier, meaning most of the descriptors were obsolete
10946 already. Reported by Tas; bugfix on 0.2.0.13-alpha.
10947 - Prevent bridge relays from serving their 'extrainfo' document
10948 to anybody who asks, now that extrainfo docs include potentially
10949 sensitive aggregated client geoip summaries. Bugfix on
10951 - If the cached networkstatus consensus is more than five days old,
10952 discard it rather than trying to use it. In theory it could be
10953 useful because it lists alternate directory mirrors, but in practice
10954 it just means we spend many minutes trying directory mirrors that
10955 are long gone from the network. Also discard router descriptors as
10956 we load them if they are more than five days old, since the onion
10957 key is probably wrong by now. Bugfix on 0.2.0.x. Fixes bug 887.
10960 - Do not mark smartlist_bsearch_idx() function as ATTR_PURE. This bug
10961 could make gcc generate non-functional binary search code. Bugfix
10963 - Build correctly on platforms without socklen_t.
10964 - Compile without warnings on solaris.
10965 - Avoid potential crash on internal error during signature collection.
10966 Fixes bug 864. Patch from rovv.
10967 - Correct handling of possible malformed authority signing key
10968 certificates with internal signature types. Fixes bug 880.
10969 Bugfix on 0.2.0.3-alpha.
10970 - Fix a hard-to-trigger resource leak when logging credential status.
10972 - When we can't initialize DNS because the network is down, do not
10973 automatically stop Tor from starting. Instead, we retry failed
10974 dns_init() every 10 minutes, and change the exit policy to reject
10975 *:* until one succeeds. Fixes bug 691.
10976 - Use 64 bits instead of 32 bits for connection identifiers used with
10977 the controller protocol, to greatly reduce risk of identifier reuse.
10978 - When we're choosing an exit node for a circuit, and we have
10979 no pending streams, choose a good general exit rather than one that
10980 supports "all the pending streams". Bugfix on 0.1.1.x. Fix by rovv.
10981 - Fix another case of assuming, when a specific exit is requested,
10982 that we know more than the user about what hosts it allows.
10983 Fixes one case of bug 752. Patch from rovv.
10984 - Clip the MaxCircuitDirtiness config option to a minimum of 10
10985 seconds. Warn the user if lower values are given in the
10986 configuration. Bugfix on 0.1.0.1-rc. Patch by Sebastian.
10987 - Clip the CircuitBuildTimeout to a minimum of 30 seconds. Warn the
10988 user if lower values are given in the configuration. Bugfix on
10989 0.1.1.17-rc. Patch by Sebastian.
10990 - Fix a memory leak when we decline to add a v2 rendezvous descriptor to
10991 the cache because we already had a v0 descriptor with the same ID.
10992 Bugfix on 0.2.0.18-alpha.
10993 - Fix a race condition when freeing keys shared between main thread
10994 and CPU workers that could result in a memory leak. Bugfix on
10995 0.1.0.1-rc. Fixes bug 889.
10996 - Send a valid END cell back when a client tries to connect to a
10997 nonexistent hidden service port. Bugfix on 0.1.2.15. Fixes bug
10998 840. Patch from rovv.
10999 - Check which hops rendezvous stream cells are associated with to
11000 prevent possible guess-the-streamid injection attacks from
11001 intermediate hops. Fixes another case of bug 446. Based on patch
11003 - If a broken client asks a non-exit router to connect somewhere,
11004 do not even do the DNS lookup before rejecting the connection.
11005 Fixes another case of bug 619. Patch from rovv.
11006 - When a relay gets a create cell it can't decrypt (e.g. because it's
11007 using the wrong onion key), we were dropping it and letting the
11008 client time out. Now actually answer with a destroy cell. Fixes
11009 bug 904. Bugfix on 0.0.2pre8.
11011 o Minor bugfixes (hidden services):
11012 - Do not throw away existing introduction points on SIGHUP. Bugfix on
11013 0.0.6pre1. Patch by Karsten. Fixes bug 874.
11016 - Report the case where all signatures in a detached set are rejected
11017 differently than the case where there is an error handling the
11019 - When we realize that another process has modified our cached
11020 descriptors, print out a more useful error message rather than
11021 triggering an assertion. Fixes bug 885. Patch from Karsten.
11022 - Implement the 0x20 hack to better resist DNS poisoning: set the
11023 case on outgoing DNS requests randomly, and reject responses that do
11024 not match the case correctly. This logic can be disabled with the
11025 ServerDNSRamdomizeCase setting, if you are using one of the 0.3%
11026 of servers that do not reliably preserve case in replies. See
11027 "Increased DNS Forgery Resistance through 0x20-Bit Encoding"
11029 - Check DNS replies for more matching fields to better resist DNS
11031 - Never use OpenSSL compression: it wastes RAM and CPU trying to
11032 compress cells, which are basically all encrypted, compressed, or
11036 Changes in version 0.2.1.11-alpha - 2009-01-20
11037 Tor 0.2.1.11-alpha finishes fixing the "if your Tor is off for a
11038 week it will take a long time to bootstrap again" bug. It also fixes
11039 an important security-related bug reported by Ilja van Sprundel. You
11040 should upgrade. (We'll send out more details about the bug once people
11041 have had some time to upgrade.)
11044 - Fix a heap-corruption bug that may be remotely triggerable on
11045 some platforms. Reported by Ilja van Sprundel.
11048 - Discard router descriptors as we load them if they are more than
11049 five days old. Otherwise if Tor is off for a long time and then
11050 starts with cached descriptors, it will try to use the onion
11051 keys in those obsolete descriptors when building circuits. Bugfix
11052 on 0.2.0.x. Fixes bug 887.
11055 - Try to make sure that the version of Libevent we're running with
11056 is binary-compatible with the one we built with. May address bug
11058 - Make setting ServerDNSRandomizeCase to 0 actually work. Bugfix
11059 for bug 905. Bugfix on 0.2.1.7-alpha.
11060 - Add a new --enable-local-appdata configuration switch to change
11061 the default location of the datadir on win32 from APPDATA to
11062 LOCAL_APPDATA. In the future, we should migrate to LOCAL_APPDATA
11063 entirely. Patch from coderman.
11066 - Make outbound DNS packets respect the OutboundBindAddress setting.
11067 Fixes the bug part of bug 798. Bugfix on 0.1.2.2-alpha.
11068 - When our circuit fails at the first hop (e.g. we get a destroy
11069 cell back), avoid using that OR connection anymore, and also
11070 tell all the one-hop directory requests waiting for it that they
11071 should fail. Bugfix on 0.2.1.3-alpha.
11072 - In the torify(1) manpage, mention that tsocks will leak your
11076 Changes in version 0.2.1.10-alpha - 2009-01-06
11077 Tor 0.2.1.10-alpha fixes two major bugs in bridge relays (one that
11078 would make the bridge relay not so useful if it had DirPort set to 0,
11079 and one that could let an attacker learn a little bit of information
11080 about the bridge's users), and a bug that would cause your Tor relay
11081 to ignore a circuit create request it can't decrypt (rather than reply
11082 with an error). It also fixes a wide variety of other bugs.
11085 - If the cached networkstatus consensus is more than five days old,
11086 discard it rather than trying to use it. In theory it could
11087 be useful because it lists alternate directory mirrors, but in
11088 practice it just means we spend many minutes trying directory
11089 mirrors that are long gone from the network. Helps bug 887 a bit;
11091 - Bridge relays that had DirPort set to 0 would stop fetching
11092 descriptors shortly after startup, and then briefly resume
11093 after a new bandwidth test and/or after publishing a new bridge
11094 descriptor. Bridge users that try to bootstrap from them would
11095 get a recent networkstatus but would get descriptors from up to
11096 18 hours earlier, meaning most of the descriptors were obsolete
11097 already. Reported by Tas; bugfix on 0.2.0.13-alpha.
11098 - Prevent bridge relays from serving their 'extrainfo' document
11099 to anybody who asks, now that extrainfo docs include potentially
11100 sensitive aggregated client geoip summaries. Bugfix on
11104 - New controller event "clients_seen" to report a geoip-based summary
11105 of which countries we've seen clients from recently. Now controllers
11106 like Vidalia can show bridge operators that they're actually making
11108 - Build correctly against versions of OpenSSL 0.9.8 or later built
11109 without support for deprecated functions.
11110 - Update to the "December 19 2008" ip-to-country file.
11112 o Minor bugfixes (on 0.2.0.x):
11113 - Authorities now vote for the Stable flag for any router whose
11114 weighted MTBF is at least 5 days, regardless of the mean MTBF.
11115 - Do not remove routers as too old if we do not have any consensus
11116 document. Bugfix on 0.2.0.7-alpha.
11117 - Do not accept incomplete ipv4 addresses (like 192.168.0) as valid.
11118 Spec conformance issue. Bugfix on Tor 0.0.2pre27.
11119 - When an exit relay resolves a stream address to a local IP address,
11120 do not just keep retrying that same exit relay over and
11121 over. Instead, just close the stream. Addresses bug 872. Bugfix
11122 on 0.2.0.32. Patch from rovv.
11123 - If a hidden service sends us an END cell, do not consider
11124 retrying the connection; just close it. Patch from rovv.
11125 - When we made bridge authorities stop serving bridge descriptors over
11126 unencrypted links, we also broke DirPort reachability testing for
11127 bridges. So bridges with a non-zero DirPort were printing spurious
11128 warns to their logs. Bugfix on 0.2.0.16-alpha. Fixes bug 709.
11129 - When a relay gets a create cell it can't decrypt (e.g. because it's
11130 using the wrong onion key), we were dropping it and letting the
11131 client time out. Now actually answer with a destroy cell. Fixes
11132 bug 904. Bugfix on 0.0.2pre8.
11133 - Squeeze 2-5% out of client performance (according to oprofile) by
11134 improving the implementation of some policy-manipulation functions.
11136 o Minor bugfixes (on 0.2.1.x):
11137 - Make get_interface_address() function work properly again; stop
11138 guessing the wrong parts of our address as our address.
11139 - Do not cannibalize a circuit if we're out of RELAY_EARLY cells to
11140 send on that circuit. Otherwise we might violate the proposal-110
11141 limit. Bugfix on 0.2.1.3-alpha. Partial fix for bug 878. Diagnosis
11143 - When we're sending non-EXTEND cells to the first hop in a circuit,
11144 for example to use an encrypted directory connection, we don't need
11145 to use RELAY_EARLY cells: the first hop knows what kind of cell
11146 it is, and nobody else can even see the cell type. Conserving
11147 RELAY_EARLY cells makes it easier to cannibalize circuits like
11149 - Stop logging nameserver addresses in reverse order.
11150 - If we are retrying a directory download slowly over and over, do
11151 not automatically give up after the 254th failure. Bugfix on
11153 - Resume reporting accurate "stream end" reasons to the local control
11154 port. They were lost in the changes for Proposal 148. Bugfix on
11157 o Deprecated and removed features:
11158 - The old "tor --version --version" command, which would print out
11159 the subversion "Id" of most of the source files, is now removed. It
11160 turned out to be less useful than we'd expected, and harder to
11163 o Code simplifications and refactoring:
11164 - Change our header file guard macros to be less likely to conflict
11165 with system headers. Adam Langley noticed that we were conflicting
11166 with log.h on Android.
11167 - Tool-assisted documentation cleanup. Nearly every function or
11168 static variable in Tor should have its own documentation now.
11171 Changes in version 0.2.1.9-alpha - 2008-12-25
11172 Tor 0.2.1.9-alpha fixes many more bugs, some of them security-related.
11174 o New directory authorities:
11175 - gabelmoo (the authority run by Karsten Loesing) now has a new
11179 - Never use a connection with a mismatched address to extend a
11180 circuit, unless that connection is canonical. A canonical
11181 connection is one whose address is authenticated by the router's
11182 identity key, either in a NETINFO cell or in a router descriptor.
11183 - Avoid a possible memory corruption bug when receiving hidden service
11184 descriptors. Bugfix on 0.2.1.6-alpha.
11187 - Fix a logic error that would automatically reject all but the first
11188 configured DNS server. Bugfix on 0.2.1.5-alpha. Possible fix for
11189 part of bug 813/868. Bug spotted by coderman.
11190 - When a stream at an exit relay is in state "resolving" or
11191 "connecting" and it receives an "end" relay cell, the exit relay
11192 would silently ignore the end cell and not close the stream. If
11193 the client never closes the circuit, then the exit relay never
11194 closes the TCP connection. Bug introduced in 0.1.2.1-alpha;
11195 reported by "wood".
11196 - When we can't initialize DNS because the network is down, do not
11197 automatically stop Tor from starting. Instead, retry failed
11198 dns_init() every 10 minutes, and change the exit policy to reject
11199 *:* until one succeeds. Fixes bug 691.
11202 - Give a better error message when an overzealous init script says
11203 "sudo -u username tor --user username". Makes Bug 882 easier for
11205 - When a directory authority gives us a new guess for our IP address,
11206 log which authority we used. Hopefully this will help us debug
11207 the recent complaints about bad IP address guesses.
11208 - Detect svn revision properly when we're using git-svn.
11209 - Try not to open more than one descriptor-downloading connection
11210 to an authority at once. This should reduce load on directory
11211 authorities. Fixes bug 366.
11212 - Add cross-certification to newly generated certificates, so that
11213 a signing key is enough information to look up a certificate.
11214 Partial implementation of proposal 157.
11215 - Start serving certificates by <identity digest, signing key digest>
11216 pairs. Partial implementation of proposal 157.
11217 - Clients now never report any stream end reason except 'MISC'.
11218 Implements proposal 148.
11219 - On platforms with a maximum syslog string length, truncate syslog
11220 messages to that length ourselves, rather than relying on the
11221 system to do it for us.
11222 - Optimize out calls to time(NULL) that occur for every IO operation,
11223 or for every cell. On systems where time() is a slow syscall,
11224 this fix will be slightly helpful.
11225 - Exit servers can now answer resolve requests for ip6.arpa addresses.
11226 - When we download a descriptor that we then immediately (as
11227 a directory authority) reject, do not retry downloading it right
11228 away. Should save some bandwidth on authorities. Fix for bug
11229 888. Patch by Sebastian Hahn.
11230 - When a download gets us zero good descriptors, do not notify
11231 Tor that new directory information has arrived.
11232 - Avoid some nasty corner cases in the logic for marking connections
11233 as too old or obsolete or noncanonical for circuits. Partial
11236 o Minor features (controller):
11237 - New CONSENSUS_ARRIVED event to note when a new consensus has
11238 been fetched and validated.
11239 - When we realize that another process has modified our cached
11240 descriptors file, print out a more useful error message rather
11241 than triggering an assertion. Fixes bug 885. Patch from Karsten.
11242 - Add an internal-use-only __ReloadTorrcOnSIGHUP option for
11243 controllers to prevent SIGHUP from reloading the
11244 configuration. Fixes bug 856.
11247 - Resume using the correct "REASON=" stream when telling the
11248 controller why we closed a stream. Bugfix in 0.2.1.1-alpha.
11249 - When a canonical connection appears later in our internal list
11250 than a noncanonical one for a given OR ID, always use the
11251 canonical one. Bugfix on 0.2.0.12-alpha. Fixes bug 805.
11253 - Clip the MaxCircuitDirtiness config option to a minimum of 10
11254 seconds. Warn the user if lower values are given in the
11255 configuration. Bugfix on 0.1.0.1-rc. Patch by Sebastian.
11256 - Clip the CircuitBuildTimeout to a minimum of 30 seconds. Warn the
11257 user if lower values are given in the configuration. Bugfix on
11258 0.1.1.17-rc. Patch by Sebastian.
11259 - Fix a race condition when freeing keys shared between main thread
11260 and CPU workers that could result in a memory leak. Bugfix on
11261 0.1.0.1-rc. Fixes bug 889.
11263 o Minor bugfixes (hidden services):
11264 - Do not throw away existing introduction points on SIGHUP (bugfix on
11265 0.0.6pre1); also, do not stall hidden services because we're
11266 throwing away introduction points; bugfix on 0.2.1.7-alpha. Spotted
11267 by John Brooks. Patch by Karsten. Fixes bug 874.
11268 - Fix a memory leak when we decline to add a v2 rendezvous
11269 descriptor to the cache because we already had a v0 descriptor
11270 with the same ID. Bugfix on 0.2.0.18-alpha.
11272 o Deprecated and removed features:
11273 - RedirectExits has been removed. It was deprecated since
11275 - Finally remove deprecated "EXTENDED_FORMAT" controller feature. It
11276 has been called EXTENDED_EVENTS since 0.1.2.4-alpha.
11277 - Cell pools are now always enabled; --disable-cell-pools is ignored.
11279 o Code simplifications and refactoring:
11280 - Rename the confusing or_is_obsolete field to the more appropriate
11281 is_bad_for_new_circs, and move it to or_connection_t where it
11283 - Move edge-only flags from connection_t to edge_connection_t: not
11284 only is this better coding, but on machines of plausible alignment,
11285 it should save 4-8 bytes per connection_t. "Every little bit helps."
11286 - Rename ServerDNSAllowBrokenResolvConf to ServerDNSAllowBrokenConfig
11287 for consistency; keep old option working for backward compatibility.
11288 - Simplify the code for finding connections to use for a circuit.
11291 Changes in version 0.2.1.8-alpha - 2008-12-08
11292 Tor 0.2.1.8-alpha fixes some crash bugs in earlier alpha releases,
11293 builds better on unusual platforms like Solaris and old OS X, and
11294 fixes a variety of other issues.
11297 - New DirPortFrontPage option that takes an html file and publishes
11298 it as "/" on the DirPort. Now relay operators can provide a
11299 disclaimer without needing to set up a separate webserver. There's
11300 a sample disclaimer in contrib/tor-exit-notice.html.
11303 - When the client is choosing entry guards, now it selects at most
11304 one guard from a given relay family. Otherwise we could end up with
11305 all of our entry points into the network run by the same operator.
11306 Suggested by Camilo Viecco. Fix on 0.1.1.11-alpha.
11309 - Fix a DOS opportunity during the voting signature collection process
11310 at directory authorities. Spotted by rovv. Bugfix on 0.2.0.x.
11311 - Fix a possible segfault when establishing an exit connection. Bugfix
11315 - Get file locking working on win32. Bugfix on 0.2.1.6-alpha. Fixes
11317 - Made Tor a little less aggressive about deleting expired
11318 certificates. Partial fix for bug 854.
11319 - Stop doing unaligned memory access that generated bus errors on
11320 sparc64. Bugfix on 0.2.0.10-alpha. Fix for bug 862.
11321 - Fix a crash bug when changing EntryNodes from the controller. Bugfix
11322 on 0.2.1.6-alpha. Fix for bug 867. Patched by Sebastian.
11323 - Make USR2 log-level switch take effect immediately. Bugfix on
11325 - If one win32 nameserver fails to get added, continue adding the
11326 rest, and don't automatically fail.
11327 - Use fcntl() for locking when flock() is not available. Should fix
11328 compilation on Solaris. Should fix Bug 873. Bugfix on 0.2.1.6-alpha.
11329 - Do not mark smartlist_bsearch_idx() function as ATTR_PURE. This bug
11330 could make gcc generate non-functional binary search code. Bugfix
11332 - Build correctly on platforms without socklen_t.
11333 - Avoid potential crash on internal error during signature collection.
11334 Fixes bug 864. Patch from rovv.
11335 - Do not use C's stdio library for writing to log files. This will
11336 improve logging performance by a minute amount, and will stop
11337 leaking fds when our disk is full. Fixes bug 861.
11338 - Stop erroneous use of O_APPEND in cases where we did not in fact
11339 want to re-seek to the end of a file before every last write().
11340 - Correct handling of possible malformed authority signing key
11341 certificates with internal signature types. Fixes bug 880. Bugfix
11343 - Fix a hard-to-trigger resource leak when logging credential status.
11347 - Directory mirrors no longer fetch the v1 directory or
11348 running-routers files. They are obsolete, and nobody asks for them
11349 anymore. This is the first step to making v1 authorities obsolete.
11351 o Minor features (controller):
11352 - Return circuit purposes in response to GETINFO circuit-status. Fixes
11356 Changes in version 0.2.0.32 - 2008-11-20
11357 Tor 0.2.0.32 fixes a major security problem in Debian and Ubuntu
11358 packages (and maybe other packages) noticed by Theo de Raadt, fixes
11359 a smaller security flaw that might allow an attacker to access local
11360 services, further improves hidden service performance, and fixes a
11361 variety of other issues.
11364 - The "User" and "Group" config options did not clear the
11365 supplementary group entries for the Tor process. The "User" option
11366 is now more robust, and we now set the groups to the specified
11367 user's primary group. The "Group" option is now ignored. For more
11368 detailed logging on credential switching, set CREDENTIAL_LOG_LEVEL
11369 in common/compat.c to LOG_NOTICE or higher. Patch by Jacob Appelbaum
11370 and Steven Murdoch. Bugfix on 0.0.2pre14. Fixes bug 848 and 857.
11371 - The "ClientDNSRejectInternalAddresses" config option wasn't being
11372 consistently obeyed: if an exit relay refuses a stream because its
11373 exit policy doesn't allow it, we would remember what IP address
11374 the relay said the destination address resolves to, even if it's
11375 an internal IP address. Bugfix on 0.2.0.7-alpha; patch by rovv.
11378 - Fix a DOS opportunity during the voting signature collection process
11379 at directory authorities. Spotted by rovv. Bugfix on 0.2.0.x.
11381 o Major bugfixes (hidden services):
11382 - When fetching v0 and v2 rendezvous service descriptors in parallel,
11383 we were failing the whole hidden service request when the v0
11384 descriptor fetch fails, even if the v2 fetch is still pending and
11385 might succeed. Similarly, if the last v2 fetch fails, we were
11386 failing the whole hidden service request even if a v0 fetch is
11387 still pending. Fixes bug 814. Bugfix on 0.2.0.10-alpha.
11388 - When extending a circuit to a hidden service directory to upload a
11389 rendezvous descriptor using a BEGIN_DIR cell, almost 1/6 of all
11390 requests failed, because the router descriptor has not been
11391 downloaded yet. In these cases, do not attempt to upload the
11392 rendezvous descriptor, but wait until the router descriptor is
11393 downloaded and retry. Likewise, do not attempt to fetch a rendezvous
11394 descriptor from a hidden service directory for which the router
11395 descriptor has not yet been downloaded. Fixes bug 767. Bugfix
11399 - Fix several infrequent memory leaks spotted by Coverity.
11400 - When testing for libevent functions, set the LDFLAGS variable
11401 correctly. Found by Riastradh.
11402 - Avoid a bug where the FastFirstHopPK 0 option would keep Tor from
11403 bootstrapping with tunneled directory connections. Bugfix on
11404 0.1.2.5-alpha. Fixes bug 797. Found by Erwin Lam.
11405 - When asked to connect to A.B.exit:80, if we don't know the IP for A
11406 and we know that server B rejects most-but-not all connections to
11407 port 80, we would previously reject the connection. Now, we assume
11408 the user knows what they were asking for. Fixes bug 752. Bugfix
11409 on 0.0.9rc5. Diagnosed by BarkerJr.
11410 - If we overrun our per-second write limits a little, count this as
11411 having used up our write allocation for the second, and choke
11412 outgoing directory writes. Previously, we had only counted this when
11413 we had met our limits precisely. Fixes bug 824. Patch from by rovv.
11414 Bugfix on 0.2.0.x (??).
11415 - Remove the old v2 directory authority 'lefkada' from the default
11416 list. It has been gone for many months.
11417 - Stop doing unaligned memory access that generated bus errors on
11418 sparc64. Bugfix on 0.2.0.10-alpha. Fixes bug 862.
11419 - Make USR2 log-level switch take effect immediately. Bugfix on
11422 o Minor bugfixes (controller):
11423 - Make DNS resolved events into "CLOSED", not "FAILED". Bugfix on
11424 0.1.2.5-alpha. Fix by Robert Hogan. Resolves bug 807.
11427 Changes in version 0.2.1.7-alpha - 2008-11-08
11428 Tor 0.2.1.7-alpha fixes a major security problem in Debian and Ubuntu
11429 packages (and maybe other packages) noticed by Theo de Raadt, fixes
11430 a smaller security flaw that might allow an attacker to access local
11431 services, adds better defense against DNS poisoning attacks on exit
11432 relays, further improves hidden service performance, and fixes a
11433 variety of other issues.
11436 - The "ClientDNSRejectInternalAddresses" config option wasn't being
11437 consistently obeyed: if an exit relay refuses a stream because its
11438 exit policy doesn't allow it, we would remember what IP address
11439 the relay said the destination address resolves to, even if it's
11440 an internal IP address. Bugfix on 0.2.0.7-alpha; patch by rovv.
11441 - The "User" and "Group" config options did not clear the
11442 supplementary group entries for the Tor process. The "User" option
11443 is now more robust, and we now set the groups to the specified
11444 user's primary group. The "Group" option is now ignored. For more
11445 detailed logging on credential switching, set CREDENTIAL_LOG_LEVEL
11446 in common/compat.c to LOG_NOTICE or higher. Patch by Jacob Appelbaum
11447 and Steven Murdoch. Bugfix on 0.0.2pre14. Fixes bug 848.
11448 - Do not use or believe expired v3 authority certificates. Patch
11449 from Karsten. Bugfix in 0.2.0.x. Fixes bug 851.
11452 - Now NodeFamily and MyFamily config options allow spaces in
11453 identity fingerprints, so it's easier to paste them in.
11454 Suggested by Lucky Green.
11455 - Implement the 0x20 hack to better resist DNS poisoning: set the
11456 case on outgoing DNS requests randomly, and reject responses that do
11457 not match the case correctly. This logic can be disabled with the
11458 ServerDNSRandomizeCase setting, if you are using one of the 0.3%
11459 of servers that do not reliably preserve case in replies. See
11460 "Increased DNS Forgery Resistance through 0x20-Bit Encoding"
11462 - Preserve case in replies to DNSPort requests in order to support
11463 the 0x20 hack for resisting DNS poisoning attacks.
11465 o Hidden service performance improvements:
11466 - When the client launches an introduction circuit, retry with a
11467 new circuit after 30 seconds rather than 60 seconds.
11468 - Launch a second client-side introduction circuit in parallel
11469 after a delay of 15 seconds (based on work by Christian Wilms).
11470 - Hidden services start out building five intro circuits rather
11471 than three, and when the first three finish they publish a service
11472 descriptor using those. Now we publish our service descriptor much
11473 faster after restart.
11476 - Minor fix in the warning messages when you're having problems
11477 bootstrapping; also, be more forgiving of bootstrap problems when
11478 we're still making incremental progress on a given bootstrap phase.
11479 - When we're choosing an exit node for a circuit, and we have
11480 no pending streams, choose a good general exit rather than one that
11481 supports "all the pending streams". Bugfix on 0.1.1.x. Fix by rovv.
11482 - Send a valid END cell back when a client tries to connect to a
11483 nonexistent hidden service port. Bugfix on 0.1.2.15. Fixes bug
11484 840. Patch from rovv.
11485 - If a broken client asks a non-exit router to connect somewhere,
11486 do not even do the DNS lookup before rejecting the connection.
11487 Fixes another case of bug 619. Patch from rovv.
11488 - Fix another case of assuming, when a specific exit is requested,
11489 that we know more than the user about what hosts it allows.
11490 Fixes another case of bug 752. Patch from rovv.
11491 - Check which hops rendezvous stream cells are associated with to
11492 prevent possible guess-the-streamid injection attacks from
11493 intermediate hops. Fixes another case of bug 446. Based on patch
11495 - Avoid using a negative right-shift when comparing 32-bit
11496 addresses. Possible fix for bug 845 and bug 811.
11497 - Make the assert_circuit_ok() function work correctly on circuits that
11498 have already been marked for close.
11499 - Fix read-off-the-end-of-string error in unit tests when decoding
11500 introduction points.
11501 - Fix uninitialized size field for memory area allocation: may improve
11502 memory performance during directory parsing.
11503 - Treat duplicate certificate fetches as failures, so that we do
11504 not try to re-fetch an expired certificate over and over and over.
11505 - Do not say we're fetching a certificate when we'll in fact skip it
11506 because of a pending download.
11509 Changes in version 0.2.1.6-alpha - 2008-09-30
11510 Tor 0.2.1.6-alpha further improves performance and robustness of
11511 hidden services, starts work on supporting per-country relay selection,
11512 and fixes a variety of smaller issues.
11515 - Implement proposal 121: make it possible to build hidden services
11516 that only certain clients are allowed to connect to. This is
11517 enforced at several points, so that unauthorized clients are unable
11518 to send INTRODUCE cells to the service, or even (depending on the
11519 type of authentication) to learn introduction points. This feature
11520 raises the bar for certain kinds of active attacks against hidden
11521 services. Code by Karsten Loesing.
11522 - Relays now store and serve v2 hidden service descriptors by default,
11523 i.e., the new default value for HidServDirectoryV2 is 1. This is
11524 the last step in proposal 114, which aims to make hidden service
11525 lookups more reliable.
11526 - Start work to allow node restrictions to include country codes. The
11527 syntax to exclude nodes in a country with country code XX is
11528 "ExcludeNodes {XX}". Patch from Robert Hogan. It still needs some
11529 refinement to decide what config options should take priority if
11530 you ask to both use a particular node and exclude it.
11531 - Allow ExitNodes list to include IP ranges and country codes, just
11532 like the Exclude*Nodes lists. Patch from Robert Hogan.
11535 - Fix a bug when parsing ports in tor_addr_port_parse() that caused
11536 Tor to fail to start if you had it configured to use a bridge
11537 relay. Fixes bug 809. Bugfix on 0.2.1.5-alpha.
11538 - When extending a circuit to a hidden service directory to upload a
11539 rendezvous descriptor using a BEGIN_DIR cell, almost 1/6 of all
11540 requests failed, because the router descriptor had not been
11541 downloaded yet. In these cases, we now wait until the router
11542 descriptor is downloaded, and then retry. Likewise, clients
11543 now skip over a hidden service directory if they don't yet have
11544 its router descriptor, rather than futilely requesting it and
11545 putting mysterious complaints in the logs. Fixes bug 767. Bugfix
11547 - When fetching v0 and v2 rendezvous service descriptors in parallel,
11548 we were failing the whole hidden service request when the v0
11549 descriptor fetch fails, even if the v2 fetch is still pending and
11550 might succeed. Similarly, if the last v2 fetch fails, we were
11551 failing the whole hidden service request even if a v0 fetch is
11552 still pending. Fixes bug 814. Bugfix on 0.2.0.10-alpha.
11553 - DNS replies need to have names matching their requests, but
11554 these names should be in the questions section, not necessarily
11555 in the answers section. Fixes bug 823. Bugfix on 0.2.1.5-alpha.
11558 - Update to the "September 1 2008" ip-to-country file.
11559 - Allow ports 465 and 587 in the default exit policy again. We had
11560 rejected them in 0.1.0.15, because back in 2005 they were commonly
11561 misconfigured and ended up as spam targets. We hear they are better
11562 locked down these days.
11563 - Use a lockfile to make sure that two Tor processes are not
11564 simultaneously running with the same datadir.
11565 - Serve the latest v3 networkstatus consensus via the control
11566 port. Use "getinfo dir/status-vote/current/consensus" to fetch it.
11567 - Better logging about stability/reliability calculations on directory
11569 - Drop the requirement to have an open dir port for storing and
11570 serving v2 hidden service descriptors.
11571 - Directory authorities now serve a /tor/dbg-stability.txt URL to
11572 help debug WFU and MTBF calculations.
11573 - Implement most of Proposal 152: allow specialized servers to permit
11574 single-hop circuits, and clients to use those servers to build
11575 single-hop circuits when using a specialized controller. Patch
11576 from Josh Albrecht. Resolves feature request 768.
11577 - Add a -p option to tor-resolve for specifying the SOCKS port: some
11578 people find host:port too confusing.
11579 - Make TrackHostExit mappings expire a while after their last use, not
11580 after their creation. Patch from Robert Hogan.
11581 - Provide circuit purposes along with circuit events to the controller.
11584 - Fix compile on OpenBSD 4.4-current. Bugfix on 0.2.1.5-alpha.
11586 - Fixed some memory leaks -- some quite frequent, some almost
11587 impossible to trigger -- based on results from Coverity.
11588 - When testing for libevent functions, set the LDFLAGS variable
11589 correctly. Found by Riastradh.
11590 - Fix an assertion bug in parsing policy-related options; possible fix
11592 - Catch and report a few more bootstrapping failure cases when Tor
11593 fails to establish a TCP connection. Cleanup on 0.2.1.x.
11594 - Avoid a bug where the FastFirstHopPK 0 option would keep Tor from
11595 bootstrapping with tunneled directory connections. Bugfix on
11596 0.1.2.5-alpha. Fixes bug 797. Found by Erwin Lam.
11597 - When asked to connect to A.B.exit:80, if we don't know the IP for A
11598 and we know that server B rejects most-but-not all connections to
11599 port 80, we would previously reject the connection. Now, we assume
11600 the user knows what they were asking for. Fixes bug 752. Bugfix
11601 on 0.0.9rc5. Diagnosed by BarkerJr.
11602 - If we are not using BEGIN_DIR cells, don't attempt to contact hidden
11603 service directories if they have no advertised dir port. Bugfix
11605 - If we overrun our per-second write limits a little, count this as
11606 having used up our write allocation for the second, and choke
11607 outgoing directory writes. Previously, we had only counted this when
11608 we had met our limits precisely. Fixes bug 824. Patch by rovv.
11609 Bugfix on 0.2.0.x (??).
11610 - Avoid a "0 divided by 0" calculation when calculating router uptime
11611 at directory authorities. Bugfix on 0.2.0.8-alpha.
11612 - Make DNS resolved controller events into "CLOSED", not
11613 "FAILED". Bugfix on 0.1.2.5-alpha. Fix by Robert Hogan. Resolves
11615 - Fix a bug where an unreachable relay would establish enough
11616 reachability testing circuits to do a bandwidth test -- if
11617 we already have a connection to the middle hop of the testing
11618 circuit, then it could establish the last hop by using the existing
11619 connection. Bugfix on 0.1.2.2-alpha, exposed when we made testing
11620 circuits no longer use entry guards in 0.2.1.3-alpha.
11621 - If we have correct permissions on $datadir, we complain to stdout
11622 and fail to start. But dangerous permissions on
11623 $datadir/cached-status/ would cause us to open a log and complain
11624 there. Now complain to stdout and fail to start in both cases. Fixes
11625 bug 820, reported by seeess.
11626 - Remove the old v2 directory authority 'lefkada' from the default
11627 list. It has been gone for many months.
11629 o Code simplifications and refactoring:
11630 - Revise the connection_new functions so that a more typesafe variant
11631 exists. This will work better with Coverity, and let us find any
11632 actual mistakes we're making here.
11633 - Refactor unit testing logic so that dmalloc can be used sensibly
11634 with unit tests to check for memory leaks.
11635 - Move all hidden-service related fields from connection and circuit
11636 structure to substructures: this way they won't eat so much memory.
11639 Changes in version 0.2.0.31 - 2008-09-03
11640 Tor 0.2.0.31 addresses two potential anonymity issues, starts to fix
11641 a big bug we're seeing where in rare cases traffic from one Tor stream
11642 gets mixed into another stream, and fixes a variety of smaller issues.
11645 - Make sure that two circuits can never exist on the same connection
11646 with the same circuit ID, even if one is marked for close. This
11647 is conceivably a bugfix for bug 779. Bugfix on 0.1.0.4-rc.
11648 - Relays now reject risky extend cells: if the extend cell includes
11649 a digest of all zeroes, or asks to extend back to the relay that
11650 sent the extend cell, tear down the circuit. Ideas suggested
11652 - If not enough of our entry guards are available so we add a new
11653 one, we might use the new one even if it overlapped with the
11654 current circuit's exit relay (or its family). Anonymity bugfix
11655 pointed out by rovv.
11658 - Recover 3-7 bytes that were wasted per memory chunk. Fixes bug
11659 794; bug spotted by rovv. Bugfix on 0.2.0.1-alpha.
11660 - Correctly detect the presence of the linux/netfilter_ipv4.h header
11661 when building against recent kernels. Bugfix on 0.1.2.1-alpha.
11662 - Pick size of default geoip filename string correctly on windows.
11663 Fixes bug 806. Bugfix on 0.2.0.30.
11664 - Make the autoconf script accept the obsolete --with-ssl-dir
11665 option as an alias for the actually-working --with-openssl-dir
11666 option. Fix the help documentation to recommend --with-openssl-dir.
11667 Based on a patch by "Dave". Bugfix on 0.2.0.1-alpha.
11668 - When using the TransPort option on OpenBSD, and using the User
11669 option to change UID and drop privileges, make sure to open
11670 /dev/pf before dropping privileges. Fixes bug 782. Patch from
11671 Christopher Davis. Bugfix on 0.1.2.1-alpha.
11672 - Try to attach connections immediately upon receiving a RENDEZVOUS2
11673 or RENDEZVOUS_ESTABLISHED cell. This can save a second or two
11674 on the client side when connecting to a hidden service. Bugfix
11675 on 0.0.6pre1. Found and fixed by Christian Wilms; resolves bug 743.
11676 - When closing an application-side connection because its circuit is
11677 getting torn down, generate the stream event correctly. Bugfix on
11678 0.1.2.x. Anonymous patch.
11681 Changes in version 0.2.1.5-alpha - 2008-08-31
11682 Tor 0.2.1.5-alpha moves us closer to handling IPv6 destinations, puts
11683 in a lot of the infrastructure for adding authorization to hidden
11684 services, lays the groundwork for having clients read their load
11685 balancing information out of the networkstatus consensus rather than
11686 the individual router descriptors, addresses two potential anonymity
11687 issues, and fixes a variety of smaller issues.
11690 - Convert many internal address representations to optionally hold
11692 - Generate and accept IPv6 addresses in many protocol elements.
11693 - Make resolver code handle nameservers located at ipv6 addresses.
11694 - Begin implementation of proposal 121 ("Client authorization for
11695 hidden services"): configure hidden services with client
11696 authorization, publish descriptors for them, and configure
11697 authorization data for hidden services at clients. The next
11698 step is to actually access hidden services that perform client
11700 - More progress toward proposal 141: Network status consensus
11701 documents and votes now contain bandwidth information for each
11702 router and a summary of that router's exit policy. Eventually this
11703 will be used by clients so that they do not have to download every
11704 known descriptor before building circuits.
11706 o Major bugfixes (on 0.2.0.x and before):
11707 - When sending CREATED cells back for a given circuit, use a 64-bit
11708 connection ID to find the right connection, rather than an addr:port
11709 combination. Now that we can have multiple OR connections between
11710 the same ORs, it is no longer possible to use addr:port to uniquely
11711 identify a connection.
11712 - Relays now reject risky extend cells: if the extend cell includes
11713 a digest of all zeroes, or asks to extend back to the relay that
11714 sent the extend cell, tear down the circuit. Ideas suggested
11716 - If not enough of our entry guards are available so we add a new
11717 one, we might use the new one even if it overlapped with the
11718 current circuit's exit relay (or its family). Anonymity bugfix
11719 pointed out by rovv.
11722 - Recover 3-7 bytes that were wasted per memory chunk. Fixes bug
11723 794; bug spotted by rovv. Bugfix on 0.2.0.1-alpha.
11724 - When using the TransPort option on OpenBSD, and using the User
11725 option to change UID and drop privileges, make sure to open /dev/pf
11726 before dropping privileges. Fixes bug 782. Patch from Christopher
11727 Davis. Bugfix on 0.1.2.1-alpha.
11728 - Correctly detect the presence of the linux/netfilter_ipv4.h header
11729 when building against recent kernels. Bugfix on 0.1.2.1-alpha.
11730 - Add a missing safe_str() call for a debug log message.
11731 - Use 64 bits instead of 32 bits for connection identifiers used with
11732 the controller protocol, to greatly reduce risk of identifier reuse.
11733 - Make the autoconf script accept the obsolete --with-ssl-dir
11734 option as an alias for the actually-working --with-openssl-dir
11735 option. Fix the help documentation to recommend --with-openssl-dir.
11736 Based on a patch by "Dave". Bugfix on 0.2.0.1-alpha.
11739 - Rate-limit too-many-sockets messages: when they happen, they happen
11740 a lot. Resolves bug 748.
11741 - Resist DNS poisoning a little better by making sure that names in
11742 answer sections match.
11743 - Print the SOCKS5 error message string as well as the error code
11744 when a tor-resolve request fails. Patch from Jacob.
11747 Changes in version 0.2.1.4-alpha - 2008-08-04
11748 Tor 0.2.1.4-alpha fixes a pair of crash bugs in 0.2.1.3-alpha.
11751 - The address part of exit policies was not correctly written
11752 to router descriptors. This generated router descriptors that failed
11753 their self-checks. Noticed by phobos, fixed by Karsten. Bugfix
11755 - Tor triggered a false assert when extending a circuit to a relay
11756 but we already have a connection open to that relay. Noticed by
11757 phobos, fixed by Karsten. Bugfix on 0.2.1.3-alpha.
11760 - Fix a hidden service logging bug: in some edge cases, the router
11761 descriptor of a previously picked introduction point becomes
11762 obsolete and we need to give up on it rather than continually
11763 complaining that it has become obsolete. Observed by xiando. Bugfix
11766 o Removed features:
11767 - Take out the TestVia config option, since it was a workaround for
11768 a bug that was fixed in Tor 0.1.1.21.
11771 Changes in version 0.2.1.3-alpha - 2008-08-03
11772 Tor 0.2.1.3-alpha implements most of the pieces to prevent
11773 infinite-length circuit attacks (see proposal 110); fixes a bug that
11774 might cause exit relays to corrupt streams they send back; allows
11775 address patterns (e.g. 255.128.0.0/16) to appear in ExcludeNodes and
11776 ExcludeExitNodes config options; and fixes a big pile of bugs.
11778 o Bootstrapping bugfixes (on 0.2.1.x-alpha):
11779 - Send a bootstrap problem "warn" event on the first problem if the
11780 reason is NO_ROUTE (that is, our network is down).
11783 - Implement most of proposal 110: The first K cells to be sent
11784 along a circuit are marked as special "early" cells; only K "early"
11785 cells will be allowed. Once this code is universal, we can block
11786 certain kinds of DOS attack by requiring that EXTEND commands must
11787 be sent using an "early" cell.
11790 - Try to attach connections immediately upon receiving a RENDEZVOUS2
11791 or RENDEZVOUS_ESTABLISHED cell. This can save a second or two
11792 on the client side when connecting to a hidden service. Bugfix
11793 on 0.0.6pre1. Found and fixed by Christian Wilms; resolves bug 743.
11794 - Ensure that two circuits can never exist on the same connection
11795 with the same circuit ID, even if one is marked for close. This
11796 is conceivably a bugfix for bug 779; fixes a bug on 0.1.0.4-rc.
11799 - When relays do their initial bandwidth measurement, don't limit
11800 to just our entry guards for the test circuits. Otherwise we tend
11801 to have multiple test circuits going through a single entry guard,
11802 which makes our bandwidth test less accurate. Fixes part of bug 654;
11803 patch contributed by Josh Albrecht.
11804 - Add an ExcludeExitNodes option so users can list a set of nodes
11805 that should be be excluded from the exit node position, but
11806 allowed elsewhere. Implements proposal 151.
11807 - Allow address patterns (e.g., 255.128.0.0/16) to appear in
11808 ExcludeNodes and ExcludeExitNodes lists.
11809 - Change the implementation of ExcludeNodes and ExcludeExitNodes to
11810 be more efficient. Formerly it was quadratic in the number of
11811 servers; now it should be linear. Fixes bug 509.
11812 - Save 16-22 bytes per open circuit by moving the n_addr, n_port,
11813 and n_conn_id_digest fields into a separate structure that's
11814 only needed when the circuit has not yet attached to an n_conn.
11817 - Change the contrib/tor.logrotate script so it makes the new
11818 logs as "_tor:_tor" rather than the default, which is generally
11819 "root:wheel". Fixes bug 676, reported by Serge Koksharov.
11820 - Stop using __attribute__((nonnull)) with GCC: it can give us useful
11821 warnings (occasionally), but it can also cause the compiler to
11822 eliminate error-checking code. Suggested by Peter Gutmann.
11823 - When a hidden service is giving up on an introduction point candidate
11824 that was not included in the last published rendezvous descriptor,
11825 don't reschedule publication of the next descriptor. Fixes bug 763.
11827 - Mark RendNodes, RendExcludeNodes, HiddenServiceNodes, and
11828 HiddenServiceExcludeNodes as obsolete: they never worked properly,
11829 and nobody claims to be using them. Fixes bug 754. Bugfix on
11830 0.1.0.1-rc. Patch from Christian Wilms.
11831 - Fix a small alignment and memory-wasting bug on buffer chunks.
11834 o Minor bugfixes (controller):
11835 - When closing an application-side connection because its circuit
11836 is getting torn down, generate the stream event correctly.
11837 Bugfix on 0.1.2.x. Anonymous patch.
11839 o Removed features:
11840 - Remove all backward-compatibility code to support relays running
11841 versions of Tor so old that they no longer work at all on the
11845 Changes in version 0.2.0.30 - 2008-07-15
11847 - Stop using __attribute__((nonnull)) with GCC: it can give us useful
11848 warnings (occasionally), but it can also cause the compiler to
11849 eliminate error-checking code. Suggested by Peter Gutmann.
11852 Changes in version 0.2.0.29-rc - 2008-07-08
11853 Tor 0.2.0.29-rc fixes two big bugs with using bridges, fixes more
11854 hidden-service performance bugs, and fixes a bunch of smaller bugs.
11857 - If you have more than one bridge but don't know their keys,
11858 you would only launch a request for the descriptor of the first one
11859 on your list. (Tor considered launching requests for the others, but
11860 found that it already had a connection on the way for $0000...0000
11861 so it didn't open another.) Bugfix on 0.2.0.x.
11862 - If you have more than one bridge but don't know their keys, and the
11863 connection to one of the bridges failed, you would cancel all
11864 pending bridge connections. (After all, they all have the same
11865 digest.) Bugfix on 0.2.0.x.
11866 - When a hidden service was trying to establish an introduction point,
11867 and Tor had built circuits preemptively for such purposes, we
11868 were ignoring all the preemptive circuits and launching a new one
11869 instead. Bugfix on 0.2.0.14-alpha.
11870 - When a hidden service was trying to establish an introduction point,
11871 and Tor *did* manage to reuse one of the preemptively built
11872 circuits, it didn't correctly remember which one it used,
11873 so it asked for another one soon after, until there were no
11874 more preemptive circuits, at which point it launched one from
11875 scratch. Bugfix on 0.0.9.x.
11876 - Make directory servers include the X-Your-Address-Is: http header in
11877 their responses even for begin_dir conns. Now clients who only
11878 ever use begin_dir connections still have a way to learn their IP
11879 address. Fixes bug 737; bugfix on 0.2.0.22-rc. Reported by goldy.
11882 - Fix a macro/CPP interaction that was confusing some compilers:
11883 some GCCs don't like #if/#endif pairs inside macro arguments.
11885 - Fix macro collision between OpenSSL 0.9.8h and Windows headers.
11886 Fixes bug 704; fix from Steven Murdoch.
11887 - When opening /dev/null in finish_daemonize(), do not pass the
11888 O_CREAT flag. Fortify was complaining, and correctly so. Fixes
11889 bug 742; fix from Michael Scherer. Bugfix on 0.0.2pre19.
11890 - Correctly detect transparent proxy support on Linux hosts that
11891 require in.h to be included before netfilter_ipv4.h. Patch
11893 - Disallow session resumption attempts during the renegotiation
11894 stage of the v2 handshake protocol. Clients should never be trying
11895 session resumption at this point, but apparently some did, in
11896 ways that caused the handshake to fail. Bugfix on 0.2.0.20-rc. Bug
11897 found by Geoff Goodell.
11900 Changes in version 0.2.1.2-alpha - 2008-06-20
11901 Tor 0.2.1.2-alpha includes a new "TestingTorNetwork" config option to
11902 make it easier to set up your own private Tor network; fixes several
11903 big bugs with using more than one bridge relay; fixes a big bug with
11904 offering hidden services quickly after Tor starts; and uses a better
11905 API for reporting potential bootstrapping problems to the controller.
11908 - New TestingTorNetwork config option to allow adjustment of
11909 previously constant values that, while reasonable, could slow
11910 bootstrapping. Implements proposal 135. Patch from Karsten.
11913 - If you have more than one bridge but don't know their digests,
11914 you would only learn a request for the descriptor of the first one
11915 on your list. (Tor considered launching requests for the others, but
11916 found that it already had a connection on the way for $0000...0000
11917 so it didn't open another.) Bugfix on 0.2.0.x.
11918 - If you have more than one bridge but don't know their digests,
11919 and the connection to one of the bridges failed, you would cancel
11920 all pending bridge connections. (After all, they all have the
11921 same digest.) Bugfix on 0.2.0.x.
11922 - When establishing a hidden service, introduction points that
11923 originate from cannibalized circuits are completely ignored and not
11924 included in rendezvous service descriptors. This might be another
11925 reason for delay in making a hidden service available. Bugfix
11926 from long ago (0.0.9.x?)
11929 - Allow OpenSSL to use dynamic locks if it wants.
11930 - When building a consensus, do not include routers that are down.
11931 This will cut down 30% to 40% on consensus size. Implements
11933 - In directory authorities' approved-routers files, allow
11934 fingerprints with or without space.
11935 - Add a "GETINFO /status/bootstrap-phase" controller option, so the
11936 controller can query our current bootstrap state in case it attaches
11937 partway through and wants to catch up.
11938 - Send an initial "Starting" bootstrap status event, so we have a
11939 state to start out in.
11942 - Asking for a conditional consensus at .../consensus/<fingerprints>
11943 would crash a dirserver if it did not already have a
11944 consensus. Bugfix on 0.2.1.1-alpha.
11945 - Clean up some macro/CPP interactions: some GCC versions don't like
11946 #if/#endif pairs inside macro arguments. Fixes bug 707. Bugfix on
11949 o Bootstrapping bugfixes (on 0.2.1.1-alpha):
11950 - Directory authorities shouldn't complain about bootstrapping
11951 problems just because they do a lot of reachability testing and
11952 some of the connection attempts fail.
11953 - Start sending "count" and "recommendation" key/value pairs in
11954 bootstrap problem status events, so the controller can hear about
11955 problems even before Tor decides they're worth reporting for sure.
11956 - If you're using bridges, generate "bootstrap problem" warnings
11957 as soon as you run out of working bridges, rather than waiting
11958 for ten failures -- which will never happen if you have less than
11960 - If we close our OR connection because there's been a circuit
11961 pending on it for too long, we were telling our bootstrap status
11962 events "REASON=NONE". Now tell them "REASON=TIMEOUT".
11965 Changes in version 0.2.1.1-alpha - 2008-06-13
11966 Tor 0.2.1.1-alpha fixes a lot of memory fragmentation problems that
11967 were making the Tor process bloat especially on Linux; makes our TLS
11968 handshake blend in better; sends "bootstrap phase" status events to
11969 the controller, so it can keep the user informed of progress (and
11970 problems) fetching directory information and establishing circuits;
11971 and adds a variety of smaller features.
11974 - More work on making our TLS handshake blend in: modify the list
11975 of ciphers advertised by OpenSSL in client mode to even more
11976 closely resemble a common web browser. We cheat a little so that
11977 we can advertise ciphers that the locally installed OpenSSL doesn't
11979 - Start sending "bootstrap phase" status events to the controller,
11980 so it can keep the user informed of progress fetching directory
11981 information and establishing circuits. Also inform the controller
11982 if we think we're stuck at a particular bootstrap phase. Implements
11984 - Resume using OpenSSL's RAND_poll() for better (and more portable)
11985 cross-platform entropy collection again. We used to use it, then
11986 stopped using it because of a bug that could crash systems that
11987 called RAND_poll when they had a lot of fds open. It looks like the
11988 bug got fixed in late 2006. Our new behavior is to call RAND_poll()
11989 at startup, and to call RAND_poll() when we reseed later only if
11990 we have a non-buggy OpenSSL version.
11993 - When we choose to abandon a new entry guard because we think our
11994 older ones might be better, close any circuits pending on that
11995 new entry guard connection. This fix should make us recover much
11996 faster when our network is down and then comes back. Bugfix on
11997 0.1.2.8-beta; found by lodger.
11999 o Memory fixes and improvements:
12000 - Add a malloc_good_size implementation to OpenBSD_malloc_linux.c,
12001 to avoid unused RAM in buffer chunks and memory pools.
12002 - Speed up parsing and cut down on memory fragmentation by using
12003 stack-style allocations for parsing directory objects. Previously,
12004 this accounted for over 40% of allocations from within Tor's code
12005 on a typical directory cache.
12006 - Use a Bloom filter rather than a digest-based set to track which
12007 descriptors we need to keep around when we're cleaning out old
12008 router descriptors. This speeds up the computation significantly,
12009 and may reduce fragmentation.
12010 - Reduce the default smartlist size from 32 to 16; it turns out that
12011 most smartlists hold around 8-12 elements tops.
12012 - Make dumpstats() log the fullness and size of openssl-internal
12014 - If the user has applied the experimental SSL_MODE_RELEASE_BUFFERS
12015 patch to their OpenSSL, turn it on to save memory on servers. This
12016 patch will (with any luck) get included in a mainline distribution
12018 - Never use OpenSSL compression: it wastes RAM and CPU trying to
12019 compress cells, which are basically all encrypted, compressed,
12023 - Stop reloading the router list from disk for no reason when we
12024 run out of reachable directory mirrors. Once upon a time reloading
12025 it would set the 'is_running' flag back to 1 for them. It hasn't
12026 done that for a long time.
12027 - In very rare situations new hidden service descriptors were
12028 published earlier than 30 seconds after the last change to the
12029 service. (We currently think that a hidden service descriptor
12030 that's been stable for 30 seconds is worth publishing.)
12033 - Allow separate log levels to be configured for different logging
12034 domains. For example, this allows one to log all notices, warnings,
12035 or errors, plus all memory management messages of level debug or
12036 higher, with: Log [MM] debug-err [*] notice-err file /var/log/tor.
12037 - Add a couple of extra warnings to --enable-gcc-warnings for GCC 4.3,
12038 and stop using a warning that had become unfixably verbose under
12040 - New --hush command-line option similar to --quiet. While --quiet
12041 disables all logging to the console on startup, --hush limits the
12042 output to messages of warning and error severity.
12043 - Servers support a new URL scheme for consensus downloads that
12044 allows the client to specify which authorities are trusted.
12045 The server then only sends the consensus if the client will trust
12046 it. Otherwise a 404 error is sent back. Clients use this
12047 new scheme when the server supports it (meaning it's running
12048 0.2.1.1-alpha or later). Implements proposal 134.
12049 - New configure/torrc options (--enable-geoip-stats,
12050 DirRecordUsageByCountry) to record how many IPs we've served
12051 directory info to in each country code, how many status documents
12052 total we've sent to each country code, and what share of the total
12053 directory requests we should expect to see.
12054 - Use the TLS1 hostname extension to more closely resemble browser
12056 - Lots of new unit tests.
12057 - Add a macro to implement the common pattern of iterating through
12058 two parallel lists in lockstep.
12061 Changes in version 0.2.0.28-rc - 2008-06-13
12062 Tor 0.2.0.28-rc fixes an anonymity-related bug, fixes a hidden-service
12063 performance bug, and fixes a bunch of smaller bugs.
12066 - Fix a bug where, when we were choosing the 'end stream reason' to
12067 put in our relay end cell that we send to the exit relay, Tor
12068 clients on Windows were sometimes sending the wrong 'reason'. The
12069 anonymity problem is that exit relays may be able to guess whether
12070 the client is running Windows, thus helping partition the anonymity
12071 set. Down the road we should stop sending reasons to exit relays,
12072 or otherwise prevent future versions of this bug.
12075 - While setting up a hidden service, some valid introduction circuits
12076 were overlooked and abandoned. This might be the reason for
12077 the long delay in making a hidden service available. Bugfix on
12081 - Update to the "June 9 2008" ip-to-country file.
12082 - Run 'make test' as part of 'make dist', so we stop releasing so
12083 many development snapshots that fail their unit tests.
12086 - When we're checking if we have enough dir info for each relay
12087 to begin establishing circuits, make sure that we actually have
12088 the descriptor listed in the consensus, not just any descriptor.
12090 - Bridge relays no longer print "xx=0" in their extrainfo document
12091 for every single country code in the geoip db. Bugfix on
12093 - Only warn when we fail to load the geoip file if we were planning to
12094 include geoip stats in our extrainfo document. Bugfix on 0.2.0.27-rc.
12095 - If we change our MaxAdvertisedBandwidth and then reload torrc,
12096 Tor won't realize it should publish a new relay descriptor. Fixes
12097 bug 688, reported by mfr. Bugfix on 0.1.2.x.
12098 - When we haven't had any application requests lately, don't bother
12099 logging that we have expired a bunch of descriptors. Bugfix
12101 - Make relay cells written on a connection count as non-padding when
12102 tracking how long a connection has been in use. Bugfix on
12103 0.2.0.1-alpha. Spotted by lodger.
12104 - Fix unit tests in 0.2.0.27-rc.
12105 - Fix compile on Windows.
12108 Changes in version 0.2.0.27-rc - 2008-06-03
12109 Tor 0.2.0.27-rc adds a few features we left out of the earlier
12110 release candidates. In particular, we now include an IP-to-country
12111 GeoIP database, so controllers can easily look up what country a
12112 given relay is in, and so bridge relays can give us some sanitized
12113 summaries about which countries are making use of bridges. (See proposal
12114 126-geoip-fetching.txt for details.)
12117 - Include an IP-to-country GeoIP file in the tarball, so bridge
12118 relays can report sanitized summaries of the usage they're seeing.
12121 - Add a "PURPOSE=" argument to "STREAM NEW" events, as suggested by
12122 Robert Hogan. Fixes the first part of bug 681.
12123 - Make bridge authorities never serve extrainfo docs.
12124 - Add support to detect Libevent versions in the 1.4.x series
12126 - Fix build on gcc 4.3 with --enable-gcc-warnings set.
12127 - Include a new contrib/tor-exit-notice.html file that exit relay
12128 operators can put on their website to help reduce abuse queries.
12131 - When tunneling an encrypted directory connection, and its first
12132 circuit fails, do not leave it unattached and ask the controller
12133 to deal. Fixes the second part of bug 681.
12134 - Make bridge authorities correctly expire old extrainfo documents
12138 Changes in version 0.2.0.26-rc - 2008-05-13
12139 Tor 0.2.0.26-rc fixes a major security vulnerability caused by a bug
12140 in Debian's OpenSSL packages. All users running any 0.2.0.x version
12141 should upgrade, whether they're running Debian or not.
12143 o Major security fixes:
12144 - Use new V3 directory authority keys on the tor26, gabelmoo, and
12145 moria1 V3 directory authorities. The old keys were generated with
12146 a vulnerable version of Debian's OpenSSL package, and must be
12147 considered compromised. Other authorities' keys were not generated
12148 with an affected version of OpenSSL.
12151 - List authority signatures as "unrecognized" based on DirServer
12152 lines, not on cert cache. Bugfix on 0.2.0.x.
12155 - Add a new V3AuthUseLegacyKey option to make it easier for
12156 authorities to change their identity keys if they have to.
12159 Changes in version 0.2.0.25-rc - 2008-04-23
12160 Tor 0.2.0.25-rc makes Tor work again on OS X and certain BSDs.
12163 - Remember to initialize threading before initializing logging.
12164 Otherwise, many BSD-family implementations will crash hard on
12165 startup. Fixes bug 671. Bugfix on 0.2.0.24-rc.
12168 - Authorities correctly free policies on bad servers on
12169 exit. Fixes bug 672. Bugfix on 0.2.0.x.
12172 Changes in version 0.2.0.24-rc - 2008-04-22
12173 Tor 0.2.0.24-rc adds dizum (run by Alex de Joode) as the new sixth
12174 v3 directory authority, makes relays with dynamic IP addresses and no
12175 DirPort notice more quickly when their IP address changes, fixes a few
12176 rare crashes and memory leaks, and fixes a few other miscellaneous bugs.
12178 o New directory authorities:
12179 - Take lefkada out of the list of v3 directory authorities, since
12180 it has been down for months.
12181 - Set up dizum (run by Alex de Joode) as the new sixth v3 directory
12185 - Detect address changes more quickly on non-directory mirror
12186 relays. Bugfix on 0.2.0.18-alpha; fixes bug 652.
12188 o Minor features (security):
12189 - Reject requests for reverse-dns lookup of names that are in
12190 a private address space. Patch from lodger.
12191 - Non-exit relays no longer allow DNS requests. Fixes bug 619. Patch
12194 o Minor bugfixes (crashes):
12195 - Avoid a rare assert that can trigger when Tor doesn't have much
12196 directory information yet and it tries to fetch a v2 hidden
12197 service descriptor. Fixes bug 651, reported by nwf.
12198 - Initialize log mutex before initializing dmalloc. Otherwise,
12199 running with dmalloc would crash. Bugfix on 0.2.0.x-alpha.
12200 - Use recursive pthread mutexes in order to avoid deadlock when
12201 logging debug-level messages to a controller. Bug spotted by nwf,
12202 bugfix on 0.2.0.16-alpha.
12204 o Minor bugfixes (resource management):
12205 - Keep address policies from leaking memory: start their refcount
12206 at 1, not 2. Bugfix on 0.2.0.16-alpha.
12207 - Free authority certificates on exit, so they don't look like memory
12208 leaks. Bugfix on 0.2.0.19-alpha.
12209 - Free static hashtables for policy maps and for TLS connections on
12210 shutdown, so they don't look like memory leaks. Bugfix on 0.2.0.x.
12211 - Avoid allocating extra space when computing consensuses on 64-bit
12212 platforms. Bug spotted by aakova.
12214 o Minor bugfixes (misc):
12215 - Do not read the configuration file when we've only been told to
12216 generate a password hash. Fixes bug 643. Bugfix on 0.0.9pre5. Fix
12217 based on patch from Sebastian Hahn.
12218 - Exit relays that are used as a client can now reach themselves
12219 using the .exit notation, rather than just launching an infinite
12220 pile of circuits. Fixes bug 641. Reported by Sebastian Hahn.
12221 - When attempting to open a logfile fails, tell us why.
12222 - Fix a dumb bug that was preventing us from knowing that we should
12223 preemptively build circuits to handle expected directory requests.
12224 Fixes bug 660. Bugfix on 0.1.2.x.
12225 - Warn less verbosely about clock skew from netinfo cells from
12226 untrusted sources. Fixes bug 663.
12227 - Make controller stream events for DNS requests more consistent,
12228 by adding "new stream" events for DNS requests, and removing
12229 spurious "stream closed" events" for cached reverse resolves.
12230 Patch from mwenge. Fixes bug 646.
12231 - Correctly notify one-hop connections when a circuit build has
12232 failed. Possible fix for bug 669. Found by lodger.
12235 Changes in version 0.2.0.23-rc - 2008-03-24
12236 Tor 0.2.0.23-rc is the fourth release candidate for the 0.2.0 series. It
12237 makes bootstrapping faster if the first directory mirror you contact
12238 is down. The bundles also include the new Vidalia 0.1.2 release.
12241 - When a tunneled directory request is made to a directory server
12242 that's down, notice after 30 seconds rather than 120 seconds. Also,
12243 fail any begindir streams that are pending on it, so they can
12244 retry elsewhere. This was causing multi-minute delays on bootstrap.
12247 Changes in version 0.2.0.22-rc - 2008-03-18
12248 Tor 0.2.0.22-rc is the third release candidate for the 0.2.0 series. It
12249 enables encrypted directory connections by default for non-relays, fixes
12250 some broken TLS behavior we added in 0.2.0.20-rc, and resolves many
12251 other bugs. The bundles also include Vidalia 0.1.1 and Torbutton 1.1.17.
12254 - Enable encrypted directory connections by default for non-relays,
12255 so censor tools that block Tor directory connections based on their
12256 plaintext patterns will no longer work. This means Tor works in
12257 certain censored countries by default again.
12260 - Make sure servers always request certificates from clients during
12261 TLS renegotiation. Reported by lodger; bugfix on 0.2.0.20-rc.
12262 - Do not enter a CPU-eating loop when a connection is closed in
12263 the middle of client-side TLS renegotiation. Fixes bug 622. Bug
12264 diagnosed by lodger; bugfix on 0.2.0.20-rc.
12265 - Fix assertion failure that could occur when a blocked circuit
12266 became unblocked, and it had pending client DNS requests. Bugfix
12267 on 0.2.0.1-alpha. Fixes bug 632.
12269 o Minor bugfixes (on 0.1.2.x):
12270 - Generate "STATUS_SERVER" events rather than misspelled
12271 "STATUS_SEVER" events. Caught by mwenge.
12272 - When counting the number of bytes written on a TLS connection,
12273 look at the BIO actually used for writing to the network, not
12274 at the BIO used (sometimes) to buffer data for the network.
12275 Looking at different BIOs could result in write counts on the
12276 order of ULONG_MAX. Fixes bug 614.
12277 - On Windows, correctly detect errors when listing the contents of
12278 a directory. Fix from lodger.
12280 o Minor bugfixes (on 0.2.0.x):
12281 - Downgrade "sslv3 alert handshake failure" message to INFO.
12282 - If we set RelayBandwidthRate and RelayBandwidthBurst very high but
12283 left BandwidthRate and BandwidthBurst at the default, we would be
12284 silently limited by those defaults. Now raise them to match the
12285 RelayBandwidth* values.
12286 - Fix the SVK version detection logic to work correctly on a branch.
12287 - Make --enable-openbsd-malloc work correctly on Linux with alpha
12288 CPUs. Fixes bug 625.
12289 - Logging functions now check that the passed severity is sane.
12290 - Use proper log levels in the testsuite call of
12291 get_interface_address6().
12292 - When using a nonstandard malloc, do not use the platform values for
12293 HAVE_MALLOC_GOOD_SIZE or HAVE_MALLOC_USABLE_SIZE.
12294 - Make the openbsd malloc code use 8k pages on alpha CPUs and
12296 - Detect mismatched page sizes when using --enable-openbsd-malloc.
12297 - Avoid double-marked-for-close warning when certain kinds of invalid
12298 .in-addr.arpa addresses are passed to the DNSPort. Part of a fix
12299 for bug 617. Bugfix on 0.2.0.1-alpha.
12300 - Make sure that the "NULL-means-reject *:*" convention is followed by
12301 all the policy manipulation functions, avoiding some possible crash
12302 bugs. Bug found by lodger. Bugfix on 0.2.0.16-alpha.
12303 - Fix the implementation of ClientDNSRejectInternalAddresses so that it
12304 actually works, and doesn't warn about every single reverse lookup.
12305 Fixes the other part of bug 617. Bugfix on 0.2.0.1-alpha.
12308 - Only log guard node status when guard node status has changed.
12309 - Downgrade the 3 most common "INFO" messages to "DEBUG". This will
12310 make "INFO" 75% less verbose.
12313 Changes in version 0.2.0.21-rc - 2008-03-02
12314 Tor 0.2.0.21-rc is the second release candidate for the 0.2.0 series. It
12315 makes Tor work well with Vidalia again, fixes a rare assert bug,
12316 and fixes a pair of more minor bugs. The bundles also include Vidalia
12317 0.1.0 and Torbutton 1.1.16.
12320 - The control port should declare that it requires password auth
12321 when HashedControlSessionPassword is set too. Patch from Matt Edman;
12322 bugfix on 0.2.0.20-rc. Fixes bug 615.
12323 - Downgrade assert in connection_buckets_decrement() to a log message.
12324 This may help us solve bug 614, and in any case will make its
12325 symptoms less severe. Bugfix on 0.2.0.20-rc. Reported by fredzupy.
12326 - We were sometimes miscounting the number of bytes read from the
12327 network, causing our rate limiting to not be followed exactly.
12328 Bugfix on 0.2.0.16-alpha. Reported by lodger.
12331 - Fix compilation with OpenSSL 0.9.8 and 0.9.8a. All other supported
12332 OpenSSL versions should have been working fine. Diagnosis and patch
12333 from lodger, Karsten Loesing, and Sebastian Hahn. Fixes bug 616.
12334 Bugfix on 0.2.0.20-rc.
12337 Changes in version 0.2.0.20-rc - 2008-02-24
12338 Tor 0.2.0.20-rc is the first release candidate for the 0.2.0 series. It
12339 makes more progress towards normalizing Tor's TLS handshake, makes
12340 hidden services work better again, helps relays bootstrap if they don't
12341 know their IP address, adds optional support for linking in openbsd's
12342 allocator or tcmalloc, allows really fast relays to scale past 15000
12343 sockets, and fixes a bunch of minor bugs reported by Veracode.
12346 - Enable the revised TLS handshake based on the one designed by
12347 Steven Murdoch in proposal 124, as revised in proposal 130. It
12348 includes version negotiation for OR connections as described in
12349 proposal 105. The new handshake is meant to be harder for censors
12350 to fingerprint, and it adds the ability to detect certain kinds of
12351 man-in-the-middle traffic analysis attacks. The version negotiation
12352 feature will allow us to improve Tor's link protocol more safely
12354 - Choose which bridge to use proportional to its advertised bandwidth,
12355 rather than uniformly at random. This should speed up Tor for
12356 bridge users. Also do this for people who set StrictEntryNodes.
12357 - When a TrackHostExits-chosen exit fails too many times in a row,
12358 stop using it. Bugfix on 0.1.2.x; fixes bug 437.
12361 - Resolved problems with (re-)fetching hidden service descriptors.
12362 Patch from Karsten Loesing; fixes problems with 0.2.0.18-alpha
12363 and 0.2.0.19-alpha.
12364 - If we only ever used Tor for hidden service lookups or posts, we
12365 would stop building circuits and start refusing connections after
12366 24 hours, since we falsely believed that Tor was dormant. Reported
12367 by nwf; bugfix on 0.1.2.x.
12368 - Servers that don't know their own IP address should go to the
12369 authorities for their first directory fetch, even if their DirPort
12370 is off or if they don't know they're reachable yet. This will help
12371 them bootstrap better. Bugfix on 0.2.0.18-alpha; fixes bug 609.
12372 - When counting the number of open sockets, count not only the number
12373 of sockets we have received from the socket() call, but also
12374 the number we've gotten from accept() and socketpair(). This bug
12375 made us fail to count all sockets that we were using for incoming
12376 connections. Bugfix on 0.2.0.x.
12377 - Fix code used to find strings within buffers, when those strings
12378 are not in the first chunk of the buffer. Bugfix on 0.2.0.x.
12379 - Fix potential segfault when parsing HTTP headers. Bugfix on 0.2.0.x.
12380 - Add a new __HashedControlSessionPassword option for controllers
12381 to use for one-off session password hashes that shouldn't get
12382 saved to disk by SAVECONF --- Vidalia users were accumulating a
12383 pile of HashedControlPassword lines in their torrc files, one for
12384 each time they had restarted Tor and then clicked Save. Make Tor
12385 automatically convert "HashedControlPassword" to this new option but
12386 only when it's given on the command line. Partial fix for bug 586.
12388 o Minor features (performance):
12389 - Tune parameters for cell pool allocation to minimize amount of
12391 - Add OpenBSD malloc code from phk as an optional malloc
12392 replacement on Linux: some glibc libraries do very poorly
12393 with Tor's memory allocation patterns. Pass
12394 --enable-openbsd-malloc to get the replacement malloc code.
12395 - Add a --with-tcmalloc option to the configure script to link
12396 against tcmalloc (if present). Does not yet search for
12397 non-system include paths.
12398 - Stop imposing an arbitrary maximum on the number of file descriptors
12399 used for busy servers. Bug reported by Olaf Selke; patch from
12402 o Minor features (other):
12403 - When SafeLogging is disabled, log addresses along with all TLS
12405 - When building with --enable-gcc-warnings, check for whether Apple's
12406 warning "-Wshorten-64-to-32" is available.
12407 - Add a --passphrase-fd argument to the tor-gencert command for
12410 o Minor bugfixes (memory leaks and code problems):
12411 - We were leaking a file descriptor if Tor started with a zero-length
12412 cached-descriptors file. Patch by freddy77; bugfix on 0.1.2.
12413 - Detect size overflow in zlib code. Reported by Justin Ferguson and
12415 - We were comparing the raw BridgePassword entry with a base64'ed
12416 version of it, when handling a "/tor/networkstatus-bridges"
12417 directory request. Now compare correctly. Noticed by Veracode.
12418 - Recover from bad tracked-since value in MTBF-history file.
12419 Should fix bug 537.
12420 - Alter the code that tries to recover from unhandled write
12421 errors, to not try to flush onto a socket that's given us
12422 unhandled errors. Bugfix on 0.1.2.x.
12423 - Make Unix controlsockets work correctly on OpenBSD. Patch from
12424 tup. Bugfix on 0.2.0.3-alpha.
12426 o Minor bugfixes (other):
12427 - If we have an extra-info document for our server, always make
12428 it available on the control port, even if we haven't gotten
12429 a copy of it from an authority yet. Patch from mwenge.
12430 - Log the correct memory chunk sizes for empty RAM chunks in mempool.c.
12431 - Directory mirrors no longer include a guess at the client's IP
12432 address if the connection appears to be coming from the same /24
12433 network; it was producing too many wrong guesses.
12434 - Make the new hidden service code respect the SafeLogging setting.
12435 Bugfix on 0.2.0.x. Patch from Karsten.
12436 - When starting as an authority, do not overwrite all certificates
12437 cached from other authorities. Bugfix on 0.2.0.x. Fixes bug 606.
12438 - If we're trying to flush the last bytes on a connection (for
12439 example, when answering a directory request), reset the
12440 time-to-give-up timeout every time we manage to write something
12441 on the socket. Bugfix on 0.1.2.x.
12442 - Change the behavior of "getinfo status/good-server-descriptor"
12443 so it doesn't return failure when any authority disappears.
12444 - Even though the man page said that "TrackHostExits ." should
12445 work, nobody had ever implemented it. Bugfix on 0.1.0.x.
12446 - Report TLS "zero return" case as a "clean close" and "IO error"
12447 as a "close". Stop calling closes "unexpected closes": existing
12448 Tors don't use SSL_close(), so having a connection close without
12449 the TLS shutdown handshake is hardly unexpected.
12450 - Send NAMESERVER_STATUS messages for a single failed nameserver
12453 o Code simplifications and refactoring:
12454 - Remove the tor_strpartition function: its logic was confused,
12455 and it was only used for one thing that could be implemented far
12459 Changes in version 0.2.0.19-alpha - 2008-02-09
12460 Tor 0.2.0.19-alpha makes more progress towards normalizing Tor's TLS
12461 handshake, makes path selection for relays more secure and IP address
12462 guessing more robust, and generally fixes a lot of bugs in preparation
12463 for calling the 0.2.0 branch stable.
12466 - Do not include recognizeable strings in the commonname part of
12467 Tor's x509 certificates.
12470 - If we're a relay, avoid picking ourselves as an introduction point,
12471 a rendezvous point, or as the final hop for internal circuits. Bug
12472 reported by taranis and lodger. Bugfix on 0.1.2.x.
12473 - Patch from "Andrew S. Lists" to catch when we contact a directory
12474 mirror at IP address X and he says we look like we're coming from
12475 IP address X. Bugfix on 0.1.2.x.
12477 o Minor features (security):
12478 - Be more paranoid about overwriting sensitive memory on free(),
12479 as a defensive programming tactic to ensure forward secrecy.
12481 o Minor features (directory authority):
12482 - Actually validate the options passed to AuthDirReject,
12483 AuthDirInvalid, AuthDirBadDir, and AuthDirBadExit.
12484 - Reject router descriptors with out-of-range bandwidthcapacity or
12485 bandwidthburst values.
12487 o Minor features (controller):
12488 - Reject controller commands over 1MB in length. This keeps rogue
12489 processes from running us out of memory.
12491 o Minor features (misc):
12492 - Give more descriptive well-formedness errors for out-of-range
12493 hidden service descriptor/protocol versions.
12494 - Make memory debugging information describe more about history
12495 of cell allocation, so we can help reduce our memory use.
12497 o Deprecated features (controller):
12498 - The status/version/num-versioning and status/version/num-concurring
12499 GETINFO options are no longer useful in the v3 directory protocol:
12500 treat them as deprecated, and warn when they're used.
12503 - When our consensus networkstatus has been expired for a while, stop
12504 being willing to build circuits using it. Fixes bug 401. Bugfix
12506 - Directory caches now fetch certificates from all authorities
12507 listed in a networkstatus consensus, even when they do not
12508 recognize them. Fixes bug 571. Bugfix on 0.2.0.x.
12509 - When connecting to a bridge without specifying its key, insert
12510 the connection into the identity-to-connection map as soon as
12511 a key is learned. Fixes bug 574. Bugfix on 0.2.0.x.
12512 - Detect versions of OS X where malloc_good_size() is present in the
12513 library but never actually declared. Resolves bug 587. Bugfix
12515 - Stop incorrectly truncating zlib responses to directory authority
12516 signature download requests. Fixes bug 593. Bugfix on 0.2.0.x.
12517 - Stop recommending that every server operator send mail to tor-ops.
12518 Resolves bug 597. Bugfix on 0.1.2.x.
12519 - Don't trigger an assert if we start a directory authority with a
12520 private IP address (like 127.0.0.1).
12521 - Avoid possible failures when generating a directory with routers
12522 with over-long versions strings, or too many flags set. Bugfix
12524 - If an attempt to launch a DNS resolve request over the control
12525 port fails because we have overrun the limit on the number of
12526 connections, tell the controller that the request has failed.
12527 - Avoid using too little bandwidth when our clock skips a few
12528 seconds. Bugfix on 0.1.2.x.
12529 - Fix shell error when warning about missing packages in configure
12530 script, on Fedora or Red Hat machines. Bugfix on 0.2.0.x.
12531 - Do not become confused when receiving a spurious VERSIONS-like
12532 cell from a confused v1 client. Bugfix on 0.2.0.x.
12533 - Re-fetch v2 (as well as v0) rendezvous descriptors when all
12534 introduction points for a hidden service have failed. Patch from
12535 Karsten Loesing. Bugfix on 0.2.0.x.
12537 o Code simplifications and refactoring:
12538 - Remove some needless generality from cpuworker code, for improved
12540 - Stop overloading the circuit_t.onionskin field for both "onionskin
12541 from a CREATE cell that we are waiting for a cpuworker to be
12542 assigned" and "onionskin from an EXTEND cell that we are going to
12543 send to an OR as soon as we are connected". Might help with bug 600.
12544 - Add an in-place version of aes_crypt() so that we can avoid doing a
12545 needless memcpy() call on each cell payload.
12548 Changes in version 0.2.0.18-alpha - 2008-01-25
12549 Tor 0.2.0.18-alpha adds a sixth v3 directory authority run by CCC,
12550 fixes a big memory leak in 0.2.0.17-alpha, and adds new config options
12551 that can warn or reject connections to ports generally associated with
12552 vulnerable-plaintext protocols.
12554 o New directory authorities:
12555 - Set up dannenberg (run by CCC) as the sixth v3 directory
12559 - Fix a major memory leak when attempting to use the v2 TLS
12560 handshake code. Bugfix on 0.2.0.x; fixes bug 589.
12561 - We accidentally enabled the under-development v2 TLS handshake
12562 code, which was causing log entries like "TLS error while
12563 renegotiating handshake". Disable it again. Resolves bug 590.
12564 - We were computing the wrong Content-Length: header for directory
12565 responses that need to be compressed on the fly, causing clients
12566 asking for those items to always fail. Bugfix on 0.2.0.x; partially
12570 - Avoid going directly to the directory authorities even if you're a
12571 relay, if you haven't found yourself reachable yet or if you've
12572 decided not to advertise your dirport yet. Addresses bug 556.
12573 - If we've gone 12 hours since our last bandwidth check, and we
12574 estimate we have less than 50KB bandwidth capacity but we could
12575 handle more, do another bandwidth test.
12576 - New config options WarnPlaintextPorts and RejectPlaintextPorts so
12577 Tor can warn and/or refuse connections to ports commonly used with
12578 vulnerable-plaintext protocols. Currently we warn on ports 23,
12579 109, 110, and 143, but we don't reject any.
12582 - When we setconf ClientOnly to 1, close any current OR and Dir
12583 listeners. Reported by mwenge.
12584 - When we get a consensus that's been signed by more people than
12585 we expect, don't log about it; it's not a big deal. Reported
12589 - Don't answer "/tor/networkstatus-bridges" directory requests if
12590 the request isn't encrypted.
12591 - Make "ClientOnly 1" config option disable directory ports too.
12592 - Patches from Karsten Loesing to make v2 hidden services more
12593 robust: work even when there aren't enough HSDir relays available;
12594 retry when a v2 rend desc fetch fails; but don't retry if we
12595 already have a usable v0 rend desc.
12598 Changes in version 0.2.0.17-alpha - 2008-01-17
12599 Tor 0.2.0.17-alpha makes the tarball build cleanly again (whoops).
12602 - Make the tor-gencert man page get included correctly in the tarball.
12605 Changes in version 0.2.0.16-alpha - 2008-01-17
12606 Tor 0.2.0.16-alpha adds a fifth v3 directory authority run by Karsten
12607 Loesing, and generally cleans up a lot of features and minor bugs.
12609 o New directory authorities:
12610 - Set up gabelmoo (run by Karsten Loesing) as the fifth v3 directory
12613 o Major performance improvements:
12614 - Switch our old ring buffer implementation for one more like that
12615 used by free Unix kernels. The wasted space in a buffer with 1mb
12616 of data will now be more like 8k than 1mb. The new implementation
12617 also avoids realloc();realloc(); patterns that can contribute to
12618 memory fragmentation.
12621 - Configuration files now accept C-style strings as values. This
12622 helps encode characters not allowed in the current configuration
12623 file format, such as newline or #. Addresses bug 557.
12624 - Although we fixed bug 539 (where servers would send HTTP status 503
12625 responses _and_ send a body too), there are still servers out
12626 there that haven't upgraded. Therefore, make clients parse such
12627 bodies when they receive them.
12628 - When we're not serving v2 directory information, there is no reason
12629 to actually keep any around. Remove the obsolete files and directory
12630 on startup if they are very old and we aren't going to serve them.
12632 o Minor performance improvements:
12633 - Reference-count and share copies of address policy entries; only 5%
12634 of them were actually distinct.
12635 - Never walk through the list of logs if we know that no log is
12636 interested in a given message.
12639 - When an authority has not signed a consensus, do not try to
12640 download a nonexistent "certificate with key 00000000". Bugfix
12641 on 0.2.0.x. Fixes bug 569.
12642 - Fix a rare assert error when we're closing one of our threads:
12643 use a mutex to protect the list of logs, so we never write to the
12644 list as it's being freed. Bugfix on 0.1.2.x. Fixes the very rare
12645 bug 575, which is kind of the revenge of bug 222.
12646 - Patch from Karsten Loesing to complain less at both the client
12647 and the relay when a relay used to have the HSDir flag but doesn't
12648 anymore, and we try to upload a hidden service descriptor.
12649 - Stop leaking one cert per TLS context. Fixes bug 582. Bugfix on
12651 - Do not try to download missing certificates until we have tried
12652 to check our fallback consensus. Fixes bug 583.
12653 - Make bridges round reported GeoIP stats info up to the nearest
12654 estimate, not down. Now we can distinguish between "0 people from
12655 this country" and "1 person from this country".
12656 - Avoid a spurious free on base64 failure. Bugfix on 0.1.2.
12657 - Avoid possible segfault if key generation fails in
12658 crypto_pk_hybrid_encrypt. Bugfix on 0.2.0.
12659 - Avoid segfault in the case where a badly behaved v2 versioning
12660 directory sends a signed networkstatus with missing client-versions.
12662 - Avoid segfaults on certain complex invocations of
12663 router_get_by_hexdigest(). Bugfix on 0.1.2.
12664 - Correct bad index on array access in parse_http_time(). Bugfix
12666 - Fix possible bug in vote generation when server versions are present
12667 but client versions are not.
12668 - Fix rare bug on REDIRECTSTREAM control command when called with no
12669 port set: it could erroneously report an error when none had
12671 - Avoid bogus crash-prone, leak-prone tor_realloc when we're
12672 compressing large objects and find ourselves with more than 4k
12673 left over. Bugfix on 0.2.0.
12674 - Fix a small memory leak when setting up a hidden service.
12675 - Fix a few memory leaks that could in theory happen under bizarre
12677 - Fix an assert if we post a general-purpose descriptor via the
12678 control port but that descriptor isn't mentioned in our current
12679 network consensus. Bug reported by Jon McLachlan; bugfix on
12682 o Minor features (controller):
12683 - Get NS events working again. Patch from tup.
12684 - The GETCONF command now escapes and quotes configuration values
12685 that don't otherwise fit into the torrc file.
12686 - The SETCONF command now handles quoted values correctly.
12688 o Minor features (directory authorities):
12689 - New configuration options to override default maximum number of
12690 servers allowed on a single IP address. This is important for
12691 running a test network on a single host.
12692 - Actually implement the -s option to tor-gencert.
12693 - Add a manual page for tor-gencert.
12695 o Minor features (bridges):
12696 - Bridge authorities no longer serve bridge descriptors over
12697 unencrypted connections.
12699 o Minor features (other):
12700 - Add hidden services and DNSPorts to the list of things that make
12701 Tor accept that it has running ports. Change starting Tor with no
12702 ports from a fatal error to a warning; we might change it back if
12703 this turns out to confuse anybody. Fixes bug 579.
12706 Changes in version 0.1.2.19 - 2008-01-17
12707 Tor 0.1.2.19 fixes a huge memory leak on exit relays, makes the default
12708 exit policy a little bit more conservative so it's safer to run an
12709 exit relay on a home system, and fixes a variety of smaller issues.
12712 - Exit policies now reject connections that are addressed to a
12713 relay's public (external) IP address too, unless
12714 ExitPolicyRejectPrivate is turned off. We do this because too
12715 many relays are running nearby to services that trust them based
12716 on network address.
12719 - When the clock jumps forward a lot, do not allow the bandwidth
12720 buckets to become negative. Fixes bug 544.
12721 - Fix a memory leak on exit relays; we were leaking a cached_resolve_t
12722 on every successful resolve. Reported by Mike Perry.
12723 - Purge old entries from the "rephist" database and the hidden
12724 service descriptor database even when DirPort is zero.
12725 - Stop thinking that 0.1.2.x directory servers can handle "begin_dir"
12726 requests. Should ease bugs 406 and 419 where 0.1.2.x relays are
12727 crashing or mis-answering these requests.
12728 - When we decide to send a 503 response to a request for servers, do
12729 not then also send the server descriptors: this defeats the whole
12730 purpose. Fixes bug 539.
12733 - Changing the ExitPolicyRejectPrivate setting should cause us to
12734 rebuild our server descriptor.
12735 - Fix handling of hex nicknames when answering controller requests for
12736 networkstatus by name, or when deciding whether to warn about
12737 unknown routers in a config option. (Patch from mwenge.)
12738 - Fix a couple of hard-to-trigger autoconf problems that could result
12739 in really weird results on platforms whose sys/types.h files define
12740 nonstandard integer types.
12741 - Don't try to create the datadir when running --verify-config or
12742 --hash-password. Resolves bug 540.
12743 - If we were having problems getting a particular descriptor from the
12744 directory caches, and then we learned about a new descriptor for
12745 that router, we weren't resetting our failure count. Reported
12747 - Although we fixed bug 539 (where servers would send HTTP status 503
12748 responses _and_ send a body too), there are still servers out there
12749 that haven't upgraded. Therefore, make clients parse such bodies
12750 when they receive them.
12751 - Run correctly on systems where rlim_t is larger than unsigned long.
12752 This includes some 64-bit systems.
12753 - Run correctly on platforms (like some versions of OS X 10.5) where
12754 the real limit for number of open files is OPEN_FILES, not rlim_max
12755 from getrlimit(RLIMIT_NOFILES).
12756 - Avoid a spurious free on base64 failure.
12757 - Avoid segfaults on certain complex invocations of
12758 router_get_by_hexdigest().
12759 - Fix rare bug on REDIRECTSTREAM control command when called with no
12760 port set: it could erroneously report an error when none had
12764 Changes in version 0.2.0.15-alpha - 2007-12-25
12765 Tor 0.2.0.14-alpha and 0.2.0.15-alpha fix a bunch of bugs with the
12766 features added in 0.2.0.13-alpha.
12769 - Fix several remotely triggerable asserts based on DirPort requests
12770 for a v2 or v3 networkstatus object before we were prepared. This
12771 was particularly bad for 0.2.0.13 and later bridge relays, who
12772 would never have a v2 networkstatus and would thus always crash
12773 when used. Bugfixes on 0.2.0.x.
12774 - Estimate the v3 networkstatus size more accurately, rather than
12775 estimating it at zero bytes and giving it artificially high priority
12776 compared to other directory requests. Bugfix on 0.2.0.x.
12779 - Fix configure.in logic for cross-compilation.
12780 - When we load a bridge descriptor from the cache, and it was
12781 previously unreachable, mark it as retriable so we won't just
12782 ignore it. Also, try fetching a new copy immediately. Bugfixes
12784 - The bridge GeoIP stats were counting other relays, for example
12785 self-reachability and authority-reachability tests.
12788 - Support compilation to target iPhone; patch from cjacker huang.
12789 To build for iPhone, pass the --enable-iphone option to configure.
12792 Changes in version 0.2.0.14-alpha - 2007-12-23
12794 - Fix a crash on startup if you install Tor 0.2.0.13-alpha fresh
12795 without a datadirectory from a previous Tor install. Reported
12797 - Fix a crash when we fetch a descriptor that turns out to be
12798 unexpected (it used to be in our networkstatus when we started
12799 fetching it, but it isn't in our current networkstatus), and we
12800 aren't using bridges. Bugfix on 0.2.0.x.
12801 - Fix a crash when accessing hidden services: it would work the first
12802 time you use a given introduction point for your service, but
12803 on subsequent requests we'd be using garbage memory. Fixed by
12804 Karsten Loesing. Bugfix on 0.2.0.13-alpha.
12805 - Fix a crash when we load a bridge descriptor from disk but we don't
12806 currently have a Bridge line for it in our torrc. Bugfix on
12810 - If bridge authorities set BridgePassword, they will serve a
12811 snapshot of known bridge routerstatuses from their DirPort to
12812 anybody who knows that password. Unset by default.
12815 - Make the unit tests build again.
12816 - Make "GETINFO/desc-annotations/id/<OR digest>" actually work.
12817 - Make PublishServerDescriptor default to 1, so the default doesn't
12818 have to change as we invent new directory protocol versions.
12819 - Fix test for rlim_t on OSX 10.3: sys/resource.h doesn't want to
12820 be included unless sys/time.h is already included. Fixes
12821 bug 553. Bugfix on 0.2.0.x.
12822 - If we receive a general-purpose descriptor and then receive an
12823 identical bridge-purpose descriptor soon after, don't discard
12824 the next one as a duplicate.
12827 - If BridgeRelay is set to 1, then the default for
12828 PublishServerDescriptor is now "bridge" rather than "v2,v3".
12829 - If the user sets RelayBandwidthRate but doesn't set
12830 RelayBandwidthBurst, then make them equal rather than erroring out.
12833 Changes in version 0.2.0.13-alpha - 2007-12-21
12834 Tor 0.2.0.13-alpha adds a fourth v3 directory authority run by Geoff
12835 Goodell, fixes many more bugs, and adds a lot of infrastructure for
12838 o New directory authorities:
12839 - Set up lefkada (run by Geoff Goodell) as the fourth v3 directory
12843 - Only update guard status (usable / not usable) once we have
12844 enough directory information. This was causing us to always pick
12845 two new guards on startup (bugfix on 0.2.0.9-alpha), and it was
12846 causing us to discard all our guards on startup if we hadn't been
12847 running for a few weeks (bugfix on 0.1.2.x). Fixes bug 448.
12848 - Purge old entries from the "rephist" database and the hidden
12849 service descriptor databases even when DirPort is zero. Bugfix
12851 - We were ignoring our RelayBandwidthRate for the first 30 seconds
12852 after opening a circuit -- even a relayed circuit. Bugfix on
12854 - Stop thinking that 0.1.2.x directory servers can handle "begin_dir"
12855 requests. Should ease bugs 406 and 419 where 0.1.2.x relays are
12856 crashing or mis-answering these types of requests.
12857 - Relays were publishing their server descriptor to v1 and v2
12858 directory authorities, but they didn't try publishing to v3-only
12859 authorities. Fix this; and also stop publishing to v1 authorities.
12861 - When we were reading router descriptors from cache, we were ignoring
12862 the annotations -- so for example we were reading in bridge-purpose
12863 descriptors as general-purpose descriptors. Bugfix on 0.2.0.8-alpha.
12864 - When we decided to send a 503 response to a request for servers, we
12865 were then also sending the server descriptors: this defeats the
12866 whole purpose. Fixes bug 539; bugfix on 0.1.2.x.
12869 - Bridge relays now behave like clients with respect to time
12870 intervals for downloading new consensus documents -- otherwise they
12871 stand out. Bridge users now wait until the end of the interval,
12872 so their bridge relay will be sure to have a new consensus document.
12873 - Three new config options (AlternateDirAuthority,
12874 AlternateBridgeAuthority, and AlternateHSAuthority) that let the
12875 user selectively replace the default directory authorities by type,
12876 rather than the all-or-nothing replacement that DirServer offers.
12877 - Tor can now be configured to read a GeoIP file from disk in one
12878 of two formats. This can be used by controllers to map IP addresses
12879 to countries. Eventually, it may support exit-by-country.
12880 - When possible, bridge relays remember which countries users
12881 are coming from, and report aggregate information in their
12882 extra-info documents, so that the bridge authorities can learn
12883 where Tor is blocked.
12884 - Bridge directory authorities now do reachability testing on the
12885 bridges they know. They provide router status summaries to the
12886 controller via "getinfo ns/purpose/bridge", and also dump summaries
12887 to a file periodically.
12888 - Stop fetching directory info so aggressively if your DirPort is
12889 on but your ORPort is off; stop fetching v2 dir info entirely.
12890 You can override these choices with the new FetchDirInfoEarly
12894 - The fix in 0.2.0.12-alpha cleared the "hsdir" flag in v3 network
12895 consensus documents when there are too many relays at a single
12896 IP address. Now clear it in v2 network status documents too, and
12897 also clear it in routerinfo_t when the relay is no longer listed
12898 in the relevant networkstatus document.
12899 - Don't crash if we get an unexpected value for the
12900 PublishServerDescriptor config option. Reported by Matt Edman;
12901 bugfix on 0.2.0.9-alpha.
12902 - Our new v2 hidden service descriptor format allows descriptors
12903 that have no introduction points. But Tor crashed when we tried
12904 to build a descriptor with no intro points (and it would have
12905 crashed if we had tried to parse one). Bugfix on 0.2.0.x; patch
12906 by Karsten Loesing.
12907 - Fix building with dmalloc 5.5.2 with glibc.
12908 - Reject uploaded descriptors and extrainfo documents if they're
12909 huge. Otherwise we'll cache them all over the network and it'll
12910 clog everything up. Reported by Aljosha Judmayer.
12911 - Check for presence of s6_addr16 and s6_addr32 fields in in6_addr
12912 via autoconf. Should fix compile on solaris. Bugfix on 0.2.0.x.
12913 - When the DANGEROUS_VERSION controller status event told us we're
12914 running an obsolete version, it used the string "OLD" to describe
12915 it. Yet the "getinfo" interface used the string "OBSOLETE". Now use
12916 "OBSOLETE" in both cases. Bugfix on 0.1.2.x.
12917 - If we can't expand our list of entry guards (e.g. because we're
12918 using bridges or we have StrictEntryNodes set), don't mark relays
12919 down when they fail a directory request. Otherwise we're too quick
12920 to mark all our entry points down. Bugfix on 0.1.2.x.
12921 - Fix handling of hex nicknames when answering controller requests for
12922 networkstatus by name, or when deciding whether to warn about unknown
12923 routers in a config option. Bugfix on 0.1.2.x. (Patch from mwenge.)
12924 - Fix a couple of hard-to-trigger autoconf problems that could result
12925 in really weird results on platforms whose sys/types.h files define
12926 nonstandard integer types. Bugfix on 0.1.2.x.
12927 - Fix compilation with --disable-threads set. Bugfix on 0.2.0.x.
12928 - Don't crash on name lookup when we have no current consensus. Fixes
12929 bug 538; bugfix on 0.2.0.x.
12930 - Only Tors that want to mirror the v2 directory info should
12931 create the "cached-status" directory in their datadir. (All Tors
12932 used to create it.) Bugfix on 0.2.0.9-alpha.
12933 - Directory authorities should only automatically download Extra Info
12934 documents if they're v1, v2, or v3 authorities. Bugfix on 0.1.2.x.
12937 - On the USR1 signal, when dmalloc is in use, log the top 10 memory
12938 consumers. (We already do this on HUP.)
12939 - Authorities and caches fetch the v2 networkstatus documents
12940 less often, now that v3 is encouraged.
12941 - Add a new config option BridgeRelay that specifies you want to
12942 be a bridge relay. Right now the only difference is that it makes
12943 you answer begin_dir requests, and it makes you cache dir info,
12944 even if your DirPort isn't on.
12945 - Add "GETINFO/desc-annotations/id/<OR digest>" so controllers can
12946 ask about source, timestamp of arrival, purpose, etc. We need
12947 something like this to help Vidalia not do GeoIP lookups on bridge
12949 - Allow multiple HashedControlPassword config lines, to support
12950 multiple controller passwords.
12951 - Authorities now decide whether they're authoritative for a given
12952 router based on the router's purpose.
12953 - New config options AuthDirBadDir and AuthDirListBadDirs for
12954 authorities to mark certain relays as "bad directories" in the
12955 networkstatus documents. Also supports the "!baddir" directive in
12956 the approved-routers file.
12959 Changes in version 0.2.0.12-alpha - 2007-11-16
12960 This twelfth development snapshot fixes some more build problems as
12961 well as a few minor bugs.
12964 - Make it build on OpenBSD again. Patch from tup.
12965 - Substitute BINDIR and LOCALSTATEDIR in scripts. Fixes
12966 package-building for Red Hat, OS X, etc.
12968 o Minor bugfixes (on 0.1.2.x):
12969 - Changing the ExitPolicyRejectPrivate setting should cause us to
12970 rebuild our server descriptor.
12972 o Minor bugfixes (on 0.2.0.x):
12973 - When we're lacking a consensus, don't try to perform rendezvous
12974 operations. Reported by Karsten Loesing.
12975 - Fix a small memory leak whenever we decide against using a
12976 newly picked entry guard. Reported by Mike Perry.
12977 - When authorities detected more than two relays running on the same
12978 IP address, they were clearing all the status flags but forgetting
12979 to clear the "hsdir" flag. So clients were being told that a
12980 given relay was the right choice for a v2 hsdir lookup, yet they
12981 never had its descriptor because it was marked as 'not running'
12983 - If we're trying to fetch a bridge descriptor and there's no way
12984 the bridge authority could help us (for example, we don't know
12985 a digest, or there is no bridge authority), don't be so eager to
12986 fall back to asking the bridge authority.
12987 - If we're using bridges or have strictentrynodes set, and our
12988 chosen exit is in the same family as all our bridges/entry guards,
12989 then be flexible about families.
12992 - When we negotiate a v2 link-layer connection (not yet implemented),
12993 accept RELAY_EARLY cells and turn them into RELAY cells if we've
12994 negotiated a v1 connection for their next step. Initial code for
12998 Changes in version 0.2.0.11-alpha - 2007-11-12
12999 This eleventh development snapshot fixes some build problems with
13000 the previous snapshot. It also includes a more secure-by-default exit
13001 policy for relays, fixes an enormous memory leak for exit relays, and
13002 fixes another bug where servers were falling out of the directory list.
13005 - Exit policies now reject connections that are addressed to a
13006 relay's public (external) IP address too, unless
13007 ExitPolicyRejectPrivate is turned off. We do this because too
13008 many relays are running nearby to services that trust them based
13009 on network address. Bugfix on 0.1.2.x.
13012 - Fix a memory leak on exit relays; we were leaking a cached_resolve_t
13013 on every successful resolve. Reported by Mike Perry; bugfix
13015 - On authorities, never downgrade to old router descriptors simply
13016 because they're listed in the consensus. This created a catch-22
13017 where we wouldn't list a new descriptor because there was an
13018 old one in the consensus, and we couldn't get the new one in the
13019 consensus because we wouldn't list it. Possible fix for bug 548.
13020 Also, this might cause bug 543 to appear on authorities; if so,
13021 we'll need a band-aid for that. Bugfix on 0.2.0.9-alpha.
13023 o Packaging fixes on 0.2.0.10-alpha:
13024 - We were including instructions about what to do with the
13025 src/config/fallback-consensus file, but we weren't actually
13026 including it in the tarball. Disable all of that for now.
13029 - Allow people to say PreferTunnelledDirConns rather than
13030 PreferTunneledDirConns, for those alternate-spellers out there.
13033 - Don't reevaluate all the information from our consensus document
13034 just because we've downloaded a v2 networkstatus that we intend
13035 to cache. Fixes bug 545; bugfix on 0.2.0.x.
13038 Changes in version 0.2.0.10-alpha - 2007-11-10
13039 This tenth development snapshot adds a third v3 directory authority
13040 run by Mike Perry, adds most of Karsten Loesing's new hidden service
13041 descriptor format, fixes a bad crash bug and new bridge bugs introduced
13042 in 0.2.0.9-alpha, fixes many bugs with the v3 directory implementation,
13043 fixes some minor memory leaks in previous 0.2.0.x snapshots, and
13044 addresses many more minor issues.
13046 o New directory authorities:
13047 - Set up ides (run by Mike Perry) as the third v3 directory authority.
13050 - Allow tunnelled directory connections to ask for an encrypted
13051 "begin_dir" connection or an anonymized "uses a full Tor circuit"
13052 connection independently. Now we can make anonymized begin_dir
13053 connections for (e.g.) more secure hidden service posting and
13055 - More progress on proposal 114: code from Karsten Loesing to
13056 implement new hidden service descriptor format.
13057 - Raise the default BandwidthRate/BandwidthBurst to 5MB/10MB, to
13058 accommodate the growing number of servers that use the default
13059 and are reaching it.
13060 - Directory authorities use a new formula for selecting which nodes
13061 to advertise as Guards: they must be in the top 7/8 in terms of
13062 how long we have known about them, and above the median of those
13063 nodes in terms of weighted fractional uptime.
13064 - Make "not enough dir info yet" warnings describe *why* Tor feels
13065 it doesn't have enough directory info yet.
13068 - Stop servers from crashing if they set a Family option (or
13069 maybe in other situations too). Bugfix on 0.2.0.9-alpha; reported
13071 - Make bridge users work again -- the move to v3 directories in
13072 0.2.0.9-alpha had introduced a number of bugs that made bridges
13073 no longer work for clients.
13074 - When the clock jumps forward a lot, do not allow the bandwidth
13075 buckets to become negative. Bugfix on 0.1.2.x; fixes bug 544.
13077 o Major bugfixes (v3 dir, bugfixes on 0.2.0.9-alpha):
13078 - When the consensus lists a router descriptor that we previously were
13079 mirroring, but that we considered non-canonical, reload the
13080 descriptor as canonical. This fixes bug 543 where Tor servers
13081 would start complaining after a few days that they don't have
13082 enough directory information to build a circuit.
13083 - Consider replacing the current consensus when certificates arrive
13084 that make the pending consensus valid. Previously, we were only
13085 considering replacement when the new certs _didn't_ help.
13086 - Fix an assert error on startup if we didn't already have the
13087 consensus and certs cached in our datadirectory: we were caching
13088 the consensus in consensus_waiting_for_certs but then free'ing it
13090 - Avoid sending a request for "keys/fp" (for which we'll get a 400 Bad
13091 Request) if we need more v3 certs but we've already got pending
13092 requests for all of them.
13093 - Correctly back off from failing certificate downloads. Fixes
13095 - Authorities don't vote on the Running flag if they have been running
13096 for less than 30 minutes themselves. Fixes bug 547, where a newly
13097 started authority would vote that everyone was down.
13099 o New requirements:
13100 - Drop support for OpenSSL version 0.9.6. Just about nobody was using
13101 it, it had no AES, and it hasn't seen any security patches since
13105 - Clients now hold circuitless TLS connections open for 1.5 times
13106 MaxCircuitDirtiness (15 minutes), since it is likely that they'll
13107 rebuild a new circuit over them within that timeframe. Previously,
13108 they held them open only for KeepalivePeriod (5 minutes).
13109 - Use "If-Modified-Since" to avoid retrieving consensus
13110 networkstatuses that we already have.
13111 - When we have no consensus, check FallbackNetworkstatusFile (defaults
13112 to $PREFIX/share/tor/fallback-consensus) for a consensus. This way
13113 we start knowing some directory caches.
13114 - When we receive a consensus from the future, warn about skew.
13115 - Improve skew reporting: try to give the user a better log message
13116 about how skewed they are, and how much this matters.
13117 - When we have a certificate for an authority, believe that
13118 certificate's claims about the authority's IP address.
13119 - New --quiet command-line option to suppress the default console log.
13120 Good in combination with --hash-password.
13121 - Authorities send back an X-Descriptor-Not-New header in response to
13122 an accepted-but-discarded descriptor upload. Partially implements
13124 - Make the log message for "tls error. breaking." more useful.
13125 - Better log messages about certificate downloads, to attempt to
13126 track down the second incarnation of bug 546.
13128 o Minor features (bridges):
13129 - If bridge users set UpdateBridgesFromAuthority, but the digest
13130 they ask for is a 404 from the bridge authority, they now fall
13131 back to trying the bridge directly.
13132 - Bridges now use begin_dir to publish their server descriptor to
13133 the bridge authority, even when they haven't set TunnelDirConns.
13135 o Minor features (controller):
13136 - When reporting clock skew, and we know that the clock is _at least
13137 as skewed_ as some value, but we don't know the actual value,
13138 report the value as a "minimum skew."
13141 - Update linux-tor-prio.sh script to allow QoS based on the uid of
13142 the Tor process. Patch from Marco Bonetti with tweaks from Mike
13146 - Refuse to start if both ORPort and UseBridges are set. Bugfix
13147 on 0.2.0.x, suggested by Matt Edman.
13148 - Don't stop fetching descriptors when FetchUselessDescriptors is
13149 set, even if we stop asking for circuits. Bugfix on 0.1.2.x;
13150 reported by tup and ioerror.
13151 - Better log message on vote from unknown authority.
13152 - Don't log "Launching 0 request for 0 router" message.
13154 o Minor bugfixes (memory leaks):
13155 - Stop leaking memory every time we parse a v3 certificate. Bugfix
13157 - Stop leaking memory every time we load a v3 certificate. Bugfix
13158 on 0.2.0.1-alpha. Fixes bug 536.
13159 - Stop leaking a cached networkstatus on exit. Bugfix on
13161 - Stop leaking voter information every time we free a consensus.
13162 Bugfix on 0.2.0.3-alpha.
13163 - Stop leaking signed data every time we check a voter signature.
13164 Bugfix on 0.2.0.3-alpha.
13165 - Stop leaking a signature every time we fail to parse a consensus or
13166 a vote. Bugfix on 0.2.0.3-alpha.
13167 - Stop leaking v2_download_status_map on shutdown. Bugfix on
13169 - Stop leaking conn->nickname every time we make a connection to a
13170 Tor relay without knowing its expected identity digest (e.g. when
13171 using bridges). Bugfix on 0.2.0.3-alpha.
13173 - Minor bugfixes (portability):
13174 - Run correctly on platforms where rlim_t is larger than unsigned
13175 long, and/or where the real limit for number of open files is
13176 OPEN_FILES, not rlim_max from getrlimit(RLIMIT_NOFILES). In
13177 particular, these may be needed for OS X 10.5.
13180 Changes in version 0.1.2.18 - 2007-10-28
13181 Tor 0.1.2.18 fixes many problems including crash bugs, problems with
13182 hidden service introduction that were causing huge delays, and a big
13183 bug that was causing some servers to disappear from the network status
13184 lists for a few hours each day.
13186 o Major bugfixes (crashes):
13187 - If a connection is shut down abruptly because of something that
13188 happened inside connection_flushed_some(), do not call
13189 connection_finished_flushing(). Should fix bug 451:
13190 "connection_stop_writing: Assertion conn->write_event failed"
13191 Bugfix on 0.1.2.7-alpha.
13192 - Fix possible segfaults in functions called from
13193 rend_process_relay_cell().
13195 o Major bugfixes (hidden services):
13196 - Hidden services were choosing introduction points uniquely by
13197 hexdigest, but when constructing the hidden service descriptor
13198 they merely wrote the (potentially ambiguous) nickname.
13199 - Clients now use the v2 intro format for hidden service
13200 connections: they specify their chosen rendezvous point by identity
13201 digest rather than by (potentially ambiguous) nickname. These
13202 changes could speed up hidden service connections dramatically.
13204 o Major bugfixes (other):
13205 - Stop publishing a new server descriptor just because we get a
13206 HUP signal. This led (in a roundabout way) to some servers getting
13207 dropped from the networkstatus lists for a few hours each day.
13208 - When looking for a circuit to cannibalize, consider family as well
13209 as identity. Fixes bug 438. Bugfix on 0.1.0.x (which introduced
13210 circuit cannibalization).
13211 - When a router wasn't listed in a new networkstatus, we were leaving
13212 the flags for that router alone -- meaning it remained Named,
13213 Running, etc -- even though absence from the networkstatus means
13214 that it shouldn't be considered to exist at all anymore. Now we
13215 clear all the flags for routers that fall out of the networkstatus
13216 consensus. Fixes bug 529.
13219 - Don't try to access (or alter) the state file when running
13220 --list-fingerprint or --verify-config or --hash-password. Resolves
13222 - When generating information telling us how to extend to a given
13223 router, do not try to include the nickname if it is
13224 absent. Resolves bug 467.
13225 - Fix a user-triggerable segfault in expand_filename(). (There isn't
13226 a way to trigger this remotely.)
13227 - When sending a status event to the controller telling it that an
13228 OR address is reachable, set the port correctly. (Previously we
13229 were reporting the dir port.)
13230 - Fix a minor memory leak whenever a controller sends the PROTOCOLINFO
13231 command. Bugfix on 0.1.2.17.
13232 - When loading bandwidth history, do not believe any information in
13233 the future. Fixes bug 434.
13234 - When loading entry guard information, do not believe any information
13236 - When we have our clock set far in the future and generate an
13237 onion key, then re-set our clock to be correct, we should not stop
13238 the onion key from getting rotated.
13239 - On some platforms, accept() can return a broken address. Detect
13240 this more quietly, and deal accordingly. Fixes bug 483.
13241 - It's not actually an error to find a non-pending entry in the DNS
13242 cache when canceling a pending resolve. Don't log unless stuff
13243 is fishy. Resolves bug 463.
13244 - Don't reset trusted dir server list when we set a configuration
13245 option. Patch from Robert Hogan.
13246 - Don't try to create the datadir when running --verify-config or
13247 --hash-password. Resolves bug 540.
13250 Changes in version 0.2.0.9-alpha - 2007-10-24
13251 This ninth development snapshot switches clients to the new v3 directory
13252 system; allows servers to be listed in the network status even when they
13253 have the same nickname as a registered server; and fixes many other
13254 bugs including a big one that was causing some servers to disappear
13255 from the network status lists for a few hours each day.
13257 o Major features (directory system):
13258 - Clients now download v3 consensus networkstatus documents instead
13259 of v2 networkstatus documents. Clients and caches now base their
13260 opinions about routers on these consensus documents. Clients only
13261 download router descriptors listed in the consensus.
13262 - Authorities now list servers who have the same nickname as
13263 a different named server, but list them with a new flag,
13264 "Unnamed". Now we can list servers that happen to pick the same
13265 nickname as a server that registered two years ago and then
13266 disappeared. Partially implements proposal 122.
13267 - If the consensus lists a router as "Unnamed", the name is assigned
13268 to a different router: do not identify the router by that name.
13269 Partially implements proposal 122.
13270 - Authorities can now come to a consensus on which method to use to
13271 compute the consensus. This gives us forward compatibility.
13274 - Stop publishing a new server descriptor just because we HUP or
13275 when we find our DirPort to be reachable but won't actually publish
13276 it. New descriptors without any real changes are dropped by the
13277 authorities, and can screw up our "publish every 18 hours" schedule.
13279 - When a router wasn't listed in a new networkstatus, we were leaving
13280 the flags for that router alone -- meaning it remained Named,
13281 Running, etc -- even though absence from the networkstatus means
13282 that it shouldn't be considered to exist at all anymore. Now we
13283 clear all the flags for routers that fall out of the networkstatus
13284 consensus. Fixes bug 529; bugfix on 0.1.2.x.
13285 - Fix awful behavior in DownloadExtraInfo option where we'd fetch
13286 extrainfo documents and then discard them immediately for not
13287 matching the latest router. Bugfix on 0.2.0.1-alpha.
13289 o Minor features (v3 directory protocol):
13290 - Allow tor-gencert to generate a new certificate without replacing
13292 - Allow certificates to include an address.
13293 - When we change our directory-cache settings, reschedule all voting
13294 and download operations.
13295 - Reattempt certificate downloads immediately on failure, as long as
13296 we haven't failed a threshold number of times yet.
13297 - Delay retrying consensus downloads while we're downloading
13298 certificates to verify the one we just got. Also, count getting a
13299 consensus that we already have (or one that isn't valid) as a failure,
13300 and count failing to get the certificates after 20 minutes as a
13302 - Build circuits and download descriptors even if our consensus is a
13303 little expired. (This feature will go away once authorities are
13306 o Minor features (router descriptor cache):
13307 - If we find a cached-routers file that's been sitting around for more
13308 than 28 days unmodified, then most likely it's a leftover from
13309 when we upgraded to 0.2.0.8-alpha. Remove it. It has no good
13311 - When we (as a cache) download a descriptor because it was listed
13312 in a consensus, remember when the consensus was supposed to expire,
13313 and don't expire the descriptor until then.
13315 o Minor features (performance):
13316 - Call routerlist_remove_old_routers() much less often. This should
13317 speed startup, especially on directory caches.
13318 - Don't try to launch new descriptor downloads quite so often when we
13319 already have enough directory information to build circuits.
13320 - Base64 decoding was actually showing up on our profile when parsing
13321 the initial descriptor file; switch to an in-process all-at-once
13322 implementation that's about 3.5x times faster than calling out to
13325 o Minor features (compilation):
13326 - Detect non-ASCII platforms (if any still exist) and refuse to
13327 build there: some of our code assumes that 'A' is 65 and so on.
13329 o Minor bugfixes (v3 directory authorities, bugfixes on 0.2.0.x):
13330 - Make the "next period" votes into "current period" votes immediately
13331 after publishing the consensus; avoid a heisenbug that made them
13332 stick around indefinitely.
13333 - When we discard a vote as a duplicate, do not report this as
13335 - Treat missing v3 keys or certificates as an error when running as a
13336 v3 directory authority.
13337 - When we're configured to be a v3 authority, but we're only listed
13338 as a non-v3 authority in our DirServer line for ourself, correct
13340 - If an authority doesn't have a qualified hostname, just put
13341 its address in the vote. This fixes the problem where we referred to
13342 "moria on moria:9031."
13343 - Distinguish between detached signatures for the wrong period, and
13344 detached signatures for a divergent vote.
13345 - Fix a small memory leak when computing a consensus.
13346 - When there's no concensus, we were forming a vote every 30
13347 minutes, but writing the "valid-after" line in our vote based
13348 on our configured V3AuthVotingInterval: so unless the intervals
13349 matched up, we immediately rejected our own vote because it didn't
13350 start at the voting interval that caused us to construct a vote.
13352 o Minor bugfixes (v3 directory protocol, bugfixes on 0.2.0.x):
13353 - Delete unverified-consensus when the real consensus is set.
13354 - Consider retrying a consensus networkstatus fetch immediately
13355 after one fails: don't wait 60 seconds to notice.
13356 - When fetching a consensus as a cache, wait until a newer consensus
13357 should exist before trying to replace the current one.
13358 - Use a more forgiving schedule for retrying failed consensus
13359 downloads than for other types.
13361 o Minor bugfixes (other directory issues):
13362 - Correct the implementation of "download votes by digest." Bugfix on
13364 - Authorities no longer send back "400 you're unreachable please fix
13365 it" errors to Tor servers that aren't online all the time. We're
13366 supposed to tolerate these servers now. Bugfix on 0.1.2.x.
13368 o Minor bugfixes (controller):
13369 - Don't reset trusted dir server list when we set a configuration
13370 option. Patch from Robert Hogan; bugfix on 0.1.2.x.
13371 - Respond to INT and TERM SIGNAL commands before we execute the
13372 signal, in case the signal shuts us down. We had a patch in
13373 0.1.2.1-alpha that tried to do this by queueing the response on
13374 the connection's buffer before shutting down, but that really
13375 isn't the same thing at all. Bug located by Matt Edman.
13377 o Minor bugfixes (misc):
13378 - Correctly check for bad options to the "PublishServerDescriptor"
13379 config option. Bugfix on 0.2.0.1-alpha; reported by Matt Edman.
13380 - Stop leaking memory on failing case of base32_decode, and make
13381 it accept upper-case letters. Bugfixes on 0.2.0.7-alpha.
13382 - Don't try to download extrainfo documents when we're trying to
13383 fetch enough directory info to build a circuit: having enough
13384 info should get priority. Bugfix on 0.2.0.x.
13385 - Don't complain that "your server has not managed to confirm that its
13386 ports are reachable" if we haven't been able to build any circuits
13387 yet. Bug found by spending four hours without a v3 consensus. Bugfix
13389 - Detect the reason for failing to mmap a descriptor file we just
13390 wrote, and give a more useful log message. Fixes bug 533. Bugfix
13393 o Code simplifications and refactoring:
13394 - Remove support for the old bw_accounting file: we've been storing
13395 bandwidth accounting information in the state file since
13396 0.1.2.5-alpha. This may result in bandwidth accounting errors
13397 if you try to upgrade from 0.1.1.x or earlier, or if you try to
13398 downgrade to 0.1.1.x or earlier.
13399 - New convenience code to locate a file within the DataDirectory.
13400 - Move non-authority functionality out of dirvote.c.
13401 - Refactor the arguments for router_pick_{directory_|trusteddir}server
13402 so that they all take the same named flags.
13405 - Include the "tor-ctrl.sh" bash script by Stefan Behte to provide
13406 Unix users an easy way to script their Tor process (e.g. by
13407 adjusting bandwidth based on the time of the day).
13410 Changes in version 0.2.0.8-alpha - 2007-10-12
13411 This eighth development snapshot fixes a crash bug that's been bothering
13412 us since February 2007, lets bridge authorities store a list of bridge
13413 descriptors they've seen, gets v3 directory voting closer to working,
13414 starts caching v3 directory consensus documents on directory mirrors,
13415 and fixes a variety of smaller issues including some minor memory leaks.
13417 o Major features (router descriptor cache):
13418 - Store routers in a file called cached-descriptors instead of in
13419 cached-routers. Initialize cached-descriptors from cached-routers
13420 if the old format is around. The new format allows us to store
13421 annotations along with descriptors.
13422 - Use annotations to record the time we received each descriptor, its
13423 source, and its purpose.
13424 - Disable the SETROUTERPURPOSE controller command: it is now
13426 - Controllers should now specify cache=no or cache=yes when using
13427 the +POSTDESCRIPTOR command.
13428 - Bridge authorities now write bridge descriptors to disk, meaning
13429 we can export them to other programs and begin distributing them
13432 o Major features (directory authorities):
13433 - When a v3 authority is missing votes or signatures, it now tries
13435 - Directory authorities track weighted fractional uptime as well as
13436 weighted mean-time-between failures. WFU is suitable for deciding
13437 whether a node is "usually up", while MTBF is suitable for deciding
13438 whether a node is "likely to stay up." We need both, because
13439 "usually up" is a good requirement for guards, while "likely to
13440 stay up" is a good requirement for long-lived connections.
13442 o Major features (v3 directory system):
13443 - Caches now download v3 network status documents as needed,
13444 and download the descriptors listed in them.
13445 - All hosts now attempt to download and keep fresh v3 authority
13446 certificates, and re-attempt after failures.
13447 - More internal-consistency checks for vote parsing.
13449 o Major bugfixes (crashes):
13450 - If a connection is shut down abruptly because of something that
13451 happened inside connection_flushed_some(), do not call
13452 connection_finished_flushing(). Should fix bug 451. Bugfix on
13455 o Major bugfixes (performance):
13456 - Fix really bad O(n^2) performance when parsing a long list of
13457 routers: Instead of searching the entire list for an "extra-info "
13458 string which usually wasn't there, once for every routerinfo
13459 we read, just scan lines forward until we find one we like.
13461 - When we add data to a write buffer in response to the data on that
13462 write buffer getting low because of a flush, do not consider the
13463 newly added data as a candidate for immediate flushing, but rather
13464 make it wait until the next round of writing. Otherwise, we flush
13465 and refill recursively, and a single greedy TLS connection can
13466 eat all of our bandwidth. Bugfix on 0.1.2.7-alpha.
13468 o Minor features (v3 authority system):
13469 - Add more ways for tools to download the votes that lead to the
13471 - Send a 503 when low on bandwidth and a vote, consensus, or
13472 certificate is requested.
13473 - If-modified-since is now implemented properly for all kinds of
13474 certificate requests.
13476 o Minor bugfixes (network statuses):
13477 - Tweak the implementation of proposal 109 slightly: allow at most
13478 two Tor servers on the same IP address, except if it's the location
13479 of a directory authority, in which case allow five. Bugfix on
13482 o Minor bugfixes (controller):
13483 - When sending a status event to the controller telling it that an
13484 OR address is reachable, set the port correctly. (Previously we
13485 were reporting the dir port.) Bugfix on 0.1.2.x.
13487 o Minor bugfixes (v3 directory system):
13488 - Fix logic to look up a cert by its signing key digest. Bugfix on
13490 - Only change the reply to a vote to "OK" if it's not already
13491 set. This gets rid of annoying "400 OK" log messages, which may
13492 have been masking some deeper issue. Bugfix on 0.2.0.7-alpha.
13493 - When we get a valid consensus, recompute the voting schedule.
13494 - Base the valid-after time of a vote on the consensus voting
13495 schedule, not on our preferred schedule.
13496 - Make the return values and messages from signature uploads and
13497 downloads more sensible.
13498 - Fix a memory leak when serving votes and consensus documents, and
13499 another when serving certificates.
13501 o Minor bugfixes (performance):
13502 - Use a slightly simpler string hashing algorithm (copying Python's
13503 instead of Java's) and optimize our digest hashing algorithm to take
13504 advantage of 64-bit platforms and to remove some possibly-costly
13506 - Fix a minor memory leak whenever we parse guards from our state
13507 file. Bugfix on 0.2.0.7-alpha.
13508 - Fix a minor memory leak whenever we write out a file. Bugfix on
13510 - Fix a minor memory leak whenever a controller sends the PROTOCOLINFO
13511 command. Bugfix on 0.2.0.5-alpha.
13513 o Minor bugfixes (portability):
13514 - On some platforms, accept() can return a broken address. Detect
13515 this more quietly, and deal accordingly. Fixes bug 483.
13516 - Stop calling tor_strlower() on uninitialized memory in some cases.
13517 Bugfix in 0.2.0.7-alpha.
13519 o Minor bugfixes (usability):
13520 - Treat some 403 responses from directory servers as INFO rather than
13521 WARN-severity events.
13522 - It's not actually an error to find a non-pending entry in the DNS
13523 cache when canceling a pending resolve. Don't log unless stuff is
13524 fishy. Resolves bug 463.
13526 o Minor bugfixes (anonymity):
13527 - Never report that we've used more bandwidth than we're willing to
13528 relay: it leaks how much non-relay traffic we're using. Resolves
13530 - When looking for a circuit to cannibalize, consider family as well
13531 as identity. Fixes bug 438. Bugfix on 0.1.0.x (which introduced
13532 circuit cannibalization).
13534 o Code simplifications and refactoring:
13535 - Make a bunch of functions static. Remove some dead code.
13536 - Pull out about a third of the really big routerlist.c; put it in a
13537 new module, networkstatus.c.
13538 - Merge the extra fields in local_routerstatus_t back into
13539 routerstatus_t: we used to need one routerstatus_t for each
13540 authority's opinion, plus a local_routerstatus_t for the locally
13541 computed consensus opinion. To save space, we put the locally
13542 modified fields into local_routerstatus_t, and only the common
13543 stuff into routerstatus_t. But once v3 directories are in use,
13544 clients and caches will no longer need to hold authority opinions;
13545 thus, the rationale for keeping the types separate is now gone.
13546 - Make the code used to reschedule and reattempt downloads more
13548 - Turn all 'Are we a directory server/mirror?' logic into a call to
13550 - Remove the code to generate the oldest (v1) directory format.
13551 The code has been disabled since 0.2.0.5-alpha.
13554 Changes in version 0.2.0.7-alpha - 2007-09-21
13555 This seventh development snapshot makes bridges work again, makes bridge
13556 authorities work for the first time, fixes two huge performance flaws
13557 in hidden services, and fixes a variety of minor issues.
13559 o New directory authorities:
13560 - Set up moria1 and tor26 as the first v3 directory authorities. See
13561 doc/spec/dir-spec.txt for details on the new directory design.
13563 o Major bugfixes (crashes):
13564 - Fix possible segfaults in functions called from
13565 rend_process_relay_cell(). Bugfix on 0.1.2.x.
13567 o Major bugfixes (bridges):
13568 - Fix a bug that made servers send a "404 Not found" in response to
13569 attempts to fetch their server descriptor. This caused Tor servers
13570 to take many minutes to establish reachability for their DirPort,
13571 and it totally crippled bridges. Bugfix on 0.2.0.5-alpha.
13572 - Make "UpdateBridgesFromAuthority" torrc option work: when bridge
13573 users configure that and specify a bridge with an identity
13574 fingerprint, now they will lookup the bridge descriptor at the
13575 default bridge authority via a one-hop tunnel, but once circuits
13576 are established they will switch to a three-hop tunnel for later
13577 connections to the bridge authority. Bugfix in 0.2.0.3-alpha.
13579 o Major bugfixes (hidden services):
13580 - Hidden services were choosing introduction points uniquely by
13581 hexdigest, but when constructing the hidden service descriptor
13582 they merely wrote the (potentially ambiguous) nickname.
13583 - Clients now use the v2 intro format for hidden service
13584 connections: they specify their chosen rendezvous point by identity
13585 digest rather than by (potentially ambiguous) nickname. Both
13586 are bugfixes on 0.1.2.x, and they could speed up hidden service
13587 connections dramatically. Thanks to Karsten Loesing.
13589 o Minor features (security):
13590 - As a client, do not believe any server that tells us that an
13591 address maps to an internal address space.
13592 - Make it possible to enable HashedControlPassword and
13593 CookieAuthentication at the same time.
13595 o Minor features (guard nodes):
13596 - Tag every guard node in our state file with the version that
13597 we believe added it, or with our own version if we add it. This way,
13598 if a user temporarily runs an old version of Tor and then switches
13599 back to a new one, she doesn't automatically lose her guards.
13601 o Minor features (speed):
13602 - When implementing AES counter mode, update only the portions of the
13603 counter buffer that need to change, and don't keep separate
13604 network-order and host-order counters when they are the same (i.e.,
13605 on big-endian hosts.)
13607 o Minor features (controller):
13608 - Accept LF instead of CRLF on controller, since some software has a
13609 hard time generating real Internet newlines.
13610 - Add GETINFO values for the server status events
13611 "REACHABILITY_SUCCEEDED" and "GOOD_SERVER_DESCRIPTOR". Patch from
13614 o Removed features:
13615 - Routers no longer include bandwidth-history lines in their
13616 descriptors; this information is already available in extra-info
13617 documents, and including it in router descriptors took up 60%
13618 (!) of compressed router descriptor downloads. Completes
13619 implementation of proposal 104.
13620 - Remove the contrib scripts ExerciseServer.py, PathDemo.py,
13621 and TorControl.py, as they use the old v0 controller protocol,
13622 and are obsoleted by TorFlow anyway.
13623 - Drop support for v1 rendezvous descriptors, since we never used
13624 them anyway, and the code has probably rotted by now. Based on
13625 patch from Karsten Loesing.
13626 - On OSX, stop warning the user that kqueue support in libevent is
13627 "experimental", since it seems to have worked fine for ages.
13630 - When generating information telling us how to extend to a given
13631 router, do not try to include the nickname if it is absent. Fixes
13632 bug 467. Bugfix on 0.2.0.3-alpha.
13633 - Fix a user-triggerable (but not remotely-triggerable) segfault
13634 in expand_filename(). Bugfix on 0.1.2.x.
13635 - Fix a memory leak when freeing incomplete requests from DNSPort.
13636 Found by Niels Provos with valgrind. Bugfix on 0.2.0.1-alpha.
13637 - Don't try to access (or alter) the state file when running
13638 --list-fingerprint or --verify-config or --hash-password. (Resolves
13639 bug 499.) Bugfix on 0.1.2.x.
13640 - Servers used to decline to publish their DirPort if their
13641 BandwidthRate, RelayBandwidthRate, or MaxAdvertisedBandwidth
13642 were below a threshold. Now they only look at BandwidthRate and
13643 RelayBandwidthRate. Bugfix on 0.1.2.x.
13644 - Remove an optimization in the AES counter-mode code that assumed
13645 that the counter never exceeded 2^68. When the counter can be set
13646 arbitrarily as an IV (as it is by Karsten's new hidden services
13647 code), this assumption no longer holds. Bugfix on 0.1.2.x.
13648 - Resume listing "AUTHORITY" flag for authorities in network status.
13649 Bugfix on 0.2.0.3-alpha; reported by Alex de Joode.
13651 o Code simplifications and refactoring:
13652 - Revamp file-writing logic so we don't need to have the entire
13653 contents of a file in memory at once before we write to disk. Tor,
13655 - Turn "descriptor store" into a full-fledged type.
13656 - Move all NT services code into a separate source file.
13657 - Unify all code that computes medians, percentile elements, etc.
13658 - Get rid of a needless malloc when parsing address policies.
13661 Changes in version 0.1.2.17 - 2007-08-30
13662 Tor 0.1.2.17 features a new Vidalia version in the Windows and OS
13663 X bundles. Vidalia 0.0.14 makes authentication required for the
13664 ControlPort in the default configuration, which addresses important
13665 security risks. Everybody who uses Vidalia (or another controller)
13668 In addition, this Tor update fixes major load balancing problems with
13669 path selection, which should speed things up a lot once many people
13672 o Major bugfixes (security):
13673 - We removed support for the old (v0) control protocol. It has been
13674 deprecated since Tor 0.1.1.1-alpha, and keeping it secure has
13675 become more of a headache than it's worth.
13677 o Major bugfixes (load balancing):
13678 - When choosing nodes for non-guard positions, weight guards
13679 proportionally less, since they already have enough load. Patch
13681 - Raise the "max believable bandwidth" from 1.5MB/s to 10MB/s. This
13682 will allow fast Tor servers to get more attention.
13683 - When we're upgrading from an old Tor version, forget our current
13684 guards and pick new ones according to the new weightings. These
13685 three load balancing patches could raise effective network capacity
13686 by a factor of four. Thanks to Mike Perry for measurements.
13688 o Major bugfixes (stream expiration):
13689 - Expire not-yet-successful application streams in all cases if
13690 they've been around longer than SocksTimeout. Right now there are
13691 some cases where the stream will live forever, demanding a new
13692 circuit every 15 seconds. Fixes bug 454; reported by lodger.
13694 o Minor features (controller):
13695 - Add a PROTOCOLINFO controller command. Like AUTHENTICATE, it
13696 is valid before any authentication has been received. It tells
13697 a controller what kind of authentication is expected, and what
13698 protocol is spoken. Implements proposal 119.
13700 o Minor bugfixes (performance):
13701 - Save on most routerlist_assert_ok() calls in routerlist.c, thus
13702 greatly speeding up loading cached-routers from disk on startup.
13703 - Disable sentinel-based debugging for buffer code: we squashed all
13704 the bugs that this was supposed to detect a long time ago, and now
13705 its only effect is to change our buffer sizes from nice powers of
13706 two (which platform mallocs tend to like) to values slightly over
13707 powers of two (which make some platform mallocs sad).
13709 o Minor bugfixes (misc):
13710 - If exit bandwidth ever exceeds one third of total bandwidth, then
13711 use the correct formula to weight exit nodes when choosing paths.
13712 Based on patch from Mike Perry.
13713 - Choose perfectly fairly among routers when choosing by bandwidth and
13714 weighting by fraction of bandwidth provided by exits. Previously, we
13715 would choose with only approximate fairness, and correct ourselves
13716 if we ran off the end of the list.
13717 - If we require CookieAuthentication but we fail to write the
13718 cookie file, we would warn but not exit, and end up in a state
13719 where no controller could authenticate. Now we exit.
13720 - If we require CookieAuthentication, stop generating a new cookie
13721 every time we change any piece of our config.
13722 - Refuse to start with certain directory authority keys, and
13723 encourage people using them to stop.
13724 - Terminate multi-line control events properly. Original patch
13726 - Fix a minor memory leak when we fail to find enough suitable
13727 servers to choose a circuit.
13728 - Stop leaking part of the descriptor when we run into a particularly
13729 unparseable piece of it.
13732 Changes in version 0.2.0.6-alpha - 2007-08-26
13733 This sixth development snapshot features a new Vidalia version in the
13734 Windows and OS X bundles. Vidalia 0.0.14 makes authentication required for
13735 the ControlPort in the default configuration, which addresses important
13738 In addition, this snapshot fixes major load balancing problems
13739 with path selection, which should speed things up a lot once many
13740 people have upgraded. The directory authorities also use a new
13741 mean-time-between-failure approach to tracking which servers are stable,
13742 rather than just looking at the most recent uptime.
13744 o New directory authorities:
13745 - Set up Tonga as the default bridge directory authority.
13748 - Directory authorities now track servers by weighted
13749 mean-times-between-failures. When we have 4 or more days of data,
13750 use measured MTBF rather than declared uptime to decide whether
13751 to call a router Stable. Implements proposal 108.
13753 o Major bugfixes (load balancing):
13754 - When choosing nodes for non-guard positions, weight guards
13755 proportionally less, since they already have enough load. Patch
13757 - Raise the "max believable bandwidth" from 1.5MB/s to 10MB/s. This
13758 will allow fast Tor servers to get more attention.
13759 - When we're upgrading from an old Tor version, forget our current
13760 guards and pick new ones according to the new weightings. These
13761 three load balancing patches could raise effective network capacity
13762 by a factor of four. Thanks to Mike Perry for measurements.
13764 o Major bugfixes (descriptor parsing):
13765 - Handle unexpected whitespace better in malformed descriptors. Bug
13766 found using Benedikt Boss's new Tor fuzzer! Bugfix on 0.2.0.x.
13769 - There is now an ugly, temporary "desc/all-recent-extrainfo-hack"
13770 GETINFO for Torstat to use until it can switch to using extrainfos.
13771 - Optionally (if built with -DEXPORTMALLINFO) export the output
13772 of mallinfo via http, as tor/mallinfo.txt. Only accessible
13776 - Do not intermix bridge routers with controller-added
13777 routers. (Bugfix on 0.2.0.x)
13778 - Do not fail with an assert when accept() returns an unexpected
13779 address family. Addresses but does not wholly fix bug 483. (Bugfix
13781 - Let directory authorities startup even when they can't generate
13782 a descriptor immediately, e.g. because they don't know their
13784 - Stop putting the authentication cookie in a file called "0"
13785 in your working directory if you don't specify anything for the
13786 new CookieAuthFile option. Reported by Matt Edman.
13787 - Make it possible to read the PROTOCOLINFO response in a way that
13788 conforms to our control-spec. Reported by Matt Edman.
13789 - Fix a minor memory leak when we fail to find enough suitable
13790 servers to choose a circuit. Bugfix on 0.1.2.x.
13791 - Stop leaking part of the descriptor when we run into a particularly
13792 unparseable piece of it. Bugfix on 0.1.2.x.
13793 - Unmap the extrainfo cache file on exit.
13796 Changes in version 0.2.0.5-alpha - 2007-08-19
13797 This fifth development snapshot fixes compilation on Windows again;
13798 fixes an obnoxious client-side bug that slowed things down and put
13799 extra load on the network; gets us closer to using the v3 directory
13800 voting scheme; makes it easier for Tor controllers to use cookie-based
13801 authentication; and fixes a variety of other bugs.
13803 o Removed features:
13804 - Version 1 directories are no longer generated in full. Instead,
13805 authorities generate and serve "stub" v1 directories that list
13806 no servers. This will stop Tor versions 0.1.0.x and earlier from
13807 working, but (for security reasons) nobody should be running those
13810 o Major bugfixes (compilation, 0.2.0.x):
13811 - Try to fix Win32 compilation again: improve checking for IPv6 types.
13812 - Try to fix MSVC compilation: build correctly on platforms that do
13813 not define s6_addr16 or s6_addr32.
13814 - Fix compile on platforms without getaddrinfo: bug found by Li-Hui
13817 o Major bugfixes (stream expiration):
13818 - Expire not-yet-successful application streams in all cases if
13819 they've been around longer than SocksTimeout. Right now there are
13820 some cases where the stream will live forever, demanding a new
13821 circuit every 15 seconds. Bugfix on 0.1.2.7-alpha; fixes bug 454;
13822 reported by lodger.
13824 o Minor features (directory servers):
13825 - When somebody requests a list of statuses or servers, and we have
13826 none of those, return a 404 rather than an empty 200.
13828 o Minor features (directory voting):
13829 - Store v3 consensus status consensuses on disk, and reload them
13832 o Minor features (security):
13833 - Warn about unsafe ControlPort configurations.
13834 - Refuse to start with certain directory authority keys, and
13835 encourage people using them to stop.
13837 o Minor features (controller):
13838 - Add a PROTOCOLINFO controller command. Like AUTHENTICATE, it
13839 is valid before any authentication has been received. It tells
13840 a controller what kind of authentication is expected, and what
13841 protocol is spoken. Implements proposal 119.
13842 - New config option CookieAuthFile to choose a new location for the
13843 cookie authentication file, and config option
13844 CookieAuthFileGroupReadable to make it group-readable.
13846 o Minor features (unit testing):
13847 - Add command-line arguments to unit-test executable so that we can
13848 invoke any chosen test from the command line rather than having
13849 to run the whole test suite at once; and so that we can turn on
13850 logging for the unit tests.
13852 o Minor bugfixes (on 0.1.2.x):
13853 - If we require CookieAuthentication but we fail to write the
13854 cookie file, we would warn but not exit, and end up in a state
13855 where no controller could authenticate. Now we exit.
13856 - If we require CookieAuthentication, stop generating a new cookie
13857 every time we change any piece of our config.
13858 - When loading bandwidth history, do not believe any information in
13859 the future. Fixes bug 434.
13860 - When loading entry guard information, do not believe any information
13862 - When we have our clock set far in the future and generate an
13863 onion key, then re-set our clock to be correct, we should not stop
13864 the onion key from getting rotated.
13865 - Clean up torrc sample config file.
13866 - Do not automatically run configure from autogen.sh. This
13867 non-standard behavior tended to annoy people who have built other
13870 o Minor bugfixes (on 0.2.0.x):
13871 - Fix a bug with AutomapHostsOnResolve that would always cause
13872 the second request to fail. Bug reported by Kate. Bugfix on
13874 - Fix a bug in ADDRMAP controller replies that would sometimes
13875 try to print a NULL. Patch from tup.
13876 - Read v3 directory authority keys from the right location.
13877 - Numerous bugfixes to directory voting code.
13880 Changes in version 0.1.2.16 - 2007-08-01
13881 Tor 0.1.2.16 fixes a critical security vulnerability that allows a
13882 remote attacker in certain situations to rewrite the user's torrc
13883 configuration file. This can completely compromise anonymity of users
13884 in most configurations, including those running the Vidalia bundles,
13885 TorK, etc. Or worse.
13887 o Major security fixes:
13888 - Close immediately after missing authentication on control port;
13889 do not allow multiple authentication attempts.
13892 Changes in version 0.2.0.4-alpha - 2007-08-01
13893 This fourth development snapshot fixes a critical security vulnerability
13894 for most users, specifically those running Vidalia, TorK, etc. Everybody
13895 should upgrade to either 0.1.2.16 or 0.2.0.4-alpha.
13897 o Major security fixes:
13898 - Close immediately after missing authentication on control port;
13899 do not allow multiple authentication attempts.
13901 o Major bugfixes (compilation):
13902 - Fix win32 compilation: apparently IN_ADDR and IN6_ADDR are already
13905 o Minor features (performance):
13906 - Be even more aggressive about releasing RAM from small
13907 empty buffers. Thanks to our free-list code, this shouldn't be too
13908 performance-intensive.
13909 - Disable sentinel-based debugging for buffer code: we squashed all
13910 the bugs that this was supposed to detect a long time ago, and
13911 now its only effect is to change our buffer sizes from nice
13912 powers of two (which platform mallocs tend to like) to values
13913 slightly over powers of two (which make some platform mallocs sad).
13914 - Log malloc statistics from mallinfo() on platforms where it
13918 Changes in version 0.2.0.3-alpha - 2007-07-29
13919 This third development snapshot introduces new experimental
13920 blocking-resistance features and a preliminary version of the v3
13921 directory voting design, and includes many other smaller features
13925 - The first pieces of our "bridge" design for blocking-resistance
13926 are implemented. People can run bridge directory authorities;
13927 people can run bridges; and people can configure their Tor clients
13928 with a set of bridges to use as the first hop into the Tor network.
13929 See http://archives.seul.org/or/talk/Jul-2007/msg00249.html for
13931 - Create listener connections before we setuid to the configured
13932 User and Group. Now non-Windows users can choose port values
13933 under 1024, start Tor as root, and have Tor bind those ports
13934 before it changes to another UID. (Windows users could already
13936 - Added a new ConstrainedSockets config option to set SO_SNDBUF and
13937 SO_RCVBUF on TCP sockets. Hopefully useful for Tor servers running
13938 on "vserver" accounts. (Patch from coderman.)
13939 - Be even more aggressive about separating local traffic from relayed
13940 traffic when RelayBandwidthRate is set. (Refines proposal 111.)
13942 o Major features (experimental):
13943 - First cut of code for "v3 dir voting": directory authorities will
13944 vote on a common network status document rather than each publishing
13945 their own opinion. This code needs more testing and more corner-case
13946 handling before it's ready for use.
13949 - Directory authorities now call routers Fast if their bandwidth is
13950 at least 100KB/s, and consider their bandwidth adequate to be a
13951 Guard if it is at least 250KB/s, no matter the medians. This fix
13952 complements proposal 107. [Bugfix on 0.1.2.x]
13953 - Directory authorities now never mark more than 3 servers per IP as
13954 Valid and Running. (Implements proposal 109, by Kevin Bauer and
13956 - Minor change to organizationName and commonName generation
13957 procedures in TLS certificates during Tor handshakes, to invalidate
13958 some earlier censorware approaches. This is not a long-term
13959 solution, but applying it will give us a bit of time to look into
13960 the epidemiology of countermeasures as they spread.
13962 o Major bugfixes (directory):
13963 - Rewrite directory tokenization code to never run off the end of
13964 a string. Fixes bug 455. Patch from croup. [Bugfix on 0.1.2.x]
13966 o Minor features (controller):
13967 - Add a SOURCE_ADDR field to STREAM NEW events so that controllers can
13968 match requests to applications. (Patch from Robert Hogan.)
13969 - Report address and port correctly on connections to DNSPort. (Patch
13970 from Robert Hogan.)
13971 - Add a RESOLVE command to launch hostname lookups. (Original patch
13972 from Robert Hogan.)
13973 - Add GETINFO status/enough-dir-info to let controllers tell whether
13974 Tor has downloaded sufficient directory information. (Patch
13976 - You can now use the ControlSocket option to tell Tor to listen for
13977 controller connections on Unix domain sockets on systems that
13978 support them. (Patch from Peter Palfrader.)
13979 - STREAM NEW events are generated for DNSPort requests and for
13980 tunneled directory connections. (Patch from Robert Hogan.)
13981 - New "GETINFO address-mappings/*" command to get address mappings
13982 with expiry information. "addr-mappings/*" is now deprecated.
13985 o Minor features (misc):
13986 - Merge in some (as-yet-unused) IPv6 address manipulation code. (Patch
13988 - The tor-gencert tool for v3 directory authorities now creates all
13989 files as readable to the file creator only, and write-protects
13990 the authority identity key.
13991 - When dumping memory usage, list bytes used in buffer memory
13993 - When running with dmalloc, dump more stats on hup and on exit.
13994 - Directory authorities now fail quickly and (relatively) harmlessly
13995 if they generate a network status document that is somehow
13998 o Traffic load balancing improvements:
13999 - If exit bandwidth ever exceeds one third of total bandwidth, then
14000 use the correct formula to weight exit nodes when choosing paths.
14001 (Based on patch from Mike Perry.)
14002 - Choose perfectly fairly among routers when choosing by bandwidth and
14003 weighting by fraction of bandwidth provided by exits. Previously, we
14004 would choose with only approximate fairness, and correct ourselves
14005 if we ran off the end of the list. [Bugfix on 0.1.2.x]
14007 o Performance improvements:
14008 - Be more aggressive with freeing buffer RAM or putting it on the
14010 - Use Critical Sections rather than Mutexes for synchronizing threads
14011 on win32; Mutexes are heavier-weight, and designed for synchronizing
14014 o Deprecated and removed features:
14015 - RedirectExits is now deprecated.
14016 - Stop allowing address masks that do not correspond to bit prefixes.
14017 We have warned about these for a really long time; now it's time
14018 to reject them. (Patch from croup.)
14020 o Minor bugfixes (directory):
14021 - Fix another crash bug related to extra-info caching. (Bug found by
14022 Peter Palfrader.) [Bugfix on 0.2.0.2-alpha]
14023 - Directories no longer return a "304 not modified" when they don't
14024 have the networkstatus the client asked for. Also fix a memory
14025 leak when returning 304 not modified. [Bugfixes on 0.2.0.2-alpha]
14026 - We had accidentally labelled 0.1.2.x directory servers as not
14027 suitable for begin_dir requests, and had labelled no directory
14028 servers as suitable for uploading extra-info documents. [Bugfix
14031 o Minor bugfixes (dns):
14032 - Fix a crash when DNSPort is set more than once. (Patch from Robert
14033 Hogan.) [Bugfix on 0.2.0.2-alpha]
14034 - Add DNSPort connections to the global connection list, so that we
14035 can time them out correctly. (Bug found by Robert Hogan.) [Bugfix
14037 - Fix a dangling reference that could lead to a crash when DNSPort is
14038 changed or closed (Patch from Robert Hogan.) [Bugfix on
14041 o Minor bugfixes (controller):
14042 - Provide DNS expiry times in GMT, not in local time. For backward
14043 compatibility, ADDRMAP events only provide GMT expiry in an extended
14044 field. "GETINFO address-mappings" always does the right thing.
14045 - Use CRLF line endings properly in NS events.
14046 - Terminate multi-line control events properly. (Original patch
14047 from tup.) [Bugfix on 0.1.2.x-alpha]
14048 - Do not include spaces in SOURCE_ADDR fields in STREAM
14049 events. Resolves bug 472. [Bugfix on 0.2.0.x-alpha]
14052 Changes in version 0.1.2.15 - 2007-07-17
14053 Tor 0.1.2.15 fixes several crash bugs, fixes some anonymity-related
14054 problems, fixes compilation on BSD, and fixes a variety of other
14055 bugs. Everybody should upgrade.
14057 o Major bugfixes (compilation):
14058 - Fix compile on FreeBSD/NetBSD/OpenBSD. Oops.
14060 o Major bugfixes (crashes):
14061 - Try even harder not to dereference the first character after
14062 an mmap(). Reported by lodger.
14063 - Fix a crash bug in directory authorities when we re-number the
14064 routerlist while inserting a new router.
14065 - When the cached-routers file is an even multiple of the page size,
14066 don't run off the end and crash. (Fixes bug 455; based on idea
14068 - Fix eventdns.c behavior on Solaris: It is critical to include
14069 orconfig.h _before_ sys/types.h, so that we can get the expected
14070 definition of _FILE_OFFSET_BITS.
14072 o Major bugfixes (security):
14073 - Fix a possible buffer overrun when using BSD natd support. Bug
14075 - When sending destroy cells from a circuit's origin, don't include
14076 the reason for tearing down the circuit. The spec says we didn't,
14077 and now we actually don't. Reported by lodger.
14078 - Keep streamids from different exits on a circuit separate. This
14079 bug may have allowed other routers on a given circuit to inject
14080 cells into streams. Reported by lodger; fixes bug 446.
14081 - If there's a never-before-connected-to guard node in our list,
14082 never choose any guards past it. This way we don't expand our
14083 guard list unless we need to.
14085 o Minor bugfixes (guard nodes):
14086 - Weight guard selection by bandwidth, so that low-bandwidth nodes
14087 don't get overused as guards.
14089 o Minor bugfixes (directory):
14090 - Correctly count the number of authorities that recommend each
14091 version. Previously, we were under-counting by 1.
14092 - Fix a potential crash bug when we load many server descriptors at
14093 once and some of them make others of them obsolete. Fixes bug 458.
14095 o Minor bugfixes (hidden services):
14096 - Stop tearing down the whole circuit when the user asks for a
14097 connection to a port that the hidden service didn't configure.
14100 o Minor bugfixes (misc):
14101 - On Windows, we were preventing other processes from reading
14102 cached-routers while Tor was running. Reported by janbar.
14103 - Fix a possible (but very unlikely) bug in picking routers by
14104 bandwidth. Add a log message to confirm that it is in fact
14105 unlikely. Patch from lodger.
14106 - Backport a couple of memory leak fixes.
14107 - Backport miscellaneous cosmetic bugfixes.
14110 Changes in version 0.2.0.2-alpha - 2007-06-02
14111 o Major bugfixes on 0.2.0.1-alpha:
14112 - Fix an assertion failure related to servers without extra-info digests.
14113 Resolves bugs 441 and 442.
14115 o Minor features (directory):
14116 - Support "If-Modified-Since" when answering HTTP requests for
14117 directories, running-routers documents, and network-status documents.
14118 (There's no need to support it for router descriptors, since those
14119 are downloaded by descriptor digest.)
14121 o Minor build issues:
14122 - Clear up some MIPSPro compiler warnings.
14123 - When building from a tarball on a machine that happens to have SVK
14124 installed, report the micro-revision as whatever version existed
14125 in the tarball, not as "x".
14128 Changes in version 0.2.0.1-alpha - 2007-06-01
14129 This early development snapshot provides new features for people running
14130 Tor as both a client and a server (check out the new RelayBandwidth
14131 config options); lets Tor run as a DNS proxy; and generally moves us
14132 forward on a lot of fronts.
14134 o Major features, server usability:
14135 - New config options RelayBandwidthRate and RelayBandwidthBurst:
14136 a separate set of token buckets for relayed traffic. Right now
14137 relayed traffic is defined as answers to directory requests, and
14138 OR connections that don't have any local circuits on them.
14140 o Major features, client usability:
14141 - A client-side DNS proxy feature to replace the need for
14142 dns-proxy-tor: Just set "DNSPort 9999", and Tor will now listen
14143 for DNS requests on port 9999, use the Tor network to resolve them
14144 anonymously, and send the reply back like a regular DNS server.
14145 The code still only implements a subset of DNS.
14146 - Make PreferTunneledDirConns and TunnelDirConns work even when
14147 we have no cached directory info. This means Tor clients can now
14148 do all of their connections protected by TLS.
14150 o Major features, performance and efficiency:
14151 - Directory authorities accept and serve "extra info" documents for
14152 routers. These documents contain fields from router descriptors
14153 that aren't usually needed, and that use a lot of excess
14154 bandwidth. Once these fields are removed from router descriptors,
14155 the bandwidth savings should be about 60%. [Partially implements
14157 - Servers upload extra-info documents to any authority that accepts
14158 them. Authorities (and caches that have been configured to download
14159 extra-info documents) download them as needed. [Partially implements
14161 - Change the way that Tor buffers data that it is waiting to write.
14162 Instead of queueing data cells in an enormous ring buffer for each
14163 client->OR or OR->OR connection, we now queue cells on a separate
14164 queue for each circuit. This lets us use less slack memory, and
14165 will eventually let us be smarter about prioritizing different kinds
14167 - Use memory pools to allocate cells with better speed and memory
14168 efficiency, especially on platforms where malloc() is inefficient.
14169 - Stop reading on edge connections when their corresponding circuit
14170 buffers are full; start again as the circuits empty out.
14172 o Major features, other:
14173 - Add an HSAuthorityRecordStats option that hidden service authorities
14174 can use to track statistics of overall hidden service usage without
14175 logging information that would be very useful to an attacker.
14176 - Start work implementing multi-level keys for directory authorities:
14177 Add a standalone tool to generate key certificates. (Proposal 103.)
14180 - Directory authorities now call routers Stable if they have an
14181 uptime of at least 30 days, even if that's not the median uptime
14182 in the network. Implements proposal 107, suggested by Kevin Bauer
14185 o Minor fixes (resource management):
14186 - Count the number of open sockets separately from the number
14187 of active connection_t objects. This will let us avoid underusing
14188 our allocated connection limit.
14189 - We no longer use socket pairs to link an edge connection to an
14190 anonymous directory connection or a DirPort test connection.
14191 Instead, we track the link internally and transfer the data
14192 in-process. This saves two sockets per "linked" connection (at the
14193 client and at the server), and avoids the nasty Windows socketpair()
14195 - Keep unused 4k and 16k buffers on free lists, rather than wasting 8k
14196 for every single inactive connection_t. Free items from the
14197 4k/16k-buffer free lists when they haven't been used for a while.
14199 o Minor features (build):
14200 - Make autoconf search for libevent, openssl, and zlib consistently.
14201 - Update deprecated macros in configure.in.
14202 - When warning about missing headers, tell the user to let us
14203 know if the compile succeeds anyway, so we can downgrade the
14205 - Include the current subversion revision as part of the version
14206 string: either fetch it directly if we're in an SVN checkout, do
14207 some magic to guess it if we're in an SVK checkout, or use
14208 the last-detected version if we're building from a .tar.gz.
14209 Use this version consistently in log messages.
14211 o Minor features (logging):
14212 - Always prepend "Bug: " to any log message about a bug.
14213 - Put a platform string (e.g. "Linux i686") in the startup log
14214 message, so when people paste just their logs, we know if it's
14215 OpenBSD or Windows or what.
14216 - When logging memory usage, break down memory used in buffers by
14219 o Minor features (directory system):
14220 - New config option V2AuthoritativeDirectory that all directory
14221 authorities should set. This will let future authorities choose
14222 not to serve V2 directory information.
14223 - Directory authorities allow multiple router descriptors and/or extra
14224 info documents to be uploaded in a single go. This will make
14225 implementing proposal 104 simpler.
14227 o Minor features (controller):
14228 - Add a new config option __DisablePredictedCircuits designed for
14229 use by the controller, when we don't want Tor to build any circuits
14231 - Let the controller specify HOP=%d as an argument to ATTACHSTREAM,
14232 so we can exit from the middle of the circuit.
14233 - Implement "getinfo status/circuit-established".
14234 - Implement "getinfo status/version/..." so a controller can tell
14235 whether the current version is recommended, and whether any versions
14236 are good, and how many authorities agree. (Patch from shibz.)
14238 o Minor features (hidden services):
14239 - Allow multiple HiddenServicePort directives with the same virtual
14240 port; when they occur, the user is sent round-robin to one
14241 of the target ports chosen at random. Partially fixes bug 393 by
14242 adding limited ad-hoc round-robining.
14244 o Minor features (other):
14246 - Add a new AutomapHostsOnResolve option: when it is enabled, any
14247 resolve request for hosts matching a given pattern causes Tor to
14248 generate an internal virtual address mapping for that host. This
14249 allows DNSPort to work sensibly with hidden service users. By
14250 default, .exit and .onion addresses are remapped; the list of
14251 patterns can be reconfigured with AutomapHostsSuffixes.
14252 - Add an "-F" option to tor-resolve to force a resolve for a .onion
14253 address. Thanks to the AutomapHostsOnResolve option, this is no
14254 longer a completely silly thing to do.
14255 - If Tor is invoked from something that isn't a shell (e.g. Vidalia),
14256 now we expand "-f ~/.tor/torrc" correctly. Suggested by Matt Edman.
14257 - Treat "2gb" when given in torrc for a bandwidth as meaning 2gb,
14258 minus 1 byte: the actual maximum declared bandwidth.
14260 o Removed features:
14261 - Removed support for the old binary "version 0" controller protocol.
14262 This has been deprecated since 0.1.1, and warnings have been issued
14263 since 0.1.2. When we encounter a v0 control message, we now send
14264 back an error and close the connection.
14265 - Remove the old "dns worker" server DNS code: it hasn't been default
14266 since 0.1.2.2-alpha, and all the servers seem to be using the new
14269 o Minor bugfixes (portability):
14270 - Even though Windows is equally happy with / and \ as path separators,
14271 try to use \ consistently on Windows and / consistently on Unix: it
14272 makes the log messages nicer.
14273 - Correctly report platform name on Windows 95 OSR2 and Windows 98 SE.
14274 - Read resolv.conf files correctly on platforms where read() returns
14275 partial results on small file reads.
14277 o Minor bugfixes (directory):
14278 - Correctly enforce that elements of directory objects do not appear
14279 more often than they are allowed to appear.
14280 - When we are reporting the DirServer line we just parsed, we were
14281 logging the second stanza of the key fingerprint, not the first.
14283 o Minor bugfixes (logging):
14284 - When we hit an EOF on a log (probably because we're shutting down),
14285 don't try to remove the log from the list: just mark it as
14286 unusable. (Bulletproofs against bug 222.)
14288 o Minor bugfixes (other):
14289 - In the exitlist script, only consider the most recently published
14290 server descriptor for each server. Also, when the user requests
14291 a list of servers that _reject_ connections to a given address,
14292 explicitly exclude the IPs that also have servers that accept
14293 connections to that address. (Resolves bug 405.)
14294 - Stop allowing hibernating servers to be "stable" or "fast".
14295 - On Windows, we were preventing other processes from reading
14296 cached-routers while Tor was running. (Reported by janbar)
14297 - Make the NodeFamilies config option work. (Reported by
14298 lodger -- it has never actually worked, even though we added it
14300 - Check return values from pthread_mutex functions.
14301 - Don't save non-general-purpose router descriptors to the disk cache,
14302 because we have no way of remembering what their purpose was when
14304 - Add even more asserts to hunt down bug 417.
14305 - Build without verbose warnings even on (not-yet-released) gcc 4.2.
14306 - Fix a possible (but very unlikely) bug in picking routers by bandwidth.
14307 Add a log message to confirm that it is in fact unlikely.
14309 o Minor bugfixes (controller):
14310 - Make 'getinfo fingerprint' return a 551 error if we're not a
14311 server, so we match what the control spec claims we do. Reported
14313 - Fix a typo in an error message when extendcircuit fails that
14314 caused us to not follow the \r\n-based delimiter protocol. Reported
14317 o Code simplifications and refactoring:
14318 - Stop passing around circuit_t and crypt_path_t pointers that are
14319 implicit in other procedure arguments.
14320 - Drop the old code to choke directory connections when the
14321 corresponding OR connections got full: thanks to the cell queue
14322 feature, OR conns don't get full any more.
14323 - Make dns_resolve() handle attaching connections to circuits
14324 properly, so the caller doesn't have to.
14325 - Rename wants_to_read and wants_to_write to read/write_blocked_on_bw.
14326 - Keep the connection array as a dynamic smartlist_t, rather than as
14327 a fixed-sized array. This is important, as the number of connections
14328 is becoming increasingly decoupled from the number of sockets.
14331 Changes in version 0.1.2.14 - 2007-05-25
14332 Tor 0.1.2.14 changes the addresses of two directory authorities (this
14333 change especially affects those who serve or use hidden services),
14334 and fixes several other crash- and security-related bugs.
14336 o Directory authority changes:
14337 - Two directory authorities (moria1 and moria2) just moved to new
14338 IP addresses. This change will particularly affect those who serve
14339 or use hidden services.
14341 o Major bugfixes (crashes):
14342 - If a directory server runs out of space in the connection table
14343 as it's processing a begin_dir request, it will free the exit stream
14344 but leave it attached to the circuit, leading to unpredictable
14345 behavior. (Reported by seeess, fixes bug 425.)
14346 - Fix a bug in dirserv_remove_invalid() that would cause authorities
14347 to corrupt memory under some really unlikely scenarios.
14348 - Tighten router parsing rules. (Bugs reported by Benedikt Boss.)
14349 - Avoid segfaults when reading from mmaped descriptor file. (Reported
14352 o Major bugfixes (security):
14353 - When choosing an entry guard for a circuit, avoid using guards
14354 that are in the same family as the chosen exit -- not just guards
14355 that are exactly the chosen exit. (Reported by lodger.)
14357 o Major bugfixes (resource management):
14358 - If a directory authority is down, skip it when deciding where to get
14359 networkstatus objects or descriptors. Otherwise we keep asking
14360 every 10 seconds forever. Fixes bug 384.
14361 - Count it as a failure if we fetch a valid network-status but we
14362 don't want to keep it. Otherwise we'll keep fetching it and keep
14363 not wanting to keep it. Fixes part of bug 422.
14364 - If all of our dirservers have given us bad or no networkstatuses
14365 lately, then stop hammering them once per minute even when we
14366 think they're failed. Fixes another part of bug 422.
14369 - Actually set the purpose correctly for descriptors inserted with
14370 purpose=controller.
14371 - When we have k non-v2 authorities in our DirServer config,
14372 we ignored the last k authorities in the list when updating our
14374 - Correctly back-off from requesting router descriptors that we are
14375 having a hard time downloading.
14376 - Read resolv.conf files correctly on platforms where read() returns
14377 partial results on small file reads.
14378 - Don't rebuild the entire router store every time we get 32K of
14379 routers: rebuild it when the journal gets very large, or when
14380 the gaps in the store get very large.
14383 - When routers publish SVN revisions in their router descriptors,
14384 authorities now include those versions correctly in networkstatus
14386 - Warn when using a version of libevent before 1.3b to run a server on
14387 OSX or BSD: these versions interact badly with userspace threads.
14390 Changes in version 0.1.2.13 - 2007-04-24
14391 This release features some major anonymity fixes, such as safer path
14392 selection; better client performance; faster bootstrapping, better
14393 address detection, and better DNS support for servers; write limiting as
14394 well as read limiting to make servers easier to run; and a huge pile of
14395 other features and bug fixes. The bundles also ship with Vidalia 0.0.11.
14397 Tor 0.1.2.13 is released in memory of Rob Levin (1955-2006), aka lilo
14398 of the Freenode IRC network, remembering his patience and vision for
14399 free speech on the Internet.
14402 - Fix a memory leak when we ask for "all" networkstatuses and we
14403 get one we don't recognize.
14404 - Add more asserts to hunt down bug 417.
14405 - Disable kqueue on OS X 10.3 and earlier, to fix bug 371.
14408 Changes in version 0.1.2.12-rc - 2007-03-16
14410 - Fix an infinite loop introduced in 0.1.2.7-alpha when we serve
14411 directory information requested inside Tor connections (i.e. via
14412 begin_dir cells). It only triggered when the same connection was
14413 serving other data at the same time. Reported by seeess.
14416 - When creating a circuit via the controller, send a 'launched'
14417 event when we're done, so we follow the spec better.
14420 Changes in version 0.1.2.11-rc - 2007-03-15
14421 o Minor bugfixes (controller), reported by daejees:
14422 - Correct the control spec to match how the code actually responds
14423 to 'getinfo addr-mappings/*'.
14424 - The control spec described a GUARDS event, but the code
14425 implemented a GUARD event. Standardize on GUARD, but let people
14426 ask for GUARDS too.
14429 Changes in version 0.1.2.10-rc - 2007-03-07
14430 o Major bugfixes (Windows):
14431 - Do not load the NT services library functions (which may not exist)
14432 just to detect if we're a service trying to shut down. Now we run
14433 on Win98 and friends again.
14435 o Minor bugfixes (other):
14436 - Clarify a couple of log messages.
14437 - Fix a misleading socks5 error number.
14440 Changes in version 0.1.2.9-rc - 2007-03-02
14441 o Major bugfixes (Windows):
14442 - On MinGW, use "%I64u" to printf/scanf 64-bit integers, instead
14443 of the usual GCC "%llu". This prevents a bug when saving 64-bit
14444 int configuration values: the high-order 32 bits would get
14445 truncated. In particular, we were being bitten by the default
14446 MaxAdvertisedBandwidth of 128 TB turning into 0. (Fixes bug 400
14447 and maybe also bug 397.)
14449 o Minor bugfixes (performance):
14450 - Use OpenSSL's AES implementation on platforms where it's faster.
14451 This could save us as much as 10% CPU usage.
14453 o Minor bugfixes (server):
14454 - Do not rotate onion key immediately after setting it for the first
14457 o Minor bugfixes (directory authorities):
14458 - Stop calling servers that have been hibernating for a long time
14459 "stable". Also, stop letting hibernating or obsolete servers affect
14460 uptime and bandwidth cutoffs.
14461 - Stop listing hibernating servers in the v1 directory.
14463 o Minor bugfixes (hidden services):
14464 - Upload hidden service descriptors slightly less often, to reduce
14465 load on authorities.
14467 o Minor bugfixes (other):
14468 - Fix an assert that could trigger if a controller quickly set then
14469 cleared EntryNodes. Bug found by Udo van den Heuvel.
14470 - On architectures where sizeof(int)>4, still clamp declarable bandwidth
14472 - Fix a potential race condition in the rpm installer. Found by
14474 - Try to fix eventdns warnings once and for all: do not treat a dns rcode
14475 of 2 as indicating that the server is completely bad; it sometimes
14476 means that the server is just bad for the request in question. (may fix
14477 the last of bug 326.)
14478 - Disable encrypted directory connections when we don't have a server
14479 descriptor for the destination. We'll get this working again in
14483 Changes in version 0.1.2.8-beta - 2007-02-26
14484 o Major bugfixes (crashes):
14485 - Stop crashing when the controller asks us to resetconf more than
14486 one config option at once. (Vidalia 0.0.11 does this.)
14487 - Fix a crash that happened on Win98 when we're given command-line
14488 arguments: don't try to load NT service functions from advapi32.dll
14489 except when we need them. (Bug introduced in 0.1.2.7-alpha;
14491 - Fix a longstanding obscure crash bug that could occur when
14492 we run out of DNS worker processes. (Resolves bug 390.)
14494 o Major bugfixes (hidden services):
14495 - Correctly detect whether hidden service descriptor downloads are
14496 in-progress. (Suggested by Karsten Loesing; fixes bug 399.)
14498 o Major bugfixes (accounting):
14499 - When we start during an accounting interval before it's time to wake
14500 up, remember to wake up at the correct time. (May fix bug 342.)
14502 o Minor bugfixes (controller):
14503 - Give the controller END_STREAM_REASON_DESTROY events _before_ we
14504 clear the corresponding on_circuit variable, and remember later
14505 that we don't need to send a redundant CLOSED event. Resolves part
14507 - Report events where a resolve succeeded or where we got a socks
14508 protocol error correctly, rather than calling both of them
14510 - Change reported stream target addresses to IP consistently when
14511 we finally get the IP from an exit node.
14512 - Send log messages to the controller even if they happen to be very
14515 o Minor bugfixes (other):
14516 - Display correct results when reporting which versions are
14517 recommended, and how recommended they are. (Resolves bug 383.)
14518 - Improve our estimates for directory bandwidth to be less random:
14519 guess that an unrecognized directory will have the average bandwidth
14520 from all known directories, not that it will have the average
14521 bandwidth from those directories earlier than it on the list.
14522 - If we start a server with ClientOnly 1, then set ClientOnly to 0
14523 and hup, stop triggering an assert based on an empty onion_key.
14524 - On platforms with no working mmap() equivalent, don't warn the
14525 user when cached-routers doesn't exist.
14526 - Warn the user when mmap() [or its equivalent] fails for some reason
14527 other than file-not-found.
14528 - Don't warn the user when cached-routers.new doesn't exist: that's
14529 perfectly fine when starting up for the first time.
14530 - When EntryNodes are configured, rebuild the guard list to contain,
14531 in order: the EntryNodes that were guards before; the rest of the
14532 EntryNodes; the nodes that were guards before.
14533 - Mask out all signals in sub-threads; only the libevent signal
14534 handler should be processing them. This should prevent some crashes
14535 on some machines using pthreads. (Patch from coderman.)
14536 - Fix switched arguments on memset in the implementation of
14537 tor_munmap() for systems with no mmap() call.
14538 - When Tor receives a router descriptor that it asked for, but
14539 no longer wants (because it has received fresh networkstatuses
14540 in the meantime), do not warn the user. Cache the descriptor if
14541 we're a cache; drop it if we aren't.
14542 - Make earlier entry guards _really_ get retried when the network
14544 - On a malformed DNS reply, always give an error to the corresponding
14546 - Build with recent libevents on platforms that do not define the
14547 nonstandard types "u_int8_t" and friends.
14549 o Minor features (controller):
14550 - Warn the user when an application uses the obsolete binary v0
14551 control protocol. We're planning to remove support for it during
14552 the next development series, so it's good to give people some
14554 - Add STREAM_BW events to report per-entry-stream bandwidth
14555 use. (Patch from Robert Hogan.)
14556 - Rate-limit SIGNEWNYM signals in response to controllers that
14557 impolitely generate them for every single stream. (Patch from
14558 mwenge; closes bug 394.)
14559 - Make REMAP stream events have a SOURCE (cache or exit), and
14560 make them generated in every case where we get a successful
14561 connected or resolved cell.
14563 o Minor bugfixes (performance):
14564 - Call router_have_min_dir_info half as often. (This is showing up in
14565 some profiles, but not others.)
14566 - When using GCC, make log_debug never get called at all, and its
14567 arguments never get evaluated, when no debug logs are configured.
14568 (This is showing up in some profiles, but not others.)
14571 - Remove some never-implemented options. Mark PathlenCoinWeight as
14573 - Implement proposal 106: Stop requiring clients to have well-formed
14574 certificates; stop checking nicknames in certificates. (Clients
14575 have certificates so that they can look like Tor servers, but in
14576 the future we might want to allow them to look like regular TLS
14577 clients instead. Nicknames in certificates serve no purpose other
14578 than making our protocol easier to recognize on the wire.)
14579 - Revise messages on handshake failure again to be even more clear about
14580 which are incoming connections and which are outgoing.
14581 - Discard any v1 directory info that's over 1 month old (for
14582 directories) or over 1 week old (for running-routers lists).
14583 - Do not warn when individual nodes in the configuration's EntryNodes,
14584 ExitNodes, etc are down: warn only when all possible nodes
14585 are down. (Fixes bug 348.)
14586 - Always remove expired routers and networkstatus docs before checking
14587 whether we have enough information to build circuits. (Fixes
14589 - Put a lower-bound on MaxAdvertisedBandwidth.
14592 Changes in version 0.1.2.7-alpha - 2007-02-06
14593 o Major bugfixes (rate limiting):
14594 - Servers decline directory requests much more aggressively when
14595 they're low on bandwidth. Otherwise they end up queueing more and
14596 more directory responses, which can't be good for latency.
14597 - But never refuse directory requests from local addresses.
14598 - Fix a memory leak when sending a 503 response for a networkstatus
14600 - Be willing to read or write on local connections (e.g. controller
14601 connections) even when the global rate limiting buckets are empty.
14602 - If our system clock jumps back in time, don't publish a negative
14603 uptime in the descriptor. Also, don't let the global rate limiting
14604 buckets go absurdly negative.
14605 - Flush local controller connection buffers periodically as we're
14606 writing to them, so we avoid queueing 4+ megabytes of data before
14609 o Major bugfixes (NT services):
14610 - Install as NT_AUTHORITY\LocalService rather than as SYSTEM; add a
14611 command-line flag so that admins can override the default by saying
14612 "tor --service install --user "SomeUser"". This will not affect
14613 existing installed services. Also, warn the user that the service
14614 will look for its configuration file in the service user's
14615 %appdata% directory. (We can't do the 'hardwire the user's appdata
14616 directory' trick any more, since we may not have read access to that
14619 o Major bugfixes (other):
14620 - Previously, we would cache up to 16 old networkstatus documents
14621 indefinitely, if they came from nontrusted authorities. Now we
14622 discard them if they are more than 10 days old.
14623 - Fix a crash bug in the presence of DNS hijacking (reported by Andrew
14625 - Detect and reject malformed DNS responses containing circular
14627 - If exits are rare enough that we're not marking exits as guards,
14628 ignore exit bandwidth when we're deciding the required bandwidth
14630 - When we're handling a directory connection tunneled over Tor,
14631 don't fill up internal memory buffers with all the data we want
14632 to tunnel; instead, only add it if the OR connection that will
14633 eventually receive it has some room for it. (This can lead to
14634 slowdowns in tunneled dir connections; a better solution will have
14635 to wait for 0.2.0.)
14637 o Minor bugfixes (dns):
14638 - Add some defensive programming to eventdns.c in an attempt to catch
14639 possible memory-stomping bugs.
14640 - Detect and reject DNS replies containing IPv4 or IPv6 records with
14641 an incorrect number of bytes. (Previously, we would ignore the
14643 - Fix as-yet-unused reverse IPv6 lookup code so it sends nybbles
14644 in the correct order, and doesn't crash.
14645 - Free memory held in recently-completed DNS lookup attempts on exit.
14646 This was not a memory leak, but may have been hiding memory leaks.
14647 - Handle TTL values correctly on reverse DNS lookups.
14648 - Treat failure to parse resolv.conf as an error.
14650 o Minor bugfixes (other):
14651 - Fix crash with "tor --list-fingerprint" (reported by seeess).
14652 - When computing clock skew from directory HTTP headers, consider what
14653 time it was when we finished asking for the directory, not what
14655 - Expire socks connections if they spend too long waiting for the
14656 handshake to finish. Previously we would let them sit around for
14657 days, if the connecting application didn't close them either.
14658 - And if the socks handshake hasn't started, don't send a
14659 "DNS resolve socks failed" handshake reply; just close it.
14660 - Stop using C functions that OpenBSD's linker doesn't like.
14661 - Don't launch requests for descriptors unless we have networkstatuses
14662 from at least half of the authorities. This delays the first
14663 download slightly under pathological circumstances, but can prevent
14664 us from downloading a bunch of descriptors we don't need.
14665 - Do not log IPs with TLS failures for incoming TLS
14666 connections. (Fixes bug 382.)
14667 - If the user asks to use invalid exit nodes, be willing to use
14669 - Stop using the reserved ac_cv namespace in our configure script.
14670 - Call stat() slightly less often; use fstat() when possible.
14671 - Refactor the way we handle pending circuits when an OR connection
14672 completes or fails, in an attempt to fix a rare crash bug.
14673 - Only rewrite a conn's address based on X-Forwarded-For: headers
14674 if it's a parseable public IP address; and stop adding extra quotes
14675 to the resulting address.
14678 - Weight directory requests by advertised bandwidth. Now we can
14679 let servers enable write limiting but still allow most clients to
14680 succeed at their directory requests. (We still ignore weights when
14681 choosing a directory authority; I hope this is a feature.)
14684 - Create a new file ReleaseNotes which was the old ChangeLog. The
14685 new ChangeLog file now includes the summaries for all development
14687 - Check for addresses with invalid characters at the exit as well
14688 as at the client, and warn less verbosely when they fail. You can
14689 override this by setting ServerDNSAllowNonRFC953Addresses to 1.
14690 - Adapt a patch from goodell to let the contrib/exitlist script
14691 take arguments rather than require direct editing.
14692 - Inform the server operator when we decide not to advertise a
14693 DirPort due to AccountingMax enabled or a low BandwidthRate. It
14694 was confusing Zax, so now we're hopefully more helpful.
14695 - Bring us one step closer to being able to establish an encrypted
14696 directory tunnel without knowing a descriptor first. Still not
14697 ready yet. As part of the change, now assume we can use a
14698 create_fast cell if we don't know anything about a router.
14699 - Allow exit nodes to use nameservers running on ports other than 53.
14700 - Servers now cache reverse DNS replies.
14701 - Add an --ignore-missing-torrc command-line option so that we can
14702 get the "use sensible defaults if the configuration file doesn't
14703 exist" behavior even when specifying a torrc location on the command
14706 o Minor features (controller):
14707 - Track reasons for OR connection failure; make these reasons
14708 available via the controller interface. (Patch from Mike Perry.)
14709 - Add a SOCKS_BAD_HOSTNAME client status event so controllers
14710 can learn when clients are sending malformed hostnames to Tor.
14711 - Clean up documentation for controller status events.
14712 - Add a REMAP status to stream events to note that a stream's
14713 address has changed because of a cached address or a MapAddress
14717 Changes in version 0.1.2.6-alpha - 2007-01-09
14719 - Fix an assert error introduced in 0.1.2.5-alpha: if a single TLS
14720 connection handles more than 4 gigs in either direction, we crash.
14721 - Fix an assert error introduced in 0.1.2.5-alpha: if we're an
14722 advertised exit node, somebody might try to exit from us when
14723 we're bootstrapping and before we've built our descriptor yet.
14724 Refuse the connection rather than crashing.
14727 - Warn if we (as a server) find that we've resolved an address that we
14728 weren't planning to resolve.
14729 - Warn that using select() on any libevent version before 1.1 will be
14730 unnecessarily slow (even for select()).
14731 - Flush ERR-level controller status events just like we currently
14732 flush ERR-level log events, so that a Tor shutdown doesn't prevent
14733 the controller from learning about current events.
14735 o Minor features (more controller status events):
14736 - Implement EXTERNAL_ADDRESS server status event so controllers can
14737 learn when our address changes.
14738 - Implement BAD_SERVER_DESCRIPTOR server status event so controllers
14739 can learn when directories reject our descriptor.
14740 - Implement SOCKS_UNKNOWN_PROTOCOL client status event so controllers
14741 can learn when a client application is speaking a non-socks protocol
14743 - Implement DANGEROUS_SOCKS client status event so controllers
14744 can learn when a client application is leaking DNS addresses.
14745 - Implement BUG general status event so controllers can learn when
14746 Tor is unhappy about its internal invariants.
14747 - Implement CLOCK_SKEW general status event so controllers can learn
14748 when Tor thinks the system clock is set incorrectly.
14749 - Implement GOOD_SERVER_DESCRIPTOR and ACCEPTED_SERVER_DESCRIPTOR
14750 server status events so controllers can learn when their descriptors
14751 are accepted by a directory.
14752 - Implement CHECKING_REACHABILITY and REACHABILITY_{SUCCEEDED|FAILED}
14753 server status events so controllers can learn about Tor's progress in
14754 deciding whether it's reachable from the outside.
14755 - Implement BAD_LIBEVENT general status event so controllers can learn
14756 when we have a version/method combination in libevent that needs to
14758 - Implement NAMESERVER_STATUS, NAMESERVER_ALL_DOWN, DNS_HIJACKED,
14759 and DNS_USELESS server status events so controllers can learn
14760 about changes to DNS server status.
14762 o Minor features (directory):
14763 - Authorities no longer recommend exits as guards if this would shift
14764 too much load to the exit nodes.
14767 Changes in version 0.1.2.5-alpha - 2007-01-06
14769 - Enable write limiting as well as read limiting. Now we sacrifice
14770 capacity if we're pushing out lots of directory traffic, rather
14771 than overrunning the user's intended bandwidth limits.
14772 - Include TLS overhead when counting bandwidth usage; previously, we
14773 would count only the bytes sent over TLS, but not the bytes used
14775 - Support running the Tor service with a torrc not in the same
14776 directory as tor.exe and default to using the torrc located in
14777 the %appdata%\Tor\ of the user who installed the service. Patch
14779 - Servers now check for the case when common DNS requests are going to
14780 wildcarded addresses (i.e. all getting the same answer), and change
14781 their exit policy to reject *:* if it's happening.
14782 - Implement BEGIN_DIR cells, so we can connect to the directory
14783 server via TLS to do encrypted directory requests rather than
14784 plaintext. Enable via the TunnelDirConns and PreferTunneledDirConns
14785 config options if you like.
14787 o Minor features (config and docs):
14788 - Start using the state file to store bandwidth accounting data:
14789 the bw_accounting file is now obsolete. We'll keep generating it
14790 for a while for people who are still using 0.1.2.4-alpha.
14791 - Try to batch changes to the state file so that we do as few
14792 disk writes as possible while still storing important things in
14794 - The state file and the bw_accounting file get saved less often when
14795 the AvoidDiskWrites config option is set.
14796 - Make PIDFile work on Windows (untested).
14797 - Add internal descriptions for a bunch of configuration options:
14798 accessible via controller interface and in comments in saved
14800 - Reject *:563 (NNTPS) in the default exit policy. We already reject
14801 NNTP by default, so this seems like a sensible addition.
14802 - Clients now reject hostnames with invalid characters. This should
14803 avoid some inadvertent info leaks. Add an option
14804 AllowNonRFC953Hostnames to disable this behavior, in case somebody
14805 is running a private network with hosts called @, !, and #.
14806 - Add a maintainer script to tell us which options are missing
14807 documentation: "make check-docs".
14808 - Add a new address-spec.txt document to describe our special-case
14809 addresses: .exit, .onion, and .noconnnect.
14811 o Minor features (DNS):
14812 - Ongoing work on eventdns infrastructure: now it has dns server
14813 and ipv6 support. One day Tor will make use of it.
14814 - Add client-side caching for reverse DNS lookups.
14815 - Add support to tor-resolve tool for reverse lookups and SOCKS5.
14816 - When we change nameservers or IP addresses, reset and re-launch
14817 our tests for DNS hijacking.
14819 o Minor features (directory):
14820 - Authorities now specify server versions in networkstatus. This adds
14821 about 2% to the size of compressed networkstatus docs, and allows
14822 clients to tell which servers support BEGIN_DIR and which don't.
14823 The implementation is forward-compatible with a proposed future
14824 protocol version scheme not tied to Tor versions.
14825 - DirServer configuration lines now have an orport= option so
14826 clients can open encrypted tunnels to the authorities without
14827 having downloaded their descriptors yet. Enabled for moria1,
14828 moria2, tor26, and lefkada now in the default configuration.
14829 - Directory servers are more willing to send a 503 "busy" if they
14830 are near their write limit, especially for v1 directory requests.
14831 Now they can use their limited bandwidth for actual Tor traffic.
14832 - Clients track responses with status 503 from dirservers. After a
14833 dirserver has given us a 503, we try not to use it until an hour has
14834 gone by, or until we have no dirservers that haven't given us a 503.
14835 - When we get a 503 from a directory, and we're not a server, we don't
14836 count the failure against the total number of failures allowed
14837 for the thing we're trying to download.
14838 - Report X-Your-Address-Is correctly from tunneled directory
14839 connections; don't report X-Your-Address-Is when it's an internal
14840 address; and never believe reported remote addresses when they're
14842 - Protect against an unlikely DoS attack on directory servers.
14843 - Add a BadDirectory flag to network status docs so that authorities
14844 can (eventually) tell clients about caches they believe to be
14847 o Minor features (controller):
14848 - Have GETINFO dir/status/* work on hosts with DirPort disabled.
14849 - Reimplement GETINFO so that info/names stays in sync with the
14851 - Implement "GETINFO fingerprint".
14852 - Implement "SETEVENTS GUARD" so controllers can get updates on
14853 entry guard status as it changes.
14855 o Minor features (clean up obsolete pieces):
14856 - Remove some options that have been deprecated since at least
14857 0.1.0.x: AccountingMaxKB, LogFile, DebugLogFile, LogLevel, and
14858 SysLog. Use AccountingMax instead of AccountingMaxKB, and use Log
14859 to set log options.
14860 - We no longer look for identity and onion keys in "identity.key" and
14861 "onion.key" -- these were replaced by secret_id_key and
14862 secret_onion_key in 0.0.8pre1.
14863 - We no longer require unrecognized directory entries to be
14866 o Major bugfixes (security):
14867 - Stop sending the HttpProxyAuthenticator string to directory
14868 servers when directory connections are tunnelled through Tor.
14869 - Clients no longer store bandwidth history in the state file.
14870 - Do not log introduction points for hidden services if SafeLogging
14872 - When generating bandwidth history, round down to the nearest
14873 1k. When storing accounting data, round up to the nearest 1k.
14874 - When we're running as a server, remember when we last rotated onion
14875 keys, so that we will rotate keys once they're a week old even if
14876 we never stay up for a week ourselves.
14878 o Major bugfixes (other):
14879 - Fix a longstanding bug in eventdns that prevented the count of
14880 timed-out resolves from ever being reset. This bug caused us to
14881 give up on a nameserver the third time it timed out, and try it
14882 10 seconds later... and to give up on it every time it timed out
14884 - Take out the '5 second' timeout from the connection retry
14885 schedule. Now the first connect attempt will wait a full 10
14886 seconds before switching to a new circuit. Perhaps this will help
14887 a lot. Based on observations from Mike Perry.
14888 - Fix a bug on the Windows implementation of tor_mmap_file() that
14889 would prevent the cached-routers file from ever loading. Reported
14893 - Fix an assert failure when a directory authority sets
14894 AuthDirRejectUnlisted and then receives a descriptor from an
14895 unlisted router. Reported by seeess.
14896 - Avoid a double-free when parsing malformed DirServer lines.
14897 - Fix a bug when a BSD-style PF socket is first used. Patch from
14899 - Fix a bug in 0.1.2.2-alpha that prevented clients from asking
14900 to resolve an address at a given exit node even when they ask for
14902 - Servers no longer ever list themselves in their "family" line,
14903 even if configured to do so. This makes it easier to configure
14904 family lists conveniently.
14905 - When running as a server, don't fall back to 127.0.0.1 when no
14906 nameservers are configured in /etc/resolv.conf; instead, make the
14907 user fix resolv.conf or specify nameservers explicitly. (Resolves
14909 - Stop accepting certain malformed ports in configured exit policies.
14910 - Don't re-write the fingerprint file every restart, unless it has
14912 - Stop warning when a single nameserver fails: only warn when _all_ of
14913 our nameservers have failed. Also, when we only have one nameserver,
14914 raise the threshold for deciding that the nameserver is dead.
14915 - Directory authorities now only decide that routers are reachable
14916 if their identity keys are as expected.
14917 - When the user uses bad syntax in the Log config line, stop
14918 suggesting other bad syntax as a replacement.
14919 - Correctly detect ipv6 DNS capability on OpenBSD.
14921 o Minor bugfixes (controller):
14922 - Report the circuit number correctly in STREAM CLOSED events. Bug
14923 reported by Mike Perry.
14924 - Do not report bizarre values for results of accounting GETINFOs
14925 when the last second's write or read exceeds the allotted bandwidth.
14926 - Report "unrecognized key" rather than an empty string when the
14927 controller tries to fetch a networkstatus that doesn't exist.
14930 Changes in version 0.1.1.26 - 2006-12-14
14931 o Security bugfixes:
14932 - Stop sending the HttpProxyAuthenticator string to directory
14933 servers when directory connections are tunnelled through Tor.
14934 - Clients no longer store bandwidth history in the state file.
14935 - Do not log introduction points for hidden services if SafeLogging
14939 - Fix an assert failure when a directory authority sets
14940 AuthDirRejectUnlisted and then receives a descriptor from an
14941 unlisted router (reported by seeess).
14944 Changes in version 0.1.2.4-alpha - 2006-12-03
14946 - Add support for using natd; this allows FreeBSDs earlier than
14947 5.1.2 to have ipfw send connections through Tor without using
14948 SOCKS. (Patch from Zajcev Evgeny with tweaks from tup.)
14951 - Make all connections to addresses of the form ".noconnect"
14952 immediately get closed. This lets application/controller combos
14953 successfully test whether they're talking to the same Tor by
14954 watching for STREAM events.
14955 - Make cross.sh cross-compilation script work even when autogen.sh
14956 hasn't been run. (Patch from Michael Mohr.)
14957 - Statistics dumped by -USR2 now include a breakdown of public key
14958 operations, for profiling.
14961 - Fix a major leak when directory authorities parse their
14962 approved-routers list, a minor memory leak when we fail to pick
14963 an exit node, and a few rare leaks on errors.
14964 - Handle TransPort connections even when the server sends data before
14965 the client sends data. Previously, the connection would just hang
14966 until the client sent data. (Patch from tup based on patch from
14968 - Avoid assert failure when our cached-routers file is empty on
14972 - Don't log spurious warnings when we see a circuit close reason we
14973 don't recognize; it's probably just from a newer version of Tor.
14974 - Have directory authorities allow larger amounts of drift in uptime
14975 without replacing the server descriptor: previously, a server that
14976 restarted every 30 minutes could have 48 "interesting" descriptors
14978 - Start linking to the Tor specification and Tor reference manual
14979 correctly in the Windows installer.
14980 - Add Vidalia to the OS X uninstaller script, so when we uninstall
14981 Tor/Privoxy we also uninstall Vidalia.
14982 - Resume building on Irix64, and fix a lot of warnings from its
14983 MIPSpro C compiler.
14984 - Don't corrupt last_guessed_ip in router_new_address_suggestion()
14985 when we're running as a client.
14988 Changes in version 0.1.1.25 - 2006-11-04
14990 - When a client asks us to resolve (rather than connect to)
14991 an address, and we have a cached answer, give them the cached
14992 answer. Previously, we would give them no answer at all.
14993 - We were building exactly the wrong circuits when we predict
14994 hidden service requirements, meaning Tor would have to build all
14995 its circuits on demand.
14996 - If none of our live entry guards have a high uptime, but we
14997 require a guard with a high uptime, try adding a new guard before
14998 we give up on the requirement. This patch should make long-lived
14999 connections more stable on average.
15000 - When testing reachability of our DirPort, don't launch new
15001 tests when there's already one in progress -- unreachable
15002 servers were stacking up dozens of testing streams.
15004 o Security bugfixes:
15005 - When the user sends a NEWNYM signal, clear the client-side DNS
15006 cache too. Otherwise we continue to act on previous information.
15009 - Avoid a memory corruption bug when creating a hash table for
15011 - Avoid possibility of controller-triggered crash when misusing
15012 certain commands from a v0 controller on platforms that do not
15013 handle printf("%s",NULL) gracefully.
15014 - Avoid infinite loop on unexpected controller input.
15015 - Don't log spurious warnings when we see a circuit close reason we
15016 don't recognize; it's probably just from a newer version of Tor.
15017 - Add Vidalia to the OS X uninstaller script, so when we uninstall
15018 Tor/Privoxy we also uninstall Vidalia.
15021 Changes in version 0.1.2.3-alpha - 2006-10-29
15023 - Prepare for servers to publish descriptors less often: never
15024 discard a descriptor simply for being too old until either it is
15025 recommended by no authorities, or until we get a better one for
15026 the same router. Make caches consider retaining old recommended
15027 routers for even longer.
15028 - If most authorities set a BadExit flag for a server, clients
15029 don't think of it as a general-purpose exit. Clients only consider
15030 authorities that advertise themselves as listing bad exits.
15031 - Directory servers now provide 'Pragma: no-cache' and 'Expires'
15032 headers for content, so that we can work better in the presence of
15033 caching HTTP proxies.
15034 - Allow authorities to list nodes as bad exits by fingerprint or by
15037 o Minor features, controller:
15038 - Add a REASON field to CIRC events; for backward compatibility, this
15039 field is sent only to controllers that have enabled the extended
15040 event format. Also, add additional reason codes to explain why
15041 a given circuit has been destroyed or truncated. (Patches from
15043 - Add a REMOTE_REASON field to extended CIRC events to tell the
15044 controller about why a remote OR told us to close a circuit.
15045 - Stream events also now have REASON and REMOTE_REASON fields,
15046 working much like those for circuit events.
15047 - There's now a GETINFO ns/... field so that controllers can ask Tor
15048 about the current status of a router.
15049 - A new event type "NS" to inform a controller when our opinion of
15050 a router's status has changed.
15051 - Add a GETINFO events/names and GETINFO features/names so controllers
15052 can tell which events and features are supported.
15053 - A new CLEARDNSCACHE signal to allow controllers to clear the
15054 client-side DNS cache without expiring circuits.
15056 o Security bugfixes:
15057 - When the user sends a NEWNYM signal, clear the client-side DNS
15058 cache too. Otherwise we continue to act on previous information.
15061 - Avoid sending junk to controllers or segfaulting when a controller
15062 uses EVENT_NEW_DESC with verbose nicknames.
15063 - Stop triggering asserts if the controller tries to extend hidden
15064 service circuits (reported by mwenge).
15065 - Avoid infinite loop on unexpected controller input.
15066 - When the controller does a "GETINFO network-status", tell it
15067 about even those routers whose descriptors are very old, and use
15068 long nicknames where appropriate.
15069 - Change NT service functions to be loaded on demand. This lets us
15070 build with MinGW without breaking Tor for Windows 98 users.
15071 - Do DirPort reachability tests less often, since a single test
15072 chews through many circuits before giving up.
15073 - In the hidden service example in torrc.sample, stop recommending
15074 esoteric and discouraged hidden service options.
15075 - When stopping an NT service, wait up to 10 sec for it to actually
15076 stop. Patch from Matt Edman; resolves bug 295.
15077 - Fix handling of verbose nicknames with ORCONN controller events:
15078 make them show up exactly when requested, rather than exactly when
15080 - When reporting verbose nicknames in entry_guards_getinfo(), avoid
15081 printing a duplicate "$" in the keys we send (reported by mwenge).
15082 - Correctly set maximum connection limit on Cygwin. (This time
15084 - Try to detect Windows correctly when cross-compiling.
15085 - Detect the size of the routers file correctly even if it is
15086 corrupted (on systems without mmap) or not page-aligned (on systems
15087 with mmap). This bug was harmless.
15088 - Sometimes we didn't bother sending a RELAY_END cell when an attempt
15089 to open a stream fails; now we do in more cases. This should
15090 make clients able to find a good exit faster in some cases, since
15091 unhandleable requests will now get an error rather than timing out.
15092 - Resolve two memory leaks when rebuilding the on-disk router cache
15093 (reported by fookoowa).
15094 - Clean up minor code warnings suggested by the MIPSpro C compiler,
15095 and reported by some Centos users.
15096 - Controller signals now work on non-Unix platforms that don't define
15097 SIGUSR1 and SIGUSR2 the way we expect.
15098 - Patch from Michael Mohr to contrib/cross.sh, so it checks more
15099 values before failing, and always enables eventdns.
15100 - Libevent-1.2 exports, but does not define in its headers, strlcpy.
15101 Try to fix this in configure.in by checking for most functions
15102 before we check for libevent.
15105 Changes in version 0.1.2.2-alpha - 2006-10-07
15107 - Make our async eventdns library on-by-default for Tor servers,
15108 and plan to deprecate the separate dnsworker threads.
15109 - Add server-side support for "reverse" DNS lookups (using PTR
15110 records so clients can determine the canonical hostname for a given
15111 IPv4 address). Only supported by servers using eventdns; servers
15112 now announce in their descriptors whether they support eventdns.
15113 - Specify and implement client-side SOCKS5 interface for reverse DNS
15114 lookups (see doc/socks-extensions.txt).
15115 - Add a BEGIN_DIR relay cell type for an easier in-protocol way to
15116 connect to directory servers through Tor. Previously, clients needed
15117 to find Tor exits to make private connections to directory servers.
15118 - Avoid choosing Exit nodes for entry or middle hops when the
15119 total bandwidth available from non-Exit nodes is much higher than
15120 the total bandwidth available from Exit nodes.
15121 - Workaround for name servers (like Earthlink's) that hijack failing
15122 DNS requests and replace the no-such-server answer with a "helpful"
15123 redirect to an advertising-driven search portal. Also work around
15124 DNS hijackers who "helpfully" decline to hijack known-invalid
15125 RFC2606 addresses. Config option "ServerDNSDetectHijacking 0"
15126 lets you turn it off.
15127 - Send out a burst of long-range padding cells once we've established
15128 that we're reachable. Spread them over 4 circuits, so hopefully
15129 a few will be fast. This exercises our bandwidth and bootstraps
15130 us into the directory more quickly.
15132 o New/improved config options:
15133 - Add new config option "ResolvConf" to let the server operator
15134 choose an alternate resolve.conf file when using eventdns.
15135 - Add an "EnforceDistinctSubnets" option to control our "exclude
15136 servers on the same /16" behavior. It's still on by default; this
15137 is mostly for people who want to operate private test networks with
15138 all the machines on the same subnet.
15139 - If one of our entry guards is on the ExcludeNodes list, or the
15140 directory authorities don't think it's a good guard, treat it as
15141 if it were unlisted: stop using it as a guard, and throw it off
15142 the guards list if it stays that way for a long time.
15143 - Allow directory authorities to be marked separately as authorities
15144 for the v1 directory protocol, the v2 directory protocol, and
15145 as hidden service directories, to make it easier to retire old
15146 authorities. V1 authorities should set "HSAuthoritativeDir 1"
15147 to continue being hidden service authorities too.
15148 - Remove 8888 as a LongLivedPort, and add 6697 (IRCS).
15150 o Minor features, controller:
15151 - Fix CIRC controller events so that controllers can learn the
15152 identity digests of non-Named servers used in circuit paths.
15153 - Let controllers ask for more useful identifiers for servers. Instead
15154 of learning identity digests for un-Named servers and nicknames
15155 for Named servers, the new identifiers include digest, nickname,
15156 and indication of Named status. Off by default; see control-spec.txt
15157 for more information.
15158 - Add a "getinfo address" controller command so it can display Tor's
15159 best guess to the user.
15160 - New controller event to alert the controller when our server
15161 descriptor has changed.
15162 - Give more meaningful errors on controller authentication failure.
15164 o Minor features, other:
15165 - When asked to resolve a hostname, don't use non-exit servers unless
15166 requested to do so. This allows servers with broken DNS to be
15167 useful to the network.
15168 - Divide eventdns log messages into warn and info messages.
15169 - Reserve the nickname "Unnamed" for routers that can't pick
15170 a hostname: any router can call itself Unnamed; directory
15171 authorities will never allocate Unnamed to any particular router;
15172 clients won't believe that any router is the canonical Unnamed.
15173 - Only include function names in log messages for info/debug messages.
15174 For notice/warn/err, the content of the message should be clear on
15175 its own, and printing the function name only confuses users.
15176 - Avoid some false positives during reachability testing: don't try
15177 to test via a server that's on the same /24 as us.
15178 - If we fail to build a circuit to an intended enclave, and it's
15179 not mandatory that we use that enclave, stop wanting it.
15180 - When eventdns is enabled, allow multithreaded builds on NetBSD and
15181 OpenBSD. (We had previously disabled threads on these platforms
15182 because they didn't have working thread-safe resolver functions.)
15184 o Major bugfixes, anonymity/security:
15185 - If a client asked for a server by name, and there's a named server
15186 in our network-status but we don't have its descriptor yet, we
15187 could return an unnamed server instead.
15188 - Fix NetBSD bug that could allow someone to force uninitialized RAM
15189 to be sent to a server's DNS resolver. This only affects NetBSD
15190 and other platforms that do not bounds-check tolower().
15191 - Reject (most) attempts to use Tor circuits with length one. (If
15192 many people start using Tor as a one-hop proxy, exit nodes become
15193 a more attractive target for compromise.)
15194 - Just because your DirPort is open doesn't mean people should be
15195 able to remotely teach you about hidden service descriptors. Now
15196 only accept rendezvous posts if you've got HSAuthoritativeDir set.
15198 o Major bugfixes, other:
15199 - Don't crash on race condition in dns.c: tor_assert(!resolve->expire)
15200 - When a client asks the server to resolve (not connect to)
15201 an address, and it has a cached answer, give them the cached answer.
15202 Previously, the server would give them no answer at all.
15203 - Allow really slow clients to not hang up five minutes into their
15204 directory downloads (suggested by Adam J. Richter).
15205 - We were building exactly the wrong circuits when we anticipated
15206 hidden service requirements, meaning Tor would have to build all
15207 its circuits on demand.
15208 - Avoid crashing when we mmap a router cache file of size 0.
15209 - When testing reachability of our DirPort, don't launch new
15210 tests when there's already one in progress -- unreachable
15211 servers were stacking up dozens of testing streams.
15213 o Minor bugfixes, correctness:
15214 - If we're a directory mirror and we ask for "all" network status
15215 documents, we would discard status documents from authorities
15216 we don't recognize.
15217 - Avoid a memory corruption bug when creating a hash table for
15219 - Avoid controller-triggered crash when misusing certain commands
15220 from a v0 controller on platforms that do not handle
15221 printf("%s",NULL) gracefully.
15222 - Don't crash when a controller sends a third argument to an
15223 "extendcircuit" request.
15224 - Controller protocol fixes: fix encoding in "getinfo addr-mappings"
15225 response; fix error code when "getinfo dir/status/" fails.
15226 - Avoid crash when telling controller stream-status and a stream
15228 - Patch from Adam Langley to fix assert() in eventdns.c.
15229 - Fix a debug log message in eventdns to say "X resolved to Y"
15230 instead of "X resolved to X".
15231 - Make eventdns give strings for DNS errors, not just error numbers.
15232 - Track unreachable entry guards correctly: don't conflate
15233 'unreachable by us right now' with 'listed as down by the directory
15234 authorities'. With the old code, if a guard was unreachable by
15235 us but listed as running, it would clog our guard list forever.
15236 - Behave correctly in case we ever have a network with more than
15237 2GB/s total advertised capacity.
15238 - Make TrackExitHosts case-insensitive, and fix the behavior of
15239 ".suffix" TrackExitHosts items to avoid matching in the middle of
15241 - Finally fix the openssl warnings from newer gccs that believe that
15242 ignoring a return value is okay, but casting a return value and
15243 then ignoring it is a sign of madness.
15244 - Prevent the contrib/exitlist script from printing the same
15245 result more than once.
15246 - Patch from Steve Hildrey: Generate network status correctly on
15247 non-versioning dirservers.
15248 - Don't listen to the X-Your-Address-Is hint if you did the lookup
15249 via Tor; otherwise you'll think you're the exit node's IP address.
15251 o Minor bugfixes, performance:
15252 - Two small performance improvements on parsing descriptors.
15253 - Major performance improvement on inserting descriptors: change
15254 algorithm from O(n^2) to O(n).
15255 - Make the common memory allocation path faster on machines where
15256 malloc(0) returns a pointer.
15257 - Start remembering X-Your-Address-Is directory hints even if you're
15258 a client, so you can become a server more smoothly.
15259 - Avoid duplicate entries on MyFamily line in server descriptor.
15261 o Packaging, features:
15262 - Remove architecture from OS X builds. The official builds are
15263 now universal binaries.
15264 - The Debian package now uses --verify-config when (re)starting,
15265 to distinguish configuration errors from other errors.
15266 - Update RPMs to require libevent 1.1b.
15268 o Packaging, bugfixes:
15269 - Patches so Tor builds with MinGW on Windows.
15270 - Patches so Tor might run on Cygwin again.
15271 - Resume building on non-gcc compilers and ancient gcc. Resume
15272 building with the -O0 compile flag. Resume building cleanly on
15274 - Run correctly on OS X platforms with case-sensitive filesystems.
15275 - Correct includes for net/if.h and net/pfvar.h on OpenBSD (from Tup).
15276 - Add autoconf checks so Tor can build on Solaris x86 again.
15279 - Documented (and renamed) ServerDNSSearchDomains and
15280 ServerDNSResolvConfFile options.
15281 - Be clearer that the *ListenAddress directives can be repeated
15285 Changes in version 0.1.1.24 - 2006-09-29
15287 - Allow really slow clients to not hang up five minutes into their
15288 directory downloads (suggested by Adam J. Richter).
15289 - Fix major performance regression from 0.1.0.x: instead of checking
15290 whether we have enough directory information every time we want to
15291 do something, only check when the directory information has changed.
15292 This should improve client CPU usage by 25-50%.
15293 - Don't crash if, after a server has been running for a while,
15294 it can't resolve its hostname.
15297 - Allow Tor to start when RunAsDaemon is set but no logs are set.
15298 - Don't crash when the controller receives a third argument to an
15299 "extendcircuit" request.
15300 - Controller protocol fixes: fix encoding in "getinfo addr-mappings"
15301 response; fix error code when "getinfo dir/status/" fails.
15302 - Fix configure.in to not produce broken configure files with
15303 more recent versions of autoconf. Thanks to Clint for his auto*
15305 - Fix security bug on NetBSD that could allow someone to force
15306 uninitialized RAM to be sent to a server's DNS resolver. This
15307 only affects NetBSD and other platforms that do not bounds-check
15309 - Warn user when using libevent 1.1a or earlier with win32 or kqueue
15310 methods: these are known to be buggy.
15311 - If we're a directory mirror and we ask for "all" network status
15312 documents, we would discard status documents from authorities
15313 we don't recognize.
15316 Changes in version 0.1.2.1-alpha - 2006-08-27
15318 - Add "eventdns" async dns library from Adam Langley, tweaked to
15319 build on OSX and Windows. Only enabled if you pass the
15320 --enable-eventdns argument to configure.
15321 - Allow servers with no hostname or IP address to learn their
15322 IP address by asking the directory authorities. This code only
15323 kicks in when you would normally have exited with a "no address"
15324 error. Nothing's authenticated, so use with care.
15325 - Rather than waiting a fixed amount of time between retrying
15326 application connections, we wait only 5 seconds for the first,
15327 10 seconds for the second, and 15 seconds for each retry after
15328 that. Hopefully this will improve the expected user experience.
15329 - Patch from Tup to add support for transparent AP connections:
15330 this basically bundles the functionality of trans-proxy-tor
15331 into the Tor mainline. Now hosts with compliant pf/netfilter
15332 implementations can redirect TCP connections straight to Tor
15333 without diverting through SOCKS. Needs docs.
15334 - Busy directory servers save lots of memory by spooling server
15335 descriptors, v1 directories, and v2 networkstatus docs to buffers
15336 as needed rather than en masse. Also mmap the cached-routers
15337 files, so we don't need to keep the whole thing in memory too.
15338 - Automatically avoid picking more than one node from the same
15339 /16 network when constructing a circuit.
15340 - Revise and clean up the torrc.sample that we ship with; add
15341 a section for BandwidthRate and BandwidthBurst.
15344 - Split circuit_t into origin_circuit_t and or_circuit_t, and
15345 split connection_t into edge, or, dir, control, and base structs.
15346 These will save quite a bit of memory on busy servers, and they'll
15347 also help us track down bugs in the code and bugs in the spec.
15348 - Experimentally re-enable kqueue on OSX when using libevent 1.1b
15349 or later. Log when we are doing this, so we can diagnose it when
15350 it fails. (Also, recommend libevent 1.1b for kqueue and
15351 win32 methods; deprecate libevent 1.0b harder; make libevent
15352 recommendation system saner.)
15353 - Start being able to build universal binaries on OS X (thanks
15355 - Export the default exit policy via the control port, so controllers
15356 don't need to guess what it is / will be later.
15357 - Add a man page entry for ProtocolWarnings.
15358 - Add TestVia config option to the man page.
15359 - Remove even more protocol-related warnings from Tor server logs,
15360 such as bad TLS handshakes and malformed begin cells.
15361 - Stop fetching descriptors if you're not a dir mirror and you
15362 haven't tried to establish any circuits lately. [This currently
15363 causes some dangerous behavior, because when you start up again
15364 you'll use your ancient server descriptors.]
15365 - New DirPort behavior: if you have your dirport set, you download
15366 descriptors aggressively like a directory mirror, whether or not
15367 your ORPort is set.
15368 - Get rid of the router_retry_connections notion. Now routers
15369 no longer try to rebuild long-term connections to directory
15370 authorities, and directory authorities no longer try to rebuild
15371 long-term connections to all servers. We still don't hang up
15372 connections in these two cases though -- we need to look at it
15373 more carefully to avoid flapping, and we likely need to wait til
15374 0.1.1.x is obsolete.
15375 - Drop compatibility with obsolete Tors that permit create cells
15376 to have the wrong circ_id_type.
15377 - Re-enable per-connection rate limiting. Get rid of the "OP
15378 bandwidth" concept. Lay groundwork for "bandwidth classes" --
15379 separate global buckets that apply depending on what sort of conn
15381 - Start publishing one minute or so after we find our ORPort
15382 to be reachable. This will help reduce the number of descriptors
15383 we have for ourselves floating around, since it's quite likely
15384 other things (e.g. DirPort) will change during that minute too.
15385 - Fork the v1 directory protocol into its own spec document,
15386 and mark dir-spec.txt as the currently correct (v2) spec.
15389 - When we find our DirPort to be reachable, publish a new descriptor
15390 so we'll tell the world (reported by pnx).
15391 - Publish a new descriptor after we hup/reload. This is important
15392 if our config has changed such that we'll want to start advertising
15393 our DirPort now, etc.
15394 - Allow Tor to start when RunAsDaemon is set but no logs are set.
15395 - When we have a state file we cannot parse, tell the user and
15396 move it aside. Now we avoid situations where the user starts
15397 Tor in 1904, Tor writes a state file with that timestamp in it,
15398 the user fixes her clock, and Tor refuses to start.
15399 - Fix configure.in to not produce broken configure files with
15400 more recent versions of autoconf. Thanks to Clint for his auto*
15402 - "tor --verify-config" now exits with -1(255) or 0 depending on
15403 whether the config options are bad or good.
15404 - Resolve bug 321 when using dnsworkers: append a period to every
15405 address we resolve at the exit node, so that we do not accidentally
15406 pick up local addresses, and so that failing searches are retried
15407 in the resolver search domains. (This is already solved for
15408 eventdns.) (This breaks Blossom servers for now.)
15409 - If we are using an exit enclave and we can't connect, e.g. because
15410 its webserver is misconfigured to not listen on localhost, then
15411 back off and try connecting from somewhere else before we fail.
15414 - Start compiling on MinGW on Windows (patches from Mike Chiussi).
15415 - Start compiling on MSVC6 on Windows (patches from Frediano Ziglio).
15416 - Fix bug 314: Tor clients issued "unsafe socks" warnings even
15417 when the IP address is mapped through MapAddress to a hostname.
15418 - Start passing "ipv4" hints to getaddrinfo(), so servers don't do
15419 useless IPv6 DNS resolves.
15420 - Patch suggested by Karsten Loesing: respond to SIGNAL command
15421 before we execute the signal, in case the signal shuts us down.
15422 - Clean up AllowInvalidNodes man page entry.
15423 - Claim a commonname of Tor, rather than TOR, in TLS handshakes.
15424 - Add more asserts to track down an assert error on a windows Tor
15425 server with connection_add being called with socket == -1.
15426 - Handle reporting OR_CONN_EVENT_NEW events to the controller.
15427 - Fix misleading log messages: an entry guard that is "unlisted",
15428 as well as not known to be "down" (because we've never heard
15429 of it), is not therefore "up".
15430 - Remove code to special-case "-cvs" ending, since it has not
15431 actually mattered since 0.0.9.
15432 - Make our socks5 handling more robust to broken socks clients:
15433 throw out everything waiting on the buffer in between socks
15434 handshake phases, since they can't possibly (so the theory
15435 goes) have predicted what we plan to respond to them.
15438 Changes in version 0.1.1.23 - 2006-07-30
15440 - Fast Tor servers, especially exit nodes, were triggering asserts
15441 due to a bug in handling the list of pending DNS resolves. Some
15442 bugs still remain here; we're hunting them.
15443 - Entry guards could crash clients by sending unexpected input.
15444 - More fixes on reachability testing: if you find yourself reachable,
15445 then don't ever make any client requests (so you stop predicting
15446 circuits), then hup or have your clock jump, then later your IP
15447 changes, you won't think circuits are working, so you won't try to
15448 test reachability, so you won't publish.
15451 - Avoid a crash if the controller does a resetconf firewallports
15452 and then a setconf fascistfirewall=1.
15453 - Avoid an integer underflow when the dir authority decides whether
15454 a router is stable: we might wrongly label it stable, and compute
15455 a slightly wrong median stability, when a descriptor is published
15457 - Fix a place where we might trigger an assert if we can't build our
15458 own server descriptor yet.
15461 Changes in version 0.1.1.22 - 2006-07-05
15463 - Fix a big bug that was causing servers to not find themselves
15464 reachable if they changed IP addresses. Since only 0.1.1.22+
15465 servers can do reachability testing correctly, now we automatically
15466 make sure to test via one of these.
15467 - Fix to allow clients and mirrors to learn directory info from
15468 descriptor downloads that get cut off partway through.
15469 - Directory authorities had a bug in deciding if a newly published
15470 descriptor was novel enough to make everybody want a copy -- a few
15471 servers seem to be publishing new descriptors many times a minute.
15473 - Fix a rare bug that was causing some servers to complain about
15474 "closing wedged cpuworkers" and skip some circuit create requests.
15475 - Make the Exit flag in directory status documents actually work.
15478 Changes in version 0.1.1.21 - 2006-06-10
15479 o Crash and assert fixes from 0.1.1.20:
15480 - Fix a rare crash on Tor servers that have enabled hibernation.
15481 - Fix a seg fault on startup for Tor networks that use only one
15482 directory authority.
15483 - Fix an assert from a race condition that occurs on Tor servers
15484 while exiting, where various threads are trying to log that they're
15485 exiting, and delete the logs, at the same time.
15486 - Make our unit tests pass again on certain obscure platforms.
15489 - Add support for building SUSE RPM packages.
15490 - Speed up initial bootstrapping for clients: if we are making our
15491 first ever connection to any entry guard, then don't mark it down
15493 - When only one Tor server in the network is labelled as a guard,
15494 and we've already picked him, we would cycle endlessly picking him
15495 again, being unhappy about it, etc. Now we specifically exclude
15496 current guards when picking a new guard.
15497 - Servers send create cells more reliably after the TLS connection
15498 is established: we were sometimes forgetting to send half of them
15499 when we had more than one pending.
15500 - If we get a create cell that asks us to extend somewhere, but the
15501 Tor server there doesn't match the expected digest, we now send
15502 a destroy cell back, rather than silently doing nothing.
15503 - Make options->RedirectExit work again.
15504 - Make cookie authentication for the controller work again.
15505 - Stop being picky about unusual characters in the arguments to
15506 mapaddress. It's none of our business.
15507 - Add a new config option "TestVia" that lets you specify preferred
15508 middle hops to use for test circuits. Perhaps this will let me
15509 debug the reachability problems better.
15511 o Log / documentation fixes:
15512 - If we're a server and some peer has a broken TLS certificate, don't
15513 log about it unless ProtocolWarnings is set, i.e., we want to hear
15514 about protocol violations by others.
15515 - Fix spelling of VirtualAddrNetwork in man page.
15516 - Add a better explanation at the top of the autogenerated torrc file
15517 about what happened to our old torrc.
15520 Changes in version 0.1.1.20 - 2006-05-23
15522 - Downgrade a log severity where servers complain that they're
15524 - Avoid a compile warning on FreeBSD.
15525 - Remove string size limit on NEWDESC messages; solve bug 291.
15526 - Correct the RunAsDaemon entry in the man page; ignore RunAsDaemon
15527 more thoroughly when we're running on windows.
15530 Changes in version 0.1.1.19-rc - 2006-05-03
15532 - Regenerate our local descriptor if it's dirty and we try to use
15533 it locally (e.g. if it changes during reachability detection).
15534 - If we setconf our ORPort to 0, we continued to listen on the
15535 old ORPort and receive connections.
15536 - Avoid a second warning about machine/limits.h on Debian
15538 - Be willing to add our own routerinfo into the routerlist.
15539 Now authorities will include themselves in their directories
15540 and network-statuses.
15541 - Stop trying to upload rendezvous descriptors to every
15542 directory authority: only try the v1 authorities.
15543 - Servers no longer complain when they think they're not
15544 registered with the directory authorities. There were too many
15546 - Backport dist-rpm changes so rpms can be built without errors.
15549 - Implement an option, VirtualAddrMask, to set which addresses
15550 get handed out in response to mapaddress requests. This works
15551 around a bug in tsocks where 127.0.0.0/8 is never socksified.
15554 Changes in version 0.1.1.18-rc - 2006-04-10
15556 - Work harder to download live network-statuses from all the
15557 directory authorities we know about. Improve the threshold
15558 decision logic so we're more robust to edge cases.
15559 - When fetching rendezvous descriptors, we were willing to ask
15560 v2 authorities too, which would always return 404.
15563 - Stop listing down or invalid nodes in the v1 directory. This will
15564 reduce its bulk by about 1/3, and reduce load on directory
15566 - When deciding whether a router is Fast or Guard-worthy, consider
15567 his advertised BandwidthRate and not just the BandwidthCapacity.
15568 - No longer ship INSTALL and README files -- they are useless now.
15569 - Force rpmbuild to behave and honor target_cpu.
15570 - Avoid warnings about machine/limits.h on Debian GNU/kFreeBSD.
15571 - Start to include translated versions of the tor-doc-*.html
15572 files, along with the screenshots. Still needs more work.
15573 - Start sending back 512 and 451 errors if mapaddress fails,
15574 rather than not sending anything back at all.
15575 - When we fail to bind or listen on an incoming or outgoing
15576 socket, we should close it before failing. otherwise we just
15577 leak it. (thanks to weasel for finding.)
15578 - Allow "getinfo dir/status/foo" to work, as long as your DirPort
15579 is enabled. (This is a hack, and will be fixed in 0.1.2.x.)
15580 - Make NoPublish (even though deprecated) work again.
15581 - Fix a minor security flaw where a versioning auth dirserver
15582 could list a recommended version many times in a row to make
15583 clients more convinced that it's recommended.
15584 - Fix crash bug if there are two unregistered servers running
15585 with the same nickname, one of them is down, and you ask for
15586 them by nickname in your EntryNodes or ExitNodes. Also, try
15587 to pick the one that's running rather than an arbitrary one.
15588 - Fix an infinite loop we could hit if we go offline for too long.
15589 - Complain when we hit WSAENOBUFS on recv() or write() too.
15590 Perhaps this will help us hunt the bug.
15591 - If you're not a versioning dirserver, don't put the string
15592 "client-versions \nserver-versions \n" in your network-status.
15593 - Lower the minimum required number of file descriptors to 1000,
15594 so we can have some overhead for Valgrind on Linux, where the
15595 default ulimit -n is 1024.
15598 - Add tor.dizum.com as the fifth authoritative directory server.
15599 - Add a new config option FetchUselessDescriptors, off by default,
15600 for when you plan to run "exitlist" on your client and you want
15601 to know about even the non-running descriptors.
15604 Changes in version 0.1.1.17-rc - 2006-03-28
15606 - Clients and servers since 0.1.1.10-alpha have been expiring
15607 connections whenever they are idle for 5 minutes and they *do*
15608 have circuits on them. Oops. With this new version, clients will
15609 discard their previous entry guard choices and avoid choosing
15610 entry guards running these flawed versions.
15611 - Fix memory leak when uncompressing concatenated zlib streams. This
15612 was causing substantial leaks over time on Tor servers.
15613 - The v1 directory was including servers as much as 48 hours old,
15614 because that's how the new routerlist->routers works. Now only
15615 include them if they're 20 hours old or less.
15618 - Resume building on irix64, netbsd 2.0, etc.
15619 - On non-gcc compilers (e.g. solaris), use "-g -O" instead of
15621 - Stop writing the "router.desc" file, ever. Nothing uses it anymore,
15622 and it is confusing some users.
15623 - Mirrors stop caching the v1 directory so often.
15624 - Make the max number of old descriptors that a cache will hold
15625 rise with the number of directory authorities, so we can scale.
15626 - Change our win32 uname() hack to be more forgiving about what
15627 win32 versions it thinks it's found.
15630 - Add lefkada.eecs.harvard.edu as a fourth authoritative directory
15632 - When the controller's *setconf commands fail, collect an error
15633 message in a string and hand it back to the controller.
15634 - Make the v2 dir's "Fast" flag based on relative capacity, just
15635 like "Stable" is based on median uptime. Name everything in the
15636 top 7/8 Fast, and only the top 1/2 gets to be a Guard.
15637 - Log server fingerprint on startup, so new server operators don't
15638 have to go hunting around their filesystem for it.
15639 - Return a robots.txt on our dirport to discourage google indexing.
15640 - Let the controller ask for GETINFO dir/status/foo so it can ask
15641 directly rather than connecting to the dir port. Only works when
15642 dirport is set for now.
15644 o New config options rather than constants in the code:
15645 - SocksTimeout: How long do we let a socks connection wait
15646 unattached before we fail it?
15647 - CircuitBuildTimeout: Cull non-open circuits that were born
15648 at least this many seconds ago.
15649 - CircuitIdleTimeout: Cull open clean circuits that were born
15650 at least this many seconds ago.
15653 Changes in version 0.1.1.16-rc - 2006-03-18
15654 o Bugfixes on 0.1.1.15-rc:
15655 - Fix assert when the controller asks to attachstream a connect-wait
15656 or resolve-wait stream.
15657 - Now do address rewriting when the controller asks us to attach
15658 to a particular circuit too. This will let Blossom specify
15659 "moria2.exit" without having to learn what moria2's IP address is.
15660 - Make the "tor --verify-config" command-line work again, so people
15661 can automatically check if their torrc will parse.
15662 - Authoritative dirservers no longer require an open connection from
15663 a server to consider him "reachable". We need this change because
15664 when we add new auth dirservers, old servers won't know not to
15666 - Let Tor build on Sun CC again.
15667 - Fix an off-by-one buffer size in dirserv.c that magically never
15668 hit our three authorities but broke sjmurdoch's own tor network.
15669 - If we as a directory mirror don't know of any v1 directory
15670 authorities, then don't try to cache any v1 directories.
15671 - Stop warning about unknown servers in our family when they are
15672 given as hex digests.
15673 - Stop complaining as quickly to the server operator that he
15674 hasn't registered his nickname/key binding.
15675 - Various cleanups so we can add new V2 Auth Dirservers.
15676 - Change "AllowUnverifiedNodes" to "AllowInvalidNodes", to
15677 reflect the updated flags in our v2 dir protocol.
15678 - Resume allowing non-printable characters for exit streams (both
15679 for connecting and for resolving). Now we tolerate applications
15680 that don't follow the RFCs. But continue to block malformed names
15683 o Bugfixes on 0.1.0.x:
15684 - Fix assert bug in close_logs(): when we close and delete logs,
15685 remove them all from the global "logfiles" list.
15686 - Fix minor integer overflow in calculating when we expect to use up
15687 our bandwidth allocation before hibernating.
15688 - Fix a couple of bugs in OpenSSL detection. Also, deal better when
15689 there are multiple SSLs installed with different versions.
15690 - When we try to be a server and Address is not explicitly set and
15691 our hostname resolves to a private IP address, try to use an
15692 interface address if it has a public address. Now Windows machines
15693 that think of themselves as localhost can work by default.
15696 - Let the controller ask for GETINFO dir/server/foo so it can ask
15697 directly rather than connecting to the dir port.
15698 - Let the controller tell us about certain router descriptors
15699 that it doesn't want Tor to use in circuits. Implement
15700 SETROUTERPURPOSE and modify +POSTDESCRIPTOR to do this.
15701 - New config option SafeSocks to reject all application connections
15702 using unsafe socks protocols. Defaults to off.
15705 Changes in version 0.1.1.15-rc - 2006-03-11
15706 o Bugfixes and cleanups:
15707 - When we're printing strings from the network, don't try to print
15708 non-printable characters. This protects us against shell escape
15709 sequence exploits, and also against attacks to fool humans into
15710 misreading their logs.
15711 - Fix a bug where Tor would fail to establish any connections if you
15712 left it off for 24 hours and then started it: we were happy with
15713 the obsolete network statuses, but they all referred to router
15714 descriptors that were too old to fetch, so we ended up with no
15715 valid router descriptors.
15716 - Fix a seg fault in the controller's "getinfo orconn-status"
15717 command while listing status on incoming handshaking connections.
15718 Introduce a status name "NEW" for these connections.
15719 - If we get a linelist or linelist_s config option from the torrc
15720 (e.g. ExitPolicy) and it has no value, warn and skip rather than
15721 silently resetting it to its default.
15722 - Don't abandon entry guards until they've been down or gone for
15724 - Cleaner and quieter log messages.
15727 - New controller signal NEWNYM that makes new application requests
15728 use clean circuits.
15729 - Add a new circuit purpose 'controller' to let the controller ask
15730 for a circuit that Tor won't try to use. Extend the EXTENDCIRCUIT
15731 controller command to let you specify the purpose if you're
15732 starting a new circuit. Add a new SETCIRCUITPURPOSE controller
15733 command to let you change a circuit's purpose after it's been
15735 - Accept "private:*" in routerdesc exit policies; not generated yet
15736 because older Tors do not understand it.
15737 - Add BSD-style contributed startup script "rc.subr" from Peter
15741 Changes in version 0.1.1.14-alpha - 2006-02-20
15742 o Bugfixes on 0.1.1.x:
15743 - Don't die if we ask for a stdout or stderr log (even implicitly)
15744 and we're set to RunAsDaemon -- just warn.
15745 - We still had a few bugs in the OR connection rotation code that
15746 caused directory servers to slowly aggregate connections to other
15747 fast Tor servers. This time for sure!
15748 - Make log entries on Win32 include the name of the function again.
15749 - We were treating a pair of exit policies if they were equal even
15750 if one said accept and the other said reject -- causing us to
15751 not always publish a new descriptor since we thought nothing
15753 - Retry pending server downloads as well as pending networkstatus
15754 downloads when we unexpectedly get a socks request.
15755 - We were ignoring the IS_FAST flag in the directory status,
15756 meaning we were willing to pick trivial-bandwidth nodes for "fast"
15758 - If the controller's SAVECONF command fails (e.g. due to file
15759 permissions), let the controller know that it failed.
15762 - If we're trying to be a Tor server and running Windows 95/98/ME
15763 as a server, explain that we'll likely crash.
15764 - When we're a server, a client asks for an old-style directory,
15765 and our write bucket is empty, don't give it to him. This way
15766 small servers can continue to serve the directory *sometimes*,
15767 without getting overloaded.
15768 - Compress exit policies even more -- look for duplicate lines
15770 - Clients now honor the "guard" flag in the router status when
15771 picking entry guards, rather than looking at is_fast or is_stable.
15772 - Retain unrecognized lines in $DATADIR/state file, so that we can
15773 be forward-compatible.
15774 - Generate 18.0.0.0/8 address policy format in descs when we can;
15775 warn when the mask is not reducible to a bit-prefix.
15776 - Let the user set ControlListenAddress in the torrc. This can be
15777 dangerous, but there are some cases (like a secured LAN) where it
15779 - Split ReachableAddresses into ReachableDirAddresses and
15780 ReachableORAddresses, so we can restrict Dir conns to port 80
15781 and OR conns to port 443.
15782 - Now we can target arch and OS in rpm builds (contributed by
15783 Phobos). Also make the resulting dist-rpm filename match the
15785 - New config options to help controllers: FetchServerDescriptors
15786 and FetchHidServDescriptors for whether to fetch server
15787 info and hidserv info or let the controller do it, and
15788 PublishServerDescriptor and PublishHidServDescriptors.
15789 - Also let the controller set the __AllDirActionsPrivate config
15790 option if you want all directory fetches/publishes to happen via
15791 Tor (it assumes your controller bootstraps your circuits).
15794 Changes in version 0.1.0.17 - 2006-02-17
15795 o Crash bugfixes on 0.1.0.x:
15796 - When servers with a non-zero DirPort came out of hibernation,
15797 sometimes they would trigger an assert.
15799 o Other important bugfixes:
15800 - On platforms that don't have getrlimit (like Windows), we were
15801 artificially constraining ourselves to a max of 1024
15802 connections. Now just assume that we can handle as many as 15000
15803 connections. Hopefully this won't cause other problems.
15805 o Backported features:
15806 - When we're a server, a client asks for an old-style directory,
15807 and our write bucket is empty, don't give it to him. This way
15808 small servers can continue to serve the directory *sometimes*,
15809 without getting overloaded.
15810 - Whenever you get a 503 in response to a directory fetch, try
15811 once more. This will become important once servers start sending
15812 503's whenever they feel busy.
15813 - Fetch a new directory every 120 minutes, not every 40 minutes.
15814 Now that we have hundreds of thousands of users running the old
15815 directory algorithm, it's starting to hurt a lot.
15816 - Bump up the period for forcing a hidden service descriptor upload
15817 from 20 minutes to 1 hour.
15820 Changes in version 0.1.1.13-alpha - 2006-02-09
15821 o Crashes in 0.1.1.x:
15822 - When you tried to setconf ORPort via the controller, Tor would
15823 crash. So people using TorCP to become a server were sad.
15824 - Solve (I hope) the stack-smashing bug that we were seeing on fast
15825 servers. The problem appears to be something do with OpenSSL's
15826 random number generation, or how we call it, or something. Let me
15827 know if the crashes continue.
15828 - Turn crypto hardware acceleration off by default, until we find
15829 somebody smart who can test it for us. (It appears to produce
15830 seg faults in at least some cases.)
15831 - Fix a rare assert error when we've tried all intro points for
15832 a hidden service and we try fetching the service descriptor again:
15833 "Assertion conn->state != AP_CONN_STATE_RENDDESC_WAIT failed"
15836 - Fix a major load balance bug: we were round-robining in 16 KB
15837 chunks, and servers with bandwidthrate of 20 KB, while downloading
15838 a 600 KB directory, would starve their other connections. Now we
15839 try to be a bit more fair.
15840 - Dir authorities and mirrors were never expiring the newest
15841 descriptor for each server, causing memory and directory bloat.
15842 - Fix memory-bloating and connection-bloating bug on servers: We
15843 were never closing any connection that had ever had a circuit on
15844 it, because we were checking conn->n_circuits == 0, yet we had a
15845 bug that let it go negative.
15846 - Make Tor work using squid as your http proxy again -- squid
15847 returns an error if you ask for a URL that's too long, and it uses
15848 a really generic error message. Plus, many people are behind a
15849 transparent squid so they don't even realize it.
15850 - On platforms that don't have getrlimit (like Windows), we were
15851 artificially constraining ourselves to a max of 1024
15852 connections. Now just assume that we can handle as many as 15000
15853 connections. Hopefully this won't cause other problems.
15854 - Add a new config option ExitPolicyRejectPrivate which defaults to
15855 1. This means all exit policies will begin with rejecting private
15856 addresses, unless the server operator explicitly turns it off.
15859 - Clients no longer download descriptors for non-running
15861 - Before we add new directory authorities, we should make it
15862 clear that only v1 authorities should receive/publish hidden
15863 service descriptors.
15866 - As soon as we've fetched some more directory info, immediately
15867 try to download more server descriptors. This way we don't have
15868 a 10 second pause during initial bootstrapping.
15869 - Remove even more loud log messages that the server operator can't
15871 - When we're running an obsolete or un-recommended version, make
15872 the log message more clear about what the problem is and what
15873 versions *are* still recommended.
15874 - Provide a more useful warn message when our onion queue gets full:
15875 the CPU is too slow or the exit policy is too liberal.
15876 - Don't warn when we receive a 503 from a dirserver/cache -- this
15877 will pave the way for them being able to refuse if they're busy.
15878 - When we fail to bind a listener, try to provide a more useful
15879 log message: e.g., "Is Tor already running?"
15880 - Adjust tor-spec to parameterize cell and key lengths. Now Ian
15881 Goldberg can prove things about our handshake protocol more
15883 - MaxConn has been obsolete for a while now. Document the ConnLimit
15884 config option, which is a *minimum* number of file descriptors
15885 that must be available else Tor refuses to start.
15886 - Apply Matt Ghali's --with-syslog-facility patch to ./configure
15887 if you log to syslog and want something other than LOG_DAEMON.
15888 - Make dirservers generate a separate "guard" flag to mean,
15889 "would make a good entry guard". Make clients parse it and vote
15890 on it. Not used by clients yet.
15891 - Implement --with-libevent-dir option to ./configure. Also, improve
15892 search techniques to find libevent, and use those for openssl too.
15893 - Bump the default bandwidthrate to 3 MB, and burst to 6 MB
15894 - Only start testing reachability once we've established a
15895 circuit. This will make startup on dirservers less noisy.
15896 - Don't try to upload hidden service descriptors until we have
15897 established a circuit.
15898 - Fix the controller's "attachstream 0" command to treat conn like
15899 it just connected, doing address remapping, handling .exit and
15900 .onion idioms, and so on. Now we're more uniform in making sure
15901 that the controller hears about new and closing connections.
15904 Changes in version 0.1.1.12-alpha - 2006-01-11
15905 o Bugfixes on 0.1.1.x:
15906 - The fix to close duplicate server connections was closing all
15907 Tor client connections if they didn't establish a circuit
15908 quickly enough. Oops.
15909 - Fix minor memory issue (double-free) that happened on exit.
15911 o Bugfixes on 0.1.0.x:
15912 - Tor didn't warn when it failed to open a log file.
15915 Changes in version 0.1.1.11-alpha - 2006-01-10
15916 o Crashes in 0.1.1.x:
15917 - Include all the assert/crash fixes from 0.1.0.16.
15918 - If you start Tor and then quit very quickly, there were some
15919 races that tried to free things that weren't allocated yet.
15920 - Fix a rare memory stomp if you're running hidden services.
15921 - Fix segfault when specifying DirServer in config without nickname.
15922 - Fix a seg fault when you finish connecting to a server but at
15923 that moment you dump his server descriptor.
15924 - Extendcircuit and Attachstream controller commands would
15925 assert/crash if you don't give them enough arguments.
15926 - Fix an assert error when we're out of space in the connection_list
15927 and we try to post a hidden service descriptor (reported by weasel).
15928 - If you specify a relative torrc path and you set RunAsDaemon in
15929 your torrc, then it chdir()'s to the new directory. If you HUP,
15930 it tries to load the new torrc location, fails, and exits.
15931 The fix: no longer allow a relative path to torrc using -f.
15934 - Implement "entry guards": automatically choose a handful of entry
15935 nodes and stick with them for all circuits. Only pick new guards
15936 when the ones you have are unsuitable, and if the old guards
15937 become suitable again, switch back. This will increase security
15938 dramatically against certain end-point attacks. The EntryNodes
15939 config option now provides some hints about which entry guards you
15940 want to use most; and StrictEntryNodes means to only use those.
15941 - New directory logic: download by descriptor digest, not by
15942 fingerprint. Caches try to download all listed digests from
15943 authorities; clients try to download "best" digests from caches.
15944 This avoids partitioning and isolating attacks better.
15945 - Make the "stable" router flag in network-status be the median of
15946 the uptimes of running valid servers, and make clients pay
15947 attention to the network-status flags. Thus the cutoff adapts
15948 to the stability of the network as a whole, making IRC, IM, etc
15949 connections more reliable.
15952 - Tor servers with dynamic IP addresses were needing to wait 18
15953 hours before they could start doing reachability testing using
15954 the new IP address and ports. This is because they were using
15955 the internal descriptor to learn what to test, yet they were only
15956 rebuilding the descriptor once they decided they were reachable.
15957 - Tor 0.1.1.9 and 0.1.1.10 had a serious bug that caused clients
15958 to download certain server descriptors, throw them away, and then
15959 fetch them again after 30 minutes. Now mirrors throw away these
15960 server descriptors so clients can't get them.
15961 - We were leaving duplicate connections to other ORs open for a week,
15962 rather than closing them once we detect a duplicate. This only
15963 really affected authdirservers, but it affected them a lot.
15964 - Spread the authdirservers' reachability testing over the entire
15965 testing interval, so we don't try to do 500 TLS's at once every
15969 - If the network is down, and we try to connect to a conn because
15970 we have a circuit in mind, and we timeout (30 seconds) because the
15971 network never answers, we were expiring the circuit, but we weren't
15972 obsoleting the connection or telling the entry_guards functions.
15973 - Some Tor servers process billions of cells per day. These statistics
15974 need to be uint64_t's.
15975 - Check for integer overflows in more places, when adding elements
15976 to smartlists. This could possibly prevent a buffer overflow
15977 on malicious huge inputs. I don't see any, but I haven't looked
15979 - ReachableAddresses kept growing new "reject *:*" lines on every
15981 - When you "setconf log" via the controller, it should remove all
15982 logs. We were automatically adding back in a "log notice stdout".
15983 - Newly bootstrapped Tor networks couldn't establish hidden service
15984 circuits until they had nodes with high uptime. Be more tolerant.
15985 - We were marking servers down when they could not answer every piece
15986 of the directory request we sent them. This was far too harsh.
15987 - Fix the torify (tsocks) config file to not use Tor for localhost
15989 - Directory authorities now go to the proper authority when asking for
15990 a networkstatus, even when they want a compressed one.
15991 - Fix a harmless bug that was causing Tor servers to log
15992 "Got an end because of misc error, but we're not an AP. Closing."
15993 - Authorities were treating their own descriptor changes as cosmetic,
15994 meaning the descriptor available in the network-status and the
15995 descriptor that clients downloaded were different.
15996 - The OS X installer was adding a symlink for tor_resolve but
15997 the binary was called tor-resolve (reported by Thomas Hardly).
15998 - Workaround a problem with some http proxies where they refuse GET
15999 requests that specify "Content-Length: 0" (reported by Adrian).
16000 - Fix wrong log message when you add a "HiddenServiceNodes" config
16001 line without any HiddenServiceDir line (reported by Chris Thomas).
16004 - Write the TorVersion into the state file so we have a prayer of
16005 keeping forward and backward compatibility.
16006 - Revive the FascistFirewall config option rather than eliminating it:
16007 now it's a synonym for ReachableAddresses *:80,*:443.
16008 - Clients choose directory servers from the network status lists,
16009 not from their internal list of router descriptors. Now they can
16010 go to caches directly rather than needing to go to authorities
16012 - Directory authorities ignore router descriptors that have only
16013 cosmetic differences: do this for 0.1.0.x servers now too.
16014 - Add a new flag to network-status indicating whether the server
16015 can answer v2 directory requests too.
16016 - Authdirs now stop whining so loudly about bad descriptors that
16017 they fetch from other dirservers. So when there's a log complaint,
16018 it's for sure from a freshly uploaded descriptor.
16019 - Reduce memory requirements in our structs by changing the order
16021 - There used to be two ways to specify your listening ports in a
16022 server descriptor: on the "router" line and with a separate "ports"
16023 line. Remove support for the "ports" line.
16024 - New config option "AuthDirRejectUnlisted" for auth dirservers as
16025 a panic button: if we get flooded with unusable servers we can
16026 revert to only listing servers in the approved-routers file.
16027 - Auth dir servers can now mark a fingerprint as "!reject" or
16028 "!invalid" in the approved-routers file (as its nickname), to
16029 refuse descriptors outright or include them but marked as invalid.
16030 - Servers store bandwidth history across restarts/crashes.
16031 - Add reasons to DESTROY and RELAY_TRUNCATED cells, so clients can
16032 get a better idea of why their circuits failed. Not used yet.
16033 - Directory mirrors now cache up to 16 unrecognized network-status
16034 docs. Now we can add new authdirservers and they'll be cached too.
16035 - When picking a random directory, prefer non-authorities if any
16037 - New controller option "getinfo desc/all-recent" to fetch the
16038 latest server descriptor for every router that Tor knows about.
16041 Changes in version 0.1.0.16 - 2006-01-02
16042 o Crash bugfixes on 0.1.0.x:
16043 - On Windows, build with a libevent patch from "I-M Weasel" to avoid
16044 corrupting the heap, losing FDs, or crashing when we need to resize
16045 the fd_sets. (This affects the Win32 binaries, not Tor's sources.)
16046 - It turns out sparc64 platforms crash on unaligned memory access
16047 too -- so detect and avoid this.
16048 - Handle truncated compressed data correctly (by detecting it and
16050 - Fix possible-but-unlikely free(NULL) in control.c.
16051 - When we were closing connections, there was a rare case that
16052 stomped on memory, triggering seg faults and asserts.
16053 - Avoid potential infinite recursion when building a descriptor. (We
16054 don't know that it ever happened, but better to fix it anyway.)
16055 - We were neglecting to unlink marked circuits from soon-to-close OR
16056 connections, which caused some rare scribbling on freed memory.
16057 - Fix a memory stomping race bug when closing the joining point of two
16058 rendezvous circuits.
16059 - Fix an assert in time parsing found by Steven Murdoch.
16061 o Other bugfixes on 0.1.0.x:
16062 - When we're doing reachability testing, provide more useful log
16063 messages so the operator knows what to expect.
16064 - Do not check whether DirPort is reachable when we are suppressing
16065 advertising it because of hibernation.
16066 - When building with -static or on Solaris, we sometimes needed -ldl.
16067 - When we're deciding whether a stream has enough circuits around
16068 that can handle it, count the freshly dirty ones and not the ones
16069 that are so dirty they won't be able to handle it.
16070 - When we're expiring old circuits, we had a logic error that caused
16071 us to close new rendezvous circuits rather than old ones.
16072 - Give a more helpful log message when you try to change ORPort via
16073 the controller: you should upgrade Tor if you want that to work.
16074 - We were failing to parse Tor versions that start with "Tor ".
16075 - Tolerate faulty streams better: when a stream fails for reason
16076 exitpolicy, stop assuming that the router is lying about his exit
16077 policy. When a stream fails for reason misc, allow it to retry just
16078 as if it was resolvefailed. When a stream has failed three times,
16079 reset its failure count so we can try again and get all three tries.
16082 Changes in version 0.1.1.10-alpha - 2005-12-11
16083 o Correctness bugfixes on 0.1.0.x:
16084 - On Windows, build with a libevent patch from "I-M Weasel" to avoid
16085 corrupting the heap, losing FDs, or crashing when we need to resize
16086 the fd_sets. (This affects the Win32 binaries, not Tor's sources.)
16087 - Stop doing the complex voodoo overkill checking for insecure
16088 Diffie-Hellman keys. Just check if it's in [2,p-2] and be happy.
16089 - When we were closing connections, there was a rare case that
16090 stomped on memory, triggering seg faults and asserts.
16091 - We were neglecting to unlink marked circuits from soon-to-close OR
16092 connections, which caused some rare scribbling on freed memory.
16093 - When we're deciding whether a stream has enough circuits around
16094 that can handle it, count the freshly dirty ones and not the ones
16095 that are so dirty they won't be able to handle it.
16096 - Recover better from TCP connections to Tor servers that are
16097 broken but don't tell you (it happens!); and rotate TLS
16098 connections once a week.
16099 - When we're expiring old circuits, we had a logic error that caused
16100 us to close new rendezvous circuits rather than old ones.
16101 - Fix a scary-looking but apparently harmless bug where circuits
16102 would sometimes start out in state CIRCUIT_STATE_OR_WAIT at
16103 servers, and never switch to state CIRCUIT_STATE_OPEN.
16104 - When building with -static or on Solaris, we sometimes needed to
16106 - Give a useful message when people run Tor as the wrong user,
16107 rather than telling them to start chowning random directories.
16108 - We were failing to inform the controller about new .onion streams.
16110 o Security bugfixes on 0.1.0.x:
16111 - Refuse server descriptors if the fingerprint line doesn't match
16112 the included identity key. Tor doesn't care, but other apps (and
16113 humans) might actually be trusting the fingerprint line.
16114 - We used to kill the circuit when we receive a relay command we
16115 don't recognize. Now we just drop it.
16116 - Start obeying our firewall options more rigorously:
16117 . If we can't get to a dirserver directly, try going via Tor.
16118 . Don't ever try to connect (as a client) to a place our
16119 firewall options forbid.
16120 . If we specify a proxy and also firewall options, obey the
16121 firewall options even when we're using the proxy: some proxies
16122 can only proxy to certain destinations.
16123 - Fix a bug found by Lasse Overlier: when we were making internal
16124 circuits (intended to be cannibalized later for rendezvous and
16125 introduction circuits), we were picking them so that they had
16126 useful exit nodes. There was no need for this, and it actually
16127 aids some statistical attacks.
16128 - Start treating internal circuits and exit circuits separately.
16129 It's important to keep them separate because internal circuits
16130 have their last hops picked like middle hops, rather than like
16131 exit hops. So exiting on them will break the user's expectations.
16133 o Bugfixes on 0.1.1.x:
16134 - Take out the mis-feature where we tried to detect IP address
16135 flapping for people with DynDNS, and chose not to upload a new
16136 server descriptor sometimes.
16137 - Try to be compatible with OpenSSL 0.9.6 again.
16138 - Log fix: when the controller is logging about .onion addresses,
16139 sometimes it didn't include the ".onion" part of the address.
16140 - Don't try to modify options->DirServers internally -- if the
16141 user didn't specify any, just add the default ones directly to
16142 the trusted dirserver list. This fixes a bug where people running
16143 controllers would use SETCONF on some totally unrelated config
16144 option, and Tor would start yelling at them about changing their
16146 - Let the controller's redirectstream command specify a port, in
16147 case the controller wants to change that too.
16148 - When we requested a pile of server descriptors, we sometimes
16149 accidentally launched a duplicate request for the first one.
16150 - Bugfix for trackhostexits: write down the fingerprint of the
16151 chosen exit, not its nickname, because the chosen exit might not
16153 - When parsing foo.exit, if foo is unknown, and we are leaving
16154 circuits unattached, set the chosen_exit field and leave the
16155 address empty. This matters because controllers got confused
16157 - Directory authorities no longer try to download server
16158 descriptors that they know they will reject.
16160 o Features and updates:
16161 - Replace balanced trees with hash tables: this should make stuff
16162 significantly faster.
16163 - Resume using the AES counter-mode implementation that we ship,
16164 rather than OpenSSL's. Ours is significantly faster.
16165 - Many other CPU and memory improvements.
16166 - Add a new config option FastFirstHopPK (on by default) so clients
16167 do a trivial crypto handshake for their first hop, since TLS has
16168 already taken care of confidentiality and authentication.
16169 - Add a new config option TestSocks so people can see if their
16170 applications are using socks4, socks4a, socks5-with-ip, or
16171 socks5-with-hostname. This way they don't have to keep mucking
16172 with tcpdump and wondering if something got cached somewhere.
16173 - Warn when listening on a public address for socks. I suspect a
16174 lot of people are setting themselves up as open socks proxies,
16175 and they have no idea that jerks on the Internet are using them,
16176 since they simply proxy the traffic into the Tor network.
16177 - Add "private:*" as an alias in configuration for policies. Now
16178 you can simplify your exit policy rather than needing to list
16179 every single internal or nonroutable network space.
16180 - Add a new controller event type that allows controllers to get
16181 all server descriptors that were uploaded to a router in its role
16182 as authoritative dirserver.
16183 - Start shipping socks-extensions.txt, tor-doc-unix.html,
16184 tor-doc-server.html, and stylesheet.css in the tarball.
16185 - Stop shipping tor-doc.html in the tarball.
16188 Changes in version 0.1.1.9-alpha - 2005-11-15
16189 o Usability improvements:
16190 - Start calling it FooListenAddress rather than FooBindAddress,
16191 since few of our users know what it means to bind an address
16193 - Reduce clutter in server logs. We're going to try to make
16194 them actually usable now. New config option ProtocolWarnings that
16195 lets you hear about how _other Tors_ are breaking the protocol. Off
16197 - Divide log messages into logging domains. Once we put some sort
16198 of interface on this, it will let people looking at more verbose
16199 log levels specify the topics they want to hear more about.
16200 - Make directory servers return better http 404 error messages
16201 instead of a generic "Servers unavailable".
16202 - Check for even more Windows version flags when writing the platform
16203 string in server descriptors, and note any we don't recognize.
16204 - Clean up more of the OpenSSL memory when exiting, so we can detect
16205 memory leaks better.
16206 - Make directory authorities be non-versioning, non-naming by
16207 default. Now we can add new directory servers without requiring
16208 their operators to pay close attention.
16209 - When logging via syslog, include the pid whenever we provide
16210 a log entry. Suggested by Todd Fries.
16212 o Performance improvements:
16213 - Directory servers now silently throw away new descriptors that
16214 haven't changed much if the timestamps are similar. We do this to
16215 tolerate older Tor servers that upload a new descriptor every 15
16216 minutes. (It seemed like a good idea at the time.)
16217 - Inline bottleneck smartlist functions; use fast versions by default.
16218 - Add a "Map from digest to void*" abstraction digestmap_t so we
16219 can do less hex encoding/decoding. Use it in router_get_by_digest()
16220 to resolve a performance bottleneck.
16221 - Allow tor_gzip_uncompress to extract as much as possible from
16222 truncated compressed data. Try to extract as many
16223 descriptors as possible from truncated http responses (when
16224 DIR_PURPOSE_FETCH_ROUTERDESC).
16225 - Make circ->onionskin a pointer, not a static array. moria2 was using
16226 125000 circuit_t's after it had been up for a few weeks, which
16227 translates to 20+ megs of wasted space.
16228 - The private half of our EDH handshake keys are now chosen out
16229 of 320 bits, not 1024 bits. (Suggested by Ian Goldberg.)
16231 o Security improvements:
16232 - Start making directory caches retain old routerinfos, so soon
16233 clients can start asking by digest of descriptor rather than by
16234 fingerprint of server.
16235 - Add half our entropy from RAND_poll in OpenSSL. This knows how
16236 to use egd (if present), openbsd weirdness (if present), vms/os2
16237 weirdness (if we ever port there), and more in the future.
16239 o Bugfixes on 0.1.0.x:
16240 - Do round-robin writes of at most 16 kB per write. This might be
16241 more fair on loaded Tor servers, and it might resolve our Windows
16242 crash bug. It might also slow things down.
16243 - Our TLS handshakes were generating a single public/private
16244 keypair for the TLS context, rather than making a new one for
16245 each new connections. Oops. (But we were still rotating them
16246 periodically, so it's not so bad.)
16247 - When we were cannibalizing a circuit with a particular exit
16248 node in mind, we weren't checking to see if that exit node was
16249 already present earlier in the circuit. Oops.
16250 - When a Tor server's IP changes (e.g. from a dyndns address),
16251 upload a new descriptor so clients will learn too.
16252 - Really busy servers were keeping enough circuits open on stable
16253 connections that they were wrapping around the circuit_id
16254 space. (It's only two bytes.) This exposed a bug where we would
16255 feel free to reuse a circuit_id even if it still exists but has
16256 been marked for close. Try to fix this bug. Some bug remains.
16257 - If we would close a stream early (e.g. it asks for a .exit that
16258 we know would refuse it) but the LeaveStreamsUnattached config
16259 option is set by the controller, then don't close it.
16261 o Bugfixes on 0.1.1.8-alpha:
16262 - Fix a big pile of memory leaks, some of them serious.
16263 - Do not try to download a routerdesc if we would immediately reject
16265 - Resume inserting a newline between all router descriptors when
16266 generating (old style) signed directories, since our spec says
16268 - When providing content-type application/octet-stream for
16269 server descriptors using .z, we were leaving out the
16270 content-encoding header. Oops. (Everything tolerated this just
16271 fine, but that doesn't mean we need to be part of the problem.)
16272 - Fix a potential seg fault in getconf and getinfo using version 1
16273 of the controller protocol.
16274 - Avoid crash: do not check whether DirPort is reachable when we
16275 are suppressing it because of hibernation.
16276 - Make --hash-password not crash on exit.
16279 Changes in version 0.1.1.8-alpha - 2005-10-07
16280 o New features (major):
16281 - Clients don't download or use the directory anymore. Now they
16282 download and use network-statuses from the trusted dirservers,
16283 and fetch individual server descriptors as needed from mirrors.
16284 See dir-spec.txt for all the gory details.
16285 - Be more conservative about whether to advertise our DirPort.
16286 The main change is to not advertise if we're running at capacity
16287 and either a) we could hibernate or b) our capacity is low and
16288 we're using a default DirPort.
16289 - Use OpenSSL's AES when OpenSSL has version 0.9.7 or later.
16291 o New features (minor):
16292 - Try to be smart about when to retry network-status and
16293 server-descriptor fetches. Still needs some tuning.
16294 - Stop parsing, storing, or using running-routers output (but
16295 mirrors still cache and serve it).
16296 - Consider a threshold of versioning dirservers (dirservers who have
16297 an opinion about which Tor versions are still recommended) before
16298 deciding whether to warn the user that he's obsolete.
16299 - Dirservers can now reject/invalidate by key and IP, with the
16300 config options "AuthDirInvalid" and "AuthDirReject". This is
16301 useful since currently we automatically list servers as running
16302 and usable even if we know they're jerks.
16303 - Provide dire warnings to any users who set DirServer; move it out
16304 of torrc.sample and into torrc.complete.
16305 - Add MyFamily to torrc.sample in the server section.
16306 - Add nicknames to the DirServer line, so we can refer to them
16307 without requiring all our users to memorize their IP addresses.
16308 - When we get an EOF or a timeout on a directory connection, note
16309 how many bytes of serverdesc we are dropping. This will help
16310 us determine whether it is smart to parse incomplete serverdesc
16312 - Add a new function to "change pseudonyms" -- that is, to stop
16313 using any currently-dirty circuits for new streams, so we don't
16314 link new actions to old actions. Currently it's only called on
16315 HUP (or SIGNAL RELOAD).
16316 - On sighup, if UseHelperNodes changed to 1, use new circuits.
16317 - Start using RAND_bytes rather than RAND_pseudo_bytes from
16318 OpenSSL. Also, reseed our entropy every hour, not just at
16319 startup. And entropy in 512-bit chunks, not 160-bit chunks.
16321 o Fixes on 0.1.1.7-alpha:
16322 - Nobody ever implemented EVENT_ADDRMAP for control protocol
16323 version 0, so don't let version 0 controllers ask for it.
16324 - If you requested something with too many newlines via the
16325 v1 controller protocol, you could crash tor.
16326 - Fix a number of memory leaks, including some pretty serious ones.
16327 - Re-enable DirPort testing again, so Tor servers will be willing
16328 to advertise their DirPort if it's reachable.
16329 - On TLS handshake, only check the other router's nickname against
16330 its expected nickname if is_named is set.
16332 o Fixes forward-ported from 0.1.0.15:
16333 - Don't crash when we don't have any spare file descriptors and we
16334 try to spawn a dns or cpu worker.
16335 - Make the numbers in read-history and write-history into uint64s,
16336 so they don't overflow and publish negatives in the descriptor.
16338 o Fixes on 0.1.0.x:
16339 - For the OS X package's modified privoxy config file, comment
16340 out the "logfile" line so we don't log everything passed
16342 - We were whining about using socks4 or socks5-with-local-lookup
16343 even when it's an IP in the "virtual" range we designed exactly
16345 - We were leaking some memory every time the client changes IPs.
16346 - Never call free() on tor_malloc()d memory. This will help us
16347 use dmalloc to detect memory leaks.
16348 - Check for named servers when looking them up by nickname;
16349 warn when we'recalling a non-named server by its nickname;
16350 don't warn twice about the same name.
16351 - Try to list MyFamily elements by key, not by nickname, and warn
16352 if we've not heard of the server.
16353 - Make windows platform detection (uname equivalent) smarter.
16354 - It turns out sparc64 doesn't like unaligned access either.
16357 Changes in version 0.1.0.15 - 2005-09-23
16358 o Bugfixes on 0.1.0.x:
16359 - Reject ports 465 and 587 (spam targets) in default exit policy.
16360 - Don't crash when we don't have any spare file descriptors and we
16361 try to spawn a dns or cpu worker.
16362 - Get rid of IgnoreVersion undocumented config option, and make us
16363 only warn, never exit, when we're running an obsolete version.
16364 - Don't try to print a null string when your server finds itself to
16365 be unreachable and the Address config option is empty.
16366 - Make the numbers in read-history and write-history into uint64s,
16367 so they don't overflow and publish negatives in the descriptor.
16368 - Fix a minor memory leak in smartlist_string_remove().
16369 - We were only allowing ourselves to upload a server descriptor at
16370 most every 20 minutes, even if it changed earlier than that.
16371 - Clean up log entries that pointed to old URLs.
16374 Changes in version 0.1.1.7-alpha - 2005-09-14
16375 o Fixes on 0.1.1.6-alpha:
16376 - Exit servers were crashing when people asked them to make a
16377 connection to an address not in their exit policy.
16378 - Looking up a non-existent stream for a v1 control connection would
16380 - Fix a seg fault if we ask a dirserver for a descriptor by
16381 fingerprint but he doesn't know about him.
16382 - SETCONF was appending items to linelists, not clearing them.
16383 - SETCONF SocksBindAddress killed Tor if it fails to bind. Now back
16384 out and refuse the setconf if it would fail.
16385 - Downgrade the dirserver log messages when whining about
16389 - Add Peter Palfrader's check-tor script to tor/contrib/
16390 It lets you easily check whether a given server (referenced by
16391 nickname) is reachable by you.
16392 - Numerous changes to move towards client-side v2 directories. Not
16395 o Fixes on 0.1.0.x:
16396 - If the user gave tor an odd number of command-line arguments,
16397 we were silently ignoring the last one. Now we complain and fail.
16398 [This wins the oldest-bug prize -- this bug has been present since
16399 November 2002, as released in Tor 0.0.0.]
16400 - Do not use unaligned memory access on alpha, mips, or mipsel.
16401 It *works*, but is very slow, so we treat them as if it doesn't.
16402 - Retry directory requests if we fail to get an answer we like
16403 from a given dirserver (we were retrying before, but only if
16404 we fail to connect).
16405 - When writing the RecommendedVersions line, sort them first.
16406 - When the client asked for a rendezvous port that the hidden
16407 service didn't want to provide, we were sending an IP address
16408 back along with the end cell. Fortunately, it was zero. But stop
16410 - Correct "your server is reachable" log entries to indicate that
16411 it was self-testing that told us so.
16414 Changes in version 0.1.1.6-alpha - 2005-09-09
16415 o Fixes on 0.1.1.5-alpha:
16416 - We broke fascistfirewall in 0.1.1.5-alpha. Oops.
16417 - Fix segfault in unit tests in 0.1.1.5-alpha. Oops.
16418 - Fix bug with tor_memmem finding a match at the end of the string.
16419 - Make unit tests run without segfaulting.
16420 - Resolve some solaris x86 compile warnings.
16421 - Handle duplicate lines in approved-routers files without warning.
16422 - Fix bug where as soon as a server refused any requests due to his
16423 exit policy (e.g. when we ask for localhost and he tells us that's
16424 127.0.0.1 and he won't do it), we decided he wasn't obeying his
16425 exit policy using him for any exits.
16426 - Only do openssl hardware accelerator stuff if openssl version is
16429 o New controller features/fixes:
16430 - Add a "RESETCONF" command so you can set config options like
16431 AllowUnverifiedNodes and LongLivedPorts to "". Also, if you give
16432 a config option in the torrc with no value, then it clears it
16433 entirely (rather than setting it to its default).
16434 - Add a "GETINFO config-file" to tell us where torrc is.
16435 - Avoid sending blank lines when GETINFO replies should be empty.
16436 - Add a QUIT command for the controller (for using it manually).
16437 - Fix a bug in SAVECONF that was adding default dirservers and
16438 other redundant entries to the torrc file.
16440 o Start on the new directory design:
16441 - Generate, publish, cache, serve new network-status format.
16442 - Publish individual descriptors (by fingerprint, by "all", and by
16444 - Publish client and server recommended versions separately.
16445 - Allow tor_gzip_uncompress() to handle multiple concatenated
16446 compressed strings. Serve compressed groups of router
16447 descriptors. The compression logic here could be more
16449 - Distinguish v1 authorities (all currently trusted directories)
16450 from v2 authorities (all trusted directories).
16451 - Change DirServers config line to note which dirs are v1 authorities.
16452 - Add configuration option "V1AuthoritativeDirectory 1" which
16453 moria1, moria2, and tor26 should set.
16454 - Remove option when getting directory cache to see whether they
16455 support running-routers; they all do now. Replace it with one
16456 to see whether caches support v2 stuff.
16459 - Dirservers now do their own external reachability testing of each
16460 Tor server, and only list them as running if they've been found to
16461 be reachable. We also send back warnings to the server's logs if
16462 it uploads a descriptor that we already believe is unreachable.
16463 - Implement exit enclaves: if we know an IP address for the
16464 destination, and there's a running Tor server at that address
16465 which allows exit to the destination, then extend the circuit to
16466 that exit first. This provides end-to-end encryption and end-to-end
16467 authentication. Also, if the user wants a .exit address or enclave,
16468 use 4 hops rather than 3, and cannibalize a general circ for it
16470 - Permit transitioning from ORPort=0 to ORPort!=0, and back, from the
16471 controller. Also, rotate dns and cpu workers if the controller
16472 changes options that will affect them; and initialize the dns
16473 worker cache tree whether or not we start out as a server.
16474 - Only upload a new server descriptor when options change, 18
16475 hours have passed, uptime is reset, or bandwidth changes a lot.
16476 - Check [X-]Forwarded-For headers in HTTP requests when generating
16477 log messages. This lets people run dirservers (and caches) behind
16478 Apache but still know which IP addresses are causing warnings.
16480 o Config option changes:
16481 - Replace (Fascist)Firewall* config options with a new
16482 ReachableAddresses option that understands address policies.
16483 For example, "ReachableAddresses *:80,*:443"
16484 - Get rid of IgnoreVersion undocumented config option, and make us
16485 only warn, never exit, when we're running an obsolete version.
16486 - Make MonthlyAccountingStart config option truly obsolete now.
16488 o Fixes on 0.1.0.x:
16489 - Reject ports 465 and 587 in the default exit policy, since
16490 people have started using them for spam too.
16491 - It turns out we couldn't bootstrap a network since we added
16492 reachability detection in 0.1.0.1-rc. Good thing the Tor network
16493 has never gone down. Add an AssumeReachable config option to let
16494 servers and dirservers bootstrap. When we're trying to build a
16495 high-uptime or high-bandwidth circuit but there aren't enough
16496 suitable servers, try being less picky rather than simply failing.
16497 - Our logic to decide if the OR we connected to was the right guy
16498 was brittle and maybe open to a mitm for unverified routers.
16499 - We weren't cannibalizing circuits correctly for
16500 CIRCUIT_PURPOSE_C_ESTABLISH_REND and
16501 CIRCUIT_PURPOSE_S_ESTABLISH_INTRO, so we were being forced to
16502 build those from scratch. This should make hidden services faster.
16503 - Predict required circuits better, with an eye toward making hidden
16504 services faster on the service end.
16505 - Retry streams if the exit node sends back a 'misc' failure. This
16506 should result in fewer random failures. Also, after failing
16507 from resolve failed or misc, reset the num failures, so we give
16508 it a fair shake next time we try.
16509 - Clean up the rendezvous warn log msgs, and downgrade some to info.
16510 - Reduce severity on logs about dns worker spawning and culling.
16511 - When we're shutting down and we do something like try to post a
16512 server descriptor or rendezvous descriptor, don't complain that
16513 we seem to be unreachable. Of course we are, we're shutting down.
16514 - Add TTLs to RESOLVED, CONNECTED, and END_REASON_EXITPOLICY cells.
16515 We don't use them yet, but maybe one day our DNS resolver will be
16516 able to discover them.
16517 - Make ContactInfo mandatory for authoritative directory servers.
16518 - Require server descriptors to list IPv4 addresses -- hostnames
16519 are no longer allowed. This also fixes some potential security
16520 problems with people providing hostnames as their address and then
16521 preferentially resolving them to partition users.
16522 - Change log line for unreachability to explicitly suggest /etc/hosts
16523 as the culprit. Also make it clearer what IP address and ports we're
16524 testing for reachability.
16525 - Put quotes around user-supplied strings when logging so users are
16526 more likely to realize if they add bad characters (like quotes)
16528 - Let auth dir servers start without specifying an Address config
16530 - Make unit tests (and other invocations that aren't the real Tor)
16531 run without launching listeners, creating subdirectories, and so on.
16534 Changes in version 0.1.1.5-alpha - 2005-08-08
16535 o Bugfixes included in 0.1.0.14.
16537 o Bugfixes on 0.1.0.x:
16538 - If you write "HiddenServicePort 6667 127.0.0.1 6668" in your
16539 torrc rather than "HiddenServicePort 6667 127.0.0.1:6668",
16540 it would silently using ignore the 6668.
16543 Changes in version 0.1.0.14 - 2005-08-08
16544 o Bugfixes on 0.1.0.x:
16545 - Fix the other half of the bug with crypto handshakes
16547 - Fix an assert trigger if you send a 'signal term' via the
16548 controller when it's listening for 'event info' messages.
16551 Changes in version 0.1.1.4-alpha - 2005-08-04
16552 o Bugfixes included in 0.1.0.13.
16555 - Improve tor_gettimeofday() granularity on windows.
16556 - Make clients regenerate their keys when their IP address changes.
16557 - Implement some more GETINFO goodness: expose helper nodes, config
16558 options, getinfo keys.
16561 Changes in version 0.1.0.13 - 2005-08-04
16562 o Bugfixes on 0.1.0.x:
16563 - Fix a critical bug in the security of our crypto handshakes.
16564 - Fix a size_t underflow in smartlist_join_strings2() that made
16565 it do bad things when you hand it an empty smartlist.
16566 - Fix Windows installer to ship Tor license (thanks to Aphex for
16567 pointing out this oversight) and put a link to the doc directory
16569 - Explicitly set no-unaligned-access for sparc: it turns out the
16570 new gcc's let you compile broken code, but that doesn't make it
16574 Changes in version 0.1.1.3-alpha - 2005-07-23
16575 o Bugfixes on 0.1.1.2-alpha:
16576 - Fix a bug in handling the controller's "post descriptor"
16578 - Fix several bugs in handling the controller's "extend circuit"
16580 - Fix a bug in handling the controller's "stream status" event.
16581 - Fix an assert failure if we have a controller listening for
16582 circuit events and we go offline.
16583 - Re-allow hidden service descriptors to publish 0 intro points.
16584 - Fix a crash when generating your hidden service descriptor if
16585 you don't have enough intro points already.
16587 o New features on 0.1.1.2-alpha:
16588 - New controller function "getinfo accounting", to ask how
16589 many bytes we've used in this time period.
16590 - Experimental support for helper nodes: a lot of the risk from
16591 a small static adversary comes because users pick new random
16592 nodes every time they rebuild a circuit. Now users will try to
16593 stick to the same small set of entry nodes if they can. Not
16594 enabled by default yet.
16596 o Bugfixes on 0.1.0.12:
16597 - If you're an auth dir server, always publish your dirport,
16598 even if you haven't yet found yourself to be reachable.
16599 - Fix a size_t underflow in smartlist_join_strings2() that made
16600 it do bad things when you hand it an empty smartlist.
16603 Changes in version 0.1.0.12 - 2005-07-18
16604 o New directory servers:
16605 - tor26 has changed IP address.
16607 o Bugfixes on 0.1.0.x:
16608 - Fix a possible double-free in tor_gzip_uncompress().
16609 - When --disable-threads is set, do not search for or link against
16610 pthreads libraries.
16611 - Don't trigger an assert if an authoritative directory server
16612 claims its dirport is 0.
16613 - Fix bug with removing Tor as an NT service: some people were
16614 getting "The service did not return an error." Thanks to Matt
16618 Changes in version 0.1.1.2-alpha - 2005-07-15
16619 o New directory servers:
16620 - tor26 has changed IP address.
16622 o Bugfixes on 0.1.0.x, crashes/leaks:
16623 - Port the servers-not-obeying-their-exit-policies fix from
16625 - Fix an fd leak in start_daemon().
16626 - On Windows, you can't always reopen a port right after you've
16627 closed it. So change retry_listeners() to only close and re-open
16628 ports that have changed.
16629 - Fix a possible double-free in tor_gzip_uncompress().
16631 o Bugfixes on 0.1.0.x, usability:
16632 - When tor_socketpair() fails in Windows, give a reasonable
16633 Windows-style errno back.
16634 - Let people type "tor --install" as well as "tor -install" when
16636 want to make it an NT service.
16637 - NT service patch from Matt Edman to improve error messages.
16638 - When the controller asks for a config option with an abbreviated
16639 name, give the full name in our response.
16640 - Correct the man page entry on TrackHostExitsExpire.
16641 - Looks like we were never delivering deflated (i.e. compressed)
16642 running-routers lists, even when asked. Oops.
16643 - When --disable-threads is set, do not search for or link against
16644 pthreads libraries.
16646 o Bugfixes on 0.1.1.x:
16647 - Fix a seg fault with autodetecting which controller version is
16651 - New hidden service descriptor format: put a version in it, and
16652 let people specify introduction/rendezvous points that aren't
16653 in "the directory" (which is subjective anyway).
16654 - Allow the DEBUG controller event to work again. Mark certain log
16655 entries as "don't tell this to controllers", so we avoid cycles.
16658 Changes in version 0.1.0.11 - 2005-06-30
16659 o Bugfixes on 0.1.0.x:
16660 - Fix major security bug: servers were disregarding their
16661 exit policies if clients behaved unexpectedly.
16662 - Make OS X init script check for missing argument, so we don't
16663 confuse users who invoke it incorrectly.
16664 - Fix a seg fault in "tor --hash-password foo".
16665 - The MAPADDRESS control command was broken.
16668 Changes in version 0.1.1.1-alpha - 2005-06-29
16670 - Make OS X init script check for missing argument, so we don't
16671 confuse users who invoke it incorrectly.
16672 - Fix a seg fault in "tor --hash-password foo".
16673 - Fix a possible way to DoS dirservers.
16674 - When we complain that your exit policy implicitly allows local or
16675 private address spaces, name them explicitly so operators can
16677 - Make the log message less scary when all the dirservers are
16678 temporarily unreachable.
16679 - We were printing the number of idle dns workers incorrectly when
16683 - Revised controller protocol (version 1) that uses ascii rather
16684 than binary. Add supporting libraries in python and java so you
16685 can use the controller from your applications without caring how
16686 our protocol works.
16687 - Spiffy new support for crypto hardware accelerators. Can somebody
16691 Changes in version 0.0.9.10 - 2005-06-16
16692 o Bugfixes on 0.0.9.x (backported from 0.1.0.10):
16693 - Refuse relay cells that claim to have a length larger than the
16694 maximum allowed. This prevents a potential attack that could read
16695 arbitrary memory (e.g. keys) from an exit server's process
16699 Changes in version 0.1.0.10 - 2005-06-14
16700 o Allow a few EINVALs from libevent before dying. Warn on kqueue with
16701 libevent before 1.1a.
16704 Changes in version 0.1.0.9-rc - 2005-06-09
16706 - Reset buf->highwater every time buf_shrink() is called, not just on
16707 a successful shrink. This was causing significant memory bloat.
16708 - Fix buffer overflow when checking hashed passwords.
16709 - Security fix: if seeding the RNG on Win32 fails, quit.
16710 - Allow seeding the RNG on Win32 even when you're not running as
16712 - Disable threading on Solaris too. Something is wonky with it,
16713 cpuworkers, and reentrant libs.
16714 - Reenable the part of the code that tries to flush as soon as an
16715 OR outbuf has a full TLS record available. Perhaps this will make
16716 OR outbufs not grow as huge except in rare cases, thus saving lots
16717 of CPU time plus memory.
16718 - Reject malformed .onion addresses rather then passing them on as
16719 normal web requests.
16720 - Adapt patch from Adam Langley: fix possible memory leak in
16721 tor_lookup_hostname().
16722 - Initialize libevent later in the startup process, so the logs are
16723 already established by the time we start logging libevent warns.
16724 - Use correct errno on win32 if libevent fails.
16725 - Check and warn about known-bad/slow libevent versions.
16726 - Pay more attention to the ClientOnly config option.
16727 - Have torctl.in/tor.sh.in check for location of su binary (needed
16729 - Correct/add man page entries for LongLivedPorts, ExitPolicy,
16730 KeepalivePeriod, ClientOnly, NoPublish, HttpProxy, HttpsProxy,
16731 HttpProxyAuthenticator
16732 - Stop warning about sigpipes in the logs. We're going to
16733 pretend that getting these occassionally is normal and fine.
16734 - Resolve OS X installer bugs: stop claiming to be 0.0.9.2 in
16736 installer screens; and don't put stuff into StartupItems unless
16737 the user asks you to.
16738 - Require servers that use the default dirservers to have public IP
16739 addresses. We have too many servers that are configured with private
16740 IPs and their admins never notice the log entries complaining that
16741 their descriptors are being rejected.
16742 - Add OSX uninstall instructions. An actual uninstall script will
16746 Changes in version 0.1.0.8-rc - 2005-05-23
16748 - It turns out that kqueue on OS X 10.3.9 was causing kernel
16749 panics. Disable kqueue on all OS X Tors.
16750 - Fix RPM: remove duplicate line accidentally added to the rpm
16752 - Disable threads on openbsd too, since its gethostaddr is not
16754 - Tolerate libevent 0.8 since it still works, even though it's
16756 - Enable building on Red Hat 9.0 again.
16757 - Allow the middle hop of the testing circuit to be running any
16758 version, now that most of them have the bugfix to let them connect
16759 to unknown servers. This will allow reachability testing to work
16760 even when 0.0.9.7-0.0.9.9 become obsolete.
16761 - Handle relay cells with rh.length too large. This prevents
16762 a potential attack that could read arbitrary memory (maybe even
16763 keys) from the exit server's process.
16764 - We screwed up the dirport reachability testing when we don't yet
16765 have a cached version of the directory. Hopefully now fixed.
16766 - Clean up router_load_single_router() (used by the controller),
16767 so it doesn't seg fault on error.
16768 - Fix a minor memory leak when somebody establishes an introduction
16769 point at your Tor server.
16770 - If a socks connection ends because read fails, don't warn that
16771 you're not sending a socks reply back.
16774 - Add HttpProxyAuthenticator config option too, that works like
16775 the HttpsProxyAuthenticator config option.
16776 - Encode hashed controller passwords in hex instead of base64,
16777 to make it easier to write controllers.
16780 Changes in version 0.1.0.7-rc - 2005-05-17
16782 - Fix a bug in the OS X package installer that prevented it from
16783 installing on Tiger.
16784 - Fix a script bug in the OS X package installer that made it
16785 complain during installation.
16786 - Find libevent even if it's hiding in /usr/local/ and your
16787 CFLAGS and LDFLAGS don't tell you to look there.
16788 - Be able to link with libevent as a shared library (the default
16789 after 1.0d), even if it's hiding in /usr/local/lib and even
16790 if you haven't added /usr/local/lib to your /etc/ld.so.conf,
16791 assuming you're running gcc. Otherwise fail and give a useful
16793 - Fix a bug in the RPM packager: set home directory for _tor to
16794 something more reasonable when first installing.
16795 - Free a minor amount of memory that is still reachable on exit.
16798 Changes in version 0.1.0.6-rc - 2005-05-14
16800 - Implement --disable-threads configure option. Disable threads on
16801 netbsd by default, because it appears to have no reentrant resolver
16803 - Apple's OS X 10.4.0 ships with a broken kqueue. The new libevent
16804 release (1.1) detects and disables kqueue if it's broken.
16805 - Append default exit policy before checking for implicit internal
16806 addresses. Now we don't log a bunch of complaints on startup
16807 when using the default exit policy.
16808 - Some people were putting "Address " in their torrc, and they had
16809 a buggy resolver that resolved " " to 0.0.0.0. Oops.
16810 - If DataDir is ~/.tor, and that expands to /.tor, then default to
16811 LOCALSTATEDIR/tor instead.
16812 - Fix fragmented-message bug in TorControl.py.
16813 - Resolve a minor bug which would prevent unreachable dirports
16814 from getting suppressed in the published descriptor.
16815 - When the controller gave us a new descriptor, we weren't resolving
16816 it immediately, so Tor would think its address was 0.0.0.0 until
16817 we fetched a new directory.
16818 - Fix an uppercase/lowercase case error in suppressing a bogus
16819 libevent warning on some Linuxes.
16822 - Begin scrubbing sensitive strings from logs by default. Turn off
16823 the config option SafeLogging if you need to do debugging.
16824 - Switch to a new buffer management algorithm, which tries to avoid
16825 reallocing and copying quite as much. In first tests it looks like
16826 it uses *more* memory on average, but less cpu.
16827 - First cut at support for "create-fast" cells. Clients can use
16828 these when extending to their first hop, since the TLS already
16829 provides forward secrecy and authentication. Not enabled on
16831 - When dirservers refuse a router descriptor, we now log its
16832 contactinfo, platform, and the poster's IP address.
16833 - Call tor_free_all instead of connections_free_all after forking, to
16834 save memory on systems that need to fork.
16835 - Whine at you if you're a server and you don't set your contactinfo.
16836 - Implement --verify-config command-line option to check if your torrc
16837 is valid without actually launching Tor.
16838 - Rewrite address "serifos.exit" to "localhost.serifos.exit"
16839 rather than just rejecting it.
16842 Changes in version 0.1.0.5-rc - 2005-04-27
16844 - Stop trying to print a null pointer if an OR conn fails because
16845 we didn't like its cert.
16847 - Switch our internal buffers implementation to use a ring buffer,
16848 to hopefully improve performance for fast servers a lot.
16849 - Add HttpsProxyAuthenticator support (basic auth only), based
16850 on patch from Adam Langley.
16851 - Bump the default BandwidthRate from 1 MB to 2 MB, to accommodate
16852 the fast servers that have been joining lately.
16853 - Give hidden service accesses extra time on the first attempt,
16854 since 60 seconds is often only barely enough. This might improve
16856 - Improve performance for dirservers: stop re-parsing the whole
16857 directory every time you regenerate it.
16858 - Add more debugging info to help us find the weird dns freebsd
16859 pthreads bug; cleaner debug messages to help track future issues.
16862 Changes in version 0.0.9.9 - 2005-04-23
16863 o Bugfixes on 0.0.9.x:
16864 - If unofficial Tor clients connect and send weird TLS certs, our
16865 Tor server triggers an assert. This release contains a minimal
16866 backport from the broader fix that we put into 0.1.0.4-rc.
16869 Changes in version 0.1.0.4-rc - 2005-04-23
16871 - If unofficial Tor clients connect and send weird TLS certs, our
16872 Tor server triggers an assert. Stop asserting, and start handling
16873 TLS errors better in other situations too.
16874 - When the controller asks us to tell it about all the debug-level
16875 logs, it turns out we were generating debug-level logs while
16876 telling it about them, which turns into a bad loop. Now keep
16877 track of whether you're sending a debug log to the controller,
16878 and don't log when you are.
16879 - Fix the "postdescriptor" feature of the controller interface: on
16880 non-complete success, only say "done" once.
16882 - Clients are now willing to load balance over up to 2mB, not 1mB,
16883 of advertised bandwidth capacity.
16884 - Add a NoPublish config option, so you can be a server (e.g. for
16885 testing running Tor servers in other Tor networks) without
16886 publishing your descriptor to the primary dirservers.
16889 Changes in version 0.1.0.3-rc - 2005-04-08
16890 o Improvements on 0.1.0.2-rc:
16891 - Client now retries when streams end early for 'hibernating' or
16892 'resource limit' reasons, rather than failing them.
16893 - More automated handling for dirserver operators:
16894 - Automatically approve nodes running 0.1.0.2-rc or later,
16895 now that the the reachability detection stuff is working.
16896 - Now we allow two unverified servers with the same nickname
16897 but different keys. But if a nickname is verified, only that
16898 nickname+key are allowed.
16899 - If you're an authdirserver connecting to an address:port,
16900 and it's not the OR you were expecting, forget about that
16901 descriptor. If he *was* the one you were expecting, then forget
16902 about all other descriptors for that address:port.
16903 - Allow servers to publish descriptors from 12 hours in the future.
16904 Corollary: only whine about clock skew from the dirserver if
16905 he's a trusted dirserver (since now even verified servers could
16906 have quite wrong clocks).
16907 - Adjust maximum skew and age for rendezvous descriptors: let skew
16908 be 48 hours rather than 90 minutes.
16909 - Efficiency improvements:
16910 - Keep a big splay tree of (circid,orconn)->circuit mappings to make
16911 it much faster to look up a circuit for each relay cell.
16912 - Remove most calls to assert_all_pending_dns_resolves_ok(),
16913 since they're eating our cpu on exit nodes.
16914 - Stop wasting time doing a case insensitive comparison for every
16915 dns name every time we do any lookup. Canonicalize the names to
16916 lowercase and be done with it.
16917 - Start sending 'truncated' cells back rather than destroy cells,
16918 if the circuit closes in front of you. This means we won't have
16919 to abandon partially built circuits.
16920 - Only warn once per nickname from add_nickname_list_to_smartlist
16921 per failure, so an entrynode or exitnode choice that's down won't
16923 - Put a note in the torrc about abuse potential with the default
16925 - Revise control spec and implementation to allow all log messages to
16926 be sent to controller with their severities intact (suggested by
16927 Matt Edman). Update TorControl to handle new log event types.
16928 - Provide better explanation messages when controller's POSTDESCRIPTOR
16930 - Stop putting nodename in the Platform string in server descriptors.
16931 It doesn't actually help, and it is confusing/upsetting some people.
16933 o Bugfixes on 0.1.0.2-rc:
16934 - We were printing the host mask wrong in exit policies in server
16935 descriptors. This isn't a critical bug though, since we were still
16936 obeying the exit policy internally.
16937 - Fix Tor when compiled with libevent but without pthreads: move
16938 connection_unregister() from _connection_free() to
16940 - Fix an assert trigger (already fixed in 0.0.9.x): when we have
16941 the rare mysterious case of accepting a conn on 0.0.0.0:0, then
16942 when we look through the connection array, we'll find any of the
16943 cpu/dnsworkers. This is no good.
16945 o Bugfixes on 0.0.9.8:
16946 - Fix possible bug on threading platforms (e.g. win32) which was
16947 leaking a file descriptor whenever a cpuworker or dnsworker died.
16948 - When using preferred entry or exit nodes, ignore whether the
16949 circuit wants uptime or capacity. They asked for the nodes, they
16951 - chdir() to your datadirectory at the *end* of the daemonize process,
16952 not the beginning. This was a problem because the first time you
16953 run tor, if your datadir isn't there, and you have runasdaemon set
16954 to 1, it will try to chdir to it before it tries to create it. Oops.
16955 - Handle changed router status correctly when dirserver reloads
16956 fingerprint file. We used to be dropping all unverified descriptors
16957 right then. The bug was hidden because we would immediately
16958 fetch a directory from another dirserver, which would include the
16959 descriptors we just dropped.
16960 - When we're connecting to an OR and he's got a different nickname/key
16961 than we were expecting, only complain loudly if we're an OP or a
16962 dirserver. Complaining loudly to the OR admins just confuses them.
16963 - Tie MAX_DIR_SIZE to MAX_BUF_SIZE, so now directory sizes won't get
16964 artificially capped at 500kB.
16967 Changes in version 0.0.9.8 - 2005-04-07
16968 o Bugfixes on 0.0.9.x:
16969 - We have a bug that I haven't found yet. Sometimes, very rarely,
16970 cpuworkers get stuck in the 'busy' state, even though the cpuworker
16971 thinks of itself as idle. This meant that no new circuits ever got
16972 established. Here's a workaround to kill any cpuworker that's been
16973 busy for more than 100 seconds.
16976 Changes in version 0.1.0.2-rc - 2005-04-01
16977 o Bugfixes on 0.1.0.1-rc:
16978 - Fixes on reachability detection:
16979 - Don't check for reachability while hibernating.
16980 - If ORPort is reachable but DirPort isn't, still publish the
16981 descriptor, but zero out DirPort until it's found reachable.
16982 - When building testing circs for ORPort testing, use only
16983 high-bandwidth nodes, so fewer circuits fail.
16984 - Complain about unreachable ORPort separately from unreachable
16985 DirPort, so the user knows what's going on.
16986 - Make sure we only conclude ORPort reachability if we didn't
16987 initiate the conn. Otherwise we could falsely conclude that
16988 we're reachable just because we connected to the guy earlier
16989 and he used that same pipe to extend to us.
16990 - Authdirservers shouldn't do ORPort reachability detection,
16991 since they're in clique mode, so it will be rare to find a
16992 server not already connected to them.
16993 - When building testing circuits, always pick middle hops running
16994 Tor 0.0.9.7, so we avoid the "can't extend to unknown routers"
16995 bug. (This is a kludge; it will go away when 0.0.9.x becomes
16997 - When we decide we're reachable, actually publish our descriptor
16999 - Fix bug in redirectstream in the controller.
17000 - Fix the state descriptor strings so logs don't claim edge streams
17001 are in a different state than they actually are.
17002 - Use recent libevent features when possible (this only really affects
17003 win32 and osx right now, because the new libevent with these
17004 features hasn't been released yet). Add code to suppress spurious
17006 - Prevent possible segfault in connection_close_unattached_ap().
17007 - Fix newlines on torrc in win32.
17008 - Improve error msgs when tor-resolve fails.
17010 o Improvements on 0.0.9.x:
17011 - New experimental script tor/contrib/ExerciseServer.py (needs more
17012 work) that uses the controller interface to build circuits and
17013 fetch pages over them. This will help us bootstrap servers that
17014 have lots of capacity but haven't noticed it yet.
17015 - New experimental script tor/contrib/PathDemo.py (needs more work)
17016 that uses the controller interface to let you choose whole paths
17018 "<hostname>.<path,separated by dots>.<length of path>.path"
17019 - When we've connected to an OR and handshaked but didn't like
17020 the result, we were closing the conn without sending destroy
17021 cells back for pending circuits. Now send those destroys.
17024 Changes in version 0.0.9.7 - 2005-04-01
17025 o Bugfixes on 0.0.9.x:
17026 - Fix another race crash bug (thanks to Glenn Fink for reporting).
17027 - Compare identity to identity, not to nickname, when extending to
17028 a router not already in the directory. This was preventing us from
17029 extending to unknown routers. Oops.
17030 - Make sure to create OS X Tor user in <500 range, so we aren't
17031 creating actual system users.
17032 - Note where connection-that-hasn't-sent-end was marked, and fix
17033 a few really loud instances of this harmless bug (it's fixed more
17037 Changes in version 0.1.0.1-rc - 2005-03-28
17039 - Add reachability testing. Your Tor server will automatically try
17040 to see if its ORPort and DirPort are reachable from the outside,
17041 and it won't upload its descriptor until it decides they are.
17042 - Handle unavailable hidden services better. Handle slow or busy
17043 hidden services better.
17044 - Add support for CONNECTing through https proxies, with "HttpsProxy"
17046 - New exit policy: accept most low-numbered ports, rather than
17047 rejecting most low-numbered ports.
17048 - More Tor controller support (still experimental). See
17049 http://tor.eff.org/doc/control-spec.txt for all the new features,
17050 including signals to emulate unix signals from any platform;
17051 redirectstream; extendcircuit; mapaddress; getinfo; postdescriptor;
17052 closestream; closecircuit; etc.
17053 - Make nt services work and start on startup on win32 (based on
17054 patch by Matt Edman).
17055 - Add a new AddressMap config directive to rewrite incoming socks
17056 addresses. This lets you, for example, declare an implicit
17057 required exit node for certain sites.
17058 - Add a new TrackHostExits config directive to trigger addressmaps
17059 for certain incoming socks addresses -- for sites that break when
17060 your exit keeps changing (based on patch by Mike Perry).
17061 - Redo the client-side dns cache so it's just an addressmap too.
17062 - Notice when our IP changes, and reset stats/uptime/reachability.
17063 - When an application is using socks5, give him the whole variety of
17064 potential socks5 responses (connect refused, host unreachable, etc),
17065 rather than just "success" or "failure".
17066 - A more sane version numbering system. See
17067 http://tor.eff.org/cvs/tor/doc/version-spec.txt for details.
17068 - New contributed script "exitlist": a simple python script to
17069 parse directories and find Tor nodes that exit to listed
17071 - New contributed script "privoxy-tor-toggle" to toggle whether
17072 Privoxy uses Tor. Seems to be configured for Debian by default.
17073 - Report HTTP reasons to client when getting a response from directory
17074 servers -- so you can actually know what went wrong.
17075 - New config option MaxAdvertisedBandwidth which lets you advertise
17076 a low bandwidthrate (to not attract as many circuits) while still
17077 allowing a higher bandwidthrate in reality.
17079 o Robustness/stability fixes:
17080 - Make Tor use Niels Provos's libevent instead of its current
17081 poll-but-sometimes-select mess. This will let us use faster async
17082 cores (like epoll, kpoll, and /dev/poll), and hopefully work better
17084 - pthread support now too. This was forced because when we forked,
17085 we ended up wasting a lot of duplicate ram over time. Also switch
17086 to foo_r versions of some library calls to allow reentry and
17088 - Better handling for heterogeneous / unreliable nodes:
17089 - Annotate circuits w/ whether they aim to contain high uptime nodes
17090 and/or high capacity nodes. When building circuits, choose
17092 - This means that every single node in an intro rend circuit,
17093 not just the last one, will have a minimum uptime.
17094 - New config option LongLivedPorts to indicate application streams
17095 that will want high uptime circuits.
17096 - Servers reset uptime when a dir fetch entirely fails. This
17097 hopefully reflects stability of the server's network connectivity.
17098 - If somebody starts his tor server in Jan 2004 and then fixes his
17099 clock, don't make his published uptime be a year.
17100 - Reset published uptime when you wake up from hibernation.
17101 - Introduce a notion of 'internal' circs, which are chosen without
17102 regard to the exit policy of the last hop. Intro and rendezvous
17103 circs must be internal circs, to avoid leaking information. Resolve
17104 and connect streams can use internal circs if they want.
17105 - New circuit pooling algorithm: make sure to have enough circs around
17106 to satisfy any predicted ports, and also make sure to have 2 internal
17107 circs around if we've required internal circs lately (and with high
17108 uptime if we've seen that lately too).
17109 - Split NewCircuitPeriod option into NewCircuitPeriod (30 secs),
17110 which describes how often we retry making new circuits if current
17111 ones are dirty, and MaxCircuitDirtiness (10 mins), which describes
17112 how long we're willing to make use of an already-dirty circuit.
17113 - Cannibalize GENERAL circs to be C_REND, C_INTRO, S_INTRO, and S_REND
17114 circ as necessary, if there are any completed ones lying around
17115 when we try to launch one.
17116 - Make hidden services try to establish a rendezvous for 30 seconds,
17117 rather than for n (where n=3) attempts to build a circuit.
17118 - Change SHUTDOWN_WAIT_LENGTH from a fixed 30 secs to a config option
17119 "ShutdownWaitLength".
17120 - Try to be more zealous about calling connection_edge_end when
17121 things go bad with edge conns in connection.c.
17122 - Revise tor-spec to add more/better stream end reasons.
17123 - Revise all calls to connection_edge_end to avoid sending "misc",
17124 and to take errno into account where possible.
17127 - Fix a race condition that can trigger an assert, when we have a
17128 pending create cell and an OR connection fails right then.
17129 - Fix several double-mark-for-close bugs, e.g. where we were finding
17130 a conn for a cell even if that conn is already marked for close.
17131 - Make sequence of log messages when starting on win32 with no config
17132 file more reasonable.
17133 - When choosing an exit node for a new non-internal circ, don't take
17134 into account whether it'll be useful for any pending x.onion
17135 addresses -- it won't.
17136 - Turn addr_policy_compare from a tristate to a quadstate; this should
17137 help address our "Ah, you allow 1.2.3.4:80. You are a good choice
17138 for google.com" problem.
17139 - Make "platform" string in descriptor more accurate for Win32 servers,
17140 so it's not just "unknown platform".
17141 - Fix an edge case in parsing config options (thanks weasel).
17142 If they say "--" on the commandline, it's not an option.
17143 - Reject odd-looking addresses at the client (e.g. addresses that
17144 contain a colon), rather than having the server drop them because
17146 - tor-resolve requests were ignoring .exit if there was a working circuit
17147 they could use instead.
17148 - REUSEADDR on normal platforms means you can rebind to the port
17149 right after somebody else has let it go. But REUSEADDR on win32
17150 means to let you bind to the port _even when somebody else
17151 already has it bound_! So, don't do that on Win32.
17152 - Change version parsing logic: a version is "obsolete" if it is not
17153 recommended and (1) there is a newer recommended version in the
17154 same series, or (2) there are no recommended versions in the same
17155 series, but there are some recommended versions in a newer series.
17156 A version is "new" if it is newer than any recommended version in
17158 - Stop most cases of hanging up on a socks connection without sending
17162 - Require BandwidthRate to be at least 20kB/s for servers.
17163 - When a dirserver causes you to give a warn, mention which dirserver
17165 - New config option DirAllowPrivateAddresses for authdirservers.
17166 Now by default they refuse router descriptors that have non-IP or
17167 private-IP addresses.
17168 - Stop publishing socksport in the directory, since it's not
17169 actually meant to be public. For compatibility, publish a 0 there
17171 - Change DirFetchPeriod/StatusFetchPeriod to have a special "Be
17172 smart" value, that is low for servers and high for clients.
17173 - If our clock jumps forward by 100 seconds or more, assume something
17174 has gone wrong with our network and abandon all not-yet-used circs.
17175 - Warn when exit policy implicitly allows local addresses.
17176 - If we get an incredibly skewed timestamp from a dirserver mirror
17177 that isn't a verified OR, don't warn -- it's probably him that's
17179 - Since we ship our own Privoxy on OS X, tweak it so it doesn't write
17180 cookies to disk and doesn't log each web request to disk. (Thanks
17181 to Brett Carrington for pointing this out.)
17182 - When a client asks us for a dir mirror and we don't have one,
17183 launch an attempt to get a fresh one.
17184 - If we're hibernating and we get a SIGINT, exit immediately.
17185 - Add --with-dmalloc ./configure option, to track memory leaks.
17186 - And try to free all memory on closing, so we can detect what
17188 - Cache local dns resolves correctly even when they're .exit
17190 - Give a better warning when some other server advertises an
17191 ORPort that is actually an apache running ssl.
17192 - Add "opt hibernating 1" to server descriptor to make it clearer
17193 whether the server is hibernating.
17196 Changes in version 0.0.9.6 - 2005-03-24
17197 o Bugfixes on 0.0.9.x (crashes and asserts):
17198 - Add new end stream reasons to maintainance branch. Fix bug where
17199 reason (8) could trigger an assert. Prevent bug from recurring.
17200 - Apparently win32 stat wants paths to not end with a slash.
17201 - Fix assert triggers in assert_cpath_layer_ok(), where we were
17202 blowing away the circuit that conn->cpath_layer points to, then
17203 checking to see if the circ is well-formed. Backport check to make
17204 sure we dont use the cpath on a closed connection.
17205 - Prevent circuit_resume_edge_reading_helper() from trying to package
17206 inbufs for marked-for-close streams.
17207 - Don't crash on hup if your options->address has become unresolvable.
17208 - Some systems (like OS X) sometimes accept() a connection and tell
17209 you the remote host is 0.0.0.0:0. If this happens, due to some
17210 other mis-features, we get confused; so refuse the conn for now.
17212 o Bugfixes on 0.0.9.x (other):
17213 - Fix harmless but scary "Unrecognized content encoding" warn message.
17214 - Add new stream error reason: TORPROTOCOL reason means "you are not
17215 speaking a version of Tor I understand; say bye-bye to your stream."
17216 - Be willing to cache directories from up to ROUTER_MAX_AGE seconds
17217 into the future, now that we are more tolerant of skew. This
17218 resolves a bug where a Tor server would refuse to cache a directory
17219 because all the directories it gets are too far in the future;
17220 yet the Tor server never logs any complaints about clock skew.
17221 - Mac packaging magic: make man pages useable, and do not overwrite
17222 existing torrc files.
17223 - Make OS X log happily to /var/log/tor/tor.log
17226 Changes in version 0.0.9.5 - 2005-02-22
17227 o Bugfixes on 0.0.9.x:
17228 - Fix an assert race at exit nodes when resolve requests fail.
17229 - Stop picking unverified dir mirrors--it only leads to misery.
17230 - Patch from Matt Edman to make NT services work better. Service
17231 support is still not compiled into the executable by default.
17232 - Patch from Dmitri Bely so the Tor service runs better under
17233 the win32 SYSTEM account.
17234 - Make tor-resolve actually work (?) on Win32.
17235 - Fix a sign bug when getrlimit claims to have 4+ billion
17236 file descriptors available.
17237 - Stop refusing to start when bandwidthburst == bandwidthrate.
17238 - When create cells have been on the onion queue more than five
17239 seconds, just send back a destroy and take them off the list.
17242 Changes in version 0.0.9.4 - 2005-02-03
17243 o Bugfixes on 0.0.9:
17244 - Fix an assert bug that took down most of our servers: when
17245 a server claims to have 1 GB of bandwidthburst, don't
17247 - Don't crash as badly if we have spawned the max allowed number
17248 of dnsworkers, or we're out of file descriptors.
17249 - Block more file-sharing ports in the default exit policy.
17250 - MaxConn is now automatically set to the hard limit of max
17251 file descriptors we're allowed (ulimit -n), minus a few for
17253 - Give a clearer message when servers need to raise their
17254 ulimit -n when they start running out of file descriptors.
17255 - SGI Compatibility patches from Jan Schaumann.
17256 - Tolerate a corrupt cached directory better.
17257 - When a dirserver hasn't approved your server, list which one.
17258 - Go into soft hibernation after 95% of the bandwidth is used,
17259 not 99%. This is especially important for daily hibernators who
17260 have a small accounting max. Hopefully it will result in fewer
17261 cut connections when the hard hibernation starts.
17262 - Load-balance better when using servers that claim more than
17263 800kB/s of capacity.
17264 - Make NT services work (experimental, only used if compiled in).
17267 Changes in version 0.0.9.3 - 2005-01-21
17268 o Bugfixes on 0.0.9:
17269 - Backport the cpu use fixes from main branch, so busy servers won't
17270 need as much processor time.
17271 - Work better when we go offline and then come back, or when we
17272 run Tor at boot before the network is up. We do this by
17273 optimistically trying to fetch a new directory whenever an
17274 application request comes in and we think we're offline -- the
17275 human is hopefully a good measure of when the network is back.
17276 - Backport some minimal hidserv bugfixes: keep rend circuits open as
17277 long as you keep using them; actually publish hidserv descriptors
17278 shortly after they change, rather than waiting 20-40 minutes.
17279 - Enable Mac startup script by default.
17280 - Fix duplicate dns_cancel_pending_resolve reported by Giorgos Pallas.
17281 - When you update AllowUnverifiedNodes or FirewallPorts via the
17282 controller's setconf feature, we were always appending, never
17284 - When you update HiddenServiceDir via setconf, it was screwing up
17285 the order of reading the lines, making it fail.
17286 - Do not rewrite a cached directory back to the cache; otherwise we
17287 will think it is recent and not fetch a newer one on startup.
17288 - Workaround for webservers that lie about Content-Encoding: Tor
17289 now tries to autodetect compressed directories and compression
17290 itself. This lets us Proxypass dir fetches through apache.
17293 Changes in version 0.0.9.2 - 2005-01-04
17294 o Bugfixes on 0.0.9 (crashes and asserts):
17295 - Fix an assert on startup when the disk is full and you're logging
17297 - If you do socks4 with an IP of 0.0.0.x but *don't* provide a socks4a
17298 style address, then we'd crash.
17299 - Fix an assert trigger when the running-routers string we get from
17300 a dirserver is broken.
17301 - Make worker threads start and run on win32. Now win32 servers
17303 - Bandaid (not actually fix, but now it doesn't crash) an assert
17304 where the dns worker dies mysteriously and the main Tor process
17305 doesn't remember anything about the address it was resolving.
17307 o Bugfixes on 0.0.9 (Win32):
17308 - Workaround for brain-damaged __FILE__ handling on MSVC: keep Nick's
17309 name out of the warning/assert messages.
17310 - Fix a superficial "unhandled error on read" bug on win32.
17311 - The win32 installer no longer requires a click-through for our
17312 license, since our Free Software license grants rights but does not
17314 - Win32: When connecting to a dirserver fails, try another one
17315 immediately. (This was already working for non-win32 Tors.)
17316 - Stop trying to parse $HOME on win32 when hunting for default
17318 - Make tor-resolve.c work on win32 by calling network_init().
17320 o Bugfixes on 0.0.9 (other):
17321 - Make 0.0.9.x build on Solaris again.
17322 - Due to a fencepost error, we were blowing away the \n when reporting
17323 confvalue items in the controller. So asking for multiple config
17324 values at once couldn't work.
17325 - When listing circuits that are pending on an opening OR connection,
17326 if we're an OR we were listing circuits that *end* at us as
17327 being pending on every listener, dns/cpu worker, etc. Stop that.
17328 - Dirservers were failing to create 'running-routers' or 'directory'
17329 strings if we had more than some threshold of routers. Fix them so
17330 they can handle any number of routers.
17331 - Fix a superficial "Duplicate mark for close" bug.
17332 - Stop checking for clock skew for OR connections, even for servers.
17333 - Fix a fencepost error that was chopping off the last letter of any
17334 nickname that is the maximum allowed nickname length.
17335 - Update URLs in log messages so they point to the new website.
17336 - Fix a potential problem in mangling server private keys while
17337 writing to disk (not triggered yet, as far as we know).
17338 - Include the licenses for other free software we include in Tor,
17339 now that we're shipping binary distributions more regularly.
17342 Changes in version 0.0.9.1 - 2004-12-15
17343 o Bugfixes on 0.0.9:
17344 - Make hibernation actually work.
17345 - Make HashedControlPassword config option work.
17346 - When we're reporting event circuit status to a controller,
17347 don't use the stream status code.
17350 Changes in version 0.0.9 - 2004-12-12
17352 - Clean up manpage and torrc.sample file.
17353 - Clean up severities and text of log warnings.
17355 - Make servers trigger an assert when they enter hibernation.
17358 Changes in version 0.0.9rc7 - 2004-12-08
17359 o Bugfixes on 0.0.9rc:
17360 - Fix a stack-trashing crash when an exit node begins hibernating.
17361 - Avoid looking at unallocated memory while considering which
17362 ports we need to build circuits to cover.
17363 - Stop a sigpipe: when an 'end' cell races with eof from the app,
17364 we shouldn't hold-open-until-flush if the eof arrived first.
17365 - Fix a bug with init_cookie_authentication() in the controller.
17366 - When recommending new-format log lines, if the upper bound is
17367 LOG_ERR, leave it implicit.
17369 o Bugfixes on 0.0.8.1:
17370 - Fix a whole slew of memory leaks.
17371 - Fix isspace() and friends so they still make Solaris happy
17372 but also so they don't trigger asserts on win32.
17373 - Fix parse_iso_time on platforms without strptime (eg win32).
17374 - win32: tolerate extra "readable" events better.
17375 - win32: when being multithreaded, leave parent fdarray open.
17376 - Make unit tests work on win32.
17379 Changes in version 0.0.9rc6 - 2004-12-06
17380 o Bugfixes on 0.0.9pre:
17381 - Clean up some more integer underflow opportunities (not exploitable
17383 - While hibernating, hup should not regrow our listeners.
17384 - Send an end to the streams we close when we hibernate, rather
17385 than just chopping them off.
17386 - React to eof immediately on non-open edge connections.
17388 o Bugfixes on 0.0.8.1:
17389 - Calculate timeout for waiting for a connected cell from the time
17390 we sent the begin cell, not from the time the stream started. If
17391 it took a long time to establish the circuit, we would time out
17392 right after sending the begin cell.
17393 - Fix router_compare_addr_to_addr_policy: it was not treating a port
17394 of * as always matching, so we were picking reject *:* nodes as
17395 exit nodes too. Oops.
17398 - New circuit building strategy: keep a list of ports that we've
17399 used in the past 6 hours, and always try to have 2 circuits open
17400 or on the way that will handle each such port. Seed us with port
17401 80 so web users won't complain that Tor is "slow to start up".
17402 - Make kill -USR1 dump more useful stats about circuits.
17403 - When warning about retrying or giving up, print the address, so
17404 the user knows which one it's talking about.
17405 - If you haven't used a clean circuit in an hour, throw it away,
17406 just to be on the safe side. (This means after 6 hours a totally
17407 unused Tor client will have no circuits open.)
17410 Changes in version 0.0.9rc5 - 2004-12-01
17411 o Bugfixes on 0.0.8.1:
17412 - Disallow NDEBUG. We don't ever want anybody to turn off debug.
17413 - Let resolve conns retry/expire also, rather than sticking around
17415 - If we are using select, make sure we stay within FD_SETSIZE.
17417 o Bugfixes on 0.0.9pre:
17418 - Fix integer underflow in tor_vsnprintf() that may be exploitable,
17419 but doesn't seem to be currently; thanks to Ilja van Sprundel for
17421 - If anybody set DirFetchPostPeriod, give them StatusFetchPeriod
17422 instead. Impose minima and maxima for all *Period options; impose
17423 even tighter maxima for fetching if we are a caching dirserver.
17424 Clip rather than rejecting.
17425 - Fetch cached running-routers from servers that serve it (that is,
17426 authdirservers and servers running 0.0.9rc5-cvs or later.)
17429 - Accept *:706 (silc) in default exit policy.
17430 - Implement new versioning format for post 0.1.
17431 - Support "foo.nickname.exit" addresses, to let Alice request the
17432 address "foo" as viewed by exit node "nickname". Based on a patch
17434 - Make tor --version --version dump the cvs Id of every file.
17437 Changes in version 0.0.9rc4 - 2004-11-28
17438 o Bugfixes on 0.0.8.1:
17439 - Make windows sockets actually non-blocking (oops), and handle
17440 win32 socket errors better.
17442 o Bugfixes on 0.0.9rc1:
17443 - Actually catch the -USR2 signal.
17446 Changes in version 0.0.9rc3 - 2004-11-25
17447 o Bugfixes on 0.0.8.1:
17448 - Flush the log file descriptor after we print "Tor opening log file",
17449 so we don't see those messages days later.
17451 o Bugfixes on 0.0.9rc1:
17452 - Make tor-resolve work again.
17453 - Avoid infinite loop in tor-resolve if tor hangs up on it.
17454 - Fix an assert trigger for clients/servers handling resolves.
17457 Changes in version 0.0.9rc2 - 2004-11-24
17458 o Bugfixes on 0.0.9rc1:
17459 - I broke socks5 support while fixing the eof bug.
17460 - Allow unitless bandwidths and intervals; they default to bytes
17462 - New servers don't start out hibernating; they are active until
17463 they run out of bytes, so they have a better estimate of how
17464 long it takes, and so their operators can know they're working.
17467 Changes in version 0.0.9rc1 - 2004-11-23
17468 o Bugfixes on 0.0.8.1:
17469 - Finally fix a bug that's been plaguing us for a year:
17470 With high load, circuit package window was reaching 0. Whenever
17471 we got a circuit-level sendme, we were reading a lot on each
17472 socket, but only writing out a bit. So we would eventually reach
17473 eof. This would be noticed and acted on even when there were still
17474 bytes sitting in the inbuf.
17475 - When poll() is interrupted, we shouldn't believe the revents values.
17477 o Bugfixes on 0.0.9pre6:
17478 - Fix hibernate bug that caused pre6 to be broken.
17479 - Don't keep rephist info for routers that haven't had activity for
17480 24 hours. (This matters now that clients have keys, since we track
17482 - Never call close_temp_logs while validating log options.
17483 - Fix backslash-escaping on tor.sh.in and torctl.in.
17486 - Implement weekly/monthly/daily accounting: now you specify your
17487 hibernation properties by
17488 AccountingMax N bytes|KB|MB|GB|TB
17489 AccountingStart day|week|month [day] HH:MM
17490 Defaults to "month 1 0:00".
17491 - Let bandwidth and interval config options be specified as 5 bytes,
17492 kb, kilobytes, etc; and as seconds, minutes, hours, days, weeks.
17493 - kill -USR2 now moves all logs to loglevel debug (kill -HUP to
17494 get back to normal.)
17495 - If your requested entry or exit node has advertised bandwidth 0,
17497 - Be more greedy about filling up relay cells -- we try reading again
17498 once we've processed the stuff we read, in case enough has arrived
17499 to fill the last cell completely.
17500 - Apply NT service patch from Osamu Fujino. Still needs more work.
17503 Changes in version 0.0.9pre6 - 2004-11-15
17504 o Bugfixes on 0.0.8.1:
17505 - Fix assert failure on malformed socks4a requests.
17506 - Use identity comparison, not nickname comparison, to choose which
17507 half of circuit-ID-space each side gets to use. This is needed
17508 because sometimes we think of a router as a nickname, and sometimes
17509 as a hex ID, and we can't predict what the other side will do.
17510 - Catch and ignore SIGXFSZ signals when log files exceed 2GB; our
17511 write() call will fail and we handle it there.
17512 - Add a FAST_SMARTLIST define to optionally inline smartlist_get
17513 and smartlist_len, which are two major profiling offenders.
17515 o Bugfixes on 0.0.9pre5:
17516 - Fix a bug in read_all that was corrupting config files on windows.
17517 - When we're raising the max number of open file descriptors to
17518 'unlimited', don't log that we just raised it to '-1'.
17519 - Include event code with events, as required by control-spec.txt.
17520 - Don't give a fingerprint when clients do --list-fingerprint:
17521 it's misleading, because it will never be the same again.
17522 - Stop using strlcpy in tor_strndup, since it was slowing us
17524 - Remove warn on startup about missing cached-directory file.
17525 - Make kill -USR1 work again.
17526 - Hibernate if we start tor during the "wait for wakeup-time" phase
17527 of an accounting interval. Log our hibernation plans better.
17528 - Authoritative dirservers now also cache their directory, so they
17529 have it on start-up.
17532 - Fetch running-routers; cache running-routers; compress
17533 running-routers; serve compressed running-routers.z
17534 - Add NSI installer script contributed by J Doe.
17535 - Commit VC6 and VC7 workspace/project files.
17536 - Commit a tor.spec for making RPM files, with help from jbash.
17537 - Add contrib/torctl.in contributed by Glenn Fink.
17538 - Implement the control-spec's SAVECONF command, to write your
17539 configuration to torrc.
17540 - Get cookie authentication for the controller closer to working.
17541 - Include control-spec.txt in the tarball.
17542 - When set_conf changes our server descriptor, upload a new copy.
17543 But don't upload it too often if there are frequent changes.
17544 - Document authentication config in man page, and document signals
17546 - Clean up confusing parts of man page and torrc.sample.
17547 - Make expand_filename handle ~ and ~username.
17548 - Use autoconf to enable largefile support where necessary. Use
17549 ftello where available, since ftell can fail at 2GB.
17550 - Distinguish between TOR_TLS_CLOSE and TOR_TLS_ERROR, so we can
17551 log more informatively.
17552 - Give a slightly more useful output for "tor -h".
17553 - Refuse application socks connections to port 0.
17554 - Check clock skew for verified servers, but allow unverified
17555 servers and clients to have any clock skew.
17556 - Break DirFetchPostPeriod into:
17557 - DirFetchPeriod for fetching full directory,
17558 - StatusFetchPeriod for fetching running-routers,
17559 - DirPostPeriod for posting server descriptor,
17560 - RendPostPeriod for posting hidden service descriptors.
17561 - Make sure the hidden service descriptors are at a random offset
17562 from each other, to hinder linkability.
17565 Changes in version 0.0.9pre5 - 2004-11-09
17566 o Bugfixes on 0.0.9pre4:
17567 - Fix a seg fault in unit tests (doesn't affect main program).
17568 - Fix an assert bug where a hidden service provider would fail if
17569 the first hop of his rendezvous circuit was down.
17570 - Hidden service operators now correctly handle version 1 style
17571 INTRODUCE1 cells (nobody generates them still, so not a critical
17573 - If do_hup fails, actually notice.
17574 - Handle more errnos from accept() without closing the listener.
17575 Some OpenBSD machines were closing their listeners because
17576 they ran out of file descriptors.
17577 - Send resolve cells to exit routers that are running a new
17578 enough version of the resolve code to work right.
17579 - Better handling of winsock includes on non-MSV win32 compilers.
17580 - Some people had wrapped their tor client/server in a script
17581 that would restart it whenever it died. This did not play well
17582 with our "shut down if your version is obsolete" code. Now people
17583 don't fetch a new directory if their local cached version is
17585 - Make our autogen.sh work on ksh as well as bash.
17588 - Hibernation: New config option "AccountingMaxKB" lets you
17589 set how many KBytes per month you want to allow your server to
17590 consume. Rather than spreading those bytes out evenly over the
17591 month, we instead hibernate for some of the month and pop up
17592 at a deterministic time, work until the bytes are consumed, then
17593 hibernate again. Config option "MonthlyAccountingStart" lets you
17594 specify which day of the month your billing cycle starts on.
17595 - Control interface: a separate program can now talk to your
17596 client/server over a socket, and get/set config options, receive
17597 notifications of circuits and streams starting/finishing/dying,
17598 bandwidth used, etc. The next step is to get some GUIs working.
17599 Let us know if you want to help out. See doc/control-spec.txt .
17600 - Ship a contrib/tor-control.py as an example script to interact
17601 with the control port.
17602 - "tor --hash-password zzyxz" will output a salted password for
17603 use in authenticating to the control interface.
17604 - New log format in config:
17605 "Log minsev[-maxsev] stdout|stderr|syslog" or
17606 "Log minsev[-maxsev] file /var/foo"
17609 - DirPolicy config option, to let people reject incoming addresses
17610 from their dirserver.
17611 - "tor --list-fingerprint" will list your identity key fingerprint
17613 - Add "pass" target for RedirectExit, to make it easier to break
17614 out of a sequence of RedirectExit rules.
17615 - Clients now generate a TLS cert too, in preparation for having
17616 them act more like real nodes.
17617 - Ship src/win32/ in the tarball, so people can use it to build.
17618 - Make old win32 fall back to CWD if SHGetSpecialFolderLocation
17620 - New "router-status" line in directory, to better bind each verified
17621 nickname to its identity key.
17622 - Deprecate unofficial config option abbreviations, and abbreviations
17623 not on the command line.
17624 - Add a pure-C tor-resolve implementation.
17625 - Use getrlimit and friends to ensure we can reach MaxConn (currently
17626 1024) file descriptors.
17628 o Code security improvements, inspired by Ilja:
17629 - Replace sprintf with snprintf. (I think they were all safe, but
17631 - Replace strcpy/strncpy with strlcpy in more places.
17632 - Avoid strcat; use snprintf or strlcat instead.
17633 - snprintf wrapper with consistent (though not C99) overflow behavior.
17636 Changes in version 0.0.9pre4 - 2004-10-17
17637 o Bugfixes on 0.0.9pre3:
17638 - If the server doesn't specify an exit policy, use the real default
17639 exit policy, not reject *:*.
17640 - Ignore fascistfirewall when uploading/downloading hidden service
17641 descriptors, since we go through Tor for those; and when using
17642 an HttpProxy, since we assume it can reach them all.
17643 - When looking for an authoritative dirserver, use only the ones
17644 configured at boot. Don't bother looking in the directory.
17645 - The rest of the fix for get_default_conf_file() on older win32.
17646 - Make 'Routerfile' config option obsolete.
17649 - New 'MyFamily nick1,...' config option for a server to
17650 specify other servers that shouldn't be used in the same circuit
17651 with it. Only believed if nick1 also specifies us.
17652 - New 'NodeFamily nick1,nick2,...' config option for a client to
17653 specify nodes that it doesn't want to use in the same circuit.
17654 - New 'Redirectexit pattern address:port' config option for a
17655 server to redirect exit connections, e.g. to a local squid.
17658 Changes in version 0.0.9pre3 - 2004-10-13
17659 o Bugfixes on 0.0.8.1:
17660 - Better torrc example lines for dirbindaddress and orbindaddress.
17661 - Improved bounds checking on parsed ints (e.g. config options and
17662 the ones we find in directories.)
17663 - Better handling of size_t vs int, so we're more robust on 64
17665 - Fix the rest of the bug where a newly started OR would appear
17666 as unverified even after we've added his fingerprint and hupped
17668 - Fix a bug from 0.0.7: when read() failed on a stream, we would
17669 close it without sending back an end. So 'connection refused'
17670 would simply be ignored and the user would get no response.
17672 o Bugfixes on 0.0.9pre2:
17673 - Serving the cached-on-disk directory to people is bad. We now
17674 provide no directory until we've fetched a fresh one.
17675 - Workaround for bug on windows where cached-directories get crlf
17677 - Make get_default_conf_file() work on older windows too.
17678 - If we write a *:* exit policy line in the descriptor, don't write
17679 any more exit policy lines.
17682 - Use only 0.0.9pre1 and later servers for resolve cells.
17683 - Make the dirservers file obsolete.
17684 - Include a dir-signing-key token in directories to tell the
17685 parsing entity which key is being used to sign.
17686 - Remove the built-in bulky default dirservers string.
17687 - New config option "Dirserver %s:%d [fingerprint]", which can be
17688 repeated as many times as needed. If no dirservers specified,
17689 default to moria1,moria2,tor26.
17690 - Make moria2 advertise a dirport of 80, so people behind firewalls
17691 will be able to get a directory.
17692 - Http proxy support
17693 - Dirservers translate requests for http://%s:%d/x to /x
17694 - You can specify "HttpProxy %s[:%d]" and all dir fetches will
17695 be routed through this host.
17696 - Clients ask for /tor/x rather than /x for new enough dirservers.
17697 This way we can one day coexist peacefully with apache.
17698 - Clients specify a "Host: %s%d" http header, to be compatible
17699 with more proxies, and so running squid on an exit node can work.
17702 Changes in version 0.0.8.1 - 2004-10-13
17704 - Fix a seg fault that can be triggered remotely for Tor
17705 clients/servers with an open dirport.
17706 - Fix a rare assert trigger, where routerinfos for entries in
17707 our cpath would expire while we're building the path.
17708 - Fix a bug in OutboundBindAddress so it (hopefully) works.
17709 - Fix a rare seg fault for people running hidden services on
17710 intermittent connections.
17711 - Fix a bug in parsing opt keywords with objects.
17712 - Fix a stale pointer assert bug when a stream detaches and
17714 - Fix a string format vulnerability (probably not exploitable)
17715 in reporting stats locally.
17716 - Fix an assert trigger: sometimes launching circuits can fail
17717 immediately, e.g. because too many circuits have failed recently.
17718 - Fix a compile warning on 64 bit platforms.
17721 Changes in version 0.0.9pre2 - 2004-10-03
17723 - Make fetching a cached directory work for 64-bit platforms too.
17724 - Make zlib.h a required header, not an optional header.
17727 Changes in version 0.0.9pre1 - 2004-10-01
17729 - Stop using separate defaults for no-config-file and
17730 empty-config-file. Now you have to explicitly turn off SocksPort,
17731 if you don't want it open.
17732 - Fix a bug in OutboundBindAddress so it (hopefully) works.
17733 - Improve man page to mention more of the 0.0.8 features.
17734 - Fix a rare seg fault for people running hidden services on
17735 intermittent connections.
17736 - Change our file IO stuff (especially wrt OpenSSL) so win32 is
17738 - Fix more dns related bugs: send back resolve_failed and end cells
17739 more reliably when the resolve fails, rather than closing the
17740 circuit and then trying to send the cell. Also attach dummy resolve
17741 connections to a circuit *before* calling dns_resolve(), to fix
17742 a bug where cached answers would never be sent in RESOLVED cells.
17743 - When we run out of disk space, or other log writing error, don't
17744 crash. Just stop logging to that log and continue.
17745 - We were starting to daemonize before we opened our logs, so if
17746 there were any problems opening logs, we would complain to stderr,
17747 which wouldn't work, and then mysteriously exit.
17748 - Fix a rare bug where sometimes a verified OR would connect to us
17749 before he'd uploaded his descriptor, which would cause us to
17750 assign conn->nickname as though he's unverified. Now we look through
17751 the fingerprint list to see if he's there.
17752 - Fix a rare assert trigger, where routerinfos for entries in
17753 our cpath would expire while we're building the path.
17756 - Clients can ask dirservers for /dir.z to get a compressed version
17757 of the directory. Only works for servers running 0.0.9, of course.
17758 - Make clients cache directories and use them to seed their router
17759 lists at startup. This means clients have a datadir again.
17760 - Configuration infrastructure support for warning on obsolete
17762 - Respond to content-encoding headers by trying to uncompress as
17764 - Reply with a deflated directory when a client asks for "dir.z".
17765 We could use allow-encodings instead, but allow-encodings isn't
17766 specified in HTTP 1.0.
17767 - Raise the max dns workers from 50 to 100.
17768 - Discourage people from setting their dirfetchpostperiod more often
17769 than once per minute.
17770 - Protect dirservers from overzealous descriptor uploading -- wait
17771 10 seconds after directory gets dirty, before regenerating.
17774 Changes in version 0.0.8 - 2004-08-25
17775 o Port it to SunOS 5.9 / Athena
17778 Changes in version 0.0.8rc2 - 2004-08-20
17779 o Make it compile on cygwin again.
17780 o When picking unverified routers, skip those with low uptime and/or
17781 low bandwidth, depending on what properties you care about.
17784 Changes in version 0.0.8rc1 - 2004-08-18
17785 o Changes from 0.0.7.3:
17787 - Fix assert triggers: if the other side returns an address 0.0.0.0,
17788 don't put it into the client dns cache.
17789 - If a begin failed due to exit policy, but we believe the IP address
17790 should have been allowed, switch that router to exitpolicy reject *:*
17791 until we get our next directory.
17793 - Clients choose nodes proportional to advertised bandwidth.
17794 - Avoid using nodes with low uptime as introduction points.
17795 - Handle servers with dynamic IP addresses: don't replace
17796 options->Address with the resolved one at startup, and
17797 detect our address right before we make a routerinfo each time.
17798 - 'FascistFirewall' option to pick dirservers and ORs on specific
17799 ports; plus 'FirewallPorts' config option to tell FascistFirewall
17800 which ports are open. (Defaults to 80,443)
17801 - Be more aggressive about trying to make circuits when the network
17802 has changed (e.g. when you unsuspend your laptop).
17803 - Check for time skew on http headers; report date in response to
17805 - If the entrynode config line has only one node, don't pick it as
17807 - Add strict{entry|exit}nodes config options. If set to 1, then
17808 we refuse to build circuits that don't include the specified entry
17810 - OutboundBindAddress config option, to bind to a specific
17811 IP address for outgoing connect()s.
17812 - End truncated log entries (e.g. directories) with "[truncated]".
17814 o Patches to 0.0.8preX:
17816 - Patches to compile and run on win32 again (maybe)?
17817 - Fix crash when looking for ~/.torrc with no $HOME set.
17818 - Fix a race bug in the unit tests.
17819 - Handle verified/unverified name collisions better when new
17820 routerinfo's arrive in a directory.
17821 - Sometimes routers were getting entered into the stats before
17822 we'd assigned their identity_digest. Oops.
17823 - Only pick and establish intro points after we've gotten a
17826 - AllowUnverifiedNodes config option to let circuits choose no-name
17827 routers in entry,middle,exit,introduction,rendezvous positions.
17828 Allow middle and rendezvous positions by default.
17829 - Add a man page for tor-resolve.
17832 Changes in version 0.0.7.3 - 2004-08-12
17833 o Stop dnsworkers from triggering an assert failure when you
17834 ask them to resolve the host "".
17837 Changes in version 0.0.8pre3 - 2004-08-09
17838 o Changes from 0.0.7.2:
17839 - Allow multiple ORs with same nickname in routerlist -- now when
17840 people give us one identity key for a nickname, then later
17841 another, we don't constantly complain until the first expires.
17842 - Remember used bandwidth (both in and out), and publish 15-minute
17843 snapshots for the past day into our descriptor.
17844 - You can now fetch $DIRURL/running-routers to get just the
17845 running-routers line, not the whole descriptor list. (But
17846 clients don't use this yet.)
17847 - When people mistakenly use Tor as an http proxy, point them
17848 at the tor-doc.html rather than the INSTALL.
17849 - Remove our mostly unused -- and broken -- hex_encode()
17850 function. Use base16_encode() instead. (Thanks to Timo Lindfors
17851 for pointing out this bug.)
17852 - Rotate onion keys every 12 hours, not every 2 hours, so we have
17853 fewer problems with people using the wrong key.
17854 - Change the default exit policy to reject the default edonkey,
17855 kazaa, gnutella ports.
17856 - Add replace_file() to util.[ch] to handle win32's rename().
17858 o Changes from 0.0.8preX:
17859 - Fix two bugs in saving onion keys to disk when rotating, so
17860 hopefully we'll get fewer people using old onion keys.
17861 - Fix an assert error that was making SocksPolicy not work.
17862 - Be willing to expire routers that have an open dirport -- it's
17863 just the authoritative dirservers we want to not forget.
17864 - Reject tor-resolve requests for .onion addresses early, so we
17865 don't build a whole rendezvous circuit and then fail.
17866 - When you're warning a server that he's unverified, don't cry
17867 wolf unpredictably.
17868 - Fix a race condition: don't try to extend onto a connection
17869 that's still handshaking.
17870 - For servers in clique mode, require the conn to be open before
17871 you'll choose it for your path.
17872 - Fix some cosmetic bugs about duplicate mark-for-close, lack of
17873 end relay cell, etc.
17874 - Measure bandwidth capacity over the last 24 hours, not just 12
17875 - Bugfix: authoritative dirservers were making and signing a new
17876 directory for each client, rather than reusing the cached one.
17879 Changes in version 0.0.8pre2 - 2004-08-04
17880 o Changes from 0.0.7.2:
17882 - Check directory signature _before_ you decide whether you're
17883 you're running an obsolete version and should exit.
17884 - Check directory signature _before_ you parse the running-routers
17885 list to decide who's running or verified.
17886 - Bugfixes and features:
17887 - Check return value of fclose while writing to disk, so we don't
17888 end up with broken files when servers run out of disk space.
17889 - Log a warning if the user uses an unsafe socks variant, so people
17890 are more likely to learn about privoxy or socat.
17891 - Dirservers now include RFC1123-style dates in the HTTP headers,
17892 which one day we will use to better detect clock skew.
17894 o Changes from 0.0.8pre1:
17895 - Make it compile without warnings again on win32.
17896 - Log a warning if you're running an unverified server, to let you
17897 know you might want to get it verified.
17898 - Only pick a default nickname if you plan to be a server.
17901 Changes in version 0.0.8pre1 - 2004-07-23
17903 - Made our unit tests compile again on OpenBSD 3.5, and tor
17904 itself compile again on OpenBSD on a sparc64.
17905 - We were neglecting milliseconds when logging on win32, so
17906 everything appeared to happen at the beginning of each second.
17908 o Protocol changes:
17909 - 'Extend' relay cell payloads now include the digest of the
17910 intended next hop's identity key. Now we can verify that we're
17911 extending to the right router, and also extend to routers we
17912 hadn't heard of before.
17915 - Tor nodes can now act as relays (with an advertised ORPort)
17916 without being manually verified by the dirserver operators.
17917 - Uploaded descriptors of unverified routers are now accepted
17918 by the dirservers, and included in the directory.
17919 - Verified routers are listed by nickname in the running-routers
17920 list; unverified routers are listed as "$<fingerprint>".
17921 - We now use hash-of-identity-key in most places rather than
17922 nickname or addr:port, for improved security/flexibility.
17923 - To avoid Sybil attacks, paths still use only verified servers.
17924 But now we have a chance to play around with hybrid approaches.
17925 - Nodes track bandwidth usage to estimate capacity (not used yet).
17926 - ClientOnly option for nodes that never want to become servers.
17927 - Directory caching.
17928 - "AuthoritativeDir 1" option for the official dirservers.
17929 - Now other nodes (clients and servers) will cache the latest
17930 directory they've pulled down.
17931 - They can enable their DirPort to serve it to others.
17932 - Clients will pull down a directory from any node with an open
17933 DirPort, and check the signature/timestamp correctly.
17934 - Authoritative dirservers now fetch directories from other
17935 authdirservers, to stay better synced.
17936 - Running-routers list tells who's down also, along with noting
17937 if they're verified (listed by nickname) or unverified (listed
17939 - Allow dirservers to serve running-router list separately.
17940 This isn't used yet.
17941 - ORs connect-on-demand to other ORs
17942 - If you get an extend cell to an OR you're not connected to,
17943 connect, handshake, and forward the create cell.
17944 - The authoritative dirservers stay connected to everybody,
17945 and everybody stays connected to 0.0.7 servers, but otherwise
17946 clients/servers expire unused connections after 5 minutes.
17947 - When servers get a sigint, they delay 30 seconds (refusing new
17948 connections) then exit. A second sigint causes immediate exit.
17949 - File and name management:
17950 - Look for .torrc if no CONFDIR "torrc" is found.
17951 - If no datadir is defined, then choose, make, and secure ~/.tor
17953 - If torrc not found, exitpolicy reject *:*.
17954 - Expands ~/ in filenames to $HOME/ (but doesn't yet expand ~arma).
17955 - If no nickname is defined, derive default from hostname.
17956 - Rename secret key files, e.g. identity.key -> secret_id_key,
17957 to discourage people from mailing their identity key to tor-ops.
17958 - Refuse to build a circuit before the directory has arrived --
17959 it won't work anyway, since you won't know the right onion keys
17961 - Try other dirservers immediately if the one you try is down. This
17962 should tolerate down dirservers better now.
17963 - Parse tor version numbers so we can do an is-newer-than check
17964 rather than an is-in-the-list check.
17965 - New socks command 'resolve', to let us shim gethostbyname()
17967 - A 'tor_resolve' script to access the socks resolve functionality.
17968 - A new socks-extensions.txt doc file to describe our
17969 interpretation and extensions to the socks protocols.
17970 - Add a ContactInfo option, which gets published in descriptor.
17971 - Publish OR uptime in descriptor (and thus in directory) too.
17972 - Write tor version at the top of each log file
17973 - New docs in the tarball:
17975 - Document that you should proxy your SSL traffic too.
17978 Changes in version 0.0.7.2 - 2004-07-07
17979 o A better fix for the 0.0.0.0 problem, that will hopefully
17980 eliminate the remaining related assertion failures.
17983 Changes in version 0.0.7.1 - 2004-07-04
17984 o When an address resolves to 0.0.0.0, treat it as a failed resolve,
17985 since internally we use 0.0.0.0 to signify "not yet resolved".
17988 Changes in version 0.0.7 - 2004-06-07
17989 o Updated the man page to reflect the new features.
17992 Changes in version 0.0.7rc2 - 2004-06-06
17993 o Changes from 0.0.7rc1:
17994 - Make it build on Win32 again.
17995 o Changes from 0.0.6.2:
17996 - Rotate dnsworkers and cpuworkers on SIGHUP, so they get new config
18000 Changes in version 0.0.7rc1 - 2004-06-02
18002 - On sighup, we were adding another log without removing the first
18003 one. So log messages would get duplicated n times for n sighups.
18004 - Several cases of using a connection after we'd freed it. The
18005 problem was that connections that are pending resolve are in both
18006 the pending_resolve tree, and also the circuit's resolving_streams
18007 list. When you want to remove one, you must remove it from both.
18008 - Fix a double-mark-for-close where an end cell arrived for a
18009 resolving stream, and then the resolve failed.
18010 - Check directory signatures based on name of signer, not on whom
18011 we got the directory from. This will let us cache directories more
18014 - Crank up some of our constants to handle more users.
18017 Changes in version 0.0.7pre1 - 2004-06-02
18018 o Fixes for crashes and other obnoxious bugs:
18019 - Fix an epipe bug: sometimes when directory connections failed
18020 to connect, we would give them a chance to flush before closing
18022 - When we detached from a circuit because of resolvefailed, we
18023 would immediately try the same circuit twice more, and then
18024 give up on the resolve thinking we'd tried three different
18026 - Limit the number of intro circuits we'll attempt to build for a
18027 hidden service per 15-minute period.
18028 - Check recommended-software string *early*, before actually parsing
18029 the directory. Thus we can detect an obsolete version and exit,
18030 even if the new directory format doesn't parse.
18031 o Fixes for security bugs:
18032 - Remember which nodes are dirservers when you startup, and if a
18033 random OR enables his dirport, don't automatically assume he's
18034 a trusted dirserver.
18036 - Directory connections were asking the wrong poll socket to
18037 start writing, and not asking themselves to start writing.
18038 - When we detached from a circuit because we sent a begin but
18039 didn't get a connected, we would use it again the first time;
18040 but after that we would correctly switch to a different one.
18041 - Stop warning when the first onion decrypt attempt fails; they
18042 will sometimes legitimately fail now that we rotate keys.
18043 - Override unaligned-access-ok check when $host_cpu is ia64 or
18044 arm. Apparently they allow it but the kernel whines.
18045 - Dirservers try to reconnect periodically too, in case connections
18047 - Fix some memory leaks in directory servers.
18048 - Allow backslash in Win32 filenames.
18049 - Made Tor build complain-free on FreeBSD, hopefully without
18050 breaking other BSD builds. We'll see.
18052 - Doxygen markup on all functions and global variables.
18053 - Make directory functions update routerlist, not replace it. So
18054 now directory disagreements are not so critical a problem.
18055 - Remove the upper limit on number of descriptors in a dirserver's
18056 directory (not that we were anywhere close).
18057 - Allow multiple logfiles at different severity ranges.
18058 - Allow *BindAddress to specify ":port" rather than setting *Port
18059 separately. Allow multiple instances of each BindAddress config
18060 option, so you can bind to multiple interfaces if you want.
18061 - Allow multiple exit policy lines, which are processed in order.
18062 Now we don't need that huge line with all the commas in it.
18063 - Enable accept/reject policies on SOCKS connections, so you can bind
18064 to 0.0.0.0 but still control who can use your OP.
18067 Changes in version 0.0.6.2 - 2004-05-16
18068 o Our integrity-checking digest was checking only the most recent cell,
18069 not the previous cells like we'd thought.
18070 Thanks to Stefan Mark for finding the flaw!
18073 Changes in version 0.0.6.1 - 2004-05-06
18074 o Fix two bugs in our AES counter-mode implementation (this affected
18075 onion-level stream encryption, but not TLS-level). It turns
18076 out we were doing something much more akin to a 16-character
18077 polyalphabetic cipher. Oops.
18078 Thanks to Stefan Mark for finding the flaw!
18079 o Retire moria3 as a directory server, and add tor26 as a directory
18083 Changes in version 0.0.6 - 2004-05-02
18084 [version bump only]
18087 Changes in version 0.0.6rc4 - 2004-05-01
18088 o Update the built-in dirservers list to use the new directory format
18089 o Fix a rare seg fault: if a node offering a hidden service attempts
18090 to build a circuit to Alice's rendezvous point and fails before it
18091 reaches the last hop, it retries with a different circuit, but
18093 o Handle windows socket errors correctly.
18096 Changes in version 0.0.6rc3 - 2004-04-28
18097 o Don't expire non-general excess circuits (if we had enough
18098 circuits open, we were expiring rendezvous circuits -- even
18099 when they had a stream attached. oops.)
18100 o Fetch randomness from /dev/urandom better (not via fopen/fread)
18101 o Better debugging for tls errors
18102 o Some versions of openssl have an SSL_pending function that erroneously
18103 returns bytes when there is a non-application record pending.
18104 o Set Content-Type on the directory and hidserv descriptor.
18105 o Remove IVs from cipher code, since AES-ctr has none.
18106 o Win32 fixes. Tor now compiles on win32 with no warnings/errors.
18107 o We were using an array of length zero in a few places.
18108 o win32's gethostbyname can't resolve an IP to an IP.
18109 o win32's close can't close a socket.
18112 Changes in version 0.0.6rc2 - 2004-04-26
18113 o Fix a bug where we were closing tls connections intermittently.
18114 It turns out openssl keeps its errors around -- so if an error
18115 happens, and you don't ask about it, and then another openssl
18116 operation happens and succeeds, and you ask if there was an error,
18117 it tells you about the first error. Fun fun.
18118 o Fix a bug that's been lurking since 27 may 03 (!)
18119 When passing back a destroy cell, we would use the wrong circ id.
18120 'Mostly harmless', but still worth fixing.
18121 o Since we don't support truncateds much, don't bother sending them;
18122 just close the circ.
18123 o check for <machine/limits.h> so we build on NetBSD again (I hope).
18124 o don't crash if a conn that sent a begin has suddenly lost its circuit
18125 (this was quite rare).
18128 Changes in version 0.0.6rc1 - 2004-04-25
18129 o We now rotate link (tls context) keys and onion keys.
18130 o CREATE cells now include oaep padding, so you can tell
18131 if you decrypted them correctly.
18132 o Add bandwidthburst to server descriptor.
18133 o Directories now say which dirserver signed them.
18134 o Use a tor_assert macro that logs failed assertions too.
18137 Changes in version 0.0.6pre5 - 2004-04-18
18138 o changes from 0.0.6pre4:
18139 - make tor build on broken freebsd 5.2 installs
18140 - fix a failed assert when you try an intro point, get a nack, and try
18141 a second one and it works.
18142 - when alice uses a port that the hidden service doesn't accept,
18143 it now sends back an end cell (denied by exit policy). otherwise
18144 alice would just have to wait to time out.
18145 - fix another rare bug: when we had tried all the intro
18146 points for a hidden service, we fetched the descriptor
18147 again, but we left our introcirc thinking it had already
18148 sent an intro, so it kept waiting for a response...
18149 - bugfix: when you sleep your hidden-service laptop, as soon
18150 as it wakes up it tries to upload a service descriptor, but
18151 socketpair fails for some reason (localhost not up yet?).
18152 now we simply give up on that upload, and we'll try again later.
18153 i'd still like to find the bug though.
18154 - if an intro circ waiting for an ack dies before getting one, then
18156 - we were reusing stale service descriptors and refetching usable
18160 Changes in version 0.0.6pre4 - 2004-04-14
18161 o changes from 0.0.6pre3:
18162 - when bob fails to connect to the rendezvous point, and his
18163 circ didn't fail because of the rendezvous point itself, then
18164 he retries a couple of times
18165 - we expire introduction and rendezvous circs more thoroughly
18166 (sometimes they were hanging around forever)
18167 - we expire unattached rendezvous streams that have been around
18168 too long (they were sticking around forever).
18169 - fix a measly fencepost error that was crashing everybody with
18173 Changes in version 0.0.6pre3 - 2004-04-14
18174 o changes from 0.0.6pre2:
18175 - make hup work again
18176 - fix some memory leaks for dirservers
18177 - allow more skew in rendezvous descriptor timestamps, to help
18178 handle people like blanu who don't know what time it is
18179 - normal circs are 3 hops, but some rend/intro circs are 4, if
18180 the initiator doesn't get to choose the last hop
18181 - send acks for introductions, so alice can know whether to try
18183 - bob publishes intro points more correctly
18184 o changes from 0.0.5:
18185 - fix an assert trigger that's been plaguing us since the days
18186 of 0.0.2prexx (thanks weasel!)
18187 - retry stream correctly when we fail to connect because of
18188 exit-policy-reject (should try another) or can't-resolve-address
18189 (also should try another, because dns on random internet servers
18191 - when we hup a dirserver and we've *removed* a server from the
18192 approved-routers list, now we remove that server from the
18193 in-memory directories too
18196 Changes in version 0.0.6pre2 - 2004-04-08
18197 o We fixed our base32 implementation. Now it works on all architectures.
18200 Changes in version 0.0.6pre1 - 2004-04-08
18202 - Hidden services and rendezvous points are implemented. Go to
18203 http://6sxoyfb3h2nvok2d.onion/ for an index of currently available
18204 hidden services. (This only works via a socks4a proxy such as
18205 Privoxy, and currently it's quite slow.)
18208 Changes in version 0.0.5 - 2004-03-30
18209 [version bump only]
18212 Changes in version 0.0.5rc3 - 2004-03-29
18213 o Install torrc as torrc.sample -- we no longer clobber your
18215 o Re-enable recommendedversion checking (we broke it in rc2, oops)
18216 o Add in a 'notice' log level for things the operator should hear
18217 but that aren't warnings
18220 Changes in version 0.0.5rc2 - 2004-03-29
18221 o Hold socks connection open until reply is flushed (if possible)
18222 o Make exit nodes resolve IPs to IPs immediately, rather than asking
18223 the dns farm to do it.
18224 o Fix c99 aliasing warnings in rephist.c
18225 o Don't include server descriptors that are older than 24 hours in the
18227 o Give socks 'reject' replies their whole 15s to attempt to flush,
18228 rather than seeing the 60s timeout and assuming the flush had failed.
18229 o Clean automake droppings from the cvs repository
18232 Changes in version 0.0.5rc1 - 2004-03-28
18233 o Fix mangled-state bug in directory fetching (was causing sigpipes).
18234 o Only build circuits after we've fetched the directory: clients were
18235 using only the directory servers before they'd fetched a directory.
18236 This also means longer startup time; so it goes.
18237 o Fix an assert trigger where an OP would fail to handshake, and we'd
18238 expect it to have a nickname.
18239 o Work around a tsocks bug: do a socks reject when AP connection dies
18240 early, else tsocks goes into an infinite loop.
18243 Changes in version 0.0.4 - 2004-03-26
18244 o When connecting to a dirserver or OR and the network is down,
18248 Changes in version 0.0.3 - 2004-03-26
18249 o Warn and fail if server chose a nickname with illegal characters
18250 o Port to Solaris and Sparc:
18251 - include missing header fcntl.h
18252 - have autoconf find -lsocket -lnsl automatically
18253 - deal with hardware word alignment
18254 - make uname() work (solaris has a different return convention)
18255 - switch from using signal() to sigaction()
18256 o Preliminary work on reputation system:
18257 - Keep statistics on success/fail of connect attempts; they're published
18258 by kill -USR1 currently.
18259 - Add a RunTesting option to try to learn link state by creating test
18260 circuits, even when SocksPort is off.
18261 - Remove unused open circuits when there are too many.
18264 Changes in version 0.0.2 - 2004-03-19
18265 - Include strlcpy and strlcat for safer string ops
18266 - define INADDR_NONE so we compile (but still not run) on solaris
18269 Changes in version 0.0.2pre27 - 2004-03-14
18271 - Allow internal tor networks (we were rejecting internal IPs,
18272 now we allow them if they're set explicitly).
18273 - And fix a few endian issues.
18276 Changes in version 0.0.2pre26 - 2004-03-14
18278 - If a stream times out after 15s without a connected cell, don't
18279 try that circuit again: try a new one.
18280 - Retry streams at most 4 times. Then give up.
18281 - When a dirserver gets a descriptor from an unknown router, it
18282 logs its fingerprint (so the dirserver operator can choose to
18283 accept it even without mail from the server operator).
18284 - Inform unapproved servers when we reject their descriptors.
18285 - Make tor build on Windows again. It works as a client, who knows
18287 - Clearer instructions in the torrc for how to set up a server.
18288 - Be more efficient about reading fd's when our global token bucket
18289 (used for rate limiting) becomes empty.
18291 - Stop asserting that computers always go forward in time. It's
18293 - When we sent a cell (e.g. destroy) and then marked an OR connection
18294 expired, we might close it before finishing a flush if the other
18295 side isn't reading right then.
18296 - Don't allow dirservers to start if they haven't defined
18297 RecommendedVersions
18298 - We were caching transient dns failures. Oops.
18299 - Prevent servers from publishing an internal IP as their address.
18300 - Address a strcat vulnerability in circuit.c
18303 Changes in version 0.0.2pre25 - 2004-03-04
18305 - Put the OR's IP in its router descriptor, not its fqdn. That way
18306 we'll stop being stalled by gethostbyname for nodes with flaky dns,
18309 - If the user typed in an address that didn't resolve, the server
18313 Changes in version 0.0.2pre24 - 2004-03-03
18315 - Fix an assertion failure in dns.c, where we were trying to dequeue
18316 a pending dns resolve even if it wasn't pending
18317 - Fix a spurious socks5 warning about still trying to write after the
18318 connection is finished.
18319 - Hold certain marked_for_close connections open until they're finished
18320 flushing, rather than losing bytes by closing them too early.
18321 - Correctly report the reason for ending a stream
18322 - Remove some duplicate calls to connection_mark_for_close
18323 - Put switch_id and start_daemon earlier in the boot sequence, so it
18324 will actually try to chdir() to options.DataDirectory
18325 - Make 'make test' exit(1) if a test fails; fix some unit tests
18326 - Make tor fail when you use a config option it doesn't know about,
18327 rather than warn and continue.
18328 - Make --version work
18329 - Bugfixes on the rpm spec file and tor.sh, so it's more up to date
18332 Changes in version 0.0.2pre23 - 2004-02-29
18334 - Print a statement when the first circ is finished, so the user
18335 knows it's working.
18336 - If a relay cell is unrecognized at the end of the circuit,
18337 send back a destroy. (So attacks to mutate cells are more
18339 - New config option 'excludenodes' to avoid certain nodes for circuits.
18340 - When it daemonizes, it chdir's to the DataDirectory rather than "/",
18341 so you can collect coredumps there.
18343 - Fix a bug in tls flushing where sometimes data got wedged and
18344 didn't flush until more data got sent. Hopefully this bug was
18345 a big factor in the random delays we were seeing.
18346 - Make 'connected' cells include the resolved IP, so the client
18347 dns cache actually gets populated.
18348 - Disallow changing from ORPort=0 to ORPort>0 on hup.
18349 - When we time-out on a stream and detach from the circuit, send an
18350 end cell down it first.
18351 - Only warn about an unknown router (in exitnodes, entrynodes,
18352 excludenodes) after we've fetched a directory.
18355 Changes in version 0.0.2pre22 - 2004-02-26
18357 - Servers publish less revealing uname information in descriptors.
18358 - More memory tracking and assertions, to crash more usefully when
18360 - If the default torrc isn't there, just use some default defaults.
18361 Plus provide an internal dirservers file if they don't have one.
18362 - When the user tries to use Tor as an http proxy, give them an http
18363 501 failure explaining that we're a socks proxy.
18364 - Dump a new router.desc on hup, to help confused people who change
18365 their exit policies and then wonder why router.desc doesn't reflect
18367 - Clean up the generic tor.sh init script that we ship with.
18369 - If the exit stream is pending on the resolve, and a destroy arrives,
18370 then the stream wasn't getting removed from the pending list. I
18371 think this was the one causing recent server crashes.
18372 - Use a more robust poll on OSX 10.3, since their poll is flaky.
18373 - When it couldn't resolve any dirservers, it was useless from then on.
18374 Now it reloads the RouterFile (or default dirservers) if it has no
18376 - Move the 'tor' binary back to /usr/local/bin/ -- it turns out
18377 many users don't even *have* a /usr/local/sbin/.
18380 Changes in version 0.0.2pre21 - 2004-02-18
18382 - There's a ChangeLog file that actually reflects the changelog.
18383 - There's a 'torify' wrapper script, with an accompanying
18384 tor-tsocks.conf, that simplifies the process of using tsocks for
18385 tor. It even has a man page.
18386 - The tor binary gets installed to sbin rather than bin now.
18387 - Retry streams where the connected cell hasn't arrived in 15 seconds
18388 - Clean up exit policy handling -- get the default out of the torrc,
18389 so we can update it without forcing each server operator to fix
18391 - Allow imaps and pop3s in default exit policy
18393 - Prevent picking middleman nodes as the last node in the circuit
18396 Changes in version 0.0.2pre20 - 2004-01-30
18398 - We now have a deb package, and it's in debian unstable. Go to
18399 it, apt-getters. :)
18400 - I've split the TotalBandwidth option into BandwidthRate (how many
18401 bytes per second you want to allow, long-term) and
18402 BandwidthBurst (how many bytes you will allow at once before the cap
18403 kicks in). This better token bucket approach lets you, say, set
18404 BandwidthRate to 10KB/s and BandwidthBurst to 10MB, allowing good
18405 performance while not exceeding your monthly bandwidth quota.
18406 - Push out a tls record's worth of data once you've got it, rather
18407 than waiting until you've read everything waiting to be read. This
18408 may improve performance by pipelining better. We'll see.
18409 - Add an AP_CONN_STATE_CONNECTING state, to allow streams to detach
18410 from failed circuits (if they haven't been connected yet) and attach
18412 - Expire old streams that haven't managed to connect. Some day we'll
18413 have them reattach to new circuits instead.
18416 - Fix several memory leaks that were causing servers to become bloated
18418 - Fix a few very rare assert triggers. A few more remain.
18419 - Setuid to User _before_ complaining about running as root.
18422 Changes in version 0.0.2pre19 - 2004-01-07
18424 - Fix deadlock condition in dns farm. We were telling a child to die by
18425 closing the parent's file descriptor to him. But newer children were
18426 inheriting the open file descriptor from the parent, and since they
18427 weren't closing it, the socket never closed, so the child never read
18428 eof, so he never knew to exit. Similarly, dns workers were holding
18429 open other sockets, leading to all sorts of chaos.
18430 - New cleaner daemon() code for forking and backgrounding.
18431 - If you log to a file, it now prints an entry at the top of the
18432 logfile so you know it's working.
18433 - The onionskin challenge length was 30 bytes longer than necessary.
18434 - Started to patch up the spec so it's not quite so out of date.
18437 Changes in version 0.0.2pre18 - 2004-01-02
18439 - Fix endian issues with the 'integrity' field in the relay header.
18440 - Fix a potential bug where connections in state
18441 AP_CONN_STATE_CIRCUIT_WAIT might unexpectedly ask to write.
18444 Changes in version 0.0.2pre17 - 2003-12-30
18446 - Made --debuglogfile (or any second log file, actually) work.
18447 - Resolved an edge case in get_unique_circ_id_by_conn where a smart
18448 adversary could force us into an infinite loop.
18451 - Each onionskin handshake now includes a hash of the computed key,
18452 to prove the server's identity and help perfect forward secrecy.
18453 - Changed cell size from 256 to 512 bytes (working toward compatibility
18455 - Changed cell length to 2 bytes, and moved it to the relay header.
18456 - Implemented end-to-end integrity checking for the payloads of
18458 - Separated streamid from 'recognized' (otherwise circuits will get
18459 messed up when we try to have streams exit from the middle). We
18460 use the integrity-checking to confirm that a cell is addressed to
18462 - Randomize the initial circid and streamid values, so an adversary who
18463 breaks into a node can't learn how many circuits or streams have
18467 Changes in version 0.0.2pre16 - 2003-12-14
18469 - Fixed a bug that made HUP trigger an assert
18470 - Fixed a bug where a circuit that immediately failed wasn't being
18471 counted as a failed circuit in counting retries.
18474 - Now we close the circuit when we get a truncated cell: otherwise we're
18475 open to an anonymity attack where a bad node in the path truncates
18476 the circuit and then we open streams at him.
18477 - Add port ranges to exit policies
18478 - Add a conservative default exit policy
18479 - Warn if you're running tor as root
18480 - on HUP, retry OR connections and close/rebind listeners
18481 - options.EntryNodes: try these nodes first when picking the first node
18482 - options.ExitNodes: if your best choices happen to include any of
18483 your preferred exit nodes, you choose among just those preferred
18485 - options.ExcludedNodes: nodes that are never picked in path building
18488 Changes in version 0.0.2pre15 - 2003-12-03
18489 o Robustness and bugfixes:
18490 - Sometimes clients would cache incorrect DNS resolves, which would
18491 really screw things up.
18492 - An OP that goes offline would slowly leak all its sockets and stop
18494 - A wide variety of bugfixes in exit node selection, exit policy
18495 handling, and processing pending streams when a new circuit is
18497 - Pick nodes for a path only from those the directory says are up
18498 - Choose randomly from all running dirservers, not always the first one
18499 - Increase allowed http header size for directory fetch.
18500 - Stop writing to stderr (if we're daemonized it will be closed).
18501 - Enable -g always, so cores will be more useful to me.
18502 - Switch "-lcrypto -lssl" to "-lssl -lcrypto" for broken distributions.
18505 - Wrote a man page. It lists commonly used options.
18508 - Change default loglevel to warn.
18509 - Make PidFile default to null rather than littering in your CWD.
18510 - OnionRouter config option is now obsolete. Instead it just checks
18512 - Moved to a single unified torrc file for both clients and servers.
18515 Changes in version 0.0.2pre14 - 2003-11-29
18516 o Robustness and bugfixes:
18517 - Force the admin to make the DataDirectory himself
18518 - to get ownership/permissions right
18519 - so clients no longer make a DataDirectory and then never use it
18520 - fix bug where a client who was offline for 45 minutes would never
18521 pull down a directory again
18522 - fix (or at least hide really well) the dns assert bug that was
18523 causing server crashes
18524 - warnings and improved robustness wrt clockskew for certs
18525 - use the native daemon(3) to daemonize, when available
18526 - exit if bind() fails
18527 - exit if neither socksport nor orport is defined
18528 - include our own tor_timegm (Win32 doesn't have its own)
18529 - bugfix for win32 with lots of connections
18530 - fix minor bias in PRNG
18531 - make dirserver more robust to corrupt cached directory
18534 - Wrote the design document (woo)
18536 o Circuit building and exit policies:
18537 - Circuits no longer try to use nodes that the directory has told them
18539 - Exit policies now support bitmasks (18.0.0.0/255.0.0.0) and
18540 bitcounts (18.0.0.0/8).
18541 - Make AP connections standby for a circuit if no suitable circuit
18542 exists, rather than failing
18543 - Circuits choose exit node based on addr/port, exit policies, and
18544 which AP connections are standing by
18545 - Bump min pathlen from 2 to 3
18546 - Relay end cells have a payload to describe why the stream ended.
18547 - If the stream failed because of exit policy, try again with a new
18549 - Clients have a dns cache to remember resolved addresses.
18550 - Notice more quickly when we have no working circuits
18553 - APPort is now called SocksPort
18554 - SocksBindAddress, ORBindAddress, DirBindAddress let you configure
18556 - RecommendedVersions is now a config variable rather than
18557 hardcoded (for dirservers)
18558 - Reloads config on HUP
18559 - Usage info on -h or --help
18560 - If you set User and Group config vars, it'll setu/gid to them.
18563 Changes in version 0.0.2pre13 - 2003-10-19
18564 o General stability:
18565 - SSL_write no longer fails when it returns WANTWRITE and the number
18566 of bytes in the buf has changed by the next SSL_write call.
18567 - Fix segfault fetching directory when network is down
18568 - Fix a variety of minor memory leaks
18569 - Dirservers reload the fingerprints file on HUP, so I don't have
18570 to take down the network when I approve a new router
18571 - Default server config file has explicit Address line to specify fqdn
18574 - Buffers grow and shrink as needed (Cut process size from 20M to 2M)
18575 - Make listener connections not ever alloc bufs
18577 o Autoconf improvements:
18578 - don't clobber an external CFLAGS in ./configure
18579 - Make install now works
18580 - create var/lib/tor on make install
18581 - autocreate a tor.sh initscript to help distribs
18582 - autocreate the torrc and sample-server-torrc with correct paths
18584 o Log files and Daemonizing now work:
18585 - If --DebugLogFile is specified, log to it at -l debug
18586 - If --LogFile is specified, use it instead of commandline
18587 - If --RunAsDaemon is set, tor forks and backgrounds on startup