1 Changes in version 0.2.7.2-alpha - 2015-0?-??
3 Changes in version 0.2.6.9 - 2015-06-11
4 Tor 0.2.6.9 fixes a regression in the circuit isolation code, increases the
5 requirements for receiving an HSDir flag, and addresses some other small
6 bugs in the systemd and sandbox code. Clients using circuit isolation
7 should upgrade; all directory authorities should upgrade.
9 o Major bugfixes (client-side privacy):
10 - Properly separate out each SOCKSPort when applying stream
11 isolation. The error occurred because each port's session group was
12 being overwritten by a default value when the listener connection
13 was initialized. Fixes bug 16247; bugfix on 0.2.6.3-alpha. Patch
16 o Minor feature (directory authorities, security):
17 - The HSDir flag given by authorities now requires the Stable flag.
18 For the current network, this results in going from 2887 to 2806
19 HSDirs. Also, it makes it harder for an attacker to launch a sybil
20 attack by raising the effort for a relay to become Stable which
21 takes at the very least 7 days to do so and by keeping the 96
22 hours uptime requirement for HSDir. Implements ticket 8243.
24 o Minor bugfixes (compilation):
25 - Build with --enable-systemd correctly when libsystemd is
26 installed, but systemd is not. Fixes bug 16164; bugfix on
27 0.2.6.3-alpha. Patch from Peter Palfrader.
29 o Minor bugfixes (Linux seccomp2 sandbox):
30 - Fix sandboxing to work when running as a relaymby renaming of
31 secret_id_key, and allowing the eventfd2 and futex syscalls. Fixes
32 bug 16244; bugfix on 0.2.6.1-alpha. Patch by Peter Palfrader.
33 - Allow systemd connections to work with the Linux seccomp2 sandbox
34 code. Fixes bug 16212; bugfix on 0.2.6.2-alpha. Patch by
37 o Minor bugfixes (tests):
38 - Fix a crash in the unit tests when built with MSVC2013. Fixes bug
39 16030; bugfix on 0.2.6.2-alpha. Patch from "NewEraCracker".
42 Changes in version 0.2.6.8 - 2015-05-21
43 Tor 0.2.6.8 fixes a bit of dodgy code in parsing INTRODUCE2 cells, and
44 fixes an authority-side bug in assigning the HSDir flag. All directory
45 authorities should upgrade.
47 o Major bugfixes (hidden services, backport from 0.2.7.1-alpha):
48 - Revert commit that made directory authorities assign the HSDir
49 flag to relay without a DirPort; this was bad because such relays
50 can't handle BEGIN_DIR cells. Fixes bug 15850; bugfix
53 o Minor bugfixes (hidden service, backport from 0.2.7.1-alpha):
54 - Fix an out-of-bounds read when parsing invalid INTRODUCE2 cells on
55 a client authorized hidden service. Fixes bug 15823; bugfix
58 o Minor features (geoip):
59 - Update geoip to the April 8 2015 Maxmind GeoLite2 Country database.
60 - Update geoip6 to the April 8 2015 Maxmind GeoLite2
64 Changes in version 0.2.7.1-alpha - 2015-05-12
65 Tor 0.2.7.1-alpha is the first alpha release in its series. It
66 includes numerous small features and bugfixes against previous Tor
67 versions, and numerous small infrastructure improvements. The most
68 notable features are several new ways for controllers to interact with
69 the hidden services subsystem.
71 o New system requirements:
72 - Tor no longer includes workarounds to support Libevent versions
73 before 1.3e. Libevent 2.0 or later is recommended. Closes
76 o Major features (controller):
77 - Add the ADD_ONION and DEL_ONION commands that allow the creation
78 and management of hidden services via the controller. Closes
80 - New "GETINFO onions/current" and "GETINFO onions/detached"
81 commands to get information about hidden services created via the
82 controller. Part of ticket 6411.
83 - New HSFETCH command to launch a request for a hidden service
84 descriptor. Closes ticket 14847.
85 - New HSPOST command to upload a hidden service descriptor. Closes
86 ticket 3523. Patch by "DonnchaC".
88 o Major bugfixes (hidden services):
89 - Revert commit that made directory authorities assign the HSDir
90 flag to relay without a DirPort; this was bad because such relays
91 can't handle BEGIN_DIR cells. Fixes bug 15850; bugfix
94 o Minor features (clock-jump tolerance):
95 - Recover better when our clock jumps back many hours, like might
96 happen for Tails or Whonix users who start with a very wrong
97 hardware clock, use Tor to discover a more accurate time, and then
98 fix their clock. Resolves part of ticket 8766.
100 o Minor features (command-line interface):
101 - Make --hash-password imply --hush to prevent unnecessary noise.
102 Closes ticket 15542. Patch from "cypherpunks".
103 - Print a warning whenever we find a relative file path being used
104 as torrc option. Resolves issue 14018.
106 o Minor features (controller):
107 - Add DirAuthority lines for default directory authorities to the
108 output of the "GETINFO config/defaults" command if not already
109 present. Implements ticket 14840.
110 - Controllers can now use "GETINFO hs/client/desc/id/..." to
111 retrieve items from the client's hidden service descriptor cache.
113 - Implement a new controller command "GETINFO status/fresh-relay-
114 descs" to fetch a descriptor/extrainfo pair that was generated on
115 demand just for the controller's use. Implements ticket 14784.
117 o Minor features (DoS-resistance):
118 - Make it harder for attackers to overload hidden services with
119 introductions, by blocking multiple introduction requests on the
120 same circuit. Resolves ticket 15515.
122 o Minor features (geoip):
123 - Update geoip to the April 8 2015 Maxmind GeoLite2 Country database.
124 - Update geoip6 to the April 8 2015 Maxmind GeoLite2
127 o Minor features (HS popularity countermeasure):
128 - To avoid leaking HS popularity, don't cycle the introduction point
129 when we've handled a fixed number of INTRODUCE2 cells but instead
130 cycle it when a random number of introductions is reached, thus
131 making it more difficult for an attacker to find out the amount of
132 clients that have used the introduction point for a specific HS.
135 o Minor features (logging):
136 - Include the Tor version in all LD_BUG log messages, since people
137 tend to cut and paste those into the bugtracker. Implements
140 o Minor features (pluggable transports):
141 - When launching managed pluggable transports on Linux systems,
142 attempt to have the kernel deliver a SIGTERM on tor exit if the
143 pluggable transport process is still running. Resolves
145 - When launching managed pluggable transports, setup a valid open
146 stdin in the child process that can be used to detect if tor has
147 terminated. The "TOR_PT_EXIT_ON_STDIN_CLOSE" environment variable
148 can be used by implementations to detect this new behavior.
149 Resolves ticket 15435.
151 o Minor features (testing):
152 - Add a test to verify that the compiler does not eliminate our
153 memwipe() implementation. Closes ticket 15377.
154 - Add make rule `check-changes` to verify the format of changes
155 files. Closes ticket 15180.
156 - Add unit tests for control_event_is_interesting(). Add a compile-
157 time check that the number of events doesn't exceed the capacity
158 of control_event_t.event_mask. Closes ticket 15431, checks for
159 bugs similar to 13085. Patch by "teor".
160 - Command-line argument tests moved to Stem. Resolves ticket 14806.
161 - Integrate the ntor, backtrace, and zero-length keys tests into the
162 automake test suite. Closes ticket 15344.
163 - Remove assertions during builds to determine Tor's test coverage.
164 We don't want to trigger these even in assertions, so including
165 them artificially makes our branch coverage look worse than it is.
166 This patch provides the new test-stem-full and coverage-html-full
167 configure options. Implements ticket 15400.
169 o Minor bugfixes (build):
170 - Improve out-of-tree builds by making non-standard rules work and
171 clean up additional files and directories. Fixes bug 15053; bugfix
174 o Minor bugfixes (command-line interface):
175 - When "--quiet" is provided along with "--validate-config", do not
176 write anything to stdout on success. Fixes bug 14994; bugfix
178 - When complaining about bad arguments to "--dump-config", use
181 o Minor bugfixes (configuration, unit tests):
182 - Only add the default fallback directories when the DirAuthorities,
183 AlternateDirAuthority, and FallbackDir directory config options
184 are set to their defaults. The default fallback directory list is
185 currently empty, this fix will only change tor's behavior when it
186 has default fallback directories. Includes unit tests for
187 consider_adding_dir_servers(). Fixes bug 15642; bugfix on
188 90f6071d8dc0 in 0.2.4.7-alpha. Patch by "teor".
190 o Minor bugfixes (correctness):
191 - For correctness, avoid modifying a constant string in
192 handle_control_postdescriptor. Fixes bug 15546; bugfix
194 - Remove side-effects from tor_assert() calls. This was harmless,
195 because we never disable assertions, but it is bad style and
196 unnecessary. Fixes bug 15211; bugfix on 0.2.5.5, 0.2.2.36,
199 o Minor bugfixes (hidden service):
200 - Fix an out-of-bounds read when parsing invalid INTRODUCE2 cells on
201 a client authorized hidden service. Fixes bug 15823; bugfix
203 - Remove an extraneous newline character from the end of hidden
204 service descriptors. Fixes bug 15296; bugfix on 0.2.0.10-alpha.
206 o Minor bugfixes (interface):
207 - Print usage information for --dump-config when it is used without
208 an argument. Also, fix the error message to use different wording
209 and add newline at the end. Fixes bug 15541; bugfix
212 o Minor bugfixes (logs):
213 - When building Tor under Clang, do not include an extra set of
214 parentheses in log messages that include function names. Fixes bug
215 15269; bugfix on every released version of Tor when compiled with
218 o Minor bugfixes (network):
219 - When attempting to use fallback technique for network interface
220 lookup, disregard loopback and multicast addresses since they are
221 unsuitable for public communications.
223 o Minor bugfixes (statistics):
224 - Disregard the ConnDirectionStatistics torrc options when Tor is
225 not a relay since in that mode of operation no sensible data is
226 being collected and because Tor might run into measurement hiccups
227 when running as a client for some time, then becoming a relay.
228 Fixes bug 15604; bugfix on 0.2.2.35.
230 o Minor bugfixes (test networks):
231 - When self-testing reachability, use ExtendAllowPrivateAddresses to
232 determine if local/private addresses imply reachability. The
233 previous fix used TestingTorNetwork, which implies
234 ExtendAllowPrivateAddresses, but this excluded rare configurations
235 where ExtendAllowPrivateAddresses is set but TestingTorNetwork is
236 not. Fixes bug 15771; bugfix on 0.2.6.1-alpha. Patch by "teor",
237 issue discovered by CJ Ess.
239 o Minor bugfixes (testing):
240 - Check for matching value in server response in ntor_ref.py. Fixes
241 bug 15591; bugfix on 0.2.4.8-alpha. Reported and fixed
243 - Set the severity correctly when testing
244 get_interface_addresses_ifaddrs() and
245 get_interface_addresses_win32(), so that the tests fail gracefully
246 instead of triggering an assertion. Fixes bug 15759; bugfix on
247 0.2.6.3-alpha. Reported by Nicolas Derive.
249 o Code simplification and refactoring:
250 - Move the hacky fallback code out of get_interface_address6() into
251 separate function and get it covered with unit-tests. Resolves
253 - Refactor hidden service client-side cache lookup to intelligently
254 report its various failure cases, and disentangle failure cases
255 involving a lack of introduction points. Closes ticket 14391.
256 - Use our own Base64 encoder instead of OpenSSL's, to allow more
257 control over the output. Part of ticket 15652.
260 - Improve the descriptions of statistics-related torrc options in
261 the manpage to describe rationale and possible uses cases. Fixes
263 - Improve the layout and formatting of ./configure --help messages.
264 Closes ticket 15024. Patch from "cypherpunks".
265 - Standardize on the term "server descriptor" in the manual page.
266 Previously, we had used "router descriptor", "server descriptor",
267 and "relay descriptor" interchangeably. Part of ticket 14987.
270 - Remove `USE_OPENSSL_BASE64` and the corresponding fallback code
271 and always use the internal Base64 decoder. The internal decoder
272 has been part of tor since tor-0.2.0.10-alpha, and no one should
273 be using the OpenSSL one. Part of ticket 15652.
274 - Remove the 'tor_strclear()' function; use memwipe() instead.
278 - Remove the (seldom-used) DynamicDHGroups feature. For anti-
279 fingerprinting we now recommend pluggable transports; for forward-
280 secrecy in TLS, we now use the P-256 group. Closes ticket 13736.
281 - Remove the undocumented "--digests" command-line option. It
282 complicated our build process, caused subtle build issues on
283 multiple platforms, and is now redundant since we started
284 including git version identifiers. Closes ticket 14742.
285 - Tor no longer contains checks for ancient directory cache versions
286 that didn't know about microdescriptors.
287 - Tor no longer contains workarounds for stat files generated by
288 super-old versions of Tor that didn't choose guards sensibly.
291 Changes in version 0.2.4.27 - 2015-04-06
292 Tor 0.2.4.27 backports two fixes from 0.2.6.7 for security issues that
293 could be used by an attacker to crash hidden services, or crash clients
294 visiting hidden services. Hidden services should upgrade as soon as
295 possible; clients should upgrade whenever packages become available.
297 This release also backports a simple improvement to make hidden
298 services a bit less vulnerable to denial-of-service attacks.
300 o Major bugfixes (security, hidden service):
301 - Fix an issue that would allow a malicious client to trigger an
302 assertion failure and halt a hidden service. Fixes bug 15600;
303 bugfix on 0.2.1.6-alpha. Reported by "disgleirio".
304 - Fix a bug that could cause a client to crash with an assertion
305 failure when parsing a malformed hidden service descriptor. Fixes
306 bug 15601; bugfix on 0.2.1.5-alpha. Found by "DonnchaC".
308 o Minor features (DoS-resistance, hidden service):
309 - Introduction points no longer allow multiple INTRODUCE1 cells to
310 arrive on the same circuit. This should make it more expensive for
311 attackers to overwhelm hidden services with introductions.
312 Resolves ticket 15515.
315 Changes in version 0.2.6.7 - 2015-04-06
316 Tor 0.2.6.7 fixes two security issues that could be used by an
317 attacker to crash hidden services, or crash clients visiting hidden
318 services. Hidden services should upgrade as soon as possible; clients
319 should upgrade whenever packages become available.
321 This release also contains two simple improvements to make hidden
322 services a bit less vulnerable to denial-of-service attacks.
324 o Major bugfixes (security, hidden service):
325 - Fix an issue that would allow a malicious client to trigger an
326 assertion failure and halt a hidden service. Fixes bug 15600;
327 bugfix on 0.2.1.6-alpha. Reported by "disgleirio".
328 - Fix a bug that could cause a client to crash with an assertion
329 failure when parsing a malformed hidden service descriptor. Fixes
330 bug 15601; bugfix on 0.2.1.5-alpha. Found by "DonnchaC".
332 o Minor features (DoS-resistance, hidden service):
333 - Introduction points no longer allow multiple INTRODUCE1 cells to
334 arrive on the same circuit. This should make it more expensive for
335 attackers to overwhelm hidden services with introductions.
336 Resolves ticket 15515.
337 - Decrease the amount of reattempts that a hidden service performs
338 when its rendezvous circuits fail. This reduces the computational
339 cost for running a hidden service under heavy load. Resolves
343 Changes in version 0.2.6.6 - 2015-03-24
344 Tor 0.2.6.6 is the first stable release in the 0.2.6 series.
346 It adds numerous safety, security, correctness, and performance
347 improvements. Client programs can be configured to use more kinds of
348 sockets, AutomapHosts works better, the multithreading backend is
349 improved, cell transmission is refactored, test coverage is much
350 higher, more denial-of-service attacks are handled, guard selection is
351 improved to handle long-term guards better, pluggable transports
352 should work a bit better, and some annoying hidden service performance
353 bugs should be addressed.
355 o Minor bugfixes (portability):
356 - Use the correct datatype in the SipHash-2-4 function to prevent
357 compilers from assuming any sort of alignment. Fixes bug 15436;
358 bugfix on 0.2.5.3-alpha.
360 Changes in version 0.2.6.5-rc - 2015-03-18
361 Tor 0.2.6.5-rc is the second and (hopefully) last release candidate in
362 the 0.2.6. It fixes a small number of bugs found in 0.2.6.4-rc.
364 o Major bugfixes (client):
365 - Avoid crashing when making certain configuration option changes on
366 clients. Fixes bug 15245; bugfix on 0.2.6.3-alpha. Reported
369 o Major bugfixes (pluggable transports):
370 - Initialize the extended OR Port authentication cookie before
371 launching pluggable transports. This prevents a race condition
372 that occured when server-side pluggable transports would cache the
373 authentication cookie before it has been (re)generated. Fixes bug
374 15240; bugfix on 0.2.5.1-alpha.
376 o Major bugfixes (portability):
377 - Do not crash on startup when running on Solaris. Fixes a bug
378 related to our fix for 9495; bugfix on 0.2.6.1-alpha. Reported
381 o Minor features (heartbeat):
382 - On relays, report how many connections we negotiated using each
383 version of the Tor link protocols. This information will let us
384 know if removing support for very old versions of the Tor
385 protocols is harming the network. Closes ticket 15212.
387 o Code simplification and refactoring:
388 - Refactor main loop to extract the 'loop' part. This makes it
389 easier to run Tor under Shadow. Closes ticket 15176.
392 Changes in version 0.2.5.11 - 2015-03-17
393 Tor 0.2.5.11 is the second stable release in the 0.2.5 series.
395 It backports several bugfixes from the 0.2.6 branch, including a
396 couple of medium-level security fixes for relays and exit nodes.
397 It also updates the list of directory authorities.
399 o Directory authority changes:
400 - Remove turtles as a directory authority.
401 - Add longclaw as a new (v3) directory authority. This implements
402 ticket 13296. This keeps the directory authority count at 9.
403 - The directory authority Faravahar has a new IP address. This
406 o Major bugfixes (crash, OSX, security):
407 - Fix a remote denial-of-service opportunity caused by a bug in
408 OSX's _strlcat_chk() function. Fixes bug 15205; bug first appeared
411 o Major bugfixes (relay, stability, possible security):
412 - Fix a bug that could lead to a relay crashing with an assertion
413 failure if a buffer of exactly the wrong layout was passed to
414 buf_pullup() at exactly the wrong time. Fixes bug 15083; bugfix on
415 0.2.0.10-alpha. Patch from 'cypherpunks'.
416 - Do not assert if the 'data' pointer on a buffer is advanced to the
417 very end of the buffer; log a BUG message instead. Only assert if
418 it is past that point. Fixes bug 15083; bugfix on 0.2.0.10-alpha.
420 o Major bugfixes (exit node stability):
421 - Fix an assertion failure that could occur under high DNS load.
422 Fixes bug 14129; bugfix on Tor 0.0.7rc1. Found by "jowr";
423 diagnosed and fixed by "cypherpunks".
425 o Major bugfixes (Linux seccomp2 sandbox):
426 - Upon receiving sighup with the seccomp2 sandbox enabled, do not
427 crash during attempts to call wait4. Fixes bug 15088; bugfix on
428 0.2.5.1-alpha. Patch from "sanic".
430 o Minor features (controller):
431 - New "GETINFO bw-event-cache" to get information about recent
432 bandwidth events. Closes ticket 14128. Useful for controllers to
433 get recent bandwidth history after the fix for ticket 13988.
435 o Minor features (geoip):
436 - Update geoip to the March 3 2015 Maxmind GeoLite2 Country database.
437 - Update geoip6 to the March 3 2015 Maxmind GeoLite2
440 o Minor bugfixes (client, automapping):
441 - Avoid crashing on torrc lines for VirtualAddrNetworkIPv[4|6] when
442 no value follows the option. Fixes bug 14142; bugfix on
443 0.2.4.7-alpha. Patch by "teor".
444 - Fix a memory leak when using AutomapHostsOnResolve. Fixes bug
445 14195; bugfix on 0.1.0.1-rc.
447 o Minor bugfixes (compilation):
448 - Build without warnings with the stock OpenSSL srtp.h header, which
449 has a duplicate declaration of SSL_get_selected_srtp_profile().
450 Fixes bug 14220; this is OpenSSL's bug, not ours.
452 o Minor bugfixes (directory authority):
453 - Allow directory authorities to fetch more data from one another if
454 they find themselves missing lots of votes. Previously, they had
455 been bumping against the 10 MB queued data limit. Fixes bug 14261;
456 bugfix on 0.1.2.5-alpha.
457 - Enlarge the buffer to read bwauth generated files to avoid an
458 issue when parsing the file in dirserv_read_measured_bandwidths().
459 Fixes bug 14125; bugfix on 0.2.2.1-alpha.
461 o Minor bugfixes (statistics):
462 - Increase period over which bandwidth observations are aggregated
463 from 15 minutes to 4 hours. Fixes bug 13988; bugfix on 0.0.8pre1.
465 o Minor bugfixes (preventative security, C safety):
466 - When reading a hexadecimal, base-32, or base-64 encoded value from
467 a string, always overwrite the whole output buffer. This prevents
468 some bugs where we would look at (but fortunately, not reveal)
469 uninitialized memory on the stack. Fixes bug 14013; bugfix on all
473 Changes in version 0.2.4.26 - 2015-03-17
474 Tor 0.2.4.26 includes an updated list of directory authorities. It
475 also backports a couple of stability and security bugfixes from 0.2.5
478 o Directory authority changes:
479 - Remove turtles as a directory authority.
480 - Add longclaw as a new (v3) directory authority. This implements
481 ticket 13296. This keeps the directory authority count at 9.
482 - The directory authority Faravahar has a new IP address. This
485 o Major bugfixes (exit node stability, also in 0.2.6.3-alpha):
486 - Fix an assertion failure that could occur under high DNS load.
487 Fixes bug 14129; bugfix on Tor 0.0.7rc1. Found by "jowr";
488 diagnosed and fixed by "cypherpunks".
490 o Major bugfixes (relay, stability, possible security, also in 0.2.6.4-rc):
491 - Fix a bug that could lead to a relay crashing with an assertion
492 failure if a buffer of exactly the wrong layout was passed to
493 buf_pullup() at exactly the wrong time. Fixes bug 15083; bugfix on
494 0.2.0.10-alpha. Patch from 'cypherpunks'.
495 - Do not assert if the 'data' pointer on a buffer is advanced to the
496 very end of the buffer; log a BUG message instead. Only assert if
497 it is past that point. Fixes bug 15083; bugfix on 0.2.0.10-alpha.
499 o Minor features (geoip):
500 - Update geoip to the March 3 2015 Maxmind GeoLite2 Country database.
501 - Update geoip6 to the March 3 2015 Maxmind GeoLite2
504 Changes in version 0.2.6.4-rc - 2015-03-09
505 Tor 0.2.6.4-alpha fixes an issue in the directory code that an
506 attacker might be able to use in order to crash certain Tor
507 directories. It also resolves some minor issues left over from, or
508 introduced in, Tor 0.2.6.3-alpha or earlier.
510 o Major bugfixes (crash, OSX, security):
511 - Fix a remote denial-of-service opportunity caused by a bug in
512 OSX's _strlcat_chk() function. Fixes bug 15205; bug first appeared
515 o Major bugfixes (relay, stability, possible security):
516 - Fix a bug that could lead to a relay crashing with an assertion
517 failure if a buffer of exactly the wrong layout is passed to
518 buf_pullup() at exactly the wrong time. Fixes bug 15083; bugfix on
519 0.2.0.10-alpha. Patch from "cypherpunks".
520 - Do not assert if the 'data' pointer on a buffer is advanced to the
521 very end of the buffer; log a BUG message instead. Only assert if
522 it is past that point. Fixes bug 15083; bugfix on 0.2.0.10-alpha.
524 o Major bugfixes (FreeBSD IPFW transparent proxy):
525 - Fix address detection with FreeBSD transparent proxies, when
526 "TransProxyType ipfw" is in use. Fixes bug 15064; bugfix
529 o Major bugfixes (Linux seccomp2 sandbox):
530 - Pass IPPROTO_TCP rather than 0 to socket(), so that the Linux
531 seccomp2 sandbox doesn't fail. Fixes bug 14989; bugfix
533 - Allow AF_UNIX hidden services to be used with the seccomp2
534 sandbox. Fixes bug 15003; bugfix on 0.2.6.3-alpha.
535 - Upon receiving sighup with the seccomp2 sandbox enabled, do not
536 crash during attempts to call wait4. Fixes bug 15088; bugfix on
537 0.2.5.1-alpha. Patch from "sanic".
539 o Minor features (controller):
540 - Messages about problems in the bootstrap process now include
541 information about the server we were trying to connect to when we
542 noticed the problem. Closes ticket 15006.
544 o Minor features (geoip):
545 - Update geoip to the March 3 2015 Maxmind GeoLite2 Country database.
546 - Update geoip6 to the March 3 2015 Maxmind GeoLite2
549 o Minor features (logs):
550 - Quiet some log messages in the heartbeat and at startup. Closes
553 o Minor bugfixes (certificate handling):
554 - If an authority operator accidentally makes a signing certificate
555 with a future publication time, do not discard its real signing
556 certificates. Fixes bug 11457; bugfix on 0.2.0.3-alpha.
557 - Remove any old authority certificates that have been superseded
558 for at least two days. Previously, we would keep superseded
559 certificates until they expired, if they were published close in
560 time to the certificate that superseded them. Fixes bug 11454;
561 bugfix on 0.2.1.8-alpha.
563 o Minor bugfixes (compilation):
564 - Fix a compilation warning on s390. Fixes bug 14988; bugfix
566 - Fix a compilation warning on FreeBSD. Fixes bug 15151; bugfix
569 o Minor bugfixes (testing):
570 - Fix endianness issues in unit test for resolve_my_address() to
571 have it pass on big endian systems. Fixes bug 14980; bugfix on
573 - Avoid a side-effect in a tor_assert() in the unit tests. Fixes bug
574 15188; bugfix on 0.1.2.3-alpha. Patch from Tom van der Woerdt.
575 - When running the new 'make test-stem' target, use the configured
576 python binary. Fixes bug 15037; bugfix on 0.2.6.3-alpha. Patch
578 - When running the zero-length-keys tests, do not use the default
579 torrc file. Fixes bug 15033; bugfix on 0.2.6.3-alpha. Reported
582 o Directory authority IP change:
583 - The directory authority Faravahar has a new IP address. This
587 - Remove some lingering dead code that once supported mempools.
588 Mempools were disabled by default in 0.2.5, and removed entirely
589 in 0.2.6.3-alpha. Closes more of ticket 14848; patch
593 Changes in version 0.2.6.3-alpha - 2015-02-19
594 Tor 0.2.6.3-alpha is the third (and hopefully final) alpha release in
595 the 0.2.6.x series. It introduces support for more kinds of sockets,
596 makes it harder to accidentally run an exit, improves our
597 multithreading backend, incorporates several fixes for the
598 AutomapHostsOnResolve option, and fixes numerous other bugs besides.
600 If no major regressions or security holes are found in this version,
601 the next version will be a release candidate.
603 o Deprecated versions:
604 - Tor relays older than 0.2.4.18-rc are no longer allowed to
605 advertise themselves on the network. Closes ticket 13555.
607 o Major features (security, unix domain sockets):
608 - Allow SocksPort to be an AF_UNIX Unix Domain Socket. Now high risk
609 applications can reach Tor without having to create AF_INET or
610 AF_INET6 sockets, meaning they can completely disable their
611 ability to make non-Tor network connections. To create a socket of
612 this type, use "SocksPort unix:/path/to/socket". Implements
614 - Support mapping hidden service virtual ports to AF_UNIX sockets.
615 The syntax is "HiddenServicePort 80 unix:/path/to/socket".
616 Implements ticket 11485.
618 o Major features (changed defaults):
619 - Prevent relay operators from unintentionally running exits: When a
620 relay is configured as an exit node, we now warn the user unless
621 the "ExitRelay" option is set to 1. We warn even more loudly if
622 the relay is configured with the default exit policy, since this
623 can indicate accidental misconfiguration. Setting "ExitRelay 0"
624 stops Tor from running as an exit relay. Closes ticket 10067.
626 o Major features (directory system):
627 - When downloading server- or microdescriptors from a directory
628 server, we no longer launch multiple simultaneous requests to the
629 same server. This reduces load on the directory servers,
630 especially when directory guards are in use. Closes ticket 9969.
631 - When downloading server- or microdescriptors over a tunneled
632 connection, do not limit the length of our requests to what the
633 Squid proxy is willing to handle. Part of ticket 9969.
634 - Authorities can now vote on the correct digests and latest
635 versions for different software packages. This allows packages
636 that include Tor to use the Tor authority system as a way to get
637 notified of updates and their correct digests. Implements proposal
638 227. Closes ticket 10395.
640 o Major features (guards):
641 - Introduce the Guardfraction feature to improves load balancing on
642 guard nodes. Specifically, it aims to reduce the traffic gap that
643 guard nodes experience when they first get the Guard flag. This is
644 a required step if we want to increase the guard lifetime to 9
645 months or greater. Closes ticket 9321.
647 o Major features (performance):
648 - Make the CPU worker implementation more efficient by avoiding the
649 kernel and lengthening pipelines. The original implementation used
650 sockets to transfer data from the main thread to the workers, and
651 didn't allow any thread to be assigned more than a single piece of
652 work at once. The new implementation avoids communications
653 overhead by making requests in shared memory, avoiding kernel IO
654 where possible, and keeping more requests in flight at once.
655 Implements ticket 9682.
657 o Major features (relay):
658 - Raise the minimum acceptable configured bandwidth rate for bridges
659 to 50 KiB/sec and for relays to 75 KiB/sec. (The old values were
660 20 KiB/sec.) Closes ticket 13822.
662 o Major bugfixes (exit node stability):
663 - Fix an assertion failure that could occur under high DNS load.
664 Fixes bug 14129; bugfix on Tor 0.0.7rc1. Found by "jowr";
665 diagnosed and fixed by "cypherpunks".
667 o Major bugfixes (mixed relay-client operation):
668 - When running as a relay and client at the same time (not
669 recommended), if we decide not to use a new guard because we want
670 to retry older guards, only close the locally-originating circuits
671 passing through that guard. Previously we would close all the
672 circuits through that guard. Fixes bug 9819; bugfix on
673 0.2.1.1-alpha. Reported by "skruffy".
675 o Minor features (build):
676 - New --disable-system-torrc compile-time option to prevent Tor from
677 looking for the system-wide torrc or torrc-defaults files.
678 Resolves ticket 13037.
680 o Minor features (controller):
681 - Include SOCKS_USERNAME and SOCKS_PASSWORD values in controller
682 events so controllers can observe circuit isolation inputs. Closes
684 - ControlPort now supports the unix:/path/to/socket syntax as an
685 alternative to the ControlSocket option, for consistency with
686 SocksPort and HiddenServicePort. Closes ticket 14451.
687 - New "GETINFO bw-event-cache" to get information about recent
688 bandwidth events. Closes ticket 14128. Useful for controllers to
689 get recent bandwidth history after the fix for ticket 13988.
691 o Minor features (Denial of service resistance):
692 - Count the total number of bytes used storing hidden service
693 descriptors against the value of MaxMemInQueues. If we're low on
694 memory, and more than 20% of our memory is used holding hidden
695 service descriptors, free them until no more than 10% of our
696 memory holds hidden service descriptors. Free the least recently
697 fetched descriptors first. Resolves ticket 13806.
698 - When we have recently been under memory pressure (over 3/4 of
699 MaxMemInQueues is allocated), then allocate smaller zlib objects
700 for small requests. Closes ticket 11791.
702 o Minor features (geoip):
703 - Update geoip and geoip6 files to the January 7 2015 Maxmind
704 GeoLite2 Country database.
706 o Minor features (guard nodes):
707 - Reduce the time delay before saving guard status to disk from 10
708 minutes to 30 seconds (or from one hour to 10 minutes if
709 AvoidDiskWrites is set). Closes ticket 12485.
711 o Minor features (hidden service):
712 - Make Sybil attacks against hidden services harder by changing the
713 minimum time required to get the HSDir flag from 25 hours up to 96
714 hours. Addresses ticket 14149.
715 - New option "HiddenServiceAllowUnknownPorts" to allow hidden
716 services to disable the anti-scanning feature introduced in
717 0.2.6.2-alpha. With this option not set, a connection to an
718 unlisted port closes the circuit. With this option set, only a
719 RELAY_DONE cell is sent. Closes ticket 14084.
721 o Minor features (interface):
722 - Implement "-f -" command-line option to read torrc configuration
723 from standard input, if you don't want to store the torrc file in
724 the file system. Implements feature 13865.
726 o Minor features (logging):
727 - Add a count of unique clients to the bridge heartbeat message.
728 Resolves ticket 6852.
729 - Suppress "router info incompatible with extra info" message when
730 reading extrainfo documents from cache. (This message got loud
731 around when we closed bug 9812 in 0.2.6.2-alpha.) Closes
733 - Elevate hidden service authorized-client message from DEBUG to
734 INFO. Closes ticket 14015.
736 o Minor features (stability):
737 - Add assertions in our hash-table iteration code to check for
738 corrupted values that could cause infinite loops. Closes
741 o Minor features (systemd):
742 - Various improvements and modernizations in systemd hardening
743 support. Closes ticket 13805. Patch from Craig Andrews.
745 o Minor features (testing networks):
746 - Drop the minimum RendPostPeriod on a testing network to 5 seconds,
747 and the default on a testing network to 2 minutes. Drop the
748 MIN_REND_INITIAL_POST_DELAY on a testing network to 5 seconds, but
749 keep the default on a testing network at 30 seconds. This reduces
750 HS bootstrap time to around 25 seconds. Also, change the default
751 time in test-network.sh to match. Closes ticket 13401. Patch
753 - Create TestingDirAuthVoteHSDir to correspond to
754 TestingDirAuthVoteExit/Guard. Ensures that authorities vote the
755 HSDir flag for the listed relays regardless of uptime or ORPort
756 connectivity. Respects the value of VoteOnHidServDirectoriesV2.
757 Partial implementation for ticket 14067. Patch by "teor".
759 o Minor features (tor2web mode):
760 - Introduce the config option Tor2webRendezvousPoints, which allows
761 clients in Tor2webMode to select a specific Rendezvous Point to be
762 used in HS circuits. This might allow better performance for
763 Tor2Web nodes. Implements ticket 12844.
765 o Minor bugfixes (client DNS):
766 - Report the correct cached DNS expiration times on SOCKS port or in
767 DNS replies. Previously, we would report everything as "never
768 expires." Fixes bug 14193; bugfix on 0.2.3.17-beta.
769 - Avoid a small memory leak when we find a cached answer for a
770 reverse DNS lookup in a client-side DNS cache. (Remember, client-
771 side DNS caching is off by default, and is not recommended.) Fixes
772 bug 14259; bugfix on 0.2.0.1-alpha.
774 o Minor bugfixes (client, automapping):
775 - Avoid crashing on torrc lines for VirtualAddrNetworkIPv[4|6] when
776 no value follows the option. Fixes bug 14142; bugfix on
777 0.2.4.7-alpha. Patch by "teor".
778 - Fix a memory leak when using AutomapHostsOnResolve. Fixes bug
779 14195; bugfix on 0.1.0.1-rc.
780 - Prevent changes to other options from removing the wildcard value
781 "." from "AutomapHostsSuffixes". Fixes bug 12509; bugfix
783 - Allow MapAddress and AutomapHostsOnResolve to work together when
784 an address is mapped into another address type (like .onion) that
785 must be automapped at resolve time. Fixes bug 7555; bugfix
788 o Minor bugfixes (client, bridges):
789 - When we are using bridges and we had a network connectivity
790 problem, only retry connecting to our currently configured
791 bridges, not all bridges we know about and remember using. Fixes
792 bug 14216; bugfix on 0.2.2.17-alpha.
794 o Minor bugfixes (client, IPv6):
795 - Reject socks requests to literal IPv6 addresses when IPv6Traffic
796 flag is not set; and not because the NoIPv4Traffic flag was set.
797 Previously we'd looked at the NoIPv4Traffic flag for both types of
798 literal addresses. Fixes bug 14280; bugfix on 0.2.4.7-alpha.
800 o Minor bugfixes (compilation):
801 - The address of an array in the middle of a structure will always
802 be non-NULL. clang recognises this and complains. Disable the
803 tautologous and redundant check to silence this warning. Fixes bug
804 14001; bugfix on 0.2.1.2-alpha.
805 - Avoid warnings when building with systemd 209 or later. Fixes bug
806 14072; bugfix on 0.2.6.2-alpha. Patch from "h.venev".
807 - Compile correctly with (unreleased) OpenSSL 1.1.0 headers.
808 Addresses ticket 14188.
809 - Build without warnings with the stock OpenSSL srtp.h header, which
810 has a duplicate declaration of SSL_get_selected_srtp_profile().
811 Fixes bug 14220; this is OpenSSL's bug, not ours.
812 - Do not compile any code related to Tor2Web mode when Tor2Web mode
813 is not enabled at compile time. Previously, this code was included
814 in a disabled state. See discussion on ticket 12844.
815 - Remove the --disable-threads configure option again. It was
816 accidentally partially reintroduced in 29ac883606d6d. Fixes bug
817 14819; bugfix on 0.2.6.2-alpha.
819 o Minor bugfixes (controller):
820 - Report "down" in response to the "GETINFO entry-guards" command
821 when relays are down with an unreachable_since value. Previously,
822 we would report "up". Fixes bug 14184; bugfix on 0.1.2.2-alpha.
823 - Avoid crashing on a malformed EXTENDCIRCUIT command. Fixes bug
824 14116; bugfix on 0.2.2.9-alpha.
825 - Add a code for the END_CIRC_REASON_IP_NOW_REDUNDANT circuit close
826 reason. Fixes bug 14207; bugfix on 0.2.6.2-alpha.
828 o Minor bugfixes (directory authority):
829 - Allow directory authorities to fetch more data from one another if
830 they find themselves missing lots of votes. Previously, they had
831 been bumping against the 10 MB queued data limit. Fixes bug 14261;
832 bugfix on 0.1.2.5-alpha.
833 - Do not attempt to download extrainfo documents which we will be
834 unable to validate with a matching server descriptor. Fixes bug
835 13762; bugfix on 0.2.0.1-alpha.
836 - Fix a bug that was truncating AUTHDIR_NEWDESC events sent to the
837 control port. Fixes bug 14953; bugfix on 0.2.0.1-alpha.
838 - Enlarge the buffer to read bwauth generated files to avoid an
839 issue when parsing the file in dirserv_read_measured_bandwidths().
840 Fixes bug 14125; bugfix on 0.2.2.1-alpha.
842 o Minor bugfixes (file handling):
843 - Stop failing when key files are zero-length. Instead, generate new
844 keys, and overwrite the empty key files. Fixes bug 13111; bugfix
845 on all versions of Tor. Patch by "teor".
846 - Stop generating a fresh .old RSA onion key file when the .old file
847 is missing. Fixes part of 13111; bugfix on 0.0.6rc1.
848 - Avoid overwriting .old key files with empty key files.
849 - Skip loading zero-length extrainfo store, router store, stats,
850 state, and key files.
851 - Avoid crashing when trying to reload a torrc specified as a
852 relative path with RunAsDaemon turned on. Fixes bug 13397; bugfix
855 o Minor bugfixes (hidden services):
856 - Close the introduction circuit when we have no more usable intro
857 points, instead of waiting for it to time out. This also ensures
858 that no follow-up HS descriptor fetch is triggered when the
859 circuit eventually times out. Fixes bug 14224; bugfix on 0.0.6.
860 - When fetching a hidden service descriptor for a down service that
861 was recently up, do not keep refetching until we try the same
862 replica twice in a row. Fixes bug 14219; bugfix on 0.2.0.10-alpha.
863 - Successfully launch Tor with a nonexistent hidden service
864 directory. Our fix for bug 13942 didn't catch this case. Fixes bug
865 14106; bugfix on 0.2.6.2-alpha.
867 o Minor bugfixes (logging):
868 - Avoid crashing when there are more log domains than entries in
869 domain_list. Bugfix on 0.2.3.1-alpha.
870 - Add a string representation for LD_SCHED. Fixes bug 14740; bugfix
872 - Don't log messages to stdout twice when starting up. Fixes bug
873 13993; bugfix on 0.2.6.1-alpha.
875 o Minor bugfixes (parsing):
876 - Stop accepting milliseconds (or other junk) at the end of
877 descriptor publication times. Fixes bug 9286; bugfix on 0.0.2pre25.
878 - Support two-number and three-number version numbers correctly, in
879 case we change the Tor versioning system in the future. Fixes bug
880 13661; bugfix on 0.0.8pre1.
882 o Minor bugfixes (path counting):
883 - When deciding whether the consensus lists any exit nodes, count
884 the number listed in the consensus, not the number we have
885 descriptors for. Fixes part of bug 14918; bugfix on 0.2.6.2-alpha.
886 - When deciding whether we have any exit nodes, only examine
887 ExitNodes when the ExitNodes option is actually set. Fixes part of
888 bug 14918; bugfix on 0.2.6.2-alpha.
889 - Get rid of redundant and possibly scary warnings that we are
890 missing directory information while we bootstrap. Fixes part of
891 bug 14918; bugfix on 0.2.6.2-alpha.
893 o Minor bugfixes (portability):
894 - Fix the ioctl()-based network interface lookup code so that it
895 will work on systems that have variable-length struct ifreq, for
897 - Fix scheduler compilation on targets where char is unsigned. Fixes
898 bug 14764; bugfix on 0.2.6.2-alpha. Reported by Christian Kujau.
900 o Minor bugfixes (sandbox):
901 - Allow glibc fatal errors to be sent to stderr before Tor exits.
902 Previously, glibc would try to write them to /dev/tty, and the
903 sandbox would trap the call and make Tor exit prematurely. Fixes
904 bug 14759; bugfix on 0.2.5.1-alpha.
906 o Minor bugfixes (shutdown):
907 - When shutting down, always call event_del() on lingering read or
908 write events before freeing them. Otherwise, we risk double-frees
909 or read-after-frees in event_base_free(). Fixes bug 12985; bugfix
912 o Minor bugfixes (small memory leaks):
913 - Avoid leaking memory when using IPv6 virtual address mappings.
914 Fixes bug 14123; bugfix on 0.2.4.7-alpha. Patch by Tom van
917 o Minor bugfixes (statistics):
918 - Increase period over which bandwidth observations are aggregated
919 from 15 minutes to 4 hours. Fixes bug 13988; bugfix on 0.0.8pre1.
921 o Minor bugfixes (systemd support):
922 - Fix detection and operation of systemd watchdog. Fixes part of bug
923 14141; bugfix on 0.2.6.2-alpha. Patch from Tomasz Torcz.
924 - Run correctly under systemd with the RunAsDaemon option set. Fixes
925 part of bug 14141; bugfix on 0.2.5.7-rc. Patch from Tomasz Torcz.
926 - Inform the systemd supervisor about more changes in the Tor
927 process status. Implements part of ticket 14141. Patch from
929 - Cause the "--disable-systemd" option to actually disable systemd
930 support. Fixes bug 14350; bugfix on 0.2.6.2-alpha. Patch
933 o Minor bugfixes (TLS):
934 - Check more thoroughly throughout the TLS code for possible
935 unlogged TLS errors. Possible diagnostic or fix for bug 13319.
937 o Minor bugfixes (transparent proxy):
938 - Use getsockname, not getsockopt, to retrieve the address for a
939 TPROXY-redirected connection. Fixes bug 13796; bugfix
942 o Code simplification and refactoring:
943 - Move fields related to isolating and configuring client ports into
944 a shared structure. Previously, they were duplicated across
945 port_cfg_t, listener_connection_t, and edge_connection_t. Failure
946 to copy them correctly had been the cause of at least one bug in
947 the past. Closes ticket 8546.
948 - Refactor the get_interface_addresses_raw() doom-function into
949 multiple smaller and simpler subfunctions. Cover the resulting
950 subfunctions with unit-tests. Fixes a significant portion of
952 - Remove workaround in dirserv_thinks_router_is_hs_dir() that was
953 only for version <= 0.2.2.24 which is now deprecated. Closes
955 - Remove a test for a long-defunct broken version-one
959 - Adding section on OpenBSD to our TUNING document. Thanks to mmcc
960 for writing the OpenBSD-specific tips. Resolves ticket 13702.
961 - Make the tor-resolve documentation match its help string and its
962 options. Resolves part of ticket 14325.
963 - Log a more useful error message from tor-resolve when failing to
964 look up a hidden service address. Resolves part of ticket 14325.
966 o Downgraded warnings:
967 - Don't warn when we've attempted to contact a relay using the wrong
968 ntor onion key. Closes ticket 9635.
971 - To avoid confusion with the "ExitRelay" option, "ExitNode" is no
972 longer silently accepted as an alias for "ExitNodes".
973 - The --enable-mempool and --enable-buf-freelists options, which
974 were originally created to work around bad malloc implementations,
975 no longer exist. They were off-by-default in 0.2.5. Closes
979 - Make the checkdir/perms test complete successfully even if the
980 global umask is not 022. Fixes bug 14215; bugfix on 0.2.6.2-alpha.
981 - Test that tor does not fail when key files are zero-length. Check
982 that tor generates new keys, and overwrites the empty key files.
983 - Test that tor generates new keys when keys are missing
985 - Test that tor does not overwrite key files that already contain
986 data (existing behavior). Tests bug 13111. Patch by "teor".
987 - New "make test-stem" target to run stem integration tests.
988 Requires that the "STEM_SOURCE_DIR" environment variable be set.
990 - Make the test_cmdline_args.py script work correctly on Windows.
991 Patch from Gisle Vanem.
992 - Move the slower unit tests into a new "./src/test/test-slow"
993 binary that can be run independently of the other tests. Closes
995 - Avoid undefined behavior when sampling huge values from the
996 Laplace distribution. This made unittests fail on Raspberry Pi.
997 Bug found by Device. Fixes bug 14090; bugfix on 0.2.6.2-alpha.
1000 Changes in version 0.2.6.2-alpha - 2014-12-31
1001 Tor 0.2.6.2-alpha is the second alpha release in the 0.2.6.x series.
1002 It introduces a major new backend for deciding when to send cells on
1003 channels, which should lead down the road to big performance
1004 increases. It contains security and statistics features for better
1005 work on hidden services, and numerous bugfixes.
1007 This release contains many new unit tests, along with major
1008 performance improvements for running testing networks using Chutney.
1009 Thanks to a series of patches contributed by "teor", testing networks
1010 should now bootstrap in seconds, rather than minutes.
1012 o Major features (relay, infrastructure):
1013 - Complete revision of the code that relays use to decide which cell
1014 to send next. Formerly, we selected the best circuit to write on
1015 each channel, but we didn't select among channels in any
1016 sophisticated way. Now, we choose the best circuits globally from
1017 among those whose channels are ready to deliver traffic.
1019 This patch implements a new inter-cmux comparison API, a global
1020 high/low watermark mechanism and a global scheduler loop for
1021 transmission prioritization across all channels as well as among
1022 circuits on one channel. This schedule is currently tuned to
1023 (tolerantly) avoid making changes in network performance, but it
1024 should form the basis for major circuit performance increases in
1025 the future. Code by Andrea; tuning by Rob Jansen; implements
1028 o Major features (hidden services):
1029 - Make HS port scanning more difficult by immediately closing the
1030 circuit when a user attempts to connect to a nonexistent port.
1031 Closes ticket 13667.
1032 - Add a HiddenServiceStatistics option that allows Tor relays to
1033 gather and publish statistics about the overall size and volume of
1034 hidden service usage. Specifically, when this option is turned on,
1035 an HSDir will publish an approximate number of hidden services
1036 that have published descriptors to it the past 24 hours. Also, if
1037 a relay has acted as a hidden service rendezvous point, it will
1038 publish the approximate amount of rendezvous cells it has relayed
1039 the past 24 hours. The statistics themselves are obfuscated so
1040 that the exact values cannot be derived. For more details see
1041 proposal 238, "Better hidden service stats from Tor relays". This
1042 feature is currently disabled by default. Implements feature 13192.
1044 o Major bugfixes (client, automap):
1045 - Repair automapping with IPv6 addresses. This automapping should
1046 have worked previously, but one piece of debugging code that we
1047 inserted to detect a regression actually caused the regression to
1048 manifest itself again. Fixes bug 13811 and bug 12831; bugfix on
1049 0.2.4.7-alpha. Diagnosed and fixed by Francisco Blas
1052 o Major bugfixes (hidden services):
1053 - When closing an introduction circuit that was opened in parallel
1054 with others, don't mark the introduction point as unreachable.
1055 Previously, the first successful connection to an introduction
1056 point would make the other introduction points get marked as
1057 having timed out. Fixes bug 13698; bugfix on 0.0.6rc2.
1059 o Directory authority changes:
1060 - Remove turtles as a directory authority.
1061 - Add longclaw as a new (v3) directory authority. This implements
1062 ticket 13296. This keeps the directory authority count at 9.
1064 o Major removed features:
1065 - Tor clients no longer support connecting to hidden services
1066 running on Tor 0.2.2.x and earlier; the Support022HiddenServices
1067 option has been removed. (There shouldn't be any hidden services
1068 running these versions on the network.) Closes ticket 7803.
1070 o Minor features (client):
1071 - Validate hostnames in SOCKS5 requests more strictly. If SafeSocks
1072 is enabled, reject requests with IP addresses as hostnames.
1073 Resolves ticket 13315.
1075 o Minor features (controller):
1076 - Add a "SIGNAL HEARTBEAT" controller command that tells Tor to
1077 write an unscheduled heartbeat message to the log. Implements
1080 o Minor features (geoip):
1081 - Update geoip and geoip6 to the November 15 2014 Maxmind GeoLite2
1084 o Minor features (hidden services):
1085 - When re-enabling the network, don't try to build introduction
1086 circuits until we have successfully built a circuit. This makes
1087 hidden services come up faster when the network is re-enabled.
1088 Patch from "akwizgran". Closes ticket 13447.
1089 - When we fail to retrieve a hidden service descriptor, send the
1090 controller an "HS_DESC FAILED" controller event. Implements
1092 - New HiddenServiceDirGroupReadable option to cause hidden service
1093 directories and hostname files to be created group-readable. Patch
1094 from "anon", David Stainton, and "meejah". Closes ticket 11291.
1096 o Minor features (systemd):
1097 - Where supported, when running with systemd, report successful
1098 startup to systemd. Part of ticket 11016. Patch by Michael Scherer.
1099 - When running with systemd, support systemd watchdog messages. Part
1100 of ticket 11016. Patch by Michael Scherer.
1102 o Minor features (transparent proxy):
1103 - Update the transparent proxy option checks to allow for both ipfw
1104 and pf on OS X. Closes ticket 14002.
1105 - Use the correct option when using IPv6 with transparent proxy
1106 support on Linux. Resolves 13808. Patch by Francisco Blas
1109 o Minor bugfixes (preventative security, C safety):
1110 - When reading a hexadecimal, base-32, or base-64 encoded value from
1111 a string, always overwrite the whole output buffer. This prevents
1112 some bugs where we would look at (but fortunately, not reveal)
1113 uninitialized memory on the stack. Fixes bug 14013; bugfix on all
1115 - Clear all memory targetted by tor_addr_{to,from}_sockaddr(), not
1116 just the part that's used. This makes it harder for data leak bugs
1117 to occur in the event of other programming failures. Resolves
1120 o Minor bugfixes (client, microdescriptors):
1121 - Use a full 256 bits of the SHA256 digest of a microdescriptor when
1122 computing which microdescriptors to download. This keeps us from
1123 erroneous download behavior if two microdescriptor digests ever
1124 have the same first 160 bits. Fixes part of bug 13399; bugfix
1126 - Reset a router's status if its microdescriptor digest changes,
1127 even if the first 160 bits remain the same. Fixes part of bug
1128 13399; bugfix on 0.2.3.1-alpha.
1130 o Minor bugfixes (compilation):
1131 - Silence clang warnings under --enable-expensive-hardening,
1132 including implicit truncation of 64 bit values to 32 bit, const
1133 char assignment to self, tautological compare, and additional
1134 parentheses around equality tests. Fixes bug 13577; bugfix
1136 - Fix a clang warning about checking whether an address in the
1137 middle of a structure is NULL. Fixes bug 14001; bugfix
1140 o Minor bugfixes (hidden services):
1141 - Correctly send a controller event when we find that a rendezvous
1142 circuit has finished. Fixes bug 13936; bugfix on 0.1.1.5-alpha.
1143 - Pre-check directory permissions for new hidden-services to avoid
1144 at least one case of "Bug: Acting on config options left us in a
1145 broken state. Dying." Fixes bug 13942; bugfix on 0.0.6pre1.
1146 - When adding a new hidden service (for example, via SETCONF), Tor
1147 no longer congratulates the user for running a relay. Fixes bug
1148 13941; bugfix on 0.2.6.1-alpha.
1149 - When fetching hidden service descriptors, we now check not only
1150 for whether we got the hidden service we had in mind, but also
1151 whether we got the particular descriptors we wanted. This prevents
1152 a class of inefficient but annoying DoS attacks by hidden service
1153 directories. Fixes bug 13214; bugfix on 0.2.1.6-alpha. Reported
1156 o Minor bugfixes (Linux seccomp2 sandbox):
1157 - Make transparent proxy support work along with the seccomp2
1158 sandbox. Fixes part of bug 13808; bugfix on 0.2.5.1-alpha. Patch
1159 by Francisco Blas Izquierdo Riera.
1160 - Fix a memory leak in tor-resolve when running with the sandbox
1161 enabled. Fixes bug 14050; bugfix on 0.2.5.9-rc.
1163 o Minor bugfixes (logging):
1164 - Downgrade warnings about RSA signature failures to info log level.
1165 Emit a warning when an extra info document is found incompatible
1166 with a corresponding router descriptor. Fixes bug 9812; bugfix
1168 - Make connection_ap_handshake_attach_circuit() log the circuit ID
1169 correctly. Fixes bug 13701; bugfix on 0.0.6.
1171 o Minor bugfixes (misc):
1172 - Stop allowing invalid address patterns like "*/24" that contain
1173 both a wildcard address and a bit prefix length. This affects all
1174 our address-range parsing code. Fixes bug 7484; bugfix
1177 o Minor bugfixes (testing networks, fast startup):
1178 - Allow Tor to build circuits using a consensus with no exits. If
1179 the consensus has no exits (typical of a bootstrapping test
1180 network), allow Tor to build circuits once enough descriptors have
1181 been downloaded. This assists in bootstrapping a testing Tor
1182 network. Fixes bug 13718; bugfix on 0.2.4.10-alpha. Patch
1184 - When V3AuthVotingInterval is low, give a lower If-Modified-Since
1185 header to directory servers. This allows us to obtain consensuses
1186 promptly when the consensus interval is very short. This assists
1187 in bootstrapping a testing Tor network. Fixes parts of bugs 13718
1188 and 13963; bugfix on 0.2.0.3-alpha. Patch by "teor".
1189 - Stop assuming that private addresses are local when checking
1190 reachability in a TestingTorNetwork. Instead, when testing, assume
1191 all OR connections are remote. (This is necessary due to many test
1192 scenarios running all relays on localhost.) This assists in
1193 bootstrapping a testing Tor network. Fixes bug 13924; bugfix on
1194 0.1.0.1-rc. Patch by "teor".
1195 - Avoid building exit circuits from a consensus with no exits. Now
1196 thanks to our fix for 13718, we accept a no-exit network as not
1197 wholly lost, but we need to remember not to try to build exit
1198 circuits on it. Closes ticket 13814; patch by "teor".
1199 - Stop requiring exits to have non-zero bandwithcapacity in a
1200 TestingTorNetwork. Instead, when TestingMinExitFlagThreshold is 0,
1201 ignore exit bandwidthcapacity. This assists in bootstrapping a
1202 testing Tor network. Fixes parts of bugs 13718 and 13839; bugfix
1203 on 0.2.0.3-alpha. Patch by "teor".
1204 - Add "internal" to some bootstrap statuses when no exits are
1205 available. If the consensus does not contain Exits, Tor will only
1206 build internal circuits. In this case, relevant statuses will
1207 contain the word "internal" as indicated in the Tor control-
1208 spec.txt. When bootstrap completes, Tor will be ready to build
1209 internal circuits. If a future consensus contains Exits, exit
1210 circuits may become available. Fixes part of bug 13718; bugfix on
1211 0.2.4.10-alpha. Patch by "teor".
1212 - Decrease minimum consensus interval to 10 seconds when
1213 TestingTorNetwork is set, or 5 seconds for the first consensus.
1214 Fix assumptions throughout the code that assume larger intervals.
1215 Fixes bugs 13718 and 13823; bugfix on 0.2.0.3-alpha. Patch
1217 - Avoid excluding guards from path building in minimal test
1218 networks, when we're in a test network and excluding guards would
1219 exclude all relays. This typically occurs in incredibly small tor
1220 networks, and those using "TestingAuthVoteGuard *". Fixes part of
1221 bug 13718; bugfix on 0.1.1.11-alpha. Patch by "teor".
1223 o Code simplification and refactoring:
1224 - Stop using can_complete_circuits as a global variable; access it
1225 with a function instead.
1226 - Avoid using operators directly as macro arguments: this lets us
1227 apply coccinelle transformations to our codebase more directly.
1228 Closes ticket 13172.
1229 - Combine the functions used to parse ClientTransportPlugin and
1230 ServerTransportPlugin into a single function. Closes ticket 6456.
1231 - Add inline functions and convenience macros for inspecting channel
1232 state. Refactor the code to use convenience macros instead of
1233 checking channel state directly. Fixes issue 7356.
1234 - Document all members of was_router_added_t and rename
1235 ROUTER_WAS_NOT_NEW to ROUTER_IS_ALREADY_KNOWN to make it less
1236 confusable with ROUTER_WAS_TOO_OLD. Fixes issue 13644.
1237 - In connection_exit_begin_conn(), use END_CIRC_REASON_TORPROTOCOL
1238 constant instead of hardcoded value. Fixes issue 13840.
1239 - Refactor our generic strmap and digestmap types into a single
1240 implementation, so that we can add a new digest256map
1244 - Document the bridge-authority-only 'networkstatus-bridges' file.
1245 Closes ticket 13713; patch from "tom".
1246 - Fix typo in PredictedPortsRelevanceTime option description in
1247 manpage. Resolves issue 13707.
1248 - Stop suggesting that users specify relays by nickname: it isn't a
1249 good idea. Also, properly cross-reference how to specify relays in
1250 all parts of manual documenting options that take a list of
1251 relays. Closes ticket 13381.
1252 - Clarify the HiddenServiceDir option description in manpage to make
1253 it clear that relative paths are taken with respect to the current
1254 working directory. Also clarify that this behavior is not
1255 guaranteed to remain indefinitely. Fixes issue 13913.
1258 - New tests for many parts of channel, relay, and circuitmux
1259 functionality. Code by Andrea; part of 9262.
1260 - New tests for parse_transport_line(). Part of ticket 6456.
1261 - In the unit tests, use chgrp() to change the group of the unit
1262 test temporary directory to the current user, so that the sticky
1263 bit doesn't interfere with tests that check directory groups.
1265 - Add unit tests for resolve_my_addr(). Part of ticket 12376; patch
1269 Changes in version 0.2.6.1-alpha - 2014-10-30
1270 Tor 0.2.6.1-alpha is the first release in the Tor 0.2.6.x series. It
1271 includes numerous code cleanups and new tests, and fixes a large
1272 number of annoying bugs. Out-of-memory conditions are handled better
1273 than in 0.2.5, pluggable transports have improved proxy support, and
1274 clients now use optimistic data for contacting hidden services. Also,
1275 we are now more robust to changes in what we consider a parseable
1276 directory object, so that tightening restrictions does not have a risk
1277 of introducing infinite download loops.
1279 This is the first alpha release in a new series, so expect there to be
1280 bugs. Users who would rather test out a more stable branch should stay
1281 with 0.2.5.x for now.
1283 o New compiler and system requirements:
1284 - Tor 0.2.6.x requires that your compiler support more of the C99
1285 language standard than before. The 'configure' script now detects
1286 whether your compiler supports C99 mid-block declarations and
1287 designated initializers. If it does not, Tor will not compile.
1289 We may revisit this requirement if it turns out that a significant
1290 number of people need to build Tor with compilers that don't
1291 bother implementing a 15-year-old standard. Closes ticket 13233.
1292 - Tor no longer supports systems without threading support. When we
1293 began working on Tor, there were several systems that didn't have
1294 threads, or where the thread support wasn't able to run the
1295 threads of a single process on multiple CPUs. That no longer
1296 holds: every system where Tor needs to run well now has threading
1297 support. Resolves ticket 12439.
1299 o Removed platform support:
1300 - We no longer include special code to build on Windows CE; as far
1301 as we know, nobody has used Tor on Windows CE in a very long time.
1302 Closes ticket 11446.
1304 o Major features (bridges):
1305 - Expose the outgoing upstream HTTP/SOCKS proxy to pluggable
1306 transports if they are configured via the "TOR_PT_PROXY"
1307 environment variable. Implements proposal 232. Resolves
1310 o Major features (client performance, hidden services):
1311 - Allow clients to use optimistic data when connecting to a hidden
1312 service, which should remove a round-trip from hidden service
1313 initialization. See proposal 181 for details. Implements
1316 o Major features (directory system):
1317 - Upon receiving an unparseable directory object, if its digest
1318 matches what we expected, then don't try to download it again.
1319 Previously, when we got a descriptor we didn't like, we would keep
1320 trying to download it over and over. Closes ticket 11243.
1322 o Major features (sample torrc):
1323 - Add a new, infrequently-changed "torrc.minimal". This file is
1324 similar to torrc.sample, but it will change as infrequently as
1325 possible, for the benefit of users whose systems prompt them for
1326 intervention whenever a default configuration file is changed.
1327 Making this change allows us to update torrc.sample to be a more
1328 generally useful "sample torrc".
1330 o Major bugfixes (directory authorities):
1331 - Do not assign the HSDir flag to relays if they are not Valid, or
1332 currently hibernating. Fixes 12573; bugfix on 0.2.0.10-alpha.
1334 o Major bugfixes (directory bandwidth performance):
1335 - Don't flush the zlib buffer aggressively when compressing
1336 directory information for clients. This should save about 7% of
1337 the bandwidth currently used for compressed descriptors and
1338 microdescriptors. Fixes bug 11787; bugfix on 0.1.1.23.
1340 o Minor features (security, memory wiping):
1341 - Ensure we securely wipe keys from memory after
1342 crypto_digest_get_digest and init_curve25519_keypair_from_file
1343 have finished using them. Resolves ticket 13477.
1345 o Minor features (security, out-of-memory handling):
1346 - When handling an out-of-memory condition, allocate less memory for
1347 temporary data structures. Fixes issue 10115.
1348 - When handling an out-of-memory condition, consider more types of
1349 buffers, including those on directory connections, and zlib
1350 buffers. Resolves ticket 11792.
1353 - When identity keypair is generated for first time, log a
1354 congratulatory message that links to the new relay lifecycle
1355 document. Implements feature 10427.
1357 o Minor features (client):
1358 - Clients are now willing to send optimistic data (before they
1359 receive a 'connected' cell) to relays of any version. (Relays
1360 without support for optimistic data are no longer supported on the
1361 Tor network.) Resolves ticket 13153.
1363 o Minor features (directory authorities):
1364 - Don't list relays with a bandwidth estimate of 0 in the consensus.
1365 Implements a feature proposed during discussion of bug 13000.
1366 - In tor-gencert, report an error if the user provides the same
1367 argument more than once.
1368 - If a directory authority can't find a best consensus method in the
1369 votes that it holds, it now falls back to its favorite consensus
1370 method. Previously, it fell back to method 1. Neither of these is
1371 likely to get enough signatures, but "fall back to favorite"
1372 doesn't require us to maintain support an obsolete consensus
1373 method. Implements part of proposal 215.
1375 o Minor features (logging):
1376 - On Unix-like systems, you can now use named pipes as the target of
1377 the Log option, and other options that try to append to files.
1378 Closes ticket 12061. Patch from "carlo von lynX".
1379 - When opening a log file at startup, send it every log message that
1380 we generated between startup and opening it. Previously, log
1381 messages that were generated before opening the log file were only
1382 logged to stdout. Closes ticket 6938.
1383 - Add a TruncateLogFile option to overwrite logs instead of
1384 appending to them. Closes ticket 5583.
1386 o Minor features (portability, Solaris):
1387 - Threads are no longer disabled by default on Solaris; we believe
1388 that the versions of Solaris with broken threading support are all
1389 obsolete by now. Resolves ticket 9495.
1391 o Minor features (relay):
1392 - Re-check our address after we detect a changed IP address from
1393 getsockname(). This ensures that the controller command "GETINFO
1394 address" will report the correct value. Resolves ticket 11582.
1396 - A new AccountingRule option lets Relays set whether they'd like
1397 AccountingMax to be applied separately to inbound and outbound
1398 traffic, or applied to the sum of inbound and outbound traffic.
1399 Resolves ticket 961. Patch by "chobe".
1401 o Minor features (testing networks):
1402 - Add the TestingDirAuthVoteExit option, which lists nodes to assign
1403 the "Exit" flag regardless of their uptime, bandwidth, or exit
1404 policy. TestingTorNetwork must be set for this option to have any
1405 effect. Previously, authorities would take up to 35 minutes to
1406 give nodes the Exit flag in a test network. Partially implements
1409 o Minor features (validation):
1410 - Check all date/time values passed to tor_timegm and
1411 parse_rfc1123_time for validity, taking leap years into account.
1412 Improves HTTP header validation. Implemented with bug 13476.
1413 - In correct_tm(), limit the range of values returned by system
1414 localtime(_r) and gmtime(_r) to be between the years 1 and 8099.
1415 This means we don't have to deal with negative or too large dates,
1416 even if a clock is wrong. Otherwise we might fail to read a file
1417 written by us which includes such a date. Fixes bug 13476.
1419 o Minor bugfixes (bridge clients):
1420 - When configured to use a bridge without an identity digest (not
1421 recommended), avoid launching an extra channel to it when
1422 bootstrapping. Fixes bug 7733; bugfix on 0.2.4.4-alpha.
1424 o Minor bugfixes (bridges):
1425 - When DisableNetwork is set, do not launch pluggable transport
1426 plugins, and if any are running, terminate them. Fixes bug 13213;
1427 bugfix on 0.2.3.6-alpha.
1429 o Minor bugfixes (C correctness):
1430 - Fix several instances of possible integer overflow/underflow/NaN.
1431 Fixes bug 13104; bugfix on 0.2.3.1-alpha and later. Patches
1433 - In circuit_build_times_calculate_timeout() in circuitstats.c,
1434 avoid dividing by zero in the pareto calculations. This traps
1435 under clang's "undefined-trap" sanitizer. Fixes bug 13290; bugfix
1437 - Fix an integer overflow in format_time_interval(). Fixes bug
1438 13393; bugfix on 0.2.0.10-alpha.
1439 - Set the correct day of year value when the system's localtime(_r)
1440 or gmtime(_r) functions fail to set struct tm. Not externally
1441 visible. Fixes bug 13476; bugfix on 0.0.2pre14.
1442 - Avoid unlikely signed integer overflow in tor_timegm on systems
1443 with 32-bit time_t. Fixes bug 13476; bugfix on 0.0.2pre14.
1445 o Minor bugfixes (client):
1446 - Fix smartlist_choose_node_by_bandwidth() so that relays with the
1447 BadExit flag are not considered worthy candidates. Fixes bug
1448 13066; bugfix on 0.1.2.3-alpha.
1449 - Use the consensus schedule for downloading consensuses, and not
1450 the generic schedule. Fixes bug 11679; bugfix on 0.2.2.6-alpha.
1451 - Handle unsupported or malformed SOCKS5 requests properly by
1452 responding with the appropriate error message before closing the
1453 connection. Fixes bugs 12971 and 13314; bugfix on 0.0.2pre13.
1455 o Minor bugfixes (client, torrc):
1456 - Stop modifying the value of our DirReqStatistics torrc option just
1457 because we're not a bridge or relay. This bug was causing Tor
1458 Browser users to write "DirReqStatistics 0" in their torrc files
1459 as if they had chosen to change the config. Fixes bug 4244; bugfix
1461 - When GeoIPExcludeUnknown is enabled, do not incorrectly decide
1462 that our options have changed every time we SIGHUP. Fixes bug
1463 9801; bugfix on 0.2.4.10-alpha. Patch from "qwerty1".
1465 o Minor bugfixes (controller):
1466 - Return an error when the second or later arguments of the
1467 "setevents" controller command are invalid events. Previously we
1468 would return success while silently skipping invalid events. Fixes
1469 bug 13205; bugfix on 0.2.3.2-alpha. Reported by "fpxnns".
1471 o Minor bugfixes (directory system):
1472 - Always believe that v3 directory authorities serve extra-info
1473 documents, whether they advertise "caches-extra-info" or not.
1474 Fixes part of bug 11683; bugfix on 0.2.0.1-alpha.
1475 - When running as a v3 directory authority, advertise that you serve
1476 extra-info documents so that clients who want them can find them
1477 from you too. Fixes part of bug 11683; bugfix on 0.2.0.1-alpha.
1478 - Check the BRIDGE_DIRINFO flag bitwise rather than using equality.
1479 Previously, directories offering BRIDGE_DIRINFO and some other
1480 flag (i.e. microdescriptors or extrainfo) would be ignored when
1481 looking for bridges. Partially fixes bug 13163; bugfix
1484 o Minor bugfixes (networking):
1485 - Check for orconns and use connection_or_close_for_error() rather
1486 than connection_mark_for_close() directly in the getsockopt()
1487 failure case of connection_handle_write_impl(). Fixes bug 11302;
1488 bugfix on 0.2.4.4-alpha.
1490 o Minor bugfixes (relay):
1491 - When generating our family list, remove spaces from around the
1492 entries. Fixes bug 12728; bugfix on 0.2.1.7-alpha.
1493 - If our previous bandwidth estimate was 0 bytes, allow publishing a
1494 new relay descriptor immediately. Fixes bug 13000; bugfix
1497 o Minor bugfixes (testing networks):
1498 - Fix TestingDirAuthVoteGuard to properly give out Guard flags in a
1499 testing network. Fixes bug 13064; bugfix on 0.2.5.2-alpha.
1500 - Stop using the default authorities in networks which provide both
1501 AlternateDirAuthority and AlternateBridgeAuthority. Partially
1502 fixes bug 13163; bugfix on 0.2.0.13-alpha.
1504 o Minor bugfixes (testing):
1505 - Stop spawn test failures due to a race condition between the
1506 SIGCHLD handler updating the process status, and the test reading
1507 it. Fixes bug 13291; bugfix on 0.2.3.3-alpha.
1509 o Minor bugfixes (testing, Windows):
1510 - Avoid passing an extra backslash when creating a temporary
1511 directory for running the unit tests on Windows. Fixes bug 12392;
1512 bugfix on 0.2.2.25-alpha. Patch from Gisle Vanem.
1514 o Minor bugfixes (windows):
1515 - Remove code to special-case handling of NTE_BAD_KEYSET when
1516 acquiring windows CryptoAPI context. This error can't actually
1517 occur for the parameters we're providing. Fixes bug 10816; bugfix
1520 o Minor bugfixes (zlib):
1521 - Avoid truncating a zlib stream when trying to finalize it with an
1522 empty output buffer. Fixes bug 11824; bugfix on 0.1.1.23.
1525 - Allow our configure script to build correctly with autoconf 2.62
1526 again. Fixes bug 12693; bugfix on 0.2.5.2-alpha.
1527 - Improve the error message from ./configure to make it clear that
1528 when asciidoc has not been found, the user will have to either add
1529 --disable-asciidoc argument or install asciidoc. Resolves
1532 o Code simplification and refactoring:
1533 - Change the entry_is_live() function to take named bitfield
1534 elements instead of an unnamed list of booleans. Closes
1536 - Refactor and unit-test entry_is_time_to_retry() in entrynodes.c.
1537 Resolves ticket 12205.
1538 - Use calloc and reallocarray functions instead of multiply-
1539 then-malloc. This makes it less likely for us to fall victim to an
1540 integer overflow attack when allocating. Resolves ticket 12855.
1541 - Use the standard macro name SIZE_MAX, instead of our
1543 - Document usage of the NO_DIRINFO and ALL_DIRINFO flags clearly in
1544 functions which take them as arguments. Replace 0 with NO_DIRINFO
1545 in a function call for clarity. Seeks to prevent future issues
1547 - Avoid 4 null pointer errors under clang static analysis by using
1548 tor_assert() to prove that the pointers aren't null. Fixes
1550 - Rework the API of policies_parse_exit_policy() to use a bitmask to
1551 represent parsing options, instead of a confusing mess of
1552 booleans. Resolves ticket 8197.
1553 - Introduce a helper function to parse ExitPolicy in
1554 or_options_t structure.
1557 - Add a doc/TUNING document with tips for handling large numbers of
1558 TCP connections when running busy Tor relay. Update the warning
1559 message to point to this file when running out of sockets
1560 operating system is allowing to use simultaneously. Resolves
1564 - We no longer remind the user about configuration options that have
1565 been obsolete since 0.2.3.x or earlier. Patch by Adrien Bak.
1566 - Remove our old, non-weighted bandwidth-based node selection code.
1567 Previously, we used it as a fallback when we couldn't perform
1568 weighted bandwidth-based node selection. But that would only
1569 happen in the cases where we had no consensus, or when we had a
1570 consensus generated by buggy or ancient directory authorities. In
1571 either case, it's better to use the more modern, better maintained
1572 algorithm, with reasonable defaults for the weights. Closes
1574 - Remove the --disable-curve25519 configure option. Relays and
1575 clients now are required to support curve25519 and the
1577 - The old "StrictEntryNodes" and "StrictExitNodes" options, which
1578 used to be deprecated synonyms for "StrictNodes", are now marked
1579 obsolete. Resolves ticket 12226.
1580 - Clients don't understand the BadDirectory flag in the consensus
1581 anymore, and ignore it.
1584 - Refactor the function that chooses guard nodes so that it can more
1585 easily be tested; write some tests for it.
1586 - Fix and re-enable the fgets_eagain unit test. Fixes bug 12503;
1587 bugfix on 0.2.3.1-alpha. Patch from "cypherpunks."
1588 - Create unit tests for format_time_interval(). With bug 13393.
1589 - Add unit tests for tor_timegm signed overflow, tor_timegm and
1590 parse_rfc1123_time validity checks, correct_tm year clamping. Unit
1591 tests (visible) fixes in bug 13476.
1592 - Add a "coverage-html" make target to generate HTML-visualized
1593 coverage results when building with --enable-coverage. (Requires
1594 lcov.) Patch from Kevin Murray.
1595 - Enable the backtrace handler (where supported) when running the
1597 - Revise all unit tests that used the legacy test_* macros to
1598 instead use the recommended tt_* macros. This patch was generated
1599 with coccinelle, to avoid manual errors. Closes ticket 13119.
1601 o Distribution (systemd):
1602 - systemd unit file: only allow tor to write to /var/lib/tor and
1603 /var/log/tor. The rest of the filesystem is accessible for reading
1604 only. Patch by intrigeri; resolves ticket 12751.
1605 - systemd unit file: ensure that the process and all its children
1606 can never gain new privileges. Patch by intrigeri; resolves
1608 - systemd unit file: set up /var/run/tor as writable for the Tor
1609 service. Patch by intrigeri; resolves ticket 13196.
1611 o Removed features (directory authorities):
1612 - Remove code that prevented authorities from listing Tor relays
1613 affected by CVE-2011-2769 as guards. These relays are already
1614 rejected altogether due to the minimum version requirement of
1615 0.2.3.16-alpha. Closes ticket 13152.
1616 - The "AuthDirRejectUnlisted" option no longer has any effect, as
1617 the fingerprints file (approved-routers) has been deprecated.
1618 - Directory authorities do not support being Naming dirauths anymore.
1619 The "NamingAuthoritativeDir" config option is now obsolete.
1620 - Directory authorities do not support giving out the BadDirectory
1622 - Directory authorities no longer advertise or support consensus
1623 methods 1 through 12 inclusive. These consensus methods were
1624 obsolete and/or insecure: maintaining the ability to support them
1625 served no good purpose. Implements part of proposal 215; closes
1628 o Testing (test-network.sh):
1629 - Stop using "echo -n", as some shells' built-in echo doesn't
1630 support "-n". Instead, use "/bin/echo -n". Partially fixes
1632 - Stop an apparent test-network hang when used with make -j2. Fixes
1634 - Add a --delay option to test-network.sh, which configures the
1635 delay before the chutney network tests for data transmission.
1636 Partially implements ticket 13161.
1639 Changes in version 0.2.5.10 - 2014-10-24
1640 Tor 0.2.5.10 is the first stable release in the 0.2.5 series.
1642 It adds several new security features, including improved
1643 denial-of-service resistance for relays, new compiler hardening
1644 options, and a system-call sandbox for hardened installations on Linux
1645 (requires seccomp2). The controller protocol has several new features,
1646 resolving IPv6 addresses should work better than before, and relays
1647 should be a little more CPU-efficient. We've added support for more
1648 OpenBSD and FreeBSD transparent proxy types. We've improved the build
1649 system and testing infrastructure to allow unit testing of more parts
1650 of the Tor codebase. Finally, we've addressed several nagging pluggable
1651 transport usability issues, and included numerous other small bugfixes
1652 and features mentioned below.
1654 This release marks end-of-life for Tor 0.2.3.x; those Tor versions
1655 have accumulated many known flaws; everyone should upgrade.
1657 o Deprecated versions:
1658 - Tor 0.2.3.x has reached end-of-life; it has received no patches or
1659 attention for some while.
1662 Changes in version 0.2.5.9-rc - 2014-10-20
1663 Tor 0.2.5.9-rc is the third release candidate for the Tor 0.2.5.x
1664 series. It disables SSL3 in response to the recent "POODLE" attack
1665 (even though POODLE does not affect Tor). It also works around a crash
1666 bug caused by some operating systems' response to the "POODLE" attack
1667 (which does affect Tor). It also contains a few miscellaneous fixes.
1669 o Major security fixes:
1670 - Disable support for SSLv3. All versions of OpenSSL in use with Tor
1671 today support TLS 1.0 or later, so we can safely turn off support
1672 for this old (and insecure) protocol. Fixes bug 13426.
1674 o Major bugfixes (openssl bug workaround):
1675 - Avoid crashing when using OpenSSL version 0.9.8zc, 1.0.0o, or
1676 1.0.1j, built with the 'no-ssl3' configuration option. Fixes bug
1677 13471. This is a workaround for an OpenSSL bug.
1680 - Disable the sandbox name resolver cache when running tor-resolve:
1681 tor-resolve doesn't use the sandbox code, and turning it on was
1682 breaking attempts to do tor-resolve on a non-default server on
1683 Linux. Fixes bug 13295; bugfix on 0.2.5.3-alpha.
1685 o Compilation fixes:
1686 - Build and run correctly on systems like OpenBSD-current that have
1687 patched OpenSSL to remove get_cipher_by_char and/or its
1688 implementations. Fixes issue 13325.
1690 o Downgraded warnings:
1691 - Downgrade the severity of the 'unexpected sendme cell from client'
1692 from 'warn' to 'protocol warning'. Closes ticket 8093.
1695 Changes in version 0.2.4.25 - 2014-10-20
1696 Tor 0.2.4.25 disables SSL3 in response to the recent "POODLE" attack
1697 (even though POODLE does not affect Tor). It also works around a crash
1698 bug caused by some operating systems' response to the "POODLE" attack
1699 (which does affect Tor).
1701 o Major security fixes (also in 0.2.5.9-rc):
1702 - Disable support for SSLv3. All versions of OpenSSL in use with Tor
1703 today support TLS 1.0 or later, so we can safely turn off support
1704 for this old (and insecure) protocol. Fixes bug 13426.
1706 o Major bugfixes (openssl bug workaround, also in 0.2.5.9-rc):
1707 - Avoid crashing when using OpenSSL version 0.9.8zc, 1.0.0o, or
1708 1.0.1j, built with the 'no-ssl3' configuration option. Fixes bug
1709 13471. This is a workaround for an OpenSSL bug.
1712 Changes in version 0.2.5.8-rc - 2014-09-22
1713 Tor 0.2.5.8-rc is the second release candidate for the Tor 0.2.5.x
1714 series. It fixes a bug that affects consistency and speed when
1715 connecting to hidden services, and it updates the location of one of
1716 the directory authorities.
1719 - Clients now send the correct address for their chosen rendezvous
1720 point when trying to access a hidden service. They used to send
1721 the wrong address, which would still work some of the time because
1722 they also sent the identity digest of the rendezvous point, and if
1723 the hidden service happened to try connecting to the rendezvous
1724 point from a relay that already had a connection open to it,
1725 the relay would reuse that connection. Now connections to hidden
1726 services should be more robust and faster. Also, this bug meant
1727 that clients were leaking to the hidden service whether they were
1728 on a little-endian (common) or big-endian (rare) system, which for
1729 some users might have reduced their anonymity. Fixes bug 13151;
1730 bugfix on 0.2.1.5-alpha.
1732 o Directory authority changes:
1733 - Change IP address for gabelmoo (v3 directory authority).
1736 Changes in version 0.2.4.24 - 2014-09-22
1737 Tor 0.2.4.24 fixes a bug that affects consistency and speed when
1738 connecting to hidden services, and it updates the location of one of
1739 the directory authorities.
1742 - Clients now send the correct address for their chosen rendezvous
1743 point when trying to access a hidden service. They used to send
1744 the wrong address, which would still work some of the time because
1745 they also sent the identity digest of the rendezvous point, and if
1746 the hidden service happened to try connecting to the rendezvous
1747 point from a relay that already had a connection open to it,
1748 the relay would reuse that connection. Now connections to hidden
1749 services should be more robust and faster. Also, this bug meant
1750 that clients were leaking to the hidden service whether they were
1751 on a little-endian (common) or big-endian (rare) system, which for
1752 some users might have reduced their anonymity. Fixes bug 13151;
1753 bugfix on 0.2.1.5-alpha.
1755 o Directory authority changes:
1756 - Change IP address for gabelmoo (v3 directory authority).
1758 o Minor features (geoip):
1759 - Update geoip and geoip6 to the August 7 2014 Maxmind GeoLite2
1763 Changes in version 0.2.5.7-rc - 2014-09-11
1764 Tor 0.2.5.7-rc fixes several regressions from earlier in the 0.2.5.x
1765 release series, and some long-standing bugs related to ORPort reachability
1766 testing and failure to send CREATE cells. It is the first release
1767 candidate for the Tor 0.2.5.x series.
1769 o Major bugfixes (client, startup):
1770 - Start making circuits as soon as DisabledNetwork is turned off.
1771 When Tor started with DisabledNetwork set, it would correctly
1772 conclude that it shouldn't build circuits, but it would mistakenly
1773 cache this conclusion, and continue believing it even when
1774 DisableNetwork is set to 0. Fixes the bug introduced by the fix
1775 for bug 11200; bugfix on 0.2.5.4-alpha.
1776 - Resume expanding abbreviations for command-line options. The fix
1777 for bug 4647 accidentally removed our hack from bug 586 that
1778 rewrote HashedControlPassword to __HashedControlSessionPassword
1779 when it appears on the commandline (which allowed the user to set
1780 her own HashedControlPassword in the torrc file while the
1781 controller generates a fresh session password for each run). Fixes
1782 bug 12948; bugfix on 0.2.5.1-alpha.
1783 - Warn about attempts to run hidden services and relays in the same
1784 process: that's probably not a good idea. Closes ticket 12908.
1786 o Major bugfixes (relay):
1787 - Avoid queuing or sending destroy cells for circuit ID zero when we
1788 fail to send a CREATE cell. Fixes bug 12848; bugfix on 0.0.8pre1.
1789 Found and fixed by "cypherpunks".
1790 - Fix ORPort reachability detection on relays running behind a
1791 proxy, by correctly updating the "local" mark on the controlling
1792 channel when changing the address of an or_connection_t after the
1793 handshake. Fixes bug 12160; bugfix on 0.2.4.4-alpha.
1795 o Minor features (bridge):
1796 - Add an ExtORPortCookieAuthFileGroupReadable option to make the
1797 cookie file for the ExtORPort g+r by default.
1799 o Minor features (geoip):
1800 - Update geoip and geoip6 to the August 7 2014 Maxmind GeoLite2
1803 o Minor bugfixes (logging):
1804 - Reduce the log severity of the "Pluggable transport proxy does not
1805 provide any needed transports and will not be launched." message,
1806 since Tor Browser includes several ClientTransportPlugin lines in
1807 its torrc-defaults file, leading every Tor Browser user who looks
1808 at her logs to see these notices and wonder if they're dangerous.
1809 Resolves bug 13124; bugfix on 0.2.5.3-alpha.
1810 - Downgrade "Unexpected onionskin length after decryption" warning
1811 to a protocol-warn, since there's nothing relay operators can do
1812 about a client that sends them a malformed create cell. Resolves
1813 bug 12996; bugfix on 0.0.6rc1.
1814 - Log more specific warnings when we get an ESTABLISH_RENDEZVOUS
1815 cell on a cannibalized or non-OR circuit. Resolves ticket 12997.
1816 - When logging information about an EXTEND2 or EXTENDED2 cell, log
1817 their names correctly. Fixes part of bug 12700; bugfix
1819 - When logging information about a relay cell whose command we don't
1820 recognize, log its command as an integer. Fixes part of bug 12700;
1821 bugfix on 0.2.1.10-alpha.
1822 - Escape all strings from the directory connection before logging
1823 them. Fixes bug 13071; bugfix on 0.1.1.15. Patch from "teor".
1825 o Minor bugfixes (controller):
1826 - Restore the functionality of CookieAuthFileGroupReadable. Fixes
1827 bug 12864; bugfix on 0.2.5.1-alpha.
1828 - Actually send TRANSPORT_LAUNCHED and HS_DESC events to
1829 controllers. Fixes bug 13085; bugfix on 0.2.5.1-alpha. Patch
1832 o Minor bugfixes (compilation):
1833 - Fix compilation of test.h with MSVC. Patch from Gisle Vanem;
1834 bugfix on 0.2.5.5-alpha.
1835 - Make the nmake make files work again. Fixes bug 13081. Bugfix on
1836 0.2.5.1-alpha. Patch from "NewEraCracker".
1837 - In routerlist_assert_ok(), don't take the address of a
1838 routerinfo's cache_info member unless that routerinfo is non-NULL.
1839 Fixes bug 13096; bugfix on 0.1.1.9-alpha. Patch by "teor".
1840 - Fix a large number of false positive warnings from the clang
1841 analyzer static analysis tool. This should make real warnings
1842 easier for clang analyzer to find. Patch from "teor". Closes
1845 o Distribution (systemd):
1846 - Verify configuration file via ExecStartPre in the systemd unit
1847 file. Patch from intrigeri; resolves ticket 12730.
1848 - Explicitly disable RunAsDaemon in the systemd unit file. Our
1849 current systemd unit uses "Type = simple", so systemd does not
1850 expect tor to fork. If the user has "RunAsDaemon 1" in their
1851 torrc, then things won't work as expected. This is e.g. the case
1852 on Debian (and derivatives), since there we pass "--defaults-torrc
1853 /usr/share/tor/tor-service-defaults-torrc" (that contains
1854 "RunAsDaemon 1") by default. Patch by intrigeri; resolves
1858 - Adjust the URLs in the README to refer to the new locations of
1859 several documents on the website. Fixes bug 12830. Patch from
1861 - Document 'reject6' and 'accept6' ExitPolicy entries. Resolves
1865 Changes in version 0.2.5.6-alpha - 2014-07-28
1866 Tor 0.2.5.6-alpha brings us a big step closer to slowing down the
1867 risk from guard rotation, and fixes a variety of other issues to get
1868 us closer to a release candidate.
1870 o Major features (also in 0.2.4.23):
1871 - Make the number of entry guards configurable via a new
1872 NumEntryGuards consensus parameter, and the number of directory
1873 guards configurable via a new NumDirectoryGuards consensus
1874 parameter. Implements ticket 12688.
1876 o Major bugfixes (also in 0.2.4.23):
1877 - Fix a bug in the bounds-checking in the 32-bit curve25519-donna
1878 implementation that caused incorrect results on 32-bit
1879 implementations when certain malformed inputs were used along with
1880 a small class of private ntor keys. This bug does not currently
1881 appear to allow an attacker to learn private keys or impersonate a
1882 Tor server, but it could provide a means to distinguish 32-bit Tor
1883 implementations from 64-bit Tor implementations. Fixes bug 12694;
1884 bugfix on 0.2.4.8-alpha. Bug found by Robert Ransom; fix from
1888 - Perform circuit cleanup operations even when circuit
1889 construction operations are disabled (because the network is
1890 disabled, or because there isn't enough directory information).
1891 Previously, when we were not building predictive circuits, we
1892 were not closing expired circuits either. Fixes bug 8387; bugfix on
1893 0.1.1.11-alpha. This bug became visible in 0.2.4.10-alpha when we
1894 became more strict about when we have "enough directory information
1898 - Authorities now assign the Guard flag to the fastest 25% of the
1899 network (it used to be the fastest 50%). Also raise the consensus
1900 weight that guarantees the Guard flag from 250 to 2000. For the
1901 current network, this results in about 1100 guards, down from 2500.
1902 This step paves the way for moving the number of entry guards
1903 down to 1 (proposal 236) while still providing reasonable expected
1904 performance for most users. Implements ticket 12690.
1905 - Update geoip and geoip6 to the July 10 2014 Maxmind GeoLite2
1907 - Slightly enhance the diagnostic message for bug 12184.
1909 o Minor bugfixes (also in 0.2.4.23):
1910 - Warn and drop the circuit if we receive an inbound 'relay early'
1911 cell. Those used to be normal to receive on hidden service circuits
1912 due to bug 1038, but the buggy Tor versions are long gone from
1913 the network so we can afford to resume watching for them. Resolves
1914 the rest of bug 1038; bugfix on 0.2.1.19.
1915 - Correct a confusing error message when trying to extend a circuit
1916 via the control protocol but we don't know a descriptor or
1917 microdescriptor for one of the specified relays. Fixes bug 12718;
1918 bugfix on 0.2.3.1-alpha.
1921 - Fix compilation when building with bufferevents enabled. (This
1922 configuration is still not expected to work, however.)
1923 Fixes bugs 12438, 12474, 11578; bugfixes on 0.2.5.1-alpha and
1924 0.2.5.3-alpha. Patches from Anthony G. Basile and Sathyanarayanan
1926 - Compile correctly with builds and forks of OpenSSL (such as
1927 LibreSSL) that disable compression. Fixes bug 12602; bugfix on
1928 0.2.1.1-alpha. Patch from "dhill".
1931 Changes in version 0.2.4.23 - 2014-07-28
1932 Tor 0.2.4.23 brings us a big step closer to slowing down the risk from
1933 guard rotation, and also backports several important fixes from the
1934 Tor 0.2.5 alpha release series.
1937 - Clients now look at the "usecreatefast" consensus parameter to
1938 decide whether to use CREATE_FAST or CREATE cells for the first hop
1939 of their circuit. This approach can improve security on connections
1940 where Tor's circuit handshake is stronger than the available TLS
1941 connection security levels, but the tradeoff is more computational
1942 load on guard relays. Implements proposal 221. Resolves ticket 9386.
1943 - Make the number of entry guards configurable via a new
1944 NumEntryGuards consensus parameter, and the number of directory
1945 guards configurable via a new NumDirectoryGuards consensus
1946 parameter. Implements ticket 12688.
1949 - Fix a bug in the bounds-checking in the 32-bit curve25519-donna
1950 implementation that caused incorrect results on 32-bit
1951 implementations when certain malformed inputs were used along with
1952 a small class of private ntor keys. This bug does not currently
1953 appear to allow an attacker to learn private keys or impersonate a
1954 Tor server, but it could provide a means to distinguish 32-bit Tor
1955 implementations from 64-bit Tor implementations. Fixes bug 12694;
1956 bugfix on 0.2.4.8-alpha. Bug found by Robert Ransom; fix from
1960 - Warn and drop the circuit if we receive an inbound 'relay early'
1961 cell. Those used to be normal to receive on hidden service circuits
1962 due to bug 1038, but the buggy Tor versions are long gone from
1963 the network so we can afford to resume watching for them. Resolves
1964 the rest of bug 1038; bugfix on 0.2.1.19.
1965 - Correct a confusing error message when trying to extend a circuit
1966 via the control protocol but we don't know a descriptor or
1967 microdescriptor for one of the specified relays. Fixes bug 12718;
1968 bugfix on 0.2.3.1-alpha.
1969 - Avoid an illegal read from stack when initializing the TLS
1970 module using a version of OpenSSL without all of the ciphers
1971 used by the v2 link handshake. Fixes bug 12227; bugfix on
1972 0.2.4.8-alpha. Found by "starlight".
1975 - Update geoip and geoip6 to the July 10 2014 Maxmind GeoLite2
1979 Changes in version 0.2.5.5-alpha - 2014-06-18
1980 Tor 0.2.5.5-alpha fixes a wide variety of remaining issues in the Tor
1981 0.2.5.x release series, including a couple of DoS issues, some
1982 performance regressions, a large number of bugs affecting the Linux
1983 seccomp2 sandbox code, and various other bugfixes. It also adds
1984 diagnostic bugfixes for a few tricky issues that we're trying to
1987 o Major features (security, traffic analysis resistance):
1988 - Several major improvements to the algorithm used to decide when to
1989 close TLS connections. Previous versions of Tor closed connections
1990 at a fixed interval after the last time a non-padding cell was
1991 sent over the connection, regardless of the target of the
1992 connection. Now, we randomize the intervals by adding up to 50% of
1993 their base value, we measure the length of time since connection
1994 last had at least one circuit, and we allow connections to known
1995 ORs to remain open a little longer (15 minutes instead of 3
1996 minutes minimum). These changes should improve Tor's resistance
1997 against some kinds of traffic analysis, and lower some overhead
1998 from needlessly closed connections. Fixes ticket 6799.
1999 Incidentally fixes ticket 12023; bugfix on 0.2.5.1-alpha.
2001 o Major bugfixes (security, OOM, new since 0.2.5.4-alpha, also in 0.2.4.22):
2002 - Fix a memory leak that could occur if a microdescriptor parse
2003 fails during the tokenizing step. This bug could enable a memory
2004 exhaustion attack by directory servers. Fixes bug 11649; bugfix
2007 o Major bugfixes (security, directory authorities):
2008 - Directory authorities now include a digest of each relay's
2009 identity key as a part of its microdescriptor.
2011 This is a workaround for bug 11743 (reported by "cypherpunks"),
2012 where Tor clients do not support receiving multiple
2013 microdescriptors with the same SHA256 digest in the same
2014 consensus. When clients receive a consensus like this, they only
2015 use one of the relays. Without this fix, a hostile relay could
2016 selectively disable some client use of target relays by
2017 constructing a router descriptor with a different identity and the
2018 same microdescriptor parameters and getting the authorities to
2019 list it in a microdescriptor consensus. This fix prevents an
2020 attacker from causing a microdescriptor collision, because the
2021 router's identity is not forgeable.
2023 o Major bugfixes (relay):
2024 - Use a direct dirport connection when uploading non-anonymous
2025 descriptors to the directory authorities. Previously, relays would
2026 incorrectly use tunnel connections under a fairly wide variety of
2027 circumstances. Fixes bug 11469; bugfix on 0.2.4.3-alpha.
2028 - When a circuit accidentally has the same circuit ID for its
2029 forward and reverse direction, correctly detect the direction of
2030 cells using that circuit. Previously, this bug made roughly one
2031 circuit in a million non-functional. Fixes bug 12195; this is a
2032 bugfix on every version of Tor.
2034 o Major bugfixes (client, pluggable transports):
2035 - When managing pluggable transports, use OS notification facilities
2036 to learn if they have crashed, and don't attempt to kill any
2037 process that has already exited. Fixes bug 8746; bugfix
2040 o Minor features (diagnostic):
2041 - When logging a warning because of bug 7164, additionally check the
2042 hash table for consistency (as proposed on ticket 11737). This may
2043 help diagnose bug 7164.
2044 - When we log a heartbeat, log how many one-hop circuits we have
2045 that are at least 30 minutes old, and log status information about
2046 a few of them. This is an attempt to track down bug 8387.
2047 - When encountering an unexpected CR while writing text to a file on
2048 Windows, log the name of the file. Should help diagnosing
2050 - Give more specific warnings when a client notices that an onion
2051 handshake has failed. Fixes ticket 9635.
2052 - Add significant new logging code to attempt to diagnose bug 12184,
2053 where relays seem to run out of available circuit IDs.
2054 - Improve the diagnostic log message for bug 8387 even further to
2055 try to improve our odds of figuring out why one-hop directory
2056 circuits sometimes do not get closed.
2058 o Minor features (security, memory management):
2059 - Memory allocation tricks (mempools and buffer freelists) are now
2060 disabled by default. You can turn them back on with
2061 --enable-mempools and --enable-buf-freelists respectively. We're
2062 disabling these features because malloc performance is good enough
2063 on most platforms, and a similar feature in OpenSSL exacerbated
2064 exploitation of the Heartbleed attack. Resolves ticket 11476.
2066 o Minor features (security):
2067 - Apply the secure SipHash-2-4 function to the hash table mapping
2068 circuit IDs and channels to circuits. We missed this one when we
2069 were converting all the other hash functions to use SipHash back
2070 in 0.2.5.3-alpha. Resolves ticket 11750.
2072 o Minor features (build):
2073 - The configure script has a --disable-seccomp option to turn off
2074 support for libseccomp on systems that have it, in case it (or
2075 Tor's use of it) is broken. Resolves ticket 11628.
2077 o Minor features (other):
2078 - Update geoip and geoip6 to the June 4 2014 Maxmind GeoLite2
2081 o Minor bugfixes (security, new since 0.2.5.4-alpha, also in 0.2.4.22):
2082 - When running a hidden service, do not allow TunneledDirConns 0;
2083 this will keep the hidden service from running, and also
2084 make it publish its descriptors directly over HTTP. Fixes bug 10849;
2085 bugfix on 0.2.1.1-alpha.
2087 o Minor bugfixes (performance):
2088 - Avoid a bug where every successful connection made us recompute
2089 the flag telling us whether we have sufficient information to
2090 build circuits. Previously, we would forget our cached value
2091 whenever we successfully opened a channel (or marked a router as
2092 running or not running for any other reason), regardless of
2093 whether we had previously believed the router to be running. This
2094 forced us to run an expensive update operation far too often.
2095 Fixes bug 12170; bugfix on 0.1.2.1-alpha.
2096 - Avoid using tor_memeq() for checking relay cell integrity. This
2097 removes a possible performance bottleneck. Fixes part of bug
2098 12169; bugfix on 0.2.1.31.
2100 o Minor bugfixes (compilation):
2101 - Fix compilation of test_status.c when building with MVSC. Bugfix
2102 on 0.2.5.4-alpha. Patch from Gisle Vanem.
2103 - Resolve GCC complaints on OpenBSD about discarding constness in
2104 TO_{ORIGIN,OR}_CIRCUIT functions. Fixes part of bug 11633; bugfix
2105 on 0.1.1.23. Patch from Dana Koch.
2106 - Resolve clang complaints on OpenBSD with -Wshorten-64-to-32 due to
2107 treatment of long and time_t as comparable types. Fixes part of
2108 bug 11633. Patch from Dana Koch.
2109 - Make Tor compile correctly with --disable-buf-freelists. Fixes bug
2110 11623; bugfix on 0.2.5.3-alpha.
2111 - When deciding whether to build the 64-bit curve25519
2112 implementation, detect platforms where we can compile 128-bit
2113 arithmetic but cannot link it. Fixes bug 11729; bugfix on
2114 0.2.4.8-alpha. Patch from "conradev".
2115 - Fix compilation when DNS_CACHE_DEBUG is enabled. Fixes bug 11761;
2116 bugfix on 0.2.3.13-alpha. Found by "cypherpunks".
2117 - Fix compilation with dmalloc. Fixes bug 11605; bugfix
2120 o Minor bugfixes (Directory server):
2121 - When sending a compressed set of descriptors or microdescriptors,
2122 make sure to finalize the zlib stream. Previously, we would write
2123 all the compressed data, but if the last descriptor we wanted to
2124 send was missing or too old, we would not mark the stream as
2125 finished. This caused problems for decompression tools. Fixes bug
2126 11648; bugfix on 0.1.1.23.
2128 o Minor bugfixes (Linux seccomp sandbox):
2129 - Make the seccomp sandbox code compile under ARM Linux. Fixes bug
2130 11622; bugfix on 0.2.5.1-alpha.
2131 - Avoid crashing when re-opening listener ports with the seccomp
2132 sandbox active. Fixes bug 12115; bugfix on 0.2.5.1-alpha.
2133 - Avoid crashing with the seccomp sandbox enabled along with
2134 ConstrainedSockets. Fixes bug 12139; bugfix on 0.2.5.1-alpha.
2135 - When we receive a SIGHUP with the sandbox enabled, correctly
2136 support rotating our log files. Fixes bug 12032; bugfix
2138 - Avoid crash when running with sandboxing enabled and
2139 DirReqStatistics not disabled. Fixes bug 12035; bugfix
2141 - Fix a "BUG" warning when trying to write bridge-stats files with
2142 the Linux syscall sandbox filter enabled. Fixes bug 12041; bugfix
2144 - Prevent the sandbox from crashing on startup when run with the
2145 --enable-expensive-hardening configuration option. Fixes bug
2146 11477; bugfix on 0.2.5.4-alpha.
2147 - When running with DirPortFrontPage and sandboxing both enabled,
2148 reload the DirPortFrontPage correctly when restarting. Fixes bug
2149 12028; bugfix on 0.2.5.1-alpha.
2150 - Don't try to enable the sandbox when using the Tor binary to check
2151 its configuration, hash a passphrase, or so on. Doing so was
2152 crashing on startup for some users. Fixes bug 11609; bugfix
2154 - Avoid warnings when running with sandboxing and node statistics
2155 enabled at the same time. Fixes part of 12064; bugfix on
2156 0.2.5.1-alpha. Patch from Michael Wolf.
2157 - Avoid warnings when running with sandboxing enabled at the same
2158 time as cookie authentication, hidden services, or directory
2159 authority voting. Fixes part of 12064; bugfix on 0.2.5.1-alpha.
2160 - Do not allow options that require calls to exec to be enabled
2161 alongside the seccomp2 sandbox: they will inevitably crash. Fixes
2162 bug 12043; bugfix on 0.2.5.1-alpha.
2163 - Handle failures in getpwnam()/getpwuid() when running with the
2164 User option set and the Linux syscall sandbox enabled. Fixes bug
2165 11946; bugfix on 0.2.5.1-alpha.
2166 - Refactor the getaddrinfo workaround that the seccomp sandbox uses
2167 to avoid calling getaddrinfo() after installing the sandbox
2168 filters. Previously, it preloaded a cache with the IPv4 address
2169 for our hostname, and nothing else. Now, it loads the cache with
2170 every address that it used to initialize the Tor process. Fixes
2171 bug 11970; bugfix on 0.2.5.1-alpha.
2173 o Minor bugfixes (pluggable transports):
2174 - Enable the ExtORPortCookieAuthFile option, to allow changing the
2175 default location of the authentication token for the extended OR
2176 Port as used by sever-side pluggable transports. We had
2177 implemented this option before, but the code to make it settable
2178 had been omitted. Fixes bug 11635; bugfix on 0.2.5.1-alpha.
2179 - Avoid another 60-second delay when starting Tor in a pluggable-
2180 transport-using configuration when we already have cached
2181 descriptors for our bridges. Fixes bug 11965; bugfix
2184 o Minor bugfixes (client):
2185 - Avoid "Tried to open a socket with DisableNetwork set" warnings
2186 when starting a client with bridges configured and DisableNetwork
2187 set. (Tor launcher starts Tor with DisableNetwork set the first
2188 time it runs.) Fixes bug 10405; bugfix on 0.2.3.9-alpha.
2190 o Minor bugfixes (testing):
2191 - The Python parts of the test scripts now work on Python 3 as well
2192 as Python 2, so systems where '/usr/bin/python' is Python 3 will
2193 no longer have the tests break. Fixes bug 11608; bugfix
2195 - When looking for versions of python that we could run the tests
2196 with, check for "python2.7" and "python3.3"; previously we were
2197 only looking for "python", "python2", and "python3". Patch from
2198 Dana Koch. Fixes bug 11632; bugfix on 0.2.5.2-alpha.
2199 - Fix all valgrind warnings produced by the unit tests. There were
2200 over a thousand memory leak warnings previously, mostly produced
2201 by forgetting to free things in the unit test code. Fixes bug
2202 11618, bugfixes on many versions of Tor.
2204 o Minor bugfixes (tor-fw-helper):
2205 - Give a correct log message when tor-fw-helper fails to launch.
2206 (Previously, we would say something like "tor-fw-helper sent us a
2207 string we could not parse".) Fixes bug 9781; bugfix
2210 o Minor bugfixes (relay, threading):
2211 - Check return code on spawn_func() in cpuworker code, so that we
2212 don't think we've spawned a nonworking cpuworker and write junk to
2213 it forever. Fix related to bug 4345; bugfix on all released Tor
2214 versions. Found by "skruffy".
2215 - Use a pthread_attr to make sure that spawn_func() cannot return an
2216 error while at the same time launching a thread. Fix related to
2217 bug 4345; bugfix on all released Tor versions. Reported
2220 o Minor bugfixes (relay, oom prevention):
2221 - Correctly detect the total available system memory. We tried to do
2222 this in 0.2.5.4-alpha, but the code was set up to always return an
2223 error value, even on success. Fixes bug 11805; bugfix
2226 o Minor bugfixes (relay, other):
2227 - We now drop CREATE cells for already-existent circuit IDs and for
2228 zero-valued circuit IDs, regardless of other factors that might
2229 otherwise have called for DESTROY cells. Fixes bug 12191; bugfix
2231 - Avoid an illegal read from stack when initializing the TLS module
2232 using a version of OpenSSL without all of the ciphers used by the
2233 v2 link handshake. Fixes bug 12227; bugfix on 0.2.4.8-alpha. Found
2235 - When rejecting DATA cells for stream_id zero, still count them
2236 against the circuit's deliver window so that we don't fail to send
2237 a SENDME. Fixes bug 11246; bugfix on 0.2.4.10-alpha.
2239 o Minor bugfixes (logging):
2240 - Fix a misformatted log message about delayed directory fetches.
2241 Fixes bug 11654; bugfix on 0.2.5.3-alpha.
2242 - Squelch a spurious LD_BUG message "No origin circuit for
2243 successful SOCKS stream" in certain hidden service failure cases;
2247 - Include a tor.service file in contrib/dist for use with systemd.
2248 Some distributions will be able to use this file unmodified;
2249 others will need to tweak it, or write their own. Patch from Jamie
2250 Nguyen; resolves ticket 8368.
2253 - Clean up several option names in the manpage to match their real
2254 names, add the missing documentation for a couple of testing and
2255 directory authority options, remove the documentation for a
2256 V2-directory fetching option that no longer exists. Resolves
2258 - Correct the documenation so that it lists the correct directory
2259 for the stats files. (They are in a subdirectory called "stats",
2261 - In the manpage, move more authority-only options into the
2262 directory authority section so that operators of regular directory
2263 caches don't get confused.
2266 - The contrib directory has been sorted and tidied. Before, it was
2267 an unsorted dumping ground for useful and not-so-useful things.
2268 Now, it is divided based on functionality, and the items which
2269 seemed to be nonfunctional or useless have been removed. Resolves
2270 ticket 8966; based on patches from "rl1987".
2273 - Remove /tor/dbg-stability.txt URL that was meant to help debug WFU
2274 and MTBF calculations, but that nobody was using. Fixes ticket 11742.
2275 - The TunnelDirConns and PreferTunnelledDirConns options no longer
2276 exist; tunneled directory connections have been available since
2277 0.1.2.5-alpha, and turning them off is not a good idea. This is a
2278 brute-force fix for 10849, where "TunnelDirConns 0" would break
2282 Changes in version 0.2.4.22 - 2014-05-16
2283 Tor 0.2.4.22 backports numerous high-priority fixes from the Tor 0.2.5
2284 alpha release series. These include blocking all authority signing
2285 keys that may have been affected by the OpenSSL "heartbleed" bug,
2286 choosing a far more secure set of TLS ciphersuites by default, closing
2287 a couple of memory leaks that could be used to run a target relay out
2288 of RAM, and several others.
2290 o Major features (security, backport from 0.2.5.4-alpha):
2291 - Block authority signing keys that were used on authorities
2292 vulnerable to the "heartbleed" bug in OpenSSL (CVE-2014-0160). (We
2293 don't have any evidence that these keys _were_ compromised; we're
2294 doing this to be prudent.) Resolves ticket 11464.
2296 o Major bugfixes (security, OOM):
2297 - Fix a memory leak that could occur if a microdescriptor parse
2298 fails during the tokenizing step. This bug could enable a memory
2299 exhaustion attack by directory servers. Fixes bug 11649; bugfix
2302 o Major bugfixes (TLS cipher selection, backport from 0.2.5.4-alpha):
2303 - The relay ciphersuite list is now generated automatically based on
2304 uniform criteria, and includes all OpenSSL ciphersuites with
2305 acceptable strength and forward secrecy. Previously, we had left
2306 some perfectly fine ciphersuites unsupported due to omission or
2307 typo. Resolves bugs 11513, 11492, 11498, 11499. Bugs reported by
2308 'cypherpunks'. Bugfix on 0.2.4.8-alpha.
2309 - Relays now trust themselves to have a better view than clients of
2310 which TLS ciphersuites are better than others. (Thanks to bug
2311 11513, the relay list is now well-considered, whereas the client
2312 list has been chosen mainly for anti-fingerprinting purposes.)
2313 Relays prefer: AES over 3DES; then ECDHE over DHE; then GCM over
2314 CBC; then SHA384 over SHA256 over SHA1; and last, AES256 over
2315 AES128. Resolves ticket 11528.
2316 - Clients now try to advertise the same list of ciphersuites as
2317 Firefox 28. This change enables selection of (fast) GCM
2318 ciphersuites, disables some strange old ciphers, and stops
2319 advertising the ECDH (not to be confused with ECDHE) ciphersuites.
2320 Resolves ticket 11438.
2322 o Minor bugfixes (configuration, security):
2323 - When running a hidden service, do not allow TunneledDirConns 0:
2324 trying to set that option together with a hidden service would
2325 otherwise prevent the hidden service from running, and also make
2326 it publish its descriptors directly over HTTP. Fixes bug 10849;
2327 bugfix on 0.2.1.1-alpha.
2329 o Minor bugfixes (controller, backport from 0.2.5.4-alpha):
2330 - Avoid sending a garbage value to the controller when a circuit is
2331 cannibalized. Fixes bug 11519; bugfix on 0.2.3.11-alpha.
2333 o Minor bugfixes (exit relay, backport from 0.2.5.4-alpha):
2334 - Stop leaking memory when we successfully resolve a PTR record.
2335 Fixes bug 11437; bugfix on 0.2.4.7-alpha.
2337 o Minor bugfixes (bridge client, backport from 0.2.5.4-alpha):
2338 - Avoid 60-second delays in the bootstrapping process when Tor is
2339 launching for a second time while using bridges. Fixes bug 9229;
2340 bugfix on 0.2.0.3-alpha.
2342 o Minor bugfixes (relays and bridges, backport from 0.2.5.4-alpha):
2343 - Give the correct URL in the warning message when trying to run a
2344 relay on an ancient version of Windows. Fixes bug 9393.
2346 o Minor bugfixes (compilation):
2347 - Fix a compilation error when compiling with --disable-curve25519.
2348 Fixes bug 9700; bugfix on 0.2.4.17-rc.
2351 - Downgrade the warning severity for the the "md was still
2352 referenced 1 node(s)" warning. Tor 0.2.5.4-alpha has better code
2353 for trying to diagnose this bug, and the current warning in
2354 earlier versions of tor achieves nothing useful. Addresses warning
2357 o Minor features (log verbosity, backport from 0.2.5.4-alpha):
2358 - When we run out of usable circuit IDs on a channel, log only one
2359 warning for the whole channel, and describe how many circuits
2360 there were on the channel. Fixes part of ticket 11553.
2362 o Minor features (security, backport from 0.2.5.4-alpha):
2363 - Decrease the lower limit of MaxMemInCellQueues to 256 MBytes (but
2364 leave the default at 8GBytes), to better support Raspberry Pi
2365 users. Fixes bug 9686; bugfix on 0.2.4.14-alpha.
2367 o Documentation (backport from 0.2.5.4-alpha):
2368 - Correctly document that we search for a system torrc file before
2369 looking in ~/.torrc. Fixes documentation side of 9213; bugfix on
2373 Changes in version 0.2.5.4-alpha - 2014-04-25
2374 Tor 0.2.5.4-alpha includes several security and performance
2375 improvements for clients and relays, including blacklisting authority
2376 signing keys that were used while susceptible to the OpenSSL
2377 "heartbleed" bug, fixing two expensive functions on busy relays,
2378 improved TLS ciphersuite preference lists, support for run-time
2379 hardening on compilers that support AddressSanitizer, and more work on
2380 the Linux sandbox code.
2382 There are also several usability fixes for clients (especially clients
2383 that use bridges), two new TransPort protocols supported (one on
2384 OpenBSD, one on FreeBSD), and various other bugfixes.
2386 This release marks end-of-life for Tor 0.2.2.x; those Tor versions
2387 have accumulated many known flaws; everyone should upgrade.
2389 o Major features (security):
2390 - If you don't specify MaxMemInQueues yourself, Tor now tries to
2391 pick a good value based on your total system memory. Previously,
2392 the default was always 8 GB. You can still override the default by
2393 setting MaxMemInQueues yourself. Resolves ticket 11396.
2394 - Block authority signing keys that were used on authorities
2395 vulnerable to the "heartbleed" bug in OpenSSL (CVE-2014-0160). (We
2396 don't have any evidence that these keys _were_ compromised; we're
2397 doing this to be prudent.) Resolves ticket 11464.
2399 o Major features (relay performance):
2400 - Speed up server-side lookups of rendezvous and introduction point
2401 circuits by using hashtables instead of linear searches. These
2402 functions previously accounted between 3 and 7% of CPU usage on
2403 some busy relays. Resolves ticket 9841.
2404 - Avoid wasting CPU when extending a circuit over a channel that is
2405 nearly out of circuit IDs. Previously, we would do a linear scan
2406 over possible circuit IDs before finding one or deciding that we
2407 had exhausted our possibilities. Now, we try at most 64 random
2408 circuit IDs before deciding that we probably won't succeed. Fixes
2409 a possible root cause of ticket 11553.
2411 o Major features (seccomp2 sandbox, Linux only):
2412 - The seccomp2 sandbox can now run a test network for multiple hours
2413 without crashing. The sandbox is still experimental, and more bugs
2414 will probably turn up. To try it, enable "Sandbox 1" on a Linux
2415 host. Resolves ticket 11351.
2416 - Strengthen sandbox code: the sandbox can now test the arguments
2417 for rename(), and blocks _sysctl() entirely. Resolves another part
2419 - When the sandbox blocks a system call, it now tries to log a stack
2420 trace before exiting. Resolves ticket 11465.
2422 o Major bugfixes (TLS cipher selection):
2423 - The relay ciphersuite list is now generated automatically based on
2424 uniform criteria, and includes all OpenSSL ciphersuites with
2425 acceptable strength and forward secrecy. Previously, we had left
2426 some perfectly fine ciphersuites unsupported due to omission or
2427 typo. Resolves bugs 11513, 11492, 11498, 11499. Bugs reported by
2428 'cypherpunks'. Bugfix on 0.2.4.8-alpha.
2429 - Relays now trust themselves to have a better view than clients of
2430 which TLS ciphersuites are better than others. (Thanks to bug
2431 11513, the relay list is now well-considered, whereas the client
2432 list has been chosen mainly for anti-fingerprinting purposes.)
2433 Relays prefer: AES over 3DES; then ECDHE over DHE; then GCM over
2434 CBC; then SHA384 over SHA256 over SHA1; and last, AES256 over
2435 AES128. Resolves ticket 11528.
2436 - Clients now try to advertise the same list of ciphersuites as
2437 Firefox 28. This change enables selection of (fast) GCM
2438 ciphersuites, disables some strange old ciphers, and stops
2439 advertising the ECDH (not to be confused with ECDHE) ciphersuites.
2440 Resolves ticket 11438.
2442 o Major bugfixes (bridge client):
2443 - Avoid 60-second delays in the bootstrapping process when Tor is
2444 launching for a second time while using bridges. Fixes bug 9229;
2445 bugfix on 0.2.0.3-alpha.
2447 o Minor features (transparent proxy, *BSD):
2448 - Support FreeBSD's ipfw firewall interface for TransPort ports on
2449 FreeBSD. To enable it, set "TransProxyType ipfw". Resolves ticket
2450 10267; patch from "yurivict".
2451 - Support OpenBSD's divert-to rules with the pf firewall for
2452 transparent proxy ports. To enable it, set "TransProxyType
2453 pf-divert". This allows Tor to run a TransPort transparent proxy
2454 port on OpenBSD 4.4 or later without root privileges. See the
2455 pf.conf(5) manual page for information on configuring pf to use
2456 divert-to rules. Closes ticket 10896; patch from Dana Koch.
2458 o Minor features (security):
2459 - New --enable-expensive-hardening option to enable security
2460 hardening options that consume nontrivial amounts of CPU and
2461 memory. Right now, this includes AddressSanitizer and UbSan, which
2462 are supported in newer versions of GCC and Clang. Closes ticket
2465 o Minor features (log verbosity):
2466 - Demote the message that we give when a flushing connection times
2467 out for too long from NOTICE to INFO. It was usually meaningless.
2468 Resolves ticket 5286.
2469 - Don't log so many notice-level bootstrapping messages at startup
2470 about downloading descriptors. Previously, we'd log a notice
2471 whenever we learned about more routers. Now, we only log a notice
2472 at every 5% of progress. Fixes bug 9963.
2473 - Warn less verbosely when receiving a malformed
2474 ESTABLISH_RENDEZVOUS cell. Fixes ticket 11279.
2475 - When we run out of usable circuit IDs on a channel, log only one
2476 warning for the whole channel, and describe how many circuits
2477 there were on the channel. Fixes part of ticket 11553.
2479 o Minor features (relay):
2480 - If a circuit timed out for at least 3 minutes, check if we have a
2481 new external IP address, and publish a new descriptor with the new
2482 IP address if it changed. Resolves ticket 2454.
2484 o Minor features (controller):
2485 - Make the entire exit policy available from the control port via
2486 GETINFO exit-policy/*. Implements enhancement 7952. Patch from
2488 - Because of the fix for ticket 11396, the real limit for memory
2489 usage may no longer match the configured MaxMemInQueues value. The
2490 real limit is now exposed via GETINFO limits/max-mem-in-queues.
2492 o Minor features (bridge client):
2493 - Report a more useful failure message when we can't connect to a
2494 bridge because we don't have the right pluggable transport
2495 configured. Resolves ticket 9665. Patch from Fábio J. Bertinatto.
2497 o Minor features (diagnostic):
2498 - Add more log messages to diagnose bug 7164, which causes
2499 intermittent "microdesc_free() called but md was still referenced"
2500 warnings. We now include more information, to figure out why we
2501 might be cleaning a microdescriptor for being too old if it's
2502 still referenced by a live node_t object.
2504 o Minor bugfixes (client, DNSPort):
2505 - When using DNSPort, try to respond to AAAA requests with AAAA
2506 answers. Previously, we hadn't looked at the request type when
2507 deciding which answer type to prefer. Fixes bug 10468; bugfix on
2509 - When receiving a DNS query for an unsupported record type, reply
2510 with no answer rather than with a NOTIMPL error. This behavior
2511 isn't correct either, but it will break fewer client programs, we
2512 hope. Fixes bug 10268; bugfix on 0.2.0.1-alpha. Original patch
2515 o Minor bugfixes (exit relay):
2516 - Stop leaking memory when we successfully resolve a PTR record.
2517 Fixes bug 11437; bugfix on 0.2.4.7-alpha.
2519 o Minor bugfixes (bridge client):
2520 - Stop accepting bridge lines containing hostnames. Doing so would
2521 cause clients to perform DNS requests on the hostnames, which was
2522 not sensible behavior. Fixes bug 10801; bugfix on 0.2.0.1-alpha.
2523 - Avoid a 60-second delay in the bootstrapping process when a Tor
2524 client with pluggable transports re-reads its configuration at
2525 just the wrong time. Re-fixes bug 11156; bugfix on 0.2.5.3-alpha.
2527 o Minor bugfixes (client, logging during bootstrap):
2528 - Warn only once if we start logging in an unsafe way. Previously,
2529 we complain as many times as we had problems. Fixes bug 9870;
2530 bugfix on 0.2.5.1-alpha.
2531 - Only report the first fatal bootstrap error on a given OR
2532 connection. This stops us from telling the controller bogus error
2533 messages like "DONE". Fixes bug 10431; bugfix on 0.2.1.1-alpha.
2534 - Be more helpful when trying to run sandboxed on Linux without
2535 libseccomp. Instead of saying "Sandbox is not implemented on this
2536 platform", we now explain that we need to be built with
2537 libseccomp. Fixes bug 11543; bugfix on 0.2.5.1-alpha.
2538 - Avoid generating spurious warnings when starting with
2539 DisableNetwork enabled. Fixes bug 11200 and bug 10405; bugfix on
2542 o Minor bugfixes (closing OR connections):
2543 - If write_to_buf() in connection_write_to_buf_impl_() ever fails,
2544 check if it's an or_connection_t and correctly call
2545 connection_or_close_for_error() rather than
2546 connection_mark_for_close() directly. Fixes bug 11304; bugfix on
2548 - When closing all connections on setting DisableNetwork to 1, use
2549 connection_or_close_normally() rather than closing OR connections
2550 out from under the channel layer. Fixes bug 11306; bugfix on
2553 o Minor bugfixes (controller):
2554 - Avoid sending a garbage value to the controller when a circuit is
2555 cannibalized. Fixes bug 11519; bugfix on 0.2.3.11-alpha.
2557 o Minor bugfixes (tor-fw-helper):
2558 - Allow tor-fw-helper to build again by adding src/ext to its
2559 CPPFLAGS. Fixes bug 11296; bugfix on 0.2.5.3-alpha.
2561 o Minor bugfixes (bridges):
2562 - Avoid potential crashes or bad behavior when launching a
2563 server-side managed proxy with ORPort or ExtORPort temporarily
2564 disabled. Fixes bug 9650; bugfix on 0.2.3.16-alpha.
2566 o Minor bugfixes (platform-specific):
2567 - Fix compilation on Solaris, which does not have <endian.h>. Fixes
2568 bug 11426; bugfix on 0.2.5.3-alpha.
2569 - When dumping a malformed directory object to disk, save it in
2570 binary mode on Windows, not text mode. Fixes bug 11342; bugfix on
2572 - Don't report failures from make_socket_reuseable() on incoming
2573 sockets on OSX: this can happen when incoming connections close
2574 early. Fixes bug 10081.
2576 o Minor bugfixes (trivial memory leaks):
2577 - Fix a small memory leak when signing a directory object. Fixes bug
2578 11275; bugfix on 0.2.4.13-alpha.
2579 - Free placeholder entries in our circuit table at exit; fixes a
2580 harmless memory leak. Fixes bug 11278; bugfix on 0.2.5.1-alpha.
2581 - Don't re-initialize a second set of OpenSSL mutexes when starting
2582 up. Previously, we'd make one set of mutexes, and then immediately
2583 replace them with another. Fixes bug 11726; bugfix on
2585 - Resolve some memory leaks found by coverity in the unit tests, on
2586 exit in tor-gencert, and on a failure to compute digests for our
2587 own keys when generating a v3 networkstatus vote. These leaks
2588 should never have affected anyone in practice.
2590 o Minor bugfixes (hidden service):
2591 - Only retry attempts to connect to a chosen rendezvous point 8
2592 times, not 30. Fixes bug 4241; bugfix on 0.1.0.1-rc.
2594 o Minor bugfixes (misc code correctness):
2595 - Fix various instances of undefined behavior in channeltls.c,
2596 tor_memmem(), and eventdns.c that would cause us to construct
2597 pointers to memory outside an allocated object. (These invalid
2598 pointers were not accessed, but C does not even allow them to
2599 exist.) Fixes bug 10363; bugfixes on 0.1.1.1-alpha, 0.1.2.1-alpha,
2600 0.2.0.10-alpha, and 0.2.3.6-alpha. Reported by "bobnomnom".
2601 - Use the AddressSanitizer and Ubsan sanitizers (in clang-3.4) to
2602 fix some miscellaneous errors in our tests and codebase. Fixes bug
2603 11232. Bugfixes on versions back as far as 0.2.1.11-alpha.
2604 - Always check return values for unlink, munmap, UnmapViewOfFile;
2605 check strftime return values more often. In some cases all we can
2606 do is report a warning, but this may help prevent deeper bugs from
2607 going unnoticed. Closes ticket 8787; bugfixes on many, many tor
2609 - Fix numerous warnings from the clang "scan-build" static analyzer.
2610 Some of these are programming style issues; some of them are false
2611 positives that indicated awkward code; some are undefined behavior
2612 cases related to constructing (but not using) invalid pointers;
2613 some are assumptions about API behavior; some are (harmlessly)
2614 logging sizeof(ptr) bytes from a token when sizeof(*ptr) would be
2615 correct; and one or two are genuine bugs that weren't reachable
2616 from the rest of the program. Fixes bug 8793; bugfixes on many,
2620 - Build the torify.1 manpage again. Previously, we were only trying
2621 to build it when also building tor-fw-helper. That's why we didn't
2622 notice that we'd broken the ability to build it. Fixes bug 11321;
2623 bugfix on 0.2.5.1-alpha.
2624 - Fix the layout of the SOCKSPort flags in the manpage. Fixes bug
2625 11061; bugfix on 0.2.4.7-alpha.
2626 - Correctly document that we search for a system torrc file before
2627 looking in ~/.torrc. Fixes documentation side of 9213; bugfix on
2629 - Resolve warnings from Doxygen.
2631 o Code simplifications and refactoring:
2632 - Remove is_internal_IP() function. Resolves ticket 4645.
2633 - Remove unused function circuit_dump_by_chan from circuitlist.c.
2634 Closes issue 9107; patch from "marek".
2635 - Change our use of the ENUM_BF macro to avoid declarations that
2638 o Deprecated versions:
2639 - Tor 0.2.2.x has reached end-of-life; it has received no patches or
2640 attention for some while. Directory authorities no longer accept
2641 descriptors from relays running any version of Tor prior to Tor
2642 0.2.3.16-alpha. Resolves ticket 11149.
2645 - New macros in test.h to simplify writing mock-functions for unit
2646 tests. Part of ticket 11507. Patch from Dana Koch.
2647 - Complete tests for the status.c module. Resolves ticket 11507.
2648 Patch from Dana Koch.
2651 - Remove all code for the long unused v1 directory protocol.
2652 Resolves ticket 11070.
2655 Changes in version 0.2.5.3-alpha - 2014-03-22
2656 Tor 0.2.5.3-alpha includes all the fixes from 0.2.4.21. It contains
2657 two new anti-DoS features for Tor relays, resolves a bug that kept
2658 SOCKS5 support for IPv6 from working, fixes several annoying usability
2659 issues for bridge users, and removes more old code for unused
2662 The Tor 0.2.5.x release series is now in patch-freeze: no feature
2663 patches not already written will be considered for inclusion in 0.2.5.x.
2665 o Major features (relay security, DoS-resistance):
2666 - When deciding whether we have run out of memory and we need to
2667 close circuits, also consider memory allocated in buffers for
2668 streams attached to each circuit.
2670 This change, which extends an anti-DoS feature introduced in
2671 0.2.4.13-alpha and improved in 0.2.4.14-alpha, lets Tor exit relays
2672 better resist more memory-based DoS attacks than before. Since the
2673 MaxMemInCellQueues option now applies to all queues, it is renamed
2674 to MaxMemInQueues. This feature fixes bug 10169.
2675 - Avoid hash-flooding denial-of-service attacks by using the secure
2676 SipHash-2-4 hash function for our hashtables. Without this
2677 feature, an attacker could degrade performance of a targeted
2678 client or server by flooding their data structures with a large
2679 number of entries to be stored at the same hash table position,
2680 thereby slowing down the Tor instance. With this feature, hash
2681 table positions are derived from a randomized cryptographic key,
2682 and an attacker cannot predict which entries will collide. Closes
2684 - Decrease the lower limit of MaxMemInQueues to 256 MBytes (but leave
2685 the default at 8GBytes), to better support Raspberry Pi users. Fixes
2686 bug 9686; bugfix on 0.2.4.14-alpha.
2688 o Minor features (bridges, pluggable transports):
2689 - Bridges now write the SHA1 digest of their identity key
2690 fingerprint (that is, a hash of a hash of their public key) to
2691 notice-level logs, and to a new hashed-fingerprint file. This
2692 information will help bridge operators look up their bridge in
2693 Globe and similar tools. Resolves ticket 10884.
2694 - Improve the message that Tor displays when running as a bridge
2695 using pluggable transports without an Extended ORPort listener.
2696 Also, log the message in the log file too. Resolves ticket 11043.
2698 o Minor features (other):
2699 - Add a new option, PredictedPortsRelevanceTime, to control how long
2700 after having received a request to connect to a given port Tor
2701 will try to keep circuits ready in anticipation of future requests
2702 for that port. Patch from "unixninja92"; implements ticket 9176.
2703 - Generate a warning if any ports are listed in the SocksPolicy,
2704 DirPolicy, AuthDirReject, AuthDirInvalid, AuthDirBadDir, or
2705 AuthDirBadExit options. (These options only support address
2706 ranges.) Fixes part of ticket 11108.
2707 - Update geoip and geoip6 to the February 7 2014 Maxmind GeoLite2
2710 o Minor bugfixes (new since 0.2.5.2-alpha, also in 0.2.4.21):
2711 - Build without warnings under clang 3.4. (We have some macros that
2712 define static functions only some of which will get used later in
2713 the module. Starting with clang 3.4, these give a warning unless the
2714 unused attribute is set on them.) Resolves ticket 10904.
2715 - Fix build warnings about missing "a2x" comment when building the
2716 manpages from scratch on OpenBSD; OpenBSD calls it "a2x.py".
2717 Fixes bug 10929; bugfix on 0.2.2.9-alpha. Patch from Dana Koch.
2719 o Minor bugfixes (client):
2720 - Improve the log message when we can't connect to a hidden service
2721 because all of the hidden service directory nodes hosting its
2722 descriptor are excluded. Improves on our fix for bug 10722, which
2723 was a bugfix on 0.2.0.10-alpha.
2724 - Raise a control port warning when we fail to connect to all of
2725 our bridges. Previously, we didn't inform the controller, and
2726 the bootstrap process would stall. Fixes bug 11069; bugfix on
2728 - Exit immediately when a process-owning controller exits.
2729 Previously, tor relays would wait for a little while after their
2730 controller exited, as if they had gotten an INT signal -- but this
2731 was problematic, since there was no feedback for the user. To do a
2732 clean shutdown, controllers should send an INT signal and give Tor
2733 a chance to clean up. Fixes bug 10449; bugfix on 0.2.2.28-beta.
2734 - Stop attempting to connect to bridges before our pluggable
2735 transports are configured (harmless but resulted in some erroneous
2736 log messages). Fixes bug 11156; bugfix on 0.2.3.2-alpha.
2737 - Fix connections to IPv6 addresses over SOCKS5. Previously, we were
2738 generating incorrect SOCKS5 responses, and confusing client
2739 applications. Fixes bug 10987; bugfix on 0.2.4.7-alpha.
2741 o Minor bugfixes (relays and bridges):
2742 - Avoid crashing on a malformed resolv.conf file when running a
2743 relay using Libevent 1. Fixes bug 8788; bugfix on 0.1.1.23.
2744 - Non-exit relays no longer launch mock DNS requests to check for
2745 DNS hijacking. This has been unnecessary since 0.2.1.7-alpha, when
2746 non-exit relays stopped servicing DNS requests. Fixes bug 965;
2747 bugfix on 0.2.1.7-alpha. Patch from Matt Pagan.
2748 - Bridges now report complete directory request statistics. Related
2749 to bug 5824; bugfix on 0.2.2.1-alpha.
2750 - Bridges now never collect statistics that were designed for
2751 relays. Fixes bug 5824; bugfix on 0.2.3.8-alpha.
2752 - Stop giving annoying warning messages when we decide not to launch
2753 a pluggable transport proxy that we don't need (because there are
2754 no bridges configured to use it). Resolves ticket 5018; bugfix
2756 - Give the correct URL in the warning message when trying to run a
2757 relay on an ancient version of Windows. Fixes bug 9393.
2759 o Minor bugfixes (backtrace support):
2760 - Support automatic backtraces on more platforms by using the
2761 "-fasynchronous-unwind-tables" compiler option. This option is
2762 needed for platforms like 32-bit Intel where "-fomit-frame-pointer"
2763 is on by default and table generation is not. This doesn't yet
2764 add Windows support; only Linux, OSX, and some BSDs are affected.
2765 Reported by 'cypherpunks'; fixes bug 11047; bugfix on 0.2.5.2-alpha.
2766 - Avoid strange behavior if two threads hit failed assertions at the
2767 same time and both try to log backtraces at once. (Previously, if
2768 this had happened, both threads would have stored their intermediate
2769 results in the same buffer, and generated junk outputs.) Reported by
2770 "cypherpunks". Fixes bug 11048; bugfix on 0.2.5.2-alpha.
2771 - Fix a compiler warning in format_number_sigsafe(). Bugfix on
2772 0.2.5.2-alpha; patch from Nick Hopper.
2774 o Minor bugfixes (unit tests):
2775 - Fix a small bug in the unit tests that might have made the tests
2776 call 'chmod' with an uninitialized bitmask. Fixes bug 10928;
2777 bugfix on 0.2.5.1-alpha. Patch from Dana Koch.
2780 - Remove all remaining code related to version-0 hidden service
2781 descriptors: they have not been in use since 0.2.2.1-alpha. Fixes
2782 the rest of bug 10841.
2785 - Document in the manpage that "KBytes" may also be written as
2786 "kilobytes" or "KB", that "Kbits" may also be written as
2787 "kilobits", and so forth. Closes ticket 9222.
2788 - Document that the ClientOnly config option overrides ORPort.
2789 Our old explanation made ClientOnly sound as though it did
2790 nothing at all. Resolves bug 9059.
2791 - Explain that SocksPolicy, DirPolicy, and similar options don't
2792 take port arguments. Fixes the other part of ticket 11108.
2793 - Fix a comment about the rend_server_descriptor_t.protocols field
2794 to more accurately describe its range. Also, make that field
2795 unsigned, to more accurately reflect its usage. Fixes bug 9099;
2796 bugfix on 0.2.1.5-alpha.
2797 - Fix the manpage's description of HiddenServiceAuthorizeClient:
2798 the maximum client name length is 16, not 19. Fixes bug 11118;
2799 bugfix on 0.2.1.6-alpha.
2801 o Code simplifications and refactoring:
2802 - Get rid of router->address, since in all cases it was just the
2803 string representation of router->addr. Resolves ticket 5528.
2805 o Test infrastructure:
2806 - Update to the latest version of tinytest.
2807 - Improve the tinytest implementation of string operation tests so
2808 that comparisons with NULL strings no longer crash the tests; they
2809 now just fail, normally. Fixes bug 9004; bugfix on 0.2.2.4-alpha.
2812 Changes in version 0.2.4.21 - 2014-02-28
2813 Tor 0.2.4.21 further improves security against potential adversaries who
2814 find breaking 1024-bit crypto doable, and backports several stability
2815 and robustness patches from the 0.2.5 branch.
2817 o Major features (client security):
2818 - When we choose a path for a 3-hop circuit, make sure it contains
2819 at least one relay that supports the NTor circuit extension
2820 handshake. Otherwise, there is a chance that we're building
2821 a circuit that's worth attacking by an adversary who finds
2822 breaking 1024-bit crypto doable, and that chance changes the game
2823 theory. Implements ticket 9777.
2826 - Do not treat streams that fail with reason
2827 END_STREAM_REASON_INTERNAL as indicating a definite circuit failure,
2828 since it could also indicate an ENETUNREACH connection error. Fixes
2829 part of bug 10777; bugfix on 0.2.4.8-alpha.
2831 o Code simplification and refactoring:
2832 - Remove data structures which were introduced to implement the
2833 CellStatistics option: they are now redundant with the new timestamp
2834 field in the regular packed_cell_t data structure, which we did
2835 in 0.2.4.18-rc in order to resolve bug 9093. Resolves ticket 10870.
2838 - Always clear OpenSSL bignums before freeing them -- even bignums
2839 that don't contain secrets. Resolves ticket 10793. Patch by
2841 - Build without warnings under clang 3.4. (We have some macros that
2842 define static functions only some of which will get used later in
2843 the module. Starting with clang 3.4, these give a warning unless the
2844 unused attribute is set on them.) Resolves ticket 10904.
2845 - Update geoip and geoip6 files to the February 7 2014 Maxmind
2846 GeoLite2 Country database.
2849 - Set the listen() backlog limit to the largest actually supported
2850 on the system, not to the value in a header file. Fixes bug 9716;
2851 bugfix on every released Tor.
2852 - Treat ENETUNREACH, EACCES, and EPERM connection failures at an
2853 exit node as a NOROUTE error, not an INTERNAL error, since they
2854 can apparently happen when trying to connect to the wrong sort
2855 of netblocks. Fixes part of bug 10777; bugfix on 0.1.0.1-rc.
2856 - Fix build warnings about missing "a2x" comment when building the
2857 manpages from scratch on OpenBSD; OpenBSD calls it "a2x.py".
2858 Fixes bug 10929; bugfix on 0.2.2.9-alpha. Patch from Dana Koch.
2859 - Avoid a segfault on SIGUSR1, where we had freed a connection but did
2860 not entirely remove it from the connection lists. Fixes bug 9602;
2861 bugfix on 0.2.4.4-alpha.
2862 - Fix a segmentation fault in our benchmark code when running with
2863 Fedora's OpenSSL package, or any other OpenSSL that provides
2864 ECDH but not P224. Fixes bug 10835; bugfix on 0.2.4.8-alpha.
2865 - Turn "circuit handshake stats since last time" log messages into a
2866 heartbeat message. Fixes bug 10485; bugfix on 0.2.4.17-rc.
2868 o Documentation fixes:
2869 - Document that all but one DirPort entry must have the NoAdvertise
2870 flag set. Fixes bug 10470; bugfix on 0.2.3.3-alpha / 0.2.3.16-alpha.
2873 Changes in version 0.2.5.2-alpha - 2014-02-13
2874 Tor 0.2.5.2-alpha includes all the fixes from 0.2.4.18-rc and 0.2.4.20,
2875 like the "poor random number generation" fix and the "building too many
2876 circuits" fix. It also further improves security against potential
2877 adversaries who find breaking 1024-bit crypto doable, and launches
2878 pluggable transports on demand (which gets us closer to integrating
2879 pluggable transport support by default -- not to be confused with Tor
2880 bundles enabling pluggable transports and bridges by default).
2882 o Major features (client security):
2883 - When we choose a path for a 3-hop circuit, make sure it contains
2884 at least one relay that supports the NTor circuit extension
2885 handshake. Otherwise, there is a chance that we're building
2886 a circuit that's worth attacking by an adversary who finds
2887 breaking 1024-bit crypto doable, and that chance changes the game
2888 theory. Implements ticket 9777.
2889 - Clients now look at the "usecreatefast" consensus parameter to
2890 decide whether to use CREATE_FAST or CREATE cells for the first hop
2891 of their circuit. This approach can improve security on connections
2892 where Tor's circuit handshake is stronger than the available TLS
2893 connection security levels, but the tradeoff is more computational
2894 load on guard relays. Implements proposal 221. Resolves ticket 9386.
2896 o Major features (bridges):
2897 - Don't launch pluggable transport proxies if we don't have any
2898 bridges configured that would use them. Now we can list many
2899 pluggable transports, and Tor will dynamically start one when it
2900 hears a bridge address that needs it. Resolves ticket 5018.
2901 - The bridge directory authority now assigns status flags (Stable,
2902 Guard, etc) to bridges based on thresholds calculated over all
2903 Running bridges. Now bridgedb can finally make use of its features
2904 to e.g. include at least one Stable bridge in its answers. Fixes
2907 o Major features (other):
2908 - Extend ORCONN controller event to include an "ID" parameter,
2909 and add four new controller event types CONN_BW, CIRC_BW,
2910 CELL_STATS, and TB_EMPTY that show connection and circuit usage.
2911 The new events are emitted in private Tor networks only, with the
2912 goal of being able to better track performance and load during
2913 full-network simulations. Implements proposal 218 and ticket 7359.
2914 - On some platforms (currently: recent OSX versions, glibc-based
2915 platforms that support the ELF format, and a few other
2916 Unix-like operating systems), Tor can now dump stack traces
2917 when a crash occurs or an assertion fails. By default, traces
2918 are dumped to stderr (if possible) and to any logs that are
2919 reporting errors. Implements ticket 9299.
2922 - Avoid a segfault on SIGUSR1, where we had freed a connection but did
2923 not entirely remove it from the connection lists. Fixes bug 9602;
2924 bugfix on 0.2.4.4-alpha.
2925 - Do not treat streams that fail with reason
2926 END_STREAM_REASON_INTERNAL as indicating a definite circuit failure,
2927 since it could also indicate an ENETUNREACH connection error. Fixes
2928 part of bug 10777; bugfix on 0.2.4.8-alpha.
2930 o Major bugfixes (new since 0.2.5.1-alpha, also in 0.2.4.20):
2931 - Do not allow OpenSSL engines to replace the PRNG, even when
2932 HardwareAccel is set. The only default builtin PRNG engine uses
2933 the Intel RDRAND instruction to replace the entire PRNG, and
2934 ignores all attempts to seed it with more entropy. That's
2935 cryptographically stupid: the right response to a new alleged
2936 entropy source is never to discard all previously used entropy
2937 sources. Fixes bug 10402; works around behavior introduced in
2938 OpenSSL 1.0.0. Diagnosis and investigation thanks to "coderman"
2940 - Fix assertion failure when AutomapHostsOnResolve yields an IPv6
2941 address. Fixes bug 10465; bugfix on 0.2.4.7-alpha.
2942 - Avoid launching spurious extra circuits when a stream is pending.
2943 This fixes a bug where any circuit that _wasn't_ unusable for new
2944 streams would be treated as if it were, causing extra circuits to
2945 be launched. Fixes bug 10456; bugfix on 0.2.4.12-alpha.
2947 o Major bugfixes (new since 0.2.5.1-alpha, also in 0.2.4.18-rc):
2948 - No longer stop reading or writing on cpuworker connections when
2949 our rate limiting buckets go empty. Now we should handle circuit
2950 handshake requests more promptly. Resolves bug 9731.
2951 - Stop trying to bootstrap all our directory information from
2952 only our first guard. Discovered while fixing bug 9946; bugfix
2955 o Minor features (bridges, pluggable transports):
2956 - Add threshold cutoffs to the networkstatus document created by
2957 the Bridge Authority. Fixes bug 1117.
2958 - On Windows, spawn background processes using the CREATE_NO_WINDOW
2959 flag. Now Tor Browser Bundle 3.5 with pluggable transports enabled
2960 doesn't pop up a blank console window. (In Tor Browser Bundle 2.x,
2961 Vidalia set this option for us.) Implements ticket 10297.
2963 o Minor features (security):
2964 - Always clear OpenSSL bignums before freeing them -- even bignums
2965 that don't contain secrets. Resolves ticket 10793. Patch by
2968 o Minor features (config options and command line):
2969 - Add an --allow-missing-torrc commandline option that tells Tor to
2970 run even if the configuration file specified by -f is not available.
2971 Implements ticket 10060.
2972 - Add support for the TPROXY transparent proxying facility on Linux.
2973 See documentation for the new TransProxyType option for more
2974 details. Implementation by "thomo". Closes ticket 10582.
2976 o Minor features (controller):
2977 - Add a new "HS_DESC" controller event that reports activities
2978 related to hidden service descriptors. Resolves ticket 8510.
2979 - New "DROPGUARDS" controller command to forget all current entry
2980 guards. Not recommended for ordinary use, since replacing guards
2981 too frequently makes several attacks easier. Resolves ticket 9934;
2984 o Minor features (build):
2985 - Assume that a user using ./configure --host wants to cross-compile,
2986 and give an error if we cannot find a properly named
2987 tool-chain. Add a --disable-tool-name-check option to proceed
2988 nevertheless. Addresses ticket 9869. Patch by Benedikt Gollatz.
2989 - If we run ./configure and the compiler recognizes -fstack-protector
2990 but the linker rejects it, warn the user about a potentially missing
2991 libssp package. Addresses ticket 9948. Patch from Benedikt Gollatz.
2993 o Minor features (testing):
2994 - If Python is installed, "make check" now runs extra tests beyond
2995 the unit test scripts.
2996 - When bootstrapping a test network, sometimes very few relays get
2997 the Guard flag. Now a new option "TestingDirAuthVoteGuard" can
2998 specify a set of relays which should be voted Guard regardless of
2999 their uptime or bandwidth. Addresses ticket 9206.
3001 o Minor features (log messages):
3002 - When ServerTransportPlugin is set on a bridge, Tor can write more
3003 useful statistics about bridge use in its extrainfo descriptors,
3004 but only if the Extended ORPort ("ExtORPort") is set too. Add a
3005 log message to inform the user in this case. Resolves ticket 9651.
3006 - When receiving a new controller connection, log the origin address.
3007 Resolves ticket 9698; patch from "sigpipe".
3008 - When logging OpenSSL engine status at startup, log the status of
3009 more engines. Fixes ticket 10043; patch from Joshua Datko.
3010 - Turn "circuit handshake stats since last time" log messages into a
3011 heartbeat message. Fixes bug 10485; bugfix on 0.2.4.17-rc.
3013 o Minor features (new since 0.2.5.1-alpha, also in 0.2.4.18-rc):
3014 - Improve the circuit queue out-of-memory handler. Previously, when
3015 we ran low on memory, we'd close whichever circuits had the most
3016 queued cells. Now, we close those that have the *oldest* queued
3017 cells, on the theory that those are most responsible for us
3018 running low on memory. Based on analysis from a forthcoming paper
3019 by Jansen, Tschorsch, Johnson, and Scheuermann. Fixes bug 9093.
3020 - Generate bootstrapping status update events correctly when fetching
3021 microdescriptors. Fixes bug 9927.
3022 - Update to the October 2 2013 Maxmind GeoLite Country database.
3024 o Minor bugfixes (clients):
3025 - When closing a channel that has already been open, do not close
3026 pending circuits that were waiting to connect to the same relay.
3027 Fixes bug 9880; bugfix on 0.2.5.1-alpha. Thanks to skruffy for
3030 o Minor bugfixes (relays):
3031 - Treat ENETUNREACH, EACCES, and EPERM connection failures at an
3032 exit node as a NOROUTE error, not an INTERNAL error, since they
3033 can apparently happen when trying to connect to the wrong sort
3034 of netblocks. Fixes part of bug 10777; bugfix on 0.1.0.1-rc.
3036 o Minor bugfixes (bridges):
3037 - Fix a bug where the first connection works to a bridge that uses a
3038 pluggable transport with client-side parameters, but we don't send
3039 the client-side parameters on subsequent connections. (We don't
3040 use any pluggable transports with client-side parameters yet,
3041 but ScrambleSuit will soon become the first one.) Fixes bug 9162;
3042 bugfix on 0.2.0.3-alpha. Based on a patch from "rl1987".
3044 o Minor bugfixes (node selection):
3045 - If ExcludeNodes is set, consider non-excluded hidden service
3046 directory servers before excluded ones. Do not consider excluded
3047 hidden service directory servers at all if StrictNodes is
3048 set. (Previously, we would sometimes decide to connect to those
3049 servers, and then realize before we initiated a connection that
3050 we had excluded them.) Fixes bug 10722; bugfix on 0.2.0.10-alpha.
3052 - If we set the ExitNodes option but it doesn't include any nodes
3053 that have the Exit flag, we would choose not to bootstrap. Now we
3054 bootstrap so long as ExitNodes includes nodes which can exit to
3055 some port. Fixes bug 10543; bugfix on 0.2.4.10-alpha.
3057 o Minor bugfixes (controller and command-line):
3058 - If changing a config option via "setconf" fails in a recoverable
3059 way, we used to nonetheless write our new control ports to the
3060 file described by the "ControlPortWriteToFile" option. Now we only
3061 write out that file if we successfully switch to the new config
3062 option. Fixes bug 5605; bugfix on 0.2.2.26-beta. Patch from "Ryman".
3063 - When a command-line option such as --version or --help that
3064 ordinarily implies --hush appears on the command line along with
3065 --quiet, then actually obey --quiet. Previously, we obeyed --quiet
3066 only if it appeared later on the command line. Fixes bug 9578;
3067 bugfix on 0.2.5.1-alpha.
3069 o Minor bugfixes (code correctness):
3070 - Previously we used two temporary files when writing descriptors to
3071 disk; now we only use one. Fixes bug 1376.
3072 - Remove an erroneous (but impossible and thus harmless) pointer
3073 comparison that would have allowed compilers to skip a bounds
3074 check in channeltls.c. Fixes bugs 10313 and 9980; bugfix on
3075 0.2.0.10-alpha. Noticed by Jared L Wong and David Fifield.
3076 - Fix an always-true assertion in pluggable transports code so it
3077 actually checks what it was trying to check. Fixes bug 10046;
3078 bugfix on 0.2.3.9-alpha. Found by "dcb".
3080 o Minor bugfixes (protocol correctness):
3081 - When receiving a VERSIONS cell with an odd number of bytes, close
3082 the connection immediately since the cell is malformed. Fixes bug
3083 10365; bugfix on 0.2.0.10-alpha. Spotted by "bobnomnom"; fix by
3086 o Minor bugfixes (build):
3087 - Restore the ability to compile Tor with V2_HANDSHAKE_SERVER
3088 turned off (that is, without support for v2 link handshakes). Fixes
3089 bug 4677; bugfix on 0.2.3.2-alpha. Patch from "piet".
3090 - Fix compilation warnings and startup issues when running with
3091 "Sandbox 1" and libseccomp-2.1.0. Fixes bug 10563; bugfix on
3093 - Fix compilation on Solaris 9, which didn't like us having an
3094 identifier named "sun". Fixes bug 10565; bugfix in 0.2.5.1-alpha.
3096 o Minor bugfixes (testing):
3097 - Fix a segmentation fault in our benchmark code when running with
3098 Fedora's OpenSSL package, or any other OpenSSL that provides
3099 ECDH but not P224. Fixes bug 10835; bugfix on 0.2.4.8-alpha.
3101 o Minor bugfixes (log messages):
3102 - Fix a bug where clients using bridges would report themselves
3103 as 50% bootstrapped even without a live consensus document.
3104 Fixes bug 9922; bugfix on 0.2.1.1-alpha.
3105 - Suppress a warning where, if there's only one directory authority
3106 in the network, we would complain that votes and signatures cannot
3107 be uploaded to other directory authorities. Fixes bug 10842;
3108 bugfix on 0.2.2.26-beta.
3109 - Report bootstrapping progress correctly when we're downloading
3110 microdescriptors. We had updated our "do we have enough microdescs
3111 to begin building circuits?" logic most recently in 0.2.4.10-alpha
3112 (see bug 5956), but we left the bootstrap status event logic at
3113 "how far through getting 1/4 of them are we?" Fixes bug 9958;
3114 bugfix on 0.2.2.36, which is where they diverged (see bug 5343).
3116 o Minor bugfixes (new since 0.2.5.1-alpha, also in 0.2.4.20):
3117 - Avoid a crash bug when starting with a corrupted microdescriptor
3118 cache file. Fixes bug 10406; bugfix on 0.2.2.6-alpha.
3119 - If we fail to dump a previously cached microdescriptor to disk, avoid
3120 freeing duplicate data later on. Fixes bug 10423; bugfix on
3121 0.2.4.13-alpha. Spotted by "bobnomnom".
3123 o Minor bugfixes on 0.2.4.x (new since 0.2.5.1-alpha, also in 0.2.4.18-rc):
3124 - Correctly log long IPv6 exit policies, instead of truncating them
3125 or reporting an error. Fixes bug 9596; bugfix on 0.2.4.7-alpha.
3126 - Our default TLS ecdhe groups were backwards: we meant to be using
3127 P224 for relays (for performance win) and P256 for bridges (since
3128 it is more common in the wild). Instead we had it backwards. After
3129 reconsideration, we decided that the default should be P256 on all
3130 hosts, since its security is probably better, and since P224 is
3131 reportedly used quite little in the wild. Found by "skruffy" on
3132 IRC. Fix for bug 9780; bugfix on 0.2.4.8-alpha.
3133 - Free directory authority certificate download statuses on exit
3134 rather than leaking them. Fixes bug 9644; bugfix on 0.2.4.13-alpha.
3136 o Minor bugfixes on 0.2.3.x (new since 0.2.5.1-alpha, also in 0.2.4.18-rc):
3137 - If the guard we choose first doesn't answer, we would try the
3138 second guard, but once we connected to the second guard we would
3139 abandon it and retry the first one, slowing down bootstrapping.
3140 The fix is to treat all our initially chosen guards as acceptable
3141 to use. Fixes bug 9946; bugfix on 0.1.1.11-alpha.
3142 - Fix an assertion failure that would occur when disabling the
3143 ORPort setting on a running Tor process while accounting was
3144 enabled. Fixes bug 6979; bugfix on 0.2.2.18-alpha.
3145 - When examining the list of network interfaces to find our address,
3146 do not consider non-running or disabled network interfaces. Fixes
3147 bug 9904; bugfix on 0.2.3.11-alpha. Patch from "hantwister".
3148 - Avoid an off-by-one error when checking buffer boundaries when
3149 formatting the exit status of a pluggable transport helper.
3150 This is probably not an exploitable bug, but better safe than
3151 sorry. Fixes bug 9928; bugfix on 0.2.3.18-rc. Bug found by
3154 o Removed code and features:
3155 - Clients now reject any directory authority certificates lacking
3156 a dir-key-crosscert element. These have been included since
3157 0.2.1.9-alpha, so there's no real reason for them to be optional
3158 any longer. Completes proposal 157. Resolves ticket 10162.
3159 - Remove all code that existed to support the v2 directory system,
3160 since there are no longer any v2 directory authorities. Resolves
3162 - Remove the HSAuthoritativeDir and AlternateHSAuthority torrc
3163 options, which were used for designating authorities as "Hidden
3164 service authorities". There has been no use of hidden service
3165 authorities since 0.2.2.1-alpha, when we stopped uploading or
3166 downloading v0 hidden service descriptors. Fixes bug 10881; also
3167 part of a fix for bug 10841.
3169 o Code simplification and refactoring:
3170 - Remove some old fallback code designed to keep Tor clients working
3171 in a network with only two working relays. Elsewhere in the code we
3172 have long since stopped supporting such networks, so there wasn't
3173 much point in keeping it around. Addresses ticket 9926.
3174 - Reject 0-length EXTEND2 cells more explicitly. Fixes bug 10536;
3175 bugfix on 0.2.4.8-alpha. Reported by "cypherpunks".
3176 - Remove data structures which were introduced to implement the
3177 CellStatistics option: they are now redundant with the addition
3178 of a timestamp to the regular packed_cell_t data structure, which
3179 we did in 0.2.4.18-rc in order to resolve ticket 9093. Implements
3182 o Documentation (man page) fixes:
3183 - Update manpage to describe some of the files you can expect to
3184 find in Tor's DataDirectory. Addresses ticket 9839.
3185 - Document that all but one DirPort entry must have the NoAdvertise
3186 flag set. Fixes bug 10470; bugfix on 0.2.3.3-alpha / 0.2.3.16-alpha.
3188 o Documentation fixes (new since 0.2.5.1-alpha, also in 0.2.4.18-rc):
3189 - Clarify the usage and risks of setting the ContactInfo torrc line
3190 for your relay or bridge. Resolves ticket 9854.
3191 - Add anchors to the manpage so we can link to the html version of
3192 the documentation for specific options. Resolves ticket 9866.
3193 - Replace remaining references to DirServer in man page and
3194 log entries. Resolves ticket 10124.
3197 - Make the "tor-gencert" tool used by directory authority operators
3198 create 2048-bit signing keys by default (rather than 1024-bit, since
3199 1024-bit is uncomfortably small these days). Addresses ticket 10324.
3202 Changes in version 0.2.4.20 - 2013-12-22
3203 Tor 0.2.4.20 fixes potentially poor random number generation for users
3204 who 1) use OpenSSL 1.0.0 or later, 2) set "HardwareAccel 1" in their
3205 torrc file, 3) have "Sandy Bridge" or "Ivy Bridge" Intel processors,
3206 and 4) have no state file in their DataDirectory (as would happen on
3207 first start). Users who generated relay or hidden service identity
3208 keys in such a situation should discard them and generate new ones.
3210 This release also fixes a logic error that caused Tor clients to build
3211 many more preemptive circuits than they actually need.
3214 - Do not allow OpenSSL engines to replace the PRNG, even when
3215 HardwareAccel is set. The only default builtin PRNG engine uses
3216 the Intel RDRAND instruction to replace the entire PRNG, and
3217 ignores all attempts to seed it with more entropy. That's
3218 cryptographically stupid: the right response to a new alleged
3219 entropy source is never to discard all previously used entropy
3220 sources. Fixes bug 10402; works around behavior introduced in
3221 OpenSSL 1.0.0. Diagnosis and investigation thanks to "coderman"
3223 - Fix assertion failure when AutomapHostsOnResolve yields an IPv6
3224 address. Fixes bug 10465; bugfix on 0.2.4.7-alpha.
3225 - Avoid launching spurious extra circuits when a stream is pending.
3226 This fixes a bug where any circuit that _wasn't_ unusable for new
3227 streams would be treated as if it were, causing extra circuits to
3228 be launched. Fixes bug 10456; bugfix on 0.2.4.12-alpha.
3231 - Avoid a crash bug when starting with a corrupted microdescriptor
3232 cache file. Fixes bug 10406; bugfix on 0.2.2.6-alpha.
3233 - If we fail to dump a previously cached microdescriptor to disk, avoid
3234 freeing duplicate data later on. Fixes bug 10423; bugfix on
3235 0.2.4.13-alpha. Spotted by "bobnomnom".
3238 Changes in version 0.2.4.19 - 2013-12-11
3239 The Tor 0.2.4 release series is dedicated to the memory of Aaron Swartz
3240 (1986-2013). Aaron worked on diverse projects including helping to guide
3241 Creative Commons, playing a key role in stopping SOPA/PIPA, bringing
3242 transparency to the U.S government's PACER documents, and contributing
3243 design and development for Tor and Tor2Web. Aaron was one of the latest
3244 martyrs in our collective fight for civil liberties and human rights,
3245 and his death is all the more painful because he was one of us.
3247 Tor 0.2.4.19, the first stable release in the 0.2.4 branch, features
3248 a new circuit handshake and link encryption that use ECC to provide
3249 better security and efficiency; makes relays better manage circuit
3250 creation requests; uses "directory guards" to reduce client enumeration
3251 risks; makes bridges collect and report statistics about the pluggable
3252 transports they support; cleans up and improves our geoip database;
3253 gets much closer to IPv6 support for clients, bridges, and relays; makes
3254 directory authorities use measured bandwidths rather than advertised
3255 ones when computing flags and thresholds; disables client-side DNS
3256 caching to reduce tracking risks; and fixes a big bug in bridge
3257 reachability testing. This release introduces two new design
3258 abstractions in the code: a new "channel" abstraction between circuits
3259 and or_connections to allow for implementing alternate relay-to-relay
3260 transports, and a new "circuitmux" abstraction storing the queue of
3261 circuits for a channel. The release also includes many stability,
3262 security, and privacy fixes.
3265 Changes in version 0.2.4.18-rc - 2013-11-16
3266 Tor 0.2.4.18-rc is the fourth release candidate for the Tor 0.2.4.x
3267 series. It takes a variety of fixes from the 0.2.5.x branch to improve
3268 stability, performance, and better handling of edge cases.
3271 - Re-enable TLS 1.1 and 1.2 when built with OpenSSL 1.0.1e or later.
3272 Resolves ticket 6055. (OpenSSL before 1.0.1 didn't have TLS 1.1 or
3273 1.2, and OpenSSL from 1.0.1 through 1.0.1d had bugs that prevented
3274 renegotiation from working with TLS 1.1 or 1.2, so we had disabled
3275 them to solve bug 6033.)
3278 - No longer stop reading or writing on cpuworker connections when
3279 our rate limiting buckets go empty. Now we should handle circuit
3280 handshake requests more promptly. Resolves bug 9731.
3281 - If we are unable to save a microdescriptor to the journal, do not
3282 drop it from memory and then reattempt downloading it. Fixes bug
3283 9645; bugfix on 0.2.2.6-alpha.
3284 - Stop trying to bootstrap all our directory information from
3285 only our first guard. Discovered while fixing bug 9946; bugfix
3287 - The new channel code sometimes lost track of in-progress circuits,
3288 causing long-running clients to stop building new circuits. The
3289 fix is to always call circuit_n_chan_done(chan, 0) from
3290 channel_closed(). Fixes bug 9776; bugfix on 0.2.4.17-rc.
3292 o Minor bugfixes (on 0.2.4.x):
3293 - Correctly log long IPv6 exit policies, instead of truncating them
3294 or reporting an error. Fixes bug 9596; bugfix on 0.2.4.7-alpha.
3295 - Our default TLS ecdhe groups were backwards: we meant to be using
3296 P224 for relays (for performance win) and P256 for bridges (since
3297 it is more common in the wild). Instead we had it backwards. After
3298 reconsideration, we decided that the default should be P256 on all
3299 hosts, since its security is probably better, and since P224 is
3300 reportedly used quite little in the wild. Found by "skruffy" on
3301 IRC. Fix for bug 9780; bugfix on 0.2.4.8-alpha.
3302 - Free directory authority certificate download statuses on exit
3303 rather than leaking them. Fixes bug 9644; bugfix on 0.2.4.13-alpha.
3305 o Minor bugfixes (on 0.2.3.x and earlier):
3306 - If the guard we choose first doesn't answer, we would try the
3307 second guard, but once we connected to the second guard we would
3308 abandon it and retry the first one, slowing down bootstrapping.
3309 The fix is to treat all our initially chosen guards as acceptable
3310 to use. Fixes bug 9946; bugfix on 0.1.1.11-alpha.
3311 - Fix an assertion failure that would occur when disabling the
3312 ORPort setting on a running Tor process while accounting was
3313 enabled. Fixes bug 6979; bugfix on 0.2.2.18-alpha.
3314 - When examining the list of network interfaces to find our address,
3315 do not consider non-running or disabled network interfaces. Fixes
3316 bug 9904; bugfix on 0.2.3.11-alpha. Patch from "hantwister".
3317 - Avoid an off-by-one error when checking buffer boundaries when
3318 formatting the exit status of a pluggable transport helper.
3319 This is probably not an exploitable bug, but better safe than
3320 sorry. Fixes bug 9928; bugfix on 0.2.3.18-rc. Bug found by
3323 o Minor features (protecting client timestamps):
3324 - Clients no longer send timestamps in their NETINFO cells. These were
3325 not used for anything, and they provided one small way for clients
3326 to be distinguished from each other as they moved from network to
3327 network or behind NAT. Implements part of proposal 222.
3328 - Clients now round timestamps in INTRODUCE cells down to the nearest
3329 10 minutes. If a new Support022HiddenServices option is set to 0, or
3330 if it's set to "auto" and the feature is disabled in the consensus,
3331 the timestamp is sent as 0 instead. Implements part of proposal 222.
3332 - Stop sending timestamps in AUTHENTICATE cells. This is not such
3333 a big deal from a security point of view, but it achieves no actual
3334 good purpose, and isn't needed. Implements part of proposal 222.
3335 - Reduce down accuracy of timestamps in hidden service descriptors.
3336 Implements part of proposal 222.
3338 o Minor features (other):
3339 - Improve the circuit queue out-of-memory handler. Previously, when
3340 we ran low on memory, we'd close whichever circuits had the most
3341 queued cells. Now, we close those that have the *oldest* queued
3342 cells, on the theory that those are most responsible for us
3343 running low on memory. Based on analysis from a forthcoming paper
3344 by Jansen, Tschorsch, Johnson, and Scheuermann. Fixes bug 9093.
3345 - Generate bootstrapping status update events correctly when fetching
3346 microdescriptors. Fixes bug 9927.
3347 - Update to the October 2 2013 Maxmind GeoLite Country database.
3349 o Documentation fixes:
3350 - Clarify the usage and risks of setting the ContactInfo torrc line
3351 for your relay or bridge. Resolves ticket 9854.
3352 - Add anchors to the manpage so we can link to the html version of
3353 the documentation for specific options. Resolves ticket 9866.
3354 - Replace remaining references to DirServer in man page and
3355 log entries. Resolves ticket 10124.
3358 Changes in version 0.2.5.1-alpha - 2013-10-02
3359 Tor 0.2.5.1-alpha introduces experimental support for syscall sandboxing
3360 on Linux, allows bridges that offer pluggable transports to report usage
3361 statistics, fixes many issues to make testing easier, and provides
3362 a pile of minor features and bugfixes that have been waiting for a
3363 release of the new branch.
3365 This is the first alpha release in a new series, so expect there to
3366 be bugs. Users who would rather test out a more stable branch should
3367 stay with 0.2.4.x for now.
3369 o Major features (security):
3370 - Use the seccomp2 syscall filtering facility on Linux to limit
3371 which system calls Tor can invoke. This is an experimental,
3372 Linux-only feature to provide defense-in-depth against unknown
3373 attacks. To try turning it on, set "Sandbox 1" in your torrc
3374 file. Please be ready to report bugs. We hope to add support
3375 for better sandboxing in the future, including more fine-grained
3376 filters, better division of responsibility, and support for more
3377 platforms. This work has been done by Cristian-Matei Toader for
3378 Google Summer of Code.
3379 - Re-enable TLS 1.1 and 1.2 when built with OpenSSL 1.0.1e or later.
3380 Resolves ticket 6055. (OpenSSL before 1.0.1 didn't have TLS 1.1 or
3381 1.2, and OpenSSL from 1.0.1 through 1.0.1d had bugs that prevented
3382 renegotiation from working with TLS 1.1 or 1.2, so we had disabled
3383 them to solve bug 6033.)
3385 o Major features (other):
3386 - Add support for passing arguments to managed pluggable transport
3387 proxies. Implements ticket 3594.
3388 - Bridges now track GeoIP information and the number of their users
3389 even when pluggable transports are in use, and report usage
3390 statistics in their extra-info descriptors. Resolves tickets 4773
3392 - Make testing Tor networks bootstrap better: lower directory fetch
3393 retry schedules and maximum interval without directory requests,
3394 and raise maximum download tries. Implements ticket 6752.
3395 - Add make target 'test-network' to run tests on a Chutney network.
3396 Implements ticket 8530.
3397 - The ntor handshake is now on-by-default, no matter what the
3398 directory authorities recommend. Implements ticket 8561.
3401 - Instead of writing destroy cells directly to outgoing connection
3402 buffers, queue them and intersperse them with other outgoing cells.
3403 This can prevent a set of resource starvation conditions where too
3404 many pending destroy cells prevent data cells from actually getting
3405 delivered. Reported by "oftc_must_be_destroyed". Fixes bug 7912;
3406 bugfix on 0.2.0.1-alpha.
3407 - If we are unable to save a microdescriptor to the journal, do not
3408 drop it from memory and then reattempt downloading it. Fixes bug
3409 9645; bugfix on 0.2.2.6-alpha.
3410 - The new channel code sometimes lost track of in-progress circuits,
3411 causing long-running clients to stop building new circuits. The
3412 fix is to always call circuit_n_chan_done(chan, 0) from
3413 channel_closed(). Fixes bug 9776; bugfix on 0.2.4.17-rc.
3416 - Tor now builds each source file in two modes: a mode that avoids
3417 exposing identifiers needlessly, and another mode that exposes
3418 more identifiers for testing. This lets the compiler do better at
3419 optimizing the production code, while enabling us to take more
3420 radical measures to let the unit tests test things.
3421 - The production builds no longer include functions used only in
3422 the unit tests; all functions exposed from a module only for
3423 unit-testing are now static in production builds.
3424 - Add an --enable-coverage configuration option to make the unit
3425 tests (and a new src/or/tor-cov target) to build with gcov test
3429 - We now have rudimentary function mocking support that our unit
3430 tests can use to test functions in isolation. Function mocking
3431 lets the tests temporarily replace a function's dependencies with
3432 stub functions, so that the tests can check the function without
3433 invoking the other functions it calls.
3434 - Add more unit tests for the <circid,channel>->circuit map, and
3435 the destroy-cell-tracking code to fix bug 7912.
3436 - Unit tests for failing cases of the TAP onion handshake.
3437 - More unit tests for address-manipulation functions.
3439 o Minor features (protecting client timestamps):
3440 - Clients no longer send timestamps in their NETINFO cells. These were
3441 not used for anything, and they provided one small way for clients
3442 to be distinguished from each other as they moved from network to
3443 network or behind NAT. Implements part of proposal 222.
3444 - Clients now round timestamps in INTRODUCE cells down to the nearest
3445 10 minutes. If a new Support022HiddenServices option is set to 0, or
3446 if it's set to "auto" and the feature is disabled in the consensus,
3447 the timestamp is sent as 0 instead. Implements part of proposal 222.
3448 - Stop sending timestamps in AUTHENTICATE cells. This is not such
3449 a big deal from a security point of view, but it achieves no actual
3450 good purpose, and isn't needed. Implements part of proposal 222.
3451 - Reduce down accuracy of timestamps in hidden service descriptors.
3452 Implements part of proposal 222.
3454 o Minor features (config options):
3455 - Config (torrc) lines now handle fingerprints which are missing
3456 their initial '$'. Resolves ticket 4341; improvement over 0.0.9pre5.
3457 - Support a --dump-config option to print some or all of the
3458 configured options. Mainly useful for debugging the command-line
3459 option parsing code. Helps resolve ticket 4647.
3460 - Raise awareness of safer logging: notify user of potentially
3461 unsafe config options, like logging more verbosely than severity
3462 "notice" or setting SafeLogging to 0. Resolves ticket 5584.
3463 - Add a new configuration option TestingV3AuthVotingStartOffset
3464 that bootstraps a network faster by changing the timing for
3465 consensus votes. Addresses ticket 8532.
3466 - Add a new torrc option "ServerTransportOptions" that allows
3467 bridge operators to pass configuration parameters to their
3468 pluggable transports. Resolves ticket 8929.
3469 - The config (torrc) file now accepts bandwidth and space limits in
3470 bits as well as bytes. (Anywhere that you can say "2 Kilobytes",
3471 you can now say "16 kilobits", and so on.) Resolves ticket 9214.
3474 o Minor features (build):
3475 - Add support for `--library-versions` flag. Implements ticket 6384.
3476 - Return the "unexpected sendme" warnings to a warn severity, but make
3477 them rate limited, to help diagnose ticket 8093.
3478 - Detect a missing asciidoc, and warn the user about it, during
3479 configure rather than at build time. Fixes issue 6506. Patch from
3482 o Minor features (other):
3483 - Use the SOCK_NONBLOCK socket type, if supported, to open nonblocking
3484 sockets in a single system call. Implements ticket 5129.
3485 - Log current accounting state (bytes sent and received + remaining
3486 time for the current accounting period) in the relay's heartbeat
3487 message. Implements ticket 5526; patch from Peter Retzlaff.
3488 - Implement the TRANSPORT_LAUNCHED control port event that
3489 notifies controllers about new launched pluggable
3490 transports. Resolves ticket 5609.
3491 - If we're using the pure-C 32-bit curve25519_donna implementation
3492 of curve25519, build it with the -fomit-frame-pointer option to
3493 make it go faster on register-starved hosts. This improves our
3494 handshake performance by about 6% on i386 hosts without nacl.
3496 - Update to the September 4 2013 Maxmind GeoLite Country database.
3499 - Set the listen() backlog limit to the largest actually supported
3500 on the system, not to the value in a header file. Fixes bug 9716;
3501 bugfix on every released Tor.
3502 - No longer accept malformed http headers when parsing urls from
3503 headers. Now we reply with Bad Request ("400"). Fixes bug 2767;
3504 bugfix on 0.0.6pre1.
3505 - In munge_extrainfo_into_routerinfo(), check the return value of
3506 memchr(). This would have been a serious issue if we ever passed
3507 it a non-extrainfo. Fixes bug 8791; bugfix on 0.2.0.6-alpha. Patch
3509 - On the chance that somebody manages to build Tor on a
3510 platform where time_t is unsigned, correct the way that
3511 microdesc_add_to_cache() handles negative time arguments.
3512 Fixes bug 8042; bugfix on 0.2.3.1-alpha.
3513 - Reject relative control socket paths and emit a warning. Previously,
3514 single-component control socket paths would be rejected, but Tor
3515 would not log why it could not validate the config. Fixes bug 9258;
3516 bugfix on 0.2.3.16-alpha.
3518 o Minor bugfixes (command line):
3519 - Use a single command-line parser for parsing torrc options on the
3520 command line and for finding special command-line options to avoid
3521 inconsistent behavior for torrc option arguments that have the same
3522 names as command-line options. Fixes bugs 4647 and 9578; bugfix on
3524 - No longer allow 'tor --hash-password' with no arguments. Fixes bug
3525 9573; bugfix on 0.0.9pre5.
3527 o Minor fixes (build, auxiliary programs):
3528 - Stop preprocessing the "torify" script with autoconf, since
3529 it no longer refers to LOCALSTATEDIR. Fixes bug 5505; patch
3531 - The tor-fw-helper program now follows the standard convention and
3532 exits with status code "0" on success. Fixes bug 9030; bugfix on
3533 0.2.3.1-alpha. Patch by Arlo Breault.
3534 - Corrected ./configure advice for what openssl dev package you should
3535 install on Debian. Fixes bug 9207; bugfix on 0.2.0.1-alpha.
3537 o Minor code improvements:
3538 - Remove constants and tests for PKCS1 padding; it's insecure and
3539 shouldn't be used for anything new. Fixes bug 8792; patch
3541 - Remove instances of strcpy() from the unit tests. They weren't
3542 hurting anything, since they were only in the unit tests, but it's
3543 embarassing to have strcpy() in the code at all, and some analysis
3544 tools don't like it. Fixes bug 8790; bugfix on 0.2.3.6-alpha and
3545 0.2.3.8-alpha. Patch from Arlo Breault.
3548 - Remove migration code from when we renamed the "cached-routers"
3549 file to "cached-descriptors" back in 0.2.0.8-alpha. This
3550 incidentally resolves ticket 6502 by cleaning up the related code
3551 a bit. Patch from Akshay Hebbar.
3553 o Code simplification and refactoring:
3554 - Extract the common duplicated code for creating a subdirectory
3555 of the data directory and writing to a file in it. Fixes ticket
3556 4282; patch from Peter Retzlaff.
3557 - Since OpenSSL 0.9.7, the i2d_*() functions support allocating output
3558 buffer. Avoid calling twice: i2d_RSAPublicKey(), i2d_DHparams(),
3559 i2d_X509(), and i2d_PublicKey(). Resolves ticket 5170.
3560 - Add a set of accessor functions for the circuit timeout data
3561 structure. Fixes ticket 6153; patch from "piet".
3562 - Clean up exit paths from connection_listener_new(). Closes ticket
3563 8789. Patch from Arlo Breault.
3564 - Since we rely on OpenSSL 0.9.8 now, we can use EVP_PKEY_cmp()
3565 and drop our own custom pkey_eq() implementation. Fixes bug 9043.
3566 - Use a doubly-linked list to implement the global circuit list.
3567 Resolves ticket 9108. Patch from Marek Majkowski.
3568 - Remove contrib/id_to_fp.c since it wasn't used anywhere.
3571 Changes in version 0.2.4.17-rc - 2013-09-05
3572 Tor 0.2.4.17-rc is the third release candidate for the Tor 0.2.4.x
3573 series. It adds an emergency step to help us tolerate the massive
3574 influx of users: 0.2.4 clients using the new (faster and safer) "NTor"
3575 circuit-level handshakes now effectively jump the queue compared to
3576 the 0.2.3 clients using "TAP" handshakes. This release also fixes a
3577 big bug hindering bridge reachability tests.
3580 - Relays now process the new "NTor" circuit-level handshake requests
3581 with higher priority than the old "TAP" circuit-level handshake
3582 requests. We still process some TAP requests to not totally starve
3583 0.2.3 clients when NTor becomes popular. A new consensus parameter
3584 "NumNTorsPerTAP" lets us tune the balance later if we need to.
3585 Implements ticket 9574.
3588 - If the circuit build timeout logic is disabled (via the consensus,
3589 or because we are an authority), then don't build testing circuits.
3590 Fixes bug 9657; bugfix on 0.2.2.14-alpha.
3591 - Bridges now send AUTH_CHALLENGE cells during their v3 handshakes;
3592 previously they did not, which prevented them from receiving
3593 successful connections from relays for self-test or bandwidth
3594 testing. Also, when a relay is extending a circuit to a bridge,
3595 it needs to send a NETINFO cell, even when the bridge hasn't sent
3596 an AUTH_CHALLENGE cell. Fixes bug 9546; bugfix on 0.2.3.6-alpha.
3597 - If the time to download the next old-style networkstatus is in
3598 the future, do not decline to consider whether to download the
3599 next microdescriptor networkstatus. Fixes bug 9564; bugfix on
3603 - Avoid double-closing the listener socket in our socketpair()
3604 replacement (used on Windows) in the case where the addresses on
3605 our opened sockets don't match what we expected. Fixes bug 9400;
3606 bugfix on 0.0.2pre7. Found by Coverity.
3608 o Minor fixes (config options):
3609 - Avoid overflows when the user sets MaxCircuitDirtiness to a
3610 ridiculously high value, by imposing a (ridiculously high) 30-day
3611 maximum on MaxCircuitDirtiness.
3612 - Fix the documentation of HeartbeatPeriod to say that the heartbeat
3613 message is logged at notice, not at info.
3614 - Warn and fail if a server is configured not to advertise any
3615 ORPorts at all. (We need *something* to put in our descriptor,
3616 or we just won't work.)
3619 - Track how many "TAP" and "NTor" circuit handshake requests we get,
3620 and how many we complete, and log it every hour to help relay
3621 operators follow trends in network load. Addresses ticket 9658.
3622 - Update to the August 7 2013 Maxmind GeoLite Country database.
3625 Changes in version 0.2.4.16-rc - 2013-08-10
3626 Tor 0.2.4.16-rc is the second release candidate for the Tor 0.2.4.x
3627 series. It fixes several crash bugs in the 0.2.4 branch.
3630 - Fix a bug in the voting algorithm that could yield incorrect results
3631 when a non-naming authority declared too many flags. Fixes bug 9200;
3632 bugfix on 0.2.0.3-alpha.
3633 - Fix an uninitialized read that could in some cases lead to a remote
3634 crash while parsing INTRODUCE2 cells. Bugfix on 0.2.4.1-alpha.
3635 Anybody running a hidden service on the experimental 0.2.4.x
3636 branch should upgrade. (This is, so far as we know, unrelated to
3638 - Avoid an assertion failure when processing DNS replies without the
3639 answer types we expected. Fixes bug 9337; bugfix on 0.2.4.7-alpha.
3640 - Avoid a crash when using --hash-password. Fixes bug 9295; bugfix on
3641 0.2.4.15-rc. Found by stem integration tests.
3644 - Fix an invalid memory read that occured when a pluggable
3645 transport proxy failed its configuration protocol.
3646 Fixes bug 9288; bugfix on 0.2.4.1-alpha.
3647 - When evaluating whether to use a connection that we haven't
3648 decided is canonical using a recent link protocol version,
3649 decide that it's canonical only if it used address _does_
3650 match the desired address. Fixes bug 9309; bugfix on
3651 0.2.4.4-alpha. Reported by skruffy.
3652 - Make the default behavior of NumDirectoryGuards be to track
3653 NumEntryGuards. Now a user who changes only NumEntryGuards will get
3654 the behavior she expects. Fixes bug 9354; bugfix on 0.2.4.8-alpha.
3655 - Fix a spurious compilation warning with some older versions of
3656 GCC on FreeBSD. Fixes bug 9254; bugfix on 0.2.4.14-alpha.
3659 - Update to the July 3 2013 Maxmind GeoLite Country database.
3662 Changes in version 0.2.4.15-rc - 2013-07-01
3663 Tor 0.2.4.15-rc is the first release candidate for the Tor 0.2.4.x
3664 series. It fixes a few smaller bugs, but generally appears stable.
3665 Please test it and let us know whether it is!
3668 - When receiving a new configuration file via the control port's
3669 LOADCONF command, do not treat the defaults file as absent.
3670 Fixes bug 9122; bugfix on 0.2.3.9-alpha.
3673 - Issue a warning when running with the bufferevents backend enabled.
3674 It's still not stable, and people should know that they're likely
3675 to hit unexpected problems. Closes ticket 9147.
3678 Changes in version 0.2.4.14-alpha - 2013-06-18
3679 Tor 0.2.4.14-alpha fixes a pair of client guard enumeration problems
3680 present in 0.2.4.13-alpha.
3683 - When we have too much memory queued in circuits (according to a new
3684 MaxMemInCellQueues option), close the circuits consuming the most
3685 memory. This prevents us from running out of memory as a relay if
3686 circuits fill up faster than they can be drained. Fixes bug 9063;
3687 bugfix on the 54th commit of Tor. This bug is a further fix beyond
3688 bug 6252, whose fix was merged into 0.2.3.21-rc.
3690 This change also fixes an earlier approach taken in 0.2.4.13-alpha,
3691 where we tried to solve this issue simply by imposing an upper limit
3692 on the number of queued cells for a single circuit. That approach
3693 proved to be problematic, since there are ways to provoke clients to
3694 send a number of cells in excess of any such reasonable limit. Fixes
3695 bug 9072; bugfix on 0.2.4.13-alpha.
3697 - Limit hidden service descriptors to at most ten introduction
3698 points, to slow one kind of guard enumeration. Fixes bug 9002;
3699 bugfix on 0.1.1.11-alpha.
3702 Changes in version 0.2.4.13-alpha - 2013-06-14
3703 Tor 0.2.4.13-alpha fixes a variety of potential remote crash
3704 vulnerabilities, makes socks5 username/password circuit isolation
3705 actually actually work (this time for sure!), and cleans up a bunch
3706 of other issues in preparation for a release candidate.
3708 o Major bugfixes (robustness):
3709 - Close any circuit that has too many cells queued on it. Fixes
3710 bug 9063; bugfix on the 54th commit of Tor. This bug is a further
3711 fix beyond bug 6252, whose fix was merged into 0.2.3.21-rc.
3712 - Prevent the get_freelists() function from running off the end of
3713 the list of freelists if it somehow gets an unrecognized
3714 allocation. Fixes bug 8844; bugfix on 0.2.0.16-alpha. Reported by
3716 - Avoid an assertion failure on OpenBSD (and perhaps other BSDs)
3717 when an exit connection with optimistic data succeeds immediately
3718 rather than returning EINPROGRESS. Fixes bug 9017; bugfix on
3720 - Fix a directory authority crash bug when building a consensus
3721 using an older consensus as its basis. Fixes bug 8833. Bugfix
3725 - Avoid a memory leak where we would leak a consensus body when we
3726 find that a consensus which we couldn't previously verify due to
3727 missing certificates is now verifiable. Fixes bug 8719; bugfix
3729 - We used to always request authority certificates by identity digest,
3730 meaning we'd get the newest one even when we wanted one with a
3731 different signing key. Then we would complain about being given
3732 a certificate we already had, and never get the one we really
3733 wanted. Now we use the "fp-sk/" resource as well as the "fp/"
3734 resource to request the one we want. Fixes bug 5595; bugfix on
3736 - Follow the socks5 protocol when offering username/password
3737 authentication. The fix for bug 8117 exposed this bug, and it
3738 turns out real-world applications like Pidgin do care. Bugfix on
3739 0.2.3.2-alpha; fixes bug 8879.
3740 - Prevent failures on Windows Vista and later when rebuilding the
3741 microdescriptor cache. Diagnosed by Robert Ransom. Fixes bug 8822;
3742 bugfix on 0.2.4.12-alpha.
3745 - Fix an impossible buffer overrun in the AES unit tests. Fixes
3746 bug 8845; bugfix on 0.2.0.7-alpha. Found by eugenis.
3747 - If for some reason we fail to write a microdescriptor while
3748 rebuilding the cache, do not let the annotations from that
3749 microdescriptor linger in the cache file, and do not let the
3750 microdescriptor stay recorded as present in its old location.
3751 Fixes bug 9047; bugfix on 0.2.2.6-alpha.
3752 - Fix a memory leak that would occur whenever a configuration
3753 option changed. Fixes bug 8718; bugfix on 0.2.3.3-alpha.
3754 - Paste the description for PathBias parameters from the man
3755 page into or.h, so the code documents them too. Fixes bug 7982;
3756 bugfix on 0.2.3.17-beta and 0.2.4.8-alpha.
3757 - Relays now treat a changed IPv6 ORPort as sufficient reason to
3758 publish an updated descriptor. Fixes bug 6026; bugfix on
3760 - When launching a resolve request on behalf of an AF_UNIX control
3761 socket, omit the address field of the new entry connection, used in
3762 subsequent controller events, rather than letting tor_dup_addr()
3763 set it to "<unknown address type>". Fixes bug 8639; bugfix on
3766 o Minor bugfixes (log messages):
3767 - Fix a scaling issue in the path bias accounting code that
3768 resulted in "Bug:" log messages from either
3769 pathbias_scale_close_rates() or pathbias_count_build_success().
3770 This represents a bugfix on a previous bugfix: the original fix
3771 attempted in 0.2.4.10-alpha was incomplete. Fixes bug 8235; bugfix
3773 - Give a less useless error message when the user asks for an IPv4
3774 address on an IPv6-only port, or vice versa. Fixes bug 8846; bugfix
3778 - Downgrade "unexpected SENDME" warnings to protocol-warn for 0.2.4.x,
3779 to tolerate bug 8093 for now.
3780 - Add an "ignoring-advertised-bws" boolean to the flag-threshold lines
3781 in directory authority votes to describe whether they have enough
3782 measured bandwidths to ignore advertised (relay descriptor)
3783 bandwidth claims. Resolves ticket 8711.
3784 - Update to the June 5 2013 Maxmind GeoLite Country database.
3786 o Removed documentation:
3787 - Remove some of the older contents of doc/ as obsolete; move others
3788 to torspec.git. Fixes bug 8965.
3790 o Code simplification and refactoring:
3791 - Avoid using character buffers when constructing most directory
3792 objects: this approach was unwieldy and error-prone. Instead,
3793 build smartlists of strings, and concatenate them when done.
3796 Changes in version 0.2.4.12-alpha - 2013-04-18
3797 Tor 0.2.4.12-alpha moves Tor forward on several fronts: it starts the
3798 process for lengthening the guard rotation period, makes directory
3799 authority opinions in the consensus a bit less gameable, makes socks5
3800 username/password circuit isolation actually work, and fixes a wide
3801 variety of other issues.
3804 - Raise the default time that a client keeps an entry guard from
3805 "1-2 months" to "2-3 months", as suggested by Tariq Elahi's WPES
3806 2012 paper. (We would make it even longer, but we need better client
3807 load balancing first.) Also, make the guard lifetime controllable
3808 via a new GuardLifetime torrc option and a GuardLifetime consensus
3809 parameter. Start of a fix for bug 8240; bugfix on 0.1.1.11-alpha.
3810 - Directory authorities now prefer using measured bandwidths to
3811 advertised ones when computing flags and thresholds. Resolves
3813 - Directory authorities that have more than a threshold number
3814 of relays with measured bandwidths now treat relays with unmeasured
3815 bandwidths as having bandwidth 0. Resolves ticket 8435.
3817 o Major bugfixes (assert / resource use):
3818 - Avoid a bug where our response to TLS renegotiation under certain
3819 network conditions could lead to a busy-loop, with 100% CPU
3820 consumption. Fixes bug 5650; bugfix on 0.2.0.16-alpha.
3821 - Avoid an assertion when we discover that we'd like to write a cell
3822 onto a closing connection: just discard the cell. Fixes another
3823 case of bug 7350; bugfix on 0.2.4.4-alpha.
3825 o Major bugfixes (client-side privacy):
3826 - When we mark a circuit as unusable for new circuits, have it
3827 continue to be unusable for new circuits even if MaxCircuitDirtiness
3828 is increased too much at the wrong time, or the system clock jumps
3829 backwards. Fixes bug 6174; bugfix on 0.0.2pre26.
3830 - If ClientDNSRejectInternalAddresses ("do not believe DNS queries
3831 which have resolved to internal addresses") is set, apply that
3832 rule to IPv6 as well. Fixes bug 8475; bugfix on 0.2.0.7-alpha.
3833 - When an exit relay rejects a stream with reason "exit policy", but
3834 we only know an exit policy summary (e.g. from the microdesc
3835 consensus) for it, do not mark the relay as useless for all exiting.
3836 Instead, mark just the circuit as unsuitable for that particular
3837 address. Fixes part of bug 7582; bugfix on 0.2.3.2-alpha.
3838 - Allow applications to get proper stream isolation with
3839 IsolateSOCKSAuth. Many SOCKS5 clients that want to offer
3840 username/password authentication also offer "no authentication". Tor
3841 had previously preferred "no authentication", so the applications
3842 never actually sent Tor their auth details. Now Tor selects
3843 username/password authentication if it's offered. You can disable
3844 this behavior on a per-SOCKSPort basis via PreferSOCKSNoAuth. Fixes
3845 bug 8117; bugfix on 0.2.3.3-alpha.
3847 o Major bugfixes (other):
3848 - When unable to find any working directory nodes to use as a
3849 directory guard, give up rather than adding the same non-working
3850 nodes to the directory guard list over and over. Fixes bug 8231;
3851 bugfix on 0.2.4.8-alpha.
3854 - Reject as invalid most directory objects containing a NUL.
3855 Belt-and-suspender fix for bug 8037.
3856 - In our testsuite, create temporary directories with a bit more
3857 entropy in their name to make name collisions less likely. Fixes
3859 - Add CACHED keyword to ADDRMAP events in the control protocol
3860 to indicate whether a DNS result will be cached or not. Resolves
3862 - Update to the April 3 2013 Maxmind GeoLite Country database.
3864 o Minor features (build):
3865 - Detect and reject attempts to build Tor with threading support
3866 when OpenSSL has been compiled without threading support.
3868 - Clarify that when autoconf is checking for nacl, it is checking
3869 specifically for nacl with a fast curve25519 implementation.
3871 - Warn if building on a platform with an unsigned time_t: there
3872 are too many places where Tor currently assumes that time_t can
3873 hold negative values. We'd like to fix them all, but probably
3876 o Minor bugfixes (build):
3877 - Fix some bugs in tor-fw-helper-natpmp when trying to build and
3878 run it on Windows. More bugs likely remain. Patch from Gisle Vanem.
3879 Fixes bug 7280; bugfix on 0.2.3.1-alpha.
3880 - Add the old src/or/micro-revision.i filename to CLEANFILES.
3881 On the off chance that somebody has one, it will go away as soon
3882 as they run "make clean". Fix for bug 7143; bugfix on 0.2.4.1-alpha.
3883 - Build Tor correctly on 32-bit platforms where the compiler can build
3884 but not run code using the "uint128_t" construction. Fixes bug 8587;
3885 bugfix on 0.2.4.8-alpha.
3886 - Fix compilation warning with some versions of clang that would
3887 prefer the -Wswitch-enum compiler flag to warn about switch
3888 statements with missing enum values, even if those switch
3889 statements have a "default:" statement. Fixes bug 8598; bugfix
3892 o Minor bugfixes (protocol):
3893 - Fix the handling of a TRUNCATE cell when it arrives while the
3894 circuit extension is in progress. Fixes bug 7947; bugfix on 0.0.7.1.
3895 - Fix a misframing issue when reading the version numbers in a
3896 VERSIONS cell. Previously we would recognize [00 01 00 02] as
3897 'version 1, version 2, and version 0x100', when it should have
3898 only included versions 1 and 2. Fixes bug 8059; bugfix on
3899 0.2.0.10-alpha. Reported pseudonymously.
3900 - Make the format and order of STREAM events for DNS lookups
3901 consistent among the various ways to launch DNS lookups. Fixes
3902 bug 8203; bugfix on 0.2.0.24-rc. Patch by "Desoxy."
3903 - Correct our check for which versions of Tor support the EXTEND2
3904 cell. We had been willing to send it to Tor 0.2.4.7-alpha and
3905 later, when support was really added in version 0.2.4.8-alpha.
3906 Fixes bug 8464; bugfix on 0.2.4.8-alpha.
3908 o Minor bugfixes (other):
3909 - Correctly store microdescriptors and extrainfo descriptors with
3910 an internal NUL byte. Fixes bug 8037; bugfix on 0.2.0.1-alpha.
3911 Bug reported by "cypherpunks".
3912 - Increase the width of the field used to remember a connection's
3913 link protocol version to two bytes. Harmless for now, since the
3914 only currently recognized versions are one byte long. Reported
3915 pseudonymously. Fixes bug 8062; bugfix on 0.2.0.10-alpha.
3916 - If the state file's path bias counts are invalid (presumably from a
3917 buggy Tor prior to 0.2.4.10-alpha), make them correct. Also add
3918 additional checks and log messages to the scaling of Path Bias
3919 counts, in case there still are remaining issues with scaling.
3920 Should help resolve bug 8235.
3921 - Eliminate several instances where we use "Nickname=ID" to refer to
3922 nodes in logs. Use "Nickname (ID)" instead. (Elsewhere, we still use
3923 "$ID=Nickname", which is also acceptable.) Fixes bug 7065. Bugfix
3924 on 0.2.3.21-rc, 0.2.4.5-alpha, 0.2.4.8-alpha, and 0.2.4.10-alpha.
3926 o Minor bugfixes (syscalls):
3927 - Always check the return values of functions fcntl() and
3928 setsockopt(). We don't believe these are ever actually failing in
3929 practice, but better safe than sorry. Also, checking these return
3930 values should please analysis tools like Coverity. Patch from
3931 'flupzor'. Fixes bug 8206; bugfix on all versions of Tor.
3932 - Use direct writes rather than stdio when building microdescriptor
3933 caches, in an attempt to mitigate bug 8031, or at least make it
3936 o Minor bugfixes (config):
3937 - When rejecting a configuration because we were unable to parse a
3938 quoted string, log an actual error message. Fixes bug 7950; bugfix
3940 - Behave correctly when the user disables LearnCircuitBuildTimeout
3941 but doesn't tell us what they would like the timeout to be. Fixes
3942 bug 6304; bugfix on 0.2.2.14-alpha.
3943 - When autodetecting the number of CPUs, use the number of available
3944 CPUs in preference to the number of configured CPUs. Inform the
3945 user if this reduces the number of available CPUs. Fixes bug 8002;
3946 bugfix on 0.2.3.1-alpha.
3947 - Make it an error when you set EntryNodes but disable UseGuardNodes,
3948 since it will (surprisingly to some users) ignore EntryNodes. Fixes
3949 bug 8180; bugfix on 0.2.3.11-alpha.
3950 - Allow TestingTorNetworks to override the 4096-byte minimum for
3951 the Fast threshold. Otherwise they can't bootstrap until they've
3952 observed more traffic. Fixes bug 8508; bugfix on 0.2.4.10-alpha.
3953 - Fix some logic errors when the user manually overrides the
3954 PathsNeededToBuildCircuits option in torrc. Fixes bug 8599; bugfix
3957 o Minor bugfixes (log messages to help diagnose bugs):
3958 - If we fail to free a microdescriptor because of bug 7164, log
3959 the filename and line number from which we tried to free it.
3960 - Add another diagnostic to the heartbeat message: track and log
3961 overhead that TLS is adding to the data we write. If this is
3962 high, we are sending too little data to SSL_write at a time.
3963 Diagnostic for bug 7707.
3964 - Add more detail to a log message about relaxed timeouts, to help
3966 - Warn more aggressively when flushing microdescriptors to a
3967 microdescriptor cache fails, in an attempt to mitigate bug 8031,
3968 or at least make it more diagnosable.
3969 - Improve debugging output to help track down bug 8185 ("Bug:
3970 outgoing relay cell has n_chan==NULL. Dropping.")
3971 - Log the purpose of a path-bias testing circuit correctly.
3972 Improves a log message from bug 8477; bugfix on 0.2.4.8-alpha.
3974 o Minor bugfixes (0.2.4.x log messages that were too noisy):
3975 - Don't attempt to relax the timeout of already opened 1-hop circuits.
3976 They might never timeout. This should eliminate some/all cases of
3977 the relaxed timeout log message.
3978 - Use circuit creation time for network liveness evaluation. This
3979 should eliminate warning log messages about liveness caused
3980 by changes in timeout evaluation. Fixes bug 6572; bugfix on
3982 - Reduce a path bias length check from notice to info. The message
3983 is triggered when creating controller circuits. Fixes bug 8196;
3984 bugfix on 0.2.4.8-alpha.
3985 - Fix a path state issue that triggered a notice during relay startup.
3986 Fixes bug 8320; bugfix on 0.2.4.10-alpha.
3987 - Reduce occurrences of warns about circuit purpose in
3988 connection_ap_expire_building(). Fixes bug 8477; bugfix on
3991 o Minor bugfixes (pre-0.2.4.x log messages that were too noisy):
3992 - If we encounter a write failure on a SOCKS connection before we
3993 finish our SOCKS handshake, don't warn that we closed the
3994 connection before we could send a SOCKS reply. Fixes bug 8427;
3995 bugfix on 0.1.0.1-rc.
3996 - Correctly recognize that [::1] is a loopback address. Fixes
3997 bug 8377; bugfix on 0.2.1.3-alpha.
3998 - Fix a directory authority warn caused when we have a large amount
3999 of badexit bandwidth. Fixes bug 8419; bugfix on 0.2.2.10-alpha.
4000 - Don't log inappropriate heartbeat messages when hibernating: a
4001 hibernating node is _expected_ to drop out of the consensus,
4002 decide it isn't bootstrapped, and so forth. Fixes bug 7302;
4003 bugfix on 0.2.3.1-alpha.
4004 - Don't complain about bootstrapping problems while hibernating.
4005 These complaints reflect a general code problem, but not one
4006 with any problematic effects (no connections are actually
4007 opened). Fixes part of bug 7302; bugfix on 0.2.3.2-alpha.
4009 o Documentation fixes:
4010 - Update tor-fw-helper.1.txt and tor-fw-helper.c to make option
4011 names match. Fixes bug 7768.
4012 - Make the torify manpage no longer refer to tsocks; torify hasn't
4013 supported tsocks since 0.2.3.14-alpha.
4014 - Make the tor manpage no longer reference tsocks.
4015 - Fix the GeoIPExcludeUnknown documentation to refer to
4016 ExcludeExitNodes rather than the currently nonexistent
4017 ExcludeEntryNodes. Spotted by "hamahangi" on tor-talk.
4020 - The tor-tsocks.conf is no longer distributed or installed. We
4021 recommend that tsocks users use torsocks instead. Resolves
4025 Changes in version 0.2.4.11-alpha - 2013-03-11
4026 Tor 0.2.4.11-alpha makes relay measurement by directory authorities
4027 more robust, makes hidden service authentication work again, and
4028 resolves a DPI fingerprint for Tor's SSL transport.
4030 o Major features (directory authorities):
4031 - Directory authorities now support a new consensus method (17)
4032 where they cap the published bandwidth of servers for which
4033 insufficient bandwidth measurements exist. Fixes part of bug 2286.
4034 - Directory authorities that set "DisableV2DirectoryInfo_ 1" no longer
4035 serve any v2 directory information. Now we can test disabling the
4036 old deprecated v2 directory format, and see whether doing so has
4037 any effect on network load. Begins to fix bug 6783.
4038 - Directory authorities now include inside each vote a statement of
4039 the performance thresholds they used when assigning flags.
4040 Implements ticket 8151.
4042 o Major bugfixes (directory authorities):
4043 - Stop marking every relay as having been down for one hour every
4044 time we restart a directory authority. These artificial downtimes
4045 were messing with our Stable and Guard flag calculations. Fixes
4046 bug 8218 (introduced by the fix for 1035). Bugfix on 0.2.2.23-alpha.
4048 o Major bugfixes (hidden services):
4049 - Allow hidden service authentication to succeed again. When we
4050 refactored the hidden service introduction code back
4051 in 0.2.4.1-alpha, we didn't update the code that checks
4052 whether authentication information is present, causing all
4053 authentication checks to return "false". Fix for bug 8207; bugfix
4054 on 0.2.4.1-alpha. Found by Coverity; this is CID 718615.
4056 o Minor features (relays, bridges):
4057 - Make bridge relays check once a minute for whether their IP
4058 address has changed, rather than only every 15 minutes. Resolves
4060 - Refactor resolve_my_address() so it returns the method by which we
4061 decided our public IP address (explicitly configured, resolved from
4062 explicit hostname, guessed from interfaces, learned by gethostname).
4063 Now we can provide more helpful log messages when a relay guesses
4064 its IP address incorrectly (e.g. due to unexpected lines in
4065 /etc/hosts). Resolves ticket 2267.
4066 - Teach bridge-using clients to avoid 0.2.2 bridges when making
4067 microdescriptor-related dir requests, and only fall back to normal
4068 descriptors if none of their bridges can handle microdescriptors
4069 (as opposed to the fix in ticket 4013, which caused them to fall
4070 back to normal descriptors if *any* of their bridges preferred
4071 them). Resolves ticket 4994.
4072 - Randomize the lifetime of our SSL link certificate, so censors can't
4073 use the static value for filtering Tor flows. Resolves ticket 8443;
4074 related to ticket 4014 which was included in 0.2.2.33.
4075 - Support a new version of the link protocol that allows 4-byte circuit
4076 IDs. Previously, circuit IDs were limited to 2 bytes, which presented
4077 a possible resource exhaustion issue. Closes ticket 7351; implements
4080 o Minor features (portability):
4081 - Tweak the curve25519-donna*.c implementations to tolerate systems
4082 that lack stdint.h. Fixes bug 3894; bugfix on 0.2.4.8-alpha.
4083 - Use Ville Laurikari's implementation of AX_CHECK_SIGN() to determine
4084 the signs of types during autoconf. This is better than our old
4085 approach, which didn't work when cross-compiling.
4086 - Detect the sign of enum values, rather than assuming that MSC is the
4087 only compiler where enum types are all signed. Fixes bug 7727;
4088 bugfix on 0.2.4.10-alpha.
4090 o Minor features (other):
4091 - Say "KBytes" rather than "KB" in the man page (for various values
4092 of K), to further reduce confusion about whether Tor counts in
4093 units of memory or fractions of units of memory. Resolves ticket 7054.
4094 - Clear the high bit on curve25519 public keys before passing them to
4095 our backend, in case we ever wind up using a backend that doesn't do
4096 so itself. If we used such a backend, and *didn't* clear the high bit,
4097 we could wind up in a situation where users with such backends would
4098 be distinguishable from users without. Fixes bug 8121; bugfix on
4100 - Update to the March 6 2013 Maxmind GeoLite Country database.
4102 o Minor bugfixes (clients):
4103 - When we receive a RELAY_END cell with the reason DONE, or with no
4104 reason, before receiving a RELAY_CONNECTED cell, report the SOCKS
4105 status as "connection refused". Previously we reported these cases
4106 as success but then immediately closed the connection. Fixes bug
4107 7902; bugfix on 0.1.0.1-rc. Reported by "oftc_must_be_destroyed".
4108 - Downgrade an assertion in connection_ap_expire_beginning to an
4109 LD_BUG message. The fix for bug 8024 should prevent this message
4110 from displaying, but just in case, a warn that we can diagnose
4111 is better than more assert crashes. Fixes bug 8065; bugfix on
4113 - Lower path use bias thresholds to .80 for notice and .60 for warn.
4114 Also make the rate limiting flags for the path use bias log messages
4115 independent from the original path bias flags. Fixes bug 8161;
4116 bugfix on 0.2.4.10-alpha.
4118 o Minor bugfixes (relays):
4119 - Stop trying to resolve our hostname so often (e.g. every time we
4120 think about doing a directory fetch). Now we reuse the cached
4121 answer in some cases. Fixes bugs 1992 (bugfix on 0.2.0.20-rc)
4122 and 2410 (bugfix on 0.1.2.2-alpha).
4123 - Stop sending a stray "(null)" in some cases for the server status
4124 "EXTERNAL_ADDRESS" controller event. Resolves bug 8200; bugfix
4126 - When choosing which stream on a formerly stalled circuit to wake
4127 first, make better use of the platform's weak RNG. Previously,
4128 we had been using the % ("modulo") operator to try to generate a
4129 1/N chance of picking each stream, but this behaves badly with
4130 many platforms' choice of weak RNG. Fixes bug 7801; bugfix on
4132 - Use our own weak RNG when we need a weak RNG. Windows's rand() and
4133 Irix's random() only return 15 bits; Solaris's random() returns more
4134 bits but its RAND_MAX says it only returns 15, and so on. Motivated
4135 by the fix for bug 7801; bugfix on 0.2.2.20-alpha.
4137 o Minor bugfixes (directory authorities):
4138 - Directory authorities now use less space when formatting identical
4139 microdescriptor lines in directory votes. Fixes bug 8158; bugfix
4142 o Minor bugfixes (memory leaks spotted by Coverity -- bug 7816):
4143 - Avoid leaking memory if we fail to compute a consensus signature
4144 or we generate a consensus we can't parse. Bugfix on 0.2.0.5-alpha.
4145 - Fix a memory leak when receiving headers from an HTTPS proxy. Bugfix
4147 - Fix a memory leak during safe-cookie controller authentication.
4148 Bugfix on 0.2.3.13-alpha.
4149 - Avoid memory leak of IPv6 policy content if we fail to format it into
4150 a router descriptor. Bugfix on 0.2.4.7-alpha.
4152 o Minor bugfixes (other code correctness issues):
4153 - Avoid a crash if we fail to generate an extrainfo descriptor.
4154 Fixes bug 8208; bugfix on 0.2.3.16-alpha. Found by Coverity;
4156 - When detecting the largest possible file descriptor (in order to
4157 close all file descriptors when launching a new program), actually
4158 use _SC_OPEN_MAX. The old code for doing this was very, very broken.
4159 Fixes bug 8209; bugfix on 0.2.3.1-alpha. Found by Coverity; this
4161 - Fix a copy-and-paste error when adding a missing A1 to a routerset
4162 because of GeoIPExcludeUnknown. Fix for Coverity CID 980650.
4163 Bugfix on 0.2.4.10-alpha.
4164 - Fix an impossible-to-trigger integer overflow when estimating how
4165 long our onionskin queue would take. (This overflow would require us
4166 to accept 4 million onionskins before processing 100 of them.) Fixes
4167 bug 8210; bugfix on 0.2.4.10-alpha.
4169 o Code simplification and refactoring:
4170 - Add a wrapper function for the common "log a message with a
4174 Changes in version 0.2.4.10-alpha - 2013-02-04
4175 Tor 0.2.4.10-alpha adds defenses at the directory authority level from
4176 certain attacks that flood the network with relays; changes the queue
4177 for circuit create requests from a sized-based limit to a time-based
4178 limit; resumes building with MSVC on Windows; and fixes a wide variety
4181 o Major bugfixes (directory authority):
4182 - When computing directory thresholds, ignore any rejected-as-sybil
4183 nodes during the computation so that they can't influence Fast,
4184 Guard, etc. (We should have done this for proposal 109.) Fixes
4186 - When marking a node as a likely sybil, reset its uptime metrics
4187 to zero, so that it cannot time towards getting marked as Guard,
4188 Stable, or HSDir. (We should have done this for proposal 109.) Fixes
4192 - When a TLS write is partially successful but incomplete, remember
4193 that the flushed part has been flushed, and notice that bytes were
4194 actually written. Reported and fixed pseudonymously. Fixes bug
4195 7708; bugfix on Tor 0.1.0.5-rc.
4196 - Reject bogus create and relay cells with 0 circuit ID or 0 stream
4197 ID: these could be used to create unexpected streams and circuits
4198 which would count as "present" to some parts of Tor but "absent"
4199 to others, leading to zombie circuits and streams or to a bandwidth
4200 denial-of-service. Fixes bug 7889; bugfix on every released version
4201 of Tor. Reported by "oftc_must_be_destroyed".
4202 - Rename all macros in our local copy of queue.h to begin with "TOR_".
4203 This change seems the only good way to permanently prevent conflicts
4204 with queue.h on various operating systems. Fixes bug 8107; bugfix
4207 o Major features (relay):
4208 - Instead of limiting the number of queued onionskins (aka circuit
4209 create requests) to a fixed, hard-to-configure number, we limit
4210 the size of the queue based on how many we expect to be able to
4211 process in a given amount of time. We estimate the time it will
4212 take to process an onionskin based on average processing time
4213 of previous onionskins. Closes ticket 7291. You'll never have to
4214 configure MaxOnionsPending again.
4216 o Major features (portability):
4217 - Resume building correctly with MSVC and Makefile.nmake. This patch
4218 resolves numerous bugs and fixes reported by ultramage, including
4219 7305, 7308, 7309, 7310, 7312, 7313, 7315, 7316, and 7669.
4220 - Make the ntor and curve25519 code build correctly with MSVC.
4221 Fix on 0.2.4.8-alpha.
4224 - When directory authorities are computing thresholds for flags,
4225 never let the threshold for the Fast flag fall below 4096
4226 bytes. Also, do not consider nodes with extremely low bandwidths
4227 when deciding thresholds for various directory flags. This change
4228 should raise our threshold for Fast relays, possibly in turn
4229 improving overall network performance; see ticket 1854. Resolves
4231 - The Tor client now ignores sub-domain components of a .onion
4232 address. This change makes HTTP "virtual" hosting
4233 possible: http://foo.aaaaaaaaaaaaaaaa.onion/ and
4234 http://bar.aaaaaaaaaaaaaaaa.onion/ can be two different websites
4235 hosted on the same hidden service. Implements proposal 204.
4236 - We compute the overhead from passing onionskins back and forth to
4237 cpuworkers, and report it when dumping statistics in response to
4238 SIGUSR1. Supports ticket 7291.
4240 o Minor features (path selection):
4241 - When deciding whether we have enough descriptors to build circuits,
4242 instead of looking at raw relay counts, look at which fraction
4243 of (bandwidth-weighted) paths we're able to build. This approach
4244 keeps clients from building circuits if their paths are likely to
4245 stand out statistically. The default fraction of paths needed is
4246 taken from the consensus directory; you can override it with the
4247 new PathsNeededToBuildCircuits option. Fixes ticket 5956.
4248 - When any country code is listed in ExcludeNodes or ExcludeExitNodes,
4249 and we have GeoIP information, also exclude all nodes with unknown
4250 countries "??" and "A1". This behavior is controlled by the
4251 new GeoIPExcludeUnknown option: you can make such nodes always
4252 excluded with "GeoIPExcludeUnknown 1", and disable the feature
4253 with "GeoIPExcludeUnknown 0". Setting "GeoIPExcludeUnknown auto"
4254 gets you the default behavior. Implements feature 7706.
4255 - Path Use Bias: Perform separate accounting for successful circuit
4256 use. Keep separate statistics on stream attempt rates versus stream
4257 success rates for each guard. Provide configurable thresholds to
4258 determine when to emit log messages or disable use of guards that
4259 fail too many stream attempts. Resolves ticket 7802.
4261 o Minor features (log messages):
4262 - When learning a fingerprint for a bridge, log its corresponding
4263 transport type. Implements ticket 7896.
4264 - Improve the log message when "Bug/attack: unexpected sendme cell
4265 from client" occurs, to help us track bug 8093.
4268 - Remove a couple of extraneous semicolons that were upsetting the
4269 cparser library. Patch by Christian Grothoff. Fixes bug 7115;
4270 bugfix on 0.2.2.1-alpha.
4271 - Remove a source of rounding error during path bias count scaling;
4272 don't count cannibalized circuits as used for path bias until we
4273 actually try to use them; and fix a circuit_package_relay_cell()
4274 warning message about n_chan==NULL. Fixes bug 7802.
4275 - Detect nacl when its headers are in a nacl/ subdirectory. Also,
4276 actually link against nacl when we're configured to use it. Fixes
4277 bug 7972; bugfix on 0.2.4.8-alpha.
4278 - Compile correctly with the --disable-curve25519 option. Fixes
4279 bug 8153; bugfix on 0.2.4.8-alpha.
4281 o Build improvements:
4282 - Do not report status verbosely from autogen.sh unless the -v flag
4283 is specified. Fixes issue 4664. Patch from Onizuka.
4284 - Replace all calls to snprintf() outside of src/ext with
4285 tor_snprintf(). Also remove the #define to replace snprintf with
4286 _snprintf on Windows; they have different semantics, and all of
4287 our callers should be using tor_snprintf() anyway. Fixes bug 7304.
4288 - Try to detect if we are ever building on a platform where
4289 memset(...,0,...) does not set the value of a double to 0.0. Such
4290 platforms are permitted by the C standard, though in practice
4291 they're pretty rare (since IEEE 754 is nigh-ubiquitous). We don't
4292 currently support them, but it's better to detect them and fail
4293 than to perform erroneously.
4296 - Stop exporting estimates of v2 and v3 directory traffic shares
4297 in extrainfo documents. They were unneeded and sometimes inaccurate.
4298 Also stop exporting any v2 directory request statistics. Resolves
4300 - Drop support for detecting and warning about versions of Libevent
4301 before 1.3e. Nothing reasonable ships with them any longer;
4302 warning the user about them shouldn't be needed. Resolves ticket
4305 o Code simplifications and refactoring:
4306 - Rename "isin" functions to "contains", for grammar. Resolves
4308 - Rename Tor's logging function log() to tor_log(), to avoid conflicts
4309 with the natural logarithm function from the system libm. Resolves
4313 Changes in version 0.2.4.9-alpha - 2013-01-15
4314 Tor 0.2.4.9-alpha provides a quick fix to make the new ntor handshake
4318 - Fix backward compatibility logic when receiving an embedded ntor
4319 handshake tunneled in a CREATE cell. This clears up the "Bug:
4320 couldn't format CREATED cell" warning. Fixes bug 7959; bugfix
4324 Changes in version 0.2.4.8-alpha - 2013-01-14
4325 Tor 0.2.4.8-alpha introduces directory guards to reduce user enumeration
4326 risks, adds a new stronger and faster circuit handshake, and offers
4327 stronger and faster link encryption when both sides support it.
4330 - Preliminary support for directory guards (proposal 207): when
4331 possible, clients now use their entry guards for non-anonymous
4332 directory requests. This can help prevent client enumeration. Note
4333 that this behavior only works when we have a usable consensus
4334 directory, and when options about what to download are more or less
4335 standard. In the future we should re-bootstrap from our guards,
4336 rather than re-bootstrapping from the preconfigured list of
4337 directory sources that ships with Tor. Resolves ticket 6526.
4338 - Tor relays and clients now support a better CREATE/EXTEND cell
4339 format, allowing the sender to specify multiple address, identity,
4340 and handshake types. Implements Robert Ransom's proposal 200;
4343 o Major features (new circuit handshake):
4344 - Tor now supports a new circuit extension handshake designed by Ian
4345 Goldberg, Douglas Stebila, and Berkant Ustaoglu. Our original
4346 circuit extension handshake, later called "TAP", was a bit slow
4347 (especially on the relay side), had a fragile security proof, and
4348 used weaker keys than we'd now prefer. The new circuit handshake
4349 uses Dan Bernstein's "curve25519" elliptic-curve Diffie-Hellman
4350 function, making it significantly more secure than the older
4351 handshake, and significantly faster. Tor can use one of two built-in
4352 pure-C curve25519-donna implementations by Adam Langley, or it
4353 can link against the "nacl" library for a tuned version if present.
4355 The built-in version is very fast for 64-bit systems when building
4356 with GCC. The built-in 32-bit version is still faster than the
4357 old TAP protocol, but using libnacl is better on most such hosts.
4359 Clients don't currently use this protocol by default, since
4360 comparatively few clients support it so far. To try it, set
4361 UseNTorHandshake to 1.
4363 Implements proposal 216; closes ticket 7202.
4365 o Major features (better link encryption):
4366 - Relays can now enable the ECDHE TLS ciphersuites when available
4367 and appropriate. These ciphersuites let us negotiate forward-secure
4368 TLS secret keys more safely and more efficiently than with our
4369 previous use of Diffie-Hellman modulo a 1024-bit prime. By default,
4370 public relays prefer the (faster) P224 group, and bridges prefer
4371 the (more common) P256 group; you can override this with the
4374 Enabling these ciphers was a little tricky, since for a long time,
4375 clients had been claiming to support them without actually doing
4376 so, in order to foil fingerprinting. But with the client-side
4377 implementation of proposal 198 in 0.2.3.17-beta, clients can now
4378 match the ciphers from recent Firefox versions *and* list the
4379 ciphers they actually mean, so relays can believe such clients
4380 when they advertise ECDHE support in their TLS ClientHello messages.
4382 This feature requires clients running 0.2.3.17-beta or later,
4383 and requires both sides to be running OpenSSL 1.0.0 or later
4384 with ECC support. OpenSSL 1.0.1, with the compile-time option
4385 "enable-ec_nistp_64_gcc_128", is highly recommended.
4387 Implements the relay side of proposal 198; closes ticket 7200.
4390 - Avoid crashing when, as a relay without IPv6-exit support, a
4391 client insists on getting an IPv6 address or nothing. Fixes bug
4392 7814; bugfix on 0.2.4.7-alpha.
4395 - Improve circuit build timeout handling for hidden services.
4396 In particular: adjust build timeouts more accurately depending
4397 upon the number of hop-RTTs that a particular circuit type
4398 undergoes. Additionally, launch intro circuits in parallel
4399 if they timeout, and take the first one to reply as valid.
4400 - Work correctly on Unix systems where EAGAIN and EWOULDBLOCK are
4401 separate error codes; or at least, don't break for that reason.
4402 Fixes bug 7935. Reported by "oftc_must_be_destroyed".
4403 - Update to the January 2 2013 Maxmind GeoLite Country database.
4405 o Minor features (testing):
4406 - Add benchmarks for DH (1024-bit multiplicative group) and ECDH
4407 (P-256) Diffie-Hellman handshakes to src/or/bench.
4408 - Add benchmark functions to test onion handshake performance.
4410 o Minor features (path bias detection):
4411 - Alter the Path Bias log messages to be more descriptive in terms
4412 of reporting timeouts and other statistics.
4413 - Create three levels of Path Bias log messages, as opposed to just
4414 two. These are configurable via consensus as well as via the torrc
4415 options PathBiasNoticeRate, PathBiasWarnRate, PathBiasExtremeRate.
4416 The default values are 0.70, 0.50, and 0.30 respectively.
4417 - Separate the log message levels from the decision to drop guards,
4418 which also is available via torrc option PathBiasDropGuards.
4419 PathBiasDropGuards still defaults to 0 (off).
4420 - Deprecate PathBiasDisableRate in favor of PathBiasDropGuards
4421 in combination with PathBiasExtremeRate.
4422 - Increase the default values for PathBiasScaleThreshold and
4423 PathBiasCircThreshold from (200, 20) to (300, 150).
4424 - Add in circuit usage accounting to path bias. If we try to use a
4425 built circuit but fail for any reason, it counts as path bias.
4426 Certain classes of circuits where the adversary gets to pick your
4427 destination node are exempt from this accounting. Usage accounting
4428 can be specifically disabled via consensus parameter or torrc.
4429 - Convert all internal path bias state to double-precision floating
4430 point, to avoid roundoff error and other issues.
4431 - Only record path bias information for circuits that have completed
4432 *two* hops. Assuming end-to-end tagging is the attack vector, this
4433 makes us more resilient to ambient circuit failure without any
4434 detection capability loss.
4436 o Minor bugfixes (log messages):
4437 - Rate-limit the "No circuits are opened. Relaxed timeout for a
4438 circuit with channel state open..." message to once per hour to
4439 keep it from filling the notice logs. Mitigates bug 7799 but does
4440 not fix the underlying cause. Bugfix on 0.2.4.7-alpha.
4441 - Avoid spurious warnings when configuring multiple client ports of
4442 which only some are nonlocal. Previously, we had claimed that some
4443 were nonlocal when in fact they weren't. Fixes bug 7836; bugfix on
4446 o Code simplifications and refactoring:
4447 - Get rid of a couple of harmless clang warnings, where we compared
4448 enums to ints. These warnings are newly introduced in clang 3.2.
4449 - Split the onion.c file into separate modules for the onion queue
4450 and the different handshakes it supports.
4451 - Remove the marshalling/unmarshalling code for sending requests to
4452 cpuworkers over a socket, and instead just send structs. The
4453 recipient will always be the same Tor binary as the sender, so
4454 any encoding is overkill.
4457 Changes in version 0.2.4.7-alpha - 2012-12-24
4458 Tor 0.2.4.7-alpha introduces a new approach to providing fallback
4459 directory mirrors for more robust bootstrapping; fixes more issues where
4460 clients with changing network conditions refuse to make any circuits;
4461 adds initial support for exiting to IPv6 addresses; resumes being able
4462 to update our GeoIP database, and includes the geoip6 file this time;
4463 turns off the client-side DNS cache by default due to privacy risks;
4464 and fixes a variety of other issues.
4466 o Major features (client resilience):
4467 - Add a new "FallbackDir" torrc option to use when we can't use
4468 a directory mirror from the consensus (either because we lack a
4469 consensus, or because they're all down). Currently, all authorities
4470 are fallbacks by default, and there are no other default fallbacks,
4471 but that will change. This option will allow us to give clients a
4472 longer list of servers to try to get a consensus from when first
4473 connecting to the Tor network, and thereby reduce load on the
4474 directory authorities. Implements proposal 206, "Preconfigured
4475 directory sources for bootstrapping". We also removed the old
4476 "FallbackNetworkstatus" option, since we never got it working well
4477 enough to use it. Closes bug 572.
4478 - If we have no circuits open, use a relaxed timeout (the
4479 95-percentile cutoff) until a circuit succeeds. This heuristic
4480 should allow Tor to succeed at building circuits even when the
4481 network connection drastically changes. Should help with bug 3443.
4483 o Major features (IPv6):
4484 - Relays can now exit to IPv6 addresses: make sure that you have IPv6
4485 connectivity, then set the IPv6Exit flag to 1. Also make sure your
4486 exit policy reads as you would like: the address * applies to all
4487 address families, whereas *4 is IPv4 address only, and *6 is IPv6
4488 addresses only. On the client side, you'll need to wait until the
4489 authorities have upgraded, wait for enough exits to support IPv6,
4490 apply the "IPv6Traffic" flag to a SocksPort, and use Socks5. Closes
4491 ticket 5547, implements proposal 117 as revised in proposal 208.
4493 We DO NOT recommend that clients with actual anonymity needs start
4494 using IPv6 over Tor yet, since not enough exits support it yet.
4496 o Major features (geoip database):
4497 - Maxmind began labelling Tor relays as being in country "A1",
4498 which breaks by-country node selection inside Tor. Now we use a
4499 script to replace "A1" ("Anonymous Proxy") entries in our geoip
4500 file with real country codes. This script fixes about 90% of "A1"
4501 entries automatically and uses manual country code assignments to
4502 fix the remaining 10%. See src/config/README.geoip for details.
4503 Fixes bug 6266. Also update to the December 5 2012 Maxmind GeoLite
4504 Country database, as modified above.
4506 o Major bugfixes (client-side DNS):
4507 - Turn off the client-side DNS cache by default. Updating and using
4508 the DNS cache is now configurable on a per-client-port
4509 level. SOCKSPort, DNSPort, etc lines may now contain
4510 {No,}Cache{IPv4,IPv6,}DNS lines to indicate that we shouldn't
4511 cache these types of DNS answers when we receive them from an
4512 exit node in response to an application request on this port, and
4513 {No,}UseCached{IPv4,IPv6,DNS} lines to indicate that if we have
4514 cached DNS answers of these types, we shouldn't use them. It's
4515 potentially risky to use cached DNS answers at the client, since
4516 doing so can indicate to one exit what answers we've gotten
4517 for DNS lookups in the past. With IPv6, this becomes especially
4518 problematic. Using cached DNS answers for requests on the same
4519 circuit would present less linkability risk, since all traffic
4520 on a circuit is already linkable, but it would also provide
4521 little performance benefit: the exit node caches DNS replies
4522 too. Implements a simplified version of Proposal 205. Implements
4525 o Major bugfixes (other):
4526 - Alter circuit build timeout measurement to start at the point
4527 where we begin the CREATE/CREATE_FAST step (as opposed to circuit
4528 initialization). This should make our timeout measurements more
4529 uniform. Previously, we were sometimes including ORconn setup time
4530 in our circuit build time measurements. Should resolve bug 3443.
4531 - Fix an assertion that could trigger in hibernate_go_dormant() when
4532 closing an or_connection_t: call channel_mark_for_close() rather
4533 than connection_mark_for_close(). Fixes bug 7267. Bugfix on
4535 - Include the geoip6 IPv6 GeoIP database in the tarball. Fixes bug
4536 7655; bugfix on 0.2.4.6-alpha.
4539 - Add a new torrc option "ServerTransportListenAddr" to let bridge
4540 operators select the address where their pluggable transports will
4541 listen for connections. Resolves ticket 7013.
4542 - Allow an optional $ before the node identity digest in the
4543 controller command GETINFO ns/id/<identity>, for consistency with
4544 md/id/<identity> and desc/id/<identity>. Resolves ticket 7059.
4545 - Log packaged cell fullness as part of the heartbeat message.
4546 Diagnosis to try to determine the extent of bug 7743.
4548 o Minor features (IPv6):
4549 - AutomapHostsOnResolve now supports IPv6 addresses. By default, we
4550 prefer to hand out virtual IPv6 addresses, since there are more of
4551 them and we can't run out. To override this behavior and make IPv4
4552 addresses preferred, set NoPreferIPv6Automap on whatever SOCKSPort
4553 or DNSPort you're using for resolving. Implements ticket 7571.
4554 - AutomapHostsOnResolve responses are now randomized, to avoid
4555 annoying situations where Tor is restarted and applications
4556 connect to the wrong addresses.
4557 - Never try more than 1000 times to pick a new virtual address when
4558 AutomapHostsOnResolve is set. That's good enough so long as we
4559 aren't close to handing out our entire virtual address space;
4560 if you're getting there, it's best to switch to IPv6 virtual
4564 - The ADDRMAP command can no longer generate an ill-formed error
4565 code on a failed MAPADDRESS. It now says "internal" rather than
4566 an English sentence fragment with spaces in the middle. Bugfix on
4568 - Fix log messages and comments to avoid saying "GMT" when we mean
4569 "UTC". Fixes bug 6113.
4570 - Compile on win64 using mingw64. Fixes bug 7260; patches from
4572 - Fix a crash when debugging unit tests on Windows: deallocate a
4573 shared library with FreeLibrary, not CloseHandle. Fixes bug 7306;
4574 bugfix on 0.2.2.17-alpha. Reported by "ultramage".
4577 - The DirServer option is now DirAuthority, for consistency with
4578 current naming patterns. You can still use the old DirServer form.
4580 o Code simplification and refactoring:
4581 - Move the client-side address-map/virtual-address/DNS-cache code
4582 out of connection_edge.c into a new addressmap.c module.
4583 - Remove unused code for parsing v1 directories and "running routers"
4584 documents. Fixes bug 6887.
4587 Changes in version 0.2.3.25 - 2012-11-19
4588 The Tor 0.2.3 release series is dedicated to the memory of Len "rabbi"
4589 Sassaman (1980-2011), a long-time cypherpunk, anonymity researcher,
4590 Mixmaster maintainer, Pynchon Gate co-designer, CodeCon organizer,
4591 programmer, and friend. Unstinting in his dedication to the cause of
4592 freedom, he inspired and helped many of us as we began our work on
4593 anonymity, and inspires us still. Please honor his memory by writing
4594 software to protect people's freedoms, and by helping others to do so.
4596 Tor 0.2.3.25, the first stable release in the 0.2.3 branch, features
4597 significantly reduced directory overhead (via microdescriptors),
4598 enormous crypto performance improvements for fast relays on new
4599 enough hardware, a new v3 TLS handshake protocol that can better
4600 resist fingerprinting, support for protocol obfuscation plugins (aka
4601 pluggable transports), better scalability for hidden services, IPv6
4602 support for bridges, performance improvements like allowing clients
4603 to skip the first round-trip on the circuit ("optimistic data") and
4604 refilling token buckets more often, a new "stream isolation" design
4605 to isolate different applications on different circuits, and many
4606 stability, security, and privacy fixes.
4609 - Tor tries to wipe potentially sensitive data after using it, so
4610 that if some subsequent security failure exposes Tor's memory,
4611 the damage will be limited. But we had a bug where the compiler
4612 was eliminating these wipe operations when it decided that the
4613 memory was no longer visible to a (correctly running) program,
4614 hence defeating our attempt at defense in depth. We fix that
4615 by using OpenSSL's OPENSSL_cleanse() operation, which a compiler
4616 is unlikely to optimize away. Future versions of Tor may use
4617 a less ridiculously heavy approach for this. Fixes bug 7352.
4618 Reported in an article by Andrey Karpov.
4621 - Fix a harmless bug when opting against publishing a relay descriptor
4622 because DisableNetwork is set. Fixes bug 7464; bugfix on
4626 Changes in version 0.2.4.6-alpha - 2012-11-13
4627 Tor 0.2.4.6-alpha fixes an assert bug that has been plaguing relays,
4628 makes our defense-in-depth memory wiping more reliable, and begins to
4629 count IPv6 addresses in bridge statistics,
4632 - Fix an assertion failure that could occur when closing a connection
4633 with a spliced rendezvous circuit. Fix for bug 7212; bugfix on
4635 - Tor tries to wipe potentially sensitive data after using it, so
4636 that if some subsequent security failure exposes Tor's memory,
4637 the damage will be limited. But we had a bug where the compiler
4638 was eliminating these wipe operations when it decided that the
4639 memory was no longer visible to a (correctly running) program,
4640 hence defeating our attempt at defense in depth. We fix that
4641 by using OpenSSL's OPENSSL_cleanse() operation, which a compiler
4642 is unlikely to optimize away. Future versions of Tor may use
4643 a less ridiculously heavy approach for this. Fixes bug 7352.
4644 Reported in an article by Andrey Karpov.
4647 - Add GeoIP database for IPv6 addresses. The new config option
4649 - Bridge statistics now count bridge clients connecting over IPv6:
4650 bridge statistics files now list "bridge-ip-versions" and
4651 extra-info documents list "geoip6-db-digest". The control protocol
4652 "CLIENTS_SEEN" and "ip-to-country" queries now support IPv6. Initial
4653 implementation by "shkoo", addressing ticket 5055.
4656 - Warn when we are binding low ports when hibernation is enabled;
4657 previously we had warned when we were _advertising_ low ports with
4658 hibernation enabled. Fixes bug 7285; bugfix on 0.2.3.9-alpha.
4659 - Fix a harmless bug when opting against publishing a relay descriptor
4660 because DisableNetwork is set. Fixes bug 7464; bugfix on
4662 - Add warning message when a managed proxy dies during configuration.
4663 Fixes bug 7195; bugfix on 0.2.4.2-alpha.
4664 - Fix a linking error when building tor-fw-helper without miniupnp.
4665 Fixes bug 7235; bugfix on 0.2.4.2-alpha. Fix by Anthony G. Basile.
4666 - Check for closing an or_connection_t without going through correct
4667 channel functions; emit a warning and then call
4668 connection_or_close_for_error() so we don't assert as in bugs 7212
4670 - Compile correctly on compilers without C99 designated initializer
4671 support. Fixes bug 7286; bugfix on 0.2.4.4-alpha.
4672 - Avoid a possible assert that can occur when channel_send_destroy() is
4673 called on a channel in CHANNEL_STATE_CLOSING, CHANNEL_STATE_CLOSED,
4674 or CHANNEL_STATE_ERROR when the Tor process is resumed after being
4675 blocked for a long interval. Fixes bug 7350; bugfix on 0.2.4.4-alpha.
4676 - Fix a memory leak on failing cases of channel_tls_process_certs_cell.
4677 Fixes bug 7422; bugfix on 0.2.4.4-alpha.
4679 o Code simplification and refactoring:
4680 - Start using OpenBSD's implementation of queue.h, so that we don't
4681 need to hand-roll our own pointer and list structures whenever we
4682 need them. (We can't rely on a sys/queue.h, since some operating
4683 systems don't have them, and the ones that do have them don't all
4684 present the same extensions.)
4687 Changes in version 0.2.4.5-alpha - 2012-10-25
4688 Tor 0.2.4.5-alpha comes hard at the heels of 0.2.4.4-alpha, to fix
4689 two important security vulnerabilities that could lead to remotely
4690 triggerable relay crashes, fix a major bug that was preventing clients
4691 from choosing suitable exit nodes, and refactor some of our code.
4693 o Major bugfixes (security, also in 0.2.3.24-rc):
4694 - Fix a group of remotely triggerable assertion failures related to
4695 incorrect link protocol negotiation. Found, diagnosed, and fixed
4696 by "some guy from France". Fix for CVE-2012-2250; bugfix on
4698 - Fix a denial of service attack by which any directory authority
4699 could crash all the others, or by which a single v2 directory
4700 authority could crash everybody downloading v2 directory
4701 information. Fixes bug 7191; bugfix on 0.2.0.10-alpha.
4703 o Major bugfixes (also in 0.2.3.24-rc):
4704 - When parsing exit policy summaries from microdescriptors, we had
4705 previously been ignoring the last character in each one, so that
4706 "accept 80,443,8080" would be treated by clients as indicating
4707 a node that allows access to ports 80, 443, and 808. That would
4708 lead to clients attempting connections that could never work,
4709 and ignoring exit nodes that would support their connections. Now
4710 clients parse these exit policy summaries correctly. Fixes bug 7192;
4711 bugfix on 0.2.3.1-alpha.
4713 o Minor bugfixes (also in 0.2.3.24-rc):
4714 - Clients now consider the ClientRejectInternalAddresses config option
4715 when using a microdescriptor consensus stanza to decide whether
4716 an exit relay would allow exiting to an internal address. Fixes
4717 bug 7190; bugfix on 0.2.3.1-alpha.
4720 - Only disable TLS session ticket support when running as a TLS
4721 server. Now clients will blend better with regular Firefox
4722 connections. Fixes bug 7189; bugfix on Tor 0.2.3.23-rc.
4724 o Code simplification and refactoring:
4725 - Start using OpenBSD's implementation of queue.h (originally by
4727 - Move the entry node code from circuitbuild.c to its own file.
4728 - Move the circuit build timeout tracking code from circuitbuild.c
4732 Changes in version 0.2.3.24-rc - 2012-10-25
4733 Tor 0.2.3.24-rc fixes two important security vulnerabilities that
4734 could lead to remotely triggerable relay crashes, and fixes
4735 a major bug that was preventing clients from choosing suitable exit
4738 o Major bugfixes (security):
4739 - Fix a group of remotely triggerable assertion failures related to
4740 incorrect link protocol negotiation. Found, diagnosed, and fixed
4741 by "some guy from France". Fix for CVE-2012-2250; bugfix on
4743 - Fix a denial of service attack by which any directory authority
4744 could crash all the others, or by which a single v2 directory
4745 authority could crash everybody downloading v2 directory
4746 information. Fixes bug 7191; bugfix on 0.2.0.10-alpha.
4749 - When parsing exit policy summaries from microdescriptors, we had
4750 previously been ignoring the last character in each one, so that
4751 "accept 80,443,8080" would be treated by clients as indicating
4752 a node that allows access to ports 80, 443, and 808. That would
4753 lead to clients attempting connections that could never work,
4754 and ignoring exit nodes that would support their connections. Now
4755 clients parse these exit policy summaries correctly. Fixes bug 7192;
4756 bugfix on 0.2.3.1-alpha.
4759 - Clients now consider the ClientRejectInternalAddresses config option
4760 when using a microdescriptor consensus stanza to decide whether
4761 an exit relay would allow exiting to an internal address. Fixes
4762 bug 7190; bugfix on 0.2.3.1-alpha.
4765 Changes in version 0.2.4.4-alpha - 2012-10-20
4766 Tor 0.2.4.4-alpha adds a new v3 directory authority, fixes a privacy
4767 vulnerability introduced by a change in OpenSSL, fixes a remotely
4768 triggerable assert, and adds new channel_t and circuitmux_t abstractions
4769 that will make it easier to test new connection transport and cell
4770 scheduling algorithms.
4772 o New directory authorities (also in 0.2.3.23-rc):
4773 - Add Faravahar (run by Sina Rabbani) as the ninth v3 directory
4774 authority. Closes ticket 5749.
4776 o Major bugfixes (security/privacy, also in 0.2.3.23-rc):
4777 - Disable TLS session tickets. OpenSSL's implementation was giving
4778 our TLS session keys the lifetime of our TLS context objects, when
4779 perfect forward secrecy would want us to discard anything that
4780 could decrypt a link connection as soon as the link connection
4781 was closed. Fixes bug 7139; bugfix on all versions of Tor linked
4782 against OpenSSL 1.0.0 or later. Found by Florent Daignière.
4783 - Discard extraneous renegotiation attempts once the V3 link
4784 protocol has been initiated. Failure to do so left us open to
4785 a remotely triggerable assertion failure. Fixes CVE-2012-2249;
4786 bugfix on 0.2.3.6-alpha. Reported by "some guy from France".
4788 o Internal abstraction features:
4789 - Introduce new channel_t abstraction between circuits and
4790 or_connection_t to allow for implementing alternate OR-to-OR
4791 transports. A channel_t is an abstract object which can either be a
4792 cell-bearing channel, which is responsible for authenticating and
4793 handshaking with the remote OR and transmitting cells to and from
4794 it, or a listening channel, which spawns new cell-bearing channels
4795 at the request of remote ORs. Implements part of ticket 6465.
4796 - Also new is the channel_tls_t subclass of channel_t, adapting it
4797 to the existing or_connection_t code. The V2/V3 protocol handshaking
4798 code which formerly resided in command.c has been moved below the
4799 channel_t abstraction layer and may be found in channeltls.c now.
4800 Implements the rest of ticket 6465.
4801 - Introduce new circuitmux_t storing the queue of circuits for
4802 a channel; this encapsulates and abstracts the queue logic and
4803 circuit selection policy, and allows the latter to be overridden
4804 easily by switching out a policy object. The existing EWMA behavior
4805 is now implemented as a circuitmux_policy_t. Resolves ticket 6816.
4807 o Required libraries:
4808 - Tor now requires OpenSSL 0.9.8 or later. OpenSSL 1.0.0 or later is
4809 strongly recommended.
4812 - Warn users who run hidden services on a Tor client with
4813 UseEntryGuards disabled that their hidden services will be
4814 vulnerable to http://freehaven.net/anonbib/#hs-attack06 (the
4815 attack which motivated Tor to support entry guards in the first
4816 place). Resolves ticket 6889.
4817 - Tor now builds correctly on Bitrig, an OpenBSD fork. Patch from
4818 dhill. Resolves ticket 6982.
4819 - Option OutboundBindAddress can be specified multiple times and
4820 accepts IPv6 addresses. Resolves ticket 6876.
4822 o Minor bugfixes (also in 0.2.3.23-rc):
4823 - Don't serve or accept v2 hidden service descriptors over a
4824 relay's DirPort. It's never correct to do so, and disabling it
4825 might make it more annoying to exploit any bugs that turn up in the
4826 descriptor-parsing code. Fixes bug 7149.
4827 - Fix two cases in src/or/transports.c where we were calling
4828 fmt_addr() twice in a parameter list. Bug found by David
4829 Fifield. Fixes bug 7014; bugfix on 0.2.3.9-alpha.
4830 - Fix memory leaks whenever we logged any message about the "path
4831 bias" detection. Fixes bug 7022; bugfix on 0.2.3.21-rc.
4832 - When relays refuse a "create" cell because their queue of pending
4833 create cells is too big (typically because their cpu can't keep up
4834 with the arrival rate), send back reason "resource limit" rather
4835 than reason "internal", so network measurement scripts can get a
4836 more accurate picture. Fixes bug 7037; bugfix on 0.1.1.11-alpha.
4839 - Command-line option "--version" implies "--quiet". Fixes bug 6997.
4840 - Free some more still-in-use memory at exit, to make hunting for
4841 memory leaks easier. Resolves bug 7029.
4842 - When a Tor client gets a "truncated" relay cell, the first byte of
4843 its payload specifies why the circuit was truncated. We were
4844 ignoring this 'reason' byte when tearing down the circuit, resulting
4845 in the controller not being told why the circuit closed. Now we
4846 pass the reason from the truncated cell to the controller. Bugfix
4847 on 0.1.2.3-alpha; fixes bug 7039.
4848 - Downgrade "Failed to hand off onionskin" messages to "debug"
4849 severity, since they're typically redundant with the "Your computer
4850 is too slow" messages. Fixes bug 7038; bugfix on 0.2.2.16-alpha.
4851 - Make clients running with IPv6 bridges connect over IPv6 again,
4852 even without setting new config options ClientUseIPv6 and
4853 ClientPreferIPv6ORPort. Fixes bug 6757; bugfix on 0.2.4.1-alpha.
4854 - Use square brackets around IPv6 addresses in numerous places
4855 that needed them, including log messages, HTTPS CONNECT proxy
4856 requests, TransportProxy statefile entries, and pluggable transport
4857 extra-info lines. Fixes bug 7011; patch by David Fifield.
4859 o Code refactoring and cleanup:
4860 - Source files taken from other packages now reside in src/ext;
4861 previously they were scattered around the rest of Tor.
4862 - Avoid use of reserved identifiers in our C code. The C standard
4863 doesn't like us declaring anything that starts with an
4864 underscore, so let's knock it off before we get in trouble. Fix
4865 for bug 1031; bugfix on the first Tor commit.
4868 Changes in version 0.2.3.23-rc - 2012-10-20
4869 Tor 0.2.3.23-rc adds a new v3 directory authority, fixes a privacy
4870 vulnerability introduced by a change in OpenSSL, and fixes a variety
4871 of smaller bugs in preparation for the release.
4873 o New directory authorities:
4874 - Add Faravahar (run by Sina Rabbani) as the ninth v3 directory
4875 authority. Closes ticket 5749.
4877 o Major bugfixes (security/privacy):
4878 - Disable TLS session tickets. OpenSSL's implementation was giving
4879 our TLS session keys the lifetime of our TLS context objects, when
4880 perfect forward secrecy would want us to discard anything that
4881 could decrypt a link connection as soon as the link connection
4882 was closed. Fixes bug 7139; bugfix on all versions of Tor linked
4883 against OpenSSL 1.0.0 or later. Found by Florent Daignière.
4884 - Discard extraneous renegotiation attempts once the V3 link
4885 protocol has been initiated. Failure to do so left us open to
4886 a remotely triggerable assertion failure. Fixes CVE-2012-2249;
4887 bugfix on 0.2.3.6-alpha. Reported by "some guy from France".
4890 - Fix a possible crash bug when checking for deactivated circuits
4891 in connection_or_flush_from_first_active_circuit(). Fixes bug 6341;
4892 bugfix on 0.2.2.7-alpha. Bug report and fix received pseudonymously.
4894 o Minor bugfixes (on 0.2.3.x):
4895 - Fix two cases in src/or/transports.c where we were calling
4896 fmt_addr() twice in a parameter list. Bug found by David
4897 Fifield. Fixes bug 7014; bugfix on 0.2.3.9-alpha.
4898 - Convert an assert in the pathbias code to a log message. The assert
4899 appears to only be triggerable by Tor2Web mode. Fixes bug 6866;
4900 bugfix on 0.2.3.17-beta.
4901 - Fix memory leaks whenever we logged any message about the "path
4902 bias" detection. Fixes bug 7022; bugfix on 0.2.3.21-rc.
4904 o Minor bugfixes (on 0.2.2.x and earlier):
4905 - Don't serve or accept v2 hidden service descriptors over a relay's
4906 DirPort. It's never correct to do so, and disabling it might
4907 make it more annoying to exploit any bugs that turn up in the
4908 descriptor-parsing code. Fixes bug 7149.
4909 - When relays refuse a "create" cell because their queue of pending
4910 create cells is too big (typically because their cpu can't keep up
4911 with the arrival rate), send back reason "resource limit" rather
4912 than reason "internal", so network measurement scripts can get a
4913 more accurate picture. Bugfix on 0.1.1.11-alpha; fixes bug 7037.
4914 - Correct file sizes when reading binary files on Cygwin, to avoid
4915 a bug where Tor would fail to read its state file. Fixes bug 6844;
4916 bugfix on 0.1.2.7-alpha.
4917 - Avoid undefined behavior when parsing the list of supported
4918 rendezvous/introduction protocols in a hidden service descriptor.
4919 Previously, Tor would have confused (as-yet-unused) protocol version
4920 numbers greater than 32 with lower ones on many platforms. Fixes
4921 bug 6827; bugfix on 0.2.0.10-alpha. Found by George Kadianakis.
4923 o Documentation fixes:
4924 - Clarify that hidden services are TCP only. Fixes bug 6024.
4927 Changes in version 0.2.4.3-alpha - 2012-09-22
4928 Tor 0.2.4.3-alpha fixes another opportunity for a remotely triggerable
4929 assertion, resumes letting relays test reachability of their DirPort,
4930 and cleans up a bunch of smaller bugs.
4933 - Fix an assertion failure in tor_timegm() that could be triggered
4934 by a badly formatted directory object. Bug found by fuzzing with
4935 Radamsa. Fixes bug 6811; bugfix on 0.2.0.20-rc.
4938 - Fix a possible crash bug when checking for deactivated circuits
4939 in connection_or_flush_from_first_active_circuit(). Fixes bug 6341;
4940 bugfix on 0.2.2.7-alpha. Bug report and fix received pseudonymously.
4941 - Allow routers to detect that their own DirPorts are running. When
4942 we removed support for versions_supports_begindir, we also
4943 accidentally removed the mechanism we used to self-test our
4944 DirPort. Diagnosed with help from kargig. Fixes bugs 6814 and 6815;
4945 bugfix on 0.2.4.2-alpha.
4947 o Security features:
4948 - Switch to a completely time-invariant approach for picking nodes
4949 weighted by bandwidth. Our old approach would run through the
4950 part of the loop after it had made its choice slightly slower
4951 than it ran through the part of the loop before it had made its
4952 choice. Addresses ticket 6538.
4953 - Disable the use of Guard nodes when in Tor2WebMode. Guard usage
4954 by tor2web clients allows hidden services to identify tor2web
4955 clients through their repeated selection of the same rendezvous
4956 and introduction point circuit endpoints (their guards). Resolves
4960 - Enable Tor to read configuration, state, and key information from
4961 a FIFO. Previously Tor would only read from files with a positive
4962 stat.st_size. Code from meejah; fixes bug 6044.
4965 - Correct file sizes when reading binary files on Cygwin, to avoid
4966 a bug where Tor would fail to read its state file. Fixes bug 6844;
4967 bugfix on 0.1.2.7-alpha.
4968 - Correctly handle votes with more than 31 flags. Fixes bug 6853;
4969 bugfix on 0.2.0.3-alpha.
4970 - When complaining about a client port on a public address, log
4971 which address we're complaining about. Fixes bug 4020; bugfix on
4972 0.2.3.3-alpha. Patch by Tom Fitzhenry.
4973 - Convert an assert in the pathbias code to a log message. The assert
4974 appears to only be triggerable by Tor2Web mode. Fixes bug 6866;
4975 bugfix on 0.2.3.17-beta.
4976 - Our new buildsystem was overzealous about rebuilding manpages: it
4977 would rebuild them all whenever any one of them changed. Now our
4978 dependency checking should be correct. Fixes bug 6843; bugfix on
4980 - Don't do reachability testing over IPv6 unless AuthDirPublishIPv6
4981 is set. Fixes bug 6880. Bugfix on 0.2.4.1-alpha.
4982 - Correct log printout about which address family is preferred
4983 when connecting to a bridge with both an IPv4 and IPv6 OR port.
4984 Fixes bug 6884; bugfix on 0.2.4.1-alpha.
4986 o Minor bugfixes (code cleanliness):
4987 - Fix round_to_power_of_2() so it doesn't invoke undefined behavior
4988 with large values. This situation was untriggered, but nevertheless
4989 incorrect. Fixes bug 6831; bugfix on 0.2.0.1-alpha.
4990 - Reject consensus votes with more than 64 known-flags. We aren't even
4991 close to that limit yet, and our code doesn't handle it correctly.
4992 Fixes bug 6833; bugfix on 0.2.0.1-alpha.
4993 - Avoid undefined behavior when parsing the list of supported
4994 rendezvous/introduction protocols in a hidden service descriptor.
4995 Previously, Tor would have confused (as-yet-unused) protocol version
4996 numbers greater than 32 with lower ones on many platforms. Fixes
4997 bug 6827; bugfix on 0.2.0.10-alpha. Found by George Kadianakis.
4998 - Fix handling of rendezvous client authorization types over 8.
4999 Fixes bug 6861; bugfix on 0.2.1.5-alpha.
5000 - Fix building with older versions of GCC (2.95, for one) that don't
5001 like preprocessor directives inside macro arguments. Found by
5002 grarpamp. Fixes bug 6842; bugfix on 0.2.4.2-alpha.
5003 - Switch weighted node selection rule from using a list of doubles
5004 to using a list of int64_t. This change should make the process
5005 slightly easier to debug and maintain. Needed to finish ticket 6538.
5007 o Code simplification and refactoring:
5008 - Move the generic "config" code into a new file, and have "config.c"
5009 hold only torrc- and state-related code. Resolves ticket 6823.
5010 - Move the core of our "choose a weighted element at random" logic
5011 into its own function, and give it unit tests. Now the logic is
5012 testable, and a little less fragile too.
5013 - Removed the testing_since field of node_t, which hasn't been used
5014 for anything since 0.2.0.9-alpha.
5016 o Documentation fixes:
5017 - Clarify that hidden services are TCP only. Fixes bug 6024.
5018 - Resolve a typo in torrc.sample.in. Fixes bug 6819; bugfix on
5022 Changes in version 0.2.3.22-rc - 2012-09-11
5023 Tor 0.2.3.22-rc fixes another opportunity for a remotely triggerable
5027 - Fix an assertion failure in tor_timegm() that could be triggered
5028 by a badly formatted directory object. Bug found by fuzzing with
5029 Radamsa. Fixes bug 6811; bugfix on 0.2.0.20-rc.
5032 - Avoid segfault when starting up having run with an extremely old
5033 version of Tor and parsing its state file. Fixes bug 6801; bugfix
5037 Changes in version 0.2.2.39 - 2012-09-11
5038 Tor 0.2.2.39 fixes two more opportunities for remotely triggerable
5042 - Fix an assertion failure in tor_timegm() that could be triggered
5043 by a badly formatted directory object. Bug found by fuzzing with
5044 Radamsa. Fixes bug 6811; bugfix on 0.2.0.20-rc.
5045 - Do not crash when comparing an address with port value 0 to an
5046 address policy. This bug could have been used to cause a remote
5047 assertion failure by or against directory authorities, or to
5048 allow some applications to crash clients. Fixes bug 6690; bugfix
5052 Changes in version 0.2.4.2-alpha - 2012-09-10
5053 Tor 0.2.4.2-alpha enables port forwarding for pluggable transports,
5054 raises the default rate limiting even more, and makes the bootstrapping
5055 log messages less noisy.
5058 - Automatically forward the TCP ports of pluggable transport
5059 proxies using tor-fw-helper if PortForwarding is enabled. Implements
5063 - Raise the default BandwidthRate/BandwidthBurst values from 5MB/10MB
5064 to 1GB/1GB. The previous defaults were intended to be "basically
5065 infinite", but it turns out they're now limiting our 100mbit+
5066 relays and bridges. Fixes bug 6605; bugfix on 0.2.0.10-alpha (the
5067 last time we raised it).
5070 - Detect when we're running with a version of OpenSSL other than the
5071 one we compiled with. This has occasionally given people hard-to-
5073 - Log fewer lines at level "notice" about our OpenSSL and Libevent
5074 versions and capabilities when everything is going right. Resolves
5075 part of ticket 6736.
5076 - Directory authorities no long accept descriptors for any version of
5077 Tor before 0.2.2.35, or for any 0.2.3 release before 0.2.3.10-alpha.
5078 These versions are insecure, unsupported, or both. Implements
5082 - Rename the (internal-use-only) UsingTestingNetworkDefaults option
5083 to start with a triple-underscore so the controller won't touch it.
5084 Patch by Meejah. Fixes bug 3155. Bugfix on 0.2.2.23-alpha.
5085 - Avoid segfault when starting up having run with an extremely old
5086 version of Tor and parsing its state file. Fixes bug 6801; bugfix
5088 - Rename the (testing-use-only) _UseFilteringSSLBufferevents option
5089 so it doesn't start with _. Fixes bug 3155. Bugfix on 0.2.3.1-alpha.
5090 - Don't follow the NULL pointer if microdescriptor generation fails.
5091 (This does not appear to be triggerable, but it's best to be safe.)
5092 Found by "f. tp.". Fixes bug 6797; bugfix on 0.2.4.1-alpha.
5093 - Fix mis-declared dependencies on src/common/crypto.c and
5094 src/or/tor_main.c that could break out-of-tree builds under some
5095 circumstances. Fixes bug 6778; bugfix on 0.2.4.1-alpha.
5096 - Avoid a warning when building common_sha1.i out of tree. Fixes bug
5097 6778; bugfix on 0.2.4.1-alpha.
5098 - Fix a harmless (in this case) build warning for implicitly
5099 converting a strlen() to an int. Bugfix on 0.2.4.1-alpha.
5102 - Now that all versions before 0.2.2.x are disallowed, we no longer
5103 need to work around their missing features. Thus we can remove a
5104 bunch of compatibility code.
5107 - Tweak tor-fw-helper to accept an arbitrary amount of arbitrary
5108 TCP ports to forward. In the past it only accepted two ports:
5109 the ORPort and the DirPort.
5112 Changes in version 0.2.4.1-alpha - 2012-09-05
5113 Tor 0.2.4.1-alpha lets bridges publish their pluggable transports to
5114 bridgedb; lets relays use IPv6 addresses and directory authorities
5115 advertise them; and switches to a cleaner build interface.
5117 This is the first alpha release in a new series, so expect there to
5118 be bugs. Users who would rather test out a more stable branch should
5119 stay with 0.2.3.x for now.
5121 o Major features (bridges):
5122 - Bridges now report the pluggable transports they support to the
5123 bridge authority, so it can pass the supported transports on to
5124 bridgedb and/or eventually do reachability testing. Implements
5127 o Major features (IPv6):
5128 - Bridge authorities now accept IPv6 bridge addresses and include
5129 them in network status documents. Implements ticket 5534.
5130 - Clients who set "ClientUseIPv6 1" may connect to entry nodes over
5131 IPv6. Set "ClientPreferIPv6ORPort 1" to make this even more likely
5132 to happen. Implements ticket 5535.
5133 - All kind of relays, not just bridges, can now advertise an IPv6
5134 OR port. Implements ticket 6362.
5135 - Directory authorities vote on IPv6 OR ports using the new consensus
5136 method 14. Implements ticket 6363.
5138 o Major features (build):
5139 - Switch to a nonrecursive Makefile structure. Now instead of each
5140 Makefile.am invoking other Makefile.am's, there is a master
5141 Makefile.am that includes the others. This change makes our build
5142 process slightly more maintainable, and improves parallelism for
5143 building with make -j. Original patch by Stewart Smith; various
5144 fixes by Jim Meyering.
5145 - Where available, we now use automake's "silent" make rules by
5146 default, so that warnings are easier to spot. You can get the old
5147 behavior with "make V=1". Patch by Stewart Smith for ticket 6522.
5149 o Minor features (code security and spec conformance):
5150 - Clear keys and key-derived material left on the stack in
5151 rendservice.c and rendclient.c. Check return value of
5152 crypto_pk_write_private_key_to_string() in rend_service_load_keys().
5153 These fixes should make us more forward-secure against cold-boot
5154 attacks and the like. Fixes bug 2385.
5155 - Reject EXTEND cells sent to nonexistent streams. According to the
5156 spec, an EXTEND cell sent to _any_ nonzero stream ID is invalid, but
5157 we were only checking for stream IDs that were currently in use.
5158 Found while hunting for more instances of bug 6271. Bugfix on
5159 0.0.2pre8, which introduced incremental circuit construction.
5161 o Minor features (streamlining);
5162 - No longer include the "opt" prefix when generating routerinfos
5163 or v2 directories: it has been needless since Tor 0.1.2. Closes
5165 - Remove some now-needless code that tried to aggressively flush
5166 OR connections as data was added to them. Since 0.2.0.1-alpha, our
5167 cell queue logic has saved us from the failure mode that this code
5168 was supposed to prevent. Removing this code will limit the number
5169 of baroque control flow paths through Tor's network logic. Reported
5170 pseudonymously on IRC. Fixes bug 6468; bugfix on 0.2.0.1-alpha.
5172 o Minor features (controller):
5173 - Add a "GETINFO signal/names" control port command. Implements
5175 - Provide default values for all options via "GETINFO config/defaults".
5176 Implements ticket 4971.
5178 o Minor features (IPv6):
5179 - New config option "AuthDirHasIPv6Connectivity 1" that directory
5180 authorities should set if they have IPv6 connectivity and want to
5181 do reachability tests for IPv6 relays. Implements feature 5974.
5182 - A relay with an IPv6 OR port now sends that address in NETINFO
5183 cells (in addition to its other address). Implements ticket 6364.
5185 o Minor features (log messages):
5186 - Omit the first heartbeat log message, because it never has anything
5187 useful to say, and it clutters up the bootstrapping messages.
5188 Resolves ticket 6758.
5189 - Don't log about reloading the microdescriptor cache at startup. Our
5190 bootstrap warnings are supposed to tell the user when there's a
5191 problem, and our bootstrap notices say when there isn't. Resolves
5192 ticket 6759; bugfix on 0.2.2.6-alpha.
5193 - Don't log "I learned some more directory information" when we're
5194 reading cached directory information. Reserve it for when new
5195 directory information arrives in response to a fetch. Resolves
5197 - Prevent rounding error in path bias counts when scaling
5198 them down, and use the correct scale factor default. Also demote
5199 some path bias related log messages down a level and make others
5200 less scary sounding. Fixes bug 6647. Bugfix against 0.2.3.17-beta.
5201 - We no longer warn so much when generating manpages from their
5204 o Code simplifications and refactoring:
5205 - Enhance our internal sscanf replacement so that we can eliminate
5206 the last remaining uses of the system sscanf. (Though those uses
5207 of sscanf were safe, sscanf itself is generally error prone, so
5208 we want to eliminate when we can.) Fixes ticket 4195 and Coverity
5210 - Move ipv6_preferred from routerinfo_t to node_t. Addresses bug 4620.
5211 - Move last_reachable and testing_since from routerinfo_t to node_t.
5212 Implements ticket 5529.
5213 - Add replaycache_t structure, functions and unit tests, then refactor
5214 rend_service_introduce() to be more clear to read, improve, debug,
5215 and test. Resolves bug 6177.
5216 - Finally remove support for malloc_good_size and malloc_usable_size.
5217 We had hoped that these functions would let us eke a little more
5218 memory out of our malloc implementation. Unfortunately, the only
5219 implementations that provided these functions are also ones that
5220 are already efficient about not overallocation: they never got us
5221 more than 7 or so bytes per allocation. Removing them saves us a
5222 little code complexity and a nontrivial amount of build complexity.
5225 - Tor maintainers now require Automake version 1.9 or later to build
5226 Tor from the Git repository. (Automake is not required when building
5227 from a source distribution.)
5230 Changes in version 0.2.3.21-rc - 2012-09-05
5231 Tor 0.2.3.21-rc is the fourth release candidate for the Tor 0.2.3.x
5232 series. It fixes a trio of potential security bugs, fixes a bug where
5233 we were leaving some of the fast relays out of the microdescriptor
5234 consensus, resumes interpreting "ORPort 0" and "DirPort 0" correctly,
5235 and cleans up other smaller issues.
5237 o Major bugfixes (security):
5238 - Tear down the circuit if we get an unexpected SENDME cell. Clients
5239 could use this trick to make their circuits receive cells faster
5240 than our flow control would have allowed, or to gum up the network,
5241 or possibly to do targeted memory denial-of-service attacks on
5242 entry nodes. Fixes bug 6252. Bugfix on the 54th commit on Tor --
5243 from July 2002, before the release of Tor 0.0.0. We had committed
5244 this patch previously, but we had to revert it because of bug 6271.
5245 Now that 6271 is fixed, this patch appears to work.
5246 - Reject any attempt to extend to an internal address. Without
5247 this fix, a router could be used to probe addresses on an internal
5248 network to see whether they were accepting connections. Fixes bug
5249 6710; bugfix on 0.0.8pre1.
5250 - Do not crash when comparing an address with port value 0 to an
5251 address policy. This bug could have been used to cause a remote
5252 assertion failure by or against directory authorities, or to
5253 allow some applications to crash clients. Fixes bug 6690; bugfix
5257 - Remove the upper bound on microdescriptor length. We were hitting
5258 the limit for routers with complex exit policies or family
5259 declarations, causing clients to not use them. Fixes the first
5260 piece of bug 6404; fix on 0.2.2.6-alpha.
5261 - Detect "ORPort 0" as meaning, uniformly, that we're not running
5262 as a relay. Previously, some of our code would treat the presence
5263 of any ORPort line as meaning that we should act like a relay,
5264 even though our new listener code would correctly not open any
5265 ORPorts for ORPort 0. Similar bugs in other Port options are also
5266 fixed. Fixes the first half of bug 6507; bugfix on 0.2.3.3-alpha.
5269 - Avoid a pair of double-free and use-after-mark bugs that can
5270 occur with certain timings in canceled and re-received DNS
5271 requests. Fixes bug 6472; bugfix on 0.0.7rc1.
5272 - Fix build and 64-bit compile warnings from --enable-openbsd-malloc.
5273 Fixes bug 6379. Bugfix on 0.2.0.20-rc.
5274 - Allow one-hop directory fetching circuits the full "circuit build
5275 timeout" period, rather than just half of it, before failing them
5276 and marking the relay down. This fix should help reduce cases where
5277 clients declare relays (or worse, bridges) unreachable because
5278 the TLS handshake takes a few seconds to complete. Fixes bug 6743;
5279 bugfix on 0.2.2.2-alpha, where we changed the timeout from a static
5281 - Authorities no longer include any router in their microdescriptor
5282 consensuses for which they couldn't generate or agree on a
5283 microdescriptor. Fixes the second piece of bug 6404; fix on
5285 - Detect and reject attempts to specify both "FooPort" and
5286 "FooPort 0" in the same configuration domain. (It's still okay
5287 to have a FooPort in your configuration file, and use "FooPort 0"
5288 on the command line to disable it.) Fixes the second half of bug
5289 6507; bugfix on 0.2.3.3-alpha.
5290 - Make wildcarded addresses (that is, ones beginning with "*.") work
5291 when provided via the controller's MapAddress command. Previously,
5292 they were accepted, but we never actually noticed that they were
5293 wildcards. Fixes bug 6244; bugfix on 0.2.3.9-alpha.
5294 - Avoid crashing on a malformed state file where EntryGuardPathBias
5295 precedes EntryGuard. Fix for bug 6774; bugfix on 0.2.3.17-beta.
5296 - Add a (probably redundant) memory clear between iterations of
5297 the router status voting loop, to prevent future coding errors
5298 where data might leak between iterations of the loop. Resolves
5301 o Minor bugfixes (log messages):
5302 - Downgrade "set buildtimeout to low value" messages to "info"
5303 severity; they were never an actual problem, there was never
5304 anything reasonable to do about them, and they tended to spam logs
5305 from time to time. Fixes bug 6251; bugfix on 0.2.2.2-alpha.
5306 - Downgrade path-bias warning messages to "info". We'll try to get
5307 them working better in 0.2.4. Add internal circuit construction
5308 state to protect against the noisy warn message "Unexpectedly high
5309 circuit_successes". Also add some additional rate-limited notice
5310 messages to help determine the root cause of the warn. Fixes bug
5311 6475. Bugfix against 0.2.3.17-beta.
5312 - Move log message when unable to find a microdesc in a routerstatus
5313 entry to parse time. Previously we'd spam this warning every time
5314 we tried to figure out which microdescriptors to download. Fixes
5315 the third piece of bug 6404; fix on 0.2.3.18-rc.
5318 - Consider new, removed or changed IPv6 OR ports a non-cosmetic
5319 change when the authority is deciding whether to accept a newly
5320 uploaded descriptor. Implements ticket 6423.
5321 - Add missing documentation for consensus and microdesc files.
5322 Resolves ticket 6732.
5325 Changes in version 0.2.2.38 - 2012-08-12
5326 Tor 0.2.2.38 fixes a remotely triggerable crash bug, and fixes a timing
5327 attack that could in theory leak path information.
5330 - Avoid an uninitialized memory read when reading a vote or consensus
5331 document that has an unrecognized flavor name. This read could
5332 lead to a remote crash bug. Fixes bug 6530; bugfix on 0.2.2.6-alpha.
5333 - Try to leak less information about what relays a client is
5334 choosing to a side-channel attacker. Previously, a Tor client would
5335 stop iterating through the list of available relays as soon as it
5336 had chosen one, thus finishing a little earlier when it picked
5337 a router earlier in the list. If an attacker can recover this
5338 timing information (nontrivial but not proven to be impossible),
5339 they could learn some coarse-grained information about which relays
5340 a client was picking (middle nodes in particular are likelier to
5341 be affected than exits). The timing attack might be mitigated by
5342 other factors (see bug 6537 for some discussion), but it's best
5343 not to take chances. Fixes bug 6537; bugfix on 0.0.8rc1.
5346 Changes in version 0.2.3.20-rc - 2012-08-05
5347 Tor 0.2.3.20-rc is the third release candidate for the Tor 0.2.3.x
5348 series. It fixes a pair of code security bugs and a potential anonymity
5349 issue, updates our RPM spec files, and cleans up other smaller issues.
5352 - Avoid read-from-freed-memory and double-free bugs that could occur
5353 when a DNS request fails while launching it. Fixes bug 6480;
5354 bugfix on 0.2.0.1-alpha.
5355 - Avoid an uninitialized memory read when reading a vote or consensus
5356 document that has an unrecognized flavor name. This read could
5357 lead to a remote crash bug. Fixes bug 6530; bugfix on 0.2.2.6-alpha.
5358 - Try to leak less information about what relays a client is
5359 choosing to a side-channel attacker. Previously, a Tor client would
5360 stop iterating through the list of available relays as soon as it
5361 had chosen one, thus finishing a little earlier when it picked
5362 a router earlier in the list. If an attacker can recover this
5363 timing information (nontrivial but not proven to be impossible),
5364 they could learn some coarse-grained information about which relays
5365 a client was picking (middle nodes in particular are likelier to
5366 be affected than exits). The timing attack might be mitigated by
5367 other factors (see bug 6537 for some discussion), but it's best
5368 not to take chances. Fixes bug 6537; bugfix on 0.0.8rc1.
5371 - Try to make the warning when giving an obsolete SOCKSListenAddress
5372 a little more useful.
5373 - Terminate active server managed proxies if Tor stops being a
5374 relay. Addresses parts of bug 6274; bugfix on 0.2.3.6-alpha.
5375 - Provide a better error message about possible OSX Asciidoc failure
5376 reasons. Fixes bug 6436.
5377 - Warn when Tor is configured to use accounting in a way that can
5378 link a hidden service to some other hidden service or public
5379 address. Resolves ticket 6490.
5382 - Check return value of fputs() when writing authority certificate
5383 file. Fixes Coverity issue 709056; bugfix on 0.2.0.1-alpha.
5384 - Ignore ServerTransportPlugin lines when Tor is not configured as
5385 a relay. Fixes bug 6274; bugfix on 0.2.3.6-alpha.
5386 - When disabling guards for having too high a proportion of failed
5387 circuits, make sure to look at each guard. Fixes bug 6397; bugfix
5391 - Update our default RPM spec files to work with mock and rpmbuild
5392 on RHEL/Fedora. They have an updated set of dependencies and
5393 conflicts, a fix for an ancient typo when creating the "_tor"
5394 user, and better instructions. Thanks to Ondrej Mikle for the
5395 patch series. Fixes bug 6043.
5398 - Make it possible to set the TestingTorNetwork configuration
5399 option using AlternateDirAuthority and AlternateBridgeAuthority
5400 as an alternative to setting DirServer. Addresses ticket 6377.
5403 - Clarify the documentation for the Alternate*Authority options.
5405 - Fix some typos in the manpages. Patch from A. Costa. Fixes bug 6500.
5407 o Code simplification and refactoring:
5408 - Do not use SMARTLIST_FOREACH for any loop whose body exceeds
5409 10 lines. Also, don't nest them. Doing so in the past has
5410 led to hard-to-debug code. The new style is to use the
5411 SMARTLIST_FOREACH_{BEGIN,END} pair. Addresses issue 6400.
5414 Changes in version 0.2.3.19-rc - 2012-07-06
5415 Tor 0.2.3.19-rc is the second release candidate for the Tor 0.2.3.x
5416 series. It fixes the compile on Windows, reverts to a GeoIP database
5417 that isn't as broken, and fixes a flow control bug that has been around
5418 since the beginning of Tor.
5421 - Fix a bug handling SENDME cells on nonexistent streams that could
5422 result in bizarre window values. Report and patch contributed
5423 pseudonymously. Fixes part of bug 6271. This bug was introduced
5424 before the first Tor release, in svn commit r152.
5425 - Revert to the May 1 2012 Maxmind GeoLite Country database. In the
5426 June 2012 database, Maxmind marked many Tor relays as country "A1",
5427 which will cause risky behavior for clients that set EntryNodes
5428 or ExitNodes. Addresses bug 6334; bugfix on 0.2.3.17-beta.
5429 - Instead of ENOBUFS on Windows, say WSAENOBUFS. Fixes compilation
5430 on Windows. Fixes bug 6296; bugfix on 0.2.3.18-rc.
5433 - Fix wrong TCP port range in parse_port_range(). Fixes bug 6218;
5434 bugfix on 0.2.1.10-alpha.
5437 Changes in version 0.2.3.18-rc - 2012-06-28
5438 Tor 0.2.3.18-rc is the first release candidate for the Tor 0.2.3.x
5439 series. It fixes a few smaller bugs, but generally appears stable.
5440 Please test it and let us know whether it is!
5443 - Allow wildcarded mapaddress targets to be specified on the
5444 controlport. Partially fixes bug 6244; bugfix on 0.2.3.9-alpha.
5445 - Make our linker option detection code more robust against linkers
5446 such as on FreeBSD 8, where a bad combination of options completes
5447 successfully but makes an unrunnable binary. Fixes bug 6173;
5448 bugfix on 0.2.3.17-beta.
5450 o Minor bugfixes (on 0.2.2.x and earlier):
5451 - Avoid a false positive in the util/threads unit test by increasing
5452 the maximum timeout time. Fixes bug 6227; bugfix on 0.2.0.4-alpha.
5453 - Replace "Sending publish request" log messages with "Launching
5454 upload", so that they no longer confusingly imply that we're
5455 sending something to a directory we might not even be connected
5456 to yet. Fixes bug 3311; bugfix on 0.2.0.10-alpha.
5457 - Make sure to set *socket_error in all error cases in
5458 connection_connect(), so it can't produce a warning about
5459 errno being zero from errno_to_orconn_end_reason(). Bugfix on
5460 0.2.1.1-alpha; resolves ticket 6028.
5461 - Downgrade "Got a certificate, but we already have it" log messages
5462 from warning to info, except when we're a dirauth. Fixes bug 5238;
5463 bugfix on 0.2.1.7-alpha.
5464 - When checking for requested signatures on the latest consensus
5465 before serving it to a client, make sure to check the right
5466 consensus flavor. Bugfix on 0.2.2.6-alpha.
5467 - Downgrade "eventdns rejected address" message to LOG_PROTOCOL_WARN.
5468 Fixes bug 5932; bugfix on 0.2.2.7-alpha.
5470 o Minor bugfixes (on 0.2.3.x):
5471 - Make format_helper_exit_status() avoid unnecessary space padding
5472 and stop confusing log_from_pipe(). Fixes ticket 5557; bugfix
5474 - Downgrade a message about cleaning the microdescriptor cache to
5475 "info" from "notice". Fixes bug 6238; bugfix on 0.2.3.1-alpha.
5476 - Log a BUG message at severity INFO if we have a networkstatus with
5477 a missing entry for some microdescriptor. Continues on a patch
5479 - Improve the log message when a managed proxy fails to launch. Fixes
5480 bug 5099; bugfix on 0.2.3.6-alpha.
5481 - Don't do DNS lookups when parsing corrupted managed proxy protocol
5482 messages. Fixes bug 6226; bugfix on 0.2.3.6-alpha.
5483 - When formatting wildcarded address mappings for the controller,
5484 be sure to include "*." as appropriate. Partially fixes bug 6244;
5485 bugfix on 0.2.3.9-alpha.
5486 - Avoid a warning caused by using strcspn() from glibc with clang 3.0.
5487 Bugfix on 0.2.3.13-alpha.
5488 - Stop logging messages about running with circuit timeout learning
5489 enabled at severity LD_BUG. Fixes bug 6169; bugfix on 0.2.3.17-beta.
5490 - Disable a spurious warning about reading on a marked and flushing
5491 connection. We shouldn't be doing that, but apparently we
5492 sometimes do. Fixes bug 6203; bugfix on 0.2.3.17-beta.
5493 - Fix a bug that stopped AllowDotExit from working on addresses
5494 that had an entry in the DNS cache. Fixes bug 6211; bugfix on
5497 o Code simplification, refactoring, unit tests:
5498 - Move tor_gettimeofday_cached() into compat_libevent.c, and use
5499 Libevent's notion of cached time when possible.
5500 - Remove duplicate code for invoking getrlimit() from control.c.
5501 - Add a unit test for the environment_variable_names_equal function.
5504 - Document the --defaults-torrc option, and the new (in 0.2.3)
5505 semantics for overriding, extending, and clearing lists of
5506 options. Closes bug 4748.
5509 Changes in version 0.2.3.17-beta - 2012-06-15
5510 Tor 0.2.3.17-beta enables compiler and linker hardening by default,
5511 gets our TLS handshake back on track for being able to blend in with
5512 Firefox, fixes a big bug in 0.2.3.16-alpha that broke Tor's interaction
5513 with Vidalia, and otherwise continues to get us closer to a release
5517 - Enable gcc and ld hardening by default. Resolves ticket 5210.
5518 - Update TLS cipher list to match Firefox 8 and later. Resolves
5520 - Implement the client side of proposal 198: remove support for
5521 clients falsely claiming to support standard ciphersuites that
5522 they can actually provide. As of modern OpenSSL versions, it's not
5523 necessary to fake any standard ciphersuite, and doing so prevents
5524 us from using better ciphersuites in the future, since servers
5525 can't know whether an advertised ciphersuite is really supported or
5526 not. Some hosts -- notably, ones with very old versions of OpenSSL
5527 or where OpenSSL has been built with ECC disabled -- will stand
5528 out because of this change; TBB users should not be affected.
5531 - Change the default value for DynamicDHGroups (introduced in
5532 0.2.3.9-alpha) to 0. This feature can make Tor relays less
5533 identifiable by their use of the mod_ssl DH group, but at
5534 the cost of some usability (#4721) and bridge tracing (#6087)
5535 regressions. Resolves ticket 5598.
5536 - Send a CRLF at the end of each STATUS_* control protocol event. This
5537 bug tickled a bug in Vidalia which would make it freeze. Fixes
5538 bug 6094; bugfix on 0.2.3.16-alpha.
5541 - Disable writing on marked-for-close connections when they are
5542 blocked on bandwidth, to prevent busy-looping in Libevent. Fixes
5543 bug 5263; bugfix on 0.0.2pre13, where we first added a special
5544 case for flushing marked connections.
5545 - Detect SSL handshake even when the initial attempt to write the
5546 server hello fails. Fixes bug 4592; bugfix on 0.2.0.13-alpha.
5547 - Change the AllowDotExit rules so they should actually work.
5548 We now enforce AllowDotExit only immediately after receiving an
5549 address via SOCKS or DNSPort: other sources are free to provide
5550 .exit addresses after the resolution occurs. Fixes bug 3940;
5551 bugfix on 0.2.2.1-alpha.
5552 - Fix a (harmless) integer overflow in cell statistics reported by
5553 some fast relays. Fixes bug 5849; bugfix on 0.2.2.1-alpha.
5554 - Make sure circuitbuild.c checks LearnCircuitBuildTimeout in all the
5555 right places and never depends on the consensus parameters or
5556 computes adaptive timeouts when it is disabled. Fixes bug 5049;
5557 bugfix on 0.2.2.14-alpha.
5558 - When building Tor on Windows with -DUNICODE (not default), ensure
5559 that error messages, filenames, and DNS server names are always
5560 NUL-terminated when we convert them to a single-byte encoding.
5561 Fixes bug 5909; bugfix on 0.2.2.16-alpha.
5562 - Make Tor build correctly again with -DUNICODE -D_UNICODE defined.
5563 Fixes bug 6097; bugfix on 0.2.2.16-alpha.
5564 - Fix an edge case where TestingTorNetwork is set but the authorities
5565 and relays all have an uptime of zero, where the private Tor network
5566 could briefly lack support for hidden services. Fixes bug 3886;
5567 bugfix on 0.2.2.18-alpha.
5568 - Correct the manpage's descriptions for the default values of
5569 DirReqStatistics and ExtraInfoStatistics. Fixes bug 2865; bugfix
5571 - Fix the documentation for the --hush and --quiet command line
5572 options, which changed their behavior back in 0.2.3.3-alpha.
5573 - Fix compilation warning with clang 3.1. Fixes bug 6141; bugfix on
5577 - Rate-limit the "Weighted bandwidth is 0.000000" message, and add
5578 more information to it, so that we can track it down in case it
5579 returns again. Mitigates bug 5235.
5580 - Check CircuitBuildTimeout and LearnCircuitBuildTimeout in
5581 options_validate(); warn if LearnCircuitBuildTimeout is disabled and
5582 CircuitBuildTimeout is set unreasonably low. Resolves ticket 5452.
5583 - Warn the user when HTTPProxy, but no other proxy type, is
5584 configured. This can cause surprising behavior: it doesn't send
5585 all of Tor's traffic over the HTTPProxy -- it sends unencrypted
5586 directory traffic only. Resolves ticket 4663.
5587 - Issue a notice if a guard completes less than 40% of your circuits.
5588 Threshold is configurable by torrc option PathBiasNoticeRate and
5589 consensus parameter pb_noticepct. There is additional, off-by-
5590 default code to disable guards which fail too many circuits.
5591 Addresses ticket 5458.
5592 - Update to the June 6 2012 Maxmind GeoLite Country database.
5594 o Code simplifications and refactoring:
5595 - Remove validate_pluggable_transports_config(): its warning
5596 message is now handled by connection_or_connect().
5599 Changes in version 0.2.2.37 - 2012-06-06
5600 Tor 0.2.2.37 introduces a workaround for a critical renegotiation
5601 bug in OpenSSL 1.0.1 (where 20% of the Tor network can't talk to itself
5605 - Work around a bug in OpenSSL that broke renegotiation with TLS
5606 1.1 and TLS 1.2. Without this workaround, all attempts to speak
5607 the v2 Tor connection protocol when both sides were using OpenSSL
5608 1.0.1 would fail. Resolves ticket 6033.
5609 - When waiting for a client to renegotiate, don't allow it to add
5610 any bytes to the input buffer. This fixes a potential DoS issue.
5611 Fixes bugs 5934 and 6007; bugfix on 0.2.0.20-rc.
5612 - Fix an edge case where if we fetch or publish a hidden service
5613 descriptor, we might build a 4-hop circuit and then use that circuit
5614 for exiting afterwards -- even if the new last hop doesn't obey our
5615 ExitNodes config option. Fixes bug 5283; bugfix on 0.2.0.10-alpha.
5618 - Fix a build warning with Clang 3.1 related to our use of vasprintf.
5619 Fixes bug 5969. Bugfix on 0.2.2.11-alpha.
5622 - Tell GCC and Clang to check for any errors in format strings passed
5623 to the tor_v*(print|scan)f functions.
5626 Changes in version 0.2.3.16-alpha - 2012-06-05
5627 Tor 0.2.3.16-alpha introduces a workaround for a critical renegotiation
5628 bug in OpenSSL 1.0.1 (where 20% of the Tor network can't talk to itself
5629 currently). It also fixes a variety of smaller bugs and other cleanups
5630 that get us closer to a release candidate.
5632 o Major bugfixes (general):
5633 - Work around a bug in OpenSSL that broke renegotiation with TLS
5634 1.1 and TLS 1.2. Without this workaround, all attempts to speak
5635 the v2 Tor connection protocol when both sides were using OpenSSL
5636 1.0.1 would fail. Resolves ticket 6033.
5637 - When waiting for a client to renegotiate, don't allow it to add
5638 any bytes to the input buffer. This fixes a potential DoS issue.
5639 Fixes bugs 5934 and 6007; bugfix on 0.2.0.20-rc.
5640 - Pass correct OR address to managed proxies (like obfsproxy),
5641 even when ORListenAddress is used. Fixes bug 4865; bugfix on
5643 - The advertised platform of a router now includes only its operating
5644 system's name (e.g., "Linux", "Darwin", "Windows 7"), and not its
5645 service pack level (for Windows) or its CPU architecture (for Unix).
5646 We also no longer include the "git-XYZ" tag in the version. Resolves
5649 o Major bugfixes (clients):
5650 - If we are unable to find any exit that supports our predicted ports,
5651 stop calling them predicted, so that we don't loop and build
5652 hopeless circuits indefinitely. Fixes bug 3296; bugfix on 0.0.9pre6,
5653 which introduced predicted ports.
5654 - Fix an edge case where if we fetch or publish a hidden service
5655 descriptor, we might build a 4-hop circuit and then use that circuit
5656 for exiting afterwards -- even if the new last hop doesn't obey our
5657 ExitNodes config option. Fixes bug 5283; bugfix on 0.2.0.10-alpha.
5658 - Check at each new consensus whether our entry guards were picked
5659 long enough ago that we should rotate them. Previously, we only
5660 did this check at startup, which could lead to us holding a guard
5661 indefinitely. Fixes bug 5380; bugfix on 0.2.1.14-rc.
5662 - When fetching a bridge descriptor from a bridge authority,
5663 always do so anonymously, whether we have been able to open
5664 circuits or not. Partial fix for bug 1938; bugfix on 0.2.0.7-alpha.
5665 This behavior makes it *safer* to use UpdateBridgesFromAuthority,
5666 but we'll need to wait for bug 6010 before it's actually usable.
5668 o Major bugfixes (directory authorities):
5669 - When computing weight parameters, behave more robustly in the
5670 presence of a bad bwweightscale value. Previously, the authorities
5671 would crash if they agreed on a sufficiently broken weight_scale
5672 value: now, they use a reasonable default and carry on. Partial
5673 fix for 5786; bugfix on 0.2.2.17-alpha.
5674 - Check more thoroughly to prevent a rogue authority from
5675 double-voting on any consensus directory parameter. Previously,
5676 authorities would crash in this case if the total number of
5677 votes for any parameter exceeded the number of active voters,
5678 but would let it pass otherwise. Partial fix for bug 5786; bugfix
5682 - Rate-limit log messages when asked to connect anonymously to
5683 a private address. When these hit, they tended to hit fast and
5684 often. Also, don't bother trying to connect to addresses that we
5685 are sure will resolve to 127.0.0.1: getting 127.0.0.1 in a directory
5686 reply makes us think we have been lied to, even when the address the
5687 client tried to connect to was "localhost." Resolves ticket 2822.
5688 - Allow packagers to insert an extra string in server descriptor
5689 platform lines by setting the preprocessor variable TOR_BUILD_TAG.
5690 Resolves the rest of ticket 2988.
5691 - Raise the threshold of server descriptors needed (75%) and exit
5692 server descriptors needed (50%) before we will declare ourselves
5693 bootstrapped. This will make clients start building circuits a
5694 little later, but makes the initially constructed circuits less
5695 skewed and less in conflict with further directory fetches. Fixes
5697 - Close any connection that sends unrecognized junk before the
5698 handshake. Solves an issue noted in bug 4369.
5699 - Improve log messages about managed transports. Resolves ticket 5070.
5700 - Tag a bridge's descriptor as "never to be sent unencrypted".
5701 This shouldn't matter, since bridges don't open non-anonymous
5702 connections to the bridge authority and don't allow unencrypted
5703 directory connections from clients, but we might as well make
5704 sure. Closes bug 5139.
5705 - Expose our view of whether we have gone dormant to the controller,
5706 via a new "GETINFO dormant" value. Torbutton and other controllers
5707 can use this to avoid doing periodic requests through Tor while
5708 it's dormant (bug 4718). Fixes bug 5954.
5709 - Tell GCC and Clang to check for any errors in format strings passed
5710 to the tor_v*(print|scan)f functions.
5711 - Update to the May 1 2012 Maxmind GeoLite Country database.
5713 o Minor bugfixes (already included in 0.2.2.36):
5714 - Reject out-of-range times like 23:59:61 in parse_rfc1123_time().
5715 Fixes bug 5346; bugfix on 0.0.8pre3.
5716 - Correct parsing of certain date types in parse_http_time().
5717 Without this patch, If-Modified-Since would behave
5718 incorrectly. Fixes bug 5346; bugfix on 0.2.0.2-alpha. Patch from
5719 Esteban Manchado Velázques.
5720 - Make our number-parsing functions always treat too-large values
5721 as an error, even when those values exceed the width of the
5722 underlying type. Previously, if the caller provided these
5723 functions with minima or maxima set to the extreme values of the
5724 underlying integer type, these functions would return those
5725 values on overflow rather than treating overflow as an error.
5726 Fixes part of bug 5786; bugfix on 0.0.9.
5727 - If we hit the error case where routerlist_insert() replaces an
5728 existing (old) server descriptor, make sure to remove that
5729 server descriptor from the old_routers list. Fix related to bug
5730 1776. Bugfix on 0.2.2.18-alpha.
5731 - Clarify the behavior of MaxCircuitDirtiness with hidden service
5732 circuits. Fixes issue 5259.
5734 o Minor bugfixes (coding cleanup, on 0.2.2.x and earlier):
5735 - Prevent a null-pointer dereference when receiving a data cell
5736 for a nonexistent stream when the circuit in question has an
5737 empty deliver window. We don't believe this is triggerable,
5738 since we don't currently allow deliver windows to become empty,
5739 but the logic is tricky enough that it's better to make the code
5740 robust. Fixes bug 5541; bugfix on 0.0.2pre14.
5741 - Fix a memory leak when trying to launch a DNS request when the
5742 network is disabled or the nameservers are unconfigurable. Fixes
5743 bug 5916; bugfix on Tor 0.1.2.1-alpha (for the unconfigurable
5744 nameserver case) and on 0.2.3.9-alpha (for the DisableNetwork case).
5745 - Don't hold a Windows file handle open for every file mapping;
5746 the file mapping handle is sufficient. Fixes bug 5951; bugfix on
5748 - Avoid O(n^2) performance characteristics when parsing a large
5749 extrainfo cache. Fixes bug 5828; bugfix on 0.2.0.1-alpha.
5750 - Format more doubles with %f, not %lf. Patch from grarpamp to make
5751 Tor build correctly on older BSDs again. Fixes bug 3894; bugfix on
5753 - Make our replacement implementation of strtok_r() compatible with
5754 the standard behavior of strtok_r(). Patch by nils. Fixes bug 5091;
5755 bugfix on 0.2.2.1-alpha.
5756 - Fix a NULL-pointer dereference on a badly formed
5757 SETCIRCUITPURPOSE command. Found by mikeyc. Fixes bug 5796;
5758 bugfix on 0.2.2.9-alpha.
5759 - Fix a build warning with Clang 3.1 related to our use of vasprintf.
5760 Fixes bug 5969. Bugfix on 0.2.2.11-alpha.
5761 - Defensively refactor rend_mid_rendezvous() so that protocol
5762 violations and length checks happen in the beginning. Fixes
5764 - Set _WIN32_WINNT to 0x0501 consistently throughout the code, so
5765 that IPv6 stuff will compile on MSVC, and compilation issues
5766 will be easier to track down. Fixes bug 5861.
5768 o Minor bugfixes (correctness, on 0.2.2.x and earlier):
5769 - Exit nodes now correctly report EADDRINUSE and EADDRNOTAVAIL as
5770 resource exhaustion, so that clients can adjust their load to
5771 try other exits. Fixes bug 4710; bugfix on 0.1.0.1-rc, which
5772 started using END_STREAM_REASON_RESOURCELIMIT.
5773 - Don't check for whether the address we're using for outbound
5774 connections has changed until after the outbound connection has
5775 completed. On Windows, getsockname() doesn't succeed until the
5776 connection is finished. Fixes bug 5374; bugfix on 0.1.1.14-alpha.
5777 - If the configuration tries to set MyFamily on a bridge, refuse to
5778 do so, and warn about the security implications. Fixes bug 4657;
5779 bugfix on 0.2.0.3-alpha.
5780 - If the client fails to set a reasonable set of ciphersuites
5781 during its v2 handshake renegotiation, allow the renegotiation to
5782 continue nevertheless (i.e. send all the required certificates).
5783 Fixes bug 4591; bugfix on 0.2.0.20-rc.
5784 - When we receive a SIGHUP and the controller __ReloadTorrcOnSIGHUP
5785 option is set to 0 (which Vidalia version 0.2.16 now does when
5786 a SAVECONF attempt fails), perform other actions that SIGHUP
5787 usually causes (like reopening the logs). Fixes bug 5095; bugfix
5789 - If we fail to write a microdescriptor to the disk cache, do not
5790 continue replacing the old microdescriptor file. Fixes bug 2954;
5791 bugfix on 0.2.2.6-alpha.
5792 - Exit nodes don't need to fetch certificates for authorities that
5793 they don't recognize; only directory authorities, bridges,
5794 and caches need to do that. Fixes part of bug 2297; bugfix on
5796 - Correctly handle checking the permissions on the parent
5797 directory of a control socket in the root directory. Bug found
5798 by Esteban Manchado Velázquez. Fixes bug 5089; bugfix on Tor
5800 - When told to add a bridge with the same digest as a preexisting
5801 bridge but a different addr:port, change the addr:port as
5802 requested. Previously we would not notice the change. Fixes half
5803 of bug 5603; fix on 0.2.2.26-beta.
5804 - End AUTHCHALLENGE error messages (in the control protocol) with
5805 a CRLF. Fixes bug 5760; bugfix on 0.2.2.36 and 0.2.3.13-alpha.
5807 o Minor bugfixes (on 0.2.3.x):
5808 - Turn an assertion (that the number of handshakes received as a
5809 server is not < 1) into a warning. Fixes bug 4873; bugfix on
5811 - Format IPv4 addresses correctly in ADDRMAP events. (Previously,
5812 we had reversed them when the answer was cached.) Fixes bug
5813 5723; bugfix on 0.2.3.1-alpha.
5814 - Work correctly on Linux systems with accept4 support advertised in
5815 their headers, but without accept4 support in the kernel. Fix
5816 by murb. Fixes bug 5762; bugfix on 0.2.3.1-alpha.
5817 - When told to add a bridge with the same addr:port as a preexisting
5818 bridge but a different transport, change the transport as
5819 requested. Previously we would not notice the change. Fixes half
5820 of bug 5603; fix on 0.2.3.2-alpha.
5821 - Avoid a "double-reply" warning when replying to a SOCKS request
5822 with a parse error. Patch from Fabian Keil. Fixes bug 4108;
5823 bugfix on 0.2.3.4-alpha.
5824 - Fix a bug where a bridge authority crashes if it has seen no
5825 directory requests when it's time to write statistics to disk.
5826 Fixes bug 5891; bugfix on 0.2.3.6-alpha. Also fixes bug 5508 in
5828 - Don't try to open non-control listeners when DisableNetwork is set.
5829 Previously, we'd open all listeners, then immediately close them.
5830 Fixes bug 5604; bugfix on 0.2.3.9-alpha.
5831 - Don't abort the managed proxy protocol if the managed proxy
5832 sends us an unrecognized line; ignore it instead. Fixes bug
5833 5910; bugfix on 0.2.3.9-alpha.
5834 - Fix a compile warning in crypto.c when compiling with clang 3.1.
5835 Fixes bug 5969, bugfix on 0.2.3.9-alpha.
5836 - Fix a compilation issue on GNU Hurd, which doesn't have PATH_MAX.
5837 Fixes bug 5355; bugfix on 0.2.3.11-alpha.
5838 - Remove bogus definition of "_WIN32" from src/win32/orconfig.h, to
5839 unbreak the MSVC build. Fixes bug 5858; bugfix on 0.2.3.12-alpha.
5840 - Resolve numerous small warnings and build issues with MSVC. Resolves
5843 o Documentation fixes:
5844 - Improve the manual's documentation for the NT Service command-line
5845 options. Addresses ticket 3964.
5846 - Clarify SessionGroup documentation slightly; resolves ticket 5437.
5847 - Document the changes to the ORPort and DirPort options, and the
5848 fact that {OR/Dir}ListenAddress is now unnecessary (and
5849 therefore deprecated). Resolves ticket 5597.
5852 - Remove the torrc.bridge file: we don't use it for anything, and
5853 it had become badly desynchronized from torrc.sample. Resolves
5857 Changes in version 0.2.2.36 - 2012-05-24
5858 Tor 0.2.2.36 updates the addresses for two of the eight directory
5859 authorities, fixes some potential anonymity and security issues,
5860 and fixes several crash bugs.
5862 Tor 0.2.1.x has reached its end-of-life. Those Tor versions have many
5863 known flaws, and nobody should be using them. You should upgrade. If
5864 you're using a Linux or BSD and its packages are obsolete, stop using
5865 those packages and upgrade anyway.
5867 o Directory authority changes:
5868 - Change IP address for maatuska (v3 directory authority).
5869 - Change IP address for ides (v3 directory authority), and rename
5873 - When building or running with any version of OpenSSL earlier
5874 than 0.9.8s or 1.0.0f, disable SSLv3 support. These OpenSSL
5875 versions have a bug (CVE-2011-4576) in which their block cipher
5876 padding includes uninitialized data, potentially leaking sensitive
5877 information to any peer with whom they make a SSLv3 connection. Tor
5878 does not use SSL v3 by default, but a hostile client or server
5879 could force an SSLv3 connection in order to gain information that
5880 they shouldn't have been able to get. The best solution here is to
5881 upgrade to OpenSSL 0.9.8s or 1.0.0f (or later). But when building
5882 or running with a non-upgraded OpenSSL, we disable SSLv3 entirely
5883 to make sure that the bug can't happen.
5884 - Never use a bridge or a controller-supplied node as an exit, even
5885 if its exit policy allows it. Found by wanoskarnet. Fixes bug
5886 5342. Bugfix on 0.1.1.15-rc (for controller-purpose descriptors)
5887 and 0.2.0.3-alpha (for bridge-purpose descriptors).
5888 - Only build circuits if we have a sufficient threshold of the total
5889 descriptors that are marked in the consensus with the "Exit"
5890 flag. This mitigates an attack proposed by wanoskarnet, in which
5891 all of a client's bridges collude to restrict the exit nodes that
5892 the client knows about. Fixes bug 5343.
5893 - Provide controllers with a safer way to implement the cookie
5894 authentication mechanism. With the old method, if another locally
5895 running program could convince a controller that it was the Tor
5896 process, then that program could trick the controller into telling
5897 it the contents of an arbitrary 32-byte file. The new "SAFECOOKIE"
5898 authentication method uses a challenge-response approach to prevent
5899 this attack. Fixes bug 5185; implements proposal 193.
5902 - Avoid logging uninitialized data when unable to decode a hidden
5903 service descriptor cookie. Fixes bug 5647; bugfix on 0.2.1.5-alpha.
5904 - Avoid a client-side assertion failure when receiving an INTRODUCE2
5905 cell on a general purpose circuit. Fixes bug 5644; bugfix on
5907 - Fix builds when the path to sed, openssl, or sha1sum contains
5908 spaces, which is pretty common on Windows. Fixes bug 5065; bugfix
5910 - Correct our replacements for the timeradd() and timersub() functions
5911 on platforms that lack them (for example, Windows). The timersub()
5912 function is used when expiring circuits, while timeradd() is
5913 currently unused. Bug report and patch by Vektor. Fixes bug 4778;
5914 bugfix on 0.2.2.24-alpha.
5915 - Fix the SOCKET_OK test that we use to tell when socket
5916 creation fails so that it works on Win64. Fixes part of bug 4533;
5917 bugfix on 0.2.2.29-beta. Bug found by wanoskarnet.
5920 - Reject out-of-range times like 23:59:61 in parse_rfc1123_time().
5921 Fixes bug 5346; bugfix on 0.0.8pre3.
5922 - Make our number-parsing functions always treat too-large values
5923 as an error, even when those values exceed the width of the
5924 underlying type. Previously, if the caller provided these
5925 functions with minima or maxima set to the extreme values of the
5926 underlying integer type, these functions would return those
5927 values on overflow rather than treating overflow as an error.
5928 Fixes part of bug 5786; bugfix on 0.0.9.
5929 - Older Linux kernels erroneously respond to strange nmap behavior
5930 by having accept() return successfully with a zero-length
5931 socket. When this happens, just close the connection. Previously,
5932 we would try harder to learn the remote address: but there was
5933 no such remote address to learn, and our method for trying to
5934 learn it was incorrect. Fixes bugs 1240, 4745, and 4747. Bugfix
5935 on 0.1.0.3-rc. Reported and diagnosed by "r1eo".
5936 - Correct parsing of certain date types in parse_http_time().
5937 Without this patch, If-Modified-Since would behave
5938 incorrectly. Fixes bug 5346; bugfix on 0.2.0.2-alpha. Patch from
5939 Esteban Manchado Velázques.
5940 - Change the BridgePassword feature (part of the "bridge community"
5941 design, which is not yet implemented) to use a time-independent
5942 comparison. The old behavior might have allowed an adversary
5943 to use timing to guess the BridgePassword value. Fixes bug 5543;
5944 bugfix on 0.2.0.14-alpha.
5945 - Detect and reject certain misformed escape sequences in
5946 configuration values. Previously, these values would cause us
5947 to crash if received in a torrc file or over an authenticated
5948 control port. Bug found by Esteban Manchado Velázquez, and
5949 independently by Robert Connolly from Matta Consulting who further
5950 noted that it allows a post-authentication heap overflow. Patch
5951 by Alexander Schrijver. Fixes bugs 5090 and 5402 (CVE 2012-1668);
5952 bugfix on 0.2.0.16-alpha.
5953 - Fix a compile warning when using the --enable-openbsd-malloc
5954 configure option. Fixes bug 5340; bugfix on 0.2.0.20-rc.
5955 - During configure, detect when we're building with clang version
5956 3.0 or lower and disable the -Wnormalized=id and -Woverride-init
5957 CFLAGS. clang doesn't support them yet.
5958 - When sending an HTTP/1.1 proxy request, include a Host header.
5959 Fixes bug 5593; bugfix on 0.2.2.1-alpha.
5960 - Fix a NULL-pointer dereference on a badly formed SETCIRCUITPURPOSE
5961 command. Found by mikeyc. Fixes bug 5796; bugfix on 0.2.2.9-alpha.
5962 - If we hit the error case where routerlist_insert() replaces an
5963 existing (old) server descriptor, make sure to remove that
5964 server descriptor from the old_routers list. Fix related to bug
5965 1776. Bugfix on 0.2.2.18-alpha.
5967 o Minor bugfixes (documentation and log messages):
5968 - Fix a typo in a log message in rend_service_rendezvous_has_opened().
5969 Fixes bug 4856; bugfix on Tor 0.0.6.
5970 - Update "ClientOnly" man page entry to explain that there isn't
5971 really any point to messing with it. Resolves ticket 5005.
5972 - Document the GiveGuardFlagTo_CVE_2011_2768_VulnerableRelays
5973 directory authority option (introduced in Tor 0.2.2.34).
5974 - Downgrade the "We're missing a certificate" message from notice
5975 to info: people kept mistaking it for a real problem, whereas it
5976 is seldom the problem even when we are failing to bootstrap. Fixes
5977 bug 5067; bugfix on 0.2.0.10-alpha.
5978 - Correctly spell "connect" in a log message on failure to create a
5979 controlsocket. Fixes bug 4803; bugfix on 0.2.2.26-beta.
5980 - Clarify the behavior of MaxCircuitDirtiness with hidden service
5981 circuits. Fixes issue 5259.
5984 - Directory authorities now reject versions of Tor older than
5985 0.2.1.30, and Tor versions between 0.2.2.1-alpha and 0.2.2.20-alpha
5986 inclusive. These versions accounted for only a small fraction of
5987 the Tor network, and have numerous known security issues. Resolves
5989 - Update to the May 1 2012 Maxmind GeoLite Country database.
5992 - When sending or relaying a RELAY_EARLY cell, we used to convert
5993 it to a RELAY cell if the connection was using the v1 link
5994 protocol. This was a workaround for older versions of Tor, which
5995 didn't handle RELAY_EARLY cells properly. Now that all supported
5996 versions can handle RELAY_EARLY cells, and now that we're enforcing
5997 the "no RELAY_EXTEND commands except in RELAY_EARLY cells" rule,
5998 remove this workaround. Addresses bug 4786.
6001 Changes in version 0.2.3.15-alpha - 2012-04-30
6002 Tor 0.2.3.15-alpha fixes a variety of smaller bugs, including making
6003 the development branch build on Windows again.
6005 o Minor bugfixes (on 0.2.2.x and earlier):
6006 - Make sure that there are no unhandled pending TLS errors before
6007 reading from a TLS stream. We had checks in 0.1.0.3-rc, but
6008 lost them in 0.1.0.5-rc when we refactored read_to_buf_tls().
6009 Bugfix on 0.1.0.5-rc; fixes bug 4528.
6010 - Fix an assert that directory authorities could trigger on sighup
6011 during some configuration state transitions. We now don't treat
6012 it as a fatal error when the new descriptor we just generated in
6013 init_keys() isn't accepted. Fixes bug 4438; bugfix on 0.2.1.9-alpha.
6014 - After we pick a directory mirror, we would refuse to use it if
6015 it's in our ExcludeExitNodes list, resulting in mysterious failures
6016 to bootstrap for people who just wanted to avoid exiting from
6017 certain locations. Fixes bug 5623; bugfix on 0.2.2.25-alpha.
6018 - When building with --enable-static-tor on OpenBSD, do not
6019 erroneously attempt to link -lrt. Fixes bug 5103.
6021 o Minor bugfixes (on 0.2.3.x):
6022 - When Tor is built with kernel headers from a recent (last few
6023 years) Linux kernel, do not fail to run on older (pre-2.6.28
6024 Linux kernels). Fixes bug 5112; bugfix on 0.2.3.1-alpha.
6025 - Fix cross-compilation issues with mingw. Bugfixes on 0.2.3.6-alpha
6027 - Fix compilation with miniupnpc version 1.6; patch from
6028 Anthony G. Basile. Fixes bug 5434; bugfix on 0.2.3.12-alpha.
6029 - Fix compilation with MSVC, which had defined MS_WINDOWS. Bugfix
6030 on 0.2.3.13-alpha; found and fixed by Gisle Vanem.
6031 - Fix compilation on platforms without unistd.h, or where environ
6032 is defined in stdlib.h. Fixes bug 5704; bugfix on 0.2.3.13-alpha.
6035 - Directory authorities are now a little more lenient at accepting
6036 older router descriptors, or newer router descriptors that don't
6037 make big changes. This should help ameliorate past and future
6038 issues where routers think they have uploaded valid descriptors,
6039 but the authorities don't think so. Fix for ticket 2479.
6040 - Make the code that clients use to detect an address change be
6041 IPv6-aware, so that it won't fill clients' logs with error
6042 messages when trying to get the IPv4 address of an IPv6
6043 connection. Implements ticket 5537.
6046 - Remove the GiveGuardFlagTo_CVE_2011_2768_VulnerableRelays option;
6047 authorities needed to use it for a while to keep the network working
6048 as people upgraded to 0.2.1.31, 0.2.2.34, or 0.2.3.6-alpha, but
6049 that was six months ago. As of now, it should no longer be needed
6053 Changes in version 0.2.3.14-alpha - 2012-04-23
6054 Tor 0.2.3.14-alpha fixes yet more bugs to get us closer to a release
6055 candidate. It also dramatically speeds up AES: fast relays should
6056 consider switching to the newer OpenSSL library.
6058 o Directory authority changes:
6059 - Change IP address for ides (v3 directory authority), and rename
6063 - Avoid logging uninitialized data when unable to decode a hidden
6064 service descriptor cookie. Fixes bug 5647; bugfix on 0.2.1.5-alpha.
6065 - Avoid a client-side assertion failure when receiving an INTRODUCE2
6066 cell on a general purpose circuit. Fixes bug 5644; bugfix on
6068 - If authorities are unable to get a v2 consensus document from other
6069 directory authorities, they no longer fall back to fetching
6070 them from regular directory caches. Fixes bug 5635; bugfix on
6071 0.2.2.26-beta, where routers stopped downloading v2 consensus
6073 - When we start a Tor client with a normal consensus already cached,
6074 be willing to download a microdescriptor consensus. Fixes bug 4011;
6075 fix on 0.2.3.1-alpha.
6077 o Major features (performance):
6078 - When built to use OpenSSL 1.0.1, and built for an x86 or x86_64
6079 instruction set, take advantage of OpenSSL's AESNI, bitsliced, or
6080 vectorized AES implementations as appropriate. These can be much,
6081 much faster than other AES implementations.
6083 o Minor bugfixes (0.2.2.x and earlier):
6084 - Don't launch more than 10 service-side introduction-point circuits
6085 for a hidden service in five minutes. Previously, we would consider
6086 launching more introduction-point circuits if at least one second
6087 had passed without any introduction-point circuits failing. Fixes
6088 bug 4607; bugfix on 0.0.7pre1.
6089 - Change the BridgePassword feature (part of the "bridge community"
6090 design, which is not yet implemented) to use a time-independent
6091 comparison. The old behavior might have allowed an adversary
6092 to use timing to guess the BridgePassword value. Fixes bug 5543;
6093 bugfix on 0.2.0.14-alpha.
6094 - Enforce correct return behavior of tor_vsscanf() when the '%%'
6095 pattern is used. Fixes bug 5558. Bugfix on 0.2.1.13.
6096 - When sending an HTTP/1.1 proxy request, include a Host header.
6097 Fixes bug 5593; bugfix on 0.2.2.1-alpha.
6098 - Don't log that we have "decided to publish new relay descriptor"
6099 unless we are actually publishing a descriptor. Fixes bug 3942;
6100 bugfix on 0.2.2.28-beta.
6102 o Minor bugfixes (0.2.3.x):
6103 - Fix a bug where a bridge authority crashes (on a failed assert)
6104 if it has seen no directory requests when it's time to write
6105 statistics to disk. Fixes bug 5508. Bugfix on 0.2.3.6-alpha.
6106 - Fix bug stomping on ORPort option NoListen and ignoring option
6107 NoAdvertise. Fixes bug 5151; bugfix on 0.2.3.9-alpha.
6108 - In the testsuite, provide a large enough buffer in the tor_sscanf
6109 unit test. Otherwise we'd overrun that buffer and crash during
6110 the unit tests. Found by weasel. Fixes bug 5449; bugfix on
6112 - Make sure we create the keys directory if it doesn't exist and we're
6113 about to store the dynamic Diffie-Hellman parameters. Fixes bug
6114 5572; bugfix on 0.2.3.13-alpha.
6115 - Fix a small memory leak when trying to decode incorrect base16
6116 authenticator during SAFECOOKIE authentication. Found by
6117 Coverity Scan. Fixes CID 507. Bugfix on 0.2.3.13-alpha.
6120 - Add more information to a log statement that might help track down
6121 bug 4091. If you're seeing "Bug: tor_addr_is_internal() called with a
6122 non-IP address" messages (or any Bug messages, for that matter!),
6123 please let us know about it.
6124 - Relays now understand an IPv6 address when they get one from a
6125 directory server. Resolves ticket 4875.
6126 - Resolve IPv6 addresses in bridge and entry statistics to country
6127 code "??" which means we at least count them. Resolves ticket 5053;
6128 improves on 0.2.3.9-alpha.
6129 - Update to the April 3 2012 Maxmind GeoLite Country database.
6130 - Begin a doc/state-contents.txt file to explain the contents of
6131 the Tor state file. Fixes bug 2987.
6133 o Default torrc changes:
6134 - Stop listing "socksport 9050" in torrc.sample. We open a socks
6135 port on 9050 by default anyway, so this should not change anything
6137 - Stop mentioning the deprecated *ListenAddress options in
6138 torrc.sample. Fixes bug 5438.
6139 - Document unit of bandwidth related options in sample torrc.
6143 - The "torify" script no longer supports the "tsocks" socksifier
6144 tool, since tsocks doesn't support DNS and UDP right for Tor.
6145 Everyone should be using torsocks instead. Fixes bugs 3530 and
6146 5180. Based on a patch by "ugh".
6149 - Change the symmetric cipher interface so that creating and
6150 initializing a stream cipher are no longer separate functions.
6151 - Remove all internal support for unpadded RSA. We never used it, and
6152 it would be a bad idea to start.
6155 Changes in version 0.2.3.13-alpha - 2012-03-26
6156 Tor 0.2.3.13-alpha fixes a variety of stability and correctness bugs
6157 in managed pluggable transports, as well as providing other cleanups
6158 that get us closer to a release candidate.
6160 o Directory authority changes:
6161 - Change IP address for maatuska (v3 directory authority).
6164 - Provide controllers with a safer way to implement the cookie
6165 authentication mechanism. With the old method, if another locally
6166 running program could convince a controller that it was the Tor
6167 process, then that program could trick the controller into telling
6168 it the contents of an arbitrary 32-byte file. The new "SAFECOOKIE"
6169 authentication method uses a challenge-response approach to prevent
6170 this attack. Fixes bug 5185, implements proposal 193.
6171 - Never use a bridge or a controller-supplied node as an exit, even
6172 if its exit policy allows it. Found by wanoskarnet. Fixes bug
6173 5342. Bugfix on 0.1.1.15-rc (for controller-purpose descriptors)
6174 and 0.2.0.3-alpha (for bridge-purpose descriptors).
6175 - Only build circuits if we have a sufficient threshold of the total
6176 descriptors that are marked in the consensus with the "Exit"
6177 flag. This mitigates an attack proposed by wanoskarnet, in which
6178 all of a client's bridges collude to restrict the exit nodes that
6179 the client knows about. Fixes bug 5343.
6181 o Major bugfixes (on Tor 0.2.3.x):
6182 - Avoid an assert when managed proxies like obfsproxy are configured,
6183 and we receive HUP signals or setconf attempts too rapidly. This
6184 situation happens most commonly when Vidalia tries to attach to
6185 Tor or tries to configure the Tor it's attached to. Fixes bug 5084;
6186 bugfix on 0.2.3.6-alpha.
6187 - Fix a relay-side pluggable transports bug where managed proxies were
6188 unreachable from the Internet, because Tor asked them to bind on
6189 localhost. Fixes bug 4725; bugfix on 0.2.3.9-alpha.
6190 - Stop discarding command-line arguments when TestingTorNetwork
6191 is set. Discovered by Kevin Bauer. Fixes bug 5373; bugfix on
6192 0.2.3.9-alpha, where task 4552 added support for two layers of
6194 - Resume allowing the unit tests to run in gdb. This was accidentally
6195 made impossible when the DisableDebuggerAttachment option was
6196 introduced. Fixes bug 5448; bugfix on 0.2.3.9-alpha.
6197 - Resume building with nat-pmp support. Fixes bug 4955; bugfix on
6198 0.2.3.11-alpha. Reported by Anthony G. Basile.
6200 o Minor bugfixes (on 0.2.2.x and earlier):
6201 - Ensure we don't cannibalize circuits that are longer than three hops
6202 already, so we don't end up making circuits with 5 or more
6203 hops. Patch contributed by wanoskarnet. Fixes bug 5231; bugfix on
6204 0.1.0.1-rc which introduced cannibalization.
6205 - Detect and reject certain misformed escape sequences in
6206 configuration values. Previously, these values would cause us
6207 to crash if received in a torrc file or over an authenticated
6208 control port. Bug found by Esteban Manchado Velázquez, and
6209 independently by Robert Connolly from Matta Consulting who further
6210 noted that it allows a post-authentication heap overflow. Patch
6211 by Alexander Schrijver. Fixes bugs 5090 and 5402 (CVE 2012-1668);
6212 bugfix on 0.2.0.16-alpha.
6213 - Fix a compile warning when using the --enable-openbsd-malloc
6214 configure option. Fixes bug 5340; bugfix on 0.2.0.20-rc.
6215 - Directory caches no longer refuse to clean out descriptors because
6216 of missing v2 networkstatus documents, unless they're configured
6217 to retrieve v2 networkstatus documents. Fixes bug 4838; bugfix on
6218 0.2.2.26-beta. Patch by Daniel Bryg.
6219 - Update to the latest version of the tinytest unit testing framework.
6220 This includes a couple of bugfixes that can be relevant for
6221 running forked unit tests on Windows, and removes all reserved
6224 o Minor bugfixes (on 0.2.3.x):
6225 - On a failed pipe() call, don't leak file descriptors. Fixes bug
6226 4296; bugfix on 0.2.3.1-alpha.
6227 - Spec conformance: on a v3 handshake, do not send a NETINFO cell
6228 until after we have received a CERTS cell. Fixes bug 4361; bugfix
6229 on 0.2.3.6-alpha. Patch by "frosty".
6230 - When binding to an IPv6 address, set the IPV6_V6ONLY socket
6231 option, so that the IP stack doesn't decide to use it for IPv4
6232 too. Fixes bug 4760; bugfix on 0.2.3.9-alpha.
6233 - Ensure that variables set in Tor's environment cannot override
6234 environment variables that Tor passes to a managed
6235 pluggable-transport proxy. Previously, Tor would pass every
6236 variable in its environment to managed proxies along with the new
6237 ones, in such a way that on many operating systems, the inherited
6238 environment variables would override those which Tor tried to
6239 explicitly set. Bugfix on 0.2.3.12-alpha for most Unixoid systems;
6240 bugfix on 0.2.3.9-alpha for Windows.
6243 - A wide variety of new unit tests by Esteban Manchado Velázquez.
6244 - Shorten links in the tor-exit-notice file. Patch by Christian Kujau.
6245 - Update to the March 6 2012 Maxmind GeoLite Country database.
6248 Changes in version 0.2.3.12-alpha - 2012-02-13
6249 Tor 0.2.3.12-alpha lets fast exit relays scale better, allows clients
6250 to use bridges that run Tor 0.2.2.x, and resolves several big bugs
6251 when Tor is configured to use a pluggable transport like obfsproxy.
6254 - Fix builds when the path to sed, openssl, or sha1sum contains
6255 spaces, which is pretty common on Windows. Fixes bug 5065; bugfix
6257 - Set the SO_REUSEADDR socket option before we call bind() on outgoing
6258 connections. This change should allow busy exit relays to stop
6259 running out of available sockets as quickly. Fixes bug 4950;
6260 bugfix on 0.2.2.26-beta.
6261 - Allow 0.2.3.x clients to use 0.2.2.x bridges. Previously the client
6262 would ask the bridge for microdescriptors, which are only supported
6263 in 0.2.3.x, and then fail to bootstrap when it didn't get the
6264 answers it wanted. Fixes bug 4013; bugfix on 0.2.3.2-alpha.
6265 - Properly set up obfsproxy's environment when in managed mode. The
6266 Tor Browser Bundle needs LD_LIBRARY_PATH to be passed to obfsproxy,
6267 and when you run your Tor as a daemon, there's no HOME. Fixes bugs
6268 5076 and 5082; bugfix on 0.2.3.6-alpha.
6271 - Use the dead_strip option when building Tor on OS X. This reduces
6272 binary size by almost 19% when linking openssl and libevent
6273 statically, which we do for Tor Browser Bundle.
6274 - Fix broken URLs in the sample torrc file, and tell readers about
6275 the OutboundBindAddress, ExitPolicyRejectPrivate, and
6276 PublishServerDescriptor options. Addresses bug 4652.
6277 - Update to the February 7 2012 Maxmind GeoLite Country database.
6280 - Downgrade the "We're missing a certificate" message from notice
6281 to info: people kept mistaking it for a real problem, whereas it
6282 is seldom the problem even when we are failing to bootstrap. Fixes
6283 bug 5067; bugfix on 0.2.0.10-alpha.
6284 - Don't put "TOR_PT_EXTENDED_SERVER_PORT=127.0.0.1:4200" in a
6285 managed pluggable transport server proxy's environment.
6286 Previously, we would put it there, even though Tor doesn't
6287 implement an 'extended server port' yet, and even though Tor
6288 almost certainly isn't listening at that address. For now, we set
6289 it to an empty string to avoid crashing older obfsproxies. Bugfix
6291 - Log the heartbeat message every HeartbeatPeriod seconds, not every
6292 HeartbeatPeriod + 1 seconds. Fixes bug 4942; bugfix on
6293 0.2.3.1-alpha. Bug reported by Scott Bennett.
6294 - Calculate absolute paths correctly on Windows. Fixes bug 4973;
6295 bugfix on 0.2.3.11-alpha.
6296 - Update "ClientOnly" man page entry to explain that there isn't
6297 really any point to messing with it. Resolves ticket 5005.
6298 - Use the correct CVE number for CVE-2011-4576 in our comments and
6299 log messages. Found by "fermenthor". Resolves bug 5066; bugfix on
6302 o Code simplifications and refactoring:
6303 - Use the _WIN32 macro throughout our code to detect Windows.
6304 (Previously we had used the obsolete 'WIN32' and the idiosyncratic
6308 Changes in version 0.2.3.11-alpha - 2012-01-22
6309 Tor 0.2.3.11-alpha marks feature-freeze for the 0.2.3 tree. It deploys
6310 the last step of the plan to limit maximum circuit length, includes
6311 a wide variety of hidden service performance and correctness fixes,
6312 works around an OpenSSL security flaw if your distro is too stubborn
6313 to upgrade, and fixes a bunch of smaller issues.
6316 - Now that Tor 0.2.0.x is completely deprecated, enable the final
6317 part of "Proposal 110: Avoiding infinite length circuits" by
6318 refusing all circuit-extend requests that do not use a relay_early
6319 cell. This change helps Tor resist a class of denial-of-service
6320 attacks by limiting the maximum circuit length.
6321 - Adjust the number of introduction points that a hidden service
6322 will try to maintain based on how long its introduction points
6323 remain in use and how many introductions they handle. Fixes
6325 - Try to use system facilities for enumerating local interface
6326 addresses, before falling back to our old approach (which was
6327 binding a UDP socket, and calling getsockname() on it). That
6328 approach was scaring OS X users whose draconian firewall
6329 software warned about binding to UDP sockets, regardless of
6330 whether packets were sent. Now we try to use getifaddrs(),
6331 SIOCGIFCONF, or GetAdaptersAddresses(), depending on what the
6332 system supports. Resolves ticket 1827.
6334 o Major security workaround:
6335 - When building or running with any version of OpenSSL earlier
6336 than 0.9.8s or 1.0.0f, disable SSLv3 support. These OpenSSL
6337 versions have a bug (CVE-2011-4576) in which their block cipher
6338 padding includes uninitialized data, potentially leaking sensitive
6339 information to any peer with whom they make a SSLv3 connection. Tor
6340 does not use SSL v3 by default, but a hostile client or server
6341 could force an SSLv3 connection in order to gain information that
6342 they shouldn't have been able to get. The best solution here is to
6343 upgrade to OpenSSL 0.9.8s or 1.0.0f (or later). But when building
6344 or running with a non-upgraded OpenSSL, we disable SSLv3 entirely
6345 to make sure that the bug can't happen.
6348 - Fix the SOCKET_OK test that we use to tell when socket
6349 creation fails so that it works on Win64. Fixes part of bug 4533;
6350 bugfix on 0.2.2.29-beta. Bug found by wanoskarnet.
6351 - Correct our replacements for the timeradd() and timersub() functions
6352 on platforms that lack them (for example, Windows). The timersub()
6353 function is used when expiring circuits, while timeradd() is
6354 currently unused. Bug report and patch by Vektor. Fixes bug 4778;
6355 bugfix on 0.2.2.24-alpha and 0.2.3.1-alpha.
6356 - Do not use OpenSSL 1.0.0's counter mode: it has a critical bug
6357 that was fixed in OpenSSL 1.0.0a. We test for the counter mode
6358 bug at runtime, not compile time, because some distributions hack
6359 their OpenSSL to mis-report its version. Fixes bug 4779; bugfix
6360 on 0.2.3.9-alpha. Found by Pascal.
6362 o Minor features (controller):
6363 - Use absolute path names when reporting the torrc filename in the
6364 control protocol, so a controller can more easily find the torrc
6365 file. Resolves bug 1101.
6366 - Extend the control protocol to report flags that control a circuit's
6367 path selection in CIRC events and in replies to 'GETINFO
6368 circuit-status'. Implements part of ticket 2411.
6369 - Extend the control protocol to report the hidden service address
6370 and current state of a hidden-service-related circuit in CIRC
6371 events and in replies to 'GETINFO circuit-status'. Implements part
6373 - When reporting the path to the cookie file to the controller,
6374 give an absolute path. Resolves ticket 4881.
6375 - Allow controllers to request an event notification whenever a
6376 circuit is cannibalized or its purpose is changed. Implements
6377 part of ticket 3457.
6378 - Include the creation time of a circuit in CIRC and CIRC2
6379 control-port events and the list produced by the 'GETINFO
6380 circuit-status' control-port command.
6382 o Minor features (directory authorities):
6383 - Directory authorities now reject versions of Tor older than
6384 0.2.1.30, and Tor versions between 0.2.2.1-alpha and 0.2.2.20-alpha
6385 inclusive. These versions accounted for only a small fraction of
6386 the Tor network, and have numerous known security issues. Resolves
6388 - Authority operators can now vote for all relays in a given
6389 set of countries to be BadDir/BadExit/Invalid/Rejected.
6390 - Provide two consensus parameters (FastFlagMinThreshold and
6391 FastFlagMaxThreshold) to control the range of allowable bandwidths
6392 for the Fast directory flag. These allow authorities to run
6393 experiments on appropriate requirements for being a "Fast" node.
6394 The AuthDirFastGuarantee config value still applies. Implements
6396 - Document the GiveGuardFlagTo_CVE_2011_2768_VulnerableRelays
6397 directory authority option (introduced in Tor 0.2.2.34).
6399 o Minor features (other):
6400 - Don't disable the DirPort when we cannot exceed our AccountingMax
6401 limit during this interval because the effective bandwidthrate is
6402 low enough. This is useful in a situation where AccountMax is only
6403 used as an additional safeguard or to provide statistics.
6404 - Prepend an informative header to generated dynamic_dh_params files.
6405 - If EntryNodes are given, but UseEntryGuards is set to 0, warn that
6406 EntryNodes will have no effect. Resolves issue 2571.
6407 - Log more useful messages when we fail to disable debugger
6409 - Log which authority we're missing votes from when we go to fetch
6410 them from the other auths.
6411 - Log (at debug level) whenever a circuit's purpose is changed.
6412 - Add missing documentation for the MaxClientCircuitsPending,
6413 UseMicrodescriptors, UserspaceIOCPBuffers, and
6414 _UseFilteringSSLBufferevents options, all introduced during
6416 - Update to the January 3 2012 Maxmind GeoLite Country database.
6418 o Minor bugfixes (hidden services):
6419 - Don't close hidden service client circuits which have almost
6420 finished connecting to their destination when they reach
6421 the normal circuit-build timeout. Previously, we would close
6422 introduction circuits which are waiting for an acknowledgement
6423 from the introduction point, and rendezvous circuits which have
6424 been specified in an INTRODUCE1 cell sent to a hidden service,
6425 after the normal CBT. Now, we mark them as 'timed out', and launch
6426 another rendezvous attempt in parallel. This behavior change can
6427 be disabled using the new CloseHSClientCircuitsImmediatelyOnTimeout
6428 option. Fixes part of bug 1297; bugfix on 0.2.2.2-alpha.
6429 - Don't close hidden-service-side rendezvous circuits when they
6430 reach the normal circuit-build timeout. This behavior change can
6431 be disabled using the new
6432 CloseHSServiceRendCircuitsImmediatelyOnTimeout option. Fixes the
6433 remaining part of bug 1297; bugfix on 0.2.2.2-alpha.
6434 - Make sure we never mark the wrong rendezvous circuit as having
6435 had its introduction cell acknowleged by the introduction-point
6436 relay. Previously, when we received an INTRODUCE_ACK cell on a
6437 client-side hidden-service introduction circuit, we might have
6438 marked a rendezvous circuit other than the one we specified in
6439 the INTRODUCE1 cell as INTRO_ACKED, which would have produced
6440 a warning message and interfered with the hidden service
6441 connection-establishment process. Fixes bug 4759; bugfix on
6442 0.2.3.3-alpha, when we added the stream-isolation feature which
6443 might cause Tor to open multiple rendezvous circuits for the same
6445 - Don't trigger an assertion failure when we mark a new client-side
6446 hidden-service introduction circuit for close during the process
6447 of creating it. Fixes bug 4796; bugfix on 0.2.3.6-alpha. Reported
6450 o Minor bugfixes (log messages):
6451 - Correctly spell "connect" in a log message on failure to create a
6452 controlsocket. Fixes bug 4803; bugfix on 0.2.2.26-beta and
6454 - Fix a typo in a log message in rend_service_rendezvous_has_opened().
6455 Fixes bug 4856; bugfix on Tor 0.0.6.
6456 - Fix the log message describing how we work around discovering
6457 that our version is the ill-fated OpenSSL 0.9.8l. Fixes bug
6458 4837; bugfix on 0.2.2.9-alpha.
6459 - When logging about a disallowed .exit name, do not also call it
6460 an "invalid onion address". Fixes bug 3325; bugfix on 0.2.2.9-alpha.
6462 o Minor bugfixes (build fixes):
6463 - During configure, detect when we're building with clang version
6464 3.0 or lower and disable the -Wnormalized=id and -Woverride-init
6465 CFLAGS. clang doesn't support them yet.
6466 - During configure, search for library containing cos function as
6467 libm lives in libcore on some platforms (BeOS/Haiku). Linking
6468 against libm was hard-coded before. Fixes the first part of bug
6469 4727; bugfix on 0.2.2.2-alpha. Patch and analysis by Martin Hebnes
6471 - Detect attempts to build Tor on (as yet hypothetical) versions
6472 of Windows where sizeof(intptr_t) != sizeof(SOCKET). Partial
6473 fix for bug 4533. Bugfix on 0.2.2.28-beta.
6474 - Preprocessor directives should not be put inside the arguments
6475 of a macro. This would break compilation with GCC releases prior
6476 to version 3.3. We would never recommend such an old GCC version,
6477 but it is apparently required for binary compatibility on some
6478 platforms (namely, certain builds of Haiku). Fixes the other part
6479 of bug 4727; bugfix on 0.2.3.3-alpha. Patch and analysis by Martin
6482 o Minor bugfixes (other):
6483 - Older Linux kernels erroneously respond to strange nmap behavior
6484 by having accept() return successfully with a zero-length
6485 socket. When this happens, just close the connection. Previously,
6486 we would try harder to learn the remote address: but there was
6487 no such remote address to learn, and our method for trying to
6488 learn it was incorrect. Fixes bugs 1240, 4745, and 4747. Bugfix
6489 on 0.1.0.3-rc. Reported and diagnosed by "r1eo".
6490 - Fix null-pointer access that could occur if TLS allocation failed.
6491 Fixes bug 4531; bugfix on 0.2.0.20-rc. Found by "troll_un". This was
6492 erroneously listed as fixed in 0.2.3.9-alpha, but the fix had
6493 accidentally been reverted.
6494 - Fix our implementation of crypto_random_hostname() so it can't
6495 overflow on ridiculously large inputs. (No Tor version has ever
6496 provided this kind of bad inputs, but let's be correct in depth.)
6497 Fixes bug 4413; bugfix on 0.2.2.9-alpha. Fix by Stephen Palmateer.
6498 - Find more places in the code that should have been testing for
6499 invalid sockets using the SOCKET_OK macro. Required for a fix
6500 for bug 4533. Bugfix on 0.2.2.28-beta.
6501 - Fix an assertion failure when, while running with bufferevents, a
6502 connection finishes connecting after it is marked for close, but
6503 before it is closed. Fixes bug 4697; bugfix on 0.2.3.1-alpha.
6504 - test_util_spawn_background_ok() hardcoded the expected value
6505 for ENOENT to 2. This isn't portable as error numbers are
6506 platform specific, and particularly the hurd has ENOENT at
6507 0x40000002. Construct expected string at runtime, using the correct
6508 value for ENOENT. Fixes bug 4733; bugfix on 0.2.3.1-alpha.
6509 - Reject attempts to disable DisableDebuggerAttachment while Tor is
6510 running. Fixes bug 4650; bugfix on 0.2.3.9-alpha.
6511 - Use an appropriate-width type for sockets in tor-fw-helper on
6512 win64. Fixes bug 1983 at last. Bugfix on 0.2.3.9-alpha.
6515 - When sending or relaying a RELAY_EARLY cell, we used to convert
6516 it to a RELAY cell if the connection was using the v1 link
6517 protocol. This was a workaround for older versions of Tor, which
6518 didn't handle RELAY_EARLY cells properly. Now that all supported
6519 versions can handle RELAY_EARLY cells, and now that we're enforcing
6520 the "no RELAY_EXTEND commands except in RELAY_EARLY cells" rule,
6521 remove this workaround. Addresses bug 4786.
6523 o Code simplifications and refactoring:
6524 - Use OpenSSL's built-in SSL_state_string_long() instead of our
6525 own homebrewed ssl_state_to_string() replacement. Patch from
6526 Emile Snyder. Fixes bug 4653.
6527 - Use macros to indicate OpenSSL versions, so we don't need to worry
6528 about accidental hexadecimal bit shifts.
6529 - Remove some workaround code for OpenSSL 0.9.6 (which is no longer
6531 - Convert more instances of tor_snprintf+tor_strdup into tor_asprintf.
6532 - Use the smartlist_add_asprintf() alias more consistently.
6533 - Use a TOR_INVALID_SOCKET macro when initializing a socket to an
6534 invalid value, rather than just -1.
6535 - Rename a handful of old identifiers, mostly related to crypto
6536 structures and crypto functions. By convention, our "create an
6537 object" functions are called "type_new()", our "free an object"
6538 functions are called "type_free()", and our types indicate that
6539 they are types only with a final "_t". But a handful of older
6540 types and functions broke these rules, with function names like
6541 "type_create" or "subsystem_op_type", or with type names like
6545 Changes in version 0.2.3.10-alpha - 2011-12-16
6546 Tor 0.2.3.10-alpha fixes a critical heap-overflow security issue in
6547 Tor's buffers code. Absolutely everybody should upgrade.
6549 The bug relied on an incorrect calculation when making data continuous
6550 in one of our IO buffers, if the first chunk of the buffer was
6551 misaligned by just the wrong amount. The miscalculation would allow an
6552 attacker to overflow a piece of heap-allocated memory. To mount this
6553 attack, the attacker would need to either open a SOCKS connection to
6554 Tor's SocksPort (usually restricted to localhost), or target a Tor
6555 instance configured to make its connections through a SOCKS proxy
6556 (which Tor does not do by default).
6558 Good security practice requires that all heap-overflow bugs should be
6559 presumed to be exploitable until proven otherwise, so we are treating
6560 this as a potential code execution attack. Please upgrade immediately!
6561 This bug does not affect bufferevents-based builds of Tor. Special
6562 thanks to "Vektor" for reporting this issue to us!
6564 This release also contains a few minor bugfixes for issues discovered
6568 - Fix a heap overflow bug that could occur when trying to pull
6569 data into the first chunk of a buffer, when that chunk had
6570 already had some data drained from it. Fixes CVE-2011-2778;
6571 bugfix on 0.2.0.16-alpha. Reported by "Vektor".
6574 - If we can't attach streams to a rendezvous circuit when we
6575 finish connecting to a hidden service, clear the rendezvous
6576 circuit's stream-isolation state and try to attach streams
6577 again. Previously, we cleared rendezvous circuits' isolation
6578 state either too early (if they were freshly built) or not at all
6579 (if they had been built earlier and were cannibalized). Bugfix on
6580 0.2.3.3-alpha; fixes bug 4655.
6581 - Fix compilation of the libnatpmp helper on non-Windows. Bugfix on
6582 0.2.3.9-alpha; fixes bug 4691. Reported by Anthony G. Basile.
6583 - Fix an assertion failure when a relay with accounting enabled
6584 starts up while dormant. Fixes bug 4702; bugfix on 0.2.3.9-alpha.
6587 - Update to the December 6 2011 Maxmind GeoLite Country database.
6590 Changes in version 0.2.2.35 - 2011-12-16
6591 Tor 0.2.2.35 fixes a critical heap-overflow security issue in Tor's
6592 buffers code. Absolutely everybody should upgrade.
6594 The bug relied on an incorrect calculation when making data continuous
6595 in one of our IO buffers, if the first chunk of the buffer was
6596 misaligned by just the wrong amount. The miscalculation would allow an
6597 attacker to overflow a piece of heap-allocated memory. To mount this
6598 attack, the attacker would need to either open a SOCKS connection to
6599 Tor's SocksPort (usually restricted to localhost), or target a Tor
6600 instance configured to make its connections through a SOCKS proxy
6601 (which Tor does not do by default).
6603 Good security practice requires that all heap-overflow bugs should be
6604 presumed to be exploitable until proven otherwise, so we are treating
6605 this as a potential code execution attack. Please upgrade immediately!
6606 This bug does not affect bufferevents-based builds of Tor. Special
6607 thanks to "Vektor" for reporting this issue to us!
6609 Tor 0.2.2.35 also fixes several bugs in previous versions, including
6610 crash bugs for unusual configurations, and a long-term bug that
6611 would prevent Tor from starting on Windows machines with draconian
6614 With this release, we remind everyone that 0.2.0.x has reached its
6615 formal end-of-life. Those Tor versions have many known flaws, and
6616 nobody should be using them. You should upgrade -- ideally to the
6617 0.2.2.x series. If you're using a Linux or BSD and its packages are
6618 obsolete, stop using those packages and upgrade anyway.
6620 The Tor 0.2.1.x series is also approaching its end-of-life: it will no
6621 longer receive support after some time in early 2012.
6624 - Fix a heap overflow bug that could occur when trying to pull
6625 data into the first chunk of a buffer, when that chunk had
6626 already had some data drained from it. Fixes CVE-2011-2778;
6627 bugfix on 0.2.0.16-alpha. Reported by "Vektor".
6628 - Initialize Libevent with the EVENT_BASE_FLAG_NOLOCK flag enabled, so
6629 that it doesn't attempt to allocate a socketpair. This could cause
6630 some problems on Windows systems with overzealous firewalls. Fix for
6631 bug 4457; workaround for Libevent versions 2.0.1-alpha through
6633 - If we mark an OR connection for close based on a cell we process,
6634 don't process any further cells on it. We already avoid further
6635 reads on marked-for-close connections, but now we also discard the
6636 cells we'd already read. Fixes bug 4299; bugfix on 0.2.0.10-alpha,
6637 which was the first version where we might mark a connection for
6638 close based on processing a cell on it.
6639 - Correctly sanity-check that we don't underflow on a memory
6640 allocation (and then assert) for hidden service introduction
6641 point decryption. Bug discovered by Dan Rosenberg. Fixes bug 4410;
6642 bugfix on 0.2.1.5-alpha.
6643 - Fix a memory leak when we check whether a hidden service
6644 descriptor has any usable introduction points left. Fixes bug
6645 4424. Bugfix on 0.2.2.25-alpha.
6646 - Don't crash when we're running as a relay and don't have a GeoIP
6647 file. Bugfix on 0.2.2.34; fixes bug 4340. This backports a fix
6648 we've had in the 0.2.3.x branch already.
6649 - When running as a client, do not print a misleading (and plain
6650 wrong) log message that we're collecting "directory request"
6651 statistics: clients don't collect statistics. Also don't create a
6652 useless (because empty) stats file in the stats/ directory. Fixes
6653 bug 4353; bugfix on 0.2.2.34.
6656 - Detect failure to initialize Libevent. This fix provides better
6657 detection for future instances of bug 4457.
6658 - Avoid frequent calls to the fairly expensive cull_wedged_cpuworkers
6659 function. This was eating up hideously large amounts of time on some
6660 busy servers. Fixes bug 4518; bugfix on 0.0.9.8.
6661 - Resolve an integer overflow bug in smartlist_ensure_capacity().
6662 Fixes bug 4230; bugfix on Tor 0.1.0.1-rc. Based on a patch by
6664 - Don't warn about unused log_mutex in log.c when building with
6665 --disable-threads using a recent GCC. Fixes bug 4437; bugfix on
6666 0.1.0.6-rc which introduced --disable-threads.
6667 - When configuring, starting, or stopping an NT service, stop
6668 immediately after the service configuration attempt has succeeded
6669 or failed. Fixes bug 3963; bugfix on 0.2.0.7-alpha.
6670 - When sending a NETINFO cell, include the original address
6671 received for the other side, not its canonical address. Found
6672 by "troll_un"; fixes bug 4349; bugfix on 0.2.0.10-alpha.
6673 - Fix a typo in a hibernation-related log message. Fixes bug 4331;
6674 bugfix on 0.2.2.23-alpha; found by "tmpname0901".
6675 - Fix a memory leak in launch_direct_bridge_descriptor_fetch() that
6676 occurred when a client tried to fetch a descriptor for a bridge
6677 in ExcludeNodes. Fixes bug 4383; bugfix on 0.2.2.25-alpha.
6678 - Backport fixes for a pair of compilation warnings on Windows.
6679 Fixes bug 4521; bugfix on 0.2.2.28-beta and on 0.2.2.29-beta.
6680 - If we had ever tried to call tor_addr_to_str on an address of
6681 unknown type, we would have done a strdup on an uninitialized
6682 buffer. Now we won't. Fixes bug 4529; bugfix on 0.2.1.3-alpha.
6683 Reported by "troll_un".
6684 - Correctly detect and handle transient lookup failures from
6685 tor_addr_lookup. Fixes bug 4530; bugfix on 0.2.1.5-alpha.
6686 Reported by "troll_un".
6687 - Fix null-pointer access that could occur if TLS allocation failed.
6688 Fixes bug 4531; bugfix on 0.2.0.20-rc. Found by "troll_un".
6689 - Use tor_socket_t type for listener argument to accept(). Fixes bug
6690 4535; bugfix on 0.2.2.28-beta. Found by "troll_un".
6693 - Add two new config options for directory authorities:
6694 AuthDirFastGuarantee sets a bandwidth threshold for guaranteeing the
6695 Fast flag, and AuthDirGuardBWGuarantee sets a bandwidth threshold
6696 that is always sufficient to satisfy the bandwidth requirement for
6697 the Guard flag. Now it will be easier for researchers to simulate
6698 Tor networks with different values. Resolves ticket 4484.
6699 - When Tor ignores a hidden service specified in its configuration,
6700 include the hidden service's directory in the warning message.
6701 Previously, we would only tell the user that some hidden service
6702 was ignored. Bugfix on 0.0.6; fixes bug 4426.
6703 - Update to the December 6 2011 Maxmind GeoLite Country database.
6705 o Packaging changes:
6706 - Make it easier to automate expert package builds on Windows,
6707 by removing an absolute path from makensis.exe command.
6710 Changes in version 0.2.1.32 - 2011-12-16
6711 Tor 0.2.1.32 backports important security and privacy fixes for
6712 oldstable. This release is intended only for package maintainers and
6713 others who cannot use the 0.2.2 stable series. All others should be
6714 using Tor 0.2.2.x or newer.
6716 The Tor 0.2.1.x series will reach formal end-of-life some time in
6717 early 2012; we will stop releasing patches for it then.
6719 o Major bugfixes (also included in 0.2.2.x):
6720 - Correctly sanity-check that we don't underflow on a memory
6721 allocation (and then assert) for hidden service introduction
6722 point decryption. Bug discovered by Dan Rosenberg. Fixes bug 4410;
6723 bugfix on 0.2.1.5-alpha.
6724 - Fix a heap overflow bug that could occur when trying to pull
6725 data into the first chunk of a buffer, when that chunk had
6726 already had some data drained from it. Fixes CVE-2011-2778;
6727 bugfix on 0.2.0.16-alpha. Reported by "Vektor".
6730 - Update to the December 6 2011 Maxmind GeoLite Country database.
6733 Changes in version 0.2.3.9-alpha - 2011-12-08
6734 Tor 0.2.3.9-alpha introduces initial IPv6 support for bridges, adds
6735 a "DisableNetwork" security feature that bundles can use to avoid
6736 touching the network until bridges are configured, moves forward on
6737 the pluggable transport design, fixes a flaw in the hidden service
6738 design that unnecessarily prevented clients with wrong clocks from
6739 reaching hidden services, and fixes a wide variety of other issues.
6742 - Clients can now connect to private bridges over IPv6. Bridges
6743 still need at least one IPv4 address in order to connect to
6744 other relays. Note that we don't yet handle the case where the
6745 user has two bridge lines for the same bridge (one IPv4, one
6746 IPv6). Implements parts of proposal 186.
6747 - New "DisableNetwork" config option to prevent Tor from launching any
6748 connections or accepting any connections except on a control port.
6749 Bundles and controllers can set this option before letting Tor talk
6750 to the rest of the network, for example to prevent any connections
6751 to a non-bridge address. Packages like Orbot can also use this
6752 option to instruct Tor to save power when the network is off.
6753 - Clients and bridges can now be configured to use a separate
6754 "transport" proxy. This approach makes the censorship arms race
6755 easier by allowing bridges to use protocol obfuscation plugins. It
6756 implements the "managed proxy" part of proposal 180 (ticket 3472).
6757 - When using OpenSSL 1.0.0 or later, use OpenSSL's counter mode
6758 implementation. It makes AES_CTR about 7% faster than our old one
6759 (which was about 10% faster than the one OpenSSL used to provide).
6760 Resolves ticket 4526.
6761 - Add a "tor2web mode" for clients that want to connect to hidden
6762 services non-anonymously (and possibly more quickly). As a safety
6763 measure to try to keep users from turning this on without knowing
6764 what they are doing, tor2web mode must be explicitly enabled at
6765 compile time, and a copy of Tor compiled to run in tor2web mode
6766 cannot be used as a normal Tor client. Implements feature 2553.
6767 - Add experimental support for running on Windows with IOCP and no
6768 kernel-space socket buffers. This feature is controlled by a new
6769 "UserspaceIOCPBuffers" config option (off by default), which has
6770 no effect unless Tor has been built with support for bufferevents,
6771 is running on Windows, and has enabled IOCP. This may, in the long
6772 run, help solve or mitigate bug 98.
6773 - Use a more secure consensus parameter voting algorithm. Now at
6774 least three directory authorities or a majority of them must
6775 vote on a given parameter before it will be included in the
6776 consensus. Implements proposal 178.
6779 - Hidden services now ignore the timestamps on INTRODUCE2 cells.
6780 They used to check that the timestamp was within 30 minutes
6781 of their system clock, so they could cap the size of their
6782 replay-detection cache, but that approach unnecessarily refused
6783 service to clients with wrong clocks. Bugfix on 0.2.1.6-alpha, when
6784 the v3 intro-point protocol (the first one which sent a timestamp
6785 field in the INTRODUCE2 cell) was introduced; fixes bug 3460.
6786 - Only use the EVP interface when AES acceleration is enabled,
6787 to avoid a 5-7% performance regression. Resolves issue 4525;
6788 bugfix on 0.2.3.8-alpha.
6790 o Privacy/anonymity features (bridge detection):
6791 - Make bridge SSL certificates a bit more stealthy by using random
6792 serial numbers, in the same fashion as OpenSSL when generating
6793 self-signed certificates. Implements ticket 4584.
6794 - Introduce a new config option "DynamicDHGroups", enabled by
6795 default, which provides each bridge with a unique prime DH modulus
6796 to be used during SSL handshakes. This option attempts to help
6797 against censors who might use the Apache DH modulus as a static
6798 identifier for bridges. Addresses ticket 4548.
6800 o Minor features (new/different config options):
6801 - New configuration option "DisableDebuggerAttachment" (on by default)
6802 to prevent basic debugging attachment attempts by other processes.
6803 Supports Mac OS X and Gnu/Linux. Resolves ticket 3313.
6804 - Allow MapAddress directives to specify matches against super-domains,
6805 as in "MapAddress *.torproject.org *.torproject.org.torserver.exit".
6806 Implements issue 933.
6807 - Slightly change behavior of "list" options (that is, config
6808 options that can appear more than once) when they appear both in
6809 torrc and on the command line. Previously, the command-line options
6810 would be appended to the ones from torrc. Now, the command-line
6811 options override the torrc options entirely. This new behavior
6812 allows the user to override list options (like exit policies and
6813 ports to listen on) from the command line, rather than simply
6814 appending to the list.
6815 - You can get the old (appending) command-line behavior for "list"
6816 options by prefixing the option name with a "+".
6817 - You can remove all the values for a "list" option from the command
6818 line without adding any new ones by prefixing the option name
6820 - Add experimental support for a "defaults" torrc file to be parsed
6821 before the regular torrc. Torrc options override the defaults file's
6822 options in the same way that the command line overrides the torrc.
6823 The SAVECONF controller command saves only those options which
6824 differ between the current configuration and the defaults file. HUP
6825 reloads both files. (Note: This is an experimental feature; its
6826 behavior will probably be refined in future 0.2.3.x-alpha versions
6827 to better meet packagers' needs.) Implements task 4552.
6830 - Try to make the introductory warning message that Tor prints on
6831 startup more useful for actually finding help and information.
6832 Resolves ticket 2474.
6833 - Running "make version" now displays the version of Tor that
6834 we're about to build. Idea from katmagic; resolves issue 4400.
6835 - Expire old or over-used hidden service introduction points.
6836 Required by fix for bug 3460.
6837 - Move the replay-detection cache for the RSA-encrypted parts of
6838 INTRODUCE2 cells to the introduction point data structures.
6839 Previously, we would use one replay-detection cache per hidden
6840 service. Required by fix for bug 3460.
6841 - Reduce the lifetime of elements of hidden services' Diffie-Hellman
6842 public key replay-detection cache from 60 minutes to 5 minutes. This
6843 replay-detection cache is now used only to detect multiple
6844 INTRODUCE2 cells specifying the same rendezvous point, so we can
6845 avoid launching multiple simultaneous attempts to connect to it.
6847 o Minor bugfixes (on Tor 0.2.2.x and earlier):
6848 - Resolve an integer overflow bug in smartlist_ensure_capacity().
6849 Fixes bug 4230; bugfix on Tor 0.1.0.1-rc. Based on a patch by
6851 - Fix a minor formatting issue in one of tor-gencert's error messages.
6853 - Prevent a false positive from the check-spaces script, by disabling
6854 the "whitespace between function name and (" check for functions
6856 - Fix a log message suggesting that people contact a non-existent
6857 email address. Fixes bug 3448.
6858 - Fix null-pointer access that could occur if TLS allocation failed.
6859 Fixes bug 4531; bugfix on 0.2.0.20-rc. Found by "troll_un".
6860 - Report a real bootstrap problem to the controller on router
6861 identity mismatch. Previously we just said "foo", which probably
6862 made a lot of sense at the time. Fixes bug 4169; bugfix on
6864 - If we had ever tried to call tor_addr_to_str() on an address of
6865 unknown type, we would have done a strdup() on an uninitialized
6866 buffer. Now we won't. Fixes bug 4529; bugfix on 0.2.1.3-alpha.
6867 Reported by "troll_un".
6868 - Correctly detect and handle transient lookup failures from
6869 tor_addr_lookup(). Fixes bug 4530; bugfix on 0.2.1.5-alpha.
6870 Reported by "troll_un".
6871 - Use tor_socket_t type for listener argument to accept(). Fixes bug
6872 4535; bugfix on 0.2.2.28-beta. Found by "troll_un".
6873 - Initialize conn->addr to a valid state in spawn_cpuworker(). Fixes
6874 bug 4532; found by "troll_un".
6876 o Minor bugfixes (on Tor 0.2.3.x):
6877 - Fix a compile warning in tor_inet_pton(). Bugfix on 0.2.3.8-alpha;
6879 - Don't send two ESTABLISH_RENDEZVOUS cells when opening a new
6880 circuit for use as a hidden service client's rendezvous point.
6881 Fixes bugs 4641 and 4171; bugfix on 0.2.3.3-alpha. Diagnosed
6882 with help from wanoskarnet.
6883 - Restore behavior of overriding SocksPort, ORPort, and similar
6884 options from the command line. Bugfix on 0.2.3.3-alpha.
6887 - Properly handle the case where the build-tree is not the same
6888 as the source tree when generating src/common/common_sha1.i,
6889 src/or/micro-revision.i, and src/or/or_sha1.i. Fixes bug 3953;
6890 bugfix on 0.2.0.1-alpha.
6892 o Code simplifications, cleanups, and refactorings:
6893 - Remove the pure attribute from all functions that used it
6894 previously. In many cases we assigned it incorrectly, because the
6895 functions might assert or call impure functions, and we don't have
6896 evidence that keeping the pure attribute is worthwhile. Implements
6897 changes suggested in ticket 4421.
6898 - Remove some dead code spotted by coverity. Fixes cid 432.
6899 Bugfix on 0.2.3.1-alpha, closes bug 4637.
6902 Changes in version 0.2.3.8-alpha - 2011-11-22
6903 Tor 0.2.3.8-alpha fixes some crash and assert bugs, including a
6904 socketpair-related bug that has been bothering Windows users. It adds
6905 support to serve microdescriptors to controllers, so Vidalia's network
6906 map can resume listing relays (once Vidalia implements its side),
6907 and adds better support for hardware AES acceleration. Finally, it
6908 starts the process of adjusting the bandwidth cutoff for getting the
6909 "Fast" flag from 20KB to (currently) 32KB -- preliminary results show
6910 that tiny relays harm performance more than they help network capacity.
6913 - Initialize Libevent with the EVENT_BASE_FLAG_NOLOCK flag enabled, so
6914 that it doesn't attempt to allocate a socketpair. This could cause
6915 some problems on Windows systems with overzealous firewalls. Fix for
6916 bug 4457; workaround for Libevent versions 2.0.1-alpha through
6918 - Correctly sanity-check that we don't underflow on a memory
6919 allocation (and then assert) for hidden service introduction
6920 point decryption. Bug discovered by Dan Rosenberg. Fixes bug 4410;
6921 bugfix on 0.2.1.5-alpha.
6922 - Remove the artificially low cutoff of 20KB to guarantee the Fast
6923 flag. In the past few years the average relay speed has picked
6924 up, and while the "top 7/8 of the network get the Fast flag" and
6925 "all relays with 20KB or more of capacity get the Fast flag" rules
6926 used to have the same result, now the top 7/8 of the network has
6927 a capacity more like 32KB. Bugfix on 0.2.1.14-rc. Fixes bug 4489.
6928 - Fix a rare assertion failure when checking whether a v0 hidden
6929 service descriptor has any usable introduction points left, and
6930 we don't have enough information to build a circuit to the first
6931 intro point named in the descriptor. The HS client code in
6932 0.2.3.x no longer uses v0 HS descriptors, but this assertion can
6933 trigger on (and crash) v0 HS authorities. Fixes bug 4411.
6934 Bugfix on 0.2.3.1-alpha; diagnosed by frosty_un.
6935 - Make bridge authorities not crash when they are asked for their own
6936 descriptor. Bugfix on 0.2.3.7-alpha, reported by Lucky Green.
6937 - When running as a client, do not print a misleading (and plain
6938 wrong) log message that we're collecting "directory request"
6939 statistics: clients don't collect statistics. Also don't create a
6940 useless (because empty) stats file in the stats/ directory. Fixes
6941 bug 4353; bugfix on 0.2.2.34 and 0.2.3.7-alpha.
6944 - Allow Tor controllers like Vidalia to obtain the microdescriptor
6945 for a relay by identity digest or nickname. Previously,
6946 microdescriptors were only available by their own digests, so a
6947 controller would have to ask for and parse the whole microdescriptor
6948 consensus in order to look up a single relay's microdesc. Fixes
6949 bug 3832; bugfix on 0.2.3.1-alpha.
6950 - Use OpenSSL's EVP interface for AES encryption, so that all AES
6951 operations can use hardware acceleration (if present). Resolves
6954 o Minor bugfixes (on 0.2.2.x and earlier):
6955 - Detect failure to initialize Libevent. This fix provides better
6956 detection for future instances of bug 4457.
6957 - Avoid frequent calls to the fairly expensive cull_wedged_cpuworkers
6958 function. This was eating up hideously large amounts of time on some
6959 busy servers. Fixes bug 4518; bugfix on 0.0.9.8.
6960 - Don't warn about unused log_mutex in log.c when building with
6961 --disable-threads using a recent GCC. Fixes bug 4437; bugfix on
6962 0.1.0.6-rc which introduced --disable-threads.
6963 - Allow manual 'authenticate' commands to the controller interface
6964 from netcat (nc) as well as telnet. We were rejecting them because
6965 they didn't come with the expected whitespace at the end of the
6966 command. Bugfix on 0.1.1.1-alpha; fixes bug 2893.
6967 - Fix some (not actually triggerable) buffer size checks in usage of
6968 tor_inet_ntop. Fixes bug 4434; bugfix on Tor 0.2.0.1-alpha. Patch
6970 - Fix parsing of some corner-cases with tor_inet_pton(). Fixes
6971 bug 4515; bugfix on 0.2.0.1-alpha; fix by Anders Sundman.
6972 - When configuring, starting, or stopping an NT service, stop
6973 immediately after the service configuration attempt has succeeded
6974 or failed. Fixes bug 3963; bugfix on 0.2.0.7-alpha.
6975 - When sending a NETINFO cell, include the original address
6976 received for the other side, not its canonical address. Found
6977 by "troll_un"; fixes bug 4349; bugfix on 0.2.0.10-alpha.
6978 - Rename the bench_{aes,dmap} functions to test_*, so that tinytest
6979 can pick them up when the tests aren't disabled. Bugfix on
6980 0.2.2.4-alpha which introduced tinytest.
6981 - Fix a memory leak when we check whether a hidden service
6982 descriptor has any usable introduction points left. Fixes bug
6983 4424. Bugfix on 0.2.2.25-alpha.
6984 - Fix a memory leak in launch_direct_bridge_descriptor_fetch() that
6985 occurred when a client tried to fetch a descriptor for a bridge
6986 in ExcludeNodes. Fixes bug 4383; bugfix on 0.2.2.25-alpha.
6988 o Minor bugfixes (on 0.2.3.x):
6989 - Make util unit tests build correctly with MSVC. Bugfix on
6990 0.2.3.3-alpha. Patch by Gisle Vanem.
6991 - Successfully detect AUTH_CHALLENGE cells with no recognized
6992 authentication type listed. Fixes bug 4367; bugfix on 0.2.3.6-alpha.
6994 - If a relay receives an AUTH_CHALLENGE cell it can't answer,
6995 it should still send a NETINFO cell to allow the connection to
6996 become open. Fixes bug 4368; fix on 0.2.3.6-alpha; bug found by
6998 - Log less loudly when we get an invalid authentication certificate
6999 from a source other than a directory authority: it's not unusual
7000 to see invalid certs because of clock skew. Fixes bug 4370; bugfix
7002 - Tolerate servers with more clock skew in their authentication
7003 certificates than previously. Fixes bug 4371; bugfix on
7005 - Fix a couple of compile warnings on Windows. Fixes bug 4469; bugfix
7006 on 0.2.3.4-alpha and 0.2.3.6-alpha.
7009 - Add two new config options for directory authorities:
7010 AuthDirFastGuarantee sets a bandwidth threshold for guaranteeing the
7011 Fast flag, and AuthDirGuardBWGuarantee sets a bandwidth threshold
7012 that is always sufficient to satisfy the bandwidth requirement for
7013 the Guard flag. Now it will be easier for researchers to simulate
7014 Tor networks with different values. Resolves ticket 4484.
7015 - When Tor ignores a hidden service specified in its configuration,
7016 include the hidden service's directory in the warning message.
7017 Previously, we would only tell the user that some hidden service
7018 was ignored. Bugfix on 0.0.6; fixes bug 4426.
7019 - When we fail to initialize Libevent, retry with IOCP disabled so we
7020 don't need to turn on multi-threading support in Libevent, which in
7021 turn requires a working socketpair(). This is a workaround for bug
7022 4457, which affects Libevent versions from 2.0.1-alpha through
7024 - Detect when we try to build on a platform that doesn't define
7025 AF_UNSPEC to 0. We don't work there, so refuse to compile.
7026 - Update to the November 1 2011 Maxmind GeoLite Country database.
7028 o Packaging changes:
7029 - Make it easier to automate expert package builds on Windows,
7030 by removing an absolute path from makensis.exe command.
7032 o Code simplifications and refactoring:
7033 - Remove some redundant #include directives throughout the code.
7034 Patch from Andrea Gelmini.
7035 - Unconditionally use OpenSSL's AES implementation instead of our
7036 old built-in one. OpenSSL's AES has been better for a while, and
7037 relatively few servers should still be on any version of OpenSSL
7038 that doesn't have good optimized assembly AES.
7039 - Use the name "CERTS" consistently to refer to the new cell type;
7040 we were calling it CERT in some places and CERTS in others.
7043 - Numerous new unit tests for functions in util.c and address.c by
7045 - The long-disabled benchmark tests are now split into their own
7046 ./src/test/bench binary.
7047 - The benchmark tests can now use more accurate timers than
7048 gettimeofday() when such timers are available.
7051 Changes in version 0.2.3.7-alpha - 2011-10-30
7052 Tor 0.2.3.7-alpha fixes a crash bug in 0.2.3.6-alpha introduced by
7053 the new v3 handshake. It also resolves yet another bridge address
7057 - If we mark an OR connection for close based on a cell we process,
7058 don't process any further cells on it. We already avoid further
7059 reads on marked-for-close connections, but now we also discard the
7060 cells we'd already read. Fixes bug 4299; bugfix on 0.2.0.10-alpha,
7061 which was the first version where we might mark a connection for
7062 close based on processing a cell on it.
7063 - Fix a double-free bug that would occur when we received an invalid
7064 certificate in a CERT cell in the new v3 handshake. Fixes bug 4343;
7065 bugfix on 0.2.3.6-alpha.
7066 - Bridges no longer include their address in NETINFO cells on outgoing
7067 OR connections, to allow them to blend in better with clients.
7068 Removes another avenue for enumerating bridges. Reported by
7069 "troll_un". Fixes bug 4348; bugfix on 0.2.0.10-alpha, when NETINFO
7070 cells were introduced.
7073 - Fixed a typo in a hibernation-related log message. Fixes bug 4331;
7074 bugfix on 0.2.2.23-alpha; found by "tmpname0901".
7077 Changes in version 0.2.3.6-alpha - 2011-10-26
7078 Tor 0.2.3.6-alpha includes the fix from 0.2.2.34 for a critical
7079 anonymity vulnerability where an attacker can deanonymize Tor
7080 users. Everybody should upgrade.
7082 This release also features support for a new v3 connection handshake
7083 protocol, and fixes to make hidden service connections more robust.
7086 - Implement a new handshake protocol (v3) for authenticating Tors to
7087 each other over TLS. It should be more resistant to fingerprinting
7088 than previous protocols, and should require less TLS hacking for
7089 future Tor implementations. Implements proposal 176.
7090 - Allow variable-length padding cells to disguise the length of
7091 Tor's TLS records. Implements part of proposal 184.
7093 o Privacy/anonymity fixes (clients):
7094 - Clients and bridges no longer send TLS certificate chains on
7095 outgoing OR connections. Previously, each client or bridge would
7096 use the same cert chain for all outgoing OR connections until
7097 its IP address changes, which allowed any relay that the client
7098 or bridge contacted to determine which entry guards it is using.
7099 Fixes CVE-2011-2768. Bugfix on 0.0.9pre5; found by "frosty_un".
7100 - If a relay receives a CREATE_FAST cell on a TLS connection, it
7101 no longer considers that connection as suitable for satisfying a
7102 circuit EXTEND request. Now relays can protect clients from the
7103 CVE-2011-2768 issue even if the clients haven't upgraded yet.
7104 - Directory authorities no longer assign the Guard flag to relays
7105 that haven't upgraded to the above "refuse EXTEND requests
7106 to client connections" fix. Now directory authorities can
7107 protect clients from the CVE-2011-2768 issue even if neither
7108 the clients nor the relays have upgraded yet. There's a new
7109 "GiveGuardFlagTo_CVE_2011_2768_VulnerableRelays" config option
7110 to let us transition smoothly, else tomorrow there would be no
7113 o Major bugfixes (hidden services):
7114 - Improve hidden service robustness: when an attempt to connect to
7115 a hidden service ends, be willing to refetch its hidden service
7116 descriptors from each of the HSDir relays responsible for them
7117 immediately. Previously, we would not consider refetching the
7118 service's descriptors from each HSDir for 15 minutes after the last
7119 fetch, which was inconvenient if the hidden service was not running
7120 during the first attempt. Bugfix on 0.2.0.18-alpha; fixes bug 3335.
7121 - When one of a hidden service's introduction points appears to be
7122 unreachable, stop trying it. Previously, we would keep trying
7123 to build circuits to the introduction point until we lost the
7124 descriptor, usually because the user gave up and restarted Tor.
7125 Partly fixes bug 3825.
7126 - Don't launch a useless circuit after failing to use one of a
7127 hidden service's introduction points. Previously, we would
7128 launch a new introduction circuit, but not set the hidden service
7129 which that circuit was intended to connect to, so it would never
7130 actually be used. A different piece of code would then create a
7131 new introduction circuit correctly. Bug reported by katmagic and
7132 found by Sebastian Hahn. Bugfix on 0.2.1.13-alpha; fixes bug 4212.
7134 o Major bugfixes (other):
7135 - Bridges now refuse CREATE or CREATE_FAST cells on OR connections
7136 that they initiated. Relays could distinguish incoming bridge
7137 connections from client connections, creating another avenue for
7138 enumerating bridges. Fixes CVE-2011-2769. Bugfix on 0.2.0.3-alpha.
7139 Found by "frosty_un".
7140 - Don't update the AccountingSoftLimitHitAt state file entry whenever
7141 tor gets started. This prevents a wrong average bandwidth
7142 estimate, which would cause relays to always start a new accounting
7143 interval at the earliest possible moment. Fixes bug 2003; bugfix
7144 on 0.2.2.7-alpha. Reported by BryonEldridge, who also helped
7145 immensely in tracking this bug down.
7146 - Fix a crash bug when changing node restrictions while a DNS lookup
7147 is in-progress. Fixes bug 4259; bugfix on 0.2.2.25-alpha. Bugfix
7150 o Minor bugfixes (on 0.2.2.x and earlier):
7151 - When a hidden service turns an extra service-side introduction
7152 circuit into a general-purpose circuit, free the rend_data and
7153 intro_key fields first, so we won't leak memory if the circuit
7154 is cannibalized for use as another service-side introduction
7155 circuit. Bugfix on 0.2.1.7-alpha; fixes bug 4251.
7156 - Rephrase the log message emitted if the TestSocks check is
7157 successful. Patch from Fabian Keil; fixes bug 4094.
7158 - Bridges now skip DNS self-tests, to act a little more stealthily.
7159 Fixes bug 4201; bugfix on 0.2.0.3-alpha, which first introduced
7160 bridges. Patch by "warms0x".
7161 - Remove a confusing dollar sign from the example fingerprint in the
7162 man page, and also make the example fingerprint a valid one. Fixes
7163 bug 4309; bugfix on 0.2.1.3-alpha.
7164 - Fix internal bug-checking logic that was supposed to catch
7165 failures in digest generation so that it will fail more robustly
7166 if we ask for a nonexistent algorithm. Found by Coverity Scan.
7167 Bugfix on 0.2.2.1-alpha; fixes Coverity CID 479.
7168 - Report any failure in init_keys() calls launched because our
7169 IP address has changed. Spotted by Coverity Scan. Bugfix on
7170 0.1.1.4-alpha; fixes CID 484.
7172 o Minor bugfixes (on 0.2.3.x):
7173 - Fix a bug in configure.in that kept it from building a configure
7174 script with autoconf versions earlier than 2.61. Fixes bug 2430;
7175 bugfix on 0.2.3.1-alpha.
7176 - Don't warn users that they are exposing a client port to the
7177 Internet if they have specified an RFC1918 address. Previously,
7178 we would warn if the user had specified any non-loopback
7179 address. Bugfix on 0.2.3.3-alpha. Fixes bug 4018; reported by Tas.
7180 - Fix memory leaks in the failing cases of the new SocksPort and
7181 ControlPort code. Found by Coverity Scan. Bugfix on 0.2.3.3-alpha;
7182 fixes coverity CIDs 485, 486, and 487.
7185 - When a hidden service's introduction point times out, consider
7186 trying it again during the next attempt to connect to the
7187 HS. Previously, we would not try it again unless a newly fetched
7188 descriptor contained it. Required by fixes for bugs 1297 and 3825.
7189 - The next version of Windows will be called Windows 8, and it has
7190 a major version of 6, minor version of 2. Correctly identify that
7191 version instead of calling it "Very recent version". Resolves
7192 ticket 4153; reported by funkstar.
7193 - The Bridge Authority now writes statistics on how many bridge
7194 descriptors it gave out in total, and how many unique descriptors
7195 it gave out. It also lists how often the most and least commonly
7196 fetched descriptors were given out, as well as the median and
7197 25th/75th percentile. Implements tickets 4200 and 4294.
7198 - Update to the October 4 2011 Maxmind GeoLite Country database.
7200 o Code simplifications and refactoring:
7201 - Remove some old code to remember statistics about which descriptors
7202 we've served as a directory mirror. The feature wasn't used and
7203 is outdated now that microdescriptors are around.
7204 - Rename Tor functions that turn strings into addresses, so that
7205 "parse" indicates that no hostname resolution occurs, and
7206 "lookup" indicates that hostname resolution may occur. This
7207 should help prevent mistakes in the future. Fixes bug 3512.
7210 Changes in version 0.2.2.34 - 2011-10-26
7211 Tor 0.2.2.34 fixes a critical anonymity vulnerability where an attacker
7212 can deanonymize Tor users. Everybody should upgrade.
7214 The attack relies on four components: 1) Clients reuse their TLS cert
7215 when talking to different relays, so relays can recognize a user by
7216 the identity key in her cert. 2) An attacker who knows the client's
7217 identity key can probe each guard relay to see if that identity key
7218 is connected to that guard relay right now. 3) A variety of active
7219 attacks in the literature (starting from "Low-Cost Traffic Analysis
7220 of Tor" by Murdoch and Danezis in 2005) allow a malicious website to
7221 discover the guard relays that a Tor user visiting the website is using.
7222 4) Clients typically pick three guards at random, so the set of guards
7223 for a given user could well be a unique fingerprint for her. This
7224 release fixes components #1 and #2, which is enough to block the attack;
7225 the other two remain as open research problems. Special thanks to
7226 "frosty_un" for reporting the issue to us!
7228 Clients should upgrade so they are no longer recognizable by the TLS
7229 certs they present. Relays should upgrade so they no longer allow a
7230 remote attacker to probe them to test whether unpatched clients are
7231 currently connected to them.
7233 This release also fixes several vulnerabilities that allow an attacker
7234 to enumerate bridge relays. Some bridge enumeration attacks still
7235 remain; see for example proposal 188.
7237 o Privacy/anonymity fixes (clients):
7238 - Clients and bridges no longer send TLS certificate chains on
7239 outgoing OR connections. Previously, each client or bridge would
7240 use the same cert chain for all outgoing OR connections until
7241 its IP address changes, which allowed any relay that the client
7242 or bridge contacted to determine which entry guards it is using.
7243 Fixes CVE-2011-2768. Bugfix on 0.0.9pre5; found by "frosty_un".
7244 - If a relay receives a CREATE_FAST cell on a TLS connection, it
7245 no longer considers that connection as suitable for satisfying a
7246 circuit EXTEND request. Now relays can protect clients from the
7247 CVE-2011-2768 issue even if the clients haven't upgraded yet.
7248 - Directory authorities no longer assign the Guard flag to relays
7249 that haven't upgraded to the above "refuse EXTEND requests
7250 to client connections" fix. Now directory authorities can
7251 protect clients from the CVE-2011-2768 issue even if neither
7252 the clients nor the relays have upgraded yet. There's a new
7253 "GiveGuardFlagTo_CVE_2011_2768_VulnerableRelays" config option
7254 to let us transition smoothly, else tomorrow there would be no
7257 o Privacy/anonymity fixes (bridge enumeration):
7258 - Bridge relays now do their directory fetches inside Tor TLS
7259 connections, like all the other clients do, rather than connecting
7260 directly to the DirPort like public relays do. Removes another
7261 avenue for enumerating bridges. Fixes bug 4115; bugfix on 0.2.0.35.
7262 - Bridges relays now build circuits for themselves in a more similar
7263 way to how clients build them. Removes another avenue for
7264 enumerating bridges. Fixes bug 4124; bugfix on 0.2.0.3-alpha,
7265 when bridges were introduced.
7266 - Bridges now refuse CREATE or CREATE_FAST cells on OR connections
7267 that they initiated. Relays could distinguish incoming bridge
7268 connections from client connections, creating another avenue for
7269 enumerating bridges. Fixes CVE-2011-2769. Bugfix on 0.2.0.3-alpha.
7270 Found by "frosty_un".
7273 - Fix a crash bug when changing node restrictions while a DNS lookup
7274 is in-progress. Fixes bug 4259; bugfix on 0.2.2.25-alpha. Bugfix
7276 - Don't launch a useless circuit after failing to use one of a
7277 hidden service's introduction points. Previously, we would
7278 launch a new introduction circuit, but not set the hidden service
7279 which that circuit was intended to connect to, so it would never
7280 actually be used. A different piece of code would then create a
7281 new introduction circuit correctly. Bug reported by katmagic and
7282 found by Sebastian Hahn. Bugfix on 0.2.1.13-alpha; fixes bug 4212.
7285 - Change an integer overflow check in the OpenBSD_Malloc code so
7286 that GCC is less likely to eliminate it as impossible. Patch
7287 from Mansour Moufid. Fixes bug 4059.
7288 - When a hidden service turns an extra service-side introduction
7289 circuit into a general-purpose circuit, free the rend_data and
7290 intro_key fields first, so we won't leak memory if the circuit
7291 is cannibalized for use as another service-side introduction
7292 circuit. Bugfix on 0.2.1.7-alpha; fixes bug 4251.
7293 - Bridges now skip DNS self-tests, to act a little more stealthily.
7294 Fixes bug 4201; bugfix on 0.2.0.3-alpha, which first introduced
7295 bridges. Patch by "warms0x".
7296 - Fix internal bug-checking logic that was supposed to catch
7297 failures in digest generation so that it will fail more robustly
7298 if we ask for a nonexistent algorithm. Found by Coverity Scan.
7299 Bugfix on 0.2.2.1-alpha; fixes Coverity CID 479.
7300 - Report any failure in init_keys() calls launched because our
7301 IP address has changed. Spotted by Coverity Scan. Bugfix on
7302 0.1.1.4-alpha; fixes CID 484.
7304 o Minor bugfixes (log messages and documentation):
7305 - Remove a confusing dollar sign from the example fingerprint in the
7306 man page, and also make the example fingerprint a valid one. Fixes
7307 bug 4309; bugfix on 0.2.1.3-alpha.
7308 - The next version of Windows will be called Windows 8, and it has
7309 a major version of 6, minor version of 2. Correctly identify that
7310 version instead of calling it "Very recent version". Resolves
7311 ticket 4153; reported by funkstar.
7312 - Downgrade log messages about circuit timeout calibration from
7313 "notice" to "info": they don't require or suggest any human
7314 intervention. Patch from Tom Lowenthal. Fixes bug 4063;
7315 bugfix on 0.2.2.14-alpha.
7318 - Turn on directory request statistics by default and include them in
7319 extra-info descriptors. Don't break if we have no GeoIP database.
7320 Backported from 0.2.3.1-alpha; implements ticket 3951.
7321 - Update to the October 4 2011 Maxmind GeoLite Country database.
7324 Changes in version 0.2.1.31 - 2011-10-26
7325 Tor 0.2.1.31 backports important security and privacy fixes for
7326 oldstable. This release is intended only for package maintainers and
7327 others who cannot use the 0.2.2 stable series. All others should be
7328 using Tor 0.2.2.x or newer.
7330 o Security fixes (also included in 0.2.2.x):
7331 - Replace all potentially sensitive memory comparison operations
7332 with versions whose runtime does not depend on the data being
7333 compared. This will help resist a class of attacks where an
7334 adversary can use variations in timing information to learn
7335 sensitive data. Fix for one case of bug 3122. (Safe memcmp
7336 implementation by Robert Ransom based partially on code by DJB.)
7337 - Fix an assert in parsing router descriptors containing IPv6
7338 addresses. This one took down the directory authorities when
7339 somebody tried some experimental code. Bugfix on 0.2.1.3-alpha.
7341 o Privacy/anonymity fixes (also included in 0.2.2.x):
7342 - Clients and bridges no longer send TLS certificate chains on
7343 outgoing OR connections. Previously, each client or bridge would
7344 use the same cert chain for all outgoing OR connections until
7345 its IP address changes, which allowed any relay that the client
7346 or bridge contacted to determine which entry guards it is using.
7347 Fixes CVE-2011-2768. Bugfix on 0.0.9pre5; found by "frosty_un".
7348 - If a relay receives a CREATE_FAST cell on a TLS connection, it
7349 no longer considers that connection as suitable for satisfying a
7350 circuit EXTEND request. Now relays can protect clients from the
7351 CVE-2011-2768 issue even if the clients haven't upgraded yet.
7352 - Bridges now refuse CREATE or CREATE_FAST cells on OR connections
7353 that they initiated. Relays could distinguish incoming bridge
7354 connections from client connections, creating another avenue for
7355 enumerating bridges. Fixes CVE-2011-2769. Bugfix on 0.2.0.3-alpha.
7356 Found by "frosty_un".
7357 - When receiving a hidden service descriptor, check that it is for
7358 the hidden service we wanted. Previously, Tor would store any
7359 hidden service descriptors that a directory gave it, whether it
7360 wanted them or not. This wouldn't have let an attacker impersonate
7361 a hidden service, but it did let directories pre-seed a client
7362 with descriptors that it didn't want. Bugfix on 0.0.6.
7363 - Avoid linkability based on cached hidden service descriptors: forget
7364 all hidden service descriptors cached as a client when processing a
7365 SIGNAL NEWNYM command. Fixes bug 3000; bugfix on 0.0.6.
7366 - Make the bridge directory authority refuse to answer directory
7367 requests for "all" descriptors. It used to include bridge
7368 descriptors in its answer, which was a major information leak.
7369 Found by "piebeer". Bugfix on 0.2.0.3-alpha.
7370 - Don't attach new streams to old rendezvous circuits after SIGNAL
7371 NEWNYM. Previously, we would keep using an existing rendezvous
7372 circuit if it remained open (i.e. if it were kept open by a
7373 long-lived stream, or if a new stream were attached to it before
7374 Tor could notice that it was old and no longer in use). Bugfix on
7375 0.1.1.15-rc; fixes bug 3375.
7377 o Minor bugfixes (also included in 0.2.2.x):
7378 - When we restart our relay, we might get a successful connection
7379 from the outside before we've started our reachability tests,
7380 triggering a warning: "ORPort found reachable, but I have no
7381 routerinfo yet. Failing to inform controller of success." This
7382 bug was harmless unless Tor is running under a controller
7383 like Vidalia, in which case the controller would never get a
7384 REACHABILITY_SUCCEEDED status event. Bugfix on 0.1.2.6-alpha;
7386 - Build correctly on OSX with zlib 1.2.4 and higher with all warnings
7387 enabled. Fixes bug 1526.
7388 - Remove undocumented option "-F" from tor-resolve: it hasn't done
7389 anything since 0.2.1.16-rc.
7390 - Avoid signed/unsigned comparisons by making SIZE_T_CEILING unsigned.
7391 None of the cases where we did this before were wrong, but by making
7392 this change we avoid warnings. Fixes bug 2475; bugfix on 0.2.1.28.
7393 - Fix a rare crash bug that could occur when a client was configured
7394 with a large number of bridges. Fixes bug 2629; bugfix on
7395 0.2.1.2-alpha. Bugfix by trac user "shitlei".
7396 - Correct the warning displayed when a rendezvous descriptor exceeds
7397 the maximum size. Fixes bug 2750; bugfix on 0.2.1.5-alpha. Found by
7399 - Fix an uncommon assertion failure when running with DNSPort under
7400 heavy load. Fixes bug 2933; bugfix on 0.2.0.1-alpha.
7401 - When warning about missing zlib development packages during compile,
7402 give the correct package names. Bugfix on 0.2.0.1-alpha.
7403 - Require that introduction point keys and onion keys have public
7404 exponent 65537. Bugfix on 0.2.0.10-alpha.
7405 - Do not crash when our configuration file becomes unreadable, for
7406 example due to a permissions change, between when we start up
7407 and when a controller calls SAVECONF. Fixes bug 3135; bugfix
7409 - Fix warnings from GCC 4.6's "-Wunused-but-set-variable" option.
7411 - Always NUL-terminate the sun_path field of a sockaddr_un before
7412 passing it to the kernel. (Not a security issue: kernels are
7413 smart enough to reject bad sockaddr_uns.) Found by Coverity;
7414 CID #428. Bugfix on Tor 0.2.0.3-alpha.
7415 - Don't stack-allocate the list of supplementary GIDs when we're
7416 about to log them. Stack-allocating NGROUPS_MAX gid_t elements
7417 could take up to 256K, which is way too much stack. Found by
7418 Coverity; CID #450. Bugfix on 0.2.1.7-alpha.
7420 o Minor bugfixes (only in 0.2.1.x):
7421 - Resume using micro-version numbers in 0.2.1.x: our Debian packages
7422 rely on them. Bugfix on 0.2.1.30.
7423 - Use git revisions instead of svn revisions when generating our
7424 micro-version numbers. Bugfix on 0.2.1.15-rc; fixes bug 2402.
7426 o Minor features (also included in 0.2.2.x):
7427 - Adjust the expiration time on our SSL session certificates to
7428 better match SSL certs seen in the wild. Resolves ticket 4014.
7429 - Allow nameservers with IPv6 address. Resolves bug 2574.
7430 - Update to the October 4 2011 Maxmind GeoLite Country database.
7433 Changes in version 0.2.3.5-alpha - 2011-09-28
7434 Tor 0.2.3.5-alpha fixes two bugs that make it possible to enumerate
7435 bridge relays; fixes an assertion error that many users started hitting
7436 today; and adds the ability to refill token buckets more often than
7437 once per second, allowing significant performance improvements.
7440 - Bridge relays now do their directory fetches inside Tor TLS
7441 connections, like all the other clients do, rather than connecting
7442 directly to the DirPort like public relays do. Removes another
7443 avenue for enumerating bridges. Fixes bug 4115; bugfix on 0.2.0.35.
7444 - Bridges relays now build circuits for themselves in a more similar
7445 way to how clients build them. Removes another avenue for
7446 enumerating bridges. Fixes bug 4124; bugfix on 0.2.0.3-alpha,
7447 when bridges were introduced.
7450 - Fix an "Assertion md->held_by_node == 1 failed" error that could
7451 occur when the same microdescriptor was referenced by two node_t
7452 objects at once. Fix for bug 4118; bugfix on Tor 0.2.3.1-alpha.
7454 o Major features (networking):
7455 - Add a new TokenBucketRefillInterval option to refill token buckets
7456 more frequently than once per second. This should improve network
7457 performance, alleviate queueing problems, and make traffic less
7458 bursty. Implements proposal 183; closes ticket 3630. Design by
7459 Florian Tschorsch and Björn Scheuermann; implementation by
7463 - Change an integer overflow check in the OpenBSD_Malloc code so
7464 that GCC is less likely to eliminate it as impossible. Patch
7465 from Mansour Moufid. Fixes bug 4059.
7467 o Minor bugfixes (usability):
7468 - Downgrade log messages about circuit timeout calibration from
7469 "notice" to "info": they don't require or suggest any human
7470 intervention. Patch from Tom Lowenthal. Fixes bug 4063;
7471 bugfix on 0.2.2.14-alpha.
7473 o Minor features (diagnostics):
7474 - When the system call to create a listener socket fails, log the
7475 error message explaining why. This may help diagnose bug 4027.
7478 Changes in version 0.2.3.4-alpha - 2011-09-13
7479 Tor 0.2.3.4-alpha includes the fixes from 0.2.2.33, including a slight
7480 tweak to Tor's TLS handshake that makes relays and bridges that run
7481 this new version reachable from Iran again. It also fixes a few new
7482 bugs in 0.2.3.x, and teaches relays to recognize when they're not
7483 listed in the network consensus and republish.
7485 o Major bugfixes (also part of 0.2.2.33):
7486 - Avoid an assertion failure when reloading a configuration with
7487 TrackExitHosts changes. Found and fixed by 'laruldan'. Fixes bug
7488 3923; bugfix on 0.2.2.25-alpha.
7490 o Minor features (security, also part of 0.2.2.33):
7491 - Check for replays of the public-key encrypted portion of an
7492 INTRODUCE1 cell, in addition to the current check for replays of
7493 the g^x value. This prevents a possible class of active attacks
7494 by an attacker who controls both an introduction point and a
7495 rendezvous point, and who uses the malleability of AES-CTR to
7496 alter the encrypted g^x portion of the INTRODUCE1 cell. We think
7497 that these attacks are infeasible (requiring the attacker to send
7498 on the order of zettabytes of altered cells in a short interval),
7499 but we'd rather block them off in case there are any classes of
7500 this attack that we missed. Reported by Willem Pinckaers.
7502 o Minor features (also part of 0.2.2.33):
7503 - Adjust the expiration time on our SSL session certificates to
7504 better match SSL certs seen in the wild. Resolves ticket 4014.
7505 - Change the default required uptime for a relay to be accepted as
7506 a HSDir (hidden service directory) from 24 hours to 25 hours.
7507 Improves on 0.2.0.10-alpha; resolves ticket 2649.
7508 - Add a VoteOnHidServDirectoriesV2 config option to allow directory
7509 authorities to abstain from voting on assignment of the HSDir
7510 consensus flag. Related to bug 2649.
7511 - Update to the September 6 2011 Maxmind GeoLite Country database.
7513 o Minor bugfixes (also part of 0.2.2.33):
7514 - Demote the 'replay detected' log message emitted when a hidden
7515 service receives the same Diffie-Hellman public key in two different
7516 INTRODUCE2 cells to info level. A normal Tor client can cause that
7517 log message during its normal operation. Bugfix on 0.2.1.6-alpha;
7518 fixes part of bug 2442.
7519 - Demote the 'INTRODUCE2 cell is too {old,new}' log message to info
7520 level. There is nothing that a hidden service's operator can do
7521 to fix its clients' clocks. Bugfix on 0.2.1.6-alpha; fixes part
7523 - Clarify a log message specifying the characters permitted in
7524 HiddenServiceAuthorizeClient client names. Previously, the log
7525 message said that "[A-Za-z0-9+-_]" were permitted; that could have
7526 given the impression that every ASCII character between "+" and "_"
7527 was permitted. Now we say "[A-Za-z0-9+_-]". Bugfix on 0.2.1.5-alpha.
7529 o Build fixes (also part of 0.2.2.33):
7530 - Clean up some code issues that prevented Tor from building on older
7531 BSDs. Fixes bug 3894; reported by "grarpamp".
7532 - Search for a platform-specific version of "ar" when cross-compiling.
7533 Should fix builds on iOS. Resolves bug 3909, found by Marco Bonetti.
7536 - Fix a bug where the SocksPort option (for example) would get
7537 ignored and replaced by the default if a SocksListenAddress
7538 option was set. Bugfix on 0.2.3.3-alpha; fixes bug 3936. Fix by
7542 - Relays now try regenerating and uploading their descriptor more
7543 frequently if they are not listed in the consensus, or if the
7544 version of their descriptor listed in the consensus is too
7545 old. This fix should prevent situations where a server declines
7546 to re-publish itself because it has done so too recently, even
7547 though the authorities decided not to list its recent-enough
7548 descriptor. Fix for bug 3327.
7551 - Relays now include a reason for regenerating their descriptors
7552 in an HTTP header when uploading to the authorities. This will
7553 make it easier to debug descriptor-upload issues in the future.
7554 - When starting as root and then changing our UID via the User
7555 control option, and we have a ControlSocket configured, make sure
7556 that the ControlSocket is owned by the same account that Tor will
7557 run under. Implements ticket 3421; fix by Jérémy Bobbio.
7560 - Abort if tor_vasprintf fails in connection_printf_to_buf (a
7561 utility function used in the control-port code). This shouldn't
7562 ever happen unless Tor is completely out of memory, but if it did
7563 happen and Tor somehow recovered from it, Tor could have sent a log
7564 message to a control port in the middle of a reply to a controller
7565 command. Fixes part of bug 3428; bugfix on 0.1.2.3-alpha.
7566 - Make 'FetchUselessDescriptors' cause all descriptor types and
7567 all consensus types (including microdescriptors) to get fetched.
7568 Fixes bug 3851; bugfix on 0.2.3.1-alpha.
7571 - Make a new "entry connection" struct as an internal subtype of "edge
7572 connection", to simplify the code and make exit connections smaller.
7575 Changes in version 0.2.2.33 - 2011-09-13
7576 Tor 0.2.2.33 fixes several bugs, and includes a slight tweak to Tor's
7577 TLS handshake that makes relays and bridges that run this new version
7578 reachable from Iran again.
7581 - Avoid an assertion failure when reloading a configuration with
7582 TrackExitHosts changes. Found and fixed by 'laruldan'. Fixes bug
7583 3923; bugfix on 0.2.2.25-alpha.
7585 o Minor features (security):
7586 - Check for replays of the public-key encrypted portion of an
7587 INTRODUCE1 cell, in addition to the current check for replays of
7588 the g^x value. This prevents a possible class of active attacks
7589 by an attacker who controls both an introduction point and a
7590 rendezvous point, and who uses the malleability of AES-CTR to
7591 alter the encrypted g^x portion of the INTRODUCE1 cell. We think
7592 that these attacks are infeasible (requiring the attacker to send
7593 on the order of zettabytes of altered cells in a short interval),
7594 but we'd rather block them off in case there are any classes of
7595 this attack that we missed. Reported by Willem Pinckaers.
7598 - Adjust the expiration time on our SSL session certificates to
7599 better match SSL certs seen in the wild. Resolves ticket 4014.
7600 - Change the default required uptime for a relay to be accepted as
7601 a HSDir (hidden service directory) from 24 hours to 25 hours.
7602 Improves on 0.2.0.10-alpha; resolves ticket 2649.
7603 - Add a VoteOnHidServDirectoriesV2 config option to allow directory
7604 authorities to abstain from voting on assignment of the HSDir
7605 consensus flag. Related to bug 2649.
7606 - Update to the September 6 2011 Maxmind GeoLite Country database.
7608 o Minor bugfixes (documentation and log messages):
7609 - Correct the man page to explain that HashedControlPassword and
7610 CookieAuthentication can both be set, in which case either method
7611 is sufficient to authenticate to Tor. Bugfix on 0.2.0.7-alpha,
7612 when we decided to allow these config options to both be set. Issue
7614 - Demote the 'replay detected' log message emitted when a hidden
7615 service receives the same Diffie-Hellman public key in two different
7616 INTRODUCE2 cells to info level. A normal Tor client can cause that
7617 log message during its normal operation. Bugfix on 0.2.1.6-alpha;
7618 fixes part of bug 2442.
7619 - Demote the 'INTRODUCE2 cell is too {old,new}' log message to info
7620 level. There is nothing that a hidden service's operator can do
7621 to fix its clients' clocks. Bugfix on 0.2.1.6-alpha; fixes part
7623 - Clarify a log message specifying the characters permitted in
7624 HiddenServiceAuthorizeClient client names. Previously, the log
7625 message said that "[A-Za-z0-9+-_]" were permitted; that could have
7626 given the impression that every ASCII character between "+" and "_"
7627 was permitted. Now we say "[A-Za-z0-9+_-]". Bugfix on 0.2.1.5-alpha.
7630 - Provide a substitute implementation of lround() for MSVC, which
7631 apparently lacks it. Patch from Gisle Vanem.
7632 - Clean up some code issues that prevented Tor from building on older
7633 BSDs. Fixes bug 3894; reported by "grarpamp".
7634 - Search for a platform-specific version of "ar" when cross-compiling.
7635 Should fix builds on iOS. Resolves bug 3909, found by Marco Bonetti.
7638 Changes in version 0.2.3.3-alpha - 2011-09-01
7639 Tor 0.2.3.3-alpha adds a new "stream isolation" feature to improve Tor's
7640 security, and provides client-side support for the microdescriptor
7641 and optimistic data features introduced earlier in the 0.2.3.x
7642 series. It also includes numerous critical bugfixes in the (optional)
7643 bufferevent-based networking backend.
7645 o Major features (stream isolation):
7646 - You can now configure Tor so that streams from different
7647 applications are isolated on different circuits, to prevent an
7648 attacker who sees your streams as they leave an exit node from
7649 linking your sessions to one another. To do this, choose some way
7650 to distinguish the applications: have them connect to different
7651 SocksPorts, or have one of them use SOCKS4 while the other uses
7652 SOCKS5, or have them pass different authentication strings to the
7653 SOCKS proxy. Then, use the new SocksPort syntax to configure the
7654 degree of isolation you need. This implements Proposal 171.
7655 - There's a new syntax for specifying multiple client ports (such as
7656 SOCKSPort, TransPort, DNSPort, NATDPort): you can now just declare
7657 multiple *Port entries with full addr:port syntax on each.
7658 The old *ListenAddress format is still supported, but you can't
7659 mix it with the new *Port syntax.
7661 o Major features (other):
7662 - Enable microdescriptor fetching by default for clients. This allows
7663 clients to download a much smaller amount of directory information.
7664 To disable it (and go back to the old-style consensus and
7665 descriptors), set "UseMicrodescriptors 0" in your torrc file.
7666 - Tor's firewall-helper feature, introduced in 0.2.3.1-alpha (see the
7667 "PortForwarding" config option), now supports Windows.
7668 - When using an exit relay running 0.2.3.x, clients can now
7669 "optimistically" send data before the exit relay reports that
7670 the stream has opened. This saves a round trip when starting
7671 connections where the client speaks first (such as web browsing).
7672 This behavior is controlled by a consensus parameter (currently
7673 disabled). To turn it on or off manually, use the "OptimisticData"
7674 torrc option. Implements proposal 181; code by Ian Goldberg.
7676 o Major bugfixes (bufferevents, fixes on 0.2.3.1-alpha):
7677 - When using IOCP on Windows, we need to enable Libevent windows
7679 - The IOCP backend now works even when the user has not specified
7680 the (internal, debugging-only) _UseFilteringSSLBufferevents option.
7681 Fixes part of bug 3752.
7682 - Correctly record the bytes we've read and written when using
7683 bufferevents, so that we can include them in our bandwidth history
7684 and advertised bandwidth. Fixes bug 3803.
7685 - Apply rate-limiting only at the bottom of a chain of filtering
7686 bufferevents. This prevents us from filling up internal read
7687 buffers and violating rate-limits when filtering bufferevents
7688 are enabled. Fixes part of bug 3804.
7689 - Add high-watermarks to the output buffers for filtered
7690 bufferevents. This prevents us from filling up internal write
7691 buffers and wasting CPU cycles when filtering bufferevents are
7692 enabled. Fixes part of bug 3804.
7693 - Correctly notice when data has been written from a bufferevent
7694 without flushing it completely. Fixes bug 3805.
7695 - Fix a bug where server-side tunneled bufferevent-based directory
7696 streams would get closed prematurely. Fixes bug 3814.
7697 - Fix a use-after-free error with per-connection rate-limiting
7698 buckets. Fixes bug 3888.
7700 o Major bugfixes (also part of 0.2.2.31-rc):
7701 - If we're configured to write our ControlPorts to disk, only write
7702 them after switching UID and creating the data directory. This way,
7703 we don't fail when starting up with a nonexistent DataDirectory
7704 and a ControlPortWriteToFile setting based on that directory. Fixes
7705 bug 3747; bugfix on Tor 0.2.2.26-beta.
7708 - Added a new CONF_CHANGED event so that controllers can be notified
7709 of any configuration changes made by other controllers, or by the
7710 user. Implements ticket 1692.
7711 - Use evbuffer_copyout() in inspect_evbuffer(). This fixes a memory
7712 leak when using bufferevents, and lets Libevent worry about how to
7713 best copy data out of a buffer.
7714 - Replace files in stats/ rather than appending to them. Now that we
7715 include statistics in extra-info descriptors, it makes no sense to
7716 keep old statistics forever. Implements ticket 2930.
7718 o Minor features (build compatibility):
7719 - Limited, experimental support for building with nmake and MSVC.
7720 - Provide a substitute implementation of lround() for MSVC, which
7721 apparently lacks it. Patch from Gisle Vanem.
7723 o Minor features (also part of 0.2.2.31-rc):
7724 - Update to the August 2 2011 Maxmind GeoLite Country database.
7726 o Minor bugfixes (on 0.2.3.x-alpha):
7727 - Fix a spurious warning when parsing SOCKS requests with
7728 bufferevents enabled. Fixes bug 3615; bugfix on 0.2.3.2-alpha.
7729 - Get rid of a harmless warning that could happen on relays running
7730 with bufferevents. The warning was caused by someone doing an http
7731 request to a relay's orport. Also don't warn for a few related
7732 non-errors. Fixes bug 3700; bugfix on 0.2.3.1-alpha.
7734 o Minor bugfixes (on 2.2.x and earlier):
7735 - Correct the man page to explain that HashedControlPassword and
7736 CookieAuthentication can both be set, in which case either method
7737 is sufficient to authenticate to Tor. Bugfix on 0.2.0.7-alpha,
7738 when we decided to allow these config options to both be set. Issue
7740 - The "--quiet" and "--hush" options now apply not only to Tor's
7741 behavior before logs are configured, but also to Tor's behavior in
7742 the absense of configured logs. Fixes bug 3550; bugfix on
7745 o Minor bugfixes (also part of 0.2.2.31-rc):
7746 - Write several files in text mode, on OSes that distinguish text
7747 mode from binary mode (namely, Windows). These files are:
7748 'buffer-stats', 'dirreq-stats', and 'entry-stats' on relays
7749 that collect those statistics; 'client_keys' and 'hostname' for
7750 hidden services that use authentication; and (in the tor-gencert
7751 utility) newly generated identity and signing keys. Previously,
7752 we wouldn't specify text mode or binary mode, leading to an
7753 assertion failure. Fixes bug 3607. Bugfix on 0.2.1.1-alpha (when
7754 the DirRecordUsageByCountry option which would have triggered
7755 the assertion failure was added), although this assertion failure
7756 would have occurred in tor-gencert on Windows in 0.2.0.1-alpha.
7757 - Selectively disable deprecation warnings on OS X because Lion
7758 started deprecating the shipped copy of openssl. Fixes bug 3643.
7759 - Remove an extra pair of quotation marks around the error
7760 message in control-port STATUS_GENERAL BUG events. Bugfix on
7761 0.1.2.6-alpha; fixes bug 3732.
7762 - When unable to format an address as a string, report its value
7763 as "???" rather than reusing the last formatted address. Bugfix
7766 o Code simplifications and refactoring:
7767 - Rewrite the listener-selection logic so that parsing which ports
7768 we want to listen on is now separate from binding to the ports
7772 - Building Tor with bufferevent support now requires Libevent
7773 2.0.13-stable or later. Previous versions of Libevent had bugs in
7774 SSL-related bufferevents and related issues that would make Tor
7775 work badly with bufferevents. Requiring 2.0.13-stable also allows
7776 Tor with bufferevents to take advantage of Libevent APIs
7777 introduced after 2.0.8-rc.
7780 Changes in version 0.2.2.32 - 2011-08-27
7781 The Tor 0.2.2 release series is dedicated to the memory of Andreas
7782 Pfitzmann (1958-2010), a pioneer in anonymity and privacy research,
7783 a founder of the PETS community, a leader in our field, a mentor,
7784 and a friend. He left us with these words: "I had the possibility
7785 to contribute to this world that is not as it should be. I hope I
7786 could help in some areas to make the world a better place, and that
7787 I could also encourage other people to be engaged in improving the
7788 world. Please, stay engaged. This world needs you, your love, your
7789 initiative -- now I cannot be part of that anymore."
7791 Tor 0.2.2.32, the first stable release in the 0.2.2 branch, is finally
7792 ready. More than two years in the making, this release features improved
7793 client performance and hidden service reliability, better compatibility
7794 for Android, correct behavior for bridges that listen on more than
7795 one address, more extensible and flexible directory object handling,
7796 better reporting of network statistics, improved code security, and
7797 many many other features and bugfixes.
7800 Changes in version 0.2.2.31-rc - 2011-08-17
7801 Tor 0.2.2.31-rc is the second and hopefully final release candidate
7802 for the Tor 0.2.2.x series.
7805 - Remove an extra pair of quotation marks around the error
7806 message in control-port STATUS_GENERAL BUG events. Bugfix on
7807 0.1.2.6-alpha; fixes bug 3732.
7808 - If we're configured to write our ControlPorts to disk, only write
7809 them after switching UID and creating the data directory. This way,
7810 we don't fail when starting up with a nonexistent DataDirectory
7811 and a ControlPortWriteToFile setting based on that directory. Fixes
7812 bug 3747; bugfix on Tor 0.2.2.26-beta.
7815 - Update to the August 2 2011 Maxmind GeoLite Country database.
7818 - Allow GETINFO fingerprint to return a fingerprint even when
7819 we have not yet built a router descriptor. Fixes bug 3577;
7820 bugfix on 0.2.0.1-alpha.
7821 - Write several files in text mode, on OSes that distinguish text
7822 mode from binary mode (namely, Windows). These files are:
7823 'buffer-stats', 'dirreq-stats', and 'entry-stats' on relays
7824 that collect those statistics; 'client_keys' and 'hostname' for
7825 hidden services that use authentication; and (in the tor-gencert
7826 utility) newly generated identity and signing keys. Previously,
7827 we wouldn't specify text mode or binary mode, leading to an
7828 assertion failure. Fixes bug 3607. Bugfix on 0.2.1.1-alpha (when
7829 the DirRecordUsageByCountry option which would have triggered
7830 the assertion failure was added), although this assertion failure
7831 would have occurred in tor-gencert on Windows in 0.2.0.1-alpha.
7832 - Selectively disable deprecation warnings on OS X because Lion
7833 started deprecating the shipped copy of openssl. Fixes bug 3643.
7834 - When unable to format an address as a string, report its value
7835 as "???" rather than reusing the last formatted address. Bugfix
7839 Changes in version 0.2.3.2-alpha - 2011-07-18
7840 Tor 0.2.3.2-alpha introduces two new experimental features:
7841 microdescriptors and pluggable transports. It also continues cleaning
7842 up a variety of recently introduced features.
7845 - Clients can now use microdescriptors instead of regular descriptors
7846 to build circuits. Microdescriptors are authority-generated
7847 summaries of regular descriptors' contents, designed to change
7848 very rarely (see proposal 158 for details). This feature is
7849 designed to save bandwidth, especially for clients on slow internet
7850 connections. It's off by default for now, since nearly no caches
7851 support it, but it will be on-by-default for clients in a future
7852 version. You can use the UseMicrodescriptors option to turn it on.
7853 - Tor clients using bridges can now be configured to use a separate
7854 'transport' proxy for each bridge. This approach helps to resist
7855 censorship by allowing bridges to use protocol obfuscation
7856 plugins. It implements part of proposal 180. Implements ticket 2841.
7857 - While we're trying to bootstrap, record how many TLS connections
7858 fail in each state, and report which states saw the most failures
7859 in response to any bootstrap failures. This feature may speed up
7860 diagnosis of censorship events. Implements ticket 3116.
7862 o Major bugfixes (on 0.2.3.1-alpha):
7863 - When configuring a large set of nodes in EntryNodes (as with
7864 'EntryNodes {cc}' or 'EntryNodes 1.1.1.1/16'), choose only a
7865 random subset to be guards, and choose them in random
7866 order. Fixes bug 2798.
7867 - Tor could crash when remembering a consensus in a non-used consensus
7868 flavor without having a current consensus set. Fixes bug 3361.
7869 - Comparing an unknown address to a microdescriptor's shortened exit
7870 policy would always give a "rejected" result. Fixes bug 3599.
7871 - Using microdescriptors as a client no longer prevents Tor from
7872 uploading and downloading hidden service descriptors. Fixes
7876 - Allow nameservers with IPv6 address. Resolves bug 2574.
7877 - Accept attempts to include a password authenticator in the
7878 handshake, as supported by SOCKS5. This handles SOCKS clients that
7879 don't know how to omit a password when authenticating. Resolves
7881 - When configuring a large set of nodes in EntryNodes, and there are
7882 enough of them listed as Guard so that we don't need to consider
7883 the non-guard entries, prefer the ones listed with the Guard flag.
7884 - Check for and recover from inconsistency in the microdescriptor
7885 cache. This will make it harder for us to accidentally free a
7886 microdescriptor without removing it from the appropriate data
7887 structures. Fixes issue 3135; issue noted by "wanoskarnet".
7888 - Log SSL state transitions at log level DEBUG, log domain
7889 HANDSHAKE. This can be useful for debugging censorship events.
7890 Implements ticket 3264.
7891 - Add port 6523 (Gobby) to LongLivedPorts. Patch by intrigeri;
7892 implements ticket 3439.
7894 o Minor bugfixes (on 0.2.3.1-alpha):
7895 - Do not free all general-purpose regular descriptors just
7896 because microdescriptor use is enabled. Fixes bug 3113.
7897 - Correctly link libevent_openssl when --enable-static-libevent
7898 is passed to configure. Fixes bug 3118.
7899 - Bridges should not complain during their heartbeat log messages that
7900 they are unlisted in the consensus: that's more or less the point
7901 of being a bridge. Fixes bug 3183.
7902 - Report a SIGNAL event to controllers when acting on a delayed
7903 SIGNAL NEWNYM command. Previously, we would report a SIGNAL
7904 event to the controller if we acted on a SIGNAL NEWNYM command
7905 immediately, and otherwise not report a SIGNAL event for the
7906 command at all. Fixes bug 3349.
7907 - Fix a crash when handling the SIGNAL controller command or
7908 reporting ERR-level status events with bufferevents enabled. Found
7909 by Robert Ransom. Fixes bug 3367.
7910 - Always ship the tor-fw-helper manpage in our release tarballs.
7911 Fixes bug 3389. Reported by Stephen Walker.
7912 - Fix a class of double-mark-for-close bugs when bufferevents
7913 are enabled. Fixes bug 3403.
7914 - Update tor-fw-helper to support libnatpmp-20110618. Fixes bug 3434.
7915 - Add SIGNAL to the list returned by the 'GETINFO events/names'
7916 control-port command. Fixes part of bug 3465.
7917 - Prevent using negative indices during unit test runs when read_all()
7918 fails. Spotted by coverity.
7919 - Fix a rare memory leak when checking the nodelist without it being
7920 present. Found by coverity.
7921 - Only try to download a microdescriptor-flavored consensus from
7922 a directory cache that provides them.
7924 o Minor bugfixes (on 0.2.2.x and earlier):
7925 - Assert that hidden-service-related operations are not performed
7926 using single-hop circuits. Previously, Tor would assert that
7927 client-side streams are not attached to single-hop circuits,
7928 but not that other sensitive operations on the client and service
7929 side are not performed using single-hop circuits. Fixes bug 3332;
7931 - Don't publish a new relay descriptor when we reload our onion key,
7932 unless the onion key has actually changed. Fixes bug 3263 and
7933 resolves another cause of bug 1810. Bugfix on 0.1.1.11-alpha.
7934 - Allow GETINFO fingerprint to return a fingerprint even when
7935 we have not yet built a router descriptor. Fixes bug 3577;
7936 bugfix on 0.2.0.1-alpha.
7937 - Make 'tor --digests' list hashes of all Tor source files. Bugfix
7938 on 0.2.2.4-alpha; fixes bug 3427.
7940 o Code simplification and refactoring:
7941 - Use tor_sscanf() in place of scanf() in more places through the
7942 code. This makes us a little more locale-independent, and
7943 should help shut up code-analysis tools that can't tell
7944 a safe sscanf string from a dangerous one.
7945 - Use tt_assert(), not tor_assert(), for checking for test failures.
7946 This makes the unit tests more able to go on in the event that
7948 - Split connection_about_to_close() into separate functions for each
7952 - On Windows, we now define the _WIN32_WINNT macros only if they
7953 are not already defined. This lets the person building Tor decide,
7954 if they want, to require a later version of Windows.
7957 Changes in version 0.2.2.30-rc - 2011-07-07
7958 Tor 0.2.2.30-rc is the first release candidate for the Tor 0.2.2.x
7959 series. It fixes a few smaller bugs, but generally appears stable.
7960 Please test it and let us know whether it is!
7963 - Send a SUCCEEDED stream event to the controller when a reverse
7964 resolve succeeded. Fixes bug 3536; bugfix on 0.0.8pre1. Issue
7965 discovered by katmagic.
7966 - Always NUL-terminate the sun_path field of a sockaddr_un before
7967 passing it to the kernel. (Not a security issue: kernels are
7968 smart enough to reject bad sockaddr_uns.) Found by Coverity;
7969 CID #428. Bugfix on Tor 0.2.0.3-alpha.
7970 - Don't stack-allocate the list of supplementary GIDs when we're
7971 about to log them. Stack-allocating NGROUPS_MAX gid_t elements
7972 could take up to 256K, which is way too much stack. Found by
7973 Coverity; CID #450. Bugfix on 0.2.1.7-alpha.
7974 - Add BUILDTIMEOUT_SET to the list returned by the 'GETINFO
7975 events/names' control-port command. Bugfix on 0.2.2.9-alpha;
7976 fixes part of bug 3465.
7977 - Fix a memory leak when receiving a descriptor for a hidden
7978 service we didn't ask for. Found by Coverity; CID #30. Bugfix
7982 - Update to the July 1 2011 Maxmind GeoLite Country database.
7985 Changes in version 0.2.2.29-beta - 2011-06-20
7986 Tor 0.2.2.29-beta reverts an accidental behavior change for users who
7987 have bridge lines in their torrc but don't want to use them; gets
7988 us closer to having the control socket feature working on Debian;
7989 and fixes a variety of smaller bugs.
7992 - Revert the UseBridges option to its behavior before 0.2.2.28-beta.
7993 When we changed the default behavior to "use bridges if any
7994 are listed in the torrc", we surprised users who had bridges
7995 in their torrc files but who didn't actually want to use them.
7996 Partial resolution for bug 3354.
7999 - Don't attach new streams to old rendezvous circuits after SIGNAL
8000 NEWNYM. Previously, we would keep using an existing rendezvous
8001 circuit if it remained open (i.e. if it were kept open by a
8002 long-lived stream, or if a new stream were attached to it before
8003 Tor could notice that it was old and no longer in use). Bugfix on
8004 0.1.1.15-rc; fixes bug 3375.
8007 - Fix a bug when using ControlSocketsGroupWritable with User. The
8008 directory's group would be checked against the current group, not
8009 the configured group. Patch by Jérémy Bobbio. Fixes bug 3393;
8010 bugfix on 0.2.2.26-beta.
8011 - Make connection_printf_to_buf()'s behavior sane. Its callers
8012 expect it to emit a CRLF iff the format string ends with CRLF;
8013 it actually emitted a CRLF iff (a) the format string ended with
8014 CRLF or (b) the resulting string was over 1023 characters long or
8015 (c) the format string did not end with CRLF *and* the resulting
8016 string was 1021 characters long or longer. Bugfix on 0.1.1.9-alpha;
8017 fixes part of bug 3407.
8018 - Make send_control_event_impl()'s behavior sane. Its callers
8019 expect it to always emit a CRLF at the end of the string; it
8020 might have emitted extra control characters as well. Bugfix on
8021 0.1.1.9-alpha; fixes another part of bug 3407.
8022 - Make crypto_rand_int() check the value of its input correctly.
8023 Previously, it accepted values up to UINT_MAX, but could return a
8024 negative number if given a value above INT_MAX+1. Found by George
8025 Kadianakis. Fixes bug 3306; bugfix on 0.2.2pre14.
8026 - Avoid a segfault when reading a malformed circuit build state
8027 with more than INT_MAX entries. Found by wanoskarnet. Bugfix on
8029 - When asked about a DNS record type we don't support via a
8030 client DNSPort, reply with NOTIMPL rather than an empty
8031 reply. Patch by intrigeri. Fixes bug 3369; bugfix on 2.0.1-alpha.
8032 - Fix a rare memory leak during stats writing. Found by coverity.
8035 - Update to the June 1 2011 Maxmind GeoLite Country database.
8037 o Code simplifications and refactoring:
8038 - Remove some dead code as indicated by coverity.
8039 - Remove a few dead assignments during router parsing. Found by
8041 - Add some forgotten return value checks during unit tests. Found
8043 - Don't use 1-bit wide signed bit fields. Found by coverity.
8046 Changes in version 0.2.2.28-beta - 2011-06-04
8047 Tor 0.2.2.28-beta makes great progress towards a new stable release: we
8048 fixed a big bug in whether relays stay in the consensus consistently,
8049 we moved closer to handling bridges and hidden services correctly,
8050 and we started the process of better handling the dreaded "my Vidalia
8051 died, and now my Tor demands a password when I try to reconnect to it"
8055 - Don't decide to make a new descriptor when receiving a HUP signal.
8056 This bug has caused a lot of 0.2.2.x relays to disappear from the
8057 consensus periodically. Fixes the most common case of triggering
8058 bug 1810; bugfix on 0.2.2.7-alpha.
8059 - Actually allow nameservers with IPv6 addresses. Fixes bug 2574.
8060 - Don't try to build descriptors if "ORPort auto" is set and we
8061 don't know our actual ORPort yet. Fix for bug 3216; bugfix on
8063 - Resolve a crash that occurred when setting BridgeRelay to 1 with
8064 accounting enabled. Fixes bug 3228; bugfix on 0.2.2.18-alpha.
8065 - Apply circuit timeouts to opened hidden-service-related circuits
8066 based on the correct start time. Previously, we would apply the
8067 circuit build timeout based on time since the circuit's creation;
8068 it was supposed to be applied based on time since the circuit
8069 entered its current state. Bugfix on 0.0.6; fixes part of bug 1297.
8070 - Use the same circuit timeout for client-side introduction
8071 circuits as for other four-hop circuits, rather than the timeout
8072 for single-hop directory-fetch circuits; the shorter timeout may
8073 have been appropriate with the static circuit build timeout in
8074 0.2.1.x and earlier, but caused many hidden service access attempts
8075 to fail with the adaptive CBT introduced in 0.2.2.2-alpha. Bugfix
8076 on 0.2.2.2-alpha; fixes another part of bug 1297.
8077 - In ticket 2511 we fixed a case where you could use an unconfigured
8078 bridge if you had configured it as a bridge the last time you ran
8079 Tor. Now fix another edge case: if you had configured it as a bridge
8080 but then switched to a different bridge via the controller, you
8081 would still be willing to use the old one. Bugfix on 0.2.0.1-alpha;
8085 - Add an __OwningControllerProcess configuration option and a
8086 TAKEOWNERSHIP control-port command. Now a Tor controller can ensure
8087 that when it exits, Tor will shut down. Implements feature 3049.
8088 - If "UseBridges 1" is set and no bridges are configured, Tor will
8089 now refuse to build any circuits until some bridges are set.
8090 If "UseBridges auto" is set, Tor will use bridges if they are
8091 configured and we are not running as a server, but otherwise will
8092 make circuits as usual. The new default is "auto". Patch by anonym,
8093 so the Tails LiveCD can stop automatically revealing you as a Tor
8097 - Fix warnings from GCC 4.6's "-Wunused-but-set-variable" option.
8098 - Remove a trailing asterisk from "exit-policy/default" in the
8099 output of the control port command "GETINFO info/names". Bugfix
8101 - Use a wide type to hold sockets when built for 64-bit Windows builds.
8103 - Warn when the user configures two HiddenServiceDir lines that point
8104 to the same directory. Bugfix on 0.0.6 (the version introducing
8105 HiddenServiceDir); fixes bug 3289.
8106 - Remove dead code from rend_cache_lookup_v2_desc_as_dir. Fixes
8107 part of bug 2748; bugfix on 0.2.0.10-alpha.
8108 - Log malformed requests for rendezvous descriptors as protocol
8109 warnings, not warnings. Also, use a more informative log message
8110 in case someone sees it at log level warning without prior
8111 info-level messages. Fixes the other part of bug 2748; bugfix
8113 - Clear the table recording the time of the last request for each
8114 hidden service descriptor from each HS directory on SIGNAL NEWNYM.
8115 Previously, we would clear our HS descriptor cache on SIGNAL
8116 NEWNYM, but if we had previously retrieved a descriptor (or tried
8117 to) from every directory responsible for it, we would refuse to
8118 fetch it again for up to 15 minutes. Bugfix on 0.2.2.25-alpha;
8120 - Fix a log message that said "bits" while displaying a value in
8121 bytes. Found by wanoskarnet. Fixes bug 3318; bugfix on
8123 - When checking for 1024-bit keys, check for 1024 bits, not 128
8124 bytes. This allows Tor to correctly discard keys of length 1017
8125 through 1023. Bugfix on 0.0.9pre5.
8128 - Relays now log the reason for publishing a new relay descriptor,
8129 so we have a better chance of hunting down instances of bug 1810.
8130 Resolves ticket 3252.
8131 - Revise most log messages that refer to nodes by nickname to
8132 instead use the "$key=nickname at address" format. This should be
8133 more useful, especially since nicknames are less and less likely
8134 to be unique. Resolves ticket 3045.
8135 - Log (at info level) when purging pieces of hidden-service-client
8136 state because of SIGNAL NEWNYM.
8139 - Remove undocumented option "-F" from tor-resolve: it hasn't done
8140 anything since 0.2.1.16-rc.
8143 Changes in version 0.2.2.27-beta - 2011-05-18
8144 Tor 0.2.2.27-beta fixes a bridge-related stability bug in the previous
8145 release, and also adds a few more general bugfixes.
8148 - Fix a crash bug when changing bridges in a running Tor process.
8149 Fixes bug 3213; bugfix on 0.2.2.26-beta.
8150 - When the controller configures a new bridge, don't wait 10 to 60
8151 seconds before trying to fetch its descriptor. Bugfix on
8152 0.2.0.3-alpha; fixes bug 3198 (suggested by 2355).
8155 - Require that onion keys have exponent 65537 in microdescriptors too.
8156 Fixes more of bug 3207; bugfix on 0.2.2.26-beta.
8157 - Tor used to limit HttpProxyAuthenticator values to 48 characters.
8158 Changed the limit to 512 characters by removing base64 newlines.
8159 Fixes bug 2752. Fix by Michael Yakubovich.
8160 - When a client starts or stops using bridges, never use a circuit
8161 that was built before the configuration change. This behavior could
8162 put at risk a user who uses bridges to ensure that her traffic
8163 only goes to the chosen addresses. Bugfix on 0.2.0.3-alpha; fixes
8167 Changes in version 0.2.2.26-beta - 2011-05-17
8168 Tor 0.2.2.26-beta fixes a variety of potential privacy problems. It
8169 also introduces a new "socksport auto" approach that should make it
8170 easier to run multiple Tors on the same system, and does a lot of
8171 cleanup to get us closer to a release candidate.
8173 o Security/privacy fixes:
8174 - Replace all potentially sensitive memory comparison operations
8175 with versions whose runtime does not depend on the data being
8176 compared. This will help resist a class of attacks where an
8177 adversary can use variations in timing information to learn
8178 sensitive data. Fix for one case of bug 3122. (Safe memcmp
8179 implementation by Robert Ransom based partially on code by DJB.)
8180 - When receiving a hidden service descriptor, check that it is for
8181 the hidden service we wanted. Previously, Tor would store any
8182 hidden service descriptors that a directory gave it, whether it
8183 wanted them or not. This wouldn't have let an attacker impersonate
8184 a hidden service, but it did let directories pre-seed a client
8185 with descriptors that it didn't want. Bugfix on 0.0.6.
8186 - On SIGHUP, do not clear out all TrackHostExits mappings, client
8187 DNS cache entries, and virtual address mappings: that's what
8188 NEWNYM is for. Fixes bug 1345; bugfix on 0.1.0.1-rc.
8191 - The options SocksPort, ControlPort, and so on now all accept a
8192 value "auto" that opens a socket on an OS-selected port. A
8193 new ControlPortWriteToFile option tells Tor to write its
8194 actual control port or ports to a chosen file. If the option
8195 ControlPortFileGroupReadable is set, the file is created as
8196 group-readable. Now users can run two Tor clients on the same
8197 system without needing to manually mess with parameters. Resolves
8198 part of ticket 3076.
8199 - Set SO_REUSEADDR on all sockets, not just listeners. This should
8200 help busy exit nodes avoid running out of useable ports just
8201 because all the ports have been used in the near past. Resolves
8205 - New "GETINFO net/listeners/(type)" controller command to return
8206 a list of addresses and ports that are bound for listeners for a
8207 given connection type. This is useful when the user has configured
8208 "SocksPort auto" and the controller needs to know which port got
8209 chosen. Resolves another part of ticket 3076.
8210 - Add a new ControlSocketsGroupWritable configuration option: when
8211 it is turned on, ControlSockets are group-writeable by the default
8212 group of the current user. Patch by Jérémy Bobbio; implements
8214 - Tor now refuses to create a ControlSocket in a directory that is
8215 world-readable (or group-readable if ControlSocketsGroupWritable
8216 is 0). This is necessary because some operating systems do not
8217 enforce permissions on an AF_UNIX sockets. Permissions on the
8218 directory holding the socket, however, seems to work everywhere.
8219 - Rate-limit a warning about failures to download v2 networkstatus
8220 documents. Resolves part of bug 1352.
8221 - Backport code from 0.2.3.x that allows directory authorities to
8222 clean their microdescriptor caches. Needed to resolve bug 2230.
8223 - When an HTTPS proxy reports "403 Forbidden", we now explain
8224 what it means rather than calling it an unexpected status code.
8225 Closes bug 2503. Patch from Michael Yakubovich.
8226 - Update to the May 1 2011 Maxmind GeoLite Country database.
8229 - Authorities now clean their microdesc cache periodically and when
8230 reading from disk initially, not only when adding new descriptors.
8231 This prevents a bug where we could lose microdescriptors. Bugfix
8232 on 0.2.2.6-alpha. Fixes bug 2230.
8233 - Do not crash when our configuration file becomes unreadable, for
8234 example due to a permissions change, between when we start up
8235 and when a controller calls SAVECONF. Fixes bug 3135; bugfix
8237 - Avoid a bug that would keep us from replacing a microdescriptor
8238 cache on Windows. (We would try to replace the file while still
8239 holding it open. That's fine on Unix, but Windows doesn't let us
8240 do that.) Bugfix on 0.2.2.6-alpha; bug found by wanoskarnet.
8241 - Add missing explanations for the authority-related torrc options
8242 RephistTrackTime, BridgePassword, and V3AuthUseLegacyKey in the
8243 man page. Resolves issue 2379.
8244 - As an authority, do not upload our own vote or signature set to
8245 ourself. It would tell us nothing new, and as of 0.2.2.24-alpha,
8246 it would get flagged as a duplicate. Resolves bug 3026.
8247 - Accept hidden service descriptors if we think we might be a hidden
8248 service directory, regardless of what our consensus says. This
8249 helps robustness, since clients and hidden services can sometimes
8250 have a more up-to-date view of the network consensus than we do,
8251 and if they think that the directory authorities list us a HSDir,
8252 we might actually be one. Related to bug 2732; bugfix on
8254 - When a controller changes TrackHostExits, remove mappings for
8255 hosts that should no longer have their exits tracked. Bugfix on
8257 - When a controller changes VirtualAddrNetwork, remove any mappings
8258 for hosts that were automapped to the old network. Bugfix on
8260 - When a controller changes one of the AutomapHosts* options, remove
8261 any mappings for hosts that should no longer be automapped. Bugfix
8263 - Do not reset the bridge descriptor download status every time we
8264 re-parse our configuration or get a configuration change. Fixes
8265 bug 3019; bugfix on 0.2.0.3-alpha.
8267 o Minor bugfixes (code cleanup):
8268 - When loading the microdesc journal, remember its current size.
8269 In 0.2.2, this helps prevent the microdesc journal from growing
8270 without limit on authorities (who are the only ones to use it in
8271 0.2.2). Fixes a part of bug 2230; bugfix on 0.2.2.6-alpha.
8272 Fix posted by "cypherpunks."
8273 - The microdesc journal is supposed to get rebuilt only if it is
8274 at least _half_ the length of the store, not _twice_ the length
8275 of the store. Bugfix on 0.2.2.6-alpha; fixes part of bug 2230.
8276 - Fix a potential null-pointer dereference while computing a
8277 consensus. Bugfix on tor-0.2.0.3-alpha, found with the help of
8279 - Avoid a possible null-pointer dereference when rebuilding the mdesc
8280 cache without actually having any descriptors to cache. Bugfix on
8281 0.2.2.6-alpha. Issue discovered using clang's static analyzer.
8282 - If we fail to compute the identity digest of a v3 legacy keypair,
8283 warn, and don't use a buffer-full of junk instead. Bugfix on
8284 0.2.1.1-alpha; fixes bug 3106.
8285 - Resolve an untriggerable issue in smartlist_string_num_isin(),
8286 where if the function had ever in the future been used to check
8287 for the presence of a too-large number, it would have given an
8288 incorrect result. (Fortunately, we only used it for 16-bit
8289 values.) Fixes bug 3175; bugfix on 0.1.0.1-rc.
8290 - Require that introduction point keys and onion handshake keys
8291 have a public exponent of 65537. Starts to fix bug 3207; bugfix
8295 - Caches no longer download and serve v2 networkstatus documents
8296 unless FetchV2Networkstatus flag is set: these documents haven't
8297 haven't been used by clients or relays since 0.2.0.x. Resolves
8301 Changes in version 0.2.3.1-alpha - 2011-05-05
8302 Tor 0.2.3.1-alpha adds some new experimental features, including support
8303 for an improved network IO backend, IOCP networking on Windows,
8304 microdescriptor caching, "fast-start" support for streams, and automatic
8305 home router configuration. There are also numerous internal improvements
8306 to try to make the code easier for developers to work with.
8308 This is the first alpha release in a new series, so expect there to be
8309 bugs. Users who would rather test out a more stable branch should
8310 stay with 0.2.2.x for now.
8313 - Tor can now optionally build with the "bufferevents" buffered IO
8314 backend provided by Libevent 2. To use this feature, make sure you
8315 have the latest possible version of Libevent, and pass the
8316 --enable-bufferevents flag to configure when building Tor from
8317 source. This feature will make our networking code more flexible,
8318 let us stack layers on each other, and let us use more efficient
8319 zero-copy transports where available.
8320 - As an experimental feature, Tor can use IOCP for networking on Windows.
8321 Once this code is tuned and optimized, it promises much better
8322 performance than the select-based backend we've used in the past. To
8323 try this feature, you must build Tor with Libevent 2, configure Tor
8324 with the "bufferevents" buffered IO backend, and add "DisableIOCP 0" to
8325 your torrc. There are known bugs here: only try this if you can help
8326 debug it as it breaks.
8327 - The EntryNodes option can now include country codes like {de} or IP
8328 addresses or network masks. Previously we had disallowed these options
8329 because we didn't have an efficient way to keep the list up to
8330 date. Fixes bug 1982, but see bug 2798 for an unresolved issue here.
8331 - Exit nodes now accept and queue data on not-yet-connected streams.
8332 Previously, the client wasn't allowed to send data until the stream was
8333 connected, which slowed down all connections. This change will enable
8334 clients to perform a "fast-start" on streams and send data without
8335 having to wait for a confirmation that the stream has opened. (Patch
8336 from Ian Goldberg; implements the server side of Proposal 174.)
8337 - Tor now has initial support for automatic port mapping on the many
8338 home routers that support NAT-PMP or UPnP. (Not yet supported on
8339 Windows). To build the support code, you'll need to have libnatpnp
8340 library and/or the libminiupnpc library, and you'll need to enable the
8341 feature specifically by passing "--enable-upnp" and/or
8342 "--enable-natpnp" to configure. To turn it on, use the new
8343 PortForwarding option.
8344 - Caches now download, cache, and serve multiple "flavors" of the
8345 consensus, including a flavor that describes microdescriptors.
8346 - Caches now download, cache, and serve microdescriptors -- small
8347 summaries of router descriptors that are authenticated by all of the
8348 directory authorities. Once enough caches are running this code,
8349 clients will be able to save significant amounts of directory bandwidth
8350 by downloading microdescriptors instead of router descriptors.
8353 - Make logging resolution configurable with a new LogTimeGranularity
8354 option, and change the default from 1 millisecond to 1 second.
8355 Implements enhancement 1668.
8356 - We log which torrc file we're using on startup. Implements ticket
8358 - Ordinarily, Tor does not count traffic from private addresses (like
8359 127.0.0.1 or 10.0.0.1) when calculating rate limits or accounting.
8360 There is now a new option, CountPrivateBandwidth, to disable this
8361 behavior. Patch from Daniel Cagara.
8362 - New --enable-static-tor configure option for building Tor as
8363 statically as possible. Idea, general hackery and thoughts from
8364 Alexei Czeskis, John Gilmore, Jacob Appelbaum. Implements ticket
8366 - If you set the NumCPUs option to 0, Tor will now try to detect how
8367 many CPUs you have. This is the new default behavior.
8368 - Turn on directory request statistics by default and include them in
8369 extra-info descriptors. Don't break if we have no GeoIP database.
8370 - Relays that set "ConnDirectionStatistics 1" write statistics on the
8371 bidirectional use of connections to disk every 24 hours.
8372 - Add a GeoIP file digest to the extra-info descriptor. Implements
8374 - The NodeFamily option -- which let you declare that you want to
8375 consider nodes to be part of a family whether they list themselves
8376 that way or not -- now allows IP address ranges and country codes.
8377 - Add a new 'Heartbeat' log message type to periodically log a message
8378 describing Tor's status at level Notice. This feature is meant for
8379 operators who log at notice, and want to make sure that their Tor
8380 server is still working. Implementation by George Kadianakis.
8382 o Minor bugfixes (on 0.2.2.25-alpha):
8383 - When loading the microdesc journal, remember its current size.
8384 In 0.2.2, this helps prevent the microdesc journal from growing
8385 without limit on authorities (who are the only ones to use it in
8386 0.2.2). Fixes a part of bug 2230; bugfix on 0.2.2.6-alpha.
8387 Fix posted by "cypherpunks."
8388 - The microdesc journal is supposed to get rebuilt only if it is
8389 at least _half_ the length of the store, not _twice_ the length
8390 of the store. Bugfix on 0.2.2.6-alpha; fixes part of bug 2230.
8391 - If as an authority we fail to compute the identity digest of a v3
8392 legacy keypair, warn, and don't use a buffer-full of junk instead.
8393 Bugfix on 0.2.1.1-alpha; fixes bug 3106.
8394 - Authorities now clean their microdesc cache periodically and when
8395 reading from disk initially, not only when adding new descriptors.
8396 This prevents a bug where we could lose microdescriptors. Bugfix
8399 o Minor features (controller):
8400 - Add a new SIGNAL event to the controller interface so that
8401 controllers can be notified when Tor handles a signal. Resolves
8402 issue 1955. Patch by John Brooks.
8403 - Add a new GETINFO option to get total bytes read and written. Patch
8404 from pipe, revised by atagar. Resolves ticket 2345.
8405 - Implement some GETINFO controller fields to provide information about
8406 the Tor process's pid, euid, username, and resource limits.
8409 - Our build system requires automake 1.6 or later to create the
8410 Makefile.in files. Previously, you could have used 1.4.
8411 This only affects developers and people building Tor from git;
8412 people who build Tor from the source distribution without changing
8413 the Makefile.am files should be fine.
8414 - Our autogen.sh script uses autoreconf to launch autoconf, automake, and
8415 so on. This is more robust against some of the failure modes
8416 associated with running the autotools pieces on their own.
8418 o Minor packaging issues:
8419 - On OpenSUSE, create the /var/run/tor directory on startup if it is not
8420 already created. Patch from Andreas Stieger. Fixes bug 2573.
8422 o Code simplifications and refactoring:
8423 - A major revision to our internal node-selecting and listing logic.
8424 Tor already had at least two major ways to look at the question of
8425 "which Tor servers do we know about": a list of router descriptors,
8426 and a list of entries in the current consensus. With
8427 microdescriptors, we're adding a third. Having so many systems
8428 without an abstraction layer over them was hurting the codebase.
8429 Now, we have a new "node_t" abstraction that presents a consistent
8430 interface to a client's view of a Tor node, and holds (nearly) all
8431 of the mutable state formerly in routerinfo_t and routerstatus_t.
8432 - The helper programs tor-gencert, tor-resolve, and tor-checkkey
8433 no longer link against Libevent: they never used it, but
8434 our library structure used to force them to link it.
8437 - Remove some old code to work around even older versions of Tor that
8438 used forked processes to handle DNS requests. Such versions of Tor
8439 are no longer in use as servers.
8441 o Documentation fixes:
8442 - Correct a broken faq link in the INSTALL file. Fixes bug 2307.
8443 - Add missing documentation for the authority-related torrc options
8444 RephistTrackTime, BridgePassword, and V3AuthUseLegacyKey. Resolves
8448 Changes in version 0.2.2.25-alpha - 2011-04-29
8449 Tor 0.2.2.25-alpha fixes many bugs: hidden service clients are more
8450 robust, routers no longer overreport their bandwidth, Win7 should crash
8451 a little less, and NEWNYM (as used by Vidalia's "new identity" button)
8452 now prevents hidden service-related activity from being linkable. It
8453 provides more information to Vidalia so you can see if your bridge is
8454 working. Also, 0.2.2.25-alpha revamps the Entry/Exit/ExcludeNodes and
8455 StrictNodes configuration options to make them more reliable, more
8456 understandable, and more regularly applied. If you use those options,
8457 please see the revised documentation for them in the manual page.
8460 - Relays were publishing grossly inflated bandwidth values because
8461 they were writing their state files wrong--now they write the
8462 correct value. Also, resume reading bandwidth history from the
8463 state file correctly. Fixes bug 2704; bugfix on 0.2.2.23-alpha.
8464 - Improve hidden service robustness: When we find that we have
8465 extended a hidden service's introduction circuit to a relay not
8466 listed as an introduction point in the HS descriptor we currently
8467 have, retry with an introduction point from the current
8468 descriptor. Previously we would just give up. Fixes bugs 1024 and
8469 1930; bugfix on 0.2.0.10-alpha.
8470 - Clients now stop trying to use an exit node associated with a given
8471 destination by TrackHostExits if they fail to reach that exit node.
8472 Fixes bug 2999. Bugfix on 0.2.0.20-rc.
8473 - Fix crash bug on platforms where gmtime and localtime can return
8474 NULL. Windows 7 users were running into this one. Fixes part of bug
8475 2077. Bugfix on all versions of Tor. Found by boboper.
8477 o Security and stability fixes:
8478 - Don't double-free a parsable, but invalid, microdescriptor, even if
8479 it is followed in the blob we're parsing by an unparsable
8480 microdescriptor. Fixes an issue reported in a comment on bug 2954.
8481 Bugfix on 0.2.2.6-alpha; fix by "cypherpunks".
8482 - If the Nickname configuration option isn't given, Tor would pick a
8483 nickname based on the local hostname as the nickname for a relay.
8484 Because nicknames are not very important in today's Tor and the
8485 "Unnamed" nickname has been implemented, this is now problematic
8486 behavior: It leaks information about the hostname without being
8487 useful at all. Fixes bug 2979; bugfix on 0.1.2.2-alpha, which
8488 introduced the Unnamed nickname. Reported by tagnaq.
8489 - Fix an uncommon assertion failure when running with DNSPort under
8490 heavy load. Fixes bug 2933; bugfix on 0.2.0.1-alpha.
8491 - Avoid linkability based on cached hidden service descriptors: forget
8492 all hidden service descriptors cached as a client when processing a
8493 SIGNAL NEWNYM command. Fixes bug 3000; bugfix on 0.0.6.
8496 - Export GeoIP information on bridge usage to controllers even if we
8497 have not yet been running for 24 hours. Now Vidalia bridge operators
8498 can get more accurate and immediate feedback about their
8499 contributions to the network.
8501 o Major features and bugfixes (node selection):
8502 - Revise and reconcile the meaning of the ExitNodes, EntryNodes,
8503 ExcludeEntryNodes, ExcludeExitNodes, ExcludeNodes, and StrictNodes
8504 options. Previously, we had been ambiguous in describing what
8505 counted as an "exit" node, and what operations exactly "StrictNodes
8506 0" would permit. This created confusion when people saw nodes built
8507 through unexpected circuits, and made it hard to tell real bugs from
8508 surprises. Now the intended behavior is:
8509 . "Exit", in the context of ExitNodes and ExcludeExitNodes, means
8510 a node that delivers user traffic outside the Tor network.
8511 . "Entry", in the context of EntryNodes, means a node used as the
8512 first hop of a multihop circuit. It doesn't include direct
8513 connections to directory servers.
8514 . "ExcludeNodes" applies to all nodes.
8515 . "StrictNodes" changes the behavior of ExcludeNodes only. When
8516 StrictNodes is set, Tor should avoid all nodes listed in
8517 ExcludeNodes, even when it will make user requests fail. When
8518 StrictNodes is *not* set, then Tor should follow ExcludeNodes
8519 whenever it can, except when it must use an excluded node to
8520 perform self-tests, connect to a hidden service, provide a
8521 hidden service, fulfill a .exit request, upload directory
8522 information, or fetch directory information.
8523 Collectively, the changes to implement the behavior fix bug 1090.
8524 - ExcludeNodes now takes precedence over EntryNodes and ExitNodes: if
8525 a node is listed in both, it's treated as excluded.
8526 - ExcludeNodes now applies to directory nodes -- as a preference if
8527 StrictNodes is 0, or an absolute requirement if StrictNodes is 1.
8528 Don't exclude all the directory authorities and set StrictNodes to 1
8529 unless you really want your Tor to break.
8530 - ExcludeNodes and ExcludeExitNodes now override exit enclaving.
8531 - ExcludeExitNodes now overrides .exit requests.
8532 - We don't use bridges listed in ExcludeNodes.
8533 - When StrictNodes is 1:
8534 . We now apply ExcludeNodes to hidden service introduction points
8535 and to rendezvous points selected by hidden service users. This
8536 can make your hidden service less reliable: use it with caution!
8537 . If we have used ExcludeNodes on ourself, do not try relay
8538 reachability self-tests.
8539 . If we have excluded all the directory authorities, we will not
8540 even try to upload our descriptor if we're a relay.
8541 . Do not honor .exit requests to an excluded node.
8542 - Remove a misfeature that caused us to ignore the Fast/Stable flags
8543 when ExitNodes is set. Bugfix on 0.2.2.7-alpha.
8544 - When the set of permitted nodes changes, we now remove any mappings
8545 introduced via TrackExitHosts to now-excluded nodes. Bugfix on
8547 - We never cannibalize a circuit that had excluded nodes on it, even
8548 if StrictNodes is 0. Bugfix on 0.1.0.1-rc.
8549 - Revert a change where we would be laxer about attaching streams to
8550 circuits than when building the circuits. This was meant to prevent
8551 a set of bugs where streams were never attachable, but our improved
8552 code here should make this unnecessary. Bugfix on 0.2.2.7-alpha.
8553 - Keep track of how many times we launch a new circuit to handle a
8554 given stream. Too many launches could indicate an inconsistency
8555 between our "launch a circuit to handle this stream" logic and our
8556 "attach this stream to one of the available circuits" logic.
8557 - Improve log messages related to excluded nodes.
8560 - Fix a spurious warning when moving from a short month to a long
8561 month on relays with month-based BandwidthAccounting. Bugfix on
8562 0.2.2.17-alpha; fixes bug 3020.
8563 - When a client finds that an origin circuit has run out of 16-bit
8564 stream IDs, we now mark it as unusable for new streams. Previously,
8565 we would try to close the entire circuit. Bugfix on 0.0.6.
8566 - Add a forgotten cast that caused a compile warning on OS X 10.6.
8567 Bugfix on 0.2.2.24-alpha.
8568 - Be more careful about reporting the correct error from a failed
8569 connect() system call. Under some circumstances, it was possible to
8570 look at an incorrect value for errno when sending the end reason.
8571 Bugfix on 0.1.0.1-rc.
8572 - Correctly handle an "impossible" overflow cases in connection byte
8573 counting, where we write or read more than 4GB on an edge connection
8574 in a single second. Bugfix on 0.1.2.8-beta.
8575 - Correct the warning displayed when a rendezvous descriptor exceeds
8576 the maximum size. Fixes bug 2750; bugfix on 0.2.1.5-alpha. Found by
8578 - Clients and hidden services now use HSDir-flagged relays for hidden
8579 service descriptor downloads and uploads even if the relays have no
8580 DirPort set and the client has disabled TunnelDirConns. This will
8581 eventually allow us to give the HSDir flag to relays with no
8582 DirPort. Fixes bug 2722; bugfix on 0.2.1.6-alpha.
8583 - Downgrade "no current certificates known for authority" message from
8584 Notice to Info. Fixes bug 2899; bugfix on 0.2.0.10-alpha.
8585 - Make the SIGNAL DUMP control-port command work on FreeBSD. Fixes bug
8586 2917. Bugfix on 0.1.1.1-alpha.
8587 - Only limit the lengths of single HS descriptors, even when multiple
8588 HS descriptors are published to an HSDir relay in a single POST
8589 operation. Fixes bug 2948; bugfix on 0.2.1.5-alpha. Found by hsdir.
8590 - Write the current time into the LastWritten line in our state file,
8591 rather than the time from the previous write attempt. Also, stop
8592 trying to use a time of -1 in our log statements. Fixes bug 3039;
8593 bugfix on 0.2.2.14-alpha.
8594 - Be more consistent in our treatment of file system paths. "~" should
8595 get expanded to the user's home directory in the Log config option.
8596 Fixes bug 2971; bugfix on 0.2.0.1-alpha, which introduced the
8597 feature for the -f and --DataDirectory options.
8600 - Make sure every relay writes a state file at least every 12 hours.
8601 Previously, a relay could go for weeks without writing its state
8602 file, and on a crash could lose its bandwidth history, capacity
8603 estimates, client country statistics, and so on. Addresses bug 3012.
8604 - Send END_STREAM_REASON_NOROUTE in response to EHOSTUNREACH errors.
8605 Clients before 0.2.1.27 didn't handle NOROUTE correctly, but such
8606 clients are already deprecated because of security bugs.
8607 - Don't allow v0 hidden service authorities to act as clients.
8608 Required by fix for bug 3000.
8609 - Ignore SIGNAL NEWNYM commands on relay-only Tor instances. Required
8610 by fix for bug 3000.
8611 - Ensure that no empty [dirreq-](read|write)-history lines are added
8612 to an extrainfo document. Implements ticket 2497.
8614 o Code simplification and refactoring:
8615 - Remove workaround code to handle directory responses from servers
8616 that had bug 539 (they would send HTTP status 503 responses _and_
8617 send a body too). Since only server versions before
8618 0.2.0.16-alpha/0.1.2.19 were affected, there is no longer reason to
8619 keep the workaround in place.
8620 - Remove the old 'fuzzy time' logic. It was supposed to be used for
8621 handling calculations where we have a known amount of clock skew and
8622 an allowed amount of unknown skew. But we only used it in three
8623 places, and we never adjusted the known/unknown skew values. This is
8624 still something we might want to do someday, but if we do, we'll
8625 want to do it differently.
8626 - Avoid signed/unsigned comparisons by making SIZE_T_CEILING unsigned.
8627 None of the cases where we did this before were wrong, but by making
8628 this change we avoid warnings. Fixes bug 2475; bugfix on 0.2.1.28.
8629 - Use GetTempDir to find the proper temporary directory location on
8630 Windows when generating temporary files for the unit tests. Patch by
8634 Changes in version 0.2.2.24-alpha - 2011-04-08
8635 Tor 0.2.2.24-alpha fixes a variety of bugs, including a big bug that
8636 prevented Tor clients from effectively using "multihomed" bridges,
8637 that is, bridges that listen on multiple ports or IP addresses so users
8638 can continue to use some of their addresses even if others get blocked.
8641 - Fix a bug where bridge users who configure the non-canonical
8642 address of a bridge automatically switch to its canonical
8643 address. If a bridge listens at more than one address, it should be
8644 able to advertise those addresses independently and any non-blocked
8645 addresses should continue to work. Bugfix on Tor 0.2.0.x. Fixes
8647 - If you configured Tor to use bridge A, and then quit and
8648 configured Tor to use bridge B instead, it would happily continue
8649 to use bridge A if it's still reachable. While this behavior is
8650 a feature if your goal is connectivity, in some scenarios it's a
8651 dangerous bug. Bugfix on Tor 0.2.0.1-alpha; fixes bug 2511.
8652 - Directory authorities now use data collected from their own
8653 uptime observations when choosing whether to assign the HSDir flag
8654 to relays, instead of trusting the uptime value the relay reports in
8655 its descriptor. This change helps prevent an attack where a small
8656 set of nodes with frequently-changing identity keys can blackhole
8657 a hidden service. (Only authorities need upgrade; others will be
8658 fine once they do.) Bugfix on 0.2.0.10-alpha; fixes bug 2709.
8661 - When we restart our relay, we might get a successful connection
8662 from the outside before we've started our reachability tests,
8663 triggering a warning: "ORPort found reachable, but I have no
8664 routerinfo yet. Failing to inform controller of success." This
8665 bug was harmless unless Tor is running under a controller
8666 like Vidalia, in which case the controller would never get a
8667 REACHABILITY_SUCCEEDED status event. Bugfix on 0.1.2.6-alpha;
8669 - Make directory authorities more accurate at recording when
8670 relays that have failed several reachability tests became
8671 unreachable, so we can provide more accuracy at assigning Stable,
8672 Guard, HSDir, etc flags. Bugfix on 0.2.0.6-alpha. Resolves bug 2716.
8673 - Fix an issue that prevented static linking of libevent on
8674 some platforms (notably Linux). Fixes bug 2698; bugfix on
8675 versions 0.2.1.23/0.2.2.8-alpha (the versions introducing
8676 the --with-static-libevent configure option).
8677 - We now ask the other side of a stream (the client or the exit)
8678 for more data on that stream when the amount of queued data on
8679 that stream dips low enough. Previously, we wouldn't ask the
8680 other side for more data until either it sent us more data (which
8681 it wasn't supposed to do if it had exhausted its window!) or we
8682 had completely flushed all our queued data. This flow control fix
8683 should improve throughput. Fixes bug 2756; bugfix on the earliest
8684 released versions of Tor (svn commit r152).
8685 - Avoid a double-mark-for-free warning when failing to attach a
8686 transparent proxy connection. (We thought we had fixed this in
8687 0.2.2.23-alpha, but it turns out our fix was checking the wrong
8688 connection.) Fixes bug 2757; bugfix on 0.1.2.1-alpha (the original
8689 bug) and 0.2.2.23-alpha (the incorrect fix).
8690 - When warning about missing zlib development packages during compile,
8691 give the correct package names. Bugfix on 0.2.0.1-alpha.
8694 - Directory authorities now log the source of a rejected POSTed v3
8696 - Make compilation with clang possible when using
8697 --enable-gcc-warnings by removing two warning options that clang
8698 hasn't implemented yet and by fixing a few warnings. Implements
8700 - When expiring circuits, use microsecond timers rather than
8701 one-second timers. This can avoid an unpleasant situation where a
8702 circuit is launched near the end of one second and expired right
8703 near the beginning of the next, and prevent fluctuations in circuit
8705 - Use computed circuit-build timeouts to decide when to launch
8706 parallel introduction circuits for hidden services. (Previously,
8707 we would retry after 15 seconds.)
8708 - Update to the April 1 2011 Maxmind GeoLite Country database.
8711 - Create the /var/run/tor directory on startup on OpenSUSE if it is
8712 not already created. Patch from Andreas Stieger. Fixes bug 2573.
8714 o Documentation changes:
8715 - Modernize the doxygen configuration file slightly. Fixes bug 2707.
8716 - Resolve all doxygen warnings except those for missing documentation.
8718 - Add doxygen documentation for more functions, fields, and types.
8721 Changes in version 0.2.2.23-alpha - 2011-03-08
8722 Tor 0.2.2.23-alpha lets relays record their bandwidth history so when
8723 they restart they don't lose their bandwidth capacity estimate. This
8724 release also fixes a diverse set of user-facing bugs, ranging from
8725 relays overrunning their rate limiting to clients falsely warning about
8726 clock skew to bridge descriptor leaks by our bridge directory authority.
8729 - Stop sending a CLOCK_SKEW controller status event whenever
8730 we fetch directory information from a relay that has a wrong clock.
8731 Instead, only inform the controller when it's a trusted authority
8732 that claims our clock is wrong. Bugfix on 0.1.2.6-alpha; fixes
8733 the rest of bug 1074.
8734 - Fix an assert in parsing router descriptors containing IPv6
8735 addresses. This one took down the directory authorities when
8736 somebody tried some experimental code. Bugfix on 0.2.1.3-alpha.
8737 - Make the bridge directory authority refuse to answer directory
8738 requests for "all" descriptors. It used to include bridge
8739 descriptors in its answer, which was a major information leak.
8740 Found by "piebeer". Bugfix on 0.2.0.3-alpha.
8741 - If relays set RelayBandwidthBurst but not RelayBandwidthRate,
8742 Tor would ignore their RelayBandwidthBurst setting,
8743 potentially using more bandwidth than expected. Bugfix on
8744 0.2.0.1-alpha. Reported by Paul Wouters. Fixes bug 2470.
8745 - Ignore and warn if the user mistakenly sets "PublishServerDescriptor
8746 hidserv" in her torrc. The 'hidserv' argument never controlled
8747 publication of hidden service descriptors. Bugfix on 0.2.0.1-alpha.
8750 - Relays now save observed peak bandwidth throughput rates to their
8751 state file (along with total usage, which was already saved)
8752 so that they can determine their correct estimated bandwidth on
8753 restart. Resolves bug 1863, where Tor relays would reset their
8754 estimated bandwidth to 0 after restarting.
8755 - Directory authorities now take changes in router IP address and
8756 ORPort into account when determining router stability. Previously,
8757 if a router changed its IP or ORPort, the authorities would not
8758 treat it as having any downtime for the purposes of stability
8759 calculation, whereas clients would experience downtime since the
8760 change could take a while to propagate to them. Resolves issue 1035.
8761 - Enable Address Space Layout Randomization (ASLR) and Data Execution
8762 Prevention (DEP) by default on Windows to make it harder for
8763 attackers to exploit vulnerabilities. Patch from John Brooks.
8765 o Minor bugfixes (on 0.2.1.x and earlier):
8766 - Fix a rare crash bug that could occur when a client was configured
8767 with a large number of bridges. Fixes bug 2629; bugfix on
8768 0.2.1.2-alpha. Bugfix by trac user "shitlei".
8769 - Avoid a double mark-for-free warning when failing to attach a
8770 transparent proxy connection. Bugfix on 0.1.2.1-alpha. Fixes
8772 - Correctly detect failure to allocate an OpenSSL BIO. Fixes bug 2378;
8773 found by "cypherpunks". This bug was introduced before the first
8774 Tor release, in svn commit r110.
8775 - Country codes aren't supported in EntryNodes until 0.2.3.x, so
8776 don't mention them in the manpage. Fixes bug 2450; issue
8777 spotted by keb and G-Lo.
8778 - Fix a bug in bandwidth history state parsing that could have been
8779 triggered if a future version of Tor ever changed the timing
8780 granularity at which bandwidth history is measured. Bugfix on
8782 - When a relay decides that its DNS is too broken for it to serve
8783 as an exit server, it advertised itself as a non-exit, but
8784 continued to act as an exit. This could create accidental
8785 partitioning opportunities for users. Instead, if a relay is
8786 going to advertise reject *:* as its exit policy, it should
8787 really act with exit policy "reject *:*". Fixes bug 2366.
8788 Bugfix on Tor 0.1.2.5-alpha. Bugfix by user "postman" on trac.
8789 - In the special case where you configure a public exit relay as your
8790 bridge, Tor would be willing to use that exit relay as the last
8791 hop in your circuit as well. Now we fail that circuit instead.
8792 Bugfix on 0.2.0.12-alpha. Fixes bug 2403. Reported by "piebeer".
8793 - Fix a bug with our locking implementation on Windows that couldn't
8794 correctly detect when a file was already locked. Fixes bug 2504,
8795 bugfix on 0.2.1.6-alpha.
8796 - Fix IPv6-related connect() failures on some platforms (BSD, OS X).
8797 Bugfix on 0.2.0.3-alpha; fixes first part of bug 2660. Patch by
8799 - Set target port in get_interface_address6() correctly. Bugfix
8800 on 0.1.1.4-alpha and 0.2.0.3-alpha; fixes second part of bug 2660.
8801 - Directory authorities are now more robust to hops back in time
8802 when calculating router stability. Previously, if a run of uptime
8803 or downtime appeared to be negative, the calculation could give
8804 incorrect results. Bugfix on 0.2.0.6-alpha; noticed when fixing
8806 - Fix an assert that got triggered when using the TestingTorNetwork
8807 configuration option and then issuing a GETINFO config-text control
8808 command. Fixes bug 2250; bugfix on 0.2.1.2-alpha.
8810 o Minor bugfixes (on 0.2.2.x):
8811 - Clients should not weight BadExit nodes as Exits in their node
8812 selection. Similarly, directory authorities should not count BadExit
8813 bandwidth as Exit bandwidth when computing bandwidth-weights.
8814 Bugfix on 0.2.2.10-alpha; fixes bug 2203.
8815 - Correctly clear our dir_read/dir_write history when there is an
8816 error parsing any bw history value from the state file. Bugfix on
8818 - Resolve a bug in verifying signatures of directory objects
8819 with digests longer than SHA1. Bugfix on 0.2.2.20-alpha.
8820 Fixes bug 2409. Found by "piebeer".
8821 - Bridge authorities no longer crash on SIGHUP when they try to
8822 publish their relay descriptor to themselves. Fixes bug 2572. Bugfix
8826 - Log less aggressively about circuit timeout changes, and improve
8827 some other circuit timeout messages. Resolves bug 2004.
8828 - Log a little more clearly about the times at which we're no longer
8829 accepting new connections. Resolves bug 2181.
8830 - Reject attempts at the client side to open connections to private
8831 IP addresses (like 127.0.0.1, 10.0.0.1, and so on) with
8832 a randomly chosen exit node. Attempts to do so are always
8833 ill-defined, generally prevented by exit policies, and usually
8834 in error. This will also help to detect loops in transparent
8835 proxy configurations. You can disable this feature by setting
8836 "ClientRejectInternalAddresses 0" in your torrc.
8837 - Always treat failure to allocate an RSA key as an unrecoverable
8839 - Update to the March 1 2011 Maxmind GeoLite Country database.
8841 o Minor features (log subsystem):
8842 - Add documentation for configuring logging at different severities in
8843 different log domains. We've had this feature since 0.2.1.1-alpha,
8844 but for some reason it never made it into the manpage. Fixes
8846 - Make it simpler to specify "All log domains except for A and B".
8847 Previously you needed to say "[*,~A,~B]". Now you can just say
8849 - Add a "LogMessageDomains 1" option to include the domains of log
8850 messages along with the messages. Without this, there's no way
8851 to use log domains without reading the source or doing a lot
8854 o Packaging changes:
8855 - Stop shipping the Tor specs files and development proposal documents
8856 in the tarball. They are now in a separate git repository at
8857 git://git.torproject.org/torspec.git
8860 Changes in version 0.2.1.30 - 2011-02-23
8861 Tor 0.2.1.30 fixes a variety of less critical bugs. The main other
8862 change is a slight tweak to Tor's TLS handshake that makes relays
8863 and bridges that run this new version reachable from Iran again.
8864 We don't expect this tweak will win the arms race long-term, but it
8865 buys us time until we roll out a better solution.
8868 - Stop sending a CLOCK_SKEW controller status event whenever
8869 we fetch directory information from a relay that has a wrong clock.
8870 Instead, only inform the controller when it's a trusted authority
8871 that claims our clock is wrong. Bugfix on 0.1.2.6-alpha; fixes
8872 the rest of bug 1074.
8873 - Fix a bounds-checking error that could allow an attacker to
8874 remotely crash a directory authority. Bugfix on 0.2.1.5-alpha.
8876 - If relays set RelayBandwidthBurst but not RelayBandwidthRate,
8877 Tor would ignore their RelayBandwidthBurst setting,
8878 potentially using more bandwidth than expected. Bugfix on
8879 0.2.0.1-alpha. Reported by Paul Wouters. Fixes bug 2470.
8880 - Ignore and warn if the user mistakenly sets "PublishServerDescriptor
8881 hidserv" in her torrc. The 'hidserv' argument never controlled
8882 publication of hidden service descriptors. Bugfix on 0.2.0.1-alpha.
8885 - Adjust our TLS Diffie-Hellman parameters to match those used by
8887 - Update to the February 1 2011 Maxmind GeoLite Country database.
8890 - Check for and reject overly long directory certificates and
8891 directory tokens before they have a chance to hit any assertions.
8892 Bugfix on 0.2.1.28. Found by "doorss".
8893 - Bring the logic that gathers routerinfos and assesses the
8894 acceptability of circuits into line. This prevents a Tor OP from
8895 getting locked in a cycle of choosing its local OR as an exit for a
8896 path (due to a .exit request) and then rejecting the circuit because
8897 its OR is not listed yet. It also prevents Tor clients from using an
8898 OR running in the same instance as an exit (due to a .exit request)
8899 if the OR does not meet the same requirements expected of an OR
8900 running elsewhere. Fixes bug 1859; bugfix on 0.1.0.1-rc.
8902 o Packaging changes:
8903 - Stop shipping the Tor specs files and development proposal documents
8904 in the tarball. They are now in a separate git repository at
8905 git://git.torproject.org/torspec.git
8906 - Do not include Git version tags as though they are SVN tags when
8907 generating a tarball from inside a repository that has switched
8908 between branches. Bugfix on 0.2.1.15-rc; fixes bug 2402.
8911 Changes in version 0.2.2.22-alpha - 2011-01-25
8912 Tor 0.2.2.22-alpha fixes a few more less-critical security issues. The
8913 main other change is a slight tweak to Tor's TLS handshake that makes
8914 relays and bridges that run this new version reachable from Iran again.
8915 We don't expect this tweak will win the arms race long-term, but it
8916 will buy us a bit more time until we roll out a better solution.
8919 - Fix a bounds-checking error that could allow an attacker to
8920 remotely crash a directory authority. Bugfix on 0.2.1.5-alpha.
8922 - Don't assert when changing from bridge to relay or vice versa
8923 via the controller. The assert happened because we didn't properly
8924 initialize our keys in this case. Bugfix on 0.2.2.18-alpha; fixes
8925 bug 2433. Reported by bastik.
8928 - Adjust our TLS Diffie-Hellman parameters to match those used by
8930 - Provide a log message stating which geoip file we're parsing
8931 instead of just stating that we're parsing the geoip file.
8932 Implements ticket 2432.
8935 - Check for and reject overly long directory certificates and
8936 directory tokens before they have a chance to hit any assertions.
8937 Bugfix on 0.2.1.28 / 0.2.2.20-alpha. Found by "doorss".
8940 Changes in version 0.2.2.21-alpha - 2011-01-15
8941 Tor 0.2.2.21-alpha includes all the patches from Tor 0.2.1.29, which
8942 continues our recent code security audit work. The main fix resolves
8943 a remote heap overflow vulnerability that can allow remote code
8944 execution (CVE-2011-0427). Other fixes address a variety of assert
8945 and crash bugs, most of which we think are hard to exploit remotely.
8947 o Major bugfixes (security), also included in 0.2.1.29:
8948 - Fix a heap overflow bug where an adversary could cause heap
8949 corruption. This bug probably allows remote code execution
8950 attacks. Reported by "debuger". Fixes CVE-2011-0427. Bugfix on
8952 - Prevent a denial-of-service attack by disallowing any
8953 zlib-compressed data whose compression factor is implausibly
8954 high. Fixes part of bug 2324; reported by "doorss".
8955 - Zero out a few more keys in memory before freeing them. Fixes
8956 bug 2384 and part of bug 2385. These key instances found by
8957 "cypherpunks", based on Andrew Case's report about being able
8958 to find sensitive data in Tor's memory space if you have enough
8959 permissions. Bugfix on 0.0.2pre9.
8961 o Major bugfixes (crashes), also included in 0.2.1.29:
8962 - Prevent calls to Libevent from inside Libevent log handlers.
8963 This had potential to cause a nasty set of crashes, especially
8964 if running Libevent with debug logging enabled, and running
8965 Tor with a controller watching for low-severity log messages.
8966 Bugfix on 0.1.0.2-rc. Fixes bug 2190.
8967 - Add a check for SIZE_T_MAX to tor_realloc() to try to avoid
8968 underflow errors there too. Fixes the other part of bug 2324.
8969 - Fix a bug where we would assert if we ever had a
8970 cached-descriptors.new file (or another file read directly into
8971 memory) of exactly SIZE_T_CEILING bytes. Fixes bug 2326; bugfix
8972 on 0.2.1.25. Found by doorss.
8973 - Fix some potential asserts and parsing issues with grossly
8974 malformed router caches. Fixes bug 2352; bugfix on Tor 0.2.1.27.
8977 o Minor bugfixes (other), also included in 0.2.1.29:
8978 - Fix a bug with handling misformed replies to reverse DNS lookup
8979 requests in DNSPort. Bugfix on Tor 0.2.0.1-alpha. Related to a
8980 bug reported by doorss.
8981 - Fix compilation on mingw when a pthreads compatibility library
8982 has been installed. (We don't want to use it, so we shouldn't
8983 be including pthread.h.) Fixes bug 2313; bugfix on 0.1.0.1-rc.
8984 - Fix a bug where we would declare that we had run out of virtual
8985 addresses when the address space was only half-exhausted. Bugfix
8987 - Correctly handle the case where AutomapHostsOnResolve is set but
8988 no virtual addresses are available. Fixes bug 2328; bugfix on
8989 0.1.2.1-alpha. Bug found by doorss.
8990 - Correctly handle wrapping around when we run out of virtual
8991 address space. Found by cypherpunks; bugfix on 0.2.0.5-alpha.
8993 o Minor features, also included in 0.2.1.29:
8994 - Update to the January 1 2011 Maxmind GeoLite Country database.
8995 - Introduce output size checks on all of our decryption functions.
8997 o Build changes, also included in 0.2.1.29:
8998 - Tor does not build packages correctly with Automake 1.6 and earlier;
8999 added a check to Makefile.am to make sure that we're building with
9000 Automake 1.7 or later.
9001 - The 0.2.1.28 tarball was missing src/common/OpenBSD_malloc_Linux.c
9002 because we built it with a too-old version of automake. Thus that
9003 release broke ./configure --enable-openbsd-malloc, which is popular
9004 among really fast exit relays on Linux.
9006 o Major bugfixes, new in 0.2.2.21-alpha:
9007 - Prevent crash/heap corruption when the cbtnummodes consensus
9008 parameter is set to 0 or large values. Fixes bug 2317; bugfix
9011 o Major features, new in 0.2.2.21-alpha:
9012 - Introduce minimum/maximum values that clients will believe
9013 from the consensus. Now we'll have a better chance to avoid crashes
9014 or worse when a consensus param has a weird value.
9016 o Minor features, new in 0.2.2.21-alpha:
9017 - Make sure to disable DirPort if running as a bridge. DirPorts aren't
9018 used on bridges, and it makes bridge scanning somewhat easier.
9019 - If writing the state file to disk fails, wait up to an hour before
9020 retrying again, rather than trying again each second. Fixes bug
9021 2346; bugfix on Tor 0.1.1.3-alpha.
9022 - Make Libevent log messages get delivered to controllers later,
9023 and not from inside the Libevent log handler. This prevents unsafe
9024 reentrant Libevent calls while still letting the log messages
9026 - Detect platforms that brokenly use a signed size_t, and refuse to
9027 build there. Found and analyzed by doorss and rransom.
9028 - Fix a bunch of compile warnings revealed by mingw with gcc 4.5.
9031 o Minor bugfixes, new in 0.2.2.21-alpha:
9032 - Handle SOCKS messages longer than 128 bytes long correctly, rather
9033 than waiting forever for them to finish. Fixes bug 2330; bugfix
9034 on 0.2.0.16-alpha. Found by doorss.
9035 - Add assertions to check for overflow in arguments to
9036 base32_encode() and base32_decode(); fix a signed-unsigned
9037 comparison there too. These bugs are not actually reachable in Tor,
9038 but it's good to prevent future errors too. Found by doorss.
9039 - Correctly detect failures to create DNS requests when using Libevent
9040 versions before v2. (Before Libevent 2, we used our own evdns
9041 implementation. Its return values for Libevent's evdns_resolve_*()
9042 functions are not consistent with those from Libevent.) Fixes bug
9043 2363; bugfix on 0.2.2.6-alpha. Found by "lodger".
9045 o Documentation, new in 0.2.2.21-alpha:
9046 - Document the default socks host and port (127.0.0.1:9050) for
9050 Changes in version 0.2.1.29 - 2011-01-15
9051 Tor 0.2.1.29 continues our recent code security audit work. The main
9052 fix resolves a remote heap overflow vulnerability that can allow remote
9053 code execution. Other fixes address a variety of assert and crash bugs,
9054 most of which we think are hard to exploit remotely.
9056 o Major bugfixes (security):
9057 - Fix a heap overflow bug where an adversary could cause heap
9058 corruption. This bug probably allows remote code execution
9059 attacks. Reported by "debuger". Fixes CVE-2011-0427. Bugfix on
9061 - Prevent a denial-of-service attack by disallowing any
9062 zlib-compressed data whose compression factor is implausibly
9063 high. Fixes part of bug 2324; reported by "doorss".
9064 - Zero out a few more keys in memory before freeing them. Fixes
9065 bug 2384 and part of bug 2385. These key instances found by
9066 "cypherpunks", based on Andrew Case's report about being able
9067 to find sensitive data in Tor's memory space if you have enough
9068 permissions. Bugfix on 0.0.2pre9.
9070 o Major bugfixes (crashes):
9071 - Prevent calls to Libevent from inside Libevent log handlers.
9072 This had potential to cause a nasty set of crashes, especially
9073 if running Libevent with debug logging enabled, and running
9074 Tor with a controller watching for low-severity log messages.
9075 Bugfix on 0.1.0.2-rc. Fixes bug 2190.
9076 - Add a check for SIZE_T_MAX to tor_realloc() to try to avoid
9077 underflow errors there too. Fixes the other part of bug 2324.
9078 - Fix a bug where we would assert if we ever had a
9079 cached-descriptors.new file (or another file read directly into
9080 memory) of exactly SIZE_T_CEILING bytes. Fixes bug 2326; bugfix
9081 on 0.2.1.25. Found by doorss.
9082 - Fix some potential asserts and parsing issues with grossly
9083 malformed router caches. Fixes bug 2352; bugfix on Tor 0.2.1.27.
9086 o Minor bugfixes (other):
9087 - Fix a bug with handling misformed replies to reverse DNS lookup
9088 requests in DNSPort. Bugfix on Tor 0.2.0.1-alpha. Related to a
9089 bug reported by doorss.
9090 - Fix compilation on mingw when a pthreads compatibility library
9091 has been installed. (We don't want to use it, so we shouldn't
9092 be including pthread.h.) Fixes bug 2313; bugfix on 0.1.0.1-rc.
9093 - Fix a bug where we would declare that we had run out of virtual
9094 addresses when the address space was only half-exhausted. Bugfix
9096 - Correctly handle the case where AutomapHostsOnResolve is set but
9097 no virtual addresses are available. Fixes bug 2328; bugfix on
9098 0.1.2.1-alpha. Bug found by doorss.
9099 - Correctly handle wrapping around to when we run out of virtual
9100 address space. Found by cypherpunks, bugfix on 0.2.0.5-alpha.
9101 - The 0.2.1.28 tarball was missing src/common/OpenBSD_malloc_Linux.c
9102 because we built it with a too-old version of automake. Thus that
9103 release broke ./configure --enable-openbsd-malloc, which is popular
9104 among really fast exit relays on Linux.
9107 - Update to the January 1 2011 Maxmind GeoLite Country database.
9108 - Introduce output size checks on all of our decryption functions.
9111 - Tor does not build packages correctly with Automake 1.6 and earlier;
9112 added a check to Makefile.am to make sure that we're building with
9113 Automake 1.7 or later.
9116 Changes in version 0.2.2.20-alpha - 2010-12-17
9117 Tor 0.2.2.20-alpha does some code cleanup to reduce the risk of remotely
9118 exploitable bugs. We also fix a variety of other significant bugs,
9119 change the IP address for one of our directory authorities, and update
9120 the minimum version that Tor relays must run to join the network.
9123 - Fix a remotely exploitable bug that could be used to crash instances
9124 of Tor remotely by overflowing on the heap. Remote-code execution
9125 hasn't been confirmed, but can't be ruled out. Everyone should
9126 upgrade. Bugfix on the 0.1.1 series and later.
9127 - Fix a bug that could break accounting on 64-bit systems with large
9128 time_t values, making them hibernate for impossibly long intervals.
9129 Fixes bug 2146. Bugfix on 0.0.9pre6; fix by boboper.
9130 - Fix a logic error in directory_fetches_from_authorities() that
9131 would cause all _non_-exits refusing single-hop-like circuits
9132 to fetch from authorities, when we wanted to have _exits_ fetch
9133 from authorities. Fixes more of 2097. Bugfix on 0.2.2.16-alpha;
9135 - Fix a stream fairness bug that would cause newer streams on a given
9136 circuit to get preference when reading bytes from the origin or
9137 destination. Fixes bug 2210. Fix by Mashael AlSabah. This bug was
9138 introduced before the first Tor release, in svn revision r152.
9140 o Directory authority changes:
9141 - Change IP address and ports for gabelmoo (v3 directory authority).
9144 - Avoid crashes when AccountingMax is set on clients. Fixes bug 2235.
9145 Bugfix on 0.2.2.18-alpha. Diagnosed by boboper.
9146 - Fix an off-by-one error in calculating some controller command
9147 argument lengths. Fortunately, this mistake is harmless since
9148 the controller code does redundant NUL termination too. Found by
9149 boboper. Bugfix on 0.1.1.1-alpha.
9150 - Do not dereference NULL if a bridge fails to build its
9151 extra-info descriptor. Found by an anonymous commenter on
9152 Trac. Bugfix on 0.2.2.19-alpha.
9155 - Update to the December 1 2010 Maxmind GeoLite Country database.
9156 - Directory authorities now reject relays running any versions of
9157 Tor between 0.2.1.3-alpha and 0.2.1.18 inclusive; they have
9158 known bugs that keep RELAY_EARLY cells from working on rendezvous
9159 circuits. Followup to fix for bug 2081.
9160 - Directory authorities now reject relays running any version of Tor
9161 older than 0.2.0.26-rc. That version is the earliest that fetches
9162 current directory information correctly. Fixes bug 2156.
9163 - Report only the top 10 ports in exit-port stats in order not to
9164 exceed the maximum extra-info descriptor length of 50 KB. Implements
9168 Changes in version 0.2.1.28 - 2010-12-17
9169 Tor 0.2.1.28 does some code cleanup to reduce the risk of remotely
9170 exploitable bugs. We also took this opportunity to change the IP address
9171 for one of our directory authorities, and to update the geoip database
9175 - Fix a remotely exploitable bug that could be used to crash instances
9176 of Tor remotely by overflowing on the heap. Remote-code execution
9177 hasn't been confirmed, but can't be ruled out. Everyone should
9178 upgrade. Bugfix on the 0.1.1 series and later.
9180 o Directory authority changes:
9181 - Change IP address and ports for gabelmoo (v3 directory authority).
9184 - Update to the December 1 2010 Maxmind GeoLite Country database.
9187 Changes in version 0.2.1.27 - 2010-11-23
9188 Yet another OpenSSL security patch broke its compatibility with Tor:
9189 Tor 0.2.1.27 makes relays work with openssl 0.9.8p and 1.0.0.b. We
9190 also took this opportunity to fix several crash bugs, integrate a new
9191 directory authority, and update the bundled GeoIP database.
9194 - Resolve an incompatibility with OpenSSL 0.9.8p and OpenSSL 1.0.0b:
9195 No longer set the tlsext_host_name extension on server SSL objects;
9196 but continue to set it on client SSL objects. Our goal in setting
9197 it was to imitate a browser, not a vhosting server. Fixes bug 2204;
9198 bugfix on 0.2.1.1-alpha.
9199 - Do not log messages to the controller while shrinking buffer
9200 freelists. Doing so would sometimes make the controller connection
9201 try to allocate a buffer chunk, which would mess up the internals
9202 of the freelist and cause an assertion failure. Fixes bug 1125;
9203 fixed by Robert Ransom. Bugfix on 0.2.0.16-alpha.
9204 - Learn our external IP address when we're a relay or bridge, even if
9205 we set PublishServerDescriptor to 0. Bugfix on 0.2.0.3-alpha,
9206 where we introduced bridge relays that don't need to publish to
9207 be useful. Fixes bug 2050.
9208 - Do even more to reject (and not just ignore) annotations on
9209 router descriptors received anywhere but from the cache. Previously
9210 we would ignore such annotations at first, but cache them to disk
9211 anyway. Bugfix on 0.2.0.8-alpha. Found by piebeer.
9212 - When you're using bridges and your network goes away and your
9213 bridges get marked as down, recover when you attempt a new socks
9214 connection (if the network is back), rather than waiting up to an
9215 hour to try fetching new descriptors for your bridges. Bugfix on
9216 0.2.0.3-alpha; fixes bug 1981.
9219 - Move to the November 2010 Maxmind GeoLite country db (rather
9220 than the June 2009 ip-to-country GeoIP db) for our statistics that
9221 count how many users relays are seeing from each country. Now we'll
9222 have more accurate data, especially for many African countries.
9224 o New directory authorities:
9225 - Set up maatuska (run by Linus Nordberg) as the eighth v3 directory
9229 - Fix an assertion failure that could occur in directory caches or
9230 bridge users when using a very short voting interval on a testing
9231 network. Diagnosed by Robert Hogan. Fixes bug 1141; bugfix on
9233 - Enforce multiplicity rules when parsing annotations. Bugfix on
9234 0.2.0.8-alpha. Found by piebeer.
9235 - Allow handshaking OR connections to take a full KeepalivePeriod
9236 seconds to handshake. Previously, we would close them after
9237 IDLE_OR_CONN_TIMEOUT (180) seconds, the same timeout as if they
9238 were open. Bugfix on 0.2.1.26; fixes bug 1840. Thanks to mingw-san
9240 - When building with --enable-gcc-warnings on OpenBSD, disable
9241 warnings in system headers. This makes --enable-gcc-warnings
9242 pass on OpenBSD 4.8.
9245 - Exit nodes didn't recognize EHOSTUNREACH as a plausible error code,
9246 and so sent back END_STREAM_REASON_MISC. Clients now recognize a new
9247 stream ending reason for this case: END_STREAM_REASON_NOROUTE.
9248 Servers can start sending this code when enough clients recognize
9249 it. Bugfix on 0.1.0.1-rc; fixes part of bug 1793.
9250 - Build correctly on mingw with more recent versions of OpenSSL 0.9.8.
9251 Patch from mingw-san.
9254 - Remove the old debian/ directory from the main Tor distribution.
9255 The official Tor-for-debian git repository lives at the URL
9256 https://git.torproject.org/debian/tor.git
9257 - Stop shipping the old doc/website/ directory in the tarball. We
9258 changed the website format in late 2010, and what we shipped in
9259 0.2.1.26 really wasn't that useful anyway.
9262 Changes in version 0.2.2.19-alpha - 2010-11-22
9263 Yet another OpenSSL security patch broke its compatibility with Tor:
9264 Tor 0.2.2.19-alpha makes relays work with OpenSSL 0.9.8p and 1.0.0.b.
9267 - Resolve an incompatibility with OpenSSL 0.9.8p and OpenSSL 1.0.0b:
9268 No longer set the tlsext_host_name extension on server SSL objects;
9269 but continue to set it on client SSL objects. Our goal in setting
9270 it was to imitate a browser, not a vhosting server. Fixes bug 2204;
9271 bugfix on 0.2.1.1-alpha.
9274 - Try harder not to exceed the maximum length of 50 KB when writing
9275 statistics to extra-info descriptors. This bug was triggered by very
9276 fast relays reporting exit-port, entry, and dirreq statistics.
9277 Reported by Olaf Selke. Bugfix on 0.2.2.1-alpha. Fixes bug 2183.
9278 - Publish a router descriptor even if generating an extra-info
9279 descriptor fails. Previously we would not publish a router
9280 descriptor without an extra-info descriptor; this can cause fast
9281 exit relays collecting exit-port statistics to drop from the
9282 consensus. Bugfix on 0.1.2.9-rc; fixes bug 2195.
9285 Changes in version 0.2.2.18-alpha - 2010-11-16
9286 Tor 0.2.2.18-alpha fixes several crash bugs that have been nagging
9287 us lately, makes unpublished bridge relays able to detect their IP
9288 address, and fixes a wide variety of other bugs to get us much closer
9289 to a stable release.
9292 - Do even more to reject (and not just ignore) annotations on
9293 router descriptors received anywhere but from the cache. Previously
9294 we would ignore such annotations at first, but cache them to disk
9295 anyway. Bugfix on 0.2.0.8-alpha. Found by piebeer.
9296 - Do not log messages to the controller while shrinking buffer
9297 freelists. Doing so would sometimes make the controller connection
9298 try to allocate a buffer chunk, which would mess up the internals
9299 of the freelist and cause an assertion failure. Fixes bug 1125;
9300 fixed by Robert Ransom. Bugfix on 0.2.0.16-alpha.
9301 - Learn our external IP address when we're a relay or bridge, even if
9302 we set PublishServerDescriptor to 0. Bugfix on 0.2.0.3-alpha,
9303 where we introduced bridge relays that don't need to publish to
9304 be useful. Fixes bug 2050.
9305 - Maintain separate TLS contexts and certificates for incoming and
9306 outgoing connections in bridge relays. Previously we would use the
9307 same TLS contexts and certs for incoming and outgoing connections.
9308 Bugfix on 0.2.0.3-alpha; addresses bug 988.
9309 - Maintain separate identity keys for incoming and outgoing TLS
9310 contexts in bridge relays. Previously we would use the same
9311 identity keys for incoming and outgoing TLS contexts. Bugfix on
9312 0.2.0.3-alpha; addresses the other half of bug 988.
9313 - Avoid an assertion failure when we as an authority receive a
9314 duplicate upload of a router descriptor that we already have,
9315 but which we previously considered an obsolete descriptor.
9316 Fixes another case of bug 1776. Bugfix on 0.2.2.16-alpha.
9317 - Avoid a crash bug triggered by looking at a dangling pointer while
9318 setting the network status consensus. Found by Robert Ransom.
9319 Bugfix on 0.2.2.17-alpha. Fixes bug 2097.
9320 - Fix a logic error where servers that _didn't_ act as exits would
9321 try to keep their server lists more aggressively up to date than
9322 exits, when it was supposed to be the other way around. Bugfix
9325 o Minor bugfixes (on Tor 0.2.1.x and earlier):
9326 - When we're trying to guess whether we know our IP address as
9327 a relay, we would log various ways that we failed to guess
9328 our address, but never log that we ended up guessing it
9329 successfully. Now add a log line to help confused and anxious
9330 relay operators. Bugfix on 0.1.2.1-alpha; fixes bug 1534.
9331 - Bring the logic that gathers routerinfos and assesses the
9332 acceptability of circuits into line. This prevents a Tor OP from
9333 getting locked in a cycle of choosing its local OR as an exit for a
9334 path (due to a .exit request) and then rejecting the circuit because
9335 its OR is not listed yet. It also prevents Tor clients from using an
9336 OR running in the same instance as an exit (due to a .exit request)
9337 if the OR does not meet the same requirements expected of an OR
9338 running elsewhere. Fixes bug 1859; bugfix on 0.1.0.1-rc.
9339 - Correctly describe errors that occur when generating a TLS object.
9340 Previously we would attribute them to a failure while generating a
9341 TLS context. Patch by Robert Ransom. Bugfix on 0.1.0.4-rc; fixes
9343 - Enforce multiplicity rules when parsing annotations. Bugfix on
9344 0.2.0.8-alpha. Found by piebeer.
9345 - Fix warnings that newer versions of autoconf produced during
9346 ./autogen.sh. These warnings appear to be harmless in our case,
9347 but they were extremely verbose. Fixes bug 2020.
9349 o Minor bugfixes (on Tor 0.2.2.x):
9350 - Enable protection of small arrays whenever we build with gcc
9351 hardening features, not only when also building with warnings
9352 enabled. Fixes bug 2031; bugfix on 0.2.2.14-alpha. Reported by keb.
9355 - Make hidden services work better in private Tor networks by not
9356 requiring any uptime to join the hidden service descriptor
9357 DHT. Implements ticket 2088.
9358 - Rate-limit the "your application is giving Tor only an IP address"
9359 warning. Addresses bug 2000; bugfix on 0.0.8pre2.
9360 - When AllowSingleHopExits is set, print a warning to explain to the
9361 relay operator why most clients are avoiding her relay.
9362 - Update to the November 1 2010 Maxmind GeoLite Country database.
9364 o Code simplifications and refactoring:
9365 - When we fixed bug 1038 we had to put in a restriction not to send
9366 RELAY_EARLY cells on rend circuits. This was necessary as long
9367 as relays using Tor 0.2.1.3-alpha through 0.2.1.18-alpha were
9368 active. Now remove this obsolete check. Resolves bug 2081.
9369 - Some options used different conventions for uppercasing of acronyms
9370 when comparing manpage and source. Fix those in favor of the
9371 manpage, as it makes sense to capitalize acronyms.
9372 - Remove the torrc.complete file. It hasn't been kept up to date
9373 and users will have better luck checking out the manpage.
9374 - Remove the obsolete "NoPublish" option; it has been flagged
9375 as obsolete and has produced a warning since 0.1.1.18-rc.
9376 - Remove everything related to building the expert bundle for OS X.
9377 It has confused many users, doesn't work right on OS X 10.6,
9378 and is hard to get rid of once installed. Resolves bug 1274.
9381 Changes in version 0.2.2.17-alpha - 2010-09-30
9382 Tor 0.2.2.17-alpha introduces a feature to make it harder for clients
9383 to use one-hop circuits (which can put the exit relays at higher risk,
9384 plus unbalance the network); fixes a big bug in bandwidth accounting
9385 for relays that want to limit their monthly bandwidth use; fixes a
9386 big pile of bugs in how clients tolerate temporary network failure;
9387 and makes our adaptive circuit build timeout feature (which improves
9388 client performance if your network is fast while not breaking things
9389 if your network is slow) better handle bad networks.
9392 - Exit relays now try harder to block exit attempts from unknown
9393 relays, to make it harder for people to use them as one-hop proxies
9394 a la tortunnel. Controlled by the refuseunknownexits consensus
9395 parameter (currently enabled), or you can override it on your
9396 relay with the RefuseUnknownExits torrc option. Resolves bug 1751.
9398 o Major bugfixes (0.2.1.x and earlier):
9399 - Fix a bug in bandwidth accounting that could make us use twice
9400 the intended bandwidth when our interval start changes due to
9401 daylight saving time. Now we tolerate skew in stored vs computed
9402 interval starts: if the start of the period changes by no more than
9403 50% of the period's duration, we remember bytes that we transferred
9404 in the old period. Fixes bug 1511; bugfix on 0.0.9pre5.
9405 - Always search the Windows system directory for system DLLs, and
9406 nowhere else. Bugfix on 0.1.1.23; fixes bug 1954.
9407 - When you're using bridges and your network goes away and your
9408 bridges get marked as down, recover when you attempt a new socks
9409 connection (if the network is back), rather than waiting up to an
9410 hour to try fetching new descriptors for your bridges. Bugfix on
9411 0.2.0.3-alpha; fixes bug 1981.
9413 o Major bugfixes (on 0.2.2.x):
9414 - Fix compilation on Windows. Bugfix on 0.2.2.16-alpha; related to
9416 - Fix a segfault that could happen when operating a bridge relay with
9417 no GeoIP database set. Fixes bug 1964; bugfix on 0.2.2.15-alpha.
9418 - The consensus bandwidth-weights (used by clients to choose fast
9419 relays) entered an unexpected edge case in September where
9420 Exits were much scarcer than Guards, resulting in bad weight
9421 recommendations. Now we compute them using new constraints that
9422 should succeed in all cases. Also alter directory authorities to
9423 not include the bandwidth-weights line if they fail to produce
9424 valid values. Fixes bug 1952; bugfix on 0.2.2.10-alpha.
9425 - When weighting bridges during path selection, we used to trust
9426 the bandwidths they provided in their descriptor, only capping them
9427 at 10MB/s. This turned out to be problematic for two reasons:
9428 Bridges could claim to handle a lot more traffic then they
9429 actually would, thus making more clients pick them and have a
9430 pretty effective DoS attack. The other issue is that new bridges
9431 that might not have a good estimate for their bw capacity yet
9432 would not get used at all unless no other bridges are available
9433 to a client. Fixes bug 1912; bugfix on 0.2.2.7-alpha.
9435 o Major bugfixes (on the circuit build timeout feature, 0.2.2.x):
9436 - Ignore cannibalized circuits when recording circuit build times.
9437 This should provide for a minor performance improvement for hidden
9438 service users using 0.2.2.14-alpha, and should remove two spurious
9439 notice log messages. Bugfix on 0.2.2.14-alpha; fixes bug 1740.
9440 - Simplify the logic that causes us to decide if the network is
9441 unavailable for purposes of recording circuit build times. If we
9442 receive no cells whatsoever for the entire duration of a circuit's
9443 full measured lifetime, the network is probably down. Also ignore
9444 one-hop directory fetching circuit timeouts when calculating our
9445 circuit build times. These changes should hopefully reduce the
9446 cases where we see ridiculous circuit build timeouts for people
9447 with spotty wireless connections. Fixes part of bug 1772; bugfix
9449 - Prevent the circuit build timeout from becoming larger than
9450 the maximum build time we have ever seen. Also, prevent the time
9451 period for measurement circuits from becoming larger than twice that
9452 value. Fixes the other part of bug 1772; bugfix on 0.2.2.2-alpha.
9455 - When we run out of directory information such that we can't build
9456 circuits, but then get enough that we can build circuits, log when
9457 we actually construct a circuit, so the user has a better chance of
9458 knowing what's going on. Fixes bug 1362.
9459 - Be more generous with how much bandwidth we'd use up (with
9460 accounting enabled) before entering "soft hibernation". Previously,
9461 we'd refuse new connections and circuits once we'd used up 95% of
9462 our allotment. Now, we use up 95% of our allotment, AND make sure
9463 that we have no more than 500MB (or 3 hours of expected traffic,
9464 whichever is lower) remaining before we enter soft hibernation.
9465 - If we've configured EntryNodes and our network goes away and/or all
9466 our entrynodes get marked down, optimistically retry them all when
9467 a new socks application request appears. Fixes bug 1882.
9468 - Add some more defensive programming for architectures that can't
9469 handle unaligned integer accesses. We don't know of any actual bugs
9470 right now, but that's the best time to fix them. Fixes bug 1943.
9471 - Support line continuations in the torrc config file. If a line
9472 ends with a single backslash character, the newline is ignored, and
9473 the configuration value is treated as continuing on the next line.
9476 o Minor bugfixes (on 0.2.1.x and earlier):
9477 - For bandwidth accounting, calculate our expected bandwidth rate
9478 based on the time during which we were active and not in
9479 soft-hibernation during the last interval. Previously, we were
9480 also considering the time spent in soft-hibernation. If this
9481 was a long time, we would wind up underestimating our bandwidth
9482 by a lot, and skewing our wakeup time towards the start of the
9483 accounting interval. Fixes bug 1789. Bugfix on 0.0.9pre5.
9485 o Minor bugfixes (on 0.2.2.x):
9486 - Resume generating CIRC FAILED REASON=TIMEOUT control port messages,
9487 which were disabled by the circuit build timeout changes in
9488 0.2.2.14-alpha. Bugfix on 0.2.2.14-alpha; fixes bug 1739.
9489 - Make sure we don't warn about missing bandwidth weights when
9490 choosing bridges or other relays not in the consensus. Bugfix on
9491 0.2.2.10-alpha; fixes bug 1805.
9492 - In our logs, do not double-report signatures from unrecognized
9493 authorities both as "from unknown authority" and "not
9494 present". Fixes bug 1956, bugfix on 0.2.2.16-alpha.
9497 Changes in version 0.2.2.16-alpha - 2010-09-17
9498 Tor 0.2.2.16-alpha fixes a variety of old stream fairness bugs (most
9499 evident at exit relays), and also continues to resolve all the little
9500 bugs that have been filling up trac lately.
9502 o Major bugfixes (stream-level fairness):
9503 - When receiving a circuit-level SENDME for a blocked circuit, try
9504 to package cells fairly from all the streams that had previously
9505 been blocked on that circuit. Previously, we had started with the
9506 oldest stream, and allowed each stream to potentially exhaust
9507 the circuit's package window. This gave older streams on any
9508 given circuit priority over newer ones. Fixes bug 1937. Detected
9509 originally by Camilo Viecco. This bug was introduced before the
9510 first Tor release, in svn commit r152: it is the new winner of
9511 the longest-lived bug prize.
9512 - When the exit relay got a circuit-level sendme cell, it started
9513 reading on the exit streams, even if had 500 cells queued in the
9514 circuit queue already, so the circuit queue just grew and grew in
9515 some cases. We fix this by not re-enabling reading on receipt of a
9516 sendme cell when the cell queue is blocked. Fixes bug 1653. Bugfix
9517 on 0.2.0.1-alpha. Detected by Mashael AlSabah. Original patch by
9519 - Newly created streams were allowed to read cells onto circuits,
9520 even if the circuit's cell queue was blocked and waiting to drain.
9521 This created potential unfairness, as older streams would be
9522 blocked, but newer streams would gladly fill the queue completely.
9523 We add code to detect this situation and prevent any stream from
9524 getting more than one free cell. Bugfix on 0.2.0.1-alpha. Partially
9528 - Update to the September 1 2010 Maxmind GeoLite Country database.
9529 - Warn when CookieAuthFileGroupReadable is set but CookieAuthFile is
9530 not. This would lead to a cookie that is still not group readable.
9531 Closes bug 1843. Suggested by katmagic.
9532 - When logging a rate-limited warning, we now mention how many messages
9533 got suppressed since the last warning.
9534 - Add new "perconnbwrate" and "perconnbwburst" consensus params to
9535 do individual connection-level rate limiting of clients. The torrc
9536 config options with the same names trump the consensus params, if
9537 both are present. Replaces the old "bwconnrate" and "bwconnburst"
9538 consensus params which were broken from 0.2.2.7-alpha through
9539 0.2.2.14-alpha. Closes bug 1947.
9540 - When a router changes IP address or port, authorities now launch
9541 a new reachability test for it. Implements ticket 1899.
9542 - Make the formerly ugly "2 unknown, 7 missing key, 0 good, 0 bad,
9543 2 no signature, 4 required" messages about consensus signatures
9544 easier to read, and make sure they get logged at the same severity
9545 as the messages explaining which keys are which. Fixes bug 1290.
9546 - Don't warn when we have a consensus that we can't verify because
9547 of missing certificates, unless those certificates are ones
9548 that we have been trying and failing to download. Fixes bug 1145.
9549 - If you configure your bridge with a known identity fingerprint,
9550 and the bridge authority is unreachable (as it is in at least
9551 one country now), fall back to directly requesting the descriptor
9552 from the bridge. Finishes the feature started in 0.2.0.10-alpha;
9554 - When building with --enable-gcc-warnings on OpenBSD, disable
9555 warnings in system headers. This makes --enable-gcc-warnings
9556 pass on OpenBSD 4.8.
9558 o Minor bugfixes (on 0.2.1.x and earlier):
9559 - Authorities will now attempt to download consensuses if their
9560 own efforts to make a live consensus have failed. This change
9561 means authorities that restart will fetch a valid consensus, and
9562 it means authorities that didn't agree with the current consensus
9563 will still fetch and serve it if it has enough signatures. Bugfix
9564 on 0.2.0.9-alpha; fixes bug 1300.
9565 - Ensure DNS requests launched by "RESOLVE" commands from the
9566 controller respect the __LeaveStreamsUnattached setconf options. The
9567 same goes for requests launched via DNSPort or transparent
9568 proxying. Bugfix on 0.2.0.1-alpha; fixes bug 1525.
9569 - Allow handshaking OR connections to take a full KeepalivePeriod
9570 seconds to handshake. Previously, we would close them after
9571 IDLE_OR_CONN_TIMEOUT (180) seconds, the same timeout as if they
9572 were open. Bugfix on 0.2.1.26; fixes bug 1840. Thanks to mingw-san
9574 - Rate-limit "Failed to hand off onionskin" warnings.
9575 - Never relay a cell for a circuit we have already destroyed.
9576 Between marking a circuit as closeable and finally closing it,
9577 it may have been possible for a few queued cells to get relayed,
9578 even though they would have been immediately dropped by the next
9579 OR in the circuit. Fixes bug 1184; bugfix on 0.2.0.1-alpha.
9580 - Never queue a cell for a circuit that's already been marked
9582 - Never vote for a server as "Running" if we have a descriptor for
9583 it claiming to be hibernating, and that descriptor was published
9584 more recently than our last contact with the server. Bugfix on
9585 0.2.0.3-alpha; fixes bug 911.
9586 - Squash a compile warning on OpenBSD. Reported by Tas; fixes
9589 o Minor bugfixes (on 0.2.2.x):
9590 - Fix a regression introduced in 0.2.2.7-alpha that marked relays
9591 down if a directory fetch fails and you've configured either
9592 bridges or EntryNodes. The intent was to mark the relay as down
9593 _unless_ you're using bridges or EntryNodes, since if you are
9594 then you could quickly run out of entry points.
9595 - Fix the Windows directory-listing code. A bug introduced in
9596 0.2.2.14-alpha could make Windows directory servers forget to load
9597 some of their cached v2 networkstatus files.
9598 - Really allow clients to use relays as bridges. Fixes bug 1776;
9599 bugfix on 0.2.2.15-alpha.
9600 - Demote a warn to info that happens when the CellStatistics option
9601 was just enabled. Bugfix on 0.2.2.15-alpha; fixes bug 1921.
9602 Reported by Moritz Bartl.
9603 - On Windows, build correctly either with or without Unicode support.
9604 This is necessary so that Tor can support fringe platforms like
9605 Windows 98 (which has no Unicode), or Windows CE (which has no
9606 non-Unicode). Bugfix on 0.2.2.14-alpha; fixes bug 1797.
9609 - Add a unit test for cross-platform directory-listing code.
9612 Changes in version 0.2.2.15-alpha - 2010-08-18
9613 Tor 0.2.2.15-alpha fixes a big bug in hidden service availability,
9614 fixes a variety of other bugs that were preventing performance
9615 experiments from moving forward, fixes several bothersome memory leaks,
9616 and generally closes a lot of smaller bugs that have been filling up
9620 - Stop assigning the HSDir flag to relays that disable their
9621 DirPort (and thus will refuse to answer directory requests). This
9622 fix should dramatically improve the reachability of hidden services:
9623 hidden services and hidden service clients pick six HSDir relays
9624 to store and retrieve the hidden service descriptor, and currently
9625 about half of the HSDir relays will refuse to work. Bugfix on
9626 0.2.0.10-alpha; fixes part of bug 1693.
9627 - The PerConnBWRate and Burst config options, along with the
9628 bwconnrate and bwconnburst consensus params, initialized each conn's
9629 token bucket values only when the connection is established. Now we
9630 update them if the config options change, and update them every time
9631 we get a new consensus. Otherwise we can encounter an ugly edge
9632 case where we initialize an OR conn to client-level bandwidth,
9633 but then later the relay joins the consensus and we leave it
9634 throttled. Bugfix on 0.2.2.7-alpha; fixes bug 1830.
9635 - Fix a regression that caused Tor to rebind its ports if it receives
9636 SIGHUP while hibernating. Bugfix in 0.1.1.6-alpha; closes bug 919.
9639 - Lower the maximum weighted-fractional-uptime cutoff to 98%. This
9640 should give us approximately 40-50% more Guard-flagged nodes,
9641 improving the anonymity the Tor network can provide and also
9642 decreasing the dropoff in throughput that relays experience when
9643 they first get the Guard flag.
9644 - Allow enabling or disabling the *Statistics config options while
9648 - Update to the August 1 2010 Maxmind GeoLite Country database.
9649 - Have the controller interface give a more useful message than
9650 "Internal Error" in response to failed GETINFO requests.
9651 - Warn when the same option is provided more than once in a torrc
9652 file, on the command line, or in a single SETCONF statement, and
9653 the option is one that only accepts a single line. Closes bug 1384.
9654 - Build correctly on mingw with more recent versions of OpenSSL 0.9.8.
9655 Patch from mingw-san.
9656 - Add support for the country code "{??}" in torrc options like
9657 ExcludeNodes, to indicate all routers of unknown country. Closes
9659 - Relays report the number of bytes spent on answering directory
9660 requests in extra-info descriptors similar to {read,write}-history.
9661 Implements enhancement 1790.
9663 o Minor bugfixes (on 0.2.1.x and earlier):
9664 - Complain if PublishServerDescriptor is given multiple arguments that
9665 include 0 or 1. This configuration will be rejected in the future.
9666 Bugfix on 0.2.0.1-alpha; closes bug 1107.
9667 - Disallow BridgeRelay 1 and ORPort 0 at once in the configuration.
9668 Bugfix on 0.2.0.13-alpha; closes bug 928.
9669 - Change "Application request when we're believed to be offline."
9670 notice to "Application request when we haven't used client
9671 functionality lately.", to clarify that it's not an error. Bugfix
9672 on 0.0.9.3; fixes bug 1222.
9673 - Fix a bug in the controller interface where "GETINFO ns/asdaskljkl"
9674 would return "551 Internal error" rather than "552 Unrecognized key
9675 ns/asdaskljkl". Bugfix on 0.1.2.3-alpha.
9676 - Users can't configure a regular relay to be their bridge. It didn't
9677 work because when Tor fetched the bridge descriptor, it found
9678 that it already had it, and didn't realize that the purpose of the
9679 descriptor had changed. Now we replace routers with a purpose other
9680 than bridge with bridge descriptors when fetching them. Bugfix on
9681 0.1.1.9-alpha. Bug 1776 not yet fixed because now we immediately
9682 refetch the descriptor with router purpose 'general', disabling
9684 - Fix a rare bug in rend_fn unit tests: we would fail a test when
9685 a randomly generated port is 0. Diagnosed by Matt Edman. Bugfix
9686 on 0.2.0.10-alpha; fixes bug 1808.
9687 - Exit nodes didn't recognize EHOSTUNREACH as a plausible error code,
9688 and so sent back END_STREAM_REASON_MISC. Clients now recognize a new
9689 stream ending reason for this case: END_STREAM_REASON_NOROUTE.
9690 Servers can start sending this code when enough clients recognize
9691 it. Also update the spec to reflect this new reason. Bugfix on
9692 0.1.0.1-rc; fixes part of bug 1793.
9693 - Delay geoip stats collection by bridges for 6 hours, not 2 hours,
9694 when we switch from being a public relay to a bridge. Otherwise
9695 there will still be clients that see the relay in their consensus,
9696 and the stats will end up wrong. Bugfix on 0.2.1.15-rc; fixes bug
9698 - Instead of giving an assertion failure on an internal mismatch
9699 on estimated freelist size, just log a BUG warning and try later.
9700 Mitigates but does not fix bug 1125.
9701 - Fix an assertion failure that could occur in caches or bridge users
9702 when using a very short voting interval on a testing network.
9703 Diagnosed by Robert Hogan. Fixes bug 1141; bugfix on 0.2.0.8-alpha.
9705 o Minor bugfixes (on 0.2.2.x):
9706 - Alter directory authorities to always consider Exit-flagged nodes
9707 as potential Guard nodes in their votes. The actual decision to
9708 use Exits as Guards is done in the consensus bandwidth weights.
9709 Fixes bug 1294; bugfix on 0.2.2.10-alpha.
9710 - When the controller is reporting the purpose of circuits that
9711 didn't finish building before the circuit build timeout, it was
9712 printing UNKNOWN_13. Now print EXPIRED. Bugfix on 0.2.2.14-alpha.
9713 - Our libevent version parsing code couldn't handle versions like
9714 1.4.14b-stable and incorrectly warned the user about using an
9715 old and broken version of libevent. Treat 1.4.14b-stable like
9716 1.4.14-stable when parsing the version. Fixes bug 1731; bugfix
9718 - Don't use substitution references like $(VAR:MOD) when
9719 $(asciidoc_files) is empty -- make(1) on NetBSD transforms
9720 '$(:x)' to 'x' rather than the empty string. This bites us in
9721 doc/ when configured with --disable-asciidoc. Bugfix on
9722 0.2.2.9-alpha; fixes bug 1773.
9723 - Remove a spurious hidden service server-side log notice about
9724 "Ancient non-dirty circuits". Bugfix on 0.2.2.14-alpha; fixes
9726 - Fix compilation with --with-dmalloc set. Bugfix on 0.2.2.6-alpha;
9728 - Correctly report written bytes on linked connections. Found while
9729 implementing 1790. Bugfix on 0.2.2.4-alpha.
9730 - Fix three memory leaks: one in circuit_build_times_parse_state(),
9731 one in dirvote_add_signatures_to_pending_consensus(), and one every
9732 time we parse a v3 network consensus. Bugfixes on 0.2.2.14-alpha,
9733 0.2.2.6-alpha, and 0.2.2.10-alpha respectively; fixes bug 1831.
9735 o Code simplifications and refactoring:
9736 - Take a first step towards making or.h smaller by splitting out
9737 function definitions for all source files in src/or/. Leave
9738 structures and defines in or.h for now.
9739 - Remove a bunch of unused function declarations as well as a block of
9740 #if 0'd code from the unit tests. Closes bug 1824.
9741 - New unit tests for exit-port history statistics; refactored exit
9742 statistics code to be more easily tested.
9743 - Remove the old debian/ directory from the main Tor distribution.
9744 The official Tor-for-debian git repository lives at the URL
9745 https://git.torproject.org/debian/tor.git
9748 Changes in version 0.2.2.14-alpha - 2010-07-12
9749 Tor 0.2.2.14-alpha greatly improves client-side handling of
9750 circuit build timeouts, which are used to estimate speed and improve
9751 performance. We also move to a much better GeoIP database, port Tor to
9752 Windows CE, introduce new compile flags that improve code security,
9753 add an eighth v3 directory authority, and address a lot of more
9757 - Tor directory authorities no longer crash when started with a
9758 cached-microdesc-consensus file in their data directory. Bugfix
9759 on 0.2.2.6-alpha; fixes bug 1532.
9760 - Treat an unset $HOME like an empty $HOME rather than triggering an
9761 assert. Bugfix on 0.0.8pre1; fixes bug 1522.
9762 - Ignore negative and large circuit build timeout values that can
9763 happen during a suspend or hibernate. These values caused various
9764 asserts to fire. Bugfix on 0.2.2.2-alpha; fixes bug 1245.
9765 - Alter calculation of Pareto distribution parameter 'Xm' for
9766 Circuit Build Timeout learning to use the weighted average of the
9767 top N=3 modes (because we have three entry guards). Considering
9768 multiple modes should improve the timeout calculation in some cases,
9769 and prevent extremely high timeout values. Bugfix on 0.2.2.2-alpha;
9771 - Alter calculation of Pareto distribution parameter 'Alpha' to use a
9772 right censored distribution model. This approach improves over the
9773 synthetic timeout generation approach that was producing insanely
9774 high timeout values. Now we calculate build timeouts using truncated
9775 times. Bugfix on 0.2.2.2-alpha; fixes bugs 1245 and 1335.
9776 - Do not close circuits that are under construction when they reach
9777 the circuit build timeout. Instead, leave them building (but do not
9778 use them) for up until the time corresponding to the 95th percentile
9779 on the Pareto CDF or 60 seconds, whichever is greater. This is done
9780 to provide better data for the new Pareto model. This percentile
9781 can be controlled by the consensus.
9784 - Move to the June 2010 Maxmind GeoLite country db (rather than the
9785 June 2009 ip-to-country GeoIP db) for our statistics that count
9786 how many users relays are seeing from each country. Now we have
9787 more accurate data for many African countries.
9788 - Port Tor to build and run correctly on Windows CE systems, using
9789 the wcecompat library. Contributed by Valerio Lupi.
9790 - New "--enable-gcc-hardening" ./configure flag (off by default)
9791 to turn on gcc compile time hardening options. It ensures
9792 that signed ints have defined behavior (-fwrapv), enables
9793 -D_FORTIFY_SOURCE=2 (requiring -O2), adds stack smashing protection
9794 with canaries (-fstack-protector-all), turns on ASLR protection if
9795 supported by the kernel (-fPIE, -pie), and adds additional security
9796 related warnings. Verified to work on Mac OS X and Debian Lenny.
9797 - New "--enable-linker-hardening" ./configure flag (off by default)
9798 to turn on ELF specific hardening features (relro, now). This does
9799 not work with Mac OS X or any other non-ELF binary format.
9801 o New directory authorities:
9802 - Set up maatuska (run by Linus Nordberg) as the eighth v3 directory
9806 - New config option "WarnUnsafeSocks 0" disables the warning that
9807 occurs whenever Tor receives a socks handshake using a version of
9808 the socks protocol that can only provide an IP address (rather
9809 than a hostname). Setups that do DNS locally over Tor are fine,
9810 and we shouldn't spam the logs in that case.
9811 - Convert the HACKING file to asciidoc, and add a few new sections
9812 to it, explaining how we use Git, how we make changelogs, and
9813 what should go in a patch.
9814 - Add a TIMEOUT_RATE keyword to the BUILDTIMEOUT_SET control port
9815 event, to give information on the current rate of circuit timeouts
9816 over our stored history.
9817 - Add ability to disable circuit build time learning via consensus
9818 parameter and via a LearnCircuitBuildTimeout config option. Also
9819 automatically disable circuit build time calculation if we are
9820 either a AuthoritativeDirectory, or if we fail to write our state
9821 file. Fixes bug 1296.
9822 - More gracefully handle corrupt state files, removing asserts
9823 in favor of saving a backup and resetting state.
9824 - Rename the "log.h" header to "torlog.h" so as to conflict with fewer
9828 - Build correctly on OSX with zlib 1.2.4 and higher with all warnings
9830 - When a2x fails, mention that the user could disable manpages instead
9831 of trying to fix their asciidoc installation.
9832 - Where available, use Libevent 2.0's periodic timers so that our
9833 once-per-second cleanup code gets called even more closely to
9834 once per second than it would otherwise. Fixes bug 943.
9835 - If you run a bridge that listens on multiple IP addresses, and
9836 some user configures a bridge address that uses a different IP
9837 address than your bridge writes in its router descriptor, and the
9838 user doesn't specify an identity key, their Tor would discard the
9839 descriptor because "it isn't one of our configured bridges", and
9840 fail to bootstrap. Now believe the descriptor and bootstrap anyway.
9841 Bugfix on 0.2.0.3-alpha.
9842 - If OpenSSL fails to make a duplicate of a private or public key, log
9843 an error message and try to exit cleanly. May help with debugging
9844 if bug 1209 ever remanifests.
9845 - Save a couple bytes in memory allocation every time we escape
9846 certain characters in a string. Patch from Florian Zumbiehl.
9847 - Make it explicit that we don't cannibalize one-hop circuits. This
9848 happens in the wild, but doesn't turn out to be a problem because
9849 we fortunately don't use those circuits. Many thanks to outofwords
9850 for the initial analysis and to swissknife who confirmed that
9851 two-hop circuits are actually created.
9852 - Make directory mirrors report non-zero dirreq-v[23]-shares again.
9853 Fixes bug 1564; bugfix on 0.2.2.9-alpha.
9854 - Eliminate a case where a circuit build time warning was displayed
9855 after network connectivity resumed. Bugfix on 0.2.2.2-alpha.
9858 Changes in version 0.2.1.26 - 2010-05-02
9859 Tor 0.2.1.26 addresses the recent connection and memory overload
9860 problems we've been seeing on relays, especially relays with their
9861 DirPort open. If your relay has been crashing, or you turned it off
9862 because it used too many resources, give this release a try.
9864 This release also fixes yet another instance of broken OpenSSL libraries
9865 that was causing some relays to drop out of the consensus.
9868 - Teach relays to defend themselves from connection overload. Relays
9869 now close idle circuits early if it looks like they were intended
9870 for directory fetches. Relays are also more aggressive about closing
9871 TLS connections that have no circuits on them. Such circuits are
9872 unlikely to be re-used, and tens of thousands of them were piling
9873 up at the fast relays, causing the relays to run out of sockets
9874 and memory. Bugfix on 0.2.0.22-rc (where clients started tunneling
9875 their directory fetches over TLS).
9876 - Fix SSL renegotiation behavior on OpenSSL versions like on Centos
9877 that claim to be earlier than 0.9.8m, but which have in reality
9878 backported huge swaths of 0.9.8m or 0.9.8n renegotiation
9879 behavior. Possible fix for some cases of bug 1346.
9880 - Directory mirrors were fetching relay descriptors only from v2
9881 directory authorities, rather than v3 authorities like they should.
9882 Only 2 v2 authorities remain (compared to 7 v3 authorities), leading
9883 to a serious bottleneck. Bugfix on 0.2.0.9-alpha. Fixes bug 1324.
9886 - Finally get rid of the deprecated and now harmful notion of "clique
9887 mode", where directory authorities maintain TLS connections to
9891 - In the util/threads test, no longer free the test_mutex before all
9892 worker threads have finished. Bugfix on 0.2.1.6-alpha.
9893 - The master thread could starve the worker threads quite badly on
9894 certain systems, causing them to run only partially in the allowed
9895 window. This resulted in test failures. Now the master thread sleeps
9896 occasionally for a few microseconds while the two worker-threads
9897 compete for the mutex. Bugfix on 0.2.0.1-alpha.
9900 Changes in version 0.2.2.13-alpha - 2010-04-24
9901 Tor 0.2.2.13-alpha addresses the recent connection and memory overload
9902 problems we've been seeing on relays, especially relays with their
9903 DirPort open. If your relay has been crashing, or you turned it off
9904 because it used too many resources, give this release a try.
9907 - Teach relays to defend themselves from connection overload. Relays
9908 now close idle circuits early if it looks like they were intended
9909 for directory fetches. Relays are also more aggressive about closing
9910 TLS connections that have no circuits on them. Such circuits are
9911 unlikely to be re-used, and tens of thousands of them were piling
9912 up at the fast relays, causing the relays to run out of sockets
9913 and memory. Bugfix on 0.2.0.22-rc (where clients started tunneling
9914 their directory fetches over TLS).
9917 - Finally get rid of the deprecated and now harmful notion of "clique
9918 mode", where directory authorities maintain TLS connections to
9920 - Directory authorities now do an immediate reachability check as soon
9921 as they hear about a new relay. This change should slightly reduce
9922 the time between setting up a relay and getting listed as running
9923 in the consensus. It should also improve the time between setting
9924 up a bridge and seeing use by bridge users.
9925 - Directory authorities no longer launch a TLS connection to every
9926 relay as they startup. Now that we have 2k+ descriptors cached,
9927 the resulting network hiccup is becoming a burden. Besides,
9928 authorities already avoid voting about Running for the first half
9929 hour of their uptime.
9932 Changes in version 0.2.2.12-alpha - 2010-04-20
9933 Tor 0.2.2.12-alpha fixes a critical bug in how directory authorities
9934 handle and vote on descriptors. It was causing relays to drop out of
9938 - Many relays have been falling out of the consensus lately because
9939 not enough authorities know about their descriptor for them to get
9940 a majority of votes. When we deprecated the v2 directory protocol,
9941 we got rid of the only way that v3 authorities can hear from each
9942 other about other descriptors. Now authorities examine every v3
9943 vote for new descriptors, and fetch them from that authority. Bugfix
9945 - Fix two typos in tor_vasprintf() that broke the compile on Windows,
9946 and a warning in or.h related to bandwidth_weight_rule_t that
9947 prevented clean compile on OS X. Fixes bug 1363; bugfix on
9949 - Fix a segfault on relays when DirReqStatistics is enabled
9950 and 24 hours pass. Bug found by keb. Fixes bug 1365; bugfix on
9954 - Demote a confusing TLS warning that relay operators might get when
9955 someone tries to talk to their OrPort. It is neither the operator's
9956 fault nor can they do anything about it. Fixes bug 1364; bugfix
9960 Changes in version 0.2.2.11-alpha - 2010-04-15
9961 Tor 0.2.2.11-alpha fixes yet another instance of broken OpenSSL
9962 libraries that was causing some relays to drop out of the consensus.
9965 - Directory mirrors were fetching relay descriptors only from v2
9966 directory authorities, rather than v3 authorities like they should.
9967 Only 2 v2 authorities remain (compared to 7 v3 authorities), leading
9968 to a serious bottleneck. Bugfix on 0.2.0.9-alpha. Fixes bug 1324.
9969 - Fix a parsing error that made every possible value of
9970 CircPriorityHalflifeMsec get treated as "1 msec". Bugfix
9971 on 0.2.2.7-alpha. Rename CircPriorityHalflifeMsec to
9972 CircuitPriorityHalflifeMsec, so authorities can tell newer relays
9973 about the option without breaking older ones.
9974 - Fix SSL renegotiation behavior on OpenSSL versions like on Centos
9975 that claim to be earlier than 0.9.8m, but which have in reality
9976 backported huge swaths of 0.9.8m or 0.9.8n renegotiation
9977 behavior. Possible fix for some cases of bug 1346.
9980 - Experiment with a more aggressive approach to preventing clients
9981 from making one-hop exit streams. Exit relays who want to try it
9982 out can set "RefuseUnknownExits 1" in their torrc, and then look
9983 for "Attempt by %s to open a stream" log messages. Let us know
9985 - Add support for statically linking zlib by specifying
9986 --enable-static-zlib, to go with our support for statically linking
9987 openssl and libevent. Resolves bug 1358.
9990 - Fix a segfault that happens whenever a Tor client that is using
9991 libevent2's bufferevents gets a hup signal. Bugfix on 0.2.2.5-alpha;
9993 - When we cleaned up the contrib/tor-exit-notice.html file, we left
9994 out the first line. Fixes bug 1295.
9995 - When building the manpage from a tarball, we required asciidoc, but
9996 the asciidoc -> roff/html conversion was already done for the
9997 tarball. Make 'make' complain only when we need asciidoc (either
9998 because we're compiling directly from git, or because we altered
9999 the asciidoc manpage in the tarball). Bugfix on 0.2.2.9-alpha.
10000 - When none of the directory authorities vote on any params, Tor
10001 segfaulted when trying to make the consensus from the votes. We
10002 didn't trigger the bug in practice, because authorities do include
10003 params in their votes. Bugfix on 0.2.2.10-alpha; fixes bug 1322.
10006 - In the util/threads test, no longer free the test_mutex before all
10007 worker threads have finished. Bugfix on 0.2.1.6-alpha.
10008 - The master thread could starve the worker threads quite badly on
10009 certain systems, causing them to run only partially in the allowed
10010 window. This resulted in test failures. Now the master thread sleeps
10011 occasionally for a few microseconds while the two worker-threads
10012 compete for the mutex. Bugfix on 0.2.0.1-alpha.
10015 Changes in version 0.2.2.10-alpha - 2010-03-07
10016 Tor 0.2.2.10-alpha fixes a regression introduced in 0.2.2.9-alpha that
10017 could prevent relays from guessing their IP address correctly. It also
10018 starts the groundwork for another client-side performance boost, since
10019 currently we're not making efficient use of relays that have both the
10020 Guard flag and the Exit flag.
10023 - Fix a regression from our patch for bug 1244 that caused relays
10024 to guess their IP address incorrectly if they didn't set Address
10025 in their torrc and/or their address fails to resolve. Bugfix on
10026 0.2.2.9-alpha; fixes bug 1269.
10028 o Major features (performance):
10029 - Directory authorities now compute consensus weightings that instruct
10030 clients how to weight relays flagged as Guard, Exit, Guard+Exit,
10031 and no flag. Clients that use these weightings will distribute
10032 network load more evenly across these different relay types. The
10033 weightings are in the consensus so we can change them globally in
10034 the future. Extra thanks to "outofwords" for finding some nasty
10035 security bugs in the first implementation of this feature.
10037 o Minor features (performance):
10038 - Always perform router selections using weighted relay bandwidth,
10039 even if we don't need a high capacity circuit at the time. Non-fast
10040 circuits now only differ from fast ones in that they can use relays
10041 not marked with the Fast flag. This "feature" could turn out to
10042 be a horrible bug; we should investigate more before it goes into
10046 - Allow disabling building of the manpages. Skipping the manpage
10047 speeds up the build considerably.
10049 o Minor bugfixes (on 0.2.2.x):
10050 - Fix a memleak in the EXTENDCIRCUIT logic. Spotted by coverity.
10051 Bugfix on 0.2.2.9-alpha.
10052 - Disallow values larger than INT32_MAX for PerConnBWRate|Burst
10053 config option. Bugfix on 0.2.2.7-alpha.
10054 - Ship the asciidoc-helper file in the tarball, so that people can
10055 build from source if they want to, and touching the .1.txt files
10056 doesn't break the build. Bugfix on 0.2.2.9-alpha.
10058 o Minor bugfixes (on 0.2.1.x or earlier):
10059 - Fix a dereference-then-NULL-check sequence when publishing
10060 descriptors. Bugfix on 0.2.1.5-alpha. Discovered by ekir; fixes
10062 - Fix another dereference-then-NULL-check sequence. Bugfix on
10063 0.2.1.14-rc. Discovered by ekir; fixes bug 1256.
10064 - Make sure we treat potentially not NUL-terminated strings correctly.
10065 Bugfix on 0.1.1.13-alpha. Discovered by rieo; fixes bug 1257.
10067 o Code simplifications and refactoring:
10068 - Fix some urls in the exit notice file and make it XHTML1.1 strict
10069 compliant. Based on a patch from Christian Kujau.
10070 - Don't use sed in asciidoc-helper anymore.
10071 - Make the build process fail if asciidoc cannot be found and
10072 building with asciidoc isn't disabled.
10075 Changes in version 0.2.2.9-alpha - 2010-02-22
10076 Tor 0.2.2.9-alpha makes Tor work again on the latest OS X, updates the
10077 location of a directory authority, and cleans up a bunch of small bugs.
10079 o Directory authority changes:
10080 - Change IP address for dannenberg (v3 directory authority), and
10081 remove moria2 (obsolete v1, v2 directory authority and v0 hidden
10082 service directory authority) from the list.
10085 - Make Tor work again on the latest OS X: when deciding whether to
10086 use strange flags to turn TLS renegotiation on, detect the OpenSSL
10087 version at run-time, not compile time. We need to do this because
10088 Apple doesn't update its dev-tools headers when it updates its
10089 libraries in a security patch.
10090 - Fix a potential buffer overflow in lookup_last_hid_serv_request()
10091 that could happen on 32-bit platforms with 64-bit time_t. Also fix
10092 a memory leak when requesting a hidden service descriptor we've
10093 requested before. Fixes bug 1242, bugfix on 0.2.0.18-alpha. Found
10095 - Authorities could be tricked into giving out the Exit flag to relays
10096 that didn't allow exiting to any ports. This bug could screw
10097 with load balancing and stats. Bugfix on 0.1.1.6-alpha; fixes bug
10098 1238. Bug discovered by Martin Kowalczyk.
10099 - When freeing a session key, zero it out completely. We only zeroed
10100 the first ptrsize bytes. Bugfix on 0.0.2pre8. Discovered and
10101 patched by ekir. Fixes bug 1254.
10104 - Fix static compilation by listing the openssl libraries in the right
10105 order. Bugfix on Tor 0.2.2.8-alpha; fixes bug 1237.
10106 - Resume handling .exit hostnames in a special way: originally we
10107 stripped the .exit part and used the requested exit relay. In
10108 0.2.2.1-alpha we stopped treating them in any special way, meaning
10109 if you use a .exit address then Tor will pass it on to the exit
10110 relay. Now we reject the .exit stream outright, since that behavior
10111 might be more expected by the user. Found and diagnosed by Scott
10112 Bennett and Downie on or-talk.
10113 - Don't spam the controller with events when we have no file
10114 descriptors available. Bugfix on 0.2.1.5-alpha. (Rate-limiting
10115 for log messages was already solved from bug 748.)
10116 - Avoid a bogus overlapped memcpy in tor_addr_copy(). Reported by
10118 - Make the DNSPort option work with libevent 2.x. Don't alter the
10119 behavior for libevent 1.x. Fixes bug 1143. Found by SwissTorExit.
10120 - Emit a GUARD DROPPED controller event for a case we missed.
10121 - Make more fields in the controller protocol case-insensitive, since
10122 control-spec.txt said they were.
10123 - Refactor resolve_my_address() to not use gethostbyname() anymore.
10124 Fixes bug 1244; bugfix on 0.0.2pre25. Reported by Mike Mestnik.
10125 - Fix a spec conformance issue: the network-status-version token
10126 must be the first token in a v3 consensus or vote. Discovered by
10127 parakeep. Bugfix on 0.2.0.3-alpha.
10129 o Code simplifications and refactoring:
10130 - Generate our manpage and HTML documentation using Asciidoc. This
10131 change should make it easier to maintain the documentation, and
10132 produce nicer HTML.
10133 - Remove the --enable-iphone option. According to reports from Marco
10134 Bonetti, Tor builds fine without any special tweaking on recent
10135 iPhone SDK versions.
10136 - Removed some unnecessary files from the source distribution. The
10137 AUTHORS file has now been merged into the people page on the
10138 website. The roadmaps and design doc can now be found in the
10139 projects directory in svn.
10140 - Enabled various circuit build timeout constants to be controlled
10141 by consensus parameters. Also set better defaults for these
10142 parameters based on experimentation on broadband and simulated
10143 high latency links.
10146 - The 'EXTENDCIRCUIT' control port command can now be used with
10147 a circ id of 0 and no path. This feature will cause Tor to build
10148 a new 'fast' general purpose circuit using its own path selection
10150 - Added a BUILDTIMEOUT_SET controller event to describe changes
10151 to the circuit build timeout.
10152 - Future-proof the controller protocol a bit by ignoring keyword
10153 arguments we do not recognize.
10154 - Expand homedirs passed to tor-checkkey. This should silence a
10155 coverity complaint about passing a user-supplied string into
10156 open() without checking it.
10159 Changes in version 0.2.1.25 - 2010-03-16
10160 Tor 0.2.1.25 fixes a regression introduced in 0.2.1.23 that could
10161 prevent relays from guessing their IP address correctly. It also fixes
10162 several minor potential security bugs.
10165 - Fix a regression from our patch for bug 1244 that caused relays
10166 to guess their IP address incorrectly if they didn't set Address
10167 in their torrc and/or their address fails to resolve. Bugfix on
10168 0.2.1.23; fixes bug 1269.
10169 - When freeing a session key, zero it out completely. We only zeroed
10170 the first ptrsize bytes. Bugfix on 0.0.2pre8. Discovered and
10171 patched by ekir. Fixes bug 1254.
10174 - Fix a dereference-then-NULL-check sequence when publishing
10175 descriptors. Bugfix on 0.2.1.5-alpha. Discovered by ekir; fixes
10177 - Fix another dereference-then-NULL-check sequence. Bugfix on
10178 0.2.1.14-rc. Discovered by ekir; fixes bug 1256.
10179 - Make sure we treat potentially not NUL-terminated strings correctly.
10180 Bugfix on 0.1.1.13-alpha. Discovered by rieo; fixes bug 1257.
10184 Changes in version 0.2.1.24 - 2010-02-21
10185 Tor 0.2.1.24 makes Tor work again on the latest OS X -- this time
10189 - Work correctly out-of-the-box with even more vendor-patched versions
10190 of OpenSSL. In particular, make it so Debian and OS X don't need
10191 customized patches to run/build.
10194 Changes in version 0.2.1.23 - 2010-02-13
10195 Tor 0.2.1.23 fixes a huge client-side performance bug, makes Tor work
10196 again on the latest OS X, and updates the location of a directory
10199 o Major bugfixes (performance):
10200 - We were selecting our guards uniformly at random, and then weighting
10201 which of our guards we'd use uniformly at random. This imbalance
10202 meant that Tor clients were severely limited on throughput (and
10203 probably latency too) by the first hop in their circuit. Now we
10204 select guards weighted by currently advertised bandwidth. We also
10205 automatically discard guards picked using the old algorithm. Fixes
10206 bug 1217; bugfix on 0.2.1.3-alpha. Found by Mike Perry.
10209 - Make Tor work again on the latest OS X: when deciding whether to
10210 use strange flags to turn TLS renegotiation on, detect the OpenSSL
10211 version at run-time, not compile time. We need to do this because
10212 Apple doesn't update its dev-tools headers when it updates its
10213 libraries in a security patch.
10214 - Fix a potential buffer overflow in lookup_last_hid_serv_request()
10215 that could happen on 32-bit platforms with 64-bit time_t. Also fix
10216 a memory leak when requesting a hidden service descriptor we've
10217 requested before. Fixes bug 1242, bugfix on 0.2.0.18-alpha. Found
10220 o Directory authority changes:
10221 - Change IP address for dannenberg (v3 directory authority), and
10222 remove moria2 (obsolete v1, v2 directory authority and v0 hidden
10223 service directory authority) from the list.
10226 - Refactor resolve_my_address() to not use gethostbyname() anymore.
10227 Fixes bug 1244; bugfix on 0.0.2pre25. Reported by Mike Mestnik.
10230 - Avoid a mad rush at the beginning of each month when each client
10231 rotates half of its guards. Instead we spread the rotation out
10232 throughout the month, but we still avoid leaving a precise timestamp
10233 in the state file about when we first picked the guard. Improves
10234 over the behavior introduced in 0.1.2.17.
10237 Changes in version 0.2.2.8-alpha - 2010-01-26
10238 Tor 0.2.2.8-alpha fixes a crash bug in 0.2.2.7-alpha that has been
10239 causing bridge relays to disappear. If you're running a bridge,
10243 - Fix a memory corruption bug on bridges that occured during the
10244 inclusion of stats data in extra-info descriptors. Also fix the
10245 interface for geoip_get_bridge_stats* to prevent similar bugs in
10246 the future. Diagnosis by Tas, patch by Karsten and Sebastian.
10247 Fixes bug 1208; bugfix on 0.2.2.7-alpha.
10250 - Ignore OutboundBindAddress when connecting to localhost.
10251 Connections to localhost need to come _from_ localhost, or else
10252 local servers (like DNS and outgoing HTTP/SOCKS proxies) will often
10256 Changes in version 0.2.2.7-alpha - 2010-01-19
10257 Tor 0.2.2.7-alpha fixes a huge client-side performance bug, as well
10258 as laying the groundwork for further relay-side performance fixes. It
10259 also starts cleaning up client behavior with respect to the EntryNodes,
10260 ExitNodes, and StrictNodes config options.
10262 This release also rotates two directory authority keys, due to a
10263 security breach of some of the Torproject servers.
10265 o Directory authority changes:
10266 - Rotate keys (both v3 identity and relay identity) for moria1
10269 o Major features (performance):
10270 - We were selecting our guards uniformly at random, and then weighting
10271 which of our guards we'd use uniformly at random. This imbalance
10272 meant that Tor clients were severely limited on throughput (and
10273 probably latency too) by the first hop in their circuit. Now we
10274 select guards weighted by currently advertised bandwidth. We also
10275 automatically discard guards picked using the old algorithm. Fixes
10276 bug 1217; bugfix on 0.2.1.3-alpha. Found by Mike Perry.
10277 - When choosing which cells to relay first, relays can now favor
10278 circuits that have been quiet recently, to provide lower latency
10279 for low-volume circuits. By default, relays enable or disable this
10280 feature based on a setting in the consensus. You can override
10281 this default by using the new "CircuitPriorityHalflife" config
10282 option. Design and code by Ian Goldberg, Can Tang, and Chris
10284 - Add separate per-conn write limiting to go with the per-conn read
10285 limiting. We added a global write limit in Tor 0.1.2.5-alpha,
10286 but never per-conn write limits.
10287 - New consensus params "bwconnrate" and "bwconnburst" to let us
10288 rate-limit client connections as they enter the network. It's
10289 controlled in the consensus so we can turn it on and off for
10290 experiments. It's starting out off. Based on proposal 163.
10292 o Major features (relay selection options):
10293 - Switch to a StrictNodes config option, rather than the previous
10294 "StrictEntryNodes" / "StrictExitNodes" separation that was missing a
10295 "StrictExcludeNodes" option.
10296 - If EntryNodes, ExitNodes, ExcludeNodes, or ExcludeExitNodes
10297 change during a config reload, mark and discard all our origin
10298 circuits. This fix should address edge cases where we change the
10299 config options and but then choose a circuit that we created before
10301 - If EntryNodes or ExitNodes are set, be more willing to use an
10302 unsuitable (e.g. slow or unstable) circuit. The user asked for it,
10304 - Make EntryNodes config option much more aggressive even when
10305 StrictNodes is not set. Before it would prepend your requested
10306 entrynodes to your list of guard nodes, but feel free to use others
10307 after that. Now it chooses only from your EntryNodes if any of
10308 those are available, and only falls back to others if a) they're
10309 all down and b) StrictNodes is not set.
10310 - Now we refresh your entry guards from EntryNodes at each consensus
10311 fetch -- rather than just at startup and then they slowly rot as
10312 the network changes.
10315 - Stop bridge directory authorities from answering dbg-stability.txt
10316 directory queries, which would let people fetch a list of all
10317 bridge identities they track. Bugfix on 0.2.1.6-alpha.
10320 - Log a notice when we get a new control connection. Now it's easier
10321 for security-conscious users to recognize when a local application
10322 is knocking on their controller door. Suggested by bug 1196.
10323 - New config option "CircuitStreamTimeout" to override our internal
10324 timeout schedule for how many seconds until we detach a stream from
10325 a circuit and try a new circuit. If your network is particularly
10326 slow, you might want to set this to a number like 60.
10327 - New controller command "getinfo config-text". It returns the
10328 contents that Tor would write if you send it a SAVECONF command,
10329 so the controller can write the file to disk itself.
10330 - New options for SafeLogging to allow scrubbing only log messages
10331 generated while acting as a relay.
10332 - Ship the bridges spec file in the tarball too.
10333 - Avoid a mad rush at the beginning of each month when each client
10334 rotates half of its guards. Instead we spread the rotation out
10335 throughout the month, but we still avoid leaving a precise timestamp
10336 in the state file about when we first picked the guard. Improves
10337 over the behavior introduced in 0.1.2.17.
10339 o Minor bugfixes (compiling):
10340 - Fix compilation on OS X 10.3, which has a stub mlockall() but
10341 hides it. Bugfix on 0.2.2.6-alpha.
10342 - Fix compilation on Solaris by removing support for the
10343 DisableAllSwap config option. Solaris doesn't have an rlimit for
10344 mlockall, so we cannot use it safely. Fixes bug 1198; bugfix on
10347 o Minor bugfixes (crashes):
10348 - Do not segfault when writing buffer stats when we haven't observed
10349 a single circuit to report about. Found by Fabian Lanze. Bugfix on
10351 - If we're in the pathological case where there's no exit bandwidth
10352 but there is non-exit bandwidth, or no guard bandwidth but there
10353 is non-guard bandwidth, don't crash during path selection. Bugfix
10355 - Fix an impossible-to-actually-trigger buffer overflow in relay
10356 descriptor generation. Bugfix on 0.1.0.15.
10358 o Minor bugfixes (privacy):
10359 - Fix an instance where a Tor directory mirror might accidentally
10360 log the IP address of a misbehaving Tor client. Bugfix on
10362 - Don't list Windows capabilities in relay descriptors. We never made
10363 use of them, and maybe it's a bad idea to publish them. Bugfix
10366 o Minor bugfixes (other):
10367 - Resolve an edge case in path weighting that could make us misweight
10368 our relay selection. Fixes bug 1203; bugfix on 0.0.8rc1.
10369 - Fix statistics on client numbers by country as seen by bridges that
10370 were broken in 0.2.2.1-alpha. Also switch to reporting full 24-hour
10371 intervals instead of variable 12-to-48-hour intervals.
10372 - After we free an internal connection structure, overwrite it
10373 with a different memory value than we use for overwriting a freed
10374 internal circuit structure. Should help with debugging. Suggested
10376 - Update our OpenSSL 0.9.8l fix so that it works with OpenSSL 0.9.8m
10379 o Removed features:
10380 - Remove the HSAuthorityRecordStats option that version 0 hidden
10381 service authorities could have used to track statistics of overall
10382 hidden service usage.
10385 Changes in version 0.2.1.22 - 2010-01-19
10386 Tor 0.2.1.22 fixes a critical privacy problem in bridge directory
10387 authorities -- it would tell you its whole history of bridge descriptors
10388 if you make the right directory request. This stable update also
10389 rotates two of the seven v3 directory authority keys and locations.
10391 o Directory authority changes:
10392 - Rotate keys (both v3 identity and relay identity) for moria1
10396 - Stop bridge directory authorities from answering dbg-stability.txt
10397 directory queries, which would let people fetch a list of all
10398 bridge identities they track. Bugfix on 0.2.1.6-alpha.
10401 Changes in version 0.2.1.21 - 2009-12-21
10402 Tor 0.2.1.21 fixes an incompatibility with the most recent OpenSSL
10403 library. If you use Tor on Linux / Unix and you're getting SSL
10404 renegotiation errors, upgrading should help. We also recommend an
10405 upgrade if you're an exit relay.
10408 - Work around a security feature in OpenSSL 0.9.8l that prevents our
10409 handshake from working unless we explicitly tell OpenSSL that we
10410 are using SSL renegotiation safely. We are, of course, but OpenSSL
10411 0.9.8l won't work unless we say we are.
10412 - Avoid crashing if the client is trying to upload many bytes and the
10413 circuit gets torn down at the same time, or if the flip side
10414 happens on the exit relay. Bugfix on 0.2.0.1-alpha; fixes bug 1150.
10417 - Do not refuse to learn about authority certs and v2 networkstatus
10418 documents that are older than the latest consensus. This bug might
10419 have degraded client bootstrapping. Bugfix on 0.2.0.10-alpha.
10420 Spotted and fixed by xmux.
10421 - Fix a couple of very-hard-to-trigger memory leaks, and one hard-to-
10422 trigger platform-specific option misparsing case found by Coverity
10424 - Fix a compilation warning on Fedora 12 by removing an impossible-to-
10425 trigger assert. Fixes bug 1173.
10428 Changes in version 0.2.2.6-alpha - 2009-11-19
10429 Tor 0.2.2.6-alpha lays the groundwork for many upcoming features:
10430 support for the new lower-footprint "microdescriptor" directory design,
10431 future-proofing our consensus format against new hash functions or
10432 other changes, and an Android port. It also makes Tor compatible with
10433 the upcoming OpenSSL 0.9.8l release, and fixes a variety of bugs.
10436 - Directory authorities can now create, vote on, and serve multiple
10437 parallel formats of directory data as part of their voting process.
10438 Partially implements Proposal 162: "Publish the consensus in
10440 - Directory authorities can now agree on and publish small summaries
10441 of router information that clients can use in place of regular
10442 server descriptors. This transition will eventually allow clients
10443 to use far less bandwidth for downloading information about the
10444 network. Begins the implementation of Proposal 158: "Clients
10445 download consensus + microdescriptors".
10446 - The directory voting system is now extensible to use multiple hash
10447 algorithms for signatures and resource selection. Newer formats
10448 are signed with SHA256, with a possibility for moving to a better
10449 hash algorithm in the future.
10450 - New DisableAllSwap option. If set to 1, Tor will attempt to lock all
10451 current and future memory pages via mlockall(). On supported
10452 platforms (modern Linux and probably BSD but not Windows or OS X),
10453 this should effectively disable any and all attempts to page out
10454 memory. This option requires that you start your Tor as root --
10455 if you use DisableAllSwap, please consider using the User option
10456 to properly reduce the privileges of your Tor.
10457 - Numerous changes, bugfixes, and workarounds from Nathan Freitas
10458 to help Tor build correctly for Android phones.
10461 - Work around a security feature in OpenSSL 0.9.8l that prevents our
10462 handshake from working unless we explicitly tell OpenSSL that we
10463 are using SSL renegotiation safely. We are, but OpenSSL 0.9.8l
10464 won't work unless we say we are.
10467 - Fix a crash bug when trying to initialize the evdns module in
10468 Libevent 2. Bugfix on 0.2.1.16-rc.
10469 - Stop logging at severity 'warn' when some other Tor client tries
10470 to establish a circuit with us using weak DH keys. It's a protocol
10471 violation, but that doesn't mean ordinary users need to hear about
10472 it. Fixes the bug part of bug 1114. Bugfix on 0.1.0.13.
10473 - Do not refuse to learn about authority certs and v2 networkstatus
10474 documents that are older than the latest consensus. This bug might
10475 have degraded client bootstrapping. Bugfix on 0.2.0.10-alpha.
10476 Spotted and fixed by xmux.
10477 - Fix numerous small code-flaws found by Coverity Scan Rung 3.
10478 - If all authorities restart at once right before a consensus vote,
10479 nobody will vote about "Running", and clients will get a consensus
10480 with no usable relays. Instead, authorities refuse to build a
10481 consensus if this happens. Bugfix on 0.2.0.10-alpha; fixes bug 1066.
10482 - If your relay can't keep up with the number of incoming create
10483 cells, it would log one warning per failure into your logs. Limit
10484 warnings to 1 per minute. Bugfix on 0.0.2pre10; fixes bug 1042.
10485 - Bridges now use "reject *:*" as their default exit policy. Bugfix
10486 on 0.2.0.3-alpha; fixes bug 1113.
10487 - Fix a memory leak on directory authorities during voting that was
10488 introduced in 0.2.2.1-alpha. Found via valgrind.
10491 Changes in version 0.2.1.20 - 2009-10-15
10492 Tor 0.2.1.20 fixes a crash bug when you're accessing many hidden
10493 services at once, prepares for more performance improvements, and
10494 fixes a bunch of smaller bugs.
10496 The Windows and OS X bundles also include a more recent Vidalia,
10497 and switch from Privoxy to Polipo.
10499 The OS X installers are now drag and drop. It's best to un-install
10500 Tor/Vidalia and then install this new bundle, rather than upgrade. If
10501 you want to upgrade, you'll need to update the paths for Tor and Polipo
10502 in the Vidalia Settings window.
10505 - Send circuit or stream sendme cells when our window has decreased
10506 by 100 cells, not when it has decreased by 101 cells. Bug uncovered
10507 by Karsten when testing the "reduce circuit window" performance
10508 patch. Bugfix on the 54th commit on Tor -- from July 2002,
10509 before the release of Tor 0.0.0. This is the new winner of the
10511 - Fix a remotely triggerable memory leak when a consensus document
10512 contains more than one signature from the same voter. Bugfix on
10514 - Avoid segfault in rare cases when finishing an introduction circuit
10515 as a client and finding out that we don't have an introduction key
10516 for it. Fixes bug 1073. Reported by Aaron Swartz.
10519 - Tor now reads the "circwindow" parameter out of the consensus,
10520 and uses that value for its circuit package window rather than the
10521 default of 1000 cells. Begins the implementation of proposal 168.
10523 o New directory authorities:
10524 - Set up urras (run by Jacob Appelbaum) as the seventh v3 directory
10526 - Move moria1 and tonga to alternate IP addresses.
10529 - Fix a signed/unsigned compile warning in 0.2.1.19.
10530 - Fix possible segmentation fault on directory authorities. Bugfix on
10532 - Fix an extremely rare infinite recursion bug that could occur if
10533 we tried to log a message after shutting down the log subsystem.
10534 Found by Matt Edman. Bugfix on 0.2.0.16-alpha.
10535 - Fix an obscure bug where hidden services on 64-bit big-endian
10536 systems might mis-read the timestamp in v3 introduce cells, and
10537 refuse to connect back to the client. Discovered by "rotor".
10538 Bugfix on 0.2.1.6-alpha.
10539 - We were triggering a CLOCK_SKEW controller status event whenever
10540 we connect via the v2 connection protocol to any relay that has
10541 a wrong clock. Instead, we should only inform the controller when
10542 it's a trusted authority that claims our clock is wrong. Bugfix
10543 on 0.2.0.20-rc; starts to fix bug 1074. Reported by SwissTorExit.
10544 - We were telling the controller about CHECKING_REACHABILITY and
10545 REACHABILITY_FAILED status events whenever we launch a testing
10546 circuit or notice that one has failed. Instead, only tell the
10547 controller when we want to inform the user of overall success or
10548 overall failure. Bugfix on 0.1.2.6-alpha. Fixes bug 1075. Reported
10550 - Don't warn when we're using a circuit that ends with a node
10551 excluded in ExcludeExitNodes, but the circuit is not used to access
10552 the outside world. This should help fix bug 1090. Bugfix on
10554 - Work around a small memory leak in some versions of OpenSSL that
10555 stopped the memory used by the hostname TLS extension from being
10559 - Add a "getinfo status/accepted-server-descriptor" controller
10560 command, which is the recommended way for controllers to learn
10561 whether our server descriptor has been successfully received by at
10562 least on directory authority. Un-recommend good-server-descriptor
10563 getinfo and status events until we have a better design for them.
10566 Changes in version 0.2.2.5-alpha - 2009-10-11
10567 Tor 0.2.2.5-alpha fixes a few compile problems in 0.2.2.4-alpha.
10570 - Make the tarball compile again. Oops. Bugfix on 0.2.2.4-alpha.
10572 o Directory authorities:
10573 - Temporarily (just for this release) move dizum to an alternate
10577 Changes in version 0.2.2.4-alpha - 2009-10-10
10578 Tor 0.2.2.4-alpha fixes more crash bugs in 0.2.2.2-alpha. It also
10579 introduces a new unit test framework, shifts directry authority
10580 addresses around to reduce the impact from recent blocking events,
10581 and fixes a few smaller bugs.
10584 - Fix several more asserts in the circuit_build_times code, for
10585 example one that causes Tor to fail to start once we have
10586 accumulated 5000 build times in the state file. Bugfixes on
10587 0.2.2.2-alpha; fixes bug 1108.
10589 o New directory authorities:
10590 - Move moria1 and Tonga to alternate IP addresses.
10593 - Log SSL state transitions at debug level during handshake, and
10594 include SSL states in error messages. This may help debug future
10595 SSL handshake issues.
10596 - Add a new "Handshake" log domain for activities that happen
10597 during the TLS handshake.
10598 - Revert to the "June 3 2009" ip-to-country file. The September one
10599 seems to have removed most US IP addresses.
10600 - Directory authorities now reject Tor relays with versions less than
10601 0.1.2.14. This step cuts out four relays from the current network,
10602 none of which are very big.
10605 - Fix a couple of smaller issues with gathering statistics. Bugfixes
10607 - Fix two memory leaks in the error case of
10608 circuit_build_times_parse_state(). Bugfix on 0.2.2.2-alpha.
10609 - Don't count one-hop circuits when we're estimating how long it
10610 takes circuits to build on average. Otherwise we'll set our circuit
10611 build timeout lower than we should. Bugfix on 0.2.2.2-alpha.
10612 - Directory authorities no longer change their opinion of, or vote on,
10613 whether a router is Running, unless they have themselves been
10614 online long enough to have some idea. Bugfix on 0.2.0.6-alpha.
10617 o Code simplifications and refactoring:
10618 - Revise our unit tests to use the "tinytest" framework, so we
10619 can run tests in their own processes, have smarter setup/teardown
10620 code, and so on. The unit test code has moved to its own
10621 subdirectory, and has been split into multiple modules.
10624 Changes in version 0.2.2.3-alpha - 2009-09-23
10625 Tor 0.2.2.3-alpha fixes a few crash bugs in 0.2.2.2-alpha.
10628 - Fix an overzealous assert in our new circuit build timeout code.
10629 Bugfix on 0.2.2.2-alpha; fixes bug 1103.
10632 - If the networkstatus consensus tells us that we should use a
10633 negative circuit package window, ignore it. Otherwise we'll
10634 believe it and then trigger an assert. Bugfix on 0.2.2.2-alpha.
10637 Changes in version 0.2.2.2-alpha - 2009-09-21
10638 Tor 0.2.2.2-alpha introduces our latest performance improvement for
10639 clients: Tor tracks the average time it takes to build a circuit, and
10640 avoids using circuits that take too long to build. For fast connections,
10641 this feature can cut your expected latency in half. For slow or flaky
10642 connections, it could ruin your Tor experience. Let us know if it does!
10645 - Tor now tracks how long it takes to build client-side circuits
10646 over time, and adapts its timeout to local network performance.
10647 Since a circuit that takes a long time to build will also provide
10648 bad performance, we get significant latency improvements by
10649 discarding the slowest 20% of circuits. Specifically, Tor creates
10650 circuits more aggressively than usual until it has enough data
10651 points for a good timeout estimate. Implements proposal 151.
10652 We are especially looking for reports (good and bad) from users with
10653 both EDGE and broadband connections that can move from broadband
10654 to EDGE and find out if the build-time data in the .tor/state gets
10655 reset without loss of Tor usability. You should also see a notice
10656 log message telling you that Tor has reset its timeout.
10657 - Directory authorities can now vote on arbitary integer values as
10658 part of the consensus process. This is designed to help set
10659 network-wide parameters. Implements proposal 167.
10660 - Tor now reads the "circwindow" parameter out of the consensus,
10661 and uses that value for its circuit package window rather than the
10662 default of 1000 cells. Begins the implementation of proposal 168.
10665 - Fix a remotely triggerable memory leak when a consensus document
10666 contains more than one signature from the same voter. Bugfix on
10670 - Fix an extremely rare infinite recursion bug that could occur if
10671 we tried to log a message after shutting down the log subsystem.
10672 Found by Matt Edman. Bugfix on 0.2.0.16-alpha.
10673 - Fix parsing for memory or time units given without a space between
10674 the number and the unit. Bugfix on 0.2.2.1-alpha; fixes bug 1076.
10675 - A networkstatus vote must contain exactly one signature. Spec
10676 conformance issue. Bugfix on 0.2.0.3-alpha.
10677 - Fix an obscure bug where hidden services on 64-bit big-endian
10678 systems might mis-read the timestamp in v3 introduce cells, and
10679 refuse to connect back to the client. Discovered by "rotor".
10680 Bugfix on 0.2.1.6-alpha.
10681 - We were triggering a CLOCK_SKEW controller status event whenever
10682 we connect via the v2 connection protocol to any relay that has
10683 a wrong clock. Instead, we should only inform the controller when
10684 it's a trusted authority that claims our clock is wrong. Bugfix
10685 on 0.2.0.20-rc; starts to fix bug 1074. Reported by SwissTorExit.
10686 - We were telling the controller about CHECKING_REACHABILITY and
10687 REACHABILITY_FAILED status events whenever we launch a testing
10688 circuit or notice that one has failed. Instead, only tell the
10689 controller when we want to inform the user of overall success or
10690 overall failure. Bugfix on 0.1.2.6-alpha. Fixes bug 1075. Reported
10692 - Don't warn when we're using a circuit that ends with a node
10693 excluded in ExcludeExitNodes, but the circuit is not used to access
10694 the outside world. This should help fix bug 1090, but more problems
10695 remain. Bugfix on 0.2.1.6-alpha.
10696 - Work around a small memory leak in some versions of OpenSSL that
10697 stopped the memory used by the hostname TLS extension from being
10699 - Make our 'torify' script more portable; if we have only one of
10700 'torsocks' or 'tsocks' installed, don't complain to the user;
10701 and explain our warning about tsocks better.
10704 - Add a "getinfo status/accepted-server-descriptor" controller
10705 command, which is the recommended way for controllers to learn
10706 whether our server descriptor has been successfully received by at
10707 least on directory authority. Un-recommend good-server-descriptor
10708 getinfo and status events until we have a better design for them.
10709 - Update to the "September 4 2009" ip-to-country file.
10712 Changes in version 0.2.2.1-alpha - 2009-08-26
10713 Tor 0.2.2.1-alpha disables ".exit" address notation by default, allows
10714 Tor clients to bootstrap on networks where only port 80 is reachable,
10715 makes it more straightforward to support hardware crypto accelerators,
10716 and starts the groundwork for gathering stats safely at relays.
10719 - Start the process of disabling ".exit" address notation, since it
10720 can be used for a variety of esoteric application-level attacks
10721 on users. To reenable it, set "AllowDotExit 1" in your torrc. Fix
10724 o New directory authorities:
10725 - Set up urras (run by Jacob Appelbaum) as the seventh v3 directory
10729 - New AccelName and AccelDir options add support for dynamic OpenSSL
10730 hardware crypto acceleration engines.
10731 - Tor now supports tunneling all of its outgoing connections over
10732 a SOCKS proxy, using the SOCKS4Proxy and/or SOCKS5Proxy
10733 configuration options. Code by Christopher Davis.
10736 - Send circuit or stream sendme cells when our window has decreased
10737 by 100 cells, not when it has decreased by 101 cells. Bug uncovered
10738 by Karsten when testing the "reduce circuit window" performance
10739 patch. Bugfix on the 54th commit on Tor -- from July 2002,
10740 before the release of Tor 0.0.0. This is the new winner of the
10743 o New options for gathering stats safely:
10744 - Directory mirrors that set "DirReqStatistics 1" write statistics
10745 about directory requests to disk every 24 hours. As compared to the
10746 --enable-geoip-stats flag in 0.2.1.x, there are a few improvements:
10747 1) stats are written to disk exactly every 24 hours; 2) estimated
10748 shares of v2 and v3 requests are determined as mean values, not at
10749 the end of a measurement period; 3) unresolved requests are listed
10750 with country code '??'; 4) directories also measure download times.
10751 - Exit nodes that set "ExitPortStatistics 1" write statistics on the
10752 number of exit streams and transferred bytes per port to disk every
10754 - Relays that set "CellStatistics 1" write statistics on how long
10755 cells spend in their circuit queues to disk every 24 hours.
10756 - Entry nodes that set "EntryStatistics 1" write statistics on the
10757 rough number and origins of connecting clients to disk every 24
10759 - Relays that write any of the above statistics to disk and set
10760 "ExtraInfoStatistics 1" include the past 24 hours of statistics in
10761 their extra-info documents.
10764 - New --digests command-line switch to output the digests of the
10765 source files Tor was built with.
10766 - The "torify" script now uses torsocks where available.
10767 - The memarea code now uses a sentinel value at the end of each area
10768 to make sure nothing writes beyond the end of an area. This might
10769 help debug some conceivable causes of bug 930.
10770 - Time and memory units in the configuration file can now be set to
10771 fractional units. For example, "2.5 GB" is now a valid value for
10773 - Certain Tor clients (such as those behind check.torproject.org) may
10774 want to fetch the consensus in an extra early manner. To enable this
10775 a user may now set FetchDirInfoExtraEarly to 1. This also depends on
10776 setting FetchDirInfoEarly to 1. Previous behavior will stay the same
10777 as only certain clients who must have this information sooner should
10779 - Instead of adding the svn revision to the Tor version string, report
10780 the git commit (when we're building from a git checkout).
10783 - If any of the v3 certs we download are unparseable, we should
10784 actually notice the failure so we don't retry indefinitely. Bugfix
10785 on 0.2.0.x; reported by "rotator".
10786 - If the cached cert file is unparseable, warn but don't exit.
10787 - Fix possible segmentation fault on directory authorities. Bugfix on
10789 - When Tor fails to parse a descriptor of any kind, dump it to disk.
10790 Might help diagnosing bug 1051.
10792 o Deprecated and removed features:
10793 - The controller no longer accepts the old obsolete "addr-mappings/"
10794 or "unregistered-servers-" GETINFO values.
10795 - Hidden services no longer publish version 0 descriptors, and clients
10796 do not request or use version 0 descriptors. However, the old hidden
10797 service authorities still accept and serve version 0 descriptors
10798 when contacted by older hidden services/clients.
10799 - The EXTENDED_EVENTS and VERBOSE_NAMES controller features are now
10800 always on; using them is necessary for correct forward-compatible
10802 - Remove support for .noconnect style addresses. Nobody was using
10803 them, and they provided another avenue for detecting Tor users
10804 via application-level web tricks.
10806 o Packaging changes:
10807 - Upgrade Vidalia from 0.1.15 to 0.2.3 in the Windows and OS X
10808 installer bundles. See
10809 https://trac.vidalia-project.net/browser/vidalia/tags/vidalia-0.2.3/CHANGELOG
10810 for details of what's new in Vidalia 0.2.3.
10811 - Windows Vidalia Bundle: update Privoxy from 3.0.6 to 3.0.14-beta.
10812 - OS X Vidalia Bundle: move to Polipo 1.0.4 with Tor specific
10813 configuration file, rather than the old Privoxy.
10814 - OS X Vidalia Bundle: Vidalia, Tor, and Polipo are compiled as
10815 x86-only for better compatibility with OS X 10.6, aka Snow Leopard.
10816 - OS X Tor Expert Bundle: Tor is compiled as x86-only for
10817 better compatibility with OS X 10.6, aka Snow Leopard.
10818 - OS X Vidalia Bundle: The multi-package installer is now replaced
10819 by a simple drag and drop to the /Applications folder. This change
10820 occurred with the upgrade to Vidalia 0.2.3.
10823 Changes in version 0.2.1.19 - 2009-07-28
10824 Tor 0.2.1.19 fixes a major bug with accessing and providing hidden
10825 services on Tor 0.2.1.3-alpha through 0.2.1.18.
10828 - Make accessing hidden services on 0.2.1.x work right again.
10829 Bugfix on 0.2.1.3-alpha; workaround for bug 1038. Diagnosis and
10830 part of patch provided by "optimist".
10833 - When a relay/bridge is writing out its identity key fingerprint to
10834 the "fingerprint" file and to its logs, write it without spaces. Now
10835 it will look like the fingerprints in our bridges documentation,
10836 and confuse fewer users.
10839 - Relays no longer publish a new server descriptor if they change
10840 their MaxAdvertisedBandwidth config option but it doesn't end up
10841 changing their advertised bandwidth numbers. Bugfix on 0.2.0.28-rc;
10842 fixes bug 1026. Patch from Sebastian.
10843 - Avoid leaking memory every time we get a create cell but we have
10844 so many already queued that we refuse it. Bugfix on 0.2.0.19-alpha;
10845 fixes bug 1034. Reported by BarkerJr.
10848 Changes in version 0.2.1.18 - 2009-07-24
10849 Tor 0.2.1.18 lays the foundations for performance improvements,
10850 adds status events to help users diagnose bootstrap problems, adds
10851 optional authentication/authorization for hidden services, fixes a
10852 variety of potential anonymity problems, and includes a huge pile of
10853 other features and bug fixes.
10856 - Add LIBS=-lrt to Makefile.am so the Tor RPMs use a static libevent.
10859 Changes in version 0.2.1.17-rc - 2009-07-07
10860 Tor 0.2.1.17-rc marks the fourth -- and hopefully last -- release
10861 candidate for the 0.2.1.x series. It lays the groundwork for further
10862 client performance improvements, and also fixes a big bug with directory
10863 authorities that were causing them to assign Guard and Stable flags
10866 The Windows bundles also finally include the geoip database that we
10867 thought we'd been shipping since 0.2.0.x (oops), and the OS X bundles
10868 should actually install Torbutton rather than giving you a cryptic
10869 failure message (oops).
10872 - Clients now use the bandwidth values in the consensus, rather than
10873 the bandwidth values in each relay descriptor. This approach opens
10874 the door to more accurate bandwidth estimates once the directory
10875 authorities start doing active measurements. Implements more of
10879 - When Tor clients restart after 1-5 days, they discard all their
10880 cached descriptors as too old, but they still use the cached
10881 consensus document. This approach is good for robustness, but
10882 bad for performance: since they don't know any bandwidths, they
10883 end up choosing at random rather than weighting their choice by
10884 speed. Fixed by the above feature of putting bandwidths in the
10885 consensus. Bugfix on 0.2.0.x.
10886 - Directory authorities were neglecting to mark relays down in their
10887 internal histories if the relays fall off the routerlist without
10888 ever being found unreachable. So there were relays in the histories
10889 that haven't been seen for eight months, and are listed as being
10890 up for eight months. This wreaked havoc on the "median wfu"
10891 and "median mtbf" calculations, in turn making Guard and Stable
10892 flags very wrong, hurting network performance. Fixes bugs 696 and
10893 969. Bugfix on 0.2.0.6-alpha.
10896 - Serve the DirPortFrontPage page even when we have been approaching
10897 our quotas recently. Fixes bug 1013; bugfix on 0.2.1.8-alpha.
10898 - The control port would close the connection before flushing long
10899 replies, such as the network consensus, if a QUIT command was issued
10900 before the reply had completed. Now, the control port flushes all
10901 pending replies before closing the connection. Also fixed a spurious
10902 warning when a QUIT command is issued after a malformed or rejected
10903 AUTHENTICATE command, but before the connection was closed. Patch
10904 by Marcus Griep. Bugfix on 0.2.0.x; fixes bugs 1015 and 1016.
10905 - When we can't find an intro key for a v2 hidden service descriptor,
10906 fall back to the v0 hidden service descriptor and log a bug message.
10907 Workaround for bug 1024.
10908 - Fix a log message that did not respect the SafeLogging option.
10912 - If we're a relay and we change our IP address, be more verbose
10913 about the reason that made us change. Should help track down
10914 further bugs for relays on dynamic IP addresses.
10917 Changes in version 0.2.0.35 - 2009-06-24
10919 - Avoid crashing in the presence of certain malformed descriptors.
10920 Found by lark, and by automated fuzzing.
10921 - Fix an edge case where a malicious exit relay could convince a
10922 controller that the client's DNS question resolves to an internal IP
10923 address. Bug found and fixed by "optimist"; bugfix on 0.1.2.8-beta.
10926 - Finally fix the bug where dynamic-IP relays disappear when their
10927 IP address changes: directory mirrors were mistakenly telling
10928 them their old address if they asked via begin_dir, so they
10929 never got an accurate answer about their new address, so they
10930 just vanished after a day. For belt-and-suspenders, relays that
10931 don't set Address in their config now avoid using begin_dir for
10932 all direct connections. Should fix bugs 827, 883, and 900.
10933 - Fix a timing-dependent, allocator-dependent, DNS-related crash bug
10934 that would occur on some exit nodes when DNS failures and timeouts
10935 occurred in certain patterns. Fix for bug 957.
10938 - When starting with a cache over a few days old, do not leak
10939 memory for the obsolete router descriptors in it. Bugfix on
10940 0.2.0.33; fixes bug 672.
10941 - Hidden service clients didn't use a cached service descriptor that
10942 was older than 15 minutes, but wouldn't fetch a new one either,
10943 because there was already one in the cache. Now, fetch a v2
10944 descriptor unless the same descriptor was added to the cache within
10945 the last 15 minutes. Fixes bug 997; reported by Marcus Griep.
10948 Changes in version 0.2.1.16-rc - 2009-06-20
10949 Tor 0.2.1.16-rc speeds up performance for fast exit relays, and fixes
10950 a bunch of minor bugs.
10953 - Fix an edge case where a malicious exit relay could convince a
10954 controller that the client's DNS question resolves to an internal IP
10955 address. Bug found and fixed by "optimist"; bugfix on 0.1.2.8-beta.
10957 o Major performance improvements (on 0.2.0.x):
10958 - Disable and refactor some debugging checks that forced a linear scan
10959 over the whole server-side DNS cache. These accounted for over 50%
10960 of CPU time on a relatively busy exit node's gprof profile. Found
10962 - Disable some debugging checks that appeared in exit node profile
10966 - Update to the "June 3 2009" ip-to-country file.
10967 - Do not have tor-resolve automatically refuse all .onion addresses;
10968 if AutomapHostsOnResolve is set in your torrc, this will work fine.
10970 o Minor bugfixes (on 0.2.0.x):
10971 - Log correct error messages for DNS-related network errors on
10973 - Fix a race condition that could cause crashes or memory corruption
10974 when running as a server with a controller listening for log
10976 - Avoid crashing when we have a policy specified in a DirPolicy or
10977 SocksPolicy or ReachableAddresses option with ports set on it,
10978 and we re-load the policy. May fix bug 996.
10979 - Hidden service clients didn't use a cached service descriptor that
10980 was older than 15 minutes, but wouldn't fetch a new one either,
10981 because there was already one in the cache. Now, fetch a v2
10982 descriptor unless the same descriptor was added to the cache within
10983 the last 15 minutes. Fixes bug 997; reported by Marcus Griep.
10985 o Minor bugfixes (on 0.2.1.x):
10986 - Don't warn users about low port and hibernation mix when they
10987 provide a *ListenAddress directive to fix that. Bugfix on
10989 - When switching back and forth between bridge mode, do not start
10990 gathering GeoIP data until two hours have passed.
10991 - Do not complain that the user has requested an excluded node as
10992 an exit when the node is not really an exit. This could happen
10993 because the circuit was for testing, or an introduction point.
10997 Changes in version 0.2.1.15-rc - 2009-05-25
10998 Tor 0.2.1.15-rc marks the second release candidate for the 0.2.1.x
10999 series. It fixes a major bug on fast exit relays, as well as a variety
11000 of more minor bugs.
11002 o Major bugfixes (on 0.2.0.x):
11003 - Fix a timing-dependent, allocator-dependent, DNS-related crash bug
11004 that would occur on some exit nodes when DNS failures and timeouts
11005 occurred in certain patterns. Fix for bug 957.
11007 o Minor bugfixes (on 0.2.0.x):
11008 - Actually return -1 in the error case for read_bandwidth_usage().
11009 Harmless bug, since we currently don't care about the return value
11010 anywhere. Bugfix on 0.2.0.9-alpha.
11011 - Provide a more useful log message if bug 977 (related to buffer
11012 freelists) ever reappears, and do not crash right away.
11013 - Fix an assertion failure on 64-bit platforms when we allocated
11014 memory right up to the end of a memarea, then realigned the memory
11015 one step beyond the end. Fixes a possible cause of bug 930.
11016 - Protect the count of open sockets with a mutex, so we can't
11017 corrupt it when two threads are closing or opening sockets at once.
11018 Fix for bug 939. Bugfix on 0.2.0.1-alpha.
11019 - Don't allow a bridge to publish its router descriptor to a
11020 non-bridge directory authority. Fixes part of bug 932.
11021 - When we change to or from being a bridge, reset our counts of
11022 client usage by country. Fixes bug 932.
11023 - Fix a bug that made stream bandwidth get misreported to the
11025 - Stop using malloc_usable_size() to use more area than we had
11026 actually allocated: it was safe, but made valgrind really unhappy.
11027 - Fix a memory leak when v3 directory authorities load their keys
11028 and cert from disk. Bugfix on 0.2.0.1-alpha.
11030 o Minor bugfixes (on 0.2.1.x):
11031 - Fix use of freed memory when deciding to mark a non-addable
11032 descriptor as never-downloadable. Bugfix on 0.2.1.9-alpha.
11035 Changes in version 0.2.1.14-rc - 2009-04-12
11036 Tor 0.2.1.14-rc marks the first release candidate for the 0.2.1.x
11037 series. It begins fixing some major performance problems, and also
11038 finally addresses the bug that was causing relays on dynamic IP
11039 addresses to fall out of the directory.
11042 - Clients replace entry guards that were chosen more than a few months
11043 ago. This change should significantly improve client performance,
11044 especially once more people upgrade, since relays that have been
11045 a guard for a long time are currently overloaded.
11047 o Major bugfixes (on 0.2.0):
11048 - Finally fix the bug where dynamic-IP relays disappear when their
11049 IP address changes: directory mirrors were mistakenly telling
11050 them their old address if they asked via begin_dir, so they
11051 never got an accurate answer about their new address, so they
11052 just vanished after a day. For belt-and-suspenders, relays that
11053 don't set Address in their config now avoid using begin_dir for
11054 all direct connections. Should fix bugs 827, 883, and 900.
11055 - Relays were falling out of the networkstatus consensus for
11056 part of a day if they changed their local config but the
11057 authorities discarded their new descriptor as "not sufficiently
11058 different". Now directory authorities accept a descriptor as changed
11059 if bandwidthrate or bandwidthburst changed. Partial fix for bug 962;
11060 patch by Sebastian.
11061 - Avoid crashing in the presence of certain malformed descriptors.
11062 Found by lark, and by automated fuzzing.
11065 - When generating circuit events with verbose nicknames for
11066 controllers, try harder to look up nicknames for routers on a
11067 circuit. (Previously, we would look in the router descriptors we had
11068 for nicknames, but not in the consensus.) Partial fix for bug 941.
11069 - If the bridge config line doesn't specify a port, assume 443.
11070 This makes bridge lines a bit smaller and easier for users to
11072 - Raise the minimum bandwidth to be a relay from 20000 bytes to 20480
11073 bytes (aka 20KB/s), to match our documentation. Also update
11074 directory authorities so they always assign the Fast flag to relays
11075 with 20KB/s of capacity. Now people running relays won't suddenly
11076 find themselves not seeing any use, if the network gets faster
11078 - Update to the "April 3 2009" ip-to-country file.
11081 - Avoid trying to print raw memory to the logs when we decide to
11082 give up on downloading a given relay descriptor. Bugfix on
11084 - In tor-resolve, when the Tor client to use is specified by
11085 <hostname>:<port>, actually use the specified port rather than
11086 defaulting to 9050. Bugfix on 0.2.1.6-alpha.
11087 - Make directory usage recording work again. Bugfix on 0.2.1.6-alpha.
11088 - When starting with a cache over a few days old, do not leak
11089 memory for the obsolete router descriptors in it. Bugfix on
11091 - Avoid double-free on list of successfully uploaded hidden
11092 service discriptors. Fix for bug 948. Bugfix on 0.2.1.6-alpha.
11093 - Change memarea_strndup() implementation to work even when
11094 duplicating a string at the end of a page. This bug was
11095 harmless for now, but could have meant crashes later. Fix by
11096 lark. Bugfix on 0.2.1.1-alpha.
11097 - Limit uploaded directory documents to be 16M rather than 500K.
11098 The directory authorities were refusing v3 consensus votes from
11099 other authorities, since the votes are now 504K. Fixes bug 959;
11100 bugfix on 0.0.2pre17 (where we raised it from 50K to 500K ;).
11101 - Directory authorities should never send a 503 "busy" response to
11102 requests for votes or keys. Bugfix on 0.2.0.8-alpha; exposed by
11106 Changes in version 0.2.1.13-alpha - 2009-03-09
11107 Tor 0.2.1.13-alpha includes another big pile of minor bugfixes and
11108 cleanups. We're finally getting close to a release candidate.
11111 - Correctly update the list of which countries we exclude as
11112 exits, when the GeoIP file is loaded or reloaded. Diagnosed by
11113 lark. Bugfix on 0.2.1.6-alpha.
11115 o Minor bugfixes (on 0.2.0.x and earlier):
11116 - Automatically detect MacOSX versions earlier than 10.4.0, and
11117 disable kqueue from inside Tor when running with these versions.
11118 We previously did this from the startup script, but that was no
11119 help to people who didn't use the startup script. Resolves bug 863.
11120 - When we had picked an exit node for a connection, but marked it as
11121 "optional", and it turned out we had no onion key for the exit,
11122 stop wanting that exit and try again. This situation may not
11123 be possible now, but will probably become feasible with proposal
11124 158. Spotted by rovv. Fixes another case of bug 752.
11125 - Clients no longer cache certificates for authorities they do not
11126 recognize. Bugfix on 0.2.0.9-alpha.
11127 - When we can't transmit a DNS request due to a network error, retry
11128 it after a while, and eventually transmit a failing response to
11129 the RESOLVED cell. Bugfix on 0.1.2.5-alpha.
11130 - If the controller claimed responsibility for a stream, but that
11131 stream never finished making its connection, it would live
11132 forever in circuit_wait state. Now we close it after SocksTimeout
11133 seconds. Bugfix on 0.1.2.7-alpha; reported by Mike Perry.
11134 - Drop begin cells to a hidden service if they come from the middle
11135 of a circuit. Patch from lark.
11136 - When we erroneously receive two EXTEND cells for the same circuit
11137 ID on the same connection, drop the second. Patch from lark.
11138 - Fix a crash that occurs on exit nodes when a nameserver request
11139 timed out. Bugfix on 0.1.2.1-alpha; our CLEAR debugging code had
11140 been suppressing the bug since 0.1.2.10-alpha. Partial fix for
11142 - Do not assume that a stack-allocated character array will be
11143 64-bit aligned on platforms that demand that uint64_t access is
11144 aligned. Possible fix for bug 604.
11145 - Parse dates and IPv4 addresses in a locale- and libc-independent
11146 manner, to avoid platform-dependent behavior on malformed input.
11147 - Build correctly when configured to build outside the main source
11148 path. Patch from Michael Gold.
11149 - We were already rejecting relay begin cells with destination port
11150 of 0. Now also reject extend cells with destination port or address
11151 of 0. Suggested by lark.
11153 o Minor bugfixes (on 0.2.1.x):
11154 - Don't re-extend introduction circuits if we ran out of RELAY_EARLY
11155 cells. Bugfix on 0.2.1.3-alpha. Fixes more of bug 878.
11156 - If we're an exit node, scrub the IP address to which we are exiting
11157 in the logs. Bugfix on 0.2.1.8-alpha.
11160 - On Linux, use the prctl call to re-enable core dumps when the user
11162 - New controller event NEWCONSENSUS that lists the networkstatus
11163 lines for every recommended relay. Now controllers like Torflow
11164 can keep up-to-date on which relays they should be using.
11165 - Update to the "February 26 2009" ip-to-country file.
11168 Changes in version 0.2.0.34 - 2009-02-08
11169 Tor 0.2.0.34 features several more security-related fixes. You should
11170 upgrade, especially if you run an exit relay (remote crash) or a
11171 directory authority (remote infinite loop), or you're on an older
11172 (pre-XP) or not-recently-patched Windows (remote exploit).
11174 This release marks end-of-life for Tor 0.1.2.x. Those Tor versions
11175 have many known flaws, and nobody should be using them. You should
11176 upgrade. If you're using a Linux or BSD and its packages are obsolete,
11177 stop using those packages and upgrade anyway.
11180 - Fix an infinite-loop bug on handling corrupt votes under certain
11181 circumstances. Bugfix on 0.2.0.8-alpha.
11182 - Fix a temporary DoS vulnerability that could be performed by
11183 a directory mirror. Bugfix on 0.2.0.9-alpha; reported by lark.
11184 - Avoid a potential crash on exit nodes when processing malformed
11185 input. Remote DoS opportunity. Bugfix on 0.2.0.33.
11186 - Do not accept incomplete ipv4 addresses (like 192.168.0) as valid.
11187 Spec conformance issue. Bugfix on Tor 0.0.2pre27.
11190 - Fix compilation on systems where time_t is a 64-bit integer.
11191 Patch from Matthias Drochner.
11192 - Don't consider expiring already-closed client connections. Fixes
11193 bug 893. Bugfix on 0.0.2pre20.
11196 Changes in version 0.2.1.12-alpha - 2009-02-08
11197 Tor 0.2.1.12-alpha features several more security-related fixes. You
11198 should upgrade, especially if you run an exit relay (remote crash) or
11199 a directory authority (remote infinite loop), or you're on an older
11200 (pre-XP) or not-recently-patched Windows (remote exploit). It also
11201 includes a big pile of minor bugfixes and cleanups.
11204 - Fix an infinite-loop bug on handling corrupt votes under certain
11205 circumstances. Bugfix on 0.2.0.8-alpha.
11206 - Fix a temporary DoS vulnerability that could be performed by
11207 a directory mirror. Bugfix on 0.2.0.9-alpha; reported by lark.
11208 - Avoid a potential crash on exit nodes when processing malformed
11209 input. Remote DoS opportunity. Bugfix on 0.2.1.7-alpha.
11212 - Let controllers actually ask for the "clients_seen" event for
11213 getting usage summaries on bridge relays. Bugfix on 0.2.1.10-alpha;
11214 reported by Matt Edman.
11215 - Fix a compile warning on OSX Panther. Fixes bug 913; bugfix against
11217 - Fix a bug in address parsing that was preventing bridges or hidden
11218 service targets from being at IPv6 addresses.
11219 - Solve a bug that kept hardware crypto acceleration from getting
11220 enabled when accounting was turned on. Fixes bug 907. Bugfix on
11222 - Remove a bash-ism from configure.in to build properly on non-Linux
11223 platforms. Bugfix on 0.2.1.1-alpha.
11224 - Fix code so authorities _actually_ send back X-Descriptor-Not-New
11225 headers. Bugfix on 0.2.0.10-alpha.
11226 - Don't consider expiring already-closed client connections. Fixes
11227 bug 893. Bugfix on 0.0.2pre20.
11228 - Fix another interesting corner-case of bug 891 spotted by rovv:
11229 Previously, if two hosts had different amounts of clock drift, and
11230 one of them created a new connection with just the wrong timing,
11231 the other might decide to deprecate the new connection erroneously.
11232 Bugfix on 0.1.1.13-alpha.
11233 - Resolve a very rare crash bug that could occur when the user forced
11234 a nameserver reconfiguration during the middle of a nameserver
11235 probe. Fixes bug 526. Bugfix on 0.1.2.1-alpha.
11236 - Support changing value of ServerDNSRandomizeCase during SIGHUP.
11237 Bugfix on 0.2.1.7-alpha.
11238 - If we're using bridges and our network goes away, be more willing
11239 to forgive our bridges and try again when we get an application
11240 request. Bugfix on 0.2.0.x.
11243 - Support platforms where time_t is 64 bits long. (Congratulations,
11244 NetBSD!) Patch from Matthias Drochner.
11245 - Add a 'getinfo status/clients-seen' controller command, in case
11246 controllers want to hear clients_seen events but connect late.
11249 - Disable GCC's strict alias optimization by default, to avoid the
11250 likelihood of its introducing subtle bugs whenever our code violates
11251 the letter of C99's alias rules.
11254 Changes in version 0.2.0.33 - 2009-01-21
11255 Tor 0.2.0.33 fixes a variety of bugs that were making relays less
11256 useful to users. It also finally fixes a bug where a relay or client
11257 that's been off for many days would take a long time to bootstrap.
11259 This update also fixes an important security-related bug reported by
11260 Ilja van Sprundel. You should upgrade. (We'll send out more details
11261 about the bug once people have had some time to upgrade.)
11264 - Fix a heap-corruption bug that may be remotely triggerable on
11265 some platforms. Reported by Ilja van Sprundel.
11268 - When a stream at an exit relay is in state "resolving" or
11269 "connecting" and it receives an "end" relay cell, the exit relay
11270 would silently ignore the end cell and not close the stream. If
11271 the client never closes the circuit, then the exit relay never
11272 closes the TCP connection. Bug introduced in Tor 0.1.2.1-alpha;
11273 reported by "wood".
11274 - When sending CREATED cells back for a given circuit, use a 64-bit
11275 connection ID to find the right connection, rather than an addr:port
11276 combination. Now that we can have multiple OR connections between
11277 the same ORs, it is no longer possible to use addr:port to uniquely
11278 identify a connection.
11279 - Bridge relays that had DirPort set to 0 would stop fetching
11280 descriptors shortly after startup, and then briefly resume
11281 after a new bandwidth test and/or after publishing a new bridge
11282 descriptor. Bridge users that try to bootstrap from them would
11283 get a recent networkstatus but would get descriptors from up to
11284 18 hours earlier, meaning most of the descriptors were obsolete
11285 already. Reported by Tas; bugfix on 0.2.0.13-alpha.
11286 - Prevent bridge relays from serving their 'extrainfo' document
11287 to anybody who asks, now that extrainfo docs include potentially
11288 sensitive aggregated client geoip summaries. Bugfix on
11290 - If the cached networkstatus consensus is more than five days old,
11291 discard it rather than trying to use it. In theory it could be
11292 useful because it lists alternate directory mirrors, but in practice
11293 it just means we spend many minutes trying directory mirrors that
11294 are long gone from the network. Also discard router descriptors as
11295 we load them if they are more than five days old, since the onion
11296 key is probably wrong by now. Bugfix on 0.2.0.x. Fixes bug 887.
11299 - Do not mark smartlist_bsearch_idx() function as ATTR_PURE. This bug
11300 could make gcc generate non-functional binary search code. Bugfix
11302 - Build correctly on platforms without socklen_t.
11303 - Compile without warnings on solaris.
11304 - Avoid potential crash on internal error during signature collection.
11305 Fixes bug 864. Patch from rovv.
11306 - Correct handling of possible malformed authority signing key
11307 certificates with internal signature types. Fixes bug 880.
11308 Bugfix on 0.2.0.3-alpha.
11309 - Fix a hard-to-trigger resource leak when logging credential status.
11311 - When we can't initialize DNS because the network is down, do not
11312 automatically stop Tor from starting. Instead, we retry failed
11313 dns_init() every 10 minutes, and change the exit policy to reject
11314 *:* until one succeeds. Fixes bug 691.
11315 - Use 64 bits instead of 32 bits for connection identifiers used with
11316 the controller protocol, to greatly reduce risk of identifier reuse.
11317 - When we're choosing an exit node for a circuit, and we have
11318 no pending streams, choose a good general exit rather than one that
11319 supports "all the pending streams". Bugfix on 0.1.1.x. Fix by rovv.
11320 - Fix another case of assuming, when a specific exit is requested,
11321 that we know more than the user about what hosts it allows.
11322 Fixes one case of bug 752. Patch from rovv.
11323 - Clip the MaxCircuitDirtiness config option to a minimum of 10
11324 seconds. Warn the user if lower values are given in the
11325 configuration. Bugfix on 0.1.0.1-rc. Patch by Sebastian.
11326 - Clip the CircuitBuildTimeout to a minimum of 30 seconds. Warn the
11327 user if lower values are given in the configuration. Bugfix on
11328 0.1.1.17-rc. Patch by Sebastian.
11329 - Fix a memory leak when we decline to add a v2 rendezvous descriptor to
11330 the cache because we already had a v0 descriptor with the same ID.
11331 Bugfix on 0.2.0.18-alpha.
11332 - Fix a race condition when freeing keys shared between main thread
11333 and CPU workers that could result in a memory leak. Bugfix on
11334 0.1.0.1-rc. Fixes bug 889.
11335 - Send a valid END cell back when a client tries to connect to a
11336 nonexistent hidden service port. Bugfix on 0.1.2.15. Fixes bug
11337 840. Patch from rovv.
11338 - Check which hops rendezvous stream cells are associated with to
11339 prevent possible guess-the-streamid injection attacks from
11340 intermediate hops. Fixes another case of bug 446. Based on patch
11342 - If a broken client asks a non-exit router to connect somewhere,
11343 do not even do the DNS lookup before rejecting the connection.
11344 Fixes another case of bug 619. Patch from rovv.
11345 - When a relay gets a create cell it can't decrypt (e.g. because it's
11346 using the wrong onion key), we were dropping it and letting the
11347 client time out. Now actually answer with a destroy cell. Fixes
11348 bug 904. Bugfix on 0.0.2pre8.
11350 o Minor bugfixes (hidden services):
11351 - Do not throw away existing introduction points on SIGHUP. Bugfix on
11352 0.0.6pre1. Patch by Karsten. Fixes bug 874.
11355 - Report the case where all signatures in a detached set are rejected
11356 differently than the case where there is an error handling the
11358 - When we realize that another process has modified our cached
11359 descriptors, print out a more useful error message rather than
11360 triggering an assertion. Fixes bug 885. Patch from Karsten.
11361 - Implement the 0x20 hack to better resist DNS poisoning: set the
11362 case on outgoing DNS requests randomly, and reject responses that do
11363 not match the case correctly. This logic can be disabled with the
11364 ServerDNSRamdomizeCase setting, if you are using one of the 0.3%
11365 of servers that do not reliably preserve case in replies. See
11366 "Increased DNS Forgery Resistance through 0x20-Bit Encoding"
11368 - Check DNS replies for more matching fields to better resist DNS
11370 - Never use OpenSSL compression: it wastes RAM and CPU trying to
11371 compress cells, which are basically all encrypted, compressed, or
11375 Changes in version 0.2.1.11-alpha - 2009-01-20
11376 Tor 0.2.1.11-alpha finishes fixing the "if your Tor is off for a
11377 week it will take a long time to bootstrap again" bug. It also fixes
11378 an important security-related bug reported by Ilja van Sprundel. You
11379 should upgrade. (We'll send out more details about the bug once people
11380 have had some time to upgrade.)
11383 - Fix a heap-corruption bug that may be remotely triggerable on
11384 some platforms. Reported by Ilja van Sprundel.
11387 - Discard router descriptors as we load them if they are more than
11388 five days old. Otherwise if Tor is off for a long time and then
11389 starts with cached descriptors, it will try to use the onion
11390 keys in those obsolete descriptors when building circuits. Bugfix
11391 on 0.2.0.x. Fixes bug 887.
11394 - Try to make sure that the version of Libevent we're running with
11395 is binary-compatible with the one we built with. May address bug
11397 - Make setting ServerDNSRandomizeCase to 0 actually work. Bugfix
11398 for bug 905. Bugfix on 0.2.1.7-alpha.
11399 - Add a new --enable-local-appdata configuration switch to change
11400 the default location of the datadir on win32 from APPDATA to
11401 LOCAL_APPDATA. In the future, we should migrate to LOCAL_APPDATA
11402 entirely. Patch from coderman.
11405 - Make outbound DNS packets respect the OutboundBindAddress setting.
11406 Fixes the bug part of bug 798. Bugfix on 0.1.2.2-alpha.
11407 - When our circuit fails at the first hop (e.g. we get a destroy
11408 cell back), avoid using that OR connection anymore, and also
11409 tell all the one-hop directory requests waiting for it that they
11410 should fail. Bugfix on 0.2.1.3-alpha.
11411 - In the torify(1) manpage, mention that tsocks will leak your
11415 Changes in version 0.2.1.10-alpha - 2009-01-06
11416 Tor 0.2.1.10-alpha fixes two major bugs in bridge relays (one that
11417 would make the bridge relay not so useful if it had DirPort set to 0,
11418 and one that could let an attacker learn a little bit of information
11419 about the bridge's users), and a bug that would cause your Tor relay
11420 to ignore a circuit create request it can't decrypt (rather than reply
11421 with an error). It also fixes a wide variety of other bugs.
11424 - If the cached networkstatus consensus is more than five days old,
11425 discard it rather than trying to use it. In theory it could
11426 be useful because it lists alternate directory mirrors, but in
11427 practice it just means we spend many minutes trying directory
11428 mirrors that are long gone from the network. Helps bug 887 a bit;
11430 - Bridge relays that had DirPort set to 0 would stop fetching
11431 descriptors shortly after startup, and then briefly resume
11432 after a new bandwidth test and/or after publishing a new bridge
11433 descriptor. Bridge users that try to bootstrap from them would
11434 get a recent networkstatus but would get descriptors from up to
11435 18 hours earlier, meaning most of the descriptors were obsolete
11436 already. Reported by Tas; bugfix on 0.2.0.13-alpha.
11437 - Prevent bridge relays from serving their 'extrainfo' document
11438 to anybody who asks, now that extrainfo docs include potentially
11439 sensitive aggregated client geoip summaries. Bugfix on
11443 - New controller event "clients_seen" to report a geoip-based summary
11444 of which countries we've seen clients from recently. Now controllers
11445 like Vidalia can show bridge operators that they're actually making
11447 - Build correctly against versions of OpenSSL 0.9.8 or later built
11448 without support for deprecated functions.
11449 - Update to the "December 19 2008" ip-to-country file.
11451 o Minor bugfixes (on 0.2.0.x):
11452 - Authorities now vote for the Stable flag for any router whose
11453 weighted MTBF is at least 5 days, regardless of the mean MTBF.
11454 - Do not remove routers as too old if we do not have any consensus
11455 document. Bugfix on 0.2.0.7-alpha.
11456 - Do not accept incomplete ipv4 addresses (like 192.168.0) as valid.
11457 Spec conformance issue. Bugfix on Tor 0.0.2pre27.
11458 - When an exit relay resolves a stream address to a local IP address,
11459 do not just keep retrying that same exit relay over and
11460 over. Instead, just close the stream. Addresses bug 872. Bugfix
11461 on 0.2.0.32. Patch from rovv.
11462 - If a hidden service sends us an END cell, do not consider
11463 retrying the connection; just close it. Patch from rovv.
11464 - When we made bridge authorities stop serving bridge descriptors over
11465 unencrypted links, we also broke DirPort reachability testing for
11466 bridges. So bridges with a non-zero DirPort were printing spurious
11467 warns to their logs. Bugfix on 0.2.0.16-alpha. Fixes bug 709.
11468 - When a relay gets a create cell it can't decrypt (e.g. because it's
11469 using the wrong onion key), we were dropping it and letting the
11470 client time out. Now actually answer with a destroy cell. Fixes
11471 bug 904. Bugfix on 0.0.2pre8.
11472 - Squeeze 2-5% out of client performance (according to oprofile) by
11473 improving the implementation of some policy-manipulation functions.
11475 o Minor bugfixes (on 0.2.1.x):
11476 - Make get_interface_address() function work properly again; stop
11477 guessing the wrong parts of our address as our address.
11478 - Do not cannibalize a circuit if we're out of RELAY_EARLY cells to
11479 send on that circuit. Otherwise we might violate the proposal-110
11480 limit. Bugfix on 0.2.1.3-alpha. Partial fix for bug 878. Diagnosis
11482 - When we're sending non-EXTEND cells to the first hop in a circuit,
11483 for example to use an encrypted directory connection, we don't need
11484 to use RELAY_EARLY cells: the first hop knows what kind of cell
11485 it is, and nobody else can even see the cell type. Conserving
11486 RELAY_EARLY cells makes it easier to cannibalize circuits like
11488 - Stop logging nameserver addresses in reverse order.
11489 - If we are retrying a directory download slowly over and over, do
11490 not automatically give up after the 254th failure. Bugfix on
11492 - Resume reporting accurate "stream end" reasons to the local control
11493 port. They were lost in the changes for Proposal 148. Bugfix on
11496 o Deprecated and removed features:
11497 - The old "tor --version --version" command, which would print out
11498 the subversion "Id" of most of the source files, is now removed. It
11499 turned out to be less useful than we'd expected, and harder to
11502 o Code simplifications and refactoring:
11503 - Change our header file guard macros to be less likely to conflict
11504 with system headers. Adam Langley noticed that we were conflicting
11505 with log.h on Android.
11506 - Tool-assisted documentation cleanup. Nearly every function or
11507 static variable in Tor should have its own documentation now.
11510 Changes in version 0.2.1.9-alpha - 2008-12-25
11511 Tor 0.2.1.9-alpha fixes many more bugs, some of them security-related.
11513 o New directory authorities:
11514 - gabelmoo (the authority run by Karsten Loesing) now has a new
11518 - Never use a connection with a mismatched address to extend a
11519 circuit, unless that connection is canonical. A canonical
11520 connection is one whose address is authenticated by the router's
11521 identity key, either in a NETINFO cell or in a router descriptor.
11522 - Avoid a possible memory corruption bug when receiving hidden service
11523 descriptors. Bugfix on 0.2.1.6-alpha.
11526 - Fix a logic error that would automatically reject all but the first
11527 configured DNS server. Bugfix on 0.2.1.5-alpha. Possible fix for
11528 part of bug 813/868. Bug spotted by coderman.
11529 - When a stream at an exit relay is in state "resolving" or
11530 "connecting" and it receives an "end" relay cell, the exit relay
11531 would silently ignore the end cell and not close the stream. If
11532 the client never closes the circuit, then the exit relay never
11533 closes the TCP connection. Bug introduced in 0.1.2.1-alpha;
11534 reported by "wood".
11535 - When we can't initialize DNS because the network is down, do not
11536 automatically stop Tor from starting. Instead, retry failed
11537 dns_init() every 10 minutes, and change the exit policy to reject
11538 *:* until one succeeds. Fixes bug 691.
11541 - Give a better error message when an overzealous init script says
11542 "sudo -u username tor --user username". Makes Bug 882 easier for
11544 - When a directory authority gives us a new guess for our IP address,
11545 log which authority we used. Hopefully this will help us debug
11546 the recent complaints about bad IP address guesses.
11547 - Detect svn revision properly when we're using git-svn.
11548 - Try not to open more than one descriptor-downloading connection
11549 to an authority at once. This should reduce load on directory
11550 authorities. Fixes bug 366.
11551 - Add cross-certification to newly generated certificates, so that
11552 a signing key is enough information to look up a certificate.
11553 Partial implementation of proposal 157.
11554 - Start serving certificates by <identity digest, signing key digest>
11555 pairs. Partial implementation of proposal 157.
11556 - Clients now never report any stream end reason except 'MISC'.
11557 Implements proposal 148.
11558 - On platforms with a maximum syslog string length, truncate syslog
11559 messages to that length ourselves, rather than relying on the
11560 system to do it for us.
11561 - Optimize out calls to time(NULL) that occur for every IO operation,
11562 or for every cell. On systems where time() is a slow syscall,
11563 this fix will be slightly helpful.
11564 - Exit servers can now answer resolve requests for ip6.arpa addresses.
11565 - When we download a descriptor that we then immediately (as
11566 a directory authority) reject, do not retry downloading it right
11567 away. Should save some bandwidth on authorities. Fix for bug
11568 888. Patch by Sebastian Hahn.
11569 - When a download gets us zero good descriptors, do not notify
11570 Tor that new directory information has arrived.
11571 - Avoid some nasty corner cases in the logic for marking connections
11572 as too old or obsolete or noncanonical for circuits. Partial
11575 o Minor features (controller):
11576 - New CONSENSUS_ARRIVED event to note when a new consensus has
11577 been fetched and validated.
11578 - When we realize that another process has modified our cached
11579 descriptors file, print out a more useful error message rather
11580 than triggering an assertion. Fixes bug 885. Patch from Karsten.
11581 - Add an internal-use-only __ReloadTorrcOnSIGHUP option for
11582 controllers to prevent SIGHUP from reloading the
11583 configuration. Fixes bug 856.
11586 - Resume using the correct "REASON=" stream when telling the
11587 controller why we closed a stream. Bugfix in 0.2.1.1-alpha.
11588 - When a canonical connection appears later in our internal list
11589 than a noncanonical one for a given OR ID, always use the
11590 canonical one. Bugfix on 0.2.0.12-alpha. Fixes bug 805.
11592 - Clip the MaxCircuitDirtiness config option to a minimum of 10
11593 seconds. Warn the user if lower values are given in the
11594 configuration. Bugfix on 0.1.0.1-rc. Patch by Sebastian.
11595 - Clip the CircuitBuildTimeout to a minimum of 30 seconds. Warn the
11596 user if lower values are given in the configuration. Bugfix on
11597 0.1.1.17-rc. Patch by Sebastian.
11598 - Fix a race condition when freeing keys shared between main thread
11599 and CPU workers that could result in a memory leak. Bugfix on
11600 0.1.0.1-rc. Fixes bug 889.
11602 o Minor bugfixes (hidden services):
11603 - Do not throw away existing introduction points on SIGHUP (bugfix on
11604 0.0.6pre1); also, do not stall hidden services because we're
11605 throwing away introduction points; bugfix on 0.2.1.7-alpha. Spotted
11606 by John Brooks. Patch by Karsten. Fixes bug 874.
11607 - Fix a memory leak when we decline to add a v2 rendezvous
11608 descriptor to the cache because we already had a v0 descriptor
11609 with the same ID. Bugfix on 0.2.0.18-alpha.
11611 o Deprecated and removed features:
11612 - RedirectExits has been removed. It was deprecated since
11614 - Finally remove deprecated "EXTENDED_FORMAT" controller feature. It
11615 has been called EXTENDED_EVENTS since 0.1.2.4-alpha.
11616 - Cell pools are now always enabled; --disable-cell-pools is ignored.
11618 o Code simplifications and refactoring:
11619 - Rename the confusing or_is_obsolete field to the more appropriate
11620 is_bad_for_new_circs, and move it to or_connection_t where it
11622 - Move edge-only flags from connection_t to edge_connection_t: not
11623 only is this better coding, but on machines of plausible alignment,
11624 it should save 4-8 bytes per connection_t. "Every little bit helps."
11625 - Rename ServerDNSAllowBrokenResolvConf to ServerDNSAllowBrokenConfig
11626 for consistency; keep old option working for backward compatibility.
11627 - Simplify the code for finding connections to use for a circuit.
11630 Changes in version 0.2.1.8-alpha - 2008-12-08
11631 Tor 0.2.1.8-alpha fixes some crash bugs in earlier alpha releases,
11632 builds better on unusual platforms like Solaris and old OS X, and
11633 fixes a variety of other issues.
11636 - New DirPortFrontPage option that takes an html file and publishes
11637 it as "/" on the DirPort. Now relay operators can provide a
11638 disclaimer without needing to set up a separate webserver. There's
11639 a sample disclaimer in contrib/tor-exit-notice.html.
11642 - When the client is choosing entry guards, now it selects at most
11643 one guard from a given relay family. Otherwise we could end up with
11644 all of our entry points into the network run by the same operator.
11645 Suggested by Camilo Viecco. Fix on 0.1.1.11-alpha.
11648 - Fix a DOS opportunity during the voting signature collection process
11649 at directory authorities. Spotted by rovv. Bugfix on 0.2.0.x.
11650 - Fix a possible segfault when establishing an exit connection. Bugfix
11654 - Get file locking working on win32. Bugfix on 0.2.1.6-alpha. Fixes
11656 - Made Tor a little less aggressive about deleting expired
11657 certificates. Partial fix for bug 854.
11658 - Stop doing unaligned memory access that generated bus errors on
11659 sparc64. Bugfix on 0.2.0.10-alpha. Fix for bug 862.
11660 - Fix a crash bug when changing EntryNodes from the controller. Bugfix
11661 on 0.2.1.6-alpha. Fix for bug 867. Patched by Sebastian.
11662 - Make USR2 log-level switch take effect immediately. Bugfix on
11664 - If one win32 nameserver fails to get added, continue adding the
11665 rest, and don't automatically fail.
11666 - Use fcntl() for locking when flock() is not available. Should fix
11667 compilation on Solaris. Should fix Bug 873. Bugfix on 0.2.1.6-alpha.
11668 - Do not mark smartlist_bsearch_idx() function as ATTR_PURE. This bug
11669 could make gcc generate non-functional binary search code. Bugfix
11671 - Build correctly on platforms without socklen_t.
11672 - Avoid potential crash on internal error during signature collection.
11673 Fixes bug 864. Patch from rovv.
11674 - Do not use C's stdio library for writing to log files. This will
11675 improve logging performance by a minute amount, and will stop
11676 leaking fds when our disk is full. Fixes bug 861.
11677 - Stop erroneous use of O_APPEND in cases where we did not in fact
11678 want to re-seek to the end of a file before every last write().
11679 - Correct handling of possible malformed authority signing key
11680 certificates with internal signature types. Fixes bug 880. Bugfix
11682 - Fix a hard-to-trigger resource leak when logging credential status.
11686 - Directory mirrors no longer fetch the v1 directory or
11687 running-routers files. They are obsolete, and nobody asks for them
11688 anymore. This is the first step to making v1 authorities obsolete.
11690 o Minor features (controller):
11691 - Return circuit purposes in response to GETINFO circuit-status. Fixes
11695 Changes in version 0.2.0.32 - 2008-11-20
11696 Tor 0.2.0.32 fixes a major security problem in Debian and Ubuntu
11697 packages (and maybe other packages) noticed by Theo de Raadt, fixes
11698 a smaller security flaw that might allow an attacker to access local
11699 services, further improves hidden service performance, and fixes a
11700 variety of other issues.
11703 - The "User" and "Group" config options did not clear the
11704 supplementary group entries for the Tor process. The "User" option
11705 is now more robust, and we now set the groups to the specified
11706 user's primary group. The "Group" option is now ignored. For more
11707 detailed logging on credential switching, set CREDENTIAL_LOG_LEVEL
11708 in common/compat.c to LOG_NOTICE or higher. Patch by Jacob Appelbaum
11709 and Steven Murdoch. Bugfix on 0.0.2pre14. Fixes bug 848 and 857.
11710 - The "ClientDNSRejectInternalAddresses" config option wasn't being
11711 consistently obeyed: if an exit relay refuses a stream because its
11712 exit policy doesn't allow it, we would remember what IP address
11713 the relay said the destination address resolves to, even if it's
11714 an internal IP address. Bugfix on 0.2.0.7-alpha; patch by rovv.
11717 - Fix a DOS opportunity during the voting signature collection process
11718 at directory authorities. Spotted by rovv. Bugfix on 0.2.0.x.
11720 o Major bugfixes (hidden services):
11721 - When fetching v0 and v2 rendezvous service descriptors in parallel,
11722 we were failing the whole hidden service request when the v0
11723 descriptor fetch fails, even if the v2 fetch is still pending and
11724 might succeed. Similarly, if the last v2 fetch fails, we were
11725 failing the whole hidden service request even if a v0 fetch is
11726 still pending. Fixes bug 814. Bugfix on 0.2.0.10-alpha.
11727 - When extending a circuit to a hidden service directory to upload a
11728 rendezvous descriptor using a BEGIN_DIR cell, almost 1/6 of all
11729 requests failed, because the router descriptor has not been
11730 downloaded yet. In these cases, do not attempt to upload the
11731 rendezvous descriptor, but wait until the router descriptor is
11732 downloaded and retry. Likewise, do not attempt to fetch a rendezvous
11733 descriptor from a hidden service directory for which the router
11734 descriptor has not yet been downloaded. Fixes bug 767. Bugfix
11738 - Fix several infrequent memory leaks spotted by Coverity.
11739 - When testing for libevent functions, set the LDFLAGS variable
11740 correctly. Found by Riastradh.
11741 - Avoid a bug where the FastFirstHopPK 0 option would keep Tor from
11742 bootstrapping with tunneled directory connections. Bugfix on
11743 0.1.2.5-alpha. Fixes bug 797. Found by Erwin Lam.
11744 - When asked to connect to A.B.exit:80, if we don't know the IP for A
11745 and we know that server B rejects most-but-not all connections to
11746 port 80, we would previously reject the connection. Now, we assume
11747 the user knows what they were asking for. Fixes bug 752. Bugfix
11748 on 0.0.9rc5. Diagnosed by BarkerJr.
11749 - If we overrun our per-second write limits a little, count this as
11750 having used up our write allocation for the second, and choke
11751 outgoing directory writes. Previously, we had only counted this when
11752 we had met our limits precisely. Fixes bug 824. Patch from by rovv.
11753 Bugfix on 0.2.0.x (??).
11754 - Remove the old v2 directory authority 'lefkada' from the default
11755 list. It has been gone for many months.
11756 - Stop doing unaligned memory access that generated bus errors on
11757 sparc64. Bugfix on 0.2.0.10-alpha. Fixes bug 862.
11758 - Make USR2 log-level switch take effect immediately. Bugfix on
11761 o Minor bugfixes (controller):
11762 - Make DNS resolved events into "CLOSED", not "FAILED". Bugfix on
11763 0.1.2.5-alpha. Fix by Robert Hogan. Resolves bug 807.
11766 Changes in version 0.2.1.7-alpha - 2008-11-08
11767 Tor 0.2.1.7-alpha fixes a major security problem in Debian and Ubuntu
11768 packages (and maybe other packages) noticed by Theo de Raadt, fixes
11769 a smaller security flaw that might allow an attacker to access local
11770 services, adds better defense against DNS poisoning attacks on exit
11771 relays, further improves hidden service performance, and fixes a
11772 variety of other issues.
11775 - The "ClientDNSRejectInternalAddresses" config option wasn't being
11776 consistently obeyed: if an exit relay refuses a stream because its
11777 exit policy doesn't allow it, we would remember what IP address
11778 the relay said the destination address resolves to, even if it's
11779 an internal IP address. Bugfix on 0.2.0.7-alpha; patch by rovv.
11780 - The "User" and "Group" config options did not clear the
11781 supplementary group entries for the Tor process. The "User" option
11782 is now more robust, and we now set the groups to the specified
11783 user's primary group. The "Group" option is now ignored. For more
11784 detailed logging on credential switching, set CREDENTIAL_LOG_LEVEL
11785 in common/compat.c to LOG_NOTICE or higher. Patch by Jacob Appelbaum
11786 and Steven Murdoch. Bugfix on 0.0.2pre14. Fixes bug 848.
11787 - Do not use or believe expired v3 authority certificates. Patch
11788 from Karsten. Bugfix in 0.2.0.x. Fixes bug 851.
11791 - Now NodeFamily and MyFamily config options allow spaces in
11792 identity fingerprints, so it's easier to paste them in.
11793 Suggested by Lucky Green.
11794 - Implement the 0x20 hack to better resist DNS poisoning: set the
11795 case on outgoing DNS requests randomly, and reject responses that do
11796 not match the case correctly. This logic can be disabled with the
11797 ServerDNSRandomizeCase setting, if you are using one of the 0.3%
11798 of servers that do not reliably preserve case in replies. See
11799 "Increased DNS Forgery Resistance through 0x20-Bit Encoding"
11801 - Preserve case in replies to DNSPort requests in order to support
11802 the 0x20 hack for resisting DNS poisoning attacks.
11804 o Hidden service performance improvements:
11805 - When the client launches an introduction circuit, retry with a
11806 new circuit after 30 seconds rather than 60 seconds.
11807 - Launch a second client-side introduction circuit in parallel
11808 after a delay of 15 seconds (based on work by Christian Wilms).
11809 - Hidden services start out building five intro circuits rather
11810 than three, and when the first three finish they publish a service
11811 descriptor using those. Now we publish our service descriptor much
11812 faster after restart.
11815 - Minor fix in the warning messages when you're having problems
11816 bootstrapping; also, be more forgiving of bootstrap problems when
11817 we're still making incremental progress on a given bootstrap phase.
11818 - When we're choosing an exit node for a circuit, and we have
11819 no pending streams, choose a good general exit rather than one that
11820 supports "all the pending streams". Bugfix on 0.1.1.x. Fix by rovv.
11821 - Send a valid END cell back when a client tries to connect to a
11822 nonexistent hidden service port. Bugfix on 0.1.2.15. Fixes bug
11823 840. Patch from rovv.
11824 - If a broken client asks a non-exit router to connect somewhere,
11825 do not even do the DNS lookup before rejecting the connection.
11826 Fixes another case of bug 619. Patch from rovv.
11827 - Fix another case of assuming, when a specific exit is requested,
11828 that we know more than the user about what hosts it allows.
11829 Fixes another case of bug 752. Patch from rovv.
11830 - Check which hops rendezvous stream cells are associated with to
11831 prevent possible guess-the-streamid injection attacks from
11832 intermediate hops. Fixes another case of bug 446. Based on patch
11834 - Avoid using a negative right-shift when comparing 32-bit
11835 addresses. Possible fix for bug 845 and bug 811.
11836 - Make the assert_circuit_ok() function work correctly on circuits that
11837 have already been marked for close.
11838 - Fix read-off-the-end-of-string error in unit tests when decoding
11839 introduction points.
11840 - Fix uninitialized size field for memory area allocation: may improve
11841 memory performance during directory parsing.
11842 - Treat duplicate certificate fetches as failures, so that we do
11843 not try to re-fetch an expired certificate over and over and over.
11844 - Do not say we're fetching a certificate when we'll in fact skip it
11845 because of a pending download.
11848 Changes in version 0.2.1.6-alpha - 2008-09-30
11849 Tor 0.2.1.6-alpha further improves performance and robustness of
11850 hidden services, starts work on supporting per-country relay selection,
11851 and fixes a variety of smaller issues.
11854 - Implement proposal 121: make it possible to build hidden services
11855 that only certain clients are allowed to connect to. This is
11856 enforced at several points, so that unauthorized clients are unable
11857 to send INTRODUCE cells to the service, or even (depending on the
11858 type of authentication) to learn introduction points. This feature
11859 raises the bar for certain kinds of active attacks against hidden
11860 services. Code by Karsten Loesing.
11861 - Relays now store and serve v2 hidden service descriptors by default,
11862 i.e., the new default value for HidServDirectoryV2 is 1. This is
11863 the last step in proposal 114, which aims to make hidden service
11864 lookups more reliable.
11865 - Start work to allow node restrictions to include country codes. The
11866 syntax to exclude nodes in a country with country code XX is
11867 "ExcludeNodes {XX}". Patch from Robert Hogan. It still needs some
11868 refinement to decide what config options should take priority if
11869 you ask to both use a particular node and exclude it.
11870 - Allow ExitNodes list to include IP ranges and country codes, just
11871 like the Exclude*Nodes lists. Patch from Robert Hogan.
11874 - Fix a bug when parsing ports in tor_addr_port_parse() that caused
11875 Tor to fail to start if you had it configured to use a bridge
11876 relay. Fixes bug 809. Bugfix on 0.2.1.5-alpha.
11877 - When extending a circuit to a hidden service directory to upload a
11878 rendezvous descriptor using a BEGIN_DIR cell, almost 1/6 of all
11879 requests failed, because the router descriptor had not been
11880 downloaded yet. In these cases, we now wait until the router
11881 descriptor is downloaded, and then retry. Likewise, clients
11882 now skip over a hidden service directory if they don't yet have
11883 its router descriptor, rather than futilely requesting it and
11884 putting mysterious complaints in the logs. Fixes bug 767. Bugfix
11886 - When fetching v0 and v2 rendezvous service descriptors in parallel,
11887 we were failing the whole hidden service request when the v0
11888 descriptor fetch fails, even if the v2 fetch is still pending and
11889 might succeed. Similarly, if the last v2 fetch fails, we were
11890 failing the whole hidden service request even if a v0 fetch is
11891 still pending. Fixes bug 814. Bugfix on 0.2.0.10-alpha.
11892 - DNS replies need to have names matching their requests, but
11893 these names should be in the questions section, not necessarily
11894 in the answers section. Fixes bug 823. Bugfix on 0.2.1.5-alpha.
11897 - Update to the "September 1 2008" ip-to-country file.
11898 - Allow ports 465 and 587 in the default exit policy again. We had
11899 rejected them in 0.1.0.15, because back in 2005 they were commonly
11900 misconfigured and ended up as spam targets. We hear they are better
11901 locked down these days.
11902 - Use a lockfile to make sure that two Tor processes are not
11903 simultaneously running with the same datadir.
11904 - Serve the latest v3 networkstatus consensus via the control
11905 port. Use "getinfo dir/status-vote/current/consensus" to fetch it.
11906 - Better logging about stability/reliability calculations on directory
11908 - Drop the requirement to have an open dir port for storing and
11909 serving v2 hidden service descriptors.
11910 - Directory authorities now serve a /tor/dbg-stability.txt URL to
11911 help debug WFU and MTBF calculations.
11912 - Implement most of Proposal 152: allow specialized servers to permit
11913 single-hop circuits, and clients to use those servers to build
11914 single-hop circuits when using a specialized controller. Patch
11915 from Josh Albrecht. Resolves feature request 768.
11916 - Add a -p option to tor-resolve for specifying the SOCKS port: some
11917 people find host:port too confusing.
11918 - Make TrackHostExit mappings expire a while after their last use, not
11919 after their creation. Patch from Robert Hogan.
11920 - Provide circuit purposes along with circuit events to the controller.
11923 - Fix compile on OpenBSD 4.4-current. Bugfix on 0.2.1.5-alpha.
11925 - Fixed some memory leaks -- some quite frequent, some almost
11926 impossible to trigger -- based on results from Coverity.
11927 - When testing for libevent functions, set the LDFLAGS variable
11928 correctly. Found by Riastradh.
11929 - Fix an assertion bug in parsing policy-related options; possible fix
11931 - Catch and report a few more bootstrapping failure cases when Tor
11932 fails to establish a TCP connection. Cleanup on 0.2.1.x.
11933 - Avoid a bug where the FastFirstHopPK 0 option would keep Tor from
11934 bootstrapping with tunneled directory connections. Bugfix on
11935 0.1.2.5-alpha. Fixes bug 797. Found by Erwin Lam.
11936 - When asked to connect to A.B.exit:80, if we don't know the IP for A
11937 and we know that server B rejects most-but-not all connections to
11938 port 80, we would previously reject the connection. Now, we assume
11939 the user knows what they were asking for. Fixes bug 752. Bugfix
11940 on 0.0.9rc5. Diagnosed by BarkerJr.
11941 - If we are not using BEGIN_DIR cells, don't attempt to contact hidden
11942 service directories if they have no advertised dir port. Bugfix
11944 - If we overrun our per-second write limits a little, count this as
11945 having used up our write allocation for the second, and choke
11946 outgoing directory writes. Previously, we had only counted this when
11947 we had met our limits precisely. Fixes bug 824. Patch by rovv.
11948 Bugfix on 0.2.0.x (??).
11949 - Avoid a "0 divided by 0" calculation when calculating router uptime
11950 at directory authorities. Bugfix on 0.2.0.8-alpha.
11951 - Make DNS resolved controller events into "CLOSED", not
11952 "FAILED". Bugfix on 0.1.2.5-alpha. Fix by Robert Hogan. Resolves
11954 - Fix a bug where an unreachable relay would establish enough
11955 reachability testing circuits to do a bandwidth test -- if
11956 we already have a connection to the middle hop of the testing
11957 circuit, then it could establish the last hop by using the existing
11958 connection. Bugfix on 0.1.2.2-alpha, exposed when we made testing
11959 circuits no longer use entry guards in 0.2.1.3-alpha.
11960 - If we have correct permissions on $datadir, we complain to stdout
11961 and fail to start. But dangerous permissions on
11962 $datadir/cached-status/ would cause us to open a log and complain
11963 there. Now complain to stdout and fail to start in both cases. Fixes
11964 bug 820, reported by seeess.
11965 - Remove the old v2 directory authority 'lefkada' from the default
11966 list. It has been gone for many months.
11968 o Code simplifications and refactoring:
11969 - Revise the connection_new functions so that a more typesafe variant
11970 exists. This will work better with Coverity, and let us find any
11971 actual mistakes we're making here.
11972 - Refactor unit testing logic so that dmalloc can be used sensibly
11973 with unit tests to check for memory leaks.
11974 - Move all hidden-service related fields from connection and circuit
11975 structure to substructures: this way they won't eat so much memory.
11978 Changes in version 0.2.0.31 - 2008-09-03
11979 Tor 0.2.0.31 addresses two potential anonymity issues, starts to fix
11980 a big bug we're seeing where in rare cases traffic from one Tor stream
11981 gets mixed into another stream, and fixes a variety of smaller issues.
11984 - Make sure that two circuits can never exist on the same connection
11985 with the same circuit ID, even if one is marked for close. This
11986 is conceivably a bugfix for bug 779. Bugfix on 0.1.0.4-rc.
11987 - Relays now reject risky extend cells: if the extend cell includes
11988 a digest of all zeroes, or asks to extend back to the relay that
11989 sent the extend cell, tear down the circuit. Ideas suggested
11991 - If not enough of our entry guards are available so we add a new
11992 one, we might use the new one even if it overlapped with the
11993 current circuit's exit relay (or its family). Anonymity bugfix
11994 pointed out by rovv.
11997 - Recover 3-7 bytes that were wasted per memory chunk. Fixes bug
11998 794; bug spotted by rovv. Bugfix on 0.2.0.1-alpha.
11999 - Correctly detect the presence of the linux/netfilter_ipv4.h header
12000 when building against recent kernels. Bugfix on 0.1.2.1-alpha.
12001 - Pick size of default geoip filename string correctly on windows.
12002 Fixes bug 806. Bugfix on 0.2.0.30.
12003 - Make the autoconf script accept the obsolete --with-ssl-dir
12004 option as an alias for the actually-working --with-openssl-dir
12005 option. Fix the help documentation to recommend --with-openssl-dir.
12006 Based on a patch by "Dave". Bugfix on 0.2.0.1-alpha.
12007 - When using the TransPort option on OpenBSD, and using the User
12008 option to change UID and drop privileges, make sure to open
12009 /dev/pf before dropping privileges. Fixes bug 782. Patch from
12010 Christopher Davis. Bugfix on 0.1.2.1-alpha.
12011 - Try to attach connections immediately upon receiving a RENDEZVOUS2
12012 or RENDEZVOUS_ESTABLISHED cell. This can save a second or two
12013 on the client side when connecting to a hidden service. Bugfix
12014 on 0.0.6pre1. Found and fixed by Christian Wilms; resolves bug 743.
12015 - When closing an application-side connection because its circuit is
12016 getting torn down, generate the stream event correctly. Bugfix on
12017 0.1.2.x. Anonymous patch.
12020 Changes in version 0.2.1.5-alpha - 2008-08-31
12021 Tor 0.2.1.5-alpha moves us closer to handling IPv6 destinations, puts
12022 in a lot of the infrastructure for adding authorization to hidden
12023 services, lays the groundwork for having clients read their load
12024 balancing information out of the networkstatus consensus rather than
12025 the individual router descriptors, addresses two potential anonymity
12026 issues, and fixes a variety of smaller issues.
12029 - Convert many internal address representations to optionally hold
12031 - Generate and accept IPv6 addresses in many protocol elements.
12032 - Make resolver code handle nameservers located at ipv6 addresses.
12033 - Begin implementation of proposal 121 ("Client authorization for
12034 hidden services"): configure hidden services with client
12035 authorization, publish descriptors for them, and configure
12036 authorization data for hidden services at clients. The next
12037 step is to actually access hidden services that perform client
12039 - More progress toward proposal 141: Network status consensus
12040 documents and votes now contain bandwidth information for each
12041 router and a summary of that router's exit policy. Eventually this
12042 will be used by clients so that they do not have to download every
12043 known descriptor before building circuits.
12045 o Major bugfixes (on 0.2.0.x and before):
12046 - When sending CREATED cells back for a given circuit, use a 64-bit
12047 connection ID to find the right connection, rather than an addr:port
12048 combination. Now that we can have multiple OR connections between
12049 the same ORs, it is no longer possible to use addr:port to uniquely
12050 identify a connection.
12051 - Relays now reject risky extend cells: if the extend cell includes
12052 a digest of all zeroes, or asks to extend back to the relay that
12053 sent the extend cell, tear down the circuit. Ideas suggested
12055 - If not enough of our entry guards are available so we add a new
12056 one, we might use the new one even if it overlapped with the
12057 current circuit's exit relay (or its family). Anonymity bugfix
12058 pointed out by rovv.
12061 - Recover 3-7 bytes that were wasted per memory chunk. Fixes bug
12062 794; bug spotted by rovv. Bugfix on 0.2.0.1-alpha.
12063 - When using the TransPort option on OpenBSD, and using the User
12064 option to change UID and drop privileges, make sure to open /dev/pf
12065 before dropping privileges. Fixes bug 782. Patch from Christopher
12066 Davis. Bugfix on 0.1.2.1-alpha.
12067 - Correctly detect the presence of the linux/netfilter_ipv4.h header
12068 when building against recent kernels. Bugfix on 0.1.2.1-alpha.
12069 - Add a missing safe_str() call for a debug log message.
12070 - Use 64 bits instead of 32 bits for connection identifiers used with
12071 the controller protocol, to greatly reduce risk of identifier reuse.
12072 - Make the autoconf script accept the obsolete --with-ssl-dir
12073 option as an alias for the actually-working --with-openssl-dir
12074 option. Fix the help documentation to recommend --with-openssl-dir.
12075 Based on a patch by "Dave". Bugfix on 0.2.0.1-alpha.
12078 - Rate-limit too-many-sockets messages: when they happen, they happen
12079 a lot. Resolves bug 748.
12080 - Resist DNS poisoning a little better by making sure that names in
12081 answer sections match.
12082 - Print the SOCKS5 error message string as well as the error code
12083 when a tor-resolve request fails. Patch from Jacob.
12086 Changes in version 0.2.1.4-alpha - 2008-08-04
12087 Tor 0.2.1.4-alpha fixes a pair of crash bugs in 0.2.1.3-alpha.
12090 - The address part of exit policies was not correctly written
12091 to router descriptors. This generated router descriptors that failed
12092 their self-checks. Noticed by phobos, fixed by Karsten. Bugfix
12094 - Tor triggered a false assert when extending a circuit to a relay
12095 but we already have a connection open to that relay. Noticed by
12096 phobos, fixed by Karsten. Bugfix on 0.2.1.3-alpha.
12099 - Fix a hidden service logging bug: in some edge cases, the router
12100 descriptor of a previously picked introduction point becomes
12101 obsolete and we need to give up on it rather than continually
12102 complaining that it has become obsolete. Observed by xiando. Bugfix
12105 o Removed features:
12106 - Take out the TestVia config option, since it was a workaround for
12107 a bug that was fixed in Tor 0.1.1.21.
12110 Changes in version 0.2.1.3-alpha - 2008-08-03
12111 Tor 0.2.1.3-alpha implements most of the pieces to prevent
12112 infinite-length circuit attacks (see proposal 110); fixes a bug that
12113 might cause exit relays to corrupt streams they send back; allows
12114 address patterns (e.g. 255.128.0.0/16) to appear in ExcludeNodes and
12115 ExcludeExitNodes config options; and fixes a big pile of bugs.
12117 o Bootstrapping bugfixes (on 0.2.1.x-alpha):
12118 - Send a bootstrap problem "warn" event on the first problem if the
12119 reason is NO_ROUTE (that is, our network is down).
12122 - Implement most of proposal 110: The first K cells to be sent
12123 along a circuit are marked as special "early" cells; only K "early"
12124 cells will be allowed. Once this code is universal, we can block
12125 certain kinds of DOS attack by requiring that EXTEND commands must
12126 be sent using an "early" cell.
12129 - Try to attach connections immediately upon receiving a RENDEZVOUS2
12130 or RENDEZVOUS_ESTABLISHED cell. This can save a second or two
12131 on the client side when connecting to a hidden service. Bugfix
12132 on 0.0.6pre1. Found and fixed by Christian Wilms; resolves bug 743.
12133 - Ensure that two circuits can never exist on the same connection
12134 with the same circuit ID, even if one is marked for close. This
12135 is conceivably a bugfix for bug 779; fixes a bug on 0.1.0.4-rc.
12138 - When relays do their initial bandwidth measurement, don't limit
12139 to just our entry guards for the test circuits. Otherwise we tend
12140 to have multiple test circuits going through a single entry guard,
12141 which makes our bandwidth test less accurate. Fixes part of bug 654;
12142 patch contributed by Josh Albrecht.
12143 - Add an ExcludeExitNodes option so users can list a set of nodes
12144 that should be be excluded from the exit node position, but
12145 allowed elsewhere. Implements proposal 151.
12146 - Allow address patterns (e.g., 255.128.0.0/16) to appear in
12147 ExcludeNodes and ExcludeExitNodes lists.
12148 - Change the implementation of ExcludeNodes and ExcludeExitNodes to
12149 be more efficient. Formerly it was quadratic in the number of
12150 servers; now it should be linear. Fixes bug 509.
12151 - Save 16-22 bytes per open circuit by moving the n_addr, n_port,
12152 and n_conn_id_digest fields into a separate structure that's
12153 only needed when the circuit has not yet attached to an n_conn.
12156 - Change the contrib/tor.logrotate script so it makes the new
12157 logs as "_tor:_tor" rather than the default, which is generally
12158 "root:wheel". Fixes bug 676, reported by Serge Koksharov.
12159 - Stop using __attribute__((nonnull)) with GCC: it can give us useful
12160 warnings (occasionally), but it can also cause the compiler to
12161 eliminate error-checking code. Suggested by Peter Gutmann.
12162 - When a hidden service is giving up on an introduction point candidate
12163 that was not included in the last published rendezvous descriptor,
12164 don't reschedule publication of the next descriptor. Fixes bug 763.
12166 - Mark RendNodes, RendExcludeNodes, HiddenServiceNodes, and
12167 HiddenServiceExcludeNodes as obsolete: they never worked properly,
12168 and nobody claims to be using them. Fixes bug 754. Bugfix on
12169 0.1.0.1-rc. Patch from Christian Wilms.
12170 - Fix a small alignment and memory-wasting bug on buffer chunks.
12173 o Minor bugfixes (controller):
12174 - When closing an application-side connection because its circuit
12175 is getting torn down, generate the stream event correctly.
12176 Bugfix on 0.1.2.x. Anonymous patch.
12178 o Removed features:
12179 - Remove all backward-compatibility code to support relays running
12180 versions of Tor so old that they no longer work at all on the
12184 Changes in version 0.2.0.30 - 2008-07-15
12186 - Stop using __attribute__((nonnull)) with GCC: it can give us useful
12187 warnings (occasionally), but it can also cause the compiler to
12188 eliminate error-checking code. Suggested by Peter Gutmann.
12191 Changes in version 0.2.0.29-rc - 2008-07-08
12192 Tor 0.2.0.29-rc fixes two big bugs with using bridges, fixes more
12193 hidden-service performance bugs, and fixes a bunch of smaller bugs.
12196 - If you have more than one bridge but don't know their keys,
12197 you would only launch a request for the descriptor of the first one
12198 on your list. (Tor considered launching requests for the others, but
12199 found that it already had a connection on the way for $0000...0000
12200 so it didn't open another.) Bugfix on 0.2.0.x.
12201 - If you have more than one bridge but don't know their keys, and the
12202 connection to one of the bridges failed, you would cancel all
12203 pending bridge connections. (After all, they all have the same
12204 digest.) Bugfix on 0.2.0.x.
12205 - When a hidden service was trying to establish an introduction point,
12206 and Tor had built circuits preemptively for such purposes, we
12207 were ignoring all the preemptive circuits and launching a new one
12208 instead. Bugfix on 0.2.0.14-alpha.
12209 - When a hidden service was trying to establish an introduction point,
12210 and Tor *did* manage to reuse one of the preemptively built
12211 circuits, it didn't correctly remember which one it used,
12212 so it asked for another one soon after, until there were no
12213 more preemptive circuits, at which point it launched one from
12214 scratch. Bugfix on 0.0.9.x.
12215 - Make directory servers include the X-Your-Address-Is: http header in
12216 their responses even for begin_dir conns. Now clients who only
12217 ever use begin_dir connections still have a way to learn their IP
12218 address. Fixes bug 737; bugfix on 0.2.0.22-rc. Reported by goldy.
12221 - Fix a macro/CPP interaction that was confusing some compilers:
12222 some GCCs don't like #if/#endif pairs inside macro arguments.
12224 - Fix macro collision between OpenSSL 0.9.8h and Windows headers.
12225 Fixes bug 704; fix from Steven Murdoch.
12226 - When opening /dev/null in finish_daemonize(), do not pass the
12227 O_CREAT flag. Fortify was complaining, and correctly so. Fixes
12228 bug 742; fix from Michael Scherer. Bugfix on 0.0.2pre19.
12229 - Correctly detect transparent proxy support on Linux hosts that
12230 require in.h to be included before netfilter_ipv4.h. Patch
12232 - Disallow session resumption attempts during the renegotiation
12233 stage of the v2 handshake protocol. Clients should never be trying
12234 session resumption at this point, but apparently some did, in
12235 ways that caused the handshake to fail. Bugfix on 0.2.0.20-rc. Bug
12236 found by Geoff Goodell.
12239 Changes in version 0.2.1.2-alpha - 2008-06-20
12240 Tor 0.2.1.2-alpha includes a new "TestingTorNetwork" config option to
12241 make it easier to set up your own private Tor network; fixes several
12242 big bugs with using more than one bridge relay; fixes a big bug with
12243 offering hidden services quickly after Tor starts; and uses a better
12244 API for reporting potential bootstrapping problems to the controller.
12247 - New TestingTorNetwork config option to allow adjustment of
12248 previously constant values that, while reasonable, could slow
12249 bootstrapping. Implements proposal 135. Patch from Karsten.
12252 - If you have more than one bridge but don't know their digests,
12253 you would only learn a request for the descriptor of the first one
12254 on your list. (Tor considered launching requests for the others, but
12255 found that it already had a connection on the way for $0000...0000
12256 so it didn't open another.) Bugfix on 0.2.0.x.
12257 - If you have more than one bridge but don't know their digests,
12258 and the connection to one of the bridges failed, you would cancel
12259 all pending bridge connections. (After all, they all have the
12260 same digest.) Bugfix on 0.2.0.x.
12261 - When establishing a hidden service, introduction points that
12262 originate from cannibalized circuits are completely ignored and not
12263 included in rendezvous service descriptors. This might be another
12264 reason for delay in making a hidden service available. Bugfix
12265 from long ago (0.0.9.x?)
12268 - Allow OpenSSL to use dynamic locks if it wants.
12269 - When building a consensus, do not include routers that are down.
12270 This will cut down 30% to 40% on consensus size. Implements
12272 - In directory authorities' approved-routers files, allow
12273 fingerprints with or without space.
12274 - Add a "GETINFO /status/bootstrap-phase" controller option, so the
12275 controller can query our current bootstrap state in case it attaches
12276 partway through and wants to catch up.
12277 - Send an initial "Starting" bootstrap status event, so we have a
12278 state to start out in.
12281 - Asking for a conditional consensus at .../consensus/<fingerprints>
12282 would crash a dirserver if it did not already have a
12283 consensus. Bugfix on 0.2.1.1-alpha.
12284 - Clean up some macro/CPP interactions: some GCC versions don't like
12285 #if/#endif pairs inside macro arguments. Fixes bug 707. Bugfix on
12288 o Bootstrapping bugfixes (on 0.2.1.1-alpha):
12289 - Directory authorities shouldn't complain about bootstrapping
12290 problems just because they do a lot of reachability testing and
12291 some of the connection attempts fail.
12292 - Start sending "count" and "recommendation" key/value pairs in
12293 bootstrap problem status events, so the controller can hear about
12294 problems even before Tor decides they're worth reporting for sure.
12295 - If you're using bridges, generate "bootstrap problem" warnings
12296 as soon as you run out of working bridges, rather than waiting
12297 for ten failures -- which will never happen if you have less than
12299 - If we close our OR connection because there's been a circuit
12300 pending on it for too long, we were telling our bootstrap status
12301 events "REASON=NONE". Now tell them "REASON=TIMEOUT".
12304 Changes in version 0.2.1.1-alpha - 2008-06-13
12305 Tor 0.2.1.1-alpha fixes a lot of memory fragmentation problems that
12306 were making the Tor process bloat especially on Linux; makes our TLS
12307 handshake blend in better; sends "bootstrap phase" status events to
12308 the controller, so it can keep the user informed of progress (and
12309 problems) fetching directory information and establishing circuits;
12310 and adds a variety of smaller features.
12313 - More work on making our TLS handshake blend in: modify the list
12314 of ciphers advertised by OpenSSL in client mode to even more
12315 closely resemble a common web browser. We cheat a little so that
12316 we can advertise ciphers that the locally installed OpenSSL doesn't
12318 - Start sending "bootstrap phase" status events to the controller,
12319 so it can keep the user informed of progress fetching directory
12320 information and establishing circuits. Also inform the controller
12321 if we think we're stuck at a particular bootstrap phase. Implements
12323 - Resume using OpenSSL's RAND_poll() for better (and more portable)
12324 cross-platform entropy collection again. We used to use it, then
12325 stopped using it because of a bug that could crash systems that
12326 called RAND_poll when they had a lot of fds open. It looks like the
12327 bug got fixed in late 2006. Our new behavior is to call RAND_poll()
12328 at startup, and to call RAND_poll() when we reseed later only if
12329 we have a non-buggy OpenSSL version.
12332 - When we choose to abandon a new entry guard because we think our
12333 older ones might be better, close any circuits pending on that
12334 new entry guard connection. This fix should make us recover much
12335 faster when our network is down and then comes back. Bugfix on
12336 0.1.2.8-beta; found by lodger.
12338 o Memory fixes and improvements:
12339 - Add a malloc_good_size implementation to OpenBSD_malloc_linux.c,
12340 to avoid unused RAM in buffer chunks and memory pools.
12341 - Speed up parsing and cut down on memory fragmentation by using
12342 stack-style allocations for parsing directory objects. Previously,
12343 this accounted for over 40% of allocations from within Tor's code
12344 on a typical directory cache.
12345 - Use a Bloom filter rather than a digest-based set to track which
12346 descriptors we need to keep around when we're cleaning out old
12347 router descriptors. This speeds up the computation significantly,
12348 and may reduce fragmentation.
12349 - Reduce the default smartlist size from 32 to 16; it turns out that
12350 most smartlists hold around 8-12 elements tops.
12351 - Make dumpstats() log the fullness and size of openssl-internal
12353 - If the user has applied the experimental SSL_MODE_RELEASE_BUFFERS
12354 patch to their OpenSSL, turn it on to save memory on servers. This
12355 patch will (with any luck) get included in a mainline distribution
12357 - Never use OpenSSL compression: it wastes RAM and CPU trying to
12358 compress cells, which are basically all encrypted, compressed,
12362 - Stop reloading the router list from disk for no reason when we
12363 run out of reachable directory mirrors. Once upon a time reloading
12364 it would set the 'is_running' flag back to 1 for them. It hasn't
12365 done that for a long time.
12366 - In very rare situations new hidden service descriptors were
12367 published earlier than 30 seconds after the last change to the
12368 service. (We currently think that a hidden service descriptor
12369 that's been stable for 30 seconds is worth publishing.)
12372 - Allow separate log levels to be configured for different logging
12373 domains. For example, this allows one to log all notices, warnings,
12374 or errors, plus all memory management messages of level debug or
12375 higher, with: Log [MM] debug-err [*] notice-err file /var/log/tor.
12376 - Add a couple of extra warnings to --enable-gcc-warnings for GCC 4.3,
12377 and stop using a warning that had become unfixably verbose under
12379 - New --hush command-line option similar to --quiet. While --quiet
12380 disables all logging to the console on startup, --hush limits the
12381 output to messages of warning and error severity.
12382 - Servers support a new URL scheme for consensus downloads that
12383 allows the client to specify which authorities are trusted.
12384 The server then only sends the consensus if the client will trust
12385 it. Otherwise a 404 error is sent back. Clients use this
12386 new scheme when the server supports it (meaning it's running
12387 0.2.1.1-alpha or later). Implements proposal 134.
12388 - New configure/torrc options (--enable-geoip-stats,
12389 DirRecordUsageByCountry) to record how many IPs we've served
12390 directory info to in each country code, how many status documents
12391 total we've sent to each country code, and what share of the total
12392 directory requests we should expect to see.
12393 - Use the TLS1 hostname extension to more closely resemble browser
12395 - Lots of new unit tests.
12396 - Add a macro to implement the common pattern of iterating through
12397 two parallel lists in lockstep.
12400 Changes in version 0.2.0.28-rc - 2008-06-13
12401 Tor 0.2.0.28-rc fixes an anonymity-related bug, fixes a hidden-service
12402 performance bug, and fixes a bunch of smaller bugs.
12405 - Fix a bug where, when we were choosing the 'end stream reason' to
12406 put in our relay end cell that we send to the exit relay, Tor
12407 clients on Windows were sometimes sending the wrong 'reason'. The
12408 anonymity problem is that exit relays may be able to guess whether
12409 the client is running Windows, thus helping partition the anonymity
12410 set. Down the road we should stop sending reasons to exit relays,
12411 or otherwise prevent future versions of this bug.
12414 - While setting up a hidden service, some valid introduction circuits
12415 were overlooked and abandoned. This might be the reason for
12416 the long delay in making a hidden service available. Bugfix on
12420 - Update to the "June 9 2008" ip-to-country file.
12421 - Run 'make test' as part of 'make dist', so we stop releasing so
12422 many development snapshots that fail their unit tests.
12425 - When we're checking if we have enough dir info for each relay
12426 to begin establishing circuits, make sure that we actually have
12427 the descriptor listed in the consensus, not just any descriptor.
12429 - Bridge relays no longer print "xx=0" in their extrainfo document
12430 for every single country code in the geoip db. Bugfix on
12432 - Only warn when we fail to load the geoip file if we were planning to
12433 include geoip stats in our extrainfo document. Bugfix on 0.2.0.27-rc.
12434 - If we change our MaxAdvertisedBandwidth and then reload torrc,
12435 Tor won't realize it should publish a new relay descriptor. Fixes
12436 bug 688, reported by mfr. Bugfix on 0.1.2.x.
12437 - When we haven't had any application requests lately, don't bother
12438 logging that we have expired a bunch of descriptors. Bugfix
12440 - Make relay cells written on a connection count as non-padding when
12441 tracking how long a connection has been in use. Bugfix on
12442 0.2.0.1-alpha. Spotted by lodger.
12443 - Fix unit tests in 0.2.0.27-rc.
12444 - Fix compile on Windows.
12447 Changes in version 0.2.0.27-rc - 2008-06-03
12448 Tor 0.2.0.27-rc adds a few features we left out of the earlier
12449 release candidates. In particular, we now include an IP-to-country
12450 GeoIP database, so controllers can easily look up what country a
12451 given relay is in, and so bridge relays can give us some sanitized
12452 summaries about which countries are making use of bridges. (See proposal
12453 126-geoip-fetching.txt for details.)
12456 - Include an IP-to-country GeoIP file in the tarball, so bridge
12457 relays can report sanitized summaries of the usage they're seeing.
12460 - Add a "PURPOSE=" argument to "STREAM NEW" events, as suggested by
12461 Robert Hogan. Fixes the first part of bug 681.
12462 - Make bridge authorities never serve extrainfo docs.
12463 - Add support to detect Libevent versions in the 1.4.x series
12465 - Fix build on gcc 4.3 with --enable-gcc-warnings set.
12466 - Include a new contrib/tor-exit-notice.html file that exit relay
12467 operators can put on their website to help reduce abuse queries.
12470 - When tunneling an encrypted directory connection, and its first
12471 circuit fails, do not leave it unattached and ask the controller
12472 to deal. Fixes the second part of bug 681.
12473 - Make bridge authorities correctly expire old extrainfo documents
12477 Changes in version 0.2.0.26-rc - 2008-05-13
12478 Tor 0.2.0.26-rc fixes a major security vulnerability caused by a bug
12479 in Debian's OpenSSL packages. All users running any 0.2.0.x version
12480 should upgrade, whether they're running Debian or not.
12482 o Major security fixes:
12483 - Use new V3 directory authority keys on the tor26, gabelmoo, and
12484 moria1 V3 directory authorities. The old keys were generated with
12485 a vulnerable version of Debian's OpenSSL package, and must be
12486 considered compromised. Other authorities' keys were not generated
12487 with an affected version of OpenSSL.
12490 - List authority signatures as "unrecognized" based on DirServer
12491 lines, not on cert cache. Bugfix on 0.2.0.x.
12494 - Add a new V3AuthUseLegacyKey option to make it easier for
12495 authorities to change their identity keys if they have to.
12498 Changes in version 0.2.0.25-rc - 2008-04-23
12499 Tor 0.2.0.25-rc makes Tor work again on OS X and certain BSDs.
12502 - Remember to initialize threading before initializing logging.
12503 Otherwise, many BSD-family implementations will crash hard on
12504 startup. Fixes bug 671. Bugfix on 0.2.0.24-rc.
12507 - Authorities correctly free policies on bad servers on
12508 exit. Fixes bug 672. Bugfix on 0.2.0.x.
12511 Changes in version 0.2.0.24-rc - 2008-04-22
12512 Tor 0.2.0.24-rc adds dizum (run by Alex de Joode) as the new sixth
12513 v3 directory authority, makes relays with dynamic IP addresses and no
12514 DirPort notice more quickly when their IP address changes, fixes a few
12515 rare crashes and memory leaks, and fixes a few other miscellaneous bugs.
12517 o New directory authorities:
12518 - Take lefkada out of the list of v3 directory authorities, since
12519 it has been down for months.
12520 - Set up dizum (run by Alex de Joode) as the new sixth v3 directory
12524 - Detect address changes more quickly on non-directory mirror
12525 relays. Bugfix on 0.2.0.18-alpha; fixes bug 652.
12527 o Minor features (security):
12528 - Reject requests for reverse-dns lookup of names that are in
12529 a private address space. Patch from lodger.
12530 - Non-exit relays no longer allow DNS requests. Fixes bug 619. Patch
12533 o Minor bugfixes (crashes):
12534 - Avoid a rare assert that can trigger when Tor doesn't have much
12535 directory information yet and it tries to fetch a v2 hidden
12536 service descriptor. Fixes bug 651, reported by nwf.
12537 - Initialize log mutex before initializing dmalloc. Otherwise,
12538 running with dmalloc would crash. Bugfix on 0.2.0.x-alpha.
12539 - Use recursive pthread mutexes in order to avoid deadlock when
12540 logging debug-level messages to a controller. Bug spotted by nwf,
12541 bugfix on 0.2.0.16-alpha.
12543 o Minor bugfixes (resource management):
12544 - Keep address policies from leaking memory: start their refcount
12545 at 1, not 2. Bugfix on 0.2.0.16-alpha.
12546 - Free authority certificates on exit, so they don't look like memory
12547 leaks. Bugfix on 0.2.0.19-alpha.
12548 - Free static hashtables for policy maps and for TLS connections on
12549 shutdown, so they don't look like memory leaks. Bugfix on 0.2.0.x.
12550 - Avoid allocating extra space when computing consensuses on 64-bit
12551 platforms. Bug spotted by aakova.
12553 o Minor bugfixes (misc):
12554 - Do not read the configuration file when we've only been told to
12555 generate a password hash. Fixes bug 643. Bugfix on 0.0.9pre5. Fix
12556 based on patch from Sebastian Hahn.
12557 - Exit relays that are used as a client can now reach themselves
12558 using the .exit notation, rather than just launching an infinite
12559 pile of circuits. Fixes bug 641. Reported by Sebastian Hahn.
12560 - When attempting to open a logfile fails, tell us why.
12561 - Fix a dumb bug that was preventing us from knowing that we should
12562 preemptively build circuits to handle expected directory requests.
12563 Fixes bug 660. Bugfix on 0.1.2.x.
12564 - Warn less verbosely about clock skew from netinfo cells from
12565 untrusted sources. Fixes bug 663.
12566 - Make controller stream events for DNS requests more consistent,
12567 by adding "new stream" events for DNS requests, and removing
12568 spurious "stream closed" events" for cached reverse resolves.
12569 Patch from mwenge. Fixes bug 646.
12570 - Correctly notify one-hop connections when a circuit build has
12571 failed. Possible fix for bug 669. Found by lodger.
12574 Changes in version 0.2.0.23-rc - 2008-03-24
12575 Tor 0.2.0.23-rc is the fourth release candidate for the 0.2.0 series. It
12576 makes bootstrapping faster if the first directory mirror you contact
12577 is down. The bundles also include the new Vidalia 0.1.2 release.
12580 - When a tunneled directory request is made to a directory server
12581 that's down, notice after 30 seconds rather than 120 seconds. Also,
12582 fail any begindir streams that are pending on it, so they can
12583 retry elsewhere. This was causing multi-minute delays on bootstrap.
12586 Changes in version 0.2.0.22-rc - 2008-03-18
12587 Tor 0.2.0.22-rc is the third release candidate for the 0.2.0 series. It
12588 enables encrypted directory connections by default for non-relays, fixes
12589 some broken TLS behavior we added in 0.2.0.20-rc, and resolves many
12590 other bugs. The bundles also include Vidalia 0.1.1 and Torbutton 1.1.17.
12593 - Enable encrypted directory connections by default for non-relays,
12594 so censor tools that block Tor directory connections based on their
12595 plaintext patterns will no longer work. This means Tor works in
12596 certain censored countries by default again.
12599 - Make sure servers always request certificates from clients during
12600 TLS renegotiation. Reported by lodger; bugfix on 0.2.0.20-rc.
12601 - Do not enter a CPU-eating loop when a connection is closed in
12602 the middle of client-side TLS renegotiation. Fixes bug 622. Bug
12603 diagnosed by lodger; bugfix on 0.2.0.20-rc.
12604 - Fix assertion failure that could occur when a blocked circuit
12605 became unblocked, and it had pending client DNS requests. Bugfix
12606 on 0.2.0.1-alpha. Fixes bug 632.
12608 o Minor bugfixes (on 0.1.2.x):
12609 - Generate "STATUS_SERVER" events rather than misspelled
12610 "STATUS_SEVER" events. Caught by mwenge.
12611 - When counting the number of bytes written on a TLS connection,
12612 look at the BIO actually used for writing to the network, not
12613 at the BIO used (sometimes) to buffer data for the network.
12614 Looking at different BIOs could result in write counts on the
12615 order of ULONG_MAX. Fixes bug 614.
12616 - On Windows, correctly detect errors when listing the contents of
12617 a directory. Fix from lodger.
12619 o Minor bugfixes (on 0.2.0.x):
12620 - Downgrade "sslv3 alert handshake failure" message to INFO.
12621 - If we set RelayBandwidthRate and RelayBandwidthBurst very high but
12622 left BandwidthRate and BandwidthBurst at the default, we would be
12623 silently limited by those defaults. Now raise them to match the
12624 RelayBandwidth* values.
12625 - Fix the SVK version detection logic to work correctly on a branch.
12626 - Make --enable-openbsd-malloc work correctly on Linux with alpha
12627 CPUs. Fixes bug 625.
12628 - Logging functions now check that the passed severity is sane.
12629 - Use proper log levels in the testsuite call of
12630 get_interface_address6().
12631 - When using a nonstandard malloc, do not use the platform values for
12632 HAVE_MALLOC_GOOD_SIZE or HAVE_MALLOC_USABLE_SIZE.
12633 - Make the openbsd malloc code use 8k pages on alpha CPUs and
12635 - Detect mismatched page sizes when using --enable-openbsd-malloc.
12636 - Avoid double-marked-for-close warning when certain kinds of invalid
12637 .in-addr.arpa addresses are passed to the DNSPort. Part of a fix
12638 for bug 617. Bugfix on 0.2.0.1-alpha.
12639 - Make sure that the "NULL-means-reject *:*" convention is followed by
12640 all the policy manipulation functions, avoiding some possible crash
12641 bugs. Bug found by lodger. Bugfix on 0.2.0.16-alpha.
12642 - Fix the implementation of ClientDNSRejectInternalAddresses so that it
12643 actually works, and doesn't warn about every single reverse lookup.
12644 Fixes the other part of bug 617. Bugfix on 0.2.0.1-alpha.
12647 - Only log guard node status when guard node status has changed.
12648 - Downgrade the 3 most common "INFO" messages to "DEBUG". This will
12649 make "INFO" 75% less verbose.
12652 Changes in version 0.2.0.21-rc - 2008-03-02
12653 Tor 0.2.0.21-rc is the second release candidate for the 0.2.0 series. It
12654 makes Tor work well with Vidalia again, fixes a rare assert bug,
12655 and fixes a pair of more minor bugs. The bundles also include Vidalia
12656 0.1.0 and Torbutton 1.1.16.
12659 - The control port should declare that it requires password auth
12660 when HashedControlSessionPassword is set too. Patch from Matt Edman;
12661 bugfix on 0.2.0.20-rc. Fixes bug 615.
12662 - Downgrade assert in connection_buckets_decrement() to a log message.
12663 This may help us solve bug 614, and in any case will make its
12664 symptoms less severe. Bugfix on 0.2.0.20-rc. Reported by fredzupy.
12665 - We were sometimes miscounting the number of bytes read from the
12666 network, causing our rate limiting to not be followed exactly.
12667 Bugfix on 0.2.0.16-alpha. Reported by lodger.
12670 - Fix compilation with OpenSSL 0.9.8 and 0.9.8a. All other supported
12671 OpenSSL versions should have been working fine. Diagnosis and patch
12672 from lodger, Karsten Loesing, and Sebastian Hahn. Fixes bug 616.
12673 Bugfix on 0.2.0.20-rc.
12676 Changes in version 0.2.0.20-rc - 2008-02-24
12677 Tor 0.2.0.20-rc is the first release candidate for the 0.2.0 series. It
12678 makes more progress towards normalizing Tor's TLS handshake, makes
12679 hidden services work better again, helps relays bootstrap if they don't
12680 know their IP address, adds optional support for linking in openbsd's
12681 allocator or tcmalloc, allows really fast relays to scale past 15000
12682 sockets, and fixes a bunch of minor bugs reported by Veracode.
12685 - Enable the revised TLS handshake based on the one designed by
12686 Steven Murdoch in proposal 124, as revised in proposal 130. It
12687 includes version negotiation for OR connections as described in
12688 proposal 105. The new handshake is meant to be harder for censors
12689 to fingerprint, and it adds the ability to detect certain kinds of
12690 man-in-the-middle traffic analysis attacks. The version negotiation
12691 feature will allow us to improve Tor's link protocol more safely
12693 - Choose which bridge to use proportional to its advertised bandwidth,
12694 rather than uniformly at random. This should speed up Tor for
12695 bridge users. Also do this for people who set StrictEntryNodes.
12696 - When a TrackHostExits-chosen exit fails too many times in a row,
12697 stop using it. Bugfix on 0.1.2.x; fixes bug 437.
12700 - Resolved problems with (re-)fetching hidden service descriptors.
12701 Patch from Karsten Loesing; fixes problems with 0.2.0.18-alpha
12702 and 0.2.0.19-alpha.
12703 - If we only ever used Tor for hidden service lookups or posts, we
12704 would stop building circuits and start refusing connections after
12705 24 hours, since we falsely believed that Tor was dormant. Reported
12706 by nwf; bugfix on 0.1.2.x.
12707 - Servers that don't know their own IP address should go to the
12708 authorities for their first directory fetch, even if their DirPort
12709 is off or if they don't know they're reachable yet. This will help
12710 them bootstrap better. Bugfix on 0.2.0.18-alpha; fixes bug 609.
12711 - When counting the number of open sockets, count not only the number
12712 of sockets we have received from the socket() call, but also
12713 the number we've gotten from accept() and socketpair(). This bug
12714 made us fail to count all sockets that we were using for incoming
12715 connections. Bugfix on 0.2.0.x.
12716 - Fix code used to find strings within buffers, when those strings
12717 are not in the first chunk of the buffer. Bugfix on 0.2.0.x.
12718 - Fix potential segfault when parsing HTTP headers. Bugfix on 0.2.0.x.
12719 - Add a new __HashedControlSessionPassword option for controllers
12720 to use for one-off session password hashes that shouldn't get
12721 saved to disk by SAVECONF --- Vidalia users were accumulating a
12722 pile of HashedControlPassword lines in their torrc files, one for
12723 each time they had restarted Tor and then clicked Save. Make Tor
12724 automatically convert "HashedControlPassword" to this new option but
12725 only when it's given on the command line. Partial fix for bug 586.
12727 o Minor features (performance):
12728 - Tune parameters for cell pool allocation to minimize amount of
12730 - Add OpenBSD malloc code from phk as an optional malloc
12731 replacement on Linux: some glibc libraries do very poorly
12732 with Tor's memory allocation patterns. Pass
12733 --enable-openbsd-malloc to get the replacement malloc code.
12734 - Add a --with-tcmalloc option to the configure script to link
12735 against tcmalloc (if present). Does not yet search for
12736 non-system include paths.
12737 - Stop imposing an arbitrary maximum on the number of file descriptors
12738 used for busy servers. Bug reported by Olaf Selke; patch from
12741 o Minor features (other):
12742 - When SafeLogging is disabled, log addresses along with all TLS
12744 - When building with --enable-gcc-warnings, check for whether Apple's
12745 warning "-Wshorten-64-to-32" is available.
12746 - Add a --passphrase-fd argument to the tor-gencert command for
12749 o Minor bugfixes (memory leaks and code problems):
12750 - We were leaking a file descriptor if Tor started with a zero-length
12751 cached-descriptors file. Patch by freddy77; bugfix on 0.1.2.
12752 - Detect size overflow in zlib code. Reported by Justin Ferguson and
12754 - We were comparing the raw BridgePassword entry with a base64'ed
12755 version of it, when handling a "/tor/networkstatus-bridges"
12756 directory request. Now compare correctly. Noticed by Veracode.
12757 - Recover from bad tracked-since value in MTBF-history file.
12758 Should fix bug 537.
12759 - Alter the code that tries to recover from unhandled write
12760 errors, to not try to flush onto a socket that's given us
12761 unhandled errors. Bugfix on 0.1.2.x.
12762 - Make Unix controlsockets work correctly on OpenBSD. Patch from
12763 tup. Bugfix on 0.2.0.3-alpha.
12765 o Minor bugfixes (other):
12766 - If we have an extra-info document for our server, always make
12767 it available on the control port, even if we haven't gotten
12768 a copy of it from an authority yet. Patch from mwenge.
12769 - Log the correct memory chunk sizes for empty RAM chunks in mempool.c.
12770 - Directory mirrors no longer include a guess at the client's IP
12771 address if the connection appears to be coming from the same /24
12772 network; it was producing too many wrong guesses.
12773 - Make the new hidden service code respect the SafeLogging setting.
12774 Bugfix on 0.2.0.x. Patch from Karsten.
12775 - When starting as an authority, do not overwrite all certificates
12776 cached from other authorities. Bugfix on 0.2.0.x. Fixes bug 606.
12777 - If we're trying to flush the last bytes on a connection (for
12778 example, when answering a directory request), reset the
12779 time-to-give-up timeout every time we manage to write something
12780 on the socket. Bugfix on 0.1.2.x.
12781 - Change the behavior of "getinfo status/good-server-descriptor"
12782 so it doesn't return failure when any authority disappears.
12783 - Even though the man page said that "TrackHostExits ." should
12784 work, nobody had ever implemented it. Bugfix on 0.1.0.x.
12785 - Report TLS "zero return" case as a "clean close" and "IO error"
12786 as a "close". Stop calling closes "unexpected closes": existing
12787 Tors don't use SSL_close(), so having a connection close without
12788 the TLS shutdown handshake is hardly unexpected.
12789 - Send NAMESERVER_STATUS messages for a single failed nameserver
12792 o Code simplifications and refactoring:
12793 - Remove the tor_strpartition function: its logic was confused,
12794 and it was only used for one thing that could be implemented far
12798 Changes in version 0.2.0.19-alpha - 2008-02-09
12799 Tor 0.2.0.19-alpha makes more progress towards normalizing Tor's TLS
12800 handshake, makes path selection for relays more secure and IP address
12801 guessing more robust, and generally fixes a lot of bugs in preparation
12802 for calling the 0.2.0 branch stable.
12805 - Do not include recognizeable strings in the commonname part of
12806 Tor's x509 certificates.
12809 - If we're a relay, avoid picking ourselves as an introduction point,
12810 a rendezvous point, or as the final hop for internal circuits. Bug
12811 reported by taranis and lodger. Bugfix on 0.1.2.x.
12812 - Patch from "Andrew S. Lists" to catch when we contact a directory
12813 mirror at IP address X and he says we look like we're coming from
12814 IP address X. Bugfix on 0.1.2.x.
12816 o Minor features (security):
12817 - Be more paranoid about overwriting sensitive memory on free(),
12818 as a defensive programming tactic to ensure forward secrecy.
12820 o Minor features (directory authority):
12821 - Actually validate the options passed to AuthDirReject,
12822 AuthDirInvalid, AuthDirBadDir, and AuthDirBadExit.
12823 - Reject router descriptors with out-of-range bandwidthcapacity or
12824 bandwidthburst values.
12826 o Minor features (controller):
12827 - Reject controller commands over 1MB in length. This keeps rogue
12828 processes from running us out of memory.
12830 o Minor features (misc):
12831 - Give more descriptive well-formedness errors for out-of-range
12832 hidden service descriptor/protocol versions.
12833 - Make memory debugging information describe more about history
12834 of cell allocation, so we can help reduce our memory use.
12836 o Deprecated features (controller):
12837 - The status/version/num-versioning and status/version/num-concurring
12838 GETINFO options are no longer useful in the v3 directory protocol:
12839 treat them as deprecated, and warn when they're used.
12842 - When our consensus networkstatus has been expired for a while, stop
12843 being willing to build circuits using it. Fixes bug 401. Bugfix
12845 - Directory caches now fetch certificates from all authorities
12846 listed in a networkstatus consensus, even when they do not
12847 recognize them. Fixes bug 571. Bugfix on 0.2.0.x.
12848 - When connecting to a bridge without specifying its key, insert
12849 the connection into the identity-to-connection map as soon as
12850 a key is learned. Fixes bug 574. Bugfix on 0.2.0.x.
12851 - Detect versions of OS X where malloc_good_size() is present in the
12852 library but never actually declared. Resolves bug 587. Bugfix
12854 - Stop incorrectly truncating zlib responses to directory authority
12855 signature download requests. Fixes bug 593. Bugfix on 0.2.0.x.
12856 - Stop recommending that every server operator send mail to tor-ops.
12857 Resolves bug 597. Bugfix on 0.1.2.x.
12858 - Don't trigger an assert if we start a directory authority with a
12859 private IP address (like 127.0.0.1).
12860 - Avoid possible failures when generating a directory with routers
12861 with over-long versions strings, or too many flags set. Bugfix
12863 - If an attempt to launch a DNS resolve request over the control
12864 port fails because we have overrun the limit on the number of
12865 connections, tell the controller that the request has failed.
12866 - Avoid using too little bandwidth when our clock skips a few
12867 seconds. Bugfix on 0.1.2.x.
12868 - Fix shell error when warning about missing packages in configure
12869 script, on Fedora or Red Hat machines. Bugfix on 0.2.0.x.
12870 - Do not become confused when receiving a spurious VERSIONS-like
12871 cell from a confused v1 client. Bugfix on 0.2.0.x.
12872 - Re-fetch v2 (as well as v0) rendezvous descriptors when all
12873 introduction points for a hidden service have failed. Patch from
12874 Karsten Loesing. Bugfix on 0.2.0.x.
12876 o Code simplifications and refactoring:
12877 - Remove some needless generality from cpuworker code, for improved
12879 - Stop overloading the circuit_t.onionskin field for both "onionskin
12880 from a CREATE cell that we are waiting for a cpuworker to be
12881 assigned" and "onionskin from an EXTEND cell that we are going to
12882 send to an OR as soon as we are connected". Might help with bug 600.
12883 - Add an in-place version of aes_crypt() so that we can avoid doing a
12884 needless memcpy() call on each cell payload.
12887 Changes in version 0.2.0.18-alpha - 2008-01-25
12888 Tor 0.2.0.18-alpha adds a sixth v3 directory authority run by CCC,
12889 fixes a big memory leak in 0.2.0.17-alpha, and adds new config options
12890 that can warn or reject connections to ports generally associated with
12891 vulnerable-plaintext protocols.
12893 o New directory authorities:
12894 - Set up dannenberg (run by CCC) as the sixth v3 directory
12898 - Fix a major memory leak when attempting to use the v2 TLS
12899 handshake code. Bugfix on 0.2.0.x; fixes bug 589.
12900 - We accidentally enabled the under-development v2 TLS handshake
12901 code, which was causing log entries like "TLS error while
12902 renegotiating handshake". Disable it again. Resolves bug 590.
12903 - We were computing the wrong Content-Length: header for directory
12904 responses that need to be compressed on the fly, causing clients
12905 asking for those items to always fail. Bugfix on 0.2.0.x; partially
12909 - Avoid going directly to the directory authorities even if you're a
12910 relay, if you haven't found yourself reachable yet or if you've
12911 decided not to advertise your dirport yet. Addresses bug 556.
12912 - If we've gone 12 hours since our last bandwidth check, and we
12913 estimate we have less than 50KB bandwidth capacity but we could
12914 handle more, do another bandwidth test.
12915 - New config options WarnPlaintextPorts and RejectPlaintextPorts so
12916 Tor can warn and/or refuse connections to ports commonly used with
12917 vulnerable-plaintext protocols. Currently we warn on ports 23,
12918 109, 110, and 143, but we don't reject any.
12921 - When we setconf ClientOnly to 1, close any current OR and Dir
12922 listeners. Reported by mwenge.
12923 - When we get a consensus that's been signed by more people than
12924 we expect, don't log about it; it's not a big deal. Reported
12928 - Don't answer "/tor/networkstatus-bridges" directory requests if
12929 the request isn't encrypted.
12930 - Make "ClientOnly 1" config option disable directory ports too.
12931 - Patches from Karsten Loesing to make v2 hidden services more
12932 robust: work even when there aren't enough HSDir relays available;
12933 retry when a v2 rend desc fetch fails; but don't retry if we
12934 already have a usable v0 rend desc.
12937 Changes in version 0.2.0.17-alpha - 2008-01-17
12938 Tor 0.2.0.17-alpha makes the tarball build cleanly again (whoops).
12941 - Make the tor-gencert man page get included correctly in the tarball.
12944 Changes in version 0.2.0.16-alpha - 2008-01-17
12945 Tor 0.2.0.16-alpha adds a fifth v3 directory authority run by Karsten
12946 Loesing, and generally cleans up a lot of features and minor bugs.
12948 o New directory authorities:
12949 - Set up gabelmoo (run by Karsten Loesing) as the fifth v3 directory
12952 o Major performance improvements:
12953 - Switch our old ring buffer implementation for one more like that
12954 used by free Unix kernels. The wasted space in a buffer with 1mb
12955 of data will now be more like 8k than 1mb. The new implementation
12956 also avoids realloc();realloc(); patterns that can contribute to
12957 memory fragmentation.
12960 - Configuration files now accept C-style strings as values. This
12961 helps encode characters not allowed in the current configuration
12962 file format, such as newline or #. Addresses bug 557.
12963 - Although we fixed bug 539 (where servers would send HTTP status 503
12964 responses _and_ send a body too), there are still servers out
12965 there that haven't upgraded. Therefore, make clients parse such
12966 bodies when they receive them.
12967 - When we're not serving v2 directory information, there is no reason
12968 to actually keep any around. Remove the obsolete files and directory
12969 on startup if they are very old and we aren't going to serve them.
12971 o Minor performance improvements:
12972 - Reference-count and share copies of address policy entries; only 5%
12973 of them were actually distinct.
12974 - Never walk through the list of logs if we know that no log is
12975 interested in a given message.
12978 - When an authority has not signed a consensus, do not try to
12979 download a nonexistent "certificate with key 00000000". Bugfix
12980 on 0.2.0.x. Fixes bug 569.
12981 - Fix a rare assert error when we're closing one of our threads:
12982 use a mutex to protect the list of logs, so we never write to the
12983 list as it's being freed. Bugfix on 0.1.2.x. Fixes the very rare
12984 bug 575, which is kind of the revenge of bug 222.
12985 - Patch from Karsten Loesing to complain less at both the client
12986 and the relay when a relay used to have the HSDir flag but doesn't
12987 anymore, and we try to upload a hidden service descriptor.
12988 - Stop leaking one cert per TLS context. Fixes bug 582. Bugfix on
12990 - Do not try to download missing certificates until we have tried
12991 to check our fallback consensus. Fixes bug 583.
12992 - Make bridges round reported GeoIP stats info up to the nearest
12993 estimate, not down. Now we can distinguish between "0 people from
12994 this country" and "1 person from this country".
12995 - Avoid a spurious free on base64 failure. Bugfix on 0.1.2.
12996 - Avoid possible segfault if key generation fails in
12997 crypto_pk_hybrid_encrypt. Bugfix on 0.2.0.
12998 - Avoid segfault in the case where a badly behaved v2 versioning
12999 directory sends a signed networkstatus with missing client-versions.
13001 - Avoid segfaults on certain complex invocations of
13002 router_get_by_hexdigest(). Bugfix on 0.1.2.
13003 - Correct bad index on array access in parse_http_time(). Bugfix
13005 - Fix possible bug in vote generation when server versions are present
13006 but client versions are not.
13007 - Fix rare bug on REDIRECTSTREAM control command when called with no
13008 port set: it could erroneously report an error when none had
13010 - Avoid bogus crash-prone, leak-prone tor_realloc when we're
13011 compressing large objects and find ourselves with more than 4k
13012 left over. Bugfix on 0.2.0.
13013 - Fix a small memory leak when setting up a hidden service.
13014 - Fix a few memory leaks that could in theory happen under bizarre
13016 - Fix an assert if we post a general-purpose descriptor via the
13017 control port but that descriptor isn't mentioned in our current
13018 network consensus. Bug reported by Jon McLachlan; bugfix on
13021 o Minor features (controller):
13022 - Get NS events working again. Patch from tup.
13023 - The GETCONF command now escapes and quotes configuration values
13024 that don't otherwise fit into the torrc file.
13025 - The SETCONF command now handles quoted values correctly.
13027 o Minor features (directory authorities):
13028 - New configuration options to override default maximum number of
13029 servers allowed on a single IP address. This is important for
13030 running a test network on a single host.
13031 - Actually implement the -s option to tor-gencert.
13032 - Add a manual page for tor-gencert.
13034 o Minor features (bridges):
13035 - Bridge authorities no longer serve bridge descriptors over
13036 unencrypted connections.
13038 o Minor features (other):
13039 - Add hidden services and DNSPorts to the list of things that make
13040 Tor accept that it has running ports. Change starting Tor with no
13041 ports from a fatal error to a warning; we might change it back if
13042 this turns out to confuse anybody. Fixes bug 579.
13045 Changes in version 0.1.2.19 - 2008-01-17
13046 Tor 0.1.2.19 fixes a huge memory leak on exit relays, makes the default
13047 exit policy a little bit more conservative so it's safer to run an
13048 exit relay on a home system, and fixes a variety of smaller issues.
13051 - Exit policies now reject connections that are addressed to a
13052 relay's public (external) IP address too, unless
13053 ExitPolicyRejectPrivate is turned off. We do this because too
13054 many relays are running nearby to services that trust them based
13055 on network address.
13058 - When the clock jumps forward a lot, do not allow the bandwidth
13059 buckets to become negative. Fixes bug 544.
13060 - Fix a memory leak on exit relays; we were leaking a cached_resolve_t
13061 on every successful resolve. Reported by Mike Perry.
13062 - Purge old entries from the "rephist" database and the hidden
13063 service descriptor database even when DirPort is zero.
13064 - Stop thinking that 0.1.2.x directory servers can handle "begin_dir"
13065 requests. Should ease bugs 406 and 419 where 0.1.2.x relays are
13066 crashing or mis-answering these requests.
13067 - When we decide to send a 503 response to a request for servers, do
13068 not then also send the server descriptors: this defeats the whole
13069 purpose. Fixes bug 539.
13072 - Changing the ExitPolicyRejectPrivate setting should cause us to
13073 rebuild our server descriptor.
13074 - Fix handling of hex nicknames when answering controller requests for
13075 networkstatus by name, or when deciding whether to warn about
13076 unknown routers in a config option. (Patch from mwenge.)
13077 - Fix a couple of hard-to-trigger autoconf problems that could result
13078 in really weird results on platforms whose sys/types.h files define
13079 nonstandard integer types.
13080 - Don't try to create the datadir when running --verify-config or
13081 --hash-password. Resolves bug 540.
13082 - If we were having problems getting a particular descriptor from the
13083 directory caches, and then we learned about a new descriptor for
13084 that router, we weren't resetting our failure count. Reported
13086 - Although we fixed bug 539 (where servers would send HTTP status 503
13087 responses _and_ send a body too), there are still servers out there
13088 that haven't upgraded. Therefore, make clients parse such bodies
13089 when they receive them.
13090 - Run correctly on systems where rlim_t is larger than unsigned long.
13091 This includes some 64-bit systems.
13092 - Run correctly on platforms (like some versions of OS X 10.5) where
13093 the real limit for number of open files is OPEN_FILES, not rlim_max
13094 from getrlimit(RLIMIT_NOFILES).
13095 - Avoid a spurious free on base64 failure.
13096 - Avoid segfaults on certain complex invocations of
13097 router_get_by_hexdigest().
13098 - Fix rare bug on REDIRECTSTREAM control command when called with no
13099 port set: it could erroneously report an error when none had
13103 Changes in version 0.2.0.15-alpha - 2007-12-25
13104 Tor 0.2.0.14-alpha and 0.2.0.15-alpha fix a bunch of bugs with the
13105 features added in 0.2.0.13-alpha.
13108 - Fix several remotely triggerable asserts based on DirPort requests
13109 for a v2 or v3 networkstatus object before we were prepared. This
13110 was particularly bad for 0.2.0.13 and later bridge relays, who
13111 would never have a v2 networkstatus and would thus always crash
13112 when used. Bugfixes on 0.2.0.x.
13113 - Estimate the v3 networkstatus size more accurately, rather than
13114 estimating it at zero bytes and giving it artificially high priority
13115 compared to other directory requests. Bugfix on 0.2.0.x.
13118 - Fix configure.in logic for cross-compilation.
13119 - When we load a bridge descriptor from the cache, and it was
13120 previously unreachable, mark it as retriable so we won't just
13121 ignore it. Also, try fetching a new copy immediately. Bugfixes
13123 - The bridge GeoIP stats were counting other relays, for example
13124 self-reachability and authority-reachability tests.
13127 - Support compilation to target iPhone; patch from cjacker huang.
13128 To build for iPhone, pass the --enable-iphone option to configure.
13131 Changes in version 0.2.0.14-alpha - 2007-12-23
13133 - Fix a crash on startup if you install Tor 0.2.0.13-alpha fresh
13134 without a datadirectory from a previous Tor install. Reported
13136 - Fix a crash when we fetch a descriptor that turns out to be
13137 unexpected (it used to be in our networkstatus when we started
13138 fetching it, but it isn't in our current networkstatus), and we
13139 aren't using bridges. Bugfix on 0.2.0.x.
13140 - Fix a crash when accessing hidden services: it would work the first
13141 time you use a given introduction point for your service, but
13142 on subsequent requests we'd be using garbage memory. Fixed by
13143 Karsten Loesing. Bugfix on 0.2.0.13-alpha.
13144 - Fix a crash when we load a bridge descriptor from disk but we don't
13145 currently have a Bridge line for it in our torrc. Bugfix on
13149 - If bridge authorities set BridgePassword, they will serve a
13150 snapshot of known bridge routerstatuses from their DirPort to
13151 anybody who knows that password. Unset by default.
13154 - Make the unit tests build again.
13155 - Make "GETINFO/desc-annotations/id/<OR digest>" actually work.
13156 - Make PublishServerDescriptor default to 1, so the default doesn't
13157 have to change as we invent new directory protocol versions.
13158 - Fix test for rlim_t on OSX 10.3: sys/resource.h doesn't want to
13159 be included unless sys/time.h is already included. Fixes
13160 bug 553. Bugfix on 0.2.0.x.
13161 - If we receive a general-purpose descriptor and then receive an
13162 identical bridge-purpose descriptor soon after, don't discard
13163 the next one as a duplicate.
13166 - If BridgeRelay is set to 1, then the default for
13167 PublishServerDescriptor is now "bridge" rather than "v2,v3".
13168 - If the user sets RelayBandwidthRate but doesn't set
13169 RelayBandwidthBurst, then make them equal rather than erroring out.
13172 Changes in version 0.2.0.13-alpha - 2007-12-21
13173 Tor 0.2.0.13-alpha adds a fourth v3 directory authority run by Geoff
13174 Goodell, fixes many more bugs, and adds a lot of infrastructure for
13177 o New directory authorities:
13178 - Set up lefkada (run by Geoff Goodell) as the fourth v3 directory
13182 - Only update guard status (usable / not usable) once we have
13183 enough directory information. This was causing us to always pick
13184 two new guards on startup (bugfix on 0.2.0.9-alpha), and it was
13185 causing us to discard all our guards on startup if we hadn't been
13186 running for a few weeks (bugfix on 0.1.2.x). Fixes bug 448.
13187 - Purge old entries from the "rephist" database and the hidden
13188 service descriptor databases even when DirPort is zero. Bugfix
13190 - We were ignoring our RelayBandwidthRate for the first 30 seconds
13191 after opening a circuit -- even a relayed circuit. Bugfix on
13193 - Stop thinking that 0.1.2.x directory servers can handle "begin_dir"
13194 requests. Should ease bugs 406 and 419 where 0.1.2.x relays are
13195 crashing or mis-answering these types of requests.
13196 - Relays were publishing their server descriptor to v1 and v2
13197 directory authorities, but they didn't try publishing to v3-only
13198 authorities. Fix this; and also stop publishing to v1 authorities.
13200 - When we were reading router descriptors from cache, we were ignoring
13201 the annotations -- so for example we were reading in bridge-purpose
13202 descriptors as general-purpose descriptors. Bugfix on 0.2.0.8-alpha.
13203 - When we decided to send a 503 response to a request for servers, we
13204 were then also sending the server descriptors: this defeats the
13205 whole purpose. Fixes bug 539; bugfix on 0.1.2.x.
13208 - Bridge relays now behave like clients with respect to time
13209 intervals for downloading new consensus documents -- otherwise they
13210 stand out. Bridge users now wait until the end of the interval,
13211 so their bridge relay will be sure to have a new consensus document.
13212 - Three new config options (AlternateDirAuthority,
13213 AlternateBridgeAuthority, and AlternateHSAuthority) that let the
13214 user selectively replace the default directory authorities by type,
13215 rather than the all-or-nothing replacement that DirServer offers.
13216 - Tor can now be configured to read a GeoIP file from disk in one
13217 of two formats. This can be used by controllers to map IP addresses
13218 to countries. Eventually, it may support exit-by-country.
13219 - When possible, bridge relays remember which countries users
13220 are coming from, and report aggregate information in their
13221 extra-info documents, so that the bridge authorities can learn
13222 where Tor is blocked.
13223 - Bridge directory authorities now do reachability testing on the
13224 bridges they know. They provide router status summaries to the
13225 controller via "getinfo ns/purpose/bridge", and also dump summaries
13226 to a file periodically.
13227 - Stop fetching directory info so aggressively if your DirPort is
13228 on but your ORPort is off; stop fetching v2 dir info entirely.
13229 You can override these choices with the new FetchDirInfoEarly
13233 - The fix in 0.2.0.12-alpha cleared the "hsdir" flag in v3 network
13234 consensus documents when there are too many relays at a single
13235 IP address. Now clear it in v2 network status documents too, and
13236 also clear it in routerinfo_t when the relay is no longer listed
13237 in the relevant networkstatus document.
13238 - Don't crash if we get an unexpected value for the
13239 PublishServerDescriptor config option. Reported by Matt Edman;
13240 bugfix on 0.2.0.9-alpha.
13241 - Our new v2 hidden service descriptor format allows descriptors
13242 that have no introduction points. But Tor crashed when we tried
13243 to build a descriptor with no intro points (and it would have
13244 crashed if we had tried to parse one). Bugfix on 0.2.0.x; patch
13245 by Karsten Loesing.
13246 - Fix building with dmalloc 5.5.2 with glibc.
13247 - Reject uploaded descriptors and extrainfo documents if they're
13248 huge. Otherwise we'll cache them all over the network and it'll
13249 clog everything up. Reported by Aljosha Judmayer.
13250 - Check for presence of s6_addr16 and s6_addr32 fields in in6_addr
13251 via autoconf. Should fix compile on solaris. Bugfix on 0.2.0.x.
13252 - When the DANGEROUS_VERSION controller status event told us we're
13253 running an obsolete version, it used the string "OLD" to describe
13254 it. Yet the "getinfo" interface used the string "OBSOLETE". Now use
13255 "OBSOLETE" in both cases. Bugfix on 0.1.2.x.
13256 - If we can't expand our list of entry guards (e.g. because we're
13257 using bridges or we have StrictEntryNodes set), don't mark relays
13258 down when they fail a directory request. Otherwise we're too quick
13259 to mark all our entry points down. Bugfix on 0.1.2.x.
13260 - Fix handling of hex nicknames when answering controller requests for
13261 networkstatus by name, or when deciding whether to warn about unknown
13262 routers in a config option. Bugfix on 0.1.2.x. (Patch from mwenge.)
13263 - Fix a couple of hard-to-trigger autoconf problems that could result
13264 in really weird results on platforms whose sys/types.h files define
13265 nonstandard integer types. Bugfix on 0.1.2.x.
13266 - Fix compilation with --disable-threads set. Bugfix on 0.2.0.x.
13267 - Don't crash on name lookup when we have no current consensus. Fixes
13268 bug 538; bugfix on 0.2.0.x.
13269 - Only Tors that want to mirror the v2 directory info should
13270 create the "cached-status" directory in their datadir. (All Tors
13271 used to create it.) Bugfix on 0.2.0.9-alpha.
13272 - Directory authorities should only automatically download Extra Info
13273 documents if they're v1, v2, or v3 authorities. Bugfix on 0.1.2.x.
13276 - On the USR1 signal, when dmalloc is in use, log the top 10 memory
13277 consumers. (We already do this on HUP.)
13278 - Authorities and caches fetch the v2 networkstatus documents
13279 less often, now that v3 is encouraged.
13280 - Add a new config option BridgeRelay that specifies you want to
13281 be a bridge relay. Right now the only difference is that it makes
13282 you answer begin_dir requests, and it makes you cache dir info,
13283 even if your DirPort isn't on.
13284 - Add "GETINFO/desc-annotations/id/<OR digest>" so controllers can
13285 ask about source, timestamp of arrival, purpose, etc. We need
13286 something like this to help Vidalia not do GeoIP lookups on bridge
13288 - Allow multiple HashedControlPassword config lines, to support
13289 multiple controller passwords.
13290 - Authorities now decide whether they're authoritative for a given
13291 router based on the router's purpose.
13292 - New config options AuthDirBadDir and AuthDirListBadDirs for
13293 authorities to mark certain relays as "bad directories" in the
13294 networkstatus documents. Also supports the "!baddir" directive in
13295 the approved-routers file.
13298 Changes in version 0.2.0.12-alpha - 2007-11-16
13299 This twelfth development snapshot fixes some more build problems as
13300 well as a few minor bugs.
13303 - Make it build on OpenBSD again. Patch from tup.
13304 - Substitute BINDIR and LOCALSTATEDIR in scripts. Fixes
13305 package-building for Red Hat, OS X, etc.
13307 o Minor bugfixes (on 0.1.2.x):
13308 - Changing the ExitPolicyRejectPrivate setting should cause us to
13309 rebuild our server descriptor.
13311 o Minor bugfixes (on 0.2.0.x):
13312 - When we're lacking a consensus, don't try to perform rendezvous
13313 operations. Reported by Karsten Loesing.
13314 - Fix a small memory leak whenever we decide against using a
13315 newly picked entry guard. Reported by Mike Perry.
13316 - When authorities detected more than two relays running on the same
13317 IP address, they were clearing all the status flags but forgetting
13318 to clear the "hsdir" flag. So clients were being told that a
13319 given relay was the right choice for a v2 hsdir lookup, yet they
13320 never had its descriptor because it was marked as 'not running'
13322 - If we're trying to fetch a bridge descriptor and there's no way
13323 the bridge authority could help us (for example, we don't know
13324 a digest, or there is no bridge authority), don't be so eager to
13325 fall back to asking the bridge authority.
13326 - If we're using bridges or have strictentrynodes set, and our
13327 chosen exit is in the same family as all our bridges/entry guards,
13328 then be flexible about families.
13331 - When we negotiate a v2 link-layer connection (not yet implemented),
13332 accept RELAY_EARLY cells and turn them into RELAY cells if we've
13333 negotiated a v1 connection for their next step. Initial code for
13337 Changes in version 0.2.0.11-alpha - 2007-11-12
13338 This eleventh development snapshot fixes some build problems with
13339 the previous snapshot. It also includes a more secure-by-default exit
13340 policy for relays, fixes an enormous memory leak for exit relays, and
13341 fixes another bug where servers were falling out of the directory list.
13344 - Exit policies now reject connections that are addressed to a
13345 relay's public (external) IP address too, unless
13346 ExitPolicyRejectPrivate is turned off. We do this because too
13347 many relays are running nearby to services that trust them based
13348 on network address. Bugfix on 0.1.2.x.
13351 - Fix a memory leak on exit relays; we were leaking a cached_resolve_t
13352 on every successful resolve. Reported by Mike Perry; bugfix
13354 - On authorities, never downgrade to old router descriptors simply
13355 because they're listed in the consensus. This created a catch-22
13356 where we wouldn't list a new descriptor because there was an
13357 old one in the consensus, and we couldn't get the new one in the
13358 consensus because we wouldn't list it. Possible fix for bug 548.
13359 Also, this might cause bug 543 to appear on authorities; if so,
13360 we'll need a band-aid for that. Bugfix on 0.2.0.9-alpha.
13362 o Packaging fixes on 0.2.0.10-alpha:
13363 - We were including instructions about what to do with the
13364 src/config/fallback-consensus file, but we weren't actually
13365 including it in the tarball. Disable all of that for now.
13368 - Allow people to say PreferTunnelledDirConns rather than
13369 PreferTunneledDirConns, for those alternate-spellers out there.
13372 - Don't reevaluate all the information from our consensus document
13373 just because we've downloaded a v2 networkstatus that we intend
13374 to cache. Fixes bug 545; bugfix on 0.2.0.x.
13377 Changes in version 0.2.0.10-alpha - 2007-11-10
13378 This tenth development snapshot adds a third v3 directory authority
13379 run by Mike Perry, adds most of Karsten Loesing's new hidden service
13380 descriptor format, fixes a bad crash bug and new bridge bugs introduced
13381 in 0.2.0.9-alpha, fixes many bugs with the v3 directory implementation,
13382 fixes some minor memory leaks in previous 0.2.0.x snapshots, and
13383 addresses many more minor issues.
13385 o New directory authorities:
13386 - Set up ides (run by Mike Perry) as the third v3 directory authority.
13389 - Allow tunnelled directory connections to ask for an encrypted
13390 "begin_dir" connection or an anonymized "uses a full Tor circuit"
13391 connection independently. Now we can make anonymized begin_dir
13392 connections for (e.g.) more secure hidden service posting and
13394 - More progress on proposal 114: code from Karsten Loesing to
13395 implement new hidden service descriptor format.
13396 - Raise the default BandwidthRate/BandwidthBurst to 5MB/10MB, to
13397 accommodate the growing number of servers that use the default
13398 and are reaching it.
13399 - Directory authorities use a new formula for selecting which nodes
13400 to advertise as Guards: they must be in the top 7/8 in terms of
13401 how long we have known about them, and above the median of those
13402 nodes in terms of weighted fractional uptime.
13403 - Make "not enough dir info yet" warnings describe *why* Tor feels
13404 it doesn't have enough directory info yet.
13407 - Stop servers from crashing if they set a Family option (or
13408 maybe in other situations too). Bugfix on 0.2.0.9-alpha; reported
13410 - Make bridge users work again -- the move to v3 directories in
13411 0.2.0.9-alpha had introduced a number of bugs that made bridges
13412 no longer work for clients.
13413 - When the clock jumps forward a lot, do not allow the bandwidth
13414 buckets to become negative. Bugfix on 0.1.2.x; fixes bug 544.
13416 o Major bugfixes (v3 dir, bugfixes on 0.2.0.9-alpha):
13417 - When the consensus lists a router descriptor that we previously were
13418 mirroring, but that we considered non-canonical, reload the
13419 descriptor as canonical. This fixes bug 543 where Tor servers
13420 would start complaining after a few days that they don't have
13421 enough directory information to build a circuit.
13422 - Consider replacing the current consensus when certificates arrive
13423 that make the pending consensus valid. Previously, we were only
13424 considering replacement when the new certs _didn't_ help.
13425 - Fix an assert error on startup if we didn't already have the
13426 consensus and certs cached in our datadirectory: we were caching
13427 the consensus in consensus_waiting_for_certs but then free'ing it
13429 - Avoid sending a request for "keys/fp" (for which we'll get a 400 Bad
13430 Request) if we need more v3 certs but we've already got pending
13431 requests for all of them.
13432 - Correctly back off from failing certificate downloads. Fixes
13434 - Authorities don't vote on the Running flag if they have been running
13435 for less than 30 minutes themselves. Fixes bug 547, where a newly
13436 started authority would vote that everyone was down.
13438 o New requirements:
13439 - Drop support for OpenSSL version 0.9.6. Just about nobody was using
13440 it, it had no AES, and it hasn't seen any security patches since
13444 - Clients now hold circuitless TLS connections open for 1.5 times
13445 MaxCircuitDirtiness (15 minutes), since it is likely that they'll
13446 rebuild a new circuit over them within that timeframe. Previously,
13447 they held them open only for KeepalivePeriod (5 minutes).
13448 - Use "If-Modified-Since" to avoid retrieving consensus
13449 networkstatuses that we already have.
13450 - When we have no consensus, check FallbackNetworkstatusFile (defaults
13451 to $PREFIX/share/tor/fallback-consensus) for a consensus. This way
13452 we start knowing some directory caches.
13453 - When we receive a consensus from the future, warn about skew.
13454 - Improve skew reporting: try to give the user a better log message
13455 about how skewed they are, and how much this matters.
13456 - When we have a certificate for an authority, believe that
13457 certificate's claims about the authority's IP address.
13458 - New --quiet command-line option to suppress the default console log.
13459 Good in combination with --hash-password.
13460 - Authorities send back an X-Descriptor-Not-New header in response to
13461 an accepted-but-discarded descriptor upload. Partially implements
13463 - Make the log message for "tls error. breaking." more useful.
13464 - Better log messages about certificate downloads, to attempt to
13465 track down the second incarnation of bug 546.
13467 o Minor features (bridges):
13468 - If bridge users set UpdateBridgesFromAuthority, but the digest
13469 they ask for is a 404 from the bridge authority, they now fall
13470 back to trying the bridge directly.
13471 - Bridges now use begin_dir to publish their server descriptor to
13472 the bridge authority, even when they haven't set TunnelDirConns.
13474 o Minor features (controller):
13475 - When reporting clock skew, and we know that the clock is _at least
13476 as skewed_ as some value, but we don't know the actual value,
13477 report the value as a "minimum skew."
13480 - Update linux-tor-prio.sh script to allow QoS based on the uid of
13481 the Tor process. Patch from Marco Bonetti with tweaks from Mike
13485 - Refuse to start if both ORPort and UseBridges are set. Bugfix
13486 on 0.2.0.x, suggested by Matt Edman.
13487 - Don't stop fetching descriptors when FetchUselessDescriptors is
13488 set, even if we stop asking for circuits. Bugfix on 0.1.2.x;
13489 reported by tup and ioerror.
13490 - Better log message on vote from unknown authority.
13491 - Don't log "Launching 0 request for 0 router" message.
13493 o Minor bugfixes (memory leaks):
13494 - Stop leaking memory every time we parse a v3 certificate. Bugfix
13496 - Stop leaking memory every time we load a v3 certificate. Bugfix
13497 on 0.2.0.1-alpha. Fixes bug 536.
13498 - Stop leaking a cached networkstatus on exit. Bugfix on
13500 - Stop leaking voter information every time we free a consensus.
13501 Bugfix on 0.2.0.3-alpha.
13502 - Stop leaking signed data every time we check a voter signature.
13503 Bugfix on 0.2.0.3-alpha.
13504 - Stop leaking a signature every time we fail to parse a consensus or
13505 a vote. Bugfix on 0.2.0.3-alpha.
13506 - Stop leaking v2_download_status_map on shutdown. Bugfix on
13508 - Stop leaking conn->nickname every time we make a connection to a
13509 Tor relay without knowing its expected identity digest (e.g. when
13510 using bridges). Bugfix on 0.2.0.3-alpha.
13512 - Minor bugfixes (portability):
13513 - Run correctly on platforms where rlim_t is larger than unsigned
13514 long, and/or where the real limit for number of open files is
13515 OPEN_FILES, not rlim_max from getrlimit(RLIMIT_NOFILES). In
13516 particular, these may be needed for OS X 10.5.
13519 Changes in version 0.1.2.18 - 2007-10-28
13520 Tor 0.1.2.18 fixes many problems including crash bugs, problems with
13521 hidden service introduction that were causing huge delays, and a big
13522 bug that was causing some servers to disappear from the network status
13523 lists for a few hours each day.
13525 o Major bugfixes (crashes):
13526 - If a connection is shut down abruptly because of something that
13527 happened inside connection_flushed_some(), do not call
13528 connection_finished_flushing(). Should fix bug 451:
13529 "connection_stop_writing: Assertion conn->write_event failed"
13530 Bugfix on 0.1.2.7-alpha.
13531 - Fix possible segfaults in functions called from
13532 rend_process_relay_cell().
13534 o Major bugfixes (hidden services):
13535 - Hidden services were choosing introduction points uniquely by
13536 hexdigest, but when constructing the hidden service descriptor
13537 they merely wrote the (potentially ambiguous) nickname.
13538 - Clients now use the v2 intro format for hidden service
13539 connections: they specify their chosen rendezvous point by identity
13540 digest rather than by (potentially ambiguous) nickname. These
13541 changes could speed up hidden service connections dramatically.
13543 o Major bugfixes (other):
13544 - Stop publishing a new server descriptor just because we get a
13545 HUP signal. This led (in a roundabout way) to some servers getting
13546 dropped from the networkstatus lists for a few hours each day.
13547 - When looking for a circuit to cannibalize, consider family as well
13548 as identity. Fixes bug 438. Bugfix on 0.1.0.x (which introduced
13549 circuit cannibalization).
13550 - When a router wasn't listed in a new networkstatus, we were leaving
13551 the flags for that router alone -- meaning it remained Named,
13552 Running, etc -- even though absence from the networkstatus means
13553 that it shouldn't be considered to exist at all anymore. Now we
13554 clear all the flags for routers that fall out of the networkstatus
13555 consensus. Fixes bug 529.
13558 - Don't try to access (or alter) the state file when running
13559 --list-fingerprint or --verify-config or --hash-password. Resolves
13561 - When generating information telling us how to extend to a given
13562 router, do not try to include the nickname if it is
13563 absent. Resolves bug 467.
13564 - Fix a user-triggerable segfault in expand_filename(). (There isn't
13565 a way to trigger this remotely.)
13566 - When sending a status event to the controller telling it that an
13567 OR address is reachable, set the port correctly. (Previously we
13568 were reporting the dir port.)
13569 - Fix a minor memory leak whenever a controller sends the PROTOCOLINFO
13570 command. Bugfix on 0.1.2.17.
13571 - When loading bandwidth history, do not believe any information in
13572 the future. Fixes bug 434.
13573 - When loading entry guard information, do not believe any information
13575 - When we have our clock set far in the future and generate an
13576 onion key, then re-set our clock to be correct, we should not stop
13577 the onion key from getting rotated.
13578 - On some platforms, accept() can return a broken address. Detect
13579 this more quietly, and deal accordingly. Fixes bug 483.
13580 - It's not actually an error to find a non-pending entry in the DNS
13581 cache when canceling a pending resolve. Don't log unless stuff
13582 is fishy. Resolves bug 463.
13583 - Don't reset trusted dir server list when we set a configuration
13584 option. Patch from Robert Hogan.
13585 - Don't try to create the datadir when running --verify-config or
13586 --hash-password. Resolves bug 540.
13589 Changes in version 0.2.0.9-alpha - 2007-10-24
13590 This ninth development snapshot switches clients to the new v3 directory
13591 system; allows servers to be listed in the network status even when they
13592 have the same nickname as a registered server; and fixes many other
13593 bugs including a big one that was causing some servers to disappear
13594 from the network status lists for a few hours each day.
13596 o Major features (directory system):
13597 - Clients now download v3 consensus networkstatus documents instead
13598 of v2 networkstatus documents. Clients and caches now base their
13599 opinions about routers on these consensus documents. Clients only
13600 download router descriptors listed in the consensus.
13601 - Authorities now list servers who have the same nickname as
13602 a different named server, but list them with a new flag,
13603 "Unnamed". Now we can list servers that happen to pick the same
13604 nickname as a server that registered two years ago and then
13605 disappeared. Partially implements proposal 122.
13606 - If the consensus lists a router as "Unnamed", the name is assigned
13607 to a different router: do not identify the router by that name.
13608 Partially implements proposal 122.
13609 - Authorities can now come to a consensus on which method to use to
13610 compute the consensus. This gives us forward compatibility.
13613 - Stop publishing a new server descriptor just because we HUP or
13614 when we find our DirPort to be reachable but won't actually publish
13615 it. New descriptors without any real changes are dropped by the
13616 authorities, and can screw up our "publish every 18 hours" schedule.
13618 - When a router wasn't listed in a new networkstatus, we were leaving
13619 the flags for that router alone -- meaning it remained Named,
13620 Running, etc -- even though absence from the networkstatus means
13621 that it shouldn't be considered to exist at all anymore. Now we
13622 clear all the flags for routers that fall out of the networkstatus
13623 consensus. Fixes bug 529; bugfix on 0.1.2.x.
13624 - Fix awful behavior in DownloadExtraInfo option where we'd fetch
13625 extrainfo documents and then discard them immediately for not
13626 matching the latest router. Bugfix on 0.2.0.1-alpha.
13628 o Minor features (v3 directory protocol):
13629 - Allow tor-gencert to generate a new certificate without replacing
13631 - Allow certificates to include an address.
13632 - When we change our directory-cache settings, reschedule all voting
13633 and download operations.
13634 - Reattempt certificate downloads immediately on failure, as long as
13635 we haven't failed a threshold number of times yet.
13636 - Delay retrying consensus downloads while we're downloading
13637 certificates to verify the one we just got. Also, count getting a
13638 consensus that we already have (or one that isn't valid) as a failure,
13639 and count failing to get the certificates after 20 minutes as a
13641 - Build circuits and download descriptors even if our consensus is a
13642 little expired. (This feature will go away once authorities are
13645 o Minor features (router descriptor cache):
13646 - If we find a cached-routers file that's been sitting around for more
13647 than 28 days unmodified, then most likely it's a leftover from
13648 when we upgraded to 0.2.0.8-alpha. Remove it. It has no good
13650 - When we (as a cache) download a descriptor because it was listed
13651 in a consensus, remember when the consensus was supposed to expire,
13652 and don't expire the descriptor until then.
13654 o Minor features (performance):
13655 - Call routerlist_remove_old_routers() much less often. This should
13656 speed startup, especially on directory caches.
13657 - Don't try to launch new descriptor downloads quite so often when we
13658 already have enough directory information to build circuits.
13659 - Base64 decoding was actually showing up on our profile when parsing
13660 the initial descriptor file; switch to an in-process all-at-once
13661 implementation that's about 3.5x times faster than calling out to
13664 o Minor features (compilation):
13665 - Detect non-ASCII platforms (if any still exist) and refuse to
13666 build there: some of our code assumes that 'A' is 65 and so on.
13668 o Minor bugfixes (v3 directory authorities, bugfixes on 0.2.0.x):
13669 - Make the "next period" votes into "current period" votes immediately
13670 after publishing the consensus; avoid a heisenbug that made them
13671 stick around indefinitely.
13672 - When we discard a vote as a duplicate, do not report this as
13674 - Treat missing v3 keys or certificates as an error when running as a
13675 v3 directory authority.
13676 - When we're configured to be a v3 authority, but we're only listed
13677 as a non-v3 authority in our DirServer line for ourself, correct
13679 - If an authority doesn't have a qualified hostname, just put
13680 its address in the vote. This fixes the problem where we referred to
13681 "moria on moria:9031."
13682 - Distinguish between detached signatures for the wrong period, and
13683 detached signatures for a divergent vote.
13684 - Fix a small memory leak when computing a consensus.
13685 - When there's no concensus, we were forming a vote every 30
13686 minutes, but writing the "valid-after" line in our vote based
13687 on our configured V3AuthVotingInterval: so unless the intervals
13688 matched up, we immediately rejected our own vote because it didn't
13689 start at the voting interval that caused us to construct a vote.
13691 o Minor bugfixes (v3 directory protocol, bugfixes on 0.2.0.x):
13692 - Delete unverified-consensus when the real consensus is set.
13693 - Consider retrying a consensus networkstatus fetch immediately
13694 after one fails: don't wait 60 seconds to notice.
13695 - When fetching a consensus as a cache, wait until a newer consensus
13696 should exist before trying to replace the current one.
13697 - Use a more forgiving schedule for retrying failed consensus
13698 downloads than for other types.
13700 o Minor bugfixes (other directory issues):
13701 - Correct the implementation of "download votes by digest." Bugfix on
13703 - Authorities no longer send back "400 you're unreachable please fix
13704 it" errors to Tor servers that aren't online all the time. We're
13705 supposed to tolerate these servers now. Bugfix on 0.1.2.x.
13707 o Minor bugfixes (controller):
13708 - Don't reset trusted dir server list when we set a configuration
13709 option. Patch from Robert Hogan; bugfix on 0.1.2.x.
13710 - Respond to INT and TERM SIGNAL commands before we execute the
13711 signal, in case the signal shuts us down. We had a patch in
13712 0.1.2.1-alpha that tried to do this by queueing the response on
13713 the connection's buffer before shutting down, but that really
13714 isn't the same thing at all. Bug located by Matt Edman.
13716 o Minor bugfixes (misc):
13717 - Correctly check for bad options to the "PublishServerDescriptor"
13718 config option. Bugfix on 0.2.0.1-alpha; reported by Matt Edman.
13719 - Stop leaking memory on failing case of base32_decode, and make
13720 it accept upper-case letters. Bugfixes on 0.2.0.7-alpha.
13721 - Don't try to download extrainfo documents when we're trying to
13722 fetch enough directory info to build a circuit: having enough
13723 info should get priority. Bugfix on 0.2.0.x.
13724 - Don't complain that "your server has not managed to confirm that its
13725 ports are reachable" if we haven't been able to build any circuits
13726 yet. Bug found by spending four hours without a v3 consensus. Bugfix
13728 - Detect the reason for failing to mmap a descriptor file we just
13729 wrote, and give a more useful log message. Fixes bug 533. Bugfix
13732 o Code simplifications and refactoring:
13733 - Remove support for the old bw_accounting file: we've been storing
13734 bandwidth accounting information in the state file since
13735 0.1.2.5-alpha. This may result in bandwidth accounting errors
13736 if you try to upgrade from 0.1.1.x or earlier, or if you try to
13737 downgrade to 0.1.1.x or earlier.
13738 - New convenience code to locate a file within the DataDirectory.
13739 - Move non-authority functionality out of dirvote.c.
13740 - Refactor the arguments for router_pick_{directory_|trusteddir}server
13741 so that they all take the same named flags.
13744 - Include the "tor-ctrl.sh" bash script by Stefan Behte to provide
13745 Unix users an easy way to script their Tor process (e.g. by
13746 adjusting bandwidth based on the time of the day).
13749 Changes in version 0.2.0.8-alpha - 2007-10-12
13750 This eighth development snapshot fixes a crash bug that's been bothering
13751 us since February 2007, lets bridge authorities store a list of bridge
13752 descriptors they've seen, gets v3 directory voting closer to working,
13753 starts caching v3 directory consensus documents on directory mirrors,
13754 and fixes a variety of smaller issues including some minor memory leaks.
13756 o Major features (router descriptor cache):
13757 - Store routers in a file called cached-descriptors instead of in
13758 cached-routers. Initialize cached-descriptors from cached-routers
13759 if the old format is around. The new format allows us to store
13760 annotations along with descriptors.
13761 - Use annotations to record the time we received each descriptor, its
13762 source, and its purpose.
13763 - Disable the SETROUTERPURPOSE controller command: it is now
13765 - Controllers should now specify cache=no or cache=yes when using
13766 the +POSTDESCRIPTOR command.
13767 - Bridge authorities now write bridge descriptors to disk, meaning
13768 we can export them to other programs and begin distributing them
13771 o Major features (directory authorities):
13772 - When a v3 authority is missing votes or signatures, it now tries
13774 - Directory authorities track weighted fractional uptime as well as
13775 weighted mean-time-between failures. WFU is suitable for deciding
13776 whether a node is "usually up", while MTBF is suitable for deciding
13777 whether a node is "likely to stay up." We need both, because
13778 "usually up" is a good requirement for guards, while "likely to
13779 stay up" is a good requirement for long-lived connections.
13781 o Major features (v3 directory system):
13782 - Caches now download v3 network status documents as needed,
13783 and download the descriptors listed in them.
13784 - All hosts now attempt to download and keep fresh v3 authority
13785 certificates, and re-attempt after failures.
13786 - More internal-consistency checks for vote parsing.
13788 o Major bugfixes (crashes):
13789 - If a connection is shut down abruptly because of something that
13790 happened inside connection_flushed_some(), do not call
13791 connection_finished_flushing(). Should fix bug 451. Bugfix on
13794 o Major bugfixes (performance):
13795 - Fix really bad O(n^2) performance when parsing a long list of
13796 routers: Instead of searching the entire list for an "extra-info "
13797 string which usually wasn't there, once for every routerinfo
13798 we read, just scan lines forward until we find one we like.
13800 - When we add data to a write buffer in response to the data on that
13801 write buffer getting low because of a flush, do not consider the
13802 newly added data as a candidate for immediate flushing, but rather
13803 make it wait until the next round of writing. Otherwise, we flush
13804 and refill recursively, and a single greedy TLS connection can
13805 eat all of our bandwidth. Bugfix on 0.1.2.7-alpha.
13807 o Minor features (v3 authority system):
13808 - Add more ways for tools to download the votes that lead to the
13810 - Send a 503 when low on bandwidth and a vote, consensus, or
13811 certificate is requested.
13812 - If-modified-since is now implemented properly for all kinds of
13813 certificate requests.
13815 o Minor bugfixes (network statuses):
13816 - Tweak the implementation of proposal 109 slightly: allow at most
13817 two Tor servers on the same IP address, except if it's the location
13818 of a directory authority, in which case allow five. Bugfix on
13821 o Minor bugfixes (controller):
13822 - When sending a status event to the controller telling it that an
13823 OR address is reachable, set the port correctly. (Previously we
13824 were reporting the dir port.) Bugfix on 0.1.2.x.
13826 o Minor bugfixes (v3 directory system):
13827 - Fix logic to look up a cert by its signing key digest. Bugfix on
13829 - Only change the reply to a vote to "OK" if it's not already
13830 set. This gets rid of annoying "400 OK" log messages, which may
13831 have been masking some deeper issue. Bugfix on 0.2.0.7-alpha.
13832 - When we get a valid consensus, recompute the voting schedule.
13833 - Base the valid-after time of a vote on the consensus voting
13834 schedule, not on our preferred schedule.
13835 - Make the return values and messages from signature uploads and
13836 downloads more sensible.
13837 - Fix a memory leak when serving votes and consensus documents, and
13838 another when serving certificates.
13840 o Minor bugfixes (performance):
13841 - Use a slightly simpler string hashing algorithm (copying Python's
13842 instead of Java's) and optimize our digest hashing algorithm to take
13843 advantage of 64-bit platforms and to remove some possibly-costly
13845 - Fix a minor memory leak whenever we parse guards from our state
13846 file. Bugfix on 0.2.0.7-alpha.
13847 - Fix a minor memory leak whenever we write out a file. Bugfix on
13849 - Fix a minor memory leak whenever a controller sends the PROTOCOLINFO
13850 command. Bugfix on 0.2.0.5-alpha.
13852 o Minor bugfixes (portability):
13853 - On some platforms, accept() can return a broken address. Detect
13854 this more quietly, and deal accordingly. Fixes bug 483.
13855 - Stop calling tor_strlower() on uninitialized memory in some cases.
13856 Bugfix in 0.2.0.7-alpha.
13858 o Minor bugfixes (usability):
13859 - Treat some 403 responses from directory servers as INFO rather than
13860 WARN-severity events.
13861 - It's not actually an error to find a non-pending entry in the DNS
13862 cache when canceling a pending resolve. Don't log unless stuff is
13863 fishy. Resolves bug 463.
13865 o Minor bugfixes (anonymity):
13866 - Never report that we've used more bandwidth than we're willing to
13867 relay: it leaks how much non-relay traffic we're using. Resolves
13869 - When looking for a circuit to cannibalize, consider family as well
13870 as identity. Fixes bug 438. Bugfix on 0.1.0.x (which introduced
13871 circuit cannibalization).
13873 o Code simplifications and refactoring:
13874 - Make a bunch of functions static. Remove some dead code.
13875 - Pull out about a third of the really big routerlist.c; put it in a
13876 new module, networkstatus.c.
13877 - Merge the extra fields in local_routerstatus_t back into
13878 routerstatus_t: we used to need one routerstatus_t for each
13879 authority's opinion, plus a local_routerstatus_t for the locally
13880 computed consensus opinion. To save space, we put the locally
13881 modified fields into local_routerstatus_t, and only the common
13882 stuff into routerstatus_t. But once v3 directories are in use,
13883 clients and caches will no longer need to hold authority opinions;
13884 thus, the rationale for keeping the types separate is now gone.
13885 - Make the code used to reschedule and reattempt downloads more
13887 - Turn all 'Are we a directory server/mirror?' logic into a call to
13889 - Remove the code to generate the oldest (v1) directory format.
13890 The code has been disabled since 0.2.0.5-alpha.
13893 Changes in version 0.2.0.7-alpha - 2007-09-21
13894 This seventh development snapshot makes bridges work again, makes bridge
13895 authorities work for the first time, fixes two huge performance flaws
13896 in hidden services, and fixes a variety of minor issues.
13898 o New directory authorities:
13899 - Set up moria1 and tor26 as the first v3 directory authorities. See
13900 doc/spec/dir-spec.txt for details on the new directory design.
13902 o Major bugfixes (crashes):
13903 - Fix possible segfaults in functions called from
13904 rend_process_relay_cell(). Bugfix on 0.1.2.x.
13906 o Major bugfixes (bridges):
13907 - Fix a bug that made servers send a "404 Not found" in response to
13908 attempts to fetch their server descriptor. This caused Tor servers
13909 to take many minutes to establish reachability for their DirPort,
13910 and it totally crippled bridges. Bugfix on 0.2.0.5-alpha.
13911 - Make "UpdateBridgesFromAuthority" torrc option work: when bridge
13912 users configure that and specify a bridge with an identity
13913 fingerprint, now they will lookup the bridge descriptor at the
13914 default bridge authority via a one-hop tunnel, but once circuits
13915 are established they will switch to a three-hop tunnel for later
13916 connections to the bridge authority. Bugfix in 0.2.0.3-alpha.
13918 o Major bugfixes (hidden services):
13919 - Hidden services were choosing introduction points uniquely by
13920 hexdigest, but when constructing the hidden service descriptor
13921 they merely wrote the (potentially ambiguous) nickname.
13922 - Clients now use the v2 intro format for hidden service
13923 connections: they specify their chosen rendezvous point by identity
13924 digest rather than by (potentially ambiguous) nickname. Both
13925 are bugfixes on 0.1.2.x, and they could speed up hidden service
13926 connections dramatically. Thanks to Karsten Loesing.
13928 o Minor features (security):
13929 - As a client, do not believe any server that tells us that an
13930 address maps to an internal address space.
13931 - Make it possible to enable HashedControlPassword and
13932 CookieAuthentication at the same time.
13934 o Minor features (guard nodes):
13935 - Tag every guard node in our state file with the version that
13936 we believe added it, or with our own version if we add it. This way,
13937 if a user temporarily runs an old version of Tor and then switches
13938 back to a new one, she doesn't automatically lose her guards.
13940 o Minor features (speed):
13941 - When implementing AES counter mode, update only the portions of the
13942 counter buffer that need to change, and don't keep separate
13943 network-order and host-order counters when they are the same (i.e.,
13944 on big-endian hosts.)
13946 o Minor features (controller):
13947 - Accept LF instead of CRLF on controller, since some software has a
13948 hard time generating real Internet newlines.
13949 - Add GETINFO values for the server status events
13950 "REACHABILITY_SUCCEEDED" and "GOOD_SERVER_DESCRIPTOR". Patch from
13953 o Removed features:
13954 - Routers no longer include bandwidth-history lines in their
13955 descriptors; this information is already available in extra-info
13956 documents, and including it in router descriptors took up 60%
13957 (!) of compressed router descriptor downloads. Completes
13958 implementation of proposal 104.
13959 - Remove the contrib scripts ExerciseServer.py, PathDemo.py,
13960 and TorControl.py, as they use the old v0 controller protocol,
13961 and are obsoleted by TorFlow anyway.
13962 - Drop support for v1 rendezvous descriptors, since we never used
13963 them anyway, and the code has probably rotted by now. Based on
13964 patch from Karsten Loesing.
13965 - On OSX, stop warning the user that kqueue support in libevent is
13966 "experimental", since it seems to have worked fine for ages.
13969 - When generating information telling us how to extend to a given
13970 router, do not try to include the nickname if it is absent. Fixes
13971 bug 467. Bugfix on 0.2.0.3-alpha.
13972 - Fix a user-triggerable (but not remotely-triggerable) segfault
13973 in expand_filename(). Bugfix on 0.1.2.x.
13974 - Fix a memory leak when freeing incomplete requests from DNSPort.
13975 Found by Niels Provos with valgrind. Bugfix on 0.2.0.1-alpha.
13976 - Don't try to access (or alter) the state file when running
13977 --list-fingerprint or --verify-config or --hash-password. (Resolves
13978 bug 499.) Bugfix on 0.1.2.x.
13979 - Servers used to decline to publish their DirPort if their
13980 BandwidthRate, RelayBandwidthRate, or MaxAdvertisedBandwidth
13981 were below a threshold. Now they only look at BandwidthRate and
13982 RelayBandwidthRate. Bugfix on 0.1.2.x.
13983 - Remove an optimization in the AES counter-mode code that assumed
13984 that the counter never exceeded 2^68. When the counter can be set
13985 arbitrarily as an IV (as it is by Karsten's new hidden services
13986 code), this assumption no longer holds. Bugfix on 0.1.2.x.
13987 - Resume listing "AUTHORITY" flag for authorities in network status.
13988 Bugfix on 0.2.0.3-alpha; reported by Alex de Joode.
13990 o Code simplifications and refactoring:
13991 - Revamp file-writing logic so we don't need to have the entire
13992 contents of a file in memory at once before we write to disk. Tor,
13994 - Turn "descriptor store" into a full-fledged type.
13995 - Move all NT services code into a separate source file.
13996 - Unify all code that computes medians, percentile elements, etc.
13997 - Get rid of a needless malloc when parsing address policies.
14000 Changes in version 0.1.2.17 - 2007-08-30
14001 Tor 0.1.2.17 features a new Vidalia version in the Windows and OS
14002 X bundles. Vidalia 0.0.14 makes authentication required for the
14003 ControlPort in the default configuration, which addresses important
14004 security risks. Everybody who uses Vidalia (or another controller)
14007 In addition, this Tor update fixes major load balancing problems with
14008 path selection, which should speed things up a lot once many people
14011 o Major bugfixes (security):
14012 - We removed support for the old (v0) control protocol. It has been
14013 deprecated since Tor 0.1.1.1-alpha, and keeping it secure has
14014 become more of a headache than it's worth.
14016 o Major bugfixes (load balancing):
14017 - When choosing nodes for non-guard positions, weight guards
14018 proportionally less, since they already have enough load. Patch
14020 - Raise the "max believable bandwidth" from 1.5MB/s to 10MB/s. This
14021 will allow fast Tor servers to get more attention.
14022 - When we're upgrading from an old Tor version, forget our current
14023 guards and pick new ones according to the new weightings. These
14024 three load balancing patches could raise effective network capacity
14025 by a factor of four. Thanks to Mike Perry for measurements.
14027 o Major bugfixes (stream expiration):
14028 - Expire not-yet-successful application streams in all cases if
14029 they've been around longer than SocksTimeout. Right now there are
14030 some cases where the stream will live forever, demanding a new
14031 circuit every 15 seconds. Fixes bug 454; reported by lodger.
14033 o Minor features (controller):
14034 - Add a PROTOCOLINFO controller command. Like AUTHENTICATE, it
14035 is valid before any authentication has been received. It tells
14036 a controller what kind of authentication is expected, and what
14037 protocol is spoken. Implements proposal 119.
14039 o Minor bugfixes (performance):
14040 - Save on most routerlist_assert_ok() calls in routerlist.c, thus
14041 greatly speeding up loading cached-routers from disk on startup.
14042 - Disable sentinel-based debugging for buffer code: we squashed all
14043 the bugs that this was supposed to detect a long time ago, and now
14044 its only effect is to change our buffer sizes from nice powers of
14045 two (which platform mallocs tend to like) to values slightly over
14046 powers of two (which make some platform mallocs sad).
14048 o Minor bugfixes (misc):
14049 - If exit bandwidth ever exceeds one third of total bandwidth, then
14050 use the correct formula to weight exit nodes when choosing paths.
14051 Based on patch from Mike Perry.
14052 - Choose perfectly fairly among routers when choosing by bandwidth and
14053 weighting by fraction of bandwidth provided by exits. Previously, we
14054 would choose with only approximate fairness, and correct ourselves
14055 if we ran off the end of the list.
14056 - If we require CookieAuthentication but we fail to write the
14057 cookie file, we would warn but not exit, and end up in a state
14058 where no controller could authenticate. Now we exit.
14059 - If we require CookieAuthentication, stop generating a new cookie
14060 every time we change any piece of our config.
14061 - Refuse to start with certain directory authority keys, and
14062 encourage people using them to stop.
14063 - Terminate multi-line control events properly. Original patch
14065 - Fix a minor memory leak when we fail to find enough suitable
14066 servers to choose a circuit.
14067 - Stop leaking part of the descriptor when we run into a particularly
14068 unparseable piece of it.
14071 Changes in version 0.2.0.6-alpha - 2007-08-26
14072 This sixth development snapshot features a new Vidalia version in the
14073 Windows and OS X bundles. Vidalia 0.0.14 makes authentication required for
14074 the ControlPort in the default configuration, which addresses important
14077 In addition, this snapshot fixes major load balancing problems
14078 with path selection, which should speed things up a lot once many
14079 people have upgraded. The directory authorities also use a new
14080 mean-time-between-failure approach to tracking which servers are stable,
14081 rather than just looking at the most recent uptime.
14083 o New directory authorities:
14084 - Set up Tonga as the default bridge directory authority.
14087 - Directory authorities now track servers by weighted
14088 mean-times-between-failures. When we have 4 or more days of data,
14089 use measured MTBF rather than declared uptime to decide whether
14090 to call a router Stable. Implements proposal 108.
14092 o Major bugfixes (load balancing):
14093 - When choosing nodes for non-guard positions, weight guards
14094 proportionally less, since they already have enough load. Patch
14096 - Raise the "max believable bandwidth" from 1.5MB/s to 10MB/s. This
14097 will allow fast Tor servers to get more attention.
14098 - When we're upgrading from an old Tor version, forget our current
14099 guards and pick new ones according to the new weightings. These
14100 three load balancing patches could raise effective network capacity
14101 by a factor of four. Thanks to Mike Perry for measurements.
14103 o Major bugfixes (descriptor parsing):
14104 - Handle unexpected whitespace better in malformed descriptors. Bug
14105 found using Benedikt Boss's new Tor fuzzer! Bugfix on 0.2.0.x.
14108 - There is now an ugly, temporary "desc/all-recent-extrainfo-hack"
14109 GETINFO for Torstat to use until it can switch to using extrainfos.
14110 - Optionally (if built with -DEXPORTMALLINFO) export the output
14111 of mallinfo via http, as tor/mallinfo.txt. Only accessible
14115 - Do not intermix bridge routers with controller-added
14116 routers. (Bugfix on 0.2.0.x)
14117 - Do not fail with an assert when accept() returns an unexpected
14118 address family. Addresses but does not wholly fix bug 483. (Bugfix
14120 - Let directory authorities startup even when they can't generate
14121 a descriptor immediately, e.g. because they don't know their
14123 - Stop putting the authentication cookie in a file called "0"
14124 in your working directory if you don't specify anything for the
14125 new CookieAuthFile option. Reported by Matt Edman.
14126 - Make it possible to read the PROTOCOLINFO response in a way that
14127 conforms to our control-spec. Reported by Matt Edman.
14128 - Fix a minor memory leak when we fail to find enough suitable
14129 servers to choose a circuit. Bugfix on 0.1.2.x.
14130 - Stop leaking part of the descriptor when we run into a particularly
14131 unparseable piece of it. Bugfix on 0.1.2.x.
14132 - Unmap the extrainfo cache file on exit.
14135 Changes in version 0.2.0.5-alpha - 2007-08-19
14136 This fifth development snapshot fixes compilation on Windows again;
14137 fixes an obnoxious client-side bug that slowed things down and put
14138 extra load on the network; gets us closer to using the v3 directory
14139 voting scheme; makes it easier for Tor controllers to use cookie-based
14140 authentication; and fixes a variety of other bugs.
14142 o Removed features:
14143 - Version 1 directories are no longer generated in full. Instead,
14144 authorities generate and serve "stub" v1 directories that list
14145 no servers. This will stop Tor versions 0.1.0.x and earlier from
14146 working, but (for security reasons) nobody should be running those
14149 o Major bugfixes (compilation, 0.2.0.x):
14150 - Try to fix Win32 compilation again: improve checking for IPv6 types.
14151 - Try to fix MSVC compilation: build correctly on platforms that do
14152 not define s6_addr16 or s6_addr32.
14153 - Fix compile on platforms without getaddrinfo: bug found by Li-Hui
14156 o Major bugfixes (stream expiration):
14157 - Expire not-yet-successful application streams in all cases if
14158 they've been around longer than SocksTimeout. Right now there are
14159 some cases where the stream will live forever, demanding a new
14160 circuit every 15 seconds. Bugfix on 0.1.2.7-alpha; fixes bug 454;
14161 reported by lodger.
14163 o Minor features (directory servers):
14164 - When somebody requests a list of statuses or servers, and we have
14165 none of those, return a 404 rather than an empty 200.
14167 o Minor features (directory voting):
14168 - Store v3 consensus status consensuses on disk, and reload them
14171 o Minor features (security):
14172 - Warn about unsafe ControlPort configurations.
14173 - Refuse to start with certain directory authority keys, and
14174 encourage people using them to stop.
14176 o Minor features (controller):
14177 - Add a PROTOCOLINFO controller command. Like AUTHENTICATE, it
14178 is valid before any authentication has been received. It tells
14179 a controller what kind of authentication is expected, and what
14180 protocol is spoken. Implements proposal 119.
14181 - New config option CookieAuthFile to choose a new location for the
14182 cookie authentication file, and config option
14183 CookieAuthFileGroupReadable to make it group-readable.
14185 o Minor features (unit testing):
14186 - Add command-line arguments to unit-test executable so that we can
14187 invoke any chosen test from the command line rather than having
14188 to run the whole test suite at once; and so that we can turn on
14189 logging for the unit tests.
14191 o Minor bugfixes (on 0.1.2.x):
14192 - If we require CookieAuthentication but we fail to write the
14193 cookie file, we would warn but not exit, and end up in a state
14194 where no controller could authenticate. Now we exit.
14195 - If we require CookieAuthentication, stop generating a new cookie
14196 every time we change any piece of our config.
14197 - When loading bandwidth history, do not believe any information in
14198 the future. Fixes bug 434.
14199 - When loading entry guard information, do not believe any information
14201 - When we have our clock set far in the future and generate an
14202 onion key, then re-set our clock to be correct, we should not stop
14203 the onion key from getting rotated.
14204 - Clean up torrc sample config file.
14205 - Do not automatically run configure from autogen.sh. This
14206 non-standard behavior tended to annoy people who have built other
14209 o Minor bugfixes (on 0.2.0.x):
14210 - Fix a bug with AutomapHostsOnResolve that would always cause
14211 the second request to fail. Bug reported by Kate. Bugfix on
14213 - Fix a bug in ADDRMAP controller replies that would sometimes
14214 try to print a NULL. Patch from tup.
14215 - Read v3 directory authority keys from the right location.
14216 - Numerous bugfixes to directory voting code.
14219 Changes in version 0.1.2.16 - 2007-08-01
14220 Tor 0.1.2.16 fixes a critical security vulnerability that allows a
14221 remote attacker in certain situations to rewrite the user's torrc
14222 configuration file. This can completely compromise anonymity of users
14223 in most configurations, including those running the Vidalia bundles,
14224 TorK, etc. Or worse.
14226 o Major security fixes:
14227 - Close immediately after missing authentication on control port;
14228 do not allow multiple authentication attempts.
14231 Changes in version 0.2.0.4-alpha - 2007-08-01
14232 This fourth development snapshot fixes a critical security vulnerability
14233 for most users, specifically those running Vidalia, TorK, etc. Everybody
14234 should upgrade to either 0.1.2.16 or 0.2.0.4-alpha.
14236 o Major security fixes:
14237 - Close immediately after missing authentication on control port;
14238 do not allow multiple authentication attempts.
14240 o Major bugfixes (compilation):
14241 - Fix win32 compilation: apparently IN_ADDR and IN6_ADDR are already
14244 o Minor features (performance):
14245 - Be even more aggressive about releasing RAM from small
14246 empty buffers. Thanks to our free-list code, this shouldn't be too
14247 performance-intensive.
14248 - Disable sentinel-based debugging for buffer code: we squashed all
14249 the bugs that this was supposed to detect a long time ago, and
14250 now its only effect is to change our buffer sizes from nice
14251 powers of two (which platform mallocs tend to like) to values
14252 slightly over powers of two (which make some platform mallocs sad).
14253 - Log malloc statistics from mallinfo() on platforms where it
14257 Changes in version 0.2.0.3-alpha - 2007-07-29
14258 This third development snapshot introduces new experimental
14259 blocking-resistance features and a preliminary version of the v3
14260 directory voting design, and includes many other smaller features
14264 - The first pieces of our "bridge" design for blocking-resistance
14265 are implemented. People can run bridge directory authorities;
14266 people can run bridges; and people can configure their Tor clients
14267 with a set of bridges to use as the first hop into the Tor network.
14268 See http://archives.seul.org/or/talk/Jul-2007/msg00249.html for
14270 - Create listener connections before we setuid to the configured
14271 User and Group. Now non-Windows users can choose port values
14272 under 1024, start Tor as root, and have Tor bind those ports
14273 before it changes to another UID. (Windows users could already
14275 - Added a new ConstrainedSockets config option to set SO_SNDBUF and
14276 SO_RCVBUF on TCP sockets. Hopefully useful for Tor servers running
14277 on "vserver" accounts. (Patch from coderman.)
14278 - Be even more aggressive about separating local traffic from relayed
14279 traffic when RelayBandwidthRate is set. (Refines proposal 111.)
14281 o Major features (experimental):
14282 - First cut of code for "v3 dir voting": directory authorities will
14283 vote on a common network status document rather than each publishing
14284 their own opinion. This code needs more testing and more corner-case
14285 handling before it's ready for use.
14288 - Directory authorities now call routers Fast if their bandwidth is
14289 at least 100KB/s, and consider their bandwidth adequate to be a
14290 Guard if it is at least 250KB/s, no matter the medians. This fix
14291 complements proposal 107. [Bugfix on 0.1.2.x]
14292 - Directory authorities now never mark more than 3 servers per IP as
14293 Valid and Running. (Implements proposal 109, by Kevin Bauer and
14295 - Minor change to organizationName and commonName generation
14296 procedures in TLS certificates during Tor handshakes, to invalidate
14297 some earlier censorware approaches. This is not a long-term
14298 solution, but applying it will give us a bit of time to look into
14299 the epidemiology of countermeasures as they spread.
14301 o Major bugfixes (directory):
14302 - Rewrite directory tokenization code to never run off the end of
14303 a string. Fixes bug 455. Patch from croup. [Bugfix on 0.1.2.x]
14305 o Minor features (controller):
14306 - Add a SOURCE_ADDR field to STREAM NEW events so that controllers can
14307 match requests to applications. (Patch from Robert Hogan.)
14308 - Report address and port correctly on connections to DNSPort. (Patch
14309 from Robert Hogan.)
14310 - Add a RESOLVE command to launch hostname lookups. (Original patch
14311 from Robert Hogan.)
14312 - Add GETINFO status/enough-dir-info to let controllers tell whether
14313 Tor has downloaded sufficient directory information. (Patch
14315 - You can now use the ControlSocket option to tell Tor to listen for
14316 controller connections on Unix domain sockets on systems that
14317 support them. (Patch from Peter Palfrader.)
14318 - STREAM NEW events are generated for DNSPort requests and for
14319 tunneled directory connections. (Patch from Robert Hogan.)
14320 - New "GETINFO address-mappings/*" command to get address mappings
14321 with expiry information. "addr-mappings/*" is now deprecated.
14324 o Minor features (misc):
14325 - Merge in some (as-yet-unused) IPv6 address manipulation code. (Patch
14327 - The tor-gencert tool for v3 directory authorities now creates all
14328 files as readable to the file creator only, and write-protects
14329 the authority identity key.
14330 - When dumping memory usage, list bytes used in buffer memory
14332 - When running with dmalloc, dump more stats on hup and on exit.
14333 - Directory authorities now fail quickly and (relatively) harmlessly
14334 if they generate a network status document that is somehow
14337 o Traffic load balancing improvements:
14338 - If exit bandwidth ever exceeds one third of total bandwidth, then
14339 use the correct formula to weight exit nodes when choosing paths.
14340 (Based on patch from Mike Perry.)
14341 - Choose perfectly fairly among routers when choosing by bandwidth and
14342 weighting by fraction of bandwidth provided by exits. Previously, we
14343 would choose with only approximate fairness, and correct ourselves
14344 if we ran off the end of the list. [Bugfix on 0.1.2.x]
14346 o Performance improvements:
14347 - Be more aggressive with freeing buffer RAM or putting it on the
14349 - Use Critical Sections rather than Mutexes for synchronizing threads
14350 on win32; Mutexes are heavier-weight, and designed for synchronizing
14353 o Deprecated and removed features:
14354 - RedirectExits is now deprecated.
14355 - Stop allowing address masks that do not correspond to bit prefixes.
14356 We have warned about these for a really long time; now it's time
14357 to reject them. (Patch from croup.)
14359 o Minor bugfixes (directory):
14360 - Fix another crash bug related to extra-info caching. (Bug found by
14361 Peter Palfrader.) [Bugfix on 0.2.0.2-alpha]
14362 - Directories no longer return a "304 not modified" when they don't
14363 have the networkstatus the client asked for. Also fix a memory
14364 leak when returning 304 not modified. [Bugfixes on 0.2.0.2-alpha]
14365 - We had accidentally labelled 0.1.2.x directory servers as not
14366 suitable for begin_dir requests, and had labelled no directory
14367 servers as suitable for uploading extra-info documents. [Bugfix
14370 o Minor bugfixes (dns):
14371 - Fix a crash when DNSPort is set more than once. (Patch from Robert
14372 Hogan.) [Bugfix on 0.2.0.2-alpha]
14373 - Add DNSPort connections to the global connection list, so that we
14374 can time them out correctly. (Bug found by Robert Hogan.) [Bugfix
14376 - Fix a dangling reference that could lead to a crash when DNSPort is
14377 changed or closed (Patch from Robert Hogan.) [Bugfix on
14380 o Minor bugfixes (controller):
14381 - Provide DNS expiry times in GMT, not in local time. For backward
14382 compatibility, ADDRMAP events only provide GMT expiry in an extended
14383 field. "GETINFO address-mappings" always does the right thing.
14384 - Use CRLF line endings properly in NS events.
14385 - Terminate multi-line control events properly. (Original patch
14386 from tup.) [Bugfix on 0.1.2.x-alpha]
14387 - Do not include spaces in SOURCE_ADDR fields in STREAM
14388 events. Resolves bug 472. [Bugfix on 0.2.0.x-alpha]
14391 Changes in version 0.1.2.15 - 2007-07-17
14392 Tor 0.1.2.15 fixes several crash bugs, fixes some anonymity-related
14393 problems, fixes compilation on BSD, and fixes a variety of other
14394 bugs. Everybody should upgrade.
14396 o Major bugfixes (compilation):
14397 - Fix compile on FreeBSD/NetBSD/OpenBSD. Oops.
14399 o Major bugfixes (crashes):
14400 - Try even harder not to dereference the first character after
14401 an mmap(). Reported by lodger.
14402 - Fix a crash bug in directory authorities when we re-number the
14403 routerlist while inserting a new router.
14404 - When the cached-routers file is an even multiple of the page size,
14405 don't run off the end and crash. (Fixes bug 455; based on idea
14407 - Fix eventdns.c behavior on Solaris: It is critical to include
14408 orconfig.h _before_ sys/types.h, so that we can get the expected
14409 definition of _FILE_OFFSET_BITS.
14411 o Major bugfixes (security):
14412 - Fix a possible buffer overrun when using BSD natd support. Bug
14414 - When sending destroy cells from a circuit's origin, don't include
14415 the reason for tearing down the circuit. The spec says we didn't,
14416 and now we actually don't. Reported by lodger.
14417 - Keep streamids from different exits on a circuit separate. This
14418 bug may have allowed other routers on a given circuit to inject
14419 cells into streams. Reported by lodger; fixes bug 446.
14420 - If there's a never-before-connected-to guard node in our list,
14421 never choose any guards past it. This way we don't expand our
14422 guard list unless we need to.
14424 o Minor bugfixes (guard nodes):
14425 - Weight guard selection by bandwidth, so that low-bandwidth nodes
14426 don't get overused as guards.
14428 o Minor bugfixes (directory):
14429 - Correctly count the number of authorities that recommend each
14430 version. Previously, we were under-counting by 1.
14431 - Fix a potential crash bug when we load many server descriptors at
14432 once and some of them make others of them obsolete. Fixes bug 458.
14434 o Minor bugfixes (hidden services):
14435 - Stop tearing down the whole circuit when the user asks for a
14436 connection to a port that the hidden service didn't configure.
14439 o Minor bugfixes (misc):
14440 - On Windows, we were preventing other processes from reading
14441 cached-routers while Tor was running. Reported by janbar.
14442 - Fix a possible (but very unlikely) bug in picking routers by
14443 bandwidth. Add a log message to confirm that it is in fact
14444 unlikely. Patch from lodger.
14445 - Backport a couple of memory leak fixes.
14446 - Backport miscellaneous cosmetic bugfixes.
14449 Changes in version 0.2.0.2-alpha - 2007-06-02
14450 o Major bugfixes on 0.2.0.1-alpha:
14451 - Fix an assertion failure related to servers without extra-info digests.
14452 Resolves bugs 441 and 442.
14454 o Minor features (directory):
14455 - Support "If-Modified-Since" when answering HTTP requests for
14456 directories, running-routers documents, and network-status documents.
14457 (There's no need to support it for router descriptors, since those
14458 are downloaded by descriptor digest.)
14460 o Minor build issues:
14461 - Clear up some MIPSPro compiler warnings.
14462 - When building from a tarball on a machine that happens to have SVK
14463 installed, report the micro-revision as whatever version existed
14464 in the tarball, not as "x".
14467 Changes in version 0.2.0.1-alpha - 2007-06-01
14468 This early development snapshot provides new features for people running
14469 Tor as both a client and a server (check out the new RelayBandwidth
14470 config options); lets Tor run as a DNS proxy; and generally moves us
14471 forward on a lot of fronts.
14473 o Major features, server usability:
14474 - New config options RelayBandwidthRate and RelayBandwidthBurst:
14475 a separate set of token buckets for relayed traffic. Right now
14476 relayed traffic is defined as answers to directory requests, and
14477 OR connections that don't have any local circuits on them.
14479 o Major features, client usability:
14480 - A client-side DNS proxy feature to replace the need for
14481 dns-proxy-tor: Just set "DNSPort 9999", and Tor will now listen
14482 for DNS requests on port 9999, use the Tor network to resolve them
14483 anonymously, and send the reply back like a regular DNS server.
14484 The code still only implements a subset of DNS.
14485 - Make PreferTunneledDirConns and TunnelDirConns work even when
14486 we have no cached directory info. This means Tor clients can now
14487 do all of their connections protected by TLS.
14489 o Major features, performance and efficiency:
14490 - Directory authorities accept and serve "extra info" documents for
14491 routers. These documents contain fields from router descriptors
14492 that aren't usually needed, and that use a lot of excess
14493 bandwidth. Once these fields are removed from router descriptors,
14494 the bandwidth savings should be about 60%. [Partially implements
14496 - Servers upload extra-info documents to any authority that accepts
14497 them. Authorities (and caches that have been configured to download
14498 extra-info documents) download them as needed. [Partially implements
14500 - Change the way that Tor buffers data that it is waiting to write.
14501 Instead of queueing data cells in an enormous ring buffer for each
14502 client->OR or OR->OR connection, we now queue cells on a separate
14503 queue for each circuit. This lets us use less slack memory, and
14504 will eventually let us be smarter about prioritizing different kinds
14506 - Use memory pools to allocate cells with better speed and memory
14507 efficiency, especially on platforms where malloc() is inefficient.
14508 - Stop reading on edge connections when their corresponding circuit
14509 buffers are full; start again as the circuits empty out.
14511 o Major features, other:
14512 - Add an HSAuthorityRecordStats option that hidden service authorities
14513 can use to track statistics of overall hidden service usage without
14514 logging information that would be very useful to an attacker.
14515 - Start work implementing multi-level keys for directory authorities:
14516 Add a standalone tool to generate key certificates. (Proposal 103.)
14519 - Directory authorities now call routers Stable if they have an
14520 uptime of at least 30 days, even if that's not the median uptime
14521 in the network. Implements proposal 107, suggested by Kevin Bauer
14524 o Minor fixes (resource management):
14525 - Count the number of open sockets separately from the number
14526 of active connection_t objects. This will let us avoid underusing
14527 our allocated connection limit.
14528 - We no longer use socket pairs to link an edge connection to an
14529 anonymous directory connection or a DirPort test connection.
14530 Instead, we track the link internally and transfer the data
14531 in-process. This saves two sockets per "linked" connection (at the
14532 client and at the server), and avoids the nasty Windows socketpair()
14534 - Keep unused 4k and 16k buffers on free lists, rather than wasting 8k
14535 for every single inactive connection_t. Free items from the
14536 4k/16k-buffer free lists when they haven't been used for a while.
14538 o Minor features (build):
14539 - Make autoconf search for libevent, openssl, and zlib consistently.
14540 - Update deprecated macros in configure.in.
14541 - When warning about missing headers, tell the user to let us
14542 know if the compile succeeds anyway, so we can downgrade the
14544 - Include the current subversion revision as part of the version
14545 string: either fetch it directly if we're in an SVN checkout, do
14546 some magic to guess it if we're in an SVK checkout, or use
14547 the last-detected version if we're building from a .tar.gz.
14548 Use this version consistently in log messages.
14550 o Minor features (logging):
14551 - Always prepend "Bug: " to any log message about a bug.
14552 - Put a platform string (e.g. "Linux i686") in the startup log
14553 message, so when people paste just their logs, we know if it's
14554 OpenBSD or Windows or what.
14555 - When logging memory usage, break down memory used in buffers by
14558 o Minor features (directory system):
14559 - New config option V2AuthoritativeDirectory that all directory
14560 authorities should set. This will let future authorities choose
14561 not to serve V2 directory information.
14562 - Directory authorities allow multiple router descriptors and/or extra
14563 info documents to be uploaded in a single go. This will make
14564 implementing proposal 104 simpler.
14566 o Minor features (controller):
14567 - Add a new config option __DisablePredictedCircuits designed for
14568 use by the controller, when we don't want Tor to build any circuits
14570 - Let the controller specify HOP=%d as an argument to ATTACHSTREAM,
14571 so we can exit from the middle of the circuit.
14572 - Implement "getinfo status/circuit-established".
14573 - Implement "getinfo status/version/..." so a controller can tell
14574 whether the current version is recommended, and whether any versions
14575 are good, and how many authorities agree. (Patch from shibz.)
14577 o Minor features (hidden services):
14578 - Allow multiple HiddenServicePort directives with the same virtual
14579 port; when they occur, the user is sent round-robin to one
14580 of the target ports chosen at random. Partially fixes bug 393 by
14581 adding limited ad-hoc round-robining.
14583 o Minor features (other):
14585 - Add a new AutomapHostsOnResolve option: when it is enabled, any
14586 resolve request for hosts matching a given pattern causes Tor to
14587 generate an internal virtual address mapping for that host. This
14588 allows DNSPort to work sensibly with hidden service users. By
14589 default, .exit and .onion addresses are remapped; the list of
14590 patterns can be reconfigured with AutomapHostsSuffixes.
14591 - Add an "-F" option to tor-resolve to force a resolve for a .onion
14592 address. Thanks to the AutomapHostsOnResolve option, this is no
14593 longer a completely silly thing to do.
14594 - If Tor is invoked from something that isn't a shell (e.g. Vidalia),
14595 now we expand "-f ~/.tor/torrc" correctly. Suggested by Matt Edman.
14596 - Treat "2gb" when given in torrc for a bandwidth as meaning 2gb,
14597 minus 1 byte: the actual maximum declared bandwidth.
14599 o Removed features:
14600 - Removed support for the old binary "version 0" controller protocol.
14601 This has been deprecated since 0.1.1, and warnings have been issued
14602 since 0.1.2. When we encounter a v0 control message, we now send
14603 back an error and close the connection.
14604 - Remove the old "dns worker" server DNS code: it hasn't been default
14605 since 0.1.2.2-alpha, and all the servers seem to be using the new
14608 o Minor bugfixes (portability):
14609 - Even though Windows is equally happy with / and \ as path separators,
14610 try to use \ consistently on Windows and / consistently on Unix: it
14611 makes the log messages nicer.
14612 - Correctly report platform name on Windows 95 OSR2 and Windows 98 SE.
14613 - Read resolv.conf files correctly on platforms where read() returns
14614 partial results on small file reads.
14616 o Minor bugfixes (directory):
14617 - Correctly enforce that elements of directory objects do not appear
14618 more often than they are allowed to appear.
14619 - When we are reporting the DirServer line we just parsed, we were
14620 logging the second stanza of the key fingerprint, not the first.
14622 o Minor bugfixes (logging):
14623 - When we hit an EOF on a log (probably because we're shutting down),
14624 don't try to remove the log from the list: just mark it as
14625 unusable. (Bulletproofs against bug 222.)
14627 o Minor bugfixes (other):
14628 - In the exitlist script, only consider the most recently published
14629 server descriptor for each server. Also, when the user requests
14630 a list of servers that _reject_ connections to a given address,
14631 explicitly exclude the IPs that also have servers that accept
14632 connections to that address. (Resolves bug 405.)
14633 - Stop allowing hibernating servers to be "stable" or "fast".
14634 - On Windows, we were preventing other processes from reading
14635 cached-routers while Tor was running. (Reported by janbar)
14636 - Make the NodeFamilies config option work. (Reported by
14637 lodger -- it has never actually worked, even though we added it
14639 - Check return values from pthread_mutex functions.
14640 - Don't save non-general-purpose router descriptors to the disk cache,
14641 because we have no way of remembering what their purpose was when
14643 - Add even more asserts to hunt down bug 417.
14644 - Build without verbose warnings even on (not-yet-released) gcc 4.2.
14645 - Fix a possible (but very unlikely) bug in picking routers by bandwidth.
14646 Add a log message to confirm that it is in fact unlikely.
14648 o Minor bugfixes (controller):
14649 - Make 'getinfo fingerprint' return a 551 error if we're not a
14650 server, so we match what the control spec claims we do. Reported
14652 - Fix a typo in an error message when extendcircuit fails that
14653 caused us to not follow the \r\n-based delimiter protocol. Reported
14656 o Code simplifications and refactoring:
14657 - Stop passing around circuit_t and crypt_path_t pointers that are
14658 implicit in other procedure arguments.
14659 - Drop the old code to choke directory connections when the
14660 corresponding OR connections got full: thanks to the cell queue
14661 feature, OR conns don't get full any more.
14662 - Make dns_resolve() handle attaching connections to circuits
14663 properly, so the caller doesn't have to.
14664 - Rename wants_to_read and wants_to_write to read/write_blocked_on_bw.
14665 - Keep the connection array as a dynamic smartlist_t, rather than as
14666 a fixed-sized array. This is important, as the number of connections
14667 is becoming increasingly decoupled from the number of sockets.
14670 Changes in version 0.1.2.14 - 2007-05-25
14671 Tor 0.1.2.14 changes the addresses of two directory authorities (this
14672 change especially affects those who serve or use hidden services),
14673 and fixes several other crash- and security-related bugs.
14675 o Directory authority changes:
14676 - Two directory authorities (moria1 and moria2) just moved to new
14677 IP addresses. This change will particularly affect those who serve
14678 or use hidden services.
14680 o Major bugfixes (crashes):
14681 - If a directory server runs out of space in the connection table
14682 as it's processing a begin_dir request, it will free the exit stream
14683 but leave it attached to the circuit, leading to unpredictable
14684 behavior. (Reported by seeess, fixes bug 425.)
14685 - Fix a bug in dirserv_remove_invalid() that would cause authorities
14686 to corrupt memory under some really unlikely scenarios.
14687 - Tighten router parsing rules. (Bugs reported by Benedikt Boss.)
14688 - Avoid segfaults when reading from mmaped descriptor file. (Reported
14691 o Major bugfixes (security):
14692 - When choosing an entry guard for a circuit, avoid using guards
14693 that are in the same family as the chosen exit -- not just guards
14694 that are exactly the chosen exit. (Reported by lodger.)
14696 o Major bugfixes (resource management):
14697 - If a directory authority is down, skip it when deciding where to get
14698 networkstatus objects or descriptors. Otherwise we keep asking
14699 every 10 seconds forever. Fixes bug 384.
14700 - Count it as a failure if we fetch a valid network-status but we
14701 don't want to keep it. Otherwise we'll keep fetching it and keep
14702 not wanting to keep it. Fixes part of bug 422.
14703 - If all of our dirservers have given us bad or no networkstatuses
14704 lately, then stop hammering them once per minute even when we
14705 think they're failed. Fixes another part of bug 422.
14708 - Actually set the purpose correctly for descriptors inserted with
14709 purpose=controller.
14710 - When we have k non-v2 authorities in our DirServer config,
14711 we ignored the last k authorities in the list when updating our
14713 - Correctly back-off from requesting router descriptors that we are
14714 having a hard time downloading.
14715 - Read resolv.conf files correctly on platforms where read() returns
14716 partial results on small file reads.
14717 - Don't rebuild the entire router store every time we get 32K of
14718 routers: rebuild it when the journal gets very large, or when
14719 the gaps in the store get very large.
14722 - When routers publish SVN revisions in their router descriptors,
14723 authorities now include those versions correctly in networkstatus
14725 - Warn when using a version of libevent before 1.3b to run a server on
14726 OSX or BSD: these versions interact badly with userspace threads.
14729 Changes in version 0.1.2.13 - 2007-04-24
14730 This release features some major anonymity fixes, such as safer path
14731 selection; better client performance; faster bootstrapping, better
14732 address detection, and better DNS support for servers; write limiting as
14733 well as read limiting to make servers easier to run; and a huge pile of
14734 other features and bug fixes. The bundles also ship with Vidalia 0.0.11.
14736 Tor 0.1.2.13 is released in memory of Rob Levin (1955-2006), aka lilo
14737 of the Freenode IRC network, remembering his patience and vision for
14738 free speech on the Internet.
14741 - Fix a memory leak when we ask for "all" networkstatuses and we
14742 get one we don't recognize.
14743 - Add more asserts to hunt down bug 417.
14744 - Disable kqueue on OS X 10.3 and earlier, to fix bug 371.
14747 Changes in version 0.1.2.12-rc - 2007-03-16
14749 - Fix an infinite loop introduced in 0.1.2.7-alpha when we serve
14750 directory information requested inside Tor connections (i.e. via
14751 begin_dir cells). It only triggered when the same connection was
14752 serving other data at the same time. Reported by seeess.
14755 - When creating a circuit via the controller, send a 'launched'
14756 event when we're done, so we follow the spec better.
14759 Changes in version 0.1.2.11-rc - 2007-03-15
14760 o Minor bugfixes (controller), reported by daejees:
14761 - Correct the control spec to match how the code actually responds
14762 to 'getinfo addr-mappings/*'.
14763 - The control spec described a GUARDS event, but the code
14764 implemented a GUARD event. Standardize on GUARD, but let people
14765 ask for GUARDS too.
14768 Changes in version 0.1.2.10-rc - 2007-03-07
14769 o Major bugfixes (Windows):
14770 - Do not load the NT services library functions (which may not exist)
14771 just to detect if we're a service trying to shut down. Now we run
14772 on Win98 and friends again.
14774 o Minor bugfixes (other):
14775 - Clarify a couple of log messages.
14776 - Fix a misleading socks5 error number.
14779 Changes in version 0.1.2.9-rc - 2007-03-02
14780 o Major bugfixes (Windows):
14781 - On MinGW, use "%I64u" to printf/scanf 64-bit integers, instead
14782 of the usual GCC "%llu". This prevents a bug when saving 64-bit
14783 int configuration values: the high-order 32 bits would get
14784 truncated. In particular, we were being bitten by the default
14785 MaxAdvertisedBandwidth of 128 TB turning into 0. (Fixes bug 400
14786 and maybe also bug 397.)
14788 o Minor bugfixes (performance):
14789 - Use OpenSSL's AES implementation on platforms where it's faster.
14790 This could save us as much as 10% CPU usage.
14792 o Minor bugfixes (server):
14793 - Do not rotate onion key immediately after setting it for the first
14796 o Minor bugfixes (directory authorities):
14797 - Stop calling servers that have been hibernating for a long time
14798 "stable". Also, stop letting hibernating or obsolete servers affect
14799 uptime and bandwidth cutoffs.
14800 - Stop listing hibernating servers in the v1 directory.
14802 o Minor bugfixes (hidden services):
14803 - Upload hidden service descriptors slightly less often, to reduce
14804 load on authorities.
14806 o Minor bugfixes (other):
14807 - Fix an assert that could trigger if a controller quickly set then
14808 cleared EntryNodes. Bug found by Udo van den Heuvel.
14809 - On architectures where sizeof(int)>4, still clamp declarable bandwidth
14811 - Fix a potential race condition in the rpm installer. Found by
14813 - Try to fix eventdns warnings once and for all: do not treat a dns rcode
14814 of 2 as indicating that the server is completely bad; it sometimes
14815 means that the server is just bad for the request in question. (may fix
14816 the last of bug 326.)
14817 - Disable encrypted directory connections when we don't have a server
14818 descriptor for the destination. We'll get this working again in
14822 Changes in version 0.1.2.8-beta - 2007-02-26
14823 o Major bugfixes (crashes):
14824 - Stop crashing when the controller asks us to resetconf more than
14825 one config option at once. (Vidalia 0.0.11 does this.)
14826 - Fix a crash that happened on Win98 when we're given command-line
14827 arguments: don't try to load NT service functions from advapi32.dll
14828 except when we need them. (Bug introduced in 0.1.2.7-alpha;
14830 - Fix a longstanding obscure crash bug that could occur when
14831 we run out of DNS worker processes. (Resolves bug 390.)
14833 o Major bugfixes (hidden services):
14834 - Correctly detect whether hidden service descriptor downloads are
14835 in-progress. (Suggested by Karsten Loesing; fixes bug 399.)
14837 o Major bugfixes (accounting):
14838 - When we start during an accounting interval before it's time to wake
14839 up, remember to wake up at the correct time. (May fix bug 342.)
14841 o Minor bugfixes (controller):
14842 - Give the controller END_STREAM_REASON_DESTROY events _before_ we
14843 clear the corresponding on_circuit variable, and remember later
14844 that we don't need to send a redundant CLOSED event. Resolves part
14846 - Report events where a resolve succeeded or where we got a socks
14847 protocol error correctly, rather than calling both of them
14849 - Change reported stream target addresses to IP consistently when
14850 we finally get the IP from an exit node.
14851 - Send log messages to the controller even if they happen to be very
14854 o Minor bugfixes (other):
14855 - Display correct results when reporting which versions are
14856 recommended, and how recommended they are. (Resolves bug 383.)
14857 - Improve our estimates for directory bandwidth to be less random:
14858 guess that an unrecognized directory will have the average bandwidth
14859 from all known directories, not that it will have the average
14860 bandwidth from those directories earlier than it on the list.
14861 - If we start a server with ClientOnly 1, then set ClientOnly to 0
14862 and hup, stop triggering an assert based on an empty onion_key.
14863 - On platforms with no working mmap() equivalent, don't warn the
14864 user when cached-routers doesn't exist.
14865 - Warn the user when mmap() [or its equivalent] fails for some reason
14866 other than file-not-found.
14867 - Don't warn the user when cached-routers.new doesn't exist: that's
14868 perfectly fine when starting up for the first time.
14869 - When EntryNodes are configured, rebuild the guard list to contain,
14870 in order: the EntryNodes that were guards before; the rest of the
14871 EntryNodes; the nodes that were guards before.
14872 - Mask out all signals in sub-threads; only the libevent signal
14873 handler should be processing them. This should prevent some crashes
14874 on some machines using pthreads. (Patch from coderman.)
14875 - Fix switched arguments on memset in the implementation of
14876 tor_munmap() for systems with no mmap() call.
14877 - When Tor receives a router descriptor that it asked for, but
14878 no longer wants (because it has received fresh networkstatuses
14879 in the meantime), do not warn the user. Cache the descriptor if
14880 we're a cache; drop it if we aren't.
14881 - Make earlier entry guards _really_ get retried when the network
14883 - On a malformed DNS reply, always give an error to the corresponding
14885 - Build with recent libevents on platforms that do not define the
14886 nonstandard types "u_int8_t" and friends.
14888 o Minor features (controller):
14889 - Warn the user when an application uses the obsolete binary v0
14890 control protocol. We're planning to remove support for it during
14891 the next development series, so it's good to give people some
14893 - Add STREAM_BW events to report per-entry-stream bandwidth
14894 use. (Patch from Robert Hogan.)
14895 - Rate-limit SIGNEWNYM signals in response to controllers that
14896 impolitely generate them for every single stream. (Patch from
14897 mwenge; closes bug 394.)
14898 - Make REMAP stream events have a SOURCE (cache or exit), and
14899 make them generated in every case where we get a successful
14900 connected or resolved cell.
14902 o Minor bugfixes (performance):
14903 - Call router_have_min_dir_info half as often. (This is showing up in
14904 some profiles, but not others.)
14905 - When using GCC, make log_debug never get called at all, and its
14906 arguments never get evaluated, when no debug logs are configured.
14907 (This is showing up in some profiles, but not others.)
14910 - Remove some never-implemented options. Mark PathlenCoinWeight as
14912 - Implement proposal 106: Stop requiring clients to have well-formed
14913 certificates; stop checking nicknames in certificates. (Clients
14914 have certificates so that they can look like Tor servers, but in
14915 the future we might want to allow them to look like regular TLS
14916 clients instead. Nicknames in certificates serve no purpose other
14917 than making our protocol easier to recognize on the wire.)
14918 - Revise messages on handshake failure again to be even more clear about
14919 which are incoming connections and which are outgoing.
14920 - Discard any v1 directory info that's over 1 month old (for
14921 directories) or over 1 week old (for running-routers lists).
14922 - Do not warn when individual nodes in the configuration's EntryNodes,
14923 ExitNodes, etc are down: warn only when all possible nodes
14924 are down. (Fixes bug 348.)
14925 - Always remove expired routers and networkstatus docs before checking
14926 whether we have enough information to build circuits. (Fixes
14928 - Put a lower-bound on MaxAdvertisedBandwidth.
14931 Changes in version 0.1.2.7-alpha - 2007-02-06
14932 o Major bugfixes (rate limiting):
14933 - Servers decline directory requests much more aggressively when
14934 they're low on bandwidth. Otherwise they end up queueing more and
14935 more directory responses, which can't be good for latency.
14936 - But never refuse directory requests from local addresses.
14937 - Fix a memory leak when sending a 503 response for a networkstatus
14939 - Be willing to read or write on local connections (e.g. controller
14940 connections) even when the global rate limiting buckets are empty.
14941 - If our system clock jumps back in time, don't publish a negative
14942 uptime in the descriptor. Also, don't let the global rate limiting
14943 buckets go absurdly negative.
14944 - Flush local controller connection buffers periodically as we're
14945 writing to them, so we avoid queueing 4+ megabytes of data before
14948 o Major bugfixes (NT services):
14949 - Install as NT_AUTHORITY\LocalService rather than as SYSTEM; add a
14950 command-line flag so that admins can override the default by saying
14951 "tor --service install --user "SomeUser"". This will not affect
14952 existing installed services. Also, warn the user that the service
14953 will look for its configuration file in the service user's
14954 %appdata% directory. (We can't do the 'hardwire the user's appdata
14955 directory' trick any more, since we may not have read access to that
14958 o Major bugfixes (other):
14959 - Previously, we would cache up to 16 old networkstatus documents
14960 indefinitely, if they came from nontrusted authorities. Now we
14961 discard them if they are more than 10 days old.
14962 - Fix a crash bug in the presence of DNS hijacking (reported by Andrew
14964 - Detect and reject malformed DNS responses containing circular
14966 - If exits are rare enough that we're not marking exits as guards,
14967 ignore exit bandwidth when we're deciding the required bandwidth
14969 - When we're handling a directory connection tunneled over Tor,
14970 don't fill up internal memory buffers with all the data we want
14971 to tunnel; instead, only add it if the OR connection that will
14972 eventually receive it has some room for it. (This can lead to
14973 slowdowns in tunneled dir connections; a better solution will have
14974 to wait for 0.2.0.)
14976 o Minor bugfixes (dns):
14977 - Add some defensive programming to eventdns.c in an attempt to catch
14978 possible memory-stomping bugs.
14979 - Detect and reject DNS replies containing IPv4 or IPv6 records with
14980 an incorrect number of bytes. (Previously, we would ignore the
14982 - Fix as-yet-unused reverse IPv6 lookup code so it sends nybbles
14983 in the correct order, and doesn't crash.
14984 - Free memory held in recently-completed DNS lookup attempts on exit.
14985 This was not a memory leak, but may have been hiding memory leaks.
14986 - Handle TTL values correctly on reverse DNS lookups.
14987 - Treat failure to parse resolv.conf as an error.
14989 o Minor bugfixes (other):
14990 - Fix crash with "tor --list-fingerprint" (reported by seeess).
14991 - When computing clock skew from directory HTTP headers, consider what
14992 time it was when we finished asking for the directory, not what
14994 - Expire socks connections if they spend too long waiting for the
14995 handshake to finish. Previously we would let them sit around for
14996 days, if the connecting application didn't close them either.
14997 - And if the socks handshake hasn't started, don't send a
14998 "DNS resolve socks failed" handshake reply; just close it.
14999 - Stop using C functions that OpenBSD's linker doesn't like.
15000 - Don't launch requests for descriptors unless we have networkstatuses
15001 from at least half of the authorities. This delays the first
15002 download slightly under pathological circumstances, but can prevent
15003 us from downloading a bunch of descriptors we don't need.
15004 - Do not log IPs with TLS failures for incoming TLS
15005 connections. (Fixes bug 382.)
15006 - If the user asks to use invalid exit nodes, be willing to use
15008 - Stop using the reserved ac_cv namespace in our configure script.
15009 - Call stat() slightly less often; use fstat() when possible.
15010 - Refactor the way we handle pending circuits when an OR connection
15011 completes or fails, in an attempt to fix a rare crash bug.
15012 - Only rewrite a conn's address based on X-Forwarded-For: headers
15013 if it's a parseable public IP address; and stop adding extra quotes
15014 to the resulting address.
15017 - Weight directory requests by advertised bandwidth. Now we can
15018 let servers enable write limiting but still allow most clients to
15019 succeed at their directory requests. (We still ignore weights when
15020 choosing a directory authority; I hope this is a feature.)
15023 - Create a new file ReleaseNotes which was the old ChangeLog. The
15024 new ChangeLog file now includes the summaries for all development
15026 - Check for addresses with invalid characters at the exit as well
15027 as at the client, and warn less verbosely when they fail. You can
15028 override this by setting ServerDNSAllowNonRFC953Addresses to 1.
15029 - Adapt a patch from goodell to let the contrib/exitlist script
15030 take arguments rather than require direct editing.
15031 - Inform the server operator when we decide not to advertise a
15032 DirPort due to AccountingMax enabled or a low BandwidthRate. It
15033 was confusing Zax, so now we're hopefully more helpful.
15034 - Bring us one step closer to being able to establish an encrypted
15035 directory tunnel without knowing a descriptor first. Still not
15036 ready yet. As part of the change, now assume we can use a
15037 create_fast cell if we don't know anything about a router.
15038 - Allow exit nodes to use nameservers running on ports other than 53.
15039 - Servers now cache reverse DNS replies.
15040 - Add an --ignore-missing-torrc command-line option so that we can
15041 get the "use sensible defaults if the configuration file doesn't
15042 exist" behavior even when specifying a torrc location on the command
15045 o Minor features (controller):
15046 - Track reasons for OR connection failure; make these reasons
15047 available via the controller interface. (Patch from Mike Perry.)
15048 - Add a SOCKS_BAD_HOSTNAME client status event so controllers
15049 can learn when clients are sending malformed hostnames to Tor.
15050 - Clean up documentation for controller status events.
15051 - Add a REMAP status to stream events to note that a stream's
15052 address has changed because of a cached address or a MapAddress
15056 Changes in version 0.1.2.6-alpha - 2007-01-09
15058 - Fix an assert error introduced in 0.1.2.5-alpha: if a single TLS
15059 connection handles more than 4 gigs in either direction, we crash.
15060 - Fix an assert error introduced in 0.1.2.5-alpha: if we're an
15061 advertised exit node, somebody might try to exit from us when
15062 we're bootstrapping and before we've built our descriptor yet.
15063 Refuse the connection rather than crashing.
15066 - Warn if we (as a server) find that we've resolved an address that we
15067 weren't planning to resolve.
15068 - Warn that using select() on any libevent version before 1.1 will be
15069 unnecessarily slow (even for select()).
15070 - Flush ERR-level controller status events just like we currently
15071 flush ERR-level log events, so that a Tor shutdown doesn't prevent
15072 the controller from learning about current events.
15074 o Minor features (more controller status events):
15075 - Implement EXTERNAL_ADDRESS server status event so controllers can
15076 learn when our address changes.
15077 - Implement BAD_SERVER_DESCRIPTOR server status event so controllers
15078 can learn when directories reject our descriptor.
15079 - Implement SOCKS_UNKNOWN_PROTOCOL client status event so controllers
15080 can learn when a client application is speaking a non-socks protocol
15082 - Implement DANGEROUS_SOCKS client status event so controllers
15083 can learn when a client application is leaking DNS addresses.
15084 - Implement BUG general status event so controllers can learn when
15085 Tor is unhappy about its internal invariants.
15086 - Implement CLOCK_SKEW general status event so controllers can learn
15087 when Tor thinks the system clock is set incorrectly.
15088 - Implement GOOD_SERVER_DESCRIPTOR and ACCEPTED_SERVER_DESCRIPTOR
15089 server status events so controllers can learn when their descriptors
15090 are accepted by a directory.
15091 - Implement CHECKING_REACHABILITY and REACHABILITY_{SUCCEEDED|FAILED}
15092 server status events so controllers can learn about Tor's progress in
15093 deciding whether it's reachable from the outside.
15094 - Implement BAD_LIBEVENT general status event so controllers can learn
15095 when we have a version/method combination in libevent that needs to
15097 - Implement NAMESERVER_STATUS, NAMESERVER_ALL_DOWN, DNS_HIJACKED,
15098 and DNS_USELESS server status events so controllers can learn
15099 about changes to DNS server status.
15101 o Minor features (directory):
15102 - Authorities no longer recommend exits as guards if this would shift
15103 too much load to the exit nodes.
15106 Changes in version 0.1.2.5-alpha - 2007-01-06
15108 - Enable write limiting as well as read limiting. Now we sacrifice
15109 capacity if we're pushing out lots of directory traffic, rather
15110 than overrunning the user's intended bandwidth limits.
15111 - Include TLS overhead when counting bandwidth usage; previously, we
15112 would count only the bytes sent over TLS, but not the bytes used
15114 - Support running the Tor service with a torrc not in the same
15115 directory as tor.exe and default to using the torrc located in
15116 the %appdata%\Tor\ of the user who installed the service. Patch
15118 - Servers now check for the case when common DNS requests are going to
15119 wildcarded addresses (i.e. all getting the same answer), and change
15120 their exit policy to reject *:* if it's happening.
15121 - Implement BEGIN_DIR cells, so we can connect to the directory
15122 server via TLS to do encrypted directory requests rather than
15123 plaintext. Enable via the TunnelDirConns and PreferTunneledDirConns
15124 config options if you like.
15126 o Minor features (config and docs):
15127 - Start using the state file to store bandwidth accounting data:
15128 the bw_accounting file is now obsolete. We'll keep generating it
15129 for a while for people who are still using 0.1.2.4-alpha.
15130 - Try to batch changes to the state file so that we do as few
15131 disk writes as possible while still storing important things in
15133 - The state file and the bw_accounting file get saved less often when
15134 the AvoidDiskWrites config option is set.
15135 - Make PIDFile work on Windows (untested).
15136 - Add internal descriptions for a bunch of configuration options:
15137 accessible via controller interface and in comments in saved
15139 - Reject *:563 (NNTPS) in the default exit policy. We already reject
15140 NNTP by default, so this seems like a sensible addition.
15141 - Clients now reject hostnames with invalid characters. This should
15142 avoid some inadvertent info leaks. Add an option
15143 AllowNonRFC953Hostnames to disable this behavior, in case somebody
15144 is running a private network with hosts called @, !, and #.
15145 - Add a maintainer script to tell us which options are missing
15146 documentation: "make check-docs".
15147 - Add a new address-spec.txt document to describe our special-case
15148 addresses: .exit, .onion, and .noconnnect.
15150 o Minor features (DNS):
15151 - Ongoing work on eventdns infrastructure: now it has dns server
15152 and ipv6 support. One day Tor will make use of it.
15153 - Add client-side caching for reverse DNS lookups.
15154 - Add support to tor-resolve tool for reverse lookups and SOCKS5.
15155 - When we change nameservers or IP addresses, reset and re-launch
15156 our tests for DNS hijacking.
15158 o Minor features (directory):
15159 - Authorities now specify server versions in networkstatus. This adds
15160 about 2% to the size of compressed networkstatus docs, and allows
15161 clients to tell which servers support BEGIN_DIR and which don't.
15162 The implementation is forward-compatible with a proposed future
15163 protocol version scheme not tied to Tor versions.
15164 - DirServer configuration lines now have an orport= option so
15165 clients can open encrypted tunnels to the authorities without
15166 having downloaded their descriptors yet. Enabled for moria1,
15167 moria2, tor26, and lefkada now in the default configuration.
15168 - Directory servers are more willing to send a 503 "busy" if they
15169 are near their write limit, especially for v1 directory requests.
15170 Now they can use their limited bandwidth for actual Tor traffic.
15171 - Clients track responses with status 503 from dirservers. After a
15172 dirserver has given us a 503, we try not to use it until an hour has
15173 gone by, or until we have no dirservers that haven't given us a 503.
15174 - When we get a 503 from a directory, and we're not a server, we don't
15175 count the failure against the total number of failures allowed
15176 for the thing we're trying to download.
15177 - Report X-Your-Address-Is correctly from tunneled directory
15178 connections; don't report X-Your-Address-Is when it's an internal
15179 address; and never believe reported remote addresses when they're
15181 - Protect against an unlikely DoS attack on directory servers.
15182 - Add a BadDirectory flag to network status docs so that authorities
15183 can (eventually) tell clients about caches they believe to be
15186 o Minor features (controller):
15187 - Have GETINFO dir/status/* work on hosts with DirPort disabled.
15188 - Reimplement GETINFO so that info/names stays in sync with the
15190 - Implement "GETINFO fingerprint".
15191 - Implement "SETEVENTS GUARD" so controllers can get updates on
15192 entry guard status as it changes.
15194 o Minor features (clean up obsolete pieces):
15195 - Remove some options that have been deprecated since at least
15196 0.1.0.x: AccountingMaxKB, LogFile, DebugLogFile, LogLevel, and
15197 SysLog. Use AccountingMax instead of AccountingMaxKB, and use Log
15198 to set log options.
15199 - We no longer look for identity and onion keys in "identity.key" and
15200 "onion.key" -- these were replaced by secret_id_key and
15201 secret_onion_key in 0.0.8pre1.
15202 - We no longer require unrecognized directory entries to be
15205 o Major bugfixes (security):
15206 - Stop sending the HttpProxyAuthenticator string to directory
15207 servers when directory connections are tunnelled through Tor.
15208 - Clients no longer store bandwidth history in the state file.
15209 - Do not log introduction points for hidden services if SafeLogging
15211 - When generating bandwidth history, round down to the nearest
15212 1k. When storing accounting data, round up to the nearest 1k.
15213 - When we're running as a server, remember when we last rotated onion
15214 keys, so that we will rotate keys once they're a week old even if
15215 we never stay up for a week ourselves.
15217 o Major bugfixes (other):
15218 - Fix a longstanding bug in eventdns that prevented the count of
15219 timed-out resolves from ever being reset. This bug caused us to
15220 give up on a nameserver the third time it timed out, and try it
15221 10 seconds later... and to give up on it every time it timed out
15223 - Take out the '5 second' timeout from the connection retry
15224 schedule. Now the first connect attempt will wait a full 10
15225 seconds before switching to a new circuit. Perhaps this will help
15226 a lot. Based on observations from Mike Perry.
15227 - Fix a bug on the Windows implementation of tor_mmap_file() that
15228 would prevent the cached-routers file from ever loading. Reported
15232 - Fix an assert failure when a directory authority sets
15233 AuthDirRejectUnlisted and then receives a descriptor from an
15234 unlisted router. Reported by seeess.
15235 - Avoid a double-free when parsing malformed DirServer lines.
15236 - Fix a bug when a BSD-style PF socket is first used. Patch from
15238 - Fix a bug in 0.1.2.2-alpha that prevented clients from asking
15239 to resolve an address at a given exit node even when they ask for
15241 - Servers no longer ever list themselves in their "family" line,
15242 even if configured to do so. This makes it easier to configure
15243 family lists conveniently.
15244 - When running as a server, don't fall back to 127.0.0.1 when no
15245 nameservers are configured in /etc/resolv.conf; instead, make the
15246 user fix resolv.conf or specify nameservers explicitly. (Resolves
15248 - Stop accepting certain malformed ports in configured exit policies.
15249 - Don't re-write the fingerprint file every restart, unless it has
15251 - Stop warning when a single nameserver fails: only warn when _all_ of
15252 our nameservers have failed. Also, when we only have one nameserver,
15253 raise the threshold for deciding that the nameserver is dead.
15254 - Directory authorities now only decide that routers are reachable
15255 if their identity keys are as expected.
15256 - When the user uses bad syntax in the Log config line, stop
15257 suggesting other bad syntax as a replacement.
15258 - Correctly detect ipv6 DNS capability on OpenBSD.
15260 o Minor bugfixes (controller):
15261 - Report the circuit number correctly in STREAM CLOSED events. Bug
15262 reported by Mike Perry.
15263 - Do not report bizarre values for results of accounting GETINFOs
15264 when the last second's write or read exceeds the allotted bandwidth.
15265 - Report "unrecognized key" rather than an empty string when the
15266 controller tries to fetch a networkstatus that doesn't exist.
15269 Changes in version 0.1.1.26 - 2006-12-14
15270 o Security bugfixes:
15271 - Stop sending the HttpProxyAuthenticator string to directory
15272 servers when directory connections are tunnelled through Tor.
15273 - Clients no longer store bandwidth history in the state file.
15274 - Do not log introduction points for hidden services if SafeLogging
15278 - Fix an assert failure when a directory authority sets
15279 AuthDirRejectUnlisted and then receives a descriptor from an
15280 unlisted router (reported by seeess).
15283 Changes in version 0.1.2.4-alpha - 2006-12-03
15285 - Add support for using natd; this allows FreeBSDs earlier than
15286 5.1.2 to have ipfw send connections through Tor without using
15287 SOCKS. (Patch from Zajcev Evgeny with tweaks from tup.)
15290 - Make all connections to addresses of the form ".noconnect"
15291 immediately get closed. This lets application/controller combos
15292 successfully test whether they're talking to the same Tor by
15293 watching for STREAM events.
15294 - Make cross.sh cross-compilation script work even when autogen.sh
15295 hasn't been run. (Patch from Michael Mohr.)
15296 - Statistics dumped by -USR2 now include a breakdown of public key
15297 operations, for profiling.
15300 - Fix a major leak when directory authorities parse their
15301 approved-routers list, a minor memory leak when we fail to pick
15302 an exit node, and a few rare leaks on errors.
15303 - Handle TransPort connections even when the server sends data before
15304 the client sends data. Previously, the connection would just hang
15305 until the client sent data. (Patch from tup based on patch from
15307 - Avoid assert failure when our cached-routers file is empty on
15311 - Don't log spurious warnings when we see a circuit close reason we
15312 don't recognize; it's probably just from a newer version of Tor.
15313 - Have directory authorities allow larger amounts of drift in uptime
15314 without replacing the server descriptor: previously, a server that
15315 restarted every 30 minutes could have 48 "interesting" descriptors
15317 - Start linking to the Tor specification and Tor reference manual
15318 correctly in the Windows installer.
15319 - Add Vidalia to the OS X uninstaller script, so when we uninstall
15320 Tor/Privoxy we also uninstall Vidalia.
15321 - Resume building on Irix64, and fix a lot of warnings from its
15322 MIPSpro C compiler.
15323 - Don't corrupt last_guessed_ip in router_new_address_suggestion()
15324 when we're running as a client.
15327 Changes in version 0.1.1.25 - 2006-11-04
15329 - When a client asks us to resolve (rather than connect to)
15330 an address, and we have a cached answer, give them the cached
15331 answer. Previously, we would give them no answer at all.
15332 - We were building exactly the wrong circuits when we predict
15333 hidden service requirements, meaning Tor would have to build all
15334 its circuits on demand.
15335 - If none of our live entry guards have a high uptime, but we
15336 require a guard with a high uptime, try adding a new guard before
15337 we give up on the requirement. This patch should make long-lived
15338 connections more stable on average.
15339 - When testing reachability of our DirPort, don't launch new
15340 tests when there's already one in progress -- unreachable
15341 servers were stacking up dozens of testing streams.
15343 o Security bugfixes:
15344 - When the user sends a NEWNYM signal, clear the client-side DNS
15345 cache too. Otherwise we continue to act on previous information.
15348 - Avoid a memory corruption bug when creating a hash table for
15350 - Avoid possibility of controller-triggered crash when misusing
15351 certain commands from a v0 controller on platforms that do not
15352 handle printf("%s",NULL) gracefully.
15353 - Avoid infinite loop on unexpected controller input.
15354 - Don't log spurious warnings when we see a circuit close reason we
15355 don't recognize; it's probably just from a newer version of Tor.
15356 - Add Vidalia to the OS X uninstaller script, so when we uninstall
15357 Tor/Privoxy we also uninstall Vidalia.
15360 Changes in version 0.1.2.3-alpha - 2006-10-29
15362 - Prepare for servers to publish descriptors less often: never
15363 discard a descriptor simply for being too old until either it is
15364 recommended by no authorities, or until we get a better one for
15365 the same router. Make caches consider retaining old recommended
15366 routers for even longer.
15367 - If most authorities set a BadExit flag for a server, clients
15368 don't think of it as a general-purpose exit. Clients only consider
15369 authorities that advertise themselves as listing bad exits.
15370 - Directory servers now provide 'Pragma: no-cache' and 'Expires'
15371 headers for content, so that we can work better in the presence of
15372 caching HTTP proxies.
15373 - Allow authorities to list nodes as bad exits by fingerprint or by
15376 o Minor features, controller:
15377 - Add a REASON field to CIRC events; for backward compatibility, this
15378 field is sent only to controllers that have enabled the extended
15379 event format. Also, add additional reason codes to explain why
15380 a given circuit has been destroyed or truncated. (Patches from
15382 - Add a REMOTE_REASON field to extended CIRC events to tell the
15383 controller about why a remote OR told us to close a circuit.
15384 - Stream events also now have REASON and REMOTE_REASON fields,
15385 working much like those for circuit events.
15386 - There's now a GETINFO ns/... field so that controllers can ask Tor
15387 about the current status of a router.
15388 - A new event type "NS" to inform a controller when our opinion of
15389 a router's status has changed.
15390 - Add a GETINFO events/names and GETINFO features/names so controllers
15391 can tell which events and features are supported.
15392 - A new CLEARDNSCACHE signal to allow controllers to clear the
15393 client-side DNS cache without expiring circuits.
15395 o Security bugfixes:
15396 - When the user sends a NEWNYM signal, clear the client-side DNS
15397 cache too. Otherwise we continue to act on previous information.
15400 - Avoid sending junk to controllers or segfaulting when a controller
15401 uses EVENT_NEW_DESC with verbose nicknames.
15402 - Stop triggering asserts if the controller tries to extend hidden
15403 service circuits (reported by mwenge).
15404 - Avoid infinite loop on unexpected controller input.
15405 - When the controller does a "GETINFO network-status", tell it
15406 about even those routers whose descriptors are very old, and use
15407 long nicknames where appropriate.
15408 - Change NT service functions to be loaded on demand. This lets us
15409 build with MinGW without breaking Tor for Windows 98 users.
15410 - Do DirPort reachability tests less often, since a single test
15411 chews through many circuits before giving up.
15412 - In the hidden service example in torrc.sample, stop recommending
15413 esoteric and discouraged hidden service options.
15414 - When stopping an NT service, wait up to 10 sec for it to actually
15415 stop. Patch from Matt Edman; resolves bug 295.
15416 - Fix handling of verbose nicknames with ORCONN controller events:
15417 make them show up exactly when requested, rather than exactly when
15419 - When reporting verbose nicknames in entry_guards_getinfo(), avoid
15420 printing a duplicate "$" in the keys we send (reported by mwenge).
15421 - Correctly set maximum connection limit on Cygwin. (This time
15423 - Try to detect Windows correctly when cross-compiling.
15424 - Detect the size of the routers file correctly even if it is
15425 corrupted (on systems without mmap) or not page-aligned (on systems
15426 with mmap). This bug was harmless.
15427 - Sometimes we didn't bother sending a RELAY_END cell when an attempt
15428 to open a stream fails; now we do in more cases. This should
15429 make clients able to find a good exit faster in some cases, since
15430 unhandleable requests will now get an error rather than timing out.
15431 - Resolve two memory leaks when rebuilding the on-disk router cache
15432 (reported by fookoowa).
15433 - Clean up minor code warnings suggested by the MIPSpro C compiler,
15434 and reported by some Centos users.
15435 - Controller signals now work on non-Unix platforms that don't define
15436 SIGUSR1 and SIGUSR2 the way we expect.
15437 - Patch from Michael Mohr to contrib/cross.sh, so it checks more
15438 values before failing, and always enables eventdns.
15439 - Libevent-1.2 exports, but does not define in its headers, strlcpy.
15440 Try to fix this in configure.in by checking for most functions
15441 before we check for libevent.
15444 Changes in version 0.1.2.2-alpha - 2006-10-07
15446 - Make our async eventdns library on-by-default for Tor servers,
15447 and plan to deprecate the separate dnsworker threads.
15448 - Add server-side support for "reverse" DNS lookups (using PTR
15449 records so clients can determine the canonical hostname for a given
15450 IPv4 address). Only supported by servers using eventdns; servers
15451 now announce in their descriptors whether they support eventdns.
15452 - Specify and implement client-side SOCKS5 interface for reverse DNS
15453 lookups (see doc/socks-extensions.txt).
15454 - Add a BEGIN_DIR relay cell type for an easier in-protocol way to
15455 connect to directory servers through Tor. Previously, clients needed
15456 to find Tor exits to make private connections to directory servers.
15457 - Avoid choosing Exit nodes for entry or middle hops when the
15458 total bandwidth available from non-Exit nodes is much higher than
15459 the total bandwidth available from Exit nodes.
15460 - Workaround for name servers (like Earthlink's) that hijack failing
15461 DNS requests and replace the no-such-server answer with a "helpful"
15462 redirect to an advertising-driven search portal. Also work around
15463 DNS hijackers who "helpfully" decline to hijack known-invalid
15464 RFC2606 addresses. Config option "ServerDNSDetectHijacking 0"
15465 lets you turn it off.
15466 - Send out a burst of long-range padding cells once we've established
15467 that we're reachable. Spread them over 4 circuits, so hopefully
15468 a few will be fast. This exercises our bandwidth and bootstraps
15469 us into the directory more quickly.
15471 o New/improved config options:
15472 - Add new config option "ResolvConf" to let the server operator
15473 choose an alternate resolve.conf file when using eventdns.
15474 - Add an "EnforceDistinctSubnets" option to control our "exclude
15475 servers on the same /16" behavior. It's still on by default; this
15476 is mostly for people who want to operate private test networks with
15477 all the machines on the same subnet.
15478 - If one of our entry guards is on the ExcludeNodes list, or the
15479 directory authorities don't think it's a good guard, treat it as
15480 if it were unlisted: stop using it as a guard, and throw it off
15481 the guards list if it stays that way for a long time.
15482 - Allow directory authorities to be marked separately as authorities
15483 for the v1 directory protocol, the v2 directory protocol, and
15484 as hidden service directories, to make it easier to retire old
15485 authorities. V1 authorities should set "HSAuthoritativeDir 1"
15486 to continue being hidden service authorities too.
15487 - Remove 8888 as a LongLivedPort, and add 6697 (IRCS).
15489 o Minor features, controller:
15490 - Fix CIRC controller events so that controllers can learn the
15491 identity digests of non-Named servers used in circuit paths.
15492 - Let controllers ask for more useful identifiers for servers. Instead
15493 of learning identity digests for un-Named servers and nicknames
15494 for Named servers, the new identifiers include digest, nickname,
15495 and indication of Named status. Off by default; see control-spec.txt
15496 for more information.
15497 - Add a "getinfo address" controller command so it can display Tor's
15498 best guess to the user.
15499 - New controller event to alert the controller when our server
15500 descriptor has changed.
15501 - Give more meaningful errors on controller authentication failure.
15503 o Minor features, other:
15504 - When asked to resolve a hostname, don't use non-exit servers unless
15505 requested to do so. This allows servers with broken DNS to be
15506 useful to the network.
15507 - Divide eventdns log messages into warn and info messages.
15508 - Reserve the nickname "Unnamed" for routers that can't pick
15509 a hostname: any router can call itself Unnamed; directory
15510 authorities will never allocate Unnamed to any particular router;
15511 clients won't believe that any router is the canonical Unnamed.
15512 - Only include function names in log messages for info/debug messages.
15513 For notice/warn/err, the content of the message should be clear on
15514 its own, and printing the function name only confuses users.
15515 - Avoid some false positives during reachability testing: don't try
15516 to test via a server that's on the same /24 as us.
15517 - If we fail to build a circuit to an intended enclave, and it's
15518 not mandatory that we use that enclave, stop wanting it.
15519 - When eventdns is enabled, allow multithreaded builds on NetBSD and
15520 OpenBSD. (We had previously disabled threads on these platforms
15521 because they didn't have working thread-safe resolver functions.)
15523 o Major bugfixes, anonymity/security:
15524 - If a client asked for a server by name, and there's a named server
15525 in our network-status but we don't have its descriptor yet, we
15526 could return an unnamed server instead.
15527 - Fix NetBSD bug that could allow someone to force uninitialized RAM
15528 to be sent to a server's DNS resolver. This only affects NetBSD
15529 and other platforms that do not bounds-check tolower().
15530 - Reject (most) attempts to use Tor circuits with length one. (If
15531 many people start using Tor as a one-hop proxy, exit nodes become
15532 a more attractive target for compromise.)
15533 - Just because your DirPort is open doesn't mean people should be
15534 able to remotely teach you about hidden service descriptors. Now
15535 only accept rendezvous posts if you've got HSAuthoritativeDir set.
15537 o Major bugfixes, other:
15538 - Don't crash on race condition in dns.c: tor_assert(!resolve->expire)
15539 - When a client asks the server to resolve (not connect to)
15540 an address, and it has a cached answer, give them the cached answer.
15541 Previously, the server would give them no answer at all.
15542 - Allow really slow clients to not hang up five minutes into their
15543 directory downloads (suggested by Adam J. Richter).
15544 - We were building exactly the wrong circuits when we anticipated
15545 hidden service requirements, meaning Tor would have to build all
15546 its circuits on demand.
15547 - Avoid crashing when we mmap a router cache file of size 0.
15548 - When testing reachability of our DirPort, don't launch new
15549 tests when there's already one in progress -- unreachable
15550 servers were stacking up dozens of testing streams.
15552 o Minor bugfixes, correctness:
15553 - If we're a directory mirror and we ask for "all" network status
15554 documents, we would discard status documents from authorities
15555 we don't recognize.
15556 - Avoid a memory corruption bug when creating a hash table for
15558 - Avoid controller-triggered crash when misusing certain commands
15559 from a v0 controller on platforms that do not handle
15560 printf("%s",NULL) gracefully.
15561 - Don't crash when a controller sends a third argument to an
15562 "extendcircuit" request.
15563 - Controller protocol fixes: fix encoding in "getinfo addr-mappings"
15564 response; fix error code when "getinfo dir/status/" fails.
15565 - Avoid crash when telling controller stream-status and a stream
15567 - Patch from Adam Langley to fix assert() in eventdns.c.
15568 - Fix a debug log message in eventdns to say "X resolved to Y"
15569 instead of "X resolved to X".
15570 - Make eventdns give strings for DNS errors, not just error numbers.
15571 - Track unreachable entry guards correctly: don't conflate
15572 'unreachable by us right now' with 'listed as down by the directory
15573 authorities'. With the old code, if a guard was unreachable by
15574 us but listed as running, it would clog our guard list forever.
15575 - Behave correctly in case we ever have a network with more than
15576 2GB/s total advertised capacity.
15577 - Make TrackExitHosts case-insensitive, and fix the behavior of
15578 ".suffix" TrackExitHosts items to avoid matching in the middle of
15580 - Finally fix the openssl warnings from newer gccs that believe that
15581 ignoring a return value is okay, but casting a return value and
15582 then ignoring it is a sign of madness.
15583 - Prevent the contrib/exitlist script from printing the same
15584 result more than once.
15585 - Patch from Steve Hildrey: Generate network status correctly on
15586 non-versioning dirservers.
15587 - Don't listen to the X-Your-Address-Is hint if you did the lookup
15588 via Tor; otherwise you'll think you're the exit node's IP address.
15590 o Minor bugfixes, performance:
15591 - Two small performance improvements on parsing descriptors.
15592 - Major performance improvement on inserting descriptors: change
15593 algorithm from O(n^2) to O(n).
15594 - Make the common memory allocation path faster on machines where
15595 malloc(0) returns a pointer.
15596 - Start remembering X-Your-Address-Is directory hints even if you're
15597 a client, so you can become a server more smoothly.
15598 - Avoid duplicate entries on MyFamily line in server descriptor.
15600 o Packaging, features:
15601 - Remove architecture from OS X builds. The official builds are
15602 now universal binaries.
15603 - The Debian package now uses --verify-config when (re)starting,
15604 to distinguish configuration errors from other errors.
15605 - Update RPMs to require libevent 1.1b.
15607 o Packaging, bugfixes:
15608 - Patches so Tor builds with MinGW on Windows.
15609 - Patches so Tor might run on Cygwin again.
15610 - Resume building on non-gcc compilers and ancient gcc. Resume
15611 building with the -O0 compile flag. Resume building cleanly on
15613 - Run correctly on OS X platforms with case-sensitive filesystems.
15614 - Correct includes for net/if.h and net/pfvar.h on OpenBSD (from Tup).
15615 - Add autoconf checks so Tor can build on Solaris x86 again.
15618 - Documented (and renamed) ServerDNSSearchDomains and
15619 ServerDNSResolvConfFile options.
15620 - Be clearer that the *ListenAddress directives can be repeated
15624 Changes in version 0.1.1.24 - 2006-09-29
15626 - Allow really slow clients to not hang up five minutes into their
15627 directory downloads (suggested by Adam J. Richter).
15628 - Fix major performance regression from 0.1.0.x: instead of checking
15629 whether we have enough directory information every time we want to
15630 do something, only check when the directory information has changed.
15631 This should improve client CPU usage by 25-50%.
15632 - Don't crash if, after a server has been running for a while,
15633 it can't resolve its hostname.
15636 - Allow Tor to start when RunAsDaemon is set but no logs are set.
15637 - Don't crash when the controller receives a third argument to an
15638 "extendcircuit" request.
15639 - Controller protocol fixes: fix encoding in "getinfo addr-mappings"
15640 response; fix error code when "getinfo dir/status/" fails.
15641 - Fix configure.in to not produce broken configure files with
15642 more recent versions of autoconf. Thanks to Clint for his auto*
15644 - Fix security bug on NetBSD that could allow someone to force
15645 uninitialized RAM to be sent to a server's DNS resolver. This
15646 only affects NetBSD and other platforms that do not bounds-check
15648 - Warn user when using libevent 1.1a or earlier with win32 or kqueue
15649 methods: these are known to be buggy.
15650 - If we're a directory mirror and we ask for "all" network status
15651 documents, we would discard status documents from authorities
15652 we don't recognize.
15655 Changes in version 0.1.2.1-alpha - 2006-08-27
15657 - Add "eventdns" async dns library from Adam Langley, tweaked to
15658 build on OSX and Windows. Only enabled if you pass the
15659 --enable-eventdns argument to configure.
15660 - Allow servers with no hostname or IP address to learn their
15661 IP address by asking the directory authorities. This code only
15662 kicks in when you would normally have exited with a "no address"
15663 error. Nothing's authenticated, so use with care.
15664 - Rather than waiting a fixed amount of time between retrying
15665 application connections, we wait only 5 seconds for the first,
15666 10 seconds for the second, and 15 seconds for each retry after
15667 that. Hopefully this will improve the expected user experience.
15668 - Patch from Tup to add support for transparent AP connections:
15669 this basically bundles the functionality of trans-proxy-tor
15670 into the Tor mainline. Now hosts with compliant pf/netfilter
15671 implementations can redirect TCP connections straight to Tor
15672 without diverting through SOCKS. Needs docs.
15673 - Busy directory servers save lots of memory by spooling server
15674 descriptors, v1 directories, and v2 networkstatus docs to buffers
15675 as needed rather than en masse. Also mmap the cached-routers
15676 files, so we don't need to keep the whole thing in memory too.
15677 - Automatically avoid picking more than one node from the same
15678 /16 network when constructing a circuit.
15679 - Revise and clean up the torrc.sample that we ship with; add
15680 a section for BandwidthRate and BandwidthBurst.
15683 - Split circuit_t into origin_circuit_t and or_circuit_t, and
15684 split connection_t into edge, or, dir, control, and base structs.
15685 These will save quite a bit of memory on busy servers, and they'll
15686 also help us track down bugs in the code and bugs in the spec.
15687 - Experimentally re-enable kqueue on OSX when using libevent 1.1b
15688 or later. Log when we are doing this, so we can diagnose it when
15689 it fails. (Also, recommend libevent 1.1b for kqueue and
15690 win32 methods; deprecate libevent 1.0b harder; make libevent
15691 recommendation system saner.)
15692 - Start being able to build universal binaries on OS X (thanks
15694 - Export the default exit policy via the control port, so controllers
15695 don't need to guess what it is / will be later.
15696 - Add a man page entry for ProtocolWarnings.
15697 - Add TestVia config option to the man page.
15698 - Remove even more protocol-related warnings from Tor server logs,
15699 such as bad TLS handshakes and malformed begin cells.
15700 - Stop fetching descriptors if you're not a dir mirror and you
15701 haven't tried to establish any circuits lately. [This currently
15702 causes some dangerous behavior, because when you start up again
15703 you'll use your ancient server descriptors.]
15704 - New DirPort behavior: if you have your dirport set, you download
15705 descriptors aggressively like a directory mirror, whether or not
15706 your ORPort is set.
15707 - Get rid of the router_retry_connections notion. Now routers
15708 no longer try to rebuild long-term connections to directory
15709 authorities, and directory authorities no longer try to rebuild
15710 long-term connections to all servers. We still don't hang up
15711 connections in these two cases though -- we need to look at it
15712 more carefully to avoid flapping, and we likely need to wait til
15713 0.1.1.x is obsolete.
15714 - Drop compatibility with obsolete Tors that permit create cells
15715 to have the wrong circ_id_type.
15716 - Re-enable per-connection rate limiting. Get rid of the "OP
15717 bandwidth" concept. Lay groundwork for "bandwidth classes" --
15718 separate global buckets that apply depending on what sort of conn
15720 - Start publishing one minute or so after we find our ORPort
15721 to be reachable. This will help reduce the number of descriptors
15722 we have for ourselves floating around, since it's quite likely
15723 other things (e.g. DirPort) will change during that minute too.
15724 - Fork the v1 directory protocol into its own spec document,
15725 and mark dir-spec.txt as the currently correct (v2) spec.
15728 - When we find our DirPort to be reachable, publish a new descriptor
15729 so we'll tell the world (reported by pnx).
15730 - Publish a new descriptor after we hup/reload. This is important
15731 if our config has changed such that we'll want to start advertising
15732 our DirPort now, etc.
15733 - Allow Tor to start when RunAsDaemon is set but no logs are set.
15734 - When we have a state file we cannot parse, tell the user and
15735 move it aside. Now we avoid situations where the user starts
15736 Tor in 1904, Tor writes a state file with that timestamp in it,
15737 the user fixes her clock, and Tor refuses to start.
15738 - Fix configure.in to not produce broken configure files with
15739 more recent versions of autoconf. Thanks to Clint for his auto*
15741 - "tor --verify-config" now exits with -1(255) or 0 depending on
15742 whether the config options are bad or good.
15743 - Resolve bug 321 when using dnsworkers: append a period to every
15744 address we resolve at the exit node, so that we do not accidentally
15745 pick up local addresses, and so that failing searches are retried
15746 in the resolver search domains. (This is already solved for
15747 eventdns.) (This breaks Blossom servers for now.)
15748 - If we are using an exit enclave and we can't connect, e.g. because
15749 its webserver is misconfigured to not listen on localhost, then
15750 back off and try connecting from somewhere else before we fail.
15753 - Start compiling on MinGW on Windows (patches from Mike Chiussi).
15754 - Start compiling on MSVC6 on Windows (patches from Frediano Ziglio).
15755 - Fix bug 314: Tor clients issued "unsafe socks" warnings even
15756 when the IP address is mapped through MapAddress to a hostname.
15757 - Start passing "ipv4" hints to getaddrinfo(), so servers don't do
15758 useless IPv6 DNS resolves.
15759 - Patch suggested by Karsten Loesing: respond to SIGNAL command
15760 before we execute the signal, in case the signal shuts us down.
15761 - Clean up AllowInvalidNodes man page entry.
15762 - Claim a commonname of Tor, rather than TOR, in TLS handshakes.
15763 - Add more asserts to track down an assert error on a windows Tor
15764 server with connection_add being called with socket == -1.
15765 - Handle reporting OR_CONN_EVENT_NEW events to the controller.
15766 - Fix misleading log messages: an entry guard that is "unlisted",
15767 as well as not known to be "down" (because we've never heard
15768 of it), is not therefore "up".
15769 - Remove code to special-case "-cvs" ending, since it has not
15770 actually mattered since 0.0.9.
15771 - Make our socks5 handling more robust to broken socks clients:
15772 throw out everything waiting on the buffer in between socks
15773 handshake phases, since they can't possibly (so the theory
15774 goes) have predicted what we plan to respond to them.
15777 Changes in version 0.1.1.23 - 2006-07-30
15779 - Fast Tor servers, especially exit nodes, were triggering asserts
15780 due to a bug in handling the list of pending DNS resolves. Some
15781 bugs still remain here; we're hunting them.
15782 - Entry guards could crash clients by sending unexpected input.
15783 - More fixes on reachability testing: if you find yourself reachable,
15784 then don't ever make any client requests (so you stop predicting
15785 circuits), then hup or have your clock jump, then later your IP
15786 changes, you won't think circuits are working, so you won't try to
15787 test reachability, so you won't publish.
15790 - Avoid a crash if the controller does a resetconf firewallports
15791 and then a setconf fascistfirewall=1.
15792 - Avoid an integer underflow when the dir authority decides whether
15793 a router is stable: we might wrongly label it stable, and compute
15794 a slightly wrong median stability, when a descriptor is published
15796 - Fix a place where we might trigger an assert if we can't build our
15797 own server descriptor yet.
15800 Changes in version 0.1.1.22 - 2006-07-05
15802 - Fix a big bug that was causing servers to not find themselves
15803 reachable if they changed IP addresses. Since only 0.1.1.22+
15804 servers can do reachability testing correctly, now we automatically
15805 make sure to test via one of these.
15806 - Fix to allow clients and mirrors to learn directory info from
15807 descriptor downloads that get cut off partway through.
15808 - Directory authorities had a bug in deciding if a newly published
15809 descriptor was novel enough to make everybody want a copy -- a few
15810 servers seem to be publishing new descriptors many times a minute.
15812 - Fix a rare bug that was causing some servers to complain about
15813 "closing wedged cpuworkers" and skip some circuit create requests.
15814 - Make the Exit flag in directory status documents actually work.
15817 Changes in version 0.1.1.21 - 2006-06-10
15818 o Crash and assert fixes from 0.1.1.20:
15819 - Fix a rare crash on Tor servers that have enabled hibernation.
15820 - Fix a seg fault on startup for Tor networks that use only one
15821 directory authority.
15822 - Fix an assert from a race condition that occurs on Tor servers
15823 while exiting, where various threads are trying to log that they're
15824 exiting, and delete the logs, at the same time.
15825 - Make our unit tests pass again on certain obscure platforms.
15828 - Add support for building SUSE RPM packages.
15829 - Speed up initial bootstrapping for clients: if we are making our
15830 first ever connection to any entry guard, then don't mark it down
15832 - When only one Tor server in the network is labelled as a guard,
15833 and we've already picked him, we would cycle endlessly picking him
15834 again, being unhappy about it, etc. Now we specifically exclude
15835 current guards when picking a new guard.
15836 - Servers send create cells more reliably after the TLS connection
15837 is established: we were sometimes forgetting to send half of them
15838 when we had more than one pending.
15839 - If we get a create cell that asks us to extend somewhere, but the
15840 Tor server there doesn't match the expected digest, we now send
15841 a destroy cell back, rather than silently doing nothing.
15842 - Make options->RedirectExit work again.
15843 - Make cookie authentication for the controller work again.
15844 - Stop being picky about unusual characters in the arguments to
15845 mapaddress. It's none of our business.
15846 - Add a new config option "TestVia" that lets you specify preferred
15847 middle hops to use for test circuits. Perhaps this will let me
15848 debug the reachability problems better.
15850 o Log / documentation fixes:
15851 - If we're a server and some peer has a broken TLS certificate, don't
15852 log about it unless ProtocolWarnings is set, i.e., we want to hear
15853 about protocol violations by others.
15854 - Fix spelling of VirtualAddrNetwork in man page.
15855 - Add a better explanation at the top of the autogenerated torrc file
15856 about what happened to our old torrc.
15859 Changes in version 0.1.1.20 - 2006-05-23
15861 - Downgrade a log severity where servers complain that they're
15863 - Avoid a compile warning on FreeBSD.
15864 - Remove string size limit on NEWDESC messages; solve bug 291.
15865 - Correct the RunAsDaemon entry in the man page; ignore RunAsDaemon
15866 more thoroughly when we're running on windows.
15869 Changes in version 0.1.1.19-rc - 2006-05-03
15871 - Regenerate our local descriptor if it's dirty and we try to use
15872 it locally (e.g. if it changes during reachability detection).
15873 - If we setconf our ORPort to 0, we continued to listen on the
15874 old ORPort and receive connections.
15875 - Avoid a second warning about machine/limits.h on Debian
15877 - Be willing to add our own routerinfo into the routerlist.
15878 Now authorities will include themselves in their directories
15879 and network-statuses.
15880 - Stop trying to upload rendezvous descriptors to every
15881 directory authority: only try the v1 authorities.
15882 - Servers no longer complain when they think they're not
15883 registered with the directory authorities. There were too many
15885 - Backport dist-rpm changes so rpms can be built without errors.
15888 - Implement an option, VirtualAddrMask, to set which addresses
15889 get handed out in response to mapaddress requests. This works
15890 around a bug in tsocks where 127.0.0.0/8 is never socksified.
15893 Changes in version 0.1.1.18-rc - 2006-04-10
15895 - Work harder to download live network-statuses from all the
15896 directory authorities we know about. Improve the threshold
15897 decision logic so we're more robust to edge cases.
15898 - When fetching rendezvous descriptors, we were willing to ask
15899 v2 authorities too, which would always return 404.
15902 - Stop listing down or invalid nodes in the v1 directory. This will
15903 reduce its bulk by about 1/3, and reduce load on directory
15905 - When deciding whether a router is Fast or Guard-worthy, consider
15906 his advertised BandwidthRate and not just the BandwidthCapacity.
15907 - No longer ship INSTALL and README files -- they are useless now.
15908 - Force rpmbuild to behave and honor target_cpu.
15909 - Avoid warnings about machine/limits.h on Debian GNU/kFreeBSD.
15910 - Start to include translated versions of the tor-doc-*.html
15911 files, along with the screenshots. Still needs more work.
15912 - Start sending back 512 and 451 errors if mapaddress fails,
15913 rather than not sending anything back at all.
15914 - When we fail to bind or listen on an incoming or outgoing
15915 socket, we should close it before failing. otherwise we just
15916 leak it. (thanks to weasel for finding.)
15917 - Allow "getinfo dir/status/foo" to work, as long as your DirPort
15918 is enabled. (This is a hack, and will be fixed in 0.1.2.x.)
15919 - Make NoPublish (even though deprecated) work again.
15920 - Fix a minor security flaw where a versioning auth dirserver
15921 could list a recommended version many times in a row to make
15922 clients more convinced that it's recommended.
15923 - Fix crash bug if there are two unregistered servers running
15924 with the same nickname, one of them is down, and you ask for
15925 them by nickname in your EntryNodes or ExitNodes. Also, try
15926 to pick the one that's running rather than an arbitrary one.
15927 - Fix an infinite loop we could hit if we go offline for too long.
15928 - Complain when we hit WSAENOBUFS on recv() or write() too.
15929 Perhaps this will help us hunt the bug.
15930 - If you're not a versioning dirserver, don't put the string
15931 "client-versions \nserver-versions \n" in your network-status.
15932 - Lower the minimum required number of file descriptors to 1000,
15933 so we can have some overhead for Valgrind on Linux, where the
15934 default ulimit -n is 1024.
15937 - Add tor.dizum.com as the fifth authoritative directory server.
15938 - Add a new config option FetchUselessDescriptors, off by default,
15939 for when you plan to run "exitlist" on your client and you want
15940 to know about even the non-running descriptors.
15943 Changes in version 0.1.1.17-rc - 2006-03-28
15945 - Clients and servers since 0.1.1.10-alpha have been expiring
15946 connections whenever they are idle for 5 minutes and they *do*
15947 have circuits on them. Oops. With this new version, clients will
15948 discard their previous entry guard choices and avoid choosing
15949 entry guards running these flawed versions.
15950 - Fix memory leak when uncompressing concatenated zlib streams. This
15951 was causing substantial leaks over time on Tor servers.
15952 - The v1 directory was including servers as much as 48 hours old,
15953 because that's how the new routerlist->routers works. Now only
15954 include them if they're 20 hours old or less.
15957 - Resume building on irix64, netbsd 2.0, etc.
15958 - On non-gcc compilers (e.g. solaris), use "-g -O" instead of
15960 - Stop writing the "router.desc" file, ever. Nothing uses it anymore,
15961 and it is confusing some users.
15962 - Mirrors stop caching the v1 directory so often.
15963 - Make the max number of old descriptors that a cache will hold
15964 rise with the number of directory authorities, so we can scale.
15965 - Change our win32 uname() hack to be more forgiving about what
15966 win32 versions it thinks it's found.
15969 - Add lefkada.eecs.harvard.edu as a fourth authoritative directory
15971 - When the controller's *setconf commands fail, collect an error
15972 message in a string and hand it back to the controller.
15973 - Make the v2 dir's "Fast" flag based on relative capacity, just
15974 like "Stable" is based on median uptime. Name everything in the
15975 top 7/8 Fast, and only the top 1/2 gets to be a Guard.
15976 - Log server fingerprint on startup, so new server operators don't
15977 have to go hunting around their filesystem for it.
15978 - Return a robots.txt on our dirport to discourage google indexing.
15979 - Let the controller ask for GETINFO dir/status/foo so it can ask
15980 directly rather than connecting to the dir port. Only works when
15981 dirport is set for now.
15983 o New config options rather than constants in the code:
15984 - SocksTimeout: How long do we let a socks connection wait
15985 unattached before we fail it?
15986 - CircuitBuildTimeout: Cull non-open circuits that were born
15987 at least this many seconds ago.
15988 - CircuitIdleTimeout: Cull open clean circuits that were born
15989 at least this many seconds ago.
15992 Changes in version 0.1.1.16-rc - 2006-03-18
15993 o Bugfixes on 0.1.1.15-rc:
15994 - Fix assert when the controller asks to attachstream a connect-wait
15995 or resolve-wait stream.
15996 - Now do address rewriting when the controller asks us to attach
15997 to a particular circuit too. This will let Blossom specify
15998 "moria2.exit" without having to learn what moria2's IP address is.
15999 - Make the "tor --verify-config" command-line work again, so people
16000 can automatically check if their torrc will parse.
16001 - Authoritative dirservers no longer require an open connection from
16002 a server to consider him "reachable". We need this change because
16003 when we add new auth dirservers, old servers won't know not to
16005 - Let Tor build on Sun CC again.
16006 - Fix an off-by-one buffer size in dirserv.c that magically never
16007 hit our three authorities but broke sjmurdoch's own tor network.
16008 - If we as a directory mirror don't know of any v1 directory
16009 authorities, then don't try to cache any v1 directories.
16010 - Stop warning about unknown servers in our family when they are
16011 given as hex digests.
16012 - Stop complaining as quickly to the server operator that he
16013 hasn't registered his nickname/key binding.
16014 - Various cleanups so we can add new V2 Auth Dirservers.
16015 - Change "AllowUnverifiedNodes" to "AllowInvalidNodes", to
16016 reflect the updated flags in our v2 dir protocol.
16017 - Resume allowing non-printable characters for exit streams (both
16018 for connecting and for resolving). Now we tolerate applications
16019 that don't follow the RFCs. But continue to block malformed names
16022 o Bugfixes on 0.1.0.x:
16023 - Fix assert bug in close_logs(): when we close and delete logs,
16024 remove them all from the global "logfiles" list.
16025 - Fix minor integer overflow in calculating when we expect to use up
16026 our bandwidth allocation before hibernating.
16027 - Fix a couple of bugs in OpenSSL detection. Also, deal better when
16028 there are multiple SSLs installed with different versions.
16029 - When we try to be a server and Address is not explicitly set and
16030 our hostname resolves to a private IP address, try to use an
16031 interface address if it has a public address. Now Windows machines
16032 that think of themselves as localhost can work by default.
16035 - Let the controller ask for GETINFO dir/server/foo so it can ask
16036 directly rather than connecting to the dir port.
16037 - Let the controller tell us about certain router descriptors
16038 that it doesn't want Tor to use in circuits. Implement
16039 SETROUTERPURPOSE and modify +POSTDESCRIPTOR to do this.
16040 - New config option SafeSocks to reject all application connections
16041 using unsafe socks protocols. Defaults to off.
16044 Changes in version 0.1.1.15-rc - 2006-03-11
16045 o Bugfixes and cleanups:
16046 - When we're printing strings from the network, don't try to print
16047 non-printable characters. This protects us against shell escape
16048 sequence exploits, and also against attacks to fool humans into
16049 misreading their logs.
16050 - Fix a bug where Tor would fail to establish any connections if you
16051 left it off for 24 hours and then started it: we were happy with
16052 the obsolete network statuses, but they all referred to router
16053 descriptors that were too old to fetch, so we ended up with no
16054 valid router descriptors.
16055 - Fix a seg fault in the controller's "getinfo orconn-status"
16056 command while listing status on incoming handshaking connections.
16057 Introduce a status name "NEW" for these connections.
16058 - If we get a linelist or linelist_s config option from the torrc
16059 (e.g. ExitPolicy) and it has no value, warn and skip rather than
16060 silently resetting it to its default.
16061 - Don't abandon entry guards until they've been down or gone for
16063 - Cleaner and quieter log messages.
16066 - New controller signal NEWNYM that makes new application requests
16067 use clean circuits.
16068 - Add a new circuit purpose 'controller' to let the controller ask
16069 for a circuit that Tor won't try to use. Extend the EXTENDCIRCUIT
16070 controller command to let you specify the purpose if you're
16071 starting a new circuit. Add a new SETCIRCUITPURPOSE controller
16072 command to let you change a circuit's purpose after it's been
16074 - Accept "private:*" in routerdesc exit policies; not generated yet
16075 because older Tors do not understand it.
16076 - Add BSD-style contributed startup script "rc.subr" from Peter
16080 Changes in version 0.1.1.14-alpha - 2006-02-20
16081 o Bugfixes on 0.1.1.x:
16082 - Don't die if we ask for a stdout or stderr log (even implicitly)
16083 and we're set to RunAsDaemon -- just warn.
16084 - We still had a few bugs in the OR connection rotation code that
16085 caused directory servers to slowly aggregate connections to other
16086 fast Tor servers. This time for sure!
16087 - Make log entries on Win32 include the name of the function again.
16088 - We were treating a pair of exit policies if they were equal even
16089 if one said accept and the other said reject -- causing us to
16090 not always publish a new descriptor since we thought nothing
16092 - Retry pending server downloads as well as pending networkstatus
16093 downloads when we unexpectedly get a socks request.
16094 - We were ignoring the IS_FAST flag in the directory status,
16095 meaning we were willing to pick trivial-bandwidth nodes for "fast"
16097 - If the controller's SAVECONF command fails (e.g. due to file
16098 permissions), let the controller know that it failed.
16101 - If we're trying to be a Tor server and running Windows 95/98/ME
16102 as a server, explain that we'll likely crash.
16103 - When we're a server, a client asks for an old-style directory,
16104 and our write bucket is empty, don't give it to him. This way
16105 small servers can continue to serve the directory *sometimes*,
16106 without getting overloaded.
16107 - Compress exit policies even more -- look for duplicate lines
16109 - Clients now honor the "guard" flag in the router status when
16110 picking entry guards, rather than looking at is_fast or is_stable.
16111 - Retain unrecognized lines in $DATADIR/state file, so that we can
16112 be forward-compatible.
16113 - Generate 18.0.0.0/8 address policy format in descs when we can;
16114 warn when the mask is not reducible to a bit-prefix.
16115 - Let the user set ControlListenAddress in the torrc. This can be
16116 dangerous, but there are some cases (like a secured LAN) where it
16118 - Split ReachableAddresses into ReachableDirAddresses and
16119 ReachableORAddresses, so we can restrict Dir conns to port 80
16120 and OR conns to port 443.
16121 - Now we can target arch and OS in rpm builds (contributed by
16122 Phobos). Also make the resulting dist-rpm filename match the
16124 - New config options to help controllers: FetchServerDescriptors
16125 and FetchHidServDescriptors for whether to fetch server
16126 info and hidserv info or let the controller do it, and
16127 PublishServerDescriptor and PublishHidServDescriptors.
16128 - Also let the controller set the __AllDirActionsPrivate config
16129 option if you want all directory fetches/publishes to happen via
16130 Tor (it assumes your controller bootstraps your circuits).
16133 Changes in version 0.1.0.17 - 2006-02-17
16134 o Crash bugfixes on 0.1.0.x:
16135 - When servers with a non-zero DirPort came out of hibernation,
16136 sometimes they would trigger an assert.
16138 o Other important bugfixes:
16139 - On platforms that don't have getrlimit (like Windows), we were
16140 artificially constraining ourselves to a max of 1024
16141 connections. Now just assume that we can handle as many as 15000
16142 connections. Hopefully this won't cause other problems.
16144 o Backported features:
16145 - When we're a server, a client asks for an old-style directory,
16146 and our write bucket is empty, don't give it to him. This way
16147 small servers can continue to serve the directory *sometimes*,
16148 without getting overloaded.
16149 - Whenever you get a 503 in response to a directory fetch, try
16150 once more. This will become important once servers start sending
16151 503's whenever they feel busy.
16152 - Fetch a new directory every 120 minutes, not every 40 minutes.
16153 Now that we have hundreds of thousands of users running the old
16154 directory algorithm, it's starting to hurt a lot.
16155 - Bump up the period for forcing a hidden service descriptor upload
16156 from 20 minutes to 1 hour.
16159 Changes in version 0.1.1.13-alpha - 2006-02-09
16160 o Crashes in 0.1.1.x:
16161 - When you tried to setconf ORPort via the controller, Tor would
16162 crash. So people using TorCP to become a server were sad.
16163 - Solve (I hope) the stack-smashing bug that we were seeing on fast
16164 servers. The problem appears to be something do with OpenSSL's
16165 random number generation, or how we call it, or something. Let me
16166 know if the crashes continue.
16167 - Turn crypto hardware acceleration off by default, until we find
16168 somebody smart who can test it for us. (It appears to produce
16169 seg faults in at least some cases.)
16170 - Fix a rare assert error when we've tried all intro points for
16171 a hidden service and we try fetching the service descriptor again:
16172 "Assertion conn->state != AP_CONN_STATE_RENDDESC_WAIT failed"
16175 - Fix a major load balance bug: we were round-robining in 16 KB
16176 chunks, and servers with bandwidthrate of 20 KB, while downloading
16177 a 600 KB directory, would starve their other connections. Now we
16178 try to be a bit more fair.
16179 - Dir authorities and mirrors were never expiring the newest
16180 descriptor for each server, causing memory and directory bloat.
16181 - Fix memory-bloating and connection-bloating bug on servers: We
16182 were never closing any connection that had ever had a circuit on
16183 it, because we were checking conn->n_circuits == 0, yet we had a
16184 bug that let it go negative.
16185 - Make Tor work using squid as your http proxy again -- squid
16186 returns an error if you ask for a URL that's too long, and it uses
16187 a really generic error message. Plus, many people are behind a
16188 transparent squid so they don't even realize it.
16189 - On platforms that don't have getrlimit (like Windows), we were
16190 artificially constraining ourselves to a max of 1024
16191 connections. Now just assume that we can handle as many as 15000
16192 connections. Hopefully this won't cause other problems.
16193 - Add a new config option ExitPolicyRejectPrivate which defaults to
16194 1. This means all exit policies will begin with rejecting private
16195 addresses, unless the server operator explicitly turns it off.
16198 - Clients no longer download descriptors for non-running
16200 - Before we add new directory authorities, we should make it
16201 clear that only v1 authorities should receive/publish hidden
16202 service descriptors.
16205 - As soon as we've fetched some more directory info, immediately
16206 try to download more server descriptors. This way we don't have
16207 a 10 second pause during initial bootstrapping.
16208 - Remove even more loud log messages that the server operator can't
16210 - When we're running an obsolete or un-recommended version, make
16211 the log message more clear about what the problem is and what
16212 versions *are* still recommended.
16213 - Provide a more useful warn message when our onion queue gets full:
16214 the CPU is too slow or the exit policy is too liberal.
16215 - Don't warn when we receive a 503 from a dirserver/cache -- this
16216 will pave the way for them being able to refuse if they're busy.
16217 - When we fail to bind a listener, try to provide a more useful
16218 log message: e.g., "Is Tor already running?"
16219 - Adjust tor-spec to parameterize cell and key lengths. Now Ian
16220 Goldberg can prove things about our handshake protocol more
16222 - MaxConn has been obsolete for a while now. Document the ConnLimit
16223 config option, which is a *minimum* number of file descriptors
16224 that must be available else Tor refuses to start.
16225 - Apply Matt Ghali's --with-syslog-facility patch to ./configure
16226 if you log to syslog and want something other than LOG_DAEMON.
16227 - Make dirservers generate a separate "guard" flag to mean,
16228 "would make a good entry guard". Make clients parse it and vote
16229 on it. Not used by clients yet.
16230 - Implement --with-libevent-dir option to ./configure. Also, improve
16231 search techniques to find libevent, and use those for openssl too.
16232 - Bump the default bandwidthrate to 3 MB, and burst to 6 MB
16233 - Only start testing reachability once we've established a
16234 circuit. This will make startup on dirservers less noisy.
16235 - Don't try to upload hidden service descriptors until we have
16236 established a circuit.
16237 - Fix the controller's "attachstream 0" command to treat conn like
16238 it just connected, doing address remapping, handling .exit and
16239 .onion idioms, and so on. Now we're more uniform in making sure
16240 that the controller hears about new and closing connections.
16243 Changes in version 0.1.1.12-alpha - 2006-01-11
16244 o Bugfixes on 0.1.1.x:
16245 - The fix to close duplicate server connections was closing all
16246 Tor client connections if they didn't establish a circuit
16247 quickly enough. Oops.
16248 - Fix minor memory issue (double-free) that happened on exit.
16250 o Bugfixes on 0.1.0.x:
16251 - Tor didn't warn when it failed to open a log file.
16254 Changes in version 0.1.1.11-alpha - 2006-01-10
16255 o Crashes in 0.1.1.x:
16256 - Include all the assert/crash fixes from 0.1.0.16.
16257 - If you start Tor and then quit very quickly, there were some
16258 races that tried to free things that weren't allocated yet.
16259 - Fix a rare memory stomp if you're running hidden services.
16260 - Fix segfault when specifying DirServer in config without nickname.
16261 - Fix a seg fault when you finish connecting to a server but at
16262 that moment you dump his server descriptor.
16263 - Extendcircuit and Attachstream controller commands would
16264 assert/crash if you don't give them enough arguments.
16265 - Fix an assert error when we're out of space in the connection_list
16266 and we try to post a hidden service descriptor (reported by weasel).
16267 - If you specify a relative torrc path and you set RunAsDaemon in
16268 your torrc, then it chdir()'s to the new directory. If you HUP,
16269 it tries to load the new torrc location, fails, and exits.
16270 The fix: no longer allow a relative path to torrc using -f.
16273 - Implement "entry guards": automatically choose a handful of entry
16274 nodes and stick with them for all circuits. Only pick new guards
16275 when the ones you have are unsuitable, and if the old guards
16276 become suitable again, switch back. This will increase security
16277 dramatically against certain end-point attacks. The EntryNodes
16278 config option now provides some hints about which entry guards you
16279 want to use most; and StrictEntryNodes means to only use those.
16280 - New directory logic: download by descriptor digest, not by
16281 fingerprint. Caches try to download all listed digests from
16282 authorities; clients try to download "best" digests from caches.
16283 This avoids partitioning and isolating attacks better.
16284 - Make the "stable" router flag in network-status be the median of
16285 the uptimes of running valid servers, and make clients pay
16286 attention to the network-status flags. Thus the cutoff adapts
16287 to the stability of the network as a whole, making IRC, IM, etc
16288 connections more reliable.
16291 - Tor servers with dynamic IP addresses were needing to wait 18
16292 hours before they could start doing reachability testing using
16293 the new IP address and ports. This is because they were using
16294 the internal descriptor to learn what to test, yet they were only
16295 rebuilding the descriptor once they decided they were reachable.
16296 - Tor 0.1.1.9 and 0.1.1.10 had a serious bug that caused clients
16297 to download certain server descriptors, throw them away, and then
16298 fetch them again after 30 minutes. Now mirrors throw away these
16299 server descriptors so clients can't get them.
16300 - We were leaving duplicate connections to other ORs open for a week,
16301 rather than closing them once we detect a duplicate. This only
16302 really affected authdirservers, but it affected them a lot.
16303 - Spread the authdirservers' reachability testing over the entire
16304 testing interval, so we don't try to do 500 TLS's at once every
16308 - If the network is down, and we try to connect to a conn because
16309 we have a circuit in mind, and we timeout (30 seconds) because the
16310 network never answers, we were expiring the circuit, but we weren't
16311 obsoleting the connection or telling the entry_guards functions.
16312 - Some Tor servers process billions of cells per day. These statistics
16313 need to be uint64_t's.
16314 - Check for integer overflows in more places, when adding elements
16315 to smartlists. This could possibly prevent a buffer overflow
16316 on malicious huge inputs. I don't see any, but I haven't looked
16318 - ReachableAddresses kept growing new "reject *:*" lines on every
16320 - When you "setconf log" via the controller, it should remove all
16321 logs. We were automatically adding back in a "log notice stdout".
16322 - Newly bootstrapped Tor networks couldn't establish hidden service
16323 circuits until they had nodes with high uptime. Be more tolerant.
16324 - We were marking servers down when they could not answer every piece
16325 of the directory request we sent them. This was far too harsh.
16326 - Fix the torify (tsocks) config file to not use Tor for localhost
16328 - Directory authorities now go to the proper authority when asking for
16329 a networkstatus, even when they want a compressed one.
16330 - Fix a harmless bug that was causing Tor servers to log
16331 "Got an end because of misc error, but we're not an AP. Closing."
16332 - Authorities were treating their own descriptor changes as cosmetic,
16333 meaning the descriptor available in the network-status and the
16334 descriptor that clients downloaded were different.
16335 - The OS X installer was adding a symlink for tor_resolve but
16336 the binary was called tor-resolve (reported by Thomas Hardly).
16337 - Workaround a problem with some http proxies where they refuse GET
16338 requests that specify "Content-Length: 0" (reported by Adrian).
16339 - Fix wrong log message when you add a "HiddenServiceNodes" config
16340 line without any HiddenServiceDir line (reported by Chris Thomas).
16343 - Write the TorVersion into the state file so we have a prayer of
16344 keeping forward and backward compatibility.
16345 - Revive the FascistFirewall config option rather than eliminating it:
16346 now it's a synonym for ReachableAddresses *:80,*:443.
16347 - Clients choose directory servers from the network status lists,
16348 not from their internal list of router descriptors. Now they can
16349 go to caches directly rather than needing to go to authorities
16351 - Directory authorities ignore router descriptors that have only
16352 cosmetic differences: do this for 0.1.0.x servers now too.
16353 - Add a new flag to network-status indicating whether the server
16354 can answer v2 directory requests too.
16355 - Authdirs now stop whining so loudly about bad descriptors that
16356 they fetch from other dirservers. So when there's a log complaint,
16357 it's for sure from a freshly uploaded descriptor.
16358 - Reduce memory requirements in our structs by changing the order
16360 - There used to be two ways to specify your listening ports in a
16361 server descriptor: on the "router" line and with a separate "ports"
16362 line. Remove support for the "ports" line.
16363 - New config option "AuthDirRejectUnlisted" for auth dirservers as
16364 a panic button: if we get flooded with unusable servers we can
16365 revert to only listing servers in the approved-routers file.
16366 - Auth dir servers can now mark a fingerprint as "!reject" or
16367 "!invalid" in the approved-routers file (as its nickname), to
16368 refuse descriptors outright or include them but marked as invalid.
16369 - Servers store bandwidth history across restarts/crashes.
16370 - Add reasons to DESTROY and RELAY_TRUNCATED cells, so clients can
16371 get a better idea of why their circuits failed. Not used yet.
16372 - Directory mirrors now cache up to 16 unrecognized network-status
16373 docs. Now we can add new authdirservers and they'll be cached too.
16374 - When picking a random directory, prefer non-authorities if any
16376 - New controller option "getinfo desc/all-recent" to fetch the
16377 latest server descriptor for every router that Tor knows about.
16380 Changes in version 0.1.0.16 - 2006-01-02
16381 o Crash bugfixes on 0.1.0.x:
16382 - On Windows, build with a libevent patch from "I-M Weasel" to avoid
16383 corrupting the heap, losing FDs, or crashing when we need to resize
16384 the fd_sets. (This affects the Win32 binaries, not Tor's sources.)
16385 - It turns out sparc64 platforms crash on unaligned memory access
16386 too -- so detect and avoid this.
16387 - Handle truncated compressed data correctly (by detecting it and
16389 - Fix possible-but-unlikely free(NULL) in control.c.
16390 - When we were closing connections, there was a rare case that
16391 stomped on memory, triggering seg faults and asserts.
16392 - Avoid potential infinite recursion when building a descriptor. (We
16393 don't know that it ever happened, but better to fix it anyway.)
16394 - We were neglecting to unlink marked circuits from soon-to-close OR
16395 connections, which caused some rare scribbling on freed memory.
16396 - Fix a memory stomping race bug when closing the joining point of two
16397 rendezvous circuits.
16398 - Fix an assert in time parsing found by Steven Murdoch.
16400 o Other bugfixes on 0.1.0.x:
16401 - When we're doing reachability testing, provide more useful log
16402 messages so the operator knows what to expect.
16403 - Do not check whether DirPort is reachable when we are suppressing
16404 advertising it because of hibernation.
16405 - When building with -static or on Solaris, we sometimes needed -ldl.
16406 - When we're deciding whether a stream has enough circuits around
16407 that can handle it, count the freshly dirty ones and not the ones
16408 that are so dirty they won't be able to handle it.
16409 - When we're expiring old circuits, we had a logic error that caused
16410 us to close new rendezvous circuits rather than old ones.
16411 - Give a more helpful log message when you try to change ORPort via
16412 the controller: you should upgrade Tor if you want that to work.
16413 - We were failing to parse Tor versions that start with "Tor ".
16414 - Tolerate faulty streams better: when a stream fails for reason
16415 exitpolicy, stop assuming that the router is lying about his exit
16416 policy. When a stream fails for reason misc, allow it to retry just
16417 as if it was resolvefailed. When a stream has failed three times,
16418 reset its failure count so we can try again and get all three tries.
16421 Changes in version 0.1.1.10-alpha - 2005-12-11
16422 o Correctness bugfixes on 0.1.0.x:
16423 - On Windows, build with a libevent patch from "I-M Weasel" to avoid
16424 corrupting the heap, losing FDs, or crashing when we need to resize
16425 the fd_sets. (This affects the Win32 binaries, not Tor's sources.)
16426 - Stop doing the complex voodoo overkill checking for insecure
16427 Diffie-Hellman keys. Just check if it's in [2,p-2] and be happy.
16428 - When we were closing connections, there was a rare case that
16429 stomped on memory, triggering seg faults and asserts.
16430 - We were neglecting to unlink marked circuits from soon-to-close OR
16431 connections, which caused some rare scribbling on freed memory.
16432 - When we're deciding whether a stream has enough circuits around
16433 that can handle it, count the freshly dirty ones and not the ones
16434 that are so dirty they won't be able to handle it.
16435 - Recover better from TCP connections to Tor servers that are
16436 broken but don't tell you (it happens!); and rotate TLS
16437 connections once a week.
16438 - When we're expiring old circuits, we had a logic error that caused
16439 us to close new rendezvous circuits rather than old ones.
16440 - Fix a scary-looking but apparently harmless bug where circuits
16441 would sometimes start out in state CIRCUIT_STATE_OR_WAIT at
16442 servers, and never switch to state CIRCUIT_STATE_OPEN.
16443 - When building with -static or on Solaris, we sometimes needed to
16445 - Give a useful message when people run Tor as the wrong user,
16446 rather than telling them to start chowning random directories.
16447 - We were failing to inform the controller about new .onion streams.
16449 o Security bugfixes on 0.1.0.x:
16450 - Refuse server descriptors if the fingerprint line doesn't match
16451 the included identity key. Tor doesn't care, but other apps (and
16452 humans) might actually be trusting the fingerprint line.
16453 - We used to kill the circuit when we receive a relay command we
16454 don't recognize. Now we just drop it.
16455 - Start obeying our firewall options more rigorously:
16456 . If we can't get to a dirserver directly, try going via Tor.
16457 . Don't ever try to connect (as a client) to a place our
16458 firewall options forbid.
16459 . If we specify a proxy and also firewall options, obey the
16460 firewall options even when we're using the proxy: some proxies
16461 can only proxy to certain destinations.
16462 - Fix a bug found by Lasse Overlier: when we were making internal
16463 circuits (intended to be cannibalized later for rendezvous and
16464 introduction circuits), we were picking them so that they had
16465 useful exit nodes. There was no need for this, and it actually
16466 aids some statistical attacks.
16467 - Start treating internal circuits and exit circuits separately.
16468 It's important to keep them separate because internal circuits
16469 have their last hops picked like middle hops, rather than like
16470 exit hops. So exiting on them will break the user's expectations.
16472 o Bugfixes on 0.1.1.x:
16473 - Take out the mis-feature where we tried to detect IP address
16474 flapping for people with DynDNS, and chose not to upload a new
16475 server descriptor sometimes.
16476 - Try to be compatible with OpenSSL 0.9.6 again.
16477 - Log fix: when the controller is logging about .onion addresses,
16478 sometimes it didn't include the ".onion" part of the address.
16479 - Don't try to modify options->DirServers internally -- if the
16480 user didn't specify any, just add the default ones directly to
16481 the trusted dirserver list. This fixes a bug where people running
16482 controllers would use SETCONF on some totally unrelated config
16483 option, and Tor would start yelling at them about changing their
16485 - Let the controller's redirectstream command specify a port, in
16486 case the controller wants to change that too.
16487 - When we requested a pile of server descriptors, we sometimes
16488 accidentally launched a duplicate request for the first one.
16489 - Bugfix for trackhostexits: write down the fingerprint of the
16490 chosen exit, not its nickname, because the chosen exit might not
16492 - When parsing foo.exit, if foo is unknown, and we are leaving
16493 circuits unattached, set the chosen_exit field and leave the
16494 address empty. This matters because controllers got confused
16496 - Directory authorities no longer try to download server
16497 descriptors that they know they will reject.
16499 o Features and updates:
16500 - Replace balanced trees with hash tables: this should make stuff
16501 significantly faster.
16502 - Resume using the AES counter-mode implementation that we ship,
16503 rather than OpenSSL's. Ours is significantly faster.
16504 - Many other CPU and memory improvements.
16505 - Add a new config option FastFirstHopPK (on by default) so clients
16506 do a trivial crypto handshake for their first hop, since TLS has
16507 already taken care of confidentiality and authentication.
16508 - Add a new config option TestSocks so people can see if their
16509 applications are using socks4, socks4a, socks5-with-ip, or
16510 socks5-with-hostname. This way they don't have to keep mucking
16511 with tcpdump and wondering if something got cached somewhere.
16512 - Warn when listening on a public address for socks. I suspect a
16513 lot of people are setting themselves up as open socks proxies,
16514 and they have no idea that jerks on the Internet are using them,
16515 since they simply proxy the traffic into the Tor network.
16516 - Add "private:*" as an alias in configuration for policies. Now
16517 you can simplify your exit policy rather than needing to list
16518 every single internal or nonroutable network space.
16519 - Add a new controller event type that allows controllers to get
16520 all server descriptors that were uploaded to a router in its role
16521 as authoritative dirserver.
16522 - Start shipping socks-extensions.txt, tor-doc-unix.html,
16523 tor-doc-server.html, and stylesheet.css in the tarball.
16524 - Stop shipping tor-doc.html in the tarball.
16527 Changes in version 0.1.1.9-alpha - 2005-11-15
16528 o Usability improvements:
16529 - Start calling it FooListenAddress rather than FooBindAddress,
16530 since few of our users know what it means to bind an address
16532 - Reduce clutter in server logs. We're going to try to make
16533 them actually usable now. New config option ProtocolWarnings that
16534 lets you hear about how _other Tors_ are breaking the protocol. Off
16536 - Divide log messages into logging domains. Once we put some sort
16537 of interface on this, it will let people looking at more verbose
16538 log levels specify the topics they want to hear more about.
16539 - Make directory servers return better http 404 error messages
16540 instead of a generic "Servers unavailable".
16541 - Check for even more Windows version flags when writing the platform
16542 string in server descriptors, and note any we don't recognize.
16543 - Clean up more of the OpenSSL memory when exiting, so we can detect
16544 memory leaks better.
16545 - Make directory authorities be non-versioning, non-naming by
16546 default. Now we can add new directory servers without requiring
16547 their operators to pay close attention.
16548 - When logging via syslog, include the pid whenever we provide
16549 a log entry. Suggested by Todd Fries.
16551 o Performance improvements:
16552 - Directory servers now silently throw away new descriptors that
16553 haven't changed much if the timestamps are similar. We do this to
16554 tolerate older Tor servers that upload a new descriptor every 15
16555 minutes. (It seemed like a good idea at the time.)
16556 - Inline bottleneck smartlist functions; use fast versions by default.
16557 - Add a "Map from digest to void*" abstraction digestmap_t so we
16558 can do less hex encoding/decoding. Use it in router_get_by_digest()
16559 to resolve a performance bottleneck.
16560 - Allow tor_gzip_uncompress to extract as much as possible from
16561 truncated compressed data. Try to extract as many
16562 descriptors as possible from truncated http responses (when
16563 DIR_PURPOSE_FETCH_ROUTERDESC).
16564 - Make circ->onionskin a pointer, not a static array. moria2 was using
16565 125000 circuit_t's after it had been up for a few weeks, which
16566 translates to 20+ megs of wasted space.
16567 - The private half of our EDH handshake keys are now chosen out
16568 of 320 bits, not 1024 bits. (Suggested by Ian Goldberg.)
16570 o Security improvements:
16571 - Start making directory caches retain old routerinfos, so soon
16572 clients can start asking by digest of descriptor rather than by
16573 fingerprint of server.
16574 - Add half our entropy from RAND_poll in OpenSSL. This knows how
16575 to use egd (if present), openbsd weirdness (if present), vms/os2
16576 weirdness (if we ever port there), and more in the future.
16578 o Bugfixes on 0.1.0.x:
16579 - Do round-robin writes of at most 16 kB per write. This might be
16580 more fair on loaded Tor servers, and it might resolve our Windows
16581 crash bug. It might also slow things down.
16582 - Our TLS handshakes were generating a single public/private
16583 keypair for the TLS context, rather than making a new one for
16584 each new connections. Oops. (But we were still rotating them
16585 periodically, so it's not so bad.)
16586 - When we were cannibalizing a circuit with a particular exit
16587 node in mind, we weren't checking to see if that exit node was
16588 already present earlier in the circuit. Oops.
16589 - When a Tor server's IP changes (e.g. from a dyndns address),
16590 upload a new descriptor so clients will learn too.
16591 - Really busy servers were keeping enough circuits open on stable
16592 connections that they were wrapping around the circuit_id
16593 space. (It's only two bytes.) This exposed a bug where we would
16594 feel free to reuse a circuit_id even if it still exists but has
16595 been marked for close. Try to fix this bug. Some bug remains.
16596 - If we would close a stream early (e.g. it asks for a .exit that
16597 we know would refuse it) but the LeaveStreamsUnattached config
16598 option is set by the controller, then don't close it.
16600 o Bugfixes on 0.1.1.8-alpha:
16601 - Fix a big pile of memory leaks, some of them serious.
16602 - Do not try to download a routerdesc if we would immediately reject
16604 - Resume inserting a newline between all router descriptors when
16605 generating (old style) signed directories, since our spec says
16607 - When providing content-type application/octet-stream for
16608 server descriptors using .z, we were leaving out the
16609 content-encoding header. Oops. (Everything tolerated this just
16610 fine, but that doesn't mean we need to be part of the problem.)
16611 - Fix a potential seg fault in getconf and getinfo using version 1
16612 of the controller protocol.
16613 - Avoid crash: do not check whether DirPort is reachable when we
16614 are suppressing it because of hibernation.
16615 - Make --hash-password not crash on exit.
16618 Changes in version 0.1.1.8-alpha - 2005-10-07
16619 o New features (major):
16620 - Clients don't download or use the directory anymore. Now they
16621 download and use network-statuses from the trusted dirservers,
16622 and fetch individual server descriptors as needed from mirrors.
16623 See dir-spec.txt for all the gory details.
16624 - Be more conservative about whether to advertise our DirPort.
16625 The main change is to not advertise if we're running at capacity
16626 and either a) we could hibernate or b) our capacity is low and
16627 we're using a default DirPort.
16628 - Use OpenSSL's AES when OpenSSL has version 0.9.7 or later.
16630 o New features (minor):
16631 - Try to be smart about when to retry network-status and
16632 server-descriptor fetches. Still needs some tuning.
16633 - Stop parsing, storing, or using running-routers output (but
16634 mirrors still cache and serve it).
16635 - Consider a threshold of versioning dirservers (dirservers who have
16636 an opinion about which Tor versions are still recommended) before
16637 deciding whether to warn the user that he's obsolete.
16638 - Dirservers can now reject/invalidate by key and IP, with the
16639 config options "AuthDirInvalid" and "AuthDirReject". This is
16640 useful since currently we automatically list servers as running
16641 and usable even if we know they're jerks.
16642 - Provide dire warnings to any users who set DirServer; move it out
16643 of torrc.sample and into torrc.complete.
16644 - Add MyFamily to torrc.sample in the server section.
16645 - Add nicknames to the DirServer line, so we can refer to them
16646 without requiring all our users to memorize their IP addresses.
16647 - When we get an EOF or a timeout on a directory connection, note
16648 how many bytes of serverdesc we are dropping. This will help
16649 us determine whether it is smart to parse incomplete serverdesc
16651 - Add a new function to "change pseudonyms" -- that is, to stop
16652 using any currently-dirty circuits for new streams, so we don't
16653 link new actions to old actions. Currently it's only called on
16654 HUP (or SIGNAL RELOAD).
16655 - On sighup, if UseHelperNodes changed to 1, use new circuits.
16656 - Start using RAND_bytes rather than RAND_pseudo_bytes from
16657 OpenSSL. Also, reseed our entropy every hour, not just at
16658 startup. And entropy in 512-bit chunks, not 160-bit chunks.
16660 o Fixes on 0.1.1.7-alpha:
16661 - Nobody ever implemented EVENT_ADDRMAP for control protocol
16662 version 0, so don't let version 0 controllers ask for it.
16663 - If you requested something with too many newlines via the
16664 v1 controller protocol, you could crash tor.
16665 - Fix a number of memory leaks, including some pretty serious ones.
16666 - Re-enable DirPort testing again, so Tor servers will be willing
16667 to advertise their DirPort if it's reachable.
16668 - On TLS handshake, only check the other router's nickname against
16669 its expected nickname if is_named is set.
16671 o Fixes forward-ported from 0.1.0.15:
16672 - Don't crash when we don't have any spare file descriptors and we
16673 try to spawn a dns or cpu worker.
16674 - Make the numbers in read-history and write-history into uint64s,
16675 so they don't overflow and publish negatives in the descriptor.
16677 o Fixes on 0.1.0.x:
16678 - For the OS X package's modified privoxy config file, comment
16679 out the "logfile" line so we don't log everything passed
16681 - We were whining about using socks4 or socks5-with-local-lookup
16682 even when it's an IP in the "virtual" range we designed exactly
16684 - We were leaking some memory every time the client changes IPs.
16685 - Never call free() on tor_malloc()d memory. This will help us
16686 use dmalloc to detect memory leaks.
16687 - Check for named servers when looking them up by nickname;
16688 warn when we'recalling a non-named server by its nickname;
16689 don't warn twice about the same name.
16690 - Try to list MyFamily elements by key, not by nickname, and warn
16691 if we've not heard of the server.
16692 - Make windows platform detection (uname equivalent) smarter.
16693 - It turns out sparc64 doesn't like unaligned access either.
16696 Changes in version 0.1.0.15 - 2005-09-23
16697 o Bugfixes on 0.1.0.x:
16698 - Reject ports 465 and 587 (spam targets) in default exit policy.
16699 - Don't crash when we don't have any spare file descriptors and we
16700 try to spawn a dns or cpu worker.
16701 - Get rid of IgnoreVersion undocumented config option, and make us
16702 only warn, never exit, when we're running an obsolete version.
16703 - Don't try to print a null string when your server finds itself to
16704 be unreachable and the Address config option is empty.
16705 - Make the numbers in read-history and write-history into uint64s,
16706 so they don't overflow and publish negatives in the descriptor.
16707 - Fix a minor memory leak in smartlist_string_remove().
16708 - We were only allowing ourselves to upload a server descriptor at
16709 most every 20 minutes, even if it changed earlier than that.
16710 - Clean up log entries that pointed to old URLs.
16713 Changes in version 0.1.1.7-alpha - 2005-09-14
16714 o Fixes on 0.1.1.6-alpha:
16715 - Exit servers were crashing when people asked them to make a
16716 connection to an address not in their exit policy.
16717 - Looking up a non-existent stream for a v1 control connection would
16719 - Fix a seg fault if we ask a dirserver for a descriptor by
16720 fingerprint but he doesn't know about him.
16721 - SETCONF was appending items to linelists, not clearing them.
16722 - SETCONF SocksBindAddress killed Tor if it fails to bind. Now back
16723 out and refuse the setconf if it would fail.
16724 - Downgrade the dirserver log messages when whining about
16728 - Add Peter Palfrader's check-tor script to tor/contrib/
16729 It lets you easily check whether a given server (referenced by
16730 nickname) is reachable by you.
16731 - Numerous changes to move towards client-side v2 directories. Not
16734 o Fixes on 0.1.0.x:
16735 - If the user gave tor an odd number of command-line arguments,
16736 we were silently ignoring the last one. Now we complain and fail.
16737 [This wins the oldest-bug prize -- this bug has been present since
16738 November 2002, as released in Tor 0.0.0.]
16739 - Do not use unaligned memory access on alpha, mips, or mipsel.
16740 It *works*, but is very slow, so we treat them as if it doesn't.
16741 - Retry directory requests if we fail to get an answer we like
16742 from a given dirserver (we were retrying before, but only if
16743 we fail to connect).
16744 - When writing the RecommendedVersions line, sort them first.
16745 - When the client asked for a rendezvous port that the hidden
16746 service didn't want to provide, we were sending an IP address
16747 back along with the end cell. Fortunately, it was zero. But stop
16749 - Correct "your server is reachable" log entries to indicate that
16750 it was self-testing that told us so.
16753 Changes in version 0.1.1.6-alpha - 2005-09-09
16754 o Fixes on 0.1.1.5-alpha:
16755 - We broke fascistfirewall in 0.1.1.5-alpha. Oops.
16756 - Fix segfault in unit tests in 0.1.1.5-alpha. Oops.
16757 - Fix bug with tor_memmem finding a match at the end of the string.
16758 - Make unit tests run without segfaulting.
16759 - Resolve some solaris x86 compile warnings.
16760 - Handle duplicate lines in approved-routers files without warning.
16761 - Fix bug where as soon as a server refused any requests due to his
16762 exit policy (e.g. when we ask for localhost and he tells us that's
16763 127.0.0.1 and he won't do it), we decided he wasn't obeying his
16764 exit policy using him for any exits.
16765 - Only do openssl hardware accelerator stuff if openssl version is
16768 o New controller features/fixes:
16769 - Add a "RESETCONF" command so you can set config options like
16770 AllowUnverifiedNodes and LongLivedPorts to "". Also, if you give
16771 a config option in the torrc with no value, then it clears it
16772 entirely (rather than setting it to its default).
16773 - Add a "GETINFO config-file" to tell us where torrc is.
16774 - Avoid sending blank lines when GETINFO replies should be empty.
16775 - Add a QUIT command for the controller (for using it manually).
16776 - Fix a bug in SAVECONF that was adding default dirservers and
16777 other redundant entries to the torrc file.
16779 o Start on the new directory design:
16780 - Generate, publish, cache, serve new network-status format.
16781 - Publish individual descriptors (by fingerprint, by "all", and by
16783 - Publish client and server recommended versions separately.
16784 - Allow tor_gzip_uncompress() to handle multiple concatenated
16785 compressed strings. Serve compressed groups of router
16786 descriptors. The compression logic here could be more
16788 - Distinguish v1 authorities (all currently trusted directories)
16789 from v2 authorities (all trusted directories).
16790 - Change DirServers config line to note which dirs are v1 authorities.
16791 - Add configuration option "V1AuthoritativeDirectory 1" which
16792 moria1, moria2, and tor26 should set.
16793 - Remove option when getting directory cache to see whether they
16794 support running-routers; they all do now. Replace it with one
16795 to see whether caches support v2 stuff.
16798 - Dirservers now do their own external reachability testing of each
16799 Tor server, and only list them as running if they've been found to
16800 be reachable. We also send back warnings to the server's logs if
16801 it uploads a descriptor that we already believe is unreachable.
16802 - Implement exit enclaves: if we know an IP address for the
16803 destination, and there's a running Tor server at that address
16804 which allows exit to the destination, then extend the circuit to
16805 that exit first. This provides end-to-end encryption and end-to-end
16806 authentication. Also, if the user wants a .exit address or enclave,
16807 use 4 hops rather than 3, and cannibalize a general circ for it
16809 - Permit transitioning from ORPort=0 to ORPort!=0, and back, from the
16810 controller. Also, rotate dns and cpu workers if the controller
16811 changes options that will affect them; and initialize the dns
16812 worker cache tree whether or not we start out as a server.
16813 - Only upload a new server descriptor when options change, 18
16814 hours have passed, uptime is reset, or bandwidth changes a lot.
16815 - Check [X-]Forwarded-For headers in HTTP requests when generating
16816 log messages. This lets people run dirservers (and caches) behind
16817 Apache but still know which IP addresses are causing warnings.
16819 o Config option changes:
16820 - Replace (Fascist)Firewall* config options with a new
16821 ReachableAddresses option that understands address policies.
16822 For example, "ReachableAddresses *:80,*:443"
16823 - Get rid of IgnoreVersion undocumented config option, and make us
16824 only warn, never exit, when we're running an obsolete version.
16825 - Make MonthlyAccountingStart config option truly obsolete now.
16827 o Fixes on 0.1.0.x:
16828 - Reject ports 465 and 587 in the default exit policy, since
16829 people have started using them for spam too.
16830 - It turns out we couldn't bootstrap a network since we added
16831 reachability detection in 0.1.0.1-rc. Good thing the Tor network
16832 has never gone down. Add an AssumeReachable config option to let
16833 servers and dirservers bootstrap. When we're trying to build a
16834 high-uptime or high-bandwidth circuit but there aren't enough
16835 suitable servers, try being less picky rather than simply failing.
16836 - Our logic to decide if the OR we connected to was the right guy
16837 was brittle and maybe open to a mitm for unverified routers.
16838 - We weren't cannibalizing circuits correctly for
16839 CIRCUIT_PURPOSE_C_ESTABLISH_REND and
16840 CIRCUIT_PURPOSE_S_ESTABLISH_INTRO, so we were being forced to
16841 build those from scratch. This should make hidden services faster.
16842 - Predict required circuits better, with an eye toward making hidden
16843 services faster on the service end.
16844 - Retry streams if the exit node sends back a 'misc' failure. This
16845 should result in fewer random failures. Also, after failing
16846 from resolve failed or misc, reset the num failures, so we give
16847 it a fair shake next time we try.
16848 - Clean up the rendezvous warn log msgs, and downgrade some to info.
16849 - Reduce severity on logs about dns worker spawning and culling.
16850 - When we're shutting down and we do something like try to post a
16851 server descriptor or rendezvous descriptor, don't complain that
16852 we seem to be unreachable. Of course we are, we're shutting down.
16853 - Add TTLs to RESOLVED, CONNECTED, and END_REASON_EXITPOLICY cells.
16854 We don't use them yet, but maybe one day our DNS resolver will be
16855 able to discover them.
16856 - Make ContactInfo mandatory for authoritative directory servers.
16857 - Require server descriptors to list IPv4 addresses -- hostnames
16858 are no longer allowed. This also fixes some potential security
16859 problems with people providing hostnames as their address and then
16860 preferentially resolving them to partition users.
16861 - Change log line for unreachability to explicitly suggest /etc/hosts
16862 as the culprit. Also make it clearer what IP address and ports we're
16863 testing for reachability.
16864 - Put quotes around user-supplied strings when logging so users are
16865 more likely to realize if they add bad characters (like quotes)
16867 - Let auth dir servers start without specifying an Address config
16869 - Make unit tests (and other invocations that aren't the real Tor)
16870 run without launching listeners, creating subdirectories, and so on.
16873 Changes in version 0.1.1.5-alpha - 2005-08-08
16874 o Bugfixes included in 0.1.0.14.
16876 o Bugfixes on 0.1.0.x:
16877 - If you write "HiddenServicePort 6667 127.0.0.1 6668" in your
16878 torrc rather than "HiddenServicePort 6667 127.0.0.1:6668",
16879 it would silently using ignore the 6668.
16882 Changes in version 0.1.0.14 - 2005-08-08
16883 o Bugfixes on 0.1.0.x:
16884 - Fix the other half of the bug with crypto handshakes
16886 - Fix an assert trigger if you send a 'signal term' via the
16887 controller when it's listening for 'event info' messages.
16890 Changes in version 0.1.1.4-alpha - 2005-08-04
16891 o Bugfixes included in 0.1.0.13.
16894 - Improve tor_gettimeofday() granularity on windows.
16895 - Make clients regenerate their keys when their IP address changes.
16896 - Implement some more GETINFO goodness: expose helper nodes, config
16897 options, getinfo keys.
16900 Changes in version 0.1.0.13 - 2005-08-04
16901 o Bugfixes on 0.1.0.x:
16902 - Fix a critical bug in the security of our crypto handshakes.
16903 - Fix a size_t underflow in smartlist_join_strings2() that made
16904 it do bad things when you hand it an empty smartlist.
16905 - Fix Windows installer to ship Tor license (thanks to Aphex for
16906 pointing out this oversight) and put a link to the doc directory
16908 - Explicitly set no-unaligned-access for sparc: it turns out the
16909 new gcc's let you compile broken code, but that doesn't make it
16913 Changes in version 0.1.1.3-alpha - 2005-07-23
16914 o Bugfixes on 0.1.1.2-alpha:
16915 - Fix a bug in handling the controller's "post descriptor"
16917 - Fix several bugs in handling the controller's "extend circuit"
16919 - Fix a bug in handling the controller's "stream status" event.
16920 - Fix an assert failure if we have a controller listening for
16921 circuit events and we go offline.
16922 - Re-allow hidden service descriptors to publish 0 intro points.
16923 - Fix a crash when generating your hidden service descriptor if
16924 you don't have enough intro points already.
16926 o New features on 0.1.1.2-alpha:
16927 - New controller function "getinfo accounting", to ask how
16928 many bytes we've used in this time period.
16929 - Experimental support for helper nodes: a lot of the risk from
16930 a small static adversary comes because users pick new random
16931 nodes every time they rebuild a circuit. Now users will try to
16932 stick to the same small set of entry nodes if they can. Not
16933 enabled by default yet.
16935 o Bugfixes on 0.1.0.12:
16936 - If you're an auth dir server, always publish your dirport,
16937 even if you haven't yet found yourself to be reachable.
16938 - Fix a size_t underflow in smartlist_join_strings2() that made
16939 it do bad things when you hand it an empty smartlist.
16942 Changes in version 0.1.0.12 - 2005-07-18
16943 o New directory servers:
16944 - tor26 has changed IP address.
16946 o Bugfixes on 0.1.0.x:
16947 - Fix a possible double-free in tor_gzip_uncompress().
16948 - When --disable-threads is set, do not search for or link against
16949 pthreads libraries.
16950 - Don't trigger an assert if an authoritative directory server
16951 claims its dirport is 0.
16952 - Fix bug with removing Tor as an NT service: some people were
16953 getting "The service did not return an error." Thanks to Matt
16957 Changes in version 0.1.1.2-alpha - 2005-07-15
16958 o New directory servers:
16959 - tor26 has changed IP address.
16961 o Bugfixes on 0.1.0.x, crashes/leaks:
16962 - Port the servers-not-obeying-their-exit-policies fix from
16964 - Fix an fd leak in start_daemon().
16965 - On Windows, you can't always reopen a port right after you've
16966 closed it. So change retry_listeners() to only close and re-open
16967 ports that have changed.
16968 - Fix a possible double-free in tor_gzip_uncompress().
16970 o Bugfixes on 0.1.0.x, usability:
16971 - When tor_socketpair() fails in Windows, give a reasonable
16972 Windows-style errno back.
16973 - Let people type "tor --install" as well as "tor -install" when
16975 want to make it an NT service.
16976 - NT service patch from Matt Edman to improve error messages.
16977 - When the controller asks for a config option with an abbreviated
16978 name, give the full name in our response.
16979 - Correct the man page entry on TrackHostExitsExpire.
16980 - Looks like we were never delivering deflated (i.e. compressed)
16981 running-routers lists, even when asked. Oops.
16982 - When --disable-threads is set, do not search for or link against
16983 pthreads libraries.
16985 o Bugfixes on 0.1.1.x:
16986 - Fix a seg fault with autodetecting which controller version is
16990 - New hidden service descriptor format: put a version in it, and
16991 let people specify introduction/rendezvous points that aren't
16992 in "the directory" (which is subjective anyway).
16993 - Allow the DEBUG controller event to work again. Mark certain log
16994 entries as "don't tell this to controllers", so we avoid cycles.
16997 Changes in version 0.1.0.11 - 2005-06-30
16998 o Bugfixes on 0.1.0.x:
16999 - Fix major security bug: servers were disregarding their
17000 exit policies if clients behaved unexpectedly.
17001 - Make OS X init script check for missing argument, so we don't
17002 confuse users who invoke it incorrectly.
17003 - Fix a seg fault in "tor --hash-password foo".
17004 - The MAPADDRESS control command was broken.
17007 Changes in version 0.1.1.1-alpha - 2005-06-29
17009 - Make OS X init script check for missing argument, so we don't
17010 confuse users who invoke it incorrectly.
17011 - Fix a seg fault in "tor --hash-password foo".
17012 - Fix a possible way to DoS dirservers.
17013 - When we complain that your exit policy implicitly allows local or
17014 private address spaces, name them explicitly so operators can
17016 - Make the log message less scary when all the dirservers are
17017 temporarily unreachable.
17018 - We were printing the number of idle dns workers incorrectly when
17022 - Revised controller protocol (version 1) that uses ascii rather
17023 than binary. Add supporting libraries in python and java so you
17024 can use the controller from your applications without caring how
17025 our protocol works.
17026 - Spiffy new support for crypto hardware accelerators. Can somebody
17030 Changes in version 0.0.9.10 - 2005-06-16
17031 o Bugfixes on 0.0.9.x (backported from 0.1.0.10):
17032 - Refuse relay cells that claim to have a length larger than the
17033 maximum allowed. This prevents a potential attack that could read
17034 arbitrary memory (e.g. keys) from an exit server's process
17038 Changes in version 0.1.0.10 - 2005-06-14
17039 o Allow a few EINVALs from libevent before dying. Warn on kqueue with
17040 libevent before 1.1a.
17043 Changes in version 0.1.0.9-rc - 2005-06-09
17045 - Reset buf->highwater every time buf_shrink() is called, not just on
17046 a successful shrink. This was causing significant memory bloat.
17047 - Fix buffer overflow when checking hashed passwords.
17048 - Security fix: if seeding the RNG on Win32 fails, quit.
17049 - Allow seeding the RNG on Win32 even when you're not running as
17051 - Disable threading on Solaris too. Something is wonky with it,
17052 cpuworkers, and reentrant libs.
17053 - Reenable the part of the code that tries to flush as soon as an
17054 OR outbuf has a full TLS record available. Perhaps this will make
17055 OR outbufs not grow as huge except in rare cases, thus saving lots
17056 of CPU time plus memory.
17057 - Reject malformed .onion addresses rather then passing them on as
17058 normal web requests.
17059 - Adapt patch from Adam Langley: fix possible memory leak in
17060 tor_lookup_hostname().
17061 - Initialize libevent later in the startup process, so the logs are
17062 already established by the time we start logging libevent warns.
17063 - Use correct errno on win32 if libevent fails.
17064 - Check and warn about known-bad/slow libevent versions.
17065 - Pay more attention to the ClientOnly config option.
17066 - Have torctl.in/tor.sh.in check for location of su binary (needed
17068 - Correct/add man page entries for LongLivedPorts, ExitPolicy,
17069 KeepalivePeriod, ClientOnly, NoPublish, HttpProxy, HttpsProxy,
17070 HttpProxyAuthenticator
17071 - Stop warning about sigpipes in the logs. We're going to
17072 pretend that getting these occassionally is normal and fine.
17073 - Resolve OS X installer bugs: stop claiming to be 0.0.9.2 in
17075 installer screens; and don't put stuff into StartupItems unless
17076 the user asks you to.
17077 - Require servers that use the default dirservers to have public IP
17078 addresses. We have too many servers that are configured with private
17079 IPs and their admins never notice the log entries complaining that
17080 their descriptors are being rejected.
17081 - Add OSX uninstall instructions. An actual uninstall script will
17085 Changes in version 0.1.0.8-rc - 2005-05-23
17087 - It turns out that kqueue on OS X 10.3.9 was causing kernel
17088 panics. Disable kqueue on all OS X Tors.
17089 - Fix RPM: remove duplicate line accidentally added to the rpm
17091 - Disable threads on openbsd too, since its gethostaddr is not
17093 - Tolerate libevent 0.8 since it still works, even though it's
17095 - Enable building on Red Hat 9.0 again.
17096 - Allow the middle hop of the testing circuit to be running any
17097 version, now that most of them have the bugfix to let them connect
17098 to unknown servers. This will allow reachability testing to work
17099 even when 0.0.9.7-0.0.9.9 become obsolete.
17100 - Handle relay cells with rh.length too large. This prevents
17101 a potential attack that could read arbitrary memory (maybe even
17102 keys) from the exit server's process.
17103 - We screwed up the dirport reachability testing when we don't yet
17104 have a cached version of the directory. Hopefully now fixed.
17105 - Clean up router_load_single_router() (used by the controller),
17106 so it doesn't seg fault on error.
17107 - Fix a minor memory leak when somebody establishes an introduction
17108 point at your Tor server.
17109 - If a socks connection ends because read fails, don't warn that
17110 you're not sending a socks reply back.
17113 - Add HttpProxyAuthenticator config option too, that works like
17114 the HttpsProxyAuthenticator config option.
17115 - Encode hashed controller passwords in hex instead of base64,
17116 to make it easier to write controllers.
17119 Changes in version 0.1.0.7-rc - 2005-05-17
17121 - Fix a bug in the OS X package installer that prevented it from
17122 installing on Tiger.
17123 - Fix a script bug in the OS X package installer that made it
17124 complain during installation.
17125 - Find libevent even if it's hiding in /usr/local/ and your
17126 CFLAGS and LDFLAGS don't tell you to look there.
17127 - Be able to link with libevent as a shared library (the default
17128 after 1.0d), even if it's hiding in /usr/local/lib and even
17129 if you haven't added /usr/local/lib to your /etc/ld.so.conf,
17130 assuming you're running gcc. Otherwise fail and give a useful
17132 - Fix a bug in the RPM packager: set home directory for _tor to
17133 something more reasonable when first installing.
17134 - Free a minor amount of memory that is still reachable on exit.
17137 Changes in version 0.1.0.6-rc - 2005-05-14
17139 - Implement --disable-threads configure option. Disable threads on
17140 netbsd by default, because it appears to have no reentrant resolver
17142 - Apple's OS X 10.4.0 ships with a broken kqueue. The new libevent
17143 release (1.1) detects and disables kqueue if it's broken.
17144 - Append default exit policy before checking for implicit internal
17145 addresses. Now we don't log a bunch of complaints on startup
17146 when using the default exit policy.
17147 - Some people were putting "Address " in their torrc, and they had
17148 a buggy resolver that resolved " " to 0.0.0.0. Oops.
17149 - If DataDir is ~/.tor, and that expands to /.tor, then default to
17150 LOCALSTATEDIR/tor instead.
17151 - Fix fragmented-message bug in TorControl.py.
17152 - Resolve a minor bug which would prevent unreachable dirports
17153 from getting suppressed in the published descriptor.
17154 - When the controller gave us a new descriptor, we weren't resolving
17155 it immediately, so Tor would think its address was 0.0.0.0 until
17156 we fetched a new directory.
17157 - Fix an uppercase/lowercase case error in suppressing a bogus
17158 libevent warning on some Linuxes.
17161 - Begin scrubbing sensitive strings from logs by default. Turn off
17162 the config option SafeLogging if you need to do debugging.
17163 - Switch to a new buffer management algorithm, which tries to avoid
17164 reallocing and copying quite as much. In first tests it looks like
17165 it uses *more* memory on average, but less cpu.
17166 - First cut at support for "create-fast" cells. Clients can use
17167 these when extending to their first hop, since the TLS already
17168 provides forward secrecy and authentication. Not enabled on
17170 - When dirservers refuse a router descriptor, we now log its
17171 contactinfo, platform, and the poster's IP address.
17172 - Call tor_free_all instead of connections_free_all after forking, to
17173 save memory on systems that need to fork.
17174 - Whine at you if you're a server and you don't set your contactinfo.
17175 - Implement --verify-config command-line option to check if your torrc
17176 is valid without actually launching Tor.
17177 - Rewrite address "serifos.exit" to "localhost.serifos.exit"
17178 rather than just rejecting it.
17181 Changes in version 0.1.0.5-rc - 2005-04-27
17183 - Stop trying to print a null pointer if an OR conn fails because
17184 we didn't like its cert.
17186 - Switch our internal buffers implementation to use a ring buffer,
17187 to hopefully improve performance for fast servers a lot.
17188 - Add HttpsProxyAuthenticator support (basic auth only), based
17189 on patch from Adam Langley.
17190 - Bump the default BandwidthRate from 1 MB to 2 MB, to accommodate
17191 the fast servers that have been joining lately.
17192 - Give hidden service accesses extra time on the first attempt,
17193 since 60 seconds is often only barely enough. This might improve
17195 - Improve performance for dirservers: stop re-parsing the whole
17196 directory every time you regenerate it.
17197 - Add more debugging info to help us find the weird dns freebsd
17198 pthreads bug; cleaner debug messages to help track future issues.
17201 Changes in version 0.0.9.9 - 2005-04-23
17202 o Bugfixes on 0.0.9.x:
17203 - If unofficial Tor clients connect and send weird TLS certs, our
17204 Tor server triggers an assert. This release contains a minimal
17205 backport from the broader fix that we put into 0.1.0.4-rc.
17208 Changes in version 0.1.0.4-rc - 2005-04-23
17210 - If unofficial Tor clients connect and send weird TLS certs, our
17211 Tor server triggers an assert. Stop asserting, and start handling
17212 TLS errors better in other situations too.
17213 - When the controller asks us to tell it about all the debug-level
17214 logs, it turns out we were generating debug-level logs while
17215 telling it about them, which turns into a bad loop. Now keep
17216 track of whether you're sending a debug log to the controller,
17217 and don't log when you are.
17218 - Fix the "postdescriptor" feature of the controller interface: on
17219 non-complete success, only say "done" once.
17221 - Clients are now willing to load balance over up to 2mB, not 1mB,
17222 of advertised bandwidth capacity.
17223 - Add a NoPublish config option, so you can be a server (e.g. for
17224 testing running Tor servers in other Tor networks) without
17225 publishing your descriptor to the primary dirservers.
17228 Changes in version 0.1.0.3-rc - 2005-04-08
17229 o Improvements on 0.1.0.2-rc:
17230 - Client now retries when streams end early for 'hibernating' or
17231 'resource limit' reasons, rather than failing them.
17232 - More automated handling for dirserver operators:
17233 - Automatically approve nodes running 0.1.0.2-rc or later,
17234 now that the the reachability detection stuff is working.
17235 - Now we allow two unverified servers with the same nickname
17236 but different keys. But if a nickname is verified, only that
17237 nickname+key are allowed.
17238 - If you're an authdirserver connecting to an address:port,
17239 and it's not the OR you were expecting, forget about that
17240 descriptor. If he *was* the one you were expecting, then forget
17241 about all other descriptors for that address:port.
17242 - Allow servers to publish descriptors from 12 hours in the future.
17243 Corollary: only whine about clock skew from the dirserver if
17244 he's a trusted dirserver (since now even verified servers could
17245 have quite wrong clocks).
17246 - Adjust maximum skew and age for rendezvous descriptors: let skew
17247 be 48 hours rather than 90 minutes.
17248 - Efficiency improvements:
17249 - Keep a big splay tree of (circid,orconn)->circuit mappings to make
17250 it much faster to look up a circuit for each relay cell.
17251 - Remove most calls to assert_all_pending_dns_resolves_ok(),
17252 since they're eating our cpu on exit nodes.
17253 - Stop wasting time doing a case insensitive comparison for every
17254 dns name every time we do any lookup. Canonicalize the names to
17255 lowercase and be done with it.
17256 - Start sending 'truncated' cells back rather than destroy cells,
17257 if the circuit closes in front of you. This means we won't have
17258 to abandon partially built circuits.
17259 - Only warn once per nickname from add_nickname_list_to_smartlist
17260 per failure, so an entrynode or exitnode choice that's down won't
17262 - Put a note in the torrc about abuse potential with the default
17264 - Revise control spec and implementation to allow all log messages to
17265 be sent to controller with their severities intact (suggested by
17266 Matt Edman). Update TorControl to handle new log event types.
17267 - Provide better explanation messages when controller's POSTDESCRIPTOR
17269 - Stop putting nodename in the Platform string in server descriptors.
17270 It doesn't actually help, and it is confusing/upsetting some people.
17272 o Bugfixes on 0.1.0.2-rc:
17273 - We were printing the host mask wrong in exit policies in server
17274 descriptors. This isn't a critical bug though, since we were still
17275 obeying the exit policy internally.
17276 - Fix Tor when compiled with libevent but without pthreads: move
17277 connection_unregister() from _connection_free() to
17279 - Fix an assert trigger (already fixed in 0.0.9.x): when we have
17280 the rare mysterious case of accepting a conn on 0.0.0.0:0, then
17281 when we look through the connection array, we'll find any of the
17282 cpu/dnsworkers. This is no good.
17284 o Bugfixes on 0.0.9.8:
17285 - Fix possible bug on threading platforms (e.g. win32) which was
17286 leaking a file descriptor whenever a cpuworker or dnsworker died.
17287 - When using preferred entry or exit nodes, ignore whether the
17288 circuit wants uptime or capacity. They asked for the nodes, they
17290 - chdir() to your datadirectory at the *end* of the daemonize process,
17291 not the beginning. This was a problem because the first time you
17292 run tor, if your datadir isn't there, and you have runasdaemon set
17293 to 1, it will try to chdir to it before it tries to create it. Oops.
17294 - Handle changed router status correctly when dirserver reloads
17295 fingerprint file. We used to be dropping all unverified descriptors
17296 right then. The bug was hidden because we would immediately
17297 fetch a directory from another dirserver, which would include the
17298 descriptors we just dropped.
17299 - When we're connecting to an OR and he's got a different nickname/key
17300 than we were expecting, only complain loudly if we're an OP or a
17301 dirserver. Complaining loudly to the OR admins just confuses them.
17302 - Tie MAX_DIR_SIZE to MAX_BUF_SIZE, so now directory sizes won't get
17303 artificially capped at 500kB.
17306 Changes in version 0.0.9.8 - 2005-04-07
17307 o Bugfixes on 0.0.9.x:
17308 - We have a bug that I haven't found yet. Sometimes, very rarely,
17309 cpuworkers get stuck in the 'busy' state, even though the cpuworker
17310 thinks of itself as idle. This meant that no new circuits ever got
17311 established. Here's a workaround to kill any cpuworker that's been
17312 busy for more than 100 seconds.
17315 Changes in version 0.1.0.2-rc - 2005-04-01
17316 o Bugfixes on 0.1.0.1-rc:
17317 - Fixes on reachability detection:
17318 - Don't check for reachability while hibernating.
17319 - If ORPort is reachable but DirPort isn't, still publish the
17320 descriptor, but zero out DirPort until it's found reachable.
17321 - When building testing circs for ORPort testing, use only
17322 high-bandwidth nodes, so fewer circuits fail.
17323 - Complain about unreachable ORPort separately from unreachable
17324 DirPort, so the user knows what's going on.
17325 - Make sure we only conclude ORPort reachability if we didn't
17326 initiate the conn. Otherwise we could falsely conclude that
17327 we're reachable just because we connected to the guy earlier
17328 and he used that same pipe to extend to us.
17329 - Authdirservers shouldn't do ORPort reachability detection,
17330 since they're in clique mode, so it will be rare to find a
17331 server not already connected to them.
17332 - When building testing circuits, always pick middle hops running
17333 Tor 0.0.9.7, so we avoid the "can't extend to unknown routers"
17334 bug. (This is a kludge; it will go away when 0.0.9.x becomes
17336 - When we decide we're reachable, actually publish our descriptor
17338 - Fix bug in redirectstream in the controller.
17339 - Fix the state descriptor strings so logs don't claim edge streams
17340 are in a different state than they actually are.
17341 - Use recent libevent features when possible (this only really affects
17342 win32 and osx right now, because the new libevent with these
17343 features hasn't been released yet). Add code to suppress spurious
17345 - Prevent possible segfault in connection_close_unattached_ap().
17346 - Fix newlines on torrc in win32.
17347 - Improve error msgs when tor-resolve fails.
17349 o Improvements on 0.0.9.x:
17350 - New experimental script tor/contrib/ExerciseServer.py (needs more
17351 work) that uses the controller interface to build circuits and
17352 fetch pages over them. This will help us bootstrap servers that
17353 have lots of capacity but haven't noticed it yet.
17354 - New experimental script tor/contrib/PathDemo.py (needs more work)
17355 that uses the controller interface to let you choose whole paths
17357 "<hostname>.<path,separated by dots>.<length of path>.path"
17358 - When we've connected to an OR and handshaked but didn't like
17359 the result, we were closing the conn without sending destroy
17360 cells back for pending circuits. Now send those destroys.
17363 Changes in version 0.0.9.7 - 2005-04-01
17364 o Bugfixes on 0.0.9.x:
17365 - Fix another race crash bug (thanks to Glenn Fink for reporting).
17366 - Compare identity to identity, not to nickname, when extending to
17367 a router not already in the directory. This was preventing us from
17368 extending to unknown routers. Oops.
17369 - Make sure to create OS X Tor user in <500 range, so we aren't
17370 creating actual system users.
17371 - Note where connection-that-hasn't-sent-end was marked, and fix
17372 a few really loud instances of this harmless bug (it's fixed more
17376 Changes in version 0.1.0.1-rc - 2005-03-28
17378 - Add reachability testing. Your Tor server will automatically try
17379 to see if its ORPort and DirPort are reachable from the outside,
17380 and it won't upload its descriptor until it decides they are.
17381 - Handle unavailable hidden services better. Handle slow or busy
17382 hidden services better.
17383 - Add support for CONNECTing through https proxies, with "HttpsProxy"
17385 - New exit policy: accept most low-numbered ports, rather than
17386 rejecting most low-numbered ports.
17387 - More Tor controller support (still experimental). See
17388 http://tor.eff.org/doc/control-spec.txt for all the new features,
17389 including signals to emulate unix signals from any platform;
17390 redirectstream; extendcircuit; mapaddress; getinfo; postdescriptor;
17391 closestream; closecircuit; etc.
17392 - Make nt services work and start on startup on win32 (based on
17393 patch by Matt Edman).
17394 - Add a new AddressMap config directive to rewrite incoming socks
17395 addresses. This lets you, for example, declare an implicit
17396 required exit node for certain sites.
17397 - Add a new TrackHostExits config directive to trigger addressmaps
17398 for certain incoming socks addresses -- for sites that break when
17399 your exit keeps changing (based on patch by Mike Perry).
17400 - Redo the client-side dns cache so it's just an addressmap too.
17401 - Notice when our IP changes, and reset stats/uptime/reachability.
17402 - When an application is using socks5, give him the whole variety of
17403 potential socks5 responses (connect refused, host unreachable, etc),
17404 rather than just "success" or "failure".
17405 - A more sane version numbering system. See
17406 http://tor.eff.org/cvs/tor/doc/version-spec.txt for details.
17407 - New contributed script "exitlist": a simple python script to
17408 parse directories and find Tor nodes that exit to listed
17410 - New contributed script "privoxy-tor-toggle" to toggle whether
17411 Privoxy uses Tor. Seems to be configured for Debian by default.
17412 - Report HTTP reasons to client when getting a response from directory
17413 servers -- so you can actually know what went wrong.
17414 - New config option MaxAdvertisedBandwidth which lets you advertise
17415 a low bandwidthrate (to not attract as many circuits) while still
17416 allowing a higher bandwidthrate in reality.
17418 o Robustness/stability fixes:
17419 - Make Tor use Niels Provos's libevent instead of its current
17420 poll-but-sometimes-select mess. This will let us use faster async
17421 cores (like epoll, kpoll, and /dev/poll), and hopefully work better
17423 - pthread support now too. This was forced because when we forked,
17424 we ended up wasting a lot of duplicate ram over time. Also switch
17425 to foo_r versions of some library calls to allow reentry and
17427 - Better handling for heterogeneous / unreliable nodes:
17428 - Annotate circuits w/ whether they aim to contain high uptime nodes
17429 and/or high capacity nodes. When building circuits, choose
17431 - This means that every single node in an intro rend circuit,
17432 not just the last one, will have a minimum uptime.
17433 - New config option LongLivedPorts to indicate application streams
17434 that will want high uptime circuits.
17435 - Servers reset uptime when a dir fetch entirely fails. This
17436 hopefully reflects stability of the server's network connectivity.
17437 - If somebody starts his tor server in Jan 2004 and then fixes his
17438 clock, don't make his published uptime be a year.
17439 - Reset published uptime when you wake up from hibernation.
17440 - Introduce a notion of 'internal' circs, which are chosen without
17441 regard to the exit policy of the last hop. Intro and rendezvous
17442 circs must be internal circs, to avoid leaking information. Resolve
17443 and connect streams can use internal circs if they want.
17444 - New circuit pooling algorithm: make sure to have enough circs around
17445 to satisfy any predicted ports, and also make sure to have 2 internal
17446 circs around if we've required internal circs lately (and with high
17447 uptime if we've seen that lately too).
17448 - Split NewCircuitPeriod option into NewCircuitPeriod (30 secs),
17449 which describes how often we retry making new circuits if current
17450 ones are dirty, and MaxCircuitDirtiness (10 mins), which describes
17451 how long we're willing to make use of an already-dirty circuit.
17452 - Cannibalize GENERAL circs to be C_REND, C_INTRO, S_INTRO, and S_REND
17453 circ as necessary, if there are any completed ones lying around
17454 when we try to launch one.
17455 - Make hidden services try to establish a rendezvous for 30 seconds,
17456 rather than for n (where n=3) attempts to build a circuit.
17457 - Change SHUTDOWN_WAIT_LENGTH from a fixed 30 secs to a config option
17458 "ShutdownWaitLength".
17459 - Try to be more zealous about calling connection_edge_end when
17460 things go bad with edge conns in connection.c.
17461 - Revise tor-spec to add more/better stream end reasons.
17462 - Revise all calls to connection_edge_end to avoid sending "misc",
17463 and to take errno into account where possible.
17466 - Fix a race condition that can trigger an assert, when we have a
17467 pending create cell and an OR connection fails right then.
17468 - Fix several double-mark-for-close bugs, e.g. where we were finding
17469 a conn for a cell even if that conn is already marked for close.
17470 - Make sequence of log messages when starting on win32 with no config
17471 file more reasonable.
17472 - When choosing an exit node for a new non-internal circ, don't take
17473 into account whether it'll be useful for any pending x.onion
17474 addresses -- it won't.
17475 - Turn addr_policy_compare from a tristate to a quadstate; this should
17476 help address our "Ah, you allow 1.2.3.4:80. You are a good choice
17477 for google.com" problem.
17478 - Make "platform" string in descriptor more accurate for Win32 servers,
17479 so it's not just "unknown platform".
17480 - Fix an edge case in parsing config options (thanks weasel).
17481 If they say "--" on the commandline, it's not an option.
17482 - Reject odd-looking addresses at the client (e.g. addresses that
17483 contain a colon), rather than having the server drop them because
17485 - tor-resolve requests were ignoring .exit if there was a working circuit
17486 they could use instead.
17487 - REUSEADDR on normal platforms means you can rebind to the port
17488 right after somebody else has let it go. But REUSEADDR on win32
17489 means to let you bind to the port _even when somebody else
17490 already has it bound_! So, don't do that on Win32.
17491 - Change version parsing logic: a version is "obsolete" if it is not
17492 recommended and (1) there is a newer recommended version in the
17493 same series, or (2) there are no recommended versions in the same
17494 series, but there are some recommended versions in a newer series.
17495 A version is "new" if it is newer than any recommended version in
17497 - Stop most cases of hanging up on a socks connection without sending
17501 - Require BandwidthRate to be at least 20kB/s for servers.
17502 - When a dirserver causes you to give a warn, mention which dirserver
17504 - New config option DirAllowPrivateAddresses for authdirservers.
17505 Now by default they refuse router descriptors that have non-IP or
17506 private-IP addresses.
17507 - Stop publishing socksport in the directory, since it's not
17508 actually meant to be public. For compatibility, publish a 0 there
17510 - Change DirFetchPeriod/StatusFetchPeriod to have a special "Be
17511 smart" value, that is low for servers and high for clients.
17512 - If our clock jumps forward by 100 seconds or more, assume something
17513 has gone wrong with our network and abandon all not-yet-used circs.
17514 - Warn when exit policy implicitly allows local addresses.
17515 - If we get an incredibly skewed timestamp from a dirserver mirror
17516 that isn't a verified OR, don't warn -- it's probably him that's
17518 - Since we ship our own Privoxy on OS X, tweak it so it doesn't write
17519 cookies to disk and doesn't log each web request to disk. (Thanks
17520 to Brett Carrington for pointing this out.)
17521 - When a client asks us for a dir mirror and we don't have one,
17522 launch an attempt to get a fresh one.
17523 - If we're hibernating and we get a SIGINT, exit immediately.
17524 - Add --with-dmalloc ./configure option, to track memory leaks.
17525 - And try to free all memory on closing, so we can detect what
17527 - Cache local dns resolves correctly even when they're .exit
17529 - Give a better warning when some other server advertises an
17530 ORPort that is actually an apache running ssl.
17531 - Add "opt hibernating 1" to server descriptor to make it clearer
17532 whether the server is hibernating.
17535 Changes in version 0.0.9.6 - 2005-03-24
17536 o Bugfixes on 0.0.9.x (crashes and asserts):
17537 - Add new end stream reasons to maintainance branch. Fix bug where
17538 reason (8) could trigger an assert. Prevent bug from recurring.
17539 - Apparently win32 stat wants paths to not end with a slash.
17540 - Fix assert triggers in assert_cpath_layer_ok(), where we were
17541 blowing away the circuit that conn->cpath_layer points to, then
17542 checking to see if the circ is well-formed. Backport check to make
17543 sure we dont use the cpath on a closed connection.
17544 - Prevent circuit_resume_edge_reading_helper() from trying to package
17545 inbufs for marked-for-close streams.
17546 - Don't crash on hup if your options->address has become unresolvable.
17547 - Some systems (like OS X) sometimes accept() a connection and tell
17548 you the remote host is 0.0.0.0:0. If this happens, due to some
17549 other mis-features, we get confused; so refuse the conn for now.
17551 o Bugfixes on 0.0.9.x (other):
17552 - Fix harmless but scary "Unrecognized content encoding" warn message.
17553 - Add new stream error reason: TORPROTOCOL reason means "you are not
17554 speaking a version of Tor I understand; say bye-bye to your stream."
17555 - Be willing to cache directories from up to ROUTER_MAX_AGE seconds
17556 into the future, now that we are more tolerant of skew. This
17557 resolves a bug where a Tor server would refuse to cache a directory
17558 because all the directories it gets are too far in the future;
17559 yet the Tor server never logs any complaints about clock skew.
17560 - Mac packaging magic: make man pages useable, and do not overwrite
17561 existing torrc files.
17562 - Make OS X log happily to /var/log/tor/tor.log
17565 Changes in version 0.0.9.5 - 2005-02-22
17566 o Bugfixes on 0.0.9.x:
17567 - Fix an assert race at exit nodes when resolve requests fail.
17568 - Stop picking unverified dir mirrors--it only leads to misery.
17569 - Patch from Matt Edman to make NT services work better. Service
17570 support is still not compiled into the executable by default.
17571 - Patch from Dmitri Bely so the Tor service runs better under
17572 the win32 SYSTEM account.
17573 - Make tor-resolve actually work (?) on Win32.
17574 - Fix a sign bug when getrlimit claims to have 4+ billion
17575 file descriptors available.
17576 - Stop refusing to start when bandwidthburst == bandwidthrate.
17577 - When create cells have been on the onion queue more than five
17578 seconds, just send back a destroy and take them off the list.
17581 Changes in version 0.0.9.4 - 2005-02-03
17582 o Bugfixes on 0.0.9:
17583 - Fix an assert bug that took down most of our servers: when
17584 a server claims to have 1 GB of bandwidthburst, don't
17586 - Don't crash as badly if we have spawned the max allowed number
17587 of dnsworkers, or we're out of file descriptors.
17588 - Block more file-sharing ports in the default exit policy.
17589 - MaxConn is now automatically set to the hard limit of max
17590 file descriptors we're allowed (ulimit -n), minus a few for
17592 - Give a clearer message when servers need to raise their
17593 ulimit -n when they start running out of file descriptors.
17594 - SGI Compatibility patches from Jan Schaumann.
17595 - Tolerate a corrupt cached directory better.
17596 - When a dirserver hasn't approved your server, list which one.
17597 - Go into soft hibernation after 95% of the bandwidth is used,
17598 not 99%. This is especially important for daily hibernators who
17599 have a small accounting max. Hopefully it will result in fewer
17600 cut connections when the hard hibernation starts.
17601 - Load-balance better when using servers that claim more than
17602 800kB/s of capacity.
17603 - Make NT services work (experimental, only used if compiled in).
17606 Changes in version 0.0.9.3 - 2005-01-21
17607 o Bugfixes on 0.0.9:
17608 - Backport the cpu use fixes from main branch, so busy servers won't
17609 need as much processor time.
17610 - Work better when we go offline and then come back, or when we
17611 run Tor at boot before the network is up. We do this by
17612 optimistically trying to fetch a new directory whenever an
17613 application request comes in and we think we're offline -- the
17614 human is hopefully a good measure of when the network is back.
17615 - Backport some minimal hidserv bugfixes: keep rend circuits open as
17616 long as you keep using them; actually publish hidserv descriptors
17617 shortly after they change, rather than waiting 20-40 minutes.
17618 - Enable Mac startup script by default.
17619 - Fix duplicate dns_cancel_pending_resolve reported by Giorgos Pallas.
17620 - When you update AllowUnverifiedNodes or FirewallPorts via the
17621 controller's setconf feature, we were always appending, never
17623 - When you update HiddenServiceDir via setconf, it was screwing up
17624 the order of reading the lines, making it fail.
17625 - Do not rewrite a cached directory back to the cache; otherwise we
17626 will think it is recent and not fetch a newer one on startup.
17627 - Workaround for webservers that lie about Content-Encoding: Tor
17628 now tries to autodetect compressed directories and compression
17629 itself. This lets us Proxypass dir fetches through apache.
17632 Changes in version 0.0.9.2 - 2005-01-04
17633 o Bugfixes on 0.0.9 (crashes and asserts):
17634 - Fix an assert on startup when the disk is full and you're logging
17636 - If you do socks4 with an IP of 0.0.0.x but *don't* provide a socks4a
17637 style address, then we'd crash.
17638 - Fix an assert trigger when the running-routers string we get from
17639 a dirserver is broken.
17640 - Make worker threads start and run on win32. Now win32 servers
17642 - Bandaid (not actually fix, but now it doesn't crash) an assert
17643 where the dns worker dies mysteriously and the main Tor process
17644 doesn't remember anything about the address it was resolving.
17646 o Bugfixes on 0.0.9 (Win32):
17647 - Workaround for brain-damaged __FILE__ handling on MSVC: keep Nick's
17648 name out of the warning/assert messages.
17649 - Fix a superficial "unhandled error on read" bug on win32.
17650 - The win32 installer no longer requires a click-through for our
17651 license, since our Free Software license grants rights but does not
17653 - Win32: When connecting to a dirserver fails, try another one
17654 immediately. (This was already working for non-win32 Tors.)
17655 - Stop trying to parse $HOME on win32 when hunting for default
17657 - Make tor-resolve.c work on win32 by calling network_init().
17659 o Bugfixes on 0.0.9 (other):
17660 - Make 0.0.9.x build on Solaris again.
17661 - Due to a fencepost error, we were blowing away the \n when reporting
17662 confvalue items in the controller. So asking for multiple config
17663 values at once couldn't work.
17664 - When listing circuits that are pending on an opening OR connection,
17665 if we're an OR we were listing circuits that *end* at us as
17666 being pending on every listener, dns/cpu worker, etc. Stop that.
17667 - Dirservers were failing to create 'running-routers' or 'directory'
17668 strings if we had more than some threshold of routers. Fix them so
17669 they can handle any number of routers.
17670 - Fix a superficial "Duplicate mark for close" bug.
17671 - Stop checking for clock skew for OR connections, even for servers.
17672 - Fix a fencepost error that was chopping off the last letter of any
17673 nickname that is the maximum allowed nickname length.
17674 - Update URLs in log messages so they point to the new website.
17675 - Fix a potential problem in mangling server private keys while
17676 writing to disk (not triggered yet, as far as we know).
17677 - Include the licenses for other free software we include in Tor,
17678 now that we're shipping binary distributions more regularly.
17681 Changes in version 0.0.9.1 - 2004-12-15
17682 o Bugfixes on 0.0.9:
17683 - Make hibernation actually work.
17684 - Make HashedControlPassword config option work.
17685 - When we're reporting event circuit status to a controller,
17686 don't use the stream status code.
17689 Changes in version 0.0.9 - 2004-12-12
17691 - Clean up manpage and torrc.sample file.
17692 - Clean up severities and text of log warnings.
17694 - Make servers trigger an assert when they enter hibernation.
17697 Changes in version 0.0.9rc7 - 2004-12-08
17698 o Bugfixes on 0.0.9rc:
17699 - Fix a stack-trashing crash when an exit node begins hibernating.
17700 - Avoid looking at unallocated memory while considering which
17701 ports we need to build circuits to cover.
17702 - Stop a sigpipe: when an 'end' cell races with eof from the app,
17703 we shouldn't hold-open-until-flush if the eof arrived first.
17704 - Fix a bug with init_cookie_authentication() in the controller.
17705 - When recommending new-format log lines, if the upper bound is
17706 LOG_ERR, leave it implicit.
17708 o Bugfixes on 0.0.8.1:
17709 - Fix a whole slew of memory leaks.
17710 - Fix isspace() and friends so they still make Solaris happy
17711 but also so they don't trigger asserts on win32.
17712 - Fix parse_iso_time on platforms without strptime (eg win32).
17713 - win32: tolerate extra "readable" events better.
17714 - win32: when being multithreaded, leave parent fdarray open.
17715 - Make unit tests work on win32.
17718 Changes in version 0.0.9rc6 - 2004-12-06
17719 o Bugfixes on 0.0.9pre:
17720 - Clean up some more integer underflow opportunities (not exploitable
17722 - While hibernating, hup should not regrow our listeners.
17723 - Send an end to the streams we close when we hibernate, rather
17724 than just chopping them off.
17725 - React to eof immediately on non-open edge connections.
17727 o Bugfixes on 0.0.8.1:
17728 - Calculate timeout for waiting for a connected cell from the time
17729 we sent the begin cell, not from the time the stream started. If
17730 it took a long time to establish the circuit, we would time out
17731 right after sending the begin cell.
17732 - Fix router_compare_addr_to_addr_policy: it was not treating a port
17733 of * as always matching, so we were picking reject *:* nodes as
17734 exit nodes too. Oops.
17737 - New circuit building strategy: keep a list of ports that we've
17738 used in the past 6 hours, and always try to have 2 circuits open
17739 or on the way that will handle each such port. Seed us with port
17740 80 so web users won't complain that Tor is "slow to start up".
17741 - Make kill -USR1 dump more useful stats about circuits.
17742 - When warning about retrying or giving up, print the address, so
17743 the user knows which one it's talking about.
17744 - If you haven't used a clean circuit in an hour, throw it away,
17745 just to be on the safe side. (This means after 6 hours a totally
17746 unused Tor client will have no circuits open.)
17749 Changes in version 0.0.9rc5 - 2004-12-01
17750 o Bugfixes on 0.0.8.1:
17751 - Disallow NDEBUG. We don't ever want anybody to turn off debug.
17752 - Let resolve conns retry/expire also, rather than sticking around
17754 - If we are using select, make sure we stay within FD_SETSIZE.
17756 o Bugfixes on 0.0.9pre:
17757 - Fix integer underflow in tor_vsnprintf() that may be exploitable,
17758 but doesn't seem to be currently; thanks to Ilja van Sprundel for
17760 - If anybody set DirFetchPostPeriod, give them StatusFetchPeriod
17761 instead. Impose minima and maxima for all *Period options; impose
17762 even tighter maxima for fetching if we are a caching dirserver.
17763 Clip rather than rejecting.
17764 - Fetch cached running-routers from servers that serve it (that is,
17765 authdirservers and servers running 0.0.9rc5-cvs or later.)
17768 - Accept *:706 (silc) in default exit policy.
17769 - Implement new versioning format for post 0.1.
17770 - Support "foo.nickname.exit" addresses, to let Alice request the
17771 address "foo" as viewed by exit node "nickname". Based on a patch
17773 - Make tor --version --version dump the cvs Id of every file.
17776 Changes in version 0.0.9rc4 - 2004-11-28
17777 o Bugfixes on 0.0.8.1:
17778 - Make windows sockets actually non-blocking (oops), and handle
17779 win32 socket errors better.
17781 o Bugfixes on 0.0.9rc1:
17782 - Actually catch the -USR2 signal.
17785 Changes in version 0.0.9rc3 - 2004-11-25
17786 o Bugfixes on 0.0.8.1:
17787 - Flush the log file descriptor after we print "Tor opening log file",
17788 so we don't see those messages days later.
17790 o Bugfixes on 0.0.9rc1:
17791 - Make tor-resolve work again.
17792 - Avoid infinite loop in tor-resolve if tor hangs up on it.
17793 - Fix an assert trigger for clients/servers handling resolves.
17796 Changes in version 0.0.9rc2 - 2004-11-24
17797 o Bugfixes on 0.0.9rc1:
17798 - I broke socks5 support while fixing the eof bug.
17799 - Allow unitless bandwidths and intervals; they default to bytes
17801 - New servers don't start out hibernating; they are active until
17802 they run out of bytes, so they have a better estimate of how
17803 long it takes, and so their operators can know they're working.
17806 Changes in version 0.0.9rc1 - 2004-11-23
17807 o Bugfixes on 0.0.8.1:
17808 - Finally fix a bug that's been plaguing us for a year:
17809 With high load, circuit package window was reaching 0. Whenever
17810 we got a circuit-level sendme, we were reading a lot on each
17811 socket, but only writing out a bit. So we would eventually reach
17812 eof. This would be noticed and acted on even when there were still
17813 bytes sitting in the inbuf.
17814 - When poll() is interrupted, we shouldn't believe the revents values.
17816 o Bugfixes on 0.0.9pre6:
17817 - Fix hibernate bug that caused pre6 to be broken.
17818 - Don't keep rephist info for routers that haven't had activity for
17819 24 hours. (This matters now that clients have keys, since we track
17821 - Never call close_temp_logs while validating log options.
17822 - Fix backslash-escaping on tor.sh.in and torctl.in.
17825 - Implement weekly/monthly/daily accounting: now you specify your
17826 hibernation properties by
17827 AccountingMax N bytes|KB|MB|GB|TB
17828 AccountingStart day|week|month [day] HH:MM
17829 Defaults to "month 1 0:00".
17830 - Let bandwidth and interval config options be specified as 5 bytes,
17831 kb, kilobytes, etc; and as seconds, minutes, hours, days, weeks.
17832 - kill -USR2 now moves all logs to loglevel debug (kill -HUP to
17833 get back to normal.)
17834 - If your requested entry or exit node has advertised bandwidth 0,
17836 - Be more greedy about filling up relay cells -- we try reading again
17837 once we've processed the stuff we read, in case enough has arrived
17838 to fill the last cell completely.
17839 - Apply NT service patch from Osamu Fujino. Still needs more work.
17842 Changes in version 0.0.9pre6 - 2004-11-15
17843 o Bugfixes on 0.0.8.1:
17844 - Fix assert failure on malformed socks4a requests.
17845 - Use identity comparison, not nickname comparison, to choose which
17846 half of circuit-ID-space each side gets to use. This is needed
17847 because sometimes we think of a router as a nickname, and sometimes
17848 as a hex ID, and we can't predict what the other side will do.
17849 - Catch and ignore SIGXFSZ signals when log files exceed 2GB; our
17850 write() call will fail and we handle it there.
17851 - Add a FAST_SMARTLIST define to optionally inline smartlist_get
17852 and smartlist_len, which are two major profiling offenders.
17854 o Bugfixes on 0.0.9pre5:
17855 - Fix a bug in read_all that was corrupting config files on windows.
17856 - When we're raising the max number of open file descriptors to
17857 'unlimited', don't log that we just raised it to '-1'.
17858 - Include event code with events, as required by control-spec.txt.
17859 - Don't give a fingerprint when clients do --list-fingerprint:
17860 it's misleading, because it will never be the same again.
17861 - Stop using strlcpy in tor_strndup, since it was slowing us
17863 - Remove warn on startup about missing cached-directory file.
17864 - Make kill -USR1 work again.
17865 - Hibernate if we start tor during the "wait for wakeup-time" phase
17866 of an accounting interval. Log our hibernation plans better.
17867 - Authoritative dirservers now also cache their directory, so they
17868 have it on start-up.
17871 - Fetch running-routers; cache running-routers; compress
17872 running-routers; serve compressed running-routers.z
17873 - Add NSI installer script contributed by J Doe.
17874 - Commit VC6 and VC7 workspace/project files.
17875 - Commit a tor.spec for making RPM files, with help from jbash.
17876 - Add contrib/torctl.in contributed by Glenn Fink.
17877 - Implement the control-spec's SAVECONF command, to write your
17878 configuration to torrc.
17879 - Get cookie authentication for the controller closer to working.
17880 - Include control-spec.txt in the tarball.
17881 - When set_conf changes our server descriptor, upload a new copy.
17882 But don't upload it too often if there are frequent changes.
17883 - Document authentication config in man page, and document signals
17885 - Clean up confusing parts of man page and torrc.sample.
17886 - Make expand_filename handle ~ and ~username.
17887 - Use autoconf to enable largefile support where necessary. Use
17888 ftello where available, since ftell can fail at 2GB.
17889 - Distinguish between TOR_TLS_CLOSE and TOR_TLS_ERROR, so we can
17890 log more informatively.
17891 - Give a slightly more useful output for "tor -h".
17892 - Refuse application socks connections to port 0.
17893 - Check clock skew for verified servers, but allow unverified
17894 servers and clients to have any clock skew.
17895 - Break DirFetchPostPeriod into:
17896 - DirFetchPeriod for fetching full directory,
17897 - StatusFetchPeriod for fetching running-routers,
17898 - DirPostPeriod for posting server descriptor,
17899 - RendPostPeriod for posting hidden service descriptors.
17900 - Make sure the hidden service descriptors are at a random offset
17901 from each other, to hinder linkability.
17904 Changes in version 0.0.9pre5 - 2004-11-09
17905 o Bugfixes on 0.0.9pre4:
17906 - Fix a seg fault in unit tests (doesn't affect main program).
17907 - Fix an assert bug where a hidden service provider would fail if
17908 the first hop of his rendezvous circuit was down.
17909 - Hidden service operators now correctly handle version 1 style
17910 INTRODUCE1 cells (nobody generates them still, so not a critical
17912 - If do_hup fails, actually notice.
17913 - Handle more errnos from accept() without closing the listener.
17914 Some OpenBSD machines were closing their listeners because
17915 they ran out of file descriptors.
17916 - Send resolve cells to exit routers that are running a new
17917 enough version of the resolve code to work right.
17918 - Better handling of winsock includes on non-MSV win32 compilers.
17919 - Some people had wrapped their tor client/server in a script
17920 that would restart it whenever it died. This did not play well
17921 with our "shut down if your version is obsolete" code. Now people
17922 don't fetch a new directory if their local cached version is
17924 - Make our autogen.sh work on ksh as well as bash.
17927 - Hibernation: New config option "AccountingMaxKB" lets you
17928 set how many KBytes per month you want to allow your server to
17929 consume. Rather than spreading those bytes out evenly over the
17930 month, we instead hibernate for some of the month and pop up
17931 at a deterministic time, work until the bytes are consumed, then
17932 hibernate again. Config option "MonthlyAccountingStart" lets you
17933 specify which day of the month your billing cycle starts on.
17934 - Control interface: a separate program can now talk to your
17935 client/server over a socket, and get/set config options, receive
17936 notifications of circuits and streams starting/finishing/dying,
17937 bandwidth used, etc. The next step is to get some GUIs working.
17938 Let us know if you want to help out. See doc/control-spec.txt .
17939 - Ship a contrib/tor-control.py as an example script to interact
17940 with the control port.
17941 - "tor --hash-password zzyxz" will output a salted password for
17942 use in authenticating to the control interface.
17943 - New log format in config:
17944 "Log minsev[-maxsev] stdout|stderr|syslog" or
17945 "Log minsev[-maxsev] file /var/foo"
17948 - DirPolicy config option, to let people reject incoming addresses
17949 from their dirserver.
17950 - "tor --list-fingerprint" will list your identity key fingerprint
17952 - Add "pass" target for RedirectExit, to make it easier to break
17953 out of a sequence of RedirectExit rules.
17954 - Clients now generate a TLS cert too, in preparation for having
17955 them act more like real nodes.
17956 - Ship src/win32/ in the tarball, so people can use it to build.
17957 - Make old win32 fall back to CWD if SHGetSpecialFolderLocation
17959 - New "router-status" line in directory, to better bind each verified
17960 nickname to its identity key.
17961 - Deprecate unofficial config option abbreviations, and abbreviations
17962 not on the command line.
17963 - Add a pure-C tor-resolve implementation.
17964 - Use getrlimit and friends to ensure we can reach MaxConn (currently
17965 1024) file descriptors.
17967 o Code security improvements, inspired by Ilja:
17968 - Replace sprintf with snprintf. (I think they were all safe, but
17970 - Replace strcpy/strncpy with strlcpy in more places.
17971 - Avoid strcat; use snprintf or strlcat instead.
17972 - snprintf wrapper with consistent (though not C99) overflow behavior.
17975 Changes in version 0.0.9pre4 - 2004-10-17
17976 o Bugfixes on 0.0.9pre3:
17977 - If the server doesn't specify an exit policy, use the real default
17978 exit policy, not reject *:*.
17979 - Ignore fascistfirewall when uploading/downloading hidden service
17980 descriptors, since we go through Tor for those; and when using
17981 an HttpProxy, since we assume it can reach them all.
17982 - When looking for an authoritative dirserver, use only the ones
17983 configured at boot. Don't bother looking in the directory.
17984 - The rest of the fix for get_default_conf_file() on older win32.
17985 - Make 'Routerfile' config option obsolete.
17988 - New 'MyFamily nick1,...' config option for a server to
17989 specify other servers that shouldn't be used in the same circuit
17990 with it. Only believed if nick1 also specifies us.
17991 - New 'NodeFamily nick1,nick2,...' config option for a client to
17992 specify nodes that it doesn't want to use in the same circuit.
17993 - New 'Redirectexit pattern address:port' config option for a
17994 server to redirect exit connections, e.g. to a local squid.
17997 Changes in version 0.0.9pre3 - 2004-10-13
17998 o Bugfixes on 0.0.8.1:
17999 - Better torrc example lines for dirbindaddress and orbindaddress.
18000 - Improved bounds checking on parsed ints (e.g. config options and
18001 the ones we find in directories.)
18002 - Better handling of size_t vs int, so we're more robust on 64
18004 - Fix the rest of the bug where a newly started OR would appear
18005 as unverified even after we've added his fingerprint and hupped
18007 - Fix a bug from 0.0.7: when read() failed on a stream, we would
18008 close it without sending back an end. So 'connection refused'
18009 would simply be ignored and the user would get no response.
18011 o Bugfixes on 0.0.9pre2:
18012 - Serving the cached-on-disk directory to people is bad. We now
18013 provide no directory until we've fetched a fresh one.
18014 - Workaround for bug on windows where cached-directories get crlf
18016 - Make get_default_conf_file() work on older windows too.
18017 - If we write a *:* exit policy line in the descriptor, don't write
18018 any more exit policy lines.
18021 - Use only 0.0.9pre1 and later servers for resolve cells.
18022 - Make the dirservers file obsolete.
18023 - Include a dir-signing-key token in directories to tell the
18024 parsing entity which key is being used to sign.
18025 - Remove the built-in bulky default dirservers string.
18026 - New config option "Dirserver %s:%d [fingerprint]", which can be
18027 repeated as many times as needed. If no dirservers specified,
18028 default to moria1,moria2,tor26.
18029 - Make moria2 advertise a dirport of 80, so people behind firewalls
18030 will be able to get a directory.
18031 - Http proxy support
18032 - Dirservers translate requests for http://%s:%d/x to /x
18033 - You can specify "HttpProxy %s[:%d]" and all dir fetches will
18034 be routed through this host.
18035 - Clients ask for /tor/x rather than /x for new enough dirservers.
18036 This way we can one day coexist peacefully with apache.
18037 - Clients specify a "Host: %s%d" http header, to be compatible
18038 with more proxies, and so running squid on an exit node can work.
18041 Changes in version 0.0.8.1 - 2004-10-13
18043 - Fix a seg fault that can be triggered remotely for Tor
18044 clients/servers with an open dirport.
18045 - Fix a rare assert trigger, where routerinfos for entries in
18046 our cpath would expire while we're building the path.
18047 - Fix a bug in OutboundBindAddress so it (hopefully) works.
18048 - Fix a rare seg fault for people running hidden services on
18049 intermittent connections.
18050 - Fix a bug in parsing opt keywords with objects.
18051 - Fix a stale pointer assert bug when a stream detaches and
18053 - Fix a string format vulnerability (probably not exploitable)
18054 in reporting stats locally.
18055 - Fix an assert trigger: sometimes launching circuits can fail
18056 immediately, e.g. because too many circuits have failed recently.
18057 - Fix a compile warning on 64 bit platforms.
18060 Changes in version 0.0.9pre2 - 2004-10-03
18062 - Make fetching a cached directory work for 64-bit platforms too.
18063 - Make zlib.h a required header, not an optional header.
18066 Changes in version 0.0.9pre1 - 2004-10-01
18068 - Stop using separate defaults for no-config-file and
18069 empty-config-file. Now you have to explicitly turn off SocksPort,
18070 if you don't want it open.
18071 - Fix a bug in OutboundBindAddress so it (hopefully) works.
18072 - Improve man page to mention more of the 0.0.8 features.
18073 - Fix a rare seg fault for people running hidden services on
18074 intermittent connections.
18075 - Change our file IO stuff (especially wrt OpenSSL) so win32 is
18077 - Fix more dns related bugs: send back resolve_failed and end cells
18078 more reliably when the resolve fails, rather than closing the
18079 circuit and then trying to send the cell. Also attach dummy resolve
18080 connections to a circuit *before* calling dns_resolve(), to fix
18081 a bug where cached answers would never be sent in RESOLVED cells.
18082 - When we run out of disk space, or other log writing error, don't
18083 crash. Just stop logging to that log and continue.
18084 - We were starting to daemonize before we opened our logs, so if
18085 there were any problems opening logs, we would complain to stderr,
18086 which wouldn't work, and then mysteriously exit.
18087 - Fix a rare bug where sometimes a verified OR would connect to us
18088 before he'd uploaded his descriptor, which would cause us to
18089 assign conn->nickname as though he's unverified. Now we look through
18090 the fingerprint list to see if he's there.
18091 - Fix a rare assert trigger, where routerinfos for entries in
18092 our cpath would expire while we're building the path.
18095 - Clients can ask dirservers for /dir.z to get a compressed version
18096 of the directory. Only works for servers running 0.0.9, of course.
18097 - Make clients cache directories and use them to seed their router
18098 lists at startup. This means clients have a datadir again.
18099 - Configuration infrastructure support for warning on obsolete
18101 - Respond to content-encoding headers by trying to uncompress as
18103 - Reply with a deflated directory when a client asks for "dir.z".
18104 We could use allow-encodings instead, but allow-encodings isn't
18105 specified in HTTP 1.0.
18106 - Raise the max dns workers from 50 to 100.
18107 - Discourage people from setting their dirfetchpostperiod more often
18108 than once per minute.
18109 - Protect dirservers from overzealous descriptor uploading -- wait
18110 10 seconds after directory gets dirty, before regenerating.
18113 Changes in version 0.0.8 - 2004-08-25
18114 o Port it to SunOS 5.9 / Athena
18117 Changes in version 0.0.8rc2 - 2004-08-20
18118 o Make it compile on cygwin again.
18119 o When picking unverified routers, skip those with low uptime and/or
18120 low bandwidth, depending on what properties you care about.
18123 Changes in version 0.0.8rc1 - 2004-08-18
18124 o Changes from 0.0.7.3:
18126 - Fix assert triggers: if the other side returns an address 0.0.0.0,
18127 don't put it into the client dns cache.
18128 - If a begin failed due to exit policy, but we believe the IP address
18129 should have been allowed, switch that router to exitpolicy reject *:*
18130 until we get our next directory.
18132 - Clients choose nodes proportional to advertised bandwidth.
18133 - Avoid using nodes with low uptime as introduction points.
18134 - Handle servers with dynamic IP addresses: don't replace
18135 options->Address with the resolved one at startup, and
18136 detect our address right before we make a routerinfo each time.
18137 - 'FascistFirewall' option to pick dirservers and ORs on specific
18138 ports; plus 'FirewallPorts' config option to tell FascistFirewall
18139 which ports are open. (Defaults to 80,443)
18140 - Be more aggressive about trying to make circuits when the network
18141 has changed (e.g. when you unsuspend your laptop).
18142 - Check for time skew on http headers; report date in response to
18144 - If the entrynode config line has only one node, don't pick it as
18146 - Add strict{entry|exit}nodes config options. If set to 1, then
18147 we refuse to build circuits that don't include the specified entry
18149 - OutboundBindAddress config option, to bind to a specific
18150 IP address for outgoing connect()s.
18151 - End truncated log entries (e.g. directories) with "[truncated]".
18153 o Patches to 0.0.8preX:
18155 - Patches to compile and run on win32 again (maybe)?
18156 - Fix crash when looking for ~/.torrc with no $HOME set.
18157 - Fix a race bug in the unit tests.
18158 - Handle verified/unverified name collisions better when new
18159 routerinfo's arrive in a directory.
18160 - Sometimes routers were getting entered into the stats before
18161 we'd assigned their identity_digest. Oops.
18162 - Only pick and establish intro points after we've gotten a
18165 - AllowUnverifiedNodes config option to let circuits choose no-name
18166 routers in entry,middle,exit,introduction,rendezvous positions.
18167 Allow middle and rendezvous positions by default.
18168 - Add a man page for tor-resolve.
18171 Changes in version 0.0.7.3 - 2004-08-12
18172 o Stop dnsworkers from triggering an assert failure when you
18173 ask them to resolve the host "".
18176 Changes in version 0.0.8pre3 - 2004-08-09
18177 o Changes from 0.0.7.2:
18178 - Allow multiple ORs with same nickname in routerlist -- now when
18179 people give us one identity key for a nickname, then later
18180 another, we don't constantly complain until the first expires.
18181 - Remember used bandwidth (both in and out), and publish 15-minute
18182 snapshots for the past day into our descriptor.
18183 - You can now fetch $DIRURL/running-routers to get just the
18184 running-routers line, not the whole descriptor list. (But
18185 clients don't use this yet.)
18186 - When people mistakenly use Tor as an http proxy, point them
18187 at the tor-doc.html rather than the INSTALL.
18188 - Remove our mostly unused -- and broken -- hex_encode()
18189 function. Use base16_encode() instead. (Thanks to Timo Lindfors
18190 for pointing out this bug.)
18191 - Rotate onion keys every 12 hours, not every 2 hours, so we have
18192 fewer problems with people using the wrong key.
18193 - Change the default exit policy to reject the default edonkey,
18194 kazaa, gnutella ports.
18195 - Add replace_file() to util.[ch] to handle win32's rename().
18197 o Changes from 0.0.8preX:
18198 - Fix two bugs in saving onion keys to disk when rotating, so
18199 hopefully we'll get fewer people using old onion keys.
18200 - Fix an assert error that was making SocksPolicy not work.
18201 - Be willing to expire routers that have an open dirport -- it's
18202 just the authoritative dirservers we want to not forget.
18203 - Reject tor-resolve requests for .onion addresses early, so we
18204 don't build a whole rendezvous circuit and then fail.
18205 - When you're warning a server that he's unverified, don't cry
18206 wolf unpredictably.
18207 - Fix a race condition: don't try to extend onto a connection
18208 that's still handshaking.
18209 - For servers in clique mode, require the conn to be open before
18210 you'll choose it for your path.
18211 - Fix some cosmetic bugs about duplicate mark-for-close, lack of
18212 end relay cell, etc.
18213 - Measure bandwidth capacity over the last 24 hours, not just 12
18214 - Bugfix: authoritative dirservers were making and signing a new
18215 directory for each client, rather than reusing the cached one.
18218 Changes in version 0.0.8pre2 - 2004-08-04
18219 o Changes from 0.0.7.2:
18221 - Check directory signature _before_ you decide whether you're
18222 you're running an obsolete version and should exit.
18223 - Check directory signature _before_ you parse the running-routers
18224 list to decide who's running or verified.
18225 - Bugfixes and features:
18226 - Check return value of fclose while writing to disk, so we don't
18227 end up with broken files when servers run out of disk space.
18228 - Log a warning if the user uses an unsafe socks variant, so people
18229 are more likely to learn about privoxy or socat.
18230 - Dirservers now include RFC1123-style dates in the HTTP headers,
18231 which one day we will use to better detect clock skew.
18233 o Changes from 0.0.8pre1:
18234 - Make it compile without warnings again on win32.
18235 - Log a warning if you're running an unverified server, to let you
18236 know you might want to get it verified.
18237 - Only pick a default nickname if you plan to be a server.
18240 Changes in version 0.0.8pre1 - 2004-07-23
18242 - Made our unit tests compile again on OpenBSD 3.5, and tor
18243 itself compile again on OpenBSD on a sparc64.
18244 - We were neglecting milliseconds when logging on win32, so
18245 everything appeared to happen at the beginning of each second.
18247 o Protocol changes:
18248 - 'Extend' relay cell payloads now include the digest of the
18249 intended next hop's identity key. Now we can verify that we're
18250 extending to the right router, and also extend to routers we
18251 hadn't heard of before.
18254 - Tor nodes can now act as relays (with an advertised ORPort)
18255 without being manually verified by the dirserver operators.
18256 - Uploaded descriptors of unverified routers are now accepted
18257 by the dirservers, and included in the directory.
18258 - Verified routers are listed by nickname in the running-routers
18259 list; unverified routers are listed as "$<fingerprint>".
18260 - We now use hash-of-identity-key in most places rather than
18261 nickname or addr:port, for improved security/flexibility.
18262 - To avoid Sybil attacks, paths still use only verified servers.
18263 But now we have a chance to play around with hybrid approaches.
18264 - Nodes track bandwidth usage to estimate capacity (not used yet).
18265 - ClientOnly option for nodes that never want to become servers.
18266 - Directory caching.
18267 - "AuthoritativeDir 1" option for the official dirservers.
18268 - Now other nodes (clients and servers) will cache the latest
18269 directory they've pulled down.
18270 - They can enable their DirPort to serve it to others.
18271 - Clients will pull down a directory from any node with an open
18272 DirPort, and check the signature/timestamp correctly.
18273 - Authoritative dirservers now fetch directories from other
18274 authdirservers, to stay better synced.
18275 - Running-routers list tells who's down also, along with noting
18276 if they're verified (listed by nickname) or unverified (listed
18278 - Allow dirservers to serve running-router list separately.
18279 This isn't used yet.
18280 - ORs connect-on-demand to other ORs
18281 - If you get an extend cell to an OR you're not connected to,
18282 connect, handshake, and forward the create cell.
18283 - The authoritative dirservers stay connected to everybody,
18284 and everybody stays connected to 0.0.7 servers, but otherwise
18285 clients/servers expire unused connections after 5 minutes.
18286 - When servers get a sigint, they delay 30 seconds (refusing new
18287 connections) then exit. A second sigint causes immediate exit.
18288 - File and name management:
18289 - Look for .torrc if no CONFDIR "torrc" is found.
18290 - If no datadir is defined, then choose, make, and secure ~/.tor
18292 - If torrc not found, exitpolicy reject *:*.
18293 - Expands ~/ in filenames to $HOME/ (but doesn't yet expand ~arma).
18294 - If no nickname is defined, derive default from hostname.
18295 - Rename secret key files, e.g. identity.key -> secret_id_key,
18296 to discourage people from mailing their identity key to tor-ops.
18297 - Refuse to build a circuit before the directory has arrived --
18298 it won't work anyway, since you won't know the right onion keys
18300 - Try other dirservers immediately if the one you try is down. This
18301 should tolerate down dirservers better now.
18302 - Parse tor version numbers so we can do an is-newer-than check
18303 rather than an is-in-the-list check.
18304 - New socks command 'resolve', to let us shim gethostbyname()
18306 - A 'tor_resolve' script to access the socks resolve functionality.
18307 - A new socks-extensions.txt doc file to describe our
18308 interpretation and extensions to the socks protocols.
18309 - Add a ContactInfo option, which gets published in descriptor.
18310 - Publish OR uptime in descriptor (and thus in directory) too.
18311 - Write tor version at the top of each log file
18312 - New docs in the tarball:
18314 - Document that you should proxy your SSL traffic too.
18317 Changes in version 0.0.7.2 - 2004-07-07
18318 o A better fix for the 0.0.0.0 problem, that will hopefully
18319 eliminate the remaining related assertion failures.
18322 Changes in version 0.0.7.1 - 2004-07-04
18323 o When an address resolves to 0.0.0.0, treat it as a failed resolve,
18324 since internally we use 0.0.0.0 to signify "not yet resolved".
18327 Changes in version 0.0.7 - 2004-06-07
18328 o Updated the man page to reflect the new features.
18331 Changes in version 0.0.7rc2 - 2004-06-06
18332 o Changes from 0.0.7rc1:
18333 - Make it build on Win32 again.
18334 o Changes from 0.0.6.2:
18335 - Rotate dnsworkers and cpuworkers on SIGHUP, so they get new config
18339 Changes in version 0.0.7rc1 - 2004-06-02
18341 - On sighup, we were adding another log without removing the first
18342 one. So log messages would get duplicated n times for n sighups.
18343 - Several cases of using a connection after we'd freed it. The
18344 problem was that connections that are pending resolve are in both
18345 the pending_resolve tree, and also the circuit's resolving_streams
18346 list. When you want to remove one, you must remove it from both.
18347 - Fix a double-mark-for-close where an end cell arrived for a
18348 resolving stream, and then the resolve failed.
18349 - Check directory signatures based on name of signer, not on whom
18350 we got the directory from. This will let us cache directories more
18353 - Crank up some of our constants to handle more users.
18356 Changes in version 0.0.7pre1 - 2004-06-02
18357 o Fixes for crashes and other obnoxious bugs:
18358 - Fix an epipe bug: sometimes when directory connections failed
18359 to connect, we would give them a chance to flush before closing
18361 - When we detached from a circuit because of resolvefailed, we
18362 would immediately try the same circuit twice more, and then
18363 give up on the resolve thinking we'd tried three different
18365 - Limit the number of intro circuits we'll attempt to build for a
18366 hidden service per 15-minute period.
18367 - Check recommended-software string *early*, before actually parsing
18368 the directory. Thus we can detect an obsolete version and exit,
18369 even if the new directory format doesn't parse.
18370 o Fixes for security bugs:
18371 - Remember which nodes are dirservers when you startup, and if a
18372 random OR enables his dirport, don't automatically assume he's
18373 a trusted dirserver.
18375 - Directory connections were asking the wrong poll socket to
18376 start writing, and not asking themselves to start writing.
18377 - When we detached from a circuit because we sent a begin but
18378 didn't get a connected, we would use it again the first time;
18379 but after that we would correctly switch to a different one.
18380 - Stop warning when the first onion decrypt attempt fails; they
18381 will sometimes legitimately fail now that we rotate keys.
18382 - Override unaligned-access-ok check when $host_cpu is ia64 or
18383 arm. Apparently they allow it but the kernel whines.
18384 - Dirservers try to reconnect periodically too, in case connections
18386 - Fix some memory leaks in directory servers.
18387 - Allow backslash in Win32 filenames.
18388 - Made Tor build complain-free on FreeBSD, hopefully without
18389 breaking other BSD builds. We'll see.
18391 - Doxygen markup on all functions and global variables.
18392 - Make directory functions update routerlist, not replace it. So
18393 now directory disagreements are not so critical a problem.
18394 - Remove the upper limit on number of descriptors in a dirserver's
18395 directory (not that we were anywhere close).
18396 - Allow multiple logfiles at different severity ranges.
18397 - Allow *BindAddress to specify ":port" rather than setting *Port
18398 separately. Allow multiple instances of each BindAddress config
18399 option, so you can bind to multiple interfaces if you want.
18400 - Allow multiple exit policy lines, which are processed in order.
18401 Now we don't need that huge line with all the commas in it.
18402 - Enable accept/reject policies on SOCKS connections, so you can bind
18403 to 0.0.0.0 but still control who can use your OP.
18406 Changes in version 0.0.6.2 - 2004-05-16
18407 o Our integrity-checking digest was checking only the most recent cell,
18408 not the previous cells like we'd thought.
18409 Thanks to Stefan Mark for finding the flaw!
18412 Changes in version 0.0.6.1 - 2004-05-06
18413 o Fix two bugs in our AES counter-mode implementation (this affected
18414 onion-level stream encryption, but not TLS-level). It turns
18415 out we were doing something much more akin to a 16-character
18416 polyalphabetic cipher. Oops.
18417 Thanks to Stefan Mark for finding the flaw!
18418 o Retire moria3 as a directory server, and add tor26 as a directory
18422 Changes in version 0.0.6 - 2004-05-02
18423 [version bump only]
18426 Changes in version 0.0.6rc4 - 2004-05-01
18427 o Update the built-in dirservers list to use the new directory format
18428 o Fix a rare seg fault: if a node offering a hidden service attempts
18429 to build a circuit to Alice's rendezvous point and fails before it
18430 reaches the last hop, it retries with a different circuit, but
18432 o Handle windows socket errors correctly.
18435 Changes in version 0.0.6rc3 - 2004-04-28
18436 o Don't expire non-general excess circuits (if we had enough
18437 circuits open, we were expiring rendezvous circuits -- even
18438 when they had a stream attached. oops.)
18439 o Fetch randomness from /dev/urandom better (not via fopen/fread)
18440 o Better debugging for tls errors
18441 o Some versions of openssl have an SSL_pending function that erroneously
18442 returns bytes when there is a non-application record pending.
18443 o Set Content-Type on the directory and hidserv descriptor.
18444 o Remove IVs from cipher code, since AES-ctr has none.
18445 o Win32 fixes. Tor now compiles on win32 with no warnings/errors.
18446 o We were using an array of length zero in a few places.
18447 o win32's gethostbyname can't resolve an IP to an IP.
18448 o win32's close can't close a socket.
18451 Changes in version 0.0.6rc2 - 2004-04-26
18452 o Fix a bug where we were closing tls connections intermittently.
18453 It turns out openssl keeps its errors around -- so if an error
18454 happens, and you don't ask about it, and then another openssl
18455 operation happens and succeeds, and you ask if there was an error,
18456 it tells you about the first error. Fun fun.
18457 o Fix a bug that's been lurking since 27 may 03 (!)
18458 When passing back a destroy cell, we would use the wrong circ id.
18459 'Mostly harmless', but still worth fixing.
18460 o Since we don't support truncateds much, don't bother sending them;
18461 just close the circ.
18462 o check for <machine/limits.h> so we build on NetBSD again (I hope).
18463 o don't crash if a conn that sent a begin has suddenly lost its circuit
18464 (this was quite rare).
18467 Changes in version 0.0.6rc1 - 2004-04-25
18468 o We now rotate link (tls context) keys and onion keys.
18469 o CREATE cells now include oaep padding, so you can tell
18470 if you decrypted them correctly.
18471 o Add bandwidthburst to server descriptor.
18472 o Directories now say which dirserver signed them.
18473 o Use a tor_assert macro that logs failed assertions too.
18476 Changes in version 0.0.6pre5 - 2004-04-18
18477 o changes from 0.0.6pre4:
18478 - make tor build on broken freebsd 5.2 installs
18479 - fix a failed assert when you try an intro point, get a nack, and try
18480 a second one and it works.
18481 - when alice uses a port that the hidden service doesn't accept,
18482 it now sends back an end cell (denied by exit policy). otherwise
18483 alice would just have to wait to time out.
18484 - fix another rare bug: when we had tried all the intro
18485 points for a hidden service, we fetched the descriptor
18486 again, but we left our introcirc thinking it had already
18487 sent an intro, so it kept waiting for a response...
18488 - bugfix: when you sleep your hidden-service laptop, as soon
18489 as it wakes up it tries to upload a service descriptor, but
18490 socketpair fails for some reason (localhost not up yet?).
18491 now we simply give up on that upload, and we'll try again later.
18492 i'd still like to find the bug though.
18493 - if an intro circ waiting for an ack dies before getting one, then
18495 - we were reusing stale service descriptors and refetching usable
18499 Changes in version 0.0.6pre4 - 2004-04-14
18500 o changes from 0.0.6pre3:
18501 - when bob fails to connect to the rendezvous point, and his
18502 circ didn't fail because of the rendezvous point itself, then
18503 he retries a couple of times
18504 - we expire introduction and rendezvous circs more thoroughly
18505 (sometimes they were hanging around forever)
18506 - we expire unattached rendezvous streams that have been around
18507 too long (they were sticking around forever).
18508 - fix a measly fencepost error that was crashing everybody with
18512 Changes in version 0.0.6pre3 - 2004-04-14
18513 o changes from 0.0.6pre2:
18514 - make hup work again
18515 - fix some memory leaks for dirservers
18516 - allow more skew in rendezvous descriptor timestamps, to help
18517 handle people like blanu who don't know what time it is
18518 - normal circs are 3 hops, but some rend/intro circs are 4, if
18519 the initiator doesn't get to choose the last hop
18520 - send acks for introductions, so alice can know whether to try
18522 - bob publishes intro points more correctly
18523 o changes from 0.0.5:
18524 - fix an assert trigger that's been plaguing us since the days
18525 of 0.0.2prexx (thanks weasel!)
18526 - retry stream correctly when we fail to connect because of
18527 exit-policy-reject (should try another) or can't-resolve-address
18528 (also should try another, because dns on random internet servers
18530 - when we hup a dirserver and we've *removed* a server from the
18531 approved-routers list, now we remove that server from the
18532 in-memory directories too
18535 Changes in version 0.0.6pre2 - 2004-04-08
18536 o We fixed our base32 implementation. Now it works on all architectures.
18539 Changes in version 0.0.6pre1 - 2004-04-08
18541 - Hidden services and rendezvous points are implemented. Go to
18542 http://6sxoyfb3h2nvok2d.onion/ for an index of currently available
18543 hidden services. (This only works via a socks4a proxy such as
18544 Privoxy, and currently it's quite slow.)
18547 Changes in version 0.0.5 - 2004-03-30
18548 [version bump only]
18551 Changes in version 0.0.5rc3 - 2004-03-29
18552 o Install torrc as torrc.sample -- we no longer clobber your
18554 o Re-enable recommendedversion checking (we broke it in rc2, oops)
18555 o Add in a 'notice' log level for things the operator should hear
18556 but that aren't warnings
18559 Changes in version 0.0.5rc2 - 2004-03-29
18560 o Hold socks connection open until reply is flushed (if possible)
18561 o Make exit nodes resolve IPs to IPs immediately, rather than asking
18562 the dns farm to do it.
18563 o Fix c99 aliasing warnings in rephist.c
18564 o Don't include server descriptors that are older than 24 hours in the
18566 o Give socks 'reject' replies their whole 15s to attempt to flush,
18567 rather than seeing the 60s timeout and assuming the flush had failed.
18568 o Clean automake droppings from the cvs repository
18571 Changes in version 0.0.5rc1 - 2004-03-28
18572 o Fix mangled-state bug in directory fetching (was causing sigpipes).
18573 o Only build circuits after we've fetched the directory: clients were
18574 using only the directory servers before they'd fetched a directory.
18575 This also means longer startup time; so it goes.
18576 o Fix an assert trigger where an OP would fail to handshake, and we'd
18577 expect it to have a nickname.
18578 o Work around a tsocks bug: do a socks reject when AP connection dies
18579 early, else tsocks goes into an infinite loop.
18582 Changes in version 0.0.4 - 2004-03-26
18583 o When connecting to a dirserver or OR and the network is down,
18587 Changes in version 0.0.3 - 2004-03-26
18588 o Warn and fail if server chose a nickname with illegal characters
18589 o Port to Solaris and Sparc:
18590 - include missing header fcntl.h
18591 - have autoconf find -lsocket -lnsl automatically
18592 - deal with hardware word alignment
18593 - make uname() work (solaris has a different return convention)
18594 - switch from using signal() to sigaction()
18595 o Preliminary work on reputation system:
18596 - Keep statistics on success/fail of connect attempts; they're published
18597 by kill -USR1 currently.
18598 - Add a RunTesting option to try to learn link state by creating test
18599 circuits, even when SocksPort is off.
18600 - Remove unused open circuits when there are too many.
18603 Changes in version 0.0.2 - 2004-03-19
18604 - Include strlcpy and strlcat for safer string ops
18605 - define INADDR_NONE so we compile (but still not run) on solaris
18608 Changes in version 0.0.2pre27 - 2004-03-14
18610 - Allow internal tor networks (we were rejecting internal IPs,
18611 now we allow them if they're set explicitly).
18612 - And fix a few endian issues.
18615 Changes in version 0.0.2pre26 - 2004-03-14
18617 - If a stream times out after 15s without a connected cell, don't
18618 try that circuit again: try a new one.
18619 - Retry streams at most 4 times. Then give up.
18620 - When a dirserver gets a descriptor from an unknown router, it
18621 logs its fingerprint (so the dirserver operator can choose to
18622 accept it even without mail from the server operator).
18623 - Inform unapproved servers when we reject their descriptors.
18624 - Make tor build on Windows again. It works as a client, who knows
18626 - Clearer instructions in the torrc for how to set up a server.
18627 - Be more efficient about reading fd's when our global token bucket
18628 (used for rate limiting) becomes empty.
18630 - Stop asserting that computers always go forward in time. It's
18632 - When we sent a cell (e.g. destroy) and then marked an OR connection
18633 expired, we might close it before finishing a flush if the other
18634 side isn't reading right then.
18635 - Don't allow dirservers to start if they haven't defined
18636 RecommendedVersions
18637 - We were caching transient dns failures. Oops.
18638 - Prevent servers from publishing an internal IP as their address.
18639 - Address a strcat vulnerability in circuit.c
18642 Changes in version 0.0.2pre25 - 2004-03-04
18644 - Put the OR's IP in its router descriptor, not its fqdn. That way
18645 we'll stop being stalled by gethostbyname for nodes with flaky dns,
18648 - If the user typed in an address that didn't resolve, the server
18652 Changes in version 0.0.2pre24 - 2004-03-03
18654 - Fix an assertion failure in dns.c, where we were trying to dequeue
18655 a pending dns resolve even if it wasn't pending
18656 - Fix a spurious socks5 warning about still trying to write after the
18657 connection is finished.
18658 - Hold certain marked_for_close connections open until they're finished
18659 flushing, rather than losing bytes by closing them too early.
18660 - Correctly report the reason for ending a stream
18661 - Remove some duplicate calls to connection_mark_for_close
18662 - Put switch_id and start_daemon earlier in the boot sequence, so it
18663 will actually try to chdir() to options.DataDirectory
18664 - Make 'make test' exit(1) if a test fails; fix some unit tests
18665 - Make tor fail when you use a config option it doesn't know about,
18666 rather than warn and continue.
18667 - Make --version work
18668 - Bugfixes on the rpm spec file and tor.sh, so it's more up to date
18671 Changes in version 0.0.2pre23 - 2004-02-29
18673 - Print a statement when the first circ is finished, so the user
18674 knows it's working.
18675 - If a relay cell is unrecognized at the end of the circuit,
18676 send back a destroy. (So attacks to mutate cells are more
18678 - New config option 'excludenodes' to avoid certain nodes for circuits.
18679 - When it daemonizes, it chdir's to the DataDirectory rather than "/",
18680 so you can collect coredumps there.
18682 - Fix a bug in tls flushing where sometimes data got wedged and
18683 didn't flush until more data got sent. Hopefully this bug was
18684 a big factor in the random delays we were seeing.
18685 - Make 'connected' cells include the resolved IP, so the client
18686 dns cache actually gets populated.
18687 - Disallow changing from ORPort=0 to ORPort>0 on hup.
18688 - When we time-out on a stream and detach from the circuit, send an
18689 end cell down it first.
18690 - Only warn about an unknown router (in exitnodes, entrynodes,
18691 excludenodes) after we've fetched a directory.
18694 Changes in version 0.0.2pre22 - 2004-02-26
18696 - Servers publish less revealing uname information in descriptors.
18697 - More memory tracking and assertions, to crash more usefully when
18699 - If the default torrc isn't there, just use some default defaults.
18700 Plus provide an internal dirservers file if they don't have one.
18701 - When the user tries to use Tor as an http proxy, give them an http
18702 501 failure explaining that we're a socks proxy.
18703 - Dump a new router.desc on hup, to help confused people who change
18704 their exit policies and then wonder why router.desc doesn't reflect
18706 - Clean up the generic tor.sh init script that we ship with.
18708 - If the exit stream is pending on the resolve, and a destroy arrives,
18709 then the stream wasn't getting removed from the pending list. I
18710 think this was the one causing recent server crashes.
18711 - Use a more robust poll on OSX 10.3, since their poll is flaky.
18712 - When it couldn't resolve any dirservers, it was useless from then on.
18713 Now it reloads the RouterFile (or default dirservers) if it has no
18715 - Move the 'tor' binary back to /usr/local/bin/ -- it turns out
18716 many users don't even *have* a /usr/local/sbin/.
18719 Changes in version 0.0.2pre21 - 2004-02-18
18721 - There's a ChangeLog file that actually reflects the changelog.
18722 - There's a 'torify' wrapper script, with an accompanying
18723 tor-tsocks.conf, that simplifies the process of using tsocks for
18724 tor. It even has a man page.
18725 - The tor binary gets installed to sbin rather than bin now.
18726 - Retry streams where the connected cell hasn't arrived in 15 seconds
18727 - Clean up exit policy handling -- get the default out of the torrc,
18728 so we can update it without forcing each server operator to fix
18730 - Allow imaps and pop3s in default exit policy
18732 - Prevent picking middleman nodes as the last node in the circuit
18735 Changes in version 0.0.2pre20 - 2004-01-30
18737 - We now have a deb package, and it's in debian unstable. Go to
18738 it, apt-getters. :)
18739 - I've split the TotalBandwidth option into BandwidthRate (how many
18740 bytes per second you want to allow, long-term) and
18741 BandwidthBurst (how many bytes you will allow at once before the cap
18742 kicks in). This better token bucket approach lets you, say, set
18743 BandwidthRate to 10KB/s and BandwidthBurst to 10MB, allowing good
18744 performance while not exceeding your monthly bandwidth quota.
18745 - Push out a tls record's worth of data once you've got it, rather
18746 than waiting until you've read everything waiting to be read. This
18747 may improve performance by pipelining better. We'll see.
18748 - Add an AP_CONN_STATE_CONNECTING state, to allow streams to detach
18749 from failed circuits (if they haven't been connected yet) and attach
18751 - Expire old streams that haven't managed to connect. Some day we'll
18752 have them reattach to new circuits instead.
18755 - Fix several memory leaks that were causing servers to become bloated
18757 - Fix a few very rare assert triggers. A few more remain.
18758 - Setuid to User _before_ complaining about running as root.
18761 Changes in version 0.0.2pre19 - 2004-01-07
18763 - Fix deadlock condition in dns farm. We were telling a child to die by
18764 closing the parent's file descriptor to him. But newer children were
18765 inheriting the open file descriptor from the parent, and since they
18766 weren't closing it, the socket never closed, so the child never read
18767 eof, so he never knew to exit. Similarly, dns workers were holding
18768 open other sockets, leading to all sorts of chaos.
18769 - New cleaner daemon() code for forking and backgrounding.
18770 - If you log to a file, it now prints an entry at the top of the
18771 logfile so you know it's working.
18772 - The onionskin challenge length was 30 bytes longer than necessary.
18773 - Started to patch up the spec so it's not quite so out of date.
18776 Changes in version 0.0.2pre18 - 2004-01-02
18778 - Fix endian issues with the 'integrity' field in the relay header.
18779 - Fix a potential bug where connections in state
18780 AP_CONN_STATE_CIRCUIT_WAIT might unexpectedly ask to write.
18783 Changes in version 0.0.2pre17 - 2003-12-30
18785 - Made --debuglogfile (or any second log file, actually) work.
18786 - Resolved an edge case in get_unique_circ_id_by_conn where a smart
18787 adversary could force us into an infinite loop.
18790 - Each onionskin handshake now includes a hash of the computed key,
18791 to prove the server's identity and help perfect forward secrecy.
18792 - Changed cell size from 256 to 512 bytes (working toward compatibility
18794 - Changed cell length to 2 bytes, and moved it to the relay header.
18795 - Implemented end-to-end integrity checking for the payloads of
18797 - Separated streamid from 'recognized' (otherwise circuits will get
18798 messed up when we try to have streams exit from the middle). We
18799 use the integrity-checking to confirm that a cell is addressed to
18801 - Randomize the initial circid and streamid values, so an adversary who
18802 breaks into a node can't learn how many circuits or streams have
18806 Changes in version 0.0.2pre16 - 2003-12-14
18808 - Fixed a bug that made HUP trigger an assert
18809 - Fixed a bug where a circuit that immediately failed wasn't being
18810 counted as a failed circuit in counting retries.
18813 - Now we close the circuit when we get a truncated cell: otherwise we're
18814 open to an anonymity attack where a bad node in the path truncates
18815 the circuit and then we open streams at him.
18816 - Add port ranges to exit policies
18817 - Add a conservative default exit policy
18818 - Warn if you're running tor as root
18819 - on HUP, retry OR connections and close/rebind listeners
18820 - options.EntryNodes: try these nodes first when picking the first node
18821 - options.ExitNodes: if your best choices happen to include any of
18822 your preferred exit nodes, you choose among just those preferred
18824 - options.ExcludedNodes: nodes that are never picked in path building
18827 Changes in version 0.0.2pre15 - 2003-12-03
18828 o Robustness and bugfixes:
18829 - Sometimes clients would cache incorrect DNS resolves, which would
18830 really screw things up.
18831 - An OP that goes offline would slowly leak all its sockets and stop
18833 - A wide variety of bugfixes in exit node selection, exit policy
18834 handling, and processing pending streams when a new circuit is
18836 - Pick nodes for a path only from those the directory says are up
18837 - Choose randomly from all running dirservers, not always the first one
18838 - Increase allowed http header size for directory fetch.
18839 - Stop writing to stderr (if we're daemonized it will be closed).
18840 - Enable -g always, so cores will be more useful to me.
18841 - Switch "-lcrypto -lssl" to "-lssl -lcrypto" for broken distributions.
18844 - Wrote a man page. It lists commonly used options.
18847 - Change default loglevel to warn.
18848 - Make PidFile default to null rather than littering in your CWD.
18849 - OnionRouter config option is now obsolete. Instead it just checks
18851 - Moved to a single unified torrc file for both clients and servers.
18854 Changes in version 0.0.2pre14 - 2003-11-29
18855 o Robustness and bugfixes:
18856 - Force the admin to make the DataDirectory himself
18857 - to get ownership/permissions right
18858 - so clients no longer make a DataDirectory and then never use it
18859 - fix bug where a client who was offline for 45 minutes would never
18860 pull down a directory again
18861 - fix (or at least hide really well) the dns assert bug that was
18862 causing server crashes
18863 - warnings and improved robustness wrt clockskew for certs
18864 - use the native daemon(3) to daemonize, when available
18865 - exit if bind() fails
18866 - exit if neither socksport nor orport is defined
18867 - include our own tor_timegm (Win32 doesn't have its own)
18868 - bugfix for win32 with lots of connections
18869 - fix minor bias in PRNG
18870 - make dirserver more robust to corrupt cached directory
18873 - Wrote the design document (woo)
18875 o Circuit building and exit policies:
18876 - Circuits no longer try to use nodes that the directory has told them
18878 - Exit policies now support bitmasks (18.0.0.0/255.0.0.0) and
18879 bitcounts (18.0.0.0/8).
18880 - Make AP connections standby for a circuit if no suitable circuit
18881 exists, rather than failing
18882 - Circuits choose exit node based on addr/port, exit policies, and
18883 which AP connections are standing by
18884 - Bump min pathlen from 2 to 3
18885 - Relay end cells have a payload to describe why the stream ended.
18886 - If the stream failed because of exit policy, try again with a new
18888 - Clients have a dns cache to remember resolved addresses.
18889 - Notice more quickly when we have no working circuits
18892 - APPort is now called SocksPort
18893 - SocksBindAddress, ORBindAddress, DirBindAddress let you configure
18895 - RecommendedVersions is now a config variable rather than
18896 hardcoded (for dirservers)
18897 - Reloads config on HUP
18898 - Usage info on -h or --help
18899 - If you set User and Group config vars, it'll setu/gid to them.
18902 Changes in version 0.0.2pre13 - 2003-10-19
18903 o General stability:
18904 - SSL_write no longer fails when it returns WANTWRITE and the number
18905 of bytes in the buf has changed by the next SSL_write call.
18906 - Fix segfault fetching directory when network is down
18907 - Fix a variety of minor memory leaks
18908 - Dirservers reload the fingerprints file on HUP, so I don't have
18909 to take down the network when I approve a new router
18910 - Default server config file has explicit Address line to specify fqdn
18913 - Buffers grow and shrink as needed (Cut process size from 20M to 2M)
18914 - Make listener connections not ever alloc bufs
18916 o Autoconf improvements:
18917 - don't clobber an external CFLAGS in ./configure
18918 - Make install now works
18919 - create var/lib/tor on make install
18920 - autocreate a tor.sh initscript to help distribs
18921 - autocreate the torrc and sample-server-torrc with correct paths
18923 o Log files and Daemonizing now work:
18924 - If --DebugLogFile is specified, log to it at -l debug
18925 - If --LogFile is specified, use it instead of commandline
18926 - If --RunAsDaemon is set, tor forks and backgrounds on startup