1 Changes in version 0.2.3.20-rc - 2012-08-05
3 - Avoid read-from-freed-memory and double-free bugs that could occur
4 when a DNS request fails while launching it. Fixes bug 6480;
5 bugfix on 0.2.0.1-alpha.
6 - Avoid an uninitialized memory read when reading a vote or consensus
7 document that has an unrecognized flavor name. This read could
8 lead to a remote crash bug. Fixes bug 6530; bugfix on 0.2.2.6-alpha.
9 - Try to leak less information about what relays a client is
10 choosing to a side-channel attacker. Previously, a Tor client would
11 stop iterating through the list of available relays as soon as it
12 had chosen one, thus finishing a little earlier when it picked
13 a router earlier in the list. If an attacker can recover this
14 timing information (nontrivial but not proven to be impossible),
15 they could learn some coarse-grained information about which relays
16 a client was picking (middle nodes in particular are likelier to
17 be affected than exits). The timing attack might be mitigated by
18 other factors (see bug 6537 for some discussion), but it's best
19 not to take chances. Fixes bug 6537; bugfix on 0.0.8rc1.
22 - Try to make the warning when giving an obsolete SOCKSListenAddress
24 - Terminate active server managed proxies if Tor stops being a
25 relay. Addresses parts of bug 6274; bugfix on 0.2.3.6-alpha.
26 - Provide a better error message about possible OSX Asciidoc failure
27 reasons. Fixes bug 6436.
28 - Warn when Tor is configured to use accounting in a way that can
29 link a hidden service to some other hidden service or public
30 address. Resolves ticket 6490.
33 - Check return value of fputs() when writing authority certificate
34 file. Fixes Coverity issue 709056; bugfix on 0.2.0.1-alpha.
35 - Ignore ServerTransportPlugin lines when Tor is not configured as
36 a relay. Fixes bug 6274; bugfix on 0.2.3.6-alpha.
37 - When disabling guards for having too high a proportion of failed
38 circuits, make sure to look at each guard. Fixes bug 6397; bugfix
40 - Fix some typos in the manpages. Patch from A. Costa. Fixes bug 6500.
43 - Update our default RPM spec files to work with mock and rpmbuild
44 on RHEL/Fedora. They have an updated set of dependencies and
45 conflicts, a fix for an ancient typo when creating the "_tor"
46 user, and better instructions. Thanks to Ondrej Mikle for the
47 patch series. Fixes bug 6043.
50 - Make it possible to set the TestingTorNetwork configuration
51 option using AlternateDirAuthority and AlternateBridgeAuthority
52 as an alternative to setting DirServer. Addresses ticket 6377.
55 - Clarify the documentation for the Alternate*Authority options.
58 o Code simplification and refactoring:
59 - Do not use SMARTLIST_FOREACH for any loop whose body exceeds
60 10 lines. Also, don't nest them. Doing so in the past has
61 led to hard-to-debug code. The new style is to use the
62 SMARTLIST_FOREACH_{BEGIN,END} pair. Addresses issue 6400.
65 Changes in version 0.2.3.19-rc - 2012-07-06
66 Tor 0.2.3.19-rc is the second release candidate for the Tor 0.2.3.x
67 series. It fixes the compile on Windows, reverts to a GeoIP database
68 that isn't as broken, and fixes a flow control bug that has been around
69 since the beginning of Tor.
72 - Fix a bug handling SENDME cells on nonexistent streams that could
73 result in bizarre window values. Report and patch contributed
74 pseudonymously. Fixes part of bug 6271. This bug was introduced
75 before the first Tor release, in svn commit r152.
76 - Revert to the May 1 2012 Maxmind GeoLite Country database. In the
77 June 2012 database, Maxmind marked many Tor relays as country "A1",
78 which will cause risky behavior for clients that set EntryNodes
79 or ExitNodes. Addresses bug 6334; bugfix on 0.2.3.17-beta.
80 - Instead of ENOBUFS on Windows, say WSAENOBUFS. Fixes compilation
81 on Windows. Fixes bug 6296; bugfix on 0.2.3.18-rc.
84 - Fix wrong TCP port range in parse_port_range(). Fixes bug 6218;
85 bugfix on 0.2.1.10-alpha.
88 Changes in version 0.2.3.18-rc - 2012-06-28
89 Tor 0.2.3.18-rc is the first release candidate for the Tor 0.2.3.x
90 series. It fixes a few smaller bugs, but generally appears stable.
91 Please test it and let us know whether it is!
94 - Allow wildcarded mapaddress targets to be specified on the
95 controlport. Partially fixes bug 6244; bugfix on 0.2.3.9-alpha.
96 - Make our linker option detection code more robust against linkers
97 such as on FreeBSD 8, where a bad combination of options completes
98 successfully but makes an unrunnable binary. Fixes bug 6173;
99 bugfix on 0.2.3.17-beta.
101 o Minor bugfixes (on 0.2.2.x and earlier):
102 - Avoid a false positive in the util/threads unit test by increasing
103 the maximum timeout time. Fixes bug 6227; bugfix on 0.2.0.4-alpha.
104 - Replace "Sending publish request" log messages with "Launching
105 upload", so that they no longer confusingly imply that we're
106 sending something to a directory we might not even be connected
107 to yet. Fixes bug 3311; bugfix on 0.2.0.10-alpha.
108 - Make sure to set *socket_error in all error cases in
109 connection_connect(), so it can't produce a warning about
110 errno being zero from errno_to_orconn_end_reason(). Bugfix on
111 0.2.1.1-alpha; resolves ticket 6028.
112 - Downgrade "Got a certificate, but we already have it" log messages
113 from warning to info, except when we're a dirauth. Fixes bug 5238;
114 bugfix on 0.2.1.7-alpha.
115 - When checking for requested signatures on the latest consensus
116 before serving it to a client, make sure to check the right
117 consensus flavor. Bugfix on 0.2.2.6-alpha.
118 - Downgrade "eventdns rejected address" message to LOG_PROTOCOL_WARN.
119 Fixes bug 5932; bugfix on 0.2.2.7-alpha.
121 o Minor bugfixes (on 0.2.3.x):
122 - Make format_helper_exit_status() avoid unnecessary space padding
123 and stop confusing log_from_pipe(). Fixes ticket 5557; bugfix
125 - Downgrade a message about cleaning the microdescriptor cache to
126 "info" from "notice". Fixes bug 6238; bugfix on 0.2.3.1-alpha.
127 - Log a BUG message at severity INFO if we have a networkstatus with
128 a missing entry for some microdescriptor. Continues on a patch
130 - Improve the log message when a managed proxy fails to launch. Fixes
131 bug 5099; bugfix on 0.2.3.6-alpha.
132 - Don't do DNS lookups when parsing corrupted managed proxy protocol
133 messages. Fixes bug 6226; bugfix on 0.2.3.6-alpha.
134 - When formatting wildcarded address mappings for the controller,
135 be sure to include "*." as appropriate. Partially fixes bug 6244;
136 bugfix on 0.2.3.9-alpha.
137 - Avoid a warning caused by using strcspn() from glibc with clang 3.0.
138 Bugfix on 0.2.3.13-alpha.
139 - Stop logging messages about running with circuit timeout learning
140 enabled at severity LD_BUG. Fixes bug 6169; bugfix on 0.2.3.17-beta.
141 - Disable a spurious warning about reading on a marked and flushing
142 connection. We shouldn't be doing that, but apparently we
143 sometimes do. Fixes bug 6203; bugfix on 0.2.3.17-beta.
144 - Fix a bug that stopped AllowDotExit from working on addresses
145 that had an entry in the DNS cache. Fixes bug 6211; bugfix on
148 o Code simplification, refactoring, unit tests:
149 - Move tor_gettimeofday_cached() into compat_libevent.c, and use
150 Libevent's notion of cached time when possible.
151 - Remove duplicate code for invoking getrlimit() from control.c.
152 - Add a unit test for the environment_variable_names_equal function.
155 - Document the --defaults-torrc option, and the new (in 0.2.3)
156 semantics for overriding, extending, and clearing lists of
157 options. Closes bug 4748.
160 Changes in version 0.2.3.17-beta - 2012-06-15
161 Tor 0.2.3.17-beta enables compiler and linker hardening by default,
162 gets our TLS handshake back on track for being able to blend in with
163 Firefox, fixes a big bug in 0.2.3.16-alpha that broke Tor's interaction
164 with Vidalia, and otherwise continues to get us closer to a release
168 - Enable gcc and ld hardening by default. Resolves ticket 5210.
169 - Update TLS cipher list to match Firefox 8 and later. Resolves
171 - Implement the client side of proposal 198: remove support for
172 clients falsely claiming to support standard ciphersuites that
173 they can actually provide. As of modern OpenSSL versions, it's not
174 necessary to fake any standard ciphersuite, and doing so prevents
175 us from using better ciphersuites in the future, since servers
176 can't know whether an advertised ciphersuite is really supported or
177 not. Some hosts -- notably, ones with very old versions of OpenSSL
178 or where OpenSSL has been built with ECC disabled -- will stand
179 out because of this change; TBB users should not be affected.
182 - Change the default value for DynamicDHGroups (introduced in
183 0.2.3.9-alpha) to 0. This feature can make Tor relays less
184 identifiable by their use of the mod_ssl DH group, but at
185 the cost of some usability (#4721) and bridge tracing (#6087)
186 regressions. Resolves ticket 5598.
187 - Send a CRLF at the end of each STATUS_* control protocol event. This
188 bug tickled a bug in Vidalia which would make it freeze. Fixes
189 bug 6094; bugfix on 0.2.3.16-alpha.
192 - Disable writing on marked-for-close connections when they are
193 blocked on bandwidth, to prevent busy-looping in Libevent. Fixes
194 bug 5263; bugfix on 0.0.2pre13, where we first added a special
195 case for flushing marked connections.
196 - Detect SSL handshake even when the initial attempt to write the
197 server hello fails. Fixes bug 4592; bugfix on 0.2.0.13-alpha.
198 - Change the AllowDotExit rules so they should actually work.
199 We now enforce AllowDotExit only immediately after receiving an
200 address via SOCKS or DNSPort: other sources are free to provide
201 .exit addresses after the resolution occurs. Fixes bug 3940;
202 bugfix on 0.2.2.1-alpha.
203 - Fix a (harmless) integer overflow in cell statistics reported by
204 some fast relays. Fixes bug 5849; bugfix on 0.2.2.1-alpha.
205 - Make sure circuitbuild.c checks LearnCircuitBuildTimeout in all the
206 right places and never depends on the consensus parameters or
207 computes adaptive timeouts when it is disabled. Fixes bug 5049;
208 bugfix on 0.2.2.14-alpha.
209 - When building Tor on Windows with -DUNICODE (not default), ensure
210 that error messages, filenames, and DNS server names are always
211 NUL-terminated when we convert them to a single-byte encoding.
212 Fixes bug 5909; bugfix on 0.2.2.16-alpha.
213 - Make Tor build correctly again with -DUNICODE -D_UNICODE defined.
214 Fixes bug 6097; bugfix on 0.2.2.16-alpha.
215 - Fix an edge case where TestingTorNetwork is set but the authorities
216 and relays all have an uptime of zero, where the private Tor network
217 could briefly lack support for hidden services. Fixes bug 3886;
218 bugfix on 0.2.2.18-alpha.
219 - Correct the manpage's descriptions for the default values of
220 DirReqStatistics and ExtraInfoStatistics. Fixes bug 2865; bugfix
222 - Fix the documentation for the --hush and --quiet command line
223 options, which changed their behavior back in 0.2.3.3-alpha.
224 - Fix compilation warning with clang 3.1. Fixes bug 6141; bugfix on
228 - Rate-limit the "Weighted bandwidth is 0.000000" message, and add
229 more information to it, so that we can track it down in case it
230 returns again. Mitigates bug 5235.
231 - Check CircuitBuildTimeout and LearnCircuitBuildTimeout in
232 options_validate(); warn if LearnCircuitBuildTimeout is disabled and
233 CircuitBuildTimeout is set unreasonably low. Resolves ticket 5452.
234 - Warn the user when HTTPProxy, but no other proxy type, is
235 configured. This can cause surprising behavior: it doesn't send
236 all of Tor's traffic over the HTTPProxy -- it sends unencrypted
237 directory traffic only. Resolves ticket 4663.
238 - Issue a notice if a guard completes less than 40% of your circuits.
239 Threshold is configurable by torrc option PathBiasNoticeRate and
240 consensus parameter pb_noticepct. There is additional, off-by-
241 default code to disable guards which fail too many circuits.
242 Addresses ticket 5458.
243 - Update to the June 6 2012 Maxmind GeoLite Country database.
245 o Code simplifications and refactoring:
246 - Remove validate_pluggable_transports_config(): its warning
247 message is now handled by connection_or_connect().
250 Changes in version 0.2.2.37 - 2012-06-06
251 Tor 0.2.2.37 introduces a workaround for a critical renegotiation
252 bug in OpenSSL 1.0.1 (where 20% of the Tor network can't talk to itself
256 - Work around a bug in OpenSSL that broke renegotiation with TLS
257 1.1 and TLS 1.2. Without this workaround, all attempts to speak
258 the v2 Tor connection protocol when both sides were using OpenSSL
259 1.0.1 would fail. Resolves ticket 6033.
260 - When waiting for a client to renegotiate, don't allow it to add
261 any bytes to the input buffer. This fixes a potential DoS issue.
262 Fixes bugs 5934 and 6007; bugfix on 0.2.0.20-rc.
263 - Fix an edge case where if we fetch or publish a hidden service
264 descriptor, we might build a 4-hop circuit and then use that circuit
265 for exiting afterwards -- even if the new last hop doesn't obey our
266 ExitNodes config option. Fixes bug 5283; bugfix on 0.2.0.10-alpha.
269 - Fix a build warning with Clang 3.1 related to our use of vasprintf.
270 Fixes bug 5969. Bugfix on 0.2.2.11-alpha.
273 - Tell GCC and Clang to check for any errors in format strings passed
274 to the tor_v*(print|scan)f functions.
277 Changes in version 0.2.3.16-alpha - 2012-06-05
278 Tor 0.2.3.16-alpha introduces a workaround for a critical renegotiation
279 bug in OpenSSL 1.0.1 (where 20% of the Tor network can't talk to itself
280 currently). It also fixes a variety of smaller bugs and other cleanups
281 that get us closer to a release candidate.
283 o Major bugfixes (general):
284 - Work around a bug in OpenSSL that broke renegotiation with TLS
285 1.1 and TLS 1.2. Without this workaround, all attempts to speak
286 the v2 Tor connection protocol when both sides were using OpenSSL
287 1.0.1 would fail. Resolves ticket 6033.
288 - When waiting for a client to renegotiate, don't allow it to add
289 any bytes to the input buffer. This fixes a potential DoS issue.
290 Fixes bugs 5934 and 6007; bugfix on 0.2.0.20-rc.
291 - Pass correct OR address to managed proxies (like obfsproxy),
292 even when ORListenAddress is used. Fixes bug 4865; bugfix on
294 - The advertised platform of a router now includes only its operating
295 system's name (e.g., "Linux", "Darwin", "Windows 7"), and not its
296 service pack level (for Windows) or its CPU architecture (for Unix).
297 We also no longer include the "git-XYZ" tag in the version. Resolves
300 o Major bugfixes (clients):
301 - If we are unable to find any exit that supports our predicted ports,
302 stop calling them predicted, so that we don't loop and build
303 hopeless circuits indefinitely. Fixes bug 3296; bugfix on 0.0.9pre6,
304 which introduced predicted ports.
305 - Fix an edge case where if we fetch or publish a hidden service
306 descriptor, we might build a 4-hop circuit and then use that circuit
307 for exiting afterwards -- even if the new last hop doesn't obey our
308 ExitNodes config option. Fixes bug 5283; bugfix on 0.2.0.10-alpha.
309 - Check at each new consensus whether our entry guards were picked
310 long enough ago that we should rotate them. Previously, we only
311 did this check at startup, which could lead to us holding a guard
312 indefinitely. Fixes bug 5380; bugfix on 0.2.1.14-rc.
313 - When fetching a bridge descriptor from a bridge authority,
314 always do so anonymously, whether we have been able to open
315 circuits or not. Partial fix for bug 1938; bugfix on 2.0.7-alpha.
316 This behavior makes it *safer* to use UpdateBridgesFromAuthority,
317 but we'll need to wait for bug 6010 before it's actually usable.
319 o Major bugfixes (directory authorities):
320 - When computing weight parameters, behave more robustly in the
321 presence of a bad bwweightscale value. Previously, the authorities
322 would crash if they agreed on a sufficiently broken weight_scale
323 value: now, they use a reasonable default and carry on. Partial
324 fix for 5786; bugfix on 0.2.2.17-alpha.
325 - Check more thoroughly to prevent a rogue authority from
326 double-voting on any consensus directory parameter. Previously,
327 authorities would crash in this case if the total number of
328 votes for any parameter exceeded the number of active voters,
329 but would let it pass otherwise. Partial fix for bug 5786; bugfix
333 - Rate-limit log messages when asked to connect anonymously to
334 a private address. When these hit, they tended to hit fast and
335 often. Also, don't bother trying to connect to addresses that we
336 are sure will resolve to 127.0.0.1: getting 127.0.0.1 in a directory
337 reply makes us think we have been lied to, even when the address the
338 client tried to connect to was "localhost." Resolves ticket 2822.
339 - Allow packagers to insert an extra string in server descriptor
340 platform lines by setting the preprocessor variable TOR_BUILD_TAG.
341 Resolves the rest of ticket 2988.
342 - Raise the threshold of server descriptors needed (75%) and exit
343 server descriptors needed (50%) before we will declare ourselves
344 bootstrapped. This will make clients start building circuits a
345 little later, but makes the initially constructed circuits less
346 skewed and less in conflict with further directory fetches. Fixes
348 - Close any connection that sends unrecognized junk before the
349 handshake. Solves an issue noted in bug 4369.
350 - Improve log messages about managed transports. Resolves ticket 5070.
351 - Tag a bridge's descriptor as "never to be sent unencrypted".
352 This shouldn't matter, since bridges don't open non-anonymous
353 connections to the bridge authority and don't allow unencrypted
354 directory connections from clients, but we might as well make
355 sure. Closes bug 5139.
356 - Expose our view of whether we have gone dormant to the controller,
357 via a new "GETINFO dormant" value. Torbutton and other controllers
358 can use this to avoid doing periodic requests through Tor while
359 it's dormant (bug 4718). Fixes bug 5954.
360 - Tell GCC and Clang to check for any errors in format strings passed
361 to the tor_v*(print|scan)f functions.
362 - Update to the May 1 2012 Maxmind GeoLite Country database.
364 o Minor bugfixes (already included in 0.2.2.36):
365 - Reject out-of-range times like 23:59:61 in parse_rfc1123_time().
366 Fixes bug 5346; bugfix on 0.0.8pre3.
367 - Correct parsing of certain date types in parse_http_time().
368 Without this patch, If-Modified-Since would behave
369 incorrectly. Fixes bug 5346; bugfix on 0.2.0.2-alpha. Patch from
370 Esteban Manchado Velázques.
371 - Make our number-parsing functions always treat too-large values
372 as an error, even when those values exceed the width of the
373 underlying type. Previously, if the caller provided these
374 functions with minima or maxima set to the extreme values of the
375 underlying integer type, these functions would return those
376 values on overflow rather than treating overflow as an error.
377 Fixes part of bug 5786; bugfix on 0.0.9.
378 - If we hit the error case where routerlist_insert() replaces an
379 existing (old) server descriptor, make sure to remove that
380 server descriptor from the old_routers list. Fix related to bug
381 1776. Bugfix on 0.2.2.18-alpha.
382 - Clarify the behavior of MaxCircuitDirtiness with hidden service
383 circuits. Fixes issue 5259.
385 o Minor bugfixes (coding cleanup, on 0.2.2.x and earlier):
386 - Prevent a null-pointer dereference when receiving a data cell
387 for a nonexistent stream when the circuit in question has an
388 empty deliver window. We don't believe this is triggerable,
389 since we don't currently allow deliver windows to become empty,
390 but the logic is tricky enough that it's better to make the code
391 robust. Fixes bug 5541; bugfix on 0.0.2pre14.
392 - Fix a memory leak when trying to launch a DNS request when the
393 network is disabled or the nameservers are unconfigurable. Fixes
394 bug 5916; bugfix on Tor 0.1.2.1-alpha (for the unconfigurable
395 nameserver case) and on 0.2.3.9-alpha (for the DisableNetwork case).
396 - Don't hold a Windows file handle open for every file mapping;
397 the file mapping handle is sufficient. Fixes bug 5951; bugfix on
399 - Avoid O(n^2) performance characteristics when parsing a large
400 extrainfo cache. Fixes bug 5828; bugfix on 0.2.0.1-alpha.
401 - Format more doubles with %f, not %lf. Patch from grarpamp to make
402 Tor build correctly on older BSDs again. Fixes bug 3894; bugfix on
404 - Make our replacement implementation of strtok_r() compatible with
405 the standard behavior of strtok_r(). Patch by nils. Fixes bug 5091;
406 bugfix on 0.2.2.1-alpha.
407 - Fix a NULL-pointer dereference on a badly formed
408 SETCIRCUITPURPOSE command. Found by mikeyc. Fixes bug 5796;
409 bugfix on 0.2.2.9-alpha.
410 - Fix a build warning with Clang 3.1 related to our use of vasprintf.
411 Fixes bug 5969. Bugfix on 0.2.2.11-alpha.
412 - Defensively refactor rend_mid_rendezvous() so that protocol
413 violations and length checks happen in the beginning. Fixes
415 - Set _WIN32_WINNT to 0x0501 consistently throughout the code, so
416 that IPv6 stuff will compile on MSVC, and compilation issues
417 will be easier to track down. Fixes bug 5861.
419 o Minor bugfixes (correctness, on 0.2.2.x and earlier):
420 - Exit nodes now correctly report EADDRINUSE and EADDRNOTAVAIL as
421 resource exhaustion, so that clients can adjust their load to
422 try other exits. Fixes bug 4710; bugfix on 0.1.0.1-rc, which
423 started using END_STREAM_REASON_RESOURCELIMIT.
424 - Don't check for whether the address we're using for outbound
425 connections has changed until after the outbound connection has
426 completed. On Windows, getsockname() doesn't succeed until the
427 connection is finished. Fixes bug 5374; bugfix on 0.1.1.14-alpha.
428 - If the configuration tries to set MyFamily on a bridge, refuse to
429 do so, and warn about the security implications. Fixes bug 4657;
430 bugfix on 0.2.0.3-alpha.
431 - If the client fails to set a reasonable set of ciphersuites
432 during its v2 handshake renegotiation, allow the renegotiation to
433 continue nevertheless (i.e. send all the required certificates).
434 Fixes bug 4591; bugfix on 0.2.0.20-rc.
435 - When we receive a SIGHUP and the controller __ReloadTorrcOnSIGHUP
436 option is set to 0 (which Vidalia version 0.2.16 now does when
437 a SAVECONF attempt fails), perform other actions that SIGHUP
438 usually causes (like reopening the logs). Fixes bug 5095; bugfix
440 - If we fail to write a microdescriptor to the disk cache, do not
441 continue replacing the old microdescriptor file. Fixes bug 2954;
442 bugfix on 0.2.2.6-alpha.
443 - Exit nodes don't need to fetch certificates for authorities that
444 they don't recognize; only directory authorities, bridges,
445 and caches need to do that. Fixes part of bug 2297; bugfix on
447 - Correctly handle checking the permissions on the parent
448 directory of a control socket in the root directory. Bug found
449 by Esteban Manchado Velázquez. Fixes bug 5089; bugfix on Tor
451 - When told to add a bridge with the same digest as a preexisting
452 bridge but a different addr:port, change the addr:port as
453 requested. Previously we would not notice the change. Fixes half
454 of bug 5603; fix on 0.2.2.26-beta.
455 - End AUTHCHALLENGE error messages (in the control protocol) with
456 a CRLF. Fixes bug 5760; bugfix on 0.2.2.36 and 0.2.3.13-alpha.
458 o Minor bugfixes (on 0.2.3.x):
459 - Turn an assertion (that the number of handshakes received as a
460 server is not < 1) into a warning. Fixes bug 4873; bugfix on
462 - Format IPv4 addresses correctly in ADDRMAP events. (Previously,
463 we had reversed them when the answer was cached.) Fixes bug
464 5723; bugfix on 0.2.3.1-alpha.
465 - Work correctly on Linux systems with accept4 support advertised in
466 their headers, but without accept4 support in the kernel. Fix
467 by murb. Fixes bug 5762; bugfix on 0.2.3.1-alpha.
468 - When told to add a bridge with the same addr:port as a preexisting
469 bridge but a different transport, change the transport as
470 requested. Previously we would not notice the change. Fixes half
471 of bug 5603; fix on 0.2.3.2-alpha.
472 - Avoid a "double-reply" warning when replying to a SOCKS request
473 with a parse error. Patch from Fabian Keil. Fixes bug 4108;
474 bugfix on 0.2.3.4-alpha.
475 - Fix a bug where a bridge authority crashes if it has seen no
476 directory requests when it's time to write statistics to disk.
477 Fixes bug 5891; bugfix on 0.2.3.6-alpha. Also fixes bug 5508 in
479 - Don't try to open non-control listeners when DisableNetwork is set.
480 Previously, we'd open all listeners, then immediately close them.
481 Fixes bug 5604; bugfix on 0.2.3.9-alpha.
482 - Don't abort the managed proxy protocol if the managed proxy
483 sends us an unrecognized line; ignore it instead. Fixes bug
484 5910; bugfix on 0.2.3.9-alpha.
485 - Fix a compile warning in crypto.c when compiling with clang 3.1.
486 Fixes bug 5969, bugfix on 0.2.3.9-alpha.
487 - Fix a compilation issue on GNU Hurd, which doesn't have PATH_MAX.
488 Fixes bug 5355; bugfix on 0.2.3.11-alpha.
489 - Remove bogus definition of "_WIN32" from src/win32/orconfig.h, to
490 unbreak the MSVC build. Fixes bug 5858; bugfix on 0.2.3.12-alpha.
491 - Resolve numerous small warnings and build issues with MSVC. Resolves
494 o Documentation fixes:
495 - Improve the manual's documentation for the NT Service command-line
496 options. Addresses ticket 3964.
497 - Clarify SessionGroup documentation slightly; resolves ticket 5437.
498 - Document the changes to the ORPort and DirPort options, and the
499 fact that {OR/Dir}ListenAddress is now unnecessary (and
500 therefore deprecated). Resolves ticket 5597.
503 - Remove the torrc.bridge file: we don't use it for anything, and
504 it had become badly desynchronized from torrc.sample. Resolves
508 Changes in version 0.2.2.36 - 2012-05-24
509 Tor 0.2.2.36 updates the addresses for two of the eight directory
510 authorities, fixes some potential anonymity and security issues,
511 and fixes several crash bugs.
513 Tor 0.2.1.x has reached its end-of-life. Those Tor versions have many
514 known flaws, and nobody should be using them. You should upgrade. If
515 you're using a Linux or BSD and its packages are obsolete, stop using
516 those packages and upgrade anyway.
518 o Directory authority changes:
519 - Change IP address for maatuska (v3 directory authority).
520 - Change IP address for ides (v3 directory authority), and rename
524 - When building or running with any version of OpenSSL earlier
525 than 0.9.8s or 1.0.0f, disable SSLv3 support. These OpenSSL
526 versions have a bug (CVE-2011-4576) in which their block cipher
527 padding includes uninitialized data, potentially leaking sensitive
528 information to any peer with whom they make a SSLv3 connection. Tor
529 does not use SSL v3 by default, but a hostile client or server
530 could force an SSLv3 connection in order to gain information that
531 they shouldn't have been able to get. The best solution here is to
532 upgrade to OpenSSL 0.9.8s or 1.0.0f (or later). But when building
533 or running with a non-upgraded OpenSSL, we disable SSLv3 entirely
534 to make sure that the bug can't happen.
535 - Never use a bridge or a controller-supplied node as an exit, even
536 if its exit policy allows it. Found by wanoskarnet. Fixes bug
537 5342. Bugfix on 0.1.1.15-rc (for controller-purpose descriptors)
538 and 0.2.0.3-alpha (for bridge-purpose descriptors).
539 - Only build circuits if we have a sufficient threshold of the total
540 descriptors that are marked in the consensus with the "Exit"
541 flag. This mitigates an attack proposed by wanoskarnet, in which
542 all of a client's bridges collude to restrict the exit nodes that
543 the client knows about. Fixes bug 5343.
544 - Provide controllers with a safer way to implement the cookie
545 authentication mechanism. With the old method, if another locally
546 running program could convince a controller that it was the Tor
547 process, then that program could trick the controller into telling
548 it the contents of an arbitrary 32-byte file. The new "SAFECOOKIE"
549 authentication method uses a challenge-response approach to prevent
550 this attack. Fixes bug 5185; implements proposal 193.
553 - Avoid logging uninitialized data when unable to decode a hidden
554 service descriptor cookie. Fixes bug 5647; bugfix on 0.2.1.5-alpha.
555 - Avoid a client-side assertion failure when receiving an INTRODUCE2
556 cell on a general purpose circuit. Fixes bug 5644; bugfix on
558 - Fix builds when the path to sed, openssl, or sha1sum contains
559 spaces, which is pretty common on Windows. Fixes bug 5065; bugfix
561 - Correct our replacements for the timeradd() and timersub() functions
562 on platforms that lack them (for example, Windows). The timersub()
563 function is used when expiring circuits, while timeradd() is
564 currently unused. Bug report and patch by Vektor. Fixes bug 4778;
565 bugfix on 0.2.2.24-alpha.
566 - Fix the SOCKET_OK test that we use to tell when socket
567 creation fails so that it works on Win64. Fixes part of bug 4533;
568 bugfix on 0.2.2.29-beta. Bug found by wanoskarnet.
571 - Reject out-of-range times like 23:59:61 in parse_rfc1123_time().
572 Fixes bug 5346; bugfix on 0.0.8pre3.
573 - Make our number-parsing functions always treat too-large values
574 as an error, even when those values exceed the width of the
575 underlying type. Previously, if the caller provided these
576 functions with minima or maxima set to the extreme values of the
577 underlying integer type, these functions would return those
578 values on overflow rather than treating overflow as an error.
579 Fixes part of bug 5786; bugfix on 0.0.9.
580 - Older Linux kernels erroneously respond to strange nmap behavior
581 by having accept() return successfully with a zero-length
582 socket. When this happens, just close the connection. Previously,
583 we would try harder to learn the remote address: but there was
584 no such remote address to learn, and our method for trying to
585 learn it was incorrect. Fixes bugs 1240, 4745, and 4747. Bugfix
586 on 0.1.0.3-rc. Reported and diagnosed by "r1eo".
587 - Correct parsing of certain date types in parse_http_time().
588 Without this patch, If-Modified-Since would behave
589 incorrectly. Fixes bug 5346; bugfix on 0.2.0.2-alpha. Patch from
590 Esteban Manchado Velázques.
591 - Change the BridgePassword feature (part of the "bridge community"
592 design, which is not yet implemented) to use a time-independent
593 comparison. The old behavior might have allowed an adversary
594 to use timing to guess the BridgePassword value. Fixes bug 5543;
595 bugfix on 0.2.0.14-alpha.
596 - Detect and reject certain misformed escape sequences in
597 configuration values. Previously, these values would cause us
598 to crash if received in a torrc file or over an authenticated
599 control port. Bug found by Esteban Manchado Velázquez, and
600 independently by Robert Connolly from Matta Consulting who further
601 noted that it allows a post-authentication heap overflow. Patch
602 by Alexander Schrijver. Fixes bugs 5090 and 5402 (CVE 2012-1668);
603 bugfix on 0.2.0.16-alpha.
604 - Fix a compile warning when using the --enable-openbsd-malloc
605 configure option. Fixes bug 5340; bugfix on 0.2.0.20-rc.
606 - During configure, detect when we're building with clang version
607 3.0 or lower and disable the -Wnormalized=id and -Woverride-init
608 CFLAGS. clang doesn't support them yet.
609 - When sending an HTTP/1.1 proxy request, include a Host header.
610 Fixes bug 5593; bugfix on 0.2.2.1-alpha.
611 - Fix a NULL-pointer dereference on a badly formed SETCIRCUITPURPOSE
612 command. Found by mikeyc. Fixes bug 5796; bugfix on 0.2.2.9-alpha.
613 - If we hit the error case where routerlist_insert() replaces an
614 existing (old) server descriptor, make sure to remove that
615 server descriptor from the old_routers list. Fix related to bug
616 1776. Bugfix on 0.2.2.18-alpha.
618 o Minor bugfixes (documentation and log messages):
619 - Fix a typo in a log message in rend_service_rendezvous_has_opened().
620 Fixes bug 4856; bugfix on Tor 0.0.6.
621 - Update "ClientOnly" man page entry to explain that there isn't
622 really any point to messing with it. Resolves ticket 5005.
623 - Document the GiveGuardFlagTo_CVE_2011_2768_VulnerableRelays
624 directory authority option (introduced in Tor 0.2.2.34).
625 - Downgrade the "We're missing a certificate" message from notice
626 to info: people kept mistaking it for a real problem, whereas it
627 is seldom the problem even when we are failing to bootstrap. Fixes
628 bug 5067; bugfix on 0.2.0.10-alpha.
629 - Correctly spell "connect" in a log message on failure to create a
630 controlsocket. Fixes bug 4803; bugfix on 0.2.2.26-beta.
631 - Clarify the behavior of MaxCircuitDirtiness with hidden service
632 circuits. Fixes issue 5259.
635 - Directory authorities now reject versions of Tor older than
636 0.2.1.30, and Tor versions between 0.2.2.1-alpha and 0.2.2.20-alpha
637 inclusive. These versions accounted for only a small fraction of
638 the Tor network, and have numerous known security issues. Resolves
640 - Update to the May 1 2012 Maxmind GeoLite Country database.
643 - When sending or relaying a RELAY_EARLY cell, we used to convert
644 it to a RELAY cell if the connection was using the v1 link
645 protocol. This was a workaround for older versions of Tor, which
646 didn't handle RELAY_EARLY cells properly. Now that all supported
647 versions can handle RELAY_EARLY cells, and now that we're enforcing
648 the "no RELAY_EXTEND commands except in RELAY_EARLY cells" rule,
649 remove this workaround. Addresses bug 4786.
652 Changes in version 0.2.3.15-alpha - 2012-04-30
653 Tor 0.2.3.15-alpha fixes a variety of smaller bugs, including making
654 the development branch build on Windows again.
656 o Minor bugfixes (on 0.2.2.x and earlier):
657 - Make sure that there are no unhandled pending TLS errors before
658 reading from a TLS stream. We had checks in 0.1.0.3-rc, but
659 lost them in 0.1.0.5-rc when we refactored read_to_buf_tls().
660 Bugfix on 0.1.0.5-rc; fixes bug 4528.
661 - Fix an assert that directory authorities could trigger on sighup
662 during some configuration state transitions. We now don't treat
663 it as a fatal error when the new descriptor we just generated in
664 init_keys() isn't accepted. Fixes bug 4438; bugfix on 0.2.1.9-alpha.
665 - After we pick a directory mirror, we would refuse to use it if
666 it's in our ExcludeExitNodes list, resulting in mysterious failures
667 to bootstrap for people who just wanted to avoid exiting from
668 certain locations. Fixes bug 5623; bugfix on 0.2.2.25-alpha.
669 - When building with --enable-static-tor on OpenBSD, do not
670 erroneously attempt to link -lrt. Fixes bug 5103.
672 o Minor bugfixes (on 0.2.3.x):
673 - When Tor is built with kernel headers from a recent (last few
674 years) Linux kernel, do not fail to run on older (pre-2.6.28
675 Linux kernels). Fixes bug 5112; bugfix on 0.2.3.1-alpha.
676 - Fix cross-compilation issues with mingw. Bugfixes on 0.2.3.6-alpha
678 - Fix compilation with miniupnpc version 1.6; patch from
679 Anthony G. Basile. Fixes bug 5434; bugfix on 0.2.3.12-alpha.
680 - Fix compilation with MSVC, which had defined MS_WINDOWS. Bugfix
681 on 0.2.3.13-alpha; found and fixed by Gisle Vanem.
682 - Fix compilation on platforms without unistd.h, or where environ
683 is defined in stdlib.h. Fixes bug 5704; bugfix on 0.2.3.13-alpha.
686 - Directory authorities are now a little more lenient at accepting
687 older router descriptors, or newer router descriptors that don't
688 make big changes. This should help ameliorate past and future
689 issues where routers think they have uploaded valid descriptors,
690 but the authorities don't think so. Fix for ticket 2479.
691 - Make the code that clients use to detect an address change be
692 IPv6-aware, so that it won't fill clients' logs with error
693 messages when trying to get the IPv4 address of an IPv6
694 connection. Implements ticket 5537.
697 - Remove the GiveGuardFlagTo_CVE_2011_2768_VulnerableRelays option;
698 authorities needed to use it for a while to keep the network working
699 as people upgraded to 0.2.1.31, 0.2.2.34, or 0.2.3.6-alpha, but
700 that was six months ago. As of now, it should no longer be needed
704 Changes in version 0.2.3.14-alpha - 2012-04-23
705 Tor 0.2.3.14-alpha fixes yet more bugs to get us closer to a release
706 candidate. It also dramatically speeds up AES: fast relays should
707 consider switching to the newer OpenSSL library.
709 o Directory authority changes:
710 - Change IP address for ides (v3 directory authority), and rename
714 - Avoid logging uninitialized data when unable to decode a hidden
715 service descriptor cookie. Fixes bug 5647; bugfix on 0.2.1.5-alpha.
716 - Avoid a client-side assertion failure when receiving an INTRODUCE2
717 cell on a general purpose circuit. Fixes bug 5644; bugfix on
719 - If authorities are unable to get a v2 consensus document from other
720 directory authorities, they no longer fall back to fetching
721 them from regular directory caches. Fixes bug 5635; bugfix on
722 0.2.2.26-beta, where routers stopped downloading v2 consensus
724 - When we start a Tor client with a normal consensus already cached,
725 be willing to download a microdescriptor consensus. Fixes bug 4011;
726 fix on 0.2.3.1-alpha.
728 o Major features (performance):
729 - When built to use OpenSSL 1.0.1, and built for an x86 or x86_64
730 instruction set, take advantage of OpenSSL's AESNI, bitsliced, or
731 vectorized AES implementations as appropriate. These can be much,
732 much faster than other AES implementations.
734 o Minor bugfixes (0.2.2.x and earlier):
735 - Don't launch more than 10 service-side introduction-point circuits
736 for a hidden service in five minutes. Previously, we would consider
737 launching more introduction-point circuits if at least one second
738 had passed without any introduction-point circuits failing. Fixes
739 bug 4607; bugfix on 0.0.7pre1.
740 - Change the BridgePassword feature (part of the "bridge community"
741 design, which is not yet implemented) to use a time-independent
742 comparison. The old behavior might have allowed an adversary
743 to use timing to guess the BridgePassword value. Fixes bug 5543;
744 bugfix on 0.2.0.14-alpha.
745 - Enforce correct return behavior of tor_vsscanf() when the '%%'
746 pattern is used. Fixes bug 5558. Bugfix on 0.2.1.13.
747 - When sending an HTTP/1.1 proxy request, include a Host header.
748 Fixes bug 5593; bugfix on 0.2.2.1-alpha.
749 - Don't log that we have "decided to publish new relay descriptor"
750 unless we are actually publishing a descriptor. Fixes bug 3942;
751 bugfix on 0.2.2.28-beta.
753 o Minor bugfixes (0.2.3.x):
754 - Fix a bug where a bridge authority crashes (on a failed assert)
755 if it has seen no directory requests when it's time to write
756 statistics to disk. Fixes bug 5508. Bugfix on 0.2.3.6-alpha.
757 - Fix bug stomping on ORPort option NoListen and ignoring option
758 NoAdvertise. Fixes bug 5151; bugfix on 0.2.3.9-alpha.
759 - In the testsuite, provide a large enough buffer in the tor_sscanf
760 unit test. Otherwise we'd overrun that buffer and crash during
761 the unit tests. Found by weasel. Fixes bug 5449; bugfix on
763 - Make sure we create the keys directory if it doesn't exist and we're
764 about to store the dynamic Diffie-Hellman parameters. Fixes bug
765 5572; bugfix on 0.2.3.13-alpha.
766 - Fix a small memory leak when trying to decode incorrect base16
767 authenticator during SAFECOOKIE authentication. Found by
768 Coverity Scan. Fixes CID 507. Bugfix on 0.2.3.13-alpha.
771 - Add more information to a log statement that might help track down
772 bug 4091. If you're seeing "Bug: tor_addr_is_internal() called with a
773 non-IP address" messages (or any Bug messages, for that matter!),
774 please let us know about it.
775 - Relays now understand an IPv6 address when they get one from a
776 directory server. Resolves ticket 4875.
777 - Resolve IPv6 addresses in bridge and entry statistics to country
778 code "??" which means we at least count them. Resolves ticket 5053;
779 improves on 0.2.3.9-alpha.
780 - Update to the April 3 2012 Maxmind GeoLite Country database.
781 - Begin a doc/state-contents.txt file to explain the contents of
782 the Tor state file. Fixes bug 2987.
784 o Default torrc changes:
785 - Stop listing "socksport 9050" in torrc.sample. We open a socks
786 port on 9050 by default anyway, so this should not change anything
788 - Stop mentioning the deprecated *ListenAddress options in
789 torrc.sample. Fixes bug 5438.
790 - Document unit of bandwidth related options in sample torrc.
794 - The "torify" script no longer supports the "tsocks" socksifier
795 tool, since tsocks doesn't support DNS and UDP right for Tor.
796 Everyone should be using torsocks instead. Fixes bugs 3530 and
797 5180. Based on a patch by "ugh".
800 - Change the symmetric cipher interface so that creating and
801 initializing a stream cipher are no longer separate functions.
802 - Remove all internal support for unpadded RSA. We never used it, and
803 it would be a bad idea to start.
806 Changes in version 0.2.3.13-alpha - 2012-03-26
807 Tor 0.2.3.13-alpha fixes a variety of stability and correctness bugs
808 in managed pluggable transports, as well as providing other cleanups
809 that get us closer to a release candidate.
811 o Directory authority changes:
812 - Change IP address for maatuska (v3 directory authority).
815 - Provide controllers with a safer way to implement the cookie
816 authentication mechanism. With the old method, if another locally
817 running program could convince a controller that it was the Tor
818 process, then that program could trick the controller into telling
819 it the contents of an arbitrary 32-byte file. The new "SAFECOOKIE"
820 authentication method uses a challenge-response approach to prevent
821 this attack. Fixes bug 5185, implements proposal 193.
822 - Never use a bridge or a controller-supplied node as an exit, even
823 if its exit policy allows it. Found by wanoskarnet. Fixes bug
824 5342. Bugfix on 0.1.1.15-rc (for controller-purpose descriptors)
825 and 0.2.0.3-alpha (for bridge-purpose descriptors).
826 - Only build circuits if we have a sufficient threshold of the total
827 descriptors that are marked in the consensus with the "Exit"
828 flag. This mitigates an attack proposed by wanoskarnet, in which
829 all of a client's bridges collude to restrict the exit nodes that
830 the client knows about. Fixes bug 5343.
832 o Major bugfixes (on Tor 0.2.3.x):
833 - Avoid an assert when managed proxies like obfsproxy are configured,
834 and we receive HUP signals or setconf attempts too rapidly. This
835 situation happens most commonly when Vidalia tries to attach to
836 Tor or tries to configure the Tor it's attached to. Fixes bug 5084;
837 bugfix on 0.2.3.6-alpha.
838 - Fix a relay-side pluggable transports bug where managed proxies were
839 unreachable from the Internet, because Tor asked them to bind on
840 localhost. Fixes bug 4725; bugfix on 0.2.3.9-alpha.
841 - Stop discarding command-line arguments when TestingTorNetwork
842 is set. Discovered by Kevin Bauer. Fixes bug 5373; bugfix on
843 0.2.3.9-alpha, where task 4552 added support for two layers of
845 - Resume allowing the unit tests to run in gdb. This was accidentally
846 made impossible when the DisableDebuggerAttachment option was
847 introduced. Fixes bug 5448; bugfix on 0.2.3.9-alpha.
848 - Resume building with nat-pmp support. Fixes bug 4955; bugfix on
849 0.2.3.11-alpha. Reported by Anthony G. Basile.
851 o Minor bugfixes (on 0.2.2.x and earlier):
852 - Ensure we don't cannibalize circuits that are longer than three hops
853 already, so we don't end up making circuits with 5 or more
854 hops. Patch contributed by wanoskarnet. Fixes bug 5231; bugfix on
855 0.1.0.1-rc which introduced cannibalization.
856 - Detect and reject certain misformed escape sequences in
857 configuration values. Previously, these values would cause us
858 to crash if received in a torrc file or over an authenticated
859 control port. Bug found by Esteban Manchado Velázquez, and
860 independently by Robert Connolly from Matta Consulting who further
861 noted that it allows a post-authentication heap overflow. Patch
862 by Alexander Schrijver. Fixes bugs 5090 and 5402 (CVE 2012-1668);
863 bugfix on 0.2.0.16-alpha.
864 - Fix a compile warning when using the --enable-openbsd-malloc
865 configure option. Fixes bug 5340; bugfix on 0.2.0.20-rc.
866 - Directory caches no longer refuse to clean out descriptors because
867 of missing v2 networkstatus documents, unless they're configured
868 to retrieve v2 networkstatus documents. Fixes bug 4838; bugfix on
869 0.2.2.26-beta. Patch by Daniel Bryg.
870 - Update to the latest version of the tinytest unit testing framework.
871 This includes a couple of bugfixes that can be relevant for
872 running forked unit tests on Windows, and removes all reserved
875 o Minor bugfixes (on 0.2.3.x):
876 - On a failed pipe() call, don't leak file descriptors. Fixes bug
877 4296; bugfix on 0.2.3.1-alpha.
878 - Spec conformance: on a v3 handshake, do not send a NETINFO cell
879 until after we have received a CERTS cell. Fixes bug 4361; bugfix
880 on 0.2.3.6-alpha. Patch by "frosty".
881 - When binding to an IPv6 address, set the IPV6_V6ONLY socket
882 option, so that the IP stack doesn't decide to use it for IPv4
883 too. Fixes bug 4760; bugfix on 0.2.3.9-alpha.
884 - Ensure that variables set in Tor's environment cannot override
885 environment variables that Tor passes to a managed
886 pluggable-transport proxy. Previously, Tor would pass every
887 variable in its environment to managed proxies along with the new
888 ones, in such a way that on many operating systems, the inherited
889 environment variables would override those which Tor tried to
890 explicitly set. Bugfix on 0.2.3.12-alpha for most Unixoid systems;
891 bugfix on 0.2.3.9-alpha for Windows.
894 - A wide variety of new unit tests by Esteban Manchado Velázquez.
895 - Shorten links in the tor-exit-notice file. Patch by Christian Kujau.
896 - Update to the March 6 2012 Maxmind GeoLite Country database.
899 Changes in version 0.2.3.12-alpha - 2012-02-13
900 Tor 0.2.3.12-alpha lets fast exit relays scale better, allows clients
901 to use bridges that run Tor 0.2.2.x, and resolves several big bugs
902 when Tor is configured to use a pluggable transport like obfsproxy.
905 - Fix builds when the path to sed, openssl, or sha1sum contains
906 spaces, which is pretty common on Windows. Fixes bug 5065; bugfix
908 - Set the SO_REUSEADDR socket option before we call bind() on outgoing
909 connections. This change should allow busy exit relays to stop
910 running out of available sockets as quickly. Fixes bug 4950;
911 bugfix on 0.2.2.26-beta.
912 - Allow 0.2.3.x clients to use 0.2.2.x bridges. Previously the client
913 would ask the bridge for microdescriptors, which are only supported
914 in 0.2.3.x, and then fail to bootstrap when it didn't get the
915 answers it wanted. Fixes bug 4013; bugfix on 0.2.3.2-alpha.
916 - Properly set up obfsproxy's environment when in managed mode. The
917 Tor Browser Bundle needs LD_LIBRARY_PATH to be passed to obfsproxy,
918 and when you run your Tor as a daemon, there's no HOME. Fixes bugs
919 5076 and 5082; bugfix on 0.2.3.6-alpha.
922 - Use the dead_strip option when building Tor on OS X. This reduces
923 binary size by almost 19% when linking openssl and libevent
924 statically, which we do for Tor Browser Bundle.
925 - Fix broken URLs in the sample torrc file, and tell readers about
926 the OutboundBindAddress, ExitPolicyRejectPrivate, and
927 PublishServerDescriptor options. Addresses bug 4652.
928 - Update to the February 7 2012 Maxmind GeoLite Country database.
931 - Downgrade the "We're missing a certificate" message from notice
932 to info: people kept mistaking it for a real problem, whereas it
933 is seldom the problem even when we are failing to bootstrap. Fixes
934 bug 5067; bugfix on 0.2.0.10-alpha.
935 - Don't put "TOR_PT_EXTENDED_SERVER_PORT=127.0.0.1:4200" in a
936 managed pluggable transport server proxy's environment.
937 Previously, we would put it there, even though Tor doesn't
938 implement an 'extended server port' yet, and even though Tor
939 almost certainly isn't listening at that address. For now, we set
940 it to an empty string to avoid crashing older obfsproxies. Bugfix
942 - Log the heartbeat message every HeartbeatPeriod seconds, not every
943 HeartbeatPeriod + 1 seconds. Fixes bug 4942; bugfix on
944 0.2.3.1-alpha. Bug reported by Scott Bennett.
945 - Calculate absolute paths correctly on Windows. Fixes bug 4973;
946 bugfix on 0.2.3.11-alpha.
947 - Update "ClientOnly" man page entry to explain that there isn't
948 really any point to messing with it. Resolves ticket 5005.
949 - Use the correct CVE number for CVE-2011-4576 in our comments and
950 log messages. Found by "fermenthor". Resolves bug 5066; bugfix on
953 o Code simplifications and refactoring:
954 - Use the _WIN32 macro throughout our code to detect Windows.
955 (Previously we had used the obsolete 'WIN32' and the idiosyncratic
959 Changes in version 0.2.3.11-alpha - 2012-01-22
960 Tor 0.2.3.11-alpha marks feature-freeze for the 0.2.3 tree. It deploys
961 the last step of the plan to limit maximum circuit length, includes
962 a wide variety of hidden service performance and correctness fixes,
963 works around an OpenSSL security flaw if your distro is too stubborn
964 to upgrade, and fixes a bunch of smaller issues.
967 - Now that Tor 0.2.0.x is completely deprecated, enable the final
968 part of "Proposal 110: Avoiding infinite length circuits" by
969 refusing all circuit-extend requests that do not use a relay_early
970 cell. This change helps Tor resist a class of denial-of-service
971 attacks by limiting the maximum circuit length.
972 - Adjust the number of introduction points that a hidden service
973 will try to maintain based on how long its introduction points
974 remain in use and how many introductions they handle. Fixes
976 - Try to use system facilities for enumerating local interface
977 addresses, before falling back to our old approach (which was
978 binding a UDP socket, and calling getsockname() on it). That
979 approach was scaring OS X users whose draconian firewall
980 software warned about binding to UDP sockets, regardless of
981 whether packets were sent. Now we try to use getifaddrs(),
982 SIOCGIFCONF, or GetAdaptersAddresses(), depending on what the
983 system supports. Resolves ticket 1827.
985 o Major security workaround:
986 - When building or running with any version of OpenSSL earlier
987 than 0.9.8s or 1.0.0f, disable SSLv3 support. These OpenSSL
988 versions have a bug (CVE-2011-4576) in which their block cipher
989 padding includes uninitialized data, potentially leaking sensitive
990 information to any peer with whom they make a SSLv3 connection. Tor
991 does not use SSL v3 by default, but a hostile client or server
992 could force an SSLv3 connection in order to gain information that
993 they shouldn't have been able to get. The best solution here is to
994 upgrade to OpenSSL 0.9.8s or 1.0.0f (or later). But when building
995 or running with a non-upgraded OpenSSL, we disable SSLv3 entirely
996 to make sure that the bug can't happen.
999 - Fix the SOCKET_OK test that we use to tell when socket
1000 creation fails so that it works on Win64. Fixes part of bug 4533;
1001 bugfix on 0.2.2.29-beta. Bug found by wanoskarnet.
1002 - Correct our replacements for the timeradd() and timersub() functions
1003 on platforms that lack them (for example, Windows). The timersub()
1004 function is used when expiring circuits, while timeradd() is
1005 currently unused. Bug report and patch by Vektor. Fixes bug 4778;
1006 bugfix on 0.2.2.24-alpha and 0.2.3.1-alpha.
1007 - Do not use OpenSSL 1.0.0's counter mode: it has a critical bug
1008 that was fixed in OpenSSL 1.0.0a. We test for the counter mode
1009 bug at runtime, not compile time, because some distributions hack
1010 their OpenSSL to mis-report its version. Fixes bug 4779; bugfix
1011 on 0.2.3.9-alpha. Found by Pascal.
1013 o Minor features (controller):
1014 - Use absolute path names when reporting the torrc filename in the
1015 control protocol, so a controller can more easily find the torrc
1016 file. Resolves bug 1101.
1017 - Extend the control protocol to report flags that control a circuit's
1018 path selection in CIRC events and in replies to 'GETINFO
1019 circuit-status'. Implements part of ticket 2411.
1020 - Extend the control protocol to report the hidden service address
1021 and current state of a hidden-service-related circuit in CIRC
1022 events and in replies to 'GETINFO circuit-status'. Implements part
1024 - When reporting the path to the cookie file to the controller,
1025 give an absolute path. Resolves ticket 4881.
1026 - Allow controllers to request an event notification whenever a
1027 circuit is cannibalized or its purpose is changed. Implements
1028 part of ticket 3457.
1029 - Include the creation time of a circuit in CIRC and CIRC2
1030 control-port events and the list produced by the 'GETINFO
1031 circuit-status' control-port command.
1033 o Minor features (directory authorities):
1034 - Directory authorities now reject versions of Tor older than
1035 0.2.1.30, and Tor versions between 0.2.2.1-alpha and 0.2.2.20-alpha
1036 inclusive. These versions accounted for only a small fraction of
1037 the Tor network, and have numerous known security issues. Resolves
1039 - Authority operators can now vote for all relays in a given
1040 set of countries to be BadDir/BadExit/Invalid/Rejected.
1041 - Provide two consensus parameters (FastFlagMinThreshold and
1042 FastFlagMaxThreshold) to control the range of allowable bandwidths
1043 for the Fast directory flag. These allow authorities to run
1044 experiments on appropriate requirements for being a "Fast" node.
1045 The AuthDirFastGuarantee config value still applies.
1046 - Document the GiveGuardFlagTo_CVE_2011_2768_VulnerableRelays
1047 directory authority option (introduced in Tor 0.2.2.34).
1049 o Minor features (other):
1050 - Don't disable the DirPort when we cannot exceed our AccountingMax
1051 limit during this interval because the effective bandwidthrate is
1052 low enough. This is useful in a situation where AccountMax is only
1053 used as an additional safeguard or to provide statistics.
1054 - Prepend an informative header to generated dynamic_dh_params files.
1055 - If EntryNodes are given, but UseEntryGuards is set to 0, warn that
1056 EntryNodes will have no effect. Resolves issue 2571.
1057 - Log more useful messages when we fail to disable debugger
1059 - Log which authority we're missing votes from when we go to fetch
1060 them from the other auths.
1061 - Log (at debug level) whenever a circuit's purpose is changed.
1062 - Add missing documentation for the MaxClientCircuitsPending,
1063 UseMicrodescriptors, UserspaceIOCPBuffers, and
1064 _UseFilteringSSLBufferevents options, all introduced during
1066 - Update to the January 3 2012 Maxmind GeoLite Country database.
1068 o Minor bugfixes (hidden services):
1069 - Don't close hidden service client circuits which have almost
1070 finished connecting to their destination when they reach
1071 the normal circuit-build timeout. Previously, we would close
1072 introduction circuits which are waiting for an acknowledgement
1073 from the introduction point, and rendezvous circuits which have
1074 been specified in an INTRODUCE1 cell sent to a hidden service,
1075 after the normal CBT. Now, we mark them as 'timed out', and launch
1076 another rendezvous attempt in parallel. This behavior change can
1077 be disabled using the new CloseHSClientCircuitsImmediatelyOnTimeout
1078 option. Fixes part of bug 1297; bugfix on 0.2.2.2-alpha.
1079 - Don't close hidden-service-side rendezvous circuits when they
1080 reach the normal circuit-build timeout. This behaviour change can
1081 be disabled using the new
1082 CloseHSServiceRendCircuitsImmediatelyOnTimeout option. Fixes the
1083 remaining part of bug 1297; bugfix on 0.2.2.2-alpha.
1084 - Make sure we never mark the wrong rendezvous circuit as having
1085 had its introduction cell acknowleged by the introduction-point
1086 relay. Previously, when we received an INTRODUCE_ACK cell on a
1087 client-side hidden-service introduction circuit, we might have
1088 marked a rendezvous circuit other than the one we specified in
1089 the INTRODUCE1 cell as INTRO_ACKED, which would have produced
1090 a warning message and interfered with the hidden service
1091 connection-establishment process. Fixes bug 4759; bugfix on
1092 0.2.3.3-alpha, when we added the stream-isolation feature which
1093 might cause Tor to open multiple rendezvous circuits for the same
1095 - Don't trigger an assertion failure when we mark a new client-side
1096 hidden-service introduction circuit for close during the process
1097 of creating it. Fixes bug 4796; bugfix on 0.2.3.6-alpha. Reported
1100 o Minor bugfixes (log messages):
1101 - Correctly spell "connect" in a log message on failure to create a
1102 controlsocket. Fixes bug 4803; bugfix on 0.2.2.26-beta and
1104 - Fix a typo in a log message in rend_service_rendezvous_has_opened().
1105 Fixes bug 4856; bugfix on Tor 0.0.6.
1106 - Fix the log message describing how we work around discovering
1107 that our version is the ill-fated OpenSSL 0.9.8l. Fixes bug
1108 4837; bugfix on 0.2.2.9-alpha.
1109 - When logging about a disallowed .exit name, do not also call it
1110 an "invalid onion address". Fixes bug 3325; bugfix on 0.2.2.9-alpha.
1112 o Minor bugfixes (build fixes):
1113 - During configure, detect when we're building with clang version
1114 3.0 or lower and disable the -Wnormalized=id and -Woverride-init
1115 CFLAGS. clang doesn't support them yet.
1116 - During configure, search for library containing cos function as
1117 libm lives in libcore on some platforms (BeOS/Haiku). Linking
1118 against libm was hard-coded before. Fixes the first part of bug
1119 4727; bugfix on 0.2.2.2-alpha. Patch and analysis by Martin Hebnes
1121 - Detect attempts to build Tor on (as yet hypothetical) versions
1122 of Windows where sizeof(intptr_t) != sizeof(SOCKET). Partial
1123 fix for bug 4533. Bugfix on 0.2.2.28-beta.
1124 - Preprocessor directives should not be put inside the arguments
1125 of a macro. This would break compilation with GCC releases prior
1126 to version 3.3. We would never recommend such an old GCC version,
1127 but it is apparently required for binary compatibility on some
1128 platforms (namely, certain builds of Haiku). Fixes the other part
1129 of bug 4727; bugfix on 0.2.3.3-alpha. Patch and analysis by Martin
1132 o Minor bugfixes (other):
1133 - Older Linux kernels erroneously respond to strange nmap behavior
1134 by having accept() return successfully with a zero-length
1135 socket. When this happens, just close the connection. Previously,
1136 we would try harder to learn the remote address: but there was
1137 no such remote address to learn, and our method for trying to
1138 learn it was incorrect. Fixes bugs 1240, 4745, and 4747. Bugfix
1139 on 0.1.0.3-rc. Reported and diagnosed by "r1eo".
1140 - Fix null-pointer access that could occur if TLS allocation failed.
1141 Fixes bug 4531; bugfix on 0.2.0.20-rc. Found by "troll_un". This was
1142 erroneously listed as fixed in 0.2.3.9-alpha, but the fix had
1143 accidentally been reverted.
1144 - Fix our implementation of crypto_random_hostname() so it can't
1145 overflow on ridiculously large inputs. (No Tor version has ever
1146 provided this kind of bad inputs, but let's be correct in depth.)
1147 Fixes bug 4413; bugfix on 0.2.2.9-alpha. Fix by Stephen Palmateer.
1148 - Find more places in the code that should have been testing for
1149 invalid sockets using the SOCKET_OK macro. Required for a fix
1150 for bug 4533. Bugfix on 0.2.2.28-beta.
1151 - Fix an assertion failure when, while running with bufferevents, a
1152 connection finishes connecting after it is marked for close, but
1153 before it is closed. Fixes bug 4697; bugfix on 0.2.3.1-alpha.
1154 - test_util_spawn_background_ok() hardcoded the expected value
1155 for ENOENT to 2. This isn't portable as error numbers are
1156 platform specific, and particularly the hurd has ENOENT at
1157 0x40000002. Construct expected string at runtime, using the correct
1158 value for ENOENT. Fixes bug 4733; bugfix on 0.2.3.1-alpha.
1159 - Reject attempts to disable DisableDebuggerAttachment while Tor is
1160 running. Fixes bug 4650; bugfix on 0.2.3.9-alpha.
1161 - Use an appropriate-width type for sockets in tor-fw-helper on
1162 win64. Fixes bug 1983 at last. Bugfix on 0.2.3.9-alpha.
1165 - When sending or relaying a RELAY_EARLY cell, we used to convert
1166 it to a RELAY cell if the connection was using the v1 link
1167 protocol. This was a workaround for older versions of Tor, which
1168 didn't handle RELAY_EARLY cells properly. Now that all supported
1169 versions can handle RELAY_EARLY cells, and now that we're enforcing
1170 the "no RELAY_EXTEND commands except in RELAY_EARLY cells" rule,
1171 remove this workaround. Addresses bug 4786.
1173 o Code simplifications and refactoring:
1174 - Use OpenSSL's built-in SSL_state_string_long() instead of our
1175 own homebrewed ssl_state_to_string() replacement. Patch from
1176 Emile Snyder. Fixes bug 4653.
1177 - Use macros to indicate OpenSSL versions, so we don't need to worry
1178 about accidental hexadecimal bit shifts.
1179 - Remove some workaround code for OpenSSL 0.9.6 (which is no longer
1181 - Convert more instances of tor_snprintf+tor_strdup into tor_asprintf.
1182 - Use the smartlist_add_asprintf() alias more consistently.
1183 - Use a TOR_INVALID_SOCKET macro when initializing a socket to an
1184 invalid value, rather than just -1.
1185 - Rename a handful of old identifiers, mostly related to crypto
1186 structures and crypto functions. By convention, our "create an
1187 object" functions are called "type_new()", our "free an object"
1188 functions are called "type_free()", and our types indicate that
1189 they are types only with a final "_t". But a handful of older
1190 types and functions broke these rules, with function names like
1191 "type_create" or "subsystem_op_type", or with type names like
1195 Changes in version 0.2.3.10-alpha - 2011-12-16
1196 Tor 0.2.3.10-alpha fixes a critical heap-overflow security issue in
1197 Tor's buffers code. Absolutely everybody should upgrade.
1199 The bug relied on an incorrect calculation when making data continuous
1200 in one of our IO buffers, if the first chunk of the buffer was
1201 misaligned by just the wrong amount. The miscalculation would allow an
1202 attacker to overflow a piece of heap-allocated memory. To mount this
1203 attack, the attacker would need to either open a SOCKS connection to
1204 Tor's SocksPort (usually restricted to localhost), or target a Tor
1205 instance configured to make its connections through a SOCKS proxy
1206 (which Tor does not do by default).
1208 Good security practice requires that all heap-overflow bugs should be
1209 presumed to be exploitable until proven otherwise, so we are treating
1210 this as a potential code execution attack. Please upgrade immediately!
1211 This bug does not affect bufferevents-based builds of Tor. Special
1212 thanks to "Vektor" for reporting this issue to us!
1214 This release also contains a few minor bugfixes for issues discovered
1218 - Fix a heap overflow bug that could occur when trying to pull
1219 data into the first chunk of a buffer, when that chunk had
1220 already had some data drained from it. Fixes CVE-2011-2778;
1221 bugfix on 0.2.0.16-alpha. Reported by "Vektor".
1224 - If we can't attach streams to a rendezvous circuit when we
1225 finish connecting to a hidden service, clear the rendezvous
1226 circuit's stream-isolation state and try to attach streams
1227 again. Previously, we cleared rendezvous circuits' isolation
1228 state either too early (if they were freshly built) or not at all
1229 (if they had been built earlier and were cannibalized). Bugfix on
1230 0.2.3.3-alpha; fixes bug 4655.
1231 - Fix compilation of the libnatpmp helper on non-Windows. Bugfix on
1232 0.2.3.9-alpha; fixes bug 4691. Reported by Anthony G. Basile.
1233 - Fix an assertion failure when a relay with accounting enabled
1234 starts up while dormant. Fixes bug 4702; bugfix on 0.2.3.9-alpha.
1237 - Update to the December 6 2011 Maxmind GeoLite Country database.
1240 Changes in version 0.2.2.35 - 2011-12-16
1241 Tor 0.2.2.35 fixes a critical heap-overflow security issue in Tor's
1242 buffers code. Absolutely everybody should upgrade.
1244 The bug relied on an incorrect calculation when making data continuous
1245 in one of our IO buffers, if the first chunk of the buffer was
1246 misaligned by just the wrong amount. The miscalculation would allow an
1247 attacker to overflow a piece of heap-allocated memory. To mount this
1248 attack, the attacker would need to either open a SOCKS connection to
1249 Tor's SocksPort (usually restricted to localhost), or target a Tor
1250 instance configured to make its connections through a SOCKS proxy
1251 (which Tor does not do by default).
1253 Good security practice requires that all heap-overflow bugs should be
1254 presumed to be exploitable until proven otherwise, so we are treating
1255 this as a potential code execution attack. Please upgrade immediately!
1256 This bug does not affect bufferevents-based builds of Tor. Special
1257 thanks to "Vektor" for reporting this issue to us!
1259 Tor 0.2.2.35 also fixes several bugs in previous versions, including
1260 crash bugs for unusual configurations, and a long-term bug that
1261 would prevent Tor from starting on Windows machines with draconian
1264 With this release, we remind everyone that 0.2.0.x has reached its
1265 formal end-of-life. Those Tor versions have many known flaws, and
1266 nobody should be using them. You should upgrade -- ideally to the
1267 0.2.2.x series. If you're using a Linux or BSD and its packages are
1268 obsolete, stop using those packages and upgrade anyway.
1270 The Tor 0.2.1.x series is also approaching its end-of-life: it will no
1271 longer receive support after some time in early 2012.
1274 - Fix a heap overflow bug that could occur when trying to pull
1275 data into the first chunk of a buffer, when that chunk had
1276 already had some data drained from it. Fixes CVE-2011-2778;
1277 bugfix on 0.2.0.16-alpha. Reported by "Vektor".
1278 - Initialize Libevent with the EVENT_BASE_FLAG_NOLOCK flag enabled, so
1279 that it doesn't attempt to allocate a socketpair. This could cause
1280 some problems on Windows systems with overzealous firewalls. Fix for
1281 bug 4457; workaround for Libevent versions 2.0.1-alpha through
1283 - If we mark an OR connection for close based on a cell we process,
1284 don't process any further cells on it. We already avoid further
1285 reads on marked-for-close connections, but now we also discard the
1286 cells we'd already read. Fixes bug 4299; bugfix on 0.2.0.10-alpha,
1287 which was the first version where we might mark a connection for
1288 close based on processing a cell on it.
1289 - Correctly sanity-check that we don't underflow on a memory
1290 allocation (and then assert) for hidden service introduction
1291 point decryption. Bug discovered by Dan Rosenberg. Fixes bug 4410;
1292 bugfix on 0.2.1.5-alpha.
1293 - Fix a memory leak when we check whether a hidden service
1294 descriptor has any usable introduction points left. Fixes bug
1295 4424. Bugfix on 0.2.2.25-alpha.
1296 - Don't crash when we're running as a relay and don't have a GeoIP
1297 file. Bugfix on 0.2.2.34; fixes bug 4340. This backports a fix
1298 we've had in the 0.2.3.x branch already.
1299 - When running as a client, do not print a misleading (and plain
1300 wrong) log message that we're collecting "directory request"
1301 statistics: clients don't collect statistics. Also don't create a
1302 useless (because empty) stats file in the stats/ directory. Fixes
1303 bug 4353; bugfix on 0.2.2.34.
1306 - Detect failure to initialize Libevent. This fix provides better
1307 detection for future instances of bug 4457.
1308 - Avoid frequent calls to the fairly expensive cull_wedged_cpuworkers
1309 function. This was eating up hideously large amounts of time on some
1310 busy servers. Fixes bug 4518; bugfix on 0.0.9.8.
1311 - Resolve an integer overflow bug in smartlist_ensure_capacity().
1312 Fixes bug 4230; bugfix on Tor 0.1.0.1-rc. Based on a patch by
1314 - Don't warn about unused log_mutex in log.c when building with
1315 --disable-threads using a recent GCC. Fixes bug 4437; bugfix on
1316 0.1.0.6-rc which introduced --disable-threads.
1317 - When configuring, starting, or stopping an NT service, stop
1318 immediately after the service configuration attempt has succeeded
1319 or failed. Fixes bug 3963; bugfix on 0.2.0.7-alpha.
1320 - When sending a NETINFO cell, include the original address
1321 received for the other side, not its canonical address. Found
1322 by "troll_un"; fixes bug 4349; bugfix on 0.2.0.10-alpha.
1323 - Fix a typo in a hibernation-related log message. Fixes bug 4331;
1324 bugfix on 0.2.2.23-alpha; found by "tmpname0901".
1325 - Fix a memory leak in launch_direct_bridge_descriptor_fetch() that
1326 occurred when a client tried to fetch a descriptor for a bridge
1327 in ExcludeNodes. Fixes bug 4383; bugfix on 0.2.2.25-alpha.
1328 - Backport fixes for a pair of compilation warnings on Windows.
1329 Fixes bug 4521; bugfix on 0.2.2.28-beta and on 0.2.2.29-beta.
1330 - If we had ever tried to call tor_addr_to_str on an address of
1331 unknown type, we would have done a strdup on an uninitialized
1332 buffer. Now we won't. Fixes bug 4529; bugfix on 0.2.1.3-alpha.
1333 Reported by "troll_un".
1334 - Correctly detect and handle transient lookup failures from
1335 tor_addr_lookup. Fixes bug 4530; bugfix on 0.2.1.5-alpha.
1336 Reported by "troll_un".
1337 - Fix null-pointer access that could occur if TLS allocation failed.
1338 Fixes bug 4531; bugfix on 0.2.0.20-rc. Found by "troll_un".
1339 - Use tor_socket_t type for listener argument to accept(). Fixes bug
1340 4535; bugfix on 0.2.2.28-beta. Found by "troll_un".
1343 - Add two new config options for directory authorities:
1344 AuthDirFastGuarantee sets a bandwidth threshold for guaranteeing the
1345 Fast flag, and AuthDirGuardBWGuarantee sets a bandwidth threshold
1346 that is always sufficient to satisfy the bandwidth requirement for
1347 the Guard flag. Now it will be easier for researchers to simulate
1348 Tor networks with different values. Resolves ticket 4484.
1349 - When Tor ignores a hidden service specified in its configuration,
1350 include the hidden service's directory in the warning message.
1351 Previously, we would only tell the user that some hidden service
1352 was ignored. Bugfix on 0.0.6; fixes bug 4426.
1353 - Update to the December 6 2011 Maxmind GeoLite Country database.
1355 o Packaging changes:
1356 - Make it easier to automate expert package builds on Windows,
1357 by removing an absolute path from makensis.exe command.
1360 Changes in version 0.2.3.9-alpha - 2011-12-08
1361 Tor 0.2.3.9-alpha introduces initial IPv6 support for bridges, adds
1362 a "DisableNetwork" security feature that bundles can use to avoid
1363 touching the network until bridges are configured, moves forward on
1364 the pluggable transport design, fixes a flaw in the hidden service
1365 design that unnecessarily prevented clients with wrong clocks from
1366 reaching hidden services, and fixes a wide variety of other issues.
1369 - Clients can now connect to private bridges over IPv6. Bridges
1370 still need at least one IPv4 address in order to connect to
1371 other relays. Note that we don't yet handle the case where the
1372 user has two bridge lines for the same bridge (one IPv4, one
1373 IPv6). Implements parts of proposal 186.
1374 - New "DisableNetwork" config option to prevent Tor from launching any
1375 connections or accepting any connections except on a control port.
1376 Bundles and controllers can set this option before letting Tor talk
1377 to the rest of the network, for example to prevent any connections
1378 to a non-bridge address. Packages like Orbot can also use this
1379 option to instruct Tor to save power when the network is off.
1380 - Clients and bridges can now be configured to use a separate
1381 "transport" proxy. This approach makes the censorship arms race
1382 easier by allowing bridges to use protocol obfuscation plugins. It
1383 implements the "managed proxy" part of proposal 180 (ticket 3472).
1384 - When using OpenSSL 1.0.0 or later, use OpenSSL's counter mode
1385 implementation. It makes AES_CTR about 7% faster than our old one
1386 (which was about 10% faster than the one OpenSSL used to provide).
1387 Resolves ticket 4526.
1388 - Add a "tor2web mode" for clients that want to connect to hidden
1389 services non-anonymously (and possibly more quickly). As a safety
1390 measure to try to keep users from turning this on without knowing
1391 what they are doing, tor2web mode must be explicitly enabled at
1392 compile time, and a copy of Tor compiled to run in tor2web mode
1393 cannot be used as a normal Tor client. Implements feature 2553.
1394 - Add experimental support for running on Windows with IOCP and no
1395 kernel-space socket buffers. This feature is controlled by a new
1396 "UserspaceIOCPBuffers" config option (off by default), which has
1397 no effect unless Tor has been built with support for bufferevents,
1398 is running on Windows, and has enabled IOCP. This may, in the long
1399 run, help solve or mitigate bug 98.
1400 - Use a more secure consensus parameter voting algorithm. Now at
1401 least three directory authorities or a majority of them must
1402 vote on a given parameter before it will be included in the
1403 consensus. Implements proposal 178.
1406 - Hidden services now ignore the timestamps on INTRODUCE2 cells.
1407 They used to check that the timestamp was within 30 minutes
1408 of their system clock, so they could cap the size of their
1409 replay-detection cache, but that approach unnecessarily refused
1410 service to clients with wrong clocks. Bugfix on 0.2.1.6-alpha, when
1411 the v3 intro-point protocol (the first one which sent a timestamp
1412 field in the INTRODUCE2 cell) was introduced; fixes bug 3460.
1413 - Only use the EVP interface when AES acceleration is enabled,
1414 to avoid a 5-7% performance regression. Resolves issue 4525;
1415 bugfix on 0.2.3.8-alpha.
1417 o Privacy/anonymity features (bridge detection):
1418 - Make bridge SSL certificates a bit more stealthy by using random
1419 serial numbers, in the same fashion as OpenSSL when generating
1420 self-signed certificates. Implements ticket 4584.
1421 - Introduce a new config option "DynamicDHGroups", enabled by
1422 default, which provides each bridge with a unique prime DH modulus
1423 to be used during SSL handshakes. This option attempts to help
1424 against censors who might use the Apache DH modulus as a static
1425 identifier for bridges. Addresses ticket 4548.
1427 o Minor features (new/different config options):
1428 - New configuration option "DisableDebuggerAttachment" (on by default)
1429 to prevent basic debugging attachment attempts by other processes.
1430 Supports Mac OS X and Gnu/Linux. Resolves ticket 3313.
1431 - Allow MapAddress directives to specify matches against super-domains,
1432 as in "MapAddress *.torproject.org *.torproject.org.torserver.exit".
1433 Implements issue 933.
1434 - Slightly change behavior of "list" options (that is, config
1435 options that can appear more than once) when they appear both in
1436 torrc and on the command line. Previously, the command-line options
1437 would be appended to the ones from torrc. Now, the command-line
1438 options override the torrc options entirely. This new behavior
1439 allows the user to override list options (like exit policies and
1440 ports to listen on) from the command line, rather than simply
1441 appending to the list.
1442 - You can get the old (appending) command-line behavior for "list"
1443 options by prefixing the option name with a "+".
1444 - You can remove all the values for a "list" option from the command
1445 line without adding any new ones by prefixing the option name
1447 - Add experimental support for a "defaults" torrc file to be parsed
1448 before the regular torrc. Torrc options override the defaults file's
1449 options in the same way that the command line overrides the torrc.
1450 The SAVECONF controller command saves only those options which
1451 differ between the current configuration and the defaults file. HUP
1452 reloads both files. (Note: This is an experimental feature; its
1453 behavior will probably be refined in future 0.2.3.x-alpha versions
1454 to better meet packagers' needs.) Implements task 4552.
1457 - Try to make the introductory warning message that Tor prints on
1458 startup more useful for actually finding help and information.
1459 Resolves ticket 2474.
1460 - Running "make version" now displays the version of Tor that
1461 we're about to build. Idea from katmagic; resolves issue 4400.
1462 - Expire old or over-used hidden service introduction points.
1463 Required by fix for bug 3460.
1464 - Move the replay-detection cache for the RSA-encrypted parts of
1465 INTRODUCE2 cells to the introduction point data structures.
1466 Previously, we would use one replay-detection cache per hidden
1467 service. Required by fix for bug 3460.
1468 - Reduce the lifetime of elements of hidden services' Diffie-Hellman
1469 public key replay-detection cache from 60 minutes to 5 minutes. This
1470 replay-detection cache is now used only to detect multiple
1471 INTRODUCE2 cells specifying the same rendezvous point, so we can
1472 avoid launching multiple simultaneous attempts to connect to it.
1474 o Minor bugfixes (on Tor 0.2.2.x and earlier):
1475 - Resolve an integer overflow bug in smartlist_ensure_capacity().
1476 Fixes bug 4230; bugfix on Tor 0.1.0.1-rc. Based on a patch by
1478 - Fix a minor formatting issue in one of tor-gencert's error messages.
1480 - Prevent a false positive from the check-spaces script, by disabling
1481 the "whitespace between function name and (" check for functions
1483 - Fix a log message suggesting that people contact a non-existent
1484 email address. Fixes bug 3448.
1485 - Fix null-pointer access that could occur if TLS allocation failed.
1486 Fixes bug 4531; bugfix on 0.2.0.20-rc. Found by "troll_un".
1487 - Report a real bootstrap problem to the controller on router
1488 identity mismatch. Previously we just said "foo", which probably
1489 made a lot of sense at the time. Fixes bug 4169; bugfix on
1491 - If we had ever tried to call tor_addr_to_str() on an address of
1492 unknown type, we would have done a strdup() on an uninitialized
1493 buffer. Now we won't. Fixes bug 4529; bugfix on 0.2.1.3-alpha.
1494 Reported by "troll_un".
1495 - Correctly detect and handle transient lookup failures from
1496 tor_addr_lookup(). Fixes bug 4530; bugfix on 0.2.1.5-alpha.
1497 Reported by "troll_un".
1498 - Use tor_socket_t type for listener argument to accept(). Fixes bug
1499 4535; bugfix on 0.2.2.28-beta. Found by "troll_un".
1500 - Initialize conn->addr to a valid state in spawn_cpuworker(). Fixes
1501 bug 4532; found by "troll_un".
1503 o Minor bugfixes (on Tor 0.2.3.x):
1504 - Fix a compile warning in tor_inet_pton(). Bugfix on 0.2.3.8-alpha;
1506 - Don't send two ESTABLISH_RENDEZVOUS cells when opening a new
1507 circuit for use as a hidden service client's rendezvous point.
1508 Fixes bugs 4641 and 4171; bugfix on 0.2.3.3-alpha. Diagnosed
1509 with help from wanoskarnet.
1510 - Restore behavior of overriding SocksPort, ORPort, and similar
1511 options from the command line. Bugfix on 0.2.3.3-alpha.
1514 - Properly handle the case where the build-tree is not the same
1515 as the source tree when generating src/common/common_sha1.i,
1516 src/or/micro-revision.i, and src/or/or_sha1.i. Fixes bug 3953;
1517 bugfix on 0.2.0.1-alpha.
1519 o Code simplifications, cleanups, and refactorings:
1520 - Remove the pure attribute from all functions that used it
1521 previously. In many cases we assigned it incorrectly, because the
1522 functions might assert or call impure functions, and we don't have
1523 evidence that keeping the pure attribute is worthwhile. Implements
1524 changes suggested in ticket 4421.
1525 - Remove some dead code spotted by coverity. Fixes cid 432.
1526 Bugfix on 0.2.3.1-alpha, closes bug 4637.
1529 Changes in version 0.2.3.8-alpha - 2011-11-22
1530 Tor 0.2.3.8-alpha fixes some crash and assert bugs, including a
1531 socketpair-related bug that has been bothering Windows users. It adds
1532 support to serve microdescriptors to controllers, so Vidalia's network
1533 map can resume listing relays (once Vidalia implements its side),
1534 and adds better support for hardware AES acceleration. Finally, it
1535 starts the process of adjusting the bandwidth cutoff for getting the
1536 "Fast" flag from 20KB to (currently) 32KB -- preliminary results show
1537 that tiny relays harm performance more than they help network capacity.
1540 - Initialize Libevent with the EVENT_BASE_FLAG_NOLOCK flag enabled, so
1541 that it doesn't attempt to allocate a socketpair. This could cause
1542 some problems on Windows systems with overzealous firewalls. Fix for
1543 bug 4457; workaround for Libevent versions 2.0.1-alpha through
1545 - Correctly sanity-check that we don't underflow on a memory
1546 allocation (and then assert) for hidden service introduction
1547 point decryption. Bug discovered by Dan Rosenberg. Fixes bug 4410;
1548 bugfix on 0.2.1.5-alpha.
1549 - Remove the artificially low cutoff of 20KB to guarantee the Fast
1550 flag. In the past few years the average relay speed has picked
1551 up, and while the "top 7/8 of the network get the Fast flag" and
1552 "all relays with 20KB or more of capacity get the Fast flag" rules
1553 used to have the same result, now the top 7/8 of the network has
1554 a capacity more like 32KB. Bugfix on 0.2.1.14-rc. Fixes bug 4489.
1555 - Fix a rare assertion failure when checking whether a v0 hidden
1556 service descriptor has any usable introduction points left, and
1557 we don't have enough information to build a circuit to the first
1558 intro point named in the descriptor. The HS client code in
1559 0.2.3.x no longer uses v0 HS descriptors, but this assertion can
1560 trigger on (and crash) v0 HS authorities. Fixes bug 4411.
1561 Bugfix on 0.2.3.1-alpha; diagnosed by frosty_un.
1562 - Make bridge authorities not crash when they are asked for their own
1563 descriptor. Bugfix on 0.2.3.7-alpha, reported by Lucky Green.
1564 - When running as a client, do not print a misleading (and plain
1565 wrong) log message that we're collecting "directory request"
1566 statistics: clients don't collect statistics. Also don't create a
1567 useless (because empty) stats file in the stats/ directory. Fixes
1568 bug 4353; bugfix on 0.2.2.34 and 0.2.3.7-alpha.
1571 - Allow Tor controllers like Vidalia to obtain the microdescriptor
1572 for a relay by identity digest or nickname. Previously,
1573 microdescriptors were only available by their own digests, so a
1574 controller would have to ask for and parse the whole microdescriptor
1575 consensus in order to look up a single relay's microdesc. Fixes
1576 bug 3832; bugfix on 0.2.3.1-alpha.
1577 - Use OpenSSL's EVP interface for AES encryption, so that all AES
1578 operations can use hardware acceleration (if present). Resolves
1581 o Minor bugfixes (on 0.2.2.x and earlier):
1582 - Detect failure to initialize Libevent. This fix provides better
1583 detection for future instances of bug 4457.
1584 - Avoid frequent calls to the fairly expensive cull_wedged_cpuworkers
1585 function. This was eating up hideously large amounts of time on some
1586 busy servers. Fixes bug 4518; bugfix on 0.0.9.8.
1587 - Don't warn about unused log_mutex in log.c when building with
1588 --disable-threads using a recent GCC. Fixes bug 4437; bugfix on
1589 0.1.0.6-rc which introduced --disable-threads.
1590 - Allow manual 'authenticate' commands to the controller interface
1591 from netcat (nc) as well as telnet. We were rejecting them because
1592 they didn't come with the expected whitespace at the end of the
1593 command. Bugfix on 0.1.1.1-alpha; fixes bug 2893.
1594 - Fix some (not actually triggerable) buffer size checks in usage of
1595 tor_inet_ntop. Fixes bug 4434; bugfix on Tor 0.2.0.1-alpha. Patch
1597 - Fix parsing of some corner-cases with tor_inet_pton(). Fixes
1598 bug 4515; bugfix on 0.2.0.1-alpha; fix by Anders Sundman.
1599 - When configuring, starting, or stopping an NT service, stop
1600 immediately after the service configuration attempt has succeeded
1601 or failed. Fixes bug 3963; bugfix on 0.2.0.7-alpha.
1602 - When sending a NETINFO cell, include the original address
1603 received for the other side, not its canonical address. Found
1604 by "troll_un"; fixes bug 4349; bugfix on 0.2.0.10-alpha.
1605 - Rename the bench_{aes,dmap} functions to test_*, so that tinytest
1606 can pick them up when the tests aren't disabled. Bugfix on
1607 0.2.2.4-alpha which introduced tinytest.
1608 - Fix a memory leak when we check whether a hidden service
1609 descriptor has any usable introduction points left. Fixes bug
1610 4424. Bugfix on 0.2.2.25-alpha.
1611 - Fix a memory leak in launch_direct_bridge_descriptor_fetch() that
1612 occurred when a client tried to fetch a descriptor for a bridge
1613 in ExcludeNodes. Fixes bug 4383; bugfix on 0.2.2.25-alpha.
1615 o Minor bugfixes (on 0.2.3.x):
1616 - Make util unit tests build correctly with MSVC. Bugfix on
1617 0.2.3.3-alpha. Patch by Gisle Vanem.
1618 - Successfully detect AUTH_CHALLENGE cells with no recognized
1619 authentication type listed. Fixes bug 4367; bugfix on 0.2.3.6-alpha.
1621 - If a relay receives an AUTH_CHALLENGE cell it can't answer,
1622 it should still send a NETINFO cell to allow the connection to
1623 become open. Fixes bug 4368; fix on 0.2.3.6-alpha; bug found by
1625 - Log less loudly when we get an invalid authentication certificate
1626 from a source other than a directory authority: it's not unusual
1627 to see invalid certs because of clock skew. Fixes bug 4370; bugfix
1629 - Tolerate servers with more clock skew in their authentication
1630 certificates than previously. Fixes bug 4371; bugfix on
1632 - Fix a couple of compile warnings on Windows. Fixes bug 4469; bugfix
1633 on 0.2.3.4-alpha and 0.2.3.6-alpha.
1636 - Add two new config options for directory authorities:
1637 AuthDirFastGuarantee sets a bandwidth threshold for guaranteeing the
1638 Fast flag, and AuthDirGuardBWGuarantee sets a bandwidth threshold
1639 that is always sufficient to satisfy the bandwidth requirement for
1640 the Guard flag. Now it will be easier for researchers to simulate
1641 Tor networks with different values. Resolves ticket 4484.
1642 - When Tor ignores a hidden service specified in its configuration,
1643 include the hidden service's directory in the warning message.
1644 Previously, we would only tell the user that some hidden service
1645 was ignored. Bugfix on 0.0.6; fixes bug 4426.
1646 - When we fail to initialize Libevent, retry with IOCP disabled so we
1647 don't need to turn on multi-threading support in Libevent, which in
1648 turn requires a working socketpair(). This is a workaround for bug
1649 4457, which affects Libevent versions from 2.0.1-alpha through
1651 - Detect when we try to build on a platform that doesn't define
1652 AF_UNSPEC to 0. We don't work there, so refuse to compile.
1653 - Update to the November 1 2011 Maxmind GeoLite Country database.
1655 o Packaging changes:
1656 - Make it easier to automate expert package builds on Windows,
1657 by removing an absolute path from makensis.exe command.
1659 o Code simplifications and refactoring:
1660 - Remove some redundant #include directives throughout the code.
1661 Patch from Andrea Gelmini.
1662 - Unconditionally use OpenSSL's AES implementation instead of our
1663 old built-in one. OpenSSL's AES has been better for a while, and
1664 relatively few servers should still be on any version of OpenSSL
1665 that doesn't have good optimized assembly AES.
1666 - Use the name "CERTS" consistently to refer to the new cell type;
1667 we were calling it CERT in some places and CERTS in others.
1670 - Numerous new unit tests for functions in util.c and address.c by
1672 - The long-disabled benchmark tests are now split into their own
1673 ./src/test/bench binary.
1674 - The benchmark tests can now use more accurate timers than
1675 gettimeofday() when such timers are available.
1678 Changes in version 0.2.3.7-alpha - 2011-10-30
1679 Tor 0.2.3.7-alpha fixes a crash bug in 0.2.3.6-alpha introduced by
1680 the new v3 handshake. It also resolves yet another bridge address
1684 - If we mark an OR connection for close based on a cell we process,
1685 don't process any further cells on it. We already avoid further
1686 reads on marked-for-close connections, but now we also discard the
1687 cells we'd already read. Fixes bug 4299; bugfix on 0.2.0.10-alpha,
1688 which was the first version where we might mark a connection for
1689 close based on processing a cell on it.
1690 - Fix a double-free bug that would occur when we received an invalid
1691 certificate in a CERT cell in the new v3 handshake. Fixes bug 4343;
1692 bugfix on 0.2.3.6-alpha.
1693 - Bridges no longer include their address in NETINFO cells on outgoing
1694 OR connections, to allow them to blend in better with clients.
1695 Removes another avenue for enumerating bridges. Reported by
1696 "troll_un". Fixes bug 4348; bugfix on 0.2.0.10-alpha, when NETINFO
1697 cells were introduced.
1700 - Fixed a typo in a hibernation-related log message. Fixes bug 4331;
1701 bugfix on 0.2.2.23-alpha; found by "tmpname0901".
1704 Changes in version 0.2.3.6-alpha - 2011-10-26
1705 Tor 0.2.3.6-alpha includes the fix from 0.2.2.34 for a critical
1706 anonymity vulnerability where an attacker can deanonymize Tor
1707 users. Everybody should upgrade.
1709 This release also features support for a new v3 connection handshake
1710 protocol, and fixes to make hidden service connections more robust.
1713 - Implement a new handshake protocol (v3) for authenticating Tors to
1714 each other over TLS. It should be more resistant to fingerprinting
1715 than previous protocols, and should require less TLS hacking for
1716 future Tor implementations. Implements proposal 176.
1717 - Allow variable-length padding cells to disguise the length of
1718 Tor's TLS records. Implements part of proposal 184.
1720 o Privacy/anonymity fixes (clients):
1721 - Clients and bridges no longer send TLS certificate chains on
1722 outgoing OR connections. Previously, each client or bridge would
1723 use the same cert chain for all outgoing OR connections until
1724 its IP address changes, which allowed any relay that the client
1725 or bridge contacted to determine which entry guards it is using.
1726 Fixes CVE-2011-2768. Bugfix on 0.0.9pre5; found by "frosty_un".
1727 - If a relay receives a CREATE_FAST cell on a TLS connection, it
1728 no longer considers that connection as suitable for satisfying a
1729 circuit EXTEND request. Now relays can protect clients from the
1730 CVE-2011-2768 issue even if the clients haven't upgraded yet.
1731 - Directory authorities no longer assign the Guard flag to relays
1732 that haven't upgraded to the above "refuse EXTEND requests
1733 to client connections" fix. Now directory authorities can
1734 protect clients from the CVE-2011-2768 issue even if neither
1735 the clients nor the relays have upgraded yet. There's a new
1736 "GiveGuardFlagTo_CVE_2011_2768_VulnerableRelays" config option
1737 to let us transition smoothly, else tomorrow there would be no
1740 o Major bugfixes (hidden services):
1741 - Improve hidden service robustness: when an attempt to connect to
1742 a hidden service ends, be willing to refetch its hidden service
1743 descriptors from each of the HSDir relays responsible for them
1744 immediately. Previously, we would not consider refetching the
1745 service's descriptors from each HSDir for 15 minutes after the last
1746 fetch, which was inconvenient if the hidden service was not running
1747 during the first attempt. Bugfix on 0.2.0.18-alpha; fixes bug 3335.
1748 - When one of a hidden service's introduction points appears to be
1749 unreachable, stop trying it. Previously, we would keep trying
1750 to build circuits to the introduction point until we lost the
1751 descriptor, usually because the user gave up and restarted Tor.
1752 Partly fixes bug 3825.
1753 - Don't launch a useless circuit after failing to use one of a
1754 hidden service's introduction points. Previously, we would
1755 launch a new introduction circuit, but not set the hidden service
1756 which that circuit was intended to connect to, so it would never
1757 actually be used. A different piece of code would then create a
1758 new introduction circuit correctly. Bug reported by katmagic and
1759 found by Sebastian Hahn. Bugfix on 0.2.1.13-alpha; fixes bug 4212.
1761 o Major bugfixes (other):
1762 - Bridges now refuse CREATE or CREATE_FAST cells on OR connections
1763 that they initiated. Relays could distinguish incoming bridge
1764 connections from client connections, creating another avenue for
1765 enumerating bridges. Fixes CVE-2011-2769. Bugfix on 0.2.0.3-alpha.
1766 Found by "frosty_un".
1767 - Don't update the AccountingSoftLimitHitAt state file entry whenever
1768 tor gets started. This prevents a wrong average bandwidth
1769 estimate, which would cause relays to always start a new accounting
1770 interval at the earliest possible moment. Fixes bug 2003; bugfix
1771 on 0.2.2.7-alpha. Reported by BryonEldridge, who also helped
1772 immensely in tracking this bug down.
1773 - Fix a crash bug when changing node restrictions while a DNS lookup
1774 is in-progress. Fixes bug 4259; bugfix on 0.2.2.25-alpha. Bugfix
1777 o Minor bugfixes (on 0.2.2.x and earlier):
1778 - When a hidden service turns an extra service-side introduction
1779 circuit into a general-purpose circuit, free the rend_data and
1780 intro_key fields first, so we won't leak memory if the circuit
1781 is cannibalized for use as another service-side introduction
1782 circuit. Bugfix on 0.2.1.7-alpha; fixes bug 4251.
1783 - Rephrase the log message emitted if the TestSocks check is
1784 successful. Patch from Fabian Keil; fixes bug 4094.
1785 - Bridges now skip DNS self-tests, to act a little more stealthily.
1786 Fixes bug 4201; bugfix on 0.2.0.3-alpha, which first introduced
1787 bridges. Patch by "warms0x".
1788 - Remove a confusing dollar sign from the example fingerprint in the
1789 man page, and also make the example fingerprint a valid one. Fixes
1790 bug 4309; bugfix on 0.2.1.3-alpha.
1791 - Fix internal bug-checking logic that was supposed to catch
1792 failures in digest generation so that it will fail more robustly
1793 if we ask for a nonexistent algorithm. Found by Coverity Scan.
1794 Bugfix on 0.2.2.1-alpha; fixes Coverity CID 479.
1795 - Report any failure in init_keys() calls launched because our
1796 IP address has changed. Spotted by Coverity Scan. Bugfix on
1797 0.1.1.4-alpha; fixes CID 484.
1799 o Minor bugfixes (on 0.2.3.x):
1800 - Fix a bug in configure.in that kept it from building a configure
1801 script with autoconf versions earlier than 2.61. Fixes bug 2430;
1802 bugfix on 0.2.3.1-alpha.
1803 - Don't warn users that they are exposing a client port to the
1804 Internet if they have specified an RFC1918 address. Previously,
1805 we would warn if the user had specified any non-loopback
1806 address. Bugfix on 0.2.3.3-alpha. Fixes bug 4018; reported by Tas.
1807 - Fix memory leaks in the failing cases of the new SocksPort and
1808 ControlPort code. Found by Coverity Scan. Bugfix on 0.2.3.3-alpha;
1809 fixes coverity CIDs 485, 486, and 487.
1812 - When a hidden service's introduction point times out, consider
1813 trying it again during the next attempt to connect to the
1814 HS. Previously, we would not try it again unless a newly fetched
1815 descriptor contained it. Required by fixes for bugs 1297 and 3825.
1816 - The next version of Windows will be called Windows 8, and it has
1817 a major version of 6, minor version of 2. Correctly identify that
1818 version instead of calling it "Very recent version". Resolves
1819 ticket 4153; reported by funkstar.
1820 - The Bridge Authority now writes statistics on how many bridge
1821 descriptors it gave out in total, and how many unique descriptors
1822 it gave out. It also lists how often the most and least commonly
1823 fetched descriptors were given out, as well as the median and
1824 25th/75th percentile. Implements tickets 4200 and 4294.
1825 - Update to the October 4 2011 Maxmind GeoLite Country database.
1827 o Code simplifications and refactoring:
1828 - Remove some old code to remember statistics about which descriptors
1829 we've served as a directory mirror. The feature wasn't used and
1830 is outdated now that microdescriptors are around.
1831 - Rename Tor functions that turn strings into addresses, so that
1832 "parse" indicates that no hostname resolution occurs, and
1833 "lookup" indicates that hostname resolution may occur. This
1834 should help prevent mistakes in the future. Fixes bug 3512.
1837 Changes in version 0.2.2.34 - 2011-10-26
1838 Tor 0.2.2.34 fixes a critical anonymity vulnerability where an attacker
1839 can deanonymize Tor users. Everybody should upgrade.
1841 The attack relies on four components: 1) Clients reuse their TLS cert
1842 when talking to different relays, so relays can recognize a user by
1843 the identity key in her cert. 2) An attacker who knows the client's
1844 identity key can probe each guard relay to see if that identity key
1845 is connected to that guard relay right now. 3) A variety of active
1846 attacks in the literature (starting from "Low-Cost Traffic Analysis
1847 of Tor" by Murdoch and Danezis in 2005) allow a malicious website to
1848 discover the guard relays that a Tor user visiting the website is using.
1849 4) Clients typically pick three guards at random, so the set of guards
1850 for a given user could well be a unique fingerprint for her. This
1851 release fixes components #1 and #2, which is enough to block the attack;
1852 the other two remain as open research problems. Special thanks to
1853 "frosty_un" for reporting the issue to us!
1855 Clients should upgrade so they are no longer recognizable by the TLS
1856 certs they present. Relays should upgrade so they no longer allow a
1857 remote attacker to probe them to test whether unpatched clients are
1858 currently connected to them.
1860 This release also fixes several vulnerabilities that allow an attacker
1861 to enumerate bridge relays. Some bridge enumeration attacks still
1862 remain; see for example proposal 188.
1864 o Privacy/anonymity fixes (clients):
1865 - Clients and bridges no longer send TLS certificate chains on
1866 outgoing OR connections. Previously, each client or bridge would
1867 use the same cert chain for all outgoing OR connections until
1868 its IP address changes, which allowed any relay that the client
1869 or bridge contacted to determine which entry guards it is using.
1870 Fixes CVE-2011-2768. Bugfix on 0.0.9pre5; found by "frosty_un".
1871 - If a relay receives a CREATE_FAST cell on a TLS connection, it
1872 no longer considers that connection as suitable for satisfying a
1873 circuit EXTEND request. Now relays can protect clients from the
1874 CVE-2011-2768 issue even if the clients haven't upgraded yet.
1875 - Directory authorities no longer assign the Guard flag to relays
1876 that haven't upgraded to the above "refuse EXTEND requests
1877 to client connections" fix. Now directory authorities can
1878 protect clients from the CVE-2011-2768 issue even if neither
1879 the clients nor the relays have upgraded yet. There's a new
1880 "GiveGuardFlagTo_CVE_2011_2768_VulnerableRelays" config option
1881 to let us transition smoothly, else tomorrow there would be no
1884 o Privacy/anonymity fixes (bridge enumeration):
1885 - Bridge relays now do their directory fetches inside Tor TLS
1886 connections, like all the other clients do, rather than connecting
1887 directly to the DirPort like public relays do. Removes another
1888 avenue for enumerating bridges. Fixes bug 4115; bugfix on 0.2.0.35.
1889 - Bridges relays now build circuits for themselves in a more similar
1890 way to how clients build them. Removes another avenue for
1891 enumerating bridges. Fixes bug 4124; bugfix on 0.2.0.3-alpha,
1892 when bridges were introduced.
1893 - Bridges now refuse CREATE or CREATE_FAST cells on OR connections
1894 that they initiated. Relays could distinguish incoming bridge
1895 connections from client connections, creating another avenue for
1896 enumerating bridges. Fixes CVE-2011-2769. Bugfix on 0.2.0.3-alpha.
1897 Found by "frosty_un".
1900 - Fix a crash bug when changing node restrictions while a DNS lookup
1901 is in-progress. Fixes bug 4259; bugfix on 0.2.2.25-alpha. Bugfix
1903 - Don't launch a useless circuit after failing to use one of a
1904 hidden service's introduction points. Previously, we would
1905 launch a new introduction circuit, but not set the hidden service
1906 which that circuit was intended to connect to, so it would never
1907 actually be used. A different piece of code would then create a
1908 new introduction circuit correctly. Bug reported by katmagic and
1909 found by Sebastian Hahn. Bugfix on 0.2.1.13-alpha; fixes bug 4212.
1912 - Change an integer overflow check in the OpenBSD_Malloc code so
1913 that GCC is less likely to eliminate it as impossible. Patch
1914 from Mansour Moufid. Fixes bug 4059.
1915 - When a hidden service turns an extra service-side introduction
1916 circuit into a general-purpose circuit, free the rend_data and
1917 intro_key fields first, so we won't leak memory if the circuit
1918 is cannibalized for use as another service-side introduction
1919 circuit. Bugfix on 0.2.1.7-alpha; fixes bug 4251.
1920 - Bridges now skip DNS self-tests, to act a little more stealthily.
1921 Fixes bug 4201; bugfix on 0.2.0.3-alpha, which first introduced
1922 bridges. Patch by "warms0x".
1923 - Fix internal bug-checking logic that was supposed to catch
1924 failures in digest generation so that it will fail more robustly
1925 if we ask for a nonexistent algorithm. Found by Coverity Scan.
1926 Bugfix on 0.2.2.1-alpha; fixes Coverity CID 479.
1927 - Report any failure in init_keys() calls launched because our
1928 IP address has changed. Spotted by Coverity Scan. Bugfix on
1929 0.1.1.4-alpha; fixes CID 484.
1931 o Minor bugfixes (log messages and documentation):
1932 - Remove a confusing dollar sign from the example fingerprint in the
1933 man page, and also make the example fingerprint a valid one. Fixes
1934 bug 4309; bugfix on 0.2.1.3-alpha.
1935 - The next version of Windows will be called Windows 8, and it has
1936 a major version of 6, minor version of 2. Correctly identify that
1937 version instead of calling it "Very recent version". Resolves
1938 ticket 4153; reported by funkstar.
1939 - Downgrade log messages about circuit timeout calibration from
1940 "notice" to "info": they don't require or suggest any human
1941 intervention. Patch from Tom Lowenthal. Fixes bug 4063;
1942 bugfix on 0.2.2.14-alpha.
1945 - Turn on directory request statistics by default and include them in
1946 extra-info descriptors. Don't break if we have no GeoIP database.
1947 Backported from 0.2.3.1-alpha; implements ticket 3951.
1948 - Update to the October 4 2011 Maxmind GeoLite Country database.
1951 Changes in version 0.2.1.31 - 2011-10-26
1952 Tor 0.2.1.31 backports important security and privacy fixes for
1953 oldstable. This release is intended only for package maintainers and
1954 others who cannot use the 0.2.2 stable series. All others should be
1955 using Tor 0.2.2.x or newer.
1957 o Security fixes (also included in 0.2.2.x):
1958 - Replace all potentially sensitive memory comparison operations
1959 with versions whose runtime does not depend on the data being
1960 compared. This will help resist a class of attacks where an
1961 adversary can use variations in timing information to learn
1962 sensitive data. Fix for one case of bug 3122. (Safe memcmp
1963 implementation by Robert Ransom based partially on code by DJB.)
1964 - Fix an assert in parsing router descriptors containing IPv6
1965 addresses. This one took down the directory authorities when
1966 somebody tried some experimental code. Bugfix on 0.2.1.3-alpha.
1968 o Privacy/anonymity fixes (also included in 0.2.2.x):
1969 - Clients and bridges no longer send TLS certificate chains on
1970 outgoing OR connections. Previously, each client or bridge would
1971 use the same cert chain for all outgoing OR connections until
1972 its IP address changes, which allowed any relay that the client
1973 or bridge contacted to determine which entry guards it is using.
1974 Fixes CVE-2011-2768. Bugfix on 0.0.9pre5; found by "frosty_un".
1975 - If a relay receives a CREATE_FAST cell on a TLS connection, it
1976 no longer considers that connection as suitable for satisfying a
1977 circuit EXTEND request. Now relays can protect clients from the
1978 CVE-2011-2768 issue even if the clients haven't upgraded yet.
1979 - Bridges now refuse CREATE or CREATE_FAST cells on OR connections
1980 that they initiated. Relays could distinguish incoming bridge
1981 connections from client connections, creating another avenue for
1982 enumerating bridges. Fixes CVE-2011-2769. Bugfix on 0.2.0.3-alpha.
1983 Found by "frosty_un".
1984 - When receiving a hidden service descriptor, check that it is for
1985 the hidden service we wanted. Previously, Tor would store any
1986 hidden service descriptors that a directory gave it, whether it
1987 wanted them or not. This wouldn't have let an attacker impersonate
1988 a hidden service, but it did let directories pre-seed a client
1989 with descriptors that it didn't want. Bugfix on 0.0.6.
1990 - Avoid linkability based on cached hidden service descriptors: forget
1991 all hidden service descriptors cached as a client when processing a
1992 SIGNAL NEWNYM command. Fixes bug 3000; bugfix on 0.0.6.
1993 - Make the bridge directory authority refuse to answer directory
1994 requests for "all" descriptors. It used to include bridge
1995 descriptors in its answer, which was a major information leak.
1996 Found by "piebeer". Bugfix on 0.2.0.3-alpha.
1997 - Don't attach new streams to old rendezvous circuits after SIGNAL
1998 NEWNYM. Previously, we would keep using an existing rendezvous
1999 circuit if it remained open (i.e. if it were kept open by a
2000 long-lived stream, or if a new stream were attached to it before
2001 Tor could notice that it was old and no longer in use). Bugfix on
2002 0.1.1.15-rc; fixes bug 3375.
2004 o Minor bugfixes (also included in 0.2.2.x):
2005 - When we restart our relay, we might get a successful connection
2006 from the outside before we've started our reachability tests,
2007 triggering a warning: "ORPort found reachable, but I have no
2008 routerinfo yet. Failing to inform controller of success." This
2009 bug was harmless unless Tor is running under a controller
2010 like Vidalia, in which case the controller would never get a
2011 REACHABILITY_SUCCEEDED status event. Bugfix on 0.1.2.6-alpha;
2013 - Build correctly on OSX with zlib 1.2.4 and higher with all warnings
2014 enabled. Fixes bug 1526.
2015 - Remove undocumented option "-F" from tor-resolve: it hasn't done
2016 anything since 0.2.1.16-rc.
2017 - Avoid signed/unsigned comparisons by making SIZE_T_CEILING unsigned.
2018 None of the cases where we did this before were wrong, but by making
2019 this change we avoid warnings. Fixes bug 2475; bugfix on 0.2.1.28.
2020 - Fix a rare crash bug that could occur when a client was configured
2021 with a large number of bridges. Fixes bug 2629; bugfix on
2022 0.2.1.2-alpha. Bugfix by trac user "shitlei".
2023 - Correct the warning displayed when a rendezvous descriptor exceeds
2024 the maximum size. Fixes bug 2750; bugfix on 0.2.1.5-alpha. Found by
2026 - Fix an uncommon assertion failure when running with DNSPort under
2027 heavy load. Fixes bug 2933; bugfix on 0.2.0.1-alpha.
2028 - When warning about missing zlib development packages during compile,
2029 give the correct package names. Bugfix on 0.2.0.1-alpha.
2030 - Require that introduction point keys and onion keys have public
2031 exponent 65537. Bugfix on 0.2.0.10-alpha.
2032 - Do not crash when our configuration file becomes unreadable, for
2033 example due to a permissions change, between when we start up
2034 and when a controller calls SAVECONF. Fixes bug 3135; bugfix
2036 - Fix warnings from GCC 4.6's "-Wunused-but-set-variable" option.
2038 - Always NUL-terminate the sun_path field of a sockaddr_un before
2039 passing it to the kernel. (Not a security issue: kernels are
2040 smart enough to reject bad sockaddr_uns.) Found by Coverity;
2041 CID #428. Bugfix on Tor 0.2.0.3-alpha.
2042 - Don't stack-allocate the list of supplementary GIDs when we're
2043 about to log them. Stack-allocating NGROUPS_MAX gid_t elements
2044 could take up to 256K, which is way too much stack. Found by
2045 Coverity; CID #450. Bugfix on 0.2.1.7-alpha.
2047 o Minor bugfixes (only in 0.2.1.x):
2048 - Resume using micro-version numbers in 0.2.1.x: our Debian packages
2049 rely on them. Bugfix on 0.2.1.30.
2050 - Use git revisions instead of svn revisions when generating our
2051 micro-version numbers. Bugfix on 0.2.1.15-rc; fixes bug 2402.
2053 o Minor features (also included in 0.2.2.x):
2054 - Adjust the expiration time on our SSL session certificates to
2055 better match SSL certs seen in the wild. Resolves ticket 4014.
2056 - Allow nameservers with IPv6 address. Resolves bug 2574.
2057 - Update to the October 4 2011 Maxmind GeoLite Country database.
2060 Changes in version 0.2.3.5-alpha - 2011-09-28
2061 Tor 0.2.3.5-alpha fixes two bugs that make it possible to enumerate
2062 bridge relays; fixes an assertion error that many users started hitting
2063 today; and adds the ability to refill token buckets more often than
2064 once per second, allowing significant performance improvements.
2067 - Bridge relays now do their directory fetches inside Tor TLS
2068 connections, like all the other clients do, rather than connecting
2069 directly to the DirPort like public relays do. Removes another
2070 avenue for enumerating bridges. Fixes bug 4115; bugfix on 0.2.0.35.
2071 - Bridges relays now build circuits for themselves in a more similar
2072 way to how clients build them. Removes another avenue for
2073 enumerating bridges. Fixes bug 4124; bugfix on 0.2.0.3-alpha,
2074 when bridges were introduced.
2077 - Fix an "Assertion md->held_by_node == 1 failed" error that could
2078 occur when the same microdescriptor was referenced by two node_t
2079 objects at once. Fix for bug 4118; bugfix on Tor 0.2.3.1-alpha.
2081 o Major features (networking):
2082 - Add a new TokenBucketRefillInterval option to refill token buckets
2083 more frequently than once per second. This should improve network
2084 performance, alleviate queueing problems, and make traffic less
2085 bursty. Implements proposal 183; closes ticket 3630. Design by
2086 Florian Tschorsch and Björn Scheuermann; implementation by
2090 - Change an integer overflow check in the OpenBSD_Malloc code so
2091 that GCC is less likely to eliminate it as impossible. Patch
2092 from Mansour Moufid. Fixes bug 4059.
2094 o Minor bugfixes (usability):
2095 - Downgrade log messages about circuit timeout calibration from
2096 "notice" to "info": they don't require or suggest any human
2097 intervention. Patch from Tom Lowenthal. Fixes bug 4063;
2098 bugfix on 0.2.2.14-alpha.
2100 o Minor features (diagnostics):
2101 - When the system call to create a listener socket fails, log the
2102 error message explaining why. This may help diagnose bug 4027.
2105 Changes in version 0.2.3.4-alpha - 2011-09-13
2106 Tor 0.2.3.4-alpha includes the fixes from 0.2.2.33, including a slight
2107 tweak to Tor's TLS handshake that makes relays and bridges that run
2108 this new version reachable from Iran again. It also fixes a few new
2109 bugs in 0.2.3.x, and teaches relays to recognize when they're not
2110 listed in the network consensus and republish.
2112 o Major bugfixes (also part of 0.2.2.33):
2113 - Avoid an assertion failure when reloading a configuration with
2114 TrackExitHosts changes. Found and fixed by 'laruldan'. Fixes bug
2115 3923; bugfix on 0.2.2.25-alpha.
2117 o Minor features (security, also part of 0.2.2.33):
2118 - Check for replays of the public-key encrypted portion of an
2119 INTRODUCE1 cell, in addition to the current check for replays of
2120 the g^x value. This prevents a possible class of active attacks
2121 by an attacker who controls both an introduction point and a
2122 rendezvous point, and who uses the malleability of AES-CTR to
2123 alter the encrypted g^x portion of the INTRODUCE1 cell. We think
2124 that these attacks is infeasible (requiring the attacker to send
2125 on the order of zettabytes of altered cells in a short interval),
2126 but we'd rather block them off in case there are any classes of
2127 this attack that we missed. Reported by Willem Pinckaers.
2129 o Minor features (also part of 0.2.2.33):
2130 - Adjust the expiration time on our SSL session certificates to
2131 better match SSL certs seen in the wild. Resolves ticket 4014.
2132 - Change the default required uptime for a relay to be accepted as
2133 a HSDir (hidden service directory) from 24 hours to 25 hours.
2134 Improves on 0.2.0.10-alpha; resolves ticket 2649.
2135 - Add a VoteOnHidServDirectoriesV2 config option to allow directory
2136 authorities to abstain from voting on assignment of the HSDir
2137 consensus flag. Related to bug 2649.
2138 - Update to the September 6 2011 Maxmind GeoLite Country database.
2140 o Minor bugfixes (also part of 0.2.2.33):
2141 - Demote the 'replay detected' log message emitted when a hidden
2142 service receives the same Diffie-Hellman public key in two different
2143 INTRODUCE2 cells to info level. A normal Tor client can cause that
2144 log message during its normal operation. Bugfix on 0.2.1.6-alpha;
2145 fixes part of bug 2442.
2146 - Demote the 'INTRODUCE2 cell is too {old,new}' log message to info
2147 level. There is nothing that a hidden service's operator can do
2148 to fix its clients' clocks. Bugfix on 0.2.1.6-alpha; fixes part
2150 - Clarify a log message specifying the characters permitted in
2151 HiddenServiceAuthorizeClient client names. Previously, the log
2152 message said that "[A-Za-z0-9+-_]" were permitted; that could have
2153 given the impression that every ASCII character between "+" and "_"
2154 was permitted. Now we say "[A-Za-z0-9+_-]". Bugfix on 0.2.1.5-alpha.
2156 o Build fixes (also part of 0.2.2.33):
2157 - Clean up some code issues that prevented Tor from building on older
2158 BSDs. Fixes bug 3894; reported by "grarpamp".
2159 - Search for a platform-specific version of "ar" when cross-compiling.
2160 Should fix builds on iOS. Resolves bug 3909, found by Marco Bonetti.
2163 - Fix a bug where the SocksPort option (for example) would get
2164 ignored and replaced by the default if a SocksListenAddress
2165 option was set. Bugfix on 0.2.3.3-alpha; fixes bug 3936. Fix by
2169 - Relays now try regenerating and uploading their descriptor more
2170 frequently if they are not listed in the consensus, or if the
2171 version of their descriptor listed in the consensus is too
2172 old. This fix should prevent situations where a server declines
2173 to re-publish itself because it has done so too recently, even
2174 though the authorities decided not to list its recent-enough
2175 descriptor. Fix for bug 3327.
2178 - Relays now include a reason for regenerating their descriptors
2179 in an HTTP header when uploading to the authorities. This will
2180 make it easier to debug descriptor-upload issues in the future.
2181 - When starting as root and then changing our UID via the User
2182 control option, and we have a ControlSocket configured, make sure
2183 that the ControlSocket is owned by the same account that Tor will
2184 run under. Implements ticket 3421; fix by Jérémy Bobbio.
2187 - Abort if tor_vasprintf fails in connection_printf_to_buf (a
2188 utility function used in the control-port code). This shouldn't
2189 ever happen unless Tor is completely out of memory, but if it did
2190 happen and Tor somehow recovered from it, Tor could have sent a log
2191 message to a control port in the middle of a reply to a controller
2192 command. Fixes part of bug 3428; bugfix on 0.1.2.3-alpha.
2193 - Make 'FetchUselessDescriptors' cause all descriptor types and
2194 all consensus types (including microdescriptors) to get fetched.
2195 Fixes bug 3851; bugfix on 0.2.3.1-alpha.
2198 - Make a new "entry connection" struct as an internal subtype of "edge
2199 connection", to simplify the code and make exit connections smaller.
2202 Changes in version 0.2.2.33 - 2011-09-13
2203 Tor 0.2.2.33 fixes several bugs, and includes a slight tweak to Tor's
2204 TLS handshake that makes relays and bridges that run this new version
2205 reachable from Iran again.
2208 - Avoid an assertion failure when reloading a configuration with
2209 TrackExitHosts changes. Found and fixed by 'laruldan'. Fixes bug
2210 3923; bugfix on 0.2.2.25-alpha.
2212 o Minor features (security):
2213 - Check for replays of the public-key encrypted portion of an
2214 INTRODUCE1 cell, in addition to the current check for replays of
2215 the g^x value. This prevents a possible class of active attacks
2216 by an attacker who controls both an introduction point and a
2217 rendezvous point, and who uses the malleability of AES-CTR to
2218 alter the encrypted g^x portion of the INTRODUCE1 cell. We think
2219 that these attacks are infeasible (requiring the attacker to send
2220 on the order of zettabytes of altered cells in a short interval),
2221 but we'd rather block them off in case there are any classes of
2222 this attack that we missed. Reported by Willem Pinckaers.
2225 - Adjust the expiration time on our SSL session certificates to
2226 better match SSL certs seen in the wild. Resolves ticket 4014.
2227 - Change the default required uptime for a relay to be accepted as
2228 a HSDir (hidden service directory) from 24 hours to 25 hours.
2229 Improves on 0.2.0.10-alpha; resolves ticket 2649.
2230 - Add a VoteOnHidServDirectoriesV2 config option to allow directory
2231 authorities to abstain from voting on assignment of the HSDir
2232 consensus flag. Related to bug 2649.
2233 - Update to the September 6 2011 Maxmind GeoLite Country database.
2235 o Minor bugfixes (documentation and log messages):
2236 - Correct the man page to explain that HashedControlPassword and
2237 CookieAuthentication can both be set, in which case either method
2238 is sufficient to authenticate to Tor. Bugfix on 0.2.0.7-alpha,
2239 when we decided to allow these config options to both be set. Issue
2241 - Demote the 'replay detected' log message emitted when a hidden
2242 service receives the same Diffie-Hellman public key in two different
2243 INTRODUCE2 cells to info level. A normal Tor client can cause that
2244 log message during its normal operation. Bugfix on 0.2.1.6-alpha;
2245 fixes part of bug 2442.
2246 - Demote the 'INTRODUCE2 cell is too {old,new}' log message to info
2247 level. There is nothing that a hidden service's operator can do
2248 to fix its clients' clocks. Bugfix on 0.2.1.6-alpha; fixes part
2250 - Clarify a log message specifying the characters permitted in
2251 HiddenServiceAuthorizeClient client names. Previously, the log
2252 message said that "[A-Za-z0-9+-_]" were permitted; that could have
2253 given the impression that every ASCII character between "+" and "_"
2254 was permitted. Now we say "[A-Za-z0-9+_-]". Bugfix on 0.2.1.5-alpha.
2257 - Provide a substitute implementation of lround() for MSVC, which
2258 apparently lacks it. Patch from Gisle Vanem.
2259 - Clean up some code issues that prevented Tor from building on older
2260 BSDs. Fixes bug 3894; reported by "grarpamp".
2261 - Search for a platform-specific version of "ar" when cross-compiling.
2262 Should fix builds on iOS. Resolves bug 3909, found by Marco Bonetti.
2265 Changes in version 0.2.3.3-alpha - 2011-09-01
2266 Tor 0.2.3.3-alpha adds a new "stream isolation" feature to improve Tor's
2267 security, and provides client-side support for the microdescriptor
2268 and optimistic data features introduced earlier in the 0.2.3.x
2269 series. It also includes numerous critical bugfixes in the (optional)
2270 bufferevent-based networking backend.
2272 o Major features (stream isolation):
2273 - You can now configure Tor so that streams from different
2274 applications are isolated on different circuits, to prevent an
2275 attacker who sees your streams as they leave an exit node from
2276 linking your sessions to one another. To do this, choose some way
2277 to distinguish the applications: have them connect to different
2278 SocksPorts, or have one of them use SOCKS4 while the other uses
2279 SOCKS5, or have them pass different authentication strings to the
2280 SOCKS proxy. Then, use the new SocksPort syntax to configure the
2281 degree of isolation you need. This implements Proposal 171.
2282 - There's a new syntax for specifying multiple client ports (such as
2283 SOCKSPort, TransPort, DNSPort, NATDPort): you can now just declare
2284 multiple *Port entries with full addr:port syntax on each.
2285 The old *ListenAddress format is still supported, but you can't
2286 mix it with the new *Port syntax.
2288 o Major features (other):
2289 - Enable microdescriptor fetching by default for clients. This allows
2290 clients to download a much smaller amount of directory information.
2291 To disable it (and go back to the old-style consensus and
2292 descriptors), set "UseMicrodescriptors 0" in your torrc file.
2293 - Tor's firewall-helper feature, introduced in 0.2.3.1-alpha (see the
2294 "PortForwarding" config option), now supports Windows.
2295 - When using an exit relay running 0.2.3.x, clients can now
2296 "optimistically" send data before the exit relay reports that
2297 the stream has opened. This saves a round trip when starting
2298 connections where the client speaks first (such as web browsing).
2299 This behavior is controlled by a consensus parameter (currently
2300 disabled). To turn it on or off manually, use the "OptimisticData"
2301 torrc option. Implements proposal 181; code by Ian Goldberg.
2303 o Major bugfixes (bufferevents, fixes on 0.2.3.1-alpha):
2304 - When using IOCP on Windows, we need to enable Libevent windows
2306 - The IOCP backend now works even when the user has not specified
2307 the (internal, debugging-only) _UseFilteringSSLBufferevents option.
2308 Fixes part of bug 3752.
2309 - Correctly record the bytes we've read and written when using
2310 bufferevents, so that we can include them in our bandwidth history
2311 and advertised bandwidth. Fixes bug 3803.
2312 - Apply rate-limiting only at the bottom of a chain of filtering
2313 bufferevents. This prevents us from filling up internal read
2314 buffers and violating rate-limits when filtering bufferevents
2315 are enabled. Fixes part of bug 3804.
2316 - Add high-watermarks to the output buffers for filtered
2317 bufferevents. This prevents us from filling up internal write
2318 buffers and wasting CPU cycles when filtering bufferevents are
2319 enabled. Fixes part of bug 3804.
2320 - Correctly notice when data has been written from a bufferevent
2321 without flushing it completely. Fixes bug 3805.
2322 - Fix a bug where server-side tunneled bufferevent-based directory
2323 streams would get closed prematurely. Fixes bug 3814.
2324 - Fix a use-after-free error with per-connection rate-limiting
2325 buckets. Fixes bug 3888.
2327 o Major bugfixes (also part of 0.2.2.31-rc):
2328 - If we're configured to write our ControlPorts to disk, only write
2329 them after switching UID and creating the data directory. This way,
2330 we don't fail when starting up with a nonexistent DataDirectory
2331 and a ControlPortWriteToFile setting based on that directory. Fixes
2332 bug 3747; bugfix on Tor 0.2.2.26-beta.
2335 - Added a new CONF_CHANGED event so that controllers can be notified
2336 of any configuration changes made by other controllers, or by the
2337 user. Implements ticket 1692.
2338 - Use evbuffer_copyout() in inspect_evbuffer(). This fixes a memory
2339 leak when using bufferevents, and lets Libevent worry about how to
2340 best copy data out of a buffer.
2341 - Replace files in stats/ rather than appending to them. Now that we
2342 include statistics in extra-info descriptors, it makes no sense to
2343 keep old statistics forever. Implements ticket 2930.
2345 o Minor features (build compatibility):
2346 - Limited, experimental support for building with nmake and MSVC.
2347 - Provide a substitute implementation of lround() for MSVC, which
2348 apparently lacks it. Patch from Gisle Vanem.
2350 o Minor features (also part of 0.2.2.31-rc):
2351 - Update to the August 2 2011 Maxmind GeoLite Country database.
2353 o Minor bugfixes (on 0.2.3.x-alpha):
2354 - Fix a spurious warning when parsing SOCKS requests with
2355 bufferevents enabled. Fixes bug 3615; bugfix on 0.2.3.2-alpha.
2356 - Get rid of a harmless warning that could happen on relays running
2357 with bufferevents. The warning was caused by someone doing an http
2358 request to a relay's orport. Also don't warn for a few related
2359 non-errors. Fixes bug 3700; bugfix on 0.2.3.1-alpha.
2361 o Minor bugfixes (on 2.2.x and earlier):
2362 - Correct the man page to explain that HashedControlPassword and
2363 CookieAuthentication can both be set, in which case either method
2364 is sufficient to authenticate to Tor. Bugfix on 0.2.0.7-alpha,
2365 when we decided to allow these config options to both be set. Issue
2367 - The "--quiet" and "--hush" options now apply not only to Tor's
2368 behavior before logs are configured, but also to Tor's behavior in
2369 the absense of configured logs. Fixes bug 3550; bugfix on
2372 o Minor bugfixes (also part of 0.2.2.31-rc):
2373 - Write several files in text mode, on OSes that distinguish text
2374 mode from binary mode (namely, Windows). These files are:
2375 'buffer-stats', 'dirreq-stats', and 'entry-stats' on relays
2376 that collect those statistics; 'client_keys' and 'hostname' for
2377 hidden services that use authentication; and (in the tor-gencert
2378 utility) newly generated identity and signing keys. Previously,
2379 we wouldn't specify text mode or binary mode, leading to an
2380 assertion failure. Fixes bug 3607. Bugfix on 0.2.1.1-alpha (when
2381 the DirRecordUsageByCountry option which would have triggered
2382 the assertion failure was added), although this assertion failure
2383 would have occurred in tor-gencert on Windows in 0.2.0.1-alpha.
2384 - Selectively disable deprecation warnings on OS X because Lion
2385 started deprecating the shipped copy of openssl. Fixes bug 3643.
2386 - Remove an extra pair of quotation marks around the error
2387 message in control-port STATUS_GENERAL BUG events. Bugfix on
2388 0.1.2.6-alpha; fixes bug 3732.
2389 - When unable to format an address as a string, report its value
2390 as "???" rather than reusing the last formatted address. Bugfix
2393 o Code simplifications and refactoring:
2394 - Rewrite the listener-selection logic so that parsing which ports
2395 we want to listen on is now separate from binding to the ports
2399 - Building Tor with bufferevent support now requires Libevent
2400 2.0.13-stable or later. Previous versions of Libevent had bugs in
2401 SSL-related bufferevents and related issues that would make Tor
2402 work badly with bufferevents. Requiring 2.0.13-stable also allows
2403 Tor with bufferevents to take advantage of Libevent APIs
2404 introduced after 2.0.8-rc.
2407 Changes in version 0.2.2.32 - 2011-08-27
2408 The Tor 0.2.2 release series is dedicated to the memory of Andreas
2409 Pfitzmann (1958-2010), a pioneer in anonymity and privacy research,
2410 a founder of the PETS community, a leader in our field, a mentor,
2411 and a friend. He left us with these words: "I had the possibility
2412 to contribute to this world that is not as it should be. I hope I
2413 could help in some areas to make the world a better place, and that
2414 I could also encourage other people to be engaged in improving the
2415 world. Please, stay engaged. This world needs you, your love, your
2416 initiative -- now I cannot be part of that anymore."
2418 Tor 0.2.2.32, the first stable release in the 0.2.2 branch, is finally
2419 ready. More than two years in the making, this release features improved
2420 client performance and hidden service reliability, better compatibility
2421 for Android, correct behavior for bridges that listen on more than
2422 one address, more extensible and flexible directory object handling,
2423 better reporting of network statistics, improved code security, and
2424 many many other features and bugfixes.
2427 Changes in version 0.2.2.31-rc - 2011-08-17
2428 Tor 0.2.2.31-rc is the second and hopefully final release candidate
2429 for the Tor 0.2.2.x series.
2432 - Remove an extra pair of quotation marks around the error
2433 message in control-port STATUS_GENERAL BUG events. Bugfix on
2434 0.1.2.6-alpha; fixes bug 3732.
2435 - If we're configured to write our ControlPorts to disk, only write
2436 them after switching UID and creating the data directory. This way,
2437 we don't fail when starting up with a nonexistent DataDirectory
2438 and a ControlPortWriteToFile setting based on that directory. Fixes
2439 bug 3747; bugfix on Tor 0.2.2.26-beta.
2442 - Update to the August 2 2011 Maxmind GeoLite Country database.
2445 - Allow GETINFO fingerprint to return a fingerprint even when
2446 we have not yet built a router descriptor. Fixes bug 3577;
2447 bugfix on 0.2.0.1-alpha.
2448 - Write several files in text mode, on OSes that distinguish text
2449 mode from binary mode (namely, Windows). These files are:
2450 'buffer-stats', 'dirreq-stats', and 'entry-stats' on relays
2451 that collect those statistics; 'client_keys' and 'hostname' for
2452 hidden services that use authentication; and (in the tor-gencert
2453 utility) newly generated identity and signing keys. Previously,
2454 we wouldn't specify text mode or binary mode, leading to an
2455 assertion failure. Fixes bug 3607. Bugfix on 0.2.1.1-alpha (when
2456 the DirRecordUsageByCountry option which would have triggered
2457 the assertion failure was added), although this assertion failure
2458 would have occurred in tor-gencert on Windows in 0.2.0.1-alpha.
2459 - Selectively disable deprecation warnings on OS X because Lion
2460 started deprecating the shipped copy of openssl. Fixes bug 3643.
2461 - When unable to format an address as a string, report its value
2462 as "???" rather than reusing the last formatted address. Bugfix
2466 Changes in version 0.2.3.2-alpha - 2011-07-18
2467 Tor 0.2.3.2-alpha introduces two new experimental features:
2468 microdescriptors and pluggable transports. It also continues cleaning
2469 up a variety of recently introduced features.
2472 - Clients can now use microdescriptors instead of regular descriptors
2473 to build circuits. Microdescriptors are authority-generated
2474 summaries of regular descriptors' contents, designed to change
2475 very rarely (see proposal 158 for details). This feature is
2476 designed to save bandwidth, especially for clients on slow internet
2477 connections. It's off by default for now, since nearly no caches
2478 support it, but it will be on-by-default for clients in a future
2479 version. You can use the UseMicrodescriptors option to turn it on.
2480 - Tor clients using bridges can now be configured to use a separate
2481 'transport' proxy for each bridge. This approach helps to resist
2482 censorship by allowing bridges to use protocol obfuscation
2483 plugins. It implements part of proposal 180. Implements ticket 2841.
2484 - While we're trying to bootstrap, record how many TLS connections
2485 fail in each state, and report which states saw the most failures
2486 in response to any bootstrap failures. This feature may speed up
2487 diagnosis of censorship events. Implements ticket 3116.
2489 o Major bugfixes (on 0.2.3.1-alpha):
2490 - When configuring a large set of nodes in EntryNodes (as with
2491 'EntryNodes {cc}' or 'EntryNodes 1.1.1.1/16'), choose only a
2492 random subset to be guards, and choose them in random
2493 order. Fixes bug 2798.
2494 - Tor could crash when remembering a consensus in a non-used consensus
2495 flavor without having a current consensus set. Fixes bug 3361.
2496 - Comparing an unknown address to a microdescriptor's shortened exit
2497 policy would always give a "rejected" result. Fixes bug 3599.
2498 - Using microdescriptors as a client no longer prevents Tor from
2499 uploading and downloading hidden service descriptors. Fixes
2503 - Allow nameservers with IPv6 address. Resolves bug 2574.
2504 - Accept attempts to include a password authenticator in the
2505 handshake, as supported by SOCKS5. This handles SOCKS clients that
2506 don't know how to omit a password when authenticating. Resolves
2508 - When configuring a large set of nodes in EntryNodes, and there are
2509 enough of them listed as Guard so that we don't need to consider
2510 the non-guard entries, prefer the ones listed with the Guard flag.
2511 - Check for and recover from inconsistency in the microdescriptor
2512 cache. This will make it harder for us to accidentally free a
2513 microdescriptor without removing it from the appropriate data
2514 structures. Fixes issue 3135; issue noted by "wanoskarnet".
2515 - Log SSL state transitions at log level DEBUG, log domain
2516 HANDSHAKE. This can be useful for debugging censorship events.
2517 Implements ticket 3264.
2518 - Add port 6523 (Gobby) to LongLivedPorts. Patch by intrigeri;
2519 implements ticket 3439.
2521 o Minor bugfixes (on 0.2.3.1-alpha):
2522 - Do not free all general-purpose regular descriptors just
2523 because microdescriptor use is enabled. Fixes bug 3113.
2524 - Correctly link libevent_openssl when --enable-static-libevent
2525 is passed to configure. Fixes bug 3118.
2526 - Bridges should not complain during their heartbeat log messages that
2527 they are unlisted in the consensus: that's more or less the point
2528 of being a bridge. Fixes bug 3183.
2529 - Report a SIGNAL event to controllers when acting on a delayed
2530 SIGNAL NEWNYM command. Previously, we would report a SIGNAL
2531 event to the controller if we acted on a SIGNAL NEWNYM command
2532 immediately, and otherwise not report a SIGNAL event for the
2533 command at all. Fixes bug 3349.
2534 - Fix a crash when handling the SIGNAL controller command or
2535 reporting ERR-level status events with bufferevents enabled. Found
2536 by Robert Ransom. Fixes bug 3367.
2537 - Always ship the tor-fw-helper manpage in our release tarballs.
2538 Fixes bug 3389. Reported by Stephen Walker.
2539 - Fix a class of double-mark-for-close bugs when bufferevents
2540 are enabled. Fixes bug 3403.
2541 - Update tor-fw-helper to support libnatpmp-20110618. Fixes bug 3434.
2542 - Add SIGNAL to the list returned by the 'GETINFO events/names'
2543 control-port command. Fixes part of bug 3465.
2544 - Prevent using negative indices during unit test runs when read_all()
2545 fails. Spotted by coverity.
2546 - Fix a rare memory leak when checking the nodelist without it being
2547 present. Found by coverity.
2548 - Only try to download a microdescriptor-flavored consensus from
2549 a directory cache that provides them.
2551 o Minor bugfixes (on 0.2.2.x and earlier):
2552 - Assert that hidden-service-related operations are not performed
2553 using single-hop circuits. Previously, Tor would assert that
2554 client-side streams are not attached to single-hop circuits,
2555 but not that other sensitive operations on the client and service
2556 side are not performed using single-hop circuits. Fixes bug 3332;
2558 - Don't publish a new relay descriptor when we reload our onion key,
2559 unless the onion key has actually changed. Fixes bug 3263 and
2560 resolves another cause of bug 1810. Bugfix on 0.1.1.11-alpha.
2561 - Allow GETINFO fingerprint to return a fingerprint even when
2562 we have not yet built a router descriptor. Fixes bug 3577;
2563 bugfix on 0.2.0.1-alpha.
2564 - Make 'tor --digests' list hashes of all Tor source files. Bugfix
2565 on 0.2.2.4-alpha; fixes bug 3427.
2567 o Code simplification and refactoring:
2568 - Use tor_sscanf() in place of scanf() in more places through the
2569 code. This makes us a little more locale-independent, and
2570 should help shut up code-analysis tools that can't tell
2571 a safe sscanf string from a dangerous one.
2572 - Use tt_assert(), not tor_assert(), for checking for test failures.
2573 This makes the unit tests more able to go on in the event that
2575 - Split connection_about_to_close() into separate functions for each
2579 - On Windows, we now define the _WIN32_WINNT macros only if they
2580 are not already defined. This lets the person building Tor decide,
2581 if they want, to require a later version of Windows.
2584 Changes in version 0.2.2.30-rc - 2011-07-07
2585 Tor 0.2.2.30-rc is the first release candidate for the Tor 0.2.2.x
2586 series. It fixes a few smaller bugs, but generally appears stable.
2587 Please test it and let us know whether it is!
2590 - Send a SUCCEEDED stream event to the controller when a reverse
2591 resolve succeeded. Fixes bug 3536; bugfix on 0.0.8pre1. Issue
2592 discovered by katmagic.
2593 - Always NUL-terminate the sun_path field of a sockaddr_un before
2594 passing it to the kernel. (Not a security issue: kernels are
2595 smart enough to reject bad sockaddr_uns.) Found by Coverity;
2596 CID #428. Bugfix on Tor 0.2.0.3-alpha.
2597 - Don't stack-allocate the list of supplementary GIDs when we're
2598 about to log them. Stack-allocating NGROUPS_MAX gid_t elements
2599 could take up to 256K, which is way too much stack. Found by
2600 Coverity; CID #450. Bugfix on 0.2.1.7-alpha.
2601 - Add BUILDTIMEOUT_SET to the list returned by the 'GETINFO
2602 events/names' control-port command. Bugfix on 0.2.2.9-alpha;
2603 fixes part of bug 3465.
2604 - Fix a memory leak when receiving a descriptor for a hidden
2605 service we didn't ask for. Found by Coverity; CID #30. Bugfix
2609 - Update to the July 1 2011 Maxmind GeoLite Country database.
2612 Changes in version 0.2.2.29-beta - 2011-06-20
2613 Tor 0.2.2.29-beta reverts an accidental behavior change for users who
2614 have bridge lines in their torrc but don't want to use them; gets
2615 us closer to having the control socket feature working on Debian;
2616 and fixes a variety of smaller bugs.
2619 - Revert the UseBridges option to its behavior before 0.2.2.28-beta.
2620 When we changed the default behavior to "use bridges if any
2621 are listed in the torrc", we surprised users who had bridges
2622 in their torrc files but who didn't actually want to use them.
2623 Partial resolution for bug 3354.
2626 - Don't attach new streams to old rendezvous circuits after SIGNAL
2627 NEWNYM. Previously, we would keep using an existing rendezvous
2628 circuit if it remained open (i.e. if it were kept open by a
2629 long-lived stream, or if a new stream were attached to it before
2630 Tor could notice that it was old and no longer in use). Bugfix on
2631 0.1.1.15-rc; fixes bug 3375.
2634 - Fix a bug when using ControlSocketsGroupWritable with User. The
2635 directory's group would be checked against the current group, not
2636 the configured group. Patch by Jérémy Bobbio. Fixes bug 3393;
2637 bugfix on 0.2.2.26-beta.
2638 - Make connection_printf_to_buf()'s behaviour sane. Its callers
2639 expect it to emit a CRLF iff the format string ends with CRLF;
2640 it actually emitted a CRLF iff (a) the format string ended with
2641 CRLF or (b) the resulting string was over 1023 characters long or
2642 (c) the format string did not end with CRLF *and* the resulting
2643 string was 1021 characters long or longer. Bugfix on 0.1.1.9-alpha;
2644 fixes part of bug 3407.
2645 - Make send_control_event_impl()'s behaviour sane. Its callers
2646 expect it to always emit a CRLF at the end of the string; it
2647 might have emitted extra control characters as well. Bugfix on
2648 0.1.1.9-alpha; fixes another part of bug 3407.
2649 - Make crypto_rand_int() check the value of its input correctly.
2650 Previously, it accepted values up to UINT_MAX, but could return a
2651 negative number if given a value above INT_MAX+1. Found by George
2652 Kadianakis. Fixes bug 3306; bugfix on 0.2.2pre14.
2653 - Avoid a segfault when reading a malformed circuit build state
2654 with more than INT_MAX entries. Found by wanoskarnet. Bugfix on
2656 - When asked about a DNS record type we don't support via a
2657 client DNSPort, reply with NOTIMPL rather than an empty
2658 reply. Patch by intrigeri. Fixes bug 3369; bugfix on 2.0.1-alpha.
2659 - Fix a rare memory leak during stats writing. Found by coverity.
2662 - Update to the June 1 2011 Maxmind GeoLite Country database.
2664 o Code simplifications and refactoring:
2665 - Remove some dead code as indicated by coverity.
2666 - Remove a few dead assignments during router parsing. Found by
2668 - Add some forgotten return value checks during unit tests. Found
2670 - Don't use 1-bit wide signed bit fields. Found by coverity.
2673 Changes in version 0.2.2.28-beta - 2011-06-04
2674 Tor 0.2.2.28-beta makes great progress towards a new stable release: we
2675 fixed a big bug in whether relays stay in the consensus consistently,
2676 we moved closer to handling bridges and hidden services correctly,
2677 and we started the process of better handling the dreaded "my Vidalia
2678 died, and now my Tor demands a password when I try to reconnect to it"
2682 - Don't decide to make a new descriptor when receiving a HUP signal.
2683 This bug has caused a lot of 0.2.2.x relays to disappear from the
2684 consensus periodically. Fixes the most common case of triggering
2685 bug 1810; bugfix on 0.2.2.7-alpha.
2686 - Actually allow nameservers with IPv6 addresses. Fixes bug 2574.
2687 - Don't try to build descriptors if "ORPort auto" is set and we
2688 don't know our actual ORPort yet. Fix for bug 3216; bugfix on
2690 - Resolve a crash that occurred when setting BridgeRelay to 1 with
2691 accounting enabled. Fixes bug 3228; bugfix on 0.2.2.18-alpha.
2692 - Apply circuit timeouts to opened hidden-service-related circuits
2693 based on the correct start time. Previously, we would apply the
2694 circuit build timeout based on time since the circuit's creation;
2695 it was supposed to be applied based on time since the circuit
2696 entered its current state. Bugfix on 0.0.6; fixes part of bug 1297.
2697 - Use the same circuit timeout for client-side introduction
2698 circuits as for other four-hop circuits, rather than the timeout
2699 for single-hop directory-fetch circuits; the shorter timeout may
2700 have been appropriate with the static circuit build timeout in
2701 0.2.1.x and earlier, but caused many hidden service access attempts
2702 to fail with the adaptive CBT introduced in 0.2.2.2-alpha. Bugfix
2703 on 0.2.2.2-alpha; fixes another part of bug 1297.
2704 - In ticket 2511 we fixed a case where you could use an unconfigured
2705 bridge if you had configured it as a bridge the last time you ran
2706 Tor. Now fix another edge case: if you had configured it as a bridge
2707 but then switched to a different bridge via the controller, you
2708 would still be willing to use the old one. Bugfix on 0.2.0.1-alpha;
2712 - Add an __OwningControllerProcess configuration option and a
2713 TAKEOWNERSHIP control-port command. Now a Tor controller can ensure
2714 that when it exits, Tor will shut down. Implements feature 3049.
2715 - If "UseBridges 1" is set and no bridges are configured, Tor will
2716 now refuse to build any circuits until some bridges are set.
2717 If "UseBridges auto" is set, Tor will use bridges if they are
2718 configured and we are not running as a server, but otherwise will
2719 make circuits as usual. The new default is "auto". Patch by anonym,
2720 so the Tails LiveCD can stop automatically revealing you as a Tor
2724 - Fix warnings from GCC 4.6's "-Wunused-but-set-variable" option.
2725 - Remove a trailing asterisk from "exit-policy/default" in the
2726 output of the control port command "GETINFO info/names". Bugfix
2728 - Use a wide type to hold sockets when built for 64-bit Windows builds.
2730 - Warn when the user configures two HiddenServiceDir lines that point
2731 to the same directory. Bugfix on 0.0.6 (the version introducing
2732 HiddenServiceDir); fixes bug 3289.
2733 - Remove dead code from rend_cache_lookup_v2_desc_as_dir. Fixes
2734 part of bug 2748; bugfix on 0.2.0.10-alpha.
2735 - Log malformed requests for rendezvous descriptors as protocol
2736 warnings, not warnings. Also, use a more informative log message
2737 in case someone sees it at log level warning without prior
2738 info-level messages. Fixes the other part of bug 2748; bugfix
2740 - Clear the table recording the time of the last request for each
2741 hidden service descriptor from each HS directory on SIGNAL NEWNYM.
2742 Previously, we would clear our HS descriptor cache on SIGNAL
2743 NEWNYM, but if we had previously retrieved a descriptor (or tried
2744 to) from every directory responsible for it, we would refuse to
2745 fetch it again for up to 15 minutes. Bugfix on 0.2.2.25-alpha;
2747 - Fix a log message that said "bits" while displaying a value in
2748 bytes. Found by wanoskarnet. Fixes bug 3318; bugfix on
2750 - When checking for 1024-bit keys, check for 1024 bits, not 128
2751 bytes. This allows Tor to correctly discard keys of length 1017
2752 through 1023. Bugfix on 0.0.9pre5.
2755 - Relays now log the reason for publishing a new relay descriptor,
2756 so we have a better chance of hunting down instances of bug 1810.
2757 Resolves ticket 3252.
2758 - Revise most log messages that refer to nodes by nickname to
2759 instead use the "$key=nickname at address" format. This should be
2760 more useful, especially since nicknames are less and less likely
2761 to be unique. Resolves ticket 3045.
2762 - Log (at info level) when purging pieces of hidden-service-client
2763 state because of SIGNAL NEWNYM.
2766 - Remove undocumented option "-F" from tor-resolve: it hasn't done
2767 anything since 0.2.1.16-rc.
2770 Changes in version 0.2.2.27-beta - 2011-05-18
2771 Tor 0.2.2.27-beta fixes a bridge-related stability bug in the previous
2772 release, and also adds a few more general bugfixes.
2775 - Fix a crash bug when changing bridges in a running Tor process.
2776 Fixes bug 3213; bugfix on 0.2.2.26-beta.
2777 - When the controller configures a new bridge, don't wait 10 to 60
2778 seconds before trying to fetch its descriptor. Bugfix on
2779 0.2.0.3-alpha; fixes bug 3198 (suggested by 2355).
2782 - Require that onion keys have exponent 65537 in microdescriptors too.
2783 Fixes more of bug 3207; bugfix on 0.2.2.26-beta.
2784 - Tor used to limit HttpProxyAuthenticator values to 48 characters.
2785 Changed the limit to 512 characters by removing base64 newlines.
2786 Fixes bug 2752. Fix by Michael Yakubovich.
2787 - When a client starts or stops using bridges, never use a circuit
2788 that was built before the configuration change. This behavior could
2789 put at risk a user who uses bridges to ensure that her traffic
2790 only goes to the chosen addresses. Bugfix on 0.2.0.3-alpha; fixes
2794 Changes in version 0.2.2.26-beta - 2011-05-17
2795 Tor 0.2.2.26-beta fixes a variety of potential privacy problems. It
2796 also introduces a new "socksport auto" approach that should make it
2797 easier to run multiple Tors on the same system, and does a lot of
2798 cleanup to get us closer to a release candidate.
2800 o Security/privacy fixes:
2801 - Replace all potentially sensitive memory comparison operations
2802 with versions whose runtime does not depend on the data being
2803 compared. This will help resist a class of attacks where an
2804 adversary can use variations in timing information to learn
2805 sensitive data. Fix for one case of bug 3122. (Safe memcmp
2806 implementation by Robert Ransom based partially on code by DJB.)
2807 - When receiving a hidden service descriptor, check that it is for
2808 the hidden service we wanted. Previously, Tor would store any
2809 hidden service descriptors that a directory gave it, whether it
2810 wanted them or not. This wouldn't have let an attacker impersonate
2811 a hidden service, but it did let directories pre-seed a client
2812 with descriptors that it didn't want. Bugfix on 0.0.6.
2813 - On SIGHUP, do not clear out all TrackHostExits mappings, client
2814 DNS cache entries, and virtual address mappings: that's what
2815 NEWNYM is for. Fixes bug 1345; bugfix on 0.1.0.1-rc.
2818 - The options SocksPort, ControlPort, and so on now all accept a
2819 value "auto" that opens a socket on an OS-selected port. A
2820 new ControlPortWriteToFile option tells Tor to write its
2821 actual control port or ports to a chosen file. If the option
2822 ControlPortFileGroupReadable is set, the file is created as
2823 group-readable. Now users can run two Tor clients on the same
2824 system without needing to manually mess with parameters. Resolves
2825 part of ticket 3076.
2826 - Set SO_REUSEADDR on all sockets, not just listeners. This should
2827 help busy exit nodes avoid running out of useable ports just
2828 because all the ports have been used in the near past. Resolves
2832 - New "GETINFO net/listeners/(type)" controller command to return
2833 a list of addresses and ports that are bound for listeners for a
2834 given connection type. This is useful when the user has configured
2835 "SocksPort auto" and the controller needs to know which port got
2836 chosen. Resolves another part of ticket 3076.
2837 - Add a new ControlSocketsGroupWritable configuration option: when
2838 it is turned on, ControlSockets are group-writeable by the default
2839 group of the current user. Patch by Jérémy Bobbio; implements
2841 - Tor now refuses to create a ControlSocket in a directory that is
2842 world-readable (or group-readable if ControlSocketsGroupWritable
2843 is 0). This is necessary because some operating systems do not
2844 enforce permissions on an AF_UNIX sockets. Permissions on the
2845 directory holding the socket, however, seems to work everywhere.
2846 - Rate-limit a warning about failures to download v2 networkstatus
2847 documents. Resolves part of bug 1352.
2848 - Backport code from 0.2.3.x that allows directory authorities to
2849 clean their microdescriptor caches. Needed to resolve bug 2230.
2850 - When an HTTPS proxy reports "403 Forbidden", we now explain
2851 what it means rather than calling it an unexpected status code.
2852 Closes bug 2503. Patch from Michael Yakubovich.
2853 - Update to the May 1 2011 Maxmind GeoLite Country database.
2856 - Authorities now clean their microdesc cache periodically and when
2857 reading from disk initially, not only when adding new descriptors.
2858 This prevents a bug where we could lose microdescriptors. Bugfix
2859 on 0.2.2.6-alpha. Fixes bug 2230.
2860 - Do not crash when our configuration file becomes unreadable, for
2861 example due to a permissions change, between when we start up
2862 and when a controller calls SAVECONF. Fixes bug 3135; bugfix
2864 - Avoid a bug that would keep us from replacing a microdescriptor
2865 cache on Windows. (We would try to replace the file while still
2866 holding it open. That's fine on Unix, but Windows doesn't let us
2867 do that.) Bugfix on 0.2.2.6-alpha; bug found by wanoskarnet.
2868 - Add missing explanations for the authority-related torrc options
2869 RephistTrackTime, BridgePassword, and V3AuthUseLegacyKey in the
2870 man page. Resolves issue 2379.
2871 - As an authority, do not upload our own vote or signature set to
2872 ourself. It would tell us nothing new, and as of 0.2.2.24-alpha,
2873 it would get flagged as a duplicate. Resolves bug 3026.
2874 - Accept hidden service descriptors if we think we might be a hidden
2875 service directory, regardless of what our consensus says. This
2876 helps robustness, since clients and hidden services can sometimes
2877 have a more up-to-date view of the network consensus than we do,
2878 and if they think that the directory authorities list us a HSDir,
2879 we might actually be one. Related to bug 2732; bugfix on
2881 - When a controller changes TrackHostExits, remove mappings for
2882 hosts that should no longer have their exits tracked. Bugfix on
2884 - When a controller changes VirtualAddrNetwork, remove any mappings
2885 for hosts that were automapped to the old network. Bugfix on
2887 - When a controller changes one of the AutomapHosts* options, remove
2888 any mappings for hosts that should no longer be automapped. Bugfix
2890 - Do not reset the bridge descriptor download status every time we
2891 re-parse our configuration or get a configuration change. Fixes
2892 bug 3019; bugfix on 0.2.0.3-alpha.
2894 o Minor bugfixes (code cleanup):
2895 - When loading the microdesc journal, remember its current size.
2896 In 0.2.2, this helps prevent the microdesc journal from growing
2897 without limit on authorities (who are the only ones to use it in
2898 0.2.2). Fixes a part of bug 2230; bugfix on 0.2.2.6-alpha.
2899 Fix posted by "cypherpunks."
2900 - The microdesc journal is supposed to get rebuilt only if it is
2901 at least _half_ the length of the store, not _twice_ the length
2902 of the store. Bugfix on 0.2.2.6-alpha; fixes part of bug 2230.
2903 - Fix a potential null-pointer dereference while computing a
2904 consensus. Bugfix on tor-0.2.0.3-alpha, found with the help of
2906 - Avoid a possible null-pointer dereference when rebuilding the mdesc
2907 cache without actually having any descriptors to cache. Bugfix on
2908 0.2.2.6-alpha. Issue discovered using clang's static analyzer.
2909 - If we fail to compute the identity digest of a v3 legacy keypair,
2910 warn, and don't use a buffer-full of junk instead. Bugfix on
2911 0.2.1.1-alpha; fixes bug 3106.
2912 - Resolve an untriggerable issue in smartlist_string_num_isin(),
2913 where if the function had ever in the future been used to check
2914 for the presence of a too-large number, it would have given an
2915 incorrect result. (Fortunately, we only used it for 16-bit
2916 values.) Fixes bug 3175; bugfix on 0.1.0.1-rc.
2917 - Require that introduction point keys and onion handshake keys
2918 have a public exponent of 65537. Starts to fix bug 3207; bugfix
2922 - Caches no longer download and serve v2 networkstatus documents
2923 unless FetchV2Networkstatus flag is set: these documents haven't
2924 haven't been used by clients or relays since 0.2.0.x. Resolves
2928 Changes in version 0.2.3.1-alpha - 2011-05-05
2929 Tor 0.2.3.1-alpha adds some new experimental features, including support
2930 for an improved network IO backend, IOCP networking on Windows,
2931 microdescriptor caching, "fast-start" support for streams, and automatic
2932 home router configuration. There are also numerous internal improvements
2933 to try to make the code easier for developers to work with.
2935 This is the first alpha release in a new series, so expect there to be
2936 bugs. Users who would rather test out a more stable branch should
2937 stay with 0.2.2.x for now.
2940 - Tor can now optionally build with the "bufferevents" buffered IO
2941 backend provided by Libevent 2. To use this feature, make sure you
2942 have the latest possible version of Libevent, and pass the
2943 --enable-bufferevents flag to configure when building Tor from
2944 source. This feature will make our networking code more flexible,
2945 let us stack layers on each other, and let us use more efficient
2946 zero-copy transports where available.
2947 - As an experimental feature, Tor can use IOCP for networking on Windows.
2948 Once this code is tuned and optimized, it promises much better
2949 performance than the select-based backend we've used in the past. To
2950 try this feature, you must build Tor with Libevent 2, configure Tor
2951 with the "bufferevents" buffered IO backend, and add "DisableIOCP 0" to
2952 your torrc. There are known bugs here: only try this if you can help
2953 debug it as it breaks.
2954 - The EntryNodes option can now include country codes like {de} or IP
2955 addresses or network masks. Previously we had disallowed these options
2956 because we didn't have an efficient way to keep the list up to
2957 date. Fixes bug 1982, but see bug 2798 for an unresolved issue here.
2958 - Exit nodes now accept and queue data on not-yet-connected streams.
2959 Previously, the client wasn't allowed to send data until the stream was
2960 connected, which slowed down all connections. This change will enable
2961 clients to perform a "fast-start" on streams and send data without
2962 having to wait for a confirmation that the stream has opened. (Patch
2963 from Ian Goldberg; implements the server side of Proposal 174.)
2964 - Tor now has initial support for automatic port mapping on the many
2965 home routers that support NAT-PMP or UPnP. (Not yet supported on
2966 Windows). To build the support code, you'll need to have libnatpnp
2967 library and/or the libminiupnpc library, and you'll need to enable the
2968 feature specifically by passing "--enable-upnp" and/or
2969 "--enable-natpnp" to configure. To turn it on, use the new
2970 PortForwarding option.
2971 - Caches now download, cache, and serve multiple "flavors" of the
2972 consensus, including a flavor that describes microdescriptors.
2973 - Caches now download, cache, and serve microdescriptors -- small
2974 summaries of router descriptors that are authenticated by all of the
2975 directory authorities. Once enough caches are running this code,
2976 clients will be able to save significant amounts of directory bandwidth
2977 by downloading microdescriptors instead of router descriptors.
2980 - Make logging resolution configurable with a new LogTimeGranularity
2981 option, and change the default from 1 millisecond to 1 second.
2982 Implements enhancement 1668.
2983 - We log which torrc file we're using on startup. Implements ticket
2985 - Ordinarily, Tor does not count traffic from private addresses (like
2986 127.0.0.1 or 10.0.0.1) when calculating rate limits or accounting.
2987 There is now a new option, CountPrivateBandwidth, to disable this
2988 behavior. Patch from Daniel Cagara.
2989 - New --enable-static-tor configure option for building Tor as
2990 statically as possible. Idea, general hackery and thoughts from
2991 Alexei Czeskis, John Gilmore, Jacob Appelbaum. Implements ticket
2993 - If you set the NumCPUs option to 0, Tor will now try to detect how
2994 many CPUs you have. This is the new default behavior.
2995 - Turn on directory request statistics by default and include them in
2996 extra-info descriptors. Don't break if we have no GeoIP database.
2997 - Relays that set "ConnDirectionStatistics 1" write statistics on the
2998 bidirectional use of connections to disk every 24 hours.
2999 - Add a GeoIP file digest to the extra-info descriptor. Implements
3001 - The NodeFamily option -- which let you declare that you want to
3002 consider nodes to be part of a family whether they list themselves
3003 that way or not -- now allows IP address ranges and country codes.
3004 - Add a new 'Heartbeat' log message type to periodically log a message
3005 describing Tor's status at level Notice. This feature is meant for
3006 operators who log at notice, and want to make sure that their Tor
3007 server is still working. Implementation by George Kadianakis.
3009 o Minor bugfixes (on 0.2.2.25-alpha):
3010 - When loading the microdesc journal, remember its current size.
3011 In 0.2.2, this helps prevent the microdesc journal from growing
3012 without limit on authorities (who are the only ones to use it in
3013 0.2.2). Fixes a part of bug 2230; bugfix on 0.2.2.6-alpha.
3014 Fix posted by "cypherpunks."
3015 - The microdesc journal is supposed to get rebuilt only if it is
3016 at least _half_ the length of the store, not _twice_ the length
3017 of the store. Bugfix on 0.2.2.6-alpha; fixes part of bug 2230.
3018 - If as an authority we fail to compute the identity digest of a v3
3019 legacy keypair, warn, and don't use a buffer-full of junk instead.
3020 Bugfix on 0.2.1.1-alpha; fixes bug 3106.
3021 - Authorities now clean their microdesc cache periodically and when
3022 reading from disk initially, not only when adding new descriptors.
3023 This prevents a bug where we could lose microdescriptors. Bugfix
3026 o Minor features (controller):
3027 - Add a new SIGNAL event to the controller interface so that
3028 controllers can be notified when Tor handles a signal. Resolves
3029 issue 1955. Patch by John Brooks.
3030 - Add a new GETINFO option to get total bytes read and written. Patch
3031 from pipe, revised by atagar. Resolves ticket 2345.
3032 - Implement some GETINFO controller fields to provide information about
3033 the Tor process's pid, euid, username, and resource limits.
3036 - Our build system requires automake 1.6 or later to create the
3037 Makefile.in files. Previously, you could have used 1.4.
3038 This only affects developers and people building Tor from git;
3039 people who build Tor from the source distribution without changing
3040 the Makefile.am files should be fine.
3041 - Our autogen.sh script uses autoreconf to launch autoconf, automake, and
3042 so on. This is more robust against some of the failure modes
3043 associated with running the autotools pieces on their own.
3045 o Minor packaging issues:
3046 - On OpenSUSE, create the /var/run/tor directory on startup if it is not
3047 already created. Patch from Andreas Stieger. Fixes bug 2573.
3049 o Code simplifications and refactoring:
3050 - A major revision to our internal node-selecting and listing logic.
3051 Tor already had at least two major ways to look at the question of
3052 "which Tor servers do we know about": a list of router descriptors,
3053 and a list of entries in the current consensus. With
3054 microdescriptors, we're adding a third. Having so many systems
3055 without an abstraction layer over them was hurting the codebase.
3056 Now, we have a new "node_t" abstraction that presents a consistent
3057 interface to a client's view of a Tor node, and holds (nearly) all
3058 of the mutable state formerly in routerinfo_t and routerstatus_t.
3059 - The helper programs tor-gencert, tor-resolve, and tor-checkkey
3060 no longer link against Libevent: they never used it, but
3061 our library structure used to force them to link it.
3064 - Remove some old code to work around even older versions of Tor that
3065 used forked processes to handle DNS requests. Such versions of Tor
3066 are no longer in use as servers.
3068 o Documentation fixes:
3069 - Correct a broken faq link in the INSTALL file. Fixes bug 2307.
3070 - Add missing documentation for the authority-related torrc options
3071 RephistTrackTime, BridgePassword, and V3AuthUseLegacyKey. Resolves
3075 Changes in version 0.2.2.25-alpha - 2011-04-29
3076 Tor 0.2.2.25-alpha fixes many bugs: hidden service clients are more
3077 robust, routers no longer overreport their bandwidth, Win7 should crash
3078 a little less, and NEWNYM (as used by Vidalia's "new identity" button)
3079 now prevents hidden service-related activity from being linkable. It
3080 provides more information to Vidalia so you can see if your bridge is
3081 working. Also, 0.2.2.25-alpha revamps the Entry/Exit/ExcludeNodes and
3082 StrictNodes configuration options to make them more reliable, more
3083 understandable, and more regularly applied. If you use those options,
3084 please see the revised documentation for them in the manual page.
3087 - Relays were publishing grossly inflated bandwidth values because
3088 they were writing their state files wrong--now they write the
3089 correct value. Also, resume reading bandwidth history from the
3090 state file correctly. Fixes bug 2704; bugfix on 0.2.2.23-alpha.
3091 - Improve hidden service robustness: When we find that we have
3092 extended a hidden service's introduction circuit to a relay not
3093 listed as an introduction point in the HS descriptor we currently
3094 have, retry with an introduction point from the current
3095 descriptor. Previously we would just give up. Fixes bugs 1024 and
3096 1930; bugfix on 0.2.0.10-alpha.
3097 - Clients now stop trying to use an exit node associated with a given
3098 destination by TrackHostExits if they fail to reach that exit node.
3099 Fixes bug 2999. Bugfix on 0.2.0.20-rc.
3100 - Fix crash bug on platforms where gmtime and localtime can return
3101 NULL. Windows 7 users were running into this one. Fixes part of bug
3102 2077. Bugfix on all versions of Tor. Found by boboper.
3104 o Security and stability fixes:
3105 - Don't double-free a parsable, but invalid, microdescriptor, even if
3106 it is followed in the blob we're parsing by an unparsable
3107 microdescriptor. Fixes an issue reported in a comment on bug 2954.
3108 Bugfix on 0.2.2.6-alpha; fix by "cypherpunks".
3109 - If the Nickname configuration option isn't given, Tor would pick a
3110 nickname based on the local hostname as the nickname for a relay.
3111 Because nicknames are not very important in today's Tor and the
3112 "Unnamed" nickname has been implemented, this is now problematic
3113 behavior: It leaks information about the hostname without being
3114 useful at all. Fixes bug 2979; bugfix on 0.1.2.2-alpha, which
3115 introduced the Unnamed nickname. Reported by tagnaq.
3116 - Fix an uncommon assertion failure when running with DNSPort under
3117 heavy load. Fixes bug 2933; bugfix on 0.2.0.1-alpha.
3118 - Avoid linkability based on cached hidden service descriptors: forget
3119 all hidden service descriptors cached as a client when processing a
3120 SIGNAL NEWNYM command. Fixes bug 3000; bugfix on 0.0.6.
3123 - Export GeoIP information on bridge usage to controllers even if we
3124 have not yet been running for 24 hours. Now Vidalia bridge operators
3125 can get more accurate and immediate feedback about their
3126 contributions to the network.
3128 o Major features and bugfixes (node selection):
3129 - Revise and reconcile the meaning of the ExitNodes, EntryNodes,
3130 ExcludeEntryNodes, ExcludeExitNodes, ExcludeNodes, and StrictNodes
3131 options. Previously, we had been ambiguous in describing what
3132 counted as an "exit" node, and what operations exactly "StrictNodes
3133 0" would permit. This created confusion when people saw nodes built
3134 through unexpected circuits, and made it hard to tell real bugs from
3135 surprises. Now the intended behavior is:
3136 . "Exit", in the context of ExitNodes and ExcludeExitNodes, means
3137 a node that delivers user traffic outside the Tor network.
3138 . "Entry", in the context of EntryNodes, means a node used as the
3139 first hop of a multihop circuit. It doesn't include direct
3140 connections to directory servers.
3141 . "ExcludeNodes" applies to all nodes.
3142 . "StrictNodes" changes the behavior of ExcludeNodes only. When
3143 StrictNodes is set, Tor should avoid all nodes listed in
3144 ExcludeNodes, even when it will make user requests fail. When
3145 StrictNodes is *not* set, then Tor should follow ExcludeNodes
3146 whenever it can, except when it must use an excluded node to
3147 perform self-tests, connect to a hidden service, provide a
3148 hidden service, fulfill a .exit request, upload directory
3149 information, or fetch directory information.
3150 Collectively, the changes to implement the behavior fix bug 1090.
3151 - ExcludeNodes now takes precedence over EntryNodes and ExitNodes: if
3152 a node is listed in both, it's treated as excluded.
3153 - ExcludeNodes now applies to directory nodes -- as a preference if
3154 StrictNodes is 0, or an absolute requirement if StrictNodes is 1.
3155 Don't exclude all the directory authorities and set StrictNodes to 1
3156 unless you really want your Tor to break.
3157 - ExcludeNodes and ExcludeExitNodes now override exit enclaving.
3158 - ExcludeExitNodes now overrides .exit requests.
3159 - We don't use bridges listed in ExcludeNodes.
3160 - When StrictNodes is 1:
3161 . We now apply ExcludeNodes to hidden service introduction points
3162 and to rendezvous points selected by hidden service users. This
3163 can make your hidden service less reliable: use it with caution!
3164 . If we have used ExcludeNodes on ourself, do not try relay
3165 reachability self-tests.
3166 . If we have excluded all the directory authorities, we will not
3167 even try to upload our descriptor if we're a relay.
3168 . Do not honor .exit requests to an excluded node.
3169 - Remove a misfeature that caused us to ignore the Fast/Stable flags
3170 when ExitNodes is set. Bugfix on 0.2.2.7-alpha.
3171 - When the set of permitted nodes changes, we now remove any mappings
3172 introduced via TrackExitHosts to now-excluded nodes. Bugfix on
3174 - We never cannibalize a circuit that had excluded nodes on it, even
3175 if StrictNodes is 0. Bugfix on 0.1.0.1-rc.
3176 - Revert a change where we would be laxer about attaching streams to
3177 circuits than when building the circuits. This was meant to prevent
3178 a set of bugs where streams were never attachable, but our improved
3179 code here should make this unnecessary. Bugfix on 0.2.2.7-alpha.
3180 - Keep track of how many times we launch a new circuit to handle a
3181 given stream. Too many launches could indicate an inconsistency
3182 between our "launch a circuit to handle this stream" logic and our
3183 "attach this stream to one of the available circuits" logic.
3184 - Improve log messages related to excluded nodes.
3187 - Fix a spurious warning when moving from a short month to a long
3188 month on relays with month-based BandwidthAccounting. Bugfix on
3189 0.2.2.17-alpha; fixes bug 3020.
3190 - When a client finds that an origin circuit has run out of 16-bit
3191 stream IDs, we now mark it as unusable for new streams. Previously,
3192 we would try to close the entire circuit. Bugfix on 0.0.6.
3193 - Add a forgotten cast that caused a compile warning on OS X 10.6.
3194 Bugfix on 0.2.2.24-alpha.
3195 - Be more careful about reporting the correct error from a failed
3196 connect() system call. Under some circumstances, it was possible to
3197 look at an incorrect value for errno when sending the end reason.
3198 Bugfix on 0.1.0.1-rc.
3199 - Correctly handle an "impossible" overflow cases in connection byte
3200 counting, where we write or read more than 4GB on an edge connection
3201 in a single second. Bugfix on 0.1.2.8-beta.
3202 - Correct the warning displayed when a rendezvous descriptor exceeds
3203 the maximum size. Fixes bug 2750; bugfix on 0.2.1.5-alpha. Found by
3205 - Clients and hidden services now use HSDir-flagged relays for hidden
3206 service descriptor downloads and uploads even if the relays have no
3207 DirPort set and the client has disabled TunnelDirConns. This will
3208 eventually allow us to give the HSDir flag to relays with no
3209 DirPort. Fixes bug 2722; bugfix on 0.2.1.6-alpha.
3210 - Downgrade "no current certificates known for authority" message from
3211 Notice to Info. Fixes bug 2899; bugfix on 0.2.0.10-alpha.
3212 - Make the SIGNAL DUMP control-port command work on FreeBSD. Fixes bug
3213 2917. Bugfix on 0.1.1.1-alpha.
3214 - Only limit the lengths of single HS descriptors, even when multiple
3215 HS descriptors are published to an HSDir relay in a single POST
3216 operation. Fixes bug 2948; bugfix on 0.2.1.5-alpha. Found by hsdir.
3217 - Write the current time into the LastWritten line in our state file,
3218 rather than the time from the previous write attempt. Also, stop
3219 trying to use a time of -1 in our log statements. Fixes bug 3039;
3220 bugfix on 0.2.2.14-alpha.
3221 - Be more consistent in our treatment of file system paths. "~" should
3222 get expanded to the user's home directory in the Log config option.
3223 Fixes bug 2971; bugfix on 0.2.0.1-alpha, which introduced the
3224 feature for the -f and --DataDirectory options.
3227 - Make sure every relay writes a state file at least every 12 hours.
3228 Previously, a relay could go for weeks without writing its state
3229 file, and on a crash could lose its bandwidth history, capacity
3230 estimates, client country statistics, and so on. Addresses bug 3012.
3231 - Send END_STREAM_REASON_NOROUTE in response to EHOSTUNREACH errors.
3232 Clients before 0.2.1.27 didn't handle NOROUTE correctly, but such
3233 clients are already deprecated because of security bugs.
3234 - Don't allow v0 hidden service authorities to act as clients.
3235 Required by fix for bug 3000.
3236 - Ignore SIGNAL NEWNYM commands on relay-only Tor instances. Required
3237 by fix for bug 3000.
3238 - Ensure that no empty [dirreq-](read|write)-history lines are added
3239 to an extrainfo document. Implements ticket 2497.
3241 o Code simplification and refactoring:
3242 - Remove workaround code to handle directory responses from servers
3243 that had bug 539 (they would send HTTP status 503 responses _and_
3244 send a body too). Since only server versions before
3245 0.2.0.16-alpha/0.1.2.19 were affected, there is no longer reason to
3246 keep the workaround in place.
3247 - Remove the old 'fuzzy time' logic. It was supposed to be used for
3248 handling calculations where we have a known amount of clock skew and
3249 an allowed amount of unknown skew. But we only used it in three
3250 places, and we never adjusted the known/unknown skew values. This is
3251 still something we might want to do someday, but if we do, we'll
3252 want to do it differently.
3253 - Avoid signed/unsigned comparisons by making SIZE_T_CEILING unsigned.
3254 None of the cases where we did this before were wrong, but by making
3255 this change we avoid warnings. Fixes bug 2475; bugfix on 0.2.1.28.
3256 - Use GetTempDir to find the proper temporary directory location on
3257 Windows when generating temporary files for the unit tests. Patch by
3261 Changes in version 0.2.2.24-alpha - 2011-04-08
3262 Tor 0.2.2.24-alpha fixes a variety of bugs, including a big bug that
3263 prevented Tor clients from effectively using "multihomed" bridges,
3264 that is, bridges that listen on multiple ports or IP addresses so users
3265 can continue to use some of their addresses even if others get blocked.
3268 - Fix a bug where bridge users who configure the non-canonical
3269 address of a bridge automatically switch to its canonical
3270 address. If a bridge listens at more than one address, it should be
3271 able to advertise those addresses independently and any non-blocked
3272 addresses should continue to work. Bugfix on Tor 0.2.0.x. Fixes
3274 - If you configured Tor to use bridge A, and then quit and
3275 configured Tor to use bridge B instead, it would happily continue
3276 to use bridge A if it's still reachable. While this behavior is
3277 a feature if your goal is connectivity, in some scenarios it's a
3278 dangerous bug. Bugfix on Tor 0.2.0.1-alpha; fixes bug 2511.
3279 - Directory authorities now use data collected from their own
3280 uptime observations when choosing whether to assign the HSDir flag
3281 to relays, instead of trusting the uptime value the relay reports in
3282 its descriptor. This change helps prevent an attack where a small
3283 set of nodes with frequently-changing identity keys can blackhole
3284 a hidden service. (Only authorities need upgrade; others will be
3285 fine once they do.) Bugfix on 0.2.0.10-alpha; fixes bug 2709.
3288 - When we restart our relay, we might get a successful connection
3289 from the outside before we've started our reachability tests,
3290 triggering a warning: "ORPort found reachable, but I have no
3291 routerinfo yet. Failing to inform controller of success." This
3292 bug was harmless unless Tor is running under a controller
3293 like Vidalia, in which case the controller would never get a
3294 REACHABILITY_SUCCEEDED status event. Bugfix on 0.1.2.6-alpha;
3296 - Make directory authorities more accurate at recording when
3297 relays that have failed several reachability tests became
3298 unreachable, so we can provide more accuracy at assigning Stable,
3299 Guard, HSDir, etc flags. Bugfix on 0.2.0.6-alpha. Resolves bug 2716.
3300 - Fix an issue that prevented static linking of libevent on
3301 some platforms (notably Linux). Fixes bug 2698; bugfix on
3302 versions 0.2.1.23/0.2.2.8-alpha (the versions introducing
3303 the --with-static-libevent configure option).
3304 - We now ask the other side of a stream (the client or the exit)
3305 for more data on that stream when the amount of queued data on
3306 that stream dips low enough. Previously, we wouldn't ask the
3307 other side for more data until either it sent us more data (which
3308 it wasn't supposed to do if it had exhausted its window!) or we
3309 had completely flushed all our queued data. This flow control fix
3310 should improve throughput. Fixes bug 2756; bugfix on the earliest
3311 released versions of Tor (svn commit r152).
3312 - Avoid a double-mark-for-free warning when failing to attach a
3313 transparent proxy connection. (We thought we had fixed this in
3314 0.2.2.23-alpha, but it turns out our fix was checking the wrong
3315 connection.) Fixes bug 2757; bugfix on 0.1.2.1-alpha (the original
3316 bug) and 0.2.2.23-alpha (the incorrect fix).
3317 - When warning about missing zlib development packages during compile,
3318 give the correct package names. Bugfix on 0.2.0.1-alpha.
3321 - Directory authorities now log the source of a rejected POSTed v3
3323 - Make compilation with clang possible when using
3324 --enable-gcc-warnings by removing two warning options that clang
3325 hasn't implemented yet and by fixing a few warnings. Implements
3327 - When expiring circuits, use microsecond timers rather than
3328 one-second timers. This can avoid an unpleasant situation where a
3329 circuit is launched near the end of one second and expired right
3330 near the beginning of the next, and prevent fluctuations in circuit
3332 - Use computed circuit-build timeouts to decide when to launch
3333 parallel introduction circuits for hidden services. (Previously,
3334 we would retry after 15 seconds.)
3335 - Update to the April 1 2011 Maxmind GeoLite Country database.
3338 - Create the /var/run/tor directory on startup on OpenSUSE if it is
3339 not already created. Patch from Andreas Stieger. Fixes bug 2573.
3341 o Documentation changes:
3342 - Modernize the doxygen configuration file slightly. Fixes bug 2707.
3343 - Resolve all doxygen warnings except those for missing documentation.
3345 - Add doxygen documentation for more functions, fields, and types.
3348 Changes in version 0.2.2.23-alpha - 2011-03-08
3349 Tor 0.2.2.23-alpha lets relays record their bandwidth history so when
3350 they restart they don't lose their bandwidth capacity estimate. This
3351 release also fixes a diverse set of user-facing bugs, ranging from
3352 relays overrunning their rate limiting to clients falsely warning about
3353 clock skew to bridge descriptor leaks by our bridge directory authority.
3356 - Stop sending a CLOCK_SKEW controller status event whenever
3357 we fetch directory information from a relay that has a wrong clock.
3358 Instead, only inform the controller when it's a trusted authority
3359 that claims our clock is wrong. Bugfix on 0.1.2.6-alpha; fixes
3360 the rest of bug 1074.
3361 - Fix an assert in parsing router descriptors containing IPv6
3362 addresses. This one took down the directory authorities when
3363 somebody tried some experimental code. Bugfix on 0.2.1.3-alpha.
3364 - Make the bridge directory authority refuse to answer directory
3365 requests for "all" descriptors. It used to include bridge
3366 descriptors in its answer, which was a major information leak.
3367 Found by "piebeer". Bugfix on 0.2.0.3-alpha.
3368 - If relays set RelayBandwidthBurst but not RelayBandwidthRate,
3369 Tor would ignore their RelayBandwidthBurst setting,
3370 potentially using more bandwidth than expected. Bugfix on
3371 0.2.0.1-alpha. Reported by Paul Wouters. Fixes bug 2470.
3372 - Ignore and warn if the user mistakenly sets "PublishServerDescriptor
3373 hidserv" in her torrc. The 'hidserv' argument never controlled
3374 publication of hidden service descriptors. Bugfix on 0.2.0.1-alpha.
3377 - Relays now save observed peak bandwidth throughput rates to their
3378 state file (along with total usage, which was already saved)
3379 so that they can determine their correct estimated bandwidth on
3380 restart. Resolves bug 1863, where Tor relays would reset their
3381 estimated bandwidth to 0 after restarting.
3382 - Directory authorities now take changes in router IP address and
3383 ORPort into account when determining router stability. Previously,
3384 if a router changed its IP or ORPort, the authorities would not
3385 treat it as having any downtime for the purposes of stability
3386 calculation, whereas clients would experience downtime since the
3387 change could take a while to propagate to them. Resolves issue 1035.
3388 - Enable Address Space Layout Randomization (ASLR) and Data Execution
3389 Prevention (DEP) by default on Windows to make it harder for
3390 attackers to exploit vulnerabilities. Patch from John Brooks.
3392 o Minor bugfixes (on 0.2.1.x and earlier):
3393 - Fix a rare crash bug that could occur when a client was configured
3394 with a large number of bridges. Fixes bug 2629; bugfix on
3395 0.2.1.2-alpha. Bugfix by trac user "shitlei".
3396 - Avoid a double mark-for-free warning when failing to attach a
3397 transparent proxy connection. Bugfix on 0.1.2.1-alpha. Fixes
3399 - Correctly detect failure to allocate an OpenSSL BIO. Fixes bug 2378;
3400 found by "cypherpunks". This bug was introduced before the first
3401 Tor release, in svn commit r110.
3402 - Country codes aren't supported in EntryNodes until 0.2.3.x, so
3403 don't mention them in the manpage. Fixes bug 2450; issue
3404 spotted by keb and G-Lo.
3405 - Fix a bug in bandwidth history state parsing that could have been
3406 triggered if a future version of Tor ever changed the timing
3407 granularity at which bandwidth history is measured. Bugfix on
3409 - When a relay decides that its DNS is too broken for it to serve
3410 as an exit server, it advertised itself as a non-exit, but
3411 continued to act as an exit. This could create accidental
3412 partitioning opportunities for users. Instead, if a relay is
3413 going to advertise reject *:* as its exit policy, it should
3414 really act with exit policy "reject *:*". Fixes bug 2366.
3415 Bugfix on Tor 0.1.2.5-alpha. Bugfix by user "postman" on trac.
3416 - In the special case where you configure a public exit relay as your
3417 bridge, Tor would be willing to use that exit relay as the last
3418 hop in your circuit as well. Now we fail that circuit instead.
3419 Bugfix on 0.2.0.12-alpha. Fixes bug 2403. Reported by "piebeer".
3420 - Fix a bug with our locking implementation on Windows that couldn't
3421 correctly detect when a file was already locked. Fixes bug 2504,
3422 bugfix on 0.2.1.6-alpha.
3423 - Fix IPv6-related connect() failures on some platforms (BSD, OS X).
3424 Bugfix on 0.2.0.3-alpha; fixes first part of bug 2660. Patch by
3426 - Set target port in get_interface_address6() correctly. Bugfix
3427 on 0.1.1.4-alpha and 0.2.0.3-alpha; fixes second part of bug 2660.
3428 - Directory authorities are now more robust to hops back in time
3429 when calculating router stability. Previously, if a run of uptime
3430 or downtime appeared to be negative, the calculation could give
3431 incorrect results. Bugfix on 0.2.0.6-alpha; noticed when fixing
3433 - Fix an assert that got triggered when using the TestingTorNetwork
3434 configuration option and then issuing a GETINFO config-text control
3435 command. Fixes bug 2250; bugfix on 0.2.1.2-alpha.
3437 o Minor bugfixes (on 0.2.2.x):
3438 - Clients should not weight BadExit nodes as Exits in their node
3439 selection. Similarly, directory authorities should not count BadExit
3440 bandwidth as Exit bandwidth when computing bandwidth-weights.
3441 Bugfix on 0.2.2.10-alpha; fixes bug 2203.
3442 - Correctly clear our dir_read/dir_write history when there is an
3443 error parsing any bw history value from the state file. Bugfix on
3445 - Resolve a bug in verifying signatures of directory objects
3446 with digests longer than SHA1. Bugfix on 0.2.2.20-alpha.
3447 Fixes bug 2409. Found by "piebeer".
3448 - Bridge authorities no longer crash on SIGHUP when they try to
3449 publish their relay descriptor to themselves. Fixes bug 2572. Bugfix
3453 - Log less aggressively about circuit timeout changes, and improve
3454 some other circuit timeout messages. Resolves bug 2004.
3455 - Log a little more clearly about the times at which we're no longer
3456 accepting new connections. Resolves bug 2181.
3457 - Reject attempts at the client side to open connections to private
3458 IP addresses (like 127.0.0.1, 10.0.0.1, and so on) with
3459 a randomly chosen exit node. Attempts to do so are always
3460 ill-defined, generally prevented by exit policies, and usually
3461 in error. This will also help to detect loops in transparent
3462 proxy configurations. You can disable this feature by setting
3463 "ClientRejectInternalAddresses 0" in your torrc.
3464 - Always treat failure to allocate an RSA key as an unrecoverable
3466 - Update to the March 1 2011 Maxmind GeoLite Country database.
3468 o Minor features (log subsystem):
3469 - Add documentation for configuring logging at different severities in
3470 different log domains. We've had this feature since 0.2.1.1-alpha,
3471 but for some reason it never made it into the manpage. Fixes
3473 - Make it simpler to specify "All log domains except for A and B".
3474 Previously you needed to say "[*,~A,~B]". Now you can just say
3476 - Add a "LogMessageDomains 1" option to include the domains of log
3477 messages along with the messages. Without this, there's no way
3478 to use log domains without reading the source or doing a lot
3481 o Packaging changes:
3482 - Stop shipping the Tor specs files and development proposal documents
3483 in the tarball. They are now in a separate git repository at
3484 git://git.torproject.org/torspec.git
3487 Changes in version 0.2.1.30 - 2011-02-23
3488 Tor 0.2.1.30 fixes a variety of less critical bugs. The main other
3489 change is a slight tweak to Tor's TLS handshake that makes relays
3490 and bridges that run this new version reachable from Iran again.
3491 We don't expect this tweak will win the arms race long-term, but it
3492 buys us time until we roll out a better solution.
3495 - Stop sending a CLOCK_SKEW controller status event whenever
3496 we fetch directory information from a relay that has a wrong clock.
3497 Instead, only inform the controller when it's a trusted authority
3498 that claims our clock is wrong. Bugfix on 0.1.2.6-alpha; fixes
3499 the rest of bug 1074.
3500 - Fix a bounds-checking error that could allow an attacker to
3501 remotely crash a directory authority. Bugfix on 0.2.1.5-alpha.
3503 - If relays set RelayBandwidthBurst but not RelayBandwidthRate,
3504 Tor would ignore their RelayBandwidthBurst setting,
3505 potentially using more bandwidth than expected. Bugfix on
3506 0.2.0.1-alpha. Reported by Paul Wouters. Fixes bug 2470.
3507 - Ignore and warn if the user mistakenly sets "PublishServerDescriptor
3508 hidserv" in her torrc. The 'hidserv' argument never controlled
3509 publication of hidden service descriptors. Bugfix on 0.2.0.1-alpha.
3512 - Adjust our TLS Diffie-Hellman parameters to match those used by
3514 - Update to the February 1 2011 Maxmind GeoLite Country database.
3517 - Check for and reject overly long directory certificates and
3518 directory tokens before they have a chance to hit any assertions.
3519 Bugfix on 0.2.1.28. Found by "doorss".
3520 - Bring the logic that gathers routerinfos and assesses the
3521 acceptability of circuits into line. This prevents a Tor OP from
3522 getting locked in a cycle of choosing its local OR as an exit for a
3523 path (due to a .exit request) and then rejecting the circuit because
3524 its OR is not listed yet. It also prevents Tor clients from using an
3525 OR running in the same instance as an exit (due to a .exit request)
3526 if the OR does not meet the same requirements expected of an OR
3527 running elsewhere. Fixes bug 1859; bugfix on 0.1.0.1-rc.
3529 o Packaging changes:
3530 - Stop shipping the Tor specs files and development proposal documents
3531 in the tarball. They are now in a separate git repository at
3532 git://git.torproject.org/torspec.git
3533 - Do not include Git version tags as though they are SVN tags when
3534 generating a tarball from inside a repository that has switched
3535 between branches. Bugfix on 0.2.1.15-rc; fixes bug 2402.
3538 Changes in version 0.2.2.22-alpha - 2011-01-25
3539 Tor 0.2.2.22-alpha fixes a few more less-critical security issues. The
3540 main other change is a slight tweak to Tor's TLS handshake that makes
3541 relays and bridges that run this new version reachable from Iran again.
3542 We don't expect this tweak will win the arms race long-term, but it
3543 will buy us a bit more time until we roll out a better solution.
3546 - Fix a bounds-checking error that could allow an attacker to
3547 remotely crash a directory authority. Bugfix on 0.2.1.5-alpha.
3549 - Don't assert when changing from bridge to relay or vice versa
3550 via the controller. The assert happened because we didn't properly
3551 initialize our keys in this case. Bugfix on 0.2.2.18-alpha; fixes
3552 bug 2433. Reported by bastik.
3555 - Adjust our TLS Diffie-Hellman parameters to match those used by
3557 - Provide a log message stating which geoip file we're parsing
3558 instead of just stating that we're parsing the geoip file.
3559 Implements ticket 2432.
3562 - Check for and reject overly long directory certificates and
3563 directory tokens before they have a chance to hit any assertions.
3564 Bugfix on 0.2.1.28 / 0.2.2.20-alpha. Found by "doorss".
3567 Changes in version 0.2.2.21-alpha - 2011-01-15
3568 Tor 0.2.2.21-alpha includes all the patches from Tor 0.2.1.29, which
3569 continues our recent code security audit work. The main fix resolves
3570 a remote heap overflow vulnerability that can allow remote code
3571 execution (CVE-2011-0427). Other fixes address a variety of assert
3572 and crash bugs, most of which we think are hard to exploit remotely.
3574 o Major bugfixes (security), also included in 0.2.1.29:
3575 - Fix a heap overflow bug where an adversary could cause heap
3576 corruption. This bug probably allows remote code execution
3577 attacks. Reported by "debuger". Fixes CVE-2011-0427. Bugfix on
3579 - Prevent a denial-of-service attack by disallowing any
3580 zlib-compressed data whose compression factor is implausibly
3581 high. Fixes part of bug 2324; reported by "doorss".
3582 - Zero out a few more keys in memory before freeing them. Fixes
3583 bug 2384 and part of bug 2385. These key instances found by
3584 "cypherpunks", based on Andrew Case's report about being able
3585 to find sensitive data in Tor's memory space if you have enough
3586 permissions. Bugfix on 0.0.2pre9.
3588 o Major bugfixes (crashes), also included in 0.2.1.29:
3589 - Prevent calls to Libevent from inside Libevent log handlers.
3590 This had potential to cause a nasty set of crashes, especially
3591 if running Libevent with debug logging enabled, and running
3592 Tor with a controller watching for low-severity log messages.
3593 Bugfix on 0.1.0.2-rc. Fixes bug 2190.
3594 - Add a check for SIZE_T_MAX to tor_realloc() to try to avoid
3595 underflow errors there too. Fixes the other part of bug 2324.
3596 - Fix a bug where we would assert if we ever had a
3597 cached-descriptors.new file (or another file read directly into
3598 memory) of exactly SIZE_T_CEILING bytes. Fixes bug 2326; bugfix
3599 on 0.2.1.25. Found by doorss.
3600 - Fix some potential asserts and parsing issues with grossly
3601 malformed router caches. Fixes bug 2352; bugfix on Tor 0.2.1.27.
3604 o Minor bugfixes (other), also included in 0.2.1.29:
3605 - Fix a bug with handling misformed replies to reverse DNS lookup
3606 requests in DNSPort. Bugfix on Tor 0.2.0.1-alpha. Related to a
3607 bug reported by doorss.
3608 - Fix compilation on mingw when a pthreads compatibility library
3609 has been installed. (We don't want to use it, so we shouldn't
3610 be including pthread.h.) Fixes bug 2313; bugfix on 0.1.0.1-rc.
3611 - Fix a bug where we would declare that we had run out of virtual
3612 addresses when the address space was only half-exhausted. Bugfix
3614 - Correctly handle the case where AutomapHostsOnResolve is set but
3615 no virtual addresses are available. Fixes bug 2328; bugfix on
3616 0.1.2.1-alpha. Bug found by doorss.
3617 - Correctly handle wrapping around when we run out of virtual
3618 address space. Found by cypherpunks; bugfix on 0.2.0.5-alpha.
3620 o Minor features, also included in 0.2.1.29:
3621 - Update to the January 1 2011 Maxmind GeoLite Country database.
3622 - Introduce output size checks on all of our decryption functions.
3624 o Build changes, also included in 0.2.1.29:
3625 - Tor does not build packages correctly with Automake 1.6 and earlier;
3626 added a check to Makefile.am to make sure that we're building with
3627 Automake 1.7 or later.
3628 - The 0.2.1.28 tarball was missing src/common/OpenBSD_malloc_Linux.c
3629 because we built it with a too-old version of automake. Thus that
3630 release broke ./configure --enable-openbsd-malloc, which is popular
3631 among really fast exit relays on Linux.
3633 o Major bugfixes, new in 0.2.2.21-alpha:
3634 - Prevent crash/heap corruption when the cbtnummodes consensus
3635 parameter is set to 0 or large values. Fixes bug 2317; bugfix
3638 o Major features, new in 0.2.2.21-alpha:
3639 - Introduce minimum/maximum values that clients will believe
3640 from the consensus. Now we'll have a better chance to avoid crashes
3641 or worse when a consensus param has a weird value.
3643 o Minor features, new in 0.2.2.21-alpha:
3644 - Make sure to disable DirPort if running as a bridge. DirPorts aren't
3645 used on bridges, and it makes bridge scanning somewhat easier.
3646 - If writing the state file to disk fails, wait up to an hour before
3647 retrying again, rather than trying again each second. Fixes bug
3648 2346; bugfix on Tor 0.1.1.3-alpha.
3649 - Make Libevent log messages get delivered to controllers later,
3650 and not from inside the Libevent log handler. This prevents unsafe
3651 reentrant Libevent calls while still letting the log messages
3653 - Detect platforms that brokenly use a signed size_t, and refuse to
3654 build there. Found and analyzed by doorss and rransom.
3655 - Fix a bunch of compile warnings revealed by mingw with gcc 4.5.
3658 o Minor bugfixes, new in 0.2.2.21-alpha:
3659 - Handle SOCKS messages longer than 128 bytes long correctly, rather
3660 than waiting forever for them to finish. Fixes bug 2330; bugfix
3661 on 0.2.0.16-alpha. Found by doorss.
3662 - Add assertions to check for overflow in arguments to
3663 base32_encode() and base32_decode(); fix a signed-unsigned
3664 comparison there too. These bugs are not actually reachable in Tor,
3665 but it's good to prevent future errors too. Found by doorss.
3666 - Correctly detect failures to create DNS requests when using Libevent
3667 versions before v2. (Before Libevent 2, we used our own evdns
3668 implementation. Its return values for Libevent's evdns_resolve_*()
3669 functions are not consistent with those from Libevent.) Fixes bug
3670 2363; bugfix on 0.2.2.6-alpha. Found by "lodger".
3672 o Documentation, new in 0.2.2.21-alpha:
3673 - Document the default socks host and port (127.0.0.1:9050) for
3677 Changes in version 0.2.1.29 - 2011-01-15
3678 Tor 0.2.1.29 continues our recent code security audit work. The main
3679 fix resolves a remote heap overflow vulnerability that can allow remote
3680 code execution. Other fixes address a variety of assert and crash bugs,
3681 most of which we think are hard to exploit remotely.
3683 o Major bugfixes (security):
3684 - Fix a heap overflow bug where an adversary could cause heap
3685 corruption. This bug probably allows remote code execution
3686 attacks. Reported by "debuger". Fixes CVE-2011-0427. Bugfix on
3688 - Prevent a denial-of-service attack by disallowing any
3689 zlib-compressed data whose compression factor is implausibly
3690 high. Fixes part of bug 2324; reported by "doorss".
3691 - Zero out a few more keys in memory before freeing them. Fixes
3692 bug 2384 and part of bug 2385. These key instances found by
3693 "cypherpunks", based on Andrew Case's report about being able
3694 to find sensitive data in Tor's memory space if you have enough
3695 permissions. Bugfix on 0.0.2pre9.
3697 o Major bugfixes (crashes):
3698 - Prevent calls to Libevent from inside Libevent log handlers.
3699 This had potential to cause a nasty set of crashes, especially
3700 if running Libevent with debug logging enabled, and running
3701 Tor with a controller watching for low-severity log messages.
3702 Bugfix on 0.1.0.2-rc. Fixes bug 2190.
3703 - Add a check for SIZE_T_MAX to tor_realloc() to try to avoid
3704 underflow errors there too. Fixes the other part of bug 2324.
3705 - Fix a bug where we would assert if we ever had a
3706 cached-descriptors.new file (or another file read directly into
3707 memory) of exactly SIZE_T_CEILING bytes. Fixes bug 2326; bugfix
3708 on 0.2.1.25. Found by doorss.
3709 - Fix some potential asserts and parsing issues with grossly
3710 malformed router caches. Fixes bug 2352; bugfix on Tor 0.2.1.27.
3713 o Minor bugfixes (other):
3714 - Fix a bug with handling misformed replies to reverse DNS lookup
3715 requests in DNSPort. Bugfix on Tor 0.2.0.1-alpha. Related to a
3716 bug reported by doorss.
3717 - Fix compilation on mingw when a pthreads compatibility library
3718 has been installed. (We don't want to use it, so we shouldn't
3719 be including pthread.h.) Fixes bug 2313; bugfix on 0.1.0.1-rc.
3720 - Fix a bug where we would declare that we had run out of virtual
3721 addresses when the address space was only half-exhausted. Bugfix
3723 - Correctly handle the case where AutomapHostsOnResolve is set but
3724 no virtual addresses are available. Fixes bug 2328; bugfix on
3725 0.1.2.1-alpha. Bug found by doorss.
3726 - Correctly handle wrapping around to when we run out of virtual
3727 address space. Found by cypherpunks, bugfix on 0.2.0.5-alpha.
3728 - The 0.2.1.28 tarball was missing src/common/OpenBSD_malloc_Linux.c
3729 because we built it with a too-old version of automake. Thus that
3730 release broke ./configure --enable-openbsd-malloc, which is popular
3731 among really fast exit relays on Linux.
3734 - Update to the January 1 2011 Maxmind GeoLite Country database.
3735 - Introduce output size checks on all of our decryption functions.
3738 - Tor does not build packages correctly with Automake 1.6 and earlier;
3739 added a check to Makefile.am to make sure that we're building with
3740 Automake 1.7 or later.
3743 Changes in version 0.2.2.20-alpha - 2010-12-17
3744 Tor 0.2.2.20-alpha does some code cleanup to reduce the risk of remotely
3745 exploitable bugs. We also fix a variety of other significant bugs,
3746 change the IP address for one of our directory authorities, and update
3747 the minimum version that Tor relays must run to join the network.
3750 - Fix a remotely exploitable bug that could be used to crash instances
3751 of Tor remotely by overflowing on the heap. Remote-code execution
3752 hasn't been confirmed, but can't be ruled out. Everyone should
3753 upgrade. Bugfix on the 0.1.1 series and later.
3754 - Fix a bug that could break accounting on 64-bit systems with large
3755 time_t values, making them hibernate for impossibly long intervals.
3756 Fixes bug 2146. Bugfix on 0.0.9pre6; fix by boboper.
3757 - Fix a logic error in directory_fetches_from_authorities() that
3758 would cause all _non_-exits refusing single-hop-like circuits
3759 to fetch from authorities, when we wanted to have _exits_ fetch
3760 from authorities. Fixes more of 2097. Bugfix on 0.2.2.16-alpha;
3762 - Fix a stream fairness bug that would cause newer streams on a given
3763 circuit to get preference when reading bytes from the origin or
3764 destination. Fixes bug 2210. Fix by Mashael AlSabah. This bug was
3765 introduced before the first Tor release, in svn revision r152.
3767 o Directory authority changes:
3768 - Change IP address and ports for gabelmoo (v3 directory authority).
3771 - Avoid crashes when AccountingMax is set on clients. Fixes bug 2235.
3772 Bugfix on 0.2.2.18-alpha. Diagnosed by boboper.
3773 - Fix an off-by-one error in calculating some controller command
3774 argument lengths. Fortunately, this mistake is harmless since
3775 the controller code does redundant NUL termination too. Found by
3776 boboper. Bugfix on 0.1.1.1-alpha.
3777 - Do not dereference NULL if a bridge fails to build its
3778 extra-info descriptor. Found by an anonymous commenter on
3779 Trac. Bugfix on 0.2.2.19-alpha.
3782 - Update to the December 1 2010 Maxmind GeoLite Country database.
3783 - Directory authorities now reject relays running any versions of
3784 Tor between 0.2.1.3-alpha and 0.2.1.18 inclusive; they have
3785 known bugs that keep RELAY_EARLY cells from working on rendezvous
3786 circuits. Followup to fix for bug 2081.
3787 - Directory authorities now reject relays running any version of Tor
3788 older than 0.2.0.26-rc. That version is the earliest that fetches
3789 current directory information correctly. Fixes bug 2156.
3790 - Report only the top 10 ports in exit-port stats in order not to
3791 exceed the maximum extra-info descriptor length of 50 KB. Implements
3795 Changes in version 0.2.1.28 - 2010-12-17
3796 Tor 0.2.1.28 does some code cleanup to reduce the risk of remotely
3797 exploitable bugs. We also took this opportunity to change the IP address
3798 for one of our directory authorities, and to update the geoip database
3802 - Fix a remotely exploitable bug that could be used to crash instances
3803 of Tor remotely by overflowing on the heap. Remote-code execution
3804 hasn't been confirmed, but can't be ruled out. Everyone should
3805 upgrade. Bugfix on the 0.1.1 series and later.
3807 o Directory authority changes:
3808 - Change IP address and ports for gabelmoo (v3 directory authority).
3811 - Update to the December 1 2010 Maxmind GeoLite Country database.
3814 Changes in version 0.2.1.27 - 2010-11-23
3815 Yet another OpenSSL security patch broke its compatibility with Tor:
3816 Tor 0.2.1.27 makes relays work with openssl 0.9.8p and 1.0.0.b. We
3817 also took this opportunity to fix several crash bugs, integrate a new
3818 directory authority, and update the bundled GeoIP database.
3821 - Resolve an incompatibility with OpenSSL 0.9.8p and OpenSSL 1.0.0b:
3822 No longer set the tlsext_host_name extension on server SSL objects;
3823 but continue to set it on client SSL objects. Our goal in setting
3824 it was to imitate a browser, not a vhosting server. Fixes bug 2204;
3825 bugfix on 0.2.1.1-alpha.
3826 - Do not log messages to the controller while shrinking buffer
3827 freelists. Doing so would sometimes make the controller connection
3828 try to allocate a buffer chunk, which would mess up the internals
3829 of the freelist and cause an assertion failure. Fixes bug 1125;
3830 fixed by Robert Ransom. Bugfix on 0.2.0.16-alpha.
3831 - Learn our external IP address when we're a relay or bridge, even if
3832 we set PublishServerDescriptor to 0. Bugfix on 0.2.0.3-alpha,
3833 where we introduced bridge relays that don't need to publish to
3834 be useful. Fixes bug 2050.
3835 - Do even more to reject (and not just ignore) annotations on
3836 router descriptors received anywhere but from the cache. Previously
3837 we would ignore such annotations at first, but cache them to disk
3838 anyway. Bugfix on 0.2.0.8-alpha. Found by piebeer.
3839 - When you're using bridges and your network goes away and your
3840 bridges get marked as down, recover when you attempt a new socks
3841 connection (if the network is back), rather than waiting up to an
3842 hour to try fetching new descriptors for your bridges. Bugfix on
3843 0.2.0.3-alpha; fixes bug 1981.
3846 - Move to the November 2010 Maxmind GeoLite country db (rather
3847 than the June 2009 ip-to-country GeoIP db) for our statistics that
3848 count how many users relays are seeing from each country. Now we'll
3849 have more accurate data, especially for many African countries.
3851 o New directory authorities:
3852 - Set up maatuska (run by Linus Nordberg) as the eighth v3 directory
3856 - Fix an assertion failure that could occur in directory caches or
3857 bridge users when using a very short voting interval on a testing
3858 network. Diagnosed by Robert Hogan. Fixes bug 1141; bugfix on
3860 - Enforce multiplicity rules when parsing annotations. Bugfix on
3861 0.2.0.8-alpha. Found by piebeer.
3862 - Allow handshaking OR connections to take a full KeepalivePeriod
3863 seconds to handshake. Previously, we would close them after
3864 IDLE_OR_CONN_TIMEOUT (180) seconds, the same timeout as if they
3865 were open. Bugfix on 0.2.1.26; fixes bug 1840. Thanks to mingw-san
3867 - When building with --enable-gcc-warnings on OpenBSD, disable
3868 warnings in system headers. This makes --enable-gcc-warnings
3869 pass on OpenBSD 4.8.
3872 - Exit nodes didn't recognize EHOSTUNREACH as a plausible error code,
3873 and so sent back END_STREAM_REASON_MISC. Clients now recognize a new
3874 stream ending reason for this case: END_STREAM_REASON_NOROUTE.
3875 Servers can start sending this code when enough clients recognize
3876 it. Bugfix on 0.1.0.1-rc; fixes part of bug 1793.
3877 - Build correctly on mingw with more recent versions of OpenSSL 0.9.8.
3878 Patch from mingw-san.
3881 - Remove the old debian/ directory from the main Tor distribution.
3882 The official Tor-for-debian git repository lives at the URL
3883 https://git.torproject.org/debian/tor.git
3884 - Stop shipping the old doc/website/ directory in the tarball. We
3885 changed the website format in late 2010, and what we shipped in
3886 0.2.1.26 really wasn't that useful anyway.
3889 Changes in version 0.2.2.19-alpha - 2010-11-22
3890 Yet another OpenSSL security patch broke its compatibility with Tor:
3891 Tor 0.2.2.19-alpha makes relays work with OpenSSL 0.9.8p and 1.0.0.b.
3894 - Resolve an incompatibility with OpenSSL 0.9.8p and OpenSSL 1.0.0b:
3895 No longer set the tlsext_host_name extension on server SSL objects;
3896 but continue to set it on client SSL objects. Our goal in setting
3897 it was to imitate a browser, not a vhosting server. Fixes bug 2204;
3898 bugfix on 0.2.1.1-alpha.
3901 - Try harder not to exceed the maximum length of 50 KB when writing
3902 statistics to extra-info descriptors. This bug was triggered by very
3903 fast relays reporting exit-port, entry, and dirreq statistics.
3904 Reported by Olaf Selke. Bugfix on 0.2.2.1-alpha. Fixes bug 2183.
3905 - Publish a router descriptor even if generating an extra-info
3906 descriptor fails. Previously we would not publish a router
3907 descriptor without an extra-info descriptor; this can cause fast
3908 exit relays collecting exit-port statistics to drop from the
3909 consensus. Bugfix on 0.1.2.9-rc; fixes bug 2195.
3912 Changes in version 0.2.2.18-alpha - 2010-11-16
3913 Tor 0.2.2.18-alpha fixes several crash bugs that have been nagging
3914 us lately, makes unpublished bridge relays able to detect their IP
3915 address, and fixes a wide variety of other bugs to get us much closer
3916 to a stable release.
3919 - Do even more to reject (and not just ignore) annotations on
3920 router descriptors received anywhere but from the cache. Previously
3921 we would ignore such annotations at first, but cache them to disk
3922 anyway. Bugfix on 0.2.0.8-alpha. Found by piebeer.
3923 - Do not log messages to the controller while shrinking buffer
3924 freelists. Doing so would sometimes make the controller connection
3925 try to allocate a buffer chunk, which would mess up the internals
3926 of the freelist and cause an assertion failure. Fixes bug 1125;
3927 fixed by Robert Ransom. Bugfix on 0.2.0.16-alpha.
3928 - Learn our external IP address when we're a relay or bridge, even if
3929 we set PublishServerDescriptor to 0. Bugfix on 0.2.0.3-alpha,
3930 where we introduced bridge relays that don't need to publish to
3931 be useful. Fixes bug 2050.
3932 - Maintain separate TLS contexts and certificates for incoming and
3933 outgoing connections in bridge relays. Previously we would use the
3934 same TLS contexts and certs for incoming and outgoing connections.
3935 Bugfix on 0.2.0.3-alpha; addresses bug 988.
3936 - Maintain separate identity keys for incoming and outgoing TLS
3937 contexts in bridge relays. Previously we would use the same
3938 identity keys for incoming and outgoing TLS contexts. Bugfix on
3939 0.2.0.3-alpha; addresses the other half of bug 988.
3940 - Avoid an assertion failure when we as an authority receive a
3941 duplicate upload of a router descriptor that we already have,
3942 but which we previously considered an obsolete descriptor.
3943 Fixes another case of bug 1776. Bugfix on 0.2.2.16-alpha.
3944 - Avoid a crash bug triggered by looking at a dangling pointer while
3945 setting the network status consensus. Found by Robert Ransom.
3946 Bugfix on 0.2.2.17-alpha. Fixes bug 2097.
3947 - Fix a logic error where servers that _didn't_ act as exits would
3948 try to keep their server lists more aggressively up to date than
3949 exits, when it was supposed to be the other way around. Bugfix
3952 o Minor bugfixes (on Tor 0.2.1.x and earlier):
3953 - When we're trying to guess whether we know our IP address as
3954 a relay, we would log various ways that we failed to guess
3955 our address, but never log that we ended up guessing it
3956 successfully. Now add a log line to help confused and anxious
3957 relay operators. Bugfix on 0.1.2.1-alpha; fixes bug 1534.
3958 - Bring the logic that gathers routerinfos and assesses the
3959 acceptability of circuits into line. This prevents a Tor OP from
3960 getting locked in a cycle of choosing its local OR as an exit for a
3961 path (due to a .exit request) and then rejecting the circuit because
3962 its OR is not listed yet. It also prevents Tor clients from using an
3963 OR running in the same instance as an exit (due to a .exit request)
3964 if the OR does not meet the same requirements expected of an OR
3965 running elsewhere. Fixes bug 1859; bugfix on 0.1.0.1-rc.
3966 - Correctly describe errors that occur when generating a TLS object.
3967 Previously we would attribute them to a failure while generating a
3968 TLS context. Patch by Robert Ransom. Bugfix on 0.1.0.4-rc; fixes
3970 - Enforce multiplicity rules when parsing annotations. Bugfix on
3971 0.2.0.8-alpha. Found by piebeer.
3972 - Fix warnings that newer versions of autoconf produced during
3973 ./autogen.sh. These warnings appear to be harmless in our case,
3974 but they were extremely verbose. Fixes bug 2020.
3976 o Minor bugfixes (on Tor 0.2.2.x):
3977 - Enable protection of small arrays whenever we build with gcc
3978 hardening features, not only when also building with warnings
3979 enabled. Fixes bug 2031; bugfix on 0.2.2.14-alpha. Reported by keb.
3982 - Make hidden services work better in private Tor networks by not
3983 requiring any uptime to join the hidden service descriptor
3984 DHT. Implements ticket 2088.
3985 - Rate-limit the "your application is giving Tor only an IP address"
3986 warning. Addresses bug 2000; bugfix on 0.0.8pre2.
3987 - When AllowSingleHopExits is set, print a warning to explain to the
3988 relay operator why most clients are avoiding her relay.
3989 - Update to the November 1 2010 Maxmind GeoLite Country database.
3991 o Code simplifications and refactoring:
3992 - When we fixed bug 1038 we had to put in a restriction not to send
3993 RELAY_EARLY cells on rend circuits. This was necessary as long
3994 as relays using Tor 0.2.1.3-alpha through 0.2.1.18-alpha were
3995 active. Now remove this obsolete check. Resolves bug 2081.
3996 - Some options used different conventions for uppercasing of acronyms
3997 when comparing manpage and source. Fix those in favor of the
3998 manpage, as it makes sense to capitalize acronyms.
3999 - Remove the torrc.complete file. It hasn't been kept up to date
4000 and users will have better luck checking out the manpage.
4001 - Remove the obsolete "NoPublish" option; it has been flagged
4002 as obsolete and has produced a warning since 0.1.1.18-rc.
4003 - Remove everything related to building the expert bundle for OS X.
4004 It has confused many users, doesn't work right on OS X 10.6,
4005 and is hard to get rid of once installed. Resolves bug 1274.
4008 Changes in version 0.2.2.17-alpha - 2010-09-30
4009 Tor 0.2.2.17-alpha introduces a feature to make it harder for clients
4010 to use one-hop circuits (which can put the exit relays at higher risk,
4011 plus unbalance the network); fixes a big bug in bandwidth accounting
4012 for relays that want to limit their monthly bandwidth use; fixes a
4013 big pile of bugs in how clients tolerate temporary network failure;
4014 and makes our adaptive circuit build timeout feature (which improves
4015 client performance if your network is fast while not breaking things
4016 if your network is slow) better handle bad networks.
4019 - Exit relays now try harder to block exit attempts from unknown
4020 relays, to make it harder for people to use them as one-hop proxies
4021 a la tortunnel. Controlled by the refuseunknownexits consensus
4022 parameter (currently enabled), or you can override it on your
4023 relay with the RefuseUnknownExits torrc option. Resolves bug 1751.
4025 o Major bugfixes (0.2.1.x and earlier):
4026 - Fix a bug in bandwidth accounting that could make us use twice
4027 the intended bandwidth when our interval start changes due to
4028 daylight saving time. Now we tolerate skew in stored vs computed
4029 interval starts: if the start of the period changes by no more than
4030 50% of the period's duration, we remember bytes that we transferred
4031 in the old period. Fixes bug 1511; bugfix on 0.0.9pre5.
4032 - Always search the Windows system directory for system DLLs, and
4033 nowhere else. Bugfix on 0.1.1.23; fixes bug 1954.
4034 - When you're using bridges and your network goes away and your
4035 bridges get marked as down, recover when you attempt a new socks
4036 connection (if the network is back), rather than waiting up to an
4037 hour to try fetching new descriptors for your bridges. Bugfix on
4038 0.2.0.3-alpha; fixes bug 1981.
4040 o Major bugfixes (on 0.2.2.x):
4041 - Fix compilation on Windows. Bugfix on 0.2.2.16-alpha; related to
4043 - Fix a segfault that could happen when operating a bridge relay with
4044 no GeoIP database set. Fixes bug 1964; bugfix on 0.2.2.15-alpha.
4045 - The consensus bandwidth-weights (used by clients to choose fast
4046 relays) entered an unexpected edge case in September where
4047 Exits were much scarcer than Guards, resulting in bad weight
4048 recommendations. Now we compute them using new constraints that
4049 should succeed in all cases. Also alter directory authorities to
4050 not include the bandwidth-weights line if they fail to produce
4051 valid values. Fixes bug 1952; bugfix on 0.2.2.10-alpha.
4052 - When weighting bridges during path selection, we used to trust
4053 the bandwidths they provided in their descriptor, only capping them
4054 at 10MB/s. This turned out to be problematic for two reasons:
4055 Bridges could claim to handle a lot more traffic then they
4056 actually would, thus making more clients pick them and have a
4057 pretty effective DoS attack. The other issue is that new bridges
4058 that might not have a good estimate for their bw capacity yet
4059 would not get used at all unless no other bridges are available
4060 to a client. Fixes bug 1912; bugfix on 0.2.2.7-alpha.
4062 o Major bugfixes (on the circuit build timeout feature, 0.2.2.x):
4063 - Ignore cannibalized circuits when recording circuit build times.
4064 This should provide for a minor performance improvement for hidden
4065 service users using 0.2.2.14-alpha, and should remove two spurious
4066 notice log messages. Bugfix on 0.2.2.14-alpha; fixes bug 1740.
4067 - Simplify the logic that causes us to decide if the network is
4068 unavailable for purposes of recording circuit build times. If we
4069 receive no cells whatsoever for the entire duration of a circuit's
4070 full measured lifetime, the network is probably down. Also ignore
4071 one-hop directory fetching circuit timeouts when calculating our
4072 circuit build times. These changes should hopefully reduce the
4073 cases where we see ridiculous circuit build timeouts for people
4074 with spotty wireless connections. Fixes part of bug 1772; bugfix
4076 - Prevent the circuit build timeout from becoming larger than
4077 the maximum build time we have ever seen. Also, prevent the time
4078 period for measurement circuits from becoming larger than twice that
4079 value. Fixes the other part of bug 1772; bugfix on 0.2.2.2-alpha.
4082 - When we run out of directory information such that we can't build
4083 circuits, but then get enough that we can build circuits, log when
4084 we actually construct a circuit, so the user has a better chance of
4085 knowing what's going on. Fixes bug 1362.
4086 - Be more generous with how much bandwidth we'd use up (with
4087 accounting enabled) before entering "soft hibernation". Previously,
4088 we'd refuse new connections and circuits once we'd used up 95% of
4089 our allotment. Now, we use up 95% of our allotment, AND make sure
4090 that we have no more than 500MB (or 3 hours of expected traffic,
4091 whichever is lower) remaining before we enter soft hibernation.
4092 - If we've configured EntryNodes and our network goes away and/or all
4093 our entrynodes get marked down, optimistically retry them all when
4094 a new socks application request appears. Fixes bug 1882.
4095 - Add some more defensive programming for architectures that can't
4096 handle unaligned integer accesses. We don't know of any actual bugs
4097 right now, but that's the best time to fix them. Fixes bug 1943.
4098 - Support line continuations in the torrc config file. If a line
4099 ends with a single backslash character, the newline is ignored, and
4100 the configuration value is treated as continuing on the next line.
4103 o Minor bugfixes (on 0.2.1.x and earlier):
4104 - For bandwidth accounting, calculate our expected bandwidth rate
4105 based on the time during which we were active and not in
4106 soft-hibernation during the last interval. Previously, we were
4107 also considering the time spent in soft-hibernation. If this
4108 was a long time, we would wind up underestimating our bandwidth
4109 by a lot, and skewing our wakeup time towards the start of the
4110 accounting interval. Fixes bug 1789. Bugfix on 0.0.9pre5.
4112 o Minor bugfixes (on 0.2.2.x):
4113 - Resume generating CIRC FAILED REASON=TIMEOUT control port messages,
4114 which were disabled by the circuit build timeout changes in
4115 0.2.2.14-alpha. Bugfix on 0.2.2.14-alpha; fixes bug 1739.
4116 - Make sure we don't warn about missing bandwidth weights when
4117 choosing bridges or other relays not in the consensus. Bugfix on
4118 0.2.2.10-alpha; fixes bug 1805.
4119 - In our logs, do not double-report signatures from unrecognized
4120 authorities both as "from unknown authority" and "not
4121 present". Fixes bug 1956, bugfix on 0.2.2.16-alpha.
4124 Changes in version 0.2.2.16-alpha - 2010-09-17
4125 Tor 0.2.2.16-alpha fixes a variety of old stream fairness bugs (most
4126 evident at exit relays), and also continues to resolve all the little
4127 bugs that have been filling up trac lately.
4129 o Major bugfixes (stream-level fairness):
4130 - When receiving a circuit-level SENDME for a blocked circuit, try
4131 to package cells fairly from all the streams that had previously
4132 been blocked on that circuit. Previously, we had started with the
4133 oldest stream, and allowed each stream to potentially exhaust
4134 the circuit's package window. This gave older streams on any
4135 given circuit priority over newer ones. Fixes bug 1937. Detected
4136 originally by Camilo Viecco. This bug was introduced before the
4137 first Tor release, in svn commit r152: it is the new winner of
4138 the longest-lived bug prize.
4139 - When the exit relay got a circuit-level sendme cell, it started
4140 reading on the exit streams, even if had 500 cells queued in the
4141 circuit queue already, so the circuit queue just grew and grew in
4142 some cases. We fix this by not re-enabling reading on receipt of a
4143 sendme cell when the cell queue is blocked. Fixes bug 1653. Bugfix
4144 on 0.2.0.1-alpha. Detected by Mashael AlSabah. Original patch by
4146 - Newly created streams were allowed to read cells onto circuits,
4147 even if the circuit's cell queue was blocked and waiting to drain.
4148 This created potential unfairness, as older streams would be
4149 blocked, but newer streams would gladly fill the queue completely.
4150 We add code to detect this situation and prevent any stream from
4151 getting more than one free cell. Bugfix on 0.2.0.1-alpha. Partially
4155 - Update to the September 1 2010 Maxmind GeoLite Country database.
4156 - Warn when CookieAuthFileGroupReadable is set but CookieAuthFile is
4157 not. This would lead to a cookie that is still not group readable.
4158 Closes bug 1843. Suggested by katmagic.
4159 - When logging a rate-limited warning, we now mention how many messages
4160 got suppressed since the last warning.
4161 - Add new "perconnbwrate" and "perconnbwburst" consensus params to
4162 do individual connection-level rate limiting of clients. The torrc
4163 config options with the same names trump the consensus params, if
4164 both are present. Replaces the old "bwconnrate" and "bwconnburst"
4165 consensus params which were broken from 0.2.2.7-alpha through
4166 0.2.2.14-alpha. Closes bug 1947.
4167 - When a router changes IP address or port, authorities now launch
4168 a new reachability test for it. Implements ticket 1899.
4169 - Make the formerly ugly "2 unknown, 7 missing key, 0 good, 0 bad,
4170 2 no signature, 4 required" messages about consensus signatures
4171 easier to read, and make sure they get logged at the same severity
4172 as the messages explaining which keys are which. Fixes bug 1290.
4173 - Don't warn when we have a consensus that we can't verify because
4174 of missing certificates, unless those certificates are ones
4175 that we have been trying and failing to download. Fixes bug 1145.
4176 - If you configure your bridge with a known identity fingerprint,
4177 and the bridge authority is unreachable (as it is in at least
4178 one country now), fall back to directly requesting the descriptor
4179 from the bridge. Finishes the feature started in 0.2.0.10-alpha;
4181 - When building with --enable-gcc-warnings on OpenBSD, disable
4182 warnings in system headers. This makes --enable-gcc-warnings
4183 pass on OpenBSD 4.8.
4185 o Minor bugfixes (on 0.2.1.x and earlier):
4186 - Authorities will now attempt to download consensuses if their
4187 own efforts to make a live consensus have failed. This change
4188 means authorities that restart will fetch a valid consensus, and
4189 it means authorities that didn't agree with the current consensus
4190 will still fetch and serve it if it has enough signatures. Bugfix
4191 on 0.2.0.9-alpha; fixes bug 1300.
4192 - Ensure DNS requests launched by "RESOLVE" commands from the
4193 controller respect the __LeaveStreamsUnattached setconf options. The
4194 same goes for requests launched via DNSPort or transparent
4195 proxying. Bugfix on 0.2.0.1-alpha; fixes bug 1525.
4196 - Allow handshaking OR connections to take a full KeepalivePeriod
4197 seconds to handshake. Previously, we would close them after
4198 IDLE_OR_CONN_TIMEOUT (180) seconds, the same timeout as if they
4199 were open. Bugfix on 0.2.1.26; fixes bug 1840. Thanks to mingw-san
4201 - Rate-limit "Failed to hand off onionskin" warnings.
4202 - Never relay a cell for a circuit we have already destroyed.
4203 Between marking a circuit as closeable and finally closing it,
4204 it may have been possible for a few queued cells to get relayed,
4205 even though they would have been immediately dropped by the next
4206 OR in the circuit. Fixes bug 1184; bugfix on 0.2.0.1-alpha.
4207 - Never queue a cell for a circuit that's already been marked
4209 - Never vote for a server as "Running" if we have a descriptor for
4210 it claiming to be hibernating, and that descriptor was published
4211 more recently than our last contact with the server. Bugfix on
4212 0.2.0.3-alpha; fixes bug 911.
4213 - Squash a compile warning on OpenBSD. Reported by Tas; fixes
4216 o Minor bugfixes (on 0.2.2.x):
4217 - Fix a regression introduced in 0.2.2.7-alpha that marked relays
4218 down if a directory fetch fails and you've configured either
4219 bridges or EntryNodes. The intent was to mark the relay as down
4220 _unless_ you're using bridges or EntryNodes, since if you are
4221 then you could quickly run out of entry points.
4222 - Fix the Windows directory-listing code. A bug introduced in
4223 0.2.2.14-alpha could make Windows directory servers forget to load
4224 some of their cached v2 networkstatus files.
4225 - Really allow clients to use relays as bridges. Fixes bug 1776;
4226 bugfix on 0.2.2.15-alpha.
4227 - Demote a warn to info that happens when the CellStatistics option
4228 was just enabled. Bugfix on 0.2.2.15-alpha; fixes bug 1921.
4229 Reported by Moritz Bartl.
4230 - On Windows, build correctly either with or without Unicode support.
4231 This is necessary so that Tor can support fringe platforms like
4232 Windows 98 (which has no Unicode), or Windows CE (which has no
4233 non-Unicode). Bugfix on 0.2.2.14-alpha; fixes bug 1797.
4236 - Add a unit test for cross-platform directory-listing code.
4239 Changes in version 0.2.2.15-alpha - 2010-08-18
4240 Tor 0.2.2.15-alpha fixes a big bug in hidden service availability,
4241 fixes a variety of other bugs that were preventing performance
4242 experiments from moving forward, fixes several bothersome memory leaks,
4243 and generally closes a lot of smaller bugs that have been filling up
4247 - Stop assigning the HSDir flag to relays that disable their
4248 DirPort (and thus will refuse to answer directory requests). This
4249 fix should dramatically improve the reachability of hidden services:
4250 hidden services and hidden service clients pick six HSDir relays
4251 to store and retrieve the hidden service descriptor, and currently
4252 about half of the HSDir relays will refuse to work. Bugfix on
4253 0.2.0.10-alpha; fixes part of bug 1693.
4254 - The PerConnBWRate and Burst config options, along with the
4255 bwconnrate and bwconnburst consensus params, initialized each conn's
4256 token bucket values only when the connection is established. Now we
4257 update them if the config options change, and update them every time
4258 we get a new consensus. Otherwise we can encounter an ugly edge
4259 case where we initialize an OR conn to client-level bandwidth,
4260 but then later the relay joins the consensus and we leave it
4261 throttled. Bugfix on 0.2.2.7-alpha; fixes bug 1830.
4262 - Fix a regression that caused Tor to rebind its ports if it receives
4263 SIGHUP while hibernating. Bugfix in 0.1.1.6-alpha; closes bug 919.
4266 - Lower the maximum weighted-fractional-uptime cutoff to 98%. This
4267 should give us approximately 40-50% more Guard-flagged nodes,
4268 improving the anonymity the Tor network can provide and also
4269 decreasing the dropoff in throughput that relays experience when
4270 they first get the Guard flag.
4271 - Allow enabling or disabling the *Statistics config options while
4275 - Update to the August 1 2010 Maxmind GeoLite Country database.
4276 - Have the controller interface give a more useful message than
4277 "Internal Error" in response to failed GETINFO requests.
4278 - Warn when the same option is provided more than once in a torrc
4279 file, on the command line, or in a single SETCONF statement, and
4280 the option is one that only accepts a single line. Closes bug 1384.
4281 - Build correctly on mingw with more recent versions of OpenSSL 0.9.8.
4282 Patch from mingw-san.
4283 - Add support for the country code "{??}" in torrc options like
4284 ExcludeNodes, to indicate all routers of unknown country. Closes
4286 - Relays report the number of bytes spent on answering directory
4287 requests in extra-info descriptors similar to {read,write}-history.
4288 Implements enhancement 1790.
4290 o Minor bugfixes (on 0.2.1.x and earlier):
4291 - Complain if PublishServerDescriptor is given multiple arguments that
4292 include 0 or 1. This configuration will be rejected in the future.
4293 Bugfix on 0.2.0.1-alpha; closes bug 1107.
4294 - Disallow BridgeRelay 1 and ORPort 0 at once in the configuration.
4295 Bugfix on 0.2.0.13-alpha; closes bug 928.
4296 - Change "Application request when we're believed to be offline."
4297 notice to "Application request when we haven't used client
4298 functionality lately.", to clarify that it's not an error. Bugfix
4299 on 0.0.9.3; fixes bug 1222.
4300 - Fix a bug in the controller interface where "GETINFO ns/asdaskljkl"
4301 would return "551 Internal error" rather than "552 Unrecognized key
4302 ns/asdaskljkl". Bugfix on 0.1.2.3-alpha.
4303 - Users can't configure a regular relay to be their bridge. It didn't
4304 work because when Tor fetched the bridge descriptor, it found
4305 that it already had it, and didn't realize that the purpose of the
4306 descriptor had changed. Now we replace routers with a purpose other
4307 than bridge with bridge descriptors when fetching them. Bugfix on
4308 0.1.1.9-alpha. Bug 1776 not yet fixed because now we immediately
4309 refetch the descriptor with router purpose 'general', disabling
4311 - Fix a rare bug in rend_fn unit tests: we would fail a test when
4312 a randomly generated port is 0. Diagnosed by Matt Edman. Bugfix
4313 on 0.2.0.10-alpha; fixes bug 1808.
4314 - Exit nodes didn't recognize EHOSTUNREACH as a plausible error code,
4315 and so sent back END_STREAM_REASON_MISC. Clients now recognize a new
4316 stream ending reason for this case: END_STREAM_REASON_NOROUTE.
4317 Servers can start sending this code when enough clients recognize
4318 it. Also update the spec to reflect this new reason. Bugfix on
4319 0.1.0.1-rc; fixes part of bug 1793.
4320 - Delay geoip stats collection by bridges for 6 hours, not 2 hours,
4321 when we switch from being a public relay to a bridge. Otherwise
4322 there will still be clients that see the relay in their consensus,
4323 and the stats will end up wrong. Bugfix on 0.2.1.15-rc; fixes bug
4325 - Instead of giving an assertion failure on an internal mismatch
4326 on estimated freelist size, just log a BUG warning and try later.
4327 Mitigates but does not fix bug 1125.
4328 - Fix an assertion failure that could occur in caches or bridge users
4329 when using a very short voting interval on a testing network.
4330 Diagnosed by Robert Hogan. Fixes bug 1141; bugfix on 0.2.0.8-alpha.
4332 o Minor bugfixes (on 0.2.2.x):
4333 - Alter directory authorities to always consider Exit-flagged nodes
4334 as potential Guard nodes in their votes. The actual decision to
4335 use Exits as Guards is done in the consensus bandwidth weights.
4336 Fixes bug 1294; bugfix on 0.2.2.10-alpha.
4337 - When the controller is reporting the purpose of circuits that
4338 didn't finish building before the circuit build timeout, it was
4339 printing UNKNOWN_13. Now print EXPIRED. Bugfix on 0.2.2.14-alpha.
4340 - Our libevent version parsing code couldn't handle versions like
4341 1.4.14b-stable and incorrectly warned the user about using an
4342 old and broken version of libevent. Treat 1.4.14b-stable like
4343 1.4.14-stable when parsing the version. Fixes bug 1731; bugfix
4345 - Don't use substitution references like $(VAR:MOD) when
4346 $(asciidoc_files) is empty -- make(1) on NetBSD transforms
4347 '$(:x)' to 'x' rather than the empty string. This bites us in
4348 doc/ when configured with --disable-asciidoc. Bugfix on
4349 0.2.2.9-alpha; fixes bug 1773.
4350 - Remove a spurious hidden service server-side log notice about
4351 "Ancient non-dirty circuits". Bugfix on 0.2.2.14-alpha; fixes
4353 - Fix compilation with --with-dmalloc set. Bugfix on 0.2.2.6-alpha;
4355 - Correctly report written bytes on linked connections. Found while
4356 implementing 1790. Bugfix on 0.2.2.4-alpha.
4357 - Fix three memory leaks: one in circuit_build_times_parse_state(),
4358 one in dirvote_add_signatures_to_pending_consensus(), and one every
4359 time we parse a v3 network consensus. Bugfixes on 0.2.2.14-alpha,
4360 0.2.2.6-alpha, and 0.2.2.10-alpha respectively; fixes bug 1831.
4362 o Code simplifications and refactoring:
4363 - Take a first step towards making or.h smaller by splitting out
4364 function definitions for all source files in src/or/. Leave
4365 structures and defines in or.h for now.
4366 - Remove a bunch of unused function declarations as well as a block of
4367 #if 0'd code from the unit tests. Closes bug 1824.
4368 - New unit tests for exit-port history statistics; refactored exit
4369 statistics code to be more easily tested.
4370 - Remove the old debian/ directory from the main Tor distribution.
4371 The official Tor-for-debian git repository lives at the URL
4372 https://git.torproject.org/debian/tor.git
4375 Changes in version 0.2.2.14-alpha - 2010-07-12
4376 Tor 0.2.2.14-alpha greatly improves client-side handling of
4377 circuit build timeouts, which are used to estimate speed and improve
4378 performance. We also move to a much better GeoIP database, port Tor to
4379 Windows CE, introduce new compile flags that improve code security,
4380 add an eighth v3 directory authority, and address a lot of more
4384 - Tor directory authorities no longer crash when started with a
4385 cached-microdesc-consensus file in their data directory. Bugfix
4386 on 0.2.2.6-alpha; fixes bug 1532.
4387 - Treat an unset $HOME like an empty $HOME rather than triggering an
4388 assert. Bugfix on 0.0.8pre1; fixes bug 1522.
4389 - Ignore negative and large circuit build timeout values that can
4390 happen during a suspend or hibernate. These values caused various
4391 asserts to fire. Bugfix on 0.2.2.2-alpha; fixes bug 1245.
4392 - Alter calculation of Pareto distribution parameter 'Xm' for
4393 Circuit Build Timeout learning to use the weighted average of the
4394 top N=3 modes (because we have three entry guards). Considering
4395 multiple modes should improve the timeout calculation in some cases,
4396 and prevent extremely high timeout values. Bugfix on 0.2.2.2-alpha;
4398 - Alter calculation of Pareto distribution parameter 'Alpha' to use a
4399 right censored distribution model. This approach improves over the
4400 synthetic timeout generation approach that was producing insanely
4401 high timeout values. Now we calculate build timeouts using truncated
4402 times. Bugfix on 0.2.2.2-alpha; fixes bugs 1245 and 1335.
4403 - Do not close circuits that are under construction when they reach
4404 the circuit build timeout. Instead, leave them building (but do not
4405 use them) for up until the time corresponding to the 95th percentile
4406 on the Pareto CDF or 60 seconds, whichever is greater. This is done
4407 to provide better data for the new Pareto model. This percentile
4408 can be controlled by the consensus.
4411 - Move to the June 2010 Maxmind GeoLite country db (rather than the
4412 June 2009 ip-to-country GeoIP db) for our statistics that count
4413 how many users relays are seeing from each country. Now we have
4414 more accurate data for many African countries.
4415 - Port Tor to build and run correctly on Windows CE systems, using
4416 the wcecompat library. Contributed by Valerio Lupi.
4417 - New "--enable-gcc-hardening" ./configure flag (off by default)
4418 to turn on gcc compile time hardening options. It ensures
4419 that signed ints have defined behavior (-fwrapv), enables
4420 -D_FORTIFY_SOURCE=2 (requiring -O2), adds stack smashing protection
4421 with canaries (-fstack-protector-all), turns on ASLR protection if
4422 supported by the kernel (-fPIE, -pie), and adds additional security
4423 related warnings. Verified to work on Mac OS X and Debian Lenny.
4424 - New "--enable-linker-hardening" ./configure flag (off by default)
4425 to turn on ELF specific hardening features (relro, now). This does
4426 not work with Mac OS X or any other non-ELF binary format.
4428 o New directory authorities:
4429 - Set up maatuska (run by Linus Nordberg) as the eighth v3 directory
4433 - New config option "WarnUnsafeSocks 0" disables the warning that
4434 occurs whenever Tor receives a socks handshake using a version of
4435 the socks protocol that can only provide an IP address (rather
4436 than a hostname). Setups that do DNS locally over Tor are fine,
4437 and we shouldn't spam the logs in that case.
4438 - Convert the HACKING file to asciidoc, and add a few new sections
4439 to it, explaining how we use Git, how we make changelogs, and
4440 what should go in a patch.
4441 - Add a TIMEOUT_RATE keyword to the BUILDTIMEOUT_SET control port
4442 event, to give information on the current rate of circuit timeouts
4443 over our stored history.
4444 - Add ability to disable circuit build time learning via consensus
4445 parameter and via a LearnCircuitBuildTimeout config option. Also
4446 automatically disable circuit build time calculation if we are
4447 either a AuthoritativeDirectory, or if we fail to write our state
4448 file. Fixes bug 1296.
4449 - More gracefully handle corrupt state files, removing asserts
4450 in favor of saving a backup and resetting state.
4451 - Rename the "log.h" header to "torlog.h" so as to conflict with fewer
4455 - Build correctly on OSX with zlib 1.2.4 and higher with all warnings
4457 - When a2x fails, mention that the user could disable manpages instead
4458 of trying to fix their asciidoc installation.
4459 - Where available, use Libevent 2.0's periodic timers so that our
4460 once-per-second cleanup code gets called even more closely to
4461 once per second than it would otherwise. Fixes bug 943.
4462 - If you run a bridge that listens on multiple IP addresses, and
4463 some user configures a bridge address that uses a different IP
4464 address than your bridge writes in its router descriptor, and the
4465 user doesn't specify an identity key, their Tor would discard the
4466 descriptor because "it isn't one of our configured bridges", and
4467 fail to bootstrap. Now believe the descriptor and bootstrap anyway.
4468 Bugfix on 0.2.0.3-alpha.
4469 - If OpenSSL fails to make a duplicate of a private or public key, log
4470 an error message and try to exit cleanly. May help with debugging
4471 if bug 1209 ever remanifests.
4472 - Save a couple bytes in memory allocation every time we escape
4473 certain characters in a string. Patch from Florian Zumbiehl.
4474 - Make it explicit that we don't cannibalize one-hop circuits. This
4475 happens in the wild, but doesn't turn out to be a problem because
4476 we fortunately don't use those circuits. Many thanks to outofwords
4477 for the initial analysis and to swissknife who confirmed that
4478 two-hop circuits are actually created.
4479 - Make directory mirrors report non-zero dirreq-v[23]-shares again.
4480 Fixes bug 1564; bugfix on 0.2.2.9-alpha.
4481 - Eliminate a case where a circuit build time warning was displayed
4482 after network connectivity resumed. Bugfix on 0.2.2.2-alpha.
4485 Changes in version 0.2.1.26 - 2010-05-02
4486 Tor 0.2.1.26 addresses the recent connection and memory overload
4487 problems we've been seeing on relays, especially relays with their
4488 DirPort open. If your relay has been crashing, or you turned it off
4489 because it used too many resources, give this release a try.
4491 This release also fixes yet another instance of broken OpenSSL libraries
4492 that was causing some relays to drop out of the consensus.
4495 - Teach relays to defend themselves from connection overload. Relays
4496 now close idle circuits early if it looks like they were intended
4497 for directory fetches. Relays are also more aggressive about closing
4498 TLS connections that have no circuits on them. Such circuits are
4499 unlikely to be re-used, and tens of thousands of them were piling
4500 up at the fast relays, causing the relays to run out of sockets
4501 and memory. Bugfix on 0.2.0.22-rc (where clients started tunneling
4502 their directory fetches over TLS).
4503 - Fix SSL renegotiation behavior on OpenSSL versions like on Centos
4504 that claim to be earlier than 0.9.8m, but which have in reality
4505 backported huge swaths of 0.9.8m or 0.9.8n renegotiation
4506 behavior. Possible fix for some cases of bug 1346.
4507 - Directory mirrors were fetching relay descriptors only from v2
4508 directory authorities, rather than v3 authorities like they should.
4509 Only 2 v2 authorities remain (compared to 7 v3 authorities), leading
4510 to a serious bottleneck. Bugfix on 0.2.0.9-alpha. Fixes bug 1324.
4513 - Finally get rid of the deprecated and now harmful notion of "clique
4514 mode", where directory authorities maintain TLS connections to
4518 - In the util/threads test, no longer free the test_mutex before all
4519 worker threads have finished. Bugfix on 0.2.1.6-alpha.
4520 - The master thread could starve the worker threads quite badly on
4521 certain systems, causing them to run only partially in the allowed
4522 window. This resulted in test failures. Now the master thread sleeps
4523 occasionally for a few microseconds while the two worker-threads
4524 compete for the mutex. Bugfix on 0.2.0.1-alpha.
4527 Changes in version 0.2.2.13-alpha - 2010-04-24
4528 Tor 0.2.2.13-alpha addresses the recent connection and memory overload
4529 problems we've been seeing on relays, especially relays with their
4530 DirPort open. If your relay has been crashing, or you turned it off
4531 because it used too many resources, give this release a try.
4534 - Teach relays to defend themselves from connection overload. Relays
4535 now close idle circuits early if it looks like they were intended
4536 for directory fetches. Relays are also more aggressive about closing
4537 TLS connections that have no circuits on them. Such circuits are
4538 unlikely to be re-used, and tens of thousands of them were piling
4539 up at the fast relays, causing the relays to run out of sockets
4540 and memory. Bugfix on 0.2.0.22-rc (where clients started tunneling
4541 their directory fetches over TLS).
4544 - Finally get rid of the deprecated and now harmful notion of "clique
4545 mode", where directory authorities maintain TLS connections to
4547 - Directory authorities now do an immediate reachability check as soon
4548 as they hear about a new relay. This change should slightly reduce
4549 the time between setting up a relay and getting listed as running
4550 in the consensus. It should also improve the time between setting
4551 up a bridge and seeing use by bridge users.
4552 - Directory authorities no longer launch a TLS connection to every
4553 relay as they startup. Now that we have 2k+ descriptors cached,
4554 the resulting network hiccup is becoming a burden. Besides,
4555 authorities already avoid voting about Running for the first half
4556 hour of their uptime.
4559 Changes in version 0.2.2.12-alpha - 2010-04-20
4560 Tor 0.2.2.12-alpha fixes a critical bug in how directory authorities
4561 handle and vote on descriptors. It was causing relays to drop out of
4565 - Many relays have been falling out of the consensus lately because
4566 not enough authorities know about their descriptor for them to get
4567 a majority of votes. When we deprecated the v2 directory protocol,
4568 we got rid of the only way that v3 authorities can hear from each
4569 other about other descriptors. Now authorities examine every v3
4570 vote for new descriptors, and fetch them from that authority. Bugfix
4572 - Fix two typos in tor_vasprintf() that broke the compile on Windows,
4573 and a warning in or.h related to bandwidth_weight_rule_t that
4574 prevented clean compile on OS X. Fixes bug 1363; bugfix on
4576 - Fix a segfault on relays when DirReqStatistics is enabled
4577 and 24 hours pass. Bug found by keb. Fixes bug 1365; bugfix on
4581 - Demote a confusing TLS warning that relay operators might get when
4582 someone tries to talk to their OrPort. It is neither the operator's
4583 fault nor can they do anything about it. Fixes bug 1364; bugfix
4587 Changes in version 0.2.2.11-alpha - 2010-04-15
4588 Tor 0.2.2.11-alpha fixes yet another instance of broken OpenSSL
4589 libraries that was causing some relays to drop out of the consensus.
4592 - Directory mirrors were fetching relay descriptors only from v2
4593 directory authorities, rather than v3 authorities like they should.
4594 Only 2 v2 authorities remain (compared to 7 v3 authorities), leading
4595 to a serious bottleneck. Bugfix on 0.2.0.9-alpha. Fixes bug 1324.
4596 - Fix a parsing error that made every possible value of
4597 CircPriorityHalflifeMsec get treated as "1 msec". Bugfix
4598 on 0.2.2.7-alpha. Rename CircPriorityHalflifeMsec to
4599 CircuitPriorityHalflifeMsec, so authorities can tell newer relays
4600 about the option without breaking older ones.
4601 - Fix SSL renegotiation behavior on OpenSSL versions like on Centos
4602 that claim to be earlier than 0.9.8m, but which have in reality
4603 backported huge swaths of 0.9.8m or 0.9.8n renegotiation
4604 behavior. Possible fix for some cases of bug 1346.
4607 - Experiment with a more aggressive approach to preventing clients
4608 from making one-hop exit streams. Exit relays who want to try it
4609 out can set "RefuseUnknownExits 1" in their torrc, and then look
4610 for "Attempt by %s to open a stream" log messages. Let us know
4612 - Add support for statically linking zlib by specifying
4613 --enable-static-zlib, to go with our support for statically linking
4614 openssl and libevent. Resolves bug 1358.
4617 - Fix a segfault that happens whenever a Tor client that is using
4618 libevent2's bufferevents gets a hup signal. Bugfix on 0.2.2.5-alpha;
4620 - When we cleaned up the contrib/tor-exit-notice.html file, we left
4621 out the first line. Fixes bug 1295.
4622 - When building the manpage from a tarball, we required asciidoc, but
4623 the asciidoc -> roff/html conversion was already done for the
4624 tarball. Make 'make' complain only when we need asciidoc (either
4625 because we're compiling directly from git, or because we altered
4626 the asciidoc manpage in the tarball). Bugfix on 0.2.2.9-alpha.
4627 - When none of the directory authorities vote on any params, Tor
4628 segfaulted when trying to make the consensus from the votes. We
4629 didn't trigger the bug in practice, because authorities do include
4630 params in their votes. Bugfix on 0.2.2.10-alpha; fixes bug 1322.
4633 - In the util/threads test, no longer free the test_mutex before all
4634 worker threads have finished. Bugfix on 0.2.1.6-alpha.
4635 - The master thread could starve the worker threads quite badly on
4636 certain systems, causing them to run only partially in the allowed
4637 window. This resulted in test failures. Now the master thread sleeps
4638 occasionally for a few microseconds while the two worker-threads
4639 compete for the mutex. Bugfix on 0.2.0.1-alpha.
4642 Changes in version 0.2.2.10-alpha - 2010-03-07
4643 Tor 0.2.2.10-alpha fixes a regression introduced in 0.2.2.9-alpha that
4644 could prevent relays from guessing their IP address correctly. It also
4645 starts the groundwork for another client-side performance boost, since
4646 currently we're not making efficient use of relays that have both the
4647 Guard flag and the Exit flag.
4650 - Fix a regression from our patch for bug 1244 that caused relays
4651 to guess their IP address incorrectly if they didn't set Address
4652 in their torrc and/or their address fails to resolve. Bugfix on
4653 0.2.2.9-alpha; fixes bug 1269.
4655 o Major features (performance):
4656 - Directory authorities now compute consensus weightings that instruct
4657 clients how to weight relays flagged as Guard, Exit, Guard+Exit,
4658 and no flag. Clients that use these weightings will distribute
4659 network load more evenly across these different relay types. The
4660 weightings are in the consensus so we can change them globally in
4661 the future. Extra thanks to "outofwords" for finding some nasty
4662 security bugs in the first implementation of this feature.
4664 o Minor features (performance):
4665 - Always perform router selections using weighted relay bandwidth,
4666 even if we don't need a high capacity circuit at the time. Non-fast
4667 circuits now only differ from fast ones in that they can use relays
4668 not marked with the Fast flag. This "feature" could turn out to
4669 be a horrible bug; we should investigate more before it goes into
4673 - Allow disabling building of the manpages. Skipping the manpage
4674 speeds up the build considerably.
4676 o Minor bugfixes (on 0.2.2.x):
4677 - Fix a memleak in the EXTENDCIRCUIT logic. Spotted by coverity.
4678 Bugfix on 0.2.2.9-alpha.
4679 - Disallow values larger than INT32_MAX for PerConnBWRate|Burst
4680 config option. Bugfix on 0.2.2.7-alpha.
4681 - Ship the asciidoc-helper file in the tarball, so that people can
4682 build from source if they want to, and touching the .1.txt files
4683 doesn't break the build. Bugfix on 0.2.2.9-alpha.
4685 o Minor bugfixes (on 0.2.1.x or earlier):
4686 - Fix a dereference-then-NULL-check sequence when publishing
4687 descriptors. Bugfix on 0.2.1.5-alpha. Discovered by ekir; fixes
4689 - Fix another dereference-then-NULL-check sequence. Bugfix on
4690 0.2.1.14-rc. Discovered by ekir; fixes bug 1256.
4691 - Make sure we treat potentially not NUL-terminated strings correctly.
4692 Bugfix on 0.1.1.13-alpha. Discovered by rieo; fixes bug 1257.
4694 o Code simplifications and refactoring:
4695 - Fix some urls in the exit notice file and make it XHTML1.1 strict
4696 compliant. Based on a patch from Christian Kujau.
4697 - Don't use sed in asciidoc-helper anymore.
4698 - Make the build process fail if asciidoc cannot be found and
4699 building with asciidoc isn't disabled.
4702 Changes in version 0.2.2.9-alpha - 2010-02-22
4703 Tor 0.2.2.9-alpha makes Tor work again on the latest OS X, updates the
4704 location of a directory authority, and cleans up a bunch of small bugs.
4706 o Directory authority changes:
4707 - Change IP address for dannenberg (v3 directory authority), and
4708 remove moria2 (obsolete v1, v2 directory authority and v0 hidden
4709 service directory authority) from the list.
4712 - Make Tor work again on the latest OS X: when deciding whether to
4713 use strange flags to turn TLS renegotiation on, detect the OpenSSL
4714 version at run-time, not compile time. We need to do this because
4715 Apple doesn't update its dev-tools headers when it updates its
4716 libraries in a security patch.
4717 - Fix a potential buffer overflow in lookup_last_hid_serv_request()
4718 that could happen on 32-bit platforms with 64-bit time_t. Also fix
4719 a memory leak when requesting a hidden service descriptor we've
4720 requested before. Fixes bug 1242, bugfix on 0.2.0.18-alpha. Found
4722 - Authorities could be tricked into giving out the Exit flag to relays
4723 that didn't allow exiting to any ports. This bug could screw
4724 with load balancing and stats. Bugfix on 0.1.1.6-alpha; fixes bug
4725 1238. Bug discovered by Martin Kowalczyk.
4726 - When freeing a session key, zero it out completely. We only zeroed
4727 the first ptrsize bytes. Bugfix on 0.0.2pre8. Discovered and
4728 patched by ekir. Fixes bug 1254.
4731 - Fix static compilation by listing the openssl libraries in the right
4732 order. Bugfix on Tor 0.2.2.8-alpha; fixes bug 1237.
4733 - Resume handling .exit hostnames in a special way: originally we
4734 stripped the .exit part and used the requested exit relay. In
4735 0.2.2.1-alpha we stopped treating them in any special way, meaning
4736 if you use a .exit address then Tor will pass it on to the exit
4737 relay. Now we reject the .exit stream outright, since that behavior
4738 might be more expected by the user. Found and diagnosed by Scott
4739 Bennett and Downie on or-talk.
4740 - Don't spam the controller with events when we have no file
4741 descriptors available. Bugfix on 0.2.1.5-alpha. (Rate-limiting
4742 for log messages was already solved from bug 748.)
4743 - Avoid a bogus overlapped memcpy in tor_addr_copy(). Reported by
4745 - Make the DNSPort option work with libevent 2.x. Don't alter the
4746 behaviour for libevent 1.x. Fixes bug 1143. Found by SwissTorExit.
4747 - Emit a GUARD DROPPED controller event for a case we missed.
4748 - Make more fields in the controller protocol case-insensitive, since
4749 control-spec.txt said they were.
4750 - Refactor resolve_my_address() to not use gethostbyname() anymore.
4751 Fixes bug 1244; bugfix on 0.0.2pre25. Reported by Mike Mestnik.
4752 - Fix a spec conformance issue: the network-status-version token
4753 must be the first token in a v3 consensus or vote. Discovered by
4754 parakeep. Bugfix on 0.2.0.3-alpha.
4756 o Code simplifications and refactoring:
4757 - Generate our manpage and HTML documentation using Asciidoc. This
4758 change should make it easier to maintain the documentation, and
4760 - Remove the --enable-iphone option. According to reports from Marco
4761 Bonetti, Tor builds fine without any special tweaking on recent
4762 iPhone SDK versions.
4763 - Removed some unnecessary files from the source distribution. The
4764 AUTHORS file has now been merged into the people page on the
4765 website. The roadmaps and design doc can now be found in the
4766 projects directory in svn.
4767 - Enabled various circuit build timeout constants to be controlled
4768 by consensus parameters. Also set better defaults for these
4769 parameters based on experimentation on broadband and simulated
4773 - The 'EXTENDCIRCUIT' control port command can now be used with
4774 a circ id of 0 and no path. This feature will cause Tor to build
4775 a new 'fast' general purpose circuit using its own path selection
4777 - Added a BUILDTIMEOUT_SET controller event to describe changes
4778 to the circuit build timeout.
4779 - Future-proof the controller protocol a bit by ignoring keyword
4780 arguments we do not recognize.
4781 - Expand homedirs passed to tor-checkkey. This should silence a
4782 coverity complaint about passing a user-supplied string into
4783 open() without checking it.
4786 Changes in version 0.2.1.25 - 2010-03-16
4787 Tor 0.2.1.25 fixes a regression introduced in 0.2.1.23 that could
4788 prevent relays from guessing their IP address correctly. It also fixes
4789 several minor potential security bugs.
4792 - Fix a regression from our patch for bug 1244 that caused relays
4793 to guess their IP address incorrectly if they didn't set Address
4794 in their torrc and/or their address fails to resolve. Bugfix on
4795 0.2.1.23; fixes bug 1269.
4796 - When freeing a session key, zero it out completely. We only zeroed
4797 the first ptrsize bytes. Bugfix on 0.0.2pre8. Discovered and
4798 patched by ekir. Fixes bug 1254.
4801 - Fix a dereference-then-NULL-check sequence when publishing
4802 descriptors. Bugfix on 0.2.1.5-alpha. Discovered by ekir; fixes
4804 - Fix another dereference-then-NULL-check sequence. Bugfix on
4805 0.2.1.14-rc. Discovered by ekir; fixes bug 1256.
4806 - Make sure we treat potentially not NUL-terminated strings correctly.
4807 Bugfix on 0.1.1.13-alpha. Discovered by rieo; fixes bug 1257.
4811 Changes in version 0.2.1.24 - 2010-02-21
4812 Tor 0.2.1.24 makes Tor work again on the latest OS X -- this time
4816 - Work correctly out-of-the-box with even more vendor-patched versions
4817 of OpenSSL. In particular, make it so Debian and OS X don't need
4818 customized patches to run/build.
4821 Changes in version 0.2.1.23 - 2010-02-13
4822 Tor 0.2.1.23 fixes a huge client-side performance bug, makes Tor work
4823 again on the latest OS X, and updates the location of a directory
4826 o Major bugfixes (performance):
4827 - We were selecting our guards uniformly at random, and then weighting
4828 which of our guards we'd use uniformly at random. This imbalance
4829 meant that Tor clients were severely limited on throughput (and
4830 probably latency too) by the first hop in their circuit. Now we
4831 select guards weighted by currently advertised bandwidth. We also
4832 automatically discard guards picked using the old algorithm. Fixes
4833 bug 1217; bugfix on 0.2.1.3-alpha. Found by Mike Perry.
4836 - Make Tor work again on the latest OS X: when deciding whether to
4837 use strange flags to turn TLS renegotiation on, detect the OpenSSL
4838 version at run-time, not compile time. We need to do this because
4839 Apple doesn't update its dev-tools headers when it updates its
4840 libraries in a security patch.
4841 - Fix a potential buffer overflow in lookup_last_hid_serv_request()
4842 that could happen on 32-bit platforms with 64-bit time_t. Also fix
4843 a memory leak when requesting a hidden service descriptor we've
4844 requested before. Fixes bug 1242, bugfix on 0.2.0.18-alpha. Found
4847 o Directory authority changes:
4848 - Change IP address for dannenberg (v3 directory authority), and
4849 remove moria2 (obsolete v1, v2 directory authority and v0 hidden
4850 service directory authority) from the list.
4853 - Refactor resolve_my_address() to not use gethostbyname() anymore.
4854 Fixes bug 1244; bugfix on 0.0.2pre25. Reported by Mike Mestnik.
4857 - Avoid a mad rush at the beginning of each month when each client
4858 rotates half of its guards. Instead we spread the rotation out
4859 throughout the month, but we still avoid leaving a precise timestamp
4860 in the state file about when we first picked the guard. Improves
4861 over the behavior introduced in 0.1.2.17.
4864 Changes in version 0.2.2.8-alpha - 2010-01-26
4865 Tor 0.2.2.8-alpha fixes a crash bug in 0.2.2.7-alpha that has been
4866 causing bridge relays to disappear. If you're running a bridge,
4870 - Fix a memory corruption bug on bridges that occured during the
4871 inclusion of stats data in extra-info descriptors. Also fix the
4872 interface for geoip_get_bridge_stats* to prevent similar bugs in
4873 the future. Diagnosis by Tas, patch by Karsten and Sebastian.
4874 Fixes bug 1208; bugfix on 0.2.2.7-alpha.
4877 - Ignore OutboundBindAddress when connecting to localhost.
4878 Connections to localhost need to come _from_ localhost, or else
4879 local servers (like DNS and outgoing HTTP/SOCKS proxies) will often
4883 Changes in version 0.2.2.7-alpha - 2010-01-19
4884 Tor 0.2.2.7-alpha fixes a huge client-side performance bug, as well
4885 as laying the groundwork for further relay-side performance fixes. It
4886 also starts cleaning up client behavior with respect to the EntryNodes,
4887 ExitNodes, and StrictNodes config options.
4889 This release also rotates two directory authority keys, due to a
4890 security breach of some of the Torproject servers.
4892 o Directory authority changes:
4893 - Rotate keys (both v3 identity and relay identity) for moria1
4896 o Major features (performance):
4897 - We were selecting our guards uniformly at random, and then weighting
4898 which of our guards we'd use uniformly at random. This imbalance
4899 meant that Tor clients were severely limited on throughput (and
4900 probably latency too) by the first hop in their circuit. Now we
4901 select guards weighted by currently advertised bandwidth. We also
4902 automatically discard guards picked using the old algorithm. Fixes
4903 bug 1217; bugfix on 0.2.1.3-alpha. Found by Mike Perry.
4904 - When choosing which cells to relay first, relays can now favor
4905 circuits that have been quiet recently, to provide lower latency
4906 for low-volume circuits. By default, relays enable or disable this
4907 feature based on a setting in the consensus. You can override
4908 this default by using the new "CircuitPriorityHalflife" config
4909 option. Design and code by Ian Goldberg, Can Tang, and Chris
4911 - Add separate per-conn write limiting to go with the per-conn read
4912 limiting. We added a global write limit in Tor 0.1.2.5-alpha,
4913 but never per-conn write limits.
4914 - New consensus params "bwconnrate" and "bwconnburst" to let us
4915 rate-limit client connections as they enter the network. It's
4916 controlled in the consensus so we can turn it on and off for
4917 experiments. It's starting out off. Based on proposal 163.
4919 o Major features (relay selection options):
4920 - Switch to a StrictNodes config option, rather than the previous
4921 "StrictEntryNodes" / "StrictExitNodes" separation that was missing a
4922 "StrictExcludeNodes" option.
4923 - If EntryNodes, ExitNodes, ExcludeNodes, or ExcludeExitNodes
4924 change during a config reload, mark and discard all our origin
4925 circuits. This fix should address edge cases where we change the
4926 config options and but then choose a circuit that we created before
4928 - If EntryNodes or ExitNodes are set, be more willing to use an
4929 unsuitable (e.g. slow or unstable) circuit. The user asked for it,
4931 - Make EntryNodes config option much more aggressive even when
4932 StrictNodes is not set. Before it would prepend your requested
4933 entrynodes to your list of guard nodes, but feel free to use others
4934 after that. Now it chooses only from your EntryNodes if any of
4935 those are available, and only falls back to others if a) they're
4936 all down and b) StrictNodes is not set.
4937 - Now we refresh your entry guards from EntryNodes at each consensus
4938 fetch -- rather than just at startup and then they slowly rot as
4939 the network changes.
4942 - Stop bridge directory authorities from answering dbg-stability.txt
4943 directory queries, which would let people fetch a list of all
4944 bridge identities they track. Bugfix on 0.2.1.6-alpha.
4947 - Log a notice when we get a new control connection. Now it's easier
4948 for security-conscious users to recognize when a local application
4949 is knocking on their controller door. Suggested by bug 1196.
4950 - New config option "CircuitStreamTimeout" to override our internal
4951 timeout schedule for how many seconds until we detach a stream from
4952 a circuit and try a new circuit. If your network is particularly
4953 slow, you might want to set this to a number like 60.
4954 - New controller command "getinfo config-text". It returns the
4955 contents that Tor would write if you send it a SAVECONF command,
4956 so the controller can write the file to disk itself.
4957 - New options for SafeLogging to allow scrubbing only log messages
4958 generated while acting as a relay.
4959 - Ship the bridges spec file in the tarball too.
4960 - Avoid a mad rush at the beginning of each month when each client
4961 rotates half of its guards. Instead we spread the rotation out
4962 throughout the month, but we still avoid leaving a precise timestamp
4963 in the state file about when we first picked the guard. Improves
4964 over the behavior introduced in 0.1.2.17.
4966 o Minor bugfixes (compiling):
4967 - Fix compilation on OS X 10.3, which has a stub mlockall() but
4968 hides it. Bugfix on 0.2.2.6-alpha.
4969 - Fix compilation on Solaris by removing support for the
4970 DisableAllSwap config option. Solaris doesn't have an rlimit for
4971 mlockall, so we cannot use it safely. Fixes bug 1198; bugfix on
4974 o Minor bugfixes (crashes):
4975 - Do not segfault when writing buffer stats when we haven't observed
4976 a single circuit to report about. Found by Fabian Lanze. Bugfix on
4978 - If we're in the pathological case where there's no exit bandwidth
4979 but there is non-exit bandwidth, or no guard bandwidth but there
4980 is non-guard bandwidth, don't crash during path selection. Bugfix
4982 - Fix an impossible-to-actually-trigger buffer overflow in relay
4983 descriptor generation. Bugfix on 0.1.0.15.
4985 o Minor bugfixes (privacy):
4986 - Fix an instance where a Tor directory mirror might accidentally
4987 log the IP address of a misbehaving Tor client. Bugfix on
4989 - Don't list Windows capabilities in relay descriptors. We never made
4990 use of them, and maybe it's a bad idea to publish them. Bugfix
4993 o Minor bugfixes (other):
4994 - Resolve an edge case in path weighting that could make us misweight
4995 our relay selection. Fixes bug 1203; bugfix on 0.0.8rc1.
4996 - Fix statistics on client numbers by country as seen by bridges that
4997 were broken in 0.2.2.1-alpha. Also switch to reporting full 24-hour
4998 intervals instead of variable 12-to-48-hour intervals.
4999 - After we free an internal connection structure, overwrite it
5000 with a different memory value than we use for overwriting a freed
5001 internal circuit structure. Should help with debugging. Suggested
5003 - Update our OpenSSL 0.9.8l fix so that it works with OpenSSL 0.9.8m
5007 - Remove the HSAuthorityRecordStats option that version 0 hidden
5008 service authorities could have used to track statistics of overall
5009 hidden service usage.
5012 Changes in version 0.2.1.22 - 2010-01-19
5013 Tor 0.2.1.22 fixes a critical privacy problem in bridge directory
5014 authorities -- it would tell you its whole history of bridge descriptors
5015 if you make the right directory request. This stable update also
5016 rotates two of the seven v3 directory authority keys and locations.
5018 o Directory authority changes:
5019 - Rotate keys (both v3 identity and relay identity) for moria1
5023 - Stop bridge directory authorities from answering dbg-stability.txt
5024 directory queries, which would let people fetch a list of all
5025 bridge identities they track. Bugfix on 0.2.1.6-alpha.
5028 Changes in version 0.2.1.21 - 2009-12-21
5029 Tor 0.2.1.21 fixes an incompatibility with the most recent OpenSSL
5030 library. If you use Tor on Linux / Unix and you're getting SSL
5031 renegotiation errors, upgrading should help. We also recommend an
5032 upgrade if you're an exit relay.
5035 - Work around a security feature in OpenSSL 0.9.8l that prevents our
5036 handshake from working unless we explicitly tell OpenSSL that we
5037 are using SSL renegotiation safely. We are, of course, but OpenSSL
5038 0.9.8l won't work unless we say we are.
5039 - Avoid crashing if the client is trying to upload many bytes and the
5040 circuit gets torn down at the same time, or if the flip side
5041 happens on the exit relay. Bugfix on 0.2.0.1-alpha; fixes bug 1150.
5044 - Do not refuse to learn about authority certs and v2 networkstatus
5045 documents that are older than the latest consensus. This bug might
5046 have degraded client bootstrapping. Bugfix on 0.2.0.10-alpha.
5047 Spotted and fixed by xmux.
5048 - Fix a couple of very-hard-to-trigger memory leaks, and one hard-to-
5049 trigger platform-specific option misparsing case found by Coverity
5051 - Fix a compilation warning on Fedora 12 by removing an impossible-to-
5052 trigger assert. Fixes bug 1173.
5055 Changes in version 0.2.2.6-alpha - 2009-11-19
5056 Tor 0.2.2.6-alpha lays the groundwork for many upcoming features:
5057 support for the new lower-footprint "microdescriptor" directory design,
5058 future-proofing our consensus format against new hash functions or
5059 other changes, and an Android port. It also makes Tor compatible with
5060 the upcoming OpenSSL 0.9.8l release, and fixes a variety of bugs.
5063 - Directory authorities can now create, vote on, and serve multiple
5064 parallel formats of directory data as part of their voting process.
5065 Partially implements Proposal 162: "Publish the consensus in
5067 - Directory authorities can now agree on and publish small summaries
5068 of router information that clients can use in place of regular
5069 server descriptors. This transition will eventually allow clients
5070 to use far less bandwidth for downloading information about the
5071 network. Begins the implementation of Proposal 158: "Clients
5072 download consensus + microdescriptors".
5073 - The directory voting system is now extensible to use multiple hash
5074 algorithms for signatures and resource selection. Newer formats
5075 are signed with SHA256, with a possibility for moving to a better
5076 hash algorithm in the future.
5077 - New DisableAllSwap option. If set to 1, Tor will attempt to lock all
5078 current and future memory pages via mlockall(). On supported
5079 platforms (modern Linux and probably BSD but not Windows or OS X),
5080 this should effectively disable any and all attempts to page out
5081 memory. This option requires that you start your Tor as root --
5082 if you use DisableAllSwap, please consider using the User option
5083 to properly reduce the privileges of your Tor.
5084 - Numerous changes, bugfixes, and workarounds from Nathan Freitas
5085 to help Tor build correctly for Android phones.
5088 - Work around a security feature in OpenSSL 0.9.8l that prevents our
5089 handshake from working unless we explicitly tell OpenSSL that we
5090 are using SSL renegotiation safely. We are, but OpenSSL 0.9.8l
5091 won't work unless we say we are.
5094 - Fix a crash bug when trying to initialize the evdns module in
5095 Libevent 2. Bugfix on 0.2.1.16-rc.
5096 - Stop logging at severity 'warn' when some other Tor client tries
5097 to establish a circuit with us using weak DH keys. It's a protocol
5098 violation, but that doesn't mean ordinary users need to hear about
5099 it. Fixes the bug part of bug 1114. Bugfix on 0.1.0.13.
5100 - Do not refuse to learn about authority certs and v2 networkstatus
5101 documents that are older than the latest consensus. This bug might
5102 have degraded client bootstrapping. Bugfix on 0.2.0.10-alpha.
5103 Spotted and fixed by xmux.
5104 - Fix numerous small code-flaws found by Coverity Scan Rung 3.
5105 - If all authorities restart at once right before a consensus vote,
5106 nobody will vote about "Running", and clients will get a consensus
5107 with no usable relays. Instead, authorities refuse to build a
5108 consensus if this happens. Bugfix on 0.2.0.10-alpha; fixes bug 1066.
5109 - If your relay can't keep up with the number of incoming create
5110 cells, it would log one warning per failure into your logs. Limit
5111 warnings to 1 per minute. Bugfix on 0.0.2pre10; fixes bug 1042.
5112 - Bridges now use "reject *:*" as their default exit policy. Bugfix
5113 on 0.2.0.3-alpha; fixes bug 1113.
5114 - Fix a memory leak on directory authorities during voting that was
5115 introduced in 0.2.2.1-alpha. Found via valgrind.
5118 Changes in version 0.2.1.20 - 2009-10-15
5119 Tor 0.2.1.20 fixes a crash bug when you're accessing many hidden
5120 services at once, prepares for more performance improvements, and
5121 fixes a bunch of smaller bugs.
5123 The Windows and OS X bundles also include a more recent Vidalia,
5124 and switch from Privoxy to Polipo.
5126 The OS X installers are now drag and drop. It's best to un-install
5127 Tor/Vidalia and then install this new bundle, rather than upgrade. If
5128 you want to upgrade, you'll need to update the paths for Tor and Polipo
5129 in the Vidalia Settings window.
5132 - Send circuit or stream sendme cells when our window has decreased
5133 by 100 cells, not when it has decreased by 101 cells. Bug uncovered
5134 by Karsten when testing the "reduce circuit window" performance
5135 patch. Bugfix on the 54th commit on Tor -- from July 2002,
5136 before the release of Tor 0.0.0. This is the new winner of the
5138 - Fix a remotely triggerable memory leak when a consensus document
5139 contains more than one signature from the same voter. Bugfix on
5141 - Avoid segfault in rare cases when finishing an introduction circuit
5142 as a client and finding out that we don't have an introduction key
5143 for it. Fixes bug 1073. Reported by Aaron Swartz.
5146 - Tor now reads the "circwindow" parameter out of the consensus,
5147 and uses that value for its circuit package window rather than the
5148 default of 1000 cells. Begins the implementation of proposal 168.
5150 o New directory authorities:
5151 - Set up urras (run by Jacob Appelbaum) as the seventh v3 directory
5153 - Move moria1 and tonga to alternate IP addresses.
5156 - Fix a signed/unsigned compile warning in 0.2.1.19.
5157 - Fix possible segmentation fault on directory authorities. Bugfix on
5159 - Fix an extremely rare infinite recursion bug that could occur if
5160 we tried to log a message after shutting down the log subsystem.
5161 Found by Matt Edman. Bugfix on 0.2.0.16-alpha.
5162 - Fix an obscure bug where hidden services on 64-bit big-endian
5163 systems might mis-read the timestamp in v3 introduce cells, and
5164 refuse to connect back to the client. Discovered by "rotor".
5165 Bugfix on 0.2.1.6-alpha.
5166 - We were triggering a CLOCK_SKEW controller status event whenever
5167 we connect via the v2 connection protocol to any relay that has
5168 a wrong clock. Instead, we should only inform the controller when
5169 it's a trusted authority that claims our clock is wrong. Bugfix
5170 on 0.2.0.20-rc; starts to fix bug 1074. Reported by SwissTorExit.
5171 - We were telling the controller about CHECKING_REACHABILITY and
5172 REACHABILITY_FAILED status events whenever we launch a testing
5173 circuit or notice that one has failed. Instead, only tell the
5174 controller when we want to inform the user of overall success or
5175 overall failure. Bugfix on 0.1.2.6-alpha. Fixes bug 1075. Reported
5177 - Don't warn when we're using a circuit that ends with a node
5178 excluded in ExcludeExitNodes, but the circuit is not used to access
5179 the outside world. This should help fix bug 1090. Bugfix on
5181 - Work around a small memory leak in some versions of OpenSSL that
5182 stopped the memory used by the hostname TLS extension from being
5186 - Add a "getinfo status/accepted-server-descriptor" controller
5187 command, which is the recommended way for controllers to learn
5188 whether our server descriptor has been successfully received by at
5189 least on directory authority. Un-recommend good-server-descriptor
5190 getinfo and status events until we have a better design for them.
5193 Changes in version 0.2.2.5-alpha - 2009-10-11
5194 Tor 0.2.2.5-alpha fixes a few compile problems in 0.2.2.4-alpha.
5197 - Make the tarball compile again. Oops. Bugfix on 0.2.2.4-alpha.
5199 o Directory authorities:
5200 - Temporarily (just for this release) move dizum to an alternate
5204 Changes in version 0.2.2.4-alpha - 2009-10-10
5205 Tor 0.2.2.4-alpha fixes more crash bugs in 0.2.2.2-alpha. It also
5206 introduces a new unit test framework, shifts directry authority
5207 addresses around to reduce the impact from recent blocking events,
5208 and fixes a few smaller bugs.
5211 - Fix several more asserts in the circuit_build_times code, for
5212 example one that causes Tor to fail to start once we have
5213 accumulated 5000 build times in the state file. Bugfixes on
5214 0.2.2.2-alpha; fixes bug 1108.
5216 o New directory authorities:
5217 - Move moria1 and Tonga to alternate IP addresses.
5220 - Log SSL state transitions at debug level during handshake, and
5221 include SSL states in error messages. This may help debug future
5222 SSL handshake issues.
5223 - Add a new "Handshake" log domain for activities that happen
5224 during the TLS handshake.
5225 - Revert to the "June 3 2009" ip-to-country file. The September one
5226 seems to have removed most US IP addresses.
5227 - Directory authorities now reject Tor relays with versions less than
5228 0.1.2.14. This step cuts out four relays from the current network,
5229 none of which are very big.
5232 - Fix a couple of smaller issues with gathering statistics. Bugfixes
5234 - Fix two memory leaks in the error case of
5235 circuit_build_times_parse_state(). Bugfix on 0.2.2.2-alpha.
5236 - Don't count one-hop circuits when we're estimating how long it
5237 takes circuits to build on average. Otherwise we'll set our circuit
5238 build timeout lower than we should. Bugfix on 0.2.2.2-alpha.
5239 - Directory authorities no longer change their opinion of, or vote on,
5240 whether a router is Running, unless they have themselves been
5241 online long enough to have some idea. Bugfix on 0.2.0.6-alpha.
5244 o Code simplifications and refactoring:
5245 - Revise our unit tests to use the "tinytest" framework, so we
5246 can run tests in their own processes, have smarter setup/teardown
5247 code, and so on. The unit test code has moved to its own
5248 subdirectory, and has been split into multiple modules.
5251 Changes in version 0.2.2.3-alpha - 2009-09-23
5252 Tor 0.2.2.3-alpha fixes a few crash bugs in 0.2.2.2-alpha.
5255 - Fix an overzealous assert in our new circuit build timeout code.
5256 Bugfix on 0.2.2.2-alpha; fixes bug 1103.
5259 - If the networkstatus consensus tells us that we should use a
5260 negative circuit package window, ignore it. Otherwise we'll
5261 believe it and then trigger an assert. Bugfix on 0.2.2.2-alpha.
5264 Changes in version 0.2.2.2-alpha - 2009-09-21
5265 Tor 0.2.2.2-alpha introduces our latest performance improvement for
5266 clients: Tor tracks the average time it takes to build a circuit, and
5267 avoids using circuits that take too long to build. For fast connections,
5268 this feature can cut your expected latency in half. For slow or flaky
5269 connections, it could ruin your Tor experience. Let us know if it does!
5272 - Tor now tracks how long it takes to build client-side circuits
5273 over time, and adapts its timeout to local network performance.
5274 Since a circuit that takes a long time to build will also provide
5275 bad performance, we get significant latency improvements by
5276 discarding the slowest 20% of circuits. Specifically, Tor creates
5277 circuits more aggressively than usual until it has enough data
5278 points for a good timeout estimate. Implements proposal 151.
5279 We are especially looking for reports (good and bad) from users with
5280 both EDGE and broadband connections that can move from broadband
5281 to EDGE and find out if the build-time data in the .tor/state gets
5282 reset without loss of Tor usability. You should also see a notice
5283 log message telling you that Tor has reset its timeout.
5284 - Directory authorities can now vote on arbitary integer values as
5285 part of the consensus process. This is designed to help set
5286 network-wide parameters. Implements proposal 167.
5287 - Tor now reads the "circwindow" parameter out of the consensus,
5288 and uses that value for its circuit package window rather than the
5289 default of 1000 cells. Begins the implementation of proposal 168.
5292 - Fix a remotely triggerable memory leak when a consensus document
5293 contains more than one signature from the same voter. Bugfix on
5297 - Fix an extremely rare infinite recursion bug that could occur if
5298 we tried to log a message after shutting down the log subsystem.
5299 Found by Matt Edman. Bugfix on 0.2.0.16-alpha.
5300 - Fix parsing for memory or time units given without a space between
5301 the number and the unit. Bugfix on 0.2.2.1-alpha; fixes bug 1076.
5302 - A networkstatus vote must contain exactly one signature. Spec
5303 conformance issue. Bugfix on 0.2.0.3-alpha.
5304 - Fix an obscure bug where hidden services on 64-bit big-endian
5305 systems might mis-read the timestamp in v3 introduce cells, and
5306 refuse to connect back to the client. Discovered by "rotor".
5307 Bugfix on 0.2.1.6-alpha.
5308 - We were triggering a CLOCK_SKEW controller status event whenever
5309 we connect via the v2 connection protocol to any relay that has
5310 a wrong clock. Instead, we should only inform the controller when
5311 it's a trusted authority that claims our clock is wrong. Bugfix
5312 on 0.2.0.20-rc; starts to fix bug 1074. Reported by SwissTorExit.
5313 - We were telling the controller about CHECKING_REACHABILITY and
5314 REACHABILITY_FAILED status events whenever we launch a testing
5315 circuit or notice that one has failed. Instead, only tell the
5316 controller when we want to inform the user of overall success or
5317 overall failure. Bugfix on 0.1.2.6-alpha. Fixes bug 1075. Reported
5319 - Don't warn when we're using a circuit that ends with a node
5320 excluded in ExcludeExitNodes, but the circuit is not used to access
5321 the outside world. This should help fix bug 1090, but more problems
5322 remain. Bugfix on 0.2.1.6-alpha.
5323 - Work around a small memory leak in some versions of OpenSSL that
5324 stopped the memory used by the hostname TLS extension from being
5326 - Make our 'torify' script more portable; if we have only one of
5327 'torsocks' or 'tsocks' installed, don't complain to the user;
5328 and explain our warning about tsocks better.
5331 - Add a "getinfo status/accepted-server-descriptor" controller
5332 command, which is the recommended way for controllers to learn
5333 whether our server descriptor has been successfully received by at
5334 least on directory authority. Un-recommend good-server-descriptor
5335 getinfo and status events until we have a better design for them.
5336 - Update to the "September 4 2009" ip-to-country file.
5339 Changes in version 0.2.2.1-alpha - 2009-08-26
5340 Tor 0.2.2.1-alpha disables ".exit" address notation by default, allows
5341 Tor clients to bootstrap on networks where only port 80 is reachable,
5342 makes it more straightforward to support hardware crypto accelerators,
5343 and starts the groundwork for gathering stats safely at relays.
5346 - Start the process of disabling ".exit" address notation, since it
5347 can be used for a variety of esoteric application-level attacks
5348 on users. To reenable it, set "AllowDotExit 1" in your torrc. Fix
5351 o New directory authorities:
5352 - Set up urras (run by Jacob Appelbaum) as the seventh v3 directory
5356 - New AccelName and AccelDir options add support for dynamic OpenSSL
5357 hardware crypto acceleration engines.
5358 - Tor now supports tunneling all of its outgoing connections over
5359 a SOCKS proxy, using the SOCKS4Proxy and/or SOCKS5Proxy
5360 configuration options. Code by Christopher Davis.
5363 - Send circuit or stream sendme cells when our window has decreased
5364 by 100 cells, not when it has decreased by 101 cells. Bug uncovered
5365 by Karsten when testing the "reduce circuit window" performance
5366 patch. Bugfix on the 54th commit on Tor -- from July 2002,
5367 before the release of Tor 0.0.0. This is the new winner of the
5370 o New options for gathering stats safely:
5371 - Directory mirrors that set "DirReqStatistics 1" write statistics
5372 about directory requests to disk every 24 hours. As compared to the
5373 --enable-geoip-stats flag in 0.2.1.x, there are a few improvements:
5374 1) stats are written to disk exactly every 24 hours; 2) estimated
5375 shares of v2 and v3 requests are determined as mean values, not at
5376 the end of a measurement period; 3) unresolved requests are listed
5377 with country code '??'; 4) directories also measure download times.
5378 - Exit nodes that set "ExitPortStatistics 1" write statistics on the
5379 number of exit streams and transferred bytes per port to disk every
5381 - Relays that set "CellStatistics 1" write statistics on how long
5382 cells spend in their circuit queues to disk every 24 hours.
5383 - Entry nodes that set "EntryStatistics 1" write statistics on the
5384 rough number and origins of connecting clients to disk every 24
5386 - Relays that write any of the above statistics to disk and set
5387 "ExtraInfoStatistics 1" include the past 24 hours of statistics in
5388 their extra-info documents.
5391 - New --digests command-line switch to output the digests of the
5392 source files Tor was built with.
5393 - The "torify" script now uses torsocks where available.
5394 - The memarea code now uses a sentinel value at the end of each area
5395 to make sure nothing writes beyond the end of an area. This might
5396 help debug some conceivable causes of bug 930.
5397 - Time and memory units in the configuration file can now be set to
5398 fractional units. For example, "2.5 GB" is now a valid value for
5400 - Certain Tor clients (such as those behind check.torproject.org) may
5401 want to fetch the consensus in an extra early manner. To enable this
5402 a user may now set FetchDirInfoExtraEarly to 1. This also depends on
5403 setting FetchDirInfoEarly to 1. Previous behavior will stay the same
5404 as only certain clients who must have this information sooner should
5406 - Instead of adding the svn revision to the Tor version string, report
5407 the git commit (when we're building from a git checkout).
5410 - If any of the v3 certs we download are unparseable, we should
5411 actually notice the failure so we don't retry indefinitely. Bugfix
5412 on 0.2.0.x; reported by "rotator".
5413 - If the cached cert file is unparseable, warn but don't exit.
5414 - Fix possible segmentation fault on directory authorities. Bugfix on
5416 - When Tor fails to parse a descriptor of any kind, dump it to disk.
5417 Might help diagnosing bug 1051.
5419 o Deprecated and removed features:
5420 - The controller no longer accepts the old obsolete "addr-mappings/"
5421 or "unregistered-servers-" GETINFO values.
5422 - Hidden services no longer publish version 0 descriptors, and clients
5423 do not request or use version 0 descriptors. However, the old hidden
5424 service authorities still accept and serve version 0 descriptors
5425 when contacted by older hidden services/clients.
5426 - The EXTENDED_EVENTS and VERBOSE_NAMES controller features are now
5427 always on; using them is necessary for correct forward-compatible
5429 - Remove support for .noconnect style addresses. Nobody was using
5430 them, and they provided another avenue for detecting Tor users
5431 via application-level web tricks.
5433 o Packaging changes:
5434 - Upgrade Vidalia from 0.1.15 to 0.2.3 in the Windows and OS X
5435 installer bundles. See
5436 https://trac.vidalia-project.net/browser/vidalia/tags/vidalia-0.2.3/CHANGELOG
5437 for details of what's new in Vidalia 0.2.3.
5438 - Windows Vidalia Bundle: update Privoxy from 3.0.6 to 3.0.14-beta.
5439 - OS X Vidalia Bundle: move to Polipo 1.0.4 with Tor specific
5440 configuration file, rather than the old Privoxy.
5441 - OS X Vidalia Bundle: Vidalia, Tor, and Polipo are compiled as
5442 x86-only for better compatibility with OS X 10.6, aka Snow Leopard.
5443 - OS X Tor Expert Bundle: Tor is compiled as x86-only for
5444 better compatibility with OS X 10.6, aka Snow Leopard.
5445 - OS X Vidalia Bundle: The multi-package installer is now replaced
5446 by a simple drag and drop to the /Applications folder. This change
5447 occurred with the upgrade to Vidalia 0.2.3.
5450 Changes in version 0.2.1.19 - 2009-07-28
5451 Tor 0.2.1.19 fixes a major bug with accessing and providing hidden
5452 services on Tor 0.2.1.3-alpha through 0.2.1.18.
5455 - Make accessing hidden services on 0.2.1.x work right again.
5456 Bugfix on 0.2.1.3-alpha; workaround for bug 1038. Diagnosis and
5457 part of patch provided by "optimist".
5460 - When a relay/bridge is writing out its identity key fingerprint to
5461 the "fingerprint" file and to its logs, write it without spaces. Now
5462 it will look like the fingerprints in our bridges documentation,
5463 and confuse fewer users.
5466 - Relays no longer publish a new server descriptor if they change
5467 their MaxAdvertisedBandwidth config option but it doesn't end up
5468 changing their advertised bandwidth numbers. Bugfix on 0.2.0.28-rc;
5469 fixes bug 1026. Patch from Sebastian.
5470 - Avoid leaking memory every time we get a create cell but we have
5471 so many already queued that we refuse it. Bugfix on 0.2.0.19-alpha;
5472 fixes bug 1034. Reported by BarkerJr.
5475 Changes in version 0.2.1.18 - 2009-07-24
5476 Tor 0.2.1.18 lays the foundations for performance improvements,
5477 adds status events to help users diagnose bootstrap problems, adds
5478 optional authentication/authorization for hidden services, fixes a
5479 variety of potential anonymity problems, and includes a huge pile of
5480 other features and bug fixes.
5483 - Add LIBS=-lrt to Makefile.am so the Tor RPMs use a static libevent.
5486 Changes in version 0.2.1.17-rc - 2009-07-07
5487 Tor 0.2.1.17-rc marks the fourth -- and hopefully last -- release
5488 candidate for the 0.2.1.x series. It lays the groundwork for further
5489 client performance improvements, and also fixes a big bug with directory
5490 authorities that were causing them to assign Guard and Stable flags
5493 The Windows bundles also finally include the geoip database that we
5494 thought we'd been shipping since 0.2.0.x (oops), and the OS X bundles
5495 should actually install Torbutton rather than giving you a cryptic
5496 failure message (oops).
5499 - Clients now use the bandwidth values in the consensus, rather than
5500 the bandwidth values in each relay descriptor. This approach opens
5501 the door to more accurate bandwidth estimates once the directory
5502 authorities start doing active measurements. Implements more of
5506 - When Tor clients restart after 1-5 days, they discard all their
5507 cached descriptors as too old, but they still use the cached
5508 consensus document. This approach is good for robustness, but
5509 bad for performance: since they don't know any bandwidths, they
5510 end up choosing at random rather than weighting their choice by
5511 speed. Fixed by the above feature of putting bandwidths in the
5512 consensus. Bugfix on 0.2.0.x.
5513 - Directory authorities were neglecting to mark relays down in their
5514 internal histories if the relays fall off the routerlist without
5515 ever being found unreachable. So there were relays in the histories
5516 that haven't been seen for eight months, and are listed as being
5517 up for eight months. This wreaked havoc on the "median wfu"
5518 and "median mtbf" calculations, in turn making Guard and Stable
5519 flags very wrong, hurting network performance. Fixes bugs 696 and
5520 969. Bugfix on 0.2.0.6-alpha.
5523 - Serve the DirPortFrontPage page even when we have been approaching
5524 our quotas recently. Fixes bug 1013; bugfix on 0.2.1.8-alpha.
5525 - The control port would close the connection before flushing long
5526 replies, such as the network consensus, if a QUIT command was issued
5527 before the reply had completed. Now, the control port flushes all
5528 pending replies before closing the connection. Also fixed a spurious
5529 warning when a QUIT command is issued after a malformed or rejected
5530 AUTHENTICATE command, but before the connection was closed. Patch
5531 by Marcus Griep. Bugfix on 0.2.0.x; fixes bugs 1015 and 1016.
5532 - When we can't find an intro key for a v2 hidden service descriptor,
5533 fall back to the v0 hidden service descriptor and log a bug message.
5534 Workaround for bug 1024.
5535 - Fix a log message that did not respect the SafeLogging option.
5539 - If we're a relay and we change our IP address, be more verbose
5540 about the reason that made us change. Should help track down
5541 further bugs for relays on dynamic IP addresses.
5544 Changes in version 0.2.0.35 - 2009-06-24
5546 - Avoid crashing in the presence of certain malformed descriptors.
5547 Found by lark, and by automated fuzzing.
5548 - Fix an edge case where a malicious exit relay could convince a
5549 controller that the client's DNS question resolves to an internal IP
5550 address. Bug found and fixed by "optimist"; bugfix on 0.1.2.8-beta.
5553 - Finally fix the bug where dynamic-IP relays disappear when their
5554 IP address changes: directory mirrors were mistakenly telling
5555 them their old address if they asked via begin_dir, so they
5556 never got an accurate answer about their new address, so they
5557 just vanished after a day. For belt-and-suspenders, relays that
5558 don't set Address in their config now avoid using begin_dir for
5559 all direct connections. Should fix bugs 827, 883, and 900.
5560 - Fix a timing-dependent, allocator-dependent, DNS-related crash bug
5561 that would occur on some exit nodes when DNS failures and timeouts
5562 occurred in certain patterns. Fix for bug 957.
5565 - When starting with a cache over a few days old, do not leak
5566 memory for the obsolete router descriptors in it. Bugfix on
5567 0.2.0.33; fixes bug 672.
5568 - Hidden service clients didn't use a cached service descriptor that
5569 was older than 15 minutes, but wouldn't fetch a new one either,
5570 because there was already one in the cache. Now, fetch a v2
5571 descriptor unless the same descriptor was added to the cache within
5572 the last 15 minutes. Fixes bug 997; reported by Marcus Griep.
5575 Changes in version 0.2.1.16-rc - 2009-06-20
5576 Tor 0.2.1.16-rc speeds up performance for fast exit relays, and fixes
5577 a bunch of minor bugs.
5580 - Fix an edge case where a malicious exit relay could convince a
5581 controller that the client's DNS question resolves to an internal IP
5582 address. Bug found and fixed by "optimist"; bugfix on 0.1.2.8-beta.
5584 o Major performance improvements (on 0.2.0.x):
5585 - Disable and refactor some debugging checks that forced a linear scan
5586 over the whole server-side DNS cache. These accounted for over 50%
5587 of CPU time on a relatively busy exit node's gprof profile. Found
5589 - Disable some debugging checks that appeared in exit node profile
5593 - Update to the "June 3 2009" ip-to-country file.
5594 - Do not have tor-resolve automatically refuse all .onion addresses;
5595 if AutomapHostsOnResolve is set in your torrc, this will work fine.
5597 o Minor bugfixes (on 0.2.0.x):
5598 - Log correct error messages for DNS-related network errors on
5600 - Fix a race condition that could cause crashes or memory corruption
5601 when running as a server with a controller listening for log
5603 - Avoid crashing when we have a policy specified in a DirPolicy or
5604 SocksPolicy or ReachableAddresses option with ports set on it,
5605 and we re-load the policy. May fix bug 996.
5606 - Hidden service clients didn't use a cached service descriptor that
5607 was older than 15 minutes, but wouldn't fetch a new one either,
5608 because there was already one in the cache. Now, fetch a v2
5609 descriptor unless the same descriptor was added to the cache within
5610 the last 15 minutes. Fixes bug 997; reported by Marcus Griep.
5612 o Minor bugfixes (on 0.2.1.x):
5613 - Don't warn users about low port and hibernation mix when they
5614 provide a *ListenAddress directive to fix that. Bugfix on
5616 - When switching back and forth between bridge mode, do not start
5617 gathering GeoIP data until two hours have passed.
5618 - Do not complain that the user has requested an excluded node as
5619 an exit when the node is not really an exit. This could happen
5620 because the circuit was for testing, or an introduction point.
5624 Changes in version 0.2.1.15-rc - 2009-05-25
5625 Tor 0.2.1.15-rc marks the second release candidate for the 0.2.1.x
5626 series. It fixes a major bug on fast exit relays, as well as a variety
5629 o Major bugfixes (on 0.2.0.x):
5630 - Fix a timing-dependent, allocator-dependent, DNS-related crash bug
5631 that would occur on some exit nodes when DNS failures and timeouts
5632 occurred in certain patterns. Fix for bug 957.
5634 o Minor bugfixes (on 0.2.0.x):
5635 - Actually return -1 in the error case for read_bandwidth_usage().
5636 Harmless bug, since we currently don't care about the return value
5637 anywhere. Bugfix on 0.2.0.9-alpha.
5638 - Provide a more useful log message if bug 977 (related to buffer
5639 freelists) ever reappears, and do not crash right away.
5640 - Fix an assertion failure on 64-bit platforms when we allocated
5641 memory right up to the end of a memarea, then realigned the memory
5642 one step beyond the end. Fixes a possible cause of bug 930.
5643 - Protect the count of open sockets with a mutex, so we can't
5644 corrupt it when two threads are closing or opening sockets at once.
5645 Fix for bug 939. Bugfix on 0.2.0.1-alpha.
5646 - Don't allow a bridge to publish its router descriptor to a
5647 non-bridge directory authority. Fixes part of bug 932.
5648 - When we change to or from being a bridge, reset our counts of
5649 client usage by country. Fixes bug 932.
5650 - Fix a bug that made stream bandwidth get misreported to the
5652 - Stop using malloc_usable_size() to use more area than we had
5653 actually allocated: it was safe, but made valgrind really unhappy.
5654 - Fix a memory leak when v3 directory authorities load their keys
5655 and cert from disk. Bugfix on 0.2.0.1-alpha.
5657 o Minor bugfixes (on 0.2.1.x):
5658 - Fix use of freed memory when deciding to mark a non-addable
5659 descriptor as never-downloadable. Bugfix on 0.2.1.9-alpha.
5662 Changes in version 0.2.1.14-rc - 2009-04-12
5663 Tor 0.2.1.14-rc marks the first release candidate for the 0.2.1.x
5664 series. It begins fixing some major performance problems, and also
5665 finally addresses the bug that was causing relays on dynamic IP
5666 addresses to fall out of the directory.
5669 - Clients replace entry guards that were chosen more than a few months
5670 ago. This change should significantly improve client performance,
5671 especially once more people upgrade, since relays that have been
5672 a guard for a long time are currently overloaded.
5674 o Major bugfixes (on 0.2.0):
5675 - Finally fix the bug where dynamic-IP relays disappear when their
5676 IP address changes: directory mirrors were mistakenly telling
5677 them their old address if they asked via begin_dir, so they
5678 never got an accurate answer about their new address, so they
5679 just vanished after a day. For belt-and-suspenders, relays that
5680 don't set Address in their config now avoid using begin_dir for
5681 all direct connections. Should fix bugs 827, 883, and 900.
5682 - Relays were falling out of the networkstatus consensus for
5683 part of a day if they changed their local config but the
5684 authorities discarded their new descriptor as "not sufficiently
5685 different". Now directory authorities accept a descriptor as changed
5686 if bandwidthrate or bandwidthburst changed. Partial fix for bug 962;
5688 - Avoid crashing in the presence of certain malformed descriptors.
5689 Found by lark, and by automated fuzzing.
5692 - When generating circuit events with verbose nicknames for
5693 controllers, try harder to look up nicknames for routers on a
5694 circuit. (Previously, we would look in the router descriptors we had
5695 for nicknames, but not in the consensus.) Partial fix for bug 941.
5696 - If the bridge config line doesn't specify a port, assume 443.
5697 This makes bridge lines a bit smaller and easier for users to
5699 - Raise the minimum bandwidth to be a relay from 20000 bytes to 20480
5700 bytes (aka 20KB/s), to match our documentation. Also update
5701 directory authorities so they always assign the Fast flag to relays
5702 with 20KB/s of capacity. Now people running relays won't suddenly
5703 find themselves not seeing any use, if the network gets faster
5705 - Update to the "April 3 2009" ip-to-country file.
5708 - Avoid trying to print raw memory to the logs when we decide to
5709 give up on downloading a given relay descriptor. Bugfix on
5711 - In tor-resolve, when the Tor client to use is specified by
5712 <hostname>:<port>, actually use the specified port rather than
5713 defaulting to 9050. Bugfix on 0.2.1.6-alpha.
5714 - Make directory usage recording work again. Bugfix on 0.2.1.6-alpha.
5715 - When starting with a cache over a few days old, do not leak
5716 memory for the obsolete router descriptors in it. Bugfix on
5718 - Avoid double-free on list of successfully uploaded hidden
5719 service discriptors. Fix for bug 948. Bugfix on 0.2.1.6-alpha.
5720 - Change memarea_strndup() implementation to work even when
5721 duplicating a string at the end of a page. This bug was
5722 harmless for now, but could have meant crashes later. Fix by
5723 lark. Bugfix on 0.2.1.1-alpha.
5724 - Limit uploaded directory documents to be 16M rather than 500K.
5725 The directory authorities were refusing v3 consensus votes from
5726 other authorities, since the votes are now 504K. Fixes bug 959;
5727 bugfix on 0.0.2pre17 (where we raised it from 50K to 500K ;).
5728 - Directory authorities should never send a 503 "busy" response to
5729 requests for votes or keys. Bugfix on 0.2.0.8-alpha; exposed by
5733 Changes in version 0.2.1.13-alpha - 2009-03-09
5734 Tor 0.2.1.13-alpha includes another big pile of minor bugfixes and
5735 cleanups. We're finally getting close to a release candidate.
5738 - Correctly update the list of which countries we exclude as
5739 exits, when the GeoIP file is loaded or reloaded. Diagnosed by
5740 lark. Bugfix on 0.2.1.6-alpha.
5742 o Minor bugfixes (on 0.2.0.x and earlier):
5743 - Automatically detect MacOSX versions earlier than 10.4.0, and
5744 disable kqueue from inside Tor when running with these versions.
5745 We previously did this from the startup script, but that was no
5746 help to people who didn't use the startup script. Resolves bug 863.
5747 - When we had picked an exit node for a connection, but marked it as
5748 "optional", and it turned out we had no onion key for the exit,
5749 stop wanting that exit and try again. This situation may not
5750 be possible now, but will probably become feasible with proposal
5751 158. Spotted by rovv. Fixes another case of bug 752.
5752 - Clients no longer cache certificates for authorities they do not
5753 recognize. Bugfix on 0.2.0.9-alpha.
5754 - When we can't transmit a DNS request due to a network error, retry
5755 it after a while, and eventually transmit a failing response to
5756 the RESOLVED cell. Bugfix on 0.1.2.5-alpha.
5757 - If the controller claimed responsibility for a stream, but that
5758 stream never finished making its connection, it would live
5759 forever in circuit_wait state. Now we close it after SocksTimeout
5760 seconds. Bugfix on 0.1.2.7-alpha; reported by Mike Perry.
5761 - Drop begin cells to a hidden service if they come from the middle
5762 of a circuit. Patch from lark.
5763 - When we erroneously receive two EXTEND cells for the same circuit
5764 ID on the same connection, drop the second. Patch from lark.
5765 - Fix a crash that occurs on exit nodes when a nameserver request
5766 timed out. Bugfix on 0.1.2.1-alpha; our CLEAR debugging code had
5767 been suppressing the bug since 0.1.2.10-alpha. Partial fix for
5769 - Do not assume that a stack-allocated character array will be
5770 64-bit aligned on platforms that demand that uint64_t access is
5771 aligned. Possible fix for bug 604.
5772 - Parse dates and IPv4 addresses in a locale- and libc-independent
5773 manner, to avoid platform-dependent behavior on malformed input.
5774 - Build correctly when configured to build outside the main source
5775 path. Patch from Michael Gold.
5776 - We were already rejecting relay begin cells with destination port
5777 of 0. Now also reject extend cells with destination port or address
5778 of 0. Suggested by lark.
5780 o Minor bugfixes (on 0.2.1.x):
5781 - Don't re-extend introduction circuits if we ran out of RELAY_EARLY
5782 cells. Bugfix on 0.2.1.3-alpha. Fixes more of bug 878.
5783 - If we're an exit node, scrub the IP address to which we are exiting
5784 in the logs. Bugfix on 0.2.1.8-alpha.
5787 - On Linux, use the prctl call to re-enable core dumps when the user
5789 - New controller event NEWCONSENSUS that lists the networkstatus
5790 lines for every recommended relay. Now controllers like Torflow
5791 can keep up-to-date on which relays they should be using.
5792 - Update to the "February 26 2009" ip-to-country file.
5795 Changes in version 0.2.0.34 - 2009-02-08
5796 Tor 0.2.0.34 features several more security-related fixes. You should
5797 upgrade, especially if you run an exit relay (remote crash) or a
5798 directory authority (remote infinite loop), or you're on an older
5799 (pre-XP) or not-recently-patched Windows (remote exploit).
5801 This release marks end-of-life for Tor 0.1.2.x. Those Tor versions
5802 have many known flaws, and nobody should be using them. You should
5803 upgrade. If you're using a Linux or BSD and its packages are obsolete,
5804 stop using those packages and upgrade anyway.
5807 - Fix an infinite-loop bug on handling corrupt votes under certain
5808 circumstances. Bugfix on 0.2.0.8-alpha.
5809 - Fix a temporary DoS vulnerability that could be performed by
5810 a directory mirror. Bugfix on 0.2.0.9-alpha; reported by lark.
5811 - Avoid a potential crash on exit nodes when processing malformed
5812 input. Remote DoS opportunity. Bugfix on 0.2.0.33.
5813 - Do not accept incomplete ipv4 addresses (like 192.168.0) as valid.
5814 Spec conformance issue. Bugfix on Tor 0.0.2pre27.
5817 - Fix compilation on systems where time_t is a 64-bit integer.
5818 Patch from Matthias Drochner.
5819 - Don't consider expiring already-closed client connections. Fixes
5820 bug 893. Bugfix on 0.0.2pre20.
5823 Changes in version 0.2.1.12-alpha - 2009-02-08
5824 Tor 0.2.1.12-alpha features several more security-related fixes. You
5825 should upgrade, especially if you run an exit relay (remote crash) or
5826 a directory authority (remote infinite loop), or you're on an older
5827 (pre-XP) or not-recently-patched Windows (remote exploit). It also
5828 includes a big pile of minor bugfixes and cleanups.
5831 - Fix an infinite-loop bug on handling corrupt votes under certain
5832 circumstances. Bugfix on 0.2.0.8-alpha.
5833 - Fix a temporary DoS vulnerability that could be performed by
5834 a directory mirror. Bugfix on 0.2.0.9-alpha; reported by lark.
5835 - Avoid a potential crash on exit nodes when processing malformed
5836 input. Remote DoS opportunity. Bugfix on 0.2.1.7-alpha.
5839 - Let controllers actually ask for the "clients_seen" event for
5840 getting usage summaries on bridge relays. Bugfix on 0.2.1.10-alpha;
5841 reported by Matt Edman.
5842 - Fix a compile warning on OSX Panther. Fixes bug 913; bugfix against
5844 - Fix a bug in address parsing that was preventing bridges or hidden
5845 service targets from being at IPv6 addresses.
5846 - Solve a bug that kept hardware crypto acceleration from getting
5847 enabled when accounting was turned on. Fixes bug 907. Bugfix on
5849 - Remove a bash-ism from configure.in to build properly on non-Linux
5850 platforms. Bugfix on 0.2.1.1-alpha.
5851 - Fix code so authorities _actually_ send back X-Descriptor-Not-New
5852 headers. Bugfix on 0.2.0.10-alpha.
5853 - Don't consider expiring already-closed client connections. Fixes
5854 bug 893. Bugfix on 0.0.2pre20.
5855 - Fix another interesting corner-case of bug 891 spotted by rovv:
5856 Previously, if two hosts had different amounts of clock drift, and
5857 one of them created a new connection with just the wrong timing,
5858 the other might decide to deprecate the new connection erroneously.
5859 Bugfix on 0.1.1.13-alpha.
5860 - Resolve a very rare crash bug that could occur when the user forced
5861 a nameserver reconfiguration during the middle of a nameserver
5862 probe. Fixes bug 526. Bugfix on 0.1.2.1-alpha.
5863 - Support changing value of ServerDNSRandomizeCase during SIGHUP.
5864 Bugfix on 0.2.1.7-alpha.
5865 - If we're using bridges and our network goes away, be more willing
5866 to forgive our bridges and try again when we get an application
5867 request. Bugfix on 0.2.0.x.
5870 - Support platforms where time_t is 64 bits long. (Congratulations,
5871 NetBSD!) Patch from Matthias Drochner.
5872 - Add a 'getinfo status/clients-seen' controller command, in case
5873 controllers want to hear clients_seen events but connect late.
5876 - Disable GCC's strict alias optimization by default, to avoid the
5877 likelihood of its introducing subtle bugs whenever our code violates
5878 the letter of C99's alias rules.
5881 Changes in version 0.2.0.33 - 2009-01-21
5882 Tor 0.2.0.33 fixes a variety of bugs that were making relays less
5883 useful to users. It also finally fixes a bug where a relay or client
5884 that's been off for many days would take a long time to bootstrap.
5886 This update also fixes an important security-related bug reported by
5887 Ilja van Sprundel. You should upgrade. (We'll send out more details
5888 about the bug once people have had some time to upgrade.)
5891 - Fix a heap-corruption bug that may be remotely triggerable on
5892 some platforms. Reported by Ilja van Sprundel.
5895 - When a stream at an exit relay is in state "resolving" or
5896 "connecting" and it receives an "end" relay cell, the exit relay
5897 would silently ignore the end cell and not close the stream. If
5898 the client never closes the circuit, then the exit relay never
5899 closes the TCP connection. Bug introduced in Tor 0.1.2.1-alpha;
5901 - When sending CREATED cells back for a given circuit, use a 64-bit
5902 connection ID to find the right connection, rather than an addr:port
5903 combination. Now that we can have multiple OR connections between
5904 the same ORs, it is no longer possible to use addr:port to uniquely
5905 identify a connection.
5906 - Bridge relays that had DirPort set to 0 would stop fetching
5907 descriptors shortly after startup, and then briefly resume
5908 after a new bandwidth test and/or after publishing a new bridge
5909 descriptor. Bridge users that try to bootstrap from them would
5910 get a recent networkstatus but would get descriptors from up to
5911 18 hours earlier, meaning most of the descriptors were obsolete
5912 already. Reported by Tas; bugfix on 0.2.0.13-alpha.
5913 - Prevent bridge relays from serving their 'extrainfo' document
5914 to anybody who asks, now that extrainfo docs include potentially
5915 sensitive aggregated client geoip summaries. Bugfix on
5917 - If the cached networkstatus consensus is more than five days old,
5918 discard it rather than trying to use it. In theory it could be
5919 useful because it lists alternate directory mirrors, but in practice
5920 it just means we spend many minutes trying directory mirrors that
5921 are long gone from the network. Also discard router descriptors as
5922 we load them if they are more than five days old, since the onion
5923 key is probably wrong by now. Bugfix on 0.2.0.x. Fixes bug 887.
5926 - Do not mark smartlist_bsearch_idx() function as ATTR_PURE. This bug
5927 could make gcc generate non-functional binary search code. Bugfix
5929 - Build correctly on platforms without socklen_t.
5930 - Compile without warnings on solaris.
5931 - Avoid potential crash on internal error during signature collection.
5932 Fixes bug 864. Patch from rovv.
5933 - Correct handling of possible malformed authority signing key
5934 certificates with internal signature types. Fixes bug 880.
5935 Bugfix on 0.2.0.3-alpha.
5936 - Fix a hard-to-trigger resource leak when logging credential status.
5938 - When we can't initialize DNS because the network is down, do not
5939 automatically stop Tor from starting. Instead, we retry failed
5940 dns_init() every 10 minutes, and change the exit policy to reject
5941 *:* until one succeeds. Fixes bug 691.
5942 - Use 64 bits instead of 32 bits for connection identifiers used with
5943 the controller protocol, to greatly reduce risk of identifier reuse.
5944 - When we're choosing an exit node for a circuit, and we have
5945 no pending streams, choose a good general exit rather than one that
5946 supports "all the pending streams". Bugfix on 0.1.1.x. Fix by rovv.
5947 - Fix another case of assuming, when a specific exit is requested,
5948 that we know more than the user about what hosts it allows.
5949 Fixes one case of bug 752. Patch from rovv.
5950 - Clip the MaxCircuitDirtiness config option to a minimum of 10
5951 seconds. Warn the user if lower values are given in the
5952 configuration. Bugfix on 0.1.0.1-rc. Patch by Sebastian.
5953 - Clip the CircuitBuildTimeout to a minimum of 30 seconds. Warn the
5954 user if lower values are given in the configuration. Bugfix on
5955 0.1.1.17-rc. Patch by Sebastian.
5956 - Fix a memory leak when we decline to add a v2 rendezvous descriptor to
5957 the cache because we already had a v0 descriptor with the same ID.
5958 Bugfix on 0.2.0.18-alpha.
5959 - Fix a race condition when freeing keys shared between main thread
5960 and CPU workers that could result in a memory leak. Bugfix on
5961 0.1.0.1-rc. Fixes bug 889.
5962 - Send a valid END cell back when a client tries to connect to a
5963 nonexistent hidden service port. Bugfix on 0.1.2.15. Fixes bug
5964 840. Patch from rovv.
5965 - Check which hops rendezvous stream cells are associated with to
5966 prevent possible guess-the-streamid injection attacks from
5967 intermediate hops. Fixes another case of bug 446. Based on patch
5969 - If a broken client asks a non-exit router to connect somewhere,
5970 do not even do the DNS lookup before rejecting the connection.
5971 Fixes another case of bug 619. Patch from rovv.
5972 - When a relay gets a create cell it can't decrypt (e.g. because it's
5973 using the wrong onion key), we were dropping it and letting the
5974 client time out. Now actually answer with a destroy cell. Fixes
5975 bug 904. Bugfix on 0.0.2pre8.
5977 o Minor bugfixes (hidden services):
5978 - Do not throw away existing introduction points on SIGHUP. Bugfix on
5979 0.0.6pre1. Patch by Karsten. Fixes bug 874.
5982 - Report the case where all signatures in a detached set are rejected
5983 differently than the case where there is an error handling the
5985 - When we realize that another process has modified our cached
5986 descriptors, print out a more useful error message rather than
5987 triggering an assertion. Fixes bug 885. Patch from Karsten.
5988 - Implement the 0x20 hack to better resist DNS poisoning: set the
5989 case on outgoing DNS requests randomly, and reject responses that do
5990 not match the case correctly. This logic can be disabled with the
5991 ServerDNSRamdomizeCase setting, if you are using one of the 0.3%
5992 of servers that do not reliably preserve case in replies. See
5993 "Increased DNS Forgery Resistance through 0x20-Bit Encoding"
5995 - Check DNS replies for more matching fields to better resist DNS
5997 - Never use OpenSSL compression: it wastes RAM and CPU trying to
5998 compress cells, which are basically all encrypted, compressed, or
6002 Changes in version 0.2.1.11-alpha - 2009-01-20
6003 Tor 0.2.1.11-alpha finishes fixing the "if your Tor is off for a
6004 week it will take a long time to bootstrap again" bug. It also fixes
6005 an important security-related bug reported by Ilja van Sprundel. You
6006 should upgrade. (We'll send out more details about the bug once people
6007 have had some time to upgrade.)
6010 - Fix a heap-corruption bug that may be remotely triggerable on
6011 some platforms. Reported by Ilja van Sprundel.
6014 - Discard router descriptors as we load them if they are more than
6015 five days old. Otherwise if Tor is off for a long time and then
6016 starts with cached descriptors, it will try to use the onion
6017 keys in those obsolete descriptors when building circuits. Bugfix
6018 on 0.2.0.x. Fixes bug 887.
6021 - Try to make sure that the version of Libevent we're running with
6022 is binary-compatible with the one we built with. May address bug
6024 - Make setting ServerDNSRandomizeCase to 0 actually work. Bugfix
6025 for bug 905. Bugfix on 0.2.1.7-alpha.
6026 - Add a new --enable-local-appdata configuration switch to change
6027 the default location of the datadir on win32 from APPDATA to
6028 LOCAL_APPDATA. In the future, we should migrate to LOCAL_APPDATA
6029 entirely. Patch from coderman.
6032 - Make outbound DNS packets respect the OutboundBindAddress setting.
6033 Fixes the bug part of bug 798. Bugfix on 0.1.2.2-alpha.
6034 - When our circuit fails at the first hop (e.g. we get a destroy
6035 cell back), avoid using that OR connection anymore, and also
6036 tell all the one-hop directory requests waiting for it that they
6037 should fail. Bugfix on 0.2.1.3-alpha.
6038 - In the torify(1) manpage, mention that tsocks will leak your
6042 Changes in version 0.2.1.10-alpha - 2009-01-06
6043 Tor 0.2.1.10-alpha fixes two major bugs in bridge relays (one that
6044 would make the bridge relay not so useful if it had DirPort set to 0,
6045 and one that could let an attacker learn a little bit of information
6046 about the bridge's users), and a bug that would cause your Tor relay
6047 to ignore a circuit create request it can't decrypt (rather than reply
6048 with an error). It also fixes a wide variety of other bugs.
6051 - If the cached networkstatus consensus is more than five days old,
6052 discard it rather than trying to use it. In theory it could
6053 be useful because it lists alternate directory mirrors, but in
6054 practice it just means we spend many minutes trying directory
6055 mirrors that are long gone from the network. Helps bug 887 a bit;
6057 - Bridge relays that had DirPort set to 0 would stop fetching
6058 descriptors shortly after startup, and then briefly resume
6059 after a new bandwidth test and/or after publishing a new bridge
6060 descriptor. Bridge users that try to bootstrap from them would
6061 get a recent networkstatus but would get descriptors from up to
6062 18 hours earlier, meaning most of the descriptors were obsolete
6063 already. Reported by Tas; bugfix on 0.2.0.13-alpha.
6064 - Prevent bridge relays from serving their 'extrainfo' document
6065 to anybody who asks, now that extrainfo docs include potentially
6066 sensitive aggregated client geoip summaries. Bugfix on
6070 - New controller event "clients_seen" to report a geoip-based summary
6071 of which countries we've seen clients from recently. Now controllers
6072 like Vidalia can show bridge operators that they're actually making
6074 - Build correctly against versions of OpenSSL 0.9.8 or later built
6075 without support for deprecated functions.
6076 - Update to the "December 19 2008" ip-to-country file.
6078 o Minor bugfixes (on 0.2.0.x):
6079 - Authorities now vote for the Stable flag for any router whose
6080 weighted MTBF is at least 5 days, regardless of the mean MTBF.
6081 - Do not remove routers as too old if we do not have any consensus
6082 document. Bugfix on 0.2.0.7-alpha.
6083 - Do not accept incomplete ipv4 addresses (like 192.168.0) as valid.
6084 Spec conformance issue. Bugfix on Tor 0.0.2pre27.
6085 - When an exit relay resolves a stream address to a local IP address,
6086 do not just keep retrying that same exit relay over and
6087 over. Instead, just close the stream. Addresses bug 872. Bugfix
6088 on 0.2.0.32. Patch from rovv.
6089 - If a hidden service sends us an END cell, do not consider
6090 retrying the connection; just close it. Patch from rovv.
6091 - When we made bridge authorities stop serving bridge descriptors over
6092 unencrypted links, we also broke DirPort reachability testing for
6093 bridges. So bridges with a non-zero DirPort were printing spurious
6094 warns to their logs. Bugfix on 0.2.0.16-alpha. Fixes bug 709.
6095 - When a relay gets a create cell it can't decrypt (e.g. because it's
6096 using the wrong onion key), we were dropping it and letting the
6097 client time out. Now actually answer with a destroy cell. Fixes
6098 bug 904. Bugfix on 0.0.2pre8.
6099 - Squeeze 2-5% out of client performance (according to oprofile) by
6100 improving the implementation of some policy-manipulation functions.
6102 o Minor bugfixes (on 0.2.1.x):
6103 - Make get_interface_address() function work properly again; stop
6104 guessing the wrong parts of our address as our address.
6105 - Do not cannibalize a circuit if we're out of RELAY_EARLY cells to
6106 send on that circuit. Otherwise we might violate the proposal-110
6107 limit. Bugfix on 0.2.1.3-alpha. Partial fix for bug 878. Diagnosis
6109 - When we're sending non-EXTEND cells to the first hop in a circuit,
6110 for example to use an encrypted directory connection, we don't need
6111 to use RELAY_EARLY cells: the first hop knows what kind of cell
6112 it is, and nobody else can even see the cell type. Conserving
6113 RELAY_EARLY cells makes it easier to cannibalize circuits like
6115 - Stop logging nameserver addresses in reverse order.
6116 - If we are retrying a directory download slowly over and over, do
6117 not automatically give up after the 254th failure. Bugfix on
6119 - Resume reporting accurate "stream end" reasons to the local control
6120 port. They were lost in the changes for Proposal 148. Bugfix on
6123 o Deprecated and removed features:
6124 - The old "tor --version --version" command, which would print out
6125 the subversion "Id" of most of the source files, is now removed. It
6126 turned out to be less useful than we'd expected, and harder to
6129 o Code simplifications and refactoring:
6130 - Change our header file guard macros to be less likely to conflict
6131 with system headers. Adam Langley noticed that we were conflicting
6132 with log.h on Android.
6133 - Tool-assisted documentation cleanup. Nearly every function or
6134 static variable in Tor should have its own documentation now.
6137 Changes in version 0.2.1.9-alpha - 2008-12-25
6138 Tor 0.2.1.9-alpha fixes many more bugs, some of them security-related.
6140 o New directory authorities:
6141 - gabelmoo (the authority run by Karsten Loesing) now has a new
6145 - Never use a connection with a mismatched address to extend a
6146 circuit, unless that connection is canonical. A canonical
6147 connection is one whose address is authenticated by the router's
6148 identity key, either in a NETINFO cell or in a router descriptor.
6149 - Avoid a possible memory corruption bug when receiving hidden service
6150 descriptors. Bugfix on 0.2.1.6-alpha.
6153 - Fix a logic error that would automatically reject all but the first
6154 configured DNS server. Bugfix on 0.2.1.5-alpha. Possible fix for
6155 part of bug 813/868. Bug spotted by coderman.
6156 - When a stream at an exit relay is in state "resolving" or
6157 "connecting" and it receives an "end" relay cell, the exit relay
6158 would silently ignore the end cell and not close the stream. If
6159 the client never closes the circuit, then the exit relay never
6160 closes the TCP connection. Bug introduced in 0.1.2.1-alpha;
6162 - When we can't initialize DNS because the network is down, do not
6163 automatically stop Tor from starting. Instead, retry failed
6164 dns_init() every 10 minutes, and change the exit policy to reject
6165 *:* until one succeeds. Fixes bug 691.
6168 - Give a better error message when an overzealous init script says
6169 "sudo -u username tor --user username". Makes Bug 882 easier for
6171 - When a directory authority gives us a new guess for our IP address,
6172 log which authority we used. Hopefully this will help us debug
6173 the recent complaints about bad IP address guesses.
6174 - Detect svn revision properly when we're using git-svn.
6175 - Try not to open more than one descriptor-downloading connection
6176 to an authority at once. This should reduce load on directory
6177 authorities. Fixes bug 366.
6178 - Add cross-certification to newly generated certificates, so that
6179 a signing key is enough information to look up a certificate.
6180 Partial implementation of proposal 157.
6181 - Start serving certificates by <identity digest, signing key digest>
6182 pairs. Partial implementation of proposal 157.
6183 - Clients now never report any stream end reason except 'MISC'.
6184 Implements proposal 148.
6185 - On platforms with a maximum syslog string length, truncate syslog
6186 messages to that length ourselves, rather than relying on the
6187 system to do it for us.
6188 - Optimize out calls to time(NULL) that occur for every IO operation,
6189 or for every cell. On systems where time() is a slow syscall,
6190 this fix will be slightly helpful.
6191 - Exit servers can now answer resolve requests for ip6.arpa addresses.
6192 - When we download a descriptor that we then immediately (as
6193 a directory authority) reject, do not retry downloading it right
6194 away. Should save some bandwidth on authorities. Fix for bug
6195 888. Patch by Sebastian Hahn.
6196 - When a download gets us zero good descriptors, do not notify
6197 Tor that new directory information has arrived.
6198 - Avoid some nasty corner cases in the logic for marking connections
6199 as too old or obsolete or noncanonical for circuits. Partial
6202 o Minor features (controller):
6203 - New CONSENSUS_ARRIVED event to note when a new consensus has
6204 been fetched and validated.
6205 - When we realize that another process has modified our cached
6206 descriptors file, print out a more useful error message rather
6207 than triggering an assertion. Fixes bug 885. Patch from Karsten.
6208 - Add an internal-use-only __ReloadTorrcOnSIGHUP option for
6209 controllers to prevent SIGHUP from reloading the
6210 configuration. Fixes bug 856.
6213 - Resume using the correct "REASON=" stream when telling the
6214 controller why we closed a stream. Bugfix in 0.2.1.1-alpha.
6215 - When a canonical connection appears later in our internal list
6216 than a noncanonical one for a given OR ID, always use the
6217 canonical one. Bugfix on 0.2.0.12-alpha. Fixes bug 805.
6219 - Clip the MaxCircuitDirtiness config option to a minimum of 10
6220 seconds. Warn the user if lower values are given in the
6221 configuration. Bugfix on 0.1.0.1-rc. Patch by Sebastian.
6222 - Clip the CircuitBuildTimeout to a minimum of 30 seconds. Warn the
6223 user if lower values are given in the configuration. Bugfix on
6224 0.1.1.17-rc. Patch by Sebastian.
6225 - Fix a race condition when freeing keys shared between main thread
6226 and CPU workers that could result in a memory leak. Bugfix on
6227 0.1.0.1-rc. Fixes bug 889.
6229 o Minor bugfixes (hidden services):
6230 - Do not throw away existing introduction points on SIGHUP (bugfix on
6231 0.0.6pre1); also, do not stall hidden services because we're
6232 throwing away introduction points; bugfix on 0.2.1.7-alpha. Spotted
6233 by John Brooks. Patch by Karsten. Fixes bug 874.
6234 - Fix a memory leak when we decline to add a v2 rendezvous
6235 descriptor to the cache because we already had a v0 descriptor
6236 with the same ID. Bugfix on 0.2.0.18-alpha.
6238 o Deprecated and removed features:
6239 - RedirectExits has been removed. It was deprecated since
6241 - Finally remove deprecated "EXTENDED_FORMAT" controller feature. It
6242 has been called EXTENDED_EVENTS since 0.1.2.4-alpha.
6243 - Cell pools are now always enabled; --disable-cell-pools is ignored.
6245 o Code simplifications and refactoring:
6246 - Rename the confusing or_is_obsolete field to the more appropriate
6247 is_bad_for_new_circs, and move it to or_connection_t where it
6249 - Move edge-only flags from connection_t to edge_connection_t: not
6250 only is this better coding, but on machines of plausible alignment,
6251 it should save 4-8 bytes per connection_t. "Every little bit helps."
6252 - Rename ServerDNSAllowBrokenResolvConf to ServerDNSAllowBrokenConfig
6253 for consistency; keep old option working for backward compatibility.
6254 - Simplify the code for finding connections to use for a circuit.
6257 Changes in version 0.2.1.8-alpha - 2008-12-08
6258 Tor 0.2.1.8-alpha fixes some crash bugs in earlier alpha releases,
6259 builds better on unusual platforms like Solaris and old OS X, and
6260 fixes a variety of other issues.
6263 - New DirPortFrontPage option that takes an html file and publishes
6264 it as "/" on the DirPort. Now relay operators can provide a
6265 disclaimer without needing to set up a separate webserver. There's
6266 a sample disclaimer in contrib/tor-exit-notice.html.
6269 - When the client is choosing entry guards, now it selects at most
6270 one guard from a given relay family. Otherwise we could end up with
6271 all of our entry points into the network run by the same operator.
6272 Suggested by Camilo Viecco. Fix on 0.1.1.11-alpha.
6275 - Fix a DOS opportunity during the voting signature collection process
6276 at directory authorities. Spotted by rovv. Bugfix on 0.2.0.x.
6277 - Fix a possible segfault when establishing an exit connection. Bugfix
6281 - Get file locking working on win32. Bugfix on 0.2.1.6-alpha. Fixes
6283 - Made Tor a little less aggressive about deleting expired
6284 certificates. Partial fix for bug 854.
6285 - Stop doing unaligned memory access that generated bus errors on
6286 sparc64. Bugfix on 0.2.0.10-alpha. Fix for bug 862.
6287 - Fix a crash bug when changing EntryNodes from the controller. Bugfix
6288 on 0.2.1.6-alpha. Fix for bug 867. Patched by Sebastian.
6289 - Make USR2 log-level switch take effect immediately. Bugfix on
6291 - If one win32 nameserver fails to get added, continue adding the
6292 rest, and don't automatically fail.
6293 - Use fcntl() for locking when flock() is not available. Should fix
6294 compilation on Solaris. Should fix Bug 873. Bugfix on 0.2.1.6-alpha.
6295 - Do not mark smartlist_bsearch_idx() function as ATTR_PURE. This bug
6296 could make gcc generate non-functional binary search code. Bugfix
6298 - Build correctly on platforms without socklen_t.
6299 - Avoid potential crash on internal error during signature collection.
6300 Fixes bug 864. Patch from rovv.
6301 - Do not use C's stdio library for writing to log files. This will
6302 improve logging performance by a minute amount, and will stop
6303 leaking fds when our disk is full. Fixes bug 861.
6304 - Stop erroneous use of O_APPEND in cases where we did not in fact
6305 want to re-seek to the end of a file before every last write().
6306 - Correct handling of possible malformed authority signing key
6307 certificates with internal signature types. Fixes bug 880. Bugfix
6309 - Fix a hard-to-trigger resource leak when logging credential status.
6313 - Directory mirrors no longer fetch the v1 directory or
6314 running-routers files. They are obsolete, and nobody asks for them
6315 anymore. This is the first step to making v1 authorities obsolete.
6317 o Minor features (controller):
6318 - Return circuit purposes in response to GETINFO circuit-status. Fixes
6322 Changes in version 0.2.0.32 - 2008-11-20
6323 Tor 0.2.0.32 fixes a major security problem in Debian and Ubuntu
6324 packages (and maybe other packages) noticed by Theo de Raadt, fixes
6325 a smaller security flaw that might allow an attacker to access local
6326 services, further improves hidden service performance, and fixes a
6327 variety of other issues.
6330 - The "User" and "Group" config options did not clear the
6331 supplementary group entries for the Tor process. The "User" option
6332 is now more robust, and we now set the groups to the specified
6333 user's primary group. The "Group" option is now ignored. For more
6334 detailed logging on credential switching, set CREDENTIAL_LOG_LEVEL
6335 in common/compat.c to LOG_NOTICE or higher. Patch by Jacob Appelbaum
6336 and Steven Murdoch. Bugfix on 0.0.2pre14. Fixes bug 848 and 857.
6337 - The "ClientDNSRejectInternalAddresses" config option wasn't being
6338 consistently obeyed: if an exit relay refuses a stream because its
6339 exit policy doesn't allow it, we would remember what IP address
6340 the relay said the destination address resolves to, even if it's
6341 an internal IP address. Bugfix on 0.2.0.7-alpha; patch by rovv.
6344 - Fix a DOS opportunity during the voting signature collection process
6345 at directory authorities. Spotted by rovv. Bugfix on 0.2.0.x.
6347 o Major bugfixes (hidden services):
6348 - When fetching v0 and v2 rendezvous service descriptors in parallel,
6349 we were failing the whole hidden service request when the v0
6350 descriptor fetch fails, even if the v2 fetch is still pending and
6351 might succeed. Similarly, if the last v2 fetch fails, we were
6352 failing the whole hidden service request even if a v0 fetch is
6353 still pending. Fixes bug 814. Bugfix on 0.2.0.10-alpha.
6354 - When extending a circuit to a hidden service directory to upload a
6355 rendezvous descriptor using a BEGIN_DIR cell, almost 1/6 of all
6356 requests failed, because the router descriptor has not been
6357 downloaded yet. In these cases, do not attempt to upload the
6358 rendezvous descriptor, but wait until the router descriptor is
6359 downloaded and retry. Likewise, do not attempt to fetch a rendezvous
6360 descriptor from a hidden service directory for which the router
6361 descriptor has not yet been downloaded. Fixes bug 767. Bugfix
6365 - Fix several infrequent memory leaks spotted by Coverity.
6366 - When testing for libevent functions, set the LDFLAGS variable
6367 correctly. Found by Riastradh.
6368 - Avoid a bug where the FastFirstHopPK 0 option would keep Tor from
6369 bootstrapping with tunneled directory connections. Bugfix on
6370 0.1.2.5-alpha. Fixes bug 797. Found by Erwin Lam.
6371 - When asked to connect to A.B.exit:80, if we don't know the IP for A
6372 and we know that server B rejects most-but-not all connections to
6373 port 80, we would previously reject the connection. Now, we assume
6374 the user knows what they were asking for. Fixes bug 752. Bugfix
6375 on 0.0.9rc5. Diagnosed by BarkerJr.
6376 - If we overrun our per-second write limits a little, count this as
6377 having used up our write allocation for the second, and choke
6378 outgoing directory writes. Previously, we had only counted this when
6379 we had met our limits precisely. Fixes bug 824. Patch from by rovv.
6380 Bugfix on 0.2.0.x (??).
6381 - Remove the old v2 directory authority 'lefkada' from the default
6382 list. It has been gone for many months.
6383 - Stop doing unaligned memory access that generated bus errors on
6384 sparc64. Bugfix on 0.2.0.10-alpha. Fixes bug 862.
6385 - Make USR2 log-level switch take effect immediately. Bugfix on
6388 o Minor bugfixes (controller):
6389 - Make DNS resolved events into "CLOSED", not "FAILED". Bugfix on
6390 0.1.2.5-alpha. Fix by Robert Hogan. Resolves bug 807.
6393 Changes in version 0.2.1.7-alpha - 2008-11-08
6394 Tor 0.2.1.7-alpha fixes a major security problem in Debian and Ubuntu
6395 packages (and maybe other packages) noticed by Theo de Raadt, fixes
6396 a smaller security flaw that might allow an attacker to access local
6397 services, adds better defense against DNS poisoning attacks on exit
6398 relays, further improves hidden service performance, and fixes a
6399 variety of other issues.
6402 - The "ClientDNSRejectInternalAddresses" config option wasn't being
6403 consistently obeyed: if an exit relay refuses a stream because its
6404 exit policy doesn't allow it, we would remember what IP address
6405 the relay said the destination address resolves to, even if it's
6406 an internal IP address. Bugfix on 0.2.0.7-alpha; patch by rovv.
6407 - The "User" and "Group" config options did not clear the
6408 supplementary group entries for the Tor process. The "User" option
6409 is now more robust, and we now set the groups to the specified
6410 user's primary group. The "Group" option is now ignored. For more
6411 detailed logging on credential switching, set CREDENTIAL_LOG_LEVEL
6412 in common/compat.c to LOG_NOTICE or higher. Patch by Jacob Appelbaum
6413 and Steven Murdoch. Bugfix on 0.0.2pre14. Fixes bug 848.
6414 - Do not use or believe expired v3 authority certificates. Patch
6415 from Karsten. Bugfix in 0.2.0.x. Fixes bug 851.
6418 - Now NodeFamily and MyFamily config options allow spaces in
6419 identity fingerprints, so it's easier to paste them in.
6420 Suggested by Lucky Green.
6421 - Implement the 0x20 hack to better resist DNS poisoning: set the
6422 case on outgoing DNS requests randomly, and reject responses that do
6423 not match the case correctly. This logic can be disabled with the
6424 ServerDNSRandomizeCase setting, if you are using one of the 0.3%
6425 of servers that do not reliably preserve case in replies. See
6426 "Increased DNS Forgery Resistance through 0x20-Bit Encoding"
6428 - Preserve case in replies to DNSPort requests in order to support
6429 the 0x20 hack for resisting DNS poisoning attacks.
6431 o Hidden service performance improvements:
6432 - When the client launches an introduction circuit, retry with a
6433 new circuit after 30 seconds rather than 60 seconds.
6434 - Launch a second client-side introduction circuit in parallel
6435 after a delay of 15 seconds (based on work by Christian Wilms).
6436 - Hidden services start out building five intro circuits rather
6437 than three, and when the first three finish they publish a service
6438 descriptor using those. Now we publish our service descriptor much
6439 faster after restart.
6442 - Minor fix in the warning messages when you're having problems
6443 bootstrapping; also, be more forgiving of bootstrap problems when
6444 we're still making incremental progress on a given bootstrap phase.
6445 - When we're choosing an exit node for a circuit, and we have
6446 no pending streams, choose a good general exit rather than one that
6447 supports "all the pending streams". Bugfix on 0.1.1.x. Fix by rovv.
6448 - Send a valid END cell back when a client tries to connect to a
6449 nonexistent hidden service port. Bugfix on 0.1.2.15. Fixes bug
6450 840. Patch from rovv.
6451 - If a broken client asks a non-exit router to connect somewhere,
6452 do not even do the DNS lookup before rejecting the connection.
6453 Fixes another case of bug 619. Patch from rovv.
6454 - Fix another case of assuming, when a specific exit is requested,
6455 that we know more than the user about what hosts it allows.
6456 Fixes another case of bug 752. Patch from rovv.
6457 - Check which hops rendezvous stream cells are associated with to
6458 prevent possible guess-the-streamid injection attacks from
6459 intermediate hops. Fixes another case of bug 446. Based on patch
6461 - Avoid using a negative right-shift when comparing 32-bit
6462 addresses. Possible fix for bug 845 and bug 811.
6463 - Make the assert_circuit_ok() function work correctly on circuits that
6464 have already been marked for close.
6465 - Fix read-off-the-end-of-string error in unit tests when decoding
6466 introduction points.
6467 - Fix uninitialized size field for memory area allocation: may improve
6468 memory performance during directory parsing.
6469 - Treat duplicate certificate fetches as failures, so that we do
6470 not try to re-fetch an expired certificate over and over and over.
6471 - Do not say we're fetching a certificate when we'll in fact skip it
6472 because of a pending download.
6475 Changes in version 0.2.1.6-alpha - 2008-09-30
6476 Tor 0.2.1.6-alpha further improves performance and robustness of
6477 hidden services, starts work on supporting per-country relay selection,
6478 and fixes a variety of smaller issues.
6481 - Implement proposal 121: make it possible to build hidden services
6482 that only certain clients are allowed to connect to. This is
6483 enforced at several points, so that unauthorized clients are unable
6484 to send INTRODUCE cells to the service, or even (depending on the
6485 type of authentication) to learn introduction points. This feature
6486 raises the bar for certain kinds of active attacks against hidden
6487 services. Code by Karsten Loesing.
6488 - Relays now store and serve v2 hidden service descriptors by default,
6489 i.e., the new default value for HidServDirectoryV2 is 1. This is
6490 the last step in proposal 114, which aims to make hidden service
6491 lookups more reliable.
6492 - Start work to allow node restrictions to include country codes. The
6493 syntax to exclude nodes in a country with country code XX is
6494 "ExcludeNodes {XX}". Patch from Robert Hogan. It still needs some
6495 refinement to decide what config options should take priority if
6496 you ask to both use a particular node and exclude it.
6497 - Allow ExitNodes list to include IP ranges and country codes, just
6498 like the Exclude*Nodes lists. Patch from Robert Hogan.
6501 - Fix a bug when parsing ports in tor_addr_port_parse() that caused
6502 Tor to fail to start if you had it configured to use a bridge
6503 relay. Fixes bug 809. Bugfix on 0.2.1.5-alpha.
6504 - When extending a circuit to a hidden service directory to upload a
6505 rendezvous descriptor using a BEGIN_DIR cell, almost 1/6 of all
6506 requests failed, because the router descriptor had not been
6507 downloaded yet. In these cases, we now wait until the router
6508 descriptor is downloaded, and then retry. Likewise, clients
6509 now skip over a hidden service directory if they don't yet have
6510 its router descriptor, rather than futilely requesting it and
6511 putting mysterious complaints in the logs. Fixes bug 767. Bugfix
6513 - When fetching v0 and v2 rendezvous service descriptors in parallel,
6514 we were failing the whole hidden service request when the v0
6515 descriptor fetch fails, even if the v2 fetch is still pending and
6516 might succeed. Similarly, if the last v2 fetch fails, we were
6517 failing the whole hidden service request even if a v0 fetch is
6518 still pending. Fixes bug 814. Bugfix on 0.2.0.10-alpha.
6519 - DNS replies need to have names matching their requests, but
6520 these names should be in the questions section, not necessarily
6521 in the answers section. Fixes bug 823. Bugfix on 0.2.1.5-alpha.
6524 - Update to the "September 1 2008" ip-to-country file.
6525 - Allow ports 465 and 587 in the default exit policy again. We had
6526 rejected them in 0.1.0.15, because back in 2005 they were commonly
6527 misconfigured and ended up as spam targets. We hear they are better
6528 locked down these days.
6529 - Use a lockfile to make sure that two Tor processes are not
6530 simultaneously running with the same datadir.
6531 - Serve the latest v3 networkstatus consensus via the control
6532 port. Use "getinfo dir/status-vote/current/consensus" to fetch it.
6533 - Better logging about stability/reliability calculations on directory
6535 - Drop the requirement to have an open dir port for storing and
6536 serving v2 hidden service descriptors.
6537 - Directory authorities now serve a /tor/dbg-stability.txt URL to
6538 help debug WFU and MTBF calculations.
6539 - Implement most of Proposal 152: allow specialized servers to permit
6540 single-hop circuits, and clients to use those servers to build
6541 single-hop circuits when using a specialized controller. Patch
6542 from Josh Albrecht. Resolves feature request 768.
6543 - Add a -p option to tor-resolve for specifying the SOCKS port: some
6544 people find host:port too confusing.
6545 - Make TrackHostExit mappings expire a while after their last use, not
6546 after their creation. Patch from Robert Hogan.
6547 - Provide circuit purposes along with circuit events to the controller.
6550 - Fix compile on OpenBSD 4.4-current. Bugfix on 0.2.1.5-alpha.
6552 - Fixed some memory leaks -- some quite frequent, some almost
6553 impossible to trigger -- based on results from Coverity.
6554 - When testing for libevent functions, set the LDFLAGS variable
6555 correctly. Found by Riastradh.
6556 - Fix an assertion bug in parsing policy-related options; possible fix
6558 - Catch and report a few more bootstrapping failure cases when Tor
6559 fails to establish a TCP connection. Cleanup on 0.2.1.x.
6560 - Avoid a bug where the FastFirstHopPK 0 option would keep Tor from
6561 bootstrapping with tunneled directory connections. Bugfix on
6562 0.1.2.5-alpha. Fixes bug 797. Found by Erwin Lam.
6563 - When asked to connect to A.B.exit:80, if we don't know the IP for A
6564 and we know that server B rejects most-but-not all connections to
6565 port 80, we would previously reject the connection. Now, we assume
6566 the user knows what they were asking for. Fixes bug 752. Bugfix
6567 on 0.0.9rc5. Diagnosed by BarkerJr.
6568 - If we are not using BEGIN_DIR cells, don't attempt to contact hidden
6569 service directories if they have no advertised dir port. Bugfix
6571 - If we overrun our per-second write limits a little, count this as
6572 having used up our write allocation for the second, and choke
6573 outgoing directory writes. Previously, we had only counted this when
6574 we had met our limits precisely. Fixes bug 824. Patch by rovv.
6575 Bugfix on 0.2.0.x (??).
6576 - Avoid a "0 divided by 0" calculation when calculating router uptime
6577 at directory authorities. Bugfix on 0.2.0.8-alpha.
6578 - Make DNS resolved controller events into "CLOSED", not
6579 "FAILED". Bugfix on 0.1.2.5-alpha. Fix by Robert Hogan. Resolves
6581 - Fix a bug where an unreachable relay would establish enough
6582 reachability testing circuits to do a bandwidth test -- if
6583 we already have a connection to the middle hop of the testing
6584 circuit, then it could establish the last hop by using the existing
6585 connection. Bugfix on 0.1.2.2-alpha, exposed when we made testing
6586 circuits no longer use entry guards in 0.2.1.3-alpha.
6587 - If we have correct permissions on $datadir, we complain to stdout
6588 and fail to start. But dangerous permissions on
6589 $datadir/cached-status/ would cause us to open a log and complain
6590 there. Now complain to stdout and fail to start in both cases. Fixes
6591 bug 820, reported by seeess.
6592 - Remove the old v2 directory authority 'lefkada' from the default
6593 list. It has been gone for many months.
6595 o Code simplifications and refactoring:
6596 - Revise the connection_new functions so that a more typesafe variant
6597 exists. This will work better with Coverity, and let us find any
6598 actual mistakes we're making here.
6599 - Refactor unit testing logic so that dmalloc can be used sensibly
6600 with unit tests to check for memory leaks.
6601 - Move all hidden-service related fields from connection and circuit
6602 structure to substructures: this way they won't eat so much memory.
6605 Changes in version 0.2.0.31 - 2008-09-03
6606 Tor 0.2.0.31 addresses two potential anonymity issues, starts to fix
6607 a big bug we're seeing where in rare cases traffic from one Tor stream
6608 gets mixed into another stream, and fixes a variety of smaller issues.
6611 - Make sure that two circuits can never exist on the same connection
6612 with the same circuit ID, even if one is marked for close. This
6613 is conceivably a bugfix for bug 779. Bugfix on 0.1.0.4-rc.
6614 - Relays now reject risky extend cells: if the extend cell includes
6615 a digest of all zeroes, or asks to extend back to the relay that
6616 sent the extend cell, tear down the circuit. Ideas suggested
6618 - If not enough of our entry guards are available so we add a new
6619 one, we might use the new one even if it overlapped with the
6620 current circuit's exit relay (or its family). Anonymity bugfix
6621 pointed out by rovv.
6624 - Recover 3-7 bytes that were wasted per memory chunk. Fixes bug
6625 794; bug spotted by rovv. Bugfix on 0.2.0.1-alpha.
6626 - Correctly detect the presence of the linux/netfilter_ipv4.h header
6627 when building against recent kernels. Bugfix on 0.1.2.1-alpha.
6628 - Pick size of default geoip filename string correctly on windows.
6629 Fixes bug 806. Bugfix on 0.2.0.30.
6630 - Make the autoconf script accept the obsolete --with-ssl-dir
6631 option as an alias for the actually-working --with-openssl-dir
6632 option. Fix the help documentation to recommend --with-openssl-dir.
6633 Based on a patch by "Dave". Bugfix on 0.2.0.1-alpha.
6634 - When using the TransPort option on OpenBSD, and using the User
6635 option to change UID and drop privileges, make sure to open
6636 /dev/pf before dropping privileges. Fixes bug 782. Patch from
6637 Christopher Davis. Bugfix on 0.1.2.1-alpha.
6638 - Try to attach connections immediately upon receiving a RENDEZVOUS2
6639 or RENDEZVOUS_ESTABLISHED cell. This can save a second or two
6640 on the client side when connecting to a hidden service. Bugfix
6641 on 0.0.6pre1. Found and fixed by Christian Wilms; resolves bug 743.
6642 - When closing an application-side connection because its circuit is
6643 getting torn down, generate the stream event correctly. Bugfix on
6644 0.1.2.x. Anonymous patch.
6647 Changes in version 0.2.1.5-alpha - 2008-08-31
6648 Tor 0.2.1.5-alpha moves us closer to handling IPv6 destinations, puts
6649 in a lot of the infrastructure for adding authorization to hidden
6650 services, lays the groundwork for having clients read their load
6651 balancing information out of the networkstatus consensus rather than
6652 the individual router descriptors, addresses two potential anonymity
6653 issues, and fixes a variety of smaller issues.
6656 - Convert many internal address representations to optionally hold
6658 - Generate and accept IPv6 addresses in many protocol elements.
6659 - Make resolver code handle nameservers located at ipv6 addresses.
6660 - Begin implementation of proposal 121 ("Client authorization for
6661 hidden services"): configure hidden services with client
6662 authorization, publish descriptors for them, and configure
6663 authorization data for hidden services at clients. The next
6664 step is to actually access hidden services that perform client
6666 - More progress toward proposal 141: Network status consensus
6667 documents and votes now contain bandwidth information for each
6668 router and a summary of that router's exit policy. Eventually this
6669 will be used by clients so that they do not have to download every
6670 known descriptor before building circuits.
6672 o Major bugfixes (on 0.2.0.x and before):
6673 - When sending CREATED cells back for a given circuit, use a 64-bit
6674 connection ID to find the right connection, rather than an addr:port
6675 combination. Now that we can have multiple OR connections between
6676 the same ORs, it is no longer possible to use addr:port to uniquely
6677 identify a connection.
6678 - Relays now reject risky extend cells: if the extend cell includes
6679 a digest of all zeroes, or asks to extend back to the relay that
6680 sent the extend cell, tear down the circuit. Ideas suggested
6682 - If not enough of our entry guards are available so we add a new
6683 one, we might use the new one even if it overlapped with the
6684 current circuit's exit relay (or its family). Anonymity bugfix
6685 pointed out by rovv.
6688 - Recover 3-7 bytes that were wasted per memory chunk. Fixes bug
6689 794; bug spotted by rovv. Bugfix on 0.2.0.1-alpha.
6690 - When using the TransPort option on OpenBSD, and using the User
6691 option to change UID and drop privileges, make sure to open /dev/pf
6692 before dropping privileges. Fixes bug 782. Patch from Christopher
6693 Davis. Bugfix on 0.1.2.1-alpha.
6694 - Correctly detect the presence of the linux/netfilter_ipv4.h header
6695 when building against recent kernels. Bugfix on 0.1.2.1-alpha.
6696 - Add a missing safe_str() call for a debug log message.
6697 - Use 64 bits instead of 32 bits for connection identifiers used with
6698 the controller protocol, to greatly reduce risk of identifier reuse.
6699 - Make the autoconf script accept the obsolete --with-ssl-dir
6700 option as an alias for the actually-working --with-openssl-dir
6701 option. Fix the help documentation to recommend --with-openssl-dir.
6702 Based on a patch by "Dave". Bugfix on 0.2.0.1-alpha.
6705 - Rate-limit too-many-sockets messages: when they happen, they happen
6706 a lot. Resolves bug 748.
6707 - Resist DNS poisoning a little better by making sure that names in
6708 answer sections match.
6709 - Print the SOCKS5 error message string as well as the error code
6710 when a tor-resolve request fails. Patch from Jacob.
6713 Changes in version 0.2.1.4-alpha - 2008-08-04
6714 Tor 0.2.1.4-alpha fixes a pair of crash bugs in 0.2.1.3-alpha.
6717 - The address part of exit policies was not correctly written
6718 to router descriptors. This generated router descriptors that failed
6719 their self-checks. Noticed by phobos, fixed by Karsten. Bugfix
6721 - Tor triggered a false assert when extending a circuit to a relay
6722 but we already have a connection open to that relay. Noticed by
6723 phobos, fixed by Karsten. Bugfix on 0.2.1.3-alpha.
6726 - Fix a hidden service logging bug: in some edge cases, the router
6727 descriptor of a previously picked introduction point becomes
6728 obsolete and we need to give up on it rather than continually
6729 complaining that it has become obsolete. Observed by xiando. Bugfix
6733 - Take out the TestVia config option, since it was a workaround for
6734 a bug that was fixed in Tor 0.1.1.21.
6737 Changes in version 0.2.1.3-alpha - 2008-08-03
6738 Tor 0.2.1.3-alpha implements most of the pieces to prevent
6739 infinite-length circuit attacks (see proposal 110); fixes a bug that
6740 might cause exit relays to corrupt streams they send back; allows
6741 address patterns (e.g. 255.128.0.0/16) to appear in ExcludeNodes and
6742 ExcludeExitNodes config options; and fixes a big pile of bugs.
6744 o Bootstrapping bugfixes (on 0.2.1.x-alpha):
6745 - Send a bootstrap problem "warn" event on the first problem if the
6746 reason is NO_ROUTE (that is, our network is down).
6749 - Implement most of proposal 110: The first K cells to be sent
6750 along a circuit are marked as special "early" cells; only K "early"
6751 cells will be allowed. Once this code is universal, we can block
6752 certain kinds of DOS attack by requiring that EXTEND commands must
6753 be sent using an "early" cell.
6756 - Try to attach connections immediately upon receiving a RENDEZVOUS2
6757 or RENDEZVOUS_ESTABLISHED cell. This can save a second or two
6758 on the client side when connecting to a hidden service. Bugfix
6759 on 0.0.6pre1. Found and fixed by Christian Wilms; resolves bug 743.
6760 - Ensure that two circuits can never exist on the same connection
6761 with the same circuit ID, even if one is marked for close. This
6762 is conceivably a bugfix for bug 779; fixes a bug on 0.1.0.4-rc.
6765 - When relays do their initial bandwidth measurement, don't limit
6766 to just our entry guards for the test circuits. Otherwise we tend
6767 to have multiple test circuits going through a single entry guard,
6768 which makes our bandwidth test less accurate. Fixes part of bug 654;
6769 patch contributed by Josh Albrecht.
6770 - Add an ExcludeExitNodes option so users can list a set of nodes
6771 that should be be excluded from the exit node position, but
6772 allowed elsewhere. Implements proposal 151.
6773 - Allow address patterns (e.g., 255.128.0.0/16) to appear in
6774 ExcludeNodes and ExcludeExitNodes lists.
6775 - Change the implementation of ExcludeNodes and ExcludeExitNodes to
6776 be more efficient. Formerly it was quadratic in the number of
6777 servers; now it should be linear. Fixes bug 509.
6778 - Save 16-22 bytes per open circuit by moving the n_addr, n_port,
6779 and n_conn_id_digest fields into a separate structure that's
6780 only needed when the circuit has not yet attached to an n_conn.
6783 - Change the contrib/tor.logrotate script so it makes the new
6784 logs as "_tor:_tor" rather than the default, which is generally
6785 "root:wheel". Fixes bug 676, reported by Serge Koksharov.
6786 - Stop using __attribute__((nonnull)) with GCC: it can give us useful
6787 warnings (occasionally), but it can also cause the compiler to
6788 eliminate error-checking code. Suggested by Peter Gutmann.
6789 - When a hidden service is giving up on an introduction point candidate
6790 that was not included in the last published rendezvous descriptor,
6791 don't reschedule publication of the next descriptor. Fixes bug 763.
6793 - Mark RendNodes, RendExcludeNodes, HiddenServiceNodes, and
6794 HiddenServiceExcludeNodes as obsolete: they never worked properly,
6795 and nobody claims to be using them. Fixes bug 754. Bugfix on
6796 0.1.0.1-rc. Patch from Christian Wilms.
6797 - Fix a small alignment and memory-wasting bug on buffer chunks.
6800 o Minor bugfixes (controller):
6801 - When closing an application-side connection because its circuit
6802 is getting torn down, generate the stream event correctly.
6803 Bugfix on 0.1.2.x. Anonymous patch.
6806 - Remove all backward-compatibility code to support relays running
6807 versions of Tor so old that they no longer work at all on the
6811 Changes in version 0.2.0.30 - 2008-07-15
6813 - Stop using __attribute__((nonnull)) with GCC: it can give us useful
6814 warnings (occasionally), but it can also cause the compiler to
6815 eliminate error-checking code. Suggested by Peter Gutmann.
6818 Changes in version 0.2.0.29-rc - 2008-07-08
6819 Tor 0.2.0.29-rc fixes two big bugs with using bridges, fixes more
6820 hidden-service performance bugs, and fixes a bunch of smaller bugs.
6823 - If you have more than one bridge but don't know their keys,
6824 you would only launch a request for the descriptor of the first one
6825 on your list. (Tor considered launching requests for the others, but
6826 found that it already had a connection on the way for $0000...0000
6827 so it didn't open another.) Bugfix on 0.2.0.x.
6828 - If you have more than one bridge but don't know their keys, and the
6829 connection to one of the bridges failed, you would cancel all
6830 pending bridge connections. (After all, they all have the same
6831 digest.) Bugfix on 0.2.0.x.
6832 - When a hidden service was trying to establish an introduction point,
6833 and Tor had built circuits preemptively for such purposes, we
6834 were ignoring all the preemptive circuits and launching a new one
6835 instead. Bugfix on 0.2.0.14-alpha.
6836 - When a hidden service was trying to establish an introduction point,
6837 and Tor *did* manage to reuse one of the preemptively built
6838 circuits, it didn't correctly remember which one it used,
6839 so it asked for another one soon after, until there were no
6840 more preemptive circuits, at which point it launched one from
6841 scratch. Bugfix on 0.0.9.x.
6842 - Make directory servers include the X-Your-Address-Is: http header in
6843 their responses even for begin_dir conns. Now clients who only
6844 ever use begin_dir connections still have a way to learn their IP
6845 address. Fixes bug 737; bugfix on 0.2.0.22-rc. Reported by goldy.
6848 - Fix a macro/CPP interaction that was confusing some compilers:
6849 some GCCs don't like #if/#endif pairs inside macro arguments.
6851 - Fix macro collision between OpenSSL 0.9.8h and Windows headers.
6852 Fixes bug 704; fix from Steven Murdoch.
6853 - When opening /dev/null in finish_daemonize(), do not pass the
6854 O_CREAT flag. Fortify was complaining, and correctly so. Fixes
6855 bug 742; fix from Michael Scherer. Bugfix on 0.0.2pre19.
6856 - Correctly detect transparent proxy support on Linux hosts that
6857 require in.h to be included before netfilter_ipv4.h. Patch
6859 - Disallow session resumption attempts during the renegotiation
6860 stage of the v2 handshake protocol. Clients should never be trying
6861 session resumption at this point, but apparently some did, in
6862 ways that caused the handshake to fail. Bugfix on 0.2.0.20-rc. Bug
6863 found by Geoff Goodell.
6866 Changes in version 0.2.1.2-alpha - 2008-06-20
6867 Tor 0.2.1.2-alpha includes a new "TestingTorNetwork" config option to
6868 make it easier to set up your own private Tor network; fixes several
6869 big bugs with using more than one bridge relay; fixes a big bug with
6870 offering hidden services quickly after Tor starts; and uses a better
6871 API for reporting potential bootstrapping problems to the controller.
6874 - New TestingTorNetwork config option to allow adjustment of
6875 previously constant values that, while reasonable, could slow
6876 bootstrapping. Implements proposal 135. Patch from Karsten.
6879 - If you have more than one bridge but don't know their digests,
6880 you would only learn a request for the descriptor of the first one
6881 on your list. (Tor considered launching requests for the others, but
6882 found that it already had a connection on the way for $0000...0000
6883 so it didn't open another.) Bugfix on 0.2.0.x.
6884 - If you have more than one bridge but don't know their digests,
6885 and the connection to one of the bridges failed, you would cancel
6886 all pending bridge connections. (After all, they all have the
6887 same digest.) Bugfix on 0.2.0.x.
6888 - When establishing a hidden service, introduction points that
6889 originate from cannibalized circuits are completely ignored and not
6890 included in rendezvous service descriptors. This might be another
6891 reason for delay in making a hidden service available. Bugfix
6892 from long ago (0.0.9.x?)
6895 - Allow OpenSSL to use dynamic locks if it wants.
6896 - When building a consensus, do not include routers that are down.
6897 This will cut down 30% to 40% on consensus size. Implements
6899 - In directory authorities' approved-routers files, allow
6900 fingerprints with or without space.
6901 - Add a "GETINFO /status/bootstrap-phase" controller option, so the
6902 controller can query our current bootstrap state in case it attaches
6903 partway through and wants to catch up.
6904 - Send an initial "Starting" bootstrap status event, so we have a
6905 state to start out in.
6908 - Asking for a conditional consensus at .../consensus/<fingerprints>
6909 would crash a dirserver if it did not already have a
6910 consensus. Bugfix on 0.2.1.1-alpha.
6911 - Clean up some macro/CPP interactions: some GCC versions don't like
6912 #if/#endif pairs inside macro arguments. Fixes bug 707. Bugfix on
6915 o Bootstrapping bugfixes (on 0.2.1.1-alpha):
6916 - Directory authorities shouldn't complain about bootstrapping
6917 problems just because they do a lot of reachability testing and
6918 some of the connection attempts fail.
6919 - Start sending "count" and "recommendation" key/value pairs in
6920 bootstrap problem status events, so the controller can hear about
6921 problems even before Tor decides they're worth reporting for sure.
6922 - If you're using bridges, generate "bootstrap problem" warnings
6923 as soon as you run out of working bridges, rather than waiting
6924 for ten failures -- which will never happen if you have less than
6926 - If we close our OR connection because there's been a circuit
6927 pending on it for too long, we were telling our bootstrap status
6928 events "REASON=NONE". Now tell them "REASON=TIMEOUT".
6931 Changes in version 0.2.1.1-alpha - 2008-06-13
6932 Tor 0.2.1.1-alpha fixes a lot of memory fragmentation problems that
6933 were making the Tor process bloat especially on Linux; makes our TLS
6934 handshake blend in better; sends "bootstrap phase" status events to
6935 the controller, so it can keep the user informed of progress (and
6936 problems) fetching directory information and establishing circuits;
6937 and adds a variety of smaller features.
6940 - More work on making our TLS handshake blend in: modify the list
6941 of ciphers advertised by OpenSSL in client mode to even more
6942 closely resemble a common web browser. We cheat a little so that
6943 we can advertise ciphers that the locally installed OpenSSL doesn't
6945 - Start sending "bootstrap phase" status events to the controller,
6946 so it can keep the user informed of progress fetching directory
6947 information and establishing circuits. Also inform the controller
6948 if we think we're stuck at a particular bootstrap phase. Implements
6950 - Resume using OpenSSL's RAND_poll() for better (and more portable)
6951 cross-platform entropy collection again. We used to use it, then
6952 stopped using it because of a bug that could crash systems that
6953 called RAND_poll when they had a lot of fds open. It looks like the
6954 bug got fixed in late 2006. Our new behavior is to call RAND_poll()
6955 at startup, and to call RAND_poll() when we reseed later only if
6956 we have a non-buggy OpenSSL version.
6959 - When we choose to abandon a new entry guard because we think our
6960 older ones might be better, close any circuits pending on that
6961 new entry guard connection. This fix should make us recover much
6962 faster when our network is down and then comes back. Bugfix on
6963 0.1.2.8-beta; found by lodger.
6965 o Memory fixes and improvements:
6966 - Add a malloc_good_size implementation to OpenBSD_malloc_linux.c,
6967 to avoid unused RAM in buffer chunks and memory pools.
6968 - Speed up parsing and cut down on memory fragmentation by using
6969 stack-style allocations for parsing directory objects. Previously,
6970 this accounted for over 40% of allocations from within Tor's code
6971 on a typical directory cache.
6972 - Use a Bloom filter rather than a digest-based set to track which
6973 descriptors we need to keep around when we're cleaning out old
6974 router descriptors. This speeds up the computation significantly,
6975 and may reduce fragmentation.
6976 - Reduce the default smartlist size from 32 to 16; it turns out that
6977 most smartlists hold around 8-12 elements tops.
6978 - Make dumpstats() log the fullness and size of openssl-internal
6980 - If the user has applied the experimental SSL_MODE_RELEASE_BUFFERS
6981 patch to their OpenSSL, turn it on to save memory on servers. This
6982 patch will (with any luck) get included in a mainline distribution
6984 - Never use OpenSSL compression: it wastes RAM and CPU trying to
6985 compress cells, which are basically all encrypted, compressed,
6989 - Stop reloading the router list from disk for no reason when we
6990 run out of reachable directory mirrors. Once upon a time reloading
6991 it would set the 'is_running' flag back to 1 for them. It hasn't
6992 done that for a long time.
6993 - In very rare situations new hidden service descriptors were
6994 published earlier than 30 seconds after the last change to the
6995 service. (We currently think that a hidden service descriptor
6996 that's been stable for 30 seconds is worth publishing.)
6999 - Allow separate log levels to be configured for different logging
7000 domains. For example, this allows one to log all notices, warnings,
7001 or errors, plus all memory management messages of level debug or
7002 higher, with: Log [MM] debug-err [*] notice-err file /var/log/tor.
7003 - Add a couple of extra warnings to --enable-gcc-warnings for GCC 4.3,
7004 and stop using a warning that had become unfixably verbose under
7006 - New --hush command-line option similar to --quiet. While --quiet
7007 disables all logging to the console on startup, --hush limits the
7008 output to messages of warning and error severity.
7009 - Servers support a new URL scheme for consensus downloads that
7010 allows the client to specify which authorities are trusted.
7011 The server then only sends the consensus if the client will trust
7012 it. Otherwise a 404 error is sent back. Clients use this
7013 new scheme when the server supports it (meaning it's running
7014 0.2.1.1-alpha or later). Implements proposal 134.
7015 - New configure/torrc options (--enable-geoip-stats,
7016 DirRecordUsageByCountry) to record how many IPs we've served
7017 directory info to in each country code, how many status documents
7018 total we've sent to each country code, and what share of the total
7019 directory requests we should expect to see.
7020 - Use the TLS1 hostname extension to more closely resemble browser
7022 - Lots of new unit tests.
7023 - Add a macro to implement the common pattern of iterating through
7024 two parallel lists in lockstep.
7027 Changes in version 0.2.0.28-rc - 2008-06-13
7028 Tor 0.2.0.28-rc fixes an anonymity-related bug, fixes a hidden-service
7029 performance bug, and fixes a bunch of smaller bugs.
7032 - Fix a bug where, when we were choosing the 'end stream reason' to
7033 put in our relay end cell that we send to the exit relay, Tor
7034 clients on Windows were sometimes sending the wrong 'reason'. The
7035 anonymity problem is that exit relays may be able to guess whether
7036 the client is running Windows, thus helping partition the anonymity
7037 set. Down the road we should stop sending reasons to exit relays,
7038 or otherwise prevent future versions of this bug.
7041 - While setting up a hidden service, some valid introduction circuits
7042 were overlooked and abandoned. This might be the reason for
7043 the long delay in making a hidden service available. Bugfix on
7047 - Update to the "June 9 2008" ip-to-country file.
7048 - Run 'make test' as part of 'make dist', so we stop releasing so
7049 many development snapshots that fail their unit tests.
7052 - When we're checking if we have enough dir info for each relay
7053 to begin establishing circuits, make sure that we actually have
7054 the descriptor listed in the consensus, not just any descriptor.
7056 - Bridge relays no longer print "xx=0" in their extrainfo document
7057 for every single country code in the geoip db. Bugfix on
7059 - Only warn when we fail to load the geoip file if we were planning to
7060 include geoip stats in our extrainfo document. Bugfix on 0.2.0.27-rc.
7061 - If we change our MaxAdvertisedBandwidth and then reload torrc,
7062 Tor won't realize it should publish a new relay descriptor. Fixes
7063 bug 688, reported by mfr. Bugfix on 0.1.2.x.
7064 - When we haven't had any application requests lately, don't bother
7065 logging that we have expired a bunch of descriptors. Bugfix
7067 - Make relay cells written on a connection count as non-padding when
7068 tracking how long a connection has been in use. Bugfix on
7069 0.2.0.1-alpha. Spotted by lodger.
7070 - Fix unit tests in 0.2.0.27-rc.
7071 - Fix compile on Windows.
7074 Changes in version 0.2.0.27-rc - 2008-06-03
7075 Tor 0.2.0.27-rc adds a few features we left out of the earlier
7076 release candidates. In particular, we now include an IP-to-country
7077 GeoIP database, so controllers can easily look up what country a
7078 given relay is in, and so bridge relays can give us some sanitized
7079 summaries about which countries are making use of bridges. (See proposal
7080 126-geoip-fetching.txt for details.)
7083 - Include an IP-to-country GeoIP file in the tarball, so bridge
7084 relays can report sanitized summaries of the usage they're seeing.
7087 - Add a "PURPOSE=" argument to "STREAM NEW" events, as suggested by
7088 Robert Hogan. Fixes the first part of bug 681.
7089 - Make bridge authorities never serve extrainfo docs.
7090 - Add support to detect Libevent versions in the 1.4.x series
7092 - Fix build on gcc 4.3 with --enable-gcc-warnings set.
7093 - Include a new contrib/tor-exit-notice.html file that exit relay
7094 operators can put on their website to help reduce abuse queries.
7097 - When tunneling an encrypted directory connection, and its first
7098 circuit fails, do not leave it unattached and ask the controller
7099 to deal. Fixes the second part of bug 681.
7100 - Make bridge authorities correctly expire old extrainfo documents
7104 Changes in version 0.2.0.26-rc - 2008-05-13
7105 Tor 0.2.0.26-rc fixes a major security vulnerability caused by a bug
7106 in Debian's OpenSSL packages. All users running any 0.2.0.x version
7107 should upgrade, whether they're running Debian or not.
7109 o Major security fixes:
7110 - Use new V3 directory authority keys on the tor26, gabelmoo, and
7111 moria1 V3 directory authorities. The old keys were generated with
7112 a vulnerable version of Debian's OpenSSL package, and must be
7113 considered compromised. Other authorities' keys were not generated
7114 with an affected version of OpenSSL.
7117 - List authority signatures as "unrecognized" based on DirServer
7118 lines, not on cert cache. Bugfix on 0.2.0.x.
7121 - Add a new V3AuthUseLegacyKey option to make it easier for
7122 authorities to change their identity keys if they have to.
7125 Changes in version 0.2.0.25-rc - 2008-04-23
7126 Tor 0.2.0.25-rc makes Tor work again on OS X and certain BSDs.
7129 - Remember to initialize threading before initializing logging.
7130 Otherwise, many BSD-family implementations will crash hard on
7131 startup. Fixes bug 671. Bugfix on 0.2.0.24-rc.
7134 - Authorities correctly free policies on bad servers on
7135 exit. Fixes bug 672. Bugfix on 0.2.0.x.
7138 Changes in version 0.2.0.24-rc - 2008-04-22
7139 Tor 0.2.0.24-rc adds dizum (run by Alex de Joode) as the new sixth
7140 v3 directory authority, makes relays with dynamic IP addresses and no
7141 DirPort notice more quickly when their IP address changes, fixes a few
7142 rare crashes and memory leaks, and fixes a few other miscellaneous bugs.
7144 o New directory authorities:
7145 - Take lefkada out of the list of v3 directory authorities, since
7146 it has been down for months.
7147 - Set up dizum (run by Alex de Joode) as the new sixth v3 directory
7151 - Detect address changes more quickly on non-directory mirror
7152 relays. Bugfix on 0.2.0.18-alpha; fixes bug 652.
7154 o Minor features (security):
7155 - Reject requests for reverse-dns lookup of names that are in
7156 a private address space. Patch from lodger.
7157 - Non-exit relays no longer allow DNS requests. Fixes bug 619. Patch
7160 o Minor bugfixes (crashes):
7161 - Avoid a rare assert that can trigger when Tor doesn't have much
7162 directory information yet and it tries to fetch a v2 hidden
7163 service descriptor. Fixes bug 651, reported by nwf.
7164 - Initialize log mutex before initializing dmalloc. Otherwise,
7165 running with dmalloc would crash. Bugfix on 0.2.0.x-alpha.
7166 - Use recursive pthread mutexes in order to avoid deadlock when
7167 logging debug-level messages to a controller. Bug spotted by nwf,
7168 bugfix on 0.2.0.16-alpha.
7170 o Minor bugfixes (resource management):
7171 - Keep address policies from leaking memory: start their refcount
7172 at 1, not 2. Bugfix on 0.2.0.16-alpha.
7173 - Free authority certificates on exit, so they don't look like memory
7174 leaks. Bugfix on 0.2.0.19-alpha.
7175 - Free static hashtables for policy maps and for TLS connections on
7176 shutdown, so they don't look like memory leaks. Bugfix on 0.2.0.x.
7177 - Avoid allocating extra space when computing consensuses on 64-bit
7178 platforms. Bug spotted by aakova.
7180 o Minor bugfixes (misc):
7181 - Do not read the configuration file when we've only been told to
7182 generate a password hash. Fixes bug 643. Bugfix on 0.0.9pre5. Fix
7183 based on patch from Sebastian Hahn.
7184 - Exit relays that are used as a client can now reach themselves
7185 using the .exit notation, rather than just launching an infinite
7186 pile of circuits. Fixes bug 641. Reported by Sebastian Hahn.
7187 - When attempting to open a logfile fails, tell us why.
7188 - Fix a dumb bug that was preventing us from knowing that we should
7189 preemptively build circuits to handle expected directory requests.
7190 Fixes bug 660. Bugfix on 0.1.2.x.
7191 - Warn less verbosely about clock skew from netinfo cells from
7192 untrusted sources. Fixes bug 663.
7193 - Make controller stream events for DNS requests more consistent,
7194 by adding "new stream" events for DNS requests, and removing
7195 spurious "stream closed" events" for cached reverse resolves.
7196 Patch from mwenge. Fixes bug 646.
7197 - Correctly notify one-hop connections when a circuit build has
7198 failed. Possible fix for bug 669. Found by lodger.
7201 Changes in version 0.2.0.23-rc - 2008-03-24
7202 Tor 0.2.0.23-rc is the fourth release candidate for the 0.2.0 series. It
7203 makes bootstrapping faster if the first directory mirror you contact
7204 is down. The bundles also include the new Vidalia 0.1.2 release.
7207 - When a tunneled directory request is made to a directory server
7208 that's down, notice after 30 seconds rather than 120 seconds. Also,
7209 fail any begindir streams that are pending on it, so they can
7210 retry elsewhere. This was causing multi-minute delays on bootstrap.
7213 Changes in version 0.2.0.22-rc - 2008-03-18
7214 Tor 0.2.0.22-rc is the third release candidate for the 0.2.0 series. It
7215 enables encrypted directory connections by default for non-relays, fixes
7216 some broken TLS behavior we added in 0.2.0.20-rc, and resolves many
7217 other bugs. The bundles also include Vidalia 0.1.1 and Torbutton 1.1.17.
7220 - Enable encrypted directory connections by default for non-relays,
7221 so censor tools that block Tor directory connections based on their
7222 plaintext patterns will no longer work. This means Tor works in
7223 certain censored countries by default again.
7226 - Make sure servers always request certificates from clients during
7227 TLS renegotiation. Reported by lodger; bugfix on 0.2.0.20-rc.
7228 - Do not enter a CPU-eating loop when a connection is closed in
7229 the middle of client-side TLS renegotiation. Fixes bug 622. Bug
7230 diagnosed by lodger; bugfix on 0.2.0.20-rc.
7231 - Fix assertion failure that could occur when a blocked circuit
7232 became unblocked, and it had pending client DNS requests. Bugfix
7233 on 0.2.0.1-alpha. Fixes bug 632.
7235 o Minor bugfixes (on 0.1.2.x):
7236 - Generate "STATUS_SERVER" events rather than misspelled
7237 "STATUS_SEVER" events. Caught by mwenge.
7238 - When counting the number of bytes written on a TLS connection,
7239 look at the BIO actually used for writing to the network, not
7240 at the BIO used (sometimes) to buffer data for the network.
7241 Looking at different BIOs could result in write counts on the
7242 order of ULONG_MAX. Fixes bug 614.
7243 - On Windows, correctly detect errors when listing the contents of
7244 a directory. Fix from lodger.
7246 o Minor bugfixes (on 0.2.0.x):
7247 - Downgrade "sslv3 alert handshake failure" message to INFO.
7248 - If we set RelayBandwidthRate and RelayBandwidthBurst very high but
7249 left BandwidthRate and BandwidthBurst at the default, we would be
7250 silently limited by those defaults. Now raise them to match the
7251 RelayBandwidth* values.
7252 - Fix the SVK version detection logic to work correctly on a branch.
7253 - Make --enable-openbsd-malloc work correctly on Linux with alpha
7254 CPUs. Fixes bug 625.
7255 - Logging functions now check that the passed severity is sane.
7256 - Use proper log levels in the testsuite call of
7257 get_interface_address6().
7258 - When using a nonstandard malloc, do not use the platform values for
7259 HAVE_MALLOC_GOOD_SIZE or HAVE_MALLOC_USABLE_SIZE.
7260 - Make the openbsd malloc code use 8k pages on alpha CPUs and
7262 - Detect mismatched page sizes when using --enable-openbsd-malloc.
7263 - Avoid double-marked-for-close warning when certain kinds of invalid
7264 .in-addr.arpa addresses are passed to the DNSPort. Part of a fix
7265 for bug 617. Bugfix on 0.2.0.1-alpha.
7266 - Make sure that the "NULL-means-reject *:*" convention is followed by
7267 all the policy manipulation functions, avoiding some possible crash
7268 bugs. Bug found by lodger. Bugfix on 0.2.0.16-alpha.
7269 - Fix the implementation of ClientDNSRejectInternalAddresses so that it
7270 actually works, and doesn't warn about every single reverse lookup.
7271 Fixes the other part of bug 617. Bugfix on 0.2.0.1-alpha.
7274 - Only log guard node status when guard node status has changed.
7275 - Downgrade the 3 most common "INFO" messages to "DEBUG". This will
7276 make "INFO" 75% less verbose.
7279 Changes in version 0.2.0.21-rc - 2008-03-02
7280 Tor 0.2.0.21-rc is the second release candidate for the 0.2.0 series. It
7281 makes Tor work well with Vidalia again, fixes a rare assert bug,
7282 and fixes a pair of more minor bugs. The bundles also include Vidalia
7283 0.1.0 and Torbutton 1.1.16.
7286 - The control port should declare that it requires password auth
7287 when HashedControlSessionPassword is set too. Patch from Matt Edman;
7288 bugfix on 0.2.0.20-rc. Fixes bug 615.
7289 - Downgrade assert in connection_buckets_decrement() to a log message.
7290 This may help us solve bug 614, and in any case will make its
7291 symptoms less severe. Bugfix on 0.2.0.20-rc. Reported by fredzupy.
7292 - We were sometimes miscounting the number of bytes read from the
7293 network, causing our rate limiting to not be followed exactly.
7294 Bugfix on 0.2.0.16-alpha. Reported by lodger.
7297 - Fix compilation with OpenSSL 0.9.8 and 0.9.8a. All other supported
7298 OpenSSL versions should have been working fine. Diagnosis and patch
7299 from lodger, Karsten Loesing, and Sebastian Hahn. Fixes bug 616.
7300 Bugfix on 0.2.0.20-rc.
7303 Changes in version 0.2.0.20-rc - 2008-02-24
7304 Tor 0.2.0.20-rc is the first release candidate for the 0.2.0 series. It
7305 makes more progress towards normalizing Tor's TLS handshake, makes
7306 hidden services work better again, helps relays bootstrap if they don't
7307 know their IP address, adds optional support for linking in openbsd's
7308 allocator or tcmalloc, allows really fast relays to scale past 15000
7309 sockets, and fixes a bunch of minor bugs reported by Veracode.
7312 - Enable the revised TLS handshake based on the one designed by
7313 Steven Murdoch in proposal 124, as revised in proposal 130. It
7314 includes version negotiation for OR connections as described in
7315 proposal 105. The new handshake is meant to be harder for censors
7316 to fingerprint, and it adds the ability to detect certain kinds of
7317 man-in-the-middle traffic analysis attacks. The version negotiation
7318 feature will allow us to improve Tor's link protocol more safely
7320 - Choose which bridge to use proportional to its advertised bandwidth,
7321 rather than uniformly at random. This should speed up Tor for
7322 bridge users. Also do this for people who set StrictEntryNodes.
7323 - When a TrackHostExits-chosen exit fails too many times in a row,
7324 stop using it. Bugfix on 0.1.2.x; fixes bug 437.
7327 - Resolved problems with (re-)fetching hidden service descriptors.
7328 Patch from Karsten Loesing; fixes problems with 0.2.0.18-alpha
7330 - If we only ever used Tor for hidden service lookups or posts, we
7331 would stop building circuits and start refusing connections after
7332 24 hours, since we falsely believed that Tor was dormant. Reported
7333 by nwf; bugfix on 0.1.2.x.
7334 - Servers that don't know their own IP address should go to the
7335 authorities for their first directory fetch, even if their DirPort
7336 is off or if they don't know they're reachable yet. This will help
7337 them bootstrap better. Bugfix on 0.2.0.18-alpha; fixes bug 609.
7338 - When counting the number of open sockets, count not only the number
7339 of sockets we have received from the socket() call, but also
7340 the number we've gotten from accept() and socketpair(). This bug
7341 made us fail to count all sockets that we were using for incoming
7342 connections. Bugfix on 0.2.0.x.
7343 - Fix code used to find strings within buffers, when those strings
7344 are not in the first chunk of the buffer. Bugfix on 0.2.0.x.
7345 - Fix potential segfault when parsing HTTP headers. Bugfix on 0.2.0.x.
7346 - Add a new __HashedControlSessionPassword option for controllers
7347 to use for one-off session password hashes that shouldn't get
7348 saved to disk by SAVECONF --- Vidalia users were accumulating a
7349 pile of HashedControlPassword lines in their torrc files, one for
7350 each time they had restarted Tor and then clicked Save. Make Tor
7351 automatically convert "HashedControlPassword" to this new option but
7352 only when it's given on the command line. Partial fix for bug 586.
7354 o Minor features (performance):
7355 - Tune parameters for cell pool allocation to minimize amount of
7357 - Add OpenBSD malloc code from phk as an optional malloc
7358 replacement on Linux: some glibc libraries do very poorly
7359 with Tor's memory allocation patterns. Pass
7360 --enable-openbsd-malloc to get the replacement malloc code.
7361 - Add a --with-tcmalloc option to the configure script to link
7362 against tcmalloc (if present). Does not yet search for
7363 non-system include paths.
7364 - Stop imposing an arbitrary maximum on the number of file descriptors
7365 used for busy servers. Bug reported by Olaf Selke; patch from
7368 o Minor features (other):
7369 - When SafeLogging is disabled, log addresses along with all TLS
7371 - When building with --enable-gcc-warnings, check for whether Apple's
7372 warning "-Wshorten-64-to-32" is available.
7373 - Add a --passphrase-fd argument to the tor-gencert command for
7376 o Minor bugfixes (memory leaks and code problems):
7377 - We were leaking a file descriptor if Tor started with a zero-length
7378 cached-descriptors file. Patch by freddy77; bugfix on 0.1.2.
7379 - Detect size overflow in zlib code. Reported by Justin Ferguson and
7381 - We were comparing the raw BridgePassword entry with a base64'ed
7382 version of it, when handling a "/tor/networkstatus-bridges"
7383 directory request. Now compare correctly. Noticed by Veracode.
7384 - Recover from bad tracked-since value in MTBF-history file.
7386 - Alter the code that tries to recover from unhandled write
7387 errors, to not try to flush onto a socket that's given us
7388 unhandled errors. Bugfix on 0.1.2.x.
7389 - Make Unix controlsockets work correctly on OpenBSD. Patch from
7390 tup. Bugfix on 0.2.0.3-alpha.
7392 o Minor bugfixes (other):
7393 - If we have an extra-info document for our server, always make
7394 it available on the control port, even if we haven't gotten
7395 a copy of it from an authority yet. Patch from mwenge.
7396 - Log the correct memory chunk sizes for empty RAM chunks in mempool.c.
7397 - Directory mirrors no longer include a guess at the client's IP
7398 address if the connection appears to be coming from the same /24
7399 network; it was producing too many wrong guesses.
7400 - Make the new hidden service code respect the SafeLogging setting.
7401 Bugfix on 0.2.0.x. Patch from Karsten.
7402 - When starting as an authority, do not overwrite all certificates
7403 cached from other authorities. Bugfix on 0.2.0.x. Fixes bug 606.
7404 - If we're trying to flush the last bytes on a connection (for
7405 example, when answering a directory request), reset the
7406 time-to-give-up timeout every time we manage to write something
7407 on the socket. Bugfix on 0.1.2.x.
7408 - Change the behavior of "getinfo status/good-server-descriptor"
7409 so it doesn't return failure when any authority disappears.
7410 - Even though the man page said that "TrackHostExits ." should
7411 work, nobody had ever implemented it. Bugfix on 0.1.0.x.
7412 - Report TLS "zero return" case as a "clean close" and "IO error"
7413 as a "close". Stop calling closes "unexpected closes": existing
7414 Tors don't use SSL_close(), so having a connection close without
7415 the TLS shutdown handshake is hardly unexpected.
7416 - Send NAMESERVER_STATUS messages for a single failed nameserver
7419 o Code simplifications and refactoring:
7420 - Remove the tor_strpartition function: its logic was confused,
7421 and it was only used for one thing that could be implemented far
7425 Changes in version 0.2.0.19-alpha - 2008-02-09
7426 Tor 0.2.0.19-alpha makes more progress towards normalizing Tor's TLS
7427 handshake, makes path selection for relays more secure and IP address
7428 guessing more robust, and generally fixes a lot of bugs in preparation
7429 for calling the 0.2.0 branch stable.
7432 - Do not include recognizeable strings in the commonname part of
7433 Tor's x509 certificates.
7436 - If we're a relay, avoid picking ourselves as an introduction point,
7437 a rendezvous point, or as the final hop for internal circuits. Bug
7438 reported by taranis and lodger. Bugfix on 0.1.2.x.
7439 - Patch from "Andrew S. Lists" to catch when we contact a directory
7440 mirror at IP address X and he says we look like we're coming from
7441 IP address X. Bugfix on 0.1.2.x.
7443 o Minor features (security):
7444 - Be more paranoid about overwriting sensitive memory on free(),
7445 as a defensive programming tactic to ensure forward secrecy.
7447 o Minor features (directory authority):
7448 - Actually validate the options passed to AuthDirReject,
7449 AuthDirInvalid, AuthDirBadDir, and AuthDirBadExit.
7450 - Reject router descriptors with out-of-range bandwidthcapacity or
7451 bandwidthburst values.
7453 o Minor features (controller):
7454 - Reject controller commands over 1MB in length. This keeps rogue
7455 processes from running us out of memory.
7457 o Minor features (misc):
7458 - Give more descriptive well-formedness errors for out-of-range
7459 hidden service descriptor/protocol versions.
7460 - Make memory debugging information describe more about history
7461 of cell allocation, so we can help reduce our memory use.
7463 o Deprecated features (controller):
7464 - The status/version/num-versioning and status/version/num-concurring
7465 GETINFO options are no longer useful in the v3 directory protocol:
7466 treat them as deprecated, and warn when they're used.
7469 - When our consensus networkstatus has been expired for a while, stop
7470 being willing to build circuits using it. Fixes bug 401. Bugfix
7472 - Directory caches now fetch certificates from all authorities
7473 listed in a networkstatus consensus, even when they do not
7474 recognize them. Fixes bug 571. Bugfix on 0.2.0.x.
7475 - When connecting to a bridge without specifying its key, insert
7476 the connection into the identity-to-connection map as soon as
7477 a key is learned. Fixes bug 574. Bugfix on 0.2.0.x.
7478 - Detect versions of OS X where malloc_good_size() is present in the
7479 library but never actually declared. Resolves bug 587. Bugfix
7481 - Stop incorrectly truncating zlib responses to directory authority
7482 signature download requests. Fixes bug 593. Bugfix on 0.2.0.x.
7483 - Stop recommending that every server operator send mail to tor-ops.
7484 Resolves bug 597. Bugfix on 0.1.2.x.
7485 - Don't trigger an assert if we start a directory authority with a
7486 private IP address (like 127.0.0.1).
7487 - Avoid possible failures when generating a directory with routers
7488 with over-long versions strings, or too many flags set. Bugfix
7490 - If an attempt to launch a DNS resolve request over the control
7491 port fails because we have overrun the limit on the number of
7492 connections, tell the controller that the request has failed.
7493 - Avoid using too little bandwidth when our clock skips a few
7494 seconds. Bugfix on 0.1.2.x.
7495 - Fix shell error when warning about missing packages in configure
7496 script, on Fedora or Red Hat machines. Bugfix on 0.2.0.x.
7497 - Do not become confused when receiving a spurious VERSIONS-like
7498 cell from a confused v1 client. Bugfix on 0.2.0.x.
7499 - Re-fetch v2 (as well as v0) rendezvous descriptors when all
7500 introduction points for a hidden service have failed. Patch from
7501 Karsten Loesing. Bugfix on 0.2.0.x.
7503 o Code simplifications and refactoring:
7504 - Remove some needless generality from cpuworker code, for improved
7506 - Stop overloading the circuit_t.onionskin field for both "onionskin
7507 from a CREATE cell that we are waiting for a cpuworker to be
7508 assigned" and "onionskin from an EXTEND cell that we are going to
7509 send to an OR as soon as we are connected". Might help with bug 600.
7510 - Add an in-place version of aes_crypt() so that we can avoid doing a
7511 needless memcpy() call on each cell payload.
7514 Changes in version 0.2.0.18-alpha - 2008-01-25
7515 Tor 0.2.0.18-alpha adds a sixth v3 directory authority run by CCC,
7516 fixes a big memory leak in 0.2.0.17-alpha, and adds new config options
7517 that can warn or reject connections to ports generally associated with
7518 vulnerable-plaintext protocols.
7520 o New directory authorities:
7521 - Set up dannenberg (run by CCC) as the sixth v3 directory
7525 - Fix a major memory leak when attempting to use the v2 TLS
7526 handshake code. Bugfix on 0.2.0.x; fixes bug 589.
7527 - We accidentally enabled the under-development v2 TLS handshake
7528 code, which was causing log entries like "TLS error while
7529 renegotiating handshake". Disable it again. Resolves bug 590.
7530 - We were computing the wrong Content-Length: header for directory
7531 responses that need to be compressed on the fly, causing clients
7532 asking for those items to always fail. Bugfix on 0.2.0.x; partially
7536 - Avoid going directly to the directory authorities even if you're a
7537 relay, if you haven't found yourself reachable yet or if you've
7538 decided not to advertise your dirport yet. Addresses bug 556.
7539 - If we've gone 12 hours since our last bandwidth check, and we
7540 estimate we have less than 50KB bandwidth capacity but we could
7541 handle more, do another bandwidth test.
7542 - New config options WarnPlaintextPorts and RejectPlaintextPorts so
7543 Tor can warn and/or refuse connections to ports commonly used with
7544 vulnerable-plaintext protocols. Currently we warn on ports 23,
7545 109, 110, and 143, but we don't reject any.
7548 - When we setconf ClientOnly to 1, close any current OR and Dir
7549 listeners. Reported by mwenge.
7550 - When we get a consensus that's been signed by more people than
7551 we expect, don't log about it; it's not a big deal. Reported
7555 - Don't answer "/tor/networkstatus-bridges" directory requests if
7556 the request isn't encrypted.
7557 - Make "ClientOnly 1" config option disable directory ports too.
7558 - Patches from Karsten Loesing to make v2 hidden services more
7559 robust: work even when there aren't enough HSDir relays available;
7560 retry when a v2 rend desc fetch fails; but don't retry if we
7561 already have a usable v0 rend desc.
7564 Changes in version 0.2.0.17-alpha - 2008-01-17
7565 Tor 0.2.0.17-alpha makes the tarball build cleanly again (whoops).
7568 - Make the tor-gencert man page get included correctly in the tarball.
7571 Changes in version 0.2.0.16-alpha - 2008-01-17
7572 Tor 0.2.0.16-alpha adds a fifth v3 directory authority run by Karsten
7573 Loesing, and generally cleans up a lot of features and minor bugs.
7575 o New directory authorities:
7576 - Set up gabelmoo (run by Karsten Loesing) as the fifth v3 directory
7579 o Major performance improvements:
7580 - Switch our old ring buffer implementation for one more like that
7581 used by free Unix kernels. The wasted space in a buffer with 1mb
7582 of data will now be more like 8k than 1mb. The new implementation
7583 also avoids realloc();realloc(); patterns that can contribute to
7584 memory fragmentation.
7587 - Configuration files now accept C-style strings as values. This
7588 helps encode characters not allowed in the current configuration
7589 file format, such as newline or #. Addresses bug 557.
7590 - Although we fixed bug 539 (where servers would send HTTP status 503
7591 responses _and_ send a body too), there are still servers out
7592 there that haven't upgraded. Therefore, make clients parse such
7593 bodies when they receive them.
7594 - When we're not serving v2 directory information, there is no reason
7595 to actually keep any around. Remove the obsolete files and directory
7596 on startup if they are very old and we aren't going to serve them.
7598 o Minor performance improvements:
7599 - Reference-count and share copies of address policy entries; only 5%
7600 of them were actually distinct.
7601 - Never walk through the list of logs if we know that no log is
7602 interested in a given message.
7605 - When an authority has not signed a consensus, do not try to
7606 download a nonexistent "certificate with key 00000000". Bugfix
7607 on 0.2.0.x. Fixes bug 569.
7608 - Fix a rare assert error when we're closing one of our threads:
7609 use a mutex to protect the list of logs, so we never write to the
7610 list as it's being freed. Bugfix on 0.1.2.x. Fixes the very rare
7611 bug 575, which is kind of the revenge of bug 222.
7612 - Patch from Karsten Loesing to complain less at both the client
7613 and the relay when a relay used to have the HSDir flag but doesn't
7614 anymore, and we try to upload a hidden service descriptor.
7615 - Stop leaking one cert per TLS context. Fixes bug 582. Bugfix on
7617 - Do not try to download missing certificates until we have tried
7618 to check our fallback consensus. Fixes bug 583.
7619 - Make bridges round reported GeoIP stats info up to the nearest
7620 estimate, not down. Now we can distinguish between "0 people from
7621 this country" and "1 person from this country".
7622 - Avoid a spurious free on base64 failure. Bugfix on 0.1.2.
7623 - Avoid possible segfault if key generation fails in
7624 crypto_pk_hybrid_encrypt. Bugfix on 0.2.0.
7625 - Avoid segfault in the case where a badly behaved v2 versioning
7626 directory sends a signed networkstatus with missing client-versions.
7628 - Avoid segfaults on certain complex invocations of
7629 router_get_by_hexdigest(). Bugfix on 0.1.2.
7630 - Correct bad index on array access in parse_http_time(). Bugfix
7632 - Fix possible bug in vote generation when server versions are present
7633 but client versions are not.
7634 - Fix rare bug on REDIRECTSTREAM control command when called with no
7635 port set: it could erroneously report an error when none had
7637 - Avoid bogus crash-prone, leak-prone tor_realloc when we're
7638 compressing large objects and find ourselves with more than 4k
7639 left over. Bugfix on 0.2.0.
7640 - Fix a small memory leak when setting up a hidden service.
7641 - Fix a few memory leaks that could in theory happen under bizarre
7643 - Fix an assert if we post a general-purpose descriptor via the
7644 control port but that descriptor isn't mentioned in our current
7645 network consensus. Bug reported by Jon McLachlan; bugfix on
7648 o Minor features (controller):
7649 - Get NS events working again. Patch from tup.
7650 - The GETCONF command now escapes and quotes configuration values
7651 that don't otherwise fit into the torrc file.
7652 - The SETCONF command now handles quoted values correctly.
7654 o Minor features (directory authorities):
7655 - New configuration options to override default maximum number of
7656 servers allowed on a single IP address. This is important for
7657 running a test network on a single host.
7658 - Actually implement the -s option to tor-gencert.
7659 - Add a manual page for tor-gencert.
7661 o Minor features (bridges):
7662 - Bridge authorities no longer serve bridge descriptors over
7663 unencrypted connections.
7665 o Minor features (other):
7666 - Add hidden services and DNSPorts to the list of things that make
7667 Tor accept that it has running ports. Change starting Tor with no
7668 ports from a fatal error to a warning; we might change it back if
7669 this turns out to confuse anybody. Fixes bug 579.
7672 Changes in version 0.1.2.19 - 2008-01-17
7673 Tor 0.1.2.19 fixes a huge memory leak on exit relays, makes the default
7674 exit policy a little bit more conservative so it's safer to run an
7675 exit relay on a home system, and fixes a variety of smaller issues.
7678 - Exit policies now reject connections that are addressed to a
7679 relay's public (external) IP address too, unless
7680 ExitPolicyRejectPrivate is turned off. We do this because too
7681 many relays are running nearby to services that trust them based
7685 - When the clock jumps forward a lot, do not allow the bandwidth
7686 buckets to become negative. Fixes bug 544.
7687 - Fix a memory leak on exit relays; we were leaking a cached_resolve_t
7688 on every successful resolve. Reported by Mike Perry.
7689 - Purge old entries from the "rephist" database and the hidden
7690 service descriptor database even when DirPort is zero.
7691 - Stop thinking that 0.1.2.x directory servers can handle "begin_dir"
7692 requests. Should ease bugs 406 and 419 where 0.1.2.x relays are
7693 crashing or mis-answering these requests.
7694 - When we decide to send a 503 response to a request for servers, do
7695 not then also send the server descriptors: this defeats the whole
7696 purpose. Fixes bug 539.
7699 - Changing the ExitPolicyRejectPrivate setting should cause us to
7700 rebuild our server descriptor.
7701 - Fix handling of hex nicknames when answering controller requests for
7702 networkstatus by name, or when deciding whether to warn about
7703 unknown routers in a config option. (Patch from mwenge.)
7704 - Fix a couple of hard-to-trigger autoconf problems that could result
7705 in really weird results on platforms whose sys/types.h files define
7706 nonstandard integer types.
7707 - Don't try to create the datadir when running --verify-config or
7708 --hash-password. Resolves bug 540.
7709 - If we were having problems getting a particular descriptor from the
7710 directory caches, and then we learned about a new descriptor for
7711 that router, we weren't resetting our failure count. Reported
7713 - Although we fixed bug 539 (where servers would send HTTP status 503
7714 responses _and_ send a body too), there are still servers out there
7715 that haven't upgraded. Therefore, make clients parse such bodies
7716 when they receive them.
7717 - Run correctly on systems where rlim_t is larger than unsigned long.
7718 This includes some 64-bit systems.
7719 - Run correctly on platforms (like some versions of OS X 10.5) where
7720 the real limit for number of open files is OPEN_FILES, not rlim_max
7721 from getrlimit(RLIMIT_NOFILES).
7722 - Avoid a spurious free on base64 failure.
7723 - Avoid segfaults on certain complex invocations of
7724 router_get_by_hexdigest().
7725 - Fix rare bug on REDIRECTSTREAM control command when called with no
7726 port set: it could erroneously report an error when none had
7730 Changes in version 0.2.0.15-alpha - 2007-12-25
7731 Tor 0.2.0.14-alpha and 0.2.0.15-alpha fix a bunch of bugs with the
7732 features added in 0.2.0.13-alpha.
7735 - Fix several remotely triggerable asserts based on DirPort requests
7736 for a v2 or v3 networkstatus object before we were prepared. This
7737 was particularly bad for 0.2.0.13 and later bridge relays, who
7738 would never have a v2 networkstatus and would thus always crash
7739 when used. Bugfixes on 0.2.0.x.
7740 - Estimate the v3 networkstatus size more accurately, rather than
7741 estimating it at zero bytes and giving it artificially high priority
7742 compared to other directory requests. Bugfix on 0.2.0.x.
7745 - Fix configure.in logic for cross-compilation.
7746 - When we load a bridge descriptor from the cache, and it was
7747 previously unreachable, mark it as retriable so we won't just
7748 ignore it. Also, try fetching a new copy immediately. Bugfixes
7750 - The bridge GeoIP stats were counting other relays, for example
7751 self-reachability and authority-reachability tests.
7754 - Support compilation to target iPhone; patch from cjacker huang.
7755 To build for iPhone, pass the --enable-iphone option to configure.
7758 Changes in version 0.2.0.14-alpha - 2007-12-23
7760 - Fix a crash on startup if you install Tor 0.2.0.13-alpha fresh
7761 without a datadirectory from a previous Tor install. Reported
7763 - Fix a crash when we fetch a descriptor that turns out to be
7764 unexpected (it used to be in our networkstatus when we started
7765 fetching it, but it isn't in our current networkstatus), and we
7766 aren't using bridges. Bugfix on 0.2.0.x.
7767 - Fix a crash when accessing hidden services: it would work the first
7768 time you use a given introduction point for your service, but
7769 on subsequent requests we'd be using garbage memory. Fixed by
7770 Karsten Loesing. Bugfix on 0.2.0.13-alpha.
7771 - Fix a crash when we load a bridge descriptor from disk but we don't
7772 currently have a Bridge line for it in our torrc. Bugfix on
7776 - If bridge authorities set BridgePassword, they will serve a
7777 snapshot of known bridge routerstatuses from their DirPort to
7778 anybody who knows that password. Unset by default.
7781 - Make the unit tests build again.
7782 - Make "GETINFO/desc-annotations/id/<OR digest>" actually work.
7783 - Make PublishServerDescriptor default to 1, so the default doesn't
7784 have to change as we invent new directory protocol versions.
7785 - Fix test for rlim_t on OSX 10.3: sys/resource.h doesn't want to
7786 be included unless sys/time.h is already included. Fixes
7787 bug 553. Bugfix on 0.2.0.x.
7788 - If we receive a general-purpose descriptor and then receive an
7789 identical bridge-purpose descriptor soon after, don't discard
7790 the next one as a duplicate.
7793 - If BridgeRelay is set to 1, then the default for
7794 PublishServerDescriptor is now "bridge" rather than "v2,v3".
7795 - If the user sets RelayBandwidthRate but doesn't set
7796 RelayBandwidthBurst, then make them equal rather than erroring out.
7799 Changes in version 0.2.0.13-alpha - 2007-12-21
7800 Tor 0.2.0.13-alpha adds a fourth v3 directory authority run by Geoff
7801 Goodell, fixes many more bugs, and adds a lot of infrastructure for
7804 o New directory authorities:
7805 - Set up lefkada (run by Geoff Goodell) as the fourth v3 directory
7809 - Only update guard status (usable / not usable) once we have
7810 enough directory information. This was causing us to always pick
7811 two new guards on startup (bugfix on 0.2.0.9-alpha), and it was
7812 causing us to discard all our guards on startup if we hadn't been
7813 running for a few weeks (bugfix on 0.1.2.x). Fixes bug 448.
7814 - Purge old entries from the "rephist" database and the hidden
7815 service descriptor databases even when DirPort is zero. Bugfix
7817 - We were ignoring our RelayBandwidthRate for the first 30 seconds
7818 after opening a circuit -- even a relayed circuit. Bugfix on
7820 - Stop thinking that 0.1.2.x directory servers can handle "begin_dir"
7821 requests. Should ease bugs 406 and 419 where 0.1.2.x relays are
7822 crashing or mis-answering these types of requests.
7823 - Relays were publishing their server descriptor to v1 and v2
7824 directory authorities, but they didn't try publishing to v3-only
7825 authorities. Fix this; and also stop publishing to v1 authorities.
7827 - When we were reading router descriptors from cache, we were ignoring
7828 the annotations -- so for example we were reading in bridge-purpose
7829 descriptors as general-purpose descriptors. Bugfix on 0.2.0.8-alpha.
7830 - When we decided to send a 503 response to a request for servers, we
7831 were then also sending the server descriptors: this defeats the
7832 whole purpose. Fixes bug 539; bugfix on 0.1.2.x.
7835 - Bridge relays now behave like clients with respect to time
7836 intervals for downloading new consensus documents -- otherwise they
7837 stand out. Bridge users now wait until the end of the interval,
7838 so their bridge relay will be sure to have a new consensus document.
7839 - Three new config options (AlternateDirAuthority,
7840 AlternateBridgeAuthority, and AlternateHSAuthority) that let the
7841 user selectively replace the default directory authorities by type,
7842 rather than the all-or-nothing replacement that DirServer offers.
7843 - Tor can now be configured to read a GeoIP file from disk in one
7844 of two formats. This can be used by controllers to map IP addresses
7845 to countries. Eventually, it may support exit-by-country.
7846 - When possible, bridge relays remember which countries users
7847 are coming from, and report aggregate information in their
7848 extra-info documents, so that the bridge authorities can learn
7849 where Tor is blocked.
7850 - Bridge directory authorities now do reachability testing on the
7851 bridges they know. They provide router status summaries to the
7852 controller via "getinfo ns/purpose/bridge", and also dump summaries
7853 to a file periodically.
7854 - Stop fetching directory info so aggressively if your DirPort is
7855 on but your ORPort is off; stop fetching v2 dir info entirely.
7856 You can override these choices with the new FetchDirInfoEarly
7860 - The fix in 0.2.0.12-alpha cleared the "hsdir" flag in v3 network
7861 consensus documents when there are too many relays at a single
7862 IP address. Now clear it in v2 network status documents too, and
7863 also clear it in routerinfo_t when the relay is no longer listed
7864 in the relevant networkstatus document.
7865 - Don't crash if we get an unexpected value for the
7866 PublishServerDescriptor config option. Reported by Matt Edman;
7867 bugfix on 0.2.0.9-alpha.
7868 - Our new v2 hidden service descriptor format allows descriptors
7869 that have no introduction points. But Tor crashed when we tried
7870 to build a descriptor with no intro points (and it would have
7871 crashed if we had tried to parse one). Bugfix on 0.2.0.x; patch
7873 - Fix building with dmalloc 5.5.2 with glibc.
7874 - Reject uploaded descriptors and extrainfo documents if they're
7875 huge. Otherwise we'll cache them all over the network and it'll
7876 clog everything up. Reported by Aljosha Judmayer.
7877 - Check for presence of s6_addr16 and s6_addr32 fields in in6_addr
7878 via autoconf. Should fix compile on solaris. Bugfix on 0.2.0.x.
7879 - When the DANGEROUS_VERSION controller status event told us we're
7880 running an obsolete version, it used the string "OLD" to describe
7881 it. Yet the "getinfo" interface used the string "OBSOLETE". Now use
7882 "OBSOLETE" in both cases. Bugfix on 0.1.2.x.
7883 - If we can't expand our list of entry guards (e.g. because we're
7884 using bridges or we have StrictEntryNodes set), don't mark relays
7885 down when they fail a directory request. Otherwise we're too quick
7886 to mark all our entry points down. Bugfix on 0.1.2.x.
7887 - Fix handling of hex nicknames when answering controller requests for
7888 networkstatus by name, or when deciding whether to warn about unknown
7889 routers in a config option. Bugfix on 0.1.2.x. (Patch from mwenge.)
7890 - Fix a couple of hard-to-trigger autoconf problems that could result
7891 in really weird results on platforms whose sys/types.h files define
7892 nonstandard integer types. Bugfix on 0.1.2.x.
7893 - Fix compilation with --disable-threads set. Bugfix on 0.2.0.x.
7894 - Don't crash on name lookup when we have no current consensus. Fixes
7895 bug 538; bugfix on 0.2.0.x.
7896 - Only Tors that want to mirror the v2 directory info should
7897 create the "cached-status" directory in their datadir. (All Tors
7898 used to create it.) Bugfix on 0.2.0.9-alpha.
7899 - Directory authorities should only automatically download Extra Info
7900 documents if they're v1, v2, or v3 authorities. Bugfix on 0.1.2.x.
7903 - On the USR1 signal, when dmalloc is in use, log the top 10 memory
7904 consumers. (We already do this on HUP.)
7905 - Authorities and caches fetch the v2 networkstatus documents
7906 less often, now that v3 is encouraged.
7907 - Add a new config option BridgeRelay that specifies you want to
7908 be a bridge relay. Right now the only difference is that it makes
7909 you answer begin_dir requests, and it makes you cache dir info,
7910 even if your DirPort isn't on.
7911 - Add "GETINFO/desc-annotations/id/<OR digest>" so controllers can
7912 ask about source, timestamp of arrival, purpose, etc. We need
7913 something like this to help Vidalia not do GeoIP lookups on bridge
7915 - Allow multiple HashedControlPassword config lines, to support
7916 multiple controller passwords.
7917 - Authorities now decide whether they're authoritative for a given
7918 router based on the router's purpose.
7919 - New config options AuthDirBadDir and AuthDirListBadDirs for
7920 authorities to mark certain relays as "bad directories" in the
7921 networkstatus documents. Also supports the "!baddir" directive in
7922 the approved-routers file.
7925 Changes in version 0.2.0.12-alpha - 2007-11-16
7926 This twelfth development snapshot fixes some more build problems as
7927 well as a few minor bugs.
7930 - Make it build on OpenBSD again. Patch from tup.
7931 - Substitute BINDIR and LOCALSTATEDIR in scripts. Fixes
7932 package-building for Red Hat, OS X, etc.
7934 o Minor bugfixes (on 0.1.2.x):
7935 - Changing the ExitPolicyRejectPrivate setting should cause us to
7936 rebuild our server descriptor.
7938 o Minor bugfixes (on 0.2.0.x):
7939 - When we're lacking a consensus, don't try to perform rendezvous
7940 operations. Reported by Karsten Loesing.
7941 - Fix a small memory leak whenever we decide against using a
7942 newly picked entry guard. Reported by Mike Perry.
7943 - When authorities detected more than two relays running on the same
7944 IP address, they were clearing all the status flags but forgetting
7945 to clear the "hsdir" flag. So clients were being told that a
7946 given relay was the right choice for a v2 hsdir lookup, yet they
7947 never had its descriptor because it was marked as 'not running'
7949 - If we're trying to fetch a bridge descriptor and there's no way
7950 the bridge authority could help us (for example, we don't know
7951 a digest, or there is no bridge authority), don't be so eager to
7952 fall back to asking the bridge authority.
7953 - If we're using bridges or have strictentrynodes set, and our
7954 chosen exit is in the same family as all our bridges/entry guards,
7955 then be flexible about families.
7958 - When we negotiate a v2 link-layer connection (not yet implemented),
7959 accept RELAY_EARLY cells and turn them into RELAY cells if we've
7960 negotiated a v1 connection for their next step. Initial code for
7964 Changes in version 0.2.0.11-alpha - 2007-11-12
7965 This eleventh development snapshot fixes some build problems with
7966 the previous snapshot. It also includes a more secure-by-default exit
7967 policy for relays, fixes an enormous memory leak for exit relays, and
7968 fixes another bug where servers were falling out of the directory list.
7971 - Exit policies now reject connections that are addressed to a
7972 relay's public (external) IP address too, unless
7973 ExitPolicyRejectPrivate is turned off. We do this because too
7974 many relays are running nearby to services that trust them based
7975 on network address. Bugfix on 0.1.2.x.
7978 - Fix a memory leak on exit relays; we were leaking a cached_resolve_t
7979 on every successful resolve. Reported by Mike Perry; bugfix
7981 - On authorities, never downgrade to old router descriptors simply
7982 because they're listed in the consensus. This created a catch-22
7983 where we wouldn't list a new descriptor because there was an
7984 old one in the consensus, and we couldn't get the new one in the
7985 consensus because we wouldn't list it. Possible fix for bug 548.
7986 Also, this might cause bug 543 to appear on authorities; if so,
7987 we'll need a band-aid for that. Bugfix on 0.2.0.9-alpha.
7989 o Packaging fixes on 0.2.0.10-alpha:
7990 - We were including instructions about what to do with the
7991 src/config/fallback-consensus file, but we weren't actually
7992 including it in the tarball. Disable all of that for now.
7995 - Allow people to say PreferTunnelledDirConns rather than
7996 PreferTunneledDirConns, for those alternate-spellers out there.
7999 - Don't reevaluate all the information from our consensus document
8000 just because we've downloaded a v2 networkstatus that we intend
8001 to cache. Fixes bug 545; bugfix on 0.2.0.x.
8004 Changes in version 0.2.0.10-alpha - 2007-11-10
8005 This tenth development snapshot adds a third v3 directory authority
8006 run by Mike Perry, adds most of Karsten Loesing's new hidden service
8007 descriptor format, fixes a bad crash bug and new bridge bugs introduced
8008 in 0.2.0.9-alpha, fixes many bugs with the v3 directory implementation,
8009 fixes some minor memory leaks in previous 0.2.0.x snapshots, and
8010 addresses many more minor issues.
8012 o New directory authorities:
8013 - Set up ides (run by Mike Perry) as the third v3 directory authority.
8016 - Allow tunnelled directory connections to ask for an encrypted
8017 "begin_dir" connection or an anonymized "uses a full Tor circuit"
8018 connection independently. Now we can make anonymized begin_dir
8019 connections for (e.g.) more secure hidden service posting and
8021 - More progress on proposal 114: code from Karsten Loesing to
8022 implement new hidden service descriptor format.
8023 - Raise the default BandwidthRate/BandwidthBurst to 5MB/10MB, to
8024 accommodate the growing number of servers that use the default
8025 and are reaching it.
8026 - Directory authorities use a new formula for selecting which nodes
8027 to advertise as Guards: they must be in the top 7/8 in terms of
8028 how long we have known about them, and above the median of those
8029 nodes in terms of weighted fractional uptime.
8030 - Make "not enough dir info yet" warnings describe *why* Tor feels
8031 it doesn't have enough directory info yet.
8034 - Stop servers from crashing if they set a Family option (or
8035 maybe in other situations too). Bugfix on 0.2.0.9-alpha; reported
8037 - Make bridge users work again -- the move to v3 directories in
8038 0.2.0.9-alpha had introduced a number of bugs that made bridges
8039 no longer work for clients.
8040 - When the clock jumps forward a lot, do not allow the bandwidth
8041 buckets to become negative. Bugfix on 0.1.2.x; fixes bug 544.
8043 o Major bugfixes (v3 dir, bugfixes on 0.2.0.9-alpha):
8044 - When the consensus lists a router descriptor that we previously were
8045 mirroring, but that we considered non-canonical, reload the
8046 descriptor as canonical. This fixes bug 543 where Tor servers
8047 would start complaining after a few days that they don't have
8048 enough directory information to build a circuit.
8049 - Consider replacing the current consensus when certificates arrive
8050 that make the pending consensus valid. Previously, we were only
8051 considering replacement when the new certs _didn't_ help.
8052 - Fix an assert error on startup if we didn't already have the
8053 consensus and certs cached in our datadirectory: we were caching
8054 the consensus in consensus_waiting_for_certs but then free'ing it
8056 - Avoid sending a request for "keys/fp" (for which we'll get a 400 Bad
8057 Request) if we need more v3 certs but we've already got pending
8058 requests for all of them.
8059 - Correctly back off from failing certificate downloads. Fixes
8061 - Authorities don't vote on the Running flag if they have been running
8062 for less than 30 minutes themselves. Fixes bug 547, where a newly
8063 started authority would vote that everyone was down.
8066 - Drop support for OpenSSL version 0.9.6. Just about nobody was using
8067 it, it had no AES, and it hasn't seen any security patches since
8071 - Clients now hold circuitless TLS connections open for 1.5 times
8072 MaxCircuitDirtiness (15 minutes), since it is likely that they'll
8073 rebuild a new circuit over them within that timeframe. Previously,
8074 they held them open only for KeepalivePeriod (5 minutes).
8075 - Use "If-Modified-Since" to avoid retrieving consensus
8076 networkstatuses that we already have.
8077 - When we have no consensus, check FallbackNetworkstatusFile (defaults
8078 to $PREFIX/share/tor/fallback-consensus) for a consensus. This way
8079 we start knowing some directory caches.
8080 - When we receive a consensus from the future, warn about skew.
8081 - Improve skew reporting: try to give the user a better log message
8082 about how skewed they are, and how much this matters.
8083 - When we have a certificate for an authority, believe that
8084 certificate's claims about the authority's IP address.
8085 - New --quiet command-line option to suppress the default console log.
8086 Good in combination with --hash-password.
8087 - Authorities send back an X-Descriptor-Not-New header in response to
8088 an accepted-but-discarded descriptor upload. Partially implements
8090 - Make the log message for "tls error. breaking." more useful.
8091 - Better log messages about certificate downloads, to attempt to
8092 track down the second incarnation of bug 546.
8094 o Minor features (bridges):
8095 - If bridge users set UpdateBridgesFromAuthority, but the digest
8096 they ask for is a 404 from the bridge authority, they now fall
8097 back to trying the bridge directly.
8098 - Bridges now use begin_dir to publish their server descriptor to
8099 the bridge authority, even when they haven't set TunnelDirConns.
8101 o Minor features (controller):
8102 - When reporting clock skew, and we know that the clock is _at least
8103 as skewed_ as some value, but we don't know the actual value,
8104 report the value as a "minimum skew."
8107 - Update linux-tor-prio.sh script to allow QoS based on the uid of
8108 the Tor process. Patch from Marco Bonetti with tweaks from Mike
8112 - Refuse to start if both ORPort and UseBridges are set. Bugfix
8113 on 0.2.0.x, suggested by Matt Edman.
8114 - Don't stop fetching descriptors when FetchUselessDescriptors is
8115 set, even if we stop asking for circuits. Bugfix on 0.1.2.x;
8116 reported by tup and ioerror.
8117 - Better log message on vote from unknown authority.
8118 - Don't log "Launching 0 request for 0 router" message.
8120 o Minor bugfixes (memory leaks):
8121 - Stop leaking memory every time we parse a v3 certificate. Bugfix
8123 - Stop leaking memory every time we load a v3 certificate. Bugfix
8124 on 0.2.0.1-alpha. Fixes bug 536.
8125 - Stop leaking a cached networkstatus on exit. Bugfix on
8127 - Stop leaking voter information every time we free a consensus.
8128 Bugfix on 0.2.0.3-alpha.
8129 - Stop leaking signed data every time we check a voter signature.
8130 Bugfix on 0.2.0.3-alpha.
8131 - Stop leaking a signature every time we fail to parse a consensus or
8132 a vote. Bugfix on 0.2.0.3-alpha.
8133 - Stop leaking v2_download_status_map on shutdown. Bugfix on
8135 - Stop leaking conn->nickname every time we make a connection to a
8136 Tor relay without knowing its expected identity digest (e.g. when
8137 using bridges). Bugfix on 0.2.0.3-alpha.
8139 - Minor bugfixes (portability):
8140 - Run correctly on platforms where rlim_t is larger than unsigned
8141 long, and/or where the real limit for number of open files is
8142 OPEN_FILES, not rlim_max from getrlimit(RLIMIT_NOFILES). In
8143 particular, these may be needed for OS X 10.5.
8146 Changes in version 0.1.2.18 - 2007-10-28
8147 Tor 0.1.2.18 fixes many problems including crash bugs, problems with
8148 hidden service introduction that were causing huge delays, and a big
8149 bug that was causing some servers to disappear from the network status
8150 lists for a few hours each day.
8152 o Major bugfixes (crashes):
8153 - If a connection is shut down abruptly because of something that
8154 happened inside connection_flushed_some(), do not call
8155 connection_finished_flushing(). Should fix bug 451:
8156 "connection_stop_writing: Assertion conn->write_event failed"
8157 Bugfix on 0.1.2.7-alpha.
8158 - Fix possible segfaults in functions called from
8159 rend_process_relay_cell().
8161 o Major bugfixes (hidden services):
8162 - Hidden services were choosing introduction points uniquely by
8163 hexdigest, but when constructing the hidden service descriptor
8164 they merely wrote the (potentially ambiguous) nickname.
8165 - Clients now use the v2 intro format for hidden service
8166 connections: they specify their chosen rendezvous point by identity
8167 digest rather than by (potentially ambiguous) nickname. These
8168 changes could speed up hidden service connections dramatically.
8170 o Major bugfixes (other):
8171 - Stop publishing a new server descriptor just because we get a
8172 HUP signal. This led (in a roundabout way) to some servers getting
8173 dropped from the networkstatus lists for a few hours each day.
8174 - When looking for a circuit to cannibalize, consider family as well
8175 as identity. Fixes bug 438. Bugfix on 0.1.0.x (which introduced
8176 circuit cannibalization).
8177 - When a router wasn't listed in a new networkstatus, we were leaving
8178 the flags for that router alone -- meaning it remained Named,
8179 Running, etc -- even though absence from the networkstatus means
8180 that it shouldn't be considered to exist at all anymore. Now we
8181 clear all the flags for routers that fall out of the networkstatus
8182 consensus. Fixes bug 529.
8185 - Don't try to access (or alter) the state file when running
8186 --list-fingerprint or --verify-config or --hash-password. Resolves
8188 - When generating information telling us how to extend to a given
8189 router, do not try to include the nickname if it is
8190 absent. Resolves bug 467.
8191 - Fix a user-triggerable segfault in expand_filename(). (There isn't
8192 a way to trigger this remotely.)
8193 - When sending a status event to the controller telling it that an
8194 OR address is reachable, set the port correctly. (Previously we
8195 were reporting the dir port.)
8196 - Fix a minor memory leak whenever a controller sends the PROTOCOLINFO
8197 command. Bugfix on 0.1.2.17.
8198 - When loading bandwidth history, do not believe any information in
8199 the future. Fixes bug 434.
8200 - When loading entry guard information, do not believe any information
8202 - When we have our clock set far in the future and generate an
8203 onion key, then re-set our clock to be correct, we should not stop
8204 the onion key from getting rotated.
8205 - On some platforms, accept() can return a broken address. Detect
8206 this more quietly, and deal accordingly. Fixes bug 483.
8207 - It's not actually an error to find a non-pending entry in the DNS
8208 cache when canceling a pending resolve. Don't log unless stuff
8209 is fishy. Resolves bug 463.
8210 - Don't reset trusted dir server list when we set a configuration
8211 option. Patch from Robert Hogan.
8212 - Don't try to create the datadir when running --verify-config or
8213 --hash-password. Resolves bug 540.
8216 Changes in version 0.2.0.9-alpha - 2007-10-24
8217 This ninth development snapshot switches clients to the new v3 directory
8218 system; allows servers to be listed in the network status even when they
8219 have the same nickname as a registered server; and fixes many other
8220 bugs including a big one that was causing some servers to disappear
8221 from the network status lists for a few hours each day.
8223 o Major features (directory system):
8224 - Clients now download v3 consensus networkstatus documents instead
8225 of v2 networkstatus documents. Clients and caches now base their
8226 opinions about routers on these consensus documents. Clients only
8227 download router descriptors listed in the consensus.
8228 - Authorities now list servers who have the same nickname as
8229 a different named server, but list them with a new flag,
8230 "Unnamed". Now we can list servers that happen to pick the same
8231 nickname as a server that registered two years ago and then
8232 disappeared. Partially implements proposal 122.
8233 - If the consensus lists a router as "Unnamed", the name is assigned
8234 to a different router: do not identify the router by that name.
8235 Partially implements proposal 122.
8236 - Authorities can now come to a consensus on which method to use to
8237 compute the consensus. This gives us forward compatibility.
8240 - Stop publishing a new server descriptor just because we HUP or
8241 when we find our DirPort to be reachable but won't actually publish
8242 it. New descriptors without any real changes are dropped by the
8243 authorities, and can screw up our "publish every 18 hours" schedule.
8245 - When a router wasn't listed in a new networkstatus, we were leaving
8246 the flags for that router alone -- meaning it remained Named,
8247 Running, etc -- even though absence from the networkstatus means
8248 that it shouldn't be considered to exist at all anymore. Now we
8249 clear all the flags for routers that fall out of the networkstatus
8250 consensus. Fixes bug 529; bugfix on 0.1.2.x.
8251 - Fix awful behavior in DownloadExtraInfo option where we'd fetch
8252 extrainfo documents and then discard them immediately for not
8253 matching the latest router. Bugfix on 0.2.0.1-alpha.
8255 o Minor features (v3 directory protocol):
8256 - Allow tor-gencert to generate a new certificate without replacing
8258 - Allow certificates to include an address.
8259 - When we change our directory-cache settings, reschedule all voting
8260 and download operations.
8261 - Reattempt certificate downloads immediately on failure, as long as
8262 we haven't failed a threshold number of times yet.
8263 - Delay retrying consensus downloads while we're downloading
8264 certificates to verify the one we just got. Also, count getting a
8265 consensus that we already have (or one that isn't valid) as a failure,
8266 and count failing to get the certificates after 20 minutes as a
8268 - Build circuits and download descriptors even if our consensus is a
8269 little expired. (This feature will go away once authorities are
8272 o Minor features (router descriptor cache):
8273 - If we find a cached-routers file that's been sitting around for more
8274 than 28 days unmodified, then most likely it's a leftover from
8275 when we upgraded to 0.2.0.8-alpha. Remove it. It has no good
8277 - When we (as a cache) download a descriptor because it was listed
8278 in a consensus, remember when the consensus was supposed to expire,
8279 and don't expire the descriptor until then.
8281 o Minor features (performance):
8282 - Call routerlist_remove_old_routers() much less often. This should
8283 speed startup, especially on directory caches.
8284 - Don't try to launch new descriptor downloads quite so often when we
8285 already have enough directory information to build circuits.
8286 - Base64 decoding was actually showing up on our profile when parsing
8287 the initial descriptor file; switch to an in-process all-at-once
8288 implementation that's about 3.5x times faster than calling out to
8291 o Minor features (compilation):
8292 - Detect non-ASCII platforms (if any still exist) and refuse to
8293 build there: some of our code assumes that 'A' is 65 and so on.
8295 o Minor bugfixes (v3 directory authorities, bugfixes on 0.2.0.x):
8296 - Make the "next period" votes into "current period" votes immediately
8297 after publishing the consensus; avoid a heisenbug that made them
8298 stick around indefinitely.
8299 - When we discard a vote as a duplicate, do not report this as
8301 - Treat missing v3 keys or certificates as an error when running as a
8302 v3 directory authority.
8303 - When we're configured to be a v3 authority, but we're only listed
8304 as a non-v3 authority in our DirServer line for ourself, correct
8306 - If an authority doesn't have a qualified hostname, just put
8307 its address in the vote. This fixes the problem where we referred to
8308 "moria on moria:9031."
8309 - Distinguish between detached signatures for the wrong period, and
8310 detached signatures for a divergent vote.
8311 - Fix a small memory leak when computing a consensus.
8312 - When there's no concensus, we were forming a vote every 30
8313 minutes, but writing the "valid-after" line in our vote based
8314 on our configured V3AuthVotingInterval: so unless the intervals
8315 matched up, we immediately rejected our own vote because it didn't
8316 start at the voting interval that caused us to construct a vote.
8318 o Minor bugfixes (v3 directory protocol, bugfixes on 0.2.0.x):
8319 - Delete unverified-consensus when the real consensus is set.
8320 - Consider retrying a consensus networkstatus fetch immediately
8321 after one fails: don't wait 60 seconds to notice.
8322 - When fetching a consensus as a cache, wait until a newer consensus
8323 should exist before trying to replace the current one.
8324 - Use a more forgiving schedule for retrying failed consensus
8325 downloads than for other types.
8327 o Minor bugfixes (other directory issues):
8328 - Correct the implementation of "download votes by digest." Bugfix on
8330 - Authorities no longer send back "400 you're unreachable please fix
8331 it" errors to Tor servers that aren't online all the time. We're
8332 supposed to tolerate these servers now. Bugfix on 0.1.2.x.
8334 o Minor bugfixes (controller):
8335 - Don't reset trusted dir server list when we set a configuration
8336 option. Patch from Robert Hogan; bugfix on 0.1.2.x.
8337 - Respond to INT and TERM SIGNAL commands before we execute the
8338 signal, in case the signal shuts us down. We had a patch in
8339 0.1.2.1-alpha that tried to do this by queueing the response on
8340 the connection's buffer before shutting down, but that really
8341 isn't the same thing at all. Bug located by Matt Edman.
8343 o Minor bugfixes (misc):
8344 - Correctly check for bad options to the "PublishServerDescriptor"
8345 config option. Bugfix on 0.2.0.1-alpha; reported by Matt Edman.
8346 - Stop leaking memory on failing case of base32_decode, and make
8347 it accept upper-case letters. Bugfixes on 0.2.0.7-alpha.
8348 - Don't try to download extrainfo documents when we're trying to
8349 fetch enough directory info to build a circuit: having enough
8350 info should get priority. Bugfix on 0.2.0.x.
8351 - Don't complain that "your server has not managed to confirm that its
8352 ports are reachable" if we haven't been able to build any circuits
8353 yet. Bug found by spending four hours without a v3 consensus. Bugfix
8355 - Detect the reason for failing to mmap a descriptor file we just
8356 wrote, and give a more useful log message. Fixes bug 533. Bugfix
8359 o Code simplifications and refactoring:
8360 - Remove support for the old bw_accounting file: we've been storing
8361 bandwidth accounting information in the state file since
8362 0.1.2.5-alpha. This may result in bandwidth accounting errors
8363 if you try to upgrade from 0.1.1.x or earlier, or if you try to
8364 downgrade to 0.1.1.x or earlier.
8365 - New convenience code to locate a file within the DataDirectory.
8366 - Move non-authority functionality out of dirvote.c.
8367 - Refactor the arguments for router_pick_{directory_|trusteddir}server
8368 so that they all take the same named flags.
8371 - Include the "tor-ctrl.sh" bash script by Stefan Behte to provide
8372 Unix users an easy way to script their Tor process (e.g. by
8373 adjusting bandwidth based on the time of the day).
8376 Changes in version 0.2.0.8-alpha - 2007-10-12
8377 This eighth development snapshot fixes a crash bug that's been bothering
8378 us since February 2007, lets bridge authorities store a list of bridge
8379 descriptors they've seen, gets v3 directory voting closer to working,
8380 starts caching v3 directory consensus documents on directory mirrors,
8381 and fixes a variety of smaller issues including some minor memory leaks.
8383 o Major features (router descriptor cache):
8384 - Store routers in a file called cached-descriptors instead of in
8385 cached-routers. Initialize cached-descriptors from cached-routers
8386 if the old format is around. The new format allows us to store
8387 annotations along with descriptors.
8388 - Use annotations to record the time we received each descriptor, its
8389 source, and its purpose.
8390 - Disable the SETROUTERPURPOSE controller command: it is now
8392 - Controllers should now specify cache=no or cache=yes when using
8393 the +POSTDESCRIPTOR command.
8394 - Bridge authorities now write bridge descriptors to disk, meaning
8395 we can export them to other programs and begin distributing them
8398 o Major features (directory authorities):
8399 - When a v3 authority is missing votes or signatures, it now tries
8401 - Directory authorities track weighted fractional uptime as well as
8402 weighted mean-time-between failures. WFU is suitable for deciding
8403 whether a node is "usually up", while MTBF is suitable for deciding
8404 whether a node is "likely to stay up." We need both, because
8405 "usually up" is a good requirement for guards, while "likely to
8406 stay up" is a good requirement for long-lived connections.
8408 o Major features (v3 directory system):
8409 - Caches now download v3 network status documents as needed,
8410 and download the descriptors listed in them.
8411 - All hosts now attempt to download and keep fresh v3 authority
8412 certificates, and re-attempt after failures.
8413 - More internal-consistency checks for vote parsing.
8415 o Major bugfixes (crashes):
8416 - If a connection is shut down abruptly because of something that
8417 happened inside connection_flushed_some(), do not call
8418 connection_finished_flushing(). Should fix bug 451. Bugfix on
8421 o Major bugfixes (performance):
8422 - Fix really bad O(n^2) performance when parsing a long list of
8423 routers: Instead of searching the entire list for an "extra-info "
8424 string which usually wasn't there, once for every routerinfo
8425 we read, just scan lines forward until we find one we like.
8427 - When we add data to a write buffer in response to the data on that
8428 write buffer getting low because of a flush, do not consider the
8429 newly added data as a candidate for immediate flushing, but rather
8430 make it wait until the next round of writing. Otherwise, we flush
8431 and refill recursively, and a single greedy TLS connection can
8432 eat all of our bandwidth. Bugfix on 0.1.2.7-alpha.
8434 o Minor features (v3 authority system):
8435 - Add more ways for tools to download the votes that lead to the
8437 - Send a 503 when low on bandwidth and a vote, consensus, or
8438 certificate is requested.
8439 - If-modified-since is now implemented properly for all kinds of
8440 certificate requests.
8442 o Minor bugfixes (network statuses):
8443 - Tweak the implementation of proposal 109 slightly: allow at most
8444 two Tor servers on the same IP address, except if it's the location
8445 of a directory authority, in which case allow five. Bugfix on
8448 o Minor bugfixes (controller):
8449 - When sending a status event to the controller telling it that an
8450 OR address is reachable, set the port correctly. (Previously we
8451 were reporting the dir port.) Bugfix on 0.1.2.x.
8453 o Minor bugfixes (v3 directory system):
8454 - Fix logic to look up a cert by its signing key digest. Bugfix on
8456 - Only change the reply to a vote to "OK" if it's not already
8457 set. This gets rid of annoying "400 OK" log messages, which may
8458 have been masking some deeper issue. Bugfix on 0.2.0.7-alpha.
8459 - When we get a valid consensus, recompute the voting schedule.
8460 - Base the valid-after time of a vote on the consensus voting
8461 schedule, not on our preferred schedule.
8462 - Make the return values and messages from signature uploads and
8463 downloads more sensible.
8464 - Fix a memory leak when serving votes and consensus documents, and
8465 another when serving certificates.
8467 o Minor bugfixes (performance):
8468 - Use a slightly simpler string hashing algorithm (copying Python's
8469 instead of Java's) and optimize our digest hashing algorithm to take
8470 advantage of 64-bit platforms and to remove some possibly-costly
8472 - Fix a minor memory leak whenever we parse guards from our state
8473 file. Bugfix on 0.2.0.7-alpha.
8474 - Fix a minor memory leak whenever we write out a file. Bugfix on
8476 - Fix a minor memory leak whenever a controller sends the PROTOCOLINFO
8477 command. Bugfix on 0.2.0.5-alpha.
8479 o Minor bugfixes (portability):
8480 - On some platforms, accept() can return a broken address. Detect
8481 this more quietly, and deal accordingly. Fixes bug 483.
8482 - Stop calling tor_strlower() on uninitialized memory in some cases.
8483 Bugfix in 0.2.0.7-alpha.
8485 o Minor bugfixes (usability):
8486 - Treat some 403 responses from directory servers as INFO rather than
8487 WARN-severity events.
8488 - It's not actually an error to find a non-pending entry in the DNS
8489 cache when canceling a pending resolve. Don't log unless stuff is
8490 fishy. Resolves bug 463.
8492 o Minor bugfixes (anonymity):
8493 - Never report that we've used more bandwidth than we're willing to
8494 relay: it leaks how much non-relay traffic we're using. Resolves
8496 - When looking for a circuit to cannibalize, consider family as well
8497 as identity. Fixes bug 438. Bugfix on 0.1.0.x (which introduced
8498 circuit cannibalization).
8500 o Code simplifications and refactoring:
8501 - Make a bunch of functions static. Remove some dead code.
8502 - Pull out about a third of the really big routerlist.c; put it in a
8503 new module, networkstatus.c.
8504 - Merge the extra fields in local_routerstatus_t back into
8505 routerstatus_t: we used to need one routerstatus_t for each
8506 authority's opinion, plus a local_routerstatus_t for the locally
8507 computed consensus opinion. To save space, we put the locally
8508 modified fields into local_routerstatus_t, and only the common
8509 stuff into routerstatus_t. But once v3 directories are in use,
8510 clients and caches will no longer need to hold authority opinions;
8511 thus, the rationale for keeping the types separate is now gone.
8512 - Make the code used to reschedule and reattempt downloads more
8514 - Turn all 'Are we a directory server/mirror?' logic into a call to
8516 - Remove the code to generate the oldest (v1) directory format.
8517 The code has been disabled since 0.2.0.5-alpha.
8520 Changes in version 0.2.0.7-alpha - 2007-09-21
8521 This seventh development snapshot makes bridges work again, makes bridge
8522 authorities work for the first time, fixes two huge performance flaws
8523 in hidden services, and fixes a variety of minor issues.
8525 o New directory authorities:
8526 - Set up moria1 and tor26 as the first v3 directory authorities. See
8527 doc/spec/dir-spec.txt for details on the new directory design.
8529 o Major bugfixes (crashes):
8530 - Fix possible segfaults in functions called from
8531 rend_process_relay_cell(). Bugfix on 0.1.2.x.
8533 o Major bugfixes (bridges):
8534 - Fix a bug that made servers send a "404 Not found" in response to
8535 attempts to fetch their server descriptor. This caused Tor servers
8536 to take many minutes to establish reachability for their DirPort,
8537 and it totally crippled bridges. Bugfix on 0.2.0.5-alpha.
8538 - Make "UpdateBridgesFromAuthority" torrc option work: when bridge
8539 users configure that and specify a bridge with an identity
8540 fingerprint, now they will lookup the bridge descriptor at the
8541 default bridge authority via a one-hop tunnel, but once circuits
8542 are established they will switch to a three-hop tunnel for later
8543 connections to the bridge authority. Bugfix in 0.2.0.3-alpha.
8545 o Major bugfixes (hidden services):
8546 - Hidden services were choosing introduction points uniquely by
8547 hexdigest, but when constructing the hidden service descriptor
8548 they merely wrote the (potentially ambiguous) nickname.
8549 - Clients now use the v2 intro format for hidden service
8550 connections: they specify their chosen rendezvous point by identity
8551 digest rather than by (potentially ambiguous) nickname. Both
8552 are bugfixes on 0.1.2.x, and they could speed up hidden service
8553 connections dramatically. Thanks to Karsten Loesing.
8555 o Minor features (security):
8556 - As a client, do not believe any server that tells us that an
8557 address maps to an internal address space.
8558 - Make it possible to enable HashedControlPassword and
8559 CookieAuthentication at the same time.
8561 o Minor features (guard nodes):
8562 - Tag every guard node in our state file with the version that
8563 we believe added it, or with our own version if we add it. This way,
8564 if a user temporarily runs an old version of Tor and then switches
8565 back to a new one, she doesn't automatically lose her guards.
8567 o Minor features (speed):
8568 - When implementing AES counter mode, update only the portions of the
8569 counter buffer that need to change, and don't keep separate
8570 network-order and host-order counters when they are the same (i.e.,
8571 on big-endian hosts.)
8573 o Minor features (controller):
8574 - Accept LF instead of CRLF on controller, since some software has a
8575 hard time generating real Internet newlines.
8576 - Add GETINFO values for the server status events
8577 "REACHABILITY_SUCCEEDED" and "GOOD_SERVER_DESCRIPTOR". Patch from
8581 - Routers no longer include bandwidth-history lines in their
8582 descriptors; this information is already available in extra-info
8583 documents, and including it in router descriptors took up 60%
8584 (!) of compressed router descriptor downloads. Completes
8585 implementation of proposal 104.
8586 - Remove the contrib scripts ExerciseServer.py, PathDemo.py,
8587 and TorControl.py, as they use the old v0 controller protocol,
8588 and are obsoleted by TorFlow anyway.
8589 - Drop support for v1 rendezvous descriptors, since we never used
8590 them anyway, and the code has probably rotted by now. Based on
8591 patch from Karsten Loesing.
8592 - On OSX, stop warning the user that kqueue support in libevent is
8593 "experimental", since it seems to have worked fine for ages.
8596 - When generating information telling us how to extend to a given
8597 router, do not try to include the nickname if it is absent. Fixes
8598 bug 467. Bugfix on 0.2.0.3-alpha.
8599 - Fix a user-triggerable (but not remotely-triggerable) segfault
8600 in expand_filename(). Bugfix on 0.1.2.x.
8601 - Fix a memory leak when freeing incomplete requests from DNSPort.
8602 Found by Niels Provos with valgrind. Bugfix on 0.2.0.1-alpha.
8603 - Don't try to access (or alter) the state file when running
8604 --list-fingerprint or --verify-config or --hash-password. (Resolves
8605 bug 499.) Bugfix on 0.1.2.x.
8606 - Servers used to decline to publish their DirPort if their
8607 BandwidthRate, RelayBandwidthRate, or MaxAdvertisedBandwidth
8608 were below a threshold. Now they only look at BandwidthRate and
8609 RelayBandwidthRate. Bugfix on 0.1.2.x.
8610 - Remove an optimization in the AES counter-mode code that assumed
8611 that the counter never exceeded 2^68. When the counter can be set
8612 arbitrarily as an IV (as it is by Karsten's new hidden services
8613 code), this assumption no longer holds. Bugfix on 0.1.2.x.
8614 - Resume listing "AUTHORITY" flag for authorities in network status.
8615 Bugfix on 0.2.0.3-alpha; reported by Alex de Joode.
8617 o Code simplifications and refactoring:
8618 - Revamp file-writing logic so we don't need to have the entire
8619 contents of a file in memory at once before we write to disk. Tor,
8621 - Turn "descriptor store" into a full-fledged type.
8622 - Move all NT services code into a separate source file.
8623 - Unify all code that computes medians, percentile elements, etc.
8624 - Get rid of a needless malloc when parsing address policies.
8627 Changes in version 0.1.2.17 - 2007-08-30
8628 Tor 0.1.2.17 features a new Vidalia version in the Windows and OS
8629 X bundles. Vidalia 0.0.14 makes authentication required for the
8630 ControlPort in the default configuration, which addresses important
8631 security risks. Everybody who uses Vidalia (or another controller)
8634 In addition, this Tor update fixes major load balancing problems with
8635 path selection, which should speed things up a lot once many people
8638 o Major bugfixes (security):
8639 - We removed support for the old (v0) control protocol. It has been
8640 deprecated since Tor 0.1.1.1-alpha, and keeping it secure has
8641 become more of a headache than it's worth.
8643 o Major bugfixes (load balancing):
8644 - When choosing nodes for non-guard positions, weight guards
8645 proportionally less, since they already have enough load. Patch
8647 - Raise the "max believable bandwidth" from 1.5MB/s to 10MB/s. This
8648 will allow fast Tor servers to get more attention.
8649 - When we're upgrading from an old Tor version, forget our current
8650 guards and pick new ones according to the new weightings. These
8651 three load balancing patches could raise effective network capacity
8652 by a factor of four. Thanks to Mike Perry for measurements.
8654 o Major bugfixes (stream expiration):
8655 - Expire not-yet-successful application streams in all cases if
8656 they've been around longer than SocksTimeout. Right now there are
8657 some cases where the stream will live forever, demanding a new
8658 circuit every 15 seconds. Fixes bug 454; reported by lodger.
8660 o Minor features (controller):
8661 - Add a PROTOCOLINFO controller command. Like AUTHENTICATE, it
8662 is valid before any authentication has been received. It tells
8663 a controller what kind of authentication is expected, and what
8664 protocol is spoken. Implements proposal 119.
8666 o Minor bugfixes (performance):
8667 - Save on most routerlist_assert_ok() calls in routerlist.c, thus
8668 greatly speeding up loading cached-routers from disk on startup.
8669 - Disable sentinel-based debugging for buffer code: we squashed all
8670 the bugs that this was supposed to detect a long time ago, and now
8671 its only effect is to change our buffer sizes from nice powers of
8672 two (which platform mallocs tend to like) to values slightly over
8673 powers of two (which make some platform mallocs sad).
8675 o Minor bugfixes (misc):
8676 - If exit bandwidth ever exceeds one third of total bandwidth, then
8677 use the correct formula to weight exit nodes when choosing paths.
8678 Based on patch from Mike Perry.
8679 - Choose perfectly fairly among routers when choosing by bandwidth and
8680 weighting by fraction of bandwidth provided by exits. Previously, we
8681 would choose with only approximate fairness, and correct ourselves
8682 if we ran off the end of the list.
8683 - If we require CookieAuthentication but we fail to write the
8684 cookie file, we would warn but not exit, and end up in a state
8685 where no controller could authenticate. Now we exit.
8686 - If we require CookieAuthentication, stop generating a new cookie
8687 every time we change any piece of our config.
8688 - Refuse to start with certain directory authority keys, and
8689 encourage people using them to stop.
8690 - Terminate multi-line control events properly. Original patch
8692 - Fix a minor memory leak when we fail to find enough suitable
8693 servers to choose a circuit.
8694 - Stop leaking part of the descriptor when we run into a particularly
8695 unparseable piece of it.
8698 Changes in version 0.2.0.6-alpha - 2007-08-26
8699 This sixth development snapshot features a new Vidalia version in the
8700 Windows and OS X bundles. Vidalia 0.0.14 makes authentication required for
8701 the ControlPort in the default configuration, which addresses important
8704 In addition, this snapshot fixes major load balancing problems
8705 with path selection, which should speed things up a lot once many
8706 people have upgraded. The directory authorities also use a new
8707 mean-time-between-failure approach to tracking which servers are stable,
8708 rather than just looking at the most recent uptime.
8710 o New directory authorities:
8711 - Set up Tonga as the default bridge directory authority.
8714 - Directory authorities now track servers by weighted
8715 mean-times-between-failures. When we have 4 or more days of data,
8716 use measured MTBF rather than declared uptime to decide whether
8717 to call a router Stable. Implements proposal 108.
8719 o Major bugfixes (load balancing):
8720 - When choosing nodes for non-guard positions, weight guards
8721 proportionally less, since they already have enough load. Patch
8723 - Raise the "max believable bandwidth" from 1.5MB/s to 10MB/s. This
8724 will allow fast Tor servers to get more attention.
8725 - When we're upgrading from an old Tor version, forget our current
8726 guards and pick new ones according to the new weightings. These
8727 three load balancing patches could raise effective network capacity
8728 by a factor of four. Thanks to Mike Perry for measurements.
8730 o Major bugfixes (descriptor parsing):
8731 - Handle unexpected whitespace better in malformed descriptors. Bug
8732 found using Benedikt Boss's new Tor fuzzer! Bugfix on 0.2.0.x.
8735 - There is now an ugly, temporary "desc/all-recent-extrainfo-hack"
8736 GETINFO for Torstat to use until it can switch to using extrainfos.
8737 - Optionally (if built with -DEXPORTMALLINFO) export the output
8738 of mallinfo via http, as tor/mallinfo.txt. Only accessible
8742 - Do not intermix bridge routers with controller-added
8743 routers. (Bugfix on 0.2.0.x)
8744 - Do not fail with an assert when accept() returns an unexpected
8745 address family. Addresses but does not wholly fix bug 483. (Bugfix
8747 - Let directory authorities startup even when they can't generate
8748 a descriptor immediately, e.g. because they don't know their
8750 - Stop putting the authentication cookie in a file called "0"
8751 in your working directory if you don't specify anything for the
8752 new CookieAuthFile option. Reported by Matt Edman.
8753 - Make it possible to read the PROTOCOLINFO response in a way that
8754 conforms to our control-spec. Reported by Matt Edman.
8755 - Fix a minor memory leak when we fail to find enough suitable
8756 servers to choose a circuit. Bugfix on 0.1.2.x.
8757 - Stop leaking part of the descriptor when we run into a particularly
8758 unparseable piece of it. Bugfix on 0.1.2.x.
8759 - Unmap the extrainfo cache file on exit.
8762 Changes in version 0.2.0.5-alpha - 2007-08-19
8763 This fifth development snapshot fixes compilation on Windows again;
8764 fixes an obnoxious client-side bug that slowed things down and put
8765 extra load on the network; gets us closer to using the v3 directory
8766 voting scheme; makes it easier for Tor controllers to use cookie-based
8767 authentication; and fixes a variety of other bugs.
8770 - Version 1 directories are no longer generated in full. Instead,
8771 authorities generate and serve "stub" v1 directories that list
8772 no servers. This will stop Tor versions 0.1.0.x and earlier from
8773 working, but (for security reasons) nobody should be running those
8776 o Major bugfixes (compilation, 0.2.0.x):
8777 - Try to fix Win32 compilation again: improve checking for IPv6 types.
8778 - Try to fix MSVC compilation: build correctly on platforms that do
8779 not define s6_addr16 or s6_addr32.
8780 - Fix compile on platforms without getaddrinfo: bug found by Li-Hui
8783 o Major bugfixes (stream expiration):
8784 - Expire not-yet-successful application streams in all cases if
8785 they've been around longer than SocksTimeout. Right now there are
8786 some cases where the stream will live forever, demanding a new
8787 circuit every 15 seconds. Bugfix on 0.1.2.7-alpha; fixes bug 454;
8790 o Minor features (directory servers):
8791 - When somebody requests a list of statuses or servers, and we have
8792 none of those, return a 404 rather than an empty 200.
8794 o Minor features (directory voting):
8795 - Store v3 consensus status consensuses on disk, and reload them
8798 o Minor features (security):
8799 - Warn about unsafe ControlPort configurations.
8800 - Refuse to start with certain directory authority keys, and
8801 encourage people using them to stop.
8803 o Minor features (controller):
8804 - Add a PROTOCOLINFO controller command. Like AUTHENTICATE, it
8805 is valid before any authentication has been received. It tells
8806 a controller what kind of authentication is expected, and what
8807 protocol is spoken. Implements proposal 119.
8808 - New config option CookieAuthFile to choose a new location for the
8809 cookie authentication file, and config option
8810 CookieAuthFileGroupReadable to make it group-readable.
8812 o Minor features (unit testing):
8813 - Add command-line arguments to unit-test executable so that we can
8814 invoke any chosen test from the command line rather than having
8815 to run the whole test suite at once; and so that we can turn on
8816 logging for the unit tests.
8818 o Minor bugfixes (on 0.1.2.x):
8819 - If we require CookieAuthentication but we fail to write the
8820 cookie file, we would warn but not exit, and end up in a state
8821 where no controller could authenticate. Now we exit.
8822 - If we require CookieAuthentication, stop generating a new cookie
8823 every time we change any piece of our config.
8824 - When loading bandwidth history, do not believe any information in
8825 the future. Fixes bug 434.
8826 - When loading entry guard information, do not believe any information
8828 - When we have our clock set far in the future and generate an
8829 onion key, then re-set our clock to be correct, we should not stop
8830 the onion key from getting rotated.
8831 - Clean up torrc sample config file.
8832 - Do not automatically run configure from autogen.sh. This
8833 non-standard behavior tended to annoy people who have built other
8836 o Minor bugfixes (on 0.2.0.x):
8837 - Fix a bug with AutomapHostsOnResolve that would always cause
8838 the second request to fail. Bug reported by Kate. Bugfix on
8840 - Fix a bug in ADDRMAP controller replies that would sometimes
8841 try to print a NULL. Patch from tup.
8842 - Read v3 directory authority keys from the right location.
8843 - Numerous bugfixes to directory voting code.
8846 Changes in version 0.1.2.16 - 2007-08-01
8847 Tor 0.1.2.16 fixes a critical security vulnerability that allows a
8848 remote attacker in certain situations to rewrite the user's torrc
8849 configuration file. This can completely compromise anonymity of users
8850 in most configurations, including those running the Vidalia bundles,
8851 TorK, etc. Or worse.
8853 o Major security fixes:
8854 - Close immediately after missing authentication on control port;
8855 do not allow multiple authentication attempts.
8858 Changes in version 0.2.0.4-alpha - 2007-08-01
8859 This fourth development snapshot fixes a critical security vulnerability
8860 for most users, specifically those running Vidalia, TorK, etc. Everybody
8861 should upgrade to either 0.1.2.16 or 0.2.0.4-alpha.
8863 o Major security fixes:
8864 - Close immediately after missing authentication on control port;
8865 do not allow multiple authentication attempts.
8867 o Major bugfixes (compilation):
8868 - Fix win32 compilation: apparently IN_ADDR and IN6_ADDR are already
8871 o Minor features (performance):
8872 - Be even more aggressive about releasing RAM from small
8873 empty buffers. Thanks to our free-list code, this shouldn't be too
8874 performance-intensive.
8875 - Disable sentinel-based debugging for buffer code: we squashed all
8876 the bugs that this was supposed to detect a long time ago, and
8877 now its only effect is to change our buffer sizes from nice
8878 powers of two (which platform mallocs tend to like) to values
8879 slightly over powers of two (which make some platform mallocs sad).
8880 - Log malloc statistics from mallinfo() on platforms where it
8884 Changes in version 0.2.0.3-alpha - 2007-07-29
8885 This third development snapshot introduces new experimental
8886 blocking-resistance features and a preliminary version of the v3
8887 directory voting design, and includes many other smaller features
8891 - The first pieces of our "bridge" design for blocking-resistance
8892 are implemented. People can run bridge directory authorities;
8893 people can run bridges; and people can configure their Tor clients
8894 with a set of bridges to use as the first hop into the Tor network.
8895 See http://archives.seul.org/or/talk/Jul-2007/msg00249.html for
8897 - Create listener connections before we setuid to the configured
8898 User and Group. Now non-Windows users can choose port values
8899 under 1024, start Tor as root, and have Tor bind those ports
8900 before it changes to another UID. (Windows users could already
8902 - Added a new ConstrainedSockets config option to set SO_SNDBUF and
8903 SO_RCVBUF on TCP sockets. Hopefully useful for Tor servers running
8904 on "vserver" accounts. (Patch from coderman.)
8905 - Be even more aggressive about separating local traffic from relayed
8906 traffic when RelayBandwidthRate is set. (Refines proposal 111.)
8908 o Major features (experimental):
8909 - First cut of code for "v3 dir voting": directory authorities will
8910 vote on a common network status document rather than each publishing
8911 their own opinion. This code needs more testing and more corner-case
8912 handling before it's ready for use.
8915 - Directory authorities now call routers Fast if their bandwidth is
8916 at least 100KB/s, and consider their bandwidth adequate to be a
8917 Guard if it is at least 250KB/s, no matter the medians. This fix
8918 complements proposal 107. [Bugfix on 0.1.2.x]
8919 - Directory authorities now never mark more than 3 servers per IP as
8920 Valid and Running. (Implements proposal 109, by Kevin Bauer and
8922 - Minor change to organizationName and commonName generation
8923 procedures in TLS certificates during Tor handshakes, to invalidate
8924 some earlier censorware approaches. This is not a long-term
8925 solution, but applying it will give us a bit of time to look into
8926 the epidemiology of countermeasures as they spread.
8928 o Major bugfixes (directory):
8929 - Rewrite directory tokenization code to never run off the end of
8930 a string. Fixes bug 455. Patch from croup. [Bugfix on 0.1.2.x]
8932 o Minor features (controller):
8933 - Add a SOURCE_ADDR field to STREAM NEW events so that controllers can
8934 match requests to applications. (Patch from Robert Hogan.)
8935 - Report address and port correctly on connections to DNSPort. (Patch
8937 - Add a RESOLVE command to launch hostname lookups. (Original patch
8939 - Add GETINFO status/enough-dir-info to let controllers tell whether
8940 Tor has downloaded sufficient directory information. (Patch
8942 - You can now use the ControlSocket option to tell Tor to listen for
8943 controller connections on Unix domain sockets on systems that
8944 support them. (Patch from Peter Palfrader.)
8945 - STREAM NEW events are generated for DNSPort requests and for
8946 tunneled directory connections. (Patch from Robert Hogan.)
8947 - New "GETINFO address-mappings/*" command to get address mappings
8948 with expiry information. "addr-mappings/*" is now deprecated.
8951 o Minor features (misc):
8952 - Merge in some (as-yet-unused) IPv6 address manipulation code. (Patch
8954 - The tor-gencert tool for v3 directory authorities now creates all
8955 files as readable to the file creator only, and write-protects
8956 the authority identity key.
8957 - When dumping memory usage, list bytes used in buffer memory
8959 - When running with dmalloc, dump more stats on hup and on exit.
8960 - Directory authorities now fail quickly and (relatively) harmlessly
8961 if they generate a network status document that is somehow
8964 o Traffic load balancing improvements:
8965 - If exit bandwidth ever exceeds one third of total bandwidth, then
8966 use the correct formula to weight exit nodes when choosing paths.
8967 (Based on patch from Mike Perry.)
8968 - Choose perfectly fairly among routers when choosing by bandwidth and
8969 weighting by fraction of bandwidth provided by exits. Previously, we
8970 would choose with only approximate fairness, and correct ourselves
8971 if we ran off the end of the list. [Bugfix on 0.1.2.x]
8973 o Performance improvements:
8974 - Be more aggressive with freeing buffer RAM or putting it on the
8976 - Use Critical Sections rather than Mutexes for synchronizing threads
8977 on win32; Mutexes are heavier-weight, and designed for synchronizing
8980 o Deprecated and removed features:
8981 - RedirectExits is now deprecated.
8982 - Stop allowing address masks that do not correspond to bit prefixes.
8983 We have warned about these for a really long time; now it's time
8984 to reject them. (Patch from croup.)
8986 o Minor bugfixes (directory):
8987 - Fix another crash bug related to extra-info caching. (Bug found by
8988 Peter Palfrader.) [Bugfix on 0.2.0.2-alpha]
8989 - Directories no longer return a "304 not modified" when they don't
8990 have the networkstatus the client asked for. Also fix a memory
8991 leak when returning 304 not modified. [Bugfixes on 0.2.0.2-alpha]
8992 - We had accidentally labelled 0.1.2.x directory servers as not
8993 suitable for begin_dir requests, and had labelled no directory
8994 servers as suitable for uploading extra-info documents. [Bugfix
8997 o Minor bugfixes (dns):
8998 - Fix a crash when DNSPort is set more than once. (Patch from Robert
8999 Hogan.) [Bugfix on 0.2.0.2-alpha]
9000 - Add DNSPort connections to the global connection list, so that we
9001 can time them out correctly. (Bug found by Robert Hogan.) [Bugfix
9003 - Fix a dangling reference that could lead to a crash when DNSPort is
9004 changed or closed (Patch from Robert Hogan.) [Bugfix on
9007 o Minor bugfixes (controller):
9008 - Provide DNS expiry times in GMT, not in local time. For backward
9009 compatibility, ADDRMAP events only provide GMT expiry in an extended
9010 field. "GETINFO address-mappings" always does the right thing.
9011 - Use CRLF line endings properly in NS events.
9012 - Terminate multi-line control events properly. (Original patch
9013 from tup.) [Bugfix on 0.1.2.x-alpha]
9014 - Do not include spaces in SOURCE_ADDR fields in STREAM
9015 events. Resolves bug 472. [Bugfix on 0.2.0.x-alpha]
9018 Changes in version 0.1.2.15 - 2007-07-17
9019 Tor 0.1.2.15 fixes several crash bugs, fixes some anonymity-related
9020 problems, fixes compilation on BSD, and fixes a variety of other
9021 bugs. Everybody should upgrade.
9023 o Major bugfixes (compilation):
9024 - Fix compile on FreeBSD/NetBSD/OpenBSD. Oops.
9026 o Major bugfixes (crashes):
9027 - Try even harder not to dereference the first character after
9028 an mmap(). Reported by lodger.
9029 - Fix a crash bug in directory authorities when we re-number the
9030 routerlist while inserting a new router.
9031 - When the cached-routers file is an even multiple of the page size,
9032 don't run off the end and crash. (Fixes bug 455; based on idea
9034 - Fix eventdns.c behavior on Solaris: It is critical to include
9035 orconfig.h _before_ sys/types.h, so that we can get the expected
9036 definition of _FILE_OFFSET_BITS.
9038 o Major bugfixes (security):
9039 - Fix a possible buffer overrun when using BSD natd support. Bug
9041 - When sending destroy cells from a circuit's origin, don't include
9042 the reason for tearing down the circuit. The spec says we didn't,
9043 and now we actually don't. Reported by lodger.
9044 - Keep streamids from different exits on a circuit separate. This
9045 bug may have allowed other routers on a given circuit to inject
9046 cells into streams. Reported by lodger; fixes bug 446.
9047 - If there's a never-before-connected-to guard node in our list,
9048 never choose any guards past it. This way we don't expand our
9049 guard list unless we need to.
9051 o Minor bugfixes (guard nodes):
9052 - Weight guard selection by bandwidth, so that low-bandwidth nodes
9053 don't get overused as guards.
9055 o Minor bugfixes (directory):
9056 - Correctly count the number of authorities that recommend each
9057 version. Previously, we were under-counting by 1.
9058 - Fix a potential crash bug when we load many server descriptors at
9059 once and some of them make others of them obsolete. Fixes bug 458.
9061 o Minor bugfixes (hidden services):
9062 - Stop tearing down the whole circuit when the user asks for a
9063 connection to a port that the hidden service didn't configure.
9066 o Minor bugfixes (misc):
9067 - On Windows, we were preventing other processes from reading
9068 cached-routers while Tor was running. Reported by janbar.
9069 - Fix a possible (but very unlikely) bug in picking routers by
9070 bandwidth. Add a log message to confirm that it is in fact
9071 unlikely. Patch from lodger.
9072 - Backport a couple of memory leak fixes.
9073 - Backport miscellaneous cosmetic bugfixes.
9076 Changes in version 0.2.0.2-alpha - 2007-06-02
9077 o Major bugfixes on 0.2.0.1-alpha:
9078 - Fix an assertion failure related to servers without extra-info digests.
9079 Resolves bugs 441 and 442.
9081 o Minor features (directory):
9082 - Support "If-Modified-Since" when answering HTTP requests for
9083 directories, running-routers documents, and network-status documents.
9084 (There's no need to support it for router descriptors, since those
9085 are downloaded by descriptor digest.)
9087 o Minor build issues:
9088 - Clear up some MIPSPro compiler warnings.
9089 - When building from a tarball on a machine that happens to have SVK
9090 installed, report the micro-revision as whatever version existed
9091 in the tarball, not as "x".
9094 Changes in version 0.2.0.1-alpha - 2007-06-01
9095 This early development snapshot provides new features for people running
9096 Tor as both a client and a server (check out the new RelayBandwidth
9097 config options); lets Tor run as a DNS proxy; and generally moves us
9098 forward on a lot of fronts.
9100 o Major features, server usability:
9101 - New config options RelayBandwidthRate and RelayBandwidthBurst:
9102 a separate set of token buckets for relayed traffic. Right now
9103 relayed traffic is defined as answers to directory requests, and
9104 OR connections that don't have any local circuits on them.
9106 o Major features, client usability:
9107 - A client-side DNS proxy feature to replace the need for
9108 dns-proxy-tor: Just set "DNSPort 9999", and Tor will now listen
9109 for DNS requests on port 9999, use the Tor network to resolve them
9110 anonymously, and send the reply back like a regular DNS server.
9111 The code still only implements a subset of DNS.
9112 - Make PreferTunneledDirConns and TunnelDirConns work even when
9113 we have no cached directory info. This means Tor clients can now
9114 do all of their connections protected by TLS.
9116 o Major features, performance and efficiency:
9117 - Directory authorities accept and serve "extra info" documents for
9118 routers. These documents contain fields from router descriptors
9119 that aren't usually needed, and that use a lot of excess
9120 bandwidth. Once these fields are removed from router descriptors,
9121 the bandwidth savings should be about 60%. [Partially implements
9123 - Servers upload extra-info documents to any authority that accepts
9124 them. Authorities (and caches that have been configured to download
9125 extra-info documents) download them as needed. [Partially implements
9127 - Change the way that Tor buffers data that it is waiting to write.
9128 Instead of queueing data cells in an enormous ring buffer for each
9129 client->OR or OR->OR connection, we now queue cells on a separate
9130 queue for each circuit. This lets us use less slack memory, and
9131 will eventually let us be smarter about prioritizing different kinds
9133 - Use memory pools to allocate cells with better speed and memory
9134 efficiency, especially on platforms where malloc() is inefficient.
9135 - Stop reading on edge connections when their corresponding circuit
9136 buffers are full; start again as the circuits empty out.
9138 o Major features, other:
9139 - Add an HSAuthorityRecordStats option that hidden service authorities
9140 can use to track statistics of overall hidden service usage without
9141 logging information that would be very useful to an attacker.
9142 - Start work implementing multi-level keys for directory authorities:
9143 Add a standalone tool to generate key certificates. (Proposal 103.)
9146 - Directory authorities now call routers Stable if they have an
9147 uptime of at least 30 days, even if that's not the median uptime
9148 in the network. Implements proposal 107, suggested by Kevin Bauer
9151 o Minor fixes (resource management):
9152 - Count the number of open sockets separately from the number
9153 of active connection_t objects. This will let us avoid underusing
9154 our allocated connection limit.
9155 - We no longer use socket pairs to link an edge connection to an
9156 anonymous directory connection or a DirPort test connection.
9157 Instead, we track the link internally and transfer the data
9158 in-process. This saves two sockets per "linked" connection (at the
9159 client and at the server), and avoids the nasty Windows socketpair()
9161 - Keep unused 4k and 16k buffers on free lists, rather than wasting 8k
9162 for every single inactive connection_t. Free items from the
9163 4k/16k-buffer free lists when they haven't been used for a while.
9165 o Minor features (build):
9166 - Make autoconf search for libevent, openssl, and zlib consistently.
9167 - Update deprecated macros in configure.in.
9168 - When warning about missing headers, tell the user to let us
9169 know if the compile succeeds anyway, so we can downgrade the
9171 - Include the current subversion revision as part of the version
9172 string: either fetch it directly if we're in an SVN checkout, do
9173 some magic to guess it if we're in an SVK checkout, or use
9174 the last-detected version if we're building from a .tar.gz.
9175 Use this version consistently in log messages.
9177 o Minor features (logging):
9178 - Always prepend "Bug: " to any log message about a bug.
9179 - Put a platform string (e.g. "Linux i686") in the startup log
9180 message, so when people paste just their logs, we know if it's
9181 OpenBSD or Windows or what.
9182 - When logging memory usage, break down memory used in buffers by
9185 o Minor features (directory system):
9186 - New config option V2AuthoritativeDirectory that all directory
9187 authorities should set. This will let future authorities choose
9188 not to serve V2 directory information.
9189 - Directory authorities allow multiple router descriptors and/or extra
9190 info documents to be uploaded in a single go. This will make
9191 implementing proposal 104 simpler.
9193 o Minor features (controller):
9194 - Add a new config option __DisablePredictedCircuits designed for
9195 use by the controller, when we don't want Tor to build any circuits
9197 - Let the controller specify HOP=%d as an argument to ATTACHSTREAM,
9198 so we can exit from the middle of the circuit.
9199 - Implement "getinfo status/circuit-established".
9200 - Implement "getinfo status/version/..." so a controller can tell
9201 whether the current version is recommended, and whether any versions
9202 are good, and how many authorities agree. (Patch from shibz.)
9204 o Minor features (hidden services):
9205 - Allow multiple HiddenServicePort directives with the same virtual
9206 port; when they occur, the user is sent round-robin to one
9207 of the target ports chosen at random. Partially fixes bug 393 by
9208 adding limited ad-hoc round-robining.
9210 o Minor features (other):
9212 - Add a new AutomapHostsOnResolve option: when it is enabled, any
9213 resolve request for hosts matching a given pattern causes Tor to
9214 generate an internal virtual address mapping for that host. This
9215 allows DNSPort to work sensibly with hidden service users. By
9216 default, .exit and .onion addresses are remapped; the list of
9217 patterns can be reconfigured with AutomapHostsSuffixes.
9218 - Add an "-F" option to tor-resolve to force a resolve for a .onion
9219 address. Thanks to the AutomapHostsOnResolve option, this is no
9220 longer a completely silly thing to do.
9221 - If Tor is invoked from something that isn't a shell (e.g. Vidalia),
9222 now we expand "-f ~/.tor/torrc" correctly. Suggested by Matt Edman.
9223 - Treat "2gb" when given in torrc for a bandwidth as meaning 2gb,
9224 minus 1 byte: the actual maximum declared bandwidth.
9227 - Removed support for the old binary "version 0" controller protocol.
9228 This has been deprecated since 0.1.1, and warnings have been issued
9229 since 0.1.2. When we encounter a v0 control message, we now send
9230 back an error and close the connection.
9231 - Remove the old "dns worker" server DNS code: it hasn't been default
9232 since 0.1.2.2-alpha, and all the servers seem to be using the new
9235 o Minor bugfixes (portability):
9236 - Even though Windows is equally happy with / and \ as path separators,
9237 try to use \ consistently on Windows and / consistently on Unix: it
9238 makes the log messages nicer.
9239 - Correctly report platform name on Windows 95 OSR2 and Windows 98 SE.
9240 - Read resolv.conf files correctly on platforms where read() returns
9241 partial results on small file reads.
9243 o Minor bugfixes (directory):
9244 - Correctly enforce that elements of directory objects do not appear
9245 more often than they are allowed to appear.
9246 - When we are reporting the DirServer line we just parsed, we were
9247 logging the second stanza of the key fingerprint, not the first.
9249 o Minor bugfixes (logging):
9250 - When we hit an EOF on a log (probably because we're shutting down),
9251 don't try to remove the log from the list: just mark it as
9252 unusable. (Bulletproofs against bug 222.)
9254 o Minor bugfixes (other):
9255 - In the exitlist script, only consider the most recently published
9256 server descriptor for each server. Also, when the user requests
9257 a list of servers that _reject_ connections to a given address,
9258 explicitly exclude the IPs that also have servers that accept
9259 connections to that address. (Resolves bug 405.)
9260 - Stop allowing hibernating servers to be "stable" or "fast".
9261 - On Windows, we were preventing other processes from reading
9262 cached-routers while Tor was running. (Reported by janbar)
9263 - Make the NodeFamilies config option work. (Reported by
9264 lodger -- it has never actually worked, even though we added it
9266 - Check return values from pthread_mutex functions.
9267 - Don't save non-general-purpose router descriptors to the disk cache,
9268 because we have no way of remembering what their purpose was when
9270 - Add even more asserts to hunt down bug 417.
9271 - Build without verbose warnings even on (not-yet-released) gcc 4.2.
9272 - Fix a possible (but very unlikely) bug in picking routers by bandwidth.
9273 Add a log message to confirm that it is in fact unlikely.
9275 o Minor bugfixes (controller):
9276 - Make 'getinfo fingerprint' return a 551 error if we're not a
9277 server, so we match what the control spec claims we do. Reported
9279 - Fix a typo in an error message when extendcircuit fails that
9280 caused us to not follow the \r\n-based delimiter protocol. Reported
9283 o Code simplifications and refactoring:
9284 - Stop passing around circuit_t and crypt_path_t pointers that are
9285 implicit in other procedure arguments.
9286 - Drop the old code to choke directory connections when the
9287 corresponding OR connections got full: thanks to the cell queue
9288 feature, OR conns don't get full any more.
9289 - Make dns_resolve() handle attaching connections to circuits
9290 properly, so the caller doesn't have to.
9291 - Rename wants_to_read and wants_to_write to read/write_blocked_on_bw.
9292 - Keep the connection array as a dynamic smartlist_t, rather than as
9293 a fixed-sized array. This is important, as the number of connections
9294 is becoming increasingly decoupled from the number of sockets.
9297 Changes in version 0.1.2.14 - 2007-05-25
9298 Tor 0.1.2.14 changes the addresses of two directory authorities (this
9299 change especially affects those who serve or use hidden services),
9300 and fixes several other crash- and security-related bugs.
9302 o Directory authority changes:
9303 - Two directory authorities (moria1 and moria2) just moved to new
9304 IP addresses. This change will particularly affect those who serve
9305 or use hidden services.
9307 o Major bugfixes (crashes):
9308 - If a directory server runs out of space in the connection table
9309 as it's processing a begin_dir request, it will free the exit stream
9310 but leave it attached to the circuit, leading to unpredictable
9311 behavior. (Reported by seeess, fixes bug 425.)
9312 - Fix a bug in dirserv_remove_invalid() that would cause authorities
9313 to corrupt memory under some really unlikely scenarios.
9314 - Tighten router parsing rules. (Bugs reported by Benedikt Boss.)
9315 - Avoid segfaults when reading from mmaped descriptor file. (Reported
9318 o Major bugfixes (security):
9319 - When choosing an entry guard for a circuit, avoid using guards
9320 that are in the same family as the chosen exit -- not just guards
9321 that are exactly the chosen exit. (Reported by lodger.)
9323 o Major bugfixes (resource management):
9324 - If a directory authority is down, skip it when deciding where to get
9325 networkstatus objects or descriptors. Otherwise we keep asking
9326 every 10 seconds forever. Fixes bug 384.
9327 - Count it as a failure if we fetch a valid network-status but we
9328 don't want to keep it. Otherwise we'll keep fetching it and keep
9329 not wanting to keep it. Fixes part of bug 422.
9330 - If all of our dirservers have given us bad or no networkstatuses
9331 lately, then stop hammering them once per minute even when we
9332 think they're failed. Fixes another part of bug 422.
9335 - Actually set the purpose correctly for descriptors inserted with
9337 - When we have k non-v2 authorities in our DirServer config,
9338 we ignored the last k authorities in the list when updating our
9340 - Correctly back-off from requesting router descriptors that we are
9341 having a hard time downloading.
9342 - Read resolv.conf files correctly on platforms where read() returns
9343 partial results on small file reads.
9344 - Don't rebuild the entire router store every time we get 32K of
9345 routers: rebuild it when the journal gets very large, or when
9346 the gaps in the store get very large.
9349 - When routers publish SVN revisions in their router descriptors,
9350 authorities now include those versions correctly in networkstatus
9352 - Warn when using a version of libevent before 1.3b to run a server on
9353 OSX or BSD: these versions interact badly with userspace threads.
9356 Changes in version 0.1.2.13 - 2007-04-24
9357 This release features some major anonymity fixes, such as safer path
9358 selection; better client performance; faster bootstrapping, better
9359 address detection, and better DNS support for servers; write limiting as
9360 well as read limiting to make servers easier to run; and a huge pile of
9361 other features and bug fixes. The bundles also ship with Vidalia 0.0.11.
9363 Tor 0.1.2.13 is released in memory of Rob Levin (1955-2006), aka lilo
9364 of the Freenode IRC network, remembering his patience and vision for
9365 free speech on the Internet.
9368 - Fix a memory leak when we ask for "all" networkstatuses and we
9369 get one we don't recognize.
9370 - Add more asserts to hunt down bug 417.
9371 - Disable kqueue on OS X 10.3 and earlier, to fix bug 371.
9374 Changes in version 0.1.2.12-rc - 2007-03-16
9376 - Fix an infinite loop introduced in 0.1.2.7-alpha when we serve
9377 directory information requested inside Tor connections (i.e. via
9378 begin_dir cells). It only triggered when the same connection was
9379 serving other data at the same time. Reported by seeess.
9382 - When creating a circuit via the controller, send a 'launched'
9383 event when we're done, so we follow the spec better.
9386 Changes in version 0.1.2.11-rc - 2007-03-15
9387 o Minor bugfixes (controller), reported by daejees:
9388 - Correct the control spec to match how the code actually responds
9389 to 'getinfo addr-mappings/*'.
9390 - The control spec described a GUARDS event, but the code
9391 implemented a GUARD event. Standardize on GUARD, but let people
9395 Changes in version 0.1.2.10-rc - 2007-03-07
9396 o Major bugfixes (Windows):
9397 - Do not load the NT services library functions (which may not exist)
9398 just to detect if we're a service trying to shut down. Now we run
9399 on Win98 and friends again.
9401 o Minor bugfixes (other):
9402 - Clarify a couple of log messages.
9403 - Fix a misleading socks5 error number.
9406 Changes in version 0.1.2.9-rc - 2007-03-02
9407 o Major bugfixes (Windows):
9408 - On MinGW, use "%I64u" to printf/scanf 64-bit integers, instead
9409 of the usual GCC "%llu". This prevents a bug when saving 64-bit
9410 int configuration values: the high-order 32 bits would get
9411 truncated. In particular, we were being bitten by the default
9412 MaxAdvertisedBandwidth of 128 TB turning into 0. (Fixes bug 400
9413 and maybe also bug 397.)
9415 o Minor bugfixes (performance):
9416 - Use OpenSSL's AES implementation on platforms where it's faster.
9417 This could save us as much as 10% CPU usage.
9419 o Minor bugfixes (server):
9420 - Do not rotate onion key immediately after setting it for the first
9423 o Minor bugfixes (directory authorities):
9424 - Stop calling servers that have been hibernating for a long time
9425 "stable". Also, stop letting hibernating or obsolete servers affect
9426 uptime and bandwidth cutoffs.
9427 - Stop listing hibernating servers in the v1 directory.
9429 o Minor bugfixes (hidden services):
9430 - Upload hidden service descriptors slightly less often, to reduce
9431 load on authorities.
9433 o Minor bugfixes (other):
9434 - Fix an assert that could trigger if a controller quickly set then
9435 cleared EntryNodes. Bug found by Udo van den Heuvel.
9436 - On architectures where sizeof(int)>4, still clamp declarable bandwidth
9438 - Fix a potential race condition in the rpm installer. Found by
9440 - Try to fix eventdns warnings once and for all: do not treat a dns rcode
9441 of 2 as indicating that the server is completely bad; it sometimes
9442 means that the server is just bad for the request in question. (may fix
9443 the last of bug 326.)
9444 - Disable encrypted directory connections when we don't have a server
9445 descriptor for the destination. We'll get this working again in
9449 Changes in version 0.1.2.8-beta - 2007-02-26
9450 o Major bugfixes (crashes):
9451 - Stop crashing when the controller asks us to resetconf more than
9452 one config option at once. (Vidalia 0.0.11 does this.)
9453 - Fix a crash that happened on Win98 when we're given command-line
9454 arguments: don't try to load NT service functions from advapi32.dll
9455 except when we need them. (Bug introduced in 0.1.2.7-alpha;
9457 - Fix a longstanding obscure crash bug that could occur when
9458 we run out of DNS worker processes. (Resolves bug 390.)
9460 o Major bugfixes (hidden services):
9461 - Correctly detect whether hidden service descriptor downloads are
9462 in-progress. (Suggested by Karsten Loesing; fixes bug 399.)
9464 o Major bugfixes (accounting):
9465 - When we start during an accounting interval before it's time to wake
9466 up, remember to wake up at the correct time. (May fix bug 342.)
9468 o Minor bugfixes (controller):
9469 - Give the controller END_STREAM_REASON_DESTROY events _before_ we
9470 clear the corresponding on_circuit variable, and remember later
9471 that we don't need to send a redundant CLOSED event. Resolves part
9473 - Report events where a resolve succeeded or where we got a socks
9474 protocol error correctly, rather than calling both of them
9476 - Change reported stream target addresses to IP consistently when
9477 we finally get the IP from an exit node.
9478 - Send log messages to the controller even if they happen to be very
9481 o Minor bugfixes (other):
9482 - Display correct results when reporting which versions are
9483 recommended, and how recommended they are. (Resolves bug 383.)
9484 - Improve our estimates for directory bandwidth to be less random:
9485 guess that an unrecognized directory will have the average bandwidth
9486 from all known directories, not that it will have the average
9487 bandwidth from those directories earlier than it on the list.
9488 - If we start a server with ClientOnly 1, then set ClientOnly to 0
9489 and hup, stop triggering an assert based on an empty onion_key.
9490 - On platforms with no working mmap() equivalent, don't warn the
9491 user when cached-routers doesn't exist.
9492 - Warn the user when mmap() [or its equivalent] fails for some reason
9493 other than file-not-found.
9494 - Don't warn the user when cached-routers.new doesn't exist: that's
9495 perfectly fine when starting up for the first time.
9496 - When EntryNodes are configured, rebuild the guard list to contain,
9497 in order: the EntryNodes that were guards before; the rest of the
9498 EntryNodes; the nodes that were guards before.
9499 - Mask out all signals in sub-threads; only the libevent signal
9500 handler should be processing them. This should prevent some crashes
9501 on some machines using pthreads. (Patch from coderman.)
9502 - Fix switched arguments on memset in the implementation of
9503 tor_munmap() for systems with no mmap() call.
9504 - When Tor receives a router descriptor that it asked for, but
9505 no longer wants (because it has received fresh networkstatuses
9506 in the meantime), do not warn the user. Cache the descriptor if
9507 we're a cache; drop it if we aren't.
9508 - Make earlier entry guards _really_ get retried when the network
9510 - On a malformed DNS reply, always give an error to the corresponding
9512 - Build with recent libevents on platforms that do not define the
9513 nonstandard types "u_int8_t" and friends.
9515 o Minor features (controller):
9516 - Warn the user when an application uses the obsolete binary v0
9517 control protocol. We're planning to remove support for it during
9518 the next development series, so it's good to give people some
9520 - Add STREAM_BW events to report per-entry-stream bandwidth
9521 use. (Patch from Robert Hogan.)
9522 - Rate-limit SIGNEWNYM signals in response to controllers that
9523 impolitely generate them for every single stream. (Patch from
9524 mwenge; closes bug 394.)
9525 - Make REMAP stream events have a SOURCE (cache or exit), and
9526 make them generated in every case where we get a successful
9527 connected or resolved cell.
9529 o Minor bugfixes (performance):
9530 - Call router_have_min_dir_info half as often. (This is showing up in
9531 some profiles, but not others.)
9532 - When using GCC, make log_debug never get called at all, and its
9533 arguments never get evaluated, when no debug logs are configured.
9534 (This is showing up in some profiles, but not others.)
9537 - Remove some never-implemented options. Mark PathlenCoinWeight as
9539 - Implement proposal 106: Stop requiring clients to have well-formed
9540 certificates; stop checking nicknames in certificates. (Clients
9541 have certificates so that they can look like Tor servers, but in
9542 the future we might want to allow them to look like regular TLS
9543 clients instead. Nicknames in certificates serve no purpose other
9544 than making our protocol easier to recognize on the wire.)
9545 - Revise messages on handshake failure again to be even more clear about
9546 which are incoming connections and which are outgoing.
9547 - Discard any v1 directory info that's over 1 month old (for
9548 directories) or over 1 week old (for running-routers lists).
9549 - Do not warn when individual nodes in the configuration's EntryNodes,
9550 ExitNodes, etc are down: warn only when all possible nodes
9551 are down. (Fixes bug 348.)
9552 - Always remove expired routers and networkstatus docs before checking
9553 whether we have enough information to build circuits. (Fixes
9555 - Put a lower-bound on MaxAdvertisedBandwidth.
9558 Changes in version 0.1.2.7-alpha - 2007-02-06
9559 o Major bugfixes (rate limiting):
9560 - Servers decline directory requests much more aggressively when
9561 they're low on bandwidth. Otherwise they end up queueing more and
9562 more directory responses, which can't be good for latency.
9563 - But never refuse directory requests from local addresses.
9564 - Fix a memory leak when sending a 503 response for a networkstatus
9566 - Be willing to read or write on local connections (e.g. controller
9567 connections) even when the global rate limiting buckets are empty.
9568 - If our system clock jumps back in time, don't publish a negative
9569 uptime in the descriptor. Also, don't let the global rate limiting
9570 buckets go absurdly negative.
9571 - Flush local controller connection buffers periodically as we're
9572 writing to them, so we avoid queueing 4+ megabytes of data before
9575 o Major bugfixes (NT services):
9576 - Install as NT_AUTHORITY\LocalService rather than as SYSTEM; add a
9577 command-line flag so that admins can override the default by saying
9578 "tor --service install --user "SomeUser"". This will not affect
9579 existing installed services. Also, warn the user that the service
9580 will look for its configuration file in the service user's
9581 %appdata% directory. (We can't do the 'hardwire the user's appdata
9582 directory' trick any more, since we may not have read access to that
9585 o Major bugfixes (other):
9586 - Previously, we would cache up to 16 old networkstatus documents
9587 indefinitely, if they came from nontrusted authorities. Now we
9588 discard them if they are more than 10 days old.
9589 - Fix a crash bug in the presence of DNS hijacking (reported by Andrew
9591 - Detect and reject malformed DNS responses containing circular
9593 - If exits are rare enough that we're not marking exits as guards,
9594 ignore exit bandwidth when we're deciding the required bandwidth
9596 - When we're handling a directory connection tunneled over Tor,
9597 don't fill up internal memory buffers with all the data we want
9598 to tunnel; instead, only add it if the OR connection that will
9599 eventually receive it has some room for it. (This can lead to
9600 slowdowns in tunneled dir connections; a better solution will have
9603 o Minor bugfixes (dns):
9604 - Add some defensive programming to eventdns.c in an attempt to catch
9605 possible memory-stomping bugs.
9606 - Detect and reject DNS replies containing IPv4 or IPv6 records with
9607 an incorrect number of bytes. (Previously, we would ignore the
9609 - Fix as-yet-unused reverse IPv6 lookup code so it sends nybbles
9610 in the correct order, and doesn't crash.
9611 - Free memory held in recently-completed DNS lookup attempts on exit.
9612 This was not a memory leak, but may have been hiding memory leaks.
9613 - Handle TTL values correctly on reverse DNS lookups.
9614 - Treat failure to parse resolv.conf as an error.
9616 o Minor bugfixes (other):
9617 - Fix crash with "tor --list-fingerprint" (reported by seeess).
9618 - When computing clock skew from directory HTTP headers, consider what
9619 time it was when we finished asking for the directory, not what
9621 - Expire socks connections if they spend too long waiting for the
9622 handshake to finish. Previously we would let them sit around for
9623 days, if the connecting application didn't close them either.
9624 - And if the socks handshake hasn't started, don't send a
9625 "DNS resolve socks failed" handshake reply; just close it.
9626 - Stop using C functions that OpenBSD's linker doesn't like.
9627 - Don't launch requests for descriptors unless we have networkstatuses
9628 from at least half of the authorities. This delays the first
9629 download slightly under pathological circumstances, but can prevent
9630 us from downloading a bunch of descriptors we don't need.
9631 - Do not log IPs with TLS failures for incoming TLS
9632 connections. (Fixes bug 382.)
9633 - If the user asks to use invalid exit nodes, be willing to use
9635 - Stop using the reserved ac_cv namespace in our configure script.
9636 - Call stat() slightly less often; use fstat() when possible.
9637 - Refactor the way we handle pending circuits when an OR connection
9638 completes or fails, in an attempt to fix a rare crash bug.
9639 - Only rewrite a conn's address based on X-Forwarded-For: headers
9640 if it's a parseable public IP address; and stop adding extra quotes
9641 to the resulting address.
9644 - Weight directory requests by advertised bandwidth. Now we can
9645 let servers enable write limiting but still allow most clients to
9646 succeed at their directory requests. (We still ignore weights when
9647 choosing a directory authority; I hope this is a feature.)
9650 - Create a new file ReleaseNotes which was the old ChangeLog. The
9651 new ChangeLog file now includes the summaries for all development
9653 - Check for addresses with invalid characters at the exit as well
9654 as at the client, and warn less verbosely when they fail. You can
9655 override this by setting ServerDNSAllowNonRFC953Addresses to 1.
9656 - Adapt a patch from goodell to let the contrib/exitlist script
9657 take arguments rather than require direct editing.
9658 - Inform the server operator when we decide not to advertise a
9659 DirPort due to AccountingMax enabled or a low BandwidthRate. It
9660 was confusing Zax, so now we're hopefully more helpful.
9661 - Bring us one step closer to being able to establish an encrypted
9662 directory tunnel without knowing a descriptor first. Still not
9663 ready yet. As part of the change, now assume we can use a
9664 create_fast cell if we don't know anything about a router.
9665 - Allow exit nodes to use nameservers running on ports other than 53.
9666 - Servers now cache reverse DNS replies.
9667 - Add an --ignore-missing-torrc command-line option so that we can
9668 get the "use sensible defaults if the configuration file doesn't
9669 exist" behavior even when specifying a torrc location on the command
9672 o Minor features (controller):
9673 - Track reasons for OR connection failure; make these reasons
9674 available via the controller interface. (Patch from Mike Perry.)
9675 - Add a SOCKS_BAD_HOSTNAME client status event so controllers
9676 can learn when clients are sending malformed hostnames to Tor.
9677 - Clean up documentation for controller status events.
9678 - Add a REMAP status to stream events to note that a stream's
9679 address has changed because of a cached address or a MapAddress
9683 Changes in version 0.1.2.6-alpha - 2007-01-09
9685 - Fix an assert error introduced in 0.1.2.5-alpha: if a single TLS
9686 connection handles more than 4 gigs in either direction, we crash.
9687 - Fix an assert error introduced in 0.1.2.5-alpha: if we're an
9688 advertised exit node, somebody might try to exit from us when
9689 we're bootstrapping and before we've built our descriptor yet.
9690 Refuse the connection rather than crashing.
9693 - Warn if we (as a server) find that we've resolved an address that we
9694 weren't planning to resolve.
9695 - Warn that using select() on any libevent version before 1.1 will be
9696 unnecessarily slow (even for select()).
9697 - Flush ERR-level controller status events just like we currently
9698 flush ERR-level log events, so that a Tor shutdown doesn't prevent
9699 the controller from learning about current events.
9701 o Minor features (more controller status events):
9702 - Implement EXTERNAL_ADDRESS server status event so controllers can
9703 learn when our address changes.
9704 - Implement BAD_SERVER_DESCRIPTOR server status event so controllers
9705 can learn when directories reject our descriptor.
9706 - Implement SOCKS_UNKNOWN_PROTOCOL client status event so controllers
9707 can learn when a client application is speaking a non-socks protocol
9709 - Implement DANGEROUS_SOCKS client status event so controllers
9710 can learn when a client application is leaking DNS addresses.
9711 - Implement BUG general status event so controllers can learn when
9712 Tor is unhappy about its internal invariants.
9713 - Implement CLOCK_SKEW general status event so controllers can learn
9714 when Tor thinks the system clock is set incorrectly.
9715 - Implement GOOD_SERVER_DESCRIPTOR and ACCEPTED_SERVER_DESCRIPTOR
9716 server status events so controllers can learn when their descriptors
9717 are accepted by a directory.
9718 - Implement CHECKING_REACHABILITY and REACHABILITY_{SUCCEEDED|FAILED}
9719 server status events so controllers can learn about Tor's progress in
9720 deciding whether it's reachable from the outside.
9721 - Implement BAD_LIBEVENT general status event so controllers can learn
9722 when we have a version/method combination in libevent that needs to
9724 - Implement NAMESERVER_STATUS, NAMESERVER_ALL_DOWN, DNS_HIJACKED,
9725 and DNS_USELESS server status events so controllers can learn
9726 about changes to DNS server status.
9728 o Minor features (directory):
9729 - Authorities no longer recommend exits as guards if this would shift
9730 too much load to the exit nodes.
9733 Changes in version 0.1.2.5-alpha - 2007-01-06
9735 - Enable write limiting as well as read limiting. Now we sacrifice
9736 capacity if we're pushing out lots of directory traffic, rather
9737 than overrunning the user's intended bandwidth limits.
9738 - Include TLS overhead when counting bandwidth usage; previously, we
9739 would count only the bytes sent over TLS, but not the bytes used
9741 - Support running the Tor service with a torrc not in the same
9742 directory as tor.exe and default to using the torrc located in
9743 the %appdata%\Tor\ of the user who installed the service. Patch
9745 - Servers now check for the case when common DNS requests are going to
9746 wildcarded addresses (i.e. all getting the same answer), and change
9747 their exit policy to reject *:* if it's happening.
9748 - Implement BEGIN_DIR cells, so we can connect to the directory
9749 server via TLS to do encrypted directory requests rather than
9750 plaintext. Enable via the TunnelDirConns and PreferTunneledDirConns
9751 config options if you like.
9753 o Minor features (config and docs):
9754 - Start using the state file to store bandwidth accounting data:
9755 the bw_accounting file is now obsolete. We'll keep generating it
9756 for a while for people who are still using 0.1.2.4-alpha.
9757 - Try to batch changes to the state file so that we do as few
9758 disk writes as possible while still storing important things in
9760 - The state file and the bw_accounting file get saved less often when
9761 the AvoidDiskWrites config option is set.
9762 - Make PIDFile work on Windows (untested).
9763 - Add internal descriptions for a bunch of configuration options:
9764 accessible via controller interface and in comments in saved
9766 - Reject *:563 (NNTPS) in the default exit policy. We already reject
9767 NNTP by default, so this seems like a sensible addition.
9768 - Clients now reject hostnames with invalid characters. This should
9769 avoid some inadvertent info leaks. Add an option
9770 AllowNonRFC953Hostnames to disable this behavior, in case somebody
9771 is running a private network with hosts called @, !, and #.
9772 - Add a maintainer script to tell us which options are missing
9773 documentation: "make check-docs".
9774 - Add a new address-spec.txt document to describe our special-case
9775 addresses: .exit, .onion, and .noconnnect.
9777 o Minor features (DNS):
9778 - Ongoing work on eventdns infrastructure: now it has dns server
9779 and ipv6 support. One day Tor will make use of it.
9780 - Add client-side caching for reverse DNS lookups.
9781 - Add support to tor-resolve tool for reverse lookups and SOCKS5.
9782 - When we change nameservers or IP addresses, reset and re-launch
9783 our tests for DNS hijacking.
9785 o Minor features (directory):
9786 - Authorities now specify server versions in networkstatus. This adds
9787 about 2% to the size of compressed networkstatus docs, and allows
9788 clients to tell which servers support BEGIN_DIR and which don't.
9789 The implementation is forward-compatible with a proposed future
9790 protocol version scheme not tied to Tor versions.
9791 - DirServer configuration lines now have an orport= option so
9792 clients can open encrypted tunnels to the authorities without
9793 having downloaded their descriptors yet. Enabled for moria1,
9794 moria2, tor26, and lefkada now in the default configuration.
9795 - Directory servers are more willing to send a 503 "busy" if they
9796 are near their write limit, especially for v1 directory requests.
9797 Now they can use their limited bandwidth for actual Tor traffic.
9798 - Clients track responses with status 503 from dirservers. After a
9799 dirserver has given us a 503, we try not to use it until an hour has
9800 gone by, or until we have no dirservers that haven't given us a 503.
9801 - When we get a 503 from a directory, and we're not a server, we don't
9802 count the failure against the total number of failures allowed
9803 for the thing we're trying to download.
9804 - Report X-Your-Address-Is correctly from tunneled directory
9805 connections; don't report X-Your-Address-Is when it's an internal
9806 address; and never believe reported remote addresses when they're
9808 - Protect against an unlikely DoS attack on directory servers.
9809 - Add a BadDirectory flag to network status docs so that authorities
9810 can (eventually) tell clients about caches they believe to be
9813 o Minor features (controller):
9814 - Have GETINFO dir/status/* work on hosts with DirPort disabled.
9815 - Reimplement GETINFO so that info/names stays in sync with the
9817 - Implement "GETINFO fingerprint".
9818 - Implement "SETEVENTS GUARD" so controllers can get updates on
9819 entry guard status as it changes.
9821 o Minor features (clean up obsolete pieces):
9822 - Remove some options that have been deprecated since at least
9823 0.1.0.x: AccountingMaxKB, LogFile, DebugLogFile, LogLevel, and
9824 SysLog. Use AccountingMax instead of AccountingMaxKB, and use Log
9826 - We no longer look for identity and onion keys in "identity.key" and
9827 "onion.key" -- these were replaced by secret_id_key and
9828 secret_onion_key in 0.0.8pre1.
9829 - We no longer require unrecognized directory entries to be
9832 o Major bugfixes (security):
9833 - Stop sending the HttpProxyAuthenticator string to directory
9834 servers when directory connections are tunnelled through Tor.
9835 - Clients no longer store bandwidth history in the state file.
9836 - Do not log introduction points for hidden services if SafeLogging
9838 - When generating bandwidth history, round down to the nearest
9839 1k. When storing accounting data, round up to the nearest 1k.
9840 - When we're running as a server, remember when we last rotated onion
9841 keys, so that we will rotate keys once they're a week old even if
9842 we never stay up for a week ourselves.
9844 o Major bugfixes (other):
9845 - Fix a longstanding bug in eventdns that prevented the count of
9846 timed-out resolves from ever being reset. This bug caused us to
9847 give up on a nameserver the third time it timed out, and try it
9848 10 seconds later... and to give up on it every time it timed out
9850 - Take out the '5 second' timeout from the connection retry
9851 schedule. Now the first connect attempt will wait a full 10
9852 seconds before switching to a new circuit. Perhaps this will help
9853 a lot. Based on observations from Mike Perry.
9854 - Fix a bug on the Windows implementation of tor_mmap_file() that
9855 would prevent the cached-routers file from ever loading. Reported
9859 - Fix an assert failure when a directory authority sets
9860 AuthDirRejectUnlisted and then receives a descriptor from an
9861 unlisted router. Reported by seeess.
9862 - Avoid a double-free when parsing malformed DirServer lines.
9863 - Fix a bug when a BSD-style PF socket is first used. Patch from
9865 - Fix a bug in 0.1.2.2-alpha that prevented clients from asking
9866 to resolve an address at a given exit node even when they ask for
9868 - Servers no longer ever list themselves in their "family" line,
9869 even if configured to do so. This makes it easier to configure
9870 family lists conveniently.
9871 - When running as a server, don't fall back to 127.0.0.1 when no
9872 nameservers are configured in /etc/resolv.conf; instead, make the
9873 user fix resolv.conf or specify nameservers explicitly. (Resolves
9875 - Stop accepting certain malformed ports in configured exit policies.
9876 - Don't re-write the fingerprint file every restart, unless it has
9878 - Stop warning when a single nameserver fails: only warn when _all_ of
9879 our nameservers have failed. Also, when we only have one nameserver,
9880 raise the threshold for deciding that the nameserver is dead.
9881 - Directory authorities now only decide that routers are reachable
9882 if their identity keys are as expected.
9883 - When the user uses bad syntax in the Log config line, stop
9884 suggesting other bad syntax as a replacement.
9885 - Correctly detect ipv6 DNS capability on OpenBSD.
9887 o Minor bugfixes (controller):
9888 - Report the circuit number correctly in STREAM CLOSED events. Bug
9889 reported by Mike Perry.
9890 - Do not report bizarre values for results of accounting GETINFOs
9891 when the last second's write or read exceeds the allotted bandwidth.
9892 - Report "unrecognized key" rather than an empty string when the
9893 controller tries to fetch a networkstatus that doesn't exist.
9896 Changes in version 0.1.1.26 - 2006-12-14
9897 o Security bugfixes:
9898 - Stop sending the HttpProxyAuthenticator string to directory
9899 servers when directory connections are tunnelled through Tor.
9900 - Clients no longer store bandwidth history in the state file.
9901 - Do not log introduction points for hidden services if SafeLogging
9905 - Fix an assert failure when a directory authority sets
9906 AuthDirRejectUnlisted and then receives a descriptor from an
9907 unlisted router (reported by seeess).
9910 Changes in version 0.1.2.4-alpha - 2006-12-03
9912 - Add support for using natd; this allows FreeBSDs earlier than
9913 5.1.2 to have ipfw send connections through Tor without using
9914 SOCKS. (Patch from Zajcev Evgeny with tweaks from tup.)
9917 - Make all connections to addresses of the form ".noconnect"
9918 immediately get closed. This lets application/controller combos
9919 successfully test whether they're talking to the same Tor by
9920 watching for STREAM events.
9921 - Make cross.sh cross-compilation script work even when autogen.sh
9922 hasn't been run. (Patch from Michael Mohr.)
9923 - Statistics dumped by -USR2 now include a breakdown of public key
9924 operations, for profiling.
9927 - Fix a major leak when directory authorities parse their
9928 approved-routers list, a minor memory leak when we fail to pick
9929 an exit node, and a few rare leaks on errors.
9930 - Handle TransPort connections even when the server sends data before
9931 the client sends data. Previously, the connection would just hang
9932 until the client sent data. (Patch from tup based on patch from
9934 - Avoid assert failure when our cached-routers file is empty on
9938 - Don't log spurious warnings when we see a circuit close reason we
9939 don't recognize; it's probably just from a newer version of Tor.
9940 - Have directory authorities allow larger amounts of drift in uptime
9941 without replacing the server descriptor: previously, a server that
9942 restarted every 30 minutes could have 48 "interesting" descriptors
9944 - Start linking to the Tor specification and Tor reference manual
9945 correctly in the Windows installer.
9946 - Add Vidalia to the OS X uninstaller script, so when we uninstall
9947 Tor/Privoxy we also uninstall Vidalia.
9948 - Resume building on Irix64, and fix a lot of warnings from its
9950 - Don't corrupt last_guessed_ip in router_new_address_suggestion()
9951 when we're running as a client.
9954 Changes in version 0.1.1.25 - 2006-11-04
9956 - When a client asks us to resolve (rather than connect to)
9957 an address, and we have a cached answer, give them the cached
9958 answer. Previously, we would give them no answer at all.
9959 - We were building exactly the wrong circuits when we predict
9960 hidden service requirements, meaning Tor would have to build all
9961 its circuits on demand.
9962 - If none of our live entry guards have a high uptime, but we
9963 require a guard with a high uptime, try adding a new guard before
9964 we give up on the requirement. This patch should make long-lived
9965 connections more stable on average.
9966 - When testing reachability of our DirPort, don't launch new
9967 tests when there's already one in progress -- unreachable
9968 servers were stacking up dozens of testing streams.
9970 o Security bugfixes:
9971 - When the user sends a NEWNYM signal, clear the client-side DNS
9972 cache too. Otherwise we continue to act on previous information.
9975 - Avoid a memory corruption bug when creating a hash table for
9977 - Avoid possibility of controller-triggered crash when misusing
9978 certain commands from a v0 controller on platforms that do not
9979 handle printf("%s",NULL) gracefully.
9980 - Avoid infinite loop on unexpected controller input.
9981 - Don't log spurious warnings when we see a circuit close reason we
9982 don't recognize; it's probably just from a newer version of Tor.
9983 - Add Vidalia to the OS X uninstaller script, so when we uninstall
9984 Tor/Privoxy we also uninstall Vidalia.
9987 Changes in version 0.1.2.3-alpha - 2006-10-29
9989 - Prepare for servers to publish descriptors less often: never
9990 discard a descriptor simply for being too old until either it is
9991 recommended by no authorities, or until we get a better one for
9992 the same router. Make caches consider retaining old recommended
9993 routers for even longer.
9994 - If most authorities set a BadExit flag for a server, clients
9995 don't think of it as a general-purpose exit. Clients only consider
9996 authorities that advertise themselves as listing bad exits.
9997 - Directory servers now provide 'Pragma: no-cache' and 'Expires'
9998 headers for content, so that we can work better in the presence of
9999 caching HTTP proxies.
10000 - Allow authorities to list nodes as bad exits by fingerprint or by
10003 o Minor features, controller:
10004 - Add a REASON field to CIRC events; for backward compatibility, this
10005 field is sent only to controllers that have enabled the extended
10006 event format. Also, add additional reason codes to explain why
10007 a given circuit has been destroyed or truncated. (Patches from
10009 - Add a REMOTE_REASON field to extended CIRC events to tell the
10010 controller about why a remote OR told us to close a circuit.
10011 - Stream events also now have REASON and REMOTE_REASON fields,
10012 working much like those for circuit events.
10013 - There's now a GETINFO ns/... field so that controllers can ask Tor
10014 about the current status of a router.
10015 - A new event type "NS" to inform a controller when our opinion of
10016 a router's status has changed.
10017 - Add a GETINFO events/names and GETINFO features/names so controllers
10018 can tell which events and features are supported.
10019 - A new CLEARDNSCACHE signal to allow controllers to clear the
10020 client-side DNS cache without expiring circuits.
10022 o Security bugfixes:
10023 - When the user sends a NEWNYM signal, clear the client-side DNS
10024 cache too. Otherwise we continue to act on previous information.
10027 - Avoid sending junk to controllers or segfaulting when a controller
10028 uses EVENT_NEW_DESC with verbose nicknames.
10029 - Stop triggering asserts if the controller tries to extend hidden
10030 service circuits (reported by mwenge).
10031 - Avoid infinite loop on unexpected controller input.
10032 - When the controller does a "GETINFO network-status", tell it
10033 about even those routers whose descriptors are very old, and use
10034 long nicknames where appropriate.
10035 - Change NT service functions to be loaded on demand. This lets us
10036 build with MinGW without breaking Tor for Windows 98 users.
10037 - Do DirPort reachability tests less often, since a single test
10038 chews through many circuits before giving up.
10039 - In the hidden service example in torrc.sample, stop recommending
10040 esoteric and discouraged hidden service options.
10041 - When stopping an NT service, wait up to 10 sec for it to actually
10042 stop. Patch from Matt Edman; resolves bug 295.
10043 - Fix handling of verbose nicknames with ORCONN controller events:
10044 make them show up exactly when requested, rather than exactly when
10046 - When reporting verbose nicknames in entry_guards_getinfo(), avoid
10047 printing a duplicate "$" in the keys we send (reported by mwenge).
10048 - Correctly set maximum connection limit on Cygwin. (This time
10050 - Try to detect Windows correctly when cross-compiling.
10051 - Detect the size of the routers file correctly even if it is
10052 corrupted (on systems without mmap) or not page-aligned (on systems
10053 with mmap). This bug was harmless.
10054 - Sometimes we didn't bother sending a RELAY_END cell when an attempt
10055 to open a stream fails; now we do in more cases. This should
10056 make clients able to find a good exit faster in some cases, since
10057 unhandleable requests will now get an error rather than timing out.
10058 - Resolve two memory leaks when rebuilding the on-disk router cache
10059 (reported by fookoowa).
10060 - Clean up minor code warnings suggested by the MIPSpro C compiler,
10061 and reported by some Centos users.
10062 - Controller signals now work on non-Unix platforms that don't define
10063 SIGUSR1 and SIGUSR2 the way we expect.
10064 - Patch from Michael Mohr to contrib/cross.sh, so it checks more
10065 values before failing, and always enables eventdns.
10066 - Libevent-1.2 exports, but does not define in its headers, strlcpy.
10067 Try to fix this in configure.in by checking for most functions
10068 before we check for libevent.
10071 Changes in version 0.1.2.2-alpha - 2006-10-07
10073 - Make our async eventdns library on-by-default for Tor servers,
10074 and plan to deprecate the separate dnsworker threads.
10075 - Add server-side support for "reverse" DNS lookups (using PTR
10076 records so clients can determine the canonical hostname for a given
10077 IPv4 address). Only supported by servers using eventdns; servers
10078 now announce in their descriptors whether they support eventdns.
10079 - Specify and implement client-side SOCKS5 interface for reverse DNS
10080 lookups (see doc/socks-extensions.txt).
10081 - Add a BEGIN_DIR relay cell type for an easier in-protocol way to
10082 connect to directory servers through Tor. Previously, clients needed
10083 to find Tor exits to make private connections to directory servers.
10084 - Avoid choosing Exit nodes for entry or middle hops when the
10085 total bandwidth available from non-Exit nodes is much higher than
10086 the total bandwidth available from Exit nodes.
10087 - Workaround for name servers (like Earthlink's) that hijack failing
10088 DNS requests and replace the no-such-server answer with a "helpful"
10089 redirect to an advertising-driven search portal. Also work around
10090 DNS hijackers who "helpfully" decline to hijack known-invalid
10091 RFC2606 addresses. Config option "ServerDNSDetectHijacking 0"
10092 lets you turn it off.
10093 - Send out a burst of long-range padding cells once we've established
10094 that we're reachable. Spread them over 4 circuits, so hopefully
10095 a few will be fast. This exercises our bandwidth and bootstraps
10096 us into the directory more quickly.
10098 o New/improved config options:
10099 - Add new config option "ResolvConf" to let the server operator
10100 choose an alternate resolve.conf file when using eventdns.
10101 - Add an "EnforceDistinctSubnets" option to control our "exclude
10102 servers on the same /16" behavior. It's still on by default; this
10103 is mostly for people who want to operate private test networks with
10104 all the machines on the same subnet.
10105 - If one of our entry guards is on the ExcludeNodes list, or the
10106 directory authorities don't think it's a good guard, treat it as
10107 if it were unlisted: stop using it as a guard, and throw it off
10108 the guards list if it stays that way for a long time.
10109 - Allow directory authorities to be marked separately as authorities
10110 for the v1 directory protocol, the v2 directory protocol, and
10111 as hidden service directories, to make it easier to retire old
10112 authorities. V1 authorities should set "HSAuthoritativeDir 1"
10113 to continue being hidden service authorities too.
10114 - Remove 8888 as a LongLivedPort, and add 6697 (IRCS).
10116 o Minor features, controller:
10117 - Fix CIRC controller events so that controllers can learn the
10118 identity digests of non-Named servers used in circuit paths.
10119 - Let controllers ask for more useful identifiers for servers. Instead
10120 of learning identity digests for un-Named servers and nicknames
10121 for Named servers, the new identifiers include digest, nickname,
10122 and indication of Named status. Off by default; see control-spec.txt
10123 for more information.
10124 - Add a "getinfo address" controller command so it can display Tor's
10125 best guess to the user.
10126 - New controller event to alert the controller when our server
10127 descriptor has changed.
10128 - Give more meaningful errors on controller authentication failure.
10130 o Minor features, other:
10131 - When asked to resolve a hostname, don't use non-exit servers unless
10132 requested to do so. This allows servers with broken DNS to be
10133 useful to the network.
10134 - Divide eventdns log messages into warn and info messages.
10135 - Reserve the nickname "Unnamed" for routers that can't pick
10136 a hostname: any router can call itself Unnamed; directory
10137 authorities will never allocate Unnamed to any particular router;
10138 clients won't believe that any router is the canonical Unnamed.
10139 - Only include function names in log messages for info/debug messages.
10140 For notice/warn/err, the content of the message should be clear on
10141 its own, and printing the function name only confuses users.
10142 - Avoid some false positives during reachability testing: don't try
10143 to test via a server that's on the same /24 as us.
10144 - If we fail to build a circuit to an intended enclave, and it's
10145 not mandatory that we use that enclave, stop wanting it.
10146 - When eventdns is enabled, allow multithreaded builds on NetBSD and
10147 OpenBSD. (We had previously disabled threads on these platforms
10148 because they didn't have working thread-safe resolver functions.)
10150 o Major bugfixes, anonymity/security:
10151 - If a client asked for a server by name, and there's a named server
10152 in our network-status but we don't have its descriptor yet, we
10153 could return an unnamed server instead.
10154 - Fix NetBSD bug that could allow someone to force uninitialized RAM
10155 to be sent to a server's DNS resolver. This only affects NetBSD
10156 and other platforms that do not bounds-check tolower().
10157 - Reject (most) attempts to use Tor circuits with length one. (If
10158 many people start using Tor as a one-hop proxy, exit nodes become
10159 a more attractive target for compromise.)
10160 - Just because your DirPort is open doesn't mean people should be
10161 able to remotely teach you about hidden service descriptors. Now
10162 only accept rendezvous posts if you've got HSAuthoritativeDir set.
10164 o Major bugfixes, other:
10165 - Don't crash on race condition in dns.c: tor_assert(!resolve->expire)
10166 - When a client asks the server to resolve (not connect to)
10167 an address, and it has a cached answer, give them the cached answer.
10168 Previously, the server would give them no answer at all.
10169 - Allow really slow clients to not hang up five minutes into their
10170 directory downloads (suggested by Adam J. Richter).
10171 - We were building exactly the wrong circuits when we anticipated
10172 hidden service requirements, meaning Tor would have to build all
10173 its circuits on demand.
10174 - Avoid crashing when we mmap a router cache file of size 0.
10175 - When testing reachability of our DirPort, don't launch new
10176 tests when there's already one in progress -- unreachable
10177 servers were stacking up dozens of testing streams.
10179 o Minor bugfixes, correctness:
10180 - If we're a directory mirror and we ask for "all" network status
10181 documents, we would discard status documents from authorities
10182 we don't recognize.
10183 - Avoid a memory corruption bug when creating a hash table for
10185 - Avoid controller-triggered crash when misusing certain commands
10186 from a v0 controller on platforms that do not handle
10187 printf("%s",NULL) gracefully.
10188 - Don't crash when a controller sends a third argument to an
10189 "extendcircuit" request.
10190 - Controller protocol fixes: fix encoding in "getinfo addr-mappings"
10191 response; fix error code when "getinfo dir/status/" fails.
10192 - Avoid crash when telling controller stream-status and a stream
10194 - Patch from Adam Langley to fix assert() in eventdns.c.
10195 - Fix a debug log message in eventdns to say "X resolved to Y"
10196 instead of "X resolved to X".
10197 - Make eventdns give strings for DNS errors, not just error numbers.
10198 - Track unreachable entry guards correctly: don't conflate
10199 'unreachable by us right now' with 'listed as down by the directory
10200 authorities'. With the old code, if a guard was unreachable by
10201 us but listed as running, it would clog our guard list forever.
10202 - Behave correctly in case we ever have a network with more than
10203 2GB/s total advertised capacity.
10204 - Make TrackExitHosts case-insensitive, and fix the behavior of
10205 ".suffix" TrackExitHosts items to avoid matching in the middle of
10207 - Finally fix the openssl warnings from newer gccs that believe that
10208 ignoring a return value is okay, but casting a return value and
10209 then ignoring it is a sign of madness.
10210 - Prevent the contrib/exitlist script from printing the same
10211 result more than once.
10212 - Patch from Steve Hildrey: Generate network status correctly on
10213 non-versioning dirservers.
10214 - Don't listen to the X-Your-Address-Is hint if you did the lookup
10215 via Tor; otherwise you'll think you're the exit node's IP address.
10217 o Minor bugfixes, performance:
10218 - Two small performance improvements on parsing descriptors.
10219 - Major performance improvement on inserting descriptors: change
10220 algorithm from O(n^2) to O(n).
10221 - Make the common memory allocation path faster on machines where
10222 malloc(0) returns a pointer.
10223 - Start remembering X-Your-Address-Is directory hints even if you're
10224 a client, so you can become a server more smoothly.
10225 - Avoid duplicate entries on MyFamily line in server descriptor.
10227 o Packaging, features:
10228 - Remove architecture from OS X builds. The official builds are
10229 now universal binaries.
10230 - The Debian package now uses --verify-config when (re)starting,
10231 to distinguish configuration errors from other errors.
10232 - Update RPMs to require libevent 1.1b.
10234 o Packaging, bugfixes:
10235 - Patches so Tor builds with MinGW on Windows.
10236 - Patches so Tor might run on Cygwin again.
10237 - Resume building on non-gcc compilers and ancient gcc. Resume
10238 building with the -O0 compile flag. Resume building cleanly on
10240 - Run correctly on OS X platforms with case-sensitive filesystems.
10241 - Correct includes for net/if.h and net/pfvar.h on OpenBSD (from Tup).
10242 - Add autoconf checks so Tor can build on Solaris x86 again.
10245 - Documented (and renamed) ServerDNSSearchDomains and
10246 ServerDNSResolvConfFile options.
10247 - Be clearer that the *ListenAddress directives can be repeated
10251 Changes in version 0.1.1.24 - 2006-09-29
10253 - Allow really slow clients to not hang up five minutes into their
10254 directory downloads (suggested by Adam J. Richter).
10255 - Fix major performance regression from 0.1.0.x: instead of checking
10256 whether we have enough directory information every time we want to
10257 do something, only check when the directory information has changed.
10258 This should improve client CPU usage by 25-50%.
10259 - Don't crash if, after a server has been running for a while,
10260 it can't resolve its hostname.
10263 - Allow Tor to start when RunAsDaemon is set but no logs are set.
10264 - Don't crash when the controller receives a third argument to an
10265 "extendcircuit" request.
10266 - Controller protocol fixes: fix encoding in "getinfo addr-mappings"
10267 response; fix error code when "getinfo dir/status/" fails.
10268 - Fix configure.in to not produce broken configure files with
10269 more recent versions of autoconf. Thanks to Clint for his auto*
10271 - Fix security bug on NetBSD that could allow someone to force
10272 uninitialized RAM to be sent to a server's DNS resolver. This
10273 only affects NetBSD and other platforms that do not bounds-check
10275 - Warn user when using libevent 1.1a or earlier with win32 or kqueue
10276 methods: these are known to be buggy.
10277 - If we're a directory mirror and we ask for "all" network status
10278 documents, we would discard status documents from authorities
10279 we don't recognize.
10282 Changes in version 0.1.2.1-alpha - 2006-08-27
10284 - Add "eventdns" async dns library from Adam Langley, tweaked to
10285 build on OSX and Windows. Only enabled if you pass the
10286 --enable-eventdns argument to configure.
10287 - Allow servers with no hostname or IP address to learn their
10288 IP address by asking the directory authorities. This code only
10289 kicks in when you would normally have exited with a "no address"
10290 error. Nothing's authenticated, so use with care.
10291 - Rather than waiting a fixed amount of time between retrying
10292 application connections, we wait only 5 seconds for the first,
10293 10 seconds for the second, and 15 seconds for each retry after
10294 that. Hopefully this will improve the expected user experience.
10295 - Patch from Tup to add support for transparent AP connections:
10296 this basically bundles the functionality of trans-proxy-tor
10297 into the Tor mainline. Now hosts with compliant pf/netfilter
10298 implementations can redirect TCP connections straight to Tor
10299 without diverting through SOCKS. Needs docs.
10300 - Busy directory servers save lots of memory by spooling server
10301 descriptors, v1 directories, and v2 networkstatus docs to buffers
10302 as needed rather than en masse. Also mmap the cached-routers
10303 files, so we don't need to keep the whole thing in memory too.
10304 - Automatically avoid picking more than one node from the same
10305 /16 network when constructing a circuit.
10306 - Revise and clean up the torrc.sample that we ship with; add
10307 a section for BandwidthRate and BandwidthBurst.
10310 - Split circuit_t into origin_circuit_t and or_circuit_t, and
10311 split connection_t into edge, or, dir, control, and base structs.
10312 These will save quite a bit of memory on busy servers, and they'll
10313 also help us track down bugs in the code and bugs in the spec.
10314 - Experimentally re-enable kqueue on OSX when using libevent 1.1b
10315 or later. Log when we are doing this, so we can diagnose it when
10316 it fails. (Also, recommend libevent 1.1b for kqueue and
10317 win32 methods; deprecate libevent 1.0b harder; make libevent
10318 recommendation system saner.)
10319 - Start being able to build universal binaries on OS X (thanks
10321 - Export the default exit policy via the control port, so controllers
10322 don't need to guess what it is / will be later.
10323 - Add a man page entry for ProtocolWarnings.
10324 - Add TestVia config option to the man page.
10325 - Remove even more protocol-related warnings from Tor server logs,
10326 such as bad TLS handshakes and malformed begin cells.
10327 - Stop fetching descriptors if you're not a dir mirror and you
10328 haven't tried to establish any circuits lately. [This currently
10329 causes some dangerous behavior, because when you start up again
10330 you'll use your ancient server descriptors.]
10331 - New DirPort behavior: if you have your dirport set, you download
10332 descriptors aggressively like a directory mirror, whether or not
10333 your ORPort is set.
10334 - Get rid of the router_retry_connections notion. Now routers
10335 no longer try to rebuild long-term connections to directory
10336 authorities, and directory authorities no longer try to rebuild
10337 long-term connections to all servers. We still don't hang up
10338 connections in these two cases though -- we need to look at it
10339 more carefully to avoid flapping, and we likely need to wait til
10340 0.1.1.x is obsolete.
10341 - Drop compatibility with obsolete Tors that permit create cells
10342 to have the wrong circ_id_type.
10343 - Re-enable per-connection rate limiting. Get rid of the "OP
10344 bandwidth" concept. Lay groundwork for "bandwidth classes" --
10345 separate global buckets that apply depending on what sort of conn
10347 - Start publishing one minute or so after we find our ORPort
10348 to be reachable. This will help reduce the number of descriptors
10349 we have for ourselves floating around, since it's quite likely
10350 other things (e.g. DirPort) will change during that minute too.
10351 - Fork the v1 directory protocol into its own spec document,
10352 and mark dir-spec.txt as the currently correct (v2) spec.
10355 - When we find our DirPort to be reachable, publish a new descriptor
10356 so we'll tell the world (reported by pnx).
10357 - Publish a new descriptor after we hup/reload. This is important
10358 if our config has changed such that we'll want to start advertising
10359 our DirPort now, etc.
10360 - Allow Tor to start when RunAsDaemon is set but no logs are set.
10361 - When we have a state file we cannot parse, tell the user and
10362 move it aside. Now we avoid situations where the user starts
10363 Tor in 1904, Tor writes a state file with that timestamp in it,
10364 the user fixes her clock, and Tor refuses to start.
10365 - Fix configure.in to not produce broken configure files with
10366 more recent versions of autoconf. Thanks to Clint for his auto*
10368 - "tor --verify-config" now exits with -1(255) or 0 depending on
10369 whether the config options are bad or good.
10370 - Resolve bug 321 when using dnsworkers: append a period to every
10371 address we resolve at the exit node, so that we do not accidentally
10372 pick up local addresses, and so that failing searches are retried
10373 in the resolver search domains. (This is already solved for
10374 eventdns.) (This breaks Blossom servers for now.)
10375 - If we are using an exit enclave and we can't connect, e.g. because
10376 its webserver is misconfigured to not listen on localhost, then
10377 back off and try connecting from somewhere else before we fail.
10380 - Start compiling on MinGW on Windows (patches from Mike Chiussi).
10381 - Start compiling on MSVC6 on Windows (patches from Frediano Ziglio).
10382 - Fix bug 314: Tor clients issued "unsafe socks" warnings even
10383 when the IP address is mapped through MapAddress to a hostname.
10384 - Start passing "ipv4" hints to getaddrinfo(), so servers don't do
10385 useless IPv6 DNS resolves.
10386 - Patch suggested by Karsten Loesing: respond to SIGNAL command
10387 before we execute the signal, in case the signal shuts us down.
10388 - Clean up AllowInvalidNodes man page entry.
10389 - Claim a commonname of Tor, rather than TOR, in TLS handshakes.
10390 - Add more asserts to track down an assert error on a windows Tor
10391 server with connection_add being called with socket == -1.
10392 - Handle reporting OR_CONN_EVENT_NEW events to the controller.
10393 - Fix misleading log messages: an entry guard that is "unlisted",
10394 as well as not known to be "down" (because we've never heard
10395 of it), is not therefore "up".
10396 - Remove code to special-case "-cvs" ending, since it has not
10397 actually mattered since 0.0.9.
10398 - Make our socks5 handling more robust to broken socks clients:
10399 throw out everything waiting on the buffer in between socks
10400 handshake phases, since they can't possibly (so the theory
10401 goes) have predicted what we plan to respond to them.
10404 Changes in version 0.1.1.23 - 2006-07-30
10406 - Fast Tor servers, especially exit nodes, were triggering asserts
10407 due to a bug in handling the list of pending DNS resolves. Some
10408 bugs still remain here; we're hunting them.
10409 - Entry guards could crash clients by sending unexpected input.
10410 - More fixes on reachability testing: if you find yourself reachable,
10411 then don't ever make any client requests (so you stop predicting
10412 circuits), then hup or have your clock jump, then later your IP
10413 changes, you won't think circuits are working, so you won't try to
10414 test reachability, so you won't publish.
10417 - Avoid a crash if the controller does a resetconf firewallports
10418 and then a setconf fascistfirewall=1.
10419 - Avoid an integer underflow when the dir authority decides whether
10420 a router is stable: we might wrongly label it stable, and compute
10421 a slightly wrong median stability, when a descriptor is published
10423 - Fix a place where we might trigger an assert if we can't build our
10424 own server descriptor yet.
10427 Changes in version 0.1.1.22 - 2006-07-05
10429 - Fix a big bug that was causing servers to not find themselves
10430 reachable if they changed IP addresses. Since only 0.1.1.22+
10431 servers can do reachability testing correctly, now we automatically
10432 make sure to test via one of these.
10433 - Fix to allow clients and mirrors to learn directory info from
10434 descriptor downloads that get cut off partway through.
10435 - Directory authorities had a bug in deciding if a newly published
10436 descriptor was novel enough to make everybody want a copy -- a few
10437 servers seem to be publishing new descriptors many times a minute.
10439 - Fix a rare bug that was causing some servers to complain about
10440 "closing wedged cpuworkers" and skip some circuit create requests.
10441 - Make the Exit flag in directory status documents actually work.
10444 Changes in version 0.1.1.21 - 2006-06-10
10445 o Crash and assert fixes from 0.1.1.20:
10446 - Fix a rare crash on Tor servers that have enabled hibernation.
10447 - Fix a seg fault on startup for Tor networks that use only one
10448 directory authority.
10449 - Fix an assert from a race condition that occurs on Tor servers
10450 while exiting, where various threads are trying to log that they're
10451 exiting, and delete the logs, at the same time.
10452 - Make our unit tests pass again on certain obscure platforms.
10455 - Add support for building SUSE RPM packages.
10456 - Speed up initial bootstrapping for clients: if we are making our
10457 first ever connection to any entry guard, then don't mark it down
10459 - When only one Tor server in the network is labelled as a guard,
10460 and we've already picked him, we would cycle endlessly picking him
10461 again, being unhappy about it, etc. Now we specifically exclude
10462 current guards when picking a new guard.
10463 - Servers send create cells more reliably after the TLS connection
10464 is established: we were sometimes forgetting to send half of them
10465 when we had more than one pending.
10466 - If we get a create cell that asks us to extend somewhere, but the
10467 Tor server there doesn't match the expected digest, we now send
10468 a destroy cell back, rather than silently doing nothing.
10469 - Make options->RedirectExit work again.
10470 - Make cookie authentication for the controller work again.
10471 - Stop being picky about unusual characters in the arguments to
10472 mapaddress. It's none of our business.
10473 - Add a new config option "TestVia" that lets you specify preferred
10474 middle hops to use for test circuits. Perhaps this will let me
10475 debug the reachability problems better.
10477 o Log / documentation fixes:
10478 - If we're a server and some peer has a broken TLS certificate, don't
10479 log about it unless ProtocolWarnings is set, i.e., we want to hear
10480 about protocol violations by others.
10481 - Fix spelling of VirtualAddrNetwork in man page.
10482 - Add a better explanation at the top of the autogenerated torrc file
10483 about what happened to our old torrc.
10486 Changes in version 0.1.1.20 - 2006-05-23
10488 - Downgrade a log severity where servers complain that they're
10490 - Avoid a compile warning on FreeBSD.
10491 - Remove string size limit on NEWDESC messages; solve bug 291.
10492 - Correct the RunAsDaemon entry in the man page; ignore RunAsDaemon
10493 more thoroughly when we're running on windows.
10496 Changes in version 0.1.1.19-rc - 2006-05-03
10498 - Regenerate our local descriptor if it's dirty and we try to use
10499 it locally (e.g. if it changes during reachability detection).
10500 - If we setconf our ORPort to 0, we continued to listen on the
10501 old ORPort and receive connections.
10502 - Avoid a second warning about machine/limits.h on Debian
10504 - Be willing to add our own routerinfo into the routerlist.
10505 Now authorities will include themselves in their directories
10506 and network-statuses.
10507 - Stop trying to upload rendezvous descriptors to every
10508 directory authority: only try the v1 authorities.
10509 - Servers no longer complain when they think they're not
10510 registered with the directory authorities. There were too many
10512 - Backport dist-rpm changes so rpms can be built without errors.
10515 - Implement an option, VirtualAddrMask, to set which addresses
10516 get handed out in response to mapaddress requests. This works
10517 around a bug in tsocks where 127.0.0.0/8 is never socksified.
10520 Changes in version 0.1.1.18-rc - 2006-04-10
10522 - Work harder to download live network-statuses from all the
10523 directory authorities we know about. Improve the threshold
10524 decision logic so we're more robust to edge cases.
10525 - When fetching rendezvous descriptors, we were willing to ask
10526 v2 authorities too, which would always return 404.
10529 - Stop listing down or invalid nodes in the v1 directory. This will
10530 reduce its bulk by about 1/3, and reduce load on directory
10532 - When deciding whether a router is Fast or Guard-worthy, consider
10533 his advertised BandwidthRate and not just the BandwidthCapacity.
10534 - No longer ship INSTALL and README files -- they are useless now.
10535 - Force rpmbuild to behave and honor target_cpu.
10536 - Avoid warnings about machine/limits.h on Debian GNU/kFreeBSD.
10537 - Start to include translated versions of the tor-doc-*.html
10538 files, along with the screenshots. Still needs more work.
10539 - Start sending back 512 and 451 errors if mapaddress fails,
10540 rather than not sending anything back at all.
10541 - When we fail to bind or listen on an incoming or outgoing
10542 socket, we should close it before failing. otherwise we just
10543 leak it. (thanks to weasel for finding.)
10544 - Allow "getinfo dir/status/foo" to work, as long as your DirPort
10545 is enabled. (This is a hack, and will be fixed in 0.1.2.x.)
10546 - Make NoPublish (even though deprecated) work again.
10547 - Fix a minor security flaw where a versioning auth dirserver
10548 could list a recommended version many times in a row to make
10549 clients more convinced that it's recommended.
10550 - Fix crash bug if there are two unregistered servers running
10551 with the same nickname, one of them is down, and you ask for
10552 them by nickname in your EntryNodes or ExitNodes. Also, try
10553 to pick the one that's running rather than an arbitrary one.
10554 - Fix an infinite loop we could hit if we go offline for too long.
10555 - Complain when we hit WSAENOBUFS on recv() or write() too.
10556 Perhaps this will help us hunt the bug.
10557 - If you're not a versioning dirserver, don't put the string
10558 "client-versions \nserver-versions \n" in your network-status.
10559 - Lower the minimum required number of file descriptors to 1000,
10560 so we can have some overhead for Valgrind on Linux, where the
10561 default ulimit -n is 1024.
10564 - Add tor.dizum.com as the fifth authoritative directory server.
10565 - Add a new config option FetchUselessDescriptors, off by default,
10566 for when you plan to run "exitlist" on your client and you want
10567 to know about even the non-running descriptors.
10570 Changes in version 0.1.1.17-rc - 2006-03-28
10572 - Clients and servers since 0.1.1.10-alpha have been expiring
10573 connections whenever they are idle for 5 minutes and they *do*
10574 have circuits on them. Oops. With this new version, clients will
10575 discard their previous entry guard choices and avoid choosing
10576 entry guards running these flawed versions.
10577 - Fix memory leak when uncompressing concatenated zlib streams. This
10578 was causing substantial leaks over time on Tor servers.
10579 - The v1 directory was including servers as much as 48 hours old,
10580 because that's how the new routerlist->routers works. Now only
10581 include them if they're 20 hours old or less.
10584 - Resume building on irix64, netbsd 2.0, etc.
10585 - On non-gcc compilers (e.g. solaris), use "-g -O" instead of
10587 - Stop writing the "router.desc" file, ever. Nothing uses it anymore,
10588 and it is confusing some users.
10589 - Mirrors stop caching the v1 directory so often.
10590 - Make the max number of old descriptors that a cache will hold
10591 rise with the number of directory authorities, so we can scale.
10592 - Change our win32 uname() hack to be more forgiving about what
10593 win32 versions it thinks it's found.
10596 - Add lefkada.eecs.harvard.edu as a fourth authoritative directory
10598 - When the controller's *setconf commands fail, collect an error
10599 message in a string and hand it back to the controller.
10600 - Make the v2 dir's "Fast" flag based on relative capacity, just
10601 like "Stable" is based on median uptime. Name everything in the
10602 top 7/8 Fast, and only the top 1/2 gets to be a Guard.
10603 - Log server fingerprint on startup, so new server operators don't
10604 have to go hunting around their filesystem for it.
10605 - Return a robots.txt on our dirport to discourage google indexing.
10606 - Let the controller ask for GETINFO dir/status/foo so it can ask
10607 directly rather than connecting to the dir port. Only works when
10608 dirport is set for now.
10610 o New config options rather than constants in the code:
10611 - SocksTimeout: How long do we let a socks connection wait
10612 unattached before we fail it?
10613 - CircuitBuildTimeout: Cull non-open circuits that were born
10614 at least this many seconds ago.
10615 - CircuitIdleTimeout: Cull open clean circuits that were born
10616 at least this many seconds ago.
10619 Changes in version 0.1.1.16-rc - 2006-03-18
10620 o Bugfixes on 0.1.1.15-rc:
10621 - Fix assert when the controller asks to attachstream a connect-wait
10622 or resolve-wait stream.
10623 - Now do address rewriting when the controller asks us to attach
10624 to a particular circuit too. This will let Blossom specify
10625 "moria2.exit" without having to learn what moria2's IP address is.
10626 - Make the "tor --verify-config" command-line work again, so people
10627 can automatically check if their torrc will parse.
10628 - Authoritative dirservers no longer require an open connection from
10629 a server to consider him "reachable". We need this change because
10630 when we add new auth dirservers, old servers won't know not to
10632 - Let Tor build on Sun CC again.
10633 - Fix an off-by-one buffer size in dirserv.c that magically never
10634 hit our three authorities but broke sjmurdoch's own tor network.
10635 - If we as a directory mirror don't know of any v1 directory
10636 authorities, then don't try to cache any v1 directories.
10637 - Stop warning about unknown servers in our family when they are
10638 given as hex digests.
10639 - Stop complaining as quickly to the server operator that he
10640 hasn't registered his nickname/key binding.
10641 - Various cleanups so we can add new V2 Auth Dirservers.
10642 - Change "AllowUnverifiedNodes" to "AllowInvalidNodes", to
10643 reflect the updated flags in our v2 dir protocol.
10644 - Resume allowing non-printable characters for exit streams (both
10645 for connecting and for resolving). Now we tolerate applications
10646 that don't follow the RFCs. But continue to block malformed names
10649 o Bugfixes on 0.1.0.x:
10650 - Fix assert bug in close_logs(): when we close and delete logs,
10651 remove them all from the global "logfiles" list.
10652 - Fix minor integer overflow in calculating when we expect to use up
10653 our bandwidth allocation before hibernating.
10654 - Fix a couple of bugs in OpenSSL detection. Also, deal better when
10655 there are multiple SSLs installed with different versions.
10656 - When we try to be a server and Address is not explicitly set and
10657 our hostname resolves to a private IP address, try to use an
10658 interface address if it has a public address. Now Windows machines
10659 that think of themselves as localhost can work by default.
10662 - Let the controller ask for GETINFO dir/server/foo so it can ask
10663 directly rather than connecting to the dir port.
10664 - Let the controller tell us about certain router descriptors
10665 that it doesn't want Tor to use in circuits. Implement
10666 SETROUTERPURPOSE and modify +POSTDESCRIPTOR to do this.
10667 - New config option SafeSocks to reject all application connections
10668 using unsafe socks protocols. Defaults to off.
10671 Changes in version 0.1.1.15-rc - 2006-03-11
10672 o Bugfixes and cleanups:
10673 - When we're printing strings from the network, don't try to print
10674 non-printable characters. This protects us against shell escape
10675 sequence exploits, and also against attacks to fool humans into
10676 misreading their logs.
10677 - Fix a bug where Tor would fail to establish any connections if you
10678 left it off for 24 hours and then started it: we were happy with
10679 the obsolete network statuses, but they all referred to router
10680 descriptors that were too old to fetch, so we ended up with no
10681 valid router descriptors.
10682 - Fix a seg fault in the controller's "getinfo orconn-status"
10683 command while listing status on incoming handshaking connections.
10684 Introduce a status name "NEW" for these connections.
10685 - If we get a linelist or linelist_s config option from the torrc
10686 (e.g. ExitPolicy) and it has no value, warn and skip rather than
10687 silently resetting it to its default.
10688 - Don't abandon entry guards until they've been down or gone for
10690 - Cleaner and quieter log messages.
10693 - New controller signal NEWNYM that makes new application requests
10694 use clean circuits.
10695 - Add a new circuit purpose 'controller' to let the controller ask
10696 for a circuit that Tor won't try to use. Extend the EXTENDCIRCUIT
10697 controller command to let you specify the purpose if you're
10698 starting a new circuit. Add a new SETCIRCUITPURPOSE controller
10699 command to let you change a circuit's purpose after it's been
10701 - Accept "private:*" in routerdesc exit policies; not generated yet
10702 because older Tors do not understand it.
10703 - Add BSD-style contributed startup script "rc.subr" from Peter
10707 Changes in version 0.1.1.14-alpha - 2006-02-20
10708 o Bugfixes on 0.1.1.x:
10709 - Don't die if we ask for a stdout or stderr log (even implicitly)
10710 and we're set to RunAsDaemon -- just warn.
10711 - We still had a few bugs in the OR connection rotation code that
10712 caused directory servers to slowly aggregate connections to other
10713 fast Tor servers. This time for sure!
10714 - Make log entries on Win32 include the name of the function again.
10715 - We were treating a pair of exit policies if they were equal even
10716 if one said accept and the other said reject -- causing us to
10717 not always publish a new descriptor since we thought nothing
10719 - Retry pending server downloads as well as pending networkstatus
10720 downloads when we unexpectedly get a socks request.
10721 - We were ignoring the IS_FAST flag in the directory status,
10722 meaning we were willing to pick trivial-bandwidth nodes for "fast"
10724 - If the controller's SAVECONF command fails (e.g. due to file
10725 permissions), let the controller know that it failed.
10728 - If we're trying to be a Tor server and running Windows 95/98/ME
10729 as a server, explain that we'll likely crash.
10730 - When we're a server, a client asks for an old-style directory,
10731 and our write bucket is empty, don't give it to him. This way
10732 small servers can continue to serve the directory *sometimes*,
10733 without getting overloaded.
10734 - Compress exit policies even more -- look for duplicate lines
10736 - Clients now honor the "guard" flag in the router status when
10737 picking entry guards, rather than looking at is_fast or is_stable.
10738 - Retain unrecognized lines in $DATADIR/state file, so that we can
10739 be forward-compatible.
10740 - Generate 18.0.0.0/8 address policy format in descs when we can;
10741 warn when the mask is not reducible to a bit-prefix.
10742 - Let the user set ControlListenAddress in the torrc. This can be
10743 dangerous, but there are some cases (like a secured LAN) where it
10745 - Split ReachableAddresses into ReachableDirAddresses and
10746 ReachableORAddresses, so we can restrict Dir conns to port 80
10747 and OR conns to port 443.
10748 - Now we can target arch and OS in rpm builds (contributed by
10749 Phobos). Also make the resulting dist-rpm filename match the
10751 - New config options to help controllers: FetchServerDescriptors
10752 and FetchHidServDescriptors for whether to fetch server
10753 info and hidserv info or let the controller do it, and
10754 PublishServerDescriptor and PublishHidServDescriptors.
10755 - Also let the controller set the __AllDirActionsPrivate config
10756 option if you want all directory fetches/publishes to happen via
10757 Tor (it assumes your controller bootstraps your circuits).
10760 Changes in version 0.1.0.17 - 2006-02-17
10761 o Crash bugfixes on 0.1.0.x:
10762 - When servers with a non-zero DirPort came out of hibernation,
10763 sometimes they would trigger an assert.
10765 o Other important bugfixes:
10766 - On platforms that don't have getrlimit (like Windows), we were
10767 artificially constraining ourselves to a max of 1024
10768 connections. Now just assume that we can handle as many as 15000
10769 connections. Hopefully this won't cause other problems.
10771 o Backported features:
10772 - When we're a server, a client asks for an old-style directory,
10773 and our write bucket is empty, don't give it to him. This way
10774 small servers can continue to serve the directory *sometimes*,
10775 without getting overloaded.
10776 - Whenever you get a 503 in response to a directory fetch, try
10777 once more. This will become important once servers start sending
10778 503's whenever they feel busy.
10779 - Fetch a new directory every 120 minutes, not every 40 minutes.
10780 Now that we have hundreds of thousands of users running the old
10781 directory algorithm, it's starting to hurt a lot.
10782 - Bump up the period for forcing a hidden service descriptor upload
10783 from 20 minutes to 1 hour.
10786 Changes in version 0.1.1.13-alpha - 2006-02-09
10787 o Crashes in 0.1.1.x:
10788 - When you tried to setconf ORPort via the controller, Tor would
10789 crash. So people using TorCP to become a server were sad.
10790 - Solve (I hope) the stack-smashing bug that we were seeing on fast
10791 servers. The problem appears to be something do with OpenSSL's
10792 random number generation, or how we call it, or something. Let me
10793 know if the crashes continue.
10794 - Turn crypto hardware acceleration off by default, until we find
10795 somebody smart who can test it for us. (It appears to produce
10796 seg faults in at least some cases.)
10797 - Fix a rare assert error when we've tried all intro points for
10798 a hidden service and we try fetching the service descriptor again:
10799 "Assertion conn->state != AP_CONN_STATE_RENDDESC_WAIT failed"
10802 - Fix a major load balance bug: we were round-robining in 16 KB
10803 chunks, and servers with bandwidthrate of 20 KB, while downloading
10804 a 600 KB directory, would starve their other connections. Now we
10805 try to be a bit more fair.
10806 - Dir authorities and mirrors were never expiring the newest
10807 descriptor for each server, causing memory and directory bloat.
10808 - Fix memory-bloating and connection-bloating bug on servers: We
10809 were never closing any connection that had ever had a circuit on
10810 it, because we were checking conn->n_circuits == 0, yet we had a
10811 bug that let it go negative.
10812 - Make Tor work using squid as your http proxy again -- squid
10813 returns an error if you ask for a URL that's too long, and it uses
10814 a really generic error message. Plus, many people are behind a
10815 transparent squid so they don't even realize it.
10816 - On platforms that don't have getrlimit (like Windows), we were
10817 artificially constraining ourselves to a max of 1024
10818 connections. Now just assume that we can handle as many as 15000
10819 connections. Hopefully this won't cause other problems.
10820 - Add a new config option ExitPolicyRejectPrivate which defaults to
10821 1. This means all exit policies will begin with rejecting private
10822 addresses, unless the server operator explicitly turns it off.
10825 - Clients no longer download descriptors for non-running
10827 - Before we add new directory authorities, we should make it
10828 clear that only v1 authorities should receive/publish hidden
10829 service descriptors.
10832 - As soon as we've fetched some more directory info, immediately
10833 try to download more server descriptors. This way we don't have
10834 a 10 second pause during initial bootstrapping.
10835 - Remove even more loud log messages that the server operator can't
10837 - When we're running an obsolete or un-recommended version, make
10838 the log message more clear about what the problem is and what
10839 versions *are* still recommended.
10840 - Provide a more useful warn message when our onion queue gets full:
10841 the CPU is too slow or the exit policy is too liberal.
10842 - Don't warn when we receive a 503 from a dirserver/cache -- this
10843 will pave the way for them being able to refuse if they're busy.
10844 - When we fail to bind a listener, try to provide a more useful
10845 log message: e.g., "Is Tor already running?"
10846 - Adjust tor-spec to parameterize cell and key lengths. Now Ian
10847 Goldberg can prove things about our handshake protocol more
10849 - MaxConn has been obsolete for a while now. Document the ConnLimit
10850 config option, which is a *minimum* number of file descriptors
10851 that must be available else Tor refuses to start.
10852 - Apply Matt Ghali's --with-syslog-facility patch to ./configure
10853 if you log to syslog and want something other than LOG_DAEMON.
10854 - Make dirservers generate a separate "guard" flag to mean,
10855 "would make a good entry guard". Make clients parse it and vote
10856 on it. Not used by clients yet.
10857 - Implement --with-libevent-dir option to ./configure. Also, improve
10858 search techniques to find libevent, and use those for openssl too.
10859 - Bump the default bandwidthrate to 3 MB, and burst to 6 MB
10860 - Only start testing reachability once we've established a
10861 circuit. This will make startup on dirservers less noisy.
10862 - Don't try to upload hidden service descriptors until we have
10863 established a circuit.
10864 - Fix the controller's "attachstream 0" command to treat conn like
10865 it just connected, doing address remapping, handling .exit and
10866 .onion idioms, and so on. Now we're more uniform in making sure
10867 that the controller hears about new and closing connections.
10870 Changes in version 0.1.1.12-alpha - 2006-01-11
10871 o Bugfixes on 0.1.1.x:
10872 - The fix to close duplicate server connections was closing all
10873 Tor client connections if they didn't establish a circuit
10874 quickly enough. Oops.
10875 - Fix minor memory issue (double-free) that happened on exit.
10877 o Bugfixes on 0.1.0.x:
10878 - Tor didn't warn when it failed to open a log file.
10881 Changes in version 0.1.1.11-alpha - 2006-01-10
10882 o Crashes in 0.1.1.x:
10883 - Include all the assert/crash fixes from 0.1.0.16.
10884 - If you start Tor and then quit very quickly, there were some
10885 races that tried to free things that weren't allocated yet.
10886 - Fix a rare memory stomp if you're running hidden services.
10887 - Fix segfault when specifying DirServer in config without nickname.
10888 - Fix a seg fault when you finish connecting to a server but at
10889 that moment you dump his server descriptor.
10890 - Extendcircuit and Attachstream controller commands would
10891 assert/crash if you don't give them enough arguments.
10892 - Fix an assert error when we're out of space in the connection_list
10893 and we try to post a hidden service descriptor (reported by weasel).
10894 - If you specify a relative torrc path and you set RunAsDaemon in
10895 your torrc, then it chdir()'s to the new directory. If you HUP,
10896 it tries to load the new torrc location, fails, and exits.
10897 The fix: no longer allow a relative path to torrc using -f.
10900 - Implement "entry guards": automatically choose a handful of entry
10901 nodes and stick with them for all circuits. Only pick new guards
10902 when the ones you have are unsuitable, and if the old guards
10903 become suitable again, switch back. This will increase security
10904 dramatically against certain end-point attacks. The EntryNodes
10905 config option now provides some hints about which entry guards you
10906 want to use most; and StrictEntryNodes means to only use those.
10907 - New directory logic: download by descriptor digest, not by
10908 fingerprint. Caches try to download all listed digests from
10909 authorities; clients try to download "best" digests from caches.
10910 This avoids partitioning and isolating attacks better.
10911 - Make the "stable" router flag in network-status be the median of
10912 the uptimes of running valid servers, and make clients pay
10913 attention to the network-status flags. Thus the cutoff adapts
10914 to the stability of the network as a whole, making IRC, IM, etc
10915 connections more reliable.
10918 - Tor servers with dynamic IP addresses were needing to wait 18
10919 hours before they could start doing reachability testing using
10920 the new IP address and ports. This is because they were using
10921 the internal descriptor to learn what to test, yet they were only
10922 rebuilding the descriptor once they decided they were reachable.
10923 - Tor 0.1.1.9 and 0.1.1.10 had a serious bug that caused clients
10924 to download certain server descriptors, throw them away, and then
10925 fetch them again after 30 minutes. Now mirrors throw away these
10926 server descriptors so clients can't get them.
10927 - We were leaving duplicate connections to other ORs open for a week,
10928 rather than closing them once we detect a duplicate. This only
10929 really affected authdirservers, but it affected them a lot.
10930 - Spread the authdirservers' reachability testing over the entire
10931 testing interval, so we don't try to do 500 TLS's at once every
10935 - If the network is down, and we try to connect to a conn because
10936 we have a circuit in mind, and we timeout (30 seconds) because the
10937 network never answers, we were expiring the circuit, but we weren't
10938 obsoleting the connection or telling the entry_guards functions.
10939 - Some Tor servers process billions of cells per day. These statistics
10940 need to be uint64_t's.
10941 - Check for integer overflows in more places, when adding elements
10942 to smartlists. This could possibly prevent a buffer overflow
10943 on malicious huge inputs. I don't see any, but I haven't looked
10945 - ReachableAddresses kept growing new "reject *:*" lines on every
10947 - When you "setconf log" via the controller, it should remove all
10948 logs. We were automatically adding back in a "log notice stdout".
10949 - Newly bootstrapped Tor networks couldn't establish hidden service
10950 circuits until they had nodes with high uptime. Be more tolerant.
10951 - We were marking servers down when they could not answer every piece
10952 of the directory request we sent them. This was far too harsh.
10953 - Fix the torify (tsocks) config file to not use Tor for localhost
10955 - Directory authorities now go to the proper authority when asking for
10956 a networkstatus, even when they want a compressed one.
10957 - Fix a harmless bug that was causing Tor servers to log
10958 "Got an end because of misc error, but we're not an AP. Closing."
10959 - Authorities were treating their own descriptor changes as cosmetic,
10960 meaning the descriptor available in the network-status and the
10961 descriptor that clients downloaded were different.
10962 - The OS X installer was adding a symlink for tor_resolve but
10963 the binary was called tor-resolve (reported by Thomas Hardly).
10964 - Workaround a problem with some http proxies where they refuse GET
10965 requests that specify "Content-Length: 0" (reported by Adrian).
10966 - Fix wrong log message when you add a "HiddenServiceNodes" config
10967 line without any HiddenServiceDir line (reported by Chris Thomas).
10970 - Write the TorVersion into the state file so we have a prayer of
10971 keeping forward and backward compatibility.
10972 - Revive the FascistFirewall config option rather than eliminating it:
10973 now it's a synonym for ReachableAddresses *:80,*:443.
10974 - Clients choose directory servers from the network status lists,
10975 not from their internal list of router descriptors. Now they can
10976 go to caches directly rather than needing to go to authorities
10978 - Directory authorities ignore router descriptors that have only
10979 cosmetic differences: do this for 0.1.0.x servers now too.
10980 - Add a new flag to network-status indicating whether the server
10981 can answer v2 directory requests too.
10982 - Authdirs now stop whining so loudly about bad descriptors that
10983 they fetch from other dirservers. So when there's a log complaint,
10984 it's for sure from a freshly uploaded descriptor.
10985 - Reduce memory requirements in our structs by changing the order
10987 - There used to be two ways to specify your listening ports in a
10988 server descriptor: on the "router" line and with a separate "ports"
10989 line. Remove support for the "ports" line.
10990 - New config option "AuthDirRejectUnlisted" for auth dirservers as
10991 a panic button: if we get flooded with unusable servers we can
10992 revert to only listing servers in the approved-routers file.
10993 - Auth dir servers can now mark a fingerprint as "!reject" or
10994 "!invalid" in the approved-routers file (as its nickname), to
10995 refuse descriptors outright or include them but marked as invalid.
10996 - Servers store bandwidth history across restarts/crashes.
10997 - Add reasons to DESTROY and RELAY_TRUNCATED cells, so clients can
10998 get a better idea of why their circuits failed. Not used yet.
10999 - Directory mirrors now cache up to 16 unrecognized network-status
11000 docs. Now we can add new authdirservers and they'll be cached too.
11001 - When picking a random directory, prefer non-authorities if any
11003 - New controller option "getinfo desc/all-recent" to fetch the
11004 latest server descriptor for every router that Tor knows about.
11007 Changes in version 0.1.0.16 - 2006-01-02
11008 o Crash bugfixes on 0.1.0.x:
11009 - On Windows, build with a libevent patch from "I-M Weasel" to avoid
11010 corrupting the heap, losing FDs, or crashing when we need to resize
11011 the fd_sets. (This affects the Win32 binaries, not Tor's sources.)
11012 - It turns out sparc64 platforms crash on unaligned memory access
11013 too -- so detect and avoid this.
11014 - Handle truncated compressed data correctly (by detecting it and
11016 - Fix possible-but-unlikely free(NULL) in control.c.
11017 - When we were closing connections, there was a rare case that
11018 stomped on memory, triggering seg faults and asserts.
11019 - Avoid potential infinite recursion when building a descriptor. (We
11020 don't know that it ever happened, but better to fix it anyway.)
11021 - We were neglecting to unlink marked circuits from soon-to-close OR
11022 connections, which caused some rare scribbling on freed memory.
11023 - Fix a memory stomping race bug when closing the joining point of two
11024 rendezvous circuits.
11025 - Fix an assert in time parsing found by Steven Murdoch.
11027 o Other bugfixes on 0.1.0.x:
11028 - When we're doing reachability testing, provide more useful log
11029 messages so the operator knows what to expect.
11030 - Do not check whether DirPort is reachable when we are suppressing
11031 advertising it because of hibernation.
11032 - When building with -static or on Solaris, we sometimes needed -ldl.
11033 - When we're deciding whether a stream has enough circuits around
11034 that can handle it, count the freshly dirty ones and not the ones
11035 that are so dirty they won't be able to handle it.
11036 - When we're expiring old circuits, we had a logic error that caused
11037 us to close new rendezvous circuits rather than old ones.
11038 - Give a more helpful log message when you try to change ORPort via
11039 the controller: you should upgrade Tor if you want that to work.
11040 - We were failing to parse Tor versions that start with "Tor ".
11041 - Tolerate faulty streams better: when a stream fails for reason
11042 exitpolicy, stop assuming that the router is lying about his exit
11043 policy. When a stream fails for reason misc, allow it to retry just
11044 as if it was resolvefailed. When a stream has failed three times,
11045 reset its failure count so we can try again and get all three tries.
11048 Changes in version 0.1.1.10-alpha - 2005-12-11
11049 o Correctness bugfixes on 0.1.0.x:
11050 - On Windows, build with a libevent patch from "I-M Weasel" to avoid
11051 corrupting the heap, losing FDs, or crashing when we need to resize
11052 the fd_sets. (This affects the Win32 binaries, not Tor's sources.)
11053 - Stop doing the complex voodoo overkill checking for insecure
11054 Diffie-Hellman keys. Just check if it's in [2,p-2] and be happy.
11055 - When we were closing connections, there was a rare case that
11056 stomped on memory, triggering seg faults and asserts.
11057 - We were neglecting to unlink marked circuits from soon-to-close OR
11058 connections, which caused some rare scribbling on freed memory.
11059 - When we're deciding whether a stream has enough circuits around
11060 that can handle it, count the freshly dirty ones and not the ones
11061 that are so dirty they won't be able to handle it.
11062 - Recover better from TCP connections to Tor servers that are
11063 broken but don't tell you (it happens!); and rotate TLS
11064 connections once a week.
11065 - When we're expiring old circuits, we had a logic error that caused
11066 us to close new rendezvous circuits rather than old ones.
11067 - Fix a scary-looking but apparently harmless bug where circuits
11068 would sometimes start out in state CIRCUIT_STATE_OR_WAIT at
11069 servers, and never switch to state CIRCUIT_STATE_OPEN.
11070 - When building with -static or on Solaris, we sometimes needed to
11072 - Give a useful message when people run Tor as the wrong user,
11073 rather than telling them to start chowning random directories.
11074 - We were failing to inform the controller about new .onion streams.
11076 o Security bugfixes on 0.1.0.x:
11077 - Refuse server descriptors if the fingerprint line doesn't match
11078 the included identity key. Tor doesn't care, but other apps (and
11079 humans) might actually be trusting the fingerprint line.
11080 - We used to kill the circuit when we receive a relay command we
11081 don't recognize. Now we just drop it.
11082 - Start obeying our firewall options more rigorously:
11083 . If we can't get to a dirserver directly, try going via Tor.
11084 . Don't ever try to connect (as a client) to a place our
11085 firewall options forbid.
11086 . If we specify a proxy and also firewall options, obey the
11087 firewall options even when we're using the proxy: some proxies
11088 can only proxy to certain destinations.
11089 - Fix a bug found by Lasse Overlier: when we were making internal
11090 circuits (intended to be cannibalized later for rendezvous and
11091 introduction circuits), we were picking them so that they had
11092 useful exit nodes. There was no need for this, and it actually
11093 aids some statistical attacks.
11094 - Start treating internal circuits and exit circuits separately.
11095 It's important to keep them separate because internal circuits
11096 have their last hops picked like middle hops, rather than like
11097 exit hops. So exiting on them will break the user's expectations.
11099 o Bugfixes on 0.1.1.x:
11100 - Take out the mis-feature where we tried to detect IP address
11101 flapping for people with DynDNS, and chose not to upload a new
11102 server descriptor sometimes.
11103 - Try to be compatible with OpenSSL 0.9.6 again.
11104 - Log fix: when the controller is logging about .onion addresses,
11105 sometimes it didn't include the ".onion" part of the address.
11106 - Don't try to modify options->DirServers internally -- if the
11107 user didn't specify any, just add the default ones directly to
11108 the trusted dirserver list. This fixes a bug where people running
11109 controllers would use SETCONF on some totally unrelated config
11110 option, and Tor would start yelling at them about changing their
11112 - Let the controller's redirectstream command specify a port, in
11113 case the controller wants to change that too.
11114 - When we requested a pile of server descriptors, we sometimes
11115 accidentally launched a duplicate request for the first one.
11116 - Bugfix for trackhostexits: write down the fingerprint of the
11117 chosen exit, not its nickname, because the chosen exit might not
11119 - When parsing foo.exit, if foo is unknown, and we are leaving
11120 circuits unattached, set the chosen_exit field and leave the
11121 address empty. This matters because controllers got confused
11123 - Directory authorities no longer try to download server
11124 descriptors that they know they will reject.
11126 o Features and updates:
11127 - Replace balanced trees with hash tables: this should make stuff
11128 significantly faster.
11129 - Resume using the AES counter-mode implementation that we ship,
11130 rather than OpenSSL's. Ours is significantly faster.
11131 - Many other CPU and memory improvements.
11132 - Add a new config option FastFirstHopPK (on by default) so clients
11133 do a trivial crypto handshake for their first hop, since TLS has
11134 already taken care of confidentiality and authentication.
11135 - Add a new config option TestSocks so people can see if their
11136 applications are using socks4, socks4a, socks5-with-ip, or
11137 socks5-with-hostname. This way they don't have to keep mucking
11138 with tcpdump and wondering if something got cached somewhere.
11139 - Warn when listening on a public address for socks. I suspect a
11140 lot of people are setting themselves up as open socks proxies,
11141 and they have no idea that jerks on the Internet are using them,
11142 since they simply proxy the traffic into the Tor network.
11143 - Add "private:*" as an alias in configuration for policies. Now
11144 you can simplify your exit policy rather than needing to list
11145 every single internal or nonroutable network space.
11146 - Add a new controller event type that allows controllers to get
11147 all server descriptors that were uploaded to a router in its role
11148 as authoritative dirserver.
11149 - Start shipping socks-extensions.txt, tor-doc-unix.html,
11150 tor-doc-server.html, and stylesheet.css in the tarball.
11151 - Stop shipping tor-doc.html in the tarball.
11154 Changes in version 0.1.1.9-alpha - 2005-11-15
11155 o Usability improvements:
11156 - Start calling it FooListenAddress rather than FooBindAddress,
11157 since few of our users know what it means to bind an address
11159 - Reduce clutter in server logs. We're going to try to make
11160 them actually usable now. New config option ProtocolWarnings that
11161 lets you hear about how _other Tors_ are breaking the protocol. Off
11163 - Divide log messages into logging domains. Once we put some sort
11164 of interface on this, it will let people looking at more verbose
11165 log levels specify the topics they want to hear more about.
11166 - Make directory servers return better http 404 error messages
11167 instead of a generic "Servers unavailable".
11168 - Check for even more Windows version flags when writing the platform
11169 string in server descriptors, and note any we don't recognize.
11170 - Clean up more of the OpenSSL memory when exiting, so we can detect
11171 memory leaks better.
11172 - Make directory authorities be non-versioning, non-naming by
11173 default. Now we can add new directory servers without requiring
11174 their operators to pay close attention.
11175 - When logging via syslog, include the pid whenever we provide
11176 a log entry. Suggested by Todd Fries.
11178 o Performance improvements:
11179 - Directory servers now silently throw away new descriptors that
11180 haven't changed much if the timestamps are similar. We do this to
11181 tolerate older Tor servers that upload a new descriptor every 15
11182 minutes. (It seemed like a good idea at the time.)
11183 - Inline bottleneck smartlist functions; use fast versions by default.
11184 - Add a "Map from digest to void*" abstraction digestmap_t so we
11185 can do less hex encoding/decoding. Use it in router_get_by_digest()
11186 to resolve a performance bottleneck.
11187 - Allow tor_gzip_uncompress to extract as much as possible from
11188 truncated compressed data. Try to extract as many
11189 descriptors as possible from truncated http responses (when
11190 DIR_PURPOSE_FETCH_ROUTERDESC).
11191 - Make circ->onionskin a pointer, not a static array. moria2 was using
11192 125000 circuit_t's after it had been up for a few weeks, which
11193 translates to 20+ megs of wasted space.
11194 - The private half of our EDH handshake keys are now chosen out
11195 of 320 bits, not 1024 bits. (Suggested by Ian Goldberg.)
11197 o Security improvements:
11198 - Start making directory caches retain old routerinfos, so soon
11199 clients can start asking by digest of descriptor rather than by
11200 fingerprint of server.
11201 - Add half our entropy from RAND_poll in OpenSSL. This knows how
11202 to use egd (if present), openbsd weirdness (if present), vms/os2
11203 weirdness (if we ever port there), and more in the future.
11205 o Bugfixes on 0.1.0.x:
11206 - Do round-robin writes of at most 16 kB per write. This might be
11207 more fair on loaded Tor servers, and it might resolve our Windows
11208 crash bug. It might also slow things down.
11209 - Our TLS handshakes were generating a single public/private
11210 keypair for the TLS context, rather than making a new one for
11211 each new connections. Oops. (But we were still rotating them
11212 periodically, so it's not so bad.)
11213 - When we were cannibalizing a circuit with a particular exit
11214 node in mind, we weren't checking to see if that exit node was
11215 already present earlier in the circuit. Oops.
11216 - When a Tor server's IP changes (e.g. from a dyndns address),
11217 upload a new descriptor so clients will learn too.
11218 - Really busy servers were keeping enough circuits open on stable
11219 connections that they were wrapping around the circuit_id
11220 space. (It's only two bytes.) This exposed a bug where we would
11221 feel free to reuse a circuit_id even if it still exists but has
11222 been marked for close. Try to fix this bug. Some bug remains.
11223 - If we would close a stream early (e.g. it asks for a .exit that
11224 we know would refuse it) but the LeaveStreamsUnattached config
11225 option is set by the controller, then don't close it.
11227 o Bugfixes on 0.1.1.8-alpha:
11228 - Fix a big pile of memory leaks, some of them serious.
11229 - Do not try to download a routerdesc if we would immediately reject
11231 - Resume inserting a newline between all router descriptors when
11232 generating (old style) signed directories, since our spec says
11234 - When providing content-type application/octet-stream for
11235 server descriptors using .z, we were leaving out the
11236 content-encoding header. Oops. (Everything tolerated this just
11237 fine, but that doesn't mean we need to be part of the problem.)
11238 - Fix a potential seg fault in getconf and getinfo using version 1
11239 of the controller protocol.
11240 - Avoid crash: do not check whether DirPort is reachable when we
11241 are suppressing it because of hibernation.
11242 - Make --hash-password not crash on exit.
11245 Changes in version 0.1.1.8-alpha - 2005-10-07
11246 o New features (major):
11247 - Clients don't download or use the directory anymore. Now they
11248 download and use network-statuses from the trusted dirservers,
11249 and fetch individual server descriptors as needed from mirrors.
11250 See dir-spec.txt for all the gory details.
11251 - Be more conservative about whether to advertise our DirPort.
11252 The main change is to not advertise if we're running at capacity
11253 and either a) we could hibernate or b) our capacity is low and
11254 we're using a default DirPort.
11255 - Use OpenSSL's AES when OpenSSL has version 0.9.7 or later.
11257 o New features (minor):
11258 - Try to be smart about when to retry network-status and
11259 server-descriptor fetches. Still needs some tuning.
11260 - Stop parsing, storing, or using running-routers output (but
11261 mirrors still cache and serve it).
11262 - Consider a threshold of versioning dirservers (dirservers who have
11263 an opinion about which Tor versions are still recommended) before
11264 deciding whether to warn the user that he's obsolete.
11265 - Dirservers can now reject/invalidate by key and IP, with the
11266 config options "AuthDirInvalid" and "AuthDirReject". This is
11267 useful since currently we automatically list servers as running
11268 and usable even if we know they're jerks.
11269 - Provide dire warnings to any users who set DirServer; move it out
11270 of torrc.sample and into torrc.complete.
11271 - Add MyFamily to torrc.sample in the server section.
11272 - Add nicknames to the DirServer line, so we can refer to them
11273 without requiring all our users to memorize their IP addresses.
11274 - When we get an EOF or a timeout on a directory connection, note
11275 how many bytes of serverdesc we are dropping. This will help
11276 us determine whether it is smart to parse incomplete serverdesc
11278 - Add a new function to "change pseudonyms" -- that is, to stop
11279 using any currently-dirty circuits for new streams, so we don't
11280 link new actions to old actions. Currently it's only called on
11281 HUP (or SIGNAL RELOAD).
11282 - On sighup, if UseHelperNodes changed to 1, use new circuits.
11283 - Start using RAND_bytes rather than RAND_pseudo_bytes from
11284 OpenSSL. Also, reseed our entropy every hour, not just at
11285 startup. And entropy in 512-bit chunks, not 160-bit chunks.
11287 o Fixes on 0.1.1.7-alpha:
11288 - Nobody ever implemented EVENT_ADDRMAP for control protocol
11289 version 0, so don't let version 0 controllers ask for it.
11290 - If you requested something with too many newlines via the
11291 v1 controller protocol, you could crash tor.
11292 - Fix a number of memory leaks, including some pretty serious ones.
11293 - Re-enable DirPort testing again, so Tor servers will be willing
11294 to advertise their DirPort if it's reachable.
11295 - On TLS handshake, only check the other router's nickname against
11296 its expected nickname if is_named is set.
11298 o Fixes forward-ported from 0.1.0.15:
11299 - Don't crash when we don't have any spare file descriptors and we
11300 try to spawn a dns or cpu worker.
11301 - Make the numbers in read-history and write-history into uint64s,
11302 so they don't overflow and publish negatives in the descriptor.
11304 o Fixes on 0.1.0.x:
11305 - For the OS X package's modified privoxy config file, comment
11306 out the "logfile" line so we don't log everything passed
11308 - We were whining about using socks4 or socks5-with-local-lookup
11309 even when it's an IP in the "virtual" range we designed exactly
11311 - We were leaking some memory every time the client changes IPs.
11312 - Never call free() on tor_malloc()d memory. This will help us
11313 use dmalloc to detect memory leaks.
11314 - Check for named servers when looking them up by nickname;
11315 warn when we'recalling a non-named server by its nickname;
11316 don't warn twice about the same name.
11317 - Try to list MyFamily elements by key, not by nickname, and warn
11318 if we've not heard of the server.
11319 - Make windows platform detection (uname equivalent) smarter.
11320 - It turns out sparc64 doesn't like unaligned access either.
11323 Changes in version 0.1.0.15 - 2005-09-23
11324 o Bugfixes on 0.1.0.x:
11325 - Reject ports 465 and 587 (spam targets) in default exit policy.
11326 - Don't crash when we don't have any spare file descriptors and we
11327 try to spawn a dns or cpu worker.
11328 - Get rid of IgnoreVersion undocumented config option, and make us
11329 only warn, never exit, when we're running an obsolete version.
11330 - Don't try to print a null string when your server finds itself to
11331 be unreachable and the Address config option is empty.
11332 - Make the numbers in read-history and write-history into uint64s,
11333 so they don't overflow and publish negatives in the descriptor.
11334 - Fix a minor memory leak in smartlist_string_remove().
11335 - We were only allowing ourselves to upload a server descriptor at
11336 most every 20 minutes, even if it changed earlier than that.
11337 - Clean up log entries that pointed to old URLs.
11340 Changes in version 0.1.1.7-alpha - 2005-09-14
11341 o Fixes on 0.1.1.6-alpha:
11342 - Exit servers were crashing when people asked them to make a
11343 connection to an address not in their exit policy.
11344 - Looking up a non-existent stream for a v1 control connection would
11346 - Fix a seg fault if we ask a dirserver for a descriptor by
11347 fingerprint but he doesn't know about him.
11348 - SETCONF was appending items to linelists, not clearing them.
11349 - SETCONF SocksBindAddress killed Tor if it fails to bind. Now back
11350 out and refuse the setconf if it would fail.
11351 - Downgrade the dirserver log messages when whining about
11355 - Add Peter Palfrader's check-tor script to tor/contrib/
11356 It lets you easily check whether a given server (referenced by
11357 nickname) is reachable by you.
11358 - Numerous changes to move towards client-side v2 directories. Not
11361 o Fixes on 0.1.0.x:
11362 - If the user gave tor an odd number of command-line arguments,
11363 we were silently ignoring the last one. Now we complain and fail.
11364 [This wins the oldest-bug prize -- this bug has been present since
11365 November 2002, as released in Tor 0.0.0.]
11366 - Do not use unaligned memory access on alpha, mips, or mipsel.
11367 It *works*, but is very slow, so we treat them as if it doesn't.
11368 - Retry directory requests if we fail to get an answer we like
11369 from a given dirserver (we were retrying before, but only if
11370 we fail to connect).
11371 - When writing the RecommendedVersions line, sort them first.
11372 - When the client asked for a rendezvous port that the hidden
11373 service didn't want to provide, we were sending an IP address
11374 back along with the end cell. Fortunately, it was zero. But stop
11376 - Correct "your server is reachable" log entries to indicate that
11377 it was self-testing that told us so.
11380 Changes in version 0.1.1.6-alpha - 2005-09-09
11381 o Fixes on 0.1.1.5-alpha:
11382 - We broke fascistfirewall in 0.1.1.5-alpha. Oops.
11383 - Fix segfault in unit tests in 0.1.1.5-alpha. Oops.
11384 - Fix bug with tor_memmem finding a match at the end of the string.
11385 - Make unit tests run without segfaulting.
11386 - Resolve some solaris x86 compile warnings.
11387 - Handle duplicate lines in approved-routers files without warning.
11388 - Fix bug where as soon as a server refused any requests due to his
11389 exit policy (e.g. when we ask for localhost and he tells us that's
11390 127.0.0.1 and he won't do it), we decided he wasn't obeying his
11391 exit policy using him for any exits.
11392 - Only do openssl hardware accelerator stuff if openssl version is
11395 o New controller features/fixes:
11396 - Add a "RESETCONF" command so you can set config options like
11397 AllowUnverifiedNodes and LongLivedPorts to "". Also, if you give
11398 a config option in the torrc with no value, then it clears it
11399 entirely (rather than setting it to its default).
11400 - Add a "GETINFO config-file" to tell us where torrc is.
11401 - Avoid sending blank lines when GETINFO replies should be empty.
11402 - Add a QUIT command for the controller (for using it manually).
11403 - Fix a bug in SAVECONF that was adding default dirservers and
11404 other redundant entries to the torrc file.
11406 o Start on the new directory design:
11407 - Generate, publish, cache, serve new network-status format.
11408 - Publish individual descriptors (by fingerprint, by "all", and by
11410 - Publish client and server recommended versions separately.
11411 - Allow tor_gzip_uncompress() to handle multiple concatenated
11412 compressed strings. Serve compressed groups of router
11413 descriptors. The compression logic here could be more
11415 - Distinguish v1 authorities (all currently trusted directories)
11416 from v2 authorities (all trusted directories).
11417 - Change DirServers config line to note which dirs are v1 authorities.
11418 - Add configuration option "V1AuthoritativeDirectory 1" which
11419 moria1, moria2, and tor26 should set.
11420 - Remove option when getting directory cache to see whether they
11421 support running-routers; they all do now. Replace it with one
11422 to see whether caches support v2 stuff.
11425 - Dirservers now do their own external reachability testing of each
11426 Tor server, and only list them as running if they've been found to
11427 be reachable. We also send back warnings to the server's logs if
11428 it uploads a descriptor that we already believe is unreachable.
11429 - Implement exit enclaves: if we know an IP address for the
11430 destination, and there's a running Tor server at that address
11431 which allows exit to the destination, then extend the circuit to
11432 that exit first. This provides end-to-end encryption and end-to-end
11433 authentication. Also, if the user wants a .exit address or enclave,
11434 use 4 hops rather than 3, and cannibalize a general circ for it
11436 - Permit transitioning from ORPort=0 to ORPort!=0, and back, from the
11437 controller. Also, rotate dns and cpu workers if the controller
11438 changes options that will affect them; and initialize the dns
11439 worker cache tree whether or not we start out as a server.
11440 - Only upload a new server descriptor when options change, 18
11441 hours have passed, uptime is reset, or bandwidth changes a lot.
11442 - Check [X-]Forwarded-For headers in HTTP requests when generating
11443 log messages. This lets people run dirservers (and caches) behind
11444 Apache but still know which IP addresses are causing warnings.
11446 o Config option changes:
11447 - Replace (Fascist)Firewall* config options with a new
11448 ReachableAddresses option that understands address policies.
11449 For example, "ReachableAddresses *:80,*:443"
11450 - Get rid of IgnoreVersion undocumented config option, and make us
11451 only warn, never exit, when we're running an obsolete version.
11452 - Make MonthlyAccountingStart config option truly obsolete now.
11454 o Fixes on 0.1.0.x:
11455 - Reject ports 465 and 587 in the default exit policy, since
11456 people have started using them for spam too.
11457 - It turns out we couldn't bootstrap a network since we added
11458 reachability detection in 0.1.0.1-rc. Good thing the Tor network
11459 has never gone down. Add an AssumeReachable config option to let
11460 servers and dirservers bootstrap. When we're trying to build a
11461 high-uptime or high-bandwidth circuit but there aren't enough
11462 suitable servers, try being less picky rather than simply failing.
11463 - Our logic to decide if the OR we connected to was the right guy
11464 was brittle and maybe open to a mitm for unverified routers.
11465 - We weren't cannibalizing circuits correctly for
11466 CIRCUIT_PURPOSE_C_ESTABLISH_REND and
11467 CIRCUIT_PURPOSE_S_ESTABLISH_INTRO, so we were being forced to
11468 build those from scratch. This should make hidden services faster.
11469 - Predict required circuits better, with an eye toward making hidden
11470 services faster on the service end.
11471 - Retry streams if the exit node sends back a 'misc' failure. This
11472 should result in fewer random failures. Also, after failing
11473 from resolve failed or misc, reset the num failures, so we give
11474 it a fair shake next time we try.
11475 - Clean up the rendezvous warn log msgs, and downgrade some to info.
11476 - Reduce severity on logs about dns worker spawning and culling.
11477 - When we're shutting down and we do something like try to post a
11478 server descriptor or rendezvous descriptor, don't complain that
11479 we seem to be unreachable. Of course we are, we're shutting down.
11480 - Add TTLs to RESOLVED, CONNECTED, and END_REASON_EXITPOLICY cells.
11481 We don't use them yet, but maybe one day our DNS resolver will be
11482 able to discover them.
11483 - Make ContactInfo mandatory for authoritative directory servers.
11484 - Require server descriptors to list IPv4 addresses -- hostnames
11485 are no longer allowed. This also fixes some potential security
11486 problems with people providing hostnames as their address and then
11487 preferentially resolving them to partition users.
11488 - Change log line for unreachability to explicitly suggest /etc/hosts
11489 as the culprit. Also make it clearer what IP address and ports we're
11490 testing for reachability.
11491 - Put quotes around user-supplied strings when logging so users are
11492 more likely to realize if they add bad characters (like quotes)
11494 - Let auth dir servers start without specifying an Address config
11496 - Make unit tests (and other invocations that aren't the real Tor)
11497 run without launching listeners, creating subdirectories, and so on.
11500 Changes in version 0.1.1.5-alpha - 2005-08-08
11501 o Bugfixes included in 0.1.0.14.
11503 o Bugfixes on 0.1.0.x:
11504 - If you write "HiddenServicePort 6667 127.0.0.1 6668" in your
11505 torrc rather than "HiddenServicePort 6667 127.0.0.1:6668",
11506 it would silently using ignore the 6668.
11509 Changes in version 0.1.0.14 - 2005-08-08
11510 o Bugfixes on 0.1.0.x:
11511 - Fix the other half of the bug with crypto handshakes
11513 - Fix an assert trigger if you send a 'signal term' via the
11514 controller when it's listening for 'event info' messages.
11517 Changes in version 0.1.1.4-alpha - 2005-08-04
11518 o Bugfixes included in 0.1.0.13.
11521 - Improve tor_gettimeofday() granularity on windows.
11522 - Make clients regenerate their keys when their IP address changes.
11523 - Implement some more GETINFO goodness: expose helper nodes, config
11524 options, getinfo keys.
11527 Changes in version 0.1.0.13 - 2005-08-04
11528 o Bugfixes on 0.1.0.x:
11529 - Fix a critical bug in the security of our crypto handshakes.
11530 - Fix a size_t underflow in smartlist_join_strings2() that made
11531 it do bad things when you hand it an empty smartlist.
11532 - Fix Windows installer to ship Tor license (thanks to Aphex for
11533 pointing out this oversight) and put a link to the doc directory
11535 - Explicitly set no-unaligned-access for sparc: it turns out the
11536 new gcc's let you compile broken code, but that doesn't make it
11540 Changes in version 0.1.1.3-alpha - 2005-07-23
11541 o Bugfixes on 0.1.1.2-alpha:
11542 - Fix a bug in handling the controller's "post descriptor"
11544 - Fix several bugs in handling the controller's "extend circuit"
11546 - Fix a bug in handling the controller's "stream status" event.
11547 - Fix an assert failure if we have a controller listening for
11548 circuit events and we go offline.
11549 - Re-allow hidden service descriptors to publish 0 intro points.
11550 - Fix a crash when generating your hidden service descriptor if
11551 you don't have enough intro points already.
11553 o New features on 0.1.1.2-alpha:
11554 - New controller function "getinfo accounting", to ask how
11555 many bytes we've used in this time period.
11556 - Experimental support for helper nodes: a lot of the risk from
11557 a small static adversary comes because users pick new random
11558 nodes every time they rebuild a circuit. Now users will try to
11559 stick to the same small set of entry nodes if they can. Not
11560 enabled by default yet.
11562 o Bugfixes on 0.1.0.12:
11563 - If you're an auth dir server, always publish your dirport,
11564 even if you haven't yet found yourself to be reachable.
11565 - Fix a size_t underflow in smartlist_join_strings2() that made
11566 it do bad things when you hand it an empty smartlist.
11569 Changes in version 0.1.0.12 - 2005-07-18
11570 o New directory servers:
11571 - tor26 has changed IP address.
11573 o Bugfixes on 0.1.0.x:
11574 - Fix a possible double-free in tor_gzip_uncompress().
11575 - When --disable-threads is set, do not search for or link against
11576 pthreads libraries.
11577 - Don't trigger an assert if an authoritative directory server
11578 claims its dirport is 0.
11579 - Fix bug with removing Tor as an NT service: some people were
11580 getting "The service did not return an error." Thanks to Matt
11584 Changes in version 0.1.1.2-alpha - 2005-07-15
11585 o New directory servers:
11586 - tor26 has changed IP address.
11588 o Bugfixes on 0.1.0.x, crashes/leaks:
11589 - Port the servers-not-obeying-their-exit-policies fix from
11591 - Fix an fd leak in start_daemon().
11592 - On Windows, you can't always reopen a port right after you've
11593 closed it. So change retry_listeners() to only close and re-open
11594 ports that have changed.
11595 - Fix a possible double-free in tor_gzip_uncompress().
11597 o Bugfixes on 0.1.0.x, usability:
11598 - When tor_socketpair() fails in Windows, give a reasonable
11599 Windows-style errno back.
11600 - Let people type "tor --install" as well as "tor -install" when
11602 want to make it an NT service.
11603 - NT service patch from Matt Edman to improve error messages.
11604 - When the controller asks for a config option with an abbreviated
11605 name, give the full name in our response.
11606 - Correct the man page entry on TrackHostExitsExpire.
11607 - Looks like we were never delivering deflated (i.e. compressed)
11608 running-routers lists, even when asked. Oops.
11609 - When --disable-threads is set, do not search for or link against
11610 pthreads libraries.
11612 o Bugfixes on 0.1.1.x:
11613 - Fix a seg fault with autodetecting which controller version is
11617 - New hidden service descriptor format: put a version in it, and
11618 let people specify introduction/rendezvous points that aren't
11619 in "the directory" (which is subjective anyway).
11620 - Allow the DEBUG controller event to work again. Mark certain log
11621 entries as "don't tell this to controllers", so we avoid cycles.
11624 Changes in version 0.1.0.11 - 2005-06-30
11625 o Bugfixes on 0.1.0.x:
11626 - Fix major security bug: servers were disregarding their
11627 exit policies if clients behaved unexpectedly.
11628 - Make OS X init script check for missing argument, so we don't
11629 confuse users who invoke it incorrectly.
11630 - Fix a seg fault in "tor --hash-password foo".
11631 - The MAPADDRESS control command was broken.
11634 Changes in version 0.1.1.1-alpha - 2005-06-29
11636 - Make OS X init script check for missing argument, so we don't
11637 confuse users who invoke it incorrectly.
11638 - Fix a seg fault in "tor --hash-password foo".
11639 - Fix a possible way to DoS dirservers.
11640 - When we complain that your exit policy implicitly allows local or
11641 private address spaces, name them explicitly so operators can
11643 - Make the log message less scary when all the dirservers are
11644 temporarily unreachable.
11645 - We were printing the number of idle dns workers incorrectly when
11649 - Revised controller protocol (version 1) that uses ascii rather
11650 than binary. Add supporting libraries in python and java so you
11651 can use the controller from your applications without caring how
11652 our protocol works.
11653 - Spiffy new support for crypto hardware accelerators. Can somebody
11657 Changes in version 0.0.9.10 - 2005-06-16
11658 o Bugfixes on 0.0.9.x (backported from 0.1.0.10):
11659 - Refuse relay cells that claim to have a length larger than the
11660 maximum allowed. This prevents a potential attack that could read
11661 arbitrary memory (e.g. keys) from an exit server's process
11665 Changes in version 0.1.0.10 - 2005-06-14
11666 o Allow a few EINVALs from libevent before dying. Warn on kqueue with
11667 libevent before 1.1a.
11670 Changes in version 0.1.0.9-rc - 2005-06-09
11672 - Reset buf->highwater every time buf_shrink() is called, not just on
11673 a successful shrink. This was causing significant memory bloat.
11674 - Fix buffer overflow when checking hashed passwords.
11675 - Security fix: if seeding the RNG on Win32 fails, quit.
11676 - Allow seeding the RNG on Win32 even when you're not running as
11678 - Disable threading on Solaris too. Something is wonky with it,
11679 cpuworkers, and reentrant libs.
11680 - Reenable the part of the code that tries to flush as soon as an
11681 OR outbuf has a full TLS record available. Perhaps this will make
11682 OR outbufs not grow as huge except in rare cases, thus saving lots
11683 of CPU time plus memory.
11684 - Reject malformed .onion addresses rather then passing them on as
11685 normal web requests.
11686 - Adapt patch from Adam Langley: fix possible memory leak in
11687 tor_lookup_hostname().
11688 - Initialize libevent later in the startup process, so the logs are
11689 already established by the time we start logging libevent warns.
11690 - Use correct errno on win32 if libevent fails.
11691 - Check and warn about known-bad/slow libevent versions.
11692 - Pay more attention to the ClientOnly config option.
11693 - Have torctl.in/tor.sh.in check for location of su binary (needed
11695 - Correct/add man page entries for LongLivedPorts, ExitPolicy,
11696 KeepalivePeriod, ClientOnly, NoPublish, HttpProxy, HttpsProxy,
11697 HttpProxyAuthenticator
11698 - Stop warning about sigpipes in the logs. We're going to
11699 pretend that getting these occassionally is normal and fine.
11700 - Resolve OS X installer bugs: stop claiming to be 0.0.9.2 in
11702 installer screens; and don't put stuff into StartupItems unless
11703 the user asks you to.
11704 - Require servers that use the default dirservers to have public IP
11705 addresses. We have too many servers that are configured with private
11706 IPs and their admins never notice the log entries complaining that
11707 their descriptors are being rejected.
11708 - Add OSX uninstall instructions. An actual uninstall script will
11712 Changes in version 0.1.0.8-rc - 2005-05-23
11714 - It turns out that kqueue on OS X 10.3.9 was causing kernel
11715 panics. Disable kqueue on all OS X Tors.
11716 - Fix RPM: remove duplicate line accidentally added to the rpm
11718 - Disable threads on openbsd too, since its gethostaddr is not
11720 - Tolerate libevent 0.8 since it still works, even though it's
11722 - Enable building on Red Hat 9.0 again.
11723 - Allow the middle hop of the testing circuit to be running any
11724 version, now that most of them have the bugfix to let them connect
11725 to unknown servers. This will allow reachability testing to work
11726 even when 0.0.9.7-0.0.9.9 become obsolete.
11727 - Handle relay cells with rh.length too large. This prevents
11728 a potential attack that could read arbitrary memory (maybe even
11729 keys) from the exit server's process.
11730 - We screwed up the dirport reachability testing when we don't yet
11731 have a cached version of the directory. Hopefully now fixed.
11732 - Clean up router_load_single_router() (used by the controller),
11733 so it doesn't seg fault on error.
11734 - Fix a minor memory leak when somebody establishes an introduction
11735 point at your Tor server.
11736 - If a socks connection ends because read fails, don't warn that
11737 you're not sending a socks reply back.
11740 - Add HttpProxyAuthenticator config option too, that works like
11741 the HttpsProxyAuthenticator config option.
11742 - Encode hashed controller passwords in hex instead of base64,
11743 to make it easier to write controllers.
11746 Changes in version 0.1.0.7-rc - 2005-05-17
11748 - Fix a bug in the OS X package installer that prevented it from
11749 installing on Tiger.
11750 - Fix a script bug in the OS X package installer that made it
11751 complain during installation.
11752 - Find libevent even if it's hiding in /usr/local/ and your
11753 CFLAGS and LDFLAGS don't tell you to look there.
11754 - Be able to link with libevent as a shared library (the default
11755 after 1.0d), even if it's hiding in /usr/local/lib and even
11756 if you haven't added /usr/local/lib to your /etc/ld.so.conf,
11757 assuming you're running gcc. Otherwise fail and give a useful
11759 - Fix a bug in the RPM packager: set home directory for _tor to
11760 something more reasonable when first installing.
11761 - Free a minor amount of memory that is still reachable on exit.
11764 Changes in version 0.1.0.6-rc - 2005-05-14
11766 - Implement --disable-threads configure option. Disable threads on
11767 netbsd by default, because it appears to have no reentrant resolver
11769 - Apple's OS X 10.4.0 ships with a broken kqueue. The new libevent
11770 release (1.1) detects and disables kqueue if it's broken.
11771 - Append default exit policy before checking for implicit internal
11772 addresses. Now we don't log a bunch of complaints on startup
11773 when using the default exit policy.
11774 - Some people were putting "Address " in their torrc, and they had
11775 a buggy resolver that resolved " " to 0.0.0.0. Oops.
11776 - If DataDir is ~/.tor, and that expands to /.tor, then default to
11777 LOCALSTATEDIR/tor instead.
11778 - Fix fragmented-message bug in TorControl.py.
11779 - Resolve a minor bug which would prevent unreachable dirports
11780 from getting suppressed in the published descriptor.
11781 - When the controller gave us a new descriptor, we weren't resolving
11782 it immediately, so Tor would think its address was 0.0.0.0 until
11783 we fetched a new directory.
11784 - Fix an uppercase/lowercase case error in suppressing a bogus
11785 libevent warning on some Linuxes.
11788 - Begin scrubbing sensitive strings from logs by default. Turn off
11789 the config option SafeLogging if you need to do debugging.
11790 - Switch to a new buffer management algorithm, which tries to avoid
11791 reallocing and copying quite as much. In first tests it looks like
11792 it uses *more* memory on average, but less cpu.
11793 - First cut at support for "create-fast" cells. Clients can use
11794 these when extending to their first hop, since the TLS already
11795 provides forward secrecy and authentication. Not enabled on
11797 - When dirservers refuse a router descriptor, we now log its
11798 contactinfo, platform, and the poster's IP address.
11799 - Call tor_free_all instead of connections_free_all after forking, to
11800 save memory on systems that need to fork.
11801 - Whine at you if you're a server and you don't set your contactinfo.
11802 - Implement --verify-config command-line option to check if your torrc
11803 is valid without actually launching Tor.
11804 - Rewrite address "serifos.exit" to "localhost.serifos.exit"
11805 rather than just rejecting it.
11808 Changes in version 0.1.0.5-rc - 2005-04-27
11810 - Stop trying to print a null pointer if an OR conn fails because
11811 we didn't like its cert.
11813 - Switch our internal buffers implementation to use a ring buffer,
11814 to hopefully improve performance for fast servers a lot.
11815 - Add HttpsProxyAuthenticator support (basic auth only), based
11816 on patch from Adam Langley.
11817 - Bump the default BandwidthRate from 1 MB to 2 MB, to accommodate
11818 the fast servers that have been joining lately.
11819 - Give hidden service accesses extra time on the first attempt,
11820 since 60 seconds is often only barely enough. This might improve
11822 - Improve performance for dirservers: stop re-parsing the whole
11823 directory every time you regenerate it.
11824 - Add more debugging info to help us find the weird dns freebsd
11825 pthreads bug; cleaner debug messages to help track future issues.
11828 Changes in version 0.0.9.9 - 2005-04-23
11829 o Bugfixes on 0.0.9.x:
11830 - If unofficial Tor clients connect and send weird TLS certs, our
11831 Tor server triggers an assert. This release contains a minimal
11832 backport from the broader fix that we put into 0.1.0.4-rc.
11835 Changes in version 0.1.0.4-rc - 2005-04-23
11837 - If unofficial Tor clients connect and send weird TLS certs, our
11838 Tor server triggers an assert. Stop asserting, and start handling
11839 TLS errors better in other situations too.
11840 - When the controller asks us to tell it about all the debug-level
11841 logs, it turns out we were generating debug-level logs while
11842 telling it about them, which turns into a bad loop. Now keep
11843 track of whether you're sending a debug log to the controller,
11844 and don't log when you are.
11845 - Fix the "postdescriptor" feature of the controller interface: on
11846 non-complete success, only say "done" once.
11848 - Clients are now willing to load balance over up to 2mB, not 1mB,
11849 of advertised bandwidth capacity.
11850 - Add a NoPublish config option, so you can be a server (e.g. for
11851 testing running Tor servers in other Tor networks) without
11852 publishing your descriptor to the primary dirservers.
11855 Changes in version 0.1.0.3-rc - 2005-04-08
11856 o Improvements on 0.1.0.2-rc:
11857 - Client now retries when streams end early for 'hibernating' or
11858 'resource limit' reasons, rather than failing them.
11859 - More automated handling for dirserver operators:
11860 - Automatically approve nodes running 0.1.0.2-rc or later,
11861 now that the the reachability detection stuff is working.
11862 - Now we allow two unverified servers with the same nickname
11863 but different keys. But if a nickname is verified, only that
11864 nickname+key are allowed.
11865 - If you're an authdirserver connecting to an address:port,
11866 and it's not the OR you were expecting, forget about that
11867 descriptor. If he *was* the one you were expecting, then forget
11868 about all other descriptors for that address:port.
11869 - Allow servers to publish descriptors from 12 hours in the future.
11870 Corollary: only whine about clock skew from the dirserver if
11871 he's a trusted dirserver (since now even verified servers could
11872 have quite wrong clocks).
11873 - Adjust maximum skew and age for rendezvous descriptors: let skew
11874 be 48 hours rather than 90 minutes.
11875 - Efficiency improvements:
11876 - Keep a big splay tree of (circid,orconn)->circuit mappings to make
11877 it much faster to look up a circuit for each relay cell.
11878 - Remove most calls to assert_all_pending_dns_resolves_ok(),
11879 since they're eating our cpu on exit nodes.
11880 - Stop wasting time doing a case insensitive comparison for every
11881 dns name every time we do any lookup. Canonicalize the names to
11882 lowercase and be done with it.
11883 - Start sending 'truncated' cells back rather than destroy cells,
11884 if the circuit closes in front of you. This means we won't have
11885 to abandon partially built circuits.
11886 - Only warn once per nickname from add_nickname_list_to_smartlist
11887 per failure, so an entrynode or exitnode choice that's down won't
11889 - Put a note in the torrc about abuse potential with the default
11891 - Revise control spec and implementation to allow all log messages to
11892 be sent to controller with their severities intact (suggested by
11893 Matt Edman). Update TorControl to handle new log event types.
11894 - Provide better explanation messages when controller's POSTDESCRIPTOR
11896 - Stop putting nodename in the Platform string in server descriptors.
11897 It doesn't actually help, and it is confusing/upsetting some people.
11899 o Bugfixes on 0.1.0.2-rc:
11900 - We were printing the host mask wrong in exit policies in server
11901 descriptors. This isn't a critical bug though, since we were still
11902 obeying the exit policy internally.
11903 - Fix Tor when compiled with libevent but without pthreads: move
11904 connection_unregister() from _connection_free() to
11906 - Fix an assert trigger (already fixed in 0.0.9.x): when we have
11907 the rare mysterious case of accepting a conn on 0.0.0.0:0, then
11908 when we look through the connection array, we'll find any of the
11909 cpu/dnsworkers. This is no good.
11911 o Bugfixes on 0.0.9.8:
11912 - Fix possible bug on threading platforms (e.g. win32) which was
11913 leaking a file descriptor whenever a cpuworker or dnsworker died.
11914 - When using preferred entry or exit nodes, ignore whether the
11915 circuit wants uptime or capacity. They asked for the nodes, they
11917 - chdir() to your datadirectory at the *end* of the daemonize process,
11918 not the beginning. This was a problem because the first time you
11919 run tor, if your datadir isn't there, and you have runasdaemon set
11920 to 1, it will try to chdir to it before it tries to create it. Oops.
11921 - Handle changed router status correctly when dirserver reloads
11922 fingerprint file. We used to be dropping all unverified descriptors
11923 right then. The bug was hidden because we would immediately
11924 fetch a directory from another dirserver, which would include the
11925 descriptors we just dropped.
11926 - When we're connecting to an OR and he's got a different nickname/key
11927 than we were expecting, only complain loudly if we're an OP or a
11928 dirserver. Complaining loudly to the OR admins just confuses them.
11929 - Tie MAX_DIR_SIZE to MAX_BUF_SIZE, so now directory sizes won't get
11930 artificially capped at 500kB.
11933 Changes in version 0.0.9.8 - 2005-04-07
11934 o Bugfixes on 0.0.9.x:
11935 - We have a bug that I haven't found yet. Sometimes, very rarely,
11936 cpuworkers get stuck in the 'busy' state, even though the cpuworker
11937 thinks of itself as idle. This meant that no new circuits ever got
11938 established. Here's a workaround to kill any cpuworker that's been
11939 busy for more than 100 seconds.
11942 Changes in version 0.1.0.2-rc - 2005-04-01
11943 o Bugfixes on 0.1.0.1-rc:
11944 - Fixes on reachability detection:
11945 - Don't check for reachability while hibernating.
11946 - If ORPort is reachable but DirPort isn't, still publish the
11947 descriptor, but zero out DirPort until it's found reachable.
11948 - When building testing circs for ORPort testing, use only
11949 high-bandwidth nodes, so fewer circuits fail.
11950 - Complain about unreachable ORPort separately from unreachable
11951 DirPort, so the user knows what's going on.
11952 - Make sure we only conclude ORPort reachability if we didn't
11953 initiate the conn. Otherwise we could falsely conclude that
11954 we're reachable just because we connected to the guy earlier
11955 and he used that same pipe to extend to us.
11956 - Authdirservers shouldn't do ORPort reachability detection,
11957 since they're in clique mode, so it will be rare to find a
11958 server not already connected to them.
11959 - When building testing circuits, always pick middle hops running
11960 Tor 0.0.9.7, so we avoid the "can't extend to unknown routers"
11961 bug. (This is a kludge; it will go away when 0.0.9.x becomes
11963 - When we decide we're reachable, actually publish our descriptor
11965 - Fix bug in redirectstream in the controller.
11966 - Fix the state descriptor strings so logs don't claim edge streams
11967 are in a different state than they actually are.
11968 - Use recent libevent features when possible (this only really affects
11969 win32 and osx right now, because the new libevent with these
11970 features hasn't been released yet). Add code to suppress spurious
11972 - Prevent possible segfault in connection_close_unattached_ap().
11973 - Fix newlines on torrc in win32.
11974 - Improve error msgs when tor-resolve fails.
11976 o Improvements on 0.0.9.x:
11977 - New experimental script tor/contrib/ExerciseServer.py (needs more
11978 work) that uses the controller interface to build circuits and
11979 fetch pages over them. This will help us bootstrap servers that
11980 have lots of capacity but haven't noticed it yet.
11981 - New experimental script tor/contrib/PathDemo.py (needs more work)
11982 that uses the controller interface to let you choose whole paths
11984 "<hostname>.<path,separated by dots>.<length of path>.path"
11985 - When we've connected to an OR and handshaked but didn't like
11986 the result, we were closing the conn without sending destroy
11987 cells back for pending circuits. Now send those destroys.
11990 Changes in version 0.0.9.7 - 2005-04-01
11991 o Bugfixes on 0.0.9.x:
11992 - Fix another race crash bug (thanks to Glenn Fink for reporting).
11993 - Compare identity to identity, not to nickname, when extending to
11994 a router not already in the directory. This was preventing us from
11995 extending to unknown routers. Oops.
11996 - Make sure to create OS X Tor user in <500 range, so we aren't
11997 creating actual system users.
11998 - Note where connection-that-hasn't-sent-end was marked, and fix
11999 a few really loud instances of this harmless bug (it's fixed more
12003 Changes in version 0.1.0.1-rc - 2005-03-28
12005 - Add reachability testing. Your Tor server will automatically try
12006 to see if its ORPort and DirPort are reachable from the outside,
12007 and it won't upload its descriptor until it decides they are.
12008 - Handle unavailable hidden services better. Handle slow or busy
12009 hidden services better.
12010 - Add support for CONNECTing through https proxies, with "HttpsProxy"
12012 - New exit policy: accept most low-numbered ports, rather than
12013 rejecting most low-numbered ports.
12014 - More Tor controller support (still experimental). See
12015 http://tor.eff.org/doc/control-spec.txt for all the new features,
12016 including signals to emulate unix signals from any platform;
12017 redirectstream; extendcircuit; mapaddress; getinfo; postdescriptor;
12018 closestream; closecircuit; etc.
12019 - Make nt services work and start on startup on win32 (based on
12020 patch by Matt Edman).
12021 - Add a new AddressMap config directive to rewrite incoming socks
12022 addresses. This lets you, for example, declare an implicit
12023 required exit node for certain sites.
12024 - Add a new TrackHostExits config directive to trigger addressmaps
12025 for certain incoming socks addresses -- for sites that break when
12026 your exit keeps changing (based on patch by Mike Perry).
12027 - Redo the client-side dns cache so it's just an addressmap too.
12028 - Notice when our IP changes, and reset stats/uptime/reachability.
12029 - When an application is using socks5, give him the whole variety of
12030 potential socks5 responses (connect refused, host unreachable, etc),
12031 rather than just "success" or "failure".
12032 - A more sane version numbering system. See
12033 http://tor.eff.org/cvs/tor/doc/version-spec.txt for details.
12034 - New contributed script "exitlist": a simple python script to
12035 parse directories and find Tor nodes that exit to listed
12037 - New contributed script "privoxy-tor-toggle" to toggle whether
12038 Privoxy uses Tor. Seems to be configured for Debian by default.
12039 - Report HTTP reasons to client when getting a response from directory
12040 servers -- so you can actually know what went wrong.
12041 - New config option MaxAdvertisedBandwidth which lets you advertise
12042 a low bandwidthrate (to not attract as many circuits) while still
12043 allowing a higher bandwidthrate in reality.
12045 o Robustness/stability fixes:
12046 - Make Tor use Niels Provos's libevent instead of its current
12047 poll-but-sometimes-select mess. This will let us use faster async
12048 cores (like epoll, kpoll, and /dev/poll), and hopefully work better
12050 - pthread support now too. This was forced because when we forked,
12051 we ended up wasting a lot of duplicate ram over time. Also switch
12052 to foo_r versions of some library calls to allow reentry and
12054 - Better handling for heterogeneous / unreliable nodes:
12055 - Annotate circuits w/ whether they aim to contain high uptime nodes
12056 and/or high capacity nodes. When building circuits, choose
12058 - This means that every single node in an intro rend circuit,
12059 not just the last one, will have a minimum uptime.
12060 - New config option LongLivedPorts to indicate application streams
12061 that will want high uptime circuits.
12062 - Servers reset uptime when a dir fetch entirely fails. This
12063 hopefully reflects stability of the server's network connectivity.
12064 - If somebody starts his tor server in Jan 2004 and then fixes his
12065 clock, don't make his published uptime be a year.
12066 - Reset published uptime when you wake up from hibernation.
12067 - Introduce a notion of 'internal' circs, which are chosen without
12068 regard to the exit policy of the last hop. Intro and rendezvous
12069 circs must be internal circs, to avoid leaking information. Resolve
12070 and connect streams can use internal circs if they want.
12071 - New circuit pooling algorithm: make sure to have enough circs around
12072 to satisfy any predicted ports, and also make sure to have 2 internal
12073 circs around if we've required internal circs lately (and with high
12074 uptime if we've seen that lately too).
12075 - Split NewCircuitPeriod option into NewCircuitPeriod (30 secs),
12076 which describes how often we retry making new circuits if current
12077 ones are dirty, and MaxCircuitDirtiness (10 mins), which describes
12078 how long we're willing to make use of an already-dirty circuit.
12079 - Cannibalize GENERAL circs to be C_REND, C_INTRO, S_INTRO, and S_REND
12080 circ as necessary, if there are any completed ones lying around
12081 when we try to launch one.
12082 - Make hidden services try to establish a rendezvous for 30 seconds,
12083 rather than for n (where n=3) attempts to build a circuit.
12084 - Change SHUTDOWN_WAIT_LENGTH from a fixed 30 secs to a config option
12085 "ShutdownWaitLength".
12086 - Try to be more zealous about calling connection_edge_end when
12087 things go bad with edge conns in connection.c.
12088 - Revise tor-spec to add more/better stream end reasons.
12089 - Revise all calls to connection_edge_end to avoid sending "misc",
12090 and to take errno into account where possible.
12093 - Fix a race condition that can trigger an assert, when we have a
12094 pending create cell and an OR connection fails right then.
12095 - Fix several double-mark-for-close bugs, e.g. where we were finding
12096 a conn for a cell even if that conn is already marked for close.
12097 - Make sequence of log messages when starting on win32 with no config
12098 file more reasonable.
12099 - When choosing an exit node for a new non-internal circ, don't take
12100 into account whether it'll be useful for any pending x.onion
12101 addresses -- it won't.
12102 - Turn addr_policy_compare from a tristate to a quadstate; this should
12103 help address our "Ah, you allow 1.2.3.4:80. You are a good choice
12104 for google.com" problem.
12105 - Make "platform" string in descriptor more accurate for Win32 servers,
12106 so it's not just "unknown platform".
12107 - Fix an edge case in parsing config options (thanks weasel).
12108 If they say "--" on the commandline, it's not an option.
12109 - Reject odd-looking addresses at the client (e.g. addresses that
12110 contain a colon), rather than having the server drop them because
12112 - tor-resolve requests were ignoring .exit if there was a working circuit
12113 they could use instead.
12114 - REUSEADDR on normal platforms means you can rebind to the port
12115 right after somebody else has let it go. But REUSEADDR on win32
12116 means to let you bind to the port _even when somebody else
12117 already has it bound_! So, don't do that on Win32.
12118 - Change version parsing logic: a version is "obsolete" if it is not
12119 recommended and (1) there is a newer recommended version in the
12120 same series, or (2) there are no recommended versions in the same
12121 series, but there are some recommended versions in a newer series.
12122 A version is "new" if it is newer than any recommended version in
12124 - Stop most cases of hanging up on a socks connection without sending
12128 - Require BandwidthRate to be at least 20kB/s for servers.
12129 - When a dirserver causes you to give a warn, mention which dirserver
12131 - New config option DirAllowPrivateAddresses for authdirservers.
12132 Now by default they refuse router descriptors that have non-IP or
12133 private-IP addresses.
12134 - Stop publishing socksport in the directory, since it's not
12135 actually meant to be public. For compatibility, publish a 0 there
12137 - Change DirFetchPeriod/StatusFetchPeriod to have a special "Be
12138 smart" value, that is low for servers and high for clients.
12139 - If our clock jumps forward by 100 seconds or more, assume something
12140 has gone wrong with our network and abandon all not-yet-used circs.
12141 - Warn when exit policy implicitly allows local addresses.
12142 - If we get an incredibly skewed timestamp from a dirserver mirror
12143 that isn't a verified OR, don't warn -- it's probably him that's
12145 - Since we ship our own Privoxy on OS X, tweak it so it doesn't write
12146 cookies to disk and doesn't log each web request to disk. (Thanks
12147 to Brett Carrington for pointing this out.)
12148 - When a client asks us for a dir mirror and we don't have one,
12149 launch an attempt to get a fresh one.
12150 - If we're hibernating and we get a SIGINT, exit immediately.
12151 - Add --with-dmalloc ./configure option, to track memory leaks.
12152 - And try to free all memory on closing, so we can detect what
12154 - Cache local dns resolves correctly even when they're .exit
12156 - Give a better warning when some other server advertises an
12157 ORPort that is actually an apache running ssl.
12158 - Add "opt hibernating 1" to server descriptor to make it clearer
12159 whether the server is hibernating.
12162 Changes in version 0.0.9.6 - 2005-03-24
12163 o Bugfixes on 0.0.9.x (crashes and asserts):
12164 - Add new end stream reasons to maintainance branch. Fix bug where
12165 reason (8) could trigger an assert. Prevent bug from recurring.
12166 - Apparently win32 stat wants paths to not end with a slash.
12167 - Fix assert triggers in assert_cpath_layer_ok(), where we were
12168 blowing away the circuit that conn->cpath_layer points to, then
12169 checking to see if the circ is well-formed. Backport check to make
12170 sure we dont use the cpath on a closed connection.
12171 - Prevent circuit_resume_edge_reading_helper() from trying to package
12172 inbufs for marked-for-close streams.
12173 - Don't crash on hup if your options->address has become unresolvable.
12174 - Some systems (like OS X) sometimes accept() a connection and tell
12175 you the remote host is 0.0.0.0:0. If this happens, due to some
12176 other mis-features, we get confused; so refuse the conn for now.
12178 o Bugfixes on 0.0.9.x (other):
12179 - Fix harmless but scary "Unrecognized content encoding" warn message.
12180 - Add new stream error reason: TORPROTOCOL reason means "you are not
12181 speaking a version of Tor I understand; say bye-bye to your stream."
12182 - Be willing to cache directories from up to ROUTER_MAX_AGE seconds
12183 into the future, now that we are more tolerant of skew. This
12184 resolves a bug where a Tor server would refuse to cache a directory
12185 because all the directories it gets are too far in the future;
12186 yet the Tor server never logs any complaints about clock skew.
12187 - Mac packaging magic: make man pages useable, and do not overwrite
12188 existing torrc files.
12189 - Make OS X log happily to /var/log/tor/tor.log
12192 Changes in version 0.0.9.5 - 2005-02-22
12193 o Bugfixes on 0.0.9.x:
12194 - Fix an assert race at exit nodes when resolve requests fail.
12195 - Stop picking unverified dir mirrors--it only leads to misery.
12196 - Patch from Matt Edman to make NT services work better. Service
12197 support is still not compiled into the executable by default.
12198 - Patch from Dmitri Bely so the Tor service runs better under
12199 the win32 SYSTEM account.
12200 - Make tor-resolve actually work (?) on Win32.
12201 - Fix a sign bug when getrlimit claims to have 4+ billion
12202 file descriptors available.
12203 - Stop refusing to start when bandwidthburst == bandwidthrate.
12204 - When create cells have been on the onion queue more than five
12205 seconds, just send back a destroy and take them off the list.
12208 Changes in version 0.0.9.4 - 2005-02-03
12209 o Bugfixes on 0.0.9:
12210 - Fix an assert bug that took down most of our servers: when
12211 a server claims to have 1 GB of bandwidthburst, don't
12213 - Don't crash as badly if we have spawned the max allowed number
12214 of dnsworkers, or we're out of file descriptors.
12215 - Block more file-sharing ports in the default exit policy.
12216 - MaxConn is now automatically set to the hard limit of max
12217 file descriptors we're allowed (ulimit -n), minus a few for
12219 - Give a clearer message when servers need to raise their
12220 ulimit -n when they start running out of file descriptors.
12221 - SGI Compatibility patches from Jan Schaumann.
12222 - Tolerate a corrupt cached directory better.
12223 - When a dirserver hasn't approved your server, list which one.
12224 - Go into soft hibernation after 95% of the bandwidth is used,
12225 not 99%. This is especially important for daily hibernators who
12226 have a small accounting max. Hopefully it will result in fewer
12227 cut connections when the hard hibernation starts.
12228 - Load-balance better when using servers that claim more than
12229 800kB/s of capacity.
12230 - Make NT services work (experimental, only used if compiled in).
12233 Changes in version 0.0.9.3 - 2005-01-21
12234 o Bugfixes on 0.0.9:
12235 - Backport the cpu use fixes from main branch, so busy servers won't
12236 need as much processor time.
12237 - Work better when we go offline and then come back, or when we
12238 run Tor at boot before the network is up. We do this by
12239 optimistically trying to fetch a new directory whenever an
12240 application request comes in and we think we're offline -- the
12241 human is hopefully a good measure of when the network is back.
12242 - Backport some minimal hidserv bugfixes: keep rend circuits open as
12243 long as you keep using them; actually publish hidserv descriptors
12244 shortly after they change, rather than waiting 20-40 minutes.
12245 - Enable Mac startup script by default.
12246 - Fix duplicate dns_cancel_pending_resolve reported by Giorgos Pallas.
12247 - When you update AllowUnverifiedNodes or FirewallPorts via the
12248 controller's setconf feature, we were always appending, never
12250 - When you update HiddenServiceDir via setconf, it was screwing up
12251 the order of reading the lines, making it fail.
12252 - Do not rewrite a cached directory back to the cache; otherwise we
12253 will think it is recent and not fetch a newer one on startup.
12254 - Workaround for webservers that lie about Content-Encoding: Tor
12255 now tries to autodetect compressed directories and compression
12256 itself. This lets us Proxypass dir fetches through apache.
12259 Changes in version 0.0.9.2 - 2005-01-04
12260 o Bugfixes on 0.0.9 (crashes and asserts):
12261 - Fix an assert on startup when the disk is full and you're logging
12263 - If you do socks4 with an IP of 0.0.0.x but *don't* provide a socks4a
12264 style address, then we'd crash.
12265 - Fix an assert trigger when the running-routers string we get from
12266 a dirserver is broken.
12267 - Make worker threads start and run on win32. Now win32 servers
12269 - Bandaid (not actually fix, but now it doesn't crash) an assert
12270 where the dns worker dies mysteriously and the main Tor process
12271 doesn't remember anything about the address it was resolving.
12273 o Bugfixes on 0.0.9 (Win32):
12274 - Workaround for brain-damaged __FILE__ handling on MSVC: keep Nick's
12275 name out of the warning/assert messages.
12276 - Fix a superficial "unhandled error on read" bug on win32.
12277 - The win32 installer no longer requires a click-through for our
12278 license, since our Free Software license grants rights but does not
12280 - Win32: When connecting to a dirserver fails, try another one
12281 immediately. (This was already working for non-win32 Tors.)
12282 - Stop trying to parse $HOME on win32 when hunting for default
12284 - Make tor-resolve.c work on win32 by calling network_init().
12286 o Bugfixes on 0.0.9 (other):
12287 - Make 0.0.9.x build on Solaris again.
12288 - Due to a fencepost error, we were blowing away the \n when reporting
12289 confvalue items in the controller. So asking for multiple config
12290 values at once couldn't work.
12291 - When listing circuits that are pending on an opening OR connection,
12292 if we're an OR we were listing circuits that *end* at us as
12293 being pending on every listener, dns/cpu worker, etc. Stop that.
12294 - Dirservers were failing to create 'running-routers' or 'directory'
12295 strings if we had more than some threshold of routers. Fix them so
12296 they can handle any number of routers.
12297 - Fix a superficial "Duplicate mark for close" bug.
12298 - Stop checking for clock skew for OR connections, even for servers.
12299 - Fix a fencepost error that was chopping off the last letter of any
12300 nickname that is the maximum allowed nickname length.
12301 - Update URLs in log messages so they point to the new website.
12302 - Fix a potential problem in mangling server private keys while
12303 writing to disk (not triggered yet, as far as we know).
12304 - Include the licenses for other free software we include in Tor,
12305 now that we're shipping binary distributions more regularly.
12308 Changes in version 0.0.9.1 - 2004-12-15
12309 o Bugfixes on 0.0.9:
12310 - Make hibernation actually work.
12311 - Make HashedControlPassword config option work.
12312 - When we're reporting event circuit status to a controller,
12313 don't use the stream status code.
12316 Changes in version 0.0.9 - 2004-12-12
12318 - Clean up manpage and torrc.sample file.
12319 - Clean up severities and text of log warnings.
12321 - Make servers trigger an assert when they enter hibernation.
12324 Changes in version 0.0.9rc7 - 2004-12-08
12325 o Bugfixes on 0.0.9rc:
12326 - Fix a stack-trashing crash when an exit node begins hibernating.
12327 - Avoid looking at unallocated memory while considering which
12328 ports we need to build circuits to cover.
12329 - Stop a sigpipe: when an 'end' cell races with eof from the app,
12330 we shouldn't hold-open-until-flush if the eof arrived first.
12331 - Fix a bug with init_cookie_authentication() in the controller.
12332 - When recommending new-format log lines, if the upper bound is
12333 LOG_ERR, leave it implicit.
12335 o Bugfixes on 0.0.8.1:
12336 - Fix a whole slew of memory leaks.
12337 - Fix isspace() and friends so they still make Solaris happy
12338 but also so they don't trigger asserts on win32.
12339 - Fix parse_iso_time on platforms without strptime (eg win32).
12340 - win32: tolerate extra "readable" events better.
12341 - win32: when being multithreaded, leave parent fdarray open.
12342 - Make unit tests work on win32.
12345 Changes in version 0.0.9rc6 - 2004-12-06
12346 o Bugfixes on 0.0.9pre:
12347 - Clean up some more integer underflow opportunities (not exploitable
12349 - While hibernating, hup should not regrow our listeners.
12350 - Send an end to the streams we close when we hibernate, rather
12351 than just chopping them off.
12352 - React to eof immediately on non-open edge connections.
12354 o Bugfixes on 0.0.8.1:
12355 - Calculate timeout for waiting for a connected cell from the time
12356 we sent the begin cell, not from the time the stream started. If
12357 it took a long time to establish the circuit, we would time out
12358 right after sending the begin cell.
12359 - Fix router_compare_addr_to_addr_policy: it was not treating a port
12360 of * as always matching, so we were picking reject *:* nodes as
12361 exit nodes too. Oops.
12364 - New circuit building strategy: keep a list of ports that we've
12365 used in the past 6 hours, and always try to have 2 circuits open
12366 or on the way that will handle each such port. Seed us with port
12367 80 so web users won't complain that Tor is "slow to start up".
12368 - Make kill -USR1 dump more useful stats about circuits.
12369 - When warning about retrying or giving up, print the address, so
12370 the user knows which one it's talking about.
12371 - If you haven't used a clean circuit in an hour, throw it away,
12372 just to be on the safe side. (This means after 6 hours a totally
12373 unused Tor client will have no circuits open.)
12376 Changes in version 0.0.9rc5 - 2004-12-01
12377 o Bugfixes on 0.0.8.1:
12378 - Disallow NDEBUG. We don't ever want anybody to turn off debug.
12379 - Let resolve conns retry/expire also, rather than sticking around
12381 - If we are using select, make sure we stay within FD_SETSIZE.
12383 o Bugfixes on 0.0.9pre:
12384 - Fix integer underflow in tor_vsnprintf() that may be exploitable,
12385 but doesn't seem to be currently; thanks to Ilja van Sprundel for
12387 - If anybody set DirFetchPostPeriod, give them StatusFetchPeriod
12388 instead. Impose minima and maxima for all *Period options; impose
12389 even tighter maxima for fetching if we are a caching dirserver.
12390 Clip rather than rejecting.
12391 - Fetch cached running-routers from servers that serve it (that is,
12392 authdirservers and servers running 0.0.9rc5-cvs or later.)
12395 - Accept *:706 (silc) in default exit policy.
12396 - Implement new versioning format for post 0.1.
12397 - Support "foo.nickname.exit" addresses, to let Alice request the
12398 address "foo" as viewed by exit node "nickname". Based on a patch
12400 - Make tor --version --version dump the cvs Id of every file.
12403 Changes in version 0.0.9rc4 - 2004-11-28
12404 o Bugfixes on 0.0.8.1:
12405 - Make windows sockets actually non-blocking (oops), and handle
12406 win32 socket errors better.
12408 o Bugfixes on 0.0.9rc1:
12409 - Actually catch the -USR2 signal.
12412 Changes in version 0.0.9rc3 - 2004-11-25
12413 o Bugfixes on 0.0.8.1:
12414 - Flush the log file descriptor after we print "Tor opening log file",
12415 so we don't see those messages days later.
12417 o Bugfixes on 0.0.9rc1:
12418 - Make tor-resolve work again.
12419 - Avoid infinite loop in tor-resolve if tor hangs up on it.
12420 - Fix an assert trigger for clients/servers handling resolves.
12423 Changes in version 0.0.9rc2 - 2004-11-24
12424 o Bugfixes on 0.0.9rc1:
12425 - I broke socks5 support while fixing the eof bug.
12426 - Allow unitless bandwidths and intervals; they default to bytes
12428 - New servers don't start out hibernating; they are active until
12429 they run out of bytes, so they have a better estimate of how
12430 long it takes, and so their operators can know they're working.
12433 Changes in version 0.0.9rc1 - 2004-11-23
12434 o Bugfixes on 0.0.8.1:
12435 - Finally fix a bug that's been plaguing us for a year:
12436 With high load, circuit package window was reaching 0. Whenever
12437 we got a circuit-level sendme, we were reading a lot on each
12438 socket, but only writing out a bit. So we would eventually reach
12439 eof. This would be noticed and acted on even when there were still
12440 bytes sitting in the inbuf.
12441 - When poll() is interrupted, we shouldn't believe the revents values.
12443 o Bugfixes on 0.0.9pre6:
12444 - Fix hibernate bug that caused pre6 to be broken.
12445 - Don't keep rephist info for routers that haven't had activity for
12446 24 hours. (This matters now that clients have keys, since we track
12448 - Never call close_temp_logs while validating log options.
12449 - Fix backslash-escaping on tor.sh.in and torctl.in.
12452 - Implement weekly/monthly/daily accounting: now you specify your
12453 hibernation properties by
12454 AccountingMax N bytes|KB|MB|GB|TB
12455 AccountingStart day|week|month [day] HH:MM
12456 Defaults to "month 1 0:00".
12457 - Let bandwidth and interval config options be specified as 5 bytes,
12458 kb, kilobytes, etc; and as seconds, minutes, hours, days, weeks.
12459 - kill -USR2 now moves all logs to loglevel debug (kill -HUP to
12460 get back to normal.)
12461 - If your requested entry or exit node has advertised bandwidth 0,
12463 - Be more greedy about filling up relay cells -- we try reading again
12464 once we've processed the stuff we read, in case enough has arrived
12465 to fill the last cell completely.
12466 - Apply NT service patch from Osamu Fujino. Still needs more work.
12469 Changes in version 0.0.9pre6 - 2004-11-15
12470 o Bugfixes on 0.0.8.1:
12471 - Fix assert failure on malformed socks4a requests.
12472 - Use identity comparison, not nickname comparison, to choose which
12473 half of circuit-ID-space each side gets to use. This is needed
12474 because sometimes we think of a router as a nickname, and sometimes
12475 as a hex ID, and we can't predict what the other side will do.
12476 - Catch and ignore SIGXFSZ signals when log files exceed 2GB; our
12477 write() call will fail and we handle it there.
12478 - Add a FAST_SMARTLIST define to optionally inline smartlist_get
12479 and smartlist_len, which are two major profiling offenders.
12481 o Bugfixes on 0.0.9pre5:
12482 - Fix a bug in read_all that was corrupting config files on windows.
12483 - When we're raising the max number of open file descriptors to
12484 'unlimited', don't log that we just raised it to '-1'.
12485 - Include event code with events, as required by control-spec.txt.
12486 - Don't give a fingerprint when clients do --list-fingerprint:
12487 it's misleading, because it will never be the same again.
12488 - Stop using strlcpy in tor_strndup, since it was slowing us
12490 - Remove warn on startup about missing cached-directory file.
12491 - Make kill -USR1 work again.
12492 - Hibernate if we start tor during the "wait for wakeup-time" phase
12493 of an accounting interval. Log our hibernation plans better.
12494 - Authoritative dirservers now also cache their directory, so they
12495 have it on start-up.
12498 - Fetch running-routers; cache running-routers; compress
12499 running-routers; serve compressed running-routers.z
12500 - Add NSI installer script contributed by J Doe.
12501 - Commit VC6 and VC7 workspace/project files.
12502 - Commit a tor.spec for making RPM files, with help from jbash.
12503 - Add contrib/torctl.in contributed by Glenn Fink.
12504 - Implement the control-spec's SAVECONF command, to write your
12505 configuration to torrc.
12506 - Get cookie authentication for the controller closer to working.
12507 - Include control-spec.txt in the tarball.
12508 - When set_conf changes our server descriptor, upload a new copy.
12509 But don't upload it too often if there are frequent changes.
12510 - Document authentication config in man page, and document signals
12512 - Clean up confusing parts of man page and torrc.sample.
12513 - Make expand_filename handle ~ and ~username.
12514 - Use autoconf to enable largefile support where necessary. Use
12515 ftello where available, since ftell can fail at 2GB.
12516 - Distinguish between TOR_TLS_CLOSE and TOR_TLS_ERROR, so we can
12517 log more informatively.
12518 - Give a slightly more useful output for "tor -h".
12519 - Refuse application socks connections to port 0.
12520 - Check clock skew for verified servers, but allow unverified
12521 servers and clients to have any clock skew.
12522 - Break DirFetchPostPeriod into:
12523 - DirFetchPeriod for fetching full directory,
12524 - StatusFetchPeriod for fetching running-routers,
12525 - DirPostPeriod for posting server descriptor,
12526 - RendPostPeriod for posting hidden service descriptors.
12527 - Make sure the hidden service descriptors are at a random offset
12528 from each other, to hinder linkability.
12531 Changes in version 0.0.9pre5 - 2004-11-09
12532 o Bugfixes on 0.0.9pre4:
12533 - Fix a seg fault in unit tests (doesn't affect main program).
12534 - Fix an assert bug where a hidden service provider would fail if
12535 the first hop of his rendezvous circuit was down.
12536 - Hidden service operators now correctly handle version 1 style
12537 INTRODUCE1 cells (nobody generates them still, so not a critical
12539 - If do_hup fails, actually notice.
12540 - Handle more errnos from accept() without closing the listener.
12541 Some OpenBSD machines were closing their listeners because
12542 they ran out of file descriptors.
12543 - Send resolve cells to exit routers that are running a new
12544 enough version of the resolve code to work right.
12545 - Better handling of winsock includes on non-MSV win32 compilers.
12546 - Some people had wrapped their tor client/server in a script
12547 that would restart it whenever it died. This did not play well
12548 with our "shut down if your version is obsolete" code. Now people
12549 don't fetch a new directory if their local cached version is
12551 - Make our autogen.sh work on ksh as well as bash.
12554 - Hibernation: New config option "AccountingMaxKB" lets you
12555 set how many KBytes per month you want to allow your server to
12556 consume. Rather than spreading those bytes out evenly over the
12557 month, we instead hibernate for some of the month and pop up
12558 at a deterministic time, work until the bytes are consumed, then
12559 hibernate again. Config option "MonthlyAccountingStart" lets you
12560 specify which day of the month your billing cycle starts on.
12561 - Control interface: a separate program can now talk to your
12562 client/server over a socket, and get/set config options, receive
12563 notifications of circuits and streams starting/finishing/dying,
12564 bandwidth used, etc. The next step is to get some GUIs working.
12565 Let us know if you want to help out. See doc/control-spec.txt .
12566 - Ship a contrib/tor-control.py as an example script to interact
12567 with the control port.
12568 - "tor --hash-password zzyxz" will output a salted password for
12569 use in authenticating to the control interface.
12570 - New log format in config:
12571 "Log minsev[-maxsev] stdout|stderr|syslog" or
12572 "Log minsev[-maxsev] file /var/foo"
12575 - DirPolicy config option, to let people reject incoming addresses
12576 from their dirserver.
12577 - "tor --list-fingerprint" will list your identity key fingerprint
12579 - Add "pass" target for RedirectExit, to make it easier to break
12580 out of a sequence of RedirectExit rules.
12581 - Clients now generate a TLS cert too, in preparation for having
12582 them act more like real nodes.
12583 - Ship src/win32/ in the tarball, so people can use it to build.
12584 - Make old win32 fall back to CWD if SHGetSpecialFolderLocation
12586 - New "router-status" line in directory, to better bind each verified
12587 nickname to its identity key.
12588 - Deprecate unofficial config option abbreviations, and abbreviations
12589 not on the command line.
12590 - Add a pure-C tor-resolve implementation.
12591 - Use getrlimit and friends to ensure we can reach MaxConn (currently
12592 1024) file descriptors.
12594 o Code security improvements, inspired by Ilja:
12595 - Replace sprintf with snprintf. (I think they were all safe, but
12597 - Replace strcpy/strncpy with strlcpy in more places.
12598 - Avoid strcat; use snprintf or strlcat instead.
12599 - snprintf wrapper with consistent (though not C99) overflow behavior.
12602 Changes in version 0.0.9pre4 - 2004-10-17
12603 o Bugfixes on 0.0.9pre3:
12604 - If the server doesn't specify an exit policy, use the real default
12605 exit policy, not reject *:*.
12606 - Ignore fascistfirewall when uploading/downloading hidden service
12607 descriptors, since we go through Tor for those; and when using
12608 an HttpProxy, since we assume it can reach them all.
12609 - When looking for an authoritative dirserver, use only the ones
12610 configured at boot. Don't bother looking in the directory.
12611 - The rest of the fix for get_default_conf_file() on older win32.
12612 - Make 'Routerfile' config option obsolete.
12615 - New 'MyFamily nick1,...' config option for a server to
12616 specify other servers that shouldn't be used in the same circuit
12617 with it. Only believed if nick1 also specifies us.
12618 - New 'NodeFamily nick1,nick2,...' config option for a client to
12619 specify nodes that it doesn't want to use in the same circuit.
12620 - New 'Redirectexit pattern address:port' config option for a
12621 server to redirect exit connections, e.g. to a local squid.
12624 Changes in version 0.0.9pre3 - 2004-10-13
12625 o Bugfixes on 0.0.8.1:
12626 - Better torrc example lines for dirbindaddress and orbindaddress.
12627 - Improved bounds checking on parsed ints (e.g. config options and
12628 the ones we find in directories.)
12629 - Better handling of size_t vs int, so we're more robust on 64
12631 - Fix the rest of the bug where a newly started OR would appear
12632 as unverified even after we've added his fingerprint and hupped
12634 - Fix a bug from 0.0.7: when read() failed on a stream, we would
12635 close it without sending back an end. So 'connection refused'
12636 would simply be ignored and the user would get no response.
12638 o Bugfixes on 0.0.9pre2:
12639 - Serving the cached-on-disk directory to people is bad. We now
12640 provide no directory until we've fetched a fresh one.
12641 - Workaround for bug on windows where cached-directories get crlf
12643 - Make get_default_conf_file() work on older windows too.
12644 - If we write a *:* exit policy line in the descriptor, don't write
12645 any more exit policy lines.
12648 - Use only 0.0.9pre1 and later servers for resolve cells.
12649 - Make the dirservers file obsolete.
12650 - Include a dir-signing-key token in directories to tell the
12651 parsing entity which key is being used to sign.
12652 - Remove the built-in bulky default dirservers string.
12653 - New config option "Dirserver %s:%d [fingerprint]", which can be
12654 repeated as many times as needed. If no dirservers specified,
12655 default to moria1,moria2,tor26.
12656 - Make moria2 advertise a dirport of 80, so people behind firewalls
12657 will be able to get a directory.
12658 - Http proxy support
12659 - Dirservers translate requests for http://%s:%d/x to /x
12660 - You can specify "HttpProxy %s[:%d]" and all dir fetches will
12661 be routed through this host.
12662 - Clients ask for /tor/x rather than /x for new enough dirservers.
12663 This way we can one day coexist peacefully with apache.
12664 - Clients specify a "Host: %s%d" http header, to be compatible
12665 with more proxies, and so running squid on an exit node can work.
12668 Changes in version 0.0.8.1 - 2004-10-13
12670 - Fix a seg fault that can be triggered remotely for Tor
12671 clients/servers with an open dirport.
12672 - Fix a rare assert trigger, where routerinfos for entries in
12673 our cpath would expire while we're building the path.
12674 - Fix a bug in OutboundBindAddress so it (hopefully) works.
12675 - Fix a rare seg fault for people running hidden services on
12676 intermittent connections.
12677 - Fix a bug in parsing opt keywords with objects.
12678 - Fix a stale pointer assert bug when a stream detaches and
12680 - Fix a string format vulnerability (probably not exploitable)
12681 in reporting stats locally.
12682 - Fix an assert trigger: sometimes launching circuits can fail
12683 immediately, e.g. because too many circuits have failed recently.
12684 - Fix a compile warning on 64 bit platforms.
12687 Changes in version 0.0.9pre2 - 2004-10-03
12689 - Make fetching a cached directory work for 64-bit platforms too.
12690 - Make zlib.h a required header, not an optional header.
12693 Changes in version 0.0.9pre1 - 2004-10-01
12695 - Stop using separate defaults for no-config-file and
12696 empty-config-file. Now you have to explicitly turn off SocksPort,
12697 if you don't want it open.
12698 - Fix a bug in OutboundBindAddress so it (hopefully) works.
12699 - Improve man page to mention more of the 0.0.8 features.
12700 - Fix a rare seg fault for people running hidden services on
12701 intermittent connections.
12702 - Change our file IO stuff (especially wrt OpenSSL) so win32 is
12704 - Fix more dns related bugs: send back resolve_failed and end cells
12705 more reliably when the resolve fails, rather than closing the
12706 circuit and then trying to send the cell. Also attach dummy resolve
12707 connections to a circuit *before* calling dns_resolve(), to fix
12708 a bug where cached answers would never be sent in RESOLVED cells.
12709 - When we run out of disk space, or other log writing error, don't
12710 crash. Just stop logging to that log and continue.
12711 - We were starting to daemonize before we opened our logs, so if
12712 there were any problems opening logs, we would complain to stderr,
12713 which wouldn't work, and then mysteriously exit.
12714 - Fix a rare bug where sometimes a verified OR would connect to us
12715 before he'd uploaded his descriptor, which would cause us to
12716 assign conn->nickname as though he's unverified. Now we look through
12717 the fingerprint list to see if he's there.
12718 - Fix a rare assert trigger, where routerinfos for entries in
12719 our cpath would expire while we're building the path.
12722 - Clients can ask dirservers for /dir.z to get a compressed version
12723 of the directory. Only works for servers running 0.0.9, of course.
12724 - Make clients cache directories and use them to seed their router
12725 lists at startup. This means clients have a datadir again.
12726 - Configuration infrastructure support for warning on obsolete
12728 - Respond to content-encoding headers by trying to uncompress as
12730 - Reply with a deflated directory when a client asks for "dir.z".
12731 We could use allow-encodings instead, but allow-encodings isn't
12732 specified in HTTP 1.0.
12733 - Raise the max dns workers from 50 to 100.
12734 - Discourage people from setting their dirfetchpostperiod more often
12735 than once per minute.
12736 - Protect dirservers from overzealous descriptor uploading -- wait
12737 10 seconds after directory gets dirty, before regenerating.
12740 Changes in version 0.0.8 - 2004-08-25
12741 o Port it to SunOS 5.9 / Athena
12744 Changes in version 0.0.8rc2 - 2004-08-20
12745 o Make it compile on cygwin again.
12746 o When picking unverified routers, skip those with low uptime and/or
12747 low bandwidth, depending on what properties you care about.
12750 Changes in version 0.0.8rc1 - 2004-08-18
12751 o Changes from 0.0.7.3:
12753 - Fix assert triggers: if the other side returns an address 0.0.0.0,
12754 don't put it into the client dns cache.
12755 - If a begin failed due to exit policy, but we believe the IP address
12756 should have been allowed, switch that router to exitpolicy reject *:*
12757 until we get our next directory.
12759 - Clients choose nodes proportional to advertised bandwidth.
12760 - Avoid using nodes with low uptime as introduction points.
12761 - Handle servers with dynamic IP addresses: don't replace
12762 options->Address with the resolved one at startup, and
12763 detect our address right before we make a routerinfo each time.
12764 - 'FascistFirewall' option to pick dirservers and ORs on specific
12765 ports; plus 'FirewallPorts' config option to tell FascistFirewall
12766 which ports are open. (Defaults to 80,443)
12767 - Be more aggressive about trying to make circuits when the network
12768 has changed (e.g. when you unsuspend your laptop).
12769 - Check for time skew on http headers; report date in response to
12771 - If the entrynode config line has only one node, don't pick it as
12773 - Add strict{entry|exit}nodes config options. If set to 1, then
12774 we refuse to build circuits that don't include the specified entry
12776 - OutboundBindAddress config option, to bind to a specific
12777 IP address for outgoing connect()s.
12778 - End truncated log entries (e.g. directories) with "[truncated]".
12780 o Patches to 0.0.8preX:
12782 - Patches to compile and run on win32 again (maybe)?
12783 - Fix crash when looking for ~/.torrc with no $HOME set.
12784 - Fix a race bug in the unit tests.
12785 - Handle verified/unverified name collisions better when new
12786 routerinfo's arrive in a directory.
12787 - Sometimes routers were getting entered into the stats before
12788 we'd assigned their identity_digest. Oops.
12789 - Only pick and establish intro points after we've gotten a
12792 - AllowUnverifiedNodes config option to let circuits choose no-name
12793 routers in entry,middle,exit,introduction,rendezvous positions.
12794 Allow middle and rendezvous positions by default.
12795 - Add a man page for tor-resolve.
12798 Changes in version 0.0.7.3 - 2004-08-12
12799 o Stop dnsworkers from triggering an assert failure when you
12800 ask them to resolve the host "".
12803 Changes in version 0.0.8pre3 - 2004-08-09
12804 o Changes from 0.0.7.2:
12805 - Allow multiple ORs with same nickname in routerlist -- now when
12806 people give us one identity key for a nickname, then later
12807 another, we don't constantly complain until the first expires.
12808 - Remember used bandwidth (both in and out), and publish 15-minute
12809 snapshots for the past day into our descriptor.
12810 - You can now fetch $DIRURL/running-routers to get just the
12811 running-routers line, not the whole descriptor list. (But
12812 clients don't use this yet.)
12813 - When people mistakenly use Tor as an http proxy, point them
12814 at the tor-doc.html rather than the INSTALL.
12815 - Remove our mostly unused -- and broken -- hex_encode()
12816 function. Use base16_encode() instead. (Thanks to Timo Lindfors
12817 for pointing out this bug.)
12818 - Rotate onion keys every 12 hours, not every 2 hours, so we have
12819 fewer problems with people using the wrong key.
12820 - Change the default exit policy to reject the default edonkey,
12821 kazaa, gnutella ports.
12822 - Add replace_file() to util.[ch] to handle win32's rename().
12824 o Changes from 0.0.8preX:
12825 - Fix two bugs in saving onion keys to disk when rotating, so
12826 hopefully we'll get fewer people using old onion keys.
12827 - Fix an assert error that was making SocksPolicy not work.
12828 - Be willing to expire routers that have an open dirport -- it's
12829 just the authoritative dirservers we want to not forget.
12830 - Reject tor-resolve requests for .onion addresses early, so we
12831 don't build a whole rendezvous circuit and then fail.
12832 - When you're warning a server that he's unverified, don't cry
12833 wolf unpredictably.
12834 - Fix a race condition: don't try to extend onto a connection
12835 that's still handshaking.
12836 - For servers in clique mode, require the conn to be open before
12837 you'll choose it for your path.
12838 - Fix some cosmetic bugs about duplicate mark-for-close, lack of
12839 end relay cell, etc.
12840 - Measure bandwidth capacity over the last 24 hours, not just 12
12841 - Bugfix: authoritative dirservers were making and signing a new
12842 directory for each client, rather than reusing the cached one.
12845 Changes in version 0.0.8pre2 - 2004-08-04
12846 o Changes from 0.0.7.2:
12848 - Check directory signature _before_ you decide whether you're
12849 you're running an obsolete version and should exit.
12850 - Check directory signature _before_ you parse the running-routers
12851 list to decide who's running or verified.
12852 - Bugfixes and features:
12853 - Check return value of fclose while writing to disk, so we don't
12854 end up with broken files when servers run out of disk space.
12855 - Log a warning if the user uses an unsafe socks variant, so people
12856 are more likely to learn about privoxy or socat.
12857 - Dirservers now include RFC1123-style dates in the HTTP headers,
12858 which one day we will use to better detect clock skew.
12860 o Changes from 0.0.8pre1:
12861 - Make it compile without warnings again on win32.
12862 - Log a warning if you're running an unverified server, to let you
12863 know you might want to get it verified.
12864 - Only pick a default nickname if you plan to be a server.
12867 Changes in version 0.0.8pre1 - 2004-07-23
12869 - Made our unit tests compile again on OpenBSD 3.5, and tor
12870 itself compile again on OpenBSD on a sparc64.
12871 - We were neglecting milliseconds when logging on win32, so
12872 everything appeared to happen at the beginning of each second.
12874 o Protocol changes:
12875 - 'Extend' relay cell payloads now include the digest of the
12876 intended next hop's identity key. Now we can verify that we're
12877 extending to the right router, and also extend to routers we
12878 hadn't heard of before.
12881 - Tor nodes can now act as relays (with an advertised ORPort)
12882 without being manually verified by the dirserver operators.
12883 - Uploaded descriptors of unverified routers are now accepted
12884 by the dirservers, and included in the directory.
12885 - Verified routers are listed by nickname in the running-routers
12886 list; unverified routers are listed as "$<fingerprint>".
12887 - We now use hash-of-identity-key in most places rather than
12888 nickname or addr:port, for improved security/flexibility.
12889 - To avoid Sybil attacks, paths still use only verified servers.
12890 But now we have a chance to play around with hybrid approaches.
12891 - Nodes track bandwidth usage to estimate capacity (not used yet).
12892 - ClientOnly option for nodes that never want to become servers.
12893 - Directory caching.
12894 - "AuthoritativeDir 1" option for the official dirservers.
12895 - Now other nodes (clients and servers) will cache the latest
12896 directory they've pulled down.
12897 - They can enable their DirPort to serve it to others.
12898 - Clients will pull down a directory from any node with an open
12899 DirPort, and check the signature/timestamp correctly.
12900 - Authoritative dirservers now fetch directories from other
12901 authdirservers, to stay better synced.
12902 - Running-routers list tells who's down also, along with noting
12903 if they're verified (listed by nickname) or unverified (listed
12905 - Allow dirservers to serve running-router list separately.
12906 This isn't used yet.
12907 - ORs connect-on-demand to other ORs
12908 - If you get an extend cell to an OR you're not connected to,
12909 connect, handshake, and forward the create cell.
12910 - The authoritative dirservers stay connected to everybody,
12911 and everybody stays connected to 0.0.7 servers, but otherwise
12912 clients/servers expire unused connections after 5 minutes.
12913 - When servers get a sigint, they delay 30 seconds (refusing new
12914 connections) then exit. A second sigint causes immediate exit.
12915 - File and name management:
12916 - Look for .torrc if no CONFDIR "torrc" is found.
12917 - If no datadir is defined, then choose, make, and secure ~/.tor
12919 - If torrc not found, exitpolicy reject *:*.
12920 - Expands ~/ in filenames to $HOME/ (but doesn't yet expand ~arma).
12921 - If no nickname is defined, derive default from hostname.
12922 - Rename secret key files, e.g. identity.key -> secret_id_key,
12923 to discourage people from mailing their identity key to tor-ops.
12924 - Refuse to build a circuit before the directory has arrived --
12925 it won't work anyway, since you won't know the right onion keys
12927 - Try other dirservers immediately if the one you try is down. This
12928 should tolerate down dirservers better now.
12929 - Parse tor version numbers so we can do an is-newer-than check
12930 rather than an is-in-the-list check.
12931 - New socks command 'resolve', to let us shim gethostbyname()
12933 - A 'tor_resolve' script to access the socks resolve functionality.
12934 - A new socks-extensions.txt doc file to describe our
12935 interpretation and extensions to the socks protocols.
12936 - Add a ContactInfo option, which gets published in descriptor.
12937 - Publish OR uptime in descriptor (and thus in directory) too.
12938 - Write tor version at the top of each log file
12939 - New docs in the tarball:
12941 - Document that you should proxy your SSL traffic too.
12944 Changes in version 0.0.7.2 - 2004-07-07
12945 o A better fix for the 0.0.0.0 problem, that will hopefully
12946 eliminate the remaining related assertion failures.
12949 Changes in version 0.0.7.1 - 2004-07-04
12950 o When an address resolves to 0.0.0.0, treat it as a failed resolve,
12951 since internally we use 0.0.0.0 to signify "not yet resolved".
12954 Changes in version 0.0.7 - 2004-06-07
12955 o Updated the man page to reflect the new features.
12958 Changes in version 0.0.7rc2 - 2004-06-06
12959 o Changes from 0.0.7rc1:
12960 - Make it build on Win32 again.
12961 o Changes from 0.0.6.2:
12962 - Rotate dnsworkers and cpuworkers on SIGHUP, so they get new config
12966 Changes in version 0.0.7rc1 - 2004-06-02
12968 - On sighup, we were adding another log without removing the first
12969 one. So log messages would get duplicated n times for n sighups.
12970 - Several cases of using a connection after we'd freed it. The
12971 problem was that connections that are pending resolve are in both
12972 the pending_resolve tree, and also the circuit's resolving_streams
12973 list. When you want to remove one, you must remove it from both.
12974 - Fix a double-mark-for-close where an end cell arrived for a
12975 resolving stream, and then the resolve failed.
12976 - Check directory signatures based on name of signer, not on whom
12977 we got the directory from. This will let us cache directories more
12980 - Crank up some of our constants to handle more users.
12983 Changes in version 0.0.7pre1 - 2004-06-02
12984 o Fixes for crashes and other obnoxious bugs:
12985 - Fix an epipe bug: sometimes when directory connections failed
12986 to connect, we would give them a chance to flush before closing
12988 - When we detached from a circuit because of resolvefailed, we
12989 would immediately try the same circuit twice more, and then
12990 give up on the resolve thinking we'd tried three different
12992 - Limit the number of intro circuits we'll attempt to build for a
12993 hidden service per 15-minute period.
12994 - Check recommended-software string *early*, before actually parsing
12995 the directory. Thus we can detect an obsolete version and exit,
12996 even if the new directory format doesn't parse.
12997 o Fixes for security bugs:
12998 - Remember which nodes are dirservers when you startup, and if a
12999 random OR enables his dirport, don't automatically assume he's
13000 a trusted dirserver.
13002 - Directory connections were asking the wrong poll socket to
13003 start writing, and not asking themselves to start writing.
13004 - When we detached from a circuit because we sent a begin but
13005 didn't get a connected, we would use it again the first time;
13006 but after that we would correctly switch to a different one.
13007 - Stop warning when the first onion decrypt attempt fails; they
13008 will sometimes legitimately fail now that we rotate keys.
13009 - Override unaligned-access-ok check when $host_cpu is ia64 or
13010 arm. Apparently they allow it but the kernel whines.
13011 - Dirservers try to reconnect periodically too, in case connections
13013 - Fix some memory leaks in directory servers.
13014 - Allow backslash in Win32 filenames.
13015 - Made Tor build complain-free on FreeBSD, hopefully without
13016 breaking other BSD builds. We'll see.
13018 - Doxygen markup on all functions and global variables.
13019 - Make directory functions update routerlist, not replace it. So
13020 now directory disagreements are not so critical a problem.
13021 - Remove the upper limit on number of descriptors in a dirserver's
13022 directory (not that we were anywhere close).
13023 - Allow multiple logfiles at different severity ranges.
13024 - Allow *BindAddress to specify ":port" rather than setting *Port
13025 separately. Allow multiple instances of each BindAddress config
13026 option, so you can bind to multiple interfaces if you want.
13027 - Allow multiple exit policy lines, which are processed in order.
13028 Now we don't need that huge line with all the commas in it.
13029 - Enable accept/reject policies on SOCKS connections, so you can bind
13030 to 0.0.0.0 but still control who can use your OP.
13033 Changes in version 0.0.6.2 - 2004-05-16
13034 o Our integrity-checking digest was checking only the most recent cell,
13035 not the previous cells like we'd thought.
13036 Thanks to Stefan Mark for finding the flaw!
13039 Changes in version 0.0.6.1 - 2004-05-06
13040 o Fix two bugs in our AES counter-mode implementation (this affected
13041 onion-level stream encryption, but not TLS-level). It turns
13042 out we were doing something much more akin to a 16-character
13043 polyalphabetic cipher. Oops.
13044 Thanks to Stefan Mark for finding the flaw!
13045 o Retire moria3 as a directory server, and add tor26 as a directory
13049 Changes in version 0.0.6 - 2004-05-02
13050 [version bump only]
13053 Changes in version 0.0.6rc4 - 2004-05-01
13054 o Update the built-in dirservers list to use the new directory format
13055 o Fix a rare seg fault: if a node offering a hidden service attempts
13056 to build a circuit to Alice's rendezvous point and fails before it
13057 reaches the last hop, it retries with a different circuit, but
13059 o Handle windows socket errors correctly.
13062 Changes in version 0.0.6rc3 - 2004-04-28
13063 o Don't expire non-general excess circuits (if we had enough
13064 circuits open, we were expiring rendezvous circuits -- even
13065 when they had a stream attached. oops.)
13066 o Fetch randomness from /dev/urandom better (not via fopen/fread)
13067 o Better debugging for tls errors
13068 o Some versions of openssl have an SSL_pending function that erroneously
13069 returns bytes when there is a non-application record pending.
13070 o Set Content-Type on the directory and hidserv descriptor.
13071 o Remove IVs from cipher code, since AES-ctr has none.
13072 o Win32 fixes. Tor now compiles on win32 with no warnings/errors.
13073 o We were using an array of length zero in a few places.
13074 o win32's gethostbyname can't resolve an IP to an IP.
13075 o win32's close can't close a socket.
13078 Changes in version 0.0.6rc2 - 2004-04-26
13079 o Fix a bug where we were closing tls connections intermittently.
13080 It turns out openssl keeps its errors around -- so if an error
13081 happens, and you don't ask about it, and then another openssl
13082 operation happens and succeeds, and you ask if there was an error,
13083 it tells you about the first error. Fun fun.
13084 o Fix a bug that's been lurking since 27 may 03 (!)
13085 When passing back a destroy cell, we would use the wrong circ id.
13086 'Mostly harmless', but still worth fixing.
13087 o Since we don't support truncateds much, don't bother sending them;
13088 just close the circ.
13089 o check for <machine/limits.h> so we build on NetBSD again (I hope).
13090 o don't crash if a conn that sent a begin has suddenly lost its circuit
13091 (this was quite rare).
13094 Changes in version 0.0.6rc1 - 2004-04-25
13095 o We now rotate link (tls context) keys and onion keys.
13096 o CREATE cells now include oaep padding, so you can tell
13097 if you decrypted them correctly.
13098 o Add bandwidthburst to server descriptor.
13099 o Directories now say which dirserver signed them.
13100 o Use a tor_assert macro that logs failed assertions too.
13103 Changes in version 0.0.6pre5 - 2004-04-18
13104 o changes from 0.0.6pre4:
13105 - make tor build on broken freebsd 5.2 installs
13106 - fix a failed assert when you try an intro point, get a nack, and try
13107 a second one and it works.
13108 - when alice uses a port that the hidden service doesn't accept,
13109 it now sends back an end cell (denied by exit policy). otherwise
13110 alice would just have to wait to time out.
13111 - fix another rare bug: when we had tried all the intro
13112 points for a hidden service, we fetched the descriptor
13113 again, but we left our introcirc thinking it had already
13114 sent an intro, so it kept waiting for a response...
13115 - bugfix: when you sleep your hidden-service laptop, as soon
13116 as it wakes up it tries to upload a service descriptor, but
13117 socketpair fails for some reason (localhost not up yet?).
13118 now we simply give up on that upload, and we'll try again later.
13119 i'd still like to find the bug though.
13120 - if an intro circ waiting for an ack dies before getting one, then
13122 - we were reusing stale service descriptors and refetching usable
13126 Changes in version 0.0.6pre4 - 2004-04-14
13127 o changes from 0.0.6pre3:
13128 - when bob fails to connect to the rendezvous point, and his
13129 circ didn't fail because of the rendezvous point itself, then
13130 he retries a couple of times
13131 - we expire introduction and rendezvous circs more thoroughly
13132 (sometimes they were hanging around forever)
13133 - we expire unattached rendezvous streams that have been around
13134 too long (they were sticking around forever).
13135 - fix a measly fencepost error that was crashing everybody with
13139 Changes in version 0.0.6pre3 - 2004-04-14
13140 o changes from 0.0.6pre2:
13141 - make hup work again
13142 - fix some memory leaks for dirservers
13143 - allow more skew in rendezvous descriptor timestamps, to help
13144 handle people like blanu who don't know what time it is
13145 - normal circs are 3 hops, but some rend/intro circs are 4, if
13146 the initiator doesn't get to choose the last hop
13147 - send acks for introductions, so alice can know whether to try
13149 - bob publishes intro points more correctly
13150 o changes from 0.0.5:
13151 - fix an assert trigger that's been plaguing us since the days
13152 of 0.0.2prexx (thanks weasel!)
13153 - retry stream correctly when we fail to connect because of
13154 exit-policy-reject (should try another) or can't-resolve-address
13155 (also should try another, because dns on random internet servers
13157 - when we hup a dirserver and we've *removed* a server from the
13158 approved-routers list, now we remove that server from the
13159 in-memory directories too
13162 Changes in version 0.0.6pre2 - 2004-04-08
13163 o We fixed our base32 implementation. Now it works on all architectures.
13166 Changes in version 0.0.6pre1 - 2004-04-08
13168 - Hidden services and rendezvous points are implemented. Go to
13169 http://6sxoyfb3h2nvok2d.onion/ for an index of currently available
13170 hidden services. (This only works via a socks4a proxy such as
13171 Privoxy, and currently it's quite slow.)
13174 Changes in version 0.0.5 - 2004-03-30
13175 [version bump only]
13178 Changes in version 0.0.5rc3 - 2004-03-29
13179 o Install torrc as torrc.sample -- we no longer clobber your
13181 o Re-enable recommendedversion checking (we broke it in rc2, oops)
13182 o Add in a 'notice' log level for things the operator should hear
13183 but that aren't warnings
13186 Changes in version 0.0.5rc2 - 2004-03-29
13187 o Hold socks connection open until reply is flushed (if possible)
13188 o Make exit nodes resolve IPs to IPs immediately, rather than asking
13189 the dns farm to do it.
13190 o Fix c99 aliasing warnings in rephist.c
13191 o Don't include server descriptors that are older than 24 hours in the
13193 o Give socks 'reject' replies their whole 15s to attempt to flush,
13194 rather than seeing the 60s timeout and assuming the flush had failed.
13195 o Clean automake droppings from the cvs repository
13198 Changes in version 0.0.5rc1 - 2004-03-28
13199 o Fix mangled-state bug in directory fetching (was causing sigpipes).
13200 o Only build circuits after we've fetched the directory: clients were
13201 using only the directory servers before they'd fetched a directory.
13202 This also means longer startup time; so it goes.
13203 o Fix an assert trigger where an OP would fail to handshake, and we'd
13204 expect it to have a nickname.
13205 o Work around a tsocks bug: do a socks reject when AP connection dies
13206 early, else tsocks goes into an infinite loop.
13209 Changes in version 0.0.4 - 2004-03-26
13210 o When connecting to a dirserver or OR and the network is down,
13214 Changes in version 0.0.3 - 2004-03-26
13215 o Warn and fail if server chose a nickname with illegal characters
13216 o Port to Solaris and Sparc:
13217 - include missing header fcntl.h
13218 - have autoconf find -lsocket -lnsl automatically
13219 - deal with hardware word alignment
13220 - make uname() work (solaris has a different return convention)
13221 - switch from using signal() to sigaction()
13222 o Preliminary work on reputation system:
13223 - Keep statistics on success/fail of connect attempts; they're published
13224 by kill -USR1 currently.
13225 - Add a RunTesting option to try to learn link state by creating test
13226 circuits, even when SocksPort is off.
13227 - Remove unused open circuits when there are too many.
13230 Changes in version 0.0.2 - 2004-03-19
13231 - Include strlcpy and strlcat for safer string ops
13232 - define INADDR_NONE so we compile (but still not run) on solaris
13235 Changes in version 0.0.2pre27 - 2004-03-14
13237 - Allow internal tor networks (we were rejecting internal IPs,
13238 now we allow them if they're set explicitly).
13239 - And fix a few endian issues.
13242 Changes in version 0.0.2pre26 - 2004-03-14
13244 - If a stream times out after 15s without a connected cell, don't
13245 try that circuit again: try a new one.
13246 - Retry streams at most 4 times. Then give up.
13247 - When a dirserver gets a descriptor from an unknown router, it
13248 logs its fingerprint (so the dirserver operator can choose to
13249 accept it even without mail from the server operator).
13250 - Inform unapproved servers when we reject their descriptors.
13251 - Make tor build on Windows again. It works as a client, who knows
13253 - Clearer instructions in the torrc for how to set up a server.
13254 - Be more efficient about reading fd's when our global token bucket
13255 (used for rate limiting) becomes empty.
13257 - Stop asserting that computers always go forward in time. It's
13259 - When we sent a cell (e.g. destroy) and then marked an OR connection
13260 expired, we might close it before finishing a flush if the other
13261 side isn't reading right then.
13262 - Don't allow dirservers to start if they haven't defined
13263 RecommendedVersions
13264 - We were caching transient dns failures. Oops.
13265 - Prevent servers from publishing an internal IP as their address.
13266 - Address a strcat vulnerability in circuit.c
13269 Changes in version 0.0.2pre25 - 2004-03-04
13271 - Put the OR's IP in its router descriptor, not its fqdn. That way
13272 we'll stop being stalled by gethostbyname for nodes with flaky dns,
13275 - If the user typed in an address that didn't resolve, the server
13279 Changes in version 0.0.2pre24 - 2004-03-03
13281 - Fix an assertion failure in dns.c, where we were trying to dequeue
13282 a pending dns resolve even if it wasn't pending
13283 - Fix a spurious socks5 warning about still trying to write after the
13284 connection is finished.
13285 - Hold certain marked_for_close connections open until they're finished
13286 flushing, rather than losing bytes by closing them too early.
13287 - Correctly report the reason for ending a stream
13288 - Remove some duplicate calls to connection_mark_for_close
13289 - Put switch_id and start_daemon earlier in the boot sequence, so it
13290 will actually try to chdir() to options.DataDirectory
13291 - Make 'make test' exit(1) if a test fails; fix some unit tests
13292 - Make tor fail when you use a config option it doesn't know about,
13293 rather than warn and continue.
13294 - Make --version work
13295 - Bugfixes on the rpm spec file and tor.sh, so it's more up to date
13298 Changes in version 0.0.2pre23 - 2004-02-29
13300 - Print a statement when the first circ is finished, so the user
13301 knows it's working.
13302 - If a relay cell is unrecognized at the end of the circuit,
13303 send back a destroy. (So attacks to mutate cells are more
13305 - New config option 'excludenodes' to avoid certain nodes for circuits.
13306 - When it daemonizes, it chdir's to the DataDirectory rather than "/",
13307 so you can collect coredumps there.
13309 - Fix a bug in tls flushing where sometimes data got wedged and
13310 didn't flush until more data got sent. Hopefully this bug was
13311 a big factor in the random delays we were seeing.
13312 - Make 'connected' cells include the resolved IP, so the client
13313 dns cache actually gets populated.
13314 - Disallow changing from ORPort=0 to ORPort>0 on hup.
13315 - When we time-out on a stream and detach from the circuit, send an
13316 end cell down it first.
13317 - Only warn about an unknown router (in exitnodes, entrynodes,
13318 excludenodes) after we've fetched a directory.
13321 Changes in version 0.0.2pre22 - 2004-02-26
13323 - Servers publish less revealing uname information in descriptors.
13324 - More memory tracking and assertions, to crash more usefully when
13326 - If the default torrc isn't there, just use some default defaults.
13327 Plus provide an internal dirservers file if they don't have one.
13328 - When the user tries to use Tor as an http proxy, give them an http
13329 501 failure explaining that we're a socks proxy.
13330 - Dump a new router.desc on hup, to help confused people who change
13331 their exit policies and then wonder why router.desc doesn't reflect
13333 - Clean up the generic tor.sh init script that we ship with.
13335 - If the exit stream is pending on the resolve, and a destroy arrives,
13336 then the stream wasn't getting removed from the pending list. I
13337 think this was the one causing recent server crashes.
13338 - Use a more robust poll on OSX 10.3, since their poll is flaky.
13339 - When it couldn't resolve any dirservers, it was useless from then on.
13340 Now it reloads the RouterFile (or default dirservers) if it has no
13342 - Move the 'tor' binary back to /usr/local/bin/ -- it turns out
13343 many users don't even *have* a /usr/local/sbin/.
13346 Changes in version 0.0.2pre21 - 2004-02-18
13348 - There's a ChangeLog file that actually reflects the changelog.
13349 - There's a 'torify' wrapper script, with an accompanying
13350 tor-tsocks.conf, that simplifies the process of using tsocks for
13351 tor. It even has a man page.
13352 - The tor binary gets installed to sbin rather than bin now.
13353 - Retry streams where the connected cell hasn't arrived in 15 seconds
13354 - Clean up exit policy handling -- get the default out of the torrc,
13355 so we can update it without forcing each server operator to fix
13357 - Allow imaps and pop3s in default exit policy
13359 - Prevent picking middleman nodes as the last node in the circuit
13362 Changes in version 0.0.2pre20 - 2004-01-30
13364 - We now have a deb package, and it's in debian unstable. Go to
13365 it, apt-getters. :)
13366 - I've split the TotalBandwidth option into BandwidthRate (how many
13367 bytes per second you want to allow, long-term) and
13368 BandwidthBurst (how many bytes you will allow at once before the cap
13369 kicks in). This better token bucket approach lets you, say, set
13370 BandwidthRate to 10KB/s and BandwidthBurst to 10MB, allowing good
13371 performance while not exceeding your monthly bandwidth quota.
13372 - Push out a tls record's worth of data once you've got it, rather
13373 than waiting until you've read everything waiting to be read. This
13374 may improve performance by pipelining better. We'll see.
13375 - Add an AP_CONN_STATE_CONNECTING state, to allow streams to detach
13376 from failed circuits (if they haven't been connected yet) and attach
13378 - Expire old streams that haven't managed to connect. Some day we'll
13379 have them reattach to new circuits instead.
13382 - Fix several memory leaks that were causing servers to become bloated
13384 - Fix a few very rare assert triggers. A few more remain.
13385 - Setuid to User _before_ complaining about running as root.
13388 Changes in version 0.0.2pre19 - 2004-01-07
13390 - Fix deadlock condition in dns farm. We were telling a child to die by
13391 closing the parent's file descriptor to him. But newer children were
13392 inheriting the open file descriptor from the parent, and since they
13393 weren't closing it, the socket never closed, so the child never read
13394 eof, so he never knew to exit. Similarly, dns workers were holding
13395 open other sockets, leading to all sorts of chaos.
13396 - New cleaner daemon() code for forking and backgrounding.
13397 - If you log to a file, it now prints an entry at the top of the
13398 logfile so you know it's working.
13399 - The onionskin challenge length was 30 bytes longer than necessary.
13400 - Started to patch up the spec so it's not quite so out of date.
13403 Changes in version 0.0.2pre18 - 2004-01-02
13405 - Fix endian issues with the 'integrity' field in the relay header.
13406 - Fix a potential bug where connections in state
13407 AP_CONN_STATE_CIRCUIT_WAIT might unexpectedly ask to write.
13410 Changes in version 0.0.2pre17 - 2003-12-30
13412 - Made --debuglogfile (or any second log file, actually) work.
13413 - Resolved an edge case in get_unique_circ_id_by_conn where a smart
13414 adversary could force us into an infinite loop.
13417 - Each onionskin handshake now includes a hash of the computed key,
13418 to prove the server's identity and help perfect forward secrecy.
13419 - Changed cell size from 256 to 512 bytes (working toward compatibility
13421 - Changed cell length to 2 bytes, and moved it to the relay header.
13422 - Implemented end-to-end integrity checking for the payloads of
13424 - Separated streamid from 'recognized' (otherwise circuits will get
13425 messed up when we try to have streams exit from the middle). We
13426 use the integrity-checking to confirm that a cell is addressed to
13428 - Randomize the initial circid and streamid values, so an adversary who
13429 breaks into a node can't learn how many circuits or streams have
13433 Changes in version 0.0.2pre16 - 2003-12-14
13435 - Fixed a bug that made HUP trigger an assert
13436 - Fixed a bug where a circuit that immediately failed wasn't being
13437 counted as a failed circuit in counting retries.
13440 - Now we close the circuit when we get a truncated cell: otherwise we're
13441 open to an anonymity attack where a bad node in the path truncates
13442 the circuit and then we open streams at him.
13443 - Add port ranges to exit policies
13444 - Add a conservative default exit policy
13445 - Warn if you're running tor as root
13446 - on HUP, retry OR connections and close/rebind listeners
13447 - options.EntryNodes: try these nodes first when picking the first node
13448 - options.ExitNodes: if your best choices happen to include any of
13449 your preferred exit nodes, you choose among just those preferred
13451 - options.ExcludedNodes: nodes that are never picked in path building
13454 Changes in version 0.0.2pre15 - 2003-12-03
13455 o Robustness and bugfixes:
13456 - Sometimes clients would cache incorrect DNS resolves, which would
13457 really screw things up.
13458 - An OP that goes offline would slowly leak all its sockets and stop
13460 - A wide variety of bugfixes in exit node selection, exit policy
13461 handling, and processing pending streams when a new circuit is
13463 - Pick nodes for a path only from those the directory says are up
13464 - Choose randomly from all running dirservers, not always the first one
13465 - Increase allowed http header size for directory fetch.
13466 - Stop writing to stderr (if we're daemonized it will be closed).
13467 - Enable -g always, so cores will be more useful to me.
13468 - Switch "-lcrypto -lssl" to "-lssl -lcrypto" for broken distributions.
13471 - Wrote a man page. It lists commonly used options.
13474 - Change default loglevel to warn.
13475 - Make PidFile default to null rather than littering in your CWD.
13476 - OnionRouter config option is now obsolete. Instead it just checks
13478 - Moved to a single unified torrc file for both clients and servers.
13481 Changes in version 0.0.2pre14 - 2003-11-29
13482 o Robustness and bugfixes:
13483 - Force the admin to make the DataDirectory himself
13484 - to get ownership/permissions right
13485 - so clients no longer make a DataDirectory and then never use it
13486 - fix bug where a client who was offline for 45 minutes would never
13487 pull down a directory again
13488 - fix (or at least hide really well) the dns assert bug that was
13489 causing server crashes
13490 - warnings and improved robustness wrt clockskew for certs
13491 - use the native daemon(3) to daemonize, when available
13492 - exit if bind() fails
13493 - exit if neither socksport nor orport is defined
13494 - include our own tor_timegm (Win32 doesn't have its own)
13495 - bugfix for win32 with lots of connections
13496 - fix minor bias in PRNG
13497 - make dirserver more robust to corrupt cached directory
13500 - Wrote the design document (woo)
13502 o Circuit building and exit policies:
13503 - Circuits no longer try to use nodes that the directory has told them
13505 - Exit policies now support bitmasks (18.0.0.0/255.0.0.0) and
13506 bitcounts (18.0.0.0/8).
13507 - Make AP connections standby for a circuit if no suitable circuit
13508 exists, rather than failing
13509 - Circuits choose exit node based on addr/port, exit policies, and
13510 which AP connections are standing by
13511 - Bump min pathlen from 2 to 3
13512 - Relay end cells have a payload to describe why the stream ended.
13513 - If the stream failed because of exit policy, try again with a new
13515 - Clients have a dns cache to remember resolved addresses.
13516 - Notice more quickly when we have no working circuits
13519 - APPort is now called SocksPort
13520 - SocksBindAddress, ORBindAddress, DirBindAddress let you configure
13522 - RecommendedVersions is now a config variable rather than
13523 hardcoded (for dirservers)
13524 - Reloads config on HUP
13525 - Usage info on -h or --help
13526 - If you set User and Group config vars, it'll setu/gid to them.
13529 Changes in version 0.0.2pre13 - 2003-10-19
13530 o General stability:
13531 - SSL_write no longer fails when it returns WANTWRITE and the number
13532 of bytes in the buf has changed by the next SSL_write call.
13533 - Fix segfault fetching directory when network is down
13534 - Fix a variety of minor memory leaks
13535 - Dirservers reload the fingerprints file on HUP, so I don't have
13536 to take down the network when I approve a new router
13537 - Default server config file has explicit Address line to specify fqdn
13540 - Buffers grow and shrink as needed (Cut process size from 20M to 2M)
13541 - Make listener connections not ever alloc bufs
13543 o Autoconf improvements:
13544 - don't clobber an external CFLAGS in ./configure
13545 - Make install now works
13546 - create var/lib/tor on make install
13547 - autocreate a tor.sh initscript to help distribs
13548 - autocreate the torrc and sample-server-torrc with correct paths
13550 o Log files and Daemonizing now work:
13551 - If --DebugLogFile is specified, log to it at -l debug
13552 - If --LogFile is specified, use it instead of commandline
13553 - If --RunAsDaemon is set, tor forks and backgrounds on startup