1 Changes in version 0.2.3.21-rc - 2012-09-05
2 Tor 0.2.3.21-rc is the fourth release candidate for the Tor 0.2.3.x
3 series. It fixes a trio of potential security bugs, fixes a bug where
4 we were leaving some of the fast relays out of the microdescriptor
5 consensus, resumes interpreting "ORPort 0" and "DirPort 0" correctly,
6 and cleans up other smaller issues.
8 o Major bugfixes (security):
9 - Tear down the circuit if we get an unexpected SENDME cell. Clients
10 could use this trick to make their circuits receive cells faster
11 than our flow control would have allowed, or to gum up the network,
12 or possibly to do targeted memory denial-of-service attacks on
13 entry nodes. Fixes bug 6252. Bugfix on the 54th commit on Tor --
14 from July 2002, before the release of Tor 0.0.0. We had committed
15 this patch previously, but we had to revert it because of bug 6271.
16 Now that 6271 is fixed, this patch appears to work.
17 - Reject any attempt to extend to an internal address. Without
18 this fix, a router could be used to probe addresses on an internal
19 network to see whether they were accepting connections. Fixes bug
20 6710; bugfix on 0.0.8pre1.
21 - Do not crash when comparing an address with port value 0 to an
22 address policy. This bug could have been used to cause a remote
23 assertion failure by or against directory authorities, or to
24 allow some applications to crash clients. Fixes bug 6690; bugfix
28 - Remove the upper bound on microdescriptor length. We were hitting
29 the limit for routers with complex exit policies or family
30 declarations, causing clients to not use them. Fixes the first
31 piece of bug 6404; fix on 0.2.2.6-alpha.
32 - Detect "ORPort 0" as meaning, uniformly, that we're not running
33 as a relay. Previously, some of our code would treat the presence
34 of any ORPort line as meaning that we should act like a relay,
35 even though our new listener code would correctly not open any
36 ORPorts for ORPort 0. Similar bugs in other Port options are also
37 fixed. Fixes the first half of bug 6507; bugfix on 0.2.3.3-alpha.
40 - Avoid a pair of double-free and use-after-mark bugs that can
41 occur with certain timings in canceled and re-received DNS
42 requests. Fixes bug 6472; bugfix on 0.0.7rc1.
43 - Fix build and 64-bit compile warnings from --enable-openbsd-malloc.
44 Fixes bug 6379. Bugfix on 0.2.0.20-rc.
45 - Authorities no longer include any router in their microdescriptor
46 consensuses for which they couldn't generate or agree on a
47 microdescriptor. Fixes the second piece of bug 6404; fix on
49 - Detect and reject attempts to specify both "FooPort" and
50 "FooPort 0" in the same configuration domain. (It's still okay
51 to have a FooPort in your configuration file, and use "FooPort 0"
52 on the command line to disable it.) Fixes the second half of bug
53 6507; bugfix on 0.2.3.3-alpha.
54 - Make wildcarded addresses (that is, ones beginning with "*.") work
55 when provided via the controller's MapAddress command. Previously,
56 they were accepted, but we never actually noticed that they were
57 wildcards. Fixes bug 6244; bugfix on 0.2.3.9-alpha.
58 - Add a (probably redundant) memory clear between iterations of
59 the router status voting loop, to prevent future coding errors
60 where data might leak between iterations of the loop. Resolves
63 o Minor bugfixes (log messages):
64 - Downgrade "set buildtimeout to low value" messages to "info"
65 severity; they were never an actual problem, there was never
66 anything reasonable to do about them, and they tended to spam logs
67 from time to time. Fixes bug 6251; bugfix on 0.2.2.2-alpha.
68 - Downgrade path-bias warning messages to "info". We'll try to get
69 them working better in 0.2.4. Add internal circuit construction
70 state to protect against the noisy warn message "Unexpectedly high
71 circuit_successes". Also add some additional rate-limited notice
72 messages to help determine the root cause of the warn. Fixes bug
73 6475. Bugfix against 0.2.3.17-beta.
74 - Move log message when unable to find a microdesc in a routerstatus
75 entry to parse time. Previously we'd spam this warning every time
76 we tried to figure out which microdescriptors to download. Fixes
77 the third piece of bug 6404; fix on 0.2.3.18-rc.
80 - Consider new, removed or changed IPv6 OR ports a non-cosmetic
81 change when the authority is deciding whether to accept a newly
82 uploaded descriptor. Implements ticket 6423.
83 - Add missing documentation for consensus and microdesc files.
87 Changes in version 0.2.2.38 - 2012-08-12
88 Tor 0.2.2.38 fixes a remotely triggerable crash bug, and fixes a timing
89 attack that could in theory leak path information.
92 - Avoid an uninitialized memory read when reading a vote or consensus
93 document that has an unrecognized flavor name. This read could
94 lead to a remote crash bug. Fixes bug 6530; bugfix on 0.2.2.6-alpha.
95 - Try to leak less information about what relays a client is
96 choosing to a side-channel attacker. Previously, a Tor client would
97 stop iterating through the list of available relays as soon as it
98 had chosen one, thus finishing a little earlier when it picked
99 a router earlier in the list. If an attacker can recover this
100 timing information (nontrivial but not proven to be impossible),
101 they could learn some coarse-grained information about which relays
102 a client was picking (middle nodes in particular are likelier to
103 be affected than exits). The timing attack might be mitigated by
104 other factors (see bug 6537 for some discussion), but it's best
105 not to take chances. Fixes bug 6537; bugfix on 0.0.8rc1.
108 Changes in version 0.2.3.20-rc - 2012-08-05
109 Tor 0.2.3.20-rc is the third release candidate for the Tor 0.2.3.x
110 series. It fixes a pair of code security bugs and a potential anonymity
111 issue, updates our RPM spec files, and cleans up other smaller issues.
114 - Avoid read-from-freed-memory and double-free bugs that could occur
115 when a DNS request fails while launching it. Fixes bug 6480;
116 bugfix on 0.2.0.1-alpha.
117 - Avoid an uninitialized memory read when reading a vote or consensus
118 document that has an unrecognized flavor name. This read could
119 lead to a remote crash bug. Fixes bug 6530; bugfix on 0.2.2.6-alpha.
120 - Try to leak less information about what relays a client is
121 choosing to a side-channel attacker. Previously, a Tor client would
122 stop iterating through the list of available relays as soon as it
123 had chosen one, thus finishing a little earlier when it picked
124 a router earlier in the list. If an attacker can recover this
125 timing information (nontrivial but not proven to be impossible),
126 they could learn some coarse-grained information about which relays
127 a client was picking (middle nodes in particular are likelier to
128 be affected than exits). The timing attack might be mitigated by
129 other factors (see bug 6537 for some discussion), but it's best
130 not to take chances. Fixes bug 6537; bugfix on 0.0.8rc1.
133 - Try to make the warning when giving an obsolete SOCKSListenAddress
134 a little more useful.
135 - Terminate active server managed proxies if Tor stops being a
136 relay. Addresses parts of bug 6274; bugfix on 0.2.3.6-alpha.
137 - Provide a better error message about possible OSX Asciidoc failure
138 reasons. Fixes bug 6436.
139 - Warn when Tor is configured to use accounting in a way that can
140 link a hidden service to some other hidden service or public
141 address. Resolves ticket 6490.
144 - Check return value of fputs() when writing authority certificate
145 file. Fixes Coverity issue 709056; bugfix on 0.2.0.1-alpha.
146 - Ignore ServerTransportPlugin lines when Tor is not configured as
147 a relay. Fixes bug 6274; bugfix on 0.2.3.6-alpha.
148 - When disabling guards for having too high a proportion of failed
149 circuits, make sure to look at each guard. Fixes bug 6397; bugfix
153 - Update our default RPM spec files to work with mock and rpmbuild
154 on RHEL/Fedora. They have an updated set of dependencies and
155 conflicts, a fix for an ancient typo when creating the "_tor"
156 user, and better instructions. Thanks to Ondrej Mikle for the
157 patch series. Fixes bug 6043.
160 - Make it possible to set the TestingTorNetwork configuration
161 option using AlternateDirAuthority and AlternateBridgeAuthority
162 as an alternative to setting DirServer. Addresses ticket 6377.
165 - Clarify the documentation for the Alternate*Authority options.
167 - Fix some typos in the manpages. Patch from A. Costa. Fixes bug 6500.
169 o Code simplification and refactoring:
170 - Do not use SMARTLIST_FOREACH for any loop whose body exceeds
171 10 lines. Also, don't nest them. Doing so in the past has
172 led to hard-to-debug code. The new style is to use the
173 SMARTLIST_FOREACH_{BEGIN,END} pair. Addresses issue 6400.
176 Changes in version 0.2.3.19-rc - 2012-07-06
177 Tor 0.2.3.19-rc is the second release candidate for the Tor 0.2.3.x
178 series. It fixes the compile on Windows, reverts to a GeoIP database
179 that isn't as broken, and fixes a flow control bug that has been around
180 since the beginning of Tor.
183 - Fix a bug handling SENDME cells on nonexistent streams that could
184 result in bizarre window values. Report and patch contributed
185 pseudonymously. Fixes part of bug 6271. This bug was introduced
186 before the first Tor release, in svn commit r152.
187 - Revert to the May 1 2012 Maxmind GeoLite Country database. In the
188 June 2012 database, Maxmind marked many Tor relays as country "A1",
189 which will cause risky behavior for clients that set EntryNodes
190 or ExitNodes. Addresses bug 6334; bugfix on 0.2.3.17-beta.
191 - Instead of ENOBUFS on Windows, say WSAENOBUFS. Fixes compilation
192 on Windows. Fixes bug 6296; bugfix on 0.2.3.18-rc.
195 - Fix wrong TCP port range in parse_port_range(). Fixes bug 6218;
196 bugfix on 0.2.1.10-alpha.
199 Changes in version 0.2.3.18-rc - 2012-06-28
200 Tor 0.2.3.18-rc is the first release candidate for the Tor 0.2.3.x
201 series. It fixes a few smaller bugs, but generally appears stable.
202 Please test it and let us know whether it is!
205 - Allow wildcarded mapaddress targets to be specified on the
206 controlport. Partially fixes bug 6244; bugfix on 0.2.3.9-alpha.
207 - Make our linker option detection code more robust against linkers
208 such as on FreeBSD 8, where a bad combination of options completes
209 successfully but makes an unrunnable binary. Fixes bug 6173;
210 bugfix on 0.2.3.17-beta.
212 o Minor bugfixes (on 0.2.2.x and earlier):
213 - Avoid a false positive in the util/threads unit test by increasing
214 the maximum timeout time. Fixes bug 6227; bugfix on 0.2.0.4-alpha.
215 - Replace "Sending publish request" log messages with "Launching
216 upload", so that they no longer confusingly imply that we're
217 sending something to a directory we might not even be connected
218 to yet. Fixes bug 3311; bugfix on 0.2.0.10-alpha.
219 - Make sure to set *socket_error in all error cases in
220 connection_connect(), so it can't produce a warning about
221 errno being zero from errno_to_orconn_end_reason(). Bugfix on
222 0.2.1.1-alpha; resolves ticket 6028.
223 - Downgrade "Got a certificate, but we already have it" log messages
224 from warning to info, except when we're a dirauth. Fixes bug 5238;
225 bugfix on 0.2.1.7-alpha.
226 - When checking for requested signatures on the latest consensus
227 before serving it to a client, make sure to check the right
228 consensus flavor. Bugfix on 0.2.2.6-alpha.
229 - Downgrade "eventdns rejected address" message to LOG_PROTOCOL_WARN.
230 Fixes bug 5932; bugfix on 0.2.2.7-alpha.
232 o Minor bugfixes (on 0.2.3.x):
233 - Make format_helper_exit_status() avoid unnecessary space padding
234 and stop confusing log_from_pipe(). Fixes ticket 5557; bugfix
236 - Downgrade a message about cleaning the microdescriptor cache to
237 "info" from "notice". Fixes bug 6238; bugfix on 0.2.3.1-alpha.
238 - Log a BUG message at severity INFO if we have a networkstatus with
239 a missing entry for some microdescriptor. Continues on a patch
241 - Improve the log message when a managed proxy fails to launch. Fixes
242 bug 5099; bugfix on 0.2.3.6-alpha.
243 - Don't do DNS lookups when parsing corrupted managed proxy protocol
244 messages. Fixes bug 6226; bugfix on 0.2.3.6-alpha.
245 - When formatting wildcarded address mappings for the controller,
246 be sure to include "*." as appropriate. Partially fixes bug 6244;
247 bugfix on 0.2.3.9-alpha.
248 - Avoid a warning caused by using strcspn() from glibc with clang 3.0.
249 Bugfix on 0.2.3.13-alpha.
250 - Stop logging messages about running with circuit timeout learning
251 enabled at severity LD_BUG. Fixes bug 6169; bugfix on 0.2.3.17-beta.
252 - Disable a spurious warning about reading on a marked and flushing
253 connection. We shouldn't be doing that, but apparently we
254 sometimes do. Fixes bug 6203; bugfix on 0.2.3.17-beta.
255 - Fix a bug that stopped AllowDotExit from working on addresses
256 that had an entry in the DNS cache. Fixes bug 6211; bugfix on
259 o Code simplification, refactoring, unit tests:
260 - Move tor_gettimeofday_cached() into compat_libevent.c, and use
261 Libevent's notion of cached time when possible.
262 - Remove duplicate code for invoking getrlimit() from control.c.
263 - Add a unit test for the environment_variable_names_equal function.
266 - Document the --defaults-torrc option, and the new (in 0.2.3)
267 semantics for overriding, extending, and clearing lists of
268 options. Closes bug 4748.
271 Changes in version 0.2.3.17-beta - 2012-06-15
272 Tor 0.2.3.17-beta enables compiler and linker hardening by default,
273 gets our TLS handshake back on track for being able to blend in with
274 Firefox, fixes a big bug in 0.2.3.16-alpha that broke Tor's interaction
275 with Vidalia, and otherwise continues to get us closer to a release
279 - Enable gcc and ld hardening by default. Resolves ticket 5210.
280 - Update TLS cipher list to match Firefox 8 and later. Resolves
282 - Implement the client side of proposal 198: remove support for
283 clients falsely claiming to support standard ciphersuites that
284 they can actually provide. As of modern OpenSSL versions, it's not
285 necessary to fake any standard ciphersuite, and doing so prevents
286 us from using better ciphersuites in the future, since servers
287 can't know whether an advertised ciphersuite is really supported or
288 not. Some hosts -- notably, ones with very old versions of OpenSSL
289 or where OpenSSL has been built with ECC disabled -- will stand
290 out because of this change; TBB users should not be affected.
293 - Change the default value for DynamicDHGroups (introduced in
294 0.2.3.9-alpha) to 0. This feature can make Tor relays less
295 identifiable by their use of the mod_ssl DH group, but at
296 the cost of some usability (#4721) and bridge tracing (#6087)
297 regressions. Resolves ticket 5598.
298 - Send a CRLF at the end of each STATUS_* control protocol event. This
299 bug tickled a bug in Vidalia which would make it freeze. Fixes
300 bug 6094; bugfix on 0.2.3.16-alpha.
303 - Disable writing on marked-for-close connections when they are
304 blocked on bandwidth, to prevent busy-looping in Libevent. Fixes
305 bug 5263; bugfix on 0.0.2pre13, where we first added a special
306 case for flushing marked connections.
307 - Detect SSL handshake even when the initial attempt to write the
308 server hello fails. Fixes bug 4592; bugfix on 0.2.0.13-alpha.
309 - Change the AllowDotExit rules so they should actually work.
310 We now enforce AllowDotExit only immediately after receiving an
311 address via SOCKS or DNSPort: other sources are free to provide
312 .exit addresses after the resolution occurs. Fixes bug 3940;
313 bugfix on 0.2.2.1-alpha.
314 - Fix a (harmless) integer overflow in cell statistics reported by
315 some fast relays. Fixes bug 5849; bugfix on 0.2.2.1-alpha.
316 - Make sure circuitbuild.c checks LearnCircuitBuildTimeout in all the
317 right places and never depends on the consensus parameters or
318 computes adaptive timeouts when it is disabled. Fixes bug 5049;
319 bugfix on 0.2.2.14-alpha.
320 - When building Tor on Windows with -DUNICODE (not default), ensure
321 that error messages, filenames, and DNS server names are always
322 NUL-terminated when we convert them to a single-byte encoding.
323 Fixes bug 5909; bugfix on 0.2.2.16-alpha.
324 - Make Tor build correctly again with -DUNICODE -D_UNICODE defined.
325 Fixes bug 6097; bugfix on 0.2.2.16-alpha.
326 - Fix an edge case where TestingTorNetwork is set but the authorities
327 and relays all have an uptime of zero, where the private Tor network
328 could briefly lack support for hidden services. Fixes bug 3886;
329 bugfix on 0.2.2.18-alpha.
330 - Correct the manpage's descriptions for the default values of
331 DirReqStatistics and ExtraInfoStatistics. Fixes bug 2865; bugfix
333 - Fix the documentation for the --hush and --quiet command line
334 options, which changed their behavior back in 0.2.3.3-alpha.
335 - Fix compilation warning with clang 3.1. Fixes bug 6141; bugfix on
339 - Rate-limit the "Weighted bandwidth is 0.000000" message, and add
340 more information to it, so that we can track it down in case it
341 returns again. Mitigates bug 5235.
342 - Check CircuitBuildTimeout and LearnCircuitBuildTimeout in
343 options_validate(); warn if LearnCircuitBuildTimeout is disabled and
344 CircuitBuildTimeout is set unreasonably low. Resolves ticket 5452.
345 - Warn the user when HTTPProxy, but no other proxy type, is
346 configured. This can cause surprising behavior: it doesn't send
347 all of Tor's traffic over the HTTPProxy -- it sends unencrypted
348 directory traffic only. Resolves ticket 4663.
349 - Issue a notice if a guard completes less than 40% of your circuits.
350 Threshold is configurable by torrc option PathBiasNoticeRate and
351 consensus parameter pb_noticepct. There is additional, off-by-
352 default code to disable guards which fail too many circuits.
353 Addresses ticket 5458.
354 - Update to the June 6 2012 Maxmind GeoLite Country database.
356 o Code simplifications and refactoring:
357 - Remove validate_pluggable_transports_config(): its warning
358 message is now handled by connection_or_connect().
361 Changes in version 0.2.2.37 - 2012-06-06
362 Tor 0.2.2.37 introduces a workaround for a critical renegotiation
363 bug in OpenSSL 1.0.1 (where 20% of the Tor network can't talk to itself
367 - Work around a bug in OpenSSL that broke renegotiation with TLS
368 1.1 and TLS 1.2. Without this workaround, all attempts to speak
369 the v2 Tor connection protocol when both sides were using OpenSSL
370 1.0.1 would fail. Resolves ticket 6033.
371 - When waiting for a client to renegotiate, don't allow it to add
372 any bytes to the input buffer. This fixes a potential DoS issue.
373 Fixes bugs 5934 and 6007; bugfix on 0.2.0.20-rc.
374 - Fix an edge case where if we fetch or publish a hidden service
375 descriptor, we might build a 4-hop circuit and then use that circuit
376 for exiting afterwards -- even if the new last hop doesn't obey our
377 ExitNodes config option. Fixes bug 5283; bugfix on 0.2.0.10-alpha.
380 - Fix a build warning with Clang 3.1 related to our use of vasprintf.
381 Fixes bug 5969. Bugfix on 0.2.2.11-alpha.
384 - Tell GCC and Clang to check for any errors in format strings passed
385 to the tor_v*(print|scan)f functions.
388 Changes in version 0.2.3.16-alpha - 2012-06-05
389 Tor 0.2.3.16-alpha introduces a workaround for a critical renegotiation
390 bug in OpenSSL 1.0.1 (where 20% of the Tor network can't talk to itself
391 currently). It also fixes a variety of smaller bugs and other cleanups
392 that get us closer to a release candidate.
394 o Major bugfixes (general):
395 - Work around a bug in OpenSSL that broke renegotiation with TLS
396 1.1 and TLS 1.2. Without this workaround, all attempts to speak
397 the v2 Tor connection protocol when both sides were using OpenSSL
398 1.0.1 would fail. Resolves ticket 6033.
399 - When waiting for a client to renegotiate, don't allow it to add
400 any bytes to the input buffer. This fixes a potential DoS issue.
401 Fixes bugs 5934 and 6007; bugfix on 0.2.0.20-rc.
402 - Pass correct OR address to managed proxies (like obfsproxy),
403 even when ORListenAddress is used. Fixes bug 4865; bugfix on
405 - The advertised platform of a router now includes only its operating
406 system's name (e.g., "Linux", "Darwin", "Windows 7"), and not its
407 service pack level (for Windows) or its CPU architecture (for Unix).
408 We also no longer include the "git-XYZ" tag in the version. Resolves
411 o Major bugfixes (clients):
412 - If we are unable to find any exit that supports our predicted ports,
413 stop calling them predicted, so that we don't loop and build
414 hopeless circuits indefinitely. Fixes bug 3296; bugfix on 0.0.9pre6,
415 which introduced predicted ports.
416 - Fix an edge case where if we fetch or publish a hidden service
417 descriptor, we might build a 4-hop circuit and then use that circuit
418 for exiting afterwards -- even if the new last hop doesn't obey our
419 ExitNodes config option. Fixes bug 5283; bugfix on 0.2.0.10-alpha.
420 - Check at each new consensus whether our entry guards were picked
421 long enough ago that we should rotate them. Previously, we only
422 did this check at startup, which could lead to us holding a guard
423 indefinitely. Fixes bug 5380; bugfix on 0.2.1.14-rc.
424 - When fetching a bridge descriptor from a bridge authority,
425 always do so anonymously, whether we have been able to open
426 circuits or not. Partial fix for bug 1938; bugfix on 0.2.0.7-alpha.
427 This behavior makes it *safer* to use UpdateBridgesFromAuthority,
428 but we'll need to wait for bug 6010 before it's actually usable.
430 o Major bugfixes (directory authorities):
431 - When computing weight parameters, behave more robustly in the
432 presence of a bad bwweightscale value. Previously, the authorities
433 would crash if they agreed on a sufficiently broken weight_scale
434 value: now, they use a reasonable default and carry on. Partial
435 fix for 5786; bugfix on 0.2.2.17-alpha.
436 - Check more thoroughly to prevent a rogue authority from
437 double-voting on any consensus directory parameter. Previously,
438 authorities would crash in this case if the total number of
439 votes for any parameter exceeded the number of active voters,
440 but would let it pass otherwise. Partial fix for bug 5786; bugfix
444 - Rate-limit log messages when asked to connect anonymously to
445 a private address. When these hit, they tended to hit fast and
446 often. Also, don't bother trying to connect to addresses that we
447 are sure will resolve to 127.0.0.1: getting 127.0.0.1 in a directory
448 reply makes us think we have been lied to, even when the address the
449 client tried to connect to was "localhost." Resolves ticket 2822.
450 - Allow packagers to insert an extra string in server descriptor
451 platform lines by setting the preprocessor variable TOR_BUILD_TAG.
452 Resolves the rest of ticket 2988.
453 - Raise the threshold of server descriptors needed (75%) and exit
454 server descriptors needed (50%) before we will declare ourselves
455 bootstrapped. This will make clients start building circuits a
456 little later, but makes the initially constructed circuits less
457 skewed and less in conflict with further directory fetches. Fixes
459 - Close any connection that sends unrecognized junk before the
460 handshake. Solves an issue noted in bug 4369.
461 - Improve log messages about managed transports. Resolves ticket 5070.
462 - Tag a bridge's descriptor as "never to be sent unencrypted".
463 This shouldn't matter, since bridges don't open non-anonymous
464 connections to the bridge authority and don't allow unencrypted
465 directory connections from clients, but we might as well make
466 sure. Closes bug 5139.
467 - Expose our view of whether we have gone dormant to the controller,
468 via a new "GETINFO dormant" value. Torbutton and other controllers
469 can use this to avoid doing periodic requests through Tor while
470 it's dormant (bug 4718). Fixes bug 5954.
471 - Tell GCC and Clang to check for any errors in format strings passed
472 to the tor_v*(print|scan)f functions.
473 - Update to the May 1 2012 Maxmind GeoLite Country database.
475 o Minor bugfixes (already included in 0.2.2.36):
476 - Reject out-of-range times like 23:59:61 in parse_rfc1123_time().
477 Fixes bug 5346; bugfix on 0.0.8pre3.
478 - Correct parsing of certain date types in parse_http_time().
479 Without this patch, If-Modified-Since would behave
480 incorrectly. Fixes bug 5346; bugfix on 0.2.0.2-alpha. Patch from
481 Esteban Manchado Velázques.
482 - Make our number-parsing functions always treat too-large values
483 as an error, even when those values exceed the width of the
484 underlying type. Previously, if the caller provided these
485 functions with minima or maxima set to the extreme values of the
486 underlying integer type, these functions would return those
487 values on overflow rather than treating overflow as an error.
488 Fixes part of bug 5786; bugfix on 0.0.9.
489 - If we hit the error case where routerlist_insert() replaces an
490 existing (old) server descriptor, make sure to remove that
491 server descriptor from the old_routers list. Fix related to bug
492 1776. Bugfix on 0.2.2.18-alpha.
493 - Clarify the behavior of MaxCircuitDirtiness with hidden service
494 circuits. Fixes issue 5259.
496 o Minor bugfixes (coding cleanup, on 0.2.2.x and earlier):
497 - Prevent a null-pointer dereference when receiving a data cell
498 for a nonexistent stream when the circuit in question has an
499 empty deliver window. We don't believe this is triggerable,
500 since we don't currently allow deliver windows to become empty,
501 but the logic is tricky enough that it's better to make the code
502 robust. Fixes bug 5541; bugfix on 0.0.2pre14.
503 - Fix a memory leak when trying to launch a DNS request when the
504 network is disabled or the nameservers are unconfigurable. Fixes
505 bug 5916; bugfix on Tor 0.1.2.1-alpha (for the unconfigurable
506 nameserver case) and on 0.2.3.9-alpha (for the DisableNetwork case).
507 - Don't hold a Windows file handle open for every file mapping;
508 the file mapping handle is sufficient. Fixes bug 5951; bugfix on
510 - Avoid O(n^2) performance characteristics when parsing a large
511 extrainfo cache. Fixes bug 5828; bugfix on 0.2.0.1-alpha.
512 - Format more doubles with %f, not %lf. Patch from grarpamp to make
513 Tor build correctly on older BSDs again. Fixes bug 3894; bugfix on
515 - Make our replacement implementation of strtok_r() compatible with
516 the standard behavior of strtok_r(). Patch by nils. Fixes bug 5091;
517 bugfix on 0.2.2.1-alpha.
518 - Fix a NULL-pointer dereference on a badly formed
519 SETCIRCUITPURPOSE command. Found by mikeyc. Fixes bug 5796;
520 bugfix on 0.2.2.9-alpha.
521 - Fix a build warning with Clang 3.1 related to our use of vasprintf.
522 Fixes bug 5969. Bugfix on 0.2.2.11-alpha.
523 - Defensively refactor rend_mid_rendezvous() so that protocol
524 violations and length checks happen in the beginning. Fixes
526 - Set _WIN32_WINNT to 0x0501 consistently throughout the code, so
527 that IPv6 stuff will compile on MSVC, and compilation issues
528 will be easier to track down. Fixes bug 5861.
530 o Minor bugfixes (correctness, on 0.2.2.x and earlier):
531 - Exit nodes now correctly report EADDRINUSE and EADDRNOTAVAIL as
532 resource exhaustion, so that clients can adjust their load to
533 try other exits. Fixes bug 4710; bugfix on 0.1.0.1-rc, which
534 started using END_STREAM_REASON_RESOURCELIMIT.
535 - Don't check for whether the address we're using for outbound
536 connections has changed until after the outbound connection has
537 completed. On Windows, getsockname() doesn't succeed until the
538 connection is finished. Fixes bug 5374; bugfix on 0.1.1.14-alpha.
539 - If the configuration tries to set MyFamily on a bridge, refuse to
540 do so, and warn about the security implications. Fixes bug 4657;
541 bugfix on 0.2.0.3-alpha.
542 - If the client fails to set a reasonable set of ciphersuites
543 during its v2 handshake renegotiation, allow the renegotiation to
544 continue nevertheless (i.e. send all the required certificates).
545 Fixes bug 4591; bugfix on 0.2.0.20-rc.
546 - When we receive a SIGHUP and the controller __ReloadTorrcOnSIGHUP
547 option is set to 0 (which Vidalia version 0.2.16 now does when
548 a SAVECONF attempt fails), perform other actions that SIGHUP
549 usually causes (like reopening the logs). Fixes bug 5095; bugfix
551 - If we fail to write a microdescriptor to the disk cache, do not
552 continue replacing the old microdescriptor file. Fixes bug 2954;
553 bugfix on 0.2.2.6-alpha.
554 - Exit nodes don't need to fetch certificates for authorities that
555 they don't recognize; only directory authorities, bridges,
556 and caches need to do that. Fixes part of bug 2297; bugfix on
558 - Correctly handle checking the permissions on the parent
559 directory of a control socket in the root directory. Bug found
560 by Esteban Manchado Velázquez. Fixes bug 5089; bugfix on Tor
562 - When told to add a bridge with the same digest as a preexisting
563 bridge but a different addr:port, change the addr:port as
564 requested. Previously we would not notice the change. Fixes half
565 of bug 5603; fix on 0.2.2.26-beta.
566 - End AUTHCHALLENGE error messages (in the control protocol) with
567 a CRLF. Fixes bug 5760; bugfix on 0.2.2.36 and 0.2.3.13-alpha.
569 o Minor bugfixes (on 0.2.3.x):
570 - Turn an assertion (that the number of handshakes received as a
571 server is not < 1) into a warning. Fixes bug 4873; bugfix on
573 - Format IPv4 addresses correctly in ADDRMAP events. (Previously,
574 we had reversed them when the answer was cached.) Fixes bug
575 5723; bugfix on 0.2.3.1-alpha.
576 - Work correctly on Linux systems with accept4 support advertised in
577 their headers, but without accept4 support in the kernel. Fix
578 by murb. Fixes bug 5762; bugfix on 0.2.3.1-alpha.
579 - When told to add a bridge with the same addr:port as a preexisting
580 bridge but a different transport, change the transport as
581 requested. Previously we would not notice the change. Fixes half
582 of bug 5603; fix on 0.2.3.2-alpha.
583 - Avoid a "double-reply" warning when replying to a SOCKS request
584 with a parse error. Patch from Fabian Keil. Fixes bug 4108;
585 bugfix on 0.2.3.4-alpha.
586 - Fix a bug where a bridge authority crashes if it has seen no
587 directory requests when it's time to write statistics to disk.
588 Fixes bug 5891; bugfix on 0.2.3.6-alpha. Also fixes bug 5508 in
590 - Don't try to open non-control listeners when DisableNetwork is set.
591 Previously, we'd open all listeners, then immediately close them.
592 Fixes bug 5604; bugfix on 0.2.3.9-alpha.
593 - Don't abort the managed proxy protocol if the managed proxy
594 sends us an unrecognized line; ignore it instead. Fixes bug
595 5910; bugfix on 0.2.3.9-alpha.
596 - Fix a compile warning in crypto.c when compiling with clang 3.1.
597 Fixes bug 5969, bugfix on 0.2.3.9-alpha.
598 - Fix a compilation issue on GNU Hurd, which doesn't have PATH_MAX.
599 Fixes bug 5355; bugfix on 0.2.3.11-alpha.
600 - Remove bogus definition of "_WIN32" from src/win32/orconfig.h, to
601 unbreak the MSVC build. Fixes bug 5858; bugfix on 0.2.3.12-alpha.
602 - Resolve numerous small warnings and build issues with MSVC. Resolves
605 o Documentation fixes:
606 - Improve the manual's documentation for the NT Service command-line
607 options. Addresses ticket 3964.
608 - Clarify SessionGroup documentation slightly; resolves ticket 5437.
609 - Document the changes to the ORPort and DirPort options, and the
610 fact that {OR/Dir}ListenAddress is now unnecessary (and
611 therefore deprecated). Resolves ticket 5597.
614 - Remove the torrc.bridge file: we don't use it for anything, and
615 it had become badly desynchronized from torrc.sample. Resolves
619 Changes in version 0.2.2.36 - 2012-05-24
620 Tor 0.2.2.36 updates the addresses for two of the eight directory
621 authorities, fixes some potential anonymity and security issues,
622 and fixes several crash bugs.
624 Tor 0.2.1.x has reached its end-of-life. Those Tor versions have many
625 known flaws, and nobody should be using them. You should upgrade. If
626 you're using a Linux or BSD and its packages are obsolete, stop using
627 those packages and upgrade anyway.
629 o Directory authority changes:
630 - Change IP address for maatuska (v3 directory authority).
631 - Change IP address for ides (v3 directory authority), and rename
635 - When building or running with any version of OpenSSL earlier
636 than 0.9.8s or 1.0.0f, disable SSLv3 support. These OpenSSL
637 versions have a bug (CVE-2011-4576) in which their block cipher
638 padding includes uninitialized data, potentially leaking sensitive
639 information to any peer with whom they make a SSLv3 connection. Tor
640 does not use SSL v3 by default, but a hostile client or server
641 could force an SSLv3 connection in order to gain information that
642 they shouldn't have been able to get. The best solution here is to
643 upgrade to OpenSSL 0.9.8s or 1.0.0f (or later). But when building
644 or running with a non-upgraded OpenSSL, we disable SSLv3 entirely
645 to make sure that the bug can't happen.
646 - Never use a bridge or a controller-supplied node as an exit, even
647 if its exit policy allows it. Found by wanoskarnet. Fixes bug
648 5342. Bugfix on 0.1.1.15-rc (for controller-purpose descriptors)
649 and 0.2.0.3-alpha (for bridge-purpose descriptors).
650 - Only build circuits if we have a sufficient threshold of the total
651 descriptors that are marked in the consensus with the "Exit"
652 flag. This mitigates an attack proposed by wanoskarnet, in which
653 all of a client's bridges collude to restrict the exit nodes that
654 the client knows about. Fixes bug 5343.
655 - Provide controllers with a safer way to implement the cookie
656 authentication mechanism. With the old method, if another locally
657 running program could convince a controller that it was the Tor
658 process, then that program could trick the controller into telling
659 it the contents of an arbitrary 32-byte file. The new "SAFECOOKIE"
660 authentication method uses a challenge-response approach to prevent
661 this attack. Fixes bug 5185; implements proposal 193.
664 - Avoid logging uninitialized data when unable to decode a hidden
665 service descriptor cookie. Fixes bug 5647; bugfix on 0.2.1.5-alpha.
666 - Avoid a client-side assertion failure when receiving an INTRODUCE2
667 cell on a general purpose circuit. Fixes bug 5644; bugfix on
669 - Fix builds when the path to sed, openssl, or sha1sum contains
670 spaces, which is pretty common on Windows. Fixes bug 5065; bugfix
672 - Correct our replacements for the timeradd() and timersub() functions
673 on platforms that lack them (for example, Windows). The timersub()
674 function is used when expiring circuits, while timeradd() is
675 currently unused. Bug report and patch by Vektor. Fixes bug 4778;
676 bugfix on 0.2.2.24-alpha.
677 - Fix the SOCKET_OK test that we use to tell when socket
678 creation fails so that it works on Win64. Fixes part of bug 4533;
679 bugfix on 0.2.2.29-beta. Bug found by wanoskarnet.
682 - Reject out-of-range times like 23:59:61 in parse_rfc1123_time().
683 Fixes bug 5346; bugfix on 0.0.8pre3.
684 - Make our number-parsing functions always treat too-large values
685 as an error, even when those values exceed the width of the
686 underlying type. Previously, if the caller provided these
687 functions with minima or maxima set to the extreme values of the
688 underlying integer type, these functions would return those
689 values on overflow rather than treating overflow as an error.
690 Fixes part of bug 5786; bugfix on 0.0.9.
691 - Older Linux kernels erroneously respond to strange nmap behavior
692 by having accept() return successfully with a zero-length
693 socket. When this happens, just close the connection. Previously,
694 we would try harder to learn the remote address: but there was
695 no such remote address to learn, and our method for trying to
696 learn it was incorrect. Fixes bugs 1240, 4745, and 4747. Bugfix
697 on 0.1.0.3-rc. Reported and diagnosed by "r1eo".
698 - Correct parsing of certain date types in parse_http_time().
699 Without this patch, If-Modified-Since would behave
700 incorrectly. Fixes bug 5346; bugfix on 0.2.0.2-alpha. Patch from
701 Esteban Manchado Velázques.
702 - Change the BridgePassword feature (part of the "bridge community"
703 design, which is not yet implemented) to use a time-independent
704 comparison. The old behavior might have allowed an adversary
705 to use timing to guess the BridgePassword value. Fixes bug 5543;
706 bugfix on 0.2.0.14-alpha.
707 - Detect and reject certain misformed escape sequences in
708 configuration values. Previously, these values would cause us
709 to crash if received in a torrc file or over an authenticated
710 control port. Bug found by Esteban Manchado Velázquez, and
711 independently by Robert Connolly from Matta Consulting who further
712 noted that it allows a post-authentication heap overflow. Patch
713 by Alexander Schrijver. Fixes bugs 5090 and 5402 (CVE 2012-1668);
714 bugfix on 0.2.0.16-alpha.
715 - Fix a compile warning when using the --enable-openbsd-malloc
716 configure option. Fixes bug 5340; bugfix on 0.2.0.20-rc.
717 - During configure, detect when we're building with clang version
718 3.0 or lower and disable the -Wnormalized=id and -Woverride-init
719 CFLAGS. clang doesn't support them yet.
720 - When sending an HTTP/1.1 proxy request, include a Host header.
721 Fixes bug 5593; bugfix on 0.2.2.1-alpha.
722 - Fix a NULL-pointer dereference on a badly formed SETCIRCUITPURPOSE
723 command. Found by mikeyc. Fixes bug 5796; bugfix on 0.2.2.9-alpha.
724 - If we hit the error case where routerlist_insert() replaces an
725 existing (old) server descriptor, make sure to remove that
726 server descriptor from the old_routers list. Fix related to bug
727 1776. Bugfix on 0.2.2.18-alpha.
729 o Minor bugfixes (documentation and log messages):
730 - Fix a typo in a log message in rend_service_rendezvous_has_opened().
731 Fixes bug 4856; bugfix on Tor 0.0.6.
732 - Update "ClientOnly" man page entry to explain that there isn't
733 really any point to messing with it. Resolves ticket 5005.
734 - Document the GiveGuardFlagTo_CVE_2011_2768_VulnerableRelays
735 directory authority option (introduced in Tor 0.2.2.34).
736 - Downgrade the "We're missing a certificate" message from notice
737 to info: people kept mistaking it for a real problem, whereas it
738 is seldom the problem even when we are failing to bootstrap. Fixes
739 bug 5067; bugfix on 0.2.0.10-alpha.
740 - Correctly spell "connect" in a log message on failure to create a
741 controlsocket. Fixes bug 4803; bugfix on 0.2.2.26-beta.
742 - Clarify the behavior of MaxCircuitDirtiness with hidden service
743 circuits. Fixes issue 5259.
746 - Directory authorities now reject versions of Tor older than
747 0.2.1.30, and Tor versions between 0.2.2.1-alpha and 0.2.2.20-alpha
748 inclusive. These versions accounted for only a small fraction of
749 the Tor network, and have numerous known security issues. Resolves
751 - Update to the May 1 2012 Maxmind GeoLite Country database.
754 - When sending or relaying a RELAY_EARLY cell, we used to convert
755 it to a RELAY cell if the connection was using the v1 link
756 protocol. This was a workaround for older versions of Tor, which
757 didn't handle RELAY_EARLY cells properly. Now that all supported
758 versions can handle RELAY_EARLY cells, and now that we're enforcing
759 the "no RELAY_EXTEND commands except in RELAY_EARLY cells" rule,
760 remove this workaround. Addresses bug 4786.
763 Changes in version 0.2.3.15-alpha - 2012-04-30
764 Tor 0.2.3.15-alpha fixes a variety of smaller bugs, including making
765 the development branch build on Windows again.
767 o Minor bugfixes (on 0.2.2.x and earlier):
768 - Make sure that there are no unhandled pending TLS errors before
769 reading from a TLS stream. We had checks in 0.1.0.3-rc, but
770 lost them in 0.1.0.5-rc when we refactored read_to_buf_tls().
771 Bugfix on 0.1.0.5-rc; fixes bug 4528.
772 - Fix an assert that directory authorities could trigger on sighup
773 during some configuration state transitions. We now don't treat
774 it as a fatal error when the new descriptor we just generated in
775 init_keys() isn't accepted. Fixes bug 4438; bugfix on 0.2.1.9-alpha.
776 - After we pick a directory mirror, we would refuse to use it if
777 it's in our ExcludeExitNodes list, resulting in mysterious failures
778 to bootstrap for people who just wanted to avoid exiting from
779 certain locations. Fixes bug 5623; bugfix on 0.2.2.25-alpha.
780 - When building with --enable-static-tor on OpenBSD, do not
781 erroneously attempt to link -lrt. Fixes bug 5103.
783 o Minor bugfixes (on 0.2.3.x):
784 - When Tor is built with kernel headers from a recent (last few
785 years) Linux kernel, do not fail to run on older (pre-2.6.28
786 Linux kernels). Fixes bug 5112; bugfix on 0.2.3.1-alpha.
787 - Fix cross-compilation issues with mingw. Bugfixes on 0.2.3.6-alpha
789 - Fix compilation with miniupnpc version 1.6; patch from
790 Anthony G. Basile. Fixes bug 5434; bugfix on 0.2.3.12-alpha.
791 - Fix compilation with MSVC, which had defined MS_WINDOWS. Bugfix
792 on 0.2.3.13-alpha; found and fixed by Gisle Vanem.
793 - Fix compilation on platforms without unistd.h, or where environ
794 is defined in stdlib.h. Fixes bug 5704; bugfix on 0.2.3.13-alpha.
797 - Directory authorities are now a little more lenient at accepting
798 older router descriptors, or newer router descriptors that don't
799 make big changes. This should help ameliorate past and future
800 issues where routers think they have uploaded valid descriptors,
801 but the authorities don't think so. Fix for ticket 2479.
802 - Make the code that clients use to detect an address change be
803 IPv6-aware, so that it won't fill clients' logs with error
804 messages when trying to get the IPv4 address of an IPv6
805 connection. Implements ticket 5537.
808 - Remove the GiveGuardFlagTo_CVE_2011_2768_VulnerableRelays option;
809 authorities needed to use it for a while to keep the network working
810 as people upgraded to 0.2.1.31, 0.2.2.34, or 0.2.3.6-alpha, but
811 that was six months ago. As of now, it should no longer be needed
815 Changes in version 0.2.3.14-alpha - 2012-04-23
816 Tor 0.2.3.14-alpha fixes yet more bugs to get us closer to a release
817 candidate. It also dramatically speeds up AES: fast relays should
818 consider switching to the newer OpenSSL library.
820 o Directory authority changes:
821 - Change IP address for ides (v3 directory authority), and rename
825 - Avoid logging uninitialized data when unable to decode a hidden
826 service descriptor cookie. Fixes bug 5647; bugfix on 0.2.1.5-alpha.
827 - Avoid a client-side assertion failure when receiving an INTRODUCE2
828 cell on a general purpose circuit. Fixes bug 5644; bugfix on
830 - If authorities are unable to get a v2 consensus document from other
831 directory authorities, they no longer fall back to fetching
832 them from regular directory caches. Fixes bug 5635; bugfix on
833 0.2.2.26-beta, where routers stopped downloading v2 consensus
835 - When we start a Tor client with a normal consensus already cached,
836 be willing to download a microdescriptor consensus. Fixes bug 4011;
837 fix on 0.2.3.1-alpha.
839 o Major features (performance):
840 - When built to use OpenSSL 1.0.1, and built for an x86 or x86_64
841 instruction set, take advantage of OpenSSL's AESNI, bitsliced, or
842 vectorized AES implementations as appropriate. These can be much,
843 much faster than other AES implementations.
845 o Minor bugfixes (0.2.2.x and earlier):
846 - Don't launch more than 10 service-side introduction-point circuits
847 for a hidden service in five minutes. Previously, we would consider
848 launching more introduction-point circuits if at least one second
849 had passed without any introduction-point circuits failing. Fixes
850 bug 4607; bugfix on 0.0.7pre1.
851 - Change the BridgePassword feature (part of the "bridge community"
852 design, which is not yet implemented) to use a time-independent
853 comparison. The old behavior might have allowed an adversary
854 to use timing to guess the BridgePassword value. Fixes bug 5543;
855 bugfix on 0.2.0.14-alpha.
856 - Enforce correct return behavior of tor_vsscanf() when the '%%'
857 pattern is used. Fixes bug 5558. Bugfix on 0.2.1.13.
858 - When sending an HTTP/1.1 proxy request, include a Host header.
859 Fixes bug 5593; bugfix on 0.2.2.1-alpha.
860 - Don't log that we have "decided to publish new relay descriptor"
861 unless we are actually publishing a descriptor. Fixes bug 3942;
862 bugfix on 0.2.2.28-beta.
864 o Minor bugfixes (0.2.3.x):
865 - Fix a bug where a bridge authority crashes (on a failed assert)
866 if it has seen no directory requests when it's time to write
867 statistics to disk. Fixes bug 5508. Bugfix on 0.2.3.6-alpha.
868 - Fix bug stomping on ORPort option NoListen and ignoring option
869 NoAdvertise. Fixes bug 5151; bugfix on 0.2.3.9-alpha.
870 - In the testsuite, provide a large enough buffer in the tor_sscanf
871 unit test. Otherwise we'd overrun that buffer and crash during
872 the unit tests. Found by weasel. Fixes bug 5449; bugfix on
874 - Make sure we create the keys directory if it doesn't exist and we're
875 about to store the dynamic Diffie-Hellman parameters. Fixes bug
876 5572; bugfix on 0.2.3.13-alpha.
877 - Fix a small memory leak when trying to decode incorrect base16
878 authenticator during SAFECOOKIE authentication. Found by
879 Coverity Scan. Fixes CID 507. Bugfix on 0.2.3.13-alpha.
882 - Add more information to a log statement that might help track down
883 bug 4091. If you're seeing "Bug: tor_addr_is_internal() called with a
884 non-IP address" messages (or any Bug messages, for that matter!),
885 please let us know about it.
886 - Relays now understand an IPv6 address when they get one from a
887 directory server. Resolves ticket 4875.
888 - Resolve IPv6 addresses in bridge and entry statistics to country
889 code "??" which means we at least count them. Resolves ticket 5053;
890 improves on 0.2.3.9-alpha.
891 - Update to the April 3 2012 Maxmind GeoLite Country database.
892 - Begin a doc/state-contents.txt file to explain the contents of
893 the Tor state file. Fixes bug 2987.
895 o Default torrc changes:
896 - Stop listing "socksport 9050" in torrc.sample. We open a socks
897 port on 9050 by default anyway, so this should not change anything
899 - Stop mentioning the deprecated *ListenAddress options in
900 torrc.sample. Fixes bug 5438.
901 - Document unit of bandwidth related options in sample torrc.
905 - The "torify" script no longer supports the "tsocks" socksifier
906 tool, since tsocks doesn't support DNS and UDP right for Tor.
907 Everyone should be using torsocks instead. Fixes bugs 3530 and
908 5180. Based on a patch by "ugh".
911 - Change the symmetric cipher interface so that creating and
912 initializing a stream cipher are no longer separate functions.
913 - Remove all internal support for unpadded RSA. We never used it, and
914 it would be a bad idea to start.
917 Changes in version 0.2.3.13-alpha - 2012-03-26
918 Tor 0.2.3.13-alpha fixes a variety of stability and correctness bugs
919 in managed pluggable transports, as well as providing other cleanups
920 that get us closer to a release candidate.
922 o Directory authority changes:
923 - Change IP address for maatuska (v3 directory authority).
926 - Provide controllers with a safer way to implement the cookie
927 authentication mechanism. With the old method, if another locally
928 running program could convince a controller that it was the Tor
929 process, then that program could trick the controller into telling
930 it the contents of an arbitrary 32-byte file. The new "SAFECOOKIE"
931 authentication method uses a challenge-response approach to prevent
932 this attack. Fixes bug 5185, implements proposal 193.
933 - Never use a bridge or a controller-supplied node as an exit, even
934 if its exit policy allows it. Found by wanoskarnet. Fixes bug
935 5342. Bugfix on 0.1.1.15-rc (for controller-purpose descriptors)
936 and 0.2.0.3-alpha (for bridge-purpose descriptors).
937 - Only build circuits if we have a sufficient threshold of the total
938 descriptors that are marked in the consensus with the "Exit"
939 flag. This mitigates an attack proposed by wanoskarnet, in which
940 all of a client's bridges collude to restrict the exit nodes that
941 the client knows about. Fixes bug 5343.
943 o Major bugfixes (on Tor 0.2.3.x):
944 - Avoid an assert when managed proxies like obfsproxy are configured,
945 and we receive HUP signals or setconf attempts too rapidly. This
946 situation happens most commonly when Vidalia tries to attach to
947 Tor or tries to configure the Tor it's attached to. Fixes bug 5084;
948 bugfix on 0.2.3.6-alpha.
949 - Fix a relay-side pluggable transports bug where managed proxies were
950 unreachable from the Internet, because Tor asked them to bind on
951 localhost. Fixes bug 4725; bugfix on 0.2.3.9-alpha.
952 - Stop discarding command-line arguments when TestingTorNetwork
953 is set. Discovered by Kevin Bauer. Fixes bug 5373; bugfix on
954 0.2.3.9-alpha, where task 4552 added support for two layers of
956 - Resume allowing the unit tests to run in gdb. This was accidentally
957 made impossible when the DisableDebuggerAttachment option was
958 introduced. Fixes bug 5448; bugfix on 0.2.3.9-alpha.
959 - Resume building with nat-pmp support. Fixes bug 4955; bugfix on
960 0.2.3.11-alpha. Reported by Anthony G. Basile.
962 o Minor bugfixes (on 0.2.2.x and earlier):
963 - Ensure we don't cannibalize circuits that are longer than three hops
964 already, so we don't end up making circuits with 5 or more
965 hops. Patch contributed by wanoskarnet. Fixes bug 5231; bugfix on
966 0.1.0.1-rc which introduced cannibalization.
967 - Detect and reject certain misformed escape sequences in
968 configuration values. Previously, these values would cause us
969 to crash if received in a torrc file or over an authenticated
970 control port. Bug found by Esteban Manchado Velázquez, and
971 independently by Robert Connolly from Matta Consulting who further
972 noted that it allows a post-authentication heap overflow. Patch
973 by Alexander Schrijver. Fixes bugs 5090 and 5402 (CVE 2012-1668);
974 bugfix on 0.2.0.16-alpha.
975 - Fix a compile warning when using the --enable-openbsd-malloc
976 configure option. Fixes bug 5340; bugfix on 0.2.0.20-rc.
977 - Directory caches no longer refuse to clean out descriptors because
978 of missing v2 networkstatus documents, unless they're configured
979 to retrieve v2 networkstatus documents. Fixes bug 4838; bugfix on
980 0.2.2.26-beta. Patch by Daniel Bryg.
981 - Update to the latest version of the tinytest unit testing framework.
982 This includes a couple of bugfixes that can be relevant for
983 running forked unit tests on Windows, and removes all reserved
986 o Minor bugfixes (on 0.2.3.x):
987 - On a failed pipe() call, don't leak file descriptors. Fixes bug
988 4296; bugfix on 0.2.3.1-alpha.
989 - Spec conformance: on a v3 handshake, do not send a NETINFO cell
990 until after we have received a CERTS cell. Fixes bug 4361; bugfix
991 on 0.2.3.6-alpha. Patch by "frosty".
992 - When binding to an IPv6 address, set the IPV6_V6ONLY socket
993 option, so that the IP stack doesn't decide to use it for IPv4
994 too. Fixes bug 4760; bugfix on 0.2.3.9-alpha.
995 - Ensure that variables set in Tor's environment cannot override
996 environment variables that Tor passes to a managed
997 pluggable-transport proxy. Previously, Tor would pass every
998 variable in its environment to managed proxies along with the new
999 ones, in such a way that on many operating systems, the inherited
1000 environment variables would override those which Tor tried to
1001 explicitly set. Bugfix on 0.2.3.12-alpha for most Unixoid systems;
1002 bugfix on 0.2.3.9-alpha for Windows.
1005 - A wide variety of new unit tests by Esteban Manchado Velázquez.
1006 - Shorten links in the tor-exit-notice file. Patch by Christian Kujau.
1007 - Update to the March 6 2012 Maxmind GeoLite Country database.
1010 Changes in version 0.2.3.12-alpha - 2012-02-13
1011 Tor 0.2.3.12-alpha lets fast exit relays scale better, allows clients
1012 to use bridges that run Tor 0.2.2.x, and resolves several big bugs
1013 when Tor is configured to use a pluggable transport like obfsproxy.
1016 - Fix builds when the path to sed, openssl, or sha1sum contains
1017 spaces, which is pretty common on Windows. Fixes bug 5065; bugfix
1019 - Set the SO_REUSEADDR socket option before we call bind() on outgoing
1020 connections. This change should allow busy exit relays to stop
1021 running out of available sockets as quickly. Fixes bug 4950;
1022 bugfix on 0.2.2.26-beta.
1023 - Allow 0.2.3.x clients to use 0.2.2.x bridges. Previously the client
1024 would ask the bridge for microdescriptors, which are only supported
1025 in 0.2.3.x, and then fail to bootstrap when it didn't get the
1026 answers it wanted. Fixes bug 4013; bugfix on 0.2.3.2-alpha.
1027 - Properly set up obfsproxy's environment when in managed mode. The
1028 Tor Browser Bundle needs LD_LIBRARY_PATH to be passed to obfsproxy,
1029 and when you run your Tor as a daemon, there's no HOME. Fixes bugs
1030 5076 and 5082; bugfix on 0.2.3.6-alpha.
1033 - Use the dead_strip option when building Tor on OS X. This reduces
1034 binary size by almost 19% when linking openssl and libevent
1035 statically, which we do for Tor Browser Bundle.
1036 - Fix broken URLs in the sample torrc file, and tell readers about
1037 the OutboundBindAddress, ExitPolicyRejectPrivate, and
1038 PublishServerDescriptor options. Addresses bug 4652.
1039 - Update to the February 7 2012 Maxmind GeoLite Country database.
1042 - Downgrade the "We're missing a certificate" message from notice
1043 to info: people kept mistaking it for a real problem, whereas it
1044 is seldom the problem even when we are failing to bootstrap. Fixes
1045 bug 5067; bugfix on 0.2.0.10-alpha.
1046 - Don't put "TOR_PT_EXTENDED_SERVER_PORT=127.0.0.1:4200" in a
1047 managed pluggable transport server proxy's environment.
1048 Previously, we would put it there, even though Tor doesn't
1049 implement an 'extended server port' yet, and even though Tor
1050 almost certainly isn't listening at that address. For now, we set
1051 it to an empty string to avoid crashing older obfsproxies. Bugfix
1053 - Log the heartbeat message every HeartbeatPeriod seconds, not every
1054 HeartbeatPeriod + 1 seconds. Fixes bug 4942; bugfix on
1055 0.2.3.1-alpha. Bug reported by Scott Bennett.
1056 - Calculate absolute paths correctly on Windows. Fixes bug 4973;
1057 bugfix on 0.2.3.11-alpha.
1058 - Update "ClientOnly" man page entry to explain that there isn't
1059 really any point to messing with it. Resolves ticket 5005.
1060 - Use the correct CVE number for CVE-2011-4576 in our comments and
1061 log messages. Found by "fermenthor". Resolves bug 5066; bugfix on
1064 o Code simplifications and refactoring:
1065 - Use the _WIN32 macro throughout our code to detect Windows.
1066 (Previously we had used the obsolete 'WIN32' and the idiosyncratic
1070 Changes in version 0.2.3.11-alpha - 2012-01-22
1071 Tor 0.2.3.11-alpha marks feature-freeze for the 0.2.3 tree. It deploys
1072 the last step of the plan to limit maximum circuit length, includes
1073 a wide variety of hidden service performance and correctness fixes,
1074 works around an OpenSSL security flaw if your distro is too stubborn
1075 to upgrade, and fixes a bunch of smaller issues.
1078 - Now that Tor 0.2.0.x is completely deprecated, enable the final
1079 part of "Proposal 110: Avoiding infinite length circuits" by
1080 refusing all circuit-extend requests that do not use a relay_early
1081 cell. This change helps Tor resist a class of denial-of-service
1082 attacks by limiting the maximum circuit length.
1083 - Adjust the number of introduction points that a hidden service
1084 will try to maintain based on how long its introduction points
1085 remain in use and how many introductions they handle. Fixes
1087 - Try to use system facilities for enumerating local interface
1088 addresses, before falling back to our old approach (which was
1089 binding a UDP socket, and calling getsockname() on it). That
1090 approach was scaring OS X users whose draconian firewall
1091 software warned about binding to UDP sockets, regardless of
1092 whether packets were sent. Now we try to use getifaddrs(),
1093 SIOCGIFCONF, or GetAdaptersAddresses(), depending on what the
1094 system supports. Resolves ticket 1827.
1096 o Major security workaround:
1097 - When building or running with any version of OpenSSL earlier
1098 than 0.9.8s or 1.0.0f, disable SSLv3 support. These OpenSSL
1099 versions have a bug (CVE-2011-4576) in which their block cipher
1100 padding includes uninitialized data, potentially leaking sensitive
1101 information to any peer with whom they make a SSLv3 connection. Tor
1102 does not use SSL v3 by default, but a hostile client or server
1103 could force an SSLv3 connection in order to gain information that
1104 they shouldn't have been able to get. The best solution here is to
1105 upgrade to OpenSSL 0.9.8s or 1.0.0f (or later). But when building
1106 or running with a non-upgraded OpenSSL, we disable SSLv3 entirely
1107 to make sure that the bug can't happen.
1110 - Fix the SOCKET_OK test that we use to tell when socket
1111 creation fails so that it works on Win64. Fixes part of bug 4533;
1112 bugfix on 0.2.2.29-beta. Bug found by wanoskarnet.
1113 - Correct our replacements for the timeradd() and timersub() functions
1114 on platforms that lack them (for example, Windows). The timersub()
1115 function is used when expiring circuits, while timeradd() is
1116 currently unused. Bug report and patch by Vektor. Fixes bug 4778;
1117 bugfix on 0.2.2.24-alpha and 0.2.3.1-alpha.
1118 - Do not use OpenSSL 1.0.0's counter mode: it has a critical bug
1119 that was fixed in OpenSSL 1.0.0a. We test for the counter mode
1120 bug at runtime, not compile time, because some distributions hack
1121 their OpenSSL to mis-report its version. Fixes bug 4779; bugfix
1122 on 0.2.3.9-alpha. Found by Pascal.
1124 o Minor features (controller):
1125 - Use absolute path names when reporting the torrc filename in the
1126 control protocol, so a controller can more easily find the torrc
1127 file. Resolves bug 1101.
1128 - Extend the control protocol to report flags that control a circuit's
1129 path selection in CIRC events and in replies to 'GETINFO
1130 circuit-status'. Implements part of ticket 2411.
1131 - Extend the control protocol to report the hidden service address
1132 and current state of a hidden-service-related circuit in CIRC
1133 events and in replies to 'GETINFO circuit-status'. Implements part
1135 - When reporting the path to the cookie file to the controller,
1136 give an absolute path. Resolves ticket 4881.
1137 - Allow controllers to request an event notification whenever a
1138 circuit is cannibalized or its purpose is changed. Implements
1139 part of ticket 3457.
1140 - Include the creation time of a circuit in CIRC and CIRC2
1141 control-port events and the list produced by the 'GETINFO
1142 circuit-status' control-port command.
1144 o Minor features (directory authorities):
1145 - Directory authorities now reject versions of Tor older than
1146 0.2.1.30, and Tor versions between 0.2.2.1-alpha and 0.2.2.20-alpha
1147 inclusive. These versions accounted for only a small fraction of
1148 the Tor network, and have numerous known security issues. Resolves
1150 - Authority operators can now vote for all relays in a given
1151 set of countries to be BadDir/BadExit/Invalid/Rejected.
1152 - Provide two consensus parameters (FastFlagMinThreshold and
1153 FastFlagMaxThreshold) to control the range of allowable bandwidths
1154 for the Fast directory flag. These allow authorities to run
1155 experiments on appropriate requirements for being a "Fast" node.
1156 The AuthDirFastGuarantee config value still applies.
1157 - Document the GiveGuardFlagTo_CVE_2011_2768_VulnerableRelays
1158 directory authority option (introduced in Tor 0.2.2.34).
1160 o Minor features (other):
1161 - Don't disable the DirPort when we cannot exceed our AccountingMax
1162 limit during this interval because the effective bandwidthrate is
1163 low enough. This is useful in a situation where AccountMax is only
1164 used as an additional safeguard or to provide statistics.
1165 - Prepend an informative header to generated dynamic_dh_params files.
1166 - If EntryNodes are given, but UseEntryGuards is set to 0, warn that
1167 EntryNodes will have no effect. Resolves issue 2571.
1168 - Log more useful messages when we fail to disable debugger
1170 - Log which authority we're missing votes from when we go to fetch
1171 them from the other auths.
1172 - Log (at debug level) whenever a circuit's purpose is changed.
1173 - Add missing documentation for the MaxClientCircuitsPending,
1174 UseMicrodescriptors, UserspaceIOCPBuffers, and
1175 _UseFilteringSSLBufferevents options, all introduced during
1177 - Update to the January 3 2012 Maxmind GeoLite Country database.
1179 o Minor bugfixes (hidden services):
1180 - Don't close hidden service client circuits which have almost
1181 finished connecting to their destination when they reach
1182 the normal circuit-build timeout. Previously, we would close
1183 introduction circuits which are waiting for an acknowledgement
1184 from the introduction point, and rendezvous circuits which have
1185 been specified in an INTRODUCE1 cell sent to a hidden service,
1186 after the normal CBT. Now, we mark them as 'timed out', and launch
1187 another rendezvous attempt in parallel. This behavior change can
1188 be disabled using the new CloseHSClientCircuitsImmediatelyOnTimeout
1189 option. Fixes part of bug 1297; bugfix on 0.2.2.2-alpha.
1190 - Don't close hidden-service-side rendezvous circuits when they
1191 reach the normal circuit-build timeout. This behaviour change can
1192 be disabled using the new
1193 CloseHSServiceRendCircuitsImmediatelyOnTimeout option. Fixes the
1194 remaining part of bug 1297; bugfix on 0.2.2.2-alpha.
1195 - Make sure we never mark the wrong rendezvous circuit as having
1196 had its introduction cell acknowleged by the introduction-point
1197 relay. Previously, when we received an INTRODUCE_ACK cell on a
1198 client-side hidden-service introduction circuit, we might have
1199 marked a rendezvous circuit other than the one we specified in
1200 the INTRODUCE1 cell as INTRO_ACKED, which would have produced
1201 a warning message and interfered with the hidden service
1202 connection-establishment process. Fixes bug 4759; bugfix on
1203 0.2.3.3-alpha, when we added the stream-isolation feature which
1204 might cause Tor to open multiple rendezvous circuits for the same
1206 - Don't trigger an assertion failure when we mark a new client-side
1207 hidden-service introduction circuit for close during the process
1208 of creating it. Fixes bug 4796; bugfix on 0.2.3.6-alpha. Reported
1211 o Minor bugfixes (log messages):
1212 - Correctly spell "connect" in a log message on failure to create a
1213 controlsocket. Fixes bug 4803; bugfix on 0.2.2.26-beta and
1215 - Fix a typo in a log message in rend_service_rendezvous_has_opened().
1216 Fixes bug 4856; bugfix on Tor 0.0.6.
1217 - Fix the log message describing how we work around discovering
1218 that our version is the ill-fated OpenSSL 0.9.8l. Fixes bug
1219 4837; bugfix on 0.2.2.9-alpha.
1220 - When logging about a disallowed .exit name, do not also call it
1221 an "invalid onion address". Fixes bug 3325; bugfix on 0.2.2.9-alpha.
1223 o Minor bugfixes (build fixes):
1224 - During configure, detect when we're building with clang version
1225 3.0 or lower and disable the -Wnormalized=id and -Woverride-init
1226 CFLAGS. clang doesn't support them yet.
1227 - During configure, search for library containing cos function as
1228 libm lives in libcore on some platforms (BeOS/Haiku). Linking
1229 against libm was hard-coded before. Fixes the first part of bug
1230 4727; bugfix on 0.2.2.2-alpha. Patch and analysis by Martin Hebnes
1232 - Detect attempts to build Tor on (as yet hypothetical) versions
1233 of Windows where sizeof(intptr_t) != sizeof(SOCKET). Partial
1234 fix for bug 4533. Bugfix on 0.2.2.28-beta.
1235 - Preprocessor directives should not be put inside the arguments
1236 of a macro. This would break compilation with GCC releases prior
1237 to version 3.3. We would never recommend such an old GCC version,
1238 but it is apparently required for binary compatibility on some
1239 platforms (namely, certain builds of Haiku). Fixes the other part
1240 of bug 4727; bugfix on 0.2.3.3-alpha. Patch and analysis by Martin
1243 o Minor bugfixes (other):
1244 - Older Linux kernels erroneously respond to strange nmap behavior
1245 by having accept() return successfully with a zero-length
1246 socket. When this happens, just close the connection. Previously,
1247 we would try harder to learn the remote address: but there was
1248 no such remote address to learn, and our method for trying to
1249 learn it was incorrect. Fixes bugs 1240, 4745, and 4747. Bugfix
1250 on 0.1.0.3-rc. Reported and diagnosed by "r1eo".
1251 - Fix null-pointer access that could occur if TLS allocation failed.
1252 Fixes bug 4531; bugfix on 0.2.0.20-rc. Found by "troll_un". This was
1253 erroneously listed as fixed in 0.2.3.9-alpha, but the fix had
1254 accidentally been reverted.
1255 - Fix our implementation of crypto_random_hostname() so it can't
1256 overflow on ridiculously large inputs. (No Tor version has ever
1257 provided this kind of bad inputs, but let's be correct in depth.)
1258 Fixes bug 4413; bugfix on 0.2.2.9-alpha. Fix by Stephen Palmateer.
1259 - Find more places in the code that should have been testing for
1260 invalid sockets using the SOCKET_OK macro. Required for a fix
1261 for bug 4533. Bugfix on 0.2.2.28-beta.
1262 - Fix an assertion failure when, while running with bufferevents, a
1263 connection finishes connecting after it is marked for close, but
1264 before it is closed. Fixes bug 4697; bugfix on 0.2.3.1-alpha.
1265 - test_util_spawn_background_ok() hardcoded the expected value
1266 for ENOENT to 2. This isn't portable as error numbers are
1267 platform specific, and particularly the hurd has ENOENT at
1268 0x40000002. Construct expected string at runtime, using the correct
1269 value for ENOENT. Fixes bug 4733; bugfix on 0.2.3.1-alpha.
1270 - Reject attempts to disable DisableDebuggerAttachment while Tor is
1271 running. Fixes bug 4650; bugfix on 0.2.3.9-alpha.
1272 - Use an appropriate-width type for sockets in tor-fw-helper on
1273 win64. Fixes bug 1983 at last. Bugfix on 0.2.3.9-alpha.
1276 - When sending or relaying a RELAY_EARLY cell, we used to convert
1277 it to a RELAY cell if the connection was using the v1 link
1278 protocol. This was a workaround for older versions of Tor, which
1279 didn't handle RELAY_EARLY cells properly. Now that all supported
1280 versions can handle RELAY_EARLY cells, and now that we're enforcing
1281 the "no RELAY_EXTEND commands except in RELAY_EARLY cells" rule,
1282 remove this workaround. Addresses bug 4786.
1284 o Code simplifications and refactoring:
1285 - Use OpenSSL's built-in SSL_state_string_long() instead of our
1286 own homebrewed ssl_state_to_string() replacement. Patch from
1287 Emile Snyder. Fixes bug 4653.
1288 - Use macros to indicate OpenSSL versions, so we don't need to worry
1289 about accidental hexadecimal bit shifts.
1290 - Remove some workaround code for OpenSSL 0.9.6 (which is no longer
1292 - Convert more instances of tor_snprintf+tor_strdup into tor_asprintf.
1293 - Use the smartlist_add_asprintf() alias more consistently.
1294 - Use a TOR_INVALID_SOCKET macro when initializing a socket to an
1295 invalid value, rather than just -1.
1296 - Rename a handful of old identifiers, mostly related to crypto
1297 structures and crypto functions. By convention, our "create an
1298 object" functions are called "type_new()", our "free an object"
1299 functions are called "type_free()", and our types indicate that
1300 they are types only with a final "_t". But a handful of older
1301 types and functions broke these rules, with function names like
1302 "type_create" or "subsystem_op_type", or with type names like
1306 Changes in version 0.2.3.10-alpha - 2011-12-16
1307 Tor 0.2.3.10-alpha fixes a critical heap-overflow security issue in
1308 Tor's buffers code. Absolutely everybody should upgrade.
1310 The bug relied on an incorrect calculation when making data continuous
1311 in one of our IO buffers, if the first chunk of the buffer was
1312 misaligned by just the wrong amount. The miscalculation would allow an
1313 attacker to overflow a piece of heap-allocated memory. To mount this
1314 attack, the attacker would need to either open a SOCKS connection to
1315 Tor's SocksPort (usually restricted to localhost), or target a Tor
1316 instance configured to make its connections through a SOCKS proxy
1317 (which Tor does not do by default).
1319 Good security practice requires that all heap-overflow bugs should be
1320 presumed to be exploitable until proven otherwise, so we are treating
1321 this as a potential code execution attack. Please upgrade immediately!
1322 This bug does not affect bufferevents-based builds of Tor. Special
1323 thanks to "Vektor" for reporting this issue to us!
1325 This release also contains a few minor bugfixes for issues discovered
1329 - Fix a heap overflow bug that could occur when trying to pull
1330 data into the first chunk of a buffer, when that chunk had
1331 already had some data drained from it. Fixes CVE-2011-2778;
1332 bugfix on 0.2.0.16-alpha. Reported by "Vektor".
1335 - If we can't attach streams to a rendezvous circuit when we
1336 finish connecting to a hidden service, clear the rendezvous
1337 circuit's stream-isolation state and try to attach streams
1338 again. Previously, we cleared rendezvous circuits' isolation
1339 state either too early (if they were freshly built) or not at all
1340 (if they had been built earlier and were cannibalized). Bugfix on
1341 0.2.3.3-alpha; fixes bug 4655.
1342 - Fix compilation of the libnatpmp helper on non-Windows. Bugfix on
1343 0.2.3.9-alpha; fixes bug 4691. Reported by Anthony G. Basile.
1344 - Fix an assertion failure when a relay with accounting enabled
1345 starts up while dormant. Fixes bug 4702; bugfix on 0.2.3.9-alpha.
1348 - Update to the December 6 2011 Maxmind GeoLite Country database.
1351 Changes in version 0.2.2.35 - 2011-12-16
1352 Tor 0.2.2.35 fixes a critical heap-overflow security issue in Tor's
1353 buffers code. Absolutely everybody should upgrade.
1355 The bug relied on an incorrect calculation when making data continuous
1356 in one of our IO buffers, if the first chunk of the buffer was
1357 misaligned by just the wrong amount. The miscalculation would allow an
1358 attacker to overflow a piece of heap-allocated memory. To mount this
1359 attack, the attacker would need to either open a SOCKS connection to
1360 Tor's SocksPort (usually restricted to localhost), or target a Tor
1361 instance configured to make its connections through a SOCKS proxy
1362 (which Tor does not do by default).
1364 Good security practice requires that all heap-overflow bugs should be
1365 presumed to be exploitable until proven otherwise, so we are treating
1366 this as a potential code execution attack. Please upgrade immediately!
1367 This bug does not affect bufferevents-based builds of Tor. Special
1368 thanks to "Vektor" for reporting this issue to us!
1370 Tor 0.2.2.35 also fixes several bugs in previous versions, including
1371 crash bugs for unusual configurations, and a long-term bug that
1372 would prevent Tor from starting on Windows machines with draconian
1375 With this release, we remind everyone that 0.2.0.x has reached its
1376 formal end-of-life. Those Tor versions have many known flaws, and
1377 nobody should be using them. You should upgrade -- ideally to the
1378 0.2.2.x series. If you're using a Linux or BSD and its packages are
1379 obsolete, stop using those packages and upgrade anyway.
1381 The Tor 0.2.1.x series is also approaching its end-of-life: it will no
1382 longer receive support after some time in early 2012.
1385 - Fix a heap overflow bug that could occur when trying to pull
1386 data into the first chunk of a buffer, when that chunk had
1387 already had some data drained from it. Fixes CVE-2011-2778;
1388 bugfix on 0.2.0.16-alpha. Reported by "Vektor".
1389 - Initialize Libevent with the EVENT_BASE_FLAG_NOLOCK flag enabled, so
1390 that it doesn't attempt to allocate a socketpair. This could cause
1391 some problems on Windows systems with overzealous firewalls. Fix for
1392 bug 4457; workaround for Libevent versions 2.0.1-alpha through
1394 - If we mark an OR connection for close based on a cell we process,
1395 don't process any further cells on it. We already avoid further
1396 reads on marked-for-close connections, but now we also discard the
1397 cells we'd already read. Fixes bug 4299; bugfix on 0.2.0.10-alpha,
1398 which was the first version where we might mark a connection for
1399 close based on processing a cell on it.
1400 - Correctly sanity-check that we don't underflow on a memory
1401 allocation (and then assert) for hidden service introduction
1402 point decryption. Bug discovered by Dan Rosenberg. Fixes bug 4410;
1403 bugfix on 0.2.1.5-alpha.
1404 - Fix a memory leak when we check whether a hidden service
1405 descriptor has any usable introduction points left. Fixes bug
1406 4424. Bugfix on 0.2.2.25-alpha.
1407 - Don't crash when we're running as a relay and don't have a GeoIP
1408 file. Bugfix on 0.2.2.34; fixes bug 4340. This backports a fix
1409 we've had in the 0.2.3.x branch already.
1410 - When running as a client, do not print a misleading (and plain
1411 wrong) log message that we're collecting "directory request"
1412 statistics: clients don't collect statistics. Also don't create a
1413 useless (because empty) stats file in the stats/ directory. Fixes
1414 bug 4353; bugfix on 0.2.2.34.
1417 - Detect failure to initialize Libevent. This fix provides better
1418 detection for future instances of bug 4457.
1419 - Avoid frequent calls to the fairly expensive cull_wedged_cpuworkers
1420 function. This was eating up hideously large amounts of time on some
1421 busy servers. Fixes bug 4518; bugfix on 0.0.9.8.
1422 - Resolve an integer overflow bug in smartlist_ensure_capacity().
1423 Fixes bug 4230; bugfix on Tor 0.1.0.1-rc. Based on a patch by
1425 - Don't warn about unused log_mutex in log.c when building with
1426 --disable-threads using a recent GCC. Fixes bug 4437; bugfix on
1427 0.1.0.6-rc which introduced --disable-threads.
1428 - When configuring, starting, or stopping an NT service, stop
1429 immediately after the service configuration attempt has succeeded
1430 or failed. Fixes bug 3963; bugfix on 0.2.0.7-alpha.
1431 - When sending a NETINFO cell, include the original address
1432 received for the other side, not its canonical address. Found
1433 by "troll_un"; fixes bug 4349; bugfix on 0.2.0.10-alpha.
1434 - Fix a typo in a hibernation-related log message. Fixes bug 4331;
1435 bugfix on 0.2.2.23-alpha; found by "tmpname0901".
1436 - Fix a memory leak in launch_direct_bridge_descriptor_fetch() that
1437 occurred when a client tried to fetch a descriptor for a bridge
1438 in ExcludeNodes. Fixes bug 4383; bugfix on 0.2.2.25-alpha.
1439 - Backport fixes for a pair of compilation warnings on Windows.
1440 Fixes bug 4521; bugfix on 0.2.2.28-beta and on 0.2.2.29-beta.
1441 - If we had ever tried to call tor_addr_to_str on an address of
1442 unknown type, we would have done a strdup on an uninitialized
1443 buffer. Now we won't. Fixes bug 4529; bugfix on 0.2.1.3-alpha.
1444 Reported by "troll_un".
1445 - Correctly detect and handle transient lookup failures from
1446 tor_addr_lookup. Fixes bug 4530; bugfix on 0.2.1.5-alpha.
1447 Reported by "troll_un".
1448 - Fix null-pointer access that could occur if TLS allocation failed.
1449 Fixes bug 4531; bugfix on 0.2.0.20-rc. Found by "troll_un".
1450 - Use tor_socket_t type for listener argument to accept(). Fixes bug
1451 4535; bugfix on 0.2.2.28-beta. Found by "troll_un".
1454 - Add two new config options for directory authorities:
1455 AuthDirFastGuarantee sets a bandwidth threshold for guaranteeing the
1456 Fast flag, and AuthDirGuardBWGuarantee sets a bandwidth threshold
1457 that is always sufficient to satisfy the bandwidth requirement for
1458 the Guard flag. Now it will be easier for researchers to simulate
1459 Tor networks with different values. Resolves ticket 4484.
1460 - When Tor ignores a hidden service specified in its configuration,
1461 include the hidden service's directory in the warning message.
1462 Previously, we would only tell the user that some hidden service
1463 was ignored. Bugfix on 0.0.6; fixes bug 4426.
1464 - Update to the December 6 2011 Maxmind GeoLite Country database.
1466 o Packaging changes:
1467 - Make it easier to automate expert package builds on Windows,
1468 by removing an absolute path from makensis.exe command.
1471 Changes in version 0.2.3.9-alpha - 2011-12-08
1472 Tor 0.2.3.9-alpha introduces initial IPv6 support for bridges, adds
1473 a "DisableNetwork" security feature that bundles can use to avoid
1474 touching the network until bridges are configured, moves forward on
1475 the pluggable transport design, fixes a flaw in the hidden service
1476 design that unnecessarily prevented clients with wrong clocks from
1477 reaching hidden services, and fixes a wide variety of other issues.
1480 - Clients can now connect to private bridges over IPv6. Bridges
1481 still need at least one IPv4 address in order to connect to
1482 other relays. Note that we don't yet handle the case where the
1483 user has two bridge lines for the same bridge (one IPv4, one
1484 IPv6). Implements parts of proposal 186.
1485 - New "DisableNetwork" config option to prevent Tor from launching any
1486 connections or accepting any connections except on a control port.
1487 Bundles and controllers can set this option before letting Tor talk
1488 to the rest of the network, for example to prevent any connections
1489 to a non-bridge address. Packages like Orbot can also use this
1490 option to instruct Tor to save power when the network is off.
1491 - Clients and bridges can now be configured to use a separate
1492 "transport" proxy. This approach makes the censorship arms race
1493 easier by allowing bridges to use protocol obfuscation plugins. It
1494 implements the "managed proxy" part of proposal 180 (ticket 3472).
1495 - When using OpenSSL 1.0.0 or later, use OpenSSL's counter mode
1496 implementation. It makes AES_CTR about 7% faster than our old one
1497 (which was about 10% faster than the one OpenSSL used to provide).
1498 Resolves ticket 4526.
1499 - Add a "tor2web mode" for clients that want to connect to hidden
1500 services non-anonymously (and possibly more quickly). As a safety
1501 measure to try to keep users from turning this on without knowing
1502 what they are doing, tor2web mode must be explicitly enabled at
1503 compile time, and a copy of Tor compiled to run in tor2web mode
1504 cannot be used as a normal Tor client. Implements feature 2553.
1505 - Add experimental support for running on Windows with IOCP and no
1506 kernel-space socket buffers. This feature is controlled by a new
1507 "UserspaceIOCPBuffers" config option (off by default), which has
1508 no effect unless Tor has been built with support for bufferevents,
1509 is running on Windows, and has enabled IOCP. This may, in the long
1510 run, help solve or mitigate bug 98.
1511 - Use a more secure consensus parameter voting algorithm. Now at
1512 least three directory authorities or a majority of them must
1513 vote on a given parameter before it will be included in the
1514 consensus. Implements proposal 178.
1517 - Hidden services now ignore the timestamps on INTRODUCE2 cells.
1518 They used to check that the timestamp was within 30 minutes
1519 of their system clock, so they could cap the size of their
1520 replay-detection cache, but that approach unnecessarily refused
1521 service to clients with wrong clocks. Bugfix on 0.2.1.6-alpha, when
1522 the v3 intro-point protocol (the first one which sent a timestamp
1523 field in the INTRODUCE2 cell) was introduced; fixes bug 3460.
1524 - Only use the EVP interface when AES acceleration is enabled,
1525 to avoid a 5-7% performance regression. Resolves issue 4525;
1526 bugfix on 0.2.3.8-alpha.
1528 o Privacy/anonymity features (bridge detection):
1529 - Make bridge SSL certificates a bit more stealthy by using random
1530 serial numbers, in the same fashion as OpenSSL when generating
1531 self-signed certificates. Implements ticket 4584.
1532 - Introduce a new config option "DynamicDHGroups", enabled by
1533 default, which provides each bridge with a unique prime DH modulus
1534 to be used during SSL handshakes. This option attempts to help
1535 against censors who might use the Apache DH modulus as a static
1536 identifier for bridges. Addresses ticket 4548.
1538 o Minor features (new/different config options):
1539 - New configuration option "DisableDebuggerAttachment" (on by default)
1540 to prevent basic debugging attachment attempts by other processes.
1541 Supports Mac OS X and Gnu/Linux. Resolves ticket 3313.
1542 - Allow MapAddress directives to specify matches against super-domains,
1543 as in "MapAddress *.torproject.org *.torproject.org.torserver.exit".
1544 Implements issue 933.
1545 - Slightly change behavior of "list" options (that is, config
1546 options that can appear more than once) when they appear both in
1547 torrc and on the command line. Previously, the command-line options
1548 would be appended to the ones from torrc. Now, the command-line
1549 options override the torrc options entirely. This new behavior
1550 allows the user to override list options (like exit policies and
1551 ports to listen on) from the command line, rather than simply
1552 appending to the list.
1553 - You can get the old (appending) command-line behavior for "list"
1554 options by prefixing the option name with a "+".
1555 - You can remove all the values for a "list" option from the command
1556 line without adding any new ones by prefixing the option name
1558 - Add experimental support for a "defaults" torrc file to be parsed
1559 before the regular torrc. Torrc options override the defaults file's
1560 options in the same way that the command line overrides the torrc.
1561 The SAVECONF controller command saves only those options which
1562 differ between the current configuration and the defaults file. HUP
1563 reloads both files. (Note: This is an experimental feature; its
1564 behavior will probably be refined in future 0.2.3.x-alpha versions
1565 to better meet packagers' needs.) Implements task 4552.
1568 - Try to make the introductory warning message that Tor prints on
1569 startup more useful for actually finding help and information.
1570 Resolves ticket 2474.
1571 - Running "make version" now displays the version of Tor that
1572 we're about to build. Idea from katmagic; resolves issue 4400.
1573 - Expire old or over-used hidden service introduction points.
1574 Required by fix for bug 3460.
1575 - Move the replay-detection cache for the RSA-encrypted parts of
1576 INTRODUCE2 cells to the introduction point data structures.
1577 Previously, we would use one replay-detection cache per hidden
1578 service. Required by fix for bug 3460.
1579 - Reduce the lifetime of elements of hidden services' Diffie-Hellman
1580 public key replay-detection cache from 60 minutes to 5 minutes. This
1581 replay-detection cache is now used only to detect multiple
1582 INTRODUCE2 cells specifying the same rendezvous point, so we can
1583 avoid launching multiple simultaneous attempts to connect to it.
1585 o Minor bugfixes (on Tor 0.2.2.x and earlier):
1586 - Resolve an integer overflow bug in smartlist_ensure_capacity().
1587 Fixes bug 4230; bugfix on Tor 0.1.0.1-rc. Based on a patch by
1589 - Fix a minor formatting issue in one of tor-gencert's error messages.
1591 - Prevent a false positive from the check-spaces script, by disabling
1592 the "whitespace between function name and (" check for functions
1594 - Fix a log message suggesting that people contact a non-existent
1595 email address. Fixes bug 3448.
1596 - Fix null-pointer access that could occur if TLS allocation failed.
1597 Fixes bug 4531; bugfix on 0.2.0.20-rc. Found by "troll_un".
1598 - Report a real bootstrap problem to the controller on router
1599 identity mismatch. Previously we just said "foo", which probably
1600 made a lot of sense at the time. Fixes bug 4169; bugfix on
1602 - If we had ever tried to call tor_addr_to_str() on an address of
1603 unknown type, we would have done a strdup() on an uninitialized
1604 buffer. Now we won't. Fixes bug 4529; bugfix on 0.2.1.3-alpha.
1605 Reported by "troll_un".
1606 - Correctly detect and handle transient lookup failures from
1607 tor_addr_lookup(). Fixes bug 4530; bugfix on 0.2.1.5-alpha.
1608 Reported by "troll_un".
1609 - Use tor_socket_t type for listener argument to accept(). Fixes bug
1610 4535; bugfix on 0.2.2.28-beta. Found by "troll_un".
1611 - Initialize conn->addr to a valid state in spawn_cpuworker(). Fixes
1612 bug 4532; found by "troll_un".
1614 o Minor bugfixes (on Tor 0.2.3.x):
1615 - Fix a compile warning in tor_inet_pton(). Bugfix on 0.2.3.8-alpha;
1617 - Don't send two ESTABLISH_RENDEZVOUS cells when opening a new
1618 circuit for use as a hidden service client's rendezvous point.
1619 Fixes bugs 4641 and 4171; bugfix on 0.2.3.3-alpha. Diagnosed
1620 with help from wanoskarnet.
1621 - Restore behavior of overriding SocksPort, ORPort, and similar
1622 options from the command line. Bugfix on 0.2.3.3-alpha.
1625 - Properly handle the case where the build-tree is not the same
1626 as the source tree when generating src/common/common_sha1.i,
1627 src/or/micro-revision.i, and src/or/or_sha1.i. Fixes bug 3953;
1628 bugfix on 0.2.0.1-alpha.
1630 o Code simplifications, cleanups, and refactorings:
1631 - Remove the pure attribute from all functions that used it
1632 previously. In many cases we assigned it incorrectly, because the
1633 functions might assert or call impure functions, and we don't have
1634 evidence that keeping the pure attribute is worthwhile. Implements
1635 changes suggested in ticket 4421.
1636 - Remove some dead code spotted by coverity. Fixes cid 432.
1637 Bugfix on 0.2.3.1-alpha, closes bug 4637.
1640 Changes in version 0.2.3.8-alpha - 2011-11-22
1641 Tor 0.2.3.8-alpha fixes some crash and assert bugs, including a
1642 socketpair-related bug that has been bothering Windows users. It adds
1643 support to serve microdescriptors to controllers, so Vidalia's network
1644 map can resume listing relays (once Vidalia implements its side),
1645 and adds better support for hardware AES acceleration. Finally, it
1646 starts the process of adjusting the bandwidth cutoff for getting the
1647 "Fast" flag from 20KB to (currently) 32KB -- preliminary results show
1648 that tiny relays harm performance more than they help network capacity.
1651 - Initialize Libevent with the EVENT_BASE_FLAG_NOLOCK flag enabled, so
1652 that it doesn't attempt to allocate a socketpair. This could cause
1653 some problems on Windows systems with overzealous firewalls. Fix for
1654 bug 4457; workaround for Libevent versions 2.0.1-alpha through
1656 - Correctly sanity-check that we don't underflow on a memory
1657 allocation (and then assert) for hidden service introduction
1658 point decryption. Bug discovered by Dan Rosenberg. Fixes bug 4410;
1659 bugfix on 0.2.1.5-alpha.
1660 - Remove the artificially low cutoff of 20KB to guarantee the Fast
1661 flag. In the past few years the average relay speed has picked
1662 up, and while the "top 7/8 of the network get the Fast flag" and
1663 "all relays with 20KB or more of capacity get the Fast flag" rules
1664 used to have the same result, now the top 7/8 of the network has
1665 a capacity more like 32KB. Bugfix on 0.2.1.14-rc. Fixes bug 4489.
1666 - Fix a rare assertion failure when checking whether a v0 hidden
1667 service descriptor has any usable introduction points left, and
1668 we don't have enough information to build a circuit to the first
1669 intro point named in the descriptor. The HS client code in
1670 0.2.3.x no longer uses v0 HS descriptors, but this assertion can
1671 trigger on (and crash) v0 HS authorities. Fixes bug 4411.
1672 Bugfix on 0.2.3.1-alpha; diagnosed by frosty_un.
1673 - Make bridge authorities not crash when they are asked for their own
1674 descriptor. Bugfix on 0.2.3.7-alpha, reported by Lucky Green.
1675 - When running as a client, do not print a misleading (and plain
1676 wrong) log message that we're collecting "directory request"
1677 statistics: clients don't collect statistics. Also don't create a
1678 useless (because empty) stats file in the stats/ directory. Fixes
1679 bug 4353; bugfix on 0.2.2.34 and 0.2.3.7-alpha.
1682 - Allow Tor controllers like Vidalia to obtain the microdescriptor
1683 for a relay by identity digest or nickname. Previously,
1684 microdescriptors were only available by their own digests, so a
1685 controller would have to ask for and parse the whole microdescriptor
1686 consensus in order to look up a single relay's microdesc. Fixes
1687 bug 3832; bugfix on 0.2.3.1-alpha.
1688 - Use OpenSSL's EVP interface for AES encryption, so that all AES
1689 operations can use hardware acceleration (if present). Resolves
1692 o Minor bugfixes (on 0.2.2.x and earlier):
1693 - Detect failure to initialize Libevent. This fix provides better
1694 detection for future instances of bug 4457.
1695 - Avoid frequent calls to the fairly expensive cull_wedged_cpuworkers
1696 function. This was eating up hideously large amounts of time on some
1697 busy servers. Fixes bug 4518; bugfix on 0.0.9.8.
1698 - Don't warn about unused log_mutex in log.c when building with
1699 --disable-threads using a recent GCC. Fixes bug 4437; bugfix on
1700 0.1.0.6-rc which introduced --disable-threads.
1701 - Allow manual 'authenticate' commands to the controller interface
1702 from netcat (nc) as well as telnet. We were rejecting them because
1703 they didn't come with the expected whitespace at the end of the
1704 command. Bugfix on 0.1.1.1-alpha; fixes bug 2893.
1705 - Fix some (not actually triggerable) buffer size checks in usage of
1706 tor_inet_ntop. Fixes bug 4434; bugfix on Tor 0.2.0.1-alpha. Patch
1708 - Fix parsing of some corner-cases with tor_inet_pton(). Fixes
1709 bug 4515; bugfix on 0.2.0.1-alpha; fix by Anders Sundman.
1710 - When configuring, starting, or stopping an NT service, stop
1711 immediately after the service configuration attempt has succeeded
1712 or failed. Fixes bug 3963; bugfix on 0.2.0.7-alpha.
1713 - When sending a NETINFO cell, include the original address
1714 received for the other side, not its canonical address. Found
1715 by "troll_un"; fixes bug 4349; bugfix on 0.2.0.10-alpha.
1716 - Rename the bench_{aes,dmap} functions to test_*, so that tinytest
1717 can pick them up when the tests aren't disabled. Bugfix on
1718 0.2.2.4-alpha which introduced tinytest.
1719 - Fix a memory leak when we check whether a hidden service
1720 descriptor has any usable introduction points left. Fixes bug
1721 4424. Bugfix on 0.2.2.25-alpha.
1722 - Fix a memory leak in launch_direct_bridge_descriptor_fetch() that
1723 occurred when a client tried to fetch a descriptor for a bridge
1724 in ExcludeNodes. Fixes bug 4383; bugfix on 0.2.2.25-alpha.
1726 o Minor bugfixes (on 0.2.3.x):
1727 - Make util unit tests build correctly with MSVC. Bugfix on
1728 0.2.3.3-alpha. Patch by Gisle Vanem.
1729 - Successfully detect AUTH_CHALLENGE cells with no recognized
1730 authentication type listed. Fixes bug 4367; bugfix on 0.2.3.6-alpha.
1732 - If a relay receives an AUTH_CHALLENGE cell it can't answer,
1733 it should still send a NETINFO cell to allow the connection to
1734 become open. Fixes bug 4368; fix on 0.2.3.6-alpha; bug found by
1736 - Log less loudly when we get an invalid authentication certificate
1737 from a source other than a directory authority: it's not unusual
1738 to see invalid certs because of clock skew. Fixes bug 4370; bugfix
1740 - Tolerate servers with more clock skew in their authentication
1741 certificates than previously. Fixes bug 4371; bugfix on
1743 - Fix a couple of compile warnings on Windows. Fixes bug 4469; bugfix
1744 on 0.2.3.4-alpha and 0.2.3.6-alpha.
1747 - Add two new config options for directory authorities:
1748 AuthDirFastGuarantee sets a bandwidth threshold for guaranteeing the
1749 Fast flag, and AuthDirGuardBWGuarantee sets a bandwidth threshold
1750 that is always sufficient to satisfy the bandwidth requirement for
1751 the Guard flag. Now it will be easier for researchers to simulate
1752 Tor networks with different values. Resolves ticket 4484.
1753 - When Tor ignores a hidden service specified in its configuration,
1754 include the hidden service's directory in the warning message.
1755 Previously, we would only tell the user that some hidden service
1756 was ignored. Bugfix on 0.0.6; fixes bug 4426.
1757 - When we fail to initialize Libevent, retry with IOCP disabled so we
1758 don't need to turn on multi-threading support in Libevent, which in
1759 turn requires a working socketpair(). This is a workaround for bug
1760 4457, which affects Libevent versions from 2.0.1-alpha through
1762 - Detect when we try to build on a platform that doesn't define
1763 AF_UNSPEC to 0. We don't work there, so refuse to compile.
1764 - Update to the November 1 2011 Maxmind GeoLite Country database.
1766 o Packaging changes:
1767 - Make it easier to automate expert package builds on Windows,
1768 by removing an absolute path from makensis.exe command.
1770 o Code simplifications and refactoring:
1771 - Remove some redundant #include directives throughout the code.
1772 Patch from Andrea Gelmini.
1773 - Unconditionally use OpenSSL's AES implementation instead of our
1774 old built-in one. OpenSSL's AES has been better for a while, and
1775 relatively few servers should still be on any version of OpenSSL
1776 that doesn't have good optimized assembly AES.
1777 - Use the name "CERTS" consistently to refer to the new cell type;
1778 we were calling it CERT in some places and CERTS in others.
1781 - Numerous new unit tests for functions in util.c and address.c by
1783 - The long-disabled benchmark tests are now split into their own
1784 ./src/test/bench binary.
1785 - The benchmark tests can now use more accurate timers than
1786 gettimeofday() when such timers are available.
1789 Changes in version 0.2.3.7-alpha - 2011-10-30
1790 Tor 0.2.3.7-alpha fixes a crash bug in 0.2.3.6-alpha introduced by
1791 the new v3 handshake. It also resolves yet another bridge address
1795 - If we mark an OR connection for close based on a cell we process,
1796 don't process any further cells on it. We already avoid further
1797 reads on marked-for-close connections, but now we also discard the
1798 cells we'd already read. Fixes bug 4299; bugfix on 0.2.0.10-alpha,
1799 which was the first version where we might mark a connection for
1800 close based on processing a cell on it.
1801 - Fix a double-free bug that would occur when we received an invalid
1802 certificate in a CERT cell in the new v3 handshake. Fixes bug 4343;
1803 bugfix on 0.2.3.6-alpha.
1804 - Bridges no longer include their address in NETINFO cells on outgoing
1805 OR connections, to allow them to blend in better with clients.
1806 Removes another avenue for enumerating bridges. Reported by
1807 "troll_un". Fixes bug 4348; bugfix on 0.2.0.10-alpha, when NETINFO
1808 cells were introduced.
1811 - Fixed a typo in a hibernation-related log message. Fixes bug 4331;
1812 bugfix on 0.2.2.23-alpha; found by "tmpname0901".
1815 Changes in version 0.2.3.6-alpha - 2011-10-26
1816 Tor 0.2.3.6-alpha includes the fix from 0.2.2.34 for a critical
1817 anonymity vulnerability where an attacker can deanonymize Tor
1818 users. Everybody should upgrade.
1820 This release also features support for a new v3 connection handshake
1821 protocol, and fixes to make hidden service connections more robust.
1824 - Implement a new handshake protocol (v3) for authenticating Tors to
1825 each other over TLS. It should be more resistant to fingerprinting
1826 than previous protocols, and should require less TLS hacking for
1827 future Tor implementations. Implements proposal 176.
1828 - Allow variable-length padding cells to disguise the length of
1829 Tor's TLS records. Implements part of proposal 184.
1831 o Privacy/anonymity fixes (clients):
1832 - Clients and bridges no longer send TLS certificate chains on
1833 outgoing OR connections. Previously, each client or bridge would
1834 use the same cert chain for all outgoing OR connections until
1835 its IP address changes, which allowed any relay that the client
1836 or bridge contacted to determine which entry guards it is using.
1837 Fixes CVE-2011-2768. Bugfix on 0.0.9pre5; found by "frosty_un".
1838 - If a relay receives a CREATE_FAST cell on a TLS connection, it
1839 no longer considers that connection as suitable for satisfying a
1840 circuit EXTEND request. Now relays can protect clients from the
1841 CVE-2011-2768 issue even if the clients haven't upgraded yet.
1842 - Directory authorities no longer assign the Guard flag to relays
1843 that haven't upgraded to the above "refuse EXTEND requests
1844 to client connections" fix. Now directory authorities can
1845 protect clients from the CVE-2011-2768 issue even if neither
1846 the clients nor the relays have upgraded yet. There's a new
1847 "GiveGuardFlagTo_CVE_2011_2768_VulnerableRelays" config option
1848 to let us transition smoothly, else tomorrow there would be no
1851 o Major bugfixes (hidden services):
1852 - Improve hidden service robustness: when an attempt to connect to
1853 a hidden service ends, be willing to refetch its hidden service
1854 descriptors from each of the HSDir relays responsible for them
1855 immediately. Previously, we would not consider refetching the
1856 service's descriptors from each HSDir for 15 minutes after the last
1857 fetch, which was inconvenient if the hidden service was not running
1858 during the first attempt. Bugfix on 0.2.0.18-alpha; fixes bug 3335.
1859 - When one of a hidden service's introduction points appears to be
1860 unreachable, stop trying it. Previously, we would keep trying
1861 to build circuits to the introduction point until we lost the
1862 descriptor, usually because the user gave up and restarted Tor.
1863 Partly fixes bug 3825.
1864 - Don't launch a useless circuit after failing to use one of a
1865 hidden service's introduction points. Previously, we would
1866 launch a new introduction circuit, but not set the hidden service
1867 which that circuit was intended to connect to, so it would never
1868 actually be used. A different piece of code would then create a
1869 new introduction circuit correctly. Bug reported by katmagic and
1870 found by Sebastian Hahn. Bugfix on 0.2.1.13-alpha; fixes bug 4212.
1872 o Major bugfixes (other):
1873 - Bridges now refuse CREATE or CREATE_FAST cells on OR connections
1874 that they initiated. Relays could distinguish incoming bridge
1875 connections from client connections, creating another avenue for
1876 enumerating bridges. Fixes CVE-2011-2769. Bugfix on 0.2.0.3-alpha.
1877 Found by "frosty_un".
1878 - Don't update the AccountingSoftLimitHitAt state file entry whenever
1879 tor gets started. This prevents a wrong average bandwidth
1880 estimate, which would cause relays to always start a new accounting
1881 interval at the earliest possible moment. Fixes bug 2003; bugfix
1882 on 0.2.2.7-alpha. Reported by BryonEldridge, who also helped
1883 immensely in tracking this bug down.
1884 - Fix a crash bug when changing node restrictions while a DNS lookup
1885 is in-progress. Fixes bug 4259; bugfix on 0.2.2.25-alpha. Bugfix
1888 o Minor bugfixes (on 0.2.2.x and earlier):
1889 - When a hidden service turns an extra service-side introduction
1890 circuit into a general-purpose circuit, free the rend_data and
1891 intro_key fields first, so we won't leak memory if the circuit
1892 is cannibalized for use as another service-side introduction
1893 circuit. Bugfix on 0.2.1.7-alpha; fixes bug 4251.
1894 - Rephrase the log message emitted if the TestSocks check is
1895 successful. Patch from Fabian Keil; fixes bug 4094.
1896 - Bridges now skip DNS self-tests, to act a little more stealthily.
1897 Fixes bug 4201; bugfix on 0.2.0.3-alpha, which first introduced
1898 bridges. Patch by "warms0x".
1899 - Remove a confusing dollar sign from the example fingerprint in the
1900 man page, and also make the example fingerprint a valid one. Fixes
1901 bug 4309; bugfix on 0.2.1.3-alpha.
1902 - Fix internal bug-checking logic that was supposed to catch
1903 failures in digest generation so that it will fail more robustly
1904 if we ask for a nonexistent algorithm. Found by Coverity Scan.
1905 Bugfix on 0.2.2.1-alpha; fixes Coverity CID 479.
1906 - Report any failure in init_keys() calls launched because our
1907 IP address has changed. Spotted by Coverity Scan. Bugfix on
1908 0.1.1.4-alpha; fixes CID 484.
1910 o Minor bugfixes (on 0.2.3.x):
1911 - Fix a bug in configure.in that kept it from building a configure
1912 script with autoconf versions earlier than 2.61. Fixes bug 2430;
1913 bugfix on 0.2.3.1-alpha.
1914 - Don't warn users that they are exposing a client port to the
1915 Internet if they have specified an RFC1918 address. Previously,
1916 we would warn if the user had specified any non-loopback
1917 address. Bugfix on 0.2.3.3-alpha. Fixes bug 4018; reported by Tas.
1918 - Fix memory leaks in the failing cases of the new SocksPort and
1919 ControlPort code. Found by Coverity Scan. Bugfix on 0.2.3.3-alpha;
1920 fixes coverity CIDs 485, 486, and 487.
1923 - When a hidden service's introduction point times out, consider
1924 trying it again during the next attempt to connect to the
1925 HS. Previously, we would not try it again unless a newly fetched
1926 descriptor contained it. Required by fixes for bugs 1297 and 3825.
1927 - The next version of Windows will be called Windows 8, and it has
1928 a major version of 6, minor version of 2. Correctly identify that
1929 version instead of calling it "Very recent version". Resolves
1930 ticket 4153; reported by funkstar.
1931 - The Bridge Authority now writes statistics on how many bridge
1932 descriptors it gave out in total, and how many unique descriptors
1933 it gave out. It also lists how often the most and least commonly
1934 fetched descriptors were given out, as well as the median and
1935 25th/75th percentile. Implements tickets 4200 and 4294.
1936 - Update to the October 4 2011 Maxmind GeoLite Country database.
1938 o Code simplifications and refactoring:
1939 - Remove some old code to remember statistics about which descriptors
1940 we've served as a directory mirror. The feature wasn't used and
1941 is outdated now that microdescriptors are around.
1942 - Rename Tor functions that turn strings into addresses, so that
1943 "parse" indicates that no hostname resolution occurs, and
1944 "lookup" indicates that hostname resolution may occur. This
1945 should help prevent mistakes in the future. Fixes bug 3512.
1948 Changes in version 0.2.2.34 - 2011-10-26
1949 Tor 0.2.2.34 fixes a critical anonymity vulnerability where an attacker
1950 can deanonymize Tor users. Everybody should upgrade.
1952 The attack relies on four components: 1) Clients reuse their TLS cert
1953 when talking to different relays, so relays can recognize a user by
1954 the identity key in her cert. 2) An attacker who knows the client's
1955 identity key can probe each guard relay to see if that identity key
1956 is connected to that guard relay right now. 3) A variety of active
1957 attacks in the literature (starting from "Low-Cost Traffic Analysis
1958 of Tor" by Murdoch and Danezis in 2005) allow a malicious website to
1959 discover the guard relays that a Tor user visiting the website is using.
1960 4) Clients typically pick three guards at random, so the set of guards
1961 for a given user could well be a unique fingerprint for her. This
1962 release fixes components #1 and #2, which is enough to block the attack;
1963 the other two remain as open research problems. Special thanks to
1964 "frosty_un" for reporting the issue to us!
1966 Clients should upgrade so they are no longer recognizable by the TLS
1967 certs they present. Relays should upgrade so they no longer allow a
1968 remote attacker to probe them to test whether unpatched clients are
1969 currently connected to them.
1971 This release also fixes several vulnerabilities that allow an attacker
1972 to enumerate bridge relays. Some bridge enumeration attacks still
1973 remain; see for example proposal 188.
1975 o Privacy/anonymity fixes (clients):
1976 - Clients and bridges no longer send TLS certificate chains on
1977 outgoing OR connections. Previously, each client or bridge would
1978 use the same cert chain for all outgoing OR connections until
1979 its IP address changes, which allowed any relay that the client
1980 or bridge contacted to determine which entry guards it is using.
1981 Fixes CVE-2011-2768. Bugfix on 0.0.9pre5; found by "frosty_un".
1982 - If a relay receives a CREATE_FAST cell on a TLS connection, it
1983 no longer considers that connection as suitable for satisfying a
1984 circuit EXTEND request. Now relays can protect clients from the
1985 CVE-2011-2768 issue even if the clients haven't upgraded yet.
1986 - Directory authorities no longer assign the Guard flag to relays
1987 that haven't upgraded to the above "refuse EXTEND requests
1988 to client connections" fix. Now directory authorities can
1989 protect clients from the CVE-2011-2768 issue even if neither
1990 the clients nor the relays have upgraded yet. There's a new
1991 "GiveGuardFlagTo_CVE_2011_2768_VulnerableRelays" config option
1992 to let us transition smoothly, else tomorrow there would be no
1995 o Privacy/anonymity fixes (bridge enumeration):
1996 - Bridge relays now do their directory fetches inside Tor TLS
1997 connections, like all the other clients do, rather than connecting
1998 directly to the DirPort like public relays do. Removes another
1999 avenue for enumerating bridges. Fixes bug 4115; bugfix on 0.2.0.35.
2000 - Bridges relays now build circuits for themselves in a more similar
2001 way to how clients build them. Removes another avenue for
2002 enumerating bridges. Fixes bug 4124; bugfix on 0.2.0.3-alpha,
2003 when bridges were introduced.
2004 - Bridges now refuse CREATE or CREATE_FAST cells on OR connections
2005 that they initiated. Relays could distinguish incoming bridge
2006 connections from client connections, creating another avenue for
2007 enumerating bridges. Fixes CVE-2011-2769. Bugfix on 0.2.0.3-alpha.
2008 Found by "frosty_un".
2011 - Fix a crash bug when changing node restrictions while a DNS lookup
2012 is in-progress. Fixes bug 4259; bugfix on 0.2.2.25-alpha. Bugfix
2014 - Don't launch a useless circuit after failing to use one of a
2015 hidden service's introduction points. Previously, we would
2016 launch a new introduction circuit, but not set the hidden service
2017 which that circuit was intended to connect to, so it would never
2018 actually be used. A different piece of code would then create a
2019 new introduction circuit correctly. Bug reported by katmagic and
2020 found by Sebastian Hahn. Bugfix on 0.2.1.13-alpha; fixes bug 4212.
2023 - Change an integer overflow check in the OpenBSD_Malloc code so
2024 that GCC is less likely to eliminate it as impossible. Patch
2025 from Mansour Moufid. Fixes bug 4059.
2026 - When a hidden service turns an extra service-side introduction
2027 circuit into a general-purpose circuit, free the rend_data and
2028 intro_key fields first, so we won't leak memory if the circuit
2029 is cannibalized for use as another service-side introduction
2030 circuit. Bugfix on 0.2.1.7-alpha; fixes bug 4251.
2031 - Bridges now skip DNS self-tests, to act a little more stealthily.
2032 Fixes bug 4201; bugfix on 0.2.0.3-alpha, which first introduced
2033 bridges. Patch by "warms0x".
2034 - Fix internal bug-checking logic that was supposed to catch
2035 failures in digest generation so that it will fail more robustly
2036 if we ask for a nonexistent algorithm. Found by Coverity Scan.
2037 Bugfix on 0.2.2.1-alpha; fixes Coverity CID 479.
2038 - Report any failure in init_keys() calls launched because our
2039 IP address has changed. Spotted by Coverity Scan. Bugfix on
2040 0.1.1.4-alpha; fixes CID 484.
2042 o Minor bugfixes (log messages and documentation):
2043 - Remove a confusing dollar sign from the example fingerprint in the
2044 man page, and also make the example fingerprint a valid one. Fixes
2045 bug 4309; bugfix on 0.2.1.3-alpha.
2046 - The next version of Windows will be called Windows 8, and it has
2047 a major version of 6, minor version of 2. Correctly identify that
2048 version instead of calling it "Very recent version". Resolves
2049 ticket 4153; reported by funkstar.
2050 - Downgrade log messages about circuit timeout calibration from
2051 "notice" to "info": they don't require or suggest any human
2052 intervention. Patch from Tom Lowenthal. Fixes bug 4063;
2053 bugfix on 0.2.2.14-alpha.
2056 - Turn on directory request statistics by default and include them in
2057 extra-info descriptors. Don't break if we have no GeoIP database.
2058 Backported from 0.2.3.1-alpha; implements ticket 3951.
2059 - Update to the October 4 2011 Maxmind GeoLite Country database.
2062 Changes in version 0.2.1.31 - 2011-10-26
2063 Tor 0.2.1.31 backports important security and privacy fixes for
2064 oldstable. This release is intended only for package maintainers and
2065 others who cannot use the 0.2.2 stable series. All others should be
2066 using Tor 0.2.2.x or newer.
2068 o Security fixes (also included in 0.2.2.x):
2069 - Replace all potentially sensitive memory comparison operations
2070 with versions whose runtime does not depend on the data being
2071 compared. This will help resist a class of attacks where an
2072 adversary can use variations in timing information to learn
2073 sensitive data. Fix for one case of bug 3122. (Safe memcmp
2074 implementation by Robert Ransom based partially on code by DJB.)
2075 - Fix an assert in parsing router descriptors containing IPv6
2076 addresses. This one took down the directory authorities when
2077 somebody tried some experimental code. Bugfix on 0.2.1.3-alpha.
2079 o Privacy/anonymity fixes (also included in 0.2.2.x):
2080 - Clients and bridges no longer send TLS certificate chains on
2081 outgoing OR connections. Previously, each client or bridge would
2082 use the same cert chain for all outgoing OR connections until
2083 its IP address changes, which allowed any relay that the client
2084 or bridge contacted to determine which entry guards it is using.
2085 Fixes CVE-2011-2768. Bugfix on 0.0.9pre5; found by "frosty_un".
2086 - If a relay receives a CREATE_FAST cell on a TLS connection, it
2087 no longer considers that connection as suitable for satisfying a
2088 circuit EXTEND request. Now relays can protect clients from the
2089 CVE-2011-2768 issue even if the clients haven't upgraded yet.
2090 - Bridges now refuse CREATE or CREATE_FAST cells on OR connections
2091 that they initiated. Relays could distinguish incoming bridge
2092 connections from client connections, creating another avenue for
2093 enumerating bridges. Fixes CVE-2011-2769. Bugfix on 0.2.0.3-alpha.
2094 Found by "frosty_un".
2095 - When receiving a hidden service descriptor, check that it is for
2096 the hidden service we wanted. Previously, Tor would store any
2097 hidden service descriptors that a directory gave it, whether it
2098 wanted them or not. This wouldn't have let an attacker impersonate
2099 a hidden service, but it did let directories pre-seed a client
2100 with descriptors that it didn't want. Bugfix on 0.0.6.
2101 - Avoid linkability based on cached hidden service descriptors: forget
2102 all hidden service descriptors cached as a client when processing a
2103 SIGNAL NEWNYM command. Fixes bug 3000; bugfix on 0.0.6.
2104 - Make the bridge directory authority refuse to answer directory
2105 requests for "all" descriptors. It used to include bridge
2106 descriptors in its answer, which was a major information leak.
2107 Found by "piebeer". Bugfix on 0.2.0.3-alpha.
2108 - Don't attach new streams to old rendezvous circuits after SIGNAL
2109 NEWNYM. Previously, we would keep using an existing rendezvous
2110 circuit if it remained open (i.e. if it were kept open by a
2111 long-lived stream, or if a new stream were attached to it before
2112 Tor could notice that it was old and no longer in use). Bugfix on
2113 0.1.1.15-rc; fixes bug 3375.
2115 o Minor bugfixes (also included in 0.2.2.x):
2116 - When we restart our relay, we might get a successful connection
2117 from the outside before we've started our reachability tests,
2118 triggering a warning: "ORPort found reachable, but I have no
2119 routerinfo yet. Failing to inform controller of success." This
2120 bug was harmless unless Tor is running under a controller
2121 like Vidalia, in which case the controller would never get a
2122 REACHABILITY_SUCCEEDED status event. Bugfix on 0.1.2.6-alpha;
2124 - Build correctly on OSX with zlib 1.2.4 and higher with all warnings
2125 enabled. Fixes bug 1526.
2126 - Remove undocumented option "-F" from tor-resolve: it hasn't done
2127 anything since 0.2.1.16-rc.
2128 - Avoid signed/unsigned comparisons by making SIZE_T_CEILING unsigned.
2129 None of the cases where we did this before were wrong, but by making
2130 this change we avoid warnings. Fixes bug 2475; bugfix on 0.2.1.28.
2131 - Fix a rare crash bug that could occur when a client was configured
2132 with a large number of bridges. Fixes bug 2629; bugfix on
2133 0.2.1.2-alpha. Bugfix by trac user "shitlei".
2134 - Correct the warning displayed when a rendezvous descriptor exceeds
2135 the maximum size. Fixes bug 2750; bugfix on 0.2.1.5-alpha. Found by
2137 - Fix an uncommon assertion failure when running with DNSPort under
2138 heavy load. Fixes bug 2933; bugfix on 0.2.0.1-alpha.
2139 - When warning about missing zlib development packages during compile,
2140 give the correct package names. Bugfix on 0.2.0.1-alpha.
2141 - Require that introduction point keys and onion keys have public
2142 exponent 65537. Bugfix on 0.2.0.10-alpha.
2143 - Do not crash when our configuration file becomes unreadable, for
2144 example due to a permissions change, between when we start up
2145 and when a controller calls SAVECONF. Fixes bug 3135; bugfix
2147 - Fix warnings from GCC 4.6's "-Wunused-but-set-variable" option.
2149 - Always NUL-terminate the sun_path field of a sockaddr_un before
2150 passing it to the kernel. (Not a security issue: kernels are
2151 smart enough to reject bad sockaddr_uns.) Found by Coverity;
2152 CID #428. Bugfix on Tor 0.2.0.3-alpha.
2153 - Don't stack-allocate the list of supplementary GIDs when we're
2154 about to log them. Stack-allocating NGROUPS_MAX gid_t elements
2155 could take up to 256K, which is way too much stack. Found by
2156 Coverity; CID #450. Bugfix on 0.2.1.7-alpha.
2158 o Minor bugfixes (only in 0.2.1.x):
2159 - Resume using micro-version numbers in 0.2.1.x: our Debian packages
2160 rely on them. Bugfix on 0.2.1.30.
2161 - Use git revisions instead of svn revisions when generating our
2162 micro-version numbers. Bugfix on 0.2.1.15-rc; fixes bug 2402.
2164 o Minor features (also included in 0.2.2.x):
2165 - Adjust the expiration time on our SSL session certificates to
2166 better match SSL certs seen in the wild. Resolves ticket 4014.
2167 - Allow nameservers with IPv6 address. Resolves bug 2574.
2168 - Update to the October 4 2011 Maxmind GeoLite Country database.
2171 Changes in version 0.2.3.5-alpha - 2011-09-28
2172 Tor 0.2.3.5-alpha fixes two bugs that make it possible to enumerate
2173 bridge relays; fixes an assertion error that many users started hitting
2174 today; and adds the ability to refill token buckets more often than
2175 once per second, allowing significant performance improvements.
2178 - Bridge relays now do their directory fetches inside Tor TLS
2179 connections, like all the other clients do, rather than connecting
2180 directly to the DirPort like public relays do. Removes another
2181 avenue for enumerating bridges. Fixes bug 4115; bugfix on 0.2.0.35.
2182 - Bridges relays now build circuits for themselves in a more similar
2183 way to how clients build them. Removes another avenue for
2184 enumerating bridges. Fixes bug 4124; bugfix on 0.2.0.3-alpha,
2185 when bridges were introduced.
2188 - Fix an "Assertion md->held_by_node == 1 failed" error that could
2189 occur when the same microdescriptor was referenced by two node_t
2190 objects at once. Fix for bug 4118; bugfix on Tor 0.2.3.1-alpha.
2192 o Major features (networking):
2193 - Add a new TokenBucketRefillInterval option to refill token buckets
2194 more frequently than once per second. This should improve network
2195 performance, alleviate queueing problems, and make traffic less
2196 bursty. Implements proposal 183; closes ticket 3630. Design by
2197 Florian Tschorsch and Björn Scheuermann; implementation by
2201 - Change an integer overflow check in the OpenBSD_Malloc code so
2202 that GCC is less likely to eliminate it as impossible. Patch
2203 from Mansour Moufid. Fixes bug 4059.
2205 o Minor bugfixes (usability):
2206 - Downgrade log messages about circuit timeout calibration from
2207 "notice" to "info": they don't require or suggest any human
2208 intervention. Patch from Tom Lowenthal. Fixes bug 4063;
2209 bugfix on 0.2.2.14-alpha.
2211 o Minor features (diagnostics):
2212 - When the system call to create a listener socket fails, log the
2213 error message explaining why. This may help diagnose bug 4027.
2216 Changes in version 0.2.3.4-alpha - 2011-09-13
2217 Tor 0.2.3.4-alpha includes the fixes from 0.2.2.33, including a slight
2218 tweak to Tor's TLS handshake that makes relays and bridges that run
2219 this new version reachable from Iran again. It also fixes a few new
2220 bugs in 0.2.3.x, and teaches relays to recognize when they're not
2221 listed in the network consensus and republish.
2223 o Major bugfixes (also part of 0.2.2.33):
2224 - Avoid an assertion failure when reloading a configuration with
2225 TrackExitHosts changes. Found and fixed by 'laruldan'. Fixes bug
2226 3923; bugfix on 0.2.2.25-alpha.
2228 o Minor features (security, also part of 0.2.2.33):
2229 - Check for replays of the public-key encrypted portion of an
2230 INTRODUCE1 cell, in addition to the current check for replays of
2231 the g^x value. This prevents a possible class of active attacks
2232 by an attacker who controls both an introduction point and a
2233 rendezvous point, and who uses the malleability of AES-CTR to
2234 alter the encrypted g^x portion of the INTRODUCE1 cell. We think
2235 that these attacks is infeasible (requiring the attacker to send
2236 on the order of zettabytes of altered cells in a short interval),
2237 but we'd rather block them off in case there are any classes of
2238 this attack that we missed. Reported by Willem Pinckaers.
2240 o Minor features (also part of 0.2.2.33):
2241 - Adjust the expiration time on our SSL session certificates to
2242 better match SSL certs seen in the wild. Resolves ticket 4014.
2243 - Change the default required uptime for a relay to be accepted as
2244 a HSDir (hidden service directory) from 24 hours to 25 hours.
2245 Improves on 0.2.0.10-alpha; resolves ticket 2649.
2246 - Add a VoteOnHidServDirectoriesV2 config option to allow directory
2247 authorities to abstain from voting on assignment of the HSDir
2248 consensus flag. Related to bug 2649.
2249 - Update to the September 6 2011 Maxmind GeoLite Country database.
2251 o Minor bugfixes (also part of 0.2.2.33):
2252 - Demote the 'replay detected' log message emitted when a hidden
2253 service receives the same Diffie-Hellman public key in two different
2254 INTRODUCE2 cells to info level. A normal Tor client can cause that
2255 log message during its normal operation. Bugfix on 0.2.1.6-alpha;
2256 fixes part of bug 2442.
2257 - Demote the 'INTRODUCE2 cell is too {old,new}' log message to info
2258 level. There is nothing that a hidden service's operator can do
2259 to fix its clients' clocks. Bugfix on 0.2.1.6-alpha; fixes part
2261 - Clarify a log message specifying the characters permitted in
2262 HiddenServiceAuthorizeClient client names. Previously, the log
2263 message said that "[A-Za-z0-9+-_]" were permitted; that could have
2264 given the impression that every ASCII character between "+" and "_"
2265 was permitted. Now we say "[A-Za-z0-9+_-]". Bugfix on 0.2.1.5-alpha.
2267 o Build fixes (also part of 0.2.2.33):
2268 - Clean up some code issues that prevented Tor from building on older
2269 BSDs. Fixes bug 3894; reported by "grarpamp".
2270 - Search for a platform-specific version of "ar" when cross-compiling.
2271 Should fix builds on iOS. Resolves bug 3909, found by Marco Bonetti.
2274 - Fix a bug where the SocksPort option (for example) would get
2275 ignored and replaced by the default if a SocksListenAddress
2276 option was set. Bugfix on 0.2.3.3-alpha; fixes bug 3936. Fix by
2280 - Relays now try regenerating and uploading their descriptor more
2281 frequently if they are not listed in the consensus, or if the
2282 version of their descriptor listed in the consensus is too
2283 old. This fix should prevent situations where a server declines
2284 to re-publish itself because it has done so too recently, even
2285 though the authorities decided not to list its recent-enough
2286 descriptor. Fix for bug 3327.
2289 - Relays now include a reason for regenerating their descriptors
2290 in an HTTP header when uploading to the authorities. This will
2291 make it easier to debug descriptor-upload issues in the future.
2292 - When starting as root and then changing our UID via the User
2293 control option, and we have a ControlSocket configured, make sure
2294 that the ControlSocket is owned by the same account that Tor will
2295 run under. Implements ticket 3421; fix by Jérémy Bobbio.
2298 - Abort if tor_vasprintf fails in connection_printf_to_buf (a
2299 utility function used in the control-port code). This shouldn't
2300 ever happen unless Tor is completely out of memory, but if it did
2301 happen and Tor somehow recovered from it, Tor could have sent a log
2302 message to a control port in the middle of a reply to a controller
2303 command. Fixes part of bug 3428; bugfix on 0.1.2.3-alpha.
2304 - Make 'FetchUselessDescriptors' cause all descriptor types and
2305 all consensus types (including microdescriptors) to get fetched.
2306 Fixes bug 3851; bugfix on 0.2.3.1-alpha.
2309 - Make a new "entry connection" struct as an internal subtype of "edge
2310 connection", to simplify the code and make exit connections smaller.
2313 Changes in version 0.2.2.33 - 2011-09-13
2314 Tor 0.2.2.33 fixes several bugs, and includes a slight tweak to Tor's
2315 TLS handshake that makes relays and bridges that run this new version
2316 reachable from Iran again.
2319 - Avoid an assertion failure when reloading a configuration with
2320 TrackExitHosts changes. Found and fixed by 'laruldan'. Fixes bug
2321 3923; bugfix on 0.2.2.25-alpha.
2323 o Minor features (security):
2324 - Check for replays of the public-key encrypted portion of an
2325 INTRODUCE1 cell, in addition to the current check for replays of
2326 the g^x value. This prevents a possible class of active attacks
2327 by an attacker who controls both an introduction point and a
2328 rendezvous point, and who uses the malleability of AES-CTR to
2329 alter the encrypted g^x portion of the INTRODUCE1 cell. We think
2330 that these attacks are infeasible (requiring the attacker to send
2331 on the order of zettabytes of altered cells in a short interval),
2332 but we'd rather block them off in case there are any classes of
2333 this attack that we missed. Reported by Willem Pinckaers.
2336 - Adjust the expiration time on our SSL session certificates to
2337 better match SSL certs seen in the wild. Resolves ticket 4014.
2338 - Change the default required uptime for a relay to be accepted as
2339 a HSDir (hidden service directory) from 24 hours to 25 hours.
2340 Improves on 0.2.0.10-alpha; resolves ticket 2649.
2341 - Add a VoteOnHidServDirectoriesV2 config option to allow directory
2342 authorities to abstain from voting on assignment of the HSDir
2343 consensus flag. Related to bug 2649.
2344 - Update to the September 6 2011 Maxmind GeoLite Country database.
2346 o Minor bugfixes (documentation and log messages):
2347 - Correct the man page to explain that HashedControlPassword and
2348 CookieAuthentication can both be set, in which case either method
2349 is sufficient to authenticate to Tor. Bugfix on 0.2.0.7-alpha,
2350 when we decided to allow these config options to both be set. Issue
2352 - Demote the 'replay detected' log message emitted when a hidden
2353 service receives the same Diffie-Hellman public key in two different
2354 INTRODUCE2 cells to info level. A normal Tor client can cause that
2355 log message during its normal operation. Bugfix on 0.2.1.6-alpha;
2356 fixes part of bug 2442.
2357 - Demote the 'INTRODUCE2 cell is too {old,new}' log message to info
2358 level. There is nothing that a hidden service's operator can do
2359 to fix its clients' clocks. Bugfix on 0.2.1.6-alpha; fixes part
2361 - Clarify a log message specifying the characters permitted in
2362 HiddenServiceAuthorizeClient client names. Previously, the log
2363 message said that "[A-Za-z0-9+-_]" were permitted; that could have
2364 given the impression that every ASCII character between "+" and "_"
2365 was permitted. Now we say "[A-Za-z0-9+_-]". Bugfix on 0.2.1.5-alpha.
2368 - Provide a substitute implementation of lround() for MSVC, which
2369 apparently lacks it. Patch from Gisle Vanem.
2370 - Clean up some code issues that prevented Tor from building on older
2371 BSDs. Fixes bug 3894; reported by "grarpamp".
2372 - Search for a platform-specific version of "ar" when cross-compiling.
2373 Should fix builds on iOS. Resolves bug 3909, found by Marco Bonetti.
2376 Changes in version 0.2.3.3-alpha - 2011-09-01
2377 Tor 0.2.3.3-alpha adds a new "stream isolation" feature to improve Tor's
2378 security, and provides client-side support for the microdescriptor
2379 and optimistic data features introduced earlier in the 0.2.3.x
2380 series. It also includes numerous critical bugfixes in the (optional)
2381 bufferevent-based networking backend.
2383 o Major features (stream isolation):
2384 - You can now configure Tor so that streams from different
2385 applications are isolated on different circuits, to prevent an
2386 attacker who sees your streams as they leave an exit node from
2387 linking your sessions to one another. To do this, choose some way
2388 to distinguish the applications: have them connect to different
2389 SocksPorts, or have one of them use SOCKS4 while the other uses
2390 SOCKS5, or have them pass different authentication strings to the
2391 SOCKS proxy. Then, use the new SocksPort syntax to configure the
2392 degree of isolation you need. This implements Proposal 171.
2393 - There's a new syntax for specifying multiple client ports (such as
2394 SOCKSPort, TransPort, DNSPort, NATDPort): you can now just declare
2395 multiple *Port entries with full addr:port syntax on each.
2396 The old *ListenAddress format is still supported, but you can't
2397 mix it with the new *Port syntax.
2399 o Major features (other):
2400 - Enable microdescriptor fetching by default for clients. This allows
2401 clients to download a much smaller amount of directory information.
2402 To disable it (and go back to the old-style consensus and
2403 descriptors), set "UseMicrodescriptors 0" in your torrc file.
2404 - Tor's firewall-helper feature, introduced in 0.2.3.1-alpha (see the
2405 "PortForwarding" config option), now supports Windows.
2406 - When using an exit relay running 0.2.3.x, clients can now
2407 "optimistically" send data before the exit relay reports that
2408 the stream has opened. This saves a round trip when starting
2409 connections where the client speaks first (such as web browsing).
2410 This behavior is controlled by a consensus parameter (currently
2411 disabled). To turn it on or off manually, use the "OptimisticData"
2412 torrc option. Implements proposal 181; code by Ian Goldberg.
2414 o Major bugfixes (bufferevents, fixes on 0.2.3.1-alpha):
2415 - When using IOCP on Windows, we need to enable Libevent windows
2417 - The IOCP backend now works even when the user has not specified
2418 the (internal, debugging-only) _UseFilteringSSLBufferevents option.
2419 Fixes part of bug 3752.
2420 - Correctly record the bytes we've read and written when using
2421 bufferevents, so that we can include them in our bandwidth history
2422 and advertised bandwidth. Fixes bug 3803.
2423 - Apply rate-limiting only at the bottom of a chain of filtering
2424 bufferevents. This prevents us from filling up internal read
2425 buffers and violating rate-limits when filtering bufferevents
2426 are enabled. Fixes part of bug 3804.
2427 - Add high-watermarks to the output buffers for filtered
2428 bufferevents. This prevents us from filling up internal write
2429 buffers and wasting CPU cycles when filtering bufferevents are
2430 enabled. Fixes part of bug 3804.
2431 - Correctly notice when data has been written from a bufferevent
2432 without flushing it completely. Fixes bug 3805.
2433 - Fix a bug where server-side tunneled bufferevent-based directory
2434 streams would get closed prematurely. Fixes bug 3814.
2435 - Fix a use-after-free error with per-connection rate-limiting
2436 buckets. Fixes bug 3888.
2438 o Major bugfixes (also part of 0.2.2.31-rc):
2439 - If we're configured to write our ControlPorts to disk, only write
2440 them after switching UID and creating the data directory. This way,
2441 we don't fail when starting up with a nonexistent DataDirectory
2442 and a ControlPortWriteToFile setting based on that directory. Fixes
2443 bug 3747; bugfix on Tor 0.2.2.26-beta.
2446 - Added a new CONF_CHANGED event so that controllers can be notified
2447 of any configuration changes made by other controllers, or by the
2448 user. Implements ticket 1692.
2449 - Use evbuffer_copyout() in inspect_evbuffer(). This fixes a memory
2450 leak when using bufferevents, and lets Libevent worry about how to
2451 best copy data out of a buffer.
2452 - Replace files in stats/ rather than appending to them. Now that we
2453 include statistics in extra-info descriptors, it makes no sense to
2454 keep old statistics forever. Implements ticket 2930.
2456 o Minor features (build compatibility):
2457 - Limited, experimental support for building with nmake and MSVC.
2458 - Provide a substitute implementation of lround() for MSVC, which
2459 apparently lacks it. Patch from Gisle Vanem.
2461 o Minor features (also part of 0.2.2.31-rc):
2462 - Update to the August 2 2011 Maxmind GeoLite Country database.
2464 o Minor bugfixes (on 0.2.3.x-alpha):
2465 - Fix a spurious warning when parsing SOCKS requests with
2466 bufferevents enabled. Fixes bug 3615; bugfix on 0.2.3.2-alpha.
2467 - Get rid of a harmless warning that could happen on relays running
2468 with bufferevents. The warning was caused by someone doing an http
2469 request to a relay's orport. Also don't warn for a few related
2470 non-errors. Fixes bug 3700; bugfix on 0.2.3.1-alpha.
2472 o Minor bugfixes (on 2.2.x and earlier):
2473 - Correct the man page to explain that HashedControlPassword and
2474 CookieAuthentication can both be set, in which case either method
2475 is sufficient to authenticate to Tor. Bugfix on 0.2.0.7-alpha,
2476 when we decided to allow these config options to both be set. Issue
2478 - The "--quiet" and "--hush" options now apply not only to Tor's
2479 behavior before logs are configured, but also to Tor's behavior in
2480 the absense of configured logs. Fixes bug 3550; bugfix on
2483 o Minor bugfixes (also part of 0.2.2.31-rc):
2484 - Write several files in text mode, on OSes that distinguish text
2485 mode from binary mode (namely, Windows). These files are:
2486 'buffer-stats', 'dirreq-stats', and 'entry-stats' on relays
2487 that collect those statistics; 'client_keys' and 'hostname' for
2488 hidden services that use authentication; and (in the tor-gencert
2489 utility) newly generated identity and signing keys. Previously,
2490 we wouldn't specify text mode or binary mode, leading to an
2491 assertion failure. Fixes bug 3607. Bugfix on 0.2.1.1-alpha (when
2492 the DirRecordUsageByCountry option which would have triggered
2493 the assertion failure was added), although this assertion failure
2494 would have occurred in tor-gencert on Windows in 0.2.0.1-alpha.
2495 - Selectively disable deprecation warnings on OS X because Lion
2496 started deprecating the shipped copy of openssl. Fixes bug 3643.
2497 - Remove an extra pair of quotation marks around the error
2498 message in control-port STATUS_GENERAL BUG events. Bugfix on
2499 0.1.2.6-alpha; fixes bug 3732.
2500 - When unable to format an address as a string, report its value
2501 as "???" rather than reusing the last formatted address. Bugfix
2504 o Code simplifications and refactoring:
2505 - Rewrite the listener-selection logic so that parsing which ports
2506 we want to listen on is now separate from binding to the ports
2510 - Building Tor with bufferevent support now requires Libevent
2511 2.0.13-stable or later. Previous versions of Libevent had bugs in
2512 SSL-related bufferevents and related issues that would make Tor
2513 work badly with bufferevents. Requiring 2.0.13-stable also allows
2514 Tor with bufferevents to take advantage of Libevent APIs
2515 introduced after 2.0.8-rc.
2518 Changes in version 0.2.2.32 - 2011-08-27
2519 The Tor 0.2.2 release series is dedicated to the memory of Andreas
2520 Pfitzmann (1958-2010), a pioneer in anonymity and privacy research,
2521 a founder of the PETS community, a leader in our field, a mentor,
2522 and a friend. He left us with these words: "I had the possibility
2523 to contribute to this world that is not as it should be. I hope I
2524 could help in some areas to make the world a better place, and that
2525 I could also encourage other people to be engaged in improving the
2526 world. Please, stay engaged. This world needs you, your love, your
2527 initiative -- now I cannot be part of that anymore."
2529 Tor 0.2.2.32, the first stable release in the 0.2.2 branch, is finally
2530 ready. More than two years in the making, this release features improved
2531 client performance and hidden service reliability, better compatibility
2532 for Android, correct behavior for bridges that listen on more than
2533 one address, more extensible and flexible directory object handling,
2534 better reporting of network statistics, improved code security, and
2535 many many other features and bugfixes.
2538 Changes in version 0.2.2.31-rc - 2011-08-17
2539 Tor 0.2.2.31-rc is the second and hopefully final release candidate
2540 for the Tor 0.2.2.x series.
2543 - Remove an extra pair of quotation marks around the error
2544 message in control-port STATUS_GENERAL BUG events. Bugfix on
2545 0.1.2.6-alpha; fixes bug 3732.
2546 - If we're configured to write our ControlPorts to disk, only write
2547 them after switching UID and creating the data directory. This way,
2548 we don't fail when starting up with a nonexistent DataDirectory
2549 and a ControlPortWriteToFile setting based on that directory. Fixes
2550 bug 3747; bugfix on Tor 0.2.2.26-beta.
2553 - Update to the August 2 2011 Maxmind GeoLite Country database.
2556 - Allow GETINFO fingerprint to return a fingerprint even when
2557 we have not yet built a router descriptor. Fixes bug 3577;
2558 bugfix on 0.2.0.1-alpha.
2559 - Write several files in text mode, on OSes that distinguish text
2560 mode from binary mode (namely, Windows). These files are:
2561 'buffer-stats', 'dirreq-stats', and 'entry-stats' on relays
2562 that collect those statistics; 'client_keys' and 'hostname' for
2563 hidden services that use authentication; and (in the tor-gencert
2564 utility) newly generated identity and signing keys. Previously,
2565 we wouldn't specify text mode or binary mode, leading to an
2566 assertion failure. Fixes bug 3607. Bugfix on 0.2.1.1-alpha (when
2567 the DirRecordUsageByCountry option which would have triggered
2568 the assertion failure was added), although this assertion failure
2569 would have occurred in tor-gencert on Windows in 0.2.0.1-alpha.
2570 - Selectively disable deprecation warnings on OS X because Lion
2571 started deprecating the shipped copy of openssl. Fixes bug 3643.
2572 - When unable to format an address as a string, report its value
2573 as "???" rather than reusing the last formatted address. Bugfix
2577 Changes in version 0.2.3.2-alpha - 2011-07-18
2578 Tor 0.2.3.2-alpha introduces two new experimental features:
2579 microdescriptors and pluggable transports. It also continues cleaning
2580 up a variety of recently introduced features.
2583 - Clients can now use microdescriptors instead of regular descriptors
2584 to build circuits. Microdescriptors are authority-generated
2585 summaries of regular descriptors' contents, designed to change
2586 very rarely (see proposal 158 for details). This feature is
2587 designed to save bandwidth, especially for clients on slow internet
2588 connections. It's off by default for now, since nearly no caches
2589 support it, but it will be on-by-default for clients in a future
2590 version. You can use the UseMicrodescriptors option to turn it on.
2591 - Tor clients using bridges can now be configured to use a separate
2592 'transport' proxy for each bridge. This approach helps to resist
2593 censorship by allowing bridges to use protocol obfuscation
2594 plugins. It implements part of proposal 180. Implements ticket 2841.
2595 - While we're trying to bootstrap, record how many TLS connections
2596 fail in each state, and report which states saw the most failures
2597 in response to any bootstrap failures. This feature may speed up
2598 diagnosis of censorship events. Implements ticket 3116.
2600 o Major bugfixes (on 0.2.3.1-alpha):
2601 - When configuring a large set of nodes in EntryNodes (as with
2602 'EntryNodes {cc}' or 'EntryNodes 1.1.1.1/16'), choose only a
2603 random subset to be guards, and choose them in random
2604 order. Fixes bug 2798.
2605 - Tor could crash when remembering a consensus in a non-used consensus
2606 flavor without having a current consensus set. Fixes bug 3361.
2607 - Comparing an unknown address to a microdescriptor's shortened exit
2608 policy would always give a "rejected" result. Fixes bug 3599.
2609 - Using microdescriptors as a client no longer prevents Tor from
2610 uploading and downloading hidden service descriptors. Fixes
2614 - Allow nameservers with IPv6 address. Resolves bug 2574.
2615 - Accept attempts to include a password authenticator in the
2616 handshake, as supported by SOCKS5. This handles SOCKS clients that
2617 don't know how to omit a password when authenticating. Resolves
2619 - When configuring a large set of nodes in EntryNodes, and there are
2620 enough of them listed as Guard so that we don't need to consider
2621 the non-guard entries, prefer the ones listed with the Guard flag.
2622 - Check for and recover from inconsistency in the microdescriptor
2623 cache. This will make it harder for us to accidentally free a
2624 microdescriptor without removing it from the appropriate data
2625 structures. Fixes issue 3135; issue noted by "wanoskarnet".
2626 - Log SSL state transitions at log level DEBUG, log domain
2627 HANDSHAKE. This can be useful for debugging censorship events.
2628 Implements ticket 3264.
2629 - Add port 6523 (Gobby) to LongLivedPorts. Patch by intrigeri;
2630 implements ticket 3439.
2632 o Minor bugfixes (on 0.2.3.1-alpha):
2633 - Do not free all general-purpose regular descriptors just
2634 because microdescriptor use is enabled. Fixes bug 3113.
2635 - Correctly link libevent_openssl when --enable-static-libevent
2636 is passed to configure. Fixes bug 3118.
2637 - Bridges should not complain during their heartbeat log messages that
2638 they are unlisted in the consensus: that's more or less the point
2639 of being a bridge. Fixes bug 3183.
2640 - Report a SIGNAL event to controllers when acting on a delayed
2641 SIGNAL NEWNYM command. Previously, we would report a SIGNAL
2642 event to the controller if we acted on a SIGNAL NEWNYM command
2643 immediately, and otherwise not report a SIGNAL event for the
2644 command at all. Fixes bug 3349.
2645 - Fix a crash when handling the SIGNAL controller command or
2646 reporting ERR-level status events with bufferevents enabled. Found
2647 by Robert Ransom. Fixes bug 3367.
2648 - Always ship the tor-fw-helper manpage in our release tarballs.
2649 Fixes bug 3389. Reported by Stephen Walker.
2650 - Fix a class of double-mark-for-close bugs when bufferevents
2651 are enabled. Fixes bug 3403.
2652 - Update tor-fw-helper to support libnatpmp-20110618. Fixes bug 3434.
2653 - Add SIGNAL to the list returned by the 'GETINFO events/names'
2654 control-port command. Fixes part of bug 3465.
2655 - Prevent using negative indices during unit test runs when read_all()
2656 fails. Spotted by coverity.
2657 - Fix a rare memory leak when checking the nodelist without it being
2658 present. Found by coverity.
2659 - Only try to download a microdescriptor-flavored consensus from
2660 a directory cache that provides them.
2662 o Minor bugfixes (on 0.2.2.x and earlier):
2663 - Assert that hidden-service-related operations are not performed
2664 using single-hop circuits. Previously, Tor would assert that
2665 client-side streams are not attached to single-hop circuits,
2666 but not that other sensitive operations on the client and service
2667 side are not performed using single-hop circuits. Fixes bug 3332;
2669 - Don't publish a new relay descriptor when we reload our onion key,
2670 unless the onion key has actually changed. Fixes bug 3263 and
2671 resolves another cause of bug 1810. Bugfix on 0.1.1.11-alpha.
2672 - Allow GETINFO fingerprint to return a fingerprint even when
2673 we have not yet built a router descriptor. Fixes bug 3577;
2674 bugfix on 0.2.0.1-alpha.
2675 - Make 'tor --digests' list hashes of all Tor source files. Bugfix
2676 on 0.2.2.4-alpha; fixes bug 3427.
2678 o Code simplification and refactoring:
2679 - Use tor_sscanf() in place of scanf() in more places through the
2680 code. This makes us a little more locale-independent, and
2681 should help shut up code-analysis tools that can't tell
2682 a safe sscanf string from a dangerous one.
2683 - Use tt_assert(), not tor_assert(), for checking for test failures.
2684 This makes the unit tests more able to go on in the event that
2686 - Split connection_about_to_close() into separate functions for each
2690 - On Windows, we now define the _WIN32_WINNT macros only if they
2691 are not already defined. This lets the person building Tor decide,
2692 if they want, to require a later version of Windows.
2695 Changes in version 0.2.2.30-rc - 2011-07-07
2696 Tor 0.2.2.30-rc is the first release candidate for the Tor 0.2.2.x
2697 series. It fixes a few smaller bugs, but generally appears stable.
2698 Please test it and let us know whether it is!
2701 - Send a SUCCEEDED stream event to the controller when a reverse
2702 resolve succeeded. Fixes bug 3536; bugfix on 0.0.8pre1. Issue
2703 discovered by katmagic.
2704 - Always NUL-terminate the sun_path field of a sockaddr_un before
2705 passing it to the kernel. (Not a security issue: kernels are
2706 smart enough to reject bad sockaddr_uns.) Found by Coverity;
2707 CID #428. Bugfix on Tor 0.2.0.3-alpha.
2708 - Don't stack-allocate the list of supplementary GIDs when we're
2709 about to log them. Stack-allocating NGROUPS_MAX gid_t elements
2710 could take up to 256K, which is way too much stack. Found by
2711 Coverity; CID #450. Bugfix on 0.2.1.7-alpha.
2712 - Add BUILDTIMEOUT_SET to the list returned by the 'GETINFO
2713 events/names' control-port command. Bugfix on 0.2.2.9-alpha;
2714 fixes part of bug 3465.
2715 - Fix a memory leak when receiving a descriptor for a hidden
2716 service we didn't ask for. Found by Coverity; CID #30. Bugfix
2720 - Update to the July 1 2011 Maxmind GeoLite Country database.
2723 Changes in version 0.2.2.29-beta - 2011-06-20
2724 Tor 0.2.2.29-beta reverts an accidental behavior change for users who
2725 have bridge lines in their torrc but don't want to use them; gets
2726 us closer to having the control socket feature working on Debian;
2727 and fixes a variety of smaller bugs.
2730 - Revert the UseBridges option to its behavior before 0.2.2.28-beta.
2731 When we changed the default behavior to "use bridges if any
2732 are listed in the torrc", we surprised users who had bridges
2733 in their torrc files but who didn't actually want to use them.
2734 Partial resolution for bug 3354.
2737 - Don't attach new streams to old rendezvous circuits after SIGNAL
2738 NEWNYM. Previously, we would keep using an existing rendezvous
2739 circuit if it remained open (i.e. if it were kept open by a
2740 long-lived stream, or if a new stream were attached to it before
2741 Tor could notice that it was old and no longer in use). Bugfix on
2742 0.1.1.15-rc; fixes bug 3375.
2745 - Fix a bug when using ControlSocketsGroupWritable with User. The
2746 directory's group would be checked against the current group, not
2747 the configured group. Patch by Jérémy Bobbio. Fixes bug 3393;
2748 bugfix on 0.2.2.26-beta.
2749 - Make connection_printf_to_buf()'s behaviour sane. Its callers
2750 expect it to emit a CRLF iff the format string ends with CRLF;
2751 it actually emitted a CRLF iff (a) the format string ended with
2752 CRLF or (b) the resulting string was over 1023 characters long or
2753 (c) the format string did not end with CRLF *and* the resulting
2754 string was 1021 characters long or longer. Bugfix on 0.1.1.9-alpha;
2755 fixes part of bug 3407.
2756 - Make send_control_event_impl()'s behaviour sane. Its callers
2757 expect it to always emit a CRLF at the end of the string; it
2758 might have emitted extra control characters as well. Bugfix on
2759 0.1.1.9-alpha; fixes another part of bug 3407.
2760 - Make crypto_rand_int() check the value of its input correctly.
2761 Previously, it accepted values up to UINT_MAX, but could return a
2762 negative number if given a value above INT_MAX+1. Found by George
2763 Kadianakis. Fixes bug 3306; bugfix on 0.2.2pre14.
2764 - Avoid a segfault when reading a malformed circuit build state
2765 with more than INT_MAX entries. Found by wanoskarnet. Bugfix on
2767 - When asked about a DNS record type we don't support via a
2768 client DNSPort, reply with NOTIMPL rather than an empty
2769 reply. Patch by intrigeri. Fixes bug 3369; bugfix on 2.0.1-alpha.
2770 - Fix a rare memory leak during stats writing. Found by coverity.
2773 - Update to the June 1 2011 Maxmind GeoLite Country database.
2775 o Code simplifications and refactoring:
2776 - Remove some dead code as indicated by coverity.
2777 - Remove a few dead assignments during router parsing. Found by
2779 - Add some forgotten return value checks during unit tests. Found
2781 - Don't use 1-bit wide signed bit fields. Found by coverity.
2784 Changes in version 0.2.2.28-beta - 2011-06-04
2785 Tor 0.2.2.28-beta makes great progress towards a new stable release: we
2786 fixed a big bug in whether relays stay in the consensus consistently,
2787 we moved closer to handling bridges and hidden services correctly,
2788 and we started the process of better handling the dreaded "my Vidalia
2789 died, and now my Tor demands a password when I try to reconnect to it"
2793 - Don't decide to make a new descriptor when receiving a HUP signal.
2794 This bug has caused a lot of 0.2.2.x relays to disappear from the
2795 consensus periodically. Fixes the most common case of triggering
2796 bug 1810; bugfix on 0.2.2.7-alpha.
2797 - Actually allow nameservers with IPv6 addresses. Fixes bug 2574.
2798 - Don't try to build descriptors if "ORPort auto" is set and we
2799 don't know our actual ORPort yet. Fix for bug 3216; bugfix on
2801 - Resolve a crash that occurred when setting BridgeRelay to 1 with
2802 accounting enabled. Fixes bug 3228; bugfix on 0.2.2.18-alpha.
2803 - Apply circuit timeouts to opened hidden-service-related circuits
2804 based on the correct start time. Previously, we would apply the
2805 circuit build timeout based on time since the circuit's creation;
2806 it was supposed to be applied based on time since the circuit
2807 entered its current state. Bugfix on 0.0.6; fixes part of bug 1297.
2808 - Use the same circuit timeout for client-side introduction
2809 circuits as for other four-hop circuits, rather than the timeout
2810 for single-hop directory-fetch circuits; the shorter timeout may
2811 have been appropriate with the static circuit build timeout in
2812 0.2.1.x and earlier, but caused many hidden service access attempts
2813 to fail with the adaptive CBT introduced in 0.2.2.2-alpha. Bugfix
2814 on 0.2.2.2-alpha; fixes another part of bug 1297.
2815 - In ticket 2511 we fixed a case where you could use an unconfigured
2816 bridge if you had configured it as a bridge the last time you ran
2817 Tor. Now fix another edge case: if you had configured it as a bridge
2818 but then switched to a different bridge via the controller, you
2819 would still be willing to use the old one. Bugfix on 0.2.0.1-alpha;
2823 - Add an __OwningControllerProcess configuration option and a
2824 TAKEOWNERSHIP control-port command. Now a Tor controller can ensure
2825 that when it exits, Tor will shut down. Implements feature 3049.
2826 - If "UseBridges 1" is set and no bridges are configured, Tor will
2827 now refuse to build any circuits until some bridges are set.
2828 If "UseBridges auto" is set, Tor will use bridges if they are
2829 configured and we are not running as a server, but otherwise will
2830 make circuits as usual. The new default is "auto". Patch by anonym,
2831 so the Tails LiveCD can stop automatically revealing you as a Tor
2835 - Fix warnings from GCC 4.6's "-Wunused-but-set-variable" option.
2836 - Remove a trailing asterisk from "exit-policy/default" in the
2837 output of the control port command "GETINFO info/names". Bugfix
2839 - Use a wide type to hold sockets when built for 64-bit Windows builds.
2841 - Warn when the user configures two HiddenServiceDir lines that point
2842 to the same directory. Bugfix on 0.0.6 (the version introducing
2843 HiddenServiceDir); fixes bug 3289.
2844 - Remove dead code from rend_cache_lookup_v2_desc_as_dir. Fixes
2845 part of bug 2748; bugfix on 0.2.0.10-alpha.
2846 - Log malformed requests for rendezvous descriptors as protocol
2847 warnings, not warnings. Also, use a more informative log message
2848 in case someone sees it at log level warning without prior
2849 info-level messages. Fixes the other part of bug 2748; bugfix
2851 - Clear the table recording the time of the last request for each
2852 hidden service descriptor from each HS directory on SIGNAL NEWNYM.
2853 Previously, we would clear our HS descriptor cache on SIGNAL
2854 NEWNYM, but if we had previously retrieved a descriptor (or tried
2855 to) from every directory responsible for it, we would refuse to
2856 fetch it again for up to 15 minutes. Bugfix on 0.2.2.25-alpha;
2858 - Fix a log message that said "bits" while displaying a value in
2859 bytes. Found by wanoskarnet. Fixes bug 3318; bugfix on
2861 - When checking for 1024-bit keys, check for 1024 bits, not 128
2862 bytes. This allows Tor to correctly discard keys of length 1017
2863 through 1023. Bugfix on 0.0.9pre5.
2866 - Relays now log the reason for publishing a new relay descriptor,
2867 so we have a better chance of hunting down instances of bug 1810.
2868 Resolves ticket 3252.
2869 - Revise most log messages that refer to nodes by nickname to
2870 instead use the "$key=nickname at address" format. This should be
2871 more useful, especially since nicknames are less and less likely
2872 to be unique. Resolves ticket 3045.
2873 - Log (at info level) when purging pieces of hidden-service-client
2874 state because of SIGNAL NEWNYM.
2877 - Remove undocumented option "-F" from tor-resolve: it hasn't done
2878 anything since 0.2.1.16-rc.
2881 Changes in version 0.2.2.27-beta - 2011-05-18
2882 Tor 0.2.2.27-beta fixes a bridge-related stability bug in the previous
2883 release, and also adds a few more general bugfixes.
2886 - Fix a crash bug when changing bridges in a running Tor process.
2887 Fixes bug 3213; bugfix on 0.2.2.26-beta.
2888 - When the controller configures a new bridge, don't wait 10 to 60
2889 seconds before trying to fetch its descriptor. Bugfix on
2890 0.2.0.3-alpha; fixes bug 3198 (suggested by 2355).
2893 - Require that onion keys have exponent 65537 in microdescriptors too.
2894 Fixes more of bug 3207; bugfix on 0.2.2.26-beta.
2895 - Tor used to limit HttpProxyAuthenticator values to 48 characters.
2896 Changed the limit to 512 characters by removing base64 newlines.
2897 Fixes bug 2752. Fix by Michael Yakubovich.
2898 - When a client starts or stops using bridges, never use a circuit
2899 that was built before the configuration change. This behavior could
2900 put at risk a user who uses bridges to ensure that her traffic
2901 only goes to the chosen addresses. Bugfix on 0.2.0.3-alpha; fixes
2905 Changes in version 0.2.2.26-beta - 2011-05-17
2906 Tor 0.2.2.26-beta fixes a variety of potential privacy problems. It
2907 also introduces a new "socksport auto" approach that should make it
2908 easier to run multiple Tors on the same system, and does a lot of
2909 cleanup to get us closer to a release candidate.
2911 o Security/privacy fixes:
2912 - Replace all potentially sensitive memory comparison operations
2913 with versions whose runtime does not depend on the data being
2914 compared. This will help resist a class of attacks where an
2915 adversary can use variations in timing information to learn
2916 sensitive data. Fix for one case of bug 3122. (Safe memcmp
2917 implementation by Robert Ransom based partially on code by DJB.)
2918 - When receiving a hidden service descriptor, check that it is for
2919 the hidden service we wanted. Previously, Tor would store any
2920 hidden service descriptors that a directory gave it, whether it
2921 wanted them or not. This wouldn't have let an attacker impersonate
2922 a hidden service, but it did let directories pre-seed a client
2923 with descriptors that it didn't want. Bugfix on 0.0.6.
2924 - On SIGHUP, do not clear out all TrackHostExits mappings, client
2925 DNS cache entries, and virtual address mappings: that's what
2926 NEWNYM is for. Fixes bug 1345; bugfix on 0.1.0.1-rc.
2929 - The options SocksPort, ControlPort, and so on now all accept a
2930 value "auto" that opens a socket on an OS-selected port. A
2931 new ControlPortWriteToFile option tells Tor to write its
2932 actual control port or ports to a chosen file. If the option
2933 ControlPortFileGroupReadable is set, the file is created as
2934 group-readable. Now users can run two Tor clients on the same
2935 system without needing to manually mess with parameters. Resolves
2936 part of ticket 3076.
2937 - Set SO_REUSEADDR on all sockets, not just listeners. This should
2938 help busy exit nodes avoid running out of useable ports just
2939 because all the ports have been used in the near past. Resolves
2943 - New "GETINFO net/listeners/(type)" controller command to return
2944 a list of addresses and ports that are bound for listeners for a
2945 given connection type. This is useful when the user has configured
2946 "SocksPort auto" and the controller needs to know which port got
2947 chosen. Resolves another part of ticket 3076.
2948 - Add a new ControlSocketsGroupWritable configuration option: when
2949 it is turned on, ControlSockets are group-writeable by the default
2950 group of the current user. Patch by Jérémy Bobbio; implements
2952 - Tor now refuses to create a ControlSocket in a directory that is
2953 world-readable (or group-readable if ControlSocketsGroupWritable
2954 is 0). This is necessary because some operating systems do not
2955 enforce permissions on an AF_UNIX sockets. Permissions on the
2956 directory holding the socket, however, seems to work everywhere.
2957 - Rate-limit a warning about failures to download v2 networkstatus
2958 documents. Resolves part of bug 1352.
2959 - Backport code from 0.2.3.x that allows directory authorities to
2960 clean their microdescriptor caches. Needed to resolve bug 2230.
2961 - When an HTTPS proxy reports "403 Forbidden", we now explain
2962 what it means rather than calling it an unexpected status code.
2963 Closes bug 2503. Patch from Michael Yakubovich.
2964 - Update to the May 1 2011 Maxmind GeoLite Country database.
2967 - Authorities now clean their microdesc cache periodically and when
2968 reading from disk initially, not only when adding new descriptors.
2969 This prevents a bug where we could lose microdescriptors. Bugfix
2970 on 0.2.2.6-alpha. Fixes bug 2230.
2971 - Do not crash when our configuration file becomes unreadable, for
2972 example due to a permissions change, between when we start up
2973 and when a controller calls SAVECONF. Fixes bug 3135; bugfix
2975 - Avoid a bug that would keep us from replacing a microdescriptor
2976 cache on Windows. (We would try to replace the file while still
2977 holding it open. That's fine on Unix, but Windows doesn't let us
2978 do that.) Bugfix on 0.2.2.6-alpha; bug found by wanoskarnet.
2979 - Add missing explanations for the authority-related torrc options
2980 RephistTrackTime, BridgePassword, and V3AuthUseLegacyKey in the
2981 man page. Resolves issue 2379.
2982 - As an authority, do not upload our own vote or signature set to
2983 ourself. It would tell us nothing new, and as of 0.2.2.24-alpha,
2984 it would get flagged as a duplicate. Resolves bug 3026.
2985 - Accept hidden service descriptors if we think we might be a hidden
2986 service directory, regardless of what our consensus says. This
2987 helps robustness, since clients and hidden services can sometimes
2988 have a more up-to-date view of the network consensus than we do,
2989 and if they think that the directory authorities list us a HSDir,
2990 we might actually be one. Related to bug 2732; bugfix on
2992 - When a controller changes TrackHostExits, remove mappings for
2993 hosts that should no longer have their exits tracked. Bugfix on
2995 - When a controller changes VirtualAddrNetwork, remove any mappings
2996 for hosts that were automapped to the old network. Bugfix on
2998 - When a controller changes one of the AutomapHosts* options, remove
2999 any mappings for hosts that should no longer be automapped. Bugfix
3001 - Do not reset the bridge descriptor download status every time we
3002 re-parse our configuration or get a configuration change. Fixes
3003 bug 3019; bugfix on 0.2.0.3-alpha.
3005 o Minor bugfixes (code cleanup):
3006 - When loading the microdesc journal, remember its current size.
3007 In 0.2.2, this helps prevent the microdesc journal from growing
3008 without limit on authorities (who are the only ones to use it in
3009 0.2.2). Fixes a part of bug 2230; bugfix on 0.2.2.6-alpha.
3010 Fix posted by "cypherpunks."
3011 - The microdesc journal is supposed to get rebuilt only if it is
3012 at least _half_ the length of the store, not _twice_ the length
3013 of the store. Bugfix on 0.2.2.6-alpha; fixes part of bug 2230.
3014 - Fix a potential null-pointer dereference while computing a
3015 consensus. Bugfix on tor-0.2.0.3-alpha, found with the help of
3017 - Avoid a possible null-pointer dereference when rebuilding the mdesc
3018 cache without actually having any descriptors to cache. Bugfix on
3019 0.2.2.6-alpha. Issue discovered using clang's static analyzer.
3020 - If we fail to compute the identity digest of a v3 legacy keypair,
3021 warn, and don't use a buffer-full of junk instead. Bugfix on
3022 0.2.1.1-alpha; fixes bug 3106.
3023 - Resolve an untriggerable issue in smartlist_string_num_isin(),
3024 where if the function had ever in the future been used to check
3025 for the presence of a too-large number, it would have given an
3026 incorrect result. (Fortunately, we only used it for 16-bit
3027 values.) Fixes bug 3175; bugfix on 0.1.0.1-rc.
3028 - Require that introduction point keys and onion handshake keys
3029 have a public exponent of 65537. Starts to fix bug 3207; bugfix
3033 - Caches no longer download and serve v2 networkstatus documents
3034 unless FetchV2Networkstatus flag is set: these documents haven't
3035 haven't been used by clients or relays since 0.2.0.x. Resolves
3039 Changes in version 0.2.3.1-alpha - 2011-05-05
3040 Tor 0.2.3.1-alpha adds some new experimental features, including support
3041 for an improved network IO backend, IOCP networking on Windows,
3042 microdescriptor caching, "fast-start" support for streams, and automatic
3043 home router configuration. There are also numerous internal improvements
3044 to try to make the code easier for developers to work with.
3046 This is the first alpha release in a new series, so expect there to be
3047 bugs. Users who would rather test out a more stable branch should
3048 stay with 0.2.2.x for now.
3051 - Tor can now optionally build with the "bufferevents" buffered IO
3052 backend provided by Libevent 2. To use this feature, make sure you
3053 have the latest possible version of Libevent, and pass the
3054 --enable-bufferevents flag to configure when building Tor from
3055 source. This feature will make our networking code more flexible,
3056 let us stack layers on each other, and let us use more efficient
3057 zero-copy transports where available.
3058 - As an experimental feature, Tor can use IOCP for networking on Windows.
3059 Once this code is tuned and optimized, it promises much better
3060 performance than the select-based backend we've used in the past. To
3061 try this feature, you must build Tor with Libevent 2, configure Tor
3062 with the "bufferevents" buffered IO backend, and add "DisableIOCP 0" to
3063 your torrc. There are known bugs here: only try this if you can help
3064 debug it as it breaks.
3065 - The EntryNodes option can now include country codes like {de} or IP
3066 addresses or network masks. Previously we had disallowed these options
3067 because we didn't have an efficient way to keep the list up to
3068 date. Fixes bug 1982, but see bug 2798 for an unresolved issue here.
3069 - Exit nodes now accept and queue data on not-yet-connected streams.
3070 Previously, the client wasn't allowed to send data until the stream was
3071 connected, which slowed down all connections. This change will enable
3072 clients to perform a "fast-start" on streams and send data without
3073 having to wait for a confirmation that the stream has opened. (Patch
3074 from Ian Goldberg; implements the server side of Proposal 174.)
3075 - Tor now has initial support for automatic port mapping on the many
3076 home routers that support NAT-PMP or UPnP. (Not yet supported on
3077 Windows). To build the support code, you'll need to have libnatpnp
3078 library and/or the libminiupnpc library, and you'll need to enable the
3079 feature specifically by passing "--enable-upnp" and/or
3080 "--enable-natpnp" to configure. To turn it on, use the new
3081 PortForwarding option.
3082 - Caches now download, cache, and serve multiple "flavors" of the
3083 consensus, including a flavor that describes microdescriptors.
3084 - Caches now download, cache, and serve microdescriptors -- small
3085 summaries of router descriptors that are authenticated by all of the
3086 directory authorities. Once enough caches are running this code,
3087 clients will be able to save significant amounts of directory bandwidth
3088 by downloading microdescriptors instead of router descriptors.
3091 - Make logging resolution configurable with a new LogTimeGranularity
3092 option, and change the default from 1 millisecond to 1 second.
3093 Implements enhancement 1668.
3094 - We log which torrc file we're using on startup. Implements ticket
3096 - Ordinarily, Tor does not count traffic from private addresses (like
3097 127.0.0.1 or 10.0.0.1) when calculating rate limits or accounting.
3098 There is now a new option, CountPrivateBandwidth, to disable this
3099 behavior. Patch from Daniel Cagara.
3100 - New --enable-static-tor configure option for building Tor as
3101 statically as possible. Idea, general hackery and thoughts from
3102 Alexei Czeskis, John Gilmore, Jacob Appelbaum. Implements ticket
3104 - If you set the NumCPUs option to 0, Tor will now try to detect how
3105 many CPUs you have. This is the new default behavior.
3106 - Turn on directory request statistics by default and include them in
3107 extra-info descriptors. Don't break if we have no GeoIP database.
3108 - Relays that set "ConnDirectionStatistics 1" write statistics on the
3109 bidirectional use of connections to disk every 24 hours.
3110 - Add a GeoIP file digest to the extra-info descriptor. Implements
3112 - The NodeFamily option -- which let you declare that you want to
3113 consider nodes to be part of a family whether they list themselves
3114 that way or not -- now allows IP address ranges and country codes.
3115 - Add a new 'Heartbeat' log message type to periodically log a message
3116 describing Tor's status at level Notice. This feature is meant for
3117 operators who log at notice, and want to make sure that their Tor
3118 server is still working. Implementation by George Kadianakis.
3120 o Minor bugfixes (on 0.2.2.25-alpha):
3121 - When loading the microdesc journal, remember its current size.
3122 In 0.2.2, this helps prevent the microdesc journal from growing
3123 without limit on authorities (who are the only ones to use it in
3124 0.2.2). Fixes a part of bug 2230; bugfix on 0.2.2.6-alpha.
3125 Fix posted by "cypherpunks."
3126 - The microdesc journal is supposed to get rebuilt only if it is
3127 at least _half_ the length of the store, not _twice_ the length
3128 of the store. Bugfix on 0.2.2.6-alpha; fixes part of bug 2230.
3129 - If as an authority we fail to compute the identity digest of a v3
3130 legacy keypair, warn, and don't use a buffer-full of junk instead.
3131 Bugfix on 0.2.1.1-alpha; fixes bug 3106.
3132 - Authorities now clean their microdesc cache periodically and when
3133 reading from disk initially, not only when adding new descriptors.
3134 This prevents a bug where we could lose microdescriptors. Bugfix
3137 o Minor features (controller):
3138 - Add a new SIGNAL event to the controller interface so that
3139 controllers can be notified when Tor handles a signal. Resolves
3140 issue 1955. Patch by John Brooks.
3141 - Add a new GETINFO option to get total bytes read and written. Patch
3142 from pipe, revised by atagar. Resolves ticket 2345.
3143 - Implement some GETINFO controller fields to provide information about
3144 the Tor process's pid, euid, username, and resource limits.
3147 - Our build system requires automake 1.6 or later to create the
3148 Makefile.in files. Previously, you could have used 1.4.
3149 This only affects developers and people building Tor from git;
3150 people who build Tor from the source distribution without changing
3151 the Makefile.am files should be fine.
3152 - Our autogen.sh script uses autoreconf to launch autoconf, automake, and
3153 so on. This is more robust against some of the failure modes
3154 associated with running the autotools pieces on their own.
3156 o Minor packaging issues:
3157 - On OpenSUSE, create the /var/run/tor directory on startup if it is not
3158 already created. Patch from Andreas Stieger. Fixes bug 2573.
3160 o Code simplifications and refactoring:
3161 - A major revision to our internal node-selecting and listing logic.
3162 Tor already had at least two major ways to look at the question of
3163 "which Tor servers do we know about": a list of router descriptors,
3164 and a list of entries in the current consensus. With
3165 microdescriptors, we're adding a third. Having so many systems
3166 without an abstraction layer over them was hurting the codebase.
3167 Now, we have a new "node_t" abstraction that presents a consistent
3168 interface to a client's view of a Tor node, and holds (nearly) all
3169 of the mutable state formerly in routerinfo_t and routerstatus_t.
3170 - The helper programs tor-gencert, tor-resolve, and tor-checkkey
3171 no longer link against Libevent: they never used it, but
3172 our library structure used to force them to link it.
3175 - Remove some old code to work around even older versions of Tor that
3176 used forked processes to handle DNS requests. Such versions of Tor
3177 are no longer in use as servers.
3179 o Documentation fixes:
3180 - Correct a broken faq link in the INSTALL file. Fixes bug 2307.
3181 - Add missing documentation for the authority-related torrc options
3182 RephistTrackTime, BridgePassword, and V3AuthUseLegacyKey. Resolves
3186 Changes in version 0.2.2.25-alpha - 2011-04-29
3187 Tor 0.2.2.25-alpha fixes many bugs: hidden service clients are more
3188 robust, routers no longer overreport their bandwidth, Win7 should crash
3189 a little less, and NEWNYM (as used by Vidalia's "new identity" button)
3190 now prevents hidden service-related activity from being linkable. It
3191 provides more information to Vidalia so you can see if your bridge is
3192 working. Also, 0.2.2.25-alpha revamps the Entry/Exit/ExcludeNodes and
3193 StrictNodes configuration options to make them more reliable, more
3194 understandable, and more regularly applied. If you use those options,
3195 please see the revised documentation for them in the manual page.
3198 - Relays were publishing grossly inflated bandwidth values because
3199 they were writing their state files wrong--now they write the
3200 correct value. Also, resume reading bandwidth history from the
3201 state file correctly. Fixes bug 2704; bugfix on 0.2.2.23-alpha.
3202 - Improve hidden service robustness: When we find that we have
3203 extended a hidden service's introduction circuit to a relay not
3204 listed as an introduction point in the HS descriptor we currently
3205 have, retry with an introduction point from the current
3206 descriptor. Previously we would just give up. Fixes bugs 1024 and
3207 1930; bugfix on 0.2.0.10-alpha.
3208 - Clients now stop trying to use an exit node associated with a given
3209 destination by TrackHostExits if they fail to reach that exit node.
3210 Fixes bug 2999. Bugfix on 0.2.0.20-rc.
3211 - Fix crash bug on platforms where gmtime and localtime can return
3212 NULL. Windows 7 users were running into this one. Fixes part of bug
3213 2077. Bugfix on all versions of Tor. Found by boboper.
3215 o Security and stability fixes:
3216 - Don't double-free a parsable, but invalid, microdescriptor, even if
3217 it is followed in the blob we're parsing by an unparsable
3218 microdescriptor. Fixes an issue reported in a comment on bug 2954.
3219 Bugfix on 0.2.2.6-alpha; fix by "cypherpunks".
3220 - If the Nickname configuration option isn't given, Tor would pick a
3221 nickname based on the local hostname as the nickname for a relay.
3222 Because nicknames are not very important in today's Tor and the
3223 "Unnamed" nickname has been implemented, this is now problematic
3224 behavior: It leaks information about the hostname without being
3225 useful at all. Fixes bug 2979; bugfix on 0.1.2.2-alpha, which
3226 introduced the Unnamed nickname. Reported by tagnaq.
3227 - Fix an uncommon assertion failure when running with DNSPort under
3228 heavy load. Fixes bug 2933; bugfix on 0.2.0.1-alpha.
3229 - Avoid linkability based on cached hidden service descriptors: forget
3230 all hidden service descriptors cached as a client when processing a
3231 SIGNAL NEWNYM command. Fixes bug 3000; bugfix on 0.0.6.
3234 - Export GeoIP information on bridge usage to controllers even if we
3235 have not yet been running for 24 hours. Now Vidalia bridge operators
3236 can get more accurate and immediate feedback about their
3237 contributions to the network.
3239 o Major features and bugfixes (node selection):
3240 - Revise and reconcile the meaning of the ExitNodes, EntryNodes,
3241 ExcludeEntryNodes, ExcludeExitNodes, ExcludeNodes, and StrictNodes
3242 options. Previously, we had been ambiguous in describing what
3243 counted as an "exit" node, and what operations exactly "StrictNodes
3244 0" would permit. This created confusion when people saw nodes built
3245 through unexpected circuits, and made it hard to tell real bugs from
3246 surprises. Now the intended behavior is:
3247 . "Exit", in the context of ExitNodes and ExcludeExitNodes, means
3248 a node that delivers user traffic outside the Tor network.
3249 . "Entry", in the context of EntryNodes, means a node used as the
3250 first hop of a multihop circuit. It doesn't include direct
3251 connections to directory servers.
3252 . "ExcludeNodes" applies to all nodes.
3253 . "StrictNodes" changes the behavior of ExcludeNodes only. When
3254 StrictNodes is set, Tor should avoid all nodes listed in
3255 ExcludeNodes, even when it will make user requests fail. When
3256 StrictNodes is *not* set, then Tor should follow ExcludeNodes
3257 whenever it can, except when it must use an excluded node to
3258 perform self-tests, connect to a hidden service, provide a
3259 hidden service, fulfill a .exit request, upload directory
3260 information, or fetch directory information.
3261 Collectively, the changes to implement the behavior fix bug 1090.
3262 - ExcludeNodes now takes precedence over EntryNodes and ExitNodes: if
3263 a node is listed in both, it's treated as excluded.
3264 - ExcludeNodes now applies to directory nodes -- as a preference if
3265 StrictNodes is 0, or an absolute requirement if StrictNodes is 1.
3266 Don't exclude all the directory authorities and set StrictNodes to 1
3267 unless you really want your Tor to break.
3268 - ExcludeNodes and ExcludeExitNodes now override exit enclaving.
3269 - ExcludeExitNodes now overrides .exit requests.
3270 - We don't use bridges listed in ExcludeNodes.
3271 - When StrictNodes is 1:
3272 . We now apply ExcludeNodes to hidden service introduction points
3273 and to rendezvous points selected by hidden service users. This
3274 can make your hidden service less reliable: use it with caution!
3275 . If we have used ExcludeNodes on ourself, do not try relay
3276 reachability self-tests.
3277 . If we have excluded all the directory authorities, we will not
3278 even try to upload our descriptor if we're a relay.
3279 . Do not honor .exit requests to an excluded node.
3280 - Remove a misfeature that caused us to ignore the Fast/Stable flags
3281 when ExitNodes is set. Bugfix on 0.2.2.7-alpha.
3282 - When the set of permitted nodes changes, we now remove any mappings
3283 introduced via TrackExitHosts to now-excluded nodes. Bugfix on
3285 - We never cannibalize a circuit that had excluded nodes on it, even
3286 if StrictNodes is 0. Bugfix on 0.1.0.1-rc.
3287 - Revert a change where we would be laxer about attaching streams to
3288 circuits than when building the circuits. This was meant to prevent
3289 a set of bugs where streams were never attachable, but our improved
3290 code here should make this unnecessary. Bugfix on 0.2.2.7-alpha.
3291 - Keep track of how many times we launch a new circuit to handle a
3292 given stream. Too many launches could indicate an inconsistency
3293 between our "launch a circuit to handle this stream" logic and our
3294 "attach this stream to one of the available circuits" logic.
3295 - Improve log messages related to excluded nodes.
3298 - Fix a spurious warning when moving from a short month to a long
3299 month on relays with month-based BandwidthAccounting. Bugfix on
3300 0.2.2.17-alpha; fixes bug 3020.
3301 - When a client finds that an origin circuit has run out of 16-bit
3302 stream IDs, we now mark it as unusable for new streams. Previously,
3303 we would try to close the entire circuit. Bugfix on 0.0.6.
3304 - Add a forgotten cast that caused a compile warning on OS X 10.6.
3305 Bugfix on 0.2.2.24-alpha.
3306 - Be more careful about reporting the correct error from a failed
3307 connect() system call. Under some circumstances, it was possible to
3308 look at an incorrect value for errno when sending the end reason.
3309 Bugfix on 0.1.0.1-rc.
3310 - Correctly handle an "impossible" overflow cases in connection byte
3311 counting, where we write or read more than 4GB on an edge connection
3312 in a single second. Bugfix on 0.1.2.8-beta.
3313 - Correct the warning displayed when a rendezvous descriptor exceeds
3314 the maximum size. Fixes bug 2750; bugfix on 0.2.1.5-alpha. Found by
3316 - Clients and hidden services now use HSDir-flagged relays for hidden
3317 service descriptor downloads and uploads even if the relays have no
3318 DirPort set and the client has disabled TunnelDirConns. This will
3319 eventually allow us to give the HSDir flag to relays with no
3320 DirPort. Fixes bug 2722; bugfix on 0.2.1.6-alpha.
3321 - Downgrade "no current certificates known for authority" message from
3322 Notice to Info. Fixes bug 2899; bugfix on 0.2.0.10-alpha.
3323 - Make the SIGNAL DUMP control-port command work on FreeBSD. Fixes bug
3324 2917. Bugfix on 0.1.1.1-alpha.
3325 - Only limit the lengths of single HS descriptors, even when multiple
3326 HS descriptors are published to an HSDir relay in a single POST
3327 operation. Fixes bug 2948; bugfix on 0.2.1.5-alpha. Found by hsdir.
3328 - Write the current time into the LastWritten line in our state file,
3329 rather than the time from the previous write attempt. Also, stop
3330 trying to use a time of -1 in our log statements. Fixes bug 3039;
3331 bugfix on 0.2.2.14-alpha.
3332 - Be more consistent in our treatment of file system paths. "~" should
3333 get expanded to the user's home directory in the Log config option.
3334 Fixes bug 2971; bugfix on 0.2.0.1-alpha, which introduced the
3335 feature for the -f and --DataDirectory options.
3338 - Make sure every relay writes a state file at least every 12 hours.
3339 Previously, a relay could go for weeks without writing its state
3340 file, and on a crash could lose its bandwidth history, capacity
3341 estimates, client country statistics, and so on. Addresses bug 3012.
3342 - Send END_STREAM_REASON_NOROUTE in response to EHOSTUNREACH errors.
3343 Clients before 0.2.1.27 didn't handle NOROUTE correctly, but such
3344 clients are already deprecated because of security bugs.
3345 - Don't allow v0 hidden service authorities to act as clients.
3346 Required by fix for bug 3000.
3347 - Ignore SIGNAL NEWNYM commands on relay-only Tor instances. Required
3348 by fix for bug 3000.
3349 - Ensure that no empty [dirreq-](read|write)-history lines are added
3350 to an extrainfo document. Implements ticket 2497.
3352 o Code simplification and refactoring:
3353 - Remove workaround code to handle directory responses from servers
3354 that had bug 539 (they would send HTTP status 503 responses _and_
3355 send a body too). Since only server versions before
3356 0.2.0.16-alpha/0.1.2.19 were affected, there is no longer reason to
3357 keep the workaround in place.
3358 - Remove the old 'fuzzy time' logic. It was supposed to be used for
3359 handling calculations where we have a known amount of clock skew and
3360 an allowed amount of unknown skew. But we only used it in three
3361 places, and we never adjusted the known/unknown skew values. This is
3362 still something we might want to do someday, but if we do, we'll
3363 want to do it differently.
3364 - Avoid signed/unsigned comparisons by making SIZE_T_CEILING unsigned.
3365 None of the cases where we did this before were wrong, but by making
3366 this change we avoid warnings. Fixes bug 2475; bugfix on 0.2.1.28.
3367 - Use GetTempDir to find the proper temporary directory location on
3368 Windows when generating temporary files for the unit tests. Patch by
3372 Changes in version 0.2.2.24-alpha - 2011-04-08
3373 Tor 0.2.2.24-alpha fixes a variety of bugs, including a big bug that
3374 prevented Tor clients from effectively using "multihomed" bridges,
3375 that is, bridges that listen on multiple ports or IP addresses so users
3376 can continue to use some of their addresses even if others get blocked.
3379 - Fix a bug where bridge users who configure the non-canonical
3380 address of a bridge automatically switch to its canonical
3381 address. If a bridge listens at more than one address, it should be
3382 able to advertise those addresses independently and any non-blocked
3383 addresses should continue to work. Bugfix on Tor 0.2.0.x. Fixes
3385 - If you configured Tor to use bridge A, and then quit and
3386 configured Tor to use bridge B instead, it would happily continue
3387 to use bridge A if it's still reachable. While this behavior is
3388 a feature if your goal is connectivity, in some scenarios it's a
3389 dangerous bug. Bugfix on Tor 0.2.0.1-alpha; fixes bug 2511.
3390 - Directory authorities now use data collected from their own
3391 uptime observations when choosing whether to assign the HSDir flag
3392 to relays, instead of trusting the uptime value the relay reports in
3393 its descriptor. This change helps prevent an attack where a small
3394 set of nodes with frequently-changing identity keys can blackhole
3395 a hidden service. (Only authorities need upgrade; others will be
3396 fine once they do.) Bugfix on 0.2.0.10-alpha; fixes bug 2709.
3399 - When we restart our relay, we might get a successful connection
3400 from the outside before we've started our reachability tests,
3401 triggering a warning: "ORPort found reachable, but I have no
3402 routerinfo yet. Failing to inform controller of success." This
3403 bug was harmless unless Tor is running under a controller
3404 like Vidalia, in which case the controller would never get a
3405 REACHABILITY_SUCCEEDED status event. Bugfix on 0.1.2.6-alpha;
3407 - Make directory authorities more accurate at recording when
3408 relays that have failed several reachability tests became
3409 unreachable, so we can provide more accuracy at assigning Stable,
3410 Guard, HSDir, etc flags. Bugfix on 0.2.0.6-alpha. Resolves bug 2716.
3411 - Fix an issue that prevented static linking of libevent on
3412 some platforms (notably Linux). Fixes bug 2698; bugfix on
3413 versions 0.2.1.23/0.2.2.8-alpha (the versions introducing
3414 the --with-static-libevent configure option).
3415 - We now ask the other side of a stream (the client or the exit)
3416 for more data on that stream when the amount of queued data on
3417 that stream dips low enough. Previously, we wouldn't ask the
3418 other side for more data until either it sent us more data (which
3419 it wasn't supposed to do if it had exhausted its window!) or we
3420 had completely flushed all our queued data. This flow control fix
3421 should improve throughput. Fixes bug 2756; bugfix on the earliest
3422 released versions of Tor (svn commit r152).
3423 - Avoid a double-mark-for-free warning when failing to attach a
3424 transparent proxy connection. (We thought we had fixed this in
3425 0.2.2.23-alpha, but it turns out our fix was checking the wrong
3426 connection.) Fixes bug 2757; bugfix on 0.1.2.1-alpha (the original
3427 bug) and 0.2.2.23-alpha (the incorrect fix).
3428 - When warning about missing zlib development packages during compile,
3429 give the correct package names. Bugfix on 0.2.0.1-alpha.
3432 - Directory authorities now log the source of a rejected POSTed v3
3434 - Make compilation with clang possible when using
3435 --enable-gcc-warnings by removing two warning options that clang
3436 hasn't implemented yet and by fixing a few warnings. Implements
3438 - When expiring circuits, use microsecond timers rather than
3439 one-second timers. This can avoid an unpleasant situation where a
3440 circuit is launched near the end of one second and expired right
3441 near the beginning of the next, and prevent fluctuations in circuit
3443 - Use computed circuit-build timeouts to decide when to launch
3444 parallel introduction circuits for hidden services. (Previously,
3445 we would retry after 15 seconds.)
3446 - Update to the April 1 2011 Maxmind GeoLite Country database.
3449 - Create the /var/run/tor directory on startup on OpenSUSE if it is
3450 not already created. Patch from Andreas Stieger. Fixes bug 2573.
3452 o Documentation changes:
3453 - Modernize the doxygen configuration file slightly. Fixes bug 2707.
3454 - Resolve all doxygen warnings except those for missing documentation.
3456 - Add doxygen documentation for more functions, fields, and types.
3459 Changes in version 0.2.2.23-alpha - 2011-03-08
3460 Tor 0.2.2.23-alpha lets relays record their bandwidth history so when
3461 they restart they don't lose their bandwidth capacity estimate. This
3462 release also fixes a diverse set of user-facing bugs, ranging from
3463 relays overrunning their rate limiting to clients falsely warning about
3464 clock skew to bridge descriptor leaks by our bridge directory authority.
3467 - Stop sending a CLOCK_SKEW controller status event whenever
3468 we fetch directory information from a relay that has a wrong clock.
3469 Instead, only inform the controller when it's a trusted authority
3470 that claims our clock is wrong. Bugfix on 0.1.2.6-alpha; fixes
3471 the rest of bug 1074.
3472 - Fix an assert in parsing router descriptors containing IPv6
3473 addresses. This one took down the directory authorities when
3474 somebody tried some experimental code. Bugfix on 0.2.1.3-alpha.
3475 - Make the bridge directory authority refuse to answer directory
3476 requests for "all" descriptors. It used to include bridge
3477 descriptors in its answer, which was a major information leak.
3478 Found by "piebeer". Bugfix on 0.2.0.3-alpha.
3479 - If relays set RelayBandwidthBurst but not RelayBandwidthRate,
3480 Tor would ignore their RelayBandwidthBurst setting,
3481 potentially using more bandwidth than expected. Bugfix on
3482 0.2.0.1-alpha. Reported by Paul Wouters. Fixes bug 2470.
3483 - Ignore and warn if the user mistakenly sets "PublishServerDescriptor
3484 hidserv" in her torrc. The 'hidserv' argument never controlled
3485 publication of hidden service descriptors. Bugfix on 0.2.0.1-alpha.
3488 - Relays now save observed peak bandwidth throughput rates to their
3489 state file (along with total usage, which was already saved)
3490 so that they can determine their correct estimated bandwidth on
3491 restart. Resolves bug 1863, where Tor relays would reset their
3492 estimated bandwidth to 0 after restarting.
3493 - Directory authorities now take changes in router IP address and
3494 ORPort into account when determining router stability. Previously,
3495 if a router changed its IP or ORPort, the authorities would not
3496 treat it as having any downtime for the purposes of stability
3497 calculation, whereas clients would experience downtime since the
3498 change could take a while to propagate to them. Resolves issue 1035.
3499 - Enable Address Space Layout Randomization (ASLR) and Data Execution
3500 Prevention (DEP) by default on Windows to make it harder for
3501 attackers to exploit vulnerabilities. Patch from John Brooks.
3503 o Minor bugfixes (on 0.2.1.x and earlier):
3504 - Fix a rare crash bug that could occur when a client was configured
3505 with a large number of bridges. Fixes bug 2629; bugfix on
3506 0.2.1.2-alpha. Bugfix by trac user "shitlei".
3507 - Avoid a double mark-for-free warning when failing to attach a
3508 transparent proxy connection. Bugfix on 0.1.2.1-alpha. Fixes
3510 - Correctly detect failure to allocate an OpenSSL BIO. Fixes bug 2378;
3511 found by "cypherpunks". This bug was introduced before the first
3512 Tor release, in svn commit r110.
3513 - Country codes aren't supported in EntryNodes until 0.2.3.x, so
3514 don't mention them in the manpage. Fixes bug 2450; issue
3515 spotted by keb and G-Lo.
3516 - Fix a bug in bandwidth history state parsing that could have been
3517 triggered if a future version of Tor ever changed the timing
3518 granularity at which bandwidth history is measured. Bugfix on
3520 - When a relay decides that its DNS is too broken for it to serve
3521 as an exit server, it advertised itself as a non-exit, but
3522 continued to act as an exit. This could create accidental
3523 partitioning opportunities for users. Instead, if a relay is
3524 going to advertise reject *:* as its exit policy, it should
3525 really act with exit policy "reject *:*". Fixes bug 2366.
3526 Bugfix on Tor 0.1.2.5-alpha. Bugfix by user "postman" on trac.
3527 - In the special case where you configure a public exit relay as your
3528 bridge, Tor would be willing to use that exit relay as the last
3529 hop in your circuit as well. Now we fail that circuit instead.
3530 Bugfix on 0.2.0.12-alpha. Fixes bug 2403. Reported by "piebeer".
3531 - Fix a bug with our locking implementation on Windows that couldn't
3532 correctly detect when a file was already locked. Fixes bug 2504,
3533 bugfix on 0.2.1.6-alpha.
3534 - Fix IPv6-related connect() failures on some platforms (BSD, OS X).
3535 Bugfix on 0.2.0.3-alpha; fixes first part of bug 2660. Patch by
3537 - Set target port in get_interface_address6() correctly. Bugfix
3538 on 0.1.1.4-alpha and 0.2.0.3-alpha; fixes second part of bug 2660.
3539 - Directory authorities are now more robust to hops back in time
3540 when calculating router stability. Previously, if a run of uptime
3541 or downtime appeared to be negative, the calculation could give
3542 incorrect results. Bugfix on 0.2.0.6-alpha; noticed when fixing
3544 - Fix an assert that got triggered when using the TestingTorNetwork
3545 configuration option and then issuing a GETINFO config-text control
3546 command. Fixes bug 2250; bugfix on 0.2.1.2-alpha.
3548 o Minor bugfixes (on 0.2.2.x):
3549 - Clients should not weight BadExit nodes as Exits in their node
3550 selection. Similarly, directory authorities should not count BadExit
3551 bandwidth as Exit bandwidth when computing bandwidth-weights.
3552 Bugfix on 0.2.2.10-alpha; fixes bug 2203.
3553 - Correctly clear our dir_read/dir_write history when there is an
3554 error parsing any bw history value from the state file. Bugfix on
3556 - Resolve a bug in verifying signatures of directory objects
3557 with digests longer than SHA1. Bugfix on 0.2.2.20-alpha.
3558 Fixes bug 2409. Found by "piebeer".
3559 - Bridge authorities no longer crash on SIGHUP when they try to
3560 publish their relay descriptor to themselves. Fixes bug 2572. Bugfix
3564 - Log less aggressively about circuit timeout changes, and improve
3565 some other circuit timeout messages. Resolves bug 2004.
3566 - Log a little more clearly about the times at which we're no longer
3567 accepting new connections. Resolves bug 2181.
3568 - Reject attempts at the client side to open connections to private
3569 IP addresses (like 127.0.0.1, 10.0.0.1, and so on) with
3570 a randomly chosen exit node. Attempts to do so are always
3571 ill-defined, generally prevented by exit policies, and usually
3572 in error. This will also help to detect loops in transparent
3573 proxy configurations. You can disable this feature by setting
3574 "ClientRejectInternalAddresses 0" in your torrc.
3575 - Always treat failure to allocate an RSA key as an unrecoverable
3577 - Update to the March 1 2011 Maxmind GeoLite Country database.
3579 o Minor features (log subsystem):
3580 - Add documentation for configuring logging at different severities in
3581 different log domains. We've had this feature since 0.2.1.1-alpha,
3582 but for some reason it never made it into the manpage. Fixes
3584 - Make it simpler to specify "All log domains except for A and B".
3585 Previously you needed to say "[*,~A,~B]". Now you can just say
3587 - Add a "LogMessageDomains 1" option to include the domains of log
3588 messages along with the messages. Without this, there's no way
3589 to use log domains without reading the source or doing a lot
3592 o Packaging changes:
3593 - Stop shipping the Tor specs files and development proposal documents
3594 in the tarball. They are now in a separate git repository at
3595 git://git.torproject.org/torspec.git
3598 Changes in version 0.2.1.30 - 2011-02-23
3599 Tor 0.2.1.30 fixes a variety of less critical bugs. The main other
3600 change is a slight tweak to Tor's TLS handshake that makes relays
3601 and bridges that run this new version reachable from Iran again.
3602 We don't expect this tweak will win the arms race long-term, but it
3603 buys us time until we roll out a better solution.
3606 - Stop sending a CLOCK_SKEW controller status event whenever
3607 we fetch directory information from a relay that has a wrong clock.
3608 Instead, only inform the controller when it's a trusted authority
3609 that claims our clock is wrong. Bugfix on 0.1.2.6-alpha; fixes
3610 the rest of bug 1074.
3611 - Fix a bounds-checking error that could allow an attacker to
3612 remotely crash a directory authority. Bugfix on 0.2.1.5-alpha.
3614 - If relays set RelayBandwidthBurst but not RelayBandwidthRate,
3615 Tor would ignore their RelayBandwidthBurst setting,
3616 potentially using more bandwidth than expected. Bugfix on
3617 0.2.0.1-alpha. Reported by Paul Wouters. Fixes bug 2470.
3618 - Ignore and warn if the user mistakenly sets "PublishServerDescriptor
3619 hidserv" in her torrc. The 'hidserv' argument never controlled
3620 publication of hidden service descriptors. Bugfix on 0.2.0.1-alpha.
3623 - Adjust our TLS Diffie-Hellman parameters to match those used by
3625 - Update to the February 1 2011 Maxmind GeoLite Country database.
3628 - Check for and reject overly long directory certificates and
3629 directory tokens before they have a chance to hit any assertions.
3630 Bugfix on 0.2.1.28. Found by "doorss".
3631 - Bring the logic that gathers routerinfos and assesses the
3632 acceptability of circuits into line. This prevents a Tor OP from
3633 getting locked in a cycle of choosing its local OR as an exit for a
3634 path (due to a .exit request) and then rejecting the circuit because
3635 its OR is not listed yet. It also prevents Tor clients from using an
3636 OR running in the same instance as an exit (due to a .exit request)
3637 if the OR does not meet the same requirements expected of an OR
3638 running elsewhere. Fixes bug 1859; bugfix on 0.1.0.1-rc.
3640 o Packaging changes:
3641 - Stop shipping the Tor specs files and development proposal documents
3642 in the tarball. They are now in a separate git repository at
3643 git://git.torproject.org/torspec.git
3644 - Do not include Git version tags as though they are SVN tags when
3645 generating a tarball from inside a repository that has switched
3646 between branches. Bugfix on 0.2.1.15-rc; fixes bug 2402.
3649 Changes in version 0.2.2.22-alpha - 2011-01-25
3650 Tor 0.2.2.22-alpha fixes a few more less-critical security issues. The
3651 main other change is a slight tweak to Tor's TLS handshake that makes
3652 relays and bridges that run this new version reachable from Iran again.
3653 We don't expect this tweak will win the arms race long-term, but it
3654 will buy us a bit more time until we roll out a better solution.
3657 - Fix a bounds-checking error that could allow an attacker to
3658 remotely crash a directory authority. Bugfix on 0.2.1.5-alpha.
3660 - Don't assert when changing from bridge to relay or vice versa
3661 via the controller. The assert happened because we didn't properly
3662 initialize our keys in this case. Bugfix on 0.2.2.18-alpha; fixes
3663 bug 2433. Reported by bastik.
3666 - Adjust our TLS Diffie-Hellman parameters to match those used by
3668 - Provide a log message stating which geoip file we're parsing
3669 instead of just stating that we're parsing the geoip file.
3670 Implements ticket 2432.
3673 - Check for and reject overly long directory certificates and
3674 directory tokens before they have a chance to hit any assertions.
3675 Bugfix on 0.2.1.28 / 0.2.2.20-alpha. Found by "doorss".
3678 Changes in version 0.2.2.21-alpha - 2011-01-15
3679 Tor 0.2.2.21-alpha includes all the patches from Tor 0.2.1.29, which
3680 continues our recent code security audit work. The main fix resolves
3681 a remote heap overflow vulnerability that can allow remote code
3682 execution (CVE-2011-0427). Other fixes address a variety of assert
3683 and crash bugs, most of which we think are hard to exploit remotely.
3685 o Major bugfixes (security), also included in 0.2.1.29:
3686 - Fix a heap overflow bug where an adversary could cause heap
3687 corruption. This bug probably allows remote code execution
3688 attacks. Reported by "debuger". Fixes CVE-2011-0427. Bugfix on
3690 - Prevent a denial-of-service attack by disallowing any
3691 zlib-compressed data whose compression factor is implausibly
3692 high. Fixes part of bug 2324; reported by "doorss".
3693 - Zero out a few more keys in memory before freeing them. Fixes
3694 bug 2384 and part of bug 2385. These key instances found by
3695 "cypherpunks", based on Andrew Case's report about being able
3696 to find sensitive data in Tor's memory space if you have enough
3697 permissions. Bugfix on 0.0.2pre9.
3699 o Major bugfixes (crashes), also included in 0.2.1.29:
3700 - Prevent calls to Libevent from inside Libevent log handlers.
3701 This had potential to cause a nasty set of crashes, especially
3702 if running Libevent with debug logging enabled, and running
3703 Tor with a controller watching for low-severity log messages.
3704 Bugfix on 0.1.0.2-rc. Fixes bug 2190.
3705 - Add a check for SIZE_T_MAX to tor_realloc() to try to avoid
3706 underflow errors there too. Fixes the other part of bug 2324.
3707 - Fix a bug where we would assert if we ever had a
3708 cached-descriptors.new file (or another file read directly into
3709 memory) of exactly SIZE_T_CEILING bytes. Fixes bug 2326; bugfix
3710 on 0.2.1.25. Found by doorss.
3711 - Fix some potential asserts and parsing issues with grossly
3712 malformed router caches. Fixes bug 2352; bugfix on Tor 0.2.1.27.
3715 o Minor bugfixes (other), also included in 0.2.1.29:
3716 - Fix a bug with handling misformed replies to reverse DNS lookup
3717 requests in DNSPort. Bugfix on Tor 0.2.0.1-alpha. Related to a
3718 bug reported by doorss.
3719 - Fix compilation on mingw when a pthreads compatibility library
3720 has been installed. (We don't want to use it, so we shouldn't
3721 be including pthread.h.) Fixes bug 2313; bugfix on 0.1.0.1-rc.
3722 - Fix a bug where we would declare that we had run out of virtual
3723 addresses when the address space was only half-exhausted. Bugfix
3725 - Correctly handle the case where AutomapHostsOnResolve is set but
3726 no virtual addresses are available. Fixes bug 2328; bugfix on
3727 0.1.2.1-alpha. Bug found by doorss.
3728 - Correctly handle wrapping around when we run out of virtual
3729 address space. Found by cypherpunks; bugfix on 0.2.0.5-alpha.
3731 o Minor features, also included in 0.2.1.29:
3732 - Update to the January 1 2011 Maxmind GeoLite Country database.
3733 - Introduce output size checks on all of our decryption functions.
3735 o Build changes, also included in 0.2.1.29:
3736 - Tor does not build packages correctly with Automake 1.6 and earlier;
3737 added a check to Makefile.am to make sure that we're building with
3738 Automake 1.7 or later.
3739 - The 0.2.1.28 tarball was missing src/common/OpenBSD_malloc_Linux.c
3740 because we built it with a too-old version of automake. Thus that
3741 release broke ./configure --enable-openbsd-malloc, which is popular
3742 among really fast exit relays on Linux.
3744 o Major bugfixes, new in 0.2.2.21-alpha:
3745 - Prevent crash/heap corruption when the cbtnummodes consensus
3746 parameter is set to 0 or large values. Fixes bug 2317; bugfix
3749 o Major features, new in 0.2.2.21-alpha:
3750 - Introduce minimum/maximum values that clients will believe
3751 from the consensus. Now we'll have a better chance to avoid crashes
3752 or worse when a consensus param has a weird value.
3754 o Minor features, new in 0.2.2.21-alpha:
3755 - Make sure to disable DirPort if running as a bridge. DirPorts aren't
3756 used on bridges, and it makes bridge scanning somewhat easier.
3757 - If writing the state file to disk fails, wait up to an hour before
3758 retrying again, rather than trying again each second. Fixes bug
3759 2346; bugfix on Tor 0.1.1.3-alpha.
3760 - Make Libevent log messages get delivered to controllers later,
3761 and not from inside the Libevent log handler. This prevents unsafe
3762 reentrant Libevent calls while still letting the log messages
3764 - Detect platforms that brokenly use a signed size_t, and refuse to
3765 build there. Found and analyzed by doorss and rransom.
3766 - Fix a bunch of compile warnings revealed by mingw with gcc 4.5.
3769 o Minor bugfixes, new in 0.2.2.21-alpha:
3770 - Handle SOCKS messages longer than 128 bytes long correctly, rather
3771 than waiting forever for them to finish. Fixes bug 2330; bugfix
3772 on 0.2.0.16-alpha. Found by doorss.
3773 - Add assertions to check for overflow in arguments to
3774 base32_encode() and base32_decode(); fix a signed-unsigned
3775 comparison there too. These bugs are not actually reachable in Tor,
3776 but it's good to prevent future errors too. Found by doorss.
3777 - Correctly detect failures to create DNS requests when using Libevent
3778 versions before v2. (Before Libevent 2, we used our own evdns
3779 implementation. Its return values for Libevent's evdns_resolve_*()
3780 functions are not consistent with those from Libevent.) Fixes bug
3781 2363; bugfix on 0.2.2.6-alpha. Found by "lodger".
3783 o Documentation, new in 0.2.2.21-alpha:
3784 - Document the default socks host and port (127.0.0.1:9050) for
3788 Changes in version 0.2.1.29 - 2011-01-15
3789 Tor 0.2.1.29 continues our recent code security audit work. The main
3790 fix resolves a remote heap overflow vulnerability that can allow remote
3791 code execution. Other fixes address a variety of assert and crash bugs,
3792 most of which we think are hard to exploit remotely.
3794 o Major bugfixes (security):
3795 - Fix a heap overflow bug where an adversary could cause heap
3796 corruption. This bug probably allows remote code execution
3797 attacks. Reported by "debuger". Fixes CVE-2011-0427. Bugfix on
3799 - Prevent a denial-of-service attack by disallowing any
3800 zlib-compressed data whose compression factor is implausibly
3801 high. Fixes part of bug 2324; reported by "doorss".
3802 - Zero out a few more keys in memory before freeing them. Fixes
3803 bug 2384 and part of bug 2385. These key instances found by
3804 "cypherpunks", based on Andrew Case's report about being able
3805 to find sensitive data in Tor's memory space if you have enough
3806 permissions. Bugfix on 0.0.2pre9.
3808 o Major bugfixes (crashes):
3809 - Prevent calls to Libevent from inside Libevent log handlers.
3810 This had potential to cause a nasty set of crashes, especially
3811 if running Libevent with debug logging enabled, and running
3812 Tor with a controller watching for low-severity log messages.
3813 Bugfix on 0.1.0.2-rc. Fixes bug 2190.
3814 - Add a check for SIZE_T_MAX to tor_realloc() to try to avoid
3815 underflow errors there too. Fixes the other part of bug 2324.
3816 - Fix a bug where we would assert if we ever had a
3817 cached-descriptors.new file (or another file read directly into
3818 memory) of exactly SIZE_T_CEILING bytes. Fixes bug 2326; bugfix
3819 on 0.2.1.25. Found by doorss.
3820 - Fix some potential asserts and parsing issues with grossly
3821 malformed router caches. Fixes bug 2352; bugfix on Tor 0.2.1.27.
3824 o Minor bugfixes (other):
3825 - Fix a bug with handling misformed replies to reverse DNS lookup
3826 requests in DNSPort. Bugfix on Tor 0.2.0.1-alpha. Related to a
3827 bug reported by doorss.
3828 - Fix compilation on mingw when a pthreads compatibility library
3829 has been installed. (We don't want to use it, so we shouldn't
3830 be including pthread.h.) Fixes bug 2313; bugfix on 0.1.0.1-rc.
3831 - Fix a bug where we would declare that we had run out of virtual
3832 addresses when the address space was only half-exhausted. Bugfix
3834 - Correctly handle the case where AutomapHostsOnResolve is set but
3835 no virtual addresses are available. Fixes bug 2328; bugfix on
3836 0.1.2.1-alpha. Bug found by doorss.
3837 - Correctly handle wrapping around to when we run out of virtual
3838 address space. Found by cypherpunks, bugfix on 0.2.0.5-alpha.
3839 - The 0.2.1.28 tarball was missing src/common/OpenBSD_malloc_Linux.c
3840 because we built it with a too-old version of automake. Thus that
3841 release broke ./configure --enable-openbsd-malloc, which is popular
3842 among really fast exit relays on Linux.
3845 - Update to the January 1 2011 Maxmind GeoLite Country database.
3846 - Introduce output size checks on all of our decryption functions.
3849 - Tor does not build packages correctly with Automake 1.6 and earlier;
3850 added a check to Makefile.am to make sure that we're building with
3851 Automake 1.7 or later.
3854 Changes in version 0.2.2.20-alpha - 2010-12-17
3855 Tor 0.2.2.20-alpha does some code cleanup to reduce the risk of remotely
3856 exploitable bugs. We also fix a variety of other significant bugs,
3857 change the IP address for one of our directory authorities, and update
3858 the minimum version that Tor relays must run to join the network.
3861 - Fix a remotely exploitable bug that could be used to crash instances
3862 of Tor remotely by overflowing on the heap. Remote-code execution
3863 hasn't been confirmed, but can't be ruled out. Everyone should
3864 upgrade. Bugfix on the 0.1.1 series and later.
3865 - Fix a bug that could break accounting on 64-bit systems with large
3866 time_t values, making them hibernate for impossibly long intervals.
3867 Fixes bug 2146. Bugfix on 0.0.9pre6; fix by boboper.
3868 - Fix a logic error in directory_fetches_from_authorities() that
3869 would cause all _non_-exits refusing single-hop-like circuits
3870 to fetch from authorities, when we wanted to have _exits_ fetch
3871 from authorities. Fixes more of 2097. Bugfix on 0.2.2.16-alpha;
3873 - Fix a stream fairness bug that would cause newer streams on a given
3874 circuit to get preference when reading bytes from the origin or
3875 destination. Fixes bug 2210. Fix by Mashael AlSabah. This bug was
3876 introduced before the first Tor release, in svn revision r152.
3878 o Directory authority changes:
3879 - Change IP address and ports for gabelmoo (v3 directory authority).
3882 - Avoid crashes when AccountingMax is set on clients. Fixes bug 2235.
3883 Bugfix on 0.2.2.18-alpha. Diagnosed by boboper.
3884 - Fix an off-by-one error in calculating some controller command
3885 argument lengths. Fortunately, this mistake is harmless since
3886 the controller code does redundant NUL termination too. Found by
3887 boboper. Bugfix on 0.1.1.1-alpha.
3888 - Do not dereference NULL if a bridge fails to build its
3889 extra-info descriptor. Found by an anonymous commenter on
3890 Trac. Bugfix on 0.2.2.19-alpha.
3893 - Update to the December 1 2010 Maxmind GeoLite Country database.
3894 - Directory authorities now reject relays running any versions of
3895 Tor between 0.2.1.3-alpha and 0.2.1.18 inclusive; they have
3896 known bugs that keep RELAY_EARLY cells from working on rendezvous
3897 circuits. Followup to fix for bug 2081.
3898 - Directory authorities now reject relays running any version of Tor
3899 older than 0.2.0.26-rc. That version is the earliest that fetches
3900 current directory information correctly. Fixes bug 2156.
3901 - Report only the top 10 ports in exit-port stats in order not to
3902 exceed the maximum extra-info descriptor length of 50 KB. Implements
3906 Changes in version 0.2.1.28 - 2010-12-17
3907 Tor 0.2.1.28 does some code cleanup to reduce the risk of remotely
3908 exploitable bugs. We also took this opportunity to change the IP address
3909 for one of our directory authorities, and to update the geoip database
3913 - Fix a remotely exploitable bug that could be used to crash instances
3914 of Tor remotely by overflowing on the heap. Remote-code execution
3915 hasn't been confirmed, but can't be ruled out. Everyone should
3916 upgrade. Bugfix on the 0.1.1 series and later.
3918 o Directory authority changes:
3919 - Change IP address and ports for gabelmoo (v3 directory authority).
3922 - Update to the December 1 2010 Maxmind GeoLite Country database.
3925 Changes in version 0.2.1.27 - 2010-11-23
3926 Yet another OpenSSL security patch broke its compatibility with Tor:
3927 Tor 0.2.1.27 makes relays work with openssl 0.9.8p and 1.0.0.b. We
3928 also took this opportunity to fix several crash bugs, integrate a new
3929 directory authority, and update the bundled GeoIP database.
3932 - Resolve an incompatibility with OpenSSL 0.9.8p and OpenSSL 1.0.0b:
3933 No longer set the tlsext_host_name extension on server SSL objects;
3934 but continue to set it on client SSL objects. Our goal in setting
3935 it was to imitate a browser, not a vhosting server. Fixes bug 2204;
3936 bugfix on 0.2.1.1-alpha.
3937 - Do not log messages to the controller while shrinking buffer
3938 freelists. Doing so would sometimes make the controller connection
3939 try to allocate a buffer chunk, which would mess up the internals
3940 of the freelist and cause an assertion failure. Fixes bug 1125;
3941 fixed by Robert Ransom. Bugfix on 0.2.0.16-alpha.
3942 - Learn our external IP address when we're a relay or bridge, even if
3943 we set PublishServerDescriptor to 0. Bugfix on 0.2.0.3-alpha,
3944 where we introduced bridge relays that don't need to publish to
3945 be useful. Fixes bug 2050.
3946 - Do even more to reject (and not just ignore) annotations on
3947 router descriptors received anywhere but from the cache. Previously
3948 we would ignore such annotations at first, but cache them to disk
3949 anyway. Bugfix on 0.2.0.8-alpha. Found by piebeer.
3950 - When you're using bridges and your network goes away and your
3951 bridges get marked as down, recover when you attempt a new socks
3952 connection (if the network is back), rather than waiting up to an
3953 hour to try fetching new descriptors for your bridges. Bugfix on
3954 0.2.0.3-alpha; fixes bug 1981.
3957 - Move to the November 2010 Maxmind GeoLite country db (rather
3958 than the June 2009 ip-to-country GeoIP db) for our statistics that
3959 count how many users relays are seeing from each country. Now we'll
3960 have more accurate data, especially for many African countries.
3962 o New directory authorities:
3963 - Set up maatuska (run by Linus Nordberg) as the eighth v3 directory
3967 - Fix an assertion failure that could occur in directory caches or
3968 bridge users when using a very short voting interval on a testing
3969 network. Diagnosed by Robert Hogan. Fixes bug 1141; bugfix on
3971 - Enforce multiplicity rules when parsing annotations. Bugfix on
3972 0.2.0.8-alpha. Found by piebeer.
3973 - Allow handshaking OR connections to take a full KeepalivePeriod
3974 seconds to handshake. Previously, we would close them after
3975 IDLE_OR_CONN_TIMEOUT (180) seconds, the same timeout as if they
3976 were open. Bugfix on 0.2.1.26; fixes bug 1840. Thanks to mingw-san
3978 - When building with --enable-gcc-warnings on OpenBSD, disable
3979 warnings in system headers. This makes --enable-gcc-warnings
3980 pass on OpenBSD 4.8.
3983 - Exit nodes didn't recognize EHOSTUNREACH as a plausible error code,
3984 and so sent back END_STREAM_REASON_MISC. Clients now recognize a new
3985 stream ending reason for this case: END_STREAM_REASON_NOROUTE.
3986 Servers can start sending this code when enough clients recognize
3987 it. Bugfix on 0.1.0.1-rc; fixes part of bug 1793.
3988 - Build correctly on mingw with more recent versions of OpenSSL 0.9.8.
3989 Patch from mingw-san.
3992 - Remove the old debian/ directory from the main Tor distribution.
3993 The official Tor-for-debian git repository lives at the URL
3994 https://git.torproject.org/debian/tor.git
3995 - Stop shipping the old doc/website/ directory in the tarball. We
3996 changed the website format in late 2010, and what we shipped in
3997 0.2.1.26 really wasn't that useful anyway.
4000 Changes in version 0.2.2.19-alpha - 2010-11-22
4001 Yet another OpenSSL security patch broke its compatibility with Tor:
4002 Tor 0.2.2.19-alpha makes relays work with OpenSSL 0.9.8p and 1.0.0.b.
4005 - Resolve an incompatibility with OpenSSL 0.9.8p and OpenSSL 1.0.0b:
4006 No longer set the tlsext_host_name extension on server SSL objects;
4007 but continue to set it on client SSL objects. Our goal in setting
4008 it was to imitate a browser, not a vhosting server. Fixes bug 2204;
4009 bugfix on 0.2.1.1-alpha.
4012 - Try harder not to exceed the maximum length of 50 KB when writing
4013 statistics to extra-info descriptors. This bug was triggered by very
4014 fast relays reporting exit-port, entry, and dirreq statistics.
4015 Reported by Olaf Selke. Bugfix on 0.2.2.1-alpha. Fixes bug 2183.
4016 - Publish a router descriptor even if generating an extra-info
4017 descriptor fails. Previously we would not publish a router
4018 descriptor without an extra-info descriptor; this can cause fast
4019 exit relays collecting exit-port statistics to drop from the
4020 consensus. Bugfix on 0.1.2.9-rc; fixes bug 2195.
4023 Changes in version 0.2.2.18-alpha - 2010-11-16
4024 Tor 0.2.2.18-alpha fixes several crash bugs that have been nagging
4025 us lately, makes unpublished bridge relays able to detect their IP
4026 address, and fixes a wide variety of other bugs to get us much closer
4027 to a stable release.
4030 - Do even more to reject (and not just ignore) annotations on
4031 router descriptors received anywhere but from the cache. Previously
4032 we would ignore such annotations at first, but cache them to disk
4033 anyway. Bugfix on 0.2.0.8-alpha. Found by piebeer.
4034 - Do not log messages to the controller while shrinking buffer
4035 freelists. Doing so would sometimes make the controller connection
4036 try to allocate a buffer chunk, which would mess up the internals
4037 of the freelist and cause an assertion failure. Fixes bug 1125;
4038 fixed by Robert Ransom. Bugfix on 0.2.0.16-alpha.
4039 - Learn our external IP address when we're a relay or bridge, even if
4040 we set PublishServerDescriptor to 0. Bugfix on 0.2.0.3-alpha,
4041 where we introduced bridge relays that don't need to publish to
4042 be useful. Fixes bug 2050.
4043 - Maintain separate TLS contexts and certificates for incoming and
4044 outgoing connections in bridge relays. Previously we would use the
4045 same TLS contexts and certs for incoming and outgoing connections.
4046 Bugfix on 0.2.0.3-alpha; addresses bug 988.
4047 - Maintain separate identity keys for incoming and outgoing TLS
4048 contexts in bridge relays. Previously we would use the same
4049 identity keys for incoming and outgoing TLS contexts. Bugfix on
4050 0.2.0.3-alpha; addresses the other half of bug 988.
4051 - Avoid an assertion failure when we as an authority receive a
4052 duplicate upload of a router descriptor that we already have,
4053 but which we previously considered an obsolete descriptor.
4054 Fixes another case of bug 1776. Bugfix on 0.2.2.16-alpha.
4055 - Avoid a crash bug triggered by looking at a dangling pointer while
4056 setting the network status consensus. Found by Robert Ransom.
4057 Bugfix on 0.2.2.17-alpha. Fixes bug 2097.
4058 - Fix a logic error where servers that _didn't_ act as exits would
4059 try to keep their server lists more aggressively up to date than
4060 exits, when it was supposed to be the other way around. Bugfix
4063 o Minor bugfixes (on Tor 0.2.1.x and earlier):
4064 - When we're trying to guess whether we know our IP address as
4065 a relay, we would log various ways that we failed to guess
4066 our address, but never log that we ended up guessing it
4067 successfully. Now add a log line to help confused and anxious
4068 relay operators. Bugfix on 0.1.2.1-alpha; fixes bug 1534.
4069 - Bring the logic that gathers routerinfos and assesses the
4070 acceptability of circuits into line. This prevents a Tor OP from
4071 getting locked in a cycle of choosing its local OR as an exit for a
4072 path (due to a .exit request) and then rejecting the circuit because
4073 its OR is not listed yet. It also prevents Tor clients from using an
4074 OR running in the same instance as an exit (due to a .exit request)
4075 if the OR does not meet the same requirements expected of an OR
4076 running elsewhere. Fixes bug 1859; bugfix on 0.1.0.1-rc.
4077 - Correctly describe errors that occur when generating a TLS object.
4078 Previously we would attribute them to a failure while generating a
4079 TLS context. Patch by Robert Ransom. Bugfix on 0.1.0.4-rc; fixes
4081 - Enforce multiplicity rules when parsing annotations. Bugfix on
4082 0.2.0.8-alpha. Found by piebeer.
4083 - Fix warnings that newer versions of autoconf produced during
4084 ./autogen.sh. These warnings appear to be harmless in our case,
4085 but they were extremely verbose. Fixes bug 2020.
4087 o Minor bugfixes (on Tor 0.2.2.x):
4088 - Enable protection of small arrays whenever we build with gcc
4089 hardening features, not only when also building with warnings
4090 enabled. Fixes bug 2031; bugfix on 0.2.2.14-alpha. Reported by keb.
4093 - Make hidden services work better in private Tor networks by not
4094 requiring any uptime to join the hidden service descriptor
4095 DHT. Implements ticket 2088.
4096 - Rate-limit the "your application is giving Tor only an IP address"
4097 warning. Addresses bug 2000; bugfix on 0.0.8pre2.
4098 - When AllowSingleHopExits is set, print a warning to explain to the
4099 relay operator why most clients are avoiding her relay.
4100 - Update to the November 1 2010 Maxmind GeoLite Country database.
4102 o Code simplifications and refactoring:
4103 - When we fixed bug 1038 we had to put in a restriction not to send
4104 RELAY_EARLY cells on rend circuits. This was necessary as long
4105 as relays using Tor 0.2.1.3-alpha through 0.2.1.18-alpha were
4106 active. Now remove this obsolete check. Resolves bug 2081.
4107 - Some options used different conventions for uppercasing of acronyms
4108 when comparing manpage and source. Fix those in favor of the
4109 manpage, as it makes sense to capitalize acronyms.
4110 - Remove the torrc.complete file. It hasn't been kept up to date
4111 and users will have better luck checking out the manpage.
4112 - Remove the obsolete "NoPublish" option; it has been flagged
4113 as obsolete and has produced a warning since 0.1.1.18-rc.
4114 - Remove everything related to building the expert bundle for OS X.
4115 It has confused many users, doesn't work right on OS X 10.6,
4116 and is hard to get rid of once installed. Resolves bug 1274.
4119 Changes in version 0.2.2.17-alpha - 2010-09-30
4120 Tor 0.2.2.17-alpha introduces a feature to make it harder for clients
4121 to use one-hop circuits (which can put the exit relays at higher risk,
4122 plus unbalance the network); fixes a big bug in bandwidth accounting
4123 for relays that want to limit their monthly bandwidth use; fixes a
4124 big pile of bugs in how clients tolerate temporary network failure;
4125 and makes our adaptive circuit build timeout feature (which improves
4126 client performance if your network is fast while not breaking things
4127 if your network is slow) better handle bad networks.
4130 - Exit relays now try harder to block exit attempts from unknown
4131 relays, to make it harder for people to use them as one-hop proxies
4132 a la tortunnel. Controlled by the refuseunknownexits consensus
4133 parameter (currently enabled), or you can override it on your
4134 relay with the RefuseUnknownExits torrc option. Resolves bug 1751.
4136 o Major bugfixes (0.2.1.x and earlier):
4137 - Fix a bug in bandwidth accounting that could make us use twice
4138 the intended bandwidth when our interval start changes due to
4139 daylight saving time. Now we tolerate skew in stored vs computed
4140 interval starts: if the start of the period changes by no more than
4141 50% of the period's duration, we remember bytes that we transferred
4142 in the old period. Fixes bug 1511; bugfix on 0.0.9pre5.
4143 - Always search the Windows system directory for system DLLs, and
4144 nowhere else. Bugfix on 0.1.1.23; fixes bug 1954.
4145 - When you're using bridges and your network goes away and your
4146 bridges get marked as down, recover when you attempt a new socks
4147 connection (if the network is back), rather than waiting up to an
4148 hour to try fetching new descriptors for your bridges. Bugfix on
4149 0.2.0.3-alpha; fixes bug 1981.
4151 o Major bugfixes (on 0.2.2.x):
4152 - Fix compilation on Windows. Bugfix on 0.2.2.16-alpha; related to
4154 - Fix a segfault that could happen when operating a bridge relay with
4155 no GeoIP database set. Fixes bug 1964; bugfix on 0.2.2.15-alpha.
4156 - The consensus bandwidth-weights (used by clients to choose fast
4157 relays) entered an unexpected edge case in September where
4158 Exits were much scarcer than Guards, resulting in bad weight
4159 recommendations. Now we compute them using new constraints that
4160 should succeed in all cases. Also alter directory authorities to
4161 not include the bandwidth-weights line if they fail to produce
4162 valid values. Fixes bug 1952; bugfix on 0.2.2.10-alpha.
4163 - When weighting bridges during path selection, we used to trust
4164 the bandwidths they provided in their descriptor, only capping them
4165 at 10MB/s. This turned out to be problematic for two reasons:
4166 Bridges could claim to handle a lot more traffic then they
4167 actually would, thus making more clients pick them and have a
4168 pretty effective DoS attack. The other issue is that new bridges
4169 that might not have a good estimate for their bw capacity yet
4170 would not get used at all unless no other bridges are available
4171 to a client. Fixes bug 1912; bugfix on 0.2.2.7-alpha.
4173 o Major bugfixes (on the circuit build timeout feature, 0.2.2.x):
4174 - Ignore cannibalized circuits when recording circuit build times.
4175 This should provide for a minor performance improvement for hidden
4176 service users using 0.2.2.14-alpha, and should remove two spurious
4177 notice log messages. Bugfix on 0.2.2.14-alpha; fixes bug 1740.
4178 - Simplify the logic that causes us to decide if the network is
4179 unavailable for purposes of recording circuit build times. If we
4180 receive no cells whatsoever for the entire duration of a circuit's
4181 full measured lifetime, the network is probably down. Also ignore
4182 one-hop directory fetching circuit timeouts when calculating our
4183 circuit build times. These changes should hopefully reduce the
4184 cases where we see ridiculous circuit build timeouts for people
4185 with spotty wireless connections. Fixes part of bug 1772; bugfix
4187 - Prevent the circuit build timeout from becoming larger than
4188 the maximum build time we have ever seen. Also, prevent the time
4189 period for measurement circuits from becoming larger than twice that
4190 value. Fixes the other part of bug 1772; bugfix on 0.2.2.2-alpha.
4193 - When we run out of directory information such that we can't build
4194 circuits, but then get enough that we can build circuits, log when
4195 we actually construct a circuit, so the user has a better chance of
4196 knowing what's going on. Fixes bug 1362.
4197 - Be more generous with how much bandwidth we'd use up (with
4198 accounting enabled) before entering "soft hibernation". Previously,
4199 we'd refuse new connections and circuits once we'd used up 95% of
4200 our allotment. Now, we use up 95% of our allotment, AND make sure
4201 that we have no more than 500MB (or 3 hours of expected traffic,
4202 whichever is lower) remaining before we enter soft hibernation.
4203 - If we've configured EntryNodes and our network goes away and/or all
4204 our entrynodes get marked down, optimistically retry them all when
4205 a new socks application request appears. Fixes bug 1882.
4206 - Add some more defensive programming for architectures that can't
4207 handle unaligned integer accesses. We don't know of any actual bugs
4208 right now, but that's the best time to fix them. Fixes bug 1943.
4209 - Support line continuations in the torrc config file. If a line
4210 ends with a single backslash character, the newline is ignored, and
4211 the configuration value is treated as continuing on the next line.
4214 o Minor bugfixes (on 0.2.1.x and earlier):
4215 - For bandwidth accounting, calculate our expected bandwidth rate
4216 based on the time during which we were active and not in
4217 soft-hibernation during the last interval. Previously, we were
4218 also considering the time spent in soft-hibernation. If this
4219 was a long time, we would wind up underestimating our bandwidth
4220 by a lot, and skewing our wakeup time towards the start of the
4221 accounting interval. Fixes bug 1789. Bugfix on 0.0.9pre5.
4223 o Minor bugfixes (on 0.2.2.x):
4224 - Resume generating CIRC FAILED REASON=TIMEOUT control port messages,
4225 which were disabled by the circuit build timeout changes in
4226 0.2.2.14-alpha. Bugfix on 0.2.2.14-alpha; fixes bug 1739.
4227 - Make sure we don't warn about missing bandwidth weights when
4228 choosing bridges or other relays not in the consensus. Bugfix on
4229 0.2.2.10-alpha; fixes bug 1805.
4230 - In our logs, do not double-report signatures from unrecognized
4231 authorities both as "from unknown authority" and "not
4232 present". Fixes bug 1956, bugfix on 0.2.2.16-alpha.
4235 Changes in version 0.2.2.16-alpha - 2010-09-17
4236 Tor 0.2.2.16-alpha fixes a variety of old stream fairness bugs (most
4237 evident at exit relays), and also continues to resolve all the little
4238 bugs that have been filling up trac lately.
4240 o Major bugfixes (stream-level fairness):
4241 - When receiving a circuit-level SENDME for a blocked circuit, try
4242 to package cells fairly from all the streams that had previously
4243 been blocked on that circuit. Previously, we had started with the
4244 oldest stream, and allowed each stream to potentially exhaust
4245 the circuit's package window. This gave older streams on any
4246 given circuit priority over newer ones. Fixes bug 1937. Detected
4247 originally by Camilo Viecco. This bug was introduced before the
4248 first Tor release, in svn commit r152: it is the new winner of
4249 the longest-lived bug prize.
4250 - When the exit relay got a circuit-level sendme cell, it started
4251 reading on the exit streams, even if had 500 cells queued in the
4252 circuit queue already, so the circuit queue just grew and grew in
4253 some cases. We fix this by not re-enabling reading on receipt of a
4254 sendme cell when the cell queue is blocked. Fixes bug 1653. Bugfix
4255 on 0.2.0.1-alpha. Detected by Mashael AlSabah. Original patch by
4257 - Newly created streams were allowed to read cells onto circuits,
4258 even if the circuit's cell queue was blocked and waiting to drain.
4259 This created potential unfairness, as older streams would be
4260 blocked, but newer streams would gladly fill the queue completely.
4261 We add code to detect this situation and prevent any stream from
4262 getting more than one free cell. Bugfix on 0.2.0.1-alpha. Partially
4266 - Update to the September 1 2010 Maxmind GeoLite Country database.
4267 - Warn when CookieAuthFileGroupReadable is set but CookieAuthFile is
4268 not. This would lead to a cookie that is still not group readable.
4269 Closes bug 1843. Suggested by katmagic.
4270 - When logging a rate-limited warning, we now mention how many messages
4271 got suppressed since the last warning.
4272 - Add new "perconnbwrate" and "perconnbwburst" consensus params to
4273 do individual connection-level rate limiting of clients. The torrc
4274 config options with the same names trump the consensus params, if
4275 both are present. Replaces the old "bwconnrate" and "bwconnburst"
4276 consensus params which were broken from 0.2.2.7-alpha through
4277 0.2.2.14-alpha. Closes bug 1947.
4278 - When a router changes IP address or port, authorities now launch
4279 a new reachability test for it. Implements ticket 1899.
4280 - Make the formerly ugly "2 unknown, 7 missing key, 0 good, 0 bad,
4281 2 no signature, 4 required" messages about consensus signatures
4282 easier to read, and make sure they get logged at the same severity
4283 as the messages explaining which keys are which. Fixes bug 1290.
4284 - Don't warn when we have a consensus that we can't verify because
4285 of missing certificates, unless those certificates are ones
4286 that we have been trying and failing to download. Fixes bug 1145.
4287 - If you configure your bridge with a known identity fingerprint,
4288 and the bridge authority is unreachable (as it is in at least
4289 one country now), fall back to directly requesting the descriptor
4290 from the bridge. Finishes the feature started in 0.2.0.10-alpha;
4292 - When building with --enable-gcc-warnings on OpenBSD, disable
4293 warnings in system headers. This makes --enable-gcc-warnings
4294 pass on OpenBSD 4.8.
4296 o Minor bugfixes (on 0.2.1.x and earlier):
4297 - Authorities will now attempt to download consensuses if their
4298 own efforts to make a live consensus have failed. This change
4299 means authorities that restart will fetch a valid consensus, and
4300 it means authorities that didn't agree with the current consensus
4301 will still fetch and serve it if it has enough signatures. Bugfix
4302 on 0.2.0.9-alpha; fixes bug 1300.
4303 - Ensure DNS requests launched by "RESOLVE" commands from the
4304 controller respect the __LeaveStreamsUnattached setconf options. The
4305 same goes for requests launched via DNSPort or transparent
4306 proxying. Bugfix on 0.2.0.1-alpha; fixes bug 1525.
4307 - Allow handshaking OR connections to take a full KeepalivePeriod
4308 seconds to handshake. Previously, we would close them after
4309 IDLE_OR_CONN_TIMEOUT (180) seconds, the same timeout as if they
4310 were open. Bugfix on 0.2.1.26; fixes bug 1840. Thanks to mingw-san
4312 - Rate-limit "Failed to hand off onionskin" warnings.
4313 - Never relay a cell for a circuit we have already destroyed.
4314 Between marking a circuit as closeable and finally closing it,
4315 it may have been possible for a few queued cells to get relayed,
4316 even though they would have been immediately dropped by the next
4317 OR in the circuit. Fixes bug 1184; bugfix on 0.2.0.1-alpha.
4318 - Never queue a cell for a circuit that's already been marked
4320 - Never vote for a server as "Running" if we have a descriptor for
4321 it claiming to be hibernating, and that descriptor was published
4322 more recently than our last contact with the server. Bugfix on
4323 0.2.0.3-alpha; fixes bug 911.
4324 - Squash a compile warning on OpenBSD. Reported by Tas; fixes
4327 o Minor bugfixes (on 0.2.2.x):
4328 - Fix a regression introduced in 0.2.2.7-alpha that marked relays
4329 down if a directory fetch fails and you've configured either
4330 bridges or EntryNodes. The intent was to mark the relay as down
4331 _unless_ you're using bridges or EntryNodes, since if you are
4332 then you could quickly run out of entry points.
4333 - Fix the Windows directory-listing code. A bug introduced in
4334 0.2.2.14-alpha could make Windows directory servers forget to load
4335 some of their cached v2 networkstatus files.
4336 - Really allow clients to use relays as bridges. Fixes bug 1776;
4337 bugfix on 0.2.2.15-alpha.
4338 - Demote a warn to info that happens when the CellStatistics option
4339 was just enabled. Bugfix on 0.2.2.15-alpha; fixes bug 1921.
4340 Reported by Moritz Bartl.
4341 - On Windows, build correctly either with or without Unicode support.
4342 This is necessary so that Tor can support fringe platforms like
4343 Windows 98 (which has no Unicode), or Windows CE (which has no
4344 non-Unicode). Bugfix on 0.2.2.14-alpha; fixes bug 1797.
4347 - Add a unit test for cross-platform directory-listing code.
4350 Changes in version 0.2.2.15-alpha - 2010-08-18
4351 Tor 0.2.2.15-alpha fixes a big bug in hidden service availability,
4352 fixes a variety of other bugs that were preventing performance
4353 experiments from moving forward, fixes several bothersome memory leaks,
4354 and generally closes a lot of smaller bugs that have been filling up
4358 - Stop assigning the HSDir flag to relays that disable their
4359 DirPort (and thus will refuse to answer directory requests). This
4360 fix should dramatically improve the reachability of hidden services:
4361 hidden services and hidden service clients pick six HSDir relays
4362 to store and retrieve the hidden service descriptor, and currently
4363 about half of the HSDir relays will refuse to work. Bugfix on
4364 0.2.0.10-alpha; fixes part of bug 1693.
4365 - The PerConnBWRate and Burst config options, along with the
4366 bwconnrate and bwconnburst consensus params, initialized each conn's
4367 token bucket values only when the connection is established. Now we
4368 update them if the config options change, and update them every time
4369 we get a new consensus. Otherwise we can encounter an ugly edge
4370 case where we initialize an OR conn to client-level bandwidth,
4371 but then later the relay joins the consensus and we leave it
4372 throttled. Bugfix on 0.2.2.7-alpha; fixes bug 1830.
4373 - Fix a regression that caused Tor to rebind its ports if it receives
4374 SIGHUP while hibernating. Bugfix in 0.1.1.6-alpha; closes bug 919.
4377 - Lower the maximum weighted-fractional-uptime cutoff to 98%. This
4378 should give us approximately 40-50% more Guard-flagged nodes,
4379 improving the anonymity the Tor network can provide and also
4380 decreasing the dropoff in throughput that relays experience when
4381 they first get the Guard flag.
4382 - Allow enabling or disabling the *Statistics config options while
4386 - Update to the August 1 2010 Maxmind GeoLite Country database.
4387 - Have the controller interface give a more useful message than
4388 "Internal Error" in response to failed GETINFO requests.
4389 - Warn when the same option is provided more than once in a torrc
4390 file, on the command line, or in a single SETCONF statement, and
4391 the option is one that only accepts a single line. Closes bug 1384.
4392 - Build correctly on mingw with more recent versions of OpenSSL 0.9.8.
4393 Patch from mingw-san.
4394 - Add support for the country code "{??}" in torrc options like
4395 ExcludeNodes, to indicate all routers of unknown country. Closes
4397 - Relays report the number of bytes spent on answering directory
4398 requests in extra-info descriptors similar to {read,write}-history.
4399 Implements enhancement 1790.
4401 o Minor bugfixes (on 0.2.1.x and earlier):
4402 - Complain if PublishServerDescriptor is given multiple arguments that
4403 include 0 or 1. This configuration will be rejected in the future.
4404 Bugfix on 0.2.0.1-alpha; closes bug 1107.
4405 - Disallow BridgeRelay 1 and ORPort 0 at once in the configuration.
4406 Bugfix on 0.2.0.13-alpha; closes bug 928.
4407 - Change "Application request when we're believed to be offline."
4408 notice to "Application request when we haven't used client
4409 functionality lately.", to clarify that it's not an error. Bugfix
4410 on 0.0.9.3; fixes bug 1222.
4411 - Fix a bug in the controller interface where "GETINFO ns/asdaskljkl"
4412 would return "551 Internal error" rather than "552 Unrecognized key
4413 ns/asdaskljkl". Bugfix on 0.1.2.3-alpha.
4414 - Users can't configure a regular relay to be their bridge. It didn't
4415 work because when Tor fetched the bridge descriptor, it found
4416 that it already had it, and didn't realize that the purpose of the
4417 descriptor had changed. Now we replace routers with a purpose other
4418 than bridge with bridge descriptors when fetching them. Bugfix on
4419 0.1.1.9-alpha. Bug 1776 not yet fixed because now we immediately
4420 refetch the descriptor with router purpose 'general', disabling
4422 - Fix a rare bug in rend_fn unit tests: we would fail a test when
4423 a randomly generated port is 0. Diagnosed by Matt Edman. Bugfix
4424 on 0.2.0.10-alpha; fixes bug 1808.
4425 - Exit nodes didn't recognize EHOSTUNREACH as a plausible error code,
4426 and so sent back END_STREAM_REASON_MISC. Clients now recognize a new
4427 stream ending reason for this case: END_STREAM_REASON_NOROUTE.
4428 Servers can start sending this code when enough clients recognize
4429 it. Also update the spec to reflect this new reason. Bugfix on
4430 0.1.0.1-rc; fixes part of bug 1793.
4431 - Delay geoip stats collection by bridges for 6 hours, not 2 hours,
4432 when we switch from being a public relay to a bridge. Otherwise
4433 there will still be clients that see the relay in their consensus,
4434 and the stats will end up wrong. Bugfix on 0.2.1.15-rc; fixes bug
4436 - Instead of giving an assertion failure on an internal mismatch
4437 on estimated freelist size, just log a BUG warning and try later.
4438 Mitigates but does not fix bug 1125.
4439 - Fix an assertion failure that could occur in caches or bridge users
4440 when using a very short voting interval on a testing network.
4441 Diagnosed by Robert Hogan. Fixes bug 1141; bugfix on 0.2.0.8-alpha.
4443 o Minor bugfixes (on 0.2.2.x):
4444 - Alter directory authorities to always consider Exit-flagged nodes
4445 as potential Guard nodes in their votes. The actual decision to
4446 use Exits as Guards is done in the consensus bandwidth weights.
4447 Fixes bug 1294; bugfix on 0.2.2.10-alpha.
4448 - When the controller is reporting the purpose of circuits that
4449 didn't finish building before the circuit build timeout, it was
4450 printing UNKNOWN_13. Now print EXPIRED. Bugfix on 0.2.2.14-alpha.
4451 - Our libevent version parsing code couldn't handle versions like
4452 1.4.14b-stable and incorrectly warned the user about using an
4453 old and broken version of libevent. Treat 1.4.14b-stable like
4454 1.4.14-stable when parsing the version. Fixes bug 1731; bugfix
4456 - Don't use substitution references like $(VAR:MOD) when
4457 $(asciidoc_files) is empty -- make(1) on NetBSD transforms
4458 '$(:x)' to 'x' rather than the empty string. This bites us in
4459 doc/ when configured with --disable-asciidoc. Bugfix on
4460 0.2.2.9-alpha; fixes bug 1773.
4461 - Remove a spurious hidden service server-side log notice about
4462 "Ancient non-dirty circuits". Bugfix on 0.2.2.14-alpha; fixes
4464 - Fix compilation with --with-dmalloc set. Bugfix on 0.2.2.6-alpha;
4466 - Correctly report written bytes on linked connections. Found while
4467 implementing 1790. Bugfix on 0.2.2.4-alpha.
4468 - Fix three memory leaks: one in circuit_build_times_parse_state(),
4469 one in dirvote_add_signatures_to_pending_consensus(), and one every
4470 time we parse a v3 network consensus. Bugfixes on 0.2.2.14-alpha,
4471 0.2.2.6-alpha, and 0.2.2.10-alpha respectively; fixes bug 1831.
4473 o Code simplifications and refactoring:
4474 - Take a first step towards making or.h smaller by splitting out
4475 function definitions for all source files in src/or/. Leave
4476 structures and defines in or.h for now.
4477 - Remove a bunch of unused function declarations as well as a block of
4478 #if 0'd code from the unit tests. Closes bug 1824.
4479 - New unit tests for exit-port history statistics; refactored exit
4480 statistics code to be more easily tested.
4481 - Remove the old debian/ directory from the main Tor distribution.
4482 The official Tor-for-debian git repository lives at the URL
4483 https://git.torproject.org/debian/tor.git
4486 Changes in version 0.2.2.14-alpha - 2010-07-12
4487 Tor 0.2.2.14-alpha greatly improves client-side handling of
4488 circuit build timeouts, which are used to estimate speed and improve
4489 performance. We also move to a much better GeoIP database, port Tor to
4490 Windows CE, introduce new compile flags that improve code security,
4491 add an eighth v3 directory authority, and address a lot of more
4495 - Tor directory authorities no longer crash when started with a
4496 cached-microdesc-consensus file in their data directory. Bugfix
4497 on 0.2.2.6-alpha; fixes bug 1532.
4498 - Treat an unset $HOME like an empty $HOME rather than triggering an
4499 assert. Bugfix on 0.0.8pre1; fixes bug 1522.
4500 - Ignore negative and large circuit build timeout values that can
4501 happen during a suspend or hibernate. These values caused various
4502 asserts to fire. Bugfix on 0.2.2.2-alpha; fixes bug 1245.
4503 - Alter calculation of Pareto distribution parameter 'Xm' for
4504 Circuit Build Timeout learning to use the weighted average of the
4505 top N=3 modes (because we have three entry guards). Considering
4506 multiple modes should improve the timeout calculation in some cases,
4507 and prevent extremely high timeout values. Bugfix on 0.2.2.2-alpha;
4509 - Alter calculation of Pareto distribution parameter 'Alpha' to use a
4510 right censored distribution model. This approach improves over the
4511 synthetic timeout generation approach that was producing insanely
4512 high timeout values. Now we calculate build timeouts using truncated
4513 times. Bugfix on 0.2.2.2-alpha; fixes bugs 1245 and 1335.
4514 - Do not close circuits that are under construction when they reach
4515 the circuit build timeout. Instead, leave them building (but do not
4516 use them) for up until the time corresponding to the 95th percentile
4517 on the Pareto CDF or 60 seconds, whichever is greater. This is done
4518 to provide better data for the new Pareto model. This percentile
4519 can be controlled by the consensus.
4522 - Move to the June 2010 Maxmind GeoLite country db (rather than the
4523 June 2009 ip-to-country GeoIP db) for our statistics that count
4524 how many users relays are seeing from each country. Now we have
4525 more accurate data for many African countries.
4526 - Port Tor to build and run correctly on Windows CE systems, using
4527 the wcecompat library. Contributed by Valerio Lupi.
4528 - New "--enable-gcc-hardening" ./configure flag (off by default)
4529 to turn on gcc compile time hardening options. It ensures
4530 that signed ints have defined behavior (-fwrapv), enables
4531 -D_FORTIFY_SOURCE=2 (requiring -O2), adds stack smashing protection
4532 with canaries (-fstack-protector-all), turns on ASLR protection if
4533 supported by the kernel (-fPIE, -pie), and adds additional security
4534 related warnings. Verified to work on Mac OS X and Debian Lenny.
4535 - New "--enable-linker-hardening" ./configure flag (off by default)
4536 to turn on ELF specific hardening features (relro, now). This does
4537 not work with Mac OS X or any other non-ELF binary format.
4539 o New directory authorities:
4540 - Set up maatuska (run by Linus Nordberg) as the eighth v3 directory
4544 - New config option "WarnUnsafeSocks 0" disables the warning that
4545 occurs whenever Tor receives a socks handshake using a version of
4546 the socks protocol that can only provide an IP address (rather
4547 than a hostname). Setups that do DNS locally over Tor are fine,
4548 and we shouldn't spam the logs in that case.
4549 - Convert the HACKING file to asciidoc, and add a few new sections
4550 to it, explaining how we use Git, how we make changelogs, and
4551 what should go in a patch.
4552 - Add a TIMEOUT_RATE keyword to the BUILDTIMEOUT_SET control port
4553 event, to give information on the current rate of circuit timeouts
4554 over our stored history.
4555 - Add ability to disable circuit build time learning via consensus
4556 parameter and via a LearnCircuitBuildTimeout config option. Also
4557 automatically disable circuit build time calculation if we are
4558 either a AuthoritativeDirectory, or if we fail to write our state
4559 file. Fixes bug 1296.
4560 - More gracefully handle corrupt state files, removing asserts
4561 in favor of saving a backup and resetting state.
4562 - Rename the "log.h" header to "torlog.h" so as to conflict with fewer
4566 - Build correctly on OSX with zlib 1.2.4 and higher with all warnings
4568 - When a2x fails, mention that the user could disable manpages instead
4569 of trying to fix their asciidoc installation.
4570 - Where available, use Libevent 2.0's periodic timers so that our
4571 once-per-second cleanup code gets called even more closely to
4572 once per second than it would otherwise. Fixes bug 943.
4573 - If you run a bridge that listens on multiple IP addresses, and
4574 some user configures a bridge address that uses a different IP
4575 address than your bridge writes in its router descriptor, and the
4576 user doesn't specify an identity key, their Tor would discard the
4577 descriptor because "it isn't one of our configured bridges", and
4578 fail to bootstrap. Now believe the descriptor and bootstrap anyway.
4579 Bugfix on 0.2.0.3-alpha.
4580 - If OpenSSL fails to make a duplicate of a private or public key, log
4581 an error message and try to exit cleanly. May help with debugging
4582 if bug 1209 ever remanifests.
4583 - Save a couple bytes in memory allocation every time we escape
4584 certain characters in a string. Patch from Florian Zumbiehl.
4585 - Make it explicit that we don't cannibalize one-hop circuits. This
4586 happens in the wild, but doesn't turn out to be a problem because
4587 we fortunately don't use those circuits. Many thanks to outofwords
4588 for the initial analysis and to swissknife who confirmed that
4589 two-hop circuits are actually created.
4590 - Make directory mirrors report non-zero dirreq-v[23]-shares again.
4591 Fixes bug 1564; bugfix on 0.2.2.9-alpha.
4592 - Eliminate a case where a circuit build time warning was displayed
4593 after network connectivity resumed. Bugfix on 0.2.2.2-alpha.
4596 Changes in version 0.2.1.26 - 2010-05-02
4597 Tor 0.2.1.26 addresses the recent connection and memory overload
4598 problems we've been seeing on relays, especially relays with their
4599 DirPort open. If your relay has been crashing, or you turned it off
4600 because it used too many resources, give this release a try.
4602 This release also fixes yet another instance of broken OpenSSL libraries
4603 that was causing some relays to drop out of the consensus.
4606 - Teach relays to defend themselves from connection overload. Relays
4607 now close idle circuits early if it looks like they were intended
4608 for directory fetches. Relays are also more aggressive about closing
4609 TLS connections that have no circuits on them. Such circuits are
4610 unlikely to be re-used, and tens of thousands of them were piling
4611 up at the fast relays, causing the relays to run out of sockets
4612 and memory. Bugfix on 0.2.0.22-rc (where clients started tunneling
4613 their directory fetches over TLS).
4614 - Fix SSL renegotiation behavior on OpenSSL versions like on Centos
4615 that claim to be earlier than 0.9.8m, but which have in reality
4616 backported huge swaths of 0.9.8m or 0.9.8n renegotiation
4617 behavior. Possible fix for some cases of bug 1346.
4618 - Directory mirrors were fetching relay descriptors only from v2
4619 directory authorities, rather than v3 authorities like they should.
4620 Only 2 v2 authorities remain (compared to 7 v3 authorities), leading
4621 to a serious bottleneck. Bugfix on 0.2.0.9-alpha. Fixes bug 1324.
4624 - Finally get rid of the deprecated and now harmful notion of "clique
4625 mode", where directory authorities maintain TLS connections to
4629 - In the util/threads test, no longer free the test_mutex before all
4630 worker threads have finished. Bugfix on 0.2.1.6-alpha.
4631 - The master thread could starve the worker threads quite badly on
4632 certain systems, causing them to run only partially in the allowed
4633 window. This resulted in test failures. Now the master thread sleeps
4634 occasionally for a few microseconds while the two worker-threads
4635 compete for the mutex. Bugfix on 0.2.0.1-alpha.
4638 Changes in version 0.2.2.13-alpha - 2010-04-24
4639 Tor 0.2.2.13-alpha addresses the recent connection and memory overload
4640 problems we've been seeing on relays, especially relays with their
4641 DirPort open. If your relay has been crashing, or you turned it off
4642 because it used too many resources, give this release a try.
4645 - Teach relays to defend themselves from connection overload. Relays
4646 now close idle circuits early if it looks like they were intended
4647 for directory fetches. Relays are also more aggressive about closing
4648 TLS connections that have no circuits on them. Such circuits are
4649 unlikely to be re-used, and tens of thousands of them were piling
4650 up at the fast relays, causing the relays to run out of sockets
4651 and memory. Bugfix on 0.2.0.22-rc (where clients started tunneling
4652 their directory fetches over TLS).
4655 - Finally get rid of the deprecated and now harmful notion of "clique
4656 mode", where directory authorities maintain TLS connections to
4658 - Directory authorities now do an immediate reachability check as soon
4659 as they hear about a new relay. This change should slightly reduce
4660 the time between setting up a relay and getting listed as running
4661 in the consensus. It should also improve the time between setting
4662 up a bridge and seeing use by bridge users.
4663 - Directory authorities no longer launch a TLS connection to every
4664 relay as they startup. Now that we have 2k+ descriptors cached,
4665 the resulting network hiccup is becoming a burden. Besides,
4666 authorities already avoid voting about Running for the first half
4667 hour of their uptime.
4670 Changes in version 0.2.2.12-alpha - 2010-04-20
4671 Tor 0.2.2.12-alpha fixes a critical bug in how directory authorities
4672 handle and vote on descriptors. It was causing relays to drop out of
4676 - Many relays have been falling out of the consensus lately because
4677 not enough authorities know about their descriptor for them to get
4678 a majority of votes. When we deprecated the v2 directory protocol,
4679 we got rid of the only way that v3 authorities can hear from each
4680 other about other descriptors. Now authorities examine every v3
4681 vote for new descriptors, and fetch them from that authority. Bugfix
4683 - Fix two typos in tor_vasprintf() that broke the compile on Windows,
4684 and a warning in or.h related to bandwidth_weight_rule_t that
4685 prevented clean compile on OS X. Fixes bug 1363; bugfix on
4687 - Fix a segfault on relays when DirReqStatistics is enabled
4688 and 24 hours pass. Bug found by keb. Fixes bug 1365; bugfix on
4692 - Demote a confusing TLS warning that relay operators might get when
4693 someone tries to talk to their OrPort. It is neither the operator's
4694 fault nor can they do anything about it. Fixes bug 1364; bugfix
4698 Changes in version 0.2.2.11-alpha - 2010-04-15
4699 Tor 0.2.2.11-alpha fixes yet another instance of broken OpenSSL
4700 libraries that was causing some relays to drop out of the consensus.
4703 - Directory mirrors were fetching relay descriptors only from v2
4704 directory authorities, rather than v3 authorities like they should.
4705 Only 2 v2 authorities remain (compared to 7 v3 authorities), leading
4706 to a serious bottleneck. Bugfix on 0.2.0.9-alpha. Fixes bug 1324.
4707 - Fix a parsing error that made every possible value of
4708 CircPriorityHalflifeMsec get treated as "1 msec". Bugfix
4709 on 0.2.2.7-alpha. Rename CircPriorityHalflifeMsec to
4710 CircuitPriorityHalflifeMsec, so authorities can tell newer relays
4711 about the option without breaking older ones.
4712 - Fix SSL renegotiation behavior on OpenSSL versions like on Centos
4713 that claim to be earlier than 0.9.8m, but which have in reality
4714 backported huge swaths of 0.9.8m or 0.9.8n renegotiation
4715 behavior. Possible fix for some cases of bug 1346.
4718 - Experiment with a more aggressive approach to preventing clients
4719 from making one-hop exit streams. Exit relays who want to try it
4720 out can set "RefuseUnknownExits 1" in their torrc, and then look
4721 for "Attempt by %s to open a stream" log messages. Let us know
4723 - Add support for statically linking zlib by specifying
4724 --enable-static-zlib, to go with our support for statically linking
4725 openssl and libevent. Resolves bug 1358.
4728 - Fix a segfault that happens whenever a Tor client that is using
4729 libevent2's bufferevents gets a hup signal. Bugfix on 0.2.2.5-alpha;
4731 - When we cleaned up the contrib/tor-exit-notice.html file, we left
4732 out the first line. Fixes bug 1295.
4733 - When building the manpage from a tarball, we required asciidoc, but
4734 the asciidoc -> roff/html conversion was already done for the
4735 tarball. Make 'make' complain only when we need asciidoc (either
4736 because we're compiling directly from git, or because we altered
4737 the asciidoc manpage in the tarball). Bugfix on 0.2.2.9-alpha.
4738 - When none of the directory authorities vote on any params, Tor
4739 segfaulted when trying to make the consensus from the votes. We
4740 didn't trigger the bug in practice, because authorities do include
4741 params in their votes. Bugfix on 0.2.2.10-alpha; fixes bug 1322.
4744 - In the util/threads test, no longer free the test_mutex before all
4745 worker threads have finished. Bugfix on 0.2.1.6-alpha.
4746 - The master thread could starve the worker threads quite badly on
4747 certain systems, causing them to run only partially in the allowed
4748 window. This resulted in test failures. Now the master thread sleeps
4749 occasionally for a few microseconds while the two worker-threads
4750 compete for the mutex. Bugfix on 0.2.0.1-alpha.
4753 Changes in version 0.2.2.10-alpha - 2010-03-07
4754 Tor 0.2.2.10-alpha fixes a regression introduced in 0.2.2.9-alpha that
4755 could prevent relays from guessing their IP address correctly. It also
4756 starts the groundwork for another client-side performance boost, since
4757 currently we're not making efficient use of relays that have both the
4758 Guard flag and the Exit flag.
4761 - Fix a regression from our patch for bug 1244 that caused relays
4762 to guess their IP address incorrectly if they didn't set Address
4763 in their torrc and/or their address fails to resolve. Bugfix on
4764 0.2.2.9-alpha; fixes bug 1269.
4766 o Major features (performance):
4767 - Directory authorities now compute consensus weightings that instruct
4768 clients how to weight relays flagged as Guard, Exit, Guard+Exit,
4769 and no flag. Clients that use these weightings will distribute
4770 network load more evenly across these different relay types. The
4771 weightings are in the consensus so we can change them globally in
4772 the future. Extra thanks to "outofwords" for finding some nasty
4773 security bugs in the first implementation of this feature.
4775 o Minor features (performance):
4776 - Always perform router selections using weighted relay bandwidth,
4777 even if we don't need a high capacity circuit at the time. Non-fast
4778 circuits now only differ from fast ones in that they can use relays
4779 not marked with the Fast flag. This "feature" could turn out to
4780 be a horrible bug; we should investigate more before it goes into
4784 - Allow disabling building of the manpages. Skipping the manpage
4785 speeds up the build considerably.
4787 o Minor bugfixes (on 0.2.2.x):
4788 - Fix a memleak in the EXTENDCIRCUIT logic. Spotted by coverity.
4789 Bugfix on 0.2.2.9-alpha.
4790 - Disallow values larger than INT32_MAX for PerConnBWRate|Burst
4791 config option. Bugfix on 0.2.2.7-alpha.
4792 - Ship the asciidoc-helper file in the tarball, so that people can
4793 build from source if they want to, and touching the .1.txt files
4794 doesn't break the build. Bugfix on 0.2.2.9-alpha.
4796 o Minor bugfixes (on 0.2.1.x or earlier):
4797 - Fix a dereference-then-NULL-check sequence when publishing
4798 descriptors. Bugfix on 0.2.1.5-alpha. Discovered by ekir; fixes
4800 - Fix another dereference-then-NULL-check sequence. Bugfix on
4801 0.2.1.14-rc. Discovered by ekir; fixes bug 1256.
4802 - Make sure we treat potentially not NUL-terminated strings correctly.
4803 Bugfix on 0.1.1.13-alpha. Discovered by rieo; fixes bug 1257.
4805 o Code simplifications and refactoring:
4806 - Fix some urls in the exit notice file and make it XHTML1.1 strict
4807 compliant. Based on a patch from Christian Kujau.
4808 - Don't use sed in asciidoc-helper anymore.
4809 - Make the build process fail if asciidoc cannot be found and
4810 building with asciidoc isn't disabled.
4813 Changes in version 0.2.2.9-alpha - 2010-02-22
4814 Tor 0.2.2.9-alpha makes Tor work again on the latest OS X, updates the
4815 location of a directory authority, and cleans up a bunch of small bugs.
4817 o Directory authority changes:
4818 - Change IP address for dannenberg (v3 directory authority), and
4819 remove moria2 (obsolete v1, v2 directory authority and v0 hidden
4820 service directory authority) from the list.
4823 - Make Tor work again on the latest OS X: when deciding whether to
4824 use strange flags to turn TLS renegotiation on, detect the OpenSSL
4825 version at run-time, not compile time. We need to do this because
4826 Apple doesn't update its dev-tools headers when it updates its
4827 libraries in a security patch.
4828 - Fix a potential buffer overflow in lookup_last_hid_serv_request()
4829 that could happen on 32-bit platforms with 64-bit time_t. Also fix
4830 a memory leak when requesting a hidden service descriptor we've
4831 requested before. Fixes bug 1242, bugfix on 0.2.0.18-alpha. Found
4833 - Authorities could be tricked into giving out the Exit flag to relays
4834 that didn't allow exiting to any ports. This bug could screw
4835 with load balancing and stats. Bugfix on 0.1.1.6-alpha; fixes bug
4836 1238. Bug discovered by Martin Kowalczyk.
4837 - When freeing a session key, zero it out completely. We only zeroed
4838 the first ptrsize bytes. Bugfix on 0.0.2pre8. Discovered and
4839 patched by ekir. Fixes bug 1254.
4842 - Fix static compilation by listing the openssl libraries in the right
4843 order. Bugfix on Tor 0.2.2.8-alpha; fixes bug 1237.
4844 - Resume handling .exit hostnames in a special way: originally we
4845 stripped the .exit part and used the requested exit relay. In
4846 0.2.2.1-alpha we stopped treating them in any special way, meaning
4847 if you use a .exit address then Tor will pass it on to the exit
4848 relay. Now we reject the .exit stream outright, since that behavior
4849 might be more expected by the user. Found and diagnosed by Scott
4850 Bennett and Downie on or-talk.
4851 - Don't spam the controller with events when we have no file
4852 descriptors available. Bugfix on 0.2.1.5-alpha. (Rate-limiting
4853 for log messages was already solved from bug 748.)
4854 - Avoid a bogus overlapped memcpy in tor_addr_copy(). Reported by
4856 - Make the DNSPort option work with libevent 2.x. Don't alter the
4857 behaviour for libevent 1.x. Fixes bug 1143. Found by SwissTorExit.
4858 - Emit a GUARD DROPPED controller event for a case we missed.
4859 - Make more fields in the controller protocol case-insensitive, since
4860 control-spec.txt said they were.
4861 - Refactor resolve_my_address() to not use gethostbyname() anymore.
4862 Fixes bug 1244; bugfix on 0.0.2pre25. Reported by Mike Mestnik.
4863 - Fix a spec conformance issue: the network-status-version token
4864 must be the first token in a v3 consensus or vote. Discovered by
4865 parakeep. Bugfix on 0.2.0.3-alpha.
4867 o Code simplifications and refactoring:
4868 - Generate our manpage and HTML documentation using Asciidoc. This
4869 change should make it easier to maintain the documentation, and
4871 - Remove the --enable-iphone option. According to reports from Marco
4872 Bonetti, Tor builds fine without any special tweaking on recent
4873 iPhone SDK versions.
4874 - Removed some unnecessary files from the source distribution. The
4875 AUTHORS file has now been merged into the people page on the
4876 website. The roadmaps and design doc can now be found in the
4877 projects directory in svn.
4878 - Enabled various circuit build timeout constants to be controlled
4879 by consensus parameters. Also set better defaults for these
4880 parameters based on experimentation on broadband and simulated
4884 - The 'EXTENDCIRCUIT' control port command can now be used with
4885 a circ id of 0 and no path. This feature will cause Tor to build
4886 a new 'fast' general purpose circuit using its own path selection
4888 - Added a BUILDTIMEOUT_SET controller event to describe changes
4889 to the circuit build timeout.
4890 - Future-proof the controller protocol a bit by ignoring keyword
4891 arguments we do not recognize.
4892 - Expand homedirs passed to tor-checkkey. This should silence a
4893 coverity complaint about passing a user-supplied string into
4894 open() without checking it.
4897 Changes in version 0.2.1.25 - 2010-03-16
4898 Tor 0.2.1.25 fixes a regression introduced in 0.2.1.23 that could
4899 prevent relays from guessing their IP address correctly. It also fixes
4900 several minor potential security bugs.
4903 - Fix a regression from our patch for bug 1244 that caused relays
4904 to guess their IP address incorrectly if they didn't set Address
4905 in their torrc and/or their address fails to resolve. Bugfix on
4906 0.2.1.23; fixes bug 1269.
4907 - When freeing a session key, zero it out completely. We only zeroed
4908 the first ptrsize bytes. Bugfix on 0.0.2pre8. Discovered and
4909 patched by ekir. Fixes bug 1254.
4912 - Fix a dereference-then-NULL-check sequence when publishing
4913 descriptors. Bugfix on 0.2.1.5-alpha. Discovered by ekir; fixes
4915 - Fix another dereference-then-NULL-check sequence. Bugfix on
4916 0.2.1.14-rc. Discovered by ekir; fixes bug 1256.
4917 - Make sure we treat potentially not NUL-terminated strings correctly.
4918 Bugfix on 0.1.1.13-alpha. Discovered by rieo; fixes bug 1257.
4922 Changes in version 0.2.1.24 - 2010-02-21
4923 Tor 0.2.1.24 makes Tor work again on the latest OS X -- this time
4927 - Work correctly out-of-the-box with even more vendor-patched versions
4928 of OpenSSL. In particular, make it so Debian and OS X don't need
4929 customized patches to run/build.
4932 Changes in version 0.2.1.23 - 2010-02-13
4933 Tor 0.2.1.23 fixes a huge client-side performance bug, makes Tor work
4934 again on the latest OS X, and updates the location of a directory
4937 o Major bugfixes (performance):
4938 - We were selecting our guards uniformly at random, and then weighting
4939 which of our guards we'd use uniformly at random. This imbalance
4940 meant that Tor clients were severely limited on throughput (and
4941 probably latency too) by the first hop in their circuit. Now we
4942 select guards weighted by currently advertised bandwidth. We also
4943 automatically discard guards picked using the old algorithm. Fixes
4944 bug 1217; bugfix on 0.2.1.3-alpha. Found by Mike Perry.
4947 - Make Tor work again on the latest OS X: when deciding whether to
4948 use strange flags to turn TLS renegotiation on, detect the OpenSSL
4949 version at run-time, not compile time. We need to do this because
4950 Apple doesn't update its dev-tools headers when it updates its
4951 libraries in a security patch.
4952 - Fix a potential buffer overflow in lookup_last_hid_serv_request()
4953 that could happen on 32-bit platforms with 64-bit time_t. Also fix
4954 a memory leak when requesting a hidden service descriptor we've
4955 requested before. Fixes bug 1242, bugfix on 0.2.0.18-alpha. Found
4958 o Directory authority changes:
4959 - Change IP address for dannenberg (v3 directory authority), and
4960 remove moria2 (obsolete v1, v2 directory authority and v0 hidden
4961 service directory authority) from the list.
4964 - Refactor resolve_my_address() to not use gethostbyname() anymore.
4965 Fixes bug 1244; bugfix on 0.0.2pre25. Reported by Mike Mestnik.
4968 - Avoid a mad rush at the beginning of each month when each client
4969 rotates half of its guards. Instead we spread the rotation out
4970 throughout the month, but we still avoid leaving a precise timestamp
4971 in the state file about when we first picked the guard. Improves
4972 over the behavior introduced in 0.1.2.17.
4975 Changes in version 0.2.2.8-alpha - 2010-01-26
4976 Tor 0.2.2.8-alpha fixes a crash bug in 0.2.2.7-alpha that has been
4977 causing bridge relays to disappear. If you're running a bridge,
4981 - Fix a memory corruption bug on bridges that occured during the
4982 inclusion of stats data in extra-info descriptors. Also fix the
4983 interface for geoip_get_bridge_stats* to prevent similar bugs in
4984 the future. Diagnosis by Tas, patch by Karsten and Sebastian.
4985 Fixes bug 1208; bugfix on 0.2.2.7-alpha.
4988 - Ignore OutboundBindAddress when connecting to localhost.
4989 Connections to localhost need to come _from_ localhost, or else
4990 local servers (like DNS and outgoing HTTP/SOCKS proxies) will often
4994 Changes in version 0.2.2.7-alpha - 2010-01-19
4995 Tor 0.2.2.7-alpha fixes a huge client-side performance bug, as well
4996 as laying the groundwork for further relay-side performance fixes. It
4997 also starts cleaning up client behavior with respect to the EntryNodes,
4998 ExitNodes, and StrictNodes config options.
5000 This release also rotates two directory authority keys, due to a
5001 security breach of some of the Torproject servers.
5003 o Directory authority changes:
5004 - Rotate keys (both v3 identity and relay identity) for moria1
5007 o Major features (performance):
5008 - We were selecting our guards uniformly at random, and then weighting
5009 which of our guards we'd use uniformly at random. This imbalance
5010 meant that Tor clients were severely limited on throughput (and
5011 probably latency too) by the first hop in their circuit. Now we
5012 select guards weighted by currently advertised bandwidth. We also
5013 automatically discard guards picked using the old algorithm. Fixes
5014 bug 1217; bugfix on 0.2.1.3-alpha. Found by Mike Perry.
5015 - When choosing which cells to relay first, relays can now favor
5016 circuits that have been quiet recently, to provide lower latency
5017 for low-volume circuits. By default, relays enable or disable this
5018 feature based on a setting in the consensus. You can override
5019 this default by using the new "CircuitPriorityHalflife" config
5020 option. Design and code by Ian Goldberg, Can Tang, and Chris
5022 - Add separate per-conn write limiting to go with the per-conn read
5023 limiting. We added a global write limit in Tor 0.1.2.5-alpha,
5024 but never per-conn write limits.
5025 - New consensus params "bwconnrate" and "bwconnburst" to let us
5026 rate-limit client connections as they enter the network. It's
5027 controlled in the consensus so we can turn it on and off for
5028 experiments. It's starting out off. Based on proposal 163.
5030 o Major features (relay selection options):
5031 - Switch to a StrictNodes config option, rather than the previous
5032 "StrictEntryNodes" / "StrictExitNodes" separation that was missing a
5033 "StrictExcludeNodes" option.
5034 - If EntryNodes, ExitNodes, ExcludeNodes, or ExcludeExitNodes
5035 change during a config reload, mark and discard all our origin
5036 circuits. This fix should address edge cases where we change the
5037 config options and but then choose a circuit that we created before
5039 - If EntryNodes or ExitNodes are set, be more willing to use an
5040 unsuitable (e.g. slow or unstable) circuit. The user asked for it,
5042 - Make EntryNodes config option much more aggressive even when
5043 StrictNodes is not set. Before it would prepend your requested
5044 entrynodes to your list of guard nodes, but feel free to use others
5045 after that. Now it chooses only from your EntryNodes if any of
5046 those are available, and only falls back to others if a) they're
5047 all down and b) StrictNodes is not set.
5048 - Now we refresh your entry guards from EntryNodes at each consensus
5049 fetch -- rather than just at startup and then they slowly rot as
5050 the network changes.
5053 - Stop bridge directory authorities from answering dbg-stability.txt
5054 directory queries, which would let people fetch a list of all
5055 bridge identities they track. Bugfix on 0.2.1.6-alpha.
5058 - Log a notice when we get a new control connection. Now it's easier
5059 for security-conscious users to recognize when a local application
5060 is knocking on their controller door. Suggested by bug 1196.
5061 - New config option "CircuitStreamTimeout" to override our internal
5062 timeout schedule for how many seconds until we detach a stream from
5063 a circuit and try a new circuit. If your network is particularly
5064 slow, you might want to set this to a number like 60.
5065 - New controller command "getinfo config-text". It returns the
5066 contents that Tor would write if you send it a SAVECONF command,
5067 so the controller can write the file to disk itself.
5068 - New options for SafeLogging to allow scrubbing only log messages
5069 generated while acting as a relay.
5070 - Ship the bridges spec file in the tarball too.
5071 - Avoid a mad rush at the beginning of each month when each client
5072 rotates half of its guards. Instead we spread the rotation out
5073 throughout the month, but we still avoid leaving a precise timestamp
5074 in the state file about when we first picked the guard. Improves
5075 over the behavior introduced in 0.1.2.17.
5077 o Minor bugfixes (compiling):
5078 - Fix compilation on OS X 10.3, which has a stub mlockall() but
5079 hides it. Bugfix on 0.2.2.6-alpha.
5080 - Fix compilation on Solaris by removing support for the
5081 DisableAllSwap config option. Solaris doesn't have an rlimit for
5082 mlockall, so we cannot use it safely. Fixes bug 1198; bugfix on
5085 o Minor bugfixes (crashes):
5086 - Do not segfault when writing buffer stats when we haven't observed
5087 a single circuit to report about. Found by Fabian Lanze. Bugfix on
5089 - If we're in the pathological case where there's no exit bandwidth
5090 but there is non-exit bandwidth, or no guard bandwidth but there
5091 is non-guard bandwidth, don't crash during path selection. Bugfix
5093 - Fix an impossible-to-actually-trigger buffer overflow in relay
5094 descriptor generation. Bugfix on 0.1.0.15.
5096 o Minor bugfixes (privacy):
5097 - Fix an instance where a Tor directory mirror might accidentally
5098 log the IP address of a misbehaving Tor client. Bugfix on
5100 - Don't list Windows capabilities in relay descriptors. We never made
5101 use of them, and maybe it's a bad idea to publish them. Bugfix
5104 o Minor bugfixes (other):
5105 - Resolve an edge case in path weighting that could make us misweight
5106 our relay selection. Fixes bug 1203; bugfix on 0.0.8rc1.
5107 - Fix statistics on client numbers by country as seen by bridges that
5108 were broken in 0.2.2.1-alpha. Also switch to reporting full 24-hour
5109 intervals instead of variable 12-to-48-hour intervals.
5110 - After we free an internal connection structure, overwrite it
5111 with a different memory value than we use for overwriting a freed
5112 internal circuit structure. Should help with debugging. Suggested
5114 - Update our OpenSSL 0.9.8l fix so that it works with OpenSSL 0.9.8m
5118 - Remove the HSAuthorityRecordStats option that version 0 hidden
5119 service authorities could have used to track statistics of overall
5120 hidden service usage.
5123 Changes in version 0.2.1.22 - 2010-01-19
5124 Tor 0.2.1.22 fixes a critical privacy problem in bridge directory
5125 authorities -- it would tell you its whole history of bridge descriptors
5126 if you make the right directory request. This stable update also
5127 rotates two of the seven v3 directory authority keys and locations.
5129 o Directory authority changes:
5130 - Rotate keys (both v3 identity and relay identity) for moria1
5134 - Stop bridge directory authorities from answering dbg-stability.txt
5135 directory queries, which would let people fetch a list of all
5136 bridge identities they track. Bugfix on 0.2.1.6-alpha.
5139 Changes in version 0.2.1.21 - 2009-12-21
5140 Tor 0.2.1.21 fixes an incompatibility with the most recent OpenSSL
5141 library. If you use Tor on Linux / Unix and you're getting SSL
5142 renegotiation errors, upgrading should help. We also recommend an
5143 upgrade if you're an exit relay.
5146 - Work around a security feature in OpenSSL 0.9.8l that prevents our
5147 handshake from working unless we explicitly tell OpenSSL that we
5148 are using SSL renegotiation safely. We are, of course, but OpenSSL
5149 0.9.8l won't work unless we say we are.
5150 - Avoid crashing if the client is trying to upload many bytes and the
5151 circuit gets torn down at the same time, or if the flip side
5152 happens on the exit relay. Bugfix on 0.2.0.1-alpha; fixes bug 1150.
5155 - Do not refuse to learn about authority certs and v2 networkstatus
5156 documents that are older than the latest consensus. This bug might
5157 have degraded client bootstrapping. Bugfix on 0.2.0.10-alpha.
5158 Spotted and fixed by xmux.
5159 - Fix a couple of very-hard-to-trigger memory leaks, and one hard-to-
5160 trigger platform-specific option misparsing case found by Coverity
5162 - Fix a compilation warning on Fedora 12 by removing an impossible-to-
5163 trigger assert. Fixes bug 1173.
5166 Changes in version 0.2.2.6-alpha - 2009-11-19
5167 Tor 0.2.2.6-alpha lays the groundwork for many upcoming features:
5168 support for the new lower-footprint "microdescriptor" directory design,
5169 future-proofing our consensus format against new hash functions or
5170 other changes, and an Android port. It also makes Tor compatible with
5171 the upcoming OpenSSL 0.9.8l release, and fixes a variety of bugs.
5174 - Directory authorities can now create, vote on, and serve multiple
5175 parallel formats of directory data as part of their voting process.
5176 Partially implements Proposal 162: "Publish the consensus in
5178 - Directory authorities can now agree on and publish small summaries
5179 of router information that clients can use in place of regular
5180 server descriptors. This transition will eventually allow clients
5181 to use far less bandwidth for downloading information about the
5182 network. Begins the implementation of Proposal 158: "Clients
5183 download consensus + microdescriptors".
5184 - The directory voting system is now extensible to use multiple hash
5185 algorithms for signatures and resource selection. Newer formats
5186 are signed with SHA256, with a possibility for moving to a better
5187 hash algorithm in the future.
5188 - New DisableAllSwap option. If set to 1, Tor will attempt to lock all
5189 current and future memory pages via mlockall(). On supported
5190 platforms (modern Linux and probably BSD but not Windows or OS X),
5191 this should effectively disable any and all attempts to page out
5192 memory. This option requires that you start your Tor as root --
5193 if you use DisableAllSwap, please consider using the User option
5194 to properly reduce the privileges of your Tor.
5195 - Numerous changes, bugfixes, and workarounds from Nathan Freitas
5196 to help Tor build correctly for Android phones.
5199 - Work around a security feature in OpenSSL 0.9.8l that prevents our
5200 handshake from working unless we explicitly tell OpenSSL that we
5201 are using SSL renegotiation safely. We are, but OpenSSL 0.9.8l
5202 won't work unless we say we are.
5205 - Fix a crash bug when trying to initialize the evdns module in
5206 Libevent 2. Bugfix on 0.2.1.16-rc.
5207 - Stop logging at severity 'warn' when some other Tor client tries
5208 to establish a circuit with us using weak DH keys. It's a protocol
5209 violation, but that doesn't mean ordinary users need to hear about
5210 it. Fixes the bug part of bug 1114. Bugfix on 0.1.0.13.
5211 - Do not refuse to learn about authority certs and v2 networkstatus
5212 documents that are older than the latest consensus. This bug might
5213 have degraded client bootstrapping. Bugfix on 0.2.0.10-alpha.
5214 Spotted and fixed by xmux.
5215 - Fix numerous small code-flaws found by Coverity Scan Rung 3.
5216 - If all authorities restart at once right before a consensus vote,
5217 nobody will vote about "Running", and clients will get a consensus
5218 with no usable relays. Instead, authorities refuse to build a
5219 consensus if this happens. Bugfix on 0.2.0.10-alpha; fixes bug 1066.
5220 - If your relay can't keep up with the number of incoming create
5221 cells, it would log one warning per failure into your logs. Limit
5222 warnings to 1 per minute. Bugfix on 0.0.2pre10; fixes bug 1042.
5223 - Bridges now use "reject *:*" as their default exit policy. Bugfix
5224 on 0.2.0.3-alpha; fixes bug 1113.
5225 - Fix a memory leak on directory authorities during voting that was
5226 introduced in 0.2.2.1-alpha. Found via valgrind.
5229 Changes in version 0.2.1.20 - 2009-10-15
5230 Tor 0.2.1.20 fixes a crash bug when you're accessing many hidden
5231 services at once, prepares for more performance improvements, and
5232 fixes a bunch of smaller bugs.
5234 The Windows and OS X bundles also include a more recent Vidalia,
5235 and switch from Privoxy to Polipo.
5237 The OS X installers are now drag and drop. It's best to un-install
5238 Tor/Vidalia and then install this new bundle, rather than upgrade. If
5239 you want to upgrade, you'll need to update the paths for Tor and Polipo
5240 in the Vidalia Settings window.
5243 - Send circuit or stream sendme cells when our window has decreased
5244 by 100 cells, not when it has decreased by 101 cells. Bug uncovered
5245 by Karsten when testing the "reduce circuit window" performance
5246 patch. Bugfix on the 54th commit on Tor -- from July 2002,
5247 before the release of Tor 0.0.0. This is the new winner of the
5249 - Fix a remotely triggerable memory leak when a consensus document
5250 contains more than one signature from the same voter. Bugfix on
5252 - Avoid segfault in rare cases when finishing an introduction circuit
5253 as a client and finding out that we don't have an introduction key
5254 for it. Fixes bug 1073. Reported by Aaron Swartz.
5257 - Tor now reads the "circwindow" parameter out of the consensus,
5258 and uses that value for its circuit package window rather than the
5259 default of 1000 cells. Begins the implementation of proposal 168.
5261 o New directory authorities:
5262 - Set up urras (run by Jacob Appelbaum) as the seventh v3 directory
5264 - Move moria1 and tonga to alternate IP addresses.
5267 - Fix a signed/unsigned compile warning in 0.2.1.19.
5268 - Fix possible segmentation fault on directory authorities. Bugfix on
5270 - Fix an extremely rare infinite recursion bug that could occur if
5271 we tried to log a message after shutting down the log subsystem.
5272 Found by Matt Edman. Bugfix on 0.2.0.16-alpha.
5273 - Fix an obscure bug where hidden services on 64-bit big-endian
5274 systems might mis-read the timestamp in v3 introduce cells, and
5275 refuse to connect back to the client. Discovered by "rotor".
5276 Bugfix on 0.2.1.6-alpha.
5277 - We were triggering a CLOCK_SKEW controller status event whenever
5278 we connect via the v2 connection protocol to any relay that has
5279 a wrong clock. Instead, we should only inform the controller when
5280 it's a trusted authority that claims our clock is wrong. Bugfix
5281 on 0.2.0.20-rc; starts to fix bug 1074. Reported by SwissTorExit.
5282 - We were telling the controller about CHECKING_REACHABILITY and
5283 REACHABILITY_FAILED status events whenever we launch a testing
5284 circuit or notice that one has failed. Instead, only tell the
5285 controller when we want to inform the user of overall success or
5286 overall failure. Bugfix on 0.1.2.6-alpha. Fixes bug 1075. Reported
5288 - Don't warn when we're using a circuit that ends with a node
5289 excluded in ExcludeExitNodes, but the circuit is not used to access
5290 the outside world. This should help fix bug 1090. Bugfix on
5292 - Work around a small memory leak in some versions of OpenSSL that
5293 stopped the memory used by the hostname TLS extension from being
5297 - Add a "getinfo status/accepted-server-descriptor" controller
5298 command, which is the recommended way for controllers to learn
5299 whether our server descriptor has been successfully received by at
5300 least on directory authority. Un-recommend good-server-descriptor
5301 getinfo and status events until we have a better design for them.
5304 Changes in version 0.2.2.5-alpha - 2009-10-11
5305 Tor 0.2.2.5-alpha fixes a few compile problems in 0.2.2.4-alpha.
5308 - Make the tarball compile again. Oops. Bugfix on 0.2.2.4-alpha.
5310 o Directory authorities:
5311 - Temporarily (just for this release) move dizum to an alternate
5315 Changes in version 0.2.2.4-alpha - 2009-10-10
5316 Tor 0.2.2.4-alpha fixes more crash bugs in 0.2.2.2-alpha. It also
5317 introduces a new unit test framework, shifts directry authority
5318 addresses around to reduce the impact from recent blocking events,
5319 and fixes a few smaller bugs.
5322 - Fix several more asserts in the circuit_build_times code, for
5323 example one that causes Tor to fail to start once we have
5324 accumulated 5000 build times in the state file. Bugfixes on
5325 0.2.2.2-alpha; fixes bug 1108.
5327 o New directory authorities:
5328 - Move moria1 and Tonga to alternate IP addresses.
5331 - Log SSL state transitions at debug level during handshake, and
5332 include SSL states in error messages. This may help debug future
5333 SSL handshake issues.
5334 - Add a new "Handshake" log domain for activities that happen
5335 during the TLS handshake.
5336 - Revert to the "June 3 2009" ip-to-country file. The September one
5337 seems to have removed most US IP addresses.
5338 - Directory authorities now reject Tor relays with versions less than
5339 0.1.2.14. This step cuts out four relays from the current network,
5340 none of which are very big.
5343 - Fix a couple of smaller issues with gathering statistics. Bugfixes
5345 - Fix two memory leaks in the error case of
5346 circuit_build_times_parse_state(). Bugfix on 0.2.2.2-alpha.
5347 - Don't count one-hop circuits when we're estimating how long it
5348 takes circuits to build on average. Otherwise we'll set our circuit
5349 build timeout lower than we should. Bugfix on 0.2.2.2-alpha.
5350 - Directory authorities no longer change their opinion of, or vote on,
5351 whether a router is Running, unless they have themselves been
5352 online long enough to have some idea. Bugfix on 0.2.0.6-alpha.
5355 o Code simplifications and refactoring:
5356 - Revise our unit tests to use the "tinytest" framework, so we
5357 can run tests in their own processes, have smarter setup/teardown
5358 code, and so on. The unit test code has moved to its own
5359 subdirectory, and has been split into multiple modules.
5362 Changes in version 0.2.2.3-alpha - 2009-09-23
5363 Tor 0.2.2.3-alpha fixes a few crash bugs in 0.2.2.2-alpha.
5366 - Fix an overzealous assert in our new circuit build timeout code.
5367 Bugfix on 0.2.2.2-alpha; fixes bug 1103.
5370 - If the networkstatus consensus tells us that we should use a
5371 negative circuit package window, ignore it. Otherwise we'll
5372 believe it and then trigger an assert. Bugfix on 0.2.2.2-alpha.
5375 Changes in version 0.2.2.2-alpha - 2009-09-21
5376 Tor 0.2.2.2-alpha introduces our latest performance improvement for
5377 clients: Tor tracks the average time it takes to build a circuit, and
5378 avoids using circuits that take too long to build. For fast connections,
5379 this feature can cut your expected latency in half. For slow or flaky
5380 connections, it could ruin your Tor experience. Let us know if it does!
5383 - Tor now tracks how long it takes to build client-side circuits
5384 over time, and adapts its timeout to local network performance.
5385 Since a circuit that takes a long time to build will also provide
5386 bad performance, we get significant latency improvements by
5387 discarding the slowest 20% of circuits. Specifically, Tor creates
5388 circuits more aggressively than usual until it has enough data
5389 points for a good timeout estimate. Implements proposal 151.
5390 We are especially looking for reports (good and bad) from users with
5391 both EDGE and broadband connections that can move from broadband
5392 to EDGE and find out if the build-time data in the .tor/state gets
5393 reset without loss of Tor usability. You should also see a notice
5394 log message telling you that Tor has reset its timeout.
5395 - Directory authorities can now vote on arbitary integer values as
5396 part of the consensus process. This is designed to help set
5397 network-wide parameters. Implements proposal 167.
5398 - Tor now reads the "circwindow" parameter out of the consensus,
5399 and uses that value for its circuit package window rather than the
5400 default of 1000 cells. Begins the implementation of proposal 168.
5403 - Fix a remotely triggerable memory leak when a consensus document
5404 contains more than one signature from the same voter. Bugfix on
5408 - Fix an extremely rare infinite recursion bug that could occur if
5409 we tried to log a message after shutting down the log subsystem.
5410 Found by Matt Edman. Bugfix on 0.2.0.16-alpha.
5411 - Fix parsing for memory or time units given without a space between
5412 the number and the unit. Bugfix on 0.2.2.1-alpha; fixes bug 1076.
5413 - A networkstatus vote must contain exactly one signature. Spec
5414 conformance issue. Bugfix on 0.2.0.3-alpha.
5415 - Fix an obscure bug where hidden services on 64-bit big-endian
5416 systems might mis-read the timestamp in v3 introduce cells, and
5417 refuse to connect back to the client. Discovered by "rotor".
5418 Bugfix on 0.2.1.6-alpha.
5419 - We were triggering a CLOCK_SKEW controller status event whenever
5420 we connect via the v2 connection protocol to any relay that has
5421 a wrong clock. Instead, we should only inform the controller when
5422 it's a trusted authority that claims our clock is wrong. Bugfix
5423 on 0.2.0.20-rc; starts to fix bug 1074. Reported by SwissTorExit.
5424 - We were telling the controller about CHECKING_REACHABILITY and
5425 REACHABILITY_FAILED status events whenever we launch a testing
5426 circuit or notice that one has failed. Instead, only tell the
5427 controller when we want to inform the user of overall success or
5428 overall failure. Bugfix on 0.1.2.6-alpha. Fixes bug 1075. Reported
5430 - Don't warn when we're using a circuit that ends with a node
5431 excluded in ExcludeExitNodes, but the circuit is not used to access
5432 the outside world. This should help fix bug 1090, but more problems
5433 remain. Bugfix on 0.2.1.6-alpha.
5434 - Work around a small memory leak in some versions of OpenSSL that
5435 stopped the memory used by the hostname TLS extension from being
5437 - Make our 'torify' script more portable; if we have only one of
5438 'torsocks' or 'tsocks' installed, don't complain to the user;
5439 and explain our warning about tsocks better.
5442 - Add a "getinfo status/accepted-server-descriptor" controller
5443 command, which is the recommended way for controllers to learn
5444 whether our server descriptor has been successfully received by at
5445 least on directory authority. Un-recommend good-server-descriptor
5446 getinfo and status events until we have a better design for them.
5447 - Update to the "September 4 2009" ip-to-country file.
5450 Changes in version 0.2.2.1-alpha - 2009-08-26
5451 Tor 0.2.2.1-alpha disables ".exit" address notation by default, allows
5452 Tor clients to bootstrap on networks where only port 80 is reachable,
5453 makes it more straightforward to support hardware crypto accelerators,
5454 and starts the groundwork for gathering stats safely at relays.
5457 - Start the process of disabling ".exit" address notation, since it
5458 can be used for a variety of esoteric application-level attacks
5459 on users. To reenable it, set "AllowDotExit 1" in your torrc. Fix
5462 o New directory authorities:
5463 - Set up urras (run by Jacob Appelbaum) as the seventh v3 directory
5467 - New AccelName and AccelDir options add support for dynamic OpenSSL
5468 hardware crypto acceleration engines.
5469 - Tor now supports tunneling all of its outgoing connections over
5470 a SOCKS proxy, using the SOCKS4Proxy and/or SOCKS5Proxy
5471 configuration options. Code by Christopher Davis.
5474 - Send circuit or stream sendme cells when our window has decreased
5475 by 100 cells, not when it has decreased by 101 cells. Bug uncovered
5476 by Karsten when testing the "reduce circuit window" performance
5477 patch. Bugfix on the 54th commit on Tor -- from July 2002,
5478 before the release of Tor 0.0.0. This is the new winner of the
5481 o New options for gathering stats safely:
5482 - Directory mirrors that set "DirReqStatistics 1" write statistics
5483 about directory requests to disk every 24 hours. As compared to the
5484 --enable-geoip-stats flag in 0.2.1.x, there are a few improvements:
5485 1) stats are written to disk exactly every 24 hours; 2) estimated
5486 shares of v2 and v3 requests are determined as mean values, not at
5487 the end of a measurement period; 3) unresolved requests are listed
5488 with country code '??'; 4) directories also measure download times.
5489 - Exit nodes that set "ExitPortStatistics 1" write statistics on the
5490 number of exit streams and transferred bytes per port to disk every
5492 - Relays that set "CellStatistics 1" write statistics on how long
5493 cells spend in their circuit queues to disk every 24 hours.
5494 - Entry nodes that set "EntryStatistics 1" write statistics on the
5495 rough number and origins of connecting clients to disk every 24
5497 - Relays that write any of the above statistics to disk and set
5498 "ExtraInfoStatistics 1" include the past 24 hours of statistics in
5499 their extra-info documents.
5502 - New --digests command-line switch to output the digests of the
5503 source files Tor was built with.
5504 - The "torify" script now uses torsocks where available.
5505 - The memarea code now uses a sentinel value at the end of each area
5506 to make sure nothing writes beyond the end of an area. This might
5507 help debug some conceivable causes of bug 930.
5508 - Time and memory units in the configuration file can now be set to
5509 fractional units. For example, "2.5 GB" is now a valid value for
5511 - Certain Tor clients (such as those behind check.torproject.org) may
5512 want to fetch the consensus in an extra early manner. To enable this
5513 a user may now set FetchDirInfoExtraEarly to 1. This also depends on
5514 setting FetchDirInfoEarly to 1. Previous behavior will stay the same
5515 as only certain clients who must have this information sooner should
5517 - Instead of adding the svn revision to the Tor version string, report
5518 the git commit (when we're building from a git checkout).
5521 - If any of the v3 certs we download are unparseable, we should
5522 actually notice the failure so we don't retry indefinitely. Bugfix
5523 on 0.2.0.x; reported by "rotator".
5524 - If the cached cert file is unparseable, warn but don't exit.
5525 - Fix possible segmentation fault on directory authorities. Bugfix on
5527 - When Tor fails to parse a descriptor of any kind, dump it to disk.
5528 Might help diagnosing bug 1051.
5530 o Deprecated and removed features:
5531 - The controller no longer accepts the old obsolete "addr-mappings/"
5532 or "unregistered-servers-" GETINFO values.
5533 - Hidden services no longer publish version 0 descriptors, and clients
5534 do not request or use version 0 descriptors. However, the old hidden
5535 service authorities still accept and serve version 0 descriptors
5536 when contacted by older hidden services/clients.
5537 - The EXTENDED_EVENTS and VERBOSE_NAMES controller features are now
5538 always on; using them is necessary for correct forward-compatible
5540 - Remove support for .noconnect style addresses. Nobody was using
5541 them, and they provided another avenue for detecting Tor users
5542 via application-level web tricks.
5544 o Packaging changes:
5545 - Upgrade Vidalia from 0.1.15 to 0.2.3 in the Windows and OS X
5546 installer bundles. See
5547 https://trac.vidalia-project.net/browser/vidalia/tags/vidalia-0.2.3/CHANGELOG
5548 for details of what's new in Vidalia 0.2.3.
5549 - Windows Vidalia Bundle: update Privoxy from 3.0.6 to 3.0.14-beta.
5550 - OS X Vidalia Bundle: move to Polipo 1.0.4 with Tor specific
5551 configuration file, rather than the old Privoxy.
5552 - OS X Vidalia Bundle: Vidalia, Tor, and Polipo are compiled as
5553 x86-only for better compatibility with OS X 10.6, aka Snow Leopard.
5554 - OS X Tor Expert Bundle: Tor is compiled as x86-only for
5555 better compatibility with OS X 10.6, aka Snow Leopard.
5556 - OS X Vidalia Bundle: The multi-package installer is now replaced
5557 by a simple drag and drop to the /Applications folder. This change
5558 occurred with the upgrade to Vidalia 0.2.3.
5561 Changes in version 0.2.1.19 - 2009-07-28
5562 Tor 0.2.1.19 fixes a major bug with accessing and providing hidden
5563 services on Tor 0.2.1.3-alpha through 0.2.1.18.
5566 - Make accessing hidden services on 0.2.1.x work right again.
5567 Bugfix on 0.2.1.3-alpha; workaround for bug 1038. Diagnosis and
5568 part of patch provided by "optimist".
5571 - When a relay/bridge is writing out its identity key fingerprint to
5572 the "fingerprint" file and to its logs, write it without spaces. Now
5573 it will look like the fingerprints in our bridges documentation,
5574 and confuse fewer users.
5577 - Relays no longer publish a new server descriptor if they change
5578 their MaxAdvertisedBandwidth config option but it doesn't end up
5579 changing their advertised bandwidth numbers. Bugfix on 0.2.0.28-rc;
5580 fixes bug 1026. Patch from Sebastian.
5581 - Avoid leaking memory every time we get a create cell but we have
5582 so many already queued that we refuse it. Bugfix on 0.2.0.19-alpha;
5583 fixes bug 1034. Reported by BarkerJr.
5586 Changes in version 0.2.1.18 - 2009-07-24
5587 Tor 0.2.1.18 lays the foundations for performance improvements,
5588 adds status events to help users diagnose bootstrap problems, adds
5589 optional authentication/authorization for hidden services, fixes a
5590 variety of potential anonymity problems, and includes a huge pile of
5591 other features and bug fixes.
5594 - Add LIBS=-lrt to Makefile.am so the Tor RPMs use a static libevent.
5597 Changes in version 0.2.1.17-rc - 2009-07-07
5598 Tor 0.2.1.17-rc marks the fourth -- and hopefully last -- release
5599 candidate for the 0.2.1.x series. It lays the groundwork for further
5600 client performance improvements, and also fixes a big bug with directory
5601 authorities that were causing them to assign Guard and Stable flags
5604 The Windows bundles also finally include the geoip database that we
5605 thought we'd been shipping since 0.2.0.x (oops), and the OS X bundles
5606 should actually install Torbutton rather than giving you a cryptic
5607 failure message (oops).
5610 - Clients now use the bandwidth values in the consensus, rather than
5611 the bandwidth values in each relay descriptor. This approach opens
5612 the door to more accurate bandwidth estimates once the directory
5613 authorities start doing active measurements. Implements more of
5617 - When Tor clients restart after 1-5 days, they discard all their
5618 cached descriptors as too old, but they still use the cached
5619 consensus document. This approach is good for robustness, but
5620 bad for performance: since they don't know any bandwidths, they
5621 end up choosing at random rather than weighting their choice by
5622 speed. Fixed by the above feature of putting bandwidths in the
5623 consensus. Bugfix on 0.2.0.x.
5624 - Directory authorities were neglecting to mark relays down in their
5625 internal histories if the relays fall off the routerlist without
5626 ever being found unreachable. So there were relays in the histories
5627 that haven't been seen for eight months, and are listed as being
5628 up for eight months. This wreaked havoc on the "median wfu"
5629 and "median mtbf" calculations, in turn making Guard and Stable
5630 flags very wrong, hurting network performance. Fixes bugs 696 and
5631 969. Bugfix on 0.2.0.6-alpha.
5634 - Serve the DirPortFrontPage page even when we have been approaching
5635 our quotas recently. Fixes bug 1013; bugfix on 0.2.1.8-alpha.
5636 - The control port would close the connection before flushing long
5637 replies, such as the network consensus, if a QUIT command was issued
5638 before the reply had completed. Now, the control port flushes all
5639 pending replies before closing the connection. Also fixed a spurious
5640 warning when a QUIT command is issued after a malformed or rejected
5641 AUTHENTICATE command, but before the connection was closed. Patch
5642 by Marcus Griep. Bugfix on 0.2.0.x; fixes bugs 1015 and 1016.
5643 - When we can't find an intro key for a v2 hidden service descriptor,
5644 fall back to the v0 hidden service descriptor and log a bug message.
5645 Workaround for bug 1024.
5646 - Fix a log message that did not respect the SafeLogging option.
5650 - If we're a relay and we change our IP address, be more verbose
5651 about the reason that made us change. Should help track down
5652 further bugs for relays on dynamic IP addresses.
5655 Changes in version 0.2.0.35 - 2009-06-24
5657 - Avoid crashing in the presence of certain malformed descriptors.
5658 Found by lark, and by automated fuzzing.
5659 - Fix an edge case where a malicious exit relay could convince a
5660 controller that the client's DNS question resolves to an internal IP
5661 address. Bug found and fixed by "optimist"; bugfix on 0.1.2.8-beta.
5664 - Finally fix the bug where dynamic-IP relays disappear when their
5665 IP address changes: directory mirrors were mistakenly telling
5666 them their old address if they asked via begin_dir, so they
5667 never got an accurate answer about their new address, so they
5668 just vanished after a day. For belt-and-suspenders, relays that
5669 don't set Address in their config now avoid using begin_dir for
5670 all direct connections. Should fix bugs 827, 883, and 900.
5671 - Fix a timing-dependent, allocator-dependent, DNS-related crash bug
5672 that would occur on some exit nodes when DNS failures and timeouts
5673 occurred in certain patterns. Fix for bug 957.
5676 - When starting with a cache over a few days old, do not leak
5677 memory for the obsolete router descriptors in it. Bugfix on
5678 0.2.0.33; fixes bug 672.
5679 - Hidden service clients didn't use a cached service descriptor that
5680 was older than 15 minutes, but wouldn't fetch a new one either,
5681 because there was already one in the cache. Now, fetch a v2
5682 descriptor unless the same descriptor was added to the cache within
5683 the last 15 minutes. Fixes bug 997; reported by Marcus Griep.
5686 Changes in version 0.2.1.16-rc - 2009-06-20
5687 Tor 0.2.1.16-rc speeds up performance for fast exit relays, and fixes
5688 a bunch of minor bugs.
5691 - Fix an edge case where a malicious exit relay could convince a
5692 controller that the client's DNS question resolves to an internal IP
5693 address. Bug found and fixed by "optimist"; bugfix on 0.1.2.8-beta.
5695 o Major performance improvements (on 0.2.0.x):
5696 - Disable and refactor some debugging checks that forced a linear scan
5697 over the whole server-side DNS cache. These accounted for over 50%
5698 of CPU time on a relatively busy exit node's gprof profile. Found
5700 - Disable some debugging checks that appeared in exit node profile
5704 - Update to the "June 3 2009" ip-to-country file.
5705 - Do not have tor-resolve automatically refuse all .onion addresses;
5706 if AutomapHostsOnResolve is set in your torrc, this will work fine.
5708 o Minor bugfixes (on 0.2.0.x):
5709 - Log correct error messages for DNS-related network errors on
5711 - Fix a race condition that could cause crashes or memory corruption
5712 when running as a server with a controller listening for log
5714 - Avoid crashing when we have a policy specified in a DirPolicy or
5715 SocksPolicy or ReachableAddresses option with ports set on it,
5716 and we re-load the policy. May fix bug 996.
5717 - Hidden service clients didn't use a cached service descriptor that
5718 was older than 15 minutes, but wouldn't fetch a new one either,
5719 because there was already one in the cache. Now, fetch a v2
5720 descriptor unless the same descriptor was added to the cache within
5721 the last 15 minutes. Fixes bug 997; reported by Marcus Griep.
5723 o Minor bugfixes (on 0.2.1.x):
5724 - Don't warn users about low port and hibernation mix when they
5725 provide a *ListenAddress directive to fix that. Bugfix on
5727 - When switching back and forth between bridge mode, do not start
5728 gathering GeoIP data until two hours have passed.
5729 - Do not complain that the user has requested an excluded node as
5730 an exit when the node is not really an exit. This could happen
5731 because the circuit was for testing, or an introduction point.
5735 Changes in version 0.2.1.15-rc - 2009-05-25
5736 Tor 0.2.1.15-rc marks the second release candidate for the 0.2.1.x
5737 series. It fixes a major bug on fast exit relays, as well as a variety
5740 o Major bugfixes (on 0.2.0.x):
5741 - Fix a timing-dependent, allocator-dependent, DNS-related crash bug
5742 that would occur on some exit nodes when DNS failures and timeouts
5743 occurred in certain patterns. Fix for bug 957.
5745 o Minor bugfixes (on 0.2.0.x):
5746 - Actually return -1 in the error case for read_bandwidth_usage().
5747 Harmless bug, since we currently don't care about the return value
5748 anywhere. Bugfix on 0.2.0.9-alpha.
5749 - Provide a more useful log message if bug 977 (related to buffer
5750 freelists) ever reappears, and do not crash right away.
5751 - Fix an assertion failure on 64-bit platforms when we allocated
5752 memory right up to the end of a memarea, then realigned the memory
5753 one step beyond the end. Fixes a possible cause of bug 930.
5754 - Protect the count of open sockets with a mutex, so we can't
5755 corrupt it when two threads are closing or opening sockets at once.
5756 Fix for bug 939. Bugfix on 0.2.0.1-alpha.
5757 - Don't allow a bridge to publish its router descriptor to a
5758 non-bridge directory authority. Fixes part of bug 932.
5759 - When we change to or from being a bridge, reset our counts of
5760 client usage by country. Fixes bug 932.
5761 - Fix a bug that made stream bandwidth get misreported to the
5763 - Stop using malloc_usable_size() to use more area than we had
5764 actually allocated: it was safe, but made valgrind really unhappy.
5765 - Fix a memory leak when v3 directory authorities load their keys
5766 and cert from disk. Bugfix on 0.2.0.1-alpha.
5768 o Minor bugfixes (on 0.2.1.x):
5769 - Fix use of freed memory when deciding to mark a non-addable
5770 descriptor as never-downloadable. Bugfix on 0.2.1.9-alpha.
5773 Changes in version 0.2.1.14-rc - 2009-04-12
5774 Tor 0.2.1.14-rc marks the first release candidate for the 0.2.1.x
5775 series. It begins fixing some major performance problems, and also
5776 finally addresses the bug that was causing relays on dynamic IP
5777 addresses to fall out of the directory.
5780 - Clients replace entry guards that were chosen more than a few months
5781 ago. This change should significantly improve client performance,
5782 especially once more people upgrade, since relays that have been
5783 a guard for a long time are currently overloaded.
5785 o Major bugfixes (on 0.2.0):
5786 - Finally fix the bug where dynamic-IP relays disappear when their
5787 IP address changes: directory mirrors were mistakenly telling
5788 them their old address if they asked via begin_dir, so they
5789 never got an accurate answer about their new address, so they
5790 just vanished after a day. For belt-and-suspenders, relays that
5791 don't set Address in their config now avoid using begin_dir for
5792 all direct connections. Should fix bugs 827, 883, and 900.
5793 - Relays were falling out of the networkstatus consensus for
5794 part of a day if they changed their local config but the
5795 authorities discarded their new descriptor as "not sufficiently
5796 different". Now directory authorities accept a descriptor as changed
5797 if bandwidthrate or bandwidthburst changed. Partial fix for bug 962;
5799 - Avoid crashing in the presence of certain malformed descriptors.
5800 Found by lark, and by automated fuzzing.
5803 - When generating circuit events with verbose nicknames for
5804 controllers, try harder to look up nicknames for routers on a
5805 circuit. (Previously, we would look in the router descriptors we had
5806 for nicknames, but not in the consensus.) Partial fix for bug 941.
5807 - If the bridge config line doesn't specify a port, assume 443.
5808 This makes bridge lines a bit smaller and easier for users to
5810 - Raise the minimum bandwidth to be a relay from 20000 bytes to 20480
5811 bytes (aka 20KB/s), to match our documentation. Also update
5812 directory authorities so they always assign the Fast flag to relays
5813 with 20KB/s of capacity. Now people running relays won't suddenly
5814 find themselves not seeing any use, if the network gets faster
5816 - Update to the "April 3 2009" ip-to-country file.
5819 - Avoid trying to print raw memory to the logs when we decide to
5820 give up on downloading a given relay descriptor. Bugfix on
5822 - In tor-resolve, when the Tor client to use is specified by
5823 <hostname>:<port>, actually use the specified port rather than
5824 defaulting to 9050. Bugfix on 0.2.1.6-alpha.
5825 - Make directory usage recording work again. Bugfix on 0.2.1.6-alpha.
5826 - When starting with a cache over a few days old, do not leak
5827 memory for the obsolete router descriptors in it. Bugfix on
5829 - Avoid double-free on list of successfully uploaded hidden
5830 service discriptors. Fix for bug 948. Bugfix on 0.2.1.6-alpha.
5831 - Change memarea_strndup() implementation to work even when
5832 duplicating a string at the end of a page. This bug was
5833 harmless for now, but could have meant crashes later. Fix by
5834 lark. Bugfix on 0.2.1.1-alpha.
5835 - Limit uploaded directory documents to be 16M rather than 500K.
5836 The directory authorities were refusing v3 consensus votes from
5837 other authorities, since the votes are now 504K. Fixes bug 959;
5838 bugfix on 0.0.2pre17 (where we raised it from 50K to 500K ;).
5839 - Directory authorities should never send a 503 "busy" response to
5840 requests for votes or keys. Bugfix on 0.2.0.8-alpha; exposed by
5844 Changes in version 0.2.1.13-alpha - 2009-03-09
5845 Tor 0.2.1.13-alpha includes another big pile of minor bugfixes and
5846 cleanups. We're finally getting close to a release candidate.
5849 - Correctly update the list of which countries we exclude as
5850 exits, when the GeoIP file is loaded or reloaded. Diagnosed by
5851 lark. Bugfix on 0.2.1.6-alpha.
5853 o Minor bugfixes (on 0.2.0.x and earlier):
5854 - Automatically detect MacOSX versions earlier than 10.4.0, and
5855 disable kqueue from inside Tor when running with these versions.
5856 We previously did this from the startup script, but that was no
5857 help to people who didn't use the startup script. Resolves bug 863.
5858 - When we had picked an exit node for a connection, but marked it as
5859 "optional", and it turned out we had no onion key for the exit,
5860 stop wanting that exit and try again. This situation may not
5861 be possible now, but will probably become feasible with proposal
5862 158. Spotted by rovv. Fixes another case of bug 752.
5863 - Clients no longer cache certificates for authorities they do not
5864 recognize. Bugfix on 0.2.0.9-alpha.
5865 - When we can't transmit a DNS request due to a network error, retry
5866 it after a while, and eventually transmit a failing response to
5867 the RESOLVED cell. Bugfix on 0.1.2.5-alpha.
5868 - If the controller claimed responsibility for a stream, but that
5869 stream never finished making its connection, it would live
5870 forever in circuit_wait state. Now we close it after SocksTimeout
5871 seconds. Bugfix on 0.1.2.7-alpha; reported by Mike Perry.
5872 - Drop begin cells to a hidden service if they come from the middle
5873 of a circuit. Patch from lark.
5874 - When we erroneously receive two EXTEND cells for the same circuit
5875 ID on the same connection, drop the second. Patch from lark.
5876 - Fix a crash that occurs on exit nodes when a nameserver request
5877 timed out. Bugfix on 0.1.2.1-alpha; our CLEAR debugging code had
5878 been suppressing the bug since 0.1.2.10-alpha. Partial fix for
5880 - Do not assume that a stack-allocated character array will be
5881 64-bit aligned on platforms that demand that uint64_t access is
5882 aligned. Possible fix for bug 604.
5883 - Parse dates and IPv4 addresses in a locale- and libc-independent
5884 manner, to avoid platform-dependent behavior on malformed input.
5885 - Build correctly when configured to build outside the main source
5886 path. Patch from Michael Gold.
5887 - We were already rejecting relay begin cells with destination port
5888 of 0. Now also reject extend cells with destination port or address
5889 of 0. Suggested by lark.
5891 o Minor bugfixes (on 0.2.1.x):
5892 - Don't re-extend introduction circuits if we ran out of RELAY_EARLY
5893 cells. Bugfix on 0.2.1.3-alpha. Fixes more of bug 878.
5894 - If we're an exit node, scrub the IP address to which we are exiting
5895 in the logs. Bugfix on 0.2.1.8-alpha.
5898 - On Linux, use the prctl call to re-enable core dumps when the user
5900 - New controller event NEWCONSENSUS that lists the networkstatus
5901 lines for every recommended relay. Now controllers like Torflow
5902 can keep up-to-date on which relays they should be using.
5903 - Update to the "February 26 2009" ip-to-country file.
5906 Changes in version 0.2.0.34 - 2009-02-08
5907 Tor 0.2.0.34 features several more security-related fixes. You should
5908 upgrade, especially if you run an exit relay (remote crash) or a
5909 directory authority (remote infinite loop), or you're on an older
5910 (pre-XP) or not-recently-patched Windows (remote exploit).
5912 This release marks end-of-life for Tor 0.1.2.x. Those Tor versions
5913 have many known flaws, and nobody should be using them. You should
5914 upgrade. If you're using a Linux or BSD and its packages are obsolete,
5915 stop using those packages and upgrade anyway.
5918 - Fix an infinite-loop bug on handling corrupt votes under certain
5919 circumstances. Bugfix on 0.2.0.8-alpha.
5920 - Fix a temporary DoS vulnerability that could be performed by
5921 a directory mirror. Bugfix on 0.2.0.9-alpha; reported by lark.
5922 - Avoid a potential crash on exit nodes when processing malformed
5923 input. Remote DoS opportunity. Bugfix on 0.2.0.33.
5924 - Do not accept incomplete ipv4 addresses (like 192.168.0) as valid.
5925 Spec conformance issue. Bugfix on Tor 0.0.2pre27.
5928 - Fix compilation on systems where time_t is a 64-bit integer.
5929 Patch from Matthias Drochner.
5930 - Don't consider expiring already-closed client connections. Fixes
5931 bug 893. Bugfix on 0.0.2pre20.
5934 Changes in version 0.2.1.12-alpha - 2009-02-08
5935 Tor 0.2.1.12-alpha features several more security-related fixes. You
5936 should upgrade, especially if you run an exit relay (remote crash) or
5937 a directory authority (remote infinite loop), or you're on an older
5938 (pre-XP) or not-recently-patched Windows (remote exploit). It also
5939 includes a big pile of minor bugfixes and cleanups.
5942 - Fix an infinite-loop bug on handling corrupt votes under certain
5943 circumstances. Bugfix on 0.2.0.8-alpha.
5944 - Fix a temporary DoS vulnerability that could be performed by
5945 a directory mirror. Bugfix on 0.2.0.9-alpha; reported by lark.
5946 - Avoid a potential crash on exit nodes when processing malformed
5947 input. Remote DoS opportunity. Bugfix on 0.2.1.7-alpha.
5950 - Let controllers actually ask for the "clients_seen" event for
5951 getting usage summaries on bridge relays. Bugfix on 0.2.1.10-alpha;
5952 reported by Matt Edman.
5953 - Fix a compile warning on OSX Panther. Fixes bug 913; bugfix against
5955 - Fix a bug in address parsing that was preventing bridges or hidden
5956 service targets from being at IPv6 addresses.
5957 - Solve a bug that kept hardware crypto acceleration from getting
5958 enabled when accounting was turned on. Fixes bug 907. Bugfix on
5960 - Remove a bash-ism from configure.in to build properly on non-Linux
5961 platforms. Bugfix on 0.2.1.1-alpha.
5962 - Fix code so authorities _actually_ send back X-Descriptor-Not-New
5963 headers. Bugfix on 0.2.0.10-alpha.
5964 - Don't consider expiring already-closed client connections. Fixes
5965 bug 893. Bugfix on 0.0.2pre20.
5966 - Fix another interesting corner-case of bug 891 spotted by rovv:
5967 Previously, if two hosts had different amounts of clock drift, and
5968 one of them created a new connection with just the wrong timing,
5969 the other might decide to deprecate the new connection erroneously.
5970 Bugfix on 0.1.1.13-alpha.
5971 - Resolve a very rare crash bug that could occur when the user forced
5972 a nameserver reconfiguration during the middle of a nameserver
5973 probe. Fixes bug 526. Bugfix on 0.1.2.1-alpha.
5974 - Support changing value of ServerDNSRandomizeCase during SIGHUP.
5975 Bugfix on 0.2.1.7-alpha.
5976 - If we're using bridges and our network goes away, be more willing
5977 to forgive our bridges and try again when we get an application
5978 request. Bugfix on 0.2.0.x.
5981 - Support platforms where time_t is 64 bits long. (Congratulations,
5982 NetBSD!) Patch from Matthias Drochner.
5983 - Add a 'getinfo status/clients-seen' controller command, in case
5984 controllers want to hear clients_seen events but connect late.
5987 - Disable GCC's strict alias optimization by default, to avoid the
5988 likelihood of its introducing subtle bugs whenever our code violates
5989 the letter of C99's alias rules.
5992 Changes in version 0.2.0.33 - 2009-01-21
5993 Tor 0.2.0.33 fixes a variety of bugs that were making relays less
5994 useful to users. It also finally fixes a bug where a relay or client
5995 that's been off for many days would take a long time to bootstrap.
5997 This update also fixes an important security-related bug reported by
5998 Ilja van Sprundel. You should upgrade. (We'll send out more details
5999 about the bug once people have had some time to upgrade.)
6002 - Fix a heap-corruption bug that may be remotely triggerable on
6003 some platforms. Reported by Ilja van Sprundel.
6006 - When a stream at an exit relay is in state "resolving" or
6007 "connecting" and it receives an "end" relay cell, the exit relay
6008 would silently ignore the end cell and not close the stream. If
6009 the client never closes the circuit, then the exit relay never
6010 closes the TCP connection. Bug introduced in Tor 0.1.2.1-alpha;
6012 - When sending CREATED cells back for a given circuit, use a 64-bit
6013 connection ID to find the right connection, rather than an addr:port
6014 combination. Now that we can have multiple OR connections between
6015 the same ORs, it is no longer possible to use addr:port to uniquely
6016 identify a connection.
6017 - Bridge relays that had DirPort set to 0 would stop fetching
6018 descriptors shortly after startup, and then briefly resume
6019 after a new bandwidth test and/or after publishing a new bridge
6020 descriptor. Bridge users that try to bootstrap from them would
6021 get a recent networkstatus but would get descriptors from up to
6022 18 hours earlier, meaning most of the descriptors were obsolete
6023 already. Reported by Tas; bugfix on 0.2.0.13-alpha.
6024 - Prevent bridge relays from serving their 'extrainfo' document
6025 to anybody who asks, now that extrainfo docs include potentially
6026 sensitive aggregated client geoip summaries. Bugfix on
6028 - If the cached networkstatus consensus is more than five days old,
6029 discard it rather than trying to use it. In theory it could be
6030 useful because it lists alternate directory mirrors, but in practice
6031 it just means we spend many minutes trying directory mirrors that
6032 are long gone from the network. Also discard router descriptors as
6033 we load them if they are more than five days old, since the onion
6034 key is probably wrong by now. Bugfix on 0.2.0.x. Fixes bug 887.
6037 - Do not mark smartlist_bsearch_idx() function as ATTR_PURE. This bug
6038 could make gcc generate non-functional binary search code. Bugfix
6040 - Build correctly on platforms without socklen_t.
6041 - Compile without warnings on solaris.
6042 - Avoid potential crash on internal error during signature collection.
6043 Fixes bug 864. Patch from rovv.
6044 - Correct handling of possible malformed authority signing key
6045 certificates with internal signature types. Fixes bug 880.
6046 Bugfix on 0.2.0.3-alpha.
6047 - Fix a hard-to-trigger resource leak when logging credential status.
6049 - When we can't initialize DNS because the network is down, do not
6050 automatically stop Tor from starting. Instead, we retry failed
6051 dns_init() every 10 minutes, and change the exit policy to reject
6052 *:* until one succeeds. Fixes bug 691.
6053 - Use 64 bits instead of 32 bits for connection identifiers used with
6054 the controller protocol, to greatly reduce risk of identifier reuse.
6055 - When we're choosing an exit node for a circuit, and we have
6056 no pending streams, choose a good general exit rather than one that
6057 supports "all the pending streams". Bugfix on 0.1.1.x. Fix by rovv.
6058 - Fix another case of assuming, when a specific exit is requested,
6059 that we know more than the user about what hosts it allows.
6060 Fixes one case of bug 752. Patch from rovv.
6061 - Clip the MaxCircuitDirtiness config option to a minimum of 10
6062 seconds. Warn the user if lower values are given in the
6063 configuration. Bugfix on 0.1.0.1-rc. Patch by Sebastian.
6064 - Clip the CircuitBuildTimeout to a minimum of 30 seconds. Warn the
6065 user if lower values are given in the configuration. Bugfix on
6066 0.1.1.17-rc. Patch by Sebastian.
6067 - Fix a memory leak when we decline to add a v2 rendezvous descriptor to
6068 the cache because we already had a v0 descriptor with the same ID.
6069 Bugfix on 0.2.0.18-alpha.
6070 - Fix a race condition when freeing keys shared between main thread
6071 and CPU workers that could result in a memory leak. Bugfix on
6072 0.1.0.1-rc. Fixes bug 889.
6073 - Send a valid END cell back when a client tries to connect to a
6074 nonexistent hidden service port. Bugfix on 0.1.2.15. Fixes bug
6075 840. Patch from rovv.
6076 - Check which hops rendezvous stream cells are associated with to
6077 prevent possible guess-the-streamid injection attacks from
6078 intermediate hops. Fixes another case of bug 446. Based on patch
6080 - If a broken client asks a non-exit router to connect somewhere,
6081 do not even do the DNS lookup before rejecting the connection.
6082 Fixes another case of bug 619. Patch from rovv.
6083 - When a relay gets a create cell it can't decrypt (e.g. because it's
6084 using the wrong onion key), we were dropping it and letting the
6085 client time out. Now actually answer with a destroy cell. Fixes
6086 bug 904. Bugfix on 0.0.2pre8.
6088 o Minor bugfixes (hidden services):
6089 - Do not throw away existing introduction points on SIGHUP. Bugfix on
6090 0.0.6pre1. Patch by Karsten. Fixes bug 874.
6093 - Report the case where all signatures in a detached set are rejected
6094 differently than the case where there is an error handling the
6096 - When we realize that another process has modified our cached
6097 descriptors, print out a more useful error message rather than
6098 triggering an assertion. Fixes bug 885. Patch from Karsten.
6099 - Implement the 0x20 hack to better resist DNS poisoning: set the
6100 case on outgoing DNS requests randomly, and reject responses that do
6101 not match the case correctly. This logic can be disabled with the
6102 ServerDNSRamdomizeCase setting, if you are using one of the 0.3%
6103 of servers that do not reliably preserve case in replies. See
6104 "Increased DNS Forgery Resistance through 0x20-Bit Encoding"
6106 - Check DNS replies for more matching fields to better resist DNS
6108 - Never use OpenSSL compression: it wastes RAM and CPU trying to
6109 compress cells, which are basically all encrypted, compressed, or
6113 Changes in version 0.2.1.11-alpha - 2009-01-20
6114 Tor 0.2.1.11-alpha finishes fixing the "if your Tor is off for a
6115 week it will take a long time to bootstrap again" bug. It also fixes
6116 an important security-related bug reported by Ilja van Sprundel. You
6117 should upgrade. (We'll send out more details about the bug once people
6118 have had some time to upgrade.)
6121 - Fix a heap-corruption bug that may be remotely triggerable on
6122 some platforms. Reported by Ilja van Sprundel.
6125 - Discard router descriptors as we load them if they are more than
6126 five days old. Otherwise if Tor is off for a long time and then
6127 starts with cached descriptors, it will try to use the onion
6128 keys in those obsolete descriptors when building circuits. Bugfix
6129 on 0.2.0.x. Fixes bug 887.
6132 - Try to make sure that the version of Libevent we're running with
6133 is binary-compatible with the one we built with. May address bug
6135 - Make setting ServerDNSRandomizeCase to 0 actually work. Bugfix
6136 for bug 905. Bugfix on 0.2.1.7-alpha.
6137 - Add a new --enable-local-appdata configuration switch to change
6138 the default location of the datadir on win32 from APPDATA to
6139 LOCAL_APPDATA. In the future, we should migrate to LOCAL_APPDATA
6140 entirely. Patch from coderman.
6143 - Make outbound DNS packets respect the OutboundBindAddress setting.
6144 Fixes the bug part of bug 798. Bugfix on 0.1.2.2-alpha.
6145 - When our circuit fails at the first hop (e.g. we get a destroy
6146 cell back), avoid using that OR connection anymore, and also
6147 tell all the one-hop directory requests waiting for it that they
6148 should fail. Bugfix on 0.2.1.3-alpha.
6149 - In the torify(1) manpage, mention that tsocks will leak your
6153 Changes in version 0.2.1.10-alpha - 2009-01-06
6154 Tor 0.2.1.10-alpha fixes two major bugs in bridge relays (one that
6155 would make the bridge relay not so useful if it had DirPort set to 0,
6156 and one that could let an attacker learn a little bit of information
6157 about the bridge's users), and a bug that would cause your Tor relay
6158 to ignore a circuit create request it can't decrypt (rather than reply
6159 with an error). It also fixes a wide variety of other bugs.
6162 - If the cached networkstatus consensus is more than five days old,
6163 discard it rather than trying to use it. In theory it could
6164 be useful because it lists alternate directory mirrors, but in
6165 practice it just means we spend many minutes trying directory
6166 mirrors that are long gone from the network. Helps bug 887 a bit;
6168 - Bridge relays that had DirPort set to 0 would stop fetching
6169 descriptors shortly after startup, and then briefly resume
6170 after a new bandwidth test and/or after publishing a new bridge
6171 descriptor. Bridge users that try to bootstrap from them would
6172 get a recent networkstatus but would get descriptors from up to
6173 18 hours earlier, meaning most of the descriptors were obsolete
6174 already. Reported by Tas; bugfix on 0.2.0.13-alpha.
6175 - Prevent bridge relays from serving their 'extrainfo' document
6176 to anybody who asks, now that extrainfo docs include potentially
6177 sensitive aggregated client geoip summaries. Bugfix on
6181 - New controller event "clients_seen" to report a geoip-based summary
6182 of which countries we've seen clients from recently. Now controllers
6183 like Vidalia can show bridge operators that they're actually making
6185 - Build correctly against versions of OpenSSL 0.9.8 or later built
6186 without support for deprecated functions.
6187 - Update to the "December 19 2008" ip-to-country file.
6189 o Minor bugfixes (on 0.2.0.x):
6190 - Authorities now vote for the Stable flag for any router whose
6191 weighted MTBF is at least 5 days, regardless of the mean MTBF.
6192 - Do not remove routers as too old if we do not have any consensus
6193 document. Bugfix on 0.2.0.7-alpha.
6194 - Do not accept incomplete ipv4 addresses (like 192.168.0) as valid.
6195 Spec conformance issue. Bugfix on Tor 0.0.2pre27.
6196 - When an exit relay resolves a stream address to a local IP address,
6197 do not just keep retrying that same exit relay over and
6198 over. Instead, just close the stream. Addresses bug 872. Bugfix
6199 on 0.2.0.32. Patch from rovv.
6200 - If a hidden service sends us an END cell, do not consider
6201 retrying the connection; just close it. Patch from rovv.
6202 - When we made bridge authorities stop serving bridge descriptors over
6203 unencrypted links, we also broke DirPort reachability testing for
6204 bridges. So bridges with a non-zero DirPort were printing spurious
6205 warns to their logs. Bugfix on 0.2.0.16-alpha. Fixes bug 709.
6206 - When a relay gets a create cell it can't decrypt (e.g. because it's
6207 using the wrong onion key), we were dropping it and letting the
6208 client time out. Now actually answer with a destroy cell. Fixes
6209 bug 904. Bugfix on 0.0.2pre8.
6210 - Squeeze 2-5% out of client performance (according to oprofile) by
6211 improving the implementation of some policy-manipulation functions.
6213 o Minor bugfixes (on 0.2.1.x):
6214 - Make get_interface_address() function work properly again; stop
6215 guessing the wrong parts of our address as our address.
6216 - Do not cannibalize a circuit if we're out of RELAY_EARLY cells to
6217 send on that circuit. Otherwise we might violate the proposal-110
6218 limit. Bugfix on 0.2.1.3-alpha. Partial fix for bug 878. Diagnosis
6220 - When we're sending non-EXTEND cells to the first hop in a circuit,
6221 for example to use an encrypted directory connection, we don't need
6222 to use RELAY_EARLY cells: the first hop knows what kind of cell
6223 it is, and nobody else can even see the cell type. Conserving
6224 RELAY_EARLY cells makes it easier to cannibalize circuits like
6226 - Stop logging nameserver addresses in reverse order.
6227 - If we are retrying a directory download slowly over and over, do
6228 not automatically give up after the 254th failure. Bugfix on
6230 - Resume reporting accurate "stream end" reasons to the local control
6231 port. They were lost in the changes for Proposal 148. Bugfix on
6234 o Deprecated and removed features:
6235 - The old "tor --version --version" command, which would print out
6236 the subversion "Id" of most of the source files, is now removed. It
6237 turned out to be less useful than we'd expected, and harder to
6240 o Code simplifications and refactoring:
6241 - Change our header file guard macros to be less likely to conflict
6242 with system headers. Adam Langley noticed that we were conflicting
6243 with log.h on Android.
6244 - Tool-assisted documentation cleanup. Nearly every function or
6245 static variable in Tor should have its own documentation now.
6248 Changes in version 0.2.1.9-alpha - 2008-12-25
6249 Tor 0.2.1.9-alpha fixes many more bugs, some of them security-related.
6251 o New directory authorities:
6252 - gabelmoo (the authority run by Karsten Loesing) now has a new
6256 - Never use a connection with a mismatched address to extend a
6257 circuit, unless that connection is canonical. A canonical
6258 connection is one whose address is authenticated by the router's
6259 identity key, either in a NETINFO cell or in a router descriptor.
6260 - Avoid a possible memory corruption bug when receiving hidden service
6261 descriptors. Bugfix on 0.2.1.6-alpha.
6264 - Fix a logic error that would automatically reject all but the first
6265 configured DNS server. Bugfix on 0.2.1.5-alpha. Possible fix for
6266 part of bug 813/868. Bug spotted by coderman.
6267 - When a stream at an exit relay is in state "resolving" or
6268 "connecting" and it receives an "end" relay cell, the exit relay
6269 would silently ignore the end cell and not close the stream. If
6270 the client never closes the circuit, then the exit relay never
6271 closes the TCP connection. Bug introduced in 0.1.2.1-alpha;
6273 - When we can't initialize DNS because the network is down, do not
6274 automatically stop Tor from starting. Instead, retry failed
6275 dns_init() every 10 minutes, and change the exit policy to reject
6276 *:* until one succeeds. Fixes bug 691.
6279 - Give a better error message when an overzealous init script says
6280 "sudo -u username tor --user username". Makes Bug 882 easier for
6282 - When a directory authority gives us a new guess for our IP address,
6283 log which authority we used. Hopefully this will help us debug
6284 the recent complaints about bad IP address guesses.
6285 - Detect svn revision properly when we're using git-svn.
6286 - Try not to open more than one descriptor-downloading connection
6287 to an authority at once. This should reduce load on directory
6288 authorities. Fixes bug 366.
6289 - Add cross-certification to newly generated certificates, so that
6290 a signing key is enough information to look up a certificate.
6291 Partial implementation of proposal 157.
6292 - Start serving certificates by <identity digest, signing key digest>
6293 pairs. Partial implementation of proposal 157.
6294 - Clients now never report any stream end reason except 'MISC'.
6295 Implements proposal 148.
6296 - On platforms with a maximum syslog string length, truncate syslog
6297 messages to that length ourselves, rather than relying on the
6298 system to do it for us.
6299 - Optimize out calls to time(NULL) that occur for every IO operation,
6300 or for every cell. On systems where time() is a slow syscall,
6301 this fix will be slightly helpful.
6302 - Exit servers can now answer resolve requests for ip6.arpa addresses.
6303 - When we download a descriptor that we then immediately (as
6304 a directory authority) reject, do not retry downloading it right
6305 away. Should save some bandwidth on authorities. Fix for bug
6306 888. Patch by Sebastian Hahn.
6307 - When a download gets us zero good descriptors, do not notify
6308 Tor that new directory information has arrived.
6309 - Avoid some nasty corner cases in the logic for marking connections
6310 as too old or obsolete or noncanonical for circuits. Partial
6313 o Minor features (controller):
6314 - New CONSENSUS_ARRIVED event to note when a new consensus has
6315 been fetched and validated.
6316 - When we realize that another process has modified our cached
6317 descriptors file, print out a more useful error message rather
6318 than triggering an assertion. Fixes bug 885. Patch from Karsten.
6319 - Add an internal-use-only __ReloadTorrcOnSIGHUP option for
6320 controllers to prevent SIGHUP from reloading the
6321 configuration. Fixes bug 856.
6324 - Resume using the correct "REASON=" stream when telling the
6325 controller why we closed a stream. Bugfix in 0.2.1.1-alpha.
6326 - When a canonical connection appears later in our internal list
6327 than a noncanonical one for a given OR ID, always use the
6328 canonical one. Bugfix on 0.2.0.12-alpha. Fixes bug 805.
6330 - Clip the MaxCircuitDirtiness config option to a minimum of 10
6331 seconds. Warn the user if lower values are given in the
6332 configuration. Bugfix on 0.1.0.1-rc. Patch by Sebastian.
6333 - Clip the CircuitBuildTimeout to a minimum of 30 seconds. Warn the
6334 user if lower values are given in the configuration. Bugfix on
6335 0.1.1.17-rc. Patch by Sebastian.
6336 - Fix a race condition when freeing keys shared between main thread
6337 and CPU workers that could result in a memory leak. Bugfix on
6338 0.1.0.1-rc. Fixes bug 889.
6340 o Minor bugfixes (hidden services):
6341 - Do not throw away existing introduction points on SIGHUP (bugfix on
6342 0.0.6pre1); also, do not stall hidden services because we're
6343 throwing away introduction points; bugfix on 0.2.1.7-alpha. Spotted
6344 by John Brooks. Patch by Karsten. Fixes bug 874.
6345 - Fix a memory leak when we decline to add a v2 rendezvous
6346 descriptor to the cache because we already had a v0 descriptor
6347 with the same ID. Bugfix on 0.2.0.18-alpha.
6349 o Deprecated and removed features:
6350 - RedirectExits has been removed. It was deprecated since
6352 - Finally remove deprecated "EXTENDED_FORMAT" controller feature. It
6353 has been called EXTENDED_EVENTS since 0.1.2.4-alpha.
6354 - Cell pools are now always enabled; --disable-cell-pools is ignored.
6356 o Code simplifications and refactoring:
6357 - Rename the confusing or_is_obsolete field to the more appropriate
6358 is_bad_for_new_circs, and move it to or_connection_t where it
6360 - Move edge-only flags from connection_t to edge_connection_t: not
6361 only is this better coding, but on machines of plausible alignment,
6362 it should save 4-8 bytes per connection_t. "Every little bit helps."
6363 - Rename ServerDNSAllowBrokenResolvConf to ServerDNSAllowBrokenConfig
6364 for consistency; keep old option working for backward compatibility.
6365 - Simplify the code for finding connections to use for a circuit.
6368 Changes in version 0.2.1.8-alpha - 2008-12-08
6369 Tor 0.2.1.8-alpha fixes some crash bugs in earlier alpha releases,
6370 builds better on unusual platforms like Solaris and old OS X, and
6371 fixes a variety of other issues.
6374 - New DirPortFrontPage option that takes an html file and publishes
6375 it as "/" on the DirPort. Now relay operators can provide a
6376 disclaimer without needing to set up a separate webserver. There's
6377 a sample disclaimer in contrib/tor-exit-notice.html.
6380 - When the client is choosing entry guards, now it selects at most
6381 one guard from a given relay family. Otherwise we could end up with
6382 all of our entry points into the network run by the same operator.
6383 Suggested by Camilo Viecco. Fix on 0.1.1.11-alpha.
6386 - Fix a DOS opportunity during the voting signature collection process
6387 at directory authorities. Spotted by rovv. Bugfix on 0.2.0.x.
6388 - Fix a possible segfault when establishing an exit connection. Bugfix
6392 - Get file locking working on win32. Bugfix on 0.2.1.6-alpha. Fixes
6394 - Made Tor a little less aggressive about deleting expired
6395 certificates. Partial fix for bug 854.
6396 - Stop doing unaligned memory access that generated bus errors on
6397 sparc64. Bugfix on 0.2.0.10-alpha. Fix for bug 862.
6398 - Fix a crash bug when changing EntryNodes from the controller. Bugfix
6399 on 0.2.1.6-alpha. Fix for bug 867. Patched by Sebastian.
6400 - Make USR2 log-level switch take effect immediately. Bugfix on
6402 - If one win32 nameserver fails to get added, continue adding the
6403 rest, and don't automatically fail.
6404 - Use fcntl() for locking when flock() is not available. Should fix
6405 compilation on Solaris. Should fix Bug 873. Bugfix on 0.2.1.6-alpha.
6406 - Do not mark smartlist_bsearch_idx() function as ATTR_PURE. This bug
6407 could make gcc generate non-functional binary search code. Bugfix
6409 - Build correctly on platforms without socklen_t.
6410 - Avoid potential crash on internal error during signature collection.
6411 Fixes bug 864. Patch from rovv.
6412 - Do not use C's stdio library for writing to log files. This will
6413 improve logging performance by a minute amount, and will stop
6414 leaking fds when our disk is full. Fixes bug 861.
6415 - Stop erroneous use of O_APPEND in cases where we did not in fact
6416 want to re-seek to the end of a file before every last write().
6417 - Correct handling of possible malformed authority signing key
6418 certificates with internal signature types. Fixes bug 880. Bugfix
6420 - Fix a hard-to-trigger resource leak when logging credential status.
6424 - Directory mirrors no longer fetch the v1 directory or
6425 running-routers files. They are obsolete, and nobody asks for them
6426 anymore. This is the first step to making v1 authorities obsolete.
6428 o Minor features (controller):
6429 - Return circuit purposes in response to GETINFO circuit-status. Fixes
6433 Changes in version 0.2.0.32 - 2008-11-20
6434 Tor 0.2.0.32 fixes a major security problem in Debian and Ubuntu
6435 packages (and maybe other packages) noticed by Theo de Raadt, fixes
6436 a smaller security flaw that might allow an attacker to access local
6437 services, further improves hidden service performance, and fixes a
6438 variety of other issues.
6441 - The "User" and "Group" config options did not clear the
6442 supplementary group entries for the Tor process. The "User" option
6443 is now more robust, and we now set the groups to the specified
6444 user's primary group. The "Group" option is now ignored. For more
6445 detailed logging on credential switching, set CREDENTIAL_LOG_LEVEL
6446 in common/compat.c to LOG_NOTICE or higher. Patch by Jacob Appelbaum
6447 and Steven Murdoch. Bugfix on 0.0.2pre14. Fixes bug 848 and 857.
6448 - The "ClientDNSRejectInternalAddresses" config option wasn't being
6449 consistently obeyed: if an exit relay refuses a stream because its
6450 exit policy doesn't allow it, we would remember what IP address
6451 the relay said the destination address resolves to, even if it's
6452 an internal IP address. Bugfix on 0.2.0.7-alpha; patch by rovv.
6455 - Fix a DOS opportunity during the voting signature collection process
6456 at directory authorities. Spotted by rovv. Bugfix on 0.2.0.x.
6458 o Major bugfixes (hidden services):
6459 - When fetching v0 and v2 rendezvous service descriptors in parallel,
6460 we were failing the whole hidden service request when the v0
6461 descriptor fetch fails, even if the v2 fetch is still pending and
6462 might succeed. Similarly, if the last v2 fetch fails, we were
6463 failing the whole hidden service request even if a v0 fetch is
6464 still pending. Fixes bug 814. Bugfix on 0.2.0.10-alpha.
6465 - When extending a circuit to a hidden service directory to upload a
6466 rendezvous descriptor using a BEGIN_DIR cell, almost 1/6 of all
6467 requests failed, because the router descriptor has not been
6468 downloaded yet. In these cases, do not attempt to upload the
6469 rendezvous descriptor, but wait until the router descriptor is
6470 downloaded and retry. Likewise, do not attempt to fetch a rendezvous
6471 descriptor from a hidden service directory for which the router
6472 descriptor has not yet been downloaded. Fixes bug 767. Bugfix
6476 - Fix several infrequent memory leaks spotted by Coverity.
6477 - When testing for libevent functions, set the LDFLAGS variable
6478 correctly. Found by Riastradh.
6479 - Avoid a bug where the FastFirstHopPK 0 option would keep Tor from
6480 bootstrapping with tunneled directory connections. Bugfix on
6481 0.1.2.5-alpha. Fixes bug 797. Found by Erwin Lam.
6482 - When asked to connect to A.B.exit:80, if we don't know the IP for A
6483 and we know that server B rejects most-but-not all connections to
6484 port 80, we would previously reject the connection. Now, we assume
6485 the user knows what they were asking for. Fixes bug 752. Bugfix
6486 on 0.0.9rc5. Diagnosed by BarkerJr.
6487 - If we overrun our per-second write limits a little, count this as
6488 having used up our write allocation for the second, and choke
6489 outgoing directory writes. Previously, we had only counted this when
6490 we had met our limits precisely. Fixes bug 824. Patch from by rovv.
6491 Bugfix on 0.2.0.x (??).
6492 - Remove the old v2 directory authority 'lefkada' from the default
6493 list. It has been gone for many months.
6494 - Stop doing unaligned memory access that generated bus errors on
6495 sparc64. Bugfix on 0.2.0.10-alpha. Fixes bug 862.
6496 - Make USR2 log-level switch take effect immediately. Bugfix on
6499 o Minor bugfixes (controller):
6500 - Make DNS resolved events into "CLOSED", not "FAILED". Bugfix on
6501 0.1.2.5-alpha. Fix by Robert Hogan. Resolves bug 807.
6504 Changes in version 0.2.1.7-alpha - 2008-11-08
6505 Tor 0.2.1.7-alpha fixes a major security problem in Debian and Ubuntu
6506 packages (and maybe other packages) noticed by Theo de Raadt, fixes
6507 a smaller security flaw that might allow an attacker to access local
6508 services, adds better defense against DNS poisoning attacks on exit
6509 relays, further improves hidden service performance, and fixes a
6510 variety of other issues.
6513 - The "ClientDNSRejectInternalAddresses" config option wasn't being
6514 consistently obeyed: if an exit relay refuses a stream because its
6515 exit policy doesn't allow it, we would remember what IP address
6516 the relay said the destination address resolves to, even if it's
6517 an internal IP address. Bugfix on 0.2.0.7-alpha; patch by rovv.
6518 - The "User" and "Group" config options did not clear the
6519 supplementary group entries for the Tor process. The "User" option
6520 is now more robust, and we now set the groups to the specified
6521 user's primary group. The "Group" option is now ignored. For more
6522 detailed logging on credential switching, set CREDENTIAL_LOG_LEVEL
6523 in common/compat.c to LOG_NOTICE or higher. Patch by Jacob Appelbaum
6524 and Steven Murdoch. Bugfix on 0.0.2pre14. Fixes bug 848.
6525 - Do not use or believe expired v3 authority certificates. Patch
6526 from Karsten. Bugfix in 0.2.0.x. Fixes bug 851.
6529 - Now NodeFamily and MyFamily config options allow spaces in
6530 identity fingerprints, so it's easier to paste them in.
6531 Suggested by Lucky Green.
6532 - Implement the 0x20 hack to better resist DNS poisoning: set the
6533 case on outgoing DNS requests randomly, and reject responses that do
6534 not match the case correctly. This logic can be disabled with the
6535 ServerDNSRandomizeCase setting, if you are using one of the 0.3%
6536 of servers that do not reliably preserve case in replies. See
6537 "Increased DNS Forgery Resistance through 0x20-Bit Encoding"
6539 - Preserve case in replies to DNSPort requests in order to support
6540 the 0x20 hack for resisting DNS poisoning attacks.
6542 o Hidden service performance improvements:
6543 - When the client launches an introduction circuit, retry with a
6544 new circuit after 30 seconds rather than 60 seconds.
6545 - Launch a second client-side introduction circuit in parallel
6546 after a delay of 15 seconds (based on work by Christian Wilms).
6547 - Hidden services start out building five intro circuits rather
6548 than three, and when the first three finish they publish a service
6549 descriptor using those. Now we publish our service descriptor much
6550 faster after restart.
6553 - Minor fix in the warning messages when you're having problems
6554 bootstrapping; also, be more forgiving of bootstrap problems when
6555 we're still making incremental progress on a given bootstrap phase.
6556 - When we're choosing an exit node for a circuit, and we have
6557 no pending streams, choose a good general exit rather than one that
6558 supports "all the pending streams". Bugfix on 0.1.1.x. Fix by rovv.
6559 - Send a valid END cell back when a client tries to connect to a
6560 nonexistent hidden service port. Bugfix on 0.1.2.15. Fixes bug
6561 840. Patch from rovv.
6562 - If a broken client asks a non-exit router to connect somewhere,
6563 do not even do the DNS lookup before rejecting the connection.
6564 Fixes another case of bug 619. Patch from rovv.
6565 - Fix another case of assuming, when a specific exit is requested,
6566 that we know more than the user about what hosts it allows.
6567 Fixes another case of bug 752. Patch from rovv.
6568 - Check which hops rendezvous stream cells are associated with to
6569 prevent possible guess-the-streamid injection attacks from
6570 intermediate hops. Fixes another case of bug 446. Based on patch
6572 - Avoid using a negative right-shift when comparing 32-bit
6573 addresses. Possible fix for bug 845 and bug 811.
6574 - Make the assert_circuit_ok() function work correctly on circuits that
6575 have already been marked for close.
6576 - Fix read-off-the-end-of-string error in unit tests when decoding
6577 introduction points.
6578 - Fix uninitialized size field for memory area allocation: may improve
6579 memory performance during directory parsing.
6580 - Treat duplicate certificate fetches as failures, so that we do
6581 not try to re-fetch an expired certificate over and over and over.
6582 - Do not say we're fetching a certificate when we'll in fact skip it
6583 because of a pending download.
6586 Changes in version 0.2.1.6-alpha - 2008-09-30
6587 Tor 0.2.1.6-alpha further improves performance and robustness of
6588 hidden services, starts work on supporting per-country relay selection,
6589 and fixes a variety of smaller issues.
6592 - Implement proposal 121: make it possible to build hidden services
6593 that only certain clients are allowed to connect to. This is
6594 enforced at several points, so that unauthorized clients are unable
6595 to send INTRODUCE cells to the service, or even (depending on the
6596 type of authentication) to learn introduction points. This feature
6597 raises the bar for certain kinds of active attacks against hidden
6598 services. Code by Karsten Loesing.
6599 - Relays now store and serve v2 hidden service descriptors by default,
6600 i.e., the new default value for HidServDirectoryV2 is 1. This is
6601 the last step in proposal 114, which aims to make hidden service
6602 lookups more reliable.
6603 - Start work to allow node restrictions to include country codes. The
6604 syntax to exclude nodes in a country with country code XX is
6605 "ExcludeNodes {XX}". Patch from Robert Hogan. It still needs some
6606 refinement to decide what config options should take priority if
6607 you ask to both use a particular node and exclude it.
6608 - Allow ExitNodes list to include IP ranges and country codes, just
6609 like the Exclude*Nodes lists. Patch from Robert Hogan.
6612 - Fix a bug when parsing ports in tor_addr_port_parse() that caused
6613 Tor to fail to start if you had it configured to use a bridge
6614 relay. Fixes bug 809. Bugfix on 0.2.1.5-alpha.
6615 - When extending a circuit to a hidden service directory to upload a
6616 rendezvous descriptor using a BEGIN_DIR cell, almost 1/6 of all
6617 requests failed, because the router descriptor had not been
6618 downloaded yet. In these cases, we now wait until the router
6619 descriptor is downloaded, and then retry. Likewise, clients
6620 now skip over a hidden service directory if they don't yet have
6621 its router descriptor, rather than futilely requesting it and
6622 putting mysterious complaints in the logs. Fixes bug 767. Bugfix
6624 - When fetching v0 and v2 rendezvous service descriptors in parallel,
6625 we were failing the whole hidden service request when the v0
6626 descriptor fetch fails, even if the v2 fetch is still pending and
6627 might succeed. Similarly, if the last v2 fetch fails, we were
6628 failing the whole hidden service request even if a v0 fetch is
6629 still pending. Fixes bug 814. Bugfix on 0.2.0.10-alpha.
6630 - DNS replies need to have names matching their requests, but
6631 these names should be in the questions section, not necessarily
6632 in the answers section. Fixes bug 823. Bugfix on 0.2.1.5-alpha.
6635 - Update to the "September 1 2008" ip-to-country file.
6636 - Allow ports 465 and 587 in the default exit policy again. We had
6637 rejected them in 0.1.0.15, because back in 2005 they were commonly
6638 misconfigured and ended up as spam targets. We hear they are better
6639 locked down these days.
6640 - Use a lockfile to make sure that two Tor processes are not
6641 simultaneously running with the same datadir.
6642 - Serve the latest v3 networkstatus consensus via the control
6643 port. Use "getinfo dir/status-vote/current/consensus" to fetch it.
6644 - Better logging about stability/reliability calculations on directory
6646 - Drop the requirement to have an open dir port for storing and
6647 serving v2 hidden service descriptors.
6648 - Directory authorities now serve a /tor/dbg-stability.txt URL to
6649 help debug WFU and MTBF calculations.
6650 - Implement most of Proposal 152: allow specialized servers to permit
6651 single-hop circuits, and clients to use those servers to build
6652 single-hop circuits when using a specialized controller. Patch
6653 from Josh Albrecht. Resolves feature request 768.
6654 - Add a -p option to tor-resolve for specifying the SOCKS port: some
6655 people find host:port too confusing.
6656 - Make TrackHostExit mappings expire a while after their last use, not
6657 after their creation. Patch from Robert Hogan.
6658 - Provide circuit purposes along with circuit events to the controller.
6661 - Fix compile on OpenBSD 4.4-current. Bugfix on 0.2.1.5-alpha.
6663 - Fixed some memory leaks -- some quite frequent, some almost
6664 impossible to trigger -- based on results from Coverity.
6665 - When testing for libevent functions, set the LDFLAGS variable
6666 correctly. Found by Riastradh.
6667 - Fix an assertion bug in parsing policy-related options; possible fix
6669 - Catch and report a few more bootstrapping failure cases when Tor
6670 fails to establish a TCP connection. Cleanup on 0.2.1.x.
6671 - Avoid a bug where the FastFirstHopPK 0 option would keep Tor from
6672 bootstrapping with tunneled directory connections. Bugfix on
6673 0.1.2.5-alpha. Fixes bug 797. Found by Erwin Lam.
6674 - When asked to connect to A.B.exit:80, if we don't know the IP for A
6675 and we know that server B rejects most-but-not all connections to
6676 port 80, we would previously reject the connection. Now, we assume
6677 the user knows what they were asking for. Fixes bug 752. Bugfix
6678 on 0.0.9rc5. Diagnosed by BarkerJr.
6679 - If we are not using BEGIN_DIR cells, don't attempt to contact hidden
6680 service directories if they have no advertised dir port. Bugfix
6682 - If we overrun our per-second write limits a little, count this as
6683 having used up our write allocation for the second, and choke
6684 outgoing directory writes. Previously, we had only counted this when
6685 we had met our limits precisely. Fixes bug 824. Patch by rovv.
6686 Bugfix on 0.2.0.x (??).
6687 - Avoid a "0 divided by 0" calculation when calculating router uptime
6688 at directory authorities. Bugfix on 0.2.0.8-alpha.
6689 - Make DNS resolved controller events into "CLOSED", not
6690 "FAILED". Bugfix on 0.1.2.5-alpha. Fix by Robert Hogan. Resolves
6692 - Fix a bug where an unreachable relay would establish enough
6693 reachability testing circuits to do a bandwidth test -- if
6694 we already have a connection to the middle hop of the testing
6695 circuit, then it could establish the last hop by using the existing
6696 connection. Bugfix on 0.1.2.2-alpha, exposed when we made testing
6697 circuits no longer use entry guards in 0.2.1.3-alpha.
6698 - If we have correct permissions on $datadir, we complain to stdout
6699 and fail to start. But dangerous permissions on
6700 $datadir/cached-status/ would cause us to open a log and complain
6701 there. Now complain to stdout and fail to start in both cases. Fixes
6702 bug 820, reported by seeess.
6703 - Remove the old v2 directory authority 'lefkada' from the default
6704 list. It has been gone for many months.
6706 o Code simplifications and refactoring:
6707 - Revise the connection_new functions so that a more typesafe variant
6708 exists. This will work better with Coverity, and let us find any
6709 actual mistakes we're making here.
6710 - Refactor unit testing logic so that dmalloc can be used sensibly
6711 with unit tests to check for memory leaks.
6712 - Move all hidden-service related fields from connection and circuit
6713 structure to substructures: this way they won't eat so much memory.
6716 Changes in version 0.2.0.31 - 2008-09-03
6717 Tor 0.2.0.31 addresses two potential anonymity issues, starts to fix
6718 a big bug we're seeing where in rare cases traffic from one Tor stream
6719 gets mixed into another stream, and fixes a variety of smaller issues.
6722 - Make sure that two circuits can never exist on the same connection
6723 with the same circuit ID, even if one is marked for close. This
6724 is conceivably a bugfix for bug 779. Bugfix on 0.1.0.4-rc.
6725 - Relays now reject risky extend cells: if the extend cell includes
6726 a digest of all zeroes, or asks to extend back to the relay that
6727 sent the extend cell, tear down the circuit. Ideas suggested
6729 - If not enough of our entry guards are available so we add a new
6730 one, we might use the new one even if it overlapped with the
6731 current circuit's exit relay (or its family). Anonymity bugfix
6732 pointed out by rovv.
6735 - Recover 3-7 bytes that were wasted per memory chunk. Fixes bug
6736 794; bug spotted by rovv. Bugfix on 0.2.0.1-alpha.
6737 - Correctly detect the presence of the linux/netfilter_ipv4.h header
6738 when building against recent kernels. Bugfix on 0.1.2.1-alpha.
6739 - Pick size of default geoip filename string correctly on windows.
6740 Fixes bug 806. Bugfix on 0.2.0.30.
6741 - Make the autoconf script accept the obsolete --with-ssl-dir
6742 option as an alias for the actually-working --with-openssl-dir
6743 option. Fix the help documentation to recommend --with-openssl-dir.
6744 Based on a patch by "Dave". Bugfix on 0.2.0.1-alpha.
6745 - When using the TransPort option on OpenBSD, and using the User
6746 option to change UID and drop privileges, make sure to open
6747 /dev/pf before dropping privileges. Fixes bug 782. Patch from
6748 Christopher Davis. Bugfix on 0.1.2.1-alpha.
6749 - Try to attach connections immediately upon receiving a RENDEZVOUS2
6750 or RENDEZVOUS_ESTABLISHED cell. This can save a second or two
6751 on the client side when connecting to a hidden service. Bugfix
6752 on 0.0.6pre1. Found and fixed by Christian Wilms; resolves bug 743.
6753 - When closing an application-side connection because its circuit is
6754 getting torn down, generate the stream event correctly. Bugfix on
6755 0.1.2.x. Anonymous patch.
6758 Changes in version 0.2.1.5-alpha - 2008-08-31
6759 Tor 0.2.1.5-alpha moves us closer to handling IPv6 destinations, puts
6760 in a lot of the infrastructure for adding authorization to hidden
6761 services, lays the groundwork for having clients read their load
6762 balancing information out of the networkstatus consensus rather than
6763 the individual router descriptors, addresses two potential anonymity
6764 issues, and fixes a variety of smaller issues.
6767 - Convert many internal address representations to optionally hold
6769 - Generate and accept IPv6 addresses in many protocol elements.
6770 - Make resolver code handle nameservers located at ipv6 addresses.
6771 - Begin implementation of proposal 121 ("Client authorization for
6772 hidden services"): configure hidden services with client
6773 authorization, publish descriptors for them, and configure
6774 authorization data for hidden services at clients. The next
6775 step is to actually access hidden services that perform client
6777 - More progress toward proposal 141: Network status consensus
6778 documents and votes now contain bandwidth information for each
6779 router and a summary of that router's exit policy. Eventually this
6780 will be used by clients so that they do not have to download every
6781 known descriptor before building circuits.
6783 o Major bugfixes (on 0.2.0.x and before):
6784 - When sending CREATED cells back for a given circuit, use a 64-bit
6785 connection ID to find the right connection, rather than an addr:port
6786 combination. Now that we can have multiple OR connections between
6787 the same ORs, it is no longer possible to use addr:port to uniquely
6788 identify a connection.
6789 - Relays now reject risky extend cells: if the extend cell includes
6790 a digest of all zeroes, or asks to extend back to the relay that
6791 sent the extend cell, tear down the circuit. Ideas suggested
6793 - If not enough of our entry guards are available so we add a new
6794 one, we might use the new one even if it overlapped with the
6795 current circuit's exit relay (or its family). Anonymity bugfix
6796 pointed out by rovv.
6799 - Recover 3-7 bytes that were wasted per memory chunk. Fixes bug
6800 794; bug spotted by rovv. Bugfix on 0.2.0.1-alpha.
6801 - When using the TransPort option on OpenBSD, and using the User
6802 option to change UID and drop privileges, make sure to open /dev/pf
6803 before dropping privileges. Fixes bug 782. Patch from Christopher
6804 Davis. Bugfix on 0.1.2.1-alpha.
6805 - Correctly detect the presence of the linux/netfilter_ipv4.h header
6806 when building against recent kernels. Bugfix on 0.1.2.1-alpha.
6807 - Add a missing safe_str() call for a debug log message.
6808 - Use 64 bits instead of 32 bits for connection identifiers used with
6809 the controller protocol, to greatly reduce risk of identifier reuse.
6810 - Make the autoconf script accept the obsolete --with-ssl-dir
6811 option as an alias for the actually-working --with-openssl-dir
6812 option. Fix the help documentation to recommend --with-openssl-dir.
6813 Based on a patch by "Dave". Bugfix on 0.2.0.1-alpha.
6816 - Rate-limit too-many-sockets messages: when they happen, they happen
6817 a lot. Resolves bug 748.
6818 - Resist DNS poisoning a little better by making sure that names in
6819 answer sections match.
6820 - Print the SOCKS5 error message string as well as the error code
6821 when a tor-resolve request fails. Patch from Jacob.
6824 Changes in version 0.2.1.4-alpha - 2008-08-04
6825 Tor 0.2.1.4-alpha fixes a pair of crash bugs in 0.2.1.3-alpha.
6828 - The address part of exit policies was not correctly written
6829 to router descriptors. This generated router descriptors that failed
6830 their self-checks. Noticed by phobos, fixed by Karsten. Bugfix
6832 - Tor triggered a false assert when extending a circuit to a relay
6833 but we already have a connection open to that relay. Noticed by
6834 phobos, fixed by Karsten. Bugfix on 0.2.1.3-alpha.
6837 - Fix a hidden service logging bug: in some edge cases, the router
6838 descriptor of a previously picked introduction point becomes
6839 obsolete and we need to give up on it rather than continually
6840 complaining that it has become obsolete. Observed by xiando. Bugfix
6844 - Take out the TestVia config option, since it was a workaround for
6845 a bug that was fixed in Tor 0.1.1.21.
6848 Changes in version 0.2.1.3-alpha - 2008-08-03
6849 Tor 0.2.1.3-alpha implements most of the pieces to prevent
6850 infinite-length circuit attacks (see proposal 110); fixes a bug that
6851 might cause exit relays to corrupt streams they send back; allows
6852 address patterns (e.g. 255.128.0.0/16) to appear in ExcludeNodes and
6853 ExcludeExitNodes config options; and fixes a big pile of bugs.
6855 o Bootstrapping bugfixes (on 0.2.1.x-alpha):
6856 - Send a bootstrap problem "warn" event on the first problem if the
6857 reason is NO_ROUTE (that is, our network is down).
6860 - Implement most of proposal 110: The first K cells to be sent
6861 along a circuit are marked as special "early" cells; only K "early"
6862 cells will be allowed. Once this code is universal, we can block
6863 certain kinds of DOS attack by requiring that EXTEND commands must
6864 be sent using an "early" cell.
6867 - Try to attach connections immediately upon receiving a RENDEZVOUS2
6868 or RENDEZVOUS_ESTABLISHED cell. This can save a second or two
6869 on the client side when connecting to a hidden service. Bugfix
6870 on 0.0.6pre1. Found and fixed by Christian Wilms; resolves bug 743.
6871 - Ensure that two circuits can never exist on the same connection
6872 with the same circuit ID, even if one is marked for close. This
6873 is conceivably a bugfix for bug 779; fixes a bug on 0.1.0.4-rc.
6876 - When relays do their initial bandwidth measurement, don't limit
6877 to just our entry guards for the test circuits. Otherwise we tend
6878 to have multiple test circuits going through a single entry guard,
6879 which makes our bandwidth test less accurate. Fixes part of bug 654;
6880 patch contributed by Josh Albrecht.
6881 - Add an ExcludeExitNodes option so users can list a set of nodes
6882 that should be be excluded from the exit node position, but
6883 allowed elsewhere. Implements proposal 151.
6884 - Allow address patterns (e.g., 255.128.0.0/16) to appear in
6885 ExcludeNodes and ExcludeExitNodes lists.
6886 - Change the implementation of ExcludeNodes and ExcludeExitNodes to
6887 be more efficient. Formerly it was quadratic in the number of
6888 servers; now it should be linear. Fixes bug 509.
6889 - Save 16-22 bytes per open circuit by moving the n_addr, n_port,
6890 and n_conn_id_digest fields into a separate structure that's
6891 only needed when the circuit has not yet attached to an n_conn.
6894 - Change the contrib/tor.logrotate script so it makes the new
6895 logs as "_tor:_tor" rather than the default, which is generally
6896 "root:wheel". Fixes bug 676, reported by Serge Koksharov.
6897 - Stop using __attribute__((nonnull)) with GCC: it can give us useful
6898 warnings (occasionally), but it can also cause the compiler to
6899 eliminate error-checking code. Suggested by Peter Gutmann.
6900 - When a hidden service is giving up on an introduction point candidate
6901 that was not included in the last published rendezvous descriptor,
6902 don't reschedule publication of the next descriptor. Fixes bug 763.
6904 - Mark RendNodes, RendExcludeNodes, HiddenServiceNodes, and
6905 HiddenServiceExcludeNodes as obsolete: they never worked properly,
6906 and nobody claims to be using them. Fixes bug 754. Bugfix on
6907 0.1.0.1-rc. Patch from Christian Wilms.
6908 - Fix a small alignment and memory-wasting bug on buffer chunks.
6911 o Minor bugfixes (controller):
6912 - When closing an application-side connection because its circuit
6913 is getting torn down, generate the stream event correctly.
6914 Bugfix on 0.1.2.x. Anonymous patch.
6917 - Remove all backward-compatibility code to support relays running
6918 versions of Tor so old that they no longer work at all on the
6922 Changes in version 0.2.0.30 - 2008-07-15
6924 - Stop using __attribute__((nonnull)) with GCC: it can give us useful
6925 warnings (occasionally), but it can also cause the compiler to
6926 eliminate error-checking code. Suggested by Peter Gutmann.
6929 Changes in version 0.2.0.29-rc - 2008-07-08
6930 Tor 0.2.0.29-rc fixes two big bugs with using bridges, fixes more
6931 hidden-service performance bugs, and fixes a bunch of smaller bugs.
6934 - If you have more than one bridge but don't know their keys,
6935 you would only launch a request for the descriptor of the first one
6936 on your list. (Tor considered launching requests for the others, but
6937 found that it already had a connection on the way for $0000...0000
6938 so it didn't open another.) Bugfix on 0.2.0.x.
6939 - If you have more than one bridge but don't know their keys, and the
6940 connection to one of the bridges failed, you would cancel all
6941 pending bridge connections. (After all, they all have the same
6942 digest.) Bugfix on 0.2.0.x.
6943 - When a hidden service was trying to establish an introduction point,
6944 and Tor had built circuits preemptively for such purposes, we
6945 were ignoring all the preemptive circuits and launching a new one
6946 instead. Bugfix on 0.2.0.14-alpha.
6947 - When a hidden service was trying to establish an introduction point,
6948 and Tor *did* manage to reuse one of the preemptively built
6949 circuits, it didn't correctly remember which one it used,
6950 so it asked for another one soon after, until there were no
6951 more preemptive circuits, at which point it launched one from
6952 scratch. Bugfix on 0.0.9.x.
6953 - Make directory servers include the X-Your-Address-Is: http header in
6954 their responses even for begin_dir conns. Now clients who only
6955 ever use begin_dir connections still have a way to learn their IP
6956 address. Fixes bug 737; bugfix on 0.2.0.22-rc. Reported by goldy.
6959 - Fix a macro/CPP interaction that was confusing some compilers:
6960 some GCCs don't like #if/#endif pairs inside macro arguments.
6962 - Fix macro collision between OpenSSL 0.9.8h and Windows headers.
6963 Fixes bug 704; fix from Steven Murdoch.
6964 - When opening /dev/null in finish_daemonize(), do not pass the
6965 O_CREAT flag. Fortify was complaining, and correctly so. Fixes
6966 bug 742; fix from Michael Scherer. Bugfix on 0.0.2pre19.
6967 - Correctly detect transparent proxy support on Linux hosts that
6968 require in.h to be included before netfilter_ipv4.h. Patch
6970 - Disallow session resumption attempts during the renegotiation
6971 stage of the v2 handshake protocol. Clients should never be trying
6972 session resumption at this point, but apparently some did, in
6973 ways that caused the handshake to fail. Bugfix on 0.2.0.20-rc. Bug
6974 found by Geoff Goodell.
6977 Changes in version 0.2.1.2-alpha - 2008-06-20
6978 Tor 0.2.1.2-alpha includes a new "TestingTorNetwork" config option to
6979 make it easier to set up your own private Tor network; fixes several
6980 big bugs with using more than one bridge relay; fixes a big bug with
6981 offering hidden services quickly after Tor starts; and uses a better
6982 API for reporting potential bootstrapping problems to the controller.
6985 - New TestingTorNetwork config option to allow adjustment of
6986 previously constant values that, while reasonable, could slow
6987 bootstrapping. Implements proposal 135. Patch from Karsten.
6990 - If you have more than one bridge but don't know their digests,
6991 you would only learn a request for the descriptor of the first one
6992 on your list. (Tor considered launching requests for the others, but
6993 found that it already had a connection on the way for $0000...0000
6994 so it didn't open another.) Bugfix on 0.2.0.x.
6995 - If you have more than one bridge but don't know their digests,
6996 and the connection to one of the bridges failed, you would cancel
6997 all pending bridge connections. (After all, they all have the
6998 same digest.) Bugfix on 0.2.0.x.
6999 - When establishing a hidden service, introduction points that
7000 originate from cannibalized circuits are completely ignored and not
7001 included in rendezvous service descriptors. This might be another
7002 reason for delay in making a hidden service available. Bugfix
7003 from long ago (0.0.9.x?)
7006 - Allow OpenSSL to use dynamic locks if it wants.
7007 - When building a consensus, do not include routers that are down.
7008 This will cut down 30% to 40% on consensus size. Implements
7010 - In directory authorities' approved-routers files, allow
7011 fingerprints with or without space.
7012 - Add a "GETINFO /status/bootstrap-phase" controller option, so the
7013 controller can query our current bootstrap state in case it attaches
7014 partway through and wants to catch up.
7015 - Send an initial "Starting" bootstrap status event, so we have a
7016 state to start out in.
7019 - Asking for a conditional consensus at .../consensus/<fingerprints>
7020 would crash a dirserver if it did not already have a
7021 consensus. Bugfix on 0.2.1.1-alpha.
7022 - Clean up some macro/CPP interactions: some GCC versions don't like
7023 #if/#endif pairs inside macro arguments. Fixes bug 707. Bugfix on
7026 o Bootstrapping bugfixes (on 0.2.1.1-alpha):
7027 - Directory authorities shouldn't complain about bootstrapping
7028 problems just because they do a lot of reachability testing and
7029 some of the connection attempts fail.
7030 - Start sending "count" and "recommendation" key/value pairs in
7031 bootstrap problem status events, so the controller can hear about
7032 problems even before Tor decides they're worth reporting for sure.
7033 - If you're using bridges, generate "bootstrap problem" warnings
7034 as soon as you run out of working bridges, rather than waiting
7035 for ten failures -- which will never happen if you have less than
7037 - If we close our OR connection because there's been a circuit
7038 pending on it for too long, we were telling our bootstrap status
7039 events "REASON=NONE". Now tell them "REASON=TIMEOUT".
7042 Changes in version 0.2.1.1-alpha - 2008-06-13
7043 Tor 0.2.1.1-alpha fixes a lot of memory fragmentation problems that
7044 were making the Tor process bloat especially on Linux; makes our TLS
7045 handshake blend in better; sends "bootstrap phase" status events to
7046 the controller, so it can keep the user informed of progress (and
7047 problems) fetching directory information and establishing circuits;
7048 and adds a variety of smaller features.
7051 - More work on making our TLS handshake blend in: modify the list
7052 of ciphers advertised by OpenSSL in client mode to even more
7053 closely resemble a common web browser. We cheat a little so that
7054 we can advertise ciphers that the locally installed OpenSSL doesn't
7056 - Start sending "bootstrap phase" status events to the controller,
7057 so it can keep the user informed of progress fetching directory
7058 information and establishing circuits. Also inform the controller
7059 if we think we're stuck at a particular bootstrap phase. Implements
7061 - Resume using OpenSSL's RAND_poll() for better (and more portable)
7062 cross-platform entropy collection again. We used to use it, then
7063 stopped using it because of a bug that could crash systems that
7064 called RAND_poll when they had a lot of fds open. It looks like the
7065 bug got fixed in late 2006. Our new behavior is to call RAND_poll()
7066 at startup, and to call RAND_poll() when we reseed later only if
7067 we have a non-buggy OpenSSL version.
7070 - When we choose to abandon a new entry guard because we think our
7071 older ones might be better, close any circuits pending on that
7072 new entry guard connection. This fix should make us recover much
7073 faster when our network is down and then comes back. Bugfix on
7074 0.1.2.8-beta; found by lodger.
7076 o Memory fixes and improvements:
7077 - Add a malloc_good_size implementation to OpenBSD_malloc_linux.c,
7078 to avoid unused RAM in buffer chunks and memory pools.
7079 - Speed up parsing and cut down on memory fragmentation by using
7080 stack-style allocations for parsing directory objects. Previously,
7081 this accounted for over 40% of allocations from within Tor's code
7082 on a typical directory cache.
7083 - Use a Bloom filter rather than a digest-based set to track which
7084 descriptors we need to keep around when we're cleaning out old
7085 router descriptors. This speeds up the computation significantly,
7086 and may reduce fragmentation.
7087 - Reduce the default smartlist size from 32 to 16; it turns out that
7088 most smartlists hold around 8-12 elements tops.
7089 - Make dumpstats() log the fullness and size of openssl-internal
7091 - If the user has applied the experimental SSL_MODE_RELEASE_BUFFERS
7092 patch to their OpenSSL, turn it on to save memory on servers. This
7093 patch will (with any luck) get included in a mainline distribution
7095 - Never use OpenSSL compression: it wastes RAM and CPU trying to
7096 compress cells, which are basically all encrypted, compressed,
7100 - Stop reloading the router list from disk for no reason when we
7101 run out of reachable directory mirrors. Once upon a time reloading
7102 it would set the 'is_running' flag back to 1 for them. It hasn't
7103 done that for a long time.
7104 - In very rare situations new hidden service descriptors were
7105 published earlier than 30 seconds after the last change to the
7106 service. (We currently think that a hidden service descriptor
7107 that's been stable for 30 seconds is worth publishing.)
7110 - Allow separate log levels to be configured for different logging
7111 domains. For example, this allows one to log all notices, warnings,
7112 or errors, plus all memory management messages of level debug or
7113 higher, with: Log [MM] debug-err [*] notice-err file /var/log/tor.
7114 - Add a couple of extra warnings to --enable-gcc-warnings for GCC 4.3,
7115 and stop using a warning that had become unfixably verbose under
7117 - New --hush command-line option similar to --quiet. While --quiet
7118 disables all logging to the console on startup, --hush limits the
7119 output to messages of warning and error severity.
7120 - Servers support a new URL scheme for consensus downloads that
7121 allows the client to specify which authorities are trusted.
7122 The server then only sends the consensus if the client will trust
7123 it. Otherwise a 404 error is sent back. Clients use this
7124 new scheme when the server supports it (meaning it's running
7125 0.2.1.1-alpha or later). Implements proposal 134.
7126 - New configure/torrc options (--enable-geoip-stats,
7127 DirRecordUsageByCountry) to record how many IPs we've served
7128 directory info to in each country code, how many status documents
7129 total we've sent to each country code, and what share of the total
7130 directory requests we should expect to see.
7131 - Use the TLS1 hostname extension to more closely resemble browser
7133 - Lots of new unit tests.
7134 - Add a macro to implement the common pattern of iterating through
7135 two parallel lists in lockstep.
7138 Changes in version 0.2.0.28-rc - 2008-06-13
7139 Tor 0.2.0.28-rc fixes an anonymity-related bug, fixes a hidden-service
7140 performance bug, and fixes a bunch of smaller bugs.
7143 - Fix a bug where, when we were choosing the 'end stream reason' to
7144 put in our relay end cell that we send to the exit relay, Tor
7145 clients on Windows were sometimes sending the wrong 'reason'. The
7146 anonymity problem is that exit relays may be able to guess whether
7147 the client is running Windows, thus helping partition the anonymity
7148 set. Down the road we should stop sending reasons to exit relays,
7149 or otherwise prevent future versions of this bug.
7152 - While setting up a hidden service, some valid introduction circuits
7153 were overlooked and abandoned. This might be the reason for
7154 the long delay in making a hidden service available. Bugfix on
7158 - Update to the "June 9 2008" ip-to-country file.
7159 - Run 'make test' as part of 'make dist', so we stop releasing so
7160 many development snapshots that fail their unit tests.
7163 - When we're checking if we have enough dir info for each relay
7164 to begin establishing circuits, make sure that we actually have
7165 the descriptor listed in the consensus, not just any descriptor.
7167 - Bridge relays no longer print "xx=0" in their extrainfo document
7168 for every single country code in the geoip db. Bugfix on
7170 - Only warn when we fail to load the geoip file if we were planning to
7171 include geoip stats in our extrainfo document. Bugfix on 0.2.0.27-rc.
7172 - If we change our MaxAdvertisedBandwidth and then reload torrc,
7173 Tor won't realize it should publish a new relay descriptor. Fixes
7174 bug 688, reported by mfr. Bugfix on 0.1.2.x.
7175 - When we haven't had any application requests lately, don't bother
7176 logging that we have expired a bunch of descriptors. Bugfix
7178 - Make relay cells written on a connection count as non-padding when
7179 tracking how long a connection has been in use. Bugfix on
7180 0.2.0.1-alpha. Spotted by lodger.
7181 - Fix unit tests in 0.2.0.27-rc.
7182 - Fix compile on Windows.
7185 Changes in version 0.2.0.27-rc - 2008-06-03
7186 Tor 0.2.0.27-rc adds a few features we left out of the earlier
7187 release candidates. In particular, we now include an IP-to-country
7188 GeoIP database, so controllers can easily look up what country a
7189 given relay is in, and so bridge relays can give us some sanitized
7190 summaries about which countries are making use of bridges. (See proposal
7191 126-geoip-fetching.txt for details.)
7194 - Include an IP-to-country GeoIP file in the tarball, so bridge
7195 relays can report sanitized summaries of the usage they're seeing.
7198 - Add a "PURPOSE=" argument to "STREAM NEW" events, as suggested by
7199 Robert Hogan. Fixes the first part of bug 681.
7200 - Make bridge authorities never serve extrainfo docs.
7201 - Add support to detect Libevent versions in the 1.4.x series
7203 - Fix build on gcc 4.3 with --enable-gcc-warnings set.
7204 - Include a new contrib/tor-exit-notice.html file that exit relay
7205 operators can put on their website to help reduce abuse queries.
7208 - When tunneling an encrypted directory connection, and its first
7209 circuit fails, do not leave it unattached and ask the controller
7210 to deal. Fixes the second part of bug 681.
7211 - Make bridge authorities correctly expire old extrainfo documents
7215 Changes in version 0.2.0.26-rc - 2008-05-13
7216 Tor 0.2.0.26-rc fixes a major security vulnerability caused by a bug
7217 in Debian's OpenSSL packages. All users running any 0.2.0.x version
7218 should upgrade, whether they're running Debian or not.
7220 o Major security fixes:
7221 - Use new V3 directory authority keys on the tor26, gabelmoo, and
7222 moria1 V3 directory authorities. The old keys were generated with
7223 a vulnerable version of Debian's OpenSSL package, and must be
7224 considered compromised. Other authorities' keys were not generated
7225 with an affected version of OpenSSL.
7228 - List authority signatures as "unrecognized" based on DirServer
7229 lines, not on cert cache. Bugfix on 0.2.0.x.
7232 - Add a new V3AuthUseLegacyKey option to make it easier for
7233 authorities to change their identity keys if they have to.
7236 Changes in version 0.2.0.25-rc - 2008-04-23
7237 Tor 0.2.0.25-rc makes Tor work again on OS X and certain BSDs.
7240 - Remember to initialize threading before initializing logging.
7241 Otherwise, many BSD-family implementations will crash hard on
7242 startup. Fixes bug 671. Bugfix on 0.2.0.24-rc.
7245 - Authorities correctly free policies on bad servers on
7246 exit. Fixes bug 672. Bugfix on 0.2.0.x.
7249 Changes in version 0.2.0.24-rc - 2008-04-22
7250 Tor 0.2.0.24-rc adds dizum (run by Alex de Joode) as the new sixth
7251 v3 directory authority, makes relays with dynamic IP addresses and no
7252 DirPort notice more quickly when their IP address changes, fixes a few
7253 rare crashes and memory leaks, and fixes a few other miscellaneous bugs.
7255 o New directory authorities:
7256 - Take lefkada out of the list of v3 directory authorities, since
7257 it has been down for months.
7258 - Set up dizum (run by Alex de Joode) as the new sixth v3 directory
7262 - Detect address changes more quickly on non-directory mirror
7263 relays. Bugfix on 0.2.0.18-alpha; fixes bug 652.
7265 o Minor features (security):
7266 - Reject requests for reverse-dns lookup of names that are in
7267 a private address space. Patch from lodger.
7268 - Non-exit relays no longer allow DNS requests. Fixes bug 619. Patch
7271 o Minor bugfixes (crashes):
7272 - Avoid a rare assert that can trigger when Tor doesn't have much
7273 directory information yet and it tries to fetch a v2 hidden
7274 service descriptor. Fixes bug 651, reported by nwf.
7275 - Initialize log mutex before initializing dmalloc. Otherwise,
7276 running with dmalloc would crash. Bugfix on 0.2.0.x-alpha.
7277 - Use recursive pthread mutexes in order to avoid deadlock when
7278 logging debug-level messages to a controller. Bug spotted by nwf,
7279 bugfix on 0.2.0.16-alpha.
7281 o Minor bugfixes (resource management):
7282 - Keep address policies from leaking memory: start their refcount
7283 at 1, not 2. Bugfix on 0.2.0.16-alpha.
7284 - Free authority certificates on exit, so they don't look like memory
7285 leaks. Bugfix on 0.2.0.19-alpha.
7286 - Free static hashtables for policy maps and for TLS connections on
7287 shutdown, so they don't look like memory leaks. Bugfix on 0.2.0.x.
7288 - Avoid allocating extra space when computing consensuses on 64-bit
7289 platforms. Bug spotted by aakova.
7291 o Minor bugfixes (misc):
7292 - Do not read the configuration file when we've only been told to
7293 generate a password hash. Fixes bug 643. Bugfix on 0.0.9pre5. Fix
7294 based on patch from Sebastian Hahn.
7295 - Exit relays that are used as a client can now reach themselves
7296 using the .exit notation, rather than just launching an infinite
7297 pile of circuits. Fixes bug 641. Reported by Sebastian Hahn.
7298 - When attempting to open a logfile fails, tell us why.
7299 - Fix a dumb bug that was preventing us from knowing that we should
7300 preemptively build circuits to handle expected directory requests.
7301 Fixes bug 660. Bugfix on 0.1.2.x.
7302 - Warn less verbosely about clock skew from netinfo cells from
7303 untrusted sources. Fixes bug 663.
7304 - Make controller stream events for DNS requests more consistent,
7305 by adding "new stream" events for DNS requests, and removing
7306 spurious "stream closed" events" for cached reverse resolves.
7307 Patch from mwenge. Fixes bug 646.
7308 - Correctly notify one-hop connections when a circuit build has
7309 failed. Possible fix for bug 669. Found by lodger.
7312 Changes in version 0.2.0.23-rc - 2008-03-24
7313 Tor 0.2.0.23-rc is the fourth release candidate for the 0.2.0 series. It
7314 makes bootstrapping faster if the first directory mirror you contact
7315 is down. The bundles also include the new Vidalia 0.1.2 release.
7318 - When a tunneled directory request is made to a directory server
7319 that's down, notice after 30 seconds rather than 120 seconds. Also,
7320 fail any begindir streams that are pending on it, so they can
7321 retry elsewhere. This was causing multi-minute delays on bootstrap.
7324 Changes in version 0.2.0.22-rc - 2008-03-18
7325 Tor 0.2.0.22-rc is the third release candidate for the 0.2.0 series. It
7326 enables encrypted directory connections by default for non-relays, fixes
7327 some broken TLS behavior we added in 0.2.0.20-rc, and resolves many
7328 other bugs. The bundles also include Vidalia 0.1.1 and Torbutton 1.1.17.
7331 - Enable encrypted directory connections by default for non-relays,
7332 so censor tools that block Tor directory connections based on their
7333 plaintext patterns will no longer work. This means Tor works in
7334 certain censored countries by default again.
7337 - Make sure servers always request certificates from clients during
7338 TLS renegotiation. Reported by lodger; bugfix on 0.2.0.20-rc.
7339 - Do not enter a CPU-eating loop when a connection is closed in
7340 the middle of client-side TLS renegotiation. Fixes bug 622. Bug
7341 diagnosed by lodger; bugfix on 0.2.0.20-rc.
7342 - Fix assertion failure that could occur when a blocked circuit
7343 became unblocked, and it had pending client DNS requests. Bugfix
7344 on 0.2.0.1-alpha. Fixes bug 632.
7346 o Minor bugfixes (on 0.1.2.x):
7347 - Generate "STATUS_SERVER" events rather than misspelled
7348 "STATUS_SEVER" events. Caught by mwenge.
7349 - When counting the number of bytes written on a TLS connection,
7350 look at the BIO actually used for writing to the network, not
7351 at the BIO used (sometimes) to buffer data for the network.
7352 Looking at different BIOs could result in write counts on the
7353 order of ULONG_MAX. Fixes bug 614.
7354 - On Windows, correctly detect errors when listing the contents of
7355 a directory. Fix from lodger.
7357 o Minor bugfixes (on 0.2.0.x):
7358 - Downgrade "sslv3 alert handshake failure" message to INFO.
7359 - If we set RelayBandwidthRate and RelayBandwidthBurst very high but
7360 left BandwidthRate and BandwidthBurst at the default, we would be
7361 silently limited by those defaults. Now raise them to match the
7362 RelayBandwidth* values.
7363 - Fix the SVK version detection logic to work correctly on a branch.
7364 - Make --enable-openbsd-malloc work correctly on Linux with alpha
7365 CPUs. Fixes bug 625.
7366 - Logging functions now check that the passed severity is sane.
7367 - Use proper log levels in the testsuite call of
7368 get_interface_address6().
7369 - When using a nonstandard malloc, do not use the platform values for
7370 HAVE_MALLOC_GOOD_SIZE or HAVE_MALLOC_USABLE_SIZE.
7371 - Make the openbsd malloc code use 8k pages on alpha CPUs and
7373 - Detect mismatched page sizes when using --enable-openbsd-malloc.
7374 - Avoid double-marked-for-close warning when certain kinds of invalid
7375 .in-addr.arpa addresses are passed to the DNSPort. Part of a fix
7376 for bug 617. Bugfix on 0.2.0.1-alpha.
7377 - Make sure that the "NULL-means-reject *:*" convention is followed by
7378 all the policy manipulation functions, avoiding some possible crash
7379 bugs. Bug found by lodger. Bugfix on 0.2.0.16-alpha.
7380 - Fix the implementation of ClientDNSRejectInternalAddresses so that it
7381 actually works, and doesn't warn about every single reverse lookup.
7382 Fixes the other part of bug 617. Bugfix on 0.2.0.1-alpha.
7385 - Only log guard node status when guard node status has changed.
7386 - Downgrade the 3 most common "INFO" messages to "DEBUG". This will
7387 make "INFO" 75% less verbose.
7390 Changes in version 0.2.0.21-rc - 2008-03-02
7391 Tor 0.2.0.21-rc is the second release candidate for the 0.2.0 series. It
7392 makes Tor work well with Vidalia again, fixes a rare assert bug,
7393 and fixes a pair of more minor bugs. The bundles also include Vidalia
7394 0.1.0 and Torbutton 1.1.16.
7397 - The control port should declare that it requires password auth
7398 when HashedControlSessionPassword is set too. Patch from Matt Edman;
7399 bugfix on 0.2.0.20-rc. Fixes bug 615.
7400 - Downgrade assert in connection_buckets_decrement() to a log message.
7401 This may help us solve bug 614, and in any case will make its
7402 symptoms less severe. Bugfix on 0.2.0.20-rc. Reported by fredzupy.
7403 - We were sometimes miscounting the number of bytes read from the
7404 network, causing our rate limiting to not be followed exactly.
7405 Bugfix on 0.2.0.16-alpha. Reported by lodger.
7408 - Fix compilation with OpenSSL 0.9.8 and 0.9.8a. All other supported
7409 OpenSSL versions should have been working fine. Diagnosis and patch
7410 from lodger, Karsten Loesing, and Sebastian Hahn. Fixes bug 616.
7411 Bugfix on 0.2.0.20-rc.
7414 Changes in version 0.2.0.20-rc - 2008-02-24
7415 Tor 0.2.0.20-rc is the first release candidate for the 0.2.0 series. It
7416 makes more progress towards normalizing Tor's TLS handshake, makes
7417 hidden services work better again, helps relays bootstrap if they don't
7418 know their IP address, adds optional support for linking in openbsd's
7419 allocator or tcmalloc, allows really fast relays to scale past 15000
7420 sockets, and fixes a bunch of minor bugs reported by Veracode.
7423 - Enable the revised TLS handshake based on the one designed by
7424 Steven Murdoch in proposal 124, as revised in proposal 130. It
7425 includes version negotiation for OR connections as described in
7426 proposal 105. The new handshake is meant to be harder for censors
7427 to fingerprint, and it adds the ability to detect certain kinds of
7428 man-in-the-middle traffic analysis attacks. The version negotiation
7429 feature will allow us to improve Tor's link protocol more safely
7431 - Choose which bridge to use proportional to its advertised bandwidth,
7432 rather than uniformly at random. This should speed up Tor for
7433 bridge users. Also do this for people who set StrictEntryNodes.
7434 - When a TrackHostExits-chosen exit fails too many times in a row,
7435 stop using it. Bugfix on 0.1.2.x; fixes bug 437.
7438 - Resolved problems with (re-)fetching hidden service descriptors.
7439 Patch from Karsten Loesing; fixes problems with 0.2.0.18-alpha
7441 - If we only ever used Tor for hidden service lookups or posts, we
7442 would stop building circuits and start refusing connections after
7443 24 hours, since we falsely believed that Tor was dormant. Reported
7444 by nwf; bugfix on 0.1.2.x.
7445 - Servers that don't know their own IP address should go to the
7446 authorities for their first directory fetch, even if their DirPort
7447 is off or if they don't know they're reachable yet. This will help
7448 them bootstrap better. Bugfix on 0.2.0.18-alpha; fixes bug 609.
7449 - When counting the number of open sockets, count not only the number
7450 of sockets we have received from the socket() call, but also
7451 the number we've gotten from accept() and socketpair(). This bug
7452 made us fail to count all sockets that we were using for incoming
7453 connections. Bugfix on 0.2.0.x.
7454 - Fix code used to find strings within buffers, when those strings
7455 are not in the first chunk of the buffer. Bugfix on 0.2.0.x.
7456 - Fix potential segfault when parsing HTTP headers. Bugfix on 0.2.0.x.
7457 - Add a new __HashedControlSessionPassword option for controllers
7458 to use for one-off session password hashes that shouldn't get
7459 saved to disk by SAVECONF --- Vidalia users were accumulating a
7460 pile of HashedControlPassword lines in their torrc files, one for
7461 each time they had restarted Tor and then clicked Save. Make Tor
7462 automatically convert "HashedControlPassword" to this new option but
7463 only when it's given on the command line. Partial fix for bug 586.
7465 o Minor features (performance):
7466 - Tune parameters for cell pool allocation to minimize amount of
7468 - Add OpenBSD malloc code from phk as an optional malloc
7469 replacement on Linux: some glibc libraries do very poorly
7470 with Tor's memory allocation patterns. Pass
7471 --enable-openbsd-malloc to get the replacement malloc code.
7472 - Add a --with-tcmalloc option to the configure script to link
7473 against tcmalloc (if present). Does not yet search for
7474 non-system include paths.
7475 - Stop imposing an arbitrary maximum on the number of file descriptors
7476 used for busy servers. Bug reported by Olaf Selke; patch from
7479 o Minor features (other):
7480 - When SafeLogging is disabled, log addresses along with all TLS
7482 - When building with --enable-gcc-warnings, check for whether Apple's
7483 warning "-Wshorten-64-to-32" is available.
7484 - Add a --passphrase-fd argument to the tor-gencert command for
7487 o Minor bugfixes (memory leaks and code problems):
7488 - We were leaking a file descriptor if Tor started with a zero-length
7489 cached-descriptors file. Patch by freddy77; bugfix on 0.1.2.
7490 - Detect size overflow in zlib code. Reported by Justin Ferguson and
7492 - We were comparing the raw BridgePassword entry with a base64'ed
7493 version of it, when handling a "/tor/networkstatus-bridges"
7494 directory request. Now compare correctly. Noticed by Veracode.
7495 - Recover from bad tracked-since value in MTBF-history file.
7497 - Alter the code that tries to recover from unhandled write
7498 errors, to not try to flush onto a socket that's given us
7499 unhandled errors. Bugfix on 0.1.2.x.
7500 - Make Unix controlsockets work correctly on OpenBSD. Patch from
7501 tup. Bugfix on 0.2.0.3-alpha.
7503 o Minor bugfixes (other):
7504 - If we have an extra-info document for our server, always make
7505 it available on the control port, even if we haven't gotten
7506 a copy of it from an authority yet. Patch from mwenge.
7507 - Log the correct memory chunk sizes for empty RAM chunks in mempool.c.
7508 - Directory mirrors no longer include a guess at the client's IP
7509 address if the connection appears to be coming from the same /24
7510 network; it was producing too many wrong guesses.
7511 - Make the new hidden service code respect the SafeLogging setting.
7512 Bugfix on 0.2.0.x. Patch from Karsten.
7513 - When starting as an authority, do not overwrite all certificates
7514 cached from other authorities. Bugfix on 0.2.0.x. Fixes bug 606.
7515 - If we're trying to flush the last bytes on a connection (for
7516 example, when answering a directory request), reset the
7517 time-to-give-up timeout every time we manage to write something
7518 on the socket. Bugfix on 0.1.2.x.
7519 - Change the behavior of "getinfo status/good-server-descriptor"
7520 so it doesn't return failure when any authority disappears.
7521 - Even though the man page said that "TrackHostExits ." should
7522 work, nobody had ever implemented it. Bugfix on 0.1.0.x.
7523 - Report TLS "zero return" case as a "clean close" and "IO error"
7524 as a "close". Stop calling closes "unexpected closes": existing
7525 Tors don't use SSL_close(), so having a connection close without
7526 the TLS shutdown handshake is hardly unexpected.
7527 - Send NAMESERVER_STATUS messages for a single failed nameserver
7530 o Code simplifications and refactoring:
7531 - Remove the tor_strpartition function: its logic was confused,
7532 and it was only used for one thing that could be implemented far
7536 Changes in version 0.2.0.19-alpha - 2008-02-09
7537 Tor 0.2.0.19-alpha makes more progress towards normalizing Tor's TLS
7538 handshake, makes path selection for relays more secure and IP address
7539 guessing more robust, and generally fixes a lot of bugs in preparation
7540 for calling the 0.2.0 branch stable.
7543 - Do not include recognizeable strings in the commonname part of
7544 Tor's x509 certificates.
7547 - If we're a relay, avoid picking ourselves as an introduction point,
7548 a rendezvous point, or as the final hop for internal circuits. Bug
7549 reported by taranis and lodger. Bugfix on 0.1.2.x.
7550 - Patch from "Andrew S. Lists" to catch when we contact a directory
7551 mirror at IP address X and he says we look like we're coming from
7552 IP address X. Bugfix on 0.1.2.x.
7554 o Minor features (security):
7555 - Be more paranoid about overwriting sensitive memory on free(),
7556 as a defensive programming tactic to ensure forward secrecy.
7558 o Minor features (directory authority):
7559 - Actually validate the options passed to AuthDirReject,
7560 AuthDirInvalid, AuthDirBadDir, and AuthDirBadExit.
7561 - Reject router descriptors with out-of-range bandwidthcapacity or
7562 bandwidthburst values.
7564 o Minor features (controller):
7565 - Reject controller commands over 1MB in length. This keeps rogue
7566 processes from running us out of memory.
7568 o Minor features (misc):
7569 - Give more descriptive well-formedness errors for out-of-range
7570 hidden service descriptor/protocol versions.
7571 - Make memory debugging information describe more about history
7572 of cell allocation, so we can help reduce our memory use.
7574 o Deprecated features (controller):
7575 - The status/version/num-versioning and status/version/num-concurring
7576 GETINFO options are no longer useful in the v3 directory protocol:
7577 treat them as deprecated, and warn when they're used.
7580 - When our consensus networkstatus has been expired for a while, stop
7581 being willing to build circuits using it. Fixes bug 401. Bugfix
7583 - Directory caches now fetch certificates from all authorities
7584 listed in a networkstatus consensus, even when they do not
7585 recognize them. Fixes bug 571. Bugfix on 0.2.0.x.
7586 - When connecting to a bridge without specifying its key, insert
7587 the connection into the identity-to-connection map as soon as
7588 a key is learned. Fixes bug 574. Bugfix on 0.2.0.x.
7589 - Detect versions of OS X where malloc_good_size() is present in the
7590 library but never actually declared. Resolves bug 587. Bugfix
7592 - Stop incorrectly truncating zlib responses to directory authority
7593 signature download requests. Fixes bug 593. Bugfix on 0.2.0.x.
7594 - Stop recommending that every server operator send mail to tor-ops.
7595 Resolves bug 597. Bugfix on 0.1.2.x.
7596 - Don't trigger an assert if we start a directory authority with a
7597 private IP address (like 127.0.0.1).
7598 - Avoid possible failures when generating a directory with routers
7599 with over-long versions strings, or too many flags set. Bugfix
7601 - If an attempt to launch a DNS resolve request over the control
7602 port fails because we have overrun the limit on the number of
7603 connections, tell the controller that the request has failed.
7604 - Avoid using too little bandwidth when our clock skips a few
7605 seconds. Bugfix on 0.1.2.x.
7606 - Fix shell error when warning about missing packages in configure
7607 script, on Fedora or Red Hat machines. Bugfix on 0.2.0.x.
7608 - Do not become confused when receiving a spurious VERSIONS-like
7609 cell from a confused v1 client. Bugfix on 0.2.0.x.
7610 - Re-fetch v2 (as well as v0) rendezvous descriptors when all
7611 introduction points for a hidden service have failed. Patch from
7612 Karsten Loesing. Bugfix on 0.2.0.x.
7614 o Code simplifications and refactoring:
7615 - Remove some needless generality from cpuworker code, for improved
7617 - Stop overloading the circuit_t.onionskin field for both "onionskin
7618 from a CREATE cell that we are waiting for a cpuworker to be
7619 assigned" and "onionskin from an EXTEND cell that we are going to
7620 send to an OR as soon as we are connected". Might help with bug 600.
7621 - Add an in-place version of aes_crypt() so that we can avoid doing a
7622 needless memcpy() call on each cell payload.
7625 Changes in version 0.2.0.18-alpha - 2008-01-25
7626 Tor 0.2.0.18-alpha adds a sixth v3 directory authority run by CCC,
7627 fixes a big memory leak in 0.2.0.17-alpha, and adds new config options
7628 that can warn or reject connections to ports generally associated with
7629 vulnerable-plaintext protocols.
7631 o New directory authorities:
7632 - Set up dannenberg (run by CCC) as the sixth v3 directory
7636 - Fix a major memory leak when attempting to use the v2 TLS
7637 handshake code. Bugfix on 0.2.0.x; fixes bug 589.
7638 - We accidentally enabled the under-development v2 TLS handshake
7639 code, which was causing log entries like "TLS error while
7640 renegotiating handshake". Disable it again. Resolves bug 590.
7641 - We were computing the wrong Content-Length: header for directory
7642 responses that need to be compressed on the fly, causing clients
7643 asking for those items to always fail. Bugfix on 0.2.0.x; partially
7647 - Avoid going directly to the directory authorities even if you're a
7648 relay, if you haven't found yourself reachable yet or if you've
7649 decided not to advertise your dirport yet. Addresses bug 556.
7650 - If we've gone 12 hours since our last bandwidth check, and we
7651 estimate we have less than 50KB bandwidth capacity but we could
7652 handle more, do another bandwidth test.
7653 - New config options WarnPlaintextPorts and RejectPlaintextPorts so
7654 Tor can warn and/or refuse connections to ports commonly used with
7655 vulnerable-plaintext protocols. Currently we warn on ports 23,
7656 109, 110, and 143, but we don't reject any.
7659 - When we setconf ClientOnly to 1, close any current OR and Dir
7660 listeners. Reported by mwenge.
7661 - When we get a consensus that's been signed by more people than
7662 we expect, don't log about it; it's not a big deal. Reported
7666 - Don't answer "/tor/networkstatus-bridges" directory requests if
7667 the request isn't encrypted.
7668 - Make "ClientOnly 1" config option disable directory ports too.
7669 - Patches from Karsten Loesing to make v2 hidden services more
7670 robust: work even when there aren't enough HSDir relays available;
7671 retry when a v2 rend desc fetch fails; but don't retry if we
7672 already have a usable v0 rend desc.
7675 Changes in version 0.2.0.17-alpha - 2008-01-17
7676 Tor 0.2.0.17-alpha makes the tarball build cleanly again (whoops).
7679 - Make the tor-gencert man page get included correctly in the tarball.
7682 Changes in version 0.2.0.16-alpha - 2008-01-17
7683 Tor 0.2.0.16-alpha adds a fifth v3 directory authority run by Karsten
7684 Loesing, and generally cleans up a lot of features and minor bugs.
7686 o New directory authorities:
7687 - Set up gabelmoo (run by Karsten Loesing) as the fifth v3 directory
7690 o Major performance improvements:
7691 - Switch our old ring buffer implementation for one more like that
7692 used by free Unix kernels. The wasted space in a buffer with 1mb
7693 of data will now be more like 8k than 1mb. The new implementation
7694 also avoids realloc();realloc(); patterns that can contribute to
7695 memory fragmentation.
7698 - Configuration files now accept C-style strings as values. This
7699 helps encode characters not allowed in the current configuration
7700 file format, such as newline or #. Addresses bug 557.
7701 - Although we fixed bug 539 (where servers would send HTTP status 503
7702 responses _and_ send a body too), there are still servers out
7703 there that haven't upgraded. Therefore, make clients parse such
7704 bodies when they receive them.
7705 - When we're not serving v2 directory information, there is no reason
7706 to actually keep any around. Remove the obsolete files and directory
7707 on startup if they are very old and we aren't going to serve them.
7709 o Minor performance improvements:
7710 - Reference-count and share copies of address policy entries; only 5%
7711 of them were actually distinct.
7712 - Never walk through the list of logs if we know that no log is
7713 interested in a given message.
7716 - When an authority has not signed a consensus, do not try to
7717 download a nonexistent "certificate with key 00000000". Bugfix
7718 on 0.2.0.x. Fixes bug 569.
7719 - Fix a rare assert error when we're closing one of our threads:
7720 use a mutex to protect the list of logs, so we never write to the
7721 list as it's being freed. Bugfix on 0.1.2.x. Fixes the very rare
7722 bug 575, which is kind of the revenge of bug 222.
7723 - Patch from Karsten Loesing to complain less at both the client
7724 and the relay when a relay used to have the HSDir flag but doesn't
7725 anymore, and we try to upload a hidden service descriptor.
7726 - Stop leaking one cert per TLS context. Fixes bug 582. Bugfix on
7728 - Do not try to download missing certificates until we have tried
7729 to check our fallback consensus. Fixes bug 583.
7730 - Make bridges round reported GeoIP stats info up to the nearest
7731 estimate, not down. Now we can distinguish between "0 people from
7732 this country" and "1 person from this country".
7733 - Avoid a spurious free on base64 failure. Bugfix on 0.1.2.
7734 - Avoid possible segfault if key generation fails in
7735 crypto_pk_hybrid_encrypt. Bugfix on 0.2.0.
7736 - Avoid segfault in the case where a badly behaved v2 versioning
7737 directory sends a signed networkstatus with missing client-versions.
7739 - Avoid segfaults on certain complex invocations of
7740 router_get_by_hexdigest(). Bugfix on 0.1.2.
7741 - Correct bad index on array access in parse_http_time(). Bugfix
7743 - Fix possible bug in vote generation when server versions are present
7744 but client versions are not.
7745 - Fix rare bug on REDIRECTSTREAM control command when called with no
7746 port set: it could erroneously report an error when none had
7748 - Avoid bogus crash-prone, leak-prone tor_realloc when we're
7749 compressing large objects and find ourselves with more than 4k
7750 left over. Bugfix on 0.2.0.
7751 - Fix a small memory leak when setting up a hidden service.
7752 - Fix a few memory leaks that could in theory happen under bizarre
7754 - Fix an assert if we post a general-purpose descriptor via the
7755 control port but that descriptor isn't mentioned in our current
7756 network consensus. Bug reported by Jon McLachlan; bugfix on
7759 o Minor features (controller):
7760 - Get NS events working again. Patch from tup.
7761 - The GETCONF command now escapes and quotes configuration values
7762 that don't otherwise fit into the torrc file.
7763 - The SETCONF command now handles quoted values correctly.
7765 o Minor features (directory authorities):
7766 - New configuration options to override default maximum number of
7767 servers allowed on a single IP address. This is important for
7768 running a test network on a single host.
7769 - Actually implement the -s option to tor-gencert.
7770 - Add a manual page for tor-gencert.
7772 o Minor features (bridges):
7773 - Bridge authorities no longer serve bridge descriptors over
7774 unencrypted connections.
7776 o Minor features (other):
7777 - Add hidden services and DNSPorts to the list of things that make
7778 Tor accept that it has running ports. Change starting Tor with no
7779 ports from a fatal error to a warning; we might change it back if
7780 this turns out to confuse anybody. Fixes bug 579.
7783 Changes in version 0.1.2.19 - 2008-01-17
7784 Tor 0.1.2.19 fixes a huge memory leak on exit relays, makes the default
7785 exit policy a little bit more conservative so it's safer to run an
7786 exit relay on a home system, and fixes a variety of smaller issues.
7789 - Exit policies now reject connections that are addressed to a
7790 relay's public (external) IP address too, unless
7791 ExitPolicyRejectPrivate is turned off. We do this because too
7792 many relays are running nearby to services that trust them based
7796 - When the clock jumps forward a lot, do not allow the bandwidth
7797 buckets to become negative. Fixes bug 544.
7798 - Fix a memory leak on exit relays; we were leaking a cached_resolve_t
7799 on every successful resolve. Reported by Mike Perry.
7800 - Purge old entries from the "rephist" database and the hidden
7801 service descriptor database even when DirPort is zero.
7802 - Stop thinking that 0.1.2.x directory servers can handle "begin_dir"
7803 requests. Should ease bugs 406 and 419 where 0.1.2.x relays are
7804 crashing or mis-answering these requests.
7805 - When we decide to send a 503 response to a request for servers, do
7806 not then also send the server descriptors: this defeats the whole
7807 purpose. Fixes bug 539.
7810 - Changing the ExitPolicyRejectPrivate setting should cause us to
7811 rebuild our server descriptor.
7812 - Fix handling of hex nicknames when answering controller requests for
7813 networkstatus by name, or when deciding whether to warn about
7814 unknown routers in a config option. (Patch from mwenge.)
7815 - Fix a couple of hard-to-trigger autoconf problems that could result
7816 in really weird results on platforms whose sys/types.h files define
7817 nonstandard integer types.
7818 - Don't try to create the datadir when running --verify-config or
7819 --hash-password. Resolves bug 540.
7820 - If we were having problems getting a particular descriptor from the
7821 directory caches, and then we learned about a new descriptor for
7822 that router, we weren't resetting our failure count. Reported
7824 - Although we fixed bug 539 (where servers would send HTTP status 503
7825 responses _and_ send a body too), there are still servers out there
7826 that haven't upgraded. Therefore, make clients parse such bodies
7827 when they receive them.
7828 - Run correctly on systems where rlim_t is larger than unsigned long.
7829 This includes some 64-bit systems.
7830 - Run correctly on platforms (like some versions of OS X 10.5) where
7831 the real limit for number of open files is OPEN_FILES, not rlim_max
7832 from getrlimit(RLIMIT_NOFILES).
7833 - Avoid a spurious free on base64 failure.
7834 - Avoid segfaults on certain complex invocations of
7835 router_get_by_hexdigest().
7836 - Fix rare bug on REDIRECTSTREAM control command when called with no
7837 port set: it could erroneously report an error when none had
7841 Changes in version 0.2.0.15-alpha - 2007-12-25
7842 Tor 0.2.0.14-alpha and 0.2.0.15-alpha fix a bunch of bugs with the
7843 features added in 0.2.0.13-alpha.
7846 - Fix several remotely triggerable asserts based on DirPort requests
7847 for a v2 or v3 networkstatus object before we were prepared. This
7848 was particularly bad for 0.2.0.13 and later bridge relays, who
7849 would never have a v2 networkstatus and would thus always crash
7850 when used. Bugfixes on 0.2.0.x.
7851 - Estimate the v3 networkstatus size more accurately, rather than
7852 estimating it at zero bytes and giving it artificially high priority
7853 compared to other directory requests. Bugfix on 0.2.0.x.
7856 - Fix configure.in logic for cross-compilation.
7857 - When we load a bridge descriptor from the cache, and it was
7858 previously unreachable, mark it as retriable so we won't just
7859 ignore it. Also, try fetching a new copy immediately. Bugfixes
7861 - The bridge GeoIP stats were counting other relays, for example
7862 self-reachability and authority-reachability tests.
7865 - Support compilation to target iPhone; patch from cjacker huang.
7866 To build for iPhone, pass the --enable-iphone option to configure.
7869 Changes in version 0.2.0.14-alpha - 2007-12-23
7871 - Fix a crash on startup if you install Tor 0.2.0.13-alpha fresh
7872 without a datadirectory from a previous Tor install. Reported
7874 - Fix a crash when we fetch a descriptor that turns out to be
7875 unexpected (it used to be in our networkstatus when we started
7876 fetching it, but it isn't in our current networkstatus), and we
7877 aren't using bridges. Bugfix on 0.2.0.x.
7878 - Fix a crash when accessing hidden services: it would work the first
7879 time you use a given introduction point for your service, but
7880 on subsequent requests we'd be using garbage memory. Fixed by
7881 Karsten Loesing. Bugfix on 0.2.0.13-alpha.
7882 - Fix a crash when we load a bridge descriptor from disk but we don't
7883 currently have a Bridge line for it in our torrc. Bugfix on
7887 - If bridge authorities set BridgePassword, they will serve a
7888 snapshot of known bridge routerstatuses from their DirPort to
7889 anybody who knows that password. Unset by default.
7892 - Make the unit tests build again.
7893 - Make "GETINFO/desc-annotations/id/<OR digest>" actually work.
7894 - Make PublishServerDescriptor default to 1, so the default doesn't
7895 have to change as we invent new directory protocol versions.
7896 - Fix test for rlim_t on OSX 10.3: sys/resource.h doesn't want to
7897 be included unless sys/time.h is already included. Fixes
7898 bug 553. Bugfix on 0.2.0.x.
7899 - If we receive a general-purpose descriptor and then receive an
7900 identical bridge-purpose descriptor soon after, don't discard
7901 the next one as a duplicate.
7904 - If BridgeRelay is set to 1, then the default for
7905 PublishServerDescriptor is now "bridge" rather than "v2,v3".
7906 - If the user sets RelayBandwidthRate but doesn't set
7907 RelayBandwidthBurst, then make them equal rather than erroring out.
7910 Changes in version 0.2.0.13-alpha - 2007-12-21
7911 Tor 0.2.0.13-alpha adds a fourth v3 directory authority run by Geoff
7912 Goodell, fixes many more bugs, and adds a lot of infrastructure for
7915 o New directory authorities:
7916 - Set up lefkada (run by Geoff Goodell) as the fourth v3 directory
7920 - Only update guard status (usable / not usable) once we have
7921 enough directory information. This was causing us to always pick
7922 two new guards on startup (bugfix on 0.2.0.9-alpha), and it was
7923 causing us to discard all our guards on startup if we hadn't been
7924 running for a few weeks (bugfix on 0.1.2.x). Fixes bug 448.
7925 - Purge old entries from the "rephist" database and the hidden
7926 service descriptor databases even when DirPort is zero. Bugfix
7928 - We were ignoring our RelayBandwidthRate for the first 30 seconds
7929 after opening a circuit -- even a relayed circuit. Bugfix on
7931 - Stop thinking that 0.1.2.x directory servers can handle "begin_dir"
7932 requests. Should ease bugs 406 and 419 where 0.1.2.x relays are
7933 crashing or mis-answering these types of requests.
7934 - Relays were publishing their server descriptor to v1 and v2
7935 directory authorities, but they didn't try publishing to v3-only
7936 authorities. Fix this; and also stop publishing to v1 authorities.
7938 - When we were reading router descriptors from cache, we were ignoring
7939 the annotations -- so for example we were reading in bridge-purpose
7940 descriptors as general-purpose descriptors. Bugfix on 0.2.0.8-alpha.
7941 - When we decided to send a 503 response to a request for servers, we
7942 were then also sending the server descriptors: this defeats the
7943 whole purpose. Fixes bug 539; bugfix on 0.1.2.x.
7946 - Bridge relays now behave like clients with respect to time
7947 intervals for downloading new consensus documents -- otherwise they
7948 stand out. Bridge users now wait until the end of the interval,
7949 so their bridge relay will be sure to have a new consensus document.
7950 - Three new config options (AlternateDirAuthority,
7951 AlternateBridgeAuthority, and AlternateHSAuthority) that let the
7952 user selectively replace the default directory authorities by type,
7953 rather than the all-or-nothing replacement that DirServer offers.
7954 - Tor can now be configured to read a GeoIP file from disk in one
7955 of two formats. This can be used by controllers to map IP addresses
7956 to countries. Eventually, it may support exit-by-country.
7957 - When possible, bridge relays remember which countries users
7958 are coming from, and report aggregate information in their
7959 extra-info documents, so that the bridge authorities can learn
7960 where Tor is blocked.
7961 - Bridge directory authorities now do reachability testing on the
7962 bridges they know. They provide router status summaries to the
7963 controller via "getinfo ns/purpose/bridge", and also dump summaries
7964 to a file periodically.
7965 - Stop fetching directory info so aggressively if your DirPort is
7966 on but your ORPort is off; stop fetching v2 dir info entirely.
7967 You can override these choices with the new FetchDirInfoEarly
7971 - The fix in 0.2.0.12-alpha cleared the "hsdir" flag in v3 network
7972 consensus documents when there are too many relays at a single
7973 IP address. Now clear it in v2 network status documents too, and
7974 also clear it in routerinfo_t when the relay is no longer listed
7975 in the relevant networkstatus document.
7976 - Don't crash if we get an unexpected value for the
7977 PublishServerDescriptor config option. Reported by Matt Edman;
7978 bugfix on 0.2.0.9-alpha.
7979 - Our new v2 hidden service descriptor format allows descriptors
7980 that have no introduction points. But Tor crashed when we tried
7981 to build a descriptor with no intro points (and it would have
7982 crashed if we had tried to parse one). Bugfix on 0.2.0.x; patch
7984 - Fix building with dmalloc 5.5.2 with glibc.
7985 - Reject uploaded descriptors and extrainfo documents if they're
7986 huge. Otherwise we'll cache them all over the network and it'll
7987 clog everything up. Reported by Aljosha Judmayer.
7988 - Check for presence of s6_addr16 and s6_addr32 fields in in6_addr
7989 via autoconf. Should fix compile on solaris. Bugfix on 0.2.0.x.
7990 - When the DANGEROUS_VERSION controller status event told us we're
7991 running an obsolete version, it used the string "OLD" to describe
7992 it. Yet the "getinfo" interface used the string "OBSOLETE". Now use
7993 "OBSOLETE" in both cases. Bugfix on 0.1.2.x.
7994 - If we can't expand our list of entry guards (e.g. because we're
7995 using bridges or we have StrictEntryNodes set), don't mark relays
7996 down when they fail a directory request. Otherwise we're too quick
7997 to mark all our entry points down. Bugfix on 0.1.2.x.
7998 - Fix handling of hex nicknames when answering controller requests for
7999 networkstatus by name, or when deciding whether to warn about unknown
8000 routers in a config option. Bugfix on 0.1.2.x. (Patch from mwenge.)
8001 - Fix a couple of hard-to-trigger autoconf problems that could result
8002 in really weird results on platforms whose sys/types.h files define
8003 nonstandard integer types. Bugfix on 0.1.2.x.
8004 - Fix compilation with --disable-threads set. Bugfix on 0.2.0.x.
8005 - Don't crash on name lookup when we have no current consensus. Fixes
8006 bug 538; bugfix on 0.2.0.x.
8007 - Only Tors that want to mirror the v2 directory info should
8008 create the "cached-status" directory in their datadir. (All Tors
8009 used to create it.) Bugfix on 0.2.0.9-alpha.
8010 - Directory authorities should only automatically download Extra Info
8011 documents if they're v1, v2, or v3 authorities. Bugfix on 0.1.2.x.
8014 - On the USR1 signal, when dmalloc is in use, log the top 10 memory
8015 consumers. (We already do this on HUP.)
8016 - Authorities and caches fetch the v2 networkstatus documents
8017 less often, now that v3 is encouraged.
8018 - Add a new config option BridgeRelay that specifies you want to
8019 be a bridge relay. Right now the only difference is that it makes
8020 you answer begin_dir requests, and it makes you cache dir info,
8021 even if your DirPort isn't on.
8022 - Add "GETINFO/desc-annotations/id/<OR digest>" so controllers can
8023 ask about source, timestamp of arrival, purpose, etc. We need
8024 something like this to help Vidalia not do GeoIP lookups on bridge
8026 - Allow multiple HashedControlPassword config lines, to support
8027 multiple controller passwords.
8028 - Authorities now decide whether they're authoritative for a given
8029 router based on the router's purpose.
8030 - New config options AuthDirBadDir and AuthDirListBadDirs for
8031 authorities to mark certain relays as "bad directories" in the
8032 networkstatus documents. Also supports the "!baddir" directive in
8033 the approved-routers file.
8036 Changes in version 0.2.0.12-alpha - 2007-11-16
8037 This twelfth development snapshot fixes some more build problems as
8038 well as a few minor bugs.
8041 - Make it build on OpenBSD again. Patch from tup.
8042 - Substitute BINDIR and LOCALSTATEDIR in scripts. Fixes
8043 package-building for Red Hat, OS X, etc.
8045 o Minor bugfixes (on 0.1.2.x):
8046 - Changing the ExitPolicyRejectPrivate setting should cause us to
8047 rebuild our server descriptor.
8049 o Minor bugfixes (on 0.2.0.x):
8050 - When we're lacking a consensus, don't try to perform rendezvous
8051 operations. Reported by Karsten Loesing.
8052 - Fix a small memory leak whenever we decide against using a
8053 newly picked entry guard. Reported by Mike Perry.
8054 - When authorities detected more than two relays running on the same
8055 IP address, they were clearing all the status flags but forgetting
8056 to clear the "hsdir" flag. So clients were being told that a
8057 given relay was the right choice for a v2 hsdir lookup, yet they
8058 never had its descriptor because it was marked as 'not running'
8060 - If we're trying to fetch a bridge descriptor and there's no way
8061 the bridge authority could help us (for example, we don't know
8062 a digest, or there is no bridge authority), don't be so eager to
8063 fall back to asking the bridge authority.
8064 - If we're using bridges or have strictentrynodes set, and our
8065 chosen exit is in the same family as all our bridges/entry guards,
8066 then be flexible about families.
8069 - When we negotiate a v2 link-layer connection (not yet implemented),
8070 accept RELAY_EARLY cells and turn them into RELAY cells if we've
8071 negotiated a v1 connection for their next step. Initial code for
8075 Changes in version 0.2.0.11-alpha - 2007-11-12
8076 This eleventh development snapshot fixes some build problems with
8077 the previous snapshot. It also includes a more secure-by-default exit
8078 policy for relays, fixes an enormous memory leak for exit relays, and
8079 fixes another bug where servers were falling out of the directory list.
8082 - Exit policies now reject connections that are addressed to a
8083 relay's public (external) IP address too, unless
8084 ExitPolicyRejectPrivate is turned off. We do this because too
8085 many relays are running nearby to services that trust them based
8086 on network address. Bugfix on 0.1.2.x.
8089 - Fix a memory leak on exit relays; we were leaking a cached_resolve_t
8090 on every successful resolve. Reported by Mike Perry; bugfix
8092 - On authorities, never downgrade to old router descriptors simply
8093 because they're listed in the consensus. This created a catch-22
8094 where we wouldn't list a new descriptor because there was an
8095 old one in the consensus, and we couldn't get the new one in the
8096 consensus because we wouldn't list it. Possible fix for bug 548.
8097 Also, this might cause bug 543 to appear on authorities; if so,
8098 we'll need a band-aid for that. Bugfix on 0.2.0.9-alpha.
8100 o Packaging fixes on 0.2.0.10-alpha:
8101 - We were including instructions about what to do with the
8102 src/config/fallback-consensus file, but we weren't actually
8103 including it in the tarball. Disable all of that for now.
8106 - Allow people to say PreferTunnelledDirConns rather than
8107 PreferTunneledDirConns, for those alternate-spellers out there.
8110 - Don't reevaluate all the information from our consensus document
8111 just because we've downloaded a v2 networkstatus that we intend
8112 to cache. Fixes bug 545; bugfix on 0.2.0.x.
8115 Changes in version 0.2.0.10-alpha - 2007-11-10
8116 This tenth development snapshot adds a third v3 directory authority
8117 run by Mike Perry, adds most of Karsten Loesing's new hidden service
8118 descriptor format, fixes a bad crash bug and new bridge bugs introduced
8119 in 0.2.0.9-alpha, fixes many bugs with the v3 directory implementation,
8120 fixes some minor memory leaks in previous 0.2.0.x snapshots, and
8121 addresses many more minor issues.
8123 o New directory authorities:
8124 - Set up ides (run by Mike Perry) as the third v3 directory authority.
8127 - Allow tunnelled directory connections to ask for an encrypted
8128 "begin_dir" connection or an anonymized "uses a full Tor circuit"
8129 connection independently. Now we can make anonymized begin_dir
8130 connections for (e.g.) more secure hidden service posting and
8132 - More progress on proposal 114: code from Karsten Loesing to
8133 implement new hidden service descriptor format.
8134 - Raise the default BandwidthRate/BandwidthBurst to 5MB/10MB, to
8135 accommodate the growing number of servers that use the default
8136 and are reaching it.
8137 - Directory authorities use a new formula for selecting which nodes
8138 to advertise as Guards: they must be in the top 7/8 in terms of
8139 how long we have known about them, and above the median of those
8140 nodes in terms of weighted fractional uptime.
8141 - Make "not enough dir info yet" warnings describe *why* Tor feels
8142 it doesn't have enough directory info yet.
8145 - Stop servers from crashing if they set a Family option (or
8146 maybe in other situations too). Bugfix on 0.2.0.9-alpha; reported
8148 - Make bridge users work again -- the move to v3 directories in
8149 0.2.0.9-alpha had introduced a number of bugs that made bridges
8150 no longer work for clients.
8151 - When the clock jumps forward a lot, do not allow the bandwidth
8152 buckets to become negative. Bugfix on 0.1.2.x; fixes bug 544.
8154 o Major bugfixes (v3 dir, bugfixes on 0.2.0.9-alpha):
8155 - When the consensus lists a router descriptor that we previously were
8156 mirroring, but that we considered non-canonical, reload the
8157 descriptor as canonical. This fixes bug 543 where Tor servers
8158 would start complaining after a few days that they don't have
8159 enough directory information to build a circuit.
8160 - Consider replacing the current consensus when certificates arrive
8161 that make the pending consensus valid. Previously, we were only
8162 considering replacement when the new certs _didn't_ help.
8163 - Fix an assert error on startup if we didn't already have the
8164 consensus and certs cached in our datadirectory: we were caching
8165 the consensus in consensus_waiting_for_certs but then free'ing it
8167 - Avoid sending a request for "keys/fp" (for which we'll get a 400 Bad
8168 Request) if we need more v3 certs but we've already got pending
8169 requests for all of them.
8170 - Correctly back off from failing certificate downloads. Fixes
8172 - Authorities don't vote on the Running flag if they have been running
8173 for less than 30 minutes themselves. Fixes bug 547, where a newly
8174 started authority would vote that everyone was down.
8177 - Drop support for OpenSSL version 0.9.6. Just about nobody was using
8178 it, it had no AES, and it hasn't seen any security patches since
8182 - Clients now hold circuitless TLS connections open for 1.5 times
8183 MaxCircuitDirtiness (15 minutes), since it is likely that they'll
8184 rebuild a new circuit over them within that timeframe. Previously,
8185 they held them open only for KeepalivePeriod (5 minutes).
8186 - Use "If-Modified-Since" to avoid retrieving consensus
8187 networkstatuses that we already have.
8188 - When we have no consensus, check FallbackNetworkstatusFile (defaults
8189 to $PREFIX/share/tor/fallback-consensus) for a consensus. This way
8190 we start knowing some directory caches.
8191 - When we receive a consensus from the future, warn about skew.
8192 - Improve skew reporting: try to give the user a better log message
8193 about how skewed they are, and how much this matters.
8194 - When we have a certificate for an authority, believe that
8195 certificate's claims about the authority's IP address.
8196 - New --quiet command-line option to suppress the default console log.
8197 Good in combination with --hash-password.
8198 - Authorities send back an X-Descriptor-Not-New header in response to
8199 an accepted-but-discarded descriptor upload. Partially implements
8201 - Make the log message for "tls error. breaking." more useful.
8202 - Better log messages about certificate downloads, to attempt to
8203 track down the second incarnation of bug 546.
8205 o Minor features (bridges):
8206 - If bridge users set UpdateBridgesFromAuthority, but the digest
8207 they ask for is a 404 from the bridge authority, they now fall
8208 back to trying the bridge directly.
8209 - Bridges now use begin_dir to publish their server descriptor to
8210 the bridge authority, even when they haven't set TunnelDirConns.
8212 o Minor features (controller):
8213 - When reporting clock skew, and we know that the clock is _at least
8214 as skewed_ as some value, but we don't know the actual value,
8215 report the value as a "minimum skew."
8218 - Update linux-tor-prio.sh script to allow QoS based on the uid of
8219 the Tor process. Patch from Marco Bonetti with tweaks from Mike
8223 - Refuse to start if both ORPort and UseBridges are set. Bugfix
8224 on 0.2.0.x, suggested by Matt Edman.
8225 - Don't stop fetching descriptors when FetchUselessDescriptors is
8226 set, even if we stop asking for circuits. Bugfix on 0.1.2.x;
8227 reported by tup and ioerror.
8228 - Better log message on vote from unknown authority.
8229 - Don't log "Launching 0 request for 0 router" message.
8231 o Minor bugfixes (memory leaks):
8232 - Stop leaking memory every time we parse a v3 certificate. Bugfix
8234 - Stop leaking memory every time we load a v3 certificate. Bugfix
8235 on 0.2.0.1-alpha. Fixes bug 536.
8236 - Stop leaking a cached networkstatus on exit. Bugfix on
8238 - Stop leaking voter information every time we free a consensus.
8239 Bugfix on 0.2.0.3-alpha.
8240 - Stop leaking signed data every time we check a voter signature.
8241 Bugfix on 0.2.0.3-alpha.
8242 - Stop leaking a signature every time we fail to parse a consensus or
8243 a vote. Bugfix on 0.2.0.3-alpha.
8244 - Stop leaking v2_download_status_map on shutdown. Bugfix on
8246 - Stop leaking conn->nickname every time we make a connection to a
8247 Tor relay without knowing its expected identity digest (e.g. when
8248 using bridges). Bugfix on 0.2.0.3-alpha.
8250 - Minor bugfixes (portability):
8251 - Run correctly on platforms where rlim_t is larger than unsigned
8252 long, and/or where the real limit for number of open files is
8253 OPEN_FILES, not rlim_max from getrlimit(RLIMIT_NOFILES). In
8254 particular, these may be needed for OS X 10.5.
8257 Changes in version 0.1.2.18 - 2007-10-28
8258 Tor 0.1.2.18 fixes many problems including crash bugs, problems with
8259 hidden service introduction that were causing huge delays, and a big
8260 bug that was causing some servers to disappear from the network status
8261 lists for a few hours each day.
8263 o Major bugfixes (crashes):
8264 - If a connection is shut down abruptly because of something that
8265 happened inside connection_flushed_some(), do not call
8266 connection_finished_flushing(). Should fix bug 451:
8267 "connection_stop_writing: Assertion conn->write_event failed"
8268 Bugfix on 0.1.2.7-alpha.
8269 - Fix possible segfaults in functions called from
8270 rend_process_relay_cell().
8272 o Major bugfixes (hidden services):
8273 - Hidden services were choosing introduction points uniquely by
8274 hexdigest, but when constructing the hidden service descriptor
8275 they merely wrote the (potentially ambiguous) nickname.
8276 - Clients now use the v2 intro format for hidden service
8277 connections: they specify their chosen rendezvous point by identity
8278 digest rather than by (potentially ambiguous) nickname. These
8279 changes could speed up hidden service connections dramatically.
8281 o Major bugfixes (other):
8282 - Stop publishing a new server descriptor just because we get a
8283 HUP signal. This led (in a roundabout way) to some servers getting
8284 dropped from the networkstatus lists for a few hours each day.
8285 - When looking for a circuit to cannibalize, consider family as well
8286 as identity. Fixes bug 438. Bugfix on 0.1.0.x (which introduced
8287 circuit cannibalization).
8288 - When a router wasn't listed in a new networkstatus, we were leaving
8289 the flags for that router alone -- meaning it remained Named,
8290 Running, etc -- even though absence from the networkstatus means
8291 that it shouldn't be considered to exist at all anymore. Now we
8292 clear all the flags for routers that fall out of the networkstatus
8293 consensus. Fixes bug 529.
8296 - Don't try to access (or alter) the state file when running
8297 --list-fingerprint or --verify-config or --hash-password. Resolves
8299 - When generating information telling us how to extend to a given
8300 router, do not try to include the nickname if it is
8301 absent. Resolves bug 467.
8302 - Fix a user-triggerable segfault in expand_filename(). (There isn't
8303 a way to trigger this remotely.)
8304 - When sending a status event to the controller telling it that an
8305 OR address is reachable, set the port correctly. (Previously we
8306 were reporting the dir port.)
8307 - Fix a minor memory leak whenever a controller sends the PROTOCOLINFO
8308 command. Bugfix on 0.1.2.17.
8309 - When loading bandwidth history, do not believe any information in
8310 the future. Fixes bug 434.
8311 - When loading entry guard information, do not believe any information
8313 - When we have our clock set far in the future and generate an
8314 onion key, then re-set our clock to be correct, we should not stop
8315 the onion key from getting rotated.
8316 - On some platforms, accept() can return a broken address. Detect
8317 this more quietly, and deal accordingly. Fixes bug 483.
8318 - It's not actually an error to find a non-pending entry in the DNS
8319 cache when canceling a pending resolve. Don't log unless stuff
8320 is fishy. Resolves bug 463.
8321 - Don't reset trusted dir server list when we set a configuration
8322 option. Patch from Robert Hogan.
8323 - Don't try to create the datadir when running --verify-config or
8324 --hash-password. Resolves bug 540.
8327 Changes in version 0.2.0.9-alpha - 2007-10-24
8328 This ninth development snapshot switches clients to the new v3 directory
8329 system; allows servers to be listed in the network status even when they
8330 have the same nickname as a registered server; and fixes many other
8331 bugs including a big one that was causing some servers to disappear
8332 from the network status lists for a few hours each day.
8334 o Major features (directory system):
8335 - Clients now download v3 consensus networkstatus documents instead
8336 of v2 networkstatus documents. Clients and caches now base their
8337 opinions about routers on these consensus documents. Clients only
8338 download router descriptors listed in the consensus.
8339 - Authorities now list servers who have the same nickname as
8340 a different named server, but list them with a new flag,
8341 "Unnamed". Now we can list servers that happen to pick the same
8342 nickname as a server that registered two years ago and then
8343 disappeared. Partially implements proposal 122.
8344 - If the consensus lists a router as "Unnamed", the name is assigned
8345 to a different router: do not identify the router by that name.
8346 Partially implements proposal 122.
8347 - Authorities can now come to a consensus on which method to use to
8348 compute the consensus. This gives us forward compatibility.
8351 - Stop publishing a new server descriptor just because we HUP or
8352 when we find our DirPort to be reachable but won't actually publish
8353 it. New descriptors without any real changes are dropped by the
8354 authorities, and can screw up our "publish every 18 hours" schedule.
8356 - When a router wasn't listed in a new networkstatus, we were leaving
8357 the flags for that router alone -- meaning it remained Named,
8358 Running, etc -- even though absence from the networkstatus means
8359 that it shouldn't be considered to exist at all anymore. Now we
8360 clear all the flags for routers that fall out of the networkstatus
8361 consensus. Fixes bug 529; bugfix on 0.1.2.x.
8362 - Fix awful behavior in DownloadExtraInfo option where we'd fetch
8363 extrainfo documents and then discard them immediately for not
8364 matching the latest router. Bugfix on 0.2.0.1-alpha.
8366 o Minor features (v3 directory protocol):
8367 - Allow tor-gencert to generate a new certificate without replacing
8369 - Allow certificates to include an address.
8370 - When we change our directory-cache settings, reschedule all voting
8371 and download operations.
8372 - Reattempt certificate downloads immediately on failure, as long as
8373 we haven't failed a threshold number of times yet.
8374 - Delay retrying consensus downloads while we're downloading
8375 certificates to verify the one we just got. Also, count getting a
8376 consensus that we already have (or one that isn't valid) as a failure,
8377 and count failing to get the certificates after 20 minutes as a
8379 - Build circuits and download descriptors even if our consensus is a
8380 little expired. (This feature will go away once authorities are
8383 o Minor features (router descriptor cache):
8384 - If we find a cached-routers file that's been sitting around for more
8385 than 28 days unmodified, then most likely it's a leftover from
8386 when we upgraded to 0.2.0.8-alpha. Remove it. It has no good
8388 - When we (as a cache) download a descriptor because it was listed
8389 in a consensus, remember when the consensus was supposed to expire,
8390 and don't expire the descriptor until then.
8392 o Minor features (performance):
8393 - Call routerlist_remove_old_routers() much less often. This should
8394 speed startup, especially on directory caches.
8395 - Don't try to launch new descriptor downloads quite so often when we
8396 already have enough directory information to build circuits.
8397 - Base64 decoding was actually showing up on our profile when parsing
8398 the initial descriptor file; switch to an in-process all-at-once
8399 implementation that's about 3.5x times faster than calling out to
8402 o Minor features (compilation):
8403 - Detect non-ASCII platforms (if any still exist) and refuse to
8404 build there: some of our code assumes that 'A' is 65 and so on.
8406 o Minor bugfixes (v3 directory authorities, bugfixes on 0.2.0.x):
8407 - Make the "next period" votes into "current period" votes immediately
8408 after publishing the consensus; avoid a heisenbug that made them
8409 stick around indefinitely.
8410 - When we discard a vote as a duplicate, do not report this as
8412 - Treat missing v3 keys or certificates as an error when running as a
8413 v3 directory authority.
8414 - When we're configured to be a v3 authority, but we're only listed
8415 as a non-v3 authority in our DirServer line for ourself, correct
8417 - If an authority doesn't have a qualified hostname, just put
8418 its address in the vote. This fixes the problem where we referred to
8419 "moria on moria:9031."
8420 - Distinguish between detached signatures for the wrong period, and
8421 detached signatures for a divergent vote.
8422 - Fix a small memory leak when computing a consensus.
8423 - When there's no concensus, we were forming a vote every 30
8424 minutes, but writing the "valid-after" line in our vote based
8425 on our configured V3AuthVotingInterval: so unless the intervals
8426 matched up, we immediately rejected our own vote because it didn't
8427 start at the voting interval that caused us to construct a vote.
8429 o Minor bugfixes (v3 directory protocol, bugfixes on 0.2.0.x):
8430 - Delete unverified-consensus when the real consensus is set.
8431 - Consider retrying a consensus networkstatus fetch immediately
8432 after one fails: don't wait 60 seconds to notice.
8433 - When fetching a consensus as a cache, wait until a newer consensus
8434 should exist before trying to replace the current one.
8435 - Use a more forgiving schedule for retrying failed consensus
8436 downloads than for other types.
8438 o Minor bugfixes (other directory issues):
8439 - Correct the implementation of "download votes by digest." Bugfix on
8441 - Authorities no longer send back "400 you're unreachable please fix
8442 it" errors to Tor servers that aren't online all the time. We're
8443 supposed to tolerate these servers now. Bugfix on 0.1.2.x.
8445 o Minor bugfixes (controller):
8446 - Don't reset trusted dir server list when we set a configuration
8447 option. Patch from Robert Hogan; bugfix on 0.1.2.x.
8448 - Respond to INT and TERM SIGNAL commands before we execute the
8449 signal, in case the signal shuts us down. We had a patch in
8450 0.1.2.1-alpha that tried to do this by queueing the response on
8451 the connection's buffer before shutting down, but that really
8452 isn't the same thing at all. Bug located by Matt Edman.
8454 o Minor bugfixes (misc):
8455 - Correctly check for bad options to the "PublishServerDescriptor"
8456 config option. Bugfix on 0.2.0.1-alpha; reported by Matt Edman.
8457 - Stop leaking memory on failing case of base32_decode, and make
8458 it accept upper-case letters. Bugfixes on 0.2.0.7-alpha.
8459 - Don't try to download extrainfo documents when we're trying to
8460 fetch enough directory info to build a circuit: having enough
8461 info should get priority. Bugfix on 0.2.0.x.
8462 - Don't complain that "your server has not managed to confirm that its
8463 ports are reachable" if we haven't been able to build any circuits
8464 yet. Bug found by spending four hours without a v3 consensus. Bugfix
8466 - Detect the reason for failing to mmap a descriptor file we just
8467 wrote, and give a more useful log message. Fixes bug 533. Bugfix
8470 o Code simplifications and refactoring:
8471 - Remove support for the old bw_accounting file: we've been storing
8472 bandwidth accounting information in the state file since
8473 0.1.2.5-alpha. This may result in bandwidth accounting errors
8474 if you try to upgrade from 0.1.1.x or earlier, or if you try to
8475 downgrade to 0.1.1.x or earlier.
8476 - New convenience code to locate a file within the DataDirectory.
8477 - Move non-authority functionality out of dirvote.c.
8478 - Refactor the arguments for router_pick_{directory_|trusteddir}server
8479 so that they all take the same named flags.
8482 - Include the "tor-ctrl.sh" bash script by Stefan Behte to provide
8483 Unix users an easy way to script their Tor process (e.g. by
8484 adjusting bandwidth based on the time of the day).
8487 Changes in version 0.2.0.8-alpha - 2007-10-12
8488 This eighth development snapshot fixes a crash bug that's been bothering
8489 us since February 2007, lets bridge authorities store a list of bridge
8490 descriptors they've seen, gets v3 directory voting closer to working,
8491 starts caching v3 directory consensus documents on directory mirrors,
8492 and fixes a variety of smaller issues including some minor memory leaks.
8494 o Major features (router descriptor cache):
8495 - Store routers in a file called cached-descriptors instead of in
8496 cached-routers. Initialize cached-descriptors from cached-routers
8497 if the old format is around. The new format allows us to store
8498 annotations along with descriptors.
8499 - Use annotations to record the time we received each descriptor, its
8500 source, and its purpose.
8501 - Disable the SETROUTERPURPOSE controller command: it is now
8503 - Controllers should now specify cache=no or cache=yes when using
8504 the +POSTDESCRIPTOR command.
8505 - Bridge authorities now write bridge descriptors to disk, meaning
8506 we can export them to other programs and begin distributing them
8509 o Major features (directory authorities):
8510 - When a v3 authority is missing votes or signatures, it now tries
8512 - Directory authorities track weighted fractional uptime as well as
8513 weighted mean-time-between failures. WFU is suitable for deciding
8514 whether a node is "usually up", while MTBF is suitable for deciding
8515 whether a node is "likely to stay up." We need both, because
8516 "usually up" is a good requirement for guards, while "likely to
8517 stay up" is a good requirement for long-lived connections.
8519 o Major features (v3 directory system):
8520 - Caches now download v3 network status documents as needed,
8521 and download the descriptors listed in them.
8522 - All hosts now attempt to download and keep fresh v3 authority
8523 certificates, and re-attempt after failures.
8524 - More internal-consistency checks for vote parsing.
8526 o Major bugfixes (crashes):
8527 - If a connection is shut down abruptly because of something that
8528 happened inside connection_flushed_some(), do not call
8529 connection_finished_flushing(). Should fix bug 451. Bugfix on
8532 o Major bugfixes (performance):
8533 - Fix really bad O(n^2) performance when parsing a long list of
8534 routers: Instead of searching the entire list for an "extra-info "
8535 string which usually wasn't there, once for every routerinfo
8536 we read, just scan lines forward until we find one we like.
8538 - When we add data to a write buffer in response to the data on that
8539 write buffer getting low because of a flush, do not consider the
8540 newly added data as a candidate for immediate flushing, but rather
8541 make it wait until the next round of writing. Otherwise, we flush
8542 and refill recursively, and a single greedy TLS connection can
8543 eat all of our bandwidth. Bugfix on 0.1.2.7-alpha.
8545 o Minor features (v3 authority system):
8546 - Add more ways for tools to download the votes that lead to the
8548 - Send a 503 when low on bandwidth and a vote, consensus, or
8549 certificate is requested.
8550 - If-modified-since is now implemented properly for all kinds of
8551 certificate requests.
8553 o Minor bugfixes (network statuses):
8554 - Tweak the implementation of proposal 109 slightly: allow at most
8555 two Tor servers on the same IP address, except if it's the location
8556 of a directory authority, in which case allow five. Bugfix on
8559 o Minor bugfixes (controller):
8560 - When sending a status event to the controller telling it that an
8561 OR address is reachable, set the port correctly. (Previously we
8562 were reporting the dir port.) Bugfix on 0.1.2.x.
8564 o Minor bugfixes (v3 directory system):
8565 - Fix logic to look up a cert by its signing key digest. Bugfix on
8567 - Only change the reply to a vote to "OK" if it's not already
8568 set. This gets rid of annoying "400 OK" log messages, which may
8569 have been masking some deeper issue. Bugfix on 0.2.0.7-alpha.
8570 - When we get a valid consensus, recompute the voting schedule.
8571 - Base the valid-after time of a vote on the consensus voting
8572 schedule, not on our preferred schedule.
8573 - Make the return values and messages from signature uploads and
8574 downloads more sensible.
8575 - Fix a memory leak when serving votes and consensus documents, and
8576 another when serving certificates.
8578 o Minor bugfixes (performance):
8579 - Use a slightly simpler string hashing algorithm (copying Python's
8580 instead of Java's) and optimize our digest hashing algorithm to take
8581 advantage of 64-bit platforms and to remove some possibly-costly
8583 - Fix a minor memory leak whenever we parse guards from our state
8584 file. Bugfix on 0.2.0.7-alpha.
8585 - Fix a minor memory leak whenever we write out a file. Bugfix on
8587 - Fix a minor memory leak whenever a controller sends the PROTOCOLINFO
8588 command. Bugfix on 0.2.0.5-alpha.
8590 o Minor bugfixes (portability):
8591 - On some platforms, accept() can return a broken address. Detect
8592 this more quietly, and deal accordingly. Fixes bug 483.
8593 - Stop calling tor_strlower() on uninitialized memory in some cases.
8594 Bugfix in 0.2.0.7-alpha.
8596 o Minor bugfixes (usability):
8597 - Treat some 403 responses from directory servers as INFO rather than
8598 WARN-severity events.
8599 - It's not actually an error to find a non-pending entry in the DNS
8600 cache when canceling a pending resolve. Don't log unless stuff is
8601 fishy. Resolves bug 463.
8603 o Minor bugfixes (anonymity):
8604 - Never report that we've used more bandwidth than we're willing to
8605 relay: it leaks how much non-relay traffic we're using. Resolves
8607 - When looking for a circuit to cannibalize, consider family as well
8608 as identity. Fixes bug 438. Bugfix on 0.1.0.x (which introduced
8609 circuit cannibalization).
8611 o Code simplifications and refactoring:
8612 - Make a bunch of functions static. Remove some dead code.
8613 - Pull out about a third of the really big routerlist.c; put it in a
8614 new module, networkstatus.c.
8615 - Merge the extra fields in local_routerstatus_t back into
8616 routerstatus_t: we used to need one routerstatus_t for each
8617 authority's opinion, plus a local_routerstatus_t for the locally
8618 computed consensus opinion. To save space, we put the locally
8619 modified fields into local_routerstatus_t, and only the common
8620 stuff into routerstatus_t. But once v3 directories are in use,
8621 clients and caches will no longer need to hold authority opinions;
8622 thus, the rationale for keeping the types separate is now gone.
8623 - Make the code used to reschedule and reattempt downloads more
8625 - Turn all 'Are we a directory server/mirror?' logic into a call to
8627 - Remove the code to generate the oldest (v1) directory format.
8628 The code has been disabled since 0.2.0.5-alpha.
8631 Changes in version 0.2.0.7-alpha - 2007-09-21
8632 This seventh development snapshot makes bridges work again, makes bridge
8633 authorities work for the first time, fixes two huge performance flaws
8634 in hidden services, and fixes a variety of minor issues.
8636 o New directory authorities:
8637 - Set up moria1 and tor26 as the first v3 directory authorities. See
8638 doc/spec/dir-spec.txt for details on the new directory design.
8640 o Major bugfixes (crashes):
8641 - Fix possible segfaults in functions called from
8642 rend_process_relay_cell(). Bugfix on 0.1.2.x.
8644 o Major bugfixes (bridges):
8645 - Fix a bug that made servers send a "404 Not found" in response to
8646 attempts to fetch their server descriptor. This caused Tor servers
8647 to take many minutes to establish reachability for their DirPort,
8648 and it totally crippled bridges. Bugfix on 0.2.0.5-alpha.
8649 - Make "UpdateBridgesFromAuthority" torrc option work: when bridge
8650 users configure that and specify a bridge with an identity
8651 fingerprint, now they will lookup the bridge descriptor at the
8652 default bridge authority via a one-hop tunnel, but once circuits
8653 are established they will switch to a three-hop tunnel for later
8654 connections to the bridge authority. Bugfix in 0.2.0.3-alpha.
8656 o Major bugfixes (hidden services):
8657 - Hidden services were choosing introduction points uniquely by
8658 hexdigest, but when constructing the hidden service descriptor
8659 they merely wrote the (potentially ambiguous) nickname.
8660 - Clients now use the v2 intro format for hidden service
8661 connections: they specify their chosen rendezvous point by identity
8662 digest rather than by (potentially ambiguous) nickname. Both
8663 are bugfixes on 0.1.2.x, and they could speed up hidden service
8664 connections dramatically. Thanks to Karsten Loesing.
8666 o Minor features (security):
8667 - As a client, do not believe any server that tells us that an
8668 address maps to an internal address space.
8669 - Make it possible to enable HashedControlPassword and
8670 CookieAuthentication at the same time.
8672 o Minor features (guard nodes):
8673 - Tag every guard node in our state file with the version that
8674 we believe added it, or with our own version if we add it. This way,
8675 if a user temporarily runs an old version of Tor and then switches
8676 back to a new one, she doesn't automatically lose her guards.
8678 o Minor features (speed):
8679 - When implementing AES counter mode, update only the portions of the
8680 counter buffer that need to change, and don't keep separate
8681 network-order and host-order counters when they are the same (i.e.,
8682 on big-endian hosts.)
8684 o Minor features (controller):
8685 - Accept LF instead of CRLF on controller, since some software has a
8686 hard time generating real Internet newlines.
8687 - Add GETINFO values for the server status events
8688 "REACHABILITY_SUCCEEDED" and "GOOD_SERVER_DESCRIPTOR". Patch from
8692 - Routers no longer include bandwidth-history lines in their
8693 descriptors; this information is already available in extra-info
8694 documents, and including it in router descriptors took up 60%
8695 (!) of compressed router descriptor downloads. Completes
8696 implementation of proposal 104.
8697 - Remove the contrib scripts ExerciseServer.py, PathDemo.py,
8698 and TorControl.py, as they use the old v0 controller protocol,
8699 and are obsoleted by TorFlow anyway.
8700 - Drop support for v1 rendezvous descriptors, since we never used
8701 them anyway, and the code has probably rotted by now. Based on
8702 patch from Karsten Loesing.
8703 - On OSX, stop warning the user that kqueue support in libevent is
8704 "experimental", since it seems to have worked fine for ages.
8707 - When generating information telling us how to extend to a given
8708 router, do not try to include the nickname if it is absent. Fixes
8709 bug 467. Bugfix on 0.2.0.3-alpha.
8710 - Fix a user-triggerable (but not remotely-triggerable) segfault
8711 in expand_filename(). Bugfix on 0.1.2.x.
8712 - Fix a memory leak when freeing incomplete requests from DNSPort.
8713 Found by Niels Provos with valgrind. Bugfix on 0.2.0.1-alpha.
8714 - Don't try to access (or alter) the state file when running
8715 --list-fingerprint or --verify-config or --hash-password. (Resolves
8716 bug 499.) Bugfix on 0.1.2.x.
8717 - Servers used to decline to publish their DirPort if their
8718 BandwidthRate, RelayBandwidthRate, or MaxAdvertisedBandwidth
8719 were below a threshold. Now they only look at BandwidthRate and
8720 RelayBandwidthRate. Bugfix on 0.1.2.x.
8721 - Remove an optimization in the AES counter-mode code that assumed
8722 that the counter never exceeded 2^68. When the counter can be set
8723 arbitrarily as an IV (as it is by Karsten's new hidden services
8724 code), this assumption no longer holds. Bugfix on 0.1.2.x.
8725 - Resume listing "AUTHORITY" flag for authorities in network status.
8726 Bugfix on 0.2.0.3-alpha; reported by Alex de Joode.
8728 o Code simplifications and refactoring:
8729 - Revamp file-writing logic so we don't need to have the entire
8730 contents of a file in memory at once before we write to disk. Tor,
8732 - Turn "descriptor store" into a full-fledged type.
8733 - Move all NT services code into a separate source file.
8734 - Unify all code that computes medians, percentile elements, etc.
8735 - Get rid of a needless malloc when parsing address policies.
8738 Changes in version 0.1.2.17 - 2007-08-30
8739 Tor 0.1.2.17 features a new Vidalia version in the Windows and OS
8740 X bundles. Vidalia 0.0.14 makes authentication required for the
8741 ControlPort in the default configuration, which addresses important
8742 security risks. Everybody who uses Vidalia (or another controller)
8745 In addition, this Tor update fixes major load balancing problems with
8746 path selection, which should speed things up a lot once many people
8749 o Major bugfixes (security):
8750 - We removed support for the old (v0) control protocol. It has been
8751 deprecated since Tor 0.1.1.1-alpha, and keeping it secure has
8752 become more of a headache than it's worth.
8754 o Major bugfixes (load balancing):
8755 - When choosing nodes for non-guard positions, weight guards
8756 proportionally less, since they already have enough load. Patch
8758 - Raise the "max believable bandwidth" from 1.5MB/s to 10MB/s. This
8759 will allow fast Tor servers to get more attention.
8760 - When we're upgrading from an old Tor version, forget our current
8761 guards and pick new ones according to the new weightings. These
8762 three load balancing patches could raise effective network capacity
8763 by a factor of four. Thanks to Mike Perry for measurements.
8765 o Major bugfixes (stream expiration):
8766 - Expire not-yet-successful application streams in all cases if
8767 they've been around longer than SocksTimeout. Right now there are
8768 some cases where the stream will live forever, demanding a new
8769 circuit every 15 seconds. Fixes bug 454; reported by lodger.
8771 o Minor features (controller):
8772 - Add a PROTOCOLINFO controller command. Like AUTHENTICATE, it
8773 is valid before any authentication has been received. It tells
8774 a controller what kind of authentication is expected, and what
8775 protocol is spoken. Implements proposal 119.
8777 o Minor bugfixes (performance):
8778 - Save on most routerlist_assert_ok() calls in routerlist.c, thus
8779 greatly speeding up loading cached-routers from disk on startup.
8780 - Disable sentinel-based debugging for buffer code: we squashed all
8781 the bugs that this was supposed to detect a long time ago, and now
8782 its only effect is to change our buffer sizes from nice powers of
8783 two (which platform mallocs tend to like) to values slightly over
8784 powers of two (which make some platform mallocs sad).
8786 o Minor bugfixes (misc):
8787 - If exit bandwidth ever exceeds one third of total bandwidth, then
8788 use the correct formula to weight exit nodes when choosing paths.
8789 Based on patch from Mike Perry.
8790 - Choose perfectly fairly among routers when choosing by bandwidth and
8791 weighting by fraction of bandwidth provided by exits. Previously, we
8792 would choose with only approximate fairness, and correct ourselves
8793 if we ran off the end of the list.
8794 - If we require CookieAuthentication but we fail to write the
8795 cookie file, we would warn but not exit, and end up in a state
8796 where no controller could authenticate. Now we exit.
8797 - If we require CookieAuthentication, stop generating a new cookie
8798 every time we change any piece of our config.
8799 - Refuse to start with certain directory authority keys, and
8800 encourage people using them to stop.
8801 - Terminate multi-line control events properly. Original patch
8803 - Fix a minor memory leak when we fail to find enough suitable
8804 servers to choose a circuit.
8805 - Stop leaking part of the descriptor when we run into a particularly
8806 unparseable piece of it.
8809 Changes in version 0.2.0.6-alpha - 2007-08-26
8810 This sixth development snapshot features a new Vidalia version in the
8811 Windows and OS X bundles. Vidalia 0.0.14 makes authentication required for
8812 the ControlPort in the default configuration, which addresses important
8815 In addition, this snapshot fixes major load balancing problems
8816 with path selection, which should speed things up a lot once many
8817 people have upgraded. The directory authorities also use a new
8818 mean-time-between-failure approach to tracking which servers are stable,
8819 rather than just looking at the most recent uptime.
8821 o New directory authorities:
8822 - Set up Tonga as the default bridge directory authority.
8825 - Directory authorities now track servers by weighted
8826 mean-times-between-failures. When we have 4 or more days of data,
8827 use measured MTBF rather than declared uptime to decide whether
8828 to call a router Stable. Implements proposal 108.
8830 o Major bugfixes (load balancing):
8831 - When choosing nodes for non-guard positions, weight guards
8832 proportionally less, since they already have enough load. Patch
8834 - Raise the "max believable bandwidth" from 1.5MB/s to 10MB/s. This
8835 will allow fast Tor servers to get more attention.
8836 - When we're upgrading from an old Tor version, forget our current
8837 guards and pick new ones according to the new weightings. These
8838 three load balancing patches could raise effective network capacity
8839 by a factor of four. Thanks to Mike Perry for measurements.
8841 o Major bugfixes (descriptor parsing):
8842 - Handle unexpected whitespace better in malformed descriptors. Bug
8843 found using Benedikt Boss's new Tor fuzzer! Bugfix on 0.2.0.x.
8846 - There is now an ugly, temporary "desc/all-recent-extrainfo-hack"
8847 GETINFO for Torstat to use until it can switch to using extrainfos.
8848 - Optionally (if built with -DEXPORTMALLINFO) export the output
8849 of mallinfo via http, as tor/mallinfo.txt. Only accessible
8853 - Do not intermix bridge routers with controller-added
8854 routers. (Bugfix on 0.2.0.x)
8855 - Do not fail with an assert when accept() returns an unexpected
8856 address family. Addresses but does not wholly fix bug 483. (Bugfix
8858 - Let directory authorities startup even when they can't generate
8859 a descriptor immediately, e.g. because they don't know their
8861 - Stop putting the authentication cookie in a file called "0"
8862 in your working directory if you don't specify anything for the
8863 new CookieAuthFile option. Reported by Matt Edman.
8864 - Make it possible to read the PROTOCOLINFO response in a way that
8865 conforms to our control-spec. Reported by Matt Edman.
8866 - Fix a minor memory leak when we fail to find enough suitable
8867 servers to choose a circuit. Bugfix on 0.1.2.x.
8868 - Stop leaking part of the descriptor when we run into a particularly
8869 unparseable piece of it. Bugfix on 0.1.2.x.
8870 - Unmap the extrainfo cache file on exit.
8873 Changes in version 0.2.0.5-alpha - 2007-08-19
8874 This fifth development snapshot fixes compilation on Windows again;
8875 fixes an obnoxious client-side bug that slowed things down and put
8876 extra load on the network; gets us closer to using the v3 directory
8877 voting scheme; makes it easier for Tor controllers to use cookie-based
8878 authentication; and fixes a variety of other bugs.
8881 - Version 1 directories are no longer generated in full. Instead,
8882 authorities generate and serve "stub" v1 directories that list
8883 no servers. This will stop Tor versions 0.1.0.x and earlier from
8884 working, but (for security reasons) nobody should be running those
8887 o Major bugfixes (compilation, 0.2.0.x):
8888 - Try to fix Win32 compilation again: improve checking for IPv6 types.
8889 - Try to fix MSVC compilation: build correctly on platforms that do
8890 not define s6_addr16 or s6_addr32.
8891 - Fix compile on platforms without getaddrinfo: bug found by Li-Hui
8894 o Major bugfixes (stream expiration):
8895 - Expire not-yet-successful application streams in all cases if
8896 they've been around longer than SocksTimeout. Right now there are
8897 some cases where the stream will live forever, demanding a new
8898 circuit every 15 seconds. Bugfix on 0.1.2.7-alpha; fixes bug 454;
8901 o Minor features (directory servers):
8902 - When somebody requests a list of statuses or servers, and we have
8903 none of those, return a 404 rather than an empty 200.
8905 o Minor features (directory voting):
8906 - Store v3 consensus status consensuses on disk, and reload them
8909 o Minor features (security):
8910 - Warn about unsafe ControlPort configurations.
8911 - Refuse to start with certain directory authority keys, and
8912 encourage people using them to stop.
8914 o Minor features (controller):
8915 - Add a PROTOCOLINFO controller command. Like AUTHENTICATE, it
8916 is valid before any authentication has been received. It tells
8917 a controller what kind of authentication is expected, and what
8918 protocol is spoken. Implements proposal 119.
8919 - New config option CookieAuthFile to choose a new location for the
8920 cookie authentication file, and config option
8921 CookieAuthFileGroupReadable to make it group-readable.
8923 o Minor features (unit testing):
8924 - Add command-line arguments to unit-test executable so that we can
8925 invoke any chosen test from the command line rather than having
8926 to run the whole test suite at once; and so that we can turn on
8927 logging for the unit tests.
8929 o Minor bugfixes (on 0.1.2.x):
8930 - If we require CookieAuthentication but we fail to write the
8931 cookie file, we would warn but not exit, and end up in a state
8932 where no controller could authenticate. Now we exit.
8933 - If we require CookieAuthentication, stop generating a new cookie
8934 every time we change any piece of our config.
8935 - When loading bandwidth history, do not believe any information in
8936 the future. Fixes bug 434.
8937 - When loading entry guard information, do not believe any information
8939 - When we have our clock set far in the future and generate an
8940 onion key, then re-set our clock to be correct, we should not stop
8941 the onion key from getting rotated.
8942 - Clean up torrc sample config file.
8943 - Do not automatically run configure from autogen.sh. This
8944 non-standard behavior tended to annoy people who have built other
8947 o Minor bugfixes (on 0.2.0.x):
8948 - Fix a bug with AutomapHostsOnResolve that would always cause
8949 the second request to fail. Bug reported by Kate. Bugfix on
8951 - Fix a bug in ADDRMAP controller replies that would sometimes
8952 try to print a NULL. Patch from tup.
8953 - Read v3 directory authority keys from the right location.
8954 - Numerous bugfixes to directory voting code.
8957 Changes in version 0.1.2.16 - 2007-08-01
8958 Tor 0.1.2.16 fixes a critical security vulnerability that allows a
8959 remote attacker in certain situations to rewrite the user's torrc
8960 configuration file. This can completely compromise anonymity of users
8961 in most configurations, including those running the Vidalia bundles,
8962 TorK, etc. Or worse.
8964 o Major security fixes:
8965 - Close immediately after missing authentication on control port;
8966 do not allow multiple authentication attempts.
8969 Changes in version 0.2.0.4-alpha - 2007-08-01
8970 This fourth development snapshot fixes a critical security vulnerability
8971 for most users, specifically those running Vidalia, TorK, etc. Everybody
8972 should upgrade to either 0.1.2.16 or 0.2.0.4-alpha.
8974 o Major security fixes:
8975 - Close immediately after missing authentication on control port;
8976 do not allow multiple authentication attempts.
8978 o Major bugfixes (compilation):
8979 - Fix win32 compilation: apparently IN_ADDR and IN6_ADDR are already
8982 o Minor features (performance):
8983 - Be even more aggressive about releasing RAM from small
8984 empty buffers. Thanks to our free-list code, this shouldn't be too
8985 performance-intensive.
8986 - Disable sentinel-based debugging for buffer code: we squashed all
8987 the bugs that this was supposed to detect a long time ago, and
8988 now its only effect is to change our buffer sizes from nice
8989 powers of two (which platform mallocs tend to like) to values
8990 slightly over powers of two (which make some platform mallocs sad).
8991 - Log malloc statistics from mallinfo() on platforms where it
8995 Changes in version 0.2.0.3-alpha - 2007-07-29
8996 This third development snapshot introduces new experimental
8997 blocking-resistance features and a preliminary version of the v3
8998 directory voting design, and includes many other smaller features
9002 - The first pieces of our "bridge" design for blocking-resistance
9003 are implemented. People can run bridge directory authorities;
9004 people can run bridges; and people can configure their Tor clients
9005 with a set of bridges to use as the first hop into the Tor network.
9006 See http://archives.seul.org/or/talk/Jul-2007/msg00249.html for
9008 - Create listener connections before we setuid to the configured
9009 User and Group. Now non-Windows users can choose port values
9010 under 1024, start Tor as root, and have Tor bind those ports
9011 before it changes to another UID. (Windows users could already
9013 - Added a new ConstrainedSockets config option to set SO_SNDBUF and
9014 SO_RCVBUF on TCP sockets. Hopefully useful for Tor servers running
9015 on "vserver" accounts. (Patch from coderman.)
9016 - Be even more aggressive about separating local traffic from relayed
9017 traffic when RelayBandwidthRate is set. (Refines proposal 111.)
9019 o Major features (experimental):
9020 - First cut of code for "v3 dir voting": directory authorities will
9021 vote on a common network status document rather than each publishing
9022 their own opinion. This code needs more testing and more corner-case
9023 handling before it's ready for use.
9026 - Directory authorities now call routers Fast if their bandwidth is
9027 at least 100KB/s, and consider their bandwidth adequate to be a
9028 Guard if it is at least 250KB/s, no matter the medians. This fix
9029 complements proposal 107. [Bugfix on 0.1.2.x]
9030 - Directory authorities now never mark more than 3 servers per IP as
9031 Valid and Running. (Implements proposal 109, by Kevin Bauer and
9033 - Minor change to organizationName and commonName generation
9034 procedures in TLS certificates during Tor handshakes, to invalidate
9035 some earlier censorware approaches. This is not a long-term
9036 solution, but applying it will give us a bit of time to look into
9037 the epidemiology of countermeasures as they spread.
9039 o Major bugfixes (directory):
9040 - Rewrite directory tokenization code to never run off the end of
9041 a string. Fixes bug 455. Patch from croup. [Bugfix on 0.1.2.x]
9043 o Minor features (controller):
9044 - Add a SOURCE_ADDR field to STREAM NEW events so that controllers can
9045 match requests to applications. (Patch from Robert Hogan.)
9046 - Report address and port correctly on connections to DNSPort. (Patch
9048 - Add a RESOLVE command to launch hostname lookups. (Original patch
9050 - Add GETINFO status/enough-dir-info to let controllers tell whether
9051 Tor has downloaded sufficient directory information. (Patch
9053 - You can now use the ControlSocket option to tell Tor to listen for
9054 controller connections on Unix domain sockets on systems that
9055 support them. (Patch from Peter Palfrader.)
9056 - STREAM NEW events are generated for DNSPort requests and for
9057 tunneled directory connections. (Patch from Robert Hogan.)
9058 - New "GETINFO address-mappings/*" command to get address mappings
9059 with expiry information. "addr-mappings/*" is now deprecated.
9062 o Minor features (misc):
9063 - Merge in some (as-yet-unused) IPv6 address manipulation code. (Patch
9065 - The tor-gencert tool for v3 directory authorities now creates all
9066 files as readable to the file creator only, and write-protects
9067 the authority identity key.
9068 - When dumping memory usage, list bytes used in buffer memory
9070 - When running with dmalloc, dump more stats on hup and on exit.
9071 - Directory authorities now fail quickly and (relatively) harmlessly
9072 if they generate a network status document that is somehow
9075 o Traffic load balancing improvements:
9076 - If exit bandwidth ever exceeds one third of total bandwidth, then
9077 use the correct formula to weight exit nodes when choosing paths.
9078 (Based on patch from Mike Perry.)
9079 - Choose perfectly fairly among routers when choosing by bandwidth and
9080 weighting by fraction of bandwidth provided by exits. Previously, we
9081 would choose with only approximate fairness, and correct ourselves
9082 if we ran off the end of the list. [Bugfix on 0.1.2.x]
9084 o Performance improvements:
9085 - Be more aggressive with freeing buffer RAM or putting it on the
9087 - Use Critical Sections rather than Mutexes for synchronizing threads
9088 on win32; Mutexes are heavier-weight, and designed for synchronizing
9091 o Deprecated and removed features:
9092 - RedirectExits is now deprecated.
9093 - Stop allowing address masks that do not correspond to bit prefixes.
9094 We have warned about these for a really long time; now it's time
9095 to reject them. (Patch from croup.)
9097 o Minor bugfixes (directory):
9098 - Fix another crash bug related to extra-info caching. (Bug found by
9099 Peter Palfrader.) [Bugfix on 0.2.0.2-alpha]
9100 - Directories no longer return a "304 not modified" when they don't
9101 have the networkstatus the client asked for. Also fix a memory
9102 leak when returning 304 not modified. [Bugfixes on 0.2.0.2-alpha]
9103 - We had accidentally labelled 0.1.2.x directory servers as not
9104 suitable for begin_dir requests, and had labelled no directory
9105 servers as suitable for uploading extra-info documents. [Bugfix
9108 o Minor bugfixes (dns):
9109 - Fix a crash when DNSPort is set more than once. (Patch from Robert
9110 Hogan.) [Bugfix on 0.2.0.2-alpha]
9111 - Add DNSPort connections to the global connection list, so that we
9112 can time them out correctly. (Bug found by Robert Hogan.) [Bugfix
9114 - Fix a dangling reference that could lead to a crash when DNSPort is
9115 changed or closed (Patch from Robert Hogan.) [Bugfix on
9118 o Minor bugfixes (controller):
9119 - Provide DNS expiry times in GMT, not in local time. For backward
9120 compatibility, ADDRMAP events only provide GMT expiry in an extended
9121 field. "GETINFO address-mappings" always does the right thing.
9122 - Use CRLF line endings properly in NS events.
9123 - Terminate multi-line control events properly. (Original patch
9124 from tup.) [Bugfix on 0.1.2.x-alpha]
9125 - Do not include spaces in SOURCE_ADDR fields in STREAM
9126 events. Resolves bug 472. [Bugfix on 0.2.0.x-alpha]
9129 Changes in version 0.1.2.15 - 2007-07-17
9130 Tor 0.1.2.15 fixes several crash bugs, fixes some anonymity-related
9131 problems, fixes compilation on BSD, and fixes a variety of other
9132 bugs. Everybody should upgrade.
9134 o Major bugfixes (compilation):
9135 - Fix compile on FreeBSD/NetBSD/OpenBSD. Oops.
9137 o Major bugfixes (crashes):
9138 - Try even harder not to dereference the first character after
9139 an mmap(). Reported by lodger.
9140 - Fix a crash bug in directory authorities when we re-number the
9141 routerlist while inserting a new router.
9142 - When the cached-routers file is an even multiple of the page size,
9143 don't run off the end and crash. (Fixes bug 455; based on idea
9145 - Fix eventdns.c behavior on Solaris: It is critical to include
9146 orconfig.h _before_ sys/types.h, so that we can get the expected
9147 definition of _FILE_OFFSET_BITS.
9149 o Major bugfixes (security):
9150 - Fix a possible buffer overrun when using BSD natd support. Bug
9152 - When sending destroy cells from a circuit's origin, don't include
9153 the reason for tearing down the circuit. The spec says we didn't,
9154 and now we actually don't. Reported by lodger.
9155 - Keep streamids from different exits on a circuit separate. This
9156 bug may have allowed other routers on a given circuit to inject
9157 cells into streams. Reported by lodger; fixes bug 446.
9158 - If there's a never-before-connected-to guard node in our list,
9159 never choose any guards past it. This way we don't expand our
9160 guard list unless we need to.
9162 o Minor bugfixes (guard nodes):
9163 - Weight guard selection by bandwidth, so that low-bandwidth nodes
9164 don't get overused as guards.
9166 o Minor bugfixes (directory):
9167 - Correctly count the number of authorities that recommend each
9168 version. Previously, we were under-counting by 1.
9169 - Fix a potential crash bug when we load many server descriptors at
9170 once and some of them make others of them obsolete. Fixes bug 458.
9172 o Minor bugfixes (hidden services):
9173 - Stop tearing down the whole circuit when the user asks for a
9174 connection to a port that the hidden service didn't configure.
9177 o Minor bugfixes (misc):
9178 - On Windows, we were preventing other processes from reading
9179 cached-routers while Tor was running. Reported by janbar.
9180 - Fix a possible (but very unlikely) bug in picking routers by
9181 bandwidth. Add a log message to confirm that it is in fact
9182 unlikely. Patch from lodger.
9183 - Backport a couple of memory leak fixes.
9184 - Backport miscellaneous cosmetic bugfixes.
9187 Changes in version 0.2.0.2-alpha - 2007-06-02
9188 o Major bugfixes on 0.2.0.1-alpha:
9189 - Fix an assertion failure related to servers without extra-info digests.
9190 Resolves bugs 441 and 442.
9192 o Minor features (directory):
9193 - Support "If-Modified-Since" when answering HTTP requests for
9194 directories, running-routers documents, and network-status documents.
9195 (There's no need to support it for router descriptors, since those
9196 are downloaded by descriptor digest.)
9198 o Minor build issues:
9199 - Clear up some MIPSPro compiler warnings.
9200 - When building from a tarball on a machine that happens to have SVK
9201 installed, report the micro-revision as whatever version existed
9202 in the tarball, not as "x".
9205 Changes in version 0.2.0.1-alpha - 2007-06-01
9206 This early development snapshot provides new features for people running
9207 Tor as both a client and a server (check out the new RelayBandwidth
9208 config options); lets Tor run as a DNS proxy; and generally moves us
9209 forward on a lot of fronts.
9211 o Major features, server usability:
9212 - New config options RelayBandwidthRate and RelayBandwidthBurst:
9213 a separate set of token buckets for relayed traffic. Right now
9214 relayed traffic is defined as answers to directory requests, and
9215 OR connections that don't have any local circuits on them.
9217 o Major features, client usability:
9218 - A client-side DNS proxy feature to replace the need for
9219 dns-proxy-tor: Just set "DNSPort 9999", and Tor will now listen
9220 for DNS requests on port 9999, use the Tor network to resolve them
9221 anonymously, and send the reply back like a regular DNS server.
9222 The code still only implements a subset of DNS.
9223 - Make PreferTunneledDirConns and TunnelDirConns work even when
9224 we have no cached directory info. This means Tor clients can now
9225 do all of their connections protected by TLS.
9227 o Major features, performance and efficiency:
9228 - Directory authorities accept and serve "extra info" documents for
9229 routers. These documents contain fields from router descriptors
9230 that aren't usually needed, and that use a lot of excess
9231 bandwidth. Once these fields are removed from router descriptors,
9232 the bandwidth savings should be about 60%. [Partially implements
9234 - Servers upload extra-info documents to any authority that accepts
9235 them. Authorities (and caches that have been configured to download
9236 extra-info documents) download them as needed. [Partially implements
9238 - Change the way that Tor buffers data that it is waiting to write.
9239 Instead of queueing data cells in an enormous ring buffer for each
9240 client->OR or OR->OR connection, we now queue cells on a separate
9241 queue for each circuit. This lets us use less slack memory, and
9242 will eventually let us be smarter about prioritizing different kinds
9244 - Use memory pools to allocate cells with better speed and memory
9245 efficiency, especially on platforms where malloc() is inefficient.
9246 - Stop reading on edge connections when their corresponding circuit
9247 buffers are full; start again as the circuits empty out.
9249 o Major features, other:
9250 - Add an HSAuthorityRecordStats option that hidden service authorities
9251 can use to track statistics of overall hidden service usage without
9252 logging information that would be very useful to an attacker.
9253 - Start work implementing multi-level keys for directory authorities:
9254 Add a standalone tool to generate key certificates. (Proposal 103.)
9257 - Directory authorities now call routers Stable if they have an
9258 uptime of at least 30 days, even if that's not the median uptime
9259 in the network. Implements proposal 107, suggested by Kevin Bauer
9262 o Minor fixes (resource management):
9263 - Count the number of open sockets separately from the number
9264 of active connection_t objects. This will let us avoid underusing
9265 our allocated connection limit.
9266 - We no longer use socket pairs to link an edge connection to an
9267 anonymous directory connection or a DirPort test connection.
9268 Instead, we track the link internally and transfer the data
9269 in-process. This saves two sockets per "linked" connection (at the
9270 client and at the server), and avoids the nasty Windows socketpair()
9272 - Keep unused 4k and 16k buffers on free lists, rather than wasting 8k
9273 for every single inactive connection_t. Free items from the
9274 4k/16k-buffer free lists when they haven't been used for a while.
9276 o Minor features (build):
9277 - Make autoconf search for libevent, openssl, and zlib consistently.
9278 - Update deprecated macros in configure.in.
9279 - When warning about missing headers, tell the user to let us
9280 know if the compile succeeds anyway, so we can downgrade the
9282 - Include the current subversion revision as part of the version
9283 string: either fetch it directly if we're in an SVN checkout, do
9284 some magic to guess it if we're in an SVK checkout, or use
9285 the last-detected version if we're building from a .tar.gz.
9286 Use this version consistently in log messages.
9288 o Minor features (logging):
9289 - Always prepend "Bug: " to any log message about a bug.
9290 - Put a platform string (e.g. "Linux i686") in the startup log
9291 message, so when people paste just their logs, we know if it's
9292 OpenBSD or Windows or what.
9293 - When logging memory usage, break down memory used in buffers by
9296 o Minor features (directory system):
9297 - New config option V2AuthoritativeDirectory that all directory
9298 authorities should set. This will let future authorities choose
9299 not to serve V2 directory information.
9300 - Directory authorities allow multiple router descriptors and/or extra
9301 info documents to be uploaded in a single go. This will make
9302 implementing proposal 104 simpler.
9304 o Minor features (controller):
9305 - Add a new config option __DisablePredictedCircuits designed for
9306 use by the controller, when we don't want Tor to build any circuits
9308 - Let the controller specify HOP=%d as an argument to ATTACHSTREAM,
9309 so we can exit from the middle of the circuit.
9310 - Implement "getinfo status/circuit-established".
9311 - Implement "getinfo status/version/..." so a controller can tell
9312 whether the current version is recommended, and whether any versions
9313 are good, and how many authorities agree. (Patch from shibz.)
9315 o Minor features (hidden services):
9316 - Allow multiple HiddenServicePort directives with the same virtual
9317 port; when they occur, the user is sent round-robin to one
9318 of the target ports chosen at random. Partially fixes bug 393 by
9319 adding limited ad-hoc round-robining.
9321 o Minor features (other):
9323 - Add a new AutomapHostsOnResolve option: when it is enabled, any
9324 resolve request for hosts matching a given pattern causes Tor to
9325 generate an internal virtual address mapping for that host. This
9326 allows DNSPort to work sensibly with hidden service users. By
9327 default, .exit and .onion addresses are remapped; the list of
9328 patterns can be reconfigured with AutomapHostsSuffixes.
9329 - Add an "-F" option to tor-resolve to force a resolve for a .onion
9330 address. Thanks to the AutomapHostsOnResolve option, this is no
9331 longer a completely silly thing to do.
9332 - If Tor is invoked from something that isn't a shell (e.g. Vidalia),
9333 now we expand "-f ~/.tor/torrc" correctly. Suggested by Matt Edman.
9334 - Treat "2gb" when given in torrc for a bandwidth as meaning 2gb,
9335 minus 1 byte: the actual maximum declared bandwidth.
9338 - Removed support for the old binary "version 0" controller protocol.
9339 This has been deprecated since 0.1.1, and warnings have been issued
9340 since 0.1.2. When we encounter a v0 control message, we now send
9341 back an error and close the connection.
9342 - Remove the old "dns worker" server DNS code: it hasn't been default
9343 since 0.1.2.2-alpha, and all the servers seem to be using the new
9346 o Minor bugfixes (portability):
9347 - Even though Windows is equally happy with / and \ as path separators,
9348 try to use \ consistently on Windows and / consistently on Unix: it
9349 makes the log messages nicer.
9350 - Correctly report platform name on Windows 95 OSR2 and Windows 98 SE.
9351 - Read resolv.conf files correctly on platforms where read() returns
9352 partial results on small file reads.
9354 o Minor bugfixes (directory):
9355 - Correctly enforce that elements of directory objects do not appear
9356 more often than they are allowed to appear.
9357 - When we are reporting the DirServer line we just parsed, we were
9358 logging the second stanza of the key fingerprint, not the first.
9360 o Minor bugfixes (logging):
9361 - When we hit an EOF on a log (probably because we're shutting down),
9362 don't try to remove the log from the list: just mark it as
9363 unusable. (Bulletproofs against bug 222.)
9365 o Minor bugfixes (other):
9366 - In the exitlist script, only consider the most recently published
9367 server descriptor for each server. Also, when the user requests
9368 a list of servers that _reject_ connections to a given address,
9369 explicitly exclude the IPs that also have servers that accept
9370 connections to that address. (Resolves bug 405.)
9371 - Stop allowing hibernating servers to be "stable" or "fast".
9372 - On Windows, we were preventing other processes from reading
9373 cached-routers while Tor was running. (Reported by janbar)
9374 - Make the NodeFamilies config option work. (Reported by
9375 lodger -- it has never actually worked, even though we added it
9377 - Check return values from pthread_mutex functions.
9378 - Don't save non-general-purpose router descriptors to the disk cache,
9379 because we have no way of remembering what their purpose was when
9381 - Add even more asserts to hunt down bug 417.
9382 - Build without verbose warnings even on (not-yet-released) gcc 4.2.
9383 - Fix a possible (but very unlikely) bug in picking routers by bandwidth.
9384 Add a log message to confirm that it is in fact unlikely.
9386 o Minor bugfixes (controller):
9387 - Make 'getinfo fingerprint' return a 551 error if we're not a
9388 server, so we match what the control spec claims we do. Reported
9390 - Fix a typo in an error message when extendcircuit fails that
9391 caused us to not follow the \r\n-based delimiter protocol. Reported
9394 o Code simplifications and refactoring:
9395 - Stop passing around circuit_t and crypt_path_t pointers that are
9396 implicit in other procedure arguments.
9397 - Drop the old code to choke directory connections when the
9398 corresponding OR connections got full: thanks to the cell queue
9399 feature, OR conns don't get full any more.
9400 - Make dns_resolve() handle attaching connections to circuits
9401 properly, so the caller doesn't have to.
9402 - Rename wants_to_read and wants_to_write to read/write_blocked_on_bw.
9403 - Keep the connection array as a dynamic smartlist_t, rather than as
9404 a fixed-sized array. This is important, as the number of connections
9405 is becoming increasingly decoupled from the number of sockets.
9408 Changes in version 0.1.2.14 - 2007-05-25
9409 Tor 0.1.2.14 changes the addresses of two directory authorities (this
9410 change especially affects those who serve or use hidden services),
9411 and fixes several other crash- and security-related bugs.
9413 o Directory authority changes:
9414 - Two directory authorities (moria1 and moria2) just moved to new
9415 IP addresses. This change will particularly affect those who serve
9416 or use hidden services.
9418 o Major bugfixes (crashes):
9419 - If a directory server runs out of space in the connection table
9420 as it's processing a begin_dir request, it will free the exit stream
9421 but leave it attached to the circuit, leading to unpredictable
9422 behavior. (Reported by seeess, fixes bug 425.)
9423 - Fix a bug in dirserv_remove_invalid() that would cause authorities
9424 to corrupt memory under some really unlikely scenarios.
9425 - Tighten router parsing rules. (Bugs reported by Benedikt Boss.)
9426 - Avoid segfaults when reading from mmaped descriptor file. (Reported
9429 o Major bugfixes (security):
9430 - When choosing an entry guard for a circuit, avoid using guards
9431 that are in the same family as the chosen exit -- not just guards
9432 that are exactly the chosen exit. (Reported by lodger.)
9434 o Major bugfixes (resource management):
9435 - If a directory authority is down, skip it when deciding where to get
9436 networkstatus objects or descriptors. Otherwise we keep asking
9437 every 10 seconds forever. Fixes bug 384.
9438 - Count it as a failure if we fetch a valid network-status but we
9439 don't want to keep it. Otherwise we'll keep fetching it and keep
9440 not wanting to keep it. Fixes part of bug 422.
9441 - If all of our dirservers have given us bad or no networkstatuses
9442 lately, then stop hammering them once per minute even when we
9443 think they're failed. Fixes another part of bug 422.
9446 - Actually set the purpose correctly for descriptors inserted with
9448 - When we have k non-v2 authorities in our DirServer config,
9449 we ignored the last k authorities in the list when updating our
9451 - Correctly back-off from requesting router descriptors that we are
9452 having a hard time downloading.
9453 - Read resolv.conf files correctly on platforms where read() returns
9454 partial results on small file reads.
9455 - Don't rebuild the entire router store every time we get 32K of
9456 routers: rebuild it when the journal gets very large, or when
9457 the gaps in the store get very large.
9460 - When routers publish SVN revisions in their router descriptors,
9461 authorities now include those versions correctly in networkstatus
9463 - Warn when using a version of libevent before 1.3b to run a server on
9464 OSX or BSD: these versions interact badly with userspace threads.
9467 Changes in version 0.1.2.13 - 2007-04-24
9468 This release features some major anonymity fixes, such as safer path
9469 selection; better client performance; faster bootstrapping, better
9470 address detection, and better DNS support for servers; write limiting as
9471 well as read limiting to make servers easier to run; and a huge pile of
9472 other features and bug fixes. The bundles also ship with Vidalia 0.0.11.
9474 Tor 0.1.2.13 is released in memory of Rob Levin (1955-2006), aka lilo
9475 of the Freenode IRC network, remembering his patience and vision for
9476 free speech on the Internet.
9479 - Fix a memory leak when we ask for "all" networkstatuses and we
9480 get one we don't recognize.
9481 - Add more asserts to hunt down bug 417.
9482 - Disable kqueue on OS X 10.3 and earlier, to fix bug 371.
9485 Changes in version 0.1.2.12-rc - 2007-03-16
9487 - Fix an infinite loop introduced in 0.1.2.7-alpha when we serve
9488 directory information requested inside Tor connections (i.e. via
9489 begin_dir cells). It only triggered when the same connection was
9490 serving other data at the same time. Reported by seeess.
9493 - When creating a circuit via the controller, send a 'launched'
9494 event when we're done, so we follow the spec better.
9497 Changes in version 0.1.2.11-rc - 2007-03-15
9498 o Minor bugfixes (controller), reported by daejees:
9499 - Correct the control spec to match how the code actually responds
9500 to 'getinfo addr-mappings/*'.
9501 - The control spec described a GUARDS event, but the code
9502 implemented a GUARD event. Standardize on GUARD, but let people
9506 Changes in version 0.1.2.10-rc - 2007-03-07
9507 o Major bugfixes (Windows):
9508 - Do not load the NT services library functions (which may not exist)
9509 just to detect if we're a service trying to shut down. Now we run
9510 on Win98 and friends again.
9512 o Minor bugfixes (other):
9513 - Clarify a couple of log messages.
9514 - Fix a misleading socks5 error number.
9517 Changes in version 0.1.2.9-rc - 2007-03-02
9518 o Major bugfixes (Windows):
9519 - On MinGW, use "%I64u" to printf/scanf 64-bit integers, instead
9520 of the usual GCC "%llu". This prevents a bug when saving 64-bit
9521 int configuration values: the high-order 32 bits would get
9522 truncated. In particular, we were being bitten by the default
9523 MaxAdvertisedBandwidth of 128 TB turning into 0. (Fixes bug 400
9524 and maybe also bug 397.)
9526 o Minor bugfixes (performance):
9527 - Use OpenSSL's AES implementation on platforms where it's faster.
9528 This could save us as much as 10% CPU usage.
9530 o Minor bugfixes (server):
9531 - Do not rotate onion key immediately after setting it for the first
9534 o Minor bugfixes (directory authorities):
9535 - Stop calling servers that have been hibernating for a long time
9536 "stable". Also, stop letting hibernating or obsolete servers affect
9537 uptime and bandwidth cutoffs.
9538 - Stop listing hibernating servers in the v1 directory.
9540 o Minor bugfixes (hidden services):
9541 - Upload hidden service descriptors slightly less often, to reduce
9542 load on authorities.
9544 o Minor bugfixes (other):
9545 - Fix an assert that could trigger if a controller quickly set then
9546 cleared EntryNodes. Bug found by Udo van den Heuvel.
9547 - On architectures where sizeof(int)>4, still clamp declarable bandwidth
9549 - Fix a potential race condition in the rpm installer. Found by
9551 - Try to fix eventdns warnings once and for all: do not treat a dns rcode
9552 of 2 as indicating that the server is completely bad; it sometimes
9553 means that the server is just bad for the request in question. (may fix
9554 the last of bug 326.)
9555 - Disable encrypted directory connections when we don't have a server
9556 descriptor for the destination. We'll get this working again in
9560 Changes in version 0.1.2.8-beta - 2007-02-26
9561 o Major bugfixes (crashes):
9562 - Stop crashing when the controller asks us to resetconf more than
9563 one config option at once. (Vidalia 0.0.11 does this.)
9564 - Fix a crash that happened on Win98 when we're given command-line
9565 arguments: don't try to load NT service functions from advapi32.dll
9566 except when we need them. (Bug introduced in 0.1.2.7-alpha;
9568 - Fix a longstanding obscure crash bug that could occur when
9569 we run out of DNS worker processes. (Resolves bug 390.)
9571 o Major bugfixes (hidden services):
9572 - Correctly detect whether hidden service descriptor downloads are
9573 in-progress. (Suggested by Karsten Loesing; fixes bug 399.)
9575 o Major bugfixes (accounting):
9576 - When we start during an accounting interval before it's time to wake
9577 up, remember to wake up at the correct time. (May fix bug 342.)
9579 o Minor bugfixes (controller):
9580 - Give the controller END_STREAM_REASON_DESTROY events _before_ we
9581 clear the corresponding on_circuit variable, and remember later
9582 that we don't need to send a redundant CLOSED event. Resolves part
9584 - Report events where a resolve succeeded or where we got a socks
9585 protocol error correctly, rather than calling both of them
9587 - Change reported stream target addresses to IP consistently when
9588 we finally get the IP from an exit node.
9589 - Send log messages to the controller even if they happen to be very
9592 o Minor bugfixes (other):
9593 - Display correct results when reporting which versions are
9594 recommended, and how recommended they are. (Resolves bug 383.)
9595 - Improve our estimates for directory bandwidth to be less random:
9596 guess that an unrecognized directory will have the average bandwidth
9597 from all known directories, not that it will have the average
9598 bandwidth from those directories earlier than it on the list.
9599 - If we start a server with ClientOnly 1, then set ClientOnly to 0
9600 and hup, stop triggering an assert based on an empty onion_key.
9601 - On platforms with no working mmap() equivalent, don't warn the
9602 user when cached-routers doesn't exist.
9603 - Warn the user when mmap() [or its equivalent] fails for some reason
9604 other than file-not-found.
9605 - Don't warn the user when cached-routers.new doesn't exist: that's
9606 perfectly fine when starting up for the first time.
9607 - When EntryNodes are configured, rebuild the guard list to contain,
9608 in order: the EntryNodes that were guards before; the rest of the
9609 EntryNodes; the nodes that were guards before.
9610 - Mask out all signals in sub-threads; only the libevent signal
9611 handler should be processing them. This should prevent some crashes
9612 on some machines using pthreads. (Patch from coderman.)
9613 - Fix switched arguments on memset in the implementation of
9614 tor_munmap() for systems with no mmap() call.
9615 - When Tor receives a router descriptor that it asked for, but
9616 no longer wants (because it has received fresh networkstatuses
9617 in the meantime), do not warn the user. Cache the descriptor if
9618 we're a cache; drop it if we aren't.
9619 - Make earlier entry guards _really_ get retried when the network
9621 - On a malformed DNS reply, always give an error to the corresponding
9623 - Build with recent libevents on platforms that do not define the
9624 nonstandard types "u_int8_t" and friends.
9626 o Minor features (controller):
9627 - Warn the user when an application uses the obsolete binary v0
9628 control protocol. We're planning to remove support for it during
9629 the next development series, so it's good to give people some
9631 - Add STREAM_BW events to report per-entry-stream bandwidth
9632 use. (Patch from Robert Hogan.)
9633 - Rate-limit SIGNEWNYM signals in response to controllers that
9634 impolitely generate them for every single stream. (Patch from
9635 mwenge; closes bug 394.)
9636 - Make REMAP stream events have a SOURCE (cache or exit), and
9637 make them generated in every case where we get a successful
9638 connected or resolved cell.
9640 o Minor bugfixes (performance):
9641 - Call router_have_min_dir_info half as often. (This is showing up in
9642 some profiles, but not others.)
9643 - When using GCC, make log_debug never get called at all, and its
9644 arguments never get evaluated, when no debug logs are configured.
9645 (This is showing up in some profiles, but not others.)
9648 - Remove some never-implemented options. Mark PathlenCoinWeight as
9650 - Implement proposal 106: Stop requiring clients to have well-formed
9651 certificates; stop checking nicknames in certificates. (Clients
9652 have certificates so that they can look like Tor servers, but in
9653 the future we might want to allow them to look like regular TLS
9654 clients instead. Nicknames in certificates serve no purpose other
9655 than making our protocol easier to recognize on the wire.)
9656 - Revise messages on handshake failure again to be even more clear about
9657 which are incoming connections and which are outgoing.
9658 - Discard any v1 directory info that's over 1 month old (for
9659 directories) or over 1 week old (for running-routers lists).
9660 - Do not warn when individual nodes in the configuration's EntryNodes,
9661 ExitNodes, etc are down: warn only when all possible nodes
9662 are down. (Fixes bug 348.)
9663 - Always remove expired routers and networkstatus docs before checking
9664 whether we have enough information to build circuits. (Fixes
9666 - Put a lower-bound on MaxAdvertisedBandwidth.
9669 Changes in version 0.1.2.7-alpha - 2007-02-06
9670 o Major bugfixes (rate limiting):
9671 - Servers decline directory requests much more aggressively when
9672 they're low on bandwidth. Otherwise they end up queueing more and
9673 more directory responses, which can't be good for latency.
9674 - But never refuse directory requests from local addresses.
9675 - Fix a memory leak when sending a 503 response for a networkstatus
9677 - Be willing to read or write on local connections (e.g. controller
9678 connections) even when the global rate limiting buckets are empty.
9679 - If our system clock jumps back in time, don't publish a negative
9680 uptime in the descriptor. Also, don't let the global rate limiting
9681 buckets go absurdly negative.
9682 - Flush local controller connection buffers periodically as we're
9683 writing to them, so we avoid queueing 4+ megabytes of data before
9686 o Major bugfixes (NT services):
9687 - Install as NT_AUTHORITY\LocalService rather than as SYSTEM; add a
9688 command-line flag so that admins can override the default by saying
9689 "tor --service install --user "SomeUser"". This will not affect
9690 existing installed services. Also, warn the user that the service
9691 will look for its configuration file in the service user's
9692 %appdata% directory. (We can't do the 'hardwire the user's appdata
9693 directory' trick any more, since we may not have read access to that
9696 o Major bugfixes (other):
9697 - Previously, we would cache up to 16 old networkstatus documents
9698 indefinitely, if they came from nontrusted authorities. Now we
9699 discard them if they are more than 10 days old.
9700 - Fix a crash bug in the presence of DNS hijacking (reported by Andrew
9702 - Detect and reject malformed DNS responses containing circular
9704 - If exits are rare enough that we're not marking exits as guards,
9705 ignore exit bandwidth when we're deciding the required bandwidth
9707 - When we're handling a directory connection tunneled over Tor,
9708 don't fill up internal memory buffers with all the data we want
9709 to tunnel; instead, only add it if the OR connection that will
9710 eventually receive it has some room for it. (This can lead to
9711 slowdowns in tunneled dir connections; a better solution will have
9714 o Minor bugfixes (dns):
9715 - Add some defensive programming to eventdns.c in an attempt to catch
9716 possible memory-stomping bugs.
9717 - Detect and reject DNS replies containing IPv4 or IPv6 records with
9718 an incorrect number of bytes. (Previously, we would ignore the
9720 - Fix as-yet-unused reverse IPv6 lookup code so it sends nybbles
9721 in the correct order, and doesn't crash.
9722 - Free memory held in recently-completed DNS lookup attempts on exit.
9723 This was not a memory leak, but may have been hiding memory leaks.
9724 - Handle TTL values correctly on reverse DNS lookups.
9725 - Treat failure to parse resolv.conf as an error.
9727 o Minor bugfixes (other):
9728 - Fix crash with "tor --list-fingerprint" (reported by seeess).
9729 - When computing clock skew from directory HTTP headers, consider what
9730 time it was when we finished asking for the directory, not what
9732 - Expire socks connections if they spend too long waiting for the
9733 handshake to finish. Previously we would let them sit around for
9734 days, if the connecting application didn't close them either.
9735 - And if the socks handshake hasn't started, don't send a
9736 "DNS resolve socks failed" handshake reply; just close it.
9737 - Stop using C functions that OpenBSD's linker doesn't like.
9738 - Don't launch requests for descriptors unless we have networkstatuses
9739 from at least half of the authorities. This delays the first
9740 download slightly under pathological circumstances, but can prevent
9741 us from downloading a bunch of descriptors we don't need.
9742 - Do not log IPs with TLS failures for incoming TLS
9743 connections. (Fixes bug 382.)
9744 - If the user asks to use invalid exit nodes, be willing to use
9746 - Stop using the reserved ac_cv namespace in our configure script.
9747 - Call stat() slightly less often; use fstat() when possible.
9748 - Refactor the way we handle pending circuits when an OR connection
9749 completes or fails, in an attempt to fix a rare crash bug.
9750 - Only rewrite a conn's address based on X-Forwarded-For: headers
9751 if it's a parseable public IP address; and stop adding extra quotes
9752 to the resulting address.
9755 - Weight directory requests by advertised bandwidth. Now we can
9756 let servers enable write limiting but still allow most clients to
9757 succeed at their directory requests. (We still ignore weights when
9758 choosing a directory authority; I hope this is a feature.)
9761 - Create a new file ReleaseNotes which was the old ChangeLog. The
9762 new ChangeLog file now includes the summaries for all development
9764 - Check for addresses with invalid characters at the exit as well
9765 as at the client, and warn less verbosely when they fail. You can
9766 override this by setting ServerDNSAllowNonRFC953Addresses to 1.
9767 - Adapt a patch from goodell to let the contrib/exitlist script
9768 take arguments rather than require direct editing.
9769 - Inform the server operator when we decide not to advertise a
9770 DirPort due to AccountingMax enabled or a low BandwidthRate. It
9771 was confusing Zax, so now we're hopefully more helpful.
9772 - Bring us one step closer to being able to establish an encrypted
9773 directory tunnel without knowing a descriptor first. Still not
9774 ready yet. As part of the change, now assume we can use a
9775 create_fast cell if we don't know anything about a router.
9776 - Allow exit nodes to use nameservers running on ports other than 53.
9777 - Servers now cache reverse DNS replies.
9778 - Add an --ignore-missing-torrc command-line option so that we can
9779 get the "use sensible defaults if the configuration file doesn't
9780 exist" behavior even when specifying a torrc location on the command
9783 o Minor features (controller):
9784 - Track reasons for OR connection failure; make these reasons
9785 available via the controller interface. (Patch from Mike Perry.)
9786 - Add a SOCKS_BAD_HOSTNAME client status event so controllers
9787 can learn when clients are sending malformed hostnames to Tor.
9788 - Clean up documentation for controller status events.
9789 - Add a REMAP status to stream events to note that a stream's
9790 address has changed because of a cached address or a MapAddress
9794 Changes in version 0.1.2.6-alpha - 2007-01-09
9796 - Fix an assert error introduced in 0.1.2.5-alpha: if a single TLS
9797 connection handles more than 4 gigs in either direction, we crash.
9798 - Fix an assert error introduced in 0.1.2.5-alpha: if we're an
9799 advertised exit node, somebody might try to exit from us when
9800 we're bootstrapping and before we've built our descriptor yet.
9801 Refuse the connection rather than crashing.
9804 - Warn if we (as a server) find that we've resolved an address that we
9805 weren't planning to resolve.
9806 - Warn that using select() on any libevent version before 1.1 will be
9807 unnecessarily slow (even for select()).
9808 - Flush ERR-level controller status events just like we currently
9809 flush ERR-level log events, so that a Tor shutdown doesn't prevent
9810 the controller from learning about current events.
9812 o Minor features (more controller status events):
9813 - Implement EXTERNAL_ADDRESS server status event so controllers can
9814 learn when our address changes.
9815 - Implement BAD_SERVER_DESCRIPTOR server status event so controllers
9816 can learn when directories reject our descriptor.
9817 - Implement SOCKS_UNKNOWN_PROTOCOL client status event so controllers
9818 can learn when a client application is speaking a non-socks protocol
9820 - Implement DANGEROUS_SOCKS client status event so controllers
9821 can learn when a client application is leaking DNS addresses.
9822 - Implement BUG general status event so controllers can learn when
9823 Tor is unhappy about its internal invariants.
9824 - Implement CLOCK_SKEW general status event so controllers can learn
9825 when Tor thinks the system clock is set incorrectly.
9826 - Implement GOOD_SERVER_DESCRIPTOR and ACCEPTED_SERVER_DESCRIPTOR
9827 server status events so controllers can learn when their descriptors
9828 are accepted by a directory.
9829 - Implement CHECKING_REACHABILITY and REACHABILITY_{SUCCEEDED|FAILED}
9830 server status events so controllers can learn about Tor's progress in
9831 deciding whether it's reachable from the outside.
9832 - Implement BAD_LIBEVENT general status event so controllers can learn
9833 when we have a version/method combination in libevent that needs to
9835 - Implement NAMESERVER_STATUS, NAMESERVER_ALL_DOWN, DNS_HIJACKED,
9836 and DNS_USELESS server status events so controllers can learn
9837 about changes to DNS server status.
9839 o Minor features (directory):
9840 - Authorities no longer recommend exits as guards if this would shift
9841 too much load to the exit nodes.
9844 Changes in version 0.1.2.5-alpha - 2007-01-06
9846 - Enable write limiting as well as read limiting. Now we sacrifice
9847 capacity if we're pushing out lots of directory traffic, rather
9848 than overrunning the user's intended bandwidth limits.
9849 - Include TLS overhead when counting bandwidth usage; previously, we
9850 would count only the bytes sent over TLS, but not the bytes used
9852 - Support running the Tor service with a torrc not in the same
9853 directory as tor.exe and default to using the torrc located in
9854 the %appdata%\Tor\ of the user who installed the service. Patch
9856 - Servers now check for the case when common DNS requests are going to
9857 wildcarded addresses (i.e. all getting the same answer), and change
9858 their exit policy to reject *:* if it's happening.
9859 - Implement BEGIN_DIR cells, so we can connect to the directory
9860 server via TLS to do encrypted directory requests rather than
9861 plaintext. Enable via the TunnelDirConns and PreferTunneledDirConns
9862 config options if you like.
9864 o Minor features (config and docs):
9865 - Start using the state file to store bandwidth accounting data:
9866 the bw_accounting file is now obsolete. We'll keep generating it
9867 for a while for people who are still using 0.1.2.4-alpha.
9868 - Try to batch changes to the state file so that we do as few
9869 disk writes as possible while still storing important things in
9871 - The state file and the bw_accounting file get saved less often when
9872 the AvoidDiskWrites config option is set.
9873 - Make PIDFile work on Windows (untested).
9874 - Add internal descriptions for a bunch of configuration options:
9875 accessible via controller interface and in comments in saved
9877 - Reject *:563 (NNTPS) in the default exit policy. We already reject
9878 NNTP by default, so this seems like a sensible addition.
9879 - Clients now reject hostnames with invalid characters. This should
9880 avoid some inadvertent info leaks. Add an option
9881 AllowNonRFC953Hostnames to disable this behavior, in case somebody
9882 is running a private network with hosts called @, !, and #.
9883 - Add a maintainer script to tell us which options are missing
9884 documentation: "make check-docs".
9885 - Add a new address-spec.txt document to describe our special-case
9886 addresses: .exit, .onion, and .noconnnect.
9888 o Minor features (DNS):
9889 - Ongoing work on eventdns infrastructure: now it has dns server
9890 and ipv6 support. One day Tor will make use of it.
9891 - Add client-side caching for reverse DNS lookups.
9892 - Add support to tor-resolve tool for reverse lookups and SOCKS5.
9893 - When we change nameservers or IP addresses, reset and re-launch
9894 our tests for DNS hijacking.
9896 o Minor features (directory):
9897 - Authorities now specify server versions in networkstatus. This adds
9898 about 2% to the size of compressed networkstatus docs, and allows
9899 clients to tell which servers support BEGIN_DIR and which don't.
9900 The implementation is forward-compatible with a proposed future
9901 protocol version scheme not tied to Tor versions.
9902 - DirServer configuration lines now have an orport= option so
9903 clients can open encrypted tunnels to the authorities without
9904 having downloaded their descriptors yet. Enabled for moria1,
9905 moria2, tor26, and lefkada now in the default configuration.
9906 - Directory servers are more willing to send a 503 "busy" if they
9907 are near their write limit, especially for v1 directory requests.
9908 Now they can use their limited bandwidth for actual Tor traffic.
9909 - Clients track responses with status 503 from dirservers. After a
9910 dirserver has given us a 503, we try not to use it until an hour has
9911 gone by, or until we have no dirservers that haven't given us a 503.
9912 - When we get a 503 from a directory, and we're not a server, we don't
9913 count the failure against the total number of failures allowed
9914 for the thing we're trying to download.
9915 - Report X-Your-Address-Is correctly from tunneled directory
9916 connections; don't report X-Your-Address-Is when it's an internal
9917 address; and never believe reported remote addresses when they're
9919 - Protect against an unlikely DoS attack on directory servers.
9920 - Add a BadDirectory flag to network status docs so that authorities
9921 can (eventually) tell clients about caches they believe to be
9924 o Minor features (controller):
9925 - Have GETINFO dir/status/* work on hosts with DirPort disabled.
9926 - Reimplement GETINFO so that info/names stays in sync with the
9928 - Implement "GETINFO fingerprint".
9929 - Implement "SETEVENTS GUARD" so controllers can get updates on
9930 entry guard status as it changes.
9932 o Minor features (clean up obsolete pieces):
9933 - Remove some options that have been deprecated since at least
9934 0.1.0.x: AccountingMaxKB, LogFile, DebugLogFile, LogLevel, and
9935 SysLog. Use AccountingMax instead of AccountingMaxKB, and use Log
9937 - We no longer look for identity and onion keys in "identity.key" and
9938 "onion.key" -- these were replaced by secret_id_key and
9939 secret_onion_key in 0.0.8pre1.
9940 - We no longer require unrecognized directory entries to be
9943 o Major bugfixes (security):
9944 - Stop sending the HttpProxyAuthenticator string to directory
9945 servers when directory connections are tunnelled through Tor.
9946 - Clients no longer store bandwidth history in the state file.
9947 - Do not log introduction points for hidden services if SafeLogging
9949 - When generating bandwidth history, round down to the nearest
9950 1k. When storing accounting data, round up to the nearest 1k.
9951 - When we're running as a server, remember when we last rotated onion
9952 keys, so that we will rotate keys once they're a week old even if
9953 we never stay up for a week ourselves.
9955 o Major bugfixes (other):
9956 - Fix a longstanding bug in eventdns that prevented the count of
9957 timed-out resolves from ever being reset. This bug caused us to
9958 give up on a nameserver the third time it timed out, and try it
9959 10 seconds later... and to give up on it every time it timed out
9961 - Take out the '5 second' timeout from the connection retry
9962 schedule. Now the first connect attempt will wait a full 10
9963 seconds before switching to a new circuit. Perhaps this will help
9964 a lot. Based on observations from Mike Perry.
9965 - Fix a bug on the Windows implementation of tor_mmap_file() that
9966 would prevent the cached-routers file from ever loading. Reported
9970 - Fix an assert failure when a directory authority sets
9971 AuthDirRejectUnlisted and then receives a descriptor from an
9972 unlisted router. Reported by seeess.
9973 - Avoid a double-free when parsing malformed DirServer lines.
9974 - Fix a bug when a BSD-style PF socket is first used. Patch from
9976 - Fix a bug in 0.1.2.2-alpha that prevented clients from asking
9977 to resolve an address at a given exit node even when they ask for
9979 - Servers no longer ever list themselves in their "family" line,
9980 even if configured to do so. This makes it easier to configure
9981 family lists conveniently.
9982 - When running as a server, don't fall back to 127.0.0.1 when no
9983 nameservers are configured in /etc/resolv.conf; instead, make the
9984 user fix resolv.conf or specify nameservers explicitly. (Resolves
9986 - Stop accepting certain malformed ports in configured exit policies.
9987 - Don't re-write the fingerprint file every restart, unless it has
9989 - Stop warning when a single nameserver fails: only warn when _all_ of
9990 our nameservers have failed. Also, when we only have one nameserver,
9991 raise the threshold for deciding that the nameserver is dead.
9992 - Directory authorities now only decide that routers are reachable
9993 if their identity keys are as expected.
9994 - When the user uses bad syntax in the Log config line, stop
9995 suggesting other bad syntax as a replacement.
9996 - Correctly detect ipv6 DNS capability on OpenBSD.
9998 o Minor bugfixes (controller):
9999 - Report the circuit number correctly in STREAM CLOSED events. Bug
10000 reported by Mike Perry.
10001 - Do not report bizarre values for results of accounting GETINFOs
10002 when the last second's write or read exceeds the allotted bandwidth.
10003 - Report "unrecognized key" rather than an empty string when the
10004 controller tries to fetch a networkstatus that doesn't exist.
10007 Changes in version 0.1.1.26 - 2006-12-14
10008 o Security bugfixes:
10009 - Stop sending the HttpProxyAuthenticator string to directory
10010 servers when directory connections are tunnelled through Tor.
10011 - Clients no longer store bandwidth history in the state file.
10012 - Do not log introduction points for hidden services if SafeLogging
10016 - Fix an assert failure when a directory authority sets
10017 AuthDirRejectUnlisted and then receives a descriptor from an
10018 unlisted router (reported by seeess).
10021 Changes in version 0.1.2.4-alpha - 2006-12-03
10023 - Add support for using natd; this allows FreeBSDs earlier than
10024 5.1.2 to have ipfw send connections through Tor without using
10025 SOCKS. (Patch from Zajcev Evgeny with tweaks from tup.)
10028 - Make all connections to addresses of the form ".noconnect"
10029 immediately get closed. This lets application/controller combos
10030 successfully test whether they're talking to the same Tor by
10031 watching for STREAM events.
10032 - Make cross.sh cross-compilation script work even when autogen.sh
10033 hasn't been run. (Patch from Michael Mohr.)
10034 - Statistics dumped by -USR2 now include a breakdown of public key
10035 operations, for profiling.
10038 - Fix a major leak when directory authorities parse their
10039 approved-routers list, a minor memory leak when we fail to pick
10040 an exit node, and a few rare leaks on errors.
10041 - Handle TransPort connections even when the server sends data before
10042 the client sends data. Previously, the connection would just hang
10043 until the client sent data. (Patch from tup based on patch from
10045 - Avoid assert failure when our cached-routers file is empty on
10049 - Don't log spurious warnings when we see a circuit close reason we
10050 don't recognize; it's probably just from a newer version of Tor.
10051 - Have directory authorities allow larger amounts of drift in uptime
10052 without replacing the server descriptor: previously, a server that
10053 restarted every 30 minutes could have 48 "interesting" descriptors
10055 - Start linking to the Tor specification and Tor reference manual
10056 correctly in the Windows installer.
10057 - Add Vidalia to the OS X uninstaller script, so when we uninstall
10058 Tor/Privoxy we also uninstall Vidalia.
10059 - Resume building on Irix64, and fix a lot of warnings from its
10060 MIPSpro C compiler.
10061 - Don't corrupt last_guessed_ip in router_new_address_suggestion()
10062 when we're running as a client.
10065 Changes in version 0.1.1.25 - 2006-11-04
10067 - When a client asks us to resolve (rather than connect to)
10068 an address, and we have a cached answer, give them the cached
10069 answer. Previously, we would give them no answer at all.
10070 - We were building exactly the wrong circuits when we predict
10071 hidden service requirements, meaning Tor would have to build all
10072 its circuits on demand.
10073 - If none of our live entry guards have a high uptime, but we
10074 require a guard with a high uptime, try adding a new guard before
10075 we give up on the requirement. This patch should make long-lived
10076 connections more stable on average.
10077 - When testing reachability of our DirPort, don't launch new
10078 tests when there's already one in progress -- unreachable
10079 servers were stacking up dozens of testing streams.
10081 o Security bugfixes:
10082 - When the user sends a NEWNYM signal, clear the client-side DNS
10083 cache too. Otherwise we continue to act on previous information.
10086 - Avoid a memory corruption bug when creating a hash table for
10088 - Avoid possibility of controller-triggered crash when misusing
10089 certain commands from a v0 controller on platforms that do not
10090 handle printf("%s",NULL) gracefully.
10091 - Avoid infinite loop on unexpected controller input.
10092 - Don't log spurious warnings when we see a circuit close reason we
10093 don't recognize; it's probably just from a newer version of Tor.
10094 - Add Vidalia to the OS X uninstaller script, so when we uninstall
10095 Tor/Privoxy we also uninstall Vidalia.
10098 Changes in version 0.1.2.3-alpha - 2006-10-29
10100 - Prepare for servers to publish descriptors less often: never
10101 discard a descriptor simply for being too old until either it is
10102 recommended by no authorities, or until we get a better one for
10103 the same router. Make caches consider retaining old recommended
10104 routers for even longer.
10105 - If most authorities set a BadExit flag for a server, clients
10106 don't think of it as a general-purpose exit. Clients only consider
10107 authorities that advertise themselves as listing bad exits.
10108 - Directory servers now provide 'Pragma: no-cache' and 'Expires'
10109 headers for content, so that we can work better in the presence of
10110 caching HTTP proxies.
10111 - Allow authorities to list nodes as bad exits by fingerprint or by
10114 o Minor features, controller:
10115 - Add a REASON field to CIRC events; for backward compatibility, this
10116 field is sent only to controllers that have enabled the extended
10117 event format. Also, add additional reason codes to explain why
10118 a given circuit has been destroyed or truncated. (Patches from
10120 - Add a REMOTE_REASON field to extended CIRC events to tell the
10121 controller about why a remote OR told us to close a circuit.
10122 - Stream events also now have REASON and REMOTE_REASON fields,
10123 working much like those for circuit events.
10124 - There's now a GETINFO ns/... field so that controllers can ask Tor
10125 about the current status of a router.
10126 - A new event type "NS" to inform a controller when our opinion of
10127 a router's status has changed.
10128 - Add a GETINFO events/names and GETINFO features/names so controllers
10129 can tell which events and features are supported.
10130 - A new CLEARDNSCACHE signal to allow controllers to clear the
10131 client-side DNS cache without expiring circuits.
10133 o Security bugfixes:
10134 - When the user sends a NEWNYM signal, clear the client-side DNS
10135 cache too. Otherwise we continue to act on previous information.
10138 - Avoid sending junk to controllers or segfaulting when a controller
10139 uses EVENT_NEW_DESC with verbose nicknames.
10140 - Stop triggering asserts if the controller tries to extend hidden
10141 service circuits (reported by mwenge).
10142 - Avoid infinite loop on unexpected controller input.
10143 - When the controller does a "GETINFO network-status", tell it
10144 about even those routers whose descriptors are very old, and use
10145 long nicknames where appropriate.
10146 - Change NT service functions to be loaded on demand. This lets us
10147 build with MinGW without breaking Tor for Windows 98 users.
10148 - Do DirPort reachability tests less often, since a single test
10149 chews through many circuits before giving up.
10150 - In the hidden service example in torrc.sample, stop recommending
10151 esoteric and discouraged hidden service options.
10152 - When stopping an NT service, wait up to 10 sec for it to actually
10153 stop. Patch from Matt Edman; resolves bug 295.
10154 - Fix handling of verbose nicknames with ORCONN controller events:
10155 make them show up exactly when requested, rather than exactly when
10157 - When reporting verbose nicknames in entry_guards_getinfo(), avoid
10158 printing a duplicate "$" in the keys we send (reported by mwenge).
10159 - Correctly set maximum connection limit on Cygwin. (This time
10161 - Try to detect Windows correctly when cross-compiling.
10162 - Detect the size of the routers file correctly even if it is
10163 corrupted (on systems without mmap) or not page-aligned (on systems
10164 with mmap). This bug was harmless.
10165 - Sometimes we didn't bother sending a RELAY_END cell when an attempt
10166 to open a stream fails; now we do in more cases. This should
10167 make clients able to find a good exit faster in some cases, since
10168 unhandleable requests will now get an error rather than timing out.
10169 - Resolve two memory leaks when rebuilding the on-disk router cache
10170 (reported by fookoowa).
10171 - Clean up minor code warnings suggested by the MIPSpro C compiler,
10172 and reported by some Centos users.
10173 - Controller signals now work on non-Unix platforms that don't define
10174 SIGUSR1 and SIGUSR2 the way we expect.
10175 - Patch from Michael Mohr to contrib/cross.sh, so it checks more
10176 values before failing, and always enables eventdns.
10177 - Libevent-1.2 exports, but does not define in its headers, strlcpy.
10178 Try to fix this in configure.in by checking for most functions
10179 before we check for libevent.
10182 Changes in version 0.1.2.2-alpha - 2006-10-07
10184 - Make our async eventdns library on-by-default for Tor servers,
10185 and plan to deprecate the separate dnsworker threads.
10186 - Add server-side support for "reverse" DNS lookups (using PTR
10187 records so clients can determine the canonical hostname for a given
10188 IPv4 address). Only supported by servers using eventdns; servers
10189 now announce in their descriptors whether they support eventdns.
10190 - Specify and implement client-side SOCKS5 interface for reverse DNS
10191 lookups (see doc/socks-extensions.txt).
10192 - Add a BEGIN_DIR relay cell type for an easier in-protocol way to
10193 connect to directory servers through Tor. Previously, clients needed
10194 to find Tor exits to make private connections to directory servers.
10195 - Avoid choosing Exit nodes for entry or middle hops when the
10196 total bandwidth available from non-Exit nodes is much higher than
10197 the total bandwidth available from Exit nodes.
10198 - Workaround for name servers (like Earthlink's) that hijack failing
10199 DNS requests and replace the no-such-server answer with a "helpful"
10200 redirect to an advertising-driven search portal. Also work around
10201 DNS hijackers who "helpfully" decline to hijack known-invalid
10202 RFC2606 addresses. Config option "ServerDNSDetectHijacking 0"
10203 lets you turn it off.
10204 - Send out a burst of long-range padding cells once we've established
10205 that we're reachable. Spread them over 4 circuits, so hopefully
10206 a few will be fast. This exercises our bandwidth and bootstraps
10207 us into the directory more quickly.
10209 o New/improved config options:
10210 - Add new config option "ResolvConf" to let the server operator
10211 choose an alternate resolve.conf file when using eventdns.
10212 - Add an "EnforceDistinctSubnets" option to control our "exclude
10213 servers on the same /16" behavior. It's still on by default; this
10214 is mostly for people who want to operate private test networks with
10215 all the machines on the same subnet.
10216 - If one of our entry guards is on the ExcludeNodes list, or the
10217 directory authorities don't think it's a good guard, treat it as
10218 if it were unlisted: stop using it as a guard, and throw it off
10219 the guards list if it stays that way for a long time.
10220 - Allow directory authorities to be marked separately as authorities
10221 for the v1 directory protocol, the v2 directory protocol, and
10222 as hidden service directories, to make it easier to retire old
10223 authorities. V1 authorities should set "HSAuthoritativeDir 1"
10224 to continue being hidden service authorities too.
10225 - Remove 8888 as a LongLivedPort, and add 6697 (IRCS).
10227 o Minor features, controller:
10228 - Fix CIRC controller events so that controllers can learn the
10229 identity digests of non-Named servers used in circuit paths.
10230 - Let controllers ask for more useful identifiers for servers. Instead
10231 of learning identity digests for un-Named servers and nicknames
10232 for Named servers, the new identifiers include digest, nickname,
10233 and indication of Named status. Off by default; see control-spec.txt
10234 for more information.
10235 - Add a "getinfo address" controller command so it can display Tor's
10236 best guess to the user.
10237 - New controller event to alert the controller when our server
10238 descriptor has changed.
10239 - Give more meaningful errors on controller authentication failure.
10241 o Minor features, other:
10242 - When asked to resolve a hostname, don't use non-exit servers unless
10243 requested to do so. This allows servers with broken DNS to be
10244 useful to the network.
10245 - Divide eventdns log messages into warn and info messages.
10246 - Reserve the nickname "Unnamed" for routers that can't pick
10247 a hostname: any router can call itself Unnamed; directory
10248 authorities will never allocate Unnamed to any particular router;
10249 clients won't believe that any router is the canonical Unnamed.
10250 - Only include function names in log messages for info/debug messages.
10251 For notice/warn/err, the content of the message should be clear on
10252 its own, and printing the function name only confuses users.
10253 - Avoid some false positives during reachability testing: don't try
10254 to test via a server that's on the same /24 as us.
10255 - If we fail to build a circuit to an intended enclave, and it's
10256 not mandatory that we use that enclave, stop wanting it.
10257 - When eventdns is enabled, allow multithreaded builds on NetBSD and
10258 OpenBSD. (We had previously disabled threads on these platforms
10259 because they didn't have working thread-safe resolver functions.)
10261 o Major bugfixes, anonymity/security:
10262 - If a client asked for a server by name, and there's a named server
10263 in our network-status but we don't have its descriptor yet, we
10264 could return an unnamed server instead.
10265 - Fix NetBSD bug that could allow someone to force uninitialized RAM
10266 to be sent to a server's DNS resolver. This only affects NetBSD
10267 and other platforms that do not bounds-check tolower().
10268 - Reject (most) attempts to use Tor circuits with length one. (If
10269 many people start using Tor as a one-hop proxy, exit nodes become
10270 a more attractive target for compromise.)
10271 - Just because your DirPort is open doesn't mean people should be
10272 able to remotely teach you about hidden service descriptors. Now
10273 only accept rendezvous posts if you've got HSAuthoritativeDir set.
10275 o Major bugfixes, other:
10276 - Don't crash on race condition in dns.c: tor_assert(!resolve->expire)
10277 - When a client asks the server to resolve (not connect to)
10278 an address, and it has a cached answer, give them the cached answer.
10279 Previously, the server would give them no answer at all.
10280 - Allow really slow clients to not hang up five minutes into their
10281 directory downloads (suggested by Adam J. Richter).
10282 - We were building exactly the wrong circuits when we anticipated
10283 hidden service requirements, meaning Tor would have to build all
10284 its circuits on demand.
10285 - Avoid crashing when we mmap a router cache file of size 0.
10286 - When testing reachability of our DirPort, don't launch new
10287 tests when there's already one in progress -- unreachable
10288 servers were stacking up dozens of testing streams.
10290 o Minor bugfixes, correctness:
10291 - If we're a directory mirror and we ask for "all" network status
10292 documents, we would discard status documents from authorities
10293 we don't recognize.
10294 - Avoid a memory corruption bug when creating a hash table for
10296 - Avoid controller-triggered crash when misusing certain commands
10297 from a v0 controller on platforms that do not handle
10298 printf("%s",NULL) gracefully.
10299 - Don't crash when a controller sends a third argument to an
10300 "extendcircuit" request.
10301 - Controller protocol fixes: fix encoding in "getinfo addr-mappings"
10302 response; fix error code when "getinfo dir/status/" fails.
10303 - Avoid crash when telling controller stream-status and a stream
10305 - Patch from Adam Langley to fix assert() in eventdns.c.
10306 - Fix a debug log message in eventdns to say "X resolved to Y"
10307 instead of "X resolved to X".
10308 - Make eventdns give strings for DNS errors, not just error numbers.
10309 - Track unreachable entry guards correctly: don't conflate
10310 'unreachable by us right now' with 'listed as down by the directory
10311 authorities'. With the old code, if a guard was unreachable by
10312 us but listed as running, it would clog our guard list forever.
10313 - Behave correctly in case we ever have a network with more than
10314 2GB/s total advertised capacity.
10315 - Make TrackExitHosts case-insensitive, and fix the behavior of
10316 ".suffix" TrackExitHosts items to avoid matching in the middle of
10318 - Finally fix the openssl warnings from newer gccs that believe that
10319 ignoring a return value is okay, but casting a return value and
10320 then ignoring it is a sign of madness.
10321 - Prevent the contrib/exitlist script from printing the same
10322 result more than once.
10323 - Patch from Steve Hildrey: Generate network status correctly on
10324 non-versioning dirservers.
10325 - Don't listen to the X-Your-Address-Is hint if you did the lookup
10326 via Tor; otherwise you'll think you're the exit node's IP address.
10328 o Minor bugfixes, performance:
10329 - Two small performance improvements on parsing descriptors.
10330 - Major performance improvement on inserting descriptors: change
10331 algorithm from O(n^2) to O(n).
10332 - Make the common memory allocation path faster on machines where
10333 malloc(0) returns a pointer.
10334 - Start remembering X-Your-Address-Is directory hints even if you're
10335 a client, so you can become a server more smoothly.
10336 - Avoid duplicate entries on MyFamily line in server descriptor.
10338 o Packaging, features:
10339 - Remove architecture from OS X builds. The official builds are
10340 now universal binaries.
10341 - The Debian package now uses --verify-config when (re)starting,
10342 to distinguish configuration errors from other errors.
10343 - Update RPMs to require libevent 1.1b.
10345 o Packaging, bugfixes:
10346 - Patches so Tor builds with MinGW on Windows.
10347 - Patches so Tor might run on Cygwin again.
10348 - Resume building on non-gcc compilers and ancient gcc. Resume
10349 building with the -O0 compile flag. Resume building cleanly on
10351 - Run correctly on OS X platforms with case-sensitive filesystems.
10352 - Correct includes for net/if.h and net/pfvar.h on OpenBSD (from Tup).
10353 - Add autoconf checks so Tor can build on Solaris x86 again.
10356 - Documented (and renamed) ServerDNSSearchDomains and
10357 ServerDNSResolvConfFile options.
10358 - Be clearer that the *ListenAddress directives can be repeated
10362 Changes in version 0.1.1.24 - 2006-09-29
10364 - Allow really slow clients to not hang up five minutes into their
10365 directory downloads (suggested by Adam J. Richter).
10366 - Fix major performance regression from 0.1.0.x: instead of checking
10367 whether we have enough directory information every time we want to
10368 do something, only check when the directory information has changed.
10369 This should improve client CPU usage by 25-50%.
10370 - Don't crash if, after a server has been running for a while,
10371 it can't resolve its hostname.
10374 - Allow Tor to start when RunAsDaemon is set but no logs are set.
10375 - Don't crash when the controller receives a third argument to an
10376 "extendcircuit" request.
10377 - Controller protocol fixes: fix encoding in "getinfo addr-mappings"
10378 response; fix error code when "getinfo dir/status/" fails.
10379 - Fix configure.in to not produce broken configure files with
10380 more recent versions of autoconf. Thanks to Clint for his auto*
10382 - Fix security bug on NetBSD that could allow someone to force
10383 uninitialized RAM to be sent to a server's DNS resolver. This
10384 only affects NetBSD and other platforms that do not bounds-check
10386 - Warn user when using libevent 1.1a or earlier with win32 or kqueue
10387 methods: these are known to be buggy.
10388 - If we're a directory mirror and we ask for "all" network status
10389 documents, we would discard status documents from authorities
10390 we don't recognize.
10393 Changes in version 0.1.2.1-alpha - 2006-08-27
10395 - Add "eventdns" async dns library from Adam Langley, tweaked to
10396 build on OSX and Windows. Only enabled if you pass the
10397 --enable-eventdns argument to configure.
10398 - Allow servers with no hostname or IP address to learn their
10399 IP address by asking the directory authorities. This code only
10400 kicks in when you would normally have exited with a "no address"
10401 error. Nothing's authenticated, so use with care.
10402 - Rather than waiting a fixed amount of time between retrying
10403 application connections, we wait only 5 seconds for the first,
10404 10 seconds for the second, and 15 seconds for each retry after
10405 that. Hopefully this will improve the expected user experience.
10406 - Patch from Tup to add support for transparent AP connections:
10407 this basically bundles the functionality of trans-proxy-tor
10408 into the Tor mainline. Now hosts with compliant pf/netfilter
10409 implementations can redirect TCP connections straight to Tor
10410 without diverting through SOCKS. Needs docs.
10411 - Busy directory servers save lots of memory by spooling server
10412 descriptors, v1 directories, and v2 networkstatus docs to buffers
10413 as needed rather than en masse. Also mmap the cached-routers
10414 files, so we don't need to keep the whole thing in memory too.
10415 - Automatically avoid picking more than one node from the same
10416 /16 network when constructing a circuit.
10417 - Revise and clean up the torrc.sample that we ship with; add
10418 a section for BandwidthRate and BandwidthBurst.
10421 - Split circuit_t into origin_circuit_t and or_circuit_t, and
10422 split connection_t into edge, or, dir, control, and base structs.
10423 These will save quite a bit of memory on busy servers, and they'll
10424 also help us track down bugs in the code and bugs in the spec.
10425 - Experimentally re-enable kqueue on OSX when using libevent 1.1b
10426 or later. Log when we are doing this, so we can diagnose it when
10427 it fails. (Also, recommend libevent 1.1b for kqueue and
10428 win32 methods; deprecate libevent 1.0b harder; make libevent
10429 recommendation system saner.)
10430 - Start being able to build universal binaries on OS X (thanks
10432 - Export the default exit policy via the control port, so controllers
10433 don't need to guess what it is / will be later.
10434 - Add a man page entry for ProtocolWarnings.
10435 - Add TestVia config option to the man page.
10436 - Remove even more protocol-related warnings from Tor server logs,
10437 such as bad TLS handshakes and malformed begin cells.
10438 - Stop fetching descriptors if you're not a dir mirror and you
10439 haven't tried to establish any circuits lately. [This currently
10440 causes some dangerous behavior, because when you start up again
10441 you'll use your ancient server descriptors.]
10442 - New DirPort behavior: if you have your dirport set, you download
10443 descriptors aggressively like a directory mirror, whether or not
10444 your ORPort is set.
10445 - Get rid of the router_retry_connections notion. Now routers
10446 no longer try to rebuild long-term connections to directory
10447 authorities, and directory authorities no longer try to rebuild
10448 long-term connections to all servers. We still don't hang up
10449 connections in these two cases though -- we need to look at it
10450 more carefully to avoid flapping, and we likely need to wait til
10451 0.1.1.x is obsolete.
10452 - Drop compatibility with obsolete Tors that permit create cells
10453 to have the wrong circ_id_type.
10454 - Re-enable per-connection rate limiting. Get rid of the "OP
10455 bandwidth" concept. Lay groundwork for "bandwidth classes" --
10456 separate global buckets that apply depending on what sort of conn
10458 - Start publishing one minute or so after we find our ORPort
10459 to be reachable. This will help reduce the number of descriptors
10460 we have for ourselves floating around, since it's quite likely
10461 other things (e.g. DirPort) will change during that minute too.
10462 - Fork the v1 directory protocol into its own spec document,
10463 and mark dir-spec.txt as the currently correct (v2) spec.
10466 - When we find our DirPort to be reachable, publish a new descriptor
10467 so we'll tell the world (reported by pnx).
10468 - Publish a new descriptor after we hup/reload. This is important
10469 if our config has changed such that we'll want to start advertising
10470 our DirPort now, etc.
10471 - Allow Tor to start when RunAsDaemon is set but no logs are set.
10472 - When we have a state file we cannot parse, tell the user and
10473 move it aside. Now we avoid situations where the user starts
10474 Tor in 1904, Tor writes a state file with that timestamp in it,
10475 the user fixes her clock, and Tor refuses to start.
10476 - Fix configure.in to not produce broken configure files with
10477 more recent versions of autoconf. Thanks to Clint for his auto*
10479 - "tor --verify-config" now exits with -1(255) or 0 depending on
10480 whether the config options are bad or good.
10481 - Resolve bug 321 when using dnsworkers: append a period to every
10482 address we resolve at the exit node, so that we do not accidentally
10483 pick up local addresses, and so that failing searches are retried
10484 in the resolver search domains. (This is already solved for
10485 eventdns.) (This breaks Blossom servers for now.)
10486 - If we are using an exit enclave and we can't connect, e.g. because
10487 its webserver is misconfigured to not listen on localhost, then
10488 back off and try connecting from somewhere else before we fail.
10491 - Start compiling on MinGW on Windows (patches from Mike Chiussi).
10492 - Start compiling on MSVC6 on Windows (patches from Frediano Ziglio).
10493 - Fix bug 314: Tor clients issued "unsafe socks" warnings even
10494 when the IP address is mapped through MapAddress to a hostname.
10495 - Start passing "ipv4" hints to getaddrinfo(), so servers don't do
10496 useless IPv6 DNS resolves.
10497 - Patch suggested by Karsten Loesing: respond to SIGNAL command
10498 before we execute the signal, in case the signal shuts us down.
10499 - Clean up AllowInvalidNodes man page entry.
10500 - Claim a commonname of Tor, rather than TOR, in TLS handshakes.
10501 - Add more asserts to track down an assert error on a windows Tor
10502 server with connection_add being called with socket == -1.
10503 - Handle reporting OR_CONN_EVENT_NEW events to the controller.
10504 - Fix misleading log messages: an entry guard that is "unlisted",
10505 as well as not known to be "down" (because we've never heard
10506 of it), is not therefore "up".
10507 - Remove code to special-case "-cvs" ending, since it has not
10508 actually mattered since 0.0.9.
10509 - Make our socks5 handling more robust to broken socks clients:
10510 throw out everything waiting on the buffer in between socks
10511 handshake phases, since they can't possibly (so the theory
10512 goes) have predicted what we plan to respond to them.
10515 Changes in version 0.1.1.23 - 2006-07-30
10517 - Fast Tor servers, especially exit nodes, were triggering asserts
10518 due to a bug in handling the list of pending DNS resolves. Some
10519 bugs still remain here; we're hunting them.
10520 - Entry guards could crash clients by sending unexpected input.
10521 - More fixes on reachability testing: if you find yourself reachable,
10522 then don't ever make any client requests (so you stop predicting
10523 circuits), then hup or have your clock jump, then later your IP
10524 changes, you won't think circuits are working, so you won't try to
10525 test reachability, so you won't publish.
10528 - Avoid a crash if the controller does a resetconf firewallports
10529 and then a setconf fascistfirewall=1.
10530 - Avoid an integer underflow when the dir authority decides whether
10531 a router is stable: we might wrongly label it stable, and compute
10532 a slightly wrong median stability, when a descriptor is published
10534 - Fix a place where we might trigger an assert if we can't build our
10535 own server descriptor yet.
10538 Changes in version 0.1.1.22 - 2006-07-05
10540 - Fix a big bug that was causing servers to not find themselves
10541 reachable if they changed IP addresses. Since only 0.1.1.22+
10542 servers can do reachability testing correctly, now we automatically
10543 make sure to test via one of these.
10544 - Fix to allow clients and mirrors to learn directory info from
10545 descriptor downloads that get cut off partway through.
10546 - Directory authorities had a bug in deciding if a newly published
10547 descriptor was novel enough to make everybody want a copy -- a few
10548 servers seem to be publishing new descriptors many times a minute.
10550 - Fix a rare bug that was causing some servers to complain about
10551 "closing wedged cpuworkers" and skip some circuit create requests.
10552 - Make the Exit flag in directory status documents actually work.
10555 Changes in version 0.1.1.21 - 2006-06-10
10556 o Crash and assert fixes from 0.1.1.20:
10557 - Fix a rare crash on Tor servers that have enabled hibernation.
10558 - Fix a seg fault on startup for Tor networks that use only one
10559 directory authority.
10560 - Fix an assert from a race condition that occurs on Tor servers
10561 while exiting, where various threads are trying to log that they're
10562 exiting, and delete the logs, at the same time.
10563 - Make our unit tests pass again on certain obscure platforms.
10566 - Add support for building SUSE RPM packages.
10567 - Speed up initial bootstrapping for clients: if we are making our
10568 first ever connection to any entry guard, then don't mark it down
10570 - When only one Tor server in the network is labelled as a guard,
10571 and we've already picked him, we would cycle endlessly picking him
10572 again, being unhappy about it, etc. Now we specifically exclude
10573 current guards when picking a new guard.
10574 - Servers send create cells more reliably after the TLS connection
10575 is established: we were sometimes forgetting to send half of them
10576 when we had more than one pending.
10577 - If we get a create cell that asks us to extend somewhere, but the
10578 Tor server there doesn't match the expected digest, we now send
10579 a destroy cell back, rather than silently doing nothing.
10580 - Make options->RedirectExit work again.
10581 - Make cookie authentication for the controller work again.
10582 - Stop being picky about unusual characters in the arguments to
10583 mapaddress. It's none of our business.
10584 - Add a new config option "TestVia" that lets you specify preferred
10585 middle hops to use for test circuits. Perhaps this will let me
10586 debug the reachability problems better.
10588 o Log / documentation fixes:
10589 - If we're a server and some peer has a broken TLS certificate, don't
10590 log about it unless ProtocolWarnings is set, i.e., we want to hear
10591 about protocol violations by others.
10592 - Fix spelling of VirtualAddrNetwork in man page.
10593 - Add a better explanation at the top of the autogenerated torrc file
10594 about what happened to our old torrc.
10597 Changes in version 0.1.1.20 - 2006-05-23
10599 - Downgrade a log severity where servers complain that they're
10601 - Avoid a compile warning on FreeBSD.
10602 - Remove string size limit on NEWDESC messages; solve bug 291.
10603 - Correct the RunAsDaemon entry in the man page; ignore RunAsDaemon
10604 more thoroughly when we're running on windows.
10607 Changes in version 0.1.1.19-rc - 2006-05-03
10609 - Regenerate our local descriptor if it's dirty and we try to use
10610 it locally (e.g. if it changes during reachability detection).
10611 - If we setconf our ORPort to 0, we continued to listen on the
10612 old ORPort and receive connections.
10613 - Avoid a second warning about machine/limits.h on Debian
10615 - Be willing to add our own routerinfo into the routerlist.
10616 Now authorities will include themselves in their directories
10617 and network-statuses.
10618 - Stop trying to upload rendezvous descriptors to every
10619 directory authority: only try the v1 authorities.
10620 - Servers no longer complain when they think they're not
10621 registered with the directory authorities. There were too many
10623 - Backport dist-rpm changes so rpms can be built without errors.
10626 - Implement an option, VirtualAddrMask, to set which addresses
10627 get handed out in response to mapaddress requests. This works
10628 around a bug in tsocks where 127.0.0.0/8 is never socksified.
10631 Changes in version 0.1.1.18-rc - 2006-04-10
10633 - Work harder to download live network-statuses from all the
10634 directory authorities we know about. Improve the threshold
10635 decision logic so we're more robust to edge cases.
10636 - When fetching rendezvous descriptors, we were willing to ask
10637 v2 authorities too, which would always return 404.
10640 - Stop listing down or invalid nodes in the v1 directory. This will
10641 reduce its bulk by about 1/3, and reduce load on directory
10643 - When deciding whether a router is Fast or Guard-worthy, consider
10644 his advertised BandwidthRate and not just the BandwidthCapacity.
10645 - No longer ship INSTALL and README files -- they are useless now.
10646 - Force rpmbuild to behave and honor target_cpu.
10647 - Avoid warnings about machine/limits.h on Debian GNU/kFreeBSD.
10648 - Start to include translated versions of the tor-doc-*.html
10649 files, along with the screenshots. Still needs more work.
10650 - Start sending back 512 and 451 errors if mapaddress fails,
10651 rather than not sending anything back at all.
10652 - When we fail to bind or listen on an incoming or outgoing
10653 socket, we should close it before failing. otherwise we just
10654 leak it. (thanks to weasel for finding.)
10655 - Allow "getinfo dir/status/foo" to work, as long as your DirPort
10656 is enabled. (This is a hack, and will be fixed in 0.1.2.x.)
10657 - Make NoPublish (even though deprecated) work again.
10658 - Fix a minor security flaw where a versioning auth dirserver
10659 could list a recommended version many times in a row to make
10660 clients more convinced that it's recommended.
10661 - Fix crash bug if there are two unregistered servers running
10662 with the same nickname, one of them is down, and you ask for
10663 them by nickname in your EntryNodes or ExitNodes. Also, try
10664 to pick the one that's running rather than an arbitrary one.
10665 - Fix an infinite loop we could hit if we go offline for too long.
10666 - Complain when we hit WSAENOBUFS on recv() or write() too.
10667 Perhaps this will help us hunt the bug.
10668 - If you're not a versioning dirserver, don't put the string
10669 "client-versions \nserver-versions \n" in your network-status.
10670 - Lower the minimum required number of file descriptors to 1000,
10671 so we can have some overhead for Valgrind on Linux, where the
10672 default ulimit -n is 1024.
10675 - Add tor.dizum.com as the fifth authoritative directory server.
10676 - Add a new config option FetchUselessDescriptors, off by default,
10677 for when you plan to run "exitlist" on your client and you want
10678 to know about even the non-running descriptors.
10681 Changes in version 0.1.1.17-rc - 2006-03-28
10683 - Clients and servers since 0.1.1.10-alpha have been expiring
10684 connections whenever they are idle for 5 minutes and they *do*
10685 have circuits on them. Oops. With this new version, clients will
10686 discard their previous entry guard choices and avoid choosing
10687 entry guards running these flawed versions.
10688 - Fix memory leak when uncompressing concatenated zlib streams. This
10689 was causing substantial leaks over time on Tor servers.
10690 - The v1 directory was including servers as much as 48 hours old,
10691 because that's how the new routerlist->routers works. Now only
10692 include them if they're 20 hours old or less.
10695 - Resume building on irix64, netbsd 2.0, etc.
10696 - On non-gcc compilers (e.g. solaris), use "-g -O" instead of
10698 - Stop writing the "router.desc" file, ever. Nothing uses it anymore,
10699 and it is confusing some users.
10700 - Mirrors stop caching the v1 directory so often.
10701 - Make the max number of old descriptors that a cache will hold
10702 rise with the number of directory authorities, so we can scale.
10703 - Change our win32 uname() hack to be more forgiving about what
10704 win32 versions it thinks it's found.
10707 - Add lefkada.eecs.harvard.edu as a fourth authoritative directory
10709 - When the controller's *setconf commands fail, collect an error
10710 message in a string and hand it back to the controller.
10711 - Make the v2 dir's "Fast" flag based on relative capacity, just
10712 like "Stable" is based on median uptime. Name everything in the
10713 top 7/8 Fast, and only the top 1/2 gets to be a Guard.
10714 - Log server fingerprint on startup, so new server operators don't
10715 have to go hunting around their filesystem for it.
10716 - Return a robots.txt on our dirport to discourage google indexing.
10717 - Let the controller ask for GETINFO dir/status/foo so it can ask
10718 directly rather than connecting to the dir port. Only works when
10719 dirport is set for now.
10721 o New config options rather than constants in the code:
10722 - SocksTimeout: How long do we let a socks connection wait
10723 unattached before we fail it?
10724 - CircuitBuildTimeout: Cull non-open circuits that were born
10725 at least this many seconds ago.
10726 - CircuitIdleTimeout: Cull open clean circuits that were born
10727 at least this many seconds ago.
10730 Changes in version 0.1.1.16-rc - 2006-03-18
10731 o Bugfixes on 0.1.1.15-rc:
10732 - Fix assert when the controller asks to attachstream a connect-wait
10733 or resolve-wait stream.
10734 - Now do address rewriting when the controller asks us to attach
10735 to a particular circuit too. This will let Blossom specify
10736 "moria2.exit" without having to learn what moria2's IP address is.
10737 - Make the "tor --verify-config" command-line work again, so people
10738 can automatically check if their torrc will parse.
10739 - Authoritative dirservers no longer require an open connection from
10740 a server to consider him "reachable". We need this change because
10741 when we add new auth dirservers, old servers won't know not to
10743 - Let Tor build on Sun CC again.
10744 - Fix an off-by-one buffer size in dirserv.c that magically never
10745 hit our three authorities but broke sjmurdoch's own tor network.
10746 - If we as a directory mirror don't know of any v1 directory
10747 authorities, then don't try to cache any v1 directories.
10748 - Stop warning about unknown servers in our family when they are
10749 given as hex digests.
10750 - Stop complaining as quickly to the server operator that he
10751 hasn't registered his nickname/key binding.
10752 - Various cleanups so we can add new V2 Auth Dirservers.
10753 - Change "AllowUnverifiedNodes" to "AllowInvalidNodes", to
10754 reflect the updated flags in our v2 dir protocol.
10755 - Resume allowing non-printable characters for exit streams (both
10756 for connecting and for resolving). Now we tolerate applications
10757 that don't follow the RFCs. But continue to block malformed names
10760 o Bugfixes on 0.1.0.x:
10761 - Fix assert bug in close_logs(): when we close and delete logs,
10762 remove them all from the global "logfiles" list.
10763 - Fix minor integer overflow in calculating when we expect to use up
10764 our bandwidth allocation before hibernating.
10765 - Fix a couple of bugs in OpenSSL detection. Also, deal better when
10766 there are multiple SSLs installed with different versions.
10767 - When we try to be a server and Address is not explicitly set and
10768 our hostname resolves to a private IP address, try to use an
10769 interface address if it has a public address. Now Windows machines
10770 that think of themselves as localhost can work by default.
10773 - Let the controller ask for GETINFO dir/server/foo so it can ask
10774 directly rather than connecting to the dir port.
10775 - Let the controller tell us about certain router descriptors
10776 that it doesn't want Tor to use in circuits. Implement
10777 SETROUTERPURPOSE and modify +POSTDESCRIPTOR to do this.
10778 - New config option SafeSocks to reject all application connections
10779 using unsafe socks protocols. Defaults to off.
10782 Changes in version 0.1.1.15-rc - 2006-03-11
10783 o Bugfixes and cleanups:
10784 - When we're printing strings from the network, don't try to print
10785 non-printable characters. This protects us against shell escape
10786 sequence exploits, and also against attacks to fool humans into
10787 misreading their logs.
10788 - Fix a bug where Tor would fail to establish any connections if you
10789 left it off for 24 hours and then started it: we were happy with
10790 the obsolete network statuses, but they all referred to router
10791 descriptors that were too old to fetch, so we ended up with no
10792 valid router descriptors.
10793 - Fix a seg fault in the controller's "getinfo orconn-status"
10794 command while listing status on incoming handshaking connections.
10795 Introduce a status name "NEW" for these connections.
10796 - If we get a linelist or linelist_s config option from the torrc
10797 (e.g. ExitPolicy) and it has no value, warn and skip rather than
10798 silently resetting it to its default.
10799 - Don't abandon entry guards until they've been down or gone for
10801 - Cleaner and quieter log messages.
10804 - New controller signal NEWNYM that makes new application requests
10805 use clean circuits.
10806 - Add a new circuit purpose 'controller' to let the controller ask
10807 for a circuit that Tor won't try to use. Extend the EXTENDCIRCUIT
10808 controller command to let you specify the purpose if you're
10809 starting a new circuit. Add a new SETCIRCUITPURPOSE controller
10810 command to let you change a circuit's purpose after it's been
10812 - Accept "private:*" in routerdesc exit policies; not generated yet
10813 because older Tors do not understand it.
10814 - Add BSD-style contributed startup script "rc.subr" from Peter
10818 Changes in version 0.1.1.14-alpha - 2006-02-20
10819 o Bugfixes on 0.1.1.x:
10820 - Don't die if we ask for a stdout or stderr log (even implicitly)
10821 and we're set to RunAsDaemon -- just warn.
10822 - We still had a few bugs in the OR connection rotation code that
10823 caused directory servers to slowly aggregate connections to other
10824 fast Tor servers. This time for sure!
10825 - Make log entries on Win32 include the name of the function again.
10826 - We were treating a pair of exit policies if they were equal even
10827 if one said accept and the other said reject -- causing us to
10828 not always publish a new descriptor since we thought nothing
10830 - Retry pending server downloads as well as pending networkstatus
10831 downloads when we unexpectedly get a socks request.
10832 - We were ignoring the IS_FAST flag in the directory status,
10833 meaning we were willing to pick trivial-bandwidth nodes for "fast"
10835 - If the controller's SAVECONF command fails (e.g. due to file
10836 permissions), let the controller know that it failed.
10839 - If we're trying to be a Tor server and running Windows 95/98/ME
10840 as a server, explain that we'll likely crash.
10841 - When we're a server, a client asks for an old-style directory,
10842 and our write bucket is empty, don't give it to him. This way
10843 small servers can continue to serve the directory *sometimes*,
10844 without getting overloaded.
10845 - Compress exit policies even more -- look for duplicate lines
10847 - Clients now honor the "guard" flag in the router status when
10848 picking entry guards, rather than looking at is_fast or is_stable.
10849 - Retain unrecognized lines in $DATADIR/state file, so that we can
10850 be forward-compatible.
10851 - Generate 18.0.0.0/8 address policy format in descs when we can;
10852 warn when the mask is not reducible to a bit-prefix.
10853 - Let the user set ControlListenAddress in the torrc. This can be
10854 dangerous, but there are some cases (like a secured LAN) where it
10856 - Split ReachableAddresses into ReachableDirAddresses and
10857 ReachableORAddresses, so we can restrict Dir conns to port 80
10858 and OR conns to port 443.
10859 - Now we can target arch and OS in rpm builds (contributed by
10860 Phobos). Also make the resulting dist-rpm filename match the
10862 - New config options to help controllers: FetchServerDescriptors
10863 and FetchHidServDescriptors for whether to fetch server
10864 info and hidserv info or let the controller do it, and
10865 PublishServerDescriptor and PublishHidServDescriptors.
10866 - Also let the controller set the __AllDirActionsPrivate config
10867 option if you want all directory fetches/publishes to happen via
10868 Tor (it assumes your controller bootstraps your circuits).
10871 Changes in version 0.1.0.17 - 2006-02-17
10872 o Crash bugfixes on 0.1.0.x:
10873 - When servers with a non-zero DirPort came out of hibernation,
10874 sometimes they would trigger an assert.
10876 o Other important bugfixes:
10877 - On platforms that don't have getrlimit (like Windows), we were
10878 artificially constraining ourselves to a max of 1024
10879 connections. Now just assume that we can handle as many as 15000
10880 connections. Hopefully this won't cause other problems.
10882 o Backported features:
10883 - When we're a server, a client asks for an old-style directory,
10884 and our write bucket is empty, don't give it to him. This way
10885 small servers can continue to serve the directory *sometimes*,
10886 without getting overloaded.
10887 - Whenever you get a 503 in response to a directory fetch, try
10888 once more. This will become important once servers start sending
10889 503's whenever they feel busy.
10890 - Fetch a new directory every 120 minutes, not every 40 minutes.
10891 Now that we have hundreds of thousands of users running the old
10892 directory algorithm, it's starting to hurt a lot.
10893 - Bump up the period for forcing a hidden service descriptor upload
10894 from 20 minutes to 1 hour.
10897 Changes in version 0.1.1.13-alpha - 2006-02-09
10898 o Crashes in 0.1.1.x:
10899 - When you tried to setconf ORPort via the controller, Tor would
10900 crash. So people using TorCP to become a server were sad.
10901 - Solve (I hope) the stack-smashing bug that we were seeing on fast
10902 servers. The problem appears to be something do with OpenSSL's
10903 random number generation, or how we call it, or something. Let me
10904 know if the crashes continue.
10905 - Turn crypto hardware acceleration off by default, until we find
10906 somebody smart who can test it for us. (It appears to produce
10907 seg faults in at least some cases.)
10908 - Fix a rare assert error when we've tried all intro points for
10909 a hidden service and we try fetching the service descriptor again:
10910 "Assertion conn->state != AP_CONN_STATE_RENDDESC_WAIT failed"
10913 - Fix a major load balance bug: we were round-robining in 16 KB
10914 chunks, and servers with bandwidthrate of 20 KB, while downloading
10915 a 600 KB directory, would starve their other connections. Now we
10916 try to be a bit more fair.
10917 - Dir authorities and mirrors were never expiring the newest
10918 descriptor for each server, causing memory and directory bloat.
10919 - Fix memory-bloating and connection-bloating bug on servers: We
10920 were never closing any connection that had ever had a circuit on
10921 it, because we were checking conn->n_circuits == 0, yet we had a
10922 bug that let it go negative.
10923 - Make Tor work using squid as your http proxy again -- squid
10924 returns an error if you ask for a URL that's too long, and it uses
10925 a really generic error message. Plus, many people are behind a
10926 transparent squid so they don't even realize it.
10927 - On platforms that don't have getrlimit (like Windows), we were
10928 artificially constraining ourselves to a max of 1024
10929 connections. Now just assume that we can handle as many as 15000
10930 connections. Hopefully this won't cause other problems.
10931 - Add a new config option ExitPolicyRejectPrivate which defaults to
10932 1. This means all exit policies will begin with rejecting private
10933 addresses, unless the server operator explicitly turns it off.
10936 - Clients no longer download descriptors for non-running
10938 - Before we add new directory authorities, we should make it
10939 clear that only v1 authorities should receive/publish hidden
10940 service descriptors.
10943 - As soon as we've fetched some more directory info, immediately
10944 try to download more server descriptors. This way we don't have
10945 a 10 second pause during initial bootstrapping.
10946 - Remove even more loud log messages that the server operator can't
10948 - When we're running an obsolete or un-recommended version, make
10949 the log message more clear about what the problem is and what
10950 versions *are* still recommended.
10951 - Provide a more useful warn message when our onion queue gets full:
10952 the CPU is too slow or the exit policy is too liberal.
10953 - Don't warn when we receive a 503 from a dirserver/cache -- this
10954 will pave the way for them being able to refuse if they're busy.
10955 - When we fail to bind a listener, try to provide a more useful
10956 log message: e.g., "Is Tor already running?"
10957 - Adjust tor-spec to parameterize cell and key lengths. Now Ian
10958 Goldberg can prove things about our handshake protocol more
10960 - MaxConn has been obsolete for a while now. Document the ConnLimit
10961 config option, which is a *minimum* number of file descriptors
10962 that must be available else Tor refuses to start.
10963 - Apply Matt Ghali's --with-syslog-facility patch to ./configure
10964 if you log to syslog and want something other than LOG_DAEMON.
10965 - Make dirservers generate a separate "guard" flag to mean,
10966 "would make a good entry guard". Make clients parse it and vote
10967 on it. Not used by clients yet.
10968 - Implement --with-libevent-dir option to ./configure. Also, improve
10969 search techniques to find libevent, and use those for openssl too.
10970 - Bump the default bandwidthrate to 3 MB, and burst to 6 MB
10971 - Only start testing reachability once we've established a
10972 circuit. This will make startup on dirservers less noisy.
10973 - Don't try to upload hidden service descriptors until we have
10974 established a circuit.
10975 - Fix the controller's "attachstream 0" command to treat conn like
10976 it just connected, doing address remapping, handling .exit and
10977 .onion idioms, and so on. Now we're more uniform in making sure
10978 that the controller hears about new and closing connections.
10981 Changes in version 0.1.1.12-alpha - 2006-01-11
10982 o Bugfixes on 0.1.1.x:
10983 - The fix to close duplicate server connections was closing all
10984 Tor client connections if they didn't establish a circuit
10985 quickly enough. Oops.
10986 - Fix minor memory issue (double-free) that happened on exit.
10988 o Bugfixes on 0.1.0.x:
10989 - Tor didn't warn when it failed to open a log file.
10992 Changes in version 0.1.1.11-alpha - 2006-01-10
10993 o Crashes in 0.1.1.x:
10994 - Include all the assert/crash fixes from 0.1.0.16.
10995 - If you start Tor and then quit very quickly, there were some
10996 races that tried to free things that weren't allocated yet.
10997 - Fix a rare memory stomp if you're running hidden services.
10998 - Fix segfault when specifying DirServer in config without nickname.
10999 - Fix a seg fault when you finish connecting to a server but at
11000 that moment you dump his server descriptor.
11001 - Extendcircuit and Attachstream controller commands would
11002 assert/crash if you don't give them enough arguments.
11003 - Fix an assert error when we're out of space in the connection_list
11004 and we try to post a hidden service descriptor (reported by weasel).
11005 - If you specify a relative torrc path and you set RunAsDaemon in
11006 your torrc, then it chdir()'s to the new directory. If you HUP,
11007 it tries to load the new torrc location, fails, and exits.
11008 The fix: no longer allow a relative path to torrc using -f.
11011 - Implement "entry guards": automatically choose a handful of entry
11012 nodes and stick with them for all circuits. Only pick new guards
11013 when the ones you have are unsuitable, and if the old guards
11014 become suitable again, switch back. This will increase security
11015 dramatically against certain end-point attacks. The EntryNodes
11016 config option now provides some hints about which entry guards you
11017 want to use most; and StrictEntryNodes means to only use those.
11018 - New directory logic: download by descriptor digest, not by
11019 fingerprint. Caches try to download all listed digests from
11020 authorities; clients try to download "best" digests from caches.
11021 This avoids partitioning and isolating attacks better.
11022 - Make the "stable" router flag in network-status be the median of
11023 the uptimes of running valid servers, and make clients pay
11024 attention to the network-status flags. Thus the cutoff adapts
11025 to the stability of the network as a whole, making IRC, IM, etc
11026 connections more reliable.
11029 - Tor servers with dynamic IP addresses were needing to wait 18
11030 hours before they could start doing reachability testing using
11031 the new IP address and ports. This is because they were using
11032 the internal descriptor to learn what to test, yet they were only
11033 rebuilding the descriptor once they decided they were reachable.
11034 - Tor 0.1.1.9 and 0.1.1.10 had a serious bug that caused clients
11035 to download certain server descriptors, throw them away, and then
11036 fetch them again after 30 minutes. Now mirrors throw away these
11037 server descriptors so clients can't get them.
11038 - We were leaving duplicate connections to other ORs open for a week,
11039 rather than closing them once we detect a duplicate. This only
11040 really affected authdirservers, but it affected them a lot.
11041 - Spread the authdirservers' reachability testing over the entire
11042 testing interval, so we don't try to do 500 TLS's at once every
11046 - If the network is down, and we try to connect to a conn because
11047 we have a circuit in mind, and we timeout (30 seconds) because the
11048 network never answers, we were expiring the circuit, but we weren't
11049 obsoleting the connection or telling the entry_guards functions.
11050 - Some Tor servers process billions of cells per day. These statistics
11051 need to be uint64_t's.
11052 - Check for integer overflows in more places, when adding elements
11053 to smartlists. This could possibly prevent a buffer overflow
11054 on malicious huge inputs. I don't see any, but I haven't looked
11056 - ReachableAddresses kept growing new "reject *:*" lines on every
11058 - When you "setconf log" via the controller, it should remove all
11059 logs. We were automatically adding back in a "log notice stdout".
11060 - Newly bootstrapped Tor networks couldn't establish hidden service
11061 circuits until they had nodes with high uptime. Be more tolerant.
11062 - We were marking servers down when they could not answer every piece
11063 of the directory request we sent them. This was far too harsh.
11064 - Fix the torify (tsocks) config file to not use Tor for localhost
11066 - Directory authorities now go to the proper authority when asking for
11067 a networkstatus, even when they want a compressed one.
11068 - Fix a harmless bug that was causing Tor servers to log
11069 "Got an end because of misc error, but we're not an AP. Closing."
11070 - Authorities were treating their own descriptor changes as cosmetic,
11071 meaning the descriptor available in the network-status and the
11072 descriptor that clients downloaded were different.
11073 - The OS X installer was adding a symlink for tor_resolve but
11074 the binary was called tor-resolve (reported by Thomas Hardly).
11075 - Workaround a problem with some http proxies where they refuse GET
11076 requests that specify "Content-Length: 0" (reported by Adrian).
11077 - Fix wrong log message when you add a "HiddenServiceNodes" config
11078 line without any HiddenServiceDir line (reported by Chris Thomas).
11081 - Write the TorVersion into the state file so we have a prayer of
11082 keeping forward and backward compatibility.
11083 - Revive the FascistFirewall config option rather than eliminating it:
11084 now it's a synonym for ReachableAddresses *:80,*:443.
11085 - Clients choose directory servers from the network status lists,
11086 not from their internal list of router descriptors. Now they can
11087 go to caches directly rather than needing to go to authorities
11089 - Directory authorities ignore router descriptors that have only
11090 cosmetic differences: do this for 0.1.0.x servers now too.
11091 - Add a new flag to network-status indicating whether the server
11092 can answer v2 directory requests too.
11093 - Authdirs now stop whining so loudly about bad descriptors that
11094 they fetch from other dirservers. So when there's a log complaint,
11095 it's for sure from a freshly uploaded descriptor.
11096 - Reduce memory requirements in our structs by changing the order
11098 - There used to be two ways to specify your listening ports in a
11099 server descriptor: on the "router" line and with a separate "ports"
11100 line. Remove support for the "ports" line.
11101 - New config option "AuthDirRejectUnlisted" for auth dirservers as
11102 a panic button: if we get flooded with unusable servers we can
11103 revert to only listing servers in the approved-routers file.
11104 - Auth dir servers can now mark a fingerprint as "!reject" or
11105 "!invalid" in the approved-routers file (as its nickname), to
11106 refuse descriptors outright or include them but marked as invalid.
11107 - Servers store bandwidth history across restarts/crashes.
11108 - Add reasons to DESTROY and RELAY_TRUNCATED cells, so clients can
11109 get a better idea of why their circuits failed. Not used yet.
11110 - Directory mirrors now cache up to 16 unrecognized network-status
11111 docs. Now we can add new authdirservers and they'll be cached too.
11112 - When picking a random directory, prefer non-authorities if any
11114 - New controller option "getinfo desc/all-recent" to fetch the
11115 latest server descriptor for every router that Tor knows about.
11118 Changes in version 0.1.0.16 - 2006-01-02
11119 o Crash bugfixes on 0.1.0.x:
11120 - On Windows, build with a libevent patch from "I-M Weasel" to avoid
11121 corrupting the heap, losing FDs, or crashing when we need to resize
11122 the fd_sets. (This affects the Win32 binaries, not Tor's sources.)
11123 - It turns out sparc64 platforms crash on unaligned memory access
11124 too -- so detect and avoid this.
11125 - Handle truncated compressed data correctly (by detecting it and
11127 - Fix possible-but-unlikely free(NULL) in control.c.
11128 - When we were closing connections, there was a rare case that
11129 stomped on memory, triggering seg faults and asserts.
11130 - Avoid potential infinite recursion when building a descriptor. (We
11131 don't know that it ever happened, but better to fix it anyway.)
11132 - We were neglecting to unlink marked circuits from soon-to-close OR
11133 connections, which caused some rare scribbling on freed memory.
11134 - Fix a memory stomping race bug when closing the joining point of two
11135 rendezvous circuits.
11136 - Fix an assert in time parsing found by Steven Murdoch.
11138 o Other bugfixes on 0.1.0.x:
11139 - When we're doing reachability testing, provide more useful log
11140 messages so the operator knows what to expect.
11141 - Do not check whether DirPort is reachable when we are suppressing
11142 advertising it because of hibernation.
11143 - When building with -static or on Solaris, we sometimes needed -ldl.
11144 - When we're deciding whether a stream has enough circuits around
11145 that can handle it, count the freshly dirty ones and not the ones
11146 that are so dirty they won't be able to handle it.
11147 - When we're expiring old circuits, we had a logic error that caused
11148 us to close new rendezvous circuits rather than old ones.
11149 - Give a more helpful log message when you try to change ORPort via
11150 the controller: you should upgrade Tor if you want that to work.
11151 - We were failing to parse Tor versions that start with "Tor ".
11152 - Tolerate faulty streams better: when a stream fails for reason
11153 exitpolicy, stop assuming that the router is lying about his exit
11154 policy. When a stream fails for reason misc, allow it to retry just
11155 as if it was resolvefailed. When a stream has failed three times,
11156 reset its failure count so we can try again and get all three tries.
11159 Changes in version 0.1.1.10-alpha - 2005-12-11
11160 o Correctness bugfixes on 0.1.0.x:
11161 - On Windows, build with a libevent patch from "I-M Weasel" to avoid
11162 corrupting the heap, losing FDs, or crashing when we need to resize
11163 the fd_sets. (This affects the Win32 binaries, not Tor's sources.)
11164 - Stop doing the complex voodoo overkill checking for insecure
11165 Diffie-Hellman keys. Just check if it's in [2,p-2] and be happy.
11166 - When we were closing connections, there was a rare case that
11167 stomped on memory, triggering seg faults and asserts.
11168 - We were neglecting to unlink marked circuits from soon-to-close OR
11169 connections, which caused some rare scribbling on freed memory.
11170 - When we're deciding whether a stream has enough circuits around
11171 that can handle it, count the freshly dirty ones and not the ones
11172 that are so dirty they won't be able to handle it.
11173 - Recover better from TCP connections to Tor servers that are
11174 broken but don't tell you (it happens!); and rotate TLS
11175 connections once a week.
11176 - When we're expiring old circuits, we had a logic error that caused
11177 us to close new rendezvous circuits rather than old ones.
11178 - Fix a scary-looking but apparently harmless bug where circuits
11179 would sometimes start out in state CIRCUIT_STATE_OR_WAIT at
11180 servers, and never switch to state CIRCUIT_STATE_OPEN.
11181 - When building with -static or on Solaris, we sometimes needed to
11183 - Give a useful message when people run Tor as the wrong user,
11184 rather than telling them to start chowning random directories.
11185 - We were failing to inform the controller about new .onion streams.
11187 o Security bugfixes on 0.1.0.x:
11188 - Refuse server descriptors if the fingerprint line doesn't match
11189 the included identity key. Tor doesn't care, but other apps (and
11190 humans) might actually be trusting the fingerprint line.
11191 - We used to kill the circuit when we receive a relay command we
11192 don't recognize. Now we just drop it.
11193 - Start obeying our firewall options more rigorously:
11194 . If we can't get to a dirserver directly, try going via Tor.
11195 . Don't ever try to connect (as a client) to a place our
11196 firewall options forbid.
11197 . If we specify a proxy and also firewall options, obey the
11198 firewall options even when we're using the proxy: some proxies
11199 can only proxy to certain destinations.
11200 - Fix a bug found by Lasse Overlier: when we were making internal
11201 circuits (intended to be cannibalized later for rendezvous and
11202 introduction circuits), we were picking them so that they had
11203 useful exit nodes. There was no need for this, and it actually
11204 aids some statistical attacks.
11205 - Start treating internal circuits and exit circuits separately.
11206 It's important to keep them separate because internal circuits
11207 have their last hops picked like middle hops, rather than like
11208 exit hops. So exiting on them will break the user's expectations.
11210 o Bugfixes on 0.1.1.x:
11211 - Take out the mis-feature where we tried to detect IP address
11212 flapping for people with DynDNS, and chose not to upload a new
11213 server descriptor sometimes.
11214 - Try to be compatible with OpenSSL 0.9.6 again.
11215 - Log fix: when the controller is logging about .onion addresses,
11216 sometimes it didn't include the ".onion" part of the address.
11217 - Don't try to modify options->DirServers internally -- if the
11218 user didn't specify any, just add the default ones directly to
11219 the trusted dirserver list. This fixes a bug where people running
11220 controllers would use SETCONF on some totally unrelated config
11221 option, and Tor would start yelling at them about changing their
11223 - Let the controller's redirectstream command specify a port, in
11224 case the controller wants to change that too.
11225 - When we requested a pile of server descriptors, we sometimes
11226 accidentally launched a duplicate request for the first one.
11227 - Bugfix for trackhostexits: write down the fingerprint of the
11228 chosen exit, not its nickname, because the chosen exit might not
11230 - When parsing foo.exit, if foo is unknown, and we are leaving
11231 circuits unattached, set the chosen_exit field and leave the
11232 address empty. This matters because controllers got confused
11234 - Directory authorities no longer try to download server
11235 descriptors that they know they will reject.
11237 o Features and updates:
11238 - Replace balanced trees with hash tables: this should make stuff
11239 significantly faster.
11240 - Resume using the AES counter-mode implementation that we ship,
11241 rather than OpenSSL's. Ours is significantly faster.
11242 - Many other CPU and memory improvements.
11243 - Add a new config option FastFirstHopPK (on by default) so clients
11244 do a trivial crypto handshake for their first hop, since TLS has
11245 already taken care of confidentiality and authentication.
11246 - Add a new config option TestSocks so people can see if their
11247 applications are using socks4, socks4a, socks5-with-ip, or
11248 socks5-with-hostname. This way they don't have to keep mucking
11249 with tcpdump and wondering if something got cached somewhere.
11250 - Warn when listening on a public address for socks. I suspect a
11251 lot of people are setting themselves up as open socks proxies,
11252 and they have no idea that jerks on the Internet are using them,
11253 since they simply proxy the traffic into the Tor network.
11254 - Add "private:*" as an alias in configuration for policies. Now
11255 you can simplify your exit policy rather than needing to list
11256 every single internal or nonroutable network space.
11257 - Add a new controller event type that allows controllers to get
11258 all server descriptors that were uploaded to a router in its role
11259 as authoritative dirserver.
11260 - Start shipping socks-extensions.txt, tor-doc-unix.html,
11261 tor-doc-server.html, and stylesheet.css in the tarball.
11262 - Stop shipping tor-doc.html in the tarball.
11265 Changes in version 0.1.1.9-alpha - 2005-11-15
11266 o Usability improvements:
11267 - Start calling it FooListenAddress rather than FooBindAddress,
11268 since few of our users know what it means to bind an address
11270 - Reduce clutter in server logs. We're going to try to make
11271 them actually usable now. New config option ProtocolWarnings that
11272 lets you hear about how _other Tors_ are breaking the protocol. Off
11274 - Divide log messages into logging domains. Once we put some sort
11275 of interface on this, it will let people looking at more verbose
11276 log levels specify the topics they want to hear more about.
11277 - Make directory servers return better http 404 error messages
11278 instead of a generic "Servers unavailable".
11279 - Check for even more Windows version flags when writing the platform
11280 string in server descriptors, and note any we don't recognize.
11281 - Clean up more of the OpenSSL memory when exiting, so we can detect
11282 memory leaks better.
11283 - Make directory authorities be non-versioning, non-naming by
11284 default. Now we can add new directory servers without requiring
11285 their operators to pay close attention.
11286 - When logging via syslog, include the pid whenever we provide
11287 a log entry. Suggested by Todd Fries.
11289 o Performance improvements:
11290 - Directory servers now silently throw away new descriptors that
11291 haven't changed much if the timestamps are similar. We do this to
11292 tolerate older Tor servers that upload a new descriptor every 15
11293 minutes. (It seemed like a good idea at the time.)
11294 - Inline bottleneck smartlist functions; use fast versions by default.
11295 - Add a "Map from digest to void*" abstraction digestmap_t so we
11296 can do less hex encoding/decoding. Use it in router_get_by_digest()
11297 to resolve a performance bottleneck.
11298 - Allow tor_gzip_uncompress to extract as much as possible from
11299 truncated compressed data. Try to extract as many
11300 descriptors as possible from truncated http responses (when
11301 DIR_PURPOSE_FETCH_ROUTERDESC).
11302 - Make circ->onionskin a pointer, not a static array. moria2 was using
11303 125000 circuit_t's after it had been up for a few weeks, which
11304 translates to 20+ megs of wasted space.
11305 - The private half of our EDH handshake keys are now chosen out
11306 of 320 bits, not 1024 bits. (Suggested by Ian Goldberg.)
11308 o Security improvements:
11309 - Start making directory caches retain old routerinfos, so soon
11310 clients can start asking by digest of descriptor rather than by
11311 fingerprint of server.
11312 - Add half our entropy from RAND_poll in OpenSSL. This knows how
11313 to use egd (if present), openbsd weirdness (if present), vms/os2
11314 weirdness (if we ever port there), and more in the future.
11316 o Bugfixes on 0.1.0.x:
11317 - Do round-robin writes of at most 16 kB per write. This might be
11318 more fair on loaded Tor servers, and it might resolve our Windows
11319 crash bug. It might also slow things down.
11320 - Our TLS handshakes were generating a single public/private
11321 keypair for the TLS context, rather than making a new one for
11322 each new connections. Oops. (But we were still rotating them
11323 periodically, so it's not so bad.)
11324 - When we were cannibalizing a circuit with a particular exit
11325 node in mind, we weren't checking to see if that exit node was
11326 already present earlier in the circuit. Oops.
11327 - When a Tor server's IP changes (e.g. from a dyndns address),
11328 upload a new descriptor so clients will learn too.
11329 - Really busy servers were keeping enough circuits open on stable
11330 connections that they were wrapping around the circuit_id
11331 space. (It's only two bytes.) This exposed a bug where we would
11332 feel free to reuse a circuit_id even if it still exists but has
11333 been marked for close. Try to fix this bug. Some bug remains.
11334 - If we would close a stream early (e.g. it asks for a .exit that
11335 we know would refuse it) but the LeaveStreamsUnattached config
11336 option is set by the controller, then don't close it.
11338 o Bugfixes on 0.1.1.8-alpha:
11339 - Fix a big pile of memory leaks, some of them serious.
11340 - Do not try to download a routerdesc if we would immediately reject
11342 - Resume inserting a newline between all router descriptors when
11343 generating (old style) signed directories, since our spec says
11345 - When providing content-type application/octet-stream for
11346 server descriptors using .z, we were leaving out the
11347 content-encoding header. Oops. (Everything tolerated this just
11348 fine, but that doesn't mean we need to be part of the problem.)
11349 - Fix a potential seg fault in getconf and getinfo using version 1
11350 of the controller protocol.
11351 - Avoid crash: do not check whether DirPort is reachable when we
11352 are suppressing it because of hibernation.
11353 - Make --hash-password not crash on exit.
11356 Changes in version 0.1.1.8-alpha - 2005-10-07
11357 o New features (major):
11358 - Clients don't download or use the directory anymore. Now they
11359 download and use network-statuses from the trusted dirservers,
11360 and fetch individual server descriptors as needed from mirrors.
11361 See dir-spec.txt for all the gory details.
11362 - Be more conservative about whether to advertise our DirPort.
11363 The main change is to not advertise if we're running at capacity
11364 and either a) we could hibernate or b) our capacity is low and
11365 we're using a default DirPort.
11366 - Use OpenSSL's AES when OpenSSL has version 0.9.7 or later.
11368 o New features (minor):
11369 - Try to be smart about when to retry network-status and
11370 server-descriptor fetches. Still needs some tuning.
11371 - Stop parsing, storing, or using running-routers output (but
11372 mirrors still cache and serve it).
11373 - Consider a threshold of versioning dirservers (dirservers who have
11374 an opinion about which Tor versions are still recommended) before
11375 deciding whether to warn the user that he's obsolete.
11376 - Dirservers can now reject/invalidate by key and IP, with the
11377 config options "AuthDirInvalid" and "AuthDirReject". This is
11378 useful since currently we automatically list servers as running
11379 and usable even if we know they're jerks.
11380 - Provide dire warnings to any users who set DirServer; move it out
11381 of torrc.sample and into torrc.complete.
11382 - Add MyFamily to torrc.sample in the server section.
11383 - Add nicknames to the DirServer line, so we can refer to them
11384 without requiring all our users to memorize their IP addresses.
11385 - When we get an EOF or a timeout on a directory connection, note
11386 how many bytes of serverdesc we are dropping. This will help
11387 us determine whether it is smart to parse incomplete serverdesc
11389 - Add a new function to "change pseudonyms" -- that is, to stop
11390 using any currently-dirty circuits for new streams, so we don't
11391 link new actions to old actions. Currently it's only called on
11392 HUP (or SIGNAL RELOAD).
11393 - On sighup, if UseHelperNodes changed to 1, use new circuits.
11394 - Start using RAND_bytes rather than RAND_pseudo_bytes from
11395 OpenSSL. Also, reseed our entropy every hour, not just at
11396 startup. And entropy in 512-bit chunks, not 160-bit chunks.
11398 o Fixes on 0.1.1.7-alpha:
11399 - Nobody ever implemented EVENT_ADDRMAP for control protocol
11400 version 0, so don't let version 0 controllers ask for it.
11401 - If you requested something with too many newlines via the
11402 v1 controller protocol, you could crash tor.
11403 - Fix a number of memory leaks, including some pretty serious ones.
11404 - Re-enable DirPort testing again, so Tor servers will be willing
11405 to advertise their DirPort if it's reachable.
11406 - On TLS handshake, only check the other router's nickname against
11407 its expected nickname if is_named is set.
11409 o Fixes forward-ported from 0.1.0.15:
11410 - Don't crash when we don't have any spare file descriptors and we
11411 try to spawn a dns or cpu worker.
11412 - Make the numbers in read-history and write-history into uint64s,
11413 so they don't overflow and publish negatives in the descriptor.
11415 o Fixes on 0.1.0.x:
11416 - For the OS X package's modified privoxy config file, comment
11417 out the "logfile" line so we don't log everything passed
11419 - We were whining about using socks4 or socks5-with-local-lookup
11420 even when it's an IP in the "virtual" range we designed exactly
11422 - We were leaking some memory every time the client changes IPs.
11423 - Never call free() on tor_malloc()d memory. This will help us
11424 use dmalloc to detect memory leaks.
11425 - Check for named servers when looking them up by nickname;
11426 warn when we'recalling a non-named server by its nickname;
11427 don't warn twice about the same name.
11428 - Try to list MyFamily elements by key, not by nickname, and warn
11429 if we've not heard of the server.
11430 - Make windows platform detection (uname equivalent) smarter.
11431 - It turns out sparc64 doesn't like unaligned access either.
11434 Changes in version 0.1.0.15 - 2005-09-23
11435 o Bugfixes on 0.1.0.x:
11436 - Reject ports 465 and 587 (spam targets) in default exit policy.
11437 - Don't crash when we don't have any spare file descriptors and we
11438 try to spawn a dns or cpu worker.
11439 - Get rid of IgnoreVersion undocumented config option, and make us
11440 only warn, never exit, when we're running an obsolete version.
11441 - Don't try to print a null string when your server finds itself to
11442 be unreachable and the Address config option is empty.
11443 - Make the numbers in read-history and write-history into uint64s,
11444 so they don't overflow and publish negatives in the descriptor.
11445 - Fix a minor memory leak in smartlist_string_remove().
11446 - We were only allowing ourselves to upload a server descriptor at
11447 most every 20 minutes, even if it changed earlier than that.
11448 - Clean up log entries that pointed to old URLs.
11451 Changes in version 0.1.1.7-alpha - 2005-09-14
11452 o Fixes on 0.1.1.6-alpha:
11453 - Exit servers were crashing when people asked them to make a
11454 connection to an address not in their exit policy.
11455 - Looking up a non-existent stream for a v1 control connection would
11457 - Fix a seg fault if we ask a dirserver for a descriptor by
11458 fingerprint but he doesn't know about him.
11459 - SETCONF was appending items to linelists, not clearing them.
11460 - SETCONF SocksBindAddress killed Tor if it fails to bind. Now back
11461 out and refuse the setconf if it would fail.
11462 - Downgrade the dirserver log messages when whining about
11466 - Add Peter Palfrader's check-tor script to tor/contrib/
11467 It lets you easily check whether a given server (referenced by
11468 nickname) is reachable by you.
11469 - Numerous changes to move towards client-side v2 directories. Not
11472 o Fixes on 0.1.0.x:
11473 - If the user gave tor an odd number of command-line arguments,
11474 we were silently ignoring the last one. Now we complain and fail.
11475 [This wins the oldest-bug prize -- this bug has been present since
11476 November 2002, as released in Tor 0.0.0.]
11477 - Do not use unaligned memory access on alpha, mips, or mipsel.
11478 It *works*, but is very slow, so we treat them as if it doesn't.
11479 - Retry directory requests if we fail to get an answer we like
11480 from a given dirserver (we were retrying before, but only if
11481 we fail to connect).
11482 - When writing the RecommendedVersions line, sort them first.
11483 - When the client asked for a rendezvous port that the hidden
11484 service didn't want to provide, we were sending an IP address
11485 back along with the end cell. Fortunately, it was zero. But stop
11487 - Correct "your server is reachable" log entries to indicate that
11488 it was self-testing that told us so.
11491 Changes in version 0.1.1.6-alpha - 2005-09-09
11492 o Fixes on 0.1.1.5-alpha:
11493 - We broke fascistfirewall in 0.1.1.5-alpha. Oops.
11494 - Fix segfault in unit tests in 0.1.1.5-alpha. Oops.
11495 - Fix bug with tor_memmem finding a match at the end of the string.
11496 - Make unit tests run without segfaulting.
11497 - Resolve some solaris x86 compile warnings.
11498 - Handle duplicate lines in approved-routers files without warning.
11499 - Fix bug where as soon as a server refused any requests due to his
11500 exit policy (e.g. when we ask for localhost and he tells us that's
11501 127.0.0.1 and he won't do it), we decided he wasn't obeying his
11502 exit policy using him for any exits.
11503 - Only do openssl hardware accelerator stuff if openssl version is
11506 o New controller features/fixes:
11507 - Add a "RESETCONF" command so you can set config options like
11508 AllowUnverifiedNodes and LongLivedPorts to "". Also, if you give
11509 a config option in the torrc with no value, then it clears it
11510 entirely (rather than setting it to its default).
11511 - Add a "GETINFO config-file" to tell us where torrc is.
11512 - Avoid sending blank lines when GETINFO replies should be empty.
11513 - Add a QUIT command for the controller (for using it manually).
11514 - Fix a bug in SAVECONF that was adding default dirservers and
11515 other redundant entries to the torrc file.
11517 o Start on the new directory design:
11518 - Generate, publish, cache, serve new network-status format.
11519 - Publish individual descriptors (by fingerprint, by "all", and by
11521 - Publish client and server recommended versions separately.
11522 - Allow tor_gzip_uncompress() to handle multiple concatenated
11523 compressed strings. Serve compressed groups of router
11524 descriptors. The compression logic here could be more
11526 - Distinguish v1 authorities (all currently trusted directories)
11527 from v2 authorities (all trusted directories).
11528 - Change DirServers config line to note which dirs are v1 authorities.
11529 - Add configuration option "V1AuthoritativeDirectory 1" which
11530 moria1, moria2, and tor26 should set.
11531 - Remove option when getting directory cache to see whether they
11532 support running-routers; they all do now. Replace it with one
11533 to see whether caches support v2 stuff.
11536 - Dirservers now do their own external reachability testing of each
11537 Tor server, and only list them as running if they've been found to
11538 be reachable. We also send back warnings to the server's logs if
11539 it uploads a descriptor that we already believe is unreachable.
11540 - Implement exit enclaves: if we know an IP address for the
11541 destination, and there's a running Tor server at that address
11542 which allows exit to the destination, then extend the circuit to
11543 that exit first. This provides end-to-end encryption and end-to-end
11544 authentication. Also, if the user wants a .exit address or enclave,
11545 use 4 hops rather than 3, and cannibalize a general circ for it
11547 - Permit transitioning from ORPort=0 to ORPort!=0, and back, from the
11548 controller. Also, rotate dns and cpu workers if the controller
11549 changes options that will affect them; and initialize the dns
11550 worker cache tree whether or not we start out as a server.
11551 - Only upload a new server descriptor when options change, 18
11552 hours have passed, uptime is reset, or bandwidth changes a lot.
11553 - Check [X-]Forwarded-For headers in HTTP requests when generating
11554 log messages. This lets people run dirservers (and caches) behind
11555 Apache but still know which IP addresses are causing warnings.
11557 o Config option changes:
11558 - Replace (Fascist)Firewall* config options with a new
11559 ReachableAddresses option that understands address policies.
11560 For example, "ReachableAddresses *:80,*:443"
11561 - Get rid of IgnoreVersion undocumented config option, and make us
11562 only warn, never exit, when we're running an obsolete version.
11563 - Make MonthlyAccountingStart config option truly obsolete now.
11565 o Fixes on 0.1.0.x:
11566 - Reject ports 465 and 587 in the default exit policy, since
11567 people have started using them for spam too.
11568 - It turns out we couldn't bootstrap a network since we added
11569 reachability detection in 0.1.0.1-rc. Good thing the Tor network
11570 has never gone down. Add an AssumeReachable config option to let
11571 servers and dirservers bootstrap. When we're trying to build a
11572 high-uptime or high-bandwidth circuit but there aren't enough
11573 suitable servers, try being less picky rather than simply failing.
11574 - Our logic to decide if the OR we connected to was the right guy
11575 was brittle and maybe open to a mitm for unverified routers.
11576 - We weren't cannibalizing circuits correctly for
11577 CIRCUIT_PURPOSE_C_ESTABLISH_REND and
11578 CIRCUIT_PURPOSE_S_ESTABLISH_INTRO, so we were being forced to
11579 build those from scratch. This should make hidden services faster.
11580 - Predict required circuits better, with an eye toward making hidden
11581 services faster on the service end.
11582 - Retry streams if the exit node sends back a 'misc' failure. This
11583 should result in fewer random failures. Also, after failing
11584 from resolve failed or misc, reset the num failures, so we give
11585 it a fair shake next time we try.
11586 - Clean up the rendezvous warn log msgs, and downgrade some to info.
11587 - Reduce severity on logs about dns worker spawning and culling.
11588 - When we're shutting down and we do something like try to post a
11589 server descriptor or rendezvous descriptor, don't complain that
11590 we seem to be unreachable. Of course we are, we're shutting down.
11591 - Add TTLs to RESOLVED, CONNECTED, and END_REASON_EXITPOLICY cells.
11592 We don't use them yet, but maybe one day our DNS resolver will be
11593 able to discover them.
11594 - Make ContactInfo mandatory for authoritative directory servers.
11595 - Require server descriptors to list IPv4 addresses -- hostnames
11596 are no longer allowed. This also fixes some potential security
11597 problems with people providing hostnames as their address and then
11598 preferentially resolving them to partition users.
11599 - Change log line for unreachability to explicitly suggest /etc/hosts
11600 as the culprit. Also make it clearer what IP address and ports we're
11601 testing for reachability.
11602 - Put quotes around user-supplied strings when logging so users are
11603 more likely to realize if they add bad characters (like quotes)
11605 - Let auth dir servers start without specifying an Address config
11607 - Make unit tests (and other invocations that aren't the real Tor)
11608 run without launching listeners, creating subdirectories, and so on.
11611 Changes in version 0.1.1.5-alpha - 2005-08-08
11612 o Bugfixes included in 0.1.0.14.
11614 o Bugfixes on 0.1.0.x:
11615 - If you write "HiddenServicePort 6667 127.0.0.1 6668" in your
11616 torrc rather than "HiddenServicePort 6667 127.0.0.1:6668",
11617 it would silently using ignore the 6668.
11620 Changes in version 0.1.0.14 - 2005-08-08
11621 o Bugfixes on 0.1.0.x:
11622 - Fix the other half of the bug with crypto handshakes
11624 - Fix an assert trigger if you send a 'signal term' via the
11625 controller when it's listening for 'event info' messages.
11628 Changes in version 0.1.1.4-alpha - 2005-08-04
11629 o Bugfixes included in 0.1.0.13.
11632 - Improve tor_gettimeofday() granularity on windows.
11633 - Make clients regenerate their keys when their IP address changes.
11634 - Implement some more GETINFO goodness: expose helper nodes, config
11635 options, getinfo keys.
11638 Changes in version 0.1.0.13 - 2005-08-04
11639 o Bugfixes on 0.1.0.x:
11640 - Fix a critical bug in the security of our crypto handshakes.
11641 - Fix a size_t underflow in smartlist_join_strings2() that made
11642 it do bad things when you hand it an empty smartlist.
11643 - Fix Windows installer to ship Tor license (thanks to Aphex for
11644 pointing out this oversight) and put a link to the doc directory
11646 - Explicitly set no-unaligned-access for sparc: it turns out the
11647 new gcc's let you compile broken code, but that doesn't make it
11651 Changes in version 0.1.1.3-alpha - 2005-07-23
11652 o Bugfixes on 0.1.1.2-alpha:
11653 - Fix a bug in handling the controller's "post descriptor"
11655 - Fix several bugs in handling the controller's "extend circuit"
11657 - Fix a bug in handling the controller's "stream status" event.
11658 - Fix an assert failure if we have a controller listening for
11659 circuit events and we go offline.
11660 - Re-allow hidden service descriptors to publish 0 intro points.
11661 - Fix a crash when generating your hidden service descriptor if
11662 you don't have enough intro points already.
11664 o New features on 0.1.1.2-alpha:
11665 - New controller function "getinfo accounting", to ask how
11666 many bytes we've used in this time period.
11667 - Experimental support for helper nodes: a lot of the risk from
11668 a small static adversary comes because users pick new random
11669 nodes every time they rebuild a circuit. Now users will try to
11670 stick to the same small set of entry nodes if they can. Not
11671 enabled by default yet.
11673 o Bugfixes on 0.1.0.12:
11674 - If you're an auth dir server, always publish your dirport,
11675 even if you haven't yet found yourself to be reachable.
11676 - Fix a size_t underflow in smartlist_join_strings2() that made
11677 it do bad things when you hand it an empty smartlist.
11680 Changes in version 0.1.0.12 - 2005-07-18
11681 o New directory servers:
11682 - tor26 has changed IP address.
11684 o Bugfixes on 0.1.0.x:
11685 - Fix a possible double-free in tor_gzip_uncompress().
11686 - When --disable-threads is set, do not search for or link against
11687 pthreads libraries.
11688 - Don't trigger an assert if an authoritative directory server
11689 claims its dirport is 0.
11690 - Fix bug with removing Tor as an NT service: some people were
11691 getting "The service did not return an error." Thanks to Matt
11695 Changes in version 0.1.1.2-alpha - 2005-07-15
11696 o New directory servers:
11697 - tor26 has changed IP address.
11699 o Bugfixes on 0.1.0.x, crashes/leaks:
11700 - Port the servers-not-obeying-their-exit-policies fix from
11702 - Fix an fd leak in start_daemon().
11703 - On Windows, you can't always reopen a port right after you've
11704 closed it. So change retry_listeners() to only close and re-open
11705 ports that have changed.
11706 - Fix a possible double-free in tor_gzip_uncompress().
11708 o Bugfixes on 0.1.0.x, usability:
11709 - When tor_socketpair() fails in Windows, give a reasonable
11710 Windows-style errno back.
11711 - Let people type "tor --install" as well as "tor -install" when
11713 want to make it an NT service.
11714 - NT service patch from Matt Edman to improve error messages.
11715 - When the controller asks for a config option with an abbreviated
11716 name, give the full name in our response.
11717 - Correct the man page entry on TrackHostExitsExpire.
11718 - Looks like we were never delivering deflated (i.e. compressed)
11719 running-routers lists, even when asked. Oops.
11720 - When --disable-threads is set, do not search for or link against
11721 pthreads libraries.
11723 o Bugfixes on 0.1.1.x:
11724 - Fix a seg fault with autodetecting which controller version is
11728 - New hidden service descriptor format: put a version in it, and
11729 let people specify introduction/rendezvous points that aren't
11730 in "the directory" (which is subjective anyway).
11731 - Allow the DEBUG controller event to work again. Mark certain log
11732 entries as "don't tell this to controllers", so we avoid cycles.
11735 Changes in version 0.1.0.11 - 2005-06-30
11736 o Bugfixes on 0.1.0.x:
11737 - Fix major security bug: servers were disregarding their
11738 exit policies if clients behaved unexpectedly.
11739 - Make OS X init script check for missing argument, so we don't
11740 confuse users who invoke it incorrectly.
11741 - Fix a seg fault in "tor --hash-password foo".
11742 - The MAPADDRESS control command was broken.
11745 Changes in version 0.1.1.1-alpha - 2005-06-29
11747 - Make OS X init script check for missing argument, so we don't
11748 confuse users who invoke it incorrectly.
11749 - Fix a seg fault in "tor --hash-password foo".
11750 - Fix a possible way to DoS dirservers.
11751 - When we complain that your exit policy implicitly allows local or
11752 private address spaces, name them explicitly so operators can
11754 - Make the log message less scary when all the dirservers are
11755 temporarily unreachable.
11756 - We were printing the number of idle dns workers incorrectly when
11760 - Revised controller protocol (version 1) that uses ascii rather
11761 than binary. Add supporting libraries in python and java so you
11762 can use the controller from your applications without caring how
11763 our protocol works.
11764 - Spiffy new support for crypto hardware accelerators. Can somebody
11768 Changes in version 0.0.9.10 - 2005-06-16
11769 o Bugfixes on 0.0.9.x (backported from 0.1.0.10):
11770 - Refuse relay cells that claim to have a length larger than the
11771 maximum allowed. This prevents a potential attack that could read
11772 arbitrary memory (e.g. keys) from an exit server's process
11776 Changes in version 0.1.0.10 - 2005-06-14
11777 o Allow a few EINVALs from libevent before dying. Warn on kqueue with
11778 libevent before 1.1a.
11781 Changes in version 0.1.0.9-rc - 2005-06-09
11783 - Reset buf->highwater every time buf_shrink() is called, not just on
11784 a successful shrink. This was causing significant memory bloat.
11785 - Fix buffer overflow when checking hashed passwords.
11786 - Security fix: if seeding the RNG on Win32 fails, quit.
11787 - Allow seeding the RNG on Win32 even when you're not running as
11789 - Disable threading on Solaris too. Something is wonky with it,
11790 cpuworkers, and reentrant libs.
11791 - Reenable the part of the code that tries to flush as soon as an
11792 OR outbuf has a full TLS record available. Perhaps this will make
11793 OR outbufs not grow as huge except in rare cases, thus saving lots
11794 of CPU time plus memory.
11795 - Reject malformed .onion addresses rather then passing them on as
11796 normal web requests.
11797 - Adapt patch from Adam Langley: fix possible memory leak in
11798 tor_lookup_hostname().
11799 - Initialize libevent later in the startup process, so the logs are
11800 already established by the time we start logging libevent warns.
11801 - Use correct errno on win32 if libevent fails.
11802 - Check and warn about known-bad/slow libevent versions.
11803 - Pay more attention to the ClientOnly config option.
11804 - Have torctl.in/tor.sh.in check for location of su binary (needed
11806 - Correct/add man page entries for LongLivedPorts, ExitPolicy,
11807 KeepalivePeriod, ClientOnly, NoPublish, HttpProxy, HttpsProxy,
11808 HttpProxyAuthenticator
11809 - Stop warning about sigpipes in the logs. We're going to
11810 pretend that getting these occassionally is normal and fine.
11811 - Resolve OS X installer bugs: stop claiming to be 0.0.9.2 in
11813 installer screens; and don't put stuff into StartupItems unless
11814 the user asks you to.
11815 - Require servers that use the default dirservers to have public IP
11816 addresses. We have too many servers that are configured with private
11817 IPs and their admins never notice the log entries complaining that
11818 their descriptors are being rejected.
11819 - Add OSX uninstall instructions. An actual uninstall script will
11823 Changes in version 0.1.0.8-rc - 2005-05-23
11825 - It turns out that kqueue on OS X 10.3.9 was causing kernel
11826 panics. Disable kqueue on all OS X Tors.
11827 - Fix RPM: remove duplicate line accidentally added to the rpm
11829 - Disable threads on openbsd too, since its gethostaddr is not
11831 - Tolerate libevent 0.8 since it still works, even though it's
11833 - Enable building on Red Hat 9.0 again.
11834 - Allow the middle hop of the testing circuit to be running any
11835 version, now that most of them have the bugfix to let them connect
11836 to unknown servers. This will allow reachability testing to work
11837 even when 0.0.9.7-0.0.9.9 become obsolete.
11838 - Handle relay cells with rh.length too large. This prevents
11839 a potential attack that could read arbitrary memory (maybe even
11840 keys) from the exit server's process.
11841 - We screwed up the dirport reachability testing when we don't yet
11842 have a cached version of the directory. Hopefully now fixed.
11843 - Clean up router_load_single_router() (used by the controller),
11844 so it doesn't seg fault on error.
11845 - Fix a minor memory leak when somebody establishes an introduction
11846 point at your Tor server.
11847 - If a socks connection ends because read fails, don't warn that
11848 you're not sending a socks reply back.
11851 - Add HttpProxyAuthenticator config option too, that works like
11852 the HttpsProxyAuthenticator config option.
11853 - Encode hashed controller passwords in hex instead of base64,
11854 to make it easier to write controllers.
11857 Changes in version 0.1.0.7-rc - 2005-05-17
11859 - Fix a bug in the OS X package installer that prevented it from
11860 installing on Tiger.
11861 - Fix a script bug in the OS X package installer that made it
11862 complain during installation.
11863 - Find libevent even if it's hiding in /usr/local/ and your
11864 CFLAGS and LDFLAGS don't tell you to look there.
11865 - Be able to link with libevent as a shared library (the default
11866 after 1.0d), even if it's hiding in /usr/local/lib and even
11867 if you haven't added /usr/local/lib to your /etc/ld.so.conf,
11868 assuming you're running gcc. Otherwise fail and give a useful
11870 - Fix a bug in the RPM packager: set home directory for _tor to
11871 something more reasonable when first installing.
11872 - Free a minor amount of memory that is still reachable on exit.
11875 Changes in version 0.1.0.6-rc - 2005-05-14
11877 - Implement --disable-threads configure option. Disable threads on
11878 netbsd by default, because it appears to have no reentrant resolver
11880 - Apple's OS X 10.4.0 ships with a broken kqueue. The new libevent
11881 release (1.1) detects and disables kqueue if it's broken.
11882 - Append default exit policy before checking for implicit internal
11883 addresses. Now we don't log a bunch of complaints on startup
11884 when using the default exit policy.
11885 - Some people were putting "Address " in their torrc, and they had
11886 a buggy resolver that resolved " " to 0.0.0.0. Oops.
11887 - If DataDir is ~/.tor, and that expands to /.tor, then default to
11888 LOCALSTATEDIR/tor instead.
11889 - Fix fragmented-message bug in TorControl.py.
11890 - Resolve a minor bug which would prevent unreachable dirports
11891 from getting suppressed in the published descriptor.
11892 - When the controller gave us a new descriptor, we weren't resolving
11893 it immediately, so Tor would think its address was 0.0.0.0 until
11894 we fetched a new directory.
11895 - Fix an uppercase/lowercase case error in suppressing a bogus
11896 libevent warning on some Linuxes.
11899 - Begin scrubbing sensitive strings from logs by default. Turn off
11900 the config option SafeLogging if you need to do debugging.
11901 - Switch to a new buffer management algorithm, which tries to avoid
11902 reallocing and copying quite as much. In first tests it looks like
11903 it uses *more* memory on average, but less cpu.
11904 - First cut at support for "create-fast" cells. Clients can use
11905 these when extending to their first hop, since the TLS already
11906 provides forward secrecy and authentication. Not enabled on
11908 - When dirservers refuse a router descriptor, we now log its
11909 contactinfo, platform, and the poster's IP address.
11910 - Call tor_free_all instead of connections_free_all after forking, to
11911 save memory on systems that need to fork.
11912 - Whine at you if you're a server and you don't set your contactinfo.
11913 - Implement --verify-config command-line option to check if your torrc
11914 is valid without actually launching Tor.
11915 - Rewrite address "serifos.exit" to "localhost.serifos.exit"
11916 rather than just rejecting it.
11919 Changes in version 0.1.0.5-rc - 2005-04-27
11921 - Stop trying to print a null pointer if an OR conn fails because
11922 we didn't like its cert.
11924 - Switch our internal buffers implementation to use a ring buffer,
11925 to hopefully improve performance for fast servers a lot.
11926 - Add HttpsProxyAuthenticator support (basic auth only), based
11927 on patch from Adam Langley.
11928 - Bump the default BandwidthRate from 1 MB to 2 MB, to accommodate
11929 the fast servers that have been joining lately.
11930 - Give hidden service accesses extra time on the first attempt,
11931 since 60 seconds is often only barely enough. This might improve
11933 - Improve performance for dirservers: stop re-parsing the whole
11934 directory every time you regenerate it.
11935 - Add more debugging info to help us find the weird dns freebsd
11936 pthreads bug; cleaner debug messages to help track future issues.
11939 Changes in version 0.0.9.9 - 2005-04-23
11940 o Bugfixes on 0.0.9.x:
11941 - If unofficial Tor clients connect and send weird TLS certs, our
11942 Tor server triggers an assert. This release contains a minimal
11943 backport from the broader fix that we put into 0.1.0.4-rc.
11946 Changes in version 0.1.0.4-rc - 2005-04-23
11948 - If unofficial Tor clients connect and send weird TLS certs, our
11949 Tor server triggers an assert. Stop asserting, and start handling
11950 TLS errors better in other situations too.
11951 - When the controller asks us to tell it about all the debug-level
11952 logs, it turns out we were generating debug-level logs while
11953 telling it about them, which turns into a bad loop. Now keep
11954 track of whether you're sending a debug log to the controller,
11955 and don't log when you are.
11956 - Fix the "postdescriptor" feature of the controller interface: on
11957 non-complete success, only say "done" once.
11959 - Clients are now willing to load balance over up to 2mB, not 1mB,
11960 of advertised bandwidth capacity.
11961 - Add a NoPublish config option, so you can be a server (e.g. for
11962 testing running Tor servers in other Tor networks) without
11963 publishing your descriptor to the primary dirservers.
11966 Changes in version 0.1.0.3-rc - 2005-04-08
11967 o Improvements on 0.1.0.2-rc:
11968 - Client now retries when streams end early for 'hibernating' or
11969 'resource limit' reasons, rather than failing them.
11970 - More automated handling for dirserver operators:
11971 - Automatically approve nodes running 0.1.0.2-rc or later,
11972 now that the the reachability detection stuff is working.
11973 - Now we allow two unverified servers with the same nickname
11974 but different keys. But if a nickname is verified, only that
11975 nickname+key are allowed.
11976 - If you're an authdirserver connecting to an address:port,
11977 and it's not the OR you were expecting, forget about that
11978 descriptor. If he *was* the one you were expecting, then forget
11979 about all other descriptors for that address:port.
11980 - Allow servers to publish descriptors from 12 hours in the future.
11981 Corollary: only whine about clock skew from the dirserver if
11982 he's a trusted dirserver (since now even verified servers could
11983 have quite wrong clocks).
11984 - Adjust maximum skew and age for rendezvous descriptors: let skew
11985 be 48 hours rather than 90 minutes.
11986 - Efficiency improvements:
11987 - Keep a big splay tree of (circid,orconn)->circuit mappings to make
11988 it much faster to look up a circuit for each relay cell.
11989 - Remove most calls to assert_all_pending_dns_resolves_ok(),
11990 since they're eating our cpu on exit nodes.
11991 - Stop wasting time doing a case insensitive comparison for every
11992 dns name every time we do any lookup. Canonicalize the names to
11993 lowercase and be done with it.
11994 - Start sending 'truncated' cells back rather than destroy cells,
11995 if the circuit closes in front of you. This means we won't have
11996 to abandon partially built circuits.
11997 - Only warn once per nickname from add_nickname_list_to_smartlist
11998 per failure, so an entrynode or exitnode choice that's down won't
12000 - Put a note in the torrc about abuse potential with the default
12002 - Revise control spec and implementation to allow all log messages to
12003 be sent to controller with their severities intact (suggested by
12004 Matt Edman). Update TorControl to handle new log event types.
12005 - Provide better explanation messages when controller's POSTDESCRIPTOR
12007 - Stop putting nodename in the Platform string in server descriptors.
12008 It doesn't actually help, and it is confusing/upsetting some people.
12010 o Bugfixes on 0.1.0.2-rc:
12011 - We were printing the host mask wrong in exit policies in server
12012 descriptors. This isn't a critical bug though, since we were still
12013 obeying the exit policy internally.
12014 - Fix Tor when compiled with libevent but without pthreads: move
12015 connection_unregister() from _connection_free() to
12017 - Fix an assert trigger (already fixed in 0.0.9.x): when we have
12018 the rare mysterious case of accepting a conn on 0.0.0.0:0, then
12019 when we look through the connection array, we'll find any of the
12020 cpu/dnsworkers. This is no good.
12022 o Bugfixes on 0.0.9.8:
12023 - Fix possible bug on threading platforms (e.g. win32) which was
12024 leaking a file descriptor whenever a cpuworker or dnsworker died.
12025 - When using preferred entry or exit nodes, ignore whether the
12026 circuit wants uptime or capacity. They asked for the nodes, they
12028 - chdir() to your datadirectory at the *end* of the daemonize process,
12029 not the beginning. This was a problem because the first time you
12030 run tor, if your datadir isn't there, and you have runasdaemon set
12031 to 1, it will try to chdir to it before it tries to create it. Oops.
12032 - Handle changed router status correctly when dirserver reloads
12033 fingerprint file. We used to be dropping all unverified descriptors
12034 right then. The bug was hidden because we would immediately
12035 fetch a directory from another dirserver, which would include the
12036 descriptors we just dropped.
12037 - When we're connecting to an OR and he's got a different nickname/key
12038 than we were expecting, only complain loudly if we're an OP or a
12039 dirserver. Complaining loudly to the OR admins just confuses them.
12040 - Tie MAX_DIR_SIZE to MAX_BUF_SIZE, so now directory sizes won't get
12041 artificially capped at 500kB.
12044 Changes in version 0.0.9.8 - 2005-04-07
12045 o Bugfixes on 0.0.9.x:
12046 - We have a bug that I haven't found yet. Sometimes, very rarely,
12047 cpuworkers get stuck in the 'busy' state, even though the cpuworker
12048 thinks of itself as idle. This meant that no new circuits ever got
12049 established. Here's a workaround to kill any cpuworker that's been
12050 busy for more than 100 seconds.
12053 Changes in version 0.1.0.2-rc - 2005-04-01
12054 o Bugfixes on 0.1.0.1-rc:
12055 - Fixes on reachability detection:
12056 - Don't check for reachability while hibernating.
12057 - If ORPort is reachable but DirPort isn't, still publish the
12058 descriptor, but zero out DirPort until it's found reachable.
12059 - When building testing circs for ORPort testing, use only
12060 high-bandwidth nodes, so fewer circuits fail.
12061 - Complain about unreachable ORPort separately from unreachable
12062 DirPort, so the user knows what's going on.
12063 - Make sure we only conclude ORPort reachability if we didn't
12064 initiate the conn. Otherwise we could falsely conclude that
12065 we're reachable just because we connected to the guy earlier
12066 and he used that same pipe to extend to us.
12067 - Authdirservers shouldn't do ORPort reachability detection,
12068 since they're in clique mode, so it will be rare to find a
12069 server not already connected to them.
12070 - When building testing circuits, always pick middle hops running
12071 Tor 0.0.9.7, so we avoid the "can't extend to unknown routers"
12072 bug. (This is a kludge; it will go away when 0.0.9.x becomes
12074 - When we decide we're reachable, actually publish our descriptor
12076 - Fix bug in redirectstream in the controller.
12077 - Fix the state descriptor strings so logs don't claim edge streams
12078 are in a different state than they actually are.
12079 - Use recent libevent features when possible (this only really affects
12080 win32 and osx right now, because the new libevent with these
12081 features hasn't been released yet). Add code to suppress spurious
12083 - Prevent possible segfault in connection_close_unattached_ap().
12084 - Fix newlines on torrc in win32.
12085 - Improve error msgs when tor-resolve fails.
12087 o Improvements on 0.0.9.x:
12088 - New experimental script tor/contrib/ExerciseServer.py (needs more
12089 work) that uses the controller interface to build circuits and
12090 fetch pages over them. This will help us bootstrap servers that
12091 have lots of capacity but haven't noticed it yet.
12092 - New experimental script tor/contrib/PathDemo.py (needs more work)
12093 that uses the controller interface to let you choose whole paths
12095 "<hostname>.<path,separated by dots>.<length of path>.path"
12096 - When we've connected to an OR and handshaked but didn't like
12097 the result, we were closing the conn without sending destroy
12098 cells back for pending circuits. Now send those destroys.
12101 Changes in version 0.0.9.7 - 2005-04-01
12102 o Bugfixes on 0.0.9.x:
12103 - Fix another race crash bug (thanks to Glenn Fink for reporting).
12104 - Compare identity to identity, not to nickname, when extending to
12105 a router not already in the directory. This was preventing us from
12106 extending to unknown routers. Oops.
12107 - Make sure to create OS X Tor user in <500 range, so we aren't
12108 creating actual system users.
12109 - Note where connection-that-hasn't-sent-end was marked, and fix
12110 a few really loud instances of this harmless bug (it's fixed more
12114 Changes in version 0.1.0.1-rc - 2005-03-28
12116 - Add reachability testing. Your Tor server will automatically try
12117 to see if its ORPort and DirPort are reachable from the outside,
12118 and it won't upload its descriptor until it decides they are.
12119 - Handle unavailable hidden services better. Handle slow or busy
12120 hidden services better.
12121 - Add support for CONNECTing through https proxies, with "HttpsProxy"
12123 - New exit policy: accept most low-numbered ports, rather than
12124 rejecting most low-numbered ports.
12125 - More Tor controller support (still experimental). See
12126 http://tor.eff.org/doc/control-spec.txt for all the new features,
12127 including signals to emulate unix signals from any platform;
12128 redirectstream; extendcircuit; mapaddress; getinfo; postdescriptor;
12129 closestream; closecircuit; etc.
12130 - Make nt services work and start on startup on win32 (based on
12131 patch by Matt Edman).
12132 - Add a new AddressMap config directive to rewrite incoming socks
12133 addresses. This lets you, for example, declare an implicit
12134 required exit node for certain sites.
12135 - Add a new TrackHostExits config directive to trigger addressmaps
12136 for certain incoming socks addresses -- for sites that break when
12137 your exit keeps changing (based on patch by Mike Perry).
12138 - Redo the client-side dns cache so it's just an addressmap too.
12139 - Notice when our IP changes, and reset stats/uptime/reachability.
12140 - When an application is using socks5, give him the whole variety of
12141 potential socks5 responses (connect refused, host unreachable, etc),
12142 rather than just "success" or "failure".
12143 - A more sane version numbering system. See
12144 http://tor.eff.org/cvs/tor/doc/version-spec.txt for details.
12145 - New contributed script "exitlist": a simple python script to
12146 parse directories and find Tor nodes that exit to listed
12148 - New contributed script "privoxy-tor-toggle" to toggle whether
12149 Privoxy uses Tor. Seems to be configured for Debian by default.
12150 - Report HTTP reasons to client when getting a response from directory
12151 servers -- so you can actually know what went wrong.
12152 - New config option MaxAdvertisedBandwidth which lets you advertise
12153 a low bandwidthrate (to not attract as many circuits) while still
12154 allowing a higher bandwidthrate in reality.
12156 o Robustness/stability fixes:
12157 - Make Tor use Niels Provos's libevent instead of its current
12158 poll-but-sometimes-select mess. This will let us use faster async
12159 cores (like epoll, kpoll, and /dev/poll), and hopefully work better
12161 - pthread support now too. This was forced because when we forked,
12162 we ended up wasting a lot of duplicate ram over time. Also switch
12163 to foo_r versions of some library calls to allow reentry and
12165 - Better handling for heterogeneous / unreliable nodes:
12166 - Annotate circuits w/ whether they aim to contain high uptime nodes
12167 and/or high capacity nodes. When building circuits, choose
12169 - This means that every single node in an intro rend circuit,
12170 not just the last one, will have a minimum uptime.
12171 - New config option LongLivedPorts to indicate application streams
12172 that will want high uptime circuits.
12173 - Servers reset uptime when a dir fetch entirely fails. This
12174 hopefully reflects stability of the server's network connectivity.
12175 - If somebody starts his tor server in Jan 2004 and then fixes his
12176 clock, don't make his published uptime be a year.
12177 - Reset published uptime when you wake up from hibernation.
12178 - Introduce a notion of 'internal' circs, which are chosen without
12179 regard to the exit policy of the last hop. Intro and rendezvous
12180 circs must be internal circs, to avoid leaking information. Resolve
12181 and connect streams can use internal circs if they want.
12182 - New circuit pooling algorithm: make sure to have enough circs around
12183 to satisfy any predicted ports, and also make sure to have 2 internal
12184 circs around if we've required internal circs lately (and with high
12185 uptime if we've seen that lately too).
12186 - Split NewCircuitPeriod option into NewCircuitPeriod (30 secs),
12187 which describes how often we retry making new circuits if current
12188 ones are dirty, and MaxCircuitDirtiness (10 mins), which describes
12189 how long we're willing to make use of an already-dirty circuit.
12190 - Cannibalize GENERAL circs to be C_REND, C_INTRO, S_INTRO, and S_REND
12191 circ as necessary, if there are any completed ones lying around
12192 when we try to launch one.
12193 - Make hidden services try to establish a rendezvous for 30 seconds,
12194 rather than for n (where n=3) attempts to build a circuit.
12195 - Change SHUTDOWN_WAIT_LENGTH from a fixed 30 secs to a config option
12196 "ShutdownWaitLength".
12197 - Try to be more zealous about calling connection_edge_end when
12198 things go bad with edge conns in connection.c.
12199 - Revise tor-spec to add more/better stream end reasons.
12200 - Revise all calls to connection_edge_end to avoid sending "misc",
12201 and to take errno into account where possible.
12204 - Fix a race condition that can trigger an assert, when we have a
12205 pending create cell and an OR connection fails right then.
12206 - Fix several double-mark-for-close bugs, e.g. where we were finding
12207 a conn for a cell even if that conn is already marked for close.
12208 - Make sequence of log messages when starting on win32 with no config
12209 file more reasonable.
12210 - When choosing an exit node for a new non-internal circ, don't take
12211 into account whether it'll be useful for any pending x.onion
12212 addresses -- it won't.
12213 - Turn addr_policy_compare from a tristate to a quadstate; this should
12214 help address our "Ah, you allow 1.2.3.4:80. You are a good choice
12215 for google.com" problem.
12216 - Make "platform" string in descriptor more accurate for Win32 servers,
12217 so it's not just "unknown platform".
12218 - Fix an edge case in parsing config options (thanks weasel).
12219 If they say "--" on the commandline, it's not an option.
12220 - Reject odd-looking addresses at the client (e.g. addresses that
12221 contain a colon), rather than having the server drop them because
12223 - tor-resolve requests were ignoring .exit if there was a working circuit
12224 they could use instead.
12225 - REUSEADDR on normal platforms means you can rebind to the port
12226 right after somebody else has let it go. But REUSEADDR on win32
12227 means to let you bind to the port _even when somebody else
12228 already has it bound_! So, don't do that on Win32.
12229 - Change version parsing logic: a version is "obsolete" if it is not
12230 recommended and (1) there is a newer recommended version in the
12231 same series, or (2) there are no recommended versions in the same
12232 series, but there are some recommended versions in a newer series.
12233 A version is "new" if it is newer than any recommended version in
12235 - Stop most cases of hanging up on a socks connection without sending
12239 - Require BandwidthRate to be at least 20kB/s for servers.
12240 - When a dirserver causes you to give a warn, mention which dirserver
12242 - New config option DirAllowPrivateAddresses for authdirservers.
12243 Now by default they refuse router descriptors that have non-IP or
12244 private-IP addresses.
12245 - Stop publishing socksport in the directory, since it's not
12246 actually meant to be public. For compatibility, publish a 0 there
12248 - Change DirFetchPeriod/StatusFetchPeriod to have a special "Be
12249 smart" value, that is low for servers and high for clients.
12250 - If our clock jumps forward by 100 seconds or more, assume something
12251 has gone wrong with our network and abandon all not-yet-used circs.
12252 - Warn when exit policy implicitly allows local addresses.
12253 - If we get an incredibly skewed timestamp from a dirserver mirror
12254 that isn't a verified OR, don't warn -- it's probably him that's
12256 - Since we ship our own Privoxy on OS X, tweak it so it doesn't write
12257 cookies to disk and doesn't log each web request to disk. (Thanks
12258 to Brett Carrington for pointing this out.)
12259 - When a client asks us for a dir mirror and we don't have one,
12260 launch an attempt to get a fresh one.
12261 - If we're hibernating and we get a SIGINT, exit immediately.
12262 - Add --with-dmalloc ./configure option, to track memory leaks.
12263 - And try to free all memory on closing, so we can detect what
12265 - Cache local dns resolves correctly even when they're .exit
12267 - Give a better warning when some other server advertises an
12268 ORPort that is actually an apache running ssl.
12269 - Add "opt hibernating 1" to server descriptor to make it clearer
12270 whether the server is hibernating.
12273 Changes in version 0.0.9.6 - 2005-03-24
12274 o Bugfixes on 0.0.9.x (crashes and asserts):
12275 - Add new end stream reasons to maintainance branch. Fix bug where
12276 reason (8) could trigger an assert. Prevent bug from recurring.
12277 - Apparently win32 stat wants paths to not end with a slash.
12278 - Fix assert triggers in assert_cpath_layer_ok(), where we were
12279 blowing away the circuit that conn->cpath_layer points to, then
12280 checking to see if the circ is well-formed. Backport check to make
12281 sure we dont use the cpath on a closed connection.
12282 - Prevent circuit_resume_edge_reading_helper() from trying to package
12283 inbufs for marked-for-close streams.
12284 - Don't crash on hup if your options->address has become unresolvable.
12285 - Some systems (like OS X) sometimes accept() a connection and tell
12286 you the remote host is 0.0.0.0:0. If this happens, due to some
12287 other mis-features, we get confused; so refuse the conn for now.
12289 o Bugfixes on 0.0.9.x (other):
12290 - Fix harmless but scary "Unrecognized content encoding" warn message.
12291 - Add new stream error reason: TORPROTOCOL reason means "you are not
12292 speaking a version of Tor I understand; say bye-bye to your stream."
12293 - Be willing to cache directories from up to ROUTER_MAX_AGE seconds
12294 into the future, now that we are more tolerant of skew. This
12295 resolves a bug where a Tor server would refuse to cache a directory
12296 because all the directories it gets are too far in the future;
12297 yet the Tor server never logs any complaints about clock skew.
12298 - Mac packaging magic: make man pages useable, and do not overwrite
12299 existing torrc files.
12300 - Make OS X log happily to /var/log/tor/tor.log
12303 Changes in version 0.0.9.5 - 2005-02-22
12304 o Bugfixes on 0.0.9.x:
12305 - Fix an assert race at exit nodes when resolve requests fail.
12306 - Stop picking unverified dir mirrors--it only leads to misery.
12307 - Patch from Matt Edman to make NT services work better. Service
12308 support is still not compiled into the executable by default.
12309 - Patch from Dmitri Bely so the Tor service runs better under
12310 the win32 SYSTEM account.
12311 - Make tor-resolve actually work (?) on Win32.
12312 - Fix a sign bug when getrlimit claims to have 4+ billion
12313 file descriptors available.
12314 - Stop refusing to start when bandwidthburst == bandwidthrate.
12315 - When create cells have been on the onion queue more than five
12316 seconds, just send back a destroy and take them off the list.
12319 Changes in version 0.0.9.4 - 2005-02-03
12320 o Bugfixes on 0.0.9:
12321 - Fix an assert bug that took down most of our servers: when
12322 a server claims to have 1 GB of bandwidthburst, don't
12324 - Don't crash as badly if we have spawned the max allowed number
12325 of dnsworkers, or we're out of file descriptors.
12326 - Block more file-sharing ports in the default exit policy.
12327 - MaxConn is now automatically set to the hard limit of max
12328 file descriptors we're allowed (ulimit -n), minus a few for
12330 - Give a clearer message when servers need to raise their
12331 ulimit -n when they start running out of file descriptors.
12332 - SGI Compatibility patches from Jan Schaumann.
12333 - Tolerate a corrupt cached directory better.
12334 - When a dirserver hasn't approved your server, list which one.
12335 - Go into soft hibernation after 95% of the bandwidth is used,
12336 not 99%. This is especially important for daily hibernators who
12337 have a small accounting max. Hopefully it will result in fewer
12338 cut connections when the hard hibernation starts.
12339 - Load-balance better when using servers that claim more than
12340 800kB/s of capacity.
12341 - Make NT services work (experimental, only used if compiled in).
12344 Changes in version 0.0.9.3 - 2005-01-21
12345 o Bugfixes on 0.0.9:
12346 - Backport the cpu use fixes from main branch, so busy servers won't
12347 need as much processor time.
12348 - Work better when we go offline and then come back, or when we
12349 run Tor at boot before the network is up. We do this by
12350 optimistically trying to fetch a new directory whenever an
12351 application request comes in and we think we're offline -- the
12352 human is hopefully a good measure of when the network is back.
12353 - Backport some minimal hidserv bugfixes: keep rend circuits open as
12354 long as you keep using them; actually publish hidserv descriptors
12355 shortly after they change, rather than waiting 20-40 minutes.
12356 - Enable Mac startup script by default.
12357 - Fix duplicate dns_cancel_pending_resolve reported by Giorgos Pallas.
12358 - When you update AllowUnverifiedNodes or FirewallPorts via the
12359 controller's setconf feature, we were always appending, never
12361 - When you update HiddenServiceDir via setconf, it was screwing up
12362 the order of reading the lines, making it fail.
12363 - Do not rewrite a cached directory back to the cache; otherwise we
12364 will think it is recent and not fetch a newer one on startup.
12365 - Workaround for webservers that lie about Content-Encoding: Tor
12366 now tries to autodetect compressed directories and compression
12367 itself. This lets us Proxypass dir fetches through apache.
12370 Changes in version 0.0.9.2 - 2005-01-04
12371 o Bugfixes on 0.0.9 (crashes and asserts):
12372 - Fix an assert on startup when the disk is full and you're logging
12374 - If you do socks4 with an IP of 0.0.0.x but *don't* provide a socks4a
12375 style address, then we'd crash.
12376 - Fix an assert trigger when the running-routers string we get from
12377 a dirserver is broken.
12378 - Make worker threads start and run on win32. Now win32 servers
12380 - Bandaid (not actually fix, but now it doesn't crash) an assert
12381 where the dns worker dies mysteriously and the main Tor process
12382 doesn't remember anything about the address it was resolving.
12384 o Bugfixes on 0.0.9 (Win32):
12385 - Workaround for brain-damaged __FILE__ handling on MSVC: keep Nick's
12386 name out of the warning/assert messages.
12387 - Fix a superficial "unhandled error on read" bug on win32.
12388 - The win32 installer no longer requires a click-through for our
12389 license, since our Free Software license grants rights but does not
12391 - Win32: When connecting to a dirserver fails, try another one
12392 immediately. (This was already working for non-win32 Tors.)
12393 - Stop trying to parse $HOME on win32 when hunting for default
12395 - Make tor-resolve.c work on win32 by calling network_init().
12397 o Bugfixes on 0.0.9 (other):
12398 - Make 0.0.9.x build on Solaris again.
12399 - Due to a fencepost error, we were blowing away the \n when reporting
12400 confvalue items in the controller. So asking for multiple config
12401 values at once couldn't work.
12402 - When listing circuits that are pending on an opening OR connection,
12403 if we're an OR we were listing circuits that *end* at us as
12404 being pending on every listener, dns/cpu worker, etc. Stop that.
12405 - Dirservers were failing to create 'running-routers' or 'directory'
12406 strings if we had more than some threshold of routers. Fix them so
12407 they can handle any number of routers.
12408 - Fix a superficial "Duplicate mark for close" bug.
12409 - Stop checking for clock skew for OR connections, even for servers.
12410 - Fix a fencepost error that was chopping off the last letter of any
12411 nickname that is the maximum allowed nickname length.
12412 - Update URLs in log messages so they point to the new website.
12413 - Fix a potential problem in mangling server private keys while
12414 writing to disk (not triggered yet, as far as we know).
12415 - Include the licenses for other free software we include in Tor,
12416 now that we're shipping binary distributions more regularly.
12419 Changes in version 0.0.9.1 - 2004-12-15
12420 o Bugfixes on 0.0.9:
12421 - Make hibernation actually work.
12422 - Make HashedControlPassword config option work.
12423 - When we're reporting event circuit status to a controller,
12424 don't use the stream status code.
12427 Changes in version 0.0.9 - 2004-12-12
12429 - Clean up manpage and torrc.sample file.
12430 - Clean up severities and text of log warnings.
12432 - Make servers trigger an assert when they enter hibernation.
12435 Changes in version 0.0.9rc7 - 2004-12-08
12436 o Bugfixes on 0.0.9rc:
12437 - Fix a stack-trashing crash when an exit node begins hibernating.
12438 - Avoid looking at unallocated memory while considering which
12439 ports we need to build circuits to cover.
12440 - Stop a sigpipe: when an 'end' cell races with eof from the app,
12441 we shouldn't hold-open-until-flush if the eof arrived first.
12442 - Fix a bug with init_cookie_authentication() in the controller.
12443 - When recommending new-format log lines, if the upper bound is
12444 LOG_ERR, leave it implicit.
12446 o Bugfixes on 0.0.8.1:
12447 - Fix a whole slew of memory leaks.
12448 - Fix isspace() and friends so they still make Solaris happy
12449 but also so they don't trigger asserts on win32.
12450 - Fix parse_iso_time on platforms without strptime (eg win32).
12451 - win32: tolerate extra "readable" events better.
12452 - win32: when being multithreaded, leave parent fdarray open.
12453 - Make unit tests work on win32.
12456 Changes in version 0.0.9rc6 - 2004-12-06
12457 o Bugfixes on 0.0.9pre:
12458 - Clean up some more integer underflow opportunities (not exploitable
12460 - While hibernating, hup should not regrow our listeners.
12461 - Send an end to the streams we close when we hibernate, rather
12462 than just chopping them off.
12463 - React to eof immediately on non-open edge connections.
12465 o Bugfixes on 0.0.8.1:
12466 - Calculate timeout for waiting for a connected cell from the time
12467 we sent the begin cell, not from the time the stream started. If
12468 it took a long time to establish the circuit, we would time out
12469 right after sending the begin cell.
12470 - Fix router_compare_addr_to_addr_policy: it was not treating a port
12471 of * as always matching, so we were picking reject *:* nodes as
12472 exit nodes too. Oops.
12475 - New circuit building strategy: keep a list of ports that we've
12476 used in the past 6 hours, and always try to have 2 circuits open
12477 or on the way that will handle each such port. Seed us with port
12478 80 so web users won't complain that Tor is "slow to start up".
12479 - Make kill -USR1 dump more useful stats about circuits.
12480 - When warning about retrying or giving up, print the address, so
12481 the user knows which one it's talking about.
12482 - If you haven't used a clean circuit in an hour, throw it away,
12483 just to be on the safe side. (This means after 6 hours a totally
12484 unused Tor client will have no circuits open.)
12487 Changes in version 0.0.9rc5 - 2004-12-01
12488 o Bugfixes on 0.0.8.1:
12489 - Disallow NDEBUG. We don't ever want anybody to turn off debug.
12490 - Let resolve conns retry/expire also, rather than sticking around
12492 - If we are using select, make sure we stay within FD_SETSIZE.
12494 o Bugfixes on 0.0.9pre:
12495 - Fix integer underflow in tor_vsnprintf() that may be exploitable,
12496 but doesn't seem to be currently; thanks to Ilja van Sprundel for
12498 - If anybody set DirFetchPostPeriod, give them StatusFetchPeriod
12499 instead. Impose minima and maxima for all *Period options; impose
12500 even tighter maxima for fetching if we are a caching dirserver.
12501 Clip rather than rejecting.
12502 - Fetch cached running-routers from servers that serve it (that is,
12503 authdirservers and servers running 0.0.9rc5-cvs or later.)
12506 - Accept *:706 (silc) in default exit policy.
12507 - Implement new versioning format for post 0.1.
12508 - Support "foo.nickname.exit" addresses, to let Alice request the
12509 address "foo" as viewed by exit node "nickname". Based on a patch
12511 - Make tor --version --version dump the cvs Id of every file.
12514 Changes in version 0.0.9rc4 - 2004-11-28
12515 o Bugfixes on 0.0.8.1:
12516 - Make windows sockets actually non-blocking (oops), and handle
12517 win32 socket errors better.
12519 o Bugfixes on 0.0.9rc1:
12520 - Actually catch the -USR2 signal.
12523 Changes in version 0.0.9rc3 - 2004-11-25
12524 o Bugfixes on 0.0.8.1:
12525 - Flush the log file descriptor after we print "Tor opening log file",
12526 so we don't see those messages days later.
12528 o Bugfixes on 0.0.9rc1:
12529 - Make tor-resolve work again.
12530 - Avoid infinite loop in tor-resolve if tor hangs up on it.
12531 - Fix an assert trigger for clients/servers handling resolves.
12534 Changes in version 0.0.9rc2 - 2004-11-24
12535 o Bugfixes on 0.0.9rc1:
12536 - I broke socks5 support while fixing the eof bug.
12537 - Allow unitless bandwidths and intervals; they default to bytes
12539 - New servers don't start out hibernating; they are active until
12540 they run out of bytes, so they have a better estimate of how
12541 long it takes, and so their operators can know they're working.
12544 Changes in version 0.0.9rc1 - 2004-11-23
12545 o Bugfixes on 0.0.8.1:
12546 - Finally fix a bug that's been plaguing us for a year:
12547 With high load, circuit package window was reaching 0. Whenever
12548 we got a circuit-level sendme, we were reading a lot on each
12549 socket, but only writing out a bit. So we would eventually reach
12550 eof. This would be noticed and acted on even when there were still
12551 bytes sitting in the inbuf.
12552 - When poll() is interrupted, we shouldn't believe the revents values.
12554 o Bugfixes on 0.0.9pre6:
12555 - Fix hibernate bug that caused pre6 to be broken.
12556 - Don't keep rephist info for routers that haven't had activity for
12557 24 hours. (This matters now that clients have keys, since we track
12559 - Never call close_temp_logs while validating log options.
12560 - Fix backslash-escaping on tor.sh.in and torctl.in.
12563 - Implement weekly/monthly/daily accounting: now you specify your
12564 hibernation properties by
12565 AccountingMax N bytes|KB|MB|GB|TB
12566 AccountingStart day|week|month [day] HH:MM
12567 Defaults to "month 1 0:00".
12568 - Let bandwidth and interval config options be specified as 5 bytes,
12569 kb, kilobytes, etc; and as seconds, minutes, hours, days, weeks.
12570 - kill -USR2 now moves all logs to loglevel debug (kill -HUP to
12571 get back to normal.)
12572 - If your requested entry or exit node has advertised bandwidth 0,
12574 - Be more greedy about filling up relay cells -- we try reading again
12575 once we've processed the stuff we read, in case enough has arrived
12576 to fill the last cell completely.
12577 - Apply NT service patch from Osamu Fujino. Still needs more work.
12580 Changes in version 0.0.9pre6 - 2004-11-15
12581 o Bugfixes on 0.0.8.1:
12582 - Fix assert failure on malformed socks4a requests.
12583 - Use identity comparison, not nickname comparison, to choose which
12584 half of circuit-ID-space each side gets to use. This is needed
12585 because sometimes we think of a router as a nickname, and sometimes
12586 as a hex ID, and we can't predict what the other side will do.
12587 - Catch and ignore SIGXFSZ signals when log files exceed 2GB; our
12588 write() call will fail and we handle it there.
12589 - Add a FAST_SMARTLIST define to optionally inline smartlist_get
12590 and smartlist_len, which are two major profiling offenders.
12592 o Bugfixes on 0.0.9pre5:
12593 - Fix a bug in read_all that was corrupting config files on windows.
12594 - When we're raising the max number of open file descriptors to
12595 'unlimited', don't log that we just raised it to '-1'.
12596 - Include event code with events, as required by control-spec.txt.
12597 - Don't give a fingerprint when clients do --list-fingerprint:
12598 it's misleading, because it will never be the same again.
12599 - Stop using strlcpy in tor_strndup, since it was slowing us
12601 - Remove warn on startup about missing cached-directory file.
12602 - Make kill -USR1 work again.
12603 - Hibernate if we start tor during the "wait for wakeup-time" phase
12604 of an accounting interval. Log our hibernation plans better.
12605 - Authoritative dirservers now also cache their directory, so they
12606 have it on start-up.
12609 - Fetch running-routers; cache running-routers; compress
12610 running-routers; serve compressed running-routers.z
12611 - Add NSI installer script contributed by J Doe.
12612 - Commit VC6 and VC7 workspace/project files.
12613 - Commit a tor.spec for making RPM files, with help from jbash.
12614 - Add contrib/torctl.in contributed by Glenn Fink.
12615 - Implement the control-spec's SAVECONF command, to write your
12616 configuration to torrc.
12617 - Get cookie authentication for the controller closer to working.
12618 - Include control-spec.txt in the tarball.
12619 - When set_conf changes our server descriptor, upload a new copy.
12620 But don't upload it too often if there are frequent changes.
12621 - Document authentication config in man page, and document signals
12623 - Clean up confusing parts of man page and torrc.sample.
12624 - Make expand_filename handle ~ and ~username.
12625 - Use autoconf to enable largefile support where necessary. Use
12626 ftello where available, since ftell can fail at 2GB.
12627 - Distinguish between TOR_TLS_CLOSE and TOR_TLS_ERROR, so we can
12628 log more informatively.
12629 - Give a slightly more useful output for "tor -h".
12630 - Refuse application socks connections to port 0.
12631 - Check clock skew for verified servers, but allow unverified
12632 servers and clients to have any clock skew.
12633 - Break DirFetchPostPeriod into:
12634 - DirFetchPeriod for fetching full directory,
12635 - StatusFetchPeriod for fetching running-routers,
12636 - DirPostPeriod for posting server descriptor,
12637 - RendPostPeriod for posting hidden service descriptors.
12638 - Make sure the hidden service descriptors are at a random offset
12639 from each other, to hinder linkability.
12642 Changes in version 0.0.9pre5 - 2004-11-09
12643 o Bugfixes on 0.0.9pre4:
12644 - Fix a seg fault in unit tests (doesn't affect main program).
12645 - Fix an assert bug where a hidden service provider would fail if
12646 the first hop of his rendezvous circuit was down.
12647 - Hidden service operators now correctly handle version 1 style
12648 INTRODUCE1 cells (nobody generates them still, so not a critical
12650 - If do_hup fails, actually notice.
12651 - Handle more errnos from accept() without closing the listener.
12652 Some OpenBSD machines were closing their listeners because
12653 they ran out of file descriptors.
12654 - Send resolve cells to exit routers that are running a new
12655 enough version of the resolve code to work right.
12656 - Better handling of winsock includes on non-MSV win32 compilers.
12657 - Some people had wrapped their tor client/server in a script
12658 that would restart it whenever it died. This did not play well
12659 with our "shut down if your version is obsolete" code. Now people
12660 don't fetch a new directory if their local cached version is
12662 - Make our autogen.sh work on ksh as well as bash.
12665 - Hibernation: New config option "AccountingMaxKB" lets you
12666 set how many KBytes per month you want to allow your server to
12667 consume. Rather than spreading those bytes out evenly over the
12668 month, we instead hibernate for some of the month and pop up
12669 at a deterministic time, work until the bytes are consumed, then
12670 hibernate again. Config option "MonthlyAccountingStart" lets you
12671 specify which day of the month your billing cycle starts on.
12672 - Control interface: a separate program can now talk to your
12673 client/server over a socket, and get/set config options, receive
12674 notifications of circuits and streams starting/finishing/dying,
12675 bandwidth used, etc. The next step is to get some GUIs working.
12676 Let us know if you want to help out. See doc/control-spec.txt .
12677 - Ship a contrib/tor-control.py as an example script to interact
12678 with the control port.
12679 - "tor --hash-password zzyxz" will output a salted password for
12680 use in authenticating to the control interface.
12681 - New log format in config:
12682 "Log minsev[-maxsev] stdout|stderr|syslog" or
12683 "Log minsev[-maxsev] file /var/foo"
12686 - DirPolicy config option, to let people reject incoming addresses
12687 from their dirserver.
12688 - "tor --list-fingerprint" will list your identity key fingerprint
12690 - Add "pass" target for RedirectExit, to make it easier to break
12691 out of a sequence of RedirectExit rules.
12692 - Clients now generate a TLS cert too, in preparation for having
12693 them act more like real nodes.
12694 - Ship src/win32/ in the tarball, so people can use it to build.
12695 - Make old win32 fall back to CWD if SHGetSpecialFolderLocation
12697 - New "router-status" line in directory, to better bind each verified
12698 nickname to its identity key.
12699 - Deprecate unofficial config option abbreviations, and abbreviations
12700 not on the command line.
12701 - Add a pure-C tor-resolve implementation.
12702 - Use getrlimit and friends to ensure we can reach MaxConn (currently
12703 1024) file descriptors.
12705 o Code security improvements, inspired by Ilja:
12706 - Replace sprintf with snprintf. (I think they were all safe, but
12708 - Replace strcpy/strncpy with strlcpy in more places.
12709 - Avoid strcat; use snprintf or strlcat instead.
12710 - snprintf wrapper with consistent (though not C99) overflow behavior.
12713 Changes in version 0.0.9pre4 - 2004-10-17
12714 o Bugfixes on 0.0.9pre3:
12715 - If the server doesn't specify an exit policy, use the real default
12716 exit policy, not reject *:*.
12717 - Ignore fascistfirewall when uploading/downloading hidden service
12718 descriptors, since we go through Tor for those; and when using
12719 an HttpProxy, since we assume it can reach them all.
12720 - When looking for an authoritative dirserver, use only the ones
12721 configured at boot. Don't bother looking in the directory.
12722 - The rest of the fix for get_default_conf_file() on older win32.
12723 - Make 'Routerfile' config option obsolete.
12726 - New 'MyFamily nick1,...' config option for a server to
12727 specify other servers that shouldn't be used in the same circuit
12728 with it. Only believed if nick1 also specifies us.
12729 - New 'NodeFamily nick1,nick2,...' config option for a client to
12730 specify nodes that it doesn't want to use in the same circuit.
12731 - New 'Redirectexit pattern address:port' config option for a
12732 server to redirect exit connections, e.g. to a local squid.
12735 Changes in version 0.0.9pre3 - 2004-10-13
12736 o Bugfixes on 0.0.8.1:
12737 - Better torrc example lines for dirbindaddress and orbindaddress.
12738 - Improved bounds checking on parsed ints (e.g. config options and
12739 the ones we find in directories.)
12740 - Better handling of size_t vs int, so we're more robust on 64
12742 - Fix the rest of the bug where a newly started OR would appear
12743 as unverified even after we've added his fingerprint and hupped
12745 - Fix a bug from 0.0.7: when read() failed on a stream, we would
12746 close it without sending back an end. So 'connection refused'
12747 would simply be ignored and the user would get no response.
12749 o Bugfixes on 0.0.9pre2:
12750 - Serving the cached-on-disk directory to people is bad. We now
12751 provide no directory until we've fetched a fresh one.
12752 - Workaround for bug on windows where cached-directories get crlf
12754 - Make get_default_conf_file() work on older windows too.
12755 - If we write a *:* exit policy line in the descriptor, don't write
12756 any more exit policy lines.
12759 - Use only 0.0.9pre1 and later servers for resolve cells.
12760 - Make the dirservers file obsolete.
12761 - Include a dir-signing-key token in directories to tell the
12762 parsing entity which key is being used to sign.
12763 - Remove the built-in bulky default dirservers string.
12764 - New config option "Dirserver %s:%d [fingerprint]", which can be
12765 repeated as many times as needed. If no dirservers specified,
12766 default to moria1,moria2,tor26.
12767 - Make moria2 advertise a dirport of 80, so people behind firewalls
12768 will be able to get a directory.
12769 - Http proxy support
12770 - Dirservers translate requests for http://%s:%d/x to /x
12771 - You can specify "HttpProxy %s[:%d]" and all dir fetches will
12772 be routed through this host.
12773 - Clients ask for /tor/x rather than /x for new enough dirservers.
12774 This way we can one day coexist peacefully with apache.
12775 - Clients specify a "Host: %s%d" http header, to be compatible
12776 with more proxies, and so running squid on an exit node can work.
12779 Changes in version 0.0.8.1 - 2004-10-13
12781 - Fix a seg fault that can be triggered remotely for Tor
12782 clients/servers with an open dirport.
12783 - Fix a rare assert trigger, where routerinfos for entries in
12784 our cpath would expire while we're building the path.
12785 - Fix a bug in OutboundBindAddress so it (hopefully) works.
12786 - Fix a rare seg fault for people running hidden services on
12787 intermittent connections.
12788 - Fix a bug in parsing opt keywords with objects.
12789 - Fix a stale pointer assert bug when a stream detaches and
12791 - Fix a string format vulnerability (probably not exploitable)
12792 in reporting stats locally.
12793 - Fix an assert trigger: sometimes launching circuits can fail
12794 immediately, e.g. because too many circuits have failed recently.
12795 - Fix a compile warning on 64 bit platforms.
12798 Changes in version 0.0.9pre2 - 2004-10-03
12800 - Make fetching a cached directory work for 64-bit platforms too.
12801 - Make zlib.h a required header, not an optional header.
12804 Changes in version 0.0.9pre1 - 2004-10-01
12806 - Stop using separate defaults for no-config-file and
12807 empty-config-file. Now you have to explicitly turn off SocksPort,
12808 if you don't want it open.
12809 - Fix a bug in OutboundBindAddress so it (hopefully) works.
12810 - Improve man page to mention more of the 0.0.8 features.
12811 - Fix a rare seg fault for people running hidden services on
12812 intermittent connections.
12813 - Change our file IO stuff (especially wrt OpenSSL) so win32 is
12815 - Fix more dns related bugs: send back resolve_failed and end cells
12816 more reliably when the resolve fails, rather than closing the
12817 circuit and then trying to send the cell. Also attach dummy resolve
12818 connections to a circuit *before* calling dns_resolve(), to fix
12819 a bug where cached answers would never be sent in RESOLVED cells.
12820 - When we run out of disk space, or other log writing error, don't
12821 crash. Just stop logging to that log and continue.
12822 - We were starting to daemonize before we opened our logs, so if
12823 there were any problems opening logs, we would complain to stderr,
12824 which wouldn't work, and then mysteriously exit.
12825 - Fix a rare bug where sometimes a verified OR would connect to us
12826 before he'd uploaded his descriptor, which would cause us to
12827 assign conn->nickname as though he's unverified. Now we look through
12828 the fingerprint list to see if he's there.
12829 - Fix a rare assert trigger, where routerinfos for entries in
12830 our cpath would expire while we're building the path.
12833 - Clients can ask dirservers for /dir.z to get a compressed version
12834 of the directory. Only works for servers running 0.0.9, of course.
12835 - Make clients cache directories and use them to seed their router
12836 lists at startup. This means clients have a datadir again.
12837 - Configuration infrastructure support for warning on obsolete
12839 - Respond to content-encoding headers by trying to uncompress as
12841 - Reply with a deflated directory when a client asks for "dir.z".
12842 We could use allow-encodings instead, but allow-encodings isn't
12843 specified in HTTP 1.0.
12844 - Raise the max dns workers from 50 to 100.
12845 - Discourage people from setting their dirfetchpostperiod more often
12846 than once per minute.
12847 - Protect dirservers from overzealous descriptor uploading -- wait
12848 10 seconds after directory gets dirty, before regenerating.
12851 Changes in version 0.0.8 - 2004-08-25
12852 o Port it to SunOS 5.9 / Athena
12855 Changes in version 0.0.8rc2 - 2004-08-20
12856 o Make it compile on cygwin again.
12857 o When picking unverified routers, skip those with low uptime and/or
12858 low bandwidth, depending on what properties you care about.
12861 Changes in version 0.0.8rc1 - 2004-08-18
12862 o Changes from 0.0.7.3:
12864 - Fix assert triggers: if the other side returns an address 0.0.0.0,
12865 don't put it into the client dns cache.
12866 - If a begin failed due to exit policy, but we believe the IP address
12867 should have been allowed, switch that router to exitpolicy reject *:*
12868 until we get our next directory.
12870 - Clients choose nodes proportional to advertised bandwidth.
12871 - Avoid using nodes with low uptime as introduction points.
12872 - Handle servers with dynamic IP addresses: don't replace
12873 options->Address with the resolved one at startup, and
12874 detect our address right before we make a routerinfo each time.
12875 - 'FascistFirewall' option to pick dirservers and ORs on specific
12876 ports; plus 'FirewallPorts' config option to tell FascistFirewall
12877 which ports are open. (Defaults to 80,443)
12878 - Be more aggressive about trying to make circuits when the network
12879 has changed (e.g. when you unsuspend your laptop).
12880 - Check for time skew on http headers; report date in response to
12882 - If the entrynode config line has only one node, don't pick it as
12884 - Add strict{entry|exit}nodes config options. If set to 1, then
12885 we refuse to build circuits that don't include the specified entry
12887 - OutboundBindAddress config option, to bind to a specific
12888 IP address for outgoing connect()s.
12889 - End truncated log entries (e.g. directories) with "[truncated]".
12891 o Patches to 0.0.8preX:
12893 - Patches to compile and run on win32 again (maybe)?
12894 - Fix crash when looking for ~/.torrc with no $HOME set.
12895 - Fix a race bug in the unit tests.
12896 - Handle verified/unverified name collisions better when new
12897 routerinfo's arrive in a directory.
12898 - Sometimes routers were getting entered into the stats before
12899 we'd assigned their identity_digest. Oops.
12900 - Only pick and establish intro points after we've gotten a
12903 - AllowUnverifiedNodes config option to let circuits choose no-name
12904 routers in entry,middle,exit,introduction,rendezvous positions.
12905 Allow middle and rendezvous positions by default.
12906 - Add a man page for tor-resolve.
12909 Changes in version 0.0.7.3 - 2004-08-12
12910 o Stop dnsworkers from triggering an assert failure when you
12911 ask them to resolve the host "".
12914 Changes in version 0.0.8pre3 - 2004-08-09
12915 o Changes from 0.0.7.2:
12916 - Allow multiple ORs with same nickname in routerlist -- now when
12917 people give us one identity key for a nickname, then later
12918 another, we don't constantly complain until the first expires.
12919 - Remember used bandwidth (both in and out), and publish 15-minute
12920 snapshots for the past day into our descriptor.
12921 - You can now fetch $DIRURL/running-routers to get just the
12922 running-routers line, not the whole descriptor list. (But
12923 clients don't use this yet.)
12924 - When people mistakenly use Tor as an http proxy, point them
12925 at the tor-doc.html rather than the INSTALL.
12926 - Remove our mostly unused -- and broken -- hex_encode()
12927 function. Use base16_encode() instead. (Thanks to Timo Lindfors
12928 for pointing out this bug.)
12929 - Rotate onion keys every 12 hours, not every 2 hours, so we have
12930 fewer problems with people using the wrong key.
12931 - Change the default exit policy to reject the default edonkey,
12932 kazaa, gnutella ports.
12933 - Add replace_file() to util.[ch] to handle win32's rename().
12935 o Changes from 0.0.8preX:
12936 - Fix two bugs in saving onion keys to disk when rotating, so
12937 hopefully we'll get fewer people using old onion keys.
12938 - Fix an assert error that was making SocksPolicy not work.
12939 - Be willing to expire routers that have an open dirport -- it's
12940 just the authoritative dirservers we want to not forget.
12941 - Reject tor-resolve requests for .onion addresses early, so we
12942 don't build a whole rendezvous circuit and then fail.
12943 - When you're warning a server that he's unverified, don't cry
12944 wolf unpredictably.
12945 - Fix a race condition: don't try to extend onto a connection
12946 that's still handshaking.
12947 - For servers in clique mode, require the conn to be open before
12948 you'll choose it for your path.
12949 - Fix some cosmetic bugs about duplicate mark-for-close, lack of
12950 end relay cell, etc.
12951 - Measure bandwidth capacity over the last 24 hours, not just 12
12952 - Bugfix: authoritative dirservers were making and signing a new
12953 directory for each client, rather than reusing the cached one.
12956 Changes in version 0.0.8pre2 - 2004-08-04
12957 o Changes from 0.0.7.2:
12959 - Check directory signature _before_ you decide whether you're
12960 you're running an obsolete version and should exit.
12961 - Check directory signature _before_ you parse the running-routers
12962 list to decide who's running or verified.
12963 - Bugfixes and features:
12964 - Check return value of fclose while writing to disk, so we don't
12965 end up with broken files when servers run out of disk space.
12966 - Log a warning if the user uses an unsafe socks variant, so people
12967 are more likely to learn about privoxy or socat.
12968 - Dirservers now include RFC1123-style dates in the HTTP headers,
12969 which one day we will use to better detect clock skew.
12971 o Changes from 0.0.8pre1:
12972 - Make it compile without warnings again on win32.
12973 - Log a warning if you're running an unverified server, to let you
12974 know you might want to get it verified.
12975 - Only pick a default nickname if you plan to be a server.
12978 Changes in version 0.0.8pre1 - 2004-07-23
12980 - Made our unit tests compile again on OpenBSD 3.5, and tor
12981 itself compile again on OpenBSD on a sparc64.
12982 - We were neglecting milliseconds when logging on win32, so
12983 everything appeared to happen at the beginning of each second.
12985 o Protocol changes:
12986 - 'Extend' relay cell payloads now include the digest of the
12987 intended next hop's identity key. Now we can verify that we're
12988 extending to the right router, and also extend to routers we
12989 hadn't heard of before.
12992 - Tor nodes can now act as relays (with an advertised ORPort)
12993 without being manually verified by the dirserver operators.
12994 - Uploaded descriptors of unverified routers are now accepted
12995 by the dirservers, and included in the directory.
12996 - Verified routers are listed by nickname in the running-routers
12997 list; unverified routers are listed as "$<fingerprint>".
12998 - We now use hash-of-identity-key in most places rather than
12999 nickname or addr:port, for improved security/flexibility.
13000 - To avoid Sybil attacks, paths still use only verified servers.
13001 But now we have a chance to play around with hybrid approaches.
13002 - Nodes track bandwidth usage to estimate capacity (not used yet).
13003 - ClientOnly option for nodes that never want to become servers.
13004 - Directory caching.
13005 - "AuthoritativeDir 1" option for the official dirservers.
13006 - Now other nodes (clients and servers) will cache the latest
13007 directory they've pulled down.
13008 - They can enable their DirPort to serve it to others.
13009 - Clients will pull down a directory from any node with an open
13010 DirPort, and check the signature/timestamp correctly.
13011 - Authoritative dirservers now fetch directories from other
13012 authdirservers, to stay better synced.
13013 - Running-routers list tells who's down also, along with noting
13014 if they're verified (listed by nickname) or unverified (listed
13016 - Allow dirservers to serve running-router list separately.
13017 This isn't used yet.
13018 - ORs connect-on-demand to other ORs
13019 - If you get an extend cell to an OR you're not connected to,
13020 connect, handshake, and forward the create cell.
13021 - The authoritative dirservers stay connected to everybody,
13022 and everybody stays connected to 0.0.7 servers, but otherwise
13023 clients/servers expire unused connections after 5 minutes.
13024 - When servers get a sigint, they delay 30 seconds (refusing new
13025 connections) then exit. A second sigint causes immediate exit.
13026 - File and name management:
13027 - Look for .torrc if no CONFDIR "torrc" is found.
13028 - If no datadir is defined, then choose, make, and secure ~/.tor
13030 - If torrc not found, exitpolicy reject *:*.
13031 - Expands ~/ in filenames to $HOME/ (but doesn't yet expand ~arma).
13032 - If no nickname is defined, derive default from hostname.
13033 - Rename secret key files, e.g. identity.key -> secret_id_key,
13034 to discourage people from mailing their identity key to tor-ops.
13035 - Refuse to build a circuit before the directory has arrived --
13036 it won't work anyway, since you won't know the right onion keys
13038 - Try other dirservers immediately if the one you try is down. This
13039 should tolerate down dirservers better now.
13040 - Parse tor version numbers so we can do an is-newer-than check
13041 rather than an is-in-the-list check.
13042 - New socks command 'resolve', to let us shim gethostbyname()
13044 - A 'tor_resolve' script to access the socks resolve functionality.
13045 - A new socks-extensions.txt doc file to describe our
13046 interpretation and extensions to the socks protocols.
13047 - Add a ContactInfo option, which gets published in descriptor.
13048 - Publish OR uptime in descriptor (and thus in directory) too.
13049 - Write tor version at the top of each log file
13050 - New docs in the tarball:
13052 - Document that you should proxy your SSL traffic too.
13055 Changes in version 0.0.7.2 - 2004-07-07
13056 o A better fix for the 0.0.0.0 problem, that will hopefully
13057 eliminate the remaining related assertion failures.
13060 Changes in version 0.0.7.1 - 2004-07-04
13061 o When an address resolves to 0.0.0.0, treat it as a failed resolve,
13062 since internally we use 0.0.0.0 to signify "not yet resolved".
13065 Changes in version 0.0.7 - 2004-06-07
13066 o Updated the man page to reflect the new features.
13069 Changes in version 0.0.7rc2 - 2004-06-06
13070 o Changes from 0.0.7rc1:
13071 - Make it build on Win32 again.
13072 o Changes from 0.0.6.2:
13073 - Rotate dnsworkers and cpuworkers on SIGHUP, so they get new config
13077 Changes in version 0.0.7rc1 - 2004-06-02
13079 - On sighup, we were adding another log without removing the first
13080 one. So log messages would get duplicated n times for n sighups.
13081 - Several cases of using a connection after we'd freed it. The
13082 problem was that connections that are pending resolve are in both
13083 the pending_resolve tree, and also the circuit's resolving_streams
13084 list. When you want to remove one, you must remove it from both.
13085 - Fix a double-mark-for-close where an end cell arrived for a
13086 resolving stream, and then the resolve failed.
13087 - Check directory signatures based on name of signer, not on whom
13088 we got the directory from. This will let us cache directories more
13091 - Crank up some of our constants to handle more users.
13094 Changes in version 0.0.7pre1 - 2004-06-02
13095 o Fixes for crashes and other obnoxious bugs:
13096 - Fix an epipe bug: sometimes when directory connections failed
13097 to connect, we would give them a chance to flush before closing
13099 - When we detached from a circuit because of resolvefailed, we
13100 would immediately try the same circuit twice more, and then
13101 give up on the resolve thinking we'd tried three different
13103 - Limit the number of intro circuits we'll attempt to build for a
13104 hidden service per 15-minute period.
13105 - Check recommended-software string *early*, before actually parsing
13106 the directory. Thus we can detect an obsolete version and exit,
13107 even if the new directory format doesn't parse.
13108 o Fixes for security bugs:
13109 - Remember which nodes are dirservers when you startup, and if a
13110 random OR enables his dirport, don't automatically assume he's
13111 a trusted dirserver.
13113 - Directory connections were asking the wrong poll socket to
13114 start writing, and not asking themselves to start writing.
13115 - When we detached from a circuit because we sent a begin but
13116 didn't get a connected, we would use it again the first time;
13117 but after that we would correctly switch to a different one.
13118 - Stop warning when the first onion decrypt attempt fails; they
13119 will sometimes legitimately fail now that we rotate keys.
13120 - Override unaligned-access-ok check when $host_cpu is ia64 or
13121 arm. Apparently they allow it but the kernel whines.
13122 - Dirservers try to reconnect periodically too, in case connections
13124 - Fix some memory leaks in directory servers.
13125 - Allow backslash in Win32 filenames.
13126 - Made Tor build complain-free on FreeBSD, hopefully without
13127 breaking other BSD builds. We'll see.
13129 - Doxygen markup on all functions and global variables.
13130 - Make directory functions update routerlist, not replace it. So
13131 now directory disagreements are not so critical a problem.
13132 - Remove the upper limit on number of descriptors in a dirserver's
13133 directory (not that we were anywhere close).
13134 - Allow multiple logfiles at different severity ranges.
13135 - Allow *BindAddress to specify ":port" rather than setting *Port
13136 separately. Allow multiple instances of each BindAddress config
13137 option, so you can bind to multiple interfaces if you want.
13138 - Allow multiple exit policy lines, which are processed in order.
13139 Now we don't need that huge line with all the commas in it.
13140 - Enable accept/reject policies on SOCKS connections, so you can bind
13141 to 0.0.0.0 but still control who can use your OP.
13144 Changes in version 0.0.6.2 - 2004-05-16
13145 o Our integrity-checking digest was checking only the most recent cell,
13146 not the previous cells like we'd thought.
13147 Thanks to Stefan Mark for finding the flaw!
13150 Changes in version 0.0.6.1 - 2004-05-06
13151 o Fix two bugs in our AES counter-mode implementation (this affected
13152 onion-level stream encryption, but not TLS-level). It turns
13153 out we were doing something much more akin to a 16-character
13154 polyalphabetic cipher. Oops.
13155 Thanks to Stefan Mark for finding the flaw!
13156 o Retire moria3 as a directory server, and add tor26 as a directory
13160 Changes in version 0.0.6 - 2004-05-02
13161 [version bump only]
13164 Changes in version 0.0.6rc4 - 2004-05-01
13165 o Update the built-in dirservers list to use the new directory format
13166 o Fix a rare seg fault: if a node offering a hidden service attempts
13167 to build a circuit to Alice's rendezvous point and fails before it
13168 reaches the last hop, it retries with a different circuit, but
13170 o Handle windows socket errors correctly.
13173 Changes in version 0.0.6rc3 - 2004-04-28
13174 o Don't expire non-general excess circuits (if we had enough
13175 circuits open, we were expiring rendezvous circuits -- even
13176 when they had a stream attached. oops.)
13177 o Fetch randomness from /dev/urandom better (not via fopen/fread)
13178 o Better debugging for tls errors
13179 o Some versions of openssl have an SSL_pending function that erroneously
13180 returns bytes when there is a non-application record pending.
13181 o Set Content-Type on the directory and hidserv descriptor.
13182 o Remove IVs from cipher code, since AES-ctr has none.
13183 o Win32 fixes. Tor now compiles on win32 with no warnings/errors.
13184 o We were using an array of length zero in a few places.
13185 o win32's gethostbyname can't resolve an IP to an IP.
13186 o win32's close can't close a socket.
13189 Changes in version 0.0.6rc2 - 2004-04-26
13190 o Fix a bug where we were closing tls connections intermittently.
13191 It turns out openssl keeps its errors around -- so if an error
13192 happens, and you don't ask about it, and then another openssl
13193 operation happens and succeeds, and you ask if there was an error,
13194 it tells you about the first error. Fun fun.
13195 o Fix a bug that's been lurking since 27 may 03 (!)
13196 When passing back a destroy cell, we would use the wrong circ id.
13197 'Mostly harmless', but still worth fixing.
13198 o Since we don't support truncateds much, don't bother sending them;
13199 just close the circ.
13200 o check for <machine/limits.h> so we build on NetBSD again (I hope).
13201 o don't crash if a conn that sent a begin has suddenly lost its circuit
13202 (this was quite rare).
13205 Changes in version 0.0.6rc1 - 2004-04-25
13206 o We now rotate link (tls context) keys and onion keys.
13207 o CREATE cells now include oaep padding, so you can tell
13208 if you decrypted them correctly.
13209 o Add bandwidthburst to server descriptor.
13210 o Directories now say which dirserver signed them.
13211 o Use a tor_assert macro that logs failed assertions too.
13214 Changes in version 0.0.6pre5 - 2004-04-18
13215 o changes from 0.0.6pre4:
13216 - make tor build on broken freebsd 5.2 installs
13217 - fix a failed assert when you try an intro point, get a nack, and try
13218 a second one and it works.
13219 - when alice uses a port that the hidden service doesn't accept,
13220 it now sends back an end cell (denied by exit policy). otherwise
13221 alice would just have to wait to time out.
13222 - fix another rare bug: when we had tried all the intro
13223 points for a hidden service, we fetched the descriptor
13224 again, but we left our introcirc thinking it had already
13225 sent an intro, so it kept waiting for a response...
13226 - bugfix: when you sleep your hidden-service laptop, as soon
13227 as it wakes up it tries to upload a service descriptor, but
13228 socketpair fails for some reason (localhost not up yet?).
13229 now we simply give up on that upload, and we'll try again later.
13230 i'd still like to find the bug though.
13231 - if an intro circ waiting for an ack dies before getting one, then
13233 - we were reusing stale service descriptors and refetching usable
13237 Changes in version 0.0.6pre4 - 2004-04-14
13238 o changes from 0.0.6pre3:
13239 - when bob fails to connect to the rendezvous point, and his
13240 circ didn't fail because of the rendezvous point itself, then
13241 he retries a couple of times
13242 - we expire introduction and rendezvous circs more thoroughly
13243 (sometimes they were hanging around forever)
13244 - we expire unattached rendezvous streams that have been around
13245 too long (they were sticking around forever).
13246 - fix a measly fencepost error that was crashing everybody with
13250 Changes in version 0.0.6pre3 - 2004-04-14
13251 o changes from 0.0.6pre2:
13252 - make hup work again
13253 - fix some memory leaks for dirservers
13254 - allow more skew in rendezvous descriptor timestamps, to help
13255 handle people like blanu who don't know what time it is
13256 - normal circs are 3 hops, but some rend/intro circs are 4, if
13257 the initiator doesn't get to choose the last hop
13258 - send acks for introductions, so alice can know whether to try
13260 - bob publishes intro points more correctly
13261 o changes from 0.0.5:
13262 - fix an assert trigger that's been plaguing us since the days
13263 of 0.0.2prexx (thanks weasel!)
13264 - retry stream correctly when we fail to connect because of
13265 exit-policy-reject (should try another) or can't-resolve-address
13266 (also should try another, because dns on random internet servers
13268 - when we hup a dirserver and we've *removed* a server from the
13269 approved-routers list, now we remove that server from the
13270 in-memory directories too
13273 Changes in version 0.0.6pre2 - 2004-04-08
13274 o We fixed our base32 implementation. Now it works on all architectures.
13277 Changes in version 0.0.6pre1 - 2004-04-08
13279 - Hidden services and rendezvous points are implemented. Go to
13280 http://6sxoyfb3h2nvok2d.onion/ for an index of currently available
13281 hidden services. (This only works via a socks4a proxy such as
13282 Privoxy, and currently it's quite slow.)
13285 Changes in version 0.0.5 - 2004-03-30
13286 [version bump only]
13289 Changes in version 0.0.5rc3 - 2004-03-29
13290 o Install torrc as torrc.sample -- we no longer clobber your
13292 o Re-enable recommendedversion checking (we broke it in rc2, oops)
13293 o Add in a 'notice' log level for things the operator should hear
13294 but that aren't warnings
13297 Changes in version 0.0.5rc2 - 2004-03-29
13298 o Hold socks connection open until reply is flushed (if possible)
13299 o Make exit nodes resolve IPs to IPs immediately, rather than asking
13300 the dns farm to do it.
13301 o Fix c99 aliasing warnings in rephist.c
13302 o Don't include server descriptors that are older than 24 hours in the
13304 o Give socks 'reject' replies their whole 15s to attempt to flush,
13305 rather than seeing the 60s timeout and assuming the flush had failed.
13306 o Clean automake droppings from the cvs repository
13309 Changes in version 0.0.5rc1 - 2004-03-28
13310 o Fix mangled-state bug in directory fetching (was causing sigpipes).
13311 o Only build circuits after we've fetched the directory: clients were
13312 using only the directory servers before they'd fetched a directory.
13313 This also means longer startup time; so it goes.
13314 o Fix an assert trigger where an OP would fail to handshake, and we'd
13315 expect it to have a nickname.
13316 o Work around a tsocks bug: do a socks reject when AP connection dies
13317 early, else tsocks goes into an infinite loop.
13320 Changes in version 0.0.4 - 2004-03-26
13321 o When connecting to a dirserver or OR and the network is down,
13325 Changes in version 0.0.3 - 2004-03-26
13326 o Warn and fail if server chose a nickname with illegal characters
13327 o Port to Solaris and Sparc:
13328 - include missing header fcntl.h
13329 - have autoconf find -lsocket -lnsl automatically
13330 - deal with hardware word alignment
13331 - make uname() work (solaris has a different return convention)
13332 - switch from using signal() to sigaction()
13333 o Preliminary work on reputation system:
13334 - Keep statistics on success/fail of connect attempts; they're published
13335 by kill -USR1 currently.
13336 - Add a RunTesting option to try to learn link state by creating test
13337 circuits, even when SocksPort is off.
13338 - Remove unused open circuits when there are too many.
13341 Changes in version 0.0.2 - 2004-03-19
13342 - Include strlcpy and strlcat for safer string ops
13343 - define INADDR_NONE so we compile (but still not run) on solaris
13346 Changes in version 0.0.2pre27 - 2004-03-14
13348 - Allow internal tor networks (we were rejecting internal IPs,
13349 now we allow them if they're set explicitly).
13350 - And fix a few endian issues.
13353 Changes in version 0.0.2pre26 - 2004-03-14
13355 - If a stream times out after 15s without a connected cell, don't
13356 try that circuit again: try a new one.
13357 - Retry streams at most 4 times. Then give up.
13358 - When a dirserver gets a descriptor from an unknown router, it
13359 logs its fingerprint (so the dirserver operator can choose to
13360 accept it even without mail from the server operator).
13361 - Inform unapproved servers when we reject their descriptors.
13362 - Make tor build on Windows again. It works as a client, who knows
13364 - Clearer instructions in the torrc for how to set up a server.
13365 - Be more efficient about reading fd's when our global token bucket
13366 (used for rate limiting) becomes empty.
13368 - Stop asserting that computers always go forward in time. It's
13370 - When we sent a cell (e.g. destroy) and then marked an OR connection
13371 expired, we might close it before finishing a flush if the other
13372 side isn't reading right then.
13373 - Don't allow dirservers to start if they haven't defined
13374 RecommendedVersions
13375 - We were caching transient dns failures. Oops.
13376 - Prevent servers from publishing an internal IP as their address.
13377 - Address a strcat vulnerability in circuit.c
13380 Changes in version 0.0.2pre25 - 2004-03-04
13382 - Put the OR's IP in its router descriptor, not its fqdn. That way
13383 we'll stop being stalled by gethostbyname for nodes with flaky dns,
13386 - If the user typed in an address that didn't resolve, the server
13390 Changes in version 0.0.2pre24 - 2004-03-03
13392 - Fix an assertion failure in dns.c, where we were trying to dequeue
13393 a pending dns resolve even if it wasn't pending
13394 - Fix a spurious socks5 warning about still trying to write after the
13395 connection is finished.
13396 - Hold certain marked_for_close connections open until they're finished
13397 flushing, rather than losing bytes by closing them too early.
13398 - Correctly report the reason for ending a stream
13399 - Remove some duplicate calls to connection_mark_for_close
13400 - Put switch_id and start_daemon earlier in the boot sequence, so it
13401 will actually try to chdir() to options.DataDirectory
13402 - Make 'make test' exit(1) if a test fails; fix some unit tests
13403 - Make tor fail when you use a config option it doesn't know about,
13404 rather than warn and continue.
13405 - Make --version work
13406 - Bugfixes on the rpm spec file and tor.sh, so it's more up to date
13409 Changes in version 0.0.2pre23 - 2004-02-29
13411 - Print a statement when the first circ is finished, so the user
13412 knows it's working.
13413 - If a relay cell is unrecognized at the end of the circuit,
13414 send back a destroy. (So attacks to mutate cells are more
13416 - New config option 'excludenodes' to avoid certain nodes for circuits.
13417 - When it daemonizes, it chdir's to the DataDirectory rather than "/",
13418 so you can collect coredumps there.
13420 - Fix a bug in tls flushing where sometimes data got wedged and
13421 didn't flush until more data got sent. Hopefully this bug was
13422 a big factor in the random delays we were seeing.
13423 - Make 'connected' cells include the resolved IP, so the client
13424 dns cache actually gets populated.
13425 - Disallow changing from ORPort=0 to ORPort>0 on hup.
13426 - When we time-out on a stream and detach from the circuit, send an
13427 end cell down it first.
13428 - Only warn about an unknown router (in exitnodes, entrynodes,
13429 excludenodes) after we've fetched a directory.
13432 Changes in version 0.0.2pre22 - 2004-02-26
13434 - Servers publish less revealing uname information in descriptors.
13435 - More memory tracking and assertions, to crash more usefully when
13437 - If the default torrc isn't there, just use some default defaults.
13438 Plus provide an internal dirservers file if they don't have one.
13439 - When the user tries to use Tor as an http proxy, give them an http
13440 501 failure explaining that we're a socks proxy.
13441 - Dump a new router.desc on hup, to help confused people who change
13442 their exit policies and then wonder why router.desc doesn't reflect
13444 - Clean up the generic tor.sh init script that we ship with.
13446 - If the exit stream is pending on the resolve, and a destroy arrives,
13447 then the stream wasn't getting removed from the pending list. I
13448 think this was the one causing recent server crashes.
13449 - Use a more robust poll on OSX 10.3, since their poll is flaky.
13450 - When it couldn't resolve any dirservers, it was useless from then on.
13451 Now it reloads the RouterFile (or default dirservers) if it has no
13453 - Move the 'tor' binary back to /usr/local/bin/ -- it turns out
13454 many users don't even *have* a /usr/local/sbin/.
13457 Changes in version 0.0.2pre21 - 2004-02-18
13459 - There's a ChangeLog file that actually reflects the changelog.
13460 - There's a 'torify' wrapper script, with an accompanying
13461 tor-tsocks.conf, that simplifies the process of using tsocks for
13462 tor. It even has a man page.
13463 - The tor binary gets installed to sbin rather than bin now.
13464 - Retry streams where the connected cell hasn't arrived in 15 seconds
13465 - Clean up exit policy handling -- get the default out of the torrc,
13466 so we can update it without forcing each server operator to fix
13468 - Allow imaps and pop3s in default exit policy
13470 - Prevent picking middleman nodes as the last node in the circuit
13473 Changes in version 0.0.2pre20 - 2004-01-30
13475 - We now have a deb package, and it's in debian unstable. Go to
13476 it, apt-getters. :)
13477 - I've split the TotalBandwidth option into BandwidthRate (how many
13478 bytes per second you want to allow, long-term) and
13479 BandwidthBurst (how many bytes you will allow at once before the cap
13480 kicks in). This better token bucket approach lets you, say, set
13481 BandwidthRate to 10KB/s and BandwidthBurst to 10MB, allowing good
13482 performance while not exceeding your monthly bandwidth quota.
13483 - Push out a tls record's worth of data once you've got it, rather
13484 than waiting until you've read everything waiting to be read. This
13485 may improve performance by pipelining better. We'll see.
13486 - Add an AP_CONN_STATE_CONNECTING state, to allow streams to detach
13487 from failed circuits (if they haven't been connected yet) and attach
13489 - Expire old streams that haven't managed to connect. Some day we'll
13490 have them reattach to new circuits instead.
13493 - Fix several memory leaks that were causing servers to become bloated
13495 - Fix a few very rare assert triggers. A few more remain.
13496 - Setuid to User _before_ complaining about running as root.
13499 Changes in version 0.0.2pre19 - 2004-01-07
13501 - Fix deadlock condition in dns farm. We were telling a child to die by
13502 closing the parent's file descriptor to him. But newer children were
13503 inheriting the open file descriptor from the parent, and since they
13504 weren't closing it, the socket never closed, so the child never read
13505 eof, so he never knew to exit. Similarly, dns workers were holding
13506 open other sockets, leading to all sorts of chaos.
13507 - New cleaner daemon() code for forking and backgrounding.
13508 - If you log to a file, it now prints an entry at the top of the
13509 logfile so you know it's working.
13510 - The onionskin challenge length was 30 bytes longer than necessary.
13511 - Started to patch up the spec so it's not quite so out of date.
13514 Changes in version 0.0.2pre18 - 2004-01-02
13516 - Fix endian issues with the 'integrity' field in the relay header.
13517 - Fix a potential bug where connections in state
13518 AP_CONN_STATE_CIRCUIT_WAIT might unexpectedly ask to write.
13521 Changes in version 0.0.2pre17 - 2003-12-30
13523 - Made --debuglogfile (or any second log file, actually) work.
13524 - Resolved an edge case in get_unique_circ_id_by_conn where a smart
13525 adversary could force us into an infinite loop.
13528 - Each onionskin handshake now includes a hash of the computed key,
13529 to prove the server's identity and help perfect forward secrecy.
13530 - Changed cell size from 256 to 512 bytes (working toward compatibility
13532 - Changed cell length to 2 bytes, and moved it to the relay header.
13533 - Implemented end-to-end integrity checking for the payloads of
13535 - Separated streamid from 'recognized' (otherwise circuits will get
13536 messed up when we try to have streams exit from the middle). We
13537 use the integrity-checking to confirm that a cell is addressed to
13539 - Randomize the initial circid and streamid values, so an adversary who
13540 breaks into a node can't learn how many circuits or streams have
13544 Changes in version 0.0.2pre16 - 2003-12-14
13546 - Fixed a bug that made HUP trigger an assert
13547 - Fixed a bug where a circuit that immediately failed wasn't being
13548 counted as a failed circuit in counting retries.
13551 - Now we close the circuit when we get a truncated cell: otherwise we're
13552 open to an anonymity attack where a bad node in the path truncates
13553 the circuit and then we open streams at him.
13554 - Add port ranges to exit policies
13555 - Add a conservative default exit policy
13556 - Warn if you're running tor as root
13557 - on HUP, retry OR connections and close/rebind listeners
13558 - options.EntryNodes: try these nodes first when picking the first node
13559 - options.ExitNodes: if your best choices happen to include any of
13560 your preferred exit nodes, you choose among just those preferred
13562 - options.ExcludedNodes: nodes that are never picked in path building
13565 Changes in version 0.0.2pre15 - 2003-12-03
13566 o Robustness and bugfixes:
13567 - Sometimes clients would cache incorrect DNS resolves, which would
13568 really screw things up.
13569 - An OP that goes offline would slowly leak all its sockets and stop
13571 - A wide variety of bugfixes in exit node selection, exit policy
13572 handling, and processing pending streams when a new circuit is
13574 - Pick nodes for a path only from those the directory says are up
13575 - Choose randomly from all running dirservers, not always the first one
13576 - Increase allowed http header size for directory fetch.
13577 - Stop writing to stderr (if we're daemonized it will be closed).
13578 - Enable -g always, so cores will be more useful to me.
13579 - Switch "-lcrypto -lssl" to "-lssl -lcrypto" for broken distributions.
13582 - Wrote a man page. It lists commonly used options.
13585 - Change default loglevel to warn.
13586 - Make PidFile default to null rather than littering in your CWD.
13587 - OnionRouter config option is now obsolete. Instead it just checks
13589 - Moved to a single unified torrc file for both clients and servers.
13592 Changes in version 0.0.2pre14 - 2003-11-29
13593 o Robustness and bugfixes:
13594 - Force the admin to make the DataDirectory himself
13595 - to get ownership/permissions right
13596 - so clients no longer make a DataDirectory and then never use it
13597 - fix bug where a client who was offline for 45 minutes would never
13598 pull down a directory again
13599 - fix (or at least hide really well) the dns assert bug that was
13600 causing server crashes
13601 - warnings and improved robustness wrt clockskew for certs
13602 - use the native daemon(3) to daemonize, when available
13603 - exit if bind() fails
13604 - exit if neither socksport nor orport is defined
13605 - include our own tor_timegm (Win32 doesn't have its own)
13606 - bugfix for win32 with lots of connections
13607 - fix minor bias in PRNG
13608 - make dirserver more robust to corrupt cached directory
13611 - Wrote the design document (woo)
13613 o Circuit building and exit policies:
13614 - Circuits no longer try to use nodes that the directory has told them
13616 - Exit policies now support bitmasks (18.0.0.0/255.0.0.0) and
13617 bitcounts (18.0.0.0/8).
13618 - Make AP connections standby for a circuit if no suitable circuit
13619 exists, rather than failing
13620 - Circuits choose exit node based on addr/port, exit policies, and
13621 which AP connections are standing by
13622 - Bump min pathlen from 2 to 3
13623 - Relay end cells have a payload to describe why the stream ended.
13624 - If the stream failed because of exit policy, try again with a new
13626 - Clients have a dns cache to remember resolved addresses.
13627 - Notice more quickly when we have no working circuits
13630 - APPort is now called SocksPort
13631 - SocksBindAddress, ORBindAddress, DirBindAddress let you configure
13633 - RecommendedVersions is now a config variable rather than
13634 hardcoded (for dirservers)
13635 - Reloads config on HUP
13636 - Usage info on -h or --help
13637 - If you set User and Group config vars, it'll setu/gid to them.
13640 Changes in version 0.0.2pre13 - 2003-10-19
13641 o General stability:
13642 - SSL_write no longer fails when it returns WANTWRITE and the number
13643 of bytes in the buf has changed by the next SSL_write call.
13644 - Fix segfault fetching directory when network is down
13645 - Fix a variety of minor memory leaks
13646 - Dirservers reload the fingerprints file on HUP, so I don't have
13647 to take down the network when I approve a new router
13648 - Default server config file has explicit Address line to specify fqdn
13651 - Buffers grow and shrink as needed (Cut process size from 20M to 2M)
13652 - Make listener connections not ever alloc bufs
13654 o Autoconf improvements:
13655 - don't clobber an external CFLAGS in ./configure
13656 - Make install now works
13657 - create var/lib/tor on make install
13658 - autocreate a tor.sh initscript to help distribs
13659 - autocreate the torrc and sample-server-torrc with correct paths
13661 o Log files and Daemonizing now work:
13662 - If --DebugLogFile is specified, log to it at -l debug
13663 - If --LogFile is specified, use it instead of commandline
13664 - If --RunAsDaemon is set, tor forks and backgrounds on startup