1 Changes in version 0.2.6.3-alpha - 2015-02-??
4 o Major features (security):
5 - Implementation of an AF_UNIX socket option to implement a SOCKS
6 proxy reachable by Unix Domain Socket. This allows client
7 applications to communicate with Tor without having the ability to
8 create AF_INET or AF_INET6 family sockets. If an application has
9 permission to create a socket with AF_UNIX, it may directly
10 communicate with Tor as if it were an other SOCKS proxy. This
11 should allow high risk applications to be entirely prevented from
12 connecting directly with TCP/IP, they will be able to only connect
13 to the internet through AF_UNIX and only through Tor. To create a
14 socket of this type, use the syntax "unix:/path/to/socket". Closes
17 o Major features (changed defaults):
18 - Prevent relay operators from unintentionally running exits: When a
19 relay is configured as an exit node, we now warn the user unless
20 the 'ExitRelay' option is set to 1. We warn even more loudly if
21 the relay is configured with the default exit policy, since this
22 tends to indicate accidental misconfiguration. Setting 'ExitRelay'
23 to 0 stops Tor from running as an exit relay. Closes ticket 10067.
25 o Major features (hidden services):
26 - Support mapping hidden service virtual ports to AF_UNIX sockets on
27 suitable platforms. Resolves ticket #11485.
29 o Major features (performance):
30 - Refactor the CPU worker implementation for better performance by
31 avoiding the kernel and lengthening pipelines. The original
32 implementation used sockets to transfer data from the main thread
33 to the worker threads, and didn't allow any thread to be assigned
34 more than a single piece of work at once. The new implementation
35 avoids communications overhead by making requests in shared
36 memory, avoiding kernel IO where possible, and keeping more
37 request in flight at once. Resolves issue #9682.
39 o Major bugfixes (client):
40 - Allow MapAddress and AutomapHostsOnResolve to work together when
41 an address is mapped into another address type that must be
42 automapped at resolve time. Fixes bug 7555; bugfix
45 o Major bugfixes (exit node stability):
46 - Fix an assertion failure that could occur under high DNS load.
47 Fixes bug 14129; bugfix on Tor 0.0.7rc1. Found by "jowr";
48 diagnosed and fixed by "cypherpunks".
50 o Major bugfixes (mixed relay-client operation):
51 - When running as a relay and a client at the same time (not
52 recommended), if we decide not to use a new guard because we want
53 to retry older guards, only close the locally-originating circuits
54 passing through that guard. Previously we would close all the
55 circuits. Fixes bug 9819; bugfix on 0.2.1.1-alpha. Reported
58 o Minor features (authorities, testing):
59 - Create TestingDirAuthVoteHSDir like TestingDirAuthVoteExit/Guard.
60 Ensures that authorities vote the HSDir flag for the listed relays
61 regardless of uptime or ORPort connectivity. Respects the value of
62 VoteOnHidServDirectoriesV2. Partial implementation for ticket
63 14067. Patch by "teor".
65 o Minor features (build):
66 - New --disable-system-torrc compile-time option to prevent Tor from
67 looking for a system-wide torrc or torrc-defaults tile. Resolves
70 o Minor features (controller):
71 - Include SOCKS_USERNAME and SOCKS_PASSWORD values in controller
72 events to let controllers observe circuit isolation inputs. Closes
74 - ControlPort now supports the unix:/path/to/dir syntax as an
75 alternative to the ControlSocket option, for consistency with
76 SocksPort and hidden services. Closes ticket 14451.
77 - New "GETINFO bw-event-cache" to get information about recent
78 bandwidth events. Closes ticket 14128. Useful for controllers to
79 get recent bandwidth history after the fix for 13988.
81 o Minor features (directory client):
82 - When downloading server- or microdescriptors from a directory
83 server, we no longer launch multiple simultaneous requests to the
84 same server. This reduces load on the directory servers,
85 especially when directory guards are in use. Closes ticket 9969.
86 - When downloading server- or microdescriptors over a tunneled
87 connection, do not limit the length of our request to what the
88 Squid proxy is willing to handle. Part of ticket 9969.
90 o Minor features (directory system):
91 - Authorities can now vote on the correct digests and latest
92 versions for different software packages. This allows packages
93 that include Tor to use the Tor authority system as a way to get
94 notified of updates and their correct digests. Implements proposal
95 227. Closes ticket 10395.
97 o Minor features (directory, memory usage):
98 - When we have recently been under memory pressure (over 3/4 of
99 MaxMemInQueues is allocated), then allocate smaller zlib objects
100 for small requests. Closes ticket 11791.
102 o Minor features (DOS resistance):
103 - Count the total number of bytes used storing hidden service
104 descriptors against the value of MaxMemInQueues. If we're low on
105 memory, and more than 20% of our memory is used holding hidden
106 service descriptors, free them until no more than 10% of our
107 memory holds hidden service descriptors. Free the least recently
108 fetched descriptors first. Resolves ticket 13806.
110 o Minor features (geoip):
111 - Update geoip to the January 7 2015 Maxmind GeoLite2
113 - Update geoip6 to the January 7 2015 Maxmind GeoLite2
116 o Minor features (Guard nodes):
117 - Reduce the time delay before saving guard status to disk from 10
118 minute to 30 seconds (or from one hour to 10 minutes if
119 AvoidDiskWrites is set). Closes ticket 12485.
121 o Minor features (hidden service):
122 - Make hidden service Sybil attacks harder by changing the minimum
123 time required to become an HSDir from 25 hours up to 96 hours.
124 Addresses ticket #14149.
125 - New option "HiddenServiceAllowUnknownPorts" to allow hidden
126 services to disable the anti-scanning feature introduced in
127 0.2.6.2-alpha. With this option not set, a connection to an
128 unlisted port closes the circuit. With this option set, only a
129 RELAY_DONE cell is sent. Closes ticket #14084.
131 o Minor features (interface):
132 - Implement '-f -' CLI suboption to allow torrc to be read from
133 standard input, thus not requiring to store torrc in file system.
134 Implements feature 13865.
136 o Minor features (logging):
137 - Add a count of unique clients to the bridge heartbeat message.
138 Resolves ticket 6852.
139 - Suppress "router info incompatible with extra info" message when
140 reading extrainfo documents from cache. (This message got loud
141 around when we closed bug 9812 in 0.2.6.2-alpha.) Closes
143 - Elevate authorized-client message from DEBUG to INFO. Closes
146 o Minor features (stability):
147 - Prevent bugs from causing infinite loops in our hash-table
148 iteration code by adding assertions that cached hash values have
149 not been corrupted. Closes ticket 11737.
151 o Minor features (systemd):
152 - Various improvements and modernizations in systemd hardening
153 support. Closes ticket 13805. Patch from Craig Andrews.
155 o Minor features (testing networks):
156 - Drop the minimum RendPostPeriod on a testing network to 5 seconds,
157 and the default to 2 minutes. Closes ticket 13401. Patch
159 - Drop the MIN_REND_INITIAL_POST_DELAY on a testing network to 5
160 seconds, but keep the default at 30 seconds. This reduces HS
161 bootstrap time to around 25 seconds. Change src/test/test-
162 network.sh default time to match. Closes ticket 13401. Patch
165 o Minor bugfixes (automapping):
166 - Prevent changes to other options from removing the wildcard value
167 "." from "AutomapHostsSuffixes". Fixes bug 12509; bugfix
170 o Minor bugfixes (build):
171 - Avoid warnings when building with systemd 209 or later. Fixes bug
172 14072; bugfix on 0.2.6.2-alpha. Patch from "h.venev".
174 o Minor bugfixes (client DNS):
175 - Report the correct cached DNS expiration times. Previously, we
176 would report everything as "never expires." Fixes bug 14193;
177 bugfix on 0.2.3.17-beta.
178 - Avoid a small memory leak when we find a cached answer for a
179 reverse DNS lookup in a client-side DNS cache. (Remember, client-
180 side DNS caching is off by default, and is not recommended.) Fixes
181 bug 14259; bugfix on 0.2.0.1-alpha.
183 o Minor bugfixes (client, automapping):
184 - Check for a missing option value in parse_virtual_addr_network
185 before asserting on the NULL in tor_addr_parse_mask_ports. This
186 avoids crashing on torrc lines like Vi[rtualAddrNetworkIPv[4|6]]
187 when no value follows the option. Fixes bug 14142; bugfix on
188 0.2.4.7-alpha. Patch by "teor".
189 - Fix a memory leak when using AutomapHostsOnResolve. Fixes bug
190 14195; bugfix on 0.1.0.1-rc.
192 o Minor bugfixes (client, bridges):
193 - When we are using bridges and we had a network connectivity
194 problem, only retry connecting to our currently configured
195 bridges, not all bridges we know about and remember using. Fixes
196 bug 14216; bugfix on tor-0.2.2.17-alpha. Patch from arma.
198 o Minor bugfixes (client, IPV6):
199 - Reject socks requests to literal IPv6 addresses when IPv6Traffic
200 flag is not set; and not because the NoIPv4Traffic flag was set.
201 Previously we'd looked at the NoIPv4Traffic flag for both types of
202 literal addresses. Fixes bug 14280; bugfix on 0.2.4.7-alpha.
204 o Minor bugfixes (compilation):
205 - Build without warnings with the stock OpenSSL srtp.h header, which
206 has a duplicate declaration of SSL_get_selected_srtp_profile().
207 Fixes bug 14220; this is OpenSSL's bug, not ours.
208 - The address of an array in the middle of a structure will always
209 be non-NULL. clang recognises this and complains. Disable the
210 tautologous and redundant check to silence this warning. Fixes bug
211 14001; bugfix on 0.2.1.2-alpha.
212 - Compile correctly with (unreleased) OpenSSL 1.1.0 headers.
213 Addresses ticket 14188.
215 o Minor bugfixes (controller):
216 - Add a code for the END_CIRC_REASON_IP_NOW_REDUNDANT circuit close
217 reason. Fixes bug 14207; bugfix on 0.2.6.2-alpha.
218 - Avoid crashing on a malformed EXTENDCIRCUIT command. Fixes bug
219 14116; bugfix on 0.2.2.9-alpha.
221 o Minor bugfixes (directory authority):
222 - Allow directory authorities to fetch more data from one another if
223 they find themselves missing lots of votes. Previously, they had
224 been bumping against the 10 MB queued data limit. Fixes bug 14261;
225 bugfix on 0.1.2.5-alpha.
226 - Enlarge the buffer to read bw-auth generated files to avoid an
227 issue when parsing the file in dirserv_read_measured_bandwidths().
228 Fixes bug 14125; bugfix on 0.2.2.1-alpha.
230 o Minor bugfixes (file handling):
231 - Stop failing when key files are zero-length. Instead, generate new
232 keys, and overwrite the empty key files. Fixes bug 13111; bugfix
233 on all versions of Tor. Patch by "teor".
234 - Stop generating a fresh .old RSA key file when the .old file is
235 missing. Fixes part of 13111; bugfix on 0.0.6rc1.
236 - Avoid overwriting .old key files with empty key files.
237 - Skip loading zero-length extra info store, router store, stats,
238 state, and key files.
239 - Avoid crashing when trying to reload a torrc specified as a
240 relative path with RunAsDaemon turned on. Fixes bug 13397; bugfix
243 o Minor bugfixes (hidden services):
244 - Close the intro circuit once we don't have any more usable intro
245 points instead of making it timeout at some point. This also make
246 sure no extra HS descriptor fetch is triggered. Fixes bug 14224;
248 - When fetching a hidden service descriptor for a down service that
249 we recently up, do not keep refetching until we try the same
250 replica twice in a row. Fixes bug 14219; bugfix on 0.2.0.10-alpha.
251 - Successfully launch Tor with a nonexistent hidden service
252 directory. Our fix for bug 13942 didn't catch this case. Fixes bug
253 14106; bugfix on 0.2.6.2-alpha.
255 o Minor bugfixes (logging):
256 - Avoid crashing when there are more log domains than entries in
257 domain_list. Bugfix on 0.2.3.1-alpha.
258 - Add a string representation for LD_SCHED. Fixes bug 14740; bugfix
261 o Minor bugfixes (parsing):
262 - Stop accepting milliseconds (or other junk) at the end of
263 descriptor publication times. Fixes bug 9286; bugfix on 0.0.2pre25.
264 - Support two-number and three-number version numbers correctly, in
265 case we change the Tor versioning system in the future. Fixes bug
266 13661; bugfix on 0.0.8pre1.
268 o Minor bugfixes (portability):
269 - Fix the ioctl()-based network interface lookup code so that it
270 will work on systems that have variable-length struct ifreq, for
273 o Minor bugfixes (shutdown):
274 - When shutting down, always call event_del() on lingering read or
275 write events before freeing them. Otherwise, we risk double-frees
276 or read-after-frees in event_base_free(). Fixes bug 12985; bugfix
279 o Minor bugfixes (small memory leaks):
280 - Avoid leaking memory when using IPv6 virtual address mappings.
281 Fixes bug 14123; bugfix on 0.2.4.7-alpha. Patch by Tom van
284 o Minor bugfixes (statistics):
285 - Increase period over which bandwidth observations are aggregated
286 from 15 minutes to 4 hours. Fixes bug 13988; bugfix on 0.0.8pre1.
288 o Minor bugfixes (systemd support):
289 - Fix detection and operation of systemd watchdog. Fixes part of bug
290 14141; bugfix on 0.2.6.2-alpha. Patch from Tomasz Torcz.
291 - Run correctly under systemd with the RunAsDaemon option set. Fixes
292 part of bug 14141; bugfix on 0.2.5.7-rc. Patch from Tomasz Torcz.
293 - Inform the systemd supervisor about more changes in the Tor
294 process status. Implements part of ticket 14141. Patch from
296 - Cause the "--disable-systemd" option to actually disable systemd
297 support. Fixes bug 14350; bugfix on 0.2.6.2-alpha. Patch
300 o Minor bugfixes (TLS):
301 - Check more thoroughly throughout the TLS code for possible
302 unlogged TLS errors. Possible diagnostic or fix for bug 13319.
304 o Code simplification and refactoring:
305 - Move fields related to isolating and configuring client ports into
306 a shared structure. Previously, they were duplicated across
307 port_cfg_t, listener_connection_t, and edge_connection_t. Failure
308 to copy one of them correctly had been the cause of at least one
309 bug in the past. Closes ticket 8546.
310 - Refactor the get_interface_addresses_raw() Doom-function into
311 multiple smaller and easier to understand subfunctions. Cover the
312 resulting subfunctions with unit-tests. Fixes a significant
313 portion of issue 12376.
314 - Remove workaround in dirserv_thinks_router_is_hs_dir() that was
315 only for version <= 0.2.2.24 which is now deprecated. Closes
317 - Remove a test for a long-defunct broken version-one
321 - Adding section on OpenBSD to our TUNING document. Thanks to mmcc
322 for writing the OpenBSD-specific tips. Resolves ticket 13702.
323 - Make the tor-resolve documentation match its help string and its
324 options. Resolves part of ticket 14325.
325 - Log a more useful error message from tor-resolve when failing to
326 look up a hidden service address. Resolves part of ticket 14325.
328 o Downgraded warnings:
329 - Don't warn when we've attempted to contact a relay using the wrong
330 ntor onion key. Closes ticket 9635.
333 - To avoid confusion with the 'ExitRelay' option, 'ExitNode' is no
334 longer silently accepted as an alias for 'ExitNodes'.
337 - Make the checkdir/perms test complete successfully even if the
338 global umask is not 022. Fixes bug 14215; bugfix on 0.2.6.2-alpha.
339 - Test that tor does not fail when key files are zero-length. Check
340 that tor generates new keys, and overwrites the empty key files.
341 - Test that tor generates new keys when keys are missing
342 (existing behaviour).
343 - Test that tor does not overwrite key files that already contain
344 data (existing behaviour). Tests bug 13111. Patch by "teor".
345 - New "make test-stem" target to run stem integration tests.
346 Requires that the "STEM_SOURCE_DIR" environment variable be set.
348 - Make the test_cmdline_args.py script work correctly on Windows.
349 Patch from Gisle Vanem.
350 - Move the slower unit tests into a new "./src/test/test-slow"
351 binary that can be run independently of the other tests. Closes
353 - Avoid undefined behavior when sampling huge values from the
354 Laplace distribution. This made unittests fail on Raspberry Pi.
355 Bug found by Device. Fixes bug 14090; bugfix on 0.2.6.2-alpha.
358 Changes in version 0.2.6.2-alpha - 2014-12-31
359 Tor 0.2.6.2-alpha is the second alpha release in the 0.2.6.x series.
360 It introduces a major new backend for deciding when to send cells on
361 channels, which should lead down the road to big performance
362 increases. It contains security and statistics features for better
363 work on hidden services, and numerous bugfixes.
365 This release contains many new unit tests, along with major
366 performance improvements for running testing networks using Chutney.
367 Thanks to a series of patches contributed by "teor", testing networks
368 should now bootstrap in seconds, rather than minutes.
370 o Major features (relay, infrastructure):
371 - Complete revision of the code that relays use to decide which cell
372 to send next. Formerly, we selected the best circuit to write on
373 each channel, but we didn't select among channels in any
374 sophisticated way. Now, we choose the best circuits globally from
375 among those whose channels are ready to deliver traffic.
377 This patch implements a new inter-cmux comparison API, a global
378 high/low watermark mechanism and a global scheduler loop for
379 transmission prioritization across all channels as well as among
380 circuits on one channel. This schedule is currently tuned to
381 (tolerantly) avoid making changes in network performance, but it
382 should form the basis for major circuit performance increases in
383 the future. Code by Andrea; tuning by Rob Jansen; implements
386 o Major features (hidden services):
387 - Make HS port scanning more difficult by immediately closing the
388 circuit when a user attempts to connect to a nonexistent port.
390 - Add a HiddenServiceStatistics option that allows Tor relays to
391 gather and publish statistics about the overall size and volume of
392 hidden service usage. Specifically, when this option is turned on,
393 an HSDir will publish an approximate number of hidden services
394 that have published descriptors to it the past 24 hours. Also, if
395 a relay has acted as a hidden service rendezvous point, it will
396 publish the approximate amount of rendezvous cells it has relayed
397 the past 24 hours. The statistics themselves are obfuscated so
398 that the exact values cannot be derived. For more details see
399 proposal 238, "Better hidden service stats from Tor relays". This
400 feature is currently disabled by default. Implements feature 13192.
402 o Major bugfixes (client, automap):
403 - Repair automapping with IPv6 addresses. This automapping should
404 have worked previously, but one piece of debugging code that we
405 inserted to detect a regression actually caused the regression to
406 manifest itself again. Fixes bug 13811 and bug 12831; bugfix on
407 0.2.4.7-alpha. Diagnosed and fixed by Francisco Blas
410 o Major bugfixes (hidden services):
411 - When closing an introduction circuit that was opened in parallel
412 with others, don't mark the introduction point as unreachable.
413 Previously, the first successful connection to an introduction
414 point would make the other introduction points get marked as
415 having timed out. Fixes bug 13698; bugfix on 0.0.6rc2.
417 o Directory authority changes:
418 - Remove turtles as a directory authority.
419 - Add longclaw as a new (v3) directory authority. This implements
420 ticket 13296. This keeps the directory authority count at 9.
422 o Major removed features:
423 - Tor clients no longer support connecting to hidden services
424 running on Tor 0.2.2.x and earlier; the Support022HiddenServices
425 option has been removed. (There shouldn't be any hidden services
426 running these versions on the network.) Closes ticket 7803.
428 o Minor features (client):
429 - Validate hostnames in SOCKS5 requests more strictly. If SafeSocks
430 is enabled, reject requests with IP addresses as hostnames.
431 Resolves ticket 13315.
433 o Minor features (controller):
434 - Add a "SIGNAL HEARTBEAT" controller command that tells Tor to
435 write an unscheduled heartbeat message to the log. Implements
438 o Minor features (geoip):
439 - Update geoip and geoip6 to the November 15 2014 Maxmind GeoLite2
442 o Minor features (hidden services):
443 - When re-enabling the network, don't try to build introduction
444 circuits until we have successfully built a circuit. This makes
445 hidden services come up faster when the network is re-enabled.
446 Patch from "akwizgran". Closes ticket 13447.
447 - When we fail to a retrieve hidden service descriptor, send the
448 controller an "HS_DESC FAILED" controller event. Implements
450 - New HiddenServiceDirGroupReadable option to cause hidden service
451 directories and hostname files to be created group-readable. Patch
452 from "anon", David Stainton, and "meejah". Closes ticket 11291.
454 o Minor features (systemd):
455 - Where supported, when running with systemd, report successful
456 startup to systemd. Part of ticket 11016. Patch by Michael Scherer.
457 - When running with systemd, support systemd watchdog messages. Part
458 of ticket 11016. Patch by Michael Scherer.
460 o Minor features (transparent proxy):
461 - Update the transparent proxy option checks to allow for both ipfw
462 and pf on OS X. Closes ticket 14002.
463 - Use the correct option when using IPv6 with transparent proxy
464 support on Linux. Resolves 13808. Patch by Francisco Blas
467 o Minor bugfixes (preventative security, C safety):
468 - When reading a hexadecimal, base-32, or base-64 encoded value from
469 a string, always overwrite the whole output buffer. This prevents
470 some bugs where we would look at (but fortunately, not reveal)
471 uninitialized memory on the stack. Fixes bug 14013; bugfix on all
473 - Clear all memory targetted by tor_addr_{to,from}_sockaddr(), not
474 just the part that's used. This makes it harder for data leak bugs
475 to occur in the event of other programming failures. Resolves
478 o Minor bugfixes (client, microdescriptors):
479 - Use a full 256 bits of the SHA256 digest of a microdescriptor when
480 computing which microdescriptors to download. This keeps us from
481 erroneous download behavior if two microdescriptor digests ever
482 have the same first 160 bits. Fixes part of bug 13399; bugfix
484 - Reset a router's status if its microdescriptor digest changes,
485 even if the first 160 bits remain the same. Fixes part of bug
486 13399; bugfix on 0.2.3.1-alpha.
488 o Minor bugfixes (compilation):
489 - Silence clang warnings under --enable-expensive-hardening,
490 including implicit truncation of 64 bit values to 32 bit, const
491 char assignment to self, tautological compare, and additional
492 parentheses around equality tests. Fixes bug 13577; bugfix
494 - Fix a clang warning about checking whether an address in the
495 middle of a structure is NULL. Fixes bug 14001; bugfix
498 o Minor bugfixes (hidden services):
499 - Correctly send a controller event when we find that a rendezvous
500 circuit has finished. Fixes bug 13936; bugfix on 0.1.1.5-alpha.
501 - Pre-check directory permissions for new hidden-services to avoid
502 at least one case of "Bug: Acting on config options left us in a
503 broken state. Dying." Fixes bug 13942; bugfix on 0.0.6pre1.
504 - When adding a new hidden service (for example, via SETCONF), Tor
505 no longer congratulates the user for running a relay. Fixes bug
506 13941; bugfix on 0.2.6.1-alpha.
507 - When fetching hidden service descriptors, we now check not only
508 for whether we got the hidden service we had in mind, but also
509 whether we got the particular descriptors we wanted. This prevents
510 a class of inefficient but annoying DoS attacks by hidden service
511 directories. Fixes bug 13214; bugfix on 0.2.1.6-alpha. Reported
514 o Minor bugfixes (Linux seccomp2 sandbox):
515 - Make transparent proxy support work along with the seccomp2
516 sandbox. Fixes part of bug 13808; bugfix on 0.2.5.1-alpha. Patch
517 by Francisco Blas Izquierdo Riera.
518 - Fix a memory leak in tor-resolve when running with the sandbox
519 enabled. Fixes bug 14050; bugfix on 0.2.5.9-rc.
521 o Minor bugfixes (logging):
522 - Downgrade warnings about RSA signature failures to info log level.
523 Emit a warning when an extra info document is found incompatible
524 with a corresponding router descriptor. Fixes bug 9812; bugfix
526 - Make connection_ap_handshake_attach_circuit() log the circuit ID
527 correctly. Fixes bug 13701; bugfix on 0.0.6.
529 o Minor bugfixes (misc):
530 - Stop allowing invalid address patterns like "*/24" that contain
531 both a wildcard address and a bit prefix length. This affects all
532 our address-range parsing code. Fixes bug 7484; bugfix
535 o Minor bugfixes (testing networks, fast startup):
536 - Allow Tor to build circuits using a consensus with no exits. If
537 the consensus has no exits (typical of a bootstrapping test
538 network), allow Tor to build circuits once enough descriptors have
539 been downloaded. This assists in bootstrapping a testing Tor
540 network. Fixes bug 13718; bugfix on 0.2.4.10-alpha. Patch
542 - When V3AuthVotingInterval is low, give a lower If-Modified-Since
543 header to directory servers. This allows us to obtain consensuses
544 promptly when the consensus interval is very short. This assists
545 in bootstrapping a testing Tor network. Fixes parts of bugs 13718
546 and 13963; bugfix on 0.2.0.3-alpha. Patch by "teor".
547 - Stop assuming that private addresses are local when checking
548 reachability in a TestingTorNetwork. Instead, when testing, assume
549 all OR connections are remote. (This is necessary due to many test
550 scenarios running all relays on localhost.) This assists in
551 bootstrapping a testing Tor network. Fixes bug 13924; bugfix on
552 0.1.0.1-rc. Patch by "teor".
553 - Avoid building exit circuits from a consensus with no exits. Now
554 thanks to our fix for 13718, we accept a no-exit network as not
555 wholly lost, but we need to remember not to try to build exit
556 circuits on it. Closes ticket 13814; patch by "teor".
557 - Stop requiring exits to have non-zero bandwithcapacity in a
558 TestingTorNetwork. Instead, when TestingMinExitFlagThreshold is 0,
559 ignore exit bandwidthcapacity. This assists in bootstrapping a
560 testing Tor network. Fixes parts of bugs 13718 and 13839; bugfix
561 on 0.2.0.3-alpha. Patch by "teor".
562 - Add "internal" to some bootstrap statuses when no exits are
563 available. If the consensus does not contain Exits, Tor will only
564 build internal circuits. In this case, relevant statuses will
565 contain the word "internal" as indicated in the Tor control-
566 spec.txt. When bootstrap completes, Tor will be ready to build
567 internal circuits. If a future consensus contains Exits, exit
568 circuits may become available. Fixes part of bug 13718; bugfix on
569 0.2.4.10-alpha. Patch by "teor".
570 - Decrease minimum consensus interval to 10 seconds when
571 TestingTorNetwork is set, or 5 seconds for the first consensus.
572 Fix assumptions throughout the code that assume larger intervals.
573 Fixes bugs 13718 and 13823; bugfix on 0.2.0.3-alpha. Patch
575 - Avoid excluding guards from path building in minimal test
576 networks, when we're in a test network and excluding guards would
577 exclude all relays. This typically occurs in incredibly small tor
578 networks, and those using "TestingAuthVoteGuard *". Fixes part of
579 bug 13718; bugfix on 0.1.1.11-alpha. Patch by "teor".
581 o Code simplification and refactoring:
582 - Stop using can_complete_circuits as a global variable; access it
583 with a function instead.
584 - Avoid using operators directly as macro arguments: this lets us
585 apply coccinelle transformations to our codebase more directly.
587 - Combine the functions used to parse ClientTransportPlugin and
588 ServerTransportPlugin into a single function. Closes ticket 6456.
589 - Add inline functions and convenience macros for inspecting channel
590 state. Refactor the code to use convenience macros instead of
591 checking channel state directly. Fixes issue 7356.
592 - Document all members of was_router_added_t and rename
593 ROUTER_WAS_NOT_NEW to ROUTER_IS_ALREADY_KNOWN to make it less
594 confusable with ROUTER_WAS_TOO_OLD. Fixes issue 13644.
595 - In connection_exit_begin_conn(), use END_CIRC_REASON_TORPROTOCOL
596 constant instead of hardcoded value. Fixes issue 13840.
597 - Refactor our generic strmap and digestmap types into a single
598 implementation, so that we can add a new digest256map
602 - Document the bridge-authority-only 'networkstatus-bridges' file.
603 Closes ticket 13713; patch from "tom".
604 - Fix typo in PredictedPortsRelevanceTime option description in
605 manpage. Resolves issue 13707.
606 - Stop suggesting that users specify relays by nickname: it isn't a
607 good idea. Also, properly cross-reference how to specify relays in
608 all parts of manual documenting options that take a list of
609 relays. Closes ticket 13381.
610 - Clarify the HiddenServiceDir option description in manpage to make
611 it clear that relative paths are taken with respect to the current
612 working directory. Also clarify that this behavior is not
613 guaranteed to remain indefinitely. Fixes issue 13913.
616 - New tests for many parts of channel, relay, and circuitmux
617 functionality. Code by Andrea; part of 9262.
618 - New tests for parse_transport_line(). Part of ticket 6456.
619 - In the unit tests, use chgrp() to change the group of the unit
620 test temporary directory to the current user, so that the sticky
621 bit doesn't interfere with tests that check directory groups.
623 - Add unit tests for resolve_my_addr(). Part of ticket 12376; patch
627 Changes in version 0.2.6.1-alpha - 2014-10-30
628 Tor 0.2.6.1-alpha is the first release in the Tor 0.2.6.x series. It
629 includes numerous code cleanups and new tests, and fixes a large
630 number of annoying bugs. Out-of-memory conditions are handled better
631 than in 0.2.5, pluggable transports have improved proxy support, and
632 clients now use optimistic data for contacting hidden services. Also,
633 we are now more robust to changes in what we consider a parseable
634 directory object, so that tightening restrictions does not have a risk
635 of introducing infinite download loops.
637 This is the first alpha release in a new series, so expect there to be
638 bugs. Users who would rather test out a more stable branch should stay
639 with 0.2.5.x for now.
641 o New compiler and system requirements:
642 - Tor 0.2.6.x requires that your compiler support more of the C99
643 language standard than before. The 'configure' script now detects
644 whether your compiler supports C99 mid-block declarations and
645 designated initializers. If it does not, Tor will not compile.
647 We may revisit this requirement if it turns out that a significant
648 number of people need to build Tor with compilers that don't
649 bother implementing a 15-year-old standard. Closes ticket 13233.
650 - Tor no longer supports systems without threading support. When we
651 began working on Tor, there were several systems that didn't have
652 threads, or where the thread support wasn't able to run the
653 threads of a single process on multiple CPUs. That no longer
654 holds: every system where Tor needs to run well now has threading
655 support. Resolves ticket 12439.
657 o Removed platform support:
658 - We no longer include special code to build on Windows CE; as far
659 as we know, nobody has used Tor on Windows CE in a very long time.
662 o Major features (bridges):
663 - Expose the outgoing upstream HTTP/SOCKS proxy to pluggable
664 transports if they are configured via the "TOR_PT_PROXY"
665 environment variable. Implements proposal 232. Resolves
668 o Major features (client performance, hidden services):
669 - Allow clients to use optimistic data when connecting to a hidden
670 service, which should remove a round-trip from hidden service
671 initialization. See proposal 181 for details. Implements
674 o Major features (directory system):
675 - Upon receiving an unparseable directory object, if its digest
676 matches what we expected, then don't try to download it again.
677 Previously, when we got a descriptor we didn't like, we would keep
678 trying to download it over and over. Closes ticket 11243.
680 o Major features (sample torrc):
681 - Add a new, infrequently-changed "torrc.minimal". This file is
682 similar to torrc.sample, but it will change as infrequently as
683 possible, for the benefit of users whose systems prompt them for
684 intervention whenever a default configuration file is changed.
685 Making this change allows us to update torrc.sample to be a more
686 generally useful "sample torrc".
688 o Major bugfixes (directory authorities):
689 - Do not assign the HSDir flag to relays if they are not Valid, or
690 currently hibernating. Fixes #12573. Bugfix on tor-0.2.0.10-alpha
692 o Major bugfixes (directory bandwidth performance):
693 - Don't flush the zlib buffer aggressively when compressing
694 directory information for clients. This should save about 7% of
695 the bandwidth currently used for compressed descriptors and
696 microdescriptors. Fixes bug 11787; bugfix on 0.1.1.23.
698 o Minor features (security, memory wiping):
699 - Ensure we securely wipe keys from memory after
700 crypto_digest_get_digest and init_curve25519_keypair_from_file
701 have finished using them. Resolves ticket 13477.
703 o Minor features (security, out-of-memory handling):
704 - When handling an out-of-memory condition, allocate less memory for
705 temporary data structures. Fixes issue 10115.
706 - When handling an out-of-memory condition, consider more types of
707 buffers, including those on directory connections, and zlib
708 buffers. Resolves ticket 11792.
711 - When identity keypair is generated for first time, log a
712 congratulatory message that links to the new relay lifecycle
713 document. Implements feature 10427.
715 o Minor features (client):
716 - Clients are now willing to send optimistic data (before they
717 receive a 'connected' cell) to relays of any version. (Relays
718 without support for optimistic data are no longer supported on the
719 Tor network.) Resolves ticket 13153.
721 o Minor features (directory authorities):
722 - Don't list relays with a bandwidth estimate of 0 in the consensus.
723 Implements a feature proposed during discussion of bug 13000.
724 - In tor-gencert, report an error if the user provides the same
725 argument more than once.
726 - If a directory authority can't find a best consensus method in the
727 votes that it holds, it now falls back to its favorite consensus
728 method. Previously, it fell back to method 1. Neither of these is
729 likely to get enough signatures, but "fall back to favorite"
730 doesn't require us to maintain support an obsolete consensus
731 method. Implements part of proposal 215.
733 o Minor features (logging):
734 - On Unix-like systems, you can now use named pipes as the target of
735 the Log option, and other options that try to append to files.
736 Closes ticket 12061. Patch from "carlo von lynX".
737 - When opening a log file at startup, send it every log message that
738 we generated between startup and opening it. Previously, log
739 messages that were generated before opening the log file were only
740 logged to stdout. Closes ticket 6938.
741 - Add a TruncateLogFile option to overwrite logs instead of
742 appending to them. Closes ticket #5583.
744 o Minor features (portability, Solaris):
745 - Threads are no longer disabled by default on Solaris; we believe
746 that the versions of Solaris with broken threading support are all
747 obsolete by now. Resolves ticket 9495.
749 o Minor features (relay):
750 - Re-check our address after we detect a changed IP address from
751 getsockname(). This ensures that the controller command "GETINFO
752 address" will report the correct value. Resolves ticket 11582.
754 - A new AccountingRule option lets Relays set whether they'd like
755 AccountingMax to be applied separately to inbound and outbound
756 traffic, or applied to the sum of inbound and outbound traffic.
757 Resolves ticket 961. Patch by "chobe".
759 o Minor features (testing networks):
760 - Add the TestingDirAuthVoteExit option, which lists nodes to assign
761 the "Exit" flag regardless of their uptime, bandwidth, or exit
762 policy. TestingTorNetwork must be set for this option to have any
763 effect. Previously, authorities would take up to 35 minutes to
764 give nodes the Exit flag in a test network. Partially implements
767 o Minor features (validation):
768 - Check all date/time values passed to tor_timegm and
769 parse_rfc1123_time for validity, taking leap years into account.
770 Improves HTTP header validation. Implemented with bug 13476.
771 - In correct_tm(), limit the range of values returned by system
772 localtime(_r) and gmtime(_r) to be between the years 1 and 8099.
773 This means we don't have to deal with negative or too large dates,
774 even if a clock is wrong. Otherwise we might fail to read a file
775 written by us which includes such a date. Fixes bug 13476.
777 o Minor bugfixes (bridge clients):
778 - When configured to use a bridge without an identity digest (not
779 recommended), avoid launching an extra channel to it when
780 bootstrapping. Fixes bug 7733; bugfix on 0.2.4.4-alpha.
782 o Minor bugfixes (bridges):
783 - When DisableNetwork is set, do not launch pluggable transport
784 plugins, and if any are running, terminate them. Fixes bug 13213;
785 bugfix on 0.2.3.6-alpha.
787 o Minor bugfixes (C correctness):
788 - Fix several instances of possible integer overflow/underflow/NaN.
789 Fixes bug 13104; bugfix on 0.2.3.1-alpha and later. Patches
791 - In circuit_build_times_calculate_timeout() in circuitstats.c,
792 avoid dividing by zero in the pareto calculations. This traps
793 under clang's "undefined-trap" sanitizer. Fixes bug 13290; bugfix
794 on tor-0.2.2.2-alpha.
795 - Fix an integer overflow in format_time_interval(). Fixes bug
796 13393; bugfix on 0.2.0.10-alpha.
797 - Set the correct day of year value when the system's localtime(_r)
798 or gmtime(_r) functions fail to set struct tm. Not externally
799 visible. Fixes bug 13476; bugfix on 0.0.2pre14.
800 - Avoid unlikely signed integer overflow in tor_timegm on systems
801 with 32-bit time_t. Fixes bug 13476; bugfix on 0.0.2pre14.
803 o Minor bugfixes (client):
804 - Fix smartlist_choose_node_by_bandwidth() so that relays with the
805 BadExit flag are not considered worthy candidates. Fixes bug
806 13066; bugfix on 0.1.2.3-alpha.
807 - Use the consensus schedule for downloading consensuses, and not
808 the generic schedule. Fixes bug 11679; bugfix on 0.2.2.6-alpha.
809 - Handle unsupported or malformed SOCKS5 requests properly by
810 responding with the appropriate error message before closing the
811 connection. Fixes bugs 12971 and 13314; bugfix on 0.0.2pre13.
813 o Minor bugfixes (client, torrc):
814 - Stop modifying the value of our DirReqStatistics torrc option just
815 because we're not a bridge or relay. This bug was causing Tor
816 Browser users to write "DirReqStatistics 0" in their torrc files
817 as if they had chosen to change the config. Fixes bug 4244; bugfix
819 - When GeoIPExcludeUnknown is enabled, do not incorrectly decide
820 that our options have changed every time we SIGHUP. Fixes bug
821 9801; bugfix on 0.2.4.10-alpha. Patch from "qwerty1".
823 o Minor bugfixes (controller):
824 - Return an error when the second or later arguments of the
825 "setevents" controller command are invalid events. Previously we
826 would return success while silently skipping invalid events. Fixes
827 bug 13205; bugfix on 0.2.3.2-alpha. Reported by "fpxnns".
829 o Minor bugfixes (directory system):
830 - Always believe that v3 directory authorities serve extra-info
831 documents, whether they advertise "caches-extra-info" or not.
832 Fixes part of bug 11683; bugfix on 0.2.0.1-alpha.
833 - When running as a v3 directory authority, advertise that you serve
834 extra-info documents so that clients who want them can find them
835 from you too. Fixes part of bug 11683; bugfix on 0.2.0.1-alpha.
836 - Check the BRIDGE_DIRINFO flag bitwise rather than using equality.
837 Previously, directories offering BRIDGE_DIRINFO and some other
838 flag (i.e. microdescriptors or extrainfo) would be ignored when
839 looking for bridges. Partially fixes bug 13163; bugfix
842 o Minor bugfixes (networking):
843 - Check for orconns and use connection_or_close_for_error() rather
844 than connection_mark_for_close() directly in the getsockopt()
845 failure case of connection_handle_write_impl(). Fixes bug 11302;
846 bugfix on 0.2.4.4-alpha.
848 o Minor bugfixes (relay):
849 - When generating our family list, remove spaces from around the
850 entries. Fixes bug 12728; bugfix on 0.2.1.7-alpha.
851 - If our previous bandwidth estimate was 0 bytes, allow publishing a
852 new relay descriptor immediately. Fixes bug 13000; bugfix
855 o Minor bugfixes (testing networks):
856 - Fix TestingDirAuthVoteGuard to properly give out Guard flags in a
857 testing network. Fixes bug 13064; bugfix on 0.2.5.2-alpha.
858 - Stop using the default authorities in networks which provide both
859 AlternateDirAuthority and AlternateBridgeAuthority. Partially
860 fixes bug 13163; bugfix on 0.2.0.13-alpha.
862 o Minor bugfixes (testing):
863 - Stop spawn test failures due to a race condition between the
864 SIGCHLD handler updating the process status, and the test reading
865 it. Fixes bug 13291; bugfix on 0.2.3.3-alpha.
867 o Minor bugfixes (testing, Windows):
868 - Avoid passing an extra backslash when creating a temporary
869 directory for running the unit tests on Windows. Fixes bug 12392;
870 bugfix on 0.2.2.25-alpha. Patch from Gisle Vanem.
872 o Minor bugfixes (windows):
873 - Remove code to special-case handling of NTE_BAD_KEYSET when
874 acquiring windows CryptoAPI context. This error can't actually
875 occur for the parameters we're providing. Fixes bug 10816; bugfix
878 o Minor bugfixes (zlib):
879 - Avoid truncating a zlib stream when trying to finalize it with an
880 empty output buffer. Fixes bug 11824; bugfix on 0.1.1.23.
883 - Allow our configure script to build correctly with autoconf 2.62
884 again. Fixes bug 12693; bugfix on 0.2.5.2-alpha.
885 - Improve the error message from ./configure to make it clear that
886 when asciidoc has not been found, the user will have to either add
887 --disable-asciidoc argument or install asciidoc. Resolves
890 o Code simplification and refactoring:
891 - Change the entry_is_live() function to take named bitfield
892 elements instead of an unnamed list of booleans. Closes
894 - Refactor and unit-test entry_is_time_to_retry() in entrynodes.c.
895 Resolves ticket 12205.
896 - Use calloc and reallocarray functions instead of multiply-
897 then-malloc. This makes it less likely for us to fall victim to an
898 integer overflow attack when allocating. Resolves ticket 12855.
899 - Use the standard macro name SIZE_MAX, instead of our
901 - Document usage of the NO_DIRINFO and ALL_DIRINFO flags clearly in
902 functions which take them as arguments. Replace 0 with NO_DIRINFO
903 in a function call for clarity. Seeks to prevent future issues
905 - Avoid 4 null pointer errors under clang static analysis by using
906 tor_assert() to prove that the pointers aren't null. Fixes
908 - Rework the API of policies_parse_exit_policy() to use a bitmask to
909 represent parsing options, instead of a confusing mess of
910 booleans. Resolves ticket 8197.
911 - Introduce a helper function to parse ExitPolicy in
912 or_options_t structure.
915 - Add a doc/TUNING document with tips for handling large numbers of
916 TCP connections when running busy Tor relay. Update the warning
917 message to point to this file when running out of sockets
918 operating system is allowing to use simultaneously. Resolves
922 - We no longer remind the user about configuration options that have
923 been obsolete since 0.2.3.x or earlier. Patch by Adrien Bak.
924 - Remove our old, non-weighted bandwidth-based node selection code.
925 Previously, we used it as a fallback when we couldn't perform
926 weighted bandwidth-based node selection. But that would only
927 happen in the cases where we had no consensus, or when we had a
928 consensus generated by buggy or ancient directory authorities. In
929 either case, it's better to use the more modern, better maintained
930 algorithm, with reasonable defaults for the weights. Closes
932 - Remove the --disable-curve25519 configure option. Relays and
933 clients now are required to support curve25519 and the
935 - The old "StrictEntryNodes" and "StrictExitNodes" options, which
936 used to be deprecated synonyms for "StrictNodes", are now marked
937 obsolete. Resolves ticket 12226.
938 - Clients don't understand the BadDirectory flag in the consensus
939 anymore, and ignore it.
942 - Refactor the function that chooses guard nodes so that it can more
943 easily be tested; write some tests for it.
944 - Fix and re-enable the fgets_eagain unit test. Fixes bug 12503;
945 bugfix on 0.2.3.1-alpha. Patch from "cypherpunks."
946 - Create unit tests for format_time_interval(). With bug 13393.
947 - Add unit tests for tor_timegm signed overflow, tor_timegm and
948 parse_rfc1123_time validity checks, correct_tm year clamping. Unit
949 tests (visible) fixes in bug 13476.
950 - Add a "coverage-html" make target to generate HTML-visualized
951 coverage results when building with --enable-coverage. (Requires
952 lcov.) Patch from Kevin Murray.
953 - Enable the backtrace handler (where supported) when running the
955 - Revise all unit tests that used the legacy test_* macros to
956 instead use the recommended tt_* macros. This patch was generated
957 with coccinelle, to avoid manual errors. Closes ticket 13119.
959 o Distribution (systemd):
960 - systemd unit file: only allow tor to write to /var/lib/tor and
961 /var/log/tor. The rest of the filesystem is accessible for reading
962 only. Patch by intrigeri; resolves ticket 12751.
963 - systemd unit file: ensure that the process and all its children
964 can never gain new privileges. Patch by intrigeri; resolves
966 - systemd unit file: set up /var/run/tor as writable for the Tor
967 service. Patch by intrigeri; resolves ticket 13196.
969 o Removed features (directory authorities):
970 - Remove code that prevented authorities from listing Tor relays
971 affected by CVE-2011-2769 as guards. These relays are already
972 rejected altogether due to the minimum version requirement of
973 0.2.3.16-alpha. Closes ticket 13152.
974 - The "AuthDirRejectUnlisted" option no longer has any effect, as
975 the fingerprints file (approved-routers) has been deprecated.
976 - Directory authorities do not support being Naming dirauths anymore.
977 The "NamingAuthoritativeDir" config option is now obsolete.
978 - Directory authorities do not support giving out the BadDirectory
980 - Directory authorities no longer advertise or support consensus
981 methods 1 through 12 inclusive. These consensus methods were
982 obsolete and/or insecure: maintaining the ability to support them
983 served no good purpose. Implements part of proposal 215; closes
986 o Testing (test-network.sh):
987 - Stop using "echo -n", as some shells' built-in echo doesn't
988 support "-n". Instead, use "/bin/echo -n". Partially fixes
990 - Stop an apparent test-network hang when used with make -j2. Fixes
992 - Add a --delay option to test-network.sh, which configures the
993 delay before the chutney network tests for data transmission.
994 Partially implements ticket 13161.
997 Changes in version 0.2.5.10 - 2014-10-24
998 Tor 0.2.5.10 is the first stable release in the 0.2.5 series.
1000 It adds several new security features, including improved
1001 denial-of-service resistance for relays, new compiler hardening
1002 options, and a system-call sandbox for hardened installations on Linux
1003 (requires seccomp2). The controller protocol has several new features,
1004 resolving IPv6 addresses should work better than before, and relays
1005 should be a little more CPU-efficient. We've added support for more
1006 OpenBSD and FreeBSD transparent proxy types. We've improved the build
1007 system and testing infrastructure to allow unit testing of more parts
1008 of the Tor codebase. Finally, we've addressed several nagging pluggable
1009 transport usability issues, and included numerous other small bugfixes
1010 and features mentioned below.
1012 This release marks end-of-life for Tor 0.2.3.x; those Tor versions
1013 have accumulated many known flaws; everyone should upgrade.
1015 o Deprecated versions:
1016 - Tor 0.2.3.x has reached end-of-life; it has received no patches or
1017 attention for some while.
1020 Changes in version 0.2.5.9-rc - 2014-10-20
1021 Tor 0.2.5.9-rc is the third release candidate for the Tor 0.2.5.x
1022 series. It disables SSL3 in response to the recent "POODLE" attack
1023 (even though POODLE does not affect Tor). It also works around a crash
1024 bug caused by some operating systems' response to the "POODLE" attack
1025 (which does affect Tor). It also contains a few miscellaneous fixes.
1027 o Major security fixes:
1028 - Disable support for SSLv3. All versions of OpenSSL in use with Tor
1029 today support TLS 1.0 or later, so we can safely turn off support
1030 for this old (and insecure) protocol. Fixes bug 13426.
1032 o Major bugfixes (openssl bug workaround):
1033 - Avoid crashing when using OpenSSL version 0.9.8zc, 1.0.0o, or
1034 1.0.1j, built with the 'no-ssl3' configuration option. Fixes bug
1035 13471. This is a workaround for an OpenSSL bug.
1038 - Disable the sandbox name resolver cache when running tor-resolve:
1039 tor-resolve doesn't use the sandbox code, and turning it on was
1040 breaking attempts to do tor-resolve on a non-default server on
1041 Linux. Fixes bug 13295; bugfix on 0.2.5.3-alpha.
1043 o Compilation fixes:
1044 - Build and run correctly on systems like OpenBSD-current that have
1045 patched OpenSSL to remove get_cipher_by_char and/or its
1046 implementations. Fixes issue 13325.
1048 o Downgraded warnings:
1049 - Downgrade the severity of the 'unexpected sendme cell from client'
1050 from 'warn' to 'protocol warning'. Closes ticket 8093.
1053 Changes in version 0.2.4.25 - 2014-10-20
1054 Tor 0.2.4.25 disables SSL3 in response to the recent "POODLE" attack
1055 (even though POODLE does not affect Tor). It also works around a crash
1056 bug caused by some operating systems' response to the "POODLE" attack
1057 (which does affect Tor).
1059 o Major security fixes (also in 0.2.5.9-rc):
1060 - Disable support for SSLv3. All versions of OpenSSL in use with Tor
1061 today support TLS 1.0 or later, so we can safely turn off support
1062 for this old (and insecure) protocol. Fixes bug 13426.
1064 o Major bugfixes (openssl bug workaround, also in 0.2.5.9-rc):
1065 - Avoid crashing when using OpenSSL version 0.9.8zc, 1.0.0o, or
1066 1.0.1j, built with the 'no-ssl3' configuration option. Fixes bug
1067 13471. This is a workaround for an OpenSSL bug.
1070 Changes in version 0.2.5.8-rc - 2014-09-22
1071 Tor 0.2.5.8-rc is the second release candidate for the Tor 0.2.5.x
1072 series. It fixes a bug that affects consistency and speed when
1073 connecting to hidden services, and it updates the location of one of
1074 the directory authorities.
1077 - Clients now send the correct address for their chosen rendezvous
1078 point when trying to access a hidden service. They used to send
1079 the wrong address, which would still work some of the time because
1080 they also sent the identity digest of the rendezvous point, and if
1081 the hidden service happened to try connecting to the rendezvous
1082 point from a relay that already had a connection open to it,
1083 the relay would reuse that connection. Now connections to hidden
1084 services should be more robust and faster. Also, this bug meant
1085 that clients were leaking to the hidden service whether they were
1086 on a little-endian (common) or big-endian (rare) system, which for
1087 some users might have reduced their anonymity. Fixes bug 13151;
1088 bugfix on 0.2.1.5-alpha.
1090 o Directory authority changes:
1091 - Change IP address for gabelmoo (v3 directory authority).
1094 Changes in version 0.2.4.24 - 2014-09-22
1095 Tor 0.2.4.24 fixes a bug that affects consistency and speed when
1096 connecting to hidden services, and it updates the location of one of
1097 the directory authorities.
1100 - Clients now send the correct address for their chosen rendezvous
1101 point when trying to access a hidden service. They used to send
1102 the wrong address, which would still work some of the time because
1103 they also sent the identity digest of the rendezvous point, and if
1104 the hidden service happened to try connecting to the rendezvous
1105 point from a relay that already had a connection open to it,
1106 the relay would reuse that connection. Now connections to hidden
1107 services should be more robust and faster. Also, this bug meant
1108 that clients were leaking to the hidden service whether they were
1109 on a little-endian (common) or big-endian (rare) system, which for
1110 some users might have reduced their anonymity. Fixes bug 13151;
1111 bugfix on 0.2.1.5-alpha.
1113 o Directory authority changes:
1114 - Change IP address for gabelmoo (v3 directory authority).
1116 o Minor features (geoip):
1117 - Update geoip and geoip6 to the August 7 2014 Maxmind GeoLite2
1121 Changes in version 0.2.5.7-rc - 2014-09-11
1122 Tor 0.2.5.7-rc fixes several regressions from earlier in the 0.2.5.x
1123 release series, and some long-standing bugs related to ORPort reachability
1124 testing and failure to send CREATE cells. It is the first release
1125 candidate for the Tor 0.2.5.x series.
1127 o Major bugfixes (client, startup):
1128 - Start making circuits as soon as DisabledNetwork is turned off.
1129 When Tor started with DisabledNetwork set, it would correctly
1130 conclude that it shouldn't build circuits, but it would mistakenly
1131 cache this conclusion, and continue believing it even when
1132 DisableNetwork is set to 0. Fixes the bug introduced by the fix
1133 for bug 11200; bugfix on 0.2.5.4-alpha.
1134 - Resume expanding abbreviations for command-line options. The fix
1135 for bug 4647 accidentally removed our hack from bug 586 that
1136 rewrote HashedControlPassword to __HashedControlSessionPassword
1137 when it appears on the commandline (which allowed the user to set
1138 her own HashedControlPassword in the torrc file while the
1139 controller generates a fresh session password for each run). Fixes
1140 bug 12948; bugfix on 0.2.5.1-alpha.
1141 - Warn about attempts to run hidden services and relays in the same
1142 process: that's probably not a good idea. Closes ticket 12908.
1144 o Major bugfixes (relay):
1145 - Avoid queuing or sending destroy cells for circuit ID zero when we
1146 fail to send a CREATE cell. Fixes bug 12848; bugfix on 0.0.8pre1.
1147 Found and fixed by "cypherpunks".
1148 - Fix ORPort reachability detection on relays running behind a
1149 proxy, by correctly updating the "local" mark on the controlling
1150 channel when changing the address of an or_connection_t after the
1151 handshake. Fixes bug 12160; bugfix on 0.2.4.4-alpha.
1153 o Minor features (bridge):
1154 - Add an ExtORPortCookieAuthFileGroupReadable option to make the
1155 cookie file for the ExtORPort g+r by default.
1157 o Minor features (geoip):
1158 - Update geoip and geoip6 to the August 7 2014 Maxmind GeoLite2
1161 o Minor bugfixes (logging):
1162 - Reduce the log severity of the "Pluggable transport proxy does not
1163 provide any needed transports and will not be launched." message,
1164 since Tor Browser includes several ClientTransportPlugin lines in
1165 its torrc-defaults file, leading every Tor Browser user who looks
1166 at her logs to see these notices and wonder if they're dangerous.
1167 Resolves bug 13124; bugfix on 0.2.5.3-alpha.
1168 - Downgrade "Unexpected onionskin length after decryption" warning
1169 to a protocol-warn, since there's nothing relay operators can do
1170 about a client that sends them a malformed create cell. Resolves
1171 bug 12996; bugfix on 0.0.6rc1.
1172 - Log more specific warnings when we get an ESTABLISH_RENDEZVOUS
1173 cell on a cannibalized or non-OR circuit. Resolves ticket 12997.
1174 - When logging information about an EXTEND2 or EXTENDED2 cell, log
1175 their names correctly. Fixes part of bug 12700; bugfix
1177 - When logging information about a relay cell whose command we don't
1178 recognize, log its command as an integer. Fixes part of bug 12700;
1179 bugfix on 0.2.1.10-alpha.
1180 - Escape all strings from the directory connection before logging
1181 them. Fixes bug 13071; bugfix on 0.1.1.15. Patch from "teor".
1183 o Minor bugfixes (controller):
1184 - Restore the functionality of CookieAuthFileGroupReadable. Fixes
1185 bug 12864; bugfix on 0.2.5.1-alpha.
1186 - Actually send TRANSPORT_LAUNCHED and HS_DESC events to
1187 controllers. Fixes bug 13085; bugfix on 0.2.5.1-alpha. Patch
1190 o Minor bugfixes (compilation):
1191 - Fix compilation of test.h with MSVC. Patch from Gisle Vanem;
1192 bugfix on 0.2.5.5-alpha.
1193 - Make the nmake make files work again. Fixes bug 13081. Bugfix on
1194 0.2.5.1-alpha. Patch from "NewEraCracker".
1195 - In routerlist_assert_ok(), don't take the address of a
1196 routerinfo's cache_info member unless that routerinfo is non-NULL.
1197 Fixes bug 13096; bugfix on 0.1.1.9-alpha. Patch by "teor".
1198 - Fix a large number of false positive warnings from the clang
1199 analyzer static analysis tool. This should make real warnings
1200 easier for clang analyzer to find. Patch from "teor". Closes
1203 o Distribution (systemd):
1204 - Verify configuration file via ExecStartPre in the systemd unit
1205 file. Patch from intrigeri; resolves ticket 12730.
1206 - Explicitly disable RunAsDaemon in the systemd unit file. Our
1207 current systemd unit uses "Type = simple", so systemd does not
1208 expect tor to fork. If the user has "RunAsDaemon 1" in their
1209 torrc, then things won't work as expected. This is e.g. the case
1210 on Debian (and derivatives), since there we pass "--defaults-torrc
1211 /usr/share/tor/tor-service-defaults-torrc" (that contains
1212 "RunAsDaemon 1") by default. Patch by intrigeri; resolves
1216 - Adjust the URLs in the README to refer to the new locations of
1217 several documents on the website. Fixes bug 12830. Patch from
1219 - Document 'reject6' and 'accept6' ExitPolicy entries. Resolves
1223 Changes in version 0.2.5.6-alpha - 2014-07-28
1224 Tor 0.2.5.6-alpha brings us a big step closer to slowing down the
1225 risk from guard rotation, and fixes a variety of other issues to get
1226 us closer to a release candidate.
1228 o Major features (also in 0.2.4.23):
1229 - Make the number of entry guards configurable via a new
1230 NumEntryGuards consensus parameter, and the number of directory
1231 guards configurable via a new NumDirectoryGuards consensus
1232 parameter. Implements ticket 12688.
1234 o Major bugfixes (also in 0.2.4.23):
1235 - Fix a bug in the bounds-checking in the 32-bit curve25519-donna
1236 implementation that caused incorrect results on 32-bit
1237 implementations when certain malformed inputs were used along with
1238 a small class of private ntor keys. This bug does not currently
1239 appear to allow an attacker to learn private keys or impersonate a
1240 Tor server, but it could provide a means to distinguish 32-bit Tor
1241 implementations from 64-bit Tor implementations. Fixes bug 12694;
1242 bugfix on 0.2.4.8-alpha. Bug found by Robert Ransom; fix from
1246 - Perform circuit cleanup operations even when circuit
1247 construction operations are disabled (because the network is
1248 disabled, or because there isn't enough directory information).
1249 Previously, when we were not building predictive circuits, we
1250 were not closing expired circuits either. Fixes bug 8387; bugfix on
1251 0.1.1.11-alpha. This bug became visible in 0.2.4.10-alpha when we
1252 became more strict about when we have "enough directory information
1256 - Authorities now assign the Guard flag to the fastest 25% of the
1257 network (it used to be the fastest 50%). Also raise the consensus
1258 weight that guarantees the Guard flag from 250 to 2000. For the
1259 current network, this results in about 1100 guards, down from 2500.
1260 This step paves the way for moving the number of entry guards
1261 down to 1 (proposal 236) while still providing reasonable expected
1262 performance for most users. Implements ticket 12690.
1263 - Update geoip and geoip6 to the July 10 2014 Maxmind GeoLite2
1265 - Slightly enhance the diagnostic message for bug 12184.
1267 o Minor bugfixes (also in 0.2.4.23):
1268 - Warn and drop the circuit if we receive an inbound 'relay early'
1269 cell. Those used to be normal to receive on hidden service circuits
1270 due to bug 1038, but the buggy Tor versions are long gone from
1271 the network so we can afford to resume watching for them. Resolves
1272 the rest of bug 1038; bugfix on 0.2.1.19.
1273 - Correct a confusing error message when trying to extend a circuit
1274 via the control protocol but we don't know a descriptor or
1275 microdescriptor for one of the specified relays. Fixes bug 12718;
1276 bugfix on 0.2.3.1-alpha.
1279 - Fix compilation when building with bufferevents enabled. (This
1280 configuration is still not expected to work, however.)
1281 Fixes bugs 12438, 12474, 11578; bugfixes on 0.2.5.1-alpha and
1282 0.2.5.3-alpha. Patches from Anthony G. Basile and Sathyanarayanan
1284 - Compile correctly with builds and forks of OpenSSL (such as
1285 LibreSSL) that disable compression. Fixes bug 12602; bugfix on
1286 0.2.1.1-alpha. Patch from "dhill".
1289 Changes in version 0.2.4.23 - 2014-07-28
1290 Tor 0.2.4.23 brings us a big step closer to slowing down the risk from
1291 guard rotation, and also backports several important fixes from the
1292 Tor 0.2.5 alpha release series.
1295 - Clients now look at the "usecreatefast" consensus parameter to
1296 decide whether to use CREATE_FAST or CREATE cells for the first hop
1297 of their circuit. This approach can improve security on connections
1298 where Tor's circuit handshake is stronger than the available TLS
1299 connection security levels, but the tradeoff is more computational
1300 load on guard relays. Implements proposal 221. Resolves ticket 9386.
1301 - Make the number of entry guards configurable via a new
1302 NumEntryGuards consensus parameter, and the number of directory
1303 guards configurable via a new NumDirectoryGuards consensus
1304 parameter. Implements ticket 12688.
1307 - Fix a bug in the bounds-checking in the 32-bit curve25519-donna
1308 implementation that caused incorrect results on 32-bit
1309 implementations when certain malformed inputs were used along with
1310 a small class of private ntor keys. This bug does not currently
1311 appear to allow an attacker to learn private keys or impersonate a
1312 Tor server, but it could provide a means to distinguish 32-bit Tor
1313 implementations from 64-bit Tor implementations. Fixes bug 12694;
1314 bugfix on 0.2.4.8-alpha. Bug found by Robert Ransom; fix from
1318 - Warn and drop the circuit if we receive an inbound 'relay early'
1319 cell. Those used to be normal to receive on hidden service circuits
1320 due to bug 1038, but the buggy Tor versions are long gone from
1321 the network so we can afford to resume watching for them. Resolves
1322 the rest of bug 1038; bugfix on 0.2.1.19.
1323 - Correct a confusing error message when trying to extend a circuit
1324 via the control protocol but we don't know a descriptor or
1325 microdescriptor for one of the specified relays. Fixes bug 12718;
1326 bugfix on 0.2.3.1-alpha.
1327 - Avoid an illegal read from stack when initializing the TLS
1328 module using a version of OpenSSL without all of the ciphers
1329 used by the v2 link handshake. Fixes bug 12227; bugfix on
1330 0.2.4.8-alpha. Found by "starlight".
1333 - Update geoip and geoip6 to the July 10 2014 Maxmind GeoLite2
1337 Changes in version 0.2.5.5-alpha - 2014-06-18
1338 Tor 0.2.5.5-alpha fixes a wide variety of remaining issues in the Tor
1339 0.2.5.x release series, including a couple of DoS issues, some
1340 performance regressions, a large number of bugs affecting the Linux
1341 seccomp2 sandbox code, and various other bugfixes. It also adds
1342 diagnostic bugfixes for a few tricky issues that we're trying to
1345 o Major features (security, traffic analysis resistance):
1346 - Several major improvements to the algorithm used to decide when to
1347 close TLS connections. Previous versions of Tor closed connections
1348 at a fixed interval after the last time a non-padding cell was
1349 sent over the connection, regardless of the target of the
1350 connection. Now, we randomize the intervals by adding up to 50% of
1351 their base value, we measure the length of time since connection
1352 last had at least one circuit, and we allow connections to known
1353 ORs to remain open a little longer (15 minutes instead of 3
1354 minutes minimum). These changes should improve Tor's resistance
1355 against some kinds of traffic analysis, and lower some overhead
1356 from needlessly closed connections. Fixes ticket 6799.
1357 Incidentally fixes ticket 12023; bugfix on 0.2.5.1-alpha.
1359 o Major bugfixes (security, OOM, new since 0.2.5.4-alpha, also in 0.2.4.22):
1360 - Fix a memory leak that could occur if a microdescriptor parse
1361 fails during the tokenizing step. This bug could enable a memory
1362 exhaustion attack by directory servers. Fixes bug 11649; bugfix
1365 o Major bugfixes (security, directory authorities):
1366 - Directory authorities now include a digest of each relay's
1367 identity key as a part of its microdescriptor.
1369 This is a workaround for bug 11743 (reported by "cypherpunks"),
1370 where Tor clients do not support receiving multiple
1371 microdescriptors with the same SHA256 digest in the same
1372 consensus. When clients receive a consensus like this, they only
1373 use one of the relays. Without this fix, a hostile relay could
1374 selectively disable some client use of target relays by
1375 constructing a router descriptor with a different identity and the
1376 same microdescriptor parameters and getting the authorities to
1377 list it in a microdescriptor consensus. This fix prevents an
1378 attacker from causing a microdescriptor collision, because the
1379 router's identity is not forgeable.
1381 o Major bugfixes (relay):
1382 - Use a direct dirport connection when uploading non-anonymous
1383 descriptors to the directory authorities. Previously, relays would
1384 incorrectly use tunnel connections under a fairly wide variety of
1385 circumstances. Fixes bug 11469; bugfix on 0.2.4.3-alpha.
1386 - When a circuit accidentally has the same circuit ID for its
1387 forward and reverse direction, correctly detect the direction of
1388 cells using that circuit. Previously, this bug made roughly one
1389 circuit in a million non-functional. Fixes bug 12195; this is a
1390 bugfix on every version of Tor.
1392 o Major bugfixes (client, pluggable transports):
1393 - When managing pluggable transports, use OS notification facilities
1394 to learn if they have crashed, and don't attempt to kill any
1395 process that has already exited. Fixes bug 8746; bugfix
1398 o Minor features (diagnostic):
1399 - When logging a warning because of bug 7164, additionally check the
1400 hash table for consistency (as proposed on ticket 11737). This may
1401 help diagnose bug 7164.
1402 - When we log a heartbeat, log how many one-hop circuits we have
1403 that are at least 30 minutes old, and log status information about
1404 a few of them. This is an attempt to track down bug 8387.
1405 - When encountering an unexpected CR while writing text to a file on
1406 Windows, log the name of the file. Should help diagnosing
1408 - Give more specific warnings when a client notices that an onion
1409 handshake has failed. Fixes ticket 9635.
1410 - Add significant new logging code to attempt to diagnose bug 12184,
1411 where relays seem to run out of available circuit IDs.
1412 - Improve the diagnostic log message for bug 8387 even further to
1413 try to improve our odds of figuring out why one-hop directory
1414 circuits sometimes do not get closed.
1416 o Minor features (security, memory management):
1417 - Memory allocation tricks (mempools and buffer freelists) are now
1418 disabled by default. You can turn them back on with
1419 --enable-mempools and --enable-buf-freelists respectively. We're
1420 disabling these features because malloc performance is good enough
1421 on most platforms, and a similar feature in OpenSSL exacerbated
1422 exploitation of the Heartbleed attack. Resolves ticket 11476.
1424 o Minor features (security):
1425 - Apply the secure SipHash-2-4 function to the hash table mapping
1426 circuit IDs and channels to circuits. We missed this one when we
1427 were converting all the other hash functions to use SipHash back
1428 in 0.2.5.3-alpha. Resolves ticket 11750.
1430 o Minor features (build):
1431 - The configure script has a --disable-seccomp option to turn off
1432 support for libseccomp on systems that have it, in case it (or
1433 Tor's use of it) is broken. Resolves ticket 11628.
1435 o Minor features (other):
1436 - Update geoip and geoip6 to the June 4 2014 Maxmind GeoLite2
1439 o Minor bugfixes (security, new since 0.2.5.4-alpha, also in 0.2.4.22):
1440 - When running a hidden service, do not allow TunneledDirConns 0;
1441 this will keep the hidden service from running, and also
1442 make it publish its descriptors directly over HTTP. Fixes bug 10849;
1443 bugfix on 0.2.1.1-alpha.
1445 o Minor bugfixes (performance):
1446 - Avoid a bug where every successful connection made us recompute
1447 the flag telling us whether we have sufficient information to
1448 build circuits. Previously, we would forget our cached value
1449 whenever we successfully opened a channel (or marked a router as
1450 running or not running for any other reason), regardless of
1451 whether we had previously believed the router to be running. This
1452 forced us to run an expensive update operation far too often.
1453 Fixes bug 12170; bugfix on 0.1.2.1-alpha.
1454 - Avoid using tor_memeq() for checking relay cell integrity. This
1455 removes a possible performance bottleneck. Fixes part of bug
1456 12169; bugfix on 0.2.1.31.
1458 o Minor bugfixes (compilation):
1459 - Fix compilation of test_status.c when building with MVSC. Bugfix
1460 on 0.2.5.4-alpha. Patch from Gisle Vanem.
1461 - Resolve GCC complaints on OpenBSD about discarding constness in
1462 TO_{ORIGIN,OR}_CIRCUIT functions. Fixes part of bug 11633; bugfix
1463 on 0.1.1.23. Patch from Dana Koch.
1464 - Resolve clang complaints on OpenBSD with -Wshorten-64-to-32 due to
1465 treatment of long and time_t as comparable types. Fixes part of
1466 bug 11633. Patch from Dana Koch.
1467 - Make Tor compile correctly with --disable-buf-freelists. Fixes bug
1468 11623; bugfix on 0.2.5.3-alpha.
1469 - When deciding whether to build the 64-bit curve25519
1470 implementation, detect platforms where we can compile 128-bit
1471 arithmetic but cannot link it. Fixes bug 11729; bugfix on
1472 0.2.4.8-alpha. Patch from "conradev".
1473 - Fix compilation when DNS_CACHE_DEBUG is enabled. Fixes bug 11761;
1474 bugfix on 0.2.3.13-alpha. Found by "cypherpunks".
1475 - Fix compilation with dmalloc. Fixes bug 11605; bugfix
1478 o Minor bugfixes (Directory server):
1479 - When sending a compressed set of descriptors or microdescriptors,
1480 make sure to finalize the zlib stream. Previously, we would write
1481 all the compressed data, but if the last descriptor we wanted to
1482 send was missing or too old, we would not mark the stream as
1483 finished. This caused problems for decompression tools. Fixes bug
1484 11648; bugfix on 0.1.1.23.
1486 o Minor bugfixes (Linux seccomp sandbox):
1487 - Make the seccomp sandbox code compile under ARM Linux. Fixes bug
1488 11622; bugfix on 0.2.5.1-alpha.
1489 - Avoid crashing when re-opening listener ports with the seccomp
1490 sandbox active. Fixes bug 12115; bugfix on 0.2.5.1-alpha.
1491 - Avoid crashing with the seccomp sandbox enabled along with
1492 ConstrainedSockets. Fixes bug 12139; bugfix on 0.2.5.1-alpha.
1493 - When we receive a SIGHUP with the sandbox enabled, correctly
1494 support rotating our log files. Fixes bug 12032; bugfix
1496 - Avoid crash when running with sandboxing enabled and
1497 DirReqStatistics not disabled. Fixes bug 12035; bugfix
1499 - Fix a "BUG" warning when trying to write bridge-stats files with
1500 the Linux syscall sandbox filter enabled. Fixes bug 12041; bugfix
1502 - Prevent the sandbox from crashing on startup when run with the
1503 --enable-expensive-hardening configuration option. Fixes bug
1504 11477; bugfix on 0.2.5.4-alpha.
1505 - When running with DirPortFrontPage and sandboxing both enabled,
1506 reload the DirPortFrontPage correctly when restarting. Fixes bug
1507 12028; bugfix on 0.2.5.1-alpha.
1508 - Don't try to enable the sandbox when using the Tor binary to check
1509 its configuration, hash a passphrase, or so on. Doing so was
1510 crashing on startup for some users. Fixes bug 11609; bugfix
1512 - Avoid warnings when running with sandboxing and node statistics
1513 enabled at the same time. Fixes part of 12064; bugfix on
1514 0.2.5.1-alpha. Patch from Michael Wolf.
1515 - Avoid warnings when running with sandboxing enabled at the same
1516 time as cookie authentication, hidden services, or directory
1517 authority voting. Fixes part of 12064; bugfix on 0.2.5.1-alpha.
1518 - Do not allow options that require calls to exec to be enabled
1519 alongside the seccomp2 sandbox: they will inevitably crash. Fixes
1520 bug 12043; bugfix on 0.2.5.1-alpha.
1521 - Handle failures in getpwnam()/getpwuid() when running with the
1522 User option set and the Linux syscall sandbox enabled. Fixes bug
1523 11946; bugfix on 0.2.5.1-alpha.
1524 - Refactor the getaddrinfo workaround that the seccomp sandbox uses
1525 to avoid calling getaddrinfo() after installing the sandbox
1526 filters. Previously, it preloaded a cache with the IPv4 address
1527 for our hostname, and nothing else. Now, it loads the cache with
1528 every address that it used to initialize the Tor process. Fixes
1529 bug 11970; bugfix on 0.2.5.1-alpha.
1531 o Minor bugfixes (pluggable transports):
1532 - Enable the ExtORPortCookieAuthFile option, to allow changing the
1533 default location of the authentication token for the extended OR
1534 Port as used by sever-side pluggable transports. We had
1535 implemented this option before, but the code to make it settable
1536 had been omitted. Fixes bug 11635; bugfix on 0.2.5.1-alpha.
1537 - Avoid another 60-second delay when starting Tor in a pluggable-
1538 transport-using configuration when we already have cached
1539 descriptors for our bridges. Fixes bug 11965; bugfix
1542 o Minor bugfixes (client):
1543 - Avoid "Tried to open a socket with DisableNetwork set" warnings
1544 when starting a client with bridges configured and DisableNetwork
1545 set. (Tor launcher starts Tor with DisableNetwork set the first
1546 time it runs.) Fixes bug 10405; bugfix on 0.2.3.9-alpha.
1548 o Minor bugfixes (testing):
1549 - The Python parts of the test scripts now work on Python 3 as well
1550 as Python 2, so systems where '/usr/bin/python' is Python 3 will
1551 no longer have the tests break. Fixes bug 11608; bugfix
1553 - When looking for versions of python that we could run the tests
1554 with, check for "python2.7" and "python3.3"; previously we were
1555 only looking for "python", "python2", and "python3". Patch from
1556 Dana Koch. Fixes bug 11632; bugfix on 0.2.5.2-alpha.
1557 - Fix all valgrind warnings produced by the unit tests. There were
1558 over a thousand memory leak warnings previously, mostly produced
1559 by forgetting to free things in the unit test code. Fixes bug
1560 11618, bugfixes on many versions of Tor.
1562 o Minor bugfixes (tor-fw-helper):
1563 - Give a correct log message when tor-fw-helper fails to launch.
1564 (Previously, we would say something like "tor-fw-helper sent us a
1565 string we could not parse".) Fixes bug 9781; bugfix
1568 o Minor bugfixes (relay, threading):
1569 - Check return code on spawn_func() in cpuworker code, so that we
1570 don't think we've spawned a nonworking cpuworker and write junk to
1571 it forever. Fix related to bug 4345; bugfix on all released Tor
1572 versions. Found by "skruffy".
1573 - Use a pthread_attr to make sure that spawn_func() cannot return an
1574 error while at the same time launching a thread. Fix related to
1575 bug 4345; bugfix on all released Tor versions. Reported
1578 o Minor bugfixes (relay, oom prevention):
1579 - Correctly detect the total available system memory. We tried to do
1580 this in 0.2.5.4-alpha, but the code was set up to always return an
1581 error value, even on success. Fixes bug 11805; bugfix
1584 o Minor bugfixes (relay, other):
1585 - We now drop CREATE cells for already-existent circuit IDs and for
1586 zero-valued circuit IDs, regardless of other factors that might
1587 otherwise have called for DESTROY cells. Fixes bug 12191; bugfix
1589 - Avoid an illegal read from stack when initializing the TLS module
1590 using a version of OpenSSL without all of the ciphers used by the
1591 v2 link handshake. Fixes bug 12227; bugfix on 0.2.4.8-alpha. Found
1593 - When rejecting DATA cells for stream_id zero, still count them
1594 against the circuit's deliver window so that we don't fail to send
1595 a SENDME. Fixes bug 11246; bugfix on 0.2.4.10-alpha.
1597 o Minor bugfixes (logging):
1598 - Fix a misformatted log message about delayed directory fetches.
1599 Fixes bug 11654; bugfix on 0.2.5.3-alpha.
1600 - Squelch a spurious LD_BUG message "No origin circuit for
1601 successful SOCKS stream" in certain hidden service failure cases;
1605 - Include a tor.service file in contrib/dist for use with systemd.
1606 Some distributions will be able to use this file unmodified;
1607 others will need to tweak it, or write their own. Patch from Jamie
1608 Nguyen; resolves ticket 8368.
1611 - Clean up several option names in the manpage to match their real
1612 names, add the missing documentation for a couple of testing and
1613 directory authority options, remove the documentation for a
1614 V2-directory fetching option that no longer exists. Resolves
1616 - Correct the documenation so that it lists the correct directory
1617 for the stats files. (They are in a subdirectory called "stats",
1619 - In the manpage, move more authority-only options into the
1620 directory authority section so that operators of regular directory
1621 caches don't get confused.
1624 - The contrib directory has been sorted and tidied. Before, it was
1625 an unsorted dumping ground for useful and not-so-useful things.
1626 Now, it is divided based on functionality, and the items which
1627 seemed to be nonfunctional or useless have been removed. Resolves
1628 ticket 8966; based on patches from "rl1987".
1631 - Remove /tor/dbg-stability.txt URL that was meant to help debug WFU
1632 and MTBF calculations, but that nobody was using. Fixes #11742.
1633 - The TunnelDirConns and PreferTunnelledDirConns options no longer
1634 exist; tunneled directory connections have been available since
1635 0.1.2.5-alpha, and turning them off is not a good idea. This is a
1636 brute-force fix for 10849, where "TunnelDirConns 0" would break
1640 Changes in version 0.2.4.22 - 2014-05-16
1641 Tor 0.2.4.22 backports numerous high-priority fixes from the Tor 0.2.5
1642 alpha release series. These include blocking all authority signing
1643 keys that may have been affected by the OpenSSL "heartbleed" bug,
1644 choosing a far more secure set of TLS ciphersuites by default, closing
1645 a couple of memory leaks that could be used to run a target relay out
1646 of RAM, and several others.
1648 o Major features (security, backport from 0.2.5.4-alpha):
1649 - Block authority signing keys that were used on authorities
1650 vulnerable to the "heartbleed" bug in OpenSSL (CVE-2014-0160). (We
1651 don't have any evidence that these keys _were_ compromised; we're
1652 doing this to be prudent.) Resolves ticket 11464.
1654 o Major bugfixes (security, OOM):
1655 - Fix a memory leak that could occur if a microdescriptor parse
1656 fails during the tokenizing step. This bug could enable a memory
1657 exhaustion attack by directory servers. Fixes bug 11649; bugfix
1660 o Major bugfixes (TLS cipher selection, backport from 0.2.5.4-alpha):
1661 - The relay ciphersuite list is now generated automatically based on
1662 uniform criteria, and includes all OpenSSL ciphersuites with
1663 acceptable strength and forward secrecy. Previously, we had left
1664 some perfectly fine ciphersuites unsupported due to omission or
1665 typo. Resolves bugs 11513, 11492, 11498, 11499. Bugs reported by
1666 'cypherpunks'. Bugfix on 0.2.4.8-alpha.
1667 - Relays now trust themselves to have a better view than clients of
1668 which TLS ciphersuites are better than others. (Thanks to bug
1669 11513, the relay list is now well-considered, whereas the client
1670 list has been chosen mainly for anti-fingerprinting purposes.)
1671 Relays prefer: AES over 3DES; then ECDHE over DHE; then GCM over
1672 CBC; then SHA384 over SHA256 over SHA1; and last, AES256 over
1673 AES128. Resolves ticket 11528.
1674 - Clients now try to advertise the same list of ciphersuites as
1675 Firefox 28. This change enables selection of (fast) GCM
1676 ciphersuites, disables some strange old ciphers, and stops
1677 advertising the ECDH (not to be confused with ECDHE) ciphersuites.
1678 Resolves ticket 11438.
1680 o Minor bugfixes (configuration, security):
1681 - When running a hidden service, do not allow TunneledDirConns 0:
1682 trying to set that option together with a hidden service would
1683 otherwise prevent the hidden service from running, and also make
1684 it publish its descriptors directly over HTTP. Fixes bug 10849;
1685 bugfix on 0.2.1.1-alpha.
1687 o Minor bugfixes (controller, backport from 0.2.5.4-alpha):
1688 - Avoid sending a garbage value to the controller when a circuit is
1689 cannibalized. Fixes bug 11519; bugfix on 0.2.3.11-alpha.
1691 o Minor bugfixes (exit relay, backport from 0.2.5.4-alpha):
1692 - Stop leaking memory when we successfully resolve a PTR record.
1693 Fixes bug 11437; bugfix on 0.2.4.7-alpha.
1695 o Minor bugfixes (bridge client, backport from 0.2.5.4-alpha):
1696 - Avoid 60-second delays in the bootstrapping process when Tor is
1697 launching for a second time while using bridges. Fixes bug 9229;
1698 bugfix on 0.2.0.3-alpha.
1700 o Minor bugfixes (relays and bridges, backport from 0.2.5.4-alpha):
1701 - Give the correct URL in the warning message when trying to run a
1702 relay on an ancient version of Windows. Fixes bug 9393.
1704 o Minor bugfixes (compilation):
1705 - Fix a compilation error when compiling with --disable-curve25519.
1706 Fixes bug 9700; bugfix on 0.2.4.17-rc.
1709 - Downgrade the warning severity for the the "md was still
1710 referenced 1 node(s)" warning. Tor 0.2.5.4-alpha has better code
1711 for trying to diagnose this bug, and the current warning in
1712 earlier versions of tor achieves nothing useful. Addresses warning
1715 o Minor features (log verbosity, backport from 0.2.5.4-alpha):
1716 - When we run out of usable circuit IDs on a channel, log only one
1717 warning for the whole channel, and describe how many circuits
1718 there were on the channel. Fixes part of ticket 11553.
1720 o Minor features (security, backport from 0.2.5.4-alpha):
1721 - Decrease the lower limit of MaxMemInCellQueues to 256 MBytes (but
1722 leave the default at 8GBytes), to better support Raspberry Pi
1723 users. Fixes bug 9686; bugfix on 0.2.4.14-alpha.
1725 o Documentation (backport from 0.2.5.4-alpha):
1726 - Correctly document that we search for a system torrc file before
1727 looking in ~/.torrc. Fixes documentation side of 9213; bugfix on
1731 Changes in version 0.2.5.4-alpha - 2014-04-25
1732 Tor 0.2.5.4-alpha includes several security and performance
1733 improvements for clients and relays, including blacklisting authority
1734 signing keys that were used while susceptible to the OpenSSL
1735 "heartbleed" bug, fixing two expensive functions on busy relays,
1736 improved TLS ciphersuite preference lists, support for run-time
1737 hardening on compilers that support AddressSanitizer, and more work on
1738 the Linux sandbox code.
1740 There are also several usability fixes for clients (especially clients
1741 that use bridges), two new TransPort protocols supported (one on
1742 OpenBSD, one on FreeBSD), and various other bugfixes.
1744 This release marks end-of-life for Tor 0.2.2.x; those Tor versions
1745 have accumulated many known flaws; everyone should upgrade.
1747 o Major features (security):
1748 - If you don't specify MaxMemInQueues yourself, Tor now tries to
1749 pick a good value based on your total system memory. Previously,
1750 the default was always 8 GB. You can still override the default by
1751 setting MaxMemInQueues yourself. Resolves ticket 11396.
1752 - Block authority signing keys that were used on authorities
1753 vulnerable to the "heartbleed" bug in OpenSSL (CVE-2014-0160). (We
1754 don't have any evidence that these keys _were_ compromised; we're
1755 doing this to be prudent.) Resolves ticket 11464.
1757 o Major features (relay performance):
1758 - Speed up server-side lookups of rendezvous and introduction point
1759 circuits by using hashtables instead of linear searches. These
1760 functions previously accounted between 3 and 7% of CPU usage on
1761 some busy relays. Resolves ticket 9841.
1762 - Avoid wasting CPU when extending a circuit over a channel that is
1763 nearly out of circuit IDs. Previously, we would do a linear scan
1764 over possible circuit IDs before finding one or deciding that we
1765 had exhausted our possibilities. Now, we try at most 64 random
1766 circuit IDs before deciding that we probably won't succeed. Fixes
1767 a possible root cause of ticket 11553.
1769 o Major features (seccomp2 sandbox, Linux only):
1770 - The seccomp2 sandbox can now run a test network for multiple hours
1771 without crashing. The sandbox is still experimental, and more bugs
1772 will probably turn up. To try it, enable "Sandbox 1" on a Linux
1773 host. Resolves ticket 11351.
1774 - Strengthen sandbox code: the sandbox can now test the arguments
1775 for rename(), and blocks _sysctl() entirely. Resolves another part
1777 - When the sandbox blocks a system call, it now tries to log a stack
1778 trace before exiting. Resolves ticket 11465.
1780 o Major bugfixes (TLS cipher selection):
1781 - The relay ciphersuite list is now generated automatically based on
1782 uniform criteria, and includes all OpenSSL ciphersuites with
1783 acceptable strength and forward secrecy. Previously, we had left
1784 some perfectly fine ciphersuites unsupported due to omission or
1785 typo. Resolves bugs 11513, 11492, 11498, 11499. Bugs reported by
1786 'cypherpunks'. Bugfix on 0.2.4.8-alpha.
1787 - Relays now trust themselves to have a better view than clients of
1788 which TLS ciphersuites are better than others. (Thanks to bug
1789 11513, the relay list is now well-considered, whereas the client
1790 list has been chosen mainly for anti-fingerprinting purposes.)
1791 Relays prefer: AES over 3DES; then ECDHE over DHE; then GCM over
1792 CBC; then SHA384 over SHA256 over SHA1; and last, AES256 over
1793 AES128. Resolves ticket 11528.
1794 - Clients now try to advertise the same list of ciphersuites as
1795 Firefox 28. This change enables selection of (fast) GCM
1796 ciphersuites, disables some strange old ciphers, and stops
1797 advertising the ECDH (not to be confused with ECDHE) ciphersuites.
1798 Resolves ticket 11438.
1800 o Major bugfixes (bridge client):
1801 - Avoid 60-second delays in the bootstrapping process when Tor is
1802 launching for a second time while using bridges. Fixes bug 9229;
1803 bugfix on 0.2.0.3-alpha.
1805 o Minor features (transparent proxy, *BSD):
1806 - Support FreeBSD's ipfw firewall interface for TransPort ports on
1807 FreeBSD. To enable it, set "TransProxyType ipfw". Resolves ticket
1808 10267; patch from "yurivict".
1809 - Support OpenBSD's divert-to rules with the pf firewall for
1810 transparent proxy ports. To enable it, set "TransProxyType
1811 pf-divert". This allows Tor to run a TransPort transparent proxy
1812 port on OpenBSD 4.4 or later without root privileges. See the
1813 pf.conf(5) manual page for information on configuring pf to use
1814 divert-to rules. Closes ticket 10896; patch from Dana Koch.
1816 o Minor features (security):
1817 - New --enable-expensive-hardening option to enable security
1818 hardening options that consume nontrivial amounts of CPU and
1819 memory. Right now, this includes AddressSanitizer and UbSan, which
1820 are supported in newer versions of GCC and Clang. Closes ticket
1823 o Minor features (log verbosity):
1824 - Demote the message that we give when a flushing connection times
1825 out for too long from NOTICE to INFO. It was usually meaningless.
1826 Resolves ticket 5286.
1827 - Don't log so many notice-level bootstrapping messages at startup
1828 about downloading descriptors. Previously, we'd log a notice
1829 whenever we learned about more routers. Now, we only log a notice
1830 at every 5% of progress. Fixes bug 9963.
1831 - Warn less verbosely when receiving a malformed
1832 ESTABLISH_RENDEZVOUS cell. Fixes ticket 11279.
1833 - When we run out of usable circuit IDs on a channel, log only one
1834 warning for the whole channel, and describe how many circuits
1835 there were on the channel. Fixes part of ticket 11553.
1837 o Minor features (relay):
1838 - If a circuit timed out for at least 3 minutes, check if we have a
1839 new external IP address, and publish a new descriptor with the new
1840 IP address if it changed. Resolves ticket 2454.
1842 o Minor features (controller):
1843 - Make the entire exit policy available from the control port via
1844 GETINFO exit-policy/*. Implements enhancement 7952. Patch from
1846 - Because of the fix for ticket 11396, the real limit for memory
1847 usage may no longer match the configured MaxMemInQueues value. The
1848 real limit is now exposed via GETINFO limits/max-mem-in-queues.
1850 o Minor features (bridge client):
1851 - Report a more useful failure message when we can't connect to a
1852 bridge because we don't have the right pluggable transport
1853 configured. Resolves ticket 9665. Patch from Fábio J. Bertinatto.
1855 o Minor features (diagnostic):
1856 - Add more log messages to diagnose bug 7164, which causes
1857 intermittent "microdesc_free() called but md was still referenced"
1858 warnings. We now include more information, to figure out why we
1859 might be cleaning a microdescriptor for being too old if it's
1860 still referenced by a live node_t object.
1862 o Minor bugfixes (client, DNSPort):
1863 - When using DNSPort, try to respond to AAAA requests with AAAA
1864 answers. Previously, we hadn't looked at the request type when
1865 deciding which answer type to prefer. Fixes bug 10468; bugfix on
1867 - When receiving a DNS query for an unsupported record type, reply
1868 with no answer rather than with a NOTIMPL error. This behavior
1869 isn't correct either, but it will break fewer client programs, we
1870 hope. Fixes bug 10268; bugfix on 0.2.0.1-alpha. Original patch
1873 o Minor bugfixes (exit relay):
1874 - Stop leaking memory when we successfully resolve a PTR record.
1875 Fixes bug 11437; bugfix on 0.2.4.7-alpha.
1877 o Minor bugfixes (bridge client):
1878 - Stop accepting bridge lines containing hostnames. Doing so would
1879 cause clients to perform DNS requests on the hostnames, which was
1880 not sensible behavior. Fixes bug 10801; bugfix on 0.2.0.1-alpha.
1881 - Avoid a 60-second delay in the bootstrapping process when a Tor
1882 client with pluggable transports re-reads its configuration at
1883 just the wrong time. Re-fixes bug 11156; bugfix on 0.2.5.3-alpha.
1885 o Minor bugfixes (client, logging during bootstrap):
1886 - Warn only once if we start logging in an unsafe way. Previously,
1887 we complain as many times as we had problems. Fixes bug 9870;
1888 bugfix on 0.2.5.1-alpha.
1889 - Only report the first fatal bootstrap error on a given OR
1890 connection. This stops us from telling the controller bogus error
1891 messages like "DONE". Fixes bug 10431; bugfix on 0.2.1.1-alpha.
1892 - Be more helpful when trying to run sandboxed on Linux without
1893 libseccomp. Instead of saying "Sandbox is not implemented on this
1894 platform", we now explain that we need to be built with
1895 libseccomp. Fixes bug 11543; bugfix on 0.2.5.1-alpha.
1896 - Avoid generating spurious warnings when starting with
1897 DisableNetwork enabled. Fixes bug 11200 and bug 10405; bugfix on
1900 o Minor bugfixes (closing OR connections):
1901 - If write_to_buf() in connection_write_to_buf_impl_() ever fails,
1902 check if it's an or_connection_t and correctly call
1903 connection_or_close_for_error() rather than
1904 connection_mark_for_close() directly. Fixes bug 11304; bugfix on
1906 - When closing all connections on setting DisableNetwork to 1, use
1907 connection_or_close_normally() rather than closing OR connections
1908 out from under the channel layer. Fixes bug 11306; bugfix on
1911 o Minor bugfixes (controller):
1912 - Avoid sending a garbage value to the controller when a circuit is
1913 cannibalized. Fixes bug 11519; bugfix on 0.2.3.11-alpha.
1915 o Minor bugfixes (tor-fw-helper):
1916 - Allow tor-fw-helper to build again by adding src/ext to its
1917 CPPFLAGS. Fixes bug 11296; bugfix on 0.2.5.3-alpha.
1919 o Minor bugfixes (bridges):
1920 - Avoid potential crashes or bad behavior when launching a
1921 server-side managed proxy with ORPort or ExtORPort temporarily
1922 disabled. Fixes bug 9650; bugfix on 0.2.3.16-alpha.
1924 o Minor bugfixes (platform-specific):
1925 - Fix compilation on Solaris, which does not have <endian.h>. Fixes
1926 bug 11426; bugfix on 0.2.5.3-alpha.
1927 - When dumping a malformed directory object to disk, save it in
1928 binary mode on Windows, not text mode. Fixes bug 11342; bugfix on
1930 - Don't report failures from make_socket_reuseable() on incoming
1931 sockets on OSX: this can happen when incoming connections close
1932 early. Fixes bug 10081.
1934 o Minor bugfixes (trivial memory leaks):
1935 - Fix a small memory leak when signing a directory object. Fixes bug
1936 11275; bugfix on 0.2.4.13-alpha.
1937 - Free placeholder entries in our circuit table at exit; fixes a
1938 harmless memory leak. Fixes bug 11278; bugfix on 0.2.5.1-alpha.
1939 - Don't re-initialize a second set of OpenSSL mutexes when starting
1940 up. Previously, we'd make one set of mutexes, and then immediately
1941 replace them with another. Fixes bug 11726; bugfix on
1943 - Resolve some memory leaks found by coverity in the unit tests, on
1944 exit in tor-gencert, and on a failure to compute digests for our
1945 own keys when generating a v3 networkstatus vote. These leaks
1946 should never have affected anyone in practice.
1948 o Minor bugfixes (hidden service):
1949 - Only retry attempts to connect to a chosen rendezvous point 8
1950 times, not 30. Fixes bug 4241; bugfix on 0.1.0.1-rc.
1952 o Minor bugfixes (misc code correctness):
1953 - Fix various instances of undefined behavior in channeltls.c,
1954 tor_memmem(), and eventdns.c that would cause us to construct
1955 pointers to memory outside an allocated object. (These invalid
1956 pointers were not accessed, but C does not even allow them to
1957 exist.) Fixes bug 10363; bugfixes on 0.1.1.1-alpha, 0.1.2.1-alpha,
1958 0.2.0.10-alpha, and 0.2.3.6-alpha. Reported by "bobnomnom".
1959 - Use the AddressSanitizer and Ubsan sanitizers (in clang-3.4) to
1960 fix some miscellaneous errors in our tests and codebase. Fixes bug
1961 11232. Bugfixes on versions back as far as 0.2.1.11-alpha.
1962 - Always check return values for unlink, munmap, UnmapViewOfFile;
1963 check strftime return values more often. In some cases all we can
1964 do is report a warning, but this may help prevent deeper bugs from
1965 going unnoticed. Closes ticket 8787; bugfixes on many, many tor
1967 - Fix numerous warnings from the clang "scan-build" static analyzer.
1968 Some of these are programming style issues; some of them are false
1969 positives that indicated awkward code; some are undefined behavior
1970 cases related to constructing (but not using) invalid pointers;
1971 some are assumptions about API behavior; some are (harmlessly)
1972 logging sizeof(ptr) bytes from a token when sizeof(*ptr) would be
1973 correct; and one or two are genuine bugs that weren't reachable
1974 from the rest of the program. Fixes bug 8793; bugfixes on many,
1978 - Build the torify.1 manpage again. Previously, we were only trying
1979 to build it when also building tor-fw-helper. That's why we didn't
1980 notice that we'd broken the ability to build it. Fixes bug 11321;
1981 bugfix on 0.2.5.1-alpha.
1982 - Fix the layout of the SOCKSPort flags in the manpage. Fixes bug
1983 11061; bugfix on 0.2.4.7-alpha.
1984 - Correctly document that we search for a system torrc file before
1985 looking in ~/.torrc. Fixes documentation side of 9213; bugfix on
1987 - Resolve warnings from Doxygen.
1989 o Code simplifications and refactoring:
1990 - Remove is_internal_IP() function. Resolves ticket 4645.
1991 - Remove unused function circuit_dump_by_chan from circuitlist.c.
1992 Closes issue 9107; patch from "marek".
1993 - Change our use of the ENUM_BF macro to avoid declarations that
1996 o Deprecated versions:
1997 - Tor 0.2.2.x has reached end-of-life; it has received no patches or
1998 attention for some while. Directory authorities no longer accept
1999 descriptors from relays running any version of Tor prior to Tor
2000 0.2.3.16-alpha. Resolves ticket 11149.
2003 - New macros in test.h to simplify writing mock-functions for unit
2004 tests. Part of ticket 11507. Patch from Dana Koch.
2005 - Complete tests for the status.c module. Resolves ticket 11507.
2006 Patch from Dana Koch.
2009 - Remove all code for the long unused v1 directory protocol.
2010 Resolves ticket 11070.
2013 Changes in version 0.2.5.3-alpha - 2014-03-22
2014 Tor 0.2.5.3-alpha includes all the fixes from 0.2.4.21. It contains
2015 two new anti-DoS features for Tor relays, resolves a bug that kept
2016 SOCKS5 support for IPv6 from working, fixes several annoying usability
2017 issues for bridge users, and removes more old code for unused
2020 The Tor 0.2.5.x release series is now in patch-freeze: no feature
2021 patches not already written will be considered for inclusion in 0.2.5.x.
2023 o Major features (relay security, DoS-resistance):
2024 - When deciding whether we have run out of memory and we need to
2025 close circuits, also consider memory allocated in buffers for
2026 streams attached to each circuit.
2028 This change, which extends an anti-DoS feature introduced in
2029 0.2.4.13-alpha and improved in 0.2.4.14-alpha, lets Tor exit relays
2030 better resist more memory-based DoS attacks than before. Since the
2031 MaxMemInCellQueues option now applies to all queues, it is renamed
2032 to MaxMemInQueues. This feature fixes bug 10169.
2033 - Avoid hash-flooding denial-of-service attacks by using the secure
2034 SipHash-2-4 hash function for our hashtables. Without this
2035 feature, an attacker could degrade performance of a targeted
2036 client or server by flooding their data structures with a large
2037 number of entries to be stored at the same hash table position,
2038 thereby slowing down the Tor instance. With this feature, hash
2039 table positions are derived from a randomized cryptographic key,
2040 and an attacker cannot predict which entries will collide. Closes
2042 - Decrease the lower limit of MaxMemInQueues to 256 MBytes (but leave
2043 the default at 8GBytes), to better support Raspberry Pi users. Fixes
2044 bug 9686; bugfix on 0.2.4.14-alpha.
2046 o Minor features (bridges, pluggable transports):
2047 - Bridges now write the SHA1 digest of their identity key
2048 fingerprint (that is, a hash of a hash of their public key) to
2049 notice-level logs, and to a new hashed-fingerprint file. This
2050 information will help bridge operators look up their bridge in
2051 Globe and similar tools. Resolves ticket 10884.
2052 - Improve the message that Tor displays when running as a bridge
2053 using pluggable transports without an Extended ORPort listener.
2054 Also, log the message in the log file too. Resolves ticket 11043.
2056 o Minor features (other):
2057 - Add a new option, PredictedPortsRelevanceTime, to control how long
2058 after having received a request to connect to a given port Tor
2059 will try to keep circuits ready in anticipation of future requests
2060 for that port. Patch from "unixninja92"; implements ticket 9176.
2061 - Generate a warning if any ports are listed in the SocksPolicy,
2062 DirPolicy, AuthDirReject, AuthDirInvalid, AuthDirBadDir, or
2063 AuthDirBadExit options. (These options only support address
2064 ranges.) Fixes part of ticket 11108.
2065 - Update geoip and geoip6 to the February 7 2014 Maxmind GeoLite2
2068 o Minor bugfixes (new since 0.2.5.2-alpha, also in 0.2.4.21):
2069 - Build without warnings under clang 3.4. (We have some macros that
2070 define static functions only some of which will get used later in
2071 the module. Starting with clang 3.4, these give a warning unless the
2072 unused attribute is set on them.) Resolves ticket 10904.
2073 - Fix build warnings about missing "a2x" comment when building the
2074 manpages from scratch on OpenBSD; OpenBSD calls it "a2x.py".
2075 Fixes bug 10929; bugfix on 0.2.2.9-alpha. Patch from Dana Koch.
2077 o Minor bugfixes (client):
2078 - Improve the log message when we can't connect to a hidden service
2079 because all of the hidden service directory nodes hosting its
2080 descriptor are excluded. Improves on our fix for bug 10722, which
2081 was a bugfix on 0.2.0.10-alpha.
2082 - Raise a control port warning when we fail to connect to all of
2083 our bridges. Previously, we didn't inform the controller, and
2084 the bootstrap process would stall. Fixes bug 11069; bugfix on
2086 - Exit immediately when a process-owning controller exits.
2087 Previously, tor relays would wait for a little while after their
2088 controller exited, as if they had gotten an INT signal -- but this
2089 was problematic, since there was no feedback for the user. To do a
2090 clean shutdown, controllers should send an INT signal and give Tor
2091 a chance to clean up. Fixes bug 10449; bugfix on 0.2.2.28-beta.
2092 - Stop attempting to connect to bridges before our pluggable
2093 transports are configured (harmless but resulted in some erroneous
2094 log messages). Fixes bug 11156; bugfix on 0.2.3.2-alpha.
2095 - Fix connections to IPv6 addresses over SOCKS5. Previously, we were
2096 generating incorrect SOCKS5 responses, and confusing client
2097 applications. Fixes bug 10987; bugfix on 0.2.4.7-alpha.
2099 o Minor bugfixes (relays and bridges):
2100 - Avoid crashing on a malformed resolv.conf file when running a
2101 relay using Libevent 1. Fixes bug 8788; bugfix on 0.1.1.23.
2102 - Non-exit relays no longer launch mock DNS requests to check for
2103 DNS hijacking. This has been unnecessary since 0.2.1.7-alpha, when
2104 non-exit relays stopped servicing DNS requests. Fixes bug 965;
2105 bugfix on 0.2.1.7-alpha. Patch from Matt Pagan.
2106 - Bridges now report complete directory request statistics. Related
2107 to bug 5824; bugfix on 0.2.2.1-alpha.
2108 - Bridges now never collect statistics that were designed for
2109 relays. Fixes bug 5824; bugfix on 0.2.3.8-alpha.
2110 - Stop giving annoying warning messages when we decide not to launch
2111 a pluggable transport proxy that we don't need (because there are
2112 no bridges configured to use it). Resolves ticket 5018; bugfix
2114 - Give the correct URL in the warning message when trying to run a
2115 relay on an ancient version of Windows. Fixes bug 9393.
2117 o Minor bugfixes (backtrace support):
2118 - Support automatic backtraces on more platforms by using the
2119 "-fasynchronous-unwind-tables" compiler option. This option is
2120 needed for platforms like 32-bit Intel where "-fomit-frame-pointer"
2121 is on by default and table generation is not. This doesn't yet
2122 add Windows support; only Linux, OSX, and some BSDs are affected.
2123 Reported by 'cypherpunks'; fixes bug 11047; bugfix on 0.2.5.2-alpha.
2124 - Avoid strange behavior if two threads hit failed assertions at the
2125 same time and both try to log backtraces at once. (Previously, if
2126 this had happened, both threads would have stored their intermediate
2127 results in the same buffer, and generated junk outputs.) Reported by
2128 "cypherpunks". Fixes bug 11048; bugfix on 0.2.5.2-alpha.
2129 - Fix a compiler warning in format_number_sigsafe(). Bugfix on
2130 0.2.5.2-alpha; patch from Nick Hopper.
2132 o Minor bugfixes (unit tests):
2133 - Fix a small bug in the unit tests that might have made the tests
2134 call 'chmod' with an uninitialized bitmask. Fixes bug 10928;
2135 bugfix on 0.2.5.1-alpha. Patch from Dana Koch.
2138 - Remove all remaining code related to version-0 hidden service
2139 descriptors: they have not been in use since 0.2.2.1-alpha. Fixes
2140 the rest of bug 10841.
2143 - Document in the manpage that "KBytes" may also be written as
2144 "kilobytes" or "KB", that "Kbits" may also be written as
2145 "kilobits", and so forth. Closes ticket 9222.
2146 - Document that the ClientOnly config option overrides ORPort.
2147 Our old explanation made ClientOnly sound as though it did
2148 nothing at all. Resolves bug 9059.
2149 - Explain that SocksPolicy, DirPolicy, and similar options don't
2150 take port arguments. Fixes the other part of ticket 11108.
2151 - Fix a comment about the rend_server_descriptor_t.protocols field
2152 to more accurately describe its range. Also, make that field
2153 unsigned, to more accurately reflect its usage. Fixes bug 9099;
2154 bugfix on 0.2.1.5-alpha.
2155 - Fix the manpage's description of HiddenServiceAuthorizeClient:
2156 the maximum client name length is 16, not 19. Fixes bug 11118;
2157 bugfix on 0.2.1.6-alpha.
2159 o Code simplifications and refactoring:
2160 - Get rid of router->address, since in all cases it was just the
2161 string representation of router->addr. Resolves ticket 5528.
2163 o Test infrastructure:
2164 - Update to the latest version of tinytest.
2165 - Improve the tinytest implementation of string operation tests so
2166 that comparisons with NULL strings no longer crash the tests; they
2167 now just fail, normally. Fixes bug 9004; bugfix on 0.2.2.4-alpha.
2170 Changes in version 0.2.4.21 - 2014-02-28
2171 Tor 0.2.4.21 further improves security against potential adversaries who
2172 find breaking 1024-bit crypto doable, and backports several stability
2173 and robustness patches from the 0.2.5 branch.
2175 o Major features (client security):
2176 - When we choose a path for a 3-hop circuit, make sure it contains
2177 at least one relay that supports the NTor circuit extension
2178 handshake. Otherwise, there is a chance that we're building
2179 a circuit that's worth attacking by an adversary who finds
2180 breaking 1024-bit crypto doable, and that chance changes the game
2181 theory. Implements ticket 9777.
2184 - Do not treat streams that fail with reason
2185 END_STREAM_REASON_INTERNAL as indicating a definite circuit failure,
2186 since it could also indicate an ENETUNREACH connection error. Fixes
2187 part of bug 10777; bugfix on 0.2.4.8-alpha.
2189 o Code simplification and refactoring:
2190 - Remove data structures which were introduced to implement the
2191 CellStatistics option: they are now redundant with the new timestamp
2192 field in the regular packed_cell_t data structure, which we did
2193 in 0.2.4.18-rc in order to resolve bug 9093. Resolves ticket 10870.
2196 - Always clear OpenSSL bignums before freeing them -- even bignums
2197 that don't contain secrets. Resolves ticket 10793. Patch by
2199 - Build without warnings under clang 3.4. (We have some macros that
2200 define static functions only some of which will get used later in
2201 the module. Starting with clang 3.4, these give a warning unless the
2202 unused attribute is set on them.) Resolves ticket 10904.
2203 - Update geoip and geoip6 files to the February 7 2014 Maxmind
2204 GeoLite2 Country database.
2207 - Set the listen() backlog limit to the largest actually supported
2208 on the system, not to the value in a header file. Fixes bug 9716;
2209 bugfix on every released Tor.
2210 - Treat ENETUNREACH, EACCES, and EPERM connection failures at an
2211 exit node as a NOROUTE error, not an INTERNAL error, since they
2212 can apparently happen when trying to connect to the wrong sort
2213 of netblocks. Fixes part of bug 10777; bugfix on 0.1.0.1-rc.
2214 - Fix build warnings about missing "a2x" comment when building the
2215 manpages from scratch on OpenBSD; OpenBSD calls it "a2x.py".
2216 Fixes bug 10929; bugfix on 0.2.2.9-alpha. Patch from Dana Koch.
2217 - Avoid a segfault on SIGUSR1, where we had freed a connection but did
2218 not entirely remove it from the connection lists. Fixes bug 9602;
2219 bugfix on 0.2.4.4-alpha.
2220 - Fix a segmentation fault in our benchmark code when running with
2221 Fedora's OpenSSL package, or any other OpenSSL that provides
2222 ECDH but not P224. Fixes bug 10835; bugfix on 0.2.4.8-alpha.
2223 - Turn "circuit handshake stats since last time" log messages into a
2224 heartbeat message. Fixes bug 10485; bugfix on 0.2.4.17-rc.
2226 o Documentation fixes:
2227 - Document that all but one DirPort entry must have the NoAdvertise
2228 flag set. Fixes bug 10470; bugfix on 0.2.3.3-alpha / 0.2.3.16-alpha.
2231 Changes in version 0.2.5.2-alpha - 2014-02-13
2232 Tor 0.2.5.2-alpha includes all the fixes from 0.2.4.18-rc and 0.2.4.20,
2233 like the "poor random number generation" fix and the "building too many
2234 circuits" fix. It also further improves security against potential
2235 adversaries who find breaking 1024-bit crypto doable, and launches
2236 pluggable transports on demand (which gets us closer to integrating
2237 pluggable transport support by default -- not to be confused with Tor
2238 bundles enabling pluggable transports and bridges by default).
2240 o Major features (client security):
2241 - When we choose a path for a 3-hop circuit, make sure it contains
2242 at least one relay that supports the NTor circuit extension
2243 handshake. Otherwise, there is a chance that we're building
2244 a circuit that's worth attacking by an adversary who finds
2245 breaking 1024-bit crypto doable, and that chance changes the game
2246 theory. Implements ticket 9777.
2247 - Clients now look at the "usecreatefast" consensus parameter to
2248 decide whether to use CREATE_FAST or CREATE cells for the first hop
2249 of their circuit. This approach can improve security on connections
2250 where Tor's circuit handshake is stronger than the available TLS
2251 connection security levels, but the tradeoff is more computational
2252 load on guard relays. Implements proposal 221. Resolves ticket 9386.
2254 o Major features (bridges):
2255 - Don't launch pluggable transport proxies if we don't have any
2256 bridges configured that would use them. Now we can list many
2257 pluggable transports, and Tor will dynamically start one when it
2258 hears a bridge address that needs it. Resolves ticket 5018.
2259 - The bridge directory authority now assigns status flags (Stable,
2260 Guard, etc) to bridges based on thresholds calculated over all
2261 Running bridges. Now bridgedb can finally make use of its features
2262 to e.g. include at least one Stable bridge in its answers. Fixes
2265 o Major features (other):
2266 - Extend ORCONN controller event to include an "ID" parameter,
2267 and add four new controller event types CONN_BW, CIRC_BW,
2268 CELL_STATS, and TB_EMPTY that show connection and circuit usage.
2269 The new events are emitted in private Tor networks only, with the
2270 goal of being able to better track performance and load during
2271 full-network simulations. Implements proposal 218 and ticket 7359.
2272 - On some platforms (currently: recent OSX versions, glibc-based
2273 platforms that support the ELF format, and a few other
2274 Unix-like operating systems), Tor can now dump stack traces
2275 when a crash occurs or an assertion fails. By default, traces
2276 are dumped to stderr (if possible) and to any logs that are
2277 reporting errors. Implements ticket 9299.
2280 - Avoid a segfault on SIGUSR1, where we had freed a connection but did
2281 not entirely remove it from the connection lists. Fixes bug 9602;
2282 bugfix on 0.2.4.4-alpha.
2283 - Do not treat streams that fail with reason
2284 END_STREAM_REASON_INTERNAL as indicating a definite circuit failure,
2285 since it could also indicate an ENETUNREACH connection error. Fixes
2286 part of bug 10777; bugfix on 0.2.4.8-alpha.
2288 o Major bugfixes (new since 0.2.5.1-alpha, also in 0.2.4.20):
2289 - Do not allow OpenSSL engines to replace the PRNG, even when
2290 HardwareAccel is set. The only default builtin PRNG engine uses
2291 the Intel RDRAND instruction to replace the entire PRNG, and
2292 ignores all attempts to seed it with more entropy. That's
2293 cryptographically stupid: the right response to a new alleged
2294 entropy source is never to discard all previously used entropy
2295 sources. Fixes bug 10402; works around behavior introduced in
2296 OpenSSL 1.0.0. Diagnosis and investigation thanks to "coderman"
2298 - Fix assertion failure when AutomapHostsOnResolve yields an IPv6
2299 address. Fixes bug 10465; bugfix on 0.2.4.7-alpha.
2300 - Avoid launching spurious extra circuits when a stream is pending.
2301 This fixes a bug where any circuit that _wasn't_ unusable for new
2302 streams would be treated as if it were, causing extra circuits to
2303 be launched. Fixes bug 10456; bugfix on 0.2.4.12-alpha.
2305 o Major bugfixes (new since 0.2.5.1-alpha, also in 0.2.4.18-rc):
2306 - No longer stop reading or writing on cpuworker connections when
2307 our rate limiting buckets go empty. Now we should handle circuit
2308 handshake requests more promptly. Resolves bug 9731.
2309 - Stop trying to bootstrap all our directory information from
2310 only our first guard. Discovered while fixing bug 9946; bugfix
2313 o Minor features (bridges, pluggable transports):
2314 - Add threshold cutoffs to the networkstatus document created by
2315 the Bridge Authority. Fixes bug 1117.
2316 - On Windows, spawn background processes using the CREATE_NO_WINDOW
2317 flag. Now Tor Browser Bundle 3.5 with pluggable transports enabled
2318 doesn't pop up a blank console window. (In Tor Browser Bundle 2.x,
2319 Vidalia set this option for us.) Implements ticket 10297.
2321 o Minor features (security):
2322 - Always clear OpenSSL bignums before freeing them -- even bignums
2323 that don't contain secrets. Resolves ticket 10793. Patch by
2326 o Minor features (config options and command line):
2327 - Add an --allow-missing-torrc commandline option that tells Tor to
2328 run even if the configuration file specified by -f is not available.
2329 Implements ticket 10060.
2330 - Add support for the TPROXY transparent proxying facility on Linux.
2331 See documentation for the new TransProxyType option for more
2332 details. Implementation by "thomo". Closes ticket 10582.
2334 o Minor features (controller):
2335 - Add a new "HS_DESC" controller event that reports activities
2336 related to hidden service descriptors. Resolves ticket 8510.
2337 - New "DROPGUARDS" controller command to forget all current entry
2338 guards. Not recommended for ordinary use, since replacing guards
2339 too frequently makes several attacks easier. Resolves ticket 9934;
2342 o Minor features (build):
2343 - Assume that a user using ./configure --host wants to cross-compile,
2344 and give an error if we cannot find a properly named
2345 tool-chain. Add a --disable-tool-name-check option to proceed
2346 nevertheless. Addresses ticket 9869. Patch by Benedikt Gollatz.
2347 - If we run ./configure and the compiler recognizes -fstack-protector
2348 but the linker rejects it, warn the user about a potentially missing
2349 libssp package. Addresses ticket 9948. Patch from Benedikt Gollatz.
2351 o Minor features (testing):
2352 - If Python is installed, "make check" now runs extra tests beyond
2353 the unit test scripts.
2354 - When bootstrapping a test network, sometimes very few relays get
2355 the Guard flag. Now a new option "TestingDirAuthVoteGuard" can
2356 specify a set of relays which should be voted Guard regardless of
2357 their uptime or bandwidth. Addresses ticket 9206.
2359 o Minor features (log messages):
2360 - When ServerTransportPlugin is set on a bridge, Tor can write more
2361 useful statistics about bridge use in its extrainfo descriptors,
2362 but only if the Extended ORPort ("ExtORPort") is set too. Add a
2363 log message to inform the user in this case. Resolves ticket 9651.
2364 - When receiving a new controller connection, log the origin address.
2365 Resolves ticket 9698; patch from "sigpipe".
2366 - When logging OpenSSL engine status at startup, log the status of
2367 more engines. Fixes ticket 10043; patch from Joshua Datko.
2368 - Turn "circuit handshake stats since last time" log messages into a
2369 heartbeat message. Fixes bug 10485; bugfix on 0.2.4.17-rc.
2371 o Minor features (new since 0.2.5.1-alpha, also in 0.2.4.18-rc):
2372 - Improve the circuit queue out-of-memory handler. Previously, when
2373 we ran low on memory, we'd close whichever circuits had the most
2374 queued cells. Now, we close those that have the *oldest* queued
2375 cells, on the theory that those are most responsible for us
2376 running low on memory. Based on analysis from a forthcoming paper
2377 by Jansen, Tschorsch, Johnson, and Scheuermann. Fixes bug 9093.
2378 - Generate bootstrapping status update events correctly when fetching
2379 microdescriptors. Fixes bug 9927.
2380 - Update to the October 2 2013 Maxmind GeoLite Country database.
2382 o Minor bugfixes (clients):
2383 - When closing a channel that has already been open, do not close
2384 pending circuits that were waiting to connect to the same relay.
2385 Fixes bug 9880; bugfix on 0.2.5.1-alpha. Thanks to skruffy for
2388 o Minor bugfixes (relays):
2389 - Treat ENETUNREACH, EACCES, and EPERM connection failures at an
2390 exit node as a NOROUTE error, not an INTERNAL error, since they
2391 can apparently happen when trying to connect to the wrong sort
2392 of netblocks. Fixes part of bug 10777; bugfix on 0.1.0.1-rc.
2394 o Minor bugfixes (bridges):
2395 - Fix a bug where the first connection works to a bridge that uses a
2396 pluggable transport with client-side parameters, but we don't send
2397 the client-side parameters on subsequent connections. (We don't
2398 use any pluggable transports with client-side parameters yet,
2399 but ScrambleSuit will soon become the first one.) Fixes bug 9162;
2400 bugfix on 0.2.0.3-alpha. Based on a patch from "rl1987".
2402 o Minor bugfixes (node selection):
2403 - If ExcludeNodes is set, consider non-excluded hidden service
2404 directory servers before excluded ones. Do not consider excluded
2405 hidden service directory servers at all if StrictNodes is
2406 set. (Previously, we would sometimes decide to connect to those
2407 servers, and then realize before we initiated a connection that
2408 we had excluded them.) Fixes bug 10722; bugfix on 0.2.0.10-alpha.
2410 - If we set the ExitNodes option but it doesn't include any nodes
2411 that have the Exit flag, we would choose not to bootstrap. Now we
2412 bootstrap so long as ExitNodes includes nodes which can exit to
2413 some port. Fixes bug 10543; bugfix on 0.2.4.10-alpha.
2415 o Minor bugfixes (controller and command-line):
2416 - If changing a config option via "setconf" fails in a recoverable
2417 way, we used to nonetheless write our new control ports to the
2418 file described by the "ControlPortWriteToFile" option. Now we only
2419 write out that file if we successfully switch to the new config
2420 option. Fixes bug 5605; bugfix on 0.2.2.26-beta. Patch from "Ryman".
2421 - When a command-line option such as --version or --help that
2422 ordinarily implies --hush appears on the command line along with
2423 --quiet, then actually obey --quiet. Previously, we obeyed --quiet
2424 only if it appeared later on the command line. Fixes bug 9578;
2425 bugfix on 0.2.5.1-alpha.
2427 o Minor bugfixes (code correctness):
2428 - Previously we used two temporary files when writing descriptors to
2429 disk; now we only use one. Fixes bug 1376.
2430 - Remove an erroneous (but impossible and thus harmless) pointer
2431 comparison that would have allowed compilers to skip a bounds
2432 check in channeltls.c. Fixes bugs 10313 and 9980; bugfix on
2433 0.2.0.10-alpha. Noticed by Jared L Wong and David Fifield.
2434 - Fix an always-true assertion in pluggable transports code so it
2435 actually checks what it was trying to check. Fixes bug 10046;
2436 bugfix on 0.2.3.9-alpha. Found by "dcb".
2438 o Minor bugfixes (protocol correctness):
2439 - When receiving a VERSIONS cell with an odd number of bytes, close
2440 the connection immediately since the cell is malformed. Fixes bug
2441 10365; bugfix on 0.2.0.10-alpha. Spotted by "bobnomnom"; fix by
2444 o Minor bugfixes (build):
2445 - Restore the ability to compile Tor with V2_HANDSHAKE_SERVER
2446 turned off (that is, without support for v2 link handshakes). Fixes
2447 bug 4677; bugfix on 0.2.3.2-alpha. Patch from "piet".
2448 - Fix compilation warnings and startup issues when running with
2449 "Sandbox 1" and libseccomp-2.1.0. Fixes bug 10563; bugfix on
2451 - Fix compilation on Solaris 9, which didn't like us having an
2452 identifier named "sun". Fixes bug 10565; bugfix in 0.2.5.1-alpha.
2454 o Minor bugfixes (testing):
2455 - Fix a segmentation fault in our benchmark code when running with
2456 Fedora's OpenSSL package, or any other OpenSSL that provides
2457 ECDH but not P224. Fixes bug 10835; bugfix on 0.2.4.8-alpha.
2459 o Minor bugfixes (log messages):
2460 - Fix a bug where clients using bridges would report themselves
2461 as 50% bootstrapped even without a live consensus document.
2462 Fixes bug 9922; bugfix on 0.2.1.1-alpha.
2463 - Suppress a warning where, if there's only one directory authority
2464 in the network, we would complain that votes and signatures cannot
2465 be uploaded to other directory authorities. Fixes bug 10842;
2466 bugfix on 0.2.2.26-beta.
2467 - Report bootstrapping progress correctly when we're downloading
2468 microdescriptors. We had updated our "do we have enough microdescs
2469 to begin building circuits?" logic most recently in 0.2.4.10-alpha
2470 (see bug 5956), but we left the bootstrap status event logic at
2471 "how far through getting 1/4 of them are we?" Fixes bug 9958;
2472 bugfix on 0.2.2.36, which is where they diverged (see bug 5343).
2474 o Minor bugfixes (new since 0.2.5.1-alpha, also in 0.2.4.20):
2475 - Avoid a crash bug when starting with a corrupted microdescriptor
2476 cache file. Fixes bug 10406; bugfix on 0.2.2.6-alpha.
2477 - If we fail to dump a previously cached microdescriptor to disk, avoid
2478 freeing duplicate data later on. Fixes bug 10423; bugfix on
2479 0.2.4.13-alpha. Spotted by "bobnomnom".
2481 o Minor bugfixes on 0.2.4.x (new since 0.2.5.1-alpha, also in 0.2.4.18-rc):
2482 - Correctly log long IPv6 exit policies, instead of truncating them
2483 or reporting an error. Fixes bug 9596; bugfix on 0.2.4.7-alpha.
2484 - Our default TLS ecdhe groups were backwards: we meant to be using
2485 P224 for relays (for performance win) and P256 for bridges (since
2486 it is more common in the wild). Instead we had it backwards. After
2487 reconsideration, we decided that the default should be P256 on all
2488 hosts, since its security is probably better, and since P224 is
2489 reportedly used quite little in the wild. Found by "skruffy" on
2490 IRC. Fix for bug 9780; bugfix on 0.2.4.8-alpha.
2491 - Free directory authority certificate download statuses on exit
2492 rather than leaking them. Fixes bug 9644; bugfix on 0.2.4.13-alpha.
2494 o Minor bugfixes on 0.2.3.x (new since 0.2.5.1-alpha, also in 0.2.4.18-rc):
2495 - If the guard we choose first doesn't answer, we would try the
2496 second guard, but once we connected to the second guard we would
2497 abandon it and retry the first one, slowing down bootstrapping.
2498 The fix is to treat all our initially chosen guards as acceptable
2499 to use. Fixes bug 9946; bugfix on 0.1.1.11-alpha.
2500 - Fix an assertion failure that would occur when disabling the
2501 ORPort setting on a running Tor process while accounting was
2502 enabled. Fixes bug 6979; bugfix on 0.2.2.18-alpha.
2503 - When examining the list of network interfaces to find our address,
2504 do not consider non-running or disabled network interfaces. Fixes
2505 bug 9904; bugfix on 0.2.3.11-alpha. Patch from "hantwister".
2506 - Avoid an off-by-one error when checking buffer boundaries when
2507 formatting the exit status of a pluggable transport helper.
2508 This is probably not an exploitable bug, but better safe than
2509 sorry. Fixes bug 9928; bugfix on 0.2.3.18-rc. Bug found by
2512 o Removed code and features:
2513 - Clients now reject any directory authority certificates lacking
2514 a dir-key-crosscert element. These have been included since
2515 0.2.1.9-alpha, so there's no real reason for them to be optional
2516 any longer. Completes proposal 157. Resolves ticket 10162.
2517 - Remove all code that existed to support the v2 directory system,
2518 since there are no longer any v2 directory authorities. Resolves
2520 - Remove the HSAuthoritativeDir and AlternateHSAuthority torrc
2521 options, which were used for designating authorities as "Hidden
2522 service authorities". There has been no use of hidden service
2523 authorities since 0.2.2.1-alpha, when we stopped uploading or
2524 downloading v0 hidden service descriptors. Fixes bug 10881; also
2525 part of a fix for bug 10841.
2527 o Code simplification and refactoring:
2528 - Remove some old fallback code designed to keep Tor clients working
2529 in a network with only two working relays. Elsewhere in the code we
2530 have long since stopped supporting such networks, so there wasn't
2531 much point in keeping it around. Addresses ticket 9926.
2532 - Reject 0-length EXTEND2 cells more explicitly. Fixes bug 10536;
2533 bugfix on 0.2.4.8-alpha. Reported by "cypherpunks".
2534 - Remove data structures which were introduced to implement the
2535 CellStatistics option: they are now redundant with the addition
2536 of a timestamp to the regular packed_cell_t data structure, which
2537 we did in 0.2.4.18-rc in order to resolve ticket 9093. Implements
2540 o Documentation (man page) fixes:
2541 - Update manpage to describe some of the files you can expect to
2542 find in Tor's DataDirectory. Addresses ticket 9839.
2543 - Document that all but one DirPort entry must have the NoAdvertise
2544 flag set. Fixes bug 10470; bugfix on 0.2.3.3-alpha / 0.2.3.16-alpha.
2546 o Documentation fixes (new since 0.2.5.1-alpha, also in 0.2.4.18-rc):
2547 - Clarify the usage and risks of setting the ContactInfo torrc line
2548 for your relay or bridge. Resolves ticket 9854.
2549 - Add anchors to the manpage so we can link to the html version of
2550 the documentation for specific options. Resolves ticket 9866.
2551 - Replace remaining references to DirServer in man page and
2552 log entries. Resolves ticket 10124.
2555 - Make the "tor-gencert" tool used by directory authority operators
2556 create 2048-bit signing keys by default (rather than 1024-bit, since
2557 1024-bit is uncomfortably small these days). Addresses ticket 10324.
2560 Changes in version 0.2.4.20 - 2013-12-22
2561 Tor 0.2.4.20 fixes potentially poor random number generation for users
2562 who 1) use OpenSSL 1.0.0 or later, 2) set "HardwareAccel 1" in their
2563 torrc file, 3) have "Sandy Bridge" or "Ivy Bridge" Intel processors,
2564 and 4) have no state file in their DataDirectory (as would happen on
2565 first start). Users who generated relay or hidden service identity
2566 keys in such a situation should discard them and generate new ones.
2568 This release also fixes a logic error that caused Tor clients to build
2569 many more preemptive circuits than they actually need.
2572 - Do not allow OpenSSL engines to replace the PRNG, even when
2573 HardwareAccel is set. The only default builtin PRNG engine uses
2574 the Intel RDRAND instruction to replace the entire PRNG, and
2575 ignores all attempts to seed it with more entropy. That's
2576 cryptographically stupid: the right response to a new alleged
2577 entropy source is never to discard all previously used entropy
2578 sources. Fixes bug 10402; works around behavior introduced in
2579 OpenSSL 1.0.0. Diagnosis and investigation thanks to "coderman"
2581 - Fix assertion failure when AutomapHostsOnResolve yields an IPv6
2582 address. Fixes bug 10465; bugfix on 0.2.4.7-alpha.
2583 - Avoid launching spurious extra circuits when a stream is pending.
2584 This fixes a bug where any circuit that _wasn't_ unusable for new
2585 streams would be treated as if it were, causing extra circuits to
2586 be launched. Fixes bug 10456; bugfix on 0.2.4.12-alpha.
2589 - Avoid a crash bug when starting with a corrupted microdescriptor
2590 cache file. Fixes bug 10406; bugfix on 0.2.2.6-alpha.
2591 - If we fail to dump a previously cached microdescriptor to disk, avoid
2592 freeing duplicate data later on. Fixes bug 10423; bugfix on
2593 0.2.4.13-alpha. Spotted by "bobnomnom".
2596 Changes in version 0.2.4.19 - 2013-12-11
2597 The Tor 0.2.4 release series is dedicated to the memory of Aaron Swartz
2598 (1986-2013). Aaron worked on diverse projects including helping to guide
2599 Creative Commons, playing a key role in stopping SOPA/PIPA, bringing
2600 transparency to the U.S government's PACER documents, and contributing
2601 design and development for Tor and Tor2Web. Aaron was one of the latest
2602 martyrs in our collective fight for civil liberties and human rights,
2603 and his death is all the more painful because he was one of us.
2605 Tor 0.2.4.19, the first stable release in the 0.2.4 branch, features
2606 a new circuit handshake and link encryption that use ECC to provide
2607 better security and efficiency; makes relays better manage circuit
2608 creation requests; uses "directory guards" to reduce client enumeration
2609 risks; makes bridges collect and report statistics about the pluggable
2610 transports they support; cleans up and improves our geoip database;
2611 gets much closer to IPv6 support for clients, bridges, and relays; makes
2612 directory authorities use measured bandwidths rather than advertised
2613 ones when computing flags and thresholds; disables client-side DNS
2614 caching to reduce tracking risks; and fixes a big bug in bridge
2615 reachability testing. This release introduces two new design
2616 abstractions in the code: a new "channel" abstraction between circuits
2617 and or_connections to allow for implementing alternate relay-to-relay
2618 transports, and a new "circuitmux" abstraction storing the queue of
2619 circuits for a channel. The release also includes many stability,
2620 security, and privacy fixes.
2623 Changes in version 0.2.4.18-rc - 2013-11-16
2624 Tor 0.2.4.18-rc is the fourth release candidate for the Tor 0.2.4.x
2625 series. It takes a variety of fixes from the 0.2.5.x branch to improve
2626 stability, performance, and better handling of edge cases.
2629 - Re-enable TLS 1.1 and 1.2 when built with OpenSSL 1.0.1e or later.
2630 Resolves ticket 6055. (OpenSSL before 1.0.1 didn't have TLS 1.1 or
2631 1.2, and OpenSSL from 1.0.1 through 1.0.1d had bugs that prevented
2632 renegotiation from working with TLS 1.1 or 1.2, so we had disabled
2633 them to solve bug 6033.)
2636 - No longer stop reading or writing on cpuworker connections when
2637 our rate limiting buckets go empty. Now we should handle circuit
2638 handshake requests more promptly. Resolves bug 9731.
2639 - If we are unable to save a microdescriptor to the journal, do not
2640 drop it from memory and then reattempt downloading it. Fixes bug
2641 9645; bugfix on 0.2.2.6-alpha.
2642 - Stop trying to bootstrap all our directory information from
2643 only our first guard. Discovered while fixing bug 9946; bugfix
2645 - The new channel code sometimes lost track of in-progress circuits,
2646 causing long-running clients to stop building new circuits. The
2647 fix is to always call circuit_n_chan_done(chan, 0) from
2648 channel_closed(). Fixes bug 9776; bugfix on 0.2.4.17-rc.
2650 o Minor bugfixes (on 0.2.4.x):
2651 - Correctly log long IPv6 exit policies, instead of truncating them
2652 or reporting an error. Fixes bug 9596; bugfix on 0.2.4.7-alpha.
2653 - Our default TLS ecdhe groups were backwards: we meant to be using
2654 P224 for relays (for performance win) and P256 for bridges (since
2655 it is more common in the wild). Instead we had it backwards. After
2656 reconsideration, we decided that the default should be P256 on all
2657 hosts, since its security is probably better, and since P224 is
2658 reportedly used quite little in the wild. Found by "skruffy" on
2659 IRC. Fix for bug 9780; bugfix on 0.2.4.8-alpha.
2660 - Free directory authority certificate download statuses on exit
2661 rather than leaking them. Fixes bug 9644; bugfix on 0.2.4.13-alpha.
2663 o Minor bugfixes (on 0.2.3.x and earlier):
2664 - If the guard we choose first doesn't answer, we would try the
2665 second guard, but once we connected to the second guard we would
2666 abandon it and retry the first one, slowing down bootstrapping.
2667 The fix is to treat all our initially chosen guards as acceptable
2668 to use. Fixes bug 9946; bugfix on 0.1.1.11-alpha.
2669 - Fix an assertion failure that would occur when disabling the
2670 ORPort setting on a running Tor process while accounting was
2671 enabled. Fixes bug 6979; bugfix on 0.2.2.18-alpha.
2672 - When examining the list of network interfaces to find our address,
2673 do not consider non-running or disabled network interfaces. Fixes
2674 bug 9904; bugfix on 0.2.3.11-alpha. Patch from "hantwister".
2675 - Avoid an off-by-one error when checking buffer boundaries when
2676 formatting the exit status of a pluggable transport helper.
2677 This is probably not an exploitable bug, but better safe than
2678 sorry. Fixes bug 9928; bugfix on 0.2.3.18-rc. Bug found by
2681 o Minor features (protecting client timestamps):
2682 - Clients no longer send timestamps in their NETINFO cells. These were
2683 not used for anything, and they provided one small way for clients
2684 to be distinguished from each other as they moved from network to
2685 network or behind NAT. Implements part of proposal 222.
2686 - Clients now round timestamps in INTRODUCE cells down to the nearest
2687 10 minutes. If a new Support022HiddenServices option is set to 0, or
2688 if it's set to "auto" and the feature is disabled in the consensus,
2689 the timestamp is sent as 0 instead. Implements part of proposal 222.
2690 - Stop sending timestamps in AUTHENTICATE cells. This is not such
2691 a big deal from a security point of view, but it achieves no actual
2692 good purpose, and isn't needed. Implements part of proposal 222.
2693 - Reduce down accuracy of timestamps in hidden service descriptors.
2694 Implements part of proposal 222.
2696 o Minor features (other):
2697 - Improve the circuit queue out-of-memory handler. Previously, when
2698 we ran low on memory, we'd close whichever circuits had the most
2699 queued cells. Now, we close those that have the *oldest* queued
2700 cells, on the theory that those are most responsible for us
2701 running low on memory. Based on analysis from a forthcoming paper
2702 by Jansen, Tschorsch, Johnson, and Scheuermann. Fixes bug 9093.
2703 - Generate bootstrapping status update events correctly when fetching
2704 microdescriptors. Fixes bug 9927.
2705 - Update to the October 2 2013 Maxmind GeoLite Country database.
2707 o Documentation fixes:
2708 - Clarify the usage and risks of setting the ContactInfo torrc line
2709 for your relay or bridge. Resolves ticket 9854.
2710 - Add anchors to the manpage so we can link to the html version of
2711 the documentation for specific options. Resolves ticket 9866.
2712 - Replace remaining references to DirServer in man page and
2713 log entries. Resolves ticket 10124.
2716 Changes in version 0.2.5.1-alpha - 2013-10-02
2717 Tor 0.2.5.1-alpha introduces experimental support for syscall sandboxing
2718 on Linux, allows bridges that offer pluggable transports to report usage
2719 statistics, fixes many issues to make testing easier, and provides
2720 a pile of minor features and bugfixes that have been waiting for a
2721 release of the new branch.
2723 This is the first alpha release in a new series, so expect there to
2724 be bugs. Users who would rather test out a more stable branch should
2725 stay with 0.2.4.x for now.
2727 o Major features (security):
2728 - Use the seccomp2 syscall filtering facility on Linux to limit
2729 which system calls Tor can invoke. This is an experimental,
2730 Linux-only feature to provide defense-in-depth against unknown
2731 attacks. To try turning it on, set "Sandbox 1" in your torrc
2732 file. Please be ready to report bugs. We hope to add support
2733 for better sandboxing in the future, including more fine-grained
2734 filters, better division of responsibility, and support for more
2735 platforms. This work has been done by Cristian-Matei Toader for
2736 Google Summer of Code.
2737 - Re-enable TLS 1.1 and 1.2 when built with OpenSSL 1.0.1e or later.
2738 Resolves ticket 6055. (OpenSSL before 1.0.1 didn't have TLS 1.1 or
2739 1.2, and OpenSSL from 1.0.1 through 1.0.1d had bugs that prevented
2740 renegotiation from working with TLS 1.1 or 1.2, so we had disabled
2741 them to solve bug 6033.)
2743 o Major features (other):
2744 - Add support for passing arguments to managed pluggable transport
2745 proxies. Implements ticket 3594.
2746 - Bridges now track GeoIP information and the number of their users
2747 even when pluggable transports are in use, and report usage
2748 statistics in their extra-info descriptors. Resolves tickets 4773
2750 - Make testing Tor networks bootstrap better: lower directory fetch
2751 retry schedules and maximum interval without directory requests,
2752 and raise maximum download tries. Implements ticket 6752.
2753 - Add make target 'test-network' to run tests on a Chutney network.
2754 Implements ticket 8530.
2755 - The ntor handshake is now on-by-default, no matter what the
2756 directory authorities recommend. Implements ticket 8561.
2759 - Instead of writing destroy cells directly to outgoing connection
2760 buffers, queue them and intersperse them with other outgoing cells.
2761 This can prevent a set of resource starvation conditions where too
2762 many pending destroy cells prevent data cells from actually getting
2763 delivered. Reported by "oftc_must_be_destroyed". Fixes bug 7912;
2764 bugfix on 0.2.0.1-alpha.
2765 - If we are unable to save a microdescriptor to the journal, do not
2766 drop it from memory and then reattempt downloading it. Fixes bug
2767 9645; bugfix on 0.2.2.6-alpha.
2768 - The new channel code sometimes lost track of in-progress circuits,
2769 causing long-running clients to stop building new circuits. The
2770 fix is to always call circuit_n_chan_done(chan, 0) from
2771 channel_closed(). Fixes bug 9776; bugfix on 0.2.4.17-rc.
2774 - Tor now builds each source file in two modes: a mode that avoids
2775 exposing identifiers needlessly, and another mode that exposes
2776 more identifiers for testing. This lets the compiler do better at
2777 optimizing the production code, while enabling us to take more
2778 radical measures to let the unit tests test things.
2779 - The production builds no longer include functions used only in
2780 the unit tests; all functions exposed from a module only for
2781 unit-testing are now static in production builds.
2782 - Add an --enable-coverage configuration option to make the unit
2783 tests (and a new src/or/tor-cov target) to build with gcov test
2787 - We now have rudimentary function mocking support that our unit
2788 tests can use to test functions in isolation. Function mocking
2789 lets the tests temporarily replace a function's dependencies with
2790 stub functions, so that the tests can check the function without
2791 invoking the other functions it calls.
2792 - Add more unit tests for the <circid,channel>->circuit map, and
2793 the destroy-cell-tracking code to fix bug 7912.
2794 - Unit tests for failing cases of the TAP onion handshake.
2795 - More unit tests for address-manipulation functions.
2797 o Minor features (protecting client timestamps):
2798 - Clients no longer send timestamps in their NETINFO cells. These were
2799 not used for anything, and they provided one small way for clients
2800 to be distinguished from each other as they moved from network to
2801 network or behind NAT. Implements part of proposal 222.
2802 - Clients now round timestamps in INTRODUCE cells down to the nearest
2803 10 minutes. If a new Support022HiddenServices option is set to 0, or
2804 if it's set to "auto" and the feature is disabled in the consensus,
2805 the timestamp is sent as 0 instead. Implements part of proposal 222.
2806 - Stop sending timestamps in AUTHENTICATE cells. This is not such
2807 a big deal from a security point of view, but it achieves no actual
2808 good purpose, and isn't needed. Implements part of proposal 222.
2809 - Reduce down accuracy of timestamps in hidden service descriptors.
2810 Implements part of proposal 222.
2812 o Minor features (config options):
2813 - Config (torrc) lines now handle fingerprints which are missing
2814 their initial '$'. Resolves ticket 4341; improvement over 0.0.9pre5.
2815 - Support a --dump-config option to print some or all of the
2816 configured options. Mainly useful for debugging the command-line
2817 option parsing code. Helps resolve ticket 4647.
2818 - Raise awareness of safer logging: notify user of potentially
2819 unsafe config options, like logging more verbosely than severity
2820 "notice" or setting SafeLogging to 0. Resolves ticket 5584.
2821 - Add a new configuration option TestingV3AuthVotingStartOffset
2822 that bootstraps a network faster by changing the timing for
2823 consensus votes. Addresses ticket 8532.
2824 - Add a new torrc option "ServerTransportOptions" that allows
2825 bridge operators to pass configuration parameters to their
2826 pluggable transports. Resolves ticket 8929.
2827 - The config (torrc) file now accepts bandwidth and space limits in
2828 bits as well as bytes. (Anywhere that you can say "2 Kilobytes",
2829 you can now say "16 kilobits", and so on.) Resolves ticket 9214.
2832 o Minor features (build):
2833 - Add support for `--library-versions` flag. Implements ticket 6384.
2834 - Return the "unexpected sendme" warnings to a warn severity, but make
2835 them rate limited, to help diagnose ticket 8093.
2836 - Detect a missing asciidoc, and warn the user about it, during
2837 configure rather than at build time. Fixes issue 6506. Patch from
2840 o Minor features (other):
2841 - Use the SOCK_NONBLOCK socket type, if supported, to open nonblocking
2842 sockets in a single system call. Implements ticket 5129.
2843 - Log current accounting state (bytes sent and received + remaining
2844 time for the current accounting period) in the relay's heartbeat
2845 message. Implements ticket 5526; patch from Peter Retzlaff.
2846 - Implement the TRANSPORT_LAUNCHED control port event that
2847 notifies controllers about new launched pluggable
2848 transports. Resolves ticket 5609.
2849 - If we're using the pure-C 32-bit curve25519_donna implementation
2850 of curve25519, build it with the -fomit-frame-pointer option to
2851 make it go faster on register-starved hosts. This improves our
2852 handshake performance by about 6% on i386 hosts without nacl.
2854 - Update to the September 4 2013 Maxmind GeoLite Country database.
2857 - Set the listen() backlog limit to the largest actually supported
2858 on the system, not to the value in a header file. Fixes bug 9716;
2859 bugfix on every released Tor.
2860 - No longer accept malformed http headers when parsing urls from
2861 headers. Now we reply with Bad Request ("400"). Fixes bug 2767;
2862 bugfix on 0.0.6pre1.
2863 - In munge_extrainfo_into_routerinfo(), check the return value of
2864 memchr(). This would have been a serious issue if we ever passed
2865 it a non-extrainfo. Fixes bug 8791; bugfix on 0.2.0.6-alpha. Patch
2867 - On the chance that somebody manages to build Tor on a
2868 platform where time_t is unsigned, correct the way that
2869 microdesc_add_to_cache() handles negative time arguments.
2870 Fixes bug 8042; bugfix on 0.2.3.1-alpha.
2871 - Reject relative control socket paths and emit a warning. Previously,
2872 single-component control socket paths would be rejected, but Tor
2873 would not log why it could not validate the config. Fixes bug 9258;
2874 bugfix on 0.2.3.16-alpha.
2876 o Minor bugfixes (command line):
2877 - Use a single command-line parser for parsing torrc options on the
2878 command line and for finding special command-line options to avoid
2879 inconsistent behavior for torrc option arguments that have the same
2880 names as command-line options. Fixes bugs 4647 and 9578; bugfix on
2882 - No longer allow 'tor --hash-password' with no arguments. Fixes bug
2883 9573; bugfix on 0.0.9pre5.
2885 o Minor fixes (build, auxiliary programs):
2886 - Stop preprocessing the "torify" script with autoconf, since
2887 it no longer refers to LOCALSTATEDIR. Fixes bug 5505; patch
2889 - The tor-fw-helper program now follows the standard convention and
2890 exits with status code "0" on success. Fixes bug 9030; bugfix on
2891 0.2.3.1-alpha. Patch by Arlo Breault.
2892 - Corrected ./configure advice for what openssl dev package you should
2893 install on Debian. Fixes bug 9207; bugfix on 0.2.0.1-alpha.
2895 o Minor code improvements:
2896 - Remove constants and tests for PKCS1 padding; it's insecure and
2897 shouldn't be used for anything new. Fixes bug 8792; patch
2899 - Remove instances of strcpy() from the unit tests. They weren't
2900 hurting anything, since they were only in the unit tests, but it's
2901 embarassing to have strcpy() in the code at all, and some analysis
2902 tools don't like it. Fixes bug 8790; bugfix on 0.2.3.6-alpha and
2903 0.2.3.8-alpha. Patch from Arlo Breault.
2906 - Remove migration code from when we renamed the "cached-routers"
2907 file to "cached-descriptors" back in 0.2.0.8-alpha. This
2908 incidentally resolves ticket 6502 by cleaning up the related code
2909 a bit. Patch from Akshay Hebbar.
2911 o Code simplification and refactoring:
2912 - Extract the common duplicated code for creating a subdirectory
2913 of the data directory and writing to a file in it. Fixes ticket
2914 4282; patch from Peter Retzlaff.
2915 - Since OpenSSL 0.9.7, the i2d_*() functions support allocating output
2916 buffer. Avoid calling twice: i2d_RSAPublicKey(), i2d_DHparams(),
2917 i2d_X509(), and i2d_PublicKey(). Resolves ticket 5170.
2918 - Add a set of accessor functions for the circuit timeout data
2919 structure. Fixes ticket 6153; patch from "piet".
2920 - Clean up exit paths from connection_listener_new(). Closes ticket
2921 8789. Patch from Arlo Breault.
2922 - Since we rely on OpenSSL 0.9.8 now, we can use EVP_PKEY_cmp()
2923 and drop our own custom pkey_eq() implementation. Fixes bug 9043.
2924 - Use a doubly-linked list to implement the global circuit list.
2925 Resolves ticket 9108. Patch from Marek Majkowski.
2926 - Remove contrib/id_to_fp.c since it wasn't used anywhere.
2929 Changes in version 0.2.4.17-rc - 2013-09-05
2930 Tor 0.2.4.17-rc is the third release candidate for the Tor 0.2.4.x
2931 series. It adds an emergency step to help us tolerate the massive
2932 influx of users: 0.2.4 clients using the new (faster and safer) "NTor"
2933 circuit-level handshakes now effectively jump the queue compared to
2934 the 0.2.3 clients using "TAP" handshakes. This release also fixes a
2935 big bug hindering bridge reachability tests.
2938 - Relays now process the new "NTor" circuit-level handshake requests
2939 with higher priority than the old "TAP" circuit-level handshake
2940 requests. We still process some TAP requests to not totally starve
2941 0.2.3 clients when NTor becomes popular. A new consensus parameter
2942 "NumNTorsPerTAP" lets us tune the balance later if we need to.
2943 Implements ticket 9574.
2946 - If the circuit build timeout logic is disabled (via the consensus,
2947 or because we are an authority), then don't build testing circuits.
2948 Fixes bug 9657; bugfix on 0.2.2.14-alpha.
2949 - Bridges now send AUTH_CHALLENGE cells during their v3 handshakes;
2950 previously they did not, which prevented them from receiving
2951 successful connections from relays for self-test or bandwidth
2952 testing. Also, when a relay is extending a circuit to a bridge,
2953 it needs to send a NETINFO cell, even when the bridge hasn't sent
2954 an AUTH_CHALLENGE cell. Fixes bug 9546; bugfix on 0.2.3.6-alpha.
2955 - If the time to download the next old-style networkstatus is in
2956 the future, do not decline to consider whether to download the
2957 next microdescriptor networkstatus. Fixes bug 9564; bugfix on
2961 - Avoid double-closing the listener socket in our socketpair()
2962 replacement (used on Windows) in the case where the addresses on
2963 our opened sockets don't match what we expected. Fixes bug 9400;
2964 bugfix on 0.0.2pre7. Found by Coverity.
2966 o Minor fixes (config options):
2967 - Avoid overflows when the user sets MaxCircuitDirtiness to a
2968 ridiculously high value, by imposing a (ridiculously high) 30-day
2969 maximum on MaxCircuitDirtiness.
2970 - Fix the documentation of HeartbeatPeriod to say that the heartbeat
2971 message is logged at notice, not at info.
2972 - Warn and fail if a server is configured not to advertise any
2973 ORPorts at all. (We need *something* to put in our descriptor,
2974 or we just won't work.)
2977 - Track how many "TAP" and "NTor" circuit handshake requests we get,
2978 and how many we complete, and log it every hour to help relay
2979 operators follow trends in network load. Addresses ticket 9658.
2980 - Update to the August 7 2013 Maxmind GeoLite Country database.
2983 Changes in version 0.2.4.16-rc - 2013-08-10
2984 Tor 0.2.4.16-rc is the second release candidate for the Tor 0.2.4.x
2985 series. It fixes several crash bugs in the 0.2.4 branch.
2988 - Fix a bug in the voting algorithm that could yield incorrect results
2989 when a non-naming authority declared too many flags. Fixes bug 9200;
2990 bugfix on 0.2.0.3-alpha.
2991 - Fix an uninitialized read that could in some cases lead to a remote
2992 crash while parsing INTRODUCE2 cells. Bugfix on 0.2.4.1-alpha.
2993 Anybody running a hidden service on the experimental 0.2.4.x
2994 branch should upgrade. (This is, so far as we know, unrelated to
2996 - Avoid an assertion failure when processing DNS replies without the
2997 answer types we expected. Fixes bug 9337; bugfix on 0.2.4.7-alpha.
2998 - Avoid a crash when using --hash-password. Fixes bug 9295; bugfix on
2999 0.2.4.15-rc. Found by stem integration tests.
3002 - Fix an invalid memory read that occured when a pluggable
3003 transport proxy failed its configuration protocol.
3004 Fixes bug 9288; bugfix on 0.2.4.1-alpha.
3005 - When evaluating whether to use a connection that we haven't
3006 decided is canonical using a recent link protocol version,
3007 decide that it's canonical only if it used address _does_
3008 match the desired address. Fixes bug 9309; bugfix on
3009 0.2.4.4-alpha. Reported by skruffy.
3010 - Make the default behavior of NumDirectoryGuards be to track
3011 NumEntryGuards. Now a user who changes only NumEntryGuards will get
3012 the behavior she expects. Fixes bug 9354; bugfix on 0.2.4.8-alpha.
3013 - Fix a spurious compilation warning with some older versions of
3014 GCC on FreeBSD. Fixes bug 9254; bugfix on 0.2.4.14-alpha.
3017 - Update to the July 3 2013 Maxmind GeoLite Country database.
3020 Changes in version 0.2.4.15-rc - 2013-07-01
3021 Tor 0.2.4.15-rc is the first release candidate for the Tor 0.2.4.x
3022 series. It fixes a few smaller bugs, but generally appears stable.
3023 Please test it and let us know whether it is!
3026 - When receiving a new configuration file via the control port's
3027 LOADCONF command, do not treat the defaults file as absent.
3028 Fixes bug 9122; bugfix on 0.2.3.9-alpha.
3031 - Issue a warning when running with the bufferevents backend enabled.
3032 It's still not stable, and people should know that they're likely
3033 to hit unexpected problems. Closes ticket 9147.
3036 Changes in version 0.2.4.14-alpha - 2013-06-18
3037 Tor 0.2.4.14-alpha fixes a pair of client guard enumeration problems
3038 present in 0.2.4.13-alpha.
3041 - When we have too much memory queued in circuits (according to a new
3042 MaxMemInCellQueues option), close the circuits consuming the most
3043 memory. This prevents us from running out of memory as a relay if
3044 circuits fill up faster than they can be drained. Fixes bug 9063;
3045 bugfix on the 54th commit of Tor. This bug is a further fix beyond
3046 bug 6252, whose fix was merged into 0.2.3.21-rc.
3048 This change also fixes an earlier approach taken in 0.2.4.13-alpha,
3049 where we tried to solve this issue simply by imposing an upper limit
3050 on the number of queued cells for a single circuit. That approach
3051 proved to be problematic, since there are ways to provoke clients to
3052 send a number of cells in excess of any such reasonable limit. Fixes
3053 bug 9072; bugfix on 0.2.4.13-alpha.
3055 - Limit hidden service descriptors to at most ten introduction
3056 points, to slow one kind of guard enumeration. Fixes bug 9002;
3057 bugfix on 0.1.1.11-alpha.
3060 Changes in version 0.2.4.13-alpha - 2013-06-14
3061 Tor 0.2.4.13-alpha fixes a variety of potential remote crash
3062 vulnerabilities, makes socks5 username/password circuit isolation
3063 actually actually work (this time for sure!), and cleans up a bunch
3064 of other issues in preparation for a release candidate.
3066 o Major bugfixes (robustness):
3067 - Close any circuit that has too many cells queued on it. Fixes
3068 bug 9063; bugfix on the 54th commit of Tor. This bug is a further
3069 fix beyond bug 6252, whose fix was merged into 0.2.3.21-rc.
3070 - Prevent the get_freelists() function from running off the end of
3071 the list of freelists if it somehow gets an unrecognized
3072 allocation. Fixes bug 8844; bugfix on 0.2.0.16-alpha. Reported by
3074 - Avoid an assertion failure on OpenBSD (and perhaps other BSDs)
3075 when an exit connection with optimistic data succeeds immediately
3076 rather than returning EINPROGRESS. Fixes bug 9017; bugfix on
3078 - Fix a directory authority crash bug when building a consensus
3079 using an older consensus as its basis. Fixes bug 8833. Bugfix
3083 - Avoid a memory leak where we would leak a consensus body when we
3084 find that a consensus which we couldn't previously verify due to
3085 missing certificates is now verifiable. Fixes bug 8719; bugfix
3087 - We used to always request authority certificates by identity digest,
3088 meaning we'd get the newest one even when we wanted one with a
3089 different signing key. Then we would complain about being given
3090 a certificate we already had, and never get the one we really
3091 wanted. Now we use the "fp-sk/" resource as well as the "fp/"
3092 resource to request the one we want. Fixes bug 5595; bugfix on
3094 - Follow the socks5 protocol when offering username/password
3095 authentication. The fix for bug 8117 exposed this bug, and it
3096 turns out real-world applications like Pidgin do care. Bugfix on
3097 0.2.3.2-alpha; fixes bug 8879.
3098 - Prevent failures on Windows Vista and later when rebuilding the
3099 microdescriptor cache. Diagnosed by Robert Ransom. Fixes bug 8822;
3100 bugfix on 0.2.4.12-alpha.
3103 - Fix an impossible buffer overrun in the AES unit tests. Fixes
3104 bug 8845; bugfix on 0.2.0.7-alpha. Found by eugenis.
3105 - If for some reason we fail to write a microdescriptor while
3106 rebuilding the cache, do not let the annotations from that
3107 microdescriptor linger in the cache file, and do not let the
3108 microdescriptor stay recorded as present in its old location.
3109 Fixes bug 9047; bugfix on 0.2.2.6-alpha.
3110 - Fix a memory leak that would occur whenever a configuration
3111 option changed. Fixes bug 8718; bugfix on 0.2.3.3-alpha.
3112 - Paste the description for PathBias parameters from the man
3113 page into or.h, so the code documents them too. Fixes bug 7982;
3114 bugfix on 0.2.3.17-beta and 0.2.4.8-alpha.
3115 - Relays now treat a changed IPv6 ORPort as sufficient reason to
3116 publish an updated descriptor. Fixes bug 6026; bugfix on
3118 - When launching a resolve request on behalf of an AF_UNIX control
3119 socket, omit the address field of the new entry connection, used in
3120 subsequent controller events, rather than letting tor_dup_addr()
3121 set it to "<unknown address type>". Fixes bug 8639; bugfix on
3124 o Minor bugfixes (log messages):
3125 - Fix a scaling issue in the path bias accounting code that
3126 resulted in "Bug:" log messages from either
3127 pathbias_scale_close_rates() or pathbias_count_build_success().
3128 This represents a bugfix on a previous bugfix: the original fix
3129 attempted in 0.2.4.10-alpha was incomplete. Fixes bug 8235; bugfix
3131 - Give a less useless error message when the user asks for an IPv4
3132 address on an IPv6-only port, or vice versa. Fixes bug 8846; bugfix
3136 - Downgrade "unexpected SENDME" warnings to protocol-warn for 0.2.4.x,
3137 to tolerate bug 8093 for now.
3138 - Add an "ignoring-advertised-bws" boolean to the flag-threshold lines
3139 in directory authority votes to describe whether they have enough
3140 measured bandwidths to ignore advertised (relay descriptor)
3141 bandwidth claims. Resolves ticket 8711.
3142 - Update to the June 5 2013 Maxmind GeoLite Country database.
3144 o Removed documentation:
3145 - Remove some of the older contents of doc/ as obsolete; move others
3146 to torspec.git. Fixes bug 8965.
3148 o Code simplification and refactoring:
3149 - Avoid using character buffers when constructing most directory
3150 objects: this approach was unwieldy and error-prone. Instead,
3151 build smartlists of strings, and concatenate them when done.
3154 Changes in version 0.2.4.12-alpha - 2013-04-18
3155 Tor 0.2.4.12-alpha moves Tor forward on several fronts: it starts the
3156 process for lengthening the guard rotation period, makes directory
3157 authority opinions in the consensus a bit less gameable, makes socks5
3158 username/password circuit isolation actually work, and fixes a wide
3159 variety of other issues.
3162 - Raise the default time that a client keeps an entry guard from
3163 "1-2 months" to "2-3 months", as suggested by Tariq Elahi's WPES
3164 2012 paper. (We would make it even longer, but we need better client
3165 load balancing first.) Also, make the guard lifetime controllable
3166 via a new GuardLifetime torrc option and a GuardLifetime consensus
3167 parameter. Start of a fix for bug 8240; bugfix on 0.1.1.11-alpha.
3168 - Directory authorities now prefer using measured bandwidths to
3169 advertised ones when computing flags and thresholds. Resolves
3171 - Directory authorities that have more than a threshold number
3172 of relays with measured bandwidths now treat relays with unmeasured
3173 bandwidths as having bandwidth 0. Resolves ticket 8435.
3175 o Major bugfixes (assert / resource use):
3176 - Avoid a bug where our response to TLS renegotiation under certain
3177 network conditions could lead to a busy-loop, with 100% CPU
3178 consumption. Fixes bug 5650; bugfix on 0.2.0.16-alpha.
3179 - Avoid an assertion when we discover that we'd like to write a cell
3180 onto a closing connection: just discard the cell. Fixes another
3181 case of bug 7350; bugfix on 0.2.4.4-alpha.
3183 o Major bugfixes (client-side privacy):
3184 - When we mark a circuit as unusable for new circuits, have it
3185 continue to be unusable for new circuits even if MaxCircuitDirtiness
3186 is increased too much at the wrong time, or the system clock jumps
3187 backwards. Fixes bug 6174; bugfix on 0.0.2pre26.
3188 - If ClientDNSRejectInternalAddresses ("do not believe DNS queries
3189 which have resolved to internal addresses") is set, apply that
3190 rule to IPv6 as well. Fixes bug 8475; bugfix on 0.2.0.7-alpha.
3191 - When an exit relay rejects a stream with reason "exit policy", but
3192 we only know an exit policy summary (e.g. from the microdesc
3193 consensus) for it, do not mark the relay as useless for all exiting.
3194 Instead, mark just the circuit as unsuitable for that particular
3195 address. Fixes part of bug 7582; bugfix on 0.2.3.2-alpha.
3196 - Allow applications to get proper stream isolation with
3197 IsolateSOCKSAuth. Many SOCKS5 clients that want to offer
3198 username/password authentication also offer "no authentication". Tor
3199 had previously preferred "no authentication", so the applications
3200 never actually sent Tor their auth details. Now Tor selects
3201 username/password authentication if it's offered. You can disable
3202 this behavior on a per-SOCKSPort basis via PreferSOCKSNoAuth. Fixes
3203 bug 8117; bugfix on 0.2.3.3-alpha.
3205 o Major bugfixes (other):
3206 - When unable to find any working directory nodes to use as a
3207 directory guard, give up rather than adding the same non-working
3208 nodes to the directory guard list over and over. Fixes bug 8231;
3209 bugfix on 0.2.4.8-alpha.
3212 - Reject as invalid most directory objects containing a NUL.
3213 Belt-and-suspender fix for bug 8037.
3214 - In our testsuite, create temporary directories with a bit more
3215 entropy in their name to make name collisions less likely. Fixes
3217 - Add CACHED keyword to ADDRMAP events in the control protocol
3218 to indicate whether a DNS result will be cached or not. Resolves
3220 - Update to the April 3 2013 Maxmind GeoLite Country database.
3222 o Minor features (build):
3223 - Detect and reject attempts to build Tor with threading support
3224 when OpenSSL has been compiled without threading support.
3226 - Clarify that when autoconf is checking for nacl, it is checking
3227 specifically for nacl with a fast curve25519 implementation.
3229 - Warn if building on a platform with an unsigned time_t: there
3230 are too many places where Tor currently assumes that time_t can
3231 hold negative values. We'd like to fix them all, but probably
3234 o Minor bugfixes (build):
3235 - Fix some bugs in tor-fw-helper-natpmp when trying to build and
3236 run it on Windows. More bugs likely remain. Patch from Gisle Vanem.
3237 Fixes bug 7280; bugfix on 0.2.3.1-alpha.
3238 - Add the old src/or/micro-revision.i filename to CLEANFILES.
3239 On the off chance that somebody has one, it will go away as soon
3240 as they run "make clean". Fix for bug 7143; bugfix on 0.2.4.1-alpha.
3241 - Build Tor correctly on 32-bit platforms where the compiler can build
3242 but not run code using the "uint128_t" construction. Fixes bug 8587;
3243 bugfix on 0.2.4.8-alpha.
3244 - Fix compilation warning with some versions of clang that would
3245 prefer the -Wswitch-enum compiler flag to warn about switch
3246 statements with missing enum values, even if those switch
3247 statements have a "default:" statement. Fixes bug 8598; bugfix
3250 o Minor bugfixes (protocol):
3251 - Fix the handling of a TRUNCATE cell when it arrives while the
3252 circuit extension is in progress. Fixes bug 7947; bugfix on 0.0.7.1.
3253 - Fix a misframing issue when reading the version numbers in a
3254 VERSIONS cell. Previously we would recognize [00 01 00 02] as
3255 'version 1, version 2, and version 0x100', when it should have
3256 only included versions 1 and 2. Fixes bug 8059; bugfix on
3257 0.2.0.10-alpha. Reported pseudonymously.
3258 - Make the format and order of STREAM events for DNS lookups
3259 consistent among the various ways to launch DNS lookups. Fixes
3260 bug 8203; bugfix on 0.2.0.24-rc. Patch by "Desoxy."
3261 - Correct our check for which versions of Tor support the EXTEND2
3262 cell. We had been willing to send it to Tor 0.2.4.7-alpha and
3263 later, when support was really added in version 0.2.4.8-alpha.
3264 Fixes bug 8464; bugfix on 0.2.4.8-alpha.
3266 o Minor bugfixes (other):
3267 - Correctly store microdescriptors and extrainfo descriptors with
3268 an internal NUL byte. Fixes bug 8037; bugfix on 0.2.0.1-alpha.
3269 Bug reported by "cypherpunks".
3270 - Increase the width of the field used to remember a connection's
3271 link protocol version to two bytes. Harmless for now, since the
3272 only currently recognized versions are one byte long. Reported
3273 pseudonymously. Fixes bug 8062; bugfix on 0.2.0.10-alpha.
3274 - If the state file's path bias counts are invalid (presumably from a
3275 buggy Tor prior to 0.2.4.10-alpha), make them correct. Also add
3276 additional checks and log messages to the scaling of Path Bias
3277 counts, in case there still are remaining issues with scaling.
3278 Should help resolve bug 8235.
3279 - Eliminate several instances where we use "Nickname=ID" to refer to
3280 nodes in logs. Use "Nickname (ID)" instead. (Elsewhere, we still use
3281 "$ID=Nickname", which is also acceptable.) Fixes bug 7065. Bugfix
3282 on 0.2.3.21-rc, 0.2.4.5-alpha, 0.2.4.8-alpha, and 0.2.4.10-alpha.
3284 o Minor bugfixes (syscalls):
3285 - Always check the return values of functions fcntl() and
3286 setsockopt(). We don't believe these are ever actually failing in
3287 practice, but better safe than sorry. Also, checking these return
3288 values should please analysis tools like Coverity. Patch from
3289 'flupzor'. Fixes bug 8206; bugfix on all versions of Tor.
3290 - Use direct writes rather than stdio when building microdescriptor
3291 caches, in an attempt to mitigate bug 8031, or at least make it
3294 o Minor bugfixes (config):
3295 - When rejecting a configuration because we were unable to parse a
3296 quoted string, log an actual error message. Fixes bug 7950; bugfix
3298 - Behave correctly when the user disables LearnCircuitBuildTimeout
3299 but doesn't tell us what they would like the timeout to be. Fixes
3300 bug 6304; bugfix on 0.2.2.14-alpha.
3301 - When autodetecting the number of CPUs, use the number of available
3302 CPUs in preference to the number of configured CPUs. Inform the
3303 user if this reduces the number of available CPUs. Fixes bug 8002;
3304 bugfix on 0.2.3.1-alpha.
3305 - Make it an error when you set EntryNodes but disable UseGuardNodes,
3306 since it will (surprisingly to some users) ignore EntryNodes. Fixes
3307 bug 8180; bugfix on 0.2.3.11-alpha.
3308 - Allow TestingTorNetworks to override the 4096-byte minimum for
3309 the Fast threshold. Otherwise they can't bootstrap until they've
3310 observed more traffic. Fixes bug 8508; bugfix on 0.2.4.10-alpha.
3311 - Fix some logic errors when the user manually overrides the
3312 PathsNeededToBuildCircuits option in torrc. Fixes bug 8599; bugfix
3315 o Minor bugfixes (log messages to help diagnose bugs):
3316 - If we fail to free a microdescriptor because of bug 7164, log
3317 the filename and line number from which we tried to free it.
3318 - Add another diagnostic to the heartbeat message: track and log
3319 overhead that TLS is adding to the data we write. If this is
3320 high, we are sending too little data to SSL_write at a time.
3321 Diagnostic for bug 7707.
3322 - Add more detail to a log message about relaxed timeouts, to help
3324 - Warn more aggressively when flushing microdescriptors to a
3325 microdescriptor cache fails, in an attempt to mitigate bug 8031,
3326 or at least make it more diagnosable.
3327 - Improve debugging output to help track down bug 8185 ("Bug:
3328 outgoing relay cell has n_chan==NULL. Dropping.")
3329 - Log the purpose of a path-bias testing circuit correctly.
3330 Improves a log message from bug 8477; bugfix on 0.2.4.8-alpha.
3332 o Minor bugfixes (0.2.4.x log messages that were too noisy):
3333 - Don't attempt to relax the timeout of already opened 1-hop circuits.
3334 They might never timeout. This should eliminate some/all cases of
3335 the relaxed timeout log message.
3336 - Use circuit creation time for network liveness evaluation. This
3337 should eliminate warning log messages about liveness caused
3338 by changes in timeout evaluation. Fixes bug 6572; bugfix on
3340 - Reduce a path bias length check from notice to info. The message
3341 is triggered when creating controller circuits. Fixes bug 8196;
3342 bugfix on 0.2.4.8-alpha.
3343 - Fix a path state issue that triggered a notice during relay startup.
3344 Fixes bug 8320; bugfix on 0.2.4.10-alpha.
3345 - Reduce occurrences of warns about circuit purpose in
3346 connection_ap_expire_building(). Fixes bug 8477; bugfix on
3349 o Minor bugfixes (pre-0.2.4.x log messages that were too noisy):
3350 - If we encounter a write failure on a SOCKS connection before we
3351 finish our SOCKS handshake, don't warn that we closed the
3352 connection before we could send a SOCKS reply. Fixes bug 8427;
3353 bugfix on 0.1.0.1-rc.
3354 - Correctly recognize that [::1] is a loopback address. Fixes
3355 bug 8377; bugfix on 0.2.1.3-alpha.
3356 - Fix a directory authority warn caused when we have a large amount
3357 of badexit bandwidth. Fixes bug 8419; bugfix on 0.2.2.10-alpha.
3358 - Don't log inappropriate heartbeat messages when hibernating: a
3359 hibernating node is _expected_ to drop out of the consensus,
3360 decide it isn't bootstrapped, and so forth. Fixes bug 7302;
3361 bugfix on 0.2.3.1-alpha.
3362 - Don't complain about bootstrapping problems while hibernating.
3363 These complaints reflect a general code problem, but not one
3364 with any problematic effects (no connections are actually
3365 opened). Fixes part of bug 7302; bugfix on 0.2.3.2-alpha.
3367 o Documentation fixes:
3368 - Update tor-fw-helper.1.txt and tor-fw-helper.c to make option
3369 names match. Fixes bug 7768.
3370 - Make the torify manpage no longer refer to tsocks; torify hasn't
3371 supported tsocks since 0.2.3.14-alpha.
3372 - Make the tor manpage no longer reference tsocks.
3373 - Fix the GeoIPExcludeUnknown documentation to refer to
3374 ExcludeExitNodes rather than the currently nonexistent
3375 ExcludeEntryNodes. Spotted by "hamahangi" on tor-talk.
3378 - The tor-tsocks.conf is no longer distributed or installed. We
3379 recommend that tsocks users use torsocks instead. Resolves
3383 Changes in version 0.2.4.11-alpha - 2013-03-11
3384 Tor 0.2.4.11-alpha makes relay measurement by directory authorities
3385 more robust, makes hidden service authentication work again, and
3386 resolves a DPI fingerprint for Tor's SSL transport.
3388 o Major features (directory authorities):
3389 - Directory authorities now support a new consensus method (17)
3390 where they cap the published bandwidth of servers for which
3391 insufficient bandwidth measurements exist. Fixes part of bug 2286.
3392 - Directory authorities that set "DisableV2DirectoryInfo_ 1" no longer
3393 serve any v2 directory information. Now we can test disabling the
3394 old deprecated v2 directory format, and see whether doing so has
3395 any effect on network load. Begins to fix bug 6783.
3396 - Directory authorities now include inside each vote a statement of
3397 the performance thresholds they used when assigning flags.
3398 Implements ticket 8151.
3400 o Major bugfixes (directory authorities):
3401 - Stop marking every relay as having been down for one hour every
3402 time we restart a directory authority. These artificial downtimes
3403 were messing with our Stable and Guard flag calculations. Fixes
3404 bug 8218 (introduced by the fix for 1035). Bugfix on 0.2.2.23-alpha.
3406 o Major bugfixes (hidden services):
3407 - Allow hidden service authentication to succeed again. When we
3408 refactored the hidden service introduction code back
3409 in 0.2.4.1-alpha, we didn't update the code that checks
3410 whether authentication information is present, causing all
3411 authentication checks to return "false". Fix for bug 8207; bugfix
3412 on 0.2.4.1-alpha. Found by Coverity; this is CID 718615.
3414 o Minor features (relays, bridges):
3415 - Make bridge relays check once a minute for whether their IP
3416 address has changed, rather than only every 15 minutes. Resolves
3418 - Refactor resolve_my_address() so it returns the method by which we
3419 decided our public IP address (explicitly configured, resolved from
3420 explicit hostname, guessed from interfaces, learned by gethostname).
3421 Now we can provide more helpful log messages when a relay guesses
3422 its IP address incorrectly (e.g. due to unexpected lines in
3423 /etc/hosts). Resolves ticket 2267.
3424 - Teach bridge-using clients to avoid 0.2.2 bridges when making
3425 microdescriptor-related dir requests, and only fall back to normal
3426 descriptors if none of their bridges can handle microdescriptors
3427 (as opposed to the fix in ticket 4013, which caused them to fall
3428 back to normal descriptors if *any* of their bridges preferred
3429 them). Resolves ticket 4994.
3430 - Randomize the lifetime of our SSL link certificate, so censors can't
3431 use the static value for filtering Tor flows. Resolves ticket 8443;
3432 related to ticket 4014 which was included in 0.2.2.33.
3433 - Support a new version of the link protocol that allows 4-byte circuit
3434 IDs. Previously, circuit IDs were limited to 2 bytes, which presented
3435 a possible resource exhaustion issue. Closes ticket 7351; implements
3438 o Minor features (portability):
3439 - Tweak the curve25519-donna*.c implementations to tolerate systems
3440 that lack stdint.h. Fixes bug 3894; bugfix on 0.2.4.8-alpha.
3441 - Use Ville Laurikari's implementation of AX_CHECK_SIGN() to determine
3442 the signs of types during autoconf. This is better than our old
3443 approach, which didn't work when cross-compiling.
3444 - Detect the sign of enum values, rather than assuming that MSC is the
3445 only compiler where enum types are all signed. Fixes bug 7727;
3446 bugfix on 0.2.4.10-alpha.
3448 o Minor features (other):
3449 - Say "KBytes" rather than "KB" in the man page (for various values
3450 of K), to further reduce confusion about whether Tor counts in
3451 units of memory or fractions of units of memory. Resolves ticket 7054.
3452 - Clear the high bit on curve25519 public keys before passing them to
3453 our backend, in case we ever wind up using a backend that doesn't do
3454 so itself. If we used such a backend, and *didn't* clear the high bit,
3455 we could wind up in a situation where users with such backends would
3456 be distinguishable from users without. Fixes bug 8121; bugfix on
3458 - Update to the March 6 2013 Maxmind GeoLite Country database.
3460 o Minor bugfixes (clients):
3461 - When we receive a RELAY_END cell with the reason DONE, or with no
3462 reason, before receiving a RELAY_CONNECTED cell, report the SOCKS
3463 status as "connection refused". Previously we reported these cases
3464 as success but then immediately closed the connection. Fixes bug
3465 7902; bugfix on 0.1.0.1-rc. Reported by "oftc_must_be_destroyed".
3466 - Downgrade an assertion in connection_ap_expire_beginning to an
3467 LD_BUG message. The fix for bug 8024 should prevent this message
3468 from displaying, but just in case, a warn that we can diagnose
3469 is better than more assert crashes. Fixes bug 8065; bugfix on
3471 - Lower path use bias thresholds to .80 for notice and .60 for warn.
3472 Also make the rate limiting flags for the path use bias log messages
3473 independent from the original path bias flags. Fixes bug 8161;
3474 bugfix on 0.2.4.10-alpha.
3476 o Minor bugfixes (relays):
3477 - Stop trying to resolve our hostname so often (e.g. every time we
3478 think about doing a directory fetch). Now we reuse the cached
3479 answer in some cases. Fixes bugs 1992 (bugfix on 0.2.0.20-rc)
3480 and 2410 (bugfix on 0.1.2.2-alpha).
3481 - Stop sending a stray "(null)" in some cases for the server status
3482 "EXTERNAL_ADDRESS" controller event. Resolves bug 8200; bugfix
3484 - When choosing which stream on a formerly stalled circuit to wake
3485 first, make better use of the platform's weak RNG. Previously,
3486 we had been using the % ("modulo") operator to try to generate a
3487 1/N chance of picking each stream, but this behaves badly with
3488 many platforms' choice of weak RNG. Fixes bug 7801; bugfix on
3490 - Use our own weak RNG when we need a weak RNG. Windows's rand() and
3491 Irix's random() only return 15 bits; Solaris's random() returns more
3492 bits but its RAND_MAX says it only returns 15, and so on. Motivated
3493 by the fix for bug 7801; bugfix on 0.2.2.20-alpha.
3495 o Minor bugfixes (directory authorities):
3496 - Directory authorities now use less space when formatting identical
3497 microdescriptor lines in directory votes. Fixes bug 8158; bugfix
3500 o Minor bugfixes (memory leaks spotted by Coverity -- bug 7816):
3501 - Avoid leaking memory if we fail to compute a consensus signature
3502 or we generate a consensus we can't parse. Bugfix on 0.2.0.5-alpha.
3503 - Fix a memory leak when receiving headers from an HTTPS proxy. Bugfix
3505 - Fix a memory leak during safe-cookie controller authentication.
3506 Bugfix on 0.2.3.13-alpha.
3507 - Avoid memory leak of IPv6 policy content if we fail to format it into
3508 a router descriptor. Bugfix on 0.2.4.7-alpha.
3510 o Minor bugfixes (other code correctness issues):
3511 - Avoid a crash if we fail to generate an extrainfo descriptor.
3512 Fixes bug 8208; bugfix on 0.2.3.16-alpha. Found by Coverity;
3514 - When detecting the largest possible file descriptor (in order to
3515 close all file descriptors when launching a new program), actually
3516 use _SC_OPEN_MAX. The old code for doing this was very, very broken.
3517 Fixes bug 8209; bugfix on 0.2.3.1-alpha. Found by Coverity; this
3519 - Fix a copy-and-paste error when adding a missing A1 to a routerset
3520 because of GeoIPExcludeUnknown. Fix for Coverity CID 980650.
3521 Bugfix on 0.2.4.10-alpha.
3522 - Fix an impossible-to-trigger integer overflow when estimating how
3523 long our onionskin queue would take. (This overflow would require us
3524 to accept 4 million onionskins before processing 100 of them.) Fixes
3525 bug 8210; bugfix on 0.2.4.10-alpha.
3527 o Code simplification and refactoring:
3528 - Add a wrapper function for the common "log a message with a
3532 Changes in version 0.2.4.10-alpha - 2013-02-04
3533 Tor 0.2.4.10-alpha adds defenses at the directory authority level from
3534 certain attacks that flood the network with relays; changes the queue
3535 for circuit create requests from a sized-based limit to a time-based
3536 limit; resumes building with MSVC on Windows; and fixes a wide variety
3539 o Major bugfixes (directory authority):
3540 - When computing directory thresholds, ignore any rejected-as-sybil
3541 nodes during the computation so that they can't influence Fast,
3542 Guard, etc. (We should have done this for proposal 109.) Fixes
3544 - When marking a node as a likely sybil, reset its uptime metrics
3545 to zero, so that it cannot time towards getting marked as Guard,
3546 Stable, or HSDir. (We should have done this for proposal 109.) Fixes
3550 - When a TLS write is partially successful but incomplete, remember
3551 that the flushed part has been flushed, and notice that bytes were
3552 actually written. Reported and fixed pseudonymously. Fixes bug
3553 7708; bugfix on Tor 0.1.0.5-rc.
3554 - Reject bogus create and relay cells with 0 circuit ID or 0 stream
3555 ID: these could be used to create unexpected streams and circuits
3556 which would count as "present" to some parts of Tor but "absent"
3557 to others, leading to zombie circuits and streams or to a bandwidth
3558 denial-of-service. Fixes bug 7889; bugfix on every released version
3559 of Tor. Reported by "oftc_must_be_destroyed".
3560 - Rename all macros in our local copy of queue.h to begin with "TOR_".
3561 This change seems the only good way to permanently prevent conflicts
3562 with queue.h on various operating systems. Fixes bug 8107; bugfix
3565 o Major features (relay):
3566 - Instead of limiting the number of queued onionskins (aka circuit
3567 create requests) to a fixed, hard-to-configure number, we limit
3568 the size of the queue based on how many we expect to be able to
3569 process in a given amount of time. We estimate the time it will
3570 take to process an onionskin based on average processing time
3571 of previous onionskins. Closes ticket 7291. You'll never have to
3572 configure MaxOnionsPending again.
3574 o Major features (portability):
3575 - Resume building correctly with MSVC and Makefile.nmake. This patch
3576 resolves numerous bugs and fixes reported by ultramage, including
3577 7305, 7308, 7309, 7310, 7312, 7313, 7315, 7316, and 7669.
3578 - Make the ntor and curve25519 code build correctly with MSVC.
3579 Fix on 0.2.4.8-alpha.
3582 - When directory authorities are computing thresholds for flags,
3583 never let the threshold for the Fast flag fall below 4096
3584 bytes. Also, do not consider nodes with extremely low bandwidths
3585 when deciding thresholds for various directory flags. This change
3586 should raise our threshold for Fast relays, possibly in turn
3587 improving overall network performance; see ticket 1854. Resolves
3589 - The Tor client now ignores sub-domain components of a .onion
3590 address. This change makes HTTP "virtual" hosting
3591 possible: http://foo.aaaaaaaaaaaaaaaa.onion/ and
3592 http://bar.aaaaaaaaaaaaaaaa.onion/ can be two different websites
3593 hosted on the same hidden service. Implements proposal 204.
3594 - We compute the overhead from passing onionskins back and forth to
3595 cpuworkers, and report it when dumping statistics in response to
3596 SIGUSR1. Supports ticket 7291.
3598 o Minor features (path selection):
3599 - When deciding whether we have enough descriptors to build circuits,
3600 instead of looking at raw relay counts, look at which fraction
3601 of (bandwidth-weighted) paths we're able to build. This approach
3602 keeps clients from building circuits if their paths are likely to
3603 stand out statistically. The default fraction of paths needed is
3604 taken from the consensus directory; you can override it with the
3605 new PathsNeededToBuildCircuits option. Fixes ticket 5956.
3606 - When any country code is listed in ExcludeNodes or ExcludeExitNodes,
3607 and we have GeoIP information, also exclude all nodes with unknown
3608 countries "??" and "A1". This behavior is controlled by the
3609 new GeoIPExcludeUnknown option: you can make such nodes always
3610 excluded with "GeoIPExcludeUnknown 1", and disable the feature
3611 with "GeoIPExcludeUnknown 0". Setting "GeoIPExcludeUnknown auto"
3612 gets you the default behavior. Implements feature 7706.
3613 - Path Use Bias: Perform separate accounting for successful circuit
3614 use. Keep separate statistics on stream attempt rates versus stream
3615 success rates for each guard. Provide configurable thresholds to
3616 determine when to emit log messages or disable use of guards that
3617 fail too many stream attempts. Resolves ticket 7802.
3619 o Minor features (log messages):
3620 - When learning a fingerprint for a bridge, log its corresponding
3621 transport type. Implements ticket 7896.
3622 - Improve the log message when "Bug/attack: unexpected sendme cell
3623 from client" occurs, to help us track bug 8093.
3626 - Remove a couple of extraneous semicolons that were upsetting the
3627 cparser library. Patch by Christian Grothoff. Fixes bug 7115;
3628 bugfix on 0.2.2.1-alpha.
3629 - Remove a source of rounding error during path bias count scaling;
3630 don't count cannibalized circuits as used for path bias until we
3631 actually try to use them; and fix a circuit_package_relay_cell()
3632 warning message about n_chan==NULL. Fixes bug 7802.
3633 - Detect nacl when its headers are in a nacl/ subdirectory. Also,
3634 actually link against nacl when we're configured to use it. Fixes
3635 bug 7972; bugfix on 0.2.4.8-alpha.
3636 - Compile correctly with the --disable-curve25519 option. Fixes
3637 bug 8153; bugfix on 0.2.4.8-alpha.
3639 o Build improvements:
3640 - Do not report status verbosely from autogen.sh unless the -v flag
3641 is specified. Fixes issue 4664. Patch from Onizuka.
3642 - Replace all calls to snprintf() outside of src/ext with
3643 tor_snprintf(). Also remove the #define to replace snprintf with
3644 _snprintf on Windows; they have different semantics, and all of
3645 our callers should be using tor_snprintf() anyway. Fixes bug 7304.
3646 - Try to detect if we are ever building on a platform where
3647 memset(...,0,...) does not set the value of a double to 0.0. Such
3648 platforms are permitted by the C standard, though in practice
3649 they're pretty rare (since IEEE 754 is nigh-ubiquitous). We don't
3650 currently support them, but it's better to detect them and fail
3651 than to perform erroneously.
3654 - Stop exporting estimates of v2 and v3 directory traffic shares
3655 in extrainfo documents. They were unneeded and sometimes inaccurate.
3656 Also stop exporting any v2 directory request statistics. Resolves
3658 - Drop support for detecting and warning about versions of Libevent
3659 before 1.3e. Nothing reasonable ships with them any longer;
3660 warning the user about them shouldn't be needed. Resolves ticket
3663 o Code simplifications and refactoring:
3664 - Rename "isin" functions to "contains", for grammar. Resolves
3666 - Rename Tor's logging function log() to tor_log(), to avoid conflicts
3667 with the natural logarithm function from the system libm. Resolves
3671 Changes in version 0.2.4.9-alpha - 2013-01-15
3672 Tor 0.2.4.9-alpha provides a quick fix to make the new ntor handshake
3676 - Fix backward compatibility logic when receiving an embedded ntor
3677 handshake tunneled in a CREATE cell. This clears up the "Bug:
3678 couldn't format CREATED cell" warning. Fixes bug 7959; bugfix
3682 Changes in version 0.2.4.8-alpha - 2013-01-14
3683 Tor 0.2.4.8-alpha introduces directory guards to reduce user enumeration
3684 risks, adds a new stronger and faster circuit handshake, and offers
3685 stronger and faster link encryption when both sides support it.
3688 - Preliminary support for directory guards (proposal 207): when
3689 possible, clients now use their entry guards for non-anonymous
3690 directory requests. This can help prevent client enumeration. Note
3691 that this behavior only works when we have a usable consensus
3692 directory, and when options about what to download are more or less
3693 standard. In the future we should re-bootstrap from our guards,
3694 rather than re-bootstrapping from the preconfigured list of
3695 directory sources that ships with Tor. Resolves ticket 6526.
3696 - Tor relays and clients now support a better CREATE/EXTEND cell
3697 format, allowing the sender to specify multiple address, identity,
3698 and handshake types. Implements Robert Ransom's proposal 200;
3701 o Major features (new circuit handshake):
3702 - Tor now supports a new circuit extension handshake designed by Ian
3703 Goldberg, Douglas Stebila, and Berkant Ustaoglu. Our original
3704 circuit extension handshake, later called "TAP", was a bit slow
3705 (especially on the relay side), had a fragile security proof, and
3706 used weaker keys than we'd now prefer. The new circuit handshake
3707 uses Dan Bernstein's "curve25519" elliptic-curve Diffie-Hellman
3708 function, making it significantly more secure than the older
3709 handshake, and significantly faster. Tor can use one of two built-in
3710 pure-C curve25519-donna implementations by Adam Langley, or it
3711 can link against the "nacl" library for a tuned version if present.
3713 The built-in version is very fast for 64-bit systems when building
3714 with GCC. The built-in 32-bit version is still faster than the
3715 old TAP protocol, but using libnacl is better on most such hosts.
3717 Clients don't currently use this protocol by default, since
3718 comparatively few clients support it so far. To try it, set
3719 UseNTorHandshake to 1.
3721 Implements proposal 216; closes ticket 7202.
3723 o Major features (better link encryption):
3724 - Relays can now enable the ECDHE TLS ciphersuites when available
3725 and appropriate. These ciphersuites let us negotiate forward-secure
3726 TLS secret keys more safely and more efficiently than with our
3727 previous use of Diffie-Hellman modulo a 1024-bit prime. By default,
3728 public relays prefer the (faster) P224 group, and bridges prefer
3729 the (more common) P256 group; you can override this with the
3732 Enabling these ciphers was a little tricky, since for a long time,
3733 clients had been claiming to support them without actually doing
3734 so, in order to foil fingerprinting. But with the client-side
3735 implementation of proposal 198 in 0.2.3.17-beta, clients can now
3736 match the ciphers from recent Firefox versions *and* list the
3737 ciphers they actually mean, so relays can believe such clients
3738 when they advertise ECDHE support in their TLS ClientHello messages.
3740 This feature requires clients running 0.2.3.17-beta or later,
3741 and requires both sides to be running OpenSSL 1.0.0 or later
3742 with ECC support. OpenSSL 1.0.1, with the compile-time option
3743 "enable-ec_nistp_64_gcc_128", is highly recommended.
3745 Implements the relay side of proposal 198; closes ticket 7200.
3748 - Avoid crashing when, as a relay without IPv6-exit support, a
3749 client insists on getting an IPv6 address or nothing. Fixes bug
3750 7814; bugfix on 0.2.4.7-alpha.
3753 - Improve circuit build timeout handling for hidden services.
3754 In particular: adjust build timeouts more accurately depending
3755 upon the number of hop-RTTs that a particular circuit type
3756 undergoes. Additionally, launch intro circuits in parallel
3757 if they timeout, and take the first one to reply as valid.
3758 - Work correctly on Unix systems where EAGAIN and EWOULDBLOCK are
3759 separate error codes; or at least, don't break for that reason.
3760 Fixes bug 7935. Reported by "oftc_must_be_destroyed".
3761 - Update to the January 2 2013 Maxmind GeoLite Country database.
3763 o Minor features (testing):
3764 - Add benchmarks for DH (1024-bit multiplicative group) and ECDH
3765 (P-256) Diffie-Hellman handshakes to src/or/bench.
3766 - Add benchmark functions to test onion handshake performance.
3768 o Minor features (path bias detection):
3769 - Alter the Path Bias log messages to be more descriptive in terms
3770 of reporting timeouts and other statistics.
3771 - Create three levels of Path Bias log messages, as opposed to just
3772 two. These are configurable via consensus as well as via the torrc
3773 options PathBiasNoticeRate, PathBiasWarnRate, PathBiasExtremeRate.
3774 The default values are 0.70, 0.50, and 0.30 respectively.
3775 - Separate the log message levels from the decision to drop guards,
3776 which also is available via torrc option PathBiasDropGuards.
3777 PathBiasDropGuards still defaults to 0 (off).
3778 - Deprecate PathBiasDisableRate in favor of PathBiasDropGuards
3779 in combination with PathBiasExtremeRate.
3780 - Increase the default values for PathBiasScaleThreshold and
3781 PathBiasCircThreshold from (200, 20) to (300, 150).
3782 - Add in circuit usage accounting to path bias. If we try to use a
3783 built circuit but fail for any reason, it counts as path bias.
3784 Certain classes of circuits where the adversary gets to pick your
3785 destination node are exempt from this accounting. Usage accounting
3786 can be specifically disabled via consensus parameter or torrc.
3787 - Convert all internal path bias state to double-precision floating
3788 point, to avoid roundoff error and other issues.
3789 - Only record path bias information for circuits that have completed
3790 *two* hops. Assuming end-to-end tagging is the attack vector, this
3791 makes us more resilient to ambient circuit failure without any
3792 detection capability loss.
3794 o Minor bugfixes (log messages):
3795 - Rate-limit the "No circuits are opened. Relaxed timeout for a
3796 circuit with channel state open..." message to once per hour to
3797 keep it from filling the notice logs. Mitigates bug 7799 but does
3798 not fix the underlying cause. Bugfix on 0.2.4.7-alpha.
3799 - Avoid spurious warnings when configuring multiple client ports of
3800 which only some are nonlocal. Previously, we had claimed that some
3801 were nonlocal when in fact they weren't. Fixes bug 7836; bugfix on
3804 o Code simplifications and refactoring:
3805 - Get rid of a couple of harmless clang warnings, where we compared
3806 enums to ints. These warnings are newly introduced in clang 3.2.
3807 - Split the onion.c file into separate modules for the onion queue
3808 and the different handshakes it supports.
3809 - Remove the marshalling/unmarshalling code for sending requests to
3810 cpuworkers over a socket, and instead just send structs. The
3811 recipient will always be the same Tor binary as the sender, so
3812 any encoding is overkill.
3815 Changes in version 0.2.4.7-alpha - 2012-12-24
3816 Tor 0.2.4.7-alpha introduces a new approach to providing fallback
3817 directory mirrors for more robust bootstrapping; fixes more issues where
3818 clients with changing network conditions refuse to make any circuits;
3819 adds initial support for exiting to IPv6 addresses; resumes being able
3820 to update our GeoIP database, and includes the geoip6 file this time;
3821 turns off the client-side DNS cache by default due to privacy risks;
3822 and fixes a variety of other issues.
3824 o Major features (client resilience):
3825 - Add a new "FallbackDir" torrc option to use when we can't use
3826 a directory mirror from the consensus (either because we lack a
3827 consensus, or because they're all down). Currently, all authorities
3828 are fallbacks by default, and there are no other default fallbacks,
3829 but that will change. This option will allow us to give clients a
3830 longer list of servers to try to get a consensus from when first
3831 connecting to the Tor network, and thereby reduce load on the
3832 directory authorities. Implements proposal 206, "Preconfigured
3833 directory sources for bootstrapping". We also removed the old
3834 "FallbackNetworkstatus" option, since we never got it working well
3835 enough to use it. Closes bug 572.
3836 - If we have no circuits open, use a relaxed timeout (the
3837 95-percentile cutoff) until a circuit succeeds. This heuristic
3838 should allow Tor to succeed at building circuits even when the
3839 network connection drastically changes. Should help with bug 3443.
3841 o Major features (IPv6):
3842 - Relays can now exit to IPv6 addresses: make sure that you have IPv6
3843 connectivity, then set the IPv6Exit flag to 1. Also make sure your
3844 exit policy reads as you would like: the address * applies to all
3845 address families, whereas *4 is IPv4 address only, and *6 is IPv6
3846 addresses only. On the client side, you'll need to wait until the
3847 authorities have upgraded, wait for enough exits to support IPv6,
3848 apply the "IPv6Traffic" flag to a SocksPort, and use Socks5. Closes
3849 ticket 5547, implements proposal 117 as revised in proposal 208.
3851 We DO NOT recommend that clients with actual anonymity needs start
3852 using IPv6 over Tor yet, since not enough exits support it yet.
3854 o Major features (geoip database):
3855 - Maxmind began labelling Tor relays as being in country "A1",
3856 which breaks by-country node selection inside Tor. Now we use a
3857 script to replace "A1" ("Anonymous Proxy") entries in our geoip
3858 file with real country codes. This script fixes about 90% of "A1"
3859 entries automatically and uses manual country code assignments to
3860 fix the remaining 10%. See src/config/README.geoip for details.
3861 Fixes bug 6266. Also update to the December 5 2012 Maxmind GeoLite
3862 Country database, as modified above.
3864 o Major bugfixes (client-side DNS):
3865 - Turn off the client-side DNS cache by default. Updating and using
3866 the DNS cache is now configurable on a per-client-port
3867 level. SOCKSPort, DNSPort, etc lines may now contain
3868 {No,}Cache{IPv4,IPv6,}DNS lines to indicate that we shouldn't
3869 cache these types of DNS answers when we receive them from an
3870 exit node in response to an application request on this port, and
3871 {No,}UseCached{IPv4,IPv6,DNS} lines to indicate that if we have
3872 cached DNS answers of these types, we shouldn't use them. It's
3873 potentially risky to use cached DNS answers at the client, since
3874 doing so can indicate to one exit what answers we've gotten
3875 for DNS lookups in the past. With IPv6, this becomes especially
3876 problematic. Using cached DNS answers for requests on the same
3877 circuit would present less linkability risk, since all traffic
3878 on a circuit is already linkable, but it would also provide
3879 little performance benefit: the exit node caches DNS replies
3880 too. Implements a simplified version of Proposal 205. Implements
3883 o Major bugfixes (other):
3884 - Alter circuit build timeout measurement to start at the point
3885 where we begin the CREATE/CREATE_FAST step (as opposed to circuit
3886 initialization). This should make our timeout measurements more
3887 uniform. Previously, we were sometimes including ORconn setup time
3888 in our circuit build time measurements. Should resolve bug 3443.
3889 - Fix an assertion that could trigger in hibernate_go_dormant() when
3890 closing an or_connection_t: call channel_mark_for_close() rather
3891 than connection_mark_for_close(). Fixes bug 7267. Bugfix on
3893 - Include the geoip6 IPv6 GeoIP database in the tarball. Fixes bug
3894 7655; bugfix on 0.2.4.6-alpha.
3897 - Add a new torrc option "ServerTransportListenAddr" to let bridge
3898 operators select the address where their pluggable transports will
3899 listen for connections. Resolves ticket 7013.
3900 - Allow an optional $ before the node identity digest in the
3901 controller command GETINFO ns/id/<identity>, for consistency with
3902 md/id/<identity> and desc/id/<identity>. Resolves ticket 7059.
3903 - Log packaged cell fullness as part of the heartbeat message.
3904 Diagnosis to try to determine the extent of bug 7743.
3906 o Minor features (IPv6):
3907 - AutomapHostsOnResolve now supports IPv6 addresses. By default, we
3908 prefer to hand out virtual IPv6 addresses, since there are more of
3909 them and we can't run out. To override this behavior and make IPv4
3910 addresses preferred, set NoPreferIPv6Automap on whatever SOCKSPort
3911 or DNSPort you're using for resolving. Implements ticket 7571.
3912 - AutomapHostsOnResolve responses are now randomized, to avoid
3913 annoying situations where Tor is restarted and applications
3914 connect to the wrong addresses.
3915 - Never try more than 1000 times to pick a new virtual address when
3916 AutomapHostsOnResolve is set. That's good enough so long as we
3917 aren't close to handing out our entire virtual address space;
3918 if you're getting there, it's best to switch to IPv6 virtual
3922 - The ADDRMAP command can no longer generate an ill-formed error
3923 code on a failed MAPADDRESS. It now says "internal" rather than
3924 an English sentence fragment with spaces in the middle. Bugfix on
3926 - Fix log messages and comments to avoid saying "GMT" when we mean
3927 "UTC". Fixes bug 6113.
3928 - Compile on win64 using mingw64. Fixes bug 7260; patches from
3930 - Fix a crash when debugging unit tests on Windows: deallocate a
3931 shared library with FreeLibrary, not CloseHandle. Fixes bug 7306;
3932 bugfix on 0.2.2.17-alpha. Reported by "ultramage".
3935 - The DirServer option is now DirAuthority, for consistency with
3936 current naming patterns. You can still use the old DirServer form.
3938 o Code simplification and refactoring:
3939 - Move the client-side address-map/virtual-address/DNS-cache code
3940 out of connection_edge.c into a new addressmap.c module.
3941 - Remove unused code for parsing v1 directories and "running routers"
3942 documents. Fixes bug 6887.
3945 Changes in version 0.2.3.25 - 2012-11-19
3946 The Tor 0.2.3 release series is dedicated to the memory of Len "rabbi"
3947 Sassaman (1980-2011), a long-time cypherpunk, anonymity researcher,
3948 Mixmaster maintainer, Pynchon Gate co-designer, CodeCon organizer,
3949 programmer, and friend. Unstinting in his dedication to the cause of
3950 freedom, he inspired and helped many of us as we began our work on
3951 anonymity, and inspires us still. Please honor his memory by writing
3952 software to protect people's freedoms, and by helping others to do so.
3954 Tor 0.2.3.25, the first stable release in the 0.2.3 branch, features
3955 significantly reduced directory overhead (via microdescriptors),
3956 enormous crypto performance improvements for fast relays on new
3957 enough hardware, a new v3 TLS handshake protocol that can better
3958 resist fingerprinting, support for protocol obfuscation plugins (aka
3959 pluggable transports), better scalability for hidden services, IPv6
3960 support for bridges, performance improvements like allowing clients
3961 to skip the first round-trip on the circuit ("optimistic data") and
3962 refilling token buckets more often, a new "stream isolation" design
3963 to isolate different applications on different circuits, and many
3964 stability, security, and privacy fixes.
3967 - Tor tries to wipe potentially sensitive data after using it, so
3968 that if some subsequent security failure exposes Tor's memory,
3969 the damage will be limited. But we had a bug where the compiler
3970 was eliminating these wipe operations when it decided that the
3971 memory was no longer visible to a (correctly running) program,
3972 hence defeating our attempt at defense in depth. We fix that
3973 by using OpenSSL's OPENSSL_cleanse() operation, which a compiler
3974 is unlikely to optimize away. Future versions of Tor may use
3975 a less ridiculously heavy approach for this. Fixes bug 7352.
3976 Reported in an article by Andrey Karpov.
3979 - Fix a harmless bug when opting against publishing a relay descriptor
3980 because DisableNetwork is set. Fixes bug 7464; bugfix on
3984 Changes in version 0.2.4.6-alpha - 2012-11-13
3985 Tor 0.2.4.6-alpha fixes an assert bug that has been plaguing relays,
3986 makes our defense-in-depth memory wiping more reliable, and begins to
3987 count IPv6 addresses in bridge statistics,
3990 - Fix an assertion failure that could occur when closing a connection
3991 with a spliced rendezvous circuit. Fix for bug 7212; bugfix on
3993 - Tor tries to wipe potentially sensitive data after using it, so
3994 that if some subsequent security failure exposes Tor's memory,
3995 the damage will be limited. But we had a bug where the compiler
3996 was eliminating these wipe operations when it decided that the
3997 memory was no longer visible to a (correctly running) program,
3998 hence defeating our attempt at defense in depth. We fix that
3999 by using OpenSSL's OPENSSL_cleanse() operation, which a compiler
4000 is unlikely to optimize away. Future versions of Tor may use
4001 a less ridiculously heavy approach for this. Fixes bug 7352.
4002 Reported in an article by Andrey Karpov.
4005 - Add GeoIP database for IPv6 addresses. The new config option
4007 - Bridge statistics now count bridge clients connecting over IPv6:
4008 bridge statistics files now list "bridge-ip-versions" and
4009 extra-info documents list "geoip6-db-digest". The control protocol
4010 "CLIENTS_SEEN" and "ip-to-country" queries now support IPv6. Initial
4011 implementation by "shkoo", addressing ticket 5055.
4014 - Warn when we are binding low ports when hibernation is enabled;
4015 previously we had warned when we were _advertising_ low ports with
4016 hibernation enabled. Fixes bug 7285; bugfix on 0.2.3.9-alpha.
4017 - Fix a harmless bug when opting against publishing a relay descriptor
4018 because DisableNetwork is set. Fixes bug 7464; bugfix on
4020 - Add warning message when a managed proxy dies during configuration.
4021 Fixes bug 7195; bugfix on 0.2.4.2-alpha.
4022 - Fix a linking error when building tor-fw-helper without miniupnp.
4023 Fixes bug 7235; bugfix on 0.2.4.2-alpha. Fix by Anthony G. Basile.
4024 - Check for closing an or_connection_t without going through correct
4025 channel functions; emit a warning and then call
4026 connection_or_close_for_error() so we don't assert as in bugs 7212
4028 - Compile correctly on compilers without C99 designated initializer
4029 support. Fixes bug 7286; bugfix on 0.2.4.4-alpha.
4030 - Avoid a possible assert that can occur when channel_send_destroy() is
4031 called on a channel in CHANNEL_STATE_CLOSING, CHANNEL_STATE_CLOSED,
4032 or CHANNEL_STATE_ERROR when the Tor process is resumed after being
4033 blocked for a long interval. Fixes bug 7350; bugfix on 0.2.4.4-alpha.
4034 - Fix a memory leak on failing cases of channel_tls_process_certs_cell.
4035 Fixes bug 7422; bugfix on 0.2.4.4-alpha.
4037 o Code simplification and refactoring:
4038 - Start using OpenBSD's implementation of queue.h, so that we don't
4039 need to hand-roll our own pointer and list structures whenever we
4040 need them. (We can't rely on a sys/queue.h, since some operating
4041 systems don't have them, and the ones that do have them don't all
4042 present the same extensions.)
4045 Changes in version 0.2.4.5-alpha - 2012-10-25
4046 Tor 0.2.4.5-alpha comes hard at the heels of 0.2.4.4-alpha, to fix
4047 two important security vulnerabilities that could lead to remotely
4048 triggerable relay crashes, fix a major bug that was preventing clients
4049 from choosing suitable exit nodes, and refactor some of our code.
4051 o Major bugfixes (security, also in 0.2.3.24-rc):
4052 - Fix a group of remotely triggerable assertion failures related to
4053 incorrect link protocol negotiation. Found, diagnosed, and fixed
4054 by "some guy from France". Fix for CVE-2012-2250; bugfix on
4056 - Fix a denial of service attack by which any directory authority
4057 could crash all the others, or by which a single v2 directory
4058 authority could crash everybody downloading v2 directory
4059 information. Fixes bug 7191; bugfix on 0.2.0.10-alpha.
4061 o Major bugfixes (also in 0.2.3.24-rc):
4062 - When parsing exit policy summaries from microdescriptors, we had
4063 previously been ignoring the last character in each one, so that
4064 "accept 80,443,8080" would be treated by clients as indicating
4065 a node that allows access to ports 80, 443, and 808. That would
4066 lead to clients attempting connections that could never work,
4067 and ignoring exit nodes that would support their connections. Now
4068 clients parse these exit policy summaries correctly. Fixes bug 7192;
4069 bugfix on 0.2.3.1-alpha.
4071 o Minor bugfixes (also in 0.2.3.24-rc):
4072 - Clients now consider the ClientRejectInternalAddresses config option
4073 when using a microdescriptor consensus stanza to decide whether
4074 an exit relay would allow exiting to an internal address. Fixes
4075 bug 7190; bugfix on 0.2.3.1-alpha.
4078 - Only disable TLS session ticket support when running as a TLS
4079 server. Now clients will blend better with regular Firefox
4080 connections. Fixes bug 7189; bugfix on Tor 0.2.3.23-rc.
4082 o Code simplification and refactoring:
4083 - Start using OpenBSD's implementation of queue.h (originally by
4085 - Move the entry node code from circuitbuild.c to its own file.
4086 - Move the circuit build timeout tracking code from circuitbuild.c
4090 Changes in version 0.2.3.24-rc - 2012-10-25
4091 Tor 0.2.3.24-rc fixes two important security vulnerabilities that
4092 could lead to remotely triggerable relay crashes, and fixes
4093 a major bug that was preventing clients from choosing suitable exit
4096 o Major bugfixes (security):
4097 - Fix a group of remotely triggerable assertion failures related to
4098 incorrect link protocol negotiation. Found, diagnosed, and fixed
4099 by "some guy from France". Fix for CVE-2012-2250; bugfix on
4101 - Fix a denial of service attack by which any directory authority
4102 could crash all the others, or by which a single v2 directory
4103 authority could crash everybody downloading v2 directory
4104 information. Fixes bug 7191; bugfix on 0.2.0.10-alpha.
4107 - When parsing exit policy summaries from microdescriptors, we had
4108 previously been ignoring the last character in each one, so that
4109 "accept 80,443,8080" would be treated by clients as indicating
4110 a node that allows access to ports 80, 443, and 808. That would
4111 lead to clients attempting connections that could never work,
4112 and ignoring exit nodes that would support their connections. Now
4113 clients parse these exit policy summaries correctly. Fixes bug 7192;
4114 bugfix on 0.2.3.1-alpha.
4117 - Clients now consider the ClientRejectInternalAddresses config option
4118 when using a microdescriptor consensus stanza to decide whether
4119 an exit relay would allow exiting to an internal address. Fixes
4120 bug 7190; bugfix on 0.2.3.1-alpha.
4123 Changes in version 0.2.4.4-alpha - 2012-10-20
4124 Tor 0.2.4.4-alpha adds a new v3 directory authority, fixes a privacy
4125 vulnerability introduced by a change in OpenSSL, fixes a remotely
4126 triggerable assert, and adds new channel_t and circuitmux_t abstractions
4127 that will make it easier to test new connection transport and cell
4128 scheduling algorithms.
4130 o New directory authorities (also in 0.2.3.23-rc):
4131 - Add Faravahar (run by Sina Rabbani) as the ninth v3 directory
4132 authority. Closes ticket 5749.
4134 o Major bugfixes (security/privacy, also in 0.2.3.23-rc):
4135 - Disable TLS session tickets. OpenSSL's implementation was giving
4136 our TLS session keys the lifetime of our TLS context objects, when
4137 perfect forward secrecy would want us to discard anything that
4138 could decrypt a link connection as soon as the link connection
4139 was closed. Fixes bug 7139; bugfix on all versions of Tor linked
4140 against OpenSSL 1.0.0 or later. Found by Florent Daignière.
4141 - Discard extraneous renegotiation attempts once the V3 link
4142 protocol has been initiated. Failure to do so left us open to
4143 a remotely triggerable assertion failure. Fixes CVE-2012-2249;
4144 bugfix on 0.2.3.6-alpha. Reported by "some guy from France".
4146 o Internal abstraction features:
4147 - Introduce new channel_t abstraction between circuits and
4148 or_connection_t to allow for implementing alternate OR-to-OR
4149 transports. A channel_t is an abstract object which can either be a
4150 cell-bearing channel, which is responsible for authenticating and
4151 handshaking with the remote OR and transmitting cells to and from
4152 it, or a listening channel, which spawns new cell-bearing channels
4153 at the request of remote ORs. Implements part of ticket 6465.
4154 - Also new is the channel_tls_t subclass of channel_t, adapting it
4155 to the existing or_connection_t code. The V2/V3 protocol handshaking
4156 code which formerly resided in command.c has been moved below the
4157 channel_t abstraction layer and may be found in channeltls.c now.
4158 Implements the rest of ticket 6465.
4159 - Introduce new circuitmux_t storing the queue of circuits for
4160 a channel; this encapsulates and abstracts the queue logic and
4161 circuit selection policy, and allows the latter to be overridden
4162 easily by switching out a policy object. The existing EWMA behavior
4163 is now implemented as a circuitmux_policy_t. Resolves ticket 6816.
4165 o Required libraries:
4166 - Tor now requires OpenSSL 0.9.8 or later. OpenSSL 1.0.0 or later is
4167 strongly recommended.
4170 - Warn users who run hidden services on a Tor client with
4171 UseEntryGuards disabled that their hidden services will be
4172 vulnerable to http://freehaven.net/anonbib/#hs-attack06 (the
4173 attack which motivated Tor to support entry guards in the first
4174 place). Resolves ticket 6889.
4175 - Tor now builds correctly on Bitrig, an OpenBSD fork. Patch from
4176 dhill. Resolves ticket 6982.
4177 - Option OutboundBindAddress can be specified multiple times and
4178 accepts IPv6 addresses. Resolves ticket 6876.
4180 o Minor bugfixes (also in 0.2.3.23-rc):
4181 - Don't serve or accept v2 hidden service descriptors over a
4182 relay's DirPort. It's never correct to do so, and disabling it
4183 might make it more annoying to exploit any bugs that turn up in the
4184 descriptor-parsing code. Fixes bug 7149.
4185 - Fix two cases in src/or/transports.c where we were calling
4186 fmt_addr() twice in a parameter list. Bug found by David
4187 Fifield. Fixes bug 7014; bugfix on 0.2.3.9-alpha.
4188 - Fix memory leaks whenever we logged any message about the "path
4189 bias" detection. Fixes bug 7022; bugfix on 0.2.3.21-rc.
4190 - When relays refuse a "create" cell because their queue of pending
4191 create cells is too big (typically because their cpu can't keep up
4192 with the arrival rate), send back reason "resource limit" rather
4193 than reason "internal", so network measurement scripts can get a
4194 more accurate picture. Fixes bug 7037; bugfix on 0.1.1.11-alpha.
4197 - Command-line option "--version" implies "--quiet". Fixes bug 6997.
4198 - Free some more still-in-use memory at exit, to make hunting for
4199 memory leaks easier. Resolves bug 7029.
4200 - When a Tor client gets a "truncated" relay cell, the first byte of
4201 its payload specifies why the circuit was truncated. We were
4202 ignoring this 'reason' byte when tearing down the circuit, resulting
4203 in the controller not being told why the circuit closed. Now we
4204 pass the reason from the truncated cell to the controller. Bugfix
4205 on 0.1.2.3-alpha; fixes bug 7039.
4206 - Downgrade "Failed to hand off onionskin" messages to "debug"
4207 severity, since they're typically redundant with the "Your computer
4208 is too slow" messages. Fixes bug 7038; bugfix on 0.2.2.16-alpha.
4209 - Make clients running with IPv6 bridges connect over IPv6 again,
4210 even without setting new config options ClientUseIPv6 and
4211 ClientPreferIPv6ORPort. Fixes bug 6757; bugfix on 0.2.4.1-alpha.
4212 - Use square brackets around IPv6 addresses in numerous places
4213 that needed them, including log messages, HTTPS CONNECT proxy
4214 requests, TransportProxy statefile entries, and pluggable transport
4215 extra-info lines. Fixes bug 7011; patch by David Fifield.
4217 o Code refactoring and cleanup:
4218 - Source files taken from other packages now reside in src/ext;
4219 previously they were scattered around the rest of Tor.
4220 - Avoid use of reserved identifiers in our C code. The C standard
4221 doesn't like us declaring anything that starts with an
4222 underscore, so let's knock it off before we get in trouble. Fix
4223 for bug 1031; bugfix on the first Tor commit.
4226 Changes in version 0.2.3.23-rc - 2012-10-20
4227 Tor 0.2.3.23-rc adds a new v3 directory authority, fixes a privacy
4228 vulnerability introduced by a change in OpenSSL, and fixes a variety
4229 of smaller bugs in preparation for the release.
4231 o New directory authorities:
4232 - Add Faravahar (run by Sina Rabbani) as the ninth v3 directory
4233 authority. Closes ticket 5749.
4235 o Major bugfixes (security/privacy):
4236 - Disable TLS session tickets. OpenSSL's implementation was giving
4237 our TLS session keys the lifetime of our TLS context objects, when
4238 perfect forward secrecy would want us to discard anything that
4239 could decrypt a link connection as soon as the link connection
4240 was closed. Fixes bug 7139; bugfix on all versions of Tor linked
4241 against OpenSSL 1.0.0 or later. Found by Florent Daignière.
4242 - Discard extraneous renegotiation attempts once the V3 link
4243 protocol has been initiated. Failure to do so left us open to
4244 a remotely triggerable assertion failure. Fixes CVE-2012-2249;
4245 bugfix on 0.2.3.6-alpha. Reported by "some guy from France".
4248 - Fix a possible crash bug when checking for deactivated circuits
4249 in connection_or_flush_from_first_active_circuit(). Fixes bug 6341;
4250 bugfix on 0.2.2.7-alpha. Bug report and fix received pseudonymously.
4252 o Minor bugfixes (on 0.2.3.x):
4253 - Fix two cases in src/or/transports.c where we were calling
4254 fmt_addr() twice in a parameter list. Bug found by David
4255 Fifield. Fixes bug 7014; bugfix on 0.2.3.9-alpha.
4256 - Convert an assert in the pathbias code to a log message. The assert
4257 appears to only be triggerable by Tor2Web mode. Fixes bug 6866;
4258 bugfix on 0.2.3.17-beta.
4259 - Fix memory leaks whenever we logged any message about the "path
4260 bias" detection. Fixes bug 7022; bugfix on 0.2.3.21-rc.
4262 o Minor bugfixes (on 0.2.2.x and earlier):
4263 - Don't serve or accept v2 hidden service descriptors over a relay's
4264 DirPort. It's never correct to do so, and disabling it might
4265 make it more annoying to exploit any bugs that turn up in the
4266 descriptor-parsing code. Fixes bug 7149.
4267 - When relays refuse a "create" cell because their queue of pending
4268 create cells is too big (typically because their cpu can't keep up
4269 with the arrival rate), send back reason "resource limit" rather
4270 than reason "internal", so network measurement scripts can get a
4271 more accurate picture. Bugfix on 0.1.1.11-alpha; fixes bug 7037.
4272 - Correct file sizes when reading binary files on Cygwin, to avoid
4273 a bug where Tor would fail to read its state file. Fixes bug 6844;
4274 bugfix on 0.1.2.7-alpha.
4275 - Avoid undefined behaviour when parsing the list of supported
4276 rendezvous/introduction protocols in a hidden service descriptor.
4277 Previously, Tor would have confused (as-yet-unused) protocol version
4278 numbers greater than 32 with lower ones on many platforms. Fixes
4279 bug 6827; bugfix on 0.2.0.10-alpha. Found by George Kadianakis.
4281 o Documentation fixes:
4282 - Clarify that hidden services are TCP only. Fixes bug 6024.
4285 Changes in version 0.2.4.3-alpha - 2012-09-22
4286 Tor 0.2.4.3-alpha fixes another opportunity for a remotely triggerable
4287 assertion, resumes letting relays test reachability of their DirPort,
4288 and cleans up a bunch of smaller bugs.
4291 - Fix an assertion failure in tor_timegm() that could be triggered
4292 by a badly formatted directory object. Bug found by fuzzing with
4293 Radamsa. Fixes bug 6811; bugfix on 0.2.0.20-rc.
4296 - Fix a possible crash bug when checking for deactivated circuits
4297 in connection_or_flush_from_first_active_circuit(). Fixes bug 6341;
4298 bugfix on 0.2.2.7-alpha. Bug report and fix received pseudonymously.
4299 - Allow routers to detect that their own DirPorts are running. When
4300 we removed support for versions_supports_begindir, we also
4301 accidentally removed the mechanism we used to self-test our
4302 DirPort. Diagnosed with help from kargig. Fixes bugs 6814 and 6815;
4303 bugfix on 0.2.4.2-alpha.
4305 o Security features:
4306 - Switch to a completely time-invariant approach for picking nodes
4307 weighted by bandwidth. Our old approach would run through the
4308 part of the loop after it had made its choice slightly slower
4309 than it ran through the part of the loop before it had made its
4310 choice. Addresses ticket 6538.
4311 - Disable the use of Guard nodes when in Tor2WebMode. Guard usage
4312 by tor2web clients allows hidden services to identify tor2web
4313 clients through their repeated selection of the same rendezvous
4314 and introduction point circuit endpoints (their guards). Resolves
4318 - Enable Tor to read configuration, state, and key information from
4319 a FIFO. Previously Tor would only read from files with a positive
4320 stat.st_size. Code from meejah; fixes bug 6044.
4323 - Correct file sizes when reading binary files on Cygwin, to avoid
4324 a bug where Tor would fail to read its state file. Fixes bug 6844;
4325 bugfix on 0.1.2.7-alpha.
4326 - Correctly handle votes with more than 31 flags. Fixes bug 6853;
4327 bugfix on 0.2.0.3-alpha.
4328 - When complaining about a client port on a public address, log
4329 which address we're complaining about. Fixes bug 4020; bugfix on
4330 0.2.3.3-alpha. Patch by Tom Fitzhenry.
4331 - Convert an assert in the pathbias code to a log message. The assert
4332 appears to only be triggerable by Tor2Web mode. Fixes bug 6866;
4333 bugfix on 0.2.3.17-beta.
4334 - Our new buildsystem was overzealous about rebuilding manpages: it
4335 would rebuild them all whenever any one of them changed. Now our
4336 dependency checking should be correct. Fixes bug 6843; bugfix on
4338 - Don't do reachability testing over IPv6 unless AuthDirPublishIPv6
4339 is set. Fixes bug 6880. Bugfix on 0.2.4.1-alpha.
4340 - Correct log printout about which address family is preferred
4341 when connecting to a bridge with both an IPv4 and IPv6 OR port.
4342 Fixes bug 6884; bugfix on 0.2.4.1-alpha.
4344 o Minor bugfixes (code cleanliness):
4345 - Fix round_to_power_of_2() so it doesn't invoke undefined behavior
4346 with large values. This situation was untriggered, but nevertheless
4347 incorrect. Fixes bug 6831; bugfix on 0.2.0.1-alpha.
4348 - Reject consensus votes with more than 64 known-flags. We aren't even
4349 close to that limit yet, and our code doesn't handle it correctly.
4350 Fixes bug 6833; bugfix on 0.2.0.1-alpha.
4351 - Avoid undefined behaviour when parsing the list of supported
4352 rendezvous/introduction protocols in a hidden service descriptor.
4353 Previously, Tor would have confused (as-yet-unused) protocol version
4354 numbers greater than 32 with lower ones on many platforms. Fixes
4355 bug 6827; bugfix on 0.2.0.10-alpha. Found by George Kadianakis.
4356 - Fix handling of rendezvous client authorization types over 8.
4357 Fixes bug 6861; bugfix on 0.2.1.5-alpha.
4358 - Fix building with older versions of GCC (2.95, for one) that don't
4359 like preprocessor directives inside macro arguments. Found by
4360 grarpamp. Fixes bug 6842; bugfix on 0.2.4.2-alpha.
4361 - Switch weighted node selection rule from using a list of doubles
4362 to using a list of int64_t. This change should make the process
4363 slightly easier to debug and maintain. Needed to finish ticket 6538.
4365 o Code simplification and refactoring:
4366 - Move the generic "config" code into a new file, and have "config.c"
4367 hold only torrc- and state-related code. Resolves ticket 6823.
4368 - Move the core of our "choose a weighted element at random" logic
4369 into its own function, and give it unit tests. Now the logic is
4370 testable, and a little less fragile too.
4371 - Removed the testing_since field of node_t, which hasn't been used
4372 for anything since 0.2.0.9-alpha.
4374 o Documentation fixes:
4375 - Clarify that hidden services are TCP only. Fixes bug 6024.
4376 - Resolve a typo in torrc.sample.in. Fixes bug 6819; bugfix on
4380 Changes in version 0.2.3.22-rc - 2012-09-11
4381 Tor 0.2.3.22-rc fixes another opportunity for a remotely triggerable
4385 - Fix an assertion failure in tor_timegm() that could be triggered
4386 by a badly formatted directory object. Bug found by fuzzing with
4387 Radamsa. Fixes bug 6811; bugfix on 0.2.0.20-rc.
4390 - Avoid segfault when starting up having run with an extremely old
4391 version of Tor and parsing its state file. Fixes bug 6801; bugfix
4395 Changes in version 0.2.2.39 - 2012-09-11
4396 Tor 0.2.2.39 fixes two more opportunities for remotely triggerable
4400 - Fix an assertion failure in tor_timegm() that could be triggered
4401 by a badly formatted directory object. Bug found by fuzzing with
4402 Radamsa. Fixes bug 6811; bugfix on 0.2.0.20-rc.
4403 - Do not crash when comparing an address with port value 0 to an
4404 address policy. This bug could have been used to cause a remote
4405 assertion failure by or against directory authorities, or to
4406 allow some applications to crash clients. Fixes bug 6690; bugfix
4410 Changes in version 0.2.4.2-alpha - 2012-09-10
4411 Tor 0.2.4.2-alpha enables port forwarding for pluggable transports,
4412 raises the default rate limiting even more, and makes the bootstrapping
4413 log messages less noisy.
4416 - Automatically forward the TCP ports of pluggable transport
4417 proxies using tor-fw-helper if PortForwarding is enabled. Implements
4421 - Raise the default BandwidthRate/BandwidthBurst values from 5MB/10MB
4422 to 1GB/1GB. The previous defaults were intended to be "basically
4423 infinite", but it turns out they're now limiting our 100mbit+
4424 relays and bridges. Fixes bug 6605; bugfix on 0.2.0.10-alpha (the
4425 last time we raised it).
4428 - Detect when we're running with a version of OpenSSL other than the
4429 one we compiled with. This has occasionally given people hard-to-
4431 - Log fewer lines at level "notice" about our OpenSSL and Libevent
4432 versions and capabilities when everything is going right. Resolves
4433 part of ticket 6736.
4434 - Directory authorities no long accept descriptors for any version of
4435 Tor before 0.2.2.35, or for any 0.2.3 release before 0.2.3.10-alpha.
4436 These versions are insecure, unsupported, or both. Implements
4440 - Rename the (internal-use-only) UsingTestingNetworkDefaults option
4441 to start with a triple-underscore so the controller won't touch it.
4442 Patch by Meejah. Fixes bug 3155. Bugfix on 0.2.2.23-alpha.
4443 - Avoid segfault when starting up having run with an extremely old
4444 version of Tor and parsing its state file. Fixes bug 6801; bugfix
4446 - Rename the (testing-use-only) _UseFilteringSSLBufferevents option
4447 so it doesn't start with _. Fixes bug 3155. Bugfix on 0.2.3.1-alpha.
4448 - Don't follow the NULL pointer if microdescriptor generation fails.
4449 (This does not appear to be triggerable, but it's best to be safe.)
4450 Found by "f. tp.". Fixes bug 6797; bugfix on 0.2.4.1-alpha.
4451 - Fix mis-declared dependencies on src/common/crypto.c and
4452 src/or/tor_main.c that could break out-of-tree builds under some
4453 circumstances. Fixes bug 6778; bugfix on 0.2.4.1-alpha.
4454 - Avoid a warning when building common_sha1.i out of tree. Fixes bug
4455 6778; bugfix on 0.2.4.1-alpha.
4456 - Fix a harmless (in this case) build warning for implicitly
4457 converting a strlen() to an int. Bugfix on 0.2.4.1-alpha.
4460 - Now that all versions before 0.2.2.x are disallowed, we no longer
4461 need to work around their missing features. Thus we can remove a
4462 bunch of compatibility code.
4465 - Tweak tor-fw-helper to accept an arbitrary amount of arbitrary
4466 TCP ports to forward. In the past it only accepted two ports:
4467 the ORPort and the DirPort.
4470 Changes in version 0.2.4.1-alpha - 2012-09-05
4471 Tor 0.2.4.1-alpha lets bridges publish their pluggable transports to
4472 bridgedb; lets relays use IPv6 addresses and directory authorities
4473 advertise them; and switches to a cleaner build interface.
4475 This is the first alpha release in a new series, so expect there to
4476 be bugs. Users who would rather test out a more stable branch should
4477 stay with 0.2.3.x for now.
4479 o Major features (bridges):
4480 - Bridges now report the pluggable transports they support to the
4481 bridge authority, so it can pass the supported transports on to
4482 bridgedb and/or eventually do reachability testing. Implements
4485 o Major features (IPv6):
4486 - Bridge authorities now accept IPv6 bridge addresses and include
4487 them in network status documents. Implements ticket 5534.
4488 - Clients who set "ClientUseIPv6 1" may connect to entry nodes over
4489 IPv6. Set "ClientPreferIPv6ORPort 1" to make this even more likely
4490 to happen. Implements ticket 5535.
4491 - All kind of relays, not just bridges, can now advertise an IPv6
4492 OR port. Implements ticket 6362.
4493 - Directory authorities vote on IPv6 OR ports using the new consensus
4494 method 14. Implements ticket 6363.
4496 o Major features (build):
4497 - Switch to a nonrecursive Makefile structure. Now instead of each
4498 Makefile.am invoking other Makefile.am's, there is a master
4499 Makefile.am that includes the others. This change makes our build
4500 process slightly more maintainable, and improves parallelism for
4501 building with make -j. Original patch by Stewart Smith; various
4502 fixes by Jim Meyering.
4503 - Where available, we now use automake's "silent" make rules by
4504 default, so that warnings are easier to spot. You can get the old
4505 behavior with "make V=1". Patch by Stewart Smith for ticket 6522.
4507 o Minor features (code security and spec conformance):
4508 - Clear keys and key-derived material left on the stack in
4509 rendservice.c and rendclient.c. Check return value of
4510 crypto_pk_write_private_key_to_string() in rend_service_load_keys().
4511 These fixes should make us more forward-secure against cold-boot
4512 attacks and the like. Fixes bug 2385.
4513 - Reject EXTEND cells sent to nonexistent streams. According to the
4514 spec, an EXTEND cell sent to _any_ nonzero stream ID is invalid, but
4515 we were only checking for stream IDs that were currently in use.
4516 Found while hunting for more instances of bug 6271. Bugfix on
4517 0.0.2pre8, which introduced incremental circuit construction.
4519 o Minor features (streamlining);
4520 - No longer include the "opt" prefix when generating routerinfos
4521 or v2 directories: it has been needless since Tor 0.1.2. Closes
4523 - Remove some now-needless code that tried to aggressively flush
4524 OR connections as data was added to them. Since 0.2.0.1-alpha, our
4525 cell queue logic has saved us from the failure mode that this code
4526 was supposed to prevent. Removing this code will limit the number
4527 of baroque control flow paths through Tor's network logic. Reported
4528 pseudonymously on IRC. Fixes bug 6468; bugfix on 0.2.0.1-alpha.
4530 o Minor features (controller):
4531 - Add a "GETINFO signal/names" control port command. Implements
4533 - Provide default values for all options via "GETINFO config/defaults".
4534 Implements ticket 4971.
4536 o Minor features (IPv6):
4537 - New config option "AuthDirHasIPv6Connectivity 1" that directory
4538 authorities should set if they have IPv6 connectivity and want to
4539 do reachability tests for IPv6 relays. Implements feature 5974.
4540 - A relay with an IPv6 OR port now sends that address in NETINFO
4541 cells (in addition to its other address). Implements ticket 6364.
4543 o Minor features (log messages):
4544 - Omit the first heartbeat log message, because it never has anything
4545 useful to say, and it clutters up the bootstrapping messages.
4546 Resolves ticket 6758.
4547 - Don't log about reloading the microdescriptor cache at startup. Our
4548 bootstrap warnings are supposed to tell the user when there's a
4549 problem, and our bootstrap notices say when there isn't. Resolves
4550 ticket 6759; bugfix on 0.2.2.6-alpha.
4551 - Don't log "I learned some more directory information" when we're
4552 reading cached directory information. Reserve it for when new
4553 directory information arrives in response to a fetch. Resolves
4555 - Prevent rounding error in path bias counts when scaling
4556 them down, and use the correct scale factor default. Also demote
4557 some path bias related log messages down a level and make others
4558 less scary sounding. Fixes bug 6647. Bugfix against 0.2.3.17-beta.
4559 - We no longer warn so much when generating manpages from their
4562 o Code simplifications and refactoring:
4563 - Enhance our internal sscanf replacement so that we can eliminate
4564 the last remaining uses of the system sscanf. (Though those uses
4565 of sscanf were safe, sscanf itself is generally error prone, so
4566 we want to eliminate when we can.) Fixes ticket 4195 and Coverity
4568 - Move ipv6_preferred from routerinfo_t to node_t. Addresses bug 4620.
4569 - Move last_reachable and testing_since from routerinfo_t to node_t.
4570 Implements ticket 5529.
4571 - Add replaycache_t structure, functions and unit tests, then refactor
4572 rend_service_introduce() to be more clear to read, improve, debug,
4573 and test. Resolves bug 6177.
4574 - Finally remove support for malloc_good_size and malloc_usable_size.
4575 We had hoped that these functions would let us eke a little more
4576 memory out of our malloc implementation. Unfortunately, the only
4577 implementations that provided these functions are also ones that
4578 are already efficient about not overallocation: they never got us
4579 more than 7 or so bytes per allocation. Removing them saves us a
4580 little code complexity and a nontrivial amount of build complexity.
4583 - Tor maintainers now require Automake version 1.9 or later to build
4584 Tor from the Git repository. (Automake is not required when building
4585 from a source distribution.)
4588 Changes in version 0.2.3.21-rc - 2012-09-05
4589 Tor 0.2.3.21-rc is the fourth release candidate for the Tor 0.2.3.x
4590 series. It fixes a trio of potential security bugs, fixes a bug where
4591 we were leaving some of the fast relays out of the microdescriptor
4592 consensus, resumes interpreting "ORPort 0" and "DirPort 0" correctly,
4593 and cleans up other smaller issues.
4595 o Major bugfixes (security):
4596 - Tear down the circuit if we get an unexpected SENDME cell. Clients
4597 could use this trick to make their circuits receive cells faster
4598 than our flow control would have allowed, or to gum up the network,
4599 or possibly to do targeted memory denial-of-service attacks on
4600 entry nodes. Fixes bug 6252. Bugfix on the 54th commit on Tor --
4601 from July 2002, before the release of Tor 0.0.0. We had committed
4602 this patch previously, but we had to revert it because of bug 6271.
4603 Now that 6271 is fixed, this patch appears to work.
4604 - Reject any attempt to extend to an internal address. Without
4605 this fix, a router could be used to probe addresses on an internal
4606 network to see whether they were accepting connections. Fixes bug
4607 6710; bugfix on 0.0.8pre1.
4608 - Do not crash when comparing an address with port value 0 to an
4609 address policy. This bug could have been used to cause a remote
4610 assertion failure by or against directory authorities, or to
4611 allow some applications to crash clients. Fixes bug 6690; bugfix
4615 - Remove the upper bound on microdescriptor length. We were hitting
4616 the limit for routers with complex exit policies or family
4617 declarations, causing clients to not use them. Fixes the first
4618 piece of bug 6404; fix on 0.2.2.6-alpha.
4619 - Detect "ORPort 0" as meaning, uniformly, that we're not running
4620 as a relay. Previously, some of our code would treat the presence
4621 of any ORPort line as meaning that we should act like a relay,
4622 even though our new listener code would correctly not open any
4623 ORPorts for ORPort 0. Similar bugs in other Port options are also
4624 fixed. Fixes the first half of bug 6507; bugfix on 0.2.3.3-alpha.
4627 - Avoid a pair of double-free and use-after-mark bugs that can
4628 occur with certain timings in canceled and re-received DNS
4629 requests. Fixes bug 6472; bugfix on 0.0.7rc1.
4630 - Fix build and 64-bit compile warnings from --enable-openbsd-malloc.
4631 Fixes bug 6379. Bugfix on 0.2.0.20-rc.
4632 - Allow one-hop directory fetching circuits the full "circuit build
4633 timeout" period, rather than just half of it, before failing them
4634 and marking the relay down. This fix should help reduce cases where
4635 clients declare relays (or worse, bridges) unreachable because
4636 the TLS handshake takes a few seconds to complete. Fixes bug 6743;
4637 bugfix on 0.2.2.2-alpha, where we changed the timeout from a static
4639 - Authorities no longer include any router in their microdescriptor
4640 consensuses for which they couldn't generate or agree on a
4641 microdescriptor. Fixes the second piece of bug 6404; fix on
4643 - Detect and reject attempts to specify both "FooPort" and
4644 "FooPort 0" in the same configuration domain. (It's still okay
4645 to have a FooPort in your configuration file, and use "FooPort 0"
4646 on the command line to disable it.) Fixes the second half of bug
4647 6507; bugfix on 0.2.3.3-alpha.
4648 - Make wildcarded addresses (that is, ones beginning with "*.") work
4649 when provided via the controller's MapAddress command. Previously,
4650 they were accepted, but we never actually noticed that they were
4651 wildcards. Fixes bug 6244; bugfix on 0.2.3.9-alpha.
4652 - Avoid crashing on a malformed state file where EntryGuardPathBias
4653 precedes EntryGuard. Fix for bug 6774; bugfix on 0.2.3.17-beta.
4654 - Add a (probably redundant) memory clear between iterations of
4655 the router status voting loop, to prevent future coding errors
4656 where data might leak between iterations of the loop. Resolves
4659 o Minor bugfixes (log messages):
4660 - Downgrade "set buildtimeout to low value" messages to "info"
4661 severity; they were never an actual problem, there was never
4662 anything reasonable to do about them, and they tended to spam logs
4663 from time to time. Fixes bug 6251; bugfix on 0.2.2.2-alpha.
4664 - Downgrade path-bias warning messages to "info". We'll try to get
4665 them working better in 0.2.4. Add internal circuit construction
4666 state to protect against the noisy warn message "Unexpectedly high
4667 circuit_successes". Also add some additional rate-limited notice
4668 messages to help determine the root cause of the warn. Fixes bug
4669 6475. Bugfix against 0.2.3.17-beta.
4670 - Move log message when unable to find a microdesc in a routerstatus
4671 entry to parse time. Previously we'd spam this warning every time
4672 we tried to figure out which microdescriptors to download. Fixes
4673 the third piece of bug 6404; fix on 0.2.3.18-rc.
4676 - Consider new, removed or changed IPv6 OR ports a non-cosmetic
4677 change when the authority is deciding whether to accept a newly
4678 uploaded descriptor. Implements ticket 6423.
4679 - Add missing documentation for consensus and microdesc files.
4680 Resolves ticket 6732.
4683 Changes in version 0.2.2.38 - 2012-08-12
4684 Tor 0.2.2.38 fixes a remotely triggerable crash bug, and fixes a timing
4685 attack that could in theory leak path information.
4688 - Avoid an uninitialized memory read when reading a vote or consensus
4689 document that has an unrecognized flavor name. This read could
4690 lead to a remote crash bug. Fixes bug 6530; bugfix on 0.2.2.6-alpha.
4691 - Try to leak less information about what relays a client is
4692 choosing to a side-channel attacker. Previously, a Tor client would
4693 stop iterating through the list of available relays as soon as it
4694 had chosen one, thus finishing a little earlier when it picked
4695 a router earlier in the list. If an attacker can recover this
4696 timing information (nontrivial but not proven to be impossible),
4697 they could learn some coarse-grained information about which relays
4698 a client was picking (middle nodes in particular are likelier to
4699 be affected than exits). The timing attack might be mitigated by
4700 other factors (see bug 6537 for some discussion), but it's best
4701 not to take chances. Fixes bug 6537; bugfix on 0.0.8rc1.
4704 Changes in version 0.2.3.20-rc - 2012-08-05
4705 Tor 0.2.3.20-rc is the third release candidate for the Tor 0.2.3.x
4706 series. It fixes a pair of code security bugs and a potential anonymity
4707 issue, updates our RPM spec files, and cleans up other smaller issues.
4710 - Avoid read-from-freed-memory and double-free bugs that could occur
4711 when a DNS request fails while launching it. Fixes bug 6480;
4712 bugfix on 0.2.0.1-alpha.
4713 - Avoid an uninitialized memory read when reading a vote or consensus
4714 document that has an unrecognized flavor name. This read could
4715 lead to a remote crash bug. Fixes bug 6530; bugfix on 0.2.2.6-alpha.
4716 - Try to leak less information about what relays a client is
4717 choosing to a side-channel attacker. Previously, a Tor client would
4718 stop iterating through the list of available relays as soon as it
4719 had chosen one, thus finishing a little earlier when it picked
4720 a router earlier in the list. If an attacker can recover this
4721 timing information (nontrivial but not proven to be impossible),
4722 they could learn some coarse-grained information about which relays
4723 a client was picking (middle nodes in particular are likelier to
4724 be affected than exits). The timing attack might be mitigated by
4725 other factors (see bug 6537 for some discussion), but it's best
4726 not to take chances. Fixes bug 6537; bugfix on 0.0.8rc1.
4729 - Try to make the warning when giving an obsolete SOCKSListenAddress
4730 a little more useful.
4731 - Terminate active server managed proxies if Tor stops being a
4732 relay. Addresses parts of bug 6274; bugfix on 0.2.3.6-alpha.
4733 - Provide a better error message about possible OSX Asciidoc failure
4734 reasons. Fixes bug 6436.
4735 - Warn when Tor is configured to use accounting in a way that can
4736 link a hidden service to some other hidden service or public
4737 address. Resolves ticket 6490.
4740 - Check return value of fputs() when writing authority certificate
4741 file. Fixes Coverity issue 709056; bugfix on 0.2.0.1-alpha.
4742 - Ignore ServerTransportPlugin lines when Tor is not configured as
4743 a relay. Fixes bug 6274; bugfix on 0.2.3.6-alpha.
4744 - When disabling guards for having too high a proportion of failed
4745 circuits, make sure to look at each guard. Fixes bug 6397; bugfix
4749 - Update our default RPM spec files to work with mock and rpmbuild
4750 on RHEL/Fedora. They have an updated set of dependencies and
4751 conflicts, a fix for an ancient typo when creating the "_tor"
4752 user, and better instructions. Thanks to Ondrej Mikle for the
4753 patch series. Fixes bug 6043.
4756 - Make it possible to set the TestingTorNetwork configuration
4757 option using AlternateDirAuthority and AlternateBridgeAuthority
4758 as an alternative to setting DirServer. Addresses ticket 6377.
4761 - Clarify the documentation for the Alternate*Authority options.
4763 - Fix some typos in the manpages. Patch from A. Costa. Fixes bug 6500.
4765 o Code simplification and refactoring:
4766 - Do not use SMARTLIST_FOREACH for any loop whose body exceeds
4767 10 lines. Also, don't nest them. Doing so in the past has
4768 led to hard-to-debug code. The new style is to use the
4769 SMARTLIST_FOREACH_{BEGIN,END} pair. Addresses issue 6400.
4772 Changes in version 0.2.3.19-rc - 2012-07-06
4773 Tor 0.2.3.19-rc is the second release candidate for the Tor 0.2.3.x
4774 series. It fixes the compile on Windows, reverts to a GeoIP database
4775 that isn't as broken, and fixes a flow control bug that has been around
4776 since the beginning of Tor.
4779 - Fix a bug handling SENDME cells on nonexistent streams that could
4780 result in bizarre window values. Report and patch contributed
4781 pseudonymously. Fixes part of bug 6271. This bug was introduced
4782 before the first Tor release, in svn commit r152.
4783 - Revert to the May 1 2012 Maxmind GeoLite Country database. In the
4784 June 2012 database, Maxmind marked many Tor relays as country "A1",
4785 which will cause risky behavior for clients that set EntryNodes
4786 or ExitNodes. Addresses bug 6334; bugfix on 0.2.3.17-beta.
4787 - Instead of ENOBUFS on Windows, say WSAENOBUFS. Fixes compilation
4788 on Windows. Fixes bug 6296; bugfix on 0.2.3.18-rc.
4791 - Fix wrong TCP port range in parse_port_range(). Fixes bug 6218;
4792 bugfix on 0.2.1.10-alpha.
4795 Changes in version 0.2.3.18-rc - 2012-06-28
4796 Tor 0.2.3.18-rc is the first release candidate for the Tor 0.2.3.x
4797 series. It fixes a few smaller bugs, but generally appears stable.
4798 Please test it and let us know whether it is!
4801 - Allow wildcarded mapaddress targets to be specified on the
4802 controlport. Partially fixes bug 6244; bugfix on 0.2.3.9-alpha.
4803 - Make our linker option detection code more robust against linkers
4804 such as on FreeBSD 8, where a bad combination of options completes
4805 successfully but makes an unrunnable binary. Fixes bug 6173;
4806 bugfix on 0.2.3.17-beta.
4808 o Minor bugfixes (on 0.2.2.x and earlier):
4809 - Avoid a false positive in the util/threads unit test by increasing
4810 the maximum timeout time. Fixes bug 6227; bugfix on 0.2.0.4-alpha.
4811 - Replace "Sending publish request" log messages with "Launching
4812 upload", so that they no longer confusingly imply that we're
4813 sending something to a directory we might not even be connected
4814 to yet. Fixes bug 3311; bugfix on 0.2.0.10-alpha.
4815 - Make sure to set *socket_error in all error cases in
4816 connection_connect(), so it can't produce a warning about
4817 errno being zero from errno_to_orconn_end_reason(). Bugfix on
4818 0.2.1.1-alpha; resolves ticket 6028.
4819 - Downgrade "Got a certificate, but we already have it" log messages
4820 from warning to info, except when we're a dirauth. Fixes bug 5238;
4821 bugfix on 0.2.1.7-alpha.
4822 - When checking for requested signatures on the latest consensus
4823 before serving it to a client, make sure to check the right
4824 consensus flavor. Bugfix on 0.2.2.6-alpha.
4825 - Downgrade "eventdns rejected address" message to LOG_PROTOCOL_WARN.
4826 Fixes bug 5932; bugfix on 0.2.2.7-alpha.
4828 o Minor bugfixes (on 0.2.3.x):
4829 - Make format_helper_exit_status() avoid unnecessary space padding
4830 and stop confusing log_from_pipe(). Fixes ticket 5557; bugfix
4832 - Downgrade a message about cleaning the microdescriptor cache to
4833 "info" from "notice". Fixes bug 6238; bugfix on 0.2.3.1-alpha.
4834 - Log a BUG message at severity INFO if we have a networkstatus with
4835 a missing entry for some microdescriptor. Continues on a patch
4837 - Improve the log message when a managed proxy fails to launch. Fixes
4838 bug 5099; bugfix on 0.2.3.6-alpha.
4839 - Don't do DNS lookups when parsing corrupted managed proxy protocol
4840 messages. Fixes bug 6226; bugfix on 0.2.3.6-alpha.
4841 - When formatting wildcarded address mappings for the controller,
4842 be sure to include "*." as appropriate. Partially fixes bug 6244;
4843 bugfix on 0.2.3.9-alpha.
4844 - Avoid a warning caused by using strcspn() from glibc with clang 3.0.
4845 Bugfix on 0.2.3.13-alpha.
4846 - Stop logging messages about running with circuit timeout learning
4847 enabled at severity LD_BUG. Fixes bug 6169; bugfix on 0.2.3.17-beta.
4848 - Disable a spurious warning about reading on a marked and flushing
4849 connection. We shouldn't be doing that, but apparently we
4850 sometimes do. Fixes bug 6203; bugfix on 0.2.3.17-beta.
4851 - Fix a bug that stopped AllowDotExit from working on addresses
4852 that had an entry in the DNS cache. Fixes bug 6211; bugfix on
4855 o Code simplification, refactoring, unit tests:
4856 - Move tor_gettimeofday_cached() into compat_libevent.c, and use
4857 Libevent's notion of cached time when possible.
4858 - Remove duplicate code for invoking getrlimit() from control.c.
4859 - Add a unit test for the environment_variable_names_equal function.
4862 - Document the --defaults-torrc option, and the new (in 0.2.3)
4863 semantics for overriding, extending, and clearing lists of
4864 options. Closes bug 4748.
4867 Changes in version 0.2.3.17-beta - 2012-06-15
4868 Tor 0.2.3.17-beta enables compiler and linker hardening by default,
4869 gets our TLS handshake back on track for being able to blend in with
4870 Firefox, fixes a big bug in 0.2.3.16-alpha that broke Tor's interaction
4871 with Vidalia, and otherwise continues to get us closer to a release
4875 - Enable gcc and ld hardening by default. Resolves ticket 5210.
4876 - Update TLS cipher list to match Firefox 8 and later. Resolves
4878 - Implement the client side of proposal 198: remove support for
4879 clients falsely claiming to support standard ciphersuites that
4880 they can actually provide. As of modern OpenSSL versions, it's not
4881 necessary to fake any standard ciphersuite, and doing so prevents
4882 us from using better ciphersuites in the future, since servers
4883 can't know whether an advertised ciphersuite is really supported or
4884 not. Some hosts -- notably, ones with very old versions of OpenSSL
4885 or where OpenSSL has been built with ECC disabled -- will stand
4886 out because of this change; TBB users should not be affected.
4889 - Change the default value for DynamicDHGroups (introduced in
4890 0.2.3.9-alpha) to 0. This feature can make Tor relays less
4891 identifiable by their use of the mod_ssl DH group, but at
4892 the cost of some usability (#4721) and bridge tracing (#6087)
4893 regressions. Resolves ticket 5598.
4894 - Send a CRLF at the end of each STATUS_* control protocol event. This
4895 bug tickled a bug in Vidalia which would make it freeze. Fixes
4896 bug 6094; bugfix on 0.2.3.16-alpha.
4899 - Disable writing on marked-for-close connections when they are
4900 blocked on bandwidth, to prevent busy-looping in Libevent. Fixes
4901 bug 5263; bugfix on 0.0.2pre13, where we first added a special
4902 case for flushing marked connections.
4903 - Detect SSL handshake even when the initial attempt to write the
4904 server hello fails. Fixes bug 4592; bugfix on 0.2.0.13-alpha.
4905 - Change the AllowDotExit rules so they should actually work.
4906 We now enforce AllowDotExit only immediately after receiving an
4907 address via SOCKS or DNSPort: other sources are free to provide
4908 .exit addresses after the resolution occurs. Fixes bug 3940;
4909 bugfix on 0.2.2.1-alpha.
4910 - Fix a (harmless) integer overflow in cell statistics reported by
4911 some fast relays. Fixes bug 5849; bugfix on 0.2.2.1-alpha.
4912 - Make sure circuitbuild.c checks LearnCircuitBuildTimeout in all the
4913 right places and never depends on the consensus parameters or
4914 computes adaptive timeouts when it is disabled. Fixes bug 5049;
4915 bugfix on 0.2.2.14-alpha.
4916 - When building Tor on Windows with -DUNICODE (not default), ensure
4917 that error messages, filenames, and DNS server names are always
4918 NUL-terminated when we convert them to a single-byte encoding.
4919 Fixes bug 5909; bugfix on 0.2.2.16-alpha.
4920 - Make Tor build correctly again with -DUNICODE -D_UNICODE defined.
4921 Fixes bug 6097; bugfix on 0.2.2.16-alpha.
4922 - Fix an edge case where TestingTorNetwork is set but the authorities
4923 and relays all have an uptime of zero, where the private Tor network
4924 could briefly lack support for hidden services. Fixes bug 3886;
4925 bugfix on 0.2.2.18-alpha.
4926 - Correct the manpage's descriptions for the default values of
4927 DirReqStatistics and ExtraInfoStatistics. Fixes bug 2865; bugfix
4929 - Fix the documentation for the --hush and --quiet command line
4930 options, which changed their behavior back in 0.2.3.3-alpha.
4931 - Fix compilation warning with clang 3.1. Fixes bug 6141; bugfix on
4935 - Rate-limit the "Weighted bandwidth is 0.000000" message, and add
4936 more information to it, so that we can track it down in case it
4937 returns again. Mitigates bug 5235.
4938 - Check CircuitBuildTimeout and LearnCircuitBuildTimeout in
4939 options_validate(); warn if LearnCircuitBuildTimeout is disabled and
4940 CircuitBuildTimeout is set unreasonably low. Resolves ticket 5452.
4941 - Warn the user when HTTPProxy, but no other proxy type, is
4942 configured. This can cause surprising behavior: it doesn't send
4943 all of Tor's traffic over the HTTPProxy -- it sends unencrypted
4944 directory traffic only. Resolves ticket 4663.
4945 - Issue a notice if a guard completes less than 40% of your circuits.
4946 Threshold is configurable by torrc option PathBiasNoticeRate and
4947 consensus parameter pb_noticepct. There is additional, off-by-
4948 default code to disable guards which fail too many circuits.
4949 Addresses ticket 5458.
4950 - Update to the June 6 2012 Maxmind GeoLite Country database.
4952 o Code simplifications and refactoring:
4953 - Remove validate_pluggable_transports_config(): its warning
4954 message is now handled by connection_or_connect().
4957 Changes in version 0.2.2.37 - 2012-06-06
4958 Tor 0.2.2.37 introduces a workaround for a critical renegotiation
4959 bug in OpenSSL 1.0.1 (where 20% of the Tor network can't talk to itself
4963 - Work around a bug in OpenSSL that broke renegotiation with TLS
4964 1.1 and TLS 1.2. Without this workaround, all attempts to speak
4965 the v2 Tor connection protocol when both sides were using OpenSSL
4966 1.0.1 would fail. Resolves ticket 6033.
4967 - When waiting for a client to renegotiate, don't allow it to add
4968 any bytes to the input buffer. This fixes a potential DoS issue.
4969 Fixes bugs 5934 and 6007; bugfix on 0.2.0.20-rc.
4970 - Fix an edge case where if we fetch or publish a hidden service
4971 descriptor, we might build a 4-hop circuit and then use that circuit
4972 for exiting afterwards -- even if the new last hop doesn't obey our
4973 ExitNodes config option. Fixes bug 5283; bugfix on 0.2.0.10-alpha.
4976 - Fix a build warning with Clang 3.1 related to our use of vasprintf.
4977 Fixes bug 5969. Bugfix on 0.2.2.11-alpha.
4980 - Tell GCC and Clang to check for any errors in format strings passed
4981 to the tor_v*(print|scan)f functions.
4984 Changes in version 0.2.3.16-alpha - 2012-06-05
4985 Tor 0.2.3.16-alpha introduces a workaround for a critical renegotiation
4986 bug in OpenSSL 1.0.1 (where 20% of the Tor network can't talk to itself
4987 currently). It also fixes a variety of smaller bugs and other cleanups
4988 that get us closer to a release candidate.
4990 o Major bugfixes (general):
4991 - Work around a bug in OpenSSL that broke renegotiation with TLS
4992 1.1 and TLS 1.2. Without this workaround, all attempts to speak
4993 the v2 Tor connection protocol when both sides were using OpenSSL
4994 1.0.1 would fail. Resolves ticket 6033.
4995 - When waiting for a client to renegotiate, don't allow it to add
4996 any bytes to the input buffer. This fixes a potential DoS issue.
4997 Fixes bugs 5934 and 6007; bugfix on 0.2.0.20-rc.
4998 - Pass correct OR address to managed proxies (like obfsproxy),
4999 even when ORListenAddress is used. Fixes bug 4865; bugfix on
5001 - The advertised platform of a router now includes only its operating
5002 system's name (e.g., "Linux", "Darwin", "Windows 7"), and not its
5003 service pack level (for Windows) or its CPU architecture (for Unix).
5004 We also no longer include the "git-XYZ" tag in the version. Resolves
5007 o Major bugfixes (clients):
5008 - If we are unable to find any exit that supports our predicted ports,
5009 stop calling them predicted, so that we don't loop and build
5010 hopeless circuits indefinitely. Fixes bug 3296; bugfix on 0.0.9pre6,
5011 which introduced predicted ports.
5012 - Fix an edge case where if we fetch or publish a hidden service
5013 descriptor, we might build a 4-hop circuit and then use that circuit
5014 for exiting afterwards -- even if the new last hop doesn't obey our
5015 ExitNodes config option. Fixes bug 5283; bugfix on 0.2.0.10-alpha.
5016 - Check at each new consensus whether our entry guards were picked
5017 long enough ago that we should rotate them. Previously, we only
5018 did this check at startup, which could lead to us holding a guard
5019 indefinitely. Fixes bug 5380; bugfix on 0.2.1.14-rc.
5020 - When fetching a bridge descriptor from a bridge authority,
5021 always do so anonymously, whether we have been able to open
5022 circuits or not. Partial fix for bug 1938; bugfix on 0.2.0.7-alpha.
5023 This behavior makes it *safer* to use UpdateBridgesFromAuthority,
5024 but we'll need to wait for bug 6010 before it's actually usable.
5026 o Major bugfixes (directory authorities):
5027 - When computing weight parameters, behave more robustly in the
5028 presence of a bad bwweightscale value. Previously, the authorities
5029 would crash if they agreed on a sufficiently broken weight_scale
5030 value: now, they use a reasonable default and carry on. Partial
5031 fix for 5786; bugfix on 0.2.2.17-alpha.
5032 - Check more thoroughly to prevent a rogue authority from
5033 double-voting on any consensus directory parameter. Previously,
5034 authorities would crash in this case if the total number of
5035 votes for any parameter exceeded the number of active voters,
5036 but would let it pass otherwise. Partial fix for bug 5786; bugfix
5040 - Rate-limit log messages when asked to connect anonymously to
5041 a private address. When these hit, they tended to hit fast and
5042 often. Also, don't bother trying to connect to addresses that we
5043 are sure will resolve to 127.0.0.1: getting 127.0.0.1 in a directory
5044 reply makes us think we have been lied to, even when the address the
5045 client tried to connect to was "localhost." Resolves ticket 2822.
5046 - Allow packagers to insert an extra string in server descriptor
5047 platform lines by setting the preprocessor variable TOR_BUILD_TAG.
5048 Resolves the rest of ticket 2988.
5049 - Raise the threshold of server descriptors needed (75%) and exit
5050 server descriptors needed (50%) before we will declare ourselves
5051 bootstrapped. This will make clients start building circuits a
5052 little later, but makes the initially constructed circuits less
5053 skewed and less in conflict with further directory fetches. Fixes
5055 - Close any connection that sends unrecognized junk before the
5056 handshake. Solves an issue noted in bug 4369.
5057 - Improve log messages about managed transports. Resolves ticket 5070.
5058 - Tag a bridge's descriptor as "never to be sent unencrypted".
5059 This shouldn't matter, since bridges don't open non-anonymous
5060 connections to the bridge authority and don't allow unencrypted
5061 directory connections from clients, but we might as well make
5062 sure. Closes bug 5139.
5063 - Expose our view of whether we have gone dormant to the controller,
5064 via a new "GETINFO dormant" value. Torbutton and other controllers
5065 can use this to avoid doing periodic requests through Tor while
5066 it's dormant (bug 4718). Fixes bug 5954.
5067 - Tell GCC and Clang to check for any errors in format strings passed
5068 to the tor_v*(print|scan)f functions.
5069 - Update to the May 1 2012 Maxmind GeoLite Country database.
5071 o Minor bugfixes (already included in 0.2.2.36):
5072 - Reject out-of-range times like 23:59:61 in parse_rfc1123_time().
5073 Fixes bug 5346; bugfix on 0.0.8pre3.
5074 - Correct parsing of certain date types in parse_http_time().
5075 Without this patch, If-Modified-Since would behave
5076 incorrectly. Fixes bug 5346; bugfix on 0.2.0.2-alpha. Patch from
5077 Esteban Manchado Velázques.
5078 - Make our number-parsing functions always treat too-large values
5079 as an error, even when those values exceed the width of the
5080 underlying type. Previously, if the caller provided these
5081 functions with minima or maxima set to the extreme values of the
5082 underlying integer type, these functions would return those
5083 values on overflow rather than treating overflow as an error.
5084 Fixes part of bug 5786; bugfix on 0.0.9.
5085 - If we hit the error case where routerlist_insert() replaces an
5086 existing (old) server descriptor, make sure to remove that
5087 server descriptor from the old_routers list. Fix related to bug
5088 1776. Bugfix on 0.2.2.18-alpha.
5089 - Clarify the behavior of MaxCircuitDirtiness with hidden service
5090 circuits. Fixes issue 5259.
5092 o Minor bugfixes (coding cleanup, on 0.2.2.x and earlier):
5093 - Prevent a null-pointer dereference when receiving a data cell
5094 for a nonexistent stream when the circuit in question has an
5095 empty deliver window. We don't believe this is triggerable,
5096 since we don't currently allow deliver windows to become empty,
5097 but the logic is tricky enough that it's better to make the code
5098 robust. Fixes bug 5541; bugfix on 0.0.2pre14.
5099 - Fix a memory leak when trying to launch a DNS request when the
5100 network is disabled or the nameservers are unconfigurable. Fixes
5101 bug 5916; bugfix on Tor 0.1.2.1-alpha (for the unconfigurable
5102 nameserver case) and on 0.2.3.9-alpha (for the DisableNetwork case).
5103 - Don't hold a Windows file handle open for every file mapping;
5104 the file mapping handle is sufficient. Fixes bug 5951; bugfix on
5106 - Avoid O(n^2) performance characteristics when parsing a large
5107 extrainfo cache. Fixes bug 5828; bugfix on 0.2.0.1-alpha.
5108 - Format more doubles with %f, not %lf. Patch from grarpamp to make
5109 Tor build correctly on older BSDs again. Fixes bug 3894; bugfix on
5111 - Make our replacement implementation of strtok_r() compatible with
5112 the standard behavior of strtok_r(). Patch by nils. Fixes bug 5091;
5113 bugfix on 0.2.2.1-alpha.
5114 - Fix a NULL-pointer dereference on a badly formed
5115 SETCIRCUITPURPOSE command. Found by mikeyc. Fixes bug 5796;
5116 bugfix on 0.2.2.9-alpha.
5117 - Fix a build warning with Clang 3.1 related to our use of vasprintf.
5118 Fixes bug 5969. Bugfix on 0.2.2.11-alpha.
5119 - Defensively refactor rend_mid_rendezvous() so that protocol
5120 violations and length checks happen in the beginning. Fixes
5122 - Set _WIN32_WINNT to 0x0501 consistently throughout the code, so
5123 that IPv6 stuff will compile on MSVC, and compilation issues
5124 will be easier to track down. Fixes bug 5861.
5126 o Minor bugfixes (correctness, on 0.2.2.x and earlier):
5127 - Exit nodes now correctly report EADDRINUSE and EADDRNOTAVAIL as
5128 resource exhaustion, so that clients can adjust their load to
5129 try other exits. Fixes bug 4710; bugfix on 0.1.0.1-rc, which
5130 started using END_STREAM_REASON_RESOURCELIMIT.
5131 - Don't check for whether the address we're using for outbound
5132 connections has changed until after the outbound connection has
5133 completed. On Windows, getsockname() doesn't succeed until the
5134 connection is finished. Fixes bug 5374; bugfix on 0.1.1.14-alpha.
5135 - If the configuration tries to set MyFamily on a bridge, refuse to
5136 do so, and warn about the security implications. Fixes bug 4657;
5137 bugfix on 0.2.0.3-alpha.
5138 - If the client fails to set a reasonable set of ciphersuites
5139 during its v2 handshake renegotiation, allow the renegotiation to
5140 continue nevertheless (i.e. send all the required certificates).
5141 Fixes bug 4591; bugfix on 0.2.0.20-rc.
5142 - When we receive a SIGHUP and the controller __ReloadTorrcOnSIGHUP
5143 option is set to 0 (which Vidalia version 0.2.16 now does when
5144 a SAVECONF attempt fails), perform other actions that SIGHUP
5145 usually causes (like reopening the logs). Fixes bug 5095; bugfix
5147 - If we fail to write a microdescriptor to the disk cache, do not
5148 continue replacing the old microdescriptor file. Fixes bug 2954;
5149 bugfix on 0.2.2.6-alpha.
5150 - Exit nodes don't need to fetch certificates for authorities that
5151 they don't recognize; only directory authorities, bridges,
5152 and caches need to do that. Fixes part of bug 2297; bugfix on
5154 - Correctly handle checking the permissions on the parent
5155 directory of a control socket in the root directory. Bug found
5156 by Esteban Manchado Velázquez. Fixes bug 5089; bugfix on Tor
5158 - When told to add a bridge with the same digest as a preexisting
5159 bridge but a different addr:port, change the addr:port as
5160 requested. Previously we would not notice the change. Fixes half
5161 of bug 5603; fix on 0.2.2.26-beta.
5162 - End AUTHCHALLENGE error messages (in the control protocol) with
5163 a CRLF. Fixes bug 5760; bugfix on 0.2.2.36 and 0.2.3.13-alpha.
5165 o Minor bugfixes (on 0.2.3.x):
5166 - Turn an assertion (that the number of handshakes received as a
5167 server is not < 1) into a warning. Fixes bug 4873; bugfix on
5169 - Format IPv4 addresses correctly in ADDRMAP events. (Previously,
5170 we had reversed them when the answer was cached.) Fixes bug
5171 5723; bugfix on 0.2.3.1-alpha.
5172 - Work correctly on Linux systems with accept4 support advertised in
5173 their headers, but without accept4 support in the kernel. Fix
5174 by murb. Fixes bug 5762; bugfix on 0.2.3.1-alpha.
5175 - When told to add a bridge with the same addr:port as a preexisting
5176 bridge but a different transport, change the transport as
5177 requested. Previously we would not notice the change. Fixes half
5178 of bug 5603; fix on 0.2.3.2-alpha.
5179 - Avoid a "double-reply" warning when replying to a SOCKS request
5180 with a parse error. Patch from Fabian Keil. Fixes bug 4108;
5181 bugfix on 0.2.3.4-alpha.
5182 - Fix a bug where a bridge authority crashes if it has seen no
5183 directory requests when it's time to write statistics to disk.
5184 Fixes bug 5891; bugfix on 0.2.3.6-alpha. Also fixes bug 5508 in
5186 - Don't try to open non-control listeners when DisableNetwork is set.
5187 Previously, we'd open all listeners, then immediately close them.
5188 Fixes bug 5604; bugfix on 0.2.3.9-alpha.
5189 - Don't abort the managed proxy protocol if the managed proxy
5190 sends us an unrecognized line; ignore it instead. Fixes bug
5191 5910; bugfix on 0.2.3.9-alpha.
5192 - Fix a compile warning in crypto.c when compiling with clang 3.1.
5193 Fixes bug 5969, bugfix on 0.2.3.9-alpha.
5194 - Fix a compilation issue on GNU Hurd, which doesn't have PATH_MAX.
5195 Fixes bug 5355; bugfix on 0.2.3.11-alpha.
5196 - Remove bogus definition of "_WIN32" from src/win32/orconfig.h, to
5197 unbreak the MSVC build. Fixes bug 5858; bugfix on 0.2.3.12-alpha.
5198 - Resolve numerous small warnings and build issues with MSVC. Resolves
5201 o Documentation fixes:
5202 - Improve the manual's documentation for the NT Service command-line
5203 options. Addresses ticket 3964.
5204 - Clarify SessionGroup documentation slightly; resolves ticket 5437.
5205 - Document the changes to the ORPort and DirPort options, and the
5206 fact that {OR/Dir}ListenAddress is now unnecessary (and
5207 therefore deprecated). Resolves ticket 5597.
5210 - Remove the torrc.bridge file: we don't use it for anything, and
5211 it had become badly desynchronized from torrc.sample. Resolves
5215 Changes in version 0.2.2.36 - 2012-05-24
5216 Tor 0.2.2.36 updates the addresses for two of the eight directory
5217 authorities, fixes some potential anonymity and security issues,
5218 and fixes several crash bugs.
5220 Tor 0.2.1.x has reached its end-of-life. Those Tor versions have many
5221 known flaws, and nobody should be using them. You should upgrade. If
5222 you're using a Linux or BSD and its packages are obsolete, stop using
5223 those packages and upgrade anyway.
5225 o Directory authority changes:
5226 - Change IP address for maatuska (v3 directory authority).
5227 - Change IP address for ides (v3 directory authority), and rename
5231 - When building or running with any version of OpenSSL earlier
5232 than 0.9.8s or 1.0.0f, disable SSLv3 support. These OpenSSL
5233 versions have a bug (CVE-2011-4576) in which their block cipher
5234 padding includes uninitialized data, potentially leaking sensitive
5235 information to any peer with whom they make a SSLv3 connection. Tor
5236 does not use SSL v3 by default, but a hostile client or server
5237 could force an SSLv3 connection in order to gain information that
5238 they shouldn't have been able to get. The best solution here is to
5239 upgrade to OpenSSL 0.9.8s or 1.0.0f (or later). But when building
5240 or running with a non-upgraded OpenSSL, we disable SSLv3 entirely
5241 to make sure that the bug can't happen.
5242 - Never use a bridge or a controller-supplied node as an exit, even
5243 if its exit policy allows it. Found by wanoskarnet. Fixes bug
5244 5342. Bugfix on 0.1.1.15-rc (for controller-purpose descriptors)
5245 and 0.2.0.3-alpha (for bridge-purpose descriptors).
5246 - Only build circuits if we have a sufficient threshold of the total
5247 descriptors that are marked in the consensus with the "Exit"
5248 flag. This mitigates an attack proposed by wanoskarnet, in which
5249 all of a client's bridges collude to restrict the exit nodes that
5250 the client knows about. Fixes bug 5343.
5251 - Provide controllers with a safer way to implement the cookie
5252 authentication mechanism. With the old method, if another locally
5253 running program could convince a controller that it was the Tor
5254 process, then that program could trick the controller into telling
5255 it the contents of an arbitrary 32-byte file. The new "SAFECOOKIE"
5256 authentication method uses a challenge-response approach to prevent
5257 this attack. Fixes bug 5185; implements proposal 193.
5260 - Avoid logging uninitialized data when unable to decode a hidden
5261 service descriptor cookie. Fixes bug 5647; bugfix on 0.2.1.5-alpha.
5262 - Avoid a client-side assertion failure when receiving an INTRODUCE2
5263 cell on a general purpose circuit. Fixes bug 5644; bugfix on
5265 - Fix builds when the path to sed, openssl, or sha1sum contains
5266 spaces, which is pretty common on Windows. Fixes bug 5065; bugfix
5268 - Correct our replacements for the timeradd() and timersub() functions
5269 on platforms that lack them (for example, Windows). The timersub()
5270 function is used when expiring circuits, while timeradd() is
5271 currently unused. Bug report and patch by Vektor. Fixes bug 4778;
5272 bugfix on 0.2.2.24-alpha.
5273 - Fix the SOCKET_OK test that we use to tell when socket
5274 creation fails so that it works on Win64. Fixes part of bug 4533;
5275 bugfix on 0.2.2.29-beta. Bug found by wanoskarnet.
5278 - Reject out-of-range times like 23:59:61 in parse_rfc1123_time().
5279 Fixes bug 5346; bugfix on 0.0.8pre3.
5280 - Make our number-parsing functions always treat too-large values
5281 as an error, even when those values exceed the width of the
5282 underlying type. Previously, if the caller provided these
5283 functions with minima or maxima set to the extreme values of the
5284 underlying integer type, these functions would return those
5285 values on overflow rather than treating overflow as an error.
5286 Fixes part of bug 5786; bugfix on 0.0.9.
5287 - Older Linux kernels erroneously respond to strange nmap behavior
5288 by having accept() return successfully with a zero-length
5289 socket. When this happens, just close the connection. Previously,
5290 we would try harder to learn the remote address: but there was
5291 no such remote address to learn, and our method for trying to
5292 learn it was incorrect. Fixes bugs 1240, 4745, and 4747. Bugfix
5293 on 0.1.0.3-rc. Reported and diagnosed by "r1eo".
5294 - Correct parsing of certain date types in parse_http_time().
5295 Without this patch, If-Modified-Since would behave
5296 incorrectly. Fixes bug 5346; bugfix on 0.2.0.2-alpha. Patch from
5297 Esteban Manchado Velázques.
5298 - Change the BridgePassword feature (part of the "bridge community"
5299 design, which is not yet implemented) to use a time-independent
5300 comparison. The old behavior might have allowed an adversary
5301 to use timing to guess the BridgePassword value. Fixes bug 5543;
5302 bugfix on 0.2.0.14-alpha.
5303 - Detect and reject certain misformed escape sequences in
5304 configuration values. Previously, these values would cause us
5305 to crash if received in a torrc file or over an authenticated
5306 control port. Bug found by Esteban Manchado Velázquez, and
5307 independently by Robert Connolly from Matta Consulting who further
5308 noted that it allows a post-authentication heap overflow. Patch
5309 by Alexander Schrijver. Fixes bugs 5090 and 5402 (CVE 2012-1668);
5310 bugfix on 0.2.0.16-alpha.
5311 - Fix a compile warning when using the --enable-openbsd-malloc
5312 configure option. Fixes bug 5340; bugfix on 0.2.0.20-rc.
5313 - During configure, detect when we're building with clang version
5314 3.0 or lower and disable the -Wnormalized=id and -Woverride-init
5315 CFLAGS. clang doesn't support them yet.
5316 - When sending an HTTP/1.1 proxy request, include a Host header.
5317 Fixes bug 5593; bugfix on 0.2.2.1-alpha.
5318 - Fix a NULL-pointer dereference on a badly formed SETCIRCUITPURPOSE
5319 command. Found by mikeyc. Fixes bug 5796; bugfix on 0.2.2.9-alpha.
5320 - If we hit the error case where routerlist_insert() replaces an
5321 existing (old) server descriptor, make sure to remove that
5322 server descriptor from the old_routers list. Fix related to bug
5323 1776. Bugfix on 0.2.2.18-alpha.
5325 o Minor bugfixes (documentation and log messages):
5326 - Fix a typo in a log message in rend_service_rendezvous_has_opened().
5327 Fixes bug 4856; bugfix on Tor 0.0.6.
5328 - Update "ClientOnly" man page entry to explain that there isn't
5329 really any point to messing with it. Resolves ticket 5005.
5330 - Document the GiveGuardFlagTo_CVE_2011_2768_VulnerableRelays
5331 directory authority option (introduced in Tor 0.2.2.34).
5332 - Downgrade the "We're missing a certificate" message from notice
5333 to info: people kept mistaking it for a real problem, whereas it
5334 is seldom the problem even when we are failing to bootstrap. Fixes
5335 bug 5067; bugfix on 0.2.0.10-alpha.
5336 - Correctly spell "connect" in a log message on failure to create a
5337 controlsocket. Fixes bug 4803; bugfix on 0.2.2.26-beta.
5338 - Clarify the behavior of MaxCircuitDirtiness with hidden service
5339 circuits. Fixes issue 5259.
5342 - Directory authorities now reject versions of Tor older than
5343 0.2.1.30, and Tor versions between 0.2.2.1-alpha and 0.2.2.20-alpha
5344 inclusive. These versions accounted for only a small fraction of
5345 the Tor network, and have numerous known security issues. Resolves
5347 - Update to the May 1 2012 Maxmind GeoLite Country database.
5350 - When sending or relaying a RELAY_EARLY cell, we used to convert
5351 it to a RELAY cell if the connection was using the v1 link
5352 protocol. This was a workaround for older versions of Tor, which
5353 didn't handle RELAY_EARLY cells properly. Now that all supported
5354 versions can handle RELAY_EARLY cells, and now that we're enforcing
5355 the "no RELAY_EXTEND commands except in RELAY_EARLY cells" rule,
5356 remove this workaround. Addresses bug 4786.
5359 Changes in version 0.2.3.15-alpha - 2012-04-30
5360 Tor 0.2.3.15-alpha fixes a variety of smaller bugs, including making
5361 the development branch build on Windows again.
5363 o Minor bugfixes (on 0.2.2.x and earlier):
5364 - Make sure that there are no unhandled pending TLS errors before
5365 reading from a TLS stream. We had checks in 0.1.0.3-rc, but
5366 lost them in 0.1.0.5-rc when we refactored read_to_buf_tls().
5367 Bugfix on 0.1.0.5-rc; fixes bug 4528.
5368 - Fix an assert that directory authorities could trigger on sighup
5369 during some configuration state transitions. We now don't treat
5370 it as a fatal error when the new descriptor we just generated in
5371 init_keys() isn't accepted. Fixes bug 4438; bugfix on 0.2.1.9-alpha.
5372 - After we pick a directory mirror, we would refuse to use it if
5373 it's in our ExcludeExitNodes list, resulting in mysterious failures
5374 to bootstrap for people who just wanted to avoid exiting from
5375 certain locations. Fixes bug 5623; bugfix on 0.2.2.25-alpha.
5376 - When building with --enable-static-tor on OpenBSD, do not
5377 erroneously attempt to link -lrt. Fixes bug 5103.
5379 o Minor bugfixes (on 0.2.3.x):
5380 - When Tor is built with kernel headers from a recent (last few
5381 years) Linux kernel, do not fail to run on older (pre-2.6.28
5382 Linux kernels). Fixes bug 5112; bugfix on 0.2.3.1-alpha.
5383 - Fix cross-compilation issues with mingw. Bugfixes on 0.2.3.6-alpha
5385 - Fix compilation with miniupnpc version 1.6; patch from
5386 Anthony G. Basile. Fixes bug 5434; bugfix on 0.2.3.12-alpha.
5387 - Fix compilation with MSVC, which had defined MS_WINDOWS. Bugfix
5388 on 0.2.3.13-alpha; found and fixed by Gisle Vanem.
5389 - Fix compilation on platforms without unistd.h, or where environ
5390 is defined in stdlib.h. Fixes bug 5704; bugfix on 0.2.3.13-alpha.
5393 - Directory authorities are now a little more lenient at accepting
5394 older router descriptors, or newer router descriptors that don't
5395 make big changes. This should help ameliorate past and future
5396 issues where routers think they have uploaded valid descriptors,
5397 but the authorities don't think so. Fix for ticket 2479.
5398 - Make the code that clients use to detect an address change be
5399 IPv6-aware, so that it won't fill clients' logs with error
5400 messages when trying to get the IPv4 address of an IPv6
5401 connection. Implements ticket 5537.
5404 - Remove the GiveGuardFlagTo_CVE_2011_2768_VulnerableRelays option;
5405 authorities needed to use it for a while to keep the network working
5406 as people upgraded to 0.2.1.31, 0.2.2.34, or 0.2.3.6-alpha, but
5407 that was six months ago. As of now, it should no longer be needed
5411 Changes in version 0.2.3.14-alpha - 2012-04-23
5412 Tor 0.2.3.14-alpha fixes yet more bugs to get us closer to a release
5413 candidate. It also dramatically speeds up AES: fast relays should
5414 consider switching to the newer OpenSSL library.
5416 o Directory authority changes:
5417 - Change IP address for ides (v3 directory authority), and rename
5421 - Avoid logging uninitialized data when unable to decode a hidden
5422 service descriptor cookie. Fixes bug 5647; bugfix on 0.2.1.5-alpha.
5423 - Avoid a client-side assertion failure when receiving an INTRODUCE2
5424 cell on a general purpose circuit. Fixes bug 5644; bugfix on
5426 - If authorities are unable to get a v2 consensus document from other
5427 directory authorities, they no longer fall back to fetching
5428 them from regular directory caches. Fixes bug 5635; bugfix on
5429 0.2.2.26-beta, where routers stopped downloading v2 consensus
5431 - When we start a Tor client with a normal consensus already cached,
5432 be willing to download a microdescriptor consensus. Fixes bug 4011;
5433 fix on 0.2.3.1-alpha.
5435 o Major features (performance):
5436 - When built to use OpenSSL 1.0.1, and built for an x86 or x86_64
5437 instruction set, take advantage of OpenSSL's AESNI, bitsliced, or
5438 vectorized AES implementations as appropriate. These can be much,
5439 much faster than other AES implementations.
5441 o Minor bugfixes (0.2.2.x and earlier):
5442 - Don't launch more than 10 service-side introduction-point circuits
5443 for a hidden service in five minutes. Previously, we would consider
5444 launching more introduction-point circuits if at least one second
5445 had passed without any introduction-point circuits failing. Fixes
5446 bug 4607; bugfix on 0.0.7pre1.
5447 - Change the BridgePassword feature (part of the "bridge community"
5448 design, which is not yet implemented) to use a time-independent
5449 comparison. The old behavior might have allowed an adversary
5450 to use timing to guess the BridgePassword value. Fixes bug 5543;
5451 bugfix on 0.2.0.14-alpha.
5452 - Enforce correct return behavior of tor_vsscanf() when the '%%'
5453 pattern is used. Fixes bug 5558. Bugfix on 0.2.1.13.
5454 - When sending an HTTP/1.1 proxy request, include a Host header.
5455 Fixes bug 5593; bugfix on 0.2.2.1-alpha.
5456 - Don't log that we have "decided to publish new relay descriptor"
5457 unless we are actually publishing a descriptor. Fixes bug 3942;
5458 bugfix on 0.2.2.28-beta.
5460 o Minor bugfixes (0.2.3.x):
5461 - Fix a bug where a bridge authority crashes (on a failed assert)
5462 if it has seen no directory requests when it's time to write
5463 statistics to disk. Fixes bug 5508. Bugfix on 0.2.3.6-alpha.
5464 - Fix bug stomping on ORPort option NoListen and ignoring option
5465 NoAdvertise. Fixes bug 5151; bugfix on 0.2.3.9-alpha.
5466 - In the testsuite, provide a large enough buffer in the tor_sscanf
5467 unit test. Otherwise we'd overrun that buffer and crash during
5468 the unit tests. Found by weasel. Fixes bug 5449; bugfix on
5470 - Make sure we create the keys directory if it doesn't exist and we're
5471 about to store the dynamic Diffie-Hellman parameters. Fixes bug
5472 5572; bugfix on 0.2.3.13-alpha.
5473 - Fix a small memory leak when trying to decode incorrect base16
5474 authenticator during SAFECOOKIE authentication. Found by
5475 Coverity Scan. Fixes CID 507. Bugfix on 0.2.3.13-alpha.
5478 - Add more information to a log statement that might help track down
5479 bug 4091. If you're seeing "Bug: tor_addr_is_internal() called with a
5480 non-IP address" messages (or any Bug messages, for that matter!),
5481 please let us know about it.
5482 - Relays now understand an IPv6 address when they get one from a
5483 directory server. Resolves ticket 4875.
5484 - Resolve IPv6 addresses in bridge and entry statistics to country
5485 code "??" which means we at least count them. Resolves ticket 5053;
5486 improves on 0.2.3.9-alpha.
5487 - Update to the April 3 2012 Maxmind GeoLite Country database.
5488 - Begin a doc/state-contents.txt file to explain the contents of
5489 the Tor state file. Fixes bug 2987.
5491 o Default torrc changes:
5492 - Stop listing "socksport 9050" in torrc.sample. We open a socks
5493 port on 9050 by default anyway, so this should not change anything
5495 - Stop mentioning the deprecated *ListenAddress options in
5496 torrc.sample. Fixes bug 5438.
5497 - Document unit of bandwidth related options in sample torrc.
5501 - The "torify" script no longer supports the "tsocks" socksifier
5502 tool, since tsocks doesn't support DNS and UDP right for Tor.
5503 Everyone should be using torsocks instead. Fixes bugs 3530 and
5504 5180. Based on a patch by "ugh".
5507 - Change the symmetric cipher interface so that creating and
5508 initializing a stream cipher are no longer separate functions.
5509 - Remove all internal support for unpadded RSA. We never used it, and
5510 it would be a bad idea to start.
5513 Changes in version 0.2.3.13-alpha - 2012-03-26
5514 Tor 0.2.3.13-alpha fixes a variety of stability and correctness bugs
5515 in managed pluggable transports, as well as providing other cleanups
5516 that get us closer to a release candidate.
5518 o Directory authority changes:
5519 - Change IP address for maatuska (v3 directory authority).
5522 - Provide controllers with a safer way to implement the cookie
5523 authentication mechanism. With the old method, if another locally
5524 running program could convince a controller that it was the Tor
5525 process, then that program could trick the controller into telling
5526 it the contents of an arbitrary 32-byte file. The new "SAFECOOKIE"
5527 authentication method uses a challenge-response approach to prevent
5528 this attack. Fixes bug 5185, implements proposal 193.
5529 - Never use a bridge or a controller-supplied node as an exit, even
5530 if its exit policy allows it. Found by wanoskarnet. Fixes bug
5531 5342. Bugfix on 0.1.1.15-rc (for controller-purpose descriptors)
5532 and 0.2.0.3-alpha (for bridge-purpose descriptors).
5533 - Only build circuits if we have a sufficient threshold of the total
5534 descriptors that are marked in the consensus with the "Exit"
5535 flag. This mitigates an attack proposed by wanoskarnet, in which
5536 all of a client's bridges collude to restrict the exit nodes that
5537 the client knows about. Fixes bug 5343.
5539 o Major bugfixes (on Tor 0.2.3.x):
5540 - Avoid an assert when managed proxies like obfsproxy are configured,
5541 and we receive HUP signals or setconf attempts too rapidly. This
5542 situation happens most commonly when Vidalia tries to attach to
5543 Tor or tries to configure the Tor it's attached to. Fixes bug 5084;
5544 bugfix on 0.2.3.6-alpha.
5545 - Fix a relay-side pluggable transports bug where managed proxies were
5546 unreachable from the Internet, because Tor asked them to bind on
5547 localhost. Fixes bug 4725; bugfix on 0.2.3.9-alpha.
5548 - Stop discarding command-line arguments when TestingTorNetwork
5549 is set. Discovered by Kevin Bauer. Fixes bug 5373; bugfix on
5550 0.2.3.9-alpha, where task 4552 added support for two layers of
5552 - Resume allowing the unit tests to run in gdb. This was accidentally
5553 made impossible when the DisableDebuggerAttachment option was
5554 introduced. Fixes bug 5448; bugfix on 0.2.3.9-alpha.
5555 - Resume building with nat-pmp support. Fixes bug 4955; bugfix on
5556 0.2.3.11-alpha. Reported by Anthony G. Basile.
5558 o Minor bugfixes (on 0.2.2.x and earlier):
5559 - Ensure we don't cannibalize circuits that are longer than three hops
5560 already, so we don't end up making circuits with 5 or more
5561 hops. Patch contributed by wanoskarnet. Fixes bug 5231; bugfix on
5562 0.1.0.1-rc which introduced cannibalization.
5563 - Detect and reject certain misformed escape sequences in
5564 configuration values. Previously, these values would cause us
5565 to crash if received in a torrc file or over an authenticated
5566 control port. Bug found by Esteban Manchado Velázquez, and
5567 independently by Robert Connolly from Matta Consulting who further
5568 noted that it allows a post-authentication heap overflow. Patch
5569 by Alexander Schrijver. Fixes bugs 5090 and 5402 (CVE 2012-1668);
5570 bugfix on 0.2.0.16-alpha.
5571 - Fix a compile warning when using the --enable-openbsd-malloc
5572 configure option. Fixes bug 5340; bugfix on 0.2.0.20-rc.
5573 - Directory caches no longer refuse to clean out descriptors because
5574 of missing v2 networkstatus documents, unless they're configured
5575 to retrieve v2 networkstatus documents. Fixes bug 4838; bugfix on
5576 0.2.2.26-beta. Patch by Daniel Bryg.
5577 - Update to the latest version of the tinytest unit testing framework.
5578 This includes a couple of bugfixes that can be relevant for
5579 running forked unit tests on Windows, and removes all reserved
5582 o Minor bugfixes (on 0.2.3.x):
5583 - On a failed pipe() call, don't leak file descriptors. Fixes bug
5584 4296; bugfix on 0.2.3.1-alpha.
5585 - Spec conformance: on a v3 handshake, do not send a NETINFO cell
5586 until after we have received a CERTS cell. Fixes bug 4361; bugfix
5587 on 0.2.3.6-alpha. Patch by "frosty".
5588 - When binding to an IPv6 address, set the IPV6_V6ONLY socket
5589 option, so that the IP stack doesn't decide to use it for IPv4
5590 too. Fixes bug 4760; bugfix on 0.2.3.9-alpha.
5591 - Ensure that variables set in Tor's environment cannot override
5592 environment variables that Tor passes to a managed
5593 pluggable-transport proxy. Previously, Tor would pass every
5594 variable in its environment to managed proxies along with the new
5595 ones, in such a way that on many operating systems, the inherited
5596 environment variables would override those which Tor tried to
5597 explicitly set. Bugfix on 0.2.3.12-alpha for most Unixoid systems;
5598 bugfix on 0.2.3.9-alpha for Windows.
5601 - A wide variety of new unit tests by Esteban Manchado Velázquez.
5602 - Shorten links in the tor-exit-notice file. Patch by Christian Kujau.
5603 - Update to the March 6 2012 Maxmind GeoLite Country database.
5606 Changes in version 0.2.3.12-alpha - 2012-02-13
5607 Tor 0.2.3.12-alpha lets fast exit relays scale better, allows clients
5608 to use bridges that run Tor 0.2.2.x, and resolves several big bugs
5609 when Tor is configured to use a pluggable transport like obfsproxy.
5612 - Fix builds when the path to sed, openssl, or sha1sum contains
5613 spaces, which is pretty common on Windows. Fixes bug 5065; bugfix
5615 - Set the SO_REUSEADDR socket option before we call bind() on outgoing
5616 connections. This change should allow busy exit relays to stop
5617 running out of available sockets as quickly. Fixes bug 4950;
5618 bugfix on 0.2.2.26-beta.
5619 - Allow 0.2.3.x clients to use 0.2.2.x bridges. Previously the client
5620 would ask the bridge for microdescriptors, which are only supported
5621 in 0.2.3.x, and then fail to bootstrap when it didn't get the
5622 answers it wanted. Fixes bug 4013; bugfix on 0.2.3.2-alpha.
5623 - Properly set up obfsproxy's environment when in managed mode. The
5624 Tor Browser Bundle needs LD_LIBRARY_PATH to be passed to obfsproxy,
5625 and when you run your Tor as a daemon, there's no HOME. Fixes bugs
5626 5076 and 5082; bugfix on 0.2.3.6-alpha.
5629 - Use the dead_strip option when building Tor on OS X. This reduces
5630 binary size by almost 19% when linking openssl and libevent
5631 statically, which we do for Tor Browser Bundle.
5632 - Fix broken URLs in the sample torrc file, and tell readers about
5633 the OutboundBindAddress, ExitPolicyRejectPrivate, and
5634 PublishServerDescriptor options. Addresses bug 4652.
5635 - Update to the February 7 2012 Maxmind GeoLite Country database.
5638 - Downgrade the "We're missing a certificate" message from notice
5639 to info: people kept mistaking it for a real problem, whereas it
5640 is seldom the problem even when we are failing to bootstrap. Fixes
5641 bug 5067; bugfix on 0.2.0.10-alpha.
5642 - Don't put "TOR_PT_EXTENDED_SERVER_PORT=127.0.0.1:4200" in a
5643 managed pluggable transport server proxy's environment.
5644 Previously, we would put it there, even though Tor doesn't
5645 implement an 'extended server port' yet, and even though Tor
5646 almost certainly isn't listening at that address. For now, we set
5647 it to an empty string to avoid crashing older obfsproxies. Bugfix
5649 - Log the heartbeat message every HeartbeatPeriod seconds, not every
5650 HeartbeatPeriod + 1 seconds. Fixes bug 4942; bugfix on
5651 0.2.3.1-alpha. Bug reported by Scott Bennett.
5652 - Calculate absolute paths correctly on Windows. Fixes bug 4973;
5653 bugfix on 0.2.3.11-alpha.
5654 - Update "ClientOnly" man page entry to explain that there isn't
5655 really any point to messing with it. Resolves ticket 5005.
5656 - Use the correct CVE number for CVE-2011-4576 in our comments and
5657 log messages. Found by "fermenthor". Resolves bug 5066; bugfix on
5660 o Code simplifications and refactoring:
5661 - Use the _WIN32 macro throughout our code to detect Windows.
5662 (Previously we had used the obsolete 'WIN32' and the idiosyncratic
5666 Changes in version 0.2.3.11-alpha - 2012-01-22
5667 Tor 0.2.3.11-alpha marks feature-freeze for the 0.2.3 tree. It deploys
5668 the last step of the plan to limit maximum circuit length, includes
5669 a wide variety of hidden service performance and correctness fixes,
5670 works around an OpenSSL security flaw if your distro is too stubborn
5671 to upgrade, and fixes a bunch of smaller issues.
5674 - Now that Tor 0.2.0.x is completely deprecated, enable the final
5675 part of "Proposal 110: Avoiding infinite length circuits" by
5676 refusing all circuit-extend requests that do not use a relay_early
5677 cell. This change helps Tor resist a class of denial-of-service
5678 attacks by limiting the maximum circuit length.
5679 - Adjust the number of introduction points that a hidden service
5680 will try to maintain based on how long its introduction points
5681 remain in use and how many introductions they handle. Fixes
5683 - Try to use system facilities for enumerating local interface
5684 addresses, before falling back to our old approach (which was
5685 binding a UDP socket, and calling getsockname() on it). That
5686 approach was scaring OS X users whose draconian firewall
5687 software warned about binding to UDP sockets, regardless of
5688 whether packets were sent. Now we try to use getifaddrs(),
5689 SIOCGIFCONF, or GetAdaptersAddresses(), depending on what the
5690 system supports. Resolves ticket 1827.
5692 o Major security workaround:
5693 - When building or running with any version of OpenSSL earlier
5694 than 0.9.8s or 1.0.0f, disable SSLv3 support. These OpenSSL
5695 versions have a bug (CVE-2011-4576) in which their block cipher
5696 padding includes uninitialized data, potentially leaking sensitive
5697 information to any peer with whom they make a SSLv3 connection. Tor
5698 does not use SSL v3 by default, but a hostile client or server
5699 could force an SSLv3 connection in order to gain information that
5700 they shouldn't have been able to get. The best solution here is to
5701 upgrade to OpenSSL 0.9.8s or 1.0.0f (or later). But when building
5702 or running with a non-upgraded OpenSSL, we disable SSLv3 entirely
5703 to make sure that the bug can't happen.
5706 - Fix the SOCKET_OK test that we use to tell when socket
5707 creation fails so that it works on Win64. Fixes part of bug 4533;
5708 bugfix on 0.2.2.29-beta. Bug found by wanoskarnet.
5709 - Correct our replacements for the timeradd() and timersub() functions
5710 on platforms that lack them (for example, Windows). The timersub()
5711 function is used when expiring circuits, while timeradd() is
5712 currently unused. Bug report and patch by Vektor. Fixes bug 4778;
5713 bugfix on 0.2.2.24-alpha and 0.2.3.1-alpha.
5714 - Do not use OpenSSL 1.0.0's counter mode: it has a critical bug
5715 that was fixed in OpenSSL 1.0.0a. We test for the counter mode
5716 bug at runtime, not compile time, because some distributions hack
5717 their OpenSSL to mis-report its version. Fixes bug 4779; bugfix
5718 on 0.2.3.9-alpha. Found by Pascal.
5720 o Minor features (controller):
5721 - Use absolute path names when reporting the torrc filename in the
5722 control protocol, so a controller can more easily find the torrc
5723 file. Resolves bug 1101.
5724 - Extend the control protocol to report flags that control a circuit's
5725 path selection in CIRC events and in replies to 'GETINFO
5726 circuit-status'. Implements part of ticket 2411.
5727 - Extend the control protocol to report the hidden service address
5728 and current state of a hidden-service-related circuit in CIRC
5729 events and in replies to 'GETINFO circuit-status'. Implements part
5731 - When reporting the path to the cookie file to the controller,
5732 give an absolute path. Resolves ticket 4881.
5733 - Allow controllers to request an event notification whenever a
5734 circuit is cannibalized or its purpose is changed. Implements
5735 part of ticket 3457.
5736 - Include the creation time of a circuit in CIRC and CIRC2
5737 control-port events and the list produced by the 'GETINFO
5738 circuit-status' control-port command.
5740 o Minor features (directory authorities):
5741 - Directory authorities now reject versions of Tor older than
5742 0.2.1.30, and Tor versions between 0.2.2.1-alpha and 0.2.2.20-alpha
5743 inclusive. These versions accounted for only a small fraction of
5744 the Tor network, and have numerous known security issues. Resolves
5746 - Authority operators can now vote for all relays in a given
5747 set of countries to be BadDir/BadExit/Invalid/Rejected.
5748 - Provide two consensus parameters (FastFlagMinThreshold and
5749 FastFlagMaxThreshold) to control the range of allowable bandwidths
5750 for the Fast directory flag. These allow authorities to run
5751 experiments on appropriate requirements for being a "Fast" node.
5752 The AuthDirFastGuarantee config value still applies. Implements
5754 - Document the GiveGuardFlagTo_CVE_2011_2768_VulnerableRelays
5755 directory authority option (introduced in Tor 0.2.2.34).
5757 o Minor features (other):
5758 - Don't disable the DirPort when we cannot exceed our AccountingMax
5759 limit during this interval because the effective bandwidthrate is
5760 low enough. This is useful in a situation where AccountMax is only
5761 used as an additional safeguard or to provide statistics.
5762 - Prepend an informative header to generated dynamic_dh_params files.
5763 - If EntryNodes are given, but UseEntryGuards is set to 0, warn that
5764 EntryNodes will have no effect. Resolves issue 2571.
5765 - Log more useful messages when we fail to disable debugger
5767 - Log which authority we're missing votes from when we go to fetch
5768 them from the other auths.
5769 - Log (at debug level) whenever a circuit's purpose is changed.
5770 - Add missing documentation for the MaxClientCircuitsPending,
5771 UseMicrodescriptors, UserspaceIOCPBuffers, and
5772 _UseFilteringSSLBufferevents options, all introduced during
5774 - Update to the January 3 2012 Maxmind GeoLite Country database.
5776 o Minor bugfixes (hidden services):
5777 - Don't close hidden service client circuits which have almost
5778 finished connecting to their destination when they reach
5779 the normal circuit-build timeout. Previously, we would close
5780 introduction circuits which are waiting for an acknowledgement
5781 from the introduction point, and rendezvous circuits which have
5782 been specified in an INTRODUCE1 cell sent to a hidden service,
5783 after the normal CBT. Now, we mark them as 'timed out', and launch
5784 another rendezvous attempt in parallel. This behavior change can
5785 be disabled using the new CloseHSClientCircuitsImmediatelyOnTimeout
5786 option. Fixes part of bug 1297; bugfix on 0.2.2.2-alpha.
5787 - Don't close hidden-service-side rendezvous circuits when they
5788 reach the normal circuit-build timeout. This behaviour change can
5789 be disabled using the new
5790 CloseHSServiceRendCircuitsImmediatelyOnTimeout option. Fixes the
5791 remaining part of bug 1297; bugfix on 0.2.2.2-alpha.
5792 - Make sure we never mark the wrong rendezvous circuit as having
5793 had its introduction cell acknowleged by the introduction-point
5794 relay. Previously, when we received an INTRODUCE_ACK cell on a
5795 client-side hidden-service introduction circuit, we might have
5796 marked a rendezvous circuit other than the one we specified in
5797 the INTRODUCE1 cell as INTRO_ACKED, which would have produced
5798 a warning message and interfered with the hidden service
5799 connection-establishment process. Fixes bug 4759; bugfix on
5800 0.2.3.3-alpha, when we added the stream-isolation feature which
5801 might cause Tor to open multiple rendezvous circuits for the same
5803 - Don't trigger an assertion failure when we mark a new client-side
5804 hidden-service introduction circuit for close during the process
5805 of creating it. Fixes bug 4796; bugfix on 0.2.3.6-alpha. Reported
5808 o Minor bugfixes (log messages):
5809 - Correctly spell "connect" in a log message on failure to create a
5810 controlsocket. Fixes bug 4803; bugfix on 0.2.2.26-beta and
5812 - Fix a typo in a log message in rend_service_rendezvous_has_opened().
5813 Fixes bug 4856; bugfix on Tor 0.0.6.
5814 - Fix the log message describing how we work around discovering
5815 that our version is the ill-fated OpenSSL 0.9.8l. Fixes bug
5816 4837; bugfix on 0.2.2.9-alpha.
5817 - When logging about a disallowed .exit name, do not also call it
5818 an "invalid onion address". Fixes bug 3325; bugfix on 0.2.2.9-alpha.
5820 o Minor bugfixes (build fixes):
5821 - During configure, detect when we're building with clang version
5822 3.0 or lower and disable the -Wnormalized=id and -Woverride-init
5823 CFLAGS. clang doesn't support them yet.
5824 - During configure, search for library containing cos function as
5825 libm lives in libcore on some platforms (BeOS/Haiku). Linking
5826 against libm was hard-coded before. Fixes the first part of bug
5827 4727; bugfix on 0.2.2.2-alpha. Patch and analysis by Martin Hebnes
5829 - Detect attempts to build Tor on (as yet hypothetical) versions
5830 of Windows where sizeof(intptr_t) != sizeof(SOCKET). Partial
5831 fix for bug 4533. Bugfix on 0.2.2.28-beta.
5832 - Preprocessor directives should not be put inside the arguments
5833 of a macro. This would break compilation with GCC releases prior
5834 to version 3.3. We would never recommend such an old GCC version,
5835 but it is apparently required for binary compatibility on some
5836 platforms (namely, certain builds of Haiku). Fixes the other part
5837 of bug 4727; bugfix on 0.2.3.3-alpha. Patch and analysis by Martin
5840 o Minor bugfixes (other):
5841 - Older Linux kernels erroneously respond to strange nmap behavior
5842 by having accept() return successfully with a zero-length
5843 socket. When this happens, just close the connection. Previously,
5844 we would try harder to learn the remote address: but there was
5845 no such remote address to learn, and our method for trying to
5846 learn it was incorrect. Fixes bugs 1240, 4745, and 4747. Bugfix
5847 on 0.1.0.3-rc. Reported and diagnosed by "r1eo".
5848 - Fix null-pointer access that could occur if TLS allocation failed.
5849 Fixes bug 4531; bugfix on 0.2.0.20-rc. Found by "troll_un". This was
5850 erroneously listed as fixed in 0.2.3.9-alpha, but the fix had
5851 accidentally been reverted.
5852 - Fix our implementation of crypto_random_hostname() so it can't
5853 overflow on ridiculously large inputs. (No Tor version has ever
5854 provided this kind of bad inputs, but let's be correct in depth.)
5855 Fixes bug 4413; bugfix on 0.2.2.9-alpha. Fix by Stephen Palmateer.
5856 - Find more places in the code that should have been testing for
5857 invalid sockets using the SOCKET_OK macro. Required for a fix
5858 for bug 4533. Bugfix on 0.2.2.28-beta.
5859 - Fix an assertion failure when, while running with bufferevents, a
5860 connection finishes connecting after it is marked for close, but
5861 before it is closed. Fixes bug 4697; bugfix on 0.2.3.1-alpha.
5862 - test_util_spawn_background_ok() hardcoded the expected value
5863 for ENOENT to 2. This isn't portable as error numbers are
5864 platform specific, and particularly the hurd has ENOENT at
5865 0x40000002. Construct expected string at runtime, using the correct
5866 value for ENOENT. Fixes bug 4733; bugfix on 0.2.3.1-alpha.
5867 - Reject attempts to disable DisableDebuggerAttachment while Tor is
5868 running. Fixes bug 4650; bugfix on 0.2.3.9-alpha.
5869 - Use an appropriate-width type for sockets in tor-fw-helper on
5870 win64. Fixes bug 1983 at last. Bugfix on 0.2.3.9-alpha.
5873 - When sending or relaying a RELAY_EARLY cell, we used to convert
5874 it to a RELAY cell if the connection was using the v1 link
5875 protocol. This was a workaround for older versions of Tor, which
5876 didn't handle RELAY_EARLY cells properly. Now that all supported
5877 versions can handle RELAY_EARLY cells, and now that we're enforcing
5878 the "no RELAY_EXTEND commands except in RELAY_EARLY cells" rule,
5879 remove this workaround. Addresses bug 4786.
5881 o Code simplifications and refactoring:
5882 - Use OpenSSL's built-in SSL_state_string_long() instead of our
5883 own homebrewed ssl_state_to_string() replacement. Patch from
5884 Emile Snyder. Fixes bug 4653.
5885 - Use macros to indicate OpenSSL versions, so we don't need to worry
5886 about accidental hexadecimal bit shifts.
5887 - Remove some workaround code for OpenSSL 0.9.6 (which is no longer
5889 - Convert more instances of tor_snprintf+tor_strdup into tor_asprintf.
5890 - Use the smartlist_add_asprintf() alias more consistently.
5891 - Use a TOR_INVALID_SOCKET macro when initializing a socket to an
5892 invalid value, rather than just -1.
5893 - Rename a handful of old identifiers, mostly related to crypto
5894 structures and crypto functions. By convention, our "create an
5895 object" functions are called "type_new()", our "free an object"
5896 functions are called "type_free()", and our types indicate that
5897 they are types only with a final "_t". But a handful of older
5898 types and functions broke these rules, with function names like
5899 "type_create" or "subsystem_op_type", or with type names like
5903 Changes in version 0.2.3.10-alpha - 2011-12-16
5904 Tor 0.2.3.10-alpha fixes a critical heap-overflow security issue in
5905 Tor's buffers code. Absolutely everybody should upgrade.
5907 The bug relied on an incorrect calculation when making data continuous
5908 in one of our IO buffers, if the first chunk of the buffer was
5909 misaligned by just the wrong amount. The miscalculation would allow an
5910 attacker to overflow a piece of heap-allocated memory. To mount this
5911 attack, the attacker would need to either open a SOCKS connection to
5912 Tor's SocksPort (usually restricted to localhost), or target a Tor
5913 instance configured to make its connections through a SOCKS proxy
5914 (which Tor does not do by default).
5916 Good security practice requires that all heap-overflow bugs should be
5917 presumed to be exploitable until proven otherwise, so we are treating
5918 this as a potential code execution attack. Please upgrade immediately!
5919 This bug does not affect bufferevents-based builds of Tor. Special
5920 thanks to "Vektor" for reporting this issue to us!
5922 This release also contains a few minor bugfixes for issues discovered
5926 - Fix a heap overflow bug that could occur when trying to pull
5927 data into the first chunk of a buffer, when that chunk had
5928 already had some data drained from it. Fixes CVE-2011-2778;
5929 bugfix on 0.2.0.16-alpha. Reported by "Vektor".
5932 - If we can't attach streams to a rendezvous circuit when we
5933 finish connecting to a hidden service, clear the rendezvous
5934 circuit's stream-isolation state and try to attach streams
5935 again. Previously, we cleared rendezvous circuits' isolation
5936 state either too early (if they were freshly built) or not at all
5937 (if they had been built earlier and were cannibalized). Bugfix on
5938 0.2.3.3-alpha; fixes bug 4655.
5939 - Fix compilation of the libnatpmp helper on non-Windows. Bugfix on
5940 0.2.3.9-alpha; fixes bug 4691. Reported by Anthony G. Basile.
5941 - Fix an assertion failure when a relay with accounting enabled
5942 starts up while dormant. Fixes bug 4702; bugfix on 0.2.3.9-alpha.
5945 - Update to the December 6 2011 Maxmind GeoLite Country database.
5948 Changes in version 0.2.2.35 - 2011-12-16
5949 Tor 0.2.2.35 fixes a critical heap-overflow security issue in Tor's
5950 buffers code. Absolutely everybody should upgrade.
5952 The bug relied on an incorrect calculation when making data continuous
5953 in one of our IO buffers, if the first chunk of the buffer was
5954 misaligned by just the wrong amount. The miscalculation would allow an
5955 attacker to overflow a piece of heap-allocated memory. To mount this
5956 attack, the attacker would need to either open a SOCKS connection to
5957 Tor's SocksPort (usually restricted to localhost), or target a Tor
5958 instance configured to make its connections through a SOCKS proxy
5959 (which Tor does not do by default).
5961 Good security practice requires that all heap-overflow bugs should be
5962 presumed to be exploitable until proven otherwise, so we are treating
5963 this as a potential code execution attack. Please upgrade immediately!
5964 This bug does not affect bufferevents-based builds of Tor. Special
5965 thanks to "Vektor" for reporting this issue to us!
5967 Tor 0.2.2.35 also fixes several bugs in previous versions, including
5968 crash bugs for unusual configurations, and a long-term bug that
5969 would prevent Tor from starting on Windows machines with draconian
5972 With this release, we remind everyone that 0.2.0.x has reached its
5973 formal end-of-life. Those Tor versions have many known flaws, and
5974 nobody should be using them. You should upgrade -- ideally to the
5975 0.2.2.x series. If you're using a Linux or BSD and its packages are
5976 obsolete, stop using those packages and upgrade anyway.
5978 The Tor 0.2.1.x series is also approaching its end-of-life: it will no
5979 longer receive support after some time in early 2012.
5982 - Fix a heap overflow bug that could occur when trying to pull
5983 data into the first chunk of a buffer, when that chunk had
5984 already had some data drained from it. Fixes CVE-2011-2778;
5985 bugfix on 0.2.0.16-alpha. Reported by "Vektor".
5986 - Initialize Libevent with the EVENT_BASE_FLAG_NOLOCK flag enabled, so
5987 that it doesn't attempt to allocate a socketpair. This could cause
5988 some problems on Windows systems with overzealous firewalls. Fix for
5989 bug 4457; workaround for Libevent versions 2.0.1-alpha through
5991 - If we mark an OR connection for close based on a cell we process,
5992 don't process any further cells on it. We already avoid further
5993 reads on marked-for-close connections, but now we also discard the
5994 cells we'd already read. Fixes bug 4299; bugfix on 0.2.0.10-alpha,
5995 which was the first version where we might mark a connection for
5996 close based on processing a cell on it.
5997 - Correctly sanity-check that we don't underflow on a memory
5998 allocation (and then assert) for hidden service introduction
5999 point decryption. Bug discovered by Dan Rosenberg. Fixes bug 4410;
6000 bugfix on 0.2.1.5-alpha.
6001 - Fix a memory leak when we check whether a hidden service
6002 descriptor has any usable introduction points left. Fixes bug
6003 4424. Bugfix on 0.2.2.25-alpha.
6004 - Don't crash when we're running as a relay and don't have a GeoIP
6005 file. Bugfix on 0.2.2.34; fixes bug 4340. This backports a fix
6006 we've had in the 0.2.3.x branch already.
6007 - When running as a client, do not print a misleading (and plain
6008 wrong) log message that we're collecting "directory request"
6009 statistics: clients don't collect statistics. Also don't create a
6010 useless (because empty) stats file in the stats/ directory. Fixes
6011 bug 4353; bugfix on 0.2.2.34.
6014 - Detect failure to initialize Libevent. This fix provides better
6015 detection for future instances of bug 4457.
6016 - Avoid frequent calls to the fairly expensive cull_wedged_cpuworkers
6017 function. This was eating up hideously large amounts of time on some
6018 busy servers. Fixes bug 4518; bugfix on 0.0.9.8.
6019 - Resolve an integer overflow bug in smartlist_ensure_capacity().
6020 Fixes bug 4230; bugfix on Tor 0.1.0.1-rc. Based on a patch by
6022 - Don't warn about unused log_mutex in log.c when building with
6023 --disable-threads using a recent GCC. Fixes bug 4437; bugfix on
6024 0.1.0.6-rc which introduced --disable-threads.
6025 - When configuring, starting, or stopping an NT service, stop
6026 immediately after the service configuration attempt has succeeded
6027 or failed. Fixes bug 3963; bugfix on 0.2.0.7-alpha.
6028 - When sending a NETINFO cell, include the original address
6029 received for the other side, not its canonical address. Found
6030 by "troll_un"; fixes bug 4349; bugfix on 0.2.0.10-alpha.
6031 - Fix a typo in a hibernation-related log message. Fixes bug 4331;
6032 bugfix on 0.2.2.23-alpha; found by "tmpname0901".
6033 - Fix a memory leak in launch_direct_bridge_descriptor_fetch() that
6034 occurred when a client tried to fetch a descriptor for a bridge
6035 in ExcludeNodes. Fixes bug 4383; bugfix on 0.2.2.25-alpha.
6036 - Backport fixes for a pair of compilation warnings on Windows.
6037 Fixes bug 4521; bugfix on 0.2.2.28-beta and on 0.2.2.29-beta.
6038 - If we had ever tried to call tor_addr_to_str on an address of
6039 unknown type, we would have done a strdup on an uninitialized
6040 buffer. Now we won't. Fixes bug 4529; bugfix on 0.2.1.3-alpha.
6041 Reported by "troll_un".
6042 - Correctly detect and handle transient lookup failures from
6043 tor_addr_lookup. Fixes bug 4530; bugfix on 0.2.1.5-alpha.
6044 Reported by "troll_un".
6045 - Fix null-pointer access that could occur if TLS allocation failed.
6046 Fixes bug 4531; bugfix on 0.2.0.20-rc. Found by "troll_un".
6047 - Use tor_socket_t type for listener argument to accept(). Fixes bug
6048 4535; bugfix on 0.2.2.28-beta. Found by "troll_un".
6051 - Add two new config options for directory authorities:
6052 AuthDirFastGuarantee sets a bandwidth threshold for guaranteeing the
6053 Fast flag, and AuthDirGuardBWGuarantee sets a bandwidth threshold
6054 that is always sufficient to satisfy the bandwidth requirement for
6055 the Guard flag. Now it will be easier for researchers to simulate
6056 Tor networks with different values. Resolves ticket 4484.
6057 - When Tor ignores a hidden service specified in its configuration,
6058 include the hidden service's directory in the warning message.
6059 Previously, we would only tell the user that some hidden service
6060 was ignored. Bugfix on 0.0.6; fixes bug 4426.
6061 - Update to the December 6 2011 Maxmind GeoLite Country database.
6063 o Packaging changes:
6064 - Make it easier to automate expert package builds on Windows,
6065 by removing an absolute path from makensis.exe command.
6068 Changes in version 0.2.1.32 - 2011-12-16
6069 Tor 0.2.1.32 backports important security and privacy fixes for
6070 oldstable. This release is intended only for package maintainers and
6071 others who cannot use the 0.2.2 stable series. All others should be
6072 using Tor 0.2.2.x or newer.
6074 The Tor 0.2.1.x series will reach formal end-of-life some time in
6075 early 2012; we will stop releasing patches for it then.
6077 o Major bugfixes (also included in 0.2.2.x):
6078 - Correctly sanity-check that we don't underflow on a memory
6079 allocation (and then assert) for hidden service introduction
6080 point decryption. Bug discovered by Dan Rosenberg. Fixes bug 4410;
6081 bugfix on 0.2.1.5-alpha.
6082 - Fix a heap overflow bug that could occur when trying to pull
6083 data into the first chunk of a buffer, when that chunk had
6084 already had some data drained from it. Fixes CVE-2011-2778;
6085 bugfix on 0.2.0.16-alpha. Reported by "Vektor".
6088 - Update to the December 6 2011 Maxmind GeoLite Country database.
6091 Changes in version 0.2.3.9-alpha - 2011-12-08
6092 Tor 0.2.3.9-alpha introduces initial IPv6 support for bridges, adds
6093 a "DisableNetwork" security feature that bundles can use to avoid
6094 touching the network until bridges are configured, moves forward on
6095 the pluggable transport design, fixes a flaw in the hidden service
6096 design that unnecessarily prevented clients with wrong clocks from
6097 reaching hidden services, and fixes a wide variety of other issues.
6100 - Clients can now connect to private bridges over IPv6. Bridges
6101 still need at least one IPv4 address in order to connect to
6102 other relays. Note that we don't yet handle the case where the
6103 user has two bridge lines for the same bridge (one IPv4, one
6104 IPv6). Implements parts of proposal 186.
6105 - New "DisableNetwork" config option to prevent Tor from launching any
6106 connections or accepting any connections except on a control port.
6107 Bundles and controllers can set this option before letting Tor talk
6108 to the rest of the network, for example to prevent any connections
6109 to a non-bridge address. Packages like Orbot can also use this
6110 option to instruct Tor to save power when the network is off.
6111 - Clients and bridges can now be configured to use a separate
6112 "transport" proxy. This approach makes the censorship arms race
6113 easier by allowing bridges to use protocol obfuscation plugins. It
6114 implements the "managed proxy" part of proposal 180 (ticket 3472).
6115 - When using OpenSSL 1.0.0 or later, use OpenSSL's counter mode
6116 implementation. It makes AES_CTR about 7% faster than our old one
6117 (which was about 10% faster than the one OpenSSL used to provide).
6118 Resolves ticket 4526.
6119 - Add a "tor2web mode" for clients that want to connect to hidden
6120 services non-anonymously (and possibly more quickly). As a safety
6121 measure to try to keep users from turning this on without knowing
6122 what they are doing, tor2web mode must be explicitly enabled at
6123 compile time, and a copy of Tor compiled to run in tor2web mode
6124 cannot be used as a normal Tor client. Implements feature 2553.
6125 - Add experimental support for running on Windows with IOCP and no
6126 kernel-space socket buffers. This feature is controlled by a new
6127 "UserspaceIOCPBuffers" config option (off by default), which has
6128 no effect unless Tor has been built with support for bufferevents,
6129 is running on Windows, and has enabled IOCP. This may, in the long
6130 run, help solve or mitigate bug 98.
6131 - Use a more secure consensus parameter voting algorithm. Now at
6132 least three directory authorities or a majority of them must
6133 vote on a given parameter before it will be included in the
6134 consensus. Implements proposal 178.
6137 - Hidden services now ignore the timestamps on INTRODUCE2 cells.
6138 They used to check that the timestamp was within 30 minutes
6139 of their system clock, so they could cap the size of their
6140 replay-detection cache, but that approach unnecessarily refused
6141 service to clients with wrong clocks. Bugfix on 0.2.1.6-alpha, when
6142 the v3 intro-point protocol (the first one which sent a timestamp
6143 field in the INTRODUCE2 cell) was introduced; fixes bug 3460.
6144 - Only use the EVP interface when AES acceleration is enabled,
6145 to avoid a 5-7% performance regression. Resolves issue 4525;
6146 bugfix on 0.2.3.8-alpha.
6148 o Privacy/anonymity features (bridge detection):
6149 - Make bridge SSL certificates a bit more stealthy by using random
6150 serial numbers, in the same fashion as OpenSSL when generating
6151 self-signed certificates. Implements ticket 4584.
6152 - Introduce a new config option "DynamicDHGroups", enabled by
6153 default, which provides each bridge with a unique prime DH modulus
6154 to be used during SSL handshakes. This option attempts to help
6155 against censors who might use the Apache DH modulus as a static
6156 identifier for bridges. Addresses ticket 4548.
6158 o Minor features (new/different config options):
6159 - New configuration option "DisableDebuggerAttachment" (on by default)
6160 to prevent basic debugging attachment attempts by other processes.
6161 Supports Mac OS X and Gnu/Linux. Resolves ticket 3313.
6162 - Allow MapAddress directives to specify matches against super-domains,
6163 as in "MapAddress *.torproject.org *.torproject.org.torserver.exit".
6164 Implements issue 933.
6165 - Slightly change behavior of "list" options (that is, config
6166 options that can appear more than once) when they appear both in
6167 torrc and on the command line. Previously, the command-line options
6168 would be appended to the ones from torrc. Now, the command-line
6169 options override the torrc options entirely. This new behavior
6170 allows the user to override list options (like exit policies and
6171 ports to listen on) from the command line, rather than simply
6172 appending to the list.
6173 - You can get the old (appending) command-line behavior for "list"
6174 options by prefixing the option name with a "+".
6175 - You can remove all the values for a "list" option from the command
6176 line without adding any new ones by prefixing the option name
6178 - Add experimental support for a "defaults" torrc file to be parsed
6179 before the regular torrc. Torrc options override the defaults file's
6180 options in the same way that the command line overrides the torrc.
6181 The SAVECONF controller command saves only those options which
6182 differ between the current configuration and the defaults file. HUP
6183 reloads both files. (Note: This is an experimental feature; its
6184 behavior will probably be refined in future 0.2.3.x-alpha versions
6185 to better meet packagers' needs.) Implements task 4552.
6188 - Try to make the introductory warning message that Tor prints on
6189 startup more useful for actually finding help and information.
6190 Resolves ticket 2474.
6191 - Running "make version" now displays the version of Tor that
6192 we're about to build. Idea from katmagic; resolves issue 4400.
6193 - Expire old or over-used hidden service introduction points.
6194 Required by fix for bug 3460.
6195 - Move the replay-detection cache for the RSA-encrypted parts of
6196 INTRODUCE2 cells to the introduction point data structures.
6197 Previously, we would use one replay-detection cache per hidden
6198 service. Required by fix for bug 3460.
6199 - Reduce the lifetime of elements of hidden services' Diffie-Hellman
6200 public key replay-detection cache from 60 minutes to 5 minutes. This
6201 replay-detection cache is now used only to detect multiple
6202 INTRODUCE2 cells specifying the same rendezvous point, so we can
6203 avoid launching multiple simultaneous attempts to connect to it.
6205 o Minor bugfixes (on Tor 0.2.2.x and earlier):
6206 - Resolve an integer overflow bug in smartlist_ensure_capacity().
6207 Fixes bug 4230; bugfix on Tor 0.1.0.1-rc. Based on a patch by
6209 - Fix a minor formatting issue in one of tor-gencert's error messages.
6211 - Prevent a false positive from the check-spaces script, by disabling
6212 the "whitespace between function name and (" check for functions
6214 - Fix a log message suggesting that people contact a non-existent
6215 email address. Fixes bug 3448.
6216 - Fix null-pointer access that could occur if TLS allocation failed.
6217 Fixes bug 4531; bugfix on 0.2.0.20-rc. Found by "troll_un".
6218 - Report a real bootstrap problem to the controller on router
6219 identity mismatch. Previously we just said "foo", which probably
6220 made a lot of sense at the time. Fixes bug 4169; bugfix on
6222 - If we had ever tried to call tor_addr_to_str() on an address of
6223 unknown type, we would have done a strdup() on an uninitialized
6224 buffer. Now we won't. Fixes bug 4529; bugfix on 0.2.1.3-alpha.
6225 Reported by "troll_un".
6226 - Correctly detect and handle transient lookup failures from
6227 tor_addr_lookup(). Fixes bug 4530; bugfix on 0.2.1.5-alpha.
6228 Reported by "troll_un".
6229 - Use tor_socket_t type for listener argument to accept(). Fixes bug
6230 4535; bugfix on 0.2.2.28-beta. Found by "troll_un".
6231 - Initialize conn->addr to a valid state in spawn_cpuworker(). Fixes
6232 bug 4532; found by "troll_un".
6234 o Minor bugfixes (on Tor 0.2.3.x):
6235 - Fix a compile warning in tor_inet_pton(). Bugfix on 0.2.3.8-alpha;
6237 - Don't send two ESTABLISH_RENDEZVOUS cells when opening a new
6238 circuit for use as a hidden service client's rendezvous point.
6239 Fixes bugs 4641 and 4171; bugfix on 0.2.3.3-alpha. Diagnosed
6240 with help from wanoskarnet.
6241 - Restore behavior of overriding SocksPort, ORPort, and similar
6242 options from the command line. Bugfix on 0.2.3.3-alpha.
6245 - Properly handle the case where the build-tree is not the same
6246 as the source tree when generating src/common/common_sha1.i,
6247 src/or/micro-revision.i, and src/or/or_sha1.i. Fixes bug 3953;
6248 bugfix on 0.2.0.1-alpha.
6250 o Code simplifications, cleanups, and refactorings:
6251 - Remove the pure attribute from all functions that used it
6252 previously. In many cases we assigned it incorrectly, because the
6253 functions might assert or call impure functions, and we don't have
6254 evidence that keeping the pure attribute is worthwhile. Implements
6255 changes suggested in ticket 4421.
6256 - Remove some dead code spotted by coverity. Fixes cid 432.
6257 Bugfix on 0.2.3.1-alpha, closes bug 4637.
6260 Changes in version 0.2.3.8-alpha - 2011-11-22
6261 Tor 0.2.3.8-alpha fixes some crash and assert bugs, including a
6262 socketpair-related bug that has been bothering Windows users. It adds
6263 support to serve microdescriptors to controllers, so Vidalia's network
6264 map can resume listing relays (once Vidalia implements its side),
6265 and adds better support for hardware AES acceleration. Finally, it
6266 starts the process of adjusting the bandwidth cutoff for getting the
6267 "Fast" flag from 20KB to (currently) 32KB -- preliminary results show
6268 that tiny relays harm performance more than they help network capacity.
6271 - Initialize Libevent with the EVENT_BASE_FLAG_NOLOCK flag enabled, so
6272 that it doesn't attempt to allocate a socketpair. This could cause
6273 some problems on Windows systems with overzealous firewalls. Fix for
6274 bug 4457; workaround for Libevent versions 2.0.1-alpha through
6276 - Correctly sanity-check that we don't underflow on a memory
6277 allocation (and then assert) for hidden service introduction
6278 point decryption. Bug discovered by Dan Rosenberg. Fixes bug 4410;
6279 bugfix on 0.2.1.5-alpha.
6280 - Remove the artificially low cutoff of 20KB to guarantee the Fast
6281 flag. In the past few years the average relay speed has picked
6282 up, and while the "top 7/8 of the network get the Fast flag" and
6283 "all relays with 20KB or more of capacity get the Fast flag" rules
6284 used to have the same result, now the top 7/8 of the network has
6285 a capacity more like 32KB. Bugfix on 0.2.1.14-rc. Fixes bug 4489.
6286 - Fix a rare assertion failure when checking whether a v0 hidden
6287 service descriptor has any usable introduction points left, and
6288 we don't have enough information to build a circuit to the first
6289 intro point named in the descriptor. The HS client code in
6290 0.2.3.x no longer uses v0 HS descriptors, but this assertion can
6291 trigger on (and crash) v0 HS authorities. Fixes bug 4411.
6292 Bugfix on 0.2.3.1-alpha; diagnosed by frosty_un.
6293 - Make bridge authorities not crash when they are asked for their own
6294 descriptor. Bugfix on 0.2.3.7-alpha, reported by Lucky Green.
6295 - When running as a client, do not print a misleading (and plain
6296 wrong) log message that we're collecting "directory request"
6297 statistics: clients don't collect statistics. Also don't create a
6298 useless (because empty) stats file in the stats/ directory. Fixes
6299 bug 4353; bugfix on 0.2.2.34 and 0.2.3.7-alpha.
6302 - Allow Tor controllers like Vidalia to obtain the microdescriptor
6303 for a relay by identity digest or nickname. Previously,
6304 microdescriptors were only available by their own digests, so a
6305 controller would have to ask for and parse the whole microdescriptor
6306 consensus in order to look up a single relay's microdesc. Fixes
6307 bug 3832; bugfix on 0.2.3.1-alpha.
6308 - Use OpenSSL's EVP interface for AES encryption, so that all AES
6309 operations can use hardware acceleration (if present). Resolves
6312 o Minor bugfixes (on 0.2.2.x and earlier):
6313 - Detect failure to initialize Libevent. This fix provides better
6314 detection for future instances of bug 4457.
6315 - Avoid frequent calls to the fairly expensive cull_wedged_cpuworkers
6316 function. This was eating up hideously large amounts of time on some
6317 busy servers. Fixes bug 4518; bugfix on 0.0.9.8.
6318 - Don't warn about unused log_mutex in log.c when building with
6319 --disable-threads using a recent GCC. Fixes bug 4437; bugfix on
6320 0.1.0.6-rc which introduced --disable-threads.
6321 - Allow manual 'authenticate' commands to the controller interface
6322 from netcat (nc) as well as telnet. We were rejecting them because
6323 they didn't come with the expected whitespace at the end of the
6324 command. Bugfix on 0.1.1.1-alpha; fixes bug 2893.
6325 - Fix some (not actually triggerable) buffer size checks in usage of
6326 tor_inet_ntop. Fixes bug 4434; bugfix on Tor 0.2.0.1-alpha. Patch
6328 - Fix parsing of some corner-cases with tor_inet_pton(). Fixes
6329 bug 4515; bugfix on 0.2.0.1-alpha; fix by Anders Sundman.
6330 - When configuring, starting, or stopping an NT service, stop
6331 immediately after the service configuration attempt has succeeded
6332 or failed. Fixes bug 3963; bugfix on 0.2.0.7-alpha.
6333 - When sending a NETINFO cell, include the original address
6334 received for the other side, not its canonical address. Found
6335 by "troll_un"; fixes bug 4349; bugfix on 0.2.0.10-alpha.
6336 - Rename the bench_{aes,dmap} functions to test_*, so that tinytest
6337 can pick them up when the tests aren't disabled. Bugfix on
6338 0.2.2.4-alpha which introduced tinytest.
6339 - Fix a memory leak when we check whether a hidden service
6340 descriptor has any usable introduction points left. Fixes bug
6341 4424. Bugfix on 0.2.2.25-alpha.
6342 - Fix a memory leak in launch_direct_bridge_descriptor_fetch() that
6343 occurred when a client tried to fetch a descriptor for a bridge
6344 in ExcludeNodes. Fixes bug 4383; bugfix on 0.2.2.25-alpha.
6346 o Minor bugfixes (on 0.2.3.x):
6347 - Make util unit tests build correctly with MSVC. Bugfix on
6348 0.2.3.3-alpha. Patch by Gisle Vanem.
6349 - Successfully detect AUTH_CHALLENGE cells with no recognized
6350 authentication type listed. Fixes bug 4367; bugfix on 0.2.3.6-alpha.
6352 - If a relay receives an AUTH_CHALLENGE cell it can't answer,
6353 it should still send a NETINFO cell to allow the connection to
6354 become open. Fixes bug 4368; fix on 0.2.3.6-alpha; bug found by
6356 - Log less loudly when we get an invalid authentication certificate
6357 from a source other than a directory authority: it's not unusual
6358 to see invalid certs because of clock skew. Fixes bug 4370; bugfix
6360 - Tolerate servers with more clock skew in their authentication
6361 certificates than previously. Fixes bug 4371; bugfix on
6363 - Fix a couple of compile warnings on Windows. Fixes bug 4469; bugfix
6364 on 0.2.3.4-alpha and 0.2.3.6-alpha.
6367 - Add two new config options for directory authorities:
6368 AuthDirFastGuarantee sets a bandwidth threshold for guaranteeing the
6369 Fast flag, and AuthDirGuardBWGuarantee sets a bandwidth threshold
6370 that is always sufficient to satisfy the bandwidth requirement for
6371 the Guard flag. Now it will be easier for researchers to simulate
6372 Tor networks with different values. Resolves ticket 4484.
6373 - When Tor ignores a hidden service specified in its configuration,
6374 include the hidden service's directory in the warning message.
6375 Previously, we would only tell the user that some hidden service
6376 was ignored. Bugfix on 0.0.6; fixes bug 4426.
6377 - When we fail to initialize Libevent, retry with IOCP disabled so we
6378 don't need to turn on multi-threading support in Libevent, which in
6379 turn requires a working socketpair(). This is a workaround for bug
6380 4457, which affects Libevent versions from 2.0.1-alpha through
6382 - Detect when we try to build on a platform that doesn't define
6383 AF_UNSPEC to 0. We don't work there, so refuse to compile.
6384 - Update to the November 1 2011 Maxmind GeoLite Country database.
6386 o Packaging changes:
6387 - Make it easier to automate expert package builds on Windows,
6388 by removing an absolute path from makensis.exe command.
6390 o Code simplifications and refactoring:
6391 - Remove some redundant #include directives throughout the code.
6392 Patch from Andrea Gelmini.
6393 - Unconditionally use OpenSSL's AES implementation instead of our
6394 old built-in one. OpenSSL's AES has been better for a while, and
6395 relatively few servers should still be on any version of OpenSSL
6396 that doesn't have good optimized assembly AES.
6397 - Use the name "CERTS" consistently to refer to the new cell type;
6398 we were calling it CERT in some places and CERTS in others.
6401 - Numerous new unit tests for functions in util.c and address.c by
6403 - The long-disabled benchmark tests are now split into their own
6404 ./src/test/bench binary.
6405 - The benchmark tests can now use more accurate timers than
6406 gettimeofday() when such timers are available.
6409 Changes in version 0.2.3.7-alpha - 2011-10-30
6410 Tor 0.2.3.7-alpha fixes a crash bug in 0.2.3.6-alpha introduced by
6411 the new v3 handshake. It also resolves yet another bridge address
6415 - If we mark an OR connection for close based on a cell we process,
6416 don't process any further cells on it. We already avoid further
6417 reads on marked-for-close connections, but now we also discard the
6418 cells we'd already read. Fixes bug 4299; bugfix on 0.2.0.10-alpha,
6419 which was the first version where we might mark a connection for
6420 close based on processing a cell on it.
6421 - Fix a double-free bug that would occur when we received an invalid
6422 certificate in a CERT cell in the new v3 handshake. Fixes bug 4343;
6423 bugfix on 0.2.3.6-alpha.
6424 - Bridges no longer include their address in NETINFO cells on outgoing
6425 OR connections, to allow them to blend in better with clients.
6426 Removes another avenue for enumerating bridges. Reported by
6427 "troll_un". Fixes bug 4348; bugfix on 0.2.0.10-alpha, when NETINFO
6428 cells were introduced.
6431 - Fixed a typo in a hibernation-related log message. Fixes bug 4331;
6432 bugfix on 0.2.2.23-alpha; found by "tmpname0901".
6435 Changes in version 0.2.3.6-alpha - 2011-10-26
6436 Tor 0.2.3.6-alpha includes the fix from 0.2.2.34 for a critical
6437 anonymity vulnerability where an attacker can deanonymize Tor
6438 users. Everybody should upgrade.
6440 This release also features support for a new v3 connection handshake
6441 protocol, and fixes to make hidden service connections more robust.
6444 - Implement a new handshake protocol (v3) for authenticating Tors to
6445 each other over TLS. It should be more resistant to fingerprinting
6446 than previous protocols, and should require less TLS hacking for
6447 future Tor implementations. Implements proposal 176.
6448 - Allow variable-length padding cells to disguise the length of
6449 Tor's TLS records. Implements part of proposal 184.
6451 o Privacy/anonymity fixes (clients):
6452 - Clients and bridges no longer send TLS certificate chains on
6453 outgoing OR connections. Previously, each client or bridge would
6454 use the same cert chain for all outgoing OR connections until
6455 its IP address changes, which allowed any relay that the client
6456 or bridge contacted to determine which entry guards it is using.
6457 Fixes CVE-2011-2768. Bugfix on 0.0.9pre5; found by "frosty_un".
6458 - If a relay receives a CREATE_FAST cell on a TLS connection, it
6459 no longer considers that connection as suitable for satisfying a
6460 circuit EXTEND request. Now relays can protect clients from the
6461 CVE-2011-2768 issue even if the clients haven't upgraded yet.
6462 - Directory authorities no longer assign the Guard flag to relays
6463 that haven't upgraded to the above "refuse EXTEND requests
6464 to client connections" fix. Now directory authorities can
6465 protect clients from the CVE-2011-2768 issue even if neither
6466 the clients nor the relays have upgraded yet. There's a new
6467 "GiveGuardFlagTo_CVE_2011_2768_VulnerableRelays" config option
6468 to let us transition smoothly, else tomorrow there would be no
6471 o Major bugfixes (hidden services):
6472 - Improve hidden service robustness: when an attempt to connect to
6473 a hidden service ends, be willing to refetch its hidden service
6474 descriptors from each of the HSDir relays responsible for them
6475 immediately. Previously, we would not consider refetching the
6476 service's descriptors from each HSDir for 15 minutes after the last
6477 fetch, which was inconvenient if the hidden service was not running
6478 during the first attempt. Bugfix on 0.2.0.18-alpha; fixes bug 3335.
6479 - When one of a hidden service's introduction points appears to be
6480 unreachable, stop trying it. Previously, we would keep trying
6481 to build circuits to the introduction point until we lost the
6482 descriptor, usually because the user gave up and restarted Tor.
6483 Partly fixes bug 3825.
6484 - Don't launch a useless circuit after failing to use one of a
6485 hidden service's introduction points. Previously, we would
6486 launch a new introduction circuit, but not set the hidden service
6487 which that circuit was intended to connect to, so it would never
6488 actually be used. A different piece of code would then create a
6489 new introduction circuit correctly. Bug reported by katmagic and
6490 found by Sebastian Hahn. Bugfix on 0.2.1.13-alpha; fixes bug 4212.
6492 o Major bugfixes (other):
6493 - Bridges now refuse CREATE or CREATE_FAST cells on OR connections
6494 that they initiated. Relays could distinguish incoming bridge
6495 connections from client connections, creating another avenue for
6496 enumerating bridges. Fixes CVE-2011-2769. Bugfix on 0.2.0.3-alpha.
6497 Found by "frosty_un".
6498 - Don't update the AccountingSoftLimitHitAt state file entry whenever
6499 tor gets started. This prevents a wrong average bandwidth
6500 estimate, which would cause relays to always start a new accounting
6501 interval at the earliest possible moment. Fixes bug 2003; bugfix
6502 on 0.2.2.7-alpha. Reported by BryonEldridge, who also helped
6503 immensely in tracking this bug down.
6504 - Fix a crash bug when changing node restrictions while a DNS lookup
6505 is in-progress. Fixes bug 4259; bugfix on 0.2.2.25-alpha. Bugfix
6508 o Minor bugfixes (on 0.2.2.x and earlier):
6509 - When a hidden service turns an extra service-side introduction
6510 circuit into a general-purpose circuit, free the rend_data and
6511 intro_key fields first, so we won't leak memory if the circuit
6512 is cannibalized for use as another service-side introduction
6513 circuit. Bugfix on 0.2.1.7-alpha; fixes bug 4251.
6514 - Rephrase the log message emitted if the TestSocks check is
6515 successful. Patch from Fabian Keil; fixes bug 4094.
6516 - Bridges now skip DNS self-tests, to act a little more stealthily.
6517 Fixes bug 4201; bugfix on 0.2.0.3-alpha, which first introduced
6518 bridges. Patch by "warms0x".
6519 - Remove a confusing dollar sign from the example fingerprint in the
6520 man page, and also make the example fingerprint a valid one. Fixes
6521 bug 4309; bugfix on 0.2.1.3-alpha.
6522 - Fix internal bug-checking logic that was supposed to catch
6523 failures in digest generation so that it will fail more robustly
6524 if we ask for a nonexistent algorithm. Found by Coverity Scan.
6525 Bugfix on 0.2.2.1-alpha; fixes Coverity CID 479.
6526 - Report any failure in init_keys() calls launched because our
6527 IP address has changed. Spotted by Coverity Scan. Bugfix on
6528 0.1.1.4-alpha; fixes CID 484.
6530 o Minor bugfixes (on 0.2.3.x):
6531 - Fix a bug in configure.in that kept it from building a configure
6532 script with autoconf versions earlier than 2.61. Fixes bug 2430;
6533 bugfix on 0.2.3.1-alpha.
6534 - Don't warn users that they are exposing a client port to the
6535 Internet if they have specified an RFC1918 address. Previously,
6536 we would warn if the user had specified any non-loopback
6537 address. Bugfix on 0.2.3.3-alpha. Fixes bug 4018; reported by Tas.
6538 - Fix memory leaks in the failing cases of the new SocksPort and
6539 ControlPort code. Found by Coverity Scan. Bugfix on 0.2.3.3-alpha;
6540 fixes coverity CIDs 485, 486, and 487.
6543 - When a hidden service's introduction point times out, consider
6544 trying it again during the next attempt to connect to the
6545 HS. Previously, we would not try it again unless a newly fetched
6546 descriptor contained it. Required by fixes for bugs 1297 and 3825.
6547 - The next version of Windows will be called Windows 8, and it has
6548 a major version of 6, minor version of 2. Correctly identify that
6549 version instead of calling it "Very recent version". Resolves
6550 ticket 4153; reported by funkstar.
6551 - The Bridge Authority now writes statistics on how many bridge
6552 descriptors it gave out in total, and how many unique descriptors
6553 it gave out. It also lists how often the most and least commonly
6554 fetched descriptors were given out, as well as the median and
6555 25th/75th percentile. Implements tickets 4200 and 4294.
6556 - Update to the October 4 2011 Maxmind GeoLite Country database.
6558 o Code simplifications and refactoring:
6559 - Remove some old code to remember statistics about which descriptors
6560 we've served as a directory mirror. The feature wasn't used and
6561 is outdated now that microdescriptors are around.
6562 - Rename Tor functions that turn strings into addresses, so that
6563 "parse" indicates that no hostname resolution occurs, and
6564 "lookup" indicates that hostname resolution may occur. This
6565 should help prevent mistakes in the future. Fixes bug 3512.
6568 Changes in version 0.2.2.34 - 2011-10-26
6569 Tor 0.2.2.34 fixes a critical anonymity vulnerability where an attacker
6570 can deanonymize Tor users. Everybody should upgrade.
6572 The attack relies on four components: 1) Clients reuse their TLS cert
6573 when talking to different relays, so relays can recognize a user by
6574 the identity key in her cert. 2) An attacker who knows the client's
6575 identity key can probe each guard relay to see if that identity key
6576 is connected to that guard relay right now. 3) A variety of active
6577 attacks in the literature (starting from "Low-Cost Traffic Analysis
6578 of Tor" by Murdoch and Danezis in 2005) allow a malicious website to
6579 discover the guard relays that a Tor user visiting the website is using.
6580 4) Clients typically pick three guards at random, so the set of guards
6581 for a given user could well be a unique fingerprint for her. This
6582 release fixes components #1 and #2, which is enough to block the attack;
6583 the other two remain as open research problems. Special thanks to
6584 "frosty_un" for reporting the issue to us!
6586 Clients should upgrade so they are no longer recognizable by the TLS
6587 certs they present. Relays should upgrade so they no longer allow a
6588 remote attacker to probe them to test whether unpatched clients are
6589 currently connected to them.
6591 This release also fixes several vulnerabilities that allow an attacker
6592 to enumerate bridge relays. Some bridge enumeration attacks still
6593 remain; see for example proposal 188.
6595 o Privacy/anonymity fixes (clients):
6596 - Clients and bridges no longer send TLS certificate chains on
6597 outgoing OR connections. Previously, each client or bridge would
6598 use the same cert chain for all outgoing OR connections until
6599 its IP address changes, which allowed any relay that the client
6600 or bridge contacted to determine which entry guards it is using.
6601 Fixes CVE-2011-2768. Bugfix on 0.0.9pre5; found by "frosty_un".
6602 - If a relay receives a CREATE_FAST cell on a TLS connection, it
6603 no longer considers that connection as suitable for satisfying a
6604 circuit EXTEND request. Now relays can protect clients from the
6605 CVE-2011-2768 issue even if the clients haven't upgraded yet.
6606 - Directory authorities no longer assign the Guard flag to relays
6607 that haven't upgraded to the above "refuse EXTEND requests
6608 to client connections" fix. Now directory authorities can
6609 protect clients from the CVE-2011-2768 issue even if neither
6610 the clients nor the relays have upgraded yet. There's a new
6611 "GiveGuardFlagTo_CVE_2011_2768_VulnerableRelays" config option
6612 to let us transition smoothly, else tomorrow there would be no
6615 o Privacy/anonymity fixes (bridge enumeration):
6616 - Bridge relays now do their directory fetches inside Tor TLS
6617 connections, like all the other clients do, rather than connecting
6618 directly to the DirPort like public relays do. Removes another
6619 avenue for enumerating bridges. Fixes bug 4115; bugfix on 0.2.0.35.
6620 - Bridges relays now build circuits for themselves in a more similar
6621 way to how clients build them. Removes another avenue for
6622 enumerating bridges. Fixes bug 4124; bugfix on 0.2.0.3-alpha,
6623 when bridges were introduced.
6624 - Bridges now refuse CREATE or CREATE_FAST cells on OR connections
6625 that they initiated. Relays could distinguish incoming bridge
6626 connections from client connections, creating another avenue for
6627 enumerating bridges. Fixes CVE-2011-2769. Bugfix on 0.2.0.3-alpha.
6628 Found by "frosty_un".
6631 - Fix a crash bug when changing node restrictions while a DNS lookup
6632 is in-progress. Fixes bug 4259; bugfix on 0.2.2.25-alpha. Bugfix
6634 - Don't launch a useless circuit after failing to use one of a
6635 hidden service's introduction points. Previously, we would
6636 launch a new introduction circuit, but not set the hidden service
6637 which that circuit was intended to connect to, so it would never
6638 actually be used. A different piece of code would then create a
6639 new introduction circuit correctly. Bug reported by katmagic and
6640 found by Sebastian Hahn. Bugfix on 0.2.1.13-alpha; fixes bug 4212.
6643 - Change an integer overflow check in the OpenBSD_Malloc code so
6644 that GCC is less likely to eliminate it as impossible. Patch
6645 from Mansour Moufid. Fixes bug 4059.
6646 - When a hidden service turns an extra service-side introduction
6647 circuit into a general-purpose circuit, free the rend_data and
6648 intro_key fields first, so we won't leak memory if the circuit
6649 is cannibalized for use as another service-side introduction
6650 circuit. Bugfix on 0.2.1.7-alpha; fixes bug 4251.
6651 - Bridges now skip DNS self-tests, to act a little more stealthily.
6652 Fixes bug 4201; bugfix on 0.2.0.3-alpha, which first introduced
6653 bridges. Patch by "warms0x".
6654 - Fix internal bug-checking logic that was supposed to catch
6655 failures in digest generation so that it will fail more robustly
6656 if we ask for a nonexistent algorithm. Found by Coverity Scan.
6657 Bugfix on 0.2.2.1-alpha; fixes Coverity CID 479.
6658 - Report any failure in init_keys() calls launched because our
6659 IP address has changed. Spotted by Coverity Scan. Bugfix on
6660 0.1.1.4-alpha; fixes CID 484.
6662 o Minor bugfixes (log messages and documentation):
6663 - Remove a confusing dollar sign from the example fingerprint in the
6664 man page, and also make the example fingerprint a valid one. Fixes
6665 bug 4309; bugfix on 0.2.1.3-alpha.
6666 - The next version of Windows will be called Windows 8, and it has
6667 a major version of 6, minor version of 2. Correctly identify that
6668 version instead of calling it "Very recent version". Resolves
6669 ticket 4153; reported by funkstar.
6670 - Downgrade log messages about circuit timeout calibration from
6671 "notice" to "info": they don't require or suggest any human
6672 intervention. Patch from Tom Lowenthal. Fixes bug 4063;
6673 bugfix on 0.2.2.14-alpha.
6676 - Turn on directory request statistics by default and include them in
6677 extra-info descriptors. Don't break if we have no GeoIP database.
6678 Backported from 0.2.3.1-alpha; implements ticket 3951.
6679 - Update to the October 4 2011 Maxmind GeoLite Country database.
6682 Changes in version 0.2.1.31 - 2011-10-26
6683 Tor 0.2.1.31 backports important security and privacy fixes for
6684 oldstable. This release is intended only for package maintainers and
6685 others who cannot use the 0.2.2 stable series. All others should be
6686 using Tor 0.2.2.x or newer.
6688 o Security fixes (also included in 0.2.2.x):
6689 - Replace all potentially sensitive memory comparison operations
6690 with versions whose runtime does not depend on the data being
6691 compared. This will help resist a class of attacks where an
6692 adversary can use variations in timing information to learn
6693 sensitive data. Fix for one case of bug 3122. (Safe memcmp
6694 implementation by Robert Ransom based partially on code by DJB.)
6695 - Fix an assert in parsing router descriptors containing IPv6
6696 addresses. This one took down the directory authorities when
6697 somebody tried some experimental code. Bugfix on 0.2.1.3-alpha.
6699 o Privacy/anonymity fixes (also included in 0.2.2.x):
6700 - Clients and bridges no longer send TLS certificate chains on
6701 outgoing OR connections. Previously, each client or bridge would
6702 use the same cert chain for all outgoing OR connections until
6703 its IP address changes, which allowed any relay that the client
6704 or bridge contacted to determine which entry guards it is using.
6705 Fixes CVE-2011-2768. Bugfix on 0.0.9pre5; found by "frosty_un".
6706 - If a relay receives a CREATE_FAST cell on a TLS connection, it
6707 no longer considers that connection as suitable for satisfying a
6708 circuit EXTEND request. Now relays can protect clients from the
6709 CVE-2011-2768 issue even if the clients haven't upgraded yet.
6710 - Bridges now refuse CREATE or CREATE_FAST cells on OR connections
6711 that they initiated. Relays could distinguish incoming bridge
6712 connections from client connections, creating another avenue for
6713 enumerating bridges. Fixes CVE-2011-2769. Bugfix on 0.2.0.3-alpha.
6714 Found by "frosty_un".
6715 - When receiving a hidden service descriptor, check that it is for
6716 the hidden service we wanted. Previously, Tor would store any
6717 hidden service descriptors that a directory gave it, whether it
6718 wanted them or not. This wouldn't have let an attacker impersonate
6719 a hidden service, but it did let directories pre-seed a client
6720 with descriptors that it didn't want. Bugfix on 0.0.6.
6721 - Avoid linkability based on cached hidden service descriptors: forget
6722 all hidden service descriptors cached as a client when processing a
6723 SIGNAL NEWNYM command. Fixes bug 3000; bugfix on 0.0.6.
6724 - Make the bridge directory authority refuse to answer directory
6725 requests for "all" descriptors. It used to include bridge
6726 descriptors in its answer, which was a major information leak.
6727 Found by "piebeer". Bugfix on 0.2.0.3-alpha.
6728 - Don't attach new streams to old rendezvous circuits after SIGNAL
6729 NEWNYM. Previously, we would keep using an existing rendezvous
6730 circuit if it remained open (i.e. if it were kept open by a
6731 long-lived stream, or if a new stream were attached to it before
6732 Tor could notice that it was old and no longer in use). Bugfix on
6733 0.1.1.15-rc; fixes bug 3375.
6735 o Minor bugfixes (also included in 0.2.2.x):
6736 - When we restart our relay, we might get a successful connection
6737 from the outside before we've started our reachability tests,
6738 triggering a warning: "ORPort found reachable, but I have no
6739 routerinfo yet. Failing to inform controller of success." This
6740 bug was harmless unless Tor is running under a controller
6741 like Vidalia, in which case the controller would never get a
6742 REACHABILITY_SUCCEEDED status event. Bugfix on 0.1.2.6-alpha;
6744 - Build correctly on OSX with zlib 1.2.4 and higher with all warnings
6745 enabled. Fixes bug 1526.
6746 - Remove undocumented option "-F" from tor-resolve: it hasn't done
6747 anything since 0.2.1.16-rc.
6748 - Avoid signed/unsigned comparisons by making SIZE_T_CEILING unsigned.
6749 None of the cases where we did this before were wrong, but by making
6750 this change we avoid warnings. Fixes bug 2475; bugfix on 0.2.1.28.
6751 - Fix a rare crash bug that could occur when a client was configured
6752 with a large number of bridges. Fixes bug 2629; bugfix on
6753 0.2.1.2-alpha. Bugfix by trac user "shitlei".
6754 - Correct the warning displayed when a rendezvous descriptor exceeds
6755 the maximum size. Fixes bug 2750; bugfix on 0.2.1.5-alpha. Found by
6757 - Fix an uncommon assertion failure when running with DNSPort under
6758 heavy load. Fixes bug 2933; bugfix on 0.2.0.1-alpha.
6759 - When warning about missing zlib development packages during compile,
6760 give the correct package names. Bugfix on 0.2.0.1-alpha.
6761 - Require that introduction point keys and onion keys have public
6762 exponent 65537. Bugfix on 0.2.0.10-alpha.
6763 - Do not crash when our configuration file becomes unreadable, for
6764 example due to a permissions change, between when we start up
6765 and when a controller calls SAVECONF. Fixes bug 3135; bugfix
6767 - Fix warnings from GCC 4.6's "-Wunused-but-set-variable" option.
6769 - Always NUL-terminate the sun_path field of a sockaddr_un before
6770 passing it to the kernel. (Not a security issue: kernels are
6771 smart enough to reject bad sockaddr_uns.) Found by Coverity;
6772 CID #428. Bugfix on Tor 0.2.0.3-alpha.
6773 - Don't stack-allocate the list of supplementary GIDs when we're
6774 about to log them. Stack-allocating NGROUPS_MAX gid_t elements
6775 could take up to 256K, which is way too much stack. Found by
6776 Coverity; CID #450. Bugfix on 0.2.1.7-alpha.
6778 o Minor bugfixes (only in 0.2.1.x):
6779 - Resume using micro-version numbers in 0.2.1.x: our Debian packages
6780 rely on them. Bugfix on 0.2.1.30.
6781 - Use git revisions instead of svn revisions when generating our
6782 micro-version numbers. Bugfix on 0.2.1.15-rc; fixes bug 2402.
6784 o Minor features (also included in 0.2.2.x):
6785 - Adjust the expiration time on our SSL session certificates to
6786 better match SSL certs seen in the wild. Resolves ticket 4014.
6787 - Allow nameservers with IPv6 address. Resolves bug 2574.
6788 - Update to the October 4 2011 Maxmind GeoLite Country database.
6791 Changes in version 0.2.3.5-alpha - 2011-09-28
6792 Tor 0.2.3.5-alpha fixes two bugs that make it possible to enumerate
6793 bridge relays; fixes an assertion error that many users started hitting
6794 today; and adds the ability to refill token buckets more often than
6795 once per second, allowing significant performance improvements.
6798 - Bridge relays now do their directory fetches inside Tor TLS
6799 connections, like all the other clients do, rather than connecting
6800 directly to the DirPort like public relays do. Removes another
6801 avenue for enumerating bridges. Fixes bug 4115; bugfix on 0.2.0.35.
6802 - Bridges relays now build circuits for themselves in a more similar
6803 way to how clients build them. Removes another avenue for
6804 enumerating bridges. Fixes bug 4124; bugfix on 0.2.0.3-alpha,
6805 when bridges were introduced.
6808 - Fix an "Assertion md->held_by_node == 1 failed" error that could
6809 occur when the same microdescriptor was referenced by two node_t
6810 objects at once. Fix for bug 4118; bugfix on Tor 0.2.3.1-alpha.
6812 o Major features (networking):
6813 - Add a new TokenBucketRefillInterval option to refill token buckets
6814 more frequently than once per second. This should improve network
6815 performance, alleviate queueing problems, and make traffic less
6816 bursty. Implements proposal 183; closes ticket 3630. Design by
6817 Florian Tschorsch and Björn Scheuermann; implementation by
6821 - Change an integer overflow check in the OpenBSD_Malloc code so
6822 that GCC is less likely to eliminate it as impossible. Patch
6823 from Mansour Moufid. Fixes bug 4059.
6825 o Minor bugfixes (usability):
6826 - Downgrade log messages about circuit timeout calibration from
6827 "notice" to "info": they don't require or suggest any human
6828 intervention. Patch from Tom Lowenthal. Fixes bug 4063;
6829 bugfix on 0.2.2.14-alpha.
6831 o Minor features (diagnostics):
6832 - When the system call to create a listener socket fails, log the
6833 error message explaining why. This may help diagnose bug 4027.
6836 Changes in version 0.2.3.4-alpha - 2011-09-13
6837 Tor 0.2.3.4-alpha includes the fixes from 0.2.2.33, including a slight
6838 tweak to Tor's TLS handshake that makes relays and bridges that run
6839 this new version reachable from Iran again. It also fixes a few new
6840 bugs in 0.2.3.x, and teaches relays to recognize when they're not
6841 listed in the network consensus and republish.
6843 o Major bugfixes (also part of 0.2.2.33):
6844 - Avoid an assertion failure when reloading a configuration with
6845 TrackExitHosts changes. Found and fixed by 'laruldan'. Fixes bug
6846 3923; bugfix on 0.2.2.25-alpha.
6848 o Minor features (security, also part of 0.2.2.33):
6849 - Check for replays of the public-key encrypted portion of an
6850 INTRODUCE1 cell, in addition to the current check for replays of
6851 the g^x value. This prevents a possible class of active attacks
6852 by an attacker who controls both an introduction point and a
6853 rendezvous point, and who uses the malleability of AES-CTR to
6854 alter the encrypted g^x portion of the INTRODUCE1 cell. We think
6855 that these attacks are infeasible (requiring the attacker to send
6856 on the order of zettabytes of altered cells in a short interval),
6857 but we'd rather block them off in case there are any classes of
6858 this attack that we missed. Reported by Willem Pinckaers.
6860 o Minor features (also part of 0.2.2.33):
6861 - Adjust the expiration time on our SSL session certificates to
6862 better match SSL certs seen in the wild. Resolves ticket 4014.
6863 - Change the default required uptime for a relay to be accepted as
6864 a HSDir (hidden service directory) from 24 hours to 25 hours.
6865 Improves on 0.2.0.10-alpha; resolves ticket 2649.
6866 - Add a VoteOnHidServDirectoriesV2 config option to allow directory
6867 authorities to abstain from voting on assignment of the HSDir
6868 consensus flag. Related to bug 2649.
6869 - Update to the September 6 2011 Maxmind GeoLite Country database.
6871 o Minor bugfixes (also part of 0.2.2.33):
6872 - Demote the 'replay detected' log message emitted when a hidden
6873 service receives the same Diffie-Hellman public key in two different
6874 INTRODUCE2 cells to info level. A normal Tor client can cause that
6875 log message during its normal operation. Bugfix on 0.2.1.6-alpha;
6876 fixes part of bug 2442.
6877 - Demote the 'INTRODUCE2 cell is too {old,new}' log message to info
6878 level. There is nothing that a hidden service's operator can do
6879 to fix its clients' clocks. Bugfix on 0.2.1.6-alpha; fixes part
6881 - Clarify a log message specifying the characters permitted in
6882 HiddenServiceAuthorizeClient client names. Previously, the log
6883 message said that "[A-Za-z0-9+-_]" were permitted; that could have
6884 given the impression that every ASCII character between "+" and "_"
6885 was permitted. Now we say "[A-Za-z0-9+_-]". Bugfix on 0.2.1.5-alpha.
6887 o Build fixes (also part of 0.2.2.33):
6888 - Clean up some code issues that prevented Tor from building on older
6889 BSDs. Fixes bug 3894; reported by "grarpamp".
6890 - Search for a platform-specific version of "ar" when cross-compiling.
6891 Should fix builds on iOS. Resolves bug 3909, found by Marco Bonetti.
6894 - Fix a bug where the SocksPort option (for example) would get
6895 ignored and replaced by the default if a SocksListenAddress
6896 option was set. Bugfix on 0.2.3.3-alpha; fixes bug 3936. Fix by
6900 - Relays now try regenerating and uploading their descriptor more
6901 frequently if they are not listed in the consensus, or if the
6902 version of their descriptor listed in the consensus is too
6903 old. This fix should prevent situations where a server declines
6904 to re-publish itself because it has done so too recently, even
6905 though the authorities decided not to list its recent-enough
6906 descriptor. Fix for bug 3327.
6909 - Relays now include a reason for regenerating their descriptors
6910 in an HTTP header when uploading to the authorities. This will
6911 make it easier to debug descriptor-upload issues in the future.
6912 - When starting as root and then changing our UID via the User
6913 control option, and we have a ControlSocket configured, make sure
6914 that the ControlSocket is owned by the same account that Tor will
6915 run under. Implements ticket 3421; fix by Jérémy Bobbio.
6918 - Abort if tor_vasprintf fails in connection_printf_to_buf (a
6919 utility function used in the control-port code). This shouldn't
6920 ever happen unless Tor is completely out of memory, but if it did
6921 happen and Tor somehow recovered from it, Tor could have sent a log
6922 message to a control port in the middle of a reply to a controller
6923 command. Fixes part of bug 3428; bugfix on 0.1.2.3-alpha.
6924 - Make 'FetchUselessDescriptors' cause all descriptor types and
6925 all consensus types (including microdescriptors) to get fetched.
6926 Fixes bug 3851; bugfix on 0.2.3.1-alpha.
6929 - Make a new "entry connection" struct as an internal subtype of "edge
6930 connection", to simplify the code and make exit connections smaller.
6933 Changes in version 0.2.2.33 - 2011-09-13
6934 Tor 0.2.2.33 fixes several bugs, and includes a slight tweak to Tor's
6935 TLS handshake that makes relays and bridges that run this new version
6936 reachable from Iran again.
6939 - Avoid an assertion failure when reloading a configuration with
6940 TrackExitHosts changes. Found and fixed by 'laruldan'. Fixes bug
6941 3923; bugfix on 0.2.2.25-alpha.
6943 o Minor features (security):
6944 - Check for replays of the public-key encrypted portion of an
6945 INTRODUCE1 cell, in addition to the current check for replays of
6946 the g^x value. This prevents a possible class of active attacks
6947 by an attacker who controls both an introduction point and a
6948 rendezvous point, and who uses the malleability of AES-CTR to
6949 alter the encrypted g^x portion of the INTRODUCE1 cell. We think
6950 that these attacks are infeasible (requiring the attacker to send
6951 on the order of zettabytes of altered cells in a short interval),
6952 but we'd rather block them off in case there are any classes of
6953 this attack that we missed. Reported by Willem Pinckaers.
6956 - Adjust the expiration time on our SSL session certificates to
6957 better match SSL certs seen in the wild. Resolves ticket 4014.
6958 - Change the default required uptime for a relay to be accepted as
6959 a HSDir (hidden service directory) from 24 hours to 25 hours.
6960 Improves on 0.2.0.10-alpha; resolves ticket 2649.
6961 - Add a VoteOnHidServDirectoriesV2 config option to allow directory
6962 authorities to abstain from voting on assignment of the HSDir
6963 consensus flag. Related to bug 2649.
6964 - Update to the September 6 2011 Maxmind GeoLite Country database.
6966 o Minor bugfixes (documentation and log messages):
6967 - Correct the man page to explain that HashedControlPassword and
6968 CookieAuthentication can both be set, in which case either method
6969 is sufficient to authenticate to Tor. Bugfix on 0.2.0.7-alpha,
6970 when we decided to allow these config options to both be set. Issue
6972 - Demote the 'replay detected' log message emitted when a hidden
6973 service receives the same Diffie-Hellman public key in two different
6974 INTRODUCE2 cells to info level. A normal Tor client can cause that
6975 log message during its normal operation. Bugfix on 0.2.1.6-alpha;
6976 fixes part of bug 2442.
6977 - Demote the 'INTRODUCE2 cell is too {old,new}' log message to info
6978 level. There is nothing that a hidden service's operator can do
6979 to fix its clients' clocks. Bugfix on 0.2.1.6-alpha; fixes part
6981 - Clarify a log message specifying the characters permitted in
6982 HiddenServiceAuthorizeClient client names. Previously, the log
6983 message said that "[A-Za-z0-9+-_]" were permitted; that could have
6984 given the impression that every ASCII character between "+" and "_"
6985 was permitted. Now we say "[A-Za-z0-9+_-]". Bugfix on 0.2.1.5-alpha.
6988 - Provide a substitute implementation of lround() for MSVC, which
6989 apparently lacks it. Patch from Gisle Vanem.
6990 - Clean up some code issues that prevented Tor from building on older
6991 BSDs. Fixes bug 3894; reported by "grarpamp".
6992 - Search for a platform-specific version of "ar" when cross-compiling.
6993 Should fix builds on iOS. Resolves bug 3909, found by Marco Bonetti.
6996 Changes in version 0.2.3.3-alpha - 2011-09-01
6997 Tor 0.2.3.3-alpha adds a new "stream isolation" feature to improve Tor's
6998 security, and provides client-side support for the microdescriptor
6999 and optimistic data features introduced earlier in the 0.2.3.x
7000 series. It also includes numerous critical bugfixes in the (optional)
7001 bufferevent-based networking backend.
7003 o Major features (stream isolation):
7004 - You can now configure Tor so that streams from different
7005 applications are isolated on different circuits, to prevent an
7006 attacker who sees your streams as they leave an exit node from
7007 linking your sessions to one another. To do this, choose some way
7008 to distinguish the applications: have them connect to different
7009 SocksPorts, or have one of them use SOCKS4 while the other uses
7010 SOCKS5, or have them pass different authentication strings to the
7011 SOCKS proxy. Then, use the new SocksPort syntax to configure the
7012 degree of isolation you need. This implements Proposal 171.
7013 - There's a new syntax for specifying multiple client ports (such as
7014 SOCKSPort, TransPort, DNSPort, NATDPort): you can now just declare
7015 multiple *Port entries with full addr:port syntax on each.
7016 The old *ListenAddress format is still supported, but you can't
7017 mix it with the new *Port syntax.
7019 o Major features (other):
7020 - Enable microdescriptor fetching by default for clients. This allows
7021 clients to download a much smaller amount of directory information.
7022 To disable it (and go back to the old-style consensus and
7023 descriptors), set "UseMicrodescriptors 0" in your torrc file.
7024 - Tor's firewall-helper feature, introduced in 0.2.3.1-alpha (see the
7025 "PortForwarding" config option), now supports Windows.
7026 - When using an exit relay running 0.2.3.x, clients can now
7027 "optimistically" send data before the exit relay reports that
7028 the stream has opened. This saves a round trip when starting
7029 connections where the client speaks first (such as web browsing).
7030 This behavior is controlled by a consensus parameter (currently
7031 disabled). To turn it on or off manually, use the "OptimisticData"
7032 torrc option. Implements proposal 181; code by Ian Goldberg.
7034 o Major bugfixes (bufferevents, fixes on 0.2.3.1-alpha):
7035 - When using IOCP on Windows, we need to enable Libevent windows
7037 - The IOCP backend now works even when the user has not specified
7038 the (internal, debugging-only) _UseFilteringSSLBufferevents option.
7039 Fixes part of bug 3752.
7040 - Correctly record the bytes we've read and written when using
7041 bufferevents, so that we can include them in our bandwidth history
7042 and advertised bandwidth. Fixes bug 3803.
7043 - Apply rate-limiting only at the bottom of a chain of filtering
7044 bufferevents. This prevents us from filling up internal read
7045 buffers and violating rate-limits when filtering bufferevents
7046 are enabled. Fixes part of bug 3804.
7047 - Add high-watermarks to the output buffers for filtered
7048 bufferevents. This prevents us from filling up internal write
7049 buffers and wasting CPU cycles when filtering bufferevents are
7050 enabled. Fixes part of bug 3804.
7051 - Correctly notice when data has been written from a bufferevent
7052 without flushing it completely. Fixes bug 3805.
7053 - Fix a bug where server-side tunneled bufferevent-based directory
7054 streams would get closed prematurely. Fixes bug 3814.
7055 - Fix a use-after-free error with per-connection rate-limiting
7056 buckets. Fixes bug 3888.
7058 o Major bugfixes (also part of 0.2.2.31-rc):
7059 - If we're configured to write our ControlPorts to disk, only write
7060 them after switching UID and creating the data directory. This way,
7061 we don't fail when starting up with a nonexistent DataDirectory
7062 and a ControlPortWriteToFile setting based on that directory. Fixes
7063 bug 3747; bugfix on Tor 0.2.2.26-beta.
7066 - Added a new CONF_CHANGED event so that controllers can be notified
7067 of any configuration changes made by other controllers, or by the
7068 user. Implements ticket 1692.
7069 - Use evbuffer_copyout() in inspect_evbuffer(). This fixes a memory
7070 leak when using bufferevents, and lets Libevent worry about how to
7071 best copy data out of a buffer.
7072 - Replace files in stats/ rather than appending to them. Now that we
7073 include statistics in extra-info descriptors, it makes no sense to
7074 keep old statistics forever. Implements ticket 2930.
7076 o Minor features (build compatibility):
7077 - Limited, experimental support for building with nmake and MSVC.
7078 - Provide a substitute implementation of lround() for MSVC, which
7079 apparently lacks it. Patch from Gisle Vanem.
7081 o Minor features (also part of 0.2.2.31-rc):
7082 - Update to the August 2 2011 Maxmind GeoLite Country database.
7084 o Minor bugfixes (on 0.2.3.x-alpha):
7085 - Fix a spurious warning when parsing SOCKS requests with
7086 bufferevents enabled. Fixes bug 3615; bugfix on 0.2.3.2-alpha.
7087 - Get rid of a harmless warning that could happen on relays running
7088 with bufferevents. The warning was caused by someone doing an http
7089 request to a relay's orport. Also don't warn for a few related
7090 non-errors. Fixes bug 3700; bugfix on 0.2.3.1-alpha.
7092 o Minor bugfixes (on 2.2.x and earlier):
7093 - Correct the man page to explain that HashedControlPassword and
7094 CookieAuthentication can both be set, in which case either method
7095 is sufficient to authenticate to Tor. Bugfix on 0.2.0.7-alpha,
7096 when we decided to allow these config options to both be set. Issue
7098 - The "--quiet" and "--hush" options now apply not only to Tor's
7099 behavior before logs are configured, but also to Tor's behavior in
7100 the absense of configured logs. Fixes bug 3550; bugfix on
7103 o Minor bugfixes (also part of 0.2.2.31-rc):
7104 - Write several files in text mode, on OSes that distinguish text
7105 mode from binary mode (namely, Windows). These files are:
7106 'buffer-stats', 'dirreq-stats', and 'entry-stats' on relays
7107 that collect those statistics; 'client_keys' and 'hostname' for
7108 hidden services that use authentication; and (in the tor-gencert
7109 utility) newly generated identity and signing keys. Previously,
7110 we wouldn't specify text mode or binary mode, leading to an
7111 assertion failure. Fixes bug 3607. Bugfix on 0.2.1.1-alpha (when
7112 the DirRecordUsageByCountry option which would have triggered
7113 the assertion failure was added), although this assertion failure
7114 would have occurred in tor-gencert on Windows in 0.2.0.1-alpha.
7115 - Selectively disable deprecation warnings on OS X because Lion
7116 started deprecating the shipped copy of openssl. Fixes bug 3643.
7117 - Remove an extra pair of quotation marks around the error
7118 message in control-port STATUS_GENERAL BUG events. Bugfix on
7119 0.1.2.6-alpha; fixes bug 3732.
7120 - When unable to format an address as a string, report its value
7121 as "???" rather than reusing the last formatted address. Bugfix
7124 o Code simplifications and refactoring:
7125 - Rewrite the listener-selection logic so that parsing which ports
7126 we want to listen on is now separate from binding to the ports
7130 - Building Tor with bufferevent support now requires Libevent
7131 2.0.13-stable or later. Previous versions of Libevent had bugs in
7132 SSL-related bufferevents and related issues that would make Tor
7133 work badly with bufferevents. Requiring 2.0.13-stable also allows
7134 Tor with bufferevents to take advantage of Libevent APIs
7135 introduced after 2.0.8-rc.
7138 Changes in version 0.2.2.32 - 2011-08-27
7139 The Tor 0.2.2 release series is dedicated to the memory of Andreas
7140 Pfitzmann (1958-2010), a pioneer in anonymity and privacy research,
7141 a founder of the PETS community, a leader in our field, a mentor,
7142 and a friend. He left us with these words: "I had the possibility
7143 to contribute to this world that is not as it should be. I hope I
7144 could help in some areas to make the world a better place, and that
7145 I could also encourage other people to be engaged in improving the
7146 world. Please, stay engaged. This world needs you, your love, your
7147 initiative -- now I cannot be part of that anymore."
7149 Tor 0.2.2.32, the first stable release in the 0.2.2 branch, is finally
7150 ready. More than two years in the making, this release features improved
7151 client performance and hidden service reliability, better compatibility
7152 for Android, correct behavior for bridges that listen on more than
7153 one address, more extensible and flexible directory object handling,
7154 better reporting of network statistics, improved code security, and
7155 many many other features and bugfixes.
7158 Changes in version 0.2.2.31-rc - 2011-08-17
7159 Tor 0.2.2.31-rc is the second and hopefully final release candidate
7160 for the Tor 0.2.2.x series.
7163 - Remove an extra pair of quotation marks around the error
7164 message in control-port STATUS_GENERAL BUG events. Bugfix on
7165 0.1.2.6-alpha; fixes bug 3732.
7166 - If we're configured to write our ControlPorts to disk, only write
7167 them after switching UID and creating the data directory. This way,
7168 we don't fail when starting up with a nonexistent DataDirectory
7169 and a ControlPortWriteToFile setting based on that directory. Fixes
7170 bug 3747; bugfix on Tor 0.2.2.26-beta.
7173 - Update to the August 2 2011 Maxmind GeoLite Country database.
7176 - Allow GETINFO fingerprint to return a fingerprint even when
7177 we have not yet built a router descriptor. Fixes bug 3577;
7178 bugfix on 0.2.0.1-alpha.
7179 - Write several files in text mode, on OSes that distinguish text
7180 mode from binary mode (namely, Windows). These files are:
7181 'buffer-stats', 'dirreq-stats', and 'entry-stats' on relays
7182 that collect those statistics; 'client_keys' and 'hostname' for
7183 hidden services that use authentication; and (in the tor-gencert
7184 utility) newly generated identity and signing keys. Previously,
7185 we wouldn't specify text mode or binary mode, leading to an
7186 assertion failure. Fixes bug 3607. Bugfix on 0.2.1.1-alpha (when
7187 the DirRecordUsageByCountry option which would have triggered
7188 the assertion failure was added), although this assertion failure
7189 would have occurred in tor-gencert on Windows in 0.2.0.1-alpha.
7190 - Selectively disable deprecation warnings on OS X because Lion
7191 started deprecating the shipped copy of openssl. Fixes bug 3643.
7192 - When unable to format an address as a string, report its value
7193 as "???" rather than reusing the last formatted address. Bugfix
7197 Changes in version 0.2.3.2-alpha - 2011-07-18
7198 Tor 0.2.3.2-alpha introduces two new experimental features:
7199 microdescriptors and pluggable transports. It also continues cleaning
7200 up a variety of recently introduced features.
7203 - Clients can now use microdescriptors instead of regular descriptors
7204 to build circuits. Microdescriptors are authority-generated
7205 summaries of regular descriptors' contents, designed to change
7206 very rarely (see proposal 158 for details). This feature is
7207 designed to save bandwidth, especially for clients on slow internet
7208 connections. It's off by default for now, since nearly no caches
7209 support it, but it will be on-by-default for clients in a future
7210 version. You can use the UseMicrodescriptors option to turn it on.
7211 - Tor clients using bridges can now be configured to use a separate
7212 'transport' proxy for each bridge. This approach helps to resist
7213 censorship by allowing bridges to use protocol obfuscation
7214 plugins. It implements part of proposal 180. Implements ticket 2841.
7215 - While we're trying to bootstrap, record how many TLS connections
7216 fail in each state, and report which states saw the most failures
7217 in response to any bootstrap failures. This feature may speed up
7218 diagnosis of censorship events. Implements ticket 3116.
7220 o Major bugfixes (on 0.2.3.1-alpha):
7221 - When configuring a large set of nodes in EntryNodes (as with
7222 'EntryNodes {cc}' or 'EntryNodes 1.1.1.1/16'), choose only a
7223 random subset to be guards, and choose them in random
7224 order. Fixes bug 2798.
7225 - Tor could crash when remembering a consensus in a non-used consensus
7226 flavor without having a current consensus set. Fixes bug 3361.
7227 - Comparing an unknown address to a microdescriptor's shortened exit
7228 policy would always give a "rejected" result. Fixes bug 3599.
7229 - Using microdescriptors as a client no longer prevents Tor from
7230 uploading and downloading hidden service descriptors. Fixes
7234 - Allow nameservers with IPv6 address. Resolves bug 2574.
7235 - Accept attempts to include a password authenticator in the
7236 handshake, as supported by SOCKS5. This handles SOCKS clients that
7237 don't know how to omit a password when authenticating. Resolves
7239 - When configuring a large set of nodes in EntryNodes, and there are
7240 enough of them listed as Guard so that we don't need to consider
7241 the non-guard entries, prefer the ones listed with the Guard flag.
7242 - Check for and recover from inconsistency in the microdescriptor
7243 cache. This will make it harder for us to accidentally free a
7244 microdescriptor without removing it from the appropriate data
7245 structures. Fixes issue 3135; issue noted by "wanoskarnet".
7246 - Log SSL state transitions at log level DEBUG, log domain
7247 HANDSHAKE. This can be useful for debugging censorship events.
7248 Implements ticket 3264.
7249 - Add port 6523 (Gobby) to LongLivedPorts. Patch by intrigeri;
7250 implements ticket 3439.
7252 o Minor bugfixes (on 0.2.3.1-alpha):
7253 - Do not free all general-purpose regular descriptors just
7254 because microdescriptor use is enabled. Fixes bug 3113.
7255 - Correctly link libevent_openssl when --enable-static-libevent
7256 is passed to configure. Fixes bug 3118.
7257 - Bridges should not complain during their heartbeat log messages that
7258 they are unlisted in the consensus: that's more or less the point
7259 of being a bridge. Fixes bug 3183.
7260 - Report a SIGNAL event to controllers when acting on a delayed
7261 SIGNAL NEWNYM command. Previously, we would report a SIGNAL
7262 event to the controller if we acted on a SIGNAL NEWNYM command
7263 immediately, and otherwise not report a SIGNAL event for the
7264 command at all. Fixes bug 3349.
7265 - Fix a crash when handling the SIGNAL controller command or
7266 reporting ERR-level status events with bufferevents enabled. Found
7267 by Robert Ransom. Fixes bug 3367.
7268 - Always ship the tor-fw-helper manpage in our release tarballs.
7269 Fixes bug 3389. Reported by Stephen Walker.
7270 - Fix a class of double-mark-for-close bugs when bufferevents
7271 are enabled. Fixes bug 3403.
7272 - Update tor-fw-helper to support libnatpmp-20110618. Fixes bug 3434.
7273 - Add SIGNAL to the list returned by the 'GETINFO events/names'
7274 control-port command. Fixes part of bug 3465.
7275 - Prevent using negative indices during unit test runs when read_all()
7276 fails. Spotted by coverity.
7277 - Fix a rare memory leak when checking the nodelist without it being
7278 present. Found by coverity.
7279 - Only try to download a microdescriptor-flavored consensus from
7280 a directory cache that provides them.
7282 o Minor bugfixes (on 0.2.2.x and earlier):
7283 - Assert that hidden-service-related operations are not performed
7284 using single-hop circuits. Previously, Tor would assert that
7285 client-side streams are not attached to single-hop circuits,
7286 but not that other sensitive operations on the client and service
7287 side are not performed using single-hop circuits. Fixes bug 3332;
7289 - Don't publish a new relay descriptor when we reload our onion key,
7290 unless the onion key has actually changed. Fixes bug 3263 and
7291 resolves another cause of bug 1810. Bugfix on 0.1.1.11-alpha.
7292 - Allow GETINFO fingerprint to return a fingerprint even when
7293 we have not yet built a router descriptor. Fixes bug 3577;
7294 bugfix on 0.2.0.1-alpha.
7295 - Make 'tor --digests' list hashes of all Tor source files. Bugfix
7296 on 0.2.2.4-alpha; fixes bug 3427.
7298 o Code simplification and refactoring:
7299 - Use tor_sscanf() in place of scanf() in more places through the
7300 code. This makes us a little more locale-independent, and
7301 should help shut up code-analysis tools that can't tell
7302 a safe sscanf string from a dangerous one.
7303 - Use tt_assert(), not tor_assert(), for checking for test failures.
7304 This makes the unit tests more able to go on in the event that
7306 - Split connection_about_to_close() into separate functions for each
7310 - On Windows, we now define the _WIN32_WINNT macros only if they
7311 are not already defined. This lets the person building Tor decide,
7312 if they want, to require a later version of Windows.
7315 Changes in version 0.2.2.30-rc - 2011-07-07
7316 Tor 0.2.2.30-rc is the first release candidate for the Tor 0.2.2.x
7317 series. It fixes a few smaller bugs, but generally appears stable.
7318 Please test it and let us know whether it is!
7321 - Send a SUCCEEDED stream event to the controller when a reverse
7322 resolve succeeded. Fixes bug 3536; bugfix on 0.0.8pre1. Issue
7323 discovered by katmagic.
7324 - Always NUL-terminate the sun_path field of a sockaddr_un before
7325 passing it to the kernel. (Not a security issue: kernels are
7326 smart enough to reject bad sockaddr_uns.) Found by Coverity;
7327 CID #428. Bugfix on Tor 0.2.0.3-alpha.
7328 - Don't stack-allocate the list of supplementary GIDs when we're
7329 about to log them. Stack-allocating NGROUPS_MAX gid_t elements
7330 could take up to 256K, which is way too much stack. Found by
7331 Coverity; CID #450. Bugfix on 0.2.1.7-alpha.
7332 - Add BUILDTIMEOUT_SET to the list returned by the 'GETINFO
7333 events/names' control-port command. Bugfix on 0.2.2.9-alpha;
7334 fixes part of bug 3465.
7335 - Fix a memory leak when receiving a descriptor for a hidden
7336 service we didn't ask for. Found by Coverity; CID #30. Bugfix
7340 - Update to the July 1 2011 Maxmind GeoLite Country database.
7343 Changes in version 0.2.2.29-beta - 2011-06-20
7344 Tor 0.2.2.29-beta reverts an accidental behavior change for users who
7345 have bridge lines in their torrc but don't want to use them; gets
7346 us closer to having the control socket feature working on Debian;
7347 and fixes a variety of smaller bugs.
7350 - Revert the UseBridges option to its behavior before 0.2.2.28-beta.
7351 When we changed the default behavior to "use bridges if any
7352 are listed in the torrc", we surprised users who had bridges
7353 in their torrc files but who didn't actually want to use them.
7354 Partial resolution for bug 3354.
7357 - Don't attach new streams to old rendezvous circuits after SIGNAL
7358 NEWNYM. Previously, we would keep using an existing rendezvous
7359 circuit if it remained open (i.e. if it were kept open by a
7360 long-lived stream, or if a new stream were attached to it before
7361 Tor could notice that it was old and no longer in use). Bugfix on
7362 0.1.1.15-rc; fixes bug 3375.
7365 - Fix a bug when using ControlSocketsGroupWritable with User. The
7366 directory's group would be checked against the current group, not
7367 the configured group. Patch by Jérémy Bobbio. Fixes bug 3393;
7368 bugfix on 0.2.2.26-beta.
7369 - Make connection_printf_to_buf()'s behaviour sane. Its callers
7370 expect it to emit a CRLF iff the format string ends with CRLF;
7371 it actually emitted a CRLF iff (a) the format string ended with
7372 CRLF or (b) the resulting string was over 1023 characters long or
7373 (c) the format string did not end with CRLF *and* the resulting
7374 string was 1021 characters long or longer. Bugfix on 0.1.1.9-alpha;
7375 fixes part of bug 3407.
7376 - Make send_control_event_impl()'s behaviour sane. Its callers
7377 expect it to always emit a CRLF at the end of the string; it
7378 might have emitted extra control characters as well. Bugfix on
7379 0.1.1.9-alpha; fixes another part of bug 3407.
7380 - Make crypto_rand_int() check the value of its input correctly.
7381 Previously, it accepted values up to UINT_MAX, but could return a
7382 negative number if given a value above INT_MAX+1. Found by George
7383 Kadianakis. Fixes bug 3306; bugfix on 0.2.2pre14.
7384 - Avoid a segfault when reading a malformed circuit build state
7385 with more than INT_MAX entries. Found by wanoskarnet. Bugfix on
7387 - When asked about a DNS record type we don't support via a
7388 client DNSPort, reply with NOTIMPL rather than an empty
7389 reply. Patch by intrigeri. Fixes bug 3369; bugfix on 2.0.1-alpha.
7390 - Fix a rare memory leak during stats writing. Found by coverity.
7393 - Update to the June 1 2011 Maxmind GeoLite Country database.
7395 o Code simplifications and refactoring:
7396 - Remove some dead code as indicated by coverity.
7397 - Remove a few dead assignments during router parsing. Found by
7399 - Add some forgotten return value checks during unit tests. Found
7401 - Don't use 1-bit wide signed bit fields. Found by coverity.
7404 Changes in version 0.2.2.28-beta - 2011-06-04
7405 Tor 0.2.2.28-beta makes great progress towards a new stable release: we
7406 fixed a big bug in whether relays stay in the consensus consistently,
7407 we moved closer to handling bridges and hidden services correctly,
7408 and we started the process of better handling the dreaded "my Vidalia
7409 died, and now my Tor demands a password when I try to reconnect to it"
7413 - Don't decide to make a new descriptor when receiving a HUP signal.
7414 This bug has caused a lot of 0.2.2.x relays to disappear from the
7415 consensus periodically. Fixes the most common case of triggering
7416 bug 1810; bugfix on 0.2.2.7-alpha.
7417 - Actually allow nameservers with IPv6 addresses. Fixes bug 2574.
7418 - Don't try to build descriptors if "ORPort auto" is set and we
7419 don't know our actual ORPort yet. Fix for bug 3216; bugfix on
7421 - Resolve a crash that occurred when setting BridgeRelay to 1 with
7422 accounting enabled. Fixes bug 3228; bugfix on 0.2.2.18-alpha.
7423 - Apply circuit timeouts to opened hidden-service-related circuits
7424 based on the correct start time. Previously, we would apply the
7425 circuit build timeout based on time since the circuit's creation;
7426 it was supposed to be applied based on time since the circuit
7427 entered its current state. Bugfix on 0.0.6; fixes part of bug 1297.
7428 - Use the same circuit timeout for client-side introduction
7429 circuits as for other four-hop circuits, rather than the timeout
7430 for single-hop directory-fetch circuits; the shorter timeout may
7431 have been appropriate with the static circuit build timeout in
7432 0.2.1.x and earlier, but caused many hidden service access attempts
7433 to fail with the adaptive CBT introduced in 0.2.2.2-alpha. Bugfix
7434 on 0.2.2.2-alpha; fixes another part of bug 1297.
7435 - In ticket 2511 we fixed a case where you could use an unconfigured
7436 bridge if you had configured it as a bridge the last time you ran
7437 Tor. Now fix another edge case: if you had configured it as a bridge
7438 but then switched to a different bridge via the controller, you
7439 would still be willing to use the old one. Bugfix on 0.2.0.1-alpha;
7443 - Add an __OwningControllerProcess configuration option and a
7444 TAKEOWNERSHIP control-port command. Now a Tor controller can ensure
7445 that when it exits, Tor will shut down. Implements feature 3049.
7446 - If "UseBridges 1" is set and no bridges are configured, Tor will
7447 now refuse to build any circuits until some bridges are set.
7448 If "UseBridges auto" is set, Tor will use bridges if they are
7449 configured and we are not running as a server, but otherwise will
7450 make circuits as usual. The new default is "auto". Patch by anonym,
7451 so the Tails LiveCD can stop automatically revealing you as a Tor
7455 - Fix warnings from GCC 4.6's "-Wunused-but-set-variable" option.
7456 - Remove a trailing asterisk from "exit-policy/default" in the
7457 output of the control port command "GETINFO info/names". Bugfix
7459 - Use a wide type to hold sockets when built for 64-bit Windows builds.
7461 - Warn when the user configures two HiddenServiceDir lines that point
7462 to the same directory. Bugfix on 0.0.6 (the version introducing
7463 HiddenServiceDir); fixes bug 3289.
7464 - Remove dead code from rend_cache_lookup_v2_desc_as_dir. Fixes
7465 part of bug 2748; bugfix on 0.2.0.10-alpha.
7466 - Log malformed requests for rendezvous descriptors as protocol
7467 warnings, not warnings. Also, use a more informative log message
7468 in case someone sees it at log level warning without prior
7469 info-level messages. Fixes the other part of bug 2748; bugfix
7471 - Clear the table recording the time of the last request for each
7472 hidden service descriptor from each HS directory on SIGNAL NEWNYM.
7473 Previously, we would clear our HS descriptor cache on SIGNAL
7474 NEWNYM, but if we had previously retrieved a descriptor (or tried
7475 to) from every directory responsible for it, we would refuse to
7476 fetch it again for up to 15 minutes. Bugfix on 0.2.2.25-alpha;
7478 - Fix a log message that said "bits" while displaying a value in
7479 bytes. Found by wanoskarnet. Fixes bug 3318; bugfix on
7481 - When checking for 1024-bit keys, check for 1024 bits, not 128
7482 bytes. This allows Tor to correctly discard keys of length 1017
7483 through 1023. Bugfix on 0.0.9pre5.
7486 - Relays now log the reason for publishing a new relay descriptor,
7487 so we have a better chance of hunting down instances of bug 1810.
7488 Resolves ticket 3252.
7489 - Revise most log messages that refer to nodes by nickname to
7490 instead use the "$key=nickname at address" format. This should be
7491 more useful, especially since nicknames are less and less likely
7492 to be unique. Resolves ticket 3045.
7493 - Log (at info level) when purging pieces of hidden-service-client
7494 state because of SIGNAL NEWNYM.
7497 - Remove undocumented option "-F" from tor-resolve: it hasn't done
7498 anything since 0.2.1.16-rc.
7501 Changes in version 0.2.2.27-beta - 2011-05-18
7502 Tor 0.2.2.27-beta fixes a bridge-related stability bug in the previous
7503 release, and also adds a few more general bugfixes.
7506 - Fix a crash bug when changing bridges in a running Tor process.
7507 Fixes bug 3213; bugfix on 0.2.2.26-beta.
7508 - When the controller configures a new bridge, don't wait 10 to 60
7509 seconds before trying to fetch its descriptor. Bugfix on
7510 0.2.0.3-alpha; fixes bug 3198 (suggested by 2355).
7513 - Require that onion keys have exponent 65537 in microdescriptors too.
7514 Fixes more of bug 3207; bugfix on 0.2.2.26-beta.
7515 - Tor used to limit HttpProxyAuthenticator values to 48 characters.
7516 Changed the limit to 512 characters by removing base64 newlines.
7517 Fixes bug 2752. Fix by Michael Yakubovich.
7518 - When a client starts or stops using bridges, never use a circuit
7519 that was built before the configuration change. This behavior could
7520 put at risk a user who uses bridges to ensure that her traffic
7521 only goes to the chosen addresses. Bugfix on 0.2.0.3-alpha; fixes
7525 Changes in version 0.2.2.26-beta - 2011-05-17
7526 Tor 0.2.2.26-beta fixes a variety of potential privacy problems. It
7527 also introduces a new "socksport auto" approach that should make it
7528 easier to run multiple Tors on the same system, and does a lot of
7529 cleanup to get us closer to a release candidate.
7531 o Security/privacy fixes:
7532 - Replace all potentially sensitive memory comparison operations
7533 with versions whose runtime does not depend on the data being
7534 compared. This will help resist a class of attacks where an
7535 adversary can use variations in timing information to learn
7536 sensitive data. Fix for one case of bug 3122. (Safe memcmp
7537 implementation by Robert Ransom based partially on code by DJB.)
7538 - When receiving a hidden service descriptor, check that it is for
7539 the hidden service we wanted. Previously, Tor would store any
7540 hidden service descriptors that a directory gave it, whether it
7541 wanted them or not. This wouldn't have let an attacker impersonate
7542 a hidden service, but it did let directories pre-seed a client
7543 with descriptors that it didn't want. Bugfix on 0.0.6.
7544 - On SIGHUP, do not clear out all TrackHostExits mappings, client
7545 DNS cache entries, and virtual address mappings: that's what
7546 NEWNYM is for. Fixes bug 1345; bugfix on 0.1.0.1-rc.
7549 - The options SocksPort, ControlPort, and so on now all accept a
7550 value "auto" that opens a socket on an OS-selected port. A
7551 new ControlPortWriteToFile option tells Tor to write its
7552 actual control port or ports to a chosen file. If the option
7553 ControlPortFileGroupReadable is set, the file is created as
7554 group-readable. Now users can run two Tor clients on the same
7555 system without needing to manually mess with parameters. Resolves
7556 part of ticket 3076.
7557 - Set SO_REUSEADDR on all sockets, not just listeners. This should
7558 help busy exit nodes avoid running out of useable ports just
7559 because all the ports have been used in the near past. Resolves
7563 - New "GETINFO net/listeners/(type)" controller command to return
7564 a list of addresses and ports that are bound for listeners for a
7565 given connection type. This is useful when the user has configured
7566 "SocksPort auto" and the controller needs to know which port got
7567 chosen. Resolves another part of ticket 3076.
7568 - Add a new ControlSocketsGroupWritable configuration option: when
7569 it is turned on, ControlSockets are group-writeable by the default
7570 group of the current user. Patch by Jérémy Bobbio; implements
7572 - Tor now refuses to create a ControlSocket in a directory that is
7573 world-readable (or group-readable if ControlSocketsGroupWritable
7574 is 0). This is necessary because some operating systems do not
7575 enforce permissions on an AF_UNIX sockets. Permissions on the
7576 directory holding the socket, however, seems to work everywhere.
7577 - Rate-limit a warning about failures to download v2 networkstatus
7578 documents. Resolves part of bug 1352.
7579 - Backport code from 0.2.3.x that allows directory authorities to
7580 clean their microdescriptor caches. Needed to resolve bug 2230.
7581 - When an HTTPS proxy reports "403 Forbidden", we now explain
7582 what it means rather than calling it an unexpected status code.
7583 Closes bug 2503. Patch from Michael Yakubovich.
7584 - Update to the May 1 2011 Maxmind GeoLite Country database.
7587 - Authorities now clean their microdesc cache periodically and when
7588 reading from disk initially, not only when adding new descriptors.
7589 This prevents a bug where we could lose microdescriptors. Bugfix
7590 on 0.2.2.6-alpha. Fixes bug 2230.
7591 - Do not crash when our configuration file becomes unreadable, for
7592 example due to a permissions change, between when we start up
7593 and when a controller calls SAVECONF. Fixes bug 3135; bugfix
7595 - Avoid a bug that would keep us from replacing a microdescriptor
7596 cache on Windows. (We would try to replace the file while still
7597 holding it open. That's fine on Unix, but Windows doesn't let us
7598 do that.) Bugfix on 0.2.2.6-alpha; bug found by wanoskarnet.
7599 - Add missing explanations for the authority-related torrc options
7600 RephistTrackTime, BridgePassword, and V3AuthUseLegacyKey in the
7601 man page. Resolves issue 2379.
7602 - As an authority, do not upload our own vote or signature set to
7603 ourself. It would tell us nothing new, and as of 0.2.2.24-alpha,
7604 it would get flagged as a duplicate. Resolves bug 3026.
7605 - Accept hidden service descriptors if we think we might be a hidden
7606 service directory, regardless of what our consensus says. This
7607 helps robustness, since clients and hidden services can sometimes
7608 have a more up-to-date view of the network consensus than we do,
7609 and if they think that the directory authorities list us a HSDir,
7610 we might actually be one. Related to bug 2732; bugfix on
7612 - When a controller changes TrackHostExits, remove mappings for
7613 hosts that should no longer have their exits tracked. Bugfix on
7615 - When a controller changes VirtualAddrNetwork, remove any mappings
7616 for hosts that were automapped to the old network. Bugfix on
7618 - When a controller changes one of the AutomapHosts* options, remove
7619 any mappings for hosts that should no longer be automapped. Bugfix
7621 - Do not reset the bridge descriptor download status every time we
7622 re-parse our configuration or get a configuration change. Fixes
7623 bug 3019; bugfix on 0.2.0.3-alpha.
7625 o Minor bugfixes (code cleanup):
7626 - When loading the microdesc journal, remember its current size.
7627 In 0.2.2, this helps prevent the microdesc journal from growing
7628 without limit on authorities (who are the only ones to use it in
7629 0.2.2). Fixes a part of bug 2230; bugfix on 0.2.2.6-alpha.
7630 Fix posted by "cypherpunks."
7631 - The microdesc journal is supposed to get rebuilt only if it is
7632 at least _half_ the length of the store, not _twice_ the length
7633 of the store. Bugfix on 0.2.2.6-alpha; fixes part of bug 2230.
7634 - Fix a potential null-pointer dereference while computing a
7635 consensus. Bugfix on tor-0.2.0.3-alpha, found with the help of
7637 - Avoid a possible null-pointer dereference when rebuilding the mdesc
7638 cache without actually having any descriptors to cache. Bugfix on
7639 0.2.2.6-alpha. Issue discovered using clang's static analyzer.
7640 - If we fail to compute the identity digest of a v3 legacy keypair,
7641 warn, and don't use a buffer-full of junk instead. Bugfix on
7642 0.2.1.1-alpha; fixes bug 3106.
7643 - Resolve an untriggerable issue in smartlist_string_num_isin(),
7644 where if the function had ever in the future been used to check
7645 for the presence of a too-large number, it would have given an
7646 incorrect result. (Fortunately, we only used it for 16-bit
7647 values.) Fixes bug 3175; bugfix on 0.1.0.1-rc.
7648 - Require that introduction point keys and onion handshake keys
7649 have a public exponent of 65537. Starts to fix bug 3207; bugfix
7653 - Caches no longer download and serve v2 networkstatus documents
7654 unless FetchV2Networkstatus flag is set: these documents haven't
7655 haven't been used by clients or relays since 0.2.0.x. Resolves
7659 Changes in version 0.2.3.1-alpha - 2011-05-05
7660 Tor 0.2.3.1-alpha adds some new experimental features, including support
7661 for an improved network IO backend, IOCP networking on Windows,
7662 microdescriptor caching, "fast-start" support for streams, and automatic
7663 home router configuration. There are also numerous internal improvements
7664 to try to make the code easier for developers to work with.
7666 This is the first alpha release in a new series, so expect there to be
7667 bugs. Users who would rather test out a more stable branch should
7668 stay with 0.2.2.x for now.
7671 - Tor can now optionally build with the "bufferevents" buffered IO
7672 backend provided by Libevent 2. To use this feature, make sure you
7673 have the latest possible version of Libevent, and pass the
7674 --enable-bufferevents flag to configure when building Tor from
7675 source. This feature will make our networking code more flexible,
7676 let us stack layers on each other, and let us use more efficient
7677 zero-copy transports where available.
7678 - As an experimental feature, Tor can use IOCP for networking on Windows.
7679 Once this code is tuned and optimized, it promises much better
7680 performance than the select-based backend we've used in the past. To
7681 try this feature, you must build Tor with Libevent 2, configure Tor
7682 with the "bufferevents" buffered IO backend, and add "DisableIOCP 0" to
7683 your torrc. There are known bugs here: only try this if you can help
7684 debug it as it breaks.
7685 - The EntryNodes option can now include country codes like {de} or IP
7686 addresses or network masks. Previously we had disallowed these options
7687 because we didn't have an efficient way to keep the list up to
7688 date. Fixes bug 1982, but see bug 2798 for an unresolved issue here.
7689 - Exit nodes now accept and queue data on not-yet-connected streams.
7690 Previously, the client wasn't allowed to send data until the stream was
7691 connected, which slowed down all connections. This change will enable
7692 clients to perform a "fast-start" on streams and send data without
7693 having to wait for a confirmation that the stream has opened. (Patch
7694 from Ian Goldberg; implements the server side of Proposal 174.)
7695 - Tor now has initial support for automatic port mapping on the many
7696 home routers that support NAT-PMP or UPnP. (Not yet supported on
7697 Windows). To build the support code, you'll need to have libnatpnp
7698 library and/or the libminiupnpc library, and you'll need to enable the
7699 feature specifically by passing "--enable-upnp" and/or
7700 "--enable-natpnp" to configure. To turn it on, use the new
7701 PortForwarding option.
7702 - Caches now download, cache, and serve multiple "flavors" of the
7703 consensus, including a flavor that describes microdescriptors.
7704 - Caches now download, cache, and serve microdescriptors -- small
7705 summaries of router descriptors that are authenticated by all of the
7706 directory authorities. Once enough caches are running this code,
7707 clients will be able to save significant amounts of directory bandwidth
7708 by downloading microdescriptors instead of router descriptors.
7711 - Make logging resolution configurable with a new LogTimeGranularity
7712 option, and change the default from 1 millisecond to 1 second.
7713 Implements enhancement 1668.
7714 - We log which torrc file we're using on startup. Implements ticket
7716 - Ordinarily, Tor does not count traffic from private addresses (like
7717 127.0.0.1 or 10.0.0.1) when calculating rate limits or accounting.
7718 There is now a new option, CountPrivateBandwidth, to disable this
7719 behavior. Patch from Daniel Cagara.
7720 - New --enable-static-tor configure option for building Tor as
7721 statically as possible. Idea, general hackery and thoughts from
7722 Alexei Czeskis, John Gilmore, Jacob Appelbaum. Implements ticket
7724 - If you set the NumCPUs option to 0, Tor will now try to detect how
7725 many CPUs you have. This is the new default behavior.
7726 - Turn on directory request statistics by default and include them in
7727 extra-info descriptors. Don't break if we have no GeoIP database.
7728 - Relays that set "ConnDirectionStatistics 1" write statistics on the
7729 bidirectional use of connections to disk every 24 hours.
7730 - Add a GeoIP file digest to the extra-info descriptor. Implements
7732 - The NodeFamily option -- which let you declare that you want to
7733 consider nodes to be part of a family whether they list themselves
7734 that way or not -- now allows IP address ranges and country codes.
7735 - Add a new 'Heartbeat' log message type to periodically log a message
7736 describing Tor's status at level Notice. This feature is meant for
7737 operators who log at notice, and want to make sure that their Tor
7738 server is still working. Implementation by George Kadianakis.
7740 o Minor bugfixes (on 0.2.2.25-alpha):
7741 - When loading the microdesc journal, remember its current size.
7742 In 0.2.2, this helps prevent the microdesc journal from growing
7743 without limit on authorities (who are the only ones to use it in
7744 0.2.2). Fixes a part of bug 2230; bugfix on 0.2.2.6-alpha.
7745 Fix posted by "cypherpunks."
7746 - The microdesc journal is supposed to get rebuilt only if it is
7747 at least _half_ the length of the store, not _twice_ the length
7748 of the store. Bugfix on 0.2.2.6-alpha; fixes part of bug 2230.
7749 - If as an authority we fail to compute the identity digest of a v3
7750 legacy keypair, warn, and don't use a buffer-full of junk instead.
7751 Bugfix on 0.2.1.1-alpha; fixes bug 3106.
7752 - Authorities now clean their microdesc cache periodically and when
7753 reading from disk initially, not only when adding new descriptors.
7754 This prevents a bug where we could lose microdescriptors. Bugfix
7757 o Minor features (controller):
7758 - Add a new SIGNAL event to the controller interface so that
7759 controllers can be notified when Tor handles a signal. Resolves
7760 issue 1955. Patch by John Brooks.
7761 - Add a new GETINFO option to get total bytes read and written. Patch
7762 from pipe, revised by atagar. Resolves ticket 2345.
7763 - Implement some GETINFO controller fields to provide information about
7764 the Tor process's pid, euid, username, and resource limits.
7767 - Our build system requires automake 1.6 or later to create the
7768 Makefile.in files. Previously, you could have used 1.4.
7769 This only affects developers and people building Tor from git;
7770 people who build Tor from the source distribution without changing
7771 the Makefile.am files should be fine.
7772 - Our autogen.sh script uses autoreconf to launch autoconf, automake, and
7773 so on. This is more robust against some of the failure modes
7774 associated with running the autotools pieces on their own.
7776 o Minor packaging issues:
7777 - On OpenSUSE, create the /var/run/tor directory on startup if it is not
7778 already created. Patch from Andreas Stieger. Fixes bug 2573.
7780 o Code simplifications and refactoring:
7781 - A major revision to our internal node-selecting and listing logic.
7782 Tor already had at least two major ways to look at the question of
7783 "which Tor servers do we know about": a list of router descriptors,
7784 and a list of entries in the current consensus. With
7785 microdescriptors, we're adding a third. Having so many systems
7786 without an abstraction layer over them was hurting the codebase.
7787 Now, we have a new "node_t" abstraction that presents a consistent
7788 interface to a client's view of a Tor node, and holds (nearly) all
7789 of the mutable state formerly in routerinfo_t and routerstatus_t.
7790 - The helper programs tor-gencert, tor-resolve, and tor-checkkey
7791 no longer link against Libevent: they never used it, but
7792 our library structure used to force them to link it.
7795 - Remove some old code to work around even older versions of Tor that
7796 used forked processes to handle DNS requests. Such versions of Tor
7797 are no longer in use as servers.
7799 o Documentation fixes:
7800 - Correct a broken faq link in the INSTALL file. Fixes bug 2307.
7801 - Add missing documentation for the authority-related torrc options
7802 RephistTrackTime, BridgePassword, and V3AuthUseLegacyKey. Resolves
7806 Changes in version 0.2.2.25-alpha - 2011-04-29
7807 Tor 0.2.2.25-alpha fixes many bugs: hidden service clients are more
7808 robust, routers no longer overreport their bandwidth, Win7 should crash
7809 a little less, and NEWNYM (as used by Vidalia's "new identity" button)
7810 now prevents hidden service-related activity from being linkable. It
7811 provides more information to Vidalia so you can see if your bridge is
7812 working. Also, 0.2.2.25-alpha revamps the Entry/Exit/ExcludeNodes and
7813 StrictNodes configuration options to make them more reliable, more
7814 understandable, and more regularly applied. If you use those options,
7815 please see the revised documentation for them in the manual page.
7818 - Relays were publishing grossly inflated bandwidth values because
7819 they were writing their state files wrong--now they write the
7820 correct value. Also, resume reading bandwidth history from the
7821 state file correctly. Fixes bug 2704; bugfix on 0.2.2.23-alpha.
7822 - Improve hidden service robustness: When we find that we have
7823 extended a hidden service's introduction circuit to a relay not
7824 listed as an introduction point in the HS descriptor we currently
7825 have, retry with an introduction point from the current
7826 descriptor. Previously we would just give up. Fixes bugs 1024 and
7827 1930; bugfix on 0.2.0.10-alpha.
7828 - Clients now stop trying to use an exit node associated with a given
7829 destination by TrackHostExits if they fail to reach that exit node.
7830 Fixes bug 2999. Bugfix on 0.2.0.20-rc.
7831 - Fix crash bug on platforms where gmtime and localtime can return
7832 NULL. Windows 7 users were running into this one. Fixes part of bug
7833 2077. Bugfix on all versions of Tor. Found by boboper.
7835 o Security and stability fixes:
7836 - Don't double-free a parsable, but invalid, microdescriptor, even if
7837 it is followed in the blob we're parsing by an unparsable
7838 microdescriptor. Fixes an issue reported in a comment on bug 2954.
7839 Bugfix on 0.2.2.6-alpha; fix by "cypherpunks".
7840 - If the Nickname configuration option isn't given, Tor would pick a
7841 nickname based on the local hostname as the nickname for a relay.
7842 Because nicknames are not very important in today's Tor and the
7843 "Unnamed" nickname has been implemented, this is now problematic
7844 behavior: It leaks information about the hostname without being
7845 useful at all. Fixes bug 2979; bugfix on 0.1.2.2-alpha, which
7846 introduced the Unnamed nickname. Reported by tagnaq.
7847 - Fix an uncommon assertion failure when running with DNSPort under
7848 heavy load. Fixes bug 2933; bugfix on 0.2.0.1-alpha.
7849 - Avoid linkability based on cached hidden service descriptors: forget
7850 all hidden service descriptors cached as a client when processing a
7851 SIGNAL NEWNYM command. Fixes bug 3000; bugfix on 0.0.6.
7854 - Export GeoIP information on bridge usage to controllers even if we
7855 have not yet been running for 24 hours. Now Vidalia bridge operators
7856 can get more accurate and immediate feedback about their
7857 contributions to the network.
7859 o Major features and bugfixes (node selection):
7860 - Revise and reconcile the meaning of the ExitNodes, EntryNodes,
7861 ExcludeEntryNodes, ExcludeExitNodes, ExcludeNodes, and StrictNodes
7862 options. Previously, we had been ambiguous in describing what
7863 counted as an "exit" node, and what operations exactly "StrictNodes
7864 0" would permit. This created confusion when people saw nodes built
7865 through unexpected circuits, and made it hard to tell real bugs from
7866 surprises. Now the intended behavior is:
7867 . "Exit", in the context of ExitNodes and ExcludeExitNodes, means
7868 a node that delivers user traffic outside the Tor network.
7869 . "Entry", in the context of EntryNodes, means a node used as the
7870 first hop of a multihop circuit. It doesn't include direct
7871 connections to directory servers.
7872 . "ExcludeNodes" applies to all nodes.
7873 . "StrictNodes" changes the behavior of ExcludeNodes only. When
7874 StrictNodes is set, Tor should avoid all nodes listed in
7875 ExcludeNodes, even when it will make user requests fail. When
7876 StrictNodes is *not* set, then Tor should follow ExcludeNodes
7877 whenever it can, except when it must use an excluded node to
7878 perform self-tests, connect to a hidden service, provide a
7879 hidden service, fulfill a .exit request, upload directory
7880 information, or fetch directory information.
7881 Collectively, the changes to implement the behavior fix bug 1090.
7882 - ExcludeNodes now takes precedence over EntryNodes and ExitNodes: if
7883 a node is listed in both, it's treated as excluded.
7884 - ExcludeNodes now applies to directory nodes -- as a preference if
7885 StrictNodes is 0, or an absolute requirement if StrictNodes is 1.
7886 Don't exclude all the directory authorities and set StrictNodes to 1
7887 unless you really want your Tor to break.
7888 - ExcludeNodes and ExcludeExitNodes now override exit enclaving.
7889 - ExcludeExitNodes now overrides .exit requests.
7890 - We don't use bridges listed in ExcludeNodes.
7891 - When StrictNodes is 1:
7892 . We now apply ExcludeNodes to hidden service introduction points
7893 and to rendezvous points selected by hidden service users. This
7894 can make your hidden service less reliable: use it with caution!
7895 . If we have used ExcludeNodes on ourself, do not try relay
7896 reachability self-tests.
7897 . If we have excluded all the directory authorities, we will not
7898 even try to upload our descriptor if we're a relay.
7899 . Do not honor .exit requests to an excluded node.
7900 - Remove a misfeature that caused us to ignore the Fast/Stable flags
7901 when ExitNodes is set. Bugfix on 0.2.2.7-alpha.
7902 - When the set of permitted nodes changes, we now remove any mappings
7903 introduced via TrackExitHosts to now-excluded nodes. Bugfix on
7905 - We never cannibalize a circuit that had excluded nodes on it, even
7906 if StrictNodes is 0. Bugfix on 0.1.0.1-rc.
7907 - Revert a change where we would be laxer about attaching streams to
7908 circuits than when building the circuits. This was meant to prevent
7909 a set of bugs where streams were never attachable, but our improved
7910 code here should make this unnecessary. Bugfix on 0.2.2.7-alpha.
7911 - Keep track of how many times we launch a new circuit to handle a
7912 given stream. Too many launches could indicate an inconsistency
7913 between our "launch a circuit to handle this stream" logic and our
7914 "attach this stream to one of the available circuits" logic.
7915 - Improve log messages related to excluded nodes.
7918 - Fix a spurious warning when moving from a short month to a long
7919 month on relays with month-based BandwidthAccounting. Bugfix on
7920 0.2.2.17-alpha; fixes bug 3020.
7921 - When a client finds that an origin circuit has run out of 16-bit
7922 stream IDs, we now mark it as unusable for new streams. Previously,
7923 we would try to close the entire circuit. Bugfix on 0.0.6.
7924 - Add a forgotten cast that caused a compile warning on OS X 10.6.
7925 Bugfix on 0.2.2.24-alpha.
7926 - Be more careful about reporting the correct error from a failed
7927 connect() system call. Under some circumstances, it was possible to
7928 look at an incorrect value for errno when sending the end reason.
7929 Bugfix on 0.1.0.1-rc.
7930 - Correctly handle an "impossible" overflow cases in connection byte
7931 counting, where we write or read more than 4GB on an edge connection
7932 in a single second. Bugfix on 0.1.2.8-beta.
7933 - Correct the warning displayed when a rendezvous descriptor exceeds
7934 the maximum size. Fixes bug 2750; bugfix on 0.2.1.5-alpha. Found by
7936 - Clients and hidden services now use HSDir-flagged relays for hidden
7937 service descriptor downloads and uploads even if the relays have no
7938 DirPort set and the client has disabled TunnelDirConns. This will
7939 eventually allow us to give the HSDir flag to relays with no
7940 DirPort. Fixes bug 2722; bugfix on 0.2.1.6-alpha.
7941 - Downgrade "no current certificates known for authority" message from
7942 Notice to Info. Fixes bug 2899; bugfix on 0.2.0.10-alpha.
7943 - Make the SIGNAL DUMP control-port command work on FreeBSD. Fixes bug
7944 2917. Bugfix on 0.1.1.1-alpha.
7945 - Only limit the lengths of single HS descriptors, even when multiple
7946 HS descriptors are published to an HSDir relay in a single POST
7947 operation. Fixes bug 2948; bugfix on 0.2.1.5-alpha. Found by hsdir.
7948 - Write the current time into the LastWritten line in our state file,
7949 rather than the time from the previous write attempt. Also, stop
7950 trying to use a time of -1 in our log statements. Fixes bug 3039;
7951 bugfix on 0.2.2.14-alpha.
7952 - Be more consistent in our treatment of file system paths. "~" should
7953 get expanded to the user's home directory in the Log config option.
7954 Fixes bug 2971; bugfix on 0.2.0.1-alpha, which introduced the
7955 feature for the -f and --DataDirectory options.
7958 - Make sure every relay writes a state file at least every 12 hours.
7959 Previously, a relay could go for weeks without writing its state
7960 file, and on a crash could lose its bandwidth history, capacity
7961 estimates, client country statistics, and so on. Addresses bug 3012.
7962 - Send END_STREAM_REASON_NOROUTE in response to EHOSTUNREACH errors.
7963 Clients before 0.2.1.27 didn't handle NOROUTE correctly, but such
7964 clients are already deprecated because of security bugs.
7965 - Don't allow v0 hidden service authorities to act as clients.
7966 Required by fix for bug 3000.
7967 - Ignore SIGNAL NEWNYM commands on relay-only Tor instances. Required
7968 by fix for bug 3000.
7969 - Ensure that no empty [dirreq-](read|write)-history lines are added
7970 to an extrainfo document. Implements ticket 2497.
7972 o Code simplification and refactoring:
7973 - Remove workaround code to handle directory responses from servers
7974 that had bug 539 (they would send HTTP status 503 responses _and_
7975 send a body too). Since only server versions before
7976 0.2.0.16-alpha/0.1.2.19 were affected, there is no longer reason to
7977 keep the workaround in place.
7978 - Remove the old 'fuzzy time' logic. It was supposed to be used for
7979 handling calculations where we have a known amount of clock skew and
7980 an allowed amount of unknown skew. But we only used it in three
7981 places, and we never adjusted the known/unknown skew values. This is
7982 still something we might want to do someday, but if we do, we'll
7983 want to do it differently.
7984 - Avoid signed/unsigned comparisons by making SIZE_T_CEILING unsigned.
7985 None of the cases where we did this before were wrong, but by making
7986 this change we avoid warnings. Fixes bug 2475; bugfix on 0.2.1.28.
7987 - Use GetTempDir to find the proper temporary directory location on
7988 Windows when generating temporary files for the unit tests. Patch by
7992 Changes in version 0.2.2.24-alpha - 2011-04-08
7993 Tor 0.2.2.24-alpha fixes a variety of bugs, including a big bug that
7994 prevented Tor clients from effectively using "multihomed" bridges,
7995 that is, bridges that listen on multiple ports or IP addresses so users
7996 can continue to use some of their addresses even if others get blocked.
7999 - Fix a bug where bridge users who configure the non-canonical
8000 address of a bridge automatically switch to its canonical
8001 address. If a bridge listens at more than one address, it should be
8002 able to advertise those addresses independently and any non-blocked
8003 addresses should continue to work. Bugfix on Tor 0.2.0.x. Fixes
8005 - If you configured Tor to use bridge A, and then quit and
8006 configured Tor to use bridge B instead, it would happily continue
8007 to use bridge A if it's still reachable. While this behavior is
8008 a feature if your goal is connectivity, in some scenarios it's a
8009 dangerous bug. Bugfix on Tor 0.2.0.1-alpha; fixes bug 2511.
8010 - Directory authorities now use data collected from their own
8011 uptime observations when choosing whether to assign the HSDir flag
8012 to relays, instead of trusting the uptime value the relay reports in
8013 its descriptor. This change helps prevent an attack where a small
8014 set of nodes with frequently-changing identity keys can blackhole
8015 a hidden service. (Only authorities need upgrade; others will be
8016 fine once they do.) Bugfix on 0.2.0.10-alpha; fixes bug 2709.
8019 - When we restart our relay, we might get a successful connection
8020 from the outside before we've started our reachability tests,
8021 triggering a warning: "ORPort found reachable, but I have no
8022 routerinfo yet. Failing to inform controller of success." This
8023 bug was harmless unless Tor is running under a controller
8024 like Vidalia, in which case the controller would never get a
8025 REACHABILITY_SUCCEEDED status event. Bugfix on 0.1.2.6-alpha;
8027 - Make directory authorities more accurate at recording when
8028 relays that have failed several reachability tests became
8029 unreachable, so we can provide more accuracy at assigning Stable,
8030 Guard, HSDir, etc flags. Bugfix on 0.2.0.6-alpha. Resolves bug 2716.
8031 - Fix an issue that prevented static linking of libevent on
8032 some platforms (notably Linux). Fixes bug 2698; bugfix on
8033 versions 0.2.1.23/0.2.2.8-alpha (the versions introducing
8034 the --with-static-libevent configure option).
8035 - We now ask the other side of a stream (the client or the exit)
8036 for more data on that stream when the amount of queued data on
8037 that stream dips low enough. Previously, we wouldn't ask the
8038 other side for more data until either it sent us more data (which
8039 it wasn't supposed to do if it had exhausted its window!) or we
8040 had completely flushed all our queued data. This flow control fix
8041 should improve throughput. Fixes bug 2756; bugfix on the earliest
8042 released versions of Tor (svn commit r152).
8043 - Avoid a double-mark-for-free warning when failing to attach a
8044 transparent proxy connection. (We thought we had fixed this in
8045 0.2.2.23-alpha, but it turns out our fix was checking the wrong
8046 connection.) Fixes bug 2757; bugfix on 0.1.2.1-alpha (the original
8047 bug) and 0.2.2.23-alpha (the incorrect fix).
8048 - When warning about missing zlib development packages during compile,
8049 give the correct package names. Bugfix on 0.2.0.1-alpha.
8052 - Directory authorities now log the source of a rejected POSTed v3
8054 - Make compilation with clang possible when using
8055 --enable-gcc-warnings by removing two warning options that clang
8056 hasn't implemented yet and by fixing a few warnings. Implements
8058 - When expiring circuits, use microsecond timers rather than
8059 one-second timers. This can avoid an unpleasant situation where a
8060 circuit is launched near the end of one second and expired right
8061 near the beginning of the next, and prevent fluctuations in circuit
8063 - Use computed circuit-build timeouts to decide when to launch
8064 parallel introduction circuits for hidden services. (Previously,
8065 we would retry after 15 seconds.)
8066 - Update to the April 1 2011 Maxmind GeoLite Country database.
8069 - Create the /var/run/tor directory on startup on OpenSUSE if it is
8070 not already created. Patch from Andreas Stieger. Fixes bug 2573.
8072 o Documentation changes:
8073 - Modernize the doxygen configuration file slightly. Fixes bug 2707.
8074 - Resolve all doxygen warnings except those for missing documentation.
8076 - Add doxygen documentation for more functions, fields, and types.
8079 Changes in version 0.2.2.23-alpha - 2011-03-08
8080 Tor 0.2.2.23-alpha lets relays record their bandwidth history so when
8081 they restart they don't lose their bandwidth capacity estimate. This
8082 release also fixes a diverse set of user-facing bugs, ranging from
8083 relays overrunning their rate limiting to clients falsely warning about
8084 clock skew to bridge descriptor leaks by our bridge directory authority.
8087 - Stop sending a CLOCK_SKEW controller status event whenever
8088 we fetch directory information from a relay that has a wrong clock.
8089 Instead, only inform the controller when it's a trusted authority
8090 that claims our clock is wrong. Bugfix on 0.1.2.6-alpha; fixes
8091 the rest of bug 1074.
8092 - Fix an assert in parsing router descriptors containing IPv6
8093 addresses. This one took down the directory authorities when
8094 somebody tried some experimental code. Bugfix on 0.2.1.3-alpha.
8095 - Make the bridge directory authority refuse to answer directory
8096 requests for "all" descriptors. It used to include bridge
8097 descriptors in its answer, which was a major information leak.
8098 Found by "piebeer". Bugfix on 0.2.0.3-alpha.
8099 - If relays set RelayBandwidthBurst but not RelayBandwidthRate,
8100 Tor would ignore their RelayBandwidthBurst setting,
8101 potentially using more bandwidth than expected. Bugfix on
8102 0.2.0.1-alpha. Reported by Paul Wouters. Fixes bug 2470.
8103 - Ignore and warn if the user mistakenly sets "PublishServerDescriptor
8104 hidserv" in her torrc. The 'hidserv' argument never controlled
8105 publication of hidden service descriptors. Bugfix on 0.2.0.1-alpha.
8108 - Relays now save observed peak bandwidth throughput rates to their
8109 state file (along with total usage, which was already saved)
8110 so that they can determine their correct estimated bandwidth on
8111 restart. Resolves bug 1863, where Tor relays would reset their
8112 estimated bandwidth to 0 after restarting.
8113 - Directory authorities now take changes in router IP address and
8114 ORPort into account when determining router stability. Previously,
8115 if a router changed its IP or ORPort, the authorities would not
8116 treat it as having any downtime for the purposes of stability
8117 calculation, whereas clients would experience downtime since the
8118 change could take a while to propagate to them. Resolves issue 1035.
8119 - Enable Address Space Layout Randomization (ASLR) and Data Execution
8120 Prevention (DEP) by default on Windows to make it harder for
8121 attackers to exploit vulnerabilities. Patch from John Brooks.
8123 o Minor bugfixes (on 0.2.1.x and earlier):
8124 - Fix a rare crash bug that could occur when a client was configured
8125 with a large number of bridges. Fixes bug 2629; bugfix on
8126 0.2.1.2-alpha. Bugfix by trac user "shitlei".
8127 - Avoid a double mark-for-free warning when failing to attach a
8128 transparent proxy connection. Bugfix on 0.1.2.1-alpha. Fixes
8130 - Correctly detect failure to allocate an OpenSSL BIO. Fixes bug 2378;
8131 found by "cypherpunks". This bug was introduced before the first
8132 Tor release, in svn commit r110.
8133 - Country codes aren't supported in EntryNodes until 0.2.3.x, so
8134 don't mention them in the manpage. Fixes bug 2450; issue
8135 spotted by keb and G-Lo.
8136 - Fix a bug in bandwidth history state parsing that could have been
8137 triggered if a future version of Tor ever changed the timing
8138 granularity at which bandwidth history is measured. Bugfix on
8140 - When a relay decides that its DNS is too broken for it to serve
8141 as an exit server, it advertised itself as a non-exit, but
8142 continued to act as an exit. This could create accidental
8143 partitioning opportunities for users. Instead, if a relay is
8144 going to advertise reject *:* as its exit policy, it should
8145 really act with exit policy "reject *:*". Fixes bug 2366.
8146 Bugfix on Tor 0.1.2.5-alpha. Bugfix by user "postman" on trac.
8147 - In the special case where you configure a public exit relay as your
8148 bridge, Tor would be willing to use that exit relay as the last
8149 hop in your circuit as well. Now we fail that circuit instead.
8150 Bugfix on 0.2.0.12-alpha. Fixes bug 2403. Reported by "piebeer".
8151 - Fix a bug with our locking implementation on Windows that couldn't
8152 correctly detect when a file was already locked. Fixes bug 2504,
8153 bugfix on 0.2.1.6-alpha.
8154 - Fix IPv6-related connect() failures on some platforms (BSD, OS X).
8155 Bugfix on 0.2.0.3-alpha; fixes first part of bug 2660. Patch by
8157 - Set target port in get_interface_address6() correctly. Bugfix
8158 on 0.1.1.4-alpha and 0.2.0.3-alpha; fixes second part of bug 2660.
8159 - Directory authorities are now more robust to hops back in time
8160 when calculating router stability. Previously, if a run of uptime
8161 or downtime appeared to be negative, the calculation could give
8162 incorrect results. Bugfix on 0.2.0.6-alpha; noticed when fixing
8164 - Fix an assert that got triggered when using the TestingTorNetwork
8165 configuration option and then issuing a GETINFO config-text control
8166 command. Fixes bug 2250; bugfix on 0.2.1.2-alpha.
8168 o Minor bugfixes (on 0.2.2.x):
8169 - Clients should not weight BadExit nodes as Exits in their node
8170 selection. Similarly, directory authorities should not count BadExit
8171 bandwidth as Exit bandwidth when computing bandwidth-weights.
8172 Bugfix on 0.2.2.10-alpha; fixes bug 2203.
8173 - Correctly clear our dir_read/dir_write history when there is an
8174 error parsing any bw history value from the state file. Bugfix on
8176 - Resolve a bug in verifying signatures of directory objects
8177 with digests longer than SHA1. Bugfix on 0.2.2.20-alpha.
8178 Fixes bug 2409. Found by "piebeer".
8179 - Bridge authorities no longer crash on SIGHUP when they try to
8180 publish their relay descriptor to themselves. Fixes bug 2572. Bugfix
8184 - Log less aggressively about circuit timeout changes, and improve
8185 some other circuit timeout messages. Resolves bug 2004.
8186 - Log a little more clearly about the times at which we're no longer
8187 accepting new connections. Resolves bug 2181.
8188 - Reject attempts at the client side to open connections to private
8189 IP addresses (like 127.0.0.1, 10.0.0.1, and so on) with
8190 a randomly chosen exit node. Attempts to do so are always
8191 ill-defined, generally prevented by exit policies, and usually
8192 in error. This will also help to detect loops in transparent
8193 proxy configurations. You can disable this feature by setting
8194 "ClientRejectInternalAddresses 0" in your torrc.
8195 - Always treat failure to allocate an RSA key as an unrecoverable
8197 - Update to the March 1 2011 Maxmind GeoLite Country database.
8199 o Minor features (log subsystem):
8200 - Add documentation for configuring logging at different severities in
8201 different log domains. We've had this feature since 0.2.1.1-alpha,
8202 but for some reason it never made it into the manpage. Fixes
8204 - Make it simpler to specify "All log domains except for A and B".
8205 Previously you needed to say "[*,~A,~B]". Now you can just say
8207 - Add a "LogMessageDomains 1" option to include the domains of log
8208 messages along with the messages. Without this, there's no way
8209 to use log domains without reading the source or doing a lot
8212 o Packaging changes:
8213 - Stop shipping the Tor specs files and development proposal documents
8214 in the tarball. They are now in a separate git repository at
8215 git://git.torproject.org/torspec.git
8218 Changes in version 0.2.1.30 - 2011-02-23
8219 Tor 0.2.1.30 fixes a variety of less critical bugs. The main other
8220 change is a slight tweak to Tor's TLS handshake that makes relays
8221 and bridges that run this new version reachable from Iran again.
8222 We don't expect this tweak will win the arms race long-term, but it
8223 buys us time until we roll out a better solution.
8226 - Stop sending a CLOCK_SKEW controller status event whenever
8227 we fetch directory information from a relay that has a wrong clock.
8228 Instead, only inform the controller when it's a trusted authority
8229 that claims our clock is wrong. Bugfix on 0.1.2.6-alpha; fixes
8230 the rest of bug 1074.
8231 - Fix a bounds-checking error that could allow an attacker to
8232 remotely crash a directory authority. Bugfix on 0.2.1.5-alpha.
8234 - If relays set RelayBandwidthBurst but not RelayBandwidthRate,
8235 Tor would ignore their RelayBandwidthBurst setting,
8236 potentially using more bandwidth than expected. Bugfix on
8237 0.2.0.1-alpha. Reported by Paul Wouters. Fixes bug 2470.
8238 - Ignore and warn if the user mistakenly sets "PublishServerDescriptor
8239 hidserv" in her torrc. The 'hidserv' argument never controlled
8240 publication of hidden service descriptors. Bugfix on 0.2.0.1-alpha.
8243 - Adjust our TLS Diffie-Hellman parameters to match those used by
8245 - Update to the February 1 2011 Maxmind GeoLite Country database.
8248 - Check for and reject overly long directory certificates and
8249 directory tokens before they have a chance to hit any assertions.
8250 Bugfix on 0.2.1.28. Found by "doorss".
8251 - Bring the logic that gathers routerinfos and assesses the
8252 acceptability of circuits into line. This prevents a Tor OP from
8253 getting locked in a cycle of choosing its local OR as an exit for a
8254 path (due to a .exit request) and then rejecting the circuit because
8255 its OR is not listed yet. It also prevents Tor clients from using an
8256 OR running in the same instance as an exit (due to a .exit request)
8257 if the OR does not meet the same requirements expected of an OR
8258 running elsewhere. Fixes bug 1859; bugfix on 0.1.0.1-rc.
8260 o Packaging changes:
8261 - Stop shipping the Tor specs files and development proposal documents
8262 in the tarball. They are now in a separate git repository at
8263 git://git.torproject.org/torspec.git
8264 - Do not include Git version tags as though they are SVN tags when
8265 generating a tarball from inside a repository that has switched
8266 between branches. Bugfix on 0.2.1.15-rc; fixes bug 2402.
8269 Changes in version 0.2.2.22-alpha - 2011-01-25
8270 Tor 0.2.2.22-alpha fixes a few more less-critical security issues. The
8271 main other change is a slight tweak to Tor's TLS handshake that makes
8272 relays and bridges that run this new version reachable from Iran again.
8273 We don't expect this tweak will win the arms race long-term, but it
8274 will buy us a bit more time until we roll out a better solution.
8277 - Fix a bounds-checking error that could allow an attacker to
8278 remotely crash a directory authority. Bugfix on 0.2.1.5-alpha.
8280 - Don't assert when changing from bridge to relay or vice versa
8281 via the controller. The assert happened because we didn't properly
8282 initialize our keys in this case. Bugfix on 0.2.2.18-alpha; fixes
8283 bug 2433. Reported by bastik.
8286 - Adjust our TLS Diffie-Hellman parameters to match those used by
8288 - Provide a log message stating which geoip file we're parsing
8289 instead of just stating that we're parsing the geoip file.
8290 Implements ticket 2432.
8293 - Check for and reject overly long directory certificates and
8294 directory tokens before they have a chance to hit any assertions.
8295 Bugfix on 0.2.1.28 / 0.2.2.20-alpha. Found by "doorss".
8298 Changes in version 0.2.2.21-alpha - 2011-01-15
8299 Tor 0.2.2.21-alpha includes all the patches from Tor 0.2.1.29, which
8300 continues our recent code security audit work. The main fix resolves
8301 a remote heap overflow vulnerability that can allow remote code
8302 execution (CVE-2011-0427). Other fixes address a variety of assert
8303 and crash bugs, most of which we think are hard to exploit remotely.
8305 o Major bugfixes (security), also included in 0.2.1.29:
8306 - Fix a heap overflow bug where an adversary could cause heap
8307 corruption. This bug probably allows remote code execution
8308 attacks. Reported by "debuger". Fixes CVE-2011-0427. Bugfix on
8310 - Prevent a denial-of-service attack by disallowing any
8311 zlib-compressed data whose compression factor is implausibly
8312 high. Fixes part of bug 2324; reported by "doorss".
8313 - Zero out a few more keys in memory before freeing them. Fixes
8314 bug 2384 and part of bug 2385. These key instances found by
8315 "cypherpunks", based on Andrew Case's report about being able
8316 to find sensitive data in Tor's memory space if you have enough
8317 permissions. Bugfix on 0.0.2pre9.
8319 o Major bugfixes (crashes), also included in 0.2.1.29:
8320 - Prevent calls to Libevent from inside Libevent log handlers.
8321 This had potential to cause a nasty set of crashes, especially
8322 if running Libevent with debug logging enabled, and running
8323 Tor with a controller watching for low-severity log messages.
8324 Bugfix on 0.1.0.2-rc. Fixes bug 2190.
8325 - Add a check for SIZE_T_MAX to tor_realloc() to try to avoid
8326 underflow errors there too. Fixes the other part of bug 2324.
8327 - Fix a bug where we would assert if we ever had a
8328 cached-descriptors.new file (or another file read directly into
8329 memory) of exactly SIZE_T_CEILING bytes. Fixes bug 2326; bugfix
8330 on 0.2.1.25. Found by doorss.
8331 - Fix some potential asserts and parsing issues with grossly
8332 malformed router caches. Fixes bug 2352; bugfix on Tor 0.2.1.27.
8335 o Minor bugfixes (other), also included in 0.2.1.29:
8336 - Fix a bug with handling misformed replies to reverse DNS lookup
8337 requests in DNSPort. Bugfix on Tor 0.2.0.1-alpha. Related to a
8338 bug reported by doorss.
8339 - Fix compilation on mingw when a pthreads compatibility library
8340 has been installed. (We don't want to use it, so we shouldn't
8341 be including pthread.h.) Fixes bug 2313; bugfix on 0.1.0.1-rc.
8342 - Fix a bug where we would declare that we had run out of virtual
8343 addresses when the address space was only half-exhausted. Bugfix
8345 - Correctly handle the case where AutomapHostsOnResolve is set but
8346 no virtual addresses are available. Fixes bug 2328; bugfix on
8347 0.1.2.1-alpha. Bug found by doorss.
8348 - Correctly handle wrapping around when we run out of virtual
8349 address space. Found by cypherpunks; bugfix on 0.2.0.5-alpha.
8351 o Minor features, also included in 0.2.1.29:
8352 - Update to the January 1 2011 Maxmind GeoLite Country database.
8353 - Introduce output size checks on all of our decryption functions.
8355 o Build changes, also included in 0.2.1.29:
8356 - Tor does not build packages correctly with Automake 1.6 and earlier;
8357 added a check to Makefile.am to make sure that we're building with
8358 Automake 1.7 or later.
8359 - The 0.2.1.28 tarball was missing src/common/OpenBSD_malloc_Linux.c
8360 because we built it with a too-old version of automake. Thus that
8361 release broke ./configure --enable-openbsd-malloc, which is popular
8362 among really fast exit relays on Linux.
8364 o Major bugfixes, new in 0.2.2.21-alpha:
8365 - Prevent crash/heap corruption when the cbtnummodes consensus
8366 parameter is set to 0 or large values. Fixes bug 2317; bugfix
8369 o Major features, new in 0.2.2.21-alpha:
8370 - Introduce minimum/maximum values that clients will believe
8371 from the consensus. Now we'll have a better chance to avoid crashes
8372 or worse when a consensus param has a weird value.
8374 o Minor features, new in 0.2.2.21-alpha:
8375 - Make sure to disable DirPort if running as a bridge. DirPorts aren't
8376 used on bridges, and it makes bridge scanning somewhat easier.
8377 - If writing the state file to disk fails, wait up to an hour before
8378 retrying again, rather than trying again each second. Fixes bug
8379 2346; bugfix on Tor 0.1.1.3-alpha.
8380 - Make Libevent log messages get delivered to controllers later,
8381 and not from inside the Libevent log handler. This prevents unsafe
8382 reentrant Libevent calls while still letting the log messages
8384 - Detect platforms that brokenly use a signed size_t, and refuse to
8385 build there. Found and analyzed by doorss and rransom.
8386 - Fix a bunch of compile warnings revealed by mingw with gcc 4.5.
8389 o Minor bugfixes, new in 0.2.2.21-alpha:
8390 - Handle SOCKS messages longer than 128 bytes long correctly, rather
8391 than waiting forever for them to finish. Fixes bug 2330; bugfix
8392 on 0.2.0.16-alpha. Found by doorss.
8393 - Add assertions to check for overflow in arguments to
8394 base32_encode() and base32_decode(); fix a signed-unsigned
8395 comparison there too. These bugs are not actually reachable in Tor,
8396 but it's good to prevent future errors too. Found by doorss.
8397 - Correctly detect failures to create DNS requests when using Libevent
8398 versions before v2. (Before Libevent 2, we used our own evdns
8399 implementation. Its return values for Libevent's evdns_resolve_*()
8400 functions are not consistent with those from Libevent.) Fixes bug
8401 2363; bugfix on 0.2.2.6-alpha. Found by "lodger".
8403 o Documentation, new in 0.2.2.21-alpha:
8404 - Document the default socks host and port (127.0.0.1:9050) for
8408 Changes in version 0.2.1.29 - 2011-01-15
8409 Tor 0.2.1.29 continues our recent code security audit work. The main
8410 fix resolves a remote heap overflow vulnerability that can allow remote
8411 code execution. Other fixes address a variety of assert and crash bugs,
8412 most of which we think are hard to exploit remotely.
8414 o Major bugfixes (security):
8415 - Fix a heap overflow bug where an adversary could cause heap
8416 corruption. This bug probably allows remote code execution
8417 attacks. Reported by "debuger". Fixes CVE-2011-0427. Bugfix on
8419 - Prevent a denial-of-service attack by disallowing any
8420 zlib-compressed data whose compression factor is implausibly
8421 high. Fixes part of bug 2324; reported by "doorss".
8422 - Zero out a few more keys in memory before freeing them. Fixes
8423 bug 2384 and part of bug 2385. These key instances found by
8424 "cypherpunks", based on Andrew Case's report about being able
8425 to find sensitive data in Tor's memory space if you have enough
8426 permissions. Bugfix on 0.0.2pre9.
8428 o Major bugfixes (crashes):
8429 - Prevent calls to Libevent from inside Libevent log handlers.
8430 This had potential to cause a nasty set of crashes, especially
8431 if running Libevent with debug logging enabled, and running
8432 Tor with a controller watching for low-severity log messages.
8433 Bugfix on 0.1.0.2-rc. Fixes bug 2190.
8434 - Add a check for SIZE_T_MAX to tor_realloc() to try to avoid
8435 underflow errors there too. Fixes the other part of bug 2324.
8436 - Fix a bug where we would assert if we ever had a
8437 cached-descriptors.new file (or another file read directly into
8438 memory) of exactly SIZE_T_CEILING bytes. Fixes bug 2326; bugfix
8439 on 0.2.1.25. Found by doorss.
8440 - Fix some potential asserts and parsing issues with grossly
8441 malformed router caches. Fixes bug 2352; bugfix on Tor 0.2.1.27.
8444 o Minor bugfixes (other):
8445 - Fix a bug with handling misformed replies to reverse DNS lookup
8446 requests in DNSPort. Bugfix on Tor 0.2.0.1-alpha. Related to a
8447 bug reported by doorss.
8448 - Fix compilation on mingw when a pthreads compatibility library
8449 has been installed. (We don't want to use it, so we shouldn't
8450 be including pthread.h.) Fixes bug 2313; bugfix on 0.1.0.1-rc.
8451 - Fix a bug where we would declare that we had run out of virtual
8452 addresses when the address space was only half-exhausted. Bugfix
8454 - Correctly handle the case where AutomapHostsOnResolve is set but
8455 no virtual addresses are available. Fixes bug 2328; bugfix on
8456 0.1.2.1-alpha. Bug found by doorss.
8457 - Correctly handle wrapping around to when we run out of virtual
8458 address space. Found by cypherpunks, bugfix on 0.2.0.5-alpha.
8459 - The 0.2.1.28 tarball was missing src/common/OpenBSD_malloc_Linux.c
8460 because we built it with a too-old version of automake. Thus that
8461 release broke ./configure --enable-openbsd-malloc, which is popular
8462 among really fast exit relays on Linux.
8465 - Update to the January 1 2011 Maxmind GeoLite Country database.
8466 - Introduce output size checks on all of our decryption functions.
8469 - Tor does not build packages correctly with Automake 1.6 and earlier;
8470 added a check to Makefile.am to make sure that we're building with
8471 Automake 1.7 or later.
8474 Changes in version 0.2.2.20-alpha - 2010-12-17
8475 Tor 0.2.2.20-alpha does some code cleanup to reduce the risk of remotely
8476 exploitable bugs. We also fix a variety of other significant bugs,
8477 change the IP address for one of our directory authorities, and update
8478 the minimum version that Tor relays must run to join the network.
8481 - Fix a remotely exploitable bug that could be used to crash instances
8482 of Tor remotely by overflowing on the heap. Remote-code execution
8483 hasn't been confirmed, but can't be ruled out. Everyone should
8484 upgrade. Bugfix on the 0.1.1 series and later.
8485 - Fix a bug that could break accounting on 64-bit systems with large
8486 time_t values, making them hibernate for impossibly long intervals.
8487 Fixes bug 2146. Bugfix on 0.0.9pre6; fix by boboper.
8488 - Fix a logic error in directory_fetches_from_authorities() that
8489 would cause all _non_-exits refusing single-hop-like circuits
8490 to fetch from authorities, when we wanted to have _exits_ fetch
8491 from authorities. Fixes more of 2097. Bugfix on 0.2.2.16-alpha;
8493 - Fix a stream fairness bug that would cause newer streams on a given
8494 circuit to get preference when reading bytes from the origin or
8495 destination. Fixes bug 2210. Fix by Mashael AlSabah. This bug was
8496 introduced before the first Tor release, in svn revision r152.
8498 o Directory authority changes:
8499 - Change IP address and ports for gabelmoo (v3 directory authority).
8502 - Avoid crashes when AccountingMax is set on clients. Fixes bug 2235.
8503 Bugfix on 0.2.2.18-alpha. Diagnosed by boboper.
8504 - Fix an off-by-one error in calculating some controller command
8505 argument lengths. Fortunately, this mistake is harmless since
8506 the controller code does redundant NUL termination too. Found by
8507 boboper. Bugfix on 0.1.1.1-alpha.
8508 - Do not dereference NULL if a bridge fails to build its
8509 extra-info descriptor. Found by an anonymous commenter on
8510 Trac. Bugfix on 0.2.2.19-alpha.
8513 - Update to the December 1 2010 Maxmind GeoLite Country database.
8514 - Directory authorities now reject relays running any versions of
8515 Tor between 0.2.1.3-alpha and 0.2.1.18 inclusive; they have
8516 known bugs that keep RELAY_EARLY cells from working on rendezvous
8517 circuits. Followup to fix for bug 2081.
8518 - Directory authorities now reject relays running any version of Tor
8519 older than 0.2.0.26-rc. That version is the earliest that fetches
8520 current directory information correctly. Fixes bug 2156.
8521 - Report only the top 10 ports in exit-port stats in order not to
8522 exceed the maximum extra-info descriptor length of 50 KB. Implements
8526 Changes in version 0.2.1.28 - 2010-12-17
8527 Tor 0.2.1.28 does some code cleanup to reduce the risk of remotely
8528 exploitable bugs. We also took this opportunity to change the IP address
8529 for one of our directory authorities, and to update the geoip database
8533 - Fix a remotely exploitable bug that could be used to crash instances
8534 of Tor remotely by overflowing on the heap. Remote-code execution
8535 hasn't been confirmed, but can't be ruled out. Everyone should
8536 upgrade. Bugfix on the 0.1.1 series and later.
8538 o Directory authority changes:
8539 - Change IP address and ports for gabelmoo (v3 directory authority).
8542 - Update to the December 1 2010 Maxmind GeoLite Country database.
8545 Changes in version 0.2.1.27 - 2010-11-23
8546 Yet another OpenSSL security patch broke its compatibility with Tor:
8547 Tor 0.2.1.27 makes relays work with openssl 0.9.8p and 1.0.0.b. We
8548 also took this opportunity to fix several crash bugs, integrate a new
8549 directory authority, and update the bundled GeoIP database.
8552 - Resolve an incompatibility with OpenSSL 0.9.8p and OpenSSL 1.0.0b:
8553 No longer set the tlsext_host_name extension on server SSL objects;
8554 but continue to set it on client SSL objects. Our goal in setting
8555 it was to imitate a browser, not a vhosting server. Fixes bug 2204;
8556 bugfix on 0.2.1.1-alpha.
8557 - Do not log messages to the controller while shrinking buffer
8558 freelists. Doing so would sometimes make the controller connection
8559 try to allocate a buffer chunk, which would mess up the internals
8560 of the freelist and cause an assertion failure. Fixes bug 1125;
8561 fixed by Robert Ransom. Bugfix on 0.2.0.16-alpha.
8562 - Learn our external IP address when we're a relay or bridge, even if
8563 we set PublishServerDescriptor to 0. Bugfix on 0.2.0.3-alpha,
8564 where we introduced bridge relays that don't need to publish to
8565 be useful. Fixes bug 2050.
8566 - Do even more to reject (and not just ignore) annotations on
8567 router descriptors received anywhere but from the cache. Previously
8568 we would ignore such annotations at first, but cache them to disk
8569 anyway. Bugfix on 0.2.0.8-alpha. Found by piebeer.
8570 - When you're using bridges and your network goes away and your
8571 bridges get marked as down, recover when you attempt a new socks
8572 connection (if the network is back), rather than waiting up to an
8573 hour to try fetching new descriptors for your bridges. Bugfix on
8574 0.2.0.3-alpha; fixes bug 1981.
8577 - Move to the November 2010 Maxmind GeoLite country db (rather
8578 than the June 2009 ip-to-country GeoIP db) for our statistics that
8579 count how many users relays are seeing from each country. Now we'll
8580 have more accurate data, especially for many African countries.
8582 o New directory authorities:
8583 - Set up maatuska (run by Linus Nordberg) as the eighth v3 directory
8587 - Fix an assertion failure that could occur in directory caches or
8588 bridge users when using a very short voting interval on a testing
8589 network. Diagnosed by Robert Hogan. Fixes bug 1141; bugfix on
8591 - Enforce multiplicity rules when parsing annotations. Bugfix on
8592 0.2.0.8-alpha. Found by piebeer.
8593 - Allow handshaking OR connections to take a full KeepalivePeriod
8594 seconds to handshake. Previously, we would close them after
8595 IDLE_OR_CONN_TIMEOUT (180) seconds, the same timeout as if they
8596 were open. Bugfix on 0.2.1.26; fixes bug 1840. Thanks to mingw-san
8598 - When building with --enable-gcc-warnings on OpenBSD, disable
8599 warnings in system headers. This makes --enable-gcc-warnings
8600 pass on OpenBSD 4.8.
8603 - Exit nodes didn't recognize EHOSTUNREACH as a plausible error code,
8604 and so sent back END_STREAM_REASON_MISC. Clients now recognize a new
8605 stream ending reason for this case: END_STREAM_REASON_NOROUTE.
8606 Servers can start sending this code when enough clients recognize
8607 it. Bugfix on 0.1.0.1-rc; fixes part of bug 1793.
8608 - Build correctly on mingw with more recent versions of OpenSSL 0.9.8.
8609 Patch from mingw-san.
8612 - Remove the old debian/ directory from the main Tor distribution.
8613 The official Tor-for-debian git repository lives at the URL
8614 https://git.torproject.org/debian/tor.git
8615 - Stop shipping the old doc/website/ directory in the tarball. We
8616 changed the website format in late 2010, and what we shipped in
8617 0.2.1.26 really wasn't that useful anyway.
8620 Changes in version 0.2.2.19-alpha - 2010-11-22
8621 Yet another OpenSSL security patch broke its compatibility with Tor:
8622 Tor 0.2.2.19-alpha makes relays work with OpenSSL 0.9.8p and 1.0.0.b.
8625 - Resolve an incompatibility with OpenSSL 0.9.8p and OpenSSL 1.0.0b:
8626 No longer set the tlsext_host_name extension on server SSL objects;
8627 but continue to set it on client SSL objects. Our goal in setting
8628 it was to imitate a browser, not a vhosting server. Fixes bug 2204;
8629 bugfix on 0.2.1.1-alpha.
8632 - Try harder not to exceed the maximum length of 50 KB when writing
8633 statistics to extra-info descriptors. This bug was triggered by very
8634 fast relays reporting exit-port, entry, and dirreq statistics.
8635 Reported by Olaf Selke. Bugfix on 0.2.2.1-alpha. Fixes bug 2183.
8636 - Publish a router descriptor even if generating an extra-info
8637 descriptor fails. Previously we would not publish a router
8638 descriptor without an extra-info descriptor; this can cause fast
8639 exit relays collecting exit-port statistics to drop from the
8640 consensus. Bugfix on 0.1.2.9-rc; fixes bug 2195.
8643 Changes in version 0.2.2.18-alpha - 2010-11-16
8644 Tor 0.2.2.18-alpha fixes several crash bugs that have been nagging
8645 us lately, makes unpublished bridge relays able to detect their IP
8646 address, and fixes a wide variety of other bugs to get us much closer
8647 to a stable release.
8650 - Do even more to reject (and not just ignore) annotations on
8651 router descriptors received anywhere but from the cache. Previously
8652 we would ignore such annotations at first, but cache them to disk
8653 anyway. Bugfix on 0.2.0.8-alpha. Found by piebeer.
8654 - Do not log messages to the controller while shrinking buffer
8655 freelists. Doing so would sometimes make the controller connection
8656 try to allocate a buffer chunk, which would mess up the internals
8657 of the freelist and cause an assertion failure. Fixes bug 1125;
8658 fixed by Robert Ransom. Bugfix on 0.2.0.16-alpha.
8659 - Learn our external IP address when we're a relay or bridge, even if
8660 we set PublishServerDescriptor to 0. Bugfix on 0.2.0.3-alpha,
8661 where we introduced bridge relays that don't need to publish to
8662 be useful. Fixes bug 2050.
8663 - Maintain separate TLS contexts and certificates for incoming and
8664 outgoing connections in bridge relays. Previously we would use the
8665 same TLS contexts and certs for incoming and outgoing connections.
8666 Bugfix on 0.2.0.3-alpha; addresses bug 988.
8667 - Maintain separate identity keys for incoming and outgoing TLS
8668 contexts in bridge relays. Previously we would use the same
8669 identity keys for incoming and outgoing TLS contexts. Bugfix on
8670 0.2.0.3-alpha; addresses the other half of bug 988.
8671 - Avoid an assertion failure when we as an authority receive a
8672 duplicate upload of a router descriptor that we already have,
8673 but which we previously considered an obsolete descriptor.
8674 Fixes another case of bug 1776. Bugfix on 0.2.2.16-alpha.
8675 - Avoid a crash bug triggered by looking at a dangling pointer while
8676 setting the network status consensus. Found by Robert Ransom.
8677 Bugfix on 0.2.2.17-alpha. Fixes bug 2097.
8678 - Fix a logic error where servers that _didn't_ act as exits would
8679 try to keep their server lists more aggressively up to date than
8680 exits, when it was supposed to be the other way around. Bugfix
8683 o Minor bugfixes (on Tor 0.2.1.x and earlier):
8684 - When we're trying to guess whether we know our IP address as
8685 a relay, we would log various ways that we failed to guess
8686 our address, but never log that we ended up guessing it
8687 successfully. Now add a log line to help confused and anxious
8688 relay operators. Bugfix on 0.1.2.1-alpha; fixes bug 1534.
8689 - Bring the logic that gathers routerinfos and assesses the
8690 acceptability of circuits into line. This prevents a Tor OP from
8691 getting locked in a cycle of choosing its local OR as an exit for a
8692 path (due to a .exit request) and then rejecting the circuit because
8693 its OR is not listed yet. It also prevents Tor clients from using an
8694 OR running in the same instance as an exit (due to a .exit request)
8695 if the OR does not meet the same requirements expected of an OR
8696 running elsewhere. Fixes bug 1859; bugfix on 0.1.0.1-rc.
8697 - Correctly describe errors that occur when generating a TLS object.
8698 Previously we would attribute them to a failure while generating a
8699 TLS context. Patch by Robert Ransom. Bugfix on 0.1.0.4-rc; fixes
8701 - Enforce multiplicity rules when parsing annotations. Bugfix on
8702 0.2.0.8-alpha. Found by piebeer.
8703 - Fix warnings that newer versions of autoconf produced during
8704 ./autogen.sh. These warnings appear to be harmless in our case,
8705 but they were extremely verbose. Fixes bug 2020.
8707 o Minor bugfixes (on Tor 0.2.2.x):
8708 - Enable protection of small arrays whenever we build with gcc
8709 hardening features, not only when also building with warnings
8710 enabled. Fixes bug 2031; bugfix on 0.2.2.14-alpha. Reported by keb.
8713 - Make hidden services work better in private Tor networks by not
8714 requiring any uptime to join the hidden service descriptor
8715 DHT. Implements ticket 2088.
8716 - Rate-limit the "your application is giving Tor only an IP address"
8717 warning. Addresses bug 2000; bugfix on 0.0.8pre2.
8718 - When AllowSingleHopExits is set, print a warning to explain to the
8719 relay operator why most clients are avoiding her relay.
8720 - Update to the November 1 2010 Maxmind GeoLite Country database.
8722 o Code simplifications and refactoring:
8723 - When we fixed bug 1038 we had to put in a restriction not to send
8724 RELAY_EARLY cells on rend circuits. This was necessary as long
8725 as relays using Tor 0.2.1.3-alpha through 0.2.1.18-alpha were
8726 active. Now remove this obsolete check. Resolves bug 2081.
8727 - Some options used different conventions for uppercasing of acronyms
8728 when comparing manpage and source. Fix those in favor of the
8729 manpage, as it makes sense to capitalize acronyms.
8730 - Remove the torrc.complete file. It hasn't been kept up to date
8731 and users will have better luck checking out the manpage.
8732 - Remove the obsolete "NoPublish" option; it has been flagged
8733 as obsolete and has produced a warning since 0.1.1.18-rc.
8734 - Remove everything related to building the expert bundle for OS X.
8735 It has confused many users, doesn't work right on OS X 10.6,
8736 and is hard to get rid of once installed. Resolves bug 1274.
8739 Changes in version 0.2.2.17-alpha - 2010-09-30
8740 Tor 0.2.2.17-alpha introduces a feature to make it harder for clients
8741 to use one-hop circuits (which can put the exit relays at higher risk,
8742 plus unbalance the network); fixes a big bug in bandwidth accounting
8743 for relays that want to limit their monthly bandwidth use; fixes a
8744 big pile of bugs in how clients tolerate temporary network failure;
8745 and makes our adaptive circuit build timeout feature (which improves
8746 client performance if your network is fast while not breaking things
8747 if your network is slow) better handle bad networks.
8750 - Exit relays now try harder to block exit attempts from unknown
8751 relays, to make it harder for people to use them as one-hop proxies
8752 a la tortunnel. Controlled by the refuseunknownexits consensus
8753 parameter (currently enabled), or you can override it on your
8754 relay with the RefuseUnknownExits torrc option. Resolves bug 1751.
8756 o Major bugfixes (0.2.1.x and earlier):
8757 - Fix a bug in bandwidth accounting that could make us use twice
8758 the intended bandwidth when our interval start changes due to
8759 daylight saving time. Now we tolerate skew in stored vs computed
8760 interval starts: if the start of the period changes by no more than
8761 50% of the period's duration, we remember bytes that we transferred
8762 in the old period. Fixes bug 1511; bugfix on 0.0.9pre5.
8763 - Always search the Windows system directory for system DLLs, and
8764 nowhere else. Bugfix on 0.1.1.23; fixes bug 1954.
8765 - When you're using bridges and your network goes away and your
8766 bridges get marked as down, recover when you attempt a new socks
8767 connection (if the network is back), rather than waiting up to an
8768 hour to try fetching new descriptors for your bridges. Bugfix on
8769 0.2.0.3-alpha; fixes bug 1981.
8771 o Major bugfixes (on 0.2.2.x):
8772 - Fix compilation on Windows. Bugfix on 0.2.2.16-alpha; related to
8774 - Fix a segfault that could happen when operating a bridge relay with
8775 no GeoIP database set. Fixes bug 1964; bugfix on 0.2.2.15-alpha.
8776 - The consensus bandwidth-weights (used by clients to choose fast
8777 relays) entered an unexpected edge case in September where
8778 Exits were much scarcer than Guards, resulting in bad weight
8779 recommendations. Now we compute them using new constraints that
8780 should succeed in all cases. Also alter directory authorities to
8781 not include the bandwidth-weights line if they fail to produce
8782 valid values. Fixes bug 1952; bugfix on 0.2.2.10-alpha.
8783 - When weighting bridges during path selection, we used to trust
8784 the bandwidths they provided in their descriptor, only capping them
8785 at 10MB/s. This turned out to be problematic for two reasons:
8786 Bridges could claim to handle a lot more traffic then they
8787 actually would, thus making more clients pick them and have a
8788 pretty effective DoS attack. The other issue is that new bridges
8789 that might not have a good estimate for their bw capacity yet
8790 would not get used at all unless no other bridges are available
8791 to a client. Fixes bug 1912; bugfix on 0.2.2.7-alpha.
8793 o Major bugfixes (on the circuit build timeout feature, 0.2.2.x):
8794 - Ignore cannibalized circuits when recording circuit build times.
8795 This should provide for a minor performance improvement for hidden
8796 service users using 0.2.2.14-alpha, and should remove two spurious
8797 notice log messages. Bugfix on 0.2.2.14-alpha; fixes bug 1740.
8798 - Simplify the logic that causes us to decide if the network is
8799 unavailable for purposes of recording circuit build times. If we
8800 receive no cells whatsoever for the entire duration of a circuit's
8801 full measured lifetime, the network is probably down. Also ignore
8802 one-hop directory fetching circuit timeouts when calculating our
8803 circuit build times. These changes should hopefully reduce the
8804 cases where we see ridiculous circuit build timeouts for people
8805 with spotty wireless connections. Fixes part of bug 1772; bugfix
8807 - Prevent the circuit build timeout from becoming larger than
8808 the maximum build time we have ever seen. Also, prevent the time
8809 period for measurement circuits from becoming larger than twice that
8810 value. Fixes the other part of bug 1772; bugfix on 0.2.2.2-alpha.
8813 - When we run out of directory information such that we can't build
8814 circuits, but then get enough that we can build circuits, log when
8815 we actually construct a circuit, so the user has a better chance of
8816 knowing what's going on. Fixes bug 1362.
8817 - Be more generous with how much bandwidth we'd use up (with
8818 accounting enabled) before entering "soft hibernation". Previously,
8819 we'd refuse new connections and circuits once we'd used up 95% of
8820 our allotment. Now, we use up 95% of our allotment, AND make sure
8821 that we have no more than 500MB (or 3 hours of expected traffic,
8822 whichever is lower) remaining before we enter soft hibernation.
8823 - If we've configured EntryNodes and our network goes away and/or all
8824 our entrynodes get marked down, optimistically retry them all when
8825 a new socks application request appears. Fixes bug 1882.
8826 - Add some more defensive programming for architectures that can't
8827 handle unaligned integer accesses. We don't know of any actual bugs
8828 right now, but that's the best time to fix them. Fixes bug 1943.
8829 - Support line continuations in the torrc config file. If a line
8830 ends with a single backslash character, the newline is ignored, and
8831 the configuration value is treated as continuing on the next line.
8834 o Minor bugfixes (on 0.2.1.x and earlier):
8835 - For bandwidth accounting, calculate our expected bandwidth rate
8836 based on the time during which we were active and not in
8837 soft-hibernation during the last interval. Previously, we were
8838 also considering the time spent in soft-hibernation. If this
8839 was a long time, we would wind up underestimating our bandwidth
8840 by a lot, and skewing our wakeup time towards the start of the
8841 accounting interval. Fixes bug 1789. Bugfix on 0.0.9pre5.
8843 o Minor bugfixes (on 0.2.2.x):
8844 - Resume generating CIRC FAILED REASON=TIMEOUT control port messages,
8845 which were disabled by the circuit build timeout changes in
8846 0.2.2.14-alpha. Bugfix on 0.2.2.14-alpha; fixes bug 1739.
8847 - Make sure we don't warn about missing bandwidth weights when
8848 choosing bridges or other relays not in the consensus. Bugfix on
8849 0.2.2.10-alpha; fixes bug 1805.
8850 - In our logs, do not double-report signatures from unrecognized
8851 authorities both as "from unknown authority" and "not
8852 present". Fixes bug 1956, bugfix on 0.2.2.16-alpha.
8855 Changes in version 0.2.2.16-alpha - 2010-09-17
8856 Tor 0.2.2.16-alpha fixes a variety of old stream fairness bugs (most
8857 evident at exit relays), and also continues to resolve all the little
8858 bugs that have been filling up trac lately.
8860 o Major bugfixes (stream-level fairness):
8861 - When receiving a circuit-level SENDME for a blocked circuit, try
8862 to package cells fairly from all the streams that had previously
8863 been blocked on that circuit. Previously, we had started with the
8864 oldest stream, and allowed each stream to potentially exhaust
8865 the circuit's package window. This gave older streams on any
8866 given circuit priority over newer ones. Fixes bug 1937. Detected
8867 originally by Camilo Viecco. This bug was introduced before the
8868 first Tor release, in svn commit r152: it is the new winner of
8869 the longest-lived bug prize.
8870 - When the exit relay got a circuit-level sendme cell, it started
8871 reading on the exit streams, even if had 500 cells queued in the
8872 circuit queue already, so the circuit queue just grew and grew in
8873 some cases. We fix this by not re-enabling reading on receipt of a
8874 sendme cell when the cell queue is blocked. Fixes bug 1653. Bugfix
8875 on 0.2.0.1-alpha. Detected by Mashael AlSabah. Original patch by
8877 - Newly created streams were allowed to read cells onto circuits,
8878 even if the circuit's cell queue was blocked and waiting to drain.
8879 This created potential unfairness, as older streams would be
8880 blocked, but newer streams would gladly fill the queue completely.
8881 We add code to detect this situation and prevent any stream from
8882 getting more than one free cell. Bugfix on 0.2.0.1-alpha. Partially
8886 - Update to the September 1 2010 Maxmind GeoLite Country database.
8887 - Warn when CookieAuthFileGroupReadable is set but CookieAuthFile is
8888 not. This would lead to a cookie that is still not group readable.
8889 Closes bug 1843. Suggested by katmagic.
8890 - When logging a rate-limited warning, we now mention how many messages
8891 got suppressed since the last warning.
8892 - Add new "perconnbwrate" and "perconnbwburst" consensus params to
8893 do individual connection-level rate limiting of clients. The torrc
8894 config options with the same names trump the consensus params, if
8895 both are present. Replaces the old "bwconnrate" and "bwconnburst"
8896 consensus params which were broken from 0.2.2.7-alpha through
8897 0.2.2.14-alpha. Closes bug 1947.
8898 - When a router changes IP address or port, authorities now launch
8899 a new reachability test for it. Implements ticket 1899.
8900 - Make the formerly ugly "2 unknown, 7 missing key, 0 good, 0 bad,
8901 2 no signature, 4 required" messages about consensus signatures
8902 easier to read, and make sure they get logged at the same severity
8903 as the messages explaining which keys are which. Fixes bug 1290.
8904 - Don't warn when we have a consensus that we can't verify because
8905 of missing certificates, unless those certificates are ones
8906 that we have been trying and failing to download. Fixes bug 1145.
8907 - If you configure your bridge with a known identity fingerprint,
8908 and the bridge authority is unreachable (as it is in at least
8909 one country now), fall back to directly requesting the descriptor
8910 from the bridge. Finishes the feature started in 0.2.0.10-alpha;
8912 - When building with --enable-gcc-warnings on OpenBSD, disable
8913 warnings in system headers. This makes --enable-gcc-warnings
8914 pass on OpenBSD 4.8.
8916 o Minor bugfixes (on 0.2.1.x and earlier):
8917 - Authorities will now attempt to download consensuses if their
8918 own efforts to make a live consensus have failed. This change
8919 means authorities that restart will fetch a valid consensus, and
8920 it means authorities that didn't agree with the current consensus
8921 will still fetch and serve it if it has enough signatures. Bugfix
8922 on 0.2.0.9-alpha; fixes bug 1300.
8923 - Ensure DNS requests launched by "RESOLVE" commands from the
8924 controller respect the __LeaveStreamsUnattached setconf options. The
8925 same goes for requests launched via DNSPort or transparent
8926 proxying. Bugfix on 0.2.0.1-alpha; fixes bug 1525.
8927 - Allow handshaking OR connections to take a full KeepalivePeriod
8928 seconds to handshake. Previously, we would close them after
8929 IDLE_OR_CONN_TIMEOUT (180) seconds, the same timeout as if they
8930 were open. Bugfix on 0.2.1.26; fixes bug 1840. Thanks to mingw-san
8932 - Rate-limit "Failed to hand off onionskin" warnings.
8933 - Never relay a cell for a circuit we have already destroyed.
8934 Between marking a circuit as closeable and finally closing it,
8935 it may have been possible for a few queued cells to get relayed,
8936 even though they would have been immediately dropped by the next
8937 OR in the circuit. Fixes bug 1184; bugfix on 0.2.0.1-alpha.
8938 - Never queue a cell for a circuit that's already been marked
8940 - Never vote for a server as "Running" if we have a descriptor for
8941 it claiming to be hibernating, and that descriptor was published
8942 more recently than our last contact with the server. Bugfix on
8943 0.2.0.3-alpha; fixes bug 911.
8944 - Squash a compile warning on OpenBSD. Reported by Tas; fixes
8947 o Minor bugfixes (on 0.2.2.x):
8948 - Fix a regression introduced in 0.2.2.7-alpha that marked relays
8949 down if a directory fetch fails and you've configured either
8950 bridges or EntryNodes. The intent was to mark the relay as down
8951 _unless_ you're using bridges or EntryNodes, since if you are
8952 then you could quickly run out of entry points.
8953 - Fix the Windows directory-listing code. A bug introduced in
8954 0.2.2.14-alpha could make Windows directory servers forget to load
8955 some of their cached v2 networkstatus files.
8956 - Really allow clients to use relays as bridges. Fixes bug 1776;
8957 bugfix on 0.2.2.15-alpha.
8958 - Demote a warn to info that happens when the CellStatistics option
8959 was just enabled. Bugfix on 0.2.2.15-alpha; fixes bug 1921.
8960 Reported by Moritz Bartl.
8961 - On Windows, build correctly either with or without Unicode support.
8962 This is necessary so that Tor can support fringe platforms like
8963 Windows 98 (which has no Unicode), or Windows CE (which has no
8964 non-Unicode). Bugfix on 0.2.2.14-alpha; fixes bug 1797.
8967 - Add a unit test for cross-platform directory-listing code.
8970 Changes in version 0.2.2.15-alpha - 2010-08-18
8971 Tor 0.2.2.15-alpha fixes a big bug in hidden service availability,
8972 fixes a variety of other bugs that were preventing performance
8973 experiments from moving forward, fixes several bothersome memory leaks,
8974 and generally closes a lot of smaller bugs that have been filling up
8978 - Stop assigning the HSDir flag to relays that disable their
8979 DirPort (and thus will refuse to answer directory requests). This
8980 fix should dramatically improve the reachability of hidden services:
8981 hidden services and hidden service clients pick six HSDir relays
8982 to store and retrieve the hidden service descriptor, and currently
8983 about half of the HSDir relays will refuse to work. Bugfix on
8984 0.2.0.10-alpha; fixes part of bug 1693.
8985 - The PerConnBWRate and Burst config options, along with the
8986 bwconnrate and bwconnburst consensus params, initialized each conn's
8987 token bucket values only when the connection is established. Now we
8988 update them if the config options change, and update them every time
8989 we get a new consensus. Otherwise we can encounter an ugly edge
8990 case where we initialize an OR conn to client-level bandwidth,
8991 but then later the relay joins the consensus and we leave it
8992 throttled. Bugfix on 0.2.2.7-alpha; fixes bug 1830.
8993 - Fix a regression that caused Tor to rebind its ports if it receives
8994 SIGHUP while hibernating. Bugfix in 0.1.1.6-alpha; closes bug 919.
8997 - Lower the maximum weighted-fractional-uptime cutoff to 98%. This
8998 should give us approximately 40-50% more Guard-flagged nodes,
8999 improving the anonymity the Tor network can provide and also
9000 decreasing the dropoff in throughput that relays experience when
9001 they first get the Guard flag.
9002 - Allow enabling or disabling the *Statistics config options while
9006 - Update to the August 1 2010 Maxmind GeoLite Country database.
9007 - Have the controller interface give a more useful message than
9008 "Internal Error" in response to failed GETINFO requests.
9009 - Warn when the same option is provided more than once in a torrc
9010 file, on the command line, or in a single SETCONF statement, and
9011 the option is one that only accepts a single line. Closes bug 1384.
9012 - Build correctly on mingw with more recent versions of OpenSSL 0.9.8.
9013 Patch from mingw-san.
9014 - Add support for the country code "{??}" in torrc options like
9015 ExcludeNodes, to indicate all routers of unknown country. Closes
9017 - Relays report the number of bytes spent on answering directory
9018 requests in extra-info descriptors similar to {read,write}-history.
9019 Implements enhancement 1790.
9021 o Minor bugfixes (on 0.2.1.x and earlier):
9022 - Complain if PublishServerDescriptor is given multiple arguments that
9023 include 0 or 1. This configuration will be rejected in the future.
9024 Bugfix on 0.2.0.1-alpha; closes bug 1107.
9025 - Disallow BridgeRelay 1 and ORPort 0 at once in the configuration.
9026 Bugfix on 0.2.0.13-alpha; closes bug 928.
9027 - Change "Application request when we're believed to be offline."
9028 notice to "Application request when we haven't used client
9029 functionality lately.", to clarify that it's not an error. Bugfix
9030 on 0.0.9.3; fixes bug 1222.
9031 - Fix a bug in the controller interface where "GETINFO ns/asdaskljkl"
9032 would return "551 Internal error" rather than "552 Unrecognized key
9033 ns/asdaskljkl". Bugfix on 0.1.2.3-alpha.
9034 - Users can't configure a regular relay to be their bridge. It didn't
9035 work because when Tor fetched the bridge descriptor, it found
9036 that it already had it, and didn't realize that the purpose of the
9037 descriptor had changed. Now we replace routers with a purpose other
9038 than bridge with bridge descriptors when fetching them. Bugfix on
9039 0.1.1.9-alpha. Bug 1776 not yet fixed because now we immediately
9040 refetch the descriptor with router purpose 'general', disabling
9042 - Fix a rare bug in rend_fn unit tests: we would fail a test when
9043 a randomly generated port is 0. Diagnosed by Matt Edman. Bugfix
9044 on 0.2.0.10-alpha; fixes bug 1808.
9045 - Exit nodes didn't recognize EHOSTUNREACH as a plausible error code,
9046 and so sent back END_STREAM_REASON_MISC. Clients now recognize a new
9047 stream ending reason for this case: END_STREAM_REASON_NOROUTE.
9048 Servers can start sending this code when enough clients recognize
9049 it. Also update the spec to reflect this new reason. Bugfix on
9050 0.1.0.1-rc; fixes part of bug 1793.
9051 - Delay geoip stats collection by bridges for 6 hours, not 2 hours,
9052 when we switch from being a public relay to a bridge. Otherwise
9053 there will still be clients that see the relay in their consensus,
9054 and the stats will end up wrong. Bugfix on 0.2.1.15-rc; fixes bug
9056 - Instead of giving an assertion failure on an internal mismatch
9057 on estimated freelist size, just log a BUG warning and try later.
9058 Mitigates but does not fix bug 1125.
9059 - Fix an assertion failure that could occur in caches or bridge users
9060 when using a very short voting interval on a testing network.
9061 Diagnosed by Robert Hogan. Fixes bug 1141; bugfix on 0.2.0.8-alpha.
9063 o Minor bugfixes (on 0.2.2.x):
9064 - Alter directory authorities to always consider Exit-flagged nodes
9065 as potential Guard nodes in their votes. The actual decision to
9066 use Exits as Guards is done in the consensus bandwidth weights.
9067 Fixes bug 1294; bugfix on 0.2.2.10-alpha.
9068 - When the controller is reporting the purpose of circuits that
9069 didn't finish building before the circuit build timeout, it was
9070 printing UNKNOWN_13. Now print EXPIRED. Bugfix on 0.2.2.14-alpha.
9071 - Our libevent version parsing code couldn't handle versions like
9072 1.4.14b-stable and incorrectly warned the user about using an
9073 old and broken version of libevent. Treat 1.4.14b-stable like
9074 1.4.14-stable when parsing the version. Fixes bug 1731; bugfix
9076 - Don't use substitution references like $(VAR:MOD) when
9077 $(asciidoc_files) is empty -- make(1) on NetBSD transforms
9078 '$(:x)' to 'x' rather than the empty string. This bites us in
9079 doc/ when configured with --disable-asciidoc. Bugfix on
9080 0.2.2.9-alpha; fixes bug 1773.
9081 - Remove a spurious hidden service server-side log notice about
9082 "Ancient non-dirty circuits". Bugfix on 0.2.2.14-alpha; fixes
9084 - Fix compilation with --with-dmalloc set. Bugfix on 0.2.2.6-alpha;
9086 - Correctly report written bytes on linked connections. Found while
9087 implementing 1790. Bugfix on 0.2.2.4-alpha.
9088 - Fix three memory leaks: one in circuit_build_times_parse_state(),
9089 one in dirvote_add_signatures_to_pending_consensus(), and one every
9090 time we parse a v3 network consensus. Bugfixes on 0.2.2.14-alpha,
9091 0.2.2.6-alpha, and 0.2.2.10-alpha respectively; fixes bug 1831.
9093 o Code simplifications and refactoring:
9094 - Take a first step towards making or.h smaller by splitting out
9095 function definitions for all source files in src/or/. Leave
9096 structures and defines in or.h for now.
9097 - Remove a bunch of unused function declarations as well as a block of
9098 #if 0'd code from the unit tests. Closes bug 1824.
9099 - New unit tests for exit-port history statistics; refactored exit
9100 statistics code to be more easily tested.
9101 - Remove the old debian/ directory from the main Tor distribution.
9102 The official Tor-for-debian git repository lives at the URL
9103 https://git.torproject.org/debian/tor.git
9106 Changes in version 0.2.2.14-alpha - 2010-07-12
9107 Tor 0.2.2.14-alpha greatly improves client-side handling of
9108 circuit build timeouts, which are used to estimate speed and improve
9109 performance. We also move to a much better GeoIP database, port Tor to
9110 Windows CE, introduce new compile flags that improve code security,
9111 add an eighth v3 directory authority, and address a lot of more
9115 - Tor directory authorities no longer crash when started with a
9116 cached-microdesc-consensus file in their data directory. Bugfix
9117 on 0.2.2.6-alpha; fixes bug 1532.
9118 - Treat an unset $HOME like an empty $HOME rather than triggering an
9119 assert. Bugfix on 0.0.8pre1; fixes bug 1522.
9120 - Ignore negative and large circuit build timeout values that can
9121 happen during a suspend or hibernate. These values caused various
9122 asserts to fire. Bugfix on 0.2.2.2-alpha; fixes bug 1245.
9123 - Alter calculation of Pareto distribution parameter 'Xm' for
9124 Circuit Build Timeout learning to use the weighted average of the
9125 top N=3 modes (because we have three entry guards). Considering
9126 multiple modes should improve the timeout calculation in some cases,
9127 and prevent extremely high timeout values. Bugfix on 0.2.2.2-alpha;
9129 - Alter calculation of Pareto distribution parameter 'Alpha' to use a
9130 right censored distribution model. This approach improves over the
9131 synthetic timeout generation approach that was producing insanely
9132 high timeout values. Now we calculate build timeouts using truncated
9133 times. Bugfix on 0.2.2.2-alpha; fixes bugs 1245 and 1335.
9134 - Do not close circuits that are under construction when they reach
9135 the circuit build timeout. Instead, leave them building (but do not
9136 use them) for up until the time corresponding to the 95th percentile
9137 on the Pareto CDF or 60 seconds, whichever is greater. This is done
9138 to provide better data for the new Pareto model. This percentile
9139 can be controlled by the consensus.
9142 - Move to the June 2010 Maxmind GeoLite country db (rather than the
9143 June 2009 ip-to-country GeoIP db) for our statistics that count
9144 how many users relays are seeing from each country. Now we have
9145 more accurate data for many African countries.
9146 - Port Tor to build and run correctly on Windows CE systems, using
9147 the wcecompat library. Contributed by Valerio Lupi.
9148 - New "--enable-gcc-hardening" ./configure flag (off by default)
9149 to turn on gcc compile time hardening options. It ensures
9150 that signed ints have defined behavior (-fwrapv), enables
9151 -D_FORTIFY_SOURCE=2 (requiring -O2), adds stack smashing protection
9152 with canaries (-fstack-protector-all), turns on ASLR protection if
9153 supported by the kernel (-fPIE, -pie), and adds additional security
9154 related warnings. Verified to work on Mac OS X and Debian Lenny.
9155 - New "--enable-linker-hardening" ./configure flag (off by default)
9156 to turn on ELF specific hardening features (relro, now). This does
9157 not work with Mac OS X or any other non-ELF binary format.
9159 o New directory authorities:
9160 - Set up maatuska (run by Linus Nordberg) as the eighth v3 directory
9164 - New config option "WarnUnsafeSocks 0" disables the warning that
9165 occurs whenever Tor receives a socks handshake using a version of
9166 the socks protocol that can only provide an IP address (rather
9167 than a hostname). Setups that do DNS locally over Tor are fine,
9168 and we shouldn't spam the logs in that case.
9169 - Convert the HACKING file to asciidoc, and add a few new sections
9170 to it, explaining how we use Git, how we make changelogs, and
9171 what should go in a patch.
9172 - Add a TIMEOUT_RATE keyword to the BUILDTIMEOUT_SET control port
9173 event, to give information on the current rate of circuit timeouts
9174 over our stored history.
9175 - Add ability to disable circuit build time learning via consensus
9176 parameter and via a LearnCircuitBuildTimeout config option. Also
9177 automatically disable circuit build time calculation if we are
9178 either a AuthoritativeDirectory, or if we fail to write our state
9179 file. Fixes bug 1296.
9180 - More gracefully handle corrupt state files, removing asserts
9181 in favor of saving a backup and resetting state.
9182 - Rename the "log.h" header to "torlog.h" so as to conflict with fewer
9186 - Build correctly on OSX with zlib 1.2.4 and higher with all warnings
9188 - When a2x fails, mention that the user could disable manpages instead
9189 of trying to fix their asciidoc installation.
9190 - Where available, use Libevent 2.0's periodic timers so that our
9191 once-per-second cleanup code gets called even more closely to
9192 once per second than it would otherwise. Fixes bug 943.
9193 - If you run a bridge that listens on multiple IP addresses, and
9194 some user configures a bridge address that uses a different IP
9195 address than your bridge writes in its router descriptor, and the
9196 user doesn't specify an identity key, their Tor would discard the
9197 descriptor because "it isn't one of our configured bridges", and
9198 fail to bootstrap. Now believe the descriptor and bootstrap anyway.
9199 Bugfix on 0.2.0.3-alpha.
9200 - If OpenSSL fails to make a duplicate of a private or public key, log
9201 an error message and try to exit cleanly. May help with debugging
9202 if bug 1209 ever remanifests.
9203 - Save a couple bytes in memory allocation every time we escape
9204 certain characters in a string. Patch from Florian Zumbiehl.
9205 - Make it explicit that we don't cannibalize one-hop circuits. This
9206 happens in the wild, but doesn't turn out to be a problem because
9207 we fortunately don't use those circuits. Many thanks to outofwords
9208 for the initial analysis and to swissknife who confirmed that
9209 two-hop circuits are actually created.
9210 - Make directory mirrors report non-zero dirreq-v[23]-shares again.
9211 Fixes bug 1564; bugfix on 0.2.2.9-alpha.
9212 - Eliminate a case where a circuit build time warning was displayed
9213 after network connectivity resumed. Bugfix on 0.2.2.2-alpha.
9216 Changes in version 0.2.1.26 - 2010-05-02
9217 Tor 0.2.1.26 addresses the recent connection and memory overload
9218 problems we've been seeing on relays, especially relays with their
9219 DirPort open. If your relay has been crashing, or you turned it off
9220 because it used too many resources, give this release a try.
9222 This release also fixes yet another instance of broken OpenSSL libraries
9223 that was causing some relays to drop out of the consensus.
9226 - Teach relays to defend themselves from connection overload. Relays
9227 now close idle circuits early if it looks like they were intended
9228 for directory fetches. Relays are also more aggressive about closing
9229 TLS connections that have no circuits on them. Such circuits are
9230 unlikely to be re-used, and tens of thousands of them were piling
9231 up at the fast relays, causing the relays to run out of sockets
9232 and memory. Bugfix on 0.2.0.22-rc (where clients started tunneling
9233 their directory fetches over TLS).
9234 - Fix SSL renegotiation behavior on OpenSSL versions like on Centos
9235 that claim to be earlier than 0.9.8m, but which have in reality
9236 backported huge swaths of 0.9.8m or 0.9.8n renegotiation
9237 behavior. Possible fix for some cases of bug 1346.
9238 - Directory mirrors were fetching relay descriptors only from v2
9239 directory authorities, rather than v3 authorities like they should.
9240 Only 2 v2 authorities remain (compared to 7 v3 authorities), leading
9241 to a serious bottleneck. Bugfix on 0.2.0.9-alpha. Fixes bug 1324.
9244 - Finally get rid of the deprecated and now harmful notion of "clique
9245 mode", where directory authorities maintain TLS connections to
9249 - In the util/threads test, no longer free the test_mutex before all
9250 worker threads have finished. Bugfix on 0.2.1.6-alpha.
9251 - The master thread could starve the worker threads quite badly on
9252 certain systems, causing them to run only partially in the allowed
9253 window. This resulted in test failures. Now the master thread sleeps
9254 occasionally for a few microseconds while the two worker-threads
9255 compete for the mutex. Bugfix on 0.2.0.1-alpha.
9258 Changes in version 0.2.2.13-alpha - 2010-04-24
9259 Tor 0.2.2.13-alpha addresses the recent connection and memory overload
9260 problems we've been seeing on relays, especially relays with their
9261 DirPort open. If your relay has been crashing, or you turned it off
9262 because it used too many resources, give this release a try.
9265 - Teach relays to defend themselves from connection overload. Relays
9266 now close idle circuits early if it looks like they were intended
9267 for directory fetches. Relays are also more aggressive about closing
9268 TLS connections that have no circuits on them. Such circuits are
9269 unlikely to be re-used, and tens of thousands of them were piling
9270 up at the fast relays, causing the relays to run out of sockets
9271 and memory. Bugfix on 0.2.0.22-rc (where clients started tunneling
9272 their directory fetches over TLS).
9275 - Finally get rid of the deprecated and now harmful notion of "clique
9276 mode", where directory authorities maintain TLS connections to
9278 - Directory authorities now do an immediate reachability check as soon
9279 as they hear about a new relay. This change should slightly reduce
9280 the time between setting up a relay and getting listed as running
9281 in the consensus. It should also improve the time between setting
9282 up a bridge and seeing use by bridge users.
9283 - Directory authorities no longer launch a TLS connection to every
9284 relay as they startup. Now that we have 2k+ descriptors cached,
9285 the resulting network hiccup is becoming a burden. Besides,
9286 authorities already avoid voting about Running for the first half
9287 hour of their uptime.
9290 Changes in version 0.2.2.12-alpha - 2010-04-20
9291 Tor 0.2.2.12-alpha fixes a critical bug in how directory authorities
9292 handle and vote on descriptors. It was causing relays to drop out of
9296 - Many relays have been falling out of the consensus lately because
9297 not enough authorities know about their descriptor for them to get
9298 a majority of votes. When we deprecated the v2 directory protocol,
9299 we got rid of the only way that v3 authorities can hear from each
9300 other about other descriptors. Now authorities examine every v3
9301 vote for new descriptors, and fetch them from that authority. Bugfix
9303 - Fix two typos in tor_vasprintf() that broke the compile on Windows,
9304 and a warning in or.h related to bandwidth_weight_rule_t that
9305 prevented clean compile on OS X. Fixes bug 1363; bugfix on
9307 - Fix a segfault on relays when DirReqStatistics is enabled
9308 and 24 hours pass. Bug found by keb. Fixes bug 1365; bugfix on
9312 - Demote a confusing TLS warning that relay operators might get when
9313 someone tries to talk to their OrPort. It is neither the operator's
9314 fault nor can they do anything about it. Fixes bug 1364; bugfix
9318 Changes in version 0.2.2.11-alpha - 2010-04-15
9319 Tor 0.2.2.11-alpha fixes yet another instance of broken OpenSSL
9320 libraries that was causing some relays to drop out of the consensus.
9323 - Directory mirrors were fetching relay descriptors only from v2
9324 directory authorities, rather than v3 authorities like they should.
9325 Only 2 v2 authorities remain (compared to 7 v3 authorities), leading
9326 to a serious bottleneck. Bugfix on 0.2.0.9-alpha. Fixes bug 1324.
9327 - Fix a parsing error that made every possible value of
9328 CircPriorityHalflifeMsec get treated as "1 msec". Bugfix
9329 on 0.2.2.7-alpha. Rename CircPriorityHalflifeMsec to
9330 CircuitPriorityHalflifeMsec, so authorities can tell newer relays
9331 about the option without breaking older ones.
9332 - Fix SSL renegotiation behavior on OpenSSL versions like on Centos
9333 that claim to be earlier than 0.9.8m, but which have in reality
9334 backported huge swaths of 0.9.8m or 0.9.8n renegotiation
9335 behavior. Possible fix for some cases of bug 1346.
9338 - Experiment with a more aggressive approach to preventing clients
9339 from making one-hop exit streams. Exit relays who want to try it
9340 out can set "RefuseUnknownExits 1" in their torrc, and then look
9341 for "Attempt by %s to open a stream" log messages. Let us know
9343 - Add support for statically linking zlib by specifying
9344 --enable-static-zlib, to go with our support for statically linking
9345 openssl and libevent. Resolves bug 1358.
9348 - Fix a segfault that happens whenever a Tor client that is using
9349 libevent2's bufferevents gets a hup signal. Bugfix on 0.2.2.5-alpha;
9351 - When we cleaned up the contrib/tor-exit-notice.html file, we left
9352 out the first line. Fixes bug 1295.
9353 - When building the manpage from a tarball, we required asciidoc, but
9354 the asciidoc -> roff/html conversion was already done for the
9355 tarball. Make 'make' complain only when we need asciidoc (either
9356 because we're compiling directly from git, or because we altered
9357 the asciidoc manpage in the tarball). Bugfix on 0.2.2.9-alpha.
9358 - When none of the directory authorities vote on any params, Tor
9359 segfaulted when trying to make the consensus from the votes. We
9360 didn't trigger the bug in practice, because authorities do include
9361 params in their votes. Bugfix on 0.2.2.10-alpha; fixes bug 1322.
9364 - In the util/threads test, no longer free the test_mutex before all
9365 worker threads have finished. Bugfix on 0.2.1.6-alpha.
9366 - The master thread could starve the worker threads quite badly on
9367 certain systems, causing them to run only partially in the allowed
9368 window. This resulted in test failures. Now the master thread sleeps
9369 occasionally for a few microseconds while the two worker-threads
9370 compete for the mutex. Bugfix on 0.2.0.1-alpha.
9373 Changes in version 0.2.2.10-alpha - 2010-03-07
9374 Tor 0.2.2.10-alpha fixes a regression introduced in 0.2.2.9-alpha that
9375 could prevent relays from guessing their IP address correctly. It also
9376 starts the groundwork for another client-side performance boost, since
9377 currently we're not making efficient use of relays that have both the
9378 Guard flag and the Exit flag.
9381 - Fix a regression from our patch for bug 1244 that caused relays
9382 to guess their IP address incorrectly if they didn't set Address
9383 in their torrc and/or their address fails to resolve. Bugfix on
9384 0.2.2.9-alpha; fixes bug 1269.
9386 o Major features (performance):
9387 - Directory authorities now compute consensus weightings that instruct
9388 clients how to weight relays flagged as Guard, Exit, Guard+Exit,
9389 and no flag. Clients that use these weightings will distribute
9390 network load more evenly across these different relay types. The
9391 weightings are in the consensus so we can change them globally in
9392 the future. Extra thanks to "outofwords" for finding some nasty
9393 security bugs in the first implementation of this feature.
9395 o Minor features (performance):
9396 - Always perform router selections using weighted relay bandwidth,
9397 even if we don't need a high capacity circuit at the time. Non-fast
9398 circuits now only differ from fast ones in that they can use relays
9399 not marked with the Fast flag. This "feature" could turn out to
9400 be a horrible bug; we should investigate more before it goes into
9404 - Allow disabling building of the manpages. Skipping the manpage
9405 speeds up the build considerably.
9407 o Minor bugfixes (on 0.2.2.x):
9408 - Fix a memleak in the EXTENDCIRCUIT logic. Spotted by coverity.
9409 Bugfix on 0.2.2.9-alpha.
9410 - Disallow values larger than INT32_MAX for PerConnBWRate|Burst
9411 config option. Bugfix on 0.2.2.7-alpha.
9412 - Ship the asciidoc-helper file in the tarball, so that people can
9413 build from source if they want to, and touching the .1.txt files
9414 doesn't break the build. Bugfix on 0.2.2.9-alpha.
9416 o Minor bugfixes (on 0.2.1.x or earlier):
9417 - Fix a dereference-then-NULL-check sequence when publishing
9418 descriptors. Bugfix on 0.2.1.5-alpha. Discovered by ekir; fixes
9420 - Fix another dereference-then-NULL-check sequence. Bugfix on
9421 0.2.1.14-rc. Discovered by ekir; fixes bug 1256.
9422 - Make sure we treat potentially not NUL-terminated strings correctly.
9423 Bugfix on 0.1.1.13-alpha. Discovered by rieo; fixes bug 1257.
9425 o Code simplifications and refactoring:
9426 - Fix some urls in the exit notice file and make it XHTML1.1 strict
9427 compliant. Based on a patch from Christian Kujau.
9428 - Don't use sed in asciidoc-helper anymore.
9429 - Make the build process fail if asciidoc cannot be found and
9430 building with asciidoc isn't disabled.
9433 Changes in version 0.2.2.9-alpha - 2010-02-22
9434 Tor 0.2.2.9-alpha makes Tor work again on the latest OS X, updates the
9435 location of a directory authority, and cleans up a bunch of small bugs.
9437 o Directory authority changes:
9438 - Change IP address for dannenberg (v3 directory authority), and
9439 remove moria2 (obsolete v1, v2 directory authority and v0 hidden
9440 service directory authority) from the list.
9443 - Make Tor work again on the latest OS X: when deciding whether to
9444 use strange flags to turn TLS renegotiation on, detect the OpenSSL
9445 version at run-time, not compile time. We need to do this because
9446 Apple doesn't update its dev-tools headers when it updates its
9447 libraries in a security patch.
9448 - Fix a potential buffer overflow in lookup_last_hid_serv_request()
9449 that could happen on 32-bit platforms with 64-bit time_t. Also fix
9450 a memory leak when requesting a hidden service descriptor we've
9451 requested before. Fixes bug 1242, bugfix on 0.2.0.18-alpha. Found
9453 - Authorities could be tricked into giving out the Exit flag to relays
9454 that didn't allow exiting to any ports. This bug could screw
9455 with load balancing and stats. Bugfix on 0.1.1.6-alpha; fixes bug
9456 1238. Bug discovered by Martin Kowalczyk.
9457 - When freeing a session key, zero it out completely. We only zeroed
9458 the first ptrsize bytes. Bugfix on 0.0.2pre8. Discovered and
9459 patched by ekir. Fixes bug 1254.
9462 - Fix static compilation by listing the openssl libraries in the right
9463 order. Bugfix on Tor 0.2.2.8-alpha; fixes bug 1237.
9464 - Resume handling .exit hostnames in a special way: originally we
9465 stripped the .exit part and used the requested exit relay. In
9466 0.2.2.1-alpha we stopped treating them in any special way, meaning
9467 if you use a .exit address then Tor will pass it on to the exit
9468 relay. Now we reject the .exit stream outright, since that behavior
9469 might be more expected by the user. Found and diagnosed by Scott
9470 Bennett and Downie on or-talk.
9471 - Don't spam the controller with events when we have no file
9472 descriptors available. Bugfix on 0.2.1.5-alpha. (Rate-limiting
9473 for log messages was already solved from bug 748.)
9474 - Avoid a bogus overlapped memcpy in tor_addr_copy(). Reported by
9476 - Make the DNSPort option work with libevent 2.x. Don't alter the
9477 behaviour for libevent 1.x. Fixes bug 1143. Found by SwissTorExit.
9478 - Emit a GUARD DROPPED controller event for a case we missed.
9479 - Make more fields in the controller protocol case-insensitive, since
9480 control-spec.txt said they were.
9481 - Refactor resolve_my_address() to not use gethostbyname() anymore.
9482 Fixes bug 1244; bugfix on 0.0.2pre25. Reported by Mike Mestnik.
9483 - Fix a spec conformance issue: the network-status-version token
9484 must be the first token in a v3 consensus or vote. Discovered by
9485 parakeep. Bugfix on 0.2.0.3-alpha.
9487 o Code simplifications and refactoring:
9488 - Generate our manpage and HTML documentation using Asciidoc. This
9489 change should make it easier to maintain the documentation, and
9491 - Remove the --enable-iphone option. According to reports from Marco
9492 Bonetti, Tor builds fine without any special tweaking on recent
9493 iPhone SDK versions.
9494 - Removed some unnecessary files from the source distribution. The
9495 AUTHORS file has now been merged into the people page on the
9496 website. The roadmaps and design doc can now be found in the
9497 projects directory in svn.
9498 - Enabled various circuit build timeout constants to be controlled
9499 by consensus parameters. Also set better defaults for these
9500 parameters based on experimentation on broadband and simulated
9504 - The 'EXTENDCIRCUIT' control port command can now be used with
9505 a circ id of 0 and no path. This feature will cause Tor to build
9506 a new 'fast' general purpose circuit using its own path selection
9508 - Added a BUILDTIMEOUT_SET controller event to describe changes
9509 to the circuit build timeout.
9510 - Future-proof the controller protocol a bit by ignoring keyword
9511 arguments we do not recognize.
9512 - Expand homedirs passed to tor-checkkey. This should silence a
9513 coverity complaint about passing a user-supplied string into
9514 open() without checking it.
9517 Changes in version 0.2.1.25 - 2010-03-16
9518 Tor 0.2.1.25 fixes a regression introduced in 0.2.1.23 that could
9519 prevent relays from guessing their IP address correctly. It also fixes
9520 several minor potential security bugs.
9523 - Fix a regression from our patch for bug 1244 that caused relays
9524 to guess their IP address incorrectly if they didn't set Address
9525 in their torrc and/or their address fails to resolve. Bugfix on
9526 0.2.1.23; fixes bug 1269.
9527 - When freeing a session key, zero it out completely. We only zeroed
9528 the first ptrsize bytes. Bugfix on 0.0.2pre8. Discovered and
9529 patched by ekir. Fixes bug 1254.
9532 - Fix a dereference-then-NULL-check sequence when publishing
9533 descriptors. Bugfix on 0.2.1.5-alpha. Discovered by ekir; fixes
9535 - Fix another dereference-then-NULL-check sequence. Bugfix on
9536 0.2.1.14-rc. Discovered by ekir; fixes bug 1256.
9537 - Make sure we treat potentially not NUL-terminated strings correctly.
9538 Bugfix on 0.1.1.13-alpha. Discovered by rieo; fixes bug 1257.
9542 Changes in version 0.2.1.24 - 2010-02-21
9543 Tor 0.2.1.24 makes Tor work again on the latest OS X -- this time
9547 - Work correctly out-of-the-box with even more vendor-patched versions
9548 of OpenSSL. In particular, make it so Debian and OS X don't need
9549 customized patches to run/build.
9552 Changes in version 0.2.1.23 - 2010-02-13
9553 Tor 0.2.1.23 fixes a huge client-side performance bug, makes Tor work
9554 again on the latest OS X, and updates the location of a directory
9557 o Major bugfixes (performance):
9558 - We were selecting our guards uniformly at random, and then weighting
9559 which of our guards we'd use uniformly at random. This imbalance
9560 meant that Tor clients were severely limited on throughput (and
9561 probably latency too) by the first hop in their circuit. Now we
9562 select guards weighted by currently advertised bandwidth. We also
9563 automatically discard guards picked using the old algorithm. Fixes
9564 bug 1217; bugfix on 0.2.1.3-alpha. Found by Mike Perry.
9567 - Make Tor work again on the latest OS X: when deciding whether to
9568 use strange flags to turn TLS renegotiation on, detect the OpenSSL
9569 version at run-time, not compile time. We need to do this because
9570 Apple doesn't update its dev-tools headers when it updates its
9571 libraries in a security patch.
9572 - Fix a potential buffer overflow in lookup_last_hid_serv_request()
9573 that could happen on 32-bit platforms with 64-bit time_t. Also fix
9574 a memory leak when requesting a hidden service descriptor we've
9575 requested before. Fixes bug 1242, bugfix on 0.2.0.18-alpha. Found
9578 o Directory authority changes:
9579 - Change IP address for dannenberg (v3 directory authority), and
9580 remove moria2 (obsolete v1, v2 directory authority and v0 hidden
9581 service directory authority) from the list.
9584 - Refactor resolve_my_address() to not use gethostbyname() anymore.
9585 Fixes bug 1244; bugfix on 0.0.2pre25. Reported by Mike Mestnik.
9588 - Avoid a mad rush at the beginning of each month when each client
9589 rotates half of its guards. Instead we spread the rotation out
9590 throughout the month, but we still avoid leaving a precise timestamp
9591 in the state file about when we first picked the guard. Improves
9592 over the behavior introduced in 0.1.2.17.
9595 Changes in version 0.2.2.8-alpha - 2010-01-26
9596 Tor 0.2.2.8-alpha fixes a crash bug in 0.2.2.7-alpha that has been
9597 causing bridge relays to disappear. If you're running a bridge,
9601 - Fix a memory corruption bug on bridges that occured during the
9602 inclusion of stats data in extra-info descriptors. Also fix the
9603 interface for geoip_get_bridge_stats* to prevent similar bugs in
9604 the future. Diagnosis by Tas, patch by Karsten and Sebastian.
9605 Fixes bug 1208; bugfix on 0.2.2.7-alpha.
9608 - Ignore OutboundBindAddress when connecting to localhost.
9609 Connections to localhost need to come _from_ localhost, or else
9610 local servers (like DNS and outgoing HTTP/SOCKS proxies) will often
9614 Changes in version 0.2.2.7-alpha - 2010-01-19
9615 Tor 0.2.2.7-alpha fixes a huge client-side performance bug, as well
9616 as laying the groundwork for further relay-side performance fixes. It
9617 also starts cleaning up client behavior with respect to the EntryNodes,
9618 ExitNodes, and StrictNodes config options.
9620 This release also rotates two directory authority keys, due to a
9621 security breach of some of the Torproject servers.
9623 o Directory authority changes:
9624 - Rotate keys (both v3 identity and relay identity) for moria1
9627 o Major features (performance):
9628 - We were selecting our guards uniformly at random, and then weighting
9629 which of our guards we'd use uniformly at random. This imbalance
9630 meant that Tor clients were severely limited on throughput (and
9631 probably latency too) by the first hop in their circuit. Now we
9632 select guards weighted by currently advertised bandwidth. We also
9633 automatically discard guards picked using the old algorithm. Fixes
9634 bug 1217; bugfix on 0.2.1.3-alpha. Found by Mike Perry.
9635 - When choosing which cells to relay first, relays can now favor
9636 circuits that have been quiet recently, to provide lower latency
9637 for low-volume circuits. By default, relays enable or disable this
9638 feature based on a setting in the consensus. You can override
9639 this default by using the new "CircuitPriorityHalflife" config
9640 option. Design and code by Ian Goldberg, Can Tang, and Chris
9642 - Add separate per-conn write limiting to go with the per-conn read
9643 limiting. We added a global write limit in Tor 0.1.2.5-alpha,
9644 but never per-conn write limits.
9645 - New consensus params "bwconnrate" and "bwconnburst" to let us
9646 rate-limit client connections as they enter the network. It's
9647 controlled in the consensus so we can turn it on and off for
9648 experiments. It's starting out off. Based on proposal 163.
9650 o Major features (relay selection options):
9651 - Switch to a StrictNodes config option, rather than the previous
9652 "StrictEntryNodes" / "StrictExitNodes" separation that was missing a
9653 "StrictExcludeNodes" option.
9654 - If EntryNodes, ExitNodes, ExcludeNodes, or ExcludeExitNodes
9655 change during a config reload, mark and discard all our origin
9656 circuits. This fix should address edge cases where we change the
9657 config options and but then choose a circuit that we created before
9659 - If EntryNodes or ExitNodes are set, be more willing to use an
9660 unsuitable (e.g. slow or unstable) circuit. The user asked for it,
9662 - Make EntryNodes config option much more aggressive even when
9663 StrictNodes is not set. Before it would prepend your requested
9664 entrynodes to your list of guard nodes, but feel free to use others
9665 after that. Now it chooses only from your EntryNodes if any of
9666 those are available, and only falls back to others if a) they're
9667 all down and b) StrictNodes is not set.
9668 - Now we refresh your entry guards from EntryNodes at each consensus
9669 fetch -- rather than just at startup and then they slowly rot as
9670 the network changes.
9673 - Stop bridge directory authorities from answering dbg-stability.txt
9674 directory queries, which would let people fetch a list of all
9675 bridge identities they track. Bugfix on 0.2.1.6-alpha.
9678 - Log a notice when we get a new control connection. Now it's easier
9679 for security-conscious users to recognize when a local application
9680 is knocking on their controller door. Suggested by bug 1196.
9681 - New config option "CircuitStreamTimeout" to override our internal
9682 timeout schedule for how many seconds until we detach a stream from
9683 a circuit and try a new circuit. If your network is particularly
9684 slow, you might want to set this to a number like 60.
9685 - New controller command "getinfo config-text". It returns the
9686 contents that Tor would write if you send it a SAVECONF command,
9687 so the controller can write the file to disk itself.
9688 - New options for SafeLogging to allow scrubbing only log messages
9689 generated while acting as a relay.
9690 - Ship the bridges spec file in the tarball too.
9691 - Avoid a mad rush at the beginning of each month when each client
9692 rotates half of its guards. Instead we spread the rotation out
9693 throughout the month, but we still avoid leaving a precise timestamp
9694 in the state file about when we first picked the guard. Improves
9695 over the behavior introduced in 0.1.2.17.
9697 o Minor bugfixes (compiling):
9698 - Fix compilation on OS X 10.3, which has a stub mlockall() but
9699 hides it. Bugfix on 0.2.2.6-alpha.
9700 - Fix compilation on Solaris by removing support for the
9701 DisableAllSwap config option. Solaris doesn't have an rlimit for
9702 mlockall, so we cannot use it safely. Fixes bug 1198; bugfix on
9705 o Minor bugfixes (crashes):
9706 - Do not segfault when writing buffer stats when we haven't observed
9707 a single circuit to report about. Found by Fabian Lanze. Bugfix on
9709 - If we're in the pathological case where there's no exit bandwidth
9710 but there is non-exit bandwidth, or no guard bandwidth but there
9711 is non-guard bandwidth, don't crash during path selection. Bugfix
9713 - Fix an impossible-to-actually-trigger buffer overflow in relay
9714 descriptor generation. Bugfix on 0.1.0.15.
9716 o Minor bugfixes (privacy):
9717 - Fix an instance where a Tor directory mirror might accidentally
9718 log the IP address of a misbehaving Tor client. Bugfix on
9720 - Don't list Windows capabilities in relay descriptors. We never made
9721 use of them, and maybe it's a bad idea to publish them. Bugfix
9724 o Minor bugfixes (other):
9725 - Resolve an edge case in path weighting that could make us misweight
9726 our relay selection. Fixes bug 1203; bugfix on 0.0.8rc1.
9727 - Fix statistics on client numbers by country as seen by bridges that
9728 were broken in 0.2.2.1-alpha. Also switch to reporting full 24-hour
9729 intervals instead of variable 12-to-48-hour intervals.
9730 - After we free an internal connection structure, overwrite it
9731 with a different memory value than we use for overwriting a freed
9732 internal circuit structure. Should help with debugging. Suggested
9734 - Update our OpenSSL 0.9.8l fix so that it works with OpenSSL 0.9.8m
9738 - Remove the HSAuthorityRecordStats option that version 0 hidden
9739 service authorities could have used to track statistics of overall
9740 hidden service usage.
9743 Changes in version 0.2.1.22 - 2010-01-19
9744 Tor 0.2.1.22 fixes a critical privacy problem in bridge directory
9745 authorities -- it would tell you its whole history of bridge descriptors
9746 if you make the right directory request. This stable update also
9747 rotates two of the seven v3 directory authority keys and locations.
9749 o Directory authority changes:
9750 - Rotate keys (both v3 identity and relay identity) for moria1
9754 - Stop bridge directory authorities from answering dbg-stability.txt
9755 directory queries, which would let people fetch a list of all
9756 bridge identities they track. Bugfix on 0.2.1.6-alpha.
9759 Changes in version 0.2.1.21 - 2009-12-21
9760 Tor 0.2.1.21 fixes an incompatibility with the most recent OpenSSL
9761 library. If you use Tor on Linux / Unix and you're getting SSL
9762 renegotiation errors, upgrading should help. We also recommend an
9763 upgrade if you're an exit relay.
9766 - Work around a security feature in OpenSSL 0.9.8l that prevents our
9767 handshake from working unless we explicitly tell OpenSSL that we
9768 are using SSL renegotiation safely. We are, of course, but OpenSSL
9769 0.9.8l won't work unless we say we are.
9770 - Avoid crashing if the client is trying to upload many bytes and the
9771 circuit gets torn down at the same time, or if the flip side
9772 happens on the exit relay. Bugfix on 0.2.0.1-alpha; fixes bug 1150.
9775 - Do not refuse to learn about authority certs and v2 networkstatus
9776 documents that are older than the latest consensus. This bug might
9777 have degraded client bootstrapping. Bugfix on 0.2.0.10-alpha.
9778 Spotted and fixed by xmux.
9779 - Fix a couple of very-hard-to-trigger memory leaks, and one hard-to-
9780 trigger platform-specific option misparsing case found by Coverity
9782 - Fix a compilation warning on Fedora 12 by removing an impossible-to-
9783 trigger assert. Fixes bug 1173.
9786 Changes in version 0.2.2.6-alpha - 2009-11-19
9787 Tor 0.2.2.6-alpha lays the groundwork for many upcoming features:
9788 support for the new lower-footprint "microdescriptor" directory design,
9789 future-proofing our consensus format against new hash functions or
9790 other changes, and an Android port. It also makes Tor compatible with
9791 the upcoming OpenSSL 0.9.8l release, and fixes a variety of bugs.
9794 - Directory authorities can now create, vote on, and serve multiple
9795 parallel formats of directory data as part of their voting process.
9796 Partially implements Proposal 162: "Publish the consensus in
9798 - Directory authorities can now agree on and publish small summaries
9799 of router information that clients can use in place of regular
9800 server descriptors. This transition will eventually allow clients
9801 to use far less bandwidth for downloading information about the
9802 network. Begins the implementation of Proposal 158: "Clients
9803 download consensus + microdescriptors".
9804 - The directory voting system is now extensible to use multiple hash
9805 algorithms for signatures and resource selection. Newer formats
9806 are signed with SHA256, with a possibility for moving to a better
9807 hash algorithm in the future.
9808 - New DisableAllSwap option. If set to 1, Tor will attempt to lock all
9809 current and future memory pages via mlockall(). On supported
9810 platforms (modern Linux and probably BSD but not Windows or OS X),
9811 this should effectively disable any and all attempts to page out
9812 memory. This option requires that you start your Tor as root --
9813 if you use DisableAllSwap, please consider using the User option
9814 to properly reduce the privileges of your Tor.
9815 - Numerous changes, bugfixes, and workarounds from Nathan Freitas
9816 to help Tor build correctly for Android phones.
9819 - Work around a security feature in OpenSSL 0.9.8l that prevents our
9820 handshake from working unless we explicitly tell OpenSSL that we
9821 are using SSL renegotiation safely. We are, but OpenSSL 0.9.8l
9822 won't work unless we say we are.
9825 - Fix a crash bug when trying to initialize the evdns module in
9826 Libevent 2. Bugfix on 0.2.1.16-rc.
9827 - Stop logging at severity 'warn' when some other Tor client tries
9828 to establish a circuit with us using weak DH keys. It's a protocol
9829 violation, but that doesn't mean ordinary users need to hear about
9830 it. Fixes the bug part of bug 1114. Bugfix on 0.1.0.13.
9831 - Do not refuse to learn about authority certs and v2 networkstatus
9832 documents that are older than the latest consensus. This bug might
9833 have degraded client bootstrapping. Bugfix on 0.2.0.10-alpha.
9834 Spotted and fixed by xmux.
9835 - Fix numerous small code-flaws found by Coverity Scan Rung 3.
9836 - If all authorities restart at once right before a consensus vote,
9837 nobody will vote about "Running", and clients will get a consensus
9838 with no usable relays. Instead, authorities refuse to build a
9839 consensus if this happens. Bugfix on 0.2.0.10-alpha; fixes bug 1066.
9840 - If your relay can't keep up with the number of incoming create
9841 cells, it would log one warning per failure into your logs. Limit
9842 warnings to 1 per minute. Bugfix on 0.0.2pre10; fixes bug 1042.
9843 - Bridges now use "reject *:*" as their default exit policy. Bugfix
9844 on 0.2.0.3-alpha; fixes bug 1113.
9845 - Fix a memory leak on directory authorities during voting that was
9846 introduced in 0.2.2.1-alpha. Found via valgrind.
9849 Changes in version 0.2.1.20 - 2009-10-15
9850 Tor 0.2.1.20 fixes a crash bug when you're accessing many hidden
9851 services at once, prepares for more performance improvements, and
9852 fixes a bunch of smaller bugs.
9854 The Windows and OS X bundles also include a more recent Vidalia,
9855 and switch from Privoxy to Polipo.
9857 The OS X installers are now drag and drop. It's best to un-install
9858 Tor/Vidalia and then install this new bundle, rather than upgrade. If
9859 you want to upgrade, you'll need to update the paths for Tor and Polipo
9860 in the Vidalia Settings window.
9863 - Send circuit or stream sendme cells when our window has decreased
9864 by 100 cells, not when it has decreased by 101 cells. Bug uncovered
9865 by Karsten when testing the "reduce circuit window" performance
9866 patch. Bugfix on the 54th commit on Tor -- from July 2002,
9867 before the release of Tor 0.0.0. This is the new winner of the
9869 - Fix a remotely triggerable memory leak when a consensus document
9870 contains more than one signature from the same voter. Bugfix on
9872 - Avoid segfault in rare cases when finishing an introduction circuit
9873 as a client and finding out that we don't have an introduction key
9874 for it. Fixes bug 1073. Reported by Aaron Swartz.
9877 - Tor now reads the "circwindow" parameter out of the consensus,
9878 and uses that value for its circuit package window rather than the
9879 default of 1000 cells. Begins the implementation of proposal 168.
9881 o New directory authorities:
9882 - Set up urras (run by Jacob Appelbaum) as the seventh v3 directory
9884 - Move moria1 and tonga to alternate IP addresses.
9887 - Fix a signed/unsigned compile warning in 0.2.1.19.
9888 - Fix possible segmentation fault on directory authorities. Bugfix on
9890 - Fix an extremely rare infinite recursion bug that could occur if
9891 we tried to log a message after shutting down the log subsystem.
9892 Found by Matt Edman. Bugfix on 0.2.0.16-alpha.
9893 - Fix an obscure bug where hidden services on 64-bit big-endian
9894 systems might mis-read the timestamp in v3 introduce cells, and
9895 refuse to connect back to the client. Discovered by "rotor".
9896 Bugfix on 0.2.1.6-alpha.
9897 - We were triggering a CLOCK_SKEW controller status event whenever
9898 we connect via the v2 connection protocol to any relay that has
9899 a wrong clock. Instead, we should only inform the controller when
9900 it's a trusted authority that claims our clock is wrong. Bugfix
9901 on 0.2.0.20-rc; starts to fix bug 1074. Reported by SwissTorExit.
9902 - We were telling the controller about CHECKING_REACHABILITY and
9903 REACHABILITY_FAILED status events whenever we launch a testing
9904 circuit or notice that one has failed. Instead, only tell the
9905 controller when we want to inform the user of overall success or
9906 overall failure. Bugfix on 0.1.2.6-alpha. Fixes bug 1075. Reported
9908 - Don't warn when we're using a circuit that ends with a node
9909 excluded in ExcludeExitNodes, but the circuit is not used to access
9910 the outside world. This should help fix bug 1090. Bugfix on
9912 - Work around a small memory leak in some versions of OpenSSL that
9913 stopped the memory used by the hostname TLS extension from being
9917 - Add a "getinfo status/accepted-server-descriptor" controller
9918 command, which is the recommended way for controllers to learn
9919 whether our server descriptor has been successfully received by at
9920 least on directory authority. Un-recommend good-server-descriptor
9921 getinfo and status events until we have a better design for them.
9924 Changes in version 0.2.2.5-alpha - 2009-10-11
9925 Tor 0.2.2.5-alpha fixes a few compile problems in 0.2.2.4-alpha.
9928 - Make the tarball compile again. Oops. Bugfix on 0.2.2.4-alpha.
9930 o Directory authorities:
9931 - Temporarily (just for this release) move dizum to an alternate
9935 Changes in version 0.2.2.4-alpha - 2009-10-10
9936 Tor 0.2.2.4-alpha fixes more crash bugs in 0.2.2.2-alpha. It also
9937 introduces a new unit test framework, shifts directry authority
9938 addresses around to reduce the impact from recent blocking events,
9939 and fixes a few smaller bugs.
9942 - Fix several more asserts in the circuit_build_times code, for
9943 example one that causes Tor to fail to start once we have
9944 accumulated 5000 build times in the state file. Bugfixes on
9945 0.2.2.2-alpha; fixes bug 1108.
9947 o New directory authorities:
9948 - Move moria1 and Tonga to alternate IP addresses.
9951 - Log SSL state transitions at debug level during handshake, and
9952 include SSL states in error messages. This may help debug future
9953 SSL handshake issues.
9954 - Add a new "Handshake" log domain for activities that happen
9955 during the TLS handshake.
9956 - Revert to the "June 3 2009" ip-to-country file. The September one
9957 seems to have removed most US IP addresses.
9958 - Directory authorities now reject Tor relays with versions less than
9959 0.1.2.14. This step cuts out four relays from the current network,
9960 none of which are very big.
9963 - Fix a couple of smaller issues with gathering statistics. Bugfixes
9965 - Fix two memory leaks in the error case of
9966 circuit_build_times_parse_state(). Bugfix on 0.2.2.2-alpha.
9967 - Don't count one-hop circuits when we're estimating how long it
9968 takes circuits to build on average. Otherwise we'll set our circuit
9969 build timeout lower than we should. Bugfix on 0.2.2.2-alpha.
9970 - Directory authorities no longer change their opinion of, or vote on,
9971 whether a router is Running, unless they have themselves been
9972 online long enough to have some idea. Bugfix on 0.2.0.6-alpha.
9975 o Code simplifications and refactoring:
9976 - Revise our unit tests to use the "tinytest" framework, so we
9977 can run tests in their own processes, have smarter setup/teardown
9978 code, and so on. The unit test code has moved to its own
9979 subdirectory, and has been split into multiple modules.
9982 Changes in version 0.2.2.3-alpha - 2009-09-23
9983 Tor 0.2.2.3-alpha fixes a few crash bugs in 0.2.2.2-alpha.
9986 - Fix an overzealous assert in our new circuit build timeout code.
9987 Bugfix on 0.2.2.2-alpha; fixes bug 1103.
9990 - If the networkstatus consensus tells us that we should use a
9991 negative circuit package window, ignore it. Otherwise we'll
9992 believe it and then trigger an assert. Bugfix on 0.2.2.2-alpha.
9995 Changes in version 0.2.2.2-alpha - 2009-09-21
9996 Tor 0.2.2.2-alpha introduces our latest performance improvement for
9997 clients: Tor tracks the average time it takes to build a circuit, and
9998 avoids using circuits that take too long to build. For fast connections,
9999 this feature can cut your expected latency in half. For slow or flaky
10000 connections, it could ruin your Tor experience. Let us know if it does!
10003 - Tor now tracks how long it takes to build client-side circuits
10004 over time, and adapts its timeout to local network performance.
10005 Since a circuit that takes a long time to build will also provide
10006 bad performance, we get significant latency improvements by
10007 discarding the slowest 20% of circuits. Specifically, Tor creates
10008 circuits more aggressively than usual until it has enough data
10009 points for a good timeout estimate. Implements proposal 151.
10010 We are especially looking for reports (good and bad) from users with
10011 both EDGE and broadband connections that can move from broadband
10012 to EDGE and find out if the build-time data in the .tor/state gets
10013 reset without loss of Tor usability. You should also see a notice
10014 log message telling you that Tor has reset its timeout.
10015 - Directory authorities can now vote on arbitary integer values as
10016 part of the consensus process. This is designed to help set
10017 network-wide parameters. Implements proposal 167.
10018 - Tor now reads the "circwindow" parameter out of the consensus,
10019 and uses that value for its circuit package window rather than the
10020 default of 1000 cells. Begins the implementation of proposal 168.
10023 - Fix a remotely triggerable memory leak when a consensus document
10024 contains more than one signature from the same voter. Bugfix on
10028 - Fix an extremely rare infinite recursion bug that could occur if
10029 we tried to log a message after shutting down the log subsystem.
10030 Found by Matt Edman. Bugfix on 0.2.0.16-alpha.
10031 - Fix parsing for memory or time units given without a space between
10032 the number and the unit. Bugfix on 0.2.2.1-alpha; fixes bug 1076.
10033 - A networkstatus vote must contain exactly one signature. Spec
10034 conformance issue. Bugfix on 0.2.0.3-alpha.
10035 - Fix an obscure bug where hidden services on 64-bit big-endian
10036 systems might mis-read the timestamp in v3 introduce cells, and
10037 refuse to connect back to the client. Discovered by "rotor".
10038 Bugfix on 0.2.1.6-alpha.
10039 - We were triggering a CLOCK_SKEW controller status event whenever
10040 we connect via the v2 connection protocol to any relay that has
10041 a wrong clock. Instead, we should only inform the controller when
10042 it's a trusted authority that claims our clock is wrong. Bugfix
10043 on 0.2.0.20-rc; starts to fix bug 1074. Reported by SwissTorExit.
10044 - We were telling the controller about CHECKING_REACHABILITY and
10045 REACHABILITY_FAILED status events whenever we launch a testing
10046 circuit or notice that one has failed. Instead, only tell the
10047 controller when we want to inform the user of overall success or
10048 overall failure. Bugfix on 0.1.2.6-alpha. Fixes bug 1075. Reported
10050 - Don't warn when we're using a circuit that ends with a node
10051 excluded in ExcludeExitNodes, but the circuit is not used to access
10052 the outside world. This should help fix bug 1090, but more problems
10053 remain. Bugfix on 0.2.1.6-alpha.
10054 - Work around a small memory leak in some versions of OpenSSL that
10055 stopped the memory used by the hostname TLS extension from being
10057 - Make our 'torify' script more portable; if we have only one of
10058 'torsocks' or 'tsocks' installed, don't complain to the user;
10059 and explain our warning about tsocks better.
10062 - Add a "getinfo status/accepted-server-descriptor" controller
10063 command, which is the recommended way for controllers to learn
10064 whether our server descriptor has been successfully received by at
10065 least on directory authority. Un-recommend good-server-descriptor
10066 getinfo and status events until we have a better design for them.
10067 - Update to the "September 4 2009" ip-to-country file.
10070 Changes in version 0.2.2.1-alpha - 2009-08-26
10071 Tor 0.2.2.1-alpha disables ".exit" address notation by default, allows
10072 Tor clients to bootstrap on networks where only port 80 is reachable,
10073 makes it more straightforward to support hardware crypto accelerators,
10074 and starts the groundwork for gathering stats safely at relays.
10077 - Start the process of disabling ".exit" address notation, since it
10078 can be used for a variety of esoteric application-level attacks
10079 on users. To reenable it, set "AllowDotExit 1" in your torrc. Fix
10082 o New directory authorities:
10083 - Set up urras (run by Jacob Appelbaum) as the seventh v3 directory
10087 - New AccelName and AccelDir options add support for dynamic OpenSSL
10088 hardware crypto acceleration engines.
10089 - Tor now supports tunneling all of its outgoing connections over
10090 a SOCKS proxy, using the SOCKS4Proxy and/or SOCKS5Proxy
10091 configuration options. Code by Christopher Davis.
10094 - Send circuit or stream sendme cells when our window has decreased
10095 by 100 cells, not when it has decreased by 101 cells. Bug uncovered
10096 by Karsten when testing the "reduce circuit window" performance
10097 patch. Bugfix on the 54th commit on Tor -- from July 2002,
10098 before the release of Tor 0.0.0. This is the new winner of the
10101 o New options for gathering stats safely:
10102 - Directory mirrors that set "DirReqStatistics 1" write statistics
10103 about directory requests to disk every 24 hours. As compared to the
10104 --enable-geoip-stats flag in 0.2.1.x, there are a few improvements:
10105 1) stats are written to disk exactly every 24 hours; 2) estimated
10106 shares of v2 and v3 requests are determined as mean values, not at
10107 the end of a measurement period; 3) unresolved requests are listed
10108 with country code '??'; 4) directories also measure download times.
10109 - Exit nodes that set "ExitPortStatistics 1" write statistics on the
10110 number of exit streams and transferred bytes per port to disk every
10112 - Relays that set "CellStatistics 1" write statistics on how long
10113 cells spend in their circuit queues to disk every 24 hours.
10114 - Entry nodes that set "EntryStatistics 1" write statistics on the
10115 rough number and origins of connecting clients to disk every 24
10117 - Relays that write any of the above statistics to disk and set
10118 "ExtraInfoStatistics 1" include the past 24 hours of statistics in
10119 their extra-info documents.
10122 - New --digests command-line switch to output the digests of the
10123 source files Tor was built with.
10124 - The "torify" script now uses torsocks where available.
10125 - The memarea code now uses a sentinel value at the end of each area
10126 to make sure nothing writes beyond the end of an area. This might
10127 help debug some conceivable causes of bug 930.
10128 - Time and memory units in the configuration file can now be set to
10129 fractional units. For example, "2.5 GB" is now a valid value for
10131 - Certain Tor clients (such as those behind check.torproject.org) may
10132 want to fetch the consensus in an extra early manner. To enable this
10133 a user may now set FetchDirInfoExtraEarly to 1. This also depends on
10134 setting FetchDirInfoEarly to 1. Previous behavior will stay the same
10135 as only certain clients who must have this information sooner should
10137 - Instead of adding the svn revision to the Tor version string, report
10138 the git commit (when we're building from a git checkout).
10141 - If any of the v3 certs we download are unparseable, we should
10142 actually notice the failure so we don't retry indefinitely. Bugfix
10143 on 0.2.0.x; reported by "rotator".
10144 - If the cached cert file is unparseable, warn but don't exit.
10145 - Fix possible segmentation fault on directory authorities. Bugfix on
10147 - When Tor fails to parse a descriptor of any kind, dump it to disk.
10148 Might help diagnosing bug 1051.
10150 o Deprecated and removed features:
10151 - The controller no longer accepts the old obsolete "addr-mappings/"
10152 or "unregistered-servers-" GETINFO values.
10153 - Hidden services no longer publish version 0 descriptors, and clients
10154 do not request or use version 0 descriptors. However, the old hidden
10155 service authorities still accept and serve version 0 descriptors
10156 when contacted by older hidden services/clients.
10157 - The EXTENDED_EVENTS and VERBOSE_NAMES controller features are now
10158 always on; using them is necessary for correct forward-compatible
10160 - Remove support for .noconnect style addresses. Nobody was using
10161 them, and they provided another avenue for detecting Tor users
10162 via application-level web tricks.
10164 o Packaging changes:
10165 - Upgrade Vidalia from 0.1.15 to 0.2.3 in the Windows and OS X
10166 installer bundles. See
10167 https://trac.vidalia-project.net/browser/vidalia/tags/vidalia-0.2.3/CHANGELOG
10168 for details of what's new in Vidalia 0.2.3.
10169 - Windows Vidalia Bundle: update Privoxy from 3.0.6 to 3.0.14-beta.
10170 - OS X Vidalia Bundle: move to Polipo 1.0.4 with Tor specific
10171 configuration file, rather than the old Privoxy.
10172 - OS X Vidalia Bundle: Vidalia, Tor, and Polipo are compiled as
10173 x86-only for better compatibility with OS X 10.6, aka Snow Leopard.
10174 - OS X Tor Expert Bundle: Tor is compiled as x86-only for
10175 better compatibility with OS X 10.6, aka Snow Leopard.
10176 - OS X Vidalia Bundle: The multi-package installer is now replaced
10177 by a simple drag and drop to the /Applications folder. This change
10178 occurred with the upgrade to Vidalia 0.2.3.
10181 Changes in version 0.2.1.19 - 2009-07-28
10182 Tor 0.2.1.19 fixes a major bug with accessing and providing hidden
10183 services on Tor 0.2.1.3-alpha through 0.2.1.18.
10186 - Make accessing hidden services on 0.2.1.x work right again.
10187 Bugfix on 0.2.1.3-alpha; workaround for bug 1038. Diagnosis and
10188 part of patch provided by "optimist".
10191 - When a relay/bridge is writing out its identity key fingerprint to
10192 the "fingerprint" file and to its logs, write it without spaces. Now
10193 it will look like the fingerprints in our bridges documentation,
10194 and confuse fewer users.
10197 - Relays no longer publish a new server descriptor if they change
10198 their MaxAdvertisedBandwidth config option but it doesn't end up
10199 changing their advertised bandwidth numbers. Bugfix on 0.2.0.28-rc;
10200 fixes bug 1026. Patch from Sebastian.
10201 - Avoid leaking memory every time we get a create cell but we have
10202 so many already queued that we refuse it. Bugfix on 0.2.0.19-alpha;
10203 fixes bug 1034. Reported by BarkerJr.
10206 Changes in version 0.2.1.18 - 2009-07-24
10207 Tor 0.2.1.18 lays the foundations for performance improvements,
10208 adds status events to help users diagnose bootstrap problems, adds
10209 optional authentication/authorization for hidden services, fixes a
10210 variety of potential anonymity problems, and includes a huge pile of
10211 other features and bug fixes.
10214 - Add LIBS=-lrt to Makefile.am so the Tor RPMs use a static libevent.
10217 Changes in version 0.2.1.17-rc - 2009-07-07
10218 Tor 0.2.1.17-rc marks the fourth -- and hopefully last -- release
10219 candidate for the 0.2.1.x series. It lays the groundwork for further
10220 client performance improvements, and also fixes a big bug with directory
10221 authorities that were causing them to assign Guard and Stable flags
10224 The Windows bundles also finally include the geoip database that we
10225 thought we'd been shipping since 0.2.0.x (oops), and the OS X bundles
10226 should actually install Torbutton rather than giving you a cryptic
10227 failure message (oops).
10230 - Clients now use the bandwidth values in the consensus, rather than
10231 the bandwidth values in each relay descriptor. This approach opens
10232 the door to more accurate bandwidth estimates once the directory
10233 authorities start doing active measurements. Implements more of
10237 - When Tor clients restart after 1-5 days, they discard all their
10238 cached descriptors as too old, but they still use the cached
10239 consensus document. This approach is good for robustness, but
10240 bad for performance: since they don't know any bandwidths, they
10241 end up choosing at random rather than weighting their choice by
10242 speed. Fixed by the above feature of putting bandwidths in the
10243 consensus. Bugfix on 0.2.0.x.
10244 - Directory authorities were neglecting to mark relays down in their
10245 internal histories if the relays fall off the routerlist without
10246 ever being found unreachable. So there were relays in the histories
10247 that haven't been seen for eight months, and are listed as being
10248 up for eight months. This wreaked havoc on the "median wfu"
10249 and "median mtbf" calculations, in turn making Guard and Stable
10250 flags very wrong, hurting network performance. Fixes bugs 696 and
10251 969. Bugfix on 0.2.0.6-alpha.
10254 - Serve the DirPortFrontPage page even when we have been approaching
10255 our quotas recently. Fixes bug 1013; bugfix on 0.2.1.8-alpha.
10256 - The control port would close the connection before flushing long
10257 replies, such as the network consensus, if a QUIT command was issued
10258 before the reply had completed. Now, the control port flushes all
10259 pending replies before closing the connection. Also fixed a spurious
10260 warning when a QUIT command is issued after a malformed or rejected
10261 AUTHENTICATE command, but before the connection was closed. Patch
10262 by Marcus Griep. Bugfix on 0.2.0.x; fixes bugs 1015 and 1016.
10263 - When we can't find an intro key for a v2 hidden service descriptor,
10264 fall back to the v0 hidden service descriptor and log a bug message.
10265 Workaround for bug 1024.
10266 - Fix a log message that did not respect the SafeLogging option.
10270 - If we're a relay and we change our IP address, be more verbose
10271 about the reason that made us change. Should help track down
10272 further bugs for relays on dynamic IP addresses.
10275 Changes in version 0.2.0.35 - 2009-06-24
10277 - Avoid crashing in the presence of certain malformed descriptors.
10278 Found by lark, and by automated fuzzing.
10279 - Fix an edge case where a malicious exit relay could convince a
10280 controller that the client's DNS question resolves to an internal IP
10281 address. Bug found and fixed by "optimist"; bugfix on 0.1.2.8-beta.
10284 - Finally fix the bug where dynamic-IP relays disappear when their
10285 IP address changes: directory mirrors were mistakenly telling
10286 them their old address if they asked via begin_dir, so they
10287 never got an accurate answer about their new address, so they
10288 just vanished after a day. For belt-and-suspenders, relays that
10289 don't set Address in their config now avoid using begin_dir for
10290 all direct connections. Should fix bugs 827, 883, and 900.
10291 - Fix a timing-dependent, allocator-dependent, DNS-related crash bug
10292 that would occur on some exit nodes when DNS failures and timeouts
10293 occurred in certain patterns. Fix for bug 957.
10296 - When starting with a cache over a few days old, do not leak
10297 memory for the obsolete router descriptors in it. Bugfix on
10298 0.2.0.33; fixes bug 672.
10299 - Hidden service clients didn't use a cached service descriptor that
10300 was older than 15 minutes, but wouldn't fetch a new one either,
10301 because there was already one in the cache. Now, fetch a v2
10302 descriptor unless the same descriptor was added to the cache within
10303 the last 15 minutes. Fixes bug 997; reported by Marcus Griep.
10306 Changes in version 0.2.1.16-rc - 2009-06-20
10307 Tor 0.2.1.16-rc speeds up performance for fast exit relays, and fixes
10308 a bunch of minor bugs.
10311 - Fix an edge case where a malicious exit relay could convince a
10312 controller that the client's DNS question resolves to an internal IP
10313 address. Bug found and fixed by "optimist"; bugfix on 0.1.2.8-beta.
10315 o Major performance improvements (on 0.2.0.x):
10316 - Disable and refactor some debugging checks that forced a linear scan
10317 over the whole server-side DNS cache. These accounted for over 50%
10318 of CPU time on a relatively busy exit node's gprof profile. Found
10320 - Disable some debugging checks that appeared in exit node profile
10324 - Update to the "June 3 2009" ip-to-country file.
10325 - Do not have tor-resolve automatically refuse all .onion addresses;
10326 if AutomapHostsOnResolve is set in your torrc, this will work fine.
10328 o Minor bugfixes (on 0.2.0.x):
10329 - Log correct error messages for DNS-related network errors on
10331 - Fix a race condition that could cause crashes or memory corruption
10332 when running as a server with a controller listening for log
10334 - Avoid crashing when we have a policy specified in a DirPolicy or
10335 SocksPolicy or ReachableAddresses option with ports set on it,
10336 and we re-load the policy. May fix bug 996.
10337 - Hidden service clients didn't use a cached service descriptor that
10338 was older than 15 minutes, but wouldn't fetch a new one either,
10339 because there was already one in the cache. Now, fetch a v2
10340 descriptor unless the same descriptor was added to the cache within
10341 the last 15 minutes. Fixes bug 997; reported by Marcus Griep.
10343 o Minor bugfixes (on 0.2.1.x):
10344 - Don't warn users about low port and hibernation mix when they
10345 provide a *ListenAddress directive to fix that. Bugfix on
10347 - When switching back and forth between bridge mode, do not start
10348 gathering GeoIP data until two hours have passed.
10349 - Do not complain that the user has requested an excluded node as
10350 an exit when the node is not really an exit. This could happen
10351 because the circuit was for testing, or an introduction point.
10355 Changes in version 0.2.1.15-rc - 2009-05-25
10356 Tor 0.2.1.15-rc marks the second release candidate for the 0.2.1.x
10357 series. It fixes a major bug on fast exit relays, as well as a variety
10358 of more minor bugs.
10360 o Major bugfixes (on 0.2.0.x):
10361 - Fix a timing-dependent, allocator-dependent, DNS-related crash bug
10362 that would occur on some exit nodes when DNS failures and timeouts
10363 occurred in certain patterns. Fix for bug 957.
10365 o Minor bugfixes (on 0.2.0.x):
10366 - Actually return -1 in the error case for read_bandwidth_usage().
10367 Harmless bug, since we currently don't care about the return value
10368 anywhere. Bugfix on 0.2.0.9-alpha.
10369 - Provide a more useful log message if bug 977 (related to buffer
10370 freelists) ever reappears, and do not crash right away.
10371 - Fix an assertion failure on 64-bit platforms when we allocated
10372 memory right up to the end of a memarea, then realigned the memory
10373 one step beyond the end. Fixes a possible cause of bug 930.
10374 - Protect the count of open sockets with a mutex, so we can't
10375 corrupt it when two threads are closing or opening sockets at once.
10376 Fix for bug 939. Bugfix on 0.2.0.1-alpha.
10377 - Don't allow a bridge to publish its router descriptor to a
10378 non-bridge directory authority. Fixes part of bug 932.
10379 - When we change to or from being a bridge, reset our counts of
10380 client usage by country. Fixes bug 932.
10381 - Fix a bug that made stream bandwidth get misreported to the
10383 - Stop using malloc_usable_size() to use more area than we had
10384 actually allocated: it was safe, but made valgrind really unhappy.
10385 - Fix a memory leak when v3 directory authorities load their keys
10386 and cert from disk. Bugfix on 0.2.0.1-alpha.
10388 o Minor bugfixes (on 0.2.1.x):
10389 - Fix use of freed memory when deciding to mark a non-addable
10390 descriptor as never-downloadable. Bugfix on 0.2.1.9-alpha.
10393 Changes in version 0.2.1.14-rc - 2009-04-12
10394 Tor 0.2.1.14-rc marks the first release candidate for the 0.2.1.x
10395 series. It begins fixing some major performance problems, and also
10396 finally addresses the bug that was causing relays on dynamic IP
10397 addresses to fall out of the directory.
10400 - Clients replace entry guards that were chosen more than a few months
10401 ago. This change should significantly improve client performance,
10402 especially once more people upgrade, since relays that have been
10403 a guard for a long time are currently overloaded.
10405 o Major bugfixes (on 0.2.0):
10406 - Finally fix the bug where dynamic-IP relays disappear when their
10407 IP address changes: directory mirrors were mistakenly telling
10408 them their old address if they asked via begin_dir, so they
10409 never got an accurate answer about their new address, so they
10410 just vanished after a day. For belt-and-suspenders, relays that
10411 don't set Address in their config now avoid using begin_dir for
10412 all direct connections. Should fix bugs 827, 883, and 900.
10413 - Relays were falling out of the networkstatus consensus for
10414 part of a day if they changed their local config but the
10415 authorities discarded their new descriptor as "not sufficiently
10416 different". Now directory authorities accept a descriptor as changed
10417 if bandwidthrate or bandwidthburst changed. Partial fix for bug 962;
10418 patch by Sebastian.
10419 - Avoid crashing in the presence of certain malformed descriptors.
10420 Found by lark, and by automated fuzzing.
10423 - When generating circuit events with verbose nicknames for
10424 controllers, try harder to look up nicknames for routers on a
10425 circuit. (Previously, we would look in the router descriptors we had
10426 for nicknames, but not in the consensus.) Partial fix for bug 941.
10427 - If the bridge config line doesn't specify a port, assume 443.
10428 This makes bridge lines a bit smaller and easier for users to
10430 - Raise the minimum bandwidth to be a relay from 20000 bytes to 20480
10431 bytes (aka 20KB/s), to match our documentation. Also update
10432 directory authorities so they always assign the Fast flag to relays
10433 with 20KB/s of capacity. Now people running relays won't suddenly
10434 find themselves not seeing any use, if the network gets faster
10436 - Update to the "April 3 2009" ip-to-country file.
10439 - Avoid trying to print raw memory to the logs when we decide to
10440 give up on downloading a given relay descriptor. Bugfix on
10442 - In tor-resolve, when the Tor client to use is specified by
10443 <hostname>:<port>, actually use the specified port rather than
10444 defaulting to 9050. Bugfix on 0.2.1.6-alpha.
10445 - Make directory usage recording work again. Bugfix on 0.2.1.6-alpha.
10446 - When starting with a cache over a few days old, do not leak
10447 memory for the obsolete router descriptors in it. Bugfix on
10449 - Avoid double-free on list of successfully uploaded hidden
10450 service discriptors. Fix for bug 948. Bugfix on 0.2.1.6-alpha.
10451 - Change memarea_strndup() implementation to work even when
10452 duplicating a string at the end of a page. This bug was
10453 harmless for now, but could have meant crashes later. Fix by
10454 lark. Bugfix on 0.2.1.1-alpha.
10455 - Limit uploaded directory documents to be 16M rather than 500K.
10456 The directory authorities were refusing v3 consensus votes from
10457 other authorities, since the votes are now 504K. Fixes bug 959;
10458 bugfix on 0.0.2pre17 (where we raised it from 50K to 500K ;).
10459 - Directory authorities should never send a 503 "busy" response to
10460 requests for votes or keys. Bugfix on 0.2.0.8-alpha; exposed by
10464 Changes in version 0.2.1.13-alpha - 2009-03-09
10465 Tor 0.2.1.13-alpha includes another big pile of minor bugfixes and
10466 cleanups. We're finally getting close to a release candidate.
10469 - Correctly update the list of which countries we exclude as
10470 exits, when the GeoIP file is loaded or reloaded. Diagnosed by
10471 lark. Bugfix on 0.2.1.6-alpha.
10473 o Minor bugfixes (on 0.2.0.x and earlier):
10474 - Automatically detect MacOSX versions earlier than 10.4.0, and
10475 disable kqueue from inside Tor when running with these versions.
10476 We previously did this from the startup script, but that was no
10477 help to people who didn't use the startup script. Resolves bug 863.
10478 - When we had picked an exit node for a connection, but marked it as
10479 "optional", and it turned out we had no onion key for the exit,
10480 stop wanting that exit and try again. This situation may not
10481 be possible now, but will probably become feasible with proposal
10482 158. Spotted by rovv. Fixes another case of bug 752.
10483 - Clients no longer cache certificates for authorities they do not
10484 recognize. Bugfix on 0.2.0.9-alpha.
10485 - When we can't transmit a DNS request due to a network error, retry
10486 it after a while, and eventually transmit a failing response to
10487 the RESOLVED cell. Bugfix on 0.1.2.5-alpha.
10488 - If the controller claimed responsibility for a stream, but that
10489 stream never finished making its connection, it would live
10490 forever in circuit_wait state. Now we close it after SocksTimeout
10491 seconds. Bugfix on 0.1.2.7-alpha; reported by Mike Perry.
10492 - Drop begin cells to a hidden service if they come from the middle
10493 of a circuit. Patch from lark.
10494 - When we erroneously receive two EXTEND cells for the same circuit
10495 ID on the same connection, drop the second. Patch from lark.
10496 - Fix a crash that occurs on exit nodes when a nameserver request
10497 timed out. Bugfix on 0.1.2.1-alpha; our CLEAR debugging code had
10498 been suppressing the bug since 0.1.2.10-alpha. Partial fix for
10500 - Do not assume that a stack-allocated character array will be
10501 64-bit aligned on platforms that demand that uint64_t access is
10502 aligned. Possible fix for bug 604.
10503 - Parse dates and IPv4 addresses in a locale- and libc-independent
10504 manner, to avoid platform-dependent behavior on malformed input.
10505 - Build correctly when configured to build outside the main source
10506 path. Patch from Michael Gold.
10507 - We were already rejecting relay begin cells with destination port
10508 of 0. Now also reject extend cells with destination port or address
10509 of 0. Suggested by lark.
10511 o Minor bugfixes (on 0.2.1.x):
10512 - Don't re-extend introduction circuits if we ran out of RELAY_EARLY
10513 cells. Bugfix on 0.2.1.3-alpha. Fixes more of bug 878.
10514 - If we're an exit node, scrub the IP address to which we are exiting
10515 in the logs. Bugfix on 0.2.1.8-alpha.
10518 - On Linux, use the prctl call to re-enable core dumps when the user
10520 - New controller event NEWCONSENSUS that lists the networkstatus
10521 lines for every recommended relay. Now controllers like Torflow
10522 can keep up-to-date on which relays they should be using.
10523 - Update to the "February 26 2009" ip-to-country file.
10526 Changes in version 0.2.0.34 - 2009-02-08
10527 Tor 0.2.0.34 features several more security-related fixes. You should
10528 upgrade, especially if you run an exit relay (remote crash) or a
10529 directory authority (remote infinite loop), or you're on an older
10530 (pre-XP) or not-recently-patched Windows (remote exploit).
10532 This release marks end-of-life for Tor 0.1.2.x. Those Tor versions
10533 have many known flaws, and nobody should be using them. You should
10534 upgrade. If you're using a Linux or BSD and its packages are obsolete,
10535 stop using those packages and upgrade anyway.
10538 - Fix an infinite-loop bug on handling corrupt votes under certain
10539 circumstances. Bugfix on 0.2.0.8-alpha.
10540 - Fix a temporary DoS vulnerability that could be performed by
10541 a directory mirror. Bugfix on 0.2.0.9-alpha; reported by lark.
10542 - Avoid a potential crash on exit nodes when processing malformed
10543 input. Remote DoS opportunity. Bugfix on 0.2.0.33.
10544 - Do not accept incomplete ipv4 addresses (like 192.168.0) as valid.
10545 Spec conformance issue. Bugfix on Tor 0.0.2pre27.
10548 - Fix compilation on systems where time_t is a 64-bit integer.
10549 Patch from Matthias Drochner.
10550 - Don't consider expiring already-closed client connections. Fixes
10551 bug 893. Bugfix on 0.0.2pre20.
10554 Changes in version 0.2.1.12-alpha - 2009-02-08
10555 Tor 0.2.1.12-alpha features several more security-related fixes. You
10556 should upgrade, especially if you run an exit relay (remote crash) or
10557 a directory authority (remote infinite loop), or you're on an older
10558 (pre-XP) or not-recently-patched Windows (remote exploit). It also
10559 includes a big pile of minor bugfixes and cleanups.
10562 - Fix an infinite-loop bug on handling corrupt votes under certain
10563 circumstances. Bugfix on 0.2.0.8-alpha.
10564 - Fix a temporary DoS vulnerability that could be performed by
10565 a directory mirror. Bugfix on 0.2.0.9-alpha; reported by lark.
10566 - Avoid a potential crash on exit nodes when processing malformed
10567 input. Remote DoS opportunity. Bugfix on 0.2.1.7-alpha.
10570 - Let controllers actually ask for the "clients_seen" event for
10571 getting usage summaries on bridge relays. Bugfix on 0.2.1.10-alpha;
10572 reported by Matt Edman.
10573 - Fix a compile warning on OSX Panther. Fixes bug 913; bugfix against
10575 - Fix a bug in address parsing that was preventing bridges or hidden
10576 service targets from being at IPv6 addresses.
10577 - Solve a bug that kept hardware crypto acceleration from getting
10578 enabled when accounting was turned on. Fixes bug 907. Bugfix on
10580 - Remove a bash-ism from configure.in to build properly on non-Linux
10581 platforms. Bugfix on 0.2.1.1-alpha.
10582 - Fix code so authorities _actually_ send back X-Descriptor-Not-New
10583 headers. Bugfix on 0.2.0.10-alpha.
10584 - Don't consider expiring already-closed client connections. Fixes
10585 bug 893. Bugfix on 0.0.2pre20.
10586 - Fix another interesting corner-case of bug 891 spotted by rovv:
10587 Previously, if two hosts had different amounts of clock drift, and
10588 one of them created a new connection with just the wrong timing,
10589 the other might decide to deprecate the new connection erroneously.
10590 Bugfix on 0.1.1.13-alpha.
10591 - Resolve a very rare crash bug that could occur when the user forced
10592 a nameserver reconfiguration during the middle of a nameserver
10593 probe. Fixes bug 526. Bugfix on 0.1.2.1-alpha.
10594 - Support changing value of ServerDNSRandomizeCase during SIGHUP.
10595 Bugfix on 0.2.1.7-alpha.
10596 - If we're using bridges and our network goes away, be more willing
10597 to forgive our bridges and try again when we get an application
10598 request. Bugfix on 0.2.0.x.
10601 - Support platforms where time_t is 64 bits long. (Congratulations,
10602 NetBSD!) Patch from Matthias Drochner.
10603 - Add a 'getinfo status/clients-seen' controller command, in case
10604 controllers want to hear clients_seen events but connect late.
10607 - Disable GCC's strict alias optimization by default, to avoid the
10608 likelihood of its introducing subtle bugs whenever our code violates
10609 the letter of C99's alias rules.
10612 Changes in version 0.2.0.33 - 2009-01-21
10613 Tor 0.2.0.33 fixes a variety of bugs that were making relays less
10614 useful to users. It also finally fixes a bug where a relay or client
10615 that's been off for many days would take a long time to bootstrap.
10617 This update also fixes an important security-related bug reported by
10618 Ilja van Sprundel. You should upgrade. (We'll send out more details
10619 about the bug once people have had some time to upgrade.)
10622 - Fix a heap-corruption bug that may be remotely triggerable on
10623 some platforms. Reported by Ilja van Sprundel.
10626 - When a stream at an exit relay is in state "resolving" or
10627 "connecting" and it receives an "end" relay cell, the exit relay
10628 would silently ignore the end cell and not close the stream. If
10629 the client never closes the circuit, then the exit relay never
10630 closes the TCP connection. Bug introduced in Tor 0.1.2.1-alpha;
10631 reported by "wood".
10632 - When sending CREATED cells back for a given circuit, use a 64-bit
10633 connection ID to find the right connection, rather than an addr:port
10634 combination. Now that we can have multiple OR connections between
10635 the same ORs, it is no longer possible to use addr:port to uniquely
10636 identify a connection.
10637 - Bridge relays that had DirPort set to 0 would stop fetching
10638 descriptors shortly after startup, and then briefly resume
10639 after a new bandwidth test and/or after publishing a new bridge
10640 descriptor. Bridge users that try to bootstrap from them would
10641 get a recent networkstatus but would get descriptors from up to
10642 18 hours earlier, meaning most of the descriptors were obsolete
10643 already. Reported by Tas; bugfix on 0.2.0.13-alpha.
10644 - Prevent bridge relays from serving their 'extrainfo' document
10645 to anybody who asks, now that extrainfo docs include potentially
10646 sensitive aggregated client geoip summaries. Bugfix on
10648 - If the cached networkstatus consensus is more than five days old,
10649 discard it rather than trying to use it. In theory it could be
10650 useful because it lists alternate directory mirrors, but in practice
10651 it just means we spend many minutes trying directory mirrors that
10652 are long gone from the network. Also discard router descriptors as
10653 we load them if they are more than five days old, since the onion
10654 key is probably wrong by now. Bugfix on 0.2.0.x. Fixes bug 887.
10657 - Do not mark smartlist_bsearch_idx() function as ATTR_PURE. This bug
10658 could make gcc generate non-functional binary search code. Bugfix
10660 - Build correctly on platforms without socklen_t.
10661 - Compile without warnings on solaris.
10662 - Avoid potential crash on internal error during signature collection.
10663 Fixes bug 864. Patch from rovv.
10664 - Correct handling of possible malformed authority signing key
10665 certificates with internal signature types. Fixes bug 880.
10666 Bugfix on 0.2.0.3-alpha.
10667 - Fix a hard-to-trigger resource leak when logging credential status.
10669 - When we can't initialize DNS because the network is down, do not
10670 automatically stop Tor from starting. Instead, we retry failed
10671 dns_init() every 10 minutes, and change the exit policy to reject
10672 *:* until one succeeds. Fixes bug 691.
10673 - Use 64 bits instead of 32 bits for connection identifiers used with
10674 the controller protocol, to greatly reduce risk of identifier reuse.
10675 - When we're choosing an exit node for a circuit, and we have
10676 no pending streams, choose a good general exit rather than one that
10677 supports "all the pending streams". Bugfix on 0.1.1.x. Fix by rovv.
10678 - Fix another case of assuming, when a specific exit is requested,
10679 that we know more than the user about what hosts it allows.
10680 Fixes one case of bug 752. Patch from rovv.
10681 - Clip the MaxCircuitDirtiness config option to a minimum of 10
10682 seconds. Warn the user if lower values are given in the
10683 configuration. Bugfix on 0.1.0.1-rc. Patch by Sebastian.
10684 - Clip the CircuitBuildTimeout to a minimum of 30 seconds. Warn the
10685 user if lower values are given in the configuration. Bugfix on
10686 0.1.1.17-rc. Patch by Sebastian.
10687 - Fix a memory leak when we decline to add a v2 rendezvous descriptor to
10688 the cache because we already had a v0 descriptor with the same ID.
10689 Bugfix on 0.2.0.18-alpha.
10690 - Fix a race condition when freeing keys shared between main thread
10691 and CPU workers that could result in a memory leak. Bugfix on
10692 0.1.0.1-rc. Fixes bug 889.
10693 - Send a valid END cell back when a client tries to connect to a
10694 nonexistent hidden service port. Bugfix on 0.1.2.15. Fixes bug
10695 840. Patch from rovv.
10696 - Check which hops rendezvous stream cells are associated with to
10697 prevent possible guess-the-streamid injection attacks from
10698 intermediate hops. Fixes another case of bug 446. Based on patch
10700 - If a broken client asks a non-exit router to connect somewhere,
10701 do not even do the DNS lookup before rejecting the connection.
10702 Fixes another case of bug 619. Patch from rovv.
10703 - When a relay gets a create cell it can't decrypt (e.g. because it's
10704 using the wrong onion key), we were dropping it and letting the
10705 client time out. Now actually answer with a destroy cell. Fixes
10706 bug 904. Bugfix on 0.0.2pre8.
10708 o Minor bugfixes (hidden services):
10709 - Do not throw away existing introduction points on SIGHUP. Bugfix on
10710 0.0.6pre1. Patch by Karsten. Fixes bug 874.
10713 - Report the case where all signatures in a detached set are rejected
10714 differently than the case where there is an error handling the
10716 - When we realize that another process has modified our cached
10717 descriptors, print out a more useful error message rather than
10718 triggering an assertion. Fixes bug 885. Patch from Karsten.
10719 - Implement the 0x20 hack to better resist DNS poisoning: set the
10720 case on outgoing DNS requests randomly, and reject responses that do
10721 not match the case correctly. This logic can be disabled with the
10722 ServerDNSRamdomizeCase setting, if you are using one of the 0.3%
10723 of servers that do not reliably preserve case in replies. See
10724 "Increased DNS Forgery Resistance through 0x20-Bit Encoding"
10726 - Check DNS replies for more matching fields to better resist DNS
10728 - Never use OpenSSL compression: it wastes RAM and CPU trying to
10729 compress cells, which are basically all encrypted, compressed, or
10733 Changes in version 0.2.1.11-alpha - 2009-01-20
10734 Tor 0.2.1.11-alpha finishes fixing the "if your Tor is off for a
10735 week it will take a long time to bootstrap again" bug. It also fixes
10736 an important security-related bug reported by Ilja van Sprundel. You
10737 should upgrade. (We'll send out more details about the bug once people
10738 have had some time to upgrade.)
10741 - Fix a heap-corruption bug that may be remotely triggerable on
10742 some platforms. Reported by Ilja van Sprundel.
10745 - Discard router descriptors as we load them if they are more than
10746 five days old. Otherwise if Tor is off for a long time and then
10747 starts with cached descriptors, it will try to use the onion
10748 keys in those obsolete descriptors when building circuits. Bugfix
10749 on 0.2.0.x. Fixes bug 887.
10752 - Try to make sure that the version of Libevent we're running with
10753 is binary-compatible with the one we built with. May address bug
10755 - Make setting ServerDNSRandomizeCase to 0 actually work. Bugfix
10756 for bug 905. Bugfix on 0.2.1.7-alpha.
10757 - Add a new --enable-local-appdata configuration switch to change
10758 the default location of the datadir on win32 from APPDATA to
10759 LOCAL_APPDATA. In the future, we should migrate to LOCAL_APPDATA
10760 entirely. Patch from coderman.
10763 - Make outbound DNS packets respect the OutboundBindAddress setting.
10764 Fixes the bug part of bug 798. Bugfix on 0.1.2.2-alpha.
10765 - When our circuit fails at the first hop (e.g. we get a destroy
10766 cell back), avoid using that OR connection anymore, and also
10767 tell all the one-hop directory requests waiting for it that they
10768 should fail. Bugfix on 0.2.1.3-alpha.
10769 - In the torify(1) manpage, mention that tsocks will leak your
10773 Changes in version 0.2.1.10-alpha - 2009-01-06
10774 Tor 0.2.1.10-alpha fixes two major bugs in bridge relays (one that
10775 would make the bridge relay not so useful if it had DirPort set to 0,
10776 and one that could let an attacker learn a little bit of information
10777 about the bridge's users), and a bug that would cause your Tor relay
10778 to ignore a circuit create request it can't decrypt (rather than reply
10779 with an error). It also fixes a wide variety of other bugs.
10782 - If the cached networkstatus consensus is more than five days old,
10783 discard it rather than trying to use it. In theory it could
10784 be useful because it lists alternate directory mirrors, but in
10785 practice it just means we spend many minutes trying directory
10786 mirrors that are long gone from the network. Helps bug 887 a bit;
10788 - Bridge relays that had DirPort set to 0 would stop fetching
10789 descriptors shortly after startup, and then briefly resume
10790 after a new bandwidth test and/or after publishing a new bridge
10791 descriptor. Bridge users that try to bootstrap from them would
10792 get a recent networkstatus but would get descriptors from up to
10793 18 hours earlier, meaning most of the descriptors were obsolete
10794 already. Reported by Tas; bugfix on 0.2.0.13-alpha.
10795 - Prevent bridge relays from serving their 'extrainfo' document
10796 to anybody who asks, now that extrainfo docs include potentially
10797 sensitive aggregated client geoip summaries. Bugfix on
10801 - New controller event "clients_seen" to report a geoip-based summary
10802 of which countries we've seen clients from recently. Now controllers
10803 like Vidalia can show bridge operators that they're actually making
10805 - Build correctly against versions of OpenSSL 0.9.8 or later built
10806 without support for deprecated functions.
10807 - Update to the "December 19 2008" ip-to-country file.
10809 o Minor bugfixes (on 0.2.0.x):
10810 - Authorities now vote for the Stable flag for any router whose
10811 weighted MTBF is at least 5 days, regardless of the mean MTBF.
10812 - Do not remove routers as too old if we do not have any consensus
10813 document. Bugfix on 0.2.0.7-alpha.
10814 - Do not accept incomplete ipv4 addresses (like 192.168.0) as valid.
10815 Spec conformance issue. Bugfix on Tor 0.0.2pre27.
10816 - When an exit relay resolves a stream address to a local IP address,
10817 do not just keep retrying that same exit relay over and
10818 over. Instead, just close the stream. Addresses bug 872. Bugfix
10819 on 0.2.0.32. Patch from rovv.
10820 - If a hidden service sends us an END cell, do not consider
10821 retrying the connection; just close it. Patch from rovv.
10822 - When we made bridge authorities stop serving bridge descriptors over
10823 unencrypted links, we also broke DirPort reachability testing for
10824 bridges. So bridges with a non-zero DirPort were printing spurious
10825 warns to their logs. Bugfix on 0.2.0.16-alpha. Fixes bug 709.
10826 - When a relay gets a create cell it can't decrypt (e.g. because it's
10827 using the wrong onion key), we were dropping it and letting the
10828 client time out. Now actually answer with a destroy cell. Fixes
10829 bug 904. Bugfix on 0.0.2pre8.
10830 - Squeeze 2-5% out of client performance (according to oprofile) by
10831 improving the implementation of some policy-manipulation functions.
10833 o Minor bugfixes (on 0.2.1.x):
10834 - Make get_interface_address() function work properly again; stop
10835 guessing the wrong parts of our address as our address.
10836 - Do not cannibalize a circuit if we're out of RELAY_EARLY cells to
10837 send on that circuit. Otherwise we might violate the proposal-110
10838 limit. Bugfix on 0.2.1.3-alpha. Partial fix for bug 878. Diagnosis
10840 - When we're sending non-EXTEND cells to the first hop in a circuit,
10841 for example to use an encrypted directory connection, we don't need
10842 to use RELAY_EARLY cells: the first hop knows what kind of cell
10843 it is, and nobody else can even see the cell type. Conserving
10844 RELAY_EARLY cells makes it easier to cannibalize circuits like
10846 - Stop logging nameserver addresses in reverse order.
10847 - If we are retrying a directory download slowly over and over, do
10848 not automatically give up after the 254th failure. Bugfix on
10850 - Resume reporting accurate "stream end" reasons to the local control
10851 port. They were lost in the changes for Proposal 148. Bugfix on
10854 o Deprecated and removed features:
10855 - The old "tor --version --version" command, which would print out
10856 the subversion "Id" of most of the source files, is now removed. It
10857 turned out to be less useful than we'd expected, and harder to
10860 o Code simplifications and refactoring:
10861 - Change our header file guard macros to be less likely to conflict
10862 with system headers. Adam Langley noticed that we were conflicting
10863 with log.h on Android.
10864 - Tool-assisted documentation cleanup. Nearly every function or
10865 static variable in Tor should have its own documentation now.
10868 Changes in version 0.2.1.9-alpha - 2008-12-25
10869 Tor 0.2.1.9-alpha fixes many more bugs, some of them security-related.
10871 o New directory authorities:
10872 - gabelmoo (the authority run by Karsten Loesing) now has a new
10876 - Never use a connection with a mismatched address to extend a
10877 circuit, unless that connection is canonical. A canonical
10878 connection is one whose address is authenticated by the router's
10879 identity key, either in a NETINFO cell or in a router descriptor.
10880 - Avoid a possible memory corruption bug when receiving hidden service
10881 descriptors. Bugfix on 0.2.1.6-alpha.
10884 - Fix a logic error that would automatically reject all but the first
10885 configured DNS server. Bugfix on 0.2.1.5-alpha. Possible fix for
10886 part of bug 813/868. Bug spotted by coderman.
10887 - When a stream at an exit relay is in state "resolving" or
10888 "connecting" and it receives an "end" relay cell, the exit relay
10889 would silently ignore the end cell and not close the stream. If
10890 the client never closes the circuit, then the exit relay never
10891 closes the TCP connection. Bug introduced in 0.1.2.1-alpha;
10892 reported by "wood".
10893 - When we can't initialize DNS because the network is down, do not
10894 automatically stop Tor from starting. Instead, retry failed
10895 dns_init() every 10 minutes, and change the exit policy to reject
10896 *:* until one succeeds. Fixes bug 691.
10899 - Give a better error message when an overzealous init script says
10900 "sudo -u username tor --user username". Makes Bug 882 easier for
10902 - When a directory authority gives us a new guess for our IP address,
10903 log which authority we used. Hopefully this will help us debug
10904 the recent complaints about bad IP address guesses.
10905 - Detect svn revision properly when we're using git-svn.
10906 - Try not to open more than one descriptor-downloading connection
10907 to an authority at once. This should reduce load on directory
10908 authorities. Fixes bug 366.
10909 - Add cross-certification to newly generated certificates, so that
10910 a signing key is enough information to look up a certificate.
10911 Partial implementation of proposal 157.
10912 - Start serving certificates by <identity digest, signing key digest>
10913 pairs. Partial implementation of proposal 157.
10914 - Clients now never report any stream end reason except 'MISC'.
10915 Implements proposal 148.
10916 - On platforms with a maximum syslog string length, truncate syslog
10917 messages to that length ourselves, rather than relying on the
10918 system to do it for us.
10919 - Optimize out calls to time(NULL) that occur for every IO operation,
10920 or for every cell. On systems where time() is a slow syscall,
10921 this fix will be slightly helpful.
10922 - Exit servers can now answer resolve requests for ip6.arpa addresses.
10923 - When we download a descriptor that we then immediately (as
10924 a directory authority) reject, do not retry downloading it right
10925 away. Should save some bandwidth on authorities. Fix for bug
10926 888. Patch by Sebastian Hahn.
10927 - When a download gets us zero good descriptors, do not notify
10928 Tor that new directory information has arrived.
10929 - Avoid some nasty corner cases in the logic for marking connections
10930 as too old or obsolete or noncanonical for circuits. Partial
10933 o Minor features (controller):
10934 - New CONSENSUS_ARRIVED event to note when a new consensus has
10935 been fetched and validated.
10936 - When we realize that another process has modified our cached
10937 descriptors file, print out a more useful error message rather
10938 than triggering an assertion. Fixes bug 885. Patch from Karsten.
10939 - Add an internal-use-only __ReloadTorrcOnSIGHUP option for
10940 controllers to prevent SIGHUP from reloading the
10941 configuration. Fixes bug 856.
10944 - Resume using the correct "REASON=" stream when telling the
10945 controller why we closed a stream. Bugfix in 0.2.1.1-alpha.
10946 - When a canonical connection appears later in our internal list
10947 than a noncanonical one for a given OR ID, always use the
10948 canonical one. Bugfix on 0.2.0.12-alpha. Fixes bug 805.
10950 - Clip the MaxCircuitDirtiness config option to a minimum of 10
10951 seconds. Warn the user if lower values are given in the
10952 configuration. Bugfix on 0.1.0.1-rc. Patch by Sebastian.
10953 - Clip the CircuitBuildTimeout to a minimum of 30 seconds. Warn the
10954 user if lower values are given in the configuration. Bugfix on
10955 0.1.1.17-rc. Patch by Sebastian.
10956 - Fix a race condition when freeing keys shared between main thread
10957 and CPU workers that could result in a memory leak. Bugfix on
10958 0.1.0.1-rc. Fixes bug 889.
10960 o Minor bugfixes (hidden services):
10961 - Do not throw away existing introduction points on SIGHUP (bugfix on
10962 0.0.6pre1); also, do not stall hidden services because we're
10963 throwing away introduction points; bugfix on 0.2.1.7-alpha. Spotted
10964 by John Brooks. Patch by Karsten. Fixes bug 874.
10965 - Fix a memory leak when we decline to add a v2 rendezvous
10966 descriptor to the cache because we already had a v0 descriptor
10967 with the same ID. Bugfix on 0.2.0.18-alpha.
10969 o Deprecated and removed features:
10970 - RedirectExits has been removed. It was deprecated since
10972 - Finally remove deprecated "EXTENDED_FORMAT" controller feature. It
10973 has been called EXTENDED_EVENTS since 0.1.2.4-alpha.
10974 - Cell pools are now always enabled; --disable-cell-pools is ignored.
10976 o Code simplifications and refactoring:
10977 - Rename the confusing or_is_obsolete field to the more appropriate
10978 is_bad_for_new_circs, and move it to or_connection_t where it
10980 - Move edge-only flags from connection_t to edge_connection_t: not
10981 only is this better coding, but on machines of plausible alignment,
10982 it should save 4-8 bytes per connection_t. "Every little bit helps."
10983 - Rename ServerDNSAllowBrokenResolvConf to ServerDNSAllowBrokenConfig
10984 for consistency; keep old option working for backward compatibility.
10985 - Simplify the code for finding connections to use for a circuit.
10988 Changes in version 0.2.1.8-alpha - 2008-12-08
10989 Tor 0.2.1.8-alpha fixes some crash bugs in earlier alpha releases,
10990 builds better on unusual platforms like Solaris and old OS X, and
10991 fixes a variety of other issues.
10994 - New DirPortFrontPage option that takes an html file and publishes
10995 it as "/" on the DirPort. Now relay operators can provide a
10996 disclaimer without needing to set up a separate webserver. There's
10997 a sample disclaimer in contrib/tor-exit-notice.html.
11000 - When the client is choosing entry guards, now it selects at most
11001 one guard from a given relay family. Otherwise we could end up with
11002 all of our entry points into the network run by the same operator.
11003 Suggested by Camilo Viecco. Fix on 0.1.1.11-alpha.
11006 - Fix a DOS opportunity during the voting signature collection process
11007 at directory authorities. Spotted by rovv. Bugfix on 0.2.0.x.
11008 - Fix a possible segfault when establishing an exit connection. Bugfix
11012 - Get file locking working on win32. Bugfix on 0.2.1.6-alpha. Fixes
11014 - Made Tor a little less aggressive about deleting expired
11015 certificates. Partial fix for bug 854.
11016 - Stop doing unaligned memory access that generated bus errors on
11017 sparc64. Bugfix on 0.2.0.10-alpha. Fix for bug 862.
11018 - Fix a crash bug when changing EntryNodes from the controller. Bugfix
11019 on 0.2.1.6-alpha. Fix for bug 867. Patched by Sebastian.
11020 - Make USR2 log-level switch take effect immediately. Bugfix on
11022 - If one win32 nameserver fails to get added, continue adding the
11023 rest, and don't automatically fail.
11024 - Use fcntl() for locking when flock() is not available. Should fix
11025 compilation on Solaris. Should fix Bug 873. Bugfix on 0.2.1.6-alpha.
11026 - Do not mark smartlist_bsearch_idx() function as ATTR_PURE. This bug
11027 could make gcc generate non-functional binary search code. Bugfix
11029 - Build correctly on platforms without socklen_t.
11030 - Avoid potential crash on internal error during signature collection.
11031 Fixes bug 864. Patch from rovv.
11032 - Do not use C's stdio library for writing to log files. This will
11033 improve logging performance by a minute amount, and will stop
11034 leaking fds when our disk is full. Fixes bug 861.
11035 - Stop erroneous use of O_APPEND in cases where we did not in fact
11036 want to re-seek to the end of a file before every last write().
11037 - Correct handling of possible malformed authority signing key
11038 certificates with internal signature types. Fixes bug 880. Bugfix
11040 - Fix a hard-to-trigger resource leak when logging credential status.
11044 - Directory mirrors no longer fetch the v1 directory or
11045 running-routers files. They are obsolete, and nobody asks for them
11046 anymore. This is the first step to making v1 authorities obsolete.
11048 o Minor features (controller):
11049 - Return circuit purposes in response to GETINFO circuit-status. Fixes
11053 Changes in version 0.2.0.32 - 2008-11-20
11054 Tor 0.2.0.32 fixes a major security problem in Debian and Ubuntu
11055 packages (and maybe other packages) noticed by Theo de Raadt, fixes
11056 a smaller security flaw that might allow an attacker to access local
11057 services, further improves hidden service performance, and fixes a
11058 variety of other issues.
11061 - The "User" and "Group" config options did not clear the
11062 supplementary group entries for the Tor process. The "User" option
11063 is now more robust, and we now set the groups to the specified
11064 user's primary group. The "Group" option is now ignored. For more
11065 detailed logging on credential switching, set CREDENTIAL_LOG_LEVEL
11066 in common/compat.c to LOG_NOTICE or higher. Patch by Jacob Appelbaum
11067 and Steven Murdoch. Bugfix on 0.0.2pre14. Fixes bug 848 and 857.
11068 - The "ClientDNSRejectInternalAddresses" config option wasn't being
11069 consistently obeyed: if an exit relay refuses a stream because its
11070 exit policy doesn't allow it, we would remember what IP address
11071 the relay said the destination address resolves to, even if it's
11072 an internal IP address. Bugfix on 0.2.0.7-alpha; patch by rovv.
11075 - Fix a DOS opportunity during the voting signature collection process
11076 at directory authorities. Spotted by rovv. Bugfix on 0.2.0.x.
11078 o Major bugfixes (hidden services):
11079 - When fetching v0 and v2 rendezvous service descriptors in parallel,
11080 we were failing the whole hidden service request when the v0
11081 descriptor fetch fails, even if the v2 fetch is still pending and
11082 might succeed. Similarly, if the last v2 fetch fails, we were
11083 failing the whole hidden service request even if a v0 fetch is
11084 still pending. Fixes bug 814. Bugfix on 0.2.0.10-alpha.
11085 - When extending a circuit to a hidden service directory to upload a
11086 rendezvous descriptor using a BEGIN_DIR cell, almost 1/6 of all
11087 requests failed, because the router descriptor has not been
11088 downloaded yet. In these cases, do not attempt to upload the
11089 rendezvous descriptor, but wait until the router descriptor is
11090 downloaded and retry. Likewise, do not attempt to fetch a rendezvous
11091 descriptor from a hidden service directory for which the router
11092 descriptor has not yet been downloaded. Fixes bug 767. Bugfix
11096 - Fix several infrequent memory leaks spotted by Coverity.
11097 - When testing for libevent functions, set the LDFLAGS variable
11098 correctly. Found by Riastradh.
11099 - Avoid a bug where the FastFirstHopPK 0 option would keep Tor from
11100 bootstrapping with tunneled directory connections. Bugfix on
11101 0.1.2.5-alpha. Fixes bug 797. Found by Erwin Lam.
11102 - When asked to connect to A.B.exit:80, if we don't know the IP for A
11103 and we know that server B rejects most-but-not all connections to
11104 port 80, we would previously reject the connection. Now, we assume
11105 the user knows what they were asking for. Fixes bug 752. Bugfix
11106 on 0.0.9rc5. Diagnosed by BarkerJr.
11107 - If we overrun our per-second write limits a little, count this as
11108 having used up our write allocation for the second, and choke
11109 outgoing directory writes. Previously, we had only counted this when
11110 we had met our limits precisely. Fixes bug 824. Patch from by rovv.
11111 Bugfix on 0.2.0.x (??).
11112 - Remove the old v2 directory authority 'lefkada' from the default
11113 list. It has been gone for many months.
11114 - Stop doing unaligned memory access that generated bus errors on
11115 sparc64. Bugfix on 0.2.0.10-alpha. Fixes bug 862.
11116 - Make USR2 log-level switch take effect immediately. Bugfix on
11119 o Minor bugfixes (controller):
11120 - Make DNS resolved events into "CLOSED", not "FAILED". Bugfix on
11121 0.1.2.5-alpha. Fix by Robert Hogan. Resolves bug 807.
11124 Changes in version 0.2.1.7-alpha - 2008-11-08
11125 Tor 0.2.1.7-alpha fixes a major security problem in Debian and Ubuntu
11126 packages (and maybe other packages) noticed by Theo de Raadt, fixes
11127 a smaller security flaw that might allow an attacker to access local
11128 services, adds better defense against DNS poisoning attacks on exit
11129 relays, further improves hidden service performance, and fixes a
11130 variety of other issues.
11133 - The "ClientDNSRejectInternalAddresses" config option wasn't being
11134 consistently obeyed: if an exit relay refuses a stream because its
11135 exit policy doesn't allow it, we would remember what IP address
11136 the relay said the destination address resolves to, even if it's
11137 an internal IP address. Bugfix on 0.2.0.7-alpha; patch by rovv.
11138 - The "User" and "Group" config options did not clear the
11139 supplementary group entries for the Tor process. The "User" option
11140 is now more robust, and we now set the groups to the specified
11141 user's primary group. The "Group" option is now ignored. For more
11142 detailed logging on credential switching, set CREDENTIAL_LOG_LEVEL
11143 in common/compat.c to LOG_NOTICE or higher. Patch by Jacob Appelbaum
11144 and Steven Murdoch. Bugfix on 0.0.2pre14. Fixes bug 848.
11145 - Do not use or believe expired v3 authority certificates. Patch
11146 from Karsten. Bugfix in 0.2.0.x. Fixes bug 851.
11149 - Now NodeFamily and MyFamily config options allow spaces in
11150 identity fingerprints, so it's easier to paste them in.
11151 Suggested by Lucky Green.
11152 - Implement the 0x20 hack to better resist DNS poisoning: set the
11153 case on outgoing DNS requests randomly, and reject responses that do
11154 not match the case correctly. This logic can be disabled with the
11155 ServerDNSRandomizeCase setting, if you are using one of the 0.3%
11156 of servers that do not reliably preserve case in replies. See
11157 "Increased DNS Forgery Resistance through 0x20-Bit Encoding"
11159 - Preserve case in replies to DNSPort requests in order to support
11160 the 0x20 hack for resisting DNS poisoning attacks.
11162 o Hidden service performance improvements:
11163 - When the client launches an introduction circuit, retry with a
11164 new circuit after 30 seconds rather than 60 seconds.
11165 - Launch a second client-side introduction circuit in parallel
11166 after a delay of 15 seconds (based on work by Christian Wilms).
11167 - Hidden services start out building five intro circuits rather
11168 than three, and when the first three finish they publish a service
11169 descriptor using those. Now we publish our service descriptor much
11170 faster after restart.
11173 - Minor fix in the warning messages when you're having problems
11174 bootstrapping; also, be more forgiving of bootstrap problems when
11175 we're still making incremental progress on a given bootstrap phase.
11176 - When we're choosing an exit node for a circuit, and we have
11177 no pending streams, choose a good general exit rather than one that
11178 supports "all the pending streams". Bugfix on 0.1.1.x. Fix by rovv.
11179 - Send a valid END cell back when a client tries to connect to a
11180 nonexistent hidden service port. Bugfix on 0.1.2.15. Fixes bug
11181 840. Patch from rovv.
11182 - If a broken client asks a non-exit router to connect somewhere,
11183 do not even do the DNS lookup before rejecting the connection.
11184 Fixes another case of bug 619. Patch from rovv.
11185 - Fix another case of assuming, when a specific exit is requested,
11186 that we know more than the user about what hosts it allows.
11187 Fixes another case of bug 752. Patch from rovv.
11188 - Check which hops rendezvous stream cells are associated with to
11189 prevent possible guess-the-streamid injection attacks from
11190 intermediate hops. Fixes another case of bug 446. Based on patch
11192 - Avoid using a negative right-shift when comparing 32-bit
11193 addresses. Possible fix for bug 845 and bug 811.
11194 - Make the assert_circuit_ok() function work correctly on circuits that
11195 have already been marked for close.
11196 - Fix read-off-the-end-of-string error in unit tests when decoding
11197 introduction points.
11198 - Fix uninitialized size field for memory area allocation: may improve
11199 memory performance during directory parsing.
11200 - Treat duplicate certificate fetches as failures, so that we do
11201 not try to re-fetch an expired certificate over and over and over.
11202 - Do not say we're fetching a certificate when we'll in fact skip it
11203 because of a pending download.
11206 Changes in version 0.2.1.6-alpha - 2008-09-30
11207 Tor 0.2.1.6-alpha further improves performance and robustness of
11208 hidden services, starts work on supporting per-country relay selection,
11209 and fixes a variety of smaller issues.
11212 - Implement proposal 121: make it possible to build hidden services
11213 that only certain clients are allowed to connect to. This is
11214 enforced at several points, so that unauthorized clients are unable
11215 to send INTRODUCE cells to the service, or even (depending on the
11216 type of authentication) to learn introduction points. This feature
11217 raises the bar for certain kinds of active attacks against hidden
11218 services. Code by Karsten Loesing.
11219 - Relays now store and serve v2 hidden service descriptors by default,
11220 i.e., the new default value for HidServDirectoryV2 is 1. This is
11221 the last step in proposal 114, which aims to make hidden service
11222 lookups more reliable.
11223 - Start work to allow node restrictions to include country codes. The
11224 syntax to exclude nodes in a country with country code XX is
11225 "ExcludeNodes {XX}". Patch from Robert Hogan. It still needs some
11226 refinement to decide what config options should take priority if
11227 you ask to both use a particular node and exclude it.
11228 - Allow ExitNodes list to include IP ranges and country codes, just
11229 like the Exclude*Nodes lists. Patch from Robert Hogan.
11232 - Fix a bug when parsing ports in tor_addr_port_parse() that caused
11233 Tor to fail to start if you had it configured to use a bridge
11234 relay. Fixes bug 809. Bugfix on 0.2.1.5-alpha.
11235 - When extending a circuit to a hidden service directory to upload a
11236 rendezvous descriptor using a BEGIN_DIR cell, almost 1/6 of all
11237 requests failed, because the router descriptor had not been
11238 downloaded yet. In these cases, we now wait until the router
11239 descriptor is downloaded, and then retry. Likewise, clients
11240 now skip over a hidden service directory if they don't yet have
11241 its router descriptor, rather than futilely requesting it and
11242 putting mysterious complaints in the logs. Fixes bug 767. Bugfix
11244 - When fetching v0 and v2 rendezvous service descriptors in parallel,
11245 we were failing the whole hidden service request when the v0
11246 descriptor fetch fails, even if the v2 fetch is still pending and
11247 might succeed. Similarly, if the last v2 fetch fails, we were
11248 failing the whole hidden service request even if a v0 fetch is
11249 still pending. Fixes bug 814. Bugfix on 0.2.0.10-alpha.
11250 - DNS replies need to have names matching their requests, but
11251 these names should be in the questions section, not necessarily
11252 in the answers section. Fixes bug 823. Bugfix on 0.2.1.5-alpha.
11255 - Update to the "September 1 2008" ip-to-country file.
11256 - Allow ports 465 and 587 in the default exit policy again. We had
11257 rejected them in 0.1.0.15, because back in 2005 they were commonly
11258 misconfigured and ended up as spam targets. We hear they are better
11259 locked down these days.
11260 - Use a lockfile to make sure that two Tor processes are not
11261 simultaneously running with the same datadir.
11262 - Serve the latest v3 networkstatus consensus via the control
11263 port. Use "getinfo dir/status-vote/current/consensus" to fetch it.
11264 - Better logging about stability/reliability calculations on directory
11266 - Drop the requirement to have an open dir port for storing and
11267 serving v2 hidden service descriptors.
11268 - Directory authorities now serve a /tor/dbg-stability.txt URL to
11269 help debug WFU and MTBF calculations.
11270 - Implement most of Proposal 152: allow specialized servers to permit
11271 single-hop circuits, and clients to use those servers to build
11272 single-hop circuits when using a specialized controller. Patch
11273 from Josh Albrecht. Resolves feature request 768.
11274 - Add a -p option to tor-resolve for specifying the SOCKS port: some
11275 people find host:port too confusing.
11276 - Make TrackHostExit mappings expire a while after their last use, not
11277 after their creation. Patch from Robert Hogan.
11278 - Provide circuit purposes along with circuit events to the controller.
11281 - Fix compile on OpenBSD 4.4-current. Bugfix on 0.2.1.5-alpha.
11283 - Fixed some memory leaks -- some quite frequent, some almost
11284 impossible to trigger -- based on results from Coverity.
11285 - When testing for libevent functions, set the LDFLAGS variable
11286 correctly. Found by Riastradh.
11287 - Fix an assertion bug in parsing policy-related options; possible fix
11289 - Catch and report a few more bootstrapping failure cases when Tor
11290 fails to establish a TCP connection. Cleanup on 0.2.1.x.
11291 - Avoid a bug where the FastFirstHopPK 0 option would keep Tor from
11292 bootstrapping with tunneled directory connections. Bugfix on
11293 0.1.2.5-alpha. Fixes bug 797. Found by Erwin Lam.
11294 - When asked to connect to A.B.exit:80, if we don't know the IP for A
11295 and we know that server B rejects most-but-not all connections to
11296 port 80, we would previously reject the connection. Now, we assume
11297 the user knows what they were asking for. Fixes bug 752. Bugfix
11298 on 0.0.9rc5. Diagnosed by BarkerJr.
11299 - If we are not using BEGIN_DIR cells, don't attempt to contact hidden
11300 service directories if they have no advertised dir port. Bugfix
11302 - If we overrun our per-second write limits a little, count this as
11303 having used up our write allocation for the second, and choke
11304 outgoing directory writes. Previously, we had only counted this when
11305 we had met our limits precisely. Fixes bug 824. Patch by rovv.
11306 Bugfix on 0.2.0.x (??).
11307 - Avoid a "0 divided by 0" calculation when calculating router uptime
11308 at directory authorities. Bugfix on 0.2.0.8-alpha.
11309 - Make DNS resolved controller events into "CLOSED", not
11310 "FAILED". Bugfix on 0.1.2.5-alpha. Fix by Robert Hogan. Resolves
11312 - Fix a bug where an unreachable relay would establish enough
11313 reachability testing circuits to do a bandwidth test -- if
11314 we already have a connection to the middle hop of the testing
11315 circuit, then it could establish the last hop by using the existing
11316 connection. Bugfix on 0.1.2.2-alpha, exposed when we made testing
11317 circuits no longer use entry guards in 0.2.1.3-alpha.
11318 - If we have correct permissions on $datadir, we complain to stdout
11319 and fail to start. But dangerous permissions on
11320 $datadir/cached-status/ would cause us to open a log and complain
11321 there. Now complain to stdout and fail to start in both cases. Fixes
11322 bug 820, reported by seeess.
11323 - Remove the old v2 directory authority 'lefkada' from the default
11324 list. It has been gone for many months.
11326 o Code simplifications and refactoring:
11327 - Revise the connection_new functions so that a more typesafe variant
11328 exists. This will work better with Coverity, and let us find any
11329 actual mistakes we're making here.
11330 - Refactor unit testing logic so that dmalloc can be used sensibly
11331 with unit tests to check for memory leaks.
11332 - Move all hidden-service related fields from connection and circuit
11333 structure to substructures: this way they won't eat so much memory.
11336 Changes in version 0.2.0.31 - 2008-09-03
11337 Tor 0.2.0.31 addresses two potential anonymity issues, starts to fix
11338 a big bug we're seeing where in rare cases traffic from one Tor stream
11339 gets mixed into another stream, and fixes a variety of smaller issues.
11342 - Make sure that two circuits can never exist on the same connection
11343 with the same circuit ID, even if one is marked for close. This
11344 is conceivably a bugfix for bug 779. Bugfix on 0.1.0.4-rc.
11345 - Relays now reject risky extend cells: if the extend cell includes
11346 a digest of all zeroes, or asks to extend back to the relay that
11347 sent the extend cell, tear down the circuit. Ideas suggested
11349 - If not enough of our entry guards are available so we add a new
11350 one, we might use the new one even if it overlapped with the
11351 current circuit's exit relay (or its family). Anonymity bugfix
11352 pointed out by rovv.
11355 - Recover 3-7 bytes that were wasted per memory chunk. Fixes bug
11356 794; bug spotted by rovv. Bugfix on 0.2.0.1-alpha.
11357 - Correctly detect the presence of the linux/netfilter_ipv4.h header
11358 when building against recent kernels. Bugfix on 0.1.2.1-alpha.
11359 - Pick size of default geoip filename string correctly on windows.
11360 Fixes bug 806. Bugfix on 0.2.0.30.
11361 - Make the autoconf script accept the obsolete --with-ssl-dir
11362 option as an alias for the actually-working --with-openssl-dir
11363 option. Fix the help documentation to recommend --with-openssl-dir.
11364 Based on a patch by "Dave". Bugfix on 0.2.0.1-alpha.
11365 - When using the TransPort option on OpenBSD, and using the User
11366 option to change UID and drop privileges, make sure to open
11367 /dev/pf before dropping privileges. Fixes bug 782. Patch from
11368 Christopher Davis. Bugfix on 0.1.2.1-alpha.
11369 - Try to attach connections immediately upon receiving a RENDEZVOUS2
11370 or RENDEZVOUS_ESTABLISHED cell. This can save a second or two
11371 on the client side when connecting to a hidden service. Bugfix
11372 on 0.0.6pre1. Found and fixed by Christian Wilms; resolves bug 743.
11373 - When closing an application-side connection because its circuit is
11374 getting torn down, generate the stream event correctly. Bugfix on
11375 0.1.2.x. Anonymous patch.
11378 Changes in version 0.2.1.5-alpha - 2008-08-31
11379 Tor 0.2.1.5-alpha moves us closer to handling IPv6 destinations, puts
11380 in a lot of the infrastructure for adding authorization to hidden
11381 services, lays the groundwork for having clients read their load
11382 balancing information out of the networkstatus consensus rather than
11383 the individual router descriptors, addresses two potential anonymity
11384 issues, and fixes a variety of smaller issues.
11387 - Convert many internal address representations to optionally hold
11389 - Generate and accept IPv6 addresses in many protocol elements.
11390 - Make resolver code handle nameservers located at ipv6 addresses.
11391 - Begin implementation of proposal 121 ("Client authorization for
11392 hidden services"): configure hidden services with client
11393 authorization, publish descriptors for them, and configure
11394 authorization data for hidden services at clients. The next
11395 step is to actually access hidden services that perform client
11397 - More progress toward proposal 141: Network status consensus
11398 documents and votes now contain bandwidth information for each
11399 router and a summary of that router's exit policy. Eventually this
11400 will be used by clients so that they do not have to download every
11401 known descriptor before building circuits.
11403 o Major bugfixes (on 0.2.0.x and before):
11404 - When sending CREATED cells back for a given circuit, use a 64-bit
11405 connection ID to find the right connection, rather than an addr:port
11406 combination. Now that we can have multiple OR connections between
11407 the same ORs, it is no longer possible to use addr:port to uniquely
11408 identify a connection.
11409 - Relays now reject risky extend cells: if the extend cell includes
11410 a digest of all zeroes, or asks to extend back to the relay that
11411 sent the extend cell, tear down the circuit. Ideas suggested
11413 - If not enough of our entry guards are available so we add a new
11414 one, we might use the new one even if it overlapped with the
11415 current circuit's exit relay (or its family). Anonymity bugfix
11416 pointed out by rovv.
11419 - Recover 3-7 bytes that were wasted per memory chunk. Fixes bug
11420 794; bug spotted by rovv. Bugfix on 0.2.0.1-alpha.
11421 - When using the TransPort option on OpenBSD, and using the User
11422 option to change UID and drop privileges, make sure to open /dev/pf
11423 before dropping privileges. Fixes bug 782. Patch from Christopher
11424 Davis. Bugfix on 0.1.2.1-alpha.
11425 - Correctly detect the presence of the linux/netfilter_ipv4.h header
11426 when building against recent kernels. Bugfix on 0.1.2.1-alpha.
11427 - Add a missing safe_str() call for a debug log message.
11428 - Use 64 bits instead of 32 bits for connection identifiers used with
11429 the controller protocol, to greatly reduce risk of identifier reuse.
11430 - Make the autoconf script accept the obsolete --with-ssl-dir
11431 option as an alias for the actually-working --with-openssl-dir
11432 option. Fix the help documentation to recommend --with-openssl-dir.
11433 Based on a patch by "Dave". Bugfix on 0.2.0.1-alpha.
11436 - Rate-limit too-many-sockets messages: when they happen, they happen
11437 a lot. Resolves bug 748.
11438 - Resist DNS poisoning a little better by making sure that names in
11439 answer sections match.
11440 - Print the SOCKS5 error message string as well as the error code
11441 when a tor-resolve request fails. Patch from Jacob.
11444 Changes in version 0.2.1.4-alpha - 2008-08-04
11445 Tor 0.2.1.4-alpha fixes a pair of crash bugs in 0.2.1.3-alpha.
11448 - The address part of exit policies was not correctly written
11449 to router descriptors. This generated router descriptors that failed
11450 their self-checks. Noticed by phobos, fixed by Karsten. Bugfix
11452 - Tor triggered a false assert when extending a circuit to a relay
11453 but we already have a connection open to that relay. Noticed by
11454 phobos, fixed by Karsten. Bugfix on 0.2.1.3-alpha.
11457 - Fix a hidden service logging bug: in some edge cases, the router
11458 descriptor of a previously picked introduction point becomes
11459 obsolete and we need to give up on it rather than continually
11460 complaining that it has become obsolete. Observed by xiando. Bugfix
11463 o Removed features:
11464 - Take out the TestVia config option, since it was a workaround for
11465 a bug that was fixed in Tor 0.1.1.21.
11468 Changes in version 0.2.1.3-alpha - 2008-08-03
11469 Tor 0.2.1.3-alpha implements most of the pieces to prevent
11470 infinite-length circuit attacks (see proposal 110); fixes a bug that
11471 might cause exit relays to corrupt streams they send back; allows
11472 address patterns (e.g. 255.128.0.0/16) to appear in ExcludeNodes and
11473 ExcludeExitNodes config options; and fixes a big pile of bugs.
11475 o Bootstrapping bugfixes (on 0.2.1.x-alpha):
11476 - Send a bootstrap problem "warn" event on the first problem if the
11477 reason is NO_ROUTE (that is, our network is down).
11480 - Implement most of proposal 110: The first K cells to be sent
11481 along a circuit are marked as special "early" cells; only K "early"
11482 cells will be allowed. Once this code is universal, we can block
11483 certain kinds of DOS attack by requiring that EXTEND commands must
11484 be sent using an "early" cell.
11487 - Try to attach connections immediately upon receiving a RENDEZVOUS2
11488 or RENDEZVOUS_ESTABLISHED cell. This can save a second or two
11489 on the client side when connecting to a hidden service. Bugfix
11490 on 0.0.6pre1. Found and fixed by Christian Wilms; resolves bug 743.
11491 - Ensure that two circuits can never exist on the same connection
11492 with the same circuit ID, even if one is marked for close. This
11493 is conceivably a bugfix for bug 779; fixes a bug on 0.1.0.4-rc.
11496 - When relays do their initial bandwidth measurement, don't limit
11497 to just our entry guards for the test circuits. Otherwise we tend
11498 to have multiple test circuits going through a single entry guard,
11499 which makes our bandwidth test less accurate. Fixes part of bug 654;
11500 patch contributed by Josh Albrecht.
11501 - Add an ExcludeExitNodes option so users can list a set of nodes
11502 that should be be excluded from the exit node position, but
11503 allowed elsewhere. Implements proposal 151.
11504 - Allow address patterns (e.g., 255.128.0.0/16) to appear in
11505 ExcludeNodes and ExcludeExitNodes lists.
11506 - Change the implementation of ExcludeNodes and ExcludeExitNodes to
11507 be more efficient. Formerly it was quadratic in the number of
11508 servers; now it should be linear. Fixes bug 509.
11509 - Save 16-22 bytes per open circuit by moving the n_addr, n_port,
11510 and n_conn_id_digest fields into a separate structure that's
11511 only needed when the circuit has not yet attached to an n_conn.
11514 - Change the contrib/tor.logrotate script so it makes the new
11515 logs as "_tor:_tor" rather than the default, which is generally
11516 "root:wheel". Fixes bug 676, reported by Serge Koksharov.
11517 - Stop using __attribute__((nonnull)) with GCC: it can give us useful
11518 warnings (occasionally), but it can also cause the compiler to
11519 eliminate error-checking code. Suggested by Peter Gutmann.
11520 - When a hidden service is giving up on an introduction point candidate
11521 that was not included in the last published rendezvous descriptor,
11522 don't reschedule publication of the next descriptor. Fixes bug 763.
11524 - Mark RendNodes, RendExcludeNodes, HiddenServiceNodes, and
11525 HiddenServiceExcludeNodes as obsolete: they never worked properly,
11526 and nobody claims to be using them. Fixes bug 754. Bugfix on
11527 0.1.0.1-rc. Patch from Christian Wilms.
11528 - Fix a small alignment and memory-wasting bug on buffer chunks.
11531 o Minor bugfixes (controller):
11532 - When closing an application-side connection because its circuit
11533 is getting torn down, generate the stream event correctly.
11534 Bugfix on 0.1.2.x. Anonymous patch.
11536 o Removed features:
11537 - Remove all backward-compatibility code to support relays running
11538 versions of Tor so old that they no longer work at all on the
11542 Changes in version 0.2.0.30 - 2008-07-15
11544 - Stop using __attribute__((nonnull)) with GCC: it can give us useful
11545 warnings (occasionally), but it can also cause the compiler to
11546 eliminate error-checking code. Suggested by Peter Gutmann.
11549 Changes in version 0.2.0.29-rc - 2008-07-08
11550 Tor 0.2.0.29-rc fixes two big bugs with using bridges, fixes more
11551 hidden-service performance bugs, and fixes a bunch of smaller bugs.
11554 - If you have more than one bridge but don't know their keys,
11555 you would only launch a request for the descriptor of the first one
11556 on your list. (Tor considered launching requests for the others, but
11557 found that it already had a connection on the way for $0000...0000
11558 so it didn't open another.) Bugfix on 0.2.0.x.
11559 - If you have more than one bridge but don't know their keys, and the
11560 connection to one of the bridges failed, you would cancel all
11561 pending bridge connections. (After all, they all have the same
11562 digest.) Bugfix on 0.2.0.x.
11563 - When a hidden service was trying to establish an introduction point,
11564 and Tor had built circuits preemptively for such purposes, we
11565 were ignoring all the preemptive circuits and launching a new one
11566 instead. Bugfix on 0.2.0.14-alpha.
11567 - When a hidden service was trying to establish an introduction point,
11568 and Tor *did* manage to reuse one of the preemptively built
11569 circuits, it didn't correctly remember which one it used,
11570 so it asked for another one soon after, until there were no
11571 more preemptive circuits, at which point it launched one from
11572 scratch. Bugfix on 0.0.9.x.
11573 - Make directory servers include the X-Your-Address-Is: http header in
11574 their responses even for begin_dir conns. Now clients who only
11575 ever use begin_dir connections still have a way to learn their IP
11576 address. Fixes bug 737; bugfix on 0.2.0.22-rc. Reported by goldy.
11579 - Fix a macro/CPP interaction that was confusing some compilers:
11580 some GCCs don't like #if/#endif pairs inside macro arguments.
11582 - Fix macro collision between OpenSSL 0.9.8h and Windows headers.
11583 Fixes bug 704; fix from Steven Murdoch.
11584 - When opening /dev/null in finish_daemonize(), do not pass the
11585 O_CREAT flag. Fortify was complaining, and correctly so. Fixes
11586 bug 742; fix from Michael Scherer. Bugfix on 0.0.2pre19.
11587 - Correctly detect transparent proxy support on Linux hosts that
11588 require in.h to be included before netfilter_ipv4.h. Patch
11590 - Disallow session resumption attempts during the renegotiation
11591 stage of the v2 handshake protocol. Clients should never be trying
11592 session resumption at this point, but apparently some did, in
11593 ways that caused the handshake to fail. Bugfix on 0.2.0.20-rc. Bug
11594 found by Geoff Goodell.
11597 Changes in version 0.2.1.2-alpha - 2008-06-20
11598 Tor 0.2.1.2-alpha includes a new "TestingTorNetwork" config option to
11599 make it easier to set up your own private Tor network; fixes several
11600 big bugs with using more than one bridge relay; fixes a big bug with
11601 offering hidden services quickly after Tor starts; and uses a better
11602 API for reporting potential bootstrapping problems to the controller.
11605 - New TestingTorNetwork config option to allow adjustment of
11606 previously constant values that, while reasonable, could slow
11607 bootstrapping. Implements proposal 135. Patch from Karsten.
11610 - If you have more than one bridge but don't know their digests,
11611 you would only learn a request for the descriptor of the first one
11612 on your list. (Tor considered launching requests for the others, but
11613 found that it already had a connection on the way for $0000...0000
11614 so it didn't open another.) Bugfix on 0.2.0.x.
11615 - If you have more than one bridge but don't know their digests,
11616 and the connection to one of the bridges failed, you would cancel
11617 all pending bridge connections. (After all, they all have the
11618 same digest.) Bugfix on 0.2.0.x.
11619 - When establishing a hidden service, introduction points that
11620 originate from cannibalized circuits are completely ignored and not
11621 included in rendezvous service descriptors. This might be another
11622 reason for delay in making a hidden service available. Bugfix
11623 from long ago (0.0.9.x?)
11626 - Allow OpenSSL to use dynamic locks if it wants.
11627 - When building a consensus, do not include routers that are down.
11628 This will cut down 30% to 40% on consensus size. Implements
11630 - In directory authorities' approved-routers files, allow
11631 fingerprints with or without space.
11632 - Add a "GETINFO /status/bootstrap-phase" controller option, so the
11633 controller can query our current bootstrap state in case it attaches
11634 partway through and wants to catch up.
11635 - Send an initial "Starting" bootstrap status event, so we have a
11636 state to start out in.
11639 - Asking for a conditional consensus at .../consensus/<fingerprints>
11640 would crash a dirserver if it did not already have a
11641 consensus. Bugfix on 0.2.1.1-alpha.
11642 - Clean up some macro/CPP interactions: some GCC versions don't like
11643 #if/#endif pairs inside macro arguments. Fixes bug 707. Bugfix on
11646 o Bootstrapping bugfixes (on 0.2.1.1-alpha):
11647 - Directory authorities shouldn't complain about bootstrapping
11648 problems just because they do a lot of reachability testing and
11649 some of the connection attempts fail.
11650 - Start sending "count" and "recommendation" key/value pairs in
11651 bootstrap problem status events, so the controller can hear about
11652 problems even before Tor decides they're worth reporting for sure.
11653 - If you're using bridges, generate "bootstrap problem" warnings
11654 as soon as you run out of working bridges, rather than waiting
11655 for ten failures -- which will never happen if you have less than
11657 - If we close our OR connection because there's been a circuit
11658 pending on it for too long, we were telling our bootstrap status
11659 events "REASON=NONE". Now tell them "REASON=TIMEOUT".
11662 Changes in version 0.2.1.1-alpha - 2008-06-13
11663 Tor 0.2.1.1-alpha fixes a lot of memory fragmentation problems that
11664 were making the Tor process bloat especially on Linux; makes our TLS
11665 handshake blend in better; sends "bootstrap phase" status events to
11666 the controller, so it can keep the user informed of progress (and
11667 problems) fetching directory information and establishing circuits;
11668 and adds a variety of smaller features.
11671 - More work on making our TLS handshake blend in: modify the list
11672 of ciphers advertised by OpenSSL in client mode to even more
11673 closely resemble a common web browser. We cheat a little so that
11674 we can advertise ciphers that the locally installed OpenSSL doesn't
11676 - Start sending "bootstrap phase" status events to the controller,
11677 so it can keep the user informed of progress fetching directory
11678 information and establishing circuits. Also inform the controller
11679 if we think we're stuck at a particular bootstrap phase. Implements
11681 - Resume using OpenSSL's RAND_poll() for better (and more portable)
11682 cross-platform entropy collection again. We used to use it, then
11683 stopped using it because of a bug that could crash systems that
11684 called RAND_poll when they had a lot of fds open. It looks like the
11685 bug got fixed in late 2006. Our new behavior is to call RAND_poll()
11686 at startup, and to call RAND_poll() when we reseed later only if
11687 we have a non-buggy OpenSSL version.
11690 - When we choose to abandon a new entry guard because we think our
11691 older ones might be better, close any circuits pending on that
11692 new entry guard connection. This fix should make us recover much
11693 faster when our network is down and then comes back. Bugfix on
11694 0.1.2.8-beta; found by lodger.
11696 o Memory fixes and improvements:
11697 - Add a malloc_good_size implementation to OpenBSD_malloc_linux.c,
11698 to avoid unused RAM in buffer chunks and memory pools.
11699 - Speed up parsing and cut down on memory fragmentation by using
11700 stack-style allocations for parsing directory objects. Previously,
11701 this accounted for over 40% of allocations from within Tor's code
11702 on a typical directory cache.
11703 - Use a Bloom filter rather than a digest-based set to track which
11704 descriptors we need to keep around when we're cleaning out old
11705 router descriptors. This speeds up the computation significantly,
11706 and may reduce fragmentation.
11707 - Reduce the default smartlist size from 32 to 16; it turns out that
11708 most smartlists hold around 8-12 elements tops.
11709 - Make dumpstats() log the fullness and size of openssl-internal
11711 - If the user has applied the experimental SSL_MODE_RELEASE_BUFFERS
11712 patch to their OpenSSL, turn it on to save memory on servers. This
11713 patch will (with any luck) get included in a mainline distribution
11715 - Never use OpenSSL compression: it wastes RAM and CPU trying to
11716 compress cells, which are basically all encrypted, compressed,
11720 - Stop reloading the router list from disk for no reason when we
11721 run out of reachable directory mirrors. Once upon a time reloading
11722 it would set the 'is_running' flag back to 1 for them. It hasn't
11723 done that for a long time.
11724 - In very rare situations new hidden service descriptors were
11725 published earlier than 30 seconds after the last change to the
11726 service. (We currently think that a hidden service descriptor
11727 that's been stable for 30 seconds is worth publishing.)
11730 - Allow separate log levels to be configured for different logging
11731 domains. For example, this allows one to log all notices, warnings,
11732 or errors, plus all memory management messages of level debug or
11733 higher, with: Log [MM] debug-err [*] notice-err file /var/log/tor.
11734 - Add a couple of extra warnings to --enable-gcc-warnings for GCC 4.3,
11735 and stop using a warning that had become unfixably verbose under
11737 - New --hush command-line option similar to --quiet. While --quiet
11738 disables all logging to the console on startup, --hush limits the
11739 output to messages of warning and error severity.
11740 - Servers support a new URL scheme for consensus downloads that
11741 allows the client to specify which authorities are trusted.
11742 The server then only sends the consensus if the client will trust
11743 it. Otherwise a 404 error is sent back. Clients use this
11744 new scheme when the server supports it (meaning it's running
11745 0.2.1.1-alpha or later). Implements proposal 134.
11746 - New configure/torrc options (--enable-geoip-stats,
11747 DirRecordUsageByCountry) to record how many IPs we've served
11748 directory info to in each country code, how many status documents
11749 total we've sent to each country code, and what share of the total
11750 directory requests we should expect to see.
11751 - Use the TLS1 hostname extension to more closely resemble browser
11753 - Lots of new unit tests.
11754 - Add a macro to implement the common pattern of iterating through
11755 two parallel lists in lockstep.
11758 Changes in version 0.2.0.28-rc - 2008-06-13
11759 Tor 0.2.0.28-rc fixes an anonymity-related bug, fixes a hidden-service
11760 performance bug, and fixes a bunch of smaller bugs.
11763 - Fix a bug where, when we were choosing the 'end stream reason' to
11764 put in our relay end cell that we send to the exit relay, Tor
11765 clients on Windows were sometimes sending the wrong 'reason'. The
11766 anonymity problem is that exit relays may be able to guess whether
11767 the client is running Windows, thus helping partition the anonymity
11768 set. Down the road we should stop sending reasons to exit relays,
11769 or otherwise prevent future versions of this bug.
11772 - While setting up a hidden service, some valid introduction circuits
11773 were overlooked and abandoned. This might be the reason for
11774 the long delay in making a hidden service available. Bugfix on
11778 - Update to the "June 9 2008" ip-to-country file.
11779 - Run 'make test' as part of 'make dist', so we stop releasing so
11780 many development snapshots that fail their unit tests.
11783 - When we're checking if we have enough dir info for each relay
11784 to begin establishing circuits, make sure that we actually have
11785 the descriptor listed in the consensus, not just any descriptor.
11787 - Bridge relays no longer print "xx=0" in their extrainfo document
11788 for every single country code in the geoip db. Bugfix on
11790 - Only warn when we fail to load the geoip file if we were planning to
11791 include geoip stats in our extrainfo document. Bugfix on 0.2.0.27-rc.
11792 - If we change our MaxAdvertisedBandwidth and then reload torrc,
11793 Tor won't realize it should publish a new relay descriptor. Fixes
11794 bug 688, reported by mfr. Bugfix on 0.1.2.x.
11795 - When we haven't had any application requests lately, don't bother
11796 logging that we have expired a bunch of descriptors. Bugfix
11798 - Make relay cells written on a connection count as non-padding when
11799 tracking how long a connection has been in use. Bugfix on
11800 0.2.0.1-alpha. Spotted by lodger.
11801 - Fix unit tests in 0.2.0.27-rc.
11802 - Fix compile on Windows.
11805 Changes in version 0.2.0.27-rc - 2008-06-03
11806 Tor 0.2.0.27-rc adds a few features we left out of the earlier
11807 release candidates. In particular, we now include an IP-to-country
11808 GeoIP database, so controllers can easily look up what country a
11809 given relay is in, and so bridge relays can give us some sanitized
11810 summaries about which countries are making use of bridges. (See proposal
11811 126-geoip-fetching.txt for details.)
11814 - Include an IP-to-country GeoIP file in the tarball, so bridge
11815 relays can report sanitized summaries of the usage they're seeing.
11818 - Add a "PURPOSE=" argument to "STREAM NEW" events, as suggested by
11819 Robert Hogan. Fixes the first part of bug 681.
11820 - Make bridge authorities never serve extrainfo docs.
11821 - Add support to detect Libevent versions in the 1.4.x series
11823 - Fix build on gcc 4.3 with --enable-gcc-warnings set.
11824 - Include a new contrib/tor-exit-notice.html file that exit relay
11825 operators can put on their website to help reduce abuse queries.
11828 - When tunneling an encrypted directory connection, and its first
11829 circuit fails, do not leave it unattached and ask the controller
11830 to deal. Fixes the second part of bug 681.
11831 - Make bridge authorities correctly expire old extrainfo documents
11835 Changes in version 0.2.0.26-rc - 2008-05-13
11836 Tor 0.2.0.26-rc fixes a major security vulnerability caused by a bug
11837 in Debian's OpenSSL packages. All users running any 0.2.0.x version
11838 should upgrade, whether they're running Debian or not.
11840 o Major security fixes:
11841 - Use new V3 directory authority keys on the tor26, gabelmoo, and
11842 moria1 V3 directory authorities. The old keys were generated with
11843 a vulnerable version of Debian's OpenSSL package, and must be
11844 considered compromised. Other authorities' keys were not generated
11845 with an affected version of OpenSSL.
11848 - List authority signatures as "unrecognized" based on DirServer
11849 lines, not on cert cache. Bugfix on 0.2.0.x.
11852 - Add a new V3AuthUseLegacyKey option to make it easier for
11853 authorities to change their identity keys if they have to.
11856 Changes in version 0.2.0.25-rc - 2008-04-23
11857 Tor 0.2.0.25-rc makes Tor work again on OS X and certain BSDs.
11860 - Remember to initialize threading before initializing logging.
11861 Otherwise, many BSD-family implementations will crash hard on
11862 startup. Fixes bug 671. Bugfix on 0.2.0.24-rc.
11865 - Authorities correctly free policies on bad servers on
11866 exit. Fixes bug 672. Bugfix on 0.2.0.x.
11869 Changes in version 0.2.0.24-rc - 2008-04-22
11870 Tor 0.2.0.24-rc adds dizum (run by Alex de Joode) as the new sixth
11871 v3 directory authority, makes relays with dynamic IP addresses and no
11872 DirPort notice more quickly when their IP address changes, fixes a few
11873 rare crashes and memory leaks, and fixes a few other miscellaneous bugs.
11875 o New directory authorities:
11876 - Take lefkada out of the list of v3 directory authorities, since
11877 it has been down for months.
11878 - Set up dizum (run by Alex de Joode) as the new sixth v3 directory
11882 - Detect address changes more quickly on non-directory mirror
11883 relays. Bugfix on 0.2.0.18-alpha; fixes bug 652.
11885 o Minor features (security):
11886 - Reject requests for reverse-dns lookup of names that are in
11887 a private address space. Patch from lodger.
11888 - Non-exit relays no longer allow DNS requests. Fixes bug 619. Patch
11891 o Minor bugfixes (crashes):
11892 - Avoid a rare assert that can trigger when Tor doesn't have much
11893 directory information yet and it tries to fetch a v2 hidden
11894 service descriptor. Fixes bug 651, reported by nwf.
11895 - Initialize log mutex before initializing dmalloc. Otherwise,
11896 running with dmalloc would crash. Bugfix on 0.2.0.x-alpha.
11897 - Use recursive pthread mutexes in order to avoid deadlock when
11898 logging debug-level messages to a controller. Bug spotted by nwf,
11899 bugfix on 0.2.0.16-alpha.
11901 o Minor bugfixes (resource management):
11902 - Keep address policies from leaking memory: start their refcount
11903 at 1, not 2. Bugfix on 0.2.0.16-alpha.
11904 - Free authority certificates on exit, so they don't look like memory
11905 leaks. Bugfix on 0.2.0.19-alpha.
11906 - Free static hashtables for policy maps and for TLS connections on
11907 shutdown, so they don't look like memory leaks. Bugfix on 0.2.0.x.
11908 - Avoid allocating extra space when computing consensuses on 64-bit
11909 platforms. Bug spotted by aakova.
11911 o Minor bugfixes (misc):
11912 - Do not read the configuration file when we've only been told to
11913 generate a password hash. Fixes bug 643. Bugfix on 0.0.9pre5. Fix
11914 based on patch from Sebastian Hahn.
11915 - Exit relays that are used as a client can now reach themselves
11916 using the .exit notation, rather than just launching an infinite
11917 pile of circuits. Fixes bug 641. Reported by Sebastian Hahn.
11918 - When attempting to open a logfile fails, tell us why.
11919 - Fix a dumb bug that was preventing us from knowing that we should
11920 preemptively build circuits to handle expected directory requests.
11921 Fixes bug 660. Bugfix on 0.1.2.x.
11922 - Warn less verbosely about clock skew from netinfo cells from
11923 untrusted sources. Fixes bug 663.
11924 - Make controller stream events for DNS requests more consistent,
11925 by adding "new stream" events for DNS requests, and removing
11926 spurious "stream closed" events" for cached reverse resolves.
11927 Patch from mwenge. Fixes bug 646.
11928 - Correctly notify one-hop connections when a circuit build has
11929 failed. Possible fix for bug 669. Found by lodger.
11932 Changes in version 0.2.0.23-rc - 2008-03-24
11933 Tor 0.2.0.23-rc is the fourth release candidate for the 0.2.0 series. It
11934 makes bootstrapping faster if the first directory mirror you contact
11935 is down. The bundles also include the new Vidalia 0.1.2 release.
11938 - When a tunneled directory request is made to a directory server
11939 that's down, notice after 30 seconds rather than 120 seconds. Also,
11940 fail any begindir streams that are pending on it, so they can
11941 retry elsewhere. This was causing multi-minute delays on bootstrap.
11944 Changes in version 0.2.0.22-rc - 2008-03-18
11945 Tor 0.2.0.22-rc is the third release candidate for the 0.2.0 series. It
11946 enables encrypted directory connections by default for non-relays, fixes
11947 some broken TLS behavior we added in 0.2.0.20-rc, and resolves many
11948 other bugs. The bundles also include Vidalia 0.1.1 and Torbutton 1.1.17.
11951 - Enable encrypted directory connections by default for non-relays,
11952 so censor tools that block Tor directory connections based on their
11953 plaintext patterns will no longer work. This means Tor works in
11954 certain censored countries by default again.
11957 - Make sure servers always request certificates from clients during
11958 TLS renegotiation. Reported by lodger; bugfix on 0.2.0.20-rc.
11959 - Do not enter a CPU-eating loop when a connection is closed in
11960 the middle of client-side TLS renegotiation. Fixes bug 622. Bug
11961 diagnosed by lodger; bugfix on 0.2.0.20-rc.
11962 - Fix assertion failure that could occur when a blocked circuit
11963 became unblocked, and it had pending client DNS requests. Bugfix
11964 on 0.2.0.1-alpha. Fixes bug 632.
11966 o Minor bugfixes (on 0.1.2.x):
11967 - Generate "STATUS_SERVER" events rather than misspelled
11968 "STATUS_SEVER" events. Caught by mwenge.
11969 - When counting the number of bytes written on a TLS connection,
11970 look at the BIO actually used for writing to the network, not
11971 at the BIO used (sometimes) to buffer data for the network.
11972 Looking at different BIOs could result in write counts on the
11973 order of ULONG_MAX. Fixes bug 614.
11974 - On Windows, correctly detect errors when listing the contents of
11975 a directory. Fix from lodger.
11977 o Minor bugfixes (on 0.2.0.x):
11978 - Downgrade "sslv3 alert handshake failure" message to INFO.
11979 - If we set RelayBandwidthRate and RelayBandwidthBurst very high but
11980 left BandwidthRate and BandwidthBurst at the default, we would be
11981 silently limited by those defaults. Now raise them to match the
11982 RelayBandwidth* values.
11983 - Fix the SVK version detection logic to work correctly on a branch.
11984 - Make --enable-openbsd-malloc work correctly on Linux with alpha
11985 CPUs. Fixes bug 625.
11986 - Logging functions now check that the passed severity is sane.
11987 - Use proper log levels in the testsuite call of
11988 get_interface_address6().
11989 - When using a nonstandard malloc, do not use the platform values for
11990 HAVE_MALLOC_GOOD_SIZE or HAVE_MALLOC_USABLE_SIZE.
11991 - Make the openbsd malloc code use 8k pages on alpha CPUs and
11993 - Detect mismatched page sizes when using --enable-openbsd-malloc.
11994 - Avoid double-marked-for-close warning when certain kinds of invalid
11995 .in-addr.arpa addresses are passed to the DNSPort. Part of a fix
11996 for bug 617. Bugfix on 0.2.0.1-alpha.
11997 - Make sure that the "NULL-means-reject *:*" convention is followed by
11998 all the policy manipulation functions, avoiding some possible crash
11999 bugs. Bug found by lodger. Bugfix on 0.2.0.16-alpha.
12000 - Fix the implementation of ClientDNSRejectInternalAddresses so that it
12001 actually works, and doesn't warn about every single reverse lookup.
12002 Fixes the other part of bug 617. Bugfix on 0.2.0.1-alpha.
12005 - Only log guard node status when guard node status has changed.
12006 - Downgrade the 3 most common "INFO" messages to "DEBUG". This will
12007 make "INFO" 75% less verbose.
12010 Changes in version 0.2.0.21-rc - 2008-03-02
12011 Tor 0.2.0.21-rc is the second release candidate for the 0.2.0 series. It
12012 makes Tor work well with Vidalia again, fixes a rare assert bug,
12013 and fixes a pair of more minor bugs. The bundles also include Vidalia
12014 0.1.0 and Torbutton 1.1.16.
12017 - The control port should declare that it requires password auth
12018 when HashedControlSessionPassword is set too. Patch from Matt Edman;
12019 bugfix on 0.2.0.20-rc. Fixes bug 615.
12020 - Downgrade assert in connection_buckets_decrement() to a log message.
12021 This may help us solve bug 614, and in any case will make its
12022 symptoms less severe. Bugfix on 0.2.0.20-rc. Reported by fredzupy.
12023 - We were sometimes miscounting the number of bytes read from the
12024 network, causing our rate limiting to not be followed exactly.
12025 Bugfix on 0.2.0.16-alpha. Reported by lodger.
12028 - Fix compilation with OpenSSL 0.9.8 and 0.9.8a. All other supported
12029 OpenSSL versions should have been working fine. Diagnosis and patch
12030 from lodger, Karsten Loesing, and Sebastian Hahn. Fixes bug 616.
12031 Bugfix on 0.2.0.20-rc.
12034 Changes in version 0.2.0.20-rc - 2008-02-24
12035 Tor 0.2.0.20-rc is the first release candidate for the 0.2.0 series. It
12036 makes more progress towards normalizing Tor's TLS handshake, makes
12037 hidden services work better again, helps relays bootstrap if they don't
12038 know their IP address, adds optional support for linking in openbsd's
12039 allocator or tcmalloc, allows really fast relays to scale past 15000
12040 sockets, and fixes a bunch of minor bugs reported by Veracode.
12043 - Enable the revised TLS handshake based on the one designed by
12044 Steven Murdoch in proposal 124, as revised in proposal 130. It
12045 includes version negotiation for OR connections as described in
12046 proposal 105. The new handshake is meant to be harder for censors
12047 to fingerprint, and it adds the ability to detect certain kinds of
12048 man-in-the-middle traffic analysis attacks. The version negotiation
12049 feature will allow us to improve Tor's link protocol more safely
12051 - Choose which bridge to use proportional to its advertised bandwidth,
12052 rather than uniformly at random. This should speed up Tor for
12053 bridge users. Also do this for people who set StrictEntryNodes.
12054 - When a TrackHostExits-chosen exit fails too many times in a row,
12055 stop using it. Bugfix on 0.1.2.x; fixes bug 437.
12058 - Resolved problems with (re-)fetching hidden service descriptors.
12059 Patch from Karsten Loesing; fixes problems with 0.2.0.18-alpha
12060 and 0.2.0.19-alpha.
12061 - If we only ever used Tor for hidden service lookups or posts, we
12062 would stop building circuits and start refusing connections after
12063 24 hours, since we falsely believed that Tor was dormant. Reported
12064 by nwf; bugfix on 0.1.2.x.
12065 - Servers that don't know their own IP address should go to the
12066 authorities for their first directory fetch, even if their DirPort
12067 is off or if they don't know they're reachable yet. This will help
12068 them bootstrap better. Bugfix on 0.2.0.18-alpha; fixes bug 609.
12069 - When counting the number of open sockets, count not only the number
12070 of sockets we have received from the socket() call, but also
12071 the number we've gotten from accept() and socketpair(). This bug
12072 made us fail to count all sockets that we were using for incoming
12073 connections. Bugfix on 0.2.0.x.
12074 - Fix code used to find strings within buffers, when those strings
12075 are not in the first chunk of the buffer. Bugfix on 0.2.0.x.
12076 - Fix potential segfault when parsing HTTP headers. Bugfix on 0.2.0.x.
12077 - Add a new __HashedControlSessionPassword option for controllers
12078 to use for one-off session password hashes that shouldn't get
12079 saved to disk by SAVECONF --- Vidalia users were accumulating a
12080 pile of HashedControlPassword lines in their torrc files, one for
12081 each time they had restarted Tor and then clicked Save. Make Tor
12082 automatically convert "HashedControlPassword" to this new option but
12083 only when it's given on the command line. Partial fix for bug 586.
12085 o Minor features (performance):
12086 - Tune parameters for cell pool allocation to minimize amount of
12088 - Add OpenBSD malloc code from phk as an optional malloc
12089 replacement on Linux: some glibc libraries do very poorly
12090 with Tor's memory allocation patterns. Pass
12091 --enable-openbsd-malloc to get the replacement malloc code.
12092 - Add a --with-tcmalloc option to the configure script to link
12093 against tcmalloc (if present). Does not yet search for
12094 non-system include paths.
12095 - Stop imposing an arbitrary maximum on the number of file descriptors
12096 used for busy servers. Bug reported by Olaf Selke; patch from
12099 o Minor features (other):
12100 - When SafeLogging is disabled, log addresses along with all TLS
12102 - When building with --enable-gcc-warnings, check for whether Apple's
12103 warning "-Wshorten-64-to-32" is available.
12104 - Add a --passphrase-fd argument to the tor-gencert command for
12107 o Minor bugfixes (memory leaks and code problems):
12108 - We were leaking a file descriptor if Tor started with a zero-length
12109 cached-descriptors file. Patch by freddy77; bugfix on 0.1.2.
12110 - Detect size overflow in zlib code. Reported by Justin Ferguson and
12112 - We were comparing the raw BridgePassword entry with a base64'ed
12113 version of it, when handling a "/tor/networkstatus-bridges"
12114 directory request. Now compare correctly. Noticed by Veracode.
12115 - Recover from bad tracked-since value in MTBF-history file.
12116 Should fix bug 537.
12117 - Alter the code that tries to recover from unhandled write
12118 errors, to not try to flush onto a socket that's given us
12119 unhandled errors. Bugfix on 0.1.2.x.
12120 - Make Unix controlsockets work correctly on OpenBSD. Patch from
12121 tup. Bugfix on 0.2.0.3-alpha.
12123 o Minor bugfixes (other):
12124 - If we have an extra-info document for our server, always make
12125 it available on the control port, even if we haven't gotten
12126 a copy of it from an authority yet. Patch from mwenge.
12127 - Log the correct memory chunk sizes for empty RAM chunks in mempool.c.
12128 - Directory mirrors no longer include a guess at the client's IP
12129 address if the connection appears to be coming from the same /24
12130 network; it was producing too many wrong guesses.
12131 - Make the new hidden service code respect the SafeLogging setting.
12132 Bugfix on 0.2.0.x. Patch from Karsten.
12133 - When starting as an authority, do not overwrite all certificates
12134 cached from other authorities. Bugfix on 0.2.0.x. Fixes bug 606.
12135 - If we're trying to flush the last bytes on a connection (for
12136 example, when answering a directory request), reset the
12137 time-to-give-up timeout every time we manage to write something
12138 on the socket. Bugfix on 0.1.2.x.
12139 - Change the behavior of "getinfo status/good-server-descriptor"
12140 so it doesn't return failure when any authority disappears.
12141 - Even though the man page said that "TrackHostExits ." should
12142 work, nobody had ever implemented it. Bugfix on 0.1.0.x.
12143 - Report TLS "zero return" case as a "clean close" and "IO error"
12144 as a "close". Stop calling closes "unexpected closes": existing
12145 Tors don't use SSL_close(), so having a connection close without
12146 the TLS shutdown handshake is hardly unexpected.
12147 - Send NAMESERVER_STATUS messages for a single failed nameserver
12150 o Code simplifications and refactoring:
12151 - Remove the tor_strpartition function: its logic was confused,
12152 and it was only used for one thing that could be implemented far
12156 Changes in version 0.2.0.19-alpha - 2008-02-09
12157 Tor 0.2.0.19-alpha makes more progress towards normalizing Tor's TLS
12158 handshake, makes path selection for relays more secure and IP address
12159 guessing more robust, and generally fixes a lot of bugs in preparation
12160 for calling the 0.2.0 branch stable.
12163 - Do not include recognizeable strings in the commonname part of
12164 Tor's x509 certificates.
12167 - If we're a relay, avoid picking ourselves as an introduction point,
12168 a rendezvous point, or as the final hop for internal circuits. Bug
12169 reported by taranis and lodger. Bugfix on 0.1.2.x.
12170 - Patch from "Andrew S. Lists" to catch when we contact a directory
12171 mirror at IP address X and he says we look like we're coming from
12172 IP address X. Bugfix on 0.1.2.x.
12174 o Minor features (security):
12175 - Be more paranoid about overwriting sensitive memory on free(),
12176 as a defensive programming tactic to ensure forward secrecy.
12178 o Minor features (directory authority):
12179 - Actually validate the options passed to AuthDirReject,
12180 AuthDirInvalid, AuthDirBadDir, and AuthDirBadExit.
12181 - Reject router descriptors with out-of-range bandwidthcapacity or
12182 bandwidthburst values.
12184 o Minor features (controller):
12185 - Reject controller commands over 1MB in length. This keeps rogue
12186 processes from running us out of memory.
12188 o Minor features (misc):
12189 - Give more descriptive well-formedness errors for out-of-range
12190 hidden service descriptor/protocol versions.
12191 - Make memory debugging information describe more about history
12192 of cell allocation, so we can help reduce our memory use.
12194 o Deprecated features (controller):
12195 - The status/version/num-versioning and status/version/num-concurring
12196 GETINFO options are no longer useful in the v3 directory protocol:
12197 treat them as deprecated, and warn when they're used.
12200 - When our consensus networkstatus has been expired for a while, stop
12201 being willing to build circuits using it. Fixes bug 401. Bugfix
12203 - Directory caches now fetch certificates from all authorities
12204 listed in a networkstatus consensus, even when they do not
12205 recognize them. Fixes bug 571. Bugfix on 0.2.0.x.
12206 - When connecting to a bridge without specifying its key, insert
12207 the connection into the identity-to-connection map as soon as
12208 a key is learned. Fixes bug 574. Bugfix on 0.2.0.x.
12209 - Detect versions of OS X where malloc_good_size() is present in the
12210 library but never actually declared. Resolves bug 587. Bugfix
12212 - Stop incorrectly truncating zlib responses to directory authority
12213 signature download requests. Fixes bug 593. Bugfix on 0.2.0.x.
12214 - Stop recommending that every server operator send mail to tor-ops.
12215 Resolves bug 597. Bugfix on 0.1.2.x.
12216 - Don't trigger an assert if we start a directory authority with a
12217 private IP address (like 127.0.0.1).
12218 - Avoid possible failures when generating a directory with routers
12219 with over-long versions strings, or too many flags set. Bugfix
12221 - If an attempt to launch a DNS resolve request over the control
12222 port fails because we have overrun the limit on the number of
12223 connections, tell the controller that the request has failed.
12224 - Avoid using too little bandwidth when our clock skips a few
12225 seconds. Bugfix on 0.1.2.x.
12226 - Fix shell error when warning about missing packages in configure
12227 script, on Fedora or Red Hat machines. Bugfix on 0.2.0.x.
12228 - Do not become confused when receiving a spurious VERSIONS-like
12229 cell from a confused v1 client. Bugfix on 0.2.0.x.
12230 - Re-fetch v2 (as well as v0) rendezvous descriptors when all
12231 introduction points for a hidden service have failed. Patch from
12232 Karsten Loesing. Bugfix on 0.2.0.x.
12234 o Code simplifications and refactoring:
12235 - Remove some needless generality from cpuworker code, for improved
12237 - Stop overloading the circuit_t.onionskin field for both "onionskin
12238 from a CREATE cell that we are waiting for a cpuworker to be
12239 assigned" and "onionskin from an EXTEND cell that we are going to
12240 send to an OR as soon as we are connected". Might help with bug 600.
12241 - Add an in-place version of aes_crypt() so that we can avoid doing a
12242 needless memcpy() call on each cell payload.
12245 Changes in version 0.2.0.18-alpha - 2008-01-25
12246 Tor 0.2.0.18-alpha adds a sixth v3 directory authority run by CCC,
12247 fixes a big memory leak in 0.2.0.17-alpha, and adds new config options
12248 that can warn or reject connections to ports generally associated with
12249 vulnerable-plaintext protocols.
12251 o New directory authorities:
12252 - Set up dannenberg (run by CCC) as the sixth v3 directory
12256 - Fix a major memory leak when attempting to use the v2 TLS
12257 handshake code. Bugfix on 0.2.0.x; fixes bug 589.
12258 - We accidentally enabled the under-development v2 TLS handshake
12259 code, which was causing log entries like "TLS error while
12260 renegotiating handshake". Disable it again. Resolves bug 590.
12261 - We were computing the wrong Content-Length: header for directory
12262 responses that need to be compressed on the fly, causing clients
12263 asking for those items to always fail. Bugfix on 0.2.0.x; partially
12267 - Avoid going directly to the directory authorities even if you're a
12268 relay, if you haven't found yourself reachable yet or if you've
12269 decided not to advertise your dirport yet. Addresses bug 556.
12270 - If we've gone 12 hours since our last bandwidth check, and we
12271 estimate we have less than 50KB bandwidth capacity but we could
12272 handle more, do another bandwidth test.
12273 - New config options WarnPlaintextPorts and RejectPlaintextPorts so
12274 Tor can warn and/or refuse connections to ports commonly used with
12275 vulnerable-plaintext protocols. Currently we warn on ports 23,
12276 109, 110, and 143, but we don't reject any.
12279 - When we setconf ClientOnly to 1, close any current OR and Dir
12280 listeners. Reported by mwenge.
12281 - When we get a consensus that's been signed by more people than
12282 we expect, don't log about it; it's not a big deal. Reported
12286 - Don't answer "/tor/networkstatus-bridges" directory requests if
12287 the request isn't encrypted.
12288 - Make "ClientOnly 1" config option disable directory ports too.
12289 - Patches from Karsten Loesing to make v2 hidden services more
12290 robust: work even when there aren't enough HSDir relays available;
12291 retry when a v2 rend desc fetch fails; but don't retry if we
12292 already have a usable v0 rend desc.
12295 Changes in version 0.2.0.17-alpha - 2008-01-17
12296 Tor 0.2.0.17-alpha makes the tarball build cleanly again (whoops).
12299 - Make the tor-gencert man page get included correctly in the tarball.
12302 Changes in version 0.2.0.16-alpha - 2008-01-17
12303 Tor 0.2.0.16-alpha adds a fifth v3 directory authority run by Karsten
12304 Loesing, and generally cleans up a lot of features and minor bugs.
12306 o New directory authorities:
12307 - Set up gabelmoo (run by Karsten Loesing) as the fifth v3 directory
12310 o Major performance improvements:
12311 - Switch our old ring buffer implementation for one more like that
12312 used by free Unix kernels. The wasted space in a buffer with 1mb
12313 of data will now be more like 8k than 1mb. The new implementation
12314 also avoids realloc();realloc(); patterns that can contribute to
12315 memory fragmentation.
12318 - Configuration files now accept C-style strings as values. This
12319 helps encode characters not allowed in the current configuration
12320 file format, such as newline or #. Addresses bug 557.
12321 - Although we fixed bug 539 (where servers would send HTTP status 503
12322 responses _and_ send a body too), there are still servers out
12323 there that haven't upgraded. Therefore, make clients parse such
12324 bodies when they receive them.
12325 - When we're not serving v2 directory information, there is no reason
12326 to actually keep any around. Remove the obsolete files and directory
12327 on startup if they are very old and we aren't going to serve them.
12329 o Minor performance improvements:
12330 - Reference-count and share copies of address policy entries; only 5%
12331 of them were actually distinct.
12332 - Never walk through the list of logs if we know that no log is
12333 interested in a given message.
12336 - When an authority has not signed a consensus, do not try to
12337 download a nonexistent "certificate with key 00000000". Bugfix
12338 on 0.2.0.x. Fixes bug 569.
12339 - Fix a rare assert error when we're closing one of our threads:
12340 use a mutex to protect the list of logs, so we never write to the
12341 list as it's being freed. Bugfix on 0.1.2.x. Fixes the very rare
12342 bug 575, which is kind of the revenge of bug 222.
12343 - Patch from Karsten Loesing to complain less at both the client
12344 and the relay when a relay used to have the HSDir flag but doesn't
12345 anymore, and we try to upload a hidden service descriptor.
12346 - Stop leaking one cert per TLS context. Fixes bug 582. Bugfix on
12348 - Do not try to download missing certificates until we have tried
12349 to check our fallback consensus. Fixes bug 583.
12350 - Make bridges round reported GeoIP stats info up to the nearest
12351 estimate, not down. Now we can distinguish between "0 people from
12352 this country" and "1 person from this country".
12353 - Avoid a spurious free on base64 failure. Bugfix on 0.1.2.
12354 - Avoid possible segfault if key generation fails in
12355 crypto_pk_hybrid_encrypt. Bugfix on 0.2.0.
12356 - Avoid segfault in the case where a badly behaved v2 versioning
12357 directory sends a signed networkstatus with missing client-versions.
12359 - Avoid segfaults on certain complex invocations of
12360 router_get_by_hexdigest(). Bugfix on 0.1.2.
12361 - Correct bad index on array access in parse_http_time(). Bugfix
12363 - Fix possible bug in vote generation when server versions are present
12364 but client versions are not.
12365 - Fix rare bug on REDIRECTSTREAM control command when called with no
12366 port set: it could erroneously report an error when none had
12368 - Avoid bogus crash-prone, leak-prone tor_realloc when we're
12369 compressing large objects and find ourselves with more than 4k
12370 left over. Bugfix on 0.2.0.
12371 - Fix a small memory leak when setting up a hidden service.
12372 - Fix a few memory leaks that could in theory happen under bizarre
12374 - Fix an assert if we post a general-purpose descriptor via the
12375 control port but that descriptor isn't mentioned in our current
12376 network consensus. Bug reported by Jon McLachlan; bugfix on
12379 o Minor features (controller):
12380 - Get NS events working again. Patch from tup.
12381 - The GETCONF command now escapes and quotes configuration values
12382 that don't otherwise fit into the torrc file.
12383 - The SETCONF command now handles quoted values correctly.
12385 o Minor features (directory authorities):
12386 - New configuration options to override default maximum number of
12387 servers allowed on a single IP address. This is important for
12388 running a test network on a single host.
12389 - Actually implement the -s option to tor-gencert.
12390 - Add a manual page for tor-gencert.
12392 o Minor features (bridges):
12393 - Bridge authorities no longer serve bridge descriptors over
12394 unencrypted connections.
12396 o Minor features (other):
12397 - Add hidden services and DNSPorts to the list of things that make
12398 Tor accept that it has running ports. Change starting Tor with no
12399 ports from a fatal error to a warning; we might change it back if
12400 this turns out to confuse anybody. Fixes bug 579.
12403 Changes in version 0.1.2.19 - 2008-01-17
12404 Tor 0.1.2.19 fixes a huge memory leak on exit relays, makes the default
12405 exit policy a little bit more conservative so it's safer to run an
12406 exit relay on a home system, and fixes a variety of smaller issues.
12409 - Exit policies now reject connections that are addressed to a
12410 relay's public (external) IP address too, unless
12411 ExitPolicyRejectPrivate is turned off. We do this because too
12412 many relays are running nearby to services that trust them based
12413 on network address.
12416 - When the clock jumps forward a lot, do not allow the bandwidth
12417 buckets to become negative. Fixes bug 544.
12418 - Fix a memory leak on exit relays; we were leaking a cached_resolve_t
12419 on every successful resolve. Reported by Mike Perry.
12420 - Purge old entries from the "rephist" database and the hidden
12421 service descriptor database even when DirPort is zero.
12422 - Stop thinking that 0.1.2.x directory servers can handle "begin_dir"
12423 requests. Should ease bugs 406 and 419 where 0.1.2.x relays are
12424 crashing or mis-answering these requests.
12425 - When we decide to send a 503 response to a request for servers, do
12426 not then also send the server descriptors: this defeats the whole
12427 purpose. Fixes bug 539.
12430 - Changing the ExitPolicyRejectPrivate setting should cause us to
12431 rebuild our server descriptor.
12432 - Fix handling of hex nicknames when answering controller requests for
12433 networkstatus by name, or when deciding whether to warn about
12434 unknown routers in a config option. (Patch from mwenge.)
12435 - Fix a couple of hard-to-trigger autoconf problems that could result
12436 in really weird results on platforms whose sys/types.h files define
12437 nonstandard integer types.
12438 - Don't try to create the datadir when running --verify-config or
12439 --hash-password. Resolves bug 540.
12440 - If we were having problems getting a particular descriptor from the
12441 directory caches, and then we learned about a new descriptor for
12442 that router, we weren't resetting our failure count. Reported
12444 - Although we fixed bug 539 (where servers would send HTTP status 503
12445 responses _and_ send a body too), there are still servers out there
12446 that haven't upgraded. Therefore, make clients parse such bodies
12447 when they receive them.
12448 - Run correctly on systems where rlim_t is larger than unsigned long.
12449 This includes some 64-bit systems.
12450 - Run correctly on platforms (like some versions of OS X 10.5) where
12451 the real limit for number of open files is OPEN_FILES, not rlim_max
12452 from getrlimit(RLIMIT_NOFILES).
12453 - Avoid a spurious free on base64 failure.
12454 - Avoid segfaults on certain complex invocations of
12455 router_get_by_hexdigest().
12456 - Fix rare bug on REDIRECTSTREAM control command when called with no
12457 port set: it could erroneously report an error when none had
12461 Changes in version 0.2.0.15-alpha - 2007-12-25
12462 Tor 0.2.0.14-alpha and 0.2.0.15-alpha fix a bunch of bugs with the
12463 features added in 0.2.0.13-alpha.
12466 - Fix several remotely triggerable asserts based on DirPort requests
12467 for a v2 or v3 networkstatus object before we were prepared. This
12468 was particularly bad for 0.2.0.13 and later bridge relays, who
12469 would never have a v2 networkstatus and would thus always crash
12470 when used. Bugfixes on 0.2.0.x.
12471 - Estimate the v3 networkstatus size more accurately, rather than
12472 estimating it at zero bytes and giving it artificially high priority
12473 compared to other directory requests. Bugfix on 0.2.0.x.
12476 - Fix configure.in logic for cross-compilation.
12477 - When we load a bridge descriptor from the cache, and it was
12478 previously unreachable, mark it as retriable so we won't just
12479 ignore it. Also, try fetching a new copy immediately. Bugfixes
12481 - The bridge GeoIP stats were counting other relays, for example
12482 self-reachability and authority-reachability tests.
12485 - Support compilation to target iPhone; patch from cjacker huang.
12486 To build for iPhone, pass the --enable-iphone option to configure.
12489 Changes in version 0.2.0.14-alpha - 2007-12-23
12491 - Fix a crash on startup if you install Tor 0.2.0.13-alpha fresh
12492 without a datadirectory from a previous Tor install. Reported
12494 - Fix a crash when we fetch a descriptor that turns out to be
12495 unexpected (it used to be in our networkstatus when we started
12496 fetching it, but it isn't in our current networkstatus), and we
12497 aren't using bridges. Bugfix on 0.2.0.x.
12498 - Fix a crash when accessing hidden services: it would work the first
12499 time you use a given introduction point for your service, but
12500 on subsequent requests we'd be using garbage memory. Fixed by
12501 Karsten Loesing. Bugfix on 0.2.0.13-alpha.
12502 - Fix a crash when we load a bridge descriptor from disk but we don't
12503 currently have a Bridge line for it in our torrc. Bugfix on
12507 - If bridge authorities set BridgePassword, they will serve a
12508 snapshot of known bridge routerstatuses from their DirPort to
12509 anybody who knows that password. Unset by default.
12512 - Make the unit tests build again.
12513 - Make "GETINFO/desc-annotations/id/<OR digest>" actually work.
12514 - Make PublishServerDescriptor default to 1, so the default doesn't
12515 have to change as we invent new directory protocol versions.
12516 - Fix test for rlim_t on OSX 10.3: sys/resource.h doesn't want to
12517 be included unless sys/time.h is already included. Fixes
12518 bug 553. Bugfix on 0.2.0.x.
12519 - If we receive a general-purpose descriptor and then receive an
12520 identical bridge-purpose descriptor soon after, don't discard
12521 the next one as a duplicate.
12524 - If BridgeRelay is set to 1, then the default for
12525 PublishServerDescriptor is now "bridge" rather than "v2,v3".
12526 - If the user sets RelayBandwidthRate but doesn't set
12527 RelayBandwidthBurst, then make them equal rather than erroring out.
12530 Changes in version 0.2.0.13-alpha - 2007-12-21
12531 Tor 0.2.0.13-alpha adds a fourth v3 directory authority run by Geoff
12532 Goodell, fixes many more bugs, and adds a lot of infrastructure for
12535 o New directory authorities:
12536 - Set up lefkada (run by Geoff Goodell) as the fourth v3 directory
12540 - Only update guard status (usable / not usable) once we have
12541 enough directory information. This was causing us to always pick
12542 two new guards on startup (bugfix on 0.2.0.9-alpha), and it was
12543 causing us to discard all our guards on startup if we hadn't been
12544 running for a few weeks (bugfix on 0.1.2.x). Fixes bug 448.
12545 - Purge old entries from the "rephist" database and the hidden
12546 service descriptor databases even when DirPort is zero. Bugfix
12548 - We were ignoring our RelayBandwidthRate for the first 30 seconds
12549 after opening a circuit -- even a relayed circuit. Bugfix on
12551 - Stop thinking that 0.1.2.x directory servers can handle "begin_dir"
12552 requests. Should ease bugs 406 and 419 where 0.1.2.x relays are
12553 crashing or mis-answering these types of requests.
12554 - Relays were publishing their server descriptor to v1 and v2
12555 directory authorities, but they didn't try publishing to v3-only
12556 authorities. Fix this; and also stop publishing to v1 authorities.
12558 - When we were reading router descriptors from cache, we were ignoring
12559 the annotations -- so for example we were reading in bridge-purpose
12560 descriptors as general-purpose descriptors. Bugfix on 0.2.0.8-alpha.
12561 - When we decided to send a 503 response to a request for servers, we
12562 were then also sending the server descriptors: this defeats the
12563 whole purpose. Fixes bug 539; bugfix on 0.1.2.x.
12566 - Bridge relays now behave like clients with respect to time
12567 intervals for downloading new consensus documents -- otherwise they
12568 stand out. Bridge users now wait until the end of the interval,
12569 so their bridge relay will be sure to have a new consensus document.
12570 - Three new config options (AlternateDirAuthority,
12571 AlternateBridgeAuthority, and AlternateHSAuthority) that let the
12572 user selectively replace the default directory authorities by type,
12573 rather than the all-or-nothing replacement that DirServer offers.
12574 - Tor can now be configured to read a GeoIP file from disk in one
12575 of two formats. This can be used by controllers to map IP addresses
12576 to countries. Eventually, it may support exit-by-country.
12577 - When possible, bridge relays remember which countries users
12578 are coming from, and report aggregate information in their
12579 extra-info documents, so that the bridge authorities can learn
12580 where Tor is blocked.
12581 - Bridge directory authorities now do reachability testing on the
12582 bridges they know. They provide router status summaries to the
12583 controller via "getinfo ns/purpose/bridge", and also dump summaries
12584 to a file periodically.
12585 - Stop fetching directory info so aggressively if your DirPort is
12586 on but your ORPort is off; stop fetching v2 dir info entirely.
12587 You can override these choices with the new FetchDirInfoEarly
12591 - The fix in 0.2.0.12-alpha cleared the "hsdir" flag in v3 network
12592 consensus documents when there are too many relays at a single
12593 IP address. Now clear it in v2 network status documents too, and
12594 also clear it in routerinfo_t when the relay is no longer listed
12595 in the relevant networkstatus document.
12596 - Don't crash if we get an unexpected value for the
12597 PublishServerDescriptor config option. Reported by Matt Edman;
12598 bugfix on 0.2.0.9-alpha.
12599 - Our new v2 hidden service descriptor format allows descriptors
12600 that have no introduction points. But Tor crashed when we tried
12601 to build a descriptor with no intro points (and it would have
12602 crashed if we had tried to parse one). Bugfix on 0.2.0.x; patch
12603 by Karsten Loesing.
12604 - Fix building with dmalloc 5.5.2 with glibc.
12605 - Reject uploaded descriptors and extrainfo documents if they're
12606 huge. Otherwise we'll cache them all over the network and it'll
12607 clog everything up. Reported by Aljosha Judmayer.
12608 - Check for presence of s6_addr16 and s6_addr32 fields in in6_addr
12609 via autoconf. Should fix compile on solaris. Bugfix on 0.2.0.x.
12610 - When the DANGEROUS_VERSION controller status event told us we're
12611 running an obsolete version, it used the string "OLD" to describe
12612 it. Yet the "getinfo" interface used the string "OBSOLETE". Now use
12613 "OBSOLETE" in both cases. Bugfix on 0.1.2.x.
12614 - If we can't expand our list of entry guards (e.g. because we're
12615 using bridges or we have StrictEntryNodes set), don't mark relays
12616 down when they fail a directory request. Otherwise we're too quick
12617 to mark all our entry points down. Bugfix on 0.1.2.x.
12618 - Fix handling of hex nicknames when answering controller requests for
12619 networkstatus by name, or when deciding whether to warn about unknown
12620 routers in a config option. Bugfix on 0.1.2.x. (Patch from mwenge.)
12621 - Fix a couple of hard-to-trigger autoconf problems that could result
12622 in really weird results on platforms whose sys/types.h files define
12623 nonstandard integer types. Bugfix on 0.1.2.x.
12624 - Fix compilation with --disable-threads set. Bugfix on 0.2.0.x.
12625 - Don't crash on name lookup when we have no current consensus. Fixes
12626 bug 538; bugfix on 0.2.0.x.
12627 - Only Tors that want to mirror the v2 directory info should
12628 create the "cached-status" directory in their datadir. (All Tors
12629 used to create it.) Bugfix on 0.2.0.9-alpha.
12630 - Directory authorities should only automatically download Extra Info
12631 documents if they're v1, v2, or v3 authorities. Bugfix on 0.1.2.x.
12634 - On the USR1 signal, when dmalloc is in use, log the top 10 memory
12635 consumers. (We already do this on HUP.)
12636 - Authorities and caches fetch the v2 networkstatus documents
12637 less often, now that v3 is encouraged.
12638 - Add a new config option BridgeRelay that specifies you want to
12639 be a bridge relay. Right now the only difference is that it makes
12640 you answer begin_dir requests, and it makes you cache dir info,
12641 even if your DirPort isn't on.
12642 - Add "GETINFO/desc-annotations/id/<OR digest>" so controllers can
12643 ask about source, timestamp of arrival, purpose, etc. We need
12644 something like this to help Vidalia not do GeoIP lookups on bridge
12646 - Allow multiple HashedControlPassword config lines, to support
12647 multiple controller passwords.
12648 - Authorities now decide whether they're authoritative for a given
12649 router based on the router's purpose.
12650 - New config options AuthDirBadDir and AuthDirListBadDirs for
12651 authorities to mark certain relays as "bad directories" in the
12652 networkstatus documents. Also supports the "!baddir" directive in
12653 the approved-routers file.
12656 Changes in version 0.2.0.12-alpha - 2007-11-16
12657 This twelfth development snapshot fixes some more build problems as
12658 well as a few minor bugs.
12661 - Make it build on OpenBSD again. Patch from tup.
12662 - Substitute BINDIR and LOCALSTATEDIR in scripts. Fixes
12663 package-building for Red Hat, OS X, etc.
12665 o Minor bugfixes (on 0.1.2.x):
12666 - Changing the ExitPolicyRejectPrivate setting should cause us to
12667 rebuild our server descriptor.
12669 o Minor bugfixes (on 0.2.0.x):
12670 - When we're lacking a consensus, don't try to perform rendezvous
12671 operations. Reported by Karsten Loesing.
12672 - Fix a small memory leak whenever we decide against using a
12673 newly picked entry guard. Reported by Mike Perry.
12674 - When authorities detected more than two relays running on the same
12675 IP address, they were clearing all the status flags but forgetting
12676 to clear the "hsdir" flag. So clients were being told that a
12677 given relay was the right choice for a v2 hsdir lookup, yet they
12678 never had its descriptor because it was marked as 'not running'
12680 - If we're trying to fetch a bridge descriptor and there's no way
12681 the bridge authority could help us (for example, we don't know
12682 a digest, or there is no bridge authority), don't be so eager to
12683 fall back to asking the bridge authority.
12684 - If we're using bridges or have strictentrynodes set, and our
12685 chosen exit is in the same family as all our bridges/entry guards,
12686 then be flexible about families.
12689 - When we negotiate a v2 link-layer connection (not yet implemented),
12690 accept RELAY_EARLY cells and turn them into RELAY cells if we've
12691 negotiated a v1 connection for their next step. Initial code for
12695 Changes in version 0.2.0.11-alpha - 2007-11-12
12696 This eleventh development snapshot fixes some build problems with
12697 the previous snapshot. It also includes a more secure-by-default exit
12698 policy for relays, fixes an enormous memory leak for exit relays, and
12699 fixes another bug where servers were falling out of the directory list.
12702 - Exit policies now reject connections that are addressed to a
12703 relay's public (external) IP address too, unless
12704 ExitPolicyRejectPrivate is turned off. We do this because too
12705 many relays are running nearby to services that trust them based
12706 on network address. Bugfix on 0.1.2.x.
12709 - Fix a memory leak on exit relays; we were leaking a cached_resolve_t
12710 on every successful resolve. Reported by Mike Perry; bugfix
12712 - On authorities, never downgrade to old router descriptors simply
12713 because they're listed in the consensus. This created a catch-22
12714 where we wouldn't list a new descriptor because there was an
12715 old one in the consensus, and we couldn't get the new one in the
12716 consensus because we wouldn't list it. Possible fix for bug 548.
12717 Also, this might cause bug 543 to appear on authorities; if so,
12718 we'll need a band-aid for that. Bugfix on 0.2.0.9-alpha.
12720 o Packaging fixes on 0.2.0.10-alpha:
12721 - We were including instructions about what to do with the
12722 src/config/fallback-consensus file, but we weren't actually
12723 including it in the tarball. Disable all of that for now.
12726 - Allow people to say PreferTunnelledDirConns rather than
12727 PreferTunneledDirConns, for those alternate-spellers out there.
12730 - Don't reevaluate all the information from our consensus document
12731 just because we've downloaded a v2 networkstatus that we intend
12732 to cache. Fixes bug 545; bugfix on 0.2.0.x.
12735 Changes in version 0.2.0.10-alpha - 2007-11-10
12736 This tenth development snapshot adds a third v3 directory authority
12737 run by Mike Perry, adds most of Karsten Loesing's new hidden service
12738 descriptor format, fixes a bad crash bug and new bridge bugs introduced
12739 in 0.2.0.9-alpha, fixes many bugs with the v3 directory implementation,
12740 fixes some minor memory leaks in previous 0.2.0.x snapshots, and
12741 addresses many more minor issues.
12743 o New directory authorities:
12744 - Set up ides (run by Mike Perry) as the third v3 directory authority.
12747 - Allow tunnelled directory connections to ask for an encrypted
12748 "begin_dir" connection or an anonymized "uses a full Tor circuit"
12749 connection independently. Now we can make anonymized begin_dir
12750 connections for (e.g.) more secure hidden service posting and
12752 - More progress on proposal 114: code from Karsten Loesing to
12753 implement new hidden service descriptor format.
12754 - Raise the default BandwidthRate/BandwidthBurst to 5MB/10MB, to
12755 accommodate the growing number of servers that use the default
12756 and are reaching it.
12757 - Directory authorities use a new formula for selecting which nodes
12758 to advertise as Guards: they must be in the top 7/8 in terms of
12759 how long we have known about them, and above the median of those
12760 nodes in terms of weighted fractional uptime.
12761 - Make "not enough dir info yet" warnings describe *why* Tor feels
12762 it doesn't have enough directory info yet.
12765 - Stop servers from crashing if they set a Family option (or
12766 maybe in other situations too). Bugfix on 0.2.0.9-alpha; reported
12768 - Make bridge users work again -- the move to v3 directories in
12769 0.2.0.9-alpha had introduced a number of bugs that made bridges
12770 no longer work for clients.
12771 - When the clock jumps forward a lot, do not allow the bandwidth
12772 buckets to become negative. Bugfix on 0.1.2.x; fixes bug 544.
12774 o Major bugfixes (v3 dir, bugfixes on 0.2.0.9-alpha):
12775 - When the consensus lists a router descriptor that we previously were
12776 mirroring, but that we considered non-canonical, reload the
12777 descriptor as canonical. This fixes bug 543 where Tor servers
12778 would start complaining after a few days that they don't have
12779 enough directory information to build a circuit.
12780 - Consider replacing the current consensus when certificates arrive
12781 that make the pending consensus valid. Previously, we were only
12782 considering replacement when the new certs _didn't_ help.
12783 - Fix an assert error on startup if we didn't already have the
12784 consensus and certs cached in our datadirectory: we were caching
12785 the consensus in consensus_waiting_for_certs but then free'ing it
12787 - Avoid sending a request for "keys/fp" (for which we'll get a 400 Bad
12788 Request) if we need more v3 certs but we've already got pending
12789 requests for all of them.
12790 - Correctly back off from failing certificate downloads. Fixes
12792 - Authorities don't vote on the Running flag if they have been running
12793 for less than 30 minutes themselves. Fixes bug 547, where a newly
12794 started authority would vote that everyone was down.
12796 o New requirements:
12797 - Drop support for OpenSSL version 0.9.6. Just about nobody was using
12798 it, it had no AES, and it hasn't seen any security patches since
12802 - Clients now hold circuitless TLS connections open for 1.5 times
12803 MaxCircuitDirtiness (15 minutes), since it is likely that they'll
12804 rebuild a new circuit over them within that timeframe. Previously,
12805 they held them open only for KeepalivePeriod (5 minutes).
12806 - Use "If-Modified-Since" to avoid retrieving consensus
12807 networkstatuses that we already have.
12808 - When we have no consensus, check FallbackNetworkstatusFile (defaults
12809 to $PREFIX/share/tor/fallback-consensus) for a consensus. This way
12810 we start knowing some directory caches.
12811 - When we receive a consensus from the future, warn about skew.
12812 - Improve skew reporting: try to give the user a better log message
12813 about how skewed they are, and how much this matters.
12814 - When we have a certificate for an authority, believe that
12815 certificate's claims about the authority's IP address.
12816 - New --quiet command-line option to suppress the default console log.
12817 Good in combination with --hash-password.
12818 - Authorities send back an X-Descriptor-Not-New header in response to
12819 an accepted-but-discarded descriptor upload. Partially implements
12821 - Make the log message for "tls error. breaking." more useful.
12822 - Better log messages about certificate downloads, to attempt to
12823 track down the second incarnation of bug 546.
12825 o Minor features (bridges):
12826 - If bridge users set UpdateBridgesFromAuthority, but the digest
12827 they ask for is a 404 from the bridge authority, they now fall
12828 back to trying the bridge directly.
12829 - Bridges now use begin_dir to publish their server descriptor to
12830 the bridge authority, even when they haven't set TunnelDirConns.
12832 o Minor features (controller):
12833 - When reporting clock skew, and we know that the clock is _at least
12834 as skewed_ as some value, but we don't know the actual value,
12835 report the value as a "minimum skew."
12838 - Update linux-tor-prio.sh script to allow QoS based on the uid of
12839 the Tor process. Patch from Marco Bonetti with tweaks from Mike
12843 - Refuse to start if both ORPort and UseBridges are set. Bugfix
12844 on 0.2.0.x, suggested by Matt Edman.
12845 - Don't stop fetching descriptors when FetchUselessDescriptors is
12846 set, even if we stop asking for circuits. Bugfix on 0.1.2.x;
12847 reported by tup and ioerror.
12848 - Better log message on vote from unknown authority.
12849 - Don't log "Launching 0 request for 0 router" message.
12851 o Minor bugfixes (memory leaks):
12852 - Stop leaking memory every time we parse a v3 certificate. Bugfix
12854 - Stop leaking memory every time we load a v3 certificate. Bugfix
12855 on 0.2.0.1-alpha. Fixes bug 536.
12856 - Stop leaking a cached networkstatus on exit. Bugfix on
12858 - Stop leaking voter information every time we free a consensus.
12859 Bugfix on 0.2.0.3-alpha.
12860 - Stop leaking signed data every time we check a voter signature.
12861 Bugfix on 0.2.0.3-alpha.
12862 - Stop leaking a signature every time we fail to parse a consensus or
12863 a vote. Bugfix on 0.2.0.3-alpha.
12864 - Stop leaking v2_download_status_map on shutdown. Bugfix on
12866 - Stop leaking conn->nickname every time we make a connection to a
12867 Tor relay without knowing its expected identity digest (e.g. when
12868 using bridges). Bugfix on 0.2.0.3-alpha.
12870 - Minor bugfixes (portability):
12871 - Run correctly on platforms where rlim_t is larger than unsigned
12872 long, and/or where the real limit for number of open files is
12873 OPEN_FILES, not rlim_max from getrlimit(RLIMIT_NOFILES). In
12874 particular, these may be needed for OS X 10.5.
12877 Changes in version 0.1.2.18 - 2007-10-28
12878 Tor 0.1.2.18 fixes many problems including crash bugs, problems with
12879 hidden service introduction that were causing huge delays, and a big
12880 bug that was causing some servers to disappear from the network status
12881 lists for a few hours each day.
12883 o Major bugfixes (crashes):
12884 - If a connection is shut down abruptly because of something that
12885 happened inside connection_flushed_some(), do not call
12886 connection_finished_flushing(). Should fix bug 451:
12887 "connection_stop_writing: Assertion conn->write_event failed"
12888 Bugfix on 0.1.2.7-alpha.
12889 - Fix possible segfaults in functions called from
12890 rend_process_relay_cell().
12892 o Major bugfixes (hidden services):
12893 - Hidden services were choosing introduction points uniquely by
12894 hexdigest, but when constructing the hidden service descriptor
12895 they merely wrote the (potentially ambiguous) nickname.
12896 - Clients now use the v2 intro format for hidden service
12897 connections: they specify their chosen rendezvous point by identity
12898 digest rather than by (potentially ambiguous) nickname. These
12899 changes could speed up hidden service connections dramatically.
12901 o Major bugfixes (other):
12902 - Stop publishing a new server descriptor just because we get a
12903 HUP signal. This led (in a roundabout way) to some servers getting
12904 dropped from the networkstatus lists for a few hours each day.
12905 - When looking for a circuit to cannibalize, consider family as well
12906 as identity. Fixes bug 438. Bugfix on 0.1.0.x (which introduced
12907 circuit cannibalization).
12908 - When a router wasn't listed in a new networkstatus, we were leaving
12909 the flags for that router alone -- meaning it remained Named,
12910 Running, etc -- even though absence from the networkstatus means
12911 that it shouldn't be considered to exist at all anymore. Now we
12912 clear all the flags for routers that fall out of the networkstatus
12913 consensus. Fixes bug 529.
12916 - Don't try to access (or alter) the state file when running
12917 --list-fingerprint or --verify-config or --hash-password. Resolves
12919 - When generating information telling us how to extend to a given
12920 router, do not try to include the nickname if it is
12921 absent. Resolves bug 467.
12922 - Fix a user-triggerable segfault in expand_filename(). (There isn't
12923 a way to trigger this remotely.)
12924 - When sending a status event to the controller telling it that an
12925 OR address is reachable, set the port correctly. (Previously we
12926 were reporting the dir port.)
12927 - Fix a minor memory leak whenever a controller sends the PROTOCOLINFO
12928 command. Bugfix on 0.1.2.17.
12929 - When loading bandwidth history, do not believe any information in
12930 the future. Fixes bug 434.
12931 - When loading entry guard information, do not believe any information
12933 - When we have our clock set far in the future and generate an
12934 onion key, then re-set our clock to be correct, we should not stop
12935 the onion key from getting rotated.
12936 - On some platforms, accept() can return a broken address. Detect
12937 this more quietly, and deal accordingly. Fixes bug 483.
12938 - It's not actually an error to find a non-pending entry in the DNS
12939 cache when canceling a pending resolve. Don't log unless stuff
12940 is fishy. Resolves bug 463.
12941 - Don't reset trusted dir server list when we set a configuration
12942 option. Patch from Robert Hogan.
12943 - Don't try to create the datadir when running --verify-config or
12944 --hash-password. Resolves bug 540.
12947 Changes in version 0.2.0.9-alpha - 2007-10-24
12948 This ninth development snapshot switches clients to the new v3 directory
12949 system; allows servers to be listed in the network status even when they
12950 have the same nickname as a registered server; and fixes many other
12951 bugs including a big one that was causing some servers to disappear
12952 from the network status lists for a few hours each day.
12954 o Major features (directory system):
12955 - Clients now download v3 consensus networkstatus documents instead
12956 of v2 networkstatus documents. Clients and caches now base their
12957 opinions about routers on these consensus documents. Clients only
12958 download router descriptors listed in the consensus.
12959 - Authorities now list servers who have the same nickname as
12960 a different named server, but list them with a new flag,
12961 "Unnamed". Now we can list servers that happen to pick the same
12962 nickname as a server that registered two years ago and then
12963 disappeared. Partially implements proposal 122.
12964 - If the consensus lists a router as "Unnamed", the name is assigned
12965 to a different router: do not identify the router by that name.
12966 Partially implements proposal 122.
12967 - Authorities can now come to a consensus on which method to use to
12968 compute the consensus. This gives us forward compatibility.
12971 - Stop publishing a new server descriptor just because we HUP or
12972 when we find our DirPort to be reachable but won't actually publish
12973 it. New descriptors without any real changes are dropped by the
12974 authorities, and can screw up our "publish every 18 hours" schedule.
12976 - When a router wasn't listed in a new networkstatus, we were leaving
12977 the flags for that router alone -- meaning it remained Named,
12978 Running, etc -- even though absence from the networkstatus means
12979 that it shouldn't be considered to exist at all anymore. Now we
12980 clear all the flags for routers that fall out of the networkstatus
12981 consensus. Fixes bug 529; bugfix on 0.1.2.x.
12982 - Fix awful behavior in DownloadExtraInfo option where we'd fetch
12983 extrainfo documents and then discard them immediately for not
12984 matching the latest router. Bugfix on 0.2.0.1-alpha.
12986 o Minor features (v3 directory protocol):
12987 - Allow tor-gencert to generate a new certificate without replacing
12989 - Allow certificates to include an address.
12990 - When we change our directory-cache settings, reschedule all voting
12991 and download operations.
12992 - Reattempt certificate downloads immediately on failure, as long as
12993 we haven't failed a threshold number of times yet.
12994 - Delay retrying consensus downloads while we're downloading
12995 certificates to verify the one we just got. Also, count getting a
12996 consensus that we already have (or one that isn't valid) as a failure,
12997 and count failing to get the certificates after 20 minutes as a
12999 - Build circuits and download descriptors even if our consensus is a
13000 little expired. (This feature will go away once authorities are
13003 o Minor features (router descriptor cache):
13004 - If we find a cached-routers file that's been sitting around for more
13005 than 28 days unmodified, then most likely it's a leftover from
13006 when we upgraded to 0.2.0.8-alpha. Remove it. It has no good
13008 - When we (as a cache) download a descriptor because it was listed
13009 in a consensus, remember when the consensus was supposed to expire,
13010 and don't expire the descriptor until then.
13012 o Minor features (performance):
13013 - Call routerlist_remove_old_routers() much less often. This should
13014 speed startup, especially on directory caches.
13015 - Don't try to launch new descriptor downloads quite so often when we
13016 already have enough directory information to build circuits.
13017 - Base64 decoding was actually showing up on our profile when parsing
13018 the initial descriptor file; switch to an in-process all-at-once
13019 implementation that's about 3.5x times faster than calling out to
13022 o Minor features (compilation):
13023 - Detect non-ASCII platforms (if any still exist) and refuse to
13024 build there: some of our code assumes that 'A' is 65 and so on.
13026 o Minor bugfixes (v3 directory authorities, bugfixes on 0.2.0.x):
13027 - Make the "next period" votes into "current period" votes immediately
13028 after publishing the consensus; avoid a heisenbug that made them
13029 stick around indefinitely.
13030 - When we discard a vote as a duplicate, do not report this as
13032 - Treat missing v3 keys or certificates as an error when running as a
13033 v3 directory authority.
13034 - When we're configured to be a v3 authority, but we're only listed
13035 as a non-v3 authority in our DirServer line for ourself, correct
13037 - If an authority doesn't have a qualified hostname, just put
13038 its address in the vote. This fixes the problem where we referred to
13039 "moria on moria:9031."
13040 - Distinguish between detached signatures for the wrong period, and
13041 detached signatures for a divergent vote.
13042 - Fix a small memory leak when computing a consensus.
13043 - When there's no concensus, we were forming a vote every 30
13044 minutes, but writing the "valid-after" line in our vote based
13045 on our configured V3AuthVotingInterval: so unless the intervals
13046 matched up, we immediately rejected our own vote because it didn't
13047 start at the voting interval that caused us to construct a vote.
13049 o Minor bugfixes (v3 directory protocol, bugfixes on 0.2.0.x):
13050 - Delete unverified-consensus when the real consensus is set.
13051 - Consider retrying a consensus networkstatus fetch immediately
13052 after one fails: don't wait 60 seconds to notice.
13053 - When fetching a consensus as a cache, wait until a newer consensus
13054 should exist before trying to replace the current one.
13055 - Use a more forgiving schedule for retrying failed consensus
13056 downloads than for other types.
13058 o Minor bugfixes (other directory issues):
13059 - Correct the implementation of "download votes by digest." Bugfix on
13061 - Authorities no longer send back "400 you're unreachable please fix
13062 it" errors to Tor servers that aren't online all the time. We're
13063 supposed to tolerate these servers now. Bugfix on 0.1.2.x.
13065 o Minor bugfixes (controller):
13066 - Don't reset trusted dir server list when we set a configuration
13067 option. Patch from Robert Hogan; bugfix on 0.1.2.x.
13068 - Respond to INT and TERM SIGNAL commands before we execute the
13069 signal, in case the signal shuts us down. We had a patch in
13070 0.1.2.1-alpha that tried to do this by queueing the response on
13071 the connection's buffer before shutting down, but that really
13072 isn't the same thing at all. Bug located by Matt Edman.
13074 o Minor bugfixes (misc):
13075 - Correctly check for bad options to the "PublishServerDescriptor"
13076 config option. Bugfix on 0.2.0.1-alpha; reported by Matt Edman.
13077 - Stop leaking memory on failing case of base32_decode, and make
13078 it accept upper-case letters. Bugfixes on 0.2.0.7-alpha.
13079 - Don't try to download extrainfo documents when we're trying to
13080 fetch enough directory info to build a circuit: having enough
13081 info should get priority. Bugfix on 0.2.0.x.
13082 - Don't complain that "your server has not managed to confirm that its
13083 ports are reachable" if we haven't been able to build any circuits
13084 yet. Bug found by spending four hours without a v3 consensus. Bugfix
13086 - Detect the reason for failing to mmap a descriptor file we just
13087 wrote, and give a more useful log message. Fixes bug 533. Bugfix
13090 o Code simplifications and refactoring:
13091 - Remove support for the old bw_accounting file: we've been storing
13092 bandwidth accounting information in the state file since
13093 0.1.2.5-alpha. This may result in bandwidth accounting errors
13094 if you try to upgrade from 0.1.1.x or earlier, or if you try to
13095 downgrade to 0.1.1.x or earlier.
13096 - New convenience code to locate a file within the DataDirectory.
13097 - Move non-authority functionality out of dirvote.c.
13098 - Refactor the arguments for router_pick_{directory_|trusteddir}server
13099 so that they all take the same named flags.
13102 - Include the "tor-ctrl.sh" bash script by Stefan Behte to provide
13103 Unix users an easy way to script their Tor process (e.g. by
13104 adjusting bandwidth based on the time of the day).
13107 Changes in version 0.2.0.8-alpha - 2007-10-12
13108 This eighth development snapshot fixes a crash bug that's been bothering
13109 us since February 2007, lets bridge authorities store a list of bridge
13110 descriptors they've seen, gets v3 directory voting closer to working,
13111 starts caching v3 directory consensus documents on directory mirrors,
13112 and fixes a variety of smaller issues including some minor memory leaks.
13114 o Major features (router descriptor cache):
13115 - Store routers in a file called cached-descriptors instead of in
13116 cached-routers. Initialize cached-descriptors from cached-routers
13117 if the old format is around. The new format allows us to store
13118 annotations along with descriptors.
13119 - Use annotations to record the time we received each descriptor, its
13120 source, and its purpose.
13121 - Disable the SETROUTERPURPOSE controller command: it is now
13123 - Controllers should now specify cache=no or cache=yes when using
13124 the +POSTDESCRIPTOR command.
13125 - Bridge authorities now write bridge descriptors to disk, meaning
13126 we can export them to other programs and begin distributing them
13129 o Major features (directory authorities):
13130 - When a v3 authority is missing votes or signatures, it now tries
13132 - Directory authorities track weighted fractional uptime as well as
13133 weighted mean-time-between failures. WFU is suitable for deciding
13134 whether a node is "usually up", while MTBF is suitable for deciding
13135 whether a node is "likely to stay up." We need both, because
13136 "usually up" is a good requirement for guards, while "likely to
13137 stay up" is a good requirement for long-lived connections.
13139 o Major features (v3 directory system):
13140 - Caches now download v3 network status documents as needed,
13141 and download the descriptors listed in them.
13142 - All hosts now attempt to download and keep fresh v3 authority
13143 certificates, and re-attempt after failures.
13144 - More internal-consistency checks for vote parsing.
13146 o Major bugfixes (crashes):
13147 - If a connection is shut down abruptly because of something that
13148 happened inside connection_flushed_some(), do not call
13149 connection_finished_flushing(). Should fix bug 451. Bugfix on
13152 o Major bugfixes (performance):
13153 - Fix really bad O(n^2) performance when parsing a long list of
13154 routers: Instead of searching the entire list for an "extra-info "
13155 string which usually wasn't there, once for every routerinfo
13156 we read, just scan lines forward until we find one we like.
13158 - When we add data to a write buffer in response to the data on that
13159 write buffer getting low because of a flush, do not consider the
13160 newly added data as a candidate for immediate flushing, but rather
13161 make it wait until the next round of writing. Otherwise, we flush
13162 and refill recursively, and a single greedy TLS connection can
13163 eat all of our bandwidth. Bugfix on 0.1.2.7-alpha.
13165 o Minor features (v3 authority system):
13166 - Add more ways for tools to download the votes that lead to the
13168 - Send a 503 when low on bandwidth and a vote, consensus, or
13169 certificate is requested.
13170 - If-modified-since is now implemented properly for all kinds of
13171 certificate requests.
13173 o Minor bugfixes (network statuses):
13174 - Tweak the implementation of proposal 109 slightly: allow at most
13175 two Tor servers on the same IP address, except if it's the location
13176 of a directory authority, in which case allow five. Bugfix on
13179 o Minor bugfixes (controller):
13180 - When sending a status event to the controller telling it that an
13181 OR address is reachable, set the port correctly. (Previously we
13182 were reporting the dir port.) Bugfix on 0.1.2.x.
13184 o Minor bugfixes (v3 directory system):
13185 - Fix logic to look up a cert by its signing key digest. Bugfix on
13187 - Only change the reply to a vote to "OK" if it's not already
13188 set. This gets rid of annoying "400 OK" log messages, which may
13189 have been masking some deeper issue. Bugfix on 0.2.0.7-alpha.
13190 - When we get a valid consensus, recompute the voting schedule.
13191 - Base the valid-after time of a vote on the consensus voting
13192 schedule, not on our preferred schedule.
13193 - Make the return values and messages from signature uploads and
13194 downloads more sensible.
13195 - Fix a memory leak when serving votes and consensus documents, and
13196 another when serving certificates.
13198 o Minor bugfixes (performance):
13199 - Use a slightly simpler string hashing algorithm (copying Python's
13200 instead of Java's) and optimize our digest hashing algorithm to take
13201 advantage of 64-bit platforms and to remove some possibly-costly
13203 - Fix a minor memory leak whenever we parse guards from our state
13204 file. Bugfix on 0.2.0.7-alpha.
13205 - Fix a minor memory leak whenever we write out a file. Bugfix on
13207 - Fix a minor memory leak whenever a controller sends the PROTOCOLINFO
13208 command. Bugfix on 0.2.0.5-alpha.
13210 o Minor bugfixes (portability):
13211 - On some platforms, accept() can return a broken address. Detect
13212 this more quietly, and deal accordingly. Fixes bug 483.
13213 - Stop calling tor_strlower() on uninitialized memory in some cases.
13214 Bugfix in 0.2.0.7-alpha.
13216 o Minor bugfixes (usability):
13217 - Treat some 403 responses from directory servers as INFO rather than
13218 WARN-severity events.
13219 - It's not actually an error to find a non-pending entry in the DNS
13220 cache when canceling a pending resolve. Don't log unless stuff is
13221 fishy. Resolves bug 463.
13223 o Minor bugfixes (anonymity):
13224 - Never report that we've used more bandwidth than we're willing to
13225 relay: it leaks how much non-relay traffic we're using. Resolves
13227 - When looking for a circuit to cannibalize, consider family as well
13228 as identity. Fixes bug 438. Bugfix on 0.1.0.x (which introduced
13229 circuit cannibalization).
13231 o Code simplifications and refactoring:
13232 - Make a bunch of functions static. Remove some dead code.
13233 - Pull out about a third of the really big routerlist.c; put it in a
13234 new module, networkstatus.c.
13235 - Merge the extra fields in local_routerstatus_t back into
13236 routerstatus_t: we used to need one routerstatus_t for each
13237 authority's opinion, plus a local_routerstatus_t for the locally
13238 computed consensus opinion. To save space, we put the locally
13239 modified fields into local_routerstatus_t, and only the common
13240 stuff into routerstatus_t. But once v3 directories are in use,
13241 clients and caches will no longer need to hold authority opinions;
13242 thus, the rationale for keeping the types separate is now gone.
13243 - Make the code used to reschedule and reattempt downloads more
13245 - Turn all 'Are we a directory server/mirror?' logic into a call to
13247 - Remove the code to generate the oldest (v1) directory format.
13248 The code has been disabled since 0.2.0.5-alpha.
13251 Changes in version 0.2.0.7-alpha - 2007-09-21
13252 This seventh development snapshot makes bridges work again, makes bridge
13253 authorities work for the first time, fixes two huge performance flaws
13254 in hidden services, and fixes a variety of minor issues.
13256 o New directory authorities:
13257 - Set up moria1 and tor26 as the first v3 directory authorities. See
13258 doc/spec/dir-spec.txt for details on the new directory design.
13260 o Major bugfixes (crashes):
13261 - Fix possible segfaults in functions called from
13262 rend_process_relay_cell(). Bugfix on 0.1.2.x.
13264 o Major bugfixes (bridges):
13265 - Fix a bug that made servers send a "404 Not found" in response to
13266 attempts to fetch their server descriptor. This caused Tor servers
13267 to take many minutes to establish reachability for their DirPort,
13268 and it totally crippled bridges. Bugfix on 0.2.0.5-alpha.
13269 - Make "UpdateBridgesFromAuthority" torrc option work: when bridge
13270 users configure that and specify a bridge with an identity
13271 fingerprint, now they will lookup the bridge descriptor at the
13272 default bridge authority via a one-hop tunnel, but once circuits
13273 are established they will switch to a three-hop tunnel for later
13274 connections to the bridge authority. Bugfix in 0.2.0.3-alpha.
13276 o Major bugfixes (hidden services):
13277 - Hidden services were choosing introduction points uniquely by
13278 hexdigest, but when constructing the hidden service descriptor
13279 they merely wrote the (potentially ambiguous) nickname.
13280 - Clients now use the v2 intro format for hidden service
13281 connections: they specify their chosen rendezvous point by identity
13282 digest rather than by (potentially ambiguous) nickname. Both
13283 are bugfixes on 0.1.2.x, and they could speed up hidden service
13284 connections dramatically. Thanks to Karsten Loesing.
13286 o Minor features (security):
13287 - As a client, do not believe any server that tells us that an
13288 address maps to an internal address space.
13289 - Make it possible to enable HashedControlPassword and
13290 CookieAuthentication at the same time.
13292 o Minor features (guard nodes):
13293 - Tag every guard node in our state file with the version that
13294 we believe added it, or with our own version if we add it. This way,
13295 if a user temporarily runs an old version of Tor and then switches
13296 back to a new one, she doesn't automatically lose her guards.
13298 o Minor features (speed):
13299 - When implementing AES counter mode, update only the portions of the
13300 counter buffer that need to change, and don't keep separate
13301 network-order and host-order counters when they are the same (i.e.,
13302 on big-endian hosts.)
13304 o Minor features (controller):
13305 - Accept LF instead of CRLF on controller, since some software has a
13306 hard time generating real Internet newlines.
13307 - Add GETINFO values for the server status events
13308 "REACHABILITY_SUCCEEDED" and "GOOD_SERVER_DESCRIPTOR". Patch from
13311 o Removed features:
13312 - Routers no longer include bandwidth-history lines in their
13313 descriptors; this information is already available in extra-info
13314 documents, and including it in router descriptors took up 60%
13315 (!) of compressed router descriptor downloads. Completes
13316 implementation of proposal 104.
13317 - Remove the contrib scripts ExerciseServer.py, PathDemo.py,
13318 and TorControl.py, as they use the old v0 controller protocol,
13319 and are obsoleted by TorFlow anyway.
13320 - Drop support for v1 rendezvous descriptors, since we never used
13321 them anyway, and the code has probably rotted by now. Based on
13322 patch from Karsten Loesing.
13323 - On OSX, stop warning the user that kqueue support in libevent is
13324 "experimental", since it seems to have worked fine for ages.
13327 - When generating information telling us how to extend to a given
13328 router, do not try to include the nickname if it is absent. Fixes
13329 bug 467. Bugfix on 0.2.0.3-alpha.
13330 - Fix a user-triggerable (but not remotely-triggerable) segfault
13331 in expand_filename(). Bugfix on 0.1.2.x.
13332 - Fix a memory leak when freeing incomplete requests from DNSPort.
13333 Found by Niels Provos with valgrind. Bugfix on 0.2.0.1-alpha.
13334 - Don't try to access (or alter) the state file when running
13335 --list-fingerprint or --verify-config or --hash-password. (Resolves
13336 bug 499.) Bugfix on 0.1.2.x.
13337 - Servers used to decline to publish their DirPort if their
13338 BandwidthRate, RelayBandwidthRate, or MaxAdvertisedBandwidth
13339 were below a threshold. Now they only look at BandwidthRate and
13340 RelayBandwidthRate. Bugfix on 0.1.2.x.
13341 - Remove an optimization in the AES counter-mode code that assumed
13342 that the counter never exceeded 2^68. When the counter can be set
13343 arbitrarily as an IV (as it is by Karsten's new hidden services
13344 code), this assumption no longer holds. Bugfix on 0.1.2.x.
13345 - Resume listing "AUTHORITY" flag for authorities in network status.
13346 Bugfix on 0.2.0.3-alpha; reported by Alex de Joode.
13348 o Code simplifications and refactoring:
13349 - Revamp file-writing logic so we don't need to have the entire
13350 contents of a file in memory at once before we write to disk. Tor,
13352 - Turn "descriptor store" into a full-fledged type.
13353 - Move all NT services code into a separate source file.
13354 - Unify all code that computes medians, percentile elements, etc.
13355 - Get rid of a needless malloc when parsing address policies.
13358 Changes in version 0.1.2.17 - 2007-08-30
13359 Tor 0.1.2.17 features a new Vidalia version in the Windows and OS
13360 X bundles. Vidalia 0.0.14 makes authentication required for the
13361 ControlPort in the default configuration, which addresses important
13362 security risks. Everybody who uses Vidalia (or another controller)
13365 In addition, this Tor update fixes major load balancing problems with
13366 path selection, which should speed things up a lot once many people
13369 o Major bugfixes (security):
13370 - We removed support for the old (v0) control protocol. It has been
13371 deprecated since Tor 0.1.1.1-alpha, and keeping it secure has
13372 become more of a headache than it's worth.
13374 o Major bugfixes (load balancing):
13375 - When choosing nodes for non-guard positions, weight guards
13376 proportionally less, since they already have enough load. Patch
13378 - Raise the "max believable bandwidth" from 1.5MB/s to 10MB/s. This
13379 will allow fast Tor servers to get more attention.
13380 - When we're upgrading from an old Tor version, forget our current
13381 guards and pick new ones according to the new weightings. These
13382 three load balancing patches could raise effective network capacity
13383 by a factor of four. Thanks to Mike Perry for measurements.
13385 o Major bugfixes (stream expiration):
13386 - Expire not-yet-successful application streams in all cases if
13387 they've been around longer than SocksTimeout. Right now there are
13388 some cases where the stream will live forever, demanding a new
13389 circuit every 15 seconds. Fixes bug 454; reported by lodger.
13391 o Minor features (controller):
13392 - Add a PROTOCOLINFO controller command. Like AUTHENTICATE, it
13393 is valid before any authentication has been received. It tells
13394 a controller what kind of authentication is expected, and what
13395 protocol is spoken. Implements proposal 119.
13397 o Minor bugfixes (performance):
13398 - Save on most routerlist_assert_ok() calls in routerlist.c, thus
13399 greatly speeding up loading cached-routers from disk on startup.
13400 - Disable sentinel-based debugging for buffer code: we squashed all
13401 the bugs that this was supposed to detect a long time ago, and now
13402 its only effect is to change our buffer sizes from nice powers of
13403 two (which platform mallocs tend to like) to values slightly over
13404 powers of two (which make some platform mallocs sad).
13406 o Minor bugfixes (misc):
13407 - If exit bandwidth ever exceeds one third of total bandwidth, then
13408 use the correct formula to weight exit nodes when choosing paths.
13409 Based on patch from Mike Perry.
13410 - Choose perfectly fairly among routers when choosing by bandwidth and
13411 weighting by fraction of bandwidth provided by exits. Previously, we
13412 would choose with only approximate fairness, and correct ourselves
13413 if we ran off the end of the list.
13414 - If we require CookieAuthentication but we fail to write the
13415 cookie file, we would warn but not exit, and end up in a state
13416 where no controller could authenticate. Now we exit.
13417 - If we require CookieAuthentication, stop generating a new cookie
13418 every time we change any piece of our config.
13419 - Refuse to start with certain directory authority keys, and
13420 encourage people using them to stop.
13421 - Terminate multi-line control events properly. Original patch
13423 - Fix a minor memory leak when we fail to find enough suitable
13424 servers to choose a circuit.
13425 - Stop leaking part of the descriptor when we run into a particularly
13426 unparseable piece of it.
13429 Changes in version 0.2.0.6-alpha - 2007-08-26
13430 This sixth development snapshot features a new Vidalia version in the
13431 Windows and OS X bundles. Vidalia 0.0.14 makes authentication required for
13432 the ControlPort in the default configuration, which addresses important
13435 In addition, this snapshot fixes major load balancing problems
13436 with path selection, which should speed things up a lot once many
13437 people have upgraded. The directory authorities also use a new
13438 mean-time-between-failure approach to tracking which servers are stable,
13439 rather than just looking at the most recent uptime.
13441 o New directory authorities:
13442 - Set up Tonga as the default bridge directory authority.
13445 - Directory authorities now track servers by weighted
13446 mean-times-between-failures. When we have 4 or more days of data,
13447 use measured MTBF rather than declared uptime to decide whether
13448 to call a router Stable. Implements proposal 108.
13450 o Major bugfixes (load balancing):
13451 - When choosing nodes for non-guard positions, weight guards
13452 proportionally less, since they already have enough load. Patch
13454 - Raise the "max believable bandwidth" from 1.5MB/s to 10MB/s. This
13455 will allow fast Tor servers to get more attention.
13456 - When we're upgrading from an old Tor version, forget our current
13457 guards and pick new ones according to the new weightings. These
13458 three load balancing patches could raise effective network capacity
13459 by a factor of four. Thanks to Mike Perry for measurements.
13461 o Major bugfixes (descriptor parsing):
13462 - Handle unexpected whitespace better in malformed descriptors. Bug
13463 found using Benedikt Boss's new Tor fuzzer! Bugfix on 0.2.0.x.
13466 - There is now an ugly, temporary "desc/all-recent-extrainfo-hack"
13467 GETINFO for Torstat to use until it can switch to using extrainfos.
13468 - Optionally (if built with -DEXPORTMALLINFO) export the output
13469 of mallinfo via http, as tor/mallinfo.txt. Only accessible
13473 - Do not intermix bridge routers with controller-added
13474 routers. (Bugfix on 0.2.0.x)
13475 - Do not fail with an assert when accept() returns an unexpected
13476 address family. Addresses but does not wholly fix bug 483. (Bugfix
13478 - Let directory authorities startup even when they can't generate
13479 a descriptor immediately, e.g. because they don't know their
13481 - Stop putting the authentication cookie in a file called "0"
13482 in your working directory if you don't specify anything for the
13483 new CookieAuthFile option. Reported by Matt Edman.
13484 - Make it possible to read the PROTOCOLINFO response in a way that
13485 conforms to our control-spec. Reported by Matt Edman.
13486 - Fix a minor memory leak when we fail to find enough suitable
13487 servers to choose a circuit. Bugfix on 0.1.2.x.
13488 - Stop leaking part of the descriptor when we run into a particularly
13489 unparseable piece of it. Bugfix on 0.1.2.x.
13490 - Unmap the extrainfo cache file on exit.
13493 Changes in version 0.2.0.5-alpha - 2007-08-19
13494 This fifth development snapshot fixes compilation on Windows again;
13495 fixes an obnoxious client-side bug that slowed things down and put
13496 extra load on the network; gets us closer to using the v3 directory
13497 voting scheme; makes it easier for Tor controllers to use cookie-based
13498 authentication; and fixes a variety of other bugs.
13500 o Removed features:
13501 - Version 1 directories are no longer generated in full. Instead,
13502 authorities generate and serve "stub" v1 directories that list
13503 no servers. This will stop Tor versions 0.1.0.x and earlier from
13504 working, but (for security reasons) nobody should be running those
13507 o Major bugfixes (compilation, 0.2.0.x):
13508 - Try to fix Win32 compilation again: improve checking for IPv6 types.
13509 - Try to fix MSVC compilation: build correctly on platforms that do
13510 not define s6_addr16 or s6_addr32.
13511 - Fix compile on platforms without getaddrinfo: bug found by Li-Hui
13514 o Major bugfixes (stream expiration):
13515 - Expire not-yet-successful application streams in all cases if
13516 they've been around longer than SocksTimeout. Right now there are
13517 some cases where the stream will live forever, demanding a new
13518 circuit every 15 seconds. Bugfix on 0.1.2.7-alpha; fixes bug 454;
13519 reported by lodger.
13521 o Minor features (directory servers):
13522 - When somebody requests a list of statuses or servers, and we have
13523 none of those, return a 404 rather than an empty 200.
13525 o Minor features (directory voting):
13526 - Store v3 consensus status consensuses on disk, and reload them
13529 o Minor features (security):
13530 - Warn about unsafe ControlPort configurations.
13531 - Refuse to start with certain directory authority keys, and
13532 encourage people using them to stop.
13534 o Minor features (controller):
13535 - Add a PROTOCOLINFO controller command. Like AUTHENTICATE, it
13536 is valid before any authentication has been received. It tells
13537 a controller what kind of authentication is expected, and what
13538 protocol is spoken. Implements proposal 119.
13539 - New config option CookieAuthFile to choose a new location for the
13540 cookie authentication file, and config option
13541 CookieAuthFileGroupReadable to make it group-readable.
13543 o Minor features (unit testing):
13544 - Add command-line arguments to unit-test executable so that we can
13545 invoke any chosen test from the command line rather than having
13546 to run the whole test suite at once; and so that we can turn on
13547 logging for the unit tests.
13549 o Minor bugfixes (on 0.1.2.x):
13550 - If we require CookieAuthentication but we fail to write the
13551 cookie file, we would warn but not exit, and end up in a state
13552 where no controller could authenticate. Now we exit.
13553 - If we require CookieAuthentication, stop generating a new cookie
13554 every time we change any piece of our config.
13555 - When loading bandwidth history, do not believe any information in
13556 the future. Fixes bug 434.
13557 - When loading entry guard information, do not believe any information
13559 - When we have our clock set far in the future and generate an
13560 onion key, then re-set our clock to be correct, we should not stop
13561 the onion key from getting rotated.
13562 - Clean up torrc sample config file.
13563 - Do not automatically run configure from autogen.sh. This
13564 non-standard behavior tended to annoy people who have built other
13567 o Minor bugfixes (on 0.2.0.x):
13568 - Fix a bug with AutomapHostsOnResolve that would always cause
13569 the second request to fail. Bug reported by Kate. Bugfix on
13571 - Fix a bug in ADDRMAP controller replies that would sometimes
13572 try to print a NULL. Patch from tup.
13573 - Read v3 directory authority keys from the right location.
13574 - Numerous bugfixes to directory voting code.
13577 Changes in version 0.1.2.16 - 2007-08-01
13578 Tor 0.1.2.16 fixes a critical security vulnerability that allows a
13579 remote attacker in certain situations to rewrite the user's torrc
13580 configuration file. This can completely compromise anonymity of users
13581 in most configurations, including those running the Vidalia bundles,
13582 TorK, etc. Or worse.
13584 o Major security fixes:
13585 - Close immediately after missing authentication on control port;
13586 do not allow multiple authentication attempts.
13589 Changes in version 0.2.0.4-alpha - 2007-08-01
13590 This fourth development snapshot fixes a critical security vulnerability
13591 for most users, specifically those running Vidalia, TorK, etc. Everybody
13592 should upgrade to either 0.1.2.16 or 0.2.0.4-alpha.
13594 o Major security fixes:
13595 - Close immediately after missing authentication on control port;
13596 do not allow multiple authentication attempts.
13598 o Major bugfixes (compilation):
13599 - Fix win32 compilation: apparently IN_ADDR and IN6_ADDR are already
13602 o Minor features (performance):
13603 - Be even more aggressive about releasing RAM from small
13604 empty buffers. Thanks to our free-list code, this shouldn't be too
13605 performance-intensive.
13606 - Disable sentinel-based debugging for buffer code: we squashed all
13607 the bugs that this was supposed to detect a long time ago, and
13608 now its only effect is to change our buffer sizes from nice
13609 powers of two (which platform mallocs tend to like) to values
13610 slightly over powers of two (which make some platform mallocs sad).
13611 - Log malloc statistics from mallinfo() on platforms where it
13615 Changes in version 0.2.0.3-alpha - 2007-07-29
13616 This third development snapshot introduces new experimental
13617 blocking-resistance features and a preliminary version of the v3
13618 directory voting design, and includes many other smaller features
13622 - The first pieces of our "bridge" design for blocking-resistance
13623 are implemented. People can run bridge directory authorities;
13624 people can run bridges; and people can configure their Tor clients
13625 with a set of bridges to use as the first hop into the Tor network.
13626 See http://archives.seul.org/or/talk/Jul-2007/msg00249.html for
13628 - Create listener connections before we setuid to the configured
13629 User and Group. Now non-Windows users can choose port values
13630 under 1024, start Tor as root, and have Tor bind those ports
13631 before it changes to another UID. (Windows users could already
13633 - Added a new ConstrainedSockets config option to set SO_SNDBUF and
13634 SO_RCVBUF on TCP sockets. Hopefully useful for Tor servers running
13635 on "vserver" accounts. (Patch from coderman.)
13636 - Be even more aggressive about separating local traffic from relayed
13637 traffic when RelayBandwidthRate is set. (Refines proposal 111.)
13639 o Major features (experimental):
13640 - First cut of code for "v3 dir voting": directory authorities will
13641 vote on a common network status document rather than each publishing
13642 their own opinion. This code needs more testing and more corner-case
13643 handling before it's ready for use.
13646 - Directory authorities now call routers Fast if their bandwidth is
13647 at least 100KB/s, and consider their bandwidth adequate to be a
13648 Guard if it is at least 250KB/s, no matter the medians. This fix
13649 complements proposal 107. [Bugfix on 0.1.2.x]
13650 - Directory authorities now never mark more than 3 servers per IP as
13651 Valid and Running. (Implements proposal 109, by Kevin Bauer and
13653 - Minor change to organizationName and commonName generation
13654 procedures in TLS certificates during Tor handshakes, to invalidate
13655 some earlier censorware approaches. This is not a long-term
13656 solution, but applying it will give us a bit of time to look into
13657 the epidemiology of countermeasures as they spread.
13659 o Major bugfixes (directory):
13660 - Rewrite directory tokenization code to never run off the end of
13661 a string. Fixes bug 455. Patch from croup. [Bugfix on 0.1.2.x]
13663 o Minor features (controller):
13664 - Add a SOURCE_ADDR field to STREAM NEW events so that controllers can
13665 match requests to applications. (Patch from Robert Hogan.)
13666 - Report address and port correctly on connections to DNSPort. (Patch
13667 from Robert Hogan.)
13668 - Add a RESOLVE command to launch hostname lookups. (Original patch
13669 from Robert Hogan.)
13670 - Add GETINFO status/enough-dir-info to let controllers tell whether
13671 Tor has downloaded sufficient directory information. (Patch
13673 - You can now use the ControlSocket option to tell Tor to listen for
13674 controller connections on Unix domain sockets on systems that
13675 support them. (Patch from Peter Palfrader.)
13676 - STREAM NEW events are generated for DNSPort requests and for
13677 tunneled directory connections. (Patch from Robert Hogan.)
13678 - New "GETINFO address-mappings/*" command to get address mappings
13679 with expiry information. "addr-mappings/*" is now deprecated.
13682 o Minor features (misc):
13683 - Merge in some (as-yet-unused) IPv6 address manipulation code. (Patch
13685 - The tor-gencert tool for v3 directory authorities now creates all
13686 files as readable to the file creator only, and write-protects
13687 the authority identity key.
13688 - When dumping memory usage, list bytes used in buffer memory
13690 - When running with dmalloc, dump more stats on hup and on exit.
13691 - Directory authorities now fail quickly and (relatively) harmlessly
13692 if they generate a network status document that is somehow
13695 o Traffic load balancing improvements:
13696 - If exit bandwidth ever exceeds one third of total bandwidth, then
13697 use the correct formula to weight exit nodes when choosing paths.
13698 (Based on patch from Mike Perry.)
13699 - Choose perfectly fairly among routers when choosing by bandwidth and
13700 weighting by fraction of bandwidth provided by exits. Previously, we
13701 would choose with only approximate fairness, and correct ourselves
13702 if we ran off the end of the list. [Bugfix on 0.1.2.x]
13704 o Performance improvements:
13705 - Be more aggressive with freeing buffer RAM or putting it on the
13707 - Use Critical Sections rather than Mutexes for synchronizing threads
13708 on win32; Mutexes are heavier-weight, and designed for synchronizing
13711 o Deprecated and removed features:
13712 - RedirectExits is now deprecated.
13713 - Stop allowing address masks that do not correspond to bit prefixes.
13714 We have warned about these for a really long time; now it's time
13715 to reject them. (Patch from croup.)
13717 o Minor bugfixes (directory):
13718 - Fix another crash bug related to extra-info caching. (Bug found by
13719 Peter Palfrader.) [Bugfix on 0.2.0.2-alpha]
13720 - Directories no longer return a "304 not modified" when they don't
13721 have the networkstatus the client asked for. Also fix a memory
13722 leak when returning 304 not modified. [Bugfixes on 0.2.0.2-alpha]
13723 - We had accidentally labelled 0.1.2.x directory servers as not
13724 suitable for begin_dir requests, and had labelled no directory
13725 servers as suitable for uploading extra-info documents. [Bugfix
13728 o Minor bugfixes (dns):
13729 - Fix a crash when DNSPort is set more than once. (Patch from Robert
13730 Hogan.) [Bugfix on 0.2.0.2-alpha]
13731 - Add DNSPort connections to the global connection list, so that we
13732 can time them out correctly. (Bug found by Robert Hogan.) [Bugfix
13734 - Fix a dangling reference that could lead to a crash when DNSPort is
13735 changed or closed (Patch from Robert Hogan.) [Bugfix on
13738 o Minor bugfixes (controller):
13739 - Provide DNS expiry times in GMT, not in local time. For backward
13740 compatibility, ADDRMAP events only provide GMT expiry in an extended
13741 field. "GETINFO address-mappings" always does the right thing.
13742 - Use CRLF line endings properly in NS events.
13743 - Terminate multi-line control events properly. (Original patch
13744 from tup.) [Bugfix on 0.1.2.x-alpha]
13745 - Do not include spaces in SOURCE_ADDR fields in STREAM
13746 events. Resolves bug 472. [Bugfix on 0.2.0.x-alpha]
13749 Changes in version 0.1.2.15 - 2007-07-17
13750 Tor 0.1.2.15 fixes several crash bugs, fixes some anonymity-related
13751 problems, fixes compilation on BSD, and fixes a variety of other
13752 bugs. Everybody should upgrade.
13754 o Major bugfixes (compilation):
13755 - Fix compile on FreeBSD/NetBSD/OpenBSD. Oops.
13757 o Major bugfixes (crashes):
13758 - Try even harder not to dereference the first character after
13759 an mmap(). Reported by lodger.
13760 - Fix a crash bug in directory authorities when we re-number the
13761 routerlist while inserting a new router.
13762 - When the cached-routers file is an even multiple of the page size,
13763 don't run off the end and crash. (Fixes bug 455; based on idea
13765 - Fix eventdns.c behavior on Solaris: It is critical to include
13766 orconfig.h _before_ sys/types.h, so that we can get the expected
13767 definition of _FILE_OFFSET_BITS.
13769 o Major bugfixes (security):
13770 - Fix a possible buffer overrun when using BSD natd support. Bug
13772 - When sending destroy cells from a circuit's origin, don't include
13773 the reason for tearing down the circuit. The spec says we didn't,
13774 and now we actually don't. Reported by lodger.
13775 - Keep streamids from different exits on a circuit separate. This
13776 bug may have allowed other routers on a given circuit to inject
13777 cells into streams. Reported by lodger; fixes bug 446.
13778 - If there's a never-before-connected-to guard node in our list,
13779 never choose any guards past it. This way we don't expand our
13780 guard list unless we need to.
13782 o Minor bugfixes (guard nodes):
13783 - Weight guard selection by bandwidth, so that low-bandwidth nodes
13784 don't get overused as guards.
13786 o Minor bugfixes (directory):
13787 - Correctly count the number of authorities that recommend each
13788 version. Previously, we were under-counting by 1.
13789 - Fix a potential crash bug when we load many server descriptors at
13790 once and some of them make others of them obsolete. Fixes bug 458.
13792 o Minor bugfixes (hidden services):
13793 - Stop tearing down the whole circuit when the user asks for a
13794 connection to a port that the hidden service didn't configure.
13797 o Minor bugfixes (misc):
13798 - On Windows, we were preventing other processes from reading
13799 cached-routers while Tor was running. Reported by janbar.
13800 - Fix a possible (but very unlikely) bug in picking routers by
13801 bandwidth. Add a log message to confirm that it is in fact
13802 unlikely. Patch from lodger.
13803 - Backport a couple of memory leak fixes.
13804 - Backport miscellaneous cosmetic bugfixes.
13807 Changes in version 0.2.0.2-alpha - 2007-06-02
13808 o Major bugfixes on 0.2.0.1-alpha:
13809 - Fix an assertion failure related to servers without extra-info digests.
13810 Resolves bugs 441 and 442.
13812 o Minor features (directory):
13813 - Support "If-Modified-Since" when answering HTTP requests for
13814 directories, running-routers documents, and network-status documents.
13815 (There's no need to support it for router descriptors, since those
13816 are downloaded by descriptor digest.)
13818 o Minor build issues:
13819 - Clear up some MIPSPro compiler warnings.
13820 - When building from a tarball on a machine that happens to have SVK
13821 installed, report the micro-revision as whatever version existed
13822 in the tarball, not as "x".
13825 Changes in version 0.2.0.1-alpha - 2007-06-01
13826 This early development snapshot provides new features for people running
13827 Tor as both a client and a server (check out the new RelayBandwidth
13828 config options); lets Tor run as a DNS proxy; and generally moves us
13829 forward on a lot of fronts.
13831 o Major features, server usability:
13832 - New config options RelayBandwidthRate and RelayBandwidthBurst:
13833 a separate set of token buckets for relayed traffic. Right now
13834 relayed traffic is defined as answers to directory requests, and
13835 OR connections that don't have any local circuits on them.
13837 o Major features, client usability:
13838 - A client-side DNS proxy feature to replace the need for
13839 dns-proxy-tor: Just set "DNSPort 9999", and Tor will now listen
13840 for DNS requests on port 9999, use the Tor network to resolve them
13841 anonymously, and send the reply back like a regular DNS server.
13842 The code still only implements a subset of DNS.
13843 - Make PreferTunneledDirConns and TunnelDirConns work even when
13844 we have no cached directory info. This means Tor clients can now
13845 do all of their connections protected by TLS.
13847 o Major features, performance and efficiency:
13848 - Directory authorities accept and serve "extra info" documents for
13849 routers. These documents contain fields from router descriptors
13850 that aren't usually needed, and that use a lot of excess
13851 bandwidth. Once these fields are removed from router descriptors,
13852 the bandwidth savings should be about 60%. [Partially implements
13854 - Servers upload extra-info documents to any authority that accepts
13855 them. Authorities (and caches that have been configured to download
13856 extra-info documents) download them as needed. [Partially implements
13858 - Change the way that Tor buffers data that it is waiting to write.
13859 Instead of queueing data cells in an enormous ring buffer for each
13860 client->OR or OR->OR connection, we now queue cells on a separate
13861 queue for each circuit. This lets us use less slack memory, and
13862 will eventually let us be smarter about prioritizing different kinds
13864 - Use memory pools to allocate cells with better speed and memory
13865 efficiency, especially on platforms where malloc() is inefficient.
13866 - Stop reading on edge connections when their corresponding circuit
13867 buffers are full; start again as the circuits empty out.
13869 o Major features, other:
13870 - Add an HSAuthorityRecordStats option that hidden service authorities
13871 can use to track statistics of overall hidden service usage without
13872 logging information that would be very useful to an attacker.
13873 - Start work implementing multi-level keys for directory authorities:
13874 Add a standalone tool to generate key certificates. (Proposal 103.)
13877 - Directory authorities now call routers Stable if they have an
13878 uptime of at least 30 days, even if that's not the median uptime
13879 in the network. Implements proposal 107, suggested by Kevin Bauer
13882 o Minor fixes (resource management):
13883 - Count the number of open sockets separately from the number
13884 of active connection_t objects. This will let us avoid underusing
13885 our allocated connection limit.
13886 - We no longer use socket pairs to link an edge connection to an
13887 anonymous directory connection or a DirPort test connection.
13888 Instead, we track the link internally and transfer the data
13889 in-process. This saves two sockets per "linked" connection (at the
13890 client and at the server), and avoids the nasty Windows socketpair()
13892 - Keep unused 4k and 16k buffers on free lists, rather than wasting 8k
13893 for every single inactive connection_t. Free items from the
13894 4k/16k-buffer free lists when they haven't been used for a while.
13896 o Minor features (build):
13897 - Make autoconf search for libevent, openssl, and zlib consistently.
13898 - Update deprecated macros in configure.in.
13899 - When warning about missing headers, tell the user to let us
13900 know if the compile succeeds anyway, so we can downgrade the
13902 - Include the current subversion revision as part of the version
13903 string: either fetch it directly if we're in an SVN checkout, do
13904 some magic to guess it if we're in an SVK checkout, or use
13905 the last-detected version if we're building from a .tar.gz.
13906 Use this version consistently in log messages.
13908 o Minor features (logging):
13909 - Always prepend "Bug: " to any log message about a bug.
13910 - Put a platform string (e.g. "Linux i686") in the startup log
13911 message, so when people paste just their logs, we know if it's
13912 OpenBSD or Windows or what.
13913 - When logging memory usage, break down memory used in buffers by
13916 o Minor features (directory system):
13917 - New config option V2AuthoritativeDirectory that all directory
13918 authorities should set. This will let future authorities choose
13919 not to serve V2 directory information.
13920 - Directory authorities allow multiple router descriptors and/or extra
13921 info documents to be uploaded in a single go. This will make
13922 implementing proposal 104 simpler.
13924 o Minor features (controller):
13925 - Add a new config option __DisablePredictedCircuits designed for
13926 use by the controller, when we don't want Tor to build any circuits
13928 - Let the controller specify HOP=%d as an argument to ATTACHSTREAM,
13929 so we can exit from the middle of the circuit.
13930 - Implement "getinfo status/circuit-established".
13931 - Implement "getinfo status/version/..." so a controller can tell
13932 whether the current version is recommended, and whether any versions
13933 are good, and how many authorities agree. (Patch from shibz.)
13935 o Minor features (hidden services):
13936 - Allow multiple HiddenServicePort directives with the same virtual
13937 port; when they occur, the user is sent round-robin to one
13938 of the target ports chosen at random. Partially fixes bug 393 by
13939 adding limited ad-hoc round-robining.
13941 o Minor features (other):
13943 - Add a new AutomapHostsOnResolve option: when it is enabled, any
13944 resolve request for hosts matching a given pattern causes Tor to
13945 generate an internal virtual address mapping for that host. This
13946 allows DNSPort to work sensibly with hidden service users. By
13947 default, .exit and .onion addresses are remapped; the list of
13948 patterns can be reconfigured with AutomapHostsSuffixes.
13949 - Add an "-F" option to tor-resolve to force a resolve for a .onion
13950 address. Thanks to the AutomapHostsOnResolve option, this is no
13951 longer a completely silly thing to do.
13952 - If Tor is invoked from something that isn't a shell (e.g. Vidalia),
13953 now we expand "-f ~/.tor/torrc" correctly. Suggested by Matt Edman.
13954 - Treat "2gb" when given in torrc for a bandwidth as meaning 2gb,
13955 minus 1 byte: the actual maximum declared bandwidth.
13957 o Removed features:
13958 - Removed support for the old binary "version 0" controller protocol.
13959 This has been deprecated since 0.1.1, and warnings have been issued
13960 since 0.1.2. When we encounter a v0 control message, we now send
13961 back an error and close the connection.
13962 - Remove the old "dns worker" server DNS code: it hasn't been default
13963 since 0.1.2.2-alpha, and all the servers seem to be using the new
13966 o Minor bugfixes (portability):
13967 - Even though Windows is equally happy with / and \ as path separators,
13968 try to use \ consistently on Windows and / consistently on Unix: it
13969 makes the log messages nicer.
13970 - Correctly report platform name on Windows 95 OSR2 and Windows 98 SE.
13971 - Read resolv.conf files correctly on platforms where read() returns
13972 partial results on small file reads.
13974 o Minor bugfixes (directory):
13975 - Correctly enforce that elements of directory objects do not appear
13976 more often than they are allowed to appear.
13977 - When we are reporting the DirServer line we just parsed, we were
13978 logging the second stanza of the key fingerprint, not the first.
13980 o Minor bugfixes (logging):
13981 - When we hit an EOF on a log (probably because we're shutting down),
13982 don't try to remove the log from the list: just mark it as
13983 unusable. (Bulletproofs against bug 222.)
13985 o Minor bugfixes (other):
13986 - In the exitlist script, only consider the most recently published
13987 server descriptor for each server. Also, when the user requests
13988 a list of servers that _reject_ connections to a given address,
13989 explicitly exclude the IPs that also have servers that accept
13990 connections to that address. (Resolves bug 405.)
13991 - Stop allowing hibernating servers to be "stable" or "fast".
13992 - On Windows, we were preventing other processes from reading
13993 cached-routers while Tor was running. (Reported by janbar)
13994 - Make the NodeFamilies config option work. (Reported by
13995 lodger -- it has never actually worked, even though we added it
13997 - Check return values from pthread_mutex functions.
13998 - Don't save non-general-purpose router descriptors to the disk cache,
13999 because we have no way of remembering what their purpose was when
14001 - Add even more asserts to hunt down bug 417.
14002 - Build without verbose warnings even on (not-yet-released) gcc 4.2.
14003 - Fix a possible (but very unlikely) bug in picking routers by bandwidth.
14004 Add a log message to confirm that it is in fact unlikely.
14006 o Minor bugfixes (controller):
14007 - Make 'getinfo fingerprint' return a 551 error if we're not a
14008 server, so we match what the control spec claims we do. Reported
14010 - Fix a typo in an error message when extendcircuit fails that
14011 caused us to not follow the \r\n-based delimiter protocol. Reported
14014 o Code simplifications and refactoring:
14015 - Stop passing around circuit_t and crypt_path_t pointers that are
14016 implicit in other procedure arguments.
14017 - Drop the old code to choke directory connections when the
14018 corresponding OR connections got full: thanks to the cell queue
14019 feature, OR conns don't get full any more.
14020 - Make dns_resolve() handle attaching connections to circuits
14021 properly, so the caller doesn't have to.
14022 - Rename wants_to_read and wants_to_write to read/write_blocked_on_bw.
14023 - Keep the connection array as a dynamic smartlist_t, rather than as
14024 a fixed-sized array. This is important, as the number of connections
14025 is becoming increasingly decoupled from the number of sockets.
14028 Changes in version 0.1.2.14 - 2007-05-25
14029 Tor 0.1.2.14 changes the addresses of two directory authorities (this
14030 change especially affects those who serve or use hidden services),
14031 and fixes several other crash- and security-related bugs.
14033 o Directory authority changes:
14034 - Two directory authorities (moria1 and moria2) just moved to new
14035 IP addresses. This change will particularly affect those who serve
14036 or use hidden services.
14038 o Major bugfixes (crashes):
14039 - If a directory server runs out of space in the connection table
14040 as it's processing a begin_dir request, it will free the exit stream
14041 but leave it attached to the circuit, leading to unpredictable
14042 behavior. (Reported by seeess, fixes bug 425.)
14043 - Fix a bug in dirserv_remove_invalid() that would cause authorities
14044 to corrupt memory under some really unlikely scenarios.
14045 - Tighten router parsing rules. (Bugs reported by Benedikt Boss.)
14046 - Avoid segfaults when reading from mmaped descriptor file. (Reported
14049 o Major bugfixes (security):
14050 - When choosing an entry guard for a circuit, avoid using guards
14051 that are in the same family as the chosen exit -- not just guards
14052 that are exactly the chosen exit. (Reported by lodger.)
14054 o Major bugfixes (resource management):
14055 - If a directory authority is down, skip it when deciding where to get
14056 networkstatus objects or descriptors. Otherwise we keep asking
14057 every 10 seconds forever. Fixes bug 384.
14058 - Count it as a failure if we fetch a valid network-status but we
14059 don't want to keep it. Otherwise we'll keep fetching it and keep
14060 not wanting to keep it. Fixes part of bug 422.
14061 - If all of our dirservers have given us bad or no networkstatuses
14062 lately, then stop hammering them once per minute even when we
14063 think they're failed. Fixes another part of bug 422.
14066 - Actually set the purpose correctly for descriptors inserted with
14067 purpose=controller.
14068 - When we have k non-v2 authorities in our DirServer config,
14069 we ignored the last k authorities in the list when updating our
14071 - Correctly back-off from requesting router descriptors that we are
14072 having a hard time downloading.
14073 - Read resolv.conf files correctly on platforms where read() returns
14074 partial results on small file reads.
14075 - Don't rebuild the entire router store every time we get 32K of
14076 routers: rebuild it when the journal gets very large, or when
14077 the gaps in the store get very large.
14080 - When routers publish SVN revisions in their router descriptors,
14081 authorities now include those versions correctly in networkstatus
14083 - Warn when using a version of libevent before 1.3b to run a server on
14084 OSX or BSD: these versions interact badly with userspace threads.
14087 Changes in version 0.1.2.13 - 2007-04-24
14088 This release features some major anonymity fixes, such as safer path
14089 selection; better client performance; faster bootstrapping, better
14090 address detection, and better DNS support for servers; write limiting as
14091 well as read limiting to make servers easier to run; and a huge pile of
14092 other features and bug fixes. The bundles also ship with Vidalia 0.0.11.
14094 Tor 0.1.2.13 is released in memory of Rob Levin (1955-2006), aka lilo
14095 of the Freenode IRC network, remembering his patience and vision for
14096 free speech on the Internet.
14099 - Fix a memory leak when we ask for "all" networkstatuses and we
14100 get one we don't recognize.
14101 - Add more asserts to hunt down bug 417.
14102 - Disable kqueue on OS X 10.3 and earlier, to fix bug 371.
14105 Changes in version 0.1.2.12-rc - 2007-03-16
14107 - Fix an infinite loop introduced in 0.1.2.7-alpha when we serve
14108 directory information requested inside Tor connections (i.e. via
14109 begin_dir cells). It only triggered when the same connection was
14110 serving other data at the same time. Reported by seeess.
14113 - When creating a circuit via the controller, send a 'launched'
14114 event when we're done, so we follow the spec better.
14117 Changes in version 0.1.2.11-rc - 2007-03-15
14118 o Minor bugfixes (controller), reported by daejees:
14119 - Correct the control spec to match how the code actually responds
14120 to 'getinfo addr-mappings/*'.
14121 - The control spec described a GUARDS event, but the code
14122 implemented a GUARD event. Standardize on GUARD, but let people
14123 ask for GUARDS too.
14126 Changes in version 0.1.2.10-rc - 2007-03-07
14127 o Major bugfixes (Windows):
14128 - Do not load the NT services library functions (which may not exist)
14129 just to detect if we're a service trying to shut down. Now we run
14130 on Win98 and friends again.
14132 o Minor bugfixes (other):
14133 - Clarify a couple of log messages.
14134 - Fix a misleading socks5 error number.
14137 Changes in version 0.1.2.9-rc - 2007-03-02
14138 o Major bugfixes (Windows):
14139 - On MinGW, use "%I64u" to printf/scanf 64-bit integers, instead
14140 of the usual GCC "%llu". This prevents a bug when saving 64-bit
14141 int configuration values: the high-order 32 bits would get
14142 truncated. In particular, we were being bitten by the default
14143 MaxAdvertisedBandwidth of 128 TB turning into 0. (Fixes bug 400
14144 and maybe also bug 397.)
14146 o Minor bugfixes (performance):
14147 - Use OpenSSL's AES implementation on platforms where it's faster.
14148 This could save us as much as 10% CPU usage.
14150 o Minor bugfixes (server):
14151 - Do not rotate onion key immediately after setting it for the first
14154 o Minor bugfixes (directory authorities):
14155 - Stop calling servers that have been hibernating for a long time
14156 "stable". Also, stop letting hibernating or obsolete servers affect
14157 uptime and bandwidth cutoffs.
14158 - Stop listing hibernating servers in the v1 directory.
14160 o Minor bugfixes (hidden services):
14161 - Upload hidden service descriptors slightly less often, to reduce
14162 load on authorities.
14164 o Minor bugfixes (other):
14165 - Fix an assert that could trigger if a controller quickly set then
14166 cleared EntryNodes. Bug found by Udo van den Heuvel.
14167 - On architectures where sizeof(int)>4, still clamp declarable bandwidth
14169 - Fix a potential race condition in the rpm installer. Found by
14171 - Try to fix eventdns warnings once and for all: do not treat a dns rcode
14172 of 2 as indicating that the server is completely bad; it sometimes
14173 means that the server is just bad for the request in question. (may fix
14174 the last of bug 326.)
14175 - Disable encrypted directory connections when we don't have a server
14176 descriptor for the destination. We'll get this working again in
14180 Changes in version 0.1.2.8-beta - 2007-02-26
14181 o Major bugfixes (crashes):
14182 - Stop crashing when the controller asks us to resetconf more than
14183 one config option at once. (Vidalia 0.0.11 does this.)
14184 - Fix a crash that happened on Win98 when we're given command-line
14185 arguments: don't try to load NT service functions from advapi32.dll
14186 except when we need them. (Bug introduced in 0.1.2.7-alpha;
14188 - Fix a longstanding obscure crash bug that could occur when
14189 we run out of DNS worker processes. (Resolves bug 390.)
14191 o Major bugfixes (hidden services):
14192 - Correctly detect whether hidden service descriptor downloads are
14193 in-progress. (Suggested by Karsten Loesing; fixes bug 399.)
14195 o Major bugfixes (accounting):
14196 - When we start during an accounting interval before it's time to wake
14197 up, remember to wake up at the correct time. (May fix bug 342.)
14199 o Minor bugfixes (controller):
14200 - Give the controller END_STREAM_REASON_DESTROY events _before_ we
14201 clear the corresponding on_circuit variable, and remember later
14202 that we don't need to send a redundant CLOSED event. Resolves part
14204 - Report events where a resolve succeeded or where we got a socks
14205 protocol error correctly, rather than calling both of them
14207 - Change reported stream target addresses to IP consistently when
14208 we finally get the IP from an exit node.
14209 - Send log messages to the controller even if they happen to be very
14212 o Minor bugfixes (other):
14213 - Display correct results when reporting which versions are
14214 recommended, and how recommended they are. (Resolves bug 383.)
14215 - Improve our estimates for directory bandwidth to be less random:
14216 guess that an unrecognized directory will have the average bandwidth
14217 from all known directories, not that it will have the average
14218 bandwidth from those directories earlier than it on the list.
14219 - If we start a server with ClientOnly 1, then set ClientOnly to 0
14220 and hup, stop triggering an assert based on an empty onion_key.
14221 - On platforms with no working mmap() equivalent, don't warn the
14222 user when cached-routers doesn't exist.
14223 - Warn the user when mmap() [or its equivalent] fails for some reason
14224 other than file-not-found.
14225 - Don't warn the user when cached-routers.new doesn't exist: that's
14226 perfectly fine when starting up for the first time.
14227 - When EntryNodes are configured, rebuild the guard list to contain,
14228 in order: the EntryNodes that were guards before; the rest of the
14229 EntryNodes; the nodes that were guards before.
14230 - Mask out all signals in sub-threads; only the libevent signal
14231 handler should be processing them. This should prevent some crashes
14232 on some machines using pthreads. (Patch from coderman.)
14233 - Fix switched arguments on memset in the implementation of
14234 tor_munmap() for systems with no mmap() call.
14235 - When Tor receives a router descriptor that it asked for, but
14236 no longer wants (because it has received fresh networkstatuses
14237 in the meantime), do not warn the user. Cache the descriptor if
14238 we're a cache; drop it if we aren't.
14239 - Make earlier entry guards _really_ get retried when the network
14241 - On a malformed DNS reply, always give an error to the corresponding
14243 - Build with recent libevents on platforms that do not define the
14244 nonstandard types "u_int8_t" and friends.
14246 o Minor features (controller):
14247 - Warn the user when an application uses the obsolete binary v0
14248 control protocol. We're planning to remove support for it during
14249 the next development series, so it's good to give people some
14251 - Add STREAM_BW events to report per-entry-stream bandwidth
14252 use. (Patch from Robert Hogan.)
14253 - Rate-limit SIGNEWNYM signals in response to controllers that
14254 impolitely generate them for every single stream. (Patch from
14255 mwenge; closes bug 394.)
14256 - Make REMAP stream events have a SOURCE (cache or exit), and
14257 make them generated in every case where we get a successful
14258 connected or resolved cell.
14260 o Minor bugfixes (performance):
14261 - Call router_have_min_dir_info half as often. (This is showing up in
14262 some profiles, but not others.)
14263 - When using GCC, make log_debug never get called at all, and its
14264 arguments never get evaluated, when no debug logs are configured.
14265 (This is showing up in some profiles, but not others.)
14268 - Remove some never-implemented options. Mark PathlenCoinWeight as
14270 - Implement proposal 106: Stop requiring clients to have well-formed
14271 certificates; stop checking nicknames in certificates. (Clients
14272 have certificates so that they can look like Tor servers, but in
14273 the future we might want to allow them to look like regular TLS
14274 clients instead. Nicknames in certificates serve no purpose other
14275 than making our protocol easier to recognize on the wire.)
14276 - Revise messages on handshake failure again to be even more clear about
14277 which are incoming connections and which are outgoing.
14278 - Discard any v1 directory info that's over 1 month old (for
14279 directories) or over 1 week old (for running-routers lists).
14280 - Do not warn when individual nodes in the configuration's EntryNodes,
14281 ExitNodes, etc are down: warn only when all possible nodes
14282 are down. (Fixes bug 348.)
14283 - Always remove expired routers and networkstatus docs before checking
14284 whether we have enough information to build circuits. (Fixes
14286 - Put a lower-bound on MaxAdvertisedBandwidth.
14289 Changes in version 0.1.2.7-alpha - 2007-02-06
14290 o Major bugfixes (rate limiting):
14291 - Servers decline directory requests much more aggressively when
14292 they're low on bandwidth. Otherwise they end up queueing more and
14293 more directory responses, which can't be good for latency.
14294 - But never refuse directory requests from local addresses.
14295 - Fix a memory leak when sending a 503 response for a networkstatus
14297 - Be willing to read or write on local connections (e.g. controller
14298 connections) even when the global rate limiting buckets are empty.
14299 - If our system clock jumps back in time, don't publish a negative
14300 uptime in the descriptor. Also, don't let the global rate limiting
14301 buckets go absurdly negative.
14302 - Flush local controller connection buffers periodically as we're
14303 writing to them, so we avoid queueing 4+ megabytes of data before
14306 o Major bugfixes (NT services):
14307 - Install as NT_AUTHORITY\LocalService rather than as SYSTEM; add a
14308 command-line flag so that admins can override the default by saying
14309 "tor --service install --user "SomeUser"". This will not affect
14310 existing installed services. Also, warn the user that the service
14311 will look for its configuration file in the service user's
14312 %appdata% directory. (We can't do the 'hardwire the user's appdata
14313 directory' trick any more, since we may not have read access to that
14316 o Major bugfixes (other):
14317 - Previously, we would cache up to 16 old networkstatus documents
14318 indefinitely, if they came from nontrusted authorities. Now we
14319 discard them if they are more than 10 days old.
14320 - Fix a crash bug in the presence of DNS hijacking (reported by Andrew
14322 - Detect and reject malformed DNS responses containing circular
14324 - If exits are rare enough that we're not marking exits as guards,
14325 ignore exit bandwidth when we're deciding the required bandwidth
14327 - When we're handling a directory connection tunneled over Tor,
14328 don't fill up internal memory buffers with all the data we want
14329 to tunnel; instead, only add it if the OR connection that will
14330 eventually receive it has some room for it. (This can lead to
14331 slowdowns in tunneled dir connections; a better solution will have
14332 to wait for 0.2.0.)
14334 o Minor bugfixes (dns):
14335 - Add some defensive programming to eventdns.c in an attempt to catch
14336 possible memory-stomping bugs.
14337 - Detect and reject DNS replies containing IPv4 or IPv6 records with
14338 an incorrect number of bytes. (Previously, we would ignore the
14340 - Fix as-yet-unused reverse IPv6 lookup code so it sends nybbles
14341 in the correct order, and doesn't crash.
14342 - Free memory held in recently-completed DNS lookup attempts on exit.
14343 This was not a memory leak, but may have been hiding memory leaks.
14344 - Handle TTL values correctly on reverse DNS lookups.
14345 - Treat failure to parse resolv.conf as an error.
14347 o Minor bugfixes (other):
14348 - Fix crash with "tor --list-fingerprint" (reported by seeess).
14349 - When computing clock skew from directory HTTP headers, consider what
14350 time it was when we finished asking for the directory, not what
14352 - Expire socks connections if they spend too long waiting for the
14353 handshake to finish. Previously we would let them sit around for
14354 days, if the connecting application didn't close them either.
14355 - And if the socks handshake hasn't started, don't send a
14356 "DNS resolve socks failed" handshake reply; just close it.
14357 - Stop using C functions that OpenBSD's linker doesn't like.
14358 - Don't launch requests for descriptors unless we have networkstatuses
14359 from at least half of the authorities. This delays the first
14360 download slightly under pathological circumstances, but can prevent
14361 us from downloading a bunch of descriptors we don't need.
14362 - Do not log IPs with TLS failures for incoming TLS
14363 connections. (Fixes bug 382.)
14364 - If the user asks to use invalid exit nodes, be willing to use
14366 - Stop using the reserved ac_cv namespace in our configure script.
14367 - Call stat() slightly less often; use fstat() when possible.
14368 - Refactor the way we handle pending circuits when an OR connection
14369 completes or fails, in an attempt to fix a rare crash bug.
14370 - Only rewrite a conn's address based on X-Forwarded-For: headers
14371 if it's a parseable public IP address; and stop adding extra quotes
14372 to the resulting address.
14375 - Weight directory requests by advertised bandwidth. Now we can
14376 let servers enable write limiting but still allow most clients to
14377 succeed at their directory requests. (We still ignore weights when
14378 choosing a directory authority; I hope this is a feature.)
14381 - Create a new file ReleaseNotes which was the old ChangeLog. The
14382 new ChangeLog file now includes the summaries for all development
14384 - Check for addresses with invalid characters at the exit as well
14385 as at the client, and warn less verbosely when they fail. You can
14386 override this by setting ServerDNSAllowNonRFC953Addresses to 1.
14387 - Adapt a patch from goodell to let the contrib/exitlist script
14388 take arguments rather than require direct editing.
14389 - Inform the server operator when we decide not to advertise a
14390 DirPort due to AccountingMax enabled or a low BandwidthRate. It
14391 was confusing Zax, so now we're hopefully more helpful.
14392 - Bring us one step closer to being able to establish an encrypted
14393 directory tunnel without knowing a descriptor first. Still not
14394 ready yet. As part of the change, now assume we can use a
14395 create_fast cell if we don't know anything about a router.
14396 - Allow exit nodes to use nameservers running on ports other than 53.
14397 - Servers now cache reverse DNS replies.
14398 - Add an --ignore-missing-torrc command-line option so that we can
14399 get the "use sensible defaults if the configuration file doesn't
14400 exist" behavior even when specifying a torrc location on the command
14403 o Minor features (controller):
14404 - Track reasons for OR connection failure; make these reasons
14405 available via the controller interface. (Patch from Mike Perry.)
14406 - Add a SOCKS_BAD_HOSTNAME client status event so controllers
14407 can learn when clients are sending malformed hostnames to Tor.
14408 - Clean up documentation for controller status events.
14409 - Add a REMAP status to stream events to note that a stream's
14410 address has changed because of a cached address or a MapAddress
14414 Changes in version 0.1.2.6-alpha - 2007-01-09
14416 - Fix an assert error introduced in 0.1.2.5-alpha: if a single TLS
14417 connection handles more than 4 gigs in either direction, we crash.
14418 - Fix an assert error introduced in 0.1.2.5-alpha: if we're an
14419 advertised exit node, somebody might try to exit from us when
14420 we're bootstrapping and before we've built our descriptor yet.
14421 Refuse the connection rather than crashing.
14424 - Warn if we (as a server) find that we've resolved an address that we
14425 weren't planning to resolve.
14426 - Warn that using select() on any libevent version before 1.1 will be
14427 unnecessarily slow (even for select()).
14428 - Flush ERR-level controller status events just like we currently
14429 flush ERR-level log events, so that a Tor shutdown doesn't prevent
14430 the controller from learning about current events.
14432 o Minor features (more controller status events):
14433 - Implement EXTERNAL_ADDRESS server status event so controllers can
14434 learn when our address changes.
14435 - Implement BAD_SERVER_DESCRIPTOR server status event so controllers
14436 can learn when directories reject our descriptor.
14437 - Implement SOCKS_UNKNOWN_PROTOCOL client status event so controllers
14438 can learn when a client application is speaking a non-socks protocol
14440 - Implement DANGEROUS_SOCKS client status event so controllers
14441 can learn when a client application is leaking DNS addresses.
14442 - Implement BUG general status event so controllers can learn when
14443 Tor is unhappy about its internal invariants.
14444 - Implement CLOCK_SKEW general status event so controllers can learn
14445 when Tor thinks the system clock is set incorrectly.
14446 - Implement GOOD_SERVER_DESCRIPTOR and ACCEPTED_SERVER_DESCRIPTOR
14447 server status events so controllers can learn when their descriptors
14448 are accepted by a directory.
14449 - Implement CHECKING_REACHABILITY and REACHABILITY_{SUCCEEDED|FAILED}
14450 server status events so controllers can learn about Tor's progress in
14451 deciding whether it's reachable from the outside.
14452 - Implement BAD_LIBEVENT general status event so controllers can learn
14453 when we have a version/method combination in libevent that needs to
14455 - Implement NAMESERVER_STATUS, NAMESERVER_ALL_DOWN, DNS_HIJACKED,
14456 and DNS_USELESS server status events so controllers can learn
14457 about changes to DNS server status.
14459 o Minor features (directory):
14460 - Authorities no longer recommend exits as guards if this would shift
14461 too much load to the exit nodes.
14464 Changes in version 0.1.2.5-alpha - 2007-01-06
14466 - Enable write limiting as well as read limiting. Now we sacrifice
14467 capacity if we're pushing out lots of directory traffic, rather
14468 than overrunning the user's intended bandwidth limits.
14469 - Include TLS overhead when counting bandwidth usage; previously, we
14470 would count only the bytes sent over TLS, but not the bytes used
14472 - Support running the Tor service with a torrc not in the same
14473 directory as tor.exe and default to using the torrc located in
14474 the %appdata%\Tor\ of the user who installed the service. Patch
14476 - Servers now check for the case when common DNS requests are going to
14477 wildcarded addresses (i.e. all getting the same answer), and change
14478 their exit policy to reject *:* if it's happening.
14479 - Implement BEGIN_DIR cells, so we can connect to the directory
14480 server via TLS to do encrypted directory requests rather than
14481 plaintext. Enable via the TunnelDirConns and PreferTunneledDirConns
14482 config options if you like.
14484 o Minor features (config and docs):
14485 - Start using the state file to store bandwidth accounting data:
14486 the bw_accounting file is now obsolete. We'll keep generating it
14487 for a while for people who are still using 0.1.2.4-alpha.
14488 - Try to batch changes to the state file so that we do as few
14489 disk writes as possible while still storing important things in
14491 - The state file and the bw_accounting file get saved less often when
14492 the AvoidDiskWrites config option is set.
14493 - Make PIDFile work on Windows (untested).
14494 - Add internal descriptions for a bunch of configuration options:
14495 accessible via controller interface and in comments in saved
14497 - Reject *:563 (NNTPS) in the default exit policy. We already reject
14498 NNTP by default, so this seems like a sensible addition.
14499 - Clients now reject hostnames with invalid characters. This should
14500 avoid some inadvertent info leaks. Add an option
14501 AllowNonRFC953Hostnames to disable this behavior, in case somebody
14502 is running a private network with hosts called @, !, and #.
14503 - Add a maintainer script to tell us which options are missing
14504 documentation: "make check-docs".
14505 - Add a new address-spec.txt document to describe our special-case
14506 addresses: .exit, .onion, and .noconnnect.
14508 o Minor features (DNS):
14509 - Ongoing work on eventdns infrastructure: now it has dns server
14510 and ipv6 support. One day Tor will make use of it.
14511 - Add client-side caching for reverse DNS lookups.
14512 - Add support to tor-resolve tool for reverse lookups and SOCKS5.
14513 - When we change nameservers or IP addresses, reset and re-launch
14514 our tests for DNS hijacking.
14516 o Minor features (directory):
14517 - Authorities now specify server versions in networkstatus. This adds
14518 about 2% to the size of compressed networkstatus docs, and allows
14519 clients to tell which servers support BEGIN_DIR and which don't.
14520 The implementation is forward-compatible with a proposed future
14521 protocol version scheme not tied to Tor versions.
14522 - DirServer configuration lines now have an orport= option so
14523 clients can open encrypted tunnels to the authorities without
14524 having downloaded their descriptors yet. Enabled for moria1,
14525 moria2, tor26, and lefkada now in the default configuration.
14526 - Directory servers are more willing to send a 503 "busy" if they
14527 are near their write limit, especially for v1 directory requests.
14528 Now they can use their limited bandwidth for actual Tor traffic.
14529 - Clients track responses with status 503 from dirservers. After a
14530 dirserver has given us a 503, we try not to use it until an hour has
14531 gone by, or until we have no dirservers that haven't given us a 503.
14532 - When we get a 503 from a directory, and we're not a server, we don't
14533 count the failure against the total number of failures allowed
14534 for the thing we're trying to download.
14535 - Report X-Your-Address-Is correctly from tunneled directory
14536 connections; don't report X-Your-Address-Is when it's an internal
14537 address; and never believe reported remote addresses when they're
14539 - Protect against an unlikely DoS attack on directory servers.
14540 - Add a BadDirectory flag to network status docs so that authorities
14541 can (eventually) tell clients about caches they believe to be
14544 o Minor features (controller):
14545 - Have GETINFO dir/status/* work on hosts with DirPort disabled.
14546 - Reimplement GETINFO so that info/names stays in sync with the
14548 - Implement "GETINFO fingerprint".
14549 - Implement "SETEVENTS GUARD" so controllers can get updates on
14550 entry guard status as it changes.
14552 o Minor features (clean up obsolete pieces):
14553 - Remove some options that have been deprecated since at least
14554 0.1.0.x: AccountingMaxKB, LogFile, DebugLogFile, LogLevel, and
14555 SysLog. Use AccountingMax instead of AccountingMaxKB, and use Log
14556 to set log options.
14557 - We no longer look for identity and onion keys in "identity.key" and
14558 "onion.key" -- these were replaced by secret_id_key and
14559 secret_onion_key in 0.0.8pre1.
14560 - We no longer require unrecognized directory entries to be
14563 o Major bugfixes (security):
14564 - Stop sending the HttpProxyAuthenticator string to directory
14565 servers when directory connections are tunnelled through Tor.
14566 - Clients no longer store bandwidth history in the state file.
14567 - Do not log introduction points for hidden services if SafeLogging
14569 - When generating bandwidth history, round down to the nearest
14570 1k. When storing accounting data, round up to the nearest 1k.
14571 - When we're running as a server, remember when we last rotated onion
14572 keys, so that we will rotate keys once they're a week old even if
14573 we never stay up for a week ourselves.
14575 o Major bugfixes (other):
14576 - Fix a longstanding bug in eventdns that prevented the count of
14577 timed-out resolves from ever being reset. This bug caused us to
14578 give up on a nameserver the third time it timed out, and try it
14579 10 seconds later... and to give up on it every time it timed out
14581 - Take out the '5 second' timeout from the connection retry
14582 schedule. Now the first connect attempt will wait a full 10
14583 seconds before switching to a new circuit. Perhaps this will help
14584 a lot. Based on observations from Mike Perry.
14585 - Fix a bug on the Windows implementation of tor_mmap_file() that
14586 would prevent the cached-routers file from ever loading. Reported
14590 - Fix an assert failure when a directory authority sets
14591 AuthDirRejectUnlisted and then receives a descriptor from an
14592 unlisted router. Reported by seeess.
14593 - Avoid a double-free when parsing malformed DirServer lines.
14594 - Fix a bug when a BSD-style PF socket is first used. Patch from
14596 - Fix a bug in 0.1.2.2-alpha that prevented clients from asking
14597 to resolve an address at a given exit node even when they ask for
14599 - Servers no longer ever list themselves in their "family" line,
14600 even if configured to do so. This makes it easier to configure
14601 family lists conveniently.
14602 - When running as a server, don't fall back to 127.0.0.1 when no
14603 nameservers are configured in /etc/resolv.conf; instead, make the
14604 user fix resolv.conf or specify nameservers explicitly. (Resolves
14606 - Stop accepting certain malformed ports in configured exit policies.
14607 - Don't re-write the fingerprint file every restart, unless it has
14609 - Stop warning when a single nameserver fails: only warn when _all_ of
14610 our nameservers have failed. Also, when we only have one nameserver,
14611 raise the threshold for deciding that the nameserver is dead.
14612 - Directory authorities now only decide that routers are reachable
14613 if their identity keys are as expected.
14614 - When the user uses bad syntax in the Log config line, stop
14615 suggesting other bad syntax as a replacement.
14616 - Correctly detect ipv6 DNS capability on OpenBSD.
14618 o Minor bugfixes (controller):
14619 - Report the circuit number correctly in STREAM CLOSED events. Bug
14620 reported by Mike Perry.
14621 - Do not report bizarre values for results of accounting GETINFOs
14622 when the last second's write or read exceeds the allotted bandwidth.
14623 - Report "unrecognized key" rather than an empty string when the
14624 controller tries to fetch a networkstatus that doesn't exist.
14627 Changes in version 0.1.1.26 - 2006-12-14
14628 o Security bugfixes:
14629 - Stop sending the HttpProxyAuthenticator string to directory
14630 servers when directory connections are tunnelled through Tor.
14631 - Clients no longer store bandwidth history in the state file.
14632 - Do not log introduction points for hidden services if SafeLogging
14636 - Fix an assert failure when a directory authority sets
14637 AuthDirRejectUnlisted and then receives a descriptor from an
14638 unlisted router (reported by seeess).
14641 Changes in version 0.1.2.4-alpha - 2006-12-03
14643 - Add support for using natd; this allows FreeBSDs earlier than
14644 5.1.2 to have ipfw send connections through Tor without using
14645 SOCKS. (Patch from Zajcev Evgeny with tweaks from tup.)
14648 - Make all connections to addresses of the form ".noconnect"
14649 immediately get closed. This lets application/controller combos
14650 successfully test whether they're talking to the same Tor by
14651 watching for STREAM events.
14652 - Make cross.sh cross-compilation script work even when autogen.sh
14653 hasn't been run. (Patch from Michael Mohr.)
14654 - Statistics dumped by -USR2 now include a breakdown of public key
14655 operations, for profiling.
14658 - Fix a major leak when directory authorities parse their
14659 approved-routers list, a minor memory leak when we fail to pick
14660 an exit node, and a few rare leaks on errors.
14661 - Handle TransPort connections even when the server sends data before
14662 the client sends data. Previously, the connection would just hang
14663 until the client sent data. (Patch from tup based on patch from
14665 - Avoid assert failure when our cached-routers file is empty on
14669 - Don't log spurious warnings when we see a circuit close reason we
14670 don't recognize; it's probably just from a newer version of Tor.
14671 - Have directory authorities allow larger amounts of drift in uptime
14672 without replacing the server descriptor: previously, a server that
14673 restarted every 30 minutes could have 48 "interesting" descriptors
14675 - Start linking to the Tor specification and Tor reference manual
14676 correctly in the Windows installer.
14677 - Add Vidalia to the OS X uninstaller script, so when we uninstall
14678 Tor/Privoxy we also uninstall Vidalia.
14679 - Resume building on Irix64, and fix a lot of warnings from its
14680 MIPSpro C compiler.
14681 - Don't corrupt last_guessed_ip in router_new_address_suggestion()
14682 when we're running as a client.
14685 Changes in version 0.1.1.25 - 2006-11-04
14687 - When a client asks us to resolve (rather than connect to)
14688 an address, and we have a cached answer, give them the cached
14689 answer. Previously, we would give them no answer at all.
14690 - We were building exactly the wrong circuits when we predict
14691 hidden service requirements, meaning Tor would have to build all
14692 its circuits on demand.
14693 - If none of our live entry guards have a high uptime, but we
14694 require a guard with a high uptime, try adding a new guard before
14695 we give up on the requirement. This patch should make long-lived
14696 connections more stable on average.
14697 - When testing reachability of our DirPort, don't launch new
14698 tests when there's already one in progress -- unreachable
14699 servers were stacking up dozens of testing streams.
14701 o Security bugfixes:
14702 - When the user sends a NEWNYM signal, clear the client-side DNS
14703 cache too. Otherwise we continue to act on previous information.
14706 - Avoid a memory corruption bug when creating a hash table for
14708 - Avoid possibility of controller-triggered crash when misusing
14709 certain commands from a v0 controller on platforms that do not
14710 handle printf("%s",NULL) gracefully.
14711 - Avoid infinite loop on unexpected controller input.
14712 - Don't log spurious warnings when we see a circuit close reason we
14713 don't recognize; it's probably just from a newer version of Tor.
14714 - Add Vidalia to the OS X uninstaller script, so when we uninstall
14715 Tor/Privoxy we also uninstall Vidalia.
14718 Changes in version 0.1.2.3-alpha - 2006-10-29
14720 - Prepare for servers to publish descriptors less often: never
14721 discard a descriptor simply for being too old until either it is
14722 recommended by no authorities, or until we get a better one for
14723 the same router. Make caches consider retaining old recommended
14724 routers for even longer.
14725 - If most authorities set a BadExit flag for a server, clients
14726 don't think of it as a general-purpose exit. Clients only consider
14727 authorities that advertise themselves as listing bad exits.
14728 - Directory servers now provide 'Pragma: no-cache' and 'Expires'
14729 headers for content, so that we can work better in the presence of
14730 caching HTTP proxies.
14731 - Allow authorities to list nodes as bad exits by fingerprint or by
14734 o Minor features, controller:
14735 - Add a REASON field to CIRC events; for backward compatibility, this
14736 field is sent only to controllers that have enabled the extended
14737 event format. Also, add additional reason codes to explain why
14738 a given circuit has been destroyed or truncated. (Patches from
14740 - Add a REMOTE_REASON field to extended CIRC events to tell the
14741 controller about why a remote OR told us to close a circuit.
14742 - Stream events also now have REASON and REMOTE_REASON fields,
14743 working much like those for circuit events.
14744 - There's now a GETINFO ns/... field so that controllers can ask Tor
14745 about the current status of a router.
14746 - A new event type "NS" to inform a controller when our opinion of
14747 a router's status has changed.
14748 - Add a GETINFO events/names and GETINFO features/names so controllers
14749 can tell which events and features are supported.
14750 - A new CLEARDNSCACHE signal to allow controllers to clear the
14751 client-side DNS cache without expiring circuits.
14753 o Security bugfixes:
14754 - When the user sends a NEWNYM signal, clear the client-side DNS
14755 cache too. Otherwise we continue to act on previous information.
14758 - Avoid sending junk to controllers or segfaulting when a controller
14759 uses EVENT_NEW_DESC with verbose nicknames.
14760 - Stop triggering asserts if the controller tries to extend hidden
14761 service circuits (reported by mwenge).
14762 - Avoid infinite loop on unexpected controller input.
14763 - When the controller does a "GETINFO network-status", tell it
14764 about even those routers whose descriptors are very old, and use
14765 long nicknames where appropriate.
14766 - Change NT service functions to be loaded on demand. This lets us
14767 build with MinGW without breaking Tor for Windows 98 users.
14768 - Do DirPort reachability tests less often, since a single test
14769 chews through many circuits before giving up.
14770 - In the hidden service example in torrc.sample, stop recommending
14771 esoteric and discouraged hidden service options.
14772 - When stopping an NT service, wait up to 10 sec for it to actually
14773 stop. Patch from Matt Edman; resolves bug 295.
14774 - Fix handling of verbose nicknames with ORCONN controller events:
14775 make them show up exactly when requested, rather than exactly when
14777 - When reporting verbose nicknames in entry_guards_getinfo(), avoid
14778 printing a duplicate "$" in the keys we send (reported by mwenge).
14779 - Correctly set maximum connection limit on Cygwin. (This time
14781 - Try to detect Windows correctly when cross-compiling.
14782 - Detect the size of the routers file correctly even if it is
14783 corrupted (on systems without mmap) or not page-aligned (on systems
14784 with mmap). This bug was harmless.
14785 - Sometimes we didn't bother sending a RELAY_END cell when an attempt
14786 to open a stream fails; now we do in more cases. This should
14787 make clients able to find a good exit faster in some cases, since
14788 unhandleable requests will now get an error rather than timing out.
14789 - Resolve two memory leaks when rebuilding the on-disk router cache
14790 (reported by fookoowa).
14791 - Clean up minor code warnings suggested by the MIPSpro C compiler,
14792 and reported by some Centos users.
14793 - Controller signals now work on non-Unix platforms that don't define
14794 SIGUSR1 and SIGUSR2 the way we expect.
14795 - Patch from Michael Mohr to contrib/cross.sh, so it checks more
14796 values before failing, and always enables eventdns.
14797 - Libevent-1.2 exports, but does not define in its headers, strlcpy.
14798 Try to fix this in configure.in by checking for most functions
14799 before we check for libevent.
14802 Changes in version 0.1.2.2-alpha - 2006-10-07
14804 - Make our async eventdns library on-by-default for Tor servers,
14805 and plan to deprecate the separate dnsworker threads.
14806 - Add server-side support for "reverse" DNS lookups (using PTR
14807 records so clients can determine the canonical hostname for a given
14808 IPv4 address). Only supported by servers using eventdns; servers
14809 now announce in their descriptors whether they support eventdns.
14810 - Specify and implement client-side SOCKS5 interface for reverse DNS
14811 lookups (see doc/socks-extensions.txt).
14812 - Add a BEGIN_DIR relay cell type for an easier in-protocol way to
14813 connect to directory servers through Tor. Previously, clients needed
14814 to find Tor exits to make private connections to directory servers.
14815 - Avoid choosing Exit nodes for entry or middle hops when the
14816 total bandwidth available from non-Exit nodes is much higher than
14817 the total bandwidth available from Exit nodes.
14818 - Workaround for name servers (like Earthlink's) that hijack failing
14819 DNS requests and replace the no-such-server answer with a "helpful"
14820 redirect to an advertising-driven search portal. Also work around
14821 DNS hijackers who "helpfully" decline to hijack known-invalid
14822 RFC2606 addresses. Config option "ServerDNSDetectHijacking 0"
14823 lets you turn it off.
14824 - Send out a burst of long-range padding cells once we've established
14825 that we're reachable. Spread them over 4 circuits, so hopefully
14826 a few will be fast. This exercises our bandwidth and bootstraps
14827 us into the directory more quickly.
14829 o New/improved config options:
14830 - Add new config option "ResolvConf" to let the server operator
14831 choose an alternate resolve.conf file when using eventdns.
14832 - Add an "EnforceDistinctSubnets" option to control our "exclude
14833 servers on the same /16" behavior. It's still on by default; this
14834 is mostly for people who want to operate private test networks with
14835 all the machines on the same subnet.
14836 - If one of our entry guards is on the ExcludeNodes list, or the
14837 directory authorities don't think it's a good guard, treat it as
14838 if it were unlisted: stop using it as a guard, and throw it off
14839 the guards list if it stays that way for a long time.
14840 - Allow directory authorities to be marked separately as authorities
14841 for the v1 directory protocol, the v2 directory protocol, and
14842 as hidden service directories, to make it easier to retire old
14843 authorities. V1 authorities should set "HSAuthoritativeDir 1"
14844 to continue being hidden service authorities too.
14845 - Remove 8888 as a LongLivedPort, and add 6697 (IRCS).
14847 o Minor features, controller:
14848 - Fix CIRC controller events so that controllers can learn the
14849 identity digests of non-Named servers used in circuit paths.
14850 - Let controllers ask for more useful identifiers for servers. Instead
14851 of learning identity digests for un-Named servers and nicknames
14852 for Named servers, the new identifiers include digest, nickname,
14853 and indication of Named status. Off by default; see control-spec.txt
14854 for more information.
14855 - Add a "getinfo address" controller command so it can display Tor's
14856 best guess to the user.
14857 - New controller event to alert the controller when our server
14858 descriptor has changed.
14859 - Give more meaningful errors on controller authentication failure.
14861 o Minor features, other:
14862 - When asked to resolve a hostname, don't use non-exit servers unless
14863 requested to do so. This allows servers with broken DNS to be
14864 useful to the network.
14865 - Divide eventdns log messages into warn and info messages.
14866 - Reserve the nickname "Unnamed" for routers that can't pick
14867 a hostname: any router can call itself Unnamed; directory
14868 authorities will never allocate Unnamed to any particular router;
14869 clients won't believe that any router is the canonical Unnamed.
14870 - Only include function names in log messages for info/debug messages.
14871 For notice/warn/err, the content of the message should be clear on
14872 its own, and printing the function name only confuses users.
14873 - Avoid some false positives during reachability testing: don't try
14874 to test via a server that's on the same /24 as us.
14875 - If we fail to build a circuit to an intended enclave, and it's
14876 not mandatory that we use that enclave, stop wanting it.
14877 - When eventdns is enabled, allow multithreaded builds on NetBSD and
14878 OpenBSD. (We had previously disabled threads on these platforms
14879 because they didn't have working thread-safe resolver functions.)
14881 o Major bugfixes, anonymity/security:
14882 - If a client asked for a server by name, and there's a named server
14883 in our network-status but we don't have its descriptor yet, we
14884 could return an unnamed server instead.
14885 - Fix NetBSD bug that could allow someone to force uninitialized RAM
14886 to be sent to a server's DNS resolver. This only affects NetBSD
14887 and other platforms that do not bounds-check tolower().
14888 - Reject (most) attempts to use Tor circuits with length one. (If
14889 many people start using Tor as a one-hop proxy, exit nodes become
14890 a more attractive target for compromise.)
14891 - Just because your DirPort is open doesn't mean people should be
14892 able to remotely teach you about hidden service descriptors. Now
14893 only accept rendezvous posts if you've got HSAuthoritativeDir set.
14895 o Major bugfixes, other:
14896 - Don't crash on race condition in dns.c: tor_assert(!resolve->expire)
14897 - When a client asks the server to resolve (not connect to)
14898 an address, and it has a cached answer, give them the cached answer.
14899 Previously, the server would give them no answer at all.
14900 - Allow really slow clients to not hang up five minutes into their
14901 directory downloads (suggested by Adam J. Richter).
14902 - We were building exactly the wrong circuits when we anticipated
14903 hidden service requirements, meaning Tor would have to build all
14904 its circuits on demand.
14905 - Avoid crashing when we mmap a router cache file of size 0.
14906 - When testing reachability of our DirPort, don't launch new
14907 tests when there's already one in progress -- unreachable
14908 servers were stacking up dozens of testing streams.
14910 o Minor bugfixes, correctness:
14911 - If we're a directory mirror and we ask for "all" network status
14912 documents, we would discard status documents from authorities
14913 we don't recognize.
14914 - Avoid a memory corruption bug when creating a hash table for
14916 - Avoid controller-triggered crash when misusing certain commands
14917 from a v0 controller on platforms that do not handle
14918 printf("%s",NULL) gracefully.
14919 - Don't crash when a controller sends a third argument to an
14920 "extendcircuit" request.
14921 - Controller protocol fixes: fix encoding in "getinfo addr-mappings"
14922 response; fix error code when "getinfo dir/status/" fails.
14923 - Avoid crash when telling controller stream-status and a stream
14925 - Patch from Adam Langley to fix assert() in eventdns.c.
14926 - Fix a debug log message in eventdns to say "X resolved to Y"
14927 instead of "X resolved to X".
14928 - Make eventdns give strings for DNS errors, not just error numbers.
14929 - Track unreachable entry guards correctly: don't conflate
14930 'unreachable by us right now' with 'listed as down by the directory
14931 authorities'. With the old code, if a guard was unreachable by
14932 us but listed as running, it would clog our guard list forever.
14933 - Behave correctly in case we ever have a network with more than
14934 2GB/s total advertised capacity.
14935 - Make TrackExitHosts case-insensitive, and fix the behavior of
14936 ".suffix" TrackExitHosts items to avoid matching in the middle of
14938 - Finally fix the openssl warnings from newer gccs that believe that
14939 ignoring a return value is okay, but casting a return value and
14940 then ignoring it is a sign of madness.
14941 - Prevent the contrib/exitlist script from printing the same
14942 result more than once.
14943 - Patch from Steve Hildrey: Generate network status correctly on
14944 non-versioning dirservers.
14945 - Don't listen to the X-Your-Address-Is hint if you did the lookup
14946 via Tor; otherwise you'll think you're the exit node's IP address.
14948 o Minor bugfixes, performance:
14949 - Two small performance improvements on parsing descriptors.
14950 - Major performance improvement on inserting descriptors: change
14951 algorithm from O(n^2) to O(n).
14952 - Make the common memory allocation path faster on machines where
14953 malloc(0) returns a pointer.
14954 - Start remembering X-Your-Address-Is directory hints even if you're
14955 a client, so you can become a server more smoothly.
14956 - Avoid duplicate entries on MyFamily line in server descriptor.
14958 o Packaging, features:
14959 - Remove architecture from OS X builds. The official builds are
14960 now universal binaries.
14961 - The Debian package now uses --verify-config when (re)starting,
14962 to distinguish configuration errors from other errors.
14963 - Update RPMs to require libevent 1.1b.
14965 o Packaging, bugfixes:
14966 - Patches so Tor builds with MinGW on Windows.
14967 - Patches so Tor might run on Cygwin again.
14968 - Resume building on non-gcc compilers and ancient gcc. Resume
14969 building with the -O0 compile flag. Resume building cleanly on
14971 - Run correctly on OS X platforms with case-sensitive filesystems.
14972 - Correct includes for net/if.h and net/pfvar.h on OpenBSD (from Tup).
14973 - Add autoconf checks so Tor can build on Solaris x86 again.
14976 - Documented (and renamed) ServerDNSSearchDomains and
14977 ServerDNSResolvConfFile options.
14978 - Be clearer that the *ListenAddress directives can be repeated
14982 Changes in version 0.1.1.24 - 2006-09-29
14984 - Allow really slow clients to not hang up five minutes into their
14985 directory downloads (suggested by Adam J. Richter).
14986 - Fix major performance regression from 0.1.0.x: instead of checking
14987 whether we have enough directory information every time we want to
14988 do something, only check when the directory information has changed.
14989 This should improve client CPU usage by 25-50%.
14990 - Don't crash if, after a server has been running for a while,
14991 it can't resolve its hostname.
14994 - Allow Tor to start when RunAsDaemon is set but no logs are set.
14995 - Don't crash when the controller receives a third argument to an
14996 "extendcircuit" request.
14997 - Controller protocol fixes: fix encoding in "getinfo addr-mappings"
14998 response; fix error code when "getinfo dir/status/" fails.
14999 - Fix configure.in to not produce broken configure files with
15000 more recent versions of autoconf. Thanks to Clint for his auto*
15002 - Fix security bug on NetBSD that could allow someone to force
15003 uninitialized RAM to be sent to a server's DNS resolver. This
15004 only affects NetBSD and other platforms that do not bounds-check
15006 - Warn user when using libevent 1.1a or earlier with win32 or kqueue
15007 methods: these are known to be buggy.
15008 - If we're a directory mirror and we ask for "all" network status
15009 documents, we would discard status documents from authorities
15010 we don't recognize.
15013 Changes in version 0.1.2.1-alpha - 2006-08-27
15015 - Add "eventdns" async dns library from Adam Langley, tweaked to
15016 build on OSX and Windows. Only enabled if you pass the
15017 --enable-eventdns argument to configure.
15018 - Allow servers with no hostname or IP address to learn their
15019 IP address by asking the directory authorities. This code only
15020 kicks in when you would normally have exited with a "no address"
15021 error. Nothing's authenticated, so use with care.
15022 - Rather than waiting a fixed amount of time between retrying
15023 application connections, we wait only 5 seconds for the first,
15024 10 seconds for the second, and 15 seconds for each retry after
15025 that. Hopefully this will improve the expected user experience.
15026 - Patch from Tup to add support for transparent AP connections:
15027 this basically bundles the functionality of trans-proxy-tor
15028 into the Tor mainline. Now hosts with compliant pf/netfilter
15029 implementations can redirect TCP connections straight to Tor
15030 without diverting through SOCKS. Needs docs.
15031 - Busy directory servers save lots of memory by spooling server
15032 descriptors, v1 directories, and v2 networkstatus docs to buffers
15033 as needed rather than en masse. Also mmap the cached-routers
15034 files, so we don't need to keep the whole thing in memory too.
15035 - Automatically avoid picking more than one node from the same
15036 /16 network when constructing a circuit.
15037 - Revise and clean up the torrc.sample that we ship with; add
15038 a section for BandwidthRate and BandwidthBurst.
15041 - Split circuit_t into origin_circuit_t and or_circuit_t, and
15042 split connection_t into edge, or, dir, control, and base structs.
15043 These will save quite a bit of memory on busy servers, and they'll
15044 also help us track down bugs in the code and bugs in the spec.
15045 - Experimentally re-enable kqueue on OSX when using libevent 1.1b
15046 or later. Log when we are doing this, so we can diagnose it when
15047 it fails. (Also, recommend libevent 1.1b for kqueue and
15048 win32 methods; deprecate libevent 1.0b harder; make libevent
15049 recommendation system saner.)
15050 - Start being able to build universal binaries on OS X (thanks
15052 - Export the default exit policy via the control port, so controllers
15053 don't need to guess what it is / will be later.
15054 - Add a man page entry for ProtocolWarnings.
15055 - Add TestVia config option to the man page.
15056 - Remove even more protocol-related warnings from Tor server logs,
15057 such as bad TLS handshakes and malformed begin cells.
15058 - Stop fetching descriptors if you're not a dir mirror and you
15059 haven't tried to establish any circuits lately. [This currently
15060 causes some dangerous behavior, because when you start up again
15061 you'll use your ancient server descriptors.]
15062 - New DirPort behavior: if you have your dirport set, you download
15063 descriptors aggressively like a directory mirror, whether or not
15064 your ORPort is set.
15065 - Get rid of the router_retry_connections notion. Now routers
15066 no longer try to rebuild long-term connections to directory
15067 authorities, and directory authorities no longer try to rebuild
15068 long-term connections to all servers. We still don't hang up
15069 connections in these two cases though -- we need to look at it
15070 more carefully to avoid flapping, and we likely need to wait til
15071 0.1.1.x is obsolete.
15072 - Drop compatibility with obsolete Tors that permit create cells
15073 to have the wrong circ_id_type.
15074 - Re-enable per-connection rate limiting. Get rid of the "OP
15075 bandwidth" concept. Lay groundwork for "bandwidth classes" --
15076 separate global buckets that apply depending on what sort of conn
15078 - Start publishing one minute or so after we find our ORPort
15079 to be reachable. This will help reduce the number of descriptors
15080 we have for ourselves floating around, since it's quite likely
15081 other things (e.g. DirPort) will change during that minute too.
15082 - Fork the v1 directory protocol into its own spec document,
15083 and mark dir-spec.txt as the currently correct (v2) spec.
15086 - When we find our DirPort to be reachable, publish a new descriptor
15087 so we'll tell the world (reported by pnx).
15088 - Publish a new descriptor after we hup/reload. This is important
15089 if our config has changed such that we'll want to start advertising
15090 our DirPort now, etc.
15091 - Allow Tor to start when RunAsDaemon is set but no logs are set.
15092 - When we have a state file we cannot parse, tell the user and
15093 move it aside. Now we avoid situations where the user starts
15094 Tor in 1904, Tor writes a state file with that timestamp in it,
15095 the user fixes her clock, and Tor refuses to start.
15096 - Fix configure.in to not produce broken configure files with
15097 more recent versions of autoconf. Thanks to Clint for his auto*
15099 - "tor --verify-config" now exits with -1(255) or 0 depending on
15100 whether the config options are bad or good.
15101 - Resolve bug 321 when using dnsworkers: append a period to every
15102 address we resolve at the exit node, so that we do not accidentally
15103 pick up local addresses, and so that failing searches are retried
15104 in the resolver search domains. (This is already solved for
15105 eventdns.) (This breaks Blossom servers for now.)
15106 - If we are using an exit enclave and we can't connect, e.g. because
15107 its webserver is misconfigured to not listen on localhost, then
15108 back off and try connecting from somewhere else before we fail.
15111 - Start compiling on MinGW on Windows (patches from Mike Chiussi).
15112 - Start compiling on MSVC6 on Windows (patches from Frediano Ziglio).
15113 - Fix bug 314: Tor clients issued "unsafe socks" warnings even
15114 when the IP address is mapped through MapAddress to a hostname.
15115 - Start passing "ipv4" hints to getaddrinfo(), so servers don't do
15116 useless IPv6 DNS resolves.
15117 - Patch suggested by Karsten Loesing: respond to SIGNAL command
15118 before we execute the signal, in case the signal shuts us down.
15119 - Clean up AllowInvalidNodes man page entry.
15120 - Claim a commonname of Tor, rather than TOR, in TLS handshakes.
15121 - Add more asserts to track down an assert error on a windows Tor
15122 server with connection_add being called with socket == -1.
15123 - Handle reporting OR_CONN_EVENT_NEW events to the controller.
15124 - Fix misleading log messages: an entry guard that is "unlisted",
15125 as well as not known to be "down" (because we've never heard
15126 of it), is not therefore "up".
15127 - Remove code to special-case "-cvs" ending, since it has not
15128 actually mattered since 0.0.9.
15129 - Make our socks5 handling more robust to broken socks clients:
15130 throw out everything waiting on the buffer in between socks
15131 handshake phases, since they can't possibly (so the theory
15132 goes) have predicted what we plan to respond to them.
15135 Changes in version 0.1.1.23 - 2006-07-30
15137 - Fast Tor servers, especially exit nodes, were triggering asserts
15138 due to a bug in handling the list of pending DNS resolves. Some
15139 bugs still remain here; we're hunting them.
15140 - Entry guards could crash clients by sending unexpected input.
15141 - More fixes on reachability testing: if you find yourself reachable,
15142 then don't ever make any client requests (so you stop predicting
15143 circuits), then hup or have your clock jump, then later your IP
15144 changes, you won't think circuits are working, so you won't try to
15145 test reachability, so you won't publish.
15148 - Avoid a crash if the controller does a resetconf firewallports
15149 and then a setconf fascistfirewall=1.
15150 - Avoid an integer underflow when the dir authority decides whether
15151 a router is stable: we might wrongly label it stable, and compute
15152 a slightly wrong median stability, when a descriptor is published
15154 - Fix a place where we might trigger an assert if we can't build our
15155 own server descriptor yet.
15158 Changes in version 0.1.1.22 - 2006-07-05
15160 - Fix a big bug that was causing servers to not find themselves
15161 reachable if they changed IP addresses. Since only 0.1.1.22+
15162 servers can do reachability testing correctly, now we automatically
15163 make sure to test via one of these.
15164 - Fix to allow clients and mirrors to learn directory info from
15165 descriptor downloads that get cut off partway through.
15166 - Directory authorities had a bug in deciding if a newly published
15167 descriptor was novel enough to make everybody want a copy -- a few
15168 servers seem to be publishing new descriptors many times a minute.
15170 - Fix a rare bug that was causing some servers to complain about
15171 "closing wedged cpuworkers" and skip some circuit create requests.
15172 - Make the Exit flag in directory status documents actually work.
15175 Changes in version 0.1.1.21 - 2006-06-10
15176 o Crash and assert fixes from 0.1.1.20:
15177 - Fix a rare crash on Tor servers that have enabled hibernation.
15178 - Fix a seg fault on startup for Tor networks that use only one
15179 directory authority.
15180 - Fix an assert from a race condition that occurs on Tor servers
15181 while exiting, where various threads are trying to log that they're
15182 exiting, and delete the logs, at the same time.
15183 - Make our unit tests pass again on certain obscure platforms.
15186 - Add support for building SUSE RPM packages.
15187 - Speed up initial bootstrapping for clients: if we are making our
15188 first ever connection to any entry guard, then don't mark it down
15190 - When only one Tor server in the network is labelled as a guard,
15191 and we've already picked him, we would cycle endlessly picking him
15192 again, being unhappy about it, etc. Now we specifically exclude
15193 current guards when picking a new guard.
15194 - Servers send create cells more reliably after the TLS connection
15195 is established: we were sometimes forgetting to send half of them
15196 when we had more than one pending.
15197 - If we get a create cell that asks us to extend somewhere, but the
15198 Tor server there doesn't match the expected digest, we now send
15199 a destroy cell back, rather than silently doing nothing.
15200 - Make options->RedirectExit work again.
15201 - Make cookie authentication for the controller work again.
15202 - Stop being picky about unusual characters in the arguments to
15203 mapaddress. It's none of our business.
15204 - Add a new config option "TestVia" that lets you specify preferred
15205 middle hops to use for test circuits. Perhaps this will let me
15206 debug the reachability problems better.
15208 o Log / documentation fixes:
15209 - If we're a server and some peer has a broken TLS certificate, don't
15210 log about it unless ProtocolWarnings is set, i.e., we want to hear
15211 about protocol violations by others.
15212 - Fix spelling of VirtualAddrNetwork in man page.
15213 - Add a better explanation at the top of the autogenerated torrc file
15214 about what happened to our old torrc.
15217 Changes in version 0.1.1.20 - 2006-05-23
15219 - Downgrade a log severity where servers complain that they're
15221 - Avoid a compile warning on FreeBSD.
15222 - Remove string size limit on NEWDESC messages; solve bug 291.
15223 - Correct the RunAsDaemon entry in the man page; ignore RunAsDaemon
15224 more thoroughly when we're running on windows.
15227 Changes in version 0.1.1.19-rc - 2006-05-03
15229 - Regenerate our local descriptor if it's dirty and we try to use
15230 it locally (e.g. if it changes during reachability detection).
15231 - If we setconf our ORPort to 0, we continued to listen on the
15232 old ORPort and receive connections.
15233 - Avoid a second warning about machine/limits.h on Debian
15235 - Be willing to add our own routerinfo into the routerlist.
15236 Now authorities will include themselves in their directories
15237 and network-statuses.
15238 - Stop trying to upload rendezvous descriptors to every
15239 directory authority: only try the v1 authorities.
15240 - Servers no longer complain when they think they're not
15241 registered with the directory authorities. There were too many
15243 - Backport dist-rpm changes so rpms can be built without errors.
15246 - Implement an option, VirtualAddrMask, to set which addresses
15247 get handed out in response to mapaddress requests. This works
15248 around a bug in tsocks where 127.0.0.0/8 is never socksified.
15251 Changes in version 0.1.1.18-rc - 2006-04-10
15253 - Work harder to download live network-statuses from all the
15254 directory authorities we know about. Improve the threshold
15255 decision logic so we're more robust to edge cases.
15256 - When fetching rendezvous descriptors, we were willing to ask
15257 v2 authorities too, which would always return 404.
15260 - Stop listing down or invalid nodes in the v1 directory. This will
15261 reduce its bulk by about 1/3, and reduce load on directory
15263 - When deciding whether a router is Fast or Guard-worthy, consider
15264 his advertised BandwidthRate and not just the BandwidthCapacity.
15265 - No longer ship INSTALL and README files -- they are useless now.
15266 - Force rpmbuild to behave and honor target_cpu.
15267 - Avoid warnings about machine/limits.h on Debian GNU/kFreeBSD.
15268 - Start to include translated versions of the tor-doc-*.html
15269 files, along with the screenshots. Still needs more work.
15270 - Start sending back 512 and 451 errors if mapaddress fails,
15271 rather than not sending anything back at all.
15272 - When we fail to bind or listen on an incoming or outgoing
15273 socket, we should close it before failing. otherwise we just
15274 leak it. (thanks to weasel for finding.)
15275 - Allow "getinfo dir/status/foo" to work, as long as your DirPort
15276 is enabled. (This is a hack, and will be fixed in 0.1.2.x.)
15277 - Make NoPublish (even though deprecated) work again.
15278 - Fix a minor security flaw where a versioning auth dirserver
15279 could list a recommended version many times in a row to make
15280 clients more convinced that it's recommended.
15281 - Fix crash bug if there are two unregistered servers running
15282 with the same nickname, one of them is down, and you ask for
15283 them by nickname in your EntryNodes or ExitNodes. Also, try
15284 to pick the one that's running rather than an arbitrary one.
15285 - Fix an infinite loop we could hit if we go offline for too long.
15286 - Complain when we hit WSAENOBUFS on recv() or write() too.
15287 Perhaps this will help us hunt the bug.
15288 - If you're not a versioning dirserver, don't put the string
15289 "client-versions \nserver-versions \n" in your network-status.
15290 - Lower the minimum required number of file descriptors to 1000,
15291 so we can have some overhead for Valgrind on Linux, where the
15292 default ulimit -n is 1024.
15295 - Add tor.dizum.com as the fifth authoritative directory server.
15296 - Add a new config option FetchUselessDescriptors, off by default,
15297 for when you plan to run "exitlist" on your client and you want
15298 to know about even the non-running descriptors.
15301 Changes in version 0.1.1.17-rc - 2006-03-28
15303 - Clients and servers since 0.1.1.10-alpha have been expiring
15304 connections whenever they are idle for 5 minutes and they *do*
15305 have circuits on them. Oops. With this new version, clients will
15306 discard their previous entry guard choices and avoid choosing
15307 entry guards running these flawed versions.
15308 - Fix memory leak when uncompressing concatenated zlib streams. This
15309 was causing substantial leaks over time on Tor servers.
15310 - The v1 directory was including servers as much as 48 hours old,
15311 because that's how the new routerlist->routers works. Now only
15312 include them if they're 20 hours old or less.
15315 - Resume building on irix64, netbsd 2.0, etc.
15316 - On non-gcc compilers (e.g. solaris), use "-g -O" instead of
15318 - Stop writing the "router.desc" file, ever. Nothing uses it anymore,
15319 and it is confusing some users.
15320 - Mirrors stop caching the v1 directory so often.
15321 - Make the max number of old descriptors that a cache will hold
15322 rise with the number of directory authorities, so we can scale.
15323 - Change our win32 uname() hack to be more forgiving about what
15324 win32 versions it thinks it's found.
15327 - Add lefkada.eecs.harvard.edu as a fourth authoritative directory
15329 - When the controller's *setconf commands fail, collect an error
15330 message in a string and hand it back to the controller.
15331 - Make the v2 dir's "Fast" flag based on relative capacity, just
15332 like "Stable" is based on median uptime. Name everything in the
15333 top 7/8 Fast, and only the top 1/2 gets to be a Guard.
15334 - Log server fingerprint on startup, so new server operators don't
15335 have to go hunting around their filesystem for it.
15336 - Return a robots.txt on our dirport to discourage google indexing.
15337 - Let the controller ask for GETINFO dir/status/foo so it can ask
15338 directly rather than connecting to the dir port. Only works when
15339 dirport is set for now.
15341 o New config options rather than constants in the code:
15342 - SocksTimeout: How long do we let a socks connection wait
15343 unattached before we fail it?
15344 - CircuitBuildTimeout: Cull non-open circuits that were born
15345 at least this many seconds ago.
15346 - CircuitIdleTimeout: Cull open clean circuits that were born
15347 at least this many seconds ago.
15350 Changes in version 0.1.1.16-rc - 2006-03-18
15351 o Bugfixes on 0.1.1.15-rc:
15352 - Fix assert when the controller asks to attachstream a connect-wait
15353 or resolve-wait stream.
15354 - Now do address rewriting when the controller asks us to attach
15355 to a particular circuit too. This will let Blossom specify
15356 "moria2.exit" without having to learn what moria2's IP address is.
15357 - Make the "tor --verify-config" command-line work again, so people
15358 can automatically check if their torrc will parse.
15359 - Authoritative dirservers no longer require an open connection from
15360 a server to consider him "reachable". We need this change because
15361 when we add new auth dirservers, old servers won't know not to
15363 - Let Tor build on Sun CC again.
15364 - Fix an off-by-one buffer size in dirserv.c that magically never
15365 hit our three authorities but broke sjmurdoch's own tor network.
15366 - If we as a directory mirror don't know of any v1 directory
15367 authorities, then don't try to cache any v1 directories.
15368 - Stop warning about unknown servers in our family when they are
15369 given as hex digests.
15370 - Stop complaining as quickly to the server operator that he
15371 hasn't registered his nickname/key binding.
15372 - Various cleanups so we can add new V2 Auth Dirservers.
15373 - Change "AllowUnverifiedNodes" to "AllowInvalidNodes", to
15374 reflect the updated flags in our v2 dir protocol.
15375 - Resume allowing non-printable characters for exit streams (both
15376 for connecting and for resolving). Now we tolerate applications
15377 that don't follow the RFCs. But continue to block malformed names
15380 o Bugfixes on 0.1.0.x:
15381 - Fix assert bug in close_logs(): when we close and delete logs,
15382 remove them all from the global "logfiles" list.
15383 - Fix minor integer overflow in calculating when we expect to use up
15384 our bandwidth allocation before hibernating.
15385 - Fix a couple of bugs in OpenSSL detection. Also, deal better when
15386 there are multiple SSLs installed with different versions.
15387 - When we try to be a server and Address is not explicitly set and
15388 our hostname resolves to a private IP address, try to use an
15389 interface address if it has a public address. Now Windows machines
15390 that think of themselves as localhost can work by default.
15393 - Let the controller ask for GETINFO dir/server/foo so it can ask
15394 directly rather than connecting to the dir port.
15395 - Let the controller tell us about certain router descriptors
15396 that it doesn't want Tor to use in circuits. Implement
15397 SETROUTERPURPOSE and modify +POSTDESCRIPTOR to do this.
15398 - New config option SafeSocks to reject all application connections
15399 using unsafe socks protocols. Defaults to off.
15402 Changes in version 0.1.1.15-rc - 2006-03-11
15403 o Bugfixes and cleanups:
15404 - When we're printing strings from the network, don't try to print
15405 non-printable characters. This protects us against shell escape
15406 sequence exploits, and also against attacks to fool humans into
15407 misreading their logs.
15408 - Fix a bug where Tor would fail to establish any connections if you
15409 left it off for 24 hours and then started it: we were happy with
15410 the obsolete network statuses, but they all referred to router
15411 descriptors that were too old to fetch, so we ended up with no
15412 valid router descriptors.
15413 - Fix a seg fault in the controller's "getinfo orconn-status"
15414 command while listing status on incoming handshaking connections.
15415 Introduce a status name "NEW" for these connections.
15416 - If we get a linelist or linelist_s config option from the torrc
15417 (e.g. ExitPolicy) and it has no value, warn and skip rather than
15418 silently resetting it to its default.
15419 - Don't abandon entry guards until they've been down or gone for
15421 - Cleaner and quieter log messages.
15424 - New controller signal NEWNYM that makes new application requests
15425 use clean circuits.
15426 - Add a new circuit purpose 'controller' to let the controller ask
15427 for a circuit that Tor won't try to use. Extend the EXTENDCIRCUIT
15428 controller command to let you specify the purpose if you're
15429 starting a new circuit. Add a new SETCIRCUITPURPOSE controller
15430 command to let you change a circuit's purpose after it's been
15432 - Accept "private:*" in routerdesc exit policies; not generated yet
15433 because older Tors do not understand it.
15434 - Add BSD-style contributed startup script "rc.subr" from Peter
15438 Changes in version 0.1.1.14-alpha - 2006-02-20
15439 o Bugfixes on 0.1.1.x:
15440 - Don't die if we ask for a stdout or stderr log (even implicitly)
15441 and we're set to RunAsDaemon -- just warn.
15442 - We still had a few bugs in the OR connection rotation code that
15443 caused directory servers to slowly aggregate connections to other
15444 fast Tor servers. This time for sure!
15445 - Make log entries on Win32 include the name of the function again.
15446 - We were treating a pair of exit policies if they were equal even
15447 if one said accept and the other said reject -- causing us to
15448 not always publish a new descriptor since we thought nothing
15450 - Retry pending server downloads as well as pending networkstatus
15451 downloads when we unexpectedly get a socks request.
15452 - We were ignoring the IS_FAST flag in the directory status,
15453 meaning we were willing to pick trivial-bandwidth nodes for "fast"
15455 - If the controller's SAVECONF command fails (e.g. due to file
15456 permissions), let the controller know that it failed.
15459 - If we're trying to be a Tor server and running Windows 95/98/ME
15460 as a server, explain that we'll likely crash.
15461 - When we're a server, a client asks for an old-style directory,
15462 and our write bucket is empty, don't give it to him. This way
15463 small servers can continue to serve the directory *sometimes*,
15464 without getting overloaded.
15465 - Compress exit policies even more -- look for duplicate lines
15467 - Clients now honor the "guard" flag in the router status when
15468 picking entry guards, rather than looking at is_fast or is_stable.
15469 - Retain unrecognized lines in $DATADIR/state file, so that we can
15470 be forward-compatible.
15471 - Generate 18.0.0.0/8 address policy format in descs when we can;
15472 warn when the mask is not reducible to a bit-prefix.
15473 - Let the user set ControlListenAddress in the torrc. This can be
15474 dangerous, but there are some cases (like a secured LAN) where it
15476 - Split ReachableAddresses into ReachableDirAddresses and
15477 ReachableORAddresses, so we can restrict Dir conns to port 80
15478 and OR conns to port 443.
15479 - Now we can target arch and OS in rpm builds (contributed by
15480 Phobos). Also make the resulting dist-rpm filename match the
15482 - New config options to help controllers: FetchServerDescriptors
15483 and FetchHidServDescriptors for whether to fetch server
15484 info and hidserv info or let the controller do it, and
15485 PublishServerDescriptor and PublishHidServDescriptors.
15486 - Also let the controller set the __AllDirActionsPrivate config
15487 option if you want all directory fetches/publishes to happen via
15488 Tor (it assumes your controller bootstraps your circuits).
15491 Changes in version 0.1.0.17 - 2006-02-17
15492 o Crash bugfixes on 0.1.0.x:
15493 - When servers with a non-zero DirPort came out of hibernation,
15494 sometimes they would trigger an assert.
15496 o Other important bugfixes:
15497 - On platforms that don't have getrlimit (like Windows), we were
15498 artificially constraining ourselves to a max of 1024
15499 connections. Now just assume that we can handle as many as 15000
15500 connections. Hopefully this won't cause other problems.
15502 o Backported features:
15503 - When we're a server, a client asks for an old-style directory,
15504 and our write bucket is empty, don't give it to him. This way
15505 small servers can continue to serve the directory *sometimes*,
15506 without getting overloaded.
15507 - Whenever you get a 503 in response to a directory fetch, try
15508 once more. This will become important once servers start sending
15509 503's whenever they feel busy.
15510 - Fetch a new directory every 120 minutes, not every 40 minutes.
15511 Now that we have hundreds of thousands of users running the old
15512 directory algorithm, it's starting to hurt a lot.
15513 - Bump up the period for forcing a hidden service descriptor upload
15514 from 20 minutes to 1 hour.
15517 Changes in version 0.1.1.13-alpha - 2006-02-09
15518 o Crashes in 0.1.1.x:
15519 - When you tried to setconf ORPort via the controller, Tor would
15520 crash. So people using TorCP to become a server were sad.
15521 - Solve (I hope) the stack-smashing bug that we were seeing on fast
15522 servers. The problem appears to be something do with OpenSSL's
15523 random number generation, or how we call it, or something. Let me
15524 know if the crashes continue.
15525 - Turn crypto hardware acceleration off by default, until we find
15526 somebody smart who can test it for us. (It appears to produce
15527 seg faults in at least some cases.)
15528 - Fix a rare assert error when we've tried all intro points for
15529 a hidden service and we try fetching the service descriptor again:
15530 "Assertion conn->state != AP_CONN_STATE_RENDDESC_WAIT failed"
15533 - Fix a major load balance bug: we were round-robining in 16 KB
15534 chunks, and servers with bandwidthrate of 20 KB, while downloading
15535 a 600 KB directory, would starve their other connections. Now we
15536 try to be a bit more fair.
15537 - Dir authorities and mirrors were never expiring the newest
15538 descriptor for each server, causing memory and directory bloat.
15539 - Fix memory-bloating and connection-bloating bug on servers: We
15540 were never closing any connection that had ever had a circuit on
15541 it, because we were checking conn->n_circuits == 0, yet we had a
15542 bug that let it go negative.
15543 - Make Tor work using squid as your http proxy again -- squid
15544 returns an error if you ask for a URL that's too long, and it uses
15545 a really generic error message. Plus, many people are behind a
15546 transparent squid so they don't even realize it.
15547 - On platforms that don't have getrlimit (like Windows), we were
15548 artificially constraining ourselves to a max of 1024
15549 connections. Now just assume that we can handle as many as 15000
15550 connections. Hopefully this won't cause other problems.
15551 - Add a new config option ExitPolicyRejectPrivate which defaults to
15552 1. This means all exit policies will begin with rejecting private
15553 addresses, unless the server operator explicitly turns it off.
15556 - Clients no longer download descriptors for non-running
15558 - Before we add new directory authorities, we should make it
15559 clear that only v1 authorities should receive/publish hidden
15560 service descriptors.
15563 - As soon as we've fetched some more directory info, immediately
15564 try to download more server descriptors. This way we don't have
15565 a 10 second pause during initial bootstrapping.
15566 - Remove even more loud log messages that the server operator can't
15568 - When we're running an obsolete or un-recommended version, make
15569 the log message more clear about what the problem is and what
15570 versions *are* still recommended.
15571 - Provide a more useful warn message when our onion queue gets full:
15572 the CPU is too slow or the exit policy is too liberal.
15573 - Don't warn when we receive a 503 from a dirserver/cache -- this
15574 will pave the way for them being able to refuse if they're busy.
15575 - When we fail to bind a listener, try to provide a more useful
15576 log message: e.g., "Is Tor already running?"
15577 - Adjust tor-spec to parameterize cell and key lengths. Now Ian
15578 Goldberg can prove things about our handshake protocol more
15580 - MaxConn has been obsolete for a while now. Document the ConnLimit
15581 config option, which is a *minimum* number of file descriptors
15582 that must be available else Tor refuses to start.
15583 - Apply Matt Ghali's --with-syslog-facility patch to ./configure
15584 if you log to syslog and want something other than LOG_DAEMON.
15585 - Make dirservers generate a separate "guard" flag to mean,
15586 "would make a good entry guard". Make clients parse it and vote
15587 on it. Not used by clients yet.
15588 - Implement --with-libevent-dir option to ./configure. Also, improve
15589 search techniques to find libevent, and use those for openssl too.
15590 - Bump the default bandwidthrate to 3 MB, and burst to 6 MB
15591 - Only start testing reachability once we've established a
15592 circuit. This will make startup on dirservers less noisy.
15593 - Don't try to upload hidden service descriptors until we have
15594 established a circuit.
15595 - Fix the controller's "attachstream 0" command to treat conn like
15596 it just connected, doing address remapping, handling .exit and
15597 .onion idioms, and so on. Now we're more uniform in making sure
15598 that the controller hears about new and closing connections.
15601 Changes in version 0.1.1.12-alpha - 2006-01-11
15602 o Bugfixes on 0.1.1.x:
15603 - The fix to close duplicate server connections was closing all
15604 Tor client connections if they didn't establish a circuit
15605 quickly enough. Oops.
15606 - Fix minor memory issue (double-free) that happened on exit.
15608 o Bugfixes on 0.1.0.x:
15609 - Tor didn't warn when it failed to open a log file.
15612 Changes in version 0.1.1.11-alpha - 2006-01-10
15613 o Crashes in 0.1.1.x:
15614 - Include all the assert/crash fixes from 0.1.0.16.
15615 - If you start Tor and then quit very quickly, there were some
15616 races that tried to free things that weren't allocated yet.
15617 - Fix a rare memory stomp if you're running hidden services.
15618 - Fix segfault when specifying DirServer in config without nickname.
15619 - Fix a seg fault when you finish connecting to a server but at
15620 that moment you dump his server descriptor.
15621 - Extendcircuit and Attachstream controller commands would
15622 assert/crash if you don't give them enough arguments.
15623 - Fix an assert error when we're out of space in the connection_list
15624 and we try to post a hidden service descriptor (reported by weasel).
15625 - If you specify a relative torrc path and you set RunAsDaemon in
15626 your torrc, then it chdir()'s to the new directory. If you HUP,
15627 it tries to load the new torrc location, fails, and exits.
15628 The fix: no longer allow a relative path to torrc using -f.
15631 - Implement "entry guards": automatically choose a handful of entry
15632 nodes and stick with them for all circuits. Only pick new guards
15633 when the ones you have are unsuitable, and if the old guards
15634 become suitable again, switch back. This will increase security
15635 dramatically against certain end-point attacks. The EntryNodes
15636 config option now provides some hints about which entry guards you
15637 want to use most; and StrictEntryNodes means to only use those.
15638 - New directory logic: download by descriptor digest, not by
15639 fingerprint. Caches try to download all listed digests from
15640 authorities; clients try to download "best" digests from caches.
15641 This avoids partitioning and isolating attacks better.
15642 - Make the "stable" router flag in network-status be the median of
15643 the uptimes of running valid servers, and make clients pay
15644 attention to the network-status flags. Thus the cutoff adapts
15645 to the stability of the network as a whole, making IRC, IM, etc
15646 connections more reliable.
15649 - Tor servers with dynamic IP addresses were needing to wait 18
15650 hours before they could start doing reachability testing using
15651 the new IP address and ports. This is because they were using
15652 the internal descriptor to learn what to test, yet they were only
15653 rebuilding the descriptor once they decided they were reachable.
15654 - Tor 0.1.1.9 and 0.1.1.10 had a serious bug that caused clients
15655 to download certain server descriptors, throw them away, and then
15656 fetch them again after 30 minutes. Now mirrors throw away these
15657 server descriptors so clients can't get them.
15658 - We were leaving duplicate connections to other ORs open for a week,
15659 rather than closing them once we detect a duplicate. This only
15660 really affected authdirservers, but it affected them a lot.
15661 - Spread the authdirservers' reachability testing over the entire
15662 testing interval, so we don't try to do 500 TLS's at once every
15666 - If the network is down, and we try to connect to a conn because
15667 we have a circuit in mind, and we timeout (30 seconds) because the
15668 network never answers, we were expiring the circuit, but we weren't
15669 obsoleting the connection or telling the entry_guards functions.
15670 - Some Tor servers process billions of cells per day. These statistics
15671 need to be uint64_t's.
15672 - Check for integer overflows in more places, when adding elements
15673 to smartlists. This could possibly prevent a buffer overflow
15674 on malicious huge inputs. I don't see any, but I haven't looked
15676 - ReachableAddresses kept growing new "reject *:*" lines on every
15678 - When you "setconf log" via the controller, it should remove all
15679 logs. We were automatically adding back in a "log notice stdout".
15680 - Newly bootstrapped Tor networks couldn't establish hidden service
15681 circuits until they had nodes with high uptime. Be more tolerant.
15682 - We were marking servers down when they could not answer every piece
15683 of the directory request we sent them. This was far too harsh.
15684 - Fix the torify (tsocks) config file to not use Tor for localhost
15686 - Directory authorities now go to the proper authority when asking for
15687 a networkstatus, even when they want a compressed one.
15688 - Fix a harmless bug that was causing Tor servers to log
15689 "Got an end because of misc error, but we're not an AP. Closing."
15690 - Authorities were treating their own descriptor changes as cosmetic,
15691 meaning the descriptor available in the network-status and the
15692 descriptor that clients downloaded were different.
15693 - The OS X installer was adding a symlink for tor_resolve but
15694 the binary was called tor-resolve (reported by Thomas Hardly).
15695 - Workaround a problem with some http proxies where they refuse GET
15696 requests that specify "Content-Length: 0" (reported by Adrian).
15697 - Fix wrong log message when you add a "HiddenServiceNodes" config
15698 line without any HiddenServiceDir line (reported by Chris Thomas).
15701 - Write the TorVersion into the state file so we have a prayer of
15702 keeping forward and backward compatibility.
15703 - Revive the FascistFirewall config option rather than eliminating it:
15704 now it's a synonym for ReachableAddresses *:80,*:443.
15705 - Clients choose directory servers from the network status lists,
15706 not from their internal list of router descriptors. Now they can
15707 go to caches directly rather than needing to go to authorities
15709 - Directory authorities ignore router descriptors that have only
15710 cosmetic differences: do this for 0.1.0.x servers now too.
15711 - Add a new flag to network-status indicating whether the server
15712 can answer v2 directory requests too.
15713 - Authdirs now stop whining so loudly about bad descriptors that
15714 they fetch from other dirservers. So when there's a log complaint,
15715 it's for sure from a freshly uploaded descriptor.
15716 - Reduce memory requirements in our structs by changing the order
15718 - There used to be two ways to specify your listening ports in a
15719 server descriptor: on the "router" line and with a separate "ports"
15720 line. Remove support for the "ports" line.
15721 - New config option "AuthDirRejectUnlisted" for auth dirservers as
15722 a panic button: if we get flooded with unusable servers we can
15723 revert to only listing servers in the approved-routers file.
15724 - Auth dir servers can now mark a fingerprint as "!reject" or
15725 "!invalid" in the approved-routers file (as its nickname), to
15726 refuse descriptors outright or include them but marked as invalid.
15727 - Servers store bandwidth history across restarts/crashes.
15728 - Add reasons to DESTROY and RELAY_TRUNCATED cells, so clients can
15729 get a better idea of why their circuits failed. Not used yet.
15730 - Directory mirrors now cache up to 16 unrecognized network-status
15731 docs. Now we can add new authdirservers and they'll be cached too.
15732 - When picking a random directory, prefer non-authorities if any
15734 - New controller option "getinfo desc/all-recent" to fetch the
15735 latest server descriptor for every router that Tor knows about.
15738 Changes in version 0.1.0.16 - 2006-01-02
15739 o Crash bugfixes on 0.1.0.x:
15740 - On Windows, build with a libevent patch from "I-M Weasel" to avoid
15741 corrupting the heap, losing FDs, or crashing when we need to resize
15742 the fd_sets. (This affects the Win32 binaries, not Tor's sources.)
15743 - It turns out sparc64 platforms crash on unaligned memory access
15744 too -- so detect and avoid this.
15745 - Handle truncated compressed data correctly (by detecting it and
15747 - Fix possible-but-unlikely free(NULL) in control.c.
15748 - When we were closing connections, there was a rare case that
15749 stomped on memory, triggering seg faults and asserts.
15750 - Avoid potential infinite recursion when building a descriptor. (We
15751 don't know that it ever happened, but better to fix it anyway.)
15752 - We were neglecting to unlink marked circuits from soon-to-close OR
15753 connections, which caused some rare scribbling on freed memory.
15754 - Fix a memory stomping race bug when closing the joining point of two
15755 rendezvous circuits.
15756 - Fix an assert in time parsing found by Steven Murdoch.
15758 o Other bugfixes on 0.1.0.x:
15759 - When we're doing reachability testing, provide more useful log
15760 messages so the operator knows what to expect.
15761 - Do not check whether DirPort is reachable when we are suppressing
15762 advertising it because of hibernation.
15763 - When building with -static or on Solaris, we sometimes needed -ldl.
15764 - When we're deciding whether a stream has enough circuits around
15765 that can handle it, count the freshly dirty ones and not the ones
15766 that are so dirty they won't be able to handle it.
15767 - When we're expiring old circuits, we had a logic error that caused
15768 us to close new rendezvous circuits rather than old ones.
15769 - Give a more helpful log message when you try to change ORPort via
15770 the controller: you should upgrade Tor if you want that to work.
15771 - We were failing to parse Tor versions that start with "Tor ".
15772 - Tolerate faulty streams better: when a stream fails for reason
15773 exitpolicy, stop assuming that the router is lying about his exit
15774 policy. When a stream fails for reason misc, allow it to retry just
15775 as if it was resolvefailed. When a stream has failed three times,
15776 reset its failure count so we can try again and get all three tries.
15779 Changes in version 0.1.1.10-alpha - 2005-12-11
15780 o Correctness bugfixes on 0.1.0.x:
15781 - On Windows, build with a libevent patch from "I-M Weasel" to avoid
15782 corrupting the heap, losing FDs, or crashing when we need to resize
15783 the fd_sets. (This affects the Win32 binaries, not Tor's sources.)
15784 - Stop doing the complex voodoo overkill checking for insecure
15785 Diffie-Hellman keys. Just check if it's in [2,p-2] and be happy.
15786 - When we were closing connections, there was a rare case that
15787 stomped on memory, triggering seg faults and asserts.
15788 - We were neglecting to unlink marked circuits from soon-to-close OR
15789 connections, which caused some rare scribbling on freed memory.
15790 - When we're deciding whether a stream has enough circuits around
15791 that can handle it, count the freshly dirty ones and not the ones
15792 that are so dirty they won't be able to handle it.
15793 - Recover better from TCP connections to Tor servers that are
15794 broken but don't tell you (it happens!); and rotate TLS
15795 connections once a week.
15796 - When we're expiring old circuits, we had a logic error that caused
15797 us to close new rendezvous circuits rather than old ones.
15798 - Fix a scary-looking but apparently harmless bug where circuits
15799 would sometimes start out in state CIRCUIT_STATE_OR_WAIT at
15800 servers, and never switch to state CIRCUIT_STATE_OPEN.
15801 - When building with -static or on Solaris, we sometimes needed to
15803 - Give a useful message when people run Tor as the wrong user,
15804 rather than telling them to start chowning random directories.
15805 - We were failing to inform the controller about new .onion streams.
15807 o Security bugfixes on 0.1.0.x:
15808 - Refuse server descriptors if the fingerprint line doesn't match
15809 the included identity key. Tor doesn't care, but other apps (and
15810 humans) might actually be trusting the fingerprint line.
15811 - We used to kill the circuit when we receive a relay command we
15812 don't recognize. Now we just drop it.
15813 - Start obeying our firewall options more rigorously:
15814 . If we can't get to a dirserver directly, try going via Tor.
15815 . Don't ever try to connect (as a client) to a place our
15816 firewall options forbid.
15817 . If we specify a proxy and also firewall options, obey the
15818 firewall options even when we're using the proxy: some proxies
15819 can only proxy to certain destinations.
15820 - Fix a bug found by Lasse Overlier: when we were making internal
15821 circuits (intended to be cannibalized later for rendezvous and
15822 introduction circuits), we were picking them so that they had
15823 useful exit nodes. There was no need for this, and it actually
15824 aids some statistical attacks.
15825 - Start treating internal circuits and exit circuits separately.
15826 It's important to keep them separate because internal circuits
15827 have their last hops picked like middle hops, rather than like
15828 exit hops. So exiting on them will break the user's expectations.
15830 o Bugfixes on 0.1.1.x:
15831 - Take out the mis-feature where we tried to detect IP address
15832 flapping for people with DynDNS, and chose not to upload a new
15833 server descriptor sometimes.
15834 - Try to be compatible with OpenSSL 0.9.6 again.
15835 - Log fix: when the controller is logging about .onion addresses,
15836 sometimes it didn't include the ".onion" part of the address.
15837 - Don't try to modify options->DirServers internally -- if the
15838 user didn't specify any, just add the default ones directly to
15839 the trusted dirserver list. This fixes a bug where people running
15840 controllers would use SETCONF on some totally unrelated config
15841 option, and Tor would start yelling at them about changing their
15843 - Let the controller's redirectstream command specify a port, in
15844 case the controller wants to change that too.
15845 - When we requested a pile of server descriptors, we sometimes
15846 accidentally launched a duplicate request for the first one.
15847 - Bugfix for trackhostexits: write down the fingerprint of the
15848 chosen exit, not its nickname, because the chosen exit might not
15850 - When parsing foo.exit, if foo is unknown, and we are leaving
15851 circuits unattached, set the chosen_exit field and leave the
15852 address empty. This matters because controllers got confused
15854 - Directory authorities no longer try to download server
15855 descriptors that they know they will reject.
15857 o Features and updates:
15858 - Replace balanced trees with hash tables: this should make stuff
15859 significantly faster.
15860 - Resume using the AES counter-mode implementation that we ship,
15861 rather than OpenSSL's. Ours is significantly faster.
15862 - Many other CPU and memory improvements.
15863 - Add a new config option FastFirstHopPK (on by default) so clients
15864 do a trivial crypto handshake for their first hop, since TLS has
15865 already taken care of confidentiality and authentication.
15866 - Add a new config option TestSocks so people can see if their
15867 applications are using socks4, socks4a, socks5-with-ip, or
15868 socks5-with-hostname. This way they don't have to keep mucking
15869 with tcpdump and wondering if something got cached somewhere.
15870 - Warn when listening on a public address for socks. I suspect a
15871 lot of people are setting themselves up as open socks proxies,
15872 and they have no idea that jerks on the Internet are using them,
15873 since they simply proxy the traffic into the Tor network.
15874 - Add "private:*" as an alias in configuration for policies. Now
15875 you can simplify your exit policy rather than needing to list
15876 every single internal or nonroutable network space.
15877 - Add a new controller event type that allows controllers to get
15878 all server descriptors that were uploaded to a router in its role
15879 as authoritative dirserver.
15880 - Start shipping socks-extensions.txt, tor-doc-unix.html,
15881 tor-doc-server.html, and stylesheet.css in the tarball.
15882 - Stop shipping tor-doc.html in the tarball.
15885 Changes in version 0.1.1.9-alpha - 2005-11-15
15886 o Usability improvements:
15887 - Start calling it FooListenAddress rather than FooBindAddress,
15888 since few of our users know what it means to bind an address
15890 - Reduce clutter in server logs. We're going to try to make
15891 them actually usable now. New config option ProtocolWarnings that
15892 lets you hear about how _other Tors_ are breaking the protocol. Off
15894 - Divide log messages into logging domains. Once we put some sort
15895 of interface on this, it will let people looking at more verbose
15896 log levels specify the topics they want to hear more about.
15897 - Make directory servers return better http 404 error messages
15898 instead of a generic "Servers unavailable".
15899 - Check for even more Windows version flags when writing the platform
15900 string in server descriptors, and note any we don't recognize.
15901 - Clean up more of the OpenSSL memory when exiting, so we can detect
15902 memory leaks better.
15903 - Make directory authorities be non-versioning, non-naming by
15904 default. Now we can add new directory servers without requiring
15905 their operators to pay close attention.
15906 - When logging via syslog, include the pid whenever we provide
15907 a log entry. Suggested by Todd Fries.
15909 o Performance improvements:
15910 - Directory servers now silently throw away new descriptors that
15911 haven't changed much if the timestamps are similar. We do this to
15912 tolerate older Tor servers that upload a new descriptor every 15
15913 minutes. (It seemed like a good idea at the time.)
15914 - Inline bottleneck smartlist functions; use fast versions by default.
15915 - Add a "Map from digest to void*" abstraction digestmap_t so we
15916 can do less hex encoding/decoding. Use it in router_get_by_digest()
15917 to resolve a performance bottleneck.
15918 - Allow tor_gzip_uncompress to extract as much as possible from
15919 truncated compressed data. Try to extract as many
15920 descriptors as possible from truncated http responses (when
15921 DIR_PURPOSE_FETCH_ROUTERDESC).
15922 - Make circ->onionskin a pointer, not a static array. moria2 was using
15923 125000 circuit_t's after it had been up for a few weeks, which
15924 translates to 20+ megs of wasted space.
15925 - The private half of our EDH handshake keys are now chosen out
15926 of 320 bits, not 1024 bits. (Suggested by Ian Goldberg.)
15928 o Security improvements:
15929 - Start making directory caches retain old routerinfos, so soon
15930 clients can start asking by digest of descriptor rather than by
15931 fingerprint of server.
15932 - Add half our entropy from RAND_poll in OpenSSL. This knows how
15933 to use egd (if present), openbsd weirdness (if present), vms/os2
15934 weirdness (if we ever port there), and more in the future.
15936 o Bugfixes on 0.1.0.x:
15937 - Do round-robin writes of at most 16 kB per write. This might be
15938 more fair on loaded Tor servers, and it might resolve our Windows
15939 crash bug. It might also slow things down.
15940 - Our TLS handshakes were generating a single public/private
15941 keypair for the TLS context, rather than making a new one for
15942 each new connections. Oops. (But we were still rotating them
15943 periodically, so it's not so bad.)
15944 - When we were cannibalizing a circuit with a particular exit
15945 node in mind, we weren't checking to see if that exit node was
15946 already present earlier in the circuit. Oops.
15947 - When a Tor server's IP changes (e.g. from a dyndns address),
15948 upload a new descriptor so clients will learn too.
15949 - Really busy servers were keeping enough circuits open on stable
15950 connections that they were wrapping around the circuit_id
15951 space. (It's only two bytes.) This exposed a bug where we would
15952 feel free to reuse a circuit_id even if it still exists but has
15953 been marked for close. Try to fix this bug. Some bug remains.
15954 - If we would close a stream early (e.g. it asks for a .exit that
15955 we know would refuse it) but the LeaveStreamsUnattached config
15956 option is set by the controller, then don't close it.
15958 o Bugfixes on 0.1.1.8-alpha:
15959 - Fix a big pile of memory leaks, some of them serious.
15960 - Do not try to download a routerdesc if we would immediately reject
15962 - Resume inserting a newline between all router descriptors when
15963 generating (old style) signed directories, since our spec says
15965 - When providing content-type application/octet-stream for
15966 server descriptors using .z, we were leaving out the
15967 content-encoding header. Oops. (Everything tolerated this just
15968 fine, but that doesn't mean we need to be part of the problem.)
15969 - Fix a potential seg fault in getconf and getinfo using version 1
15970 of the controller protocol.
15971 - Avoid crash: do not check whether DirPort is reachable when we
15972 are suppressing it because of hibernation.
15973 - Make --hash-password not crash on exit.
15976 Changes in version 0.1.1.8-alpha - 2005-10-07
15977 o New features (major):
15978 - Clients don't download or use the directory anymore. Now they
15979 download and use network-statuses from the trusted dirservers,
15980 and fetch individual server descriptors as needed from mirrors.
15981 See dir-spec.txt for all the gory details.
15982 - Be more conservative about whether to advertise our DirPort.
15983 The main change is to not advertise if we're running at capacity
15984 and either a) we could hibernate or b) our capacity is low and
15985 we're using a default DirPort.
15986 - Use OpenSSL's AES when OpenSSL has version 0.9.7 or later.
15988 o New features (minor):
15989 - Try to be smart about when to retry network-status and
15990 server-descriptor fetches. Still needs some tuning.
15991 - Stop parsing, storing, or using running-routers output (but
15992 mirrors still cache and serve it).
15993 - Consider a threshold of versioning dirservers (dirservers who have
15994 an opinion about which Tor versions are still recommended) before
15995 deciding whether to warn the user that he's obsolete.
15996 - Dirservers can now reject/invalidate by key and IP, with the
15997 config options "AuthDirInvalid" and "AuthDirReject". This is
15998 useful since currently we automatically list servers as running
15999 and usable even if we know they're jerks.
16000 - Provide dire warnings to any users who set DirServer; move it out
16001 of torrc.sample and into torrc.complete.
16002 - Add MyFamily to torrc.sample in the server section.
16003 - Add nicknames to the DirServer line, so we can refer to them
16004 without requiring all our users to memorize their IP addresses.
16005 - When we get an EOF or a timeout on a directory connection, note
16006 how many bytes of serverdesc we are dropping. This will help
16007 us determine whether it is smart to parse incomplete serverdesc
16009 - Add a new function to "change pseudonyms" -- that is, to stop
16010 using any currently-dirty circuits for new streams, so we don't
16011 link new actions to old actions. Currently it's only called on
16012 HUP (or SIGNAL RELOAD).
16013 - On sighup, if UseHelperNodes changed to 1, use new circuits.
16014 - Start using RAND_bytes rather than RAND_pseudo_bytes from
16015 OpenSSL. Also, reseed our entropy every hour, not just at
16016 startup. And entropy in 512-bit chunks, not 160-bit chunks.
16018 o Fixes on 0.1.1.7-alpha:
16019 - Nobody ever implemented EVENT_ADDRMAP for control protocol
16020 version 0, so don't let version 0 controllers ask for it.
16021 - If you requested something with too many newlines via the
16022 v1 controller protocol, you could crash tor.
16023 - Fix a number of memory leaks, including some pretty serious ones.
16024 - Re-enable DirPort testing again, so Tor servers will be willing
16025 to advertise their DirPort if it's reachable.
16026 - On TLS handshake, only check the other router's nickname against
16027 its expected nickname if is_named is set.
16029 o Fixes forward-ported from 0.1.0.15:
16030 - Don't crash when we don't have any spare file descriptors and we
16031 try to spawn a dns or cpu worker.
16032 - Make the numbers in read-history and write-history into uint64s,
16033 so they don't overflow and publish negatives in the descriptor.
16035 o Fixes on 0.1.0.x:
16036 - For the OS X package's modified privoxy config file, comment
16037 out the "logfile" line so we don't log everything passed
16039 - We were whining about using socks4 or socks5-with-local-lookup
16040 even when it's an IP in the "virtual" range we designed exactly
16042 - We were leaking some memory every time the client changes IPs.
16043 - Never call free() on tor_malloc()d memory. This will help us
16044 use dmalloc to detect memory leaks.
16045 - Check for named servers when looking them up by nickname;
16046 warn when we'recalling a non-named server by its nickname;
16047 don't warn twice about the same name.
16048 - Try to list MyFamily elements by key, not by nickname, and warn
16049 if we've not heard of the server.
16050 - Make windows platform detection (uname equivalent) smarter.
16051 - It turns out sparc64 doesn't like unaligned access either.
16054 Changes in version 0.1.0.15 - 2005-09-23
16055 o Bugfixes on 0.1.0.x:
16056 - Reject ports 465 and 587 (spam targets) in default exit policy.
16057 - Don't crash when we don't have any spare file descriptors and we
16058 try to spawn a dns or cpu worker.
16059 - Get rid of IgnoreVersion undocumented config option, and make us
16060 only warn, never exit, when we're running an obsolete version.
16061 - Don't try to print a null string when your server finds itself to
16062 be unreachable and the Address config option is empty.
16063 - Make the numbers in read-history and write-history into uint64s,
16064 so they don't overflow and publish negatives in the descriptor.
16065 - Fix a minor memory leak in smartlist_string_remove().
16066 - We were only allowing ourselves to upload a server descriptor at
16067 most every 20 minutes, even if it changed earlier than that.
16068 - Clean up log entries that pointed to old URLs.
16071 Changes in version 0.1.1.7-alpha - 2005-09-14
16072 o Fixes on 0.1.1.6-alpha:
16073 - Exit servers were crashing when people asked them to make a
16074 connection to an address not in their exit policy.
16075 - Looking up a non-existent stream for a v1 control connection would
16077 - Fix a seg fault if we ask a dirserver for a descriptor by
16078 fingerprint but he doesn't know about him.
16079 - SETCONF was appending items to linelists, not clearing them.
16080 - SETCONF SocksBindAddress killed Tor if it fails to bind. Now back
16081 out and refuse the setconf if it would fail.
16082 - Downgrade the dirserver log messages when whining about
16086 - Add Peter Palfrader's check-tor script to tor/contrib/
16087 It lets you easily check whether a given server (referenced by
16088 nickname) is reachable by you.
16089 - Numerous changes to move towards client-side v2 directories. Not
16092 o Fixes on 0.1.0.x:
16093 - If the user gave tor an odd number of command-line arguments,
16094 we were silently ignoring the last one. Now we complain and fail.
16095 [This wins the oldest-bug prize -- this bug has been present since
16096 November 2002, as released in Tor 0.0.0.]
16097 - Do not use unaligned memory access on alpha, mips, or mipsel.
16098 It *works*, but is very slow, so we treat them as if it doesn't.
16099 - Retry directory requests if we fail to get an answer we like
16100 from a given dirserver (we were retrying before, but only if
16101 we fail to connect).
16102 - When writing the RecommendedVersions line, sort them first.
16103 - When the client asked for a rendezvous port that the hidden
16104 service didn't want to provide, we were sending an IP address
16105 back along with the end cell. Fortunately, it was zero. But stop
16107 - Correct "your server is reachable" log entries to indicate that
16108 it was self-testing that told us so.
16111 Changes in version 0.1.1.6-alpha - 2005-09-09
16112 o Fixes on 0.1.1.5-alpha:
16113 - We broke fascistfirewall in 0.1.1.5-alpha. Oops.
16114 - Fix segfault in unit tests in 0.1.1.5-alpha. Oops.
16115 - Fix bug with tor_memmem finding a match at the end of the string.
16116 - Make unit tests run without segfaulting.
16117 - Resolve some solaris x86 compile warnings.
16118 - Handle duplicate lines in approved-routers files without warning.
16119 - Fix bug where as soon as a server refused any requests due to his
16120 exit policy (e.g. when we ask for localhost and he tells us that's
16121 127.0.0.1 and he won't do it), we decided he wasn't obeying his
16122 exit policy using him for any exits.
16123 - Only do openssl hardware accelerator stuff if openssl version is
16126 o New controller features/fixes:
16127 - Add a "RESETCONF" command so you can set config options like
16128 AllowUnverifiedNodes and LongLivedPorts to "". Also, if you give
16129 a config option in the torrc with no value, then it clears it
16130 entirely (rather than setting it to its default).
16131 - Add a "GETINFO config-file" to tell us where torrc is.
16132 - Avoid sending blank lines when GETINFO replies should be empty.
16133 - Add a QUIT command for the controller (for using it manually).
16134 - Fix a bug in SAVECONF that was adding default dirservers and
16135 other redundant entries to the torrc file.
16137 o Start on the new directory design:
16138 - Generate, publish, cache, serve new network-status format.
16139 - Publish individual descriptors (by fingerprint, by "all", and by
16141 - Publish client and server recommended versions separately.
16142 - Allow tor_gzip_uncompress() to handle multiple concatenated
16143 compressed strings. Serve compressed groups of router
16144 descriptors. The compression logic here could be more
16146 - Distinguish v1 authorities (all currently trusted directories)
16147 from v2 authorities (all trusted directories).
16148 - Change DirServers config line to note which dirs are v1 authorities.
16149 - Add configuration option "V1AuthoritativeDirectory 1" which
16150 moria1, moria2, and tor26 should set.
16151 - Remove option when getting directory cache to see whether they
16152 support running-routers; they all do now. Replace it with one
16153 to see whether caches support v2 stuff.
16156 - Dirservers now do their own external reachability testing of each
16157 Tor server, and only list them as running if they've been found to
16158 be reachable. We also send back warnings to the server's logs if
16159 it uploads a descriptor that we already believe is unreachable.
16160 - Implement exit enclaves: if we know an IP address for the
16161 destination, and there's a running Tor server at that address
16162 which allows exit to the destination, then extend the circuit to
16163 that exit first. This provides end-to-end encryption and end-to-end
16164 authentication. Also, if the user wants a .exit address or enclave,
16165 use 4 hops rather than 3, and cannibalize a general circ for it
16167 - Permit transitioning from ORPort=0 to ORPort!=0, and back, from the
16168 controller. Also, rotate dns and cpu workers if the controller
16169 changes options that will affect them; and initialize the dns
16170 worker cache tree whether or not we start out as a server.
16171 - Only upload a new server descriptor when options change, 18
16172 hours have passed, uptime is reset, or bandwidth changes a lot.
16173 - Check [X-]Forwarded-For headers in HTTP requests when generating
16174 log messages. This lets people run dirservers (and caches) behind
16175 Apache but still know which IP addresses are causing warnings.
16177 o Config option changes:
16178 - Replace (Fascist)Firewall* config options with a new
16179 ReachableAddresses option that understands address policies.
16180 For example, "ReachableAddresses *:80,*:443"
16181 - Get rid of IgnoreVersion undocumented config option, and make us
16182 only warn, never exit, when we're running an obsolete version.
16183 - Make MonthlyAccountingStart config option truly obsolete now.
16185 o Fixes on 0.1.0.x:
16186 - Reject ports 465 and 587 in the default exit policy, since
16187 people have started using them for spam too.
16188 - It turns out we couldn't bootstrap a network since we added
16189 reachability detection in 0.1.0.1-rc. Good thing the Tor network
16190 has never gone down. Add an AssumeReachable config option to let
16191 servers and dirservers bootstrap. When we're trying to build a
16192 high-uptime or high-bandwidth circuit but there aren't enough
16193 suitable servers, try being less picky rather than simply failing.
16194 - Our logic to decide if the OR we connected to was the right guy
16195 was brittle and maybe open to a mitm for unverified routers.
16196 - We weren't cannibalizing circuits correctly for
16197 CIRCUIT_PURPOSE_C_ESTABLISH_REND and
16198 CIRCUIT_PURPOSE_S_ESTABLISH_INTRO, so we were being forced to
16199 build those from scratch. This should make hidden services faster.
16200 - Predict required circuits better, with an eye toward making hidden
16201 services faster on the service end.
16202 - Retry streams if the exit node sends back a 'misc' failure. This
16203 should result in fewer random failures. Also, after failing
16204 from resolve failed or misc, reset the num failures, so we give
16205 it a fair shake next time we try.
16206 - Clean up the rendezvous warn log msgs, and downgrade some to info.
16207 - Reduce severity on logs about dns worker spawning and culling.
16208 - When we're shutting down and we do something like try to post a
16209 server descriptor or rendezvous descriptor, don't complain that
16210 we seem to be unreachable. Of course we are, we're shutting down.
16211 - Add TTLs to RESOLVED, CONNECTED, and END_REASON_EXITPOLICY cells.
16212 We don't use them yet, but maybe one day our DNS resolver will be
16213 able to discover them.
16214 - Make ContactInfo mandatory for authoritative directory servers.
16215 - Require server descriptors to list IPv4 addresses -- hostnames
16216 are no longer allowed. This also fixes some potential security
16217 problems with people providing hostnames as their address and then
16218 preferentially resolving them to partition users.
16219 - Change log line for unreachability to explicitly suggest /etc/hosts
16220 as the culprit. Also make it clearer what IP address and ports we're
16221 testing for reachability.
16222 - Put quotes around user-supplied strings when logging so users are
16223 more likely to realize if they add bad characters (like quotes)
16225 - Let auth dir servers start without specifying an Address config
16227 - Make unit tests (and other invocations that aren't the real Tor)
16228 run without launching listeners, creating subdirectories, and so on.
16231 Changes in version 0.1.1.5-alpha - 2005-08-08
16232 o Bugfixes included in 0.1.0.14.
16234 o Bugfixes on 0.1.0.x:
16235 - If you write "HiddenServicePort 6667 127.0.0.1 6668" in your
16236 torrc rather than "HiddenServicePort 6667 127.0.0.1:6668",
16237 it would silently using ignore the 6668.
16240 Changes in version 0.1.0.14 - 2005-08-08
16241 o Bugfixes on 0.1.0.x:
16242 - Fix the other half of the bug with crypto handshakes
16244 - Fix an assert trigger if you send a 'signal term' via the
16245 controller when it's listening for 'event info' messages.
16248 Changes in version 0.1.1.4-alpha - 2005-08-04
16249 o Bugfixes included in 0.1.0.13.
16252 - Improve tor_gettimeofday() granularity on windows.
16253 - Make clients regenerate their keys when their IP address changes.
16254 - Implement some more GETINFO goodness: expose helper nodes, config
16255 options, getinfo keys.
16258 Changes in version 0.1.0.13 - 2005-08-04
16259 o Bugfixes on 0.1.0.x:
16260 - Fix a critical bug in the security of our crypto handshakes.
16261 - Fix a size_t underflow in smartlist_join_strings2() that made
16262 it do bad things when you hand it an empty smartlist.
16263 - Fix Windows installer to ship Tor license (thanks to Aphex for
16264 pointing out this oversight) and put a link to the doc directory
16266 - Explicitly set no-unaligned-access for sparc: it turns out the
16267 new gcc's let you compile broken code, but that doesn't make it
16271 Changes in version 0.1.1.3-alpha - 2005-07-23
16272 o Bugfixes on 0.1.1.2-alpha:
16273 - Fix a bug in handling the controller's "post descriptor"
16275 - Fix several bugs in handling the controller's "extend circuit"
16277 - Fix a bug in handling the controller's "stream status" event.
16278 - Fix an assert failure if we have a controller listening for
16279 circuit events and we go offline.
16280 - Re-allow hidden service descriptors to publish 0 intro points.
16281 - Fix a crash when generating your hidden service descriptor if
16282 you don't have enough intro points already.
16284 o New features on 0.1.1.2-alpha:
16285 - New controller function "getinfo accounting", to ask how
16286 many bytes we've used in this time period.
16287 - Experimental support for helper nodes: a lot of the risk from
16288 a small static adversary comes because users pick new random
16289 nodes every time they rebuild a circuit. Now users will try to
16290 stick to the same small set of entry nodes if they can. Not
16291 enabled by default yet.
16293 o Bugfixes on 0.1.0.12:
16294 - If you're an auth dir server, always publish your dirport,
16295 even if you haven't yet found yourself to be reachable.
16296 - Fix a size_t underflow in smartlist_join_strings2() that made
16297 it do bad things when you hand it an empty smartlist.
16300 Changes in version 0.1.0.12 - 2005-07-18
16301 o New directory servers:
16302 - tor26 has changed IP address.
16304 o Bugfixes on 0.1.0.x:
16305 - Fix a possible double-free in tor_gzip_uncompress().
16306 - When --disable-threads is set, do not search for or link against
16307 pthreads libraries.
16308 - Don't trigger an assert if an authoritative directory server
16309 claims its dirport is 0.
16310 - Fix bug with removing Tor as an NT service: some people were
16311 getting "The service did not return an error." Thanks to Matt
16315 Changes in version 0.1.1.2-alpha - 2005-07-15
16316 o New directory servers:
16317 - tor26 has changed IP address.
16319 o Bugfixes on 0.1.0.x, crashes/leaks:
16320 - Port the servers-not-obeying-their-exit-policies fix from
16322 - Fix an fd leak in start_daemon().
16323 - On Windows, you can't always reopen a port right after you've
16324 closed it. So change retry_listeners() to only close and re-open
16325 ports that have changed.
16326 - Fix a possible double-free in tor_gzip_uncompress().
16328 o Bugfixes on 0.1.0.x, usability:
16329 - When tor_socketpair() fails in Windows, give a reasonable
16330 Windows-style errno back.
16331 - Let people type "tor --install" as well as "tor -install" when
16333 want to make it an NT service.
16334 - NT service patch from Matt Edman to improve error messages.
16335 - When the controller asks for a config option with an abbreviated
16336 name, give the full name in our response.
16337 - Correct the man page entry on TrackHostExitsExpire.
16338 - Looks like we were never delivering deflated (i.e. compressed)
16339 running-routers lists, even when asked. Oops.
16340 - When --disable-threads is set, do not search for or link against
16341 pthreads libraries.
16343 o Bugfixes on 0.1.1.x:
16344 - Fix a seg fault with autodetecting which controller version is
16348 - New hidden service descriptor format: put a version in it, and
16349 let people specify introduction/rendezvous points that aren't
16350 in "the directory" (which is subjective anyway).
16351 - Allow the DEBUG controller event to work again. Mark certain log
16352 entries as "don't tell this to controllers", so we avoid cycles.
16355 Changes in version 0.1.0.11 - 2005-06-30
16356 o Bugfixes on 0.1.0.x:
16357 - Fix major security bug: servers were disregarding their
16358 exit policies if clients behaved unexpectedly.
16359 - Make OS X init script check for missing argument, so we don't
16360 confuse users who invoke it incorrectly.
16361 - Fix a seg fault in "tor --hash-password foo".
16362 - The MAPADDRESS control command was broken.
16365 Changes in version 0.1.1.1-alpha - 2005-06-29
16367 - Make OS X init script check for missing argument, so we don't
16368 confuse users who invoke it incorrectly.
16369 - Fix a seg fault in "tor --hash-password foo".
16370 - Fix a possible way to DoS dirservers.
16371 - When we complain that your exit policy implicitly allows local or
16372 private address spaces, name them explicitly so operators can
16374 - Make the log message less scary when all the dirservers are
16375 temporarily unreachable.
16376 - We were printing the number of idle dns workers incorrectly when
16380 - Revised controller protocol (version 1) that uses ascii rather
16381 than binary. Add supporting libraries in python and java so you
16382 can use the controller from your applications without caring how
16383 our protocol works.
16384 - Spiffy new support for crypto hardware accelerators. Can somebody
16388 Changes in version 0.0.9.10 - 2005-06-16
16389 o Bugfixes on 0.0.9.x (backported from 0.1.0.10):
16390 - Refuse relay cells that claim to have a length larger than the
16391 maximum allowed. This prevents a potential attack that could read
16392 arbitrary memory (e.g. keys) from an exit server's process
16396 Changes in version 0.1.0.10 - 2005-06-14
16397 o Allow a few EINVALs from libevent before dying. Warn on kqueue with
16398 libevent before 1.1a.
16401 Changes in version 0.1.0.9-rc - 2005-06-09
16403 - Reset buf->highwater every time buf_shrink() is called, not just on
16404 a successful shrink. This was causing significant memory bloat.
16405 - Fix buffer overflow when checking hashed passwords.
16406 - Security fix: if seeding the RNG on Win32 fails, quit.
16407 - Allow seeding the RNG on Win32 even when you're not running as
16409 - Disable threading on Solaris too. Something is wonky with it,
16410 cpuworkers, and reentrant libs.
16411 - Reenable the part of the code that tries to flush as soon as an
16412 OR outbuf has a full TLS record available. Perhaps this will make
16413 OR outbufs not grow as huge except in rare cases, thus saving lots
16414 of CPU time plus memory.
16415 - Reject malformed .onion addresses rather then passing them on as
16416 normal web requests.
16417 - Adapt patch from Adam Langley: fix possible memory leak in
16418 tor_lookup_hostname().
16419 - Initialize libevent later in the startup process, so the logs are
16420 already established by the time we start logging libevent warns.
16421 - Use correct errno on win32 if libevent fails.
16422 - Check and warn about known-bad/slow libevent versions.
16423 - Pay more attention to the ClientOnly config option.
16424 - Have torctl.in/tor.sh.in check for location of su binary (needed
16426 - Correct/add man page entries for LongLivedPorts, ExitPolicy,
16427 KeepalivePeriod, ClientOnly, NoPublish, HttpProxy, HttpsProxy,
16428 HttpProxyAuthenticator
16429 - Stop warning about sigpipes in the logs. We're going to
16430 pretend that getting these occassionally is normal and fine.
16431 - Resolve OS X installer bugs: stop claiming to be 0.0.9.2 in
16433 installer screens; and don't put stuff into StartupItems unless
16434 the user asks you to.
16435 - Require servers that use the default dirservers to have public IP
16436 addresses. We have too many servers that are configured with private
16437 IPs and their admins never notice the log entries complaining that
16438 their descriptors are being rejected.
16439 - Add OSX uninstall instructions. An actual uninstall script will
16443 Changes in version 0.1.0.8-rc - 2005-05-23
16445 - It turns out that kqueue on OS X 10.3.9 was causing kernel
16446 panics. Disable kqueue on all OS X Tors.
16447 - Fix RPM: remove duplicate line accidentally added to the rpm
16449 - Disable threads on openbsd too, since its gethostaddr is not
16451 - Tolerate libevent 0.8 since it still works, even though it's
16453 - Enable building on Red Hat 9.0 again.
16454 - Allow the middle hop of the testing circuit to be running any
16455 version, now that most of them have the bugfix to let them connect
16456 to unknown servers. This will allow reachability testing to work
16457 even when 0.0.9.7-0.0.9.9 become obsolete.
16458 - Handle relay cells with rh.length too large. This prevents
16459 a potential attack that could read arbitrary memory (maybe even
16460 keys) from the exit server's process.
16461 - We screwed up the dirport reachability testing when we don't yet
16462 have a cached version of the directory. Hopefully now fixed.
16463 - Clean up router_load_single_router() (used by the controller),
16464 so it doesn't seg fault on error.
16465 - Fix a minor memory leak when somebody establishes an introduction
16466 point at your Tor server.
16467 - If a socks connection ends because read fails, don't warn that
16468 you're not sending a socks reply back.
16471 - Add HttpProxyAuthenticator config option too, that works like
16472 the HttpsProxyAuthenticator config option.
16473 - Encode hashed controller passwords in hex instead of base64,
16474 to make it easier to write controllers.
16477 Changes in version 0.1.0.7-rc - 2005-05-17
16479 - Fix a bug in the OS X package installer that prevented it from
16480 installing on Tiger.
16481 - Fix a script bug in the OS X package installer that made it
16482 complain during installation.
16483 - Find libevent even if it's hiding in /usr/local/ and your
16484 CFLAGS and LDFLAGS don't tell you to look there.
16485 - Be able to link with libevent as a shared library (the default
16486 after 1.0d), even if it's hiding in /usr/local/lib and even
16487 if you haven't added /usr/local/lib to your /etc/ld.so.conf,
16488 assuming you're running gcc. Otherwise fail and give a useful
16490 - Fix a bug in the RPM packager: set home directory for _tor to
16491 something more reasonable when first installing.
16492 - Free a minor amount of memory that is still reachable on exit.
16495 Changes in version 0.1.0.6-rc - 2005-05-14
16497 - Implement --disable-threads configure option. Disable threads on
16498 netbsd by default, because it appears to have no reentrant resolver
16500 - Apple's OS X 10.4.0 ships with a broken kqueue. The new libevent
16501 release (1.1) detects and disables kqueue if it's broken.
16502 - Append default exit policy before checking for implicit internal
16503 addresses. Now we don't log a bunch of complaints on startup
16504 when using the default exit policy.
16505 - Some people were putting "Address " in their torrc, and they had
16506 a buggy resolver that resolved " " to 0.0.0.0. Oops.
16507 - If DataDir is ~/.tor, and that expands to /.tor, then default to
16508 LOCALSTATEDIR/tor instead.
16509 - Fix fragmented-message bug in TorControl.py.
16510 - Resolve a minor bug which would prevent unreachable dirports
16511 from getting suppressed in the published descriptor.
16512 - When the controller gave us a new descriptor, we weren't resolving
16513 it immediately, so Tor would think its address was 0.0.0.0 until
16514 we fetched a new directory.
16515 - Fix an uppercase/lowercase case error in suppressing a bogus
16516 libevent warning on some Linuxes.
16519 - Begin scrubbing sensitive strings from logs by default. Turn off
16520 the config option SafeLogging if you need to do debugging.
16521 - Switch to a new buffer management algorithm, which tries to avoid
16522 reallocing and copying quite as much. In first tests it looks like
16523 it uses *more* memory on average, but less cpu.
16524 - First cut at support for "create-fast" cells. Clients can use
16525 these when extending to their first hop, since the TLS already
16526 provides forward secrecy and authentication. Not enabled on
16528 - When dirservers refuse a router descriptor, we now log its
16529 contactinfo, platform, and the poster's IP address.
16530 - Call tor_free_all instead of connections_free_all after forking, to
16531 save memory on systems that need to fork.
16532 - Whine at you if you're a server and you don't set your contactinfo.
16533 - Implement --verify-config command-line option to check if your torrc
16534 is valid without actually launching Tor.
16535 - Rewrite address "serifos.exit" to "localhost.serifos.exit"
16536 rather than just rejecting it.
16539 Changes in version 0.1.0.5-rc - 2005-04-27
16541 - Stop trying to print a null pointer if an OR conn fails because
16542 we didn't like its cert.
16544 - Switch our internal buffers implementation to use a ring buffer,
16545 to hopefully improve performance for fast servers a lot.
16546 - Add HttpsProxyAuthenticator support (basic auth only), based
16547 on patch from Adam Langley.
16548 - Bump the default BandwidthRate from 1 MB to 2 MB, to accommodate
16549 the fast servers that have been joining lately.
16550 - Give hidden service accesses extra time on the first attempt,
16551 since 60 seconds is often only barely enough. This might improve
16553 - Improve performance for dirservers: stop re-parsing the whole
16554 directory every time you regenerate it.
16555 - Add more debugging info to help us find the weird dns freebsd
16556 pthreads bug; cleaner debug messages to help track future issues.
16559 Changes in version 0.0.9.9 - 2005-04-23
16560 o Bugfixes on 0.0.9.x:
16561 - If unofficial Tor clients connect and send weird TLS certs, our
16562 Tor server triggers an assert. This release contains a minimal
16563 backport from the broader fix that we put into 0.1.0.4-rc.
16566 Changes in version 0.1.0.4-rc - 2005-04-23
16568 - If unofficial Tor clients connect and send weird TLS certs, our
16569 Tor server triggers an assert. Stop asserting, and start handling
16570 TLS errors better in other situations too.
16571 - When the controller asks us to tell it about all the debug-level
16572 logs, it turns out we were generating debug-level logs while
16573 telling it about them, which turns into a bad loop. Now keep
16574 track of whether you're sending a debug log to the controller,
16575 and don't log when you are.
16576 - Fix the "postdescriptor" feature of the controller interface: on
16577 non-complete success, only say "done" once.
16579 - Clients are now willing to load balance over up to 2mB, not 1mB,
16580 of advertised bandwidth capacity.
16581 - Add a NoPublish config option, so you can be a server (e.g. for
16582 testing running Tor servers in other Tor networks) without
16583 publishing your descriptor to the primary dirservers.
16586 Changes in version 0.1.0.3-rc - 2005-04-08
16587 o Improvements on 0.1.0.2-rc:
16588 - Client now retries when streams end early for 'hibernating' or
16589 'resource limit' reasons, rather than failing them.
16590 - More automated handling for dirserver operators:
16591 - Automatically approve nodes running 0.1.0.2-rc or later,
16592 now that the the reachability detection stuff is working.
16593 - Now we allow two unverified servers with the same nickname
16594 but different keys. But if a nickname is verified, only that
16595 nickname+key are allowed.
16596 - If you're an authdirserver connecting to an address:port,
16597 and it's not the OR you were expecting, forget about that
16598 descriptor. If he *was* the one you were expecting, then forget
16599 about all other descriptors for that address:port.
16600 - Allow servers to publish descriptors from 12 hours in the future.
16601 Corollary: only whine about clock skew from the dirserver if
16602 he's a trusted dirserver (since now even verified servers could
16603 have quite wrong clocks).
16604 - Adjust maximum skew and age for rendezvous descriptors: let skew
16605 be 48 hours rather than 90 minutes.
16606 - Efficiency improvements:
16607 - Keep a big splay tree of (circid,orconn)->circuit mappings to make
16608 it much faster to look up a circuit for each relay cell.
16609 - Remove most calls to assert_all_pending_dns_resolves_ok(),
16610 since they're eating our cpu on exit nodes.
16611 - Stop wasting time doing a case insensitive comparison for every
16612 dns name every time we do any lookup. Canonicalize the names to
16613 lowercase and be done with it.
16614 - Start sending 'truncated' cells back rather than destroy cells,
16615 if the circuit closes in front of you. This means we won't have
16616 to abandon partially built circuits.
16617 - Only warn once per nickname from add_nickname_list_to_smartlist
16618 per failure, so an entrynode or exitnode choice that's down won't
16620 - Put a note in the torrc about abuse potential with the default
16622 - Revise control spec and implementation to allow all log messages to
16623 be sent to controller with their severities intact (suggested by
16624 Matt Edman). Update TorControl to handle new log event types.
16625 - Provide better explanation messages when controller's POSTDESCRIPTOR
16627 - Stop putting nodename in the Platform string in server descriptors.
16628 It doesn't actually help, and it is confusing/upsetting some people.
16630 o Bugfixes on 0.1.0.2-rc:
16631 - We were printing the host mask wrong in exit policies in server
16632 descriptors. This isn't a critical bug though, since we were still
16633 obeying the exit policy internally.
16634 - Fix Tor when compiled with libevent but without pthreads: move
16635 connection_unregister() from _connection_free() to
16637 - Fix an assert trigger (already fixed in 0.0.9.x): when we have
16638 the rare mysterious case of accepting a conn on 0.0.0.0:0, then
16639 when we look through the connection array, we'll find any of the
16640 cpu/dnsworkers. This is no good.
16642 o Bugfixes on 0.0.9.8:
16643 - Fix possible bug on threading platforms (e.g. win32) which was
16644 leaking a file descriptor whenever a cpuworker or dnsworker died.
16645 - When using preferred entry or exit nodes, ignore whether the
16646 circuit wants uptime or capacity. They asked for the nodes, they
16648 - chdir() to your datadirectory at the *end* of the daemonize process,
16649 not the beginning. This was a problem because the first time you
16650 run tor, if your datadir isn't there, and you have runasdaemon set
16651 to 1, it will try to chdir to it before it tries to create it. Oops.
16652 - Handle changed router status correctly when dirserver reloads
16653 fingerprint file. We used to be dropping all unverified descriptors
16654 right then. The bug was hidden because we would immediately
16655 fetch a directory from another dirserver, which would include the
16656 descriptors we just dropped.
16657 - When we're connecting to an OR and he's got a different nickname/key
16658 than we were expecting, only complain loudly if we're an OP or a
16659 dirserver. Complaining loudly to the OR admins just confuses them.
16660 - Tie MAX_DIR_SIZE to MAX_BUF_SIZE, so now directory sizes won't get
16661 artificially capped at 500kB.
16664 Changes in version 0.0.9.8 - 2005-04-07
16665 o Bugfixes on 0.0.9.x:
16666 - We have a bug that I haven't found yet. Sometimes, very rarely,
16667 cpuworkers get stuck in the 'busy' state, even though the cpuworker
16668 thinks of itself as idle. This meant that no new circuits ever got
16669 established. Here's a workaround to kill any cpuworker that's been
16670 busy for more than 100 seconds.
16673 Changes in version 0.1.0.2-rc - 2005-04-01
16674 o Bugfixes on 0.1.0.1-rc:
16675 - Fixes on reachability detection:
16676 - Don't check for reachability while hibernating.
16677 - If ORPort is reachable but DirPort isn't, still publish the
16678 descriptor, but zero out DirPort until it's found reachable.
16679 - When building testing circs for ORPort testing, use only
16680 high-bandwidth nodes, so fewer circuits fail.
16681 - Complain about unreachable ORPort separately from unreachable
16682 DirPort, so the user knows what's going on.
16683 - Make sure we only conclude ORPort reachability if we didn't
16684 initiate the conn. Otherwise we could falsely conclude that
16685 we're reachable just because we connected to the guy earlier
16686 and he used that same pipe to extend to us.
16687 - Authdirservers shouldn't do ORPort reachability detection,
16688 since they're in clique mode, so it will be rare to find a
16689 server not already connected to them.
16690 - When building testing circuits, always pick middle hops running
16691 Tor 0.0.9.7, so we avoid the "can't extend to unknown routers"
16692 bug. (This is a kludge; it will go away when 0.0.9.x becomes
16694 - When we decide we're reachable, actually publish our descriptor
16696 - Fix bug in redirectstream in the controller.
16697 - Fix the state descriptor strings so logs don't claim edge streams
16698 are in a different state than they actually are.
16699 - Use recent libevent features when possible (this only really affects
16700 win32 and osx right now, because the new libevent with these
16701 features hasn't been released yet). Add code to suppress spurious
16703 - Prevent possible segfault in connection_close_unattached_ap().
16704 - Fix newlines on torrc in win32.
16705 - Improve error msgs when tor-resolve fails.
16707 o Improvements on 0.0.9.x:
16708 - New experimental script tor/contrib/ExerciseServer.py (needs more
16709 work) that uses the controller interface to build circuits and
16710 fetch pages over them. This will help us bootstrap servers that
16711 have lots of capacity but haven't noticed it yet.
16712 - New experimental script tor/contrib/PathDemo.py (needs more work)
16713 that uses the controller interface to let you choose whole paths
16715 "<hostname>.<path,separated by dots>.<length of path>.path"
16716 - When we've connected to an OR and handshaked but didn't like
16717 the result, we were closing the conn without sending destroy
16718 cells back for pending circuits. Now send those destroys.
16721 Changes in version 0.0.9.7 - 2005-04-01
16722 o Bugfixes on 0.0.9.x:
16723 - Fix another race crash bug (thanks to Glenn Fink for reporting).
16724 - Compare identity to identity, not to nickname, when extending to
16725 a router not already in the directory. This was preventing us from
16726 extending to unknown routers. Oops.
16727 - Make sure to create OS X Tor user in <500 range, so we aren't
16728 creating actual system users.
16729 - Note where connection-that-hasn't-sent-end was marked, and fix
16730 a few really loud instances of this harmless bug (it's fixed more
16734 Changes in version 0.1.0.1-rc - 2005-03-28
16736 - Add reachability testing. Your Tor server will automatically try
16737 to see if its ORPort and DirPort are reachable from the outside,
16738 and it won't upload its descriptor until it decides they are.
16739 - Handle unavailable hidden services better. Handle slow or busy
16740 hidden services better.
16741 - Add support for CONNECTing through https proxies, with "HttpsProxy"
16743 - New exit policy: accept most low-numbered ports, rather than
16744 rejecting most low-numbered ports.
16745 - More Tor controller support (still experimental). See
16746 http://tor.eff.org/doc/control-spec.txt for all the new features,
16747 including signals to emulate unix signals from any platform;
16748 redirectstream; extendcircuit; mapaddress; getinfo; postdescriptor;
16749 closestream; closecircuit; etc.
16750 - Make nt services work and start on startup on win32 (based on
16751 patch by Matt Edman).
16752 - Add a new AddressMap config directive to rewrite incoming socks
16753 addresses. This lets you, for example, declare an implicit
16754 required exit node for certain sites.
16755 - Add a new TrackHostExits config directive to trigger addressmaps
16756 for certain incoming socks addresses -- for sites that break when
16757 your exit keeps changing (based on patch by Mike Perry).
16758 - Redo the client-side dns cache so it's just an addressmap too.
16759 - Notice when our IP changes, and reset stats/uptime/reachability.
16760 - When an application is using socks5, give him the whole variety of
16761 potential socks5 responses (connect refused, host unreachable, etc),
16762 rather than just "success" or "failure".
16763 - A more sane version numbering system. See
16764 http://tor.eff.org/cvs/tor/doc/version-spec.txt for details.
16765 - New contributed script "exitlist": a simple python script to
16766 parse directories and find Tor nodes that exit to listed
16768 - New contributed script "privoxy-tor-toggle" to toggle whether
16769 Privoxy uses Tor. Seems to be configured for Debian by default.
16770 - Report HTTP reasons to client when getting a response from directory
16771 servers -- so you can actually know what went wrong.
16772 - New config option MaxAdvertisedBandwidth which lets you advertise
16773 a low bandwidthrate (to not attract as many circuits) while still
16774 allowing a higher bandwidthrate in reality.
16776 o Robustness/stability fixes:
16777 - Make Tor use Niels Provos's libevent instead of its current
16778 poll-but-sometimes-select mess. This will let us use faster async
16779 cores (like epoll, kpoll, and /dev/poll), and hopefully work better
16781 - pthread support now too. This was forced because when we forked,
16782 we ended up wasting a lot of duplicate ram over time. Also switch
16783 to foo_r versions of some library calls to allow reentry and
16785 - Better handling for heterogeneous / unreliable nodes:
16786 - Annotate circuits w/ whether they aim to contain high uptime nodes
16787 and/or high capacity nodes. When building circuits, choose
16789 - This means that every single node in an intro rend circuit,
16790 not just the last one, will have a minimum uptime.
16791 - New config option LongLivedPorts to indicate application streams
16792 that will want high uptime circuits.
16793 - Servers reset uptime when a dir fetch entirely fails. This
16794 hopefully reflects stability of the server's network connectivity.
16795 - If somebody starts his tor server in Jan 2004 and then fixes his
16796 clock, don't make his published uptime be a year.
16797 - Reset published uptime when you wake up from hibernation.
16798 - Introduce a notion of 'internal' circs, which are chosen without
16799 regard to the exit policy of the last hop. Intro and rendezvous
16800 circs must be internal circs, to avoid leaking information. Resolve
16801 and connect streams can use internal circs if they want.
16802 - New circuit pooling algorithm: make sure to have enough circs around
16803 to satisfy any predicted ports, and also make sure to have 2 internal
16804 circs around if we've required internal circs lately (and with high
16805 uptime if we've seen that lately too).
16806 - Split NewCircuitPeriod option into NewCircuitPeriod (30 secs),
16807 which describes how often we retry making new circuits if current
16808 ones are dirty, and MaxCircuitDirtiness (10 mins), which describes
16809 how long we're willing to make use of an already-dirty circuit.
16810 - Cannibalize GENERAL circs to be C_REND, C_INTRO, S_INTRO, and S_REND
16811 circ as necessary, if there are any completed ones lying around
16812 when we try to launch one.
16813 - Make hidden services try to establish a rendezvous for 30 seconds,
16814 rather than for n (where n=3) attempts to build a circuit.
16815 - Change SHUTDOWN_WAIT_LENGTH from a fixed 30 secs to a config option
16816 "ShutdownWaitLength".
16817 - Try to be more zealous about calling connection_edge_end when
16818 things go bad with edge conns in connection.c.
16819 - Revise tor-spec to add more/better stream end reasons.
16820 - Revise all calls to connection_edge_end to avoid sending "misc",
16821 and to take errno into account where possible.
16824 - Fix a race condition that can trigger an assert, when we have a
16825 pending create cell and an OR connection fails right then.
16826 - Fix several double-mark-for-close bugs, e.g. where we were finding
16827 a conn for a cell even if that conn is already marked for close.
16828 - Make sequence of log messages when starting on win32 with no config
16829 file more reasonable.
16830 - When choosing an exit node for a new non-internal circ, don't take
16831 into account whether it'll be useful for any pending x.onion
16832 addresses -- it won't.
16833 - Turn addr_policy_compare from a tristate to a quadstate; this should
16834 help address our "Ah, you allow 1.2.3.4:80. You are a good choice
16835 for google.com" problem.
16836 - Make "platform" string in descriptor more accurate for Win32 servers,
16837 so it's not just "unknown platform".
16838 - Fix an edge case in parsing config options (thanks weasel).
16839 If they say "--" on the commandline, it's not an option.
16840 - Reject odd-looking addresses at the client (e.g. addresses that
16841 contain a colon), rather than having the server drop them because
16843 - tor-resolve requests were ignoring .exit if there was a working circuit
16844 they could use instead.
16845 - REUSEADDR on normal platforms means you can rebind to the port
16846 right after somebody else has let it go. But REUSEADDR on win32
16847 means to let you bind to the port _even when somebody else
16848 already has it bound_! So, don't do that on Win32.
16849 - Change version parsing logic: a version is "obsolete" if it is not
16850 recommended and (1) there is a newer recommended version in the
16851 same series, or (2) there are no recommended versions in the same
16852 series, but there are some recommended versions in a newer series.
16853 A version is "new" if it is newer than any recommended version in
16855 - Stop most cases of hanging up on a socks connection without sending
16859 - Require BandwidthRate to be at least 20kB/s for servers.
16860 - When a dirserver causes you to give a warn, mention which dirserver
16862 - New config option DirAllowPrivateAddresses for authdirservers.
16863 Now by default they refuse router descriptors that have non-IP or
16864 private-IP addresses.
16865 - Stop publishing socksport in the directory, since it's not
16866 actually meant to be public. For compatibility, publish a 0 there
16868 - Change DirFetchPeriod/StatusFetchPeriod to have a special "Be
16869 smart" value, that is low for servers and high for clients.
16870 - If our clock jumps forward by 100 seconds or more, assume something
16871 has gone wrong with our network and abandon all not-yet-used circs.
16872 - Warn when exit policy implicitly allows local addresses.
16873 - If we get an incredibly skewed timestamp from a dirserver mirror
16874 that isn't a verified OR, don't warn -- it's probably him that's
16876 - Since we ship our own Privoxy on OS X, tweak it so it doesn't write
16877 cookies to disk and doesn't log each web request to disk. (Thanks
16878 to Brett Carrington for pointing this out.)
16879 - When a client asks us for a dir mirror and we don't have one,
16880 launch an attempt to get a fresh one.
16881 - If we're hibernating and we get a SIGINT, exit immediately.
16882 - Add --with-dmalloc ./configure option, to track memory leaks.
16883 - And try to free all memory on closing, so we can detect what
16885 - Cache local dns resolves correctly even when they're .exit
16887 - Give a better warning when some other server advertises an
16888 ORPort that is actually an apache running ssl.
16889 - Add "opt hibernating 1" to server descriptor to make it clearer
16890 whether the server is hibernating.
16893 Changes in version 0.0.9.6 - 2005-03-24
16894 o Bugfixes on 0.0.9.x (crashes and asserts):
16895 - Add new end stream reasons to maintainance branch. Fix bug where
16896 reason (8) could trigger an assert. Prevent bug from recurring.
16897 - Apparently win32 stat wants paths to not end with a slash.
16898 - Fix assert triggers in assert_cpath_layer_ok(), where we were
16899 blowing away the circuit that conn->cpath_layer points to, then
16900 checking to see if the circ is well-formed. Backport check to make
16901 sure we dont use the cpath on a closed connection.
16902 - Prevent circuit_resume_edge_reading_helper() from trying to package
16903 inbufs for marked-for-close streams.
16904 - Don't crash on hup if your options->address has become unresolvable.
16905 - Some systems (like OS X) sometimes accept() a connection and tell
16906 you the remote host is 0.0.0.0:0. If this happens, due to some
16907 other mis-features, we get confused; so refuse the conn for now.
16909 o Bugfixes on 0.0.9.x (other):
16910 - Fix harmless but scary "Unrecognized content encoding" warn message.
16911 - Add new stream error reason: TORPROTOCOL reason means "you are not
16912 speaking a version of Tor I understand; say bye-bye to your stream."
16913 - Be willing to cache directories from up to ROUTER_MAX_AGE seconds
16914 into the future, now that we are more tolerant of skew. This
16915 resolves a bug where a Tor server would refuse to cache a directory
16916 because all the directories it gets are too far in the future;
16917 yet the Tor server never logs any complaints about clock skew.
16918 - Mac packaging magic: make man pages useable, and do not overwrite
16919 existing torrc files.
16920 - Make OS X log happily to /var/log/tor/tor.log
16923 Changes in version 0.0.9.5 - 2005-02-22
16924 o Bugfixes on 0.0.9.x:
16925 - Fix an assert race at exit nodes when resolve requests fail.
16926 - Stop picking unverified dir mirrors--it only leads to misery.
16927 - Patch from Matt Edman to make NT services work better. Service
16928 support is still not compiled into the executable by default.
16929 - Patch from Dmitri Bely so the Tor service runs better under
16930 the win32 SYSTEM account.
16931 - Make tor-resolve actually work (?) on Win32.
16932 - Fix a sign bug when getrlimit claims to have 4+ billion
16933 file descriptors available.
16934 - Stop refusing to start when bandwidthburst == bandwidthrate.
16935 - When create cells have been on the onion queue more than five
16936 seconds, just send back a destroy and take them off the list.
16939 Changes in version 0.0.9.4 - 2005-02-03
16940 o Bugfixes on 0.0.9:
16941 - Fix an assert bug that took down most of our servers: when
16942 a server claims to have 1 GB of bandwidthburst, don't
16944 - Don't crash as badly if we have spawned the max allowed number
16945 of dnsworkers, or we're out of file descriptors.
16946 - Block more file-sharing ports in the default exit policy.
16947 - MaxConn is now automatically set to the hard limit of max
16948 file descriptors we're allowed (ulimit -n), minus a few for
16950 - Give a clearer message when servers need to raise their
16951 ulimit -n when they start running out of file descriptors.
16952 - SGI Compatibility patches from Jan Schaumann.
16953 - Tolerate a corrupt cached directory better.
16954 - When a dirserver hasn't approved your server, list which one.
16955 - Go into soft hibernation after 95% of the bandwidth is used,
16956 not 99%. This is especially important for daily hibernators who
16957 have a small accounting max. Hopefully it will result in fewer
16958 cut connections when the hard hibernation starts.
16959 - Load-balance better when using servers that claim more than
16960 800kB/s of capacity.
16961 - Make NT services work (experimental, only used if compiled in).
16964 Changes in version 0.0.9.3 - 2005-01-21
16965 o Bugfixes on 0.0.9:
16966 - Backport the cpu use fixes from main branch, so busy servers won't
16967 need as much processor time.
16968 - Work better when we go offline and then come back, or when we
16969 run Tor at boot before the network is up. We do this by
16970 optimistically trying to fetch a new directory whenever an
16971 application request comes in and we think we're offline -- the
16972 human is hopefully a good measure of when the network is back.
16973 - Backport some minimal hidserv bugfixes: keep rend circuits open as
16974 long as you keep using them; actually publish hidserv descriptors
16975 shortly after they change, rather than waiting 20-40 minutes.
16976 - Enable Mac startup script by default.
16977 - Fix duplicate dns_cancel_pending_resolve reported by Giorgos Pallas.
16978 - When you update AllowUnverifiedNodes or FirewallPorts via the
16979 controller's setconf feature, we were always appending, never
16981 - When you update HiddenServiceDir via setconf, it was screwing up
16982 the order of reading the lines, making it fail.
16983 - Do not rewrite a cached directory back to the cache; otherwise we
16984 will think it is recent and not fetch a newer one on startup.
16985 - Workaround for webservers that lie about Content-Encoding: Tor
16986 now tries to autodetect compressed directories and compression
16987 itself. This lets us Proxypass dir fetches through apache.
16990 Changes in version 0.0.9.2 - 2005-01-04
16991 o Bugfixes on 0.0.9 (crashes and asserts):
16992 - Fix an assert on startup when the disk is full and you're logging
16994 - If you do socks4 with an IP of 0.0.0.x but *don't* provide a socks4a
16995 style address, then we'd crash.
16996 - Fix an assert trigger when the running-routers string we get from
16997 a dirserver is broken.
16998 - Make worker threads start and run on win32. Now win32 servers
17000 - Bandaid (not actually fix, but now it doesn't crash) an assert
17001 where the dns worker dies mysteriously and the main Tor process
17002 doesn't remember anything about the address it was resolving.
17004 o Bugfixes on 0.0.9 (Win32):
17005 - Workaround for brain-damaged __FILE__ handling on MSVC: keep Nick's
17006 name out of the warning/assert messages.
17007 - Fix a superficial "unhandled error on read" bug on win32.
17008 - The win32 installer no longer requires a click-through for our
17009 license, since our Free Software license grants rights but does not
17011 - Win32: When connecting to a dirserver fails, try another one
17012 immediately. (This was already working for non-win32 Tors.)
17013 - Stop trying to parse $HOME on win32 when hunting for default
17015 - Make tor-resolve.c work on win32 by calling network_init().
17017 o Bugfixes on 0.0.9 (other):
17018 - Make 0.0.9.x build on Solaris again.
17019 - Due to a fencepost error, we were blowing away the \n when reporting
17020 confvalue items in the controller. So asking for multiple config
17021 values at once couldn't work.
17022 - When listing circuits that are pending on an opening OR connection,
17023 if we're an OR we were listing circuits that *end* at us as
17024 being pending on every listener, dns/cpu worker, etc. Stop that.
17025 - Dirservers were failing to create 'running-routers' or 'directory'
17026 strings if we had more than some threshold of routers. Fix them so
17027 they can handle any number of routers.
17028 - Fix a superficial "Duplicate mark for close" bug.
17029 - Stop checking for clock skew for OR connections, even for servers.
17030 - Fix a fencepost error that was chopping off the last letter of any
17031 nickname that is the maximum allowed nickname length.
17032 - Update URLs in log messages so they point to the new website.
17033 - Fix a potential problem in mangling server private keys while
17034 writing to disk (not triggered yet, as far as we know).
17035 - Include the licenses for other free software we include in Tor,
17036 now that we're shipping binary distributions more regularly.
17039 Changes in version 0.0.9.1 - 2004-12-15
17040 o Bugfixes on 0.0.9:
17041 - Make hibernation actually work.
17042 - Make HashedControlPassword config option work.
17043 - When we're reporting event circuit status to a controller,
17044 don't use the stream status code.
17047 Changes in version 0.0.9 - 2004-12-12
17049 - Clean up manpage and torrc.sample file.
17050 - Clean up severities and text of log warnings.
17052 - Make servers trigger an assert when they enter hibernation.
17055 Changes in version 0.0.9rc7 - 2004-12-08
17056 o Bugfixes on 0.0.9rc:
17057 - Fix a stack-trashing crash when an exit node begins hibernating.
17058 - Avoid looking at unallocated memory while considering which
17059 ports we need to build circuits to cover.
17060 - Stop a sigpipe: when an 'end' cell races with eof from the app,
17061 we shouldn't hold-open-until-flush if the eof arrived first.
17062 - Fix a bug with init_cookie_authentication() in the controller.
17063 - When recommending new-format log lines, if the upper bound is
17064 LOG_ERR, leave it implicit.
17066 o Bugfixes on 0.0.8.1:
17067 - Fix a whole slew of memory leaks.
17068 - Fix isspace() and friends so they still make Solaris happy
17069 but also so they don't trigger asserts on win32.
17070 - Fix parse_iso_time on platforms without strptime (eg win32).
17071 - win32: tolerate extra "readable" events better.
17072 - win32: when being multithreaded, leave parent fdarray open.
17073 - Make unit tests work on win32.
17076 Changes in version 0.0.9rc6 - 2004-12-06
17077 o Bugfixes on 0.0.9pre:
17078 - Clean up some more integer underflow opportunities (not exploitable
17080 - While hibernating, hup should not regrow our listeners.
17081 - Send an end to the streams we close when we hibernate, rather
17082 than just chopping them off.
17083 - React to eof immediately on non-open edge connections.
17085 o Bugfixes on 0.0.8.1:
17086 - Calculate timeout for waiting for a connected cell from the time
17087 we sent the begin cell, not from the time the stream started. If
17088 it took a long time to establish the circuit, we would time out
17089 right after sending the begin cell.
17090 - Fix router_compare_addr_to_addr_policy: it was not treating a port
17091 of * as always matching, so we were picking reject *:* nodes as
17092 exit nodes too. Oops.
17095 - New circuit building strategy: keep a list of ports that we've
17096 used in the past 6 hours, and always try to have 2 circuits open
17097 or on the way that will handle each such port. Seed us with port
17098 80 so web users won't complain that Tor is "slow to start up".
17099 - Make kill -USR1 dump more useful stats about circuits.
17100 - When warning about retrying or giving up, print the address, so
17101 the user knows which one it's talking about.
17102 - If you haven't used a clean circuit in an hour, throw it away,
17103 just to be on the safe side. (This means after 6 hours a totally
17104 unused Tor client will have no circuits open.)
17107 Changes in version 0.0.9rc5 - 2004-12-01
17108 o Bugfixes on 0.0.8.1:
17109 - Disallow NDEBUG. We don't ever want anybody to turn off debug.
17110 - Let resolve conns retry/expire also, rather than sticking around
17112 - If we are using select, make sure we stay within FD_SETSIZE.
17114 o Bugfixes on 0.0.9pre:
17115 - Fix integer underflow in tor_vsnprintf() that may be exploitable,
17116 but doesn't seem to be currently; thanks to Ilja van Sprundel for
17118 - If anybody set DirFetchPostPeriod, give them StatusFetchPeriod
17119 instead. Impose minima and maxima for all *Period options; impose
17120 even tighter maxima for fetching if we are a caching dirserver.
17121 Clip rather than rejecting.
17122 - Fetch cached running-routers from servers that serve it (that is,
17123 authdirservers and servers running 0.0.9rc5-cvs or later.)
17126 - Accept *:706 (silc) in default exit policy.
17127 - Implement new versioning format for post 0.1.
17128 - Support "foo.nickname.exit" addresses, to let Alice request the
17129 address "foo" as viewed by exit node "nickname". Based on a patch
17131 - Make tor --version --version dump the cvs Id of every file.
17134 Changes in version 0.0.9rc4 - 2004-11-28
17135 o Bugfixes on 0.0.8.1:
17136 - Make windows sockets actually non-blocking (oops), and handle
17137 win32 socket errors better.
17139 o Bugfixes on 0.0.9rc1:
17140 - Actually catch the -USR2 signal.
17143 Changes in version 0.0.9rc3 - 2004-11-25
17144 o Bugfixes on 0.0.8.1:
17145 - Flush the log file descriptor after we print "Tor opening log file",
17146 so we don't see those messages days later.
17148 o Bugfixes on 0.0.9rc1:
17149 - Make tor-resolve work again.
17150 - Avoid infinite loop in tor-resolve if tor hangs up on it.
17151 - Fix an assert trigger for clients/servers handling resolves.
17154 Changes in version 0.0.9rc2 - 2004-11-24
17155 o Bugfixes on 0.0.9rc1:
17156 - I broke socks5 support while fixing the eof bug.
17157 - Allow unitless bandwidths and intervals; they default to bytes
17159 - New servers don't start out hibernating; they are active until
17160 they run out of bytes, so they have a better estimate of how
17161 long it takes, and so their operators can know they're working.
17164 Changes in version 0.0.9rc1 - 2004-11-23
17165 o Bugfixes on 0.0.8.1:
17166 - Finally fix a bug that's been plaguing us for a year:
17167 With high load, circuit package window was reaching 0. Whenever
17168 we got a circuit-level sendme, we were reading a lot on each
17169 socket, but only writing out a bit. So we would eventually reach
17170 eof. This would be noticed and acted on even when there were still
17171 bytes sitting in the inbuf.
17172 - When poll() is interrupted, we shouldn't believe the revents values.
17174 o Bugfixes on 0.0.9pre6:
17175 - Fix hibernate bug that caused pre6 to be broken.
17176 - Don't keep rephist info for routers that haven't had activity for
17177 24 hours. (This matters now that clients have keys, since we track
17179 - Never call close_temp_logs while validating log options.
17180 - Fix backslash-escaping on tor.sh.in and torctl.in.
17183 - Implement weekly/monthly/daily accounting: now you specify your
17184 hibernation properties by
17185 AccountingMax N bytes|KB|MB|GB|TB
17186 AccountingStart day|week|month [day] HH:MM
17187 Defaults to "month 1 0:00".
17188 - Let bandwidth and interval config options be specified as 5 bytes,
17189 kb, kilobytes, etc; and as seconds, minutes, hours, days, weeks.
17190 - kill -USR2 now moves all logs to loglevel debug (kill -HUP to
17191 get back to normal.)
17192 - If your requested entry or exit node has advertised bandwidth 0,
17194 - Be more greedy about filling up relay cells -- we try reading again
17195 once we've processed the stuff we read, in case enough has arrived
17196 to fill the last cell completely.
17197 - Apply NT service patch from Osamu Fujino. Still needs more work.
17200 Changes in version 0.0.9pre6 - 2004-11-15
17201 o Bugfixes on 0.0.8.1:
17202 - Fix assert failure on malformed socks4a requests.
17203 - Use identity comparison, not nickname comparison, to choose which
17204 half of circuit-ID-space each side gets to use. This is needed
17205 because sometimes we think of a router as a nickname, and sometimes
17206 as a hex ID, and we can't predict what the other side will do.
17207 - Catch and ignore SIGXFSZ signals when log files exceed 2GB; our
17208 write() call will fail and we handle it there.
17209 - Add a FAST_SMARTLIST define to optionally inline smartlist_get
17210 and smartlist_len, which are two major profiling offenders.
17212 o Bugfixes on 0.0.9pre5:
17213 - Fix a bug in read_all that was corrupting config files on windows.
17214 - When we're raising the max number of open file descriptors to
17215 'unlimited', don't log that we just raised it to '-1'.
17216 - Include event code with events, as required by control-spec.txt.
17217 - Don't give a fingerprint when clients do --list-fingerprint:
17218 it's misleading, because it will never be the same again.
17219 - Stop using strlcpy in tor_strndup, since it was slowing us
17221 - Remove warn on startup about missing cached-directory file.
17222 - Make kill -USR1 work again.
17223 - Hibernate if we start tor during the "wait for wakeup-time" phase
17224 of an accounting interval. Log our hibernation plans better.
17225 - Authoritative dirservers now also cache their directory, so they
17226 have it on start-up.
17229 - Fetch running-routers; cache running-routers; compress
17230 running-routers; serve compressed running-routers.z
17231 - Add NSI installer script contributed by J Doe.
17232 - Commit VC6 and VC7 workspace/project files.
17233 - Commit a tor.spec for making RPM files, with help from jbash.
17234 - Add contrib/torctl.in contributed by Glenn Fink.
17235 - Implement the control-spec's SAVECONF command, to write your
17236 configuration to torrc.
17237 - Get cookie authentication for the controller closer to working.
17238 - Include control-spec.txt in the tarball.
17239 - When set_conf changes our server descriptor, upload a new copy.
17240 But don't upload it too often if there are frequent changes.
17241 - Document authentication config in man page, and document signals
17243 - Clean up confusing parts of man page and torrc.sample.
17244 - Make expand_filename handle ~ and ~username.
17245 - Use autoconf to enable largefile support where necessary. Use
17246 ftello where available, since ftell can fail at 2GB.
17247 - Distinguish between TOR_TLS_CLOSE and TOR_TLS_ERROR, so we can
17248 log more informatively.
17249 - Give a slightly more useful output for "tor -h".
17250 - Refuse application socks connections to port 0.
17251 - Check clock skew for verified servers, but allow unverified
17252 servers and clients to have any clock skew.
17253 - Break DirFetchPostPeriod into:
17254 - DirFetchPeriod for fetching full directory,
17255 - StatusFetchPeriod for fetching running-routers,
17256 - DirPostPeriod for posting server descriptor,
17257 - RendPostPeriod for posting hidden service descriptors.
17258 - Make sure the hidden service descriptors are at a random offset
17259 from each other, to hinder linkability.
17262 Changes in version 0.0.9pre5 - 2004-11-09
17263 o Bugfixes on 0.0.9pre4:
17264 - Fix a seg fault in unit tests (doesn't affect main program).
17265 - Fix an assert bug where a hidden service provider would fail if
17266 the first hop of his rendezvous circuit was down.
17267 - Hidden service operators now correctly handle version 1 style
17268 INTRODUCE1 cells (nobody generates them still, so not a critical
17270 - If do_hup fails, actually notice.
17271 - Handle more errnos from accept() without closing the listener.
17272 Some OpenBSD machines were closing their listeners because
17273 they ran out of file descriptors.
17274 - Send resolve cells to exit routers that are running a new
17275 enough version of the resolve code to work right.
17276 - Better handling of winsock includes on non-MSV win32 compilers.
17277 - Some people had wrapped their tor client/server in a script
17278 that would restart it whenever it died. This did not play well
17279 with our "shut down if your version is obsolete" code. Now people
17280 don't fetch a new directory if their local cached version is
17282 - Make our autogen.sh work on ksh as well as bash.
17285 - Hibernation: New config option "AccountingMaxKB" lets you
17286 set how many KBytes per month you want to allow your server to
17287 consume. Rather than spreading those bytes out evenly over the
17288 month, we instead hibernate for some of the month and pop up
17289 at a deterministic time, work until the bytes are consumed, then
17290 hibernate again. Config option "MonthlyAccountingStart" lets you
17291 specify which day of the month your billing cycle starts on.
17292 - Control interface: a separate program can now talk to your
17293 client/server over a socket, and get/set config options, receive
17294 notifications of circuits and streams starting/finishing/dying,
17295 bandwidth used, etc. The next step is to get some GUIs working.
17296 Let us know if you want to help out. See doc/control-spec.txt .
17297 - Ship a contrib/tor-control.py as an example script to interact
17298 with the control port.
17299 - "tor --hash-password zzyxz" will output a salted password for
17300 use in authenticating to the control interface.
17301 - New log format in config:
17302 "Log minsev[-maxsev] stdout|stderr|syslog" or
17303 "Log minsev[-maxsev] file /var/foo"
17306 - DirPolicy config option, to let people reject incoming addresses
17307 from their dirserver.
17308 - "tor --list-fingerprint" will list your identity key fingerprint
17310 - Add "pass" target for RedirectExit, to make it easier to break
17311 out of a sequence of RedirectExit rules.
17312 - Clients now generate a TLS cert too, in preparation for having
17313 them act more like real nodes.
17314 - Ship src/win32/ in the tarball, so people can use it to build.
17315 - Make old win32 fall back to CWD if SHGetSpecialFolderLocation
17317 - New "router-status" line in directory, to better bind each verified
17318 nickname to its identity key.
17319 - Deprecate unofficial config option abbreviations, and abbreviations
17320 not on the command line.
17321 - Add a pure-C tor-resolve implementation.
17322 - Use getrlimit and friends to ensure we can reach MaxConn (currently
17323 1024) file descriptors.
17325 o Code security improvements, inspired by Ilja:
17326 - Replace sprintf with snprintf. (I think they were all safe, but
17328 - Replace strcpy/strncpy with strlcpy in more places.
17329 - Avoid strcat; use snprintf or strlcat instead.
17330 - snprintf wrapper with consistent (though not C99) overflow behavior.
17333 Changes in version 0.0.9pre4 - 2004-10-17
17334 o Bugfixes on 0.0.9pre3:
17335 - If the server doesn't specify an exit policy, use the real default
17336 exit policy, not reject *:*.
17337 - Ignore fascistfirewall when uploading/downloading hidden service
17338 descriptors, since we go through Tor for those; and when using
17339 an HttpProxy, since we assume it can reach them all.
17340 - When looking for an authoritative dirserver, use only the ones
17341 configured at boot. Don't bother looking in the directory.
17342 - The rest of the fix for get_default_conf_file() on older win32.
17343 - Make 'Routerfile' config option obsolete.
17346 - New 'MyFamily nick1,...' config option for a server to
17347 specify other servers that shouldn't be used in the same circuit
17348 with it. Only believed if nick1 also specifies us.
17349 - New 'NodeFamily nick1,nick2,...' config option for a client to
17350 specify nodes that it doesn't want to use in the same circuit.
17351 - New 'Redirectexit pattern address:port' config option for a
17352 server to redirect exit connections, e.g. to a local squid.
17355 Changes in version 0.0.9pre3 - 2004-10-13
17356 o Bugfixes on 0.0.8.1:
17357 - Better torrc example lines for dirbindaddress and orbindaddress.
17358 - Improved bounds checking on parsed ints (e.g. config options and
17359 the ones we find in directories.)
17360 - Better handling of size_t vs int, so we're more robust on 64
17362 - Fix the rest of the bug where a newly started OR would appear
17363 as unverified even after we've added his fingerprint and hupped
17365 - Fix a bug from 0.0.7: when read() failed on a stream, we would
17366 close it without sending back an end. So 'connection refused'
17367 would simply be ignored and the user would get no response.
17369 o Bugfixes on 0.0.9pre2:
17370 - Serving the cached-on-disk directory to people is bad. We now
17371 provide no directory until we've fetched a fresh one.
17372 - Workaround for bug on windows where cached-directories get crlf
17374 - Make get_default_conf_file() work on older windows too.
17375 - If we write a *:* exit policy line in the descriptor, don't write
17376 any more exit policy lines.
17379 - Use only 0.0.9pre1 and later servers for resolve cells.
17380 - Make the dirservers file obsolete.
17381 - Include a dir-signing-key token in directories to tell the
17382 parsing entity which key is being used to sign.
17383 - Remove the built-in bulky default dirservers string.
17384 - New config option "Dirserver %s:%d [fingerprint]", which can be
17385 repeated as many times as needed. If no dirservers specified,
17386 default to moria1,moria2,tor26.
17387 - Make moria2 advertise a dirport of 80, so people behind firewalls
17388 will be able to get a directory.
17389 - Http proxy support
17390 - Dirservers translate requests for http://%s:%d/x to /x
17391 - You can specify "HttpProxy %s[:%d]" and all dir fetches will
17392 be routed through this host.
17393 - Clients ask for /tor/x rather than /x for new enough dirservers.
17394 This way we can one day coexist peacefully with apache.
17395 - Clients specify a "Host: %s%d" http header, to be compatible
17396 with more proxies, and so running squid on an exit node can work.
17399 Changes in version 0.0.8.1 - 2004-10-13
17401 - Fix a seg fault that can be triggered remotely for Tor
17402 clients/servers with an open dirport.
17403 - Fix a rare assert trigger, where routerinfos for entries in
17404 our cpath would expire while we're building the path.
17405 - Fix a bug in OutboundBindAddress so it (hopefully) works.
17406 - Fix a rare seg fault for people running hidden services on
17407 intermittent connections.
17408 - Fix a bug in parsing opt keywords with objects.
17409 - Fix a stale pointer assert bug when a stream detaches and
17411 - Fix a string format vulnerability (probably not exploitable)
17412 in reporting stats locally.
17413 - Fix an assert trigger: sometimes launching circuits can fail
17414 immediately, e.g. because too many circuits have failed recently.
17415 - Fix a compile warning on 64 bit platforms.
17418 Changes in version 0.0.9pre2 - 2004-10-03
17420 - Make fetching a cached directory work for 64-bit platforms too.
17421 - Make zlib.h a required header, not an optional header.
17424 Changes in version 0.0.9pre1 - 2004-10-01
17426 - Stop using separate defaults for no-config-file and
17427 empty-config-file. Now you have to explicitly turn off SocksPort,
17428 if you don't want it open.
17429 - Fix a bug in OutboundBindAddress so it (hopefully) works.
17430 - Improve man page to mention more of the 0.0.8 features.
17431 - Fix a rare seg fault for people running hidden services on
17432 intermittent connections.
17433 - Change our file IO stuff (especially wrt OpenSSL) so win32 is
17435 - Fix more dns related bugs: send back resolve_failed and end cells
17436 more reliably when the resolve fails, rather than closing the
17437 circuit and then trying to send the cell. Also attach dummy resolve
17438 connections to a circuit *before* calling dns_resolve(), to fix
17439 a bug where cached answers would never be sent in RESOLVED cells.
17440 - When we run out of disk space, or other log writing error, don't
17441 crash. Just stop logging to that log and continue.
17442 - We were starting to daemonize before we opened our logs, so if
17443 there were any problems opening logs, we would complain to stderr,
17444 which wouldn't work, and then mysteriously exit.
17445 - Fix a rare bug where sometimes a verified OR would connect to us
17446 before he'd uploaded his descriptor, which would cause us to
17447 assign conn->nickname as though he's unverified. Now we look through
17448 the fingerprint list to see if he's there.
17449 - Fix a rare assert trigger, where routerinfos for entries in
17450 our cpath would expire while we're building the path.
17453 - Clients can ask dirservers for /dir.z to get a compressed version
17454 of the directory. Only works for servers running 0.0.9, of course.
17455 - Make clients cache directories and use them to seed their router
17456 lists at startup. This means clients have a datadir again.
17457 - Configuration infrastructure support for warning on obsolete
17459 - Respond to content-encoding headers by trying to uncompress as
17461 - Reply with a deflated directory when a client asks for "dir.z".
17462 We could use allow-encodings instead, but allow-encodings isn't
17463 specified in HTTP 1.0.
17464 - Raise the max dns workers from 50 to 100.
17465 - Discourage people from setting their dirfetchpostperiod more often
17466 than once per minute.
17467 - Protect dirservers from overzealous descriptor uploading -- wait
17468 10 seconds after directory gets dirty, before regenerating.
17471 Changes in version 0.0.8 - 2004-08-25
17472 o Port it to SunOS 5.9 / Athena
17475 Changes in version 0.0.8rc2 - 2004-08-20
17476 o Make it compile on cygwin again.
17477 o When picking unverified routers, skip those with low uptime and/or
17478 low bandwidth, depending on what properties you care about.
17481 Changes in version 0.0.8rc1 - 2004-08-18
17482 o Changes from 0.0.7.3:
17484 - Fix assert triggers: if the other side returns an address 0.0.0.0,
17485 don't put it into the client dns cache.
17486 - If a begin failed due to exit policy, but we believe the IP address
17487 should have been allowed, switch that router to exitpolicy reject *:*
17488 until we get our next directory.
17490 - Clients choose nodes proportional to advertised bandwidth.
17491 - Avoid using nodes with low uptime as introduction points.
17492 - Handle servers with dynamic IP addresses: don't replace
17493 options->Address with the resolved one at startup, and
17494 detect our address right before we make a routerinfo each time.
17495 - 'FascistFirewall' option to pick dirservers and ORs on specific
17496 ports; plus 'FirewallPorts' config option to tell FascistFirewall
17497 which ports are open. (Defaults to 80,443)
17498 - Be more aggressive about trying to make circuits when the network
17499 has changed (e.g. when you unsuspend your laptop).
17500 - Check for time skew on http headers; report date in response to
17502 - If the entrynode config line has only one node, don't pick it as
17504 - Add strict{entry|exit}nodes config options. If set to 1, then
17505 we refuse to build circuits that don't include the specified entry
17507 - OutboundBindAddress config option, to bind to a specific
17508 IP address for outgoing connect()s.
17509 - End truncated log entries (e.g. directories) with "[truncated]".
17511 o Patches to 0.0.8preX:
17513 - Patches to compile and run on win32 again (maybe)?
17514 - Fix crash when looking for ~/.torrc with no $HOME set.
17515 - Fix a race bug in the unit tests.
17516 - Handle verified/unverified name collisions better when new
17517 routerinfo's arrive in a directory.
17518 - Sometimes routers were getting entered into the stats before
17519 we'd assigned their identity_digest. Oops.
17520 - Only pick and establish intro points after we've gotten a
17523 - AllowUnverifiedNodes config option to let circuits choose no-name
17524 routers in entry,middle,exit,introduction,rendezvous positions.
17525 Allow middle and rendezvous positions by default.
17526 - Add a man page for tor-resolve.
17529 Changes in version 0.0.7.3 - 2004-08-12
17530 o Stop dnsworkers from triggering an assert failure when you
17531 ask them to resolve the host "".
17534 Changes in version 0.0.8pre3 - 2004-08-09
17535 o Changes from 0.0.7.2:
17536 - Allow multiple ORs with same nickname in routerlist -- now when
17537 people give us one identity key for a nickname, then later
17538 another, we don't constantly complain until the first expires.
17539 - Remember used bandwidth (both in and out), and publish 15-minute
17540 snapshots for the past day into our descriptor.
17541 - You can now fetch $DIRURL/running-routers to get just the
17542 running-routers line, not the whole descriptor list. (But
17543 clients don't use this yet.)
17544 - When people mistakenly use Tor as an http proxy, point them
17545 at the tor-doc.html rather than the INSTALL.
17546 - Remove our mostly unused -- and broken -- hex_encode()
17547 function. Use base16_encode() instead. (Thanks to Timo Lindfors
17548 for pointing out this bug.)
17549 - Rotate onion keys every 12 hours, not every 2 hours, so we have
17550 fewer problems with people using the wrong key.
17551 - Change the default exit policy to reject the default edonkey,
17552 kazaa, gnutella ports.
17553 - Add replace_file() to util.[ch] to handle win32's rename().
17555 o Changes from 0.0.8preX:
17556 - Fix two bugs in saving onion keys to disk when rotating, so
17557 hopefully we'll get fewer people using old onion keys.
17558 - Fix an assert error that was making SocksPolicy not work.
17559 - Be willing to expire routers that have an open dirport -- it's
17560 just the authoritative dirservers we want to not forget.
17561 - Reject tor-resolve requests for .onion addresses early, so we
17562 don't build a whole rendezvous circuit and then fail.
17563 - When you're warning a server that he's unverified, don't cry
17564 wolf unpredictably.
17565 - Fix a race condition: don't try to extend onto a connection
17566 that's still handshaking.
17567 - For servers in clique mode, require the conn to be open before
17568 you'll choose it for your path.
17569 - Fix some cosmetic bugs about duplicate mark-for-close, lack of
17570 end relay cell, etc.
17571 - Measure bandwidth capacity over the last 24 hours, not just 12
17572 - Bugfix: authoritative dirservers were making and signing a new
17573 directory for each client, rather than reusing the cached one.
17576 Changes in version 0.0.8pre2 - 2004-08-04
17577 o Changes from 0.0.7.2:
17579 - Check directory signature _before_ you decide whether you're
17580 you're running an obsolete version and should exit.
17581 - Check directory signature _before_ you parse the running-routers
17582 list to decide who's running or verified.
17583 - Bugfixes and features:
17584 - Check return value of fclose while writing to disk, so we don't
17585 end up with broken files when servers run out of disk space.
17586 - Log a warning if the user uses an unsafe socks variant, so people
17587 are more likely to learn about privoxy or socat.
17588 - Dirservers now include RFC1123-style dates in the HTTP headers,
17589 which one day we will use to better detect clock skew.
17591 o Changes from 0.0.8pre1:
17592 - Make it compile without warnings again on win32.
17593 - Log a warning if you're running an unverified server, to let you
17594 know you might want to get it verified.
17595 - Only pick a default nickname if you plan to be a server.
17598 Changes in version 0.0.8pre1 - 2004-07-23
17600 - Made our unit tests compile again on OpenBSD 3.5, and tor
17601 itself compile again on OpenBSD on a sparc64.
17602 - We were neglecting milliseconds when logging on win32, so
17603 everything appeared to happen at the beginning of each second.
17605 o Protocol changes:
17606 - 'Extend' relay cell payloads now include the digest of the
17607 intended next hop's identity key. Now we can verify that we're
17608 extending to the right router, and also extend to routers we
17609 hadn't heard of before.
17612 - Tor nodes can now act as relays (with an advertised ORPort)
17613 without being manually verified by the dirserver operators.
17614 - Uploaded descriptors of unverified routers are now accepted
17615 by the dirservers, and included in the directory.
17616 - Verified routers are listed by nickname in the running-routers
17617 list; unverified routers are listed as "$<fingerprint>".
17618 - We now use hash-of-identity-key in most places rather than
17619 nickname or addr:port, for improved security/flexibility.
17620 - To avoid Sybil attacks, paths still use only verified servers.
17621 But now we have a chance to play around with hybrid approaches.
17622 - Nodes track bandwidth usage to estimate capacity (not used yet).
17623 - ClientOnly option for nodes that never want to become servers.
17624 - Directory caching.
17625 - "AuthoritativeDir 1" option for the official dirservers.
17626 - Now other nodes (clients and servers) will cache the latest
17627 directory they've pulled down.
17628 - They can enable their DirPort to serve it to others.
17629 - Clients will pull down a directory from any node with an open
17630 DirPort, and check the signature/timestamp correctly.
17631 - Authoritative dirservers now fetch directories from other
17632 authdirservers, to stay better synced.
17633 - Running-routers list tells who's down also, along with noting
17634 if they're verified (listed by nickname) or unverified (listed
17636 - Allow dirservers to serve running-router list separately.
17637 This isn't used yet.
17638 - ORs connect-on-demand to other ORs
17639 - If you get an extend cell to an OR you're not connected to,
17640 connect, handshake, and forward the create cell.
17641 - The authoritative dirservers stay connected to everybody,
17642 and everybody stays connected to 0.0.7 servers, but otherwise
17643 clients/servers expire unused connections after 5 minutes.
17644 - When servers get a sigint, they delay 30 seconds (refusing new
17645 connections) then exit. A second sigint causes immediate exit.
17646 - File and name management:
17647 - Look for .torrc if no CONFDIR "torrc" is found.
17648 - If no datadir is defined, then choose, make, and secure ~/.tor
17650 - If torrc not found, exitpolicy reject *:*.
17651 - Expands ~/ in filenames to $HOME/ (but doesn't yet expand ~arma).
17652 - If no nickname is defined, derive default from hostname.
17653 - Rename secret key files, e.g. identity.key -> secret_id_key,
17654 to discourage people from mailing their identity key to tor-ops.
17655 - Refuse to build a circuit before the directory has arrived --
17656 it won't work anyway, since you won't know the right onion keys
17658 - Try other dirservers immediately if the one you try is down. This
17659 should tolerate down dirservers better now.
17660 - Parse tor version numbers so we can do an is-newer-than check
17661 rather than an is-in-the-list check.
17662 - New socks command 'resolve', to let us shim gethostbyname()
17664 - A 'tor_resolve' script to access the socks resolve functionality.
17665 - A new socks-extensions.txt doc file to describe our
17666 interpretation and extensions to the socks protocols.
17667 - Add a ContactInfo option, which gets published in descriptor.
17668 - Publish OR uptime in descriptor (and thus in directory) too.
17669 - Write tor version at the top of each log file
17670 - New docs in the tarball:
17672 - Document that you should proxy your SSL traffic too.
17675 Changes in version 0.0.7.2 - 2004-07-07
17676 o A better fix for the 0.0.0.0 problem, that will hopefully
17677 eliminate the remaining related assertion failures.
17680 Changes in version 0.0.7.1 - 2004-07-04
17681 o When an address resolves to 0.0.0.0, treat it as a failed resolve,
17682 since internally we use 0.0.0.0 to signify "not yet resolved".
17685 Changes in version 0.0.7 - 2004-06-07
17686 o Updated the man page to reflect the new features.
17689 Changes in version 0.0.7rc2 - 2004-06-06
17690 o Changes from 0.0.7rc1:
17691 - Make it build on Win32 again.
17692 o Changes from 0.0.6.2:
17693 - Rotate dnsworkers and cpuworkers on SIGHUP, so they get new config
17697 Changes in version 0.0.7rc1 - 2004-06-02
17699 - On sighup, we were adding another log without removing the first
17700 one. So log messages would get duplicated n times for n sighups.
17701 - Several cases of using a connection after we'd freed it. The
17702 problem was that connections that are pending resolve are in both
17703 the pending_resolve tree, and also the circuit's resolving_streams
17704 list. When you want to remove one, you must remove it from both.
17705 - Fix a double-mark-for-close where an end cell arrived for a
17706 resolving stream, and then the resolve failed.
17707 - Check directory signatures based on name of signer, not on whom
17708 we got the directory from. This will let us cache directories more
17711 - Crank up some of our constants to handle more users.
17714 Changes in version 0.0.7pre1 - 2004-06-02
17715 o Fixes for crashes and other obnoxious bugs:
17716 - Fix an epipe bug: sometimes when directory connections failed
17717 to connect, we would give them a chance to flush before closing
17719 - When we detached from a circuit because of resolvefailed, we
17720 would immediately try the same circuit twice more, and then
17721 give up on the resolve thinking we'd tried three different
17723 - Limit the number of intro circuits we'll attempt to build for a
17724 hidden service per 15-minute period.
17725 - Check recommended-software string *early*, before actually parsing
17726 the directory. Thus we can detect an obsolete version and exit,
17727 even if the new directory format doesn't parse.
17728 o Fixes for security bugs:
17729 - Remember which nodes are dirservers when you startup, and if a
17730 random OR enables his dirport, don't automatically assume he's
17731 a trusted dirserver.
17733 - Directory connections were asking the wrong poll socket to
17734 start writing, and not asking themselves to start writing.
17735 - When we detached from a circuit because we sent a begin but
17736 didn't get a connected, we would use it again the first time;
17737 but after that we would correctly switch to a different one.
17738 - Stop warning when the first onion decrypt attempt fails; they
17739 will sometimes legitimately fail now that we rotate keys.
17740 - Override unaligned-access-ok check when $host_cpu is ia64 or
17741 arm. Apparently they allow it but the kernel whines.
17742 - Dirservers try to reconnect periodically too, in case connections
17744 - Fix some memory leaks in directory servers.
17745 - Allow backslash in Win32 filenames.
17746 - Made Tor build complain-free on FreeBSD, hopefully without
17747 breaking other BSD builds. We'll see.
17749 - Doxygen markup on all functions and global variables.
17750 - Make directory functions update routerlist, not replace it. So
17751 now directory disagreements are not so critical a problem.
17752 - Remove the upper limit on number of descriptors in a dirserver's
17753 directory (not that we were anywhere close).
17754 - Allow multiple logfiles at different severity ranges.
17755 - Allow *BindAddress to specify ":port" rather than setting *Port
17756 separately. Allow multiple instances of each BindAddress config
17757 option, so you can bind to multiple interfaces if you want.
17758 - Allow multiple exit policy lines, which are processed in order.
17759 Now we don't need that huge line with all the commas in it.
17760 - Enable accept/reject policies on SOCKS connections, so you can bind
17761 to 0.0.0.0 but still control who can use your OP.
17764 Changes in version 0.0.6.2 - 2004-05-16
17765 o Our integrity-checking digest was checking only the most recent cell,
17766 not the previous cells like we'd thought.
17767 Thanks to Stefan Mark for finding the flaw!
17770 Changes in version 0.0.6.1 - 2004-05-06
17771 o Fix two bugs in our AES counter-mode implementation (this affected
17772 onion-level stream encryption, but not TLS-level). It turns
17773 out we were doing something much more akin to a 16-character
17774 polyalphabetic cipher. Oops.
17775 Thanks to Stefan Mark for finding the flaw!
17776 o Retire moria3 as a directory server, and add tor26 as a directory
17780 Changes in version 0.0.6 - 2004-05-02
17781 [version bump only]
17784 Changes in version 0.0.6rc4 - 2004-05-01
17785 o Update the built-in dirservers list to use the new directory format
17786 o Fix a rare seg fault: if a node offering a hidden service attempts
17787 to build a circuit to Alice's rendezvous point and fails before it
17788 reaches the last hop, it retries with a different circuit, but
17790 o Handle windows socket errors correctly.
17793 Changes in version 0.0.6rc3 - 2004-04-28
17794 o Don't expire non-general excess circuits (if we had enough
17795 circuits open, we were expiring rendezvous circuits -- even
17796 when they had a stream attached. oops.)
17797 o Fetch randomness from /dev/urandom better (not via fopen/fread)
17798 o Better debugging for tls errors
17799 o Some versions of openssl have an SSL_pending function that erroneously
17800 returns bytes when there is a non-application record pending.
17801 o Set Content-Type on the directory and hidserv descriptor.
17802 o Remove IVs from cipher code, since AES-ctr has none.
17803 o Win32 fixes. Tor now compiles on win32 with no warnings/errors.
17804 o We were using an array of length zero in a few places.
17805 o win32's gethostbyname can't resolve an IP to an IP.
17806 o win32's close can't close a socket.
17809 Changes in version 0.0.6rc2 - 2004-04-26
17810 o Fix a bug where we were closing tls connections intermittently.
17811 It turns out openssl keeps its errors around -- so if an error
17812 happens, and you don't ask about it, and then another openssl
17813 operation happens and succeeds, and you ask if there was an error,
17814 it tells you about the first error. Fun fun.
17815 o Fix a bug that's been lurking since 27 may 03 (!)
17816 When passing back a destroy cell, we would use the wrong circ id.
17817 'Mostly harmless', but still worth fixing.
17818 o Since we don't support truncateds much, don't bother sending them;
17819 just close the circ.
17820 o check for <machine/limits.h> so we build on NetBSD again (I hope).
17821 o don't crash if a conn that sent a begin has suddenly lost its circuit
17822 (this was quite rare).
17825 Changes in version 0.0.6rc1 - 2004-04-25
17826 o We now rotate link (tls context) keys and onion keys.
17827 o CREATE cells now include oaep padding, so you can tell
17828 if you decrypted them correctly.
17829 o Add bandwidthburst to server descriptor.
17830 o Directories now say which dirserver signed them.
17831 o Use a tor_assert macro that logs failed assertions too.
17834 Changes in version 0.0.6pre5 - 2004-04-18
17835 o changes from 0.0.6pre4:
17836 - make tor build on broken freebsd 5.2 installs
17837 - fix a failed assert when you try an intro point, get a nack, and try
17838 a second one and it works.
17839 - when alice uses a port that the hidden service doesn't accept,
17840 it now sends back an end cell (denied by exit policy). otherwise
17841 alice would just have to wait to time out.
17842 - fix another rare bug: when we had tried all the intro
17843 points for a hidden service, we fetched the descriptor
17844 again, but we left our introcirc thinking it had already
17845 sent an intro, so it kept waiting for a response...
17846 - bugfix: when you sleep your hidden-service laptop, as soon
17847 as it wakes up it tries to upload a service descriptor, but
17848 socketpair fails for some reason (localhost not up yet?).
17849 now we simply give up on that upload, and we'll try again later.
17850 i'd still like to find the bug though.
17851 - if an intro circ waiting for an ack dies before getting one, then
17853 - we were reusing stale service descriptors and refetching usable
17857 Changes in version 0.0.6pre4 - 2004-04-14
17858 o changes from 0.0.6pre3:
17859 - when bob fails to connect to the rendezvous point, and his
17860 circ didn't fail because of the rendezvous point itself, then
17861 he retries a couple of times
17862 - we expire introduction and rendezvous circs more thoroughly
17863 (sometimes they were hanging around forever)
17864 - we expire unattached rendezvous streams that have been around
17865 too long (they were sticking around forever).
17866 - fix a measly fencepost error that was crashing everybody with
17870 Changes in version 0.0.6pre3 - 2004-04-14
17871 o changes from 0.0.6pre2:
17872 - make hup work again
17873 - fix some memory leaks for dirservers
17874 - allow more skew in rendezvous descriptor timestamps, to help
17875 handle people like blanu who don't know what time it is
17876 - normal circs are 3 hops, but some rend/intro circs are 4, if
17877 the initiator doesn't get to choose the last hop
17878 - send acks for introductions, so alice can know whether to try
17880 - bob publishes intro points more correctly
17881 o changes from 0.0.5:
17882 - fix an assert trigger that's been plaguing us since the days
17883 of 0.0.2prexx (thanks weasel!)
17884 - retry stream correctly when we fail to connect because of
17885 exit-policy-reject (should try another) or can't-resolve-address
17886 (also should try another, because dns on random internet servers
17888 - when we hup a dirserver and we've *removed* a server from the
17889 approved-routers list, now we remove that server from the
17890 in-memory directories too
17893 Changes in version 0.0.6pre2 - 2004-04-08
17894 o We fixed our base32 implementation. Now it works on all architectures.
17897 Changes in version 0.0.6pre1 - 2004-04-08
17899 - Hidden services and rendezvous points are implemented. Go to
17900 http://6sxoyfb3h2nvok2d.onion/ for an index of currently available
17901 hidden services. (This only works via a socks4a proxy such as
17902 Privoxy, and currently it's quite slow.)
17905 Changes in version 0.0.5 - 2004-03-30
17906 [version bump only]
17909 Changes in version 0.0.5rc3 - 2004-03-29
17910 o Install torrc as torrc.sample -- we no longer clobber your
17912 o Re-enable recommendedversion checking (we broke it in rc2, oops)
17913 o Add in a 'notice' log level for things the operator should hear
17914 but that aren't warnings
17917 Changes in version 0.0.5rc2 - 2004-03-29
17918 o Hold socks connection open until reply is flushed (if possible)
17919 o Make exit nodes resolve IPs to IPs immediately, rather than asking
17920 the dns farm to do it.
17921 o Fix c99 aliasing warnings in rephist.c
17922 o Don't include server descriptors that are older than 24 hours in the
17924 o Give socks 'reject' replies their whole 15s to attempt to flush,
17925 rather than seeing the 60s timeout and assuming the flush had failed.
17926 o Clean automake droppings from the cvs repository
17929 Changes in version 0.0.5rc1 - 2004-03-28
17930 o Fix mangled-state bug in directory fetching (was causing sigpipes).
17931 o Only build circuits after we've fetched the directory: clients were
17932 using only the directory servers before they'd fetched a directory.
17933 This also means longer startup time; so it goes.
17934 o Fix an assert trigger where an OP would fail to handshake, and we'd
17935 expect it to have a nickname.
17936 o Work around a tsocks bug: do a socks reject when AP connection dies
17937 early, else tsocks goes into an infinite loop.
17940 Changes in version 0.0.4 - 2004-03-26
17941 o When connecting to a dirserver or OR and the network is down,
17945 Changes in version 0.0.3 - 2004-03-26
17946 o Warn and fail if server chose a nickname with illegal characters
17947 o Port to Solaris and Sparc:
17948 - include missing header fcntl.h
17949 - have autoconf find -lsocket -lnsl automatically
17950 - deal with hardware word alignment
17951 - make uname() work (solaris has a different return convention)
17952 - switch from using signal() to sigaction()
17953 o Preliminary work on reputation system:
17954 - Keep statistics on success/fail of connect attempts; they're published
17955 by kill -USR1 currently.
17956 - Add a RunTesting option to try to learn link state by creating test
17957 circuits, even when SocksPort is off.
17958 - Remove unused open circuits when there are too many.
17961 Changes in version 0.0.2 - 2004-03-19
17962 - Include strlcpy and strlcat for safer string ops
17963 - define INADDR_NONE so we compile (but still not run) on solaris
17966 Changes in version 0.0.2pre27 - 2004-03-14
17968 - Allow internal tor networks (we were rejecting internal IPs,
17969 now we allow them if they're set explicitly).
17970 - And fix a few endian issues.
17973 Changes in version 0.0.2pre26 - 2004-03-14
17975 - If a stream times out after 15s without a connected cell, don't
17976 try that circuit again: try a new one.
17977 - Retry streams at most 4 times. Then give up.
17978 - When a dirserver gets a descriptor from an unknown router, it
17979 logs its fingerprint (so the dirserver operator can choose to
17980 accept it even without mail from the server operator).
17981 - Inform unapproved servers when we reject their descriptors.
17982 - Make tor build on Windows again. It works as a client, who knows
17984 - Clearer instructions in the torrc for how to set up a server.
17985 - Be more efficient about reading fd's when our global token bucket
17986 (used for rate limiting) becomes empty.
17988 - Stop asserting that computers always go forward in time. It's
17990 - When we sent a cell (e.g. destroy) and then marked an OR connection
17991 expired, we might close it before finishing a flush if the other
17992 side isn't reading right then.
17993 - Don't allow dirservers to start if they haven't defined
17994 RecommendedVersions
17995 - We were caching transient dns failures. Oops.
17996 - Prevent servers from publishing an internal IP as their address.
17997 - Address a strcat vulnerability in circuit.c
18000 Changes in version 0.0.2pre25 - 2004-03-04
18002 - Put the OR's IP in its router descriptor, not its fqdn. That way
18003 we'll stop being stalled by gethostbyname for nodes with flaky dns,
18006 - If the user typed in an address that didn't resolve, the server
18010 Changes in version 0.0.2pre24 - 2004-03-03
18012 - Fix an assertion failure in dns.c, where we were trying to dequeue
18013 a pending dns resolve even if it wasn't pending
18014 - Fix a spurious socks5 warning about still trying to write after the
18015 connection is finished.
18016 - Hold certain marked_for_close connections open until they're finished
18017 flushing, rather than losing bytes by closing them too early.
18018 - Correctly report the reason for ending a stream
18019 - Remove some duplicate calls to connection_mark_for_close
18020 - Put switch_id and start_daemon earlier in the boot sequence, so it
18021 will actually try to chdir() to options.DataDirectory
18022 - Make 'make test' exit(1) if a test fails; fix some unit tests
18023 - Make tor fail when you use a config option it doesn't know about,
18024 rather than warn and continue.
18025 - Make --version work
18026 - Bugfixes on the rpm spec file and tor.sh, so it's more up to date
18029 Changes in version 0.0.2pre23 - 2004-02-29
18031 - Print a statement when the first circ is finished, so the user
18032 knows it's working.
18033 - If a relay cell is unrecognized at the end of the circuit,
18034 send back a destroy. (So attacks to mutate cells are more
18036 - New config option 'excludenodes' to avoid certain nodes for circuits.
18037 - When it daemonizes, it chdir's to the DataDirectory rather than "/",
18038 so you can collect coredumps there.
18040 - Fix a bug in tls flushing where sometimes data got wedged and
18041 didn't flush until more data got sent. Hopefully this bug was
18042 a big factor in the random delays we were seeing.
18043 - Make 'connected' cells include the resolved IP, so the client
18044 dns cache actually gets populated.
18045 - Disallow changing from ORPort=0 to ORPort>0 on hup.
18046 - When we time-out on a stream and detach from the circuit, send an
18047 end cell down it first.
18048 - Only warn about an unknown router (in exitnodes, entrynodes,
18049 excludenodes) after we've fetched a directory.
18052 Changes in version 0.0.2pre22 - 2004-02-26
18054 - Servers publish less revealing uname information in descriptors.
18055 - More memory tracking and assertions, to crash more usefully when
18057 - If the default torrc isn't there, just use some default defaults.
18058 Plus provide an internal dirservers file if they don't have one.
18059 - When the user tries to use Tor as an http proxy, give them an http
18060 501 failure explaining that we're a socks proxy.
18061 - Dump a new router.desc on hup, to help confused people who change
18062 their exit policies and then wonder why router.desc doesn't reflect
18064 - Clean up the generic tor.sh init script that we ship with.
18066 - If the exit stream is pending on the resolve, and a destroy arrives,
18067 then the stream wasn't getting removed from the pending list. I
18068 think this was the one causing recent server crashes.
18069 - Use a more robust poll on OSX 10.3, since their poll is flaky.
18070 - When it couldn't resolve any dirservers, it was useless from then on.
18071 Now it reloads the RouterFile (or default dirservers) if it has no
18073 - Move the 'tor' binary back to /usr/local/bin/ -- it turns out
18074 many users don't even *have* a /usr/local/sbin/.
18077 Changes in version 0.0.2pre21 - 2004-02-18
18079 - There's a ChangeLog file that actually reflects the changelog.
18080 - There's a 'torify' wrapper script, with an accompanying
18081 tor-tsocks.conf, that simplifies the process of using tsocks for
18082 tor. It even has a man page.
18083 - The tor binary gets installed to sbin rather than bin now.
18084 - Retry streams where the connected cell hasn't arrived in 15 seconds
18085 - Clean up exit policy handling -- get the default out of the torrc,
18086 so we can update it without forcing each server operator to fix
18088 - Allow imaps and pop3s in default exit policy
18090 - Prevent picking middleman nodes as the last node in the circuit
18093 Changes in version 0.0.2pre20 - 2004-01-30
18095 - We now have a deb package, and it's in debian unstable. Go to
18096 it, apt-getters. :)
18097 - I've split the TotalBandwidth option into BandwidthRate (how many
18098 bytes per second you want to allow, long-term) and
18099 BandwidthBurst (how many bytes you will allow at once before the cap
18100 kicks in). This better token bucket approach lets you, say, set
18101 BandwidthRate to 10KB/s and BandwidthBurst to 10MB, allowing good
18102 performance while not exceeding your monthly bandwidth quota.
18103 - Push out a tls record's worth of data once you've got it, rather
18104 than waiting until you've read everything waiting to be read. This
18105 may improve performance by pipelining better. We'll see.
18106 - Add an AP_CONN_STATE_CONNECTING state, to allow streams to detach
18107 from failed circuits (if they haven't been connected yet) and attach
18109 - Expire old streams that haven't managed to connect. Some day we'll
18110 have them reattach to new circuits instead.
18113 - Fix several memory leaks that were causing servers to become bloated
18115 - Fix a few very rare assert triggers. A few more remain.
18116 - Setuid to User _before_ complaining about running as root.
18119 Changes in version 0.0.2pre19 - 2004-01-07
18121 - Fix deadlock condition in dns farm. We were telling a child to die by
18122 closing the parent's file descriptor to him. But newer children were
18123 inheriting the open file descriptor from the parent, and since they
18124 weren't closing it, the socket never closed, so the child never read
18125 eof, so he never knew to exit. Similarly, dns workers were holding
18126 open other sockets, leading to all sorts of chaos.
18127 - New cleaner daemon() code for forking and backgrounding.
18128 - If you log to a file, it now prints an entry at the top of the
18129 logfile so you know it's working.
18130 - The onionskin challenge length was 30 bytes longer than necessary.
18131 - Started to patch up the spec so it's not quite so out of date.
18134 Changes in version 0.0.2pre18 - 2004-01-02
18136 - Fix endian issues with the 'integrity' field in the relay header.
18137 - Fix a potential bug where connections in state
18138 AP_CONN_STATE_CIRCUIT_WAIT might unexpectedly ask to write.
18141 Changes in version 0.0.2pre17 - 2003-12-30
18143 - Made --debuglogfile (or any second log file, actually) work.
18144 - Resolved an edge case in get_unique_circ_id_by_conn where a smart
18145 adversary could force us into an infinite loop.
18148 - Each onionskin handshake now includes a hash of the computed key,
18149 to prove the server's identity and help perfect forward secrecy.
18150 - Changed cell size from 256 to 512 bytes (working toward compatibility
18152 - Changed cell length to 2 bytes, and moved it to the relay header.
18153 - Implemented end-to-end integrity checking for the payloads of
18155 - Separated streamid from 'recognized' (otherwise circuits will get
18156 messed up when we try to have streams exit from the middle). We
18157 use the integrity-checking to confirm that a cell is addressed to
18159 - Randomize the initial circid and streamid values, so an adversary who
18160 breaks into a node can't learn how many circuits or streams have
18164 Changes in version 0.0.2pre16 - 2003-12-14
18166 - Fixed a bug that made HUP trigger an assert
18167 - Fixed a bug where a circuit that immediately failed wasn't being
18168 counted as a failed circuit in counting retries.
18171 - Now we close the circuit when we get a truncated cell: otherwise we're
18172 open to an anonymity attack where a bad node in the path truncates
18173 the circuit and then we open streams at him.
18174 - Add port ranges to exit policies
18175 - Add a conservative default exit policy
18176 - Warn if you're running tor as root
18177 - on HUP, retry OR connections and close/rebind listeners
18178 - options.EntryNodes: try these nodes first when picking the first node
18179 - options.ExitNodes: if your best choices happen to include any of
18180 your preferred exit nodes, you choose among just those preferred
18182 - options.ExcludedNodes: nodes that are never picked in path building
18185 Changes in version 0.0.2pre15 - 2003-12-03
18186 o Robustness and bugfixes:
18187 - Sometimes clients would cache incorrect DNS resolves, which would
18188 really screw things up.
18189 - An OP that goes offline would slowly leak all its sockets and stop
18191 - A wide variety of bugfixes in exit node selection, exit policy
18192 handling, and processing pending streams when a new circuit is
18194 - Pick nodes for a path only from those the directory says are up
18195 - Choose randomly from all running dirservers, not always the first one
18196 - Increase allowed http header size for directory fetch.
18197 - Stop writing to stderr (if we're daemonized it will be closed).
18198 - Enable -g always, so cores will be more useful to me.
18199 - Switch "-lcrypto -lssl" to "-lssl -lcrypto" for broken distributions.
18202 - Wrote a man page. It lists commonly used options.
18205 - Change default loglevel to warn.
18206 - Make PidFile default to null rather than littering in your CWD.
18207 - OnionRouter config option is now obsolete. Instead it just checks
18209 - Moved to a single unified torrc file for both clients and servers.
18212 Changes in version 0.0.2pre14 - 2003-11-29
18213 o Robustness and bugfixes:
18214 - Force the admin to make the DataDirectory himself
18215 - to get ownership/permissions right
18216 - so clients no longer make a DataDirectory and then never use it
18217 - fix bug where a client who was offline for 45 minutes would never
18218 pull down a directory again
18219 - fix (or at least hide really well) the dns assert bug that was
18220 causing server crashes
18221 - warnings and improved robustness wrt clockskew for certs
18222 - use the native daemon(3) to daemonize, when available
18223 - exit if bind() fails
18224 - exit if neither socksport nor orport is defined
18225 - include our own tor_timegm (Win32 doesn't have its own)
18226 - bugfix for win32 with lots of connections
18227 - fix minor bias in PRNG
18228 - make dirserver more robust to corrupt cached directory
18231 - Wrote the design document (woo)
18233 o Circuit building and exit policies:
18234 - Circuits no longer try to use nodes that the directory has told them
18236 - Exit policies now support bitmasks (18.0.0.0/255.0.0.0) and
18237 bitcounts (18.0.0.0/8).
18238 - Make AP connections standby for a circuit if no suitable circuit
18239 exists, rather than failing
18240 - Circuits choose exit node based on addr/port, exit policies, and
18241 which AP connections are standing by
18242 - Bump min pathlen from 2 to 3
18243 - Relay end cells have a payload to describe why the stream ended.
18244 - If the stream failed because of exit policy, try again with a new
18246 - Clients have a dns cache to remember resolved addresses.
18247 - Notice more quickly when we have no working circuits
18250 - APPort is now called SocksPort
18251 - SocksBindAddress, ORBindAddress, DirBindAddress let you configure
18253 - RecommendedVersions is now a config variable rather than
18254 hardcoded (for dirservers)
18255 - Reloads config on HUP
18256 - Usage info on -h or --help
18257 - If you set User and Group config vars, it'll setu/gid to them.
18260 Changes in version 0.0.2pre13 - 2003-10-19
18261 o General stability:
18262 - SSL_write no longer fails when it returns WANTWRITE and the number
18263 of bytes in the buf has changed by the next SSL_write call.
18264 - Fix segfault fetching directory when network is down
18265 - Fix a variety of minor memory leaks
18266 - Dirservers reload the fingerprints file on HUP, so I don't have
18267 to take down the network when I approve a new router
18268 - Default server config file has explicit Address line to specify fqdn
18271 - Buffers grow and shrink as needed (Cut process size from 20M to 2M)
18272 - Make listener connections not ever alloc bufs
18274 o Autoconf improvements:
18275 - don't clobber an external CFLAGS in ./configure
18276 - Make install now works
18277 - create var/lib/tor on make install
18278 - autocreate a tor.sh initscript to help distribs
18279 - autocreate the torrc and sample-server-torrc with correct paths
18281 o Log files and Daemonizing now work:
18282 - If --DebugLogFile is specified, log to it at -l debug
18283 - If --LogFile is specified, use it instead of commandline
18284 - If --RunAsDaemon is set, tor forks and backgrounds on startup