1 Changes in version 0.2.6.2-alpha - 2014-12-31
2 Tor 0.2.6.2-alpha is the second alpha release in the 0.2.6.x series.
3 It introduces a major new backend for deciding when to send cells on
4 channels, which should lead down the road to big performance
5 increases. It contains security and statistics features for better
6 work on hidden services, and numerous bugfixes.
8 This release contains many new unit tests, along with major
9 performance improvements for running testing networks using Chutney.
10 Thanks to a series of patches contributed by "teor", testing networks
11 should now bootstrap in seconds, rather than minutes.
13 o Major features (relay, infrastructure):
14 - Complete revision of the code that relays use to decide which cell
15 to send next. Formerly, we selected the best circuit to write on
16 each channel, but we didn't select among channels in any
17 sophisticated way. Now, we choose the best circuits globally from
18 among those whose channels are ready to deliver traffic.
20 This patch implements a new inter-cmux comparison API, a global
21 high/low watermark mechanism and a global scheduler loop for
22 transmission prioritization across all channels as well as among
23 circuits on one channel. This schedule is currently tuned to
24 (tolerantly) avoid making changes in network performance, but it
25 should form the basis for major circuit performance increases in
26 the future. Code by Andrea; tuning by Rob Jansen; implements
29 o Major features (hidden services):
30 - Make HS port scanning more difficult by immediately closing the
31 circuit when a user attempts to connect to a nonexistent port.
33 - Add a HiddenServiceStatistics option that allows Tor relays to
34 gather and publish statistics about the overall size and volume of
35 hidden service usage. Specifically, when this option is turned on,
36 an HSDir will publish an approximate number of hidden services
37 that have published descriptors to it the past 24 hours. Also, if
38 a relay has acted as a hidden service rendezvous point, it will
39 publish the approximate amount of rendezvous cells it has relayed
40 the past 24 hours. The statistics themselves are obfuscated so
41 that the exact values cannot be derived. For more details see
42 proposal 238, "Better hidden service stats from Tor relays". This
43 feature is currently disabled by default. Implements feature 13192.
45 o Major bugfixes (client, automap):
46 - Repair automapping with IPv6 addresses. This automapping should
47 have worked previously, but one piece of debugging code that we
48 inserted to detect a regression actually caused the regression to
49 manifest itself again. Fixes bug 13811 and bug 12831; bugfix on
50 0.2.4.7-alpha. Diagnosed and fixed by Francisco Blas
53 o Major bugfixes (hidden services):
54 - When closing an introduction circuit that was opened in parallel
55 with others, don't mark the introduction point as unreachable.
56 Previously, the first successful connection to an introduction
57 point would make the other introduction points get marked as
58 having timed out. Fixes bug 13698; bugfix on 0.0.6rc2.
60 o Directory authority changes:
61 - Remove turtles as a directory authority.
62 - Add longclaw as a new (v3) directory authority. This implements
63 ticket 13296. This keeps the directory authority count at 9.
65 o Major removed features:
66 - Tor clients no longer support connecting to hidden services
67 running on Tor 0.2.2.x and earlier; the Support022HiddenServices
68 option has been removed. (There shouldn't be any hidden services
69 running these versions on the network.) Closes ticket 7803.
71 o Minor features (client):
72 - Validate hostnames in SOCKS5 requests more strictly. If SafeSocks
73 is enabled, reject requests with IP addresses as hostnames.
74 Resolves ticket 13315.
76 o Minor features (controller):
77 - Add a "SIGNAL HEARTBEAT" controller command that tells Tor to
78 write an unscheduled heartbeat message to the log. Implements
81 o Minor features (geoip):
82 - Update geoip and geoip6 to the November 15 2014 Maxmind GeoLite2
85 o Minor features (hidden services):
86 - When re-enabling the network, don't try to build introduction
87 circuits until we have successfully built a circuit. This makes
88 hidden services come up faster when the network is re-enabled.
89 Patch from "akwizgran". Closes ticket 13447.
90 - When we fail to a retrieve hidden service descriptor, send the
91 controller an "HS_DESC FAILED" controller event. Implements
93 - New HiddenServiceDirGroupReadable option to cause hidden service
94 directories and hostname files to be created group-readable. Patch
95 from "anon", David Stainton, and "meejah". Closes ticket 11291.
97 o Minor features (systemd):
98 - Where supported, when running with systemd, report successful
99 startup to systemd. Part of ticket 11016. Patch by Michael Scherer.
100 - When running with systemd, support systemd watchdog messages. Part
101 of ticket 11016. Patch by Michael Scherer.
103 o Minor features (transparent proxy):
104 - Update the transparent proxy option checks to allow for both ipfw
105 and pf on OS X. Closes ticket 14002.
106 - Use the correct option when using IPv6 with transparent proxy
107 support on Linux. Resolves 13808. Patch by Francisco Blas
110 o Minor bugfixes (preventative security, C safety):
111 - When reading a hexadecimal, base-32, or base-64 encoded value from
112 a string, always overwrite the whole output buffer. This prevents
113 some bugs where we would look at (but fortunately, not reveal)
114 uninitialized memory on the stack. Fixes bug 14013; bugfix on all
116 - Clear all memory targetted by tor_addr_{to,from}_sockaddr(), not
117 just the part that's used. This makes it harder for data leak bugs
118 to occur in the event of other programming failures. Resolves
121 o Minor bugfixes (client, microdescriptors):
122 - Use a full 256 bits of the SHA256 digest of a microdescriptor when
123 computing which microdescriptors to download. This keeps us from
124 erroneous download behavior if two microdescriptor digests ever
125 have the same first 160 bits. Fixes part of bug 13399; bugfix
127 - Reset a router's status if its microdescriptor digest changes,
128 even if the first 160 bits remain the same. Fixes part of bug
129 13399; bugfix on 0.2.3.1-alpha.
131 o Minor bugfixes (compilation):
132 - Silence clang warnings under --enable-expensive-hardening,
133 including implicit truncation of 64 bit values to 32 bit, const
134 char assignment to self, tautological compare, and additional
135 parentheses around equality tests. Fixes bug 13577; bugfix
137 - Fix a clang warning about checking whether an address in the
138 middle of a structure is NULL. Fixes bug 14001; bugfix
141 o Minor bugfixes (hidden services):
142 - Correctly send a controller event when we find that a rendezvous
143 circuit has finished. Fixes bug 13936; bugfix on 0.1.1.5-alpha.
144 - Pre-check directory permissions for new hidden-services to avoid
145 at least one case of "Bug: Acting on config options left us in a
146 broken state. Dying." Fixes bug 13942; bugfix on 0.0.6pre1.
147 - When adding a new hidden service (for example, via SETCONF), Tor
148 no longer congratulates the user for running a relay. Fixes bug
149 13941; bugfix on 0.2.6.1-alpha.
150 - When fetching hidden service descriptors, we now check not only
151 for whether we got the hidden service we had in mind, but also
152 whether we got the particular descriptors we wanted. This prevents
153 a class of inefficient but annoying DoS attacks by hidden service
154 directories. Fixes bug 13214; bugfix on 0.2.1.6-alpha. Reported
157 o Minor bugfixes (Linux seccomp2 sandbox):
158 - Make transparent proxy support work along with the seccomp2
159 sandbox. Fixes part of bug 13808; bugfix on 0.2.5.1-alpha. Patch
160 by Francisco Blas Izquierdo Riera.
161 - Fix a memory leak in tor-resolve when running with the sandbox
162 enabled. Fixes bug 14050; bugfix on 0.2.5.9-rc.
164 o Minor bugfixes (logging):
165 - Downgrade warnings about RSA signature failures to info log level.
166 Emit a warning when an extra info document is found incompatible
167 with a corresponding router descriptor. Fixes bug 9812; bugfix
169 - Make connection_ap_handshake_attach_circuit() log the circuit ID
170 correctly. Fixes bug 13701; bugfix on 0.0.6.
172 o Minor bugfixes (misc):
173 - Stop allowing invalid address patterns like "*/24" that contain
174 both a wildcard address and a bit prefix length. This affects all
175 our address-range parsing code. Fixes bug 7484; bugfix
178 o Minor bugfixes (testing networks, fast startup):
179 - Allow Tor to build circuits using a consensus with no exits. If
180 the consensus has no exits (typical of a bootstrapping test
181 network), allow Tor to build circuits once enough descriptors have
182 been downloaded. This assists in bootstrapping a testing Tor
183 network. Fixes bug 13718; bugfix on 0.2.4.10-alpha. Patch
185 - When V3AuthVotingInterval is low, give a lower If-Modified-Since
186 header to directory servers. This allows us to obtain consensuses
187 promptly when the consensus interval is very short. This assists
188 in bootstrapping a testing Tor network. Fixes parts of bugs 13718
189 and 13963; bugfix on 0.2.0.3-alpha. Patch by "teor".
190 - Stop assuming that private addresses are local when checking
191 reachability in a TestingTorNetwork. Instead, when testing, assume
192 all OR connections are remote. (This is necessary due to many test
193 scenarios running all relays on localhost.) This assists in
194 bootstrapping a testing Tor network. Fixes bug 13924; bugfix on
195 0.1.0.1-rc. Patch by "teor".
196 - Avoid building exit circuits from a consensus with no exits. Now
197 thanks to our fix for 13718, we accept a no-exit network as not
198 wholly lost, but we need to remember not to try to build exit
199 circuits on it. Closes ticket 13814; patch by "teor".
200 - Stop requiring exits to have non-zero bandwithcapacity in a
201 TestingTorNetwork. Instead, when TestingMinExitFlagThreshold is 0,
202 ignore exit bandwidthcapacity. This assists in bootstrapping a
203 testing Tor network. Fixes parts of bugs 13718 and 13839; bugfix
204 on 0.2.0.3-alpha. Patch by "teor".
205 - Add "internal" to some bootstrap statuses when no exits are
206 available. If the consensus does not contain Exits, Tor will only
207 build internal circuits. In this case, relevant statuses will
208 contain the word "internal" as indicated in the Tor control-
209 spec.txt. When bootstrap completes, Tor will be ready to build
210 internal circuits. If a future consensus contains Exits, exit
211 circuits may become available. Fixes part of bug 13718; bugfix on
212 0.2.4.10-alpha. Patch by "teor".
213 - Decrease minimum consensus interval to 10 seconds when
214 TestingTorNetwork is set, or 5 seconds for the first consensus.
215 Fix assumptions throughout the code that assume larger intervals.
216 Fixes bugs 13718 and 13823; bugfix on 0.2.0.3-alpha. Patch
218 - Avoid excluding guards from path building in minimal test
219 networks, when we're in a test network and excluding guards would
220 exclude all relays. This typically occurs in incredibly small tor
221 networks, and those using "TestingAuthVoteGuard *". Fixes part of
222 bug 13718; bugfix on 0.1.1.11-alpha. Patch by "teor".
224 o Code simplification and refactoring:
225 - Stop using can_complete_circuits as a global variable; access it
226 with a function instead.
227 - Avoid using operators directly as macro arguments: this lets us
228 apply coccinelle transformations to our codebase more directly.
230 - Combine the functions used to parse ClientTransportPlugin and
231 ServerTransportPlugin into a single function. Closes ticket 6456.
232 - Add inline functions and convenience macros for inspecting channel
233 state. Refactor the code to use convenience macros instead of
234 checking channel state directly. Fixes issue 7356.
235 - Document all members of was_router_added_t and rename
236 ROUTER_WAS_NOT_NEW to ROUTER_IS_ALREADY_KNOWN to make it less
237 confusable with ROUTER_WAS_TOO_OLD. Fixes issue 13644.
238 - In connection_exit_begin_conn(), use END_CIRC_REASON_TORPROTOCOL
239 constant instead of hardcoded value. Fixes issue 13840.
240 - Refactor our generic strmap and digestmap types into a single
241 implementation, so that we can add a new digest256map
245 - Document the bridge-authority-only 'networkstatus-bridges' file.
246 Closes ticket 13713; patch from "tom".
247 - Fix typo in PredictedPortsRelevanceTime option description in
248 manpage. Resolves issue 13707.
249 - Stop suggesting that users specify relays by nickname: it isn't a
250 good idea. Also, properly cross-reference how to specify relays in
251 all parts of manual documenting options that take a list of
252 relays. Closes ticket 13381.
253 - Clarify the HiddenServiceDir option description in manpage to make
254 it clear that relative paths are taken with respect to the current
255 working directory. Also clarify that this behavior is not
256 guaranteed to remain indefinitely. Fixes issue 13913.
259 - New tests for many parts of channel, relay, and circuitmux
260 functionality. Code by Andrea; part of 9262.
261 - New tests for parse_transport_line(). Part of ticket 6456.
262 - In the unit tests, use chgrp() to change the group of the unit
263 test temporary directory to the current user, so that the sticky
264 bit doesn't interfere with tests that check directory groups.
266 - Add unit tests for resolve_my_addr(). Part of ticket 12376; patch
270 Changes in version 0.2.6.1-alpha - 2014-10-30
271 Tor 0.2.6.1-alpha is the first release in the Tor 0.2.6.x series. It
272 includes numerous code cleanups and new tests, and fixes a large
273 number of annoying bugs. Out-of-memory conditions are handled better
274 than in 0.2.5, pluggable transports have improved proxy support, and
275 clients now use optimistic data for contacting hidden services. Also,
276 we are now more robust to changes in what we consider a parseable
277 directory object, so that tightening restrictions does not have a risk
278 of introducing infinite download loops.
280 This is the first alpha release in a new series, so expect there to be
281 bugs. Users who would rather test out a more stable branch should stay
282 with 0.2.5.x for now.
284 o New compiler and system requirements:
285 - Tor 0.2.6.x requires that your compiler support more of the C99
286 language standard than before. The 'configure' script now detects
287 whether your compiler supports C99 mid-block declarations and
288 designated initializers. If it does not, Tor will not compile.
290 We may revisit this requirement if it turns out that a significant
291 number of people need to build Tor with compilers that don't
292 bother implementing a 15-year-old standard. Closes ticket 13233.
293 - Tor no longer supports systems without threading support. When we
294 began working on Tor, there were several systems that didn't have
295 threads, or where the thread support wasn't able to run the
296 threads of a single process on multiple CPUs. That no longer
297 holds: every system where Tor needs to run well now has threading
298 support. Resolves ticket 12439.
300 o Removed platform support:
301 - We no longer include special code to build on Windows CE; as far
302 as we know, nobody has used Tor on Windows CE in a very long time.
305 o Major features (bridges):
306 - Expose the outgoing upstream HTTP/SOCKS proxy to pluggable
307 transports if they are configured via the "TOR_PT_PROXY"
308 environment variable. Implements proposal 232. Resolves
311 o Major features (client performance, hidden services):
312 - Allow clients to use optimistic data when connecting to a hidden
313 service, which should remove a round-trip from hidden service
314 initialization. See proposal 181 for details. Implements
317 o Major features (directory system):
318 - Upon receiving an unparseable directory object, if its digest
319 matches what we expected, then don't try to download it again.
320 Previously, when we got a descriptor we didn't like, we would keep
321 trying to download it over and over. Closes ticket 11243.
323 o Major features (sample torrc):
324 - Add a new, infrequently-changed "torrc.minimal". This file is
325 similar to torrc.sample, but it will change as infrequently as
326 possible, for the benefit of users whose systems prompt them for
327 intervention whenever a default configuration file is changed.
328 Making this change allows us to update torrc.sample to be a more
329 generally useful "sample torrc".
331 o Major bugfixes (directory authorities):
332 - Do not assign the HSDir flag to relays if they are not Valid, or
333 currently hibernating. Fixes #12573. Bugfix on tor-0.2.0.10-alpha
335 o Major bugfixes (directory bandwidth performance):
336 - Don't flush the zlib buffer aggressively when compressing
337 directory information for clients. This should save about 7% of
338 the bandwidth currently used for compressed descriptors and
339 microdescriptors. Fixes bug 11787; bugfix on 0.1.1.23.
341 o Minor features (security, memory wiping):
342 - Ensure we securely wipe keys from memory after
343 crypto_digest_get_digest and init_curve25519_keypair_from_file
344 have finished using them. Resolves ticket 13477.
346 o Minor features (security, out-of-memory handling):
347 - When handling an out-of-memory condition, allocate less memory for
348 temporary data structures. Fixes issue 10115.
349 - When handling an out-of-memory condition, consider more types of
350 buffers, including those on directory connections, and zlib
351 buffers. Resolves ticket 11792.
354 - When identity keypair is generated for first time, log a
355 congratulatory message that links to the new relay lifecycle
356 document. Implements feature 10427.
358 o Minor features (client):
359 - Clients are now willing to send optimistic data (before they
360 receive a 'connected' cell) to relays of any version. (Relays
361 without support for optimistic data are no longer supported on the
362 Tor network.) Resolves ticket 13153.
364 o Minor features (directory authorities):
365 - Don't list relays with a bandwidth estimate of 0 in the consensus.
366 Implements a feature proposed during discussion of bug 13000.
367 - In tor-gencert, report an error if the user provides the same
368 argument more than once.
369 - If a directory authority can't find a best consensus method in the
370 votes that it holds, it now falls back to its favorite consensus
371 method. Previously, it fell back to method 1. Neither of these is
372 likely to get enough signatures, but "fall back to favorite"
373 doesn't require us to maintain support an obsolete consensus
374 method. Implements part of proposal 215.
376 o Minor features (logging):
377 - On Unix-like systems, you can now use named pipes as the target of
378 the Log option, and other options that try to append to files.
379 Closes ticket 12061. Patch from "carlo von lynX".
380 - When opening a log file at startup, send it every log message that
381 we generated between startup and opening it. Previously, log
382 messages that were generated before opening the log file were only
383 logged to stdout. Closes ticket 6938.
384 - Add a TruncateLogFile option to overwrite logs instead of
385 appending to them. Closes ticket #5583.
387 o Minor features (portability, Solaris):
388 - Threads are no longer disabled by default on Solaris; we believe
389 that the versions of Solaris with broken threading support are all
390 obsolete by now. Resolves ticket 9495.
392 o Minor features (relay):
393 - Re-check our address after we detect a changed IP address from
394 getsockname(). This ensures that the controller command "GETINFO
395 address" will report the correct value. Resolves ticket 11582.
397 - A new AccountingRule option lets Relays set whether they'd like
398 AccountingMax to be applied separately to inbound and outbound
399 traffic, or applied to the sum of inbound and outbound traffic.
400 Resolves ticket 961. Patch by "chobe".
402 o Minor features (testing networks):
403 - Add the TestingDirAuthVoteExit option, which lists nodes to assign
404 the "Exit" flag regardless of their uptime, bandwidth, or exit
405 policy. TestingTorNetwork must be set for this option to have any
406 effect. Previously, authorities would take up to 35 minutes to
407 give nodes the Exit flag in a test network. Partially implements
410 o Minor features (validation):
411 - Check all date/time values passed to tor_timegm and
412 parse_rfc1123_time for validity, taking leap years into account.
413 Improves HTTP header validation. Implemented with bug 13476.
414 - In correct_tm(), limit the range of values returned by system
415 localtime(_r) and gmtime(_r) to be between the years 1 and 8099.
416 This means we don't have to deal with negative or too large dates,
417 even if a clock is wrong. Otherwise we might fail to read a file
418 written by us which includes such a date. Fixes bug 13476.
420 o Minor bugfixes (bridge clients):
421 - When configured to use a bridge without an identity digest (not
422 recommended), avoid launching an extra channel to it when
423 bootstrapping. Fixes bug 7733; bugfix on 0.2.4.4-alpha.
425 o Minor bugfixes (bridges):
426 - When DisableNetwork is set, do not launch pluggable transport
427 plugins, and if any are running, terminate them. Fixes bug 13213;
428 bugfix on 0.2.3.6-alpha.
430 o Minor bugfixes (C correctness):
431 - Fix several instances of possible integer overflow/underflow/NaN.
432 Fixes bug 13104; bugfix on 0.2.3.1-alpha and later. Patches
434 - In circuit_build_times_calculate_timeout() in circuitstats.c,
435 avoid dividing by zero in the pareto calculations. This traps
436 under clang's "undefined-trap" sanitizer. Fixes bug 13290; bugfix
437 on tor-0.2.2.2-alpha.
438 - Fix an integer overflow in format_time_interval(). Fixes bug
439 13393; bugfix on 0.2.0.10-alpha.
440 - Set the correct day of year value when the system's localtime(_r)
441 or gmtime(_r) functions fail to set struct tm. Not externally
442 visible. Fixes bug 13476; bugfix on 0.0.2pre14.
443 - Avoid unlikely signed integer overflow in tor_timegm on systems
444 with 32-bit time_t. Fixes bug 13476; bugfix on 0.0.2pre14.
446 o Minor bugfixes (client):
447 - Fix smartlist_choose_node_by_bandwidth() so that relays with the
448 BadExit flag are not considered worthy candidates. Fixes bug
449 13066; bugfix on 0.1.2.3-alpha.
450 - Use the consensus schedule for downloading consensuses, and not
451 the generic schedule. Fixes bug 11679; bugfix on 0.2.2.6-alpha.
452 - Handle unsupported or malformed SOCKS5 requests properly by
453 responding with the appropriate error message before closing the
454 connection. Fixes bugs 12971 and 13314; bugfix on 0.0.2pre13.
456 o Minor bugfixes (client, torrc):
457 - Stop modifying the value of our DirReqStatistics torrc option just
458 because we're not a bridge or relay. This bug was causing Tor
459 Browser users to write "DirReqStatistics 0" in their torrc files
460 as if they had chosen to change the config. Fixes bug 4244; bugfix
462 - When GeoIPExcludeUnknown is enabled, do not incorrectly decide
463 that our options have changed every time we SIGHUP. Fixes bug
464 9801; bugfix on 0.2.4.10-alpha. Patch from "qwerty1".
466 o Minor bugfixes (controller):
467 - Return an error when the second or later arguments of the
468 "setevents" controller command are invalid events. Previously we
469 would return success while silently skipping invalid events. Fixes
470 bug 13205; bugfix on 0.2.3.2-alpha. Reported by "fpxnns".
472 o Minor bugfixes (directory system):
473 - Always believe that v3 directory authorities serve extra-info
474 documents, whether they advertise "caches-extra-info" or not.
475 Fixes part of bug 11683; bugfix on 0.2.0.1-alpha.
476 - When running as a v3 directory authority, advertise that you serve
477 extra-info documents so that clients who want them can find them
478 from you too. Fixes part of bug 11683; bugfix on 0.2.0.1-alpha.
479 - Check the BRIDGE_DIRINFO flag bitwise rather than using equality.
480 Previously, directories offering BRIDGE_DIRINFO and some other
481 flag (i.e. microdescriptors or extrainfo) would be ignored when
482 looking for bridges. Partially fixes bug 13163; bugfix
485 o Minor bugfixes (networking):
486 - Check for orconns and use connection_or_close_for_error() rather
487 than connection_mark_for_close() directly in the getsockopt()
488 failure case of connection_handle_write_impl(). Fixes bug 11302;
489 bugfix on 0.2.4.4-alpha.
491 o Minor bugfixes (relay):
492 - When generating our family list, remove spaces from around the
493 entries. Fixes bug 12728; bugfix on 0.2.1.7-alpha.
494 - If our previous bandwidth estimate was 0 bytes, allow publishing a
495 new relay descriptor immediately. Fixes bug 13000; bugfix
498 o Minor bugfixes (testing networks):
499 - Fix TestingDirAuthVoteGuard to properly give out Guard flags in a
500 testing network. Fixes bug 13064; bugfix on 0.2.5.2-alpha.
501 - Stop using the default authorities in networks which provide both
502 AlternateDirAuthority and AlternateBridgeAuthority. Partially
503 fixes bug 13163; bugfix on 0.2.0.13-alpha.
505 o Minor bugfixes (testing):
506 - Stop spawn test failures due to a race condition between the
507 SIGCHLD handler updating the process status, and the test reading
508 it. Fixes bug 13291; bugfix on 0.2.3.3-alpha.
510 o Minor bugfixes (testing, Windows):
511 - Avoid passing an extra backslash when creating a temporary
512 directory for running the unit tests on Windows. Fixes bug 12392;
513 bugfix on 0.2.2.25-alpha. Patch from Gisle Vanem.
515 o Minor bugfixes (windows):
516 - Remove code to special-case handling of NTE_BAD_KEYSET when
517 acquiring windows CryptoAPI context. This error can't actually
518 occur for the parameters we're providing. Fixes bug 10816; bugfix
521 o Minor bugfixes (zlib):
522 - Avoid truncating a zlib stream when trying to finalize it with an
523 empty output buffer. Fixes bug 11824; bugfix on 0.1.1.23.
526 - Allow our configure script to build correctly with autoconf 2.62
527 again. Fixes bug 12693; bugfix on 0.2.5.2-alpha.
528 - Improve the error message from ./configure to make it clear that
529 when asciidoc has not been found, the user will have to either add
530 --disable-asciidoc argument or install asciidoc. Resolves
533 o Code simplification and refactoring:
534 - Change the entry_is_live() function to take named bitfield
535 elements instead of an unnamed list of booleans. Closes
537 - Refactor and unit-test entry_is_time_to_retry() in entrynodes.c.
538 Resolves ticket 12205.
539 - Use calloc and reallocarray functions instead of multiply-
540 then-malloc. This makes it less likely for us to fall victim to an
541 integer overflow attack when allocating. Resolves ticket 12855.
542 - Use the standard macro name SIZE_MAX, instead of our
544 - Document usage of the NO_DIRINFO and ALL_DIRINFO flags clearly in
545 functions which take them as arguments. Replace 0 with NO_DIRINFO
546 in a function call for clarity. Seeks to prevent future issues
548 - Avoid 4 null pointer errors under clang static analysis by using
549 tor_assert() to prove that the pointers aren't null. Fixes
551 - Rework the API of policies_parse_exit_policy() to use a bitmask to
552 represent parsing options, instead of a confusing mess of
553 booleans. Resolves ticket 8197.
554 - Introduce a helper function to parse ExitPolicy in
555 or_options_t structure.
558 - Add a doc/TUNING document with tips for handling large numbers of
559 TCP connections when running busy Tor relay. Update the warning
560 message to point to this file when running out of sockets
561 operating system is allowing to use simultaneously. Resolves
565 - We no longer remind the user about configuration options that have
566 been obsolete since 0.2.3.x or earlier. Patch by Adrien Bak.
567 - Remove our old, non-weighted bandwidth-based node selection code.
568 Previously, we used it as a fallback when we couldn't perform
569 weighted bandwidth-based node selection. But that would only
570 happen in the cases where we had no consensus, or when we had a
571 consensus generated by buggy or ancient directory authorities. In
572 either case, it's better to use the more modern, better maintained
573 algorithm, with reasonable defaults for the weights. Closes
575 - Remove the --disable-curve25519 configure option. Relays and
576 clients now are required to support curve25519 and the
578 - The old "StrictEntryNodes" and "StrictExitNodes" options, which
579 used to be deprecated synonyms for "StrictNodes", are now marked
580 obsolete. Resolves ticket 12226.
581 - Clients don't understand the BadDirectory flag in the consensus
582 anymore, and ignore it.
585 - Refactor the function that chooses guard nodes so that it can more
586 easily be tested; write some tests for it.
587 - Fix and re-enable the fgets_eagain unit test. Fixes bug 12503;
588 bugfix on 0.2.3.1-alpha. Patch from "cypherpunks."
589 - Create unit tests for format_time_interval(). With bug 13393.
590 - Add unit tests for tor_timegm signed overflow, tor_timegm and
591 parse_rfc1123_time validity checks, correct_tm year clamping. Unit
592 tests (visible) fixes in bug 13476.
593 - Add a "coverage-html" make target to generate HTML-visualized
594 coverage results when building with --enable-coverage. (Requires
595 lcov.) Patch from Kevin Murray.
596 - Enable the backtrace handler (where supported) when running the
598 - Revise all unit tests that used the legacy test_* macros to
599 instead use the recommended tt_* macros. This patch was generated
600 with coccinelle, to avoid manual errors. Closes ticket 13119.
602 o Distribution (systemd):
603 - systemd unit file: only allow tor to write to /var/lib/tor and
604 /var/log/tor. The rest of the filesystem is accessible for reading
605 only. Patch by intrigeri; resolves ticket 12751.
606 - systemd unit file: ensure that the process and all its children
607 can never gain new privileges. Patch by intrigeri; resolves
609 - systemd unit file: set up /var/run/tor as writable for the Tor
610 service. Patch by intrigeri; resolves ticket 13196.
612 o Removed features (directory authorities):
613 - Remove code that prevented authorities from listing Tor relays
614 affected by CVE-2011-2769 as guards. These relays are already
615 rejected altogether due to the minimum version requirement of
616 0.2.3.16-alpha. Closes ticket 13152.
617 - The "AuthDirRejectUnlisted" option no longer has any effect, as
618 the fingerprints file (approved-routers) has been deprecated.
619 - Directory authorities do not support being Naming dirauths anymore.
620 The "NamingAuthoritativeDir" config option is now obsolete.
621 - Directory authorities do not support giving out the BadDirectory
623 - Directory authorities no longer advertise or support consensus
624 methods 1 through 12 inclusive. These consensus methods were
625 obsolete and/or insecure: maintaining the ability to support them
626 served no good purpose. Implements part of proposal 215; closes
629 o Testing (test-network.sh):
630 - Stop using "echo -n", as some shells' built-in echo doesn't
631 support "-n". Instead, use "/bin/echo -n". Partially fixes
633 - Stop an apparent test-network hang when used with make -j2. Fixes
635 - Add a --delay option to test-network.sh, which configures the
636 delay before the chutney network tests for data transmission.
637 Partially implements ticket 13161.
640 Changes in version 0.2.5.10 - 2014-10-24
641 Tor 0.2.5.10 is the first stable release in the 0.2.5 series.
643 It adds several new security features, including improved
644 denial-of-service resistance for relays, new compiler hardening
645 options, and a system-call sandbox for hardened installations on Linux
646 (requires seccomp2). The controller protocol has several new features,
647 resolving IPv6 addresses should work better than before, and relays
648 should be a little more CPU-efficient. We've added support for more
649 OpenBSD and FreeBSD transparent proxy types. We've improved the build
650 system and testing infrastructure to allow unit testing of more parts
651 of the Tor codebase. Finally, we've addressed several nagging pluggable
652 transport usability issues, and included numerous other small bugfixes
653 and features mentioned below.
655 This release marks end-of-life for Tor 0.2.3.x; those Tor versions
656 have accumulated many known flaws; everyone should upgrade.
658 o Deprecated versions:
659 - Tor 0.2.3.x has reached end-of-life; it has received no patches or
660 attention for some while.
663 Changes in version 0.2.5.9-rc - 2014-10-20
664 Tor 0.2.5.9-rc is the third release candidate for the Tor 0.2.5.x
665 series. It disables SSL3 in response to the recent "POODLE" attack
666 (even though POODLE does not affect Tor). It also works around a crash
667 bug caused by some operating systems' response to the "POODLE" attack
668 (which does affect Tor). It also contains a few miscellaneous fixes.
670 o Major security fixes:
671 - Disable support for SSLv3. All versions of OpenSSL in use with Tor
672 today support TLS 1.0 or later, so we can safely turn off support
673 for this old (and insecure) protocol. Fixes bug 13426.
675 o Major bugfixes (openssl bug workaround):
676 - Avoid crashing when using OpenSSL version 0.9.8zc, 1.0.0o, or
677 1.0.1j, built with the 'no-ssl3' configuration option. Fixes bug
678 13471. This is a workaround for an OpenSSL bug.
681 - Disable the sandbox name resolver cache when running tor-resolve:
682 tor-resolve doesn't use the sandbox code, and turning it on was
683 breaking attempts to do tor-resolve on a non-default server on
684 Linux. Fixes bug 13295; bugfix on 0.2.5.3-alpha.
687 - Build and run correctly on systems like OpenBSD-current that have
688 patched OpenSSL to remove get_cipher_by_char and/or its
689 implementations. Fixes issue 13325.
691 o Downgraded warnings:
692 - Downgrade the severity of the 'unexpected sendme cell from client'
693 from 'warn' to 'protocol warning'. Closes ticket 8093.
696 Changes in version 0.2.4.25 - 2014-10-20
697 Tor 0.2.4.25 disables SSL3 in response to the recent "POODLE" attack
698 (even though POODLE does not affect Tor). It also works around a crash
699 bug caused by some operating systems' response to the "POODLE" attack
700 (which does affect Tor).
702 o Major security fixes (also in 0.2.5.9-rc):
703 - Disable support for SSLv3. All versions of OpenSSL in use with Tor
704 today support TLS 1.0 or later, so we can safely turn off support
705 for this old (and insecure) protocol. Fixes bug 13426.
707 o Major bugfixes (openssl bug workaround, also in 0.2.5.9-rc):
708 - Avoid crashing when using OpenSSL version 0.9.8zc, 1.0.0o, or
709 1.0.1j, built with the 'no-ssl3' configuration option. Fixes bug
710 13471. This is a workaround for an OpenSSL bug.
713 Changes in version 0.2.5.8-rc - 2014-09-22
714 Tor 0.2.5.8-rc is the second release candidate for the Tor 0.2.5.x
715 series. It fixes a bug that affects consistency and speed when
716 connecting to hidden services, and it updates the location of one of
717 the directory authorities.
720 - Clients now send the correct address for their chosen rendezvous
721 point when trying to access a hidden service. They used to send
722 the wrong address, which would still work some of the time because
723 they also sent the identity digest of the rendezvous point, and if
724 the hidden service happened to try connecting to the rendezvous
725 point from a relay that already had a connection open to it,
726 the relay would reuse that connection. Now connections to hidden
727 services should be more robust and faster. Also, this bug meant
728 that clients were leaking to the hidden service whether they were
729 on a little-endian (common) or big-endian (rare) system, which for
730 some users might have reduced their anonymity. Fixes bug 13151;
731 bugfix on 0.2.1.5-alpha.
733 o Directory authority changes:
734 - Change IP address for gabelmoo (v3 directory authority).
737 Changes in version 0.2.4.24 - 2014-09-22
738 Tor 0.2.4.24 fixes a bug that affects consistency and speed when
739 connecting to hidden services, and it updates the location of one of
740 the directory authorities.
743 - Clients now send the correct address for their chosen rendezvous
744 point when trying to access a hidden service. They used to send
745 the wrong address, which would still work some of the time because
746 they also sent the identity digest of the rendezvous point, and if
747 the hidden service happened to try connecting to the rendezvous
748 point from a relay that already had a connection open to it,
749 the relay would reuse that connection. Now connections to hidden
750 services should be more robust and faster. Also, this bug meant
751 that clients were leaking to the hidden service whether they were
752 on a little-endian (common) or big-endian (rare) system, which for
753 some users might have reduced their anonymity. Fixes bug 13151;
754 bugfix on 0.2.1.5-alpha.
756 o Directory authority changes:
757 - Change IP address for gabelmoo (v3 directory authority).
759 o Minor features (geoip):
760 - Update geoip and geoip6 to the August 7 2014 Maxmind GeoLite2
764 Changes in version 0.2.5.7-rc - 2014-09-11
765 Tor 0.2.5.7-rc fixes several regressions from earlier in the 0.2.5.x
766 release series, and some long-standing bugs related to ORPort reachability
767 testing and failure to send CREATE cells. It is the first release
768 candidate for the Tor 0.2.5.x series.
770 o Major bugfixes (client, startup):
771 - Start making circuits as soon as DisabledNetwork is turned off.
772 When Tor started with DisabledNetwork set, it would correctly
773 conclude that it shouldn't build circuits, but it would mistakenly
774 cache this conclusion, and continue believing it even when
775 DisableNetwork is set to 0. Fixes the bug introduced by the fix
776 for bug 11200; bugfix on 0.2.5.4-alpha.
777 - Resume expanding abbreviations for command-line options. The fix
778 for bug 4647 accidentally removed our hack from bug 586 that
779 rewrote HashedControlPassword to __HashedControlSessionPassword
780 when it appears on the commandline (which allowed the user to set
781 her own HashedControlPassword in the torrc file while the
782 controller generates a fresh session password for each run). Fixes
783 bug 12948; bugfix on 0.2.5.1-alpha.
784 - Warn about attempts to run hidden services and relays in the same
785 process: that's probably not a good idea. Closes ticket 12908.
787 o Major bugfixes (relay):
788 - Avoid queuing or sending destroy cells for circuit ID zero when we
789 fail to send a CREATE cell. Fixes bug 12848; bugfix on 0.0.8pre1.
790 Found and fixed by "cypherpunks".
791 - Fix ORPort reachability detection on relays running behind a
792 proxy, by correctly updating the "local" mark on the controlling
793 channel when changing the address of an or_connection_t after the
794 handshake. Fixes bug 12160; bugfix on 0.2.4.4-alpha.
796 o Minor features (bridge):
797 - Add an ExtORPortCookieAuthFileGroupReadable option to make the
798 cookie file for the ExtORPort g+r by default.
800 o Minor features (geoip):
801 - Update geoip and geoip6 to the August 7 2014 Maxmind GeoLite2
804 o Minor bugfixes (logging):
805 - Reduce the log severity of the "Pluggable transport proxy does not
806 provide any needed transports and will not be launched." message,
807 since Tor Browser includes several ClientTransportPlugin lines in
808 its torrc-defaults file, leading every Tor Browser user who looks
809 at her logs to see these notices and wonder if they're dangerous.
810 Resolves bug 13124; bugfix on 0.2.5.3-alpha.
811 - Downgrade "Unexpected onionskin length after decryption" warning
812 to a protocol-warn, since there's nothing relay operators can do
813 about a client that sends them a malformed create cell. Resolves
814 bug 12996; bugfix on 0.0.6rc1.
815 - Log more specific warnings when we get an ESTABLISH_RENDEZVOUS
816 cell on a cannibalized or non-OR circuit. Resolves ticket 12997.
817 - When logging information about an EXTEND2 or EXTENDED2 cell, log
818 their names correctly. Fixes part of bug 12700; bugfix
820 - When logging information about a relay cell whose command we don't
821 recognize, log its command as an integer. Fixes part of bug 12700;
822 bugfix on 0.2.1.10-alpha.
823 - Escape all strings from the directory connection before logging
824 them. Fixes bug 13071; bugfix on 0.1.1.15. Patch from "teor".
826 o Minor bugfixes (controller):
827 - Restore the functionality of CookieAuthFileGroupReadable. Fixes
828 bug 12864; bugfix on 0.2.5.1-alpha.
829 - Actually send TRANSPORT_LAUNCHED and HS_DESC events to
830 controllers. Fixes bug 13085; bugfix on 0.2.5.1-alpha. Patch
833 o Minor bugfixes (compilation):
834 - Fix compilation of test.h with MSVC. Patch from Gisle Vanem;
835 bugfix on 0.2.5.5-alpha.
836 - Make the nmake make files work again. Fixes bug 13081. Bugfix on
837 0.2.5.1-alpha. Patch from "NewEraCracker".
838 - In routerlist_assert_ok(), don't take the address of a
839 routerinfo's cache_info member unless that routerinfo is non-NULL.
840 Fixes bug 13096; bugfix on 0.1.1.9-alpha. Patch by "teor".
841 - Fix a large number of false positive warnings from the clang
842 analyzer static analysis tool. This should make real warnings
843 easier for clang analyzer to find. Patch from "teor". Closes
846 o Distribution (systemd):
847 - Verify configuration file via ExecStartPre in the systemd unit
848 file. Patch from intrigeri; resolves ticket 12730.
849 - Explicitly disable RunAsDaemon in the systemd unit file. Our
850 current systemd unit uses "Type = simple", so systemd does not
851 expect tor to fork. If the user has "RunAsDaemon 1" in their
852 torrc, then things won't work as expected. This is e.g. the case
853 on Debian (and derivatives), since there we pass "--defaults-torrc
854 /usr/share/tor/tor-service-defaults-torrc" (that contains
855 "RunAsDaemon 1") by default. Patch by intrigeri; resolves
859 - Adjust the URLs in the README to refer to the new locations of
860 several documents on the website. Fixes bug 12830. Patch from
862 - Document 'reject6' and 'accept6' ExitPolicy entries. Resolves
866 Changes in version 0.2.5.6-alpha - 2014-07-28
867 Tor 0.2.5.6-alpha brings us a big step closer to slowing down the
868 risk from guard rotation, and fixes a variety of other issues to get
869 us closer to a release candidate.
871 o Major features (also in 0.2.4.23):
872 - Make the number of entry guards configurable via a new
873 NumEntryGuards consensus parameter, and the number of directory
874 guards configurable via a new NumDirectoryGuards consensus
875 parameter. Implements ticket 12688.
877 o Major bugfixes (also in 0.2.4.23):
878 - Fix a bug in the bounds-checking in the 32-bit curve25519-donna
879 implementation that caused incorrect results on 32-bit
880 implementations when certain malformed inputs were used along with
881 a small class of private ntor keys. This bug does not currently
882 appear to allow an attacker to learn private keys or impersonate a
883 Tor server, but it could provide a means to distinguish 32-bit Tor
884 implementations from 64-bit Tor implementations. Fixes bug 12694;
885 bugfix on 0.2.4.8-alpha. Bug found by Robert Ransom; fix from
889 - Perform circuit cleanup operations even when circuit
890 construction operations are disabled (because the network is
891 disabled, or because there isn't enough directory information).
892 Previously, when we were not building predictive circuits, we
893 were not closing expired circuits either. Fixes bug 8387; bugfix on
894 0.1.1.11-alpha. This bug became visible in 0.2.4.10-alpha when we
895 became more strict about when we have "enough directory information
899 - Authorities now assign the Guard flag to the fastest 25% of the
900 network (it used to be the fastest 50%). Also raise the consensus
901 weight that guarantees the Guard flag from 250 to 2000. For the
902 current network, this results in about 1100 guards, down from 2500.
903 This step paves the way for moving the number of entry guards
904 down to 1 (proposal 236) while still providing reasonable expected
905 performance for most users. Implements ticket 12690.
906 - Update geoip and geoip6 to the July 10 2014 Maxmind GeoLite2
908 - Slightly enhance the diagnostic message for bug 12184.
910 o Minor bugfixes (also in 0.2.4.23):
911 - Warn and drop the circuit if we receive an inbound 'relay early'
912 cell. Those used to be normal to receive on hidden service circuits
913 due to bug 1038, but the buggy Tor versions are long gone from
914 the network so we can afford to resume watching for them. Resolves
915 the rest of bug 1038; bugfix on 0.2.1.19.
916 - Correct a confusing error message when trying to extend a circuit
917 via the control protocol but we don't know a descriptor or
918 microdescriptor for one of the specified relays. Fixes bug 12718;
919 bugfix on 0.2.3.1-alpha.
922 - Fix compilation when building with bufferevents enabled. (This
923 configuration is still not expected to work, however.)
924 Fixes bugs 12438, 12474, 11578; bugfixes on 0.2.5.1-alpha and
925 0.2.5.3-alpha. Patches from Anthony G. Basile and Sathyanarayanan
927 - Compile correctly with builds and forks of OpenSSL (such as
928 LibreSSL) that disable compression. Fixes bug 12602; bugfix on
929 0.2.1.1-alpha. Patch from "dhill".
932 Changes in version 0.2.4.23 - 2014-07-28
933 Tor 0.2.4.23 brings us a big step closer to slowing down the risk from
934 guard rotation, and also backports several important fixes from the
935 Tor 0.2.5 alpha release series.
938 - Clients now look at the "usecreatefast" consensus parameter to
939 decide whether to use CREATE_FAST or CREATE cells for the first hop
940 of their circuit. This approach can improve security on connections
941 where Tor's circuit handshake is stronger than the available TLS
942 connection security levels, but the tradeoff is more computational
943 load on guard relays. Implements proposal 221. Resolves ticket 9386.
944 - Make the number of entry guards configurable via a new
945 NumEntryGuards consensus parameter, and the number of directory
946 guards configurable via a new NumDirectoryGuards consensus
947 parameter. Implements ticket 12688.
950 - Fix a bug in the bounds-checking in the 32-bit curve25519-donna
951 implementation that caused incorrect results on 32-bit
952 implementations when certain malformed inputs were used along with
953 a small class of private ntor keys. This bug does not currently
954 appear to allow an attacker to learn private keys or impersonate a
955 Tor server, but it could provide a means to distinguish 32-bit Tor
956 implementations from 64-bit Tor implementations. Fixes bug 12694;
957 bugfix on 0.2.4.8-alpha. Bug found by Robert Ransom; fix from
961 - Warn and drop the circuit if we receive an inbound 'relay early'
962 cell. Those used to be normal to receive on hidden service circuits
963 due to bug 1038, but the buggy Tor versions are long gone from
964 the network so we can afford to resume watching for them. Resolves
965 the rest of bug 1038; bugfix on 0.2.1.19.
966 - Correct a confusing error message when trying to extend a circuit
967 via the control protocol but we don't know a descriptor or
968 microdescriptor for one of the specified relays. Fixes bug 12718;
969 bugfix on 0.2.3.1-alpha.
970 - Avoid an illegal read from stack when initializing the TLS
971 module using a version of OpenSSL without all of the ciphers
972 used by the v2 link handshake. Fixes bug 12227; bugfix on
973 0.2.4.8-alpha. Found by "starlight".
976 - Update geoip and geoip6 to the July 10 2014 Maxmind GeoLite2
980 Changes in version 0.2.5.5-alpha - 2014-06-18
981 Tor 0.2.5.5-alpha fixes a wide variety of remaining issues in the Tor
982 0.2.5.x release series, including a couple of DoS issues, some
983 performance regressions, a large number of bugs affecting the Linux
984 seccomp2 sandbox code, and various other bugfixes. It also adds
985 diagnostic bugfixes for a few tricky issues that we're trying to
988 o Major features (security, traffic analysis resistance):
989 - Several major improvements to the algorithm used to decide when to
990 close TLS connections. Previous versions of Tor closed connections
991 at a fixed interval after the last time a non-padding cell was
992 sent over the connection, regardless of the target of the
993 connection. Now, we randomize the intervals by adding up to 50% of
994 their base value, we measure the length of time since connection
995 last had at least one circuit, and we allow connections to known
996 ORs to remain open a little longer (15 minutes instead of 3
997 minutes minimum). These changes should improve Tor's resistance
998 against some kinds of traffic analysis, and lower some overhead
999 from needlessly closed connections. Fixes ticket 6799.
1000 Incidentally fixes ticket 12023; bugfix on 0.2.5.1-alpha.
1002 o Major bugfixes (security, OOM, new since 0.2.5.4-alpha, also in 0.2.4.22):
1003 - Fix a memory leak that could occur if a microdescriptor parse
1004 fails during the tokenizing step. This bug could enable a memory
1005 exhaustion attack by directory servers. Fixes bug 11649; bugfix
1008 o Major bugfixes (security, directory authorities):
1009 - Directory authorities now include a digest of each relay's
1010 identity key as a part of its microdescriptor.
1012 This is a workaround for bug 11743 (reported by "cypherpunks"),
1013 where Tor clients do not support receiving multiple
1014 microdescriptors with the same SHA256 digest in the same
1015 consensus. When clients receive a consensus like this, they only
1016 use one of the relays. Without this fix, a hostile relay could
1017 selectively disable some client use of target relays by
1018 constructing a router descriptor with a different identity and the
1019 same microdescriptor parameters and getting the authorities to
1020 list it in a microdescriptor consensus. This fix prevents an
1021 attacker from causing a microdescriptor collision, because the
1022 router's identity is not forgeable.
1024 o Major bugfixes (relay):
1025 - Use a direct dirport connection when uploading non-anonymous
1026 descriptors to the directory authorities. Previously, relays would
1027 incorrectly use tunnel connections under a fairly wide variety of
1028 circumstances. Fixes bug 11469; bugfix on 0.2.4.3-alpha.
1029 - When a circuit accidentally has the same circuit ID for its
1030 forward and reverse direction, correctly detect the direction of
1031 cells using that circuit. Previously, this bug made roughly one
1032 circuit in a million non-functional. Fixes bug 12195; this is a
1033 bugfix on every version of Tor.
1035 o Major bugfixes (client, pluggable transports):
1036 - When managing pluggable transports, use OS notification facilities
1037 to learn if they have crashed, and don't attempt to kill any
1038 process that has already exited. Fixes bug 8746; bugfix
1041 o Minor features (diagnostic):
1042 - When logging a warning because of bug 7164, additionally check the
1043 hash table for consistency (as proposed on ticket 11737). This may
1044 help diagnose bug 7164.
1045 - When we log a heartbeat, log how many one-hop circuits we have
1046 that are at least 30 minutes old, and log status information about
1047 a few of them. This is an attempt to track down bug 8387.
1048 - When encountering an unexpected CR while writing text to a file on
1049 Windows, log the name of the file. Should help diagnosing
1051 - Give more specific warnings when a client notices that an onion
1052 handshake has failed. Fixes ticket 9635.
1053 - Add significant new logging code to attempt to diagnose bug 12184,
1054 where relays seem to run out of available circuit IDs.
1055 - Improve the diagnostic log message for bug 8387 even further to
1056 try to improve our odds of figuring out why one-hop directory
1057 circuits sometimes do not get closed.
1059 o Minor features (security, memory management):
1060 - Memory allocation tricks (mempools and buffer freelists) are now
1061 disabled by default. You can turn them back on with
1062 --enable-mempools and --enable-buf-freelists respectively. We're
1063 disabling these features because malloc performance is good enough
1064 on most platforms, and a similar feature in OpenSSL exacerbated
1065 exploitation of the Heartbleed attack. Resolves ticket 11476.
1067 o Minor features (security):
1068 - Apply the secure SipHash-2-4 function to the hash table mapping
1069 circuit IDs and channels to circuits. We missed this one when we
1070 were converting all the other hash functions to use SipHash back
1071 in 0.2.5.3-alpha. Resolves ticket 11750.
1073 o Minor features (build):
1074 - The configure script has a --disable-seccomp option to turn off
1075 support for libseccomp on systems that have it, in case it (or
1076 Tor's use of it) is broken. Resolves ticket 11628.
1078 o Minor features (other):
1079 - Update geoip and geoip6 to the June 4 2014 Maxmind GeoLite2
1082 o Minor bugfixes (security, new since 0.2.5.4-alpha, also in 0.2.4.22):
1083 - When running a hidden service, do not allow TunneledDirConns 0;
1084 this will keep the hidden service from running, and also
1085 make it publish its descriptors directly over HTTP. Fixes bug 10849;
1086 bugfix on 0.2.1.1-alpha.
1088 o Minor bugfixes (performance):
1089 - Avoid a bug where every successful connection made us recompute
1090 the flag telling us whether we have sufficient information to
1091 build circuits. Previously, we would forget our cached value
1092 whenever we successfully opened a channel (or marked a router as
1093 running or not running for any other reason), regardless of
1094 whether we had previously believed the router to be running. This
1095 forced us to run an expensive update operation far too often.
1096 Fixes bug 12170; bugfix on 0.1.2.1-alpha.
1097 - Avoid using tor_memeq() for checking relay cell integrity. This
1098 removes a possible performance bottleneck. Fixes part of bug
1099 12169; bugfix on 0.2.1.31.
1101 o Minor bugfixes (compilation):
1102 - Fix compilation of test_status.c when building with MVSC. Bugfix
1103 on 0.2.5.4-alpha. Patch from Gisle Vanem.
1104 - Resolve GCC complaints on OpenBSD about discarding constness in
1105 TO_{ORIGIN,OR}_CIRCUIT functions. Fixes part of bug 11633; bugfix
1106 on 0.1.1.23. Patch from Dana Koch.
1107 - Resolve clang complaints on OpenBSD with -Wshorten-64-to-32 due to
1108 treatment of long and time_t as comparable types. Fixes part of
1109 bug 11633. Patch from Dana Koch.
1110 - Make Tor compile correctly with --disable-buf-freelists. Fixes bug
1111 11623; bugfix on 0.2.5.3-alpha.
1112 - When deciding whether to build the 64-bit curve25519
1113 implementation, detect platforms where we can compile 128-bit
1114 arithmetic but cannot link it. Fixes bug 11729; bugfix on
1115 0.2.4.8-alpha. Patch from "conradev".
1116 - Fix compilation when DNS_CACHE_DEBUG is enabled. Fixes bug 11761;
1117 bugfix on 0.2.3.13-alpha. Found by "cypherpunks".
1118 - Fix compilation with dmalloc. Fixes bug 11605; bugfix
1121 o Minor bugfixes (Directory server):
1122 - When sending a compressed set of descriptors or microdescriptors,
1123 make sure to finalize the zlib stream. Previously, we would write
1124 all the compressed data, but if the last descriptor we wanted to
1125 send was missing or too old, we would not mark the stream as
1126 finished. This caused problems for decompression tools. Fixes bug
1127 11648; bugfix on 0.1.1.23.
1129 o Minor bugfixes (Linux seccomp sandbox):
1130 - Make the seccomp sandbox code compile under ARM Linux. Fixes bug
1131 11622; bugfix on 0.2.5.1-alpha.
1132 - Avoid crashing when re-opening listener ports with the seccomp
1133 sandbox active. Fixes bug 12115; bugfix on 0.2.5.1-alpha.
1134 - Avoid crashing with the seccomp sandbox enabled along with
1135 ConstrainedSockets. Fixes bug 12139; bugfix on 0.2.5.1-alpha.
1136 - When we receive a SIGHUP with the sandbox enabled, correctly
1137 support rotating our log files. Fixes bug 12032; bugfix
1139 - Avoid crash when running with sandboxing enabled and
1140 DirReqStatistics not disabled. Fixes bug 12035; bugfix
1142 - Fix a "BUG" warning when trying to write bridge-stats files with
1143 the Linux syscall sandbox filter enabled. Fixes bug 12041; bugfix
1145 - Prevent the sandbox from crashing on startup when run with the
1146 --enable-expensive-hardening configuration option. Fixes bug
1147 11477; bugfix on 0.2.5.4-alpha.
1148 - When running with DirPortFrontPage and sandboxing both enabled,
1149 reload the DirPortFrontPage correctly when restarting. Fixes bug
1150 12028; bugfix on 0.2.5.1-alpha.
1151 - Don't try to enable the sandbox when using the Tor binary to check
1152 its configuration, hash a passphrase, or so on. Doing so was
1153 crashing on startup for some users. Fixes bug 11609; bugfix
1155 - Avoid warnings when running with sandboxing and node statistics
1156 enabled at the same time. Fixes part of 12064; bugfix on
1157 0.2.5.1-alpha. Patch from Michael Wolf.
1158 - Avoid warnings when running with sandboxing enabled at the same
1159 time as cookie authentication, hidden services, or directory
1160 authority voting. Fixes part of 12064; bugfix on 0.2.5.1-alpha.
1161 - Do not allow options that require calls to exec to be enabled
1162 alongside the seccomp2 sandbox: they will inevitably crash. Fixes
1163 bug 12043; bugfix on 0.2.5.1-alpha.
1164 - Handle failures in getpwnam()/getpwuid() when running with the
1165 User option set and the Linux syscall sandbox enabled. Fixes bug
1166 11946; bugfix on 0.2.5.1-alpha.
1167 - Refactor the getaddrinfo workaround that the seccomp sandbox uses
1168 to avoid calling getaddrinfo() after installing the sandbox
1169 filters. Previously, it preloaded a cache with the IPv4 address
1170 for our hostname, and nothing else. Now, it loads the cache with
1171 every address that it used to initialize the Tor process. Fixes
1172 bug 11970; bugfix on 0.2.5.1-alpha.
1174 o Minor bugfixes (pluggable transports):
1175 - Enable the ExtORPortCookieAuthFile option, to allow changing the
1176 default location of the authentication token for the extended OR
1177 Port as used by sever-side pluggable transports. We had
1178 implemented this option before, but the code to make it settable
1179 had been omitted. Fixes bug 11635; bugfix on 0.2.5.1-alpha.
1180 - Avoid another 60-second delay when starting Tor in a pluggable-
1181 transport-using configuration when we already have cached
1182 descriptors for our bridges. Fixes bug 11965; bugfix
1185 o Minor bugfixes (client):
1186 - Avoid "Tried to open a socket with DisableNetwork set" warnings
1187 when starting a client with bridges configured and DisableNetwork
1188 set. (Tor launcher starts Tor with DisableNetwork set the first
1189 time it runs.) Fixes bug 10405; bugfix on 0.2.3.9-alpha.
1191 o Minor bugfixes (testing):
1192 - The Python parts of the test scripts now work on Python 3 as well
1193 as Python 2, so systems where '/usr/bin/python' is Python 3 will
1194 no longer have the tests break. Fixes bug 11608; bugfix
1196 - When looking for versions of python that we could run the tests
1197 with, check for "python2.7" and "python3.3"; previously we were
1198 only looking for "python", "python2", and "python3". Patch from
1199 Dana Koch. Fixes bug 11632; bugfix on 0.2.5.2-alpha.
1200 - Fix all valgrind warnings produced by the unit tests. There were
1201 over a thousand memory leak warnings previously, mostly produced
1202 by forgetting to free things in the unit test code. Fixes bug
1203 11618, bugfixes on many versions of Tor.
1205 o Minor bugfixes (tor-fw-helper):
1206 - Give a correct log message when tor-fw-helper fails to launch.
1207 (Previously, we would say something like "tor-fw-helper sent us a
1208 string we could not parse".) Fixes bug 9781; bugfix
1211 o Minor bugfixes (relay, threading):
1212 - Check return code on spawn_func() in cpuworker code, so that we
1213 don't think we've spawned a nonworking cpuworker and write junk to
1214 it forever. Fix related to bug 4345; bugfix on all released Tor
1215 versions. Found by "skruffy".
1216 - Use a pthread_attr to make sure that spawn_func() cannot return an
1217 error while at the same time launching a thread. Fix related to
1218 bug 4345; bugfix on all released Tor versions. Reported
1221 o Minor bugfixes (relay, oom prevention):
1222 - Correctly detect the total available system memory. We tried to do
1223 this in 0.2.5.4-alpha, but the code was set up to always return an
1224 error value, even on success. Fixes bug 11805; bugfix
1227 o Minor bugfixes (relay, other):
1228 - We now drop CREATE cells for already-existent circuit IDs and for
1229 zero-valued circuit IDs, regardless of other factors that might
1230 otherwise have called for DESTROY cells. Fixes bug 12191; bugfix
1232 - Avoid an illegal read from stack when initializing the TLS module
1233 using a version of OpenSSL without all of the ciphers used by the
1234 v2 link handshake. Fixes bug 12227; bugfix on 0.2.4.8-alpha. Found
1236 - When rejecting DATA cells for stream_id zero, still count them
1237 against the circuit's deliver window so that we don't fail to send
1238 a SENDME. Fixes bug 11246; bugfix on 0.2.4.10-alpha.
1240 o Minor bugfixes (logging):
1241 - Fix a misformatted log message about delayed directory fetches.
1242 Fixes bug 11654; bugfix on 0.2.5.3-alpha.
1243 - Squelch a spurious LD_BUG message "No origin circuit for
1244 successful SOCKS stream" in certain hidden service failure cases;
1248 - Include a tor.service file in contrib/dist for use with systemd.
1249 Some distributions will be able to use this file unmodified;
1250 others will need to tweak it, or write their own. Patch from Jamie
1251 Nguyen; resolves ticket 8368.
1254 - Clean up several option names in the manpage to match their real
1255 names, add the missing documentation for a couple of testing and
1256 directory authority options, remove the documentation for a
1257 V2-directory fetching option that no longer exists. Resolves
1259 - Correct the documenation so that it lists the correct directory
1260 for the stats files. (They are in a subdirectory called "stats",
1262 - In the manpage, move more authority-only options into the
1263 directory authority section so that operators of regular directory
1264 caches don't get confused.
1267 - The contrib directory has been sorted and tidied. Before, it was
1268 an unsorted dumping ground for useful and not-so-useful things.
1269 Now, it is divided based on functionality, and the items which
1270 seemed to be nonfunctional or useless have been removed. Resolves
1271 ticket 8966; based on patches from "rl1987".
1274 - Remove /tor/dbg-stability.txt URL that was meant to help debug WFU
1275 and MTBF calculations, but that nobody was using. Fixes #11742.
1276 - The TunnelDirConns and PreferTunnelledDirConns options no longer
1277 exist; tunneled directory connections have been available since
1278 0.1.2.5-alpha, and turning them off is not a good idea. This is a
1279 brute-force fix for 10849, where "TunnelDirConns 0" would break
1283 Changes in version 0.2.4.22 - 2014-05-16
1284 Tor 0.2.4.22 backports numerous high-priority fixes from the Tor 0.2.5
1285 alpha release series. These include blocking all authority signing
1286 keys that may have been affected by the OpenSSL "heartbleed" bug,
1287 choosing a far more secure set of TLS ciphersuites by default, closing
1288 a couple of memory leaks that could be used to run a target relay out
1289 of RAM, and several others.
1291 o Major features (security, backport from 0.2.5.4-alpha):
1292 - Block authority signing keys that were used on authorities
1293 vulnerable to the "heartbleed" bug in OpenSSL (CVE-2014-0160). (We
1294 don't have any evidence that these keys _were_ compromised; we're
1295 doing this to be prudent.) Resolves ticket 11464.
1297 o Major bugfixes (security, OOM):
1298 - Fix a memory leak that could occur if a microdescriptor parse
1299 fails during the tokenizing step. This bug could enable a memory
1300 exhaustion attack by directory servers. Fixes bug 11649; bugfix
1303 o Major bugfixes (TLS cipher selection, backport from 0.2.5.4-alpha):
1304 - The relay ciphersuite list is now generated automatically based on
1305 uniform criteria, and includes all OpenSSL ciphersuites with
1306 acceptable strength and forward secrecy. Previously, we had left
1307 some perfectly fine ciphersuites unsupported due to omission or
1308 typo. Resolves bugs 11513, 11492, 11498, 11499. Bugs reported by
1309 'cypherpunks'. Bugfix on 0.2.4.8-alpha.
1310 - Relays now trust themselves to have a better view than clients of
1311 which TLS ciphersuites are better than others. (Thanks to bug
1312 11513, the relay list is now well-considered, whereas the client
1313 list has been chosen mainly for anti-fingerprinting purposes.)
1314 Relays prefer: AES over 3DES; then ECDHE over DHE; then GCM over
1315 CBC; then SHA384 over SHA256 over SHA1; and last, AES256 over
1316 AES128. Resolves ticket 11528.
1317 - Clients now try to advertise the same list of ciphersuites as
1318 Firefox 28. This change enables selection of (fast) GCM
1319 ciphersuites, disables some strange old ciphers, and stops
1320 advertising the ECDH (not to be confused with ECDHE) ciphersuites.
1321 Resolves ticket 11438.
1323 o Minor bugfixes (configuration, security):
1324 - When running a hidden service, do not allow TunneledDirConns 0:
1325 trying to set that option together with a hidden service would
1326 otherwise prevent the hidden service from running, and also make
1327 it publish its descriptors directly over HTTP. Fixes bug 10849;
1328 bugfix on 0.2.1.1-alpha.
1330 o Minor bugfixes (controller, backport from 0.2.5.4-alpha):
1331 - Avoid sending a garbage value to the controller when a circuit is
1332 cannibalized. Fixes bug 11519; bugfix on 0.2.3.11-alpha.
1334 o Minor bugfixes (exit relay, backport from 0.2.5.4-alpha):
1335 - Stop leaking memory when we successfully resolve a PTR record.
1336 Fixes bug 11437; bugfix on 0.2.4.7-alpha.
1338 o Minor bugfixes (bridge client, backport from 0.2.5.4-alpha):
1339 - Avoid 60-second delays in the bootstrapping process when Tor is
1340 launching for a second time while using bridges. Fixes bug 9229;
1341 bugfix on 0.2.0.3-alpha.
1343 o Minor bugfixes (relays and bridges, backport from 0.2.5.4-alpha):
1344 - Give the correct URL in the warning message when trying to run a
1345 relay on an ancient version of Windows. Fixes bug 9393.
1347 o Minor bugfixes (compilation):
1348 - Fix a compilation error when compiling with --disable-curve25519.
1349 Fixes bug 9700; bugfix on 0.2.4.17-rc.
1352 - Downgrade the warning severity for the the "md was still
1353 referenced 1 node(s)" warning. Tor 0.2.5.4-alpha has better code
1354 for trying to diagnose this bug, and the current warning in
1355 earlier versions of tor achieves nothing useful. Addresses warning
1358 o Minor features (log verbosity, backport from 0.2.5.4-alpha):
1359 - When we run out of usable circuit IDs on a channel, log only one
1360 warning for the whole channel, and describe how many circuits
1361 there were on the channel. Fixes part of ticket 11553.
1363 o Minor features (security, backport from 0.2.5.4-alpha):
1364 - Decrease the lower limit of MaxMemInCellQueues to 256 MBytes (but
1365 leave the default at 8GBytes), to better support Raspberry Pi
1366 users. Fixes bug 9686; bugfix on 0.2.4.14-alpha.
1368 o Documentation (backport from 0.2.5.4-alpha):
1369 - Correctly document that we search for a system torrc file before
1370 looking in ~/.torrc. Fixes documentation side of 9213; bugfix on
1374 Changes in version 0.2.5.4-alpha - 2014-04-25
1375 Tor 0.2.5.4-alpha includes several security and performance
1376 improvements for clients and relays, including blacklisting authority
1377 signing keys that were used while susceptible to the OpenSSL
1378 "heartbleed" bug, fixing two expensive functions on busy relays,
1379 improved TLS ciphersuite preference lists, support for run-time
1380 hardening on compilers that support AddressSanitizer, and more work on
1381 the Linux sandbox code.
1383 There are also several usability fixes for clients (especially clients
1384 that use bridges), two new TransPort protocols supported (one on
1385 OpenBSD, one on FreeBSD), and various other bugfixes.
1387 This release marks end-of-life for Tor 0.2.2.x; those Tor versions
1388 have accumulated many known flaws; everyone should upgrade.
1390 o Major features (security):
1391 - If you don't specify MaxMemInQueues yourself, Tor now tries to
1392 pick a good value based on your total system memory. Previously,
1393 the default was always 8 GB. You can still override the default by
1394 setting MaxMemInQueues yourself. Resolves ticket 11396.
1395 - Block authority signing keys that were used on authorities
1396 vulnerable to the "heartbleed" bug in OpenSSL (CVE-2014-0160). (We
1397 don't have any evidence that these keys _were_ compromised; we're
1398 doing this to be prudent.) Resolves ticket 11464.
1400 o Major features (relay performance):
1401 - Speed up server-side lookups of rendezvous and introduction point
1402 circuits by using hashtables instead of linear searches. These
1403 functions previously accounted between 3 and 7% of CPU usage on
1404 some busy relays. Resolves ticket 9841.
1405 - Avoid wasting CPU when extending a circuit over a channel that is
1406 nearly out of circuit IDs. Previously, we would do a linear scan
1407 over possible circuit IDs before finding one or deciding that we
1408 had exhausted our possibilities. Now, we try at most 64 random
1409 circuit IDs before deciding that we probably won't succeed. Fixes
1410 a possible root cause of ticket 11553.
1412 o Major features (seccomp2 sandbox, Linux only):
1413 - The seccomp2 sandbox can now run a test network for multiple hours
1414 without crashing. The sandbox is still experimental, and more bugs
1415 will probably turn up. To try it, enable "Sandbox 1" on a Linux
1416 host. Resolves ticket 11351.
1417 - Strengthen sandbox code: the sandbox can now test the arguments
1418 for rename(), and blocks _sysctl() entirely. Resolves another part
1420 - When the sandbox blocks a system call, it now tries to log a stack
1421 trace before exiting. Resolves ticket 11465.
1423 o Major bugfixes (TLS cipher selection):
1424 - The relay ciphersuite list is now generated automatically based on
1425 uniform criteria, and includes all OpenSSL ciphersuites with
1426 acceptable strength and forward secrecy. Previously, we had left
1427 some perfectly fine ciphersuites unsupported due to omission or
1428 typo. Resolves bugs 11513, 11492, 11498, 11499. Bugs reported by
1429 'cypherpunks'. Bugfix on 0.2.4.8-alpha.
1430 - Relays now trust themselves to have a better view than clients of
1431 which TLS ciphersuites are better than others. (Thanks to bug
1432 11513, the relay list is now well-considered, whereas the client
1433 list has been chosen mainly for anti-fingerprinting purposes.)
1434 Relays prefer: AES over 3DES; then ECDHE over DHE; then GCM over
1435 CBC; then SHA384 over SHA256 over SHA1; and last, AES256 over
1436 AES128. Resolves ticket 11528.
1437 - Clients now try to advertise the same list of ciphersuites as
1438 Firefox 28. This change enables selection of (fast) GCM
1439 ciphersuites, disables some strange old ciphers, and stops
1440 advertising the ECDH (not to be confused with ECDHE) ciphersuites.
1441 Resolves ticket 11438.
1443 o Major bugfixes (bridge client):
1444 - Avoid 60-second delays in the bootstrapping process when Tor is
1445 launching for a second time while using bridges. Fixes bug 9229;
1446 bugfix on 0.2.0.3-alpha.
1448 o Minor features (transparent proxy, *BSD):
1449 - Support FreeBSD's ipfw firewall interface for TransPort ports on
1450 FreeBSD. To enable it, set "TransProxyType ipfw". Resolves ticket
1451 10267; patch from "yurivict".
1452 - Support OpenBSD's divert-to rules with the pf firewall for
1453 transparent proxy ports. To enable it, set "TransProxyType
1454 pf-divert". This allows Tor to run a TransPort transparent proxy
1455 port on OpenBSD 4.4 or later without root privileges. See the
1456 pf.conf(5) manual page for information on configuring pf to use
1457 divert-to rules. Closes ticket 10896; patch from Dana Koch.
1459 o Minor features (security):
1460 - New --enable-expensive-hardening option to enable security
1461 hardening options that consume nontrivial amounts of CPU and
1462 memory. Right now, this includes AddressSanitizer and UbSan, which
1463 are supported in newer versions of GCC and Clang. Closes ticket
1466 o Minor features (log verbosity):
1467 - Demote the message that we give when a flushing connection times
1468 out for too long from NOTICE to INFO. It was usually meaningless.
1469 Resolves ticket 5286.
1470 - Don't log so many notice-level bootstrapping messages at startup
1471 about downloading descriptors. Previously, we'd log a notice
1472 whenever we learned about more routers. Now, we only log a notice
1473 at every 5% of progress. Fixes bug 9963.
1474 - Warn less verbosely when receiving a malformed
1475 ESTABLISH_RENDEZVOUS cell. Fixes ticket 11279.
1476 - When we run out of usable circuit IDs on a channel, log only one
1477 warning for the whole channel, and describe how many circuits
1478 there were on the channel. Fixes part of ticket 11553.
1480 o Minor features (relay):
1481 - If a circuit timed out for at least 3 minutes, check if we have a
1482 new external IP address, and publish a new descriptor with the new
1483 IP address if it changed. Resolves ticket 2454.
1485 o Minor features (controller):
1486 - Make the entire exit policy available from the control port via
1487 GETINFO exit-policy/*. Implements enhancement 7952. Patch from
1489 - Because of the fix for ticket 11396, the real limit for memory
1490 usage may no longer match the configured MaxMemInQueues value. The
1491 real limit is now exposed via GETINFO limits/max-mem-in-queues.
1493 o Minor features (bridge client):
1494 - Report a more useful failure message when we can't connect to a
1495 bridge because we don't have the right pluggable transport
1496 configured. Resolves ticket 9665. Patch from Fábio J. Bertinatto.
1498 o Minor features (diagnostic):
1499 - Add more log messages to diagnose bug 7164, which causes
1500 intermittent "microdesc_free() called but md was still referenced"
1501 warnings. We now include more information, to figure out why we
1502 might be cleaning a microdescriptor for being too old if it's
1503 still referenced by a live node_t object.
1505 o Minor bugfixes (client, DNSPort):
1506 - When using DNSPort, try to respond to AAAA requests with AAAA
1507 answers. Previously, we hadn't looked at the request type when
1508 deciding which answer type to prefer. Fixes bug 10468; bugfix on
1510 - When receiving a DNS query for an unsupported record type, reply
1511 with no answer rather than with a NOTIMPL error. This behavior
1512 isn't correct either, but it will break fewer client programs, we
1513 hope. Fixes bug 10268; bugfix on 0.2.0.1-alpha. Original patch
1516 o Minor bugfixes (exit relay):
1517 - Stop leaking memory when we successfully resolve a PTR record.
1518 Fixes bug 11437; bugfix on 0.2.4.7-alpha.
1520 o Minor bugfixes (bridge client):
1521 - Stop accepting bridge lines containing hostnames. Doing so would
1522 cause clients to perform DNS requests on the hostnames, which was
1523 not sensible behavior. Fixes bug 10801; bugfix on 0.2.0.1-alpha.
1524 - Avoid a 60-second delay in the bootstrapping process when a Tor
1525 client with pluggable transports re-reads its configuration at
1526 just the wrong time. Re-fixes bug 11156; bugfix on 0.2.5.3-alpha.
1528 o Minor bugfixes (client, logging during bootstrap):
1529 - Warn only once if we start logging in an unsafe way. Previously,
1530 we complain as many times as we had problems. Fixes bug 9870;
1531 bugfix on 0.2.5.1-alpha.
1532 - Only report the first fatal bootstrap error on a given OR
1533 connection. This stops us from telling the controller bogus error
1534 messages like "DONE". Fixes bug 10431; bugfix on 0.2.1.1-alpha.
1535 - Be more helpful when trying to run sandboxed on Linux without
1536 libseccomp. Instead of saying "Sandbox is not implemented on this
1537 platform", we now explain that we need to be built with
1538 libseccomp. Fixes bug 11543; bugfix on 0.2.5.1-alpha.
1539 - Avoid generating spurious warnings when starting with
1540 DisableNetwork enabled. Fixes bug 11200 and bug 10405; bugfix on
1543 o Minor bugfixes (closing OR connections):
1544 - If write_to_buf() in connection_write_to_buf_impl_() ever fails,
1545 check if it's an or_connection_t and correctly call
1546 connection_or_close_for_error() rather than
1547 connection_mark_for_close() directly. Fixes bug 11304; bugfix on
1549 - When closing all connections on setting DisableNetwork to 1, use
1550 connection_or_close_normally() rather than closing OR connections
1551 out from under the channel layer. Fixes bug 11306; bugfix on
1554 o Minor bugfixes (controller):
1555 - Avoid sending a garbage value to the controller when a circuit is
1556 cannibalized. Fixes bug 11519; bugfix on 0.2.3.11-alpha.
1558 o Minor bugfixes (tor-fw-helper):
1559 - Allow tor-fw-helper to build again by adding src/ext to its
1560 CPPFLAGS. Fixes bug 11296; bugfix on 0.2.5.3-alpha.
1562 o Minor bugfixes (bridges):
1563 - Avoid potential crashes or bad behavior when launching a
1564 server-side managed proxy with ORPort or ExtORPort temporarily
1565 disabled. Fixes bug 9650; bugfix on 0.2.3.16-alpha.
1567 o Minor bugfixes (platform-specific):
1568 - Fix compilation on Solaris, which does not have <endian.h>. Fixes
1569 bug 11426; bugfix on 0.2.5.3-alpha.
1570 - When dumping a malformed directory object to disk, save it in
1571 binary mode on Windows, not text mode. Fixes bug 11342; bugfix on
1573 - Don't report failures from make_socket_reuseable() on incoming
1574 sockets on OSX: this can happen when incoming connections close
1575 early. Fixes bug 10081.
1577 o Minor bugfixes (trivial memory leaks):
1578 - Fix a small memory leak when signing a directory object. Fixes bug
1579 11275; bugfix on 0.2.4.13-alpha.
1580 - Free placeholder entries in our circuit table at exit; fixes a
1581 harmless memory leak. Fixes bug 11278; bugfix on 0.2.5.1-alpha.
1582 - Don't re-initialize a second set of OpenSSL mutexes when starting
1583 up. Previously, we'd make one set of mutexes, and then immediately
1584 replace them with another. Fixes bug 11726; bugfix on
1586 - Resolve some memory leaks found by coverity in the unit tests, on
1587 exit in tor-gencert, and on a failure to compute digests for our
1588 own keys when generating a v3 networkstatus vote. These leaks
1589 should never have affected anyone in practice.
1591 o Minor bugfixes (hidden service):
1592 - Only retry attempts to connect to a chosen rendezvous point 8
1593 times, not 30. Fixes bug 4241; bugfix on 0.1.0.1-rc.
1595 o Minor bugfixes (misc code correctness):
1596 - Fix various instances of undefined behavior in channeltls.c,
1597 tor_memmem(), and eventdns.c that would cause us to construct
1598 pointers to memory outside an allocated object. (These invalid
1599 pointers were not accessed, but C does not even allow them to
1600 exist.) Fixes bug 10363; bugfixes on 0.1.1.1-alpha, 0.1.2.1-alpha,
1601 0.2.0.10-alpha, and 0.2.3.6-alpha. Reported by "bobnomnom".
1602 - Use the AddressSanitizer and Ubsan sanitizers (in clang-3.4) to
1603 fix some miscellaneous errors in our tests and codebase. Fixes bug
1604 11232. Bugfixes on versions back as far as 0.2.1.11-alpha.
1605 - Always check return values for unlink, munmap, UnmapViewOfFile;
1606 check strftime return values more often. In some cases all we can
1607 do is report a warning, but this may help prevent deeper bugs from
1608 going unnoticed. Closes ticket 8787; bugfixes on many, many tor
1610 - Fix numerous warnings from the clang "scan-build" static analyzer.
1611 Some of these are programming style issues; some of them are false
1612 positives that indicated awkward code; some are undefined behavior
1613 cases related to constructing (but not using) invalid pointers;
1614 some are assumptions about API behavior; some are (harmlessly)
1615 logging sizeof(ptr) bytes from a token when sizeof(*ptr) would be
1616 correct; and one or two are genuine bugs that weren't reachable
1617 from the rest of the program. Fixes bug 8793; bugfixes on many,
1621 - Build the torify.1 manpage again. Previously, we were only trying
1622 to build it when also building tor-fw-helper. That's why we didn't
1623 notice that we'd broken the ability to build it. Fixes bug 11321;
1624 bugfix on 0.2.5.1-alpha.
1625 - Fix the layout of the SOCKSPort flags in the manpage. Fixes bug
1626 11061; bugfix on 0.2.4.7-alpha.
1627 - Correctly document that we search for a system torrc file before
1628 looking in ~/.torrc. Fixes documentation side of 9213; bugfix on
1630 - Resolve warnings from Doxygen.
1632 o Code simplifications and refactoring:
1633 - Remove is_internal_IP() function. Resolves ticket 4645.
1634 - Remove unused function circuit_dump_by_chan from circuitlist.c.
1635 Closes issue 9107; patch from "marek".
1636 - Change our use of the ENUM_BF macro to avoid declarations that
1639 o Deprecated versions:
1640 - Tor 0.2.2.x has reached end-of-life; it has received no patches or
1641 attention for some while. Directory authorities no longer accept
1642 descriptors from relays running any version of Tor prior to Tor
1643 0.2.3.16-alpha. Resolves ticket 11149.
1646 - New macros in test.h to simplify writing mock-functions for unit
1647 tests. Part of ticket 11507. Patch from Dana Koch.
1648 - Complete tests for the status.c module. Resolves ticket 11507.
1649 Patch from Dana Koch.
1652 - Remove all code for the long unused v1 directory protocol.
1653 Resolves ticket 11070.
1656 Changes in version 0.2.5.3-alpha - 2014-03-22
1657 Tor 0.2.5.3-alpha includes all the fixes from 0.2.4.21. It contains
1658 two new anti-DoS features for Tor relays, resolves a bug that kept
1659 SOCKS5 support for IPv6 from working, fixes several annoying usability
1660 issues for bridge users, and removes more old code for unused
1663 The Tor 0.2.5.x release series is now in patch-freeze: no feature
1664 patches not already written will be considered for inclusion in 0.2.5.x.
1666 o Major features (relay security, DoS-resistance):
1667 - When deciding whether we have run out of memory and we need to
1668 close circuits, also consider memory allocated in buffers for
1669 streams attached to each circuit.
1671 This change, which extends an anti-DoS feature introduced in
1672 0.2.4.13-alpha and improved in 0.2.4.14-alpha, lets Tor exit relays
1673 better resist more memory-based DoS attacks than before. Since the
1674 MaxMemInCellQueues option now applies to all queues, it is renamed
1675 to MaxMemInQueues. This feature fixes bug 10169.
1676 - Avoid hash-flooding denial-of-service attacks by using the secure
1677 SipHash-2-4 hash function for our hashtables. Without this
1678 feature, an attacker could degrade performance of a targeted
1679 client or server by flooding their data structures with a large
1680 number of entries to be stored at the same hash table position,
1681 thereby slowing down the Tor instance. With this feature, hash
1682 table positions are derived from a randomized cryptographic key,
1683 and an attacker cannot predict which entries will collide. Closes
1685 - Decrease the lower limit of MaxMemInQueues to 256 MBytes (but leave
1686 the default at 8GBytes), to better support Raspberry Pi users. Fixes
1687 bug 9686; bugfix on 0.2.4.14-alpha.
1689 o Minor features (bridges, pluggable transports):
1690 - Bridges now write the SHA1 digest of their identity key
1691 fingerprint (that is, a hash of a hash of their public key) to
1692 notice-level logs, and to a new hashed-fingerprint file. This
1693 information will help bridge operators look up their bridge in
1694 Globe and similar tools. Resolves ticket 10884.
1695 - Improve the message that Tor displays when running as a bridge
1696 using pluggable transports without an Extended ORPort listener.
1697 Also, log the message in the log file too. Resolves ticket 11043.
1699 o Minor features (other):
1700 - Add a new option, PredictedPortsRelevanceTime, to control how long
1701 after having received a request to connect to a given port Tor
1702 will try to keep circuits ready in anticipation of future requests
1703 for that port. Patch from "unixninja92"; implements ticket 9176.
1704 - Generate a warning if any ports are listed in the SocksPolicy,
1705 DirPolicy, AuthDirReject, AuthDirInvalid, AuthDirBadDir, or
1706 AuthDirBadExit options. (These options only support address
1707 ranges.) Fixes part of ticket 11108.
1708 - Update geoip and geoip6 to the February 7 2014 Maxmind GeoLite2
1711 o Minor bugfixes (new since 0.2.5.2-alpha, also in 0.2.4.21):
1712 - Build without warnings under clang 3.4. (We have some macros that
1713 define static functions only some of which will get used later in
1714 the module. Starting with clang 3.4, these give a warning unless the
1715 unused attribute is set on them.) Resolves ticket 10904.
1716 - Fix build warnings about missing "a2x" comment when building the
1717 manpages from scratch on OpenBSD; OpenBSD calls it "a2x.py".
1718 Fixes bug 10929; bugfix on 0.2.2.9-alpha. Patch from Dana Koch.
1720 o Minor bugfixes (client):
1721 - Improve the log message when we can't connect to a hidden service
1722 because all of the hidden service directory nodes hosting its
1723 descriptor are excluded. Improves on our fix for bug 10722, which
1724 was a bugfix on 0.2.0.10-alpha.
1725 - Raise a control port warning when we fail to connect to all of
1726 our bridges. Previously, we didn't inform the controller, and
1727 the bootstrap process would stall. Fixes bug 11069; bugfix on
1729 - Exit immediately when a process-owning controller exits.
1730 Previously, tor relays would wait for a little while after their
1731 controller exited, as if they had gotten an INT signal -- but this
1732 was problematic, since there was no feedback for the user. To do a
1733 clean shutdown, controllers should send an INT signal and give Tor
1734 a chance to clean up. Fixes bug 10449; bugfix on 0.2.2.28-beta.
1735 - Stop attempting to connect to bridges before our pluggable
1736 transports are configured (harmless but resulted in some erroneous
1737 log messages). Fixes bug 11156; bugfix on 0.2.3.2-alpha.
1738 - Fix connections to IPv6 addresses over SOCKS5. Previously, we were
1739 generating incorrect SOCKS5 responses, and confusing client
1740 applications. Fixes bug 10987; bugfix on 0.2.4.7-alpha.
1742 o Minor bugfixes (relays and bridges):
1743 - Avoid crashing on a malformed resolv.conf file when running a
1744 relay using Libevent 1. Fixes bug 8788; bugfix on 0.1.1.23.
1745 - Non-exit relays no longer launch mock DNS requests to check for
1746 DNS hijacking. This has been unnecessary since 0.2.1.7-alpha, when
1747 non-exit relays stopped servicing DNS requests. Fixes bug 965;
1748 bugfix on 0.2.1.7-alpha. Patch from Matt Pagan.
1749 - Bridges now report complete directory request statistics. Related
1750 to bug 5824; bugfix on 0.2.2.1-alpha.
1751 - Bridges now never collect statistics that were designed for
1752 relays. Fixes bug 5824; bugfix on 0.2.3.8-alpha.
1753 - Stop giving annoying warning messages when we decide not to launch
1754 a pluggable transport proxy that we don't need (because there are
1755 no bridges configured to use it). Resolves ticket 5018; bugfix
1757 - Give the correct URL in the warning message when trying to run a
1758 relay on an ancient version of Windows. Fixes bug 9393.
1760 o Minor bugfixes (backtrace support):
1761 - Support automatic backtraces on more platforms by using the
1762 "-fasynchronous-unwind-tables" compiler option. This option is
1763 needed for platforms like 32-bit Intel where "-fomit-frame-pointer"
1764 is on by default and table generation is not. This doesn't yet
1765 add Windows support; only Linux, OSX, and some BSDs are affected.
1766 Reported by 'cypherpunks'; fixes bug 11047; bugfix on 0.2.5.2-alpha.
1767 - Avoid strange behavior if two threads hit failed assertions at the
1768 same time and both try to log backtraces at once. (Previously, if
1769 this had happened, both threads would have stored their intermediate
1770 results in the same buffer, and generated junk outputs.) Reported by
1771 "cypherpunks". Fixes bug 11048; bugfix on 0.2.5.2-alpha.
1772 - Fix a compiler warning in format_number_sigsafe(). Bugfix on
1773 0.2.5.2-alpha; patch from Nick Hopper.
1775 o Minor bugfixes (unit tests):
1776 - Fix a small bug in the unit tests that might have made the tests
1777 call 'chmod' with an uninitialized bitmask. Fixes bug 10928;
1778 bugfix on 0.2.5.1-alpha. Patch from Dana Koch.
1781 - Remove all remaining code related to version-0 hidden service
1782 descriptors: they have not been in use since 0.2.2.1-alpha. Fixes
1783 the rest of bug 10841.
1786 - Document in the manpage that "KBytes" may also be written as
1787 "kilobytes" or "KB", that "Kbits" may also be written as
1788 "kilobits", and so forth. Closes ticket 9222.
1789 - Document that the ClientOnly config option overrides ORPort.
1790 Our old explanation made ClientOnly sound as though it did
1791 nothing at all. Resolves bug 9059.
1792 - Explain that SocksPolicy, DirPolicy, and similar options don't
1793 take port arguments. Fixes the other part of ticket 11108.
1794 - Fix a comment about the rend_server_descriptor_t.protocols field
1795 to more accurately describe its range. Also, make that field
1796 unsigned, to more accurately reflect its usage. Fixes bug 9099;
1797 bugfix on 0.2.1.5-alpha.
1798 - Fix the manpage's description of HiddenServiceAuthorizeClient:
1799 the maximum client name length is 16, not 19. Fixes bug 11118;
1800 bugfix on 0.2.1.6-alpha.
1802 o Code simplifications and refactoring:
1803 - Get rid of router->address, since in all cases it was just the
1804 string representation of router->addr. Resolves ticket 5528.
1806 o Test infrastructure:
1807 - Update to the latest version of tinytest.
1808 - Improve the tinytest implementation of string operation tests so
1809 that comparisons with NULL strings no longer crash the tests; they
1810 now just fail, normally. Fixes bug 9004; bugfix on 0.2.2.4-alpha.
1813 Changes in version 0.2.4.21 - 2014-02-28
1814 Tor 0.2.4.21 further improves security against potential adversaries who
1815 find breaking 1024-bit crypto doable, and backports several stability
1816 and robustness patches from the 0.2.5 branch.
1818 o Major features (client security):
1819 - When we choose a path for a 3-hop circuit, make sure it contains
1820 at least one relay that supports the NTor circuit extension
1821 handshake. Otherwise, there is a chance that we're building
1822 a circuit that's worth attacking by an adversary who finds
1823 breaking 1024-bit crypto doable, and that chance changes the game
1824 theory. Implements ticket 9777.
1827 - Do not treat streams that fail with reason
1828 END_STREAM_REASON_INTERNAL as indicating a definite circuit failure,
1829 since it could also indicate an ENETUNREACH connection error. Fixes
1830 part of bug 10777; bugfix on 0.2.4.8-alpha.
1832 o Code simplification and refactoring:
1833 - Remove data structures which were introduced to implement the
1834 CellStatistics option: they are now redundant with the new timestamp
1835 field in the regular packed_cell_t data structure, which we did
1836 in 0.2.4.18-rc in order to resolve bug 9093. Resolves ticket 10870.
1839 - Always clear OpenSSL bignums before freeing them -- even bignums
1840 that don't contain secrets. Resolves ticket 10793. Patch by
1842 - Build without warnings under clang 3.4. (We have some macros that
1843 define static functions only some of which will get used later in
1844 the module. Starting with clang 3.4, these give a warning unless the
1845 unused attribute is set on them.) Resolves ticket 10904.
1846 - Update geoip and geoip6 files to the February 7 2014 Maxmind
1847 GeoLite2 Country database.
1850 - Set the listen() backlog limit to the largest actually supported
1851 on the system, not to the value in a header file. Fixes bug 9716;
1852 bugfix on every released Tor.
1853 - Treat ENETUNREACH, EACCES, and EPERM connection failures at an
1854 exit node as a NOROUTE error, not an INTERNAL error, since they
1855 can apparently happen when trying to connect to the wrong sort
1856 of netblocks. Fixes part of bug 10777; bugfix on 0.1.0.1-rc.
1857 - Fix build warnings about missing "a2x" comment when building the
1858 manpages from scratch on OpenBSD; OpenBSD calls it "a2x.py".
1859 Fixes bug 10929; bugfix on 0.2.2.9-alpha. Patch from Dana Koch.
1860 - Avoid a segfault on SIGUSR1, where we had freed a connection but did
1861 not entirely remove it from the connection lists. Fixes bug 9602;
1862 bugfix on 0.2.4.4-alpha.
1863 - Fix a segmentation fault in our benchmark code when running with
1864 Fedora's OpenSSL package, or any other OpenSSL that provides
1865 ECDH but not P224. Fixes bug 10835; bugfix on 0.2.4.8-alpha.
1866 - Turn "circuit handshake stats since last time" log messages into a
1867 heartbeat message. Fixes bug 10485; bugfix on 0.2.4.17-rc.
1869 o Documentation fixes:
1870 - Document that all but one DirPort entry must have the NoAdvertise
1871 flag set. Fixes bug 10470; bugfix on 0.2.3.3-alpha / 0.2.3.16-alpha.
1874 Changes in version 0.2.5.2-alpha - 2014-02-13
1875 Tor 0.2.5.2-alpha includes all the fixes from 0.2.4.18-rc and 0.2.4.20,
1876 like the "poor random number generation" fix and the "building too many
1877 circuits" fix. It also further improves security against potential
1878 adversaries who find breaking 1024-bit crypto doable, and launches
1879 pluggable transports on demand (which gets us closer to integrating
1880 pluggable transport support by default -- not to be confused with Tor
1881 bundles enabling pluggable transports and bridges by default).
1883 o Major features (client security):
1884 - When we choose a path for a 3-hop circuit, make sure it contains
1885 at least one relay that supports the NTor circuit extension
1886 handshake. Otherwise, there is a chance that we're building
1887 a circuit that's worth attacking by an adversary who finds
1888 breaking 1024-bit crypto doable, and that chance changes the game
1889 theory. Implements ticket 9777.
1890 - Clients now look at the "usecreatefast" consensus parameter to
1891 decide whether to use CREATE_FAST or CREATE cells for the first hop
1892 of their circuit. This approach can improve security on connections
1893 where Tor's circuit handshake is stronger than the available TLS
1894 connection security levels, but the tradeoff is more computational
1895 load on guard relays. Implements proposal 221. Resolves ticket 9386.
1897 o Major features (bridges):
1898 - Don't launch pluggable transport proxies if we don't have any
1899 bridges configured that would use them. Now we can list many
1900 pluggable transports, and Tor will dynamically start one when it
1901 hears a bridge address that needs it. Resolves ticket 5018.
1902 - The bridge directory authority now assigns status flags (Stable,
1903 Guard, etc) to bridges based on thresholds calculated over all
1904 Running bridges. Now bridgedb can finally make use of its features
1905 to e.g. include at least one Stable bridge in its answers. Fixes
1908 o Major features (other):
1909 - Extend ORCONN controller event to include an "ID" parameter,
1910 and add four new controller event types CONN_BW, CIRC_BW,
1911 CELL_STATS, and TB_EMPTY that show connection and circuit usage.
1912 The new events are emitted in private Tor networks only, with the
1913 goal of being able to better track performance and load during
1914 full-network simulations. Implements proposal 218 and ticket 7359.
1915 - On some platforms (currently: recent OSX versions, glibc-based
1916 platforms that support the ELF format, and a few other
1917 Unix-like operating systems), Tor can now dump stack traces
1918 when a crash occurs or an assertion fails. By default, traces
1919 are dumped to stderr (if possible) and to any logs that are
1920 reporting errors. Implements ticket 9299.
1923 - Avoid a segfault on SIGUSR1, where we had freed a connection but did
1924 not entirely remove it from the connection lists. Fixes bug 9602;
1925 bugfix on 0.2.4.4-alpha.
1926 - Do not treat streams that fail with reason
1927 END_STREAM_REASON_INTERNAL as indicating a definite circuit failure,
1928 since it could also indicate an ENETUNREACH connection error. Fixes
1929 part of bug 10777; bugfix on 0.2.4.8-alpha.
1931 o Major bugfixes (new since 0.2.5.1-alpha, also in 0.2.4.20):
1932 - Do not allow OpenSSL engines to replace the PRNG, even when
1933 HardwareAccel is set. The only default builtin PRNG engine uses
1934 the Intel RDRAND instruction to replace the entire PRNG, and
1935 ignores all attempts to seed it with more entropy. That's
1936 cryptographically stupid: the right response to a new alleged
1937 entropy source is never to discard all previously used entropy
1938 sources. Fixes bug 10402; works around behavior introduced in
1939 OpenSSL 1.0.0. Diagnosis and investigation thanks to "coderman"
1941 - Fix assertion failure when AutomapHostsOnResolve yields an IPv6
1942 address. Fixes bug 10465; bugfix on 0.2.4.7-alpha.
1943 - Avoid launching spurious extra circuits when a stream is pending.
1944 This fixes a bug where any circuit that _wasn't_ unusable for new
1945 streams would be treated as if it were, causing extra circuits to
1946 be launched. Fixes bug 10456; bugfix on 0.2.4.12-alpha.
1948 o Major bugfixes (new since 0.2.5.1-alpha, also in 0.2.4.18-rc):
1949 - No longer stop reading or writing on cpuworker connections when
1950 our rate limiting buckets go empty. Now we should handle circuit
1951 handshake requests more promptly. Resolves bug 9731.
1952 - Stop trying to bootstrap all our directory information from
1953 only our first guard. Discovered while fixing bug 9946; bugfix
1956 o Minor features (bridges, pluggable transports):
1957 - Add threshold cutoffs to the networkstatus document created by
1958 the Bridge Authority. Fixes bug 1117.
1959 - On Windows, spawn background processes using the CREATE_NO_WINDOW
1960 flag. Now Tor Browser Bundle 3.5 with pluggable transports enabled
1961 doesn't pop up a blank console window. (In Tor Browser Bundle 2.x,
1962 Vidalia set this option for us.) Implements ticket 10297.
1964 o Minor features (security):
1965 - Always clear OpenSSL bignums before freeing them -- even bignums
1966 that don't contain secrets. Resolves ticket 10793. Patch by
1969 o Minor features (config options and command line):
1970 - Add an --allow-missing-torrc commandline option that tells Tor to
1971 run even if the configuration file specified by -f is not available.
1972 Implements ticket 10060.
1973 - Add support for the TPROXY transparent proxying facility on Linux.
1974 See documentation for the new TransProxyType option for more
1975 details. Implementation by "thomo". Closes ticket 10582.
1977 o Minor features (controller):
1978 - Add a new "HS_DESC" controller event that reports activities
1979 related to hidden service descriptors. Resolves ticket 8510.
1980 - New "DROPGUARDS" controller command to forget all current entry
1981 guards. Not recommended for ordinary use, since replacing guards
1982 too frequently makes several attacks easier. Resolves ticket 9934;
1985 o Minor features (build):
1986 - Assume that a user using ./configure --host wants to cross-compile,
1987 and give an error if we cannot find a properly named
1988 tool-chain. Add a --disable-tool-name-check option to proceed
1989 nevertheless. Addresses ticket 9869. Patch by Benedikt Gollatz.
1990 - If we run ./configure and the compiler recognizes -fstack-protector
1991 but the linker rejects it, warn the user about a potentially missing
1992 libssp package. Addresses ticket 9948. Patch from Benedikt Gollatz.
1994 o Minor features (testing):
1995 - If Python is installed, "make check" now runs extra tests beyond
1996 the unit test scripts.
1997 - When bootstrapping a test network, sometimes very few relays get
1998 the Guard flag. Now a new option "TestingDirAuthVoteGuard" can
1999 specify a set of relays which should be voted Guard regardless of
2000 their uptime or bandwidth. Addresses ticket 9206.
2002 o Minor features (log messages):
2003 - When ServerTransportPlugin is set on a bridge, Tor can write more
2004 useful statistics about bridge use in its extrainfo descriptors,
2005 but only if the Extended ORPort ("ExtORPort") is set too. Add a
2006 log message to inform the user in this case. Resolves ticket 9651.
2007 - When receiving a new controller connection, log the origin address.
2008 Resolves ticket 9698; patch from "sigpipe".
2009 - When logging OpenSSL engine status at startup, log the status of
2010 more engines. Fixes ticket 10043; patch from Joshua Datko.
2011 - Turn "circuit handshake stats since last time" log messages into a
2012 heartbeat message. Fixes bug 10485; bugfix on 0.2.4.17-rc.
2014 o Minor features (new since 0.2.5.1-alpha, also in 0.2.4.18-rc):
2015 - Improve the circuit queue out-of-memory handler. Previously, when
2016 we ran low on memory, we'd close whichever circuits had the most
2017 queued cells. Now, we close those that have the *oldest* queued
2018 cells, on the theory that those are most responsible for us
2019 running low on memory. Based on analysis from a forthcoming paper
2020 by Jansen, Tschorsch, Johnson, and Scheuermann. Fixes bug 9093.
2021 - Generate bootstrapping status update events correctly when fetching
2022 microdescriptors. Fixes bug 9927.
2023 - Update to the October 2 2013 Maxmind GeoLite Country database.
2025 o Minor bugfixes (clients):
2026 - When closing a channel that has already been open, do not close
2027 pending circuits that were waiting to connect to the same relay.
2028 Fixes bug 9880; bugfix on 0.2.5.1-alpha. Thanks to skruffy for
2031 o Minor bugfixes (relays):
2032 - Treat ENETUNREACH, EACCES, and EPERM connection failures at an
2033 exit node as a NOROUTE error, not an INTERNAL error, since they
2034 can apparently happen when trying to connect to the wrong sort
2035 of netblocks. Fixes part of bug 10777; bugfix on 0.1.0.1-rc.
2037 o Minor bugfixes (bridges):
2038 - Fix a bug where the first connection works to a bridge that uses a
2039 pluggable transport with client-side parameters, but we don't send
2040 the client-side parameters on subsequent connections. (We don't
2041 use any pluggable transports with client-side parameters yet,
2042 but ScrambleSuit will soon become the first one.) Fixes bug 9162;
2043 bugfix on 0.2.0.3-alpha. Based on a patch from "rl1987".
2045 o Minor bugfixes (node selection):
2046 - If ExcludeNodes is set, consider non-excluded hidden service
2047 directory servers before excluded ones. Do not consider excluded
2048 hidden service directory servers at all if StrictNodes is
2049 set. (Previously, we would sometimes decide to connect to those
2050 servers, and then realize before we initiated a connection that
2051 we had excluded them.) Fixes bug 10722; bugfix on 0.2.0.10-alpha.
2053 - If we set the ExitNodes option but it doesn't include any nodes
2054 that have the Exit flag, we would choose not to bootstrap. Now we
2055 bootstrap so long as ExitNodes includes nodes which can exit to
2056 some port. Fixes bug 10543; bugfix on 0.2.4.10-alpha.
2058 o Minor bugfixes (controller and command-line):
2059 - If changing a config option via "setconf" fails in a recoverable
2060 way, we used to nonetheless write our new control ports to the
2061 file described by the "ControlPortWriteToFile" option. Now we only
2062 write out that file if we successfully switch to the new config
2063 option. Fixes bug 5605; bugfix on 0.2.2.26-beta. Patch from "Ryman".
2064 - When a command-line option such as --version or --help that
2065 ordinarily implies --hush appears on the command line along with
2066 --quiet, then actually obey --quiet. Previously, we obeyed --quiet
2067 only if it appeared later on the command line. Fixes bug 9578;
2068 bugfix on 0.2.5.1-alpha.
2070 o Minor bugfixes (code correctness):
2071 - Previously we used two temporary files when writing descriptors to
2072 disk; now we only use one. Fixes bug 1376.
2073 - Remove an erroneous (but impossible and thus harmless) pointer
2074 comparison that would have allowed compilers to skip a bounds
2075 check in channeltls.c. Fixes bugs 10313 and 9980; bugfix on
2076 0.2.0.10-alpha. Noticed by Jared L Wong and David Fifield.
2077 - Fix an always-true assertion in pluggable transports code so it
2078 actually checks what it was trying to check. Fixes bug 10046;
2079 bugfix on 0.2.3.9-alpha. Found by "dcb".
2081 o Minor bugfixes (protocol correctness):
2082 - When receiving a VERSIONS cell with an odd number of bytes, close
2083 the connection immediately since the cell is malformed. Fixes bug
2084 10365; bugfix on 0.2.0.10-alpha. Spotted by "bobnomnom"; fix by
2087 o Minor bugfixes (build):
2088 - Restore the ability to compile Tor with V2_HANDSHAKE_SERVER
2089 turned off (that is, without support for v2 link handshakes). Fixes
2090 bug 4677; bugfix on 0.2.3.2-alpha. Patch from "piet".
2091 - Fix compilation warnings and startup issues when running with
2092 "Sandbox 1" and libseccomp-2.1.0. Fixes bug 10563; bugfix on
2094 - Fix compilation on Solaris 9, which didn't like us having an
2095 identifier named "sun". Fixes bug 10565; bugfix in 0.2.5.1-alpha.
2097 o Minor bugfixes (testing):
2098 - Fix a segmentation fault in our benchmark code when running with
2099 Fedora's OpenSSL package, or any other OpenSSL that provides
2100 ECDH but not P224. Fixes bug 10835; bugfix on 0.2.4.8-alpha.
2102 o Minor bugfixes (log messages):
2103 - Fix a bug where clients using bridges would report themselves
2104 as 50% bootstrapped even without a live consensus document.
2105 Fixes bug 9922; bugfix on 0.2.1.1-alpha.
2106 - Suppress a warning where, if there's only one directory authority
2107 in the network, we would complain that votes and signatures cannot
2108 be uploaded to other directory authorities. Fixes bug 10842;
2109 bugfix on 0.2.2.26-beta.
2110 - Report bootstrapping progress correctly when we're downloading
2111 microdescriptors. We had updated our "do we have enough microdescs
2112 to begin building circuits?" logic most recently in 0.2.4.10-alpha
2113 (see bug 5956), but we left the bootstrap status event logic at
2114 "how far through getting 1/4 of them are we?" Fixes bug 9958;
2115 bugfix on 0.2.2.36, which is where they diverged (see bug 5343).
2117 o Minor bugfixes (new since 0.2.5.1-alpha, also in 0.2.4.20):
2118 - Avoid a crash bug when starting with a corrupted microdescriptor
2119 cache file. Fixes bug 10406; bugfix on 0.2.2.6-alpha.
2120 - If we fail to dump a previously cached microdescriptor to disk, avoid
2121 freeing duplicate data later on. Fixes bug 10423; bugfix on
2122 0.2.4.13-alpha. Spotted by "bobnomnom".
2124 o Minor bugfixes on 0.2.4.x (new since 0.2.5.1-alpha, also in 0.2.4.18-rc):
2125 - Correctly log long IPv6 exit policies, instead of truncating them
2126 or reporting an error. Fixes bug 9596; bugfix on 0.2.4.7-alpha.
2127 - Our default TLS ecdhe groups were backwards: we meant to be using
2128 P224 for relays (for performance win) and P256 for bridges (since
2129 it is more common in the wild). Instead we had it backwards. After
2130 reconsideration, we decided that the default should be P256 on all
2131 hosts, since its security is probably better, and since P224 is
2132 reportedly used quite little in the wild. Found by "skruffy" on
2133 IRC. Fix for bug 9780; bugfix on 0.2.4.8-alpha.
2134 - Free directory authority certificate download statuses on exit
2135 rather than leaking them. Fixes bug 9644; bugfix on 0.2.4.13-alpha.
2137 o Minor bugfixes on 0.2.3.x (new since 0.2.5.1-alpha, also in 0.2.4.18-rc):
2138 - If the guard we choose first doesn't answer, we would try the
2139 second guard, but once we connected to the second guard we would
2140 abandon it and retry the first one, slowing down bootstrapping.
2141 The fix is to treat all our initially chosen guards as acceptable
2142 to use. Fixes bug 9946; bugfix on 0.1.1.11-alpha.
2143 - Fix an assertion failure that would occur when disabling the
2144 ORPort setting on a running Tor process while accounting was
2145 enabled. Fixes bug 6979; bugfix on 0.2.2.18-alpha.
2146 - When examining the list of network interfaces to find our address,
2147 do not consider non-running or disabled network interfaces. Fixes
2148 bug 9904; bugfix on 0.2.3.11-alpha. Patch from "hantwister".
2149 - Avoid an off-by-one error when checking buffer boundaries when
2150 formatting the exit status of a pluggable transport helper.
2151 This is probably not an exploitable bug, but better safe than
2152 sorry. Fixes bug 9928; bugfix on 0.2.3.18-rc. Bug found by
2155 o Removed code and features:
2156 - Clients now reject any directory authority certificates lacking
2157 a dir-key-crosscert element. These have been included since
2158 0.2.1.9-alpha, so there's no real reason for them to be optional
2159 any longer. Completes proposal 157. Resolves ticket 10162.
2160 - Remove all code that existed to support the v2 directory system,
2161 since there are no longer any v2 directory authorities. Resolves
2163 - Remove the HSAuthoritativeDir and AlternateHSAuthority torrc
2164 options, which were used for designating authorities as "Hidden
2165 service authorities". There has been no use of hidden service
2166 authorities since 0.2.2.1-alpha, when we stopped uploading or
2167 downloading v0 hidden service descriptors. Fixes bug 10881; also
2168 part of a fix for bug 10841.
2170 o Code simplification and refactoring:
2171 - Remove some old fallback code designed to keep Tor clients working
2172 in a network with only two working relays. Elsewhere in the code we
2173 have long since stopped supporting such networks, so there wasn't
2174 much point in keeping it around. Addresses ticket 9926.
2175 - Reject 0-length EXTEND2 cells more explicitly. Fixes bug 10536;
2176 bugfix on 0.2.4.8-alpha. Reported by "cypherpunks".
2177 - Remove data structures which were introduced to implement the
2178 CellStatistics option: they are now redundant with the addition
2179 of a timestamp to the regular packed_cell_t data structure, which
2180 we did in 0.2.4.18-rc in order to resolve ticket 9093. Implements
2183 o Documentation (man page) fixes:
2184 - Update manpage to describe some of the files you can expect to
2185 find in Tor's DataDirectory. Addresses ticket 9839.
2186 - Document that all but one DirPort entry must have the NoAdvertise
2187 flag set. Fixes bug 10470; bugfix on 0.2.3.3-alpha / 0.2.3.16-alpha.
2189 o Documentation fixes (new since 0.2.5.1-alpha, also in 0.2.4.18-rc):
2190 - Clarify the usage and risks of setting the ContactInfo torrc line
2191 for your relay or bridge. Resolves ticket 9854.
2192 - Add anchors to the manpage so we can link to the html version of
2193 the documentation for specific options. Resolves ticket 9866.
2194 - Replace remaining references to DirServer in man page and
2195 log entries. Resolves ticket 10124.
2198 - Make the "tor-gencert" tool used by directory authority operators
2199 create 2048-bit signing keys by default (rather than 1024-bit, since
2200 1024-bit is uncomfortably small these days). Addresses ticket 10324.
2203 Changes in version 0.2.4.20 - 2013-12-22
2204 Tor 0.2.4.20 fixes potentially poor random number generation for users
2205 who 1) use OpenSSL 1.0.0 or later, 2) set "HardwareAccel 1" in their
2206 torrc file, 3) have "Sandy Bridge" or "Ivy Bridge" Intel processors,
2207 and 4) have no state file in their DataDirectory (as would happen on
2208 first start). Users who generated relay or hidden service identity
2209 keys in such a situation should discard them and generate new ones.
2211 This release also fixes a logic error that caused Tor clients to build
2212 many more preemptive circuits than they actually need.
2215 - Do not allow OpenSSL engines to replace the PRNG, even when
2216 HardwareAccel is set. The only default builtin PRNG engine uses
2217 the Intel RDRAND instruction to replace the entire PRNG, and
2218 ignores all attempts to seed it with more entropy. That's
2219 cryptographically stupid: the right response to a new alleged
2220 entropy source is never to discard all previously used entropy
2221 sources. Fixes bug 10402; works around behavior introduced in
2222 OpenSSL 1.0.0. Diagnosis and investigation thanks to "coderman"
2224 - Fix assertion failure when AutomapHostsOnResolve yields an IPv6
2225 address. Fixes bug 10465; bugfix on 0.2.4.7-alpha.
2226 - Avoid launching spurious extra circuits when a stream is pending.
2227 This fixes a bug where any circuit that _wasn't_ unusable for new
2228 streams would be treated as if it were, causing extra circuits to
2229 be launched. Fixes bug 10456; bugfix on 0.2.4.12-alpha.
2232 - Avoid a crash bug when starting with a corrupted microdescriptor
2233 cache file. Fixes bug 10406; bugfix on 0.2.2.6-alpha.
2234 - If we fail to dump a previously cached microdescriptor to disk, avoid
2235 freeing duplicate data later on. Fixes bug 10423; bugfix on
2236 0.2.4.13-alpha. Spotted by "bobnomnom".
2239 Changes in version 0.2.4.19 - 2013-12-11
2240 The Tor 0.2.4 release series is dedicated to the memory of Aaron Swartz
2241 (1986-2013). Aaron worked on diverse projects including helping to guide
2242 Creative Commons, playing a key role in stopping SOPA/PIPA, bringing
2243 transparency to the U.S government's PACER documents, and contributing
2244 design and development for Tor and Tor2Web. Aaron was one of the latest
2245 martyrs in our collective fight for civil liberties and human rights,
2246 and his death is all the more painful because he was one of us.
2248 Tor 0.2.4.19, the first stable release in the 0.2.4 branch, features
2249 a new circuit handshake and link encryption that use ECC to provide
2250 better security and efficiency; makes relays better manage circuit
2251 creation requests; uses "directory guards" to reduce client enumeration
2252 risks; makes bridges collect and report statistics about the pluggable
2253 transports they support; cleans up and improves our geoip database;
2254 gets much closer to IPv6 support for clients, bridges, and relays; makes
2255 directory authorities use measured bandwidths rather than advertised
2256 ones when computing flags and thresholds; disables client-side DNS
2257 caching to reduce tracking risks; and fixes a big bug in bridge
2258 reachability testing. This release introduces two new design
2259 abstractions in the code: a new "channel" abstraction between circuits
2260 and or_connections to allow for implementing alternate relay-to-relay
2261 transports, and a new "circuitmux" abstraction storing the queue of
2262 circuits for a channel. The release also includes many stability,
2263 security, and privacy fixes.
2266 Changes in version 0.2.4.18-rc - 2013-11-16
2267 Tor 0.2.4.18-rc is the fourth release candidate for the Tor 0.2.4.x
2268 series. It takes a variety of fixes from the 0.2.5.x branch to improve
2269 stability, performance, and better handling of edge cases.
2272 - Re-enable TLS 1.1 and 1.2 when built with OpenSSL 1.0.1e or later.
2273 Resolves ticket 6055. (OpenSSL before 1.0.1 didn't have TLS 1.1 or
2274 1.2, and OpenSSL from 1.0.1 through 1.0.1d had bugs that prevented
2275 renegotiation from working with TLS 1.1 or 1.2, so we had disabled
2276 them to solve bug 6033.)
2279 - No longer stop reading or writing on cpuworker connections when
2280 our rate limiting buckets go empty. Now we should handle circuit
2281 handshake requests more promptly. Resolves bug 9731.
2282 - If we are unable to save a microdescriptor to the journal, do not
2283 drop it from memory and then reattempt downloading it. Fixes bug
2284 9645; bugfix on 0.2.2.6-alpha.
2285 - Stop trying to bootstrap all our directory information from
2286 only our first guard. Discovered while fixing bug 9946; bugfix
2288 - The new channel code sometimes lost track of in-progress circuits,
2289 causing long-running clients to stop building new circuits. The
2290 fix is to always call circuit_n_chan_done(chan, 0) from
2291 channel_closed(). Fixes bug 9776; bugfix on 0.2.4.17-rc.
2293 o Minor bugfixes (on 0.2.4.x):
2294 - Correctly log long IPv6 exit policies, instead of truncating them
2295 or reporting an error. Fixes bug 9596; bugfix on 0.2.4.7-alpha.
2296 - Our default TLS ecdhe groups were backwards: we meant to be using
2297 P224 for relays (for performance win) and P256 for bridges (since
2298 it is more common in the wild). Instead we had it backwards. After
2299 reconsideration, we decided that the default should be P256 on all
2300 hosts, since its security is probably better, and since P224 is
2301 reportedly used quite little in the wild. Found by "skruffy" on
2302 IRC. Fix for bug 9780; bugfix on 0.2.4.8-alpha.
2303 - Free directory authority certificate download statuses on exit
2304 rather than leaking them. Fixes bug 9644; bugfix on 0.2.4.13-alpha.
2306 o Minor bugfixes (on 0.2.3.x and earlier):
2307 - If the guard we choose first doesn't answer, we would try the
2308 second guard, but once we connected to the second guard we would
2309 abandon it and retry the first one, slowing down bootstrapping.
2310 The fix is to treat all our initially chosen guards as acceptable
2311 to use. Fixes bug 9946; bugfix on 0.1.1.11-alpha.
2312 - Fix an assertion failure that would occur when disabling the
2313 ORPort setting on a running Tor process while accounting was
2314 enabled. Fixes bug 6979; bugfix on 0.2.2.18-alpha.
2315 - When examining the list of network interfaces to find our address,
2316 do not consider non-running or disabled network interfaces. Fixes
2317 bug 9904; bugfix on 0.2.3.11-alpha. Patch from "hantwister".
2318 - Avoid an off-by-one error when checking buffer boundaries when
2319 formatting the exit status of a pluggable transport helper.
2320 This is probably not an exploitable bug, but better safe than
2321 sorry. Fixes bug 9928; bugfix on 0.2.3.18-rc. Bug found by
2324 o Minor features (protecting client timestamps):
2325 - Clients no longer send timestamps in their NETINFO cells. These were
2326 not used for anything, and they provided one small way for clients
2327 to be distinguished from each other as they moved from network to
2328 network or behind NAT. Implements part of proposal 222.
2329 - Clients now round timestamps in INTRODUCE cells down to the nearest
2330 10 minutes. If a new Support022HiddenServices option is set to 0, or
2331 if it's set to "auto" and the feature is disabled in the consensus,
2332 the timestamp is sent as 0 instead. Implements part of proposal 222.
2333 - Stop sending timestamps in AUTHENTICATE cells. This is not such
2334 a big deal from a security point of view, but it achieves no actual
2335 good purpose, and isn't needed. Implements part of proposal 222.
2336 - Reduce down accuracy of timestamps in hidden service descriptors.
2337 Implements part of proposal 222.
2339 o Minor features (other):
2340 - Improve the circuit queue out-of-memory handler. Previously, when
2341 we ran low on memory, we'd close whichever circuits had the most
2342 queued cells. Now, we close those that have the *oldest* queued
2343 cells, on the theory that those are most responsible for us
2344 running low on memory. Based on analysis from a forthcoming paper
2345 by Jansen, Tschorsch, Johnson, and Scheuermann. Fixes bug 9093.
2346 - Generate bootstrapping status update events correctly when fetching
2347 microdescriptors. Fixes bug 9927.
2348 - Update to the October 2 2013 Maxmind GeoLite Country database.
2350 o Documentation fixes:
2351 - Clarify the usage and risks of setting the ContactInfo torrc line
2352 for your relay or bridge. Resolves ticket 9854.
2353 - Add anchors to the manpage so we can link to the html version of
2354 the documentation for specific options. Resolves ticket 9866.
2355 - Replace remaining references to DirServer in man page and
2356 log entries. Resolves ticket 10124.
2359 Changes in version 0.2.5.1-alpha - 2013-10-02
2360 Tor 0.2.5.1-alpha introduces experimental support for syscall sandboxing
2361 on Linux, allows bridges that offer pluggable transports to report usage
2362 statistics, fixes many issues to make testing easier, and provides
2363 a pile of minor features and bugfixes that have been waiting for a
2364 release of the new branch.
2366 This is the first alpha release in a new series, so expect there to
2367 be bugs. Users who would rather test out a more stable branch should
2368 stay with 0.2.4.x for now.
2370 o Major features (security):
2371 - Use the seccomp2 syscall filtering facility on Linux to limit
2372 which system calls Tor can invoke. This is an experimental,
2373 Linux-only feature to provide defense-in-depth against unknown
2374 attacks. To try turning it on, set "Sandbox 1" in your torrc
2375 file. Please be ready to report bugs. We hope to add support
2376 for better sandboxing in the future, including more fine-grained
2377 filters, better division of responsibility, and support for more
2378 platforms. This work has been done by Cristian-Matei Toader for
2379 Google Summer of Code.
2380 - Re-enable TLS 1.1 and 1.2 when built with OpenSSL 1.0.1e or later.
2381 Resolves ticket 6055. (OpenSSL before 1.0.1 didn't have TLS 1.1 or
2382 1.2, and OpenSSL from 1.0.1 through 1.0.1d had bugs that prevented
2383 renegotiation from working with TLS 1.1 or 1.2, so we had disabled
2384 them to solve bug 6033.)
2386 o Major features (other):
2387 - Add support for passing arguments to managed pluggable transport
2388 proxies. Implements ticket 3594.
2389 - Bridges now track GeoIP information and the number of their users
2390 even when pluggable transports are in use, and report usage
2391 statistics in their extra-info descriptors. Resolves tickets 4773
2393 - Make testing Tor networks bootstrap better: lower directory fetch
2394 retry schedules and maximum interval without directory requests,
2395 and raise maximum download tries. Implements ticket 6752.
2396 - Add make target 'test-network' to run tests on a Chutney network.
2397 Implements ticket 8530.
2398 - The ntor handshake is now on-by-default, no matter what the
2399 directory authorities recommend. Implements ticket 8561.
2402 - Instead of writing destroy cells directly to outgoing connection
2403 buffers, queue them and intersperse them with other outgoing cells.
2404 This can prevent a set of resource starvation conditions where too
2405 many pending destroy cells prevent data cells from actually getting
2406 delivered. Reported by "oftc_must_be_destroyed". Fixes bug 7912;
2407 bugfix on 0.2.0.1-alpha.
2408 - If we are unable to save a microdescriptor to the journal, do not
2409 drop it from memory and then reattempt downloading it. Fixes bug
2410 9645; bugfix on 0.2.2.6-alpha.
2411 - The new channel code sometimes lost track of in-progress circuits,
2412 causing long-running clients to stop building new circuits. The
2413 fix is to always call circuit_n_chan_done(chan, 0) from
2414 channel_closed(). Fixes bug 9776; bugfix on 0.2.4.17-rc.
2417 - Tor now builds each source file in two modes: a mode that avoids
2418 exposing identifiers needlessly, and another mode that exposes
2419 more identifiers for testing. This lets the compiler do better at
2420 optimizing the production code, while enabling us to take more
2421 radical measures to let the unit tests test things.
2422 - The production builds no longer include functions used only in
2423 the unit tests; all functions exposed from a module only for
2424 unit-testing are now static in production builds.
2425 - Add an --enable-coverage configuration option to make the unit
2426 tests (and a new src/or/tor-cov target) to build with gcov test
2430 - We now have rudimentary function mocking support that our unit
2431 tests can use to test functions in isolation. Function mocking
2432 lets the tests temporarily replace a function's dependencies with
2433 stub functions, so that the tests can check the function without
2434 invoking the other functions it calls.
2435 - Add more unit tests for the <circid,channel>->circuit map, and
2436 the destroy-cell-tracking code to fix bug 7912.
2437 - Unit tests for failing cases of the TAP onion handshake.
2438 - More unit tests for address-manipulation functions.
2440 o Minor features (protecting client timestamps):
2441 - Clients no longer send timestamps in their NETINFO cells. These were
2442 not used for anything, and they provided one small way for clients
2443 to be distinguished from each other as they moved from network to
2444 network or behind NAT. Implements part of proposal 222.
2445 - Clients now round timestamps in INTRODUCE cells down to the nearest
2446 10 minutes. If a new Support022HiddenServices option is set to 0, or
2447 if it's set to "auto" and the feature is disabled in the consensus,
2448 the timestamp is sent as 0 instead. Implements part of proposal 222.
2449 - Stop sending timestamps in AUTHENTICATE cells. This is not such
2450 a big deal from a security point of view, but it achieves no actual
2451 good purpose, and isn't needed. Implements part of proposal 222.
2452 - Reduce down accuracy of timestamps in hidden service descriptors.
2453 Implements part of proposal 222.
2455 o Minor features (config options):
2456 - Config (torrc) lines now handle fingerprints which are missing
2457 their initial '$'. Resolves ticket 4341; improvement over 0.0.9pre5.
2458 - Support a --dump-config option to print some or all of the
2459 configured options. Mainly useful for debugging the command-line
2460 option parsing code. Helps resolve ticket 4647.
2461 - Raise awareness of safer logging: notify user of potentially
2462 unsafe config options, like logging more verbosely than severity
2463 "notice" or setting SafeLogging to 0. Resolves ticket 5584.
2464 - Add a new configuration option TestingV3AuthVotingStartOffset
2465 that bootstraps a network faster by changing the timing for
2466 consensus votes. Addresses ticket 8532.
2467 - Add a new torrc option "ServerTransportOptions" that allows
2468 bridge operators to pass configuration parameters to their
2469 pluggable transports. Resolves ticket 8929.
2470 - The config (torrc) file now accepts bandwidth and space limits in
2471 bits as well as bytes. (Anywhere that you can say "2 Kilobytes",
2472 you can now say "16 kilobits", and so on.) Resolves ticket 9214.
2475 o Minor features (build):
2476 - Add support for `--library-versions` flag. Implements ticket 6384.
2477 - Return the "unexpected sendme" warnings to a warn severity, but make
2478 them rate limited, to help diagnose ticket 8093.
2479 - Detect a missing asciidoc, and warn the user about it, during
2480 configure rather than at build time. Fixes issue 6506. Patch from
2483 o Minor features (other):
2484 - Use the SOCK_NONBLOCK socket type, if supported, to open nonblocking
2485 sockets in a single system call. Implements ticket 5129.
2486 - Log current accounting state (bytes sent and received + remaining
2487 time for the current accounting period) in the relay's heartbeat
2488 message. Implements ticket 5526; patch from Peter Retzlaff.
2489 - Implement the TRANSPORT_LAUNCHED control port event that
2490 notifies controllers about new launched pluggable
2491 transports. Resolves ticket 5609.
2492 - If we're using the pure-C 32-bit curve25519_donna implementation
2493 of curve25519, build it with the -fomit-frame-pointer option to
2494 make it go faster on register-starved hosts. This improves our
2495 handshake performance by about 6% on i386 hosts without nacl.
2497 - Update to the September 4 2013 Maxmind GeoLite Country database.
2500 - Set the listen() backlog limit to the largest actually supported
2501 on the system, not to the value in a header file. Fixes bug 9716;
2502 bugfix on every released Tor.
2503 - No longer accept malformed http headers when parsing urls from
2504 headers. Now we reply with Bad Request ("400"). Fixes bug 2767;
2505 bugfix on 0.0.6pre1.
2506 - In munge_extrainfo_into_routerinfo(), check the return value of
2507 memchr(). This would have been a serious issue if we ever passed
2508 it a non-extrainfo. Fixes bug 8791; bugfix on 0.2.0.6-alpha. Patch
2510 - On the chance that somebody manages to build Tor on a
2511 platform where time_t is unsigned, correct the way that
2512 microdesc_add_to_cache() handles negative time arguments.
2513 Fixes bug 8042; bugfix on 0.2.3.1-alpha.
2514 - Reject relative control socket paths and emit a warning. Previously,
2515 single-component control socket paths would be rejected, but Tor
2516 would not log why it could not validate the config. Fixes bug 9258;
2517 bugfix on 0.2.3.16-alpha.
2519 o Minor bugfixes (command line):
2520 - Use a single command-line parser for parsing torrc options on the
2521 command line and for finding special command-line options to avoid
2522 inconsistent behavior for torrc option arguments that have the same
2523 names as command-line options. Fixes bugs 4647 and 9578; bugfix on
2525 - No longer allow 'tor --hash-password' with no arguments. Fixes bug
2526 9573; bugfix on 0.0.9pre5.
2528 o Minor fixes (build, auxiliary programs):
2529 - Stop preprocessing the "torify" script with autoconf, since
2530 it no longer refers to LOCALSTATEDIR. Fixes bug 5505; patch
2532 - The tor-fw-helper program now follows the standard convention and
2533 exits with status code "0" on success. Fixes bug 9030; bugfix on
2534 0.2.3.1-alpha. Patch by Arlo Breault.
2535 - Corrected ./configure advice for what openssl dev package you should
2536 install on Debian. Fixes bug 9207; bugfix on 0.2.0.1-alpha.
2538 o Minor code improvements:
2539 - Remove constants and tests for PKCS1 padding; it's insecure and
2540 shouldn't be used for anything new. Fixes bug 8792; patch
2542 - Remove instances of strcpy() from the unit tests. They weren't
2543 hurting anything, since they were only in the unit tests, but it's
2544 embarassing to have strcpy() in the code at all, and some analysis
2545 tools don't like it. Fixes bug 8790; bugfix on 0.2.3.6-alpha and
2546 0.2.3.8-alpha. Patch from Arlo Breault.
2549 - Remove migration code from when we renamed the "cached-routers"
2550 file to "cached-descriptors" back in 0.2.0.8-alpha. This
2551 incidentally resolves ticket 6502 by cleaning up the related code
2552 a bit. Patch from Akshay Hebbar.
2554 o Code simplification and refactoring:
2555 - Extract the common duplicated code for creating a subdirectory
2556 of the data directory and writing to a file in it. Fixes ticket
2557 4282; patch from Peter Retzlaff.
2558 - Since OpenSSL 0.9.7, the i2d_*() functions support allocating output
2559 buffer. Avoid calling twice: i2d_RSAPublicKey(), i2d_DHparams(),
2560 i2d_X509(), and i2d_PublicKey(). Resolves ticket 5170.
2561 - Add a set of accessor functions for the circuit timeout data
2562 structure. Fixes ticket 6153; patch from "piet".
2563 - Clean up exit paths from connection_listener_new(). Closes ticket
2564 8789. Patch from Arlo Breault.
2565 - Since we rely on OpenSSL 0.9.8 now, we can use EVP_PKEY_cmp()
2566 and drop our own custom pkey_eq() implementation. Fixes bug 9043.
2567 - Use a doubly-linked list to implement the global circuit list.
2568 Resolves ticket 9108. Patch from Marek Majkowski.
2569 - Remove contrib/id_to_fp.c since it wasn't used anywhere.
2572 Changes in version 0.2.4.17-rc - 2013-09-05
2573 Tor 0.2.4.17-rc is the third release candidate for the Tor 0.2.4.x
2574 series. It adds an emergency step to help us tolerate the massive
2575 influx of users: 0.2.4 clients using the new (faster and safer) "NTor"
2576 circuit-level handshakes now effectively jump the queue compared to
2577 the 0.2.3 clients using "TAP" handshakes. This release also fixes a
2578 big bug hindering bridge reachability tests.
2581 - Relays now process the new "NTor" circuit-level handshake requests
2582 with higher priority than the old "TAP" circuit-level handshake
2583 requests. We still process some TAP requests to not totally starve
2584 0.2.3 clients when NTor becomes popular. A new consensus parameter
2585 "NumNTorsPerTAP" lets us tune the balance later if we need to.
2586 Implements ticket 9574.
2589 - If the circuit build timeout logic is disabled (via the consensus,
2590 or because we are an authority), then don't build testing circuits.
2591 Fixes bug 9657; bugfix on 0.2.2.14-alpha.
2592 - Bridges now send AUTH_CHALLENGE cells during their v3 handshakes;
2593 previously they did not, which prevented them from receiving
2594 successful connections from relays for self-test or bandwidth
2595 testing. Also, when a relay is extending a circuit to a bridge,
2596 it needs to send a NETINFO cell, even when the bridge hasn't sent
2597 an AUTH_CHALLENGE cell. Fixes bug 9546; bugfix on 0.2.3.6-alpha.
2598 - If the time to download the next old-style networkstatus is in
2599 the future, do not decline to consider whether to download the
2600 next microdescriptor networkstatus. Fixes bug 9564; bugfix on
2604 - Avoid double-closing the listener socket in our socketpair()
2605 replacement (used on Windows) in the case where the addresses on
2606 our opened sockets don't match what we expected. Fixes bug 9400;
2607 bugfix on 0.0.2pre7. Found by Coverity.
2609 o Minor fixes (config options):
2610 - Avoid overflows when the user sets MaxCircuitDirtiness to a
2611 ridiculously high value, by imposing a (ridiculously high) 30-day
2612 maximum on MaxCircuitDirtiness.
2613 - Fix the documentation of HeartbeatPeriod to say that the heartbeat
2614 message is logged at notice, not at info.
2615 - Warn and fail if a server is configured not to advertise any
2616 ORPorts at all. (We need *something* to put in our descriptor,
2617 or we just won't work.)
2620 - Track how many "TAP" and "NTor" circuit handshake requests we get,
2621 and how many we complete, and log it every hour to help relay
2622 operators follow trends in network load. Addresses ticket 9658.
2623 - Update to the August 7 2013 Maxmind GeoLite Country database.
2626 Changes in version 0.2.4.16-rc - 2013-08-10
2627 Tor 0.2.4.16-rc is the second release candidate for the Tor 0.2.4.x
2628 series. It fixes several crash bugs in the 0.2.4 branch.
2631 - Fix a bug in the voting algorithm that could yield incorrect results
2632 when a non-naming authority declared too many flags. Fixes bug 9200;
2633 bugfix on 0.2.0.3-alpha.
2634 - Fix an uninitialized read that could in some cases lead to a remote
2635 crash while parsing INTRODUCE2 cells. Bugfix on 0.2.4.1-alpha.
2636 Anybody running a hidden service on the experimental 0.2.4.x
2637 branch should upgrade. (This is, so far as we know, unrelated to
2639 - Avoid an assertion failure when processing DNS replies without the
2640 answer types we expected. Fixes bug 9337; bugfix on 0.2.4.7-alpha.
2641 - Avoid a crash when using --hash-password. Fixes bug 9295; bugfix on
2642 0.2.4.15-rc. Found by stem integration tests.
2645 - Fix an invalid memory read that occured when a pluggable
2646 transport proxy failed its configuration protocol.
2647 Fixes bug 9288; bugfix on 0.2.4.1-alpha.
2648 - When evaluating whether to use a connection that we haven't
2649 decided is canonical using a recent link protocol version,
2650 decide that it's canonical only if it used address _does_
2651 match the desired address. Fixes bug 9309; bugfix on
2652 0.2.4.4-alpha. Reported by skruffy.
2653 - Make the default behavior of NumDirectoryGuards be to track
2654 NumEntryGuards. Now a user who changes only NumEntryGuards will get
2655 the behavior she expects. Fixes bug 9354; bugfix on 0.2.4.8-alpha.
2656 - Fix a spurious compilation warning with some older versions of
2657 GCC on FreeBSD. Fixes bug 9254; bugfix on 0.2.4.14-alpha.
2660 - Update to the July 3 2013 Maxmind GeoLite Country database.
2663 Changes in version 0.2.4.15-rc - 2013-07-01
2664 Tor 0.2.4.15-rc is the first release candidate for the Tor 0.2.4.x
2665 series. It fixes a few smaller bugs, but generally appears stable.
2666 Please test it and let us know whether it is!
2669 - When receiving a new configuration file via the control port's
2670 LOADCONF command, do not treat the defaults file as absent.
2671 Fixes bug 9122; bugfix on 0.2.3.9-alpha.
2674 - Issue a warning when running with the bufferevents backend enabled.
2675 It's still not stable, and people should know that they're likely
2676 to hit unexpected problems. Closes ticket 9147.
2679 Changes in version 0.2.4.14-alpha - 2013-06-18
2680 Tor 0.2.4.14-alpha fixes a pair of client guard enumeration problems
2681 present in 0.2.4.13-alpha.
2684 - When we have too much memory queued in circuits (according to a new
2685 MaxMemInCellQueues option), close the circuits consuming the most
2686 memory. This prevents us from running out of memory as a relay if
2687 circuits fill up faster than they can be drained. Fixes bug 9063;
2688 bugfix on the 54th commit of Tor. This bug is a further fix beyond
2689 bug 6252, whose fix was merged into 0.2.3.21-rc.
2691 This change also fixes an earlier approach taken in 0.2.4.13-alpha,
2692 where we tried to solve this issue simply by imposing an upper limit
2693 on the number of queued cells for a single circuit. That approach
2694 proved to be problematic, since there are ways to provoke clients to
2695 send a number of cells in excess of any such reasonable limit. Fixes
2696 bug 9072; bugfix on 0.2.4.13-alpha.
2698 - Limit hidden service descriptors to at most ten introduction
2699 points, to slow one kind of guard enumeration. Fixes bug 9002;
2700 bugfix on 0.1.1.11-alpha.
2703 Changes in version 0.2.4.13-alpha - 2013-06-14
2704 Tor 0.2.4.13-alpha fixes a variety of potential remote crash
2705 vulnerabilities, makes socks5 username/password circuit isolation
2706 actually actually work (this time for sure!), and cleans up a bunch
2707 of other issues in preparation for a release candidate.
2709 o Major bugfixes (robustness):
2710 - Close any circuit that has too many cells queued on it. Fixes
2711 bug 9063; bugfix on the 54th commit of Tor. This bug is a further
2712 fix beyond bug 6252, whose fix was merged into 0.2.3.21-rc.
2713 - Prevent the get_freelists() function from running off the end of
2714 the list of freelists if it somehow gets an unrecognized
2715 allocation. Fixes bug 8844; bugfix on 0.2.0.16-alpha. Reported by
2717 - Avoid an assertion failure on OpenBSD (and perhaps other BSDs)
2718 when an exit connection with optimistic data succeeds immediately
2719 rather than returning EINPROGRESS. Fixes bug 9017; bugfix on
2721 - Fix a directory authority crash bug when building a consensus
2722 using an older consensus as its basis. Fixes bug 8833. Bugfix
2726 - Avoid a memory leak where we would leak a consensus body when we
2727 find that a consensus which we couldn't previously verify due to
2728 missing certificates is now verifiable. Fixes bug 8719; bugfix
2730 - We used to always request authority certificates by identity digest,
2731 meaning we'd get the newest one even when we wanted one with a
2732 different signing key. Then we would complain about being given
2733 a certificate we already had, and never get the one we really
2734 wanted. Now we use the "fp-sk/" resource as well as the "fp/"
2735 resource to request the one we want. Fixes bug 5595; bugfix on
2737 - Follow the socks5 protocol when offering username/password
2738 authentication. The fix for bug 8117 exposed this bug, and it
2739 turns out real-world applications like Pidgin do care. Bugfix on
2740 0.2.3.2-alpha; fixes bug 8879.
2741 - Prevent failures on Windows Vista and later when rebuilding the
2742 microdescriptor cache. Diagnosed by Robert Ransom. Fixes bug 8822;
2743 bugfix on 0.2.4.12-alpha.
2746 - Fix an impossible buffer overrun in the AES unit tests. Fixes
2747 bug 8845; bugfix on 0.2.0.7-alpha. Found by eugenis.
2748 - If for some reason we fail to write a microdescriptor while
2749 rebuilding the cache, do not let the annotations from that
2750 microdescriptor linger in the cache file, and do not let the
2751 microdescriptor stay recorded as present in its old location.
2752 Fixes bug 9047; bugfix on 0.2.2.6-alpha.
2753 - Fix a memory leak that would occur whenever a configuration
2754 option changed. Fixes bug 8718; bugfix on 0.2.3.3-alpha.
2755 - Paste the description for PathBias parameters from the man
2756 page into or.h, so the code documents them too. Fixes bug 7982;
2757 bugfix on 0.2.3.17-beta and 0.2.4.8-alpha.
2758 - Relays now treat a changed IPv6 ORPort as sufficient reason to
2759 publish an updated descriptor. Fixes bug 6026; bugfix on
2761 - When launching a resolve request on behalf of an AF_UNIX control
2762 socket, omit the address field of the new entry connection, used in
2763 subsequent controller events, rather than letting tor_dup_addr()
2764 set it to "<unknown address type>". Fixes bug 8639; bugfix on
2767 o Minor bugfixes (log messages):
2768 - Fix a scaling issue in the path bias accounting code that
2769 resulted in "Bug:" log messages from either
2770 pathbias_scale_close_rates() or pathbias_count_build_success().
2771 This represents a bugfix on a previous bugfix: the original fix
2772 attempted in 0.2.4.10-alpha was incomplete. Fixes bug 8235; bugfix
2774 - Give a less useless error message when the user asks for an IPv4
2775 address on an IPv6-only port, or vice versa. Fixes bug 8846; bugfix
2779 - Downgrade "unexpected SENDME" warnings to protocol-warn for 0.2.4.x,
2780 to tolerate bug 8093 for now.
2781 - Add an "ignoring-advertised-bws" boolean to the flag-threshold lines
2782 in directory authority votes to describe whether they have enough
2783 measured bandwidths to ignore advertised (relay descriptor)
2784 bandwidth claims. Resolves ticket 8711.
2785 - Update to the June 5 2013 Maxmind GeoLite Country database.
2787 o Removed documentation:
2788 - Remove some of the older contents of doc/ as obsolete; move others
2789 to torspec.git. Fixes bug 8965.
2791 o Code simplification and refactoring:
2792 - Avoid using character buffers when constructing most directory
2793 objects: this approach was unwieldy and error-prone. Instead,
2794 build smartlists of strings, and concatenate them when done.
2797 Changes in version 0.2.4.12-alpha - 2013-04-18
2798 Tor 0.2.4.12-alpha moves Tor forward on several fronts: it starts the
2799 process for lengthening the guard rotation period, makes directory
2800 authority opinions in the consensus a bit less gameable, makes socks5
2801 username/password circuit isolation actually work, and fixes a wide
2802 variety of other issues.
2805 - Raise the default time that a client keeps an entry guard from
2806 "1-2 months" to "2-3 months", as suggested by Tariq Elahi's WPES
2807 2012 paper. (We would make it even longer, but we need better client
2808 load balancing first.) Also, make the guard lifetime controllable
2809 via a new GuardLifetime torrc option and a GuardLifetime consensus
2810 parameter. Start of a fix for bug 8240; bugfix on 0.1.1.11-alpha.
2811 - Directory authorities now prefer using measured bandwidths to
2812 advertised ones when computing flags and thresholds. Resolves
2814 - Directory authorities that have more than a threshold number
2815 of relays with measured bandwidths now treat relays with unmeasured
2816 bandwidths as having bandwidth 0. Resolves ticket 8435.
2818 o Major bugfixes (assert / resource use):
2819 - Avoid a bug where our response to TLS renegotiation under certain
2820 network conditions could lead to a busy-loop, with 100% CPU
2821 consumption. Fixes bug 5650; bugfix on 0.2.0.16-alpha.
2822 - Avoid an assertion when we discover that we'd like to write a cell
2823 onto a closing connection: just discard the cell. Fixes another
2824 case of bug 7350; bugfix on 0.2.4.4-alpha.
2826 o Major bugfixes (client-side privacy):
2827 - When we mark a circuit as unusable for new circuits, have it
2828 continue to be unusable for new circuits even if MaxCircuitDirtiness
2829 is increased too much at the wrong time, or the system clock jumps
2830 backwards. Fixes bug 6174; bugfix on 0.0.2pre26.
2831 - If ClientDNSRejectInternalAddresses ("do not believe DNS queries
2832 which have resolved to internal addresses") is set, apply that
2833 rule to IPv6 as well. Fixes bug 8475; bugfix on 0.2.0.7-alpha.
2834 - When an exit relay rejects a stream with reason "exit policy", but
2835 we only know an exit policy summary (e.g. from the microdesc
2836 consensus) for it, do not mark the relay as useless for all exiting.
2837 Instead, mark just the circuit as unsuitable for that particular
2838 address. Fixes part of bug 7582; bugfix on 0.2.3.2-alpha.
2839 - Allow applications to get proper stream isolation with
2840 IsolateSOCKSAuth. Many SOCKS5 clients that want to offer
2841 username/password authentication also offer "no authentication". Tor
2842 had previously preferred "no authentication", so the applications
2843 never actually sent Tor their auth details. Now Tor selects
2844 username/password authentication if it's offered. You can disable
2845 this behavior on a per-SOCKSPort basis via PreferSOCKSNoAuth. Fixes
2846 bug 8117; bugfix on 0.2.3.3-alpha.
2848 o Major bugfixes (other):
2849 - When unable to find any working directory nodes to use as a
2850 directory guard, give up rather than adding the same non-working
2851 nodes to the directory guard list over and over. Fixes bug 8231;
2852 bugfix on 0.2.4.8-alpha.
2855 - Reject as invalid most directory objects containing a NUL.
2856 Belt-and-suspender fix for bug 8037.
2857 - In our testsuite, create temporary directories with a bit more
2858 entropy in their name to make name collisions less likely. Fixes
2860 - Add CACHED keyword to ADDRMAP events in the control protocol
2861 to indicate whether a DNS result will be cached or not. Resolves
2863 - Update to the April 3 2013 Maxmind GeoLite Country database.
2865 o Minor features (build):
2866 - Detect and reject attempts to build Tor with threading support
2867 when OpenSSL has been compiled without threading support.
2869 - Clarify that when autoconf is checking for nacl, it is checking
2870 specifically for nacl with a fast curve25519 implementation.
2872 - Warn if building on a platform with an unsigned time_t: there
2873 are too many places where Tor currently assumes that time_t can
2874 hold negative values. We'd like to fix them all, but probably
2877 o Minor bugfixes (build):
2878 - Fix some bugs in tor-fw-helper-natpmp when trying to build and
2879 run it on Windows. More bugs likely remain. Patch from Gisle Vanem.
2880 Fixes bug 7280; bugfix on 0.2.3.1-alpha.
2881 - Add the old src/or/micro-revision.i filename to CLEANFILES.
2882 On the off chance that somebody has one, it will go away as soon
2883 as they run "make clean". Fix for bug 7143; bugfix on 0.2.4.1-alpha.
2884 - Build Tor correctly on 32-bit platforms where the compiler can build
2885 but not run code using the "uint128_t" construction. Fixes bug 8587;
2886 bugfix on 0.2.4.8-alpha.
2887 - Fix compilation warning with some versions of clang that would
2888 prefer the -Wswitch-enum compiler flag to warn about switch
2889 statements with missing enum values, even if those switch
2890 statements have a "default:" statement. Fixes bug 8598; bugfix
2893 o Minor bugfixes (protocol):
2894 - Fix the handling of a TRUNCATE cell when it arrives while the
2895 circuit extension is in progress. Fixes bug 7947; bugfix on 0.0.7.1.
2896 - Fix a misframing issue when reading the version numbers in a
2897 VERSIONS cell. Previously we would recognize [00 01 00 02] as
2898 'version 1, version 2, and version 0x100', when it should have
2899 only included versions 1 and 2. Fixes bug 8059; bugfix on
2900 0.2.0.10-alpha. Reported pseudonymously.
2901 - Make the format and order of STREAM events for DNS lookups
2902 consistent among the various ways to launch DNS lookups. Fixes
2903 bug 8203; bugfix on 0.2.0.24-rc. Patch by "Desoxy."
2904 - Correct our check for which versions of Tor support the EXTEND2
2905 cell. We had been willing to send it to Tor 0.2.4.7-alpha and
2906 later, when support was really added in version 0.2.4.8-alpha.
2907 Fixes bug 8464; bugfix on 0.2.4.8-alpha.
2909 o Minor bugfixes (other):
2910 - Correctly store microdescriptors and extrainfo descriptors with
2911 an internal NUL byte. Fixes bug 8037; bugfix on 0.2.0.1-alpha.
2912 Bug reported by "cypherpunks".
2913 - Increase the width of the field used to remember a connection's
2914 link protocol version to two bytes. Harmless for now, since the
2915 only currently recognized versions are one byte long. Reported
2916 pseudonymously. Fixes bug 8062; bugfix on 0.2.0.10-alpha.
2917 - If the state file's path bias counts are invalid (presumably from a
2918 buggy Tor prior to 0.2.4.10-alpha), make them correct. Also add
2919 additional checks and log messages to the scaling of Path Bias
2920 counts, in case there still are remaining issues with scaling.
2921 Should help resolve bug 8235.
2922 - Eliminate several instances where we use "Nickname=ID" to refer to
2923 nodes in logs. Use "Nickname (ID)" instead. (Elsewhere, we still use
2924 "$ID=Nickname", which is also acceptable.) Fixes bug 7065. Bugfix
2925 on 0.2.3.21-rc, 0.2.4.5-alpha, 0.2.4.8-alpha, and 0.2.4.10-alpha.
2927 o Minor bugfixes (syscalls):
2928 - Always check the return values of functions fcntl() and
2929 setsockopt(). We don't believe these are ever actually failing in
2930 practice, but better safe than sorry. Also, checking these return
2931 values should please analysis tools like Coverity. Patch from
2932 'flupzor'. Fixes bug 8206; bugfix on all versions of Tor.
2933 - Use direct writes rather than stdio when building microdescriptor
2934 caches, in an attempt to mitigate bug 8031, or at least make it
2937 o Minor bugfixes (config):
2938 - When rejecting a configuration because we were unable to parse a
2939 quoted string, log an actual error message. Fixes bug 7950; bugfix
2941 - Behave correctly when the user disables LearnCircuitBuildTimeout
2942 but doesn't tell us what they would like the timeout to be. Fixes
2943 bug 6304; bugfix on 0.2.2.14-alpha.
2944 - When autodetecting the number of CPUs, use the number of available
2945 CPUs in preference to the number of configured CPUs. Inform the
2946 user if this reduces the number of available CPUs. Fixes bug 8002;
2947 bugfix on 0.2.3.1-alpha.
2948 - Make it an error when you set EntryNodes but disable UseGuardNodes,
2949 since it will (surprisingly to some users) ignore EntryNodes. Fixes
2950 bug 8180; bugfix on 0.2.3.11-alpha.
2951 - Allow TestingTorNetworks to override the 4096-byte minimum for
2952 the Fast threshold. Otherwise they can't bootstrap until they've
2953 observed more traffic. Fixes bug 8508; bugfix on 0.2.4.10-alpha.
2954 - Fix some logic errors when the user manually overrides the
2955 PathsNeededToBuildCircuits option in torrc. Fixes bug 8599; bugfix
2958 o Minor bugfixes (log messages to help diagnose bugs):
2959 - If we fail to free a microdescriptor because of bug 7164, log
2960 the filename and line number from which we tried to free it.
2961 - Add another diagnostic to the heartbeat message: track and log
2962 overhead that TLS is adding to the data we write. If this is
2963 high, we are sending too little data to SSL_write at a time.
2964 Diagnostic for bug 7707.
2965 - Add more detail to a log message about relaxed timeouts, to help
2967 - Warn more aggressively when flushing microdescriptors to a
2968 microdescriptor cache fails, in an attempt to mitigate bug 8031,
2969 or at least make it more diagnosable.
2970 - Improve debugging output to help track down bug 8185 ("Bug:
2971 outgoing relay cell has n_chan==NULL. Dropping.")
2972 - Log the purpose of a path-bias testing circuit correctly.
2973 Improves a log message from bug 8477; bugfix on 0.2.4.8-alpha.
2975 o Minor bugfixes (0.2.4.x log messages that were too noisy):
2976 - Don't attempt to relax the timeout of already opened 1-hop circuits.
2977 They might never timeout. This should eliminate some/all cases of
2978 the relaxed timeout log message.
2979 - Use circuit creation time for network liveness evaluation. This
2980 should eliminate warning log messages about liveness caused
2981 by changes in timeout evaluation. Fixes bug 6572; bugfix on
2983 - Reduce a path bias length check from notice to info. The message
2984 is triggered when creating controller circuits. Fixes bug 8196;
2985 bugfix on 0.2.4.8-alpha.
2986 - Fix a path state issue that triggered a notice during relay startup.
2987 Fixes bug 8320; bugfix on 0.2.4.10-alpha.
2988 - Reduce occurrences of warns about circuit purpose in
2989 connection_ap_expire_building(). Fixes bug 8477; bugfix on
2992 o Minor bugfixes (pre-0.2.4.x log messages that were too noisy):
2993 - If we encounter a write failure on a SOCKS connection before we
2994 finish our SOCKS handshake, don't warn that we closed the
2995 connection before we could send a SOCKS reply. Fixes bug 8427;
2996 bugfix on 0.1.0.1-rc.
2997 - Correctly recognize that [::1] is a loopback address. Fixes
2998 bug 8377; bugfix on 0.2.1.3-alpha.
2999 - Fix a directory authority warn caused when we have a large amount
3000 of badexit bandwidth. Fixes bug 8419; bugfix on 0.2.2.10-alpha.
3001 - Don't log inappropriate heartbeat messages when hibernating: a
3002 hibernating node is _expected_ to drop out of the consensus,
3003 decide it isn't bootstrapped, and so forth. Fixes bug 7302;
3004 bugfix on 0.2.3.1-alpha.
3005 - Don't complain about bootstrapping problems while hibernating.
3006 These complaints reflect a general code problem, but not one
3007 with any problematic effects (no connections are actually
3008 opened). Fixes part of bug 7302; bugfix on 0.2.3.2-alpha.
3010 o Documentation fixes:
3011 - Update tor-fw-helper.1.txt and tor-fw-helper.c to make option
3012 names match. Fixes bug 7768.
3013 - Make the torify manpage no longer refer to tsocks; torify hasn't
3014 supported tsocks since 0.2.3.14-alpha.
3015 - Make the tor manpage no longer reference tsocks.
3016 - Fix the GeoIPExcludeUnknown documentation to refer to
3017 ExcludeExitNodes rather than the currently nonexistent
3018 ExcludeEntryNodes. Spotted by "hamahangi" on tor-talk.
3021 - The tor-tsocks.conf is no longer distributed or installed. We
3022 recommend that tsocks users use torsocks instead. Resolves
3026 Changes in version 0.2.4.11-alpha - 2013-03-11
3027 Tor 0.2.4.11-alpha makes relay measurement by directory authorities
3028 more robust, makes hidden service authentication work again, and
3029 resolves a DPI fingerprint for Tor's SSL transport.
3031 o Major features (directory authorities):
3032 - Directory authorities now support a new consensus method (17)
3033 where they cap the published bandwidth of servers for which
3034 insufficient bandwidth measurements exist. Fixes part of bug 2286.
3035 - Directory authorities that set "DisableV2DirectoryInfo_ 1" no longer
3036 serve any v2 directory information. Now we can test disabling the
3037 old deprecated v2 directory format, and see whether doing so has
3038 any effect on network load. Begins to fix bug 6783.
3039 - Directory authorities now include inside each vote a statement of
3040 the performance thresholds they used when assigning flags.
3041 Implements ticket 8151.
3043 o Major bugfixes (directory authorities):
3044 - Stop marking every relay as having been down for one hour every
3045 time we restart a directory authority. These artificial downtimes
3046 were messing with our Stable and Guard flag calculations. Fixes
3047 bug 8218 (introduced by the fix for 1035). Bugfix on 0.2.2.23-alpha.
3049 o Major bugfixes (hidden services):
3050 - Allow hidden service authentication to succeed again. When we
3051 refactored the hidden service introduction code back
3052 in 0.2.4.1-alpha, we didn't update the code that checks
3053 whether authentication information is present, causing all
3054 authentication checks to return "false". Fix for bug 8207; bugfix
3055 on 0.2.4.1-alpha. Found by Coverity; this is CID 718615.
3057 o Minor features (relays, bridges):
3058 - Make bridge relays check once a minute for whether their IP
3059 address has changed, rather than only every 15 minutes. Resolves
3061 - Refactor resolve_my_address() so it returns the method by which we
3062 decided our public IP address (explicitly configured, resolved from
3063 explicit hostname, guessed from interfaces, learned by gethostname).
3064 Now we can provide more helpful log messages when a relay guesses
3065 its IP address incorrectly (e.g. due to unexpected lines in
3066 /etc/hosts). Resolves ticket 2267.
3067 - Teach bridge-using clients to avoid 0.2.2 bridges when making
3068 microdescriptor-related dir requests, and only fall back to normal
3069 descriptors if none of their bridges can handle microdescriptors
3070 (as opposed to the fix in ticket 4013, which caused them to fall
3071 back to normal descriptors if *any* of their bridges preferred
3072 them). Resolves ticket 4994.
3073 - Randomize the lifetime of our SSL link certificate, so censors can't
3074 use the static value for filtering Tor flows. Resolves ticket 8443;
3075 related to ticket 4014 which was included in 0.2.2.33.
3076 - Support a new version of the link protocol that allows 4-byte circuit
3077 IDs. Previously, circuit IDs were limited to 2 bytes, which presented
3078 a possible resource exhaustion issue. Closes ticket 7351; implements
3081 o Minor features (portability):
3082 - Tweak the curve25519-donna*.c implementations to tolerate systems
3083 that lack stdint.h. Fixes bug 3894; bugfix on 0.2.4.8-alpha.
3084 - Use Ville Laurikari's implementation of AX_CHECK_SIGN() to determine
3085 the signs of types during autoconf. This is better than our old
3086 approach, which didn't work when cross-compiling.
3087 - Detect the sign of enum values, rather than assuming that MSC is the
3088 only compiler where enum types are all signed. Fixes bug 7727;
3089 bugfix on 0.2.4.10-alpha.
3091 o Minor features (other):
3092 - Say "KBytes" rather than "KB" in the man page (for various values
3093 of K), to further reduce confusion about whether Tor counts in
3094 units of memory or fractions of units of memory. Resolves ticket 7054.
3095 - Clear the high bit on curve25519 public keys before passing them to
3096 our backend, in case we ever wind up using a backend that doesn't do
3097 so itself. If we used such a backend, and *didn't* clear the high bit,
3098 we could wind up in a situation where users with such backends would
3099 be distinguishable from users without. Fixes bug 8121; bugfix on
3101 - Update to the March 6 2013 Maxmind GeoLite Country database.
3103 o Minor bugfixes (clients):
3104 - When we receive a RELAY_END cell with the reason DONE, or with no
3105 reason, before receiving a RELAY_CONNECTED cell, report the SOCKS
3106 status as "connection refused". Previously we reported these cases
3107 as success but then immediately closed the connection. Fixes bug
3108 7902; bugfix on 0.1.0.1-rc. Reported by "oftc_must_be_destroyed".
3109 - Downgrade an assertion in connection_ap_expire_beginning to an
3110 LD_BUG message. The fix for bug 8024 should prevent this message
3111 from displaying, but just in case, a warn that we can diagnose
3112 is better than more assert crashes. Fixes bug 8065; bugfix on
3114 - Lower path use bias thresholds to .80 for notice and .60 for warn.
3115 Also make the rate limiting flags for the path use bias log messages
3116 independent from the original path bias flags. Fixes bug 8161;
3117 bugfix on 0.2.4.10-alpha.
3119 o Minor bugfixes (relays):
3120 - Stop trying to resolve our hostname so often (e.g. every time we
3121 think about doing a directory fetch). Now we reuse the cached
3122 answer in some cases. Fixes bugs 1992 (bugfix on 0.2.0.20-rc)
3123 and 2410 (bugfix on 0.1.2.2-alpha).
3124 - Stop sending a stray "(null)" in some cases for the server status
3125 "EXTERNAL_ADDRESS" controller event. Resolves bug 8200; bugfix
3127 - When choosing which stream on a formerly stalled circuit to wake
3128 first, make better use of the platform's weak RNG. Previously,
3129 we had been using the % ("modulo") operator to try to generate a
3130 1/N chance of picking each stream, but this behaves badly with
3131 many platforms' choice of weak RNG. Fixes bug 7801; bugfix on
3133 - Use our own weak RNG when we need a weak RNG. Windows's rand() and
3134 Irix's random() only return 15 bits; Solaris's random() returns more
3135 bits but its RAND_MAX says it only returns 15, and so on. Motivated
3136 by the fix for bug 7801; bugfix on 0.2.2.20-alpha.
3138 o Minor bugfixes (directory authorities):
3139 - Directory authorities now use less space when formatting identical
3140 microdescriptor lines in directory votes. Fixes bug 8158; bugfix
3143 o Minor bugfixes (memory leaks spotted by Coverity -- bug 7816):
3144 - Avoid leaking memory if we fail to compute a consensus signature
3145 or we generate a consensus we can't parse. Bugfix on 0.2.0.5-alpha.
3146 - Fix a memory leak when receiving headers from an HTTPS proxy. Bugfix
3148 - Fix a memory leak during safe-cookie controller authentication.
3149 Bugfix on 0.2.3.13-alpha.
3150 - Avoid memory leak of IPv6 policy content if we fail to format it into
3151 a router descriptor. Bugfix on 0.2.4.7-alpha.
3153 o Minor bugfixes (other code correctness issues):
3154 - Avoid a crash if we fail to generate an extrainfo descriptor.
3155 Fixes bug 8208; bugfix on 0.2.3.16-alpha. Found by Coverity;
3157 - When detecting the largest possible file descriptor (in order to
3158 close all file descriptors when launching a new program), actually
3159 use _SC_OPEN_MAX. The old code for doing this was very, very broken.
3160 Fixes bug 8209; bugfix on 0.2.3.1-alpha. Found by Coverity; this
3162 - Fix a copy-and-paste error when adding a missing A1 to a routerset
3163 because of GeoIPExcludeUnknown. Fix for Coverity CID 980650.
3164 Bugfix on 0.2.4.10-alpha.
3165 - Fix an impossible-to-trigger integer overflow when estimating how
3166 long our onionskin queue would take. (This overflow would require us
3167 to accept 4 million onionskins before processing 100 of them.) Fixes
3168 bug 8210; bugfix on 0.2.4.10-alpha.
3170 o Code simplification and refactoring:
3171 - Add a wrapper function for the common "log a message with a
3175 Changes in version 0.2.4.10-alpha - 2013-02-04
3176 Tor 0.2.4.10-alpha adds defenses at the directory authority level from
3177 certain attacks that flood the network with relays; changes the queue
3178 for circuit create requests from a sized-based limit to a time-based
3179 limit; resumes building with MSVC on Windows; and fixes a wide variety
3182 o Major bugfixes (directory authority):
3183 - When computing directory thresholds, ignore any rejected-as-sybil
3184 nodes during the computation so that they can't influence Fast,
3185 Guard, etc. (We should have done this for proposal 109.) Fixes
3187 - When marking a node as a likely sybil, reset its uptime metrics
3188 to zero, so that it cannot time towards getting marked as Guard,
3189 Stable, or HSDir. (We should have done this for proposal 109.) Fixes
3193 - When a TLS write is partially successful but incomplete, remember
3194 that the flushed part has been flushed, and notice that bytes were
3195 actually written. Reported and fixed pseudonymously. Fixes bug
3196 7708; bugfix on Tor 0.1.0.5-rc.
3197 - Reject bogus create and relay cells with 0 circuit ID or 0 stream
3198 ID: these could be used to create unexpected streams and circuits
3199 which would count as "present" to some parts of Tor but "absent"
3200 to others, leading to zombie circuits and streams or to a bandwidth
3201 denial-of-service. Fixes bug 7889; bugfix on every released version
3202 of Tor. Reported by "oftc_must_be_destroyed".
3203 - Rename all macros in our local copy of queue.h to begin with "TOR_".
3204 This change seems the only good way to permanently prevent conflicts
3205 with queue.h on various operating systems. Fixes bug 8107; bugfix
3208 o Major features (relay):
3209 - Instead of limiting the number of queued onionskins (aka circuit
3210 create requests) to a fixed, hard-to-configure number, we limit
3211 the size of the queue based on how many we expect to be able to
3212 process in a given amount of time. We estimate the time it will
3213 take to process an onionskin based on average processing time
3214 of previous onionskins. Closes ticket 7291. You'll never have to
3215 configure MaxOnionsPending again.
3217 o Major features (portability):
3218 - Resume building correctly with MSVC and Makefile.nmake. This patch
3219 resolves numerous bugs and fixes reported by ultramage, including
3220 7305, 7308, 7309, 7310, 7312, 7313, 7315, 7316, and 7669.
3221 - Make the ntor and curve25519 code build correctly with MSVC.
3222 Fix on 0.2.4.8-alpha.
3225 - When directory authorities are computing thresholds for flags,
3226 never let the threshold for the Fast flag fall below 4096
3227 bytes. Also, do not consider nodes with extremely low bandwidths
3228 when deciding thresholds for various directory flags. This change
3229 should raise our threshold for Fast relays, possibly in turn
3230 improving overall network performance; see ticket 1854. Resolves
3232 - The Tor client now ignores sub-domain components of a .onion
3233 address. This change makes HTTP "virtual" hosting
3234 possible: http://foo.aaaaaaaaaaaaaaaa.onion/ and
3235 http://bar.aaaaaaaaaaaaaaaa.onion/ can be two different websites
3236 hosted on the same hidden service. Implements proposal 204.
3237 - We compute the overhead from passing onionskins back and forth to
3238 cpuworkers, and report it when dumping statistics in response to
3239 SIGUSR1. Supports ticket 7291.
3241 o Minor features (path selection):
3242 - When deciding whether we have enough descriptors to build circuits,
3243 instead of looking at raw relay counts, look at which fraction
3244 of (bandwidth-weighted) paths we're able to build. This approach
3245 keeps clients from building circuits if their paths are likely to
3246 stand out statistically. The default fraction of paths needed is
3247 taken from the consensus directory; you can override it with the
3248 new PathsNeededToBuildCircuits option. Fixes ticket 5956.
3249 - When any country code is listed in ExcludeNodes or ExcludeExitNodes,
3250 and we have GeoIP information, also exclude all nodes with unknown
3251 countries "??" and "A1". This behavior is controlled by the
3252 new GeoIPExcludeUnknown option: you can make such nodes always
3253 excluded with "GeoIPExcludeUnknown 1", and disable the feature
3254 with "GeoIPExcludeUnknown 0". Setting "GeoIPExcludeUnknown auto"
3255 gets you the default behavior. Implements feature 7706.
3256 - Path Use Bias: Perform separate accounting for successful circuit
3257 use. Keep separate statistics on stream attempt rates versus stream
3258 success rates for each guard. Provide configurable thresholds to
3259 determine when to emit log messages or disable use of guards that
3260 fail too many stream attempts. Resolves ticket 7802.
3262 o Minor features (log messages):
3263 - When learning a fingerprint for a bridge, log its corresponding
3264 transport type. Implements ticket 7896.
3265 - Improve the log message when "Bug/attack: unexpected sendme cell
3266 from client" occurs, to help us track bug 8093.
3269 - Remove a couple of extraneous semicolons that were upsetting the
3270 cparser library. Patch by Christian Grothoff. Fixes bug 7115;
3271 bugfix on 0.2.2.1-alpha.
3272 - Remove a source of rounding error during path bias count scaling;
3273 don't count cannibalized circuits as used for path bias until we
3274 actually try to use them; and fix a circuit_package_relay_cell()
3275 warning message about n_chan==NULL. Fixes bug 7802.
3276 - Detect nacl when its headers are in a nacl/ subdirectory. Also,
3277 actually link against nacl when we're configured to use it. Fixes
3278 bug 7972; bugfix on 0.2.4.8-alpha.
3279 - Compile correctly with the --disable-curve25519 option. Fixes
3280 bug 8153; bugfix on 0.2.4.8-alpha.
3282 o Build improvements:
3283 - Do not report status verbosely from autogen.sh unless the -v flag
3284 is specified. Fixes issue 4664. Patch from Onizuka.
3285 - Replace all calls to snprintf() outside of src/ext with
3286 tor_snprintf(). Also remove the #define to replace snprintf with
3287 _snprintf on Windows; they have different semantics, and all of
3288 our callers should be using tor_snprintf() anyway. Fixes bug 7304.
3289 - Try to detect if we are ever building on a platform where
3290 memset(...,0,...) does not set the value of a double to 0.0. Such
3291 platforms are permitted by the C standard, though in practice
3292 they're pretty rare (since IEEE 754 is nigh-ubiquitous). We don't
3293 currently support them, but it's better to detect them and fail
3294 than to perform erroneously.
3297 - Stop exporting estimates of v2 and v3 directory traffic shares
3298 in extrainfo documents. They were unneeded and sometimes inaccurate.
3299 Also stop exporting any v2 directory request statistics. Resolves
3301 - Drop support for detecting and warning about versions of Libevent
3302 before 1.3e. Nothing reasonable ships with them any longer;
3303 warning the user about them shouldn't be needed. Resolves ticket
3306 o Code simplifications and refactoring:
3307 - Rename "isin" functions to "contains", for grammar. Resolves
3309 - Rename Tor's logging function log() to tor_log(), to avoid conflicts
3310 with the natural logarithm function from the system libm. Resolves
3314 Changes in version 0.2.4.9-alpha - 2013-01-15
3315 Tor 0.2.4.9-alpha provides a quick fix to make the new ntor handshake
3319 - Fix backward compatibility logic when receiving an embedded ntor
3320 handshake tunneled in a CREATE cell. This clears up the "Bug:
3321 couldn't format CREATED cell" warning. Fixes bug 7959; bugfix
3325 Changes in version 0.2.4.8-alpha - 2013-01-14
3326 Tor 0.2.4.8-alpha introduces directory guards to reduce user enumeration
3327 risks, adds a new stronger and faster circuit handshake, and offers
3328 stronger and faster link encryption when both sides support it.
3331 - Preliminary support for directory guards (proposal 207): when
3332 possible, clients now use their entry guards for non-anonymous
3333 directory requests. This can help prevent client enumeration. Note
3334 that this behavior only works when we have a usable consensus
3335 directory, and when options about what to download are more or less
3336 standard. In the future we should re-bootstrap from our guards,
3337 rather than re-bootstrapping from the preconfigured list of
3338 directory sources that ships with Tor. Resolves ticket 6526.
3339 - Tor relays and clients now support a better CREATE/EXTEND cell
3340 format, allowing the sender to specify multiple address, identity,
3341 and handshake types. Implements Robert Ransom's proposal 200;
3344 o Major features (new circuit handshake):
3345 - Tor now supports a new circuit extension handshake designed by Ian
3346 Goldberg, Douglas Stebila, and Berkant Ustaoglu. Our original
3347 circuit extension handshake, later called "TAP", was a bit slow
3348 (especially on the relay side), had a fragile security proof, and
3349 used weaker keys than we'd now prefer. The new circuit handshake
3350 uses Dan Bernstein's "curve25519" elliptic-curve Diffie-Hellman
3351 function, making it significantly more secure than the older
3352 handshake, and significantly faster. Tor can use one of two built-in
3353 pure-C curve25519-donna implementations by Adam Langley, or it
3354 can link against the "nacl" library for a tuned version if present.
3356 The built-in version is very fast for 64-bit systems when building
3357 with GCC. The built-in 32-bit version is still faster than the
3358 old TAP protocol, but using libnacl is better on most such hosts.
3360 Clients don't currently use this protocol by default, since
3361 comparatively few clients support it so far. To try it, set
3362 UseNTorHandshake to 1.
3364 Implements proposal 216; closes ticket 7202.
3366 o Major features (better link encryption):
3367 - Relays can now enable the ECDHE TLS ciphersuites when available
3368 and appropriate. These ciphersuites let us negotiate forward-secure
3369 TLS secret keys more safely and more efficiently than with our
3370 previous use of Diffie-Hellman modulo a 1024-bit prime. By default,
3371 public relays prefer the (faster) P224 group, and bridges prefer
3372 the (more common) P256 group; you can override this with the
3375 Enabling these ciphers was a little tricky, since for a long time,
3376 clients had been claiming to support them without actually doing
3377 so, in order to foil fingerprinting. But with the client-side
3378 implementation of proposal 198 in 0.2.3.17-beta, clients can now
3379 match the ciphers from recent Firefox versions *and* list the
3380 ciphers they actually mean, so relays can believe such clients
3381 when they advertise ECDHE support in their TLS ClientHello messages.
3383 This feature requires clients running 0.2.3.17-beta or later,
3384 and requires both sides to be running OpenSSL 1.0.0 or later
3385 with ECC support. OpenSSL 1.0.1, with the compile-time option
3386 "enable-ec_nistp_64_gcc_128", is highly recommended.
3388 Implements the relay side of proposal 198; closes ticket 7200.
3391 - Avoid crashing when, as a relay without IPv6-exit support, a
3392 client insists on getting an IPv6 address or nothing. Fixes bug
3393 7814; bugfix on 0.2.4.7-alpha.
3396 - Improve circuit build timeout handling for hidden services.
3397 In particular: adjust build timeouts more accurately depending
3398 upon the number of hop-RTTs that a particular circuit type
3399 undergoes. Additionally, launch intro circuits in parallel
3400 if they timeout, and take the first one to reply as valid.
3401 - Work correctly on Unix systems where EAGAIN and EWOULDBLOCK are
3402 separate error codes; or at least, don't break for that reason.
3403 Fixes bug 7935. Reported by "oftc_must_be_destroyed".
3404 - Update to the January 2 2013 Maxmind GeoLite Country database.
3406 o Minor features (testing):
3407 - Add benchmarks for DH (1024-bit multiplicative group) and ECDH
3408 (P-256) Diffie-Hellman handshakes to src/or/bench.
3409 - Add benchmark functions to test onion handshake performance.
3411 o Minor features (path bias detection):
3412 - Alter the Path Bias log messages to be more descriptive in terms
3413 of reporting timeouts and other statistics.
3414 - Create three levels of Path Bias log messages, as opposed to just
3415 two. These are configurable via consensus as well as via the torrc
3416 options PathBiasNoticeRate, PathBiasWarnRate, PathBiasExtremeRate.
3417 The default values are 0.70, 0.50, and 0.30 respectively.
3418 - Separate the log message levels from the decision to drop guards,
3419 which also is available via torrc option PathBiasDropGuards.
3420 PathBiasDropGuards still defaults to 0 (off).
3421 - Deprecate PathBiasDisableRate in favor of PathBiasDropGuards
3422 in combination with PathBiasExtremeRate.
3423 - Increase the default values for PathBiasScaleThreshold and
3424 PathBiasCircThreshold from (200, 20) to (300, 150).
3425 - Add in circuit usage accounting to path bias. If we try to use a
3426 built circuit but fail for any reason, it counts as path bias.
3427 Certain classes of circuits where the adversary gets to pick your
3428 destination node are exempt from this accounting. Usage accounting
3429 can be specifically disabled via consensus parameter or torrc.
3430 - Convert all internal path bias state to double-precision floating
3431 point, to avoid roundoff error and other issues.
3432 - Only record path bias information for circuits that have completed
3433 *two* hops. Assuming end-to-end tagging is the attack vector, this
3434 makes us more resilient to ambient circuit failure without any
3435 detection capability loss.
3437 o Minor bugfixes (log messages):
3438 - Rate-limit the "No circuits are opened. Relaxed timeout for a
3439 circuit with channel state open..." message to once per hour to
3440 keep it from filling the notice logs. Mitigates bug 7799 but does
3441 not fix the underlying cause. Bugfix on 0.2.4.7-alpha.
3442 - Avoid spurious warnings when configuring multiple client ports of
3443 which only some are nonlocal. Previously, we had claimed that some
3444 were nonlocal when in fact they weren't. Fixes bug 7836; bugfix on
3447 o Code simplifications and refactoring:
3448 - Get rid of a couple of harmless clang warnings, where we compared
3449 enums to ints. These warnings are newly introduced in clang 3.2.
3450 - Split the onion.c file into separate modules for the onion queue
3451 and the different handshakes it supports.
3452 - Remove the marshalling/unmarshalling code for sending requests to
3453 cpuworkers over a socket, and instead just send structs. The
3454 recipient will always be the same Tor binary as the sender, so
3455 any encoding is overkill.
3458 Changes in version 0.2.4.7-alpha - 2012-12-24
3459 Tor 0.2.4.7-alpha introduces a new approach to providing fallback
3460 directory mirrors for more robust bootstrapping; fixes more issues where
3461 clients with changing network conditions refuse to make any circuits;
3462 adds initial support for exiting to IPv6 addresses; resumes being able
3463 to update our GeoIP database, and includes the geoip6 file this time;
3464 turns off the client-side DNS cache by default due to privacy risks;
3465 and fixes a variety of other issues.
3467 o Major features (client resilience):
3468 - Add a new "FallbackDir" torrc option to use when we can't use
3469 a directory mirror from the consensus (either because we lack a
3470 consensus, or because they're all down). Currently, all authorities
3471 are fallbacks by default, and there are no other default fallbacks,
3472 but that will change. This option will allow us to give clients a
3473 longer list of servers to try to get a consensus from when first
3474 connecting to the Tor network, and thereby reduce load on the
3475 directory authorities. Implements proposal 206, "Preconfigured
3476 directory sources for bootstrapping". We also removed the old
3477 "FallbackNetworkstatus" option, since we never got it working well
3478 enough to use it. Closes bug 572.
3479 - If we have no circuits open, use a relaxed timeout (the
3480 95-percentile cutoff) until a circuit succeeds. This heuristic
3481 should allow Tor to succeed at building circuits even when the
3482 network connection drastically changes. Should help with bug 3443.
3484 o Major features (IPv6):
3485 - Relays can now exit to IPv6 addresses: make sure that you have IPv6
3486 connectivity, then set the IPv6Exit flag to 1. Also make sure your
3487 exit policy reads as you would like: the address * applies to all
3488 address families, whereas *4 is IPv4 address only, and *6 is IPv6
3489 addresses only. On the client side, you'll need to wait until the
3490 authorities have upgraded, wait for enough exits to support IPv6,
3491 apply the "IPv6Traffic" flag to a SocksPort, and use Socks5. Closes
3492 ticket 5547, implements proposal 117 as revised in proposal 208.
3494 We DO NOT recommend that clients with actual anonymity needs start
3495 using IPv6 over Tor yet, since not enough exits support it yet.
3497 o Major features (geoip database):
3498 - Maxmind began labelling Tor relays as being in country "A1",
3499 which breaks by-country node selection inside Tor. Now we use a
3500 script to replace "A1" ("Anonymous Proxy") entries in our geoip
3501 file with real country codes. This script fixes about 90% of "A1"
3502 entries automatically and uses manual country code assignments to
3503 fix the remaining 10%. See src/config/README.geoip for details.
3504 Fixes bug 6266. Also update to the December 5 2012 Maxmind GeoLite
3505 Country database, as modified above.
3507 o Major bugfixes (client-side DNS):
3508 - Turn off the client-side DNS cache by default. Updating and using
3509 the DNS cache is now configurable on a per-client-port
3510 level. SOCKSPort, DNSPort, etc lines may now contain
3511 {No,}Cache{IPv4,IPv6,}DNS lines to indicate that we shouldn't
3512 cache these types of DNS answers when we receive them from an
3513 exit node in response to an application request on this port, and
3514 {No,}UseCached{IPv4,IPv6,DNS} lines to indicate that if we have
3515 cached DNS answers of these types, we shouldn't use them. It's
3516 potentially risky to use cached DNS answers at the client, since
3517 doing so can indicate to one exit what answers we've gotten
3518 for DNS lookups in the past. With IPv6, this becomes especially
3519 problematic. Using cached DNS answers for requests on the same
3520 circuit would present less linkability risk, since all traffic
3521 on a circuit is already linkable, but it would also provide
3522 little performance benefit: the exit node caches DNS replies
3523 too. Implements a simplified version of Proposal 205. Implements
3526 o Major bugfixes (other):
3527 - Alter circuit build timeout measurement to start at the point
3528 where we begin the CREATE/CREATE_FAST step (as opposed to circuit
3529 initialization). This should make our timeout measurements more
3530 uniform. Previously, we were sometimes including ORconn setup time
3531 in our circuit build time measurements. Should resolve bug 3443.
3532 - Fix an assertion that could trigger in hibernate_go_dormant() when
3533 closing an or_connection_t: call channel_mark_for_close() rather
3534 than connection_mark_for_close(). Fixes bug 7267. Bugfix on
3536 - Include the geoip6 IPv6 GeoIP database in the tarball. Fixes bug
3537 7655; bugfix on 0.2.4.6-alpha.
3540 - Add a new torrc option "ServerTransportListenAddr" to let bridge
3541 operators select the address where their pluggable transports will
3542 listen for connections. Resolves ticket 7013.
3543 - Allow an optional $ before the node identity digest in the
3544 controller command GETINFO ns/id/<identity>, for consistency with
3545 md/id/<identity> and desc/id/<identity>. Resolves ticket 7059.
3546 - Log packaged cell fullness as part of the heartbeat message.
3547 Diagnosis to try to determine the extent of bug 7743.
3549 o Minor features (IPv6):
3550 - AutomapHostsOnResolve now supports IPv6 addresses. By default, we
3551 prefer to hand out virtual IPv6 addresses, since there are more of
3552 them and we can't run out. To override this behavior and make IPv4
3553 addresses preferred, set NoPreferIPv6Automap on whatever SOCKSPort
3554 or DNSPort you're using for resolving. Implements ticket 7571.
3555 - AutomapHostsOnResolve responses are now randomized, to avoid
3556 annoying situations where Tor is restarted and applications
3557 connect to the wrong addresses.
3558 - Never try more than 1000 times to pick a new virtual address when
3559 AutomapHostsOnResolve is set. That's good enough so long as we
3560 aren't close to handing out our entire virtual address space;
3561 if you're getting there, it's best to switch to IPv6 virtual
3565 - The ADDRMAP command can no longer generate an ill-formed error
3566 code on a failed MAPADDRESS. It now says "internal" rather than
3567 an English sentence fragment with spaces in the middle. Bugfix on
3569 - Fix log messages and comments to avoid saying "GMT" when we mean
3570 "UTC". Fixes bug 6113.
3571 - Compile on win64 using mingw64. Fixes bug 7260; patches from
3573 - Fix a crash when debugging unit tests on Windows: deallocate a
3574 shared library with FreeLibrary, not CloseHandle. Fixes bug 7306;
3575 bugfix on 0.2.2.17-alpha. Reported by "ultramage".
3578 - The DirServer option is now DirAuthority, for consistency with
3579 current naming patterns. You can still use the old DirServer form.
3581 o Code simplification and refactoring:
3582 - Move the client-side address-map/virtual-address/DNS-cache code
3583 out of connection_edge.c into a new addressmap.c module.
3584 - Remove unused code for parsing v1 directories and "running routers"
3585 documents. Fixes bug 6887.
3588 Changes in version 0.2.3.25 - 2012-11-19
3589 The Tor 0.2.3 release series is dedicated to the memory of Len "rabbi"
3590 Sassaman (1980-2011), a long-time cypherpunk, anonymity researcher,
3591 Mixmaster maintainer, Pynchon Gate co-designer, CodeCon organizer,
3592 programmer, and friend. Unstinting in his dedication to the cause of
3593 freedom, he inspired and helped many of us as we began our work on
3594 anonymity, and inspires us still. Please honor his memory by writing
3595 software to protect people's freedoms, and by helping others to do so.
3597 Tor 0.2.3.25, the first stable release in the 0.2.3 branch, features
3598 significantly reduced directory overhead (via microdescriptors),
3599 enormous crypto performance improvements for fast relays on new
3600 enough hardware, a new v3 TLS handshake protocol that can better
3601 resist fingerprinting, support for protocol obfuscation plugins (aka
3602 pluggable transports), better scalability for hidden services, IPv6
3603 support for bridges, performance improvements like allowing clients
3604 to skip the first round-trip on the circuit ("optimistic data") and
3605 refilling token buckets more often, a new "stream isolation" design
3606 to isolate different applications on different circuits, and many
3607 stability, security, and privacy fixes.
3610 - Tor tries to wipe potentially sensitive data after using it, so
3611 that if some subsequent security failure exposes Tor's memory,
3612 the damage will be limited. But we had a bug where the compiler
3613 was eliminating these wipe operations when it decided that the
3614 memory was no longer visible to a (correctly running) program,
3615 hence defeating our attempt at defense in depth. We fix that
3616 by using OpenSSL's OPENSSL_cleanse() operation, which a compiler
3617 is unlikely to optimize away. Future versions of Tor may use
3618 a less ridiculously heavy approach for this. Fixes bug 7352.
3619 Reported in an article by Andrey Karpov.
3622 - Fix a harmless bug when opting against publishing a relay descriptor
3623 because DisableNetwork is set. Fixes bug 7464; bugfix on
3627 Changes in version 0.2.4.6-alpha - 2012-11-13
3628 Tor 0.2.4.6-alpha fixes an assert bug that has been plaguing relays,
3629 makes our defense-in-depth memory wiping more reliable, and begins to
3630 count IPv6 addresses in bridge statistics,
3633 - Fix an assertion failure that could occur when closing a connection
3634 with a spliced rendezvous circuit. Fix for bug 7212; bugfix on
3636 - Tor tries to wipe potentially sensitive data after using it, so
3637 that if some subsequent security failure exposes Tor's memory,
3638 the damage will be limited. But we had a bug where the compiler
3639 was eliminating these wipe operations when it decided that the
3640 memory was no longer visible to a (correctly running) program,
3641 hence defeating our attempt at defense in depth. We fix that
3642 by using OpenSSL's OPENSSL_cleanse() operation, which a compiler
3643 is unlikely to optimize away. Future versions of Tor may use
3644 a less ridiculously heavy approach for this. Fixes bug 7352.
3645 Reported in an article by Andrey Karpov.
3648 - Add GeoIP database for IPv6 addresses. The new config option
3650 - Bridge statistics now count bridge clients connecting over IPv6:
3651 bridge statistics files now list "bridge-ip-versions" and
3652 extra-info documents list "geoip6-db-digest". The control protocol
3653 "CLIENTS_SEEN" and "ip-to-country" queries now support IPv6. Initial
3654 implementation by "shkoo", addressing ticket 5055.
3657 - Warn when we are binding low ports when hibernation is enabled;
3658 previously we had warned when we were _advertising_ low ports with
3659 hibernation enabled. Fixes bug 7285; bugfix on 0.2.3.9-alpha.
3660 - Fix a harmless bug when opting against publishing a relay descriptor
3661 because DisableNetwork is set. Fixes bug 7464; bugfix on
3663 - Add warning message when a managed proxy dies during configuration.
3664 Fixes bug 7195; bugfix on 0.2.4.2-alpha.
3665 - Fix a linking error when building tor-fw-helper without miniupnp.
3666 Fixes bug 7235; bugfix on 0.2.4.2-alpha. Fix by Anthony G. Basile.
3667 - Check for closing an or_connection_t without going through correct
3668 channel functions; emit a warning and then call
3669 connection_or_close_for_error() so we don't assert as in bugs 7212
3671 - Compile correctly on compilers without C99 designated initializer
3672 support. Fixes bug 7286; bugfix on 0.2.4.4-alpha.
3673 - Avoid a possible assert that can occur when channel_send_destroy() is
3674 called on a channel in CHANNEL_STATE_CLOSING, CHANNEL_STATE_CLOSED,
3675 or CHANNEL_STATE_ERROR when the Tor process is resumed after being
3676 blocked for a long interval. Fixes bug 7350; bugfix on 0.2.4.4-alpha.
3677 - Fix a memory leak on failing cases of channel_tls_process_certs_cell.
3678 Fixes bug 7422; bugfix on 0.2.4.4-alpha.
3680 o Code simplification and refactoring:
3681 - Start using OpenBSD's implementation of queue.h, so that we don't
3682 need to hand-roll our own pointer and list structures whenever we
3683 need them. (We can't rely on a sys/queue.h, since some operating
3684 systems don't have them, and the ones that do have them don't all
3685 present the same extensions.)
3688 Changes in version 0.2.4.5-alpha - 2012-10-25
3689 Tor 0.2.4.5-alpha comes hard at the heels of 0.2.4.4-alpha, to fix
3690 two important security vulnerabilities that could lead to remotely
3691 triggerable relay crashes, fix a major bug that was preventing clients
3692 from choosing suitable exit nodes, and refactor some of our code.
3694 o Major bugfixes (security, also in 0.2.3.24-rc):
3695 - Fix a group of remotely triggerable assertion failures related to
3696 incorrect link protocol negotiation. Found, diagnosed, and fixed
3697 by "some guy from France". Fix for CVE-2012-2250; bugfix on
3699 - Fix a denial of service attack by which any directory authority
3700 could crash all the others, or by which a single v2 directory
3701 authority could crash everybody downloading v2 directory
3702 information. Fixes bug 7191; bugfix on 0.2.0.10-alpha.
3704 o Major bugfixes (also in 0.2.3.24-rc):
3705 - When parsing exit policy summaries from microdescriptors, we had
3706 previously been ignoring the last character in each one, so that
3707 "accept 80,443,8080" would be treated by clients as indicating
3708 a node that allows access to ports 80, 443, and 808. That would
3709 lead to clients attempting connections that could never work,
3710 and ignoring exit nodes that would support their connections. Now
3711 clients parse these exit policy summaries correctly. Fixes bug 7192;
3712 bugfix on 0.2.3.1-alpha.
3714 o Minor bugfixes (also in 0.2.3.24-rc):
3715 - Clients now consider the ClientRejectInternalAddresses config option
3716 when using a microdescriptor consensus stanza to decide whether
3717 an exit relay would allow exiting to an internal address. Fixes
3718 bug 7190; bugfix on 0.2.3.1-alpha.
3721 - Only disable TLS session ticket support when running as a TLS
3722 server. Now clients will blend better with regular Firefox
3723 connections. Fixes bug 7189; bugfix on Tor 0.2.3.23-rc.
3725 o Code simplification and refactoring:
3726 - Start using OpenBSD's implementation of queue.h (originally by
3728 - Move the entry node code from circuitbuild.c to its own file.
3729 - Move the circuit build timeout tracking code from circuitbuild.c
3733 Changes in version 0.2.3.24-rc - 2012-10-25
3734 Tor 0.2.3.24-rc fixes two important security vulnerabilities that
3735 could lead to remotely triggerable relay crashes, and fixes
3736 a major bug that was preventing clients from choosing suitable exit
3739 o Major bugfixes (security):
3740 - Fix a group of remotely triggerable assertion failures related to
3741 incorrect link protocol negotiation. Found, diagnosed, and fixed
3742 by "some guy from France". Fix for CVE-2012-2250; bugfix on
3744 - Fix a denial of service attack by which any directory authority
3745 could crash all the others, or by which a single v2 directory
3746 authority could crash everybody downloading v2 directory
3747 information. Fixes bug 7191; bugfix on 0.2.0.10-alpha.
3750 - When parsing exit policy summaries from microdescriptors, we had
3751 previously been ignoring the last character in each one, so that
3752 "accept 80,443,8080" would be treated by clients as indicating
3753 a node that allows access to ports 80, 443, and 808. That would
3754 lead to clients attempting connections that could never work,
3755 and ignoring exit nodes that would support their connections. Now
3756 clients parse these exit policy summaries correctly. Fixes bug 7192;
3757 bugfix on 0.2.3.1-alpha.
3760 - Clients now consider the ClientRejectInternalAddresses config option
3761 when using a microdescriptor consensus stanza to decide whether
3762 an exit relay would allow exiting to an internal address. Fixes
3763 bug 7190; bugfix on 0.2.3.1-alpha.
3766 Changes in version 0.2.4.4-alpha - 2012-10-20
3767 Tor 0.2.4.4-alpha adds a new v3 directory authority, fixes a privacy
3768 vulnerability introduced by a change in OpenSSL, fixes a remotely
3769 triggerable assert, and adds new channel_t and circuitmux_t abstractions
3770 that will make it easier to test new connection transport and cell
3771 scheduling algorithms.
3773 o New directory authorities (also in 0.2.3.23-rc):
3774 - Add Faravahar (run by Sina Rabbani) as the ninth v3 directory
3775 authority. Closes ticket 5749.
3777 o Major bugfixes (security/privacy, also in 0.2.3.23-rc):
3778 - Disable TLS session tickets. OpenSSL's implementation was giving
3779 our TLS session keys the lifetime of our TLS context objects, when
3780 perfect forward secrecy would want us to discard anything that
3781 could decrypt a link connection as soon as the link connection
3782 was closed. Fixes bug 7139; bugfix on all versions of Tor linked
3783 against OpenSSL 1.0.0 or later. Found by Florent Daignière.
3784 - Discard extraneous renegotiation attempts once the V3 link
3785 protocol has been initiated. Failure to do so left us open to
3786 a remotely triggerable assertion failure. Fixes CVE-2012-2249;
3787 bugfix on 0.2.3.6-alpha. Reported by "some guy from France".
3789 o Internal abstraction features:
3790 - Introduce new channel_t abstraction between circuits and
3791 or_connection_t to allow for implementing alternate OR-to-OR
3792 transports. A channel_t is an abstract object which can either be a
3793 cell-bearing channel, which is responsible for authenticating and
3794 handshaking with the remote OR and transmitting cells to and from
3795 it, or a listening channel, which spawns new cell-bearing channels
3796 at the request of remote ORs. Implements part of ticket 6465.
3797 - Also new is the channel_tls_t subclass of channel_t, adapting it
3798 to the existing or_connection_t code. The V2/V3 protocol handshaking
3799 code which formerly resided in command.c has been moved below the
3800 channel_t abstraction layer and may be found in channeltls.c now.
3801 Implements the rest of ticket 6465.
3802 - Introduce new circuitmux_t storing the queue of circuits for
3803 a channel; this encapsulates and abstracts the queue logic and
3804 circuit selection policy, and allows the latter to be overridden
3805 easily by switching out a policy object. The existing EWMA behavior
3806 is now implemented as a circuitmux_policy_t. Resolves ticket 6816.
3808 o Required libraries:
3809 - Tor now requires OpenSSL 0.9.8 or later. OpenSSL 1.0.0 or later is
3810 strongly recommended.
3813 - Warn users who run hidden services on a Tor client with
3814 UseEntryGuards disabled that their hidden services will be
3815 vulnerable to http://freehaven.net/anonbib/#hs-attack06 (the
3816 attack which motivated Tor to support entry guards in the first
3817 place). Resolves ticket 6889.
3818 - Tor now builds correctly on Bitrig, an OpenBSD fork. Patch from
3819 dhill. Resolves ticket 6982.
3820 - Option OutboundBindAddress can be specified multiple times and
3821 accepts IPv6 addresses. Resolves ticket 6876.
3823 o Minor bugfixes (also in 0.2.3.23-rc):
3824 - Don't serve or accept v2 hidden service descriptors over a
3825 relay's DirPort. It's never correct to do so, and disabling it
3826 might make it more annoying to exploit any bugs that turn up in the
3827 descriptor-parsing code. Fixes bug 7149.
3828 - Fix two cases in src/or/transports.c where we were calling
3829 fmt_addr() twice in a parameter list. Bug found by David
3830 Fifield. Fixes bug 7014; bugfix on 0.2.3.9-alpha.
3831 - Fix memory leaks whenever we logged any message about the "path
3832 bias" detection. Fixes bug 7022; bugfix on 0.2.3.21-rc.
3833 - When relays refuse a "create" cell because their queue of pending
3834 create cells is too big (typically because their cpu can't keep up
3835 with the arrival rate), send back reason "resource limit" rather
3836 than reason "internal", so network measurement scripts can get a
3837 more accurate picture. Fixes bug 7037; bugfix on 0.1.1.11-alpha.
3840 - Command-line option "--version" implies "--quiet". Fixes bug 6997.
3841 - Free some more still-in-use memory at exit, to make hunting for
3842 memory leaks easier. Resolves bug 7029.
3843 - When a Tor client gets a "truncated" relay cell, the first byte of
3844 its payload specifies why the circuit was truncated. We were
3845 ignoring this 'reason' byte when tearing down the circuit, resulting
3846 in the controller not being told why the circuit closed. Now we
3847 pass the reason from the truncated cell to the controller. Bugfix
3848 on 0.1.2.3-alpha; fixes bug 7039.
3849 - Downgrade "Failed to hand off onionskin" messages to "debug"
3850 severity, since they're typically redundant with the "Your computer
3851 is too slow" messages. Fixes bug 7038; bugfix on 0.2.2.16-alpha.
3852 - Make clients running with IPv6 bridges connect over IPv6 again,
3853 even without setting new config options ClientUseIPv6 and
3854 ClientPreferIPv6ORPort. Fixes bug 6757; bugfix on 0.2.4.1-alpha.
3855 - Use square brackets around IPv6 addresses in numerous places
3856 that needed them, including log messages, HTTPS CONNECT proxy
3857 requests, TransportProxy statefile entries, and pluggable transport
3858 extra-info lines. Fixes bug 7011; patch by David Fifield.
3860 o Code refactoring and cleanup:
3861 - Source files taken from other packages now reside in src/ext;
3862 previously they were scattered around the rest of Tor.
3863 - Avoid use of reserved identifiers in our C code. The C standard
3864 doesn't like us declaring anything that starts with an
3865 underscore, so let's knock it off before we get in trouble. Fix
3866 for bug 1031; bugfix on the first Tor commit.
3869 Changes in version 0.2.3.23-rc - 2012-10-20
3870 Tor 0.2.3.23-rc adds a new v3 directory authority, fixes a privacy
3871 vulnerability introduced by a change in OpenSSL, and fixes a variety
3872 of smaller bugs in preparation for the release.
3874 o New directory authorities:
3875 - Add Faravahar (run by Sina Rabbani) as the ninth v3 directory
3876 authority. Closes ticket 5749.
3878 o Major bugfixes (security/privacy):
3879 - Disable TLS session tickets. OpenSSL's implementation was giving
3880 our TLS session keys the lifetime of our TLS context objects, when
3881 perfect forward secrecy would want us to discard anything that
3882 could decrypt a link connection as soon as the link connection
3883 was closed. Fixes bug 7139; bugfix on all versions of Tor linked
3884 against OpenSSL 1.0.0 or later. Found by Florent Daignière.
3885 - Discard extraneous renegotiation attempts once the V3 link
3886 protocol has been initiated. Failure to do so left us open to
3887 a remotely triggerable assertion failure. Fixes CVE-2012-2249;
3888 bugfix on 0.2.3.6-alpha. Reported by "some guy from France".
3891 - Fix a possible crash bug when checking for deactivated circuits
3892 in connection_or_flush_from_first_active_circuit(). Fixes bug 6341;
3893 bugfix on 0.2.2.7-alpha. Bug report and fix received pseudonymously.
3895 o Minor bugfixes (on 0.2.3.x):
3896 - Fix two cases in src/or/transports.c where we were calling
3897 fmt_addr() twice in a parameter list. Bug found by David
3898 Fifield. Fixes bug 7014; bugfix on 0.2.3.9-alpha.
3899 - Convert an assert in the pathbias code to a log message. The assert
3900 appears to only be triggerable by Tor2Web mode. Fixes bug 6866;
3901 bugfix on 0.2.3.17-beta.
3902 - Fix memory leaks whenever we logged any message about the "path
3903 bias" detection. Fixes bug 7022; bugfix on 0.2.3.21-rc.
3905 o Minor bugfixes (on 0.2.2.x and earlier):
3906 - Don't serve or accept v2 hidden service descriptors over a relay's
3907 DirPort. It's never correct to do so, and disabling it might
3908 make it more annoying to exploit any bugs that turn up in the
3909 descriptor-parsing code. Fixes bug 7149.
3910 - When relays refuse a "create" cell because their queue of pending
3911 create cells is too big (typically because their cpu can't keep up
3912 with the arrival rate), send back reason "resource limit" rather
3913 than reason "internal", so network measurement scripts can get a
3914 more accurate picture. Bugfix on 0.1.1.11-alpha; fixes bug 7037.
3915 - Correct file sizes when reading binary files on Cygwin, to avoid
3916 a bug where Tor would fail to read its state file. Fixes bug 6844;
3917 bugfix on 0.1.2.7-alpha.
3918 - Avoid undefined behaviour when parsing the list of supported
3919 rendezvous/introduction protocols in a hidden service descriptor.
3920 Previously, Tor would have confused (as-yet-unused) protocol version
3921 numbers greater than 32 with lower ones on many platforms. Fixes
3922 bug 6827; bugfix on 0.2.0.10-alpha. Found by George Kadianakis.
3924 o Documentation fixes:
3925 - Clarify that hidden services are TCP only. Fixes bug 6024.
3928 Changes in version 0.2.4.3-alpha - 2012-09-22
3929 Tor 0.2.4.3-alpha fixes another opportunity for a remotely triggerable
3930 assertion, resumes letting relays test reachability of their DirPort,
3931 and cleans up a bunch of smaller bugs.
3934 - Fix an assertion failure in tor_timegm() that could be triggered
3935 by a badly formatted directory object. Bug found by fuzzing with
3936 Radamsa. Fixes bug 6811; bugfix on 0.2.0.20-rc.
3939 - Fix a possible crash bug when checking for deactivated circuits
3940 in connection_or_flush_from_first_active_circuit(). Fixes bug 6341;
3941 bugfix on 0.2.2.7-alpha. Bug report and fix received pseudonymously.
3942 - Allow routers to detect that their own DirPorts are running. When
3943 we removed support for versions_supports_begindir, we also
3944 accidentally removed the mechanism we used to self-test our
3945 DirPort. Diagnosed with help from kargig. Fixes bugs 6814 and 6815;
3946 bugfix on 0.2.4.2-alpha.
3948 o Security features:
3949 - Switch to a completely time-invariant approach for picking nodes
3950 weighted by bandwidth. Our old approach would run through the
3951 part of the loop after it had made its choice slightly slower
3952 than it ran through the part of the loop before it had made its
3953 choice. Addresses ticket 6538.
3954 - Disable the use of Guard nodes when in Tor2WebMode. Guard usage
3955 by tor2web clients allows hidden services to identify tor2web
3956 clients through their repeated selection of the same rendezvous
3957 and introduction point circuit endpoints (their guards). Resolves
3961 - Enable Tor to read configuration, state, and key information from
3962 a FIFO. Previously Tor would only read from files with a positive
3963 stat.st_size. Code from meejah; fixes bug 6044.
3966 - Correct file sizes when reading binary files on Cygwin, to avoid
3967 a bug where Tor would fail to read its state file. Fixes bug 6844;
3968 bugfix on 0.1.2.7-alpha.
3969 - Correctly handle votes with more than 31 flags. Fixes bug 6853;
3970 bugfix on 0.2.0.3-alpha.
3971 - When complaining about a client port on a public address, log
3972 which address we're complaining about. Fixes bug 4020; bugfix on
3973 0.2.3.3-alpha. Patch by Tom Fitzhenry.
3974 - Convert an assert in the pathbias code to a log message. The assert
3975 appears to only be triggerable by Tor2Web mode. Fixes bug 6866;
3976 bugfix on 0.2.3.17-beta.
3977 - Our new buildsystem was overzealous about rebuilding manpages: it
3978 would rebuild them all whenever any one of them changed. Now our
3979 dependency checking should be correct. Fixes bug 6843; bugfix on
3981 - Don't do reachability testing over IPv6 unless AuthDirPublishIPv6
3982 is set. Fixes bug 6880. Bugfix on 0.2.4.1-alpha.
3983 - Correct log printout about which address family is preferred
3984 when connecting to a bridge with both an IPv4 and IPv6 OR port.
3985 Fixes bug 6884; bugfix on 0.2.4.1-alpha.
3987 o Minor bugfixes (code cleanliness):
3988 - Fix round_to_power_of_2() so it doesn't invoke undefined behavior
3989 with large values. This situation was untriggered, but nevertheless
3990 incorrect. Fixes bug 6831; bugfix on 0.2.0.1-alpha.
3991 - Reject consensus votes with more than 64 known-flags. We aren't even
3992 close to that limit yet, and our code doesn't handle it correctly.
3993 Fixes bug 6833; bugfix on 0.2.0.1-alpha.
3994 - Avoid undefined behaviour when parsing the list of supported
3995 rendezvous/introduction protocols in a hidden service descriptor.
3996 Previously, Tor would have confused (as-yet-unused) protocol version
3997 numbers greater than 32 with lower ones on many platforms. Fixes
3998 bug 6827; bugfix on 0.2.0.10-alpha. Found by George Kadianakis.
3999 - Fix handling of rendezvous client authorization types over 8.
4000 Fixes bug 6861; bugfix on 0.2.1.5-alpha.
4001 - Fix building with older versions of GCC (2.95, for one) that don't
4002 like preprocessor directives inside macro arguments. Found by
4003 grarpamp. Fixes bug 6842; bugfix on 0.2.4.2-alpha.
4004 - Switch weighted node selection rule from using a list of doubles
4005 to using a list of int64_t. This change should make the process
4006 slightly easier to debug and maintain. Needed to finish ticket 6538.
4008 o Code simplification and refactoring:
4009 - Move the generic "config" code into a new file, and have "config.c"
4010 hold only torrc- and state-related code. Resolves ticket 6823.
4011 - Move the core of our "choose a weighted element at random" logic
4012 into its own function, and give it unit tests. Now the logic is
4013 testable, and a little less fragile too.
4014 - Removed the testing_since field of node_t, which hasn't been used
4015 for anything since 0.2.0.9-alpha.
4017 o Documentation fixes:
4018 - Clarify that hidden services are TCP only. Fixes bug 6024.
4019 - Resolve a typo in torrc.sample.in. Fixes bug 6819; bugfix on
4023 Changes in version 0.2.3.22-rc - 2012-09-11
4024 Tor 0.2.3.22-rc fixes another opportunity for a remotely triggerable
4028 - Fix an assertion failure in tor_timegm() that could be triggered
4029 by a badly formatted directory object. Bug found by fuzzing with
4030 Radamsa. Fixes bug 6811; bugfix on 0.2.0.20-rc.
4033 - Avoid segfault when starting up having run with an extremely old
4034 version of Tor and parsing its state file. Fixes bug 6801; bugfix
4038 Changes in version 0.2.2.39 - 2012-09-11
4039 Tor 0.2.2.39 fixes two more opportunities for remotely triggerable
4043 - Fix an assertion failure in tor_timegm() that could be triggered
4044 by a badly formatted directory object. Bug found by fuzzing with
4045 Radamsa. Fixes bug 6811; bugfix on 0.2.0.20-rc.
4046 - Do not crash when comparing an address with port value 0 to an
4047 address policy. This bug could have been used to cause a remote
4048 assertion failure by or against directory authorities, or to
4049 allow some applications to crash clients. Fixes bug 6690; bugfix
4053 Changes in version 0.2.4.2-alpha - 2012-09-10
4054 Tor 0.2.4.2-alpha enables port forwarding for pluggable transports,
4055 raises the default rate limiting even more, and makes the bootstrapping
4056 log messages less noisy.
4059 - Automatically forward the TCP ports of pluggable transport
4060 proxies using tor-fw-helper if PortForwarding is enabled. Implements
4064 - Raise the default BandwidthRate/BandwidthBurst values from 5MB/10MB
4065 to 1GB/1GB. The previous defaults were intended to be "basically
4066 infinite", but it turns out they're now limiting our 100mbit+
4067 relays and bridges. Fixes bug 6605; bugfix on 0.2.0.10-alpha (the
4068 last time we raised it).
4071 - Detect when we're running with a version of OpenSSL other than the
4072 one we compiled with. This has occasionally given people hard-to-
4074 - Log fewer lines at level "notice" about our OpenSSL and Libevent
4075 versions and capabilities when everything is going right. Resolves
4076 part of ticket 6736.
4077 - Directory authorities no long accept descriptors for any version of
4078 Tor before 0.2.2.35, or for any 0.2.3 release before 0.2.3.10-alpha.
4079 These versions are insecure, unsupported, or both. Implements
4083 - Rename the (internal-use-only) UsingTestingNetworkDefaults option
4084 to start with a triple-underscore so the controller won't touch it.
4085 Patch by Meejah. Fixes bug 3155. Bugfix on 0.2.2.23-alpha.
4086 - Avoid segfault when starting up having run with an extremely old
4087 version of Tor and parsing its state file. Fixes bug 6801; bugfix
4089 - Rename the (testing-use-only) _UseFilteringSSLBufferevents option
4090 so it doesn't start with _. Fixes bug 3155. Bugfix on 0.2.3.1-alpha.
4091 - Don't follow the NULL pointer if microdescriptor generation fails.
4092 (This does not appear to be triggerable, but it's best to be safe.)
4093 Found by "f. tp.". Fixes bug 6797; bugfix on 0.2.4.1-alpha.
4094 - Fix mis-declared dependencies on src/common/crypto.c and
4095 src/or/tor_main.c that could break out-of-tree builds under some
4096 circumstances. Fixes bug 6778; bugfix on 0.2.4.1-alpha.
4097 - Avoid a warning when building common_sha1.i out of tree. Fixes bug
4098 6778; bugfix on 0.2.4.1-alpha.
4099 - Fix a harmless (in this case) build warning for implicitly
4100 converting a strlen() to an int. Bugfix on 0.2.4.1-alpha.
4103 - Now that all versions before 0.2.2.x are disallowed, we no longer
4104 need to work around their missing features. Thus we can remove a
4105 bunch of compatibility code.
4108 - Tweak tor-fw-helper to accept an arbitrary amount of arbitrary
4109 TCP ports to forward. In the past it only accepted two ports:
4110 the ORPort and the DirPort.
4113 Changes in version 0.2.4.1-alpha - 2012-09-05
4114 Tor 0.2.4.1-alpha lets bridges publish their pluggable transports to
4115 bridgedb; lets relays use IPv6 addresses and directory authorities
4116 advertise them; and switches to a cleaner build interface.
4118 This is the first alpha release in a new series, so expect there to
4119 be bugs. Users who would rather test out a more stable branch should
4120 stay with 0.2.3.x for now.
4122 o Major features (bridges):
4123 - Bridges now report the pluggable transports they support to the
4124 bridge authority, so it can pass the supported transports on to
4125 bridgedb and/or eventually do reachability testing. Implements
4128 o Major features (IPv6):
4129 - Bridge authorities now accept IPv6 bridge addresses and include
4130 them in network status documents. Implements ticket 5534.
4131 - Clients who set "ClientUseIPv6 1" may connect to entry nodes over
4132 IPv6. Set "ClientPreferIPv6ORPort 1" to make this even more likely
4133 to happen. Implements ticket 5535.
4134 - All kind of relays, not just bridges, can now advertise an IPv6
4135 OR port. Implements ticket 6362.
4136 - Directory authorities vote on IPv6 OR ports using the new consensus
4137 method 14. Implements ticket 6363.
4139 o Major features (build):
4140 - Switch to a nonrecursive Makefile structure. Now instead of each
4141 Makefile.am invoking other Makefile.am's, there is a master
4142 Makefile.am that includes the others. This change makes our build
4143 process slightly more maintainable, and improves parallelism for
4144 building with make -j. Original patch by Stewart Smith; various
4145 fixes by Jim Meyering.
4146 - Where available, we now use automake's "silent" make rules by
4147 default, so that warnings are easier to spot. You can get the old
4148 behavior with "make V=1". Patch by Stewart Smith for ticket 6522.
4150 o Minor features (code security and spec conformance):
4151 - Clear keys and key-derived material left on the stack in
4152 rendservice.c and rendclient.c. Check return value of
4153 crypto_pk_write_private_key_to_string() in rend_service_load_keys().
4154 These fixes should make us more forward-secure against cold-boot
4155 attacks and the like. Fixes bug 2385.
4156 - Reject EXTEND cells sent to nonexistent streams. According to the
4157 spec, an EXTEND cell sent to _any_ nonzero stream ID is invalid, but
4158 we were only checking for stream IDs that were currently in use.
4159 Found while hunting for more instances of bug 6271. Bugfix on
4160 0.0.2pre8, which introduced incremental circuit construction.
4162 o Minor features (streamlining);
4163 - No longer include the "opt" prefix when generating routerinfos
4164 or v2 directories: it has been needless since Tor 0.1.2. Closes
4166 - Remove some now-needless code that tried to aggressively flush
4167 OR connections as data was added to them. Since 0.2.0.1-alpha, our
4168 cell queue logic has saved us from the failure mode that this code
4169 was supposed to prevent. Removing this code will limit the number
4170 of baroque control flow paths through Tor's network logic. Reported
4171 pseudonymously on IRC. Fixes bug 6468; bugfix on 0.2.0.1-alpha.
4173 o Minor features (controller):
4174 - Add a "GETINFO signal/names" control port command. Implements
4176 - Provide default values for all options via "GETINFO config/defaults".
4177 Implements ticket 4971.
4179 o Minor features (IPv6):
4180 - New config option "AuthDirHasIPv6Connectivity 1" that directory
4181 authorities should set if they have IPv6 connectivity and want to
4182 do reachability tests for IPv6 relays. Implements feature 5974.
4183 - A relay with an IPv6 OR port now sends that address in NETINFO
4184 cells (in addition to its other address). Implements ticket 6364.
4186 o Minor features (log messages):
4187 - Omit the first heartbeat log message, because it never has anything
4188 useful to say, and it clutters up the bootstrapping messages.
4189 Resolves ticket 6758.
4190 - Don't log about reloading the microdescriptor cache at startup. Our
4191 bootstrap warnings are supposed to tell the user when there's a
4192 problem, and our bootstrap notices say when there isn't. Resolves
4193 ticket 6759; bugfix on 0.2.2.6-alpha.
4194 - Don't log "I learned some more directory information" when we're
4195 reading cached directory information. Reserve it for when new
4196 directory information arrives in response to a fetch. Resolves
4198 - Prevent rounding error in path bias counts when scaling
4199 them down, and use the correct scale factor default. Also demote
4200 some path bias related log messages down a level and make others
4201 less scary sounding. Fixes bug 6647. Bugfix against 0.2.3.17-beta.
4202 - We no longer warn so much when generating manpages from their
4205 o Code simplifications and refactoring:
4206 - Enhance our internal sscanf replacement so that we can eliminate
4207 the last remaining uses of the system sscanf. (Though those uses
4208 of sscanf were safe, sscanf itself is generally error prone, so
4209 we want to eliminate when we can.) Fixes ticket 4195 and Coverity
4211 - Move ipv6_preferred from routerinfo_t to node_t. Addresses bug 4620.
4212 - Move last_reachable and testing_since from routerinfo_t to node_t.
4213 Implements ticket 5529.
4214 - Add replaycache_t structure, functions and unit tests, then refactor
4215 rend_service_introduce() to be more clear to read, improve, debug,
4216 and test. Resolves bug 6177.
4217 - Finally remove support for malloc_good_size and malloc_usable_size.
4218 We had hoped that these functions would let us eke a little more
4219 memory out of our malloc implementation. Unfortunately, the only
4220 implementations that provided these functions are also ones that
4221 are already efficient about not overallocation: they never got us
4222 more than 7 or so bytes per allocation. Removing them saves us a
4223 little code complexity and a nontrivial amount of build complexity.
4226 - Tor maintainers now require Automake version 1.9 or later to build
4227 Tor from the Git repository. (Automake is not required when building
4228 from a source distribution.)
4231 Changes in version 0.2.3.21-rc - 2012-09-05
4232 Tor 0.2.3.21-rc is the fourth release candidate for the Tor 0.2.3.x
4233 series. It fixes a trio of potential security bugs, fixes a bug where
4234 we were leaving some of the fast relays out of the microdescriptor
4235 consensus, resumes interpreting "ORPort 0" and "DirPort 0" correctly,
4236 and cleans up other smaller issues.
4238 o Major bugfixes (security):
4239 - Tear down the circuit if we get an unexpected SENDME cell. Clients
4240 could use this trick to make their circuits receive cells faster
4241 than our flow control would have allowed, or to gum up the network,
4242 or possibly to do targeted memory denial-of-service attacks on
4243 entry nodes. Fixes bug 6252. Bugfix on the 54th commit on Tor --
4244 from July 2002, before the release of Tor 0.0.0. We had committed
4245 this patch previously, but we had to revert it because of bug 6271.
4246 Now that 6271 is fixed, this patch appears to work.
4247 - Reject any attempt to extend to an internal address. Without
4248 this fix, a router could be used to probe addresses on an internal
4249 network to see whether they were accepting connections. Fixes bug
4250 6710; bugfix on 0.0.8pre1.
4251 - Do not crash when comparing an address with port value 0 to an
4252 address policy. This bug could have been used to cause a remote
4253 assertion failure by or against directory authorities, or to
4254 allow some applications to crash clients. Fixes bug 6690; bugfix
4258 - Remove the upper bound on microdescriptor length. We were hitting
4259 the limit for routers with complex exit policies or family
4260 declarations, causing clients to not use them. Fixes the first
4261 piece of bug 6404; fix on 0.2.2.6-alpha.
4262 - Detect "ORPort 0" as meaning, uniformly, that we're not running
4263 as a relay. Previously, some of our code would treat the presence
4264 of any ORPort line as meaning that we should act like a relay,
4265 even though our new listener code would correctly not open any
4266 ORPorts for ORPort 0. Similar bugs in other Port options are also
4267 fixed. Fixes the first half of bug 6507; bugfix on 0.2.3.3-alpha.
4270 - Avoid a pair of double-free and use-after-mark bugs that can
4271 occur with certain timings in canceled and re-received DNS
4272 requests. Fixes bug 6472; bugfix on 0.0.7rc1.
4273 - Fix build and 64-bit compile warnings from --enable-openbsd-malloc.
4274 Fixes bug 6379. Bugfix on 0.2.0.20-rc.
4275 - Allow one-hop directory fetching circuits the full "circuit build
4276 timeout" period, rather than just half of it, before failing them
4277 and marking the relay down. This fix should help reduce cases where
4278 clients declare relays (or worse, bridges) unreachable because
4279 the TLS handshake takes a few seconds to complete. Fixes bug 6743;
4280 bugfix on 0.2.2.2-alpha, where we changed the timeout from a static
4282 - Authorities no longer include any router in their microdescriptor
4283 consensuses for which they couldn't generate or agree on a
4284 microdescriptor. Fixes the second piece of bug 6404; fix on
4286 - Detect and reject attempts to specify both "FooPort" and
4287 "FooPort 0" in the same configuration domain. (It's still okay
4288 to have a FooPort in your configuration file, and use "FooPort 0"
4289 on the command line to disable it.) Fixes the second half of bug
4290 6507; bugfix on 0.2.3.3-alpha.
4291 - Make wildcarded addresses (that is, ones beginning with "*.") work
4292 when provided via the controller's MapAddress command. Previously,
4293 they were accepted, but we never actually noticed that they were
4294 wildcards. Fixes bug 6244; bugfix on 0.2.3.9-alpha.
4295 - Avoid crashing on a malformed state file where EntryGuardPathBias
4296 precedes EntryGuard. Fix for bug 6774; bugfix on 0.2.3.17-beta.
4297 - Add a (probably redundant) memory clear between iterations of
4298 the router status voting loop, to prevent future coding errors
4299 where data might leak between iterations of the loop. Resolves
4302 o Minor bugfixes (log messages):
4303 - Downgrade "set buildtimeout to low value" messages to "info"
4304 severity; they were never an actual problem, there was never
4305 anything reasonable to do about them, and they tended to spam logs
4306 from time to time. Fixes bug 6251; bugfix on 0.2.2.2-alpha.
4307 - Downgrade path-bias warning messages to "info". We'll try to get
4308 them working better in 0.2.4. Add internal circuit construction
4309 state to protect against the noisy warn message "Unexpectedly high
4310 circuit_successes". Also add some additional rate-limited notice
4311 messages to help determine the root cause of the warn. Fixes bug
4312 6475. Bugfix against 0.2.3.17-beta.
4313 - Move log message when unable to find a microdesc in a routerstatus
4314 entry to parse time. Previously we'd spam this warning every time
4315 we tried to figure out which microdescriptors to download. Fixes
4316 the third piece of bug 6404; fix on 0.2.3.18-rc.
4319 - Consider new, removed or changed IPv6 OR ports a non-cosmetic
4320 change when the authority is deciding whether to accept a newly
4321 uploaded descriptor. Implements ticket 6423.
4322 - Add missing documentation for consensus and microdesc files.
4323 Resolves ticket 6732.
4326 Changes in version 0.2.2.38 - 2012-08-12
4327 Tor 0.2.2.38 fixes a remotely triggerable crash bug, and fixes a timing
4328 attack that could in theory leak path information.
4331 - Avoid an uninitialized memory read when reading a vote or consensus
4332 document that has an unrecognized flavor name. This read could
4333 lead to a remote crash bug. Fixes bug 6530; bugfix on 0.2.2.6-alpha.
4334 - Try to leak less information about what relays a client is
4335 choosing to a side-channel attacker. Previously, a Tor client would
4336 stop iterating through the list of available relays as soon as it
4337 had chosen one, thus finishing a little earlier when it picked
4338 a router earlier in the list. If an attacker can recover this
4339 timing information (nontrivial but not proven to be impossible),
4340 they could learn some coarse-grained information about which relays
4341 a client was picking (middle nodes in particular are likelier to
4342 be affected than exits). The timing attack might be mitigated by
4343 other factors (see bug 6537 for some discussion), but it's best
4344 not to take chances. Fixes bug 6537; bugfix on 0.0.8rc1.
4347 Changes in version 0.2.3.20-rc - 2012-08-05
4348 Tor 0.2.3.20-rc is the third release candidate for the Tor 0.2.3.x
4349 series. It fixes a pair of code security bugs and a potential anonymity
4350 issue, updates our RPM spec files, and cleans up other smaller issues.
4353 - Avoid read-from-freed-memory and double-free bugs that could occur
4354 when a DNS request fails while launching it. Fixes bug 6480;
4355 bugfix on 0.2.0.1-alpha.
4356 - Avoid an uninitialized memory read when reading a vote or consensus
4357 document that has an unrecognized flavor name. This read could
4358 lead to a remote crash bug. Fixes bug 6530; bugfix on 0.2.2.6-alpha.
4359 - Try to leak less information about what relays a client is
4360 choosing to a side-channel attacker. Previously, a Tor client would
4361 stop iterating through the list of available relays as soon as it
4362 had chosen one, thus finishing a little earlier when it picked
4363 a router earlier in the list. If an attacker can recover this
4364 timing information (nontrivial but not proven to be impossible),
4365 they could learn some coarse-grained information about which relays
4366 a client was picking (middle nodes in particular are likelier to
4367 be affected than exits). The timing attack might be mitigated by
4368 other factors (see bug 6537 for some discussion), but it's best
4369 not to take chances. Fixes bug 6537; bugfix on 0.0.8rc1.
4372 - Try to make the warning when giving an obsolete SOCKSListenAddress
4373 a little more useful.
4374 - Terminate active server managed proxies if Tor stops being a
4375 relay. Addresses parts of bug 6274; bugfix on 0.2.3.6-alpha.
4376 - Provide a better error message about possible OSX Asciidoc failure
4377 reasons. Fixes bug 6436.
4378 - Warn when Tor is configured to use accounting in a way that can
4379 link a hidden service to some other hidden service or public
4380 address. Resolves ticket 6490.
4383 - Check return value of fputs() when writing authority certificate
4384 file. Fixes Coverity issue 709056; bugfix on 0.2.0.1-alpha.
4385 - Ignore ServerTransportPlugin lines when Tor is not configured as
4386 a relay. Fixes bug 6274; bugfix on 0.2.3.6-alpha.
4387 - When disabling guards for having too high a proportion of failed
4388 circuits, make sure to look at each guard. Fixes bug 6397; bugfix
4392 - Update our default RPM spec files to work with mock and rpmbuild
4393 on RHEL/Fedora. They have an updated set of dependencies and
4394 conflicts, a fix for an ancient typo when creating the "_tor"
4395 user, and better instructions. Thanks to Ondrej Mikle for the
4396 patch series. Fixes bug 6043.
4399 - Make it possible to set the TestingTorNetwork configuration
4400 option using AlternateDirAuthority and AlternateBridgeAuthority
4401 as an alternative to setting DirServer. Addresses ticket 6377.
4404 - Clarify the documentation for the Alternate*Authority options.
4406 - Fix some typos in the manpages. Patch from A. Costa. Fixes bug 6500.
4408 o Code simplification and refactoring:
4409 - Do not use SMARTLIST_FOREACH for any loop whose body exceeds
4410 10 lines. Also, don't nest them. Doing so in the past has
4411 led to hard-to-debug code. The new style is to use the
4412 SMARTLIST_FOREACH_{BEGIN,END} pair. Addresses issue 6400.
4415 Changes in version 0.2.3.19-rc - 2012-07-06
4416 Tor 0.2.3.19-rc is the second release candidate for the Tor 0.2.3.x
4417 series. It fixes the compile on Windows, reverts to a GeoIP database
4418 that isn't as broken, and fixes a flow control bug that has been around
4419 since the beginning of Tor.
4422 - Fix a bug handling SENDME cells on nonexistent streams that could
4423 result in bizarre window values. Report and patch contributed
4424 pseudonymously. Fixes part of bug 6271. This bug was introduced
4425 before the first Tor release, in svn commit r152.
4426 - Revert to the May 1 2012 Maxmind GeoLite Country database. In the
4427 June 2012 database, Maxmind marked many Tor relays as country "A1",
4428 which will cause risky behavior for clients that set EntryNodes
4429 or ExitNodes. Addresses bug 6334; bugfix on 0.2.3.17-beta.
4430 - Instead of ENOBUFS on Windows, say WSAENOBUFS. Fixes compilation
4431 on Windows. Fixes bug 6296; bugfix on 0.2.3.18-rc.
4434 - Fix wrong TCP port range in parse_port_range(). Fixes bug 6218;
4435 bugfix on 0.2.1.10-alpha.
4438 Changes in version 0.2.3.18-rc - 2012-06-28
4439 Tor 0.2.3.18-rc is the first release candidate for the Tor 0.2.3.x
4440 series. It fixes a few smaller bugs, but generally appears stable.
4441 Please test it and let us know whether it is!
4444 - Allow wildcarded mapaddress targets to be specified on the
4445 controlport. Partially fixes bug 6244; bugfix on 0.2.3.9-alpha.
4446 - Make our linker option detection code more robust against linkers
4447 such as on FreeBSD 8, where a bad combination of options completes
4448 successfully but makes an unrunnable binary. Fixes bug 6173;
4449 bugfix on 0.2.3.17-beta.
4451 o Minor bugfixes (on 0.2.2.x and earlier):
4452 - Avoid a false positive in the util/threads unit test by increasing
4453 the maximum timeout time. Fixes bug 6227; bugfix on 0.2.0.4-alpha.
4454 - Replace "Sending publish request" log messages with "Launching
4455 upload", so that they no longer confusingly imply that we're
4456 sending something to a directory we might not even be connected
4457 to yet. Fixes bug 3311; bugfix on 0.2.0.10-alpha.
4458 - Make sure to set *socket_error in all error cases in
4459 connection_connect(), so it can't produce a warning about
4460 errno being zero from errno_to_orconn_end_reason(). Bugfix on
4461 0.2.1.1-alpha; resolves ticket 6028.
4462 - Downgrade "Got a certificate, but we already have it" log messages
4463 from warning to info, except when we're a dirauth. Fixes bug 5238;
4464 bugfix on 0.2.1.7-alpha.
4465 - When checking for requested signatures on the latest consensus
4466 before serving it to a client, make sure to check the right
4467 consensus flavor. Bugfix on 0.2.2.6-alpha.
4468 - Downgrade "eventdns rejected address" message to LOG_PROTOCOL_WARN.
4469 Fixes bug 5932; bugfix on 0.2.2.7-alpha.
4471 o Minor bugfixes (on 0.2.3.x):
4472 - Make format_helper_exit_status() avoid unnecessary space padding
4473 and stop confusing log_from_pipe(). Fixes ticket 5557; bugfix
4475 - Downgrade a message about cleaning the microdescriptor cache to
4476 "info" from "notice". Fixes bug 6238; bugfix on 0.2.3.1-alpha.
4477 - Log a BUG message at severity INFO if we have a networkstatus with
4478 a missing entry for some microdescriptor. Continues on a patch
4480 - Improve the log message when a managed proxy fails to launch. Fixes
4481 bug 5099; bugfix on 0.2.3.6-alpha.
4482 - Don't do DNS lookups when parsing corrupted managed proxy protocol
4483 messages. Fixes bug 6226; bugfix on 0.2.3.6-alpha.
4484 - When formatting wildcarded address mappings for the controller,
4485 be sure to include "*." as appropriate. Partially fixes bug 6244;
4486 bugfix on 0.2.3.9-alpha.
4487 - Avoid a warning caused by using strcspn() from glibc with clang 3.0.
4488 Bugfix on 0.2.3.13-alpha.
4489 - Stop logging messages about running with circuit timeout learning
4490 enabled at severity LD_BUG. Fixes bug 6169; bugfix on 0.2.3.17-beta.
4491 - Disable a spurious warning about reading on a marked and flushing
4492 connection. We shouldn't be doing that, but apparently we
4493 sometimes do. Fixes bug 6203; bugfix on 0.2.3.17-beta.
4494 - Fix a bug that stopped AllowDotExit from working on addresses
4495 that had an entry in the DNS cache. Fixes bug 6211; bugfix on
4498 o Code simplification, refactoring, unit tests:
4499 - Move tor_gettimeofday_cached() into compat_libevent.c, and use
4500 Libevent's notion of cached time when possible.
4501 - Remove duplicate code for invoking getrlimit() from control.c.
4502 - Add a unit test for the environment_variable_names_equal function.
4505 - Document the --defaults-torrc option, and the new (in 0.2.3)
4506 semantics for overriding, extending, and clearing lists of
4507 options. Closes bug 4748.
4510 Changes in version 0.2.3.17-beta - 2012-06-15
4511 Tor 0.2.3.17-beta enables compiler and linker hardening by default,
4512 gets our TLS handshake back on track for being able to blend in with
4513 Firefox, fixes a big bug in 0.2.3.16-alpha that broke Tor's interaction
4514 with Vidalia, and otherwise continues to get us closer to a release
4518 - Enable gcc and ld hardening by default. Resolves ticket 5210.
4519 - Update TLS cipher list to match Firefox 8 and later. Resolves
4521 - Implement the client side of proposal 198: remove support for
4522 clients falsely claiming to support standard ciphersuites that
4523 they can actually provide. As of modern OpenSSL versions, it's not
4524 necessary to fake any standard ciphersuite, and doing so prevents
4525 us from using better ciphersuites in the future, since servers
4526 can't know whether an advertised ciphersuite is really supported or
4527 not. Some hosts -- notably, ones with very old versions of OpenSSL
4528 or where OpenSSL has been built with ECC disabled -- will stand
4529 out because of this change; TBB users should not be affected.
4532 - Change the default value for DynamicDHGroups (introduced in
4533 0.2.3.9-alpha) to 0. This feature can make Tor relays less
4534 identifiable by their use of the mod_ssl DH group, but at
4535 the cost of some usability (#4721) and bridge tracing (#6087)
4536 regressions. Resolves ticket 5598.
4537 - Send a CRLF at the end of each STATUS_* control protocol event. This
4538 bug tickled a bug in Vidalia which would make it freeze. Fixes
4539 bug 6094; bugfix on 0.2.3.16-alpha.
4542 - Disable writing on marked-for-close connections when they are
4543 blocked on bandwidth, to prevent busy-looping in Libevent. Fixes
4544 bug 5263; bugfix on 0.0.2pre13, where we first added a special
4545 case for flushing marked connections.
4546 - Detect SSL handshake even when the initial attempt to write the
4547 server hello fails. Fixes bug 4592; bugfix on 0.2.0.13-alpha.
4548 - Change the AllowDotExit rules so they should actually work.
4549 We now enforce AllowDotExit only immediately after receiving an
4550 address via SOCKS or DNSPort: other sources are free to provide
4551 .exit addresses after the resolution occurs. Fixes bug 3940;
4552 bugfix on 0.2.2.1-alpha.
4553 - Fix a (harmless) integer overflow in cell statistics reported by
4554 some fast relays. Fixes bug 5849; bugfix on 0.2.2.1-alpha.
4555 - Make sure circuitbuild.c checks LearnCircuitBuildTimeout in all the
4556 right places and never depends on the consensus parameters or
4557 computes adaptive timeouts when it is disabled. Fixes bug 5049;
4558 bugfix on 0.2.2.14-alpha.
4559 - When building Tor on Windows with -DUNICODE (not default), ensure
4560 that error messages, filenames, and DNS server names are always
4561 NUL-terminated when we convert them to a single-byte encoding.
4562 Fixes bug 5909; bugfix on 0.2.2.16-alpha.
4563 - Make Tor build correctly again with -DUNICODE -D_UNICODE defined.
4564 Fixes bug 6097; bugfix on 0.2.2.16-alpha.
4565 - Fix an edge case where TestingTorNetwork is set but the authorities
4566 and relays all have an uptime of zero, where the private Tor network
4567 could briefly lack support for hidden services. Fixes bug 3886;
4568 bugfix on 0.2.2.18-alpha.
4569 - Correct the manpage's descriptions for the default values of
4570 DirReqStatistics and ExtraInfoStatistics. Fixes bug 2865; bugfix
4572 - Fix the documentation for the --hush and --quiet command line
4573 options, which changed their behavior back in 0.2.3.3-alpha.
4574 - Fix compilation warning with clang 3.1. Fixes bug 6141; bugfix on
4578 - Rate-limit the "Weighted bandwidth is 0.000000" message, and add
4579 more information to it, so that we can track it down in case it
4580 returns again. Mitigates bug 5235.
4581 - Check CircuitBuildTimeout and LearnCircuitBuildTimeout in
4582 options_validate(); warn if LearnCircuitBuildTimeout is disabled and
4583 CircuitBuildTimeout is set unreasonably low. Resolves ticket 5452.
4584 - Warn the user when HTTPProxy, but no other proxy type, is
4585 configured. This can cause surprising behavior: it doesn't send
4586 all of Tor's traffic over the HTTPProxy -- it sends unencrypted
4587 directory traffic only. Resolves ticket 4663.
4588 - Issue a notice if a guard completes less than 40% of your circuits.
4589 Threshold is configurable by torrc option PathBiasNoticeRate and
4590 consensus parameter pb_noticepct. There is additional, off-by-
4591 default code to disable guards which fail too many circuits.
4592 Addresses ticket 5458.
4593 - Update to the June 6 2012 Maxmind GeoLite Country database.
4595 o Code simplifications and refactoring:
4596 - Remove validate_pluggable_transports_config(): its warning
4597 message is now handled by connection_or_connect().
4600 Changes in version 0.2.2.37 - 2012-06-06
4601 Tor 0.2.2.37 introduces a workaround for a critical renegotiation
4602 bug in OpenSSL 1.0.1 (where 20% of the Tor network can't talk to itself
4606 - Work around a bug in OpenSSL that broke renegotiation with TLS
4607 1.1 and TLS 1.2. Without this workaround, all attempts to speak
4608 the v2 Tor connection protocol when both sides were using OpenSSL
4609 1.0.1 would fail. Resolves ticket 6033.
4610 - When waiting for a client to renegotiate, don't allow it to add
4611 any bytes to the input buffer. This fixes a potential DoS issue.
4612 Fixes bugs 5934 and 6007; bugfix on 0.2.0.20-rc.
4613 - Fix an edge case where if we fetch or publish a hidden service
4614 descriptor, we might build a 4-hop circuit and then use that circuit
4615 for exiting afterwards -- even if the new last hop doesn't obey our
4616 ExitNodes config option. Fixes bug 5283; bugfix on 0.2.0.10-alpha.
4619 - Fix a build warning with Clang 3.1 related to our use of vasprintf.
4620 Fixes bug 5969. Bugfix on 0.2.2.11-alpha.
4623 - Tell GCC and Clang to check for any errors in format strings passed
4624 to the tor_v*(print|scan)f functions.
4627 Changes in version 0.2.3.16-alpha - 2012-06-05
4628 Tor 0.2.3.16-alpha introduces a workaround for a critical renegotiation
4629 bug in OpenSSL 1.0.1 (where 20% of the Tor network can't talk to itself
4630 currently). It also fixes a variety of smaller bugs and other cleanups
4631 that get us closer to a release candidate.
4633 o Major bugfixes (general):
4634 - Work around a bug in OpenSSL that broke renegotiation with TLS
4635 1.1 and TLS 1.2. Without this workaround, all attempts to speak
4636 the v2 Tor connection protocol when both sides were using OpenSSL
4637 1.0.1 would fail. Resolves ticket 6033.
4638 - When waiting for a client to renegotiate, don't allow it to add
4639 any bytes to the input buffer. This fixes a potential DoS issue.
4640 Fixes bugs 5934 and 6007; bugfix on 0.2.0.20-rc.
4641 - Pass correct OR address to managed proxies (like obfsproxy),
4642 even when ORListenAddress is used. Fixes bug 4865; bugfix on
4644 - The advertised platform of a router now includes only its operating
4645 system's name (e.g., "Linux", "Darwin", "Windows 7"), and not its
4646 service pack level (for Windows) or its CPU architecture (for Unix).
4647 We also no longer include the "git-XYZ" tag in the version. Resolves
4650 o Major bugfixes (clients):
4651 - If we are unable to find any exit that supports our predicted ports,
4652 stop calling them predicted, so that we don't loop and build
4653 hopeless circuits indefinitely. Fixes bug 3296; bugfix on 0.0.9pre6,
4654 which introduced predicted ports.
4655 - Fix an edge case where if we fetch or publish a hidden service
4656 descriptor, we might build a 4-hop circuit and then use that circuit
4657 for exiting afterwards -- even if the new last hop doesn't obey our
4658 ExitNodes config option. Fixes bug 5283; bugfix on 0.2.0.10-alpha.
4659 - Check at each new consensus whether our entry guards were picked
4660 long enough ago that we should rotate them. Previously, we only
4661 did this check at startup, which could lead to us holding a guard
4662 indefinitely. Fixes bug 5380; bugfix on 0.2.1.14-rc.
4663 - When fetching a bridge descriptor from a bridge authority,
4664 always do so anonymously, whether we have been able to open
4665 circuits or not. Partial fix for bug 1938; bugfix on 0.2.0.7-alpha.
4666 This behavior makes it *safer* to use UpdateBridgesFromAuthority,
4667 but we'll need to wait for bug 6010 before it's actually usable.
4669 o Major bugfixes (directory authorities):
4670 - When computing weight parameters, behave more robustly in the
4671 presence of a bad bwweightscale value. Previously, the authorities
4672 would crash if they agreed on a sufficiently broken weight_scale
4673 value: now, they use a reasonable default and carry on. Partial
4674 fix for 5786; bugfix on 0.2.2.17-alpha.
4675 - Check more thoroughly to prevent a rogue authority from
4676 double-voting on any consensus directory parameter. Previously,
4677 authorities would crash in this case if the total number of
4678 votes for any parameter exceeded the number of active voters,
4679 but would let it pass otherwise. Partial fix for bug 5786; bugfix
4683 - Rate-limit log messages when asked to connect anonymously to
4684 a private address. When these hit, they tended to hit fast and
4685 often. Also, don't bother trying to connect to addresses that we
4686 are sure will resolve to 127.0.0.1: getting 127.0.0.1 in a directory
4687 reply makes us think we have been lied to, even when the address the
4688 client tried to connect to was "localhost." Resolves ticket 2822.
4689 - Allow packagers to insert an extra string in server descriptor
4690 platform lines by setting the preprocessor variable TOR_BUILD_TAG.
4691 Resolves the rest of ticket 2988.
4692 - Raise the threshold of server descriptors needed (75%) and exit
4693 server descriptors needed (50%) before we will declare ourselves
4694 bootstrapped. This will make clients start building circuits a
4695 little later, but makes the initially constructed circuits less
4696 skewed and less in conflict with further directory fetches. Fixes
4698 - Close any connection that sends unrecognized junk before the
4699 handshake. Solves an issue noted in bug 4369.
4700 - Improve log messages about managed transports. Resolves ticket 5070.
4701 - Tag a bridge's descriptor as "never to be sent unencrypted".
4702 This shouldn't matter, since bridges don't open non-anonymous
4703 connections to the bridge authority and don't allow unencrypted
4704 directory connections from clients, but we might as well make
4705 sure. Closes bug 5139.
4706 - Expose our view of whether we have gone dormant to the controller,
4707 via a new "GETINFO dormant" value. Torbutton and other controllers
4708 can use this to avoid doing periodic requests through Tor while
4709 it's dormant (bug 4718). Fixes bug 5954.
4710 - Tell GCC and Clang to check for any errors in format strings passed
4711 to the tor_v*(print|scan)f functions.
4712 - Update to the May 1 2012 Maxmind GeoLite Country database.
4714 o Minor bugfixes (already included in 0.2.2.36):
4715 - Reject out-of-range times like 23:59:61 in parse_rfc1123_time().
4716 Fixes bug 5346; bugfix on 0.0.8pre3.
4717 - Correct parsing of certain date types in parse_http_time().
4718 Without this patch, If-Modified-Since would behave
4719 incorrectly. Fixes bug 5346; bugfix on 0.2.0.2-alpha. Patch from
4720 Esteban Manchado Velázques.
4721 - Make our number-parsing functions always treat too-large values
4722 as an error, even when those values exceed the width of the
4723 underlying type. Previously, if the caller provided these
4724 functions with minima or maxima set to the extreme values of the
4725 underlying integer type, these functions would return those
4726 values on overflow rather than treating overflow as an error.
4727 Fixes part of bug 5786; bugfix on 0.0.9.
4728 - If we hit the error case where routerlist_insert() replaces an
4729 existing (old) server descriptor, make sure to remove that
4730 server descriptor from the old_routers list. Fix related to bug
4731 1776. Bugfix on 0.2.2.18-alpha.
4732 - Clarify the behavior of MaxCircuitDirtiness with hidden service
4733 circuits. Fixes issue 5259.
4735 o Minor bugfixes (coding cleanup, on 0.2.2.x and earlier):
4736 - Prevent a null-pointer dereference when receiving a data cell
4737 for a nonexistent stream when the circuit in question has an
4738 empty deliver window. We don't believe this is triggerable,
4739 since we don't currently allow deliver windows to become empty,
4740 but the logic is tricky enough that it's better to make the code
4741 robust. Fixes bug 5541; bugfix on 0.0.2pre14.
4742 - Fix a memory leak when trying to launch a DNS request when the
4743 network is disabled or the nameservers are unconfigurable. Fixes
4744 bug 5916; bugfix on Tor 0.1.2.1-alpha (for the unconfigurable
4745 nameserver case) and on 0.2.3.9-alpha (for the DisableNetwork case).
4746 - Don't hold a Windows file handle open for every file mapping;
4747 the file mapping handle is sufficient. Fixes bug 5951; bugfix on
4749 - Avoid O(n^2) performance characteristics when parsing a large
4750 extrainfo cache. Fixes bug 5828; bugfix on 0.2.0.1-alpha.
4751 - Format more doubles with %f, not %lf. Patch from grarpamp to make
4752 Tor build correctly on older BSDs again. Fixes bug 3894; bugfix on
4754 - Make our replacement implementation of strtok_r() compatible with
4755 the standard behavior of strtok_r(). Patch by nils. Fixes bug 5091;
4756 bugfix on 0.2.2.1-alpha.
4757 - Fix a NULL-pointer dereference on a badly formed
4758 SETCIRCUITPURPOSE command. Found by mikeyc. Fixes bug 5796;
4759 bugfix on 0.2.2.9-alpha.
4760 - Fix a build warning with Clang 3.1 related to our use of vasprintf.
4761 Fixes bug 5969. Bugfix on 0.2.2.11-alpha.
4762 - Defensively refactor rend_mid_rendezvous() so that protocol
4763 violations and length checks happen in the beginning. Fixes
4765 - Set _WIN32_WINNT to 0x0501 consistently throughout the code, so
4766 that IPv6 stuff will compile on MSVC, and compilation issues
4767 will be easier to track down. Fixes bug 5861.
4769 o Minor bugfixes (correctness, on 0.2.2.x and earlier):
4770 - Exit nodes now correctly report EADDRINUSE and EADDRNOTAVAIL as
4771 resource exhaustion, so that clients can adjust their load to
4772 try other exits. Fixes bug 4710; bugfix on 0.1.0.1-rc, which
4773 started using END_STREAM_REASON_RESOURCELIMIT.
4774 - Don't check for whether the address we're using for outbound
4775 connections has changed until after the outbound connection has
4776 completed. On Windows, getsockname() doesn't succeed until the
4777 connection is finished. Fixes bug 5374; bugfix on 0.1.1.14-alpha.
4778 - If the configuration tries to set MyFamily on a bridge, refuse to
4779 do so, and warn about the security implications. Fixes bug 4657;
4780 bugfix on 0.2.0.3-alpha.
4781 - If the client fails to set a reasonable set of ciphersuites
4782 during its v2 handshake renegotiation, allow the renegotiation to
4783 continue nevertheless (i.e. send all the required certificates).
4784 Fixes bug 4591; bugfix on 0.2.0.20-rc.
4785 - When we receive a SIGHUP and the controller __ReloadTorrcOnSIGHUP
4786 option is set to 0 (which Vidalia version 0.2.16 now does when
4787 a SAVECONF attempt fails), perform other actions that SIGHUP
4788 usually causes (like reopening the logs). Fixes bug 5095; bugfix
4790 - If we fail to write a microdescriptor to the disk cache, do not
4791 continue replacing the old microdescriptor file. Fixes bug 2954;
4792 bugfix on 0.2.2.6-alpha.
4793 - Exit nodes don't need to fetch certificates for authorities that
4794 they don't recognize; only directory authorities, bridges,
4795 and caches need to do that. Fixes part of bug 2297; bugfix on
4797 - Correctly handle checking the permissions on the parent
4798 directory of a control socket in the root directory. Bug found
4799 by Esteban Manchado Velázquez. Fixes bug 5089; bugfix on Tor
4801 - When told to add a bridge with the same digest as a preexisting
4802 bridge but a different addr:port, change the addr:port as
4803 requested. Previously we would not notice the change. Fixes half
4804 of bug 5603; fix on 0.2.2.26-beta.
4805 - End AUTHCHALLENGE error messages (in the control protocol) with
4806 a CRLF. Fixes bug 5760; bugfix on 0.2.2.36 and 0.2.3.13-alpha.
4808 o Minor bugfixes (on 0.2.3.x):
4809 - Turn an assertion (that the number of handshakes received as a
4810 server is not < 1) into a warning. Fixes bug 4873; bugfix on
4812 - Format IPv4 addresses correctly in ADDRMAP events. (Previously,
4813 we had reversed them when the answer was cached.) Fixes bug
4814 5723; bugfix on 0.2.3.1-alpha.
4815 - Work correctly on Linux systems with accept4 support advertised in
4816 their headers, but without accept4 support in the kernel. Fix
4817 by murb. Fixes bug 5762; bugfix on 0.2.3.1-alpha.
4818 - When told to add a bridge with the same addr:port as a preexisting
4819 bridge but a different transport, change the transport as
4820 requested. Previously we would not notice the change. Fixes half
4821 of bug 5603; fix on 0.2.3.2-alpha.
4822 - Avoid a "double-reply" warning when replying to a SOCKS request
4823 with a parse error. Patch from Fabian Keil. Fixes bug 4108;
4824 bugfix on 0.2.3.4-alpha.
4825 - Fix a bug where a bridge authority crashes if it has seen no
4826 directory requests when it's time to write statistics to disk.
4827 Fixes bug 5891; bugfix on 0.2.3.6-alpha. Also fixes bug 5508 in
4829 - Don't try to open non-control listeners when DisableNetwork is set.
4830 Previously, we'd open all listeners, then immediately close them.
4831 Fixes bug 5604; bugfix on 0.2.3.9-alpha.
4832 - Don't abort the managed proxy protocol if the managed proxy
4833 sends us an unrecognized line; ignore it instead. Fixes bug
4834 5910; bugfix on 0.2.3.9-alpha.
4835 - Fix a compile warning in crypto.c when compiling with clang 3.1.
4836 Fixes bug 5969, bugfix on 0.2.3.9-alpha.
4837 - Fix a compilation issue on GNU Hurd, which doesn't have PATH_MAX.
4838 Fixes bug 5355; bugfix on 0.2.3.11-alpha.
4839 - Remove bogus definition of "_WIN32" from src/win32/orconfig.h, to
4840 unbreak the MSVC build. Fixes bug 5858; bugfix on 0.2.3.12-alpha.
4841 - Resolve numerous small warnings and build issues with MSVC. Resolves
4844 o Documentation fixes:
4845 - Improve the manual's documentation for the NT Service command-line
4846 options. Addresses ticket 3964.
4847 - Clarify SessionGroup documentation slightly; resolves ticket 5437.
4848 - Document the changes to the ORPort and DirPort options, and the
4849 fact that {OR/Dir}ListenAddress is now unnecessary (and
4850 therefore deprecated). Resolves ticket 5597.
4853 - Remove the torrc.bridge file: we don't use it for anything, and
4854 it had become badly desynchronized from torrc.sample. Resolves
4858 Changes in version 0.2.2.36 - 2012-05-24
4859 Tor 0.2.2.36 updates the addresses for two of the eight directory
4860 authorities, fixes some potential anonymity and security issues,
4861 and fixes several crash bugs.
4863 Tor 0.2.1.x has reached its end-of-life. Those Tor versions have many
4864 known flaws, and nobody should be using them. You should upgrade. If
4865 you're using a Linux or BSD and its packages are obsolete, stop using
4866 those packages and upgrade anyway.
4868 o Directory authority changes:
4869 - Change IP address for maatuska (v3 directory authority).
4870 - Change IP address for ides (v3 directory authority), and rename
4874 - When building or running with any version of OpenSSL earlier
4875 than 0.9.8s or 1.0.0f, disable SSLv3 support. These OpenSSL
4876 versions have a bug (CVE-2011-4576) in which their block cipher
4877 padding includes uninitialized data, potentially leaking sensitive
4878 information to any peer with whom they make a SSLv3 connection. Tor
4879 does not use SSL v3 by default, but a hostile client or server
4880 could force an SSLv3 connection in order to gain information that
4881 they shouldn't have been able to get. The best solution here is to
4882 upgrade to OpenSSL 0.9.8s or 1.0.0f (or later). But when building
4883 or running with a non-upgraded OpenSSL, we disable SSLv3 entirely
4884 to make sure that the bug can't happen.
4885 - Never use a bridge or a controller-supplied node as an exit, even
4886 if its exit policy allows it. Found by wanoskarnet. Fixes bug
4887 5342. Bugfix on 0.1.1.15-rc (for controller-purpose descriptors)
4888 and 0.2.0.3-alpha (for bridge-purpose descriptors).
4889 - Only build circuits if we have a sufficient threshold of the total
4890 descriptors that are marked in the consensus with the "Exit"
4891 flag. This mitigates an attack proposed by wanoskarnet, in which
4892 all of a client's bridges collude to restrict the exit nodes that
4893 the client knows about. Fixes bug 5343.
4894 - Provide controllers with a safer way to implement the cookie
4895 authentication mechanism. With the old method, if another locally
4896 running program could convince a controller that it was the Tor
4897 process, then that program could trick the controller into telling
4898 it the contents of an arbitrary 32-byte file. The new "SAFECOOKIE"
4899 authentication method uses a challenge-response approach to prevent
4900 this attack. Fixes bug 5185; implements proposal 193.
4903 - Avoid logging uninitialized data when unable to decode a hidden
4904 service descriptor cookie. Fixes bug 5647; bugfix on 0.2.1.5-alpha.
4905 - Avoid a client-side assertion failure when receiving an INTRODUCE2
4906 cell on a general purpose circuit. Fixes bug 5644; bugfix on
4908 - Fix builds when the path to sed, openssl, or sha1sum contains
4909 spaces, which is pretty common on Windows. Fixes bug 5065; bugfix
4911 - Correct our replacements for the timeradd() and timersub() functions
4912 on platforms that lack them (for example, Windows). The timersub()
4913 function is used when expiring circuits, while timeradd() is
4914 currently unused. Bug report and patch by Vektor. Fixes bug 4778;
4915 bugfix on 0.2.2.24-alpha.
4916 - Fix the SOCKET_OK test that we use to tell when socket
4917 creation fails so that it works on Win64. Fixes part of bug 4533;
4918 bugfix on 0.2.2.29-beta. Bug found by wanoskarnet.
4921 - Reject out-of-range times like 23:59:61 in parse_rfc1123_time().
4922 Fixes bug 5346; bugfix on 0.0.8pre3.
4923 - Make our number-parsing functions always treat too-large values
4924 as an error, even when those values exceed the width of the
4925 underlying type. Previously, if the caller provided these
4926 functions with minima or maxima set to the extreme values of the
4927 underlying integer type, these functions would return those
4928 values on overflow rather than treating overflow as an error.
4929 Fixes part of bug 5786; bugfix on 0.0.9.
4930 - Older Linux kernels erroneously respond to strange nmap behavior
4931 by having accept() return successfully with a zero-length
4932 socket. When this happens, just close the connection. Previously,
4933 we would try harder to learn the remote address: but there was
4934 no such remote address to learn, and our method for trying to
4935 learn it was incorrect. Fixes bugs 1240, 4745, and 4747. Bugfix
4936 on 0.1.0.3-rc. Reported and diagnosed by "r1eo".
4937 - Correct parsing of certain date types in parse_http_time().
4938 Without this patch, If-Modified-Since would behave
4939 incorrectly. Fixes bug 5346; bugfix on 0.2.0.2-alpha. Patch from
4940 Esteban Manchado Velázques.
4941 - Change the BridgePassword feature (part of the "bridge community"
4942 design, which is not yet implemented) to use a time-independent
4943 comparison. The old behavior might have allowed an adversary
4944 to use timing to guess the BridgePassword value. Fixes bug 5543;
4945 bugfix on 0.2.0.14-alpha.
4946 - Detect and reject certain misformed escape sequences in
4947 configuration values. Previously, these values would cause us
4948 to crash if received in a torrc file or over an authenticated
4949 control port. Bug found by Esteban Manchado Velázquez, and
4950 independently by Robert Connolly from Matta Consulting who further
4951 noted that it allows a post-authentication heap overflow. Patch
4952 by Alexander Schrijver. Fixes bugs 5090 and 5402 (CVE 2012-1668);
4953 bugfix on 0.2.0.16-alpha.
4954 - Fix a compile warning when using the --enable-openbsd-malloc
4955 configure option. Fixes bug 5340; bugfix on 0.2.0.20-rc.
4956 - During configure, detect when we're building with clang version
4957 3.0 or lower and disable the -Wnormalized=id and -Woverride-init
4958 CFLAGS. clang doesn't support them yet.
4959 - When sending an HTTP/1.1 proxy request, include a Host header.
4960 Fixes bug 5593; bugfix on 0.2.2.1-alpha.
4961 - Fix a NULL-pointer dereference on a badly formed SETCIRCUITPURPOSE
4962 command. Found by mikeyc. Fixes bug 5796; bugfix on 0.2.2.9-alpha.
4963 - If we hit the error case where routerlist_insert() replaces an
4964 existing (old) server descriptor, make sure to remove that
4965 server descriptor from the old_routers list. Fix related to bug
4966 1776. Bugfix on 0.2.2.18-alpha.
4968 o Minor bugfixes (documentation and log messages):
4969 - Fix a typo in a log message in rend_service_rendezvous_has_opened().
4970 Fixes bug 4856; bugfix on Tor 0.0.6.
4971 - Update "ClientOnly" man page entry to explain that there isn't
4972 really any point to messing with it. Resolves ticket 5005.
4973 - Document the GiveGuardFlagTo_CVE_2011_2768_VulnerableRelays
4974 directory authority option (introduced in Tor 0.2.2.34).
4975 - Downgrade the "We're missing a certificate" message from notice
4976 to info: people kept mistaking it for a real problem, whereas it
4977 is seldom the problem even when we are failing to bootstrap. Fixes
4978 bug 5067; bugfix on 0.2.0.10-alpha.
4979 - Correctly spell "connect" in a log message on failure to create a
4980 controlsocket. Fixes bug 4803; bugfix on 0.2.2.26-beta.
4981 - Clarify the behavior of MaxCircuitDirtiness with hidden service
4982 circuits. Fixes issue 5259.
4985 - Directory authorities now reject versions of Tor older than
4986 0.2.1.30, and Tor versions between 0.2.2.1-alpha and 0.2.2.20-alpha
4987 inclusive. These versions accounted for only a small fraction of
4988 the Tor network, and have numerous known security issues. Resolves
4990 - Update to the May 1 2012 Maxmind GeoLite Country database.
4993 - When sending or relaying a RELAY_EARLY cell, we used to convert
4994 it to a RELAY cell if the connection was using the v1 link
4995 protocol. This was a workaround for older versions of Tor, which
4996 didn't handle RELAY_EARLY cells properly. Now that all supported
4997 versions can handle RELAY_EARLY cells, and now that we're enforcing
4998 the "no RELAY_EXTEND commands except in RELAY_EARLY cells" rule,
4999 remove this workaround. Addresses bug 4786.
5002 Changes in version 0.2.3.15-alpha - 2012-04-30
5003 Tor 0.2.3.15-alpha fixes a variety of smaller bugs, including making
5004 the development branch build on Windows again.
5006 o Minor bugfixes (on 0.2.2.x and earlier):
5007 - Make sure that there are no unhandled pending TLS errors before
5008 reading from a TLS stream. We had checks in 0.1.0.3-rc, but
5009 lost them in 0.1.0.5-rc when we refactored read_to_buf_tls().
5010 Bugfix on 0.1.0.5-rc; fixes bug 4528.
5011 - Fix an assert that directory authorities could trigger on sighup
5012 during some configuration state transitions. We now don't treat
5013 it as a fatal error when the new descriptor we just generated in
5014 init_keys() isn't accepted. Fixes bug 4438; bugfix on 0.2.1.9-alpha.
5015 - After we pick a directory mirror, we would refuse to use it if
5016 it's in our ExcludeExitNodes list, resulting in mysterious failures
5017 to bootstrap for people who just wanted to avoid exiting from
5018 certain locations. Fixes bug 5623; bugfix on 0.2.2.25-alpha.
5019 - When building with --enable-static-tor on OpenBSD, do not
5020 erroneously attempt to link -lrt. Fixes bug 5103.
5022 o Minor bugfixes (on 0.2.3.x):
5023 - When Tor is built with kernel headers from a recent (last few
5024 years) Linux kernel, do not fail to run on older (pre-2.6.28
5025 Linux kernels). Fixes bug 5112; bugfix on 0.2.3.1-alpha.
5026 - Fix cross-compilation issues with mingw. Bugfixes on 0.2.3.6-alpha
5028 - Fix compilation with miniupnpc version 1.6; patch from
5029 Anthony G. Basile. Fixes bug 5434; bugfix on 0.2.3.12-alpha.
5030 - Fix compilation with MSVC, which had defined MS_WINDOWS. Bugfix
5031 on 0.2.3.13-alpha; found and fixed by Gisle Vanem.
5032 - Fix compilation on platforms without unistd.h, or where environ
5033 is defined in stdlib.h. Fixes bug 5704; bugfix on 0.2.3.13-alpha.
5036 - Directory authorities are now a little more lenient at accepting
5037 older router descriptors, or newer router descriptors that don't
5038 make big changes. This should help ameliorate past and future
5039 issues where routers think they have uploaded valid descriptors,
5040 but the authorities don't think so. Fix for ticket 2479.
5041 - Make the code that clients use to detect an address change be
5042 IPv6-aware, so that it won't fill clients' logs with error
5043 messages when trying to get the IPv4 address of an IPv6
5044 connection. Implements ticket 5537.
5047 - Remove the GiveGuardFlagTo_CVE_2011_2768_VulnerableRelays option;
5048 authorities needed to use it for a while to keep the network working
5049 as people upgraded to 0.2.1.31, 0.2.2.34, or 0.2.3.6-alpha, but
5050 that was six months ago. As of now, it should no longer be needed
5054 Changes in version 0.2.3.14-alpha - 2012-04-23
5055 Tor 0.2.3.14-alpha fixes yet more bugs to get us closer to a release
5056 candidate. It also dramatically speeds up AES: fast relays should
5057 consider switching to the newer OpenSSL library.
5059 o Directory authority changes:
5060 - Change IP address for ides (v3 directory authority), and rename
5064 - Avoid logging uninitialized data when unable to decode a hidden
5065 service descriptor cookie. Fixes bug 5647; bugfix on 0.2.1.5-alpha.
5066 - Avoid a client-side assertion failure when receiving an INTRODUCE2
5067 cell on a general purpose circuit. Fixes bug 5644; bugfix on
5069 - If authorities are unable to get a v2 consensus document from other
5070 directory authorities, they no longer fall back to fetching
5071 them from regular directory caches. Fixes bug 5635; bugfix on
5072 0.2.2.26-beta, where routers stopped downloading v2 consensus
5074 - When we start a Tor client with a normal consensus already cached,
5075 be willing to download a microdescriptor consensus. Fixes bug 4011;
5076 fix on 0.2.3.1-alpha.
5078 o Major features (performance):
5079 - When built to use OpenSSL 1.0.1, and built for an x86 or x86_64
5080 instruction set, take advantage of OpenSSL's AESNI, bitsliced, or
5081 vectorized AES implementations as appropriate. These can be much,
5082 much faster than other AES implementations.
5084 o Minor bugfixes (0.2.2.x and earlier):
5085 - Don't launch more than 10 service-side introduction-point circuits
5086 for a hidden service in five minutes. Previously, we would consider
5087 launching more introduction-point circuits if at least one second
5088 had passed without any introduction-point circuits failing. Fixes
5089 bug 4607; bugfix on 0.0.7pre1.
5090 - Change the BridgePassword feature (part of the "bridge community"
5091 design, which is not yet implemented) to use a time-independent
5092 comparison. The old behavior might have allowed an adversary
5093 to use timing to guess the BridgePassword value. Fixes bug 5543;
5094 bugfix on 0.2.0.14-alpha.
5095 - Enforce correct return behavior of tor_vsscanf() when the '%%'
5096 pattern is used. Fixes bug 5558. Bugfix on 0.2.1.13.
5097 - When sending an HTTP/1.1 proxy request, include a Host header.
5098 Fixes bug 5593; bugfix on 0.2.2.1-alpha.
5099 - Don't log that we have "decided to publish new relay descriptor"
5100 unless we are actually publishing a descriptor. Fixes bug 3942;
5101 bugfix on 0.2.2.28-beta.
5103 o Minor bugfixes (0.2.3.x):
5104 - Fix a bug where a bridge authority crashes (on a failed assert)
5105 if it has seen no directory requests when it's time to write
5106 statistics to disk. Fixes bug 5508. Bugfix on 0.2.3.6-alpha.
5107 - Fix bug stomping on ORPort option NoListen and ignoring option
5108 NoAdvertise. Fixes bug 5151; bugfix on 0.2.3.9-alpha.
5109 - In the testsuite, provide a large enough buffer in the tor_sscanf
5110 unit test. Otherwise we'd overrun that buffer and crash during
5111 the unit tests. Found by weasel. Fixes bug 5449; bugfix on
5113 - Make sure we create the keys directory if it doesn't exist and we're
5114 about to store the dynamic Diffie-Hellman parameters. Fixes bug
5115 5572; bugfix on 0.2.3.13-alpha.
5116 - Fix a small memory leak when trying to decode incorrect base16
5117 authenticator during SAFECOOKIE authentication. Found by
5118 Coverity Scan. Fixes CID 507. Bugfix on 0.2.3.13-alpha.
5121 - Add more information to a log statement that might help track down
5122 bug 4091. If you're seeing "Bug: tor_addr_is_internal() called with a
5123 non-IP address" messages (or any Bug messages, for that matter!),
5124 please let us know about it.
5125 - Relays now understand an IPv6 address when they get one from a
5126 directory server. Resolves ticket 4875.
5127 - Resolve IPv6 addresses in bridge and entry statistics to country
5128 code "??" which means we at least count them. Resolves ticket 5053;
5129 improves on 0.2.3.9-alpha.
5130 - Update to the April 3 2012 Maxmind GeoLite Country database.
5131 - Begin a doc/state-contents.txt file to explain the contents of
5132 the Tor state file. Fixes bug 2987.
5134 o Default torrc changes:
5135 - Stop listing "socksport 9050" in torrc.sample. We open a socks
5136 port on 9050 by default anyway, so this should not change anything
5138 - Stop mentioning the deprecated *ListenAddress options in
5139 torrc.sample. Fixes bug 5438.
5140 - Document unit of bandwidth related options in sample torrc.
5144 - The "torify" script no longer supports the "tsocks" socksifier
5145 tool, since tsocks doesn't support DNS and UDP right for Tor.
5146 Everyone should be using torsocks instead. Fixes bugs 3530 and
5147 5180. Based on a patch by "ugh".
5150 - Change the symmetric cipher interface so that creating and
5151 initializing a stream cipher are no longer separate functions.
5152 - Remove all internal support for unpadded RSA. We never used it, and
5153 it would be a bad idea to start.
5156 Changes in version 0.2.3.13-alpha - 2012-03-26
5157 Tor 0.2.3.13-alpha fixes a variety of stability and correctness bugs
5158 in managed pluggable transports, as well as providing other cleanups
5159 that get us closer to a release candidate.
5161 o Directory authority changes:
5162 - Change IP address for maatuska (v3 directory authority).
5165 - Provide controllers with a safer way to implement the cookie
5166 authentication mechanism. With the old method, if another locally
5167 running program could convince a controller that it was the Tor
5168 process, then that program could trick the controller into telling
5169 it the contents of an arbitrary 32-byte file. The new "SAFECOOKIE"
5170 authentication method uses a challenge-response approach to prevent
5171 this attack. Fixes bug 5185, implements proposal 193.
5172 - Never use a bridge or a controller-supplied node as an exit, even
5173 if its exit policy allows it. Found by wanoskarnet. Fixes bug
5174 5342. Bugfix on 0.1.1.15-rc (for controller-purpose descriptors)
5175 and 0.2.0.3-alpha (for bridge-purpose descriptors).
5176 - Only build circuits if we have a sufficient threshold of the total
5177 descriptors that are marked in the consensus with the "Exit"
5178 flag. This mitigates an attack proposed by wanoskarnet, in which
5179 all of a client's bridges collude to restrict the exit nodes that
5180 the client knows about. Fixes bug 5343.
5182 o Major bugfixes (on Tor 0.2.3.x):
5183 - Avoid an assert when managed proxies like obfsproxy are configured,
5184 and we receive HUP signals or setconf attempts too rapidly. This
5185 situation happens most commonly when Vidalia tries to attach to
5186 Tor or tries to configure the Tor it's attached to. Fixes bug 5084;
5187 bugfix on 0.2.3.6-alpha.
5188 - Fix a relay-side pluggable transports bug where managed proxies were
5189 unreachable from the Internet, because Tor asked them to bind on
5190 localhost. Fixes bug 4725; bugfix on 0.2.3.9-alpha.
5191 - Stop discarding command-line arguments when TestingTorNetwork
5192 is set. Discovered by Kevin Bauer. Fixes bug 5373; bugfix on
5193 0.2.3.9-alpha, where task 4552 added support for two layers of
5195 - Resume allowing the unit tests to run in gdb. This was accidentally
5196 made impossible when the DisableDebuggerAttachment option was
5197 introduced. Fixes bug 5448; bugfix on 0.2.3.9-alpha.
5198 - Resume building with nat-pmp support. Fixes bug 4955; bugfix on
5199 0.2.3.11-alpha. Reported by Anthony G. Basile.
5201 o Minor bugfixes (on 0.2.2.x and earlier):
5202 - Ensure we don't cannibalize circuits that are longer than three hops
5203 already, so we don't end up making circuits with 5 or more
5204 hops. Patch contributed by wanoskarnet. Fixes bug 5231; bugfix on
5205 0.1.0.1-rc which introduced cannibalization.
5206 - Detect and reject certain misformed escape sequences in
5207 configuration values. Previously, these values would cause us
5208 to crash if received in a torrc file or over an authenticated
5209 control port. Bug found by Esteban Manchado Velázquez, and
5210 independently by Robert Connolly from Matta Consulting who further
5211 noted that it allows a post-authentication heap overflow. Patch
5212 by Alexander Schrijver. Fixes bugs 5090 and 5402 (CVE 2012-1668);
5213 bugfix on 0.2.0.16-alpha.
5214 - Fix a compile warning when using the --enable-openbsd-malloc
5215 configure option. Fixes bug 5340; bugfix on 0.2.0.20-rc.
5216 - Directory caches no longer refuse to clean out descriptors because
5217 of missing v2 networkstatus documents, unless they're configured
5218 to retrieve v2 networkstatus documents. Fixes bug 4838; bugfix on
5219 0.2.2.26-beta. Patch by Daniel Bryg.
5220 - Update to the latest version of the tinytest unit testing framework.
5221 This includes a couple of bugfixes that can be relevant for
5222 running forked unit tests on Windows, and removes all reserved
5225 o Minor bugfixes (on 0.2.3.x):
5226 - On a failed pipe() call, don't leak file descriptors. Fixes bug
5227 4296; bugfix on 0.2.3.1-alpha.
5228 - Spec conformance: on a v3 handshake, do not send a NETINFO cell
5229 until after we have received a CERTS cell. Fixes bug 4361; bugfix
5230 on 0.2.3.6-alpha. Patch by "frosty".
5231 - When binding to an IPv6 address, set the IPV6_V6ONLY socket
5232 option, so that the IP stack doesn't decide to use it for IPv4
5233 too. Fixes bug 4760; bugfix on 0.2.3.9-alpha.
5234 - Ensure that variables set in Tor's environment cannot override
5235 environment variables that Tor passes to a managed
5236 pluggable-transport proxy. Previously, Tor would pass every
5237 variable in its environment to managed proxies along with the new
5238 ones, in such a way that on many operating systems, the inherited
5239 environment variables would override those which Tor tried to
5240 explicitly set. Bugfix on 0.2.3.12-alpha for most Unixoid systems;
5241 bugfix on 0.2.3.9-alpha for Windows.
5244 - A wide variety of new unit tests by Esteban Manchado Velázquez.
5245 - Shorten links in the tor-exit-notice file. Patch by Christian Kujau.
5246 - Update to the March 6 2012 Maxmind GeoLite Country database.
5249 Changes in version 0.2.3.12-alpha - 2012-02-13
5250 Tor 0.2.3.12-alpha lets fast exit relays scale better, allows clients
5251 to use bridges that run Tor 0.2.2.x, and resolves several big bugs
5252 when Tor is configured to use a pluggable transport like obfsproxy.
5255 - Fix builds when the path to sed, openssl, or sha1sum contains
5256 spaces, which is pretty common on Windows. Fixes bug 5065; bugfix
5258 - Set the SO_REUSEADDR socket option before we call bind() on outgoing
5259 connections. This change should allow busy exit relays to stop
5260 running out of available sockets as quickly. Fixes bug 4950;
5261 bugfix on 0.2.2.26-beta.
5262 - Allow 0.2.3.x clients to use 0.2.2.x bridges. Previously the client
5263 would ask the bridge for microdescriptors, which are only supported
5264 in 0.2.3.x, and then fail to bootstrap when it didn't get the
5265 answers it wanted. Fixes bug 4013; bugfix on 0.2.3.2-alpha.
5266 - Properly set up obfsproxy's environment when in managed mode. The
5267 Tor Browser Bundle needs LD_LIBRARY_PATH to be passed to obfsproxy,
5268 and when you run your Tor as a daemon, there's no HOME. Fixes bugs
5269 5076 and 5082; bugfix on 0.2.3.6-alpha.
5272 - Use the dead_strip option when building Tor on OS X. This reduces
5273 binary size by almost 19% when linking openssl and libevent
5274 statically, which we do for Tor Browser Bundle.
5275 - Fix broken URLs in the sample torrc file, and tell readers about
5276 the OutboundBindAddress, ExitPolicyRejectPrivate, and
5277 PublishServerDescriptor options. Addresses bug 4652.
5278 - Update to the February 7 2012 Maxmind GeoLite Country database.
5281 - Downgrade the "We're missing a certificate" message from notice
5282 to info: people kept mistaking it for a real problem, whereas it
5283 is seldom the problem even when we are failing to bootstrap. Fixes
5284 bug 5067; bugfix on 0.2.0.10-alpha.
5285 - Don't put "TOR_PT_EXTENDED_SERVER_PORT=127.0.0.1:4200" in a
5286 managed pluggable transport server proxy's environment.
5287 Previously, we would put it there, even though Tor doesn't
5288 implement an 'extended server port' yet, and even though Tor
5289 almost certainly isn't listening at that address. For now, we set
5290 it to an empty string to avoid crashing older obfsproxies. Bugfix
5292 - Log the heartbeat message every HeartbeatPeriod seconds, not every
5293 HeartbeatPeriod + 1 seconds. Fixes bug 4942; bugfix on
5294 0.2.3.1-alpha. Bug reported by Scott Bennett.
5295 - Calculate absolute paths correctly on Windows. Fixes bug 4973;
5296 bugfix on 0.2.3.11-alpha.
5297 - Update "ClientOnly" man page entry to explain that there isn't
5298 really any point to messing with it. Resolves ticket 5005.
5299 - Use the correct CVE number for CVE-2011-4576 in our comments and
5300 log messages. Found by "fermenthor". Resolves bug 5066; bugfix on
5303 o Code simplifications and refactoring:
5304 - Use the _WIN32 macro throughout our code to detect Windows.
5305 (Previously we had used the obsolete 'WIN32' and the idiosyncratic
5309 Changes in version 0.2.3.11-alpha - 2012-01-22
5310 Tor 0.2.3.11-alpha marks feature-freeze for the 0.2.3 tree. It deploys
5311 the last step of the plan to limit maximum circuit length, includes
5312 a wide variety of hidden service performance and correctness fixes,
5313 works around an OpenSSL security flaw if your distro is too stubborn
5314 to upgrade, and fixes a bunch of smaller issues.
5317 - Now that Tor 0.2.0.x is completely deprecated, enable the final
5318 part of "Proposal 110: Avoiding infinite length circuits" by
5319 refusing all circuit-extend requests that do not use a relay_early
5320 cell. This change helps Tor resist a class of denial-of-service
5321 attacks by limiting the maximum circuit length.
5322 - Adjust the number of introduction points that a hidden service
5323 will try to maintain based on how long its introduction points
5324 remain in use and how many introductions they handle. Fixes
5326 - Try to use system facilities for enumerating local interface
5327 addresses, before falling back to our old approach (which was
5328 binding a UDP socket, and calling getsockname() on it). That
5329 approach was scaring OS X users whose draconian firewall
5330 software warned about binding to UDP sockets, regardless of
5331 whether packets were sent. Now we try to use getifaddrs(),
5332 SIOCGIFCONF, or GetAdaptersAddresses(), depending on what the
5333 system supports. Resolves ticket 1827.
5335 o Major security workaround:
5336 - When building or running with any version of OpenSSL earlier
5337 than 0.9.8s or 1.0.0f, disable SSLv3 support. These OpenSSL
5338 versions have a bug (CVE-2011-4576) in which their block cipher
5339 padding includes uninitialized data, potentially leaking sensitive
5340 information to any peer with whom they make a SSLv3 connection. Tor
5341 does not use SSL v3 by default, but a hostile client or server
5342 could force an SSLv3 connection in order to gain information that
5343 they shouldn't have been able to get. The best solution here is to
5344 upgrade to OpenSSL 0.9.8s or 1.0.0f (or later). But when building
5345 or running with a non-upgraded OpenSSL, we disable SSLv3 entirely
5346 to make sure that the bug can't happen.
5349 - Fix the SOCKET_OK test that we use to tell when socket
5350 creation fails so that it works on Win64. Fixes part of bug 4533;
5351 bugfix on 0.2.2.29-beta. Bug found by wanoskarnet.
5352 - Correct our replacements for the timeradd() and timersub() functions
5353 on platforms that lack them (for example, Windows). The timersub()
5354 function is used when expiring circuits, while timeradd() is
5355 currently unused. Bug report and patch by Vektor. Fixes bug 4778;
5356 bugfix on 0.2.2.24-alpha and 0.2.3.1-alpha.
5357 - Do not use OpenSSL 1.0.0's counter mode: it has a critical bug
5358 that was fixed in OpenSSL 1.0.0a. We test for the counter mode
5359 bug at runtime, not compile time, because some distributions hack
5360 their OpenSSL to mis-report its version. Fixes bug 4779; bugfix
5361 on 0.2.3.9-alpha. Found by Pascal.
5363 o Minor features (controller):
5364 - Use absolute path names when reporting the torrc filename in the
5365 control protocol, so a controller can more easily find the torrc
5366 file. Resolves bug 1101.
5367 - Extend the control protocol to report flags that control a circuit's
5368 path selection in CIRC events and in replies to 'GETINFO
5369 circuit-status'. Implements part of ticket 2411.
5370 - Extend the control protocol to report the hidden service address
5371 and current state of a hidden-service-related circuit in CIRC
5372 events and in replies to 'GETINFO circuit-status'. Implements part
5374 - When reporting the path to the cookie file to the controller,
5375 give an absolute path. Resolves ticket 4881.
5376 - Allow controllers to request an event notification whenever a
5377 circuit is cannibalized or its purpose is changed. Implements
5378 part of ticket 3457.
5379 - Include the creation time of a circuit in CIRC and CIRC2
5380 control-port events and the list produced by the 'GETINFO
5381 circuit-status' control-port command.
5383 o Minor features (directory authorities):
5384 - Directory authorities now reject versions of Tor older than
5385 0.2.1.30, and Tor versions between 0.2.2.1-alpha and 0.2.2.20-alpha
5386 inclusive. These versions accounted for only a small fraction of
5387 the Tor network, and have numerous known security issues. Resolves
5389 - Authority operators can now vote for all relays in a given
5390 set of countries to be BadDir/BadExit/Invalid/Rejected.
5391 - Provide two consensus parameters (FastFlagMinThreshold and
5392 FastFlagMaxThreshold) to control the range of allowable bandwidths
5393 for the Fast directory flag. These allow authorities to run
5394 experiments on appropriate requirements for being a "Fast" node.
5395 The AuthDirFastGuarantee config value still applies. Implements
5397 - Document the GiveGuardFlagTo_CVE_2011_2768_VulnerableRelays
5398 directory authority option (introduced in Tor 0.2.2.34).
5400 o Minor features (other):
5401 - Don't disable the DirPort when we cannot exceed our AccountingMax
5402 limit during this interval because the effective bandwidthrate is
5403 low enough. This is useful in a situation where AccountMax is only
5404 used as an additional safeguard or to provide statistics.
5405 - Prepend an informative header to generated dynamic_dh_params files.
5406 - If EntryNodes are given, but UseEntryGuards is set to 0, warn that
5407 EntryNodes will have no effect. Resolves issue 2571.
5408 - Log more useful messages when we fail to disable debugger
5410 - Log which authority we're missing votes from when we go to fetch
5411 them from the other auths.
5412 - Log (at debug level) whenever a circuit's purpose is changed.
5413 - Add missing documentation for the MaxClientCircuitsPending,
5414 UseMicrodescriptors, UserspaceIOCPBuffers, and
5415 _UseFilteringSSLBufferevents options, all introduced during
5417 - Update to the January 3 2012 Maxmind GeoLite Country database.
5419 o Minor bugfixes (hidden services):
5420 - Don't close hidden service client circuits which have almost
5421 finished connecting to their destination when they reach
5422 the normal circuit-build timeout. Previously, we would close
5423 introduction circuits which are waiting for an acknowledgement
5424 from the introduction point, and rendezvous circuits which have
5425 been specified in an INTRODUCE1 cell sent to a hidden service,
5426 after the normal CBT. Now, we mark them as 'timed out', and launch
5427 another rendezvous attempt in parallel. This behavior change can
5428 be disabled using the new CloseHSClientCircuitsImmediatelyOnTimeout
5429 option. Fixes part of bug 1297; bugfix on 0.2.2.2-alpha.
5430 - Don't close hidden-service-side rendezvous circuits when they
5431 reach the normal circuit-build timeout. This behaviour change can
5432 be disabled using the new
5433 CloseHSServiceRendCircuitsImmediatelyOnTimeout option. Fixes the
5434 remaining part of bug 1297; bugfix on 0.2.2.2-alpha.
5435 - Make sure we never mark the wrong rendezvous circuit as having
5436 had its introduction cell acknowleged by the introduction-point
5437 relay. Previously, when we received an INTRODUCE_ACK cell on a
5438 client-side hidden-service introduction circuit, we might have
5439 marked a rendezvous circuit other than the one we specified in
5440 the INTRODUCE1 cell as INTRO_ACKED, which would have produced
5441 a warning message and interfered with the hidden service
5442 connection-establishment process. Fixes bug 4759; bugfix on
5443 0.2.3.3-alpha, when we added the stream-isolation feature which
5444 might cause Tor to open multiple rendezvous circuits for the same
5446 - Don't trigger an assertion failure when we mark a new client-side
5447 hidden-service introduction circuit for close during the process
5448 of creating it. Fixes bug 4796; bugfix on 0.2.3.6-alpha. Reported
5451 o Minor bugfixes (log messages):
5452 - Correctly spell "connect" in a log message on failure to create a
5453 controlsocket. Fixes bug 4803; bugfix on 0.2.2.26-beta and
5455 - Fix a typo in a log message in rend_service_rendezvous_has_opened().
5456 Fixes bug 4856; bugfix on Tor 0.0.6.
5457 - Fix the log message describing how we work around discovering
5458 that our version is the ill-fated OpenSSL 0.9.8l. Fixes bug
5459 4837; bugfix on 0.2.2.9-alpha.
5460 - When logging about a disallowed .exit name, do not also call it
5461 an "invalid onion address". Fixes bug 3325; bugfix on 0.2.2.9-alpha.
5463 o Minor bugfixes (build fixes):
5464 - During configure, detect when we're building with clang version
5465 3.0 or lower and disable the -Wnormalized=id and -Woverride-init
5466 CFLAGS. clang doesn't support them yet.
5467 - During configure, search for library containing cos function as
5468 libm lives in libcore on some platforms (BeOS/Haiku). Linking
5469 against libm was hard-coded before. Fixes the first part of bug
5470 4727; bugfix on 0.2.2.2-alpha. Patch and analysis by Martin Hebnes
5472 - Detect attempts to build Tor on (as yet hypothetical) versions
5473 of Windows where sizeof(intptr_t) != sizeof(SOCKET). Partial
5474 fix for bug 4533. Bugfix on 0.2.2.28-beta.
5475 - Preprocessor directives should not be put inside the arguments
5476 of a macro. This would break compilation with GCC releases prior
5477 to version 3.3. We would never recommend such an old GCC version,
5478 but it is apparently required for binary compatibility on some
5479 platforms (namely, certain builds of Haiku). Fixes the other part
5480 of bug 4727; bugfix on 0.2.3.3-alpha. Patch and analysis by Martin
5483 o Minor bugfixes (other):
5484 - Older Linux kernels erroneously respond to strange nmap behavior
5485 by having accept() return successfully with a zero-length
5486 socket. When this happens, just close the connection. Previously,
5487 we would try harder to learn the remote address: but there was
5488 no such remote address to learn, and our method for trying to
5489 learn it was incorrect. Fixes bugs 1240, 4745, and 4747. Bugfix
5490 on 0.1.0.3-rc. Reported and diagnosed by "r1eo".
5491 - Fix null-pointer access that could occur if TLS allocation failed.
5492 Fixes bug 4531; bugfix on 0.2.0.20-rc. Found by "troll_un". This was
5493 erroneously listed as fixed in 0.2.3.9-alpha, but the fix had
5494 accidentally been reverted.
5495 - Fix our implementation of crypto_random_hostname() so it can't
5496 overflow on ridiculously large inputs. (No Tor version has ever
5497 provided this kind of bad inputs, but let's be correct in depth.)
5498 Fixes bug 4413; bugfix on 0.2.2.9-alpha. Fix by Stephen Palmateer.
5499 - Find more places in the code that should have been testing for
5500 invalid sockets using the SOCKET_OK macro. Required for a fix
5501 for bug 4533. Bugfix on 0.2.2.28-beta.
5502 - Fix an assertion failure when, while running with bufferevents, a
5503 connection finishes connecting after it is marked for close, but
5504 before it is closed. Fixes bug 4697; bugfix on 0.2.3.1-alpha.
5505 - test_util_spawn_background_ok() hardcoded the expected value
5506 for ENOENT to 2. This isn't portable as error numbers are
5507 platform specific, and particularly the hurd has ENOENT at
5508 0x40000002. Construct expected string at runtime, using the correct
5509 value for ENOENT. Fixes bug 4733; bugfix on 0.2.3.1-alpha.
5510 - Reject attempts to disable DisableDebuggerAttachment while Tor is
5511 running. Fixes bug 4650; bugfix on 0.2.3.9-alpha.
5512 - Use an appropriate-width type for sockets in tor-fw-helper on
5513 win64. Fixes bug 1983 at last. Bugfix on 0.2.3.9-alpha.
5516 - When sending or relaying a RELAY_EARLY cell, we used to convert
5517 it to a RELAY cell if the connection was using the v1 link
5518 protocol. This was a workaround for older versions of Tor, which
5519 didn't handle RELAY_EARLY cells properly. Now that all supported
5520 versions can handle RELAY_EARLY cells, and now that we're enforcing
5521 the "no RELAY_EXTEND commands except in RELAY_EARLY cells" rule,
5522 remove this workaround. Addresses bug 4786.
5524 o Code simplifications and refactoring:
5525 - Use OpenSSL's built-in SSL_state_string_long() instead of our
5526 own homebrewed ssl_state_to_string() replacement. Patch from
5527 Emile Snyder. Fixes bug 4653.
5528 - Use macros to indicate OpenSSL versions, so we don't need to worry
5529 about accidental hexadecimal bit shifts.
5530 - Remove some workaround code for OpenSSL 0.9.6 (which is no longer
5532 - Convert more instances of tor_snprintf+tor_strdup into tor_asprintf.
5533 - Use the smartlist_add_asprintf() alias more consistently.
5534 - Use a TOR_INVALID_SOCKET macro when initializing a socket to an
5535 invalid value, rather than just -1.
5536 - Rename a handful of old identifiers, mostly related to crypto
5537 structures and crypto functions. By convention, our "create an
5538 object" functions are called "type_new()", our "free an object"
5539 functions are called "type_free()", and our types indicate that
5540 they are types only with a final "_t". But a handful of older
5541 types and functions broke these rules, with function names like
5542 "type_create" or "subsystem_op_type", or with type names like
5546 Changes in version 0.2.3.10-alpha - 2011-12-16
5547 Tor 0.2.3.10-alpha fixes a critical heap-overflow security issue in
5548 Tor's buffers code. Absolutely everybody should upgrade.
5550 The bug relied on an incorrect calculation when making data continuous
5551 in one of our IO buffers, if the first chunk of the buffer was
5552 misaligned by just the wrong amount. The miscalculation would allow an
5553 attacker to overflow a piece of heap-allocated memory. To mount this
5554 attack, the attacker would need to either open a SOCKS connection to
5555 Tor's SocksPort (usually restricted to localhost), or target a Tor
5556 instance configured to make its connections through a SOCKS proxy
5557 (which Tor does not do by default).
5559 Good security practice requires that all heap-overflow bugs should be
5560 presumed to be exploitable until proven otherwise, so we are treating
5561 this as a potential code execution attack. Please upgrade immediately!
5562 This bug does not affect bufferevents-based builds of Tor. Special
5563 thanks to "Vektor" for reporting this issue to us!
5565 This release also contains a few minor bugfixes for issues discovered
5569 - Fix a heap overflow bug that could occur when trying to pull
5570 data into the first chunk of a buffer, when that chunk had
5571 already had some data drained from it. Fixes CVE-2011-2778;
5572 bugfix on 0.2.0.16-alpha. Reported by "Vektor".
5575 - If we can't attach streams to a rendezvous circuit when we
5576 finish connecting to a hidden service, clear the rendezvous
5577 circuit's stream-isolation state and try to attach streams
5578 again. Previously, we cleared rendezvous circuits' isolation
5579 state either too early (if they were freshly built) or not at all
5580 (if they had been built earlier and were cannibalized). Bugfix on
5581 0.2.3.3-alpha; fixes bug 4655.
5582 - Fix compilation of the libnatpmp helper on non-Windows. Bugfix on
5583 0.2.3.9-alpha; fixes bug 4691. Reported by Anthony G. Basile.
5584 - Fix an assertion failure when a relay with accounting enabled
5585 starts up while dormant. Fixes bug 4702; bugfix on 0.2.3.9-alpha.
5588 - Update to the December 6 2011 Maxmind GeoLite Country database.
5591 Changes in version 0.2.2.35 - 2011-12-16
5592 Tor 0.2.2.35 fixes a critical heap-overflow security issue in Tor's
5593 buffers code. Absolutely everybody should upgrade.
5595 The bug relied on an incorrect calculation when making data continuous
5596 in one of our IO buffers, if the first chunk of the buffer was
5597 misaligned by just the wrong amount. The miscalculation would allow an
5598 attacker to overflow a piece of heap-allocated memory. To mount this
5599 attack, the attacker would need to either open a SOCKS connection to
5600 Tor's SocksPort (usually restricted to localhost), or target a Tor
5601 instance configured to make its connections through a SOCKS proxy
5602 (which Tor does not do by default).
5604 Good security practice requires that all heap-overflow bugs should be
5605 presumed to be exploitable until proven otherwise, so we are treating
5606 this as a potential code execution attack. Please upgrade immediately!
5607 This bug does not affect bufferevents-based builds of Tor. Special
5608 thanks to "Vektor" for reporting this issue to us!
5610 Tor 0.2.2.35 also fixes several bugs in previous versions, including
5611 crash bugs for unusual configurations, and a long-term bug that
5612 would prevent Tor from starting on Windows machines with draconian
5615 With this release, we remind everyone that 0.2.0.x has reached its
5616 formal end-of-life. Those Tor versions have many known flaws, and
5617 nobody should be using them. You should upgrade -- ideally to the
5618 0.2.2.x series. If you're using a Linux or BSD and its packages are
5619 obsolete, stop using those packages and upgrade anyway.
5621 The Tor 0.2.1.x series is also approaching its end-of-life: it will no
5622 longer receive support after some time in early 2012.
5625 - Fix a heap overflow bug that could occur when trying to pull
5626 data into the first chunk of a buffer, when that chunk had
5627 already had some data drained from it. Fixes CVE-2011-2778;
5628 bugfix on 0.2.0.16-alpha. Reported by "Vektor".
5629 - Initialize Libevent with the EVENT_BASE_FLAG_NOLOCK flag enabled, so
5630 that it doesn't attempt to allocate a socketpair. This could cause
5631 some problems on Windows systems with overzealous firewalls. Fix for
5632 bug 4457; workaround for Libevent versions 2.0.1-alpha through
5634 - If we mark an OR connection for close based on a cell we process,
5635 don't process any further cells on it. We already avoid further
5636 reads on marked-for-close connections, but now we also discard the
5637 cells we'd already read. Fixes bug 4299; bugfix on 0.2.0.10-alpha,
5638 which was the first version where we might mark a connection for
5639 close based on processing a cell on it.
5640 - Correctly sanity-check that we don't underflow on a memory
5641 allocation (and then assert) for hidden service introduction
5642 point decryption. Bug discovered by Dan Rosenberg. Fixes bug 4410;
5643 bugfix on 0.2.1.5-alpha.
5644 - Fix a memory leak when we check whether a hidden service
5645 descriptor has any usable introduction points left. Fixes bug
5646 4424. Bugfix on 0.2.2.25-alpha.
5647 - Don't crash when we're running as a relay and don't have a GeoIP
5648 file. Bugfix on 0.2.2.34; fixes bug 4340. This backports a fix
5649 we've had in the 0.2.3.x branch already.
5650 - When running as a client, do not print a misleading (and plain
5651 wrong) log message that we're collecting "directory request"
5652 statistics: clients don't collect statistics. Also don't create a
5653 useless (because empty) stats file in the stats/ directory. Fixes
5654 bug 4353; bugfix on 0.2.2.34.
5657 - Detect failure to initialize Libevent. This fix provides better
5658 detection for future instances of bug 4457.
5659 - Avoid frequent calls to the fairly expensive cull_wedged_cpuworkers
5660 function. This was eating up hideously large amounts of time on some
5661 busy servers. Fixes bug 4518; bugfix on 0.0.9.8.
5662 - Resolve an integer overflow bug in smartlist_ensure_capacity().
5663 Fixes bug 4230; bugfix on Tor 0.1.0.1-rc. Based on a patch by
5665 - Don't warn about unused log_mutex in log.c when building with
5666 --disable-threads using a recent GCC. Fixes bug 4437; bugfix on
5667 0.1.0.6-rc which introduced --disable-threads.
5668 - When configuring, starting, or stopping an NT service, stop
5669 immediately after the service configuration attempt has succeeded
5670 or failed. Fixes bug 3963; bugfix on 0.2.0.7-alpha.
5671 - When sending a NETINFO cell, include the original address
5672 received for the other side, not its canonical address. Found
5673 by "troll_un"; fixes bug 4349; bugfix on 0.2.0.10-alpha.
5674 - Fix a typo in a hibernation-related log message. Fixes bug 4331;
5675 bugfix on 0.2.2.23-alpha; found by "tmpname0901".
5676 - Fix a memory leak in launch_direct_bridge_descriptor_fetch() that
5677 occurred when a client tried to fetch a descriptor for a bridge
5678 in ExcludeNodes. Fixes bug 4383; bugfix on 0.2.2.25-alpha.
5679 - Backport fixes for a pair of compilation warnings on Windows.
5680 Fixes bug 4521; bugfix on 0.2.2.28-beta and on 0.2.2.29-beta.
5681 - If we had ever tried to call tor_addr_to_str on an address of
5682 unknown type, we would have done a strdup on an uninitialized
5683 buffer. Now we won't. Fixes bug 4529; bugfix on 0.2.1.3-alpha.
5684 Reported by "troll_un".
5685 - Correctly detect and handle transient lookup failures from
5686 tor_addr_lookup. Fixes bug 4530; bugfix on 0.2.1.5-alpha.
5687 Reported by "troll_un".
5688 - Fix null-pointer access that could occur if TLS allocation failed.
5689 Fixes bug 4531; bugfix on 0.2.0.20-rc. Found by "troll_un".
5690 - Use tor_socket_t type for listener argument to accept(). Fixes bug
5691 4535; bugfix on 0.2.2.28-beta. Found by "troll_un".
5694 - Add two new config options for directory authorities:
5695 AuthDirFastGuarantee sets a bandwidth threshold for guaranteeing the
5696 Fast flag, and AuthDirGuardBWGuarantee sets a bandwidth threshold
5697 that is always sufficient to satisfy the bandwidth requirement for
5698 the Guard flag. Now it will be easier for researchers to simulate
5699 Tor networks with different values. Resolves ticket 4484.
5700 - When Tor ignores a hidden service specified in its configuration,
5701 include the hidden service's directory in the warning message.
5702 Previously, we would only tell the user that some hidden service
5703 was ignored. Bugfix on 0.0.6; fixes bug 4426.
5704 - Update to the December 6 2011 Maxmind GeoLite Country database.
5706 o Packaging changes:
5707 - Make it easier to automate expert package builds on Windows,
5708 by removing an absolute path from makensis.exe command.
5711 Changes in version 0.2.1.32 - 2011-12-16
5712 Tor 0.2.1.32 backports important security and privacy fixes for
5713 oldstable. This release is intended only for package maintainers and
5714 others who cannot use the 0.2.2 stable series. All others should be
5715 using Tor 0.2.2.x or newer.
5717 The Tor 0.2.1.x series will reach formal end-of-life some time in
5718 early 2012; we will stop releasing patches for it then.
5720 o Major bugfixes (also included in 0.2.2.x):
5721 - Correctly sanity-check that we don't underflow on a memory
5722 allocation (and then assert) for hidden service introduction
5723 point decryption. Bug discovered by Dan Rosenberg. Fixes bug 4410;
5724 bugfix on 0.2.1.5-alpha.
5725 - Fix a heap overflow bug that could occur when trying to pull
5726 data into the first chunk of a buffer, when that chunk had
5727 already had some data drained from it. Fixes CVE-2011-2778;
5728 bugfix on 0.2.0.16-alpha. Reported by "Vektor".
5731 - Update to the December 6 2011 Maxmind GeoLite Country database.
5734 Changes in version 0.2.3.9-alpha - 2011-12-08
5735 Tor 0.2.3.9-alpha introduces initial IPv6 support for bridges, adds
5736 a "DisableNetwork" security feature that bundles can use to avoid
5737 touching the network until bridges are configured, moves forward on
5738 the pluggable transport design, fixes a flaw in the hidden service
5739 design that unnecessarily prevented clients with wrong clocks from
5740 reaching hidden services, and fixes a wide variety of other issues.
5743 - Clients can now connect to private bridges over IPv6. Bridges
5744 still need at least one IPv4 address in order to connect to
5745 other relays. Note that we don't yet handle the case where the
5746 user has two bridge lines for the same bridge (one IPv4, one
5747 IPv6). Implements parts of proposal 186.
5748 - New "DisableNetwork" config option to prevent Tor from launching any
5749 connections or accepting any connections except on a control port.
5750 Bundles and controllers can set this option before letting Tor talk
5751 to the rest of the network, for example to prevent any connections
5752 to a non-bridge address. Packages like Orbot can also use this
5753 option to instruct Tor to save power when the network is off.
5754 - Clients and bridges can now be configured to use a separate
5755 "transport" proxy. This approach makes the censorship arms race
5756 easier by allowing bridges to use protocol obfuscation plugins. It
5757 implements the "managed proxy" part of proposal 180 (ticket 3472).
5758 - When using OpenSSL 1.0.0 or later, use OpenSSL's counter mode
5759 implementation. It makes AES_CTR about 7% faster than our old one
5760 (which was about 10% faster than the one OpenSSL used to provide).
5761 Resolves ticket 4526.
5762 - Add a "tor2web mode" for clients that want to connect to hidden
5763 services non-anonymously (and possibly more quickly). As a safety
5764 measure to try to keep users from turning this on without knowing
5765 what they are doing, tor2web mode must be explicitly enabled at
5766 compile time, and a copy of Tor compiled to run in tor2web mode
5767 cannot be used as a normal Tor client. Implements feature 2553.
5768 - Add experimental support for running on Windows with IOCP and no
5769 kernel-space socket buffers. This feature is controlled by a new
5770 "UserspaceIOCPBuffers" config option (off by default), which has
5771 no effect unless Tor has been built with support for bufferevents,
5772 is running on Windows, and has enabled IOCP. This may, in the long
5773 run, help solve or mitigate bug 98.
5774 - Use a more secure consensus parameter voting algorithm. Now at
5775 least three directory authorities or a majority of them must
5776 vote on a given parameter before it will be included in the
5777 consensus. Implements proposal 178.
5780 - Hidden services now ignore the timestamps on INTRODUCE2 cells.
5781 They used to check that the timestamp was within 30 minutes
5782 of their system clock, so they could cap the size of their
5783 replay-detection cache, but that approach unnecessarily refused
5784 service to clients with wrong clocks. Bugfix on 0.2.1.6-alpha, when
5785 the v3 intro-point protocol (the first one which sent a timestamp
5786 field in the INTRODUCE2 cell) was introduced; fixes bug 3460.
5787 - Only use the EVP interface when AES acceleration is enabled,
5788 to avoid a 5-7% performance regression. Resolves issue 4525;
5789 bugfix on 0.2.3.8-alpha.
5791 o Privacy/anonymity features (bridge detection):
5792 - Make bridge SSL certificates a bit more stealthy by using random
5793 serial numbers, in the same fashion as OpenSSL when generating
5794 self-signed certificates. Implements ticket 4584.
5795 - Introduce a new config option "DynamicDHGroups", enabled by
5796 default, which provides each bridge with a unique prime DH modulus
5797 to be used during SSL handshakes. This option attempts to help
5798 against censors who might use the Apache DH modulus as a static
5799 identifier for bridges. Addresses ticket 4548.
5801 o Minor features (new/different config options):
5802 - New configuration option "DisableDebuggerAttachment" (on by default)
5803 to prevent basic debugging attachment attempts by other processes.
5804 Supports Mac OS X and Gnu/Linux. Resolves ticket 3313.
5805 - Allow MapAddress directives to specify matches against super-domains,
5806 as in "MapAddress *.torproject.org *.torproject.org.torserver.exit".
5807 Implements issue 933.
5808 - Slightly change behavior of "list" options (that is, config
5809 options that can appear more than once) when they appear both in
5810 torrc and on the command line. Previously, the command-line options
5811 would be appended to the ones from torrc. Now, the command-line
5812 options override the torrc options entirely. This new behavior
5813 allows the user to override list options (like exit policies and
5814 ports to listen on) from the command line, rather than simply
5815 appending to the list.
5816 - You can get the old (appending) command-line behavior for "list"
5817 options by prefixing the option name with a "+".
5818 - You can remove all the values for a "list" option from the command
5819 line without adding any new ones by prefixing the option name
5821 - Add experimental support for a "defaults" torrc file to be parsed
5822 before the regular torrc. Torrc options override the defaults file's
5823 options in the same way that the command line overrides the torrc.
5824 The SAVECONF controller command saves only those options which
5825 differ between the current configuration and the defaults file. HUP
5826 reloads both files. (Note: This is an experimental feature; its
5827 behavior will probably be refined in future 0.2.3.x-alpha versions
5828 to better meet packagers' needs.) Implements task 4552.
5831 - Try to make the introductory warning message that Tor prints on
5832 startup more useful for actually finding help and information.
5833 Resolves ticket 2474.
5834 - Running "make version" now displays the version of Tor that
5835 we're about to build. Idea from katmagic; resolves issue 4400.
5836 - Expire old or over-used hidden service introduction points.
5837 Required by fix for bug 3460.
5838 - Move the replay-detection cache for the RSA-encrypted parts of
5839 INTRODUCE2 cells to the introduction point data structures.
5840 Previously, we would use one replay-detection cache per hidden
5841 service. Required by fix for bug 3460.
5842 - Reduce the lifetime of elements of hidden services' Diffie-Hellman
5843 public key replay-detection cache from 60 minutes to 5 minutes. This
5844 replay-detection cache is now used only to detect multiple
5845 INTRODUCE2 cells specifying the same rendezvous point, so we can
5846 avoid launching multiple simultaneous attempts to connect to it.
5848 o Minor bugfixes (on Tor 0.2.2.x and earlier):
5849 - Resolve an integer overflow bug in smartlist_ensure_capacity().
5850 Fixes bug 4230; bugfix on Tor 0.1.0.1-rc. Based on a patch by
5852 - Fix a minor formatting issue in one of tor-gencert's error messages.
5854 - Prevent a false positive from the check-spaces script, by disabling
5855 the "whitespace between function name and (" check for functions
5857 - Fix a log message suggesting that people contact a non-existent
5858 email address. Fixes bug 3448.
5859 - Fix null-pointer access that could occur if TLS allocation failed.
5860 Fixes bug 4531; bugfix on 0.2.0.20-rc. Found by "troll_un".
5861 - Report a real bootstrap problem to the controller on router
5862 identity mismatch. Previously we just said "foo", which probably
5863 made a lot of sense at the time. Fixes bug 4169; bugfix on
5865 - If we had ever tried to call tor_addr_to_str() on an address of
5866 unknown type, we would have done a strdup() on an uninitialized
5867 buffer. Now we won't. Fixes bug 4529; bugfix on 0.2.1.3-alpha.
5868 Reported by "troll_un".
5869 - Correctly detect and handle transient lookup failures from
5870 tor_addr_lookup(). Fixes bug 4530; bugfix on 0.2.1.5-alpha.
5871 Reported by "troll_un".
5872 - Use tor_socket_t type for listener argument to accept(). Fixes bug
5873 4535; bugfix on 0.2.2.28-beta. Found by "troll_un".
5874 - Initialize conn->addr to a valid state in spawn_cpuworker(). Fixes
5875 bug 4532; found by "troll_un".
5877 o Minor bugfixes (on Tor 0.2.3.x):
5878 - Fix a compile warning in tor_inet_pton(). Bugfix on 0.2.3.8-alpha;
5880 - Don't send two ESTABLISH_RENDEZVOUS cells when opening a new
5881 circuit for use as a hidden service client's rendezvous point.
5882 Fixes bugs 4641 and 4171; bugfix on 0.2.3.3-alpha. Diagnosed
5883 with help from wanoskarnet.
5884 - Restore behavior of overriding SocksPort, ORPort, and similar
5885 options from the command line. Bugfix on 0.2.3.3-alpha.
5888 - Properly handle the case where the build-tree is not the same
5889 as the source tree when generating src/common/common_sha1.i,
5890 src/or/micro-revision.i, and src/or/or_sha1.i. Fixes bug 3953;
5891 bugfix on 0.2.0.1-alpha.
5893 o Code simplifications, cleanups, and refactorings:
5894 - Remove the pure attribute from all functions that used it
5895 previously. In many cases we assigned it incorrectly, because the
5896 functions might assert or call impure functions, and we don't have
5897 evidence that keeping the pure attribute is worthwhile. Implements
5898 changes suggested in ticket 4421.
5899 - Remove some dead code spotted by coverity. Fixes cid 432.
5900 Bugfix on 0.2.3.1-alpha, closes bug 4637.
5903 Changes in version 0.2.3.8-alpha - 2011-11-22
5904 Tor 0.2.3.8-alpha fixes some crash and assert bugs, including a
5905 socketpair-related bug that has been bothering Windows users. It adds
5906 support to serve microdescriptors to controllers, so Vidalia's network
5907 map can resume listing relays (once Vidalia implements its side),
5908 and adds better support for hardware AES acceleration. Finally, it
5909 starts the process of adjusting the bandwidth cutoff for getting the
5910 "Fast" flag from 20KB to (currently) 32KB -- preliminary results show
5911 that tiny relays harm performance more than they help network capacity.
5914 - Initialize Libevent with the EVENT_BASE_FLAG_NOLOCK flag enabled, so
5915 that it doesn't attempt to allocate a socketpair. This could cause
5916 some problems on Windows systems with overzealous firewalls. Fix for
5917 bug 4457; workaround for Libevent versions 2.0.1-alpha through
5919 - Correctly sanity-check that we don't underflow on a memory
5920 allocation (and then assert) for hidden service introduction
5921 point decryption. Bug discovered by Dan Rosenberg. Fixes bug 4410;
5922 bugfix on 0.2.1.5-alpha.
5923 - Remove the artificially low cutoff of 20KB to guarantee the Fast
5924 flag. In the past few years the average relay speed has picked
5925 up, and while the "top 7/8 of the network get the Fast flag" and
5926 "all relays with 20KB or more of capacity get the Fast flag" rules
5927 used to have the same result, now the top 7/8 of the network has
5928 a capacity more like 32KB. Bugfix on 0.2.1.14-rc. Fixes bug 4489.
5929 - Fix a rare assertion failure when checking whether a v0 hidden
5930 service descriptor has any usable introduction points left, and
5931 we don't have enough information to build a circuit to the first
5932 intro point named in the descriptor. The HS client code in
5933 0.2.3.x no longer uses v0 HS descriptors, but this assertion can
5934 trigger on (and crash) v0 HS authorities. Fixes bug 4411.
5935 Bugfix on 0.2.3.1-alpha; diagnosed by frosty_un.
5936 - Make bridge authorities not crash when they are asked for their own
5937 descriptor. Bugfix on 0.2.3.7-alpha, reported by Lucky Green.
5938 - When running as a client, do not print a misleading (and plain
5939 wrong) log message that we're collecting "directory request"
5940 statistics: clients don't collect statistics. Also don't create a
5941 useless (because empty) stats file in the stats/ directory. Fixes
5942 bug 4353; bugfix on 0.2.2.34 and 0.2.3.7-alpha.
5945 - Allow Tor controllers like Vidalia to obtain the microdescriptor
5946 for a relay by identity digest or nickname. Previously,
5947 microdescriptors were only available by their own digests, so a
5948 controller would have to ask for and parse the whole microdescriptor
5949 consensus in order to look up a single relay's microdesc. Fixes
5950 bug 3832; bugfix on 0.2.3.1-alpha.
5951 - Use OpenSSL's EVP interface for AES encryption, so that all AES
5952 operations can use hardware acceleration (if present). Resolves
5955 o Minor bugfixes (on 0.2.2.x and earlier):
5956 - Detect failure to initialize Libevent. This fix provides better
5957 detection for future instances of bug 4457.
5958 - Avoid frequent calls to the fairly expensive cull_wedged_cpuworkers
5959 function. This was eating up hideously large amounts of time on some
5960 busy servers. Fixes bug 4518; bugfix on 0.0.9.8.
5961 - Don't warn about unused log_mutex in log.c when building with
5962 --disable-threads using a recent GCC. Fixes bug 4437; bugfix on
5963 0.1.0.6-rc which introduced --disable-threads.
5964 - Allow manual 'authenticate' commands to the controller interface
5965 from netcat (nc) as well as telnet. We were rejecting them because
5966 they didn't come with the expected whitespace at the end of the
5967 command. Bugfix on 0.1.1.1-alpha; fixes bug 2893.
5968 - Fix some (not actually triggerable) buffer size checks in usage of
5969 tor_inet_ntop. Fixes bug 4434; bugfix on Tor 0.2.0.1-alpha. Patch
5971 - Fix parsing of some corner-cases with tor_inet_pton(). Fixes
5972 bug 4515; bugfix on 0.2.0.1-alpha; fix by Anders Sundman.
5973 - When configuring, starting, or stopping an NT service, stop
5974 immediately after the service configuration attempt has succeeded
5975 or failed. Fixes bug 3963; bugfix on 0.2.0.7-alpha.
5976 - When sending a NETINFO cell, include the original address
5977 received for the other side, not its canonical address. Found
5978 by "troll_un"; fixes bug 4349; bugfix on 0.2.0.10-alpha.
5979 - Rename the bench_{aes,dmap} functions to test_*, so that tinytest
5980 can pick them up when the tests aren't disabled. Bugfix on
5981 0.2.2.4-alpha which introduced tinytest.
5982 - Fix a memory leak when we check whether a hidden service
5983 descriptor has any usable introduction points left. Fixes bug
5984 4424. Bugfix on 0.2.2.25-alpha.
5985 - Fix a memory leak in launch_direct_bridge_descriptor_fetch() that
5986 occurred when a client tried to fetch a descriptor for a bridge
5987 in ExcludeNodes. Fixes bug 4383; bugfix on 0.2.2.25-alpha.
5989 o Minor bugfixes (on 0.2.3.x):
5990 - Make util unit tests build correctly with MSVC. Bugfix on
5991 0.2.3.3-alpha. Patch by Gisle Vanem.
5992 - Successfully detect AUTH_CHALLENGE cells with no recognized
5993 authentication type listed. Fixes bug 4367; bugfix on 0.2.3.6-alpha.
5995 - If a relay receives an AUTH_CHALLENGE cell it can't answer,
5996 it should still send a NETINFO cell to allow the connection to
5997 become open. Fixes bug 4368; fix on 0.2.3.6-alpha; bug found by
5999 - Log less loudly when we get an invalid authentication certificate
6000 from a source other than a directory authority: it's not unusual
6001 to see invalid certs because of clock skew. Fixes bug 4370; bugfix
6003 - Tolerate servers with more clock skew in their authentication
6004 certificates than previously. Fixes bug 4371; bugfix on
6006 - Fix a couple of compile warnings on Windows. Fixes bug 4469; bugfix
6007 on 0.2.3.4-alpha and 0.2.3.6-alpha.
6010 - Add two new config options for directory authorities:
6011 AuthDirFastGuarantee sets a bandwidth threshold for guaranteeing the
6012 Fast flag, and AuthDirGuardBWGuarantee sets a bandwidth threshold
6013 that is always sufficient to satisfy the bandwidth requirement for
6014 the Guard flag. Now it will be easier for researchers to simulate
6015 Tor networks with different values. Resolves ticket 4484.
6016 - When Tor ignores a hidden service specified in its configuration,
6017 include the hidden service's directory in the warning message.
6018 Previously, we would only tell the user that some hidden service
6019 was ignored. Bugfix on 0.0.6; fixes bug 4426.
6020 - When we fail to initialize Libevent, retry with IOCP disabled so we
6021 don't need to turn on multi-threading support in Libevent, which in
6022 turn requires a working socketpair(). This is a workaround for bug
6023 4457, which affects Libevent versions from 2.0.1-alpha through
6025 - Detect when we try to build on a platform that doesn't define
6026 AF_UNSPEC to 0. We don't work there, so refuse to compile.
6027 - Update to the November 1 2011 Maxmind GeoLite Country database.
6029 o Packaging changes:
6030 - Make it easier to automate expert package builds on Windows,
6031 by removing an absolute path from makensis.exe command.
6033 o Code simplifications and refactoring:
6034 - Remove some redundant #include directives throughout the code.
6035 Patch from Andrea Gelmini.
6036 - Unconditionally use OpenSSL's AES implementation instead of our
6037 old built-in one. OpenSSL's AES has been better for a while, and
6038 relatively few servers should still be on any version of OpenSSL
6039 that doesn't have good optimized assembly AES.
6040 - Use the name "CERTS" consistently to refer to the new cell type;
6041 we were calling it CERT in some places and CERTS in others.
6044 - Numerous new unit tests for functions in util.c and address.c by
6046 - The long-disabled benchmark tests are now split into their own
6047 ./src/test/bench binary.
6048 - The benchmark tests can now use more accurate timers than
6049 gettimeofday() when such timers are available.
6052 Changes in version 0.2.3.7-alpha - 2011-10-30
6053 Tor 0.2.3.7-alpha fixes a crash bug in 0.2.3.6-alpha introduced by
6054 the new v3 handshake. It also resolves yet another bridge address
6058 - If we mark an OR connection for close based on a cell we process,
6059 don't process any further cells on it. We already avoid further
6060 reads on marked-for-close connections, but now we also discard the
6061 cells we'd already read. Fixes bug 4299; bugfix on 0.2.0.10-alpha,
6062 which was the first version where we might mark a connection for
6063 close based on processing a cell on it.
6064 - Fix a double-free bug that would occur when we received an invalid
6065 certificate in a CERT cell in the new v3 handshake. Fixes bug 4343;
6066 bugfix on 0.2.3.6-alpha.
6067 - Bridges no longer include their address in NETINFO cells on outgoing
6068 OR connections, to allow them to blend in better with clients.
6069 Removes another avenue for enumerating bridges. Reported by
6070 "troll_un". Fixes bug 4348; bugfix on 0.2.0.10-alpha, when NETINFO
6071 cells were introduced.
6074 - Fixed a typo in a hibernation-related log message. Fixes bug 4331;
6075 bugfix on 0.2.2.23-alpha; found by "tmpname0901".
6078 Changes in version 0.2.3.6-alpha - 2011-10-26
6079 Tor 0.2.3.6-alpha includes the fix from 0.2.2.34 for a critical
6080 anonymity vulnerability where an attacker can deanonymize Tor
6081 users. Everybody should upgrade.
6083 This release also features support for a new v3 connection handshake
6084 protocol, and fixes to make hidden service connections more robust.
6087 - Implement a new handshake protocol (v3) for authenticating Tors to
6088 each other over TLS. It should be more resistant to fingerprinting
6089 than previous protocols, and should require less TLS hacking for
6090 future Tor implementations. Implements proposal 176.
6091 - Allow variable-length padding cells to disguise the length of
6092 Tor's TLS records. Implements part of proposal 184.
6094 o Privacy/anonymity fixes (clients):
6095 - Clients and bridges no longer send TLS certificate chains on
6096 outgoing OR connections. Previously, each client or bridge would
6097 use the same cert chain for all outgoing OR connections until
6098 its IP address changes, which allowed any relay that the client
6099 or bridge contacted to determine which entry guards it is using.
6100 Fixes CVE-2011-2768. Bugfix on 0.0.9pre5; found by "frosty_un".
6101 - If a relay receives a CREATE_FAST cell on a TLS connection, it
6102 no longer considers that connection as suitable for satisfying a
6103 circuit EXTEND request. Now relays can protect clients from the
6104 CVE-2011-2768 issue even if the clients haven't upgraded yet.
6105 - Directory authorities no longer assign the Guard flag to relays
6106 that haven't upgraded to the above "refuse EXTEND requests
6107 to client connections" fix. Now directory authorities can
6108 protect clients from the CVE-2011-2768 issue even if neither
6109 the clients nor the relays have upgraded yet. There's a new
6110 "GiveGuardFlagTo_CVE_2011_2768_VulnerableRelays" config option
6111 to let us transition smoothly, else tomorrow there would be no
6114 o Major bugfixes (hidden services):
6115 - Improve hidden service robustness: when an attempt to connect to
6116 a hidden service ends, be willing to refetch its hidden service
6117 descriptors from each of the HSDir relays responsible for them
6118 immediately. Previously, we would not consider refetching the
6119 service's descriptors from each HSDir for 15 minutes after the last
6120 fetch, which was inconvenient if the hidden service was not running
6121 during the first attempt. Bugfix on 0.2.0.18-alpha; fixes bug 3335.
6122 - When one of a hidden service's introduction points appears to be
6123 unreachable, stop trying it. Previously, we would keep trying
6124 to build circuits to the introduction point until we lost the
6125 descriptor, usually because the user gave up and restarted Tor.
6126 Partly fixes bug 3825.
6127 - Don't launch a useless circuit after failing to use one of a
6128 hidden service's introduction points. Previously, we would
6129 launch a new introduction circuit, but not set the hidden service
6130 which that circuit was intended to connect to, so it would never
6131 actually be used. A different piece of code would then create a
6132 new introduction circuit correctly. Bug reported by katmagic and
6133 found by Sebastian Hahn. Bugfix on 0.2.1.13-alpha; fixes bug 4212.
6135 o Major bugfixes (other):
6136 - Bridges now refuse CREATE or CREATE_FAST cells on OR connections
6137 that they initiated. Relays could distinguish incoming bridge
6138 connections from client connections, creating another avenue for
6139 enumerating bridges. Fixes CVE-2011-2769. Bugfix on 0.2.0.3-alpha.
6140 Found by "frosty_un".
6141 - Don't update the AccountingSoftLimitHitAt state file entry whenever
6142 tor gets started. This prevents a wrong average bandwidth
6143 estimate, which would cause relays to always start a new accounting
6144 interval at the earliest possible moment. Fixes bug 2003; bugfix
6145 on 0.2.2.7-alpha. Reported by BryonEldridge, who also helped
6146 immensely in tracking this bug down.
6147 - Fix a crash bug when changing node restrictions while a DNS lookup
6148 is in-progress. Fixes bug 4259; bugfix on 0.2.2.25-alpha. Bugfix
6151 o Minor bugfixes (on 0.2.2.x and earlier):
6152 - When a hidden service turns an extra service-side introduction
6153 circuit into a general-purpose circuit, free the rend_data and
6154 intro_key fields first, so we won't leak memory if the circuit
6155 is cannibalized for use as another service-side introduction
6156 circuit. Bugfix on 0.2.1.7-alpha; fixes bug 4251.
6157 - Rephrase the log message emitted if the TestSocks check is
6158 successful. Patch from Fabian Keil; fixes bug 4094.
6159 - Bridges now skip DNS self-tests, to act a little more stealthily.
6160 Fixes bug 4201; bugfix on 0.2.0.3-alpha, which first introduced
6161 bridges. Patch by "warms0x".
6162 - Remove a confusing dollar sign from the example fingerprint in the
6163 man page, and also make the example fingerprint a valid one. Fixes
6164 bug 4309; bugfix on 0.2.1.3-alpha.
6165 - Fix internal bug-checking logic that was supposed to catch
6166 failures in digest generation so that it will fail more robustly
6167 if we ask for a nonexistent algorithm. Found by Coverity Scan.
6168 Bugfix on 0.2.2.1-alpha; fixes Coverity CID 479.
6169 - Report any failure in init_keys() calls launched because our
6170 IP address has changed. Spotted by Coverity Scan. Bugfix on
6171 0.1.1.4-alpha; fixes CID 484.
6173 o Minor bugfixes (on 0.2.3.x):
6174 - Fix a bug in configure.in that kept it from building a configure
6175 script with autoconf versions earlier than 2.61. Fixes bug 2430;
6176 bugfix on 0.2.3.1-alpha.
6177 - Don't warn users that they are exposing a client port to the
6178 Internet if they have specified an RFC1918 address. Previously,
6179 we would warn if the user had specified any non-loopback
6180 address. Bugfix on 0.2.3.3-alpha. Fixes bug 4018; reported by Tas.
6181 - Fix memory leaks in the failing cases of the new SocksPort and
6182 ControlPort code. Found by Coverity Scan. Bugfix on 0.2.3.3-alpha;
6183 fixes coverity CIDs 485, 486, and 487.
6186 - When a hidden service's introduction point times out, consider
6187 trying it again during the next attempt to connect to the
6188 HS. Previously, we would not try it again unless a newly fetched
6189 descriptor contained it. Required by fixes for bugs 1297 and 3825.
6190 - The next version of Windows will be called Windows 8, and it has
6191 a major version of 6, minor version of 2. Correctly identify that
6192 version instead of calling it "Very recent version". Resolves
6193 ticket 4153; reported by funkstar.
6194 - The Bridge Authority now writes statistics on how many bridge
6195 descriptors it gave out in total, and how many unique descriptors
6196 it gave out. It also lists how often the most and least commonly
6197 fetched descriptors were given out, as well as the median and
6198 25th/75th percentile. Implements tickets 4200 and 4294.
6199 - Update to the October 4 2011 Maxmind GeoLite Country database.
6201 o Code simplifications and refactoring:
6202 - Remove some old code to remember statistics about which descriptors
6203 we've served as a directory mirror. The feature wasn't used and
6204 is outdated now that microdescriptors are around.
6205 - Rename Tor functions that turn strings into addresses, so that
6206 "parse" indicates that no hostname resolution occurs, and
6207 "lookup" indicates that hostname resolution may occur. This
6208 should help prevent mistakes in the future. Fixes bug 3512.
6211 Changes in version 0.2.2.34 - 2011-10-26
6212 Tor 0.2.2.34 fixes a critical anonymity vulnerability where an attacker
6213 can deanonymize Tor users. Everybody should upgrade.
6215 The attack relies on four components: 1) Clients reuse their TLS cert
6216 when talking to different relays, so relays can recognize a user by
6217 the identity key in her cert. 2) An attacker who knows the client's
6218 identity key can probe each guard relay to see if that identity key
6219 is connected to that guard relay right now. 3) A variety of active
6220 attacks in the literature (starting from "Low-Cost Traffic Analysis
6221 of Tor" by Murdoch and Danezis in 2005) allow a malicious website to
6222 discover the guard relays that a Tor user visiting the website is using.
6223 4) Clients typically pick three guards at random, so the set of guards
6224 for a given user could well be a unique fingerprint for her. This
6225 release fixes components #1 and #2, which is enough to block the attack;
6226 the other two remain as open research problems. Special thanks to
6227 "frosty_un" for reporting the issue to us!
6229 Clients should upgrade so they are no longer recognizable by the TLS
6230 certs they present. Relays should upgrade so they no longer allow a
6231 remote attacker to probe them to test whether unpatched clients are
6232 currently connected to them.
6234 This release also fixes several vulnerabilities that allow an attacker
6235 to enumerate bridge relays. Some bridge enumeration attacks still
6236 remain; see for example proposal 188.
6238 o Privacy/anonymity fixes (clients):
6239 - Clients and bridges no longer send TLS certificate chains on
6240 outgoing OR connections. Previously, each client or bridge would
6241 use the same cert chain for all outgoing OR connections until
6242 its IP address changes, which allowed any relay that the client
6243 or bridge contacted to determine which entry guards it is using.
6244 Fixes CVE-2011-2768. Bugfix on 0.0.9pre5; found by "frosty_un".
6245 - If a relay receives a CREATE_FAST cell on a TLS connection, it
6246 no longer considers that connection as suitable for satisfying a
6247 circuit EXTEND request. Now relays can protect clients from the
6248 CVE-2011-2768 issue even if the clients haven't upgraded yet.
6249 - Directory authorities no longer assign the Guard flag to relays
6250 that haven't upgraded to the above "refuse EXTEND requests
6251 to client connections" fix. Now directory authorities can
6252 protect clients from the CVE-2011-2768 issue even if neither
6253 the clients nor the relays have upgraded yet. There's a new
6254 "GiveGuardFlagTo_CVE_2011_2768_VulnerableRelays" config option
6255 to let us transition smoothly, else tomorrow there would be no
6258 o Privacy/anonymity fixes (bridge enumeration):
6259 - Bridge relays now do their directory fetches inside Tor TLS
6260 connections, like all the other clients do, rather than connecting
6261 directly to the DirPort like public relays do. Removes another
6262 avenue for enumerating bridges. Fixes bug 4115; bugfix on 0.2.0.35.
6263 - Bridges relays now build circuits for themselves in a more similar
6264 way to how clients build them. Removes another avenue for
6265 enumerating bridges. Fixes bug 4124; bugfix on 0.2.0.3-alpha,
6266 when bridges were introduced.
6267 - Bridges now refuse CREATE or CREATE_FAST cells on OR connections
6268 that they initiated. Relays could distinguish incoming bridge
6269 connections from client connections, creating another avenue for
6270 enumerating bridges. Fixes CVE-2011-2769. Bugfix on 0.2.0.3-alpha.
6271 Found by "frosty_un".
6274 - Fix a crash bug when changing node restrictions while a DNS lookup
6275 is in-progress. Fixes bug 4259; bugfix on 0.2.2.25-alpha. Bugfix
6277 - Don't launch a useless circuit after failing to use one of a
6278 hidden service's introduction points. Previously, we would
6279 launch a new introduction circuit, but not set the hidden service
6280 which that circuit was intended to connect to, so it would never
6281 actually be used. A different piece of code would then create a
6282 new introduction circuit correctly. Bug reported by katmagic and
6283 found by Sebastian Hahn. Bugfix on 0.2.1.13-alpha; fixes bug 4212.
6286 - Change an integer overflow check in the OpenBSD_Malloc code so
6287 that GCC is less likely to eliminate it as impossible. Patch
6288 from Mansour Moufid. Fixes bug 4059.
6289 - When a hidden service turns an extra service-side introduction
6290 circuit into a general-purpose circuit, free the rend_data and
6291 intro_key fields first, so we won't leak memory if the circuit
6292 is cannibalized for use as another service-side introduction
6293 circuit. Bugfix on 0.2.1.7-alpha; fixes bug 4251.
6294 - Bridges now skip DNS self-tests, to act a little more stealthily.
6295 Fixes bug 4201; bugfix on 0.2.0.3-alpha, which first introduced
6296 bridges. Patch by "warms0x".
6297 - Fix internal bug-checking logic that was supposed to catch
6298 failures in digest generation so that it will fail more robustly
6299 if we ask for a nonexistent algorithm. Found by Coverity Scan.
6300 Bugfix on 0.2.2.1-alpha; fixes Coverity CID 479.
6301 - Report any failure in init_keys() calls launched because our
6302 IP address has changed. Spotted by Coverity Scan. Bugfix on
6303 0.1.1.4-alpha; fixes CID 484.
6305 o Minor bugfixes (log messages and documentation):
6306 - Remove a confusing dollar sign from the example fingerprint in the
6307 man page, and also make the example fingerprint a valid one. Fixes
6308 bug 4309; bugfix on 0.2.1.3-alpha.
6309 - The next version of Windows will be called Windows 8, and it has
6310 a major version of 6, minor version of 2. Correctly identify that
6311 version instead of calling it "Very recent version". Resolves
6312 ticket 4153; reported by funkstar.
6313 - Downgrade log messages about circuit timeout calibration from
6314 "notice" to "info": they don't require or suggest any human
6315 intervention. Patch from Tom Lowenthal. Fixes bug 4063;
6316 bugfix on 0.2.2.14-alpha.
6319 - Turn on directory request statistics by default and include them in
6320 extra-info descriptors. Don't break if we have no GeoIP database.
6321 Backported from 0.2.3.1-alpha; implements ticket 3951.
6322 - Update to the October 4 2011 Maxmind GeoLite Country database.
6325 Changes in version 0.2.1.31 - 2011-10-26
6326 Tor 0.2.1.31 backports important security and privacy fixes for
6327 oldstable. This release is intended only for package maintainers and
6328 others who cannot use the 0.2.2 stable series. All others should be
6329 using Tor 0.2.2.x or newer.
6331 o Security fixes (also included in 0.2.2.x):
6332 - Replace all potentially sensitive memory comparison operations
6333 with versions whose runtime does not depend on the data being
6334 compared. This will help resist a class of attacks where an
6335 adversary can use variations in timing information to learn
6336 sensitive data. Fix for one case of bug 3122. (Safe memcmp
6337 implementation by Robert Ransom based partially on code by DJB.)
6338 - Fix an assert in parsing router descriptors containing IPv6
6339 addresses. This one took down the directory authorities when
6340 somebody tried some experimental code. Bugfix on 0.2.1.3-alpha.
6342 o Privacy/anonymity fixes (also included in 0.2.2.x):
6343 - Clients and bridges no longer send TLS certificate chains on
6344 outgoing OR connections. Previously, each client or bridge would
6345 use the same cert chain for all outgoing OR connections until
6346 its IP address changes, which allowed any relay that the client
6347 or bridge contacted to determine which entry guards it is using.
6348 Fixes CVE-2011-2768. Bugfix on 0.0.9pre5; found by "frosty_un".
6349 - If a relay receives a CREATE_FAST cell on a TLS connection, it
6350 no longer considers that connection as suitable for satisfying a
6351 circuit EXTEND request. Now relays can protect clients from the
6352 CVE-2011-2768 issue even if the clients haven't upgraded yet.
6353 - Bridges now refuse CREATE or CREATE_FAST cells on OR connections
6354 that they initiated. Relays could distinguish incoming bridge
6355 connections from client connections, creating another avenue for
6356 enumerating bridges. Fixes CVE-2011-2769. Bugfix on 0.2.0.3-alpha.
6357 Found by "frosty_un".
6358 - When receiving a hidden service descriptor, check that it is for
6359 the hidden service we wanted. Previously, Tor would store any
6360 hidden service descriptors that a directory gave it, whether it
6361 wanted them or not. This wouldn't have let an attacker impersonate
6362 a hidden service, but it did let directories pre-seed a client
6363 with descriptors that it didn't want. Bugfix on 0.0.6.
6364 - Avoid linkability based on cached hidden service descriptors: forget
6365 all hidden service descriptors cached as a client when processing a
6366 SIGNAL NEWNYM command. Fixes bug 3000; bugfix on 0.0.6.
6367 - Make the bridge directory authority refuse to answer directory
6368 requests for "all" descriptors. It used to include bridge
6369 descriptors in its answer, which was a major information leak.
6370 Found by "piebeer". Bugfix on 0.2.0.3-alpha.
6371 - Don't attach new streams to old rendezvous circuits after SIGNAL
6372 NEWNYM. Previously, we would keep using an existing rendezvous
6373 circuit if it remained open (i.e. if it were kept open by a
6374 long-lived stream, or if a new stream were attached to it before
6375 Tor could notice that it was old and no longer in use). Bugfix on
6376 0.1.1.15-rc; fixes bug 3375.
6378 o Minor bugfixes (also included in 0.2.2.x):
6379 - When we restart our relay, we might get a successful connection
6380 from the outside before we've started our reachability tests,
6381 triggering a warning: "ORPort found reachable, but I have no
6382 routerinfo yet. Failing to inform controller of success." This
6383 bug was harmless unless Tor is running under a controller
6384 like Vidalia, in which case the controller would never get a
6385 REACHABILITY_SUCCEEDED status event. Bugfix on 0.1.2.6-alpha;
6387 - Build correctly on OSX with zlib 1.2.4 and higher with all warnings
6388 enabled. Fixes bug 1526.
6389 - Remove undocumented option "-F" from tor-resolve: it hasn't done
6390 anything since 0.2.1.16-rc.
6391 - Avoid signed/unsigned comparisons by making SIZE_T_CEILING unsigned.
6392 None of the cases where we did this before were wrong, but by making
6393 this change we avoid warnings. Fixes bug 2475; bugfix on 0.2.1.28.
6394 - Fix a rare crash bug that could occur when a client was configured
6395 with a large number of bridges. Fixes bug 2629; bugfix on
6396 0.2.1.2-alpha. Bugfix by trac user "shitlei".
6397 - Correct the warning displayed when a rendezvous descriptor exceeds
6398 the maximum size. Fixes bug 2750; bugfix on 0.2.1.5-alpha. Found by
6400 - Fix an uncommon assertion failure when running with DNSPort under
6401 heavy load. Fixes bug 2933; bugfix on 0.2.0.1-alpha.
6402 - When warning about missing zlib development packages during compile,
6403 give the correct package names. Bugfix on 0.2.0.1-alpha.
6404 - Require that introduction point keys and onion keys have public
6405 exponent 65537. Bugfix on 0.2.0.10-alpha.
6406 - Do not crash when our configuration file becomes unreadable, for
6407 example due to a permissions change, between when we start up
6408 and when a controller calls SAVECONF. Fixes bug 3135; bugfix
6410 - Fix warnings from GCC 4.6's "-Wunused-but-set-variable" option.
6412 - Always NUL-terminate the sun_path field of a sockaddr_un before
6413 passing it to the kernel. (Not a security issue: kernels are
6414 smart enough to reject bad sockaddr_uns.) Found by Coverity;
6415 CID #428. Bugfix on Tor 0.2.0.3-alpha.
6416 - Don't stack-allocate the list of supplementary GIDs when we're
6417 about to log them. Stack-allocating NGROUPS_MAX gid_t elements
6418 could take up to 256K, which is way too much stack. Found by
6419 Coverity; CID #450. Bugfix on 0.2.1.7-alpha.
6421 o Minor bugfixes (only in 0.2.1.x):
6422 - Resume using micro-version numbers in 0.2.1.x: our Debian packages
6423 rely on them. Bugfix on 0.2.1.30.
6424 - Use git revisions instead of svn revisions when generating our
6425 micro-version numbers. Bugfix on 0.2.1.15-rc; fixes bug 2402.
6427 o Minor features (also included in 0.2.2.x):
6428 - Adjust the expiration time on our SSL session certificates to
6429 better match SSL certs seen in the wild. Resolves ticket 4014.
6430 - Allow nameservers with IPv6 address. Resolves bug 2574.
6431 - Update to the October 4 2011 Maxmind GeoLite Country database.
6434 Changes in version 0.2.3.5-alpha - 2011-09-28
6435 Tor 0.2.3.5-alpha fixes two bugs that make it possible to enumerate
6436 bridge relays; fixes an assertion error that many users started hitting
6437 today; and adds the ability to refill token buckets more often than
6438 once per second, allowing significant performance improvements.
6441 - Bridge relays now do their directory fetches inside Tor TLS
6442 connections, like all the other clients do, rather than connecting
6443 directly to the DirPort like public relays do. Removes another
6444 avenue for enumerating bridges. Fixes bug 4115; bugfix on 0.2.0.35.
6445 - Bridges relays now build circuits for themselves in a more similar
6446 way to how clients build them. Removes another avenue for
6447 enumerating bridges. Fixes bug 4124; bugfix on 0.2.0.3-alpha,
6448 when bridges were introduced.
6451 - Fix an "Assertion md->held_by_node == 1 failed" error that could
6452 occur when the same microdescriptor was referenced by two node_t
6453 objects at once. Fix for bug 4118; bugfix on Tor 0.2.3.1-alpha.
6455 o Major features (networking):
6456 - Add a new TokenBucketRefillInterval option to refill token buckets
6457 more frequently than once per second. This should improve network
6458 performance, alleviate queueing problems, and make traffic less
6459 bursty. Implements proposal 183; closes ticket 3630. Design by
6460 Florian Tschorsch and Björn Scheuermann; implementation by
6464 - Change an integer overflow check in the OpenBSD_Malloc code so
6465 that GCC is less likely to eliminate it as impossible. Patch
6466 from Mansour Moufid. Fixes bug 4059.
6468 o Minor bugfixes (usability):
6469 - Downgrade log messages about circuit timeout calibration from
6470 "notice" to "info": they don't require or suggest any human
6471 intervention. Patch from Tom Lowenthal. Fixes bug 4063;
6472 bugfix on 0.2.2.14-alpha.
6474 o Minor features (diagnostics):
6475 - When the system call to create a listener socket fails, log the
6476 error message explaining why. This may help diagnose bug 4027.
6479 Changes in version 0.2.3.4-alpha - 2011-09-13
6480 Tor 0.2.3.4-alpha includes the fixes from 0.2.2.33, including a slight
6481 tweak to Tor's TLS handshake that makes relays and bridges that run
6482 this new version reachable from Iran again. It also fixes a few new
6483 bugs in 0.2.3.x, and teaches relays to recognize when they're not
6484 listed in the network consensus and republish.
6486 o Major bugfixes (also part of 0.2.2.33):
6487 - Avoid an assertion failure when reloading a configuration with
6488 TrackExitHosts changes. Found and fixed by 'laruldan'. Fixes bug
6489 3923; bugfix on 0.2.2.25-alpha.
6491 o Minor features (security, also part of 0.2.2.33):
6492 - Check for replays of the public-key encrypted portion of an
6493 INTRODUCE1 cell, in addition to the current check for replays of
6494 the g^x value. This prevents a possible class of active attacks
6495 by an attacker who controls both an introduction point and a
6496 rendezvous point, and who uses the malleability of AES-CTR to
6497 alter the encrypted g^x portion of the INTRODUCE1 cell. We think
6498 that these attacks are infeasible (requiring the attacker to send
6499 on the order of zettabytes of altered cells in a short interval),
6500 but we'd rather block them off in case there are any classes of
6501 this attack that we missed. Reported by Willem Pinckaers.
6503 o Minor features (also part of 0.2.2.33):
6504 - Adjust the expiration time on our SSL session certificates to
6505 better match SSL certs seen in the wild. Resolves ticket 4014.
6506 - Change the default required uptime for a relay to be accepted as
6507 a HSDir (hidden service directory) from 24 hours to 25 hours.
6508 Improves on 0.2.0.10-alpha; resolves ticket 2649.
6509 - Add a VoteOnHidServDirectoriesV2 config option to allow directory
6510 authorities to abstain from voting on assignment of the HSDir
6511 consensus flag. Related to bug 2649.
6512 - Update to the September 6 2011 Maxmind GeoLite Country database.
6514 o Minor bugfixes (also part of 0.2.2.33):
6515 - Demote the 'replay detected' log message emitted when a hidden
6516 service receives the same Diffie-Hellman public key in two different
6517 INTRODUCE2 cells to info level. A normal Tor client can cause that
6518 log message during its normal operation. Bugfix on 0.2.1.6-alpha;
6519 fixes part of bug 2442.
6520 - Demote the 'INTRODUCE2 cell is too {old,new}' log message to info
6521 level. There is nothing that a hidden service's operator can do
6522 to fix its clients' clocks. Bugfix on 0.2.1.6-alpha; fixes part
6524 - Clarify a log message specifying the characters permitted in
6525 HiddenServiceAuthorizeClient client names. Previously, the log
6526 message said that "[A-Za-z0-9+-_]" were permitted; that could have
6527 given the impression that every ASCII character between "+" and "_"
6528 was permitted. Now we say "[A-Za-z0-9+_-]". Bugfix on 0.2.1.5-alpha.
6530 o Build fixes (also part of 0.2.2.33):
6531 - Clean up some code issues that prevented Tor from building on older
6532 BSDs. Fixes bug 3894; reported by "grarpamp".
6533 - Search for a platform-specific version of "ar" when cross-compiling.
6534 Should fix builds on iOS. Resolves bug 3909, found by Marco Bonetti.
6537 - Fix a bug where the SocksPort option (for example) would get
6538 ignored and replaced by the default if a SocksListenAddress
6539 option was set. Bugfix on 0.2.3.3-alpha; fixes bug 3936. Fix by
6543 - Relays now try regenerating and uploading their descriptor more
6544 frequently if they are not listed in the consensus, or if the
6545 version of their descriptor listed in the consensus is too
6546 old. This fix should prevent situations where a server declines
6547 to re-publish itself because it has done so too recently, even
6548 though the authorities decided not to list its recent-enough
6549 descriptor. Fix for bug 3327.
6552 - Relays now include a reason for regenerating their descriptors
6553 in an HTTP header when uploading to the authorities. This will
6554 make it easier to debug descriptor-upload issues in the future.
6555 - When starting as root and then changing our UID via the User
6556 control option, and we have a ControlSocket configured, make sure
6557 that the ControlSocket is owned by the same account that Tor will
6558 run under. Implements ticket 3421; fix by Jérémy Bobbio.
6561 - Abort if tor_vasprintf fails in connection_printf_to_buf (a
6562 utility function used in the control-port code). This shouldn't
6563 ever happen unless Tor is completely out of memory, but if it did
6564 happen and Tor somehow recovered from it, Tor could have sent a log
6565 message to a control port in the middle of a reply to a controller
6566 command. Fixes part of bug 3428; bugfix on 0.1.2.3-alpha.
6567 - Make 'FetchUselessDescriptors' cause all descriptor types and
6568 all consensus types (including microdescriptors) to get fetched.
6569 Fixes bug 3851; bugfix on 0.2.3.1-alpha.
6572 - Make a new "entry connection" struct as an internal subtype of "edge
6573 connection", to simplify the code and make exit connections smaller.
6576 Changes in version 0.2.2.33 - 2011-09-13
6577 Tor 0.2.2.33 fixes several bugs, and includes a slight tweak to Tor's
6578 TLS handshake that makes relays and bridges that run this new version
6579 reachable from Iran again.
6582 - Avoid an assertion failure when reloading a configuration with
6583 TrackExitHosts changes. Found and fixed by 'laruldan'. Fixes bug
6584 3923; bugfix on 0.2.2.25-alpha.
6586 o Minor features (security):
6587 - Check for replays of the public-key encrypted portion of an
6588 INTRODUCE1 cell, in addition to the current check for replays of
6589 the g^x value. This prevents a possible class of active attacks
6590 by an attacker who controls both an introduction point and a
6591 rendezvous point, and who uses the malleability of AES-CTR to
6592 alter the encrypted g^x portion of the INTRODUCE1 cell. We think
6593 that these attacks are infeasible (requiring the attacker to send
6594 on the order of zettabytes of altered cells in a short interval),
6595 but we'd rather block them off in case there are any classes of
6596 this attack that we missed. Reported by Willem Pinckaers.
6599 - Adjust the expiration time on our SSL session certificates to
6600 better match SSL certs seen in the wild. Resolves ticket 4014.
6601 - Change the default required uptime for a relay to be accepted as
6602 a HSDir (hidden service directory) from 24 hours to 25 hours.
6603 Improves on 0.2.0.10-alpha; resolves ticket 2649.
6604 - Add a VoteOnHidServDirectoriesV2 config option to allow directory
6605 authorities to abstain from voting on assignment of the HSDir
6606 consensus flag. Related to bug 2649.
6607 - Update to the September 6 2011 Maxmind GeoLite Country database.
6609 o Minor bugfixes (documentation and log messages):
6610 - Correct the man page to explain that HashedControlPassword and
6611 CookieAuthentication can both be set, in which case either method
6612 is sufficient to authenticate to Tor. Bugfix on 0.2.0.7-alpha,
6613 when we decided to allow these config options to both be set. Issue
6615 - Demote the 'replay detected' log message emitted when a hidden
6616 service receives the same Diffie-Hellman public key in two different
6617 INTRODUCE2 cells to info level. A normal Tor client can cause that
6618 log message during its normal operation. Bugfix on 0.2.1.6-alpha;
6619 fixes part of bug 2442.
6620 - Demote the 'INTRODUCE2 cell is too {old,new}' log message to info
6621 level. There is nothing that a hidden service's operator can do
6622 to fix its clients' clocks. Bugfix on 0.2.1.6-alpha; fixes part
6624 - Clarify a log message specifying the characters permitted in
6625 HiddenServiceAuthorizeClient client names. Previously, the log
6626 message said that "[A-Za-z0-9+-_]" were permitted; that could have
6627 given the impression that every ASCII character between "+" and "_"
6628 was permitted. Now we say "[A-Za-z0-9+_-]". Bugfix on 0.2.1.5-alpha.
6631 - Provide a substitute implementation of lround() for MSVC, which
6632 apparently lacks it. Patch from Gisle Vanem.
6633 - Clean up some code issues that prevented Tor from building on older
6634 BSDs. Fixes bug 3894; reported by "grarpamp".
6635 - Search for a platform-specific version of "ar" when cross-compiling.
6636 Should fix builds on iOS. Resolves bug 3909, found by Marco Bonetti.
6639 Changes in version 0.2.3.3-alpha - 2011-09-01
6640 Tor 0.2.3.3-alpha adds a new "stream isolation" feature to improve Tor's
6641 security, and provides client-side support for the microdescriptor
6642 and optimistic data features introduced earlier in the 0.2.3.x
6643 series. It also includes numerous critical bugfixes in the (optional)
6644 bufferevent-based networking backend.
6646 o Major features (stream isolation):
6647 - You can now configure Tor so that streams from different
6648 applications are isolated on different circuits, to prevent an
6649 attacker who sees your streams as they leave an exit node from
6650 linking your sessions to one another. To do this, choose some way
6651 to distinguish the applications: have them connect to different
6652 SocksPorts, or have one of them use SOCKS4 while the other uses
6653 SOCKS5, or have them pass different authentication strings to the
6654 SOCKS proxy. Then, use the new SocksPort syntax to configure the
6655 degree of isolation you need. This implements Proposal 171.
6656 - There's a new syntax for specifying multiple client ports (such as
6657 SOCKSPort, TransPort, DNSPort, NATDPort): you can now just declare
6658 multiple *Port entries with full addr:port syntax on each.
6659 The old *ListenAddress format is still supported, but you can't
6660 mix it with the new *Port syntax.
6662 o Major features (other):
6663 - Enable microdescriptor fetching by default for clients. This allows
6664 clients to download a much smaller amount of directory information.
6665 To disable it (and go back to the old-style consensus and
6666 descriptors), set "UseMicrodescriptors 0" in your torrc file.
6667 - Tor's firewall-helper feature, introduced in 0.2.3.1-alpha (see the
6668 "PortForwarding" config option), now supports Windows.
6669 - When using an exit relay running 0.2.3.x, clients can now
6670 "optimistically" send data before the exit relay reports that
6671 the stream has opened. This saves a round trip when starting
6672 connections where the client speaks first (such as web browsing).
6673 This behavior is controlled by a consensus parameter (currently
6674 disabled). To turn it on or off manually, use the "OptimisticData"
6675 torrc option. Implements proposal 181; code by Ian Goldberg.
6677 o Major bugfixes (bufferevents, fixes on 0.2.3.1-alpha):
6678 - When using IOCP on Windows, we need to enable Libevent windows
6680 - The IOCP backend now works even when the user has not specified
6681 the (internal, debugging-only) _UseFilteringSSLBufferevents option.
6682 Fixes part of bug 3752.
6683 - Correctly record the bytes we've read and written when using
6684 bufferevents, so that we can include them in our bandwidth history
6685 and advertised bandwidth. Fixes bug 3803.
6686 - Apply rate-limiting only at the bottom of a chain of filtering
6687 bufferevents. This prevents us from filling up internal read
6688 buffers and violating rate-limits when filtering bufferevents
6689 are enabled. Fixes part of bug 3804.
6690 - Add high-watermarks to the output buffers for filtered
6691 bufferevents. This prevents us from filling up internal write
6692 buffers and wasting CPU cycles when filtering bufferevents are
6693 enabled. Fixes part of bug 3804.
6694 - Correctly notice when data has been written from a bufferevent
6695 without flushing it completely. Fixes bug 3805.
6696 - Fix a bug where server-side tunneled bufferevent-based directory
6697 streams would get closed prematurely. Fixes bug 3814.
6698 - Fix a use-after-free error with per-connection rate-limiting
6699 buckets. Fixes bug 3888.
6701 o Major bugfixes (also part of 0.2.2.31-rc):
6702 - If we're configured to write our ControlPorts to disk, only write
6703 them after switching UID and creating the data directory. This way,
6704 we don't fail when starting up with a nonexistent DataDirectory
6705 and a ControlPortWriteToFile setting based on that directory. Fixes
6706 bug 3747; bugfix on Tor 0.2.2.26-beta.
6709 - Added a new CONF_CHANGED event so that controllers can be notified
6710 of any configuration changes made by other controllers, or by the
6711 user. Implements ticket 1692.
6712 - Use evbuffer_copyout() in inspect_evbuffer(). This fixes a memory
6713 leak when using bufferevents, and lets Libevent worry about how to
6714 best copy data out of a buffer.
6715 - Replace files in stats/ rather than appending to them. Now that we
6716 include statistics in extra-info descriptors, it makes no sense to
6717 keep old statistics forever. Implements ticket 2930.
6719 o Minor features (build compatibility):
6720 - Limited, experimental support for building with nmake and MSVC.
6721 - Provide a substitute implementation of lround() for MSVC, which
6722 apparently lacks it. Patch from Gisle Vanem.
6724 o Minor features (also part of 0.2.2.31-rc):
6725 - Update to the August 2 2011 Maxmind GeoLite Country database.
6727 o Minor bugfixes (on 0.2.3.x-alpha):
6728 - Fix a spurious warning when parsing SOCKS requests with
6729 bufferevents enabled. Fixes bug 3615; bugfix on 0.2.3.2-alpha.
6730 - Get rid of a harmless warning that could happen on relays running
6731 with bufferevents. The warning was caused by someone doing an http
6732 request to a relay's orport. Also don't warn for a few related
6733 non-errors. Fixes bug 3700; bugfix on 0.2.3.1-alpha.
6735 o Minor bugfixes (on 2.2.x and earlier):
6736 - Correct the man page to explain that HashedControlPassword and
6737 CookieAuthentication can both be set, in which case either method
6738 is sufficient to authenticate to Tor. Bugfix on 0.2.0.7-alpha,
6739 when we decided to allow these config options to both be set. Issue
6741 - The "--quiet" and "--hush" options now apply not only to Tor's
6742 behavior before logs are configured, but also to Tor's behavior in
6743 the absense of configured logs. Fixes bug 3550; bugfix on
6746 o Minor bugfixes (also part of 0.2.2.31-rc):
6747 - Write several files in text mode, on OSes that distinguish text
6748 mode from binary mode (namely, Windows). These files are:
6749 'buffer-stats', 'dirreq-stats', and 'entry-stats' on relays
6750 that collect those statistics; 'client_keys' and 'hostname' for
6751 hidden services that use authentication; and (in the tor-gencert
6752 utility) newly generated identity and signing keys. Previously,
6753 we wouldn't specify text mode or binary mode, leading to an
6754 assertion failure. Fixes bug 3607. Bugfix on 0.2.1.1-alpha (when
6755 the DirRecordUsageByCountry option which would have triggered
6756 the assertion failure was added), although this assertion failure
6757 would have occurred in tor-gencert on Windows in 0.2.0.1-alpha.
6758 - Selectively disable deprecation warnings on OS X because Lion
6759 started deprecating the shipped copy of openssl. Fixes bug 3643.
6760 - Remove an extra pair of quotation marks around the error
6761 message in control-port STATUS_GENERAL BUG events. Bugfix on
6762 0.1.2.6-alpha; fixes bug 3732.
6763 - When unable to format an address as a string, report its value
6764 as "???" rather than reusing the last formatted address. Bugfix
6767 o Code simplifications and refactoring:
6768 - Rewrite the listener-selection logic so that parsing which ports
6769 we want to listen on is now separate from binding to the ports
6773 - Building Tor with bufferevent support now requires Libevent
6774 2.0.13-stable or later. Previous versions of Libevent had bugs in
6775 SSL-related bufferevents and related issues that would make Tor
6776 work badly with bufferevents. Requiring 2.0.13-stable also allows
6777 Tor with bufferevents to take advantage of Libevent APIs
6778 introduced after 2.0.8-rc.
6781 Changes in version 0.2.2.32 - 2011-08-27
6782 The Tor 0.2.2 release series is dedicated to the memory of Andreas
6783 Pfitzmann (1958-2010), a pioneer in anonymity and privacy research,
6784 a founder of the PETS community, a leader in our field, a mentor,
6785 and a friend. He left us with these words: "I had the possibility
6786 to contribute to this world that is not as it should be. I hope I
6787 could help in some areas to make the world a better place, and that
6788 I could also encourage other people to be engaged in improving the
6789 world. Please, stay engaged. This world needs you, your love, your
6790 initiative -- now I cannot be part of that anymore."
6792 Tor 0.2.2.32, the first stable release in the 0.2.2 branch, is finally
6793 ready. More than two years in the making, this release features improved
6794 client performance and hidden service reliability, better compatibility
6795 for Android, correct behavior for bridges that listen on more than
6796 one address, more extensible and flexible directory object handling,
6797 better reporting of network statistics, improved code security, and
6798 many many other features and bugfixes.
6801 Changes in version 0.2.2.31-rc - 2011-08-17
6802 Tor 0.2.2.31-rc is the second and hopefully final release candidate
6803 for the Tor 0.2.2.x series.
6806 - Remove an extra pair of quotation marks around the error
6807 message in control-port STATUS_GENERAL BUG events. Bugfix on
6808 0.1.2.6-alpha; fixes bug 3732.
6809 - If we're configured to write our ControlPorts to disk, only write
6810 them after switching UID and creating the data directory. This way,
6811 we don't fail when starting up with a nonexistent DataDirectory
6812 and a ControlPortWriteToFile setting based on that directory. Fixes
6813 bug 3747; bugfix on Tor 0.2.2.26-beta.
6816 - Update to the August 2 2011 Maxmind GeoLite Country database.
6819 - Allow GETINFO fingerprint to return a fingerprint even when
6820 we have not yet built a router descriptor. Fixes bug 3577;
6821 bugfix on 0.2.0.1-alpha.
6822 - Write several files in text mode, on OSes that distinguish text
6823 mode from binary mode (namely, Windows). These files are:
6824 'buffer-stats', 'dirreq-stats', and 'entry-stats' on relays
6825 that collect those statistics; 'client_keys' and 'hostname' for
6826 hidden services that use authentication; and (in the tor-gencert
6827 utility) newly generated identity and signing keys. Previously,
6828 we wouldn't specify text mode or binary mode, leading to an
6829 assertion failure. Fixes bug 3607. Bugfix on 0.2.1.1-alpha (when
6830 the DirRecordUsageByCountry option which would have triggered
6831 the assertion failure was added), although this assertion failure
6832 would have occurred in tor-gencert on Windows in 0.2.0.1-alpha.
6833 - Selectively disable deprecation warnings on OS X because Lion
6834 started deprecating the shipped copy of openssl. Fixes bug 3643.
6835 - When unable to format an address as a string, report its value
6836 as "???" rather than reusing the last formatted address. Bugfix
6840 Changes in version 0.2.3.2-alpha - 2011-07-18
6841 Tor 0.2.3.2-alpha introduces two new experimental features:
6842 microdescriptors and pluggable transports. It also continues cleaning
6843 up a variety of recently introduced features.
6846 - Clients can now use microdescriptors instead of regular descriptors
6847 to build circuits. Microdescriptors are authority-generated
6848 summaries of regular descriptors' contents, designed to change
6849 very rarely (see proposal 158 for details). This feature is
6850 designed to save bandwidth, especially for clients on slow internet
6851 connections. It's off by default for now, since nearly no caches
6852 support it, but it will be on-by-default for clients in a future
6853 version. You can use the UseMicrodescriptors option to turn it on.
6854 - Tor clients using bridges can now be configured to use a separate
6855 'transport' proxy for each bridge. This approach helps to resist
6856 censorship by allowing bridges to use protocol obfuscation
6857 plugins. It implements part of proposal 180. Implements ticket 2841.
6858 - While we're trying to bootstrap, record how many TLS connections
6859 fail in each state, and report which states saw the most failures
6860 in response to any bootstrap failures. This feature may speed up
6861 diagnosis of censorship events. Implements ticket 3116.
6863 o Major bugfixes (on 0.2.3.1-alpha):
6864 - When configuring a large set of nodes in EntryNodes (as with
6865 'EntryNodes {cc}' or 'EntryNodes 1.1.1.1/16'), choose only a
6866 random subset to be guards, and choose them in random
6867 order. Fixes bug 2798.
6868 - Tor could crash when remembering a consensus in a non-used consensus
6869 flavor without having a current consensus set. Fixes bug 3361.
6870 - Comparing an unknown address to a microdescriptor's shortened exit
6871 policy would always give a "rejected" result. Fixes bug 3599.
6872 - Using microdescriptors as a client no longer prevents Tor from
6873 uploading and downloading hidden service descriptors. Fixes
6877 - Allow nameservers with IPv6 address. Resolves bug 2574.
6878 - Accept attempts to include a password authenticator in the
6879 handshake, as supported by SOCKS5. This handles SOCKS clients that
6880 don't know how to omit a password when authenticating. Resolves
6882 - When configuring a large set of nodes in EntryNodes, and there are
6883 enough of them listed as Guard so that we don't need to consider
6884 the non-guard entries, prefer the ones listed with the Guard flag.
6885 - Check for and recover from inconsistency in the microdescriptor
6886 cache. This will make it harder for us to accidentally free a
6887 microdescriptor without removing it from the appropriate data
6888 structures. Fixes issue 3135; issue noted by "wanoskarnet".
6889 - Log SSL state transitions at log level DEBUG, log domain
6890 HANDSHAKE. This can be useful for debugging censorship events.
6891 Implements ticket 3264.
6892 - Add port 6523 (Gobby) to LongLivedPorts. Patch by intrigeri;
6893 implements ticket 3439.
6895 o Minor bugfixes (on 0.2.3.1-alpha):
6896 - Do not free all general-purpose regular descriptors just
6897 because microdescriptor use is enabled. Fixes bug 3113.
6898 - Correctly link libevent_openssl when --enable-static-libevent
6899 is passed to configure. Fixes bug 3118.
6900 - Bridges should not complain during their heartbeat log messages that
6901 they are unlisted in the consensus: that's more or less the point
6902 of being a bridge. Fixes bug 3183.
6903 - Report a SIGNAL event to controllers when acting on a delayed
6904 SIGNAL NEWNYM command. Previously, we would report a SIGNAL
6905 event to the controller if we acted on a SIGNAL NEWNYM command
6906 immediately, and otherwise not report a SIGNAL event for the
6907 command at all. Fixes bug 3349.
6908 - Fix a crash when handling the SIGNAL controller command or
6909 reporting ERR-level status events with bufferevents enabled. Found
6910 by Robert Ransom. Fixes bug 3367.
6911 - Always ship the tor-fw-helper manpage in our release tarballs.
6912 Fixes bug 3389. Reported by Stephen Walker.
6913 - Fix a class of double-mark-for-close bugs when bufferevents
6914 are enabled. Fixes bug 3403.
6915 - Update tor-fw-helper to support libnatpmp-20110618. Fixes bug 3434.
6916 - Add SIGNAL to the list returned by the 'GETINFO events/names'
6917 control-port command. Fixes part of bug 3465.
6918 - Prevent using negative indices during unit test runs when read_all()
6919 fails. Spotted by coverity.
6920 - Fix a rare memory leak when checking the nodelist without it being
6921 present. Found by coverity.
6922 - Only try to download a microdescriptor-flavored consensus from
6923 a directory cache that provides them.
6925 o Minor bugfixes (on 0.2.2.x and earlier):
6926 - Assert that hidden-service-related operations are not performed
6927 using single-hop circuits. Previously, Tor would assert that
6928 client-side streams are not attached to single-hop circuits,
6929 but not that other sensitive operations on the client and service
6930 side are not performed using single-hop circuits. Fixes bug 3332;
6932 - Don't publish a new relay descriptor when we reload our onion key,
6933 unless the onion key has actually changed. Fixes bug 3263 and
6934 resolves another cause of bug 1810. Bugfix on 0.1.1.11-alpha.
6935 - Allow GETINFO fingerprint to return a fingerprint even when
6936 we have not yet built a router descriptor. Fixes bug 3577;
6937 bugfix on 0.2.0.1-alpha.
6938 - Make 'tor --digests' list hashes of all Tor source files. Bugfix
6939 on 0.2.2.4-alpha; fixes bug 3427.
6941 o Code simplification and refactoring:
6942 - Use tor_sscanf() in place of scanf() in more places through the
6943 code. This makes us a little more locale-independent, and
6944 should help shut up code-analysis tools that can't tell
6945 a safe sscanf string from a dangerous one.
6946 - Use tt_assert(), not tor_assert(), for checking for test failures.
6947 This makes the unit tests more able to go on in the event that
6949 - Split connection_about_to_close() into separate functions for each
6953 - On Windows, we now define the _WIN32_WINNT macros only if they
6954 are not already defined. This lets the person building Tor decide,
6955 if they want, to require a later version of Windows.
6958 Changes in version 0.2.2.30-rc - 2011-07-07
6959 Tor 0.2.2.30-rc is the first release candidate for the Tor 0.2.2.x
6960 series. It fixes a few smaller bugs, but generally appears stable.
6961 Please test it and let us know whether it is!
6964 - Send a SUCCEEDED stream event to the controller when a reverse
6965 resolve succeeded. Fixes bug 3536; bugfix on 0.0.8pre1. Issue
6966 discovered by katmagic.
6967 - Always NUL-terminate the sun_path field of a sockaddr_un before
6968 passing it to the kernel. (Not a security issue: kernels are
6969 smart enough to reject bad sockaddr_uns.) Found by Coverity;
6970 CID #428. Bugfix on Tor 0.2.0.3-alpha.
6971 - Don't stack-allocate the list of supplementary GIDs when we're
6972 about to log them. Stack-allocating NGROUPS_MAX gid_t elements
6973 could take up to 256K, which is way too much stack. Found by
6974 Coverity; CID #450. Bugfix on 0.2.1.7-alpha.
6975 - Add BUILDTIMEOUT_SET to the list returned by the 'GETINFO
6976 events/names' control-port command. Bugfix on 0.2.2.9-alpha;
6977 fixes part of bug 3465.
6978 - Fix a memory leak when receiving a descriptor for a hidden
6979 service we didn't ask for. Found by Coverity; CID #30. Bugfix
6983 - Update to the July 1 2011 Maxmind GeoLite Country database.
6986 Changes in version 0.2.2.29-beta - 2011-06-20
6987 Tor 0.2.2.29-beta reverts an accidental behavior change for users who
6988 have bridge lines in their torrc but don't want to use them; gets
6989 us closer to having the control socket feature working on Debian;
6990 and fixes a variety of smaller bugs.
6993 - Revert the UseBridges option to its behavior before 0.2.2.28-beta.
6994 When we changed the default behavior to "use bridges if any
6995 are listed in the torrc", we surprised users who had bridges
6996 in their torrc files but who didn't actually want to use them.
6997 Partial resolution for bug 3354.
7000 - Don't attach new streams to old rendezvous circuits after SIGNAL
7001 NEWNYM. Previously, we would keep using an existing rendezvous
7002 circuit if it remained open (i.e. if it were kept open by a
7003 long-lived stream, or if a new stream were attached to it before
7004 Tor could notice that it was old and no longer in use). Bugfix on
7005 0.1.1.15-rc; fixes bug 3375.
7008 - Fix a bug when using ControlSocketsGroupWritable with User. The
7009 directory's group would be checked against the current group, not
7010 the configured group. Patch by Jérémy Bobbio. Fixes bug 3393;
7011 bugfix on 0.2.2.26-beta.
7012 - Make connection_printf_to_buf()'s behaviour sane. Its callers
7013 expect it to emit a CRLF iff the format string ends with CRLF;
7014 it actually emitted a CRLF iff (a) the format string ended with
7015 CRLF or (b) the resulting string was over 1023 characters long or
7016 (c) the format string did not end with CRLF *and* the resulting
7017 string was 1021 characters long or longer. Bugfix on 0.1.1.9-alpha;
7018 fixes part of bug 3407.
7019 - Make send_control_event_impl()'s behaviour sane. Its callers
7020 expect it to always emit a CRLF at the end of the string; it
7021 might have emitted extra control characters as well. Bugfix on
7022 0.1.1.9-alpha; fixes another part of bug 3407.
7023 - Make crypto_rand_int() check the value of its input correctly.
7024 Previously, it accepted values up to UINT_MAX, but could return a
7025 negative number if given a value above INT_MAX+1. Found by George
7026 Kadianakis. Fixes bug 3306; bugfix on 0.2.2pre14.
7027 - Avoid a segfault when reading a malformed circuit build state
7028 with more than INT_MAX entries. Found by wanoskarnet. Bugfix on
7030 - When asked about a DNS record type we don't support via a
7031 client DNSPort, reply with NOTIMPL rather than an empty
7032 reply. Patch by intrigeri. Fixes bug 3369; bugfix on 2.0.1-alpha.
7033 - Fix a rare memory leak during stats writing. Found by coverity.
7036 - Update to the June 1 2011 Maxmind GeoLite Country database.
7038 o Code simplifications and refactoring:
7039 - Remove some dead code as indicated by coverity.
7040 - Remove a few dead assignments during router parsing. Found by
7042 - Add some forgotten return value checks during unit tests. Found
7044 - Don't use 1-bit wide signed bit fields. Found by coverity.
7047 Changes in version 0.2.2.28-beta - 2011-06-04
7048 Tor 0.2.2.28-beta makes great progress towards a new stable release: we
7049 fixed a big bug in whether relays stay in the consensus consistently,
7050 we moved closer to handling bridges and hidden services correctly,
7051 and we started the process of better handling the dreaded "my Vidalia
7052 died, and now my Tor demands a password when I try to reconnect to it"
7056 - Don't decide to make a new descriptor when receiving a HUP signal.
7057 This bug has caused a lot of 0.2.2.x relays to disappear from the
7058 consensus periodically. Fixes the most common case of triggering
7059 bug 1810; bugfix on 0.2.2.7-alpha.
7060 - Actually allow nameservers with IPv6 addresses. Fixes bug 2574.
7061 - Don't try to build descriptors if "ORPort auto" is set and we
7062 don't know our actual ORPort yet. Fix for bug 3216; bugfix on
7064 - Resolve a crash that occurred when setting BridgeRelay to 1 with
7065 accounting enabled. Fixes bug 3228; bugfix on 0.2.2.18-alpha.
7066 - Apply circuit timeouts to opened hidden-service-related circuits
7067 based on the correct start time. Previously, we would apply the
7068 circuit build timeout based on time since the circuit's creation;
7069 it was supposed to be applied based on time since the circuit
7070 entered its current state. Bugfix on 0.0.6; fixes part of bug 1297.
7071 - Use the same circuit timeout for client-side introduction
7072 circuits as for other four-hop circuits, rather than the timeout
7073 for single-hop directory-fetch circuits; the shorter timeout may
7074 have been appropriate with the static circuit build timeout in
7075 0.2.1.x and earlier, but caused many hidden service access attempts
7076 to fail with the adaptive CBT introduced in 0.2.2.2-alpha. Bugfix
7077 on 0.2.2.2-alpha; fixes another part of bug 1297.
7078 - In ticket 2511 we fixed a case where you could use an unconfigured
7079 bridge if you had configured it as a bridge the last time you ran
7080 Tor. Now fix another edge case: if you had configured it as a bridge
7081 but then switched to a different bridge via the controller, you
7082 would still be willing to use the old one. Bugfix on 0.2.0.1-alpha;
7086 - Add an __OwningControllerProcess configuration option and a
7087 TAKEOWNERSHIP control-port command. Now a Tor controller can ensure
7088 that when it exits, Tor will shut down. Implements feature 3049.
7089 - If "UseBridges 1" is set and no bridges are configured, Tor will
7090 now refuse to build any circuits until some bridges are set.
7091 If "UseBridges auto" is set, Tor will use bridges if they are
7092 configured and we are not running as a server, but otherwise will
7093 make circuits as usual. The new default is "auto". Patch by anonym,
7094 so the Tails LiveCD can stop automatically revealing you as a Tor
7098 - Fix warnings from GCC 4.6's "-Wunused-but-set-variable" option.
7099 - Remove a trailing asterisk from "exit-policy/default" in the
7100 output of the control port command "GETINFO info/names". Bugfix
7102 - Use a wide type to hold sockets when built for 64-bit Windows builds.
7104 - Warn when the user configures two HiddenServiceDir lines that point
7105 to the same directory. Bugfix on 0.0.6 (the version introducing
7106 HiddenServiceDir); fixes bug 3289.
7107 - Remove dead code from rend_cache_lookup_v2_desc_as_dir. Fixes
7108 part of bug 2748; bugfix on 0.2.0.10-alpha.
7109 - Log malformed requests for rendezvous descriptors as protocol
7110 warnings, not warnings. Also, use a more informative log message
7111 in case someone sees it at log level warning without prior
7112 info-level messages. Fixes the other part of bug 2748; bugfix
7114 - Clear the table recording the time of the last request for each
7115 hidden service descriptor from each HS directory on SIGNAL NEWNYM.
7116 Previously, we would clear our HS descriptor cache on SIGNAL
7117 NEWNYM, but if we had previously retrieved a descriptor (or tried
7118 to) from every directory responsible for it, we would refuse to
7119 fetch it again for up to 15 minutes. Bugfix on 0.2.2.25-alpha;
7121 - Fix a log message that said "bits" while displaying a value in
7122 bytes. Found by wanoskarnet. Fixes bug 3318; bugfix on
7124 - When checking for 1024-bit keys, check for 1024 bits, not 128
7125 bytes. This allows Tor to correctly discard keys of length 1017
7126 through 1023. Bugfix on 0.0.9pre5.
7129 - Relays now log the reason for publishing a new relay descriptor,
7130 so we have a better chance of hunting down instances of bug 1810.
7131 Resolves ticket 3252.
7132 - Revise most log messages that refer to nodes by nickname to
7133 instead use the "$key=nickname at address" format. This should be
7134 more useful, especially since nicknames are less and less likely
7135 to be unique. Resolves ticket 3045.
7136 - Log (at info level) when purging pieces of hidden-service-client
7137 state because of SIGNAL NEWNYM.
7140 - Remove undocumented option "-F" from tor-resolve: it hasn't done
7141 anything since 0.2.1.16-rc.
7144 Changes in version 0.2.2.27-beta - 2011-05-18
7145 Tor 0.2.2.27-beta fixes a bridge-related stability bug in the previous
7146 release, and also adds a few more general bugfixes.
7149 - Fix a crash bug when changing bridges in a running Tor process.
7150 Fixes bug 3213; bugfix on 0.2.2.26-beta.
7151 - When the controller configures a new bridge, don't wait 10 to 60
7152 seconds before trying to fetch its descriptor. Bugfix on
7153 0.2.0.3-alpha; fixes bug 3198 (suggested by 2355).
7156 - Require that onion keys have exponent 65537 in microdescriptors too.
7157 Fixes more of bug 3207; bugfix on 0.2.2.26-beta.
7158 - Tor used to limit HttpProxyAuthenticator values to 48 characters.
7159 Changed the limit to 512 characters by removing base64 newlines.
7160 Fixes bug 2752. Fix by Michael Yakubovich.
7161 - When a client starts or stops using bridges, never use a circuit
7162 that was built before the configuration change. This behavior could
7163 put at risk a user who uses bridges to ensure that her traffic
7164 only goes to the chosen addresses. Bugfix on 0.2.0.3-alpha; fixes
7168 Changes in version 0.2.2.26-beta - 2011-05-17
7169 Tor 0.2.2.26-beta fixes a variety of potential privacy problems. It
7170 also introduces a new "socksport auto" approach that should make it
7171 easier to run multiple Tors on the same system, and does a lot of
7172 cleanup to get us closer to a release candidate.
7174 o Security/privacy fixes:
7175 - Replace all potentially sensitive memory comparison operations
7176 with versions whose runtime does not depend on the data being
7177 compared. This will help resist a class of attacks where an
7178 adversary can use variations in timing information to learn
7179 sensitive data. Fix for one case of bug 3122. (Safe memcmp
7180 implementation by Robert Ransom based partially on code by DJB.)
7181 - When receiving a hidden service descriptor, check that it is for
7182 the hidden service we wanted. Previously, Tor would store any
7183 hidden service descriptors that a directory gave it, whether it
7184 wanted them or not. This wouldn't have let an attacker impersonate
7185 a hidden service, but it did let directories pre-seed a client
7186 with descriptors that it didn't want. Bugfix on 0.0.6.
7187 - On SIGHUP, do not clear out all TrackHostExits mappings, client
7188 DNS cache entries, and virtual address mappings: that's what
7189 NEWNYM is for. Fixes bug 1345; bugfix on 0.1.0.1-rc.
7192 - The options SocksPort, ControlPort, and so on now all accept a
7193 value "auto" that opens a socket on an OS-selected port. A
7194 new ControlPortWriteToFile option tells Tor to write its
7195 actual control port or ports to a chosen file. If the option
7196 ControlPortFileGroupReadable is set, the file is created as
7197 group-readable. Now users can run two Tor clients on the same
7198 system without needing to manually mess with parameters. Resolves
7199 part of ticket 3076.
7200 - Set SO_REUSEADDR on all sockets, not just listeners. This should
7201 help busy exit nodes avoid running out of useable ports just
7202 because all the ports have been used in the near past. Resolves
7206 - New "GETINFO net/listeners/(type)" controller command to return
7207 a list of addresses and ports that are bound for listeners for a
7208 given connection type. This is useful when the user has configured
7209 "SocksPort auto" and the controller needs to know which port got
7210 chosen. Resolves another part of ticket 3076.
7211 - Add a new ControlSocketsGroupWritable configuration option: when
7212 it is turned on, ControlSockets are group-writeable by the default
7213 group of the current user. Patch by Jérémy Bobbio; implements
7215 - Tor now refuses to create a ControlSocket in a directory that is
7216 world-readable (or group-readable if ControlSocketsGroupWritable
7217 is 0). This is necessary because some operating systems do not
7218 enforce permissions on an AF_UNIX sockets. Permissions on the
7219 directory holding the socket, however, seems to work everywhere.
7220 - Rate-limit a warning about failures to download v2 networkstatus
7221 documents. Resolves part of bug 1352.
7222 - Backport code from 0.2.3.x that allows directory authorities to
7223 clean their microdescriptor caches. Needed to resolve bug 2230.
7224 - When an HTTPS proxy reports "403 Forbidden", we now explain
7225 what it means rather than calling it an unexpected status code.
7226 Closes bug 2503. Patch from Michael Yakubovich.
7227 - Update to the May 1 2011 Maxmind GeoLite Country database.
7230 - Authorities now clean their microdesc cache periodically and when
7231 reading from disk initially, not only when adding new descriptors.
7232 This prevents a bug where we could lose microdescriptors. Bugfix
7233 on 0.2.2.6-alpha. Fixes bug 2230.
7234 - Do not crash when our configuration file becomes unreadable, for
7235 example due to a permissions change, between when we start up
7236 and when a controller calls SAVECONF. Fixes bug 3135; bugfix
7238 - Avoid a bug that would keep us from replacing a microdescriptor
7239 cache on Windows. (We would try to replace the file while still
7240 holding it open. That's fine on Unix, but Windows doesn't let us
7241 do that.) Bugfix on 0.2.2.6-alpha; bug found by wanoskarnet.
7242 - Add missing explanations for the authority-related torrc options
7243 RephistTrackTime, BridgePassword, and V3AuthUseLegacyKey in the
7244 man page. Resolves issue 2379.
7245 - As an authority, do not upload our own vote or signature set to
7246 ourself. It would tell us nothing new, and as of 0.2.2.24-alpha,
7247 it would get flagged as a duplicate. Resolves bug 3026.
7248 - Accept hidden service descriptors if we think we might be a hidden
7249 service directory, regardless of what our consensus says. This
7250 helps robustness, since clients and hidden services can sometimes
7251 have a more up-to-date view of the network consensus than we do,
7252 and if they think that the directory authorities list us a HSDir,
7253 we might actually be one. Related to bug 2732; bugfix on
7255 - When a controller changes TrackHostExits, remove mappings for
7256 hosts that should no longer have their exits tracked. Bugfix on
7258 - When a controller changes VirtualAddrNetwork, remove any mappings
7259 for hosts that were automapped to the old network. Bugfix on
7261 - When a controller changes one of the AutomapHosts* options, remove
7262 any mappings for hosts that should no longer be automapped. Bugfix
7264 - Do not reset the bridge descriptor download status every time we
7265 re-parse our configuration or get a configuration change. Fixes
7266 bug 3019; bugfix on 0.2.0.3-alpha.
7268 o Minor bugfixes (code cleanup):
7269 - When loading the microdesc journal, remember its current size.
7270 In 0.2.2, this helps prevent the microdesc journal from growing
7271 without limit on authorities (who are the only ones to use it in
7272 0.2.2). Fixes a part of bug 2230; bugfix on 0.2.2.6-alpha.
7273 Fix posted by "cypherpunks."
7274 - The microdesc journal is supposed to get rebuilt only if it is
7275 at least _half_ the length of the store, not _twice_ the length
7276 of the store. Bugfix on 0.2.2.6-alpha; fixes part of bug 2230.
7277 - Fix a potential null-pointer dereference while computing a
7278 consensus. Bugfix on tor-0.2.0.3-alpha, found with the help of
7280 - Avoid a possible null-pointer dereference when rebuilding the mdesc
7281 cache without actually having any descriptors to cache. Bugfix on
7282 0.2.2.6-alpha. Issue discovered using clang's static analyzer.
7283 - If we fail to compute the identity digest of a v3 legacy keypair,
7284 warn, and don't use a buffer-full of junk instead. Bugfix on
7285 0.2.1.1-alpha; fixes bug 3106.
7286 - Resolve an untriggerable issue in smartlist_string_num_isin(),
7287 where if the function had ever in the future been used to check
7288 for the presence of a too-large number, it would have given an
7289 incorrect result. (Fortunately, we only used it for 16-bit
7290 values.) Fixes bug 3175; bugfix on 0.1.0.1-rc.
7291 - Require that introduction point keys and onion handshake keys
7292 have a public exponent of 65537. Starts to fix bug 3207; bugfix
7296 - Caches no longer download and serve v2 networkstatus documents
7297 unless FetchV2Networkstatus flag is set: these documents haven't
7298 haven't been used by clients or relays since 0.2.0.x. Resolves
7302 Changes in version 0.2.3.1-alpha - 2011-05-05
7303 Tor 0.2.3.1-alpha adds some new experimental features, including support
7304 for an improved network IO backend, IOCP networking on Windows,
7305 microdescriptor caching, "fast-start" support for streams, and automatic
7306 home router configuration. There are also numerous internal improvements
7307 to try to make the code easier for developers to work with.
7309 This is the first alpha release in a new series, so expect there to be
7310 bugs. Users who would rather test out a more stable branch should
7311 stay with 0.2.2.x for now.
7314 - Tor can now optionally build with the "bufferevents" buffered IO
7315 backend provided by Libevent 2. To use this feature, make sure you
7316 have the latest possible version of Libevent, and pass the
7317 --enable-bufferevents flag to configure when building Tor from
7318 source. This feature will make our networking code more flexible,
7319 let us stack layers on each other, and let us use more efficient
7320 zero-copy transports where available.
7321 - As an experimental feature, Tor can use IOCP for networking on Windows.
7322 Once this code is tuned and optimized, it promises much better
7323 performance than the select-based backend we've used in the past. To
7324 try this feature, you must build Tor with Libevent 2, configure Tor
7325 with the "bufferevents" buffered IO backend, and add "DisableIOCP 0" to
7326 your torrc. There are known bugs here: only try this if you can help
7327 debug it as it breaks.
7328 - The EntryNodes option can now include country codes like {de} or IP
7329 addresses or network masks. Previously we had disallowed these options
7330 because we didn't have an efficient way to keep the list up to
7331 date. Fixes bug 1982, but see bug 2798 for an unresolved issue here.
7332 - Exit nodes now accept and queue data on not-yet-connected streams.
7333 Previously, the client wasn't allowed to send data until the stream was
7334 connected, which slowed down all connections. This change will enable
7335 clients to perform a "fast-start" on streams and send data without
7336 having to wait for a confirmation that the stream has opened. (Patch
7337 from Ian Goldberg; implements the server side of Proposal 174.)
7338 - Tor now has initial support for automatic port mapping on the many
7339 home routers that support NAT-PMP or UPnP. (Not yet supported on
7340 Windows). To build the support code, you'll need to have libnatpnp
7341 library and/or the libminiupnpc library, and you'll need to enable the
7342 feature specifically by passing "--enable-upnp" and/or
7343 "--enable-natpnp" to configure. To turn it on, use the new
7344 PortForwarding option.
7345 - Caches now download, cache, and serve multiple "flavors" of the
7346 consensus, including a flavor that describes microdescriptors.
7347 - Caches now download, cache, and serve microdescriptors -- small
7348 summaries of router descriptors that are authenticated by all of the
7349 directory authorities. Once enough caches are running this code,
7350 clients will be able to save significant amounts of directory bandwidth
7351 by downloading microdescriptors instead of router descriptors.
7354 - Make logging resolution configurable with a new LogTimeGranularity
7355 option, and change the default from 1 millisecond to 1 second.
7356 Implements enhancement 1668.
7357 - We log which torrc file we're using on startup. Implements ticket
7359 - Ordinarily, Tor does not count traffic from private addresses (like
7360 127.0.0.1 or 10.0.0.1) when calculating rate limits or accounting.
7361 There is now a new option, CountPrivateBandwidth, to disable this
7362 behavior. Patch from Daniel Cagara.
7363 - New --enable-static-tor configure option for building Tor as
7364 statically as possible. Idea, general hackery and thoughts from
7365 Alexei Czeskis, John Gilmore, Jacob Appelbaum. Implements ticket
7367 - If you set the NumCPUs option to 0, Tor will now try to detect how
7368 many CPUs you have. This is the new default behavior.
7369 - Turn on directory request statistics by default and include them in
7370 extra-info descriptors. Don't break if we have no GeoIP database.
7371 - Relays that set "ConnDirectionStatistics 1" write statistics on the
7372 bidirectional use of connections to disk every 24 hours.
7373 - Add a GeoIP file digest to the extra-info descriptor. Implements
7375 - The NodeFamily option -- which let you declare that you want to
7376 consider nodes to be part of a family whether they list themselves
7377 that way or not -- now allows IP address ranges and country codes.
7378 - Add a new 'Heartbeat' log message type to periodically log a message
7379 describing Tor's status at level Notice. This feature is meant for
7380 operators who log at notice, and want to make sure that their Tor
7381 server is still working. Implementation by George Kadianakis.
7383 o Minor bugfixes (on 0.2.2.25-alpha):
7384 - When loading the microdesc journal, remember its current size.
7385 In 0.2.2, this helps prevent the microdesc journal from growing
7386 without limit on authorities (who are the only ones to use it in
7387 0.2.2). Fixes a part of bug 2230; bugfix on 0.2.2.6-alpha.
7388 Fix posted by "cypherpunks."
7389 - The microdesc journal is supposed to get rebuilt only if it is
7390 at least _half_ the length of the store, not _twice_ the length
7391 of the store. Bugfix on 0.2.2.6-alpha; fixes part of bug 2230.
7392 - If as an authority we fail to compute the identity digest of a v3
7393 legacy keypair, warn, and don't use a buffer-full of junk instead.
7394 Bugfix on 0.2.1.1-alpha; fixes bug 3106.
7395 - Authorities now clean their microdesc cache periodically and when
7396 reading from disk initially, not only when adding new descriptors.
7397 This prevents a bug where we could lose microdescriptors. Bugfix
7400 o Minor features (controller):
7401 - Add a new SIGNAL event to the controller interface so that
7402 controllers can be notified when Tor handles a signal. Resolves
7403 issue 1955. Patch by John Brooks.
7404 - Add a new GETINFO option to get total bytes read and written. Patch
7405 from pipe, revised by atagar. Resolves ticket 2345.
7406 - Implement some GETINFO controller fields to provide information about
7407 the Tor process's pid, euid, username, and resource limits.
7410 - Our build system requires automake 1.6 or later to create the
7411 Makefile.in files. Previously, you could have used 1.4.
7412 This only affects developers and people building Tor from git;
7413 people who build Tor from the source distribution without changing
7414 the Makefile.am files should be fine.
7415 - Our autogen.sh script uses autoreconf to launch autoconf, automake, and
7416 so on. This is more robust against some of the failure modes
7417 associated with running the autotools pieces on their own.
7419 o Minor packaging issues:
7420 - On OpenSUSE, create the /var/run/tor directory on startup if it is not
7421 already created. Patch from Andreas Stieger. Fixes bug 2573.
7423 o Code simplifications and refactoring:
7424 - A major revision to our internal node-selecting and listing logic.
7425 Tor already had at least two major ways to look at the question of
7426 "which Tor servers do we know about": a list of router descriptors,
7427 and a list of entries in the current consensus. With
7428 microdescriptors, we're adding a third. Having so many systems
7429 without an abstraction layer over them was hurting the codebase.
7430 Now, we have a new "node_t" abstraction that presents a consistent
7431 interface to a client's view of a Tor node, and holds (nearly) all
7432 of the mutable state formerly in routerinfo_t and routerstatus_t.
7433 - The helper programs tor-gencert, tor-resolve, and tor-checkkey
7434 no longer link against Libevent: they never used it, but
7435 our library structure used to force them to link it.
7438 - Remove some old code to work around even older versions of Tor that
7439 used forked processes to handle DNS requests. Such versions of Tor
7440 are no longer in use as servers.
7442 o Documentation fixes:
7443 - Correct a broken faq link in the INSTALL file. Fixes bug 2307.
7444 - Add missing documentation for the authority-related torrc options
7445 RephistTrackTime, BridgePassword, and V3AuthUseLegacyKey. Resolves
7449 Changes in version 0.2.2.25-alpha - 2011-04-29
7450 Tor 0.2.2.25-alpha fixes many bugs: hidden service clients are more
7451 robust, routers no longer overreport their bandwidth, Win7 should crash
7452 a little less, and NEWNYM (as used by Vidalia's "new identity" button)
7453 now prevents hidden service-related activity from being linkable. It
7454 provides more information to Vidalia so you can see if your bridge is
7455 working. Also, 0.2.2.25-alpha revamps the Entry/Exit/ExcludeNodes and
7456 StrictNodes configuration options to make them more reliable, more
7457 understandable, and more regularly applied. If you use those options,
7458 please see the revised documentation for them in the manual page.
7461 - Relays were publishing grossly inflated bandwidth values because
7462 they were writing their state files wrong--now they write the
7463 correct value. Also, resume reading bandwidth history from the
7464 state file correctly. Fixes bug 2704; bugfix on 0.2.2.23-alpha.
7465 - Improve hidden service robustness: When we find that we have
7466 extended a hidden service's introduction circuit to a relay not
7467 listed as an introduction point in the HS descriptor we currently
7468 have, retry with an introduction point from the current
7469 descriptor. Previously we would just give up. Fixes bugs 1024 and
7470 1930; bugfix on 0.2.0.10-alpha.
7471 - Clients now stop trying to use an exit node associated with a given
7472 destination by TrackHostExits if they fail to reach that exit node.
7473 Fixes bug 2999. Bugfix on 0.2.0.20-rc.
7474 - Fix crash bug on platforms where gmtime and localtime can return
7475 NULL. Windows 7 users were running into this one. Fixes part of bug
7476 2077. Bugfix on all versions of Tor. Found by boboper.
7478 o Security and stability fixes:
7479 - Don't double-free a parsable, but invalid, microdescriptor, even if
7480 it is followed in the blob we're parsing by an unparsable
7481 microdescriptor. Fixes an issue reported in a comment on bug 2954.
7482 Bugfix on 0.2.2.6-alpha; fix by "cypherpunks".
7483 - If the Nickname configuration option isn't given, Tor would pick a
7484 nickname based on the local hostname as the nickname for a relay.
7485 Because nicknames are not very important in today's Tor and the
7486 "Unnamed" nickname has been implemented, this is now problematic
7487 behavior: It leaks information about the hostname without being
7488 useful at all. Fixes bug 2979; bugfix on 0.1.2.2-alpha, which
7489 introduced the Unnamed nickname. Reported by tagnaq.
7490 - Fix an uncommon assertion failure when running with DNSPort under
7491 heavy load. Fixes bug 2933; bugfix on 0.2.0.1-alpha.
7492 - Avoid linkability based on cached hidden service descriptors: forget
7493 all hidden service descriptors cached as a client when processing a
7494 SIGNAL NEWNYM command. Fixes bug 3000; bugfix on 0.0.6.
7497 - Export GeoIP information on bridge usage to controllers even if we
7498 have not yet been running for 24 hours. Now Vidalia bridge operators
7499 can get more accurate and immediate feedback about their
7500 contributions to the network.
7502 o Major features and bugfixes (node selection):
7503 - Revise and reconcile the meaning of the ExitNodes, EntryNodes,
7504 ExcludeEntryNodes, ExcludeExitNodes, ExcludeNodes, and StrictNodes
7505 options. Previously, we had been ambiguous in describing what
7506 counted as an "exit" node, and what operations exactly "StrictNodes
7507 0" would permit. This created confusion when people saw nodes built
7508 through unexpected circuits, and made it hard to tell real bugs from
7509 surprises. Now the intended behavior is:
7510 . "Exit", in the context of ExitNodes and ExcludeExitNodes, means
7511 a node that delivers user traffic outside the Tor network.
7512 . "Entry", in the context of EntryNodes, means a node used as the
7513 first hop of a multihop circuit. It doesn't include direct
7514 connections to directory servers.
7515 . "ExcludeNodes" applies to all nodes.
7516 . "StrictNodes" changes the behavior of ExcludeNodes only. When
7517 StrictNodes is set, Tor should avoid all nodes listed in
7518 ExcludeNodes, even when it will make user requests fail. When
7519 StrictNodes is *not* set, then Tor should follow ExcludeNodes
7520 whenever it can, except when it must use an excluded node to
7521 perform self-tests, connect to a hidden service, provide a
7522 hidden service, fulfill a .exit request, upload directory
7523 information, or fetch directory information.
7524 Collectively, the changes to implement the behavior fix bug 1090.
7525 - ExcludeNodes now takes precedence over EntryNodes and ExitNodes: if
7526 a node is listed in both, it's treated as excluded.
7527 - ExcludeNodes now applies to directory nodes -- as a preference if
7528 StrictNodes is 0, or an absolute requirement if StrictNodes is 1.
7529 Don't exclude all the directory authorities and set StrictNodes to 1
7530 unless you really want your Tor to break.
7531 - ExcludeNodes and ExcludeExitNodes now override exit enclaving.
7532 - ExcludeExitNodes now overrides .exit requests.
7533 - We don't use bridges listed in ExcludeNodes.
7534 - When StrictNodes is 1:
7535 . We now apply ExcludeNodes to hidden service introduction points
7536 and to rendezvous points selected by hidden service users. This
7537 can make your hidden service less reliable: use it with caution!
7538 . If we have used ExcludeNodes on ourself, do not try relay
7539 reachability self-tests.
7540 . If we have excluded all the directory authorities, we will not
7541 even try to upload our descriptor if we're a relay.
7542 . Do not honor .exit requests to an excluded node.
7543 - Remove a misfeature that caused us to ignore the Fast/Stable flags
7544 when ExitNodes is set. Bugfix on 0.2.2.7-alpha.
7545 - When the set of permitted nodes changes, we now remove any mappings
7546 introduced via TrackExitHosts to now-excluded nodes. Bugfix on
7548 - We never cannibalize a circuit that had excluded nodes on it, even
7549 if StrictNodes is 0. Bugfix on 0.1.0.1-rc.
7550 - Revert a change where we would be laxer about attaching streams to
7551 circuits than when building the circuits. This was meant to prevent
7552 a set of bugs where streams were never attachable, but our improved
7553 code here should make this unnecessary. Bugfix on 0.2.2.7-alpha.
7554 - Keep track of how many times we launch a new circuit to handle a
7555 given stream. Too many launches could indicate an inconsistency
7556 between our "launch a circuit to handle this stream" logic and our
7557 "attach this stream to one of the available circuits" logic.
7558 - Improve log messages related to excluded nodes.
7561 - Fix a spurious warning when moving from a short month to a long
7562 month on relays with month-based BandwidthAccounting. Bugfix on
7563 0.2.2.17-alpha; fixes bug 3020.
7564 - When a client finds that an origin circuit has run out of 16-bit
7565 stream IDs, we now mark it as unusable for new streams. Previously,
7566 we would try to close the entire circuit. Bugfix on 0.0.6.
7567 - Add a forgotten cast that caused a compile warning on OS X 10.6.
7568 Bugfix on 0.2.2.24-alpha.
7569 - Be more careful about reporting the correct error from a failed
7570 connect() system call. Under some circumstances, it was possible to
7571 look at an incorrect value for errno when sending the end reason.
7572 Bugfix on 0.1.0.1-rc.
7573 - Correctly handle an "impossible" overflow cases in connection byte
7574 counting, where we write or read more than 4GB on an edge connection
7575 in a single second. Bugfix on 0.1.2.8-beta.
7576 - Correct the warning displayed when a rendezvous descriptor exceeds
7577 the maximum size. Fixes bug 2750; bugfix on 0.2.1.5-alpha. Found by
7579 - Clients and hidden services now use HSDir-flagged relays for hidden
7580 service descriptor downloads and uploads even if the relays have no
7581 DirPort set and the client has disabled TunnelDirConns. This will
7582 eventually allow us to give the HSDir flag to relays with no
7583 DirPort. Fixes bug 2722; bugfix on 0.2.1.6-alpha.
7584 - Downgrade "no current certificates known for authority" message from
7585 Notice to Info. Fixes bug 2899; bugfix on 0.2.0.10-alpha.
7586 - Make the SIGNAL DUMP control-port command work on FreeBSD. Fixes bug
7587 2917. Bugfix on 0.1.1.1-alpha.
7588 - Only limit the lengths of single HS descriptors, even when multiple
7589 HS descriptors are published to an HSDir relay in a single POST
7590 operation. Fixes bug 2948; bugfix on 0.2.1.5-alpha. Found by hsdir.
7591 - Write the current time into the LastWritten line in our state file,
7592 rather than the time from the previous write attempt. Also, stop
7593 trying to use a time of -1 in our log statements. Fixes bug 3039;
7594 bugfix on 0.2.2.14-alpha.
7595 - Be more consistent in our treatment of file system paths. "~" should
7596 get expanded to the user's home directory in the Log config option.
7597 Fixes bug 2971; bugfix on 0.2.0.1-alpha, which introduced the
7598 feature for the -f and --DataDirectory options.
7601 - Make sure every relay writes a state file at least every 12 hours.
7602 Previously, a relay could go for weeks without writing its state
7603 file, and on a crash could lose its bandwidth history, capacity
7604 estimates, client country statistics, and so on. Addresses bug 3012.
7605 - Send END_STREAM_REASON_NOROUTE in response to EHOSTUNREACH errors.
7606 Clients before 0.2.1.27 didn't handle NOROUTE correctly, but such
7607 clients are already deprecated because of security bugs.
7608 - Don't allow v0 hidden service authorities to act as clients.
7609 Required by fix for bug 3000.
7610 - Ignore SIGNAL NEWNYM commands on relay-only Tor instances. Required
7611 by fix for bug 3000.
7612 - Ensure that no empty [dirreq-](read|write)-history lines are added
7613 to an extrainfo document. Implements ticket 2497.
7615 o Code simplification and refactoring:
7616 - Remove workaround code to handle directory responses from servers
7617 that had bug 539 (they would send HTTP status 503 responses _and_
7618 send a body too). Since only server versions before
7619 0.2.0.16-alpha/0.1.2.19 were affected, there is no longer reason to
7620 keep the workaround in place.
7621 - Remove the old 'fuzzy time' logic. It was supposed to be used for
7622 handling calculations where we have a known amount of clock skew and
7623 an allowed amount of unknown skew. But we only used it in three
7624 places, and we never adjusted the known/unknown skew values. This is
7625 still something we might want to do someday, but if we do, we'll
7626 want to do it differently.
7627 - Avoid signed/unsigned comparisons by making SIZE_T_CEILING unsigned.
7628 None of the cases where we did this before were wrong, but by making
7629 this change we avoid warnings. Fixes bug 2475; bugfix on 0.2.1.28.
7630 - Use GetTempDir to find the proper temporary directory location on
7631 Windows when generating temporary files for the unit tests. Patch by
7635 Changes in version 0.2.2.24-alpha - 2011-04-08
7636 Tor 0.2.2.24-alpha fixes a variety of bugs, including a big bug that
7637 prevented Tor clients from effectively using "multihomed" bridges,
7638 that is, bridges that listen on multiple ports or IP addresses so users
7639 can continue to use some of their addresses even if others get blocked.
7642 - Fix a bug where bridge users who configure the non-canonical
7643 address of a bridge automatically switch to its canonical
7644 address. If a bridge listens at more than one address, it should be
7645 able to advertise those addresses independently and any non-blocked
7646 addresses should continue to work. Bugfix on Tor 0.2.0.x. Fixes
7648 - If you configured Tor to use bridge A, and then quit and
7649 configured Tor to use bridge B instead, it would happily continue
7650 to use bridge A if it's still reachable. While this behavior is
7651 a feature if your goal is connectivity, in some scenarios it's a
7652 dangerous bug. Bugfix on Tor 0.2.0.1-alpha; fixes bug 2511.
7653 - Directory authorities now use data collected from their own
7654 uptime observations when choosing whether to assign the HSDir flag
7655 to relays, instead of trusting the uptime value the relay reports in
7656 its descriptor. This change helps prevent an attack where a small
7657 set of nodes with frequently-changing identity keys can blackhole
7658 a hidden service. (Only authorities need upgrade; others will be
7659 fine once they do.) Bugfix on 0.2.0.10-alpha; fixes bug 2709.
7662 - When we restart our relay, we might get a successful connection
7663 from the outside before we've started our reachability tests,
7664 triggering a warning: "ORPort found reachable, but I have no
7665 routerinfo yet. Failing to inform controller of success." This
7666 bug was harmless unless Tor is running under a controller
7667 like Vidalia, in which case the controller would never get a
7668 REACHABILITY_SUCCEEDED status event. Bugfix on 0.1.2.6-alpha;
7670 - Make directory authorities more accurate at recording when
7671 relays that have failed several reachability tests became
7672 unreachable, so we can provide more accuracy at assigning Stable,
7673 Guard, HSDir, etc flags. Bugfix on 0.2.0.6-alpha. Resolves bug 2716.
7674 - Fix an issue that prevented static linking of libevent on
7675 some platforms (notably Linux). Fixes bug 2698; bugfix on
7676 versions 0.2.1.23/0.2.2.8-alpha (the versions introducing
7677 the --with-static-libevent configure option).
7678 - We now ask the other side of a stream (the client or the exit)
7679 for more data on that stream when the amount of queued data on
7680 that stream dips low enough. Previously, we wouldn't ask the
7681 other side for more data until either it sent us more data (which
7682 it wasn't supposed to do if it had exhausted its window!) or we
7683 had completely flushed all our queued data. This flow control fix
7684 should improve throughput. Fixes bug 2756; bugfix on the earliest
7685 released versions of Tor (svn commit r152).
7686 - Avoid a double-mark-for-free warning when failing to attach a
7687 transparent proxy connection. (We thought we had fixed this in
7688 0.2.2.23-alpha, but it turns out our fix was checking the wrong
7689 connection.) Fixes bug 2757; bugfix on 0.1.2.1-alpha (the original
7690 bug) and 0.2.2.23-alpha (the incorrect fix).
7691 - When warning about missing zlib development packages during compile,
7692 give the correct package names. Bugfix on 0.2.0.1-alpha.
7695 - Directory authorities now log the source of a rejected POSTed v3
7697 - Make compilation with clang possible when using
7698 --enable-gcc-warnings by removing two warning options that clang
7699 hasn't implemented yet and by fixing a few warnings. Implements
7701 - When expiring circuits, use microsecond timers rather than
7702 one-second timers. This can avoid an unpleasant situation where a
7703 circuit is launched near the end of one second and expired right
7704 near the beginning of the next, and prevent fluctuations in circuit
7706 - Use computed circuit-build timeouts to decide when to launch
7707 parallel introduction circuits for hidden services. (Previously,
7708 we would retry after 15 seconds.)
7709 - Update to the April 1 2011 Maxmind GeoLite Country database.
7712 - Create the /var/run/tor directory on startup on OpenSUSE if it is
7713 not already created. Patch from Andreas Stieger. Fixes bug 2573.
7715 o Documentation changes:
7716 - Modernize the doxygen configuration file slightly. Fixes bug 2707.
7717 - Resolve all doxygen warnings except those for missing documentation.
7719 - Add doxygen documentation for more functions, fields, and types.
7722 Changes in version 0.2.2.23-alpha - 2011-03-08
7723 Tor 0.2.2.23-alpha lets relays record their bandwidth history so when
7724 they restart they don't lose their bandwidth capacity estimate. This
7725 release also fixes a diverse set of user-facing bugs, ranging from
7726 relays overrunning their rate limiting to clients falsely warning about
7727 clock skew to bridge descriptor leaks by our bridge directory authority.
7730 - Stop sending a CLOCK_SKEW controller status event whenever
7731 we fetch directory information from a relay that has a wrong clock.
7732 Instead, only inform the controller when it's a trusted authority
7733 that claims our clock is wrong. Bugfix on 0.1.2.6-alpha; fixes
7734 the rest of bug 1074.
7735 - Fix an assert in parsing router descriptors containing IPv6
7736 addresses. This one took down the directory authorities when
7737 somebody tried some experimental code. Bugfix on 0.2.1.3-alpha.
7738 - Make the bridge directory authority refuse to answer directory
7739 requests for "all" descriptors. It used to include bridge
7740 descriptors in its answer, which was a major information leak.
7741 Found by "piebeer". Bugfix on 0.2.0.3-alpha.
7742 - If relays set RelayBandwidthBurst but not RelayBandwidthRate,
7743 Tor would ignore their RelayBandwidthBurst setting,
7744 potentially using more bandwidth than expected. Bugfix on
7745 0.2.0.1-alpha. Reported by Paul Wouters. Fixes bug 2470.
7746 - Ignore and warn if the user mistakenly sets "PublishServerDescriptor
7747 hidserv" in her torrc. The 'hidserv' argument never controlled
7748 publication of hidden service descriptors. Bugfix on 0.2.0.1-alpha.
7751 - Relays now save observed peak bandwidth throughput rates to their
7752 state file (along with total usage, which was already saved)
7753 so that they can determine their correct estimated bandwidth on
7754 restart. Resolves bug 1863, where Tor relays would reset their
7755 estimated bandwidth to 0 after restarting.
7756 - Directory authorities now take changes in router IP address and
7757 ORPort into account when determining router stability. Previously,
7758 if a router changed its IP or ORPort, the authorities would not
7759 treat it as having any downtime for the purposes of stability
7760 calculation, whereas clients would experience downtime since the
7761 change could take a while to propagate to them. Resolves issue 1035.
7762 - Enable Address Space Layout Randomization (ASLR) and Data Execution
7763 Prevention (DEP) by default on Windows to make it harder for
7764 attackers to exploit vulnerabilities. Patch from John Brooks.
7766 o Minor bugfixes (on 0.2.1.x and earlier):
7767 - Fix a rare crash bug that could occur when a client was configured
7768 with a large number of bridges. Fixes bug 2629; bugfix on
7769 0.2.1.2-alpha. Bugfix by trac user "shitlei".
7770 - Avoid a double mark-for-free warning when failing to attach a
7771 transparent proxy connection. Bugfix on 0.1.2.1-alpha. Fixes
7773 - Correctly detect failure to allocate an OpenSSL BIO. Fixes bug 2378;
7774 found by "cypherpunks". This bug was introduced before the first
7775 Tor release, in svn commit r110.
7776 - Country codes aren't supported in EntryNodes until 0.2.3.x, so
7777 don't mention them in the manpage. Fixes bug 2450; issue
7778 spotted by keb and G-Lo.
7779 - Fix a bug in bandwidth history state parsing that could have been
7780 triggered if a future version of Tor ever changed the timing
7781 granularity at which bandwidth history is measured. Bugfix on
7783 - When a relay decides that its DNS is too broken for it to serve
7784 as an exit server, it advertised itself as a non-exit, but
7785 continued to act as an exit. This could create accidental
7786 partitioning opportunities for users. Instead, if a relay is
7787 going to advertise reject *:* as its exit policy, it should
7788 really act with exit policy "reject *:*". Fixes bug 2366.
7789 Bugfix on Tor 0.1.2.5-alpha. Bugfix by user "postman" on trac.
7790 - In the special case where you configure a public exit relay as your
7791 bridge, Tor would be willing to use that exit relay as the last
7792 hop in your circuit as well. Now we fail that circuit instead.
7793 Bugfix on 0.2.0.12-alpha. Fixes bug 2403. Reported by "piebeer".
7794 - Fix a bug with our locking implementation on Windows that couldn't
7795 correctly detect when a file was already locked. Fixes bug 2504,
7796 bugfix on 0.2.1.6-alpha.
7797 - Fix IPv6-related connect() failures on some platforms (BSD, OS X).
7798 Bugfix on 0.2.0.3-alpha; fixes first part of bug 2660. Patch by
7800 - Set target port in get_interface_address6() correctly. Bugfix
7801 on 0.1.1.4-alpha and 0.2.0.3-alpha; fixes second part of bug 2660.
7802 - Directory authorities are now more robust to hops back in time
7803 when calculating router stability. Previously, if a run of uptime
7804 or downtime appeared to be negative, the calculation could give
7805 incorrect results. Bugfix on 0.2.0.6-alpha; noticed when fixing
7807 - Fix an assert that got triggered when using the TestingTorNetwork
7808 configuration option and then issuing a GETINFO config-text control
7809 command. Fixes bug 2250; bugfix on 0.2.1.2-alpha.
7811 o Minor bugfixes (on 0.2.2.x):
7812 - Clients should not weight BadExit nodes as Exits in their node
7813 selection. Similarly, directory authorities should not count BadExit
7814 bandwidth as Exit bandwidth when computing bandwidth-weights.
7815 Bugfix on 0.2.2.10-alpha; fixes bug 2203.
7816 - Correctly clear our dir_read/dir_write history when there is an
7817 error parsing any bw history value from the state file. Bugfix on
7819 - Resolve a bug in verifying signatures of directory objects
7820 with digests longer than SHA1. Bugfix on 0.2.2.20-alpha.
7821 Fixes bug 2409. Found by "piebeer".
7822 - Bridge authorities no longer crash on SIGHUP when they try to
7823 publish their relay descriptor to themselves. Fixes bug 2572. Bugfix
7827 - Log less aggressively about circuit timeout changes, and improve
7828 some other circuit timeout messages. Resolves bug 2004.
7829 - Log a little more clearly about the times at which we're no longer
7830 accepting new connections. Resolves bug 2181.
7831 - Reject attempts at the client side to open connections to private
7832 IP addresses (like 127.0.0.1, 10.0.0.1, and so on) with
7833 a randomly chosen exit node. Attempts to do so are always
7834 ill-defined, generally prevented by exit policies, and usually
7835 in error. This will also help to detect loops in transparent
7836 proxy configurations. You can disable this feature by setting
7837 "ClientRejectInternalAddresses 0" in your torrc.
7838 - Always treat failure to allocate an RSA key as an unrecoverable
7840 - Update to the March 1 2011 Maxmind GeoLite Country database.
7842 o Minor features (log subsystem):
7843 - Add documentation for configuring logging at different severities in
7844 different log domains. We've had this feature since 0.2.1.1-alpha,
7845 but for some reason it never made it into the manpage. Fixes
7847 - Make it simpler to specify "All log domains except for A and B".
7848 Previously you needed to say "[*,~A,~B]". Now you can just say
7850 - Add a "LogMessageDomains 1" option to include the domains of log
7851 messages along with the messages. Without this, there's no way
7852 to use log domains without reading the source or doing a lot
7855 o Packaging changes:
7856 - Stop shipping the Tor specs files and development proposal documents
7857 in the tarball. They are now in a separate git repository at
7858 git://git.torproject.org/torspec.git
7861 Changes in version 0.2.1.30 - 2011-02-23
7862 Tor 0.2.1.30 fixes a variety of less critical bugs. The main other
7863 change is a slight tweak to Tor's TLS handshake that makes relays
7864 and bridges that run this new version reachable from Iran again.
7865 We don't expect this tweak will win the arms race long-term, but it
7866 buys us time until we roll out a better solution.
7869 - Stop sending a CLOCK_SKEW controller status event whenever
7870 we fetch directory information from a relay that has a wrong clock.
7871 Instead, only inform the controller when it's a trusted authority
7872 that claims our clock is wrong. Bugfix on 0.1.2.6-alpha; fixes
7873 the rest of bug 1074.
7874 - Fix a bounds-checking error that could allow an attacker to
7875 remotely crash a directory authority. Bugfix on 0.2.1.5-alpha.
7877 - If relays set RelayBandwidthBurst but not RelayBandwidthRate,
7878 Tor would ignore their RelayBandwidthBurst setting,
7879 potentially using more bandwidth than expected. Bugfix on
7880 0.2.0.1-alpha. Reported by Paul Wouters. Fixes bug 2470.
7881 - Ignore and warn if the user mistakenly sets "PublishServerDescriptor
7882 hidserv" in her torrc. The 'hidserv' argument never controlled
7883 publication of hidden service descriptors. Bugfix on 0.2.0.1-alpha.
7886 - Adjust our TLS Diffie-Hellman parameters to match those used by
7888 - Update to the February 1 2011 Maxmind GeoLite Country database.
7891 - Check for and reject overly long directory certificates and
7892 directory tokens before they have a chance to hit any assertions.
7893 Bugfix on 0.2.1.28. Found by "doorss".
7894 - Bring the logic that gathers routerinfos and assesses the
7895 acceptability of circuits into line. This prevents a Tor OP from
7896 getting locked in a cycle of choosing its local OR as an exit for a
7897 path (due to a .exit request) and then rejecting the circuit because
7898 its OR is not listed yet. It also prevents Tor clients from using an
7899 OR running in the same instance as an exit (due to a .exit request)
7900 if the OR does not meet the same requirements expected of an OR
7901 running elsewhere. Fixes bug 1859; bugfix on 0.1.0.1-rc.
7903 o Packaging changes:
7904 - Stop shipping the Tor specs files and development proposal documents
7905 in the tarball. They are now in a separate git repository at
7906 git://git.torproject.org/torspec.git
7907 - Do not include Git version tags as though they are SVN tags when
7908 generating a tarball from inside a repository that has switched
7909 between branches. Bugfix on 0.2.1.15-rc; fixes bug 2402.
7912 Changes in version 0.2.2.22-alpha - 2011-01-25
7913 Tor 0.2.2.22-alpha fixes a few more less-critical security issues. The
7914 main other change is a slight tweak to Tor's TLS handshake that makes
7915 relays and bridges that run this new version reachable from Iran again.
7916 We don't expect this tweak will win the arms race long-term, but it
7917 will buy us a bit more time until we roll out a better solution.
7920 - Fix a bounds-checking error that could allow an attacker to
7921 remotely crash a directory authority. Bugfix on 0.2.1.5-alpha.
7923 - Don't assert when changing from bridge to relay or vice versa
7924 via the controller. The assert happened because we didn't properly
7925 initialize our keys in this case. Bugfix on 0.2.2.18-alpha; fixes
7926 bug 2433. Reported by bastik.
7929 - Adjust our TLS Diffie-Hellman parameters to match those used by
7931 - Provide a log message stating which geoip file we're parsing
7932 instead of just stating that we're parsing the geoip file.
7933 Implements ticket 2432.
7936 - Check for and reject overly long directory certificates and
7937 directory tokens before they have a chance to hit any assertions.
7938 Bugfix on 0.2.1.28 / 0.2.2.20-alpha. Found by "doorss".
7941 Changes in version 0.2.2.21-alpha - 2011-01-15
7942 Tor 0.2.2.21-alpha includes all the patches from Tor 0.2.1.29, which
7943 continues our recent code security audit work. The main fix resolves
7944 a remote heap overflow vulnerability that can allow remote code
7945 execution (CVE-2011-0427). Other fixes address a variety of assert
7946 and crash bugs, most of which we think are hard to exploit remotely.
7948 o Major bugfixes (security), also included in 0.2.1.29:
7949 - Fix a heap overflow bug where an adversary could cause heap
7950 corruption. This bug probably allows remote code execution
7951 attacks. Reported by "debuger". Fixes CVE-2011-0427. Bugfix on
7953 - Prevent a denial-of-service attack by disallowing any
7954 zlib-compressed data whose compression factor is implausibly
7955 high. Fixes part of bug 2324; reported by "doorss".
7956 - Zero out a few more keys in memory before freeing them. Fixes
7957 bug 2384 and part of bug 2385. These key instances found by
7958 "cypherpunks", based on Andrew Case's report about being able
7959 to find sensitive data in Tor's memory space if you have enough
7960 permissions. Bugfix on 0.0.2pre9.
7962 o Major bugfixes (crashes), also included in 0.2.1.29:
7963 - Prevent calls to Libevent from inside Libevent log handlers.
7964 This had potential to cause a nasty set of crashes, especially
7965 if running Libevent with debug logging enabled, and running
7966 Tor with a controller watching for low-severity log messages.
7967 Bugfix on 0.1.0.2-rc. Fixes bug 2190.
7968 - Add a check for SIZE_T_MAX to tor_realloc() to try to avoid
7969 underflow errors there too. Fixes the other part of bug 2324.
7970 - Fix a bug where we would assert if we ever had a
7971 cached-descriptors.new file (or another file read directly into
7972 memory) of exactly SIZE_T_CEILING bytes. Fixes bug 2326; bugfix
7973 on 0.2.1.25. Found by doorss.
7974 - Fix some potential asserts and parsing issues with grossly
7975 malformed router caches. Fixes bug 2352; bugfix on Tor 0.2.1.27.
7978 o Minor bugfixes (other), also included in 0.2.1.29:
7979 - Fix a bug with handling misformed replies to reverse DNS lookup
7980 requests in DNSPort. Bugfix on Tor 0.2.0.1-alpha. Related to a
7981 bug reported by doorss.
7982 - Fix compilation on mingw when a pthreads compatibility library
7983 has been installed. (We don't want to use it, so we shouldn't
7984 be including pthread.h.) Fixes bug 2313; bugfix on 0.1.0.1-rc.
7985 - Fix a bug where we would declare that we had run out of virtual
7986 addresses when the address space was only half-exhausted. Bugfix
7988 - Correctly handle the case where AutomapHostsOnResolve is set but
7989 no virtual addresses are available. Fixes bug 2328; bugfix on
7990 0.1.2.1-alpha. Bug found by doorss.
7991 - Correctly handle wrapping around when we run out of virtual
7992 address space. Found by cypherpunks; bugfix on 0.2.0.5-alpha.
7994 o Minor features, also included in 0.2.1.29:
7995 - Update to the January 1 2011 Maxmind GeoLite Country database.
7996 - Introduce output size checks on all of our decryption functions.
7998 o Build changes, also included in 0.2.1.29:
7999 - Tor does not build packages correctly with Automake 1.6 and earlier;
8000 added a check to Makefile.am to make sure that we're building with
8001 Automake 1.7 or later.
8002 - The 0.2.1.28 tarball was missing src/common/OpenBSD_malloc_Linux.c
8003 because we built it with a too-old version of automake. Thus that
8004 release broke ./configure --enable-openbsd-malloc, which is popular
8005 among really fast exit relays on Linux.
8007 o Major bugfixes, new in 0.2.2.21-alpha:
8008 - Prevent crash/heap corruption when the cbtnummodes consensus
8009 parameter is set to 0 or large values. Fixes bug 2317; bugfix
8012 o Major features, new in 0.2.2.21-alpha:
8013 - Introduce minimum/maximum values that clients will believe
8014 from the consensus. Now we'll have a better chance to avoid crashes
8015 or worse when a consensus param has a weird value.
8017 o Minor features, new in 0.2.2.21-alpha:
8018 - Make sure to disable DirPort if running as a bridge. DirPorts aren't
8019 used on bridges, and it makes bridge scanning somewhat easier.
8020 - If writing the state file to disk fails, wait up to an hour before
8021 retrying again, rather than trying again each second. Fixes bug
8022 2346; bugfix on Tor 0.1.1.3-alpha.
8023 - Make Libevent log messages get delivered to controllers later,
8024 and not from inside the Libevent log handler. This prevents unsafe
8025 reentrant Libevent calls while still letting the log messages
8027 - Detect platforms that brokenly use a signed size_t, and refuse to
8028 build there. Found and analyzed by doorss and rransom.
8029 - Fix a bunch of compile warnings revealed by mingw with gcc 4.5.
8032 o Minor bugfixes, new in 0.2.2.21-alpha:
8033 - Handle SOCKS messages longer than 128 bytes long correctly, rather
8034 than waiting forever for them to finish. Fixes bug 2330; bugfix
8035 on 0.2.0.16-alpha. Found by doorss.
8036 - Add assertions to check for overflow in arguments to
8037 base32_encode() and base32_decode(); fix a signed-unsigned
8038 comparison there too. These bugs are not actually reachable in Tor,
8039 but it's good to prevent future errors too. Found by doorss.
8040 - Correctly detect failures to create DNS requests when using Libevent
8041 versions before v2. (Before Libevent 2, we used our own evdns
8042 implementation. Its return values for Libevent's evdns_resolve_*()
8043 functions are not consistent with those from Libevent.) Fixes bug
8044 2363; bugfix on 0.2.2.6-alpha. Found by "lodger".
8046 o Documentation, new in 0.2.2.21-alpha:
8047 - Document the default socks host and port (127.0.0.1:9050) for
8051 Changes in version 0.2.1.29 - 2011-01-15
8052 Tor 0.2.1.29 continues our recent code security audit work. The main
8053 fix resolves a remote heap overflow vulnerability that can allow remote
8054 code execution. Other fixes address a variety of assert and crash bugs,
8055 most of which we think are hard to exploit remotely.
8057 o Major bugfixes (security):
8058 - Fix a heap overflow bug where an adversary could cause heap
8059 corruption. This bug probably allows remote code execution
8060 attacks. Reported by "debuger". Fixes CVE-2011-0427. Bugfix on
8062 - Prevent a denial-of-service attack by disallowing any
8063 zlib-compressed data whose compression factor is implausibly
8064 high. Fixes part of bug 2324; reported by "doorss".
8065 - Zero out a few more keys in memory before freeing them. Fixes
8066 bug 2384 and part of bug 2385. These key instances found by
8067 "cypherpunks", based on Andrew Case's report about being able
8068 to find sensitive data in Tor's memory space if you have enough
8069 permissions. Bugfix on 0.0.2pre9.
8071 o Major bugfixes (crashes):
8072 - Prevent calls to Libevent from inside Libevent log handlers.
8073 This had potential to cause a nasty set of crashes, especially
8074 if running Libevent with debug logging enabled, and running
8075 Tor with a controller watching for low-severity log messages.
8076 Bugfix on 0.1.0.2-rc. Fixes bug 2190.
8077 - Add a check for SIZE_T_MAX to tor_realloc() to try to avoid
8078 underflow errors there too. Fixes the other part of bug 2324.
8079 - Fix a bug where we would assert if we ever had a
8080 cached-descriptors.new file (or another file read directly into
8081 memory) of exactly SIZE_T_CEILING bytes. Fixes bug 2326; bugfix
8082 on 0.2.1.25. Found by doorss.
8083 - Fix some potential asserts and parsing issues with grossly
8084 malformed router caches. Fixes bug 2352; bugfix on Tor 0.2.1.27.
8087 o Minor bugfixes (other):
8088 - Fix a bug with handling misformed replies to reverse DNS lookup
8089 requests in DNSPort. Bugfix on Tor 0.2.0.1-alpha. Related to a
8090 bug reported by doorss.
8091 - Fix compilation on mingw when a pthreads compatibility library
8092 has been installed. (We don't want to use it, so we shouldn't
8093 be including pthread.h.) Fixes bug 2313; bugfix on 0.1.0.1-rc.
8094 - Fix a bug where we would declare that we had run out of virtual
8095 addresses when the address space was only half-exhausted. Bugfix
8097 - Correctly handle the case where AutomapHostsOnResolve is set but
8098 no virtual addresses are available. Fixes bug 2328; bugfix on
8099 0.1.2.1-alpha. Bug found by doorss.
8100 - Correctly handle wrapping around to when we run out of virtual
8101 address space. Found by cypherpunks, bugfix on 0.2.0.5-alpha.
8102 - The 0.2.1.28 tarball was missing src/common/OpenBSD_malloc_Linux.c
8103 because we built it with a too-old version of automake. Thus that
8104 release broke ./configure --enable-openbsd-malloc, which is popular
8105 among really fast exit relays on Linux.
8108 - Update to the January 1 2011 Maxmind GeoLite Country database.
8109 - Introduce output size checks on all of our decryption functions.
8112 - Tor does not build packages correctly with Automake 1.6 and earlier;
8113 added a check to Makefile.am to make sure that we're building with
8114 Automake 1.7 or later.
8117 Changes in version 0.2.2.20-alpha - 2010-12-17
8118 Tor 0.2.2.20-alpha does some code cleanup to reduce the risk of remotely
8119 exploitable bugs. We also fix a variety of other significant bugs,
8120 change the IP address for one of our directory authorities, and update
8121 the minimum version that Tor relays must run to join the network.
8124 - Fix a remotely exploitable bug that could be used to crash instances
8125 of Tor remotely by overflowing on the heap. Remote-code execution
8126 hasn't been confirmed, but can't be ruled out. Everyone should
8127 upgrade. Bugfix on the 0.1.1 series and later.
8128 - Fix a bug that could break accounting on 64-bit systems with large
8129 time_t values, making them hibernate for impossibly long intervals.
8130 Fixes bug 2146. Bugfix on 0.0.9pre6; fix by boboper.
8131 - Fix a logic error in directory_fetches_from_authorities() that
8132 would cause all _non_-exits refusing single-hop-like circuits
8133 to fetch from authorities, when we wanted to have _exits_ fetch
8134 from authorities. Fixes more of 2097. Bugfix on 0.2.2.16-alpha;
8136 - Fix a stream fairness bug that would cause newer streams on a given
8137 circuit to get preference when reading bytes from the origin or
8138 destination. Fixes bug 2210. Fix by Mashael AlSabah. This bug was
8139 introduced before the first Tor release, in svn revision r152.
8141 o Directory authority changes:
8142 - Change IP address and ports for gabelmoo (v3 directory authority).
8145 - Avoid crashes when AccountingMax is set on clients. Fixes bug 2235.
8146 Bugfix on 0.2.2.18-alpha. Diagnosed by boboper.
8147 - Fix an off-by-one error in calculating some controller command
8148 argument lengths. Fortunately, this mistake is harmless since
8149 the controller code does redundant NUL termination too. Found by
8150 boboper. Bugfix on 0.1.1.1-alpha.
8151 - Do not dereference NULL if a bridge fails to build its
8152 extra-info descriptor. Found by an anonymous commenter on
8153 Trac. Bugfix on 0.2.2.19-alpha.
8156 - Update to the December 1 2010 Maxmind GeoLite Country database.
8157 - Directory authorities now reject relays running any versions of
8158 Tor between 0.2.1.3-alpha and 0.2.1.18 inclusive; they have
8159 known bugs that keep RELAY_EARLY cells from working on rendezvous
8160 circuits. Followup to fix for bug 2081.
8161 - Directory authorities now reject relays running any version of Tor
8162 older than 0.2.0.26-rc. That version is the earliest that fetches
8163 current directory information correctly. Fixes bug 2156.
8164 - Report only the top 10 ports in exit-port stats in order not to
8165 exceed the maximum extra-info descriptor length of 50 KB. Implements
8169 Changes in version 0.2.1.28 - 2010-12-17
8170 Tor 0.2.1.28 does some code cleanup to reduce the risk of remotely
8171 exploitable bugs. We also took this opportunity to change the IP address
8172 for one of our directory authorities, and to update the geoip database
8176 - Fix a remotely exploitable bug that could be used to crash instances
8177 of Tor remotely by overflowing on the heap. Remote-code execution
8178 hasn't been confirmed, but can't be ruled out. Everyone should
8179 upgrade. Bugfix on the 0.1.1 series and later.
8181 o Directory authority changes:
8182 - Change IP address and ports for gabelmoo (v3 directory authority).
8185 - Update to the December 1 2010 Maxmind GeoLite Country database.
8188 Changes in version 0.2.1.27 - 2010-11-23
8189 Yet another OpenSSL security patch broke its compatibility with Tor:
8190 Tor 0.2.1.27 makes relays work with openssl 0.9.8p and 1.0.0.b. We
8191 also took this opportunity to fix several crash bugs, integrate a new
8192 directory authority, and update the bundled GeoIP database.
8195 - Resolve an incompatibility with OpenSSL 0.9.8p and OpenSSL 1.0.0b:
8196 No longer set the tlsext_host_name extension on server SSL objects;
8197 but continue to set it on client SSL objects. Our goal in setting
8198 it was to imitate a browser, not a vhosting server. Fixes bug 2204;
8199 bugfix on 0.2.1.1-alpha.
8200 - Do not log messages to the controller while shrinking buffer
8201 freelists. Doing so would sometimes make the controller connection
8202 try to allocate a buffer chunk, which would mess up the internals
8203 of the freelist and cause an assertion failure. Fixes bug 1125;
8204 fixed by Robert Ransom. Bugfix on 0.2.0.16-alpha.
8205 - Learn our external IP address when we're a relay or bridge, even if
8206 we set PublishServerDescriptor to 0. Bugfix on 0.2.0.3-alpha,
8207 where we introduced bridge relays that don't need to publish to
8208 be useful. Fixes bug 2050.
8209 - Do even more to reject (and not just ignore) annotations on
8210 router descriptors received anywhere but from the cache. Previously
8211 we would ignore such annotations at first, but cache them to disk
8212 anyway. Bugfix on 0.2.0.8-alpha. Found by piebeer.
8213 - When you're using bridges and your network goes away and your
8214 bridges get marked as down, recover when you attempt a new socks
8215 connection (if the network is back), rather than waiting up to an
8216 hour to try fetching new descriptors for your bridges. Bugfix on
8217 0.2.0.3-alpha; fixes bug 1981.
8220 - Move to the November 2010 Maxmind GeoLite country db (rather
8221 than the June 2009 ip-to-country GeoIP db) for our statistics that
8222 count how many users relays are seeing from each country. Now we'll
8223 have more accurate data, especially for many African countries.
8225 o New directory authorities:
8226 - Set up maatuska (run by Linus Nordberg) as the eighth v3 directory
8230 - Fix an assertion failure that could occur in directory caches or
8231 bridge users when using a very short voting interval on a testing
8232 network. Diagnosed by Robert Hogan. Fixes bug 1141; bugfix on
8234 - Enforce multiplicity rules when parsing annotations. Bugfix on
8235 0.2.0.8-alpha. Found by piebeer.
8236 - Allow handshaking OR connections to take a full KeepalivePeriod
8237 seconds to handshake. Previously, we would close them after
8238 IDLE_OR_CONN_TIMEOUT (180) seconds, the same timeout as if they
8239 were open. Bugfix on 0.2.1.26; fixes bug 1840. Thanks to mingw-san
8241 - When building with --enable-gcc-warnings on OpenBSD, disable
8242 warnings in system headers. This makes --enable-gcc-warnings
8243 pass on OpenBSD 4.8.
8246 - Exit nodes didn't recognize EHOSTUNREACH as a plausible error code,
8247 and so sent back END_STREAM_REASON_MISC. Clients now recognize a new
8248 stream ending reason for this case: END_STREAM_REASON_NOROUTE.
8249 Servers can start sending this code when enough clients recognize
8250 it. Bugfix on 0.1.0.1-rc; fixes part of bug 1793.
8251 - Build correctly on mingw with more recent versions of OpenSSL 0.9.8.
8252 Patch from mingw-san.
8255 - Remove the old debian/ directory from the main Tor distribution.
8256 The official Tor-for-debian git repository lives at the URL
8257 https://git.torproject.org/debian/tor.git
8258 - Stop shipping the old doc/website/ directory in the tarball. We
8259 changed the website format in late 2010, and what we shipped in
8260 0.2.1.26 really wasn't that useful anyway.
8263 Changes in version 0.2.2.19-alpha - 2010-11-22
8264 Yet another OpenSSL security patch broke its compatibility with Tor:
8265 Tor 0.2.2.19-alpha makes relays work with OpenSSL 0.9.8p and 1.0.0.b.
8268 - Resolve an incompatibility with OpenSSL 0.9.8p and OpenSSL 1.0.0b:
8269 No longer set the tlsext_host_name extension on server SSL objects;
8270 but continue to set it on client SSL objects. Our goal in setting
8271 it was to imitate a browser, not a vhosting server. Fixes bug 2204;
8272 bugfix on 0.2.1.1-alpha.
8275 - Try harder not to exceed the maximum length of 50 KB when writing
8276 statistics to extra-info descriptors. This bug was triggered by very
8277 fast relays reporting exit-port, entry, and dirreq statistics.
8278 Reported by Olaf Selke. Bugfix on 0.2.2.1-alpha. Fixes bug 2183.
8279 - Publish a router descriptor even if generating an extra-info
8280 descriptor fails. Previously we would not publish a router
8281 descriptor without an extra-info descriptor; this can cause fast
8282 exit relays collecting exit-port statistics to drop from the
8283 consensus. Bugfix on 0.1.2.9-rc; fixes bug 2195.
8286 Changes in version 0.2.2.18-alpha - 2010-11-16
8287 Tor 0.2.2.18-alpha fixes several crash bugs that have been nagging
8288 us lately, makes unpublished bridge relays able to detect their IP
8289 address, and fixes a wide variety of other bugs to get us much closer
8290 to a stable release.
8293 - Do even more to reject (and not just ignore) annotations on
8294 router descriptors received anywhere but from the cache. Previously
8295 we would ignore such annotations at first, but cache them to disk
8296 anyway. Bugfix on 0.2.0.8-alpha. Found by piebeer.
8297 - Do not log messages to the controller while shrinking buffer
8298 freelists. Doing so would sometimes make the controller connection
8299 try to allocate a buffer chunk, which would mess up the internals
8300 of the freelist and cause an assertion failure. Fixes bug 1125;
8301 fixed by Robert Ransom. Bugfix on 0.2.0.16-alpha.
8302 - Learn our external IP address when we're a relay or bridge, even if
8303 we set PublishServerDescriptor to 0. Bugfix on 0.2.0.3-alpha,
8304 where we introduced bridge relays that don't need to publish to
8305 be useful. Fixes bug 2050.
8306 - Maintain separate TLS contexts and certificates for incoming and
8307 outgoing connections in bridge relays. Previously we would use the
8308 same TLS contexts and certs for incoming and outgoing connections.
8309 Bugfix on 0.2.0.3-alpha; addresses bug 988.
8310 - Maintain separate identity keys for incoming and outgoing TLS
8311 contexts in bridge relays. Previously we would use the same
8312 identity keys for incoming and outgoing TLS contexts. Bugfix on
8313 0.2.0.3-alpha; addresses the other half of bug 988.
8314 - Avoid an assertion failure when we as an authority receive a
8315 duplicate upload of a router descriptor that we already have,
8316 but which we previously considered an obsolete descriptor.
8317 Fixes another case of bug 1776. Bugfix on 0.2.2.16-alpha.
8318 - Avoid a crash bug triggered by looking at a dangling pointer while
8319 setting the network status consensus. Found by Robert Ransom.
8320 Bugfix on 0.2.2.17-alpha. Fixes bug 2097.
8321 - Fix a logic error where servers that _didn't_ act as exits would
8322 try to keep their server lists more aggressively up to date than
8323 exits, when it was supposed to be the other way around. Bugfix
8326 o Minor bugfixes (on Tor 0.2.1.x and earlier):
8327 - When we're trying to guess whether we know our IP address as
8328 a relay, we would log various ways that we failed to guess
8329 our address, but never log that we ended up guessing it
8330 successfully. Now add a log line to help confused and anxious
8331 relay operators. Bugfix on 0.1.2.1-alpha; fixes bug 1534.
8332 - Bring the logic that gathers routerinfos and assesses the
8333 acceptability of circuits into line. This prevents a Tor OP from
8334 getting locked in a cycle of choosing its local OR as an exit for a
8335 path (due to a .exit request) and then rejecting the circuit because
8336 its OR is not listed yet. It also prevents Tor clients from using an
8337 OR running in the same instance as an exit (due to a .exit request)
8338 if the OR does not meet the same requirements expected of an OR
8339 running elsewhere. Fixes bug 1859; bugfix on 0.1.0.1-rc.
8340 - Correctly describe errors that occur when generating a TLS object.
8341 Previously we would attribute them to a failure while generating a
8342 TLS context. Patch by Robert Ransom. Bugfix on 0.1.0.4-rc; fixes
8344 - Enforce multiplicity rules when parsing annotations. Bugfix on
8345 0.2.0.8-alpha. Found by piebeer.
8346 - Fix warnings that newer versions of autoconf produced during
8347 ./autogen.sh. These warnings appear to be harmless in our case,
8348 but they were extremely verbose. Fixes bug 2020.
8350 o Minor bugfixes (on Tor 0.2.2.x):
8351 - Enable protection of small arrays whenever we build with gcc
8352 hardening features, not only when also building with warnings
8353 enabled. Fixes bug 2031; bugfix on 0.2.2.14-alpha. Reported by keb.
8356 - Make hidden services work better in private Tor networks by not
8357 requiring any uptime to join the hidden service descriptor
8358 DHT. Implements ticket 2088.
8359 - Rate-limit the "your application is giving Tor only an IP address"
8360 warning. Addresses bug 2000; bugfix on 0.0.8pre2.
8361 - When AllowSingleHopExits is set, print a warning to explain to the
8362 relay operator why most clients are avoiding her relay.
8363 - Update to the November 1 2010 Maxmind GeoLite Country database.
8365 o Code simplifications and refactoring:
8366 - When we fixed bug 1038 we had to put in a restriction not to send
8367 RELAY_EARLY cells on rend circuits. This was necessary as long
8368 as relays using Tor 0.2.1.3-alpha through 0.2.1.18-alpha were
8369 active. Now remove this obsolete check. Resolves bug 2081.
8370 - Some options used different conventions for uppercasing of acronyms
8371 when comparing manpage and source. Fix those in favor of the
8372 manpage, as it makes sense to capitalize acronyms.
8373 - Remove the torrc.complete file. It hasn't been kept up to date
8374 and users will have better luck checking out the manpage.
8375 - Remove the obsolete "NoPublish" option; it has been flagged
8376 as obsolete and has produced a warning since 0.1.1.18-rc.
8377 - Remove everything related to building the expert bundle for OS X.
8378 It has confused many users, doesn't work right on OS X 10.6,
8379 and is hard to get rid of once installed. Resolves bug 1274.
8382 Changes in version 0.2.2.17-alpha - 2010-09-30
8383 Tor 0.2.2.17-alpha introduces a feature to make it harder for clients
8384 to use one-hop circuits (which can put the exit relays at higher risk,
8385 plus unbalance the network); fixes a big bug in bandwidth accounting
8386 for relays that want to limit their monthly bandwidth use; fixes a
8387 big pile of bugs in how clients tolerate temporary network failure;
8388 and makes our adaptive circuit build timeout feature (which improves
8389 client performance if your network is fast while not breaking things
8390 if your network is slow) better handle bad networks.
8393 - Exit relays now try harder to block exit attempts from unknown
8394 relays, to make it harder for people to use them as one-hop proxies
8395 a la tortunnel. Controlled by the refuseunknownexits consensus
8396 parameter (currently enabled), or you can override it on your
8397 relay with the RefuseUnknownExits torrc option. Resolves bug 1751.
8399 o Major bugfixes (0.2.1.x and earlier):
8400 - Fix a bug in bandwidth accounting that could make us use twice
8401 the intended bandwidth when our interval start changes due to
8402 daylight saving time. Now we tolerate skew in stored vs computed
8403 interval starts: if the start of the period changes by no more than
8404 50% of the period's duration, we remember bytes that we transferred
8405 in the old period. Fixes bug 1511; bugfix on 0.0.9pre5.
8406 - Always search the Windows system directory for system DLLs, and
8407 nowhere else. Bugfix on 0.1.1.23; fixes bug 1954.
8408 - When you're using bridges and your network goes away and your
8409 bridges get marked as down, recover when you attempt a new socks
8410 connection (if the network is back), rather than waiting up to an
8411 hour to try fetching new descriptors for your bridges. Bugfix on
8412 0.2.0.3-alpha; fixes bug 1981.
8414 o Major bugfixes (on 0.2.2.x):
8415 - Fix compilation on Windows. Bugfix on 0.2.2.16-alpha; related to
8417 - Fix a segfault that could happen when operating a bridge relay with
8418 no GeoIP database set. Fixes bug 1964; bugfix on 0.2.2.15-alpha.
8419 - The consensus bandwidth-weights (used by clients to choose fast
8420 relays) entered an unexpected edge case in September where
8421 Exits were much scarcer than Guards, resulting in bad weight
8422 recommendations. Now we compute them using new constraints that
8423 should succeed in all cases. Also alter directory authorities to
8424 not include the bandwidth-weights line if they fail to produce
8425 valid values. Fixes bug 1952; bugfix on 0.2.2.10-alpha.
8426 - When weighting bridges during path selection, we used to trust
8427 the bandwidths they provided in their descriptor, only capping them
8428 at 10MB/s. This turned out to be problematic for two reasons:
8429 Bridges could claim to handle a lot more traffic then they
8430 actually would, thus making more clients pick them and have a
8431 pretty effective DoS attack. The other issue is that new bridges
8432 that might not have a good estimate for their bw capacity yet
8433 would not get used at all unless no other bridges are available
8434 to a client. Fixes bug 1912; bugfix on 0.2.2.7-alpha.
8436 o Major bugfixes (on the circuit build timeout feature, 0.2.2.x):
8437 - Ignore cannibalized circuits when recording circuit build times.
8438 This should provide for a minor performance improvement for hidden
8439 service users using 0.2.2.14-alpha, and should remove two spurious
8440 notice log messages. Bugfix on 0.2.2.14-alpha; fixes bug 1740.
8441 - Simplify the logic that causes us to decide if the network is
8442 unavailable for purposes of recording circuit build times. If we
8443 receive no cells whatsoever for the entire duration of a circuit's
8444 full measured lifetime, the network is probably down. Also ignore
8445 one-hop directory fetching circuit timeouts when calculating our
8446 circuit build times. These changes should hopefully reduce the
8447 cases where we see ridiculous circuit build timeouts for people
8448 with spotty wireless connections. Fixes part of bug 1772; bugfix
8450 - Prevent the circuit build timeout from becoming larger than
8451 the maximum build time we have ever seen. Also, prevent the time
8452 period for measurement circuits from becoming larger than twice that
8453 value. Fixes the other part of bug 1772; bugfix on 0.2.2.2-alpha.
8456 - When we run out of directory information such that we can't build
8457 circuits, but then get enough that we can build circuits, log when
8458 we actually construct a circuit, so the user has a better chance of
8459 knowing what's going on. Fixes bug 1362.
8460 - Be more generous with how much bandwidth we'd use up (with
8461 accounting enabled) before entering "soft hibernation". Previously,
8462 we'd refuse new connections and circuits once we'd used up 95% of
8463 our allotment. Now, we use up 95% of our allotment, AND make sure
8464 that we have no more than 500MB (or 3 hours of expected traffic,
8465 whichever is lower) remaining before we enter soft hibernation.
8466 - If we've configured EntryNodes and our network goes away and/or all
8467 our entrynodes get marked down, optimistically retry them all when
8468 a new socks application request appears. Fixes bug 1882.
8469 - Add some more defensive programming for architectures that can't
8470 handle unaligned integer accesses. We don't know of any actual bugs
8471 right now, but that's the best time to fix them. Fixes bug 1943.
8472 - Support line continuations in the torrc config file. If a line
8473 ends with a single backslash character, the newline is ignored, and
8474 the configuration value is treated as continuing on the next line.
8477 o Minor bugfixes (on 0.2.1.x and earlier):
8478 - For bandwidth accounting, calculate our expected bandwidth rate
8479 based on the time during which we were active and not in
8480 soft-hibernation during the last interval. Previously, we were
8481 also considering the time spent in soft-hibernation. If this
8482 was a long time, we would wind up underestimating our bandwidth
8483 by a lot, and skewing our wakeup time towards the start of the
8484 accounting interval. Fixes bug 1789. Bugfix on 0.0.9pre5.
8486 o Minor bugfixes (on 0.2.2.x):
8487 - Resume generating CIRC FAILED REASON=TIMEOUT control port messages,
8488 which were disabled by the circuit build timeout changes in
8489 0.2.2.14-alpha. Bugfix on 0.2.2.14-alpha; fixes bug 1739.
8490 - Make sure we don't warn about missing bandwidth weights when
8491 choosing bridges or other relays not in the consensus. Bugfix on
8492 0.2.2.10-alpha; fixes bug 1805.
8493 - In our logs, do not double-report signatures from unrecognized
8494 authorities both as "from unknown authority" and "not
8495 present". Fixes bug 1956, bugfix on 0.2.2.16-alpha.
8498 Changes in version 0.2.2.16-alpha - 2010-09-17
8499 Tor 0.2.2.16-alpha fixes a variety of old stream fairness bugs (most
8500 evident at exit relays), and also continues to resolve all the little
8501 bugs that have been filling up trac lately.
8503 o Major bugfixes (stream-level fairness):
8504 - When receiving a circuit-level SENDME for a blocked circuit, try
8505 to package cells fairly from all the streams that had previously
8506 been blocked on that circuit. Previously, we had started with the
8507 oldest stream, and allowed each stream to potentially exhaust
8508 the circuit's package window. This gave older streams on any
8509 given circuit priority over newer ones. Fixes bug 1937. Detected
8510 originally by Camilo Viecco. This bug was introduced before the
8511 first Tor release, in svn commit r152: it is the new winner of
8512 the longest-lived bug prize.
8513 - When the exit relay got a circuit-level sendme cell, it started
8514 reading on the exit streams, even if had 500 cells queued in the
8515 circuit queue already, so the circuit queue just grew and grew in
8516 some cases. We fix this by not re-enabling reading on receipt of a
8517 sendme cell when the cell queue is blocked. Fixes bug 1653. Bugfix
8518 on 0.2.0.1-alpha. Detected by Mashael AlSabah. Original patch by
8520 - Newly created streams were allowed to read cells onto circuits,
8521 even if the circuit's cell queue was blocked and waiting to drain.
8522 This created potential unfairness, as older streams would be
8523 blocked, but newer streams would gladly fill the queue completely.
8524 We add code to detect this situation and prevent any stream from
8525 getting more than one free cell. Bugfix on 0.2.0.1-alpha. Partially
8529 - Update to the September 1 2010 Maxmind GeoLite Country database.
8530 - Warn when CookieAuthFileGroupReadable is set but CookieAuthFile is
8531 not. This would lead to a cookie that is still not group readable.
8532 Closes bug 1843. Suggested by katmagic.
8533 - When logging a rate-limited warning, we now mention how many messages
8534 got suppressed since the last warning.
8535 - Add new "perconnbwrate" and "perconnbwburst" consensus params to
8536 do individual connection-level rate limiting of clients. The torrc
8537 config options with the same names trump the consensus params, if
8538 both are present. Replaces the old "bwconnrate" and "bwconnburst"
8539 consensus params which were broken from 0.2.2.7-alpha through
8540 0.2.2.14-alpha. Closes bug 1947.
8541 - When a router changes IP address or port, authorities now launch
8542 a new reachability test for it. Implements ticket 1899.
8543 - Make the formerly ugly "2 unknown, 7 missing key, 0 good, 0 bad,
8544 2 no signature, 4 required" messages about consensus signatures
8545 easier to read, and make sure they get logged at the same severity
8546 as the messages explaining which keys are which. Fixes bug 1290.
8547 - Don't warn when we have a consensus that we can't verify because
8548 of missing certificates, unless those certificates are ones
8549 that we have been trying and failing to download. Fixes bug 1145.
8550 - If you configure your bridge with a known identity fingerprint,
8551 and the bridge authority is unreachable (as it is in at least
8552 one country now), fall back to directly requesting the descriptor
8553 from the bridge. Finishes the feature started in 0.2.0.10-alpha;
8555 - When building with --enable-gcc-warnings on OpenBSD, disable
8556 warnings in system headers. This makes --enable-gcc-warnings
8557 pass on OpenBSD 4.8.
8559 o Minor bugfixes (on 0.2.1.x and earlier):
8560 - Authorities will now attempt to download consensuses if their
8561 own efforts to make a live consensus have failed. This change
8562 means authorities that restart will fetch a valid consensus, and
8563 it means authorities that didn't agree with the current consensus
8564 will still fetch and serve it if it has enough signatures. Bugfix
8565 on 0.2.0.9-alpha; fixes bug 1300.
8566 - Ensure DNS requests launched by "RESOLVE" commands from the
8567 controller respect the __LeaveStreamsUnattached setconf options. The
8568 same goes for requests launched via DNSPort or transparent
8569 proxying. Bugfix on 0.2.0.1-alpha; fixes bug 1525.
8570 - Allow handshaking OR connections to take a full KeepalivePeriod
8571 seconds to handshake. Previously, we would close them after
8572 IDLE_OR_CONN_TIMEOUT (180) seconds, the same timeout as if they
8573 were open. Bugfix on 0.2.1.26; fixes bug 1840. Thanks to mingw-san
8575 - Rate-limit "Failed to hand off onionskin" warnings.
8576 - Never relay a cell for a circuit we have already destroyed.
8577 Between marking a circuit as closeable and finally closing it,
8578 it may have been possible for a few queued cells to get relayed,
8579 even though they would have been immediately dropped by the next
8580 OR in the circuit. Fixes bug 1184; bugfix on 0.2.0.1-alpha.
8581 - Never queue a cell for a circuit that's already been marked
8583 - Never vote for a server as "Running" if we have a descriptor for
8584 it claiming to be hibernating, and that descriptor was published
8585 more recently than our last contact with the server. Bugfix on
8586 0.2.0.3-alpha; fixes bug 911.
8587 - Squash a compile warning on OpenBSD. Reported by Tas; fixes
8590 o Minor bugfixes (on 0.2.2.x):
8591 - Fix a regression introduced in 0.2.2.7-alpha that marked relays
8592 down if a directory fetch fails and you've configured either
8593 bridges or EntryNodes. The intent was to mark the relay as down
8594 _unless_ you're using bridges or EntryNodes, since if you are
8595 then you could quickly run out of entry points.
8596 - Fix the Windows directory-listing code. A bug introduced in
8597 0.2.2.14-alpha could make Windows directory servers forget to load
8598 some of their cached v2 networkstatus files.
8599 - Really allow clients to use relays as bridges. Fixes bug 1776;
8600 bugfix on 0.2.2.15-alpha.
8601 - Demote a warn to info that happens when the CellStatistics option
8602 was just enabled. Bugfix on 0.2.2.15-alpha; fixes bug 1921.
8603 Reported by Moritz Bartl.
8604 - On Windows, build correctly either with or without Unicode support.
8605 This is necessary so that Tor can support fringe platforms like
8606 Windows 98 (which has no Unicode), or Windows CE (which has no
8607 non-Unicode). Bugfix on 0.2.2.14-alpha; fixes bug 1797.
8610 - Add a unit test for cross-platform directory-listing code.
8613 Changes in version 0.2.2.15-alpha - 2010-08-18
8614 Tor 0.2.2.15-alpha fixes a big bug in hidden service availability,
8615 fixes a variety of other bugs that were preventing performance
8616 experiments from moving forward, fixes several bothersome memory leaks,
8617 and generally closes a lot of smaller bugs that have been filling up
8621 - Stop assigning the HSDir flag to relays that disable their
8622 DirPort (and thus will refuse to answer directory requests). This
8623 fix should dramatically improve the reachability of hidden services:
8624 hidden services and hidden service clients pick six HSDir relays
8625 to store and retrieve the hidden service descriptor, and currently
8626 about half of the HSDir relays will refuse to work. Bugfix on
8627 0.2.0.10-alpha; fixes part of bug 1693.
8628 - The PerConnBWRate and Burst config options, along with the
8629 bwconnrate and bwconnburst consensus params, initialized each conn's
8630 token bucket values only when the connection is established. Now we
8631 update them if the config options change, and update them every time
8632 we get a new consensus. Otherwise we can encounter an ugly edge
8633 case where we initialize an OR conn to client-level bandwidth,
8634 but then later the relay joins the consensus and we leave it
8635 throttled. Bugfix on 0.2.2.7-alpha; fixes bug 1830.
8636 - Fix a regression that caused Tor to rebind its ports if it receives
8637 SIGHUP while hibernating. Bugfix in 0.1.1.6-alpha; closes bug 919.
8640 - Lower the maximum weighted-fractional-uptime cutoff to 98%. This
8641 should give us approximately 40-50% more Guard-flagged nodes,
8642 improving the anonymity the Tor network can provide and also
8643 decreasing the dropoff in throughput that relays experience when
8644 they first get the Guard flag.
8645 - Allow enabling or disabling the *Statistics config options while
8649 - Update to the August 1 2010 Maxmind GeoLite Country database.
8650 - Have the controller interface give a more useful message than
8651 "Internal Error" in response to failed GETINFO requests.
8652 - Warn when the same option is provided more than once in a torrc
8653 file, on the command line, or in a single SETCONF statement, and
8654 the option is one that only accepts a single line. Closes bug 1384.
8655 - Build correctly on mingw with more recent versions of OpenSSL 0.9.8.
8656 Patch from mingw-san.
8657 - Add support for the country code "{??}" in torrc options like
8658 ExcludeNodes, to indicate all routers of unknown country. Closes
8660 - Relays report the number of bytes spent on answering directory
8661 requests in extra-info descriptors similar to {read,write}-history.
8662 Implements enhancement 1790.
8664 o Minor bugfixes (on 0.2.1.x and earlier):
8665 - Complain if PublishServerDescriptor is given multiple arguments that
8666 include 0 or 1. This configuration will be rejected in the future.
8667 Bugfix on 0.2.0.1-alpha; closes bug 1107.
8668 - Disallow BridgeRelay 1 and ORPort 0 at once in the configuration.
8669 Bugfix on 0.2.0.13-alpha; closes bug 928.
8670 - Change "Application request when we're believed to be offline."
8671 notice to "Application request when we haven't used client
8672 functionality lately.", to clarify that it's not an error. Bugfix
8673 on 0.0.9.3; fixes bug 1222.
8674 - Fix a bug in the controller interface where "GETINFO ns/asdaskljkl"
8675 would return "551 Internal error" rather than "552 Unrecognized key
8676 ns/asdaskljkl". Bugfix on 0.1.2.3-alpha.
8677 - Users can't configure a regular relay to be their bridge. It didn't
8678 work because when Tor fetched the bridge descriptor, it found
8679 that it already had it, and didn't realize that the purpose of the
8680 descriptor had changed. Now we replace routers with a purpose other
8681 than bridge with bridge descriptors when fetching them. Bugfix on
8682 0.1.1.9-alpha. Bug 1776 not yet fixed because now we immediately
8683 refetch the descriptor with router purpose 'general', disabling
8685 - Fix a rare bug in rend_fn unit tests: we would fail a test when
8686 a randomly generated port is 0. Diagnosed by Matt Edman. Bugfix
8687 on 0.2.0.10-alpha; fixes bug 1808.
8688 - Exit nodes didn't recognize EHOSTUNREACH as a plausible error code,
8689 and so sent back END_STREAM_REASON_MISC. Clients now recognize a new
8690 stream ending reason for this case: END_STREAM_REASON_NOROUTE.
8691 Servers can start sending this code when enough clients recognize
8692 it. Also update the spec to reflect this new reason. Bugfix on
8693 0.1.0.1-rc; fixes part of bug 1793.
8694 - Delay geoip stats collection by bridges for 6 hours, not 2 hours,
8695 when we switch from being a public relay to a bridge. Otherwise
8696 there will still be clients that see the relay in their consensus,
8697 and the stats will end up wrong. Bugfix on 0.2.1.15-rc; fixes bug
8699 - Instead of giving an assertion failure on an internal mismatch
8700 on estimated freelist size, just log a BUG warning and try later.
8701 Mitigates but does not fix bug 1125.
8702 - Fix an assertion failure that could occur in caches or bridge users
8703 when using a very short voting interval on a testing network.
8704 Diagnosed by Robert Hogan. Fixes bug 1141; bugfix on 0.2.0.8-alpha.
8706 o Minor bugfixes (on 0.2.2.x):
8707 - Alter directory authorities to always consider Exit-flagged nodes
8708 as potential Guard nodes in their votes. The actual decision to
8709 use Exits as Guards is done in the consensus bandwidth weights.
8710 Fixes bug 1294; bugfix on 0.2.2.10-alpha.
8711 - When the controller is reporting the purpose of circuits that
8712 didn't finish building before the circuit build timeout, it was
8713 printing UNKNOWN_13. Now print EXPIRED. Bugfix on 0.2.2.14-alpha.
8714 - Our libevent version parsing code couldn't handle versions like
8715 1.4.14b-stable and incorrectly warned the user about using an
8716 old and broken version of libevent. Treat 1.4.14b-stable like
8717 1.4.14-stable when parsing the version. Fixes bug 1731; bugfix
8719 - Don't use substitution references like $(VAR:MOD) when
8720 $(asciidoc_files) is empty -- make(1) on NetBSD transforms
8721 '$(:x)' to 'x' rather than the empty string. This bites us in
8722 doc/ when configured with --disable-asciidoc. Bugfix on
8723 0.2.2.9-alpha; fixes bug 1773.
8724 - Remove a spurious hidden service server-side log notice about
8725 "Ancient non-dirty circuits". Bugfix on 0.2.2.14-alpha; fixes
8727 - Fix compilation with --with-dmalloc set. Bugfix on 0.2.2.6-alpha;
8729 - Correctly report written bytes on linked connections. Found while
8730 implementing 1790. Bugfix on 0.2.2.4-alpha.
8731 - Fix three memory leaks: one in circuit_build_times_parse_state(),
8732 one in dirvote_add_signatures_to_pending_consensus(), and one every
8733 time we parse a v3 network consensus. Bugfixes on 0.2.2.14-alpha,
8734 0.2.2.6-alpha, and 0.2.2.10-alpha respectively; fixes bug 1831.
8736 o Code simplifications and refactoring:
8737 - Take a first step towards making or.h smaller by splitting out
8738 function definitions for all source files in src/or/. Leave
8739 structures and defines in or.h for now.
8740 - Remove a bunch of unused function declarations as well as a block of
8741 #if 0'd code from the unit tests. Closes bug 1824.
8742 - New unit tests for exit-port history statistics; refactored exit
8743 statistics code to be more easily tested.
8744 - Remove the old debian/ directory from the main Tor distribution.
8745 The official Tor-for-debian git repository lives at the URL
8746 https://git.torproject.org/debian/tor.git
8749 Changes in version 0.2.2.14-alpha - 2010-07-12
8750 Tor 0.2.2.14-alpha greatly improves client-side handling of
8751 circuit build timeouts, which are used to estimate speed and improve
8752 performance. We also move to a much better GeoIP database, port Tor to
8753 Windows CE, introduce new compile flags that improve code security,
8754 add an eighth v3 directory authority, and address a lot of more
8758 - Tor directory authorities no longer crash when started with a
8759 cached-microdesc-consensus file in their data directory. Bugfix
8760 on 0.2.2.6-alpha; fixes bug 1532.
8761 - Treat an unset $HOME like an empty $HOME rather than triggering an
8762 assert. Bugfix on 0.0.8pre1; fixes bug 1522.
8763 - Ignore negative and large circuit build timeout values that can
8764 happen during a suspend or hibernate. These values caused various
8765 asserts to fire. Bugfix on 0.2.2.2-alpha; fixes bug 1245.
8766 - Alter calculation of Pareto distribution parameter 'Xm' for
8767 Circuit Build Timeout learning to use the weighted average of the
8768 top N=3 modes (because we have three entry guards). Considering
8769 multiple modes should improve the timeout calculation in some cases,
8770 and prevent extremely high timeout values. Bugfix on 0.2.2.2-alpha;
8772 - Alter calculation of Pareto distribution parameter 'Alpha' to use a
8773 right censored distribution model. This approach improves over the
8774 synthetic timeout generation approach that was producing insanely
8775 high timeout values. Now we calculate build timeouts using truncated
8776 times. Bugfix on 0.2.2.2-alpha; fixes bugs 1245 and 1335.
8777 - Do not close circuits that are under construction when they reach
8778 the circuit build timeout. Instead, leave them building (but do not
8779 use them) for up until the time corresponding to the 95th percentile
8780 on the Pareto CDF or 60 seconds, whichever is greater. This is done
8781 to provide better data for the new Pareto model. This percentile
8782 can be controlled by the consensus.
8785 - Move to the June 2010 Maxmind GeoLite country db (rather than the
8786 June 2009 ip-to-country GeoIP db) for our statistics that count
8787 how many users relays are seeing from each country. Now we have
8788 more accurate data for many African countries.
8789 - Port Tor to build and run correctly on Windows CE systems, using
8790 the wcecompat library. Contributed by Valerio Lupi.
8791 - New "--enable-gcc-hardening" ./configure flag (off by default)
8792 to turn on gcc compile time hardening options. It ensures
8793 that signed ints have defined behavior (-fwrapv), enables
8794 -D_FORTIFY_SOURCE=2 (requiring -O2), adds stack smashing protection
8795 with canaries (-fstack-protector-all), turns on ASLR protection if
8796 supported by the kernel (-fPIE, -pie), and adds additional security
8797 related warnings. Verified to work on Mac OS X and Debian Lenny.
8798 - New "--enable-linker-hardening" ./configure flag (off by default)
8799 to turn on ELF specific hardening features (relro, now). This does
8800 not work with Mac OS X or any other non-ELF binary format.
8802 o New directory authorities:
8803 - Set up maatuska (run by Linus Nordberg) as the eighth v3 directory
8807 - New config option "WarnUnsafeSocks 0" disables the warning that
8808 occurs whenever Tor receives a socks handshake using a version of
8809 the socks protocol that can only provide an IP address (rather
8810 than a hostname). Setups that do DNS locally over Tor are fine,
8811 and we shouldn't spam the logs in that case.
8812 - Convert the HACKING file to asciidoc, and add a few new sections
8813 to it, explaining how we use Git, how we make changelogs, and
8814 what should go in a patch.
8815 - Add a TIMEOUT_RATE keyword to the BUILDTIMEOUT_SET control port
8816 event, to give information on the current rate of circuit timeouts
8817 over our stored history.
8818 - Add ability to disable circuit build time learning via consensus
8819 parameter and via a LearnCircuitBuildTimeout config option. Also
8820 automatically disable circuit build time calculation if we are
8821 either a AuthoritativeDirectory, or if we fail to write our state
8822 file. Fixes bug 1296.
8823 - More gracefully handle corrupt state files, removing asserts
8824 in favor of saving a backup and resetting state.
8825 - Rename the "log.h" header to "torlog.h" so as to conflict with fewer
8829 - Build correctly on OSX with zlib 1.2.4 and higher with all warnings
8831 - When a2x fails, mention that the user could disable manpages instead
8832 of trying to fix their asciidoc installation.
8833 - Where available, use Libevent 2.0's periodic timers so that our
8834 once-per-second cleanup code gets called even more closely to
8835 once per second than it would otherwise. Fixes bug 943.
8836 - If you run a bridge that listens on multiple IP addresses, and
8837 some user configures a bridge address that uses a different IP
8838 address than your bridge writes in its router descriptor, and the
8839 user doesn't specify an identity key, their Tor would discard the
8840 descriptor because "it isn't one of our configured bridges", and
8841 fail to bootstrap. Now believe the descriptor and bootstrap anyway.
8842 Bugfix on 0.2.0.3-alpha.
8843 - If OpenSSL fails to make a duplicate of a private or public key, log
8844 an error message and try to exit cleanly. May help with debugging
8845 if bug 1209 ever remanifests.
8846 - Save a couple bytes in memory allocation every time we escape
8847 certain characters in a string. Patch from Florian Zumbiehl.
8848 - Make it explicit that we don't cannibalize one-hop circuits. This
8849 happens in the wild, but doesn't turn out to be a problem because
8850 we fortunately don't use those circuits. Many thanks to outofwords
8851 for the initial analysis and to swissknife who confirmed that
8852 two-hop circuits are actually created.
8853 - Make directory mirrors report non-zero dirreq-v[23]-shares again.
8854 Fixes bug 1564; bugfix on 0.2.2.9-alpha.
8855 - Eliminate a case where a circuit build time warning was displayed
8856 after network connectivity resumed. Bugfix on 0.2.2.2-alpha.
8859 Changes in version 0.2.1.26 - 2010-05-02
8860 Tor 0.2.1.26 addresses the recent connection and memory overload
8861 problems we've been seeing on relays, especially relays with their
8862 DirPort open. If your relay has been crashing, or you turned it off
8863 because it used too many resources, give this release a try.
8865 This release also fixes yet another instance of broken OpenSSL libraries
8866 that was causing some relays to drop out of the consensus.
8869 - Teach relays to defend themselves from connection overload. Relays
8870 now close idle circuits early if it looks like they were intended
8871 for directory fetches. Relays are also more aggressive about closing
8872 TLS connections that have no circuits on them. Such circuits are
8873 unlikely to be re-used, and tens of thousands of them were piling
8874 up at the fast relays, causing the relays to run out of sockets
8875 and memory. Bugfix on 0.2.0.22-rc (where clients started tunneling
8876 their directory fetches over TLS).
8877 - Fix SSL renegotiation behavior on OpenSSL versions like on Centos
8878 that claim to be earlier than 0.9.8m, but which have in reality
8879 backported huge swaths of 0.9.8m or 0.9.8n renegotiation
8880 behavior. Possible fix for some cases of bug 1346.
8881 - Directory mirrors were fetching relay descriptors only from v2
8882 directory authorities, rather than v3 authorities like they should.
8883 Only 2 v2 authorities remain (compared to 7 v3 authorities), leading
8884 to a serious bottleneck. Bugfix on 0.2.0.9-alpha. Fixes bug 1324.
8887 - Finally get rid of the deprecated and now harmful notion of "clique
8888 mode", where directory authorities maintain TLS connections to
8892 - In the util/threads test, no longer free the test_mutex before all
8893 worker threads have finished. Bugfix on 0.2.1.6-alpha.
8894 - The master thread could starve the worker threads quite badly on
8895 certain systems, causing them to run only partially in the allowed
8896 window. This resulted in test failures. Now the master thread sleeps
8897 occasionally for a few microseconds while the two worker-threads
8898 compete for the mutex. Bugfix on 0.2.0.1-alpha.
8901 Changes in version 0.2.2.13-alpha - 2010-04-24
8902 Tor 0.2.2.13-alpha addresses the recent connection and memory overload
8903 problems we've been seeing on relays, especially relays with their
8904 DirPort open. If your relay has been crashing, or you turned it off
8905 because it used too many resources, give this release a try.
8908 - Teach relays to defend themselves from connection overload. Relays
8909 now close idle circuits early if it looks like they were intended
8910 for directory fetches. Relays are also more aggressive about closing
8911 TLS connections that have no circuits on them. Such circuits are
8912 unlikely to be re-used, and tens of thousands of them were piling
8913 up at the fast relays, causing the relays to run out of sockets
8914 and memory. Bugfix on 0.2.0.22-rc (where clients started tunneling
8915 their directory fetches over TLS).
8918 - Finally get rid of the deprecated and now harmful notion of "clique
8919 mode", where directory authorities maintain TLS connections to
8921 - Directory authorities now do an immediate reachability check as soon
8922 as they hear about a new relay. This change should slightly reduce
8923 the time between setting up a relay and getting listed as running
8924 in the consensus. It should also improve the time between setting
8925 up a bridge and seeing use by bridge users.
8926 - Directory authorities no longer launch a TLS connection to every
8927 relay as they startup. Now that we have 2k+ descriptors cached,
8928 the resulting network hiccup is becoming a burden. Besides,
8929 authorities already avoid voting about Running for the first half
8930 hour of their uptime.
8933 Changes in version 0.2.2.12-alpha - 2010-04-20
8934 Tor 0.2.2.12-alpha fixes a critical bug in how directory authorities
8935 handle and vote on descriptors. It was causing relays to drop out of
8939 - Many relays have been falling out of the consensus lately because
8940 not enough authorities know about their descriptor for them to get
8941 a majority of votes. When we deprecated the v2 directory protocol,
8942 we got rid of the only way that v3 authorities can hear from each
8943 other about other descriptors. Now authorities examine every v3
8944 vote for new descriptors, and fetch them from that authority. Bugfix
8946 - Fix two typos in tor_vasprintf() that broke the compile on Windows,
8947 and a warning in or.h related to bandwidth_weight_rule_t that
8948 prevented clean compile on OS X. Fixes bug 1363; bugfix on
8950 - Fix a segfault on relays when DirReqStatistics is enabled
8951 and 24 hours pass. Bug found by keb. Fixes bug 1365; bugfix on
8955 - Demote a confusing TLS warning that relay operators might get when
8956 someone tries to talk to their OrPort. It is neither the operator's
8957 fault nor can they do anything about it. Fixes bug 1364; bugfix
8961 Changes in version 0.2.2.11-alpha - 2010-04-15
8962 Tor 0.2.2.11-alpha fixes yet another instance of broken OpenSSL
8963 libraries that was causing some relays to drop out of the consensus.
8966 - Directory mirrors were fetching relay descriptors only from v2
8967 directory authorities, rather than v3 authorities like they should.
8968 Only 2 v2 authorities remain (compared to 7 v3 authorities), leading
8969 to a serious bottleneck. Bugfix on 0.2.0.9-alpha. Fixes bug 1324.
8970 - Fix a parsing error that made every possible value of
8971 CircPriorityHalflifeMsec get treated as "1 msec". Bugfix
8972 on 0.2.2.7-alpha. Rename CircPriorityHalflifeMsec to
8973 CircuitPriorityHalflifeMsec, so authorities can tell newer relays
8974 about the option without breaking older ones.
8975 - Fix SSL renegotiation behavior on OpenSSL versions like on Centos
8976 that claim to be earlier than 0.9.8m, but which have in reality
8977 backported huge swaths of 0.9.8m or 0.9.8n renegotiation
8978 behavior. Possible fix for some cases of bug 1346.
8981 - Experiment with a more aggressive approach to preventing clients
8982 from making one-hop exit streams. Exit relays who want to try it
8983 out can set "RefuseUnknownExits 1" in their torrc, and then look
8984 for "Attempt by %s to open a stream" log messages. Let us know
8986 - Add support for statically linking zlib by specifying
8987 --enable-static-zlib, to go with our support for statically linking
8988 openssl and libevent. Resolves bug 1358.
8991 - Fix a segfault that happens whenever a Tor client that is using
8992 libevent2's bufferevents gets a hup signal. Bugfix on 0.2.2.5-alpha;
8994 - When we cleaned up the contrib/tor-exit-notice.html file, we left
8995 out the first line. Fixes bug 1295.
8996 - When building the manpage from a tarball, we required asciidoc, but
8997 the asciidoc -> roff/html conversion was already done for the
8998 tarball. Make 'make' complain only when we need asciidoc (either
8999 because we're compiling directly from git, or because we altered
9000 the asciidoc manpage in the tarball). Bugfix on 0.2.2.9-alpha.
9001 - When none of the directory authorities vote on any params, Tor
9002 segfaulted when trying to make the consensus from the votes. We
9003 didn't trigger the bug in practice, because authorities do include
9004 params in their votes. Bugfix on 0.2.2.10-alpha; fixes bug 1322.
9007 - In the util/threads test, no longer free the test_mutex before all
9008 worker threads have finished. Bugfix on 0.2.1.6-alpha.
9009 - The master thread could starve the worker threads quite badly on
9010 certain systems, causing them to run only partially in the allowed
9011 window. This resulted in test failures. Now the master thread sleeps
9012 occasionally for a few microseconds while the two worker-threads
9013 compete for the mutex. Bugfix on 0.2.0.1-alpha.
9016 Changes in version 0.2.2.10-alpha - 2010-03-07
9017 Tor 0.2.2.10-alpha fixes a regression introduced in 0.2.2.9-alpha that
9018 could prevent relays from guessing their IP address correctly. It also
9019 starts the groundwork for another client-side performance boost, since
9020 currently we're not making efficient use of relays that have both the
9021 Guard flag and the Exit flag.
9024 - Fix a regression from our patch for bug 1244 that caused relays
9025 to guess their IP address incorrectly if they didn't set Address
9026 in their torrc and/or their address fails to resolve. Bugfix on
9027 0.2.2.9-alpha; fixes bug 1269.
9029 o Major features (performance):
9030 - Directory authorities now compute consensus weightings that instruct
9031 clients how to weight relays flagged as Guard, Exit, Guard+Exit,
9032 and no flag. Clients that use these weightings will distribute
9033 network load more evenly across these different relay types. The
9034 weightings are in the consensus so we can change them globally in
9035 the future. Extra thanks to "outofwords" for finding some nasty
9036 security bugs in the first implementation of this feature.
9038 o Minor features (performance):
9039 - Always perform router selections using weighted relay bandwidth,
9040 even if we don't need a high capacity circuit at the time. Non-fast
9041 circuits now only differ from fast ones in that they can use relays
9042 not marked with the Fast flag. This "feature" could turn out to
9043 be a horrible bug; we should investigate more before it goes into
9047 - Allow disabling building of the manpages. Skipping the manpage
9048 speeds up the build considerably.
9050 o Minor bugfixes (on 0.2.2.x):
9051 - Fix a memleak in the EXTENDCIRCUIT logic. Spotted by coverity.
9052 Bugfix on 0.2.2.9-alpha.
9053 - Disallow values larger than INT32_MAX for PerConnBWRate|Burst
9054 config option. Bugfix on 0.2.2.7-alpha.
9055 - Ship the asciidoc-helper file in the tarball, so that people can
9056 build from source if they want to, and touching the .1.txt files
9057 doesn't break the build. Bugfix on 0.2.2.9-alpha.
9059 o Minor bugfixes (on 0.2.1.x or earlier):
9060 - Fix a dereference-then-NULL-check sequence when publishing
9061 descriptors. Bugfix on 0.2.1.5-alpha. Discovered by ekir; fixes
9063 - Fix another dereference-then-NULL-check sequence. Bugfix on
9064 0.2.1.14-rc. Discovered by ekir; fixes bug 1256.
9065 - Make sure we treat potentially not NUL-terminated strings correctly.
9066 Bugfix on 0.1.1.13-alpha. Discovered by rieo; fixes bug 1257.
9068 o Code simplifications and refactoring:
9069 - Fix some urls in the exit notice file and make it XHTML1.1 strict
9070 compliant. Based on a patch from Christian Kujau.
9071 - Don't use sed in asciidoc-helper anymore.
9072 - Make the build process fail if asciidoc cannot be found and
9073 building with asciidoc isn't disabled.
9076 Changes in version 0.2.2.9-alpha - 2010-02-22
9077 Tor 0.2.2.9-alpha makes Tor work again on the latest OS X, updates the
9078 location of a directory authority, and cleans up a bunch of small bugs.
9080 o Directory authority changes:
9081 - Change IP address for dannenberg (v3 directory authority), and
9082 remove moria2 (obsolete v1, v2 directory authority and v0 hidden
9083 service directory authority) from the list.
9086 - Make Tor work again on the latest OS X: when deciding whether to
9087 use strange flags to turn TLS renegotiation on, detect the OpenSSL
9088 version at run-time, not compile time. We need to do this because
9089 Apple doesn't update its dev-tools headers when it updates its
9090 libraries in a security patch.
9091 - Fix a potential buffer overflow in lookup_last_hid_serv_request()
9092 that could happen on 32-bit platforms with 64-bit time_t. Also fix
9093 a memory leak when requesting a hidden service descriptor we've
9094 requested before. Fixes bug 1242, bugfix on 0.2.0.18-alpha. Found
9096 - Authorities could be tricked into giving out the Exit flag to relays
9097 that didn't allow exiting to any ports. This bug could screw
9098 with load balancing and stats. Bugfix on 0.1.1.6-alpha; fixes bug
9099 1238. Bug discovered by Martin Kowalczyk.
9100 - When freeing a session key, zero it out completely. We only zeroed
9101 the first ptrsize bytes. Bugfix on 0.0.2pre8. Discovered and
9102 patched by ekir. Fixes bug 1254.
9105 - Fix static compilation by listing the openssl libraries in the right
9106 order. Bugfix on Tor 0.2.2.8-alpha; fixes bug 1237.
9107 - Resume handling .exit hostnames in a special way: originally we
9108 stripped the .exit part and used the requested exit relay. In
9109 0.2.2.1-alpha we stopped treating them in any special way, meaning
9110 if you use a .exit address then Tor will pass it on to the exit
9111 relay. Now we reject the .exit stream outright, since that behavior
9112 might be more expected by the user. Found and diagnosed by Scott
9113 Bennett and Downie on or-talk.
9114 - Don't spam the controller with events when we have no file
9115 descriptors available. Bugfix on 0.2.1.5-alpha. (Rate-limiting
9116 for log messages was already solved from bug 748.)
9117 - Avoid a bogus overlapped memcpy in tor_addr_copy(). Reported by
9119 - Make the DNSPort option work with libevent 2.x. Don't alter the
9120 behaviour for libevent 1.x. Fixes bug 1143. Found by SwissTorExit.
9121 - Emit a GUARD DROPPED controller event for a case we missed.
9122 - Make more fields in the controller protocol case-insensitive, since
9123 control-spec.txt said they were.
9124 - Refactor resolve_my_address() to not use gethostbyname() anymore.
9125 Fixes bug 1244; bugfix on 0.0.2pre25. Reported by Mike Mestnik.
9126 - Fix a spec conformance issue: the network-status-version token
9127 must be the first token in a v3 consensus or vote. Discovered by
9128 parakeep. Bugfix on 0.2.0.3-alpha.
9130 o Code simplifications and refactoring:
9131 - Generate our manpage and HTML documentation using Asciidoc. This
9132 change should make it easier to maintain the documentation, and
9134 - Remove the --enable-iphone option. According to reports from Marco
9135 Bonetti, Tor builds fine without any special tweaking on recent
9136 iPhone SDK versions.
9137 - Removed some unnecessary files from the source distribution. The
9138 AUTHORS file has now been merged into the people page on the
9139 website. The roadmaps and design doc can now be found in the
9140 projects directory in svn.
9141 - Enabled various circuit build timeout constants to be controlled
9142 by consensus parameters. Also set better defaults for these
9143 parameters based on experimentation on broadband and simulated
9147 - The 'EXTENDCIRCUIT' control port command can now be used with
9148 a circ id of 0 and no path. This feature will cause Tor to build
9149 a new 'fast' general purpose circuit using its own path selection
9151 - Added a BUILDTIMEOUT_SET controller event to describe changes
9152 to the circuit build timeout.
9153 - Future-proof the controller protocol a bit by ignoring keyword
9154 arguments we do not recognize.
9155 - Expand homedirs passed to tor-checkkey. This should silence a
9156 coverity complaint about passing a user-supplied string into
9157 open() without checking it.
9160 Changes in version 0.2.1.25 - 2010-03-16
9161 Tor 0.2.1.25 fixes a regression introduced in 0.2.1.23 that could
9162 prevent relays from guessing their IP address correctly. It also fixes
9163 several minor potential security bugs.
9166 - Fix a regression from our patch for bug 1244 that caused relays
9167 to guess their IP address incorrectly if they didn't set Address
9168 in their torrc and/or their address fails to resolve. Bugfix on
9169 0.2.1.23; fixes bug 1269.
9170 - When freeing a session key, zero it out completely. We only zeroed
9171 the first ptrsize bytes. Bugfix on 0.0.2pre8. Discovered and
9172 patched by ekir. Fixes bug 1254.
9175 - Fix a dereference-then-NULL-check sequence when publishing
9176 descriptors. Bugfix on 0.2.1.5-alpha. Discovered by ekir; fixes
9178 - Fix another dereference-then-NULL-check sequence. Bugfix on
9179 0.2.1.14-rc. Discovered by ekir; fixes bug 1256.
9180 - Make sure we treat potentially not NUL-terminated strings correctly.
9181 Bugfix on 0.1.1.13-alpha. Discovered by rieo; fixes bug 1257.
9185 Changes in version 0.2.1.24 - 2010-02-21
9186 Tor 0.2.1.24 makes Tor work again on the latest OS X -- this time
9190 - Work correctly out-of-the-box with even more vendor-patched versions
9191 of OpenSSL. In particular, make it so Debian and OS X don't need
9192 customized patches to run/build.
9195 Changes in version 0.2.1.23 - 2010-02-13
9196 Tor 0.2.1.23 fixes a huge client-side performance bug, makes Tor work
9197 again on the latest OS X, and updates the location of a directory
9200 o Major bugfixes (performance):
9201 - We were selecting our guards uniformly at random, and then weighting
9202 which of our guards we'd use uniformly at random. This imbalance
9203 meant that Tor clients were severely limited on throughput (and
9204 probably latency too) by the first hop in their circuit. Now we
9205 select guards weighted by currently advertised bandwidth. We also
9206 automatically discard guards picked using the old algorithm. Fixes
9207 bug 1217; bugfix on 0.2.1.3-alpha. Found by Mike Perry.
9210 - Make Tor work again on the latest OS X: when deciding whether to
9211 use strange flags to turn TLS renegotiation on, detect the OpenSSL
9212 version at run-time, not compile time. We need to do this because
9213 Apple doesn't update its dev-tools headers when it updates its
9214 libraries in a security patch.
9215 - Fix a potential buffer overflow in lookup_last_hid_serv_request()
9216 that could happen on 32-bit platforms with 64-bit time_t. Also fix
9217 a memory leak when requesting a hidden service descriptor we've
9218 requested before. Fixes bug 1242, bugfix on 0.2.0.18-alpha. Found
9221 o Directory authority changes:
9222 - Change IP address for dannenberg (v3 directory authority), and
9223 remove moria2 (obsolete v1, v2 directory authority and v0 hidden
9224 service directory authority) from the list.
9227 - Refactor resolve_my_address() to not use gethostbyname() anymore.
9228 Fixes bug 1244; bugfix on 0.0.2pre25. Reported by Mike Mestnik.
9231 - Avoid a mad rush at the beginning of each month when each client
9232 rotates half of its guards. Instead we spread the rotation out
9233 throughout the month, but we still avoid leaving a precise timestamp
9234 in the state file about when we first picked the guard. Improves
9235 over the behavior introduced in 0.1.2.17.
9238 Changes in version 0.2.2.8-alpha - 2010-01-26
9239 Tor 0.2.2.8-alpha fixes a crash bug in 0.2.2.7-alpha that has been
9240 causing bridge relays to disappear. If you're running a bridge,
9244 - Fix a memory corruption bug on bridges that occured during the
9245 inclusion of stats data in extra-info descriptors. Also fix the
9246 interface for geoip_get_bridge_stats* to prevent similar bugs in
9247 the future. Diagnosis by Tas, patch by Karsten and Sebastian.
9248 Fixes bug 1208; bugfix on 0.2.2.7-alpha.
9251 - Ignore OutboundBindAddress when connecting to localhost.
9252 Connections to localhost need to come _from_ localhost, or else
9253 local servers (like DNS and outgoing HTTP/SOCKS proxies) will often
9257 Changes in version 0.2.2.7-alpha - 2010-01-19
9258 Tor 0.2.2.7-alpha fixes a huge client-side performance bug, as well
9259 as laying the groundwork for further relay-side performance fixes. It
9260 also starts cleaning up client behavior with respect to the EntryNodes,
9261 ExitNodes, and StrictNodes config options.
9263 This release also rotates two directory authority keys, due to a
9264 security breach of some of the Torproject servers.
9266 o Directory authority changes:
9267 - Rotate keys (both v3 identity and relay identity) for moria1
9270 o Major features (performance):
9271 - We were selecting our guards uniformly at random, and then weighting
9272 which of our guards we'd use uniformly at random. This imbalance
9273 meant that Tor clients were severely limited on throughput (and
9274 probably latency too) by the first hop in their circuit. Now we
9275 select guards weighted by currently advertised bandwidth. We also
9276 automatically discard guards picked using the old algorithm. Fixes
9277 bug 1217; bugfix on 0.2.1.3-alpha. Found by Mike Perry.
9278 - When choosing which cells to relay first, relays can now favor
9279 circuits that have been quiet recently, to provide lower latency
9280 for low-volume circuits. By default, relays enable or disable this
9281 feature based on a setting in the consensus. You can override
9282 this default by using the new "CircuitPriorityHalflife" config
9283 option. Design and code by Ian Goldberg, Can Tang, and Chris
9285 - Add separate per-conn write limiting to go with the per-conn read
9286 limiting. We added a global write limit in Tor 0.1.2.5-alpha,
9287 but never per-conn write limits.
9288 - New consensus params "bwconnrate" and "bwconnburst" to let us
9289 rate-limit client connections as they enter the network. It's
9290 controlled in the consensus so we can turn it on and off for
9291 experiments. It's starting out off. Based on proposal 163.
9293 o Major features (relay selection options):
9294 - Switch to a StrictNodes config option, rather than the previous
9295 "StrictEntryNodes" / "StrictExitNodes" separation that was missing a
9296 "StrictExcludeNodes" option.
9297 - If EntryNodes, ExitNodes, ExcludeNodes, or ExcludeExitNodes
9298 change during a config reload, mark and discard all our origin
9299 circuits. This fix should address edge cases where we change the
9300 config options and but then choose a circuit that we created before
9302 - If EntryNodes or ExitNodes are set, be more willing to use an
9303 unsuitable (e.g. slow or unstable) circuit. The user asked for it,
9305 - Make EntryNodes config option much more aggressive even when
9306 StrictNodes is not set. Before it would prepend your requested
9307 entrynodes to your list of guard nodes, but feel free to use others
9308 after that. Now it chooses only from your EntryNodes if any of
9309 those are available, and only falls back to others if a) they're
9310 all down and b) StrictNodes is not set.
9311 - Now we refresh your entry guards from EntryNodes at each consensus
9312 fetch -- rather than just at startup and then they slowly rot as
9313 the network changes.
9316 - Stop bridge directory authorities from answering dbg-stability.txt
9317 directory queries, which would let people fetch a list of all
9318 bridge identities they track. Bugfix on 0.2.1.6-alpha.
9321 - Log a notice when we get a new control connection. Now it's easier
9322 for security-conscious users to recognize when a local application
9323 is knocking on their controller door. Suggested by bug 1196.
9324 - New config option "CircuitStreamTimeout" to override our internal
9325 timeout schedule for how many seconds until we detach a stream from
9326 a circuit and try a new circuit. If your network is particularly
9327 slow, you might want to set this to a number like 60.
9328 - New controller command "getinfo config-text". It returns the
9329 contents that Tor would write if you send it a SAVECONF command,
9330 so the controller can write the file to disk itself.
9331 - New options for SafeLogging to allow scrubbing only log messages
9332 generated while acting as a relay.
9333 - Ship the bridges spec file in the tarball too.
9334 - Avoid a mad rush at the beginning of each month when each client
9335 rotates half of its guards. Instead we spread the rotation out
9336 throughout the month, but we still avoid leaving a precise timestamp
9337 in the state file about when we first picked the guard. Improves
9338 over the behavior introduced in 0.1.2.17.
9340 o Minor bugfixes (compiling):
9341 - Fix compilation on OS X 10.3, which has a stub mlockall() but
9342 hides it. Bugfix on 0.2.2.6-alpha.
9343 - Fix compilation on Solaris by removing support for the
9344 DisableAllSwap config option. Solaris doesn't have an rlimit for
9345 mlockall, so we cannot use it safely. Fixes bug 1198; bugfix on
9348 o Minor bugfixes (crashes):
9349 - Do not segfault when writing buffer stats when we haven't observed
9350 a single circuit to report about. Found by Fabian Lanze. Bugfix on
9352 - If we're in the pathological case where there's no exit bandwidth
9353 but there is non-exit bandwidth, or no guard bandwidth but there
9354 is non-guard bandwidth, don't crash during path selection. Bugfix
9356 - Fix an impossible-to-actually-trigger buffer overflow in relay
9357 descriptor generation. Bugfix on 0.1.0.15.
9359 o Minor bugfixes (privacy):
9360 - Fix an instance where a Tor directory mirror might accidentally
9361 log the IP address of a misbehaving Tor client. Bugfix on
9363 - Don't list Windows capabilities in relay descriptors. We never made
9364 use of them, and maybe it's a bad idea to publish them. Bugfix
9367 o Minor bugfixes (other):
9368 - Resolve an edge case in path weighting that could make us misweight
9369 our relay selection. Fixes bug 1203; bugfix on 0.0.8rc1.
9370 - Fix statistics on client numbers by country as seen by bridges that
9371 were broken in 0.2.2.1-alpha. Also switch to reporting full 24-hour
9372 intervals instead of variable 12-to-48-hour intervals.
9373 - After we free an internal connection structure, overwrite it
9374 with a different memory value than we use for overwriting a freed
9375 internal circuit structure. Should help with debugging. Suggested
9377 - Update our OpenSSL 0.9.8l fix so that it works with OpenSSL 0.9.8m
9381 - Remove the HSAuthorityRecordStats option that version 0 hidden
9382 service authorities could have used to track statistics of overall
9383 hidden service usage.
9386 Changes in version 0.2.1.22 - 2010-01-19
9387 Tor 0.2.1.22 fixes a critical privacy problem in bridge directory
9388 authorities -- it would tell you its whole history of bridge descriptors
9389 if you make the right directory request. This stable update also
9390 rotates two of the seven v3 directory authority keys and locations.
9392 o Directory authority changes:
9393 - Rotate keys (both v3 identity and relay identity) for moria1
9397 - Stop bridge directory authorities from answering dbg-stability.txt
9398 directory queries, which would let people fetch a list of all
9399 bridge identities they track. Bugfix on 0.2.1.6-alpha.
9402 Changes in version 0.2.1.21 - 2009-12-21
9403 Tor 0.2.1.21 fixes an incompatibility with the most recent OpenSSL
9404 library. If you use Tor on Linux / Unix and you're getting SSL
9405 renegotiation errors, upgrading should help. We also recommend an
9406 upgrade if you're an exit relay.
9409 - Work around a security feature in OpenSSL 0.9.8l that prevents our
9410 handshake from working unless we explicitly tell OpenSSL that we
9411 are using SSL renegotiation safely. We are, of course, but OpenSSL
9412 0.9.8l won't work unless we say we are.
9413 - Avoid crashing if the client is trying to upload many bytes and the
9414 circuit gets torn down at the same time, or if the flip side
9415 happens on the exit relay. Bugfix on 0.2.0.1-alpha; fixes bug 1150.
9418 - Do not refuse to learn about authority certs and v2 networkstatus
9419 documents that are older than the latest consensus. This bug might
9420 have degraded client bootstrapping. Bugfix on 0.2.0.10-alpha.
9421 Spotted and fixed by xmux.
9422 - Fix a couple of very-hard-to-trigger memory leaks, and one hard-to-
9423 trigger platform-specific option misparsing case found by Coverity
9425 - Fix a compilation warning on Fedora 12 by removing an impossible-to-
9426 trigger assert. Fixes bug 1173.
9429 Changes in version 0.2.2.6-alpha - 2009-11-19
9430 Tor 0.2.2.6-alpha lays the groundwork for many upcoming features:
9431 support for the new lower-footprint "microdescriptor" directory design,
9432 future-proofing our consensus format against new hash functions or
9433 other changes, and an Android port. It also makes Tor compatible with
9434 the upcoming OpenSSL 0.9.8l release, and fixes a variety of bugs.
9437 - Directory authorities can now create, vote on, and serve multiple
9438 parallel formats of directory data as part of their voting process.
9439 Partially implements Proposal 162: "Publish the consensus in
9441 - Directory authorities can now agree on and publish small summaries
9442 of router information that clients can use in place of regular
9443 server descriptors. This transition will eventually allow clients
9444 to use far less bandwidth for downloading information about the
9445 network. Begins the implementation of Proposal 158: "Clients
9446 download consensus + microdescriptors".
9447 - The directory voting system is now extensible to use multiple hash
9448 algorithms for signatures and resource selection. Newer formats
9449 are signed with SHA256, with a possibility for moving to a better
9450 hash algorithm in the future.
9451 - New DisableAllSwap option. If set to 1, Tor will attempt to lock all
9452 current and future memory pages via mlockall(). On supported
9453 platforms (modern Linux and probably BSD but not Windows or OS X),
9454 this should effectively disable any and all attempts to page out
9455 memory. This option requires that you start your Tor as root --
9456 if you use DisableAllSwap, please consider using the User option
9457 to properly reduce the privileges of your Tor.
9458 - Numerous changes, bugfixes, and workarounds from Nathan Freitas
9459 to help Tor build correctly for Android phones.
9462 - Work around a security feature in OpenSSL 0.9.8l that prevents our
9463 handshake from working unless we explicitly tell OpenSSL that we
9464 are using SSL renegotiation safely. We are, but OpenSSL 0.9.8l
9465 won't work unless we say we are.
9468 - Fix a crash bug when trying to initialize the evdns module in
9469 Libevent 2. Bugfix on 0.2.1.16-rc.
9470 - Stop logging at severity 'warn' when some other Tor client tries
9471 to establish a circuit with us using weak DH keys. It's a protocol
9472 violation, but that doesn't mean ordinary users need to hear about
9473 it. Fixes the bug part of bug 1114. Bugfix on 0.1.0.13.
9474 - Do not refuse to learn about authority certs and v2 networkstatus
9475 documents that are older than the latest consensus. This bug might
9476 have degraded client bootstrapping. Bugfix on 0.2.0.10-alpha.
9477 Spotted and fixed by xmux.
9478 - Fix numerous small code-flaws found by Coverity Scan Rung 3.
9479 - If all authorities restart at once right before a consensus vote,
9480 nobody will vote about "Running", and clients will get a consensus
9481 with no usable relays. Instead, authorities refuse to build a
9482 consensus if this happens. Bugfix on 0.2.0.10-alpha; fixes bug 1066.
9483 - If your relay can't keep up with the number of incoming create
9484 cells, it would log one warning per failure into your logs. Limit
9485 warnings to 1 per minute. Bugfix on 0.0.2pre10; fixes bug 1042.
9486 - Bridges now use "reject *:*" as their default exit policy. Bugfix
9487 on 0.2.0.3-alpha; fixes bug 1113.
9488 - Fix a memory leak on directory authorities during voting that was
9489 introduced in 0.2.2.1-alpha. Found via valgrind.
9492 Changes in version 0.2.1.20 - 2009-10-15
9493 Tor 0.2.1.20 fixes a crash bug when you're accessing many hidden
9494 services at once, prepares for more performance improvements, and
9495 fixes a bunch of smaller bugs.
9497 The Windows and OS X bundles also include a more recent Vidalia,
9498 and switch from Privoxy to Polipo.
9500 The OS X installers are now drag and drop. It's best to un-install
9501 Tor/Vidalia and then install this new bundle, rather than upgrade. If
9502 you want to upgrade, you'll need to update the paths for Tor and Polipo
9503 in the Vidalia Settings window.
9506 - Send circuit or stream sendme cells when our window has decreased
9507 by 100 cells, not when it has decreased by 101 cells. Bug uncovered
9508 by Karsten when testing the "reduce circuit window" performance
9509 patch. Bugfix on the 54th commit on Tor -- from July 2002,
9510 before the release of Tor 0.0.0. This is the new winner of the
9512 - Fix a remotely triggerable memory leak when a consensus document
9513 contains more than one signature from the same voter. Bugfix on
9515 - Avoid segfault in rare cases when finishing an introduction circuit
9516 as a client and finding out that we don't have an introduction key
9517 for it. Fixes bug 1073. Reported by Aaron Swartz.
9520 - Tor now reads the "circwindow" parameter out of the consensus,
9521 and uses that value for its circuit package window rather than the
9522 default of 1000 cells. Begins the implementation of proposal 168.
9524 o New directory authorities:
9525 - Set up urras (run by Jacob Appelbaum) as the seventh v3 directory
9527 - Move moria1 and tonga to alternate IP addresses.
9530 - Fix a signed/unsigned compile warning in 0.2.1.19.
9531 - Fix possible segmentation fault on directory authorities. Bugfix on
9533 - Fix an extremely rare infinite recursion bug that could occur if
9534 we tried to log a message after shutting down the log subsystem.
9535 Found by Matt Edman. Bugfix on 0.2.0.16-alpha.
9536 - Fix an obscure bug where hidden services on 64-bit big-endian
9537 systems might mis-read the timestamp in v3 introduce cells, and
9538 refuse to connect back to the client. Discovered by "rotor".
9539 Bugfix on 0.2.1.6-alpha.
9540 - We were triggering a CLOCK_SKEW controller status event whenever
9541 we connect via the v2 connection protocol to any relay that has
9542 a wrong clock. Instead, we should only inform the controller when
9543 it's a trusted authority that claims our clock is wrong. Bugfix
9544 on 0.2.0.20-rc; starts to fix bug 1074. Reported by SwissTorExit.
9545 - We were telling the controller about CHECKING_REACHABILITY and
9546 REACHABILITY_FAILED status events whenever we launch a testing
9547 circuit or notice that one has failed. Instead, only tell the
9548 controller when we want to inform the user of overall success or
9549 overall failure. Bugfix on 0.1.2.6-alpha. Fixes bug 1075. Reported
9551 - Don't warn when we're using a circuit that ends with a node
9552 excluded in ExcludeExitNodes, but the circuit is not used to access
9553 the outside world. This should help fix bug 1090. Bugfix on
9555 - Work around a small memory leak in some versions of OpenSSL that
9556 stopped the memory used by the hostname TLS extension from being
9560 - Add a "getinfo status/accepted-server-descriptor" controller
9561 command, which is the recommended way for controllers to learn
9562 whether our server descriptor has been successfully received by at
9563 least on directory authority. Un-recommend good-server-descriptor
9564 getinfo and status events until we have a better design for them.
9567 Changes in version 0.2.2.5-alpha - 2009-10-11
9568 Tor 0.2.2.5-alpha fixes a few compile problems in 0.2.2.4-alpha.
9571 - Make the tarball compile again. Oops. Bugfix on 0.2.2.4-alpha.
9573 o Directory authorities:
9574 - Temporarily (just for this release) move dizum to an alternate
9578 Changes in version 0.2.2.4-alpha - 2009-10-10
9579 Tor 0.2.2.4-alpha fixes more crash bugs in 0.2.2.2-alpha. It also
9580 introduces a new unit test framework, shifts directry authority
9581 addresses around to reduce the impact from recent blocking events,
9582 and fixes a few smaller bugs.
9585 - Fix several more asserts in the circuit_build_times code, for
9586 example one that causes Tor to fail to start once we have
9587 accumulated 5000 build times in the state file. Bugfixes on
9588 0.2.2.2-alpha; fixes bug 1108.
9590 o New directory authorities:
9591 - Move moria1 and Tonga to alternate IP addresses.
9594 - Log SSL state transitions at debug level during handshake, and
9595 include SSL states in error messages. This may help debug future
9596 SSL handshake issues.
9597 - Add a new "Handshake" log domain for activities that happen
9598 during the TLS handshake.
9599 - Revert to the "June 3 2009" ip-to-country file. The September one
9600 seems to have removed most US IP addresses.
9601 - Directory authorities now reject Tor relays with versions less than
9602 0.1.2.14. This step cuts out four relays from the current network,
9603 none of which are very big.
9606 - Fix a couple of smaller issues with gathering statistics. Bugfixes
9608 - Fix two memory leaks in the error case of
9609 circuit_build_times_parse_state(). Bugfix on 0.2.2.2-alpha.
9610 - Don't count one-hop circuits when we're estimating how long it
9611 takes circuits to build on average. Otherwise we'll set our circuit
9612 build timeout lower than we should. Bugfix on 0.2.2.2-alpha.
9613 - Directory authorities no longer change their opinion of, or vote on,
9614 whether a router is Running, unless they have themselves been
9615 online long enough to have some idea. Bugfix on 0.2.0.6-alpha.
9618 o Code simplifications and refactoring:
9619 - Revise our unit tests to use the "tinytest" framework, so we
9620 can run tests in their own processes, have smarter setup/teardown
9621 code, and so on. The unit test code has moved to its own
9622 subdirectory, and has been split into multiple modules.
9625 Changes in version 0.2.2.3-alpha - 2009-09-23
9626 Tor 0.2.2.3-alpha fixes a few crash bugs in 0.2.2.2-alpha.
9629 - Fix an overzealous assert in our new circuit build timeout code.
9630 Bugfix on 0.2.2.2-alpha; fixes bug 1103.
9633 - If the networkstatus consensus tells us that we should use a
9634 negative circuit package window, ignore it. Otherwise we'll
9635 believe it and then trigger an assert. Bugfix on 0.2.2.2-alpha.
9638 Changes in version 0.2.2.2-alpha - 2009-09-21
9639 Tor 0.2.2.2-alpha introduces our latest performance improvement for
9640 clients: Tor tracks the average time it takes to build a circuit, and
9641 avoids using circuits that take too long to build. For fast connections,
9642 this feature can cut your expected latency in half. For slow or flaky
9643 connections, it could ruin your Tor experience. Let us know if it does!
9646 - Tor now tracks how long it takes to build client-side circuits
9647 over time, and adapts its timeout to local network performance.
9648 Since a circuit that takes a long time to build will also provide
9649 bad performance, we get significant latency improvements by
9650 discarding the slowest 20% of circuits. Specifically, Tor creates
9651 circuits more aggressively than usual until it has enough data
9652 points for a good timeout estimate. Implements proposal 151.
9653 We are especially looking for reports (good and bad) from users with
9654 both EDGE and broadband connections that can move from broadband
9655 to EDGE and find out if the build-time data in the .tor/state gets
9656 reset without loss of Tor usability. You should also see a notice
9657 log message telling you that Tor has reset its timeout.
9658 - Directory authorities can now vote on arbitary integer values as
9659 part of the consensus process. This is designed to help set
9660 network-wide parameters. Implements proposal 167.
9661 - Tor now reads the "circwindow" parameter out of the consensus,
9662 and uses that value for its circuit package window rather than the
9663 default of 1000 cells. Begins the implementation of proposal 168.
9666 - Fix a remotely triggerable memory leak when a consensus document
9667 contains more than one signature from the same voter. Bugfix on
9671 - Fix an extremely rare infinite recursion bug that could occur if
9672 we tried to log a message after shutting down the log subsystem.
9673 Found by Matt Edman. Bugfix on 0.2.0.16-alpha.
9674 - Fix parsing for memory or time units given without a space between
9675 the number and the unit. Bugfix on 0.2.2.1-alpha; fixes bug 1076.
9676 - A networkstatus vote must contain exactly one signature. Spec
9677 conformance issue. Bugfix on 0.2.0.3-alpha.
9678 - Fix an obscure bug where hidden services on 64-bit big-endian
9679 systems might mis-read the timestamp in v3 introduce cells, and
9680 refuse to connect back to the client. Discovered by "rotor".
9681 Bugfix on 0.2.1.6-alpha.
9682 - We were triggering a CLOCK_SKEW controller status event whenever
9683 we connect via the v2 connection protocol to any relay that has
9684 a wrong clock. Instead, we should only inform the controller when
9685 it's a trusted authority that claims our clock is wrong. Bugfix
9686 on 0.2.0.20-rc; starts to fix bug 1074. Reported by SwissTorExit.
9687 - We were telling the controller about CHECKING_REACHABILITY and
9688 REACHABILITY_FAILED status events whenever we launch a testing
9689 circuit or notice that one has failed. Instead, only tell the
9690 controller when we want to inform the user of overall success or
9691 overall failure. Bugfix on 0.1.2.6-alpha. Fixes bug 1075. Reported
9693 - Don't warn when we're using a circuit that ends with a node
9694 excluded in ExcludeExitNodes, but the circuit is not used to access
9695 the outside world. This should help fix bug 1090, but more problems
9696 remain. Bugfix on 0.2.1.6-alpha.
9697 - Work around a small memory leak in some versions of OpenSSL that
9698 stopped the memory used by the hostname TLS extension from being
9700 - Make our 'torify' script more portable; if we have only one of
9701 'torsocks' or 'tsocks' installed, don't complain to the user;
9702 and explain our warning about tsocks better.
9705 - Add a "getinfo status/accepted-server-descriptor" controller
9706 command, which is the recommended way for controllers to learn
9707 whether our server descriptor has been successfully received by at
9708 least on directory authority. Un-recommend good-server-descriptor
9709 getinfo and status events until we have a better design for them.
9710 - Update to the "September 4 2009" ip-to-country file.
9713 Changes in version 0.2.2.1-alpha - 2009-08-26
9714 Tor 0.2.2.1-alpha disables ".exit" address notation by default, allows
9715 Tor clients to bootstrap on networks where only port 80 is reachable,
9716 makes it more straightforward to support hardware crypto accelerators,
9717 and starts the groundwork for gathering stats safely at relays.
9720 - Start the process of disabling ".exit" address notation, since it
9721 can be used for a variety of esoteric application-level attacks
9722 on users. To reenable it, set "AllowDotExit 1" in your torrc. Fix
9725 o New directory authorities:
9726 - Set up urras (run by Jacob Appelbaum) as the seventh v3 directory
9730 - New AccelName and AccelDir options add support for dynamic OpenSSL
9731 hardware crypto acceleration engines.
9732 - Tor now supports tunneling all of its outgoing connections over
9733 a SOCKS proxy, using the SOCKS4Proxy and/or SOCKS5Proxy
9734 configuration options. Code by Christopher Davis.
9737 - Send circuit or stream sendme cells when our window has decreased
9738 by 100 cells, not when it has decreased by 101 cells. Bug uncovered
9739 by Karsten when testing the "reduce circuit window" performance
9740 patch. Bugfix on the 54th commit on Tor -- from July 2002,
9741 before the release of Tor 0.0.0. This is the new winner of the
9744 o New options for gathering stats safely:
9745 - Directory mirrors that set "DirReqStatistics 1" write statistics
9746 about directory requests to disk every 24 hours. As compared to the
9747 --enable-geoip-stats flag in 0.2.1.x, there are a few improvements:
9748 1) stats are written to disk exactly every 24 hours; 2) estimated
9749 shares of v2 and v3 requests are determined as mean values, not at
9750 the end of a measurement period; 3) unresolved requests are listed
9751 with country code '??'; 4) directories also measure download times.
9752 - Exit nodes that set "ExitPortStatistics 1" write statistics on the
9753 number of exit streams and transferred bytes per port to disk every
9755 - Relays that set "CellStatistics 1" write statistics on how long
9756 cells spend in their circuit queues to disk every 24 hours.
9757 - Entry nodes that set "EntryStatistics 1" write statistics on the
9758 rough number and origins of connecting clients to disk every 24
9760 - Relays that write any of the above statistics to disk and set
9761 "ExtraInfoStatistics 1" include the past 24 hours of statistics in
9762 their extra-info documents.
9765 - New --digests command-line switch to output the digests of the
9766 source files Tor was built with.
9767 - The "torify" script now uses torsocks where available.
9768 - The memarea code now uses a sentinel value at the end of each area
9769 to make sure nothing writes beyond the end of an area. This might
9770 help debug some conceivable causes of bug 930.
9771 - Time and memory units in the configuration file can now be set to
9772 fractional units. For example, "2.5 GB" is now a valid value for
9774 - Certain Tor clients (such as those behind check.torproject.org) may
9775 want to fetch the consensus in an extra early manner. To enable this
9776 a user may now set FetchDirInfoExtraEarly to 1. This also depends on
9777 setting FetchDirInfoEarly to 1. Previous behavior will stay the same
9778 as only certain clients who must have this information sooner should
9780 - Instead of adding the svn revision to the Tor version string, report
9781 the git commit (when we're building from a git checkout).
9784 - If any of the v3 certs we download are unparseable, we should
9785 actually notice the failure so we don't retry indefinitely. Bugfix
9786 on 0.2.0.x; reported by "rotator".
9787 - If the cached cert file is unparseable, warn but don't exit.
9788 - Fix possible segmentation fault on directory authorities. Bugfix on
9790 - When Tor fails to parse a descriptor of any kind, dump it to disk.
9791 Might help diagnosing bug 1051.
9793 o Deprecated and removed features:
9794 - The controller no longer accepts the old obsolete "addr-mappings/"
9795 or "unregistered-servers-" GETINFO values.
9796 - Hidden services no longer publish version 0 descriptors, and clients
9797 do not request or use version 0 descriptors. However, the old hidden
9798 service authorities still accept and serve version 0 descriptors
9799 when contacted by older hidden services/clients.
9800 - The EXTENDED_EVENTS and VERBOSE_NAMES controller features are now
9801 always on; using them is necessary for correct forward-compatible
9803 - Remove support for .noconnect style addresses. Nobody was using
9804 them, and they provided another avenue for detecting Tor users
9805 via application-level web tricks.
9807 o Packaging changes:
9808 - Upgrade Vidalia from 0.1.15 to 0.2.3 in the Windows and OS X
9809 installer bundles. See
9810 https://trac.vidalia-project.net/browser/vidalia/tags/vidalia-0.2.3/CHANGELOG
9811 for details of what's new in Vidalia 0.2.3.
9812 - Windows Vidalia Bundle: update Privoxy from 3.0.6 to 3.0.14-beta.
9813 - OS X Vidalia Bundle: move to Polipo 1.0.4 with Tor specific
9814 configuration file, rather than the old Privoxy.
9815 - OS X Vidalia Bundle: Vidalia, Tor, and Polipo are compiled as
9816 x86-only for better compatibility with OS X 10.6, aka Snow Leopard.
9817 - OS X Tor Expert Bundle: Tor is compiled as x86-only for
9818 better compatibility with OS X 10.6, aka Snow Leopard.
9819 - OS X Vidalia Bundle: The multi-package installer is now replaced
9820 by a simple drag and drop to the /Applications folder. This change
9821 occurred with the upgrade to Vidalia 0.2.3.
9824 Changes in version 0.2.1.19 - 2009-07-28
9825 Tor 0.2.1.19 fixes a major bug with accessing and providing hidden
9826 services on Tor 0.2.1.3-alpha through 0.2.1.18.
9829 - Make accessing hidden services on 0.2.1.x work right again.
9830 Bugfix on 0.2.1.3-alpha; workaround for bug 1038. Diagnosis and
9831 part of patch provided by "optimist".
9834 - When a relay/bridge is writing out its identity key fingerprint to
9835 the "fingerprint" file and to its logs, write it without spaces. Now
9836 it will look like the fingerprints in our bridges documentation,
9837 and confuse fewer users.
9840 - Relays no longer publish a new server descriptor if they change
9841 their MaxAdvertisedBandwidth config option but it doesn't end up
9842 changing their advertised bandwidth numbers. Bugfix on 0.2.0.28-rc;
9843 fixes bug 1026. Patch from Sebastian.
9844 - Avoid leaking memory every time we get a create cell but we have
9845 so many already queued that we refuse it. Bugfix on 0.2.0.19-alpha;
9846 fixes bug 1034. Reported by BarkerJr.
9849 Changes in version 0.2.1.18 - 2009-07-24
9850 Tor 0.2.1.18 lays the foundations for performance improvements,
9851 adds status events to help users diagnose bootstrap problems, adds
9852 optional authentication/authorization for hidden services, fixes a
9853 variety of potential anonymity problems, and includes a huge pile of
9854 other features and bug fixes.
9857 - Add LIBS=-lrt to Makefile.am so the Tor RPMs use a static libevent.
9860 Changes in version 0.2.1.17-rc - 2009-07-07
9861 Tor 0.2.1.17-rc marks the fourth -- and hopefully last -- release
9862 candidate for the 0.2.1.x series. It lays the groundwork for further
9863 client performance improvements, and also fixes a big bug with directory
9864 authorities that were causing them to assign Guard and Stable flags
9867 The Windows bundles also finally include the geoip database that we
9868 thought we'd been shipping since 0.2.0.x (oops), and the OS X bundles
9869 should actually install Torbutton rather than giving you a cryptic
9870 failure message (oops).
9873 - Clients now use the bandwidth values in the consensus, rather than
9874 the bandwidth values in each relay descriptor. This approach opens
9875 the door to more accurate bandwidth estimates once the directory
9876 authorities start doing active measurements. Implements more of
9880 - When Tor clients restart after 1-5 days, they discard all their
9881 cached descriptors as too old, but they still use the cached
9882 consensus document. This approach is good for robustness, but
9883 bad for performance: since they don't know any bandwidths, they
9884 end up choosing at random rather than weighting their choice by
9885 speed. Fixed by the above feature of putting bandwidths in the
9886 consensus. Bugfix on 0.2.0.x.
9887 - Directory authorities were neglecting to mark relays down in their
9888 internal histories if the relays fall off the routerlist without
9889 ever being found unreachable. So there were relays in the histories
9890 that haven't been seen for eight months, and are listed as being
9891 up for eight months. This wreaked havoc on the "median wfu"
9892 and "median mtbf" calculations, in turn making Guard and Stable
9893 flags very wrong, hurting network performance. Fixes bugs 696 and
9894 969. Bugfix on 0.2.0.6-alpha.
9897 - Serve the DirPortFrontPage page even when we have been approaching
9898 our quotas recently. Fixes bug 1013; bugfix on 0.2.1.8-alpha.
9899 - The control port would close the connection before flushing long
9900 replies, such as the network consensus, if a QUIT command was issued
9901 before the reply had completed. Now, the control port flushes all
9902 pending replies before closing the connection. Also fixed a spurious
9903 warning when a QUIT command is issued after a malformed or rejected
9904 AUTHENTICATE command, but before the connection was closed. Patch
9905 by Marcus Griep. Bugfix on 0.2.0.x; fixes bugs 1015 and 1016.
9906 - When we can't find an intro key for a v2 hidden service descriptor,
9907 fall back to the v0 hidden service descriptor and log a bug message.
9908 Workaround for bug 1024.
9909 - Fix a log message that did not respect the SafeLogging option.
9913 - If we're a relay and we change our IP address, be more verbose
9914 about the reason that made us change. Should help track down
9915 further bugs for relays on dynamic IP addresses.
9918 Changes in version 0.2.0.35 - 2009-06-24
9920 - Avoid crashing in the presence of certain malformed descriptors.
9921 Found by lark, and by automated fuzzing.
9922 - Fix an edge case where a malicious exit relay could convince a
9923 controller that the client's DNS question resolves to an internal IP
9924 address. Bug found and fixed by "optimist"; bugfix on 0.1.2.8-beta.
9927 - Finally fix the bug where dynamic-IP relays disappear when their
9928 IP address changes: directory mirrors were mistakenly telling
9929 them their old address if they asked via begin_dir, so they
9930 never got an accurate answer about their new address, so they
9931 just vanished after a day. For belt-and-suspenders, relays that
9932 don't set Address in their config now avoid using begin_dir for
9933 all direct connections. Should fix bugs 827, 883, and 900.
9934 - Fix a timing-dependent, allocator-dependent, DNS-related crash bug
9935 that would occur on some exit nodes when DNS failures and timeouts
9936 occurred in certain patterns. Fix for bug 957.
9939 - When starting with a cache over a few days old, do not leak
9940 memory for the obsolete router descriptors in it. Bugfix on
9941 0.2.0.33; fixes bug 672.
9942 - Hidden service clients didn't use a cached service descriptor that
9943 was older than 15 minutes, but wouldn't fetch a new one either,
9944 because there was already one in the cache. Now, fetch a v2
9945 descriptor unless the same descriptor was added to the cache within
9946 the last 15 minutes. Fixes bug 997; reported by Marcus Griep.
9949 Changes in version 0.2.1.16-rc - 2009-06-20
9950 Tor 0.2.1.16-rc speeds up performance for fast exit relays, and fixes
9951 a bunch of minor bugs.
9954 - Fix an edge case where a malicious exit relay could convince a
9955 controller that the client's DNS question resolves to an internal IP
9956 address. Bug found and fixed by "optimist"; bugfix on 0.1.2.8-beta.
9958 o Major performance improvements (on 0.2.0.x):
9959 - Disable and refactor some debugging checks that forced a linear scan
9960 over the whole server-side DNS cache. These accounted for over 50%
9961 of CPU time on a relatively busy exit node's gprof profile. Found
9963 - Disable some debugging checks that appeared in exit node profile
9967 - Update to the "June 3 2009" ip-to-country file.
9968 - Do not have tor-resolve automatically refuse all .onion addresses;
9969 if AutomapHostsOnResolve is set in your torrc, this will work fine.
9971 o Minor bugfixes (on 0.2.0.x):
9972 - Log correct error messages for DNS-related network errors on
9974 - Fix a race condition that could cause crashes or memory corruption
9975 when running as a server with a controller listening for log
9977 - Avoid crashing when we have a policy specified in a DirPolicy or
9978 SocksPolicy or ReachableAddresses option with ports set on it,
9979 and we re-load the policy. May fix bug 996.
9980 - Hidden service clients didn't use a cached service descriptor that
9981 was older than 15 minutes, but wouldn't fetch a new one either,
9982 because there was already one in the cache. Now, fetch a v2
9983 descriptor unless the same descriptor was added to the cache within
9984 the last 15 minutes. Fixes bug 997; reported by Marcus Griep.
9986 o Minor bugfixes (on 0.2.1.x):
9987 - Don't warn users about low port and hibernation mix when they
9988 provide a *ListenAddress directive to fix that. Bugfix on
9990 - When switching back and forth between bridge mode, do not start
9991 gathering GeoIP data until two hours have passed.
9992 - Do not complain that the user has requested an excluded node as
9993 an exit when the node is not really an exit. This could happen
9994 because the circuit was for testing, or an introduction point.
9998 Changes in version 0.2.1.15-rc - 2009-05-25
9999 Tor 0.2.1.15-rc marks the second release candidate for the 0.2.1.x
10000 series. It fixes a major bug on fast exit relays, as well as a variety
10001 of more minor bugs.
10003 o Major bugfixes (on 0.2.0.x):
10004 - Fix a timing-dependent, allocator-dependent, DNS-related crash bug
10005 that would occur on some exit nodes when DNS failures and timeouts
10006 occurred in certain patterns. Fix for bug 957.
10008 o Minor bugfixes (on 0.2.0.x):
10009 - Actually return -1 in the error case for read_bandwidth_usage().
10010 Harmless bug, since we currently don't care about the return value
10011 anywhere. Bugfix on 0.2.0.9-alpha.
10012 - Provide a more useful log message if bug 977 (related to buffer
10013 freelists) ever reappears, and do not crash right away.
10014 - Fix an assertion failure on 64-bit platforms when we allocated
10015 memory right up to the end of a memarea, then realigned the memory
10016 one step beyond the end. Fixes a possible cause of bug 930.
10017 - Protect the count of open sockets with a mutex, so we can't
10018 corrupt it when two threads are closing or opening sockets at once.
10019 Fix for bug 939. Bugfix on 0.2.0.1-alpha.
10020 - Don't allow a bridge to publish its router descriptor to a
10021 non-bridge directory authority. Fixes part of bug 932.
10022 - When we change to or from being a bridge, reset our counts of
10023 client usage by country. Fixes bug 932.
10024 - Fix a bug that made stream bandwidth get misreported to the
10026 - Stop using malloc_usable_size() to use more area than we had
10027 actually allocated: it was safe, but made valgrind really unhappy.
10028 - Fix a memory leak when v3 directory authorities load their keys
10029 and cert from disk. Bugfix on 0.2.0.1-alpha.
10031 o Minor bugfixes (on 0.2.1.x):
10032 - Fix use of freed memory when deciding to mark a non-addable
10033 descriptor as never-downloadable. Bugfix on 0.2.1.9-alpha.
10036 Changes in version 0.2.1.14-rc - 2009-04-12
10037 Tor 0.2.1.14-rc marks the first release candidate for the 0.2.1.x
10038 series. It begins fixing some major performance problems, and also
10039 finally addresses the bug that was causing relays on dynamic IP
10040 addresses to fall out of the directory.
10043 - Clients replace entry guards that were chosen more than a few months
10044 ago. This change should significantly improve client performance,
10045 especially once more people upgrade, since relays that have been
10046 a guard for a long time are currently overloaded.
10048 o Major bugfixes (on 0.2.0):
10049 - Finally fix the bug where dynamic-IP relays disappear when their
10050 IP address changes: directory mirrors were mistakenly telling
10051 them their old address if they asked via begin_dir, so they
10052 never got an accurate answer about their new address, so they
10053 just vanished after a day. For belt-and-suspenders, relays that
10054 don't set Address in their config now avoid using begin_dir for
10055 all direct connections. Should fix bugs 827, 883, and 900.
10056 - Relays were falling out of the networkstatus consensus for
10057 part of a day if they changed their local config but the
10058 authorities discarded their new descriptor as "not sufficiently
10059 different". Now directory authorities accept a descriptor as changed
10060 if bandwidthrate or bandwidthburst changed. Partial fix for bug 962;
10061 patch by Sebastian.
10062 - Avoid crashing in the presence of certain malformed descriptors.
10063 Found by lark, and by automated fuzzing.
10066 - When generating circuit events with verbose nicknames for
10067 controllers, try harder to look up nicknames for routers on a
10068 circuit. (Previously, we would look in the router descriptors we had
10069 for nicknames, but not in the consensus.) Partial fix for bug 941.
10070 - If the bridge config line doesn't specify a port, assume 443.
10071 This makes bridge lines a bit smaller and easier for users to
10073 - Raise the minimum bandwidth to be a relay from 20000 bytes to 20480
10074 bytes (aka 20KB/s), to match our documentation. Also update
10075 directory authorities so they always assign the Fast flag to relays
10076 with 20KB/s of capacity. Now people running relays won't suddenly
10077 find themselves not seeing any use, if the network gets faster
10079 - Update to the "April 3 2009" ip-to-country file.
10082 - Avoid trying to print raw memory to the logs when we decide to
10083 give up on downloading a given relay descriptor. Bugfix on
10085 - In tor-resolve, when the Tor client to use is specified by
10086 <hostname>:<port>, actually use the specified port rather than
10087 defaulting to 9050. Bugfix on 0.2.1.6-alpha.
10088 - Make directory usage recording work again. Bugfix on 0.2.1.6-alpha.
10089 - When starting with a cache over a few days old, do not leak
10090 memory for the obsolete router descriptors in it. Bugfix on
10092 - Avoid double-free on list of successfully uploaded hidden
10093 service discriptors. Fix for bug 948. Bugfix on 0.2.1.6-alpha.
10094 - Change memarea_strndup() implementation to work even when
10095 duplicating a string at the end of a page. This bug was
10096 harmless for now, but could have meant crashes later. Fix by
10097 lark. Bugfix on 0.2.1.1-alpha.
10098 - Limit uploaded directory documents to be 16M rather than 500K.
10099 The directory authorities were refusing v3 consensus votes from
10100 other authorities, since the votes are now 504K. Fixes bug 959;
10101 bugfix on 0.0.2pre17 (where we raised it from 50K to 500K ;).
10102 - Directory authorities should never send a 503 "busy" response to
10103 requests for votes or keys. Bugfix on 0.2.0.8-alpha; exposed by
10107 Changes in version 0.2.1.13-alpha - 2009-03-09
10108 Tor 0.2.1.13-alpha includes another big pile of minor bugfixes and
10109 cleanups. We're finally getting close to a release candidate.
10112 - Correctly update the list of which countries we exclude as
10113 exits, when the GeoIP file is loaded or reloaded. Diagnosed by
10114 lark. Bugfix on 0.2.1.6-alpha.
10116 o Minor bugfixes (on 0.2.0.x and earlier):
10117 - Automatically detect MacOSX versions earlier than 10.4.0, and
10118 disable kqueue from inside Tor when running with these versions.
10119 We previously did this from the startup script, but that was no
10120 help to people who didn't use the startup script. Resolves bug 863.
10121 - When we had picked an exit node for a connection, but marked it as
10122 "optional", and it turned out we had no onion key for the exit,
10123 stop wanting that exit and try again. This situation may not
10124 be possible now, but will probably become feasible with proposal
10125 158. Spotted by rovv. Fixes another case of bug 752.
10126 - Clients no longer cache certificates for authorities they do not
10127 recognize. Bugfix on 0.2.0.9-alpha.
10128 - When we can't transmit a DNS request due to a network error, retry
10129 it after a while, and eventually transmit a failing response to
10130 the RESOLVED cell. Bugfix on 0.1.2.5-alpha.
10131 - If the controller claimed responsibility for a stream, but that
10132 stream never finished making its connection, it would live
10133 forever in circuit_wait state. Now we close it after SocksTimeout
10134 seconds. Bugfix on 0.1.2.7-alpha; reported by Mike Perry.
10135 - Drop begin cells to a hidden service if they come from the middle
10136 of a circuit. Patch from lark.
10137 - When we erroneously receive two EXTEND cells for the same circuit
10138 ID on the same connection, drop the second. Patch from lark.
10139 - Fix a crash that occurs on exit nodes when a nameserver request
10140 timed out. Bugfix on 0.1.2.1-alpha; our CLEAR debugging code had
10141 been suppressing the bug since 0.1.2.10-alpha. Partial fix for
10143 - Do not assume that a stack-allocated character array will be
10144 64-bit aligned on platforms that demand that uint64_t access is
10145 aligned. Possible fix for bug 604.
10146 - Parse dates and IPv4 addresses in a locale- and libc-independent
10147 manner, to avoid platform-dependent behavior on malformed input.
10148 - Build correctly when configured to build outside the main source
10149 path. Patch from Michael Gold.
10150 - We were already rejecting relay begin cells with destination port
10151 of 0. Now also reject extend cells with destination port or address
10152 of 0. Suggested by lark.
10154 o Minor bugfixes (on 0.2.1.x):
10155 - Don't re-extend introduction circuits if we ran out of RELAY_EARLY
10156 cells. Bugfix on 0.2.1.3-alpha. Fixes more of bug 878.
10157 - If we're an exit node, scrub the IP address to which we are exiting
10158 in the logs. Bugfix on 0.2.1.8-alpha.
10161 - On Linux, use the prctl call to re-enable core dumps when the user
10163 - New controller event NEWCONSENSUS that lists the networkstatus
10164 lines for every recommended relay. Now controllers like Torflow
10165 can keep up-to-date on which relays they should be using.
10166 - Update to the "February 26 2009" ip-to-country file.
10169 Changes in version 0.2.0.34 - 2009-02-08
10170 Tor 0.2.0.34 features several more security-related fixes. You should
10171 upgrade, especially if you run an exit relay (remote crash) or a
10172 directory authority (remote infinite loop), or you're on an older
10173 (pre-XP) or not-recently-patched Windows (remote exploit).
10175 This release marks end-of-life for Tor 0.1.2.x. Those Tor versions
10176 have many known flaws, and nobody should be using them. You should
10177 upgrade. If you're using a Linux or BSD and its packages are obsolete,
10178 stop using those packages and upgrade anyway.
10181 - Fix an infinite-loop bug on handling corrupt votes under certain
10182 circumstances. Bugfix on 0.2.0.8-alpha.
10183 - Fix a temporary DoS vulnerability that could be performed by
10184 a directory mirror. Bugfix on 0.2.0.9-alpha; reported by lark.
10185 - Avoid a potential crash on exit nodes when processing malformed
10186 input. Remote DoS opportunity. Bugfix on 0.2.0.33.
10187 - Do not accept incomplete ipv4 addresses (like 192.168.0) as valid.
10188 Spec conformance issue. Bugfix on Tor 0.0.2pre27.
10191 - Fix compilation on systems where time_t is a 64-bit integer.
10192 Patch from Matthias Drochner.
10193 - Don't consider expiring already-closed client connections. Fixes
10194 bug 893. Bugfix on 0.0.2pre20.
10197 Changes in version 0.2.1.12-alpha - 2009-02-08
10198 Tor 0.2.1.12-alpha features several more security-related fixes. You
10199 should upgrade, especially if you run an exit relay (remote crash) or
10200 a directory authority (remote infinite loop), or you're on an older
10201 (pre-XP) or not-recently-patched Windows (remote exploit). It also
10202 includes a big pile of minor bugfixes and cleanups.
10205 - Fix an infinite-loop bug on handling corrupt votes under certain
10206 circumstances. Bugfix on 0.2.0.8-alpha.
10207 - Fix a temporary DoS vulnerability that could be performed by
10208 a directory mirror. Bugfix on 0.2.0.9-alpha; reported by lark.
10209 - Avoid a potential crash on exit nodes when processing malformed
10210 input. Remote DoS opportunity. Bugfix on 0.2.1.7-alpha.
10213 - Let controllers actually ask for the "clients_seen" event for
10214 getting usage summaries on bridge relays. Bugfix on 0.2.1.10-alpha;
10215 reported by Matt Edman.
10216 - Fix a compile warning on OSX Panther. Fixes bug 913; bugfix against
10218 - Fix a bug in address parsing that was preventing bridges or hidden
10219 service targets from being at IPv6 addresses.
10220 - Solve a bug that kept hardware crypto acceleration from getting
10221 enabled when accounting was turned on. Fixes bug 907. Bugfix on
10223 - Remove a bash-ism from configure.in to build properly on non-Linux
10224 platforms. Bugfix on 0.2.1.1-alpha.
10225 - Fix code so authorities _actually_ send back X-Descriptor-Not-New
10226 headers. Bugfix on 0.2.0.10-alpha.
10227 - Don't consider expiring already-closed client connections. Fixes
10228 bug 893. Bugfix on 0.0.2pre20.
10229 - Fix another interesting corner-case of bug 891 spotted by rovv:
10230 Previously, if two hosts had different amounts of clock drift, and
10231 one of them created a new connection with just the wrong timing,
10232 the other might decide to deprecate the new connection erroneously.
10233 Bugfix on 0.1.1.13-alpha.
10234 - Resolve a very rare crash bug that could occur when the user forced
10235 a nameserver reconfiguration during the middle of a nameserver
10236 probe. Fixes bug 526. Bugfix on 0.1.2.1-alpha.
10237 - Support changing value of ServerDNSRandomizeCase during SIGHUP.
10238 Bugfix on 0.2.1.7-alpha.
10239 - If we're using bridges and our network goes away, be more willing
10240 to forgive our bridges and try again when we get an application
10241 request. Bugfix on 0.2.0.x.
10244 - Support platforms where time_t is 64 bits long. (Congratulations,
10245 NetBSD!) Patch from Matthias Drochner.
10246 - Add a 'getinfo status/clients-seen' controller command, in case
10247 controllers want to hear clients_seen events but connect late.
10250 - Disable GCC's strict alias optimization by default, to avoid the
10251 likelihood of its introducing subtle bugs whenever our code violates
10252 the letter of C99's alias rules.
10255 Changes in version 0.2.0.33 - 2009-01-21
10256 Tor 0.2.0.33 fixes a variety of bugs that were making relays less
10257 useful to users. It also finally fixes a bug where a relay or client
10258 that's been off for many days would take a long time to bootstrap.
10260 This update also fixes an important security-related bug reported by
10261 Ilja van Sprundel. You should upgrade. (We'll send out more details
10262 about the bug once people have had some time to upgrade.)
10265 - Fix a heap-corruption bug that may be remotely triggerable on
10266 some platforms. Reported by Ilja van Sprundel.
10269 - When a stream at an exit relay is in state "resolving" or
10270 "connecting" and it receives an "end" relay cell, the exit relay
10271 would silently ignore the end cell and not close the stream. If
10272 the client never closes the circuit, then the exit relay never
10273 closes the TCP connection. Bug introduced in Tor 0.1.2.1-alpha;
10274 reported by "wood".
10275 - When sending CREATED cells back for a given circuit, use a 64-bit
10276 connection ID to find the right connection, rather than an addr:port
10277 combination. Now that we can have multiple OR connections between
10278 the same ORs, it is no longer possible to use addr:port to uniquely
10279 identify a connection.
10280 - Bridge relays that had DirPort set to 0 would stop fetching
10281 descriptors shortly after startup, and then briefly resume
10282 after a new bandwidth test and/or after publishing a new bridge
10283 descriptor. Bridge users that try to bootstrap from them would
10284 get a recent networkstatus but would get descriptors from up to
10285 18 hours earlier, meaning most of the descriptors were obsolete
10286 already. Reported by Tas; bugfix on 0.2.0.13-alpha.
10287 - Prevent bridge relays from serving their 'extrainfo' document
10288 to anybody who asks, now that extrainfo docs include potentially
10289 sensitive aggregated client geoip summaries. Bugfix on
10291 - If the cached networkstatus consensus is more than five days old,
10292 discard it rather than trying to use it. In theory it could be
10293 useful because it lists alternate directory mirrors, but in practice
10294 it just means we spend many minutes trying directory mirrors that
10295 are long gone from the network. Also discard router descriptors as
10296 we load them if they are more than five days old, since the onion
10297 key is probably wrong by now. Bugfix on 0.2.0.x. Fixes bug 887.
10300 - Do not mark smartlist_bsearch_idx() function as ATTR_PURE. This bug
10301 could make gcc generate non-functional binary search code. Bugfix
10303 - Build correctly on platforms without socklen_t.
10304 - Compile without warnings on solaris.
10305 - Avoid potential crash on internal error during signature collection.
10306 Fixes bug 864. Patch from rovv.
10307 - Correct handling of possible malformed authority signing key
10308 certificates with internal signature types. Fixes bug 880.
10309 Bugfix on 0.2.0.3-alpha.
10310 - Fix a hard-to-trigger resource leak when logging credential status.
10312 - When we can't initialize DNS because the network is down, do not
10313 automatically stop Tor from starting. Instead, we retry failed
10314 dns_init() every 10 minutes, and change the exit policy to reject
10315 *:* until one succeeds. Fixes bug 691.
10316 - Use 64 bits instead of 32 bits for connection identifiers used with
10317 the controller protocol, to greatly reduce risk of identifier reuse.
10318 - When we're choosing an exit node for a circuit, and we have
10319 no pending streams, choose a good general exit rather than one that
10320 supports "all the pending streams". Bugfix on 0.1.1.x. Fix by rovv.
10321 - Fix another case of assuming, when a specific exit is requested,
10322 that we know more than the user about what hosts it allows.
10323 Fixes one case of bug 752. Patch from rovv.
10324 - Clip the MaxCircuitDirtiness config option to a minimum of 10
10325 seconds. Warn the user if lower values are given in the
10326 configuration. Bugfix on 0.1.0.1-rc. Patch by Sebastian.
10327 - Clip the CircuitBuildTimeout to a minimum of 30 seconds. Warn the
10328 user if lower values are given in the configuration. Bugfix on
10329 0.1.1.17-rc. Patch by Sebastian.
10330 - Fix a memory leak when we decline to add a v2 rendezvous descriptor to
10331 the cache because we already had a v0 descriptor with the same ID.
10332 Bugfix on 0.2.0.18-alpha.
10333 - Fix a race condition when freeing keys shared between main thread
10334 and CPU workers that could result in a memory leak. Bugfix on
10335 0.1.0.1-rc. Fixes bug 889.
10336 - Send a valid END cell back when a client tries to connect to a
10337 nonexistent hidden service port. Bugfix on 0.1.2.15. Fixes bug
10338 840. Patch from rovv.
10339 - Check which hops rendezvous stream cells are associated with to
10340 prevent possible guess-the-streamid injection attacks from
10341 intermediate hops. Fixes another case of bug 446. Based on patch
10343 - If a broken client asks a non-exit router to connect somewhere,
10344 do not even do the DNS lookup before rejecting the connection.
10345 Fixes another case of bug 619. Patch from rovv.
10346 - When a relay gets a create cell it can't decrypt (e.g. because it's
10347 using the wrong onion key), we were dropping it and letting the
10348 client time out. Now actually answer with a destroy cell. Fixes
10349 bug 904. Bugfix on 0.0.2pre8.
10351 o Minor bugfixes (hidden services):
10352 - Do not throw away existing introduction points on SIGHUP. Bugfix on
10353 0.0.6pre1. Patch by Karsten. Fixes bug 874.
10356 - Report the case where all signatures in a detached set are rejected
10357 differently than the case where there is an error handling the
10359 - When we realize that another process has modified our cached
10360 descriptors, print out a more useful error message rather than
10361 triggering an assertion. Fixes bug 885. Patch from Karsten.
10362 - Implement the 0x20 hack to better resist DNS poisoning: set the
10363 case on outgoing DNS requests randomly, and reject responses that do
10364 not match the case correctly. This logic can be disabled with the
10365 ServerDNSRamdomizeCase setting, if you are using one of the 0.3%
10366 of servers that do not reliably preserve case in replies. See
10367 "Increased DNS Forgery Resistance through 0x20-Bit Encoding"
10369 - Check DNS replies for more matching fields to better resist DNS
10371 - Never use OpenSSL compression: it wastes RAM and CPU trying to
10372 compress cells, which are basically all encrypted, compressed, or
10376 Changes in version 0.2.1.11-alpha - 2009-01-20
10377 Tor 0.2.1.11-alpha finishes fixing the "if your Tor is off for a
10378 week it will take a long time to bootstrap again" bug. It also fixes
10379 an important security-related bug reported by Ilja van Sprundel. You
10380 should upgrade. (We'll send out more details about the bug once people
10381 have had some time to upgrade.)
10384 - Fix a heap-corruption bug that may be remotely triggerable on
10385 some platforms. Reported by Ilja van Sprundel.
10388 - Discard router descriptors as we load them if they are more than
10389 five days old. Otherwise if Tor is off for a long time and then
10390 starts with cached descriptors, it will try to use the onion
10391 keys in those obsolete descriptors when building circuits. Bugfix
10392 on 0.2.0.x. Fixes bug 887.
10395 - Try to make sure that the version of Libevent we're running with
10396 is binary-compatible with the one we built with. May address bug
10398 - Make setting ServerDNSRandomizeCase to 0 actually work. Bugfix
10399 for bug 905. Bugfix on 0.2.1.7-alpha.
10400 - Add a new --enable-local-appdata configuration switch to change
10401 the default location of the datadir on win32 from APPDATA to
10402 LOCAL_APPDATA. In the future, we should migrate to LOCAL_APPDATA
10403 entirely. Patch from coderman.
10406 - Make outbound DNS packets respect the OutboundBindAddress setting.
10407 Fixes the bug part of bug 798. Bugfix on 0.1.2.2-alpha.
10408 - When our circuit fails at the first hop (e.g. we get a destroy
10409 cell back), avoid using that OR connection anymore, and also
10410 tell all the one-hop directory requests waiting for it that they
10411 should fail. Bugfix on 0.2.1.3-alpha.
10412 - In the torify(1) manpage, mention that tsocks will leak your
10416 Changes in version 0.2.1.10-alpha - 2009-01-06
10417 Tor 0.2.1.10-alpha fixes two major bugs in bridge relays (one that
10418 would make the bridge relay not so useful if it had DirPort set to 0,
10419 and one that could let an attacker learn a little bit of information
10420 about the bridge's users), and a bug that would cause your Tor relay
10421 to ignore a circuit create request it can't decrypt (rather than reply
10422 with an error). It also fixes a wide variety of other bugs.
10425 - If the cached networkstatus consensus is more than five days old,
10426 discard it rather than trying to use it. In theory it could
10427 be useful because it lists alternate directory mirrors, but in
10428 practice it just means we spend many minutes trying directory
10429 mirrors that are long gone from the network. Helps bug 887 a bit;
10431 - Bridge relays that had DirPort set to 0 would stop fetching
10432 descriptors shortly after startup, and then briefly resume
10433 after a new bandwidth test and/or after publishing a new bridge
10434 descriptor. Bridge users that try to bootstrap from them would
10435 get a recent networkstatus but would get descriptors from up to
10436 18 hours earlier, meaning most of the descriptors were obsolete
10437 already. Reported by Tas; bugfix on 0.2.0.13-alpha.
10438 - Prevent bridge relays from serving their 'extrainfo' document
10439 to anybody who asks, now that extrainfo docs include potentially
10440 sensitive aggregated client geoip summaries. Bugfix on
10444 - New controller event "clients_seen" to report a geoip-based summary
10445 of which countries we've seen clients from recently. Now controllers
10446 like Vidalia can show bridge operators that they're actually making
10448 - Build correctly against versions of OpenSSL 0.9.8 or later built
10449 without support for deprecated functions.
10450 - Update to the "December 19 2008" ip-to-country file.
10452 o Minor bugfixes (on 0.2.0.x):
10453 - Authorities now vote for the Stable flag for any router whose
10454 weighted MTBF is at least 5 days, regardless of the mean MTBF.
10455 - Do not remove routers as too old if we do not have any consensus
10456 document. Bugfix on 0.2.0.7-alpha.
10457 - Do not accept incomplete ipv4 addresses (like 192.168.0) as valid.
10458 Spec conformance issue. Bugfix on Tor 0.0.2pre27.
10459 - When an exit relay resolves a stream address to a local IP address,
10460 do not just keep retrying that same exit relay over and
10461 over. Instead, just close the stream. Addresses bug 872. Bugfix
10462 on 0.2.0.32. Patch from rovv.
10463 - If a hidden service sends us an END cell, do not consider
10464 retrying the connection; just close it. Patch from rovv.
10465 - When we made bridge authorities stop serving bridge descriptors over
10466 unencrypted links, we also broke DirPort reachability testing for
10467 bridges. So bridges with a non-zero DirPort were printing spurious
10468 warns to their logs. Bugfix on 0.2.0.16-alpha. Fixes bug 709.
10469 - When a relay gets a create cell it can't decrypt (e.g. because it's
10470 using the wrong onion key), we were dropping it and letting the
10471 client time out. Now actually answer with a destroy cell. Fixes
10472 bug 904. Bugfix on 0.0.2pre8.
10473 - Squeeze 2-5% out of client performance (according to oprofile) by
10474 improving the implementation of some policy-manipulation functions.
10476 o Minor bugfixes (on 0.2.1.x):
10477 - Make get_interface_address() function work properly again; stop
10478 guessing the wrong parts of our address as our address.
10479 - Do not cannibalize a circuit if we're out of RELAY_EARLY cells to
10480 send on that circuit. Otherwise we might violate the proposal-110
10481 limit. Bugfix on 0.2.1.3-alpha. Partial fix for bug 878. Diagnosis
10483 - When we're sending non-EXTEND cells to the first hop in a circuit,
10484 for example to use an encrypted directory connection, we don't need
10485 to use RELAY_EARLY cells: the first hop knows what kind of cell
10486 it is, and nobody else can even see the cell type. Conserving
10487 RELAY_EARLY cells makes it easier to cannibalize circuits like
10489 - Stop logging nameserver addresses in reverse order.
10490 - If we are retrying a directory download slowly over and over, do
10491 not automatically give up after the 254th failure. Bugfix on
10493 - Resume reporting accurate "stream end" reasons to the local control
10494 port. They were lost in the changes for Proposal 148. Bugfix on
10497 o Deprecated and removed features:
10498 - The old "tor --version --version" command, which would print out
10499 the subversion "Id" of most of the source files, is now removed. It
10500 turned out to be less useful than we'd expected, and harder to
10503 o Code simplifications and refactoring:
10504 - Change our header file guard macros to be less likely to conflict
10505 with system headers. Adam Langley noticed that we were conflicting
10506 with log.h on Android.
10507 - Tool-assisted documentation cleanup. Nearly every function or
10508 static variable in Tor should have its own documentation now.
10511 Changes in version 0.2.1.9-alpha - 2008-12-25
10512 Tor 0.2.1.9-alpha fixes many more bugs, some of them security-related.
10514 o New directory authorities:
10515 - gabelmoo (the authority run by Karsten Loesing) now has a new
10519 - Never use a connection with a mismatched address to extend a
10520 circuit, unless that connection is canonical. A canonical
10521 connection is one whose address is authenticated by the router's
10522 identity key, either in a NETINFO cell or in a router descriptor.
10523 - Avoid a possible memory corruption bug when receiving hidden service
10524 descriptors. Bugfix on 0.2.1.6-alpha.
10527 - Fix a logic error that would automatically reject all but the first
10528 configured DNS server. Bugfix on 0.2.1.5-alpha. Possible fix for
10529 part of bug 813/868. Bug spotted by coderman.
10530 - When a stream at an exit relay is in state "resolving" or
10531 "connecting" and it receives an "end" relay cell, the exit relay
10532 would silently ignore the end cell and not close the stream. If
10533 the client never closes the circuit, then the exit relay never
10534 closes the TCP connection. Bug introduced in 0.1.2.1-alpha;
10535 reported by "wood".
10536 - When we can't initialize DNS because the network is down, do not
10537 automatically stop Tor from starting. Instead, retry failed
10538 dns_init() every 10 minutes, and change the exit policy to reject
10539 *:* until one succeeds. Fixes bug 691.
10542 - Give a better error message when an overzealous init script says
10543 "sudo -u username tor --user username". Makes Bug 882 easier for
10545 - When a directory authority gives us a new guess for our IP address,
10546 log which authority we used. Hopefully this will help us debug
10547 the recent complaints about bad IP address guesses.
10548 - Detect svn revision properly when we're using git-svn.
10549 - Try not to open more than one descriptor-downloading connection
10550 to an authority at once. This should reduce load on directory
10551 authorities. Fixes bug 366.
10552 - Add cross-certification to newly generated certificates, so that
10553 a signing key is enough information to look up a certificate.
10554 Partial implementation of proposal 157.
10555 - Start serving certificates by <identity digest, signing key digest>
10556 pairs. Partial implementation of proposal 157.
10557 - Clients now never report any stream end reason except 'MISC'.
10558 Implements proposal 148.
10559 - On platforms with a maximum syslog string length, truncate syslog
10560 messages to that length ourselves, rather than relying on the
10561 system to do it for us.
10562 - Optimize out calls to time(NULL) that occur for every IO operation,
10563 or for every cell. On systems where time() is a slow syscall,
10564 this fix will be slightly helpful.
10565 - Exit servers can now answer resolve requests for ip6.arpa addresses.
10566 - When we download a descriptor that we then immediately (as
10567 a directory authority) reject, do not retry downloading it right
10568 away. Should save some bandwidth on authorities. Fix for bug
10569 888. Patch by Sebastian Hahn.
10570 - When a download gets us zero good descriptors, do not notify
10571 Tor that new directory information has arrived.
10572 - Avoid some nasty corner cases in the logic for marking connections
10573 as too old or obsolete or noncanonical for circuits. Partial
10576 o Minor features (controller):
10577 - New CONSENSUS_ARRIVED event to note when a new consensus has
10578 been fetched and validated.
10579 - When we realize that another process has modified our cached
10580 descriptors file, print out a more useful error message rather
10581 than triggering an assertion. Fixes bug 885. Patch from Karsten.
10582 - Add an internal-use-only __ReloadTorrcOnSIGHUP option for
10583 controllers to prevent SIGHUP from reloading the
10584 configuration. Fixes bug 856.
10587 - Resume using the correct "REASON=" stream when telling the
10588 controller why we closed a stream. Bugfix in 0.2.1.1-alpha.
10589 - When a canonical connection appears later in our internal list
10590 than a noncanonical one for a given OR ID, always use the
10591 canonical one. Bugfix on 0.2.0.12-alpha. Fixes bug 805.
10593 - Clip the MaxCircuitDirtiness config option to a minimum of 10
10594 seconds. Warn the user if lower values are given in the
10595 configuration. Bugfix on 0.1.0.1-rc. Patch by Sebastian.
10596 - Clip the CircuitBuildTimeout to a minimum of 30 seconds. Warn the
10597 user if lower values are given in the configuration. Bugfix on
10598 0.1.1.17-rc. Patch by Sebastian.
10599 - Fix a race condition when freeing keys shared between main thread
10600 and CPU workers that could result in a memory leak. Bugfix on
10601 0.1.0.1-rc. Fixes bug 889.
10603 o Minor bugfixes (hidden services):
10604 - Do not throw away existing introduction points on SIGHUP (bugfix on
10605 0.0.6pre1); also, do not stall hidden services because we're
10606 throwing away introduction points; bugfix on 0.2.1.7-alpha. Spotted
10607 by John Brooks. Patch by Karsten. Fixes bug 874.
10608 - Fix a memory leak when we decline to add a v2 rendezvous
10609 descriptor to the cache because we already had a v0 descriptor
10610 with the same ID. Bugfix on 0.2.0.18-alpha.
10612 o Deprecated and removed features:
10613 - RedirectExits has been removed. It was deprecated since
10615 - Finally remove deprecated "EXTENDED_FORMAT" controller feature. It
10616 has been called EXTENDED_EVENTS since 0.1.2.4-alpha.
10617 - Cell pools are now always enabled; --disable-cell-pools is ignored.
10619 o Code simplifications and refactoring:
10620 - Rename the confusing or_is_obsolete field to the more appropriate
10621 is_bad_for_new_circs, and move it to or_connection_t where it
10623 - Move edge-only flags from connection_t to edge_connection_t: not
10624 only is this better coding, but on machines of plausible alignment,
10625 it should save 4-8 bytes per connection_t. "Every little bit helps."
10626 - Rename ServerDNSAllowBrokenResolvConf to ServerDNSAllowBrokenConfig
10627 for consistency; keep old option working for backward compatibility.
10628 - Simplify the code for finding connections to use for a circuit.
10631 Changes in version 0.2.1.8-alpha - 2008-12-08
10632 Tor 0.2.1.8-alpha fixes some crash bugs in earlier alpha releases,
10633 builds better on unusual platforms like Solaris and old OS X, and
10634 fixes a variety of other issues.
10637 - New DirPortFrontPage option that takes an html file and publishes
10638 it as "/" on the DirPort. Now relay operators can provide a
10639 disclaimer without needing to set up a separate webserver. There's
10640 a sample disclaimer in contrib/tor-exit-notice.html.
10643 - When the client is choosing entry guards, now it selects at most
10644 one guard from a given relay family. Otherwise we could end up with
10645 all of our entry points into the network run by the same operator.
10646 Suggested by Camilo Viecco. Fix on 0.1.1.11-alpha.
10649 - Fix a DOS opportunity during the voting signature collection process
10650 at directory authorities. Spotted by rovv. Bugfix on 0.2.0.x.
10651 - Fix a possible segfault when establishing an exit connection. Bugfix
10655 - Get file locking working on win32. Bugfix on 0.2.1.6-alpha. Fixes
10657 - Made Tor a little less aggressive about deleting expired
10658 certificates. Partial fix for bug 854.
10659 - Stop doing unaligned memory access that generated bus errors on
10660 sparc64. Bugfix on 0.2.0.10-alpha. Fix for bug 862.
10661 - Fix a crash bug when changing EntryNodes from the controller. Bugfix
10662 on 0.2.1.6-alpha. Fix for bug 867. Patched by Sebastian.
10663 - Make USR2 log-level switch take effect immediately. Bugfix on
10665 - If one win32 nameserver fails to get added, continue adding the
10666 rest, and don't automatically fail.
10667 - Use fcntl() for locking when flock() is not available. Should fix
10668 compilation on Solaris. Should fix Bug 873. Bugfix on 0.2.1.6-alpha.
10669 - Do not mark smartlist_bsearch_idx() function as ATTR_PURE. This bug
10670 could make gcc generate non-functional binary search code. Bugfix
10672 - Build correctly on platforms without socklen_t.
10673 - Avoid potential crash on internal error during signature collection.
10674 Fixes bug 864. Patch from rovv.
10675 - Do not use C's stdio library for writing to log files. This will
10676 improve logging performance by a minute amount, and will stop
10677 leaking fds when our disk is full. Fixes bug 861.
10678 - Stop erroneous use of O_APPEND in cases where we did not in fact
10679 want to re-seek to the end of a file before every last write().
10680 - Correct handling of possible malformed authority signing key
10681 certificates with internal signature types. Fixes bug 880. Bugfix
10683 - Fix a hard-to-trigger resource leak when logging credential status.
10687 - Directory mirrors no longer fetch the v1 directory or
10688 running-routers files. They are obsolete, and nobody asks for them
10689 anymore. This is the first step to making v1 authorities obsolete.
10691 o Minor features (controller):
10692 - Return circuit purposes in response to GETINFO circuit-status. Fixes
10696 Changes in version 0.2.0.32 - 2008-11-20
10697 Tor 0.2.0.32 fixes a major security problem in Debian and Ubuntu
10698 packages (and maybe other packages) noticed by Theo de Raadt, fixes
10699 a smaller security flaw that might allow an attacker to access local
10700 services, further improves hidden service performance, and fixes a
10701 variety of other issues.
10704 - The "User" and "Group" config options did not clear the
10705 supplementary group entries for the Tor process. The "User" option
10706 is now more robust, and we now set the groups to the specified
10707 user's primary group. The "Group" option is now ignored. For more
10708 detailed logging on credential switching, set CREDENTIAL_LOG_LEVEL
10709 in common/compat.c to LOG_NOTICE or higher. Patch by Jacob Appelbaum
10710 and Steven Murdoch. Bugfix on 0.0.2pre14. Fixes bug 848 and 857.
10711 - The "ClientDNSRejectInternalAddresses" config option wasn't being
10712 consistently obeyed: if an exit relay refuses a stream because its
10713 exit policy doesn't allow it, we would remember what IP address
10714 the relay said the destination address resolves to, even if it's
10715 an internal IP address. Bugfix on 0.2.0.7-alpha; patch by rovv.
10718 - Fix a DOS opportunity during the voting signature collection process
10719 at directory authorities. Spotted by rovv. Bugfix on 0.2.0.x.
10721 o Major bugfixes (hidden services):
10722 - When fetching v0 and v2 rendezvous service descriptors in parallel,
10723 we were failing the whole hidden service request when the v0
10724 descriptor fetch fails, even if the v2 fetch is still pending and
10725 might succeed. Similarly, if the last v2 fetch fails, we were
10726 failing the whole hidden service request even if a v0 fetch is
10727 still pending. Fixes bug 814. Bugfix on 0.2.0.10-alpha.
10728 - When extending a circuit to a hidden service directory to upload a
10729 rendezvous descriptor using a BEGIN_DIR cell, almost 1/6 of all
10730 requests failed, because the router descriptor has not been
10731 downloaded yet. In these cases, do not attempt to upload the
10732 rendezvous descriptor, but wait until the router descriptor is
10733 downloaded and retry. Likewise, do not attempt to fetch a rendezvous
10734 descriptor from a hidden service directory for which the router
10735 descriptor has not yet been downloaded. Fixes bug 767. Bugfix
10739 - Fix several infrequent memory leaks spotted by Coverity.
10740 - When testing for libevent functions, set the LDFLAGS variable
10741 correctly. Found by Riastradh.
10742 - Avoid a bug where the FastFirstHopPK 0 option would keep Tor from
10743 bootstrapping with tunneled directory connections. Bugfix on
10744 0.1.2.5-alpha. Fixes bug 797. Found by Erwin Lam.
10745 - When asked to connect to A.B.exit:80, if we don't know the IP for A
10746 and we know that server B rejects most-but-not all connections to
10747 port 80, we would previously reject the connection. Now, we assume
10748 the user knows what they were asking for. Fixes bug 752. Bugfix
10749 on 0.0.9rc5. Diagnosed by BarkerJr.
10750 - If we overrun our per-second write limits a little, count this as
10751 having used up our write allocation for the second, and choke
10752 outgoing directory writes. Previously, we had only counted this when
10753 we had met our limits precisely. Fixes bug 824. Patch from by rovv.
10754 Bugfix on 0.2.0.x (??).
10755 - Remove the old v2 directory authority 'lefkada' from the default
10756 list. It has been gone for many months.
10757 - Stop doing unaligned memory access that generated bus errors on
10758 sparc64. Bugfix on 0.2.0.10-alpha. Fixes bug 862.
10759 - Make USR2 log-level switch take effect immediately. Bugfix on
10762 o Minor bugfixes (controller):
10763 - Make DNS resolved events into "CLOSED", not "FAILED". Bugfix on
10764 0.1.2.5-alpha. Fix by Robert Hogan. Resolves bug 807.
10767 Changes in version 0.2.1.7-alpha - 2008-11-08
10768 Tor 0.2.1.7-alpha fixes a major security problem in Debian and Ubuntu
10769 packages (and maybe other packages) noticed by Theo de Raadt, fixes
10770 a smaller security flaw that might allow an attacker to access local
10771 services, adds better defense against DNS poisoning attacks on exit
10772 relays, further improves hidden service performance, and fixes a
10773 variety of other issues.
10776 - The "ClientDNSRejectInternalAddresses" config option wasn't being
10777 consistently obeyed: if an exit relay refuses a stream because its
10778 exit policy doesn't allow it, we would remember what IP address
10779 the relay said the destination address resolves to, even if it's
10780 an internal IP address. Bugfix on 0.2.0.7-alpha; patch by rovv.
10781 - The "User" and "Group" config options did not clear the
10782 supplementary group entries for the Tor process. The "User" option
10783 is now more robust, and we now set the groups to the specified
10784 user's primary group. The "Group" option is now ignored. For more
10785 detailed logging on credential switching, set CREDENTIAL_LOG_LEVEL
10786 in common/compat.c to LOG_NOTICE or higher. Patch by Jacob Appelbaum
10787 and Steven Murdoch. Bugfix on 0.0.2pre14. Fixes bug 848.
10788 - Do not use or believe expired v3 authority certificates. Patch
10789 from Karsten. Bugfix in 0.2.0.x. Fixes bug 851.
10792 - Now NodeFamily and MyFamily config options allow spaces in
10793 identity fingerprints, so it's easier to paste them in.
10794 Suggested by Lucky Green.
10795 - Implement the 0x20 hack to better resist DNS poisoning: set the
10796 case on outgoing DNS requests randomly, and reject responses that do
10797 not match the case correctly. This logic can be disabled with the
10798 ServerDNSRandomizeCase setting, if you are using one of the 0.3%
10799 of servers that do not reliably preserve case in replies. See
10800 "Increased DNS Forgery Resistance through 0x20-Bit Encoding"
10802 - Preserve case in replies to DNSPort requests in order to support
10803 the 0x20 hack for resisting DNS poisoning attacks.
10805 o Hidden service performance improvements:
10806 - When the client launches an introduction circuit, retry with a
10807 new circuit after 30 seconds rather than 60 seconds.
10808 - Launch a second client-side introduction circuit in parallel
10809 after a delay of 15 seconds (based on work by Christian Wilms).
10810 - Hidden services start out building five intro circuits rather
10811 than three, and when the first three finish they publish a service
10812 descriptor using those. Now we publish our service descriptor much
10813 faster after restart.
10816 - Minor fix in the warning messages when you're having problems
10817 bootstrapping; also, be more forgiving of bootstrap problems when
10818 we're still making incremental progress on a given bootstrap phase.
10819 - When we're choosing an exit node for a circuit, and we have
10820 no pending streams, choose a good general exit rather than one that
10821 supports "all the pending streams". Bugfix on 0.1.1.x. Fix by rovv.
10822 - Send a valid END cell back when a client tries to connect to a
10823 nonexistent hidden service port. Bugfix on 0.1.2.15. Fixes bug
10824 840. Patch from rovv.
10825 - If a broken client asks a non-exit router to connect somewhere,
10826 do not even do the DNS lookup before rejecting the connection.
10827 Fixes another case of bug 619. Patch from rovv.
10828 - Fix another case of assuming, when a specific exit is requested,
10829 that we know more than the user about what hosts it allows.
10830 Fixes another case of bug 752. Patch from rovv.
10831 - Check which hops rendezvous stream cells are associated with to
10832 prevent possible guess-the-streamid injection attacks from
10833 intermediate hops. Fixes another case of bug 446. Based on patch
10835 - Avoid using a negative right-shift when comparing 32-bit
10836 addresses. Possible fix for bug 845 and bug 811.
10837 - Make the assert_circuit_ok() function work correctly on circuits that
10838 have already been marked for close.
10839 - Fix read-off-the-end-of-string error in unit tests when decoding
10840 introduction points.
10841 - Fix uninitialized size field for memory area allocation: may improve
10842 memory performance during directory parsing.
10843 - Treat duplicate certificate fetches as failures, so that we do
10844 not try to re-fetch an expired certificate over and over and over.
10845 - Do not say we're fetching a certificate when we'll in fact skip it
10846 because of a pending download.
10849 Changes in version 0.2.1.6-alpha - 2008-09-30
10850 Tor 0.2.1.6-alpha further improves performance and robustness of
10851 hidden services, starts work on supporting per-country relay selection,
10852 and fixes a variety of smaller issues.
10855 - Implement proposal 121: make it possible to build hidden services
10856 that only certain clients are allowed to connect to. This is
10857 enforced at several points, so that unauthorized clients are unable
10858 to send INTRODUCE cells to the service, or even (depending on the
10859 type of authentication) to learn introduction points. This feature
10860 raises the bar for certain kinds of active attacks against hidden
10861 services. Code by Karsten Loesing.
10862 - Relays now store and serve v2 hidden service descriptors by default,
10863 i.e., the new default value for HidServDirectoryV2 is 1. This is
10864 the last step in proposal 114, which aims to make hidden service
10865 lookups more reliable.
10866 - Start work to allow node restrictions to include country codes. The
10867 syntax to exclude nodes in a country with country code XX is
10868 "ExcludeNodes {XX}". Patch from Robert Hogan. It still needs some
10869 refinement to decide what config options should take priority if
10870 you ask to both use a particular node and exclude it.
10871 - Allow ExitNodes list to include IP ranges and country codes, just
10872 like the Exclude*Nodes lists. Patch from Robert Hogan.
10875 - Fix a bug when parsing ports in tor_addr_port_parse() that caused
10876 Tor to fail to start if you had it configured to use a bridge
10877 relay. Fixes bug 809. Bugfix on 0.2.1.5-alpha.
10878 - When extending a circuit to a hidden service directory to upload a
10879 rendezvous descriptor using a BEGIN_DIR cell, almost 1/6 of all
10880 requests failed, because the router descriptor had not been
10881 downloaded yet. In these cases, we now wait until the router
10882 descriptor is downloaded, and then retry. Likewise, clients
10883 now skip over a hidden service directory if they don't yet have
10884 its router descriptor, rather than futilely requesting it and
10885 putting mysterious complaints in the logs. Fixes bug 767. Bugfix
10887 - When fetching v0 and v2 rendezvous service descriptors in parallel,
10888 we were failing the whole hidden service request when the v0
10889 descriptor fetch fails, even if the v2 fetch is still pending and
10890 might succeed. Similarly, if the last v2 fetch fails, we were
10891 failing the whole hidden service request even if a v0 fetch is
10892 still pending. Fixes bug 814. Bugfix on 0.2.0.10-alpha.
10893 - DNS replies need to have names matching their requests, but
10894 these names should be in the questions section, not necessarily
10895 in the answers section. Fixes bug 823. Bugfix on 0.2.1.5-alpha.
10898 - Update to the "September 1 2008" ip-to-country file.
10899 - Allow ports 465 and 587 in the default exit policy again. We had
10900 rejected them in 0.1.0.15, because back in 2005 they were commonly
10901 misconfigured and ended up as spam targets. We hear they are better
10902 locked down these days.
10903 - Use a lockfile to make sure that two Tor processes are not
10904 simultaneously running with the same datadir.
10905 - Serve the latest v3 networkstatus consensus via the control
10906 port. Use "getinfo dir/status-vote/current/consensus" to fetch it.
10907 - Better logging about stability/reliability calculations on directory
10909 - Drop the requirement to have an open dir port for storing and
10910 serving v2 hidden service descriptors.
10911 - Directory authorities now serve a /tor/dbg-stability.txt URL to
10912 help debug WFU and MTBF calculations.
10913 - Implement most of Proposal 152: allow specialized servers to permit
10914 single-hop circuits, and clients to use those servers to build
10915 single-hop circuits when using a specialized controller. Patch
10916 from Josh Albrecht. Resolves feature request 768.
10917 - Add a -p option to tor-resolve for specifying the SOCKS port: some
10918 people find host:port too confusing.
10919 - Make TrackHostExit mappings expire a while after their last use, not
10920 after their creation. Patch from Robert Hogan.
10921 - Provide circuit purposes along with circuit events to the controller.
10924 - Fix compile on OpenBSD 4.4-current. Bugfix on 0.2.1.5-alpha.
10926 - Fixed some memory leaks -- some quite frequent, some almost
10927 impossible to trigger -- based on results from Coverity.
10928 - When testing for libevent functions, set the LDFLAGS variable
10929 correctly. Found by Riastradh.
10930 - Fix an assertion bug in parsing policy-related options; possible fix
10932 - Catch and report a few more bootstrapping failure cases when Tor
10933 fails to establish a TCP connection. Cleanup on 0.2.1.x.
10934 - Avoid a bug where the FastFirstHopPK 0 option would keep Tor from
10935 bootstrapping with tunneled directory connections. Bugfix on
10936 0.1.2.5-alpha. Fixes bug 797. Found by Erwin Lam.
10937 - When asked to connect to A.B.exit:80, if we don't know the IP for A
10938 and we know that server B rejects most-but-not all connections to
10939 port 80, we would previously reject the connection. Now, we assume
10940 the user knows what they were asking for. Fixes bug 752. Bugfix
10941 on 0.0.9rc5. Diagnosed by BarkerJr.
10942 - If we are not using BEGIN_DIR cells, don't attempt to contact hidden
10943 service directories if they have no advertised dir port. Bugfix
10945 - If we overrun our per-second write limits a little, count this as
10946 having used up our write allocation for the second, and choke
10947 outgoing directory writes. Previously, we had only counted this when
10948 we had met our limits precisely. Fixes bug 824. Patch by rovv.
10949 Bugfix on 0.2.0.x (??).
10950 - Avoid a "0 divided by 0" calculation when calculating router uptime
10951 at directory authorities. Bugfix on 0.2.0.8-alpha.
10952 - Make DNS resolved controller events into "CLOSED", not
10953 "FAILED". Bugfix on 0.1.2.5-alpha. Fix by Robert Hogan. Resolves
10955 - Fix a bug where an unreachable relay would establish enough
10956 reachability testing circuits to do a bandwidth test -- if
10957 we already have a connection to the middle hop of the testing
10958 circuit, then it could establish the last hop by using the existing
10959 connection. Bugfix on 0.1.2.2-alpha, exposed when we made testing
10960 circuits no longer use entry guards in 0.2.1.3-alpha.
10961 - If we have correct permissions on $datadir, we complain to stdout
10962 and fail to start. But dangerous permissions on
10963 $datadir/cached-status/ would cause us to open a log and complain
10964 there. Now complain to stdout and fail to start in both cases. Fixes
10965 bug 820, reported by seeess.
10966 - Remove the old v2 directory authority 'lefkada' from the default
10967 list. It has been gone for many months.
10969 o Code simplifications and refactoring:
10970 - Revise the connection_new functions so that a more typesafe variant
10971 exists. This will work better with Coverity, and let us find any
10972 actual mistakes we're making here.
10973 - Refactor unit testing logic so that dmalloc can be used sensibly
10974 with unit tests to check for memory leaks.
10975 - Move all hidden-service related fields from connection and circuit
10976 structure to substructures: this way they won't eat so much memory.
10979 Changes in version 0.2.0.31 - 2008-09-03
10980 Tor 0.2.0.31 addresses two potential anonymity issues, starts to fix
10981 a big bug we're seeing where in rare cases traffic from one Tor stream
10982 gets mixed into another stream, and fixes a variety of smaller issues.
10985 - Make sure that two circuits can never exist on the same connection
10986 with the same circuit ID, even if one is marked for close. This
10987 is conceivably a bugfix for bug 779. Bugfix on 0.1.0.4-rc.
10988 - Relays now reject risky extend cells: if the extend cell includes
10989 a digest of all zeroes, or asks to extend back to the relay that
10990 sent the extend cell, tear down the circuit. Ideas suggested
10992 - If not enough of our entry guards are available so we add a new
10993 one, we might use the new one even if it overlapped with the
10994 current circuit's exit relay (or its family). Anonymity bugfix
10995 pointed out by rovv.
10998 - Recover 3-7 bytes that were wasted per memory chunk. Fixes bug
10999 794; bug spotted by rovv. Bugfix on 0.2.0.1-alpha.
11000 - Correctly detect the presence of the linux/netfilter_ipv4.h header
11001 when building against recent kernels. Bugfix on 0.1.2.1-alpha.
11002 - Pick size of default geoip filename string correctly on windows.
11003 Fixes bug 806. Bugfix on 0.2.0.30.
11004 - Make the autoconf script accept the obsolete --with-ssl-dir
11005 option as an alias for the actually-working --with-openssl-dir
11006 option. Fix the help documentation to recommend --with-openssl-dir.
11007 Based on a patch by "Dave". Bugfix on 0.2.0.1-alpha.
11008 - When using the TransPort option on OpenBSD, and using the User
11009 option to change UID and drop privileges, make sure to open
11010 /dev/pf before dropping privileges. Fixes bug 782. Patch from
11011 Christopher Davis. Bugfix on 0.1.2.1-alpha.
11012 - Try to attach connections immediately upon receiving a RENDEZVOUS2
11013 or RENDEZVOUS_ESTABLISHED cell. This can save a second or two
11014 on the client side when connecting to a hidden service. Bugfix
11015 on 0.0.6pre1. Found and fixed by Christian Wilms; resolves bug 743.
11016 - When closing an application-side connection because its circuit is
11017 getting torn down, generate the stream event correctly. Bugfix on
11018 0.1.2.x. Anonymous patch.
11021 Changes in version 0.2.1.5-alpha - 2008-08-31
11022 Tor 0.2.1.5-alpha moves us closer to handling IPv6 destinations, puts
11023 in a lot of the infrastructure for adding authorization to hidden
11024 services, lays the groundwork for having clients read their load
11025 balancing information out of the networkstatus consensus rather than
11026 the individual router descriptors, addresses two potential anonymity
11027 issues, and fixes a variety of smaller issues.
11030 - Convert many internal address representations to optionally hold
11032 - Generate and accept IPv6 addresses in many protocol elements.
11033 - Make resolver code handle nameservers located at ipv6 addresses.
11034 - Begin implementation of proposal 121 ("Client authorization for
11035 hidden services"): configure hidden services with client
11036 authorization, publish descriptors for them, and configure
11037 authorization data for hidden services at clients. The next
11038 step is to actually access hidden services that perform client
11040 - More progress toward proposal 141: Network status consensus
11041 documents and votes now contain bandwidth information for each
11042 router and a summary of that router's exit policy. Eventually this
11043 will be used by clients so that they do not have to download every
11044 known descriptor before building circuits.
11046 o Major bugfixes (on 0.2.0.x and before):
11047 - When sending CREATED cells back for a given circuit, use a 64-bit
11048 connection ID to find the right connection, rather than an addr:port
11049 combination. Now that we can have multiple OR connections between
11050 the same ORs, it is no longer possible to use addr:port to uniquely
11051 identify a connection.
11052 - Relays now reject risky extend cells: if the extend cell includes
11053 a digest of all zeroes, or asks to extend back to the relay that
11054 sent the extend cell, tear down the circuit. Ideas suggested
11056 - If not enough of our entry guards are available so we add a new
11057 one, we might use the new one even if it overlapped with the
11058 current circuit's exit relay (or its family). Anonymity bugfix
11059 pointed out by rovv.
11062 - Recover 3-7 bytes that were wasted per memory chunk. Fixes bug
11063 794; bug spotted by rovv. Bugfix on 0.2.0.1-alpha.
11064 - When using the TransPort option on OpenBSD, and using the User
11065 option to change UID and drop privileges, make sure to open /dev/pf
11066 before dropping privileges. Fixes bug 782. Patch from Christopher
11067 Davis. Bugfix on 0.1.2.1-alpha.
11068 - Correctly detect the presence of the linux/netfilter_ipv4.h header
11069 when building against recent kernels. Bugfix on 0.1.2.1-alpha.
11070 - Add a missing safe_str() call for a debug log message.
11071 - Use 64 bits instead of 32 bits for connection identifiers used with
11072 the controller protocol, to greatly reduce risk of identifier reuse.
11073 - Make the autoconf script accept the obsolete --with-ssl-dir
11074 option as an alias for the actually-working --with-openssl-dir
11075 option. Fix the help documentation to recommend --with-openssl-dir.
11076 Based on a patch by "Dave". Bugfix on 0.2.0.1-alpha.
11079 - Rate-limit too-many-sockets messages: when they happen, they happen
11080 a lot. Resolves bug 748.
11081 - Resist DNS poisoning a little better by making sure that names in
11082 answer sections match.
11083 - Print the SOCKS5 error message string as well as the error code
11084 when a tor-resolve request fails. Patch from Jacob.
11087 Changes in version 0.2.1.4-alpha - 2008-08-04
11088 Tor 0.2.1.4-alpha fixes a pair of crash bugs in 0.2.1.3-alpha.
11091 - The address part of exit policies was not correctly written
11092 to router descriptors. This generated router descriptors that failed
11093 their self-checks. Noticed by phobos, fixed by Karsten. Bugfix
11095 - Tor triggered a false assert when extending a circuit to a relay
11096 but we already have a connection open to that relay. Noticed by
11097 phobos, fixed by Karsten. Bugfix on 0.2.1.3-alpha.
11100 - Fix a hidden service logging bug: in some edge cases, the router
11101 descriptor of a previously picked introduction point becomes
11102 obsolete and we need to give up on it rather than continually
11103 complaining that it has become obsolete. Observed by xiando. Bugfix
11106 o Removed features:
11107 - Take out the TestVia config option, since it was a workaround for
11108 a bug that was fixed in Tor 0.1.1.21.
11111 Changes in version 0.2.1.3-alpha - 2008-08-03
11112 Tor 0.2.1.3-alpha implements most of the pieces to prevent
11113 infinite-length circuit attacks (see proposal 110); fixes a bug that
11114 might cause exit relays to corrupt streams they send back; allows
11115 address patterns (e.g. 255.128.0.0/16) to appear in ExcludeNodes and
11116 ExcludeExitNodes config options; and fixes a big pile of bugs.
11118 o Bootstrapping bugfixes (on 0.2.1.x-alpha):
11119 - Send a bootstrap problem "warn" event on the first problem if the
11120 reason is NO_ROUTE (that is, our network is down).
11123 - Implement most of proposal 110: The first K cells to be sent
11124 along a circuit are marked as special "early" cells; only K "early"
11125 cells will be allowed. Once this code is universal, we can block
11126 certain kinds of DOS attack by requiring that EXTEND commands must
11127 be sent using an "early" cell.
11130 - Try to attach connections immediately upon receiving a RENDEZVOUS2
11131 or RENDEZVOUS_ESTABLISHED cell. This can save a second or two
11132 on the client side when connecting to a hidden service. Bugfix
11133 on 0.0.6pre1. Found and fixed by Christian Wilms; resolves bug 743.
11134 - Ensure that two circuits can never exist on the same connection
11135 with the same circuit ID, even if one is marked for close. This
11136 is conceivably a bugfix for bug 779; fixes a bug on 0.1.0.4-rc.
11139 - When relays do their initial bandwidth measurement, don't limit
11140 to just our entry guards for the test circuits. Otherwise we tend
11141 to have multiple test circuits going through a single entry guard,
11142 which makes our bandwidth test less accurate. Fixes part of bug 654;
11143 patch contributed by Josh Albrecht.
11144 - Add an ExcludeExitNodes option so users can list a set of nodes
11145 that should be be excluded from the exit node position, but
11146 allowed elsewhere. Implements proposal 151.
11147 - Allow address patterns (e.g., 255.128.0.0/16) to appear in
11148 ExcludeNodes and ExcludeExitNodes lists.
11149 - Change the implementation of ExcludeNodes and ExcludeExitNodes to
11150 be more efficient. Formerly it was quadratic in the number of
11151 servers; now it should be linear. Fixes bug 509.
11152 - Save 16-22 bytes per open circuit by moving the n_addr, n_port,
11153 and n_conn_id_digest fields into a separate structure that's
11154 only needed when the circuit has not yet attached to an n_conn.
11157 - Change the contrib/tor.logrotate script so it makes the new
11158 logs as "_tor:_tor" rather than the default, which is generally
11159 "root:wheel". Fixes bug 676, reported by Serge Koksharov.
11160 - Stop using __attribute__((nonnull)) with GCC: it can give us useful
11161 warnings (occasionally), but it can also cause the compiler to
11162 eliminate error-checking code. Suggested by Peter Gutmann.
11163 - When a hidden service is giving up on an introduction point candidate
11164 that was not included in the last published rendezvous descriptor,
11165 don't reschedule publication of the next descriptor. Fixes bug 763.
11167 - Mark RendNodes, RendExcludeNodes, HiddenServiceNodes, and
11168 HiddenServiceExcludeNodes as obsolete: they never worked properly,
11169 and nobody claims to be using them. Fixes bug 754. Bugfix on
11170 0.1.0.1-rc. Patch from Christian Wilms.
11171 - Fix a small alignment and memory-wasting bug on buffer chunks.
11174 o Minor bugfixes (controller):
11175 - When closing an application-side connection because its circuit
11176 is getting torn down, generate the stream event correctly.
11177 Bugfix on 0.1.2.x. Anonymous patch.
11179 o Removed features:
11180 - Remove all backward-compatibility code to support relays running
11181 versions of Tor so old that they no longer work at all on the
11185 Changes in version 0.2.0.30 - 2008-07-15
11187 - Stop using __attribute__((nonnull)) with GCC: it can give us useful
11188 warnings (occasionally), but it can also cause the compiler to
11189 eliminate error-checking code. Suggested by Peter Gutmann.
11192 Changes in version 0.2.0.29-rc - 2008-07-08
11193 Tor 0.2.0.29-rc fixes two big bugs with using bridges, fixes more
11194 hidden-service performance bugs, and fixes a bunch of smaller bugs.
11197 - If you have more than one bridge but don't know their keys,
11198 you would only launch a request for the descriptor of the first one
11199 on your list. (Tor considered launching requests for the others, but
11200 found that it already had a connection on the way for $0000...0000
11201 so it didn't open another.) Bugfix on 0.2.0.x.
11202 - If you have more than one bridge but don't know their keys, and the
11203 connection to one of the bridges failed, you would cancel all
11204 pending bridge connections. (After all, they all have the same
11205 digest.) Bugfix on 0.2.0.x.
11206 - When a hidden service was trying to establish an introduction point,
11207 and Tor had built circuits preemptively for such purposes, we
11208 were ignoring all the preemptive circuits and launching a new one
11209 instead. Bugfix on 0.2.0.14-alpha.
11210 - When a hidden service was trying to establish an introduction point,
11211 and Tor *did* manage to reuse one of the preemptively built
11212 circuits, it didn't correctly remember which one it used,
11213 so it asked for another one soon after, until there were no
11214 more preemptive circuits, at which point it launched one from
11215 scratch. Bugfix on 0.0.9.x.
11216 - Make directory servers include the X-Your-Address-Is: http header in
11217 their responses even for begin_dir conns. Now clients who only
11218 ever use begin_dir connections still have a way to learn their IP
11219 address. Fixes bug 737; bugfix on 0.2.0.22-rc. Reported by goldy.
11222 - Fix a macro/CPP interaction that was confusing some compilers:
11223 some GCCs don't like #if/#endif pairs inside macro arguments.
11225 - Fix macro collision between OpenSSL 0.9.8h and Windows headers.
11226 Fixes bug 704; fix from Steven Murdoch.
11227 - When opening /dev/null in finish_daemonize(), do not pass the
11228 O_CREAT flag. Fortify was complaining, and correctly so. Fixes
11229 bug 742; fix from Michael Scherer. Bugfix on 0.0.2pre19.
11230 - Correctly detect transparent proxy support on Linux hosts that
11231 require in.h to be included before netfilter_ipv4.h. Patch
11233 - Disallow session resumption attempts during the renegotiation
11234 stage of the v2 handshake protocol. Clients should never be trying
11235 session resumption at this point, but apparently some did, in
11236 ways that caused the handshake to fail. Bugfix on 0.2.0.20-rc. Bug
11237 found by Geoff Goodell.
11240 Changes in version 0.2.1.2-alpha - 2008-06-20
11241 Tor 0.2.1.2-alpha includes a new "TestingTorNetwork" config option to
11242 make it easier to set up your own private Tor network; fixes several
11243 big bugs with using more than one bridge relay; fixes a big bug with
11244 offering hidden services quickly after Tor starts; and uses a better
11245 API for reporting potential bootstrapping problems to the controller.
11248 - New TestingTorNetwork config option to allow adjustment of
11249 previously constant values that, while reasonable, could slow
11250 bootstrapping. Implements proposal 135. Patch from Karsten.
11253 - If you have more than one bridge but don't know their digests,
11254 you would only learn a request for the descriptor of the first one
11255 on your list. (Tor considered launching requests for the others, but
11256 found that it already had a connection on the way for $0000...0000
11257 so it didn't open another.) Bugfix on 0.2.0.x.
11258 - If you have more than one bridge but don't know their digests,
11259 and the connection to one of the bridges failed, you would cancel
11260 all pending bridge connections. (After all, they all have the
11261 same digest.) Bugfix on 0.2.0.x.
11262 - When establishing a hidden service, introduction points that
11263 originate from cannibalized circuits are completely ignored and not
11264 included in rendezvous service descriptors. This might be another
11265 reason for delay in making a hidden service available. Bugfix
11266 from long ago (0.0.9.x?)
11269 - Allow OpenSSL to use dynamic locks if it wants.
11270 - When building a consensus, do not include routers that are down.
11271 This will cut down 30% to 40% on consensus size. Implements
11273 - In directory authorities' approved-routers files, allow
11274 fingerprints with or without space.
11275 - Add a "GETINFO /status/bootstrap-phase" controller option, so the
11276 controller can query our current bootstrap state in case it attaches
11277 partway through and wants to catch up.
11278 - Send an initial "Starting" bootstrap status event, so we have a
11279 state to start out in.
11282 - Asking for a conditional consensus at .../consensus/<fingerprints>
11283 would crash a dirserver if it did not already have a
11284 consensus. Bugfix on 0.2.1.1-alpha.
11285 - Clean up some macro/CPP interactions: some GCC versions don't like
11286 #if/#endif pairs inside macro arguments. Fixes bug 707. Bugfix on
11289 o Bootstrapping bugfixes (on 0.2.1.1-alpha):
11290 - Directory authorities shouldn't complain about bootstrapping
11291 problems just because they do a lot of reachability testing and
11292 some of the connection attempts fail.
11293 - Start sending "count" and "recommendation" key/value pairs in
11294 bootstrap problem status events, so the controller can hear about
11295 problems even before Tor decides they're worth reporting for sure.
11296 - If you're using bridges, generate "bootstrap problem" warnings
11297 as soon as you run out of working bridges, rather than waiting
11298 for ten failures -- which will never happen if you have less than
11300 - If we close our OR connection because there's been a circuit
11301 pending on it for too long, we were telling our bootstrap status
11302 events "REASON=NONE". Now tell them "REASON=TIMEOUT".
11305 Changes in version 0.2.1.1-alpha - 2008-06-13
11306 Tor 0.2.1.1-alpha fixes a lot of memory fragmentation problems that
11307 were making the Tor process bloat especially on Linux; makes our TLS
11308 handshake blend in better; sends "bootstrap phase" status events to
11309 the controller, so it can keep the user informed of progress (and
11310 problems) fetching directory information and establishing circuits;
11311 and adds a variety of smaller features.
11314 - More work on making our TLS handshake blend in: modify the list
11315 of ciphers advertised by OpenSSL in client mode to even more
11316 closely resemble a common web browser. We cheat a little so that
11317 we can advertise ciphers that the locally installed OpenSSL doesn't
11319 - Start sending "bootstrap phase" status events to the controller,
11320 so it can keep the user informed of progress fetching directory
11321 information and establishing circuits. Also inform the controller
11322 if we think we're stuck at a particular bootstrap phase. Implements
11324 - Resume using OpenSSL's RAND_poll() for better (and more portable)
11325 cross-platform entropy collection again. We used to use it, then
11326 stopped using it because of a bug that could crash systems that
11327 called RAND_poll when they had a lot of fds open. It looks like the
11328 bug got fixed in late 2006. Our new behavior is to call RAND_poll()
11329 at startup, and to call RAND_poll() when we reseed later only if
11330 we have a non-buggy OpenSSL version.
11333 - When we choose to abandon a new entry guard because we think our
11334 older ones might be better, close any circuits pending on that
11335 new entry guard connection. This fix should make us recover much
11336 faster when our network is down and then comes back. Bugfix on
11337 0.1.2.8-beta; found by lodger.
11339 o Memory fixes and improvements:
11340 - Add a malloc_good_size implementation to OpenBSD_malloc_linux.c,
11341 to avoid unused RAM in buffer chunks and memory pools.
11342 - Speed up parsing and cut down on memory fragmentation by using
11343 stack-style allocations for parsing directory objects. Previously,
11344 this accounted for over 40% of allocations from within Tor's code
11345 on a typical directory cache.
11346 - Use a Bloom filter rather than a digest-based set to track which
11347 descriptors we need to keep around when we're cleaning out old
11348 router descriptors. This speeds up the computation significantly,
11349 and may reduce fragmentation.
11350 - Reduce the default smartlist size from 32 to 16; it turns out that
11351 most smartlists hold around 8-12 elements tops.
11352 - Make dumpstats() log the fullness and size of openssl-internal
11354 - If the user has applied the experimental SSL_MODE_RELEASE_BUFFERS
11355 patch to their OpenSSL, turn it on to save memory on servers. This
11356 patch will (with any luck) get included in a mainline distribution
11358 - Never use OpenSSL compression: it wastes RAM and CPU trying to
11359 compress cells, which are basically all encrypted, compressed,
11363 - Stop reloading the router list from disk for no reason when we
11364 run out of reachable directory mirrors. Once upon a time reloading
11365 it would set the 'is_running' flag back to 1 for them. It hasn't
11366 done that for a long time.
11367 - In very rare situations new hidden service descriptors were
11368 published earlier than 30 seconds after the last change to the
11369 service. (We currently think that a hidden service descriptor
11370 that's been stable for 30 seconds is worth publishing.)
11373 - Allow separate log levels to be configured for different logging
11374 domains. For example, this allows one to log all notices, warnings,
11375 or errors, plus all memory management messages of level debug or
11376 higher, with: Log [MM] debug-err [*] notice-err file /var/log/tor.
11377 - Add a couple of extra warnings to --enable-gcc-warnings for GCC 4.3,
11378 and stop using a warning that had become unfixably verbose under
11380 - New --hush command-line option similar to --quiet. While --quiet
11381 disables all logging to the console on startup, --hush limits the
11382 output to messages of warning and error severity.
11383 - Servers support a new URL scheme for consensus downloads that
11384 allows the client to specify which authorities are trusted.
11385 The server then only sends the consensus if the client will trust
11386 it. Otherwise a 404 error is sent back. Clients use this
11387 new scheme when the server supports it (meaning it's running
11388 0.2.1.1-alpha or later). Implements proposal 134.
11389 - New configure/torrc options (--enable-geoip-stats,
11390 DirRecordUsageByCountry) to record how many IPs we've served
11391 directory info to in each country code, how many status documents
11392 total we've sent to each country code, and what share of the total
11393 directory requests we should expect to see.
11394 - Use the TLS1 hostname extension to more closely resemble browser
11396 - Lots of new unit tests.
11397 - Add a macro to implement the common pattern of iterating through
11398 two parallel lists in lockstep.
11401 Changes in version 0.2.0.28-rc - 2008-06-13
11402 Tor 0.2.0.28-rc fixes an anonymity-related bug, fixes a hidden-service
11403 performance bug, and fixes a bunch of smaller bugs.
11406 - Fix a bug where, when we were choosing the 'end stream reason' to
11407 put in our relay end cell that we send to the exit relay, Tor
11408 clients on Windows were sometimes sending the wrong 'reason'. The
11409 anonymity problem is that exit relays may be able to guess whether
11410 the client is running Windows, thus helping partition the anonymity
11411 set. Down the road we should stop sending reasons to exit relays,
11412 or otherwise prevent future versions of this bug.
11415 - While setting up a hidden service, some valid introduction circuits
11416 were overlooked and abandoned. This might be the reason for
11417 the long delay in making a hidden service available. Bugfix on
11421 - Update to the "June 9 2008" ip-to-country file.
11422 - Run 'make test' as part of 'make dist', so we stop releasing so
11423 many development snapshots that fail their unit tests.
11426 - When we're checking if we have enough dir info for each relay
11427 to begin establishing circuits, make sure that we actually have
11428 the descriptor listed in the consensus, not just any descriptor.
11430 - Bridge relays no longer print "xx=0" in their extrainfo document
11431 for every single country code in the geoip db. Bugfix on
11433 - Only warn when we fail to load the geoip file if we were planning to
11434 include geoip stats in our extrainfo document. Bugfix on 0.2.0.27-rc.
11435 - If we change our MaxAdvertisedBandwidth and then reload torrc,
11436 Tor won't realize it should publish a new relay descriptor. Fixes
11437 bug 688, reported by mfr. Bugfix on 0.1.2.x.
11438 - When we haven't had any application requests lately, don't bother
11439 logging that we have expired a bunch of descriptors. Bugfix
11441 - Make relay cells written on a connection count as non-padding when
11442 tracking how long a connection has been in use. Bugfix on
11443 0.2.0.1-alpha. Spotted by lodger.
11444 - Fix unit tests in 0.2.0.27-rc.
11445 - Fix compile on Windows.
11448 Changes in version 0.2.0.27-rc - 2008-06-03
11449 Tor 0.2.0.27-rc adds a few features we left out of the earlier
11450 release candidates. In particular, we now include an IP-to-country
11451 GeoIP database, so controllers can easily look up what country a
11452 given relay is in, and so bridge relays can give us some sanitized
11453 summaries about which countries are making use of bridges. (See proposal
11454 126-geoip-fetching.txt for details.)
11457 - Include an IP-to-country GeoIP file in the tarball, so bridge
11458 relays can report sanitized summaries of the usage they're seeing.
11461 - Add a "PURPOSE=" argument to "STREAM NEW" events, as suggested by
11462 Robert Hogan. Fixes the first part of bug 681.
11463 - Make bridge authorities never serve extrainfo docs.
11464 - Add support to detect Libevent versions in the 1.4.x series
11466 - Fix build on gcc 4.3 with --enable-gcc-warnings set.
11467 - Include a new contrib/tor-exit-notice.html file that exit relay
11468 operators can put on their website to help reduce abuse queries.
11471 - When tunneling an encrypted directory connection, and its first
11472 circuit fails, do not leave it unattached and ask the controller
11473 to deal. Fixes the second part of bug 681.
11474 - Make bridge authorities correctly expire old extrainfo documents
11478 Changes in version 0.2.0.26-rc - 2008-05-13
11479 Tor 0.2.0.26-rc fixes a major security vulnerability caused by a bug
11480 in Debian's OpenSSL packages. All users running any 0.2.0.x version
11481 should upgrade, whether they're running Debian or not.
11483 o Major security fixes:
11484 - Use new V3 directory authority keys on the tor26, gabelmoo, and
11485 moria1 V3 directory authorities. The old keys were generated with
11486 a vulnerable version of Debian's OpenSSL package, and must be
11487 considered compromised. Other authorities' keys were not generated
11488 with an affected version of OpenSSL.
11491 - List authority signatures as "unrecognized" based on DirServer
11492 lines, not on cert cache. Bugfix on 0.2.0.x.
11495 - Add a new V3AuthUseLegacyKey option to make it easier for
11496 authorities to change their identity keys if they have to.
11499 Changes in version 0.2.0.25-rc - 2008-04-23
11500 Tor 0.2.0.25-rc makes Tor work again on OS X and certain BSDs.
11503 - Remember to initialize threading before initializing logging.
11504 Otherwise, many BSD-family implementations will crash hard on
11505 startup. Fixes bug 671. Bugfix on 0.2.0.24-rc.
11508 - Authorities correctly free policies on bad servers on
11509 exit. Fixes bug 672. Bugfix on 0.2.0.x.
11512 Changes in version 0.2.0.24-rc - 2008-04-22
11513 Tor 0.2.0.24-rc adds dizum (run by Alex de Joode) as the new sixth
11514 v3 directory authority, makes relays with dynamic IP addresses and no
11515 DirPort notice more quickly when their IP address changes, fixes a few
11516 rare crashes and memory leaks, and fixes a few other miscellaneous bugs.
11518 o New directory authorities:
11519 - Take lefkada out of the list of v3 directory authorities, since
11520 it has been down for months.
11521 - Set up dizum (run by Alex de Joode) as the new sixth v3 directory
11525 - Detect address changes more quickly on non-directory mirror
11526 relays. Bugfix on 0.2.0.18-alpha; fixes bug 652.
11528 o Minor features (security):
11529 - Reject requests for reverse-dns lookup of names that are in
11530 a private address space. Patch from lodger.
11531 - Non-exit relays no longer allow DNS requests. Fixes bug 619. Patch
11534 o Minor bugfixes (crashes):
11535 - Avoid a rare assert that can trigger when Tor doesn't have much
11536 directory information yet and it tries to fetch a v2 hidden
11537 service descriptor. Fixes bug 651, reported by nwf.
11538 - Initialize log mutex before initializing dmalloc. Otherwise,
11539 running with dmalloc would crash. Bugfix on 0.2.0.x-alpha.
11540 - Use recursive pthread mutexes in order to avoid deadlock when
11541 logging debug-level messages to a controller. Bug spotted by nwf,
11542 bugfix on 0.2.0.16-alpha.
11544 o Minor bugfixes (resource management):
11545 - Keep address policies from leaking memory: start their refcount
11546 at 1, not 2. Bugfix on 0.2.0.16-alpha.
11547 - Free authority certificates on exit, so they don't look like memory
11548 leaks. Bugfix on 0.2.0.19-alpha.
11549 - Free static hashtables for policy maps and for TLS connections on
11550 shutdown, so they don't look like memory leaks. Bugfix on 0.2.0.x.
11551 - Avoid allocating extra space when computing consensuses on 64-bit
11552 platforms. Bug spotted by aakova.
11554 o Minor bugfixes (misc):
11555 - Do not read the configuration file when we've only been told to
11556 generate a password hash. Fixes bug 643. Bugfix on 0.0.9pre5. Fix
11557 based on patch from Sebastian Hahn.
11558 - Exit relays that are used as a client can now reach themselves
11559 using the .exit notation, rather than just launching an infinite
11560 pile of circuits. Fixes bug 641. Reported by Sebastian Hahn.
11561 - When attempting to open a logfile fails, tell us why.
11562 - Fix a dumb bug that was preventing us from knowing that we should
11563 preemptively build circuits to handle expected directory requests.
11564 Fixes bug 660. Bugfix on 0.1.2.x.
11565 - Warn less verbosely about clock skew from netinfo cells from
11566 untrusted sources. Fixes bug 663.
11567 - Make controller stream events for DNS requests more consistent,
11568 by adding "new stream" events for DNS requests, and removing
11569 spurious "stream closed" events" for cached reverse resolves.
11570 Patch from mwenge. Fixes bug 646.
11571 - Correctly notify one-hop connections when a circuit build has
11572 failed. Possible fix for bug 669. Found by lodger.
11575 Changes in version 0.2.0.23-rc - 2008-03-24
11576 Tor 0.2.0.23-rc is the fourth release candidate for the 0.2.0 series. It
11577 makes bootstrapping faster if the first directory mirror you contact
11578 is down. The bundles also include the new Vidalia 0.1.2 release.
11581 - When a tunneled directory request is made to a directory server
11582 that's down, notice after 30 seconds rather than 120 seconds. Also,
11583 fail any begindir streams that are pending on it, so they can
11584 retry elsewhere. This was causing multi-minute delays on bootstrap.
11587 Changes in version 0.2.0.22-rc - 2008-03-18
11588 Tor 0.2.0.22-rc is the third release candidate for the 0.2.0 series. It
11589 enables encrypted directory connections by default for non-relays, fixes
11590 some broken TLS behavior we added in 0.2.0.20-rc, and resolves many
11591 other bugs. The bundles also include Vidalia 0.1.1 and Torbutton 1.1.17.
11594 - Enable encrypted directory connections by default for non-relays,
11595 so censor tools that block Tor directory connections based on their
11596 plaintext patterns will no longer work. This means Tor works in
11597 certain censored countries by default again.
11600 - Make sure servers always request certificates from clients during
11601 TLS renegotiation. Reported by lodger; bugfix on 0.2.0.20-rc.
11602 - Do not enter a CPU-eating loop when a connection is closed in
11603 the middle of client-side TLS renegotiation. Fixes bug 622. Bug
11604 diagnosed by lodger; bugfix on 0.2.0.20-rc.
11605 - Fix assertion failure that could occur when a blocked circuit
11606 became unblocked, and it had pending client DNS requests. Bugfix
11607 on 0.2.0.1-alpha. Fixes bug 632.
11609 o Minor bugfixes (on 0.1.2.x):
11610 - Generate "STATUS_SERVER" events rather than misspelled
11611 "STATUS_SEVER" events. Caught by mwenge.
11612 - When counting the number of bytes written on a TLS connection,
11613 look at the BIO actually used for writing to the network, not
11614 at the BIO used (sometimes) to buffer data for the network.
11615 Looking at different BIOs could result in write counts on the
11616 order of ULONG_MAX. Fixes bug 614.
11617 - On Windows, correctly detect errors when listing the contents of
11618 a directory. Fix from lodger.
11620 o Minor bugfixes (on 0.2.0.x):
11621 - Downgrade "sslv3 alert handshake failure" message to INFO.
11622 - If we set RelayBandwidthRate and RelayBandwidthBurst very high but
11623 left BandwidthRate and BandwidthBurst at the default, we would be
11624 silently limited by those defaults. Now raise them to match the
11625 RelayBandwidth* values.
11626 - Fix the SVK version detection logic to work correctly on a branch.
11627 - Make --enable-openbsd-malloc work correctly on Linux with alpha
11628 CPUs. Fixes bug 625.
11629 - Logging functions now check that the passed severity is sane.
11630 - Use proper log levels in the testsuite call of
11631 get_interface_address6().
11632 - When using a nonstandard malloc, do not use the platform values for
11633 HAVE_MALLOC_GOOD_SIZE or HAVE_MALLOC_USABLE_SIZE.
11634 - Make the openbsd malloc code use 8k pages on alpha CPUs and
11636 - Detect mismatched page sizes when using --enable-openbsd-malloc.
11637 - Avoid double-marked-for-close warning when certain kinds of invalid
11638 .in-addr.arpa addresses are passed to the DNSPort. Part of a fix
11639 for bug 617. Bugfix on 0.2.0.1-alpha.
11640 - Make sure that the "NULL-means-reject *:*" convention is followed by
11641 all the policy manipulation functions, avoiding some possible crash
11642 bugs. Bug found by lodger. Bugfix on 0.2.0.16-alpha.
11643 - Fix the implementation of ClientDNSRejectInternalAddresses so that it
11644 actually works, and doesn't warn about every single reverse lookup.
11645 Fixes the other part of bug 617. Bugfix on 0.2.0.1-alpha.
11648 - Only log guard node status when guard node status has changed.
11649 - Downgrade the 3 most common "INFO" messages to "DEBUG". This will
11650 make "INFO" 75% less verbose.
11653 Changes in version 0.2.0.21-rc - 2008-03-02
11654 Tor 0.2.0.21-rc is the second release candidate for the 0.2.0 series. It
11655 makes Tor work well with Vidalia again, fixes a rare assert bug,
11656 and fixes a pair of more minor bugs. The bundles also include Vidalia
11657 0.1.0 and Torbutton 1.1.16.
11660 - The control port should declare that it requires password auth
11661 when HashedControlSessionPassword is set too. Patch from Matt Edman;
11662 bugfix on 0.2.0.20-rc. Fixes bug 615.
11663 - Downgrade assert in connection_buckets_decrement() to a log message.
11664 This may help us solve bug 614, and in any case will make its
11665 symptoms less severe. Bugfix on 0.2.0.20-rc. Reported by fredzupy.
11666 - We were sometimes miscounting the number of bytes read from the
11667 network, causing our rate limiting to not be followed exactly.
11668 Bugfix on 0.2.0.16-alpha. Reported by lodger.
11671 - Fix compilation with OpenSSL 0.9.8 and 0.9.8a. All other supported
11672 OpenSSL versions should have been working fine. Diagnosis and patch
11673 from lodger, Karsten Loesing, and Sebastian Hahn. Fixes bug 616.
11674 Bugfix on 0.2.0.20-rc.
11677 Changes in version 0.2.0.20-rc - 2008-02-24
11678 Tor 0.2.0.20-rc is the first release candidate for the 0.2.0 series. It
11679 makes more progress towards normalizing Tor's TLS handshake, makes
11680 hidden services work better again, helps relays bootstrap if they don't
11681 know their IP address, adds optional support for linking in openbsd's
11682 allocator or tcmalloc, allows really fast relays to scale past 15000
11683 sockets, and fixes a bunch of minor bugs reported by Veracode.
11686 - Enable the revised TLS handshake based on the one designed by
11687 Steven Murdoch in proposal 124, as revised in proposal 130. It
11688 includes version negotiation for OR connections as described in
11689 proposal 105. The new handshake is meant to be harder for censors
11690 to fingerprint, and it adds the ability to detect certain kinds of
11691 man-in-the-middle traffic analysis attacks. The version negotiation
11692 feature will allow us to improve Tor's link protocol more safely
11694 - Choose which bridge to use proportional to its advertised bandwidth,
11695 rather than uniformly at random. This should speed up Tor for
11696 bridge users. Also do this for people who set StrictEntryNodes.
11697 - When a TrackHostExits-chosen exit fails too many times in a row,
11698 stop using it. Bugfix on 0.1.2.x; fixes bug 437.
11701 - Resolved problems with (re-)fetching hidden service descriptors.
11702 Patch from Karsten Loesing; fixes problems with 0.2.0.18-alpha
11703 and 0.2.0.19-alpha.
11704 - If we only ever used Tor for hidden service lookups or posts, we
11705 would stop building circuits and start refusing connections after
11706 24 hours, since we falsely believed that Tor was dormant. Reported
11707 by nwf; bugfix on 0.1.2.x.
11708 - Servers that don't know their own IP address should go to the
11709 authorities for their first directory fetch, even if their DirPort
11710 is off or if they don't know they're reachable yet. This will help
11711 them bootstrap better. Bugfix on 0.2.0.18-alpha; fixes bug 609.
11712 - When counting the number of open sockets, count not only the number
11713 of sockets we have received from the socket() call, but also
11714 the number we've gotten from accept() and socketpair(). This bug
11715 made us fail to count all sockets that we were using for incoming
11716 connections. Bugfix on 0.2.0.x.
11717 - Fix code used to find strings within buffers, when those strings
11718 are not in the first chunk of the buffer. Bugfix on 0.2.0.x.
11719 - Fix potential segfault when parsing HTTP headers. Bugfix on 0.2.0.x.
11720 - Add a new __HashedControlSessionPassword option for controllers
11721 to use for one-off session password hashes that shouldn't get
11722 saved to disk by SAVECONF --- Vidalia users were accumulating a
11723 pile of HashedControlPassword lines in their torrc files, one for
11724 each time they had restarted Tor and then clicked Save. Make Tor
11725 automatically convert "HashedControlPassword" to this new option but
11726 only when it's given on the command line. Partial fix for bug 586.
11728 o Minor features (performance):
11729 - Tune parameters for cell pool allocation to minimize amount of
11731 - Add OpenBSD malloc code from phk as an optional malloc
11732 replacement on Linux: some glibc libraries do very poorly
11733 with Tor's memory allocation patterns. Pass
11734 --enable-openbsd-malloc to get the replacement malloc code.
11735 - Add a --with-tcmalloc option to the configure script to link
11736 against tcmalloc (if present). Does not yet search for
11737 non-system include paths.
11738 - Stop imposing an arbitrary maximum on the number of file descriptors
11739 used for busy servers. Bug reported by Olaf Selke; patch from
11742 o Minor features (other):
11743 - When SafeLogging is disabled, log addresses along with all TLS
11745 - When building with --enable-gcc-warnings, check for whether Apple's
11746 warning "-Wshorten-64-to-32" is available.
11747 - Add a --passphrase-fd argument to the tor-gencert command for
11750 o Minor bugfixes (memory leaks and code problems):
11751 - We were leaking a file descriptor if Tor started with a zero-length
11752 cached-descriptors file. Patch by freddy77; bugfix on 0.1.2.
11753 - Detect size overflow in zlib code. Reported by Justin Ferguson and
11755 - We were comparing the raw BridgePassword entry with a base64'ed
11756 version of it, when handling a "/tor/networkstatus-bridges"
11757 directory request. Now compare correctly. Noticed by Veracode.
11758 - Recover from bad tracked-since value in MTBF-history file.
11759 Should fix bug 537.
11760 - Alter the code that tries to recover from unhandled write
11761 errors, to not try to flush onto a socket that's given us
11762 unhandled errors. Bugfix on 0.1.2.x.
11763 - Make Unix controlsockets work correctly on OpenBSD. Patch from
11764 tup. Bugfix on 0.2.0.3-alpha.
11766 o Minor bugfixes (other):
11767 - If we have an extra-info document for our server, always make
11768 it available on the control port, even if we haven't gotten
11769 a copy of it from an authority yet. Patch from mwenge.
11770 - Log the correct memory chunk sizes for empty RAM chunks in mempool.c.
11771 - Directory mirrors no longer include a guess at the client's IP
11772 address if the connection appears to be coming from the same /24
11773 network; it was producing too many wrong guesses.
11774 - Make the new hidden service code respect the SafeLogging setting.
11775 Bugfix on 0.2.0.x. Patch from Karsten.
11776 - When starting as an authority, do not overwrite all certificates
11777 cached from other authorities. Bugfix on 0.2.0.x. Fixes bug 606.
11778 - If we're trying to flush the last bytes on a connection (for
11779 example, when answering a directory request), reset the
11780 time-to-give-up timeout every time we manage to write something
11781 on the socket. Bugfix on 0.1.2.x.
11782 - Change the behavior of "getinfo status/good-server-descriptor"
11783 so it doesn't return failure when any authority disappears.
11784 - Even though the man page said that "TrackHostExits ." should
11785 work, nobody had ever implemented it. Bugfix on 0.1.0.x.
11786 - Report TLS "zero return" case as a "clean close" and "IO error"
11787 as a "close". Stop calling closes "unexpected closes": existing
11788 Tors don't use SSL_close(), so having a connection close without
11789 the TLS shutdown handshake is hardly unexpected.
11790 - Send NAMESERVER_STATUS messages for a single failed nameserver
11793 o Code simplifications and refactoring:
11794 - Remove the tor_strpartition function: its logic was confused,
11795 and it was only used for one thing that could be implemented far
11799 Changes in version 0.2.0.19-alpha - 2008-02-09
11800 Tor 0.2.0.19-alpha makes more progress towards normalizing Tor's TLS
11801 handshake, makes path selection for relays more secure and IP address
11802 guessing more robust, and generally fixes a lot of bugs in preparation
11803 for calling the 0.2.0 branch stable.
11806 - Do not include recognizeable strings in the commonname part of
11807 Tor's x509 certificates.
11810 - If we're a relay, avoid picking ourselves as an introduction point,
11811 a rendezvous point, or as the final hop for internal circuits. Bug
11812 reported by taranis and lodger. Bugfix on 0.1.2.x.
11813 - Patch from "Andrew S. Lists" to catch when we contact a directory
11814 mirror at IP address X and he says we look like we're coming from
11815 IP address X. Bugfix on 0.1.2.x.
11817 o Minor features (security):
11818 - Be more paranoid about overwriting sensitive memory on free(),
11819 as a defensive programming tactic to ensure forward secrecy.
11821 o Minor features (directory authority):
11822 - Actually validate the options passed to AuthDirReject,
11823 AuthDirInvalid, AuthDirBadDir, and AuthDirBadExit.
11824 - Reject router descriptors with out-of-range bandwidthcapacity or
11825 bandwidthburst values.
11827 o Minor features (controller):
11828 - Reject controller commands over 1MB in length. This keeps rogue
11829 processes from running us out of memory.
11831 o Minor features (misc):
11832 - Give more descriptive well-formedness errors for out-of-range
11833 hidden service descriptor/protocol versions.
11834 - Make memory debugging information describe more about history
11835 of cell allocation, so we can help reduce our memory use.
11837 o Deprecated features (controller):
11838 - The status/version/num-versioning and status/version/num-concurring
11839 GETINFO options are no longer useful in the v3 directory protocol:
11840 treat them as deprecated, and warn when they're used.
11843 - When our consensus networkstatus has been expired for a while, stop
11844 being willing to build circuits using it. Fixes bug 401. Bugfix
11846 - Directory caches now fetch certificates from all authorities
11847 listed in a networkstatus consensus, even when they do not
11848 recognize them. Fixes bug 571. Bugfix on 0.2.0.x.
11849 - When connecting to a bridge without specifying its key, insert
11850 the connection into the identity-to-connection map as soon as
11851 a key is learned. Fixes bug 574. Bugfix on 0.2.0.x.
11852 - Detect versions of OS X where malloc_good_size() is present in the
11853 library but never actually declared. Resolves bug 587. Bugfix
11855 - Stop incorrectly truncating zlib responses to directory authority
11856 signature download requests. Fixes bug 593. Bugfix on 0.2.0.x.
11857 - Stop recommending that every server operator send mail to tor-ops.
11858 Resolves bug 597. Bugfix on 0.1.2.x.
11859 - Don't trigger an assert if we start a directory authority with a
11860 private IP address (like 127.0.0.1).
11861 - Avoid possible failures when generating a directory with routers
11862 with over-long versions strings, or too many flags set. Bugfix
11864 - If an attempt to launch a DNS resolve request over the control
11865 port fails because we have overrun the limit on the number of
11866 connections, tell the controller that the request has failed.
11867 - Avoid using too little bandwidth when our clock skips a few
11868 seconds. Bugfix on 0.1.2.x.
11869 - Fix shell error when warning about missing packages in configure
11870 script, on Fedora or Red Hat machines. Bugfix on 0.2.0.x.
11871 - Do not become confused when receiving a spurious VERSIONS-like
11872 cell from a confused v1 client. Bugfix on 0.2.0.x.
11873 - Re-fetch v2 (as well as v0) rendezvous descriptors when all
11874 introduction points for a hidden service have failed. Patch from
11875 Karsten Loesing. Bugfix on 0.2.0.x.
11877 o Code simplifications and refactoring:
11878 - Remove some needless generality from cpuworker code, for improved
11880 - Stop overloading the circuit_t.onionskin field for both "onionskin
11881 from a CREATE cell that we are waiting for a cpuworker to be
11882 assigned" and "onionskin from an EXTEND cell that we are going to
11883 send to an OR as soon as we are connected". Might help with bug 600.
11884 - Add an in-place version of aes_crypt() so that we can avoid doing a
11885 needless memcpy() call on each cell payload.
11888 Changes in version 0.2.0.18-alpha - 2008-01-25
11889 Tor 0.2.0.18-alpha adds a sixth v3 directory authority run by CCC,
11890 fixes a big memory leak in 0.2.0.17-alpha, and adds new config options
11891 that can warn or reject connections to ports generally associated with
11892 vulnerable-plaintext protocols.
11894 o New directory authorities:
11895 - Set up dannenberg (run by CCC) as the sixth v3 directory
11899 - Fix a major memory leak when attempting to use the v2 TLS
11900 handshake code. Bugfix on 0.2.0.x; fixes bug 589.
11901 - We accidentally enabled the under-development v2 TLS handshake
11902 code, which was causing log entries like "TLS error while
11903 renegotiating handshake". Disable it again. Resolves bug 590.
11904 - We were computing the wrong Content-Length: header for directory
11905 responses that need to be compressed on the fly, causing clients
11906 asking for those items to always fail. Bugfix on 0.2.0.x; partially
11910 - Avoid going directly to the directory authorities even if you're a
11911 relay, if you haven't found yourself reachable yet or if you've
11912 decided not to advertise your dirport yet. Addresses bug 556.
11913 - If we've gone 12 hours since our last bandwidth check, and we
11914 estimate we have less than 50KB bandwidth capacity but we could
11915 handle more, do another bandwidth test.
11916 - New config options WarnPlaintextPorts and RejectPlaintextPorts so
11917 Tor can warn and/or refuse connections to ports commonly used with
11918 vulnerable-plaintext protocols. Currently we warn on ports 23,
11919 109, 110, and 143, but we don't reject any.
11922 - When we setconf ClientOnly to 1, close any current OR and Dir
11923 listeners. Reported by mwenge.
11924 - When we get a consensus that's been signed by more people than
11925 we expect, don't log about it; it's not a big deal. Reported
11929 - Don't answer "/tor/networkstatus-bridges" directory requests if
11930 the request isn't encrypted.
11931 - Make "ClientOnly 1" config option disable directory ports too.
11932 - Patches from Karsten Loesing to make v2 hidden services more
11933 robust: work even when there aren't enough HSDir relays available;
11934 retry when a v2 rend desc fetch fails; but don't retry if we
11935 already have a usable v0 rend desc.
11938 Changes in version 0.2.0.17-alpha - 2008-01-17
11939 Tor 0.2.0.17-alpha makes the tarball build cleanly again (whoops).
11942 - Make the tor-gencert man page get included correctly in the tarball.
11945 Changes in version 0.2.0.16-alpha - 2008-01-17
11946 Tor 0.2.0.16-alpha adds a fifth v3 directory authority run by Karsten
11947 Loesing, and generally cleans up a lot of features and minor bugs.
11949 o New directory authorities:
11950 - Set up gabelmoo (run by Karsten Loesing) as the fifth v3 directory
11953 o Major performance improvements:
11954 - Switch our old ring buffer implementation for one more like that
11955 used by free Unix kernels. The wasted space in a buffer with 1mb
11956 of data will now be more like 8k than 1mb. The new implementation
11957 also avoids realloc();realloc(); patterns that can contribute to
11958 memory fragmentation.
11961 - Configuration files now accept C-style strings as values. This
11962 helps encode characters not allowed in the current configuration
11963 file format, such as newline or #. Addresses bug 557.
11964 - Although we fixed bug 539 (where servers would send HTTP status 503
11965 responses _and_ send a body too), there are still servers out
11966 there that haven't upgraded. Therefore, make clients parse such
11967 bodies when they receive them.
11968 - When we're not serving v2 directory information, there is no reason
11969 to actually keep any around. Remove the obsolete files and directory
11970 on startup if they are very old and we aren't going to serve them.
11972 o Minor performance improvements:
11973 - Reference-count and share copies of address policy entries; only 5%
11974 of them were actually distinct.
11975 - Never walk through the list of logs if we know that no log is
11976 interested in a given message.
11979 - When an authority has not signed a consensus, do not try to
11980 download a nonexistent "certificate with key 00000000". Bugfix
11981 on 0.2.0.x. Fixes bug 569.
11982 - Fix a rare assert error when we're closing one of our threads:
11983 use a mutex to protect the list of logs, so we never write to the
11984 list as it's being freed. Bugfix on 0.1.2.x. Fixes the very rare
11985 bug 575, which is kind of the revenge of bug 222.
11986 - Patch from Karsten Loesing to complain less at both the client
11987 and the relay when a relay used to have the HSDir flag but doesn't
11988 anymore, and we try to upload a hidden service descriptor.
11989 - Stop leaking one cert per TLS context. Fixes bug 582. Bugfix on
11991 - Do not try to download missing certificates until we have tried
11992 to check our fallback consensus. Fixes bug 583.
11993 - Make bridges round reported GeoIP stats info up to the nearest
11994 estimate, not down. Now we can distinguish between "0 people from
11995 this country" and "1 person from this country".
11996 - Avoid a spurious free on base64 failure. Bugfix on 0.1.2.
11997 - Avoid possible segfault if key generation fails in
11998 crypto_pk_hybrid_encrypt. Bugfix on 0.2.0.
11999 - Avoid segfault in the case where a badly behaved v2 versioning
12000 directory sends a signed networkstatus with missing client-versions.
12002 - Avoid segfaults on certain complex invocations of
12003 router_get_by_hexdigest(). Bugfix on 0.1.2.
12004 - Correct bad index on array access in parse_http_time(). Bugfix
12006 - Fix possible bug in vote generation when server versions are present
12007 but client versions are not.
12008 - Fix rare bug on REDIRECTSTREAM control command when called with no
12009 port set: it could erroneously report an error when none had
12011 - Avoid bogus crash-prone, leak-prone tor_realloc when we're
12012 compressing large objects and find ourselves with more than 4k
12013 left over. Bugfix on 0.2.0.
12014 - Fix a small memory leak when setting up a hidden service.
12015 - Fix a few memory leaks that could in theory happen under bizarre
12017 - Fix an assert if we post a general-purpose descriptor via the
12018 control port but that descriptor isn't mentioned in our current
12019 network consensus. Bug reported by Jon McLachlan; bugfix on
12022 o Minor features (controller):
12023 - Get NS events working again. Patch from tup.
12024 - The GETCONF command now escapes and quotes configuration values
12025 that don't otherwise fit into the torrc file.
12026 - The SETCONF command now handles quoted values correctly.
12028 o Minor features (directory authorities):
12029 - New configuration options to override default maximum number of
12030 servers allowed on a single IP address. This is important for
12031 running a test network on a single host.
12032 - Actually implement the -s option to tor-gencert.
12033 - Add a manual page for tor-gencert.
12035 o Minor features (bridges):
12036 - Bridge authorities no longer serve bridge descriptors over
12037 unencrypted connections.
12039 o Minor features (other):
12040 - Add hidden services and DNSPorts to the list of things that make
12041 Tor accept that it has running ports. Change starting Tor with no
12042 ports from a fatal error to a warning; we might change it back if
12043 this turns out to confuse anybody. Fixes bug 579.
12046 Changes in version 0.1.2.19 - 2008-01-17
12047 Tor 0.1.2.19 fixes a huge memory leak on exit relays, makes the default
12048 exit policy a little bit more conservative so it's safer to run an
12049 exit relay on a home system, and fixes a variety of smaller issues.
12052 - Exit policies now reject connections that are addressed to a
12053 relay's public (external) IP address too, unless
12054 ExitPolicyRejectPrivate is turned off. We do this because too
12055 many relays are running nearby to services that trust them based
12056 on network address.
12059 - When the clock jumps forward a lot, do not allow the bandwidth
12060 buckets to become negative. Fixes bug 544.
12061 - Fix a memory leak on exit relays; we were leaking a cached_resolve_t
12062 on every successful resolve. Reported by Mike Perry.
12063 - Purge old entries from the "rephist" database and the hidden
12064 service descriptor database even when DirPort is zero.
12065 - Stop thinking that 0.1.2.x directory servers can handle "begin_dir"
12066 requests. Should ease bugs 406 and 419 where 0.1.2.x relays are
12067 crashing or mis-answering these requests.
12068 - When we decide to send a 503 response to a request for servers, do
12069 not then also send the server descriptors: this defeats the whole
12070 purpose. Fixes bug 539.
12073 - Changing the ExitPolicyRejectPrivate setting should cause us to
12074 rebuild our server descriptor.
12075 - Fix handling of hex nicknames when answering controller requests for
12076 networkstatus by name, or when deciding whether to warn about
12077 unknown routers in a config option. (Patch from mwenge.)
12078 - Fix a couple of hard-to-trigger autoconf problems that could result
12079 in really weird results on platforms whose sys/types.h files define
12080 nonstandard integer types.
12081 - Don't try to create the datadir when running --verify-config or
12082 --hash-password. Resolves bug 540.
12083 - If we were having problems getting a particular descriptor from the
12084 directory caches, and then we learned about a new descriptor for
12085 that router, we weren't resetting our failure count. Reported
12087 - Although we fixed bug 539 (where servers would send HTTP status 503
12088 responses _and_ send a body too), there are still servers out there
12089 that haven't upgraded. Therefore, make clients parse such bodies
12090 when they receive them.
12091 - Run correctly on systems where rlim_t is larger than unsigned long.
12092 This includes some 64-bit systems.
12093 - Run correctly on platforms (like some versions of OS X 10.5) where
12094 the real limit for number of open files is OPEN_FILES, not rlim_max
12095 from getrlimit(RLIMIT_NOFILES).
12096 - Avoid a spurious free on base64 failure.
12097 - Avoid segfaults on certain complex invocations of
12098 router_get_by_hexdigest().
12099 - Fix rare bug on REDIRECTSTREAM control command when called with no
12100 port set: it could erroneously report an error when none had
12104 Changes in version 0.2.0.15-alpha - 2007-12-25
12105 Tor 0.2.0.14-alpha and 0.2.0.15-alpha fix a bunch of bugs with the
12106 features added in 0.2.0.13-alpha.
12109 - Fix several remotely triggerable asserts based on DirPort requests
12110 for a v2 or v3 networkstatus object before we were prepared. This
12111 was particularly bad for 0.2.0.13 and later bridge relays, who
12112 would never have a v2 networkstatus and would thus always crash
12113 when used. Bugfixes on 0.2.0.x.
12114 - Estimate the v3 networkstatus size more accurately, rather than
12115 estimating it at zero bytes and giving it artificially high priority
12116 compared to other directory requests. Bugfix on 0.2.0.x.
12119 - Fix configure.in logic for cross-compilation.
12120 - When we load a bridge descriptor from the cache, and it was
12121 previously unreachable, mark it as retriable so we won't just
12122 ignore it. Also, try fetching a new copy immediately. Bugfixes
12124 - The bridge GeoIP stats were counting other relays, for example
12125 self-reachability and authority-reachability tests.
12128 - Support compilation to target iPhone; patch from cjacker huang.
12129 To build for iPhone, pass the --enable-iphone option to configure.
12132 Changes in version 0.2.0.14-alpha - 2007-12-23
12134 - Fix a crash on startup if you install Tor 0.2.0.13-alpha fresh
12135 without a datadirectory from a previous Tor install. Reported
12137 - Fix a crash when we fetch a descriptor that turns out to be
12138 unexpected (it used to be in our networkstatus when we started
12139 fetching it, but it isn't in our current networkstatus), and we
12140 aren't using bridges. Bugfix on 0.2.0.x.
12141 - Fix a crash when accessing hidden services: it would work the first
12142 time you use a given introduction point for your service, but
12143 on subsequent requests we'd be using garbage memory. Fixed by
12144 Karsten Loesing. Bugfix on 0.2.0.13-alpha.
12145 - Fix a crash when we load a bridge descriptor from disk but we don't
12146 currently have a Bridge line for it in our torrc. Bugfix on
12150 - If bridge authorities set BridgePassword, they will serve a
12151 snapshot of known bridge routerstatuses from their DirPort to
12152 anybody who knows that password. Unset by default.
12155 - Make the unit tests build again.
12156 - Make "GETINFO/desc-annotations/id/<OR digest>" actually work.
12157 - Make PublishServerDescriptor default to 1, so the default doesn't
12158 have to change as we invent new directory protocol versions.
12159 - Fix test for rlim_t on OSX 10.3: sys/resource.h doesn't want to
12160 be included unless sys/time.h is already included. Fixes
12161 bug 553. Bugfix on 0.2.0.x.
12162 - If we receive a general-purpose descriptor and then receive an
12163 identical bridge-purpose descriptor soon after, don't discard
12164 the next one as a duplicate.
12167 - If BridgeRelay is set to 1, then the default for
12168 PublishServerDescriptor is now "bridge" rather than "v2,v3".
12169 - If the user sets RelayBandwidthRate but doesn't set
12170 RelayBandwidthBurst, then make them equal rather than erroring out.
12173 Changes in version 0.2.0.13-alpha - 2007-12-21
12174 Tor 0.2.0.13-alpha adds a fourth v3 directory authority run by Geoff
12175 Goodell, fixes many more bugs, and adds a lot of infrastructure for
12178 o New directory authorities:
12179 - Set up lefkada (run by Geoff Goodell) as the fourth v3 directory
12183 - Only update guard status (usable / not usable) once we have
12184 enough directory information. This was causing us to always pick
12185 two new guards on startup (bugfix on 0.2.0.9-alpha), and it was
12186 causing us to discard all our guards on startup if we hadn't been
12187 running for a few weeks (bugfix on 0.1.2.x). Fixes bug 448.
12188 - Purge old entries from the "rephist" database and the hidden
12189 service descriptor databases even when DirPort is zero. Bugfix
12191 - We were ignoring our RelayBandwidthRate for the first 30 seconds
12192 after opening a circuit -- even a relayed circuit. Bugfix on
12194 - Stop thinking that 0.1.2.x directory servers can handle "begin_dir"
12195 requests. Should ease bugs 406 and 419 where 0.1.2.x relays are
12196 crashing or mis-answering these types of requests.
12197 - Relays were publishing their server descriptor to v1 and v2
12198 directory authorities, but they didn't try publishing to v3-only
12199 authorities. Fix this; and also stop publishing to v1 authorities.
12201 - When we were reading router descriptors from cache, we were ignoring
12202 the annotations -- so for example we were reading in bridge-purpose
12203 descriptors as general-purpose descriptors. Bugfix on 0.2.0.8-alpha.
12204 - When we decided to send a 503 response to a request for servers, we
12205 were then also sending the server descriptors: this defeats the
12206 whole purpose. Fixes bug 539; bugfix on 0.1.2.x.
12209 - Bridge relays now behave like clients with respect to time
12210 intervals for downloading new consensus documents -- otherwise they
12211 stand out. Bridge users now wait until the end of the interval,
12212 so their bridge relay will be sure to have a new consensus document.
12213 - Three new config options (AlternateDirAuthority,
12214 AlternateBridgeAuthority, and AlternateHSAuthority) that let the
12215 user selectively replace the default directory authorities by type,
12216 rather than the all-or-nothing replacement that DirServer offers.
12217 - Tor can now be configured to read a GeoIP file from disk in one
12218 of two formats. This can be used by controllers to map IP addresses
12219 to countries. Eventually, it may support exit-by-country.
12220 - When possible, bridge relays remember which countries users
12221 are coming from, and report aggregate information in their
12222 extra-info documents, so that the bridge authorities can learn
12223 where Tor is blocked.
12224 - Bridge directory authorities now do reachability testing on the
12225 bridges they know. They provide router status summaries to the
12226 controller via "getinfo ns/purpose/bridge", and also dump summaries
12227 to a file periodically.
12228 - Stop fetching directory info so aggressively if your DirPort is
12229 on but your ORPort is off; stop fetching v2 dir info entirely.
12230 You can override these choices with the new FetchDirInfoEarly
12234 - The fix in 0.2.0.12-alpha cleared the "hsdir" flag in v3 network
12235 consensus documents when there are too many relays at a single
12236 IP address. Now clear it in v2 network status documents too, and
12237 also clear it in routerinfo_t when the relay is no longer listed
12238 in the relevant networkstatus document.
12239 - Don't crash if we get an unexpected value for the
12240 PublishServerDescriptor config option. Reported by Matt Edman;
12241 bugfix on 0.2.0.9-alpha.
12242 - Our new v2 hidden service descriptor format allows descriptors
12243 that have no introduction points. But Tor crashed when we tried
12244 to build a descriptor with no intro points (and it would have
12245 crashed if we had tried to parse one). Bugfix on 0.2.0.x; patch
12246 by Karsten Loesing.
12247 - Fix building with dmalloc 5.5.2 with glibc.
12248 - Reject uploaded descriptors and extrainfo documents if they're
12249 huge. Otherwise we'll cache them all over the network and it'll
12250 clog everything up. Reported by Aljosha Judmayer.
12251 - Check for presence of s6_addr16 and s6_addr32 fields in in6_addr
12252 via autoconf. Should fix compile on solaris. Bugfix on 0.2.0.x.
12253 - When the DANGEROUS_VERSION controller status event told us we're
12254 running an obsolete version, it used the string "OLD" to describe
12255 it. Yet the "getinfo" interface used the string "OBSOLETE". Now use
12256 "OBSOLETE" in both cases. Bugfix on 0.1.2.x.
12257 - If we can't expand our list of entry guards (e.g. because we're
12258 using bridges or we have StrictEntryNodes set), don't mark relays
12259 down when they fail a directory request. Otherwise we're too quick
12260 to mark all our entry points down. Bugfix on 0.1.2.x.
12261 - Fix handling of hex nicknames when answering controller requests for
12262 networkstatus by name, or when deciding whether to warn about unknown
12263 routers in a config option. Bugfix on 0.1.2.x. (Patch from mwenge.)
12264 - Fix a couple of hard-to-trigger autoconf problems that could result
12265 in really weird results on platforms whose sys/types.h files define
12266 nonstandard integer types. Bugfix on 0.1.2.x.
12267 - Fix compilation with --disable-threads set. Bugfix on 0.2.0.x.
12268 - Don't crash on name lookup when we have no current consensus. Fixes
12269 bug 538; bugfix on 0.2.0.x.
12270 - Only Tors that want to mirror the v2 directory info should
12271 create the "cached-status" directory in their datadir. (All Tors
12272 used to create it.) Bugfix on 0.2.0.9-alpha.
12273 - Directory authorities should only automatically download Extra Info
12274 documents if they're v1, v2, or v3 authorities. Bugfix on 0.1.2.x.
12277 - On the USR1 signal, when dmalloc is in use, log the top 10 memory
12278 consumers. (We already do this on HUP.)
12279 - Authorities and caches fetch the v2 networkstatus documents
12280 less often, now that v3 is encouraged.
12281 - Add a new config option BridgeRelay that specifies you want to
12282 be a bridge relay. Right now the only difference is that it makes
12283 you answer begin_dir requests, and it makes you cache dir info,
12284 even if your DirPort isn't on.
12285 - Add "GETINFO/desc-annotations/id/<OR digest>" so controllers can
12286 ask about source, timestamp of arrival, purpose, etc. We need
12287 something like this to help Vidalia not do GeoIP lookups on bridge
12289 - Allow multiple HashedControlPassword config lines, to support
12290 multiple controller passwords.
12291 - Authorities now decide whether they're authoritative for a given
12292 router based on the router's purpose.
12293 - New config options AuthDirBadDir and AuthDirListBadDirs for
12294 authorities to mark certain relays as "bad directories" in the
12295 networkstatus documents. Also supports the "!baddir" directive in
12296 the approved-routers file.
12299 Changes in version 0.2.0.12-alpha - 2007-11-16
12300 This twelfth development snapshot fixes some more build problems as
12301 well as a few minor bugs.
12304 - Make it build on OpenBSD again. Patch from tup.
12305 - Substitute BINDIR and LOCALSTATEDIR in scripts. Fixes
12306 package-building for Red Hat, OS X, etc.
12308 o Minor bugfixes (on 0.1.2.x):
12309 - Changing the ExitPolicyRejectPrivate setting should cause us to
12310 rebuild our server descriptor.
12312 o Minor bugfixes (on 0.2.0.x):
12313 - When we're lacking a consensus, don't try to perform rendezvous
12314 operations. Reported by Karsten Loesing.
12315 - Fix a small memory leak whenever we decide against using a
12316 newly picked entry guard. Reported by Mike Perry.
12317 - When authorities detected more than two relays running on the same
12318 IP address, they were clearing all the status flags but forgetting
12319 to clear the "hsdir" flag. So clients were being told that a
12320 given relay was the right choice for a v2 hsdir lookup, yet they
12321 never had its descriptor because it was marked as 'not running'
12323 - If we're trying to fetch a bridge descriptor and there's no way
12324 the bridge authority could help us (for example, we don't know
12325 a digest, or there is no bridge authority), don't be so eager to
12326 fall back to asking the bridge authority.
12327 - If we're using bridges or have strictentrynodes set, and our
12328 chosen exit is in the same family as all our bridges/entry guards,
12329 then be flexible about families.
12332 - When we negotiate a v2 link-layer connection (not yet implemented),
12333 accept RELAY_EARLY cells and turn them into RELAY cells if we've
12334 negotiated a v1 connection for their next step. Initial code for
12338 Changes in version 0.2.0.11-alpha - 2007-11-12
12339 This eleventh development snapshot fixes some build problems with
12340 the previous snapshot. It also includes a more secure-by-default exit
12341 policy for relays, fixes an enormous memory leak for exit relays, and
12342 fixes another bug where servers were falling out of the directory list.
12345 - Exit policies now reject connections that are addressed to a
12346 relay's public (external) IP address too, unless
12347 ExitPolicyRejectPrivate is turned off. We do this because too
12348 many relays are running nearby to services that trust them based
12349 on network address. Bugfix on 0.1.2.x.
12352 - Fix a memory leak on exit relays; we were leaking a cached_resolve_t
12353 on every successful resolve. Reported by Mike Perry; bugfix
12355 - On authorities, never downgrade to old router descriptors simply
12356 because they're listed in the consensus. This created a catch-22
12357 where we wouldn't list a new descriptor because there was an
12358 old one in the consensus, and we couldn't get the new one in the
12359 consensus because we wouldn't list it. Possible fix for bug 548.
12360 Also, this might cause bug 543 to appear on authorities; if so,
12361 we'll need a band-aid for that. Bugfix on 0.2.0.9-alpha.
12363 o Packaging fixes on 0.2.0.10-alpha:
12364 - We were including instructions about what to do with the
12365 src/config/fallback-consensus file, but we weren't actually
12366 including it in the tarball. Disable all of that for now.
12369 - Allow people to say PreferTunnelledDirConns rather than
12370 PreferTunneledDirConns, for those alternate-spellers out there.
12373 - Don't reevaluate all the information from our consensus document
12374 just because we've downloaded a v2 networkstatus that we intend
12375 to cache. Fixes bug 545; bugfix on 0.2.0.x.
12378 Changes in version 0.2.0.10-alpha - 2007-11-10
12379 This tenth development snapshot adds a third v3 directory authority
12380 run by Mike Perry, adds most of Karsten Loesing's new hidden service
12381 descriptor format, fixes a bad crash bug and new bridge bugs introduced
12382 in 0.2.0.9-alpha, fixes many bugs with the v3 directory implementation,
12383 fixes some minor memory leaks in previous 0.2.0.x snapshots, and
12384 addresses many more minor issues.
12386 o New directory authorities:
12387 - Set up ides (run by Mike Perry) as the third v3 directory authority.
12390 - Allow tunnelled directory connections to ask for an encrypted
12391 "begin_dir" connection or an anonymized "uses a full Tor circuit"
12392 connection independently. Now we can make anonymized begin_dir
12393 connections for (e.g.) more secure hidden service posting and
12395 - More progress on proposal 114: code from Karsten Loesing to
12396 implement new hidden service descriptor format.
12397 - Raise the default BandwidthRate/BandwidthBurst to 5MB/10MB, to
12398 accommodate the growing number of servers that use the default
12399 and are reaching it.
12400 - Directory authorities use a new formula for selecting which nodes
12401 to advertise as Guards: they must be in the top 7/8 in terms of
12402 how long we have known about them, and above the median of those
12403 nodes in terms of weighted fractional uptime.
12404 - Make "not enough dir info yet" warnings describe *why* Tor feels
12405 it doesn't have enough directory info yet.
12408 - Stop servers from crashing if they set a Family option (or
12409 maybe in other situations too). Bugfix on 0.2.0.9-alpha; reported
12411 - Make bridge users work again -- the move to v3 directories in
12412 0.2.0.9-alpha had introduced a number of bugs that made bridges
12413 no longer work for clients.
12414 - When the clock jumps forward a lot, do not allow the bandwidth
12415 buckets to become negative. Bugfix on 0.1.2.x; fixes bug 544.
12417 o Major bugfixes (v3 dir, bugfixes on 0.2.0.9-alpha):
12418 - When the consensus lists a router descriptor that we previously were
12419 mirroring, but that we considered non-canonical, reload the
12420 descriptor as canonical. This fixes bug 543 where Tor servers
12421 would start complaining after a few days that they don't have
12422 enough directory information to build a circuit.
12423 - Consider replacing the current consensus when certificates arrive
12424 that make the pending consensus valid. Previously, we were only
12425 considering replacement when the new certs _didn't_ help.
12426 - Fix an assert error on startup if we didn't already have the
12427 consensus and certs cached in our datadirectory: we were caching
12428 the consensus in consensus_waiting_for_certs but then free'ing it
12430 - Avoid sending a request for "keys/fp" (for which we'll get a 400 Bad
12431 Request) if we need more v3 certs but we've already got pending
12432 requests for all of them.
12433 - Correctly back off from failing certificate downloads. Fixes
12435 - Authorities don't vote on the Running flag if they have been running
12436 for less than 30 minutes themselves. Fixes bug 547, where a newly
12437 started authority would vote that everyone was down.
12439 o New requirements:
12440 - Drop support for OpenSSL version 0.9.6. Just about nobody was using
12441 it, it had no AES, and it hasn't seen any security patches since
12445 - Clients now hold circuitless TLS connections open for 1.5 times
12446 MaxCircuitDirtiness (15 minutes), since it is likely that they'll
12447 rebuild a new circuit over them within that timeframe. Previously,
12448 they held them open only for KeepalivePeriod (5 minutes).
12449 - Use "If-Modified-Since" to avoid retrieving consensus
12450 networkstatuses that we already have.
12451 - When we have no consensus, check FallbackNetworkstatusFile (defaults
12452 to $PREFIX/share/tor/fallback-consensus) for a consensus. This way
12453 we start knowing some directory caches.
12454 - When we receive a consensus from the future, warn about skew.
12455 - Improve skew reporting: try to give the user a better log message
12456 about how skewed they are, and how much this matters.
12457 - When we have a certificate for an authority, believe that
12458 certificate's claims about the authority's IP address.
12459 - New --quiet command-line option to suppress the default console log.
12460 Good in combination with --hash-password.
12461 - Authorities send back an X-Descriptor-Not-New header in response to
12462 an accepted-but-discarded descriptor upload. Partially implements
12464 - Make the log message for "tls error. breaking." more useful.
12465 - Better log messages about certificate downloads, to attempt to
12466 track down the second incarnation of bug 546.
12468 o Minor features (bridges):
12469 - If bridge users set UpdateBridgesFromAuthority, but the digest
12470 they ask for is a 404 from the bridge authority, they now fall
12471 back to trying the bridge directly.
12472 - Bridges now use begin_dir to publish their server descriptor to
12473 the bridge authority, even when they haven't set TunnelDirConns.
12475 o Minor features (controller):
12476 - When reporting clock skew, and we know that the clock is _at least
12477 as skewed_ as some value, but we don't know the actual value,
12478 report the value as a "minimum skew."
12481 - Update linux-tor-prio.sh script to allow QoS based on the uid of
12482 the Tor process. Patch from Marco Bonetti with tweaks from Mike
12486 - Refuse to start if both ORPort and UseBridges are set. Bugfix
12487 on 0.2.0.x, suggested by Matt Edman.
12488 - Don't stop fetching descriptors when FetchUselessDescriptors is
12489 set, even if we stop asking for circuits. Bugfix on 0.1.2.x;
12490 reported by tup and ioerror.
12491 - Better log message on vote from unknown authority.
12492 - Don't log "Launching 0 request for 0 router" message.
12494 o Minor bugfixes (memory leaks):
12495 - Stop leaking memory every time we parse a v3 certificate. Bugfix
12497 - Stop leaking memory every time we load a v3 certificate. Bugfix
12498 on 0.2.0.1-alpha. Fixes bug 536.
12499 - Stop leaking a cached networkstatus on exit. Bugfix on
12501 - Stop leaking voter information every time we free a consensus.
12502 Bugfix on 0.2.0.3-alpha.
12503 - Stop leaking signed data every time we check a voter signature.
12504 Bugfix on 0.2.0.3-alpha.
12505 - Stop leaking a signature every time we fail to parse a consensus or
12506 a vote. Bugfix on 0.2.0.3-alpha.
12507 - Stop leaking v2_download_status_map on shutdown. Bugfix on
12509 - Stop leaking conn->nickname every time we make a connection to a
12510 Tor relay without knowing its expected identity digest (e.g. when
12511 using bridges). Bugfix on 0.2.0.3-alpha.
12513 - Minor bugfixes (portability):
12514 - Run correctly on platforms where rlim_t is larger than unsigned
12515 long, and/or where the real limit for number of open files is
12516 OPEN_FILES, not rlim_max from getrlimit(RLIMIT_NOFILES). In
12517 particular, these may be needed for OS X 10.5.
12520 Changes in version 0.1.2.18 - 2007-10-28
12521 Tor 0.1.2.18 fixes many problems including crash bugs, problems with
12522 hidden service introduction that were causing huge delays, and a big
12523 bug that was causing some servers to disappear from the network status
12524 lists for a few hours each day.
12526 o Major bugfixes (crashes):
12527 - If a connection is shut down abruptly because of something that
12528 happened inside connection_flushed_some(), do not call
12529 connection_finished_flushing(). Should fix bug 451:
12530 "connection_stop_writing: Assertion conn->write_event failed"
12531 Bugfix on 0.1.2.7-alpha.
12532 - Fix possible segfaults in functions called from
12533 rend_process_relay_cell().
12535 o Major bugfixes (hidden services):
12536 - Hidden services were choosing introduction points uniquely by
12537 hexdigest, but when constructing the hidden service descriptor
12538 they merely wrote the (potentially ambiguous) nickname.
12539 - Clients now use the v2 intro format for hidden service
12540 connections: they specify their chosen rendezvous point by identity
12541 digest rather than by (potentially ambiguous) nickname. These
12542 changes could speed up hidden service connections dramatically.
12544 o Major bugfixes (other):
12545 - Stop publishing a new server descriptor just because we get a
12546 HUP signal. This led (in a roundabout way) to some servers getting
12547 dropped from the networkstatus lists for a few hours each day.
12548 - When looking for a circuit to cannibalize, consider family as well
12549 as identity. Fixes bug 438. Bugfix on 0.1.0.x (which introduced
12550 circuit cannibalization).
12551 - When a router wasn't listed in a new networkstatus, we were leaving
12552 the flags for that router alone -- meaning it remained Named,
12553 Running, etc -- even though absence from the networkstatus means
12554 that it shouldn't be considered to exist at all anymore. Now we
12555 clear all the flags for routers that fall out of the networkstatus
12556 consensus. Fixes bug 529.
12559 - Don't try to access (or alter) the state file when running
12560 --list-fingerprint or --verify-config or --hash-password. Resolves
12562 - When generating information telling us how to extend to a given
12563 router, do not try to include the nickname if it is
12564 absent. Resolves bug 467.
12565 - Fix a user-triggerable segfault in expand_filename(). (There isn't
12566 a way to trigger this remotely.)
12567 - When sending a status event to the controller telling it that an
12568 OR address is reachable, set the port correctly. (Previously we
12569 were reporting the dir port.)
12570 - Fix a minor memory leak whenever a controller sends the PROTOCOLINFO
12571 command. Bugfix on 0.1.2.17.
12572 - When loading bandwidth history, do not believe any information in
12573 the future. Fixes bug 434.
12574 - When loading entry guard information, do not believe any information
12576 - When we have our clock set far in the future and generate an
12577 onion key, then re-set our clock to be correct, we should not stop
12578 the onion key from getting rotated.
12579 - On some platforms, accept() can return a broken address. Detect
12580 this more quietly, and deal accordingly. Fixes bug 483.
12581 - It's not actually an error to find a non-pending entry in the DNS
12582 cache when canceling a pending resolve. Don't log unless stuff
12583 is fishy. Resolves bug 463.
12584 - Don't reset trusted dir server list when we set a configuration
12585 option. Patch from Robert Hogan.
12586 - Don't try to create the datadir when running --verify-config or
12587 --hash-password. Resolves bug 540.
12590 Changes in version 0.2.0.9-alpha - 2007-10-24
12591 This ninth development snapshot switches clients to the new v3 directory
12592 system; allows servers to be listed in the network status even when they
12593 have the same nickname as a registered server; and fixes many other
12594 bugs including a big one that was causing some servers to disappear
12595 from the network status lists for a few hours each day.
12597 o Major features (directory system):
12598 - Clients now download v3 consensus networkstatus documents instead
12599 of v2 networkstatus documents. Clients and caches now base their
12600 opinions about routers on these consensus documents. Clients only
12601 download router descriptors listed in the consensus.
12602 - Authorities now list servers who have the same nickname as
12603 a different named server, but list them with a new flag,
12604 "Unnamed". Now we can list servers that happen to pick the same
12605 nickname as a server that registered two years ago and then
12606 disappeared. Partially implements proposal 122.
12607 - If the consensus lists a router as "Unnamed", the name is assigned
12608 to a different router: do not identify the router by that name.
12609 Partially implements proposal 122.
12610 - Authorities can now come to a consensus on which method to use to
12611 compute the consensus. This gives us forward compatibility.
12614 - Stop publishing a new server descriptor just because we HUP or
12615 when we find our DirPort to be reachable but won't actually publish
12616 it. New descriptors without any real changes are dropped by the
12617 authorities, and can screw up our "publish every 18 hours" schedule.
12619 - When a router wasn't listed in a new networkstatus, we were leaving
12620 the flags for that router alone -- meaning it remained Named,
12621 Running, etc -- even though absence from the networkstatus means
12622 that it shouldn't be considered to exist at all anymore. Now we
12623 clear all the flags for routers that fall out of the networkstatus
12624 consensus. Fixes bug 529; bugfix on 0.1.2.x.
12625 - Fix awful behavior in DownloadExtraInfo option where we'd fetch
12626 extrainfo documents and then discard them immediately for not
12627 matching the latest router. Bugfix on 0.2.0.1-alpha.
12629 o Minor features (v3 directory protocol):
12630 - Allow tor-gencert to generate a new certificate without replacing
12632 - Allow certificates to include an address.
12633 - When we change our directory-cache settings, reschedule all voting
12634 and download operations.
12635 - Reattempt certificate downloads immediately on failure, as long as
12636 we haven't failed a threshold number of times yet.
12637 - Delay retrying consensus downloads while we're downloading
12638 certificates to verify the one we just got. Also, count getting a
12639 consensus that we already have (or one that isn't valid) as a failure,
12640 and count failing to get the certificates after 20 minutes as a
12642 - Build circuits and download descriptors even if our consensus is a
12643 little expired. (This feature will go away once authorities are
12646 o Minor features (router descriptor cache):
12647 - If we find a cached-routers file that's been sitting around for more
12648 than 28 days unmodified, then most likely it's a leftover from
12649 when we upgraded to 0.2.0.8-alpha. Remove it. It has no good
12651 - When we (as a cache) download a descriptor because it was listed
12652 in a consensus, remember when the consensus was supposed to expire,
12653 and don't expire the descriptor until then.
12655 o Minor features (performance):
12656 - Call routerlist_remove_old_routers() much less often. This should
12657 speed startup, especially on directory caches.
12658 - Don't try to launch new descriptor downloads quite so often when we
12659 already have enough directory information to build circuits.
12660 - Base64 decoding was actually showing up on our profile when parsing
12661 the initial descriptor file; switch to an in-process all-at-once
12662 implementation that's about 3.5x times faster than calling out to
12665 o Minor features (compilation):
12666 - Detect non-ASCII platforms (if any still exist) and refuse to
12667 build there: some of our code assumes that 'A' is 65 and so on.
12669 o Minor bugfixes (v3 directory authorities, bugfixes on 0.2.0.x):
12670 - Make the "next period" votes into "current period" votes immediately
12671 after publishing the consensus; avoid a heisenbug that made them
12672 stick around indefinitely.
12673 - When we discard a vote as a duplicate, do not report this as
12675 - Treat missing v3 keys or certificates as an error when running as a
12676 v3 directory authority.
12677 - When we're configured to be a v3 authority, but we're only listed
12678 as a non-v3 authority in our DirServer line for ourself, correct
12680 - If an authority doesn't have a qualified hostname, just put
12681 its address in the vote. This fixes the problem where we referred to
12682 "moria on moria:9031."
12683 - Distinguish between detached signatures for the wrong period, and
12684 detached signatures for a divergent vote.
12685 - Fix a small memory leak when computing a consensus.
12686 - When there's no concensus, we were forming a vote every 30
12687 minutes, but writing the "valid-after" line in our vote based
12688 on our configured V3AuthVotingInterval: so unless the intervals
12689 matched up, we immediately rejected our own vote because it didn't
12690 start at the voting interval that caused us to construct a vote.
12692 o Minor bugfixes (v3 directory protocol, bugfixes on 0.2.0.x):
12693 - Delete unverified-consensus when the real consensus is set.
12694 - Consider retrying a consensus networkstatus fetch immediately
12695 after one fails: don't wait 60 seconds to notice.
12696 - When fetching a consensus as a cache, wait until a newer consensus
12697 should exist before trying to replace the current one.
12698 - Use a more forgiving schedule for retrying failed consensus
12699 downloads than for other types.
12701 o Minor bugfixes (other directory issues):
12702 - Correct the implementation of "download votes by digest." Bugfix on
12704 - Authorities no longer send back "400 you're unreachable please fix
12705 it" errors to Tor servers that aren't online all the time. We're
12706 supposed to tolerate these servers now. Bugfix on 0.1.2.x.
12708 o Minor bugfixes (controller):
12709 - Don't reset trusted dir server list when we set a configuration
12710 option. Patch from Robert Hogan; bugfix on 0.1.2.x.
12711 - Respond to INT and TERM SIGNAL commands before we execute the
12712 signal, in case the signal shuts us down. We had a patch in
12713 0.1.2.1-alpha that tried to do this by queueing the response on
12714 the connection's buffer before shutting down, but that really
12715 isn't the same thing at all. Bug located by Matt Edman.
12717 o Minor bugfixes (misc):
12718 - Correctly check for bad options to the "PublishServerDescriptor"
12719 config option. Bugfix on 0.2.0.1-alpha; reported by Matt Edman.
12720 - Stop leaking memory on failing case of base32_decode, and make
12721 it accept upper-case letters. Bugfixes on 0.2.0.7-alpha.
12722 - Don't try to download extrainfo documents when we're trying to
12723 fetch enough directory info to build a circuit: having enough
12724 info should get priority. Bugfix on 0.2.0.x.
12725 - Don't complain that "your server has not managed to confirm that its
12726 ports are reachable" if we haven't been able to build any circuits
12727 yet. Bug found by spending four hours without a v3 consensus. Bugfix
12729 - Detect the reason for failing to mmap a descriptor file we just
12730 wrote, and give a more useful log message. Fixes bug 533. Bugfix
12733 o Code simplifications and refactoring:
12734 - Remove support for the old bw_accounting file: we've been storing
12735 bandwidth accounting information in the state file since
12736 0.1.2.5-alpha. This may result in bandwidth accounting errors
12737 if you try to upgrade from 0.1.1.x or earlier, or if you try to
12738 downgrade to 0.1.1.x or earlier.
12739 - New convenience code to locate a file within the DataDirectory.
12740 - Move non-authority functionality out of dirvote.c.
12741 - Refactor the arguments for router_pick_{directory_|trusteddir}server
12742 so that they all take the same named flags.
12745 - Include the "tor-ctrl.sh" bash script by Stefan Behte to provide
12746 Unix users an easy way to script their Tor process (e.g. by
12747 adjusting bandwidth based on the time of the day).
12750 Changes in version 0.2.0.8-alpha - 2007-10-12
12751 This eighth development snapshot fixes a crash bug that's been bothering
12752 us since February 2007, lets bridge authorities store a list of bridge
12753 descriptors they've seen, gets v3 directory voting closer to working,
12754 starts caching v3 directory consensus documents on directory mirrors,
12755 and fixes a variety of smaller issues including some minor memory leaks.
12757 o Major features (router descriptor cache):
12758 - Store routers in a file called cached-descriptors instead of in
12759 cached-routers. Initialize cached-descriptors from cached-routers
12760 if the old format is around. The new format allows us to store
12761 annotations along with descriptors.
12762 - Use annotations to record the time we received each descriptor, its
12763 source, and its purpose.
12764 - Disable the SETROUTERPURPOSE controller command: it is now
12766 - Controllers should now specify cache=no or cache=yes when using
12767 the +POSTDESCRIPTOR command.
12768 - Bridge authorities now write bridge descriptors to disk, meaning
12769 we can export them to other programs and begin distributing them
12772 o Major features (directory authorities):
12773 - When a v3 authority is missing votes or signatures, it now tries
12775 - Directory authorities track weighted fractional uptime as well as
12776 weighted mean-time-between failures. WFU is suitable for deciding
12777 whether a node is "usually up", while MTBF is suitable for deciding
12778 whether a node is "likely to stay up." We need both, because
12779 "usually up" is a good requirement for guards, while "likely to
12780 stay up" is a good requirement for long-lived connections.
12782 o Major features (v3 directory system):
12783 - Caches now download v3 network status documents as needed,
12784 and download the descriptors listed in them.
12785 - All hosts now attempt to download and keep fresh v3 authority
12786 certificates, and re-attempt after failures.
12787 - More internal-consistency checks for vote parsing.
12789 o Major bugfixes (crashes):
12790 - If a connection is shut down abruptly because of something that
12791 happened inside connection_flushed_some(), do not call
12792 connection_finished_flushing(). Should fix bug 451. Bugfix on
12795 o Major bugfixes (performance):
12796 - Fix really bad O(n^2) performance when parsing a long list of
12797 routers: Instead of searching the entire list for an "extra-info "
12798 string which usually wasn't there, once for every routerinfo
12799 we read, just scan lines forward until we find one we like.
12801 - When we add data to a write buffer in response to the data on that
12802 write buffer getting low because of a flush, do not consider the
12803 newly added data as a candidate for immediate flushing, but rather
12804 make it wait until the next round of writing. Otherwise, we flush
12805 and refill recursively, and a single greedy TLS connection can
12806 eat all of our bandwidth. Bugfix on 0.1.2.7-alpha.
12808 o Minor features (v3 authority system):
12809 - Add more ways for tools to download the votes that lead to the
12811 - Send a 503 when low on bandwidth and a vote, consensus, or
12812 certificate is requested.
12813 - If-modified-since is now implemented properly for all kinds of
12814 certificate requests.
12816 o Minor bugfixes (network statuses):
12817 - Tweak the implementation of proposal 109 slightly: allow at most
12818 two Tor servers on the same IP address, except if it's the location
12819 of a directory authority, in which case allow five. Bugfix on
12822 o Minor bugfixes (controller):
12823 - When sending a status event to the controller telling it that an
12824 OR address is reachable, set the port correctly. (Previously we
12825 were reporting the dir port.) Bugfix on 0.1.2.x.
12827 o Minor bugfixes (v3 directory system):
12828 - Fix logic to look up a cert by its signing key digest. Bugfix on
12830 - Only change the reply to a vote to "OK" if it's not already
12831 set. This gets rid of annoying "400 OK" log messages, which may
12832 have been masking some deeper issue. Bugfix on 0.2.0.7-alpha.
12833 - When we get a valid consensus, recompute the voting schedule.
12834 - Base the valid-after time of a vote on the consensus voting
12835 schedule, not on our preferred schedule.
12836 - Make the return values and messages from signature uploads and
12837 downloads more sensible.
12838 - Fix a memory leak when serving votes and consensus documents, and
12839 another when serving certificates.
12841 o Minor bugfixes (performance):
12842 - Use a slightly simpler string hashing algorithm (copying Python's
12843 instead of Java's) and optimize our digest hashing algorithm to take
12844 advantage of 64-bit platforms and to remove some possibly-costly
12846 - Fix a minor memory leak whenever we parse guards from our state
12847 file. Bugfix on 0.2.0.7-alpha.
12848 - Fix a minor memory leak whenever we write out a file. Bugfix on
12850 - Fix a minor memory leak whenever a controller sends the PROTOCOLINFO
12851 command. Bugfix on 0.2.0.5-alpha.
12853 o Minor bugfixes (portability):
12854 - On some platforms, accept() can return a broken address. Detect
12855 this more quietly, and deal accordingly. Fixes bug 483.
12856 - Stop calling tor_strlower() on uninitialized memory in some cases.
12857 Bugfix in 0.2.0.7-alpha.
12859 o Minor bugfixes (usability):
12860 - Treat some 403 responses from directory servers as INFO rather than
12861 WARN-severity events.
12862 - It's not actually an error to find a non-pending entry in the DNS
12863 cache when canceling a pending resolve. Don't log unless stuff is
12864 fishy. Resolves bug 463.
12866 o Minor bugfixes (anonymity):
12867 - Never report that we've used more bandwidth than we're willing to
12868 relay: it leaks how much non-relay traffic we're using. Resolves
12870 - When looking for a circuit to cannibalize, consider family as well
12871 as identity. Fixes bug 438. Bugfix on 0.1.0.x (which introduced
12872 circuit cannibalization).
12874 o Code simplifications and refactoring:
12875 - Make a bunch of functions static. Remove some dead code.
12876 - Pull out about a third of the really big routerlist.c; put it in a
12877 new module, networkstatus.c.
12878 - Merge the extra fields in local_routerstatus_t back into
12879 routerstatus_t: we used to need one routerstatus_t for each
12880 authority's opinion, plus a local_routerstatus_t for the locally
12881 computed consensus opinion. To save space, we put the locally
12882 modified fields into local_routerstatus_t, and only the common
12883 stuff into routerstatus_t. But once v3 directories are in use,
12884 clients and caches will no longer need to hold authority opinions;
12885 thus, the rationale for keeping the types separate is now gone.
12886 - Make the code used to reschedule and reattempt downloads more
12888 - Turn all 'Are we a directory server/mirror?' logic into a call to
12890 - Remove the code to generate the oldest (v1) directory format.
12891 The code has been disabled since 0.2.0.5-alpha.
12894 Changes in version 0.2.0.7-alpha - 2007-09-21
12895 This seventh development snapshot makes bridges work again, makes bridge
12896 authorities work for the first time, fixes two huge performance flaws
12897 in hidden services, and fixes a variety of minor issues.
12899 o New directory authorities:
12900 - Set up moria1 and tor26 as the first v3 directory authorities. See
12901 doc/spec/dir-spec.txt for details on the new directory design.
12903 o Major bugfixes (crashes):
12904 - Fix possible segfaults in functions called from
12905 rend_process_relay_cell(). Bugfix on 0.1.2.x.
12907 o Major bugfixes (bridges):
12908 - Fix a bug that made servers send a "404 Not found" in response to
12909 attempts to fetch their server descriptor. This caused Tor servers
12910 to take many minutes to establish reachability for their DirPort,
12911 and it totally crippled bridges. Bugfix on 0.2.0.5-alpha.
12912 - Make "UpdateBridgesFromAuthority" torrc option work: when bridge
12913 users configure that and specify a bridge with an identity
12914 fingerprint, now they will lookup the bridge descriptor at the
12915 default bridge authority via a one-hop tunnel, but once circuits
12916 are established they will switch to a three-hop tunnel for later
12917 connections to the bridge authority. Bugfix in 0.2.0.3-alpha.
12919 o Major bugfixes (hidden services):
12920 - Hidden services were choosing introduction points uniquely by
12921 hexdigest, but when constructing the hidden service descriptor
12922 they merely wrote the (potentially ambiguous) nickname.
12923 - Clients now use the v2 intro format for hidden service
12924 connections: they specify their chosen rendezvous point by identity
12925 digest rather than by (potentially ambiguous) nickname. Both
12926 are bugfixes on 0.1.2.x, and they could speed up hidden service
12927 connections dramatically. Thanks to Karsten Loesing.
12929 o Minor features (security):
12930 - As a client, do not believe any server that tells us that an
12931 address maps to an internal address space.
12932 - Make it possible to enable HashedControlPassword and
12933 CookieAuthentication at the same time.
12935 o Minor features (guard nodes):
12936 - Tag every guard node in our state file with the version that
12937 we believe added it, or with our own version if we add it. This way,
12938 if a user temporarily runs an old version of Tor and then switches
12939 back to a new one, she doesn't automatically lose her guards.
12941 o Minor features (speed):
12942 - When implementing AES counter mode, update only the portions of the
12943 counter buffer that need to change, and don't keep separate
12944 network-order and host-order counters when they are the same (i.e.,
12945 on big-endian hosts.)
12947 o Minor features (controller):
12948 - Accept LF instead of CRLF on controller, since some software has a
12949 hard time generating real Internet newlines.
12950 - Add GETINFO values for the server status events
12951 "REACHABILITY_SUCCEEDED" and "GOOD_SERVER_DESCRIPTOR". Patch from
12954 o Removed features:
12955 - Routers no longer include bandwidth-history lines in their
12956 descriptors; this information is already available in extra-info
12957 documents, and including it in router descriptors took up 60%
12958 (!) of compressed router descriptor downloads. Completes
12959 implementation of proposal 104.
12960 - Remove the contrib scripts ExerciseServer.py, PathDemo.py,
12961 and TorControl.py, as they use the old v0 controller protocol,
12962 and are obsoleted by TorFlow anyway.
12963 - Drop support for v1 rendezvous descriptors, since we never used
12964 them anyway, and the code has probably rotted by now. Based on
12965 patch from Karsten Loesing.
12966 - On OSX, stop warning the user that kqueue support in libevent is
12967 "experimental", since it seems to have worked fine for ages.
12970 - When generating information telling us how to extend to a given
12971 router, do not try to include the nickname if it is absent. Fixes
12972 bug 467. Bugfix on 0.2.0.3-alpha.
12973 - Fix a user-triggerable (but not remotely-triggerable) segfault
12974 in expand_filename(). Bugfix on 0.1.2.x.
12975 - Fix a memory leak when freeing incomplete requests from DNSPort.
12976 Found by Niels Provos with valgrind. Bugfix on 0.2.0.1-alpha.
12977 - Don't try to access (or alter) the state file when running
12978 --list-fingerprint or --verify-config or --hash-password. (Resolves
12979 bug 499.) Bugfix on 0.1.2.x.
12980 - Servers used to decline to publish their DirPort if their
12981 BandwidthRate, RelayBandwidthRate, or MaxAdvertisedBandwidth
12982 were below a threshold. Now they only look at BandwidthRate and
12983 RelayBandwidthRate. Bugfix on 0.1.2.x.
12984 - Remove an optimization in the AES counter-mode code that assumed
12985 that the counter never exceeded 2^68. When the counter can be set
12986 arbitrarily as an IV (as it is by Karsten's new hidden services
12987 code), this assumption no longer holds. Bugfix on 0.1.2.x.
12988 - Resume listing "AUTHORITY" flag for authorities in network status.
12989 Bugfix on 0.2.0.3-alpha; reported by Alex de Joode.
12991 o Code simplifications and refactoring:
12992 - Revamp file-writing logic so we don't need to have the entire
12993 contents of a file in memory at once before we write to disk. Tor,
12995 - Turn "descriptor store" into a full-fledged type.
12996 - Move all NT services code into a separate source file.
12997 - Unify all code that computes medians, percentile elements, etc.
12998 - Get rid of a needless malloc when parsing address policies.
13001 Changes in version 0.1.2.17 - 2007-08-30
13002 Tor 0.1.2.17 features a new Vidalia version in the Windows and OS
13003 X bundles. Vidalia 0.0.14 makes authentication required for the
13004 ControlPort in the default configuration, which addresses important
13005 security risks. Everybody who uses Vidalia (or another controller)
13008 In addition, this Tor update fixes major load balancing problems with
13009 path selection, which should speed things up a lot once many people
13012 o Major bugfixes (security):
13013 - We removed support for the old (v0) control protocol. It has been
13014 deprecated since Tor 0.1.1.1-alpha, and keeping it secure has
13015 become more of a headache than it's worth.
13017 o Major bugfixes (load balancing):
13018 - When choosing nodes for non-guard positions, weight guards
13019 proportionally less, since they already have enough load. Patch
13021 - Raise the "max believable bandwidth" from 1.5MB/s to 10MB/s. This
13022 will allow fast Tor servers to get more attention.
13023 - When we're upgrading from an old Tor version, forget our current
13024 guards and pick new ones according to the new weightings. These
13025 three load balancing patches could raise effective network capacity
13026 by a factor of four. Thanks to Mike Perry for measurements.
13028 o Major bugfixes (stream expiration):
13029 - Expire not-yet-successful application streams in all cases if
13030 they've been around longer than SocksTimeout. Right now there are
13031 some cases where the stream will live forever, demanding a new
13032 circuit every 15 seconds. Fixes bug 454; reported by lodger.
13034 o Minor features (controller):
13035 - Add a PROTOCOLINFO controller command. Like AUTHENTICATE, it
13036 is valid before any authentication has been received. It tells
13037 a controller what kind of authentication is expected, and what
13038 protocol is spoken. Implements proposal 119.
13040 o Minor bugfixes (performance):
13041 - Save on most routerlist_assert_ok() calls in routerlist.c, thus
13042 greatly speeding up loading cached-routers from disk on startup.
13043 - Disable sentinel-based debugging for buffer code: we squashed all
13044 the bugs that this was supposed to detect a long time ago, and now
13045 its only effect is to change our buffer sizes from nice powers of
13046 two (which platform mallocs tend to like) to values slightly over
13047 powers of two (which make some platform mallocs sad).
13049 o Minor bugfixes (misc):
13050 - If exit bandwidth ever exceeds one third of total bandwidth, then
13051 use the correct formula to weight exit nodes when choosing paths.
13052 Based on patch from Mike Perry.
13053 - Choose perfectly fairly among routers when choosing by bandwidth and
13054 weighting by fraction of bandwidth provided by exits. Previously, we
13055 would choose with only approximate fairness, and correct ourselves
13056 if we ran off the end of the list.
13057 - If we require CookieAuthentication but we fail to write the
13058 cookie file, we would warn but not exit, and end up in a state
13059 where no controller could authenticate. Now we exit.
13060 - If we require CookieAuthentication, stop generating a new cookie
13061 every time we change any piece of our config.
13062 - Refuse to start with certain directory authority keys, and
13063 encourage people using them to stop.
13064 - Terminate multi-line control events properly. Original patch
13066 - Fix a minor memory leak when we fail to find enough suitable
13067 servers to choose a circuit.
13068 - Stop leaking part of the descriptor when we run into a particularly
13069 unparseable piece of it.
13072 Changes in version 0.2.0.6-alpha - 2007-08-26
13073 This sixth development snapshot features a new Vidalia version in the
13074 Windows and OS X bundles. Vidalia 0.0.14 makes authentication required for
13075 the ControlPort in the default configuration, which addresses important
13078 In addition, this snapshot fixes major load balancing problems
13079 with path selection, which should speed things up a lot once many
13080 people have upgraded. The directory authorities also use a new
13081 mean-time-between-failure approach to tracking which servers are stable,
13082 rather than just looking at the most recent uptime.
13084 o New directory authorities:
13085 - Set up Tonga as the default bridge directory authority.
13088 - Directory authorities now track servers by weighted
13089 mean-times-between-failures. When we have 4 or more days of data,
13090 use measured MTBF rather than declared uptime to decide whether
13091 to call a router Stable. Implements proposal 108.
13093 o Major bugfixes (load balancing):
13094 - When choosing nodes for non-guard positions, weight guards
13095 proportionally less, since they already have enough load. Patch
13097 - Raise the "max believable bandwidth" from 1.5MB/s to 10MB/s. This
13098 will allow fast Tor servers to get more attention.
13099 - When we're upgrading from an old Tor version, forget our current
13100 guards and pick new ones according to the new weightings. These
13101 three load balancing patches could raise effective network capacity
13102 by a factor of four. Thanks to Mike Perry for measurements.
13104 o Major bugfixes (descriptor parsing):
13105 - Handle unexpected whitespace better in malformed descriptors. Bug
13106 found using Benedikt Boss's new Tor fuzzer! Bugfix on 0.2.0.x.
13109 - There is now an ugly, temporary "desc/all-recent-extrainfo-hack"
13110 GETINFO for Torstat to use until it can switch to using extrainfos.
13111 - Optionally (if built with -DEXPORTMALLINFO) export the output
13112 of mallinfo via http, as tor/mallinfo.txt. Only accessible
13116 - Do not intermix bridge routers with controller-added
13117 routers. (Bugfix on 0.2.0.x)
13118 - Do not fail with an assert when accept() returns an unexpected
13119 address family. Addresses but does not wholly fix bug 483. (Bugfix
13121 - Let directory authorities startup even when they can't generate
13122 a descriptor immediately, e.g. because they don't know their
13124 - Stop putting the authentication cookie in a file called "0"
13125 in your working directory if you don't specify anything for the
13126 new CookieAuthFile option. Reported by Matt Edman.
13127 - Make it possible to read the PROTOCOLINFO response in a way that
13128 conforms to our control-spec. Reported by Matt Edman.
13129 - Fix a minor memory leak when we fail to find enough suitable
13130 servers to choose a circuit. Bugfix on 0.1.2.x.
13131 - Stop leaking part of the descriptor when we run into a particularly
13132 unparseable piece of it. Bugfix on 0.1.2.x.
13133 - Unmap the extrainfo cache file on exit.
13136 Changes in version 0.2.0.5-alpha - 2007-08-19
13137 This fifth development snapshot fixes compilation on Windows again;
13138 fixes an obnoxious client-side bug that slowed things down and put
13139 extra load on the network; gets us closer to using the v3 directory
13140 voting scheme; makes it easier for Tor controllers to use cookie-based
13141 authentication; and fixes a variety of other bugs.
13143 o Removed features:
13144 - Version 1 directories are no longer generated in full. Instead,
13145 authorities generate and serve "stub" v1 directories that list
13146 no servers. This will stop Tor versions 0.1.0.x and earlier from
13147 working, but (for security reasons) nobody should be running those
13150 o Major bugfixes (compilation, 0.2.0.x):
13151 - Try to fix Win32 compilation again: improve checking for IPv6 types.
13152 - Try to fix MSVC compilation: build correctly on platforms that do
13153 not define s6_addr16 or s6_addr32.
13154 - Fix compile on platforms without getaddrinfo: bug found by Li-Hui
13157 o Major bugfixes (stream expiration):
13158 - Expire not-yet-successful application streams in all cases if
13159 they've been around longer than SocksTimeout. Right now there are
13160 some cases where the stream will live forever, demanding a new
13161 circuit every 15 seconds. Bugfix on 0.1.2.7-alpha; fixes bug 454;
13162 reported by lodger.
13164 o Minor features (directory servers):
13165 - When somebody requests a list of statuses or servers, and we have
13166 none of those, return a 404 rather than an empty 200.
13168 o Minor features (directory voting):
13169 - Store v3 consensus status consensuses on disk, and reload them
13172 o Minor features (security):
13173 - Warn about unsafe ControlPort configurations.
13174 - Refuse to start with certain directory authority keys, and
13175 encourage people using them to stop.
13177 o Minor features (controller):
13178 - Add a PROTOCOLINFO controller command. Like AUTHENTICATE, it
13179 is valid before any authentication has been received. It tells
13180 a controller what kind of authentication is expected, and what
13181 protocol is spoken. Implements proposal 119.
13182 - New config option CookieAuthFile to choose a new location for the
13183 cookie authentication file, and config option
13184 CookieAuthFileGroupReadable to make it group-readable.
13186 o Minor features (unit testing):
13187 - Add command-line arguments to unit-test executable so that we can
13188 invoke any chosen test from the command line rather than having
13189 to run the whole test suite at once; and so that we can turn on
13190 logging for the unit tests.
13192 o Minor bugfixes (on 0.1.2.x):
13193 - If we require CookieAuthentication but we fail to write the
13194 cookie file, we would warn but not exit, and end up in a state
13195 where no controller could authenticate. Now we exit.
13196 - If we require CookieAuthentication, stop generating a new cookie
13197 every time we change any piece of our config.
13198 - When loading bandwidth history, do not believe any information in
13199 the future. Fixes bug 434.
13200 - When loading entry guard information, do not believe any information
13202 - When we have our clock set far in the future and generate an
13203 onion key, then re-set our clock to be correct, we should not stop
13204 the onion key from getting rotated.
13205 - Clean up torrc sample config file.
13206 - Do not automatically run configure from autogen.sh. This
13207 non-standard behavior tended to annoy people who have built other
13210 o Minor bugfixes (on 0.2.0.x):
13211 - Fix a bug with AutomapHostsOnResolve that would always cause
13212 the second request to fail. Bug reported by Kate. Bugfix on
13214 - Fix a bug in ADDRMAP controller replies that would sometimes
13215 try to print a NULL. Patch from tup.
13216 - Read v3 directory authority keys from the right location.
13217 - Numerous bugfixes to directory voting code.
13220 Changes in version 0.1.2.16 - 2007-08-01
13221 Tor 0.1.2.16 fixes a critical security vulnerability that allows a
13222 remote attacker in certain situations to rewrite the user's torrc
13223 configuration file. This can completely compromise anonymity of users
13224 in most configurations, including those running the Vidalia bundles,
13225 TorK, etc. Or worse.
13227 o Major security fixes:
13228 - Close immediately after missing authentication on control port;
13229 do not allow multiple authentication attempts.
13232 Changes in version 0.2.0.4-alpha - 2007-08-01
13233 This fourth development snapshot fixes a critical security vulnerability
13234 for most users, specifically those running Vidalia, TorK, etc. Everybody
13235 should upgrade to either 0.1.2.16 or 0.2.0.4-alpha.
13237 o Major security fixes:
13238 - Close immediately after missing authentication on control port;
13239 do not allow multiple authentication attempts.
13241 o Major bugfixes (compilation):
13242 - Fix win32 compilation: apparently IN_ADDR and IN6_ADDR are already
13245 o Minor features (performance):
13246 - Be even more aggressive about releasing RAM from small
13247 empty buffers. Thanks to our free-list code, this shouldn't be too
13248 performance-intensive.
13249 - Disable sentinel-based debugging for buffer code: we squashed all
13250 the bugs that this was supposed to detect a long time ago, and
13251 now its only effect is to change our buffer sizes from nice
13252 powers of two (which platform mallocs tend to like) to values
13253 slightly over powers of two (which make some platform mallocs sad).
13254 - Log malloc statistics from mallinfo() on platforms where it
13258 Changes in version 0.2.0.3-alpha - 2007-07-29
13259 This third development snapshot introduces new experimental
13260 blocking-resistance features and a preliminary version of the v3
13261 directory voting design, and includes many other smaller features
13265 - The first pieces of our "bridge" design for blocking-resistance
13266 are implemented. People can run bridge directory authorities;
13267 people can run bridges; and people can configure their Tor clients
13268 with a set of bridges to use as the first hop into the Tor network.
13269 See http://archives.seul.org/or/talk/Jul-2007/msg00249.html for
13271 - Create listener connections before we setuid to the configured
13272 User and Group. Now non-Windows users can choose port values
13273 under 1024, start Tor as root, and have Tor bind those ports
13274 before it changes to another UID. (Windows users could already
13276 - Added a new ConstrainedSockets config option to set SO_SNDBUF and
13277 SO_RCVBUF on TCP sockets. Hopefully useful for Tor servers running
13278 on "vserver" accounts. (Patch from coderman.)
13279 - Be even more aggressive about separating local traffic from relayed
13280 traffic when RelayBandwidthRate is set. (Refines proposal 111.)
13282 o Major features (experimental):
13283 - First cut of code for "v3 dir voting": directory authorities will
13284 vote on a common network status document rather than each publishing
13285 their own opinion. This code needs more testing and more corner-case
13286 handling before it's ready for use.
13289 - Directory authorities now call routers Fast if their bandwidth is
13290 at least 100KB/s, and consider their bandwidth adequate to be a
13291 Guard if it is at least 250KB/s, no matter the medians. This fix
13292 complements proposal 107. [Bugfix on 0.1.2.x]
13293 - Directory authorities now never mark more than 3 servers per IP as
13294 Valid and Running. (Implements proposal 109, by Kevin Bauer and
13296 - Minor change to organizationName and commonName generation
13297 procedures in TLS certificates during Tor handshakes, to invalidate
13298 some earlier censorware approaches. This is not a long-term
13299 solution, but applying it will give us a bit of time to look into
13300 the epidemiology of countermeasures as they spread.
13302 o Major bugfixes (directory):
13303 - Rewrite directory tokenization code to never run off the end of
13304 a string. Fixes bug 455. Patch from croup. [Bugfix on 0.1.2.x]
13306 o Minor features (controller):
13307 - Add a SOURCE_ADDR field to STREAM NEW events so that controllers can
13308 match requests to applications. (Patch from Robert Hogan.)
13309 - Report address and port correctly on connections to DNSPort. (Patch
13310 from Robert Hogan.)
13311 - Add a RESOLVE command to launch hostname lookups. (Original patch
13312 from Robert Hogan.)
13313 - Add GETINFO status/enough-dir-info to let controllers tell whether
13314 Tor has downloaded sufficient directory information. (Patch
13316 - You can now use the ControlSocket option to tell Tor to listen for
13317 controller connections on Unix domain sockets on systems that
13318 support them. (Patch from Peter Palfrader.)
13319 - STREAM NEW events are generated for DNSPort requests and for
13320 tunneled directory connections. (Patch from Robert Hogan.)
13321 - New "GETINFO address-mappings/*" command to get address mappings
13322 with expiry information. "addr-mappings/*" is now deprecated.
13325 o Minor features (misc):
13326 - Merge in some (as-yet-unused) IPv6 address manipulation code. (Patch
13328 - The tor-gencert tool for v3 directory authorities now creates all
13329 files as readable to the file creator only, and write-protects
13330 the authority identity key.
13331 - When dumping memory usage, list bytes used in buffer memory
13333 - When running with dmalloc, dump more stats on hup and on exit.
13334 - Directory authorities now fail quickly and (relatively) harmlessly
13335 if they generate a network status document that is somehow
13338 o Traffic load balancing improvements:
13339 - If exit bandwidth ever exceeds one third of total bandwidth, then
13340 use the correct formula to weight exit nodes when choosing paths.
13341 (Based on patch from Mike Perry.)
13342 - Choose perfectly fairly among routers when choosing by bandwidth and
13343 weighting by fraction of bandwidth provided by exits. Previously, we
13344 would choose with only approximate fairness, and correct ourselves
13345 if we ran off the end of the list. [Bugfix on 0.1.2.x]
13347 o Performance improvements:
13348 - Be more aggressive with freeing buffer RAM or putting it on the
13350 - Use Critical Sections rather than Mutexes for synchronizing threads
13351 on win32; Mutexes are heavier-weight, and designed for synchronizing
13354 o Deprecated and removed features:
13355 - RedirectExits is now deprecated.
13356 - Stop allowing address masks that do not correspond to bit prefixes.
13357 We have warned about these for a really long time; now it's time
13358 to reject them. (Patch from croup.)
13360 o Minor bugfixes (directory):
13361 - Fix another crash bug related to extra-info caching. (Bug found by
13362 Peter Palfrader.) [Bugfix on 0.2.0.2-alpha]
13363 - Directories no longer return a "304 not modified" when they don't
13364 have the networkstatus the client asked for. Also fix a memory
13365 leak when returning 304 not modified. [Bugfixes on 0.2.0.2-alpha]
13366 - We had accidentally labelled 0.1.2.x directory servers as not
13367 suitable for begin_dir requests, and had labelled no directory
13368 servers as suitable for uploading extra-info documents. [Bugfix
13371 o Minor bugfixes (dns):
13372 - Fix a crash when DNSPort is set more than once. (Patch from Robert
13373 Hogan.) [Bugfix on 0.2.0.2-alpha]
13374 - Add DNSPort connections to the global connection list, so that we
13375 can time them out correctly. (Bug found by Robert Hogan.) [Bugfix
13377 - Fix a dangling reference that could lead to a crash when DNSPort is
13378 changed or closed (Patch from Robert Hogan.) [Bugfix on
13381 o Minor bugfixes (controller):
13382 - Provide DNS expiry times in GMT, not in local time. For backward
13383 compatibility, ADDRMAP events only provide GMT expiry in an extended
13384 field. "GETINFO address-mappings" always does the right thing.
13385 - Use CRLF line endings properly in NS events.
13386 - Terminate multi-line control events properly. (Original patch
13387 from tup.) [Bugfix on 0.1.2.x-alpha]
13388 - Do not include spaces in SOURCE_ADDR fields in STREAM
13389 events. Resolves bug 472. [Bugfix on 0.2.0.x-alpha]
13392 Changes in version 0.1.2.15 - 2007-07-17
13393 Tor 0.1.2.15 fixes several crash bugs, fixes some anonymity-related
13394 problems, fixes compilation on BSD, and fixes a variety of other
13395 bugs. Everybody should upgrade.
13397 o Major bugfixes (compilation):
13398 - Fix compile on FreeBSD/NetBSD/OpenBSD. Oops.
13400 o Major bugfixes (crashes):
13401 - Try even harder not to dereference the first character after
13402 an mmap(). Reported by lodger.
13403 - Fix a crash bug in directory authorities when we re-number the
13404 routerlist while inserting a new router.
13405 - When the cached-routers file is an even multiple of the page size,
13406 don't run off the end and crash. (Fixes bug 455; based on idea
13408 - Fix eventdns.c behavior on Solaris: It is critical to include
13409 orconfig.h _before_ sys/types.h, so that we can get the expected
13410 definition of _FILE_OFFSET_BITS.
13412 o Major bugfixes (security):
13413 - Fix a possible buffer overrun when using BSD natd support. Bug
13415 - When sending destroy cells from a circuit's origin, don't include
13416 the reason for tearing down the circuit. The spec says we didn't,
13417 and now we actually don't. Reported by lodger.
13418 - Keep streamids from different exits on a circuit separate. This
13419 bug may have allowed other routers on a given circuit to inject
13420 cells into streams. Reported by lodger; fixes bug 446.
13421 - If there's a never-before-connected-to guard node in our list,
13422 never choose any guards past it. This way we don't expand our
13423 guard list unless we need to.
13425 o Minor bugfixes (guard nodes):
13426 - Weight guard selection by bandwidth, so that low-bandwidth nodes
13427 don't get overused as guards.
13429 o Minor bugfixes (directory):
13430 - Correctly count the number of authorities that recommend each
13431 version. Previously, we were under-counting by 1.
13432 - Fix a potential crash bug when we load many server descriptors at
13433 once and some of them make others of them obsolete. Fixes bug 458.
13435 o Minor bugfixes (hidden services):
13436 - Stop tearing down the whole circuit when the user asks for a
13437 connection to a port that the hidden service didn't configure.
13440 o Minor bugfixes (misc):
13441 - On Windows, we were preventing other processes from reading
13442 cached-routers while Tor was running. Reported by janbar.
13443 - Fix a possible (but very unlikely) bug in picking routers by
13444 bandwidth. Add a log message to confirm that it is in fact
13445 unlikely. Patch from lodger.
13446 - Backport a couple of memory leak fixes.
13447 - Backport miscellaneous cosmetic bugfixes.
13450 Changes in version 0.2.0.2-alpha - 2007-06-02
13451 o Major bugfixes on 0.2.0.1-alpha:
13452 - Fix an assertion failure related to servers without extra-info digests.
13453 Resolves bugs 441 and 442.
13455 o Minor features (directory):
13456 - Support "If-Modified-Since" when answering HTTP requests for
13457 directories, running-routers documents, and network-status documents.
13458 (There's no need to support it for router descriptors, since those
13459 are downloaded by descriptor digest.)
13461 o Minor build issues:
13462 - Clear up some MIPSPro compiler warnings.
13463 - When building from a tarball on a machine that happens to have SVK
13464 installed, report the micro-revision as whatever version existed
13465 in the tarball, not as "x".
13468 Changes in version 0.2.0.1-alpha - 2007-06-01
13469 This early development snapshot provides new features for people running
13470 Tor as both a client and a server (check out the new RelayBandwidth
13471 config options); lets Tor run as a DNS proxy; and generally moves us
13472 forward on a lot of fronts.
13474 o Major features, server usability:
13475 - New config options RelayBandwidthRate and RelayBandwidthBurst:
13476 a separate set of token buckets for relayed traffic. Right now
13477 relayed traffic is defined as answers to directory requests, and
13478 OR connections that don't have any local circuits on them.
13480 o Major features, client usability:
13481 - A client-side DNS proxy feature to replace the need for
13482 dns-proxy-tor: Just set "DNSPort 9999", and Tor will now listen
13483 for DNS requests on port 9999, use the Tor network to resolve them
13484 anonymously, and send the reply back like a regular DNS server.
13485 The code still only implements a subset of DNS.
13486 - Make PreferTunneledDirConns and TunnelDirConns work even when
13487 we have no cached directory info. This means Tor clients can now
13488 do all of their connections protected by TLS.
13490 o Major features, performance and efficiency:
13491 - Directory authorities accept and serve "extra info" documents for
13492 routers. These documents contain fields from router descriptors
13493 that aren't usually needed, and that use a lot of excess
13494 bandwidth. Once these fields are removed from router descriptors,
13495 the bandwidth savings should be about 60%. [Partially implements
13497 - Servers upload extra-info documents to any authority that accepts
13498 them. Authorities (and caches that have been configured to download
13499 extra-info documents) download them as needed. [Partially implements
13501 - Change the way that Tor buffers data that it is waiting to write.
13502 Instead of queueing data cells in an enormous ring buffer for each
13503 client->OR or OR->OR connection, we now queue cells on a separate
13504 queue for each circuit. This lets us use less slack memory, and
13505 will eventually let us be smarter about prioritizing different kinds
13507 - Use memory pools to allocate cells with better speed and memory
13508 efficiency, especially on platforms where malloc() is inefficient.
13509 - Stop reading on edge connections when their corresponding circuit
13510 buffers are full; start again as the circuits empty out.
13512 o Major features, other:
13513 - Add an HSAuthorityRecordStats option that hidden service authorities
13514 can use to track statistics of overall hidden service usage without
13515 logging information that would be very useful to an attacker.
13516 - Start work implementing multi-level keys for directory authorities:
13517 Add a standalone tool to generate key certificates. (Proposal 103.)
13520 - Directory authorities now call routers Stable if they have an
13521 uptime of at least 30 days, even if that's not the median uptime
13522 in the network. Implements proposal 107, suggested by Kevin Bauer
13525 o Minor fixes (resource management):
13526 - Count the number of open sockets separately from the number
13527 of active connection_t objects. This will let us avoid underusing
13528 our allocated connection limit.
13529 - We no longer use socket pairs to link an edge connection to an
13530 anonymous directory connection or a DirPort test connection.
13531 Instead, we track the link internally and transfer the data
13532 in-process. This saves two sockets per "linked" connection (at the
13533 client and at the server), and avoids the nasty Windows socketpair()
13535 - Keep unused 4k and 16k buffers on free lists, rather than wasting 8k
13536 for every single inactive connection_t. Free items from the
13537 4k/16k-buffer free lists when they haven't been used for a while.
13539 o Minor features (build):
13540 - Make autoconf search for libevent, openssl, and zlib consistently.
13541 - Update deprecated macros in configure.in.
13542 - When warning about missing headers, tell the user to let us
13543 know if the compile succeeds anyway, so we can downgrade the
13545 - Include the current subversion revision as part of the version
13546 string: either fetch it directly if we're in an SVN checkout, do
13547 some magic to guess it if we're in an SVK checkout, or use
13548 the last-detected version if we're building from a .tar.gz.
13549 Use this version consistently in log messages.
13551 o Minor features (logging):
13552 - Always prepend "Bug: " to any log message about a bug.
13553 - Put a platform string (e.g. "Linux i686") in the startup log
13554 message, so when people paste just their logs, we know if it's
13555 OpenBSD or Windows or what.
13556 - When logging memory usage, break down memory used in buffers by
13559 o Minor features (directory system):
13560 - New config option V2AuthoritativeDirectory that all directory
13561 authorities should set. This will let future authorities choose
13562 not to serve V2 directory information.
13563 - Directory authorities allow multiple router descriptors and/or extra
13564 info documents to be uploaded in a single go. This will make
13565 implementing proposal 104 simpler.
13567 o Minor features (controller):
13568 - Add a new config option __DisablePredictedCircuits designed for
13569 use by the controller, when we don't want Tor to build any circuits
13571 - Let the controller specify HOP=%d as an argument to ATTACHSTREAM,
13572 so we can exit from the middle of the circuit.
13573 - Implement "getinfo status/circuit-established".
13574 - Implement "getinfo status/version/..." so a controller can tell
13575 whether the current version is recommended, and whether any versions
13576 are good, and how many authorities agree. (Patch from shibz.)
13578 o Minor features (hidden services):
13579 - Allow multiple HiddenServicePort directives with the same virtual
13580 port; when they occur, the user is sent round-robin to one
13581 of the target ports chosen at random. Partially fixes bug 393 by
13582 adding limited ad-hoc round-robining.
13584 o Minor features (other):
13586 - Add a new AutomapHostsOnResolve option: when it is enabled, any
13587 resolve request for hosts matching a given pattern causes Tor to
13588 generate an internal virtual address mapping for that host. This
13589 allows DNSPort to work sensibly with hidden service users. By
13590 default, .exit and .onion addresses are remapped; the list of
13591 patterns can be reconfigured with AutomapHostsSuffixes.
13592 - Add an "-F" option to tor-resolve to force a resolve for a .onion
13593 address. Thanks to the AutomapHostsOnResolve option, this is no
13594 longer a completely silly thing to do.
13595 - If Tor is invoked from something that isn't a shell (e.g. Vidalia),
13596 now we expand "-f ~/.tor/torrc" correctly. Suggested by Matt Edman.
13597 - Treat "2gb" when given in torrc for a bandwidth as meaning 2gb,
13598 minus 1 byte: the actual maximum declared bandwidth.
13600 o Removed features:
13601 - Removed support for the old binary "version 0" controller protocol.
13602 This has been deprecated since 0.1.1, and warnings have been issued
13603 since 0.1.2. When we encounter a v0 control message, we now send
13604 back an error and close the connection.
13605 - Remove the old "dns worker" server DNS code: it hasn't been default
13606 since 0.1.2.2-alpha, and all the servers seem to be using the new
13609 o Minor bugfixes (portability):
13610 - Even though Windows is equally happy with / and \ as path separators,
13611 try to use \ consistently on Windows and / consistently on Unix: it
13612 makes the log messages nicer.
13613 - Correctly report platform name on Windows 95 OSR2 and Windows 98 SE.
13614 - Read resolv.conf files correctly on platforms where read() returns
13615 partial results on small file reads.
13617 o Minor bugfixes (directory):
13618 - Correctly enforce that elements of directory objects do not appear
13619 more often than they are allowed to appear.
13620 - When we are reporting the DirServer line we just parsed, we were
13621 logging the second stanza of the key fingerprint, not the first.
13623 o Minor bugfixes (logging):
13624 - When we hit an EOF on a log (probably because we're shutting down),
13625 don't try to remove the log from the list: just mark it as
13626 unusable. (Bulletproofs against bug 222.)
13628 o Minor bugfixes (other):
13629 - In the exitlist script, only consider the most recently published
13630 server descriptor for each server. Also, when the user requests
13631 a list of servers that _reject_ connections to a given address,
13632 explicitly exclude the IPs that also have servers that accept
13633 connections to that address. (Resolves bug 405.)
13634 - Stop allowing hibernating servers to be "stable" or "fast".
13635 - On Windows, we were preventing other processes from reading
13636 cached-routers while Tor was running. (Reported by janbar)
13637 - Make the NodeFamilies config option work. (Reported by
13638 lodger -- it has never actually worked, even though we added it
13640 - Check return values from pthread_mutex functions.
13641 - Don't save non-general-purpose router descriptors to the disk cache,
13642 because we have no way of remembering what their purpose was when
13644 - Add even more asserts to hunt down bug 417.
13645 - Build without verbose warnings even on (not-yet-released) gcc 4.2.
13646 - Fix a possible (but very unlikely) bug in picking routers by bandwidth.
13647 Add a log message to confirm that it is in fact unlikely.
13649 o Minor bugfixes (controller):
13650 - Make 'getinfo fingerprint' return a 551 error if we're not a
13651 server, so we match what the control spec claims we do. Reported
13653 - Fix a typo in an error message when extendcircuit fails that
13654 caused us to not follow the \r\n-based delimiter protocol. Reported
13657 o Code simplifications and refactoring:
13658 - Stop passing around circuit_t and crypt_path_t pointers that are
13659 implicit in other procedure arguments.
13660 - Drop the old code to choke directory connections when the
13661 corresponding OR connections got full: thanks to the cell queue
13662 feature, OR conns don't get full any more.
13663 - Make dns_resolve() handle attaching connections to circuits
13664 properly, so the caller doesn't have to.
13665 - Rename wants_to_read and wants_to_write to read/write_blocked_on_bw.
13666 - Keep the connection array as a dynamic smartlist_t, rather than as
13667 a fixed-sized array. This is important, as the number of connections
13668 is becoming increasingly decoupled from the number of sockets.
13671 Changes in version 0.1.2.14 - 2007-05-25
13672 Tor 0.1.2.14 changes the addresses of two directory authorities (this
13673 change especially affects those who serve or use hidden services),
13674 and fixes several other crash- and security-related bugs.
13676 o Directory authority changes:
13677 - Two directory authorities (moria1 and moria2) just moved to new
13678 IP addresses. This change will particularly affect those who serve
13679 or use hidden services.
13681 o Major bugfixes (crashes):
13682 - If a directory server runs out of space in the connection table
13683 as it's processing a begin_dir request, it will free the exit stream
13684 but leave it attached to the circuit, leading to unpredictable
13685 behavior. (Reported by seeess, fixes bug 425.)
13686 - Fix a bug in dirserv_remove_invalid() that would cause authorities
13687 to corrupt memory under some really unlikely scenarios.
13688 - Tighten router parsing rules. (Bugs reported by Benedikt Boss.)
13689 - Avoid segfaults when reading from mmaped descriptor file. (Reported
13692 o Major bugfixes (security):
13693 - When choosing an entry guard for a circuit, avoid using guards
13694 that are in the same family as the chosen exit -- not just guards
13695 that are exactly the chosen exit. (Reported by lodger.)
13697 o Major bugfixes (resource management):
13698 - If a directory authority is down, skip it when deciding where to get
13699 networkstatus objects or descriptors. Otherwise we keep asking
13700 every 10 seconds forever. Fixes bug 384.
13701 - Count it as a failure if we fetch a valid network-status but we
13702 don't want to keep it. Otherwise we'll keep fetching it and keep
13703 not wanting to keep it. Fixes part of bug 422.
13704 - If all of our dirservers have given us bad or no networkstatuses
13705 lately, then stop hammering them once per minute even when we
13706 think they're failed. Fixes another part of bug 422.
13709 - Actually set the purpose correctly for descriptors inserted with
13710 purpose=controller.
13711 - When we have k non-v2 authorities in our DirServer config,
13712 we ignored the last k authorities in the list when updating our
13714 - Correctly back-off from requesting router descriptors that we are
13715 having a hard time downloading.
13716 - Read resolv.conf files correctly on platforms where read() returns
13717 partial results on small file reads.
13718 - Don't rebuild the entire router store every time we get 32K of
13719 routers: rebuild it when the journal gets very large, or when
13720 the gaps in the store get very large.
13723 - When routers publish SVN revisions in their router descriptors,
13724 authorities now include those versions correctly in networkstatus
13726 - Warn when using a version of libevent before 1.3b to run a server on
13727 OSX or BSD: these versions interact badly with userspace threads.
13730 Changes in version 0.1.2.13 - 2007-04-24
13731 This release features some major anonymity fixes, such as safer path
13732 selection; better client performance; faster bootstrapping, better
13733 address detection, and better DNS support for servers; write limiting as
13734 well as read limiting to make servers easier to run; and a huge pile of
13735 other features and bug fixes. The bundles also ship with Vidalia 0.0.11.
13737 Tor 0.1.2.13 is released in memory of Rob Levin (1955-2006), aka lilo
13738 of the Freenode IRC network, remembering his patience and vision for
13739 free speech on the Internet.
13742 - Fix a memory leak when we ask for "all" networkstatuses and we
13743 get one we don't recognize.
13744 - Add more asserts to hunt down bug 417.
13745 - Disable kqueue on OS X 10.3 and earlier, to fix bug 371.
13748 Changes in version 0.1.2.12-rc - 2007-03-16
13750 - Fix an infinite loop introduced in 0.1.2.7-alpha when we serve
13751 directory information requested inside Tor connections (i.e. via
13752 begin_dir cells). It only triggered when the same connection was
13753 serving other data at the same time. Reported by seeess.
13756 - When creating a circuit via the controller, send a 'launched'
13757 event when we're done, so we follow the spec better.
13760 Changes in version 0.1.2.11-rc - 2007-03-15
13761 o Minor bugfixes (controller), reported by daejees:
13762 - Correct the control spec to match how the code actually responds
13763 to 'getinfo addr-mappings/*'.
13764 - The control spec described a GUARDS event, but the code
13765 implemented a GUARD event. Standardize on GUARD, but let people
13766 ask for GUARDS too.
13769 Changes in version 0.1.2.10-rc - 2007-03-07
13770 o Major bugfixes (Windows):
13771 - Do not load the NT services library functions (which may not exist)
13772 just to detect if we're a service trying to shut down. Now we run
13773 on Win98 and friends again.
13775 o Minor bugfixes (other):
13776 - Clarify a couple of log messages.
13777 - Fix a misleading socks5 error number.
13780 Changes in version 0.1.2.9-rc - 2007-03-02
13781 o Major bugfixes (Windows):
13782 - On MinGW, use "%I64u" to printf/scanf 64-bit integers, instead
13783 of the usual GCC "%llu". This prevents a bug when saving 64-bit
13784 int configuration values: the high-order 32 bits would get
13785 truncated. In particular, we were being bitten by the default
13786 MaxAdvertisedBandwidth of 128 TB turning into 0. (Fixes bug 400
13787 and maybe also bug 397.)
13789 o Minor bugfixes (performance):
13790 - Use OpenSSL's AES implementation on platforms where it's faster.
13791 This could save us as much as 10% CPU usage.
13793 o Minor bugfixes (server):
13794 - Do not rotate onion key immediately after setting it for the first
13797 o Minor bugfixes (directory authorities):
13798 - Stop calling servers that have been hibernating for a long time
13799 "stable". Also, stop letting hibernating or obsolete servers affect
13800 uptime and bandwidth cutoffs.
13801 - Stop listing hibernating servers in the v1 directory.
13803 o Minor bugfixes (hidden services):
13804 - Upload hidden service descriptors slightly less often, to reduce
13805 load on authorities.
13807 o Minor bugfixes (other):
13808 - Fix an assert that could trigger if a controller quickly set then
13809 cleared EntryNodes. Bug found by Udo van den Heuvel.
13810 - On architectures where sizeof(int)>4, still clamp declarable bandwidth
13812 - Fix a potential race condition in the rpm installer. Found by
13814 - Try to fix eventdns warnings once and for all: do not treat a dns rcode
13815 of 2 as indicating that the server is completely bad; it sometimes
13816 means that the server is just bad for the request in question. (may fix
13817 the last of bug 326.)
13818 - Disable encrypted directory connections when we don't have a server
13819 descriptor for the destination. We'll get this working again in
13823 Changes in version 0.1.2.8-beta - 2007-02-26
13824 o Major bugfixes (crashes):
13825 - Stop crashing when the controller asks us to resetconf more than
13826 one config option at once. (Vidalia 0.0.11 does this.)
13827 - Fix a crash that happened on Win98 when we're given command-line
13828 arguments: don't try to load NT service functions from advapi32.dll
13829 except when we need them. (Bug introduced in 0.1.2.7-alpha;
13831 - Fix a longstanding obscure crash bug that could occur when
13832 we run out of DNS worker processes. (Resolves bug 390.)
13834 o Major bugfixes (hidden services):
13835 - Correctly detect whether hidden service descriptor downloads are
13836 in-progress. (Suggested by Karsten Loesing; fixes bug 399.)
13838 o Major bugfixes (accounting):
13839 - When we start during an accounting interval before it's time to wake
13840 up, remember to wake up at the correct time. (May fix bug 342.)
13842 o Minor bugfixes (controller):
13843 - Give the controller END_STREAM_REASON_DESTROY events _before_ we
13844 clear the corresponding on_circuit variable, and remember later
13845 that we don't need to send a redundant CLOSED event. Resolves part
13847 - Report events where a resolve succeeded or where we got a socks
13848 protocol error correctly, rather than calling both of them
13850 - Change reported stream target addresses to IP consistently when
13851 we finally get the IP from an exit node.
13852 - Send log messages to the controller even if they happen to be very
13855 o Minor bugfixes (other):
13856 - Display correct results when reporting which versions are
13857 recommended, and how recommended they are. (Resolves bug 383.)
13858 - Improve our estimates for directory bandwidth to be less random:
13859 guess that an unrecognized directory will have the average bandwidth
13860 from all known directories, not that it will have the average
13861 bandwidth from those directories earlier than it on the list.
13862 - If we start a server with ClientOnly 1, then set ClientOnly to 0
13863 and hup, stop triggering an assert based on an empty onion_key.
13864 - On platforms with no working mmap() equivalent, don't warn the
13865 user when cached-routers doesn't exist.
13866 - Warn the user when mmap() [or its equivalent] fails for some reason
13867 other than file-not-found.
13868 - Don't warn the user when cached-routers.new doesn't exist: that's
13869 perfectly fine when starting up for the first time.
13870 - When EntryNodes are configured, rebuild the guard list to contain,
13871 in order: the EntryNodes that were guards before; the rest of the
13872 EntryNodes; the nodes that were guards before.
13873 - Mask out all signals in sub-threads; only the libevent signal
13874 handler should be processing them. This should prevent some crashes
13875 on some machines using pthreads. (Patch from coderman.)
13876 - Fix switched arguments on memset in the implementation of
13877 tor_munmap() for systems with no mmap() call.
13878 - When Tor receives a router descriptor that it asked for, but
13879 no longer wants (because it has received fresh networkstatuses
13880 in the meantime), do not warn the user. Cache the descriptor if
13881 we're a cache; drop it if we aren't.
13882 - Make earlier entry guards _really_ get retried when the network
13884 - On a malformed DNS reply, always give an error to the corresponding
13886 - Build with recent libevents on platforms that do not define the
13887 nonstandard types "u_int8_t" and friends.
13889 o Minor features (controller):
13890 - Warn the user when an application uses the obsolete binary v0
13891 control protocol. We're planning to remove support for it during
13892 the next development series, so it's good to give people some
13894 - Add STREAM_BW events to report per-entry-stream bandwidth
13895 use. (Patch from Robert Hogan.)
13896 - Rate-limit SIGNEWNYM signals in response to controllers that
13897 impolitely generate them for every single stream. (Patch from
13898 mwenge; closes bug 394.)
13899 - Make REMAP stream events have a SOURCE (cache or exit), and
13900 make them generated in every case where we get a successful
13901 connected or resolved cell.
13903 o Minor bugfixes (performance):
13904 - Call router_have_min_dir_info half as often. (This is showing up in
13905 some profiles, but not others.)
13906 - When using GCC, make log_debug never get called at all, and its
13907 arguments never get evaluated, when no debug logs are configured.
13908 (This is showing up in some profiles, but not others.)
13911 - Remove some never-implemented options. Mark PathlenCoinWeight as
13913 - Implement proposal 106: Stop requiring clients to have well-formed
13914 certificates; stop checking nicknames in certificates. (Clients
13915 have certificates so that they can look like Tor servers, but in
13916 the future we might want to allow them to look like regular TLS
13917 clients instead. Nicknames in certificates serve no purpose other
13918 than making our protocol easier to recognize on the wire.)
13919 - Revise messages on handshake failure again to be even more clear about
13920 which are incoming connections and which are outgoing.
13921 - Discard any v1 directory info that's over 1 month old (for
13922 directories) or over 1 week old (for running-routers lists).
13923 - Do not warn when individual nodes in the configuration's EntryNodes,
13924 ExitNodes, etc are down: warn only when all possible nodes
13925 are down. (Fixes bug 348.)
13926 - Always remove expired routers and networkstatus docs before checking
13927 whether we have enough information to build circuits. (Fixes
13929 - Put a lower-bound on MaxAdvertisedBandwidth.
13932 Changes in version 0.1.2.7-alpha - 2007-02-06
13933 o Major bugfixes (rate limiting):
13934 - Servers decline directory requests much more aggressively when
13935 they're low on bandwidth. Otherwise they end up queueing more and
13936 more directory responses, which can't be good for latency.
13937 - But never refuse directory requests from local addresses.
13938 - Fix a memory leak when sending a 503 response for a networkstatus
13940 - Be willing to read or write on local connections (e.g. controller
13941 connections) even when the global rate limiting buckets are empty.
13942 - If our system clock jumps back in time, don't publish a negative
13943 uptime in the descriptor. Also, don't let the global rate limiting
13944 buckets go absurdly negative.
13945 - Flush local controller connection buffers periodically as we're
13946 writing to them, so we avoid queueing 4+ megabytes of data before
13949 o Major bugfixes (NT services):
13950 - Install as NT_AUTHORITY\LocalService rather than as SYSTEM; add a
13951 command-line flag so that admins can override the default by saying
13952 "tor --service install --user "SomeUser"". This will not affect
13953 existing installed services. Also, warn the user that the service
13954 will look for its configuration file in the service user's
13955 %appdata% directory. (We can't do the 'hardwire the user's appdata
13956 directory' trick any more, since we may not have read access to that
13959 o Major bugfixes (other):
13960 - Previously, we would cache up to 16 old networkstatus documents
13961 indefinitely, if they came from nontrusted authorities. Now we
13962 discard them if they are more than 10 days old.
13963 - Fix a crash bug in the presence of DNS hijacking (reported by Andrew
13965 - Detect and reject malformed DNS responses containing circular
13967 - If exits are rare enough that we're not marking exits as guards,
13968 ignore exit bandwidth when we're deciding the required bandwidth
13970 - When we're handling a directory connection tunneled over Tor,
13971 don't fill up internal memory buffers with all the data we want
13972 to tunnel; instead, only add it if the OR connection that will
13973 eventually receive it has some room for it. (This can lead to
13974 slowdowns in tunneled dir connections; a better solution will have
13975 to wait for 0.2.0.)
13977 o Minor bugfixes (dns):
13978 - Add some defensive programming to eventdns.c in an attempt to catch
13979 possible memory-stomping bugs.
13980 - Detect and reject DNS replies containing IPv4 or IPv6 records with
13981 an incorrect number of bytes. (Previously, we would ignore the
13983 - Fix as-yet-unused reverse IPv6 lookup code so it sends nybbles
13984 in the correct order, and doesn't crash.
13985 - Free memory held in recently-completed DNS lookup attempts on exit.
13986 This was not a memory leak, but may have been hiding memory leaks.
13987 - Handle TTL values correctly on reverse DNS lookups.
13988 - Treat failure to parse resolv.conf as an error.
13990 o Minor bugfixes (other):
13991 - Fix crash with "tor --list-fingerprint" (reported by seeess).
13992 - When computing clock skew from directory HTTP headers, consider what
13993 time it was when we finished asking for the directory, not what
13995 - Expire socks connections if they spend too long waiting for the
13996 handshake to finish. Previously we would let them sit around for
13997 days, if the connecting application didn't close them either.
13998 - And if the socks handshake hasn't started, don't send a
13999 "DNS resolve socks failed" handshake reply; just close it.
14000 - Stop using C functions that OpenBSD's linker doesn't like.
14001 - Don't launch requests for descriptors unless we have networkstatuses
14002 from at least half of the authorities. This delays the first
14003 download slightly under pathological circumstances, but can prevent
14004 us from downloading a bunch of descriptors we don't need.
14005 - Do not log IPs with TLS failures for incoming TLS
14006 connections. (Fixes bug 382.)
14007 - If the user asks to use invalid exit nodes, be willing to use
14009 - Stop using the reserved ac_cv namespace in our configure script.
14010 - Call stat() slightly less often; use fstat() when possible.
14011 - Refactor the way we handle pending circuits when an OR connection
14012 completes or fails, in an attempt to fix a rare crash bug.
14013 - Only rewrite a conn's address based on X-Forwarded-For: headers
14014 if it's a parseable public IP address; and stop adding extra quotes
14015 to the resulting address.
14018 - Weight directory requests by advertised bandwidth. Now we can
14019 let servers enable write limiting but still allow most clients to
14020 succeed at their directory requests. (We still ignore weights when
14021 choosing a directory authority; I hope this is a feature.)
14024 - Create a new file ReleaseNotes which was the old ChangeLog. The
14025 new ChangeLog file now includes the summaries for all development
14027 - Check for addresses with invalid characters at the exit as well
14028 as at the client, and warn less verbosely when they fail. You can
14029 override this by setting ServerDNSAllowNonRFC953Addresses to 1.
14030 - Adapt a patch from goodell to let the contrib/exitlist script
14031 take arguments rather than require direct editing.
14032 - Inform the server operator when we decide not to advertise a
14033 DirPort due to AccountingMax enabled or a low BandwidthRate. It
14034 was confusing Zax, so now we're hopefully more helpful.
14035 - Bring us one step closer to being able to establish an encrypted
14036 directory tunnel without knowing a descriptor first. Still not
14037 ready yet. As part of the change, now assume we can use a
14038 create_fast cell if we don't know anything about a router.
14039 - Allow exit nodes to use nameservers running on ports other than 53.
14040 - Servers now cache reverse DNS replies.
14041 - Add an --ignore-missing-torrc command-line option so that we can
14042 get the "use sensible defaults if the configuration file doesn't
14043 exist" behavior even when specifying a torrc location on the command
14046 o Minor features (controller):
14047 - Track reasons for OR connection failure; make these reasons
14048 available via the controller interface. (Patch from Mike Perry.)
14049 - Add a SOCKS_BAD_HOSTNAME client status event so controllers
14050 can learn when clients are sending malformed hostnames to Tor.
14051 - Clean up documentation for controller status events.
14052 - Add a REMAP status to stream events to note that a stream's
14053 address has changed because of a cached address or a MapAddress
14057 Changes in version 0.1.2.6-alpha - 2007-01-09
14059 - Fix an assert error introduced in 0.1.2.5-alpha: if a single TLS
14060 connection handles more than 4 gigs in either direction, we crash.
14061 - Fix an assert error introduced in 0.1.2.5-alpha: if we're an
14062 advertised exit node, somebody might try to exit from us when
14063 we're bootstrapping and before we've built our descriptor yet.
14064 Refuse the connection rather than crashing.
14067 - Warn if we (as a server) find that we've resolved an address that we
14068 weren't planning to resolve.
14069 - Warn that using select() on any libevent version before 1.1 will be
14070 unnecessarily slow (even for select()).
14071 - Flush ERR-level controller status events just like we currently
14072 flush ERR-level log events, so that a Tor shutdown doesn't prevent
14073 the controller from learning about current events.
14075 o Minor features (more controller status events):
14076 - Implement EXTERNAL_ADDRESS server status event so controllers can
14077 learn when our address changes.
14078 - Implement BAD_SERVER_DESCRIPTOR server status event so controllers
14079 can learn when directories reject our descriptor.
14080 - Implement SOCKS_UNKNOWN_PROTOCOL client status event so controllers
14081 can learn when a client application is speaking a non-socks protocol
14083 - Implement DANGEROUS_SOCKS client status event so controllers
14084 can learn when a client application is leaking DNS addresses.
14085 - Implement BUG general status event so controllers can learn when
14086 Tor is unhappy about its internal invariants.
14087 - Implement CLOCK_SKEW general status event so controllers can learn
14088 when Tor thinks the system clock is set incorrectly.
14089 - Implement GOOD_SERVER_DESCRIPTOR and ACCEPTED_SERVER_DESCRIPTOR
14090 server status events so controllers can learn when their descriptors
14091 are accepted by a directory.
14092 - Implement CHECKING_REACHABILITY and REACHABILITY_{SUCCEEDED|FAILED}
14093 server status events so controllers can learn about Tor's progress in
14094 deciding whether it's reachable from the outside.
14095 - Implement BAD_LIBEVENT general status event so controllers can learn
14096 when we have a version/method combination in libevent that needs to
14098 - Implement NAMESERVER_STATUS, NAMESERVER_ALL_DOWN, DNS_HIJACKED,
14099 and DNS_USELESS server status events so controllers can learn
14100 about changes to DNS server status.
14102 o Minor features (directory):
14103 - Authorities no longer recommend exits as guards if this would shift
14104 too much load to the exit nodes.
14107 Changes in version 0.1.2.5-alpha - 2007-01-06
14109 - Enable write limiting as well as read limiting. Now we sacrifice
14110 capacity if we're pushing out lots of directory traffic, rather
14111 than overrunning the user's intended bandwidth limits.
14112 - Include TLS overhead when counting bandwidth usage; previously, we
14113 would count only the bytes sent over TLS, but not the bytes used
14115 - Support running the Tor service with a torrc not in the same
14116 directory as tor.exe and default to using the torrc located in
14117 the %appdata%\Tor\ of the user who installed the service. Patch
14119 - Servers now check for the case when common DNS requests are going to
14120 wildcarded addresses (i.e. all getting the same answer), and change
14121 their exit policy to reject *:* if it's happening.
14122 - Implement BEGIN_DIR cells, so we can connect to the directory
14123 server via TLS to do encrypted directory requests rather than
14124 plaintext. Enable via the TunnelDirConns and PreferTunneledDirConns
14125 config options if you like.
14127 o Minor features (config and docs):
14128 - Start using the state file to store bandwidth accounting data:
14129 the bw_accounting file is now obsolete. We'll keep generating it
14130 for a while for people who are still using 0.1.2.4-alpha.
14131 - Try to batch changes to the state file so that we do as few
14132 disk writes as possible while still storing important things in
14134 - The state file and the bw_accounting file get saved less often when
14135 the AvoidDiskWrites config option is set.
14136 - Make PIDFile work on Windows (untested).
14137 - Add internal descriptions for a bunch of configuration options:
14138 accessible via controller interface and in comments in saved
14140 - Reject *:563 (NNTPS) in the default exit policy. We already reject
14141 NNTP by default, so this seems like a sensible addition.
14142 - Clients now reject hostnames with invalid characters. This should
14143 avoid some inadvertent info leaks. Add an option
14144 AllowNonRFC953Hostnames to disable this behavior, in case somebody
14145 is running a private network with hosts called @, !, and #.
14146 - Add a maintainer script to tell us which options are missing
14147 documentation: "make check-docs".
14148 - Add a new address-spec.txt document to describe our special-case
14149 addresses: .exit, .onion, and .noconnnect.
14151 o Minor features (DNS):
14152 - Ongoing work on eventdns infrastructure: now it has dns server
14153 and ipv6 support. One day Tor will make use of it.
14154 - Add client-side caching for reverse DNS lookups.
14155 - Add support to tor-resolve tool for reverse lookups and SOCKS5.
14156 - When we change nameservers or IP addresses, reset and re-launch
14157 our tests for DNS hijacking.
14159 o Minor features (directory):
14160 - Authorities now specify server versions in networkstatus. This adds
14161 about 2% to the size of compressed networkstatus docs, and allows
14162 clients to tell which servers support BEGIN_DIR and which don't.
14163 The implementation is forward-compatible with a proposed future
14164 protocol version scheme not tied to Tor versions.
14165 - DirServer configuration lines now have an orport= option so
14166 clients can open encrypted tunnels to the authorities without
14167 having downloaded their descriptors yet. Enabled for moria1,
14168 moria2, tor26, and lefkada now in the default configuration.
14169 - Directory servers are more willing to send a 503 "busy" if they
14170 are near their write limit, especially for v1 directory requests.
14171 Now they can use their limited bandwidth for actual Tor traffic.
14172 - Clients track responses with status 503 from dirservers. After a
14173 dirserver has given us a 503, we try not to use it until an hour has
14174 gone by, or until we have no dirservers that haven't given us a 503.
14175 - When we get a 503 from a directory, and we're not a server, we don't
14176 count the failure against the total number of failures allowed
14177 for the thing we're trying to download.
14178 - Report X-Your-Address-Is correctly from tunneled directory
14179 connections; don't report X-Your-Address-Is when it's an internal
14180 address; and never believe reported remote addresses when they're
14182 - Protect against an unlikely DoS attack on directory servers.
14183 - Add a BadDirectory flag to network status docs so that authorities
14184 can (eventually) tell clients about caches they believe to be
14187 o Minor features (controller):
14188 - Have GETINFO dir/status/* work on hosts with DirPort disabled.
14189 - Reimplement GETINFO so that info/names stays in sync with the
14191 - Implement "GETINFO fingerprint".
14192 - Implement "SETEVENTS GUARD" so controllers can get updates on
14193 entry guard status as it changes.
14195 o Minor features (clean up obsolete pieces):
14196 - Remove some options that have been deprecated since at least
14197 0.1.0.x: AccountingMaxKB, LogFile, DebugLogFile, LogLevel, and
14198 SysLog. Use AccountingMax instead of AccountingMaxKB, and use Log
14199 to set log options.
14200 - We no longer look for identity and onion keys in "identity.key" and
14201 "onion.key" -- these were replaced by secret_id_key and
14202 secret_onion_key in 0.0.8pre1.
14203 - We no longer require unrecognized directory entries to be
14206 o Major bugfixes (security):
14207 - Stop sending the HttpProxyAuthenticator string to directory
14208 servers when directory connections are tunnelled through Tor.
14209 - Clients no longer store bandwidth history in the state file.
14210 - Do not log introduction points for hidden services if SafeLogging
14212 - When generating bandwidth history, round down to the nearest
14213 1k. When storing accounting data, round up to the nearest 1k.
14214 - When we're running as a server, remember when we last rotated onion
14215 keys, so that we will rotate keys once they're a week old even if
14216 we never stay up for a week ourselves.
14218 o Major bugfixes (other):
14219 - Fix a longstanding bug in eventdns that prevented the count of
14220 timed-out resolves from ever being reset. This bug caused us to
14221 give up on a nameserver the third time it timed out, and try it
14222 10 seconds later... and to give up on it every time it timed out
14224 - Take out the '5 second' timeout from the connection retry
14225 schedule. Now the first connect attempt will wait a full 10
14226 seconds before switching to a new circuit. Perhaps this will help
14227 a lot. Based on observations from Mike Perry.
14228 - Fix a bug on the Windows implementation of tor_mmap_file() that
14229 would prevent the cached-routers file from ever loading. Reported
14233 - Fix an assert failure when a directory authority sets
14234 AuthDirRejectUnlisted and then receives a descriptor from an
14235 unlisted router. Reported by seeess.
14236 - Avoid a double-free when parsing malformed DirServer lines.
14237 - Fix a bug when a BSD-style PF socket is first used. Patch from
14239 - Fix a bug in 0.1.2.2-alpha that prevented clients from asking
14240 to resolve an address at a given exit node even when they ask for
14242 - Servers no longer ever list themselves in their "family" line,
14243 even if configured to do so. This makes it easier to configure
14244 family lists conveniently.
14245 - When running as a server, don't fall back to 127.0.0.1 when no
14246 nameservers are configured in /etc/resolv.conf; instead, make the
14247 user fix resolv.conf or specify nameservers explicitly. (Resolves
14249 - Stop accepting certain malformed ports in configured exit policies.
14250 - Don't re-write the fingerprint file every restart, unless it has
14252 - Stop warning when a single nameserver fails: only warn when _all_ of
14253 our nameservers have failed. Also, when we only have one nameserver,
14254 raise the threshold for deciding that the nameserver is dead.
14255 - Directory authorities now only decide that routers are reachable
14256 if their identity keys are as expected.
14257 - When the user uses bad syntax in the Log config line, stop
14258 suggesting other bad syntax as a replacement.
14259 - Correctly detect ipv6 DNS capability on OpenBSD.
14261 o Minor bugfixes (controller):
14262 - Report the circuit number correctly in STREAM CLOSED events. Bug
14263 reported by Mike Perry.
14264 - Do not report bizarre values for results of accounting GETINFOs
14265 when the last second's write or read exceeds the allotted bandwidth.
14266 - Report "unrecognized key" rather than an empty string when the
14267 controller tries to fetch a networkstatus that doesn't exist.
14270 Changes in version 0.1.1.26 - 2006-12-14
14271 o Security bugfixes:
14272 - Stop sending the HttpProxyAuthenticator string to directory
14273 servers when directory connections are tunnelled through Tor.
14274 - Clients no longer store bandwidth history in the state file.
14275 - Do not log introduction points for hidden services if SafeLogging
14279 - Fix an assert failure when a directory authority sets
14280 AuthDirRejectUnlisted and then receives a descriptor from an
14281 unlisted router (reported by seeess).
14284 Changes in version 0.1.2.4-alpha - 2006-12-03
14286 - Add support for using natd; this allows FreeBSDs earlier than
14287 5.1.2 to have ipfw send connections through Tor without using
14288 SOCKS. (Patch from Zajcev Evgeny with tweaks from tup.)
14291 - Make all connections to addresses of the form ".noconnect"
14292 immediately get closed. This lets application/controller combos
14293 successfully test whether they're talking to the same Tor by
14294 watching for STREAM events.
14295 - Make cross.sh cross-compilation script work even when autogen.sh
14296 hasn't been run. (Patch from Michael Mohr.)
14297 - Statistics dumped by -USR2 now include a breakdown of public key
14298 operations, for profiling.
14301 - Fix a major leak when directory authorities parse their
14302 approved-routers list, a minor memory leak when we fail to pick
14303 an exit node, and a few rare leaks on errors.
14304 - Handle TransPort connections even when the server sends data before
14305 the client sends data. Previously, the connection would just hang
14306 until the client sent data. (Patch from tup based on patch from
14308 - Avoid assert failure when our cached-routers file is empty on
14312 - Don't log spurious warnings when we see a circuit close reason we
14313 don't recognize; it's probably just from a newer version of Tor.
14314 - Have directory authorities allow larger amounts of drift in uptime
14315 without replacing the server descriptor: previously, a server that
14316 restarted every 30 minutes could have 48 "interesting" descriptors
14318 - Start linking to the Tor specification and Tor reference manual
14319 correctly in the Windows installer.
14320 - Add Vidalia to the OS X uninstaller script, so when we uninstall
14321 Tor/Privoxy we also uninstall Vidalia.
14322 - Resume building on Irix64, and fix a lot of warnings from its
14323 MIPSpro C compiler.
14324 - Don't corrupt last_guessed_ip in router_new_address_suggestion()
14325 when we're running as a client.
14328 Changes in version 0.1.1.25 - 2006-11-04
14330 - When a client asks us to resolve (rather than connect to)
14331 an address, and we have a cached answer, give them the cached
14332 answer. Previously, we would give them no answer at all.
14333 - We were building exactly the wrong circuits when we predict
14334 hidden service requirements, meaning Tor would have to build all
14335 its circuits on demand.
14336 - If none of our live entry guards have a high uptime, but we
14337 require a guard with a high uptime, try adding a new guard before
14338 we give up on the requirement. This patch should make long-lived
14339 connections more stable on average.
14340 - When testing reachability of our DirPort, don't launch new
14341 tests when there's already one in progress -- unreachable
14342 servers were stacking up dozens of testing streams.
14344 o Security bugfixes:
14345 - When the user sends a NEWNYM signal, clear the client-side DNS
14346 cache too. Otherwise we continue to act on previous information.
14349 - Avoid a memory corruption bug when creating a hash table for
14351 - Avoid possibility of controller-triggered crash when misusing
14352 certain commands from a v0 controller on platforms that do not
14353 handle printf("%s",NULL) gracefully.
14354 - Avoid infinite loop on unexpected controller input.
14355 - Don't log spurious warnings when we see a circuit close reason we
14356 don't recognize; it's probably just from a newer version of Tor.
14357 - Add Vidalia to the OS X uninstaller script, so when we uninstall
14358 Tor/Privoxy we also uninstall Vidalia.
14361 Changes in version 0.1.2.3-alpha - 2006-10-29
14363 - Prepare for servers to publish descriptors less often: never
14364 discard a descriptor simply for being too old until either it is
14365 recommended by no authorities, or until we get a better one for
14366 the same router. Make caches consider retaining old recommended
14367 routers for even longer.
14368 - If most authorities set a BadExit flag for a server, clients
14369 don't think of it as a general-purpose exit. Clients only consider
14370 authorities that advertise themselves as listing bad exits.
14371 - Directory servers now provide 'Pragma: no-cache' and 'Expires'
14372 headers for content, so that we can work better in the presence of
14373 caching HTTP proxies.
14374 - Allow authorities to list nodes as bad exits by fingerprint or by
14377 o Minor features, controller:
14378 - Add a REASON field to CIRC events; for backward compatibility, this
14379 field is sent only to controllers that have enabled the extended
14380 event format. Also, add additional reason codes to explain why
14381 a given circuit has been destroyed or truncated. (Patches from
14383 - Add a REMOTE_REASON field to extended CIRC events to tell the
14384 controller about why a remote OR told us to close a circuit.
14385 - Stream events also now have REASON and REMOTE_REASON fields,
14386 working much like those for circuit events.
14387 - There's now a GETINFO ns/... field so that controllers can ask Tor
14388 about the current status of a router.
14389 - A new event type "NS" to inform a controller when our opinion of
14390 a router's status has changed.
14391 - Add a GETINFO events/names and GETINFO features/names so controllers
14392 can tell which events and features are supported.
14393 - A new CLEARDNSCACHE signal to allow controllers to clear the
14394 client-side DNS cache without expiring circuits.
14396 o Security bugfixes:
14397 - When the user sends a NEWNYM signal, clear the client-side DNS
14398 cache too. Otherwise we continue to act on previous information.
14401 - Avoid sending junk to controllers or segfaulting when a controller
14402 uses EVENT_NEW_DESC with verbose nicknames.
14403 - Stop triggering asserts if the controller tries to extend hidden
14404 service circuits (reported by mwenge).
14405 - Avoid infinite loop on unexpected controller input.
14406 - When the controller does a "GETINFO network-status", tell it
14407 about even those routers whose descriptors are very old, and use
14408 long nicknames where appropriate.
14409 - Change NT service functions to be loaded on demand. This lets us
14410 build with MinGW without breaking Tor for Windows 98 users.
14411 - Do DirPort reachability tests less often, since a single test
14412 chews through many circuits before giving up.
14413 - In the hidden service example in torrc.sample, stop recommending
14414 esoteric and discouraged hidden service options.
14415 - When stopping an NT service, wait up to 10 sec for it to actually
14416 stop. Patch from Matt Edman; resolves bug 295.
14417 - Fix handling of verbose nicknames with ORCONN controller events:
14418 make them show up exactly when requested, rather than exactly when
14420 - When reporting verbose nicknames in entry_guards_getinfo(), avoid
14421 printing a duplicate "$" in the keys we send (reported by mwenge).
14422 - Correctly set maximum connection limit on Cygwin. (This time
14424 - Try to detect Windows correctly when cross-compiling.
14425 - Detect the size of the routers file correctly even if it is
14426 corrupted (on systems without mmap) or not page-aligned (on systems
14427 with mmap). This bug was harmless.
14428 - Sometimes we didn't bother sending a RELAY_END cell when an attempt
14429 to open a stream fails; now we do in more cases. This should
14430 make clients able to find a good exit faster in some cases, since
14431 unhandleable requests will now get an error rather than timing out.
14432 - Resolve two memory leaks when rebuilding the on-disk router cache
14433 (reported by fookoowa).
14434 - Clean up minor code warnings suggested by the MIPSpro C compiler,
14435 and reported by some Centos users.
14436 - Controller signals now work on non-Unix platforms that don't define
14437 SIGUSR1 and SIGUSR2 the way we expect.
14438 - Patch from Michael Mohr to contrib/cross.sh, so it checks more
14439 values before failing, and always enables eventdns.
14440 - Libevent-1.2 exports, but does not define in its headers, strlcpy.
14441 Try to fix this in configure.in by checking for most functions
14442 before we check for libevent.
14445 Changes in version 0.1.2.2-alpha - 2006-10-07
14447 - Make our async eventdns library on-by-default for Tor servers,
14448 and plan to deprecate the separate dnsworker threads.
14449 - Add server-side support for "reverse" DNS lookups (using PTR
14450 records so clients can determine the canonical hostname for a given
14451 IPv4 address). Only supported by servers using eventdns; servers
14452 now announce in their descriptors whether they support eventdns.
14453 - Specify and implement client-side SOCKS5 interface for reverse DNS
14454 lookups (see doc/socks-extensions.txt).
14455 - Add a BEGIN_DIR relay cell type for an easier in-protocol way to
14456 connect to directory servers through Tor. Previously, clients needed
14457 to find Tor exits to make private connections to directory servers.
14458 - Avoid choosing Exit nodes for entry or middle hops when the
14459 total bandwidth available from non-Exit nodes is much higher than
14460 the total bandwidth available from Exit nodes.
14461 - Workaround for name servers (like Earthlink's) that hijack failing
14462 DNS requests and replace the no-such-server answer with a "helpful"
14463 redirect to an advertising-driven search portal. Also work around
14464 DNS hijackers who "helpfully" decline to hijack known-invalid
14465 RFC2606 addresses. Config option "ServerDNSDetectHijacking 0"
14466 lets you turn it off.
14467 - Send out a burst of long-range padding cells once we've established
14468 that we're reachable. Spread them over 4 circuits, so hopefully
14469 a few will be fast. This exercises our bandwidth and bootstraps
14470 us into the directory more quickly.
14472 o New/improved config options:
14473 - Add new config option "ResolvConf" to let the server operator
14474 choose an alternate resolve.conf file when using eventdns.
14475 - Add an "EnforceDistinctSubnets" option to control our "exclude
14476 servers on the same /16" behavior. It's still on by default; this
14477 is mostly for people who want to operate private test networks with
14478 all the machines on the same subnet.
14479 - If one of our entry guards is on the ExcludeNodes list, or the
14480 directory authorities don't think it's a good guard, treat it as
14481 if it were unlisted: stop using it as a guard, and throw it off
14482 the guards list if it stays that way for a long time.
14483 - Allow directory authorities to be marked separately as authorities
14484 for the v1 directory protocol, the v2 directory protocol, and
14485 as hidden service directories, to make it easier to retire old
14486 authorities. V1 authorities should set "HSAuthoritativeDir 1"
14487 to continue being hidden service authorities too.
14488 - Remove 8888 as a LongLivedPort, and add 6697 (IRCS).
14490 o Minor features, controller:
14491 - Fix CIRC controller events so that controllers can learn the
14492 identity digests of non-Named servers used in circuit paths.
14493 - Let controllers ask for more useful identifiers for servers. Instead
14494 of learning identity digests for un-Named servers and nicknames
14495 for Named servers, the new identifiers include digest, nickname,
14496 and indication of Named status. Off by default; see control-spec.txt
14497 for more information.
14498 - Add a "getinfo address" controller command so it can display Tor's
14499 best guess to the user.
14500 - New controller event to alert the controller when our server
14501 descriptor has changed.
14502 - Give more meaningful errors on controller authentication failure.
14504 o Minor features, other:
14505 - When asked to resolve a hostname, don't use non-exit servers unless
14506 requested to do so. This allows servers with broken DNS to be
14507 useful to the network.
14508 - Divide eventdns log messages into warn and info messages.
14509 - Reserve the nickname "Unnamed" for routers that can't pick
14510 a hostname: any router can call itself Unnamed; directory
14511 authorities will never allocate Unnamed to any particular router;
14512 clients won't believe that any router is the canonical Unnamed.
14513 - Only include function names in log messages for info/debug messages.
14514 For notice/warn/err, the content of the message should be clear on
14515 its own, and printing the function name only confuses users.
14516 - Avoid some false positives during reachability testing: don't try
14517 to test via a server that's on the same /24 as us.
14518 - If we fail to build a circuit to an intended enclave, and it's
14519 not mandatory that we use that enclave, stop wanting it.
14520 - When eventdns is enabled, allow multithreaded builds on NetBSD and
14521 OpenBSD. (We had previously disabled threads on these platforms
14522 because they didn't have working thread-safe resolver functions.)
14524 o Major bugfixes, anonymity/security:
14525 - If a client asked for a server by name, and there's a named server
14526 in our network-status but we don't have its descriptor yet, we
14527 could return an unnamed server instead.
14528 - Fix NetBSD bug that could allow someone to force uninitialized RAM
14529 to be sent to a server's DNS resolver. This only affects NetBSD
14530 and other platforms that do not bounds-check tolower().
14531 - Reject (most) attempts to use Tor circuits with length one. (If
14532 many people start using Tor as a one-hop proxy, exit nodes become
14533 a more attractive target for compromise.)
14534 - Just because your DirPort is open doesn't mean people should be
14535 able to remotely teach you about hidden service descriptors. Now
14536 only accept rendezvous posts if you've got HSAuthoritativeDir set.
14538 o Major bugfixes, other:
14539 - Don't crash on race condition in dns.c: tor_assert(!resolve->expire)
14540 - When a client asks the server to resolve (not connect to)
14541 an address, and it has a cached answer, give them the cached answer.
14542 Previously, the server would give them no answer at all.
14543 - Allow really slow clients to not hang up five minutes into their
14544 directory downloads (suggested by Adam J. Richter).
14545 - We were building exactly the wrong circuits when we anticipated
14546 hidden service requirements, meaning Tor would have to build all
14547 its circuits on demand.
14548 - Avoid crashing when we mmap a router cache file of size 0.
14549 - When testing reachability of our DirPort, don't launch new
14550 tests when there's already one in progress -- unreachable
14551 servers were stacking up dozens of testing streams.
14553 o Minor bugfixes, correctness:
14554 - If we're a directory mirror and we ask for "all" network status
14555 documents, we would discard status documents from authorities
14556 we don't recognize.
14557 - Avoid a memory corruption bug when creating a hash table for
14559 - Avoid controller-triggered crash when misusing certain commands
14560 from a v0 controller on platforms that do not handle
14561 printf("%s",NULL) gracefully.
14562 - Don't crash when a controller sends a third argument to an
14563 "extendcircuit" request.
14564 - Controller protocol fixes: fix encoding in "getinfo addr-mappings"
14565 response; fix error code when "getinfo dir/status/" fails.
14566 - Avoid crash when telling controller stream-status and a stream
14568 - Patch from Adam Langley to fix assert() in eventdns.c.
14569 - Fix a debug log message in eventdns to say "X resolved to Y"
14570 instead of "X resolved to X".
14571 - Make eventdns give strings for DNS errors, not just error numbers.
14572 - Track unreachable entry guards correctly: don't conflate
14573 'unreachable by us right now' with 'listed as down by the directory
14574 authorities'. With the old code, if a guard was unreachable by
14575 us but listed as running, it would clog our guard list forever.
14576 - Behave correctly in case we ever have a network with more than
14577 2GB/s total advertised capacity.
14578 - Make TrackExitHosts case-insensitive, and fix the behavior of
14579 ".suffix" TrackExitHosts items to avoid matching in the middle of
14581 - Finally fix the openssl warnings from newer gccs that believe that
14582 ignoring a return value is okay, but casting a return value and
14583 then ignoring it is a sign of madness.
14584 - Prevent the contrib/exitlist script from printing the same
14585 result more than once.
14586 - Patch from Steve Hildrey: Generate network status correctly on
14587 non-versioning dirservers.
14588 - Don't listen to the X-Your-Address-Is hint if you did the lookup
14589 via Tor; otherwise you'll think you're the exit node's IP address.
14591 o Minor bugfixes, performance:
14592 - Two small performance improvements on parsing descriptors.
14593 - Major performance improvement on inserting descriptors: change
14594 algorithm from O(n^2) to O(n).
14595 - Make the common memory allocation path faster on machines where
14596 malloc(0) returns a pointer.
14597 - Start remembering X-Your-Address-Is directory hints even if you're
14598 a client, so you can become a server more smoothly.
14599 - Avoid duplicate entries on MyFamily line in server descriptor.
14601 o Packaging, features:
14602 - Remove architecture from OS X builds. The official builds are
14603 now universal binaries.
14604 - The Debian package now uses --verify-config when (re)starting,
14605 to distinguish configuration errors from other errors.
14606 - Update RPMs to require libevent 1.1b.
14608 o Packaging, bugfixes:
14609 - Patches so Tor builds with MinGW on Windows.
14610 - Patches so Tor might run on Cygwin again.
14611 - Resume building on non-gcc compilers and ancient gcc. Resume
14612 building with the -O0 compile flag. Resume building cleanly on
14614 - Run correctly on OS X platforms with case-sensitive filesystems.
14615 - Correct includes for net/if.h and net/pfvar.h on OpenBSD (from Tup).
14616 - Add autoconf checks so Tor can build on Solaris x86 again.
14619 - Documented (and renamed) ServerDNSSearchDomains and
14620 ServerDNSResolvConfFile options.
14621 - Be clearer that the *ListenAddress directives can be repeated
14625 Changes in version 0.1.1.24 - 2006-09-29
14627 - Allow really slow clients to not hang up five minutes into their
14628 directory downloads (suggested by Adam J. Richter).
14629 - Fix major performance regression from 0.1.0.x: instead of checking
14630 whether we have enough directory information every time we want to
14631 do something, only check when the directory information has changed.
14632 This should improve client CPU usage by 25-50%.
14633 - Don't crash if, after a server has been running for a while,
14634 it can't resolve its hostname.
14637 - Allow Tor to start when RunAsDaemon is set but no logs are set.
14638 - Don't crash when the controller receives a third argument to an
14639 "extendcircuit" request.
14640 - Controller protocol fixes: fix encoding in "getinfo addr-mappings"
14641 response; fix error code when "getinfo dir/status/" fails.
14642 - Fix configure.in to not produce broken configure files with
14643 more recent versions of autoconf. Thanks to Clint for his auto*
14645 - Fix security bug on NetBSD that could allow someone to force
14646 uninitialized RAM to be sent to a server's DNS resolver. This
14647 only affects NetBSD and other platforms that do not bounds-check
14649 - Warn user when using libevent 1.1a or earlier with win32 or kqueue
14650 methods: these are known to be buggy.
14651 - If we're a directory mirror and we ask for "all" network status
14652 documents, we would discard status documents from authorities
14653 we don't recognize.
14656 Changes in version 0.1.2.1-alpha - 2006-08-27
14658 - Add "eventdns" async dns library from Adam Langley, tweaked to
14659 build on OSX and Windows. Only enabled if you pass the
14660 --enable-eventdns argument to configure.
14661 - Allow servers with no hostname or IP address to learn their
14662 IP address by asking the directory authorities. This code only
14663 kicks in when you would normally have exited with a "no address"
14664 error. Nothing's authenticated, so use with care.
14665 - Rather than waiting a fixed amount of time between retrying
14666 application connections, we wait only 5 seconds for the first,
14667 10 seconds for the second, and 15 seconds for each retry after
14668 that. Hopefully this will improve the expected user experience.
14669 - Patch from Tup to add support for transparent AP connections:
14670 this basically bundles the functionality of trans-proxy-tor
14671 into the Tor mainline. Now hosts with compliant pf/netfilter
14672 implementations can redirect TCP connections straight to Tor
14673 without diverting through SOCKS. Needs docs.
14674 - Busy directory servers save lots of memory by spooling server
14675 descriptors, v1 directories, and v2 networkstatus docs to buffers
14676 as needed rather than en masse. Also mmap the cached-routers
14677 files, so we don't need to keep the whole thing in memory too.
14678 - Automatically avoid picking more than one node from the same
14679 /16 network when constructing a circuit.
14680 - Revise and clean up the torrc.sample that we ship with; add
14681 a section for BandwidthRate and BandwidthBurst.
14684 - Split circuit_t into origin_circuit_t and or_circuit_t, and
14685 split connection_t into edge, or, dir, control, and base structs.
14686 These will save quite a bit of memory on busy servers, and they'll
14687 also help us track down bugs in the code and bugs in the spec.
14688 - Experimentally re-enable kqueue on OSX when using libevent 1.1b
14689 or later. Log when we are doing this, so we can diagnose it when
14690 it fails. (Also, recommend libevent 1.1b for kqueue and
14691 win32 methods; deprecate libevent 1.0b harder; make libevent
14692 recommendation system saner.)
14693 - Start being able to build universal binaries on OS X (thanks
14695 - Export the default exit policy via the control port, so controllers
14696 don't need to guess what it is / will be later.
14697 - Add a man page entry for ProtocolWarnings.
14698 - Add TestVia config option to the man page.
14699 - Remove even more protocol-related warnings from Tor server logs,
14700 such as bad TLS handshakes and malformed begin cells.
14701 - Stop fetching descriptors if you're not a dir mirror and you
14702 haven't tried to establish any circuits lately. [This currently
14703 causes some dangerous behavior, because when you start up again
14704 you'll use your ancient server descriptors.]
14705 - New DirPort behavior: if you have your dirport set, you download
14706 descriptors aggressively like a directory mirror, whether or not
14707 your ORPort is set.
14708 - Get rid of the router_retry_connections notion. Now routers
14709 no longer try to rebuild long-term connections to directory
14710 authorities, and directory authorities no longer try to rebuild
14711 long-term connections to all servers. We still don't hang up
14712 connections in these two cases though -- we need to look at it
14713 more carefully to avoid flapping, and we likely need to wait til
14714 0.1.1.x is obsolete.
14715 - Drop compatibility with obsolete Tors that permit create cells
14716 to have the wrong circ_id_type.
14717 - Re-enable per-connection rate limiting. Get rid of the "OP
14718 bandwidth" concept. Lay groundwork for "bandwidth classes" --
14719 separate global buckets that apply depending on what sort of conn
14721 - Start publishing one minute or so after we find our ORPort
14722 to be reachable. This will help reduce the number of descriptors
14723 we have for ourselves floating around, since it's quite likely
14724 other things (e.g. DirPort) will change during that minute too.
14725 - Fork the v1 directory protocol into its own spec document,
14726 and mark dir-spec.txt as the currently correct (v2) spec.
14729 - When we find our DirPort to be reachable, publish a new descriptor
14730 so we'll tell the world (reported by pnx).
14731 - Publish a new descriptor after we hup/reload. This is important
14732 if our config has changed such that we'll want to start advertising
14733 our DirPort now, etc.
14734 - Allow Tor to start when RunAsDaemon is set but no logs are set.
14735 - When we have a state file we cannot parse, tell the user and
14736 move it aside. Now we avoid situations where the user starts
14737 Tor in 1904, Tor writes a state file with that timestamp in it,
14738 the user fixes her clock, and Tor refuses to start.
14739 - Fix configure.in to not produce broken configure files with
14740 more recent versions of autoconf. Thanks to Clint for his auto*
14742 - "tor --verify-config" now exits with -1(255) or 0 depending on
14743 whether the config options are bad or good.
14744 - Resolve bug 321 when using dnsworkers: append a period to every
14745 address we resolve at the exit node, so that we do not accidentally
14746 pick up local addresses, and so that failing searches are retried
14747 in the resolver search domains. (This is already solved for
14748 eventdns.) (This breaks Blossom servers for now.)
14749 - If we are using an exit enclave and we can't connect, e.g. because
14750 its webserver is misconfigured to not listen on localhost, then
14751 back off and try connecting from somewhere else before we fail.
14754 - Start compiling on MinGW on Windows (patches from Mike Chiussi).
14755 - Start compiling on MSVC6 on Windows (patches from Frediano Ziglio).
14756 - Fix bug 314: Tor clients issued "unsafe socks" warnings even
14757 when the IP address is mapped through MapAddress to a hostname.
14758 - Start passing "ipv4" hints to getaddrinfo(), so servers don't do
14759 useless IPv6 DNS resolves.
14760 - Patch suggested by Karsten Loesing: respond to SIGNAL command
14761 before we execute the signal, in case the signal shuts us down.
14762 - Clean up AllowInvalidNodes man page entry.
14763 - Claim a commonname of Tor, rather than TOR, in TLS handshakes.
14764 - Add more asserts to track down an assert error on a windows Tor
14765 server with connection_add being called with socket == -1.
14766 - Handle reporting OR_CONN_EVENT_NEW events to the controller.
14767 - Fix misleading log messages: an entry guard that is "unlisted",
14768 as well as not known to be "down" (because we've never heard
14769 of it), is not therefore "up".
14770 - Remove code to special-case "-cvs" ending, since it has not
14771 actually mattered since 0.0.9.
14772 - Make our socks5 handling more robust to broken socks clients:
14773 throw out everything waiting on the buffer in between socks
14774 handshake phases, since they can't possibly (so the theory
14775 goes) have predicted what we plan to respond to them.
14778 Changes in version 0.1.1.23 - 2006-07-30
14780 - Fast Tor servers, especially exit nodes, were triggering asserts
14781 due to a bug in handling the list of pending DNS resolves. Some
14782 bugs still remain here; we're hunting them.
14783 - Entry guards could crash clients by sending unexpected input.
14784 - More fixes on reachability testing: if you find yourself reachable,
14785 then don't ever make any client requests (so you stop predicting
14786 circuits), then hup or have your clock jump, then later your IP
14787 changes, you won't think circuits are working, so you won't try to
14788 test reachability, so you won't publish.
14791 - Avoid a crash if the controller does a resetconf firewallports
14792 and then a setconf fascistfirewall=1.
14793 - Avoid an integer underflow when the dir authority decides whether
14794 a router is stable: we might wrongly label it stable, and compute
14795 a slightly wrong median stability, when a descriptor is published
14797 - Fix a place where we might trigger an assert if we can't build our
14798 own server descriptor yet.
14801 Changes in version 0.1.1.22 - 2006-07-05
14803 - Fix a big bug that was causing servers to not find themselves
14804 reachable if they changed IP addresses. Since only 0.1.1.22+
14805 servers can do reachability testing correctly, now we automatically
14806 make sure to test via one of these.
14807 - Fix to allow clients and mirrors to learn directory info from
14808 descriptor downloads that get cut off partway through.
14809 - Directory authorities had a bug in deciding if a newly published
14810 descriptor was novel enough to make everybody want a copy -- a few
14811 servers seem to be publishing new descriptors many times a minute.
14813 - Fix a rare bug that was causing some servers to complain about
14814 "closing wedged cpuworkers" and skip some circuit create requests.
14815 - Make the Exit flag in directory status documents actually work.
14818 Changes in version 0.1.1.21 - 2006-06-10
14819 o Crash and assert fixes from 0.1.1.20:
14820 - Fix a rare crash on Tor servers that have enabled hibernation.
14821 - Fix a seg fault on startup for Tor networks that use only one
14822 directory authority.
14823 - Fix an assert from a race condition that occurs on Tor servers
14824 while exiting, where various threads are trying to log that they're
14825 exiting, and delete the logs, at the same time.
14826 - Make our unit tests pass again on certain obscure platforms.
14829 - Add support for building SUSE RPM packages.
14830 - Speed up initial bootstrapping for clients: if we are making our
14831 first ever connection to any entry guard, then don't mark it down
14833 - When only one Tor server in the network is labelled as a guard,
14834 and we've already picked him, we would cycle endlessly picking him
14835 again, being unhappy about it, etc. Now we specifically exclude
14836 current guards when picking a new guard.
14837 - Servers send create cells more reliably after the TLS connection
14838 is established: we were sometimes forgetting to send half of them
14839 when we had more than one pending.
14840 - If we get a create cell that asks us to extend somewhere, but the
14841 Tor server there doesn't match the expected digest, we now send
14842 a destroy cell back, rather than silently doing nothing.
14843 - Make options->RedirectExit work again.
14844 - Make cookie authentication for the controller work again.
14845 - Stop being picky about unusual characters in the arguments to
14846 mapaddress. It's none of our business.
14847 - Add a new config option "TestVia" that lets you specify preferred
14848 middle hops to use for test circuits. Perhaps this will let me
14849 debug the reachability problems better.
14851 o Log / documentation fixes:
14852 - If we're a server and some peer has a broken TLS certificate, don't
14853 log about it unless ProtocolWarnings is set, i.e., we want to hear
14854 about protocol violations by others.
14855 - Fix spelling of VirtualAddrNetwork in man page.
14856 - Add a better explanation at the top of the autogenerated torrc file
14857 about what happened to our old torrc.
14860 Changes in version 0.1.1.20 - 2006-05-23
14862 - Downgrade a log severity where servers complain that they're
14864 - Avoid a compile warning on FreeBSD.
14865 - Remove string size limit on NEWDESC messages; solve bug 291.
14866 - Correct the RunAsDaemon entry in the man page; ignore RunAsDaemon
14867 more thoroughly when we're running on windows.
14870 Changes in version 0.1.1.19-rc - 2006-05-03
14872 - Regenerate our local descriptor if it's dirty and we try to use
14873 it locally (e.g. if it changes during reachability detection).
14874 - If we setconf our ORPort to 0, we continued to listen on the
14875 old ORPort and receive connections.
14876 - Avoid a second warning about machine/limits.h on Debian
14878 - Be willing to add our own routerinfo into the routerlist.
14879 Now authorities will include themselves in their directories
14880 and network-statuses.
14881 - Stop trying to upload rendezvous descriptors to every
14882 directory authority: only try the v1 authorities.
14883 - Servers no longer complain when they think they're not
14884 registered with the directory authorities. There were too many
14886 - Backport dist-rpm changes so rpms can be built without errors.
14889 - Implement an option, VirtualAddrMask, to set which addresses
14890 get handed out in response to mapaddress requests. This works
14891 around a bug in tsocks where 127.0.0.0/8 is never socksified.
14894 Changes in version 0.1.1.18-rc - 2006-04-10
14896 - Work harder to download live network-statuses from all the
14897 directory authorities we know about. Improve the threshold
14898 decision logic so we're more robust to edge cases.
14899 - When fetching rendezvous descriptors, we were willing to ask
14900 v2 authorities too, which would always return 404.
14903 - Stop listing down or invalid nodes in the v1 directory. This will
14904 reduce its bulk by about 1/3, and reduce load on directory
14906 - When deciding whether a router is Fast or Guard-worthy, consider
14907 his advertised BandwidthRate and not just the BandwidthCapacity.
14908 - No longer ship INSTALL and README files -- they are useless now.
14909 - Force rpmbuild to behave and honor target_cpu.
14910 - Avoid warnings about machine/limits.h on Debian GNU/kFreeBSD.
14911 - Start to include translated versions of the tor-doc-*.html
14912 files, along with the screenshots. Still needs more work.
14913 - Start sending back 512 and 451 errors if mapaddress fails,
14914 rather than not sending anything back at all.
14915 - When we fail to bind or listen on an incoming or outgoing
14916 socket, we should close it before failing. otherwise we just
14917 leak it. (thanks to weasel for finding.)
14918 - Allow "getinfo dir/status/foo" to work, as long as your DirPort
14919 is enabled. (This is a hack, and will be fixed in 0.1.2.x.)
14920 - Make NoPublish (even though deprecated) work again.
14921 - Fix a minor security flaw where a versioning auth dirserver
14922 could list a recommended version many times in a row to make
14923 clients more convinced that it's recommended.
14924 - Fix crash bug if there are two unregistered servers running
14925 with the same nickname, one of them is down, and you ask for
14926 them by nickname in your EntryNodes or ExitNodes. Also, try
14927 to pick the one that's running rather than an arbitrary one.
14928 - Fix an infinite loop we could hit if we go offline for too long.
14929 - Complain when we hit WSAENOBUFS on recv() or write() too.
14930 Perhaps this will help us hunt the bug.
14931 - If you're not a versioning dirserver, don't put the string
14932 "client-versions \nserver-versions \n" in your network-status.
14933 - Lower the minimum required number of file descriptors to 1000,
14934 so we can have some overhead for Valgrind on Linux, where the
14935 default ulimit -n is 1024.
14938 - Add tor.dizum.com as the fifth authoritative directory server.
14939 - Add a new config option FetchUselessDescriptors, off by default,
14940 for when you plan to run "exitlist" on your client and you want
14941 to know about even the non-running descriptors.
14944 Changes in version 0.1.1.17-rc - 2006-03-28
14946 - Clients and servers since 0.1.1.10-alpha have been expiring
14947 connections whenever they are idle for 5 minutes and they *do*
14948 have circuits on them. Oops. With this new version, clients will
14949 discard their previous entry guard choices and avoid choosing
14950 entry guards running these flawed versions.
14951 - Fix memory leak when uncompressing concatenated zlib streams. This
14952 was causing substantial leaks over time on Tor servers.
14953 - The v1 directory was including servers as much as 48 hours old,
14954 because that's how the new routerlist->routers works. Now only
14955 include them if they're 20 hours old or less.
14958 - Resume building on irix64, netbsd 2.0, etc.
14959 - On non-gcc compilers (e.g. solaris), use "-g -O" instead of
14961 - Stop writing the "router.desc" file, ever. Nothing uses it anymore,
14962 and it is confusing some users.
14963 - Mirrors stop caching the v1 directory so often.
14964 - Make the max number of old descriptors that a cache will hold
14965 rise with the number of directory authorities, so we can scale.
14966 - Change our win32 uname() hack to be more forgiving about what
14967 win32 versions it thinks it's found.
14970 - Add lefkada.eecs.harvard.edu as a fourth authoritative directory
14972 - When the controller's *setconf commands fail, collect an error
14973 message in a string and hand it back to the controller.
14974 - Make the v2 dir's "Fast" flag based on relative capacity, just
14975 like "Stable" is based on median uptime. Name everything in the
14976 top 7/8 Fast, and only the top 1/2 gets to be a Guard.
14977 - Log server fingerprint on startup, so new server operators don't
14978 have to go hunting around their filesystem for it.
14979 - Return a robots.txt on our dirport to discourage google indexing.
14980 - Let the controller ask for GETINFO dir/status/foo so it can ask
14981 directly rather than connecting to the dir port. Only works when
14982 dirport is set for now.
14984 o New config options rather than constants in the code:
14985 - SocksTimeout: How long do we let a socks connection wait
14986 unattached before we fail it?
14987 - CircuitBuildTimeout: Cull non-open circuits that were born
14988 at least this many seconds ago.
14989 - CircuitIdleTimeout: Cull open clean circuits that were born
14990 at least this many seconds ago.
14993 Changes in version 0.1.1.16-rc - 2006-03-18
14994 o Bugfixes on 0.1.1.15-rc:
14995 - Fix assert when the controller asks to attachstream a connect-wait
14996 or resolve-wait stream.
14997 - Now do address rewriting when the controller asks us to attach
14998 to a particular circuit too. This will let Blossom specify
14999 "moria2.exit" without having to learn what moria2's IP address is.
15000 - Make the "tor --verify-config" command-line work again, so people
15001 can automatically check if their torrc will parse.
15002 - Authoritative dirservers no longer require an open connection from
15003 a server to consider him "reachable". We need this change because
15004 when we add new auth dirservers, old servers won't know not to
15006 - Let Tor build on Sun CC again.
15007 - Fix an off-by-one buffer size in dirserv.c that magically never
15008 hit our three authorities but broke sjmurdoch's own tor network.
15009 - If we as a directory mirror don't know of any v1 directory
15010 authorities, then don't try to cache any v1 directories.
15011 - Stop warning about unknown servers in our family when they are
15012 given as hex digests.
15013 - Stop complaining as quickly to the server operator that he
15014 hasn't registered his nickname/key binding.
15015 - Various cleanups so we can add new V2 Auth Dirservers.
15016 - Change "AllowUnverifiedNodes" to "AllowInvalidNodes", to
15017 reflect the updated flags in our v2 dir protocol.
15018 - Resume allowing non-printable characters for exit streams (both
15019 for connecting and for resolving). Now we tolerate applications
15020 that don't follow the RFCs. But continue to block malformed names
15023 o Bugfixes on 0.1.0.x:
15024 - Fix assert bug in close_logs(): when we close and delete logs,
15025 remove them all from the global "logfiles" list.
15026 - Fix minor integer overflow in calculating when we expect to use up
15027 our bandwidth allocation before hibernating.
15028 - Fix a couple of bugs in OpenSSL detection. Also, deal better when
15029 there are multiple SSLs installed with different versions.
15030 - When we try to be a server and Address is not explicitly set and
15031 our hostname resolves to a private IP address, try to use an
15032 interface address if it has a public address. Now Windows machines
15033 that think of themselves as localhost can work by default.
15036 - Let the controller ask for GETINFO dir/server/foo so it can ask
15037 directly rather than connecting to the dir port.
15038 - Let the controller tell us about certain router descriptors
15039 that it doesn't want Tor to use in circuits. Implement
15040 SETROUTERPURPOSE and modify +POSTDESCRIPTOR to do this.
15041 - New config option SafeSocks to reject all application connections
15042 using unsafe socks protocols. Defaults to off.
15045 Changes in version 0.1.1.15-rc - 2006-03-11
15046 o Bugfixes and cleanups:
15047 - When we're printing strings from the network, don't try to print
15048 non-printable characters. This protects us against shell escape
15049 sequence exploits, and also against attacks to fool humans into
15050 misreading their logs.
15051 - Fix a bug where Tor would fail to establish any connections if you
15052 left it off for 24 hours and then started it: we were happy with
15053 the obsolete network statuses, but they all referred to router
15054 descriptors that were too old to fetch, so we ended up with no
15055 valid router descriptors.
15056 - Fix a seg fault in the controller's "getinfo orconn-status"
15057 command while listing status on incoming handshaking connections.
15058 Introduce a status name "NEW" for these connections.
15059 - If we get a linelist or linelist_s config option from the torrc
15060 (e.g. ExitPolicy) and it has no value, warn and skip rather than
15061 silently resetting it to its default.
15062 - Don't abandon entry guards until they've been down or gone for
15064 - Cleaner and quieter log messages.
15067 - New controller signal NEWNYM that makes new application requests
15068 use clean circuits.
15069 - Add a new circuit purpose 'controller' to let the controller ask
15070 for a circuit that Tor won't try to use. Extend the EXTENDCIRCUIT
15071 controller command to let you specify the purpose if you're
15072 starting a new circuit. Add a new SETCIRCUITPURPOSE controller
15073 command to let you change a circuit's purpose after it's been
15075 - Accept "private:*" in routerdesc exit policies; not generated yet
15076 because older Tors do not understand it.
15077 - Add BSD-style contributed startup script "rc.subr" from Peter
15081 Changes in version 0.1.1.14-alpha - 2006-02-20
15082 o Bugfixes on 0.1.1.x:
15083 - Don't die if we ask for a stdout or stderr log (even implicitly)
15084 and we're set to RunAsDaemon -- just warn.
15085 - We still had a few bugs in the OR connection rotation code that
15086 caused directory servers to slowly aggregate connections to other
15087 fast Tor servers. This time for sure!
15088 - Make log entries on Win32 include the name of the function again.
15089 - We were treating a pair of exit policies if they were equal even
15090 if one said accept and the other said reject -- causing us to
15091 not always publish a new descriptor since we thought nothing
15093 - Retry pending server downloads as well as pending networkstatus
15094 downloads when we unexpectedly get a socks request.
15095 - We were ignoring the IS_FAST flag in the directory status,
15096 meaning we were willing to pick trivial-bandwidth nodes for "fast"
15098 - If the controller's SAVECONF command fails (e.g. due to file
15099 permissions), let the controller know that it failed.
15102 - If we're trying to be a Tor server and running Windows 95/98/ME
15103 as a server, explain that we'll likely crash.
15104 - When we're a server, a client asks for an old-style directory,
15105 and our write bucket is empty, don't give it to him. This way
15106 small servers can continue to serve the directory *sometimes*,
15107 without getting overloaded.
15108 - Compress exit policies even more -- look for duplicate lines
15110 - Clients now honor the "guard" flag in the router status when
15111 picking entry guards, rather than looking at is_fast or is_stable.
15112 - Retain unrecognized lines in $DATADIR/state file, so that we can
15113 be forward-compatible.
15114 - Generate 18.0.0.0/8 address policy format in descs when we can;
15115 warn when the mask is not reducible to a bit-prefix.
15116 - Let the user set ControlListenAddress in the torrc. This can be
15117 dangerous, but there are some cases (like a secured LAN) where it
15119 - Split ReachableAddresses into ReachableDirAddresses and
15120 ReachableORAddresses, so we can restrict Dir conns to port 80
15121 and OR conns to port 443.
15122 - Now we can target arch and OS in rpm builds (contributed by
15123 Phobos). Also make the resulting dist-rpm filename match the
15125 - New config options to help controllers: FetchServerDescriptors
15126 and FetchHidServDescriptors for whether to fetch server
15127 info and hidserv info or let the controller do it, and
15128 PublishServerDescriptor and PublishHidServDescriptors.
15129 - Also let the controller set the __AllDirActionsPrivate config
15130 option if you want all directory fetches/publishes to happen via
15131 Tor (it assumes your controller bootstraps your circuits).
15134 Changes in version 0.1.0.17 - 2006-02-17
15135 o Crash bugfixes on 0.1.0.x:
15136 - When servers with a non-zero DirPort came out of hibernation,
15137 sometimes they would trigger an assert.
15139 o Other important bugfixes:
15140 - On platforms that don't have getrlimit (like Windows), we were
15141 artificially constraining ourselves to a max of 1024
15142 connections. Now just assume that we can handle as many as 15000
15143 connections. Hopefully this won't cause other problems.
15145 o Backported features:
15146 - When we're a server, a client asks for an old-style directory,
15147 and our write bucket is empty, don't give it to him. This way
15148 small servers can continue to serve the directory *sometimes*,
15149 without getting overloaded.
15150 - Whenever you get a 503 in response to a directory fetch, try
15151 once more. This will become important once servers start sending
15152 503's whenever they feel busy.
15153 - Fetch a new directory every 120 minutes, not every 40 minutes.
15154 Now that we have hundreds of thousands of users running the old
15155 directory algorithm, it's starting to hurt a lot.
15156 - Bump up the period for forcing a hidden service descriptor upload
15157 from 20 minutes to 1 hour.
15160 Changes in version 0.1.1.13-alpha - 2006-02-09
15161 o Crashes in 0.1.1.x:
15162 - When you tried to setconf ORPort via the controller, Tor would
15163 crash. So people using TorCP to become a server were sad.
15164 - Solve (I hope) the stack-smashing bug that we were seeing on fast
15165 servers. The problem appears to be something do with OpenSSL's
15166 random number generation, or how we call it, or something. Let me
15167 know if the crashes continue.
15168 - Turn crypto hardware acceleration off by default, until we find
15169 somebody smart who can test it for us. (It appears to produce
15170 seg faults in at least some cases.)
15171 - Fix a rare assert error when we've tried all intro points for
15172 a hidden service and we try fetching the service descriptor again:
15173 "Assertion conn->state != AP_CONN_STATE_RENDDESC_WAIT failed"
15176 - Fix a major load balance bug: we were round-robining in 16 KB
15177 chunks, and servers with bandwidthrate of 20 KB, while downloading
15178 a 600 KB directory, would starve their other connections. Now we
15179 try to be a bit more fair.
15180 - Dir authorities and mirrors were never expiring the newest
15181 descriptor for each server, causing memory and directory bloat.
15182 - Fix memory-bloating and connection-bloating bug on servers: We
15183 were never closing any connection that had ever had a circuit on
15184 it, because we were checking conn->n_circuits == 0, yet we had a
15185 bug that let it go negative.
15186 - Make Tor work using squid as your http proxy again -- squid
15187 returns an error if you ask for a URL that's too long, and it uses
15188 a really generic error message. Plus, many people are behind a
15189 transparent squid so they don't even realize it.
15190 - On platforms that don't have getrlimit (like Windows), we were
15191 artificially constraining ourselves to a max of 1024
15192 connections. Now just assume that we can handle as many as 15000
15193 connections. Hopefully this won't cause other problems.
15194 - Add a new config option ExitPolicyRejectPrivate which defaults to
15195 1. This means all exit policies will begin with rejecting private
15196 addresses, unless the server operator explicitly turns it off.
15199 - Clients no longer download descriptors for non-running
15201 - Before we add new directory authorities, we should make it
15202 clear that only v1 authorities should receive/publish hidden
15203 service descriptors.
15206 - As soon as we've fetched some more directory info, immediately
15207 try to download more server descriptors. This way we don't have
15208 a 10 second pause during initial bootstrapping.
15209 - Remove even more loud log messages that the server operator can't
15211 - When we're running an obsolete or un-recommended version, make
15212 the log message more clear about what the problem is and what
15213 versions *are* still recommended.
15214 - Provide a more useful warn message when our onion queue gets full:
15215 the CPU is too slow or the exit policy is too liberal.
15216 - Don't warn when we receive a 503 from a dirserver/cache -- this
15217 will pave the way for them being able to refuse if they're busy.
15218 - When we fail to bind a listener, try to provide a more useful
15219 log message: e.g., "Is Tor already running?"
15220 - Adjust tor-spec to parameterize cell and key lengths. Now Ian
15221 Goldberg can prove things about our handshake protocol more
15223 - MaxConn has been obsolete for a while now. Document the ConnLimit
15224 config option, which is a *minimum* number of file descriptors
15225 that must be available else Tor refuses to start.
15226 - Apply Matt Ghali's --with-syslog-facility patch to ./configure
15227 if you log to syslog and want something other than LOG_DAEMON.
15228 - Make dirservers generate a separate "guard" flag to mean,
15229 "would make a good entry guard". Make clients parse it and vote
15230 on it. Not used by clients yet.
15231 - Implement --with-libevent-dir option to ./configure. Also, improve
15232 search techniques to find libevent, and use those for openssl too.
15233 - Bump the default bandwidthrate to 3 MB, and burst to 6 MB
15234 - Only start testing reachability once we've established a
15235 circuit. This will make startup on dirservers less noisy.
15236 - Don't try to upload hidden service descriptors until we have
15237 established a circuit.
15238 - Fix the controller's "attachstream 0" command to treat conn like
15239 it just connected, doing address remapping, handling .exit and
15240 .onion idioms, and so on. Now we're more uniform in making sure
15241 that the controller hears about new and closing connections.
15244 Changes in version 0.1.1.12-alpha - 2006-01-11
15245 o Bugfixes on 0.1.1.x:
15246 - The fix to close duplicate server connections was closing all
15247 Tor client connections if they didn't establish a circuit
15248 quickly enough. Oops.
15249 - Fix minor memory issue (double-free) that happened on exit.
15251 o Bugfixes on 0.1.0.x:
15252 - Tor didn't warn when it failed to open a log file.
15255 Changes in version 0.1.1.11-alpha - 2006-01-10
15256 o Crashes in 0.1.1.x:
15257 - Include all the assert/crash fixes from 0.1.0.16.
15258 - If you start Tor and then quit very quickly, there were some
15259 races that tried to free things that weren't allocated yet.
15260 - Fix a rare memory stomp if you're running hidden services.
15261 - Fix segfault when specifying DirServer in config without nickname.
15262 - Fix a seg fault when you finish connecting to a server but at
15263 that moment you dump his server descriptor.
15264 - Extendcircuit and Attachstream controller commands would
15265 assert/crash if you don't give them enough arguments.
15266 - Fix an assert error when we're out of space in the connection_list
15267 and we try to post a hidden service descriptor (reported by weasel).
15268 - If you specify a relative torrc path and you set RunAsDaemon in
15269 your torrc, then it chdir()'s to the new directory. If you HUP,
15270 it tries to load the new torrc location, fails, and exits.
15271 The fix: no longer allow a relative path to torrc using -f.
15274 - Implement "entry guards": automatically choose a handful of entry
15275 nodes and stick with them for all circuits. Only pick new guards
15276 when the ones you have are unsuitable, and if the old guards
15277 become suitable again, switch back. This will increase security
15278 dramatically against certain end-point attacks. The EntryNodes
15279 config option now provides some hints about which entry guards you
15280 want to use most; and StrictEntryNodes means to only use those.
15281 - New directory logic: download by descriptor digest, not by
15282 fingerprint. Caches try to download all listed digests from
15283 authorities; clients try to download "best" digests from caches.
15284 This avoids partitioning and isolating attacks better.
15285 - Make the "stable" router flag in network-status be the median of
15286 the uptimes of running valid servers, and make clients pay
15287 attention to the network-status flags. Thus the cutoff adapts
15288 to the stability of the network as a whole, making IRC, IM, etc
15289 connections more reliable.
15292 - Tor servers with dynamic IP addresses were needing to wait 18
15293 hours before they could start doing reachability testing using
15294 the new IP address and ports. This is because they were using
15295 the internal descriptor to learn what to test, yet they were only
15296 rebuilding the descriptor once they decided they were reachable.
15297 - Tor 0.1.1.9 and 0.1.1.10 had a serious bug that caused clients
15298 to download certain server descriptors, throw them away, and then
15299 fetch them again after 30 minutes. Now mirrors throw away these
15300 server descriptors so clients can't get them.
15301 - We were leaving duplicate connections to other ORs open for a week,
15302 rather than closing them once we detect a duplicate. This only
15303 really affected authdirservers, but it affected them a lot.
15304 - Spread the authdirservers' reachability testing over the entire
15305 testing interval, so we don't try to do 500 TLS's at once every
15309 - If the network is down, and we try to connect to a conn because
15310 we have a circuit in mind, and we timeout (30 seconds) because the
15311 network never answers, we were expiring the circuit, but we weren't
15312 obsoleting the connection or telling the entry_guards functions.
15313 - Some Tor servers process billions of cells per day. These statistics
15314 need to be uint64_t's.
15315 - Check for integer overflows in more places, when adding elements
15316 to smartlists. This could possibly prevent a buffer overflow
15317 on malicious huge inputs. I don't see any, but I haven't looked
15319 - ReachableAddresses kept growing new "reject *:*" lines on every
15321 - When you "setconf log" via the controller, it should remove all
15322 logs. We were automatically adding back in a "log notice stdout".
15323 - Newly bootstrapped Tor networks couldn't establish hidden service
15324 circuits until they had nodes with high uptime. Be more tolerant.
15325 - We were marking servers down when they could not answer every piece
15326 of the directory request we sent them. This was far too harsh.
15327 - Fix the torify (tsocks) config file to not use Tor for localhost
15329 - Directory authorities now go to the proper authority when asking for
15330 a networkstatus, even when they want a compressed one.
15331 - Fix a harmless bug that was causing Tor servers to log
15332 "Got an end because of misc error, but we're not an AP. Closing."
15333 - Authorities were treating their own descriptor changes as cosmetic,
15334 meaning the descriptor available in the network-status and the
15335 descriptor that clients downloaded were different.
15336 - The OS X installer was adding a symlink for tor_resolve but
15337 the binary was called tor-resolve (reported by Thomas Hardly).
15338 - Workaround a problem with some http proxies where they refuse GET
15339 requests that specify "Content-Length: 0" (reported by Adrian).
15340 - Fix wrong log message when you add a "HiddenServiceNodes" config
15341 line without any HiddenServiceDir line (reported by Chris Thomas).
15344 - Write the TorVersion into the state file so we have a prayer of
15345 keeping forward and backward compatibility.
15346 - Revive the FascistFirewall config option rather than eliminating it:
15347 now it's a synonym for ReachableAddresses *:80,*:443.
15348 - Clients choose directory servers from the network status lists,
15349 not from their internal list of router descriptors. Now they can
15350 go to caches directly rather than needing to go to authorities
15352 - Directory authorities ignore router descriptors that have only
15353 cosmetic differences: do this for 0.1.0.x servers now too.
15354 - Add a new flag to network-status indicating whether the server
15355 can answer v2 directory requests too.
15356 - Authdirs now stop whining so loudly about bad descriptors that
15357 they fetch from other dirservers. So when there's a log complaint,
15358 it's for sure from a freshly uploaded descriptor.
15359 - Reduce memory requirements in our structs by changing the order
15361 - There used to be two ways to specify your listening ports in a
15362 server descriptor: on the "router" line and with a separate "ports"
15363 line. Remove support for the "ports" line.
15364 - New config option "AuthDirRejectUnlisted" for auth dirservers as
15365 a panic button: if we get flooded with unusable servers we can
15366 revert to only listing servers in the approved-routers file.
15367 - Auth dir servers can now mark a fingerprint as "!reject" or
15368 "!invalid" in the approved-routers file (as its nickname), to
15369 refuse descriptors outright or include them but marked as invalid.
15370 - Servers store bandwidth history across restarts/crashes.
15371 - Add reasons to DESTROY and RELAY_TRUNCATED cells, so clients can
15372 get a better idea of why their circuits failed. Not used yet.
15373 - Directory mirrors now cache up to 16 unrecognized network-status
15374 docs. Now we can add new authdirservers and they'll be cached too.
15375 - When picking a random directory, prefer non-authorities if any
15377 - New controller option "getinfo desc/all-recent" to fetch the
15378 latest server descriptor for every router that Tor knows about.
15381 Changes in version 0.1.0.16 - 2006-01-02
15382 o Crash bugfixes on 0.1.0.x:
15383 - On Windows, build with a libevent patch from "I-M Weasel" to avoid
15384 corrupting the heap, losing FDs, or crashing when we need to resize
15385 the fd_sets. (This affects the Win32 binaries, not Tor's sources.)
15386 - It turns out sparc64 platforms crash on unaligned memory access
15387 too -- so detect and avoid this.
15388 - Handle truncated compressed data correctly (by detecting it and
15390 - Fix possible-but-unlikely free(NULL) in control.c.
15391 - When we were closing connections, there was a rare case that
15392 stomped on memory, triggering seg faults and asserts.
15393 - Avoid potential infinite recursion when building a descriptor. (We
15394 don't know that it ever happened, but better to fix it anyway.)
15395 - We were neglecting to unlink marked circuits from soon-to-close OR
15396 connections, which caused some rare scribbling on freed memory.
15397 - Fix a memory stomping race bug when closing the joining point of two
15398 rendezvous circuits.
15399 - Fix an assert in time parsing found by Steven Murdoch.
15401 o Other bugfixes on 0.1.0.x:
15402 - When we're doing reachability testing, provide more useful log
15403 messages so the operator knows what to expect.
15404 - Do not check whether DirPort is reachable when we are suppressing
15405 advertising it because of hibernation.
15406 - When building with -static or on Solaris, we sometimes needed -ldl.
15407 - When we're deciding whether a stream has enough circuits around
15408 that can handle it, count the freshly dirty ones and not the ones
15409 that are so dirty they won't be able to handle it.
15410 - When we're expiring old circuits, we had a logic error that caused
15411 us to close new rendezvous circuits rather than old ones.
15412 - Give a more helpful log message when you try to change ORPort via
15413 the controller: you should upgrade Tor if you want that to work.
15414 - We were failing to parse Tor versions that start with "Tor ".
15415 - Tolerate faulty streams better: when a stream fails for reason
15416 exitpolicy, stop assuming that the router is lying about his exit
15417 policy. When a stream fails for reason misc, allow it to retry just
15418 as if it was resolvefailed. When a stream has failed three times,
15419 reset its failure count so we can try again and get all three tries.
15422 Changes in version 0.1.1.10-alpha - 2005-12-11
15423 o Correctness bugfixes on 0.1.0.x:
15424 - On Windows, build with a libevent patch from "I-M Weasel" to avoid
15425 corrupting the heap, losing FDs, or crashing when we need to resize
15426 the fd_sets. (This affects the Win32 binaries, not Tor's sources.)
15427 - Stop doing the complex voodoo overkill checking for insecure
15428 Diffie-Hellman keys. Just check if it's in [2,p-2] and be happy.
15429 - When we were closing connections, there was a rare case that
15430 stomped on memory, triggering seg faults and asserts.
15431 - We were neglecting to unlink marked circuits from soon-to-close OR
15432 connections, which caused some rare scribbling on freed memory.
15433 - When we're deciding whether a stream has enough circuits around
15434 that can handle it, count the freshly dirty ones and not the ones
15435 that are so dirty they won't be able to handle it.
15436 - Recover better from TCP connections to Tor servers that are
15437 broken but don't tell you (it happens!); and rotate TLS
15438 connections once a week.
15439 - When we're expiring old circuits, we had a logic error that caused
15440 us to close new rendezvous circuits rather than old ones.
15441 - Fix a scary-looking but apparently harmless bug where circuits
15442 would sometimes start out in state CIRCUIT_STATE_OR_WAIT at
15443 servers, and never switch to state CIRCUIT_STATE_OPEN.
15444 - When building with -static or on Solaris, we sometimes needed to
15446 - Give a useful message when people run Tor as the wrong user,
15447 rather than telling them to start chowning random directories.
15448 - We were failing to inform the controller about new .onion streams.
15450 o Security bugfixes on 0.1.0.x:
15451 - Refuse server descriptors if the fingerprint line doesn't match
15452 the included identity key. Tor doesn't care, but other apps (and
15453 humans) might actually be trusting the fingerprint line.
15454 - We used to kill the circuit when we receive a relay command we
15455 don't recognize. Now we just drop it.
15456 - Start obeying our firewall options more rigorously:
15457 . If we can't get to a dirserver directly, try going via Tor.
15458 . Don't ever try to connect (as a client) to a place our
15459 firewall options forbid.
15460 . If we specify a proxy and also firewall options, obey the
15461 firewall options even when we're using the proxy: some proxies
15462 can only proxy to certain destinations.
15463 - Fix a bug found by Lasse Overlier: when we were making internal
15464 circuits (intended to be cannibalized later for rendezvous and
15465 introduction circuits), we were picking them so that they had
15466 useful exit nodes. There was no need for this, and it actually
15467 aids some statistical attacks.
15468 - Start treating internal circuits and exit circuits separately.
15469 It's important to keep them separate because internal circuits
15470 have their last hops picked like middle hops, rather than like
15471 exit hops. So exiting on them will break the user's expectations.
15473 o Bugfixes on 0.1.1.x:
15474 - Take out the mis-feature where we tried to detect IP address
15475 flapping for people with DynDNS, and chose not to upload a new
15476 server descriptor sometimes.
15477 - Try to be compatible with OpenSSL 0.9.6 again.
15478 - Log fix: when the controller is logging about .onion addresses,
15479 sometimes it didn't include the ".onion" part of the address.
15480 - Don't try to modify options->DirServers internally -- if the
15481 user didn't specify any, just add the default ones directly to
15482 the trusted dirserver list. This fixes a bug where people running
15483 controllers would use SETCONF on some totally unrelated config
15484 option, and Tor would start yelling at them about changing their
15486 - Let the controller's redirectstream command specify a port, in
15487 case the controller wants to change that too.
15488 - When we requested a pile of server descriptors, we sometimes
15489 accidentally launched a duplicate request for the first one.
15490 - Bugfix for trackhostexits: write down the fingerprint of the
15491 chosen exit, not its nickname, because the chosen exit might not
15493 - When parsing foo.exit, if foo is unknown, and we are leaving
15494 circuits unattached, set the chosen_exit field and leave the
15495 address empty. This matters because controllers got confused
15497 - Directory authorities no longer try to download server
15498 descriptors that they know they will reject.
15500 o Features and updates:
15501 - Replace balanced trees with hash tables: this should make stuff
15502 significantly faster.
15503 - Resume using the AES counter-mode implementation that we ship,
15504 rather than OpenSSL's. Ours is significantly faster.
15505 - Many other CPU and memory improvements.
15506 - Add a new config option FastFirstHopPK (on by default) so clients
15507 do a trivial crypto handshake for their first hop, since TLS has
15508 already taken care of confidentiality and authentication.
15509 - Add a new config option TestSocks so people can see if their
15510 applications are using socks4, socks4a, socks5-with-ip, or
15511 socks5-with-hostname. This way they don't have to keep mucking
15512 with tcpdump and wondering if something got cached somewhere.
15513 - Warn when listening on a public address for socks. I suspect a
15514 lot of people are setting themselves up as open socks proxies,
15515 and they have no idea that jerks on the Internet are using them,
15516 since they simply proxy the traffic into the Tor network.
15517 - Add "private:*" as an alias in configuration for policies. Now
15518 you can simplify your exit policy rather than needing to list
15519 every single internal or nonroutable network space.
15520 - Add a new controller event type that allows controllers to get
15521 all server descriptors that were uploaded to a router in its role
15522 as authoritative dirserver.
15523 - Start shipping socks-extensions.txt, tor-doc-unix.html,
15524 tor-doc-server.html, and stylesheet.css in the tarball.
15525 - Stop shipping tor-doc.html in the tarball.
15528 Changes in version 0.1.1.9-alpha - 2005-11-15
15529 o Usability improvements:
15530 - Start calling it FooListenAddress rather than FooBindAddress,
15531 since few of our users know what it means to bind an address
15533 - Reduce clutter in server logs. We're going to try to make
15534 them actually usable now. New config option ProtocolWarnings that
15535 lets you hear about how _other Tors_ are breaking the protocol. Off
15537 - Divide log messages into logging domains. Once we put some sort
15538 of interface on this, it will let people looking at more verbose
15539 log levels specify the topics they want to hear more about.
15540 - Make directory servers return better http 404 error messages
15541 instead of a generic "Servers unavailable".
15542 - Check for even more Windows version flags when writing the platform
15543 string in server descriptors, and note any we don't recognize.
15544 - Clean up more of the OpenSSL memory when exiting, so we can detect
15545 memory leaks better.
15546 - Make directory authorities be non-versioning, non-naming by
15547 default. Now we can add new directory servers without requiring
15548 their operators to pay close attention.
15549 - When logging via syslog, include the pid whenever we provide
15550 a log entry. Suggested by Todd Fries.
15552 o Performance improvements:
15553 - Directory servers now silently throw away new descriptors that
15554 haven't changed much if the timestamps are similar. We do this to
15555 tolerate older Tor servers that upload a new descriptor every 15
15556 minutes. (It seemed like a good idea at the time.)
15557 - Inline bottleneck smartlist functions; use fast versions by default.
15558 - Add a "Map from digest to void*" abstraction digestmap_t so we
15559 can do less hex encoding/decoding. Use it in router_get_by_digest()
15560 to resolve a performance bottleneck.
15561 - Allow tor_gzip_uncompress to extract as much as possible from
15562 truncated compressed data. Try to extract as many
15563 descriptors as possible from truncated http responses (when
15564 DIR_PURPOSE_FETCH_ROUTERDESC).
15565 - Make circ->onionskin a pointer, not a static array. moria2 was using
15566 125000 circuit_t's after it had been up for a few weeks, which
15567 translates to 20+ megs of wasted space.
15568 - The private half of our EDH handshake keys are now chosen out
15569 of 320 bits, not 1024 bits. (Suggested by Ian Goldberg.)
15571 o Security improvements:
15572 - Start making directory caches retain old routerinfos, so soon
15573 clients can start asking by digest of descriptor rather than by
15574 fingerprint of server.
15575 - Add half our entropy from RAND_poll in OpenSSL. This knows how
15576 to use egd (if present), openbsd weirdness (if present), vms/os2
15577 weirdness (if we ever port there), and more in the future.
15579 o Bugfixes on 0.1.0.x:
15580 - Do round-robin writes of at most 16 kB per write. This might be
15581 more fair on loaded Tor servers, and it might resolve our Windows
15582 crash bug. It might also slow things down.
15583 - Our TLS handshakes were generating a single public/private
15584 keypair for the TLS context, rather than making a new one for
15585 each new connections. Oops. (But we were still rotating them
15586 periodically, so it's not so bad.)
15587 - When we were cannibalizing a circuit with a particular exit
15588 node in mind, we weren't checking to see if that exit node was
15589 already present earlier in the circuit. Oops.
15590 - When a Tor server's IP changes (e.g. from a dyndns address),
15591 upload a new descriptor so clients will learn too.
15592 - Really busy servers were keeping enough circuits open on stable
15593 connections that they were wrapping around the circuit_id
15594 space. (It's only two bytes.) This exposed a bug where we would
15595 feel free to reuse a circuit_id even if it still exists but has
15596 been marked for close. Try to fix this bug. Some bug remains.
15597 - If we would close a stream early (e.g. it asks for a .exit that
15598 we know would refuse it) but the LeaveStreamsUnattached config
15599 option is set by the controller, then don't close it.
15601 o Bugfixes on 0.1.1.8-alpha:
15602 - Fix a big pile of memory leaks, some of them serious.
15603 - Do not try to download a routerdesc if we would immediately reject
15605 - Resume inserting a newline between all router descriptors when
15606 generating (old style) signed directories, since our spec says
15608 - When providing content-type application/octet-stream for
15609 server descriptors using .z, we were leaving out the
15610 content-encoding header. Oops. (Everything tolerated this just
15611 fine, but that doesn't mean we need to be part of the problem.)
15612 - Fix a potential seg fault in getconf and getinfo using version 1
15613 of the controller protocol.
15614 - Avoid crash: do not check whether DirPort is reachable when we
15615 are suppressing it because of hibernation.
15616 - Make --hash-password not crash on exit.
15619 Changes in version 0.1.1.8-alpha - 2005-10-07
15620 o New features (major):
15621 - Clients don't download or use the directory anymore. Now they
15622 download and use network-statuses from the trusted dirservers,
15623 and fetch individual server descriptors as needed from mirrors.
15624 See dir-spec.txt for all the gory details.
15625 - Be more conservative about whether to advertise our DirPort.
15626 The main change is to not advertise if we're running at capacity
15627 and either a) we could hibernate or b) our capacity is low and
15628 we're using a default DirPort.
15629 - Use OpenSSL's AES when OpenSSL has version 0.9.7 or later.
15631 o New features (minor):
15632 - Try to be smart about when to retry network-status and
15633 server-descriptor fetches. Still needs some tuning.
15634 - Stop parsing, storing, or using running-routers output (but
15635 mirrors still cache and serve it).
15636 - Consider a threshold of versioning dirservers (dirservers who have
15637 an opinion about which Tor versions are still recommended) before
15638 deciding whether to warn the user that he's obsolete.
15639 - Dirservers can now reject/invalidate by key and IP, with the
15640 config options "AuthDirInvalid" and "AuthDirReject". This is
15641 useful since currently we automatically list servers as running
15642 and usable even if we know they're jerks.
15643 - Provide dire warnings to any users who set DirServer; move it out
15644 of torrc.sample and into torrc.complete.
15645 - Add MyFamily to torrc.sample in the server section.
15646 - Add nicknames to the DirServer line, so we can refer to them
15647 without requiring all our users to memorize their IP addresses.
15648 - When we get an EOF or a timeout on a directory connection, note
15649 how many bytes of serverdesc we are dropping. This will help
15650 us determine whether it is smart to parse incomplete serverdesc
15652 - Add a new function to "change pseudonyms" -- that is, to stop
15653 using any currently-dirty circuits for new streams, so we don't
15654 link new actions to old actions. Currently it's only called on
15655 HUP (or SIGNAL RELOAD).
15656 - On sighup, if UseHelperNodes changed to 1, use new circuits.
15657 - Start using RAND_bytes rather than RAND_pseudo_bytes from
15658 OpenSSL. Also, reseed our entropy every hour, not just at
15659 startup. And entropy in 512-bit chunks, not 160-bit chunks.
15661 o Fixes on 0.1.1.7-alpha:
15662 - Nobody ever implemented EVENT_ADDRMAP for control protocol
15663 version 0, so don't let version 0 controllers ask for it.
15664 - If you requested something with too many newlines via the
15665 v1 controller protocol, you could crash tor.
15666 - Fix a number of memory leaks, including some pretty serious ones.
15667 - Re-enable DirPort testing again, so Tor servers will be willing
15668 to advertise their DirPort if it's reachable.
15669 - On TLS handshake, only check the other router's nickname against
15670 its expected nickname if is_named is set.
15672 o Fixes forward-ported from 0.1.0.15:
15673 - Don't crash when we don't have any spare file descriptors and we
15674 try to spawn a dns or cpu worker.
15675 - Make the numbers in read-history and write-history into uint64s,
15676 so they don't overflow and publish negatives in the descriptor.
15678 o Fixes on 0.1.0.x:
15679 - For the OS X package's modified privoxy config file, comment
15680 out the "logfile" line so we don't log everything passed
15682 - We were whining about using socks4 or socks5-with-local-lookup
15683 even when it's an IP in the "virtual" range we designed exactly
15685 - We were leaking some memory every time the client changes IPs.
15686 - Never call free() on tor_malloc()d memory. This will help us
15687 use dmalloc to detect memory leaks.
15688 - Check for named servers when looking them up by nickname;
15689 warn when we'recalling a non-named server by its nickname;
15690 don't warn twice about the same name.
15691 - Try to list MyFamily elements by key, not by nickname, and warn
15692 if we've not heard of the server.
15693 - Make windows platform detection (uname equivalent) smarter.
15694 - It turns out sparc64 doesn't like unaligned access either.
15697 Changes in version 0.1.0.15 - 2005-09-23
15698 o Bugfixes on 0.1.0.x:
15699 - Reject ports 465 and 587 (spam targets) in default exit policy.
15700 - Don't crash when we don't have any spare file descriptors and we
15701 try to spawn a dns or cpu worker.
15702 - Get rid of IgnoreVersion undocumented config option, and make us
15703 only warn, never exit, when we're running an obsolete version.
15704 - Don't try to print a null string when your server finds itself to
15705 be unreachable and the Address config option is empty.
15706 - Make the numbers in read-history and write-history into uint64s,
15707 so they don't overflow and publish negatives in the descriptor.
15708 - Fix a minor memory leak in smartlist_string_remove().
15709 - We were only allowing ourselves to upload a server descriptor at
15710 most every 20 minutes, even if it changed earlier than that.
15711 - Clean up log entries that pointed to old URLs.
15714 Changes in version 0.1.1.7-alpha - 2005-09-14
15715 o Fixes on 0.1.1.6-alpha:
15716 - Exit servers were crashing when people asked them to make a
15717 connection to an address not in their exit policy.
15718 - Looking up a non-existent stream for a v1 control connection would
15720 - Fix a seg fault if we ask a dirserver for a descriptor by
15721 fingerprint but he doesn't know about him.
15722 - SETCONF was appending items to linelists, not clearing them.
15723 - SETCONF SocksBindAddress killed Tor if it fails to bind. Now back
15724 out and refuse the setconf if it would fail.
15725 - Downgrade the dirserver log messages when whining about
15729 - Add Peter Palfrader's check-tor script to tor/contrib/
15730 It lets you easily check whether a given server (referenced by
15731 nickname) is reachable by you.
15732 - Numerous changes to move towards client-side v2 directories. Not
15735 o Fixes on 0.1.0.x:
15736 - If the user gave tor an odd number of command-line arguments,
15737 we were silently ignoring the last one. Now we complain and fail.
15738 [This wins the oldest-bug prize -- this bug has been present since
15739 November 2002, as released in Tor 0.0.0.]
15740 - Do not use unaligned memory access on alpha, mips, or mipsel.
15741 It *works*, but is very slow, so we treat them as if it doesn't.
15742 - Retry directory requests if we fail to get an answer we like
15743 from a given dirserver (we were retrying before, but only if
15744 we fail to connect).
15745 - When writing the RecommendedVersions line, sort them first.
15746 - When the client asked for a rendezvous port that the hidden
15747 service didn't want to provide, we were sending an IP address
15748 back along with the end cell. Fortunately, it was zero. But stop
15750 - Correct "your server is reachable" log entries to indicate that
15751 it was self-testing that told us so.
15754 Changes in version 0.1.1.6-alpha - 2005-09-09
15755 o Fixes on 0.1.1.5-alpha:
15756 - We broke fascistfirewall in 0.1.1.5-alpha. Oops.
15757 - Fix segfault in unit tests in 0.1.1.5-alpha. Oops.
15758 - Fix bug with tor_memmem finding a match at the end of the string.
15759 - Make unit tests run without segfaulting.
15760 - Resolve some solaris x86 compile warnings.
15761 - Handle duplicate lines in approved-routers files without warning.
15762 - Fix bug where as soon as a server refused any requests due to his
15763 exit policy (e.g. when we ask for localhost and he tells us that's
15764 127.0.0.1 and he won't do it), we decided he wasn't obeying his
15765 exit policy using him for any exits.
15766 - Only do openssl hardware accelerator stuff if openssl version is
15769 o New controller features/fixes:
15770 - Add a "RESETCONF" command so you can set config options like
15771 AllowUnverifiedNodes and LongLivedPorts to "". Also, if you give
15772 a config option in the torrc with no value, then it clears it
15773 entirely (rather than setting it to its default).
15774 - Add a "GETINFO config-file" to tell us where torrc is.
15775 - Avoid sending blank lines when GETINFO replies should be empty.
15776 - Add a QUIT command for the controller (for using it manually).
15777 - Fix a bug in SAVECONF that was adding default dirservers and
15778 other redundant entries to the torrc file.
15780 o Start on the new directory design:
15781 - Generate, publish, cache, serve new network-status format.
15782 - Publish individual descriptors (by fingerprint, by "all", and by
15784 - Publish client and server recommended versions separately.
15785 - Allow tor_gzip_uncompress() to handle multiple concatenated
15786 compressed strings. Serve compressed groups of router
15787 descriptors. The compression logic here could be more
15789 - Distinguish v1 authorities (all currently trusted directories)
15790 from v2 authorities (all trusted directories).
15791 - Change DirServers config line to note which dirs are v1 authorities.
15792 - Add configuration option "V1AuthoritativeDirectory 1" which
15793 moria1, moria2, and tor26 should set.
15794 - Remove option when getting directory cache to see whether they
15795 support running-routers; they all do now. Replace it with one
15796 to see whether caches support v2 stuff.
15799 - Dirservers now do their own external reachability testing of each
15800 Tor server, and only list them as running if they've been found to
15801 be reachable. We also send back warnings to the server's logs if
15802 it uploads a descriptor that we already believe is unreachable.
15803 - Implement exit enclaves: if we know an IP address for the
15804 destination, and there's a running Tor server at that address
15805 which allows exit to the destination, then extend the circuit to
15806 that exit first. This provides end-to-end encryption and end-to-end
15807 authentication. Also, if the user wants a .exit address or enclave,
15808 use 4 hops rather than 3, and cannibalize a general circ for it
15810 - Permit transitioning from ORPort=0 to ORPort!=0, and back, from the
15811 controller. Also, rotate dns and cpu workers if the controller
15812 changes options that will affect them; and initialize the dns
15813 worker cache tree whether or not we start out as a server.
15814 - Only upload a new server descriptor when options change, 18
15815 hours have passed, uptime is reset, or bandwidth changes a lot.
15816 - Check [X-]Forwarded-For headers in HTTP requests when generating
15817 log messages. This lets people run dirservers (and caches) behind
15818 Apache but still know which IP addresses are causing warnings.
15820 o Config option changes:
15821 - Replace (Fascist)Firewall* config options with a new
15822 ReachableAddresses option that understands address policies.
15823 For example, "ReachableAddresses *:80,*:443"
15824 - Get rid of IgnoreVersion undocumented config option, and make us
15825 only warn, never exit, when we're running an obsolete version.
15826 - Make MonthlyAccountingStart config option truly obsolete now.
15828 o Fixes on 0.1.0.x:
15829 - Reject ports 465 and 587 in the default exit policy, since
15830 people have started using them for spam too.
15831 - It turns out we couldn't bootstrap a network since we added
15832 reachability detection in 0.1.0.1-rc. Good thing the Tor network
15833 has never gone down. Add an AssumeReachable config option to let
15834 servers and dirservers bootstrap. When we're trying to build a
15835 high-uptime or high-bandwidth circuit but there aren't enough
15836 suitable servers, try being less picky rather than simply failing.
15837 - Our logic to decide if the OR we connected to was the right guy
15838 was brittle and maybe open to a mitm for unverified routers.
15839 - We weren't cannibalizing circuits correctly for
15840 CIRCUIT_PURPOSE_C_ESTABLISH_REND and
15841 CIRCUIT_PURPOSE_S_ESTABLISH_INTRO, so we were being forced to
15842 build those from scratch. This should make hidden services faster.
15843 - Predict required circuits better, with an eye toward making hidden
15844 services faster on the service end.
15845 - Retry streams if the exit node sends back a 'misc' failure. This
15846 should result in fewer random failures. Also, after failing
15847 from resolve failed or misc, reset the num failures, so we give
15848 it a fair shake next time we try.
15849 - Clean up the rendezvous warn log msgs, and downgrade some to info.
15850 - Reduce severity on logs about dns worker spawning and culling.
15851 - When we're shutting down and we do something like try to post a
15852 server descriptor or rendezvous descriptor, don't complain that
15853 we seem to be unreachable. Of course we are, we're shutting down.
15854 - Add TTLs to RESOLVED, CONNECTED, and END_REASON_EXITPOLICY cells.
15855 We don't use them yet, but maybe one day our DNS resolver will be
15856 able to discover them.
15857 - Make ContactInfo mandatory for authoritative directory servers.
15858 - Require server descriptors to list IPv4 addresses -- hostnames
15859 are no longer allowed. This also fixes some potential security
15860 problems with people providing hostnames as their address and then
15861 preferentially resolving them to partition users.
15862 - Change log line for unreachability to explicitly suggest /etc/hosts
15863 as the culprit. Also make it clearer what IP address and ports we're
15864 testing for reachability.
15865 - Put quotes around user-supplied strings when logging so users are
15866 more likely to realize if they add bad characters (like quotes)
15868 - Let auth dir servers start without specifying an Address config
15870 - Make unit tests (and other invocations that aren't the real Tor)
15871 run without launching listeners, creating subdirectories, and so on.
15874 Changes in version 0.1.1.5-alpha - 2005-08-08
15875 o Bugfixes included in 0.1.0.14.
15877 o Bugfixes on 0.1.0.x:
15878 - If you write "HiddenServicePort 6667 127.0.0.1 6668" in your
15879 torrc rather than "HiddenServicePort 6667 127.0.0.1:6668",
15880 it would silently using ignore the 6668.
15883 Changes in version 0.1.0.14 - 2005-08-08
15884 o Bugfixes on 0.1.0.x:
15885 - Fix the other half of the bug with crypto handshakes
15887 - Fix an assert trigger if you send a 'signal term' via the
15888 controller when it's listening for 'event info' messages.
15891 Changes in version 0.1.1.4-alpha - 2005-08-04
15892 o Bugfixes included in 0.1.0.13.
15895 - Improve tor_gettimeofday() granularity on windows.
15896 - Make clients regenerate their keys when their IP address changes.
15897 - Implement some more GETINFO goodness: expose helper nodes, config
15898 options, getinfo keys.
15901 Changes in version 0.1.0.13 - 2005-08-04
15902 o Bugfixes on 0.1.0.x:
15903 - Fix a critical bug in the security of our crypto handshakes.
15904 - Fix a size_t underflow in smartlist_join_strings2() that made
15905 it do bad things when you hand it an empty smartlist.
15906 - Fix Windows installer to ship Tor license (thanks to Aphex for
15907 pointing out this oversight) and put a link to the doc directory
15909 - Explicitly set no-unaligned-access for sparc: it turns out the
15910 new gcc's let you compile broken code, but that doesn't make it
15914 Changes in version 0.1.1.3-alpha - 2005-07-23
15915 o Bugfixes on 0.1.1.2-alpha:
15916 - Fix a bug in handling the controller's "post descriptor"
15918 - Fix several bugs in handling the controller's "extend circuit"
15920 - Fix a bug in handling the controller's "stream status" event.
15921 - Fix an assert failure if we have a controller listening for
15922 circuit events and we go offline.
15923 - Re-allow hidden service descriptors to publish 0 intro points.
15924 - Fix a crash when generating your hidden service descriptor if
15925 you don't have enough intro points already.
15927 o New features on 0.1.1.2-alpha:
15928 - New controller function "getinfo accounting", to ask how
15929 many bytes we've used in this time period.
15930 - Experimental support for helper nodes: a lot of the risk from
15931 a small static adversary comes because users pick new random
15932 nodes every time they rebuild a circuit. Now users will try to
15933 stick to the same small set of entry nodes if they can. Not
15934 enabled by default yet.
15936 o Bugfixes on 0.1.0.12:
15937 - If you're an auth dir server, always publish your dirport,
15938 even if you haven't yet found yourself to be reachable.
15939 - Fix a size_t underflow in smartlist_join_strings2() that made
15940 it do bad things when you hand it an empty smartlist.
15943 Changes in version 0.1.0.12 - 2005-07-18
15944 o New directory servers:
15945 - tor26 has changed IP address.
15947 o Bugfixes on 0.1.0.x:
15948 - Fix a possible double-free in tor_gzip_uncompress().
15949 - When --disable-threads is set, do not search for or link against
15950 pthreads libraries.
15951 - Don't trigger an assert if an authoritative directory server
15952 claims its dirport is 0.
15953 - Fix bug with removing Tor as an NT service: some people were
15954 getting "The service did not return an error." Thanks to Matt
15958 Changes in version 0.1.1.2-alpha - 2005-07-15
15959 o New directory servers:
15960 - tor26 has changed IP address.
15962 o Bugfixes on 0.1.0.x, crashes/leaks:
15963 - Port the servers-not-obeying-their-exit-policies fix from
15965 - Fix an fd leak in start_daemon().
15966 - On Windows, you can't always reopen a port right after you've
15967 closed it. So change retry_listeners() to only close and re-open
15968 ports that have changed.
15969 - Fix a possible double-free in tor_gzip_uncompress().
15971 o Bugfixes on 0.1.0.x, usability:
15972 - When tor_socketpair() fails in Windows, give a reasonable
15973 Windows-style errno back.
15974 - Let people type "tor --install" as well as "tor -install" when
15976 want to make it an NT service.
15977 - NT service patch from Matt Edman to improve error messages.
15978 - When the controller asks for a config option with an abbreviated
15979 name, give the full name in our response.
15980 - Correct the man page entry on TrackHostExitsExpire.
15981 - Looks like we were never delivering deflated (i.e. compressed)
15982 running-routers lists, even when asked. Oops.
15983 - When --disable-threads is set, do not search for or link against
15984 pthreads libraries.
15986 o Bugfixes on 0.1.1.x:
15987 - Fix a seg fault with autodetecting which controller version is
15991 - New hidden service descriptor format: put a version in it, and
15992 let people specify introduction/rendezvous points that aren't
15993 in "the directory" (which is subjective anyway).
15994 - Allow the DEBUG controller event to work again. Mark certain log
15995 entries as "don't tell this to controllers", so we avoid cycles.
15998 Changes in version 0.1.0.11 - 2005-06-30
15999 o Bugfixes on 0.1.0.x:
16000 - Fix major security bug: servers were disregarding their
16001 exit policies if clients behaved unexpectedly.
16002 - Make OS X init script check for missing argument, so we don't
16003 confuse users who invoke it incorrectly.
16004 - Fix a seg fault in "tor --hash-password foo".
16005 - The MAPADDRESS control command was broken.
16008 Changes in version 0.1.1.1-alpha - 2005-06-29
16010 - Make OS X init script check for missing argument, so we don't
16011 confuse users who invoke it incorrectly.
16012 - Fix a seg fault in "tor --hash-password foo".
16013 - Fix a possible way to DoS dirservers.
16014 - When we complain that your exit policy implicitly allows local or
16015 private address spaces, name them explicitly so operators can
16017 - Make the log message less scary when all the dirservers are
16018 temporarily unreachable.
16019 - We were printing the number of idle dns workers incorrectly when
16023 - Revised controller protocol (version 1) that uses ascii rather
16024 than binary. Add supporting libraries in python and java so you
16025 can use the controller from your applications without caring how
16026 our protocol works.
16027 - Spiffy new support for crypto hardware accelerators. Can somebody
16031 Changes in version 0.0.9.10 - 2005-06-16
16032 o Bugfixes on 0.0.9.x (backported from 0.1.0.10):
16033 - Refuse relay cells that claim to have a length larger than the
16034 maximum allowed. This prevents a potential attack that could read
16035 arbitrary memory (e.g. keys) from an exit server's process
16039 Changes in version 0.1.0.10 - 2005-06-14
16040 o Allow a few EINVALs from libevent before dying. Warn on kqueue with
16041 libevent before 1.1a.
16044 Changes in version 0.1.0.9-rc - 2005-06-09
16046 - Reset buf->highwater every time buf_shrink() is called, not just on
16047 a successful shrink. This was causing significant memory bloat.
16048 - Fix buffer overflow when checking hashed passwords.
16049 - Security fix: if seeding the RNG on Win32 fails, quit.
16050 - Allow seeding the RNG on Win32 even when you're not running as
16052 - Disable threading on Solaris too. Something is wonky with it,
16053 cpuworkers, and reentrant libs.
16054 - Reenable the part of the code that tries to flush as soon as an
16055 OR outbuf has a full TLS record available. Perhaps this will make
16056 OR outbufs not grow as huge except in rare cases, thus saving lots
16057 of CPU time plus memory.
16058 - Reject malformed .onion addresses rather then passing them on as
16059 normal web requests.
16060 - Adapt patch from Adam Langley: fix possible memory leak in
16061 tor_lookup_hostname().
16062 - Initialize libevent later in the startup process, so the logs are
16063 already established by the time we start logging libevent warns.
16064 - Use correct errno on win32 if libevent fails.
16065 - Check and warn about known-bad/slow libevent versions.
16066 - Pay more attention to the ClientOnly config option.
16067 - Have torctl.in/tor.sh.in check for location of su binary (needed
16069 - Correct/add man page entries for LongLivedPorts, ExitPolicy,
16070 KeepalivePeriod, ClientOnly, NoPublish, HttpProxy, HttpsProxy,
16071 HttpProxyAuthenticator
16072 - Stop warning about sigpipes in the logs. We're going to
16073 pretend that getting these occassionally is normal and fine.
16074 - Resolve OS X installer bugs: stop claiming to be 0.0.9.2 in
16076 installer screens; and don't put stuff into StartupItems unless
16077 the user asks you to.
16078 - Require servers that use the default dirservers to have public IP
16079 addresses. We have too many servers that are configured with private
16080 IPs and their admins never notice the log entries complaining that
16081 their descriptors are being rejected.
16082 - Add OSX uninstall instructions. An actual uninstall script will
16086 Changes in version 0.1.0.8-rc - 2005-05-23
16088 - It turns out that kqueue on OS X 10.3.9 was causing kernel
16089 panics. Disable kqueue on all OS X Tors.
16090 - Fix RPM: remove duplicate line accidentally added to the rpm
16092 - Disable threads on openbsd too, since its gethostaddr is not
16094 - Tolerate libevent 0.8 since it still works, even though it's
16096 - Enable building on Red Hat 9.0 again.
16097 - Allow the middle hop of the testing circuit to be running any
16098 version, now that most of them have the bugfix to let them connect
16099 to unknown servers. This will allow reachability testing to work
16100 even when 0.0.9.7-0.0.9.9 become obsolete.
16101 - Handle relay cells with rh.length too large. This prevents
16102 a potential attack that could read arbitrary memory (maybe even
16103 keys) from the exit server's process.
16104 - We screwed up the dirport reachability testing when we don't yet
16105 have a cached version of the directory. Hopefully now fixed.
16106 - Clean up router_load_single_router() (used by the controller),
16107 so it doesn't seg fault on error.
16108 - Fix a minor memory leak when somebody establishes an introduction
16109 point at your Tor server.
16110 - If a socks connection ends because read fails, don't warn that
16111 you're not sending a socks reply back.
16114 - Add HttpProxyAuthenticator config option too, that works like
16115 the HttpsProxyAuthenticator config option.
16116 - Encode hashed controller passwords in hex instead of base64,
16117 to make it easier to write controllers.
16120 Changes in version 0.1.0.7-rc - 2005-05-17
16122 - Fix a bug in the OS X package installer that prevented it from
16123 installing on Tiger.
16124 - Fix a script bug in the OS X package installer that made it
16125 complain during installation.
16126 - Find libevent even if it's hiding in /usr/local/ and your
16127 CFLAGS and LDFLAGS don't tell you to look there.
16128 - Be able to link with libevent as a shared library (the default
16129 after 1.0d), even if it's hiding in /usr/local/lib and even
16130 if you haven't added /usr/local/lib to your /etc/ld.so.conf,
16131 assuming you're running gcc. Otherwise fail and give a useful
16133 - Fix a bug in the RPM packager: set home directory for _tor to
16134 something more reasonable when first installing.
16135 - Free a minor amount of memory that is still reachable on exit.
16138 Changes in version 0.1.0.6-rc - 2005-05-14
16140 - Implement --disable-threads configure option. Disable threads on
16141 netbsd by default, because it appears to have no reentrant resolver
16143 - Apple's OS X 10.4.0 ships with a broken kqueue. The new libevent
16144 release (1.1) detects and disables kqueue if it's broken.
16145 - Append default exit policy before checking for implicit internal
16146 addresses. Now we don't log a bunch of complaints on startup
16147 when using the default exit policy.
16148 - Some people were putting "Address " in their torrc, and they had
16149 a buggy resolver that resolved " " to 0.0.0.0. Oops.
16150 - If DataDir is ~/.tor, and that expands to /.tor, then default to
16151 LOCALSTATEDIR/tor instead.
16152 - Fix fragmented-message bug in TorControl.py.
16153 - Resolve a minor bug which would prevent unreachable dirports
16154 from getting suppressed in the published descriptor.
16155 - When the controller gave us a new descriptor, we weren't resolving
16156 it immediately, so Tor would think its address was 0.0.0.0 until
16157 we fetched a new directory.
16158 - Fix an uppercase/lowercase case error in suppressing a bogus
16159 libevent warning on some Linuxes.
16162 - Begin scrubbing sensitive strings from logs by default. Turn off
16163 the config option SafeLogging if you need to do debugging.
16164 - Switch to a new buffer management algorithm, which tries to avoid
16165 reallocing and copying quite as much. In first tests it looks like
16166 it uses *more* memory on average, but less cpu.
16167 - First cut at support for "create-fast" cells. Clients can use
16168 these when extending to their first hop, since the TLS already
16169 provides forward secrecy and authentication. Not enabled on
16171 - When dirservers refuse a router descriptor, we now log its
16172 contactinfo, platform, and the poster's IP address.
16173 - Call tor_free_all instead of connections_free_all after forking, to
16174 save memory on systems that need to fork.
16175 - Whine at you if you're a server and you don't set your contactinfo.
16176 - Implement --verify-config command-line option to check if your torrc
16177 is valid without actually launching Tor.
16178 - Rewrite address "serifos.exit" to "localhost.serifos.exit"
16179 rather than just rejecting it.
16182 Changes in version 0.1.0.5-rc - 2005-04-27
16184 - Stop trying to print a null pointer if an OR conn fails because
16185 we didn't like its cert.
16187 - Switch our internal buffers implementation to use a ring buffer,
16188 to hopefully improve performance for fast servers a lot.
16189 - Add HttpsProxyAuthenticator support (basic auth only), based
16190 on patch from Adam Langley.
16191 - Bump the default BandwidthRate from 1 MB to 2 MB, to accommodate
16192 the fast servers that have been joining lately.
16193 - Give hidden service accesses extra time on the first attempt,
16194 since 60 seconds is often only barely enough. This might improve
16196 - Improve performance for dirservers: stop re-parsing the whole
16197 directory every time you regenerate it.
16198 - Add more debugging info to help us find the weird dns freebsd
16199 pthreads bug; cleaner debug messages to help track future issues.
16202 Changes in version 0.0.9.9 - 2005-04-23
16203 o Bugfixes on 0.0.9.x:
16204 - If unofficial Tor clients connect and send weird TLS certs, our
16205 Tor server triggers an assert. This release contains a minimal
16206 backport from the broader fix that we put into 0.1.0.4-rc.
16209 Changes in version 0.1.0.4-rc - 2005-04-23
16211 - If unofficial Tor clients connect and send weird TLS certs, our
16212 Tor server triggers an assert. Stop asserting, and start handling
16213 TLS errors better in other situations too.
16214 - When the controller asks us to tell it about all the debug-level
16215 logs, it turns out we were generating debug-level logs while
16216 telling it about them, which turns into a bad loop. Now keep
16217 track of whether you're sending a debug log to the controller,
16218 and don't log when you are.
16219 - Fix the "postdescriptor" feature of the controller interface: on
16220 non-complete success, only say "done" once.
16222 - Clients are now willing to load balance over up to 2mB, not 1mB,
16223 of advertised bandwidth capacity.
16224 - Add a NoPublish config option, so you can be a server (e.g. for
16225 testing running Tor servers in other Tor networks) without
16226 publishing your descriptor to the primary dirservers.
16229 Changes in version 0.1.0.3-rc - 2005-04-08
16230 o Improvements on 0.1.0.2-rc:
16231 - Client now retries when streams end early for 'hibernating' or
16232 'resource limit' reasons, rather than failing them.
16233 - More automated handling for dirserver operators:
16234 - Automatically approve nodes running 0.1.0.2-rc or later,
16235 now that the the reachability detection stuff is working.
16236 - Now we allow two unverified servers with the same nickname
16237 but different keys. But if a nickname is verified, only that
16238 nickname+key are allowed.
16239 - If you're an authdirserver connecting to an address:port,
16240 and it's not the OR you were expecting, forget about that
16241 descriptor. If he *was* the one you were expecting, then forget
16242 about all other descriptors for that address:port.
16243 - Allow servers to publish descriptors from 12 hours in the future.
16244 Corollary: only whine about clock skew from the dirserver if
16245 he's a trusted dirserver (since now even verified servers could
16246 have quite wrong clocks).
16247 - Adjust maximum skew and age for rendezvous descriptors: let skew
16248 be 48 hours rather than 90 minutes.
16249 - Efficiency improvements:
16250 - Keep a big splay tree of (circid,orconn)->circuit mappings to make
16251 it much faster to look up a circuit for each relay cell.
16252 - Remove most calls to assert_all_pending_dns_resolves_ok(),
16253 since they're eating our cpu on exit nodes.
16254 - Stop wasting time doing a case insensitive comparison for every
16255 dns name every time we do any lookup. Canonicalize the names to
16256 lowercase and be done with it.
16257 - Start sending 'truncated' cells back rather than destroy cells,
16258 if the circuit closes in front of you. This means we won't have
16259 to abandon partially built circuits.
16260 - Only warn once per nickname from add_nickname_list_to_smartlist
16261 per failure, so an entrynode or exitnode choice that's down won't
16263 - Put a note in the torrc about abuse potential with the default
16265 - Revise control spec and implementation to allow all log messages to
16266 be sent to controller with their severities intact (suggested by
16267 Matt Edman). Update TorControl to handle new log event types.
16268 - Provide better explanation messages when controller's POSTDESCRIPTOR
16270 - Stop putting nodename in the Platform string in server descriptors.
16271 It doesn't actually help, and it is confusing/upsetting some people.
16273 o Bugfixes on 0.1.0.2-rc:
16274 - We were printing the host mask wrong in exit policies in server
16275 descriptors. This isn't a critical bug though, since we were still
16276 obeying the exit policy internally.
16277 - Fix Tor when compiled with libevent but without pthreads: move
16278 connection_unregister() from _connection_free() to
16280 - Fix an assert trigger (already fixed in 0.0.9.x): when we have
16281 the rare mysterious case of accepting a conn on 0.0.0.0:0, then
16282 when we look through the connection array, we'll find any of the
16283 cpu/dnsworkers. This is no good.
16285 o Bugfixes on 0.0.9.8:
16286 - Fix possible bug on threading platforms (e.g. win32) which was
16287 leaking a file descriptor whenever a cpuworker or dnsworker died.
16288 - When using preferred entry or exit nodes, ignore whether the
16289 circuit wants uptime or capacity. They asked for the nodes, they
16291 - chdir() to your datadirectory at the *end* of the daemonize process,
16292 not the beginning. This was a problem because the first time you
16293 run tor, if your datadir isn't there, and you have runasdaemon set
16294 to 1, it will try to chdir to it before it tries to create it. Oops.
16295 - Handle changed router status correctly when dirserver reloads
16296 fingerprint file. We used to be dropping all unverified descriptors
16297 right then. The bug was hidden because we would immediately
16298 fetch a directory from another dirserver, which would include the
16299 descriptors we just dropped.
16300 - When we're connecting to an OR and he's got a different nickname/key
16301 than we were expecting, only complain loudly if we're an OP or a
16302 dirserver. Complaining loudly to the OR admins just confuses them.
16303 - Tie MAX_DIR_SIZE to MAX_BUF_SIZE, so now directory sizes won't get
16304 artificially capped at 500kB.
16307 Changes in version 0.0.9.8 - 2005-04-07
16308 o Bugfixes on 0.0.9.x:
16309 - We have a bug that I haven't found yet. Sometimes, very rarely,
16310 cpuworkers get stuck in the 'busy' state, even though the cpuworker
16311 thinks of itself as idle. This meant that no new circuits ever got
16312 established. Here's a workaround to kill any cpuworker that's been
16313 busy for more than 100 seconds.
16316 Changes in version 0.1.0.2-rc - 2005-04-01
16317 o Bugfixes on 0.1.0.1-rc:
16318 - Fixes on reachability detection:
16319 - Don't check for reachability while hibernating.
16320 - If ORPort is reachable but DirPort isn't, still publish the
16321 descriptor, but zero out DirPort until it's found reachable.
16322 - When building testing circs for ORPort testing, use only
16323 high-bandwidth nodes, so fewer circuits fail.
16324 - Complain about unreachable ORPort separately from unreachable
16325 DirPort, so the user knows what's going on.
16326 - Make sure we only conclude ORPort reachability if we didn't
16327 initiate the conn. Otherwise we could falsely conclude that
16328 we're reachable just because we connected to the guy earlier
16329 and he used that same pipe to extend to us.
16330 - Authdirservers shouldn't do ORPort reachability detection,
16331 since they're in clique mode, so it will be rare to find a
16332 server not already connected to them.
16333 - When building testing circuits, always pick middle hops running
16334 Tor 0.0.9.7, so we avoid the "can't extend to unknown routers"
16335 bug. (This is a kludge; it will go away when 0.0.9.x becomes
16337 - When we decide we're reachable, actually publish our descriptor
16339 - Fix bug in redirectstream in the controller.
16340 - Fix the state descriptor strings so logs don't claim edge streams
16341 are in a different state than they actually are.
16342 - Use recent libevent features when possible (this only really affects
16343 win32 and osx right now, because the new libevent with these
16344 features hasn't been released yet). Add code to suppress spurious
16346 - Prevent possible segfault in connection_close_unattached_ap().
16347 - Fix newlines on torrc in win32.
16348 - Improve error msgs when tor-resolve fails.
16350 o Improvements on 0.0.9.x:
16351 - New experimental script tor/contrib/ExerciseServer.py (needs more
16352 work) that uses the controller interface to build circuits and
16353 fetch pages over them. This will help us bootstrap servers that
16354 have lots of capacity but haven't noticed it yet.
16355 - New experimental script tor/contrib/PathDemo.py (needs more work)
16356 that uses the controller interface to let you choose whole paths
16358 "<hostname>.<path,separated by dots>.<length of path>.path"
16359 - When we've connected to an OR and handshaked but didn't like
16360 the result, we were closing the conn without sending destroy
16361 cells back for pending circuits. Now send those destroys.
16364 Changes in version 0.0.9.7 - 2005-04-01
16365 o Bugfixes on 0.0.9.x:
16366 - Fix another race crash bug (thanks to Glenn Fink for reporting).
16367 - Compare identity to identity, not to nickname, when extending to
16368 a router not already in the directory. This was preventing us from
16369 extending to unknown routers. Oops.
16370 - Make sure to create OS X Tor user in <500 range, so we aren't
16371 creating actual system users.
16372 - Note where connection-that-hasn't-sent-end was marked, and fix
16373 a few really loud instances of this harmless bug (it's fixed more
16377 Changes in version 0.1.0.1-rc - 2005-03-28
16379 - Add reachability testing. Your Tor server will automatically try
16380 to see if its ORPort and DirPort are reachable from the outside,
16381 and it won't upload its descriptor until it decides they are.
16382 - Handle unavailable hidden services better. Handle slow or busy
16383 hidden services better.
16384 - Add support for CONNECTing through https proxies, with "HttpsProxy"
16386 - New exit policy: accept most low-numbered ports, rather than
16387 rejecting most low-numbered ports.
16388 - More Tor controller support (still experimental). See
16389 http://tor.eff.org/doc/control-spec.txt for all the new features,
16390 including signals to emulate unix signals from any platform;
16391 redirectstream; extendcircuit; mapaddress; getinfo; postdescriptor;
16392 closestream; closecircuit; etc.
16393 - Make nt services work and start on startup on win32 (based on
16394 patch by Matt Edman).
16395 - Add a new AddressMap config directive to rewrite incoming socks
16396 addresses. This lets you, for example, declare an implicit
16397 required exit node for certain sites.
16398 - Add a new TrackHostExits config directive to trigger addressmaps
16399 for certain incoming socks addresses -- for sites that break when
16400 your exit keeps changing (based on patch by Mike Perry).
16401 - Redo the client-side dns cache so it's just an addressmap too.
16402 - Notice when our IP changes, and reset stats/uptime/reachability.
16403 - When an application is using socks5, give him the whole variety of
16404 potential socks5 responses (connect refused, host unreachable, etc),
16405 rather than just "success" or "failure".
16406 - A more sane version numbering system. See
16407 http://tor.eff.org/cvs/tor/doc/version-spec.txt for details.
16408 - New contributed script "exitlist": a simple python script to
16409 parse directories and find Tor nodes that exit to listed
16411 - New contributed script "privoxy-tor-toggle" to toggle whether
16412 Privoxy uses Tor. Seems to be configured for Debian by default.
16413 - Report HTTP reasons to client when getting a response from directory
16414 servers -- so you can actually know what went wrong.
16415 - New config option MaxAdvertisedBandwidth which lets you advertise
16416 a low bandwidthrate (to not attract as many circuits) while still
16417 allowing a higher bandwidthrate in reality.
16419 o Robustness/stability fixes:
16420 - Make Tor use Niels Provos's libevent instead of its current
16421 poll-but-sometimes-select mess. This will let us use faster async
16422 cores (like epoll, kpoll, and /dev/poll), and hopefully work better
16424 - pthread support now too. This was forced because when we forked,
16425 we ended up wasting a lot of duplicate ram over time. Also switch
16426 to foo_r versions of some library calls to allow reentry and
16428 - Better handling for heterogeneous / unreliable nodes:
16429 - Annotate circuits w/ whether they aim to contain high uptime nodes
16430 and/or high capacity nodes. When building circuits, choose
16432 - This means that every single node in an intro rend circuit,
16433 not just the last one, will have a minimum uptime.
16434 - New config option LongLivedPorts to indicate application streams
16435 that will want high uptime circuits.
16436 - Servers reset uptime when a dir fetch entirely fails. This
16437 hopefully reflects stability of the server's network connectivity.
16438 - If somebody starts his tor server in Jan 2004 and then fixes his
16439 clock, don't make his published uptime be a year.
16440 - Reset published uptime when you wake up from hibernation.
16441 - Introduce a notion of 'internal' circs, which are chosen without
16442 regard to the exit policy of the last hop. Intro and rendezvous
16443 circs must be internal circs, to avoid leaking information. Resolve
16444 and connect streams can use internal circs if they want.
16445 - New circuit pooling algorithm: make sure to have enough circs around
16446 to satisfy any predicted ports, and also make sure to have 2 internal
16447 circs around if we've required internal circs lately (and with high
16448 uptime if we've seen that lately too).
16449 - Split NewCircuitPeriod option into NewCircuitPeriod (30 secs),
16450 which describes how often we retry making new circuits if current
16451 ones are dirty, and MaxCircuitDirtiness (10 mins), which describes
16452 how long we're willing to make use of an already-dirty circuit.
16453 - Cannibalize GENERAL circs to be C_REND, C_INTRO, S_INTRO, and S_REND
16454 circ as necessary, if there are any completed ones lying around
16455 when we try to launch one.
16456 - Make hidden services try to establish a rendezvous for 30 seconds,
16457 rather than for n (where n=3) attempts to build a circuit.
16458 - Change SHUTDOWN_WAIT_LENGTH from a fixed 30 secs to a config option
16459 "ShutdownWaitLength".
16460 - Try to be more zealous about calling connection_edge_end when
16461 things go bad with edge conns in connection.c.
16462 - Revise tor-spec to add more/better stream end reasons.
16463 - Revise all calls to connection_edge_end to avoid sending "misc",
16464 and to take errno into account where possible.
16467 - Fix a race condition that can trigger an assert, when we have a
16468 pending create cell and an OR connection fails right then.
16469 - Fix several double-mark-for-close bugs, e.g. where we were finding
16470 a conn for a cell even if that conn is already marked for close.
16471 - Make sequence of log messages when starting on win32 with no config
16472 file more reasonable.
16473 - When choosing an exit node for a new non-internal circ, don't take
16474 into account whether it'll be useful for any pending x.onion
16475 addresses -- it won't.
16476 - Turn addr_policy_compare from a tristate to a quadstate; this should
16477 help address our "Ah, you allow 1.2.3.4:80. You are a good choice
16478 for google.com" problem.
16479 - Make "platform" string in descriptor more accurate for Win32 servers,
16480 so it's not just "unknown platform".
16481 - Fix an edge case in parsing config options (thanks weasel).
16482 If they say "--" on the commandline, it's not an option.
16483 - Reject odd-looking addresses at the client (e.g. addresses that
16484 contain a colon), rather than having the server drop them because
16486 - tor-resolve requests were ignoring .exit if there was a working circuit
16487 they could use instead.
16488 - REUSEADDR on normal platforms means you can rebind to the port
16489 right after somebody else has let it go. But REUSEADDR on win32
16490 means to let you bind to the port _even when somebody else
16491 already has it bound_! So, don't do that on Win32.
16492 - Change version parsing logic: a version is "obsolete" if it is not
16493 recommended and (1) there is a newer recommended version in the
16494 same series, or (2) there are no recommended versions in the same
16495 series, but there are some recommended versions in a newer series.
16496 A version is "new" if it is newer than any recommended version in
16498 - Stop most cases of hanging up on a socks connection without sending
16502 - Require BandwidthRate to be at least 20kB/s for servers.
16503 - When a dirserver causes you to give a warn, mention which dirserver
16505 - New config option DirAllowPrivateAddresses for authdirservers.
16506 Now by default they refuse router descriptors that have non-IP or
16507 private-IP addresses.
16508 - Stop publishing socksport in the directory, since it's not
16509 actually meant to be public. For compatibility, publish a 0 there
16511 - Change DirFetchPeriod/StatusFetchPeriod to have a special "Be
16512 smart" value, that is low for servers and high for clients.
16513 - If our clock jumps forward by 100 seconds or more, assume something
16514 has gone wrong with our network and abandon all not-yet-used circs.
16515 - Warn when exit policy implicitly allows local addresses.
16516 - If we get an incredibly skewed timestamp from a dirserver mirror
16517 that isn't a verified OR, don't warn -- it's probably him that's
16519 - Since we ship our own Privoxy on OS X, tweak it so it doesn't write
16520 cookies to disk and doesn't log each web request to disk. (Thanks
16521 to Brett Carrington for pointing this out.)
16522 - When a client asks us for a dir mirror and we don't have one,
16523 launch an attempt to get a fresh one.
16524 - If we're hibernating and we get a SIGINT, exit immediately.
16525 - Add --with-dmalloc ./configure option, to track memory leaks.
16526 - And try to free all memory on closing, so we can detect what
16528 - Cache local dns resolves correctly even when they're .exit
16530 - Give a better warning when some other server advertises an
16531 ORPort that is actually an apache running ssl.
16532 - Add "opt hibernating 1" to server descriptor to make it clearer
16533 whether the server is hibernating.
16536 Changes in version 0.0.9.6 - 2005-03-24
16537 o Bugfixes on 0.0.9.x (crashes and asserts):
16538 - Add new end stream reasons to maintainance branch. Fix bug where
16539 reason (8) could trigger an assert. Prevent bug from recurring.
16540 - Apparently win32 stat wants paths to not end with a slash.
16541 - Fix assert triggers in assert_cpath_layer_ok(), where we were
16542 blowing away the circuit that conn->cpath_layer points to, then
16543 checking to see if the circ is well-formed. Backport check to make
16544 sure we dont use the cpath on a closed connection.
16545 - Prevent circuit_resume_edge_reading_helper() from trying to package
16546 inbufs for marked-for-close streams.
16547 - Don't crash on hup if your options->address has become unresolvable.
16548 - Some systems (like OS X) sometimes accept() a connection and tell
16549 you the remote host is 0.0.0.0:0. If this happens, due to some
16550 other mis-features, we get confused; so refuse the conn for now.
16552 o Bugfixes on 0.0.9.x (other):
16553 - Fix harmless but scary "Unrecognized content encoding" warn message.
16554 - Add new stream error reason: TORPROTOCOL reason means "you are not
16555 speaking a version of Tor I understand; say bye-bye to your stream."
16556 - Be willing to cache directories from up to ROUTER_MAX_AGE seconds
16557 into the future, now that we are more tolerant of skew. This
16558 resolves a bug where a Tor server would refuse to cache a directory
16559 because all the directories it gets are too far in the future;
16560 yet the Tor server never logs any complaints about clock skew.
16561 - Mac packaging magic: make man pages useable, and do not overwrite
16562 existing torrc files.
16563 - Make OS X log happily to /var/log/tor/tor.log
16566 Changes in version 0.0.9.5 - 2005-02-22
16567 o Bugfixes on 0.0.9.x:
16568 - Fix an assert race at exit nodes when resolve requests fail.
16569 - Stop picking unverified dir mirrors--it only leads to misery.
16570 - Patch from Matt Edman to make NT services work better. Service
16571 support is still not compiled into the executable by default.
16572 - Patch from Dmitri Bely so the Tor service runs better under
16573 the win32 SYSTEM account.
16574 - Make tor-resolve actually work (?) on Win32.
16575 - Fix a sign bug when getrlimit claims to have 4+ billion
16576 file descriptors available.
16577 - Stop refusing to start when bandwidthburst == bandwidthrate.
16578 - When create cells have been on the onion queue more than five
16579 seconds, just send back a destroy and take them off the list.
16582 Changes in version 0.0.9.4 - 2005-02-03
16583 o Bugfixes on 0.0.9:
16584 - Fix an assert bug that took down most of our servers: when
16585 a server claims to have 1 GB of bandwidthburst, don't
16587 - Don't crash as badly if we have spawned the max allowed number
16588 of dnsworkers, or we're out of file descriptors.
16589 - Block more file-sharing ports in the default exit policy.
16590 - MaxConn is now automatically set to the hard limit of max
16591 file descriptors we're allowed (ulimit -n), minus a few for
16593 - Give a clearer message when servers need to raise their
16594 ulimit -n when they start running out of file descriptors.
16595 - SGI Compatibility patches from Jan Schaumann.
16596 - Tolerate a corrupt cached directory better.
16597 - When a dirserver hasn't approved your server, list which one.
16598 - Go into soft hibernation after 95% of the bandwidth is used,
16599 not 99%. This is especially important for daily hibernators who
16600 have a small accounting max. Hopefully it will result in fewer
16601 cut connections when the hard hibernation starts.
16602 - Load-balance better when using servers that claim more than
16603 800kB/s of capacity.
16604 - Make NT services work (experimental, only used if compiled in).
16607 Changes in version 0.0.9.3 - 2005-01-21
16608 o Bugfixes on 0.0.9:
16609 - Backport the cpu use fixes from main branch, so busy servers won't
16610 need as much processor time.
16611 - Work better when we go offline and then come back, or when we
16612 run Tor at boot before the network is up. We do this by
16613 optimistically trying to fetch a new directory whenever an
16614 application request comes in and we think we're offline -- the
16615 human is hopefully a good measure of when the network is back.
16616 - Backport some minimal hidserv bugfixes: keep rend circuits open as
16617 long as you keep using them; actually publish hidserv descriptors
16618 shortly after they change, rather than waiting 20-40 minutes.
16619 - Enable Mac startup script by default.
16620 - Fix duplicate dns_cancel_pending_resolve reported by Giorgos Pallas.
16621 - When you update AllowUnverifiedNodes or FirewallPorts via the
16622 controller's setconf feature, we were always appending, never
16624 - When you update HiddenServiceDir via setconf, it was screwing up
16625 the order of reading the lines, making it fail.
16626 - Do not rewrite a cached directory back to the cache; otherwise we
16627 will think it is recent and not fetch a newer one on startup.
16628 - Workaround for webservers that lie about Content-Encoding: Tor
16629 now tries to autodetect compressed directories and compression
16630 itself. This lets us Proxypass dir fetches through apache.
16633 Changes in version 0.0.9.2 - 2005-01-04
16634 o Bugfixes on 0.0.9 (crashes and asserts):
16635 - Fix an assert on startup when the disk is full and you're logging
16637 - If you do socks4 with an IP of 0.0.0.x but *don't* provide a socks4a
16638 style address, then we'd crash.
16639 - Fix an assert trigger when the running-routers string we get from
16640 a dirserver is broken.
16641 - Make worker threads start and run on win32. Now win32 servers
16643 - Bandaid (not actually fix, but now it doesn't crash) an assert
16644 where the dns worker dies mysteriously and the main Tor process
16645 doesn't remember anything about the address it was resolving.
16647 o Bugfixes on 0.0.9 (Win32):
16648 - Workaround for brain-damaged __FILE__ handling on MSVC: keep Nick's
16649 name out of the warning/assert messages.
16650 - Fix a superficial "unhandled error on read" bug on win32.
16651 - The win32 installer no longer requires a click-through for our
16652 license, since our Free Software license grants rights but does not
16654 - Win32: When connecting to a dirserver fails, try another one
16655 immediately. (This was already working for non-win32 Tors.)
16656 - Stop trying to parse $HOME on win32 when hunting for default
16658 - Make tor-resolve.c work on win32 by calling network_init().
16660 o Bugfixes on 0.0.9 (other):
16661 - Make 0.0.9.x build on Solaris again.
16662 - Due to a fencepost error, we were blowing away the \n when reporting
16663 confvalue items in the controller. So asking for multiple config
16664 values at once couldn't work.
16665 - When listing circuits that are pending on an opening OR connection,
16666 if we're an OR we were listing circuits that *end* at us as
16667 being pending on every listener, dns/cpu worker, etc. Stop that.
16668 - Dirservers were failing to create 'running-routers' or 'directory'
16669 strings if we had more than some threshold of routers. Fix them so
16670 they can handle any number of routers.
16671 - Fix a superficial "Duplicate mark for close" bug.
16672 - Stop checking for clock skew for OR connections, even for servers.
16673 - Fix a fencepost error that was chopping off the last letter of any
16674 nickname that is the maximum allowed nickname length.
16675 - Update URLs in log messages so they point to the new website.
16676 - Fix a potential problem in mangling server private keys while
16677 writing to disk (not triggered yet, as far as we know).
16678 - Include the licenses for other free software we include in Tor,
16679 now that we're shipping binary distributions more regularly.
16682 Changes in version 0.0.9.1 - 2004-12-15
16683 o Bugfixes on 0.0.9:
16684 - Make hibernation actually work.
16685 - Make HashedControlPassword config option work.
16686 - When we're reporting event circuit status to a controller,
16687 don't use the stream status code.
16690 Changes in version 0.0.9 - 2004-12-12
16692 - Clean up manpage and torrc.sample file.
16693 - Clean up severities and text of log warnings.
16695 - Make servers trigger an assert when they enter hibernation.
16698 Changes in version 0.0.9rc7 - 2004-12-08
16699 o Bugfixes on 0.0.9rc:
16700 - Fix a stack-trashing crash when an exit node begins hibernating.
16701 - Avoid looking at unallocated memory while considering which
16702 ports we need to build circuits to cover.
16703 - Stop a sigpipe: when an 'end' cell races with eof from the app,
16704 we shouldn't hold-open-until-flush if the eof arrived first.
16705 - Fix a bug with init_cookie_authentication() in the controller.
16706 - When recommending new-format log lines, if the upper bound is
16707 LOG_ERR, leave it implicit.
16709 o Bugfixes on 0.0.8.1:
16710 - Fix a whole slew of memory leaks.
16711 - Fix isspace() and friends so they still make Solaris happy
16712 but also so they don't trigger asserts on win32.
16713 - Fix parse_iso_time on platforms without strptime (eg win32).
16714 - win32: tolerate extra "readable" events better.
16715 - win32: when being multithreaded, leave parent fdarray open.
16716 - Make unit tests work on win32.
16719 Changes in version 0.0.9rc6 - 2004-12-06
16720 o Bugfixes on 0.0.9pre:
16721 - Clean up some more integer underflow opportunities (not exploitable
16723 - While hibernating, hup should not regrow our listeners.
16724 - Send an end to the streams we close when we hibernate, rather
16725 than just chopping them off.
16726 - React to eof immediately on non-open edge connections.
16728 o Bugfixes on 0.0.8.1:
16729 - Calculate timeout for waiting for a connected cell from the time
16730 we sent the begin cell, not from the time the stream started. If
16731 it took a long time to establish the circuit, we would time out
16732 right after sending the begin cell.
16733 - Fix router_compare_addr_to_addr_policy: it was not treating a port
16734 of * as always matching, so we were picking reject *:* nodes as
16735 exit nodes too. Oops.
16738 - New circuit building strategy: keep a list of ports that we've
16739 used in the past 6 hours, and always try to have 2 circuits open
16740 or on the way that will handle each such port. Seed us with port
16741 80 so web users won't complain that Tor is "slow to start up".
16742 - Make kill -USR1 dump more useful stats about circuits.
16743 - When warning about retrying or giving up, print the address, so
16744 the user knows which one it's talking about.
16745 - If you haven't used a clean circuit in an hour, throw it away,
16746 just to be on the safe side. (This means after 6 hours a totally
16747 unused Tor client will have no circuits open.)
16750 Changes in version 0.0.9rc5 - 2004-12-01
16751 o Bugfixes on 0.0.8.1:
16752 - Disallow NDEBUG. We don't ever want anybody to turn off debug.
16753 - Let resolve conns retry/expire also, rather than sticking around
16755 - If we are using select, make sure we stay within FD_SETSIZE.
16757 o Bugfixes on 0.0.9pre:
16758 - Fix integer underflow in tor_vsnprintf() that may be exploitable,
16759 but doesn't seem to be currently; thanks to Ilja van Sprundel for
16761 - If anybody set DirFetchPostPeriod, give them StatusFetchPeriod
16762 instead. Impose minima and maxima for all *Period options; impose
16763 even tighter maxima for fetching if we are a caching dirserver.
16764 Clip rather than rejecting.
16765 - Fetch cached running-routers from servers that serve it (that is,
16766 authdirservers and servers running 0.0.9rc5-cvs or later.)
16769 - Accept *:706 (silc) in default exit policy.
16770 - Implement new versioning format for post 0.1.
16771 - Support "foo.nickname.exit" addresses, to let Alice request the
16772 address "foo" as viewed by exit node "nickname". Based on a patch
16774 - Make tor --version --version dump the cvs Id of every file.
16777 Changes in version 0.0.9rc4 - 2004-11-28
16778 o Bugfixes on 0.0.8.1:
16779 - Make windows sockets actually non-blocking (oops), and handle
16780 win32 socket errors better.
16782 o Bugfixes on 0.0.9rc1:
16783 - Actually catch the -USR2 signal.
16786 Changes in version 0.0.9rc3 - 2004-11-25
16787 o Bugfixes on 0.0.8.1:
16788 - Flush the log file descriptor after we print "Tor opening log file",
16789 so we don't see those messages days later.
16791 o Bugfixes on 0.0.9rc1:
16792 - Make tor-resolve work again.
16793 - Avoid infinite loop in tor-resolve if tor hangs up on it.
16794 - Fix an assert trigger for clients/servers handling resolves.
16797 Changes in version 0.0.9rc2 - 2004-11-24
16798 o Bugfixes on 0.0.9rc1:
16799 - I broke socks5 support while fixing the eof bug.
16800 - Allow unitless bandwidths and intervals; they default to bytes
16802 - New servers don't start out hibernating; they are active until
16803 they run out of bytes, so they have a better estimate of how
16804 long it takes, and so their operators can know they're working.
16807 Changes in version 0.0.9rc1 - 2004-11-23
16808 o Bugfixes on 0.0.8.1:
16809 - Finally fix a bug that's been plaguing us for a year:
16810 With high load, circuit package window was reaching 0. Whenever
16811 we got a circuit-level sendme, we were reading a lot on each
16812 socket, but only writing out a bit. So we would eventually reach
16813 eof. This would be noticed and acted on even when there were still
16814 bytes sitting in the inbuf.
16815 - When poll() is interrupted, we shouldn't believe the revents values.
16817 o Bugfixes on 0.0.9pre6:
16818 - Fix hibernate bug that caused pre6 to be broken.
16819 - Don't keep rephist info for routers that haven't had activity for
16820 24 hours. (This matters now that clients have keys, since we track
16822 - Never call close_temp_logs while validating log options.
16823 - Fix backslash-escaping on tor.sh.in and torctl.in.
16826 - Implement weekly/monthly/daily accounting: now you specify your
16827 hibernation properties by
16828 AccountingMax N bytes|KB|MB|GB|TB
16829 AccountingStart day|week|month [day] HH:MM
16830 Defaults to "month 1 0:00".
16831 - Let bandwidth and interval config options be specified as 5 bytes,
16832 kb, kilobytes, etc; and as seconds, minutes, hours, days, weeks.
16833 - kill -USR2 now moves all logs to loglevel debug (kill -HUP to
16834 get back to normal.)
16835 - If your requested entry or exit node has advertised bandwidth 0,
16837 - Be more greedy about filling up relay cells -- we try reading again
16838 once we've processed the stuff we read, in case enough has arrived
16839 to fill the last cell completely.
16840 - Apply NT service patch from Osamu Fujino. Still needs more work.
16843 Changes in version 0.0.9pre6 - 2004-11-15
16844 o Bugfixes on 0.0.8.1:
16845 - Fix assert failure on malformed socks4a requests.
16846 - Use identity comparison, not nickname comparison, to choose which
16847 half of circuit-ID-space each side gets to use. This is needed
16848 because sometimes we think of a router as a nickname, and sometimes
16849 as a hex ID, and we can't predict what the other side will do.
16850 - Catch and ignore SIGXFSZ signals when log files exceed 2GB; our
16851 write() call will fail and we handle it there.
16852 - Add a FAST_SMARTLIST define to optionally inline smartlist_get
16853 and smartlist_len, which are two major profiling offenders.
16855 o Bugfixes on 0.0.9pre5:
16856 - Fix a bug in read_all that was corrupting config files on windows.
16857 - When we're raising the max number of open file descriptors to
16858 'unlimited', don't log that we just raised it to '-1'.
16859 - Include event code with events, as required by control-spec.txt.
16860 - Don't give a fingerprint when clients do --list-fingerprint:
16861 it's misleading, because it will never be the same again.
16862 - Stop using strlcpy in tor_strndup, since it was slowing us
16864 - Remove warn on startup about missing cached-directory file.
16865 - Make kill -USR1 work again.
16866 - Hibernate if we start tor during the "wait for wakeup-time" phase
16867 of an accounting interval. Log our hibernation plans better.
16868 - Authoritative dirservers now also cache their directory, so they
16869 have it on start-up.
16872 - Fetch running-routers; cache running-routers; compress
16873 running-routers; serve compressed running-routers.z
16874 - Add NSI installer script contributed by J Doe.
16875 - Commit VC6 and VC7 workspace/project files.
16876 - Commit a tor.spec for making RPM files, with help from jbash.
16877 - Add contrib/torctl.in contributed by Glenn Fink.
16878 - Implement the control-spec's SAVECONF command, to write your
16879 configuration to torrc.
16880 - Get cookie authentication for the controller closer to working.
16881 - Include control-spec.txt in the tarball.
16882 - When set_conf changes our server descriptor, upload a new copy.
16883 But don't upload it too often if there are frequent changes.
16884 - Document authentication config in man page, and document signals
16886 - Clean up confusing parts of man page and torrc.sample.
16887 - Make expand_filename handle ~ and ~username.
16888 - Use autoconf to enable largefile support where necessary. Use
16889 ftello where available, since ftell can fail at 2GB.
16890 - Distinguish between TOR_TLS_CLOSE and TOR_TLS_ERROR, so we can
16891 log more informatively.
16892 - Give a slightly more useful output for "tor -h".
16893 - Refuse application socks connections to port 0.
16894 - Check clock skew for verified servers, but allow unverified
16895 servers and clients to have any clock skew.
16896 - Break DirFetchPostPeriod into:
16897 - DirFetchPeriod for fetching full directory,
16898 - StatusFetchPeriod for fetching running-routers,
16899 - DirPostPeriod for posting server descriptor,
16900 - RendPostPeriod for posting hidden service descriptors.
16901 - Make sure the hidden service descriptors are at a random offset
16902 from each other, to hinder linkability.
16905 Changes in version 0.0.9pre5 - 2004-11-09
16906 o Bugfixes on 0.0.9pre4:
16907 - Fix a seg fault in unit tests (doesn't affect main program).
16908 - Fix an assert bug where a hidden service provider would fail if
16909 the first hop of his rendezvous circuit was down.
16910 - Hidden service operators now correctly handle version 1 style
16911 INTRODUCE1 cells (nobody generates them still, so not a critical
16913 - If do_hup fails, actually notice.
16914 - Handle more errnos from accept() without closing the listener.
16915 Some OpenBSD machines were closing their listeners because
16916 they ran out of file descriptors.
16917 - Send resolve cells to exit routers that are running a new
16918 enough version of the resolve code to work right.
16919 - Better handling of winsock includes on non-MSV win32 compilers.
16920 - Some people had wrapped their tor client/server in a script
16921 that would restart it whenever it died. This did not play well
16922 with our "shut down if your version is obsolete" code. Now people
16923 don't fetch a new directory if their local cached version is
16925 - Make our autogen.sh work on ksh as well as bash.
16928 - Hibernation: New config option "AccountingMaxKB" lets you
16929 set how many KBytes per month you want to allow your server to
16930 consume. Rather than spreading those bytes out evenly over the
16931 month, we instead hibernate for some of the month and pop up
16932 at a deterministic time, work until the bytes are consumed, then
16933 hibernate again. Config option "MonthlyAccountingStart" lets you
16934 specify which day of the month your billing cycle starts on.
16935 - Control interface: a separate program can now talk to your
16936 client/server over a socket, and get/set config options, receive
16937 notifications of circuits and streams starting/finishing/dying,
16938 bandwidth used, etc. The next step is to get some GUIs working.
16939 Let us know if you want to help out. See doc/control-spec.txt .
16940 - Ship a contrib/tor-control.py as an example script to interact
16941 with the control port.
16942 - "tor --hash-password zzyxz" will output a salted password for
16943 use in authenticating to the control interface.
16944 - New log format in config:
16945 "Log minsev[-maxsev] stdout|stderr|syslog" or
16946 "Log minsev[-maxsev] file /var/foo"
16949 - DirPolicy config option, to let people reject incoming addresses
16950 from their dirserver.
16951 - "tor --list-fingerprint" will list your identity key fingerprint
16953 - Add "pass" target for RedirectExit, to make it easier to break
16954 out of a sequence of RedirectExit rules.
16955 - Clients now generate a TLS cert too, in preparation for having
16956 them act more like real nodes.
16957 - Ship src/win32/ in the tarball, so people can use it to build.
16958 - Make old win32 fall back to CWD if SHGetSpecialFolderLocation
16960 - New "router-status" line in directory, to better bind each verified
16961 nickname to its identity key.
16962 - Deprecate unofficial config option abbreviations, and abbreviations
16963 not on the command line.
16964 - Add a pure-C tor-resolve implementation.
16965 - Use getrlimit and friends to ensure we can reach MaxConn (currently
16966 1024) file descriptors.
16968 o Code security improvements, inspired by Ilja:
16969 - Replace sprintf with snprintf. (I think they were all safe, but
16971 - Replace strcpy/strncpy with strlcpy in more places.
16972 - Avoid strcat; use snprintf or strlcat instead.
16973 - snprintf wrapper with consistent (though not C99) overflow behavior.
16976 Changes in version 0.0.9pre4 - 2004-10-17
16977 o Bugfixes on 0.0.9pre3:
16978 - If the server doesn't specify an exit policy, use the real default
16979 exit policy, not reject *:*.
16980 - Ignore fascistfirewall when uploading/downloading hidden service
16981 descriptors, since we go through Tor for those; and when using
16982 an HttpProxy, since we assume it can reach them all.
16983 - When looking for an authoritative dirserver, use only the ones
16984 configured at boot. Don't bother looking in the directory.
16985 - The rest of the fix for get_default_conf_file() on older win32.
16986 - Make 'Routerfile' config option obsolete.
16989 - New 'MyFamily nick1,...' config option for a server to
16990 specify other servers that shouldn't be used in the same circuit
16991 with it. Only believed if nick1 also specifies us.
16992 - New 'NodeFamily nick1,nick2,...' config option for a client to
16993 specify nodes that it doesn't want to use in the same circuit.
16994 - New 'Redirectexit pattern address:port' config option for a
16995 server to redirect exit connections, e.g. to a local squid.
16998 Changes in version 0.0.9pre3 - 2004-10-13
16999 o Bugfixes on 0.0.8.1:
17000 - Better torrc example lines for dirbindaddress and orbindaddress.
17001 - Improved bounds checking on parsed ints (e.g. config options and
17002 the ones we find in directories.)
17003 - Better handling of size_t vs int, so we're more robust on 64
17005 - Fix the rest of the bug where a newly started OR would appear
17006 as unverified even after we've added his fingerprint and hupped
17008 - Fix a bug from 0.0.7: when read() failed on a stream, we would
17009 close it without sending back an end. So 'connection refused'
17010 would simply be ignored and the user would get no response.
17012 o Bugfixes on 0.0.9pre2:
17013 - Serving the cached-on-disk directory to people is bad. We now
17014 provide no directory until we've fetched a fresh one.
17015 - Workaround for bug on windows where cached-directories get crlf
17017 - Make get_default_conf_file() work on older windows too.
17018 - If we write a *:* exit policy line in the descriptor, don't write
17019 any more exit policy lines.
17022 - Use only 0.0.9pre1 and later servers for resolve cells.
17023 - Make the dirservers file obsolete.
17024 - Include a dir-signing-key token in directories to tell the
17025 parsing entity which key is being used to sign.
17026 - Remove the built-in bulky default dirservers string.
17027 - New config option "Dirserver %s:%d [fingerprint]", which can be
17028 repeated as many times as needed. If no dirservers specified,
17029 default to moria1,moria2,tor26.
17030 - Make moria2 advertise a dirport of 80, so people behind firewalls
17031 will be able to get a directory.
17032 - Http proxy support
17033 - Dirservers translate requests for http://%s:%d/x to /x
17034 - You can specify "HttpProxy %s[:%d]" and all dir fetches will
17035 be routed through this host.
17036 - Clients ask for /tor/x rather than /x for new enough dirservers.
17037 This way we can one day coexist peacefully with apache.
17038 - Clients specify a "Host: %s%d" http header, to be compatible
17039 with more proxies, and so running squid on an exit node can work.
17042 Changes in version 0.0.8.1 - 2004-10-13
17044 - Fix a seg fault that can be triggered remotely for Tor
17045 clients/servers with an open dirport.
17046 - Fix a rare assert trigger, where routerinfos for entries in
17047 our cpath would expire while we're building the path.
17048 - Fix a bug in OutboundBindAddress so it (hopefully) works.
17049 - Fix a rare seg fault for people running hidden services on
17050 intermittent connections.
17051 - Fix a bug in parsing opt keywords with objects.
17052 - Fix a stale pointer assert bug when a stream detaches and
17054 - Fix a string format vulnerability (probably not exploitable)
17055 in reporting stats locally.
17056 - Fix an assert trigger: sometimes launching circuits can fail
17057 immediately, e.g. because too many circuits have failed recently.
17058 - Fix a compile warning on 64 bit platforms.
17061 Changes in version 0.0.9pre2 - 2004-10-03
17063 - Make fetching a cached directory work for 64-bit platforms too.
17064 - Make zlib.h a required header, not an optional header.
17067 Changes in version 0.0.9pre1 - 2004-10-01
17069 - Stop using separate defaults for no-config-file and
17070 empty-config-file. Now you have to explicitly turn off SocksPort,
17071 if you don't want it open.
17072 - Fix a bug in OutboundBindAddress so it (hopefully) works.
17073 - Improve man page to mention more of the 0.0.8 features.
17074 - Fix a rare seg fault for people running hidden services on
17075 intermittent connections.
17076 - Change our file IO stuff (especially wrt OpenSSL) so win32 is
17078 - Fix more dns related bugs: send back resolve_failed and end cells
17079 more reliably when the resolve fails, rather than closing the
17080 circuit and then trying to send the cell. Also attach dummy resolve
17081 connections to a circuit *before* calling dns_resolve(), to fix
17082 a bug where cached answers would never be sent in RESOLVED cells.
17083 - When we run out of disk space, or other log writing error, don't
17084 crash. Just stop logging to that log and continue.
17085 - We were starting to daemonize before we opened our logs, so if
17086 there were any problems opening logs, we would complain to stderr,
17087 which wouldn't work, and then mysteriously exit.
17088 - Fix a rare bug where sometimes a verified OR would connect to us
17089 before he'd uploaded his descriptor, which would cause us to
17090 assign conn->nickname as though he's unverified. Now we look through
17091 the fingerprint list to see if he's there.
17092 - Fix a rare assert trigger, where routerinfos for entries in
17093 our cpath would expire while we're building the path.
17096 - Clients can ask dirservers for /dir.z to get a compressed version
17097 of the directory. Only works for servers running 0.0.9, of course.
17098 - Make clients cache directories and use them to seed their router
17099 lists at startup. This means clients have a datadir again.
17100 - Configuration infrastructure support for warning on obsolete
17102 - Respond to content-encoding headers by trying to uncompress as
17104 - Reply with a deflated directory when a client asks for "dir.z".
17105 We could use allow-encodings instead, but allow-encodings isn't
17106 specified in HTTP 1.0.
17107 - Raise the max dns workers from 50 to 100.
17108 - Discourage people from setting their dirfetchpostperiod more often
17109 than once per minute.
17110 - Protect dirservers from overzealous descriptor uploading -- wait
17111 10 seconds after directory gets dirty, before regenerating.
17114 Changes in version 0.0.8 - 2004-08-25
17115 o Port it to SunOS 5.9 / Athena
17118 Changes in version 0.0.8rc2 - 2004-08-20
17119 o Make it compile on cygwin again.
17120 o When picking unverified routers, skip those with low uptime and/or
17121 low bandwidth, depending on what properties you care about.
17124 Changes in version 0.0.8rc1 - 2004-08-18
17125 o Changes from 0.0.7.3:
17127 - Fix assert triggers: if the other side returns an address 0.0.0.0,
17128 don't put it into the client dns cache.
17129 - If a begin failed due to exit policy, but we believe the IP address
17130 should have been allowed, switch that router to exitpolicy reject *:*
17131 until we get our next directory.
17133 - Clients choose nodes proportional to advertised bandwidth.
17134 - Avoid using nodes with low uptime as introduction points.
17135 - Handle servers with dynamic IP addresses: don't replace
17136 options->Address with the resolved one at startup, and
17137 detect our address right before we make a routerinfo each time.
17138 - 'FascistFirewall' option to pick dirservers and ORs on specific
17139 ports; plus 'FirewallPorts' config option to tell FascistFirewall
17140 which ports are open. (Defaults to 80,443)
17141 - Be more aggressive about trying to make circuits when the network
17142 has changed (e.g. when you unsuspend your laptop).
17143 - Check for time skew on http headers; report date in response to
17145 - If the entrynode config line has only one node, don't pick it as
17147 - Add strict{entry|exit}nodes config options. If set to 1, then
17148 we refuse to build circuits that don't include the specified entry
17150 - OutboundBindAddress config option, to bind to a specific
17151 IP address for outgoing connect()s.
17152 - End truncated log entries (e.g. directories) with "[truncated]".
17154 o Patches to 0.0.8preX:
17156 - Patches to compile and run on win32 again (maybe)?
17157 - Fix crash when looking for ~/.torrc with no $HOME set.
17158 - Fix a race bug in the unit tests.
17159 - Handle verified/unverified name collisions better when new
17160 routerinfo's arrive in a directory.
17161 - Sometimes routers were getting entered into the stats before
17162 we'd assigned their identity_digest. Oops.
17163 - Only pick and establish intro points after we've gotten a
17166 - AllowUnverifiedNodes config option to let circuits choose no-name
17167 routers in entry,middle,exit,introduction,rendezvous positions.
17168 Allow middle and rendezvous positions by default.
17169 - Add a man page for tor-resolve.
17172 Changes in version 0.0.7.3 - 2004-08-12
17173 o Stop dnsworkers from triggering an assert failure when you
17174 ask them to resolve the host "".
17177 Changes in version 0.0.8pre3 - 2004-08-09
17178 o Changes from 0.0.7.2:
17179 - Allow multiple ORs with same nickname in routerlist -- now when
17180 people give us one identity key for a nickname, then later
17181 another, we don't constantly complain until the first expires.
17182 - Remember used bandwidth (both in and out), and publish 15-minute
17183 snapshots for the past day into our descriptor.
17184 - You can now fetch $DIRURL/running-routers to get just the
17185 running-routers line, not the whole descriptor list. (But
17186 clients don't use this yet.)
17187 - When people mistakenly use Tor as an http proxy, point them
17188 at the tor-doc.html rather than the INSTALL.
17189 - Remove our mostly unused -- and broken -- hex_encode()
17190 function. Use base16_encode() instead. (Thanks to Timo Lindfors
17191 for pointing out this bug.)
17192 - Rotate onion keys every 12 hours, not every 2 hours, so we have
17193 fewer problems with people using the wrong key.
17194 - Change the default exit policy to reject the default edonkey,
17195 kazaa, gnutella ports.
17196 - Add replace_file() to util.[ch] to handle win32's rename().
17198 o Changes from 0.0.8preX:
17199 - Fix two bugs in saving onion keys to disk when rotating, so
17200 hopefully we'll get fewer people using old onion keys.
17201 - Fix an assert error that was making SocksPolicy not work.
17202 - Be willing to expire routers that have an open dirport -- it's
17203 just the authoritative dirservers we want to not forget.
17204 - Reject tor-resolve requests for .onion addresses early, so we
17205 don't build a whole rendezvous circuit and then fail.
17206 - When you're warning a server that he's unverified, don't cry
17207 wolf unpredictably.
17208 - Fix a race condition: don't try to extend onto a connection
17209 that's still handshaking.
17210 - For servers in clique mode, require the conn to be open before
17211 you'll choose it for your path.
17212 - Fix some cosmetic bugs about duplicate mark-for-close, lack of
17213 end relay cell, etc.
17214 - Measure bandwidth capacity over the last 24 hours, not just 12
17215 - Bugfix: authoritative dirservers were making and signing a new
17216 directory for each client, rather than reusing the cached one.
17219 Changes in version 0.0.8pre2 - 2004-08-04
17220 o Changes from 0.0.7.2:
17222 - Check directory signature _before_ you decide whether you're
17223 you're running an obsolete version and should exit.
17224 - Check directory signature _before_ you parse the running-routers
17225 list to decide who's running or verified.
17226 - Bugfixes and features:
17227 - Check return value of fclose while writing to disk, so we don't
17228 end up with broken files when servers run out of disk space.
17229 - Log a warning if the user uses an unsafe socks variant, so people
17230 are more likely to learn about privoxy or socat.
17231 - Dirservers now include RFC1123-style dates in the HTTP headers,
17232 which one day we will use to better detect clock skew.
17234 o Changes from 0.0.8pre1:
17235 - Make it compile without warnings again on win32.
17236 - Log a warning if you're running an unverified server, to let you
17237 know you might want to get it verified.
17238 - Only pick a default nickname if you plan to be a server.
17241 Changes in version 0.0.8pre1 - 2004-07-23
17243 - Made our unit tests compile again on OpenBSD 3.5, and tor
17244 itself compile again on OpenBSD on a sparc64.
17245 - We were neglecting milliseconds when logging on win32, so
17246 everything appeared to happen at the beginning of each second.
17248 o Protocol changes:
17249 - 'Extend' relay cell payloads now include the digest of the
17250 intended next hop's identity key. Now we can verify that we're
17251 extending to the right router, and also extend to routers we
17252 hadn't heard of before.
17255 - Tor nodes can now act as relays (with an advertised ORPort)
17256 without being manually verified by the dirserver operators.
17257 - Uploaded descriptors of unverified routers are now accepted
17258 by the dirservers, and included in the directory.
17259 - Verified routers are listed by nickname in the running-routers
17260 list; unverified routers are listed as "$<fingerprint>".
17261 - We now use hash-of-identity-key in most places rather than
17262 nickname or addr:port, for improved security/flexibility.
17263 - To avoid Sybil attacks, paths still use only verified servers.
17264 But now we have a chance to play around with hybrid approaches.
17265 - Nodes track bandwidth usage to estimate capacity (not used yet).
17266 - ClientOnly option for nodes that never want to become servers.
17267 - Directory caching.
17268 - "AuthoritativeDir 1" option for the official dirservers.
17269 - Now other nodes (clients and servers) will cache the latest
17270 directory they've pulled down.
17271 - They can enable their DirPort to serve it to others.
17272 - Clients will pull down a directory from any node with an open
17273 DirPort, and check the signature/timestamp correctly.
17274 - Authoritative dirservers now fetch directories from other
17275 authdirservers, to stay better synced.
17276 - Running-routers list tells who's down also, along with noting
17277 if they're verified (listed by nickname) or unverified (listed
17279 - Allow dirservers to serve running-router list separately.
17280 This isn't used yet.
17281 - ORs connect-on-demand to other ORs
17282 - If you get an extend cell to an OR you're not connected to,
17283 connect, handshake, and forward the create cell.
17284 - The authoritative dirservers stay connected to everybody,
17285 and everybody stays connected to 0.0.7 servers, but otherwise
17286 clients/servers expire unused connections after 5 minutes.
17287 - When servers get a sigint, they delay 30 seconds (refusing new
17288 connections) then exit. A second sigint causes immediate exit.
17289 - File and name management:
17290 - Look for .torrc if no CONFDIR "torrc" is found.
17291 - If no datadir is defined, then choose, make, and secure ~/.tor
17293 - If torrc not found, exitpolicy reject *:*.
17294 - Expands ~/ in filenames to $HOME/ (but doesn't yet expand ~arma).
17295 - If no nickname is defined, derive default from hostname.
17296 - Rename secret key files, e.g. identity.key -> secret_id_key,
17297 to discourage people from mailing their identity key to tor-ops.
17298 - Refuse to build a circuit before the directory has arrived --
17299 it won't work anyway, since you won't know the right onion keys
17301 - Try other dirservers immediately if the one you try is down. This
17302 should tolerate down dirservers better now.
17303 - Parse tor version numbers so we can do an is-newer-than check
17304 rather than an is-in-the-list check.
17305 - New socks command 'resolve', to let us shim gethostbyname()
17307 - A 'tor_resolve' script to access the socks resolve functionality.
17308 - A new socks-extensions.txt doc file to describe our
17309 interpretation and extensions to the socks protocols.
17310 - Add a ContactInfo option, which gets published in descriptor.
17311 - Publish OR uptime in descriptor (and thus in directory) too.
17312 - Write tor version at the top of each log file
17313 - New docs in the tarball:
17315 - Document that you should proxy your SSL traffic too.
17318 Changes in version 0.0.7.2 - 2004-07-07
17319 o A better fix for the 0.0.0.0 problem, that will hopefully
17320 eliminate the remaining related assertion failures.
17323 Changes in version 0.0.7.1 - 2004-07-04
17324 o When an address resolves to 0.0.0.0, treat it as a failed resolve,
17325 since internally we use 0.0.0.0 to signify "not yet resolved".
17328 Changes in version 0.0.7 - 2004-06-07
17329 o Updated the man page to reflect the new features.
17332 Changes in version 0.0.7rc2 - 2004-06-06
17333 o Changes from 0.0.7rc1:
17334 - Make it build on Win32 again.
17335 o Changes from 0.0.6.2:
17336 - Rotate dnsworkers and cpuworkers on SIGHUP, so they get new config
17340 Changes in version 0.0.7rc1 - 2004-06-02
17342 - On sighup, we were adding another log without removing the first
17343 one. So log messages would get duplicated n times for n sighups.
17344 - Several cases of using a connection after we'd freed it. The
17345 problem was that connections that are pending resolve are in both
17346 the pending_resolve tree, and also the circuit's resolving_streams
17347 list. When you want to remove one, you must remove it from both.
17348 - Fix a double-mark-for-close where an end cell arrived for a
17349 resolving stream, and then the resolve failed.
17350 - Check directory signatures based on name of signer, not on whom
17351 we got the directory from. This will let us cache directories more
17354 - Crank up some of our constants to handle more users.
17357 Changes in version 0.0.7pre1 - 2004-06-02
17358 o Fixes for crashes and other obnoxious bugs:
17359 - Fix an epipe bug: sometimes when directory connections failed
17360 to connect, we would give them a chance to flush before closing
17362 - When we detached from a circuit because of resolvefailed, we
17363 would immediately try the same circuit twice more, and then
17364 give up on the resolve thinking we'd tried three different
17366 - Limit the number of intro circuits we'll attempt to build for a
17367 hidden service per 15-minute period.
17368 - Check recommended-software string *early*, before actually parsing
17369 the directory. Thus we can detect an obsolete version and exit,
17370 even if the new directory format doesn't parse.
17371 o Fixes for security bugs:
17372 - Remember which nodes are dirservers when you startup, and if a
17373 random OR enables his dirport, don't automatically assume he's
17374 a trusted dirserver.
17376 - Directory connections were asking the wrong poll socket to
17377 start writing, and not asking themselves to start writing.
17378 - When we detached from a circuit because we sent a begin but
17379 didn't get a connected, we would use it again the first time;
17380 but after that we would correctly switch to a different one.
17381 - Stop warning when the first onion decrypt attempt fails; they
17382 will sometimes legitimately fail now that we rotate keys.
17383 - Override unaligned-access-ok check when $host_cpu is ia64 or
17384 arm. Apparently they allow it but the kernel whines.
17385 - Dirservers try to reconnect periodically too, in case connections
17387 - Fix some memory leaks in directory servers.
17388 - Allow backslash in Win32 filenames.
17389 - Made Tor build complain-free on FreeBSD, hopefully without
17390 breaking other BSD builds. We'll see.
17392 - Doxygen markup on all functions and global variables.
17393 - Make directory functions update routerlist, not replace it. So
17394 now directory disagreements are not so critical a problem.
17395 - Remove the upper limit on number of descriptors in a dirserver's
17396 directory (not that we were anywhere close).
17397 - Allow multiple logfiles at different severity ranges.
17398 - Allow *BindAddress to specify ":port" rather than setting *Port
17399 separately. Allow multiple instances of each BindAddress config
17400 option, so you can bind to multiple interfaces if you want.
17401 - Allow multiple exit policy lines, which are processed in order.
17402 Now we don't need that huge line with all the commas in it.
17403 - Enable accept/reject policies on SOCKS connections, so you can bind
17404 to 0.0.0.0 but still control who can use your OP.
17407 Changes in version 0.0.6.2 - 2004-05-16
17408 o Our integrity-checking digest was checking only the most recent cell,
17409 not the previous cells like we'd thought.
17410 Thanks to Stefan Mark for finding the flaw!
17413 Changes in version 0.0.6.1 - 2004-05-06
17414 o Fix two bugs in our AES counter-mode implementation (this affected
17415 onion-level stream encryption, but not TLS-level). It turns
17416 out we were doing something much more akin to a 16-character
17417 polyalphabetic cipher. Oops.
17418 Thanks to Stefan Mark for finding the flaw!
17419 o Retire moria3 as a directory server, and add tor26 as a directory
17423 Changes in version 0.0.6 - 2004-05-02
17424 [version bump only]
17427 Changes in version 0.0.6rc4 - 2004-05-01
17428 o Update the built-in dirservers list to use the new directory format
17429 o Fix a rare seg fault: if a node offering a hidden service attempts
17430 to build a circuit to Alice's rendezvous point and fails before it
17431 reaches the last hop, it retries with a different circuit, but
17433 o Handle windows socket errors correctly.
17436 Changes in version 0.0.6rc3 - 2004-04-28
17437 o Don't expire non-general excess circuits (if we had enough
17438 circuits open, we were expiring rendezvous circuits -- even
17439 when they had a stream attached. oops.)
17440 o Fetch randomness from /dev/urandom better (not via fopen/fread)
17441 o Better debugging for tls errors
17442 o Some versions of openssl have an SSL_pending function that erroneously
17443 returns bytes when there is a non-application record pending.
17444 o Set Content-Type on the directory and hidserv descriptor.
17445 o Remove IVs from cipher code, since AES-ctr has none.
17446 o Win32 fixes. Tor now compiles on win32 with no warnings/errors.
17447 o We were using an array of length zero in a few places.
17448 o win32's gethostbyname can't resolve an IP to an IP.
17449 o win32's close can't close a socket.
17452 Changes in version 0.0.6rc2 - 2004-04-26
17453 o Fix a bug where we were closing tls connections intermittently.
17454 It turns out openssl keeps its errors around -- so if an error
17455 happens, and you don't ask about it, and then another openssl
17456 operation happens and succeeds, and you ask if there was an error,
17457 it tells you about the first error. Fun fun.
17458 o Fix a bug that's been lurking since 27 may 03 (!)
17459 When passing back a destroy cell, we would use the wrong circ id.
17460 'Mostly harmless', but still worth fixing.
17461 o Since we don't support truncateds much, don't bother sending them;
17462 just close the circ.
17463 o check for <machine/limits.h> so we build on NetBSD again (I hope).
17464 o don't crash if a conn that sent a begin has suddenly lost its circuit
17465 (this was quite rare).
17468 Changes in version 0.0.6rc1 - 2004-04-25
17469 o We now rotate link (tls context) keys and onion keys.
17470 o CREATE cells now include oaep padding, so you can tell
17471 if you decrypted them correctly.
17472 o Add bandwidthburst to server descriptor.
17473 o Directories now say which dirserver signed them.
17474 o Use a tor_assert macro that logs failed assertions too.
17477 Changes in version 0.0.6pre5 - 2004-04-18
17478 o changes from 0.0.6pre4:
17479 - make tor build on broken freebsd 5.2 installs
17480 - fix a failed assert when you try an intro point, get a nack, and try
17481 a second one and it works.
17482 - when alice uses a port that the hidden service doesn't accept,
17483 it now sends back an end cell (denied by exit policy). otherwise
17484 alice would just have to wait to time out.
17485 - fix another rare bug: when we had tried all the intro
17486 points for a hidden service, we fetched the descriptor
17487 again, but we left our introcirc thinking it had already
17488 sent an intro, so it kept waiting for a response...
17489 - bugfix: when you sleep your hidden-service laptop, as soon
17490 as it wakes up it tries to upload a service descriptor, but
17491 socketpair fails for some reason (localhost not up yet?).
17492 now we simply give up on that upload, and we'll try again later.
17493 i'd still like to find the bug though.
17494 - if an intro circ waiting for an ack dies before getting one, then
17496 - we were reusing stale service descriptors and refetching usable
17500 Changes in version 0.0.6pre4 - 2004-04-14
17501 o changes from 0.0.6pre3:
17502 - when bob fails to connect to the rendezvous point, and his
17503 circ didn't fail because of the rendezvous point itself, then
17504 he retries a couple of times
17505 - we expire introduction and rendezvous circs more thoroughly
17506 (sometimes they were hanging around forever)
17507 - we expire unattached rendezvous streams that have been around
17508 too long (they were sticking around forever).
17509 - fix a measly fencepost error that was crashing everybody with
17513 Changes in version 0.0.6pre3 - 2004-04-14
17514 o changes from 0.0.6pre2:
17515 - make hup work again
17516 - fix some memory leaks for dirservers
17517 - allow more skew in rendezvous descriptor timestamps, to help
17518 handle people like blanu who don't know what time it is
17519 - normal circs are 3 hops, but some rend/intro circs are 4, if
17520 the initiator doesn't get to choose the last hop
17521 - send acks for introductions, so alice can know whether to try
17523 - bob publishes intro points more correctly
17524 o changes from 0.0.5:
17525 - fix an assert trigger that's been plaguing us since the days
17526 of 0.0.2prexx (thanks weasel!)
17527 - retry stream correctly when we fail to connect because of
17528 exit-policy-reject (should try another) or can't-resolve-address
17529 (also should try another, because dns on random internet servers
17531 - when we hup a dirserver and we've *removed* a server from the
17532 approved-routers list, now we remove that server from the
17533 in-memory directories too
17536 Changes in version 0.0.6pre2 - 2004-04-08
17537 o We fixed our base32 implementation. Now it works on all architectures.
17540 Changes in version 0.0.6pre1 - 2004-04-08
17542 - Hidden services and rendezvous points are implemented. Go to
17543 http://6sxoyfb3h2nvok2d.onion/ for an index of currently available
17544 hidden services. (This only works via a socks4a proxy such as
17545 Privoxy, and currently it's quite slow.)
17548 Changes in version 0.0.5 - 2004-03-30
17549 [version bump only]
17552 Changes in version 0.0.5rc3 - 2004-03-29
17553 o Install torrc as torrc.sample -- we no longer clobber your
17555 o Re-enable recommendedversion checking (we broke it in rc2, oops)
17556 o Add in a 'notice' log level for things the operator should hear
17557 but that aren't warnings
17560 Changes in version 0.0.5rc2 - 2004-03-29
17561 o Hold socks connection open until reply is flushed (if possible)
17562 o Make exit nodes resolve IPs to IPs immediately, rather than asking
17563 the dns farm to do it.
17564 o Fix c99 aliasing warnings in rephist.c
17565 o Don't include server descriptors that are older than 24 hours in the
17567 o Give socks 'reject' replies their whole 15s to attempt to flush,
17568 rather than seeing the 60s timeout and assuming the flush had failed.
17569 o Clean automake droppings from the cvs repository
17572 Changes in version 0.0.5rc1 - 2004-03-28
17573 o Fix mangled-state bug in directory fetching (was causing sigpipes).
17574 o Only build circuits after we've fetched the directory: clients were
17575 using only the directory servers before they'd fetched a directory.
17576 This also means longer startup time; so it goes.
17577 o Fix an assert trigger where an OP would fail to handshake, and we'd
17578 expect it to have a nickname.
17579 o Work around a tsocks bug: do a socks reject when AP connection dies
17580 early, else tsocks goes into an infinite loop.
17583 Changes in version 0.0.4 - 2004-03-26
17584 o When connecting to a dirserver or OR and the network is down,
17588 Changes in version 0.0.3 - 2004-03-26
17589 o Warn and fail if server chose a nickname with illegal characters
17590 o Port to Solaris and Sparc:
17591 - include missing header fcntl.h
17592 - have autoconf find -lsocket -lnsl automatically
17593 - deal with hardware word alignment
17594 - make uname() work (solaris has a different return convention)
17595 - switch from using signal() to sigaction()
17596 o Preliminary work on reputation system:
17597 - Keep statistics on success/fail of connect attempts; they're published
17598 by kill -USR1 currently.
17599 - Add a RunTesting option to try to learn link state by creating test
17600 circuits, even when SocksPort is off.
17601 - Remove unused open circuits when there are too many.
17604 Changes in version 0.0.2 - 2004-03-19
17605 - Include strlcpy and strlcat for safer string ops
17606 - define INADDR_NONE so we compile (but still not run) on solaris
17609 Changes in version 0.0.2pre27 - 2004-03-14
17611 - Allow internal tor networks (we were rejecting internal IPs,
17612 now we allow them if they're set explicitly).
17613 - And fix a few endian issues.
17616 Changes in version 0.0.2pre26 - 2004-03-14
17618 - If a stream times out after 15s without a connected cell, don't
17619 try that circuit again: try a new one.
17620 - Retry streams at most 4 times. Then give up.
17621 - When a dirserver gets a descriptor from an unknown router, it
17622 logs its fingerprint (so the dirserver operator can choose to
17623 accept it even without mail from the server operator).
17624 - Inform unapproved servers when we reject their descriptors.
17625 - Make tor build on Windows again. It works as a client, who knows
17627 - Clearer instructions in the torrc for how to set up a server.
17628 - Be more efficient about reading fd's when our global token bucket
17629 (used for rate limiting) becomes empty.
17631 - Stop asserting that computers always go forward in time. It's
17633 - When we sent a cell (e.g. destroy) and then marked an OR connection
17634 expired, we might close it before finishing a flush if the other
17635 side isn't reading right then.
17636 - Don't allow dirservers to start if they haven't defined
17637 RecommendedVersions
17638 - We were caching transient dns failures. Oops.
17639 - Prevent servers from publishing an internal IP as their address.
17640 - Address a strcat vulnerability in circuit.c
17643 Changes in version 0.0.2pre25 - 2004-03-04
17645 - Put the OR's IP in its router descriptor, not its fqdn. That way
17646 we'll stop being stalled by gethostbyname for nodes with flaky dns,
17649 - If the user typed in an address that didn't resolve, the server
17653 Changes in version 0.0.2pre24 - 2004-03-03
17655 - Fix an assertion failure in dns.c, where we were trying to dequeue
17656 a pending dns resolve even if it wasn't pending
17657 - Fix a spurious socks5 warning about still trying to write after the
17658 connection is finished.
17659 - Hold certain marked_for_close connections open until they're finished
17660 flushing, rather than losing bytes by closing them too early.
17661 - Correctly report the reason for ending a stream
17662 - Remove some duplicate calls to connection_mark_for_close
17663 - Put switch_id and start_daemon earlier in the boot sequence, so it
17664 will actually try to chdir() to options.DataDirectory
17665 - Make 'make test' exit(1) if a test fails; fix some unit tests
17666 - Make tor fail when you use a config option it doesn't know about,
17667 rather than warn and continue.
17668 - Make --version work
17669 - Bugfixes on the rpm spec file and tor.sh, so it's more up to date
17672 Changes in version 0.0.2pre23 - 2004-02-29
17674 - Print a statement when the first circ is finished, so the user
17675 knows it's working.
17676 - If a relay cell is unrecognized at the end of the circuit,
17677 send back a destroy. (So attacks to mutate cells are more
17679 - New config option 'excludenodes' to avoid certain nodes for circuits.
17680 - When it daemonizes, it chdir's to the DataDirectory rather than "/",
17681 so you can collect coredumps there.
17683 - Fix a bug in tls flushing where sometimes data got wedged and
17684 didn't flush until more data got sent. Hopefully this bug was
17685 a big factor in the random delays we were seeing.
17686 - Make 'connected' cells include the resolved IP, so the client
17687 dns cache actually gets populated.
17688 - Disallow changing from ORPort=0 to ORPort>0 on hup.
17689 - When we time-out on a stream and detach from the circuit, send an
17690 end cell down it first.
17691 - Only warn about an unknown router (in exitnodes, entrynodes,
17692 excludenodes) after we've fetched a directory.
17695 Changes in version 0.0.2pre22 - 2004-02-26
17697 - Servers publish less revealing uname information in descriptors.
17698 - More memory tracking and assertions, to crash more usefully when
17700 - If the default torrc isn't there, just use some default defaults.
17701 Plus provide an internal dirservers file if they don't have one.
17702 - When the user tries to use Tor as an http proxy, give them an http
17703 501 failure explaining that we're a socks proxy.
17704 - Dump a new router.desc on hup, to help confused people who change
17705 their exit policies and then wonder why router.desc doesn't reflect
17707 - Clean up the generic tor.sh init script that we ship with.
17709 - If the exit stream is pending on the resolve, and a destroy arrives,
17710 then the stream wasn't getting removed from the pending list. I
17711 think this was the one causing recent server crashes.
17712 - Use a more robust poll on OSX 10.3, since their poll is flaky.
17713 - When it couldn't resolve any dirservers, it was useless from then on.
17714 Now it reloads the RouterFile (or default dirservers) if it has no
17716 - Move the 'tor' binary back to /usr/local/bin/ -- it turns out
17717 many users don't even *have* a /usr/local/sbin/.
17720 Changes in version 0.0.2pre21 - 2004-02-18
17722 - There's a ChangeLog file that actually reflects the changelog.
17723 - There's a 'torify' wrapper script, with an accompanying
17724 tor-tsocks.conf, that simplifies the process of using tsocks for
17725 tor. It even has a man page.
17726 - The tor binary gets installed to sbin rather than bin now.
17727 - Retry streams where the connected cell hasn't arrived in 15 seconds
17728 - Clean up exit policy handling -- get the default out of the torrc,
17729 so we can update it without forcing each server operator to fix
17731 - Allow imaps and pop3s in default exit policy
17733 - Prevent picking middleman nodes as the last node in the circuit
17736 Changes in version 0.0.2pre20 - 2004-01-30
17738 - We now have a deb package, and it's in debian unstable. Go to
17739 it, apt-getters. :)
17740 - I've split the TotalBandwidth option into BandwidthRate (how many
17741 bytes per second you want to allow, long-term) and
17742 BandwidthBurst (how many bytes you will allow at once before the cap
17743 kicks in). This better token bucket approach lets you, say, set
17744 BandwidthRate to 10KB/s and BandwidthBurst to 10MB, allowing good
17745 performance while not exceeding your monthly bandwidth quota.
17746 - Push out a tls record's worth of data once you've got it, rather
17747 than waiting until you've read everything waiting to be read. This
17748 may improve performance by pipelining better. We'll see.
17749 - Add an AP_CONN_STATE_CONNECTING state, to allow streams to detach
17750 from failed circuits (if they haven't been connected yet) and attach
17752 - Expire old streams that haven't managed to connect. Some day we'll
17753 have them reattach to new circuits instead.
17756 - Fix several memory leaks that were causing servers to become bloated
17758 - Fix a few very rare assert triggers. A few more remain.
17759 - Setuid to User _before_ complaining about running as root.
17762 Changes in version 0.0.2pre19 - 2004-01-07
17764 - Fix deadlock condition in dns farm. We were telling a child to die by
17765 closing the parent's file descriptor to him. But newer children were
17766 inheriting the open file descriptor from the parent, and since they
17767 weren't closing it, the socket never closed, so the child never read
17768 eof, so he never knew to exit. Similarly, dns workers were holding
17769 open other sockets, leading to all sorts of chaos.
17770 - New cleaner daemon() code for forking and backgrounding.
17771 - If you log to a file, it now prints an entry at the top of the
17772 logfile so you know it's working.
17773 - The onionskin challenge length was 30 bytes longer than necessary.
17774 - Started to patch up the spec so it's not quite so out of date.
17777 Changes in version 0.0.2pre18 - 2004-01-02
17779 - Fix endian issues with the 'integrity' field in the relay header.
17780 - Fix a potential bug where connections in state
17781 AP_CONN_STATE_CIRCUIT_WAIT might unexpectedly ask to write.
17784 Changes in version 0.0.2pre17 - 2003-12-30
17786 - Made --debuglogfile (or any second log file, actually) work.
17787 - Resolved an edge case in get_unique_circ_id_by_conn where a smart
17788 adversary could force us into an infinite loop.
17791 - Each onionskin handshake now includes a hash of the computed key,
17792 to prove the server's identity and help perfect forward secrecy.
17793 - Changed cell size from 256 to 512 bytes (working toward compatibility
17795 - Changed cell length to 2 bytes, and moved it to the relay header.
17796 - Implemented end-to-end integrity checking for the payloads of
17798 - Separated streamid from 'recognized' (otherwise circuits will get
17799 messed up when we try to have streams exit from the middle). We
17800 use the integrity-checking to confirm that a cell is addressed to
17802 - Randomize the initial circid and streamid values, so an adversary who
17803 breaks into a node can't learn how many circuits or streams have
17807 Changes in version 0.0.2pre16 - 2003-12-14
17809 - Fixed a bug that made HUP trigger an assert
17810 - Fixed a bug where a circuit that immediately failed wasn't being
17811 counted as a failed circuit in counting retries.
17814 - Now we close the circuit when we get a truncated cell: otherwise we're
17815 open to an anonymity attack where a bad node in the path truncates
17816 the circuit and then we open streams at him.
17817 - Add port ranges to exit policies
17818 - Add a conservative default exit policy
17819 - Warn if you're running tor as root
17820 - on HUP, retry OR connections and close/rebind listeners
17821 - options.EntryNodes: try these nodes first when picking the first node
17822 - options.ExitNodes: if your best choices happen to include any of
17823 your preferred exit nodes, you choose among just those preferred
17825 - options.ExcludedNodes: nodes that are never picked in path building
17828 Changes in version 0.0.2pre15 - 2003-12-03
17829 o Robustness and bugfixes:
17830 - Sometimes clients would cache incorrect DNS resolves, which would
17831 really screw things up.
17832 - An OP that goes offline would slowly leak all its sockets and stop
17834 - A wide variety of bugfixes in exit node selection, exit policy
17835 handling, and processing pending streams when a new circuit is
17837 - Pick nodes for a path only from those the directory says are up
17838 - Choose randomly from all running dirservers, not always the first one
17839 - Increase allowed http header size for directory fetch.
17840 - Stop writing to stderr (if we're daemonized it will be closed).
17841 - Enable -g always, so cores will be more useful to me.
17842 - Switch "-lcrypto -lssl" to "-lssl -lcrypto" for broken distributions.
17845 - Wrote a man page. It lists commonly used options.
17848 - Change default loglevel to warn.
17849 - Make PidFile default to null rather than littering in your CWD.
17850 - OnionRouter config option is now obsolete. Instead it just checks
17852 - Moved to a single unified torrc file for both clients and servers.
17855 Changes in version 0.0.2pre14 - 2003-11-29
17856 o Robustness and bugfixes:
17857 - Force the admin to make the DataDirectory himself
17858 - to get ownership/permissions right
17859 - so clients no longer make a DataDirectory and then never use it
17860 - fix bug where a client who was offline for 45 minutes would never
17861 pull down a directory again
17862 - fix (or at least hide really well) the dns assert bug that was
17863 causing server crashes
17864 - warnings and improved robustness wrt clockskew for certs
17865 - use the native daemon(3) to daemonize, when available
17866 - exit if bind() fails
17867 - exit if neither socksport nor orport is defined
17868 - include our own tor_timegm (Win32 doesn't have its own)
17869 - bugfix for win32 with lots of connections
17870 - fix minor bias in PRNG
17871 - make dirserver more robust to corrupt cached directory
17874 - Wrote the design document (woo)
17876 o Circuit building and exit policies:
17877 - Circuits no longer try to use nodes that the directory has told them
17879 - Exit policies now support bitmasks (18.0.0.0/255.0.0.0) and
17880 bitcounts (18.0.0.0/8).
17881 - Make AP connections standby for a circuit if no suitable circuit
17882 exists, rather than failing
17883 - Circuits choose exit node based on addr/port, exit policies, and
17884 which AP connections are standing by
17885 - Bump min pathlen from 2 to 3
17886 - Relay end cells have a payload to describe why the stream ended.
17887 - If the stream failed because of exit policy, try again with a new
17889 - Clients have a dns cache to remember resolved addresses.
17890 - Notice more quickly when we have no working circuits
17893 - APPort is now called SocksPort
17894 - SocksBindAddress, ORBindAddress, DirBindAddress let you configure
17896 - RecommendedVersions is now a config variable rather than
17897 hardcoded (for dirservers)
17898 - Reloads config on HUP
17899 - Usage info on -h or --help
17900 - If you set User and Group config vars, it'll setu/gid to them.
17903 Changes in version 0.0.2pre13 - 2003-10-19
17904 o General stability:
17905 - SSL_write no longer fails when it returns WANTWRITE and the number
17906 of bytes in the buf has changed by the next SSL_write call.
17907 - Fix segfault fetching directory when network is down
17908 - Fix a variety of minor memory leaks
17909 - Dirservers reload the fingerprints file on HUP, so I don't have
17910 to take down the network when I approve a new router
17911 - Default server config file has explicit Address line to specify fqdn
17914 - Buffers grow and shrink as needed (Cut process size from 20M to 2M)
17915 - Make listener connections not ever alloc bufs
17917 o Autoconf improvements:
17918 - don't clobber an external CFLAGS in ./configure
17919 - Make install now works
17920 - create var/lib/tor on make install
17921 - autocreate a tor.sh initscript to help distribs
17922 - autocreate the torrc and sample-server-torrc with correct paths
17924 o Log files and Daemonizing now work:
17925 - If --DebugLogFile is specified, log to it at -l debug
17926 - If --LogFile is specified, use it instead of commandline
17927 - If --RunAsDaemon is set, tor forks and backgrounds on startup